Jump to content
LaunchBox Community Forums

MCF

Members
  • Posts

    51
  • Joined

  • Last visited

Posts posted by MCF

  1. DOSBox-X is a fork of the original DOSBox with additional features, including support for PC-9801!

    Below are the steps I used to get PC-9801 working effortlessly with Launchbox.

    1. Go to https://github.com/joncampbell123/dosbox-x/releases to download the latest release of DOSBox-X. I use the mingw win64 sdl1 build, however you should experiment and see which suits you best.
    2. In LaunchBox, create an emulator for DOSBox-X and set -set machine=pc98 force ibm keyboard -fs -conf as the Default Command-Line Parameters.
      image.thumb.png.118e711aaa547a3599c196d1d3d52888.png
    3. Add the following AHK to Running Script to allow quitting DOSBox-X by pressing Esc, and then click OK to save the emulator
      $Esc::
      {
      	Process, Close, dosbox-x.exe
      }

      image.png.6fea7abc9cfab8e603203c2d4b13f3ce.png
    4. Create a conf file with the same name as the game HDI file and edit is as below. Please take care to change the location of the HDI file in the IMGMOUNT command, as this is just using my setup as an example. Explanation on the options at the bottom of this article.
      [sdl]
      output=openglpp
      [render]
      frameskip=0
      aspect=false
      scaler=none
      [autoexec]
      IMGMOUNT C "D:\Games\NEC PC-9801\Briganty.hdi"
      BOOT C:

      For FDI floppy files, please refer to the sample CONF file instead.

      [sdl]
      output=openglpp
      [render]
      frameskip=0
      aspect=false
      scaler=none
      [autoexec]
      IMGMOUNT A "D:\Games\NEC PC-9801\Rude Breaker.fdi"
      BOOT A:
    5. In Launchbox, set the launching ROM file to the CONF file.
      image.png.4cca647ac921ddbdf6b16b3b9b7b21f1.png

     

    EXPLANATION ON OPTIONS IN THE CONF FILE

    • To read up on what options are available when making your own CONF file, please refer to https://github.com/joncampbell123/dosbox-x/blob/master/dosbox-x.reference.conf
    • By default, DOSBox-X will load the CONF file dosbox-x.conf in the directory where you have DOSBox-X installed.
    • The alterations in the game specific CONF files as above will supersede whatever is configured in dosbox-x.conf, so there is no need to edit that file.
    • I prefer output=openglpp because it provides pure sharp pixels without any filtering. If you want simple bilinear filtering, change it to output=opengl or output=surface, depending on which you personally prefer. Additional options are available if you read the dosbox-x reference conf in the link above.
    • the [autoexec] section is an absolute must, otherwise the game will not boot and you're just greeted with the PC-9801 Z: prompt.

    Do let me know how the instructions above work for you, and I hope this makes life easier for emulating PC-9801 games :)

  2. As the title suggests... how do I change the fullscreen resolution in FS-UAE?

    I am using FS-UAE Launcher in conjunction with Launchbox to manage my Amiga and Amiga CD32 games... but it is stuck at 1920x1080 fullscreen instead of capturing my desktop resolution of 3840x2160.

    I have reviewed both https://fs-uae.net/video-options and https://fs-uae.net/configuration-files

    These are my current Video and Advanced Video in FS-UAE Launcher.

    image.thumb.png.4b46abe60df83e376f6825efc874b051.png  image.thumb.png.61336d0b31b90d7522fdf89cdb6bbf00.png

    Below is one of the sample fs-uae config files I created in my Configuration folder.

    [fs-uae]
    amiga_model = A1200
    fast_memory = 8192
    hard_drive_0 = D:\Games\Amiga/Chaos Engine 2.zip
    x_whdload_args = ChaosEngine2AGA.Slave PRELOAD

    Appending the following 2 lines did not do anything, and it still loads in 1920 x 1080.

    fullscreen_width = 3840
    fullscreen_height = 2160

    Any help is greatly appreciated. Thank you.

  3. I only setup the Mouse and Superscope games in Launchbox... other SNES games I play on a Super Nt. :)

    Some games like Shien's Revenge and Mario & Wario are really fun mouse games, and do not work with controllers.

    I have the 24 April SNES9X Git installed, and have the Fullscreen on ROM Open checkbox ticked, but the results are still the same. Sending 7 just does not work on my PC.

    I gave up setting up the AHK for the mouse in SNES9X and switched to Mednafen. Thanks for all your help @JoeViking245... SNES9X is just being stubborn on my PC I guess.

    • Game On 1
  4. I have Mednafen in D:\Emulators\Mednafen, and I want to use it for NeoGeo Pocket and NEC PC-FX.

    Unfortunately double clicking on the game in Launchbox does nothing.

    I know it's not a problem with Mednafen, because I can launch the games from the Command Prompt, i.e. mednafen.exe "D:\Games\NeoGeo Pocket\faselei.ngc"

    Please advice

  5. On 4/26/2023 at 11:55 PM, JoeViking245 said:

    Download and tested a game and the following worked for me.

    WinWaitActive ahk_exe snes9x-x64.exe
    send 7

     

    This assumes your executable is "snes9x-x64.exe".  Didn't need the key delay (which some emulators do. i.e. MAME) and the WInWaitACtive alleviates any guessing games for the Sleep timer.  Be sure it's above any escape sequence.

    image.png.df6cbb7227fd4feaa1f7c58e4f8dcc81.png

    If that still doesn't work for you, then there's something else wonky going on.  It'd also mean it's time to move to BigBox and a proper controller. ;) 

    Could this be failing becuase I configured SNES9X to be fullscreen by default?

  6. 40 minutes ago, JoeViking245 said:

    I've never used SNES9x.  Does the Use Mouse not work?

    image.png.124e56fb5c14fe23e01da314635ecff6.png

     

    Regardless, if you find you still need to press 7 to switch controllers, you may try adding a SetKeyDelay.  You'll also need to add a delay/pause/wait because the running script executes right away.  You want to wait a little for the emulator to actually be running before "pressing 7".

    Sleep, 5000
    SetKeyDelay, 125, 50
    Send, 7

    "5000" = 5 seconds.  Adjust accordingly depending on how long it takes for the emulator to be fully loaded.

    I want to eventually use BigBox and not require using keyboard and mouse :)

    Unfortunately the suggested AHK did not work... I had set a variation of Sleep, even delaying up to 20 seconds did not work

    This is different from the KEGA Fusion emulator (which I use to emulate Sega Master System games), and the following AHK to send F12 works

    Sleep 5000
    Send {F12}

  7. Not sure if this was posted, but I couldn't find this in this topic

    I am having problems enabling mouse in SNES9X

    I have -port1 mouse1 added as a parameter to the emulator, but I find that it still requires my pressing 7 to actually enable it in SNES9X

    I tried the following AHKs in the Running Scripts section, to no avail

    • SendInput {vk47}

    • Send, 7

    • Send 7

    • Send {7}

    • SendInput, {7}

    • SendInput, {Raw}7

    Any help is greatly appreciated.

  8. On 1/19/2021 at 5:19 AM, polygonslayer said:

    Cheers, but I just checked and nothing shows up in the log :/
    It's really strange. Double clicking the exe it doesn't even seem to appear in the task manager most of the time. Could some sort of windows update have screwed up something that the emulator depends on?

    Really hard to say in these cases :(

    My script is just basic PowerShell converted to EXE, so there shouldn't be any compatibility issues.

    You may try configuring the Project Phoenix emulator itself to launch in Windows 7 or Windows XP compatibility mode and then try again?

    • Like 1
  9. 2 hours ago, polygonslayer said:

    Hey, I've been thinking of ditching Rocketlauncher finally (only used for some emulators, like Phoenix), but I've just noticed that Phoenix doesn't boot at all any more for me. Even when trying to manually boot the exe. Tried a fresh download as well.
    It's really strange since I had it working a few months ago and I haven't touched it since and now the emulator doesn't want to even start. It pops up in the task manager for a split second then vanishes. Anyone else had a similar issue?  :/

    This launcher sounds like exactly what I need once I can just get the emulator to boot. haha

    Any help would be greatly appreciated. Thanks :)

    You may want to check your System log in the Event Viewer, there should be something there that shows why it crashed.

    • Thanks 1
  10. I am using a humble Intel NUC7i3BNH

    It's only a 7th gen i3 processor, but it gets the job done and I can emulate all the 8-bit and 16-bit consoles perfectly.

    32-bit emulation is limited only to 3DO, CD-i, and PS1.

    Redream and PPSSPP works well for most titles, but anything above that it out of the question.

  11. On 5/31/2020 at 9:31 AM, bundangdon said:

    Thanks a lot for the quick response. While using the startup screen, this is what I get
    Untitled-1.thumb.jpg.1fe219c10ad6aeb4a50d7022def24ad8.jpgAnd nothing happens beyond that. I can only guess that the startup screen interrupts the plugin, hence causing the whole thing to stop completely

    I believe you're right... does it work if you disable Startup Screen?

    The commands require the Project Phoenix emulator to be the frontmost window

  12. 20 hours ago, bundangdon said:

    This works great and I really appreciate this plugin. The only problem is that it won't work when using Launchbox's startup screen plugin. Is there any way to fix this issue?

    I don't use the Startup Screen feature in Launchbox. I just did a quick test and it loaded fine for me.

    What happens when Startup Screen is enabled and you launch the emulator?

  13. On 5/26/2020 at 3:45 AM, Kid said:

    I have the same issue with just some of the WHDloads (*.LHA files).

    Every .LHA that I have tried within FS-UAE launcher works fine. But some do not work when using Launchbox/Bigbox (with FS-UAE) receiving the error above in SpuRge's first post. The error is the same for the games that don't work, just the game name within the error changes obviously.

    I though I fixed this issue last year setting up FS-UAE as portable but I can't find the post and forgot to document it :(

    Cheers,

    Kid

    I had the same problem too, but my solution was to convert the LHA files to ZIP, which solves the problem :)

    CHD

    The CHD must be stored in a folder that shares the same name as the MAME ROM.

    Using Killer Instinct as an example, the MAME ROM file is kinst.zip. The CHD must be stored in a folder named kinst in the same directory where the ROM file is stored.

    5PlvcqB.jpg

  14. On 5/16/2020 at 5:41 PM, Bellozanne said:

    Thanks very much chaps!

    Still struggling with Dragon's lair but will soldier on!!

    I'm probably overlooking something simple

    I have followed the above tutorial step by step but keep gettin Princess Daphne screaming "Save me!!"

    any other thoughts would be most welcome

    B.

    After you get the error, look for the file daphne_log.txt in your Daphne directory

    It should provide greater detail on what went wrong

  15. On 5/8/2020 at 2:30 PM, squaretac said:

    Hi MCF,

    Yes. Please point me in the right direction. 

    This is my MAME settings for NeoGeo (please ignore those other associated platforms)

    pMy6mHv.jpg

    The BIOS file neogeo.zip needs to be in the ROMS folder in your MAME directory. You can look around online for it.

    -bios unibios32 is not mandatory, it's only used if you want to use Universe BIOS (see http://unibios.free.fr/)

    Please ensure all your NeoGeo ROMs follow MAME's naming convetions, i.e. Samurai Shodown must be samsho.zip, Fatal Fury is fatfury1.zip, and so on and so forth.

  16. On 5/11/2020 at 7:08 AM, Cnells2000 said:

     

    Untitled.jpg

     

    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

    1. Launch Notepad
    2. 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
    3. 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
    4. The source script file is the script.ahk that was created in Step 2 above
    5. 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
    6. Click Convert
    7. Go to E:\Torrents\Wacky Races and check if EXIT.EXE has been created
    8. If yes, added EXIT.EXE as an Additional App for Wacky Races in Launchbox, and set it to Automatically Run Before Main Application
×
×
  • Create New...