after spending 2 days cleaning up mod bugs in nukemod (they piled up sence last i checked) i managed to get the mod to run stable, and i managed to get debug fred to stop complaining. to my astonishment even the latest cvs build worked. so i resumed modding. i fixed a few bugs, i tested a feature or two. and did a bunch of other stuff without screwing anything up. then i decided i needed another weapon. so i copy an old weapon, change the name and a couple of entries. and suddently the mod just wouldnt run, its as if all the bugs came back. after 6 hours of trying to figure out what i did wrong i decided to stop messing with the mod data, and try screwing with some of fs's settings. i tried killing the sound, and i toggled features. finally i decided to switch over to opengl mode. suprisingly the game stopped crashing. i switched back to d3d mode and got the same crash. so then i thought maybe my video drivers got borked so i reinsalled my vid drivers and i still get the same crash. id much perfer d3d cause it uses my env maps. what i dont understand is how can adding a weapon make one rendered work and another fail? furthermore how can the problem linger even after reverting a backup of the changed files? freespace is starting to evade all reason. perhaps it has become self aware.
*edit*
my point is that was working fine with d3d at one point, and all the sudden it crashes on mission commit. even when i just run normal fsopen it does this. it was working fine with the same buld before and now it only runs in ogl. whats going on?
