$RFSTART and $RFEND no longer work in H17?

   2103   5   1
User Avatar
Member
146 posts
Joined: Sept. 2011
Offline
I could be going mad. So can someone confirm this behaviour before I report it as a bug, please?

$RFSTART and $RFEND refer to the start and end of the preview region of one's timeline, not the whole thing, so you could just render out, say, the middle of your scene. But they've stopped working for me: $RFSTART now equals $FSTART, and $RFEND equals $FEND. Which makes them useless:





Should be rendering from 184 to 227, not 1 to 250.

Just me?

(17.0.416 / Mac)
Edited by howiem - Dec. 6, 2018 01:19:34

Attachments:
Screen Shot 2018-12-06 at 06.14.46.png (306.2 KB)
Screen Shot 2018-12-06 at 06.15.00.png (331.6 KB)

User Avatar
Member
7737 posts
Joined: Sept. 2011
Offline
I've been using RFSTART/END in 17 without issue.

I remember seeing that happen back in the day when setting the play bar range with a script. Are you setting the play bar range manually, or with a script? If the latter you might need to call ‘varchange’.
Edited by jsmack - Dec. 6, 2018 02:02:52
User Avatar
Member
146 posts
Joined: Sept. 2011
Offline
Nope - just dragging the ends of the bar.

Just tried starting a new session, empty file, dragged the play bar range in a bit and typed in the textport:



Have to try trashing prefs etc. Boo. Thanks for checking for me

Attachments:
Screen Shot 2018-12-06 at 07.18.32.png (75.4 KB)

User Avatar
Member
7737 posts
Joined: Sept. 2011
Offline
Hey, I tried setting the play back range with the widget and got the same result you did(doesn't update). I've always typed in the numbers when working a project so it didn't come up for me. I can submit a bug if you don't want to.

Looks like the bug was introduced after release. It is not present in build 352, but is in 416(the current production build).
Edited by jsmack - Dec. 6, 2018 02:45:35
User Avatar
Member
146 posts
Joined: Sept. 2011
Offline
I've just submitted it - thanks for checking man - I owe you one. My sanity was in question
User Avatar
Member
146 posts
Joined: Sept. 2011
Offline
This is now fixed in 17.0.472. Yay
  • Quick Links