Deprecated Darkstar fourms

I compiled a fresh build (x86) & database and it always crashes with release build but not debug. How can i pinpoint a crash when not in debug mode?

I have the same problem, so I just compile using debug default.
However, one thing I notice, the game server does not go to the root sarkstar directory when building via release. You can go to the win32 folder, the game folder, the release folder, and move the exe and .pdb out. Copy or cut and paste it in the darkstar folder. It requires some libraries it will not be able to find if you leave it in the release folder.

Delaide wrote:I have the same problem, so I just compile using debug default.
However, one thing I notice, the game server does not go to the root sarkstar directory when building via release. You can go to the win32 folder, the game folder, the release folder, and move the exe and .pdb out. Copy or cut and paste it in the darkstar folder. It requires some libraries it will not be able to find if you leave it in the release folder.

I made a .batch file that automatically copies the release binary to my dsp folder. I've tried to follow steps from Microsoft to debug a release version but i always end up getting 'basepath cannot be relative' even by changing it to the /dsp root.

the "Command" property under Debugging in the solution properties was the cause for that

at any rate, I fixed both the crash and the compiling, so you should be able to debug release and run release without crashing

kjLotus wrote:the "Command" property under Debugging in the solution properties was the cause for that

at any rate, I fixed both the crash and the compiling, so you should be able to debug release and run release without crashing

Awesome, many thanks!