Same here. Happening on my PC and Laptop. (I tried verifying game files but that did not resolve it)
I believe it started happening with the 34.30 release.
Are you seeing a problem where you need to select modeling mode twice to get into it? The first time trying to switch modes there is a shift in the lighting and this log output:
LogFort: [DSCT_GI_Off_C_0] TODM Condition: GI_Off = false
LogFort: [DSCT_GI_Medium_C_0] TODM Condition: GI_Medium = false
LogFort: [DSCT_Erebus_C_0] TODM Condition: Erebus = false
LogFort: [DSCT_Mobile_C_0] TODM Condition: Mobile = false
LogFort: [DSCT_PerfMode_C_0] TODM Condition: PC_PerfMode = false
LogFort: [DSA_UEFN_Ch5S1_C_0] TODM Scalability: TODM Visibility = true
As for the actual crash, It’s always a memory error similar to
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff
Edit: New callstacks in v35:
Fatal error: [File:Z:\UEVFS\Root\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectHash.cpp] [Line: 63]
Unidentified failure for object GizmoComponentHitTarget /Engine/Transient.EdModeInteractiveToolsContext_2:EditorInteractiveGizmoManager_0.FreeRotationSubGizmo_1.GizmoComponentHitTarget_0, hash itself may be corrupted or buggy.
