Actually after more testing I see that I was wrong. I realized I had rotated my controllers before the backup and I didn’t think that would be a problem. Apparently rotating anything in the player BP causes the fatal error. If anyone has a fix for this please let me know as I’m afraid to touch the Player BP in case I lose my work. Cannot find another thread about this error and I don’t see anything in the 4.14 documentation that addresses it.
I accidentally rotated the camera instead of a Controller inside my VRPawn BP (player). This caused the player to be frozen to the floor and I even though I undid the camera rotation I am still stuck. Even creating a new pawn does not fix the issue. I have recreated this error.
Create two pawns, one is the player pawn and one a vehicle to walk around in. Parent the player to the vehicle. Adjust the rotation of the camera and the player will be stuck. I have a custom game mode, player controller and camera manager set up. I went ahead and added a camera to the player itself and instead of using a player start, I placed the pawn in the level and told the level blueprint to possess at start. That should be all that needs to happen to reproduce the error.
If this happens in a project, I have to scrap that file and hope I have a backup as I have yet to find a solution. I have tried removing the camera manager and that did not help.
This is interesting. I recreated the project and copied all code into the new one. It was working. I next copied the file and backed it up on a separate drive. Went back into engine which was still open and the error came back. So now I apparently cannot save my game without the error? At this point the ue4 engine is completely useless to create a vehicle game as I now cannot save a backup without causing the error. I know that this was all I did to create the issue and now all files are corrupt.
More testing shows that if the player camera manager is removed then rotating the camera or the controllers will not cause this. However, I have found that if the parent has the mesh set as the BP root (for enabling physics) then the player is locked again. I do not have a collision set up on the parent. Also the issue doesn’t occur till I reload the game. This accounts for the earlier post where I was wondering why my backup was corrupt. There was no issue initially till I reloaded.
I was unable to reproduce this issue with the steps provided. I have a few questions for you that will help narrow down what issue it is that you are experiencing.
- When reproducing this issue did you do so in a clean project with no previous assets?
- If so, could you provide a more detailed list of steps to reproduce this issue on our end?
- Could you provide screen shots of any blueprints/settings that may be involved?
- What VR device are you using when this error occurs?
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.