If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
we are using Royal Render to submit the written vrscenes. The submit plugin reads the filepath written in the vrscene and this leads to a wrong image file path output:
in the vrscene:
img_file="Oelfilter_test.v003.001.<reName>.<frame0 4>.exr";
img_dir="*censored*/Oelfilter/test/houdini/render/";
in submitter:
../*censored*/Oelfilter_test_test.v003.001.<frame04>.exr
but it expects:
../*censored*/Oelfilter_test_test.v003.001.0001.exr
Hello Mr.Hoo , this is how V-Ray understands $F4. This shouldn't be a problem for files names. In order to check the problem I'll need the whole file path expression you are using.
vrscene should be fixed in the next night, frame tag replacement was done wrong (there is an error message in the log btw).
As a workaround you could use ${F4} instead of $F.
Hi Andrei,
currently we have the issue, that ${F4} in the File Path is not evaluated correctly inside the vrscene file. It is evaluated to <frame4>, and therefore writes incorrect named files.
How is V-Ray set up on the machine doing the export for this log ? The PYTHONPATH variable should contain the appsdk/python27 folder - not having this is the only reason I can think of for this message to pop up.
More info here: https://forums.chaosgroup.com/forum/...udini-18-0-391
When you say set up, can you be more specific? I'm not really the TD but is the PYTHONPATH typically set in the .env or is that a system variable?
STDOUT: VFH [Error] * Python evaluation error: "No module named vray"
STDOUT: VFH [Error] * Traceback (most recent call last):
STDOUT: VFH [Error] * File "<stdin>", line 1, in <module>
STDOUT: VFH [Error] * ImportError: No module named vray
How is V-Ray set up on the machine doing the export for this log ? The PYTHONPATH variable should contain the appsdk/python27 folder - not having this is the only reason I can think of for this message to pop up.
More info here: https://forums.chaosgroup.com/forum/...udini-18-0-391
Thanks I'll take a look. When I get a second I'll test again. My recollection is that we never got anything except Export Local/Render to work and that - for that scene at least - the .vrscene file creation was taking so long that we just ended up rendering in the Command line.
vrscene should be fixed in the next night, frame tag replacement was done wrong (there is an error message in the log btw).
As a workaround you could use ${F4} instead of $F.
I was under the impression the problem is resolved - the submissions were failing because of errors in the log. Can you please try enabling the Log window and checking for text in red ?
OK, so in the linked file both vrayScene nodes are reading the same sequence. The one called SEQ is reading it as a sequence whereas SINGLE is just reading frame 1501. SEQ does not render but SINGLE does.
Leave a comment: