the profile will have the calibration info for that base with it
the profile will have the calibration info for that base with it
Pso yeah it'll mess with your own calibration
Ltry this if the sled's pitch sensitivity is too weird
Land keep trimming
1So sharing vpconf files are a bad idea?
PI 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.
11Although I used it and finally got it to seemingly working and love it
PI 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.
1Can you have profiles for telemffb that doesn’t affect vpconfig?
Pyeah 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
PI look at it that vpconfig is to adjust how the base feels & telemffb is to adjust what effects the sim sends to the base
1I gathered that last night, I thought when I loaded the profile it was just loading to telemffb but it changed my vpconfig too
Pwith 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.
Poh 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.
1I didn’t hardly any feedback in dcs until I installed telemffb?
Pyeah 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.
SThanks mate i will give it a try. and what about telemffb?
SI can not understand how F4E fly. i mean i pull stick aft and always it counters FWD, it always counters to the opposite direction.
SSo if i want to fly i move stick back and also trim back otherwise it counters my input
Pcheck for double bindings??
P& no axis curves with ffb
1Yes 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?
One more question, when I change aircraft in dcs why does my vpconfig settings change? Mainly the gain and effects?
PI'm not sure about that? Is it trying to load a different profile for a new module? Sorry you might need to take that one to support channel
1I dunno, I stored the config ect…. Had me puzzled
1It’s like when telemffb changed Aircraft it’s reverting back to something
Pstore 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
1That’s what I was thinking
LI 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.
SSo this is normal? THis is they way it should work?
Si think i am okay
LThey say you trim the real thing pretty much the whole time. The pitch stability system is not classified if you want to know more.
LThe beauty of the thing (for us) is that we don't have to think about trim. We feel it in our grip hand and it comes naturally.
LI have no idea how sprung joystick owners can fly F-4E - especially in combat
LBig part of the difficulty is the placing of the AoA indicator, I just can't see it during dogfights
L(I'm in VR)
Buse the audio cues and feel
RMy first thought after trying the F14 again.
1Any suggestions as to why when I try to recalibrate my axis one of them is 38xx in center as opposed to close to 2000?
Ayou probably need to remove the band on that axis and get it closer to numerical center and put the band back on
Athe 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
Athen after that, re-calibrate the min/max values for the axis and you should be good to go
1That’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
Acenter is automatically computed between min and max
Ai 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
1Makes sense!
A(talking about the raw_x/y values here)
1It was exceeding it until I moved the motor manually
Ayeah, that's what i figured when you mentioned the center being so high
1Now to hopefully figure out how to get a Constant Spring effect instead of a progressive type effect
Awhat are you trying to accomplish?