BattleJenkins
I agree. However I have voiced opinion for this for years before your arrival. There are three factors involved why there is no FPS control on anything.
1. The change would require an architecture change to C2 root rendering.
Earlier this year Ashley threw in a simple FPS controller. However due to everything else it was impossible to get smooth animation. I know it's possible to have a good FPS controller but all the plugins that require motion would need re-working.
2, Ashley believes that there is no reason to run less than max capable and 60fps marker. Also Ashley claims that dt is working well enough even when the fps drops.. Though evidence shows enough to contrary.
3. It's a once man team doing the core programming...still .. Maybe down the road there will be enough programming staff to really take on some of the developer bottle necks.
i actually once linked to a fantastic article that swapped the FPS control. Due abvoe reason 1. There was the alternative or limiting the FPS of logic instead. This means that by dropping logic updates to less often this would allow better maintaince of FPS smooth rendering and ultimatly betterg ame performance without requiring the architecture changes. unfortunatly it was ignored. but hey. I tested out the theory on my own.
I wrote an on every 0.0033 tick. Inside there was a loop that went through an array and called a function. Essentialy I wrote a logic kernel. On my tests for mobile. I was able to get 5fps program up to 60fps by only doing the logic of the trig at apx 24fps and 30fps. So for my standards now that if there is any heavy trig going on. I'll either limit the updates or build a simple kernel. The result has been fantastic