Fallout 76 crashing after latest patch

[takatori]

After the latest Fallout 76 update I started getting random crashes while playing with VorpX.
It’s stable when played vanilla, but crashes within 2-3 minutes using VorpX.

Any other reports? Or any hints wheat I should look at?

I’m using the default VorpX profile.
No difference between Geometry or Normals, or with head tracking enabled or not.

Windows Event viewer reports:
Faulting application name: vorpControl64.dat, version: 21.3.2.0, time stamp: 0x6203f721
Faulting module name: ntdll.dll, version: 10.0.19041.1466, time stamp: 0xe2f8ca76
Exception code: 0xc0000005
Fault offset: 0x0000000000063416
Faulting process ID: 0x5498
Faulting application start time: 0x01d82f2044764d37
Faulting application path: C:\Program Files (x86)\Animation Labs\vorpX\vorpControl64.dat
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 29ff171a-5a05-4aa5-afce-7449c1d2e660
Faulting package full name:
Faulting package-relative application ID:

[takatori]

Solution appears to be to disable AMD FidelityFX in the profile, and only enable once in-game???

I’ve replicated this now multiple times:

– Launch the game with AMD FidelityFX disabled in the profile: no crashes
– Enable AMD FidelityFX while in-game: no crashes
– Save AMD FidelityFX enabled to the profile, re-launch: random crashes
– Launch the game with AMD FidelityFX disabled in the profile: no crashes

This doesn’t make any sense to me …

[takatori]

I’ve confirmed this odd behaviour five additional times today:

3x: If the game is launched after saving AMD FidelityFX as Low, Medium, or Full in the VorpX profile, it will crash within 1-2 minutes of entering gameplay.

2x: If the game is launched after saving AMD FidelityFX as Off in the VorpX profile, it will run stably for as much as two hours even if AMD FidelityFX is set to Low, Medium or Full during gameplay and selecting “OK” instead of “OK+Save”.

I don’t understand how this could be, but it’s consistent.

[Ralf]

Finally got a chance to check this. As far as I can tell the game seems to work fine before running the DirectVR scanner. I’ll have to take a closer look to check whether that’s fixable by adjusting some scanner parameters or whether it’s something more serious. Possible that Bethesda ‘improved’ their anticheat measures and kick vorpX out when it applies memory scanner tracking.

For the time being please play without running the scanner. If the scanner issue is fixable, I’ll upload a profile with updated scanner settings and let you know here.

[takatori]

Thanks — and FYI, the FidelityFX pattern mentioned above is a false alarm: though the pattern held across more than a dozen tries at playing, the pattern failed today, so it was just random alignment with what I was trying, apparently.

Will try without the scan, thanks!

[Author]

Posts