[Alternate Download]

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

[Alternate Download]

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

[Program crashes with WAPID 1.0]

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

Matt

[Program crashes with WAPID 1.0]

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

[Program crashes with WAPID 1.0]

Perfect. Thank you, John!  

[Program crashes with WAPID 1.0]

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.  

[Program crashes with WAPID 1.0]

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

[Program crashes with WAPID 1.0]

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

[Program crashes with WAPID 1.0]

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.  

[8.33KHz frequency spacing]

18 hours ago, John Dowson said:

It is the same offset in FSUIPC7 - 0x05C4, and is also read-only. To set the frequency, you need to use the appropriate control/event (or maybe preset, depending on avionics).
Usually you would set the frequency by inc/dec of the current (standby) frequency, and the inc/dec controls should inc/dec through the 8.33KHz spacing.

That's perfect...thank you! 

[8.33KHz frequency spacing]

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

[PMDG SDK]

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

PMDG_NG3_SDK.h

[PMDG SDK]

Hey Paul!

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

PMDG_737_MSFS_SDK.pdf

[PMDG SDK]

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. 

[WASM not working after SU10 update]

8 hours ago, John Dowson said:

Please don't do this if you don't know what logging to set. You already have WAPI debug level logging set (in your FSUIPC7.ini) and that should be sufficient. Turn the other logging off.

From your log, it looks like no aircraft was loaded. You have to have an aircraft selected and be ready-to-fly before you can access or use lvars/hvars/calculator code.

So, please try again and make sure that you have an aircraft loaded and ready-to-fly. If you still have issues, please show me your new log, and also what you actually did - was FSUIPC7 auto-started, or did you start it manually? If the latter, what state was MSFS in when you started FSUIPC7? Note that you should NOT start FSUIPC7 if MSFS is in a pause state.

John

 

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

[WASM not working after SU10 update]

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

[SU10 LVAR]

Thank you, Paul! 

Matt

[SU10 LVAR]

Hey Paul!

john was kind enough to provide the new WAPID.dll  to me. 
 

www.dropbox.com/s/ryv8oz2jp9nzqat/FSUIPC_WAPID.dll?dl=1

[SU10 LVAR]

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

[SU10 and FSUIPC7 MSFS]

1 hour ago, John Dowson said:

I have not updated the WASM zip file yet as I have still not released this. Currently its available in the latest beta download, in the SDK folder, so you will need to download this to get it for now - or use the attached: 

FSUIPC_WAPID.dll 105 kB · 0 downloads FSUIPC_WAPID.h 2.87 kB · 0 downloads

Thank you, John. 

[SU10 and FSUIPC7 MSFS]

John,

Have you had a chance to update the WAPID.dll to work with latest WASM build? Im getting an error with C# app when using the latest FSUIPC beta.  Hoping you’re just crazy busy and didn’t include the new WAPID.dll in the latest WASM module download zip.  
 

The installed WASM version is 0.9.0 while the WAPI is expecting WASM version 0.5.9

[SU10 LVAR]

Hey Paul!

I can read the LVARs via FSUIPC7, which suggest the WASM client is functioning:

a total of 2246 Lvars loaded

However, I cant write to the lvars; this includes using your MSFSVariableService V1.3.

Interesting, I do get the error:

The installed WASM version is 0.9.0 while the WAPI is expecting WASM version 0.5.9

From the FSUIPC log:
112532 Starting WAPI...
   112532   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.5.11 (WASM version 0.9.0)
   112532   [INFO]: Connected to MSFS
   113407   [INFO]: SimConnect_Close done
   117204 C:\Users\imdag\AppData\Roaming\Microsoft Flight Simulator\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
   127813 Starting WAPI...
   127813   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.5.11 (WASM version 0.9.0)
   127829   [INFO]: Connected to MSFS

 

[SU10 and FSUIPC7 MSFS]

Unfortunately, I'm on a multi-continent business trip and really can't troubleshoot myself...frustrating!  The recompile wapid seems to work just fine with every other aircraft, except the Fenix...can't wait to get home and figure this one out. 

 

 

[SU10 and FSUIPC7 MSFS]

Thanks, John; currently, the WAPID.dll just needs to be in the same directory as Paul's .dll.  I guess my struggles are why is the issues relegated to the Fenix.  However, that's my problem to solve :).  Thank you for the quick release of the version of FSUIPC...LVARs seem to load much smoother. 

[SU10 LVAR]

Paul,

I have an interesting problem I'm hoping to get your advice on.  Post SU10, my application will no longer set LVARs; however, it only applies to the FENIX.  John has released a new FSUIPC version with updated libraries and I'm wondering if you're .dll will need the same?

Matt