We get it. We use ad blockers too. But GameDev.net displays them so we can continue to be a great platform for you.
Please whitelist GameDev.net and our advertisers.
Also consider a GDNet+ Pro subscription to remove all ads from GameDev.net.
Jump to content
Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.
Posted 10 December 2012 - 12:08 PM
Posted 10 December 2012 - 01:42 PM
Love DAOC? Tryout my DAOC clone: https://dl.dropboxusercontent.com/u/8974528/VON_Dist.zip
Posted 10 December 2012 - 09:23 PM
Posted 11 December 2012 - 08:39 AM
Yes the windows timings will be out possibly by quite a margin as you say, but when you think about it that would make sense hence why I should be receiving a v-sync message that will cause the graphics system to flip its buffers so the actual frame timings shouldn't affect it. Your suggestion about updating the wheel based on time (which is how it should have been done in the first place to be honest!) is a good one, and something I shall be implementing on the next test. Thanks for the help.
I've noticed if you try for 60hz your delta time between frames is not always EXACTLY 0.016666666667f (many times not even within an epsilon of it), which isn't surprising as Windows makes no claim to be a real-time operating system.
One suggestion is to rotate the wheel by a number of degrees (or radians) that accounts for the delta time between this frame and last frame (i.e. multiply your rotation strength by delta time).
Yes the v-sync being overridden was one of my first thoughts and unfortunately that does not seem to be the case, at least I couldn't find any setting that might affect it. I did try a couple of tests with forced triple buffering, anisotropic filtering turned on and off etc. all to no avail. I should say the system only has the onboard graphics, hence why the only thing on screen pretty much is a textured quad that is being rotated. As for the FPS, our engine has the ability to display the FPS but perhaps that is giving me some false positives. I shall try forcing the FPS overlay of the directx device on it. I think that still works even using the release directx libraries.
The control panel for your graphics cards is probably set to override v-sync. Check it.
You can also print the FPS easily enough to the console once every second. That would be an easy way to determine what is happening.
Posted 17 December 2012 - 09:37 AM
GameDev.net™, the GameDev.net logo, and GDNet™ are trademarks of GameDev.net, LLC.