Doom Builder Won't do Anything Correctly

Well, I have no clue what is going on, but once I do get Doom Builder to start, it basically goes into "spaz" mode, and can't do anything that involves texturing, loading, or saving anything correctly. Just going through these ought to give you an idea of what's happening:

http://www.questwizard.net/files/dbwtf/dbwtf-01.png
http://www.questwizard.net/files/dbwtf/dbwtf-02.png
http://www.questwizard.net/files/dbwtf/dbwtf-03.png
That's a LOT of screwed up palettes and bad or missing texture issues. Happens in the 2D or 3D modes.

http://www.questwizard.net/files/dbwtf/dbwtf-04.png
http://www.questwizard.net/files/dbwtf/dbwtf-05.png
Yeah, it can't even load MAP01 without spewing hundreds of errors, let alone correctly. This is the error log: http://www.questwizard.net/files/dbwtf/dbwtf.txt

http://www.questwizard.net/files/dbwtf/dbwtf-06.png
http://www.questwizard.net/files/dbwtf/dbwtf-07.png
Trying to load the first map I made into Doom Builder, and it appears to hate it more than anything in the world. This is the WAD (NOTE: Its for Skulltag): http://www.questwizard.net/files/dbwtf/CavedIn.wad
If you try playing it, it works perfectly fine, without error, so its got to be DB messing up somewhere.

http://www.questwizard.net/files/dbwtf/dbwtf-08.png
http://www.questwizard.net/files/dbwtf/dbwtf-09.png
Its got no problem other than massive texture problems in both 2d and 3d when I start a new map up. It appears to work correctly with drawing out sectors and placing things and all.

http://www.questwizard.net/files/dbwtf/dbwtf-10.png
http://www.questwizard.net/files/dbwtf/dbwtf-11.png
http://www.questwizard.net/files/dbwtf/dbwtf-12.png
http://www.questwizard.net/files/dbwtf/dbwtf-13.png
http://www.questwizard.net/files/dbwtf/dbwtf-14.png
If I want to go into 3d mode after I make a new map, it fails miserably, and it doesn't matter how many different nodebuilders and different versions of them I use, it crashes them all.

http://www.questwizard.net/files/dbwtf/dbwtf-15.png
http://www.questwizard.net/files/dbwtf/dbwtf-16.png
Saving is seriously borked, and the nodes won't build no matter what I do.

http://www.questwizard.net/files/dbwtf/dbwtf-17.png
http://www.questwizard.net/files/dbwtf/dbwtf-18.png
Tried to load it up again, and it blows up in my face with an overflow error. Loading other maps either does this, loads a seriously corrupted version of it even though there's no problems with the WADs, as they play just fine, or it just crashes DB to the error report screen.

Somehow I think its a character encoding issue that's causing it, because it seems to be loading and saving values that are completely corrupted, because the one time I did get it to go into 3D mode on something, it was a big ugly pile of infinitely-stretching polygons with screwed textures and missing polygons all over the place. Went back out, and after that, it wouldn't let me back into 3D mode. It just crapped out at the nodebuilding process again and again.

Does Doom Builder not like double-byte character sets or something, because my system locale is set to Japanese, and if I switch it back over to US English, my keyboard layout screws up entirely (its a Japanese keyboard), and acts like its the US English layout, and a lot of other programs (especially Windows Explorer) show nothing but ?????????? or boxes in place of any non-ASCII characters, so a locale switch is NOT an option here. However, if I do that, Doom Builder works perfectly, without screwing up anything. Got any ideas on how I could fix it without having to do a locale switch, hack it, or go buy VB6 and fix it myself?

WOW RELAX!!!! Do you think anyone will bother to solve ALL of that shit for you.

Weird I just downgrabbed your map and it shows up fine in doombuilder for me, nice looking rock map btw.

I've never encountered these problems before with my version of doombuilder(1.68), I asmume you use the latest version of db.

This inverted/polarized/recolored texture thing is common, not just for doom builder, but for many such programs with certain things similar to Doom Builder. It's a problem of the images using a different palette than every sensible thing. Just ignore it, you're fine.
If it really bothers you, try messing with the graphics settings on your OS, or in Doom Builder.

Oh, and the white textures are ones that didn't load from the WAD, Just reload the WAD and you'll be ok...

I have the EXACT same problem, and I am using a Taiwanese computer. Now, to start off, I never had any problems with Doom Builder, on any PC i've installed it on. However, I am visiting family in Taiwan right now. I experience the exact same problem you do, on a Taiwanese PC. I even suspected that it might have something to do with the locale, but I wasn't sure. After reading your thread, it seems that this is most likely the problem.

EDIT:
Nevermind, I finally was able to change the system locale after blindly navigating through menus in a foreign language. Anyways, Doom Builder works perfectly now. It seems like that is exactly why Doom Builder didn't work before for you or me, it needs to be changed to an english system locale.

I see the first screenshot shows the hideous CTF textures I made that somehow found their way into Skull Tag. Ignore, there is nothing to see here.

Crotalus said:

I have the EXACT same problem, and I am using a Taiwanese computer. Now, to start off, I never had any problems with Doom Builder, on any PC i've installed it on. However, I am visiting family in Taiwan right now. I experience the exact same problem you do, on a Taiwanese PC. I even suspected that it might have something to do with the locale, but I wasn't sure. After reading your thread, it seems that this is most likely the problem.

EDIT:
Nevermind, I finally was able to change the system locale after blindly navigating through menus in a foreign language. Anyways, Doom Builder works perfectly now. It seems like that is exactly why Doom Builder didn't work before for you or me, it needs to be changed to an english system locale.

Yeah. This definitely confirms it.. I don't see why it should have any problems with it anyway, seeing as the basic ASCII stuff is pretty much identical in all three of the character sets we've got it in right now.

There's only two differences in shift_jis (the one I'm on), which is the backslash becoming a yen sign and a tilde becoming a horizontal bar on top instead of the bottom of the character. Big5 (the one I'm guessing you're on) doesn't have any differences in the first 128 characters that i know of. Then again, even if there were, its only a difference in the fonts, and not the actual encoding anyway, so this kind of stuff shouldn't be happening regardless of the character set, as long as there aren't very major differences, and if double-byte characters are not used in the strings. Solution would probably be to make DB a Unicode app, but have it save data in plain ASCII (conversion there should be incredibly simple if I've got this all down right. seems like you'd just have to search for the 00 bytes in strings and delete them), since that'll make those first 128 characters exactly the same, and make system locale settings completely irrelevant, so a non-English locale would no longer cause errors. Hopefully this'll be fixed sometimes soon, because I don't want to have to deal with ????? and boxes everywhere and/or a funny keyboard layout that doesn7t match the keyboard.