Jump to content
LaunchBox Community Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


sundogak last won the day on February 24

sundogak had the most liked content!

Community Reputation

95 Excellent

About sundogak

  • Rank
    32-Bit GPU

Recent Profile Visitors

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

  1. sundogak

    execute key

    So you backed up the file and deleted it like suggested?
  2. sundogak

    execute key

    If talking keyboard bindings rather than controller, then go to Launchbox\Data\BigBoxSettings.xml and either manually edit (scroll through and look for key you want to change), or backup file and delete it.
  3. See here on instructions for Flycast core. For games that need CHD files you need them as well and they need to be in path structure that the core wants to see. Snip from the instructions: How to play NAOMI Games:¶ Run NAOMI games stored in MAME format zip files by following the same process as standard Dreamcast games Run NAOMI GD-ROM format games stored in MAME zip + chd format by running the zip file through RetroArch. The zip file should be stored in your roms folder with the chd file in a subdirectory of the roms folder named after the mame ID. Example (MAME ID=ikaruga) - [ROM FOLDER]/ikaruga.zip - [ROM FOLDER]/ikaruga/gdl-0010.chd
  4. See attached example. Goes in your MAME\ini directory. Just change any plugins you want to "1" and any you want off to "0". # # PLUGINS OPTIONS # cheat 1 cheatfind 0 console 0 data 1 discord 0 dummy 0 gdbstub 0 hiscore 1 layout 0 portname 1 showcp 0 timer 0 plugin.ini
  5. See this thread below for attempts to make it work. Highlights: 1) One issue is the RA core is version 1.8 of Hatari and standalone is up to 2.2 2) tos.img file needs to go in the Retroarch\system directory. 1.02 (CRC32 = D3C32283), others may work but that is what have. 3) Some have noted that needs hatari.cfg file in Retroarch\system directory. I have found RA will run regardless as long as tos.img is in system directory. The path to the image directory is driven by RA. But if you do have it in the system directory, doesn't "hurt" anything. Note that the paths are normal Windows path format not the Linux format used in the instructions. See example attached. Note: Hatari loves to stick things (nvram, and autosaves for example) in the Users\###\AppData\Local \Hatari folder by default (for 2.2). The RA core one likes to stick things in Users\####\.hatari So if hit F12 when Hatari is running (as well with RA core) will see where paths are set as well as other emulation settings. If you hit save cfg in the F12 screen it will dump a full CFG file similar to standalone. Haven't played with it enough in RA core to see if it will take all those settings or not. 4) .st extension files seem to work for me. However, I and at least others in the thread below couldn't get the .ipf files to work. Core says it works with them but all games I have tried get stuck at white screen and will not boot. Again, might be some combination of settings but suspect it is just an old version not playing well. 5) End result: Standalone is easier, works relatively quickly out of box, and is updated. I have Steem and Hatari working. I prefer to use RA where possible as well, but when you get to the computer emulation they have lots of issues and the benefit of unified controller is less of an issue since most times you are stuck with hitting the keyboard at some point. YMMV. I hatari.cfg
  6. I added the new ScummVM as a separate emulator. If use the pointer files in this thread it will get you 90% there. I didn't do for every version/game but you get the idea. I used EpicFails launcher prior but he would also need to update plugin since his DB internal to the program doesn't pull all the codes for the new games. One advantage (like the internal LB method) is that it works with Pause Screens which is what originally sent me down the path since wanted access to manuals in pause. Pause screens, at least on my setup, never worked if using the batch file method. The other is that this will also work with Retroarch with no changes since pointer files have GameID files in the text file as well.
  7. take a look at this thread as well for MAME setup.
  8. If using a "common" directory structure the following zip file has the text pointers formatted correctly for RA and LB. If you have different directory naming then won't be as useful but can see what text files look like and/or drag into the appropriate folder. Once they are in the directory you just tell LB to look for any file with *.scummvm in name and import those only. If setup the ScummVM emulator as noted above then it will launch the games using the text file game ID. ScummVM LB Pointer Txt Files in Directory Structure.7z
  9. The version that comes with LB isn't updated yet to 2.1.0 (after all ScummVM was just finalized today). Additionally, the built in settings within LB will need to be updated to reflect the new codes that are supported in 2.1.0 which is why you don't see them in LB. LB wouldn't know which codes they were or what games were to be supported until ScummVM folks finalized things. Since you are not using batch files you can go another route in the mean time. Basically, you do as follows: 1) Add the new ScummVM emulator EXE path like any other emulator (version 2.1.0 downloaded from ScummVM site). 2) make sure to to check "don't use quotes" and the "use file name only without extension..." 3) In the default command line parameters insert command that points to location of your scummvm.ini which can be anywhere but in my case I keep with the EXE location rather in my User directory so it is portable: ScummVM -c "G:\Emulators\ScummVM\ScummVM\scummvm.ini" --no-console -f the -f just tells it to go to full screen. All other settings are taken from your INI file. 4) Go to the directory with a new game and make a text file with the name of the Game ID. In the case of Blade Runner, it is bladerunner-win. The extension can be anything but I use scummvm since that is also what Retroarch likes. If you open the text file and also insert the game ID (i.e., the same as title without extension) then Retroarch will also work in addition to normal emulator installed above. 5) Then add the "rom" like normal within LB by pointing it to the bladerunner-win.scummvm file. See below example. 5) If you want to find the game IDs for other new games just open up the ScummVM emulator and go to the game after you added it and click "Edit Game" and will see ID on first tab. Setting a dummy text file with the name will allow LB to launch the game with the above settings.
  10. Assuming you are talking game themes, go to the LB folder under videos and then whatever platform name you want to add to. Then under that platform add the videos in the "Theme" directory. Example below for MAME. If you are talking about themes for LB itself then you can put videos under the specific LB Theme (as one option):
  11. ...all whopping $3.02 of it which brings my total haul to $13.09 (got $10.07 last year). The original claim per the class action was "up to $65". For those who may not recall/or were not around for the whole ordeal see link here: https://www.cnet.com/how-to/ps3-other-os-settlement-claim-how-to/ Now I wasn't delusional that would get the much (if anything). However, I always find these class action settlements "educational" from perspective of how long the legal system takes to work through all this. This claim form was submitted in October 2016. Sony was sued in 2011 and the final settlement was in 2017. I think I bought my "fat" PS3 ~2009 (which still have). For the original claim (~2014), I had to submit a scan of the boot disc showing it was used for multiple OS capability. Of course, that was a hilarious requirement since you could just label any old CD-R disc and scan it to "count". Ultimately the judge threw out the original claim process saying it was too complicated and that there wasn't enough money (originally $55) going to claimants. The 2016 era settlement required you show your serial number (or PS3 gamer ID) and "attest" you knew/used the OS function. Obviously, the lawyers burning through 9 years of billable left little left for the settlement. I was never that worked up with Sony on this since I treated the other OS capability as a curiosity. But it is an example of how these cases are meaningless from compensation to end users (witness the abomination of the Equifax settlement). Anyway, off to go pickup a "King Size" KitKat with my additional bounty, just in time for Halloween. 😀
  12. 1) Easiest: Just directly install LB on external drive. Then it will download media there and don't have to go through all that. I have mine on external "G" drive. So all LB files are on G:\LaunchBox\... If concerned about caching speed (i.e., internal is SSD, external mechanical) then there is way around that. There is a thread here that shows how to keep the LB cache on C drive via virtual links and free utility. If both your external and internal are mechanical drives likely not worth messing with the cache location. 2) Alt: Adjust paths in edit platform to external drive location. It will then download to wherever you tell it. You will have to manually adjust each platform initially but will not have to do after the first time. Could do via XML file with search /replace rather than the platform window to speed it up.
  13. @kidshoalin Region log os go in playlist folder like noted below and as path noted in the linked screenshots. They don't go in separate region folder since LB just treats them like any other playlist.
  14. @kidshoalin on your question on where these go, look here for discussion and screenshots (click on "sundogak relied to a topic" link). and here
  15. @kidshoalin FX3 is already made, look at thread page 22.
  • Create New...