Im still looking for the best way to deploy the latest version with customizations to the entire office. What is best practice? Prior to 2.6 I used to push settings, block notifications, etc. Since the change to a json file I havent been able to deploy with settings transparent to the end user. There hasnt been an update in the deployment help blog since converting to json.
Is this just not possible since the (2.6-2.8?) change?
@robs_1 , thanks for your inquiry. Just to make very sure that you’re aware these resources exist:
https://enscape3d.com/community/blog/knowledgebase/deploy-to-multiple-machines/
https://enscape3d.com/community/blog/knowledgebase/installer-program-options/
If you are already, can you briefly go into detail regarding which settings you refer to? Is it perhaps actually about the Enscape Settings themselves? For that, we recommend a network folder for example in which settings can simply be saved for everyone to access. Of course, they could also be distributed to local folders on the machines themselves. - alternatively, Settings can also be saved directly into projects as well.
Thanks for the helpful resource links @Demian_Gutberlet !
Expanding on the folder location further, as Enscape continues to expand the location of where settings and libraries are saved. perhaps it makes sense from the user-perspective to wrap all of those folder path settings into one portion of the Enscape settings tool. Right now, you would have to load several different parts of the Enscape UI to modify each of those separate folder paths (ie custom asset library folder, enscape material folder, camera presets, etc). Just a thought! Cheers,.
I appreciate the Feedback @Sh3ny8nG , I have gladly forwarded it accordingly through your voice. 