FPS dropped from 100 to 64 to 50
Posted: Tue Feb 12, 2008 4:22 am
I'm still playing around with the RigidBody-Sample (see also this other topic) but now I've run into a different problem.
At first, I got 100 fps with rigid body data in all of the frames, and I saw that it was good.
Then, after some work (including a new calibration), I suddenly only got 64 fps. Hardly fluctuating, 64 plus or minus 0.1.
The Rigid Body Tool itself still ran at around 100 fps. I tried several things including putting back my old calibration file, unplugging and replugging the cameras, recalibrating again, starting and stopping the Calibration and RB tools, and changing the Illumination and Exposure in the calibration file. At a certain point, I was back at 100 fps, but for an old (now invalid) calibration file, and when I put back the new (valid) one I was back at 64 fps and couldn't get back to 100 even with the old calibration file.
Then I unplugged and replugged the cameras once more, and suddenly I was at... 50 fps.
Another replug, back at 64. Haven't seen 100 since.
All this time, the RB tool itself happily runs at 100 fps. The RB API has no way to set FPS. What is going on? How do I prevent or fix this weird behaviour?
At first, I got 100 fps with rigid body data in all of the frames, and I saw that it was good.
Then, after some work (including a new calibration), I suddenly only got 64 fps. Hardly fluctuating, 64 plus or minus 0.1.
The Rigid Body Tool itself still ran at around 100 fps. I tried several things including putting back my old calibration file, unplugging and replugging the cameras, recalibrating again, starting and stopping the Calibration and RB tools, and changing the Illumination and Exposure in the calibration file. At a certain point, I was back at 100 fps, but for an old (now invalid) calibration file, and when I put back the new (valid) one I was back at 64 fps and couldn't get back to 100 even with the old calibration file.
Then I unplugged and replugged the cameras once more, and suddenly I was at... 50 fps.
Another replug, back at 64. Haven't seen 100 since.
All this time, the RB tool itself happily runs at 100 fps. The RB API has no way to set FPS. What is going on? How do I prevent or fix this weird behaviour?