|
Why do some games run slow and jerky?
Hello
I have a modern, one year old PC with lots of memory, etc and Fedora Core 1#/Gnome installed. However, I've had this problem on other computers as well and I swear I can't figure it out. What is going on is that when I try to run Tux Racer, FooBillard, Flight Gear and a few other really popular Linux games, they run very slow and jerky and there's this long delay when I try to move the cursor or when a prop in the game moves. I think someone mentioned something about needing to download OpenGL but I'm not sure if there is a version of this for Fedora or even where I would find an easy-to-install RPM for it. Could it be my graphics card?. Do I need a super-powerful one to run these games or maybe just upgrade my graphics card drivers?. I just have no idea. Please help me if you can and thank you!! |
If you would list some of your pc specs that would help. Overall it sounds like you need to install the proper video/opengl drivers for your video card. Provide more information and hardware specific and more advice and help can be provided.
|
Post your graphics card. To test your 3d performance, run the following in a console:
$ glxgears A window will popup with some spinning gears. Let it run for a while and you will get a printout of your fps in the console. Post that as well. |
Hey, thank's for the speedy reply!:)
Ok, there's a sysinfo command for Linux that displays all your system specs at a glance in the terminal but I forgot what it is. If I can get that info I'd display it here because I'd like to know myself (especially what graphics card is in this thing). The other info (and it just keeps going and going so I had stop it) is ... [freddy@localhost freddy]$ $ glxgears bash: $: command not found [freddy@localhost freddy]$ glxgears Xlib: extension "XFree86-DRI" missing on display ":0.0". 654 frames in 5.0 seconds = 130.800 FPS 842 frames in 5.0 seconds = 168.400 FPS 1224 frames in 5.0 seconds = 244.800 FPS 918 frames in 5.0 seconds = 183.600 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 918 frames in 5.0 seconds = 183.600 FPS 995 frames in 5.0 seconds = 199.000 FPS 1071 frames in 5.0 seconds = 214.200 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 1066 frames in 5.0 seconds = 213.200 FPS 918 frames in 5.0 seconds = 183.600 FPS 994 frames in 5.0 seconds = 198.800 FPS 1071 frames in 5.0 seconds = 214.200 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS 995 frames in 5.0 seconds = 199.000 FPS 994 frames in 5.0 seconds = 198.800 FPS And when I stopped it... X connection to :0.0 broken (explicit kill or server shutdown). [freddy@localhost freddy]$ Hope this helps. These games are so cool but I have never been able to play them. Thank you again! |
Those fps really suck. No wonder your games aren't running well. Try running this in a console:
$ lspci It should give a printout of everything on the pci bus including your graphics card. Post the output here. We need to know your graphics card to give any meaningful help. By the way, the "$" is just the prompt for an ordinary user; you don't include that in the command but I guess you figured that out. When in a console as root the prompt will change to "#". The convention is to use either "$" or "#" to let people know if they need to be root to run the command or if you can run it as an ordinary user. |
Ok, I tried it and I'm getting this...
[freddy@localhost freddy]$ lspci bash: lspci: command not found [freddy@localhost freddy]$ |
Try this :
$ /sbin/lspci This is the command for Redhat 9, it's probably the same. |
Quote:
VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] So now what do we do? |
well i dont know about Fedoa but Suse does not enable 3D support for the graphics card by default...so maybe you will have to go through the config utility of fedora and enable 3d acceleration...for this you will need to have your graphics card drivers installed.....now i dont know much about the card u listed above...so u should probably try googling about it to find out the driver it uses...once u have done that issue this command as root:
lsmod see is the module name in the driver is present in the list displayed after the above command....if it is...then you are good to go....enable 3d and play....else you will probably have to install the drivers,etc. good luck |
You have a via motherboard with integrated graphics. Did a little googling and can see that this mb/chipset is problematic in linux. There seems to be some trouble enbling the agp bus. Saw this work around in one forum. Try running the following:
$ su <enter your root password> # modprobe agpgart agp_try_unsupported=1 If the module loads OK(i.e. no error messages with the above), then run glxgears again: $ glxgears See if you get any improvement in your fps. |
Quote:
[root@localhost freddy]# modprobe agpgart agp_try_unsupported=1 bash: modprobe: command not found [root@localhost freddy]# I also went into my Fedora control panel settings where it say's "configure video card" and all I get is a way to change to a different card but not actually configure the one that is currently installed. Is there some other (easy) way to do this? |
You have yet to post what graphics card you have
|
Quote:
VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] UPDATE: I just installed a Voodoo 3 graphics card. Fedora configured it automatically and it works but I'm STILL getting the slow and jerky gameplay...ahhh!!! |
Try doing /sbin/modprobe instead of modprobe. Keep forgetting you don't have /sbin in PATH so you have to designate the full path to the command. I always found that to be one of the annoying things about redhat.
It's a motherboard problem from what I've found using google. No matter what card you have in there, you have problems enabling agp. |
Unless you can find hardware accelerated drivers for either of this video devices, you will have crappy performance. By hardware accelerated, for example, the nvidia.com drivers they distribute that allow for open gl, etc.
|
| All times are GMT -5. The time now is 05:55 PM. |