I don't remember if I ever got that error; probably I did and checked the "don't show again" box. We don't have debug symbols for the EXE - but we do have them for the DLL.Your screenshot help me 1 step further but now I get this error: [...]
The mod=... command argument should cause the mod to be loaded. In my screenshot it's ini=... – which also works, if the respective ini file loads the mod.and it loads BtS not CoM![]()
There are instructions at the end of the opening post of Nightinggale's makefile thread. And this is what I've put in the AdvCiv manual:BTW I tried googling on how to set up the debugger in VS properly but didn't find anything useful yet.
Spoiler :
To attach the VS debugger, I recommend creating a copy of
My Games\Beyond the Sword\CivilizationIV.ini, e.g. named AdvCivDebug.ini. It's easiest to place it in the same directory as Civ4BeyondSword.exe (CIV4_PATH directory). In the copy, set FullScreen = 0 and Mod = Mods\AdvCiv. You may also want to reduce ScreenHeight a little (rationale) and make some other debug-friendly settings: CheatCode = chipotle, LoggingEnabled = 1, AutoSaveInterval = 1. Then select the “Debug” configuration in VS 2010 and under “Configuration Properties” - “Debugging,” enter Civ4BeyondSword.exe with its full path(!) into the “Command” field and ini=AdvCivDebug.ini into “Command Arguments”. (VS will write that information into CvGameCoreDLL\Project\AdvCiv.vcxproj.user; that file can also be edited manually.) You can then “Start Debugging” via the “Debug” menu.





)

![Pissed [pissed] [pissed]](/images/smilies/pissed.gif)