DB trouble

[Flame Spawn]

DB crashes left and right whenever I save, which erases the map data and forces me to use a backup file it creates. Last time the friggin thing crashed when I was selecting New Map!!! *burn* Anyone else having DB problems!?!?!?!?!?!?!?

[g6672D]

Please elaborate. It is a little hard to decide the problem without any symptoms.

[Flame Spawn]

Well it has to be something up with DB because in the error message title box it had builder.exe in it. I don't know what's up. =\

This is what it's been doing:
1) Sometimes when I try to save, the "Doom Builder has encountered a problem and needs to close" error message pops up for some random reason. I click "Don't Send".
2) After DB closes, I reopen it and open my WAD I've been working on. The whole map had been erased (the MAP01 didn't appear when I was in ZDoom (Doom in Hexen format), the cfg I chose for the WAD).
3) I'm forced to find a backup WAD file and redo all of the crap I did before.

Would pics help?

[Dutch Devil]

Got that error too sometimes its pretty annoying, but I make backups from my backups quite frequently.
So I can live with that if it chrashes so be it, atleast all my previous work did not get lost forever.
Don't know what could't be the reason for this maybe its windows XP that causes this dunno really.

[g6672D]

Well I'm running XP and it works fine. But I'm not running SP2 since I play DOS games.

If it seems to be XP spawning problems, try running Doom Builder in compatibility mode for Windows 98. Sometimes, it does fix issues with apps.

[Doom_Dude]

I was using 1.67 on win2k and it was crashing. It would also crash when going into 3D mode.... so I reverted to 1.66 and haven't had a problem since and that was a month ago. I think 1.67 has issues but wtf do I know. DB never crashed as much on me like 1.67 did.

[ace]

All's I can say is that DB 1.66 works without all of the new stuff, and 1.67 works without all the stability. Perhaps there shoudld be a 1.67.5: the best of both worlds!

Or that could just be v1.68 with better coding for stability and all the functionality and all that good stuff. :p


But yeh, this happens sometimes. Your best bet is to find version 1.66 somewhere. I use 1.67 and haven't had problems recently, so I don't have it now, but it can come in handy for stuff like that.

[hawkwind2]

Are you guys aware of this unofficial build ?

http://members.lycos.co.uk/doomguy0505/builderx/

Here for fixes ...

http://forum.zdoom.org/potato.php?t=7510

Works for me. :)

[Doom_Dude]

Nope didn't know about that. Personally I'm gonna stay safe with 1.66 for now and will keep it that way until my megawad is complete since 1.66 is working so well. It's nerve wracking when an editor eats your work, even if it's only a minutes worth. Hoohaa....

[ace]

It's nerve wracking when an editor eats your work, even if it's only a minutes worth. Hoohaa....

Indeed. Once I got a few minor things changed, then saved it (with DB I learn to save and save often :p) and it deleted the map. I had saved it before about 10 minutes earlier, so I wasn't really thinking when I yelled AAAACK and banged my head on the desk.

I've not tried that unofficial version... perhaps I'll look into it. Maybe the DECORATE editor has an error-checker so I don't need to find ZDoom crashing on me all the time because of something I did wrong... :p