flythrough/use camera path lightcache calc not working vray adv

[super gnu]

im trying to generate a flythrough lightcache, like ive done a million times.

however now when i hit render, it calculates the lightcache only for the last frame. normally you see a nice smudgy mess being created. this time i get a sharp version of the last frame.

same result if i have it on "single frame" with use camera path enabled.

ive definitely got the camera as the active view, and the timeline is set to the range over which the camera operates.

any suggestions?

[super gnu]

definitely something weird going on. if i shorten the timeline, i get whatever the last frame on the timeline is, being calculated.

doesnt matter which frame i choose to render, or if i choose to render the active time segment. same result.

im on the latest vray and ive trid in 2014 and 2016..

i have another scene that worked fine a few days ago with the same software.

[super gnu]

ok i reinstalled 3.5, and now its working as expected. so.. seems its a 3.6 bug.

[vlado]

If it's a bug, I would like to fix it, but I'll need a scene for that. The tests that we have here work fine, so there's probably something specific in your case.

There were some changes in 3.6 to make the light cache samples more evenly distributed along the camera path and maybe that calculation goes wrong for your scene.

Best regards,
Vlado

[olly]

Did this get fixed? I having the same problem!

Light cache is also taking around 16 minutes to save in VRay 3.6 - I just posted about it here

[olly]

Actually the same thing is wrong with the IR map when using "use camera path" - loads of samples for the first frame and hardly any for the rest of the path.

[tashko.zashev]

I just wanted to update this thread with our findings about this issue. '
We found a bug in the in the latest release 3.6 builds with Use irradiance map and our dev. team is working to solve it. V-Ray 3.50.04 seems to be the latest version where this issue doesn't exist.

[jackieteh]

Hi, may I know is there any update for this post? I have the same issue here...

[Miro]

Hi, may I know is there any update for this post? I have the same issue here...

The issue is still open. We'll update this thread when we have any news.

[jackieteh]

Hi, still no update for this thread?

[suhit2005]

Hi, I also have similar issue any update on this....?

[jackieteh]

Hi, I also have similar issue any update on this....?

Hi, same here, i am still waiting for answer...

[jim mann]

Hi, same here, i am still waiting for answer...

Am also experiencing this. Not keen on the idea of changing all the render machines back to 3.5.04

Correction, it's an issue with the file/scene. Older versions of max, with older versiobs of Vray exhibit the same issue, but current version, on a different scene works fine.

[jackieteh]

Am also experiencing this. Not keen on the idea of changing all the render machines back to 3.5.04

Correction, it's an issue with the file/scene. Older versions of max, with older versiobs of Vray exhibit the same issue, but current version, on a different scene works fine.

Oh do you mean the problem is because i am open a scene which is using older version of Vray,( for example i open a scene created with 3ds max 2014 and vray 2.xx into 3ds max 2014 and vray 3.xx? )

[jim mann]

Oh do you mean the problem is because i am open a scene which is using older version of Vray,( for example i open a scene created with 3ds max 2014 and vray 2.xx into 3ds max 2014 and vray 3.xx? )

The problem was connected to the scene, and not the version of Vray. Other scenes (Max files) worked fine in the latest version of Vray.