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.