no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Last revision | |||
— | op2_sdk:debugging_scenarios [2016/11/03 17:51] – created vagabond | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Debugging Custom Scenario 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' | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ====== Debugging Multiplayer Scenarios ====== | ||
+ | |||
+ | Multiple instances of Outpost 2 may be opened on the same computer. From multiple open instances of Outpost 2 on the same computer, TCP/IP games may be ran without issue. This allows for testing Outpost 2 multiplayer scenarios without requiring multiple computers. Setting and stepping through breakpoints within Visual Studio will not break Outpost 2 network links. | ||
+ | |||
+ | **Opening multiple Instances of Outpost 2 From Visual Studio** | ||
+ | |||
+ | - Ensure the Outpost 2 executable is referenced in your solution as described on the [[op2_sdk: | ||
+ | - Compile and transfer the required files to the Outpost 2 directory. To automate the process, see the [[op2_sdk: | ||
+ | - Open Outpost 2 from Visual Studio for debugging. | ||
+ | - From the Solution Explorer: right click on the Outpost 2 executable -> Debug -> Start New Instance. | ||
+ | - Start the multiplayer scenario and debug as needed. | ||
+ | |||
+ | {{ op2_sdk: | ||
+ | |||
+ | ---- | ||
+ | - //Go Back to [[op2_sdk: | ||
+ | - //Go Back to [[outpost_2: | ||
+ | - //Go Back to [[http:// | ||