Brecht

In the little patch below I have a jit.world and an equivalent using jit.gl.render.

How come the jit.world is running at only ~60fps while the jit.gl.render is running at the requested ~144fps?

Is jit.gl.render more efficient when not having the need for the additional functionality of jit.world? 

In the little patch below I have a jit.world and an equivalent using jit.gl.render.
How come the jit.world is running at only ~60fps while the jit.gl.render is running at the requested ~144fps? 

Is jit.gl.render more efficient when not having the need for the additional functionality of jit.world? 


jit-world-vs-jit-gl-render-fps-discrepancy

(Without looking at the patch) sounds like jit.world has sync on. Then fps is capped at the refresh frequency of your display. There should be an @sync attribute for that.

This works, but seems to ignore the requested fps entirely, and runs faster.

jit.world @fps is a convenience attribute for setting @interval ((1.0 / fps) * 1000.0 = interval ).

if you want the exact behavior of the gl.render/jit.window combinations, simply set jit.world @sync 0 @displaylink 0 @interval 7

jit.world @fps is a convenience attribute for setting @interval ((1.0 / fps) * 1000.0 = interval ).
if you want the exact behavior of the gl.render/jit.window combinations, simply set jit.world @sync 0 @displaylink 0 @interval 7


jit.world vs. jit.gl.render fps discrepancy