dragonflightdesign

I believe the airports may be available on fsim.net. I'm afraid I can't help with the engines as I wasn't involved with the MSFS2020 version.

Hello Doug Thanks for confirming that I had at least correctly identified the source of the problem and for providing two possible solutions. -Dai

Well, maybe it isn't such an odd problem - ! :smile: My simconnect gauge works perfectly in both windowed and fullscreen mode, as long as FSX stays in either windowed or fullscreen mode. However, if I resize the FSX window, around thirty seconds later FSX crashes with either a BEX or an appcrash. Commenting out the simconnect gauge stops the crash, so the source is pretty obvious. I think I might have a problem with conflicting calls as during the window resize process PANEL_SERVICE_CONNECT is called before PANEL_SERVICE_DISCONNECT. Can anyone confirm that this might be the source of the problem? If so, is there a way of detecting a window resize call? While writing this, I've considered putting the simconnect gauge in an invisible window which is launched by the main panel as the invisible window would never be resized. Would that help? I don't have time to try it ATM, but I will tomorrow.

I'm definately head-scratching. As a test I set up a read/write in XML instead using execute_calculator_code but got the same result. Oh well, I'll keep poking at it. You're right - I'm not over-happy in just ignoring it either!

It's FSX and it still fails without the mask. I've checked that I'm not doing something stupid like turning them off elsewhere but no. It's not an absolute that I use the FSX default generators - I just want to know if they're active and producing voltage - so it's just as easy to create my own (almost! :smile: ). If you've no other suggestions then I'll take this route; I appreciate your help, always.

Hello Ed That was quick! The mask was just something I tried. Yes, the engines are running: the intro line to that section of code (which I should have left in) is: if (e2n2.var_value.n>8700) { This always equates to true after engine start. -Dai

Hello Ed [electrical] max_battery_voltage = 24.0 generator_alternator_voltage = 30.0 max_generator_alternator_amps = 400.0 engine_generator_map= 1,1,1 MODULE_VAR default_gen2_active = {GENERAL_ENGINE2_GENERATOR_ACTIVE}; MODULE_VAR default_gen2_switch = {GENERAL_ENGINE2_GENERATOR_SWITCH}; ----------------- lookup_var(&default_gen2_active); // lookup_var(&default_gen2_switch); // if (!default_gen2_active.var_value.b ) // if (!default_gen2_switch.var_value.b ) // if (!default_gen2_switch.var_value.n ) if (!default_gen2_active.var_value.n) { // trigger_key_event(KEY_TOGGLE_MASTER_ALTERNATOR, 0); trigger_key_event(KEY_TOGGLE_ALTERNATOR2, 0); // send_key_event(KEY_TOGGLE_ALTERNATOR2, 0); } I think that about sums up all of my tries. Running in debug mode shows that neither _switch nor _active ever changes from zero/false. Do you need any other info? -Dai

i.e. I can't start them! :smile: The aircraft.cfg file contains an engine_generator_map line with a genny for each engine and I've tried trigger_key_event(KEY_TOGGLE_MASTER_ALTERNATOR, 0); and trigger_key_event(KEY_TOGGLE_ALTERNATORx, 0); but they don't seem to want to play. Is there something missing from the .air file, for example?

This should give you a head start on C++ gauges: http://library.avsim.net/search.php?SearchTerm=sd2gau35.zip&CatID=root&Go=Search Doesn't deal with GDI+ though. Maybe one day if we get lucky :smile:

Some more minor changes and a new section on using SimConnect as a gauge - thanks to WarpD and Doug Dowson for the help. NEW: Some corrections and updates to the new section on using SimConnect as a gauge.

Hi Bill Would you like to shoot the last one and pin this one please? Thank you. :smile: -Dai

Some more minor changes and a new section on using SimConnect as a gauge - thanks to WarpD and Doug Dowson for the help.

Hi Doug It was the fuel dump gauge. I didn't push the investigation too far on that one; all I saw was simconnect connecting to it and then immediately disconnecting. I just assumed it was part of the same problem. However, I think you may have saved me some time (I'll find out soon enough!). I'm going to rebuild my gauge using VS2010 with the /MTd parameter. [Edit] Well, that was it :Whew:- VS2013 was causing the trouble but I have no idea why. I just built the gauge in VS2010 and it worked first time, then upgraded the project to VS2013 and it still worked. Over time I have also upgraded a major project from VS2008 through VS2010 to VS2013 and it hasn't given any trouble. I can only assume because the .vcxproj file contained the 'correct' information. Lesson learned. -Dai

Thanks Ed - time to nuke FSX. If it loads and runs for you then there has to be something fundamentaly wrong with my setup. One of Doug Dowson's gauges won't load either, but I'm sure it used to. I'll get back in a few days when I've had time to press the big red button.

That might have been part of it but not all of it :mad: . I finally got round to attaching procmon to the process and found that the gauge is being loaded and then immediately unloaded. One step forward (I think....). I'll keep working on it.

Well, this is a headbanger and no mistake. I threw all the code away, reduced the bitmaps to 8-bit and started again. I added a separate bitmap for the static background (a bright red rectangle) and as suggested, used ICON_SWITCH_STEP_TO. FSX still requested to trust the gauge but again, nothing showed up on screen. Just so I could attach the debugger, I added this to the gauge callback: MODULE_VAR tick18 = { TICK18 }; //------------------- case PANEL_SERVICE_PRE_UPDATE: lookup_var(&tick18); break; The breakpoint (lookup_var) is never hit, suggesting that the gauge is actually not loading correctly. Figuring that it might be something in the compiler settings I ripped everything out from an existing working project and used the .cpp, .h and .rc files you have. Same result...

I would have thought that if ICON_SWITCH_STEP_TO was the problem, the static background bitmap (SELECTOR_OFF) would have shown up anyway. I'll give it a try in the morning and report back :smile: Oh - and I'll revert the bitmaps to 8-bit where they started. Going to 24-bit was just part of the testing (or fishing around, as it would be better stated).

No, that's me trying to cut the code down to as small as possible for the archive. Try this: https://www.dropbox.com/s/6siidcp9nidk17u/SelectorSimconnect.rar?dl=0 Now a VS2013 project. SELECTOR_OFF (and it's siblings) should be in the sdk.h file?

Hello Ed Thank you :smile: Dropbox link here: https://www.dropbox.com/s/eegyc6iwsgu6k1l/SelectorNoSimconnect.rar?dl=0 If you'd be kind enough to keep your comments public in this thread, it may help anyone who commits the same mistake. The project is currently at VS2005 because I had wondered if creating it in VS2013 was part of the problem. Any version of VS will do as I have access to all of them as part of my job. -Dai

You'd have thought after years of creating gauges I'd know the answer to this one, but some seven-eight hours of frustration later... I have a really simple standalone gauge that has seven sequential bitmaps in it, illustrating a selector switch. The gauge does nothing except rotate the switch as it's for a new section in sd2gau on using SimConnect as a gauge. Only. it. just. will. not. show. up. on. screen. Would someone be willing to make me feel really stupid and take a look at the code please? :smile:

Thanks Ed.... I think

I'm sure Bill will tell me that there's a far better way of doing this but... :smile: If you copy and paste the html code below and save it as <filename>.html it will create a webpage with the SimConnect exceptions set up as hyperlinks to the error explanation. I got fed-up with continually trying to find the information in both the FSX and P3D SDK documentation, so I turned it into a webpage. No nasty Javascript or CSS, just simple, pure HTML 4.0. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML> <HEAD> <TITLE>SimConnect Exceptions</TITLE> </HEAD> <tr><td><A NAME = "top"><h3>SIMCONNECT_EXCEPTION</h3></td></tr> <p>The SIMCONNECT_EXCEPTION enumeration type is used with the SIMCONNECT_RECV_EXCEPTION structure to return information on an error that has occurred.</p> <p>enum SIMCONNECT_EXCEPTION{ <table> <TR><TD WIDTH=32></TD><TD><A HREF = "#0">SIMCONNECT_EXCEPTION_NONE = 0,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#1">SIMCONNECT_EXCEPTION_ERROR = 1,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#2">SIMCONNECT_EXCEPTION_SIZE_MISMATCH = 2,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#3">SIMCONNECT_EXCEPTION_UNRECOGNIZED_ID = 3,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#4">SIMCONNECT_EXCEPTION_UNOPENED = 4,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#5">SIMCONNECT_EXCEPTION_VERSION_MISMATCH = 5,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#6">SIMCONNECT_EXCEPTION_TOO_MANY_GROUPS = 6,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#7">SIMCONNECT_EXCEPTION_NAME_UNRECOGNIZED = 7,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#8">SIMCONNECT_EXCEPTION_TOO_MANY_EVENT_NAMES = 8,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#9">SIMCONNECT_EXCEPTION_EVENT_ID_DUPLICATE = 9,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#10">SIMCONNECT_EXCEPTION_TOO_MANY_MAPS = 10,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#11">SIMCONNECT_EXCEPTION_TOO_MANY_OBJECTS = 11,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#12">SIMCONNECT_EXCEPTION_TOO_MANY_REQUESTS = 12,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#13">SIMCONNECT_EXCEPTION_WEATHER_INVALID_PORT = 13,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#14">SIMCONNECT_EXCEPTION_WEATHER_INVALID_METAR = 14,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#15">SIMCONNECT_EXCEPTION_WEATHER_UNABLE_TO_GET_OBSERVATION = 15,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#16">SIMCONNECT_EXCEPTION_WEATHER_UNABLE_TO_CREATE_STATION = 16,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#17">SIMCONNECT_EXCEPTION_WEATHER_UNABLE_TO_REMOVE_STATION = 17,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#18">SIMCONNECT_EXCEPTION_INVALID_DATA_TYPE = 18,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#19">SIMCONNECT_EXCEPTION_INVALID_DATA_SIZE = 19,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#20">SIMCONNECT_EXCEPTION_DATA_ERROR = 20,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#21">SIMCONNECT_EXCEPTION_INVALID_ARRAY = 21,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#22">SIMCONNECT_EXCEPTION_CREATE_OBJECT_FAILED = 22,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#23">SIMCONNECT_EXCEPTION_LOAD_FLIGHTPLAN_FAILED = 23,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#24">SIMCONNECT_EXCEPTION_OPERATION_INVALID_FOR_OJBECT_TYPE = 24,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#25">SIMCONNECT_EXCEPTION_ILLEGAL_OPERATION = 25,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#26">SIMCONNECT_EXCEPTION_ALREADY_SUBSCRIBED = 26,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#27">SIMCONNECT_EXCEPTION_INVALID_ENUM = 27,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#28">SIMCONNECT_EXCEPTION_DEFINITION_ERROR = 28,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#29">SIMCONNECT_EXCEPTION_DUPLICATE_ID = 29,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#30">SIMCONNECT_EXCEPTION_DATUM_ID = 30,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#31">SIMCONNECT_EXCEPTION_OUT_OF_BOUNDS = 31,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#32">SIMCONNECT_EXCEPTION_ALREADY_CREATED = 32,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#33">SIMCONNECT_EXCEPTION_OBJECT_OUTSIDE_REALITY_BUBBLE = 33,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#34">SIMCONNECT_EXCEPTION_OBJECT_CONTAINER = 34,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#35">SIMCONNECT_EXCEPTION_OBJECT_AI = 35,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#36">SIMCONNECT_EXCEPTION_OBJECT_ATC = 36,</A></TD></TR> <TR><TD WIDTH=32></TD><TD><A HREF = "#37">SIMCONNECT_EXCEPTION_OBJECT_SCHEDULE = 37,</A></TD></TR> </table> };</p> <h4>General Errors</h4> <table> <tr><td><A NAME = "0">SIMCONNECT_EXCEPTION_NONE</A></td></tr> <tr><td><font color="gray">Specifies that there has not been an error. This value is not currently used.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "1">SIMCONNECT_EXCEPTION_ERROR</A></td></tr> <tr><td><font color="gray">An unspecific error has occurred. This can be from incorrect flag settings, null or incorrect parameters, the need to have at least one up or down event with an input event, failed calls from the SimConnect server to the operating system, among other reasons.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "2">SIMCONNECT_EXCEPTION_SIZE_MISMATCH</A></td></tr> <tr><td><font color="gray">Specifies the size of the data provided does not match the size required. This typically occurs when the wrong string length, fixed or variable, is involved. </td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "3">SIMCONNECT_EXCEPTION_UNRECOGNIZED_ID</A></td></tr> <tr><td><font color="gray">Specifies that the client event, request ID, data definition ID, or object ID was not recognized. </td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "4">SIMCONNECT_EXCEPTION_UNOPENED</A></td></tr> <tr><td><font color="gray">Specifies that communication with the SimConnect server has not been opened. This error is not currently used.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "5">SIMCONNECT_EXCEPTION_VERSION_MISMATCH</A></td></tr> <tr><td><font color="gray">Specifies a versioning error has occurred. Typically this will occur when a client built on a newer version of the SimConnect client dll attempts to work with an older version of the SimConnect server. </td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "6">SIMCONNECT_EXCEPTION_TOO_MANY_GROUPS</A></td></tr> <tr><td><font color="gray">Specifies that the maximum number of groups allowed has been reached. The maximum is 20. </td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "7">SIMCONNECT_EXCEPTION_NAME_UNRECOGNIZED</A></td></tr> <tr><td><font color="gray">Specifies that the simulation event name (such as "brakes") is not recognized. </td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "8">SIMCONNECT_EXCEPTION_TOO_MANY_EVENT_NAMES</A></td></tr> <tr><td><font color="gray">Specifies that the maximum number of event names allowed has been reached. The maximum is 1000.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "9">SIMCONNECT_EXCEPTION_EVENT_ID_DUPLICATE</A></td></tr> <tr><td><font color="gray">Specifies that the event ID has been used already. This can occur with calls to SimConnect_MapClientEventToSimEvent, or SimConnect_SubscribeToSystemEvent. <td></td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "10">SIMCONNECT_EXCEPTION_TOO_MANY_MAPS</A></td></tr> <tr><td><font color="gray">Specifies that the maximum number of mappings allowed has been reached. The maximum is 20.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "11">SIMCONNECT_EXCEPTION_TOO_MANY_OBJECTS</A></td></tr> <tr><td><font color="gray">Specifies that the maximum number of objects allowed has been reached. The maximum is 1000.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "12">SIMCONNECT_EXCEPTION_TOO_MANY_REQUESTS</A></td></tr> <tr><td><font color="gray">Specifies that the maximum number of requests allowed has been reached. The maximum is 1000.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "18">SIMCONNECT_EXCEPTION_INVALID_DATA_TYPE</A></td></tr> <tr><td><font color="gray">Specifies that the data type requested does not apply to the type of data requested. Typically this occurs with a fixed length string of the wrong length.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "19">SIMCONNECT_EXCEPTION_INVALID_DATA_SIZE</A></td></tr> <tr><td><font color="gray">Specifies that the size of the data provided is not what is expected. This can occur when the size of a structure provided does not match the size given, or a null string entry is made for a menu or sub-menu entry text, or data with a size of zero is added to a data definition. It can also occur with an invalid request to SimConnect_CreateClientData.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "20">SIMCONNECT_EXCEPTION_DATA_ERROR</A></td></tr> <tr><td><font color="gray">Specifies a generic data error. This error is used by the SimConnect_WeatherCreateThermal function to report incorrect parameters, such as negative radii or values greater than the maximum allowed. It is also used by the SimConnect_FlightSave and SimConnect_FlightLoad functions to report incorrect file types. It is also used by other functions to report that flags or reserved parameters have not been set to zero.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "21">SIMCONNECT_EXCEPTION_INVALID_ARRAY</A></td></tr> <tr><td><font color="gray">Specifies an invalid array has been sent to the SimConnect_SetDataOnSimObject function.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "26">SIMCONNECT_EXCEPTION_ALREADY_SUBSCRIBED</A></td></tr> <tr><td><font color="gray">Specifies that the client has already subscribed to that event.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "27">SIMCONNECT_EXCEPTION_INVALID_ENUM</A></td></tr> <tr><td><font color="gray">Specifies that the member of the enumeration provided was not valid. Currently this is only used if an unknown type is provided to SimConnect_RequestDataOnSimObjectType.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "28">SIMCONNECT_EXCEPTION_DEFINITION_ERROR</A></td></tr> <tr><td><font color="gray">Specifies that there is a problem with a data definition. Currently this is only used if a variable length definition is sent with SimConnect_RequestDataOnSimObject.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "29">SIMCONNECT_EXCEPTION_DUPLICATE_ID</A></td></tr> <tr><td><font color="gray">Specifies that the ID has already been used. This can occur with menu IDs, or with the IDs provided to SimConnect_AddToDataDefinition, SimConnect_AddClientEventToNotificationGroup or SimConnect_MapClientDataNameToID.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "30">SIMCONNECT_EXCEPTION_DATUM_ID</A></td></tr> <tr><td><font color="gray">Specifies that the datum ID is not recognized. This currently occurs with a call to the SimConnect_SetDataOnSimObject function.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "31">SIMCONNECT_EXCEPTION_OUT_OF_BOUNDS</A></td></tr> <tr><td><font color="gray">Specifies that the radius given in the SimConnect_RequestDataOnSimObjectType was outside the acceptable range, or with an invalid request to SimConnect_CreateClientData.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "32">SIMCONNECT_EXCEPTION_ALREADY_CREATED</A></td></tr> <tr><td><font color="gray">Specifies that a client data area with the name requested by a call to SimConnect_MapClientDataNameToID has already been created by another addon. Try again with a different name.</td> </table> <A HREF = "#top">Top</a><br><br> <h4>Weather System Errors</h4> <table> <tr><td><A NAME = "13">SIMCONNECT_EXCEPTION_WEATHER_INVALID_PORT</A></td></tr> <tr><td><font color="gray">Specifies an invalid port number was requested.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "14">SIMCONNECT_EXCEPTION_WEATHER_INVALID_METAR</A></td></tr> <tr><td><font color="gray">Specifies that the metar data supplied did not match the required format. See the section Metar Data Format for details on the format required.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "15">SIMCONNECT_EXCEPTION_WEATHER_UNABLE_TO_GET_OBSERVATION</A></td></tr> <tr><td><font color="gray">Specifies that the weather observation requested was not available. Refer to the remarks section for SimConnect_WeatherRequestObservationAtStation for some notes on this exception.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "16">SIMCONNECT_EXCEPTION_WEATHER_UNABLE_TO_CREATE_STATION</A></td></tr> <tr><td><font color="gray">Specifies that the weather station could not be created.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "17">SIMCONNECT_EXCEPTION_WEATHER_UNABLE_TO_REMOVE_STATION</A></td></tr> <tr><td><font color="gray">Specifies that the weather station could not be removed.</td> </table> <A HREF = "#top">Top</a><br><br> <h4>AI errors</h4> <table> <tr><td><A NAME = "22">SIMCONNECT_EXCEPTION_CREATE_OBJECT_FAILED</A></td></tr> <tr><td><font color="gray">Specifies that the attempt to create an AI object failed.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "23">SIMCONNECT_EXCEPTION_LOAD_FLIGHTPLAN_FAILED</A></td></tr> <tr><td><font color="gray">Specifies that the specified flight plan could not be found, or did not load correctly.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "24">SIMCONNECT_EXCEPTION_OPERATION_INVALID_FOR_OBJECT_TYPE</A></td></tr> <tr><td><font color="gray">Specifies that the operation requested does not apply to the object type, for example trying to set a flight plan on an object that is not an aircraft will result in this error.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "25">SIMCONNECT_EXCEPTION_ILLEGAL_OPERATION</A></td></tr> <tr><td><font color="gray">Specifies that the AI operation requested cannot be completed, such as requesting that an object be removed when the client did not create that object. This error also applies to the Weather system.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "33">SIMCONNECT_EXCEPTION_OBJECT_OUTSIDE_REALITY_BUBBLE</A></td></tr> <tr><td><font color="gray">Specifies that an attempt to create an ATC controlled AI object failed because the location of the object is outside the reality bubble.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "34">SIMCONNECT_EXCEPTION_OBJECT_CONTAINER</A></td></tr> <tr><td><font color="gray">Specifies that an attempt to create an AI object failed because of an error with the container system for the object.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "35">SIMCONNECT_EXCEPTION_OBJECT_AI</A></td></tr> <tr><td><font color="gray">Specifies that an attempt to create an AI object failed because of an error with the AI system for the object.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "36">SIMCONNECT_EXCEPTION_OBJECT_ATC</A></td></tr> <tr><td><font color="gray">Specifies that an attempt to create an AI object failed because of an error with the ATC system for the object.</td> </table> <A HREF = "#top">Top</a><br><br> <table> <tr><td><A NAME = "37">SIMCONNECT_EXCEPTION_OBJECT_SCHEDULE</A></td></tr> <tr><td><font color="gray">Specifies that an attempt to create an AI object failed because of a scheduling problem.</td> </table> <A HREF = "#top">Top</a><br><br>

AT LAST!!! That has been one steep learning curve - ! It was like someone turned a (dim) light on sometime over the last two days and I'm now starting to understand the SDK. Thank you both very much for your help

Thanks Doug - I was starting to think I was being particularly stupid. If I don't get it tonight, it will have to wait until I get back from Florida in ten days' time.

That's what I was doing when I found that I could successfully read FlightSaved - the above code was my last despairing try before I went to bed last night. Now I'm seriously beginning to wonder if FlightLoaded actually works.