Jump to content
The simFlight Network Forums

IanAbel

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About IanAbel

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Edina, MN
  1. IanAbel

    Airline and Title not updating...

    Will go get it and start using, thanks again... UPDATE: BRILLIANT, works like a charm, cycled through a couple of dozen a/c and all reported correctly immediately - thanks so much Paul!!
  2. IanAbel

    Airline and Title not updating...

    Good News Paul... let me know if there's any way I can help. Again, new to this stuff but been a developer (almost everything known to man!!) for 40+ years ;)
  3. IanAbel

    Airline and Title not updating...

    Understand... thanks. I wish there was a reliable way to reproduce it, I've tried quite a few variations to see if I can come up with something consistent but no luck I'm afraid. If I go back and forth between several liveries of the same a/c and a second a/c variant, I can usually get it to happen every fourth or fifth time, but never consistent. Not sure what a/c you have for FSX but seems like the feelthere E170/E190 make it occurs, maybe because they vary between having a reg. in several of the a/c and none in others! That's about the best I've got for now. If I can get some more time to test it I'll let you know if I find something concrete...
  4. IanAbel

    Airline and Title not updating...

    Paul, Loaded the latest DLL first... In both FSX (local not Steam) and P3D, the logged variables appear just fine, UNTIL I try and interrogate them, at that point, whilst somewhat inconsistent, the Reg -313C and Airline 3148 seem to be being overwritten by the prior values! It seems to occur most consistently if the aircraft selected is another variant in the same aircraft.cfg. If the reg# is populated and I select an a/c without a reg., when I run the update request the next time the logged variables change to show the "last values" in the app, hope that makes sense. It seems like the FSUIPCConnection.Process call is updating those two offsets. Any ideas? Below is the code I wrote to test it, not sure if it helps or if Pete should be the one to contact? Imports FSUIPC Public Class Form1 Private RegID As New Offset(Of String)("AircraftInfo", &H313C, 12) Private airline As New Offset(Of String)("AircraftInfo", &H3148, 24) Private aircraftType As New Offset(Of String)("AircraftInfo", &H3160, 24) Private aircraftModel As New Offset(Of String)("AircraftInfo", &H3500, 24) Private nameTitle As New Offset(Of String)("AircraftInfo", &H3D00, 96) Private Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load FSUIPCConnection.Open() End Sub Private Sub ButtonUpdate_Click(sender As Object, e As EventArgs) Handles ButtonUpdate.Click FSUIPCConnection.Process("AircraftInfo") ' Now display the data on the form DataRegID.Text = RegID.Value DataAirline.Text = airline.Value DataACType.Text = aircraftType.Value DataModel.Text = aircraftModel.Value DataName.Text = nameTitle.Value End Sub End Class
  5. Paul, Having found a problem with getting a reliable return for offsets 3148 (Airline name) and 3D00 (aircraft title), I used your your FSUIPCExampleCode_VB (extremely helpful BTW!!), and in the grouping section simply replaced the first two offsets to those I'm interested in above. Running P3Dv4, it is very inconsistent in updating, often retaining the last data read even through several changes of a/c. Is this a problem with P3D? It almost seems as if the change is not registering somehow even though other values report correctly. I'd like to obtain this data, but it doesn't seem to work. Any help/suggestions greatly appreciated. EDIT: Offset 313C acts the same way...whereas 3500 (model) seems more consistent.
  6. Paul, Thanks and I'm sorry I put you too that work. Since you confirmed it actually works, I re-checked the code (I've inherited it), turns out the Connect was wrapped in a "Try" that included updating some FSUIPC setting, AND it was throwing an arithmetic exception since the batterymaster offset was declared as 8-bytes instead of 4. Interestingly FS2004 seems to be the only sim where adjacent bytes result in a huge number which throws an exception being moved into a long! Onward and upward, I'm hoping to master this but grateful for the support on the forum here, especially your timely and so very helpful assistance. Regards, Ian.
  7. Paul, Thanks for the quick reply. I'm actually on Win7 with my test version, but I'll try running both as admin, and one of the users (who is very savvy and can be relied on to provide accurate info) is on Win10 but said he always runs FS9 as admin and also ran my ACARS as admin too.
  8. I'm sure there may be an obvious answer, but I can't find it <sigh> Developing an ACARS application for BAVirtual, I have only one real problem. FSUIPCConnection.Open() works without issue for all flavors of FSX, P3Dv3/4 and X-Plane 10/11, the only sim that refuses the connection is FS2004. This is vb.net/Visual Studio, using the latest client DLL (3.1.5). FS2004 reported by several beta testers AND on my own installation, using FSUIPC 3.991 returns an exception and the ex.message "Error #12: FSUIPC_ERR_SENDMSG. Error sending message to FSUIPC." Try ' Attempt to open a connection to FSUIPC (running on any version of Flight Sim) FSUIPCConnection.Open() Catch ex As Exception If DebugingOn And mainfrm.debugRepeatCount < 10 Then WriteDebugEntry("", "FSUIPCConnect", ex.Message) mainfrm.debugRepeatCount += 1 End If End Try Suggestions? I'm certainly doing something wrong, just don't know what it is :(
×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.