Impossible to do the AFCS start and get damper with Force Feedback, any clue ?

[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]

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 14 hours ago 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 14 hours ago 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 13 hours ago 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 13 hours ago 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.

[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 23 minutes ago by Tshark