HStrange, I am not getting any native FFB on DCS, despite having activated it in the Options menu. None of my Effects are on "Sticky" so native FFB is not being over ridden. Feedback from TelemFFB works fine though.
BWhat module?
HModules with native FFB like the F-14, P-47 and Huey
HFrom what I understand, base should lose all effects when DCS loads, this doesn't happen
J@walmis in the process of trying to move a DIY grip from a Arduino Micro to the 32 shift register you sent me, is there any info on how to properly wire this up? I have looked all over the discord for something.
DYes, I unchecked it this morning when i brought down the filters... I will try it again.
MI'm having an issue I hope is just me missing something simple. I have Rhino kit #1, which I just updated to the most current software. WEBUSB Tool connects, no option to update firmware so assuming that's up to date now.? VP Force software sees when its USB connected but motors status offline and neither webusb tool or vp force register position.
In windows game controller settings it shows up and the position can be read there. The motors seem happy as the cogging disappears when connected/powered.
In windows game controller settings it shows up and the position can be read there. The motors seem happy as the cogging disappears when connected/powered.
RDo you mean you can see the axis moving using joy.col but not at the vpforce configurator? That’s strange. I had an issue where the configurator kept saying motor offline, but there was no cogging at the motor . Turned out one of the serial wires to the motor was fraying at the connector. I re-crimped the wire and everything is ok again.
MCan see axes moving in Windows Game Controller Settings but not vpforce configurator. I need to doublecheck those connections, plugging in one of the serials was a little janky maybe that's the problem
WDoes the configurator show anything else? Like the cycle_time should be updating
MOn the configurator all I can see is that USB is connected, no other signs of life
WThat's strange, you did get the latest configurator, right?
MI'm on 1.0.16-1
WCan you screenshot the webusb page?
M
WAh, crap, it thinks you have a newer firmware 
WWill fix it asap
MAwesome much appreciated
WFix pushed
MWhoa didn't think you were doing this like right now :p
webusb now tracks position but I get an error trying to launch vpforce configurator
webusb now tracks position but I get an error trying to launch vpforce configurator
MError:LIBUSB_TRANSFER_ERROR
MCommandline Processing Error
MNo longer throwing that error but when vpforce config is up it's back to usb connected but nothing else. webusb seems sorted and I'll call that progress for the time being! Close to bedtime for me now though
AWere 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