John Dowson

No - these are distinct simvars. The GENERAL ENGINE STARTER ACTIVE simvar is a read-only boolean that indicates if the indexed engine starter is active. If you want to read the value of this simvar, then you can add this to a spare (free for general use) offset. You can do this using the myOffsets.txt file - see the Advanced User guide for details. Not sure what this means...

License sent.

The only fix for this issue is to install the combined (2015, 2017, 2019, 2022) VC++ redistributable package, as stated.

I am currently on holiday and will reply when I am back, on Wednesday. However this: No - if you look at the presets: you should see that it should be ipc.writeLvar(“FSUIPC_C510_Ignition_1", 2) to turn the ignition on ipc.writeLvar(“FSUIPC_C510_Ignition_1", 1)vto turn the ignition off Otherwise, if you have defined the presets, you can use ipc.execPreset instead.

Trial licenses sent. Please be aware that I am now on holiday. Any more requests for trial licenses will be processed next week (Wednesday 18th October) John

Actually both of these methods do work - they just don't animate the switch. They do set the A-var (A:TURB ENG IGNITION SWITCH EX1) correctly. The animation of the switch is controlled by a B-var, and you currently cannot access B-vars either via standard controls or calculator code. There is a hack that you can use if you want to animate the switch - basically you edit the code and define an lvar that controls the b-var. To do this for ignition switch 1 (switch 2 will be the same, just change the numbers), you need to add the following code to the C510_interior.xml file (under Community\cockspur-aircraft-c510\SimObjects\Airplanes\cockspur-aircraft-C510\model). Open this file in an editor (e.g. Notepad++), scroll down to line 351 (comment line) and then paste the following text below the comment: <Component ID="FSUIPC_External_Control"> <UseTemplate Name="ASOBO_GT_Update"> <UPDATE_CODE> (L:FSUIPC_C510_Ignition_1, Number) s0 (A:TURB ENG IGNITION SWITCH EX1:1, Number) s1 l0 0 &gt; if{ l1 l0 != if{ 0 (&gt;L:FSUIPC_C510_Ignition_1) 1 (&gt;B:ENGINE_Ignition_1_Toggle) } } </UPDATE_CODE> <FREQUENCY>1</FREQUENCY> </UseTemplate> </Component> Next, add the following presets to your myevents.txt file (- in your FSUIPC7 installation folder - create this file if it doesn't exist): //Cockspur/Mustang C510 Mustang_C510_Ignition1_on#2 (>L:FSUIPC_C510_Ignition_1) Mustang_C510_Ignition1_norm#1 (>L:FSUIPC_C510_Ignition_1) You can then assign directly to those presets. If you would prefer a single toggle preset, use the following code: <Component ID="FSUIPC_External_Control"> <UseTemplate Name="ASOBO_GT_Update"> <UPDATE_CODE> (L:FSUIPC_C510_Ignition_1, Number) s0 l0 0 &gt; if{ 0 (&gt;L:FSUIPC_C510_Ignition_1) 1 (&gt;B:ENGINE_Ignition_1_Toggle) } </UPDATE_CODE> <FREQUENCY>1</FREQUENCY> </UseTemplate> </Component> and preset //Cockspur/Mustang C510 Mustang_C510_Ignition1_Toggle#1 (>L:FSUIPC_C510_Ignition_1) Ignition switch 2 is similar, with code: <Component ID="FSUIPC_External_Control2"> <UseTemplate Name="ASOBO_GT_Update"> <UPDATE_CODE> (L:FSUIPC_C510_Ignition_2, Number) s0 (A:TURB ENG IGNITION SWITCH EX1:2, Number) s1 l0 0 &gt; if{ l1 l0 != if{ 0 (&gt;L:FSUIPC_C510_Ignition_2) 1 (&gt;B:ENGINE_Ignition_2_Toggle) } } </UPDATE_CODE> <FREQUENCY>1</FREQUENCY> </UseTemplate> </Component> and presets: //Cockspur/Mustang C510 Mustang_C510_Ignition1_on#2 (>L:FSUIPC_C510_Ignition_1) Mustang_C510_Ignition1_norm#1 (>L:FSUIPC_C510_Ignition_1) Mustang_C510_Ignition2_on#2 (>L:FSUIPC_C510_Ignition_2) Mustang_C510_Ignition2_norm#1 (>L:FSUIPC_C510_Ignition_2) John

Sounds reasonably, but I don't think this will be that easy to implement. I will make a note to look into at some point, but not sure when I will have time. I already have quite a long list of new functionality to implement (mainly for FSUIPC7 / MSFS) and have very little time for this as support is still taking up most of my time. Regards, John

Not sure how much, if any, progress there is...! As I say, I can load that dll in WideClient but it crashes soon after, and I don't know why. I would like to see if you see the same though...and if that works in FSUIPC4 for you. That's ok - I don't need to see this. I still don't understand why your dll loads ok in FSUIP4 but not in WideClient (they use the same lua compiler). I will see if I can determine why, but still not sure how to go about this at the moment...

Btw, it seems that WideClient is crashing when using that luacom.dll I attached, shortly after or when the script loading the luacom.dll library is terminated. I also tried switching back to your version of the luacom.dll and now I see the same as you - it loads ok in FSUIPC4 but not in WideClient. I would be interested to see if you can use that luacom.dll, and also why this is different than the one you provided - maybe it is an older version? Anyway, please try that version and let me know how it goes, both with WideClient and FSUIPC4. This library is for using Microsoft's Component Object Model (COM) interface, not for handling COM ports, which is what the FSUIPC COM library is used for. Thee two COM libraries are therefore very different...! It maybe that using this library also requires that lua is also installed in Windows, which is why it didn't work for me before I installed it. I still don't understand why this is different in WidecCient though...

I am getting the same error you initially reported ("The specified module could not be found.") in both FSX and WideClient: How did you get the dll loaded in FSUIPC4? Did you write the lua program that uses the luacom.dll, or was that supplied to you? Could you attach that as well please (if allowed). There really is no difference in WideClient’s Lua facilities to those in FSUIPC (except where explicitly stated of course), so I’ve no idea why the 32-bit LuaCom.dll gives errors there but not with FSUIPC4. Do you know the lua version that the luacom.dll was built with/for? There seems to be a 64-bit fork of the luacom project, so I could try building () that. However, I would like to get the 32-bit version loaded by FSUIPC4 first.... Later: Some success....I installed the latest lua-for-windows package and took the luacom.dll from there, and used this to replace the one you provided. This now loads ok in both FSUIPC4 and in WideClient, so it looks to be a problem with that dll. Are you sure it is the same one that you are using with FSUIPC4? I have attached the one I am using (it is slightly larger than the one you provided, 168KB vs 164KB) - it is the one that comes with the 5.1.4 lua distribution: luacom.dll Can you please try with that version. Cheers, John

License sent. John

That is the best way to do it, otherwise you would have to clear/delete every profile-specific assignment via the UI. Once am aircraft has been assigned to a profile, the only way to remove it i by removing the aircraft name from the [Profile.xxxx] section. And if you want to remove the profile completely, you have to delete the [Profile.xxx] section together with all the other sections referencing that profile, e,g, [Axes.xxx], [Buttons.xxx], etc. Yes - they are comments that generated automatically. From the Advanced User guide: John

But that is for calibration WITH a reverse zone - the central 'Set' values are the idle position. Check for NRZ (top left of calibration panel) and they will disappear.

Not sure what you mean.... How are you assigning? Assign your throttle with Send direct to FSUIPC calibration using the Throttle1 and Throttle2 controls. Then go to the calibration. tab and calibrate with NRZ checked. If you then look at the out value sent, the minimum will be 0 at your calibrated idle position (usually around -16383). And if you have assigned your reverser button to Throttle Decr (on repeat), pressing and holding the button will activate the reversers. And the assignment to Throttle Cut on release will kill the reversers and go back to idle when you release the button.

For the engine starters, you can use the standard controls Toggle Starter1 and Toggle Starter2. The ignition switches in the VC use the TURBINE_IGNITION_SWITCH_SET1 and TURBINE_IGNITION_SWITCH_SET2 controls/events. However, assigning to these directly has no effect. I have also tried with a preset/calc code to send these events (e.g. '2 (>K:TURBINE_IGNITION_SWITCH_SET1)') but again these have no effect. So I'm sorry but I do not know how to control the ignition switches externally. You should ask either the aircraft provider or, probably better, ask about this on the MF discord channel - use the MSFS2020 channel. This is the general channel for asking on how to control buttons/switches etc from an external application. They may give you a way to do this using MobiFlight, but if it can be done in MF then it can be done in FSUIPC. Sorry I can't be of more help. Please update if you find a solution. I will also investigate further (i.e. take a look at the aircraft code/xml to see if that reveals anything) when I have more time... Quite a lot to do at the moment, and I am away from Wednesday afternoon until Tuesday (inclusive), back next Wednesday. Regards, John

Ok - but also when using a button for reverse thrust, make sure you also calibrate the axes with No Revere Zone (NRZ) checked.

You have assigned the throttle button to decrement (on repeat) while the button is held (R), and also to decrement again when the button is released (U). That is weird. You can delete the assignment sent on release (U), but, if this is the button that you are using to activate reversers, then you would normally assign the release to the throttle cut control. This then gives you reverse thrust while you gold the button and goes to idle when you release.

Hi Luke, can you try the attached version please, v7.3.25c. In this version, offset 0x0264 will hold the following values, or a combination thereof: 0 - No pause 1 - "full" Pause (sim + traffic + etc...), activated (and disabled) using Pause Set or Pause Toggle 2 - FSX Legacy Pause (not used anymore) - redundant 4 - Pause was activated using the "Active Pause" - only assignable in MSFS (not FSUIPC) 8 - Pause the player sim but traffic, multi, etc... will still run, activated using Pause On, disabled using Pause Off 16 - 'esc' pause So the sim can be in up to 4 distinct pause states at the same time. You can activate/disable all pause states when in another pause state, except for the esc pause state which blocks other pause states until deactivated. I have also updated the pause control offset 0x0262 - you can pause/unpause only two of the above pause states, by setting/clearing 1 and 8. So with this offset you can set/clear up to 2 distinct pause states. Let me know if you have any issues. Cheers, John FSUIPC7.exe

Ok, thanks for the update. I am rather busy at the moment, but when I have time I will try to reproduce with the delay parameter here and look into this to provide a fix. I will update you once I have investigated further. Cheers, John

You need to determine what holds this information. If there is a simulator variable available, check to see if this variable is held in an offset, and if not it can added. If no simvar is available, then you can check the available lvars, but you would have to do this for each aircraft. AC MAX PASSENGERS: I cannot see anything that holds this. However, it could maybe (roughly) calculated from the weights, e.g. ( (max gross weight - empty weight - fuel weight) / 220 lbs) (where 220 lbs is the industry standard for the weigth of one passenger + luggage) AC MTOW: could this be the MAX GROSS WEIGHT held in offset 0x1334? AC MAXFUEL: this depends on whether the aircraft uses the new fuelsystem or the legacy one (held in offset 0x07A8). For aircrft that use the legacy system, you can use the FUEL TOTAL CAPACITY simvar held in offset 0x1240. For aircraft that use the new fuelsystem it is more complicated. If you know the nymber if tanks, you can sum the indexed simvar FUELSYSTEM TANK CAPACITY. However, I am not sure how to determine the number of tanks available, s you may be better off summing the capacity simvars (e.g. FUEL TANK CENTER CAPACITY, FUEL TANK CENTER2 CAPACITY, FUEL TANK CENTER3 CAPACITY, FUEL TANK EXTERNAL1 CAPACITY, etc). See https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_Fuel_Variables.htm AC ZFW: this is again something you would have to calculate from the available weights AC TAS: that should be in offset 0x02B8 (AIRSPEED TRUE) AC MAX CRUISING ALT: not sure if this is available - I can only see a Design Cruise Altitude, i.e. optimal rather than max. See https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_FlightModel_Variables.htm. Sorry I can't be of more help. John

Then why not use the latest version of LINDA, v3.3.5? But I have seen the LINDA 3.2.6.111 is also available for download at the bottom of the following page if you need that version: https://www.avsim.com/forums/topic/573578-linda-335-p3dv5fsuipc6-compatible-5-jun-2022/ Ok. I can provide you with a courtesy / free license for FSUIPC6 if you require one - let me know. Regards, John

That should be possible but I cannot help with this.... However, some aircraft use protection and it may not be allowed. You should ask about this on the aircraft support (presuming there is one) or maybe on the Asobo forums. I will look at the start/ignition controls sometime next week. John

As i said, if you can attach the file I can take a look...next week sometime....

Sorry, I do have the C510. I can check the start/ignition, but not today - finishing for the day now. As for the G1000, maybe try the available presets. These work both for the default G1000 and the one from WT

Sorry, I see you are using the Cockspur Mustang C510 - unfortunately there don't seem to be any presets available for this aircraft, and as I don't own this aircraft if is difficult for me to advise. Maybe worth asking on the MF discord channel - they lead the community effort for discovering calculator code for presets.... John