Soulflight

Go to the FMC and select "FS actions", there should be an item called "connect GPU (Ground Power Unit). After that, check that the battery switch is on, located on the left of the the overhead panel, and that primary and secondary ext power are set on, right next to that.

Without providing any settings you are running, the 22 FPS is highly subjective. My 5600x (basically the direct competition to the 10700k) pretty much owns MSFS in all scenarios, the sutters I get are all "limited by GPU" on moderate to high settings. But my GPU is only an nvidia 970 with 4GB of VRAM so thats expectable. With this, I noticed I can run stable 20FPS at LAX, but i gut heavy stutters at EDDF because of addon scenery texture sizes eating VRAM. Terrain LOD seems to affect CPU and GPU, i have it on 175 and raising it to 200 causes me more stutters, but never the "limited by main thread" ones. So, again, what settings are you running?

Just to give an example from today, I just loaded up a flight at Santa Marta, Colombia (SKSM) and official METAR reported 3kts of wind from south. In MSFS life weather there was such a strong storm it blew my twin otter off airfield right after load-up despite parking brakes being set. No IRL indictation whatsoever given that there currently are such winds in this area. I texted my friend who lives there and he is laying on the beach......

I get your point but MSFS was released two years ago and the weather still shows inaccuracies observable in everyday use. CBs for example are not modeled at all and i miss the wind varieties AS gave me in FSX.

The good thing to know is that on my rig i wont have this effect because of my old 970 GPU which is sure to bottleneck everything. 🤣

Then they are pretty pig headed, my guess is a lot of people wait for exactly this to happen including myself. AS simply had the most sophisticated weather on the FSX/P3D platform and to prevent them from doing their work is similar to, for example, locking PMDG out from making planes for MSFS.

Yes sorry, I am talking about 4x8GB with all slots populated.

Hello everyone, I recently discovered that on my system only half of my installed RAM is actually used by my system. My system is old, i know, but my system does the job and we all have our priorities. ;) I have 32 Gigs of Kingston HyperX DDR3 1600 RAM installed, which is supported according to the manual. The thing is: - BIOS, on startup and in menu, shows only 16GB installed instead of 32 GB. - BIOS "SPD menu" correctly shows all 4 x 8GB installed with correct CL10 timings also being shown. Same goes for "DRAM timing control" - Windows 10 task manager shows 32 Gigs of RAM installed, but 16,1 Gigs "reserved for hardware", what? - HWinfo64 also shows 32 GB installed and detected. For troubleshooting I restored my overclock to stock settings. (AMD 8350 @ 5,0 Ghz) I tried reseating all 4 DIMMs so far and can boot from every single one of them, as long as they are in the first two slots of my mothermoard. windows memory test (from the boot manager) also shows no issues. If I only insert 2 DIMMs in slots 3 and 4, the system wont boot. I tried cleaning them with a vacuum cleaner with no change. So i can rule out faulty RAM at this point, it has to be some setting in BIOS or Windows. Any ideas?

OK this sounds extremely interesting. I found that out while trying to take off from Bogota btw, so elevation might be a factor.

So I got the maddog as my first tubeliner for MSFS, its overall the third maddog I have from Leonardo and before I had their 2 Versions of the plane in FSX. But this EFB thing is confusing me and I am not sure if it works as it should with the MSFS weight system. The load manager that comes with the plane states 149500lbs as MTOW (i use lbs because thats what the sim uses as well). However, the EFB states 122319lbs as MTOW and tells me "takeoff not allowed" when I am above it. Therefore on a heavier take-off flight i am not able to get matching V-speeds. I am also not really sure if MSFS properly updates my weights entered in the LM, as the figues provided by the LM/ Gross WT gauge in the cockpit are different from what the MSFS weight and balance setup shows. The fuel amount is roughly the same in both. Did i overlook something or is this system not yet properly syncing?

Top of descent. I think in the aerosoft Airbus versions it used to be a straight arrow.

BTW any word if HiFi got on with their work on Active Sky MSFS version? Thats all i wait for ;)

Nope, but with the release of airliners like PMDGs 737 and Leonardos Maddog I really hope that after nearly 2 years they will finally implement this simple feature. Those planes just dont look good with massive zoom applied. All this just confirms how much they were struggling to make xbox users a significant audience for MSFS.

Let me just vent here! Dear Asobo, we understand running servers for a growing community is hard and capacity is limited. But then please, please re-write the code of MSFS to not harrass me with "Your connection had an issue" popups. It makes flying on impossible and each time I have to enter the pause menu, just to get a mouse cursor and click on "ok". First of all, my connection is fine. Its your network running out of capacity, not "my connection had a problem". Second, stop switching me to "offline mode", all I will do is enter my options and change it back, and it works fine. Just reconnect automatically. thanks. Is there any option located in any cfg or ini where i can tell MSFS to just reconnect when possible and thats it?

OK, at least the key bindings were still there and accessible by selecting the "keyboard/mouse/joystick" profiles instead of "default". Graphics and sound settings I had to set up again though. Best is to take photos of your current option screens so you can save time and put everything the way it were again.

I just restarted MSFS and it loaded the first-launch screens, addons are still there but all settings are lost, including controls. Are they stored somewhere else? MS Store version.... Why is something like that even happening?

Ouch, weak spot 😅 Yes I have addon linker and I was setting up one folder just for keeping repaints there. It still causes issues with some external programs trying to recognize custom repaint planes. How do the addon plane devs add their own liveries then, which are included in the planes "the old way"?

Now we all know you are supposed to use the community folder to install addon liveries to any planes. But I want to know if the FSX/P3D way still works as well? I would prefer that to keep my file structure more organized, also with some addons like Air Hauler, the community-folder method doesnt work so well since it is not recognizing the custom plane variants. So I tried to manually install a repaint of the Blackbox BN-2 Islander today instead of using the community folder, I copied over the texture folder to the aircrafts base folder and copy-pasted the "flightsim.xx" entry to the aircraft.cfg with the subsequent number, like we all are used to doing it for years. But the repaint won't show up in the MSFS menu. Is there more to it which i am not aware of? Or does this method not work with MSFS per se?

It definitely is, in my case MSFS immediately crashes the moment REX is trying to inject weather to it.

My bad. I narrowed the crash down to REX weather force connecting to the sim. With MSFS' own live weather it seems to be running fine. Compatibility issue.

My bad. I narrowed the crash down to REX weather force connecting to the sim. With MSFS' own live weather it seems to be running fine. Compatibility issue.

Thats two different things. At least there is a value to be set of this now in the camera.cfg (which means at least we can manually adjust the viewpoint outside the sim). The other thing would be binding a key to that value. That option still seems to be missing so far.

Yes i have seen your thread regarding that. The option unfortunately is missing in my Win10 graphics settings. thanks anyways. I updated my graphics drivers today (nvidia) with no change so far. With reinstalling everything i have to say that I am still not ready to enter the week-long process of downloading, installing and setting everything up the way it was, just because I installed a mandatory update.

persistant CTDs after max 10 minutes even in safe mode. I hope that counts as significant. 😉

FINALLY!!!!! Now just get SU9 running stable and we are friends again, Asobo. 😅