Build Type:
Binary
Build Version:
Version: 4.14.1-3224400+++UE4+Release-4.14
Issue Description:
This VR Blueprints project (no C++) was originally in 4.13 but when 4.14 was released we ported over to that (we just opened a copy rather than migrating everything over manually). Until this bug happens there is usually zero issues with the engine and the project. End of November-beginning of December we encountered a bug (didn’t know it at the time) where anytime we were in our Player Pawn BP that after compiling the BP about four or five times the engine would crash and spit out an Access Violation error similar to the one that is attached to this report. Rather than thinking it was a bug, we assumed it was due to us just opening a copy of the 4.13 project in 4.14 rather than migrate everything over by hand as we normally do. Because of that we just rebuilt the player pawn BP and everything was fine again until today.
I didn’t make any drastic changes to the player BP and after using any version of the Play button (VR Preview, normal Play, etc.) if I make any changes and attempt to compile the player pawn BP the engine instantly crashes spitting out an Access Violation error. The one thing I do notice happen afterwards is that SteamVR ends up reporting a 108 error. This only happens in the player pawn BP though which is why I’m not really suspecting this is a Steam VR issue but not sure.
Repro Steps:
There isn’t really a way to reproduce this. I’m going to try and get a sample project together to share but without that there is nothing specially causing this that I do other than Play the game in editor and then attempt to compile a Player Pawn BP right after.
Attachments:
-
SteamVR System Report // Link: SteamVR_SystemReport.txt
-
Crash Diagnostic Files // Link: Crash_Diagnostic_Files.zip
-
Crash Reporter Summary // Link: Crash_Reporter_Summary.txt