Call of Duty: Modern Warfare 2 (Windows)/Debug Material

This is a sub-page of Call of Duty: Modern Warfare 2 (Windows).

This page is dedicated to the debugging content from Call of Duty: Modern Warfare 2. They can be accessed using console commands or modding.

To do:
Get more debugging commands. There is probably more than this.

Crash Debugger?

This needs some investigation.
Discuss ideas and findings on the talk page.

In this image, the Multiplayer section of the game crashed while attempting to write to a .cfg file.

It turns out the game has a built in crash debugger that can pop up if certain fatal errors occur during game play. For example, the debugger will not pop up if the game can't find the .ff of a map when it is trying to load it, but it will pop up if the game can't find the .d3dbsp of a map while loading that map.

If the player were to use a modified executable (specifically, one that adds the developer console back into the Singleplayer section of the game), they would be able to access the debugger by simply pressing F1 in-game. This would pop up the same window but the player is actually able to enter commands into a text box and see anything that is being logged.

developer_script

To access this, go into the developer console and type /developer_script 1. Below is the result.

phys_drawDebugInfo

To access this, go into the developer console and type /phys_drawDebugInfo 1. Below is the result. Judging from this command's name, it would definitely have been used to debug the physics engine or something that had to do with the physics.

cg_drawFPS

To access this, go into the developer console and type /cg_drawFPS *. Replace the * with either 1, 2, 3, or 4. Below are the results for each number.