Hi RMA Team,
We have a terrible terrible bug that makes working on shared files really hard.
Context: We all work from a synced-shared drive that’s part of Dropbox for Business. Each user and each computer would have a different looking path to this folder based on their Windows username and in which drive they have installed Dropbox, so if a program is using a referenced/linked file we need to have ways that the link is always accessible regarding of username/dropbox installation setup.
How have we solved that? using virtual drives. So in our case we sue a common agreed upon virtual drive letter “F:”, so it does not matter how in each user the path looks to get to:
in my case it could be:
or in George’s case might be:
For both of us, and anyone in our team it will unequivocally will always be F:\projects\test_project_folder
So when we are going to add an image file to a material we make sure we go through the F: drive path.
This works for anything we use like Indesign documents, Modo files, Illustrator smart objects, etc.
But there’s one program that is swapping, all by itself the path we give it for the actual physical path that each user/computer has. And this is just not ok. It breaks sharing files among the team.
We used to think that some of us were distracting and linking files from the incorrect physical path, until after watching it closely we realize it’s not us it’s Rhino!
Watch here how my file path from F:Drive becomes D:drive all by itself.
BTW, when a different person opens a file we do encounter this absolutely useless dialog box:
…and I say absolutely useless because none of the things that a user working in a production environment would possibly want to do upon seeing this dialog can be done (easily). It’s unbelievable how little real world thinking all your rendering/materials/image tools have in them. I’m sure it makes perfect sense when you have cube_test.3dm with one material, like the video I just made. When I opend this today I just wanted to pull the Scotch bottle out while I wipe off my tears.
…but it’s late here and I have more work to do, so quick bug report for now, and I’ll come back on more specific feedback about how to fix that dialog another day. For now please fix ASAP the fact that we get to see that dialog at all, because something that Rhino is doing wrong, not us.