---

DaniJ said:
PWADs like Phobos: Anomaly Reborn can also be loaded in beta4 but due to most of the BOOM support not having been implemented yet - it isn't really playable.

---

---

ultdoomer said:
Finally, how does Alt Mouse Handling affect control?

---

---

Grazza said:
It seems that if -complevel 7 is used when attempting to play back a Doom2.exe-format demo, the behaviour is to some extent random.

---

---

entryway said:
Does It works better than the default handler? Much better for me.

---

---

myk said:
On the other hand, GLBoom is fast but has visual glitches, like stacking skies, and apparently some HOMs in a newer version of PrBoom+... no idea where those came from.

---

---

Belial said:
...

Funny, when we wanted to play PrBoom multiplayer we've found all we needed in the docs.

Use -iwad for the client. You don't specify the IWAD on the server.

---

---

RazTK said:
Fix the problem when you save the game while you are playing in net game, because you get an error if you try to load it later.

---

---

entryway said:
How can I reproduce it?

prboom_server.exe -c glboom.cfg -N 2 -s 4 -l 1 // default_compatibility_level 2
glboom -net localhost -nofullscreen
glboom -net localhost -nofullscreen

Saving and loading work correctly for me

---

---

Grazza said:
An error I've got a couple of times when using saves

---

---

Grazza said:
Have you tried adjusting the OpenGL settings in glboom.cfg? (Some information here - this is included in the prboom package as boom.cfg.html)

---

---

As for the new HOM issue, perhaps this is related to the fix for the MBF special skies, or for the glitches in MM map29 and map30 (I don't know why it would, but those are things that have changed recently). You can turn the latter off by setting test_sky1 and test_sky2 to 0 in the cfg.

---

---

RazTK said:
This is the exact error I get when I'm trying to load a network save game.

---

---

myk said:
this glitch occurs in Map01, as shown here

---

---

entryway said:
From which version you have seen it the first time?

---

---

Grazza said:
An issue with your card perhaps?

---

---

Regarding translucency, this isn't just with GL. Boom itself made fireballs (and other stuff) translucent. See BOOMDEH.TXT.

---

---

myk said:
Perhaps. I'm pretty sure that if I redo the nodes it'll disappear.

---

---

myk said:
But in GLBoom the translucency setting is ignored (at least on my computer)

---

---

ultdoomer said:
Whenever I play a demo in that port, you don't see anything until about three seconds because it starts "drawing" your movements before it enters graphics mode.

---

---

Grazza said:
I don't find this at all.

---

---

Grazza said:
try changing level_precache in the cfg to 1.

---

---

Grazza said:
What's your processor/graphics card?

---

---

Grazza said:
One thing you could check: are you using -complevel -1, and is it finding a doom2.gwa file? That could lead to problems if the gwa file is of low quality. (Don't know if it could lead to this problem, but it would mean it was using different nodes from the normal ones.)

---

---

ultdoomer said:
I don't know if I worded that well, so let me ask you this so I know you understand: Do you first see the graphics when Andrey opens the first door of E1M1 (about 2 seconds in) in his e1uv-404.lmp demo?

---

---

ultdoomer said:
Processor: Intel Pentium 4 CPU 2.80Ghz
Graphics card: RADEON X300

---

---

ultdoomer said:
I was wondering if you could do something about glBoom's level starts. Whenever I play a demo in that port, I don't see anything until about three seconds because it starts "drawing" the movements before it enters graphics mode.

---

---

Grazza said:
After all, in Boom you can make any thing translucent via a bex/deh, but for this stuff you can't even turn it off in that way - it's all or nothing.

---

---

Grazza said:
I've looked into this a bit more. I still can't see how to disable this in Boom, but I've found a way to do it in Prboom-plus

---

---

myk said:
And it's not that the translucency bit is a toggle (on and off depending on whether the sprite was translucent in the first place.)

---

• Boom made 17 of the things translucent by default.
  
• In Boom, the translucency bit makes things translucent. For the 17 things that are translucent by default, there is no way to make them non-translucent (apart from disabling translucency altogether).
  
• In PrBoom, the translucency bit makes things non-translucent. For the things that are not translucent by default, there is no way to make them translucent.