Bottle

I'm waiting to see what AMD throws our way in regards to both CPU and GPU. No upgrade for me until at least Christmas.

I agree. We should consider post release to be more like they are continuing development rather than they are fixing bugs. It seems pretty obvious that a bean counter somewhere in MS decided the release date and not the developers. Having suffered a lot myself from top-down management styles, I empathise a with Asobo.

https://www.stitcher.com/podcast/justin-siems/pilot-to-pilot-aviation-podcast/e/77556871

I think they forgot to model the couple of bricks lying under the front seat.

I have no bets in this race, so you might be right. But he's not the only one to report the rumours that numbers of cards will be low, especially the 3090. Personally, I'm waiting until the new year until supply and drivers are sorted out, tests and reviews done (especially wrt MFS), patches for the sim have come out, and hopefully the new AMD CPUs and graphics cards have been released. In a situation like this where a number of new things are being released at about the same time, once the dust settles will be the best time to upgrade in my book.

This may be a useful video to watch. Especially when he talks about the availability of cards. Some of you may be very disappointed or at least frustrated by the wait.

The only thing the AI will have learned it to avoid humans at all costs.

Yep, I have HT turned on. I'm hoping mention of stutter improvements in the Sept update indicates its origins are in the software and that the improvement gets me through to the new year when I hope to build a new PC with the newly released AMD CPU.

That's an interesting idea. But see my post above. Granted, it's not the fastest CPU or motherboard, but everything working off of M.2 NVMe drives means one would expect to have minimal write issues and in any case the data that has to be saved (literally a couple of coordinate, altitude and flight condition numbers) is miniscule.

Internet usage didn't show anything consistent with the stutters (it was quite noisy throughout). I have 200Mb dl and 20Mb ul speeds and generally with low latency, so I'm not expecting anything there. I have the sim installed on an M.2 NVMe drive and my OS and Windows Store, et al. on a seperate M.2 NVMe drive. I wasn't expecting those to be a problem but of course they could be for a host of different reasons. There are multiple scenarios one can envisage but one is that there is something in the sim code that gets caught up and so the CPU has a temporary "brain fade" with respect to supplying the GPU with information. It's interesting that it's quite consistently a 10% drop in CPU usage and and exact halving of FPS. The GPU drop is more variable.

I'm with you there. My initial free flight test suggested stutters were all but eliminated, but a couple of hours of the bush flight challenge and I can see that they're still there, though possibly briefer. I have an i7 6700K, so only a quad core. I decided to track CPU and GPU via task manager to see what's happening during the stutters. Interestingly it was very apparent and consistent. I get a half FPS stutter that appears to be caused by a 10% DECREASE in CPU usage and an associated dip in GPU (most likely the CPU dip is causative of the GPU dip). RAM usage is solidly consistent throughout.

Google "node-based particle effects" and watch a few videos to get an idea of what's in store for the sim. Add to that addressing inertia, stutters and ap and we'll be "cooking with gas" as they say.

Might be placebo, but I've just tooled around in my usual way (Orcas in the Savage Cub) for about 15 minutes, and not a single stutter. Plus the live weather actually seems nuanced now. The first time I've had to side slip into a landing. From other people's observations of what's been downloaded, looks like they are slipping in some extra fixes nor mentioned in the patch notes.

I left flight simming almost immediately after FSX was released. It was supposed to be revolutionary but instead looked like [word not allowed] and performance was the same. Now I'm back and not leaving. In the last week I've had my best flight sim experiences ever, and it's only going to get better. Thanks Asobo. Begrudging thanks to MS as well though I'm pretty convinced the poor release is all down to them.

Perhaps it should be called "wearing sunglasses mod"

Here's another good one.

Have a look at Flightchops' interpretation at about 18'

The ability to scrape ice off your plane once you've landed. The ability to swap between normal sound and headphone simulated sound whilst in flight.

I decided to try out the DA40 for the first time and chose a route from Telluride (TEX) to Aspen Pitkin County Airport (ASE). Well, soon after takeoff I realised the DA40 is not the best choice for the mountainous territory but soldiered on. Slowly I gained altitude so I could skim through the passes and enjoyed the very realistic turbulence along the way. I'm assuming the plane felt under powered because of the altitude. It looked like plain sailing for a while until I iced up having passed through some very light cloud (it is about 11,000 feet after all). Then I started to get low fuel warnings! Oh dear; can't see, I'm running out of fuel and I don't know how to drive the G1000. Thankfully I had airport notifications turned on so up popped Gunnison–Crested Butte Regional Airport (GUC). At first I was confused by the runway numbers because it has a small grass strip with no numbers pained.But I managed to get down and find a fuel pump (discovered how the refueling system works in game as well). The default airport looks really nice (highly recommend it for a nice airport plus the surrounding landscape) and I noticed the huge "W" painted on the nearby hillside which can be easily seen in satellite images (I wonder what the backstory to that is). The one thing I'd like to see implemented is a way to scrape off the ice once you've landed. Without that, I had to continue with only about 25% visibility. Off I went and it was clear that the direct route would be too high so I detoured through some lower valleys. Really nice scenery again. I saw Buckhorn Ranch Airport-Crested Butte Airpark to my left but resisted landing their, choosing to keep climbing as it looked like a tough mountain ridge ahead to get over. I wasn't wrong! As I climbed I iced up even more (only about 10% visibility now) and the plane became harder and harder to handle (I'm assuming ice weight is modelled). In the end I foolishly committed myself to cresting the ridge with insufficient altitude or space to turn around and literally just clipped the ridgeline with my gear all the while listening to the stall enunciator screaming at me for my foolishness. But once over, what a ride down the valley it was! Following West Brush Creek past Teocalli Mountain then onto the aptly named Conundrum Creek and finally down to Aspen, all with only blurry visibility through the ice. But my troubles hadn't stopped there. Still heavily covered with ice and at altitude I fought stalling in my lazy plane as I tried to circle the airport and again literally clipped a pine tree in someone's backyard. Without being to see much I accidentally ended up once again in a river valley and flying in the wrong direction! What to do other than attempt a tight turn in an iced plane! This time I thought I was a goner but having skimmed the trees once again whilst fighting a stall (and probably scariung some fly fishermen below) I finally came in for a landing. What a relief. I followed the taxi assist arrows and curiously they led me down between two covered car parks (which is an actual taxiway at the airport). Ignominiously I crashed fatally simply as I negotiated the parking lot (I'm not sure if my wing hit something or a car drove into me). All up it was one of the best most convincing flights I've ever had. I'll be back there to explore the landscape more (it's really quite breathtaking) but in a beefier plane. Question for those familiar with the DA40. I had to fight excessive RPM warnings throughout and couldn't adjust with the keys I'd mapped, nore did there seem to be a control in the cockpit. I'm assuming the DA40 has an automatic RPM limiter and it can't be tinkered with. Is that correct? Probably not a problem under normal flying conditions but when at high density altitude conditions and iced up it causes some headaches. i7 - 6700K (stock 4.0 GHz) - HT turned on 32 Gb 3200 RAM - XMP settings in BIOS Gigabyte aero 1070 OC (8 Gb) GPU - 452.06 driver M.2 SSD 1920 x 1080 144Hz G-sync Ultra settings except a few turned down. Averaging low 40 fps with occasional stutters down to 20 fps

Small questions here. I was flying the VL3 Evolution around Victoria Island yesterday when I ran into icing conditions. I discovered my airspeed indicator had stopped working and suspected my pitot tube must have frozen. I went looking around the cockpit to find a pitot heater button but couldn't find one. However, the mapped pitot heater on my keyboard solved the problem. Q: Does anyone know if the VL3 Evolution has a pitot heater button IRL and it's not been modelled in the MFS cockpit?

I’ve never used it but it sounds eminently appropriate. I’ll investigate tomorrow.

Has anyone tries CH Control Manager? You can make all sorts of sensitivity maps with it. If that then maps into the sim, then you’re fixed. I’ll experiment with it tomorrow.

No VoIP is included in the game so you have to use an external app of some sort. TS or Discord for instance.

I checked for Windows and Intel updates (none needed). Then Nvidia did an automatic driver update. Then I updated apps in the MS Store. Then I rebooted my system just to be sure. Opened MS Store again and signed up for Game Pass. Then installed MFS (I was surprised to find it even allowed me, through a prompt screen, to download the launcher onto a drive of my choice). Started MFS and it started with an accessibility setup. After that it started downloading everything else (again after asking me where I wanted to locate it). The whole thing crashed after about 5% but to be fair I was also messing about with Windows at the time. After I restarted it, it sensibly started again where it had left off. 1.5 hours later and it was installed (I have 200/20 internet speed). Less than an hour to map and calibrate my HOTAS (including CH throttle and pedals). No problems anywhere. I’ve been flying around for about 3 hours so far with a bit of settings experimentation with nothing of comment other than some slow points during loading. It all looks rock solid for me so far, and working well on ultra and 1080p with nothing but a 1070 card, i7 6700K CPU and 32 Gb of 3200 RAM.