We are considering “variations” support in Vantage, yes. It will be native, no need to code it using App SDK.
If you can explain more about your end goal, i.e. how you would like to combine these different sets, it might help us design the system so it fits your needs.
Virtual aircraft walk-through with customers on the Desktop:
- Trigger per button an animation or a switch that opens lavatory doors, turn down seats, open overhead stowage compartments to show the interior.
- Show different seat models, which also switch dependent models of the seats (class separators etc.)
- Switch or animate (back and forth switch) between different light-sets (color and intensity of interior lights, exterior sun and sky)
Design review:
- switch between different model variants (hatrack contours, etc.) inside a scene
- switch between different materials on the models
- switch between different light-sets
Because of the heavy data we have, we organize in 3dsmax a whole cabin with different xrefscenes for seats, sidewalls, ceiling, lavatories and so on.
Because of that, a change in the scene in 3dsmax would require to open the xrefscene and update it in 3dsmax.
We organize everything with layers (geometrical variants and light properties for different light-setups), that are then configured using scene-states in 3DSMax, since we have to switch multiple things at the same time.
A system like scene states support together with layer structure support would probably beneficial in Vantage.
Priority one would be geometric switches (layer visibility), second would be light properties. third material properties.
This is something planned, yes, but not sure when it will happen.
Can’t you use the live link for now and have everything stored in the 3dsMax scene ?
Because of our organization with xref-scenes and xref-object-materials, I didn’t try that yet, since the update in 3dsmax is a bit time consuming in that case, if we do not want to merge the scene.
If we implement the deduplication above, this would also break the material assignments, even if you don’t reexport the .vrscene.
This applied only to .vantage files created without this deduplication present.
What if you don’t break deduplication, but filter the material properties to just show the unique materials? Or, not sure, but couldn’t you keep the specific object properties at the objects and not in the materials? Probably not possible because of the mesh and material compilation and optimization of the vrscene-format or because of the speed of raytracing? Maybe another solution would be to have a toggle to ignore the per object properties completely during export, since they might be used only for offline-rendering and compositing, but not necessary for real time rendering? And sometimes we even forgot that we have these settings still set.