In my last blog post where I discussed the upcoming MSFS AAU2 (Aircraft & Avionics Update) which is due to release on 23 June, I briefly mentioned some issues I had been having with my gaming PC. The PC in question, I called GBS Beast Mark V (which was the 5th gaming machine I had built in recent years). I built the machine in May of 2018 (5 years ago) and at the time it was pretty much top of the line with an Intel i7 8700K CPU, Nvidia 1080Ti GPU and 32GB of RAM. It performed well with the games of that time period including American Truck Simulator, Euro Truck Simulator 2 and Prepar3D Flight Simulator. It performed OK with the new Microsoft Flight Simulator. However, sacrifices had to be made with some graphic settings in an effort to keep the FPS above the 30 FPS mark.
However, over the past month or so I had been experiencing several issues which caused concern for the overall health and longevity of the machine. I’m pretty good about keeping backups, so about two weeks ago I made a backup of everything I needed and a few days later the machine finally rolled over and said no more. I quickly put a plan in place to start looking at the costs of building a new machine which would obviously be more powerful and hopefully future proof for at least another 5 years.
GBS Beast Mark VI
Obviously technology has taken a huge leap forward over the past several years and certainly so since 2018. As previously stated, I wanted to try to future proof any new build everywhere possible. As with previous builds, the most intensive gaming I play is flight sim. To truly maximize the total immersion possible, any new build would need to have the very best CPU and GPU available and that’s what I’ve done with this new build.
GBS Beast Mark VI features an Intel i9 13900KF CPU on a Z790 motherboard and cooled with a liquid CPU cooler. In addition, I’m going with the top of the line Nvidia 4090 24GB GPU. In addition, I’m adding three Samsung 990 Pro NVME SSD’s and reusing three Samsung 870 Evo SSD’s from the old machine. Total storage capacity will be 8 TB. In addition, I’m adding 32 GB RAM (DDR5) which is more than enough for the games I play and all this will be housed in a massive (largest case I’ve ever used due to the massive Nvidia 4090 GPU) Corsair 5000D Airflow ATX Case.
As I have stated many, many times over the years. I tweak my system for smoothness and typically don’t concern myself too much with how many FPS I can get from the hardware. As stated above, my old gaming machine was still capable of giving me a fairly smooth experience around the 30 FPS mark in Microsoft Flight Simulator. Of course, I had to dialed down some of the graphics settings in order to achieve this, but nonetheless I was able to enjoy the sim just the same.
Of course, the beauty of having this extremely beefy system now with the i9 13900 KF CPU and the truly awesome Nvidia 4090 GPU, I’m pretty much able to run my graphics settings to the full extreme and still enjoy a smooth, buttery visual experience at 60+ FPS with both the Fenix Airbus A320 and the PMDG Boeing 737-800.
The WOW Factor
I’m literally blown away at the huge leap forward I’m experiencing with this new PC and it very much reminds me of how I felt 5 years ago when GBS Beast Mark V came to life. But of course MSFS wasn’t around at that time and has completely changed the flight simulation landscape. Over the next few weeks I’ll continue tweaking the new machine and will post my settings once they are all dialed in the way I want them. While I’m not saying one cannot enjoy MSFS without a 4090 GPU, I will just say that it is absolute joy to see the virtual skies in all their glory without sacrificing performance.
It’s great to have a gaming machine once again and I look forward to many years of what I believe will be truly awesome experiences in all the simulation games I enjoy. Obviously, Farming Simulator and American Truck/Euro Truck will certainly enjoy the benefits of the updated hardware, but of course not to the same level as MSFS since that is both a CPU and GPU extensive simulation.
Until next time…
One of the most common questions I receive from readers of my blog is regarding FPS improvements in Flight Sim and in recent months (for obvious reasons) these questions are concerning MSFS or Microsoft Flight Simulator (2020). Just in the past few days I’ve received three different emails asking for pointers on just how to squeeze out a few more FPS on the platform. While I’ve provided a few tips/answers to these emails already, I’ve selected one of those email questions to feature for this article. Let’s go!
Hello Jerry, I’m really struggling to achieve 60 FPS within MSFS when flying either the PMDG 737 or the Fenix A320. My hardware setup is not that much different from what you are showing on your blog site and I’ve also attempted to match your MSFS settings. The best I seem to be able to achieve is about 35-40FPS with mostly clear skies. But this number drops down to 25-30 FPS in cloudy/stormy conditions and about the best I can achieve on the ground is in the mid 20’s. I’m fairly new to flight sim with MSFS being my first introduction. I don’t seem to have these issues when flying the default Cessna and my other games also seem to be fine with 60+ FPS. What gives? JP
Thank you JP for your email. First, allow me to state for the record that I don’t get a consistent 60 FPS in MSFS with my posted settings. I never have. For many years I used to really stress over this fact until I finally realized that within flight sim a steady 60 FPS isn’t necessary and second to that, is really, really difficult to achieve especially when flying the more complex airliners like PMDG. On my current hardware configuration, really the only way one could achieve a steady 60 FPS will require the graphics settings to be turned down really low and that’s just not something I’m willing to do, nor do I feel is necessary.
One of the best solutions I can provide to you is fairly simple. Setup your sim the way you like it, which will provide you a smooth visual experience and simply forget about the actual FPS number. I realize this is probably the advice you were not wanting to hear, but trust me….once you get MSFS dialed in where you have stable visuals and just simply ignore the FPS number, your overall enjoyment factor will increase.
Over the past couple of decades I’ve used all flight sim platforms from FSX, P3D and now MSFS. I’ve always been somewhat behind when it comes to hardware specs. Today, my gaming machine is approaching 5 years old. When it was built and for a few months I perhaps could have considered it the top of the line at that time, but that’s no longer the case. Even after upgrading my GPU to the 12 GB 3080 Ti back in the late summer of 2022, I’m still running an older spec CPU which went into the machine in 2018. These specs just aren’t capable of running MSFS at a steady 60 FPS or more with the desired visual settings I require in the sim.
Having said all that, what I can say is based on my current hardware and my MSFS settings which I’ve posted, I have a steady sim with zero lag, zero stutter and all the beautiful eye-candy that I require in my sim when flying the PMDG or the Fenix. Some may argue with me, but flight sim does not require a solid 60 FPS to be enjoyable.
In closing, the Microsoft/Asobo team have made incredible progress with better maximizing the performance of the platform and I’m sure over time this will continue. In addition, the Fenix team have done the same with even more work currently in progress. The best advice I can give anyone reading this is to dial in your graphics settings to the point where you can achieve a stable experience with no lag and no stutter, then forget about the FPS number. Once you’ve done this, I promise you can enjoy flight sim without the stress of chasing 60 FPS.
Until next time…
There are many reasons why the user community of Microsoft Flight Simulator or just about any major gaming title (simulation or otherwise) should participate in the various beta or early adopter updates released from time to time. While in a perfect world, the developer behind any gaming title should have the resources to perform system testing to rule out major issues, the hard truth is most do not and there’s almost no way for any developer to test all the possible scenarios including hardware configurations and 3rd party add-ons/mods which all can and mostly likely will have an impact in the finished product. In actuality, the developer (in this case Microsoft/Asobo) will perform their very best due diligence to ensure the update performs on a few different hardware configurations and generally leaves it up to 3rd party developers and mod creators to “shoe horn” their add-ons around what they’ve been provided. So our participation in these beta programs (especially when feedback is sent back to the developer) is instrumental in the overall wellbeing of the gaming title.
Generally speaking, most 3rd party developers will participate in the beta programs for obvious reasons. But they do not receive the beta version in advance of the general public. In other words, 3rd party developers like PMDG and Fenix only have access to the beta when it’s been made available to all of us. The 3rd party devs will utilize the time between when the beta is released and it becomes GA (General Availability) to work out any issues with their add-on. Of course in many situations this all becomes a fast moving target as there may be many iterations of the beta. The time a 3rd party developer spends adjusting their add-on to function correctly with the beta could become a complete waste of time as changes are made and pushed out during the beta cycle. In other words, in some cases the only way of truly knowing if a 3rd party add-on is going to work is to wait until the beta has become GA and been released to the entire community.
Over the years, I’ve participated in many beta programs for all sorts of gaming titles. Some have been positive, wonderful experiences of being able to gain access to new functionality or performance enhancements before everyone else. But in a few cases these beta experiences have become an absolute nightmare. In many cases the only way to escape the beta is to complete reinstall the current live version. As you can probably imagine this can be an extremely time consuming process.
A few weeks ago, Microsoft/Asobo began their open beta for the upcoming SU11 update and the word on the street is the experience hasn’t been an easy one. Especially with some 3rd party aircraft and live weather. Some 3rd party developers will do their best to provide solutions or workarounds for their products for the beta cycle, but most simply can’t and won’t guarantee functionality on a beta installation. On the bright side, with regards to the SU11 beta, some users have reported experiencing a significant performance improvement from SU10.
If you’re wondering if participating in the MSFS beta program is right for you, I would say it depends. If you mainly fly default aircraft or if you still fly P3D/XPlane then participating in the SU11 beta (or any future beta release) is probably OK for you. However, if MSFS is your sole flight sim platform and you’re an every day flyer of add-on aircraft like the Fenix A320 or the PMDG 737, then I would highly suggest you hold off. Bottom line, if you want full system compatibility between MSFS and 3rd party aircraft, then stay on the current live MSFS build. Otherwise you may be in for a surprise when you attempt to fly your favorite 3rd party aircraft in the beta build.
As always, thanks for reading.
It’s been a while since I took the time to write a flight sim blog post. I’ve been busy with lots of DIY projects and just enjoying the spare time I have flying. As I discussed soon after the release of MSFS, I decided to continue to fly Prepar3D v5 for all my airliner flights and have enjoyed Microsoft Flight Simulator mostly for General Aviation flying. While I recognized from the very beginning that MSFS was going to be the new flight simulator standard, I saw no immediate need to begin flying airliners in the platform until just recently for several reasons.
First, while I did briefly play around with the FBW A320 in MSFS and will admit that what that team accomplished with the FBW A320 project is truly amazing, I didn’t see it replacing the FSLabs A319, A320, A321 I had in P3Dv5. Second, from a short-haul perspective….I had everything I truly needed between the FSLabs and the PMDG 737. I truly was waiting for something to grab my attention to the point where it would suck me right into MSFS. Third, I must admit that I’m super spoiled with using Chaseplane to handle all my camera views in P3D. The MSFS camera view system is seriously lacking when compared to Chaseplane and as I’ve been a Chaseplane user from the very beginning, old habits are truly difficult to break.
While I’ve been anxiously awaiting PMDG’s release into MSFS, I was slight disappointed in their release strategy. Don’t get me wrong, I understand the reason behind releasing the Boeing 737-700 first, followed by the 737-600 then finally the 737-800 followed by the 737-900. After all, had PMDG released the B738 first, they might have struggled with getting the sales on the –700/-600. But, for me personally I’m just not interested in owning a –700 or –600 variant. My primary interests are in the 737-800 and the 737-900. As I fly mostly American Airlines with some Alaska Airlines flights mixed in. But I digress as this blog post is supposed to be about the Fenix A320.
I began hearing about the Fenix A320 project a few months ago. I’ll be honest, I really didn’t pay much attention to it until the last 60-90 days before release. But the more I read about it the more I anxiously awaited its release and realized this could be the airliner to finally bring me more into MSFS. After all, I absolutely love the visuals (eye candy) in MSFS over P3D and truly want to do more airliner flying in the new sim.
The Fenix A320 was a day one purchase for me and since the release, install and setup…I’ve flown nothing but the Fenix in MSFS. I’ve successfully logged 24 flights in the Fenix and absolutely love it. I’ve managed to setup the MSFS camera system to a point where I can use it and have been having fun. I’ve flown a variety of short flights (1-2 hours) and several longer flights of 3-4 hours. Both the Fenix and MSFS have performed flawlessly. I’ve also started adding a few airports into MSFS from both some freeware selections on Flightsim.to and a few payware options where I’ve had discounts from previous P3D purchases. While I’m not ready to uninstall P3D as I plan to fly P3D tomorrow in the Boeing 777, I’ll do the majority of my short-haul operations, and certainly all my Airbus flying in MSFS.
Final thoughts on the Fenix A320. I don’t like to “Never Say Never”, but if the devs behind the Fenix project remain true to their word and release the additional engine types and sharklets for the A320 and if they also produce (in time) an A319 and A321, I’ll be a Fenix customer from this point forward and won’t even consider any future FSLabs purchases in the A319/A320/A321 categories. But of course time will tell.
As always, thank you for reading.
Until next time…