Announcement
Collapse
No announcement yet.
vrscene import - can't re-link image maps
Collapse
X
-
I don't think you can at the moment. Only option is to import the .vrscene on a machine that has access to this path.
I hope to take a look at this soon. I will add several options to help with finding missing assets while importing, including the option to browse for the file manually.
I will report back here.
Greetings,
Vladimir NedevVantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help
-
Originally posted by vladimir.nedev View PostI don't think you can at the moment. Only option is to import the .vrscene on a machine that has access to this path.
I hope to take a look at this soon. I will add several options to help with finding missing assets while importing, including the option to browse for the file manually.
I will report back here.
Greetings,
Vladimir Nedev
Any update on progress with this issue?
Comment
-
Originally posted by studiotribe View PostThanks Vladimir,
Any update on progress with this issue?
I am working on the environment importance sampling + shadow catcher problems.
Greetings,
Vladimir NedevVantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help
Comment
-
The re-linking of image maps (and other external files like IES files and ptex textures) during .vrscene import is finally possible in tomorrow's nightly build ( 2016.09.03 ).
When an image cannot be found, you will be asked to locate the missing file.
The mapping between the old and new location will be stored, so if you have moved whole folders (with sub-folders) without modifying any names, you will only need to re-link the first file, and the rest should be found automatically.
This is similar to how MODO image map re-linking works when you open a scene.
Greetings,
Vladimir NedevVantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help
Comment
Comment