I love so many of the changes happening at Enscape. Thanks for doing cool, innovative stuff. I think the cart might be getting before the horse on the solo license though. Having a license that can be logged into from any machine, anywhere is awesome. Truly, that would be an incredible asset IF enscape worked appropriately on the same project between machines. Until there is a good, solid and USER FRIENDLY way to see material links, linked assets, and ensure that files work across the board this plan doesn’t really make sense, and will probably lead to solo operations to feel the same frustration that users already working on a laptop and a desktop, or in a team feel. Unless everything happens on one machine, or users go through unrealistic, cumbersome processes every time they switch machines, none of the environments look entirely correct, or have all assets available. Would enscape/chaos please consider making muli machine use a higher priority before releasing multi machine licenses so that this feature is actually useful?
Why does nobody from Enscape ever address questions regarding making the platform easily usable (and consistent) on multiple machines? Is this something on the drawing board, and a future goal?
One could presume because it ventures into EULA territory where concurrent (single) license usage is frowned upon… like any other (software selling) vendor.
But until someone does…
I’m curious, what are you running up against exactly? I run the same models across multiple machines (not at the same time) with the same* results - w/ no dropped assets or material loss…? But then I work w/ Enscape fairly ootb (no custom assets for example)
I can’t help wonder/presume perhaps (?) it’s your infrastructure that might be lacking here? Do your machines work within the same environment? Do you maintain materials and (presumably custom) assets on a shared resource?
…or (and this where I potentially null the entirety of the above for not understanding the limitations of the solo license) is it that the license is machine-tied?
*hardware dependant
At one point in time I had an NAS at my studio (switched exclusively to cloud backup/group storage in probably 22) . This setup was feasible to get custom assets to follow as long as the NAS had the same device lettering and path as the other machines. It also worked only if I was in the studio (I understand that I could have made my NAS available outside of our local network, but that would have been problematic in other ways, like not having the material and custom assets saved locally for speed and reliability, which Dropbox allows). It would have been feasible to create multiple external drives (or internal drives) constantly clone them and sync them so that paths were always consistent, but I think it goes without saying how messy, time consuming, and potentially lossy/destructive that process would be. At the end of the day there is no “reasonable” infrastructure that can be implemented. Yes, there are options, but none that are good, or easily managed. Any other software that I use between multiple machines can sort this out (adobe, sketchup, etc) it’s just kind of chaotic at chaos in this regard.
I mean, sure, but that’s a broken thought process as well. The same kind of file sharing ability is necessary for firms that have multiple people touching the same file. For my particular use case, I pay for both a solo license and a floating license, so that when necessary, others on my small team can learn enscape for future use, use in projects, or have freelancers help out on projects and ensure that I am covered from a license perspective. It would be way harder (and expensive from a time perspective)to share my solo license and “crack” it in some way just to violate EULA and have “free” enscape running on other machines.