[Sidefx-houdini-list] whitewater_sim writing the wrong frames
gary at corestudio.com
Fri Aug 4 15:10:23 EDT 2017
Hmm, that could be it. In looking the whitewaterobject the Creation Frame is ch(opcreator(“.”)+”/startframe”) which evaluates to 612. Not sure where that is coming from? But 900-612 is 288 which is close to the first .sim file being written. Actually it’s 289. But the output is set to $RFSTART and $RFEND (as are most of the nodes). The seed is set to $ST.
Gary Jaeger / 650.728.7957 direct / 415.518.1419 mobile
> On Aug 4, 2017, at 11:58 AM, Gregory Ecker <gregory.ecker at gmail.com> wrote:
> hard to say without looking at it. Are you using or referencing $SF
> somewhere instead of $F ? $SF is relative to the start frame of the dopnet
> it is being evaluated in, so if the start frame of your dopnet is 900,
> $SF would be 1 at that frame.
> just a guess.
> On Fri, Aug 4, 2017 at 2:52 PM, Gary Jaeger <gary at corestudio.com> wrote:
>> Hi. Can anybody think of why my whitewater_sim output would be writing the
>> wrong frame numbers? Or at least they are unexpected! My scene frame range
>> is 900-1200. I cached out the whitewater_source no problem. I can check
>> Load from Disk and scrub the source particles. But when I now try to write
>> out the whitewater_sim output the file numbers are starting at .289 for
>> some reason? I assume I caused a mess someplace but for the life of me I
>> can’t figure it out. Where could that be coming from?
>> Gary Jaeger / 650.728.7957 direct / 415.518.1419 mobile
>> http://corestudio.com <http://corestudio.com/>
>> Sidefx-houdini-list mailing list
>> Sidefx-houdini-list at sidefx.com
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
More information about the Sidefx-houdini-list