Can anyone tell me why button 1 is permanently red (pushed) on my system just like in this picture f
Can anyone tell me why button 1 is permanently red (pushed) on my system just like in this picture from the manual?
P@.durham so that number 1 button is it linked to any of the buttons on the grip?
TMeans that I cannot set any buttons in dcs as this is always pushed.
Also is there a way I can get my brake axis on the stick to act as axis rather than button?
Also is there a way I can get my brake axis on the stick to act as axis rather than button?
TIt is the new Virpil CM2, and no I am not using the loopback app. The picture was from the manual - Loaded software is V 1.0.14 and firmware is V1.0.14-2, both of which I believe are the latest
TYes the first detente of the trigger
TAre you available for a call on Discord?
TOr telephone?
Pahh ok, can you plug the grip into the virpil base & make that a pulse not a constant button press?
Pnot right now, I could soon like 30min
TThe Virpil software is no longer working as the base is gone, so it cannot read anything.
TThat sounds great, although you are able to use all your vkb software as you have a pass through from the grip
Pyeah I really like the idea of the passthrough for that reason, maybe as Walmis does more work if it's possible he could add config software for the different grips that plug direct in
PSo it looks like the trouble is that trigger being constant, when you're in the DCS keybind settings can you press the wanted button & get it to come up at all?
Pyou could also take note of the button # for each physical button & when binding in DCS manually add the button for each, I'll have to check that
P
P
Pthat will at least let you get some bindings started
TWorks perfectly without the 20cm extension
Pwha? 
Pwithout the extension the button isn't constant?
Pif that's the case try re-seating the grip & extension
Awhat grip do you have? i have the alpha, and that's the trigger lever, which defaults to pressed when extended. If i pull the trigger switch in, it then becomes unpressed
APressed
AUnpressed
TOk - removed the 20cm extension and now no errant button pushes, so ready to go into dcs and see if I can set up force trim in the apache
TThis extension has been a dick for some time, and basically stopped me swapping grips for different planes - I have four grips - CM2, F14, TMF18 and TM-A10. Used to be able to swap in a couple of minutes, but the extension was so picky, once I got it working I just left it alone.
TYes when the guard is down get a press on btn6, which goes away when I unsafe it.
THere goes force trim!
TGetting closer - you available - going to voice in case you are
Poh shit sorry m8, give me a min
SI don't know why it is like that but you can invert the button from VPForce configurator's button mapping tab. It should solve the problem not being able to map buttons in DCS.
PSo is there any way to configure the Virpil & Winwing grips via the VPforce config app? Or if I buy Virpil & Winwing grips will I still need to buy the bases too?
WWhat do you mean to configure? They're plug and play
PI just mean how with the Virpil software you get the options to do different things with the buttons/axis etc. can we do the same sort of configuration in the vpforce app?
Plike if this was with my vkb (I don't own virpil/WW atm) I can change the flip trigger to act differently depending how I set it, I imagine that virpil/WW have similar configurability & can we do the same thing with vpforce?
Psorry if I'm making this confusing 
WThere's limited stuff you can manipulate with the Rhino software. Since there's tools (such as joystick Gremlin) that can do the more advanced stuff, I haven't put in much effort to cover all the edge use cases 
Pyeah nice, I kinda forgot about JG
PHey Walmis, just wondering what's going on here? This might be normal I might need to run the debug to get a proper log for you, I'm getting motor vibration/shudder occasionally when going to full x deflection, I'm also using software endstops, this hasn't happened during flight but can happen when between flights & the stick has gone 'limp' & I move it to the x endstop. Is this the motor's doing their self protection thing? the motor temp was around 34° is this too hot? I wouldn't think it was especially with the fans & as I say it's not happening when flying. Does it just not like touching the endstop while in the 'limp' state it's in between flights & I just need to be careful not to be tempted to move the stick unless flying? Sorry for the txt wall.
Si had the same thing last night with XPForce.. i made a post here but deleted since it cleared up after a reboot
Smy motors were dead cold though and the repeating disconnects happened right away. not sure what the problem was, it was only with the joystic not the pedal single axis.
Si made sure the joystick was the "master device" in xpforce config also
WYeah, I have a fix committed for the next firmware update.
WI've noticed the author of XPforce started working on better multi device support
Sit mostly works.. kinda finicky though
Ahere's a random thing -- i've been playing some IL2, and all a sudden the LEDs on my virpil alpha grip, attached to the rhino, turned on 
A(is that something to be worried about? like, they've never worked before... and I assume if i disconnect and re-connect, the LEDs will stop working)
AProof that I’m not crazy…
TWith a lot of messing around with my virpil 200mm extension, I got it to send a constant push on button 1, which then upset DCS as I could not configure any controls without them being overwritten by button 1, which does not exist. Tried the invert to no effect, so just set it to zero and nothing seen by DCS.
T
AYour bug is so weird, cause even with the button constantly activating for me when I have the lever pushed out, it doesn’t fight when attempting to create other binds with the grip