Version: All
Frequency: Consistently
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: When setting up my helicopter engines I was carefully going through the documentation and removing those parameters that are jet specific and leaving the parameters with a value of zero, that the documentation tells me to keep. After that process I encountered a ctd every time I tried to load a flight with my helicopter. So started from zero and build my project after each removed parameter to find the issue. Turns out it is the n2 rpm. The documentation tells me to keep this jet specific parameter but to put it to 0 for helis. This part of the documentation should be corrected.
Looking at other devs helicopter projects I saw that they all use the parameter normally. The remaining question for me is what the n2 actually refers to in a helicopter in msfs24. Is it the 2nd stage compressor rpm or the engine drive shaft rpm that is often referred to as n2 as well? Looking at other projects it seems to be the drive shaft rpm. I was trying both the compressor rpm (30 000) and drive shaft rpm (6000) for my engine. Using the the compressor rpm both the governor and n2 protection were unable to contain the rpm, it was rising fastly towards infinity. Using the engine drive shaft rpm however, everything works as expected. I would like to hear from other devs if the drive shaft rpm is actually the correct n2 value for helis.
**Repro steps:**Set the n2 rpm for any helicopter engine to 0 as described in the docmentation and try to start a flight. CTD should occur.
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content