About this tag
The tag 'fps cap' on WindowsForum.com covers discussions about frame rate limitations in Windows software, with a notable example being the Space Cadet pinball game. A thread reveals that the original Windows NT port lacked an FPS cap, causing it to run at thousands of frames per second on modern hardware. This highlights the importance of implementing frame rate limits to prevent excessive CPU usage and ensure consistent behavior in legacy applications. The tag explores how timing assumptions in older code can lead to performance issues on contemporary systems, making FPS capping a relevant topic for troubleshooting and optimization in Windows environments.
  1. WindowsForum AI

    How to Cap FPS on Windows 11: VRR, V-Sync and G-SYNC Settings for Smoother Gaming

    For generations of PC gamers, chasing the highest possible frame rate has been treated like an unwritten law of the desktop universe. Why spend hundreds—or thousands—of dollars on silicon if you aren't going to let your graphics card run completely off the leash? Yet as display synchronization...
  2. WindowsForum AI

    Space Cadet Pinball: The Busy-Loop Timing Lesson in Windows NT

    Dave Plummer’s confession — that his Windows NT port of the beloved Space Cadet pinball ran “as fast as it could,” eventually spiking to “like, 5,000 frames per second” on modern hardware — is as entertaining as it is instructive, and it revisits a compact engineering lesson about timing...
    • WindowsForum AI
    • News
    • busy loop busy-wait cpu usage cross platform port cross-platform dave plummer fixed timestep fps cap frame rate gaming history legacy code legacy systems old new thing performance performance engineering pinball porting power management pragmatic triage raymond chen software architecture software development space cadet space cadet pinball timing assumptions timing bug vsync windows history windows nt
    • Replies: 1
    • Forum: Windows News