(Embergen) UNC network path export

Hello devs.

Embergen v1.2.2 can’t transform $(projectdir) tag to correct folder if opened project is located on network drive (For example “\\nas\projects_temp_\test_project.ember”). When I hit Export it pretends to export something but there are no actual files after that.

If I specify the output path manually by entering “\\nas\projects_temp_\vdb” then export doesn’t work at all and displays an error.


Also it creates “nas” folder on drive C :slight_smile:

If I use mapped drive letter “I:_temp_” then export works fine, but unfortunately we can’t use mapped drive in production.

Can you please confirm this bug on your side?

Hi Nik, you want to work locally when using EmberGen. This means all imported meshes and exported assets should be done locally before being moved to a network drive. Let me know if you have any questions about this!

Hi. Thanks for the answer but tbh it’s not very helpful.
Embergen has not only Indie but also Studio pricing. Studios usually have more than 1 PC, they use shared storages and strict pipelines where local paths are forbidden.

Network paths work completely fine as input btw.

Instead of your suggestion you want to acknowledge the bug and consider a fix.
I believe paths system is not as hard as other things and algorithms in Embergen :slight_smile:

1 Like