Stuck on Ladder in Delta Reactor Room

[jyudoki]

Just encountered a game stopping bug in Delta Reactor Room (the one with lost souls). At first I had trouble walking up the initial set of stairs without jumping, with my character getting stuck. Next, when I try to go up the ladder to the next level, I get stuck and cannot proceed no matter what.

I've looked this up and found that it's a random bug that happens with both vanilla and BFG edition. Here's a video of it from someone else:

https://www.youtube.com/watch?v=zrsW5taL88c

Could this be isolated and fixed perhaps? Attached my affected quicksave:

QuickSave.zip

Edit: It appears perhaps on level load all the ladders and stairs are loaded wrong so that it makes traversal difficult/impossible until the level is reloaded.

[HarrievG]

I encountered this same bug too.,
Not sure it is an engine bug since you show that it even happens on the console port and original released bins.
That being said, the loading part about the ladders is interesting. Did you debug this yourself? if you can point to what is in your opinion the offending code, i can take a look. Or if you deduced this from logging, sharing those would also be appreciated.

Edit:
Actually, after seeing the whole vid you linked, I am not so sure if this is NOT an engine problem. the load thing is starting to sound very plausible.

@DanielGibson I will chase this and update here.

[HarrievG]

tests to perform:

• Load from supplied save game.
  so far unable to reproduce from save game in 32bit win debug and release

• normal load from start of map

• DevLoad from start of map,

[HarrievG]

ladder_load_relase32.txt
Attaching an save game load which is made from the quicksave above, and saved infront of the first ladder encountered

Lots of warnings. Not sure if there are really bad ones.

Made with
"+set fs_basepath \"E:\\SteamLibrary\\steamapps\\common\\Doom 3\"", "+set fs_devpath ", "+set r_fullscreen 0", "+set com_allowConsole 1", "+set developer 1"

[HarrievG]

I have done some searching, and it appears that the ladder bug is common, but only in this level.
It also seems to be persistent from saves, but i cannot reproduce it with the supplied one.

Would love to get my hands on a save game that persistently reproduces this.
For now, i dont think this should hold back the next release.

[DanielGibson]

Did you also test with release binaries?
Maybe the bug doesn't happen with (unoptimized) debug binaries..
If it indeed only happens in release mode, you could try CMake's RelWithDebInfo release type

[HarrievG]

Yes , I tried 32 bit release and debug.
Could you give a try at reproducing it? Then at least we can be sure the save game is unfortunately not the golden egg we are looking for..

[HarrievG]

Is it also maybe possible for us to try to reproduce it on his exact same build? Can we extract that that info from save game?

[DanielGibson]

I don't think that this is stored in the savegame.
But maybe @jyudoki can tell us which build was used, and if the bug is reproducable when loading the savegame, or only happened when originally playing the map and saving.

I'll try to remember to reproduce it, I think I've tried before unsuccessfully, but I don't even remember if I only tried on Linux or also on Windows.
(My vacation is over so I don't have as much time for dhewm3 this week)

[jyudoki]

I was using the latest public build. When loading the save game it will always be bugged. However when loading the level from scratch it will be fine. That’s why I suspect the issue is due to the level loading improperly at the very start. Also this seems like a long standing bug on multiple platforms including Xbox and BFG so I’m pretty sure it’s not linked to any specific build. Thanks for taking the time to look into it. Cheers Justin Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Daniel Gibson <notifications@github.com> Sent: Wednesday, January 20, 2021 11:52:02 AM To: dhewm/dhewm3 <dhewm3@noreply.github.com> Cc: jyudoki <justin.yu84@outlook.com>; Mention <mention@noreply.github.com> Subject: Re: [dhewm/dhewm3] Stuck on Ladder in Delta Reactor Room (#328) I don't think that this is stored in the savegame. But maybe @jyudoki<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjyudoki&data=04%7C01%7C%7C292ded87f1814157c31408d8bcdd99e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637467007239968569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WT%2FAQVHJWOy0FJuJfL9sbObc%2F6uDWCP3MWmLgM0SL7I%3D&reserved=0> can tell us which build was used, and if the bug is reproducable when loading the savegame, or only happened when originally playing the map and saving. I'll try to remember to reproduce it, I think I've tried before unsuccessfully, but I don't even remember if I only tried on Linux or also on Windows. (My vacation is over so I don't have as much time for dhewm3 this week) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdhewm%2Fdhewm3%2Fissues%2F328%23issuecomment-763248034&data=04%7C01%7C%7C292ded87f1814157c31408d8bcdd99e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637467007239978523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=j30h%2FqG9lBPsRUa%2F9qM1xC3%2BFGBrkGQoToAae0yBgAg%3D&reserved=0>, or unsubscribe<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARW6FSVCPKV5QJYYLFS27DLS2YSLFANCNFSM4TV4QYTQ&data=04%7C01%7C%7C292ded87f1814157c31408d8bcdd99e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637467007239978523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=q%2F5hxIdYXEwU5VtNTlaKkfs3hcHYl2qeYmbhlqOO0Vk%3D&reserved=0>.

[DanielGibson]

I was using the latest public build.

In November the latest public build was 1.5.1 RC2, unless Justin meant the latest proper release (not pre-release) which was 1.5.0 (or used some semi-public build I linked somewhere in a bugreport to test specific fixes).

[HarrievG]

Ok, I will try again with the released builds!

I hope I am able repro it.
@jyudoki if you are still encountering it, could you also attach one of your logs here while you have "com_developer 1" set?

-H.

[turol]

I have never actually played Doom3 that far but it appears that the save is very far from any ladders. This makes reproducing and testing under Valgrind hard. Can you make another save which is directly in front of a ladder?

[HarrievG]

Yes, its a bit far, you have to progress the level a bit.

1. You follow the path to the reactor room where you interact with the monitor
2. you backtrack, and a hole in the ground opens up. Enter that hole and exit on the other side of the floor
3. follow the path and you will see a dead guy sitting/leaning on a crate/battery (or something) pick that up.
4. backtrack again to the reactor room and walk to same spot you interacted with monitor, the object will be taken from your inventory and the reactor will start
5. backtrack once more, and this time a monsters appear from that same hole. ( turn on god mode, so you don't die and can just walk past it/kill easily )
6. enter hole and exit on other side again, a new path is opened here.
7. after taking this new path and doing some fights, a ladder will present it self shortly.

Its pretty linear, and you cant really stray from the designed path.
I also haven't finished doom3, but played only the demo content before picking up DHEWM3 for my hobby project.. and now play specific levels just to see/feel how the original developers pulled off different things.
I have to say, that this is a very, very nice part to play. if you haven't played it, it worth doing so anyway ;)

I have not tried no-clipping immediately to an ladder, although I think it should be a feasible test run, it is always dangerous to use this type of cheat since you can easily miss trigger volumes that trigger need logic for progression

so yes these are a lot of steps.... and if you (@jyudoki) could make the save game again in front of the first ladder, that would be great. !

Oh, and the output with com_developer 1 might be helpful even if we cant reproduce with your savegame,

[turol]

That's no good... I suspect this is caused by uninitialized memory. Valgrind can easily find these but the problem is that it slows down the game by about 10-50 times. Those steps are completely infeasible under Valgrind.