Yeah, I don’t get how it is so unreliable for some. There is obviously a difference between their system and ours. I’m not saying it is their fault but in the end if you look at the number actually flying then clearly very few have an issue updating.
Unfortunately I know of no way to help those people without remoting to their machines and I certainly won’t be offering that.
Strange, my TQ6+ is working properly. I just had a look in it’s text file, and I see the following:
It doesn’t look like this is using the new format, but it is working. I can’t run the sim right now, so I can’t say for sure if this is the active profile or not, but it works fine.
My rudder, and yoke, are in the new format, with two sensitivity options as well as the neutral one.
I suspect that the reason it is still in the old format is it is the only one that is not using a default profile. I created this one when I was messing around with getting SPAD to control the throttle instead of MSFS, so I could properly map reverse thrust. It never worked out well, not going into full reverse for some reason, and I didn’t spend much time on it, and just disabled it in SPAD. But the profile remains.
What a puzzler. I’m going to try running the VF software standalone and work on the throttle and see if that will fix it. I’m also going to try a different usb hub. My system has worked fine up until today’s update with all of it. I have an I9-9900K, 64GB ram, RTX 2070S, SSD drive, reasonably fast internet connection, 4K HDR Monitor. On the latter, HDR has now returned with this update, and the screen looks spectacular again. I seemed to have lost the ability to use HDR functionality in the prior update (when HDR was set, it looked washed out), but it is back now. There must be a combination of user error and odd software/hardware interactions at play here with the updates, which is I know is frustrating to lots of people. My only comment is that if it hasn’t happened to you yet, it might at some future date, perhaps even without any user error (although that is always a possibility).
Mark
Tomorrow I will back up that entire folder structure, then have a go at resetting the profile for the throttle to default, confirm the file is changed to include the new attributes, then try launching it again.
In theory if I do have an issue, I may be able to simply restore that folder with the sim shut down.
I’ll let you know how I get on tomorrow.
I just reinstalled the VF software, re-ran Spadnext as admin to ‘recalibrate’ the usb ports, and again had a CTD when the TQ6+ was plugged in. I unplugged the TQ6+ and MSFS loaded normally. Then, while MSFS is runnning, if I plug the TQ6+ in, it says, new hardware detected, and immediately then crashes to the desktop. So there is something new related to the TQ6+ that is causing an issue for my system. It seems like there are a variety of peripherals that are causing this for others, not the same one for all. I am going to let VF know about it so they can check into it as well. Let me know what you find.
EDIT: the issue for me was having a ‘null’ profile in the throttle to allow for features like reverse thrust that the default profile did not. Removing the null profile and using default allowed the sim to run under 1.10.7.0.
The only issue I had was poor FPS after install. I had to restart everything and it seems to be ok so far. Downloads and installs have never been a problem for me. Even back in Alpha
Smooth install as usual (knock on wood), took 9.38 min all in all. Reduced fps but not that much as first thought as vfr map was opened in pop out mode ad switching this off gained 5-7 fps.
Same abrupt tbm AP behaviour as above.
Nothing in community folder or mods and there wont be for next 6-12 months. MFS solo on new PC (no other games, programs, apps). All other windows business on seperate PC.
same here, plain sailing and installations since beta, and it’s SMOOTH. stock systwm, not tweaked, windows updated regularly. 
yup, ditto. removed community mods with every update, always same pc system, never overclocked,/fiddled with, been going good and smooth since beta!
No you are not lucky. I had a smooth upgrade as well and the new AA and night lighting is fantastic. Remember someone is more likely to post if something is wrong and not when everything is fine.
You are correct, but just because people post a problem doesn’t mean it isn’t real, or is because they are inept. It is complicated software, and things that work pre-update sometimes don’t afterwards, and it requires work to fix, that is facilitated by getting input from other similarly situated users. I have had no problems until this last update, and haven’t changed anything in my system during that time. I have a higher end system, and understand computers and software. As I noted above, a profile for one of my peripherals caused the problem here, and I have corrected it. I don’t take your comment as critical of those who do have problems, but there are many who immediately assume those who have problems are making them up or are idiots.
I hope you all continue to have no issues going forward.
Mark
