Elite: Dangerous Display Switcher

Bilbo_Fraggins · Jan 7, 2015

Thank you for sharing your work with the community. It is greatly appreciated. Even though I do not yet have a Rift, the UI color changing feature makes this program invaluable.

Smack332 · Jan 8, 2015

Smack332 said:
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.

Check update.

The_Baron · Jan 8, 2015

I renamed my Bindings profile and all is well again. Thanks so much for this invaluable program. Now to see which of the pre-set colour schemes makes the text most legible!

SilverlightPony · Jan 9, 2015

I'm getting the error about it not finding the XML files. They're in the default subfolder, but in my case it's D:\Games\Elite Dangerous\Products\FORC-FDEV-D-1003, rather than FORC-FDEV-D-1002. Ideally, the tool would look for the files with a wildcard on the FORC- subdirectory, since the number's not always the same.

Smack332 · Jan 9, 2015

SilverlightPony said:
I'm getting the error about it not finding the XML files. They're in the default subfolder, but in my case it's D:\Games\Elite Dangerous\Products\FORC-FDEV-D-1003, rather than FORC-FDEV-D-1002. Ideally, the tool would look for the files with a wildcard on the FORC- subdirectory, since the number's not always the same.

The program looks for the files in any subdirectory starting with FORC, so that should not be an issue. Did you put the files in the EDLaunch folder?

- - - - - Additional Content Posted / Auto Merge - - - - -

The_Baron said:
I renamed my Bindings profile and all is well again. Thanks so much for this invaluable program. Now to see which of the pre-set colour schemes makes the text most legible!

Glad you got it sorted out. I'm using the 'Medium green with blue accents' which is quite nice. But I have not tried them all. Let me know which one you like best. Or make your own

.

deftly · Jan 9, 2015

Very nice. Any chance of adding SuperSampling resolutions to the Rift config options? It makes the text so much more readable.

http://www.tested.com/tech/pcs/454383-aliasing-be-gone-how-downsample-pc-games/

Smack332 · Jan 9, 2015

You can input the resolution of your choice. So if you're using 2560 x 1440, just put that in the resolution textbox and hit apply. I haven't tested it, but it should work.

Magictrip · Jan 9, 2015

Just to let you know, I don't know why but I had 2 FORC-FDEV and that made the application do not find the correct files.

It appeared to me that your search was returning both folders and trying to concatenate them.

SilverlightPony · Jan 9, 2015

Smack332 said:
The program looks for the files in any subdirectory starting with FORC, so that should not be an issue. Did you put the files in the EDLaunch folder?

There is no EDLaunch folder in my installation. I installed the game to D:\Games\Elite Dangerous\ , and that's where the launcher is located. I prefer to leave the game files where the installer put them (which in this case is D:\Games\Elite Dangerous\Products\FORC-FDEV-D-1003\AppConfig.xml), but if the game will read them properly from D:\Games\Elite Dangerous\ , I'll try moving them there.

Tovrin · Jan 9, 2015

No matter where I put these files, I keep getting

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Xml.XmlException: Invalid XML document. The document does not have a root element.
at System.Xml.XmlDocument.Save(String filename)
at ED_Display_Switcher.Form1.settingsToFiles(String settings, String displaySettings, String appConfig, String gfxSettings, String pre)
at ED_Display_Switcher.Form1.btnApply_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
EDDS
Assembly Version: 0.3.2.0
Win32 Version: 0.3.2.0
CodeBase: file:///C:/Users/<USERNAME>/AppData/Local/Frontier_Developments/Products/FORC-FDEV-D-1001/EDDS.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Smack332 · Jan 9, 2015

SilverlightPony said:
There is no EDLaunch folder in my installation. I installed the game to D:\Games\Elite Dangerous\ , and that's where the launcher is located. I prefer to leave the game files where the installer put them (which in this case is D:\Games\Elite Dangerous\Products\FORC-FDEV-D-1003\AppConfig.xml), but if the game will read them properly from D:\Games\Elite Dangerous\ , I'll try moving them there.

You have to have the EDDS files in the main game folder, in your case Elite Dangerous.

Edit:

Just to clarify: Leave the game xml files where they are, just put the EDDS.exe and EDDS.xml in the main game folder.
If you still get an error, I'm not sure what's causing it. Do you also have a GraphicsConfiguration.xml file in D:\Games\Elite Dangerous\Products\FORC-FDEV-D-1003\?

Smack332 · Jan 9, 2015

Magictrip said:
Just to let you know, I don't know why but I had 2 FORC-FDEV and that made the application do not find the correct files.

It appeared to me that your search was returning both folders and trying to concatenate them.

Yes, I did not anticipate anyone having two of these folders. In that case EDDS will only search one of them (the one with the highest number).

Weird how many different setups there are. The FORC-FDEV folders have separate numbers, some are in the products folder while others are in the user appdata folder. You have two of them...

Are the contents of your two FORC-FDEV folders the same?

Smack332 · Jan 9, 2015

Tovrin said:
No matter where I put these files, I keep getting

Do you get an error message on startup, or only when you try to save?

Right now EDDS seems to be in your user/appdata folder. Make sure to put both EDDS.exe and EDDS.xml in your game folder (called EDLaunch unless you renamed it on installation). You also seem to be using an older version of EDDS, v0.32. Download v0.33 (although that should not change anything related to your error message).

Make sure you run EDDS as an administrator. If you still get an error, let me know.

SilverlightPony · Jan 9, 2015

Smack332 said:
You have to have the EDDS files in the main game folder, in your case Elite Dangerous.

Edit:

Just to clarify: Leave the game xml files where they are, just put the EDDS.exe and EDDS.xml in the main game folder.
If you still get an error, I'm not sure what's causing it. Do you also have a GraphicsConfiguration.xml file in D:\Games\Elite Dangerous\Products\FORC-FDEV-D-1003\?

Oh, that's what it was. That's...unintuitive.

Milamber · Jan 13, 2015

Is there a general preferred option for color?

Viajero · Jan 13, 2015

just installed v33 and when i click on "enable" for the second window the path the app looks in for my appconfig.xml seems very weird. I ll see if i can post it.

EDDS is installed in the same folder where i hve my edlaunch.exe (which is in my install foder G://EDLaunch/, and my appconfig.xml file is in G://EDLaunch/Products/FORC-FDEV-D-1001/

Ive also tried 0.32, the error is the same:

Smack332 · Jan 13, 2015

Viajero said:
just installed v33 and when i click on "enable" for the second window the path the app looks in for my appconfig.xml seems very weird.
/snip

That happens because you have multiple FORC-FDEV folders. Fixed in v0.34 (see OP).

Tovrin · Jan 16, 2015

Smack332 said:
Do you get an error message on startup, or only when you try to save?

When I save

Right now EDDS seems to be in your user/appdata folder. Make sure to put both EDDS.exe and EDDS.xml in your game folder (called EDLaunch unless you renamed it on installation). You also seem to be using an older version of EDDS, v0.32. Download v0.33 (although that should not change anything related to your error message).

That seems to have been the problem ... though I did originally crash when I put it in the EDLaunch folder. The new version seems to have done the trick.

Viajero · Jan 16, 2015

Smack332 said:
That happens because you have multiple FORC-FDEV folders. Fixed in v0.34 (see OP).

Oooh, goody. Thanks, that did it.

Daggoo · Jan 16, 2015

Amazing app. As someone who regularly switches between mouse/keyboard, HOTAS, and Oculus, this is exactly what I've been looking for. Thank you for making this!