Using FSUIPC7 with Mobiflight WASM module

[John Dowson]

28 minutes ago, Stinger2k3 said:

I doubt that it would recognise evt files that have had their names changed unless the WASM is changed too. I would stick to the original file name.

Event file names are independent of the WASM - its only the names of the events in the file that depend on the WASM.
His problem was that MSFs wasn't running, and event files are only loaded once FSUIPC is connected yo MSFS.

[Stinger2k3]

12 minutes ago, John Dowson said:

Event file names are independent of the WASM - its only the names of the events in the file that depend on the WASM.
His problem was that MSFs wasn't running, and event files are only loaded once FSUIPC is connected yo MSFS.

Yep , I doubted myself as soon as I wrote it !

[Maltloaf]

John,

 

It all works!! Flipping wonderful, you sir are a genius.  Now to give Mobiflight some love.

[DannyT]

Hi, 

Where can i get the event File?

The other event files here are unavailable.

Regards

[John Dowson]

You can get the list of MobiFlight events from MobiFlight and create your own file. You can use the ones I posted earlier, but they are quite old by now and so probably not complete. Here they are again, but you are better off either creating your own or maybe someone else will post some files with the later events included: MB1.evtMB2.evt

[sep23]

On 1/12/2021 at 8:43 AM, John Dowson said:

As I mentioned in a previous post, I think it would be better to create an event file for each device (e.g. G1000.evt, G3000.evt, etc), and then just add the ones for the systems you use. I guess I could also look into making the [EventFiles] ini section profile specific if different event files will be used for different profiles.

Hi John, Just a follow up... So am I understanding correctly that I should not have both MobiFlight event files in the FSUIPC folder? Is there a reason you are suggesting to swap these files in an out depending on the equipment in each plane. I have both in the FSUIPC folder right now and events from both files all seem to be available to me which assigning keys or buttons. Am I just lucky that everything seems to be working?

Also, what would be your suggested workflow as far as swapping these files as I go from one plane to another? Thanks for addressing all me dumb questions!

Best Regards,

Scott

 

[John Dowson]

13 hours ago, sep23 said:

Hi John, Just a follow up... So am I understanding correctly that I should not have both MobiFlight event files in the FSUIPC folder? Is there a reason you are suggesting to swap these files in an out depending on the equipment in each plane. I have both in the FSUIPC folder right now and events from both files all seem to be available to me which assigning keys or buttons. Am I just lucky that everything seems to be working?

You can use as many event files as you need. I was just thinking that you could split the events into different files, so AS1000 events in one file, AS3000 in another,  etc.  Then, if using something like SimStarter, you could just load the files for the events needed for the loaded aircraft.

However, there is no issue having all events available for every aircraft.

[sep23]

Oh, ok! Thanks John!

[mauriciokami]

 

On 2/2/2021 at 7:09 AM, John Dowson said:

I think, but am not sure, that the MobiFlight module gets the events through via SimConnect.
For events that are handled in the gauge key event handler, it seems that you need to match the string name when you register the simconnect event to that used in the WASM module, e.g.
    hr = SimConnect_MapClientEventToSimEvent(hSimConnect, EVENT_MFD_MODE_1, "#0x11000");

So the event string (in the event file) you need to use would be "#0x11000". However, you cannot use this with FSUIPC as the custom event strings must contain a period (.), e.g. MobiFlight.AS1000_PFD_VOL_1_INC, so not sure at the moment if this is possible. Maybe its possible to use something like "MyWASMNAME.#0x11000", where MyWASMNAME is taken from the WASM manifest (maybe the "creator" attribute?)...

Anyway, I'm looking into this at the moment. I will be providing a WASM module to handle lvars (and also hvars, but later) thats integrated into FSUIPC and allows you to specify which lvars you want to use (via files) and then be able to use these (get/set) in FSUIPC as before, but also with an additional control that allows you to set any lvar.

John

hello John Dowson, did you check out the functionality of WASM by calling straight through events in C #?

[John Dowson]

7 hours ago, mauriciokami said:

hello John Dowson, did you check out the functionality of WASM by calling straight through events in C #?

I don't use C#

[guit33]

Hello

I am looking for the event to move the knob of the GTC580 for the G3000 (for the TBM930): to zoom the map .

I try all the event possible (with knob inside) and they don't work

Is all the event are working ? 

 

187=MobiFlight.AS3000_TSC_Vertical_TopKnob_Large_DEC

[Stinger2k3]

25 minutes ago, guit33 said:

Hello

I am looking for the event to move the knob of the GTC580 for the G3000 (for the TBM930): to zoom the map .

I try all the event possible (with knob inside) and they don't work

Is all the event are working ? 

 

187=MobiFlight.AS3000_TSC_Vertical_TopKnob_Large_DEC

Hi, i don't use the TBM but for the correct event for  Longitude and G1000 is....

AS1000_MFD_RANGE_INC 

and

AS1000_MFD_RANGE_DEC

Try this one.

[guit33]

Hello

Unfortunately This one does not exist for the G3000

I try all these and they don't work (I use Mobiflight wasm and the event file for fsuipc)

171=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Large_INC
172=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Large_DEC
173=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Small_INC
174=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Small_DEC
175=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Push_Long
176=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Push
177=MobiFlight.AS3000_TSC_Horizontal_BottomKnob_Small_INC
178=MobiFlight.AS3000_TSC_Horizontal_BottomKnob_Small_DEC
179=MobiFlight.AS3000_TSC_Horizontal_BottomKnob_Push
180=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Small_INC
181=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Small_DEC
182=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Push_Long
183=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Push
184=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Large_INC
185=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Large_DEC
186=MobiFlight.AS3000_TSC_Vertical_TopKnob_Large_INC
187=MobiFlight.AS3000_TSC_Vertical_TopKnob_Large_DEC
188=MobiFlight.AS3000_TSC_Vertical_TopKnob_Small_INC
189=MobiFlight.AS3000_TSC_Vertical_TopKnob_Small_DEC

[John Dowson]

This is the complete list of event for the G3000 from the latest cip file (https://bitbucket.org/mobiflight/mobiflightfc/src/master/Presets/msfs2020_eventids.cip😞

Quote

G3000 PFD:GROUP

AS3000_PFD_SOFTKEYS_1

AS3000_PFD_SOFTKEYS_2

AS3000_PFD_SOFTKEYS_3

AS3000_PFD_SOFTKEYS_4

AS3000_PFD_SOFTKEYS_5

AS3000_PFD_SOFTKEYS_6

AS3000_PFD_SOFTKEYS_7

AS3000_PFD_SOFTKEYS_8

AS3000_PFD_SOFTKEYS_9

AS3000_PFD_SOFTKEYS_10

AS3000_PFD_SOFTKEYS_11

AS3000_PFD_SOFTKEYS_12

G3000 PFD Top Panel:GROUP

AS3000_PFD_BottomKnob_Small_INC

AS3000_PFD_BottomKnob_Small_DEC

AS3000_PFD_BottomKnob_Push_Long

AS3000_PFD_BottomKnob_Push

AS3000_PFD_BottomKnob_Large_INC

AS3000_PFD_BottomKnob_Large_DEC

AS3000_PFD_TopKnob_Large_INC

AS3000_PFD_TopKnob_Large_DEC

AS3000_PFD_TopKnob_Small_INC

AS3000_PFD_TopKnob_Small_DEC

G3000 MFD:GROUP

AS3000_MFD_SOFTKEYS_1

AS3000_MFD_SOFTKEYS_2

AS3000_MFD_SOFTKEYS_3

AS3000_MFD_SOFTKEYS_4

AS3000_MFD_SOFTKEYS_5

AS3000_MFD_SOFTKEYS_6

AS3000_MFD_SOFTKEYS_7

AS3000_MFD_SOFTKEYS_8

AS3000_MFD_SOFTKEYS_9

AS3000_MFD_SOFTKEYS_10

AS3000_MFD_SOFTKEYS_11

AS3000_MFD_SOFTKEYS_12

GTX 580 TBM:GROUP

AS3000_TSC_Horizontal_SoftKey_1

AS3000_TSC_Horizontal_SoftKey_2

AS3000_TSC_Horizontal_SoftKey_3

AS3000_TSC_Horizontal_TopKnob_Large_INC

AS3000_TSC_Horizontal_TopKnob_Large_DEC

AS3000_TSC_Horizontal_TopKnob_Small_INC

AS3000_TSC_Horizontal_TopKnob_Small_DEC

AS3000_TSC_Horizontal_TopKnob_Push_Long

AS3000_TSC_Horizontal_TopKnob_Push

AS3000_TSC_Horizontal_BottomKnob_Small_INC

AS3000_TSC_Horizontal_BottomKnob_Small_DEC

AS3000_TSC_Horizontal_BottomKnob_Push

 

If the events aren't working, you could ask over on the Mobiflight discord channel (https://discord.com/channels/608690978081210392/804777121255915562).

[guit33]

Thank you John, I will check

[Stinger2k3]

4 hours ago, guit33 said:

Hello

Unfortunately This one does not exist for the G3000

I try all these and they don't work (I use Mobiflight wasm and the event file for fsuipc)

171=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Large_INC
172=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Large_DEC
173=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Small_INC
174=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Small_DEC
175=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Push_Long
176=MobiFlight.AS3000_TSC_Horizontal_TopKnob_Push
177=MobiFlight.AS3000_TSC_Horizontal_BottomKnob_Small_INC
178=MobiFlight.AS3000_TSC_Horizontal_BottomKnob_Small_DEC
179=MobiFlight.AS3000_TSC_Horizontal_BottomKnob_Push
180=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Small_INC
181=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Small_DEC
182=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Push_Long
183=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Push
184=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Large_INC
185=MobiFlight.AS3000_TSC_Vertical_BottomKnob_Large_DEC
186=MobiFlight.AS3000_TSC_Vertical_TopKnob_Large_INC
187=MobiFlight.AS3000_TSC_Vertical_TopKnob_Large_DEC
188=MobiFlight.AS3000_TSC_Vertical_TopKnob_Small_INC
189=MobiFlight.AS3000_TSC_Vertical_TopKnob_Small_DEC

For the map zoom you dont need to use one specifically for the g3000 as it uses the g1000 event. This is why it works with the longitude.

[guit33]

Sorry

But it does not work (nothing happen) with the g1000 event.

I have a events.txt in C:\Users\Guillaume\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\mobiflight-event-module\modules

I have a GNS3000.evt in c\fsuipc (last version)

I have programme fsuipc

Does it work for you in the TBM930 ?

GNS3000.evt events.txt

[Stinger2k3]

13 hours ago, guit33 said:

Sorry

But it does not work (nothing happen) with the g1000 event.

I have a events.txt in C:\Users\Guillaume\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\mobiflight-event-module\modules

I have a GNS3000.evt in c\fsuipc (last version)

I have programme fsuipc

Does it work for you in the TBM930 ?

GNS3000.evt 2.05 kB · 0 downloads events.txt 10.46 kB · 0 downloads

 

[Stinger2k3]

Try it in the Longitude to make sure it is working with that aircraft for you.

I cannot test the TBM at present because my cockpit is currently dismantled while I am doing some scenery design work.

[Stinger2k3]

18 hours ago, guit33 said:

Sorry

But it does not work (nothing happen) with the g1000 event.

I have a events.txt in C:\Users\Guillaume\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\mobiflight-event-module\modules

I have a GNS3000.evt in c\fsuipc (last version)

I have programme fsuipc

Does it work for you in the TBM930 ?

GNS3000.evt 2.05 kB · 0 downloads events.txt 10.46 kB · 0 downloads

Inside your community folder you should have the following....

A folder called "mobiflight-event-module

Inside this folder you should see a folder called "modules", plus a file called layout.json and a file called manifest.json.

Inside the modules" folder you should have a file called "StandaloneModule.wasm"

Hope this helps

Keith

[Maltloaf]

Another question on the same vain as I asked above somewhere.  I have just bought the MSFS PMDG DC-6 and it is amazing.  Not a DC-3 unfortunately but awesome just the same.  I have the same issue with the DC-6 Gyro-pilot as I did with MSFS G530 etc.  I don’t know the event IDs that will talk to the gyro-pilot.  I found this here somewhere on MSFS Forum:

 

DC6_AP_ON#43401 (>K:ROTOR_BRAKE)

DC6_AP_OFF#43401 (>K:ROTOR_BRAKE)

DC6_AP_HANDLE_ON#40401 (>K:ROTOR_BRAKE)

DC6_AP_HANDLE_OFF#40401 (>K:ROTOR_BRAKE)

DC6_AP_PITCH_UP#440 100 * 8 + (>K:ROTOR_BRAKE)

DC6_AP_PITCH_DOWN#440 100 * 7 + (>K:ROTOR_BRAKE)

DC6_AP_ALT_HOLD_ON#43601 (>K:ROTOR_BRAKE)

DC6_AP_ALT_HOLD_OFF#43601 (>K:ROTOR_BRAKE).

 

Not sure what to do with it so I tried a new event list in FSUIPC

0=Mobiflight.DC_6_AP_ON  etc

It appears in the FSUIPC lists and I can assign it but it doesn’t do anything.  It was just a punt and didn’t expect it to.

 

But no luck.  Any ideas?

[John Dowson]

10 minutes ago, Maltloaf said:

But no luck.  Any ideas?

They are Rotor Brake controls. PMDG use this mechanism a lot. In FSUIPC, assign to the Rotor Brake control in the drop-down menu, and give the appropriate number for the parameter, so for:
   DC6_AP_ALT_HOLD_OFF#43601 (>K:ROTOR_BRAKE)
you would use parameter 43601. Check the PMDG SDK documentation for a list of available Rotor Brake control codes.

14 minutes ago, Maltloaf said:

Not sure what to do with it so I tried a new event list in FSUIPC

0=Mobiflight.DC_6_AP_ON  etc

It appears in the FSUIPC lists and I can assign it but it doesn’t do anything.  It was just a punt and didn’t expect it to.

I can't see those events in the MF spreadsheet - are you sure they are Mobiflight events?

[Maltloaf]

Seriously! That simple!  They just use the Helicopter Rotor Brake command with a parameter.  Brilliant!  I now need to work out the 'DC6_AP_PITCH_UP#440 100 * 8 + ' bit, ie what is the 6 fig parameter.  I assume the *8 is something to do with how many increments it moves.  And where the SDK is hinding, but that was far easier than I expected.

 

 

Thanks John

[John Dowson]

10 minutes ago, Maltloaf said:

I now need to work out the 'DC6_AP_PITCH_UP#440 100 * 8 + ' bit, ie what is the 6 fig parameter.  I assume the *8 is something to do with how many increments it moves.  And where the SDK is hinding, but that was far easier than I expected.

I can't really help you with this as I don't have the DC6 or access to the documentation. If you are having issues deriving the parameter to be used, you could create a new topic with a relevant title that would attract other DC6 users, or ask on the PMDG forums.

[Maltloaf]

Do these show in the event log?  Mine seems to be contiously logging Light Potentiometers to the extent you can't read anything?