same issue, 185 ![]()
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes. The issue is present and prominent in the brand new Cessna 185F, which makes it impossible to fly at dusk and night.
Provide extra information to complete the original description of the issue:
• there’s no more to include. It’s hyper bright and cannot be adjusted manually
If relevant, provide additional screenshots/video:
•
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
• When is this going to be fixed?G450/530 is unusable in all planes except A2A Comanche! Fix it please Asobo!
This worked for me. If anyone’s wondering how to do it, go in Developer Mode, then:
Tools > Behaviors
Select 404 Titan in the top right dropdown
Select the gns530 file in the second dropdown (you have to be in the plane)
Click Materials tab
Right click on the line under “Interpolation” > Open in Code editor
Replace the code
save
Thanks for the tip. Replace the code with what?
The code is in the comment that my previous comment replied to.
Ongoing in SU2 1.4.20.0
Flew the cessna-185-skywagon today and it’s still the same.
GNS screens too bright at night / Carenado Cessna 404 Titan - Bug Reporting Hub / Aircraft & Systems - Microsoft Flight Simulator Forums cessna-404-titan
Go vote for the issue! ![]()
Still an issue that’s been occurring since launch and not been addressed as of SU2 or SUB3.
Occurs in ALL GNS 530/430 aircraft at night.
This is incompetence. Something so basic as this bug is, AND it is still not fixed 6 MONTHS after reported? I don’t care how ‘nice’ Jorge is and the guys at Asobo, this is failing to run this project properly. They put energy into putting out new content that is just as broken as he old content they still have not fixed. That makes NO sense at all. And then come on monthly and make more excuses and act like they are overworked. If you are overworked its because you have to do the same things 3 or 4 times over again because you do shoddy work in the first place. Get it right in the first place or don’t release it.
I have to agree, there is no excuse for this issue not being fixed 6 months after being reported.
I wrote the Zen Desk about this and to their credit they did say this was a known problem that MSFS is aware of…and to their knowledge, it is an issue with the individual plane having this bug. What I didn’t hear was when it would be fixed but I doubt they control that or have access to that information.
Can you please check also the Cessna 404?
Sorry I don’t have it.
What aircraft is that?
A2A Aerostar and Carenado Skywagon.
Just tried on the 404, not fixed.



