Or fly extended periods of time without trimming. I showed my parents and brother my setup a few days ago, they did not use trim and constantly countered the stick instead. That's like the first time i've heard the fans. Otherwise i only hear it in WW2 dogfights
Is the native FFB profile for the F5E rather weak, or is it just me? Idk if it is supposed to be that light (even with hydraulics). I can pull 8gs with fingertip pressure
The F-16 being weird in ffb kind of makes sense though, especially the elevator axis being soft. The sim version we have is taking simulated FSSB controls, and meshing them in to traditional spring feel to give some sense of that (the elevator being softer than the ailerons), then trying to translate that in to FFB. Something is bound to get lost in translation/feel weird. Especially compared to non-FCS jets.
Your Rhino had a pre-release firmware loaded that fixed the mentioned issues on the new board revision. I'll release v1.0.16 today, so should be all good afterwards.
Thank you, also before I updated the firmware, I selected my VPC Alpha as the connected grip and it caused the stick to start oscillating back and forth.
@walmis I feel like I’ve noticed jolts every once in a while (don’t use hardware trimming though), but usually when I’m doing smaller movements and there are engine rumble effects on, I see you mentioned jolts fixed in the new firmware update but only with hardware trim
Almost feels like there could be a series of wave effects that might be being applied and then they sorta hit a resonance point or something? Hard to describe tho
Still having an issue with axis inversion. My rhino is flipped to bring the stick closer to me. In vpforce configurator I checked both axis invert boxes. In DCS the Y axis is correct but I always have to invert the X axis in DCS. Any ideas why this is happening? Inverting in vpforce should invert both axis for DCS without having to set anything in DCS? In vpforce configurator both axis do appear inverted successfully when moving the stick.
It’s reproducible in the sense that I experience it, but there’s not a predefined way I can make it happen. Let me percolate on that, I might be able to grab logs, but if it’s in the middle of a long session, probably hard to identify
Walmis, this issue is back after updating firmware from .14 to .16, any idea what changed? Following your advice i was able to stop the crazy oscillations but they are back and its very violent if it accidentally happens.