ahh cool I wasn't sure if I had the option to just hide what I want or if I had to make a white list
ahh cool I wasn't sure if I had the option to just hide what I want or if I had to make a white list.
TThere’s also another tick mark to be made to actually hide the devices. It took me a minute to figure that out the first time. In the device box select the devices to hide and then under it select the box to enable hiding.
AYou make a whitelist of apps that you want to still see the devices, and just select which devices are to be hidden, then hit the enable checkbox.
PThanks guys, got it sorted, most the confusion was cause I downloaded the master version or something like that from Github, once I got the right one it's all easy. I just selected the VKB grip I wanted blocked, I haven't made a whitelist yet, is it possible to make a blacklist instead? I only really need to hide the grip from IL2. Cheers again guys
AYeah. There's a tickbox that I believe makes it a blacklist.
TI plugged in the kit board today and my computer is not recognizing the board as a game controller. In Device Manager it is described as "Unknown USB Device (Device Descriptor Request Failed)". Anyone run into this before?
TI didn't try it with any power connections hooked up, just USB and motor signal plugs. If that makes a difference.
LHappend to me, one wire of the usb plug was not attached to the plug itself
TThe GND and DM were flipped on the plug side. Flipped them to match the board annotation and it works!
TI'll put a +1 on the request for the shift register wiring. I wired it up as I thought it should be and was getting some unexpected behavior.
TAlthough I swear it was working at first but after a while it started acting weird. Couldn’t press individual buttons but could press them sequentially if held down. I’ll need some more time to play with it, I could have had something crossed up.
TIt could have also been my config, though I thought I clicked store/send correctly. I tried both generic and VPForce registers.
TNo matter what I did on the config store/send, I couldn’t get the “Read” config to work like I expected so maybe that was an indication of issues. When you click read is it supposed to adjust the configurator? If I clicked store/send and then changed my grip type and then clicked “Read” it wouldn’t do anything. I thought it might change back to the last grip type I stored.
TEnded up reconnecting everything and spamming the send button. Working now!
WRead just gets the active configuration - if you change something without send and click read it will revert back.
WGlad you got it working!
DI thought only store keeps the configuration in long term memory, shouldn't read revert back to the last store and have send only volatile, keeping it in memory until next shutdown/restart/read?
WYeah, that makes sense
SInstant trim (FFB FRIENDLY) and no spring no ffb modes on the apache are still broken
SSo disappointing
SI have to use simffb software to create the effects manually and unbind trim in dcs
MDid it break this month?
JAbout my question. I tried two days ago and it did work.
NAre Winwing grips plug and play now?
DWith the adapter
TMine shows some funny button combos on the VP Configurator but they all show up in DCS OK.
NWhat adaptor is that?
DThe one that walmis makes
WCould you make a screen recording if you get a chance? There's a Chrome extension that makes this easy: https://chrome.google.com/webstore/detail/screencastify-screen-vide/mmeijimgabbpbgpdklnllpncmdofkcpn?hl=en
Njust seen it on the pre order form. thanks for the help
WYeah, it's an adapter that goes between Rhino and WW grip
DIts a work of genius
NThanks. so its about a year on the pre order at the moment?
TI'll try
D
TNot really a google user, I sent a screenshot instead.
SIts always been broken since Apache came out
RONLY a Sith deals in absolutes…
Doooh. thats good 
MWhat do you mean by this?
Force trim worked for me on the Apache last night
Is there something I'm missing?
Force trim worked for me on the Apache last night
Is there something I'm missing?
SYes, the force trim option and no spring ffb mode adds input lag
S
SIf you fly using the regular mode this doesnt happen
AWell I only use the instant trim mode, isn't that the default one?
AI wouldn't have noticed that
Await why am I yellow
Dwtf is with that input lag
Dcause you been helping with the manual
HQuick question: mounting a Virpil or WWing stick to the Rhino: will that still allow me to use their respective software to setup buttons/axis and stuff?
Or will those apps no longer recognize their stick?
Or will those apps no longer recognize their stick?
SI use a Virpil stick on the Rhino Base. Windows will only recognise the Rhino base device with the axis and buttons of the stick mapped to the Rhino device. So you can't use the Virpil configurator to change the settings of the stick. That's all done via the Rhino Configurator.
DVKB works because it instead connects directly to the VKB Blackbox (unlike Virpil and WW)