Stuck at Chapter 3 Manual Override

[Nagumo]

Hi there,

i'm stuck in the main engine room at which you are able (or should be) to manually start the engine (or some important part of the process ^^).
I killed all enemys and put the battery into its slot. Then the path is going to a control station at which the ingame PC Screen is telling me that i have to wait....BUT....nothing happens.

I see that the "machine" above my head is not going smoothly but what can i do?

Really annoying, because nothing is pointing at anything beside the ingame PC scree, which is doing nothing at all.

What am i missing? Or is this maybe a lost trigger???

[GrittySmitty762]

Originally posted by Nagumo:

Hi there,

i'm stuck in the main engine room at which you are able (or should be) to manually start the engine (or some important part of the process ^^).
I killed all enemys and put the battery into its slot. Then the path is going to a control station at which the ingame PC Screen is telling me that i have to wait....BUT....nothing happens.

I see that the "machine" above my head is not going smoothly but what can i do?

Really annoying, because nothing is pointing at anything beside the ingame PC scree, which is doing nothing at all.

What am i missing? Or is this maybe a lost trigger???

Im having the same issue. Funny thing is the first time it spawned enemies. They killed me and i reloaded. Now no enemies have spawned and its stuck. You find a fix?

[GrittySmitty762]

So after you insert the battery in that room its suppose to spawn a large amount of enemies you need to fight to progress the engine repair. They are tied to it. I had to keep reloading my save from right outside the room to trigger them. I think if you spend too much time in there before inserting the battery it breaks the spawn for the enemies.

[Nagumo]

Yeah, a reload solved it for me, too. Sidenote: I'm playing on PS5 so this bug seems to be occur on PC and Consoles.

[Drake Ravenwolf]

Try the 1.04 patch and let me know if its working for you now

[Dehexed]

This happened to me today, so it's still not fixed.

[Korhal]

The remake is a little "finnicky" sometimes. There is another instance, where you have to put in a security card, yet the game might not be accept your input - the fix is "stomping". :D

[CrazyDoctor]

I got stuck in the same area with the same problem. Multiple reloads didn't fix the problem, but going in, killing the necromorphs, and going straight to putting the battery/powerpack in WITHOUT SEARCHING THE ROOM FIRST finally triggered the second necromorph onslaught. I think it penalizes you for searching the room first.

[paulatreides]

Same issue in the middle of august 2024 here.

[Evil Roy Slade]

Same issue .all enemies dead engine room panel stuck in pre-ignition phase

[jules_schmules]

September 15 2024, same issue. Seems like the people that claim the room punishes you for looting/exploring before installing the battery pack are correct. At least, installing the battery pack as fast as possible worked for me. Grab the explosive barrel(s) from the hallway before the save room, open the door to the engine room, trigger aggro, and kinesis throw the explosive into the necros. You should be able to get 3 at a time if you're patient. Then, kinesis the spear limbs off the dead necros, and kill the last necro that births the mini-spawns. Take the spawns out quickly with some pulse rifle or flame thrower blasts, then continue all the way to the back of the room, go right up the ramp, and kinesis the battery down to the power hub.

After 3 or 4 failed attempts of my game getting stuck prompting me to go to the control terminal, but not actually being able to do anything, I tried the above strategy. Immediately after inserting the battery into the hub, spooky music played, and enemies spawned a few seconds later. Took out the newly-spawned enemies and was able to proceed to the terminal which worked.

[Stellar]

Same problem, walking around for 10 minutes wondering what to do. You would think they would fix this bug already.

[ΩLNTΩ Sinys]

end of march 2025, and this bug still isnt fixed?