Force Feedback Centre Pressure Broken, all variants unflyable now.

[Phantom_Mark]

Force Feedback Spring Centre Pressure broken on both variants of the Mirage on the latest release, neither are flyable as a result now.

In other words, for those who don't use a FFB and wonder what all the fuss is about, there is no longer a force which keeps the stick sprung in the centre, which means the stick flops around all over the place and unusable,  the Mirage sadly has never had proper FFB implementation but this basic level of functionality is actually required for the hardware to be at all compatible with this module.

Stick and FFB still works as expected on other modules in this release.

Test Stick: Microsoft Force Feedback 2

F1EE release / Update  25/1/23

[MAXsenna]

Force Feedback Spring Centre Pressure broken on both variants of the Mirage on the latest release, neither are flyable as a result now.

In other words, for those who don't use a FFB and wonder what all the fuss is about, there is no longer a force which keeps the stick sprung in the centre, which means the stick flops around all over the place and unusable,  the Mirage sadly has never had proper FFB implementation but this basic level of functionality is actually required for the hardware to be at all compatible with this module.

Stick and FFB still works as expected on other modules in this release.

Test Stick: Microsoft Force Feedback 2

F1EE release / Update  25/1/23

This is actually strange as FFB works so well in the C-101.
Hope this gets fixed soon. But there were some mentions of FFB implementation in the changelogs.
They didn't add some options in the special menu by chance?

Cheers!

Sent from my MAR-LX1A using Tapatalk

[Phantom_Mark]

Sadly not, I did check as well.

[MAXsenna]

Sadly not, I did check as well.

That's a bummer, was gonna test AAR tonight.
Oh, well. This happened after another previous patch as well, didn't it?
Hopefully an easy fix.

Sent from my MAR-LX1A using Tapatalk

[SlipHavoc]

I noticed this as well after this most recent patch, force seems very weak, with little or no centering spring.  I haven't messed around with it much, but I did try with the FFB emulation checkbox in the Special tab in Options both checked and unchecked, and in both the F1CE and F1EE, and it seemed to be the same in all conditions.

 

Edit: Of course right after I posted this, I found a reply in the main Bugs forum that says it's fixed internally and should be out in the next patch:

 

Edited January 26, 2023 by SlipHavoc

[Phantom_Mark]

4 hours ago, SlipHavoc said:

I noticed this as well after this most recent patch, force seems very weak, with little or no centering spring.  I haven't messed around with it much, but I did try with the FFB emulation checkbox in the Special tab in Options both checked and unchecked, and in both the F1CE and F1EE, and it seemed to be the same in all conditions.

 

Edit: Of course right after I posted this, I found a reply in the main Bugs forum that says it's fixed internally and should be out in the next patch:

 

 

Ironic I moved my post from the main bug forum to the correct "controller bugs" forum and they never replied here tho right ?

At least its potentially fixed now, with any luck they will get around to implementing some more FFB features soon as well, this old airframe is more than deserving, the Tomcat is a delight with its more proper and fully featured FFB implementation.

Edited January 26, 2023 by Phantom_Mark

[Vibora]

FFB is fixed internally. It will be available in next update.

[Phantom_Mark]

On 1/27/2023 at 8:40 AM, Vibora said:

FFB is fixed internally. It will be available in next update.

In case I missed it, have we any idea when the update with a fix might be rolling out ?  ty

[MAXsenna]

In case I missed it, have we any idea when the update with a fix might be rolling out ?  ty

Next OB is early March.

Sent from my MAR-LX1A using Tapatalk

[Phantom_Mark]

That sucks when you have a bug which renders something completely unusable for more than a month   It is what it is I guess, thanks for the heads up.  

[MAXsenna]

That sucks when you have a bug which renders something completely unusable for more than a month   It is what it is I guess, thanks for the heads up.  

Yeah, I agree! But to be fair, ED sets the dates for patches, not Aerges.
According to rumours, the next patch will be huge, and users are speculating we will finally be getting multi-threading.
It also means that all devs have a whole month to focus on other bugs etc.
So just let's be positive!

Cheers!

Sent from my MAR-LX1A using Tapatalk

[Phantom_Mark]

On a positive note its giving me a chance to setup my new VR headset properly in prep for other cool stuff that is coming, so yes, all is not lost

[Phantom_Mark]

Have we any idea when the patch drops out of interest, literally been weeks and weeks since I have been able to fly these planes ? 

[MAXsenna]

Have we any idea when the patch drops out of interest, literally been weeks and weeks since I have been able to fly these planes ? 

Nope! But I've seen users asking for hotfix patches from 3rd parties, not related to the upcoming patch.
A reasonable request if you ask me.

Sent from my MAR-LX1A using Tapatalk

[Phantom_Mark]

Selfishly I have to concur, for an absolute game ending bug like this it is maybe unreasonable to be denied use of the product for maybe 4 - 6 weeks when  mid term hot fix might resolve small but game breaking issues like this ?

 

[erniedaoage]

Yeah but people with forcefeedback sticks are a minority in the flightsimmarket. I bought the F1 on release, but i wasn't able to fly it till the last patch and now its broken.  

 

[Phantom_Mark]

@NineLine In extreme cases like this, where something is terminally broken immediately after a patch, as in this case, is there not a way third parties can get a hotfix out, it doesn't feel like an unreasonable request when you consider there is people who are literally unable to use their content for way past a month now ?