**** Official Microsoft Flight Simulator Thread ****

PSA: Don't buy the Orbx London City Pack (at least not yet) unless you want to ruin several iconic landmarks...


I hope they'll update it cos their Canary Wharf is considerably better than standard, and it adds several other buildings which aren't there by default.
 
Techen said:
no judder for me in window or full screen I do see lfc kicking in sometimes when FPS drops hard but otherwise it’s lovely !
Click to expand...

Are you using the Windows gamepass version or not though? If you're using the steam one, what display settings options do you have for fullscreen etc? On gamepass there are only 2 - fullscreen or windowed (and as explained in my previous post, fullscreen is not 'true' fullscreen).

The game for me is unplayable due to terrible judder unless I put vsync on in game and set a 60fps limit. This is smooth as butter but ONLY if the framerate can maintain a solid 60. If it drops to the 50's or 40's the judder returns. This is with Gsync set to be on for fullscreen and windowed in the NV control panel by the way and the Gsync indicator widget is displaying. However, Gsync is just not working in this game and it's therefore an unplayable judderfest for me.

Going to try the latest NV drivers from yesterday, just in case. I already know it won't help though. This is a "fake fullscreen" not playing right with Gsync issue that I've had with a handful of games years ago but can't recall which ones.
 
Last edited:
willhub said:
Why of a planes cruise speed is 455KTAS can't it exceed 350 without breaking up?
Click to expand...

Assuming this isn't some sort of program bug I think you may be getting mixed up between true and indicated airspeed. Your aircraft's air speed indicator's reading (KIAS) will vary considerably from your true airspeed (KTAS) depending on local air pressure and temperature. This means that it reads progressively lower than your true airspeed the higher you go. The reason that the airspeed indicator is not built to automatically correct for varying air pressure at altitude and read true airspeed is because dangerous conditions like stalling, critical mach or over-speeding are dependent largely on the aircraft's indicated airspeed, not its true airspeed. For navigation purposes to get ground speed a correction to indicated air speed needs to be made using a formula that takes into account altitude etc.
 
Folks, is it me or does it take sometime for this game to load?
Is there a way to skip the logo splash screens?
Even loading a flight sometimes takes a min or so (listen to me complaining compared to the loading times of Spectrum and C64 days :D)
 
Cavallino said:
Folks, is it me or does it take sometime for this game to load?
Is there a way to skip the logo splash screens?
Even loading a flight sometimes takes a min or so (listen to me complaining compared to the loading times of Spectrum and C64 days :D)
Click to expand...

Oh yes feels it takes an age too. We're so used to things being instant. I did think about the C64 and Oric days at the time too when we use to wait ages for cassettes to load! And I remember a particular game probably 4 times out of 5 wouldn't load after the waiting!

I don't think there's any way out of the splash screen. I assume it's caching /loading program items into RAM, not sure tbh. I was thinking it's loading items off the net but can you play this without the net if so then that blows my theory out of the window.
 
After a bit more time spent in the game, I’m beginning to see where some of the frustration is coming from. Most of the GA aircraft are uncontrollable, slightest input gives you a bucking or twisting bronco even with sensitivity dialled down. I’ve crashed several times on takeoff already as you just cannot get stabilised enough to look away from the windscreen and activate the autopilot. The only aircraft I’ve had much success with is the Icon Microlight.

In my revised humble opinion, this is early access at best and should have been offered as such at a price to match. Oh it’s a lovely scenery simulator but needs a major rework to come up to scratch.
 
Got the same x52 issue here. If anyone has a xml map for the x52 and wouldn’t mind sharing that would be very kind.

Also getting random CTD when connecting the x52.
 
Vern1961 said:
After a bit more time spent in the game, I’m beginning to see where some of the frustration is coming from. Most of the GA aircraft are uncontrollable, slightest input gives you a bucking or twisting bronco even with sensitivity dialled down. I’ve crashed several times on takeoff already as you just cannot get stabilised enough to look away from the windscreen and activate the autopilot. The only aircraft I’ve had much success with is the Icon Microlight.

In my revised humble opinion, this is early access at best and should have been offered as such at a price to match. Oh it’s a lovely scenery simulator but needs a major rework to come up to scratch.
Click to expand...

have you changed the snsitivity/deadzones? My xbox controller was virtually unusable at default. I have set the deadzones to 15% and the sensitivity curves to -25 and it flies like a dream now, well as much as a dream using an xbox controller is.
 
Last edited:
physichull said:
I've got a 6700k, 2080ti and 32 Gb RAM and its runs well on my system at high settings, need to dial it down a little from ultra, but a lot of it is individual preference. You should get good performance from your rig.
Click to expand...

Thankyou for your reply, I forgot to mention I have 32 gb ram as well,
So with a 1080ti,i7 7600k and 32 gb ram I find messing with individual settings very hard so basically just select pre selected options,
So just trying to get enough basic info to get the best possible performance for this game.
 
jonchaz said:
Assuming this isn't some sort of program bug I think you may be getting mixed up between true and indicated airspeed. Your aircraft's air speed indicator's reading (KIAS) will vary considerably from your true airspeed (KTAS) depending on local air pressure and temperature. This means that it reads progressively lower than your true airspeed the higher you go. The reason that the airspeed indicator is not built to automatically correct for varying air pressure at altitude and read true airspeed is because dangerous conditions like stalling, critical mach or over-speeding are dependent largely on the aircraft's indicated airspeed, not its true airspeed. For navigation purposes to get ground speed a correction to indicated air speed needs to be made using a formula that takes into account altitude etc.
Click to expand...

Maybe I'm not controlling the plane properly I tried a 747 or whatever it is and was struggling to get to 50k ft spending forever ascending at 250Knots and only way I could get near 500 was to descent so fast the plane crashed .
 
You must log in or register to reply here.
Back
Top Bottom