Severity:High
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)
Marketplace package name: if applicable
Context: What package? When editing or mounted from Community? In main menu or in flight? etc…
Similar MSFS 2020 issue: insert url here if applicable
Bug description: There seems to be a lot of Hydraulic System docs missing, while struggling to make a functional Hydraulics system, I’ve looked at the 737 one and noticed there are a few parameters that aren’t documented:
Actuator type “Flaps” has an index function? What does this do?
There is a “ThrustReverser” actuator type.
The “Trigger” functions are undocumented
In the .FLT file sections, the 737 seems to have a starting pressure for everything, Documentation for this is missing
Repro steps:
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content
Ok I think it was removed in the latest version of SU5 documentation. Index was used before we introduced the use of Name as reference, especially for ModularSimObject context. Name being introduced shortly after, Index is essentially deprecated and will only appear in some aircraft designed at that time.
So just ignore it and always use Name instead.
This is not particularly tied to flaps. This is just a general index for the actuator, just like we had for the Fuel System before name indexing was introduced Modular Fuel System Information
In fact, I’m pretty sure these can be removed without consequences in the 737 systems.cfg without consequences.
What determines what actuator will be used for which flaps can be found in interior_Behavior_Config_Prog.xml, in the Get_Procedure_Flaps_Manager_Parameters function for example:
You’ll notice we use the Name for indexing, with the :'Flaps'_n suffix.
Chances are the first implementation was done before name indexing existed, and we originally used A:HYDRAULIC ACTUATOR ACTIVE:1 and A:HYDRAULIC ACTUATOR ACTIVE:2
In that case, how would the sim know what flap system is tied to what actuator? So when the extend flaps event is sent, it doesn’t extend a flap that doesn’t have a working actuator?
Is the set by the system_type_index in the flaps section? In that case, the Flaps section is missing documentation.
Or is the procedure needed in order to make the Flap movement actually connected to the actuator condition? I assumed it was baked in.
Say you have
Flap.1 = trailing edge system
Flap.2 = Leading edge
and you have
Actuator.10 #Name:Front#type:Flaps
Actuator.11 #Name:Back#type:Flaps
how does it know the second actuator should be controlling the first flaps system.
If a procedure is needed, then the documentation concerning that is also missing
No, this one is limited to the electrical system as documented.
For hydraulic flaps, it seems to be linked using the FLAPS.N section index to match the actuator.
So FLAPS.0 will be linked to your first defined flaps actuator, FLAPS.1 to the second, etc…
This is flawed in both cases anyway, as order is not necessarily preserved in a ModularSimObject context.
I think we’re missing an explicit parameter to provide the name of whatever circuit/actuator is used.
