Jump to content
LaunchBox Community Forums

launcherbox

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

2 Neutral

About launcherbox

  • Rank
    8-Bit Processor

Recent Profile Visitors

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

  1. Cheers guys, turning off RDTSC via Advanced Settings seems to work. I can then enable it on a per-game basis via each game's config file and adding : [General] useRDTSC = true
  2. Same issue here. Followd BSoD's 1.14 instructions to the letter, and nothing Wii U/Cemu related is working for me through LB
  3. Hi folks Windows 10 Latest LB RA 1.7.3 I've set up Neo Geo MVS and Neo Geo AES as platforms (I know the differences are minor, but hey), and have imported games for each platform. I'm using the fbalpha2012_neogeo core to handle the running of games on both platforms. The problem I'm having is that within the core options using the GUI, I can change the Neo Geo system to either be AES, or MVS. It saves this setting in the retroarch-core-options.cfg file as "fbalpha2012_neogeo_neogeo_mode = "MVS", or "fbalpha2012_neogeo_neogeo_mode = "AES" depending on how I set it using the GUI. However, I'm unable to affect this setting using an --appendconfig, or a core override. No matter what I do, RA will pull the setting from core-options.cfg, meaning I've to manually change the system using the GUI every time. Is there any way anyone can think of to specify an append or override here, so I can have AES and MVS based on directed setting, rather than a manual switch each time?
  4. I'm having issues with AHK myself, it doesn't seem to be doing, well, anything 🤔
  5. Nevermind, figured it out. It's stupidly easy 😳 You basically just find the logo you want, and name it as it's named in LB, and drop it into the folder that houses the logos for your chosen theme.
  6. Hi folks, I downloaded and installed the lovely Y2Guru Plain and Simple theme for LB Big Box. It's a lovely little theme, and I love the clean buttons/icons that display the name and logo of each platform. However, I have a number of non standard systems set up like Famicom, Famicom Disk System, Satellaview, Neo Geo Pocket Color, Taito Type X/2, Turbo Grafx-CD, and MSX2 which have no icons, only the name of these systems is displayed. Is there a way I can add in icons for each system, and have the theme display them? If so, are these icons freely available to find?
  7. Hi folks, as per thread heading, I would love to be able to set up Additional App settings for an entire platform, rather than just per game one by one. I've found this thread which details what to do quite well, apart from one thing; it deals with only having one additional app. In my own particular setup, I need x2 additional apps set up for the system to work correctly. I can't seem to adapt the above mentioned tutorial to work with x2 additional apps, and am obviously getting lost somewhere with all the copying/pasting specific parts of the platform xml file. Please help 😕
  8. Ok, just for the sake of completion and if anyone else ever has this problem, I've figured it out. Basically, the best I can deduce is that because the version of AHS within Launchbox closes when LB closes, it's not persistent (meaning the second the emulator is closed, AHS closes too, leaving it unable to fulfill tasks post emulator shutdown). How I got around this is as follows: 1) We need to run AHS independently of LB, so we can control it beyond emulator shutdown. So first, you need to create your own .txt file, and give it a name like myscript.ahk. You then edit this file (I use Notepad++), and I inserted this code: #SingleInstance, Force #Persistent SetTitleMatchMode, 2 DetectHiddenWindows, On SetTimer, ProcessCheckTimer, 2000 Return ProcessCheckTimer: Process, Exist, javaw.exe pid1 := ErrorLevel If (!pid1) { Run, F:\Tools\Xpadder-v2014.01.01\Xpadder\Xpadder.exe /C ExitApp } *the path to Xpadder will need to be adapted to your own installation path In essence, what's happening here is that the process javaw.exe is being checked to see if it's running (ParaJVE runs under Java), and when it's not found to be running (as in when you exit the emu), the Xpadder shutdown command is ran. 2) You need to then use Additional Apps to run Xpadder BEFORE the emu starts by creating a run before app profile under Additional Apps 3) You then create a second instance of an Additional App profile, and for the application .exe path, you point it towards you myscript.ahs. You will also need to associate AHS files within windows, with the AHS application itself found in the Launchbox installation folder. So you basically have told LB to boot Xpadder before the emu starts. You're then telling it to run your new script when the application ends, and this script takes care of shutting down ParaJVE for you, and it all closes nicely. This is probably very convoluted, I don't really know, I've no experience with scripting, but for whatever reason, ParaJVE does not play nicely with LB when you need LB to recognise the emu has shut down.
  9. Ok, just for the sake of completion and if anyone else ever has this problem, I've figured it out. Basically, the best I can deduce is that because the version of AHS within Launchbox closes when LB closes, it's not persistent (meaning the second the emulator is closed, AHS closes too, leaving it unable to fulfill tasks post emulator shutdown). How I got around this is as follows: 1) We need to run AHS independently of LB, so we can control it beyond emulator shutdown. So first, you need to create your own .txt file, and give it a name like myscript.ahk. You then edit this file (I use Notepad++), and I inserted this code: #SingleInstance, Force #Persistent SetTitleMatchMode, 2 DetectHiddenWindows, On SetTimer, ProcessCheckTimer, 2000 Return ProcessCheckTimer: Process, Exist, javaw.exe pid1 := ErrorLevel If (!pid1) { Run, F:\Tools\Xpadder-v2014.01.01\Xpadder\Xpadder.exe /C ExitApp } *the path to Xpadder will need to be adapted to your own installation path In essence, what's happening here is that the process javaw.exe is being checked to see if it's running (ParaJVE runs under Java), and when it's not found to be running (as in when you exit the emu), the Xpadder shutdown command is ran. 2) You need to then use Additional Apps to run Xpadder BEFORE the emu starts by creating a run before app profile under Additional Apps 3) You then create a second instance of an Additional App profile, and for the application .exe path, you point it towards you myscript.ahs. You will also need to associate AHS files within windows, with the AHS application itself found in the Launchbox installation folder. So you basically have told LB to boot Xpadder before the emu starts. You're then telling it to run your new script when the application ends, and this script takes care of shutting down ParaJVE for you, and it all closes nicely. This is probably very convoluted, I don't really know, I've no experience with scripting, but for whatever reason, ParaJVE does not play nicely with LB when you need LB to recognise the emu has shut down.
  10. Hi folks Just looking to see if anyone can help me with ParaJVE (Vectrex emulator that runs under Java), and Xpadder. I want Xpadder to start when I launch a Vectrex game, and I want Xpadder to close when I quit the emu and return to LB. The script from early on in this thread certainly boots Xpadder, but it won't close it after I quit ParaJVE. Script here: Run, C:\Xpadder\Xpadder.exe /m $Esc:: { Run, C:\Xpadder\Xpadder.exe /C Process, Close, {{{StartupEXE}}} } Obviously I've altered the paths to Xpadder to suit my own installation. I have a feeling that Launchbox isn't recognizing when ParaJVE has closed, and therefore isn't executing the secondary part of the script to close Xpadder. I can manually close Xpadder via the command prompt with the above command, so the syntax is fine, it's just LB doesn't know when to execute it I feel. I'm wondering if it's possible to maybe alter the script to check for an instance of Java running, and if so, fine, if not, exit Xpadder?
  11. Thanks very much for the help Kondorito. The script you linked to above (once I have changed the paths to Xpadder.exe) will indeed start Xpadder, but will not close it when ParaJVE closes 😞 The best I can reason is that Launchbox has difficulty in recognizing that ParaJVE has closed as a process
  12. Hi folks, just wondering if anyone might be able to help me with this issue. Basically I've used Zombeaver's excellent guide to get ParaJVE set up, configured, and working in Launchbox. Lovely little emu, and for the most part, plays lovely with LB. That is, until I went to start a game...damn, no controller support in ParaJVE. So I figured I needed a mapper, so I used Xpadder, which again, works perfectly. I can now launch, play, and exit games in ParaJVE through LB. Cool. Next problem, I need Xpadder to launch before ParaJVE...no problem, LB has me covered. I use the Additional Apps feature to configure Xpadder to start before ParaJVE starts, and it works flawlessly. I now boot a game, Xpadder will launch, it'll load the profile, ParaJVE will launch, the game will boot, I play the game, and exit it. Perfect. Only problem is Xpadder remains active/running. Fine, I'll add a second instance of an Additional App configuration to stop Xpadder when ParaJVE is closed down. Here's where the problems begin. For whatever reason, LB cannot 'see' what the status of ParaJVE is, because when I create a second instance of Additional Apps to close Xpadder upon exiting ParaJVE (automatically run after main application), Xpadder will close right after it's launched. No matter what way I configure the additional app settings to close Xpadder, it just either won't close, or closes while ParaJVE is still running. I can't get it to close Xpadder, when I exit ParaJVE. So after some research, I found suggestions of maybe creating a autohotkey script. This one (tailored for my needs) is the one I've tried: #SingleInstance, Force #Persistent SetTitleMatchMode, 2 DetectHiddenWindows, On SetTimer, ProcessCheckTimer, 3000 Return ProcessCheckTimer: Process, Exist, javaw.exe pid1 := ErrorLevel If (!pid1) { Process, Close, Xpadder.exe ExitApp } Return ^^ I'm no scripter, but from what I understand, the above basically is asking that the process "javaw.exe" is checked to be running or not (this is needed for ParaJVE), and if it's not found to be running, then the process of Xpadder.exe is closed. However, it doesn't work. When I quit ParaJVE, Xpadder still will not close. Has anyone any ideas on how to get Launchbox to close Xpadder when I quit ParaJVE? Pretty please?? Edit: Windows 10 fully updated Launchbox Premium fully updated Xpadder 2014.01.01
×
×
  • Create New...