6 hours ago, Fielder said:

On steam the folder which holds the controller profiles (you read them with notepad) is something like:

C:\Steam\userdata\94959374\1250410\remote

Thanks for the info, but it seems to me that all Steam setups are not equal. I do have the remote folders but nothing related to "input_profile..." inside any of them.

I think the best choice for now is to "patiently" wait for Asobo to release the promised hotfix during this weekend (I suspect some newcomers here would say that it was not "promised"..., but anyway 😴) and more importantly, that it will be successful. I don't think this hotfix will be optional, so everybody will have to install it anyway. I also don't want to think that we'll need to employ those kinds of workarounds at every update release (how many would they still be?, fifteen, twenty of them?, who knows?).

Another clear conclusion out of all this mess is that MS/Asobo need to figure out a way to be more reliable in future patches/updates, and implementing an effective QA program from now on.

Cheers, Ed

It's not the testing .... it's what they do with the reported faults. Most of those from the 'huge beta testing team' were simply ignored.
I suspect that little has changed.

It is also not exactly clear how they could have a large number of patch testers busily beta testing a new patch while the rest of us still run the existing version, at least without running two separate and distinct sets of servers. 

3 minutes ago, keithb77 said:

It's not the testing .... it's what they do with the reported faults. Most of those from the 'huge beta testing team' were simply ignored.
I suspect that little has changed.

Maybe the whole process have to be revised entirely.

There's also at this time a lot of people having problems loading the community liveries (third party repaints) after the recent update, because something was not properly tested before release and a intended change was not announced, etc., who knows?.

Cheers, Ed

While waiting for the patch for Patch 5... as my KB and Mouse are plugged directly into the computer, and all my flight controls go through my powered Belkin Hub... I'm going to try and run the sim with just KB and Mouse.  Perhaps it will load fully and run, and then I will plug in the hub and see if it detects my HW... anyone else try this... has it worked?

Ta- C

1 hour ago, cavaricooper said:

While waiting for the patch for Patch 5... as my KB and Mouse are plugged directly into the computer, and all my flight controls go through my powered Belkin Hub... I'm going to try and run the sim with just KB and Mouse.  Perhaps it will load fully and run, and then I will plug in the hub and see if it detects my HW... anyone else try this... has it worked?

Ta- C

Carl, try it using the PSX and see if it will load.

No joy... as soon as I plugged in my hub, it found the new controllers in sim and CTD.

PSX always works fine!

C

where can i get the hotfix

4 minutes ago, ashepherd316 said:

where can i get the hotfix

lol

4 hours ago, edpatino said:

Maybe the whole process have to be revised entirely.

How do you revise that which doesn't exist? As far as I can tell, they have no discernable development and release process. This is not a team of software development professions. It's a bunch of guys doing cool stuff on their PCs.

5 minutes ago, odourboy said:

How do you revise that which doesn't exist? As far as I can tell, they have no discernable development and release process. This is not a team of software development professions. It's a bunch of guys doing cool stuff on their PCs.

Actually, it appears that they do have a release process and that's why it is causing red tape for them.  I suspect they have to go through a release process for Windows Store, and then another one for Steam.  And that's probably why they were hesitant to do a hotfix one to two days after their patch in the past because of the red tape.  Anyways, that's my best educated guess as I am a software developer myself.

Seems like they were willing to jump over the hurdle of the red tape and do a hotfix for this release. What they really need is a beta testing team again.  A beta testing team will help them immensely to detect these problems before they release the patch.

32 minutes ago, ashepherd316 said:

where can i get the hotfix

In the future. You'll need a DeLorean. 

20 hours ago, Will Fly For Cheese said:

Hope it's not mandatory - for those of us who don't have the CTD issue.

likely an update for all.... the update will be in a new version is my bet

2 minutes ago, abrams_tank said:

Actually, it appears that they do have a release process and that's why it is causing red tape for them.  I suspect they have to go through a release process for Windows Store, and then another one for Steam.  And that's probably why they were hesitant to do a hotfix one to two days after their patch in the past because of the red tape.  Anyways, that's my best educated guess as I am a software developer myself.

Seems like they were willing to jump over the hurdle of the red tape and do a hotfix for this release. What they really need is a beta testing team again.  A beta testing team will help them immensely to detect these problems before they release the patch.

Don't confuse process with packaging. But I agree on the testing side... a proper regression test suite should be applied to anything that goes out the door. If if we're, these blunders wouldn't be happening.

16 minutes ago, odourboy said:

How do you revise that which doesn't exist? As far as I can tell, they have no discernable development and release process. This is not a team of software development professions. It's a bunch of guys doing cool stuff on their PCs.

I think they surely have one, remember that is also MS not only Asobo behind this. In my opinion they need to improve their internal processes and take advantage of the experience of MS. Could you imagine this happening with a Windows 10 update?.

Let's hope this Update 5 will be a matter of the past after this weekend. And for Asobo, lessons learned I hope.

In the meantime, I'm back to my aging P3Dv4.5. At least it runs fabulous on my laptop.

Cheers, Ed