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.

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

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.

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)

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.

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

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 !

indeed. especially in head on passes. I only ever lock bombers attacked from the side

hopefully it gets adressed. this is an immersion killer

+ 1 I made another thread about it. it's killing immersion

Question. when trimming my plane on the elevator axis, the stick doesnt move like in any other warbird. The trim tab should move and that should have an effect on the stick depending on the airspeed. right now the trim acts directly on the control surface. this is wrong Is this a bug ? A missing feature ? thanks

my issue is specific to the FFB beast apparently. by resetting, I mean deleting these entries (045B ports (vendor ID)). they will be created again once you restart your computer. done with this software : USBDEVIEW

fixed. if you ever have that issue, its a USB issue that needs to be adressed by resetting some specific USB's with USBDEVIEW. all 045B ports (vendor ID)

I cant get any force feedback from my FFbeast anymore.. that is the Standard DirectX FFB from the game. All the force feedback I get from the telemetry of DCS works, but what should come native from the game is gone. Any idea what happens ? Happened to somebody else before ? Thanks

in that case we ALSO need some shaking of the cockpit.. this is too static

is that normal ? no matter the setting, you get no vibration/shaking of the cockpit

after 90min on contention Cold War server tonight.. All cores where throttled at least once. dcs.log

thank you for the heads up anyway!

forget about my sign. this was before my intel CPU died 1 year ago. I am now running the Intel safe BIOS and settings, since they clearly have issuee with gen13/14 CPUs

I confirm this happening with Intel, non OC. 13900k here. I have a 14900k sitting in a box in case this one burns away. Yes yes. don't worry. My old CPU intel died because of this about a year ago. It's been replaced by intel, and I am now running it with latest BIOS and safe setting (at a loss of performance of course). I even have a 14900k that is sitting on the side that I bought until my 13900k would be replaced. Clearly there is an issue with the latest patch. never had such high temps since I updated the BIOS with the new intel 'safe' settings I have no log to report, as I have no crash myself. just very high temps

please go read the dedicated thread i linked.. Most people have this. Plenty documented I dont want to run DCS until it pushes my CPU at 100°.

crazy indeed

that aint serious (that was just loading Cold War Contention server. not even going 3d) :

read my edit of the post before.. we had peak at 100° and average at 95°....

friend had 3 freezes and blue screen tonight after the patch. prolly temp linked too. myself my CPU had peaks at freaking 100° !!!! and was idle in the mid 90°s I dont want to burn another intel CPU... Not playing DCS tonight anymore. Come on ED; this is not serious