Sounds like you got extremely lucky. Give it a couple more tries. There’s a reason there are massive threads on reddit and on these forums as well as folks who have already found the errors in code base (of course, the neo mod team spotted it) where they screwed up the A320, and you’re going to sit here and downplay it like it’s some kind of circle jerk that isn’t real?
All I’m doing is describing my honest experience, which seems to contradict what is being described on here in places.
At the sake of reiteration, if something doesn’t work for me, I will happily say so. If it does work, I will also say so and I have no agenda or bias in that regard. If you are so eager to believe what all these people say and join the circle jerk (your words not mine) , then that’s on you.
Totally agreed! Installing a patch should allow for a delayed install. A good practice is usually to wait for a week, so a hotfix can be worked out, and you install the final solution. Never force-feed a patch.
Sounds like ■■■■■ potentiometers and such in your X56. My old X56 had issues like that in X-plane.
Good for you
however, this topic got 192 votes
it must mean something, doesn’t it? Asobo themselves have acknowledged it as a known issue, I don’t think people complain just for the sake of it
Also, the issue with cold and dark startup of the A320 doesn’t always happen, so perhaps you’ve just been lucky on your first flight?
Hope they will fix it soon.
So presumably starting with engines already running leaps over a part of the logic that causes the engine to shut down? My guess would be that starting on the runway, with engines running, then shutting the aircraft down, and then attempting a re-start would cause the bug to manifest also.
not really it’s not a titan rtx, you need a replacement for your old titan, 3080 or 3090 should be good, but also 3070 is better
The new frame limiter for cockpits in options at the bottom - it’s set to medium - put it back to high!
No issues with the pots in my x56. And it wasn’t just pots. It was buttons as well.
I was playing as the patch dropped and all was fine. I updated the game, and the issue started. Tried other games, no issues at all.
Ultimately as a last resort, I uninstalled MFS2020 and reinstalled fresh. The problem is now gone. Everything works as smoothly as it should.
Same for me… With a lot of other bug…
I can’t even fly, no control and there is no menu to adjust yoke sensitivity which i think is the problem for me. Tried the BE36 and couldn’t even get airborne then a 172 and it went nose first into the ground from about 500ft and I could do nothing. That happened several times. I guess I’ll shut this down for a couple days and see if they comeback with an update. They did add the altimeter knob to the a36, beyond that I have no clue what improvements have been made.
any of your mfd pfd issues were caused from the g1000 upgrade mod that was designed BEFORE the patch.
I have no g1000 mods. I have had the blanking issue since the patch.
do you have the refresh rate mod?
No mods installed at all. Only scenery addons and a couple of liveries.
for grins have you moved those out of your community folder and tested without any mods at all?
Yes, I had moved everything out of community folder prior to installing the patch. (not my first FS rodeo ) Tested, bad performance and a the mfd blanked out in the G58. I’ve subsequently put my stuff back in the folder and nothing changed there. Had one subsequent blank out on the C172.
System Specs:
asrock z390 phantom gaming mobo
I7-9700k @ 4.9 GHz
32 GB Ram
Geforce RTX 2070 running 1440p Acer monitor
FS is on dedicated 500gb M.2
Internet download speed average 450 Mbps
We don’t need no stinking testing!
King air and caravan will no longer start even with checklist being auto completed