Announcement

Collapse
No announcement yet.

Capping Frame Rate to Refresh Rate on a Intel GMA X3500

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Capping Frame Rate to Refresh Rate on a Intel GMA X3500

    My brother is trying to play some classic Unreal Engine 1 games on his Lenovo 3000 N200 laptop with an Intel GMA X3500 GPU but is having issues due to the fact the games are running to fast, making them amusingly unplayable. My desktop machine which has a Diamond Radeon HD 4670 does not have this problem as I am using the R600 Gallium3D drivers and they are capping the game's frame rate at my screen's refresh rate. So, even though my machine is more capable it is not playing the games too fast even though the weaker Intel is. Is there anyway to activate a smiliar functionality with the Intel drivers? He is running Fedora 17 with the stock drivers provided with the distribution.

  • #2
    You should be able to limit the frame rate in the game settings.

    I installed Unreal Anthology. This includes both Unreal and Unreal II. It also includes UT and UT2004, but those work fine. Both Unreal and Unreal II run way too fast. The flyby goes too fast, the briefing movie in Unreal II shows extremely fast animations, walking around is impossible because...

    Comment


    • #3
      That requires separate third-party renderers and I do not know if they work with the Linux versions of Rune or UT99, which are the games he is trying to play.

      Games are running fantastically on my radeon.

      Comment


      • #4
        Okay, the problem with UT99 seems strangely to have been with the sound. Got it working on proper OSS rather than ALSA OSS emulation using my little script here and it is fine:

        Code:
        #!/bin/sh
        #
        # OSS Startup Script
        # Created by Hamish Paul Wilson
        # July 23, 2012
        #
        # Move to /etc/profile.d/
        #
        
        modprobe snd-pcm-oss
        However, Rune is still going like a bat out of hell.

        Comment


        • #5
          Unfortunately that odd solution was in fact too odd - the actual reason it worked then was because we had Firefox open in the background. I would still like to find a better solution to this problem though.

          Comment

          Working...
          X