gameknife / gkNextRenderer

A Modern gkRenderer
15 stars 2 forks source link

frames per second counter is broken? #6

Closed tigrazone closed 2 weeks ago

tigrazone commented 2 weeks ago

in RayTracingInVulkan I change number of bounces but fps counter is still 59-60 with ANY SCENE. I try on 3060 laptop. Is it error or it's ok? I also try to set Temporary Steps to 2-8 and fps counter not changed. I think, in gkNextRenderer used same code for recursive path tracing cycle(is it faster then for cycle?) and same fps counter code. Please check

gameknife commented 2 weeks ago

--present-mode=0, disable the vsync

tigrazone commented 2 weeks ago

Is your created by defines recursive path tracing cycle are faster then cycle by for operator?

gameknife commented 2 weeks ago

Is your created by defines recursive path tracing cycle are faster then cycle by for operator?

the define recursive and for will not affect the performance, you mentioned the fps at 59-60, it must be the vsync issue, in RayTracingInVulkan, start with --present-mode=0 will gain much more fps.

but there's a different impl: the default bounce times is set to 4, but it is not enough for refraction material, so I add ray.BounceCount--; to refraction material, to get more bounce for specific materials, but others still limited to default bounce times