Elite Dangerous Odyssey | Minor Update 08.09.2022

Factabulous

Factabulous
1662628360654.png
 

foperider

F
How can you disable lens flares? They are an artifact caused by camera lenses and do not exist when using the naked eye. So I certainly do not want to see them looking through the canopy.
 

Cori

Cori
foperider said:
How can you disable lens flares? They are an artifact caused by camera lenses and do not exist when using the naked eye. So I certainly do not want to see them looking through the canopy.
Click to expand...
There was a reply earlier explaining this, something about it being difficult to replicate the effects that are seen by the human eye on screen. So developers show lens flares, which people recognise, instead.
 

Sparrow_NC

Sparrow_NC
foperider said:
How can you disable lens flares? They are an artifact caused by camera lenses and do not exist when using the naked eye. So I certainly do not want to see them looking through the canopy.
Click to expand...
This. But if you override the lens flare, you won't see the anomaly anymore (same shader).
Morbad said:
You can manually disable lens flares separate from the other graphical settings by editing GraphicsConfig.xml in the elite-dangerous-64 directory (or by pasting the relevant section into GraphicsConfigOverride in the game directory in your user profile).

This is what the segment looks like:

Code: 
 <LensFlares>
    <Off>
      <LocalisationName>$QUALITY_OFF;</LocalisationName>
      <Enabled>false</Enabled>
      <QualityIndex>0</QualityIndex>
      <ImportanceThreshold>2</ImportanceThreshold>
    </Off>
    <Low>
      <LocalisationName>$QUALITY_LOW;</LocalisationName>
      <Enabled>true</Enabled>
      <QualityIndex>0</QualityIndex>
      <ImportanceThreshold>2</ImportanceThreshold>    
    </Low>
    <Medium>
      <LocalisationName>$QUALITY_MEDIUM;</LocalisationName>
      <Enabled>true</Enabled>
      <QualityIndex>1</QualityIndex>
      <ImportanceThreshold>1</ImportanceThreshold>
    </Medium>
    <High>
      <LocalisationName>$QUALITY_HIGH;</LocalisationName>
      <Enabled>true</Enabled>
      <QualityIndex>2</QualityIndex>
      <ImportanceThreshold>0</ImportanceThreshold>
    </High>
  </LensFlares>

You can just set all the "Enabled" segments to "false" so no matter what quality setting you use, lensflares are off.

I would also recommend turning down the "GlareWeight" values in the Bloom segment. Half of the defaults keeps some bloom but looks much more natural.
Click to expand...
 

sallymorganmoore

Senior Community Manager : Elite Dangerous

Terekhov

Terekhov
Factabulous said:
I can't believe Sally has locked us out of the update thread! It's almost like she think's we'll fill it with drivel! 😡
Click to expand...
I actually think that the separate timeline thread is an excellent idea, and I seriously hope that ongoing, a similar locked thread accompanies any downtime (or major incident that the CMs need to get involved in managing comms for). The thread should be an easy read of the notice and progression of the work, and a list of known issues maintained until the issue is complete and fallout dealt with.

There should be a separate community discussion thread relating to the downtime locked thread where the feedback and drivel can take place. The important CM updates were getting lost buried in the previous open threads.
 

Factabulous

Factabulous
Terekhov said:
I actually think that the separate timeline thread is an excellent idea, and I seriously hope that ongoing, a similar locked thread accompanies any downtime (or major incident that the CMs need to get involved in managing comms for). The thread should be an easy read of the notice and progression of the work, and a list of known issues maintained until the issue is complete and fallout dealt with.

There should be a separate community discussion thread relating to the downtime locked thread where the feedback and drivel can take place. The important CM updates were getting lost buried in the previous open threads.
Click to expand...
I completely agree - Sally is, as ever, doing a most excellent job.

And we still have this thread for the important posts

duck.gif
 

IDIDOIT

I
Terekhov said:
I actually think that the separate timeline thread is an excellent idea, and I seriously hope that ongoing, a similar locked thread accompanies any downtime (or major incident that the CMs need to get involved in managing comms for). The thread should be an easy read of the notice and progression of the work, and a list of known issues maintained until the issue is complete and fallout dealt with.

There should be a separate community discussion thread relating to the downtime locked thread where the feedback and drivel can take place. The important CM updates were getting lost buried in the previous open threads.
Click to expand...
Agreed, but the quality of communication need a boost. At the start of the outage it was updated to say it was not 40 min, but 2 hours. Then nothing for 2 Hours followed by "downtime continues". It is like the person posting is not in contact with the team performing the work and does not actually know the status
 
You must log in or register to reply here.
Back
Top Bottom