Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: mrclean on January 09, 2008, 12:00:46 am
-
ok for starters other games are fine.. aparently thus far "bubble bobble" all different versions of the game won't load with the ultimarc u360 sticks from my front end MaLa... I get to the MAME Warning, to type on OK or move the joystick Left/Right ... which works on everyother game but this one aparently.. however i need to manually type in OK on my keyboard for the game to load and then once the game is loaded my U360 for Player 1 doesn't work at all.. but player 2 joy works... I'm not having any other problems with any other games (*that I know of) is there a fix / or a work-around for this issue using MaLa and u360's Im stumped
-
Map your Ultrastik left/right inputs (JOYCODE_1_LEFT / JOYCODE_1_RIGHT?) to UI_LEFT and UI_RIGHT in your MAME ctrlr file.
MAME probably has only left/right cursor keys mapped to these inputs.
-
yup you'll have to remap the joystick on player 1 as if it were your arrow keys on the keyboard.
-
I went to my ctrl folder and saw 4 settings one for hotrod,slickstick,hotrodse,and xarcade.. now im not sure exactly what i need to do to create a new one for the u360
-
I had a problem with my trackball control panel since it had a trackball and two buttons. I couldn't make button 1 left and button 2 right also, because that effected the game.
So I made button 1 an 'O' and button 2 a 'K' and went with it. It was a bit annoying for the keyboard encoder, but not that big of a deal. I just couldn't use the defaults.
Oh, you can also use a mame build that removes them.
-
you can program your ipac japc or mini pac to make the joys whatever you want them to also by running a game and pressing tab on the keyboard you can change your new assighned input to each specific game or all the games your choise.
-
I had a problem with my trackball control panel since it had a trackball and two buttons. I couldn't make button 1 left and button 2 right also, because that effected the game.
Maybe it was different back then :dunno, but...
UI_left & UI_right do not effect the gameplay, and it's these two that mame looks for to get past the "OK" screen, not the gaming left & right (p1_left & p1_right that would effect play). Maybe the confusion is just that UI_left is usually mapped the same as p1_left, and ditto with rights.
-
UI_left & UI_right do not effect the gameplay, and it's these two that mame looks for to get past the "OK" screen, not the gaming left & right (p1_left & p1_right that would effect play). Maybe the confusion is just that UI_left is usually mapped the same as p1_left, and ditto with rights.
[/quote]
I'm still confused as to HOW TO set it up?
-
UI_left & UI_right do not effect the gameplay, and it's these two that mame looks for to get past the "OK" screen, not the gaming left & right (p1_left & p1_right that would effect play). Maybe the confusion is just that UI_left is usually mapped the same as p1_left, and ditto with rights.
I'm still confused as to HOW TO set it up?
Start game, press tab, select "Input (general)", select "User Interface", find "UI Left", press enter, move stick left, (wait until mame writes joy left), repeat for "UI Right", esc.
A little more info a mame's FAQ (http://mamedev.org/devwiki/index.php/FAQ:Controls#How_do_I_configure_the_keys.3F).
-
Start game, press tab, select "Input (general)", select "User Interface", find "UI Left", press enter, move stick left, (wait until mame writes joy left), repeat for "UI Right", esc.
I know how to do thats, however.. not working! MaLa won't Map my U360 sticks properly.. I can't even get into MAME period only on certain specific games, Now Galaga, and bubble bobble ive noticed. majority works but these are messed up :dunno
-
download headkaze's mame compiler .. the mame source .. and edit ui.c, put two slashes ("//") in front of the ui_* dialog box calls and compile. done :)
-
I downloaded the compiler, and i found the ui.c file to edit.. but im unsure exactly where im editing can you be more specific
-
go into ui_display_startup_screens() in ui.c
and comment out the ui_set_handler() calls ...
really you can just put /* ..... */ around case 0 and case 2 IIRC ... basically there is a ui_set_handler() call with handler_messagebox_anykey and another one with messagebox_ok .. those are calling the screens up that ask you to hit "any key" or "OK" (left/right) to continue. i comment that stuff out...
i also tend to grep the code for all those Initializing... Loading... Decoding.. Decrypting... etc msgs and disable those too. i prefer that it goes directly to the game without any start up shennanigans to "reveal the man behind the curtain."
also while you are in there you might as well try some fun options in the Makefile
for a core 2 duo i was using
-march=nocona -mtune=nocona -minline-all-stringops -maccumulate-outgoing-args -mmmx -msse -msse2 -msse3 -mfpmath=sse -funroll-loops -fomit-frame-pointer
you could change the march/mtune for another CPU ... and remove whatever level of SSE is not supported.
anyways..if you edit that ui.c stuff you will at least be forever free of those silly start up confirmations that dont belong on a cabinet anyway.
i dont mind so much the one showing technical details like resolution. but the press OK is rather annoying, i must say.
so you could leave the handler_messagebox_anykey one .. and comment the ok one .. or at least change it to handler_messagebox_anykey if you dont mind it so much and want to keep the disclaimer :)
-
ah im still confused ... i need to figure this out ! again if any one can still help me alleviate this problem please let me know
-
now Mario Bro's US player 1 won't work.. only player 2 whats the deal ?