EDIT: I've now found a work-around for this problem, see here.
I'm installing ED on a new PC, and found that the ED Launcher stupidly still installs all the game's main files (3.5GB!) to "C:\Users\username\AppData\Local\Frontier Developments\Products". I thought they'd fixed this ridiculous decision by Gamma, but apparently not. (Don't FD have any idea what AppData is supposed to be used for? It'll mess with all sorts of backup utilities.)
Anyway, during Beta there was a trick where by you create a "Products" folder in the EDLaunch folder, before you install the game (using the Launcher). However, if I try that now, the new fancy ED Launcher fails to start with the following error:
Error during application startup
Exception initialising application
Value cannot be null.
Parameter name: path
And when I OK that, I then get this error message:
Unhandled exception: Cannot create instance of 'CobraBayWindow' undefined in assembly 'EDLaunch, Version=0.4.1765.0, Culture=neutral, PublicKeyToken=null'.
Exception has been thrown by the target of an invocation. Error in markup file 'EDLaunch;components/CobraBayWindow.xaml'.
So it appears that ED's fancy new launcher no-longer supports this trick, or more likely a new bug is preventing it from working. (ED works on my other PC just fine with Products in the EDLaunch folder, but that was simply upgraded from Beta, and so appears to circumvent this bug.)
I've created a ticket, and support has TRIED to help, but they are as clearly puzzled as me. With FD's developers mostly going on holiday for a week (?), I'm not holding my breath for the ED Launcher to be fixed any time soon. So I wanted to know if anyone has discovered a new trick to get around this problem?
EDIT: I guess I should have created this thread in the "Elite: Dangerous Support" forum that is 'hidden' at the bottom of the forum list. I'd be happy if a moderator kindly moved it there.
I'm installing ED on a new PC, and found that the ED Launcher stupidly still installs all the game's main files (3.5GB!) to "C:\Users\username\AppData\Local\Frontier Developments\Products". I thought they'd fixed this ridiculous decision by Gamma, but apparently not. (Don't FD have any idea what AppData is supposed to be used for? It'll mess with all sorts of backup utilities.)
Anyway, during Beta there was a trick where by you create a "Products" folder in the EDLaunch folder, before you install the game (using the Launcher). However, if I try that now, the new fancy ED Launcher fails to start with the following error:
Error during application startup
Exception initialising application
Value cannot be null.
Parameter name: path
And when I OK that, I then get this error message:
Unhandled exception: Cannot create instance of 'CobraBayWindow' undefined in assembly 'EDLaunch, Version=0.4.1765.0, Culture=neutral, PublicKeyToken=null'.
Exception has been thrown by the target of an invocation. Error in markup file 'EDLaunch;components/CobraBayWindow.xaml'.
So it appears that ED's fancy new launcher no-longer supports this trick, or more likely a new bug is preventing it from working. (ED works on my other PC just fine with Products in the EDLaunch folder, but that was simply upgraded from Beta, and so appears to circumvent this bug.)
I've created a ticket, and support has TRIED to help, but they are as clearly puzzled as me. With FD's developers mostly going on holiday for a week (?), I'm not holding my breath for the ED Launcher to be fixed any time soon. So I wanted to know if anyone has discovered a new trick to get around this problem?
EDIT: I guess I should have created this thread in the "Elite: Dangerous Support" forum that is 'hidden' at the bottom of the forum list. I'd be happy if a moderator kindly moved it there.
Last edited: