Announcement

Collapse
No announcement yet.

Standalone per frame

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mr.Hoo
    replied
    Originally posted by bdancer View Post
    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

    Leave a comment:


  • bdancer
    replied
    Well may be Royal Render need to support this syntax then?

    Leave a comment:


  • Mr.Hoo
    replied
    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

    Leave a comment:


  • chakarov
    replied
    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.

    Leave a comment:


  • Mr.Hoo
    replied
    Originally posted by bdancer View Post
    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.

    Any idea why that is happening again?

    VFH [Info] * Build number:7598 hash:a9b4e90 from 05 Jul 2020 11:54

    Thanks
    Dominik

    Leave a comment:


  • corestudio
    replied
    Update. Looks like it works! all three modes of the Deadline ROP.

    Leave a comment:


  • hsz
    replied
    Gary, add this to the houdini.env - this line

    PYTHONPATH="${VRAY_APPSDK}/python27;${PYTHONPATH}"

    Leave a comment:


  • corestudio
    replied
    Originally posted by Gosho.Genchev View Post
    Thank you for the logs. Here are the errors:

    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?

    Leave a comment:


  • Gosho.Genchev
    replied
    Thank you for the logs. Here are the errors:
    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

    Leave a comment:


  • corestudio
    replied
    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.

    Leave a comment:


  • bdancer
    replied
    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.

    Leave a comment:


  • Gosho.Genchev
    replied
    We've never gotten the V-Ray Deadline submitters to work.
    We did report the Deadline problems.

    Are we talking about this thread: https://forums.chaosgroup.com/forum/...be-fixed/page2

    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 ?

    Click image for larger version

Name:	log_errors.png
Views:	410
Size:	276.2 KB
ID:	1065425

    Leave a comment:


  • corestudio
    replied
    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.

    https://www.dropbox.com/s/oq8wa0xwc8...scene.zip?dl=0

    Leave a comment:


  • bdancer
    replied
    Tnx, much appreciated!

    Leave a comment:


  • corestudio
    replied
    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.

    Leave a comment:

Working...
X