freeflyer454
-
Posts
34 -
Joined
-
Last visited
freeflyer454's Achievements
8-Bit Processor (3/7)
8
Reputation
-
Dang. It might only work if a hot key is set to trigger it. I don't have a lot of experience with AutoHotKey so I'm just guessing. Well, I'll look at adding that feature to the rom launcher in a few days.
-
Just did a quick search for the AHK command to move the mouse. In LaunchBox, go to Tools > Manage > Emulators... then edit the entry for the Phoenix Rom Launcher. On the left side of the window, look for Running Script. Inside there, paste the following: MouseMove, 0, 50, 0, R That *should* move the mouse down 50 pixels from it's current position when the Phoenix Rom Launcher is run. I haven't tested it for certain, but you can play around with it and see if that does what you're looking for. Hope that helps.
-
Sure, the program is written in AutoIt, so it'd just be a simple line of code and recompile it. I'm offshore atm and won't be home for another week or so, but you can try it yourself. Or look into adding a similar AHK script to launchbox when it launches the phoenix-rom-launcher. Either way could move the mouse for you. Hope that helps.
-
As far as I know, the Phoenix emulator doesn't have a way to launch directly into fullscreen mode. Doesn't seem to be any commandline options for that. This launcher app I made uses Phoenix's keyboard shortcut to go fullscreen as soon as it's launched. Works pretty good.
-
Sorry.. had some new priorities come up. Still plan on working on this when I get a chance.
-
Thanks. From just looking at it, the program should determine the platform easily since the path contains both the word "Jaguar" and the extension ".J64". So I may have to dig a little deeper into it to find where the undeclared variable is. I'll try to come up with a fix soon.
-
Hmm.. ok. If you don't mind, what's the full path & name of your rom that you're launching? I'll see if I can figure out what's going on with it. It's strange to me that it's giving a "Variable used without being declared" error. You'd think it'd pick that up when the program is being compiled, but so far, they've all compiled cleanly.
-
I think that error means the Rom_Launcher can't determine the platform for the rom being launched. Is this the original Rom_Launcher from the first post that you are using? That one used key words in the rom's path to determine which platform it was for. The versions I created on the 2nd page of this post also used the rom's file extension to determine the platform. They haven't been fully tested so I haven't updated the original post with the newer version yet, but I think they should work better.
-
I finally got around to adding this feature. It compiled cleanly, but I haven't tested it out yet. The route I went was to just add an entry to the launcher's ini file. You'll see it listed as "AHK_script=". Not sure if it'll work with just the name (if in the same directory) or if you'll need to supply the full path in quotes. So basically, after launching Phoenix, the launcher will run the AutoKey() function if it's been enabled. If it's disabled and there is a value in the script's path variable, then it will launch that script. Also, this assumes AHK is installed and ahk scripts are associated with the AHK program. Let me know if this works. I'll try to do some testing with it and maybe add a section for it to the GUI once I have time. _Phoenix_Rom_Launcher.ini _Phoenix_Rom_Launcher.exe
-
Hmm... is your idea to integrate the features of your AHK script into the rom launcher or is it to use your AHK script on the launcher & Phoenix? Your AHK script could probably be launched through LB alongside the launcher (disable the AutoKey feature) and modified to kill both the launcher & Phoenix on confirmation of exit. Have you tried that yet? Trying to incorporate the features of your AHK script into the rom launcher would involve figuring out controller input in AutoIt. It seems there are some rudimentary examples of controller input with AutoIt, but that'd take some time to test & play around with it. Edit: Forget that... I see what the issue is. Without the AutoKey feature turned on, the rom_launcher immediately exits after launching Phoenix (so an AHK script launched through LB wouldn't work in that scenario). And with the AutoKey feature turned on, it kills Phoenix as soon as Esc is pressed and then exits. Another option might be to have the rom_launcher launch your AHK script. I think AutoIt can launch AHK scripts using ShellExecute("path\to\script.ahk")
-
So, I looked into it some last night. I couldn't strictly use the rom's file extension because Phoenix accepts some common extensions (".bin", ".binar", ".rom") for multiple platforms. but all the rest of the extensions for various rom files I can use as a filter to determine the platform. I combined that with my previous way of filtering for common system names. So, I think that solution will work a majority of the time (though I haven't had a chance to test it yet). Here's a quick updated version I cooked up last night - if you want to give it a test drive. I'll look into the AHK script you provided. I'm not sure if AutoIt can handle controller input - I'll have to investigate that one. But at least the variation 1 should be do-able. _Phoenix_Rom_Launcher.exe
-
Ah... that's good to know. I didn't realize that's how LaunchBox handled compressed roms. I think I did it the way I did because that was the easiest way to determine which platform the game was being launched for. I need to know the platform since the xml nodes are in different node paths between platforms. I guess a more fool-proof way would be to compare the game's file extension with lists of extensions for each platform. I'll look into implementing that and updating the script. I need to update the script here anyways (got another version that works with ColecoVision roms now). I'm working offshore at the moment, but I'll try to get it done in a day or two (hopefully).
-
Phoenix: Jaguar emulator - how to automatically start games?
freeflyer454 replied to legolas119's topic in Noobs
It's not necessary. That's just a feature I added to the program to easily kill the Phoenix emulator with the Esc key. I believe me & some other people had problems getting the AutoHotKey feature in LB to work with Phoenix, so I just put my own version of it into this program as a convenience. -
Phoenix: Jaguar emulator - how to automatically start games?
freeflyer454 replied to legolas119's topic in Noobs
One thing you'll have to do after you import the new games into Phoenix... you'll need to delete the old "_Phoenix_Rom_Launcher.xml" file. The way I wrote the script, it won't overwrite it's backup file, so you'll have to do that manually before making a new backup (otherwise, the backup utility will only keep giving you the "Restore" option). -
Phoenix: Jaguar emulator - how to automatically start games?
freeflyer454 replied to legolas119's topic in Noobs
Yes, it'll work like that. Only thing is if you ever do a restore from that backup file, you'll have to setup the bios-es again. You could always just copy over the bio settings for those systems from the config xml to the backup xml. Not that big of a deal, though. Glad you got it working.