Funky D

I did some testing with the fully loaded Kodiak on sloped grass strips after reading about your issues with bouncing in the other thread. I didn't have any bouncing issues with the regular tires with multiple landings at different small strips, and not all of those landings were pretty. If you want to dumb-down the flight model no one can stop you, but I'm guessing your issues are related to improper technique. The numbers aren't in the manual, but check the pics of this flightsim.to addon for the Kodiak's landing speed chart. If you're bouncing, you are probably coming in too fast... my fully loaded landings were 70-75kts over the fence.

I suspect they're making changes on the backend with ATC processing... I'm not in the beta, but I'm noticing ATC has been better lately with descents in career missions. Sometimes ATC will ask me to descend twice, a bug that I never noticed in the past. There seems to be tweaking going on with both career missions and ATC that never makes it to the change logs.

Are you using the tundra tires? I've read about people finding the tundra version "bouncy" like you mentioned. I couldn't find any info about tundra tires for the real aircraft so not sure how common they are in the wild (all the pics I've found of the real aircraft seem to have the same tire size). I haven't had issues with the regular version, but I usually fly it into paved strips. I will say that most aircraft in the sim are too forgiving when it comes to bounces or porpoising. I don't think I've ever bounced the default 172 and I've had some doozy sim landings that you'd never get away with so "peacefully" in real life!

With the last update to the Kodiak's flight model, you can hold it off the runway fully loaded until stall speed if you try. I can't comment on torque numbers, but I believe all devs have had to do workarounds to make turbine engines work somewhat believably. Hopefully the new turbine SDK additions in SU6 help with this and SWS can implement them when SU6 goes live.

Since this is a marketplace plane, the updates are automatic. Microsoft/Asobo list the marketplace updates every week in their marketplace newsletter, or you can join the FSReborn Discord or keep an eye on the Phenom thread in the official MSFS forums.

I've only flown the update once, but there are some nice changes that are apparent right away. The G3000 has some further customizations to make it more like the real Phenom version. CAS advisories are now auto acknowledged after a short amount of time (nice during startup and taxi when the Bleed advisories appear), the transponder page has been completely overhauled to match the real aircraft, and I believe some text colors on the PFD have been updated. I also noticed the adjusted crosswind ground handling on my first flight (the takeoff roll seemed to need gradual rudder correction instead of needing a bunch of correction all at once at higher speed). One thing I'm testing is extremity deadzones on my yoke... most of the nice yokes out there have 180° of roll axis, but the real Phenom seems to be only 90°, so I set extremity deadzones so the yoke reaches full deflection at around 45°. This makes it more sensitive, but should also make handling in crosswinds easier. The one bummer is the new flight model shows up as a different variant, so I needed to sell and repurchase my version in career mode. About to take her up for a spin again and will hopefully find a destination with a bit of crosswind to test the handling further.

Probably related to VRAM management. I don't see the issue often, and the times I do it's when switching from internal to external views and back, and I usually only do this at altitude when VRAM requirements are at their lowest. I also use the in-sim dynamic settings and only purchase native 2024 airports and aircraft. I would guess using addons not optimized for 2024 would just make this problem worse. For me the blurry gauges clear up within a second, so it doesn't bother me when I do notice it, but I could see it being annoying if it happened more often and took longer to clear up.

I believe the issue is most noticeable with analog gauges, if you fly mostly in glass cockpits you may never see the issue.

...for half-baked advice. Pretty sure the sim does not even have the ability to touch the Windows Narrator settings, but by reposting this it just adds to the algorithm and gives this bad advice to more people. Settings -> Accessibility -> Narration and audio -> Enable Screen Narrator This is also available right when you start the sim, I believe there is a direct button to the accessibility settings.

And lately, more and more people have then been posting the incorrect or partially correct "answers" here or Reddit or Discord or name your forum of choice. If the poster wanted an AI response instead of a response from a human that knew what they were talking about, they could just go straight to ChatGPT or Claude or Gemini or name your AI of choice. LLM's do not know the answer. They do not know how to reason. They take the massive amount of data they have access to and churn out a response. The source of that response could be a sarcastic troll or a combination of information that may be related to original question but isn't actually the answer to the original question at all. I've asked AI about things readily available online... I asked the length of a 5090FE and it gave me random lengths from (presumably) other 5090 cards. I've asked AI the location of MSFS 2024's application folder and it gave me the location of 2020's folder instead. And it gave those wrong answers very authoratively! AI isn't taking jobs because it knows how to do anything... it's taking jobs because the former human employees wrote very detailed processes and the AI was trained on that data. It's why AI is good at coding: there are millions of GitHub code repositories out there that helped train AI. But AI doesn't actually know how to code... it just knows how to spit out code that was already used, hopefully in a working application. AI doesn't have access to the MSFS source code. It can't give any super special tips and tricks for MSFS that aren't already available online. Sometimes those tips and tricks are valid, and sometimes they are snake oil... just like AI itself.

Have you tried disabling any audio devices you don't use? If you go to the Windows Control Panel -> Sound, you can right click any playback and recording device you don't use and disable. I remember seeing this fixing the audio issues for some people... I personally haven't had any audio issues since SU4.

The EFB is also crooked for me at the start of each flight, but you can right click drag the edges to rotate the EFB so it's horizontal, or you can use the scroll wheel while the mouse is along the edge to rotate. Then left click drag will angle the EFB up or down. Hope this helps!

I am fine with "unrealistic" products as long as they're marketed correctly and priced fairly. Plenty of casual users want to fly simple planes that look nice... with MScenery they were getting an overpriced product with flashy marketing pics and ended up sitting in a cockpit that looked like it came out of Minecraft. It would be nice if they added a marketplace filter for realism so the more arcade-like products could be filtered out.

Big respect for AvAngel calling out MScenery in one of her recent videos. It takes some guts as one of the top MSFS content creators to push back on something that was obviously making MS money. We'll never know how many gullible console users forked over real money for sub-FSX-freeware-quality aircraft, but hopefully the bad purchases won't keep those users away from the many great marketplace products. MS/Asobo really need to follow this up with new marketplace rules: No AI-enhanced product images and no review manipulation.

There is also the issue of bandwidth... higher satellite and TIN resolution = more data to stream. People like to blame the consoles for Asobo downgrading the satellite resolution in both 2024 and 2020, but I would wager the real reasoning behind the downgrade was someone at MS took notice of the bandwidth being used and forced Asobo to cut the resolution to reduce costs. Apple Maps seems to have higher resolution elevation data for many of their 3D locations than Google or Bing maps... I wonder if this is less about any technical differences and more about the lower popularity of Apple Maps negating the extra bandwidth needed for higher resolutions. The resolutions available for commercial and government use are probably crazy detailed.