05-04-2024, 08:03 PM
Trying to set up my laptop with Disco. Disco is loaded as is net framwork but I cannot fin the launcher to get my stuff installed. Any help would be greatly appreciated as I am NOT a techy person
05-04-2024, 08:03 PM
05-04-2024, 08:10 PM
(05-04-2024, 08:03 PM)Doc Holliday Wrote: [ -> ]Trying to set up my laptop with Disco. Disco is loaded as is net framwork but I cannot fin the launcher to get my stuff installed. Any help would be greatly appreciated as I am NOT a techy person
I think that the default install location is C:\Users\YourUserName\AppData\Local\Discovery Freelancer 4.91.0\
if it's already installed.
To download it go to https://github.com/Lazrius/DSLauncher (do this on the new computer if you haven't already)
Also, you'll need the account export file from the machine that you played on before.
This is done by selecting all accounts in the accounts list in the launcher, (of old computer) and right-clicking anywhere there, then clicking
"export selected accounts". This newly created file should then be found in the location listed above and after transferring it to the new computer, also to the location above, it can then be used in the newly installed launcher by right-clicking in the accounts list areas and then clicking,
"import launcher accounts". ( It should see the export file automatically if it was put in the right directory)
After which you should see your player accounts in the new launcher.
I hope this helps.
05-13-2024, 10:08 PM
Is Alley (the person listed on the Launcher info as launch code writer) still around, or anyone else with code knowledge?
My launcher always halts around 1720k memory usage on the first use after bootup.
I'm thinking that it's calling for a windows service which I don't have enabled at boot, and the launcher times out waiting for it maybe?
If anyone has knowledge of what the launcher is doing at/about 1700k, perhaps I can rectify this.
As additional info, simply ending task on the launcher and relaunching it fixes the problem, and it will work fine for the remainder of the
boot session, and only does this at first launch after boot, so it's not a big deal. I'm just a damn perfectionist that wants to fix it.