MAME Error Messages (Joystick left and right)

[brownicus15]

Does anyone have a custom compiled MAME that avoids these error messages?  OR does someone have the ability to literally explain to me as if I was 5 years old how to compile my own?

[JDFan]

The one I'm using currently for 0.149 romset -- [ROMsite redacted]

[BadMouth]

.......just don't post in a forum asking why a game isn't working when there is supposed to be a giant red box there to tell you why it doesn't work

If you have an issue, always test it with the official MAME build before complaining or asking for help.

[JDFan]

.......just don't post in a forum asking why a game isn't working when there is supposed to be a giant red box there to tell you why it doesn't work

If you have an issue, always test it with the official MAME build before complaining or asking for help.

^^ Very good advice !! -- If you are removing the warnings about problems with certain games be sure to check if there is a warning about the problem before complaining that something is wrong.

[Generic Eric]

5 year olds aren't expected to compile mame.  I'll try to link the tutorial I used later.

In the meantime you may consider googling how to compile mame.

[yotsuya]

I just rolled my own this afternoon! 

[SegaOutrun]

yea its called nonag. I cant link it because its against mame policy but a google search for nonag will turn up what you are looking for.

for example im using MameUI 0.155 64 bit nonag-cave-dinput-hiscore

Mameui=mame with gui
64 bits=optimized for 64 bit OS
nonag= no warnings
cave= driver for cave games (although I think its in by default in regular mame now
Dinput= Dinput controllers (i use some fightstick and dinput steering wheel)
hiscore= saves your highscores

[B2K24]

What's so difficult about moving the joystick left and right?

[JDFan]

What's so difficult about moving the joystick left and right?

It's not that there is any difficulty in doing it - It's more that it breaks the ambience of the system - you go through all the trouble of setting up your front end etc. to make the experience immersive and responsive and then every game (or almost every game) you get a message that some parts of the emulation is not 100% that reminds everyone the system is using an emulator and making new users think there is a problem with the machine even though in most cases (esp. if you set it up with only working games that may have a minor sound issue etc. but nothing game breaking) no one except an enthusiast of that particular game would notice any issue.

Why not just have a toggle setting in the options to turn it off\on that could be used when troubleshooting rather than have the nag screen so prominent (even if it is on by default) - I realize they have it there to cut down on complaints\ issue logs on their forums but in my opinion they probably actually increase the questions by having games that most would see as fine throw up a screen saying there is issues with the emulation causing people to go to the forums looking for a fix to the problem they were warned about. 

[Louis Tully]

.

[Thenasty]

I just rolled my own this afternoon! 

I need a hit. You wanna share ?   

[yotsuya]

I just rolled my own this afternoon! 

I need a hit. You wanna share ?   

MAME 156. My Romset is 146, tho. 

[MKChamp]

I just rolled my own this afternoon! 

I need a hit. You wanna share ?   

MAME 156. My Romset is 146, tho. 

I think you may have misunderstood :-)

[Haze]

these 'no nag' builds are causing problems yet again tho..

i'm seeing lots of people trying to play 'zero team' in MAME, and then wonder why it's half broken when we've said it works.

I did some digging, and in every case they've disabled the warning screens with no nag patches, or downloaded builds with them hacked out, so don't get the message telling them that they're meant to be running New Zero Team or Zero Team 2000.

Makes me sad that people are so determined to hack out or turn off what are in reality very important warning screens, they're there for a reason, we ask people to not turn them off in builds that get distributed, yet it continues to happen, and causes all sorts of problems.  I don't buy the 'seamless cabinet' argument either, you're going to especially want to know if there are problems with the game being emulated if you're sticking it in a cab.

I don't know if people really think they're helping by distributing these patches and patched builds, but they're actually doing an incredible amount of damage and causing people to have a sub-par MAME experience.

[Grasshopper]

these 'no nag' builds are causing problems yet again tho..

i'm seeing lots of people trying to play 'zero team' in MAME, and then wonder why it's half broken when we've said it works.

I did some digging, and in every case they've disabled the warning screens with no nag patches, or downloaded builds with them hacked out, so don't get the message telling them that they're meant to be running New Zero Team or Zero Team 2000.

Makes me sad that people are so determined to hack out or turn off what are in reality very important warning screens, they're there for a reason, we ask people to not turn them off in builds that get distributed, yet it continues to happen, and causes all sorts of problems.  I don't buy the 'seamless cabinet' argument either, you're going to especially want to know if there are problems with the game being emulated if you're sticking it in a cab.

I don't know if people really think they're helping by distributing these patches and patched builds, but they're actually doing an incredible amount of damage and causing people to have a sub-par MAME experience.

The point is that a warning message is important and useful the first time you see it. However, once you're aware that a given game has problems, the warning message becomes pointless and annoying.

It does seem daft to me that the standard MAME build doesn't include a config file option to disable warning messages for specific games.

[JDFan]

While I can see the need for the notifications and can see where removing them and distributing builds that have it removed can cause the devs headaches - I would think that providing a setting to disable them in the official build would be a better choice for everyone - since many people are going to disable them at least by having it as an option in the official build troubleshooting could be simpler if the user could be told to reenable the setting as a first step - making educating the users much easier than it is currently if they are using a build that has had them removed since there is no setting in the official build to turn them off.

Figure if the devs were to put a setting in to disable them, they could also include checking the setting and ensuring it is enabled and displaying prior to reporting a problem as part of any troubleshooting advice - saving them the headaches that using an unofficial build with it removed causes.

[Haze]

I'm sorry, I can't agree.

We only show the initial disclaimer the first time any game is launched, yet people still hack that out.

We show the warnings every time because they're important.

Having the warnings disabled serves no good purpose, and too many people would just disable it once as part of their initial setup, then report errors to us.  (and we've noticed people usually upgrade MAME by dropping a new exe in the old folder, meaning they could have set it year ago and forgotten about it)

The only solution I can see is that if we provide a option we also DISABLE any games that would have any warning screens if that option is enabled, but I'm 99% certain if we did that people would just distribute patches to re-enable them instead.

All I can ask is that people stop distributing such changes and builds containing these changes, making them easier and easier for people to apply (which is what we've seen over the last year, to the point where it almost is just an option for people) is causing more and more problems.

[eds1275]

I'm sorry, I can't agree.

We only show the initial disclaimer the first time any game is launched, yet people still hack that out.

I'm with you. I'm under the impression that if you are smart enough to compile your own you should be able to do some basic troubleshooting and solve 99% of problems yourself because likely you are the one that caused them.