Main > Linux
32/64bit Groovy Arcade Linux LiveCD/Install
dmarcum99:
--- Quote from: bitbytebit on March 31, 2011, 07:52:16 pm ---
--- 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.
--- End quote ---
Is this program supposed to run @ 57hz by default? I just figured that the fvwm is running @ 60hz and running the program verifies it. Should I run the wg3dh program and then remote in and try to run glxgears?
bitbytebit:
--- Quote from: dmarcum99 on March 31, 2011, 08:04:50 pm ---
Is this program supposed to run @ 57hz by default? I just figured that the fvwm is running @ 60hz and running the program verifies it. Should I run the wg3dh program and then remote in and try to run glxgears?
--- End quote ---
Yeah try to remote in, use the same DISPLAY=:0.0 on the command line for it. It runs at whatever the screen modelines refresh is.
dmarcum99:
--- Quote from: bitbytebit on March 31, 2011, 08:26:56 pm ---
--- Quote from: dmarcum99 on March 31, 2011, 08:04:50 pm ---
Is this program supposed to run @ 57hz by default? I just figured that the fvwm is running @ 60hz and running the program verifies it. Should I run the wg3dh program and then remote in and try to run glxgears?
--- End quote ---
Yeah try to remote in, use the same DISPLAY=:0.0 on the command line for it. It runs at whatever the screen modelines refresh is.
--- End quote ---
I used DISPLAY=:0.0 glxgears and it reported 57.022FPS
I am going to try the onboard video (ati4200) again and see if that help any. I don't believe I tried it after you gave me the new xorg.sh file
bitbytebit:
--- Quote from: dmarcum99 on March 31, 2011, 08:49:51 pm ---
--- Quote from: bitbytebit on March 31, 2011, 08:26:56 pm ---
--- Quote from: dmarcum99 on March 31, 2011, 08:04:50 pm ---
Is this program supposed to run @ 57hz by default? I just figured that the fvwm is running @ 60hz and running the program verifies it. Should I run the wg3dh program and then remote in and try to run glxgears?
--- End quote ---
Yeah try to remote in, use the same DISPLAY=:0.0 on the command line for it. It runs at whatever the screen modelines refresh is.
--- End quote ---
I used DISPLAY=:0.0 glxgears and it reported 57.022FPS
I am going to try the onboard video (ati4200) again and see if that help any. I don't believe I tried it after you gave me the new xorg.sh file
--- End quote ---
So it's just certain games that do this, or all? I'm going to have to look at this since I in theory should be able to reproduce the issue here. Does that game do resolution changes? That could be a part of the problem if so. Seems like the video card is probably ok, it seems to be centered around the actual running of mame and either resolution switching or it's not setting up vsync right. I'm guessing more likely the game and/or resolution changing, also do you have the monitor=d9800 sections in mame.ini? Your using a d9200 or d9800? The log files are each different from mame, once you had the .ini file in use it's stuck at 640x480@57 but the game may want to change resolutions, try to remove the .ini file for the game too and let groovymame do it, since it should be able to figure it out and that's possibly causing some issues I think (since when setup in an .ini file it no longer will change resolutions). I'm looking at that game here too in a bit, will see what I can find and if I can reproduce the issue.
Update:
Yeah it does the same thing here, and it does change resolutions to 512x256x57.00 actually. Does it work in Windows, and really at vsync or just throttling there or with triplebuffer? I'm guessing this is an issue with this and probably other games in mame that switch resolutions and possibly wanted different refresh rates but of course it seems mame doesn't help us out (at least that I know of) with knowing the new refresh rate. Would be interesting to really figure out though what it wants, do you have verbose logs of it working with groovymame in Windows properly, or regular mame? That would be interesting to see.
dmarcum99:
At first I thought I found a bug and wanted to help you out by testing them. That's why I kept posting... Then we found out that my setup was skewed a bit and you got that sorted.
The problem is only with a couple of games I found. I've tried maybe 200 roms and those two games (mace.zip & wg3dh.zip) were the only ones I spotted. I feel much better that you were able to reproduce the symptoms. I deleted the ini files and even tried the throttle setting in a new ini file and it still ran 200%.
I haven't hooked up my XP hard drive for a couple of weeks, but I can hook it back up to see if the same problems exist in windows. This linux setup is so sweet I can't believe this thing hasn't went viral yet.
My mobo must be doing something....no matter what I try I can't get my pci ATI 9250 to work with the 64 bit Groovymame live cd. It works great in windows...just cant get past the setup screen on the live cd...? I don't feel so bad cause the ati 4350 is working fine.