Now another project is down/corrupt (a camera is suddenly not working out of no where)
with the premise of 1) and 3), I am suspicious towards engine changes … was the down time [cf 2) ] related to an update, and is this update then ‘bulletproof’?
If so, I hope you can help me with a double check of the engine-update
There wasn’t any engine nor Editor/backend release today. Point 2 is just some issue on the backend we had, but I’m not sure about 1 and 2. Definitely not release related though.
Thanks - it means a lot to me, that this structure/organization is a listening one.
On the other hand, the corruption I am experiencing relates very much to cameras+layers [dis+enabling] and special shaders [of which are depending on first app load (loading script orders), and or post-initialize code etc].
As all the mentioned above, seem to have the potential of making a project fragile, I hope that the engine+editor combination will be more stable in the future.
At the moment I am currently moving assets into a third new project within two days :-/
@mvaligursky Should be able to help more if you can share a project with the current setup
With 1. That shouldn’t have happened and if you can describe more of the issue with corrupted assets, it would be something we would like a look at. This is the first report I’ve heard with assets being corrupted.
ok, sounds really proactive … also nice with in depth info relating to 1.38.0
At this specific moment, I am balancing things in my hand … adjusting the two corrupt projects, versus pursuing a new - and quite more-optimal - solution in the third (?)
where the sea should keep on being reflective as in the After the flood demo.
Don’t have time to share 2nd corrupt project, but in essence it seemed very Editor related/oriented, as a camera suddenly didn’t work (black screen) after being disabled, for then to be put back on (went through every little detail, so it seems like a ‘more tough’ bug … apropos 1.38.0).