Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: jmad18 on December 12, 2013, 01:45:25 am
-
(http://i.imgur.com/s9zEO6i.png?1)
http://imgur.com/s9zEO6i (http://imgur.com/s9zEO6i)
Please refer to the picture. In certain games (such as Rompers) an error message will pop up on the bottom during gameplay.
Initially, I thought that "UI Display Comment" would have something to do with it, but it doesn't seem to do anything.
I looked in the main INI file and there is nothing related to this either.
Unfortunately, I don't know the first place to look in the source code in order to remove this.
Do you know how to remove this in the source code, or at least where it's located? I don't mean to remove the entire function, but rather I just want to prevent MAME from displaying the messages.
-
It's the popmessage in machine/namcos1.c
however you should probably be reporting it to Mametesters, it could be indicating there is an unhandled protection case at that point, so the game might not even be behaving 100% correctly; that's why it's there!
-
Oh, I see. I was looking in all the wrong places (src/emu specifically). I didn't know that the popup messages were handled individually per game.
There wouldn't be a global method of removing popup messages completely, would there?
-
Oh, I see. I was looking in all the wrong places (src/emu specifically). I didn't know that the popup messages were handled individually per game.
There wouldn't be a global method of removing popup messages completely, would there?
unfortunately while I'm sure somebody will post something this is exactly the type of patch we don't want people applying
those message provide useful information, and can give serious indications of when something might be wrong during the actual emulation execution. hiding them globally benefits nobody and only hinders the bug reporting process. ie it's the sticking your head in the sand solution, although people here seem fond of that....
if messages like this come up then they should be reported, if they're harmless then the devs will disable them on a per-case basis, or fix the bug. (or at least acknowledge the case reported, hide the message, and make a log of it in the source for future reference)
-
I was able to successfully reproduce this reported issue so I submitted a report for it.
http://mametesters.org/view.php?id=5394 (http://mametesters.org/view.php?id=5394)