'can't delete some objects' issue when I delete and replace geometry

Vantage Issues
1

I understand that there is an issue where objects with the same name can’t be deleted. However, this issue seems to arise with geometry that’s been deleted and then replaced. Can Vantage actually delete from an imported vrscene? Let me explain…

We have a large scene created in 3ds Max. We export as a vrscene and it imports into Vantage. We decide to change a few things so we delete that geometry in Vantage (there is a warning that this is permanent) and we export just the amended geometry from 3ds Max and import this into Vantage. This seems to work perfectly. We carry on with the project etc. But if we open that scene at a later date that geometry that we deleted has re appeared (bright pink with no textures) and it can’t be selected or deleted. At this point we have 100s of cameras set up with scene states and there seems to be nothing we can do to purge all the unwanted geometry. The scene is ruined. ‘Open as config’ can’t help save our cameras and scene states because it just imports in all the geometry we don’t want.

I’m wondering, Does Vantage actually delete geometry from a vrscene? It appears to as I’m working on the scene but maybe it can’t edit vrscenes? This would explain why there is geometry with the same name when opened at a later date. I’m trying to understand how it works but I am confused why some of my Vantage files are literally KBs in size but then some are 500mb in size (despite them having the same vrscene geometry loaded). I assumed geometry was getting embedded into the scene but now I’m thinking that’s not the case (because of the ‘ghosted’ geometry that can’t be deleted.

A separate issue but maybe related to amending and replacing vrscenes… We also have problems with camera groups. I usually have to import groups of cameras from Max to Vantage as I’m working though projects. But I end up running into problems where I select a group of cameras to render but it will either not recognise that group or it will render a different group. Sometimes after I reopen a scene then there may be groups of cameras that have duplicated and renamed with ‘02’ on the end and sometimes seemingly random cameras have jumped to different groups. I’ve been working with Vantage a couple of years now and these issues seem inconsistent and I’m not sure what causes the problems with the cameras groups. Although it generally appears if I have to change and reimport cameras.

Thanks​

2

The .vantage file does not contain geometry or materials, etc. It only references one or more vrscene (or other format) files as sources for scene contents. It then adds modifications to those files. “Deleted” geometries simply get unloaded. I’m not sure how you managed to grow the file to 500mb because I think the only larger piece of information there is the thumbnail image for each saved camera but this is mere kilobytes, so you’d need something like over a thousand cameras.

If you have a (preferably simple) scene that can be used to reproduce the camera group issues, please send it in a support ticket: https://support.chaos.com/hc/en-us/requests/new

3

Thank you. So I suppose after we have ‘deleted’ any unwanted geometry from Vantage, we have to rename the amended geometry in 3dsMax before we export it and the undeletable geometry issue shouldn’t occur.

FYI regarding the file size, (which isn’t really a problem, just confusing) we do have a lot of cameras. Maybe 300-400. However, I have a Vantage file with around 250 cameras and it’s only 708 kilobytes. This happens to be the Vantage scene I have had to recreate because of the unwanted geometry in the initial Vantage scene which is 418mb. So these scenes are basically identical. They have the same vrscene loaded in to them and they have pretty much the same amount of cameras (the initial scene has roughly an extra 60 cameras in along with scene states save to each camera which is basically the sun rotation).

Our scenes are quite heavy but I’ll try and recreate the camera group issue and send it over. Appreciate you looking into it thanks.