Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
op2_sdk:projectsettings [2016/10/06 08:44] – [Debugging Custom Mission DLLs] vagabond | op2_sdk:projectsettings [2016/11/03 17:40] (current) – Moved Debuging Scenario information to a separate wiki page. vagabond | ||
---|---|---|---|
Line 70: | Line 70: | ||
---- | ---- | ||
- | + | - //Go Back to [[op2_sdk: | |
- | ===== Debugging Custom Mission DLLs ===== | + | |
- | + | ||
- | Since we do not have access to the Outpost 2 source code or program debug database (PDB file), we cannot step through the Outpost 2 executable code or compare the stack trace with source code. However, we can still debug custom scenario DLLs. | + | |
- | + | ||
- | In order to debug your DLL, follow the required steps from previous sections to ensure a copy of all required files (mission DLL, MAP file, tech tree file, etc) are contained in the Outpost 2 root directory. Then ensure your Visual Studio project is linked to Outpost 2. | + | |
- | + | ||
- | - Recompile your project if needed. | + | |
- | - Set a break point where you want to examine the code or perform whatever other debugging action. | + | |
- | - Press Start Debugging (or hit F5). Outpost 2 should load normally. Once Outpost 2 accesses your DLL, Visual Studio should pause the program at the break point and let you examine the stack trace. | + | |
- | + | ||
- | {{ op2_sdk: | + | |
- | + | ||
- | **Note:** //Visual Studio must have access to your scenario' | + | |
- | + | ||
- | ---- | + | |
- | - //Go Back to [[op2_sdk: | + | |
- //Go Back to [[outpost_2: | - //Go Back to [[outpost_2: | ||
- | - //Go Back to [[http:// | + | - //Go Back to [[http:// |