kingm56

Good evening, Paul. First, thank you for all your help to date; I truly appreciate it! I wanted to ask if your DLL allows reading SIMVARs in MSFS. I know that John provides a method using myOffsets.txt, but that file needs to be placed in the FSUIPC directory, which isn't ideal for an application used by multiple people. Would your DLL provide a way to access SIMVARs directly without relying on myOffsets.txt? I don't need to write to them, just read. Thanks for your time!

Paul, First, I hope you're doing well. When Time permits, I hope to leverage your expertise. I’m writing managed C# code that communicates through FSUIPC. My goal is to toggle the fuel pumps using the MSFS event ELECTRICAL_BUS_TO_CIRCUIT_CONNECTION_TOGGLE (event ID 67076). However, I’m unsure about the correct second parameter to send in order to toggle the specific fuel pump switch(es). FBW API states: The individual pumps are controlled via circuit connections. The corresponding circuit connection numbers are as follows: Fuel and Trim Tank CIRCUIT CONNECTION NUMBERS | | 2 | 3 | 64 | 65 | | | 66 | 67 | 68 | 69 | | | 70 | 71 | 72 | 73 | 74 | | | 78 | 79 | 76 | 77 | 75 | | | | | | | 80 | 81 | | | | | | Example Reverse Polish Notation (RPN) for Fuel Pump Circuit Connection 2 1 (>K:2:ELECTRICAL_BUS_TO_CIRCUIT_CONNECTION_TOGGLE) I'm every, I'm unable to manipulate the switches via SendControlToFS with appropriate ID method. I assume my value is incorrect. Again, I would appreciate your expertise, when/if ime permits.

This one works, John! Matt

John, I hope you had a wonderful Holiday. Since .18, I've noted the offsets ID'd in the title no longer return values; they're null. Can you confirm they're still functional in 7.5.1? Thank you!

John, When you get a minute, would you mind checking the FSUIPC WASM Module 1.0.6 + WAPI 1.0.4 link to ensure the right FSUIPC_WAPID.dll is uploaded? I'm getting the following error in my application: **** The installed WASM version is 1.0.5 while the WAPI is expecting WASM version 1.0.6. Please update the WASM module as this may cause issues. I have abstracted FSUIPC_WAPID.dll from FSUIPC-WASMv1.0.6.zip.886\FSUIPC_WAPI.zip\FSUIPC_WAPI\dll\ file and placed in my .exe directory. Thank you, John! Matt

I hope all is well, John! Concerning the subject, is there an FSUIPC7 DWORD offset to input the MINS akin to 6588 (AIR_LandAltWindow); I'm hoping one exist and you just haven't had an opportunity to to update the documentation. Matt

Thanks Paul; for some reason, only the fsuipcClient.xml is downloading, not the actual dll.

Paul, Is there another option to get the current FSUIPCClient.dll for .net6? I'm getting errors when trying to download via nuget package. I suspect it's due to my ISP/overseas. Matt

Worked perfectly, John. Thank you for the quick fix! Matt

Thanks John! I will test this evening and get back with you.

Perfect. Thank you, John!

Hey Paul, I was using WAPID 0.9; what's odd is everything works fine until calling MSFSVariableServices.Stop() and/or FSUIPCConnection.Close(), both seem to generate the crash. Where can I find the logs? The only relative logs I see is the FSUIPC7.log, which I provided above. I don't see any other logs (except for install and uninstall log) in my FSUIPC7 directory, or in the MSFS Community folder.

Thanks, John; I was actually thinking the same as I had a similar issue when SU10 was officially released.

Paul/John, As always, I appreciate your assistance. To better define the issue, the problem surfaced when updated to WAPID 1.0 and FusipcClient.dll 3.3.4.404; The app connects without issue and MSFSVariableServices works fine. However, when attempting to close the connection, the app immediately freezes and crashes; after a few attempts, it will also crash MSFS. Paul, your MSFSVariableSrvices_CS_V1.4 also crashes when attempting to stop MSFSVariableServices. Rolling back to FSUIPC7 7.6.16 and the previous WAPID resolves the issue, which I have asked my users to do for now. Click Event Closing FSUIPC private void Connect_Click(object sender, EventArgs e) { try { if (FSUIPCConnection.IsOpen) { try { // Connection is open so stop the timer and close the connection this.fltSimTimer.Stop(); FSUIPCConnection.Close(); ConfigPicBoxes(picBoxConnect, Color.White); if (Classes.FlagMgmt.chkLstThreadActive == true) { Classes.Copilot_CommonChkLstTasks.copilotChkLstFlowThread.Abort(); } ConfigureButtons(); } catch (Exception) { } } Event Logs Faulting application name: FSUIPC7.exe, version: 7.3.1.7, time stamp: 0x63f77964 Faulting module name: FSUIPC7.exe, version: 7.3.1.7, time stamp: 0x63f77964 Exception code: 0xc0000005 Fault offset: 0x00000000000f0496 Faulting process id: 0x0x5808 Faulting application start time: 0x0x1D94A030C1CCBCF Faulting application path: D:\MSFS Utilites\FSUIPC7\FSUIPC7.exe Faulting module path: D:\MSFS Utilites\FSUIPC7\FSUIPC7.exe Report Id: 015a8111-c695-49c2-993f-bfd10ae3584f Faulting package full name: Faulting package-relative application ID: Faulting application name: FSFO_NEXT.exe, version: 1.2.11.0, time stamp: 0x829e5f1b Faulting module name: FSUIPC_WAPID.dll, version: 0.0.0.0, time stamp: 0x63f4bd2f Exception code: 0xc0000005 Fault offset: 0x0000000000003896 Faulting process id: 0x0x6FE4 Faulting application start time: 0x0x1D94A0405F731C2 Faulting application path: C:\Users\kingm\Dropbox\FSFO\FSFO_NEXT\FSFO_NEXT\bin\Release\FSFO_NEXT.exe Faulting module path: C:\Users\kingm\Dropbox\FSFO\FSFO_NEXT\FSFO_NEXT\bin\Release\FSUIPC_WAPID.dll Report Id: 70aa165c-3f0c-42d0-a5af-cb32313a2605 Faulting package full name: Faulting package-relative application ID: Paul MSFSVariableSrvices_CS_V1.4 also crashes when attempting to stop MSFSVariableServices. It also crashed MSFS when I clicked STOP Application: MSFSVariableServices_CSharp.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFA9B6D3896 Stack: Faulting application name: MSFSVariableServices_CSharp.exe, version: 1.4.0.0, time stamp: 0x9c35aaae Faulting module name: FSUIPC_WAPID.dll, version: 0.0.0.0, time stamp: 0x63f4bd2f Exception code: 0xc0000005 Fault offset: 0x0000000000003896 Faulting process id: 0x0x70E4 Faulting application start time: 0x0x1D94A080C75EFA2 Faulting application path: C:\Users\kingm\Desktop\Development\MSFSVariableServices_CS_V1.4\MSFSVariableServices_CSharp\bin\Debug\MSFSVariableServices_CSharp.exe Faulting module path: C:\Users\kingm\Desktop\Development\MSFSVariableServices_CS_V1.4\MSFSVariableServices_CSharp\bin\Debug\FSUIPC_WAPID.dll Report Id: 95e7a8cf-b4c6-4e84-bed1-1ac075448fb2 Faulting package full name: Faulting package-relative application ID: Please let me know how else I can help!! John The part in underline is new, is this normal? [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.0 (WASM version 1.0.0) using connection -1 FSUIPC7.log

Evening Paul, I updated to the WAPID to 1.0 and now when disconnecting my app ( FSUIPCConnection.Close();) from MSFS via click event, my application now crashes. When reviewing the event log, all I get is faulty application WAPID.dll. I wonder if I also need to close the wapi connection too? It also crashes MSFS.

That's perfect...thank you!

Good evening, John. Concerning offset 034E, it supports 4-dights in BCD format; however, MSFS has a lot of frequency that require 5 digits. Is there another offset I should be using to set the radio freq to 123.455 (example) vice 123.45. I know there's an offset in FSUIPC6 that allows your to read five digits, but not write. Hope you had a good holiday. Matt

Sorry, Paul. I'll check with John about the errors. PMDG_NG3_SDK.h

Hey Paul! I've attached the SDK; as you can see, it looks a lot like P3D's SDK. PMDG_737_MSFS_SDK.pdf

Hey Paul, I hope you're doing well! I just had a look at PMDG's newly released SDK and it appears to very similar to the P3D version; however, I notice you .dll does seem to have any impact on some functions. For example, setting the Alt works fine in P3D, but not MSFS: FSUIPCConnection.SendControlToFS(PMDG_737_NGX_Control.EVT_MCP_ALT_SET, 11000); PMDG_737_NGX_Control.EVT_MCP_ALT_SET = 84137 The event numbers appears to be the same; so, I'm curious if you might offer any suggestions why it has no effect.

My apologies, John; I was working off an old playbook.

John, I'm having the same issue; I tried the edit to the FSUIPC7.ini with not effect. I increased my logging in hopes you may find what I can't. FSUIPC7 (3).log

Thank you, Paul! Matt

Hey Paul! john was kind enough to provide the new WAPID.dll to me. www.dropbox.com/s/ryv8oz2jp9nzqat/FSUIPC_WAPID.dll?dl=1

Confirmed…the dll needs to be updated. Is there something I can do to help, Paul?