Were you able to resolve the AP issue? I’ll give it a test later today but last time I had some trou
Were you able to resolve the AP issue? I’ll give it a test later today but last time I had some trouble getting it to catch alt hold
WWCursory review requested - feedback welcome - this is the VPForce FFB Config that I'm using as my default helo profile. (VPForce Rhino + 75mm extension) [Note: for max motor current and max psu I have intentionally set them down to ~85% of max]
FSo ive been thinking about this for a while, is the "deadzone" in the force feedback intentional? The motors seem to pick up the slightest movement just fine but within the green circle visible in the configurator theres not really any spring action happening, so i was wondering if that was intentional or a artifact from my design, and if its intentional if this is configurable
WIt's very small around the center since the force is proportional to deflection.
You can use the spring mapping to increase the gain near the center, something like:
You can use the spring mapping to increase the gain near the center, something like:
FI see, ill try that
MHey Walmis, I just tried that and it seems that it starts some sort of feedback loop that sends the stick moving in all directions without any input. The effect seems to be more magnified when damper and inertia are enabled but even with just spring force it still happens.
WYeah, it's a bit different for the big motor kit. It needs to be tuned - too high gains will cause oscillations.
MAh, ok. So Should I just start with a smaller gain or is there another solution? Because I'm also trying to tighten up the center a little bit.
WThis one works well on my Rhino:
WSet deadband to zero also
MOk will do. I'll keep messing with the settings. Thanks for your help!
JHello, the rhino thread is worn out and when trying to attach the f18 stick it is impossible to adjust it and it oscillates. Is there any way to solve it?
SPrint a new one
JI have little knowledge about it. Where can I get the characteristics of the part to be printed?
S@walmis, he needs this part
SWhat I would do is copy it with some calipers, my CAD program, and go to town printing it, or make a better one out of Aluminum
SBut if you don't have the time, or facilities, you'll have to acquire a new one.
BI'm sure Walmis could just send you the file itself
Fis that a wear part or unusual handling?
TI also feel that this part will wear out soon when switching the stick.
Maybe the best would be to have the .stl data pinned.
Maybe the best would be to have the .stl data pinned.
Fso this happens because the user switches sticks a lot?
Tor when you insert the new stick not 100% correctly. And the probability is of course higher when you switch the stick quite often.
JI have changed sticks 4 times, one to test with the f18, another with the VPC Mongoos t50 of a friend and another with a z extension with each of them
Fthats curious as i had a friend print a petg part to attach my vkb adapter(which is also printed tbf) and ive (un)screwed that at least 4 times as well without any damage
JMaybe the mistake was mine, which is most likely. I have near vision problems and sometimes I don't see well. I'm just trying to know if there is a way to solve it. If it's possible to print this piece again it would be great
Fif you can get walmis to send the file and someone near that can print, or walmis just print it for you itll likely be easy to fix
Fyoull likely have to open up the gimbal though
D@walmis Is it possible to get the STL file for the threaded Rhino connector? I'd like to print a few spares on the off chance I go to hook up one of my sticks and mess up the thread.
TSame for me 
@walmis
@walmis
Dcould I get this too please, I may consider getting this printed in metal
WAttached the printables: https://discord.com/channels/965234441511383080/1198547200058347670
If anyone requires spare parts one can request them via order form: http://order.vpforce.eu
If anyone requires spare parts one can request them via order form: http://order.vpforce.eu
JThank you very much 
Valmis
Valmis
MOK, so sometimes either my USB hub or the joystick loses connection for a second, enough to trigger the disconnect-reconnect sound on the joystick (PC does no see that but I hear the buzzer). when this happens, DCS does not reconnect the joystick even if I do a "rescan devices" from the controls settings in DCS, the only solution is to restart DCS altogether. Is there any fix to this ?
BTry connecting directly if possible.
BMostly as a reoubleshooting option, also worth updating drivers for your mainboards usb controllers.
If still persisting I'd consider something like a bad cable or bad hub.
If still persisting I'd consider something like a bad cable or bad hub.
MQuestion about helo trim within DCS: My understanding of how it should work is that when I release the trim button it basically sets that stick position as the new center. What I'm experiencing is that the stick kinda sets that new center but then still pulls part way back towards the original center when I release the trimmer.
I've got instant trim set within DCS as recommended by the manual and have tried this with the Hind and Ka-50. Am I just misunderstanding how trim should work or is it a settings issue on my end?
I've got instant trim set within DCS as recommended by the manual and have tried this with the Hind and Ka-50. Am I just misunderstanding how trim should work or is it a settings issue on my end?
Nwhat you describe sounds like what happens when you have axis curves set in DCS. Curves+FFB don't get along.
MAh yeah that fixed it, thanks for your help! I'm so used to adding curves that I didn't even think about it being a problem.
DYeah, I have had to (and gladly) get rid of any curves within DCS.
Aluckily the rhino offers massive movement range, which should at least help with non-curved operation
BAnd you can map and scale these as you wish in configurator, and switch as needed with a few clicks.
JHello, there is no way I can get TelemFFB to work, the only thing I get is the waiting for data message. I have reinstalled everything, deleted the registry key but it's still the same. I guess I'm missing something.In Il2 it works perfect.The issue is only in DCS
MI'd exclude that. It does not happen with any other device and I already did some intensive troubleshooting to find out I was using an insufficient power source for the USB. This one time the issue was the whole M/B USB went down for a second (so every USB peripheral got disconnected and reconnected). Every other one came back as available in DCS but the Rhino. So to my mind that says two things
1) problems with the USB subsystem in the m/b (drivers, chipset dying, w/e) BUT
2) notwithstanding that the Rhino doesn't seem to be able to come back alive (in DCS, because the system sees it alright) from a disconnect. So despite having a potential USB chain problem (chipset, drivers, cable, hub, power source you name it) the Rhino still refuses to resuscitate in DCS when it "plugs back in" eventually.
1) problems with the USB subsystem in the m/b (drivers, chipset dying, w/e) BUT
2) notwithstanding that the Rhino doesn't seem to be able to come back alive (in DCS, because the system sees it alright) from a disconnect. So despite having a potential USB chain problem (chipset, drivers, cable, hub, power source you name it) the Rhino still refuses to resuscitate in DCS when it "plugs back in" eventually.
MI'ma dive in and give it another whirl, see if it happens again.
BAs I've got a cat fond of chewing cables, I can attest a bad cable can indeed bring dowm the whole system as a safety precaution.
Cant recommended usb treeviewer more.
https://www.uwe-sieber.de/usbtreeview_e.html
If anything drops out and reconnect it will be marked on the tree and has helped diagnose a few almost similar cases, but its a common synptom with a whole bucket of varying causes so can't just say "its x" guaranteed.
Cant recommended usb treeviewer more.
https://www.uwe-sieber.de/usbtreeview_e.html
If anything drops out and reconnect it will be marked on the tree and has helped diagnose a few almost similar cases, but its a common synptom with a whole bucket of varying causes so can't just say "its x" guaranteed.
MNo. I have just tried it. The Rhino and the VPC Rotor TCS plus are both connected to the same hub.
Mwith DCS running, if I unplug and re-plug the collective, it comes back for the system and DCS.
NAssuming you have allowed TelemFFB to install the export script for you, Check the DCS logs to see if there is anything causing the script to fail.
It’s possible there’s a conflict with something else in your setup which is causing it to fail (and therefore not send any telemetry)
It’s possible there’s a conflict with something else in your setup which is causing it to fail (and therefore not send any telemetry)
Mwhen I unplug and plug back the Rhino, the system sees it ok but it stops existing for DCS
Mhm, on this last test TelemFFB wasn't even running.