Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- Lord_of_the_Galaxy December 2016
- ondsinet_ December 2016
- quark December 2016
new FX2D ignores frameRate()
Howdy, some days ago I had a little problem with my program having too little fps, so I tried some different renderers, including the brand new FX2D. While this one gave me awesome performance, with supposed framerates in the order of the tens of thousands, I wanted to lock it to 60. But frameRate(60) or similar makes my sketches go crazy reporting framerates such as 14000 and such. Using any other renderer fixes the problem but when using FX2D the framerate sparks to "OVER NINE THOUSAND!", which interferes with my animations. Also is seems more like 3fps than thousands but it could be too fast for us humans to see.
Is it just me or is this a processng bug?
EDIT After some testing, i belive that the fps are actually becoming pretty low, while the variable frameRate returns inaccuate values. I'm not sure tho, since even now the framerate sometimes jumps over 800
Answers
What testing did you do?
Instead of allowing Processing to calculate frameRate, why not just use the frameCount variable to check yourself?
Don't use frameRate() or frameCount to control animation. The first assumes that the frame rate is being measured correctly, the second simply counts the frames rendered and does not take into account time.
The solution is to use the time elapsed between frames. You can find out more here
Well, I'm not sure that this was a question on how to solve problematic frame rates. It was more of why it occurs.
In any case, your advice is extremely important when designing a game (or anything else).
Yes, quark's suggestion is quite useful indeed.
But I was more interested in knowing why this happens, because this looks like a bug to me.
BTW the unreasonably high framerate is actually very slow, like 0.5 fps , calling a println echoing the millis confirms that.
I guess this new feature is still prone to errors.
Please file this bug.