Re: Game consistently crashing during same cutscene, cannot progress
@FeralGoblin4ever Similar issue with me, it's always during the same part, don't want to spoil you so I'll just say...the hallway scene after walking through the train near the beginning.
It's always at the same moment in the scene, causes a complete crash to desktop, event viewer/reliability monitor aren't giving me anything; and I've done all of the same troubleshooting steps as you, give or take.
I looked through some of your info in your dxdiag report, we don't even have similar machines generation-wise; although they're both high-specced and users with higher-end PCs seem to be having the most issues as far as crashing goes.
Here's the last block of warnings I get in my IGO_Log in ProgramData before it forcefully restarts my PC. I would add my dxdiag as well but I don't believe I can attach files in a reply to a thread.
INFO 08:45:15 AM (0) 12192 mhook.cpp: 192 mhooks: BlockAlloc: Allocated block at 00000000222B0000 as 282 trampolines
INFO 08:45:15 AM (0) 12192 DXGIHook.cpp: 868 DXGIHook::Setup(force long wait: 0)
INFO 08:45:15 AM 🏀 12192 DXGIHook.cpp: 868 DXGIHook::Setup(force long wait: 0)
WARN 08:45:15 AM (17) 3120 IGOApplication.cpp: 224 IGOApplication created 5
INFO 08:45:15 AM (0) 12236 InputHook.cpp: 3050 InputHook::TryHook
WARN 08:45:15 AM (0) 12236 InputHook.cpp: 3095 input hooks: no DirectInput found.
INFO 08:45:15 AM (0) 12236 InputHook.cpp: 3110 input hooks: w 1 x 1 d 0
INFO 08:45:15 AM (15) 3120 IGOApplication.cpp: 715 IGOApplication mWindowed = 1
INFO 08:45:15 AM (0) 3120 IGOApplication.cpp: 716 IGOApplication window screens size (new) = 1920x1080
INFO 08:45:15 AM (0) 3120 IGOApplication.cpp: 717 IGOApplication window screens size (set) = 0x0
INFO 08:45:15 AM (0) 3120 IGOApplication.cpp: 721 IGOApplication window screens scaling = 1000000 1000000
INFO 08:45:15 AM (0) 3120 IGOApplication.cpp: 661 IGOApplication screens size not used (new 1920x1080 old 0x0, ready = 0)
It's always at the same moment in the scene, causes a complete crash to desktop, event viewer/reliability monitor aren't giving me anything; and I've done all of the same troubleshooting steps as you, give or take.
I looked through some of your info in your dxdiag report, we don't even have similar machines generation-wise; although they're both high-specced and users with higher-end PCs seem to be having the most issues as far as crashing goes.
Here's the last block of warnings I get in my IGO_Log in ProgramData before it forcefully restarts my PC. I would add my dxdiag as well but I don't believe I can attach files in a reply to a thread.
INFO 08:45:15 AM (0) 12192 mhook.cpp: 192 mhooks: BlockAlloc: Allocated block at 00000000222B0000 as 282 trampolines
INFO 08:45:15 AM (0) 12192 DXGIHook.cpp: 868 DXGIHook::Setup(force long wait: 0)
INFO 08:45:15 AM 🏀 12192 DXGIHook.cpp: 868 DXGIHook::Setup(force long wait: 0)
WARN 08:45:15 AM (17) 3120 IGOApplication.cpp: 224 IGOApplication created 5
INFO 08:45:15 AM (0) 12236 InputHook.cpp: 3050 InputHook::TryHook
WARN 08:45:15 AM (0) 12236 InputHook.cpp: 3095 input hooks: no DirectInput found.
INFO 08:45:15 AM (0) 12236 InputHook.cpp: 3110 input hooks: w 1 x 1 d 0
INFO 08:45:15 AM (15) 3120 IGOApplication.cpp: 715 IGOApplication mWindowed = 1
INFO 08:45:15 AM (0) 3120 IGOApplication.cpp: 716 IGOApplication window screens size (new) = 1920x1080
INFO 08:45:15 AM (0) 3120 IGOApplication.cpp: 717 IGOApplication window screens size (set) = 0x0
INFO 08:45:15 AM (0) 3120 IGOApplication.cpp: 721 IGOApplication window screens scaling = 1000000 1000000
INFO 08:45:15 AM (0) 3120 IGOApplication.cpp: 661 IGOApplication screens size not used (new 1920x1080 old 0x0, ready = 0)
