Another file sequence bug.

[Dubbie99]

vray_adv_51020_houdini18.5.672_ff45c2b_16483
Windows 10

I have a V-Ray light with an animated texture on it.
When I render a single frame, it renders just fine. When I render a sequence, the vrscene file for each frame doesn't have the frame number in it. It just has the <frame> token still in there.
So the sequence renders black because the texture is not found.

I have resorted to parsing all the vrscene files and replacing the token with the proper frame number just to get my renders out.

It would be really good if you could fix this and the other deadline file sequence bug as well.

[update] just confirmed that this seems to be happening with any sort of file sequence, such as displacement image file sequence or a vray image emission map.

Thanks,

Rhys

[bdancer]

> It just has the <frame> token still in there.

Well, this is correct.. Frame will be replaced with the framenumber render time...
How are you animating the path? Manually with some script?

[Dubbie99]

hrm. Well even if I do a local render to a sequence, the map doesn't show.
If I render current frame it does.
The path is just set with $F4. nothing fancy.

[chakarov]

Hello Dubbie99 , unfortunately I can't reproduce it on my end. Can you share a simple scene were the problem occur.

[Dubbie99]

I think I have figured out what my problem was. I actually had the override frame number box checked. With that off, it renders fine. With it on, it does not.

[bdancer]

> With that off, it renders fine. With it on, it does not.

If it's on - what setting do you have? I guess the generated override frame is out of your images range? If you could attach full setup with textures I could check this.

[Dubbie99]

Sorry for the delay in getting back to you on this.
I will try to set up a scene tomorrow for you.