Instant trim (FFB FRIENDLY) and no spring no ffb modes on the apache are still broken
Instant 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)
SSpeaking of the configurator:
I have a weird issue. I'm running a relatively fresh Win 11 install and only recently tried to change my FFB config. I downloaded version 1.0.13. When I first started it, the window was blank and crashed/didn't respond. I tried with the Rhino disconnected, without power, connected, etc. Then it worked for one time.
Then it stopped working entirely. So I can't change my config anymore. Tried different compatibility mode settings etc. but no joy.
The configurator launches with a blank window. The Rhino "ID" is recognised and shown in the top of the window when connected. The app uses CPU resources even when it's blank. Clicking on it will bring up the "this application doesn't respond" dialogue.
I re-downloaded it and also tried the 1.0.7 version. Firmware is up to date.
Any idea how to fix it?
I have a weird issue. I'm running a relatively fresh Win 11 install and only recently tried to change my FFB config. I downloaded version 1.0.13. When I first started it, the window was blank and crashed/didn't respond. I tried with the Rhino disconnected, without power, connected, etc. Then it worked for one time.
Then it stopped working entirely. So I can't change my config anymore. Tried different compatibility mode settings etc. but no joy.
The configurator launches with a blank window. The Rhino "ID" is recognised and shown in the top of the window when connected. The app uses CPU resources even when it's blank. Clicking on it will bring up the "this application doesn't respond" dialogue.
I re-downloaded it and also tried the 1.0.7 version. Firmware is up to date.
Any idea how to fix it?
HShit; so no pass though... but... seeing as the Virpil software doesn't need to be running in the background, because the entire config is always saved to the device: wouldn't it work to configure the stick with the default base and then putting it on the Rhino? (I think WWing also saves it directly to the device)
Snegative
the config is saved to your base afaik, so the stick doesn't know of the config
the config is saved to your base afaik, so the stick doesn't know of the config
WMy guess it's something related to Qt and OpenGL. I got rid of the OpenGL dependency in the new version, so hopefully that will fix it.
SOk, thanks. I'm looking forward to the new version then. Until then I can use an old laptop for config changes
RInteresting, I was going to use a virpil alpha, but might use my TM warthog now. With the virpil gear, every axis and button is maintained compared to being mount to a virpil base?
Ktrying to lighten the stick for flying force trimmed helos
When I change it in "effects" and not in "settings" the stiffness of the stick does not change
I have to change the "settings" slider as well. Is this accurate?
When I change it in "effects" and not in "settings" the stiffness of the stick does not change
I have to change the "settings" slider as well. Is this accurate?
S
Sthese settings are bad with the ah64D
WYeah, the spring effect in "effects" tab adjusts the spring when no FFB game is running. So you have to use the slider or the potentiometer if bound to spring adjustment.
S
Sim running this external software that lets me choose the effects for when im trimming and when centering. hat up trim and hat down reset trim to center
Sworks quiet well. I would say its much more comfortable then the dcs apache one because when you trim it doesn't instantly cause you to loose all forces which turns into a jerky movement and it fixes the problem with the lag since you can use regular joystick mode and you only trim in this software
AThat's actually a very good idea. Some kind of friction or dampening stuff while force trim is happening is probably nice to have
T@walmis, I'm making progress on the Arduino slave to send analog data via the shift register. I've got the shift register and an arduino slave talking to the debug console using the Generic Grip (Debug) setting. Buttons are working and I can get it to send some axis data but I'm still figuring how to get that data into the right bytes. My question is, if I want to have 4 axes do I need to emulate the signal to be the same as the VPC Constellation Alpha/Prime? Is there a way to make a custom grip so I don't have to reverse engineer the VPC bit math?
TThis is the main issue I am having getting the data into the correct bytes. When I plug/unplug the USB it changes the position of my axis input on the debug lines.
WHey, you can use the WinWing adapter profile:
W