Roms run fine in MAME, but lagging in Hyperspin. Vsync related.

[bulbousbeard]

Yes you can either do it via commandline args or just make different MAME ini files for different games.

Say you want pacman to run differently. Just copy mame.ini to pacman.ini and set the ini however you want.

[magus90]

Yes you can either do it via commandline args or just make different MAME ini files for different games.

Say you want pacman to run differently. Just copy mame.ini to pacman.ini and set the ini however you want.

THanks man, that worked. Although i have one issue, i made an Ini for pacman, and it worked great, for pacman. But now when i play the other games that should be using the default MAME ini they are not using it. They are using the pacman ini.....i think.

If i make an ini for each game it seems to work, the rom uses those settings, but then whatever games are left out seem to not use the default ini like i thought they would. Does that just mean i have to make an ini for every single rom?

[Yenome]

I dont see how the refresh rate of the monitor is going to limit the speed your computer will run the game. using mame -bench switch turns off video output to the monitor but it still runs the game and gives a fps score.
I had read that HLSL is less of a resource hog than GLSL. even tho i use GLSL my self with lottes. Only issue i have with lottes it has a memory leak. when using lottes and doing a benchmark with mame it kicks back memory leaks. there is no reason anything pre 2000's will not run at 100% on your system. i use a weak amd athlon II x2. id suggest making a new folder and doing nothing to ini just add a couple roms. make sure it work fine. then add hyperspin to the mix. still using default setting for mame. dont even make an ini for it. if vsync is causing you issues i would say its more likely driver issues IMO.

[bulbousbeard]

> I dont see how the refresh rate of the monitor is going to limit the speed your computer will run the game.

Obviously you don't. It doesn't mean that you understand how it works.

If your monitor can run at a maximum of 60hz, how are you going to run a game that runs at 61hz at full speed with vsync on?

[Mr_Numbers]

There is HUGE debate online about whether refresh rates would affect PC performance, even if vsync is on.  It's not a bad question so please cite your source showing the impact it can have.  I tried looking this up and got scores of mixed answers.

> I dont see how the refresh rate of the monitor is going to limit the speed your computer will run the game.

Obviously you don't. It doesn't mean that you understand how it works.

If your monitor can run at a maximum of 60hz, how are you going to run a game that runs at 61hz at full speed with vsync on?

[Yenome]

> I dont see how the refresh rate of the monitor is going to limit the speed your computer will run the game.

Obviously you don't. It doesn't mean that you understand how it works.

If your monitor can run at a maximum of 60hz, how are you going to run a game that runs at 61hz at full speed with vsync on?

key point monitor.
in that case i see what your saying. but that still doesnt say your pc wont run it full speed. just the monitor wont display full speed. still not a limit of the pc. that is a monitor limit. thats like me getting 120fps in games when my monitor is only 60hz refresh. doesnt mean my pc aint pushing 120fps. which is why i just leave vsync on for my monitor since to me double the frame rate of the monitor refresh makes no diff that i see.

[zamboniguy]

Can I do this process below if I use mameiufx instead of mame? If so, how?  Thanks

MAME .159 supports CRT simulation via Direct3D and HLSL.

Last year, Timothy Lottes created a great CRT simulation shader, and it was ported to GLSL for SDLMAME by SoltanGris42. The problem is that SDLMAME is a pile of turd, because it has horrible audio latency and doesn't support the Raw Input API in Windows, so it had more input lag than Windows MAME.

Couriersud, one of the brilliant MAME developers, has been aligning the different video APIs that MAME uses as part of a larger effort to eventually GPU accelerate 3D games in MAME crossplatform.

Due to his work, you can now run the Timothy Lottes Shader in Windows MAME and still get the low latency Raw Input API and low audio latency of Windows MAME while getting the superior CRT shader. It really is the best of both worlds.

This is the new de facto setup for high quality MAME builds using LCDs.

WOW Couriersud is awesome.

Here's a build of the latest MAME source with the Timothy Lottes shader included and the ini already configured; all you have to do is change the ROM path to match yours, and you're done.

https://www.dropbox.com/s/g75np6v6ad9s5jy/mamesvn.zip

Here's a breakdown of the options you want in MAME's INI and why they're important:

sleep 0 -- If you enable sleep in MAME, you will get microstuttering. It is simply not reliable if you want perfect video.

audio_latency 1 -- This is the lowest latency audio setting in Windows MAME currently. The default, 2, sucks.

video opengl -- You need to use OpenGL to run the GLSL shader; this is a new option made available by Couriersud.

gl_forcepow2texture 1

gl_notexturerect 1

gl_vbo 1

gl_pbo 1

gl_glsl 1

gl_glsl_filter 0 -- If you enable filtering, you get a soft, ---smurfy--- picture.

glsl_shader_mame0 shader\Lottes_CRT -- This is where you tell it which shader to run (this is included in the archive).

I didn't change it in the INI because everyone's monitor is different, the chances are that you'll want to adjust the gamma setting to around 0.75 or so. It'll probably be too bright otherwise.

One more tip: Nvidia's OpenGL driver is buggy and has microstuttering unless you go into the Nvidia 3d settings and disable "Threaded Optimization" for this program (not that anyone other than me probably even notices).

So there you go: this is the best MAME has ever been on an LCD. You're welcome.™