-----
Last edited:
So without the logistics of this. I noticed the stupid orange issue as well with my color scheme. As someone else mentioned, I am thinking there has to be another palate or another part of the same palate that you would need to update. I haven't looked into it and will just wait till something else happens.
I'm surprised though that FD hasn't just capitalized on this and put a color scheme tool in the Frontier Store that allows you to do this. Figure they could make some good quick money having this option available.
Until then, yes it's not an FD issue because that orange matches with the crappy orange that is the default color for everyone. It's up to us, not them, to figure out the HUD palate for the new part of the HUD...
EDProfiler is the standard app of choice for changing this, and that appears on every list of must have tools I can find. While not 'officially' support by FDev as an application it has never been said that it was a 'no no'
What if I told you:
Its orange, because normally its blue?
Thats not the point. FD never made an Interface Agreement with the maker of EDProfiler. Therefore the maker of EDProfiler has no leg to stand on if, for whatever reason, the color modding mechanism would change, seized to exist or stopped working at all.
No one but FD knows why the color config file is there. Someone found it, someone changed it and there the possibility was born. ED might have said, you may use it, but thats it. Now their code has changed and maybe the way to UI reacts unexpected to the color configuration mechanism, tough luck. If their intended functionality works as expected, fine. If the undocumented feature stops working there, well it was fun while it lasted, its not an acquired right of usage or anything...
IT WORKS AS EXPECTED!
Omg! Just read above! I already said that OP has an inverted color scheme. All his screenshots point to UI elements that should be blue by default. But due to his color scheme, they are now orange (same as his shield rings).
Doh! That is bad news. Half of me had already hoped they could apply the same to the pips on the main scanner, enemies = red, friends = green, others may be colored whatever. That would solve many of the problems I have with alternative color sets like the N2O ones or Dr Kaii's Spiritual Teal.
Unsupported or not, toning down the UI colors is the only way I can bear the overbright UI at all, in particular since 3.3.
O7,
[noob]
LOL, funny that nobody realised it while everyone was arguing if modding a file is a mod or not.
There's a brightness control in panel 4.
FD just don't actively prevent it.
It just blows my mind that you good folks are even arguing against me. Forget about whether this is supported or not, either way it's a mess in the current state. Can we not agree upon that at least?![]()
Thats not the point. FD never made an Interface Agreement with the maker of EDProfiler. Therefore the maker of EDProfiler has no leg to stand on if, for whatever reason, the color modding mechanism would change, seized to exist or stopped working at all.
No one but FD knows why the color config file is there. Someone found it, someone changed it and there the possibility was born. ED might have said, you may use it, but thats it. Now their code has changed and maybe the way to UI reacts unexpected to the color configuration mechanism, tough luck. If their intended functionality works as expected, fine. If the undocumented feature stops working there, well it was fun while it lasted, its not an acquired right of usage or anything...
You talk about quality control, there is zero quality control on features that aren't officially back or support, merely tolerated. If it was a officially supported feature you would have a point, as it not, you don't.
That it is not supported is not the issue, and never was. What is the issue, is that some of the game uses it while other, newer parts don't.
I'm sorry, no easy way to say this; But.. You're guessing and pulling that drivel out of your bottom!
So, please, keep that drivel for your friends who'll think you're an expert.
However! If you open that file, lo-and-behold you will find;
<!-- If you are looking for the SSAA setting this has moved in to Settings.xml in the save directory
** typically: C:\Users\{username}\AppData\Roaming\Frontier Developments\Elite Dangerous\Options\Graphics.
** If this file does not exist you can generate it by entering the graphics options screen in game
** and hitting apply. You can then add <SSAA>X</SSAA> when X is the SSAA amount (1 by default) -->
There are further entries (comments) showing other stuff too.
Now please, explain to me, why that is in there? Now me, I'm only 30 years a developer, so I'm just spiff-balling here;
But I think it's to show the reader where and what to do... I could be wrong mind..
That it is not supported is not the issue, and never was.
What is the issue, is that some of the game uses it while other, newer parts don't.
A really bad design choice, as it means they have to support two differing code bases.
So, please, keep that drivel for your friends who'll think you're an expert.
I'm only 30 years a developer
You are right apart from the bolded part. As others already pointed out, it doesn't work unexpected. The text that people are referring to is blue in vanilla. Therefore it's orange when you are using a blue HUD.
Do you see the shields? They aren't blue as well. It's the same thing.
What a load of drivel!
In the history of Elite, FD have never once rolled a 'hotfix' that was nothing more than a config file. lols
It is absolutely to allow players to configure the system in a way that best suits them. That's why the settings are in a file in the first place!!!
Finally, what it demonstrates is that FD have code that does use those settings and other code which doesn't use those settings, which from a development point of view is not a good idea.
'A modified colour scheme is a derivative work'? Which law school did you go to?
If anyone, anyone had a derivative of Elite Dangerous as you claim they'd find their backside in court so fast. Thousands of players have modified that file, and to the best of my knowledge, no-one has yet been brought to court. So please less of the 'I pulled this law out of my bottom' type stuff.
The 'only' thing you got right was the bit about FD not having to support it.
It was funny tho, gave me a great laugh.
Now me, I'm only 30 years a developer, so I'm just spiff-balling here; But I think it's to show the reader where and what to do... I could be wrong mind..
So, please, keep that drivel for your friends who'll think you're an expert.
That it is not supported is not the issue, and never was. What is the issue, is that some of the game uses it while other, newer parts don't. A really bad design choice, as it means they have to support two differing code bases. But hey, I don't work there, and I can't play the game much anyways, because guess what? The new lighting is a total mess in VR!! I now get migraine headaches if I play for anything more than 20 minutes. But that's my problem. I just think it's wrong that you spout that pulled out of a hat rubbish.