I’m brand new to the rhino but I tried one of the profiles from knowledge thread last night and it completely screwed up my stuff, use caution! I could’ve done something wrong but it changed my stick calibration everything…..
I don't have rhino in & config app open atm but can you copy paste your own calibration numbers somewhere then load the new profile & copy paste you calibration back in? not exactly smooth operation but better than recalibrating if you don't want to.
I just have a few generic profiles I use then tweak each new module from there as I fly it. Have a generic profile each for; fbw jet, non-fbw jet, warbird, helo, ga. Load the profile & tweak as you fly it.
yeah always keep a backup copy of a default profile that has been calibrated, that way if anything goes wrong you can reload that & get back to a baseline that was working
with dcs & IL2 you don't need telemffb as those sims have native ffb support, msfs2020 needs telemffb cause it has no native support. So you can run dcs without telemffb & still get whatever ffb effects the module maker baked in.
oh yeah you can point telemffb app to the config profile you want it to load for a certian module, so when you jump in the f-18 it will load the vpconfig profile you tell it too.
yeah so the f-14 has good ffb native, the f4 has some it just depends on the module maker. Telemffb adds more though, like the bumps from ground texture on taxi etc.
Yes it felt incredible after installing it! One more question, when I change aircraft in dcs why does my vpconfig settings change? Mainly the gain and effects?
store config means that's the default config that the rhino will load & use, so even if you don't turn on the config app the rhino will use the stored profile by default
I know it's unlike anything else I've flown. Bobweights and bellows maintain pitch stability in F-4E and HB modelled it. The neutral trim position moves around based on airspeed (bellows) and g (bobweights). Whether you need to trim nose down or nose up depends on what's happening to your airspeed. When it increases, to maintain level flight you trim nose down and vice versa. It's normal that you are trimming it pretty much all the time. You don't even think about it after a while.
the pro tip i learned from someone else on here -- with the band off, manually set axis min to 0, and axis max to 4096, then set 100% spring, apply those settings, then while carefully trying to keep the joystick perfectly vertical, add the band back on, which should get you a pretty decent middle around the numerical middle of the motor range
That’s what I just did but I don’t understand why it’s not setting the center value to 2048 when recalibrating? I think everything is working ok but seeing the center seems to do nothing. Unless I’m doing something wrong. I’m following the protomaker build guide as I did the diy unit
i wouldn't worry about it lining up exactly halfway between 0 and 4096. what you ultimately care about, is that your moveable range does not extend below 0 and above 4096