Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: GMZombie on December 31, 2005, 05:15:05 pm
-
how do i do that. i looked in the mame config file and it only had the option of not displaying the game info? i thought they got rid of the press ok to continue but i maybe was wrong?
-
They have a couple of warnings you can't disable without changing the code.
-
oh ok...does anybody know how to do that? eh its not that big of a deal i just wanted to upgrade my other machine and that didnt have them in it? didnt they used to have skip disclaimer in there..
-
It only displays once. Then never again.
Except for game warnings; those still display no matter what.
-
oh ok...does anybody know how to do that? eh its not that big of a deal i just wanted to upgrade my other machine and that didnt have them in it? didnt they used to have skip disclaimer in there..
In these functions just do a "return 0" after the local variable declarations.
int ui_display_copyright(mame_bitmap *bitmap)
int ui_display_game_warnings(mame_bitmap *bitmap)
int ui_display_game_info(mame_bitmap *bitmap)
-
Or change to these lines in mame.c
/* if we didn't find a settings file, show the disclaimer */
if (settingsloaded || options.skip_disclaimer || 1)
{
/* show info about incorrect behaviour (wrong colors etc.) */
if (options.skip_warnings || 1)
{
/* show info about the game */
if (options.skip_gameinfo || 1)
-
Just found this thread and used headkaze's method for disabling. After I compile, do I have to turn on any switches to make this happen, or did the lines I changed automatically take care of business for me? Thanks!
-
Just found this thread and used headkaze's method for disabling. After I compile, do I have to turn on any switches to make this happen, or did the lines I changed automatically take care of business for me? Thanks!
If you used his method then no, nothing else is needed. Just compile and things will be fine for you.
-
OK just re-compiled MAME with the changes, but still seeing the "OK" screen. If I set the "skip_gameinfo" to 0 I still see the game info as well. I changed these lines in Mame.c
Original:
if (settingsloaded || options.skip_disclaimer || ui_display_copyright(artwork_get_ui_bitmap()) == 0)
{
/* show info about incorrect behaviour (wrong colors etc.) */
if (options.skip_warnings || ui_display_game_warnings(artwork_get_ui_bitmap()) == 0)
{
/* show info about the game */
if (options.skip_gameinfo || ui_display_game_info(artwork_get_ui_bitmap()) == 0)
Changed:
if (settingsloaded || options.skip_disclaimer || 1)
{
/* show info about incorrect behaviour (wrong colors etc.) */
if (options.skip_warnings || 1)
{
/* show info about the game */
if (options.skip_gameinfo || 1)
Not sure what gives? Can anyone help?
-
OK just re-compiled MAME with the changes, but still seeing the "OK" screen. If I set the "skip_gameinfo" to 0 I still see the game info as well. I changed these lines in Mame.c
Original:
if (settingsloaded || options.skip_disclaimer || ui_display_copyright(artwork_get_ui_bitmap()) == 0)
{
/* show info about incorrect behaviour (wrong colors etc.) */
if (options.skip_warnings || ui_display_game_warnings(artwork_get_ui_bitmap()) == 0)
{
/* show info about the game */
if (options.skip_gameinfo || ui_display_game_info(artwork_get_ui_bitmap()) == 0)
Changed:
if (settingsloaded || options.skip_disclaimer || 1)
{
/* show info about incorrect behaviour (wrong colors etc.) */
if (options.skip_warnings || 1)
{
/* show info about the game */
if (options.skip_gameinfo || 1)
Not sure what gives? Can anyone help?
Hummm, you sure you are using the newly compiled version? :)
I would just open usrintrf.c and and modify the methods themselves.
Use MikeQ's method, that will do the trick:
In these functions just do a "return 0" after the local variable declarations.
int ui_display_copyright(mame_bitmap *bitmap)
int ui_display_game_warnings(mame_bitmap *bitmap)
int ui_display_game_info(mame_bitmap *bitmap)
-
Hmmm... not to interrupt your technical discussion because I am glad this is being documented somewhere but for many like myself that find compiling each version of mame cumbersome, here's an alternative.
I just ran a game at random then took the cfg that was generated and copied it to ..\cfg\<romname>.cfg for every rom I had using a bat file.
If you have any custom settings in a couple of your cfgs then make sure you do not over-write those particular games.
-
Hmmm... not to interrupt your technical discussion because I am glad this is being documented somewhere but for many like myself that find compiling each version of mame cumbersome, here's an alternative.
I just ran a game at random then took the cfg that was generated and copied it to ..\cfg\<romname>.cfg for every rom I had using a bat file.
If you have any custom settings in a couple of your cfgs then make sure you do not over-write those particular games.
What was your batch file? What did you use to generate the list of roms?