Let's suppose there is a brilliant analyst out there who could fix everything fixable at this point.  How many really think all his or her work would not be ruined by the very next patch--and this tedious merry-go-round would begin yet again.

Speaking of which--anyone who cannot distinguish an "announcement" from a "patch" and refers to both using the same word (i.e. "update") is either hopelessly confused or trying to hide the fact that they clearly don't have a clue about how to fix this thing.  If recent history confirms anything--it is that.

The past two months have offered next to nothing to simmers --but a great deal to those who enjoy troubleshooting hardware and software issues.  I have nothing against the latter--in fact I marvel at your patience and the amount of free time at your disposal.

Asobo needs to stop spending their time "updating" (in both senses of the word),  take a break, and get whatever outside help they need.  Then they can let us know when, if ever, this thing is actually ready to be used as a flight simulator.

Given the amount of money they have already collected from the community, another installment of this nonsense in a week or two would really be even more insulting.

 

8 minutes ago, TASCHMANN said:

Let's suppose there is a brilliant analyst out there who could fix everything fixable at this point.  How many really think all his or her work would not be ruined by the very next patch--and this tedious merry-go-round would begin yet again.

Speaking of which--anyone who cannot distinguish an "announcement" from a "patch" and refers to both using the same word (i.e. "update") is either hopelessly confused or trying to hide the fact that they clearly don't have a clue about how to fix this thing.  If recent history confirms anything--it is that.

The past two months have offered next to nothing to simmers --but a great deal to those who enjoy troubleshooting hardware and software issues.  I have nothing against the latter--in fact I marvel at your patience and the amount of free time at your disposal.

Asobo needs to stop spending their time "updating" (in both senses of the word),  take a break, and get whatever outside help they need.  Then they can let us know when, if ever, this thing is actually ready to be used as a flight simulator.

Given the amount of money they have already collected from the community, another installment of this nonsense in a week or two would really be even more insulting.

 

way way to negative, no issues here right from the start.

easy solution, stop flying this one, if you cannot handle it.

also amasing to see how much more positive the ppl on the reddit forums are.

happy flying.

 

Edited October 30, 20205 yr by Tuskin38

31 minutes ago, wim123 said:

way way to negative, no issues here right from the start.

easy solution, stop flying this one, if you cannot handle it.

also amasing to see how much more positive the ppl on the reddit forums are.

happy flying.

I noticed that as well and on the MFS forum. I wish that when

negative issues are reported we all had a clearer database of numbers between

satisfied and unsatisfied members. Things would be a lot clearer and at a guess

more positive.

The default A320 also seems to have picked up some bugs which weren't there previously.

Like the 747 it also now suffers from the spinning dial syndrome, when tuning the knobs on the AP Panel. A couple of clicks and the knob continues to rotate on it's own.

Also having been settled in a steady flight under AP, all of a sudden I just started wallowing with the wings dipping from side to side. No explanation - the aloft winds had not changed and I hadn't touched anything, just erratic behaviour.

22 minutes ago, Elvensmith said:

The default A320 also seems to have picked up some bugs which weren't there previously.

Like the 747 it also now suffers from the spinning dial syndrome, when tuning the knobs on the AP Panel. A couple of clicks and the knob continues to rotate on it's own.

Also having been settled in a steady flight under AP, all of a sudden I just started wallowing with the wings dipping from side to side. No explanation - the aloft winds had not changed and I hadn't touched anything, just erratic behaviour.

Play with sensitivity settings I have no idea what Im doing with them lol but moved them around a bit and bus starting working properly 

Edited October 30, 20205 yr by Richard Sennett

10 hours ago, bobcat999 said:

I just don't understand this.  My Saitek throttle is plugged in to a (cheap-ish) hub, and has customised settings on the levers (for reverse etc.) and on all of the buttons below the leavers (for pause, release parking brake etc.) and absolutely no CTD's - a flawless update.. 

How can people have such different experiences? There must be something deeper going on here than just using hubs or certain USB peripherals. 😕

You're right, how can people have such different experience? And how can Microsoft let a release out with such problem?

You know what I saw on another forum? A guy has a HOTAS Warthog (top-notch hardware) and on his system, the Cessna keeps circling when taxiing. He realized the sim "believes" the left brakes is always active so the left wheel is blocked when taxiing. His hardware was working perfect before this update.

I had high hopes but this last one has really messed up my experience. I read all about how the control sensitivities have changed so went in and checked all mine before even trying a flight. I use a Honeycomb Alpha + CH Pedals + CH Throttle Quadrant. I tried 2 flights, one with the 152 and another with the 172 G1000. Both flights resulted in same behavior. I cannot seem to get full throttle enough to climb and could not achieve any semblance of level flight. 1152 kept going up and down and right and left. 172 was the same even trying to engage the AP. That just killed all the speed until it stalled. offensive initials not allowed?

Yes, all controllers have been recalibrated in Windows before even attempting a flight. 

6 minutes ago, Mikeingreen said:

I had high hopes but this last one has really messed up my experience. I read all about how the control sensitivities have changed so went in and checked all mine before even trying a flight. I use a Honeycomb Alpha + CH Pedals + CH Throttle Quadrant. I tried 2 flights, one with the 152 and another with the 172 G1000. Both flights resulted in same behavior. I cannot seem to get full throttle enough to climb and could not achieve any semblance of level flight. 1152 kept going up and down and right and left. 172 was the same even trying to engage the AP. That just killed all the speed until it stalled. offensive initials not allowed?

Yes, all controllers have been recalibrated in Windows before even attempting a flight. 

I have the exact same controller setup and it's working perfectly after the last update, I did not have to touch any of the calibrations.

Do you have a controller bound to the mixture axis?  Too lean a mixture would explain your lack of power in the C152/C172.   You might have to move the mixture lever back and forth once even if it's in the full rich position to get it to sync to the controller position.

11 hours ago, bobcat999 said:

I just don't understand this.  My Saitek throttle is plugged in to a (cheap-ish) hub, and has customised settings on the levers (for reverse etc.) and on all of the buttons below the leavers (for pause, release parking brake etc.) and absolutely no CTD's - a flawless update.. 

How can people have such different experiences? There must be something deeper going on here than just using hubs or certain USB peripherals. 😕

 

22 minutes ago, Rocky said:

You're right, how can people have such different experience? And how can Microsoft let a release out with such problem?

You know what I saw on another forum? A guy has a HOTAS Warthog (top-notch hardware) and on his system, the Cessna keeps circling when taxiing. He realized the sim "believes" the left brakes is always active so the left wheel is blocked when taxiing. His hardware was working perfect before this update.

Because I don't think it has to do with any particular hardware but rather the controller profiles they are using.  A "null" profile is one you create when you copy an existing profile and remove all assignments.  Some people use these to switch between two controllers so that they won't conflict.  Others using FSUIPC will use them to create a profile that can be hooked to FSUIPC.  

These null devices all have one thing in common, they don't have any "button assignments", and it appears the lack of the presence of those xml tags is what causes the CTD, based on my limited testing.  Version 1.9.5 didn't have a problem with these files.  This version does.

Bottom line, if your controller profile had at least one button assignment, you were good.  If your controller profile didn't have a button assignment, but was not the active profile, then you were also good to go until you tried to change to that profile.  If your controller profile had no button assignments AND it was the active profile, you CTD'd before the program loaded. (lucky me)

I posted a fix for this in another thread here which adds some xml tags that prevents this from happening, but at this point it's probably easier to wait for the hotfix.

Edited October 30, 20205 yr by wthomas33065

Haven't "flown" MSFS in a while (unsure if I even did during the last patch) as I've been "working" in the QW787 (P3dv5) for my company in OnAir, but did a test flight in MSFS today from DTNH to LMML in the TBM.

My takeaway: Worked flawless. Good performance. No CTD and looks that make every other sim look like 1995. 

On 10/29/2020 at 11:55 AM, ankh21 said:

Mh, i can't download from the store, it always says: Code: 0x80070141 😭

I found this online, and it worked for me.

https://www.reddit.com/r/XboxGamePassPC/comments/io1ur4/heres_how_to_troubleshoot_if_you_have_problems/

I used the method from a comment post from "zockmotte" down the page a bit.

 

7 minutes ago, N7470 said:

I have the exact same controller setup and it's working perfectly after the last update, I did not have to touch any of the calibrations.

Do you have a controller bound to the mixture axis?  Too lean a mixture would explain your lack of power in the C152/C172.   You might have to move the mixture lever back and forth once even if it's in the full rich position to get it to sync to the controller position.

Yes, I have a lever bound to Mixture. That was my first thought on the can't climb issue. Verified in the sim that it is indeed working as assigned but that wasn't it. If I pulled it back too far it died just like it should. I have always had all the axis on all 3 controllers at 0% Sensitivity and that is where they are still set. This thing is just a wreck now and I don't see the Hotfix for the CTD fixing that.

11 minutes ago, Mikeingreen said:

Yes, I have a lever bound to Mixture. That was my first thought on the can't climb issue. Verified in the sim that it is indeed working as assigned but that wasn't it. If I pulled it back too far it died just like it should. I have always had all the axis on all 3 controllers at 0% Sensitivity and that is where they are still set. This thing is just a wreck now and I don't see the Hotfix for the CTD fixing that.

I just did a quick takeoff test from SAN in the 152.  Power was normal and was able to climb at 500 fpm with no problems. 

There are two options for mixture axis.  I am using "mixture -100 to 100" on the "engine 4" lever on the CH quadrant.   The other option is "mixture 0 to 100" which I don't think works right on this controller.

I also have all the toggle and magneto switches unbound on the Alpha and am not using FSUIPC at all if that helps.

26 minutes ago, Swe_Richard said:

...and looks that make every other sim look like 1995. 

It really is a massive leap. MSFS literally sucked the air out of the industry. But...they have a long way to go. And that is the only hope P3D and XP have. They have time, but they have Mount Everest to climb. Should be a fun year watching how they respond to the juggernaut that is MSFS.