[RESOLVED] Angle-of-Attack Indexer Light to dark

[FoxTwo]

I think the problem that most of us are having is that on cold start jester sets the ECM to standby, which is incredibly dim, so while people were saying it was incredibly hard to see in the daylight, that's because it was, based on the position of the DECM switch. The current brightness may in fact actually be FINE and would explain the inconsistency in the reports you're seeing. At the very least, I know mine was. With the switch in the ON (highest brightness position) it looks fine to me on the latest open beta version (as of today).

 

You probably want to reevaluate whether or not, post DECM switch fix, it needs to be brighter in the first place. I'm not sure it does.

Edited January 25, 2021 by FoxTwo

[IronMike]

I don't think it exceeds max brightness with the DECM switch, just that it lowers or increases it, which it shouldnt of course, that is just a bug. Quite hilarious that it slipped by for so long, our apologies for that. But apart from fixing that (which we still need to do), we have increased the max brightness, so those who thought it too dim, can have a brighter max setting now. It should be well visible during daylight now, too, for those who have found it too dim before.

[sLYFa]

The DECM switch controls a value from 0 to 1 in 0.2 increments. This means that everyone was flying with 20% intensity most of the time (Jester switches DECM to STBY by default). With the switch in RPT (i.e. 100% brightness) IMO the indexer is more than bright enough. So the right amount of brightness was there all along, we just didnt know how to control it.

Btw I think this has been introduced somewhere after release which explains why the LTS TEST before engine start didnt light up the indexer while the indexer would work in flight (Jester switches DECM on only after engine start) 

Edited January 25, 2021 by sLYFa

[IronMike]

3 minutes ago, sLYFa said:

The DECM switch controls a value from 0 to 1 in 0.2 increments. This means that everyone was flying with 20% intensity most of the time (Jester switches DECM to STBY by default). With the switch in RPT (i.e. 100% brightness) IMO the indexer is more than bright enough. So the right amount of brightness was there all along, we just didnt know how to control it.

Btw I think this has been introduced somewhere after release which explains why the LTS TEST before engine start didnt light up the indexer while the indexer would work in flight (Jester switches DECM on only after engine start) 

 

 

Good points, indeed.

[Lt_Jaeger]

I would agree. 

After that find, I land with "music on" and being "blinded by the light". 

 

HB, could you please tune down the indexer, the light is way too bright. 

 

Just kidding!!! 

 

I hope it is not too big of a hassle to fix that problem, after that everything should be OK for, I believe, everyone. To bad you had to "waste" time to increase brightness while it was always there but just hidden......but one has to smile a little at that bug. 

 

In my opinion nobody owns anybody an apology, but everybody needs to get the guy who found that weird "cross wiring " a beer.

[RustBelt]

On 1/25/2021 at 7:03 PM, IronMike said:

 

Good points, indeed.

Very good points one might say. 

So, I suppose again, which DECM switch setting did heatblur think they had it set to that we must have been wrong about all this time?

[IronMike]

12 hours ago, RustBelt said:

Very good points one might say. 

So, I suppose again, which DECM switch setting did heatblur think they had it set to that we must have been wrong about all this time?

 

The one I explained to you already 2 times now. Please stop wasting our time with this. Thread closed.