This new patch has made me stop playing

So, I can’t adjust my sensitivity settings after this update.

The AP on the a3neo is still fubar. The Localizer/ILS is working better though. Sometimes the mach/knots button will switch to mach and I won’t be able to switch it back to knots, other AP knobs become non reactive.

Ap will sometimes remain active, but drift off course and just not respond to heading/nav inputs.

The TBM had some issues as well, but I forget what exactly they were.

Weather is still broken, although better.

The preformance is better, but now the altitude/speed screen stutters at high FPS.

Yeeeeeeeeeesh!

3 Likes

Let me clarify, I’m not “done,” I’m just taking a break until the game becomes playable. Hopefully it’s only a few days, I’ve been having a blast until this insane “update.”

3 Likes

Same, i give up. I will back to this sim in a few month i think. Too much unresolved issues since alpha/beta, not enough progress. And this patch is a regression so…no reason to be optimistic.
(sensivity can be adjust manually in the xml config files)

3 Likes

Well, thanks for the xml config file tip. Now to go hunting for it! Microsoft has the most. . . interesting file paths.

I’ve loved this game so far I just wish they could get their ■■■■ together on the weather and airliners.

For the sensitivity, it is always modifiable manually in the file which saves the assignments of keys
For those with MS Store version, in the folder C:\Users\youruser\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\

there are sub-folder, 1 contains the logbook, another the game parameters, and the others the assignments (1 folder per device). they are in an XML file (you just have to open the files with an editor like notepad ++ to find the right one (not the container.xx files but the others with full of letters and numbers).
In this xml file, go to section Axes and modify :
ex :

<Axes>
<Axis AxisName=“X” AxisSensitivy="-40" AxisDeadZone=“0”/>
<Axis AxisName=“Y” AxisSensitivy="-40" AxisDeadZone=“0”/>
<Axis AxisName=“rZ” AxisSensitivy="-69" AxisDeadZone=“0”/>
<Axis AxisName=“SliderX” AxisSensitivy=“0” AxisDeadZone=“0”/>
</Axes>

3 Likes

Do you know where this would be for the steam version with a custom package install location? I don’t have that long named folder at all in app data local. I’ve looked everywhere in the appdata folders, package folder, steam folders, program data folder.

No, i just know the path is different for steam version and my psot can’t be applicable to Steam version

This sim was released out of pressure. The market was perfect giving the COVID-19 pandemic world wide and a lot more people are social distancing and staying at home. If they waited longer they would have lost money. They saw an opportunity to capitalize and they took it knowing that the sim wasn’t ready. So basically what I’m saying is we paid to be beta testers :blush:

2 Likes

Beta ? no, where are in an Alpha phase in a development software pont of view :wink:

1 Like

:rofl: haha you’re right “Alpha”

I’d have to agree, this seems pretty alpha to me.

Unless they snippty snap fix it like that in a few weeks-months, then we’re paying to alpha test.

Hopefully I’m wrong, I have no reason to wish this sim to stay in this current state, I wish it had the functionality of Xplane 11 at MINIMUM plus what they already have in, I’d have NO complaints then.

As is it’s a ■■■■ shoot to start the plane up, take off, and land in one piece. I never had issues for decades in xplane or fsx

The XML’s on Steam version can be found in
C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\Input

Ok I found that folder (and have seen it before), but it only contains the default profiles for controllers, not the custom ones.

ok, non default config files for steam i found at:

those 4 marked files are for each device respectivly

1 Like

Fair comment but expecting a sim released last month to have the same polish as x-plane v11 that has been out and updated for several years was never likely.

My Patch Download stocks at 6,87GiB. Jumps always back to 0% after it reched 3% of the image. Tried to restart the game often, turned Antivir off, restartet pc. nothing helped.

1 Like

Trust me when I say this is not an Alpha experience. It has improved vastly but there are still many glaring issues that need to be resolved before I can truly call this a simulator. At this point it is strictly a game no matter how much I want it to be a proper simulator.

I also need to take a break form MSFS as it no fun right now with all the unresolved issues still pending, as far as I am concerned it is not flyable as it is.
Time to go back to my old reliable rock steady PD3 for now where you can still hand fly an airplane to instrument rated tolerances . I am still optimistic that MSFS at some point in the near future will be up and running as advertised, I realize it is a quantum leap in simulator technology but have trouble understanding why it was initially rushed into an early release date with all the bugs that became evident soon after, and it seems the same has happened with this latest patch!
Keeping my fingers crossed, happy landing y’all.

Yeah I stopped playing for now… The micro-stutter is terrible… Maybe I’ll try again (I just use turboprops now i’m not doing much with the jets until they are better)… just wish I didn’t sign up for the OnAir trial before this patch. I did see if you up the glass cockpit refresh to high it might help the stutter so maybe that’ll be a win. Going to try soon…

What issues with the TBM other than the incomplete G3000 and missing VNAV? I did several flights after 1.8.3 patch and had no issues with this particular plane.

Regarding the PFD jankyness, it’s due to the second item in the release notes:

New option available to control cockpit screen update frequency.

You probably have “Cockpit screen refresh rate”
on graphics options set to medium or low. Set it to high and it will be like before, at a CPU cost.