MAME 173 No Nag?

[Guest]

Has anyone already done a MAME 173 compile with no nag?  The MAME Compiler app isnt showing 173 yet...

[potts43]

I wonder if 173 fixes the bugs in 172?

[rastan]

I wonder if 173 fixes the bugs in 172?

 

Hopefully because I went back to 171 because the problems with 172 were just too much for me to mess around with.... 

[potts43]

I need a raw version that uses two aimtraks. 172 didn't work but 171 did

[kylecp1979]

I don't know they don't mention much in the new features.

 

http://mamedev.org/history.html

 

I wonder if 173 fixes the bugs in 172?

[artman999999]

I compiled the new version and found it to be slightly slower than 172.  I felt like 172 had some advantages over previous versions (maybe it's my imagination), but 173 is about 1% slower when emulating Pink Sweets, Ibara, and MM Pork.  I realize these are demanding roms (unlike a pacman, for instance) and 1% doesn't seem like much.  But the 1% is a TOTAL average slowdown.  So even though most parts hum right along throwing 100% emulation into the average, when the screen gets busy the audio stuttering is really noticeable and the slowdown is unacceptable.  It was barely acceptable before.

 

Also, I finally figured out how to use BGFX and can get it to look like my preferred HLSL settings, but it seems even SLOWER than HLSL!  I'm sure someone will benchmark it and tell me I'm wrong.  But the three games above emulate (on my system) at 99% on mame v172 and 98% on v173 using HLSL D3D settings.  Using BGFX, the percentages drop by yet another whole percent (-1%) to 98% and 97%, respectively.  Playing a shmup with those levels becomes tedious at best.

 

I'll go ahead and post a no-nag 173, but I'm not a huge fan of it.

[artman999999]

Posted in the DL section. -A

[potts43]

What is bgfx? Is that the same thing as glsl?

[potts43]

Posted in the DL section. -A

Is this the raw version? If not it won't work with two lightguns which is what us guys use. Thanks very much.

[gigapig]

What is bgfx? Is that the same thing as glsl?

 

It's a new renderer which still uses HLSL but may be better for scaling and new effects, you can also set which DX version you are using.

 

I couldn't get it working in 0.172, maybe this one will work.

 

More info here.

[sevenseal]

Posted in the DL section. -A

did you use a diff file (mkchamp) to patch this compiled mame? just wondering because using that diff for 173 does leave issues.

its best hardcode the changes since all the file structure have been moved/changed.

hi-score is now built in Mame now, the patch is not required, just activated the plugin.

just my thoughts

[artman999999]

@sevenseal - Sort of.  The mkchamp diff was re-written by ozfalcon to be more efficient than even the .172 diff, and in theory should be even faster than before.  Rather than just suppress the messages, the new diff essentially bypasses the warning module as if it isn't even there.  I haven't seen any issues with 173 yet, so I'd be interested to hear more specifics.  As far as the built in hi-score lua script - Yeah, I hear you.  But this is only the second revision to have it included, and the current hi-score diff has been effective literally for years now - I won't give up on something I know works until I'm sure the new one is solid.

 

If you want to manually code out the no-nag, compile 173 64bit dinput and post the mame64.exe file on this thread, that would be awesome.  I would be very interested to see if there is a speed boost on a side-by-side comparison.  Posting the same version in the DL section will just confuse members and look strange.  Frankly, I began to compile because it was historically a hassle to get the nonag versions in a timely manner.  But if we have people with programmer-level knowledge (such as yourself) who are willing to do it quickly after a release, that's much better.

 

@gigapig - the BGFX slider settings are now more intuitive than before.  After it's selected in mame.ini, you can just fire up a rom, select slide controls, then select HLSL there and the slider menu will expand into what looks like a normal HLSL setup.  If you set THESE settings up to match your preferred HLSL settings, the screen will look like it did before BGFX was added.  But that leads me to ask - why jump through the hoops, then?  And I don't think those BGFX/HLSL settings are saved anywhere (yet).  

[artman999999]

Just had another thought - I never tried to run an UNPATCHED 173 beside an UNPATCHED 172.  I'll try that tonight.  Well, maybe tomorrow - it's Friday night, you know.  

[sevenseal]

https://onedrive.live.com/redir?resid=B589ED803582B702!2311&authkey=!AM6tm566FmeGjWk&ithint=folder%2c

 

those are my compiled mame and mameuifx...

unable to test them, i am only able to vnc into my server to do code from my cellphone

[bhudkins]

https://onedrive.live.com/redir?resid=B589ED803582B702!2311&authkey=!AM6tm566FmeGjWk&ithint=folder%2c

 

those are my compiled mame and mameuifx...

unable to test them, i am only able to vnc into my server to do code from my cellphone

 

Does your compile happen to be raw input? I also need raw input for the dual aimtraks.

 

I did notice as others have mentioned, 173 seems to be slower than previous versions. Was very noticeable in MK4

[sevenseal]

Does your compile happen to be raw input? I also need raw input for the dual aimtraks.

I did notice as others have mentioned, 173 seems to be slower than previous versions. Was very noticeable in MK4

yes they are

[Metalzoic]

The only problem I have with 172 is that I no longer have the ability to switch NEO-GEO games between MVS and AES bios. AES is no longer an option.

I didn't update to 173. Will probably wait until 174 or 5 depending on shader improvements.

The other weird thing with 172 is that Midway games look like they have too many lines of resolution when run with GLSL. Is that how they're supposed to be?

[sevenseal]

The only problem I have with 172 is that I no longer have the ability to switch NEO-GEO games between MVS and AES bios. AES is no longer an option.

I didn't update to 173. Will probably wait until 174 or 5 depending on shader improvements.

The other weird thing with 172 is that Midway games look like they have too many lines of resolution when run with GLSL. Is that how they're supposed to be?

i would say try out 173 and how it is, nrver know unless you try it?

[Metalzoic]

I'll wait. I read through the changelog the day it came out and it didn't add enough to shaders for me to go through the process of updating all roms, updating the entire MAME folder, re-building/creating 20 XMLs & genres for MAME & all manufacturer wheels etc...

Probably next version.

 

Does 173 have the AES bios switching back though?

[griffin518]

https://onedrive.live.com/redir?resid=B589ED803582B702!2311&authkey=!AM6tm566FmeGjWk&ithint=folder%2c

 

those are my compiled mame and mameuifx...

unable to test them, i am only able to vnc into my server to do code from my cellphone

 

Thanks for the uifx build! Really appreciate it.

 

Any idea why the binary is so big vs stock (128MB vs 87MB)? That's so odd and it's piqued my curiousity.

[bhudkins]

Still seems like dual lightguns isnt working in 173

[potts43]

Still seems like dual lightguns isnt working in 173

Thanks for that info![emoji1303]

[griffin518]

On the MAMEUIFX build I'm getting info screen pop-ups for things like "display isn't 100% accurate" (use galaga as an example). Is there a way to hide those? That's new since 0.171. I do have "skip game informations screen on startup" check in the UI configuration.

 

Also, does anyone know if high scores got sorted out?

[sevenseal]

well to be honest, probably have to do with my compile environment, probably didnt take one of my command making them

[sevenseal]

Still seems like dual lightguns isnt working in 173

depends on your setting you have in your mame.ini

mame 172+later...

directinput and raw are built together but has priority setting overall. but you can disable dinput.

do have joystick set to auto? should be set to none for lightguns...

make sure dual lightguns is unchecked, that opition always breaks the function of lightgun.

theres another setting to make sure but i cant confirm it right now.