[Not a bug] Timer() is reset to zero on each hub in Hexen

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Timer() is reset to zero on each hub in Hexen

Postby theleo_ua » Mon Sep 06, 2021 5:27 am

GZDoom 4.6.1 (OpenGL 3.3 version) x64 / Win7

Steps:

1) run hexen
2) start map02
3) use noclip cheat and go to "exit hub" portal, but do not enter it
4) check total game time (for example by savegame or by automap widget)
5) enter the portal and proceed to next hub
6) check total game time (for example by savegame or by automap widget)

Actual result: time in step 6 is zero (0:00:00)
Expected result: time in step 6 should be sum of step 4 and step 5 time (something like 0:00:15), as in vanilla

NOTE: in previous versions of gzdoom it worked as expected (step 6 was sum of step 4 and step 5)
NOTE 2: if I want to use scripts which detects start of the game with condition like "if timer() == 0", then those scripts worked correctly in previous versions of gzdoom (script executed only after ESC / new game), but works incorrectly in 4.6.1 (script executed on each hub)
User avatar
theleo_ua
 
Joined: 07 Feb 2016

Re: Timer() is reset to zero on each hub in Hexen

Postby Blue Shadow » Tue Sep 07, 2021 8:16 am

If we're talking about hubs, Timer() returns hub time, not total game time, so it's normal the value it returns resets to zero when leaving one hub for another.

I don't know what version of GZDoom it worked as you're expecting. I happen to have GZDoom 1.8.2. I did a test, and it worked like I described above; as in, the value returned by the function reset to zero when I left Seven Portals for Shadow Wood in Hexen.
User avatar
Blue Shadow
 
Joined: 14 Nov 2010
Operating System: Windows 10/8.1/8/201x 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: ATI/AMD (Modern GZDoom)


Return to Closed Bugs

Who is online

Users browsing this forum: No registered users and 0 guests