Jump to content

JoeViking245

Moderators
  • Posts

    5674
  • Joined

  • Last visited

  • Days Won

    43

Posts posted by JoeViking245

  1. 16 minutes ago, jestermgee said:

    I have created a category but am now stuck if it's possible just to make an entry within this category that just opens a file? 

    No.
    Items (games, pdf file, videos etc.) HAVE to be imported into a 'Platform'. Which could then reside under the Category. But I believe you can set a platform at the Root level (which would sit alongside the 'Categories').  At least you can in LaunchBox. Not sure about Big Box (don't use it that much).

    If you can have a Platform reside at the Root level, and you have just ONE 'item' in that platform, there's a plugin that will 'launch' that one item when selecting the platform. aka, you won't have to enter the platform then select the one item to open it.

    Last I knew, it still works.

     

  2. In LaunchBox, edit the platform.  On the right-hand side, click the yellow + symbol and navigate to and select the logo you found. Click the field right below the yellow + symbol and select Clear Logo (Override).  Click OK to save and close. Open Big Box (press Ctrl+B to switch to it) and Refresh Platform Wheel Images cache.

    • Like 1
  3. 1 minute ago, Noah Evans said:

    LaunchBox can launch it only if the launcher accepts a ROM argument. In Edit Emulator, point Executable to the launcher, set Working Folder to its folder, and try just "%romfile%" or --game="%romfile%" in Default Command-Line Parameters; don’t put the ROM path in the executable field. If neither works, the launcher likely expects an internal game name/index or has no CLI—check its readme/config or use a small wrapper. What syntax does its help/readme document?

    Nice totally-non-helpful AI response.  Might try starting to reply to posts that you actually have personal knowledge on and using your own words. Not using an ignorant AI's response.

    • Like 1
  4. 4 hours ago, marcosgaming said:

    I think that difference here Is in input mode...

    What input to use in my situation?

    If you set your encoder to Xinput mode and plug in 2 Xbox controllers, Supermodel will see 4 controllers. Joy1, Joy2, Joy3 and Joy4.  Which order it sees them in, no idea. But you'll always have 4 players (4 active controllers).

    I suppose you could set it up in the ini to cover the other 2.  e.g.:
    InputJoyUp = "KEY_UP,JOY1_UP,JOY3_UP"
    InputJoyUp2 = "KEY_R,JOY2_UP,JOY4_UP"

    This seems it should cover whether your encoder is in Xinput or Keyboard mode.

     

    The easiest way may be to set the encoder to whichever mode is easiest for you and best compatible across the board for all your emulators.

    Plugin in and turn on the 2 Xbox controllers and start SuperModel. Go into the Key Bindings tab and set them up from there.

     

    image.thumb.png.39a5a8c3c9c41cc7e3fa2531e750abc1.png

     

  5. 4 hours ago, marcosgaming said:

    Driving games: They play amazingly with an Xbox 360 controller, but steering/handling is terrible when using an arcade cabinet control panel.

    With the controller, the steering is variable along the Y axis. You can turn left a little or a lot (or anywhere inbetween).

    Where-as a joystick is a go/no-go situation.  It either has the wheel centered, cranked all the way to the left or all the way to the right. You can't just turn slightly.

    4 hours ago, marcosgaming said:

    My ultimate goal is to have a 100% working Supermodel.ini where both two Xbox 360 controllers AND a dual-player arcade cabinet/keyboard can coexist smoothly without breaking each other's inputs.

    Is this actually possible, or is it an impossible mission? If anyone has a working config file for a similar dual-setup (arcade cab + Xbox pads) or some advice, I'd really appreciate it if you could share it.

    Here's an example setup that makes use of a 2-player cab (with the encoder set to keyboard mode) and 2 controllers

    ; 4-way digital joysticks
    InputJoyUp = "KEY_UP,JOY1_UP"
    InputJoyDown = "KEY_DOWN,JOY1_DOWN"
    InputJoyLeft = "KEY_LEFT,JOY1_LEFT"
    InputJoyRight = "KEY_RIGHT,JOY1_RIGHT"
    InputJoyUp2 = "KEY_R,JOY2_UP"
    InputJoyDown2 = "KEY_F,JOY2_DOWN"
    InputJoyLeft2 = "KEY_D,JOY2_LEFT"
    InputJoyRight2 = "KEY_G,JOY2_RIGHT"

    Player 1 joystick is mapped to up/down/left/right
    Player 2 joystick is mapped to R/F/D/G

    Controller 1 (Joy1) & 2 (Joy2) are mapped to their respective up/down/left/right

     

    Now if your encoder is set to Xinput mode, that's a different story.

  6. Do you have any files in your C:\LaunchBox\Emulators\RetroArch\config\Nestopia\ folder?

    Do you have any files in your C:\LaunchBox\Emulators\RetroArch\overlays\GameBezels\NES\ folder?

     

    I selected all games in my Nintendo Entertainment System platform and ran Tools < Download < Update Metadata and Media for Selected Games...

    Then in the wizard, selected Check None for LB and EmuMovies images, checked Download Bezels and chose Theme Bezels (the default). Then selected Yes, Download and replace all.... After a few minutes (when it was done) launched a game and the bezel appeared. It showed a default Famicom bezel for 1942 and a game-specific bezel for Kart Fighter.  aka, it Just Worked™.

    The 2 folders mentioned above (plus a couple others) is where new files (based on today's date) appeared.

    Not sure if your platform being called Nintendo (vs. Nintendo Entertainment System) has anything to do with it. But more-so, verify that the platform is set to Scrape-as Nintendo Entertainment System.

  7. 19 minutes ago, wolfenstein0099 said:

    Thanks bud!

    You can call me Joe.  (Bud reminds me of Jeff Spicole. lol)

    23 minutes ago, wolfenstein0099 said:

    I set cap of my frame rate to 60. Not unlimited, prefer maximum performance, also set my vsynic to fast to fix the flickering and in flycast. I have vsynic set to on, vulcan and per pixel. Now the gun works great and no screen tearing as well.

    Thanks.  Was this all in Flycast? Or in the NVidia Control Panel.

    26 minutes ago, wolfenstein0099 said:

    Thanks a million Joe. Once I reonstalled everything it fixed all my issues! 

    (much better. ;))  Always glad to help. Glad to hear it's fixed.

  8. 6 minutes ago, wolfenstein0099 said:

    it's running as admin

    Don't run things as Admin! 
    If you have to do that, you'll never get things running in LaunchBox. That's not a threat or a warning. It's a promise.  (just sayin' ;))

    8 minutes ago, wolfenstein0099 said:

    Same error every time I boot it. 

    I'll have to resort to the proverbial "have you tried turning it off and back on again?" (restart the computer)

  9. First thing's first... When you select the game in U-Shoot and click the play icon image.png.2dd11f22b5b0b57ca8f49de8a4f00139.png, does it launch and play?  All the outputs work?

     

    14 minutes ago, wolfenstein0099 said:

    With u shoot I ran the xml for the game after I made u shoot an emulator and I got this.... 

    Edit the game and in the Emulation section, check the box to use an emulator then select the emulator you added for U-Shoot.

    9 minutes ago, wolfenstein0099 said:

    If I try to run u shoot as the emulator it just crashes.

    Then something's not setup correctly.
    Edit your U-Shoot emulator (in LaunchBox) and share [legible] a screenshot of the Details section.

  10. For anyone [else] following, this was resolved after a couple DM's back and forth.

    The Fix: install a fresh copy of MAME and install MSOP onto it.

     

    U-Shoot:

    There's a little writeup I did here on how to add it as an emulator in LaunchBox.
    https://forums.launchbox-app.com/files/file/5633-demulshooter-auto-launcher/?tab=comments#findComment-20827

    But before you can start adding games to use this "emulator", you need to set the games up in U-Shoot itself. 

    Complete instructions for setting up games in U-Shoot can be found on its Wiki page.

     

    If you setup the games per the Wiki and the outputs work when being launched from the U-Shoot GUI, then add the 'emulator' and games per my writeup linked above, and the outputs don't work when launching a game from LaunchBox... I really don't know what to tell you.

  11. Using the 1st method they show (Tools < Import < ROM Files < Single Platform), 
    select Add Folder.

    If your games are like so:
    E:\Games\ScummVM\Beneath a Steel Sky\  
    E:\Games\ScummVM\Day of the Tentacle\  
    E:\Games\ScummVM\The Dig\

    ..the folder you select to add is E:\Games\ScummVM

    image.png.967ec182c1f1cefcdea0b29b35aa049b.png

    Note: you're selecting the folder that contains the games. Not the emulator.  Unless of course you put all the game folders in the same one as your emulator (which might be kind of messy).

    Then on the last screen should show the games.

    Now if those game folders name are off/different/weird, e.g. "001", "002", "003".. as in not related to the games title, you'll get:
    image.thumb.png.96dbc71ace93b358de5f27d7eb03d0c6.png

     

    I believe the importer cross checks the folder name(s) against ScummVM supported games. It's that title that gets sent to the emulator to launch.

    e.g. King's Quest 1
    image.thumb.png.72c4a92d8cf7d109fce9dd16831cd963.png

  12. 20 minutes ago, ShawnS said:

    As for the other point, RA does load faster on subsequent launches but I'd never noticed the initial load taking this long before. It's not a big deal but since it cropped up around the same time as the startup screen thing, I thought maybe there was some relation.

    Well... there was 'some relation'.  Startup screens don't just make it pretty. It also hides computer nuances. ;) 

    22 minutes ago, ShawnS said:

    Thanks for the quick answer!

    You're welcome. Glad it was and easy fix and you learned something new. B|

  13. 52 minutes ago, wolfenstein0099 said:

    I'm also using u shoot for flycast. I was playing house of the dead 2 and confessional mission and it worked perfect with u shoot outside of launchbox. So I know it's hooking. 

    I missed the U-Shoot part.

    1)  So HOTR isn't detecting outputs when launching a game for both MAME with MSOP nor Flycast with U-Shoot from within LaunchBox?

    aka HOTR isn't detecting any outputs when launching a game from LaunchBox.

     

    Let's start with MAME:
    2)  Is it detecting that a game was even launched [from LaunchBox]?  (MAME w/MSOP)
    image.png.fdb8d3381a7f55b2059343e720595d0f.png

    3)  Is the game even starting? Or does it just close and go back to LB?

    4)  You promise that the mame.exe you're testing with is the exact same mame.exe LB is pointing to AND the one you're using outside of LB? 
    I've seen it more-often-than-not that issues like you're having was because the user was testing against different copies of mame.exe.  e.g. Outside of LB D:\MAME\mame.exe and inside of LB D:\LaunchBox\Emulators\MAME 0.288\mame.exe

    5)  In LB when you edit your MAME emulator, in the Plugin Settings, do you have it checked to Let LaunchBox manage these settings?  'Shouldn't' matter. But part of the process-of-elimination.

    LaunchBox isn't going to block anything that the emulator's trying to do. (just so you know)

    Suggestions:
    - Do your testing via LaunchBox. Not Big Box. It's just easier when testing.
    - Double-click HOTR icon in the taskbar to bring up its window so you can see it.
    - Start MAME (or press Alt+Enter when it opens) in windowed mode so you can see both it and HOTD's windows.
        - Or if you have a 2nd monitor, move HOTR to it.
    - [Temporarily] turn off Startup Screens to help see both windows.
    - Have LB/BB start HOTR when LB/BB starts. It has a small footprint. 'Hides' in the background. And you'll not ever have to remember. ;) 
       - Add it via Tools < Options < General < Startup Applications
    - Answer all questions.

    Note: what I mentioned yesterday about the lua script and command-line parameters, that was for the old version of MSOP.  The latest version Just Works™. So disregard.

     

    I tested with MAME 0.288 both outside and inside of LB with HOTR and saw this. So I know it works.
    image.thumb.png.f3918a668e1c1f35b3f3d71e7efc2356.png

     

    U-Shoot:
    That's for another day as it's near-convoluted to setup. But not impossible.

    • Like 1
  14. 32 minutes ago, wolfenstein0099 said:

    I'm having a problem with hook of the repeater and launchbox. Im using u shoot and mame state output project to help with hook of the reaper. Now everything works great outside my launchbox build but when I launch a game, my gun isn't getting the hook. It's only in launchbox. Any ideas of a fix? 

    Any chance you're testing against 2 versions of MAME?  If the one LB is pointing to is MAME 0.289, M.S.O.P. won't work.

    One test would be to right-click a game and select Open MAME. Start a game and check your outputs in HOTR. While you're there, in this MAME's GUI, the top of its window will show its version #.

    If they are indeed and you promise they're the same, show what you have for the command-line parameters (in LB, edit your MAME emulator). 

     

    It seems to me I had to do something on a per game basis to load the lua script(s) via a custom command-line parameters (in edit game). If nothing above sheds any light, I'll take a look at my cab tomorrow and see if I can find what I did.

  15. There're 3 areas to look at for Startup Screens:

     1) Globally under Tools < Options < Gameplay < Game Startup
           Obviously not the issue as it's working with your other emulators.

    2) Per emulator under Tools < Manage < Emulators... [select and edit your emulator].
           In your case, look here 1st and confirm that it didn't inadvertently get disabled in the Startup Screen section, "Enable Game Startup Screen"

    3) Per game.  Edit a game you're seeing this happen with and look in the Startup/Pause section. 
           If Override is not checked, the issue is not here.

     

    6 hours ago, ShawnS said:

    There also seems to be a delay in RetroArch starting up and appearing on screen. I'm not sure if that's LaunchBox running a timer before showing it, or if something is up with RetroArch on first launch.

    You mentioned "on 1st launch".  Is it safe to say that subsequent launches start faster?  If so, it's probably how long RA takes to [first] startup. Once it's been started, like most any other app on Windows, part of it gets put into cache so next time you want to open the app, Window's "got your back" and has it ready to rock & roll (start faster).

    LaunchBox isn't going to delay the startup of a game because hey, that's one of its main purposes. Next to making your collection look pretty, it's there to let you play your games.

    Now, if subsequent startups of RA aren't faster, well... it was probably be hidden by the Startup Screens you no longer see. ;) 

    • Thanks 1
  16. The key to using MAME in LaunchBox is to only have one installation of MAME to-rule-them-all.  "All" being all platforms [it can emulate]. And "one" being just one instance of MAME when you go into Tools-Manage-Emulators.

    The key trick is to have -rompath %romlocation% in your command-line parameters.  Though not really useful for other emulators, for MAME it can save a lot of headaches.  This makes it so you can have your MAME ROMs for any of its platforms** in any location(s).  And ZERO need to create/edit mame.ini.

    To have MAME work with the LaunchBox Pause Screens, leave in -keyboardprovider dinput.

    When you add MAME as an emulator, LaunchBox will by default add those parameters in there for you, along with a couple other useful ditties.
    -artwork_crop -skip_gameinfo -nofilter -keyboardprovider dinput -rompath %romlocation

    LaunchBox should also check 3 boxes. Remove Quotes, Remove file extension and folder path and Attempt to hide console window.

    image.thumb.png.09ede7e25dd5c0e800a1730618381746.png

    **any of its platforms it can emulate in
    e.g. Arcade, Nintendo Game & Watch, Sega Model 2 and any consoles (like Atari 2600)

    For the different platforms, you can name them anything you want. Just as long as in MAME's Associated Platforms they're spelled the same as you named them.

     

    In the end, the above screenshot is all you need for a single MAME emulator instance in LaunchBox for Arcade-type platforms. And it should Just Work™.  Consoles like the Atari 2600 do require some command-line parameters be added to them in the Associated Platforms section. But will work with the above MAME instance.

    Game & Watch, as MAME sees it, is not a console and requires no extracurricular parameters to be listed in the Associated Platforms.

  17. 16 minutes ago, xokia said:

    what's the point of the "use emulator" section (under edit additional versions)? 

    Until recently, Additional Versions, Documents, Links were all Additional Apps. You wouldn't want your "GameMap.png" to open with the emulator.

    Maybe you have a Model 2 game in your Arcade platform that works with MAME. But you have a variant of that game as an Additional Version and you want to use SM2-Emu for that specific version.  Having it there creates for near endless possibilites.

     

    21 minutes ago, xokia said:

    should this all not be added as part of the import wizard?

    It is and it was. That's why your Additional Versions have an emulator assigned to them.

     

    21 minutes ago, xokia said:

    Seems like an import file bug to me. There is now a dependency on filling things out manually after a file is imported.

    I do not recall having to do that in prior versions. Once imported whichever file you selected as default would get launched.
    This is the first time I have manually had to go to emulators and manually point it to a specific emulator after importation. 

    This is the 1st I've heard of someone importing games and having the selected emulator in the Wizard not get assigned to the main game.

    I call it glitch in the matrix, and suspect you couldn't repeat it if your tried.

     

    The good thing is that this was a super easy fix. 
    If you experience this in other platforms, please let us know.

  18. 26 minutes ago, xokia said:

    Clicking Play should start the "default" game correct?

    No.  Clicking Play only launches the ROM that's pointed to in the Launching section, with the emulator that's in the Emulation section.  Clicking Play has no reason to look at Additional Versions.  Can look at it this way, if it's just a single game with no other versions, would it be listed as an Additional Version? (rhetorical question)

    If there isn't anything in the Emulation section (as with a game you start with a batch file or an exe), LaunchBox attempts to execute the file that's in the Launching section.  Which is why I suggested in the 1st place to "double check the emulator that's associated with the game you're trying to launch.  (edit game, Emulation section)".  

    What appeared to be happening was, LB was attempting to execute full/path/to/eboot.bin (aka the file in your Launching section) because there was nothing in the Emulation section. Then Windows wanted to know how you want to open the file.

  19. With RPCS3, if you have auto-import enabled, LaunchBox will pick up all the file types (iso, bin, etc.) for the games [that have been added to the emulator] and add them to your collection.  (vs. a manual Import-File)  But again, they needed to be added to RPCS3 first for LB to 'see' them.

    (maybe something to try in the future)

     

    36 minutes ago, xokia said:

    The eboot.bin is the default main game which the .bin is what its complaining about.

    The secondary game is a .ISO

    The 2 (and only) games I have for PS3 are both bin files and were auto-added to LB (but doesn't matter HOW they were added. As long as they point to the correct file).  They're both 'main' games with no additional apps.

    Here's what one of them looks like.

    image.thumb.png.cc01d60fb1554adc6c077ee065fd0759.png

    image.thumb.png.e2328bafc64cfc197f038014b36d4862.png

    Notice that in the Emulation section, the box is checked and RPCS3 is selected. This way when I click Play, LB sends the full path to that eboot.bin file, to the emulator RPCS3.

    I have it on good authority that if you were to also check that box and set the emulator to RPCS3, clicking Play will start the game without needing to right-click and select the version.  Well maybe not "on good authority" as you refuse to provide the images (which are 'worth a thousand words') I asked for.  So call it "an educated guess".

  20. 59 minutes ago, onebadveggie said:

    As far it running in Launchbox, I used the same script I did for Xemu, but had to add an extra "Send, !{F4}" to get it to shut down completely (I think a single command sends it back to the UI, and the second shuts it down).

    Doing a quick test and using just $Esc::Send,!{F4} (nothing more. Nothing less) in the Running Script worked perfectly here for exiting the game.  Tested on v1.0.104

    Looks like the emulator might have potential. :) 

    • Like 1
    • Thanks 1
  21. 13 minutes ago, xokia said:

    Clearly they are both RPSC3 the "name" was auto added by the importer

    Good.  So as an Additional Version, it is assigned to RPCS3. 

    What about for the main game that is set in the Launching section?  You know.... The one that LaunchBox launches when you simply click Play.  Does it have an emulator assigned to it in the Emulation section?  (...for the 3rd time.)

×
×
  • Create New...