---

Fisk said:
@Janitor: Agreed. I've toyed with an "early" version of Builder64, and I must say, I am very pleased. You guys will love this program once it hits the net.

---

---

hardcore_gamer said:


oh really0_o

Whats so great about it other then then the fact that it can create Doom 64 levels like the old Doom Builder could for the Doom 64 TC?

---

---

hardcore_gamer said:


oh really0_o

Whats so great about it other then then the fact that it can create Doom 64 levels like the old Doom Builder could for the Doom 64 TC?

---

---

esselfortium said:

All the Doom 64 features are accessible from it just as easily as you can change a sector's floor height or light level in Doom Builder. No gross hacks or magic tag numbers or whatever.

---

---

Kaiser said:


Because the TC is awful. End of story.

---

---

hardcore_gamer said:
LOL sounds great! But why create a "new" Doom Builder instead of just creating a new configuration.file for the old Doom Builder?

---

---

skadoomer said:

Take a closer look at that doom builder screen shot. Notice anything different, like a color section in that sector properties window? Doom 64's engine supports wall coloring independent of a sector, so the floor can be blue, the ceiling can be red, and the wall can be set to fade two colors or be a solid green if you wanted. Heck the players color doesn't even have to change because the lit color of objects is set independently as well. No doom engine supports this yet (not even doomsday) because the doom 64 levels use a different map format than pc doom.
Hence, a configuration file wouldn't do the trick because it cannot support these things.

---

---

Kaiser said:
Because the TC is awful. End of story.

---

---

Fisk said:
Also, I discovered what was wrong with the test WADs. If you guys want to fix it yourself:

1) Open doom64.wad with a lump editor of your choice.
2) Extract the entry MAP01 as a .wad.
3) Open MAP01.wad.
4) Save MACROS.lmp.
5) Use glbsp with -normal on one of the test WADs. For example, "glbsp.exe -normal test_deathtrigger.wad -o test_deathtrigger.wad".
6) Inject MACROS.lmp as the last lump in the WAD you built.
7) Enjoy.

Ergo, Doom64.exe will crash when it doesn't find a MACROS lump with the map it tries to load, and there are no GL nodes for some of those WADs. ...Although, the GLBSP.exe for Builder64 could be different than the regular GLBSP. I dunno.

---

---

hardcore_gamer said:


Oh yea, i failed to notice that before!

But what about the sector color it self? If the wall is blue, the ceiling is green and the floor is red, then of what color would the glow be? For example, when the player walks into a sector that has green lighting, then the players view and gun becomes a little green, but if the walls and the floor and the ceiling all have there own color then what color would affect the players view when he enters the sector? I failed to see any option in the screenshot that mention this.

---

---

Gez said:
I suppose the player is affected by the Thing Color.

So suppose you have orange ceiling, green upper wall blend, purple lower wall blend, pink floor, and blue thing. When the player arrives there, his gun takes on a blueish tint even if the walls and flats around do not look blue at all.

---

---

Kaiser said:
The only downside to D64 editing is that it takes more time to complete a level than to complete a standard Doom level because of the way lighting is set up, it takes more time to properly light up a room.

---

---

skadoomer said:

Take a closer look at that doom builder screen shot. Notice anything different, like a color section in that sector properties window? Doom 64's engine supports wall coloring independent of a sector, so the floor can be blue, the ceiling can be red, and the wall can be set to fade two colors or be a solid green if you wanted. No doom engine supports this yet (not even doomsday) because the doom 64 levels use a different map format than pc doom.

---

---

Bashe said:
I did notice that the mouse sensitivity doesn't go high enough for my needs, but that was easily remedied by changing it manually in the config. It did produce an amusing graphic in the menu though, as the slider was off of the track. :D

---

---

DoomKn1ght said:
Fantastic , way better than the tc.

BTW, have you keep .md2 support from Doom3D, even if this format fail?

---

---

Kaiser said:
Btw, post your CPU specs please.

---

---

Patrick Pineda said:


# Intel Pentium M Processor 740 (1.73GHz/2MB Cache/400MHz FSB*)
# 15.4-inch WXGA display
# 1024MB of RAM (2 stick configuration)
# Intel integrated Media Accelerator 900 graphics card
# 60GB Hard Drive (5400RPM)
# Microsoft Windows XP Home
# Dell 1470 Internal Wireless 802.11a/b/g

---