The premium aircraft cfg files are locked in a file archive in order to prevent them from being distributed to standard version users. It’s a shame that they could not find a way to have them moddable while restricting the use to those who have bought the right deluxe/premium version.
Unless someone knows how to get the files from the archive and then re-archive them, I don’t see this happening.
Fortunately the panel.xml allows for state machines, so you can have a state and conditions that define the transition to another state.
So I now implemented the BUSES TIED annunciation exactly as it’s required and made a pull request with that change
All aircraft included in the standard edition can be modded this way as it is done here with the G36.
Aircraft that are available only with the deluxe or premium deluxe versions cannot be easily modded since they are encrypted.
So everyone can use the G36 mod discussed here since the G36 is included in standard edition - it doesn’t matter which version you have.
Check the charts in section 5 of the POH shown above your post, but general rule of thumb for cruise is 25"MP/2500RPM and about 17GPH at about 170KTAS, or 23"MP/2300RPM and about 15GPH at around 160KTAS.
Fair point, on the right hand screen, on the top left side you’ll have 2 circular dials. The first one is the engine Manifold Pressure (MP), and the second is engine RPM. For cruise flight you will normally setup the engine controls to either show 23 on the first gauge and 2300 on the second, or 25 on the first and 2500 on the second.
The fuel flow gauge is just underneath those dials, with the number 30 at the far end. Each tick mark represents 2GPH, once you have your MP and RPM set, slowly reduce your mixture until the fuel flow meter shows between the 7th and 8th bars and you’re good to go.
Stupid question time: I installed the V0.2 patch in the community folder and it worked great, thanks kindly. The V0.2 patch folder was titled “Bonanza-G36-performance-fixes” while the V0.3 folder is titled “Bonanza-G36-improvement-project”. So when I place the new V0.3 folder in the community folder do I still have to keep the previous “performance fixes” folder there as well or should I delete that?
Thanks to the developers, the g36 now is more enjoyable to fly, once again I am disconcerted about the lack of attention to the flight dynamics by Asobo, What was the alpha and beta tests for?
I think it’s obvious that none of the aircraft were released in a “done” state.
In the source files you basically can see everywhere traces of unfinished details.
Asobo will have to prove their intentions here by improving the default aircraft no matter if community is working on mods.
I had a look at the checklist files (fun fact, the comments there are partially french ), they are quite a lot of work to implement in a way that also the highlighting and copilot would work.
I think I’ll work with paper checklists at this time which is anyway more comfortable than that popup window blocking the view.
I’ve made a start using the POH to add the checklist items (interactive) for pre-flight. I’ve so far added each of the normal checklist sections, just got to fill them out.
Once I’ve done the pre-flight i’ll push over to @FrettFS’s Git repository. And we can test / see how user friendly they are.