FFB died while flying

This has been a rather seldom issue before the last 1.5.4 update, now it seems to occur more often. Namely, the FFB dies, which forces to restart DCS. I should mention that it has currently only died for me when I was in FW-190D9. Used to go out in BF-109k4, su25T (haven´t tested this one for a long time now) sometimes as well (before 1.5.4).

dcs.log.zip

FFB has been mostly missing for me with the release of 1.5.4 today. Flying P-51 offline and online. Only once did I have it out of four game starts and even then it was all over the place and didn't register stalls properly and just gave random pulsed feedback even when flying straight and level.

Well I wasn´t that unfortunate luckily, but it should certainly be fixed. Maybe you could attach your log file so that ED has more resources for eliminating the issue?

I've been having this problem with 1.5.4 also.

FFB will die randomly, and I have to exit DCS and unplug/replug the controller to get it to come back. The controller is still recognized and the axes work, just no forces.

I tried skipping my USB hub and going straight to the computer, and messing with power settings, but I couldn't get it to stop disconnecting.

Just tried the 109 - there were forces but overall it seemed to be wrong or feel different than in 1.5.3 and I also was missing the shaking / buffeting.

MSFFB2 here.

dcs.log.rar

I have the same problem with 1.5.4, force feedback works fine till suddenly it stops and the stick is soft. i'm flying with Microsoft force feedback 2.

I have the same problem with 1.5.4, force feedback works fine till suddenly it stops and the stick is soft. i'm flying with Microsoft force feedback 2.

+1

Exactly the same experience here. Also using MSFF2 stick.

S!

09166.509 INFO INPUT: Device [Keyboard] created deviceId = 6

09166.554 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}] created deviceId = 7

09166.554 INFO INPUT: Joystick created[sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}

09166.585 INFO INPUT: Device [Keyboard] created deviceId = 8

09166.630 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}] created deviceId = 9

09166.630 INFO INPUT: Joystick created[sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}

09166.647 INFO INPUT: Device [Keyboard] created deviceId = 10

09166.690 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}] created deviceId = 11

09166.690 INFO INPUT: Joystick created[sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}

09168.354 INFO INPUT: Device [Keyboard] created deviceId = 12

09168.398 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}] created deviceId = 13

09168.398 INFO INPUT: Joystick created[sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}

09168.427 INFO INPUT: Device [Keyboard] created deviceId = 14

09168.470 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}] created deviceId = 15

09168.470 INFO INPUT: Joystick created[sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}

09168.510 INFO INPUT: Device [Keyboard] created deviceId = 16

09168.558 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}] created deviceId = 17

09168.558 INFO INPUT: Joystick created[sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}

09210.374 INFO INPUT: Device [Keyboard] created deviceId = 18

09210.452 INFO INPUT: Device [Keyboard] created deviceId = 19

09217.067 INFO INPUT: Device [Keyboard] created deviceId = 20

09217.075 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}] created deviceId = 21

09217.075 INFO INPUT: Joystick created[sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}

09217.129 INFO INPUT: Device [Keyboard] created deviceId = 22

09217.136 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}] created deviceId = 23

09217.136 INFO INPUT: Joystick created[sideWinder Force Feedback 2 Joystick {C107E430-446E-11e6-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}

Found this in my logfile. Seems like there is something wrong with the controldevice system. (I have only 1 MSFFB2 attached.)

Saitek cyborg evo force has no FFB since 1.5.4 beta (forcefeedback off in log file) while at the same time in 1.5.3 works perfect (FFB enabled in options)

1.5.4

00000.172 INFO INPUT: Joystick created[saitek Cyborg Evo Force {181AB450-B7F5-11e2-8007-444553540000}], ForceFeedBack: off, guidFFDriver: {E49863B0-9192-11d1-BF85-00609760A39F}

1.5.3

00000.078 INFO INPUT: Joystick created[saitek Cyborg Evo Force {181AB450-B7F5-11e2-8007-444553540000}], ForceFeedBack: yes