Tweet
Hi guys,
Until now, I'm using Rhino 5 and the latest VfR 2.X release for daily work.
In order to possibly purchase the upgrade to VfR 3.6X and Rhino 6, I have installed Rhino 6 and VfR 3.60.02 (Trial) on a secondary computer to test workflow, compatibility and possible issues with my current and ongoing projects.
As I work on many parallel trade fair and retail store developments for a big company, it is very important to use existing files and libraries created with the RH5/VfR2.X combo.
While it basically works to open and render existing projects without big issues, I have a major difficulty with the handling of material conflicts when working with external block files:
In order to keep the main project files (e.g. a complete retail store) small, many shared elements such as furniture, product displays, products etc. are organized in an external parts library, which gives me the oportunity to update and refine parts from time to time.
So a typical project file can be only 30-100 mb, but contains maybe 150 external block models and hundreds of instances of them.
As I use the same standard materials both in the "master" file and many block instances, there is a material conflict when loading a project.
The previous way of loading models in VfR2.X was: a dialog window asked if I wanted to use, replace or rename an existing material.
Choosing "use existing material" and then once clicking "apply all" forced VfR to load everything automatically, not asking again and use all material settings as saved in the "master file".
This behaviour is my intended use. It gives the opportunity to fine tune materials of the same name in context of the whole scene, regardless their settings in the individual block files.
?n VfR 3.6 / RH6, the "apply all" option seems not to work that way - it doesn't have the effect to handle every material conflict automatically.
Instead, the material conflict window comes up again and again and I have to confirm the option for every single material in every external block that is already in the scene.
That means: every time I want to load a project (which I do 5 to 10 times a day), I have to manually click away hundreds of "material conflict" windows. Until after many minutes of clicking, the model finally is opened.
External linked models make no sense if it necessary to do over 100 interactions just to open a project;
Unfortunately, VfR 3.6 is in that form useless for me and I would have to stay with 2.X as long as possible.
Have I overlooked something, is there a workaround or the chance to fix this behaviour in the next release?
Kind regards,
Andreas
Comment