Jump to content
LaunchBox Community Forums

MCF

Members
  • Posts

    51
  • Joined

  • Last visited

Everything posted by MCF

  1. Can you go into the Xpadder Wacky Races folder and see if there's any EXE files in there? Use these steps to create an AHK script Launch Notepad Copy and paste the line below in Notepad and save it as "script.ahk" in a convenient location (i.e. Desktop, Documents), as suggested by @Retro808 $ESC::WinClose, ahk_exe your wacky races executable file Download the Autohotkey package from https://www.autohotkey.com/download/, in the ZIP file is a Compiler folder. AHK2EXE is there, this is the tool used to compile the AHK script into an EXE application The source script file is the script.ahk that was created in Step 2 above For the destination EXE file, name it as EXIT.EXE (or any other file name you like, so long as the extension is EXE) and place it in E:\Torrents\Wacky Races Click Convert Go to E:\Torrents\Wacky Races and check if EXIT.EXE has been created If yes, added EXIT.EXE as an Additional App for Wacky Races in Launchbox, and set it to Automatically Run Before Main Application
  2. Try this workaround... Just simply set any EXE for the game's application path in the Launcher tab (i.e. notepad.exe), and leave the Emulation tab blank.
  3. I avoid Retroarch entirely, and am currently using MAME for my NeoGeo emulation needs. Let me know if you're interested for advice/tips on how to use MAME to emulate NeoGeo instead. Doesn't matter if it's MVS or AES.
  4. This AHK script $Esc:: { Process, Close, whatever the game exe is } Just save the above as an AHK file, and then use the AHK2EXE tool to compile it. Note the red colored section of the script needs to be changed to the name of the game executable. However, @neil9000 is right, this is not the recommended way to exit from a PC game as the risk of corruption of your save games is high. Better to exit properly via the game's menus.
  5. My bad, forgot this was for PC games. Try these steps and let me know the outcome (I have not personally tested it) Download the Autohotkey package from https://www.autohotkey.com/download/, in the ZIP file is a Compiler folder. AHK2EXE is there. Convert the AHK script to an EXE and place it in the same folder where the PC game is. Add the EXE as an Additional App in Launchbox, and set it to Automatically Run Before Main Application.
  6. This is what I do with FS-UAE, and has been working flawlessly for normal Amiga titles and CD32 titles Create a configuration for the game in FS-UAE Launcher, the model must be set to CD32 These config files are saved with the extension fs-uae in the Configurations folder where you store your FS-UAE emulator (i.e. D:\emus\FS-UAE\Configurations) For CD32 and CDTV titles, I create a subfolder called CD32 under Configurations (i.e. D:\emus\FS-UAE\Configurations\CD32). This step can be skipped if you would rather have all your Amiga fs-uae files in the same folder, it doesn't matter. In Launchbox, I set the Game folder path for the CD32 platform to D:\emus\FS-UAE\Configurations\CD32, and the fs-uae file is the ROM file
  7. Are you using WHDloads or the ADF floppy images?
  8. I configure warp to the R2 button on my 8bitdo controller using the option below. There is a Controllers folder where you store the FS-UAE emulator, and in there would be a CONF file for your controller. Just open it in Notepad to see what the button labels are. The sample below is from the CONF file created by FS-UAE for my controller, you should have something similar as well. [default] include = universal_gamepad axis_0_neg = lstick_left axis_0_pos = lstick_right axis_1_neg = lstick_up axis_1_pos = lstick_down axis_2_pos = left_trigger axis_3_neg = rstick_left axis_3_pos = rstick_right axis_4_neg = rstick_up axis_4_pos = rstick_down axis_5_pos = right_trigger button_0 = south_button button_1 = east_button button_10 = menu_button button_2 = west_button button_3 = north_button button_4 = left_shoulder button_5 = right_shoulder button_6 = select_button button_7 = start_button button_8 = lstick_button button_9 = rstick_button hat_0_down = dpad_down hat_0_left = dpad_left hat_0_right = dpad_right hat_0_up = dpad_up
  9. Try this and let me know the outcome $Esc:: { Send !{f4} Process, Close, DemulShooter.exe }
  10. Use something like this, just change the red-colored portion of the AHK below to the executable of the game $Esc:: { Process, Close, whatever the game exe is }
  11. Hi everyone, I just created my very first tutorial video, which has been uploaded to my YouTube channel Retro Emulation Nation https://bit.ly/retroemulation Please check it out and let me know what you think.
  12. I am currently learning PowerShell as part of my day job, and I figured I can move away from AHK and use PowerShell for automating stuff in Launchbox as well. This is my first stab at it, designed to get the infamous Project Phoenix Emulator to work hand-in-hand with Launchbox. It's not 100% PowerShell though, as I could not figure out how to move the mouse pointer without AHK. So an AHK script is embedded in Base64 to the PowerShell script. To give credit where it's due, the inspiration for this came from the tool made by @jophran SETUP INSTRUCTIONS Refer to THIS ARTICLE to download the emulator and the translation patch (Yeah, the interface is in Cyrillic and the patch is to translate it to English) Once the emulator has been patched, launch it and click on the 3DO and Jaguar icons on the left to have the emulator generate the requisite settings Search online for 3DO - FZ-10.bin and put it in the 3DO\BIOS folder Search online for [BIOS] Atari Jaguar (World).j64 and put it in the Jaguar\BIOS folder Launch the emulator Click on the 3DO icon and select File > Add BIOS file to the collection to connect the BIOS file Click File > Open CDROM image and simply pick any 3DO game to add to the emulator Click on the Jaguar icon and select File > Add BIOS file to the collection to connect the BIOS file Click File > Add CARTRIDGE file to the collection and simply pick any Jaguar game to add to the emulator Steps 6-9 are required to generate the required lines in the emulator's configuration file for the launcher to work. Close the emulator Download the attachment below. Put PhoenixLaunchbox.exe in the same folder where the Project Phoenix Emulator is Set PhoenixLaunchbox.exe as the emulator in Launchbox, add -Filename as the Default Command-Line Parameter. No other changes are required FEATURES It will automatically load the 3DO or Jaguar core, depending on your ROM/ISO file extension It has an embedded AHK script in it to automatically press the Power button on the emulator. Because it is based on the relative position of the window, ensure the toolbar is at the top of the emulator window The emulator will go to fullscreen 2 seconds after the game starts Pressing Escape on the keyboard will kill the emulator, like most other emulators LIMITATIONS The compiled executable is 64-bit only The Project Phoenix Emulator will popup an Android button in the toolbar from time to time, ensure the Android button is set to the same line as the main toolbar, otherwise the AHK script will cause the Android button to be pressed instead of the Power button Anyway, I hope y'all like it, and feel free to comment and suggest improvements / enhancements. Will upload this to the DOWNLOADS section once I am able to spend more time testing it and looking out for errors and areas for improvement. Project Phoenix Launcher.zip
  13. I am using 3DO - FZ-10.bin for 3DO and [BIOS] Atari Jaguar (World).j64 for Jaguar.
  14. MCF

    Sega CD

    Have you tried using KEGA Fusion instead? At least to isolate if the problem lies with the BIOS or the Sega CD disc images? In Launchbox, are you pointing to the CUE file to load these games?
  15. What format are your CDTV images in? It should be BIN+CUE all compressed in a ZIP, that's what works for me. Also ensure the CUE file is pointing to the BIN file correctly. Note that CDTV and Amiga CD are two different things. I have the CDTV versions of Defender of the Crown, Xenon 2, and Psycho Killer setup with FS-UAE, and they all work.
  16. If you really want to pick and choose, download from (link removed) That's what I do anyway ? As a general rule, just check the file size and go for the largest one For Super Street Fighter II Turbo, the parent ROM would be the World 940223 version since it's 11.64MB in size while the other versions (clones) are significantly smaller. I hope this helps.
  17. Definitely weird What happens if you try to manually add one of those missing games using the Add Games button on the lower right corner of the screen? Is it able to save and launch?
  18. I am using BizHawk to emulate ColecoVision ?
  19. I was able to convert many X68000 games from DIM to HDF. Downside is because HDF is a virtual hard disk image, every HDF file clocks in at 9.95MB, even if the game size is just 1-2MB. Just have to convert DIM to XDF, dump it in the HDF and manually edit AUTOEXEC.BAT If there's demand, I will do a tutorial video (when I can find some time away from my corporate day job that is)
  20. Go to the Emulation tab, tick Use Custom Command-Line Parameters and enter -port2 superscope
  21. Try downloading the latest version of KEGA Fusion from https://www.emucr.com/2017/10/kega-fusion-364-xbrz-15.html?m=1
  22. Thanks for the MAME tip. Will have to check it out! I am maintaining both emulators to run CD-i games since some games only work on MAME and vice versa
  23. Hey all I had been using MAME to emulate CD-i, but it had many drawbacks such as the lack of proper fullscreen, the annoying CD-i text at the top of the screen, and needing to press a button to actually start the game. And I REALLY wanted to play Mutant Rampage Body Slam, which couldn't load in MAME. So I went off to try the CD-i Emulator, and unfortunately it has neither keyboard nor gamepad support, and controls are restricted only to using the mouse. And switching it to fullscreen requires actually clicking options in the menu bar. And it's not even really fullscreen, it just maximizes the window. AHK and JoyToKey to the rescue for a proper fullscreen + gamepad solution! Please refer to the Launchbox-specific instructions below. Download CD-i emulator Download JoyToKey Look for and download the required BIOS cdimono1.zip Download the file attached to this post Extract everything to the same folder Ensure cdirunner.exe, JoyToKey.exe, VistaAPI.dll, cdi200.rom, cdi220.rom, and cdi220b.rom are in the same folder as wcdiemu-v053b3.exe Rename wcdiemu-v053b3.exe to wcdiemu.exe. This is to ensure this AHK app doesn't need to be edited and recompiled if the emulator needs to be updated to other versions in the future. Launch JoyToKey and configure a profile for CD-i with the following button mapping suggestions Configure a new emulator in Launchbox, set it to cdirunner.exe Ensure your CD-i ISOs are in ISO format, for some reason I couldn't get this to work with BIN+CUE or CHD. IsoBuster is my tool of choice to convert the CD images to ISO Import your CD-i game of choice to Launchbox, and enjoy! FEATURES AND RESTRICTIONS Both the original AHK source and the EXE executable are in the ZIP file The CD-i emulator will launch in proper fullscreen, like all other normal emulators The EXE was created using AHK2EXE, and is designed for 64-bit Windows only. If you're running 32-bit Windows, you will need to use AHK2EXE to recompile the AHK script to an EXE executable Press ESC to exit the emulator and kill all the associated processes, so there's no need to manually configure the Running AutoHotkey Script for the emulator in Launchbox All game file names must be one word, i.e. "Hotel Mario.iso" must be renamed to "HotelMario.iso" or "Hotel_Mario.iso" CDI Fullscreen.zip
  24. I made a derivative of Fayne Aldan's genius work. FEATURES ? Launches np21.exe in fullscreen Pressing Esc on the keyboard will terminate runner21.exe, np21.exe, joytokey.exe, autohotkey.exe LIMITATIONS ? Hardcoded to work only with np21.exe, will not work with any other variants of the Neko Project emulator (although this can be altered in the provided AHK file) 64-bit executable, will only work on 64-bit version of Windows Must be stored in the same location as np21.exe Ensure that you don't have anything that launches Autohotkey.exe before using this The following two files from the JoyToKey package must also be in the same location as np21.exe JoyToKey.exe VistaAPI.dll runner21.zip
×
×
  • Create New...