I’m running out of ideas.
I’ve started 5.1 (from source, build myself today).
Started vr example & enabled GPU light mass & tried to bake some lights.
Started vr
Stopped vr
Started vr
Stopped vr
started vr
Stopped vr
d3d error
Display freeze (music still plays)
Reset pc.
Reset was so hard windows though it got new updates started fresh configuration
Has any1 else had this problem? I want to simulate my home in vr, but every time I try to bake it or lumen it just explodes with crashes after few vr play/stop/play/stop increments
I’m on latest studio drivers
3090 gpu
I’ve tried on 2 pcs. Both have the same problem
I was wondering if I set up my scene incorrectly somehow.
I don’t know how they build vr example, but it does not use lightmass, so no idea how they baked lighting there.
Few times I saw some “error” code it fels like xr/sdk was doing some check on vr device after I left the game and causing that error. Will try to reproduce it, but its very painful as its hard pc reset each time :- (
If it happens on two different PCs, then it’s more likely it’s a library or engine bug.
Try enabling the D3D debug layer and API verification, and see if it catches someting.
Hey @Neumiller@jwatte
Finally had time to test it.
Surprisingly whatever that flag is helped the massive crash. Now I just get empty window crash but pc survives! So this is a lot better ^^ I know its still bad. But one step closer.
Also 5.1 official + build from source seems to be a little more stable too.
Crash loogs are a bit hmm tricky, one of them seem to have some interesting info tho >
[2022.11.16-16.49.38:916][422]LogSlate: Slate User Unregistered. User Index 8
[2022.11.16-16.49.38:916][422]LogSlate: Slate User Destroyed. User Index 8, Is Virtual User: 1
[2022.11.16-16.49.38:917][422]LogUObjectHash: Compacting FUObjectHashTables data took 0.38ms
[2022.11.16-16.49.38:997][423]LogPlayLevel: Display: Destroying online subsystem :Context_2
[2022.11.16-16.49.39:020][423]LogD3D12RHI: Warning: ID3D12Device::CreateGraphicsPipelineState: The depth stencil unit or pixel shader expects a Depth Stencil View, but the PSO indicates that none will be bound. This is OK, as reads of an unbound Depth Stencil View are defined to return 0; and writes are discarded. It is also possible the developer knows the data will not be used anyway. This is only a problem if the developer actually intended to bind a Depth Stencil View here.
[2022.11.16-16.49.39:020][423]LogD3D12RHI: Warning: ID3D12Device::CreateGraphicsPipelineState: The depth stencil unit or pixel shader expects a Depth Stencil View, but the PSO indicates that none will be bound. This is OK, as reads of an unbound Depth Stencil View are defined to return 0; and writes are discarded. It is also possible the developer knows the data will not be used anyway. This is only a problem if the developer actually intended to bind a Depth Stencil View here.
[2022.11.16-16.49.39:020][423]LogD3D12RHI: Error: ID3D12Resource2::<final-release>: CORRUPTION: An ID3D12Resource object (0x00000222B4E22450:'D3D12Chronometer::D3d12QueryBuffer') is referenced by GPU operations in-flight on Command Queue (0x0000022200820850:'3D Queue (GPU 0)'). It is not safe to final-release objects that may have GPU operations pending. This can result in application instability.
[2022.11.16-16.49.47:373][423]LogWindows: Could not start crash report client using ../../../Engine/Binaries/Win64/CrashReportClientEditor-Win64-Debug.exe
[2022.11.16-16.49.47:373][423]LogMemory: Platform Memory Stats for WindowsEditor
[2022.11.16-16.49.47:373][423]LogMemory: Process Physical Memory: 2500.36 MB used, 2513.20 MB peak
[2022.11.16-16.49.47:373][423]LogMemory: Process Virtual Memory: 4609.02 MB used, 4779.83 MB peak
[2022.11.16-16.49.47:373][423]LogMemory: Physical Memory: 38290.34 MB used, 26368.85 MB free, 64659.19 MB total
[2022.11.16-16.49.47:373][423]LogMemory: Virtual Memory: 107472.94 MB used, 18230.53 MB free, 125703.47 MB total
[2022.11.16-16.49.47:373][423]Message dialog closed, result: Ok, title: The UE-PolandHome_102 Editor has crashed and will close, text: Fatal error!
[2022.11.16-16.49.47:373][423]LogWindows: Error: === Critical error: ===
[2022.11.16-16.49.47:373][423]LogWindows: Error:
[2022.11.16-16.49.47:373][423]LogWindows: Error: Fatal error!
[2022.11.16-16.49.47:373][423]LogWindows: Error:
[2022.11.16-16.49.47:373][423]LogWindows: Error: Unhandled Exception: 0x0000087d
[2022.11.16-16.49.47:373][423]LogWindows: Error:
[2022.11.16-16.49.47:373][423]LogWindows: Error: [Callstack] 0x00007ffb56efcd29 KERNELBASE.dll!UnknownFunction []
[2022.11.16-16.49.47:373][423]LogWindows: Error: [Callstack] 0x0000009766574ec0 UnknownFunction []
[2022.11.16-16.49.47:373][423]LogWindows: Error: [Callstack] 0x0000009766575fc0 UnknownFunction []
[2022.11.16-16.49.47:373][423]LogWindows: Error: [Callstack] 0x000000000000087d UnknownFunction []
[2022.11.16-16.49.47:373][423]LogWindows: Error:
