YankeeFan

Thanks again for the additional suggestions/tips. The strange thing is I've run my application in Debug mode where I can add breakpoint and check values at any line in my application, and I dont find any problems whats so ever. However, with over 100-200 users of my application their PC systems can be quite diff. including Flight Sim version 2000 to 2004, Windows OS 98/XP Home/XP Pro, FSUIPC versions from 2.9xxx to 3.202, even languages from English to Czech, so it has been a real challenge to say the least to try to troubleshoot. In my application whenever an error occurs it will write to an errlog.txt file, but when Windows jumps in and causes error messages it is a bit hard to trap those to include to the errlog.txt file. I am just waiting for the day where it will become obvious whats happing. Thanks again! John McCormack

Thank you Pete for your suggestions. I've taken a close look and am following the guidelines set forth in the Programmers Guide for FSUIPC for those two offsets, so I guess I'm at a lost for moment. I will keep digging at and try some diff. things to see if I can isolete the possible cause further. Thanks again for your suggestions and a fast reply!

Hi Pete, Does FSUIPC use ntdll.dll directly or indirectly when writing data to an offset or in any other way? The reason I ask is it appears ever since I started writing to offsets 32FA and 3380 to send informational messages from my program to FS so that it appears in the ATIS text box (white text on green background) on screen, alot of users of my application are experiencing an Windows error message at random times. Such as "Active AirSource has encountered a problem and needs to close. We are sorry for the inconvenience." It refers to module ntdll.dll at offset 0006112b. Which I am not using in my application, however FSUIPC is an intregal part of my application and was wondering if you are using it. Thanks for any assistance, John McCormack

Oh ok np, thanks Pete for clearing this up. I wasn't sure if my application was going nuts once again

Hi Pete, I noticed that FSUIPC v3.20 is showing as v3.153 at offset 3306, or has the FSUIPC version moved to a new offset value? Thanks! John McCormack

Pete, Just in case you weren't aware, the download available at http://www.schiratti.com/dowson.html is still showing as v3.08 and when I downloaded it and unzipped it, it was dates 9/19/2003.

Many thanks Pete, that makes alot more sense now! Also, thanks for sheading some light(no pun intended) on the new Cabin light switch as well.

Thanks for the information, will try going down that avenue and see where it leads.

Never mind on this post, that's exactly what it appears I needed to do is convert the decimal value returned from the offset to a binary string and read each byte from right to left to make the determination of ON/OFF.

I am having a bit of a hard time figuiring out how to determine exactly which light switch is on by simply reading the [0D0C] offset. According to the SDK the light switches are defined as follows; 0D0C 2 bytes Lights (FS2k/CFS2), a switch for each one: 0 Navigation 1 Beacon 2 Landing 3 Taxi 4 Strobes 5 Instruments 6 Recognition 7 Wing 8 Logo If somebody has some sample code written in VB that would be great. Basically I am trying to determine each of the possible light switches if ON or OFF. When testing and had all lights off except for NAV the value in [0D0C] = 33, when I used the "L" key to switch everything on the value was 1023. Does the value of the offset just need a conversion like Decimal to Binary? Thanks! John

So I take it that there is no way of telling through the use of FSUIPC what the autopilot settings/values are then?

Does anyone have any idea how and where the autopilot information is being stored for PSS aircraft. All my aircrafts I've tested all return correctly all the autopilot information (eg. Nav Hold, Alt Hold, Hdg Hold, including values for Alt, Hdg, Speed, etc.) except the PSS ones?? Thanks, John

Oh ok, thanks Pete

Hi Pete, Is there offsets in v3.04 that I may have overlooked that has been identified for just the aircraft manufacturer and aircraft model information (eg. Bombardier, Learjet 45) as apposed to the aircraft title at 3D00? 3D00 256 Name of the current aircraft (from the “title” parameter in the AIRCRAFT.CFG file). Valid for FS2K only. Thanks, John

Thanks I will use what works! This is my first week programming using FSUIPC, so I am stumbling a bit at the moment. But, hopefully I will be able to get use to it enough where I can proceed without havings so many elementary questions. Thanks again! John McCormack