Jump to content

Trim no longer working with Rhino ffb


Go to solution Solved by Number481,

Recommended Posts

Posted

As the title implies since the recent update the Rhino ffb has had the ability to trim taken away. I hope this is resolved soon as I love the hook but is a pain to fly without the “trimmer release”! 

Posted

Still works fine on my Brunner, however the trim reset function currently is not working and ED is aware. 
 

check you bindings? Maybe something got messed up? Double bound in UI layer maybe? 

Posted
14 hours ago, 142nd_Bama said:

As the title implies since the recent update the Rhino ffb has had the ability to trim taken away. I hope this is resolved soon as I love the hook but is a pain to fly without the “trimmer release”! 

Are you using both Direct Input, (enabled FFB in DCS settings), and telemetry in the VPForce app? No one else has reported this, so I highly doubt FFB suddenly stopped working for that particular brand, as DCS has no way of knowing what FFB brand a user has. When FFB is enabled in DCS it just sends out the Direct Input signals to ALL FFB connected devices through Direct Input (Microsoft). I'd check with other Rhino users and double check the configuration. 

Cheers! 

  • Solution
Posted
20 hours ago, 142nd_Bama said:

As the title implies since the recent update the Rhino ffb has had the ability to trim taken away. I hope this is resolved soon as I love the hook but is a pain to fly without the “trimmer release”! 

As the guys said, it is working fine.  Trimmer mode set to default, trim control bound in the settings.

Initially there was no support so you needed to use hardware trim either in configurator or TelemFFB.  With this last update (or maybe the one before?  I wasn't paying attention), they added native support.  Make sure you don't still have "sticky spring" (in configurator) or the spring override (in TelemFFB) enabled.

Posted (edited)

@Number481 I use hardware trim and override in all the helos. It worked until this update to the 47. I will double check the spring override but that shouldn’t affect the hardware Trim should it? I’ve also tried both ways, in game Trim and hardware to no avail along with a couple more squad mates. Unless there’s a new button I haven’t hit within dcs but I didn’t see anything…..

Edited by 142nd_Bama
  • 3 weeks later...
Posted

Native FFB trim doesn't seem to be working with this update on my Rhino.  I have the "centering device" interrupt bound on my stick, not using TelemFFB, only native FFB, trim mode is default, and I have the trim hat bound for beep trim in all directions.  I can see the correct buttons actuate on the 3d model in the cockpit, but force gradient remains when I press the CD interrupt, and the stick does not move when using the beep trim hat.

 

i9 12900k @ 4.9ghz, 64gb RAM

Nvidia RTX 3090

Windows 11 x64

Pimax Crystal

VP Force Rhino w/RS F16GRH, Virpil TCS Rotor Plus AH-64 Collective, BRD F1 Pedals, WH Throttle, FSSB R3 w/WH Grip, PointCTRL v2

Posted
3 hours ago, heloguy said:

Native FFB trim doesn't seem to be working with this update on my Rhino.

It works well enough for me. I do use TelemFFB, but that shouldn't make any difference in this case since I don't use the Hardware Trim option.

Spoiler

Ryzen 9 5900X | 64GB G.Skill TridentZ 3600 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X570-E GAMING | Samsung 990Pro 2TB + 960Pro 1TB NMVe | VR: Varjo Aero
Pro Flight Trainer Puma | VIRPIL MT-50CM2 grip on VPForce Rhino with Z-curve extension | Virpil CM3 throttle | Virpil CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | TPR rudder pedals

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings

 

Posted
4 hours ago, Raven (Elysian Angel) said:

It works well enough for me. I do use TelemFFB, but that shouldn't make any difference in this case since I don't use the Hardware Trim option.

Huh.  Well, I'll try a repair then, and report back.  I tried using the trim in the UH-1, and AH-64, and everything worked fine.  Just doesn't work in the 47 for me, for some reason.

 

i9 12900k @ 4.9ghz, 64gb RAM

Nvidia RTX 3090

Windows 11 x64

Pimax Crystal

VP Force Rhino w/RS F16GRH, Virpil TCS Rotor Plus AH-64 Collective, BRD F1 Pedals, WH Throttle, FSSB R3 w/WH Grip, PointCTRL v2

Posted
18 minutes ago, heloguy said:

and report back

Perhaps it’s just unexpected behaviour because of DASH and LCT now being implemented? No idea - I flew yesterday and today and didn’t have any issues.

Spoiler

Ryzen 9 5900X | 64GB G.Skill TridentZ 3600 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X570-E GAMING | Samsung 990Pro 2TB + 960Pro 1TB NMVe | VR: Varjo Aero
Pro Flight Trainer Puma | VIRPIL MT-50CM2 grip on VPForce Rhino with Z-curve extension | Virpil CM3 throttle | Virpil CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | TPR rudder pedals

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings

 

Posted
24 minutes ago, Raven (Elysian Angel) said:

Perhaps it’s just unexpected behaviour because of DASH and LCT now being implemented? No idea - I flew yesterday and today and didn’t have any issues.

Nah.  The force gradient should go away on the Rhino while I have the "CD Release" button pressed.  I have it bound, and I can see it animated as pressed, and the force gradient remains.  If I move the stick to a new position, and release the button, it does not re-reference.  It centers right back to default, which is wrong.  Hopefully it's a local problem, and not a bug, but, after my repair is done, I'll report back.  Has nothing to do with DASH and LCT.

  • Like 1
 

i9 12900k @ 4.9ghz, 64gb RAM

Nvidia RTX 3090

Windows 11 x64

Pimax Crystal

VP Force Rhino w/RS F16GRH, Virpil TCS Rotor Plus AH-64 Collective, BRD F1 Pedals, WH Throttle, FSSB R3 w/WH Grip, PointCTRL v2

Posted
Nah.  The force gradient should go away on the Rhino while I have the "CD Release" button pressed.  I have it bound, and I can see it animated as pressed, and the force gradient remains.  If I move the stick to a new position, and release the button, it does not re-reference.  It centers right back to default, which is wrong.  Hopefully it's a local problem, and not a bug, but, after my repair is done, I'll report back.  Has nothing to do with DASH and LCT.
Bob is not on, is he?

Sent from my SM-A536B using Tapatalk

Posted

I have the same issue as heloguy, CD Release does nothing at all with my VPForce. No TelemFFB or anything else. Annoying as I can't trim at all so its constant force

Posted
12 hours ago, MAXsenna said:

Bob is not on, is he?

Sent from my SM-A536B using Tapatalk
 

I assume not, as I don't even know how to turn him on.  Unless he's on by default.

 

i9 12900k @ 4.9ghz, 64gb RAM

Nvidia RTX 3090

Windows 11 x64

Pimax Crystal

VP Force Rhino w/RS F16GRH, Virpil TCS Rotor Plus AH-64 Collective, BRD F1 Pedals, WH Throttle, FSSB R3 w/WH Grip, PointCTRL v2

Posted
I assume not, as I don't even know how to turn him on.  Unless he's on by default.
No, he's not. Unless one did what I did, bound it to a two position switch that is synced at start, and always forget about it.

Sent from my SM-A536B using Tapatalk

Posted
36 minutes ago, MAXsenna said:

No, he's not. Unless one did what I did, bound it to a two position switch that is synced at start, and always forget about it. emoji6.png

Sent from my SM-A536B using Tapatalk
 

Confirmed, I don't have Bob bound to anything, so, not a factor.  Re-confirmed I have FFB enabled in the settings, and trim option for the CH-47 is set to Default.

  • Like 1
 

i9 12900k @ 4.9ghz, 64gb RAM

Nvidia RTX 3090

Windows 11 x64

Pimax Crystal

VP Force Rhino w/RS F16GRH, Virpil TCS Rotor Plus AH-64 Collective, BRD F1 Pedals, WH Throttle, FSSB R3 w/WH Grip, PointCTRL v2

Posted

 

15 hours ago, heloguy said:

Nah.  The force gradient should go away on the Rhino while I have the "CD Release" button pressed.  I have it bound, and I can see it animated as pressed, and the force gradient remains.  If I move the stick to a new position, and release the button, it does not re-reference.  It centers right back to default, which is wrong.  Hopefully it's a local problem, and not a bug, but, after my repair is done, I'll report back.  Has nothing to do with DASH and LCT.

Look for a keybind simply named "Trim" or something to that effect. The CD Release does not work yet, the simplified "Trim" works. It's what I'm using and it works perfectly.

  • Thanks 1
Posted
10 hours ago, Marsvinet said:

 

Look for a keybind simply named "Trim" or something to that effect. The CD Release does not work yet, the simplified "Trim" works. It's what I'm using and it works perfectly.

Got it, thanks.  That worked for me as well.

 

i9 12900k @ 4.9ghz, 64gb RAM

Nvidia RTX 3090

Windows 11 x64

Pimax Crystal

VP Force Rhino w/RS F16GRH, Virpil TCS Rotor Plus AH-64 Collective, BRD F1 Pedals, WH Throttle, FSSB R3 w/WH Grip, PointCTRL v2

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...