Jump to content
LaunchBox Community Forums

JoeViking245

Moderators
  • Posts

    5,575
  • Joined

  • Last visited

  • Days Won

    41

Posts posted by JoeViking245

  1. 13 minutes ago, Shinlocke said:

    I am being told that RetroArch is not really good for Lightgun Emulation, at least for the RS3 Reaper. 
    I am going to try to use RetroBat instead for those games and see if that resolves the issue. 

    It's more of an emulator setup issue than a frontend issue.

    The emulators I use with my Gun4IR are Demul, Flycast, Model2 (emulator.exe) and [standalone] MAME. I don't use TeknoParrot, but do have a couple games using JConfig. Then alongside these, I use DemulShooter (where applicable), LUA scripts for MAME and QMamehook.

  2. 24 minutes ago, Drake008 said:

    I have the settings like so in the mame.ini

    rompath              "roms;e:\Romvault MAME\RomRoot\MAME CHDs (merged);e:\Romvault MAME\RomRoot\MAME ROMs (split)"

    and when I try to start a chd game like Killer Instinct it gies black and then back to the launchbox menu. Normal roms are running fine. What do I do wrong here?

    Did you remove -rompath %romlocation% from the command-line parameters? (Tools-Manage Emulators-Edit [MAME])

  3. On 4/17/2026 at 11:52 PM, Drake008 said:

    is there a way to have the roms and chds in different folder and not everything in one?

    Assuming you're referring to MAME, yes.  (be sure to read the entire post)

     

  4. 8 hours ago, Shinlocke said:

    but the trigger and buttons on the gun don't seem map. When its in Lightgun, I don't seem to see the controller options to map Trigger etc like I do when its set to Joystick

    The lightgun I believe should be being seen as a mouse.  When mapping the trigger and buttons (aka left/middle/right clicks) try pointing the gun at the screen when pressing them.  Specific lightgun & emulator software pending, if you're not aiming the screen, the gun thinks you are shooting offscreen and uses different modes. Depending on what you selected in the lightguns' software settings.

  5. 2 minutes ago, Gaming.Zone said:

    Think it was a caching issue that all 3 had to be removed to clear?

    No.  There was a "glitch in the Matrix" that the developers were able to quickly resolve (thanks for bringing it up, BTW). :D  But the final part of the fix (in this case) required us to remove those folders as mentioned [so LB could rebuild them].

  6. 2 minutes ago, Gaming.Zone said:

    Good to know it is not local to just me.  I can deal with manual updating emulators.  I just needed to know.

    Fixed(ish).

    • Close LaunchBox
    • Navigate to you /LaunchBox/Plugins/ folder
    • Delete the following folders:
      • Dolphin LaunchBox Integration
      • PCSX2 LaunchBox Integration
      • RetroArch LaunchBox Integration
    • (Re)start LaunchBox
    • Thanks 1
  7. 21 minutes ago, Gaming.Zone said:

    Can anyone think of anything else to try?  This feels like 3 broken plugins to me.

    I'm seeing the same issue with those 3 updates.  

    For now, I suggest leaving the 3 emulators alone.  If you know of and feel you have to update one of them, do it manually.  You know, the old-fashioned way. ;)

    • Thanks 1
  8. "None" is for a list of games that do not have an associate platform.  

    "Exists" is for a list of games that do have an associate platform.

    "All" is for a list of all games, regardless of platform association.

     

    55 minutes ago, chinagreenelvis said:

    so if there's no option to prevent that platform from being scanned or some way to actually audit what gets detected as missing, that forces me to have to re-scan every single other console platform one by one.

    Correct. Currently it's scan all platforms, or one-by-one.

     

  9. Thanks Christian, for not only all you've done for the LaunchBox apps and the Community, but for your never relenting help to me and my exhaustive plugin programming questions.  You have always been and continue to be greatly appreciated!

    I wish you all the best!  Be well and talk soon.

    • Thanks 1
  10. 8 hours ago, sipes760 said:

    I am not using custom display settings, or errant parameters, and I only have one copy of FBNeo on my PC. 

    Good. Process of elimination, step #1 complete. ;)

    Typically, the box Remove Quotes would get unchecked as well (just like MAME).  Though with fbneo64.exe, it does work either way (not sure if it does for MAME).

     

    Try:  Change your Blitter to DirectX9.

    image.thumb.png.4518a26b542d712ed68b07131679a682.png

  11. 7 hours ago, oldgamer said:

    We need to add this request to the Launchbox game database so we can start adding all the images and media.

    To make an "official" request, at the top of this page click Help & support and select Request a Feature.  

    That way it'll get 'logged' to-be-looked-into.  vs. "Hey! That's a great request! I'll have to remember to look into that.  [time passes...] What was I supposed to look into? Maybe if I look through the myriad of posts I'll remember.  Now... was that on the forums? Discord? Facebook? X?..."  etc. etc. ;) 

    After the post becomes public, be sure to post a link to it here so others that come across this can go and upvote it.

  12. Are you setting a custom display setting?  vs. say using 1280x920?  Do you have any default command-line parameters set that are forcing the display mode setting? Or possibly an errant parameter?  In the emulators settings (in LaunchBox) or in the Associated Platforms section?  Can you share a screenshot of the command-line parameters you've set in LB (in the main Details section and the Associated Platforms section).

    When testing outside of LaunchBox, any chance you're testing on a different FBNeo build? e.g. you have it installed in 2 locations and you're testing stand-alone on one and LB is pointing to the exe on "the other" install.

  13. 4 minutes ago, xokia said:

    If I install Autohotkey 2.0 does that screw up the autohotkey 1.0 code I have in launchbox?

    I personally recommend sticking with v1.  For what it's used for in LaunchBox, you don't gain any functionality with v2.  Also, sticking with v1, you can make use of the exe located in the ThirdParty folder, keeping LaunchBox truly portable.  Along with easily making 'your' scripts usable by all users (e.g. negating the need to have AHK installed on your system).

    My opinion™.  :)

    • Thanks 1
  14. 2 hours ago, xokia said:

    Maybe an issue with loading .bat files I cant tell. Works perfectly from command line fails from launchbox and hangs at the loading screen.

    Unless this was working for you in a previous LaunchBox version, this is not a beta issue.

    • Like 1
×
×
  • Create New...