Elite: Dangerous Display Switcher
- Thread starter Smack332
- Start date
Pathing issues
Got it working by placing the EDDS files in the following location
C:\Users\USERNAME\AppData\Local\Frontier_Developments
I have an ED Launcher directory in Program Files, and two folders in App Data for Frontier too, which I had tried initially.
just trial and error after reading a previous post, hope this helps someone.
Thanks for sharing the tool, looks great!
Got it working by placing the EDDS files in the following location
C:\Users\USERNAME\AppData\Local\Frontier_Developments
I have an ED Launcher directory in Program Files, and two folders in App Data for Frontier too, which I had tried initially.
just trial and error after reading a previous post, hope this helps someone.
Thanks for sharing the tool, looks great!
Last edited:
This works for me too. Thanks!
EDDS looks for the files to edit in various places. The appconfig.xml and graphicsconfiguration.xml files are (on my computer) in EDLaunch/Products/FORC-FDEV-D-1002, while the others are in the Frontier_Developments folder under local user. Apparently ED installs differ, and that may break the app. Good that you got it working, but can you confirm that everything works as intended? When you put EDDS in the Frontier_Developments folders, it will look for appconfig.xml and graphicsconfiguration.xml in Frontier_Developments/Products/FORC* folder. Does this exist?
Apparently ED installs files in different folders for different users. If EDDS does not work for you, this may be the cause. I'm trying to nail this down, so if EDDS does not work for you, please give me the following info:
- Your ED install location
- The full path of the location of AppConfig.xml and GraphicsConfiguration.xml (for me these are in D:\EDLaunch\Products\FORC-FDEV-D-1002).
- The full path of the location of Settings.xml and DisplaySettings.xml (for me these are in C:\Users\USERNAME\AppData\Local\Frontier Developments\Elite Dangerous\Options\Graphics).
I'm not using the tool, but I admire what you are trying to accomplish.
The installs are different for people depending on what level of beta they joined I believe, as it installed in different locations.
For example, if it helps, mine is in:
C:\Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1002
I know some others are in appdata/ localappdata.
Yeah, here it is; looks like its all working fine, although I aint had time to play yet
C:\Users\USER\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1002
Thank you.
It seems that the files are either in C:\Users\USERNAME\AppData\Local\Frontier_Developments\Products\FORC* or in EDLaunch\Products\FORC*.
I'll update EDDS to look for the files in both places when I got the time.
Works fine, keybinds and all!
BUT I cant play out of the rift, its hi-res and crappy at the same time lol - its a totally different game in the rift - I wont be playing on screens, (or trading I guess lol)
Needed a new GFX, and a HOTAs to get the best out of it, but worth every penny.
EDDS is now updated to look for the files in C:\Users\USERNAME\AppData\Local\Frontier_Developments if they're not found in the game folder. Hopefully these are the only possible locations of the files 
.
For those of you that have ED installed in Program Files (x86); Do you have to run EDDS as administrator? I can't test this as I have it installed on a separate HD.
- - - - - Additional Content Posted / Auto Merge - - - - -
I agree, but sometimes I play on a monitor just to test stuff out, new keybindings etc. Easier that way.
I also ended up with a new GTX970 and an X52Pro after getting the DK2 and ED. Like you said, worth every penny.
.For those of you that have ED installed in Program Files (x86); Do you have to run EDDS as administrator? I can't test this as I have it installed on a separate HD.
- - - - - Additional Content Posted / Auto Merge - - - - -
I agree, but sometimes I play on a monitor just to test stuff out, new keybindings etc. Easier that way.
I also ended up with a new GTX970 and an X52Pro after getting the DK2 and ED. Like you said, worth every penny
.Kudos and rep for you, sir! Awesome little time saver.
Thanks a lot for your work, but EDDS does not work for me.
I put it in the good place, run it as administrator, but it does not find both .xml files.
Here is my install location :
Thanks for your help.
I put it in the good place, run it as administrator, but it does not find both .xml files.
Here is my install location :
- full path of Appconfig.xml & GraphicConf.xml : C:\Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1010
- full path of others .xml files : C:\Users\USERNAME\AppData\Local\Frontier Developments\Elite Dangerous\Options\Graphics
Thanks for your help.
EDDS should find them in those locations. Do you get any error messages?
It was put in by request. EDDS was originally made as a tool to switch between the Oculus Rift and a regular monitor, and some wanted the option to change bindings as well. I'll leave it in there, but I'll add a checkbox for the bindings so that unless this is checked, it doesn't change anything.
- - - - - Additional Content Posted / Auto Merge - - - - -
Thanks. Glad you figured it out.
Thanks for this!
Have you really lost your bindings? EDDS does not overwrite any control bindings. All it does is edit the StartPreset.start file in C:\Users\USERNAME\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings. This only contains the name of the current bindings profile. Your actual bindings file should still be in the same folder, and should still load when you change the name in EDDS (or in ED settings) to your profile's name.
I will include a check box in the next update to prevent EDDS from automatically changing the name of the profile, as I can see how this might throw people off.