I did some test on my rig. A screen with a simple sphere looping with a flip 0, I get 2850 fps with a TEXT instruction saying "FPS: 2850" in small letters. If I use FastImage to display the fps, I get 3000 fps of the same thing. So roughly, I lost 150 fps with a TEXT instruction.
I also did a second test, but with a busy screen. With or without using the TEXT instruction on the busy screen, I got a solid 160 fps, so I lost no frames on my second test.
Using TEXT for a flip 1 won't have ANY influence.
Finally, using TEXT to display your FPS is very convenient if your 3D app is in the lower FPS ranges. If it's hitting 1000+ fps, then obviously TEXT will eat up a couple of them to do what it has to do.
I also did a second test, but with a busy screen. With or without using the TEXT instruction on the busy screen, I got a solid 160 fps, so I lost no frames on my second test.
Using TEXT for a flip 1 won't have ANY influence.
Finally, using TEXT to display your FPS is very convenient if your 3D app is in the lower FPS ranges. If it's hitting 1000+ fps, then obviously TEXT will eat up a couple of them to do what it has to do.