I sent them a polite email.
I've turned gamma right down to 1 in order to de-saturate the colours and brightness, I just don't get why they don't see that the colours and brightness are wrong.
ok the star lighting is a change but I noticed that the colours of the outline of the current ship when ED starts is hopelessly over-saturated when comparing to previous ED versions.The colour map now seems to be more dependent on what type the main system star is atm.
So in one system it seems over saturated.
A jump later and it seems under saturated, make another and everything seems to have a pinkish hue.
There won't be a one fix for all cases even if the old methods worked at all.
And on the whole it's better now, just that planets are dark is worth it.
ok the star lighting is a change but I noticed that the colours of the outline of the current ship when ED starts is hopelessly over-saturated when comparing to previous ED versions.
The lighting within stations is over-bright even with gamma turned down to 1, The colours within the stations is over-staturated when compared to previous.
Someone accidentally bumped the "Brightness", "Contrast", and "Saturation" sliders, they're to busy fixing bugs to notice)
Wont steamvr start automatically when EDprofiler starts Elite?can EDProfiler start VR in Steam.
If so where should I point EDProfiler to find startup file, not sure were to look
Wont steamvr start automatically when EDprofiler starts Elite?
That reason is FD completely re-design the backend for lighting with the beyond release.For some reason I'm not able to use Tonemapping![]()
Is it looking for EDlaunch or EliteDangerous64.exe? I cant remember, probably the launcher:When i try to start ED in EDprofiler a screen pops up wanting me to point it to the startup file.
ED was downloaded and configured by Steam.
Is it looking for EDlaunch or EliteDangerous64.exe? I cant remember, probably the launcher:
EDlaunch will be in drive\Program Files (x86)\Steam\steamapps\common\Elite Dangerous
Elitedangerous64 will be in drive\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\elite-dangerous-64
Hello there,
For some reason CMDR Logs refuses to work for me. Profiler is up to date and I tried:
- starting the game before the Profiler
- starting Profiler before starting the game
- turning LOG prefix off and on.
Logs are simply not created when writing into Local Chat.
Any ideas?
Had a similar thing happen with me, I found out Bitdefender was blocking Elite dangerous and EDProfiler from talking to each other. I had to add them to an accepted/safe program list to get around this. You think your antivirus may be blocking it?