Timing executable inside

Miscellaneous Forums/General Discussion/Timing executable inside

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

Kenshin: Yeah that's it, you should get those lines no matter what the flag in windowed mode...

OEJ: moving another window over the demo doesn't affect it on my PC. If I boost the shapes up to 3000 ish then the window moving around is a bit slow.

I guess we are just going to have to bite the bullet and choose a method so that we can get on with a game. My demo has music and sounds too and a background, and fonts, and animimages, so this might all be making performance worse on some PCs.

[edit] In fact in my demo I have an FPS counter which counts the number of flips per second. Now this is normally rock stead and the same as my desktop Hz (in windowed mode) but If I stress the app, the FPS can drop, this is the jerks people are seeing as the logic catches up. You could add an FPS counter to yours, stick it in FLip -1 mode, and find the borderline between full FPS (i.e. desktop Hz) and half that (i.e. draw taking too long) On this borderline, sometimes it will render full FPS and other times not. This will result in jerks, unless Flip 0 is on. It's the same thing in FPS games of course. PLus it'll be more obvious on even faster moving shapes.