Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

Need help with Airfoillabs C172 instrument backlighting rotary

After several days of trying, I’ve finally given up and need some assistance. There are 2 rotaries on the C172 panel controlling the panel lighting. The upper one controls the instrument backlighting intensity and the lower one controls the glareshield and pedestal lighting intensity. These rotaries are moved by mouse clicking on the right (up) and left (down) side of each rotary.

I had no problem creating 2 Bespoke Events for the lower knob controlling the glareshield and pedestal lighting. Detective displayed 2 possible sets of Commands and a likely single DataRef (172/lights/int/int_glare_pedes_lt). In a matter of minutes I had created 2 Bespoke Events using one of the up and down sets of Commands for the first line of each and the above DataRef with the incremental (Set+) and decremental (Set-) operators, each set to a value of “1”. These 2 events could then be bound to a rotary on one of my RP-48s.

But the other lighting control is a different story. I’ve tried using both sets of Commands with various likely DataRefs and nothing works. I believe that one of the two sets of Commands is applicable and that the problem concerns my selection and use of the DataRefs.

Detective suggests that these 5 DataRefs relate to this rotary.

DataRef : sim/cockpit/electrical/instrument_brightness DataRef Data: 0.716681003570557

DataRef : sim/cockpit2/electrical/instrument_brightness_ratio[0] DataRef Data: 1.66723716259003

DataRef : sim/cockpit2/electrical/instrument_brightness_ratio_auto[0] DataRef Data: 1.66723716259003

DataRef : sim/cockpit2/electrical/instrument_brightness_ratio_manual[0] DataRef Data: 0.716681003570557

DataRef : sim/cockpit2/switches/instrument_brightness_ratio[0]

They appear grouped together in the above order in several places in Detective. None of these DataRefs individually seems to work with the Commands I’ve been using. The simple procedure I used with the other lighting rotary just doesn’t seem to work here. And I have no idea how to incorporate all 5 DataRefs, if that’s what’s necessary, into a single Bespoke Event. Perhaps I need to use the Go To operator to tie together 5 Command lines, each with one of the DataRefs, to get the rotary to move. But I haven’t the faintest idea whether this would work or how to set this up.

Here are the Commands I’ve been using:

This set worked for the glareshied and pedestal lighting rotary and may also be applicable to the instrument lighting that I’m having trouble with:
66682 sim/instruments/panel_bright_down
66683 sim/instruments/panel_bright_up

This is the other set that may be relevant to the instrument lighting I'm having a problem with:
66684 sim/instruments/instrument_bright_down
66685 sim/instruments/instrument_bright_up

Any assistance will be appreciated.

Thanks,
Robert







Comments

  • Hi Robert,

    Have you tried simply incrementing one or all of the Datarefs by some fractional amount, say 0.1 and -0.1.

    Also make sure you are using the latest version of GIT released yesterday as it fixes a major bug with Datarefs.

    Best wishes
    Steve
  • Hi Steve,

    I've tried 0.1 with each of the 5 DataRefs and no luck. How would I script all 5 DataRefs to run seriatim as they seem to do in Detective? I've tried several ways, get no response, but really don't know how to do it.

    Thanks,
    Robert
  • You can add multiple Tasks in a Bespoke Event that updated each of the DataRefs one after the other.

    Best wishes
    Steve
  • All is working fine now. Turns out there were 2 additional tasks that were needed in addition to the 5 listed above. And using 0.1 was also key. Thanks, Robert
Sign In or Register to comment.