Main > Software Forum
LEDBlinky - Arcade LED Control software and Animation Editor - v8.2
arzoo:
--- Quote from: DJO_Maverick on May 01, 2023, 04:42:46 pm ---So far I've tried with GroovyMame 0.253, 0.254, and normal MAME 0.254 (current). None of them are sending any output to the output test window.
And just to make sure I'm not crazy, this is what I've got at the relevant part of my mame.ini:
--- Code: ---#
# OSD OUTPUT OPTIONS
#
output Windows
#
# OSD INPUT OPTIONS
#
--- End code ---
Am I missing something obvious, before I start working backwards through a whole lot of builds?
Thanks,
--- End quote ---
That looks correct. Not sure what the issue is but I guess it could be something else specific to your system? I'll have to test .254 on my system to see if there's a bigger problem here.
arzoo:
--- Quote from: DJO_Maverick on May 01, 2023, 04:42:46 pm ---So far I've tried with GroovyMame 0.253, 0.254, and normal MAME 0.254 (current). None of them are sending any output to the output test window.
And just to make sure I'm not crazy, this is what I've got at the relevant part of my mame.ini:
--- Code: ---#
# OSD OUTPUT OPTIONS
#
output Windows
#
# OSD INPUT OPTIONS
#
--- End code ---
Am I missing something obvious, before I start working backwards through a whole lot of builds?
Thanks,
--- End quote ---
I've confirmed the mame output system is working with .249 which was the latest version I currently have installed. But I did notice that it only worked when the OSD OUTPUT OPTIONS "output" value was set to "windows" all lower case. My support doc had the value listed as "Windows" which does not seem to work with later versions of mame. Try using "windows" and let me know if that works for you with .254?
--- Code: ---output windows
--- End code ---
DJO_Maverick:
--- Quote from: arzoo on May 01, 2023, 11:34:56 pm ---I've confirmed the mame output system is working with .249 which was the latest version I currently have installed. But I did notice that it only worked when the OSD OUTPUT OPTIONS "output" value was set to "windows" all lower case. My support doc had the value listed as "Windows" which does not seem to work with later versions of mame. Try using "windows" and let me know if that works for you with .254?
--- Code: ---output windows
--- End code ---
--- End quote ---
That's exactly what it was, ha. Making it all lowercase fixed it, outputting as expected.
Thank you!
arzoo:
--- Quote from: DJO_Maverick on May 02, 2023, 08:58:35 am ---That's exactly what it was, ha. Making it all lowercase fixed it, outputting as expected.
Thank you!
--- End quote ---
Excellent! Sorry for the misdirection on the support page - it's been fixed.
DJO_Maverick:
So one odd issue I've run into in fine-tuning seems to crop up in some 49-way or analog games; taking Arch Rivals for example. Colors.ini designates the sticks as orange, and my otherwise not implicated P3 Button 2 (KEYCODE_G) lights up orange.
Sticks are mapped to U360 analog, properly. From the perspective of global input assignments and game input assignments visible within Mame, every reference to KEYCODE_G (other than P3 Button 2) has been deleted now, and nothing is mapped to P2 X/Y for any device other than the U360... yet the orange remains.
I checked the debug, and it has this relevant line on game load:
--- Code: ---[05/05/2023 23:37:28] P2_AD_STICK_X_EXT (MAME-DEFAULT): |JOYCODE_2_ANALOG_X|MOUSECODE_2_ANALOG_X|KEYCODE_G|JOYCODE_2_RIGHT
--- End code ---
Similar phantom string for Y_EXT, and both for P1 as well (just not mapped to anything with a light).
Yet when I go manually open up the Mame default.cfg, there isn't even a default port in the file for P2_AD_STICK_X_EXT. I can manually ADD an entry for it, and map it to none. If I do so, Blinky correctly previews the game with that rogue light off, and will load the game with it off that time... however, every time I turn on Mame, it automatically deletes any _EXT ports that I manually added... which results in the rogue light coming back after restart.
I can't tell if that input ID was deprecated at some point, or whether it is a Blinky or Mame issue. At this point, no doubt it would just be easier to just change from 'G' on the key encoder for that button and adjust accordingly, but now I'm just really curious where these seemingly uneditable defaults are coming from?