With the floating license we use Enscape allot between multiple users and then ultimately in a conference room. We often tweak the settings file to get the look that we want but then need to constantly copy the .xml files back and fourth between the various machines. Having the ability to add a networked pathway would be ideal so that the settings could more easily be updated across multiple machines.
Define Additional Pathways for Use of Shared .XML Settings Files
- bhaslow
- Thread is marked as Resolved.
-
Great idea
-
Thank you for your feedback! This is already on our agenda and got your upvote.
-
-
Per project would be great. Even better would be per view so we could reliably rerender each view with its corresponding settings (field of view, depth of field, exposure, ...).
-
In project would be just as good though we have a few stylized settings that we like to use on multiple projects.
If it's per project, I'm hoping we can save the settings in our Revit templates.
-
Can we have the Enscape settings save with a file an not become the default on that machine for all projects? I noticed that when I move from my workstation to our VR workstation, it doesn't remember by settings for that project, it seems to remember the settings from the last user on that machine, regardless whether those settings were adjusted in Revit or SketchUp. I think it makes more sense that those settings stay with the file and that a new project could have some preset defaults.
-
-
I think this has been suggested before, but it would be great to have shared settings profiles or select the .XML file on a network location.
Our current workflow involves either sending the .xml file via computers or taking screenshots of the setting profiles and sharing that.
Thanks!
-
jstevenson Got your upvote!
-
+1 vote from me, either option would work