JoeViking245

Correct. Quite tedious. But correct. So something like: D:\Emulators\MAME\ini\apple2\3dstarfi\apple2.ini This is assuming that RA MAME accepts the same command line parameters as 'the real deal'.

I imagine you could do the exact same thing here as you would for setting-up/saving individual softlist game config files. Instead of -cfg_directory you'd use -inipath

(I deleted and moved some stuff for readability here. DO NOT DELETE ANYTHING LIKE I DID) <mapdevice device="Generic USB Joystick" controller="JOYCODE_1" /> <mapdevice device="Generic USB Joystick" controller="JOYCODE_2" /> <mapdevice device="Xinmotek Controller device id: Xinmotek Controller" controller="JOYCODE_3" /> <mapdevice device="XInput Player 1 device id: XInput Player 1" controller="JOYCODE_4" /> <port type="P1_JOYSTICK_UP"> <newseq type="standard"> JOYCODE_1_YAXIS_UP_SWITCH OR JOYCODE_2_YAXIS_UP_SWITCH OR JOYCODE_4_YAXIS_UP_SWITCH OR JOYCODE_5_YAXIS_UP_SWITCH </newseq> 1st 4 lines show "JOYCODE_1" "JOYCODE_2" "JOYCODE_3" "JOYCODE_4" (note: 1, 2, 3, 4) The 2nd to last line here references JOYCODE_1, 2, 4, 5 (note: 1, 2, 4, 5) So when you tested this, it probably didn't work for the last 2 controllers correctly. Based on what I'm seeing, the 1st 4 lines should point to 1, 2, 4, 5 OR (less likely) the 2nd to last line needs to reference 1, 2, 3, 4.

That good to know. Thanks.

That appears all fine. Those 4 "mapdevice" lines are what you'll add to the cfg file after you set all the inputs. Open MAME set all the controllers under player one. exit MAME copy ../MAME/cgf/default.cg to ../MAME/ctrlr/ add those 4 lines and save

Where exactly are you talking? Can you share a screen shot (or something) of what you're seeing?

I was just about to no. But.... Since your cab is just one player... you can have just one cfg file. (A total brain fart, afterthought on my part) When you set your General Inputs for Player 1 Controls, i.e. for P1 UP, You'll set all 3 joysticks to UP. So it'll say [something along the lines of ] P1 UP Joy1Up OR Joy2UP OR Joy3UP P1 DOWN Joy1Down OR Joy2Down OR Joy3Down P1 LEFT Joy1Left OR Joy3Left OR Joy3Left (and so on down the line) What it actually calls the joysticks/numbers is probably different, but you get the idea. To be clear, this is what it 'may' look like in MAME when setting it up. It'll look totally different in the .cfg file where you'll add in the ID info. Might as well throw the wheel, gun and gamepad in here too. So you might end up with ["something like"] P1 UP Joy1Up OR Joy2UP OR Joy3UP OR gamePad_UP So ya, just the one .cfg file. And this will handle any input from any of the various 'controllers' for your one player cab. Still do the part where you copy it to the "ctrlr" folder and add all the ID info in. Give the file a special name like "MyCustomControlsThatJoeVikingHelpedMeWith.cfg". Or something simpler like "MyCabControls.cfg". Whatever you want to call it. (best not to have any spaces in the name) And then in "mame.ini", set the ctrlr line (as before) to this cfg. Disregard what I mentioned about the rom_name.ini files (like "tron.ini"). Disregard needing to add Custom Command-Line Parameters. And if you had set up game-specific controls, you 'should' be able to delete those cfg files (like "tron.cfg" that would have gotten saved to your ../MAME/cfg/ folder). Note: those game-specific cfg files will also save other misc info like # of times played. So if you delete them, they will reappear on their own. Sorry for my confusion, confusing you. hope I haven't made matters even more so confusing. lol

Wait! So your cab isn't setup for 3 players, but just 3 'types' of controls? Remember that 'can of worms' I mentioned? lol Just kidding. I think then what you're wanting to do is create 3 different config files. For each one, you setup Player 1 controls with the respective joystick. Then save them individually as something like "4way.cfg", "8way.cfg" and "flightStick.cfg" (or something that's easy for you to remember). (in each one of the 3, you'll add the respective ID's and JOYCODE_1) Then in your mame.ini file, have the "CORE INPUT OPTIONS" section set ctrlr to 8way.cfg # # CORE INPUT OPTIONS # coin_lockout 1 ctrlr 8way Since this is [probably] the most common, this will be the default. Unfortunately there's not a way (that I'm aware of) for MAME to automatically load a 'special' configuration file based on controller type used. If you did this, I think you'd still need to then edit each of these cfg's to add the ID info. Since you've created the 4way.cfg and flightStick.cfg configuration files, what you can do is create a game (machine/rom) specific ini file that only needs one line of text in it. Then save these files in ../MAME/ini/ i.e. create "tron.ini", and in it, have the line ctrlr flightStick No more. No less. ("tron" being the rom name only. v.s. the games full 'Title') Not to add more to the confusion... Another option [instead of creating a zillion ini files] is, in LaunchBox, for all the games that use, i.e. a 4-way joystick, you can use the Custom Command-Line Parameter "-ctrlr 4way". If you happen to have Categories for your Arcade Platform... i.e. ..you can Bulk Edit the Custom Command-Line Parameters for the respective category.

Disregard everything I said about Xinput and you'll be good. Yup. That should work. But I don't know if Supermodel is caSe sENsaTivE or not. But I do know "FullScreen = 1" does work. I don't know if "FULLSCREEN = 1" does or not.

Yes. You can save game-specific configurations that will override the [created] default configuration. When playing a game and you go into the MAME menu (press Tab) and you select Input (this Machine) and make changes, those game-specific 'changes' will be automatically saved and will ONLY ever be used buy that specific game, every time it's loaded. You'll find 'this' game-specific configuration file in the "cfg" folder: ../MAME/cfg/defender.cfg

Yes and No. Windows switching around the controller input 'locations' (ports) when you unplug, plug-in and/or reboot is their little gift to us. But what they can't change is the controllers' (devices) ID's. Call it a unique serial number each device has. When you do the steps from the above link, you'll be getting and saving these ID's and setting them to the respective 'controller #' for MAME. So then at this point, MAME doesn't care which port they're plugged into. It reads the 'serial numbers' from all ports, then matches those to what you have setup in your config file for controller #'s. Ya, you probably should. At least the wheel, the gun, the gamepad (if you intend to use it with MAME) as well as the cab joy's and buttons. The trackball is usually 'just a mouse'. So should be fine. I honestly have no idea about the spinner. Generally, what you want to do is: plug in E V E R Y D E V I C E you have. Set up all the default inputs in MAME for each player/device. Get the ID's from every device as they are set up "now" (step 2). Modify the config file to associate the ID's (step 3) with the players/devices (step 2) Play games. Don't know if you stumbled across this during your research, but it kind lays out these steps in a little more detail. Except step 5. That always stays the same. Oh... and to be clear, all this is for stand alone MAME only. No RetroArch-MAME or some offshoot branch of MAME shtuff. Just good ol' fashioned MAME. It may work for those also. But this can of worms would end up turning into a barrel of snakes. Just sayin'.

You indicate that it's working [now] from the command prompt. That's an excellent start! Make sure in LaunchBox you're pointing to your 'updated' version (in case you placed it in a different folder). Plain and simple. Just point to Supermodel.exe and don't check any boxes. And if you did by chance change the path or added a second Supermodel Emulator in LaunchBox, make sure to verify that it's set to Default for the associated Platform (if you have a designated Model 3 Platform) or at least the games that use it are pointing to the correct copy of the Emulator. To get it FullScreen, edit your supermodel.ini file and add in "FullScreen = 1". And again, if you are using an Xinput device, set that. And while you're at it, add in some simulated Force Feedback.

@rmetzger What does your supermode.ini section for steering and pedals look like? ; Steering wheel InputSteeringLeft = "KEY_LEFT" ; digital, turn wheel left InputSteeringRight = "KEY_RIGHT" ; digital, turn wheel right InputSteering = "JOY1_XAXIS" ; analog, full steering range ; Pedals InputAccelerator = "KEY_LEFTCTRL,JOY1_RZAXIS_POS" InputBrake = "KEY_LEFTALT,JOY1_ZAXIS_POS" Here, I can use the Left/Right arrows OR the left joystick on my Xbox 360 controller for steering. And for the gas pedal, Ctrl on the keyboard OR the Right Trigger on the controller. Brake is Alt OR Left trigger. Also, if using a controller with Xinput, be sure to have "InputSystem = xinput" in the ini file. (or you can set it from the command line.) And remember, an emulator will only run as good through a FrontEnd as you can get it to work standalone. As this seems to be an emulator related issue, a great resource for Q&A would be their forums. Not that it hurts to ask here. [Soccer game - probably Virtua Striker 2 ]

Thanks! And you are most welcome. Ya, it wasn't originally intended to be shared. So, "quirky", it is. lol

Not sure I can link directly to the original sm3 post, but it says something like I think "5" is for the service menu.

What version of Supermodel are you using? (latest is SNV 860) Does it work when you run it stand-alone (Command Prompt)? Supermodel.exe "F:\LaunchBox\Games\Sega Model 3\swtrilgy.zip" If you're updating or have updated it, make sure you have the Game.xml file for that particular release.

I tried the Copy/Paste thing and like you, thought "There has to be a better way". So I wrote a little stand alone program for personal use that makes it [at least] a little easier. It needs my 2 program files (an .exe and a .dll) and "[LIST_MAME_MINI].xml" and "controls.xml" located in ../CPWizard/Data/ Create a new folder (call it whatever and put it where ever) and copy these 4 files into it. (this way we don't accidentally screw up the 2 existing xml's [just in case]) You'll probably need to UnBlock my 2 files for Windows to let you run it. Start typing the rom filename (no extension) in the search box and it'll populate a list based off what's in your existing controls.xml (I used this mainly to edit existing control 'values'). Once typed, press Enter. Here you should see the info (right grid box) that's in LIST_MAME_MINI. Below that, click Add to controls.xml and it'll add it. This may take a few (several?) seconds. When the wait cursor stops 'waiting', click Search and it should now populate the grid box on the left. At this point, you can edit the Values to your liking (i.e. change "1" to "Gas Pedal") and then click Update controls.xml. If for some reason (using hotwhl2p as an example) say it actually has 2 buttons, you can add P1_BUTTON2 by double clicking it. Then to make it organized, click Up to put it below BUTTON1. Don't forget to click Update controls.xml when you're done editing. If you have "portname" installed with MAME, you can sometimes get controller information from it. https://github.com/cracyc/mame-portnames It's not required, but can be helpful. (example for "1942" showing the "Fire" and "Loop" Values) Again, this was a personal project and works "for me". Results may vary. Not initially intended for public use. So it's probably as "pretty" as it's going to get. But hey, if it works... Great! MAMEcontrollers.7z

What: By default, this shows the game specific controls image (if one exist) on a 3rd** monitor when you launch and are playing a game. This works in both LaunchBox and BigBox. The image it looks for is the one you set for the specific game as “Arcade - Controls Information”. (As opposed to “Arcade - Control Panel “, “Box – Front”, “Screenshot - Game Title” etc.) Any game for any Platform can have an associated “Arcade - Controls Information” image. If the specific game doesn’t have an “Arcade - Controls Information” image associated with it, the plugin will then search for the Platforms “Device” image file located in: ..\LaunchBox\Images\Platform\your_games_platform\Device\ If neither of those are found, nothing will be shown. **You can change which monitor the image is displayed on by renaming “3.mon” (included in the download) to the number of the monitor you want the image to appear on. i.e. “4.mon”, “2.mon” or even “1.mon”. (I thing you might be able to rename this to test on a different display without having to exit/restart LaunchBox.) Why: This was created as a just-because, proof-of-concept type of thing. The problem I have is that I don’t have 3 monitors to test this on. Though I can attest that it does work with 2 monitors. (Rename “3.mon” to “2.mon”) I don’t really plan to add a 3rd monitor to my personal setup and like many of the other plugins I created, I probably won’t use it. Lol But, like all of the other plugins, it was a lot of fun creating. And it seems to work. But still debating how practical it actually is. Help wanted: That said, if someone, anyone (or even many) could try this and provide some feedback, it would be greatly appreciated. Mainly looking to find out if it does actually display correctly on a 3rd (4th? [that’d be cool]) monitor. But any and all feedback is appreciated. How: Oh ya… installing… Download the zip file DisplayControls 0.0.1.0.zip Unblock it Extract the contents to your ../LaunchBox/Plugins/ folder Rename “3.mon” as necessary. Start LaunchBox and play a game.

@megashub Thank you very much!! Glad you like it. As for me accepting payment for additional features, as nice as it would be, no. If a request is within my abilities, I'll just add it. With discretion, of course. As for your requests, I can a l m o s t see #1 being convenient. If say you're filling in the Application Command-Line Parameters, you'd get a dropdown list of all the cl Parameters used for additional apps in that Platform to select from [or finish typing your own]. The "almost" part is that it's kind of a redundancy of the intent of this plugin: You select all your desired games, fill in the 'form' [once], click OK and you're done. But I'm thinking this isn't what you meant. I think what you want is what was referenced to in the Additional Notes:. A Bulk Edit Additional apps plugin. Which (as far as I'm aware of) [still] doesn't exist. And for good reason. The LaunchBox API (which is what's used to create plugins) doesn't include a method for editing Additional Apps. Though there is Add New and Delete Existing, I imagine with a bit of (a lot of 'a bit of' ) finessing using those, someone could make that work. There is however an easy fix/resolution/cure_for_the_typo... Exit LaunchBox Go to your ../LaunchBox/Data/Platforms/ folder and edit the platform.xml file with a text editor. (Notepad++ is my got-to) 'platform' is the Platform that has the typo in it. (Backup of your xml file first. Just in case) Go to Search, Replace... (or press Ctrl+H) Fill in Find what: and Replace with: and click Replace All (Check your spelling before clicking Replace All! ) Save and exit Start LaunchBox (BigBox) Play games Use the full command line because who knows what else in the file has simply "dne".

Some of the 'zips' are probably Device files and possibly some Bios files too. So not actual playable games. A few games are actually "built-in" to MAME where there is no rom file, per se. [at least there used to be some]. For the chd games, you more than likely have a zip file as well as the folder. So you might have something like: ../MAME/roms/area51.zip ../MAME/roms/area51/area51.chd That'll hopefully account for at least some of the difference.

There was a change with MAME. The link has the replacement bublbobl.xml. Copy it into \LaunchBox\ThirdParty\hi2txt\hi2txt.zip (replacing the existing one inside the zip).