Whine whine whine whine cry cry cry cry.
edit: So the crazy "solution" from below was fixable by deleting a file that has nothing to do with the WAD itself at all.
To be clear, I worked around the problem I describe below (edit: twice), but I wasted so much time trying to do so that I'm right pissed about it.
So I had this problem and I pulled out as much hair as was cut the last time I was at a barber shop (it stopped up their vacuum). The good news is I found a workaround. The bad news is I don't see any hope of a fix, what with CodeImp's apparent hostility toward DB1 (haven't dared try to ask about it on the DB forums for hopefully obvious reasons).
Problem is exactly what it says on the tin: After saving a WAD in Doombuilder 2, Doombuilder 1 won't load from it or save to it.
See, I'm trying to make my first WAD for Vanilla Doom II (not counting the dozens of test maps where I played around with the editor). I've been using DB1 because I can work much faster using it than DB2. I'm most comfortable with using it for nearly every bit of mapping I could possibly need. But I really wanted to use the linedef curve plugin in DB2 to make a semicircular staircase, among small other things.
So I loaded my map up in DB2, saved it, ran it in ChocoRenderLimits, checked it out, and it seemed to work just fine for what I was testing (though visplane counts get scary sometimes, something I've been working on a lot lately)
Satisfied, I was going to continue editing in DB1 so I tried loading it up and lo and behold:
I wanted to punch someone. It would have been satisfying. I'm not learning DB2 and abandoning my favorite editor to do an entire WAD minus one-half of a level just because of something so stupid, and there's no way I'm abandoning a map that seems to be coming along this well (though having never made a serious map, I wouldn't know that 100% for sure).
Could not browse the WAD file contents in this file.
Error -2147221504: Invalid assignment. Forgot an assignment terminator?
Thinking it over, I'm wondered if loading the map in another editor and resaving could fix this, so I grabbed SLADE and, in my haste, got version 3 (edit: that is, an old beta), which does not have a map editor. Since it opened the WAD, I tried saving with it anyway, but no dice - DB1 won't open it. Since version 2 apparently *does* have a map editor though, I grabbed it as well and tried opening up my WAD. Not only does it open up, but it shows up just fine.
I decided to save the map with a different name as a precaution. What possible precaution? I have no idea, I just did it because I felt like it.
I try to open up this WAD under the new filename and it opens up just fine. I fly around in it a bit and then try to save over the bugged file (which I backed up, by the way) but once again, I get an error. *This time* it says it can't save because of the "Invalid assignment. Forgot an assignment terminator?" crap. Turns out, when I tried to save under the original name, the bugged WAD was present, so it tried to put the map inside the WAD instead.
However, I save in a new file without failure and I'm able to load from it in DB1 once again.
So something DB2 does when it saves a WAD is incompatible with DB1, and if you edit a DB1-made WAD with DB2 and save it, it breaks it for DB1, and you just might have to go through all of this mess.*
Most frustrating was finding google results for this problem with no solutions whatsoever, just abandoned threads. So I wrote this thing.
Ugh. -_- /noobrant
* And here is where I'm wrong, of course. It is a bit crazy to think that one vanilla WAD would be different from another vanilla WAD (and I don't know shit about WADs so I wouldn't know if other kinds of WADs are different from vanilla, etc. though I'd imagine they would be). Apparently I could have skipped all of this crap just by deleting/moving/renaming/etc. the DBS file created by DB2 because CodeImp decided to use a completely different DBS file format (from what I could see when I opened it up in Notepad++) in DB2 from DB1 (and why wouldn't he, seeing as he doesn't support DB1 anymore?). It's really kinda silly that an editor won't load a perfectly fine WAD just because it sees a config file that has nothing to do with it but is in a different format than it expects.
Last edited by Enzo03 on 02-12-13 at 20:46