Not sure if this is the place, but with heavy scenes is the proper protocol with .vrscene files to do /frame? If so, do we add $F to the file name? And then how to tell standalone to render them as a sequence vs submitting them one by one? thanks
> If so, do we add $F to the file name?
Yes.
> And then how to tell standalone to render them as a sequence vs submitting them one by one?
What do you mean by that?
Submitting where? Submitting how?
V-Ray Deadline ROP has frame number controls.
If you have custom submitter - you’ll have to implement it yourself.
V-Ray Standalone is not a render manager.
OK, thanks. My ultimate goal actually isn’t really to render the .vrscene files with standalone but rather to read them into another scene and render *that* scene. We’ve never gotten the V-Ray Deadline submitters to work. But we hit another snag. If we render .vrscene files as a sequence out with $F in the file path, we can read them into a vrayScene node. They show in the viewport but do not render. However if we create .vrscene files as one huge file for the sequence, they don’t show in the viewport but DO render. Sigh. I don’t really care if they show in the viewport, but making the 2000+ frame .vrscene I think is going to be a non-starter
> We’ve never gotten the V-Ray Deadline submitters to work.
Well, you could report whats missing / not working.
Btw, latest Deadline version also supports VFH.
> But we hit another snag. If we render .vrscene files as a sequence out with $F in the file path, we can read them into a vrayScene node. They show in the viewport but do not render.
And what are the errors / warnings anything in log? Exported vrscene contents?
I can’t fix the issue if I don’t know that issue exists…
Any changes for a scene setup?
Hey I’m trying to help as well. We did report the Deadline problems. I’m making a scene right now that shows the problem with the .vrscene sequences.
Tnx, much appreciated!
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.
We’ve never gotten the V-Ray Deadline submitters to work.
We did report the Deadline problems.
Are we talking about this thread: - Chaos Forums
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 ?
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.
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.
Thank you for the logs. Here are the errors:
STDOUT: VFH * Python evaluation error: “No module named vray”
STDOUT: VFH * Traceback (most recent call last):
STDOUT: VFH * File “<stdin>”, line 1, in <module>
STDOUT: VFH * 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: - Chaos Forums
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?
Gary, add this to the houdini.env - this line
PYTHONPATH=“${VRAY_APPSDK}/python27;${PYTHONPATH}”
Update. Looks like it works! all three modes of the Deadline ROP.
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.
Any idea why that is happening again?
VFH * Build number:7598 hash:a9b4e90 from 05 Jul 2020 11:54
Thanks
Dominik
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.
Hi,
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
Well may be Royal Render need to support this syntax then?
yeah, I wrote them some hours ago - I just wanted to ask here before asking them 