So the ideal scenario would be able to mix of absolute and relative paths, per each referenced file. If i’m understanding the workflow.
Yes, in our case, we only need local ones.
+1 I’m surprised that it isn’t handled by Windows itself.
I wanted to chime in here that the most preferred behavior would be to prioritize relative paths, and it seems like it prioritizes absolute paths. This means that if I distribute a .rws file to users on a shared local server to which they all have access, and then they copy both the .3dm files and the .rws files to their local disc, the .rws file will always load the shared local server .3dm files, not the local disc files. I have to instead distribute a Rhino Script to tediously regenerate the .rws files to their local paths via command line prompts, which is somewhat slow and not ideal for less technical users not accustomed to running scripts.
I should note that this might seem like a counterintuitive use case, since for collaborative purposes you might actually want all the files to remain on the shared local server, and utilize the locking mechanism to manage users. But in our use cases, we’re also using Worksessions to split projects into manageable file chunks, and .rws files to help reassemble various different subsets of files for specific use cases.
1 Like
That is how I use Worksession as a single user, not a member of a group/team.
1 Like