ROP Fetch TOP - how to use ROP Node Configuration?

   Views 666   Replies 4   Subscribers 0
User Avatar
Member
9087 posts
Joined: July 2007
Offline
- I have a ROP Geometry Output SOP set to Render Frame Range 1|100|1
- Fetched it using ROP Fetch TOP
- set FramesAndBatching/EvaluateUsing to ROP Node Configuration

it results in 1 workitem

1. How do I make it actually using the range from my ROP?
- tried adding float3 parm of the same name as on ROP Fetch TOP (range1, renge2, range3) on top of ROP's default (f1, f2, f3), but that didn't make any difference

2. is it possible to also add other settings like All Frames In one Batch to the ROP itself? Is this ROP Node Config actually configurable?
- I tried to look for TOP Related Node Properties, but there is nothing related to Frames and Batching

It's very important for settings to live on the ROP rather than be scattered in all the possible TOPNetworks that may fetch the ROP, especially the Range to avoid node produced one result when cooked from node itself (Save To Disk) and another when cooked from TOPnet

H20.5.487
Edited by tamte - Feb. 1, 2025 14:46:00
Tomas Slancik
CG Supervisor
Framestore, NY
User Avatar
Member
9087 posts
Joined: July 2007
Offline
as a workaround using expressions in the range on ROP Fetch TOP seem to work
ch(chsop('roppath') + "/f1")
ch(chsop('roppath') + "/f2")
ch(chsop('roppath') + "/f3")

this also allows the "roppath" to be dependent on workitem attributes

I'd still be nice to know why the ROP Node Config creates just a single workitem for the whole range
Edited by tamte - Feb. 1, 2025 15:02:11
Tomas Slancik
CG Supervisor
Framestore, NY
User Avatar
Staff
613 posts
Joined: May 2014
Offline
tamte
I'd still be nice to know why the ROP Node Config creates just a single workitem for the whole range

That mode exists specifically for use with ROPs like the FBX, Alembic and sometimes USD where the frame range isn't known until the ROP actually cooks. For example, the FBX ROP can be setup to load a frame range from an FBX file. In that case the only thing TOPs can do is create a single task that cooks the target ROP exactly as-is, and waits for it to cook over what frame range it wants.

For ROPs with frame ranges defined statically using parameters it's possible to use a ch-ref.
User Avatar
Member
9087 posts
Joined: July 2007
Offline
the CH references are ok, but still require a setup, it's be nice to be able to just add TOP related parameters on the ROP itself that ROP Fetch could inherit

that way the same ROP fetched into one or multiple TOPnets can produce the same result as it's configured without User having to think about what needs to be channel referenced

of course this is just a workaround to seemingly not being able to fetch configured TOP node statically https://www.sidefx.com/forum/topic/99586/ [www.sidefx.com]
since that would also allow to have config already on the TOP node which is part of the setup and just fetch to a bigger TOPnet to set dependencies
Tomas Slancik
CG Supervisor
Framestore, NY
User Avatar
Staff
613 posts
Joined: May 2014
Offline
That should be possible, e.g. by having the ROP Fetch evaluate the frame parameters on the ROP and use the values found there. Please log an RFE.
  • Quick Links