,
I didn’t have to lock the camera in 4.12.5 which is my main point, if your solution had worked for me which it sort of did one time in one case, it is a worse work flow then 4.12.5, it is a step back not forward.
My shots are longer 90 seconds, they do not have a spawned in camera but a placed one, maybe it is putting the camera to a default location because the memory size of the physics data it is about to produce is beyond what is expected? Leaving it in the tiny window working with out having to click in the editor and lock the camera. Can you explain why it works in the small window with out doing these extra steps?
Here is a link to an old version of the shot I am working with it is 5 months old. This was created using a 580GTX, using 4.11-4.12.5 ocean plugin, etc. Now I am using 1080GTX and have added to the scene, and this scene still work exactly as it did in 4.12.5 with my current latest drivers. Regardless of the minor differences in our machine setup the key difference is that I am running 4.14.1.
My request is that you can get an engineer to explain why this change / bug happened since it still works the same as it did but in the small tiny window, and if they accept as an unintended circumstance of the all the code changes slammed into the build before Christmas break. If possible a timeline of when it will be fixed in a point release.