How to attach Visual Studio Debugger to a mission DLL - OPU Launcher

[Vagabond]

So, we are trying to debug a mission DLL. I used to be able to attach the VS debugger using the setup described at https://wiki.outpost2.net/doku.php?id=op2_sdk:projectsettings under the section Referencing the Outpost 2 executable.

There is a really long thread that discusses how I got to writing the wiki article here: https://forum.outpost2.net/index.php/topic,5793.0.html

I'm trying to figure out if I am just forgetting a step from years ago, or if using the OPULauncher changes what needs to happen to get VS to register a breakpoint in the mission DLL source code. I'm wondering if someone has recently tried debugging a mission and could help? We are using VS 2022 Community Edition right now, but would be willing to update to VS2026 if helpful.

Thanks,
Brett

[Sirbomber]

I've never included the game executable as a secondary project, but in the project debugging properties, setting the command to the base OP2 executable with a command of /OPU has always worked reliably for me.