Jump to content
LaunchBox Community Forums

Your_Friendly_AI_Overlord

Members
  • Posts

    485
  • Joined

  • Last visited

3 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Your_Friendly_AI_Overlord's Achievements

32-Bit GPU

32-Bit GPU (5/7)

123

Reputation

  1. In LaunchBox > Tools > Manage > Emulators > Dolphin (your first screenshot), in the Default Command-Line Parameters, change: /b /e to -b -e
  2. Some of that you can already do. Click the drop-down menu on the left side of LaunchBox and select [Games Missing Media].
  3. It could indeed be the audio device used. Laptops utilize the onboard audio chip when using the laptop speakers. When switching to HDMI out, you must also switch to the HDMI audio device in Windows.
  4. Yeah... It probably wasn't a good idea to binge watch Bassie en Adriaan before watching The Matrix. All I can think now, maybe Bassie is The One. 😉 Dreamcast games should be unpacked before launching. Bios files must be placed in the system\dc folder, still zipped. Dreamcast games usually come in bin/gdi, bin/cue or cdi format. Naomi games are zip or zip/chd and should not be unpacked before launching. (If you unpack a zipped naomi game, it would contain romfiles with names like epr-21868.ic7.)
  5. You need to set up m2emulator with a fullscreen resolution your display accepts. So maybe you use a resolution that works on your laptop screen, but doesn't on your tv. (via HDMI)
  6. You need dc_boot.bin and place it in the RetroArch\system\dc folder. Look HERE for more information about the bios files you need (and the Flycast core in general). Also, if your Dreamcast game is compressed with zip, you need to extract the zip before launching. And make sure your games work in RetroArch directly before adding them to LaunchBox. Are you sure you actually have a Dreamcast game? Sega Naomi is the equivalent arcade hardware and shares a lot of the same games with the Dreamcast.
  7. This seems correct. When you press the button you have entered under "Close the Active Window", LaunchBox sends a virtual key press of the Escape key for emulators that close with Escape natively. TeknoParrot should close with Escape natively. In the TeknoParrot settings make sure that "Confirmation prompt on exit" is unticked. And that "Global Hotkeys > Exit Game Key" shows the virtual-key code: 0x1B. 0x1B = Escape. If this still does not work, you can try the following and see if it makes a difference: - Disable Startup- / Shutdown screen for your game or TeknoParrot in general. - Check if you run TeknoParrot with Admin rights. --> Run TeknoParrot as normal.
  8. Recently the PS3 XMB (XrossMediaBar), the PS3's user interface, started (partially) working in RPCS3. As of yet you can't launch games from the XMB and only PSN games show up. I expect full functionality will be implemented in future updates. But it may be fun to tinker around with it a little. - Update RPCS3 to the latest version. - First get the XMB working in RPCS3 directly. Download the latest PS3 firmware from Sony's website and install in RPCS3. (RPCS3 > File > Install Firmware.) Then, File > Boot VSH/XMB. - In launchBox add vsh.self, found in rpcs3\dev_flash\vsh\module, as a rom file to your Playstation 3 platform. More information about the XMB in RPCS3 here: https://www.reddit.com/r/emulation/comments/rv3kzb/rpcs3_vshxmb_now_booting_on_the_master_build/
  9. Once I had stability issues myself. My pc would randomly BSOD. Sometimes once a week, sometimes twice a day. I had this issue for two years. Turned my pc inside out. Did a fresh install of windows. Reinstalled drivers more than once. Run memtest for 12 hours. Moved drives to different SATA connectors. Down clock my CPU. Etc.. Nothing worked. Until one day I thought it could be the SATA cable to my system drive. Changed the cable and, Yes. Perfectly stable ever since. Sometimes the cause of stability issues is something trivial like a dodgy SATA cable. You could try removing your GPU drivers with DDU. https://www.wagnardsoft.com/forums/viewtopic.php?t=3847 and then installing the most recent one.
  10. Some other options: 1.) Run a Windows system integrity check. Open a command- or powershell window with admin rights and enter: sfc /scannow 2.) In the LaunchBox\Updates folder, install your last update over your current build. Be careful to install to the LaunchBox folder and not LaunchBox\LaunchBox (a double folder). Also check if you are on the latest LaunchBox version (that your license permits). 3.) From your LaunchBox\Updates folder, install LaunchBox to a second location on your PC. Preferably on a different drive. Add some games and emulators. If your second installation does not crash, you know something is wrong with your current build. If it does crash you have to look further. In all honesty, I rarely read about LaunchBox or BigBox crashing or rebooting a PC and I never experienced it myself. It's more likely to be either a corruption in your current LaunchBox build, or a Windows or hardware issue.
  11. I just added After Burner to LaunchBox (12.6). For me images download and display just fine. I don't use themes though. The LaunchBox DB ID must show #6236. If it doesn't click the red square with the cross and click "Search for Metadata" again. After that go to Media > Images and click "Download Media" in the bottom right corner.
  12. Have you refreshed your images in both BigBox and LaunchBox?
  13. Make sure that in LaunchBox > Tools > Manage > Emulators > RetroArch, the checkbox "Extract ROM archives before running" is unticked.
  14. Not to mention, do your games run in RetroArch directly? If they don't, there's no point in troubleshooting LaunchBox yet.
  15. This is necessary because LaunchBox pulls metadata from mame.exe. Metadata RetroArch doesn't have. I do not use RetroArch for Mame emulation, so I can't help you much. But this is important: - The games must run in RetroArch first. - Make sure that in LaunchBox > Tools > Manage > Emulators > RetroArch, "Extract ROM archives before running" is unticked and that in the "Associated Platforms" tab, everything is set up properly. - All games must be set to use RetroArch as the emulator. You need to tell Mame standalone the location of your roms. Either via the Mame gui > Configure Options > Configure Directories > Roms, or by editing mame.ini. Yes, this is a hard requirement.
×
×
  • Create New...