JoeViking245

From the other post I linked... - In the ‘../MAME/cfg’ folder, copy “default.cfg” and paste it into the ‘../MAME/ctrlr/’ folder. From here you can rename it to something like “MyControls.cfg”. It probably have said "... you should rename it..". Which I assume is what you did. Renamed it to "zerodelay_x2" because that's what your mame.ini is looking for. (I'm guessing you mistyped when you just now wrote "zerodelay_cfg" [vs "zerodelay_x2"?]). Whichever it is, make sure it's name is the same as what's in your mame.ini. So it's now copied into the ctrlr folder, is properly renamed... now insert the "<mapdevice device=" lines just as you did before [but with those corrections noted above].

Just fix those 2 lines in whatever file you're loading your controllers with. According to the verbose out you showed in 'dmList.txt', you're using "zerodelay_x2.cfg" to load your controllers. So change them in there. I'm guessing in your mame.ini file, you have listed under # CORE INPUT OPTIONS... "ctrlr zerodelay_x2". If you have that in there AND you're trying to make changes to default.cfg, you're you're going to have a real tough time troubleshooting.

@darrenmarchand It looks like it loaded your 2 Generic USB Joystick's like it was supposed to. (note: "joycode #0" shown here is your "JOYCODE_1". "joycode #1" is your "JOYCODE_2") Looking again at your zerodelay_x2.cfg file, I think you need to revise the lines for Kinmotek and XInput. For those 2, remove the stuff before (and including) "Device id: " after: Moral of the story, put in the devices ID info, but not "Device id: ".

@darrenmarchand May I see what your verbose output looks like (with at least your 4 main controllers plugged in and on.. if not everything, including wheel etc.)? Open Windows Command Prompt and navigate to your MAME main folder. At the prompt, type mame.exe -v >dmList.txt (change mame.exe to mame64.exe if needed) After the MAME main window gets fully loaded, Exit MAME. (don't be tempted to play games. ) Drag and drop the new "dmList.txt" file that it created into your reply here.

It's saying your cdimono1.zip is missing those 2 files.

That's probably because of the language your chd files are in. cdimono1 is for PAL and cdimon2 is for NTSC.

You asked. We delivered. (Bulk) Remove Additional Applications (though may be a little bit too late. lol)

(Bulk) Remove Additional Applications View File (Bulk) Remove Additional Applications The intent of this plugin is to Remove the same** Additional Application for all games in a given Platform, all at one time. **Same is determined by the Additional Applications Application Name and Application Path. If they match exactly, they are the ‘same’. Why use this? Quite possibly because you used the Bulk Add Additional Applications plugin and you clicked “OK” before realizing you forgot to add in the Command-Line Parameters or it's simply not needed anymore. Setup: Download and extract "BulkRemoveAdditionalApps.dll" from the zip file and place it in your Plugins subfolder of LaunchBox. Right click the dll file, select Properties, and click "Unblock" (if it's there) and click OK. Using the plugin: - Click Tools and select "Bulk Remove Additional Apps". - Click the dropdown box and select a Platform. - Click Get to show the Additional Apps for that Platform.*** - Check the Remove box(s) for the Additional Apps you wish to delete. - Click Remove to delete/remove all occurrences of those selected Additional Apps.**** *** The plugin will 'combine' any Additional Apps that have the exact same Name AND App Path, and only display one of those. When you remove that "one", all occurrences (having the same Name and Path) will be removed. ***Example: You used the Bulk Add Additional Applications plugin to add an Additional App to 245 different games. You named it “My Run-Before App” and set the Application Path to “D:\MyApps\RunBefore.exe”. This plugin will only display it in the list once, instead of 245 times. (Because they all “have the exact same Name AND App Path”.) **** Once you click Remove, the apps you had selected will get removed/deleted forever. There is no undoing this once OK is clicked! (unless of course you have your backup file that was created with the LaunchBox built-in Automatic Backup feature.) Submitter JoeViking245 Submitted 05/08/2021 Category Third-party Apps and Plugins  

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.