Frames per tick control
-
For the purpose of this suggestion, tick means a physics update. The idea is an option (even if console only) that sets how many frames happen before a tick, with the default being 1 (every tick). By increasing this, you could make slow motion without reduced frame rate. This would be kind of like an automated F button, and should not be too difficult to implement.
-
This is very similar to just changing how many frames happen per second, which can be done by typing
tpt.setfpscap( frames per second you want ) in the console.
-
This would require the graphics and update methods to be independent from eachother and ran on separate threads, which is not as simple as you make it sound.
-
@therocketeer (View Post)
I was thinking he meant to separate the update/graphics stuff from the interface stuff. Particle updates, particle graphics, and the interface are all separate things which each happen once a frame. It would probably be easy to make the particle graphics only draw every 2 (or more) particle updates. Separating the interface and the simulation entirely would be harder, but that is what you would need to do if you wanted like the mouse and any buttons on the edges to always be responsive.
