RoboCop: Rogue City

RoboCop: Rogue City

View Stats:
kayem Oct 7, 2023 @ 1:53am
Crash after intro cutscene
RTX 4070 Ti, Ryzen 5600, 32 GB RAM

Game is crashing after the intro cutscene. Thats all.

Thanks for convincing me to not buy this crap, good job.
< >
Showing 1-10 of 10 comments
yefy Nov 4, 2023 @ 12:44pm 
Same here. 1st run after full game installed today > black screen after intro cutscene, then crash.

RTX4070 FE, i5-12600K, 16 GB RAM.

I'm using the latest game optimised Nvidia driver (express-installed via GFE, but after several crashes, I did a clean reinstall using DDU cleaner, and did not touch any settings in NCP.)

My final fix

Deactivate Nvidia Frame Generation (I only use DLSS Performance mode, for now)

I did not try this before a clean driver reinstall, so above solution might have worked in any case.

However, after not crashing, I reactivated frame gen without crashing in-game (I then tried running the intro cutscene again, and it did crash, so frame gen is causing some issue atm.)

Next step: I intend to activate frame gen again after the intro, and then see if the crash is only related to the intro cutscene.
Last edited by yefy; Nov 4, 2023 @ 12:51pm
yefy Nov 4, 2023 @ 4:55pm 
Originally posted by yefy:
Same here. 1st run after full game installed today > black screen after intro cutscene, then crash.

RTX4070 FE, i5-12600K, 16 GB RAM.

My final fix

Deactivate Nvidia Frame Generation (I only use DLSS Performance mode, for now)
Update

The game finally did not crash with frame gen activated (deactivating frame gen seemingly works for many people to avoid the initial LowLevelFatalError).

So, I started the game as usual with previous settings from last crash after intro cutscene. I then changed Performance to DLAA. I quit the game and started it again. Shaders needed to preload again = crazy stuttering during start-up logos + menu, for a while. When the stuttering stopped, I changed back to Performance, and no crash after the intro cutscene...hopefully stays that way 🤷‍♂️

Might not work for all...
darkjairo29 Nov 4, 2023 @ 7:19pm 
I spoke to support and they told me that they are aware and will review both the issue of the game closing without warning after a black screen, and the UE5 fatal engine error, according to the colleague above who says that UE5 is known for these bugs , I will tell you that so far no game I have tried with UE5 has crashed this way so often, an urgent patch is needed.
FlyingAllNight Nov 5, 2023 @ 8:26pm 
Stuck on this too. Tried continuing my save and can't. Guess im waiting for a patch
yefy Nov 6, 2023 @ 6:15am 
Originally posted by darkjairo29:
I spoke to support and they told me that they are aware and will review both the issue of the game closing without warning after a black screen, and the UE5 fatal engine error, according to the colleague above who says that UE5 is known for these bugs , I will tell you that so far no game I have tried with UE5 has crashed this way so often, an urgent patch is needed.
Black screen > "UE5 fatal engine error" = LowLevelFatalError...I assume is the same error?

My earlier Update fix only worked for the intro cutscene. The game crashed again later with black screen after having scanned some power cables inside the 1st level in the building's lower (basement?) level... 😓

I might play without DLSS frame gen, until a patch has fixed the bug...👾
Originally posted by yefy:
My earlier Update fix only worked for the intro cutscene. The game crashed again later with black screen after having scanned some power cables inside the 1st level in the building's lower (basement?) level... 😓

I might play without DLSS frame gen, until a patch has fixed the bug...👾
It's a wrong implementation of Nvidia Streamline SDK into Unreal Engine 5 and it cannot be fixed by reinstalling drivers or any magic (only fix is to disable upscalers and use TAA), because soon or later the game will crash drivers again.
The game forces GPU driver to crash and closes with LowLevelFatalError.
Avoid to use DLSS and FG for now.
https://steamcommunity.com/app/1681430/discussions/1/3940146862830699161/
You can safely use TAA with any other settings.
But any upscaler usage will crash GPU drivers soon or later.
yefy Nov 29, 2023 @ 2:30pm 
So, not even fixed with latest Patch 3 (Nov 27)?

I played with TAA, very stable but only good for 1440p on High setting for ~60 fps (barely) with a RTX 4070 FE...

EDIT: Reflections on Medium will mostly keep a stable ~60 fps, but looks so much better on *High*.
Last edited by yefy; Nov 29, 2023 @ 2:33pm
my game crashed after the cut scene (there was a black screen, then the game closed without error). I lowered the graphics settings (from medium to low) and I finally got the game loaded. my pc: i5-8400, gtx 1650, 8gb ram, hdd
Phil Jul 14, 2024 @ 3:44am 
Had the problem with this game and Ghost of Tsushima. The problem was the BIOS and its CPU voltage settings, a current problem modern CPUs and boards have (the limits are too high) with games using the Unreal 5 engine. As the game goes 100% on your system the first time you start it as it wants to compile shaders this might lead to your CPU crashing either the game or the whole PC.

So it might be worth a try to look up your motherboard vendor and CPU and see if there are some BIOS settings which might fix that. Helped me at least. You can also use a start parameter to start the game without shader compilation (might lead to lag during the game though as they are then compiled on demand instead of beforehand). With Tsushima it also helped to start the game in windowed mode to reduce the load on the GPU but it did not help with this game.
Last edited by Phil; Jul 14, 2024 @ 3:44am
< >
Showing 1-10 of 10 comments
Per page: 1530 50

Date Posted: Oct 7, 2023 @ 1:53am
Posts: 10