search

ChaosGroup / blender_with_vray_additions

Blender with patches for V-Ray *.vrscene export
Other
28 stars 13 forks source link

DR with absolute paths - doesn't seem to work. #252

Open philstopford opened 5 years ago

philstopford commented 5 years ago

I have assets in d:\blender available on my main system as well as the render node, I hoped to use 'absolute paths' to avoid pushing more data over the network than necessary. On the render node, though, I see :

[2018/Oct/17|20:42:51] Starting DR session from 10.0.1.151 [2018/Oct/17|20:42:51] Receiving DR scene from 10.0.1.151 [2018/Oct/17|20:42:51] Reading scene file "C:\Users\phils\AppData\Local\Temp\vrscene_20207_4808.txt" [2018/Oct/17|20:42:51] error: Error in file "C:\Users\phils\AppData\Local\Temp\vrscene_20207_4808.txt", line 377: No file "C:\Users\phils\AppData\Local\Temp\scene_nodes.vrscene" exists [2018/Oct/17|20:42:51] Starting render sequence.

and the render fails.

If I use the regular V-ray transfer, the render proceeds as expected.

bdancer commented 5 years ago

Is the export directory set to "d:\blender"?

philstopford commented 5 years ago

No - the export directory is still global tmp. It's so removed from the asset sharing setting that I didn't understand that the two are related. My expectation had been that the vrscene would be shared as before with the nodes, but any external assets would be referenced from their locations (as absolute paths).

I'm obviously not entirely clear on the mechanism behind the scenes.

bdancer commented 5 years ago

"absolute" means absolute, like all paths are exported as is. User have to make sure all the paths are the same on main machine and DR nodes.

philstopford commented 5 years ago

So the vrscenes used for the DR are written to the absolute path of the export path, and that should be available on the nodes. It's not just about the asset sharing (e.g. images)

bdancer commented 5 years ago

@philstopford if you have "separate files" turned on then yes, but if you disable it - then no.