Diagnostic Tools

[Dariusz Makowski (Dadal)]

Heya

Any chance to get from Chas group a diangnostic tools that would tell us how much our CPU spend doing what?

Like

Calculating trace depth
Calculating AA noise
Calculating Shader Noise
Calculating GI / noise/tresholds
etc etc?

I think for the moment tunning up scenes is a bit "blind" u up samples and hope that shader glossines has enought samples so that AA wont have to clear it up etc etc. If we had diagnostic tools we could be more accurate in shadering and tweaking scenes, since we would know what our CPU is wasting his power on...

Thanks.

[vlado]

It would take more time to collect these particular statistics than to perform the actual calculations - they are negligible compared to the most calculation-intensive tasks - ray casting, texture sampling and shader calculations.

Even if V-Ray did print the statistics you want, they won't help in any way to do what you need - which I assume is to figure out how many subdivs to put for a given material. In theory, it might be possible to get an approximation of how many samples would be needed to clear up a material for the specified Noise threshold - I suppose this would be much more useful.

Best regards,
Vlado

[zeronove]

In theory, it might be possible to get an approximation of how many samples would be needed to clear up a material for the specified Noise threshold

gasp!!! ...may I ask you to elaborate this idea a bit more