Missing Lights in Cockpit/External View [cause: Bravo switches]
-
I've noticed that many of the external lights are not showing up from the regular cockpit view nor the external view ('End' key). They show up in the drone view only. These lights are:
- Strobe lights
- Nav lights
- Beacon light
The taxi, landing, recognition, and wing ice lights show up correctly in all views.
Is this a conscious design decision to avoid distracting light bleed in the cockpit in some circumstances, or is it a minor bug? It happens in all three Dukes.
UPDATE: For future readers, hardware mappings to the default commands for beacon/strobe etc. are the reason for this issue.
-
Everything seems to be operating normally in all views on my end. You're more than welcome to share a video if you can catch this happening again.
-
Thanks Nick. I thought it odd that others hadn't reported it. I launched the sim with almost all of my mods removed and it behaved normally. I added back some stock aircraft improvement mods, suspecting a clash. Also normal.
I added everything else back and now the problem returned. Well, almost. The nav lights are now working in all views, but not the rest I listed.
So something must be conflicting; I just don't know what or why! I don't use a whole lot of add-ons. Some improvement mods for default GA aircraft (no apparent effect as mentioned), some scenery mods (We Love VFR + powerlines, solar farms, ship traffic), a few avionics additions (PMS50, KLN-90B), a few liveries, and less than a handful of payware aircraft - I'm super selective there. I've now reloaded the sim about 6 times with different sets of add-ons to try to narrow it down but no luck as yet.
I recorded some video but other than it showing the issue, I don't think it'll help troubleshoot.
I see in the config files that the Duke appears to have its own light effect definitions, so that makes it even more puzzling. Will keep trying... :)
-
Thanks Randolf. I'm just posting again as I have finally found the culprit. It was not what I expected: It was my Honeycomb Bravo switch mappings!
When I tested earlier, I didn't have my controls plugged in. This evening, I went for a flight in another aircraft and then thought I'd troubleshoot the Duke lighting again. Having slowly stripped back to no mods at all, it was still happening... until I flicked all the switches on my Bravo, where I had the beacon & strobe mapped for the Comanche (but not the nav lights). Being in a forced 'off' state, they affect the lights on the Duke (and presumably other aircraft; I just don't tend to fly others often).
It works like this:
- Bravo switches are off = Duke lights show in drone camera only
- Bravo switches are on = Duke lights show in all views
Of course, the 3-position switches in the Duke cockpit move freely no matter the state of the Bravo switches, as they are not linked to the default bindings for beacon and strobes. The landing and taxi lights are, so I could only test those by flicking my Bravo's switches, meaning the issue didn't show.
I'm glad I have found the reason, though the way it manifested itself in certain camera views is really quite strange. Good to know should someone else have the same issue in future! :)
-
@Mustang For what it is worth I decided to to change the "Yoke" set up for the DC-6's.
4 mags and one switch, I removed the L,R,Both and Start...Then...I got really feisty and cleared out "All" electrical bindings...on both Wheel and Throttle. There are times I can't get my fingers behind the engine controls...like right after Take Off. So it may be a little "Old School", I just use the Mouse". And also the Lear 35 (PWS) just got an update and I noticed the landing lights would not go out at all, and that is with the above "No switches" set-up, SU-15 issue adding fuel to problem?
