Unusual setting/bug affecting object Transforms

[mhedinger]

Hi,

I opened a saved scene in VRED 2020.1 today and all the objects in the scene appear in different locations and/or with different orientations than they had when I saved the file. I have since tried to open some of the incremental save backups, but weirdly they also have the same issue.

This makes me suspect that the problem is a bug or a setting I am unaware of, rather than an issue with the file itself.

What is interesting is that when I navigate into my cameras and activate some of the saved view points, the camera seems to locate itself correctly so the transformations seem to only apply to geometry nodes - camera and light nodes seem to have stayed intact.

If this was a simple scene, I would just rearrange everything. But this is a huge scene and many of the renderings were already made. So if I now were to try and recreate the scene, I am sure that some things would not match up or that small position & lighting changes would be visible when mixing new frames with previously rendered ones for animations. It is also a macro scene with a physical camera, so even the slightest changes will be noticeable.

If anyone has experienced this before, or if you have any suggestions as to which setting might have caused this to happen, please let me know. I cannot explain to myself how this could possibly happen on every version of this scene, even ones that have been left untouched as backup files.

I've attached the last successful rendering, along with a screenshot of how the same arrangement is being represented by VRED since all of this has started.

Please Help! Thank you!

Edit: I have just noticed that some of the objects in that scene have had their transform values completely reset to 0, whereas others just have some of the transform values changed, while retaining others. In case this helps in figuring out the issue.

[Christian_Garimberti]

Hi, is it possible that your scene was created in 2020.2?

[mhedinger]

Hi, thank you for getting back to me.

The scene was originally created in 2020 first release, on my workstation at home. The computer I am currently working on is 2020.1. My machine at home has since been updated to 2020.2.

Opening the file on my computer at home after updating to 2020.2 was the last known instance where the scene appeared correctly.

I have worked with this scene for the last month or so, on 2 different computers, and across all VRED 2020 versions: 2020, 2020.1, and 2020.2 - this is the first time anything like this happens.

That being said, I can neither confirm, nor deny, that this is the first/only time the file was last saved in 2020.2 and then opened in 2020.1 - I am hoping that this is the problem, bringing it from 2020.2 back into 2020.1 but I won't know until I get home.

Even so, this seems to have affected incremental saves of this scene that have never been opened/saved in 2020.2. Yet they behave in the same, strange way.

[Christian_Garimberti · Accepted solution]

I hope for You that is is your case... The solution will be easy ...
Note then there is not backward compatibility from 2020.2.
In this case specially for the new reference behavior.
I tried and I get the same your problem. Every imported model moved and rotated.
Best
Chris

[marcus_fritzen]

Hi,

what Chris wrote is correct. If you have saved your scene in 2020.2, it is possible that it will loose transformations when it is opened in 2020.1 again. This happens e.g. when the file reference node itself has a transformation. I could explain the details behind this behavior but it wouldn't help you.

In general, there is no guarantee that scenes saved with a specific VRED version will work in prior versions! However, the file should work fine in the version with which it was saved.

Regarding the incremental saved files, those should be unaffected if they are not saved with 2020.2.

Cheers,

Marcus

[mhedinger]

Thanks Chris and Marcus. It has indeed worked fine again once I opened it in 2020.2.

Thank you for your help.