Relative path creation bug?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi, I'm an IT admin trying to help a colleage with a Max issue, hopefully someone on here can help!
We're re-organising our file storage, and to help make projects portable between different staff we want to use relative paths in asset manager, however Max seems to be creating very inneficient paths which won't work across devices.
We have our .max file in a project folder, and then for example 'models' folder within the same folder containing model files. I would expect the relative path to generate simply 'models/filename' but instead we get '../../../../../all the way back to the drive root/subfolder/subfolder/subfolder/models/file'. If we manually edit the path in Max it respects the correct path and finds the assetts, however this will take a long time! Is it possible that we've missed something in the config and we can correct this behaviour?