John Dowson

It could be that those offsets are not populated. I am going to put together a list of working/not working offsets so that these can be reported to PMDG once the SDK has been released. You could check the following offsets which are the most recent ones i have checked as working; Otherwise, you can add the following to the [General] section of your FSUIPC7.ini which will log the reception of PMDG client data: TestOptions=x400 John

Please see the description of how FSUIPC's tiller/rudder blending works in the box on page 30 of the FSUIPC7 User guide. Also see the ini parameters MaxSteerSpeed in the Advanced User guide (P9). Maybe try with MaxSteerSpeed=Q20,30,0,60 With that,, you would have 0% rudder up to 20 knots, linear increasing to 10% from 20-30 knots, then linear increasing to to 100% from 30-60knots. Adjust as needed. John,

You don't need the lua script if using the presets.

Then the location in your UserCfg.opt file is incorrect: I do not know why this is incorrect...very strange... Do you have a Steam or MS store installation? If using Steam (which the installer detects due to the presence of the UserCfg.opt file under $APPDATA$\Roaming\Microsoft Flight Simulator), you could try correcting this by changing the InstalledPackagesPath location (it is at the end of the file) to the correct one, and then re-install FSUIPC7. If you are using an MS Store installation, you need to uninstall FSUIPC7, delete or rename the file C:\Users\josem\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt and then install FSUIPC7 again. John

But the problem looks to be that the offset value isn't changing, no? Presuming that is the correct offset (I have only spot-checked some and calculated the rest from an SDK file) and if so then the data isn't being provided correctly. As the SDK for the PMDG 737 for MSFS has still not been published, there is not much that can be done at the moment. I will take a look at this to verify (tomorrow now) and will start to maintain a list of of valid/invalid offsets for the PMDG 737 - should have done this at release! John

Strange...you should get an application crash event (maybe preceded and followed by other events) when you get a CTD. But Tobi and MCE would be your best bet for support on this, as you said.

Try with: ipc.createLvar("ipcpmdg_ELEC_annunAPU_GEN_OFF_BUS", 1234) ipc.createLvar("ipcpmdg_APU_EGTNeedle", 4321) ipc.reloadWASM() ipc.sleep(1000) ... i.e. you need to reload thee lvars from the WASM a before they become available. Note also that if a reload results in more lvars being found than previously (which of course there will be as you have created some), then this will/should trigger the reload of the [LvarOffsets] section from the ini. John

That is as (newly) documented : I guess the next byte 65FA is for the copilot button. The other offsets must be correct then, just not populated correctly by PMDG. Cheers, John

Check for crash and failure events with Windows Event Viewer - may help.

FSUIPC has nothing to do with Tobi and knows nothing about it, as do I!

Ok. But if you don't create the lvars, they won't exist and they will be ignored. But I need to see your pmdg737.lua script - you forgot to attach that... John

The license has now been updated. John

Yes, that's what I (eventually) understood, but thanks for clarifying. Sounds like it is an issue for PMDG, but as the SDK has still not yet been officially published, there is not that much that can be done at the moment. I will take a look though, but, as I said, I'm not that familiar with the 737 at the moment and I'm not sure how to get these to light up - they flash or either remain off. I need to get more familiar with the aircraft's systems and cockpit layout anyway... Cheers, John

You mean that they don't hold the expected data values... Not sure about that one - do you mean that that also does not hold the correct value? Which switch is that? Is there a mapping of (lvar) switch number to function anywhere? You can control the switches using the Rotor Brake controls. But I guess you know that and are trying to determine the state of these switches, no? I'll check to see if I can see any lvars that hold the state. John

No...please read the lua library documentation - and also the template I showed you. It would be more like this: myEventFunction(controlnum, param) -- Check parameter of Rotor Brake control to see if if param == 7715 then ipc.control(1071,77) -- send 'M' key (77) press elseif param == 7717 then ipc.control(1072,77) -- send 'M' key (77) release end end -- Wait for control to be received event.control(66587, "myEventFunction") If you want to send separate press and release, you need to use the separate FSUIPC added controls to send the key press (1071) and then the key release (1072) - ipc.keypress would send them both together. Note also that you need to have the lua running - it should be started from the [Auto] or, better, [Auto.xxx] (where xxx is the profile name) section of your FSUIPC7.ini. Again, consult the documentation if not sure (Advanced User guide). John Later: Btw, I used 77 (the 'M' key) as that is what you were using, You change this value to any other key or key+modifier - see the Advanced User guide for the keycode and shifts/modifier codes/numbers.

Nothing complex - something along the following lines - where <controlnum> is the control/event received when you press the button in the VC, and <keycode> is the key press you want to send: myEventFunction(controlnum, param) -- send keypress here - may need to check the control' parameter first if a Rotor Brake control ipc.keypress(<keycode>) end -- Wait for control to be received event.control(<controlnum>, myEventFunction) But as I keep saying, you can only do this if some sort of control/event is sent when press the button in the VC.

I am slightly confused by your post. The PMDG offsets are not lvars, it is additional read-only data provided by PMDG. What happens> Show me the lua scrip, and activate logging for lua plugins and see if you get any errors. Note that if creating youy own lvars, it may take a short time before that lvar is available for reading/writing. That enables the broadcasting of the data to enable the FSUIPC PMDG offsets (read-only) to be populated. Do those lvars exist, or are you creating them? You cannot add lvars that you create using the [LvarOffsets] section as this is only processed when the initial lvars are received from the WASM. If they exist when you list them but are not available for adding to offsets, this implies that they had not been created when the WASM scanned for existing lvars. This happens with complex aircraft as it can take up to a minute or so to create all the necessary lvars. You should update the LvarScanDelay FSUIPC_WASM.ini parameter - this defaults to 5 (seconds) but is recommend to start with a value of 45 or so (see the Advanced User guide for details). Any further issues, please show me your FSUIPC7.ini as well as the FSUIPC7.log file, and any lua scripts if the problem is there. John

Ok, so your problem is that FSUIPC is not running, i.e. not auto-starting. For auto-start issues, please see John

Where is your Community folder? The installer thinks that it is here: C:\Program Files (x86)\Microsoft Flight Simulator\HLM_Packages"\Community\ which is a very strange path...especially that strange double-quote... Do you have a steam install or an MS store install? If the former, please show me this file: C:\Users\josem\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt If you have an MS Store installation, remove/delete that file and re-install. John

You still have some assignments to virtual buttons that should be removed (although these should not be having any affect): Your log also shows an error in your Rotaries.lua: Other than that, your log shows the events being sent as assigned, although its difficult to tell as you have obviously changed your assignments when doing this, and I can only see the assignments as they were when you exited. It is always better to provide a matching FSUIPC7.ini and FSUIPC7.log file for each test. Could you switch to using the Baron G58 for your tests - it is in the same profile as your Britten Norman Islander, and I can check/verify that here. In fact, I have just tested and all of the avionics master controls work - Toggle Avionics Master, Avionics Master 1 On/Off/Set, Avionics Master Set. So please try in that aircraft, or is this problem specific to the Britten Norman Islander?

But I already answered this...this is only possible if pressing the button emits an event or changes something (i.e. simvar or lvar) that can be picked-up by FSUIPC, and you would need a lua script to intercept that and send the key press. FSUIPC does not react to mouse operations in the FS, only to the data it receives from the result if that mouse operation, usually an event. If the switches are animated, then the first thing you should try is to set logging for Events (non-axis controls) and flip the switches in the VC and see if any event is logged. The PMDG aircraft for P3D use custom controls, and the FSLabs uses the Rotor Brake control with the parameter indicating the switch and the mouse action, See if any of those are logged. If so, then a simple lua script can intercept these and send the key press. Many aircraft (GA) have a PTT button on the yoke, but this generally doesn't do anything as default ATC does not require this (it uses menu options). Toy would assign this by button to PTT for the ATC system you are using.

The current license only expired today. I will generate a new one tomorrow or Friday. I like to leave a day or two between the expiry of one trial license before I generate the next one one. Sorry for the inconvenience. John

What aircraft are you using, and does the PTT button in the VC actually work? I thought this was inoperative on most, if not all, aircraft... If there is a functioning PTT button in the VC, you need to see if activating this emits an event (it will be a custom event - there are no standard events for PTT) or changes a simvar or lvar. If so, you could use a lua script to pick up this change and then send the key press - which would go to the FS, vPilot would have to have this registered as a hot key to pick this up. If you let me know what FS and what aircraft you are using (and if I have this aircraft), I could take a look to see what, if anything, is emitted or changed.

What do you mean by this? The PMDG offsets only report state, you cannot write to them. If the offsets are not holding the correct data, then there is nothing I can do about this - they are just populated from what is received from the FS. I believe those offsets to now be correct, according to the SDK header file that I have, Offsets 0x65EA (MAIN_NoseWheelSteeringSwNORM) and 0x65FD (MAIN_annunSPEEDBRAKE_ARMED) are correct, and those inbetween are assigned based upon the latest NG3 SDK header file. I am not that familiar with the 737, so cannot verify those offsets (it is not clear to me what they should contain), but if there are any issues, nothing can be done until the SDK has been published, and then (assuming the SDK header file is correct - if not I will update once published) it will be an issue for PMDG. Maybe ask about this on the PMDG forums, but I don't think this will be supported (by PMDG) until the SDK is released, but you may get a response from another PMDG user. John

What was the problem? Is everything now working as expected?