fixed internally for next update Impossible to do the AFCS start and get damper with Force Feedback, any clue ?

[Psifire]

This is the same issue that is posted with the Moza AB9 and a few other FF joysticks, but the solutions for the AB9 doesn't work for the Sidewinder so I think we need a new topic.

 

Symptoms:  Autopilot BIT fails when a Sidewinder Force Feedback 2 joystick is plugged in and Force Feedback is enabled. Ekran BIT was successfully completed, and AFCS switch was activated after alignment and startup.  Hands are off the stick.  BIT starts and then all buttons on autopilot panel immediately start flashing green when it detects input.  I've followed several different suggested procedures for startup, and all result in the same thing.  I get to the Autopilot BIT, it starts and then immediately fails, I'm guessing because it detects joystick input from the sidewinder.

Is it Reproduceable?:  Yes

Solved by disabling Force Feedback, but of course we need a better solution than that.  I can post a track if you need one, but it seems pretty clear that having an option to disable control inputs during autopilot BIT would solve a ton of problems for people with FFB joysticks.  I'm a bit shocked it never occured to you that this would be an issue.

Edited because I was using the wrong Abbreviations.  I just got the control labels mixed up, it is correct now.

Edited September 20 by Psifire

[Psifire]

Just went in and tested, and I can complete the AFCS test and get the Damper warning light to go off if I unassign my Sidewinder FFB2 from the pitch and roll axis, so definitely being caused by the Sidewinder.  Wouldn't this test fail with any controller that was getting a tiny bit of almost imperceptable axis jitter as well?  Yeah, need an option to disable controller inputs during BIT.

[ARM505]

VPForce Rhino worked first time, no issues. Strange. I just let the stick wander around doing it's thing and it all worked.

[FZG_Immel]

Ive been trying to complete a proper cold start, and with my FFBeast base, I am totally unable to obtain a DAMPER OFF light to go off..

 

any clue ?

 

anywhere where this is addressed ?

 

thanks !

[MAXsenna]

Anyone have a solution for the Sidweinder FFB2?  It's having the same issue, but the solutions above don't work. 

For my MS SW FFB2 I have to swap axis in all modules.
Open control settings. Click on the FFB2 column, click the FFB tune button on the bottom. Then click swap axis.

Cheers!

Sent from my SM-A536B using Tapatalk

[MAXsenna]

Ive been trying to complete a proper cold start, and with my FFBeast base, I am totally unable to obtain a DAMPER OFF light to go off..
 
any clue ?
 
anywhere where this is addressed ?
 
thanks !

Have you set the correct FFB axis? It seems that's an issue for some.

Sent from my SM-A536B using Tapatalk

[FZG_Immel]

of course. everything works fine with a hot start or with a air start

 

thx

Edited September 20 by FZG_Immel

[Raven (Elysian Angel)]

It might also have to do with your specific settings in whichever software FFBeast uses. I had issues with trimming in the F-4 and F-14 with my Rhino until I finetuned the settings - but it took a while for me to fully understand how the software works. It might be something related to either too much spring force or too little, or too much friction counteracting the spring force.

 

All I know is that is works fine for me, but others have reported issues with it too, using a FFB stick. If I were you, I’d check the settings in the FFB software.

Edited September 20 by Raven (Elysian Angel)
Autocorrect is the worst!

[FZG_Immel]

I understand what you mean. But I have no issues with any other airplane.

My understanding is that MAYBE, some FFB setting from the telemetry, that I am using on top of the DCS FFB from directX is preventing the autotest from the AFCS to go to the end...  

 

I guess I should just start with no effects from telemetry and add them one by one.

 

But again, I have NO issues trimming the Mig-29.. its just that it cannot run the AFCS test to the end, such as the dampers never kick in.

Edited September 20 by FZG_Immel

[Raven (Elysian Angel)]

5 minutes ago, FZG_Immel said:

But again, I have NO issues trimming the Mig-29.. its just that it cannot run the AFCS test to the end, such as the dampers never kick in.

My suspicion is that the the AFCS test uses the trim system in the background. That’s why I brought it up: if something interferes with trim forces somehow, it may prevent the test from successfully completing. But perhaps I’m mistaken. Did you try trimming to neutral and then hitting the AFCS OFF switch on the stick, as the training mission suggests in case of test failure?

 

I had no issues with other modules either, but trimming in the F-4 felt weird until I fixed the settings I was referring to, and it also helped the F-14.

In fact, it even made some helicopters easier to fly.

[FZG_Immel]

5 minutes ago, Raven (Elysian Angel) said:

My suspicion is that the the AFCS test uses the trim system in the background. That’s why I brought it up: if something interferes with trim forces somehow, it may prevent the test from successfully completing. But perhaps I’m mistaken. Did you try trimming to neutral and then hitting the AFCS OFF switch on the stick, as the training mission suggests in case of test failure?

 

I had no issues with other modules either, but trimming in the F-4 felt weird until I fixed the settings I was referring to, and it also helped the F-14.

In fact, it even made some helicopters easier to fly.

yes, I have tried. same result

you are right and maybe onto something though. Because If I use a FFB profile that I use with the F-4, the AFCS test moves the stick (physically, in game and IRL , but only back and left). If I use a Mig-29 profile I created , based on the F-4 profile but with only 60% of the force applied, then the stick doesnt move at all. So clearly the FFB software and certain settings are influencing that AFCS test and its failure. 

I think I will create a profile with NO effects at all, and try the AFCS test.  if that works, i can always switch to profile for flying afterward (I can easely switch profiles in game)

Edited September 20 by FZG_Immel

[Raven (Elysian Angel)]

3 minutes ago, FZG_Immel said:

I think I will create a profile with NO effects at all, and try the AFCS test.  if that works, i can always switch to profile for flying afterward (I can easely switch profiles in game)

It’s way past midnight where I live, and I’m about to go to bed, but if it helps I can check tomorrow in my profiles and let you know what exactly is different in my F-4 and MiG-29 profiles.

I have a “up to third gen jet” profile which I use for the F-4, Mirage F1 and as you might have guessed, all other jets up to third gen.

For MiG-29 I use my “fourth gen non-FBW” profile, which I also use for F-15E for example.

[Psifire]

3 hours ago, MAXsenna said:

For my MS SW FFB2 I have to swap axis in all modules.
Open control settings. Click on the FFB2 column, click the FFB tune button on the bottom. Then click swap axis.

Cheers!

Sent from my SM-A536B using Tapatalk
 

That helps with the FFB forces being applied wrong, but not with this issue.  This happens when you are trying to cold start the aircraft and you do the BIT for the autopilot.  The game detects joystick inputs and fails because in the real aircraft you can't move the stick during this process.  The only way to get it through the Autopilot BIT successfully is to erase the axis assignments for the joystick then remap it when it's done.

[VANOIS]

Unfortunately, erasing the axis doesn't help me, only physically disabling the joystick

[VANOIS]

I have attached the track, I hope it will help fix the problem sooner

Островная разборка-20250920-132221.zip

[Raven (Elysian Angel)]

OK I'll show you my settings for comparison. Keep in mind I have different hardware, a different setup and likely a different grip and different extension. Your mileage may vary etc etc.

The 'Effects' tab are (for me) global settings that I keep consistent across all profiles, but I may untick "Friction" for some profiles, such as my FBW profile. Ignore "Static Force": that's because my grip is offset from the centre of the base, so I need a bit of constant force in pitch away from me to prevent sag.

The 'Settings' tab are modifiers that are calculated at the end of the equation that determines how much force is exerted by the FFB motors. The first screenshot (the one with 50% spring force) is my 3rd gen profile, and the other one (with 40% spring) is my 4th gen profile.
I keep all forces at a lower level with more modern aircraft because you tend to throw them around more often, whereas with 3rd gen and older you need to be a lot more deliberate and careful with your inputs. Higher forces that you throw around more often equals more heat generation, and I want my hardware to last a long time so I take care of it.

But generally, the things you need to be careful with are primarily Friction and Inertia, because they work in the opposite direction of other forces. Wrong settings can cause oscillations and even damage the motors. If I have Friction set to 10% in 'Effects' and 10% in 'Settings', the total amount of Friction is just 1% because 'Settings' are global modifiers at the end of the calculations. I wouldn't go above 2% personally. 1% and 1.5% are very noticeable and plenty to do the job.

What helped me the most is 'Adaptive Recentring' in the 'Effects' tab: that needs to be at 100% or it won't have enough authority. That 100% means 100% of whichever spring force is exerted at any specific moment, so that's less around the centre position, and more as you pull Gs. It's also more with higher global modifiers. 100% of very little is still very little, but it might just be enough to do the job.
I'm aware that Moza software is basically a copy of VPForce's software, but it might work differently for FFBeast. You might not have all of the configurability that I have, or perhaps you have more...

Good luck!

[Tshark]

I have an FFBeast and had the same issue.  I was using an F-14 profile modified for the MiG-29.  I switched profiles to the MiG-29 profile from "JustFlyIt" (you can find it on the FFBeast website).  Now the AFCS BIT test works great and the MiG-29 flies much better.  When I get some time I will compare profiles and find out what the differences are.

Edited September 21 by Tshark

[FZG_Immel]

i have this profile. I will test it

 

RAVEN, thanks a lot for your detailed answer. I used to have a rhino before the FFbeast, so I will try to compare profiles, and see which setting is causing the issue.- 

 

Tshark, let me know if you figure it out.

 

My profiles are highly tweaked to produce a lot of AoA/stall effects and such. so i'd like to keep using them while finding whats creating the issue.

[FZG_Immel]

2 hours ago, Tshark said:

I have an FFBeast and had the same issue.  I was using an F-14 profile modified for the MiG-29.  I switched profiles to the MiG-29 profile from "JustFlyIt" (you can find it on the FFBeast website).  Now the AFCS BIT test works great and the MiG-29 flies much better.  When I get some time I will compare profiles and find out what the differences are.

I tried this profile, but with me the stick started shaking more and more (violently) during the AFCS check. 

 

I will try removing the stick axis from the controls to see it if works

 

EDIT: yes, when I remove the Roll and Pitch axis from my FFbeast column, in adjust control, the AFCS test goes to the end and I get damper off lights to go away. 

 

So it defintely comes from a setting of the FFBeast setting.

 

which is strange, because in the FFBeast setting, if I only leave the Dirext X Standard FFB effet for both elevator and aileron axis, it still doest work...  must but a setting within this too... either periodic effect strenghts, spring effect strenghts, or even trimmer effect strenghts

Edited September 21 by FZG_Immel

[Raven (Elysian Angel)]

1 hour ago, FZG_Immel said:

so I will try to compare profiles, and see which setting is causing the issue

Keep in mind there's not just the amount of force for each effect, but also the frequency at which they occur. I tend to not touch these settings, but my current 'Low Pass Output Filters' are suggested by Walmis himself so I'm using those.

[FZG_Immel]

I am onto something.  I managed to get the ACFS to work, but it implied some very specific settings, even with the JustFlyIt profile for the Mig-29 ...

 

basically those in red, and more specifically prolly those in yellow (only showing elevator here, but assume same setting for ailerons)

i have tried using these setting with my personal profile, but not only this is way too strong, but also some other settings seems to interfere. 

 

As a temporary solution, I now simply cold start with this profile, and switch to my favorite profile as part of my take off check list. 

It would be great if ED implemented an option to simply exclude the FFB interaction with the AFCS test though, because this get very complicated.

for example, in the instant action  cold start there is some wind (24kmh) that in my FFBeast telemetry also causes the AOA to go from -5 to +20 degree...  since I have some effects linked to the AOA stall shake, this also creates some force in the stick on the ground, prolly making the AFCS auto test to fail.

 

 

[sith1144]

heres my track, with a vpforce Rhino. at some point I slightly open the canopy and close it again, after that I run an AFCS bit with master gain (FFB strength) at 0, then one at 100, then one with it fully off, then another couple at 100%. At no point does the AFCS align.

is what I would say if the track wasn't too big? its made with the startup tutorial mission, and its 152MB and I have a limit of 50. uhh, it should be available here for 7 days https://limewire.com/d/po67L#wWstxlXvdL

[MAXsenna]

That helps with the FFB forces being applied wrong, but not with this issue.  This happens when you are trying to cold start the aircraft and you do the BIT for the autopilot.  The game detects joystick inputs and fails because in the real aircraft you can't move the stick during this process.  The only way to get it through the Autopilot BIT successfully is to erase the axis assignments for the joystick then remap it when it's done.

Ah, so in the real aircraft the stick doesn't move during the test?
No wonder why it fails then.

Sent from my SM-A536B using Tapatalk

[Explicable]

On 9/18/2025 at 10:29 AM, Wags said:

Probably not, but without a track, we cannot know. This is not something we can reproduce.

Literally every person I know has problems with AFCS, including me. And instead of always asking for a track, QA should be adhoc testing it like a natural user. Do multiple flights, land, shut down engines, repair, then try to turn afcs back on... it doesnt work. 

[sith1144]

here's another go in the instant access scenario, to get a shorter track. first 2 attempts are at 100% stick gain/power, then 0%, then 50%

Edit: oh and I only touch the stick to neutralize trim, I don't touch it while afcs calibrates itself

mig-29 AFCS problems.trk

Edited September 22 by sith1144