kingm56

I hope you're doing well and enjoyed your holiday, John. I'm experiencing an issue with the FBW A320 (latest developmental version) and FSUIPC 7.3.6. In short, I'm getting the following error after a few minutes: [INFO]: **** STARTING FSUIPC7 WASM INTERFACE (WAPI) VERSION 0.5.10 (WASM VERSION 0.5.9) [INFO]: CONNECTED TO MSFS [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_TransmitClientEvent for EVENT_SET_HVAR failed!!!! The errors do not occur with other aircraft, just the FBW A320; currently, I only have two Aircraft in my community folder (PMDG and FBW). I'd appreciate any ideas you might have. Thank you, John. -Matt FSUIPC7.log

Thank you, my friend! By the way, I'm seeing a lot of "ERROR SIMCONNECT_REQUESTCLIENTDATA FOR LVARS FAILED" errors in the log. The errors are random but often.; they occurred with I updated the to FSUIPC 7.3.6 and WAPID.dll 0.5.10. Any ideas?

Hey John That's precisely what I mean; I understand why we can't read the 'old' PMDG 7xx Offsets. However, I don't understand why we can't write them via Offset 3110. I tried using the same method I used in P3D but can't seem to get it to function in MSFS. EDIT: Disregard - I had to recompute event IDs to meet Rotor Brake...all good now. Still, I hope we're able to read the OFFsets one day. Thank you, John.

Hey John! Would that explain why we can't read the offsets vice setting PMDG events via simconnect, which are facilitated via OFFSETS 3110 and 3114? I understand why we cant read them, but I'm confused why we can't set PMDG events.

Thanks, Paul; I assume it has something to do with the increase in LVARS. If there's anything I can help you with, please let me know. -Matt

MSFSVariableSercvices v1.2 does not work with FSUIPC_WAPID.dll and FSUIPC v7.3.5. Program crashes when connecting to MSFS. My program does the same so there appears to be some larger issue I hope John can fix. I reverted back to previous FSUIPC and WAPID and all is good.

Paul, I just tried SPAD and it works flawlessly. Really at a loss why it doesn't work via your .dll.

I have SPAD installed; let me try to manipulate a control and get back with you

Absolutely, all other normal events work; it's simply the events associated with PMDG controls that don't work. It's odd the events work with SPAD and not FSUIPC.

Paul, FSUIPCConnection.SendControlToFS(PMDG_737_NGX_Control.EVT_OH_ELEC_BATTERY_SWITCH, 536870912); //Single left mouse click Maybe it's the mouse flags that's changed? SendControlToFS method sets offsets 3114 and 3110;

Paul, Any reason we can’t send events via your .dll, similar to the video posted. I tried sending multiple events hoping they would work but they appear to have no impact. Manipulating the LVARS only seems to impact the animations without regard to the actual systems. For example, you can ‘flip’ the battery switch but not happens.

Hey Amine, I ended up writing my own class to capture joystick events; I'm not sure why those offsets no longer work. John and Paul could possibly offer an explanation, as well as fix them going forward.

Good evening and happy Easter, John! When reviewing my logs, I notice the following error: Different WASM version: The WASM version is 0.5.8 while the WAPI version is 0.5.6. This may cause issues However, the download page still list FSUIPC WASM Module 0.5.6 as the current version. Is there another section to download 0.5.8? THANK YOU -Matt

John, Worked like a charm; thank you! Any chance of including the Airbus A330-900neo.hvar file in your next build? If not, it's not a big deal to simply copy the A320.hvar and rename. Again, thank you for taking the time to help. Matt

Good evening, Mr. Dowson. I have a question pertaining to Hvars; specifically, what value does FSUIPC7 use to load Hvars? I thought it could be offset 0x3500, but that doesn't appear to be correct. In short, the headwind A330 shares the exact Hvarsas the FBW A320; I was hoping there was a configuration within FSUIPC to have FSUIPC load the a320 hvars when the Headwind A330 is loaded. Thank you for the great customer service and always being there to answer my questions. Truly appreciate you and your dad. Matt

FSUIPCLog.txt Thank you, sir! Log attached

Hey John! Is it possible to manually install WASM? I'm trying to install (clicking WASM) but it's not installing. Any ideas on why it might not be installing? Thank you! Matt

Mr Dowson, That worked perfectly...thank you!

Sir, Is there a control or offset to manipulate the window heat (787 and 747)? The option is available via MSFS control options; so, I'm hoping there's a control I'm missing.

Hey Paul 1. Joystick is registering as 0 2. Button is 1 3. Offsets are 0 and 56 Don't worry, my friend. I went a head and wrote my own class using SharpDX dll. Thank you as always though! -Matt

Hey Paul, I assumed it doesn't work because I tested with your FSUIPCExampleCode_CS 1.2.0 with .dll 3.2.17. Clicking on Listen for Joystick Button Presses, and clicking on Button 1, does not impact the counter at all.... there's no exception thrown. The Respond to Key Presses' class/methods work perfectly; so, it could have something to do with the device ID; I know windows changed this methodology in Win10. I tried to change the Joystick ID from 0 to 5...no joy. -Matt

Paul, Checked with John, he states the offset x2910 is active and functioning properly. Any plans to update your dll to take advantage of said offset? -- Hot Button test at offset 0x2910 -- First, write to offset to signal the button I am interested in -- I will use my joystick #1 button #6 for both off to on and in to off ipc.writeUD(0x2910, 0x000681) -- where 0x81 (129) is joystick 1, 06 is button 6 and 00 is for off-to-on -- function to register change function hotButtonActivated(offset, value) if value ~= 0 then ipc.log("Hot button changed: " .. value) -- clear flag ipc.writeUB(offset, 0); end end -- event on trigger event.offset(0x2913, "UB", "hotButtonActivated")

Thanks for checking, John. I'm accessing via Paul's dll; so, it's probably on that end.

Good evening, Mr Dowson I am having issues with FSUIPC and WASM; specifically, I have installed FSUIPC with the WASM module (attachment 1), which connects successfully to MSFS. However, when I attempt to go to FSUIPC > Addons > List LVARS/HVARs, it's greyed-out. Typically when this happens, it's because FSUIPC cannot access the module folder; however, my module folder is placed in the correct location (attachment 1 and 2). Can you offer any suggestions I'm missing?

Hey John! It doesn't appear to be working. I confirmed with Paul over at his .dll forum; if you could add to your long list of offsets to work Id be grateful. Matt