747 V3 dome light? How to clear an mistaken entry?

robains

The EVT_OH_DOME_SWITCH ... trying to map it to a T8 but without much success, it'll turn ON but never turn OFF - tried all switch actions.

But more important, how do I "clear" and entry in the Switch Event (other than manually editing the xml files)?  Example, suppose I make a mistake with the Switch Event ON and enter "toggle_Cabin_Lights" but I changed my mind and don't want any entry for the switch ON.  There used to be a _NO_EVENT, but that's not available for the PMDG - any hints?

UPDATE: found it "BLANK"

EDIT: there appears to be two identical EVT_CDU_R_START and EVT_CDU_L_START ... unrelated, but is there a file I can search thru to quickly ID PMDG supported events?  The scroll and search process can get pretty time consuming.

Cheers, Rob.

robains

SOLVED Dome Light problem I was having ... using MOUSERIGHT_WITH_OFF or MOUSERIGHT2X_SLOW_WITH_OFF2X works well.

Cheers, Rob.

admin_pps

Hi Rob,

All the events are listed in the .h file in the SDK directory. Goto <flight sim dir>\PMDG\<aircraft>\SDK.

I'll look at adding them to the website soon.

Best wishes

Steve

robains

Thanks Steve, wish I could setup my own bespokes so I could call multiple PMDG events with one bespoke, the "CLUSTER" events are pretty limited.  Any chance this could happen in the future, disable the "detective" part but allow for creating bespokes with existing PMDG events?

Appreciate what you've provided (so quickly), has been very useful ... again many thanks.

Cheers, Rob.

admin_pps

It may be possible. In the meantime, let me know what Cluster events you need and I will add them. They have always been driven by customer demand in the past.

Best wishes

Steve

robains

Hey Steve,

Too many cluster events I'd like and they are most likely just one offs specific to my setup ... I typically separate out LEFT and RIGHT into single event ... example Left Inboard and Left Outboard Landing Lights would be clustered into Left Landing Lights and same for Right side.  Basic idea is combining common related sequence of switchs/buttons into a LEFT and RIGHT cluster set.

I was thinking more along the idea that we can still click on "Detective" (maybe rename it to something else "Builder" when PMDG aircraft are loaded) but the actual ability to "Detect" is disabled (assuming this is a PMDG requirement) but we can still select events and create bespokes as per other aircraft.

Cheers, Rob.

c912039

Hi Steve,

I dont have any PMDG aircraft yet, but I do write my code in a similar fashion as discussed by Rob.

I create BEvs for each switch or button in an aircraft.  If there are multiple switches or buttons for a similar activity (Left Landing Lights, Centre Landing Lights, Right Landing Lights), I create a BEv for each.
I then create, what I call a MACRO BEv (and I name it with MACRO too), which calls multiple BEv's, and I assign that MACRO BEv to the GF switch or button.

Having the Detective Screen avail, with the Events and LVar Toggle buttons disabled (if that's whats required) would be very useful.
There may be some standard functions, such as programming FSX/P3D default radio functions that may still be needed, even with PMDG aircraft,and not having access to the Detective screen to write BEv's for default actions might also be limiting.

Regards
David

admin_pps

I have added Lua support directly into GIT with the version out today. It works with PMDG and iFly aircraft as well. You can use Bespoke Vars to send data back to GIT for use.

This should help you guys out where Detective is not available. See here for guide: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/43-lua.html

Best wishes
Steve