Cessna 172:
I have my Panel Lights mapped to the L key.
The only thing that lights up is the digital clock on the left of the dashboard. Panel lights do not work.
Youâre going to have to tell us a whole lot more than that if you want help.
First, have you emptied your community folder and tested it again? Do you have any mods for the Cessna 172? Which Cessna 172, - the classic or G1000? Have you added your mods back in after removing everything one by one, killing and starting the sim each time, starting with the C-172 mods, till you found which one broke your lights? Have you modified any files in your main OneStore directory (a big no-no).
I donât use Mods.
Lights donât work in any plane.
Iâve restarted the sim and my PC.
They did work on one flight using the key that I mapped. Now the panel lights donât work in any aircraft.
What about if you use the switch on the panel? Do they turn on then?
Other than that, I donât know what to do, but maybe somebody else does, that information is helpful.
Hi.
If you look on the cockpit dash just to the left of the Throttle lever you will see two rotary dials. They
are both âgangedâ [that is; each one has two rotaries. An inner ring and an outer ring].
You can adjust these individually, left and right, with the mouse wheel.
The top rotary:
Outer = panel lighting brightness.
Inner = radio lighting brightness.
The bottom rotary:
Outer = floodlight brightness.
Inner = glare shield brightness.
Adjust to taste and you are good to go.
3 Likes
He said his keybinding isnât working for any aircraftâŠ
He still didnât answer if using a panel switch turns on the lights to let us know if itâs the keybinding or a systems issue.
Yup ⊠I have observed a number of light issues as well. See:
⊠and other reports related issues too:
What I observed in my tests (inclding in 1.10.11.0) is that (for the panel lights) I need to âmanuallyâ turn up the brightness dials inside the cockpit via the ârealâ controls ⊠once the brightness is up then I can âtoggle itâ.
What I did not get working in any aircraft that I tried (typically I test my issues with King Air, Longitude, 787, A320) is to bind the â(De)Increase Brightnessâ command to a button. It has no effect.
So if someone has seen an aircraft where those commands do work ⊠then I would like to hear that.
I hope everyone is doing these tests with empty Community folders. The UWA light mod definitely messes with the lights and can break their operation. Iâve uninstalled them now and it fixed the issues I was having with the C152 mod. It was breaking the glareshield potentiometer (my glareshield lights were full power all the time), and the low amperage light was on all the time, too.
I never installed any aircraft modifications or liveries (up to now) ⊠but I did buy a few airports.
And so far âthe Nene-nui in meâ is only tempted by one Community âaircraftâ âŠ
That is such a lovely idea 
1 Like
Thank you captainLIF. This appears to have fixed my issue.
I wonder why they would have the brightness turned all the way downâŠ
Thanks again for your time. 
Coogan Bear
You are very welcome.
I have yet to try and assign these light functions to my yoke.
But if the mapping [within MSFS] exists, I will certainly do so.
Regards.
If you find any aircraft where the â(De)Increase Light Potentiometerâ bindings show any effect I would like to hear about that. I have so far not found any ⊠and I suspect the commands do not work (like some of the âToggle xyz lightâ problems I references above).
I also noticed some inconsistencies. In one or two cases I saw that inside the 3D cockpit the switch is named âRecognition Lightâ ⊠but you need a different control binding (NAV or Landing or so) to toggle it. I think the Longitude was one such example (but I would have to check).
I wonder too.
I suspect that it is an âaccidentâ, as it could simply be that those setting are simply âreset to zeroâ when an aircraft is loaded by the game ⊠and that is where they stay until you âmanuallyâ dial them up.
Given that things like custom cameras and even flight hour counters are persistent for one aircraft they clearly have a facility to store âper aircraft stateâ between flights. So I would like to see some more âcockpit stateâ preserved between flights. The brightness dials seem like candidates ⊠or are real pilots always dialing them down when they shut down the aircraft?
Now there seem to be cases in some aircraft where the brightness dial is the only 3D cockpit control to turn them âonâ (so there is no additional switch) ⊠but in those cases I would expect the control binding to not simply âtoggleâ an internal bit-state ⊠but to actually âdial upâ the brightness to max if it is presently at zero. I guess such thinks would need to be labeled as âwishlistâ items.
1 Like
Hmm. I suspect that you may be right regarding some of these lightâs issues.
I will be very disappointed if it is not possible to map the light potâs to my yoke!
And I accept your point about this discontinuity between flights. Sadly, as things stand we have no option to save a true âsnapshotâ of the state of the aircraft at flights end. This behaviour is indicative of a game, not a simulator!
And I personally see this as an bad omission. If for no other reason that it renders as pointless any
attempt at a proper aircraft shut down proceedure.
Perhaps I shall raise this as a wish list item.
1 Like
I just posted my command bindings (which have a heavy âlightâ focus right now) for the Virpil throttle here âŠ
It contains some hints at which commands seem âbuggyâ or which I consider as âmissingâ (but those aspects should actually be in some of the forum postings too).
Nicely done. I am sure other CM2 users will find that very useful.
I have done a very similar thing with my yoke. Although, as well as using a âshiftâ function to âdouble upâ commands, a little judicious programming with the software allows you to assign additional commands to any given button using a short [one shot] press and a long [hold] press technique.
I havenât finished my current version for MSFS 2020, but I include an old P3d version to
demonstrate the point:
Note:
One or two of the commands trigger macroâs
A few of the commands can only be achieved using FSUIPC.
I followed other advice on here and just switched accident crash/ mode to disabled and that worked for me after racking my brains out for the past two days.
Other advice is to switch off AI and ground aircraft density . I did that first and it did not work only when I disabled airplane crash and collision did it work for me.
Maybe it worked for others because their computer is set up differently I am not sure.
When doing this you have to go into Developer mode and switch on.
A menu with small writing appears top left of your monitor (Make sure you are viewing in full screen mode to see the menu. Choose options with Dev Mode on and choose option to disable collisions.
Hope that helps because I know it is very frustrating with those panels turning off during a flight.
adjusting is a realy big wordâŠ
you cant set it to 0, 99, 99,2, 99,3, 99,4âŠ100%
BUt between 1 to 99% there is no setting possible.