progressive now ignoring noise threshold.?

[super gnu]

wierd one. been using the same settings for all my current job.. renders slow but converges to a lovely clean render overnight.

progressive, msr 16, noise thresh.0.004 global subdivs 0

all was entirely predictable until my last test render. it was giving me an eta of 6 hrs (always drops as parts reach noise thresh.)

i cancelled it, adjusted a couple of maps, reduced render res from 3500 wide to 2500 wide and hit render again.

the render completed in 20 mins, but still all grainy, as if id set a noise threshold of 0.02, not 0.004

i checked, all my settings are as before, but it now refuses to do a longer cleaner render.

using the latest 3.2 on 2014

[super gnu]

ok seems to be a bug.. i forgot i also added a camera correction modifier to the camera.. took that off, and now it renders as expected i.e. slowly and for ages.

[super gnu]

hm, possibly also worth noting that i got a build of vray from vlado one day before the official release to solve a bug.. dunno if its exactly the same one as the official release.. its 3.25.01

[super gnu]

ok i was mistaken. its still doing the wierd thing.. wasnt the camera correction.

[super gnu]

so, it basically seems like ive lost a decimal place in my noise thresh. if i set it to 0.001, it does get cleaner before stopping, but still granier than my earlier tests at 0.004 threshold. very odd. is there any reason an exterior shot would be noisier (for a given final noise threshold) than an interior shot in the same scene with the same settings?

i ask because the last full on render i did in this scene was an interior, so its possible i just dont understand noise threshold properly.


as i understand it, if progressive finishes, at a given noise threshold, without a time limit, it will always produce the same graininess level, irrespective of the scene..?

-nope, not that.. ive just gone back to my interior cam.. its doing the same thing.

[super gnu]

ok quick update, after pulling my hair out for several hours, i -think- ive fixed it.

until now ive been using standard camera with vray exposure control set to photographic. been working fine.

however i really needed to migrate to physical cameras, since each shot needs different exposure settings.

so i replaced my standard cams with physcams and copied the settings from the exposure control to the camera.

i left the exposure control on, since the physcams override it, and was testing an angle from a perspective view.

i got the wierd result.

now ive removed the exposure control and im using a physcam for my test shot, it seems to be working ok.

so,
*exposure control +standard cam = fine
*physcam = fine
*exposure control +standard cam *with physcams in the scene* -broken noise threshold..

wierd, but thats my analysis so far.

[vlado]

This is max 2014, right?

Best regards,
Vlado

[super gnu]

yep it is.. and the version of vray you gave me for the rt gpu issue. its the same scene (the one with the swimming pool)

[super gnu]

just wondering if you were able to reproduce this or its some stupid error ive made somewhere? its such an odd problem..