Abel wrote:Thanks, I'll give it a try soon. I'm happy about the change because one of the things I use the statistics for is to see if the system is working at optimal speed and if no swapping is occurring. If there is swapping, I tend to close other programs and then watch if LuxRender's S/s value goes up; lately this didn't work too well as like you say it tended to take a long time to get closer to current speed. I'm sure there are other means to check if there is enough memory available to LuxRender but I like the direct feedback of LuxRender's statistics.
jeanphi wrote:Instead of a fixed filter value you should probably use min(1, elapsedtime/filtertimewindow) otherwise depending on the frequency of the calls to the update method you'll modify the filter response (and don't forget to treat the elapsedtime==0 cas like before otherwise you might blow up the computation). The added benefit will be a more commonly understandable parameter :)
Users browsing this forum: No registered users and 1 guest