Can't delete geometry, always comes back upon reopening the file ❓

[Robin.Walker]

Using vantage with corona, so exporting from max then using vantage stand alone, no live link.

Inside vantage I can delete geometry but it always comes back upon reopening the file

This is what i do:

• Delete a piece of geometry inside vantage (it warns me there is no undo)
• I see the geo is gone
• I save the file
• I close the file
• I open the file - the geometry is back

Is this normal behavior?

Alternatively, I could just re-export the model again from max, but I would like to keep all my cameras and environment setup in vantage. I thought open file as config did this but when I open a file as config it also brings in all the geometry from that file.

Thanks!

[Alexander.Atanasov]

Hi Yurgen99,

Does that happen to any type of geometry in any project or that just particular one? On my side deleted objects in Vantage upon reload of saved config file remain deleted. Can you send a sample scene so we can test it on our side?

Best regards,
Alexander

[Robin.Walker]

I did some further investigation:

• Any new scenes I export from max and corona do not suffer with this issue in vantage
• Regarding the problematic file I actually have a like 30 vantage files (i use different a file for each camera) and they all have this issue because they came from the original file I exported.
• This file I exported from max and corona was done some time ago before corona 12 release so it was beta. (it was a daily build).
• If I open a new blank vantage scene then 'open as config' one of the problematic files it still imports all the geo, where as any other scene I open as config only brings in the cameras and lighting.
• I also noticed that any additional geo I ‘import’ into the vantage file is deletable permanently. It's only all the original geo which cannot if that makes sense.

Somehow the geo is embedded in the root file and my vantage files are referencing it like an xref?

I have found a workaround for now, If I rename the original exported vantage file [the root file) to something else, it will no long be loadable and all geo is gone and I just see an error message. From here I can re-import new geo which is now deletable. This does of course effect all my files though.

Do you still want a file? Can send it on pm if you want as it’s work related.

Cheers (this is Robin btw from narrativ (we did some vantage corona videos last year), not sure how to change my username haha, made it years ago).

[Robin.Walker]

Some even further investigation: (in case anyone ever as the same issue)

If I open up any of the problematic files with notepad I am able see that the vantage file is pulling from a root file and also pulling all the geo from there, hence why it is never deletable and embedded into the file somehow.

From here I can edit the notepad and do a find and replace and simply remove the rootfile text (or just change its name to something random).

Save the file and then when you open up this vantage scene it will be unable to load in all the geo because it can't locate it, then you can reimport (using import in vantage) your new geo, which is now deletable.

I don't know the inner workings of how this happens in the first place but this solution works for a file by file bases rather than renaming the actuall root file which effects all files. Maybe this is something which happened in the beta versions of vantage, I'm not sure.

[npg]

The saved file also has a section called "deleted" listing the deleted objects. If loading this list failed for some reason there would be messages with text "Some changes will not be applied" in the debug log (help menu).

[Robin.Walker]

ah yes, I have these errors in my files, lots of warnings and a few erros of missing root files. However, this was due to my silly and most likely incorrect way of working back during the beta. It was a while ago now but I think I must have been deleting the actual root file each time I wanted to update the geo (due to the fact that I couldnt delete geo inside of vantage most likely). Then open the file, geo was missing as I intended and then I would import new geo.