After updating firmware I am also getting this error ....?
After updating firmware I am also getting this error ....?
IRemove USB from Rhino base , re insert, Reboot PC
IPower supply is connected, why am I getting this error?
SThanks, but it turns out I was not using the latest configurator...:-).
DWell, I've done the suggested manipulations but still nothing... Still HANDS ON on some deliveries and not on others.
In fact, the liveries I assigned in TelemFFB a few months ago seem to work fine BUT as soon as TelemFFB loads them under the names “Airbus H145.*” or “Airbus H160.x” then it makes HANDS ON.
I unplugged everything (no USB other than Rhino) and same problem.
I have the impression that I need to change the titles of some liveries (e.g. remove the “Airbus Hxxxx” and clone my profile which works...
In fact, the liveries I assigned in TelemFFB a few months ago seem to work fine BUT as soon as TelemFFB loads them under the names “Airbus H145.*” or “Airbus H160.x” then it makes HANDS ON.
I unplugged everything (no USB other than Rhino) and same problem.
I have the impression that I need to change the titles of some liveries (e.g. remove the “Airbus Hxxxx” and clone my profile which works...
DI try with the new FW (b3)
RHello, just updated to latest firmware, configurator and TelemFFB and ran into a problem in DCS. I've been flying the A-10C II on a longer mp mission, when I got soem error beeps and the stick went dead in my hand. This happened to me twice, about an hour apart. It happened in fairly low-stress situations, too, which makes it all the more weird! Turning off the unit with the red button and turning it on again a second later worked (and I was able to stay in the air and keep flying), but this is obviously quite the hiccup!
Oddly, I tried provoking it after by doing a couple of instant-action dogfights in the F-14 and got nothing, It just worked.
The debug tab on the Configurator did mention FAULT_UNDERVOLTAGE. Screenshots for reference. I haven't touched any config options since I updated and I never had this issue before the latest update. Could be a coincidence, but I thought I would mention.
Does anyone have any ideas?
Oddly, I tried provoking it after by doing a couple of instant-action dogfights in the F-14 and got nothing, It just worked.
The debug tab on the Configurator did mention FAULT_UNDERVOLTAGE. Screenshots for reference. I haven't touched any config options since I updated and I never had this issue before the latest update. Could be a coincidence, but I thought I would mention.
Does anyone have any ideas?
RI have also had a different, fairly consistent issue, while I'm at it, that I have been meaning to ask about. Fairly often - most often when switching to the F-14 - I will find myself in a situation, where I have FFB coming from the game, but trimming doesn't work! I have no idea why. It's a bit of a dice toss every time I enter a plane, whether it will have trim or not. Most of the time, it will, but every... I wanna say 20%-25% of the times, it doesn't. The only solution appears to be to restart DCS.
I don't know where the fault lies here, and it's not something that is consistent enough that it is easily reproducible. There isn't a specific set of plane and mission that just triggers it every time. Honestly feels like it's just DCS randomly fucking up...
Any ideas on this one?
I don't know where the fault lies here, and it's not something that is consistent enough that it is easily reproducible. There isn't a specific set of plane and mission that just triggers it every time. Honestly feels like it's just DCS randomly fucking up...
Any ideas on this one?
D@Number481 Okay, I've tried it and here are my findings:
I tried with the HPG livery (the one from the action pack).
A) If I launch the livery WITHOUT changing the title = TelemFFB matches the title with the default profile (Airbus H145.) and it crashes (HANDS ON)
B) If I run the same livery but change the name (I remove the Airbus H145) then TelemFFB asks me to create or clone a profile. And then, when I clone my working profile (i.e. a personal profile), I no longer have HANDS ON.
Do the profiles “Airbus H145.” and 160 have a specificity that an old profile (made with a TelemFFB 1-2 months ago) would not have???
I tried with the HPG livery (the one from the action pack).
A) If I launch the livery WITHOUT changing the title = TelemFFB matches the title with the default profile (Airbus H145.) and it crashes (HANDS ON)
B) If I run the same livery but change the name (I remove the Airbus H145) then TelemFFB asks me to create or clone a profile. And then, when I clone my working profile (i.e. a personal profile), I no longer have HANDS ON.
Do the profiles “Airbus H145.” and 160 have a specificity that an old profile (made with a TelemFFB 1-2 months ago) would not have???
DThen I edit all my liveries 
NThe hands on/off is determined by the adjustment sliders in the config. Are they different between the two profiles in TelemFFB?
DNo that's why it's very strange. I compared line by line and it's 100% the same. The only difference I saw is:
DH145 NAME_1 matched with (defaut) profile called "Airbus H145.*
DH145 NAME_2 dont match with any profile then I (can) clone my old profile (called "HEMS Team Blue")
DThen my Helicopter named "TEAM BLUE" (aircraft.cfg) is match with my (old) profile called "HEMS TEAM BLUE" (in telemFFB)
DI'm crazy
DEx n°2:
DI have the HANDS ON on the screen => slider in TelemFFB at 10% and 5% (like my old profile) BUT if i push at 100% and 95% then the HANDS ON disappears temporarily
DIt's sol STRANGE 
DBut now with Titles changed in all my H145 liveries...then no more HANDS ON... => do you understand anything?
D(problem solved with this little trick i can say)
NI guess I don't understand anything?
When the helicopter tablet is set up properly, "Hands ON" gets triggered by TelemFFB when the joystick exceeds the configured hands-on deadzone range. Conversely, "Hands Off" gets triggered once the stick is back inside the configured hands-off deadzone setting range.
That is the only setting which affects when and why Hands on/off gets triggered.
I am not at home currently so I can't test anything, but if you send me your userconfig.xml I can look at it in a couple of days when I get back.
When the helicopter tablet is set up properly, "Hands ON" gets triggered by TelemFFB when the joystick exceeds the configured hands-on deadzone range. Conversely, "Hands Off" gets triggered once the stick is back inside the configured hands-off deadzone setting range.
That is the only setting which affects when and why Hands on/off gets triggered.
I am not at home currently so I can't test anything, but if you send me your userconfig.xml I can look at it in a couple of days when I get back.
Rhey guys I haven't played in a while and just went to use the VP force base however it is not picking up the winwing adapter
DYes, of course, I can send you this.
I know the whole thing “well enough” to have been able to manage the last few months well and as soon as the update (FW 1.0.17) and the new TelemFFB, my basic liveries (title = Airbus H145 XY) are doing HANDS ON.
Whereas in the game, there's no input at all. I thought I was going crazy!
Maybe you'll find something invisible
Anyway, thanks for your precious help. I can finally fly again with my few cool liveries!
I know the whole thing “well enough” to have been able to manage the last few months well and as soon as the update (FW 1.0.17) and the new TelemFFB, my basic liveries (title = Airbus H145 XY) are doing HANDS ON.
Whereas in the game, there's no input at all. I thought I was going crazy!
Maybe you'll find something invisible
Anyway, thanks for your precious help. I can finally fly again with my few cool liveries!
Rok 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
MHey 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.
HDid you check the bindings for trim release?
MYeah, they also are as usual
HAny curves or saturation changes on the cyclic inside DCS?
KI 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.
RThanks. Is it possible to roll back to an earlier fw?
RI 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.
W@R7-Cedar @RimanDk Pushed a firmware update with some USB code updates, try it and report if it has resolved the issues
RThank you
IInstalling 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)
His anyone getting an idle oscillation (slight one that doesn't get out of control) since latest firmware and calibration software update
BI 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?
RThank 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.
RThe 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!
HYou just need to do a new calibration in VP config. That‘s all.
KCan 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.
Shello, 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.
SI can't have button actuation in the Rhino FFB WebUSB Tool too.
Sps: i'm using the A10 warthog stick and was working before.
Sok got it, just changed to generic grip
NMaps the input spring gain (from game) to a desired output spring gain. With a linear 1.0 to 1.0 line, the output will always equal the input.
TI did, but was able to tune it out with some changes to friction/inertia. I would recommend loading the Rhino defaults with the new firmware/app and then seeing if the oscillation goes away. Then tweak back to your original settings one at a time and see what induces the instability.
IThanks
WIt's fine. Just download the latest configurator package .zip
MTodays firmware update did the trick for me too. Apache trims as usual. Thanks Walmis!
HThanks mate! Yeah I was thinking the same with reintroducing one at a time from default. Nice to hear you got a fix too. I was hoping I wasn't the only one!