w00master

Thanks so much for your help. You're correct. You led me in the right direction. After your feedback, and learning about IfWinExist as well as those functions REQUIRING some sort of loop, this is what solved for me. Here's the revised script. This should work for anyone using Gun4IR and MAME: (Note: place below script in "Running Scripts" for your MAME Emulator in Launchbox.) Run, %COMSPEC% /C echo M3.1 > COM1 Run, %COMSPEC% /C echo M3.1 > COM2 SetTitleMatchMode, 2 loop { ifWinExist, ahk_class MAME { WinActivate ahk_class MAME WinActivate ahk_class MAME } Sleep, 100 } Return ~ESC:: Run, %COMSPEC% /C echo M3.0 > COM1 Run, %COMSPEC% /C echo M3.0 > COM2 ExitApp return Hope this helps anyone else! Edit: anyone wanting to use this script, the only thing you need to change in the above are the COM numbers for your Gun4IR. Beyond that, nothing else needs to be changed.

Thanks mate. Unfortunately, this doesn't work as well. However, (on the bright side), I did notice it working for me.... once. I moved the script to the top, however - the moment (I believe) the com commands go off, I lose focus. I tried moving that portion of the script further down, but this didn't take either. Appreciate the help - I'll keep digging. It's pretty assuredly something about executing the script (maybe it's the COM commands? Perhaps someone on here that uses Gun4IR"? Thanks!

So, I tried this out, unfortunately I'm still seeing the same issue. I really believe it's the AHK script that's taking priority over MAME. I'll post this on AHK forums, but any ideas? Thanks!

Sounds good. I do know my MAME instance is set to open full screen. I will check on the other one.

Thanks @JoeViking245!!! That did get rid of the warning console windows, but unfortunately I still have the "focus" window issue - game loads behind Launchbox, and have to alt-tab over. Here's a screencast of what happens: https://app.screencast.com/vSZAcybCMHFOC Am I SOL? LOL

Honestly confused on this. Never seen this type of error message before. It doesn't effect the playing of the game, but the error message always takes focus away from it so I end up having to "alt-tab" over to the game. This happens both in LaunchBox and BigBox. So here's what's happening. Anytime, I play Area 51 (for example) through Launchbox, I get this error (see screenshot). However, if I run the same rom directly in MAME, I don't get this window error. I believe it may have something to do with the running script I have (this script is standard for this game for anyone that uses Gun4IR): Run, %COMSPEC% /C echo M3.1 > COM1 Run, %COMSPEC% /C echo M3.1 > COM2 ~ESC:: Run, %COMSPEC% /C echo M3.0 > COM1 Run, %COMSPEC% /C echo M3.0 > COM2 ExitApp return The error message is only commenting on the bezel art. (But strangely, when the game loads the bezel art shows up)? Ultimately, how do I get rid of these windows? It constatly takes away focus from the game. Any help would be very much appreciated.

Hey Everyone- I recently obtained a set of Gun4IR lightguns. These things are so awesome and been having a blast getting my LightGuns setup. That said, because I prefer playing on the actual aspect ratio (instead of stretched), I've been using an AHK script to dynamically adjust this when a MAME game launches. The script does work in that the GUN4IR guns recognize the correct aspect ratio boundaries. However, in MAME games I run into a focus issue. Here's the AHK Script I'm using (note: I've also employed the script that removes the error/warning messages): Run, %COMSPEC% /C echo M3.1 > COM4 Run, %COMSPEC% /C echo M3.1 > COM5 WinWait, ahk_exe {{{StartupEXE}}},,60 if ErrorLevel return WinWaitActive,,,30 if ErrorLevel return Sleep 2000 SetKeyDelay, 125, 50 Send, {space 3} ~ESC:: Run, %COMSPEC% /C echo M3.0 > COM4 Run, %COMSPEC% /C echo M3.0 > COM5 ExitApp return So again, technically this works - but I run in to 2 issues: 1. When the game launches out of LaunchBox/BigBox - the MAME game window loses focus and I have to alt-tab over to the game 2. When in the MAME game, when I go into configure controls (or whatever), whenever I hit Escape, instead of going back one step in MAME, the window - again - loses focus. Strangely, this only happens once. Here's a screencast video of all of this happening: https://app.screencast.com/przDsPsSqgQB9 Just in case, I've done the same screencast without the script portion that removes some of the warning screens in MAME (still the same behavior): https://app.screencast.com/wqNIQpyQZC03w Any help would be appreciated!

Commenting on this almost 1 1/2 years later, and this works beautifully. Thank you both for this!!!!

Hey everyone - love the updates, but the latest update when using the "import rom" tool in Launchbox - skips the "move, copy, keep files where they are" step at the wizard step of "Would you like to download metadata for your games?" At this stage of the wizard, if you actually hit "BACK" instead of "NEXT" (like you usually do), you will get back that screen where it asks you about your roms "love, copy, keep where they are at" step. 100% a bug - hoping y'all get to it! (NOTE: Not sure why certain sections of my post are highlighted - didn't mean to do that! Sorry everyone!)

Hey everyone- I've scoured the boards and google on this, but I cannot figure out what's going on here. Everything works in Mame - but the trackball and dial do not work in LaunchBox/BigBox. Regarding the INI file, I have 2 instances of Mame on my Launchbox - the first one (no version number for some reason?) had the mame.ini file in the same directory as mame.exe. In my other Mame folder (version 0.264) - for some reason there was no mame.ini file in the main folder. When I "looked" for it in the /ini folder - there wasn't one in there? So "stupidly" (?) I went to the original MAME folder, copied the mame.ini file from there and copied it to the 0.264 folder as well. Still no avail. I'm clearly doing something wrong. Any help would be greatly appreciated. Edit: as an update, I checked the MAME Input Devices screen (Through BigBox), and mouse isn't being detected. i've tripled check my mame.ini file - mouse is enabled: # # CORE INPUT OPTIONS # coin_lockout 1 ctrlr mouse 1 joystick 1 lightgun 0 multikeyboard 0 multimouse 0 steadykey 0 ui_active 0 offscreen_reload 0 joystick_map auto joystick_deadzone 0.15 joystick_saturation 0.85 joystick_threshold 0.3 natural 0 joystick_contradictory 0 coin_impulse 0 # # CORE INPUT AUTOMATIC ENABLE OPTIONS # paddle_device keyboard adstick_device keyboard pedal_device keyboard dial_device mouse trackball_device mouse lightgun_device keyboard positional_device keyboard mouse_device mouse Is my mame.ini file in the wrong directory? (Currently in the same directory as my mame.exe file. Additionally, I went ahead and recreated the config after deleting mame.ini and recreating it (mame -createconfig). Still same result.