Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Whilst the proxying did start the PA BDO version just fine, the controller still did not work for me :(
Is this expected to work, or am I out of luck for this?
I imagine since console process is kept open for steam's tracking that the controller events actually go to it and not to the game process
and placed these files into that DIR, renamed it to Magicka.exe and edited the config.bat accordingly, i set the non steam game to my BDO DIR and the BDO exe and when i launch it it does say I am playing Magicka with the Green and does not disappear when i sign in, however the overlay is not active i cannot access remote play or any other functions
1. Install BDO on Steam
2. Open the steam install dir for BDO
3. Rename 'BlackDesertLauncher.exe' to 'Steam_BlackDesertLauncher.exe'
4. Copy 'BlackDesertLauncher.exe' and 'BlackDesertLauncher_Config.bat' from the BDOLaunchProxy zip[ github.com ] into the install dir.
5. Set NONSTEAM_LAUNCH to 'Steam_BlackDesertLauncher.exe'
this is my config
@echo off
set DEFAULT=1
set TIMEOUT=5
set STEAM_LOCATION="D:\Steam\steamapps\common\Black Desert Online"
set NONSTEAM_LOCATION="D:\Steam\steamapps\common\Black Desert Online"
set STEAM_LAUNCH=Steam_BlackDesertLauncher.exe
set NONSTEAM_LAUNCH=Steam_BlackDesertLauncher.exe
https://github.com/Stapleton/BDOLaunchProxy/releases/tag/1.2
So far bat2exe doesnt allow the config file to work properly. Seems like when i call the config script to add all your install variables for the script to use, bat2exe just stores all of that in the exe instead of reading the file from disk. This makes the application basically useless as the config no longer works.
I tried using iexpress built into Windows to create the exe for it however this is immediately having issues with not finding the script to run even though its supposed to also extract it out of itself so this problem shouldnt happen.
Until i find a solution to this distribution issue or someone beats me to it, the work around will be to use the program i used to create the exe.
Figured out a solution as i was writing this. I will be pushing a new commit with the updated exe, a new release version, better distribution, and maybe a quick how to create the exe yourself.