Jump to content
LaunchBox Community Forums

Charco

Moderators
  • Posts

    1,001
  • Joined

  • Last visited

Posts posted by Charco

  1. Yeah, the Motorola 68000 CPU was used in a lot of arcade boards at the time, so the Sharp x68000 is home to a wealth of arcade perfect ports. Capcom actually used x68000s as their dev machines for their CPS1 games.

    Whether it's worth emulating is really down to the number of x68000 exclusives you might be interested in playing. Theres a great version of Castlevania on there called Akumajou Dracula and the system has quite a few exclusive shoot 'em ups that are worth checking out, Cho Ren Sha 68k being worthy of mention. If you are into shoot 'em ups, it's worth checking out as it's a genre that is English-friendly.

    If you are already using RetroArch, there is a good x68000 core available.

  2. 5 minutes ago, johnnyskullhead said:

    the titles do look really long

    bit confused re- Try simplifying the name of your .cue and .bin files, don't forget to adjust your .bin file name change in the .cue file using notepad.

    If you edit the name of the .bin file, ensure to open the .cue file in Notepad and update the filename that it is pointing to, otherwise it will not launch the game.

  3. There's a fair bit of complexity there between RetroArch, Rocket Launcher, and Big Box, so it might be difficult to diagnose this issue. Can you first test to see if this happens when using RetroArch on it's own so that we can rule out the other applications and see if this is RA-related?

  4. Here's a script to launch Yatagarasu Attack on Cataclysm in full screen from the launcher:

    #SingleInstance force
    Loop
    while WinExist("YatagarasuLauncher")
    {
    Send, {Tab}{Enter}
    ExitApp
    }

    Just point LaunchBox to the launcher and this script should do the trick.

  5. 14 hours ago, kmoney said:

    @Jason Carr I have experiencing a weird issue with my startup of LaunchBox and it has been happening on and off ever since you added the startup speed increases to LaunchBox a few betas ago. I have been holding off saying anything thinking it could be unrelated. My LaunchBox startup time and loading interface was usually around 3 seconds before you added the startup speed increase a few betas ago. It is usually about 3 seconds startup time after you added that increased startup speed but sometimes randomly it will take about 10 seconds for startup and the longest of that seems to be stuck on loading interface.

    It seems to happen most often when I havent used LaunchBox for a while. I can launch LB and close it and relaunch back to back many times in a row and it will always startup in about 3 seconds but if I do not open LB for a while like overnight the first launch of LB will take about 10 seconds and then other times it will not do this. I was thinking at first it could be Windows Defender scanning folder at startup but I have added exclusions to LB and BB.

    I know it seems like a weird issue but I did not have it until I downloaded that beta with the increased startup time and I remember when I downloaded that particular beta it took about 25 seconds to reload LaunchBox which is unusual for that one time only.

    If I start LB or BB after booting up my PC it takes twice as long to start compared to if I have opened already, closed it, and opened it again.

  6. I am wondering if he meant using a keyboard in BB though? Like press F on your keyboard to go to F in your game wheel? I imagine the vast majority of people use BB with a controller or joystick, but I guess it would be no harm if it were to be added. 

  7. Hi there, I've used x360ce for some Windows games but not with emulators so far. I just drop the exe in the same folder as the game exe and run it, map the buttons, and it just worked. I have not used it with my Switch Pro controller yet though, just a USB snes pad.

    • Like 1
×
×
  • Create New...