Jump to content
LaunchBox Community Forums

JoeViking245

Moderators
  • Posts

    4,267
  • Joined

  • Last visited

  • Days Won

    34

Everything posted by JoeViking245

  1. 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
  2. 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.
  3. 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.
  4. 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
  5. 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'.
  6. 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.
  7. @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 ]
  8. Thanks! And you are most welcome. Ya, it wasn't originally intended to be shared. So, "quirky", it is. lol
  9. Not sure I can link directly to the original sm3 post, but it says something like I think "5" is for the service menu.
  10. 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.
  11. 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
  12. 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.
  13. @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".
  14. 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.
  15. 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).
  16. Your thinking is correct. There isn't [an easy way]. The hard way is to modify the source code and compile your own. But that would be more a of a pain than it's worth for a momentary popup notification.
  17. Updated: v 4.02 Fixed: Will now add the Associated Platform and Custom Command-line Parameters to the emulator when you choose "Import clones as additional apps".
  18. Thanks for letting me know. I'll work on fixing my oversight. I would love to say that you're not alone in this problem. But after about a year and a half this is the 1st that it's come up. lol Well, maybe you're just the first to take the time let me know. Thanks again for getting back.
  19. If we're talking the same thing, it does appear complicated, but it's not overly complicated. You'll use the Command Prompt just once to get a list of all your controller ID's. Once you get those, it's a matter of following the rest of 'the guide' to set them up for MAME. https://docs.mamedev.org/advanced/devicemap.html There are supposedly some third party programs out there that can help with this. Not just for MAME, but other emulators/situations as well. But I've never tried any. There've been several (many?) posts here on the forums and probably even some YT videos. You'll want to look for 'stable controller IDs' or 'stable IDs' or a variant thereof.
  20. See if un-checking "Use folder names instead of ROM file names for game titles" helps any. Then also, if you check "Search for game information in the local metadata database", LaunchBox will then know how to properly name the games based off the roms [zip] file name. For example "woodpeca" would become "Woodpecker (set 2)" and "woodpeck" would become "Woodpecker (set 1)".
  21. @dcosborne No. The other plugins wouldn't be causing this issue. And we're go to go through the latest LaunchBox betas. From what I can see and just tested, the code was never written to account for the selection Import Clones as Additional Apps when adding the Platform and Custom Command Lines to the emulators additional apps. In other words, if you select that option [red box]... ...the Platform and its' Custom Command Line Parameters will never get added to your selected emulator. However it does seem to work with the other 2 options. Let me know if the other 2 don't work on your end. Those 3 options were originally put there to mimic the MAME Arcade Full Set importer tool. And honestly, when testing I'd never looked beyond making that selection and seeing the Platform and games were indeed added. I suppose I never totally thought through adding Clones as Additional Apps for Consoles. I'll put that on my "to-do" list. As always, thanks [sincerely] for letting me know. And if you would, let me know if those other 2 aren't working for you either. If it's of any consequence, luckily, Casio Loopy Carts don't have any clones in the MAME set.
  22. RetroAchievement Badges official release: Includes an Updater and some other refinements. The biggest one (that you may notice) is "The". This will now 'convert' R-Achievements "Addams Family, The" to "The Addams Family" making it so the Badge now appears (without having to right-click). Anyone who wishes to use the 'official' release and had previously installed the beta release... Completely delete the beta release folder first! I tried to make a seamless integration between the two, but it made things more problematic than good.
  23. RetroAchievement Badges View File RetroAchievement Badges What does this plugin do? Adds “RetroAchievement” Badges to games that support RetroAchievements. (See complete list of games here: https://retroachievements.org/gameList.php) Why? Because some people wanted it. April 24, 2023 Version 2.3.5 will be the last update for this plugin. As of LaunchBox version 13.2 (Feb. 27, 2023), Achievement Badges are now supported. (Includes RetroAchievements, Steam and GOG achievements) To enable: click the hamburger menu, select View, Badges, Game Attributes, Enable Achievements. How to install the plugin: Download RetroAchBadge v2.x.x.zip UnBlock the zip file. Right click the file, select “Properties” and check the box that says ‘Unblock’ [or something along those lines] Click OK to close the Properties window Open the zip file Copy the folder “RetroAchBadge” into your “/LaunchBox/Plugins/” folder Start LaunchBox Select Tools Select RetroAchievements Badge Updater (Internet connection required) Click Start Update and Wait for the Updater to complete. (This may take up to 1 minute.) How to see the badges: Start LaunchBox (not necessary if you just completed the Install - steps 1 through 9) Click BADGES Select Plugin Badges 'Check’ Enable Retroachievements How to add or remove the badge from a game: Right click the game and select "RetroAchievements Badge" How to get updates for new games added to RetroAchievements: In LaunchBox, Select Tools Select RetroAchievements Badge Updater (Internet connection required) If you added or removed RetroAchievement badges for specific games, those games will remain added or removed after running the Updater. To reset the games that have been added/removed, delete the files Added.xml and Removed.xml located in the plugins folder and rerun the Updater. A word about Platform names: Some of the Platform names used by RetroAchievements are different than the default names used in LaunchBox. When using the Badge Updater, it will ‘convert’ these to the default names. Examples: “Mega Drive” gets changed to "Sega Genesis". “SNES” to "Super Nintendo Entertainment System". "Game Boy" to "Nintendo Game Boy". This plugin will not rename any of your existing Platforms. When checking for badges, the plugin will check your Platforms Scrape As setting as well as the Platform name. Example: If you named your Platform "Game Boy" and Scrape As is set to "Nintendo Game Boy", badges will show for that Platform. Platform names that get changed: From To "Mega Drive" "Sega Genesis" "SNES" "Super Nintendo Entertainment System" "Game Boy" "Nintendo Game Boy" "Game Boy Advance" "Nintendo Game Boy Advance" "Game Boy Color" "Nintendo Game Boy Color" "NES" "Nintendo Entertainment System" "32X" "Sega 32X" "Master System" "Sega Master System" "PlayStation" "Sony Playstation" "Game Gear" "Sega Game Gear" "Virtual Boy" "Nintendo Virtual Boy" "MSX" "Microsoft MSX" "SG-1000" "Sega SG-1000" "Saturn" "Sega Saturn" "Intellivision" "Mattel Intellivision" "Vectrex" "GCE Vectrex" "PC-8000_8800" "NEC PC-8801" "PC-9800" "NEC PC-9801" "PC-FX" "NEC PC-FX" "Dreamcast" "Sega Dreamcast" "PlayStation Portable" "Sony PSP" "PC Engine" "NEC TurboGrafx-16" Changing the default icon: If you wish to use a different Badge icon, replace “\LaunchBox\Images\Badges\RABadge001.png” with your own image. Known Issues: Game titles are taken directly from RetroAchievements and may differ (slightly or a lot) from yours. So if you have a game that is known to have achievements and the badge isn’t showing, follow all steps under How to add or remove the badge from a game:. Updating via the Tools menu may take up to 1 minute to complete. Though not really an 'issue' perse, but it is a "thing". So plan your updates around refilling your water glass, grabbing a soda or whatever takes you about 60 seconds to do. Unknown issues: Let me know when you find them. Designed for LaunchBox 11.3 and newer. Major contributors to the plugin are: @jayjay Submitter JoeViking245 Submitted 04/17/2021 Category Third-party Apps and Plugins  
  24. Version 2.3.6

    1,114 downloads

    RetroAchievement Badges Version 2.3.6 was the last update for this plugin. (Sept. 2024) This plugin is broken and is no longer supported. As of LaunchBox version 13.2 (Feb. 27, 2023), Achievement Badges are supported directly in LaunchBox. To enable: click View < Badges < Game Attributes < Enable Achievements. I wish to give a huge thanks to @jayjay for his work in initiating this plugin all those years ago!! And to all Community Members who have used, provided feedback and gratitude, Thank You for Your Support! (This thread remains here for historical reference until such time The Management deems otherwise) What does this plugin do? Adds “RetroAchievement” Badges to games that support RetroAchievements. (See complete list of games here: https://retroachievements.org/gameList.php) Why? Because some people wanted it. How to install the plugin: Download RetroAchBadge v2.x.x.zip UnBlock the zip file. Right click the file, select “Properties” and check the box that says ‘Unblock’ [or something along those lines] Click OK to close the Properties window Open the zip file Copy the folder “RetroAchBadge” into your “/LaunchBox/Plugins/” folder Start LaunchBox Select Tools Select RetroAchievements Badge Updater (Internet connection required) Click Start Update and Wait for the Updater to complete. (This may take up to 1 minute.) How to see the badges: Start LaunchBox (not necessary if you just completed the Install - steps 1 through 9) Click BADGES Select Plugin Badges 'Check’ Enable Retroachievements How to add or remove the badge from a game: Right click the game and select "RetroAchievements Badge" How to get updates for new games added to RetroAchievements: In LaunchBox, Select Tools Select RetroAchievements Badge Updater (Internet connection required) If you added or removed RetroAchievement badges for specific games, those games will remain added or removed after running the Updater. To reset the games that have been added/removed, delete the files Added.xml and Removed.xml located in the plugins folder and rerun the Updater. A word about Platform names: Some of the Platform names used by RetroAchievements are different than the default names used in LaunchBox. When using the Badge Updater, it will ‘convert’ these to the default names. Examples: “Mega Drive” gets changed to "Sega Genesis". “SNES” to "Super Nintendo Entertainment System". "Game Boy" to "Nintendo Game Boy". This plugin will not rename any of your existing Platforms. When checking for badges, the plugin will check your Platforms Scrape As setting as well as the Platform name. Example: If you named your Platform "Game Boy" and Scrape As is set to "Nintendo Game Boy", badges will show for that Platform. Platform names that get changed: From To "Mega Drive" "Sega Genesis" "SNES" "Super Nintendo Entertainment System" "Game Boy" "Nintendo Game Boy" "Game Boy Advance" "Nintendo Game Boy Advance" "Game Boy Color" "Nintendo Game Boy Color" "NES" "Nintendo Entertainment System" "32X" "Sega 32X" "Master System" "Sega Master System" "PlayStation" "Sony Playstation" "Game Gear" "Sega Game Gear" "Virtual Boy" "Nintendo Virtual Boy" "MSX" "Microsoft MSX" "SG-1000" "Sega SG-1000" "Saturn" "Sega Saturn" "Intellivision" "Mattel Intellivision" "Vectrex" "GCE Vectrex" "PC-8000_8800" "NEC PC-8801" "PC-9800" "NEC PC-9801" "PC-FX" "NEC PC-FX" "Dreamcast" "Sega Dreamcast" "PlayStation Portable" "Sony PSP" "PC Engine" "NEC TurboGrafx-16" Changing the default icon: If you wish to use a different Badge icon, replace “\LaunchBox\Images\Badges\RABadge001.png” with your own image. Known Issues: Game titles are taken directly from RetroAchievements and may differ (slightly or a lot) from yours. So if you have a game that is known to have achievements and the badge isn’t showing, follow all steps under How to add or remove the badge from a game:. Updating via the Tools menu may take up to 1 minute to complete. Though not really an 'issue' perse, but it is a "thing". So plan your updates around refilling your water glass, grabbing a soda or whatever takes you about 60 seconds to do. Unknown issues: Let me know when you find them. Designed for LaunchBox 11.3 and newer. Major contributors to the plugin are: @jayjay
  25. You could create a batch file and run it inside the folder where your roms are located. If you have 7zip installed, it would look something like this: for %%i in (*.*) do "C:\Program Files\7-Zip\7z.exe" a "%%~ni.zip" "%%i"
×
×
  • Create New...