AirPanther

My apologies if this has been answered... I couldn't find the answer. My P3D has crashed to desktop a few times, and I'm wondering; can sending lots of data to P3D via FSUIPC, while the scenario is loading cause it t crash? I'm repeatedly sending a control inhibit, and not sure if that is the culprit. In FS Interrogate, offset 0x3365 "In Menu or Dialog" turns to non-zero (usually 3) anytime the sim is loading or in a menu, so I'm wondering if checking for that offset to be 0 before writing data to P3D would lower the likelihood of a crash? Thanks, Robert

Are you referring to the APU EGT? If so, have you checked 0x648C (Length 4 [FLT32])? Have you checked the "Offset Mapping for PMDG 737" document from the PMDG SDK? Maybe PMDG is doing a more complex/accurate calculation and storing it in a custom area? Robert

Paul, Thank you very much for your response. That's what I ended up doing! Since my program was already sending network packets, I'm just sending the flags across the network whenever they change, and other copies of the software listen for the flags and update their local LVARs. So far, works really well. Thanks again Paul! Robert

Good morning, My app uses LVARs to read/write to Prepar3d, allowing gauges to read the LVARs and show failure flags. It works very well, except, in shared cockpit multiplayer as it appears local variables are truly only local. Any idea how to synchronize LVARs across multiple computers with shared cockpit? There are approximately 50 LVARs to keep in sync. Would I have to store each value in a seperate offset then have a client app to read it and process the LVARs on the individual computers? Seems like there's probably an easier way? Thanks, Robert

That's great, I will grab the update. Thanks much Paul! Robert

Wow...I FINALLY found the needle in the haystack... mainly while typing up my findings to you, Paul I finally figured out this was an issue caused by writing to FLOAT64 variables. In my app, in the length fields, I use length 9 to differentiate between Int64 and Float64 (both length 8). I do the same thing with length 5 for Float vs. Int32 (both length 4). When initializing the offset, I didn't realize I was passing the length 9 to your module, when instead, I should have been converting 9 to 8 and 5 to 4 before initializing the offset. This issue has always been there... but looks like I hadn't been using any FLOAT64 variables. So offset initialization didn't even occur in my mind as a possibility. I ironically, the reads work fine, especially since battery voltage is only 2 digits. Man... this is one of those bugs I need a strong beverage after............. I really appreciate your help Paul. Talking through it was a big help, and made me look at things from angles I hadn't considered. Thank you! Robert

Paul, I truly appreciate your help, but decided to roll back to an earlier build from before the problem happened. It's about 30 days old, but seems like it will be easier to re-stitch the changes, than trying to find the "needle in a haystack" issue that led to this. I changed something somewhere that caused this to break, as it's been working perfectly for quite some time, but can't figure out what the change was. I'm still curious, so I don't break it again, but for the moment, the blocker is averted. I'll keep you posed if the problem becomes revealed as I'm re-stitching the updates. You're super responsive; I truly appreciate it! Thanks, Robert

I went through the code and changed all offsets to not use a group, and made sure the Process() commands do not reference a group, and still getting the same error 😞

Hi Paul, FSUIPCConnection.DLLVersion returns 3.3.8.410 1) I am using a named offset group called "CustomGroup" 2) No multi-threading Robert

Thanks Paul, here's what I get: System.IndexOutOfRangeException: Index was outside the bounds of the array. at FSUIPC.FSUIPCConnection.Process(Byte ClassInstance, IEnumerable`1 GroupNames) in C:\Dev\FsuipcClient\fsuipcClient\fsuipcClient\fsuipcConnection.cs:line 707

Thank you; .NET Framework is 4.8. Just wondering... does it have anything to do with target platform, or anything similar? I'm targeting x64, but have also tried x86 and Any CPU, with similar results. Also, since upgrading, I'm now getting a second error from Process(): Exception thrown: 'System.IndexOutOfRangeException' in fsuipcClient.dll Exception thrown: 'System.Exception' in fsuipcClient.dll Robert

Good morning Paul, I'm on 3.3.8 now; Downloaded from NuGet successfully. I'm not seeing the fsuipcClient.pdb. Where should I look?

Ok, I will start with an update and report back. Thanks, Paul

Paul, DLL Version is 3.1.9.311. fsuipcClient.pdb isn't in the folder, and I can't find it on my system. Also tried downloading from your site (application templates), but can't seem to find it. Where can I find it? Thanks, Robert

Hi Paul, BLUF: Any idea what would cause Process() to generate IndexOutOfRangeException? Whenever I call Process(), I get the following error. The code (reads and writes) has been working perfectly for months, then this error started a few days ago, and I can't figure out what changed to cause this. I still get a successful fsuipc connection, but the reads/writes no longer sync properly to P3D (Presumably because of the error below). Exception thrown: 'System.IndexOutOfRangeException' in FSUIPCClient.dll System.IndexOutOfRangeException: Index was outside the bounds of the array. at FSUIPC.FSUIPCConnection.Process(Byte ClassInstance, IEnumerable`1 GroupNames) at FsuipcSdk.Fsuipcx.Process() in C:\Users\airpa\fsuipcx.cs:line 285 Line 285 is below: public bool Process () { if (FSUIPCConnection.IsOpen) FSUIPCConnection.Process(); // Line 285 return true; } Any thoughts are greatly appreciated, Robert