ZDoom 2.0.98 Bugfixing bugfix release

Post by **randi** » Mon Nov 07, 2005 11:35 pm

Have you tried co-op recently? Those bugs should have been fixed in 2.0.97. If it still doesn't work, what exactly doesn't work?

Belial · Post by **Belial** » Mon Nov 07, 2005 11:42 pm

ATM the most important coop bug is http://forum.zdoom.org/potato.php?t=7251.

Post by **Bio Hazard** » Mon Nov 07, 2005 11:53 pm

So the "You lose your inventory when you die" bug got fixed? is that what this changelog entry was for?:

randy wrote:Removed the multiplayer check from AInventory::ShouldRespawn(). Now the dmflag is always respected, even without alwaysapplydmflags.

Post by **Graf Zahl** » Tue Nov 08, 2005 3:14 am

randy wrote:
Graf Zahl wrote:Are there plans for a stable floating point release before rewriting the actor handling completely?
Not at this time. The new scripting was actually one of the prime reasons for the switch to floating point. (I didn't want to subject the people who might use it to floating point math.) By itself, floating point doesn't add any real value. I just want to get a nice solid fixed point version out, hence the 97 and 98 releases (which were not as solid as I would have liked). Then I can concentrate on new features again.

I'm asking because from experience the most bugs have been found through public testing. I really think it's a good idea to release one or two versions for testing purposes before something that massive is added to the code. I'm quite sure many users here are willing to help with that.

The Ultimate DooMer · Tue Nov 08, 2005 10:40 am

Graf Zahl wrote:If that is a concern I can add a 'locked' software mode that doesn't recreate the nodes but also doesn't allow switching to GL mode when inside a level.

That would be quite a good feature actually, since that would make a full merger between 96x and GZDoom possible without any chance of anything OpenGL-related harming wads created for 96x, or those containing features that don't like OpenGL.

(yes I've had a lot of trouble off OpenGL, graphics cards, drivers etc. in the past, and it's only thanks to a PC blowout early last year that I don't have that trouble anymore. Plus I don't like OpenGL's handling of fog and doors with partially-transparent middle textures)

Grubber · Post by **Grubber** » Tue Nov 08, 2005 12:26 pm

I agree, that would be really useful.

Hirogen2 · Post by **Hirogen2** » Wed Nov 09, 2005 7:58 am

Close it. Please.

clarence144 · Post by **clarence144** » Wed Nov 09, 2005 8:55 pm

Will .97 demos still work in this new version?

deathz0r · Post by **deathz0r** » Thu Nov 10, 2005 2:14 am

Graf Zahl wrote:Is there really any need to do this separately?

Yes. GZDoom forces my display settings to 320x200 software mode upon startup, which really gets on my nerves.

Post by **Graf Zahl** » Thu Nov 10, 2005 2:34 am

Can you post the startup log you get with '+logfile log'? If started in software mode there is absolutely nothing different from ZDoom starting up.

Doomguy0505 · Post by **Doomguy0505** » Thu Nov 10, 2005 3:50 am

@deathz0r: http://autoexec.ytmnd.com/

wildweasel · Post by **wildweasel** » Thu Nov 10, 2005 3:51 am

Edit your INI file to the resolution settings you want, then mark it read-only.

deathz0r · Post by **deathz0r** » Thu Nov 10, 2005 3:49 pm

Graf Zahl wrote:Can you post the startup log you get with '+logfile log'? If started in software mode there is absolutely nothing different from ZDoom starting up.

Oddly enough, it doesn't appear to be doing it anymore. It must have done something when I first loaded it though, since I've only used 0.9.14 once before reporting that quirk.

Regardless, here's the log:

Code: Select all

Log started: Fri Nov 11 08:45:04 2005

 adding gzdoom.wad (146 lumps)
 adding zvox.wad (32 lumps)
CPU Speed: 1673.774653 MHz
CPU Vendor ID: AuthenticAMD
  Name: AMD Athlon(tm) XP 2000+
  Family 6 (7), Model 8, Stepping 1
  Features: MMX MMX+ SSE 3DNow! 3DNow!+
I_InitSound: Initializing FMOD
  Setting DirectSound output succeeded
  Setting driver 0 succeeded
  Initialization succeeded
R_OPENGL: Couldn't create render context. Reverting to software mode...
Resolution: 640 x 400
Switching to software renderer...
Init DOOM refresh subsystem.
2665 textures created
Init miscellaneous info.
Init Playloop state.
Setting up sound.
S_Init
Checking network game status.
player 1 of 1 (1 nodes)

Doomguy0505 wrote:@deathz0r: http://autoexec.ytmnd.com/

You're seriously a retard. Shut the hell up and go do something useful or contributive... I don't know, such as leaving the forums for a start?

Post by **Graf Zahl** » Thu Nov 10, 2005 3:58 pm

deathz0r wrote: Regardless, here's the log:

Code: Select all

Log started: Fri Nov 11 08:45:04 2005

 adding gzdoom.wad (146 lumps)
 adding zvox.wad (32 lumps)
CPU Speed: 1673.774653 MHz
CPU Vendor ID: AuthenticAMD
  Name: AMD Athlon(tm) XP 2000+
  Family 6 (7), Model 8, Stepping 1
  Features: MMX MMX+ SSE 3DNow! 3DNow!+
I_InitSound: Initializing FMOD
  Setting DirectSound output succeeded
  Setting driver 0 succeeded
  Initialization succeeded
R_OPENGL: Couldn't create render context. Reverting to software mode...
Resolution: 640 x 400
Switching to software renderer...
Init DOOM refresh subsystem.
2665 textures created
Init miscellaneous info.
Init Playloop state.
Setting up sound.
S_Init
Checking network game status.
player 1 of 1 (1 nodes)

That error is truly odd. It sets up the graphics hardware properly and fails at a point that doesn't make any sense at all.

deathz0r · Post by **deathz0r** » Thu Nov 10, 2005 4:07 pm

Graf Zahl wrote:That error is truly odd. It sets up the graphics hardware properly and fails at a point that doesn't make any sense at all.

99% sure it's a vexing bug. This video card (S3 Savage ProDDR) does not support OpenGL 1.2 at all. It either forces programs to switch to software mode, or it renders everything as white.