|
|
Post by thundercunt on Nov 14, 2023 16:27:25 GMT -5
Not only your entire wad will vanish into oblivion, but all your UDB configurations and settings will disappear too.
|
|
SilverMiner
You're trying to say you like DOS better than me, right?
The code isn't free if one can't close it
Posts: 1,040
|
Post by SilverMiner on Nov 14, 2023 16:31:17 GMT -5
nice info, i use GZDB 1.14 (year 2013)
|
|
BIG DICK NIGGA
this post is a lie about my bodily proportions
Major Arlene obsessed, 100% verified freakazoid. AKA bzzrak
Posts: 2,296 
|
Post by BIG DICK NIGGA on Nov 14, 2023 18:18:51 GMT -5
Trololololol!
|
|
|
|
Post by noisomedead on Nov 14, 2023 19:55:43 GMT -5
for anyone this happens to, doombuilder creates backup files in the WAD directory, with .backup1, .backup2 etc appended to the filename, so you have a chance to save some of your work even if the main file is lost
|
|
|
|
Post by thundercunt on Nov 20, 2023 10:01:42 GMT -5
for anyone this happens to, doombuilder creates backup files in the WAD directory, with .backup1, .backup2 etc appended to the filename, so you have a chance to save some of your work even if the main file is lost Yeah, I suppose that this is better than nothing. But now I had a really scary thought. What if UDB partially corrupts your wad? You don't notice anything because the map you are editing looks fine. But when you try opening another map, oops, they are gone (and backups will be wasted if you save the corrupted wad 3 times) |
|
SilverMiner
You're trying to say you like DOS better than me, right?
The code isn't free if one can't close it
Posts: 1,040
|
Post by SilverMiner on Nov 20, 2023 10:12:17 GMT -5
I dunno if UDB corrupts something, but XWE 1.16 really did
|
|
|
|
Post by JadingTsunami on Nov 20, 2023 11:26:39 GMT -5
for anyone this happens to, doombuilder creates backup files in the WAD directory, with .backup1, .backup2 etc appended to the filename, so you have a chance to save some of your work even if the main file is lost Yeah, I suppose that this is better than nothing. But now I had a really scary thought. What if UDB partially corrupts your wad? You don't notice anything because the map you are editing looks fine. But when you try opening another map, oops, they are gone (and backups will be wasted if you save the corrupted wad 3 times) I keep my WADs in progress in version control to control for that exact eventuality. Then it's just a matter of committing and pushing the changes regularly. At that point you basically have a time machine and can rewind/fast forward to any point. |
|
|
|
Post by killerratte on Dec 7, 2023 16:13:26 GMT -5
I always work on maps in single wad files to both avoid long saving times and corruption issues. I compile the maps only after they are "finished". The worst I've seen so far happen in UDB is a map becoming completely unsaveable, it wasn't even far into the map. I built a small shape and some normal edges and suddenly nothing worked and UDB becomes uncloseable / it never stops saving and I had to force close it via task manager. This thankfully only happened once, but I suppose IF something like this happens it's best to just copy & paste linedefs over into a fresh file and try again.
|
|
|
|
Post by thundercunt on Dec 15, 2023 18:36:23 GMT -5
It seems they implemented some new feature for wad recovery
|
|
