Garfield_X Posted January 10, 2014 Report Share Posted January 10, 2014 HI It looks to me that when getting the AIPlaneInfo and looking to aircraft that taxi in, i never see the parking variables filled.(GateName, GateNumbering) Or do i miss something? Peter Link to comment Share on other sites More sharing options...
Garfield_X Posted January 10, 2014 Author Report Share Posted January 10, 2014 Just to clarify, i had read that this values are for FSX only, but i would expect that for P3D it would behave similar. But i can be wrong of course. Link to comment Share on other sites More sharing options...
Paul Henty Posted January 10, 2014 Report Share Posted January 10, 2014 Hi Peter, I've just reinstalled my laptop so my FSX/FSUIPC stuff isn't up an running yet. I'll get it installed at the weekend and test this for you - only on FSX though as I don't have P3D. At least if it works on FSX we can rule out a problem with the DLL. Paul Link to comment Share on other sites More sharing options...
Garfield_X Posted January 10, 2014 Author Report Share Posted January 10, 2014 Thanks! And i have only FS9 en P3D installed. :) It could be a FSUIPC issues, as maybe it only fills those values if it is FSX, or it must be coded in de DLL that is only fills those vaules when it is FSX If i need to test something just let me know. Link to comment Share on other sites More sharing options...
Paul Henty Posted January 10, 2014 Report Share Posted January 10, 2014 or it must be coded in de DLL that is only fills those vaules when it is FSX Good guess. Just checked the code and that's exactly the problem. Easy enough to fix though. I'll make a fixed version of the DLL for you over the weekend. Paul Link to comment Share on other sites More sharing options...
Garfield_X Posted January 11, 2014 Author Report Share Posted January 11, 2014 Ok, thanks. And now we must hope that FSUIPC reads those values too if it is P3D :) Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 11, 2014 Report Share Posted January 11, 2014 Ok, thanks. And now we must hope that FSUIPC reads those values too if it is P3D :) It reads everything in P3D that it does in FSX. The rest depends on P3D. Pete Link to comment Share on other sites More sharing options...
Garfield_X Posted January 11, 2014 Author Report Share Posted January 11, 2014 :cool: yep, that's the last part of the chain :) Link to comment Share on other sites More sharing options...
Paul Henty Posted January 11, 2014 Report Share Posted January 11, 2014 Here's the fix. Let me know how it goes. Two zips: one targets the .NET 2 framework, the other .NET 4 Client Profile. EDIT: Bugs in this upload. See good attachments further down. Paul Link to comment Share on other sites More sharing options...
Garfield_X Posted January 11, 2014 Author Report Share Posted January 11, 2014 Thank you Paul I just tested it, but it seems that the values are all zero, although traffictoolbox shows an assigned parking. As Pete said he reads all in what he did for FSX, then it must be P3D that does not set the data correct for FSUIPC? Peter Link to comment Share on other sites More sharing options...
Paul Henty Posted January 11, 2014 Report Share Posted January 11, 2014 Can you just do two quick tests for me? When you application is running can you please test the values of: FSUIPCConnection.FlightSimVersionConnected to make sure it's coming back as 'Prepar3d'. FSUIPCConnection.DLLVersion to make sure it's 2.6.5124. (This will show what dll was actually loaded, rather than checking the version number on the disk). Thanks, Paul Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 11, 2014 Report Share Posted January 11, 2014 Also try using TrafficLook, which is the test program I made for the FSUIPC AI traiffic data readouts. Pete Link to comment Share on other sites More sharing options...
Garfield_X Posted January 12, 2014 Author Report Share Posted January 12, 2014 My apologize. Never do a quick test when you are tired. (had copied the new DLL in the wrong folder :oops: ) After a good sleep, i saw what i did wrong yesterday evening, and all works as aspected. thank you. Also never test it on a busy airport like EHAM where all slots for ground traffic are full. When an aircraft had landed, it disappeared of the ground list (there where more then 96 AC on the ground) until a certain distance (i think) and the become visible in the list again. Link to comment Share on other sites More sharing options...
Garfield_X Posted January 12, 2014 Author Report Share Posted January 12, 2014 Hi Paul I came a cross an issues that was not present in the 2.4 version. When the following line is present, the FS sccreen starts 'jumping'. (tested with FS9) private Offset<short> slewMode = new Offset<short>(0x05DC, true); // Offset for moving the plane When trying the slew command FS continue to refresh the scenery. Switching to the 2,4 version everything works fine (i'm using the .NET 4 framework version) edit: also your C# test program with produces the same result with this new version. Peter Link to comment Share on other sites More sharing options...
Paul Henty Posted January 13, 2014 Report Share Posted January 13, 2014 Sorry about that. There was a bug with the write only offsets. Fix attached. Paul FSUIPCClient2.6_NET2.zip FSUIPCClient2.6_NET4.zip Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now