If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
here are further results
v 1-46
qmc noise threshold 0,01
min samples 8
result : 7m 27 sec , rays 35942907
qmc noise threshold 0,02
min samples 3
result : 5m 18 sec , rays 24025846
qmc noise threshold 0,03
min samples 3
result : 4m 36 sec , rays 19028980
this seems that it does the trick
in the irmap rollout it stills shows 29148 samples for the last and fastest try
should we use these as a default maybe now as the settings i had before were the default ones
there is no change in the image quality , however due to the resolution its very difficult to judge that accurately.
i m glad we got somewhere
thanks for all your time and suggestions vlado
it looks like after all that 1-46 might be staying...
actually there is other way to increase speed, by decreasing the amount value(right above the noise value) to 0.6 for example, and decrease the hsph to 20-25. I think, vray cuts out to fast samples. This will work very well on exteriors even with animation.
hi again
losbellos: the issue in this post was not mainly how to optimize the specific scene as the method you mention etc i know and have been using in previous vray versions
the problem is that both 1-45 and 1-46 with the same default values behave completely differently.
if there is a need for every scene to change qmc noise etc to get a scene rendering roughly the same as 1-45 then maybe those default values should change to something else and furthermore people should be made aware from now on.
i only mean it in a very positive way so everyone can get even better results out of vray.
regards
alkis
If you have the time, try to follow some threads about 1.46 in the general and bug sections of the forum. Quite a lot of people are testing the differences between 1.45/1.09 and 1.46. Especially IR map and qmc settings need different values...
For IR map, change hsph to half the value you used before (and best to lower interp also). The qmc iq already discussed above. These are just my thoughts and are based on test with 1.09 vs 1.46, not sure if they apply to 1.45 vs 1.46.
Vray 1.46 has new default settings, but when you load an old scene it takes of course the values of that scene... I would also like to see a shift in values so that old and new builds render a bit more the same. But as vlado already said, this is different for every scene so probabely there's no general rule to do so.
its clear what is the problem, but the solution will be anyway always modify by hand. As every secene has to be tweaked for best performance.
And the usual stuff; if u start a scene with a version of software which works ok, better finish with it. Then when u start a newone start on a new software. No problems then (at least by this) ALso I strongly suggest to test all the features u might need.
And I think quite many times it has been noted that it is a beta.
I mean this on a very friendly way of course. No offense.
And the usual stuff; if u start a scene with a version of software which works ok, better finish with it. Then when u start a newone start on a new software. No problems then (at least by this) ALso I strongly suggest to test all the features u might need.
Many times you don't work on a project from start to finish in one continuous amount of time. So after a few months (in which you changed versions), you need to dig up that old file and render some changes. If then everything else that didn't need to change looks suddenly also different or it takes forever to render... Of course you could switch to the version you created the file with, but it would be nicer if this isn't necessary.
Also no offence but usually situations are not that simple.
thank you vlado
this is precisely why i have stayed with vray for all this time and will continue to do so.
i have a feeling as well that the updated build might be much closer than 1.45.70 was with 1.46.04
vlado please prove me right....
Comment