Jump to content
LaunchBox Community Forums

Headrush69

Members
  • Posts

    1,370
  • Joined

  • Last visited

Everything posted by Headrush69

  1. Also, make sure you have emulation turned off. When switching from Teknoparrot to JConfig i've had that bite me a few times. (Forgetting to turn emulation off)
  2. That was indeed the issue. This helps as I can make a folder for my custom layouts and not worry about updates replacing them.
  3. I tried that in the past and it didn't work. Maybe it had some kind of identical naming issue between the sets, I'll check it out again.
  4. Do you mean having multiple bezels in different layout files per game that you can flip between? If so, do you know exactly which version? I mostly use Bezel Project themed bezels, but there are dynamic features and overlay support in some MAME artwork sets and the ability to swap them easily would be super useful just while setting up bezels. Currently I have to swap back and forth between artwork folders, find the features I'm missing that I want and than manually add them to the layout file for the Bezel Project artwork. Additional question: Would the Bezel Project accept the inclusion of updated layout files that add things as simple as colour overlays, or lit graphics if they were optional and never changed or affected the single bezel image?
  5. I don't use those modes with my Dolphinbar, but as neil9000 said, in those modes the IR part of the Wiimote will appear as the system mouse so you just configure Daphne Singe the same as the mouse. For the other buttons on the Wiimote, you have to look at the Dolphinbar instructions for how it maps the other buttons to key equivalents. Than it is just a matter of changing the config.ini within the Daphne Singe folder to match. (file name may be different depending on which exact variant of Daphne Singe you are using)
  6. Headrush69

    Mame.xml

    Do you have MAME installed in a directory that requires elevated rights? Do you get the same error if you try to write the file to a different location?
  7. I think that version is quite dated and it looks like no commits since 2019. I would try the Retroarch mupen64plus core that is constantly updated or even try m64p emulator if you dislike Retroarch. PS: To each his own, but I never cared for Project64. I used it in the past for some mods and it seemed OK, until you saw it running with an accurate 64 emulator and noticed thing that were missing or not right.
  8. Not sure exactly what you're trying here. Easiest approach is run this core through Retroarch. This should install without issue and doesn't have anything to do with LaunchBox. (This mod runs perfectly fine with it)
  9. You have to find someone who has created a layout file that has a bezel and both screens already, or create one yourself.
  10. Like neil9000 mentioned, if you only connect a USB power source, you wouldn't have the bluetooth functionality. Dolphin can connect to a bluetooth adapter in your PC other than the Dolphinbar, but in my experience it never worked flawlessly like the Dolphinbar. Finding the specific bluetooth adapter that has all functionality isn't easy either. The Dolphine forums have some documentation on this you can check out if you want to try.
  11. Since you are already set up with RockeLauncher, you have the option of using RocketLauncher with LaunchBox as well. (You can do only some platforms or even just individual games) I only use RL with a couple platforms, but there are some things it does better. One specific issue that relates to your type issue: some Teknoparrot games take longer to start (Mario Kart) than LaunchBox's timed startup screen, and you get those startup windows showing sometimes. Since RL actively waits for the game window before hiding the startup screen, you don't have that problem.
  12. Just give them a different platform name when you import them, but make sure to set Scrape As to Arcade.
  13. Run some games in window mode with task manager running to see if something else is running. Windows Defender or virus scanning apps that get enabled can do things like that.
  14. You have to unselect the check mark on the Root level as well.
  15. Not exactly. You assign your keyboard keys to map to this Retropad abstract controller. You can see the defaults in retroarch.cfg. I have set all mine to nul and than in a core override (which is saved in Retroarch/config), I set the keys I want for that specific core. Here is an example from my my Stella core: So now in Retroarch, you will see those keys are set to those Retropad buttons. What the remap does, is it allows you do re-assign the Retropad buttons to different emulator functionality. For example, if Retropad button A is set to punch, you can remap Retropad button B to punch. Remaps change the Retropad assignments to the emulator function, not your keyboard keys. Retroarch controller mapping does seem different at first, but once you wrap your head around it, there are lots of advantages. You also have to remember Retroarch is dealing with so many cores, while an individual emulator is only dealing with one, so they need flexibility that straight keystroke mapping can't handle. Just a heads up, I've noticed with the flycast core, it seems some things have to mapped to specific Retropad buttons. For example in Naomi racing games, whatever key I choose, (or joystick button), has to be mapped to Retropad L2 and R2 for analog controls like gas pedal and brakes to work. Hope that helps.
  16. When you select keyboard, this represents the device connected to the emulated machine, not your keyboard. The L2 and R2 in your screenshot are Retropad virtual buttons and you do not appear to have them mapped to your physical controller yet. Once you do you will see your physical controller listed after Port 1: You haven't said what controllers you are using, or if just a keyboard, but changing keycodes (which also map to the virtual Retropad buttons), can be done in your retroarch.cfg file or added in a core or file specific override. Something like this: You can see here Retroarch default keyboard key mappings to virtual Retropad
  17. When it comes to MAME roms, names really don't mean much, it's all about the checksum. You can always use to see the checksums for the files it expects. Then you would have to compare with the checksums for the files within your intv.zip rom. (If you have 7-zip installed, its has a right mouse click contextual menu for getting checksums)
  18. You have to change into the directory mame.exe is in then.
  19. Are you in the directory where mame.exe is located? Are you using Powershell or command prompt? If Powershell, make it .\mame.exe
  20. Thanks as always. I've noticed lately that you stopped including the plain gameplay video in your collections, any reason for that? The only reason I ask is I still haven't decided on which theme I'm going to use and might not go with the unified theme videos. I keep flipping back and forth and can't decide. 😉
  21. Nah. Nothing wrong with the channel but I'm not interested in Android emulation news (which he seems to cover a lot) and basically he just reading change logs in most of the videos I have seen. Would prefer to see video of changes of improvements and updates he mentions. I just check the The General Emulation Wiki page and I can see emulation updates very quickly and research more or update if I see something that interests me.
  22. Just an FYI, looks like MAME specifically has some improvements in 0.243 to deal with the Apple IIgs joystick issues. I'm sticking with 0.242 for a while due to some possible regressions with new developments made in 0,243 for other systems, so I haven't checked whether the Apple IIgs improvements help yet. Edit: I broke down and tried 0.243 in a separate install and some joystick issues are fixed but I'm still seeing issues in some still, especially Gauntlet. Using the Joystick Calibrator referenced in the MameTester page for the bug, it seems analog values outside the expected byte size (0-255) occur, especially on diagonals. It could be the app itself but seems input still isn't perfect for analog joysticks.
  23. LOL Glad you got it working. When I first started with LB, similar problem drove me crazy.
  24. In the import options did you select Allow Duplicates? Sometimes when a rom doesn't import I find it's because LB thinks it's already installed. Since text between ( ) and [ ] which are used in hack rom names a lot aren't used when importing the rom, that could be part of the issue.
  25. To clarify, are you saying they aren't added into LB or that meta data isn't downloaded? As Retro808 mentioned, The LB database doesn't have hacks roms, so unless you are scraping using a platform that matches where Emumovies has them (and it has those hacks), you won't get that meta data added.
×
×
  • Create New...