Scaling performance based on FPS

[funwithtriangles]

Can performance.regress (or perhaps performance.current) be based on FPS? Most of the time my users don't need a pixelated canvas but if they are running low powered hardware on a particularly complex scene, I'd love this feature to kick in. From my understanding, performance.current is manually set by using performance.regress and is not tied to the current performance of the machine (e.g. FPS).

Has anyone ever achieved good results by regressing based on the user's FPS? Or some other metric? I can see this being achieved in one of two ways:

1. Have some way of making performance.current respond to the user's FPS. If they're using a very powerful machine, this value will always steadily remain at 1, regardless of performance.regress being called or not
2. Handle when performance.regress is called by checking the user's FPS. If it's below a certain threshold, then only call performance.regress

[drcmda]

sure, it's completely extensible. if you find a way to figure out what the current fps is you can set the performance margins and let the app react to it.

[funwithtriangles]

Is there a way to update performance.current?

[drcmda]

const set = useThree(state => state.set)

set(state => ({ performance: { ...state.performance, current: 1 } }))

though that's not how it should work. performance.current is set to min when something calls regress(). you should adapt min instead. set it to 1 when everything's stable and lower when you detect fps lag. call regress in anything that moves, then react to current any way you like.