story

I was using 1.0 version of the library earlier and you might be right that this is the problem. I'll check it out. It might have went away... I discovered a bug in the latest version (1.1) of FSUIPC_Write (the overload that takes a byte array as parameter). I don't think it could ever have worked... Your code: int idx; for ( idx = (Token + 4) ; i < (Token + dwSize + 3); i++) { IPC[idx] = param[idx]; //xfer byte array to IPC managed FifO buffer } I've fixed it so it works: int idx; int startidx = Token + 4; for ( idx = (Token + 4) ; idx < (Token + dwSize + 3); idx++) { IPC[idx] = param[idx - startidx]; //xfer byte array to IPC managed FifO buffer }

Hi! I'm currently rewriting an old application in C#.Net and I'm having some difficulties with FSUIPC (using Scott McCrorys 1.1 library). Sometimes I get odd responses from FSUIPC when trying to retrieve heading or altitude (heading 360 or altitude 0). These almost always happens when I do a lot of reads after one another. It gets quite annoying when cruising at 39000 ft and suddenly FSUIPC says I'm at the ground... I would like to hear if anyone else have had these problems or have a solution to them? Regards Rickard Nord