Paul Henty

Yes, you can get the latest version on NuGet - it's called FSUIPCClientDLL. It targets all versions up to .NET7. Full details are on the website: http://fsuipc.paulhenty.com Paul

IsOpen is true because it's connected to FSUIPC7. The counter is probably doesn't update until the player has loaded an aircraft. It should start counting up when you start a flight. This seems correct then. If it's sticking at 219 then there is no activity. The ValueChanged property on 0x337E will be false. So your app knows that MSFS has been unloaded. The activity counter might also stop when the user has ended the flight and is back in the menus. Paul

You need to be checking the ValueChanged property of offset 0x337E. If you close MSFS and this offset is still changing (counting up), you'll need to ask John Dowson in the FSUIPC7 support forum if he has any other ideas for detecting if MSFS is unloaded. Paul

Hi Andy, The IsOpen property refers only to the FSUIPC connection, not the flight sim. Prior to FSUIPC7 this was effectively the same thing as FSUIPC ran inside the flight sim. WideClient.exe and FSUIPC7 run outside of the flight sim, so the connection will be open if they are running, even if the flight sim is not. If you want to know if the flight sim is open you can try polling offset 0x337E (activity counter) to make sure it's changing. See the notes in the documentation as there are times it might not update (e.g. loading new aircraft). Paul

These module are only for reading and writing LVars and HVars with the MSFS flight sim. They are not for any other sim (e.g. P3D) and cannot be used for reading/writing offsets. If you're using MSFS and the aircraft you are using provides LVars for the data you need (e.g. flaps position) you could rewrite your app to use LVARs. You will need to use the MSFSVariableServices class in my DLL. There is more info and an example project here: http://fsuipc.paulhenty.com/#downloads The example project will let you read LVars so you can check that you can get all the data you need before you start coding. (Note that the WASM module is installed with FSUIPC7. The FSUIPC_WAPID.dll needs to be downloaded and placed in your project. It should be set to be copied to the output folder when the project builds. Paul

The only way without WideClient is to run the app on the same PC as the simulator. Paul

Hi Ramon, It doesn't look like focus is the problem then. I afraid I can't suggest anything else. I can't see any reason that your program reading some data would stop your CDU working. I'm not sure what you mean by this. If you're running your software on a different machine that the flight sim then you have to use WideClient. If you want it to talk directly to FSUIPC you need to run it on the flight sim machine. You don't need to make any change your software to do this. It will automatically detect either FSUIPC or WideClient. Paul

Hi Ramon I not sure what the problem could be. There should be no problem having multiple software programs using the same Wideclient connection. I don't know how your CDU and the software works. Does the software need to have focus to work? If the CDU hardware is just seen as a keyboard then it probably needs to be the focused application. Having your own software in focus would stop it working. If that's not the problem, you'll need to think about what your software is doing that could be interfering with the CDU software, or the communication with the CDU hardware. E.g. if the CDUs are on a COM port, is your software also using COM ports? The same one? I may have some more ideas if you can let me know more about what your software does and how the CDUs are connected and communicate with Prosim. Paul

The top 4 errors are because Windows has flagged the files as coming from the internet. If you right click them in the File Explorer and select properties you'll find an option to unblock them. It might be better to unblock the ZIP file and then unzip it again. The 6 warning should resolve when you build the project for the first time and the NuGet components get automatically downloaded and installed. Paul

Hi David, You should just choose the update option here and let VS re-target to the 4.8 framework. It will work fine. The example projects target 4.6.2 because that is the earliest version that Microsoft still support at the moment. Paul

Hi Jason. You'll need to ask John Dowson about this in the MSFS (FSUIPC7) support forum. Paul

Hi, You are getting the warnings because my DLL depends on the Win32 API and the WinForms library . Those are not included in the .NET Standard 2.0 specification. It's telling you that if you use my library, your application will no longer be .NET Standard 2.0 compatible. e.g. It won't run on Linux. Running it on a Windows .NET 8 machine will be fine because that platform does include the Win32 API and the WinForms library. Since my DLL cannot work on any platform except Windows I cannot make it target a cross-platform specification like .NET Standard 2.0. Even the .NET versions I do target have to be the specific 'windows' versions. e.g. net6.0-windows not net6.0. If you must use Standard 2.0, the only thing you can do is tell VS to suppress the warning, but your app will not really be compatible with Standard 2.0. Paul

Hi Kees, This forum is for .NET programming; your questions seems to be about Lua so this isn't really the best place to get help with that. However, you'll probably get better performance by using the lua event system for LVars: event.Lvar("lvarname", interval, "function-name") This will call the specified function when the value of the LVar changes. That function can then set the value in the offset. I think this will reduce the processing from the current situation where you are reading the writing every LVAR every 100ms. I don't really know lua that well, so If you want more information about this, please ask John Downson in the main FSUIPC forum (not any of the sub-forums) at the link below. https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/ Paul

My DLL has no way to access SimConnect variables. I know FSUIPC7 has a way to map a simconnect variable to an unused offset, but I'm not sure if this works with a whole structure, or if it works with earlier versions of FSUIPC. @John Dowson will be able to tell you if it's possible to access this simconnect data via offsets. If he doesn't see this and reply here, please ask him directly in the main FSUIPC support forum. Paul

Hi Robert, I don't know anything about the P3D shared cockpit feature, but it sounds like these particular variables are not getting shared between the copies of P3D. I guess P3D can't share everything due to bandwidth, especially if you're using third-party aircraft. FSUIPC itself doesn't do any cockpit sharing so offset values will also not be shared unless they are backed by P3D data that is shared. So writing to spare offsets on one copy of P3D will not be seen on the other. I don't think there's an easy way to do this. You'll need to come up with a way to pass the data between the two PCs yourself. The obvious way is probably to use a TCP link between your application running on the the server and the client(s) and pass the LVAR data between them. .NET has a TcpClient and TcpListener class. Your application can then exchange the LVAR data over the TCP link and update the local copies of the LVARs using FSUIPC. There might be some .net libraries that make data exchange easier than writing your own networking code, but I've never looked into this. Paul