and to confirm the blue dot in the VP configurator shows in the trimmed position?
and to confirm the blue dot in the VP configurator shows in the trimmed position?
VIf I'm reading this correctly, the X center is 1600. Is that problematic? With everything reset to factory before running calibration, the left direction only gets about 2/3 of the way on the VPForce Configurator indicator when I hit the limits of the base
Vand what does Force Comp do?
Vps physically whether deflected left or right fully, the VKB adaptor (i.e. just checking the tip of the Rhino before my grip starts) extends just past the lip of the base - i.e. it's not like the base itself is skew/limited more in one direction
Vjust the software seems to think it has less range to the left I guess?
WMaybe the leather bunches up? You should feel a solid bump at the edge.
The calibration looks fine.
Hover the force comp field and an explanation should pop up.
The calibration looks fine.
Hover the force comp field and an explanation should pop up.
VYeah, it's not the leather - I do feel the bump. Just the C: 1675 and raw_x value being in the 1600s I thought that might be bad, given it recommends a center around 2048
VI did see the popup for Force Comp, thanks - just I don't understand it.
WWhen under force there is some flex in the system, gimbal, belts etc. And you will find that you might not be able to reach the logical axis limits .
WThis is because the motors are axis sensors
VSo crank it up to 190 and 100 respectively, or is it something to be tuned/tested?
W190, 100 works well for Rhino
WBut you can play around and see how it works if interested 
HDo you possibly have a second stick bound to the pitch/roll axes?
HOh, just saw your other post saying you checked that
HLast thing I'd try is wiping your saved games folder and rebuilding it
HOne way to do that would be moving the entire folder somewhere else, launching DCS and letting it rebuild it, and seeing if that fixes the issue
HIf it does, try moving things back in sections to see what causes the issue to reappear
VYes it does
VNo, double and triple checked...no other devices bound to x/y axis
MI've had a weird issue in the last couple of days. I have a VIRPIL TCS rotor base and hawk 60 grip, A VIRPIL CM2 throttle, and verbal t50 CM2 grip attached to the rhino. Everything has been working okay for a couple of weeks. Now it has been 2 or 3 days that when I connect the rhino to the powered USB hub I use for all those peripherals, the VIRPIL collective disconnects for some reason. I have changed the powered USB hub with a new one but it still happens.
The hub is a USB 3.0 connected to a 3.2 USB port on the motherboard so it shouldn't be a USB bandwidth problem. Any idea what I could check to troubleshoot this?
The hub is a USB 3.0 connected to a 3.2 USB port on the motherboard so it shouldn't be a USB bandwidth problem. Any idea what I could check to troubleshoot this?
DDisconnects and reconnects?
Mthe TCS rotor? no it just disappears. I get this behavior consistently from the TCS rotor, not so consistently (at least not that I'm aware of, or I didn't pay enough attention to that. More testing would be needed I guess) from the throttle...
I mean the TCS rotor disappears as long as the Rhino is plugged in. If I unplug the Rhino it comes back.
I mean the TCS rotor disappears as long as the Rhino is plugged in. If I unplug the Rhino it comes back.
WIt disappears from game devices or from device manager ?
WMYeah I have monitored it with that, USBLogview and USBDeview... it disappears from both, device manager AND game devices
Mno idea why. Maybe the collective is acting up IDK. I could see the current draw (from USBTreeview) is in line with the throttle (500ma) while the Rhino only draws 200ma (ofc, as that is powered by its brick...)
WI'd try booting up Linux live USB such as Ubuntu and see in the kernel logs
dmesghm. I can sure try and do that in time. If you have any other suggestion I'm open.
WI assume you tried different motherboard USB sockets or plugging everything directly to the motherboard
MI did change to EVERY damn port on the M/B.
Turns out it was the USB hub power brick. It's powered by a USB-C so i was using a phone charger that happened to be JUST sufficient. It was flimsy enough that it would eventually give up and stop sending 5V reliably, causing the whole issue. A different power source seems to have solved all issues.
To restate: the Rhino was definitely NOT the cause.
Thanks for taking the time to interact, @walmis. 10/10 would buy a second Rhino. (it's a joke...)
Turns out it was the USB hub power brick. It's powered by a USB-C so i was using a phone charger that happened to be JUST sufficient. It was flimsy enough that it would eventually give up and stop sending 5V reliably, causing the whole issue. A different power source seems to have solved all issues.
To restate: the Rhino was definitely NOT the cause.
Thanks for taking the time to interact, @walmis. 10/10 would buy a second Rhino. (it's a joke...)
MI mean the buy part. I meant the 10/10
Vcoult it be something in telem ffb?
Nunlikely, TelemFFB only sends axis information to DCS in a couple very rare instances (trim following for the Harrier and one or 2 other modules).. but it would be pretty easy to find out
VI don't understand what is happening....last time I tried the apache, it was working flawlessly
Vnow I have this strange reset issue.
HA good rule of thumb is to always ensure the power supply you grab out of the random electronics box in the closet meets or exceeds the wattage required by the thing you're about to plug it into to prevent problems.
I had a similar issue a while back with a wireless router acting strange and it wound up being an underpowered power supply
I had a similar issue a while back with a wireless router acting strange and it wound up being an underpowered power supply
Nwithout any real valuable advice to give.. I would say remove any mods you may have installed and do a slow DCS repair (if you've not already done that)
HDid you try cleaning out your saved games folder yet?
HThe other good choice is the slow repair or a complete module reinstall
VI just discoved that I have the same issue in every module with trim, so Fox example also mirage F1 and f14
VYes I did a slow repair
VI tried to delete the files in input folder...still no joy
VNow I deleted all the saved games folder
VAnd checking again
VOk saved games destroyed...issue still there
V
V
Wthat's weird, can you make a video with the DCS input overlay showing?
VI did...too big to put here
Wyoutube private vid?