Main > Linux
32/64bit Groovy Arcade Linux LiveCD/Install
bitbytebit:
--- Quote from: dmarcum99 on March 31, 2011, 03:12:35 am ---I certainly appreciate all the help. :notworthy: Donation worthy without question. :notworthy:
Running these two games (mace & wg3dh), they're still running too fast. A few post ago you asked me to ssh in and get an output while the game is running. I did this again since I got a new xorg.sh file. I also attached the groovymame verbose info. This info is from wg3dh...and I had a ini set to 640x480x32@57.00
**note** as soon as I "tab" into the mame control panel, the game slows down....I almost dare to say that it slows to the correct speed.
--- End quote ---
Well it does look like it's now correctly setting up the xorg xrandr modelines, doesn't have the default ones anymore, and says it's choosing the right resolution. It is getting it from an .ini file, might remove that just to double check, but I don't think that matters. What percentage speed does it run at when you push F11? That might give some clue as to what refresh rate is really being used, oddly though I can't see where it wouldn't be working with the xrandr and mame output. Try to run with the monitor type 'cga' just to see, when forcing it to use strict 15khz resolutions. Also the bottom of the xrandr output is trimmed off, that part shows the xrandr view of what the vertical refresh is :) so double check that number and see that it's 57hz just to be safe.
dmarcum99:
Sorry for all the hastle.
I ran the game (wg3dh) and used the F11 key (I forgot about that function) and the game menu starts around 105 percent, but when the demo continues it goes anywhere to 200% to 245%. The same situation happens without the ini file.
I also ran the other game (mace) using F11, and it acts similar. The intro starts at 105% and then the demo goes anywhere from 142% to 195%
Another thing regarding the ini files. When I set them up at their native resolution (640x480x32@57.00) I'm expecting a full screen. This does not happen on both games. Instead, the screen gets squished. When not using an ini file, I had a larger picture, but same game speed results as when they were using the ini file.
I'll try the CGA monitor option later....at work now....gotta go!
YOU GUYS ROCK!!! :applaud: :applaud: :applaud: :applaud: :applaud: :applaud: :applaud: :applaud:
bitbytebit:
--- Quote from: dmarcum99 on March 31, 2011, 09:54:29 am ---Sorry for all the hastle.
I ran the game (wg3dh) and used the F11 key (I forgot about that function) and the game menu starts around 105 percent, but when the demo continues it goes anywhere to 200% to 245%. The same situation happens without the ini file.
I also ran the other game (mace) using F11, and it acts similar. The intro starts at 105% and then the demo goes anywhere from 142% to 195%
Another thing regarding the ini files. When I set them up at their native resolution (640x480x32@57.00) I'm expecting a full screen. This does not happen on both games. Instead, the screen gets squished. When not using an ini file, I had a larger picture, but same game speed results as when they were using the ini file.
I'll try the CGA monitor option later....at work now....gotta go!
YOU GUYS ROCK!!! :applaud: :applaud: :applaud: :applaud: :applaud: :applaud: :applaud: :applaud:
--- End quote ---
Using fvwm as the window manager, run the program `glxgears` and see how fast it runs. Basically it should follow vsync and run at 57hz or fps, if not then it's your cards vsync that isn't working for some odd reason. See what message it prints to the xterm, and if it says it's following the framerate or not.
dmarcum99:
I'm not sure that I'm using the right syntax. How do I tell the program to run at 57hz?? I'm at the terminal and I type 'glxgears -geometry 640x480x32@57.00'
It's outputting 60.034 fps....???
bitbytebit:
--- Quote from: dmarcum99 on March 31, 2011, 07:24:42 pm ---I'm not sure that I'm using the right syntax. How do I tell the program to run at 57hz?? I'm at the terminal and I type 'glxgears -geometry 640x480x32@57.00'
It's outputting 60.034 fps....???
--- End quote ---
It doesn't take args, but that just confirms that vsync does work for your setup. Its odd since all looks technically good in the logs and settings from what I can tell. Has to be something else going on but not sure what it is.