ok I got it to recognize the adaptor but now it wont recognize the stick the WW F18 stick attached.
ok I got it to recognize the adaptor but now it wont recognize the stick the WW F18 stick attached. even when I click the buttons to enable them they still aren't recognized. @walmis
16 Replies
Hey guys, is sombody also experiencing a bug with the force trim in the AH 64 D Apache in DCS? After releasing the trim up (force trim unlock) button the stick always returns to center. I checked my special option trim settings and it’s the right one. I even cycled it through. It appeared after I updated everything (DCS, Telemffb, Configurator) yesterday and now I don’t know if its DCS’s fault or some settings. For a Workaround I activated hardware force trim in the configuration software but that feels not as precise when flying.
Did you check the bindings for trim release?
Yeah, they also are as usual
Any curves or saturation changes on the cyclic inside DCS?
I heard the exact same problem from someone else. That was the reason why I'll not update to new firmware, Configurator and Telem until these issues are found and fixed.
Thanks. Is it possible to roll back to an earlier fw?
I recently had the same issue. Letting the trim release button go then the stick goes back to center instead of staying where it is, isn't it? Mine got fixed by changing the USB port from a hub to diretly into the motherboard, as Walmis guided me to. I have too many USB devices. It might worth trying if your situation is the same.
@R7-Cedar @RimanDk Pushed a firmware update with some USB code updates, try it and report if it has resolved the issues
Thank you
Installing a limiter adapter: Question, How do you tune the axis to compensate for the adapter? do you need to do this or just a recalibration of the joystick is enough? (DCS)
is anyone getting an idle oscillation (slight one that doesn't get out of control) since latest firmware and calibration software update
I updated the Rhino Firmware to v1.0.17b4 and now when I open VPforce Configurator I get this message. When I click OK the app closes. What did I do wrong?
Thank you Walmis, I'm trying it now. First I tried to move the joystick bask to the hub to see if the problem comes back, so far the the Fedit and DCS is working as normal (Strangely, and kinda expected, the "DCS generated FFB getting inhibited issue" is not coming back). But the other issue I reported earlier comes back when I tried to plug both the Joystick and the Pedal (Mutual exclusion issue for USB connecting Joystick and Pedal). I'm about to update the firmware to Latest Firmware: v1.0.17b4 and see how it goes.
The firmware v1.0.17b4 appear to have addressed "Mutual exclusion issue for USB connecting Joystick and Pedal" issue, I'm flying both the Joystick and Pedal connected via Sabrent USB hub now. Thank you again Walmis, flying with VP-FORCE Feedback is such a joy!
You just need to do a new calibration in VP config. That‘s all.
Can someone point me towards explanation what exactly this "Spring Dynamics" setting is doing? I'm mainly flying F-4 in DCS and can't tell the difference between it on and off. I get the description but there is no explanation in manual, I'm not sure if this is working or not.
hello, after update the rhino Firmware and the Configurator to the lastest version my rhino stopped registering the button in the app and ion the game controllers windows app. any ideias? the axis are ok.
I can't have button actuation in the Rhino FFB WebUSB Tool too.
ps: i'm using the A10 warthog stick and was working before.