Help with the new draw cap in v96
-
Were other fps and frame related stuff changed? Im testing a bomb that, for 1 frame, has a LIGH flash. On v95 you could see it for a slight second, if I set drawcap to 60 it still doesnt show it, along with my fps still not being the same as in v95.
Edited once by Pexy. Last: 11th Jul 2021 -
All that happened was that the draw cap was made possible to disconnect from the FPS cap.
As for "regular frame drawing", I realise now that you want every frame drawn exactly once, like in v95. This is achieved by setting the draw cap to 0, which is the "do what v95 did" setting. If you want this to be the default, rather than TPT querying your monitor's refresh rate and setting it automatically as the draw cap, you'll have to add tpt.setdrawcap(0) to your autorun sequence.
We used to have an option to disable this automation, but @jacob1 didn't like it so it's gone now. I *cough* hope this thread convinces him that this should be possible to disable in the settings dialog. Since there'll surely be a v96.1 soon, thanks to a custom GOL bug that nobody managed to report until 6 hours after v96.0 was released, I guess you could also wait for that.Edited 3 times by LBPHacker. Last: 11th Jul 2021 -
Thanks a bunch, works perfectly.
-
This post has been removed by LBPHacker: not related - also, you can literally just check
-
Annoying, this is the problem I was worried about when I removed the option. I'll think about ways to fix it. I could restore 95.0 behavior, but I don't like that behavior, it can cause excessive gpu usage. I could add vsync (which was my real goal), but this prevents you from setting the fps cap above 60.Edited once by jacob1. Last: 11th Jul 2021
