Mame 0.116u1 and GameEx 8.16 prob

[Lord Zog]

Since upgrading to MAME/MAME 32 0.116u1, the warning screens come on saying to enter "OK" then the system info. 0.116 worked fine. Anyone else having this prob and a way to do it automatically by a script or so if anyone else has this prob. Only started after upgrading to 0.116u1 this afternoon. Thanks!

[Tom Speirs]

I just had an email from Headkaze. From what I undesrtand this will affect "everyone". They've implemented multiple keyborad suporrt in MAME.

Not quite sure what to do for now.

[Brian Hoffman]

I just had an email from Headkaze. From what I undesrtand this will affect "everyone". They've implemented multiple keyborad suporrt in MAME.

Not quite sure what to do for now.

U2 version is released..maybe its fixed?

[Lord Zog]

Nah. Still does it. Woot.

[headkaze]

I've been running tests with 0.116u2 and currently there is no way to send keys to it because it has changed it's input system to use RAWINPUT. The reason they did this was to support multiple keyboards as input. This is also going to cause problems with IPAC's, HotRod's, X-Arcades, keyboard hacks etc. etc. Because every keyboard plugged into Mame will be treated as a separate device. This issue was first raised on BYOAC and I encourage people to voice thier concerns. There is a challenge that the majority of Mame users don't give a toss about cab builders, and lets face it multiple keyboard support sounds good to the average Joe running Mame on a PC. I think multiple keyboard support is something worth having in Mame, but it would be nice to be able to turn it off. Also right now this breaks GameEx's ability to skip disclaimer and pause Mame while you view your CP. It's also messing with my CP Viewer program and caused me to waste a whole night trying to figure out how to fix it. To no avail unfortunately.

You can read more about it @ http://www.mameworld.info/ubbthreads/showt...p;Number=114434

[bkenobi]

I don't understand what the problem is at the moment. This issue only occurs in 0.116u#, which is an incremental test release. This release is not ready for people to use as their primary build, so why are you guys all using it. Wait a couple weeks or so and the bugs will (hopefully) be worked out with 0.117. Yes, this may become an issue, but the version of MAME you guys are running is not really a supported version by ANYONE!

[headkaze]

I understand that bkenobi but I'm just preparing for the worse case scenario. I don't use the u* releases myself but the RAWINPUT code might be put into 117, it's hard to say right now if it will or not. It's not the end of the world, but it will be annoying to have to figure out ways around it.

[Lord Zog]

I play with the u builds just cause I work with some of the drivers and it's nice to see whats been changed in them. Other than that, I usually stick to the original root builds, but, I wanted to see the progress of cps3.c from Haze as well.

[bkenobi]

Yeah, I didn't see that the new CPS3.c was being compiled into the u builds. That makes sense why the general public might be interested. But, the problem is that developmental builds are always buggy. And that's true HK, the MAME devs may leave the new system in place if they can get it working. Anyway, sounds like a pain, but all new "features" could be considered bad when it requires going back and changing tons of code when nothing has been implemented for it yet .

Fortunately, HK is on the case! So it's really just a matter of time before he and Tom sort it out. Good luck guys!

[eXo]

I struck gold.

In mame32 .116u2, goto

default game options -> misc

and check Skip Game Info.

It bypasses all the warning screens.

[katuuuz]

I struck gold.

In mame32 .116u2, goto

default game options -> misc

and check Skip Game Info.

It bypasses all the warning screens.

in my case you are wrong. it does bypass a few, but the 'type ok" screen is still there upon the first launch of a game. meaning if i open street fighter 2 for the first time, i'm prompted to type "ok". upon exiting and reloading the same rom, i'm not. i don't know about you but i'm not going through my full rom set and pressing ok for the first go.

will going back to the previous build solve this issue? because i'm ready to do so if it will.

[eXo]

in my case you are wrong. it does bypass a few, but the 'type ok" screen is still there upon the first launch of a game. meaning if i open street fighter 2 for the first time, i'm prompted to type "ok". upon exiting and reloading the same rom, i'm not. i don't know about you but i'm not going through my full rom set and pressing ok for the first go.

will going back to the previous build solve this issue? because i'm ready to do so if it will.

ya, dropping back before 0.116 will get rid of it.

And your right, it does retain the "press ok" stuff - I just didn't notice it because I've played most of my roms at least once before.

ah well.. at least it gets rid of a few of the screens.

[bkenobi]

ya, dropping back before 0.116 will get rid of it.

And your right, it does retain the "press ok" stuff - I just didn't notice it because I've played most of my roms at least once before.

ah well.. at least it gets rid of a few of the screens.

So if it only does this for new roms (ones you haven't played yet), there are 2 options.

1) Turn on the machine in screen saver mode and let it run for a LONG time. Probably set the time to switch games to the minimum time (~1 minute or so). Make sure you have an older version of MAME installed (pre 0.116).

2) Keep a keyboard handy for the next few weeks so that any new games can be dealt with.

3) You can also use the left/right movement on the joystick instead of pressing ok. I don't know if this will work with your cab's config as I don't know if you have a joystick (could be just a trackball or spinner potentially).

4) Just stick with an older version of MAME (pre 0.116) for a while until this is sorted out.

I'll probably use option 4 since my roms are only up to date to 0.115 anyway.

[Tom Speirs]

I thought of this a while back, but one way would be to write a small .net app that goes through all games on an older MAME version and bypasses the disclaimer.

I could code this but am a little busy. Perhaps Headkaze might want to do it for the general good?

[Tom Speirs]

Sod it, coding it now, quick and dirty.

[Tom Speirs]

Here you go.

This app will go through each mame game and bypass the disclaimer, so on future runs is shouldnt ask (in theory).

Instructions:

Place the app in the gameex folder

Use the same version of MAME in GameEx and update the list

run the app

Set mame version exe

set rom folder

Click go.

BypassMAMEDisclaimers.zip

[Tom Speirs]

Here you go.

This app will go through each mame game and bypass the disclaimer, so on future runs is shouldnt ask (in theory).

Instructions:

Place the app in the gameex folder

Use the same version of MAME in GameEx and update the list

run the app

Set mame version exe

set rom folder

Click go.

Folks, be sure to let me know how this works out. If so I'll improve on it..

[bkenobi]

I'm sure this will work, but I have a question. What is being modified when this is done? If we can figure out what file is being changed and how, perhaps we could just eliminate having to open the roms in mame. Maybe that's what you're doing already and if so, GREAT!

[headkaze]

Hey Tom all the app has to do is generate an empty xml file for each game in the cfg folder. Once there is a [rom].cfg for the game it will not show the disclaimer. No need to run Mame.

[Tom Speirs]

Hey Tom all the app has to do is generate an empty xml file for each game in the cfg folder. Once there is a [rom].cfg for the game it will not show the disclaimer. No need to run Mame.

Maybe I should just have GameEx do that then before launching? That definitly works??

[headkaze]

Maybe I should just have GameEx do that then before launching? That definitly works??

It definately works, it's been a known method to skip disclaimer for a long time you just generate an empty cfg file for each game. You could have GameEx check if the cfg for the game exists and generate one before it runs if it doesn't. It won't skip the other messages, but now it seems they have added an option to turn those off.

[bkenobi]

Then problem solved, right (for now anyway)?

[Tom Speirs]

Then problem solved, right (for now anyway)?

Not solved, improved. Or at least will be when I code the file creation into GameEx.

[Tom Speirs]

It definately works, it's been a known method to skip disclaimer for a long time you just generate an empty cfg file for each game. You could have GameEx check if the cfg for the game exists and generate one before it runs if it doesn't. It won't skip the other messages, but now it seems they have added an option to turn those off.

-skip_gameinfo has been an option in MAME for a long time BTW. Its the -skip_disclaimer that was removed.

The only remaining screen that wont skip is the third ok screen in mame when emulation is not accurate. IMHO not a problem though, I really dont see the point of playing games that don't work.. Only thing is it also shows for imperfect games such as Galaga (although maybe galaga is perfect now).

[Stu1983]

Maybe I should just have GameEx do that then before launching? That definitly works??

Yeah I left your app running all night and all that has changed in my MAME directory is I now have tons and tons of cfg's in the cfg directory

Stu