Hi devs. I already posted similar bugreport for Embergen but that bug was not so severe.
In our studio all artists use network storage for projects files (UNC path \nas\projects). If we open liquigen project from \nas location then imported fbx meshes transform their paths to strange relative path format like “..\..\..\..\..\..nas\projects”. This leads to failed import because of broken path.
Obviously the same liquigen project being opened from local drive location works fine, but it’s nearly impossible to work in this manner by constantly moving files between local and network drives.
Please consider either a correct support of UNC paths or at least make automatic-relative-path conversion optional so we could disable this unwanted behavior in Preferences.
Technically \nas\projects is not a UNC path. It would have to be \\nas\projects (starting with two backslashes.) Was this a typo and you meant the latter?
Have you disabled “Relative Asset Paths” in “Settings → Preferences”? (see image below)
Does typing out the UNC path manually work? (make sure to use two backslashes)
Hi.
Path root is \\nas ofc. Forum formatter trimmed it.
Yes, project file is on the network drive.
And thanks a lot for the setting, that’s exactly what I needed. I didn’t check if it was already implemented, my bad.
No worries. I still think it should’ve worked with that option selected. I’m curious, if you re-enable relative paths, and try typing in the path manually, does it work?
Yep, that’s a UNC path edge case in Liquigen. with **Relative Asset Paths** enabled, it tries to normalize paths on load and ends up mangling `\\nas\share` when reopening the project. The classic serialize/deserialize mismatch occurs when saving is successful and reloading is interrupted.
workarounds for now:
* deactivate **Relative Asset Paths** for UNC locations * or map a drive letter to the NAS
It’s merely path processing that doesn’t yet completely respect UNC roots, not a user error.
