Hello! Let me see if I'm following you correctly.
Do you want to se your proxy geometry in viewport and render your bgeo seq in RV right?
Found 6 posts.
Search results Show results as topic list.
Houdini Indie and Apprentice » Rendering instances Redshift
- dyne
- 6 posts
- Offline
HOULY Daily Challenge » Day 1 | Elements: Earth
- dyne
- 6 posts
- Offline
Hi, Carlos Dordelly here again. Here is my entry with my official Side FX account too.
Cheers.
Cheers.
HOULY Daily Challenge » INTRODUCTION
- dyne
- 6 posts
- Offline
Hello! If my side fx account is from my design studio I need to create a personal side fx account to submit my work? I have this doubt after read the groups question on the FAQs.
Thanks.
Thanks.
3rd Party » Redshift ROP + Deadline: extra tokens detected in expression
- dyne
- 6 posts
- Offline
PDG/TOPs » Basic Wedge - ROP Geometry Performance
- dyne
- 6 posts
- Offline
Hi guys! I'm learning some PDG basic things and I have to say that TOPs a reaally awesome thing! But, I have an small issue, if I make a basic wedge variations on a geometry (like scale a cube) all my variations are cooked almost immediately but the TOP Geometry node takes too long to write each file, even if I change the total slots parameter to “Equal CPU Count Less One” in the local scheduler.
Is there any way to improve the performance of the ROP Geometry? I'm using Houdini 18.0.460, I understand that this can be useful to run in background without affect the main performance of the cpu but in some cases I would prefer to export with full performance to export my multiple assets more quicker.
In the attached video you can see how it takes almost 4 minutes to write the bgeo cube files and is happening the same thing with the Alembic ROP, I suppose I'm missing something somewhere.
Thanks a lot, cheers!
Is there any way to improve the performance of the ROP Geometry? I'm using Houdini 18.0.460, I understand that this can be useful to run in background without affect the main performance of the cpu but in some cases I would prefer to export with full performance to export my multiple assets more quicker.
In the attached video you can see how it takes almost 4 minutes to write the bgeo cube files and is happening the same thing with the Alembic ROP, I suppose I'm missing something somewhere.
Thanks a lot, cheers!
3rd Party » Redshift ROP + Deadline: extra tokens detected in expression
- dyne
- 6 posts
- Offline
Hi guys!
I installed Deadline recently and normally I have a multiple RS Rops where I define the render folder path with a string parameter in a null node. The thing is when I submit the render job to Deadline with the expression that I use for output I'm getting this error:
(Syntax error - extra tokens detected in expression (/out/Redshift_ROP_HQ_PMs_DWAA/RS_outputFileNamePrefix)).
I 'm defining the folder paths in the null like this: $HIP/render/
And the rest of the expression on the RS Rop is like this: `chs(“../RENDER_PATHS/render_folder”)`$HIPNAME/$HIPNAME.$AOV.$F3.exr
Somebody knows how I have to change the output expression in order to get the render correctly? Here is a screenshot from the expression:
Thanks a lot!
I installed Deadline recently and normally I have a multiple RS Rops where I define the render folder path with a string parameter in a null node. The thing is when I submit the render job to Deadline with the expression that I use for output I'm getting this error:
(Syntax error - extra tokens detected in expression (/out/Redshift_ROP_HQ_PMs_DWAA/RS_outputFileNamePrefix)).
I 'm defining the folder paths in the null like this: $HIP/render/
And the rest of the expression on the RS Rop is like this: `chs(“../RENDER_PATHS/render_folder”)`$HIPNAME/$HIPNAME.$AOV.$F3.exr
Somebody knows how I have to change the output expression in order to get the render correctly? Here is a screenshot from the expression:
Thanks a lot!
-
- Quick Links