PCLauncher with Battlenet (Diablo III) auto start

[thomas3120]

Hello,

I seem to have steam and origin games start up and go directly to the game.

 

However in Diablo III, which uses Battlenet, I have to press 'PLAY' on the battle net game screen to play/start the game.

 

Is there any way around this? (still using hyperlaunchHQ)

 

any info or suggestions much appreciated,

 

thomas

[thomas3120]

Just seeing if i'm on the right track:

 

Do I need to add under 'add emulator' each game I want to add toward the bottom:

 

Also above adding lnk extension in global PCLauncher throws an error but games are all in green and don't work.  I have to leave extensions blank.  The roms point to a folder with the game shortcuts

 

Here i have the steam ID, but i didn't want to use the steam ID.  What would I place/point to in the Application box and also what in the AppWaitexe box?  (a bit confused on these)

 

I'm doing this under SYSTEM Settings instead of GLOBAL Settings....is this correct?

 

 

This is under PCLauncher Modules(or vice versa)

 

 

Does this look correct, inis for each game?

 

Last thing, I was wondering if someone could kindly post an ini of a steam game.  I've read the ini pclauncher and it explains a bit on steam games but not 100% clear on it yet.

 

any help is appreciated

 

thomas

[bulbousbeard]

You don't need to launch D3 (or WOW) through Battle.Net.

 

You can launch the D3 binary directly. You just need to add the "-launch" switch.

 

C:\Program Files (x86)\Diablo III\Diablo III.exe -launch

 

That's got it.™

[Metalzoic]

I am really confused about what you have going on there...
 

Just seeing if i'm on the right track:
 
Do I need to add under 'add emulator' each game I want to add toward the bottom:
 

Also above adding lnk extension in global PCLauncher throws an error but games are all in green and don't work.  I have to leave extensions blank.  The roms point to a folder with the game shortcuts

 
Not sure what you mean about "add emulator" for each game. These are PC games so they don't use an actual emulator. PCLauncher is the correct "emulator" like you have set, but it's a virtual one.

 

You also have a Rom Path set, but these are PC games. Not roms. You normally just point each game to it's EXE or its SteamID in the PCLauncher module and leave the rom path blank (Although it looks like you're pointing to shortcuts instead of the exe?). Far as I know you shouldn't need a rom path unless you are running a non-pc game under the same wheel. 

 

These aren't roms being run by an emulator so you shouldn't be adding extensions under Global>Emulators>PCLauncher. 
 

 

Here i have the steam ID, but i didn't want to use the steam ID.  What would I place/point to in the Application box and also what in the AppWaitexe box?  (a bit confused on these)
 

I'm doing this under SYSTEM Settings instead of GLOBAL Settings....is this correct?

 

The Application box is where you're supposed to put the path to your PC game (like I mentioned above). The path to the games EXE goes there, although I think you can also put the path to a LNK shortcut instead if you want... I'm curious why you're using shortcuts? However Steam games are a bit different, for those you leave the Application blank and put the Steam ID number in its box instead (matched to the SteamIDs.ini in the modules folder).

 

The AppWait.exe box is similar to setting your Fade Title. Sometimes RcoketLauncher needs help to know what window/exe to focus on for your game. Not all games need anything extra, but if they do you can try setting the Fade Title setting or the AppWaitExe setting. You can click the ? by each for instructions, but basically for AppWaitExe you would put the main exe that you want RocketLauncher to focus on. Fade Title uses the Window_Class instead of the exe. You only need to add something there if a game is giving you focus issues and you only use one of them. One might work better than the other depending on the game. (foe example MKX works better with AppWaitExe set to MK10.exe, JamesTown needs FadeTitle set instead and most games don't need anything in either)

 

These are PCLauncher module settings under your PC system, so they aren't System or Global settings... 

 

 

This is under PCLauncher Modules(or vice versa)
 

 
Does this look correct, inis for each game?
 
Last thing, I was wondering if someone could kindly post an ini of a steam game.  I've read the ini pclauncher and it explains a bit on steam games but not 100% clear on it yet.
 
any help is appreciated
 
thomas

 
Not sure what you have going on here either. I have a ton of Steam and non-Steam games and not a single one of them has it's own .ini file in the RocketLauncher>Modules>PCLauncher folder. 

So I have no INIs to show you for Steam Games. The games individual module settings are in the PCLauncher.ini within that same folder. I have no idea what those INI's you have are from or why they are there.

EDIT: Unless they used to be done that way instead of setup in the SteamIDs.ini file?

 

Then again maybe you're just doing it all in a way I'm unaware of.

 

Is HyperLaunch 1.1.1.4 a really old version of HyperLaunch? I'm using RocketLauncher now, but I was using HyperLaunch before and it was really no different. I still basically setup PC games now just like I did then.

[Metalzoic]

I don't know if this helps, but there are some PCLauncher/Steam tips in this thread.
http://www.hyperspin-fe.com/topic/8766-pc-games-and-steam-games-together-under-one-system/

My post is #7 and has some tips.
This thread was about running Steam and Non-Steam games all from one wheel, but might help out if you read it all.