Difference between revisions of "PCLauncher"
Jump to navigation
Jump to search
Line 132: | Line 132: | ||
|- | |- | ||
|ExitMethod | |ExitMethod | ||
− | |Define | + | |Define an alternative way to close your launched primary application, if desired, to exit your Application in case it doesn't close with your RocketLauncher exit keys. |
− | * | + | *WinClose Application: Closes the window of the application. |
+ | *WinClose AppWaitExe: Closes the window of the window of the AppWaitExe if defined. | ||
+ | *Process Close Application: Force closes the application executable. This may prevent save data from being saved and should be used as a last resort. | ||
+ | *Process Close AppWaitExe: Like above, but force closes the AppWaitExe if defined. | ||
+ | *Send Alt+F4: Simulates an Alt+F4 key sequence which some applications require when WinClose does not work. | ||
+ | *InGame: Disables any RocketLauncher exit keys for this application. You will be required to close the application by it's internal methods. This is recommended for most PC Games so all data is saved on exit and no accidental terminations occur. | ||
*'''WARNING''', if fading is enabled on exit, make sure you test your ExitMethod choice works, otherwise you might get a blank screen while game never closed. | *'''WARNING''', if fading is enabled on exit, make sure you test your ExitMethod choice works, otherwise you might get a blank screen while game never closed. | ||
|- | |- |
Revision as of 01:36, 26 March 2016
Description
PCLauncher gives you the ability to launch any PC Application via your favorite Frontend. It differs from the other modules that RocketLauncher treats it slightly differently in some internal checks:
- You do not need a Rom_Path defined
- You do not need Rom_Extensions defined
- You do not need an Emu_Path defined
Features
All of the following can be defined per-game:
- Can launch separate Pre-Launch (before application runs), Post-Launch (right after application launches), and Post-Exit (right after application exits) scripts or executables
- Daemon Tools Lite support for mounting disc images. Useful when a game has protection, like a CD-check. Can run executables from the root of a mounted image.Add parameters to the CLI of your application
- Use a window title and/or ahk_class of your application to hold up the module for correcly timed Fade support
- Adjustable ExitMethod by using either a hard exit (Process, Close) or a friendly exit (WinClose)
- Steam support for launching games solely based on their SteamID
- Steam Browser Protocol support
- Origin support coming soon!
- URL launching support
- Adjustable "working folder", useful for GoG games that need a different folder when the application exists somewhere else
- Cursor hiding
- Relative paths supported for all path-related keys
INI Keys
First create a [Section] for each game, named after your database name.
Key | Description |
---|---|
Application | REQUIRED (when not a steam game) The directory (path) and executable, batch, or shortcut (lnk file) to your application.
|
AppWaitExe | This will be the exe, if different then the Application, that you want the script to wait to close.
|
DiscImage | Path to a disc image (ccd,cdi,cue,iso,isz,nrg) if required by a game, usually for a cd check. Only fill this key if a cd/dvd image is required by your game.
|
DXWndGame | Set this to true if this game should be launched with DXWnd to force it to run in windowed mode.
|
DXWndMaximizeWindow | Set your preferred method when DXWndGame is enabled.
|
Parameters | This can be any number of parameters that you want to supply to your application. |
SteamID | If you are launching a Steam game, provide the ID of the game here. Example: SteamID=105600
|
OriginGame | (NOT IMPLEMENTED YET) Set to true if this is a game using the Origin Service. If true, it will allow automatic logging into Origin so you do not get stuck at a login prompt while loading. |
WorkingFolder | Mostly for GoG games, allows you to set a different working directory then the default directory (the one Application exists in) |
PreLaunch | This can be used to run another application before launching the Application. This will usually be blank.
|
PreLaunchParameters | This can be any number of parameters that you want to supply to your PreLaunch application. |
PreLaunchSleep | If you need the script to wait after launching your PreLaunch app for a set amount of time, put that here (1000=1 second).\ |
PostLaunch | This can be used to run another application after the Application has launched, but before the module waits for the Application to close. This will usually be blank.
|
PostLaunchParameters | This can be any number of parameters that you want to supply to your PostLaunch application. |
PostLaunchSleep | If you need the script to wait after launching your PostLaunch app for a set amount of time, put that here (1000=1 second). |
PostExit | This can be used to run another application after the Application has closed. This will usually be blank.
|
PostExitParameters | This can be any number of parameters that you want to supply to your PostLaunch application. |
PostExitSleep | If you need the script to wait after launching your PostLaunch app for a set amount of time, put that here (1000=1 second). |
ExitMethod | Define an alternative way to close your launched primary application, if desired, to exit your Application in case it doesn't close with your RocketLauncher exit keys.
|
FadeTitle | This is the Window Title & Class of your application.
|
FadeInExitSleep | Adds a sleep right before Fade exists (1000=1 second).
|
HideCursor | True or False - hides the mouse cursor and restores it on exit.
|