I’d love to plan a fly-in for v5; once that’s out I say we take a Saturday afternoon to get together and revel in our work. 100% willing to take point on planning that
@Forest4a The issues you’re experiencing are telling me you don’t have the mod installed or are not using automixture with the mod. The AP issue is a known bug in the game as of now. As a personal workaround I set the AP to hold the current altitude I’m at. This also resets the problematic FD, will try simply recycling the FD today to see of that works for me as well.
A fly-in would be a ton of fun! I’m generally at my day job on Saturdays so you all need to take a ton of pics!
Noticed what I assume is an anomaly: started a flight on the runway at KASE, used the hotkey to set mixture to best power, and went to full throttle with the brakes on–the engine RPM would not rise above 2600 until I started moving. Seems pretty unlikely that this is real-world behavior. Maybe we can fix it with the max RPM friction? I’ll fool with in when I’m in the mood to tweak instead of just fly.
Also noticed that the EGT in the release candidate of the G1000 sits at 1 degree, but I assume that’s on their end. Engine pages look lovely, though!
Please note there are some compatibility issues with the G1000 0.3 pre-release. For example: since I changed the electrical systems I reference different variables for voltage and load. I have fixed this internally (not on dev-build for now).
Thanks all, the issue doesn’t seem to be with the mod.
I thought it may have had been something to do with it since my first flight with the mod was plagued by the bug, the worst I’ve seen. Though, I had a perfect flight last night with no issues, with the plane at least(side note below ).
The performance boost of the plane is a blessing. I’m currently doing a circumnavigation of Canada in the G36 and I’m glad I found this mod. The 2nd half of my journey will be much more efficient.
Side note: Avoid runway 16 if flying into Yellowknife. The arctic lake bug that put lakes on top of non existent hills put a big hill right in front of the runway. Lol makes for a very tricky landing, especially at night.
Forest4a - I’ve seen your AP issue as well, but in my case, I can always track it to the flight director going wonky. It’s never happened on the first leg of a flight for me, however. Any time it happens, its after I land, set up the altitude in the AP for the next leg, then take off. Sometimes (say, 30% of flights?), the FD indicator will go off the display nose high prior to engaging the AP. When I see that happen, if I engage the AP in SLC mode, guaranteed it’ll climb insanely until stall. But if I change to VS mode first then engage, I’ll often get a “pop” to 15 degrees nose up or so for a few moments, but then the FD indicator generally comes down quickly to what it should be and puts the plane in a more appropriate climb attitude. But most of the time when I see the FD indicator drift up off the display I’ll just hand-fly to my cruise altitude, and wait for the FD to realize I’m at the selected altitude and bring the indicator back down. I haven’t found a repeatable way to force the FD to reexamine it’s logic on the fly, unfortunately. Changing to VS mode, setting climb rate to close to what you’re currently flying, then engaging AP seems to work best, it seems,but there’s still a delay before the FD comes back down to match your AP settings.
Back when “live weather” was stuck with winds 225@3 and unchanging baro, or if I fly with a weather preset, I never have this issue. Since the last patch and corrected weather, I see the FD get “confused” more often. Not sure if there’s a real correlation, however.
The arctic lakes issue unfortunately isn’t just in the arctic. I fly a lot in the Ohio-West Virginia-Pennsylvania tristate area, and I see the lifted lakes often. Usually, they reform themselves correctly as I get closer to them and the scenery resolution and textures changes, but not always. Weirdly, it’s not ALL lakes, just some of them. But it’s always the same lakes, each and every time … one of which is very near my primary FBO in FSEconomy. As you noted, makes for interesting night ops!
That would be normal behaviour for a fixed pitch propreller (maybe not 100 rpm…), but not sure about a constant speed prop. I guess theoretically, it could also occur in a CS prop if the fine pitch angle limit is reached at full prop lever forward?
I’m hoping the checklists fit right in without too many changes, each item references a simvar so hopefully not too many changed; @FrettFS did you change your variables to match G1000 or changed the G1000 to reference yours?
If you’re setting FLC speed on the ground, the moment you hit a tailwind situation the FD pegs at full nose up, it takes about 2000ft of climb or about 2 min being airborne for the FD to correct itself afterwards. The best option is to not touch the FLC button until airborne already, then the FD will operate normally.
A little teaser screenshot taken during the FSEconomy flight I’m in right now. We are still trying to figure out a bug with the Lean page that occurs in the G36 (as you noted @dciskey, the EGT and CHT not showing correctly). All credits for the G1000 goodness to the Working Title folks!
Interesting; I usually set up the FLC rate while on the ground, to save the time fine tuning it once on the climb. That would explain why it only acts wonky maybe a third of the time; if most of the time I’m airborne long enough for the FD to recompute what it needs to do, I won’t see the issue. But if I get the aircraft cleaned up and trimmed for climb more quickly than normal, the FD is still figuring things out.
In other words, it’s time to change my procedures as my procedure is what induces the problem. Cool, wilco! Thanks
I’ll have to try this also. I always set my FLC on the ground and have been having issues with the C208 the last couple flights. And I do believe it was with a tailwind. Thanks!
I downloaded your mod and I appreciate your work. However, not all the fixes seem to be working for me. The AP altitude hold works now and the checklists are different. But the performance still seems lackluster. Climbing to 14500 ft was a chore at 200fpm (2500rpm and auto mixture on). Once at 14500ft my cruise speed was 110-120 kts (145ktas) at full throttle and 2500rpm. If I’m doing something wrong let me know.
I can pretty much do 450 fpm at 14000 (5 deg celsius) (just testing now because @dciskey, @Matchrocket and @Exp232 have done most of the work on the performance lately).
I am however manually adjusting mixture to max EGT and @ 2700 rpm during climb. Cruising @ 155 kts TAS, spot on compared to POH for ISA+20. Running LOP.
(The integration of the new G1000 mod is not available yet)
I’m running the release version. And to add some info during my climb to 14500 I was around 100kts ias and 200fpm climb. Full throttle auto mixture 2500rpm. If I’m doing something wrong I would appreciate the feedback. I’m also going to try reinstalling the mod.
Try the dev version… The current dev-version should be ‘stable’, but it is changing on a daily basis so no guarantees.
A lot of tweaks were applied in this area. If I recall correctly the current release version has indeed some problems at higher altitudes. We are currently in the process of dealing with the last tasks and tests before releasing 0.5. I expect sometime after the G1000 v0.3 update but we’re not rushing it.
).
)
