Here’s an example of what I’m talking about. I’m in the F-18 atm.
Here’s an example of what I’m talking about. I’m in the F-18 atm.
GThis is with Telemffb running
Nfirst guess...
Your Y axis is inverted (dot in configurator moves opposite to direction of stick) and rather than invert it in configurator, you have inverted it in DCS to compensate.
The "g force effect" in TelemFFB which applies a constant "forward" force as G loading increases doesn't know you inverted the axis in DCS. So what it thinks is forward is actually back. You can disable the effect to see if it stops happening, but you will want to get your axes set up properly in configurator, otherwise things like trim are also going to be backwards (unless you go in and invert all the FFB tune settings in DCS too)
Your Y axis is inverted (dot in configurator moves opposite to direction of stick) and rather than invert it in configurator, you have inverted it in DCS to compensate.
The "g force effect" in TelemFFB which applies a constant "forward" force as G loading increases doesn't know you inverted the axis in DCS. So what it thinks is forward is actually back. You can disable the effect to see if it stops happening, but you will want to get your axes set up properly in configurator, otherwise things like trim are also going to be backwards (unless you go in and invert all the FFB tune settings in DCS too)
GThat’s it! lol I need to retrain myself from just making changes in dcs lol. Thanks @Number481
NThere’s only a couple aircraft where you have to invert the FFB on the roll axis (just the FFB, not the axis itself). The F5 comes to mind but I can’t recall the other. One of the warbirds I think.
GSo those suggestions worked perfectly. Just about all the modules I’ve tried are awesome with one exception. The F-4 is trying to climb straight up without any stick movement and I can’t seem to trim it. Are there any special tricks to that setup?
NNo.. the F4 should work with just the basic trim bindings in DCS. Shouldn't be any additional settings required.
It is a trim happy bird though.. as in real life, you can't really trim it for sustained hands off flight.
A lot of people, myself included, crank up the FFB gain values in the F4s special settings. I've got mine somewhere around %200 on roll and %250 on pitch. The bobweight and bellows are simulated quite nicely, but the force curves are a little anemic at lower speeds with the default values.
It is a trim happy bird though.. as in real life, you can't really trim it for sustained hands off flight.
A lot of people, myself included, crank up the FFB gain values in the F4s special settings. I've got mine somewhere around %200 on roll and %250 on pitch. The bobweight and bellows are simulated quite nicely, but the force curves are a little anemic at lower speeds with the default values.
GYeah I’ve flown the F-4 a decent amount. I’m wondering where that uncommanded pull I’ll is coming from.
GIt literally wants to climb up as if I’m pulling straight up with no stick input and that won’t trim up. It’s nothing slight.
GIt’s the only module behaving that way for me. Everything else feels great. F-14 feels fantastic
NShouldn't be anything in TelemFFB that would cause that, but best to try to reproduce without it running to be sure. Almost sounds like a runaway trim binding.. sure you don't have any unintentional bindings in there? What does the trim gauge in the cockpit do when it happens?
CThe F4 needs constant trim adjustments. My understanding is that this is an accurate depiction of the plane.
GAgreed! I know about the constant trim adjustments I’ve been flying the F-4 since before release in testing. Tomorrow I’ll check the bindings and see if theres a conflict somewhere. This isn’t the jet being out of trim. It feels like I’m trying to counter 100% back pressure on the stick and no amount of nose down trim makes it remotely flyable.
CAh that makes sense and yes that seems unusual. I do not have the problem with my rhino.
FThe thing is, the periodic effects jump back to 100% after a while, but I cannot figure out why? I store the settings like 30% spring in the Rhino memory, but after next restart (or now it happened after starting MSFS and loading a plane) it's back to 100%. I am puzzled. Basically after setting it up and flying it's fine, but when starting a new flight it resets to 97% spring and 100% periodic.
KThere is a function to load a specific config file each time TelemFFB is startet and also for a specific plane. Did you use it and forget you have configured it?
NAnother thing to be aware of is that, currently, TelemFFB always tries to leave the device how it found it when it was started, even if you are not using the Configurator profile loading feature or the real-time gain slider features. (This is how it works at the moment. I plan to update the code so it only does this if you have changed the gains using the override feature).
When TelemFFB starts, it reads the current gain values from the device. When you exit TelemFFB, it pushes those gain values back. So if you manually change the gains in configurator after TelemFFB has started, when TelemFFB exits it will push back the values it retrieved on startup. This only goes to the "running config" however. If you replug the device or restart the PC, it should go back to your last stored value.
Doesn't sound like that's what is happening, but it is another way your gains can change.
When TelemFFB starts, it reads the current gain values from the device. When you exit TelemFFB, it pushes those gain values back. So if you manually change the gains in configurator after TelemFFB has started, when TelemFFB exits it will push back the values it retrieved on startup. This only goes to the "running config" however. If you replug the device or restart the PC, it should go back to your last stored value.
Doesn't sound like that's what is happening, but it is another way your gains can change.
IIs there anything I should do with expert settings to get best use out of my build? One thing I noticed is my motor A is 30 and my max PSU is 7 even tho my PSU says max is 9.23A. I’be noticed folks have different amp settings and other things—assuming this is not pulling data from the controller or motors; thus is just standard config?
H@Ither [PALADIN] Well, when your PSU is capable to deliver 9+ Amps and doesn’t need to support additional devices, you can up the PSU limit. 30A for the motors is a good value. (Maybe, depending on the quality of the PSU, leave a little wiggle room)
RIve noticed with my extra long extension i needed to turn down (spring strength proportional damping) i was getting reverb in the center of the stick.
SHad a few questions that are all kind of related. Context - I primarily play DCS, and I recently completed Hiob's pedal mod so I have that running. In
the Configurator
the Configurator
- 1) For hardware force trim, there is a tick that says override Trim. This isn't covered in the documentation are there example use cases when you would/wouldn't want this enabled?
- 2) In terms of the configurator binding and loopback app, is it possible to have modifiers? For example, I may want my force trim release to be button 19, and the reset to be button 3+19, is that doable?
- 3) From the documentation it seems like pedals aren't supported in DCS w/ force trim/following. Is there a reason I can't use hardware force trim with the pedals? The documenation eludes to a double input but I don't understand how that is any different than trimming the regular stick. I assume the issue is that you can't have a HW force trim bind from a different device in the Configurator? If so, that seems like a software feature that could come at some point? I realize that with the no spring mode, it's not a necessity, but still a nice to have.
- 4) On the subject of the loopback app and streamlining things, is it possible and or planned to have a loopback for axis as well? The primary use case here would be the brake pedals so I don't have to bind the rudder to the VPForce device and the brakes from the MFG in DCS.
HI think* with the Loopback app you can actually bind trim buttons to the pedals. You can set it up in a way, that the same button trims pedals and stick (for helicopters e.g.). I only recently started to use the loopback function, so I haven’t figured out all the peculiarities, but the basic pedal trimming works.*Actually I just tried and it works perfectly fine.
CHi, I've been trying to troubleshoot some odd behavior with the DCS Phantom. The first problem was that I'd somehow gotten my balance spring settings waaay out of whack. Easily remedied once I figured it out.
CWhat's surprising me is that my generic setting for friction is being respected, despite not having it set to 'sticky'.
CThis was causing the controls to never completely attain the trim point, which made AFCS and ALT HOLD an exercise in futility since my inputs were always greater than the min breakout forces
CIn short, should I be surprised that DCS wasn't taking over friction settings, and instead leaving the non-stickied configurator ones in place? And should I also eliminate damping and spring forces then as well?
GI’m also having issues with the Phantom and I’m at a bit of a loss as to what to do. Trim is maxed out nose down. Confirmed on the cockpit gauge on the left. I’ve also confirmed that there aren’t any conflicts with pitch commands in the controls or trim commands in the controls. In Configurator it’s showing dead center on the calibration and every other aircraft in the sim is flying great. But the F4 wants to keep pulling up like I have full back stick. It flew perfectly fine with my Virpil TM.
GIf anyone has any ideas I’m all ears
HWorked fine for me yesterday evening. Some Ideas:
- triple check for double bindings both axis and none-axis (and curves! No curves with ffb)
- check the bindings for the backseater
- check your vp config for trim settings (hardware trim and trim override)
- What is your DCS controls overlay showing?
YAny idea what cause disconnecting of FFB on higher spring force ? Let's say I have extra pot for spring force and on higher setting I can hear beep and FFB disconnects then e-stop reset and it works again is it a PSU limitation or my USB ?
AIf you have the VPForce congfurator open while this happens you'll probably get a error telling you what's happened in the bottom right, but it sounds like a power issue to me
GThanks I'll check all of this...
WCan the smart folks here confirm that the solution to @Greekbull issue is to turn OFF FFB in DCS (when flying the F-4 only)? This has solved the severe pitch up issue, but leaves you without any effects other than what you load through the configurator (spring, damper, inertia, etc)?
(edited first sentance clarify)
(edited first sentance clarify)
NNo. Something else is wrong. FFB works fine with the F4.
GYeah witcohe and I are having the exact same issue. I’ve been traveling on business today so haven’t had a chance to do any testing
HYes, no problems here neither. The Phantom works fine with FFB and the Rhino. Something else is off.
In addition to my suggestions above, you guys may check if pther export scripts are working alongside the Rhino/TelemFFB and disable them for testing.
In addition to my suggestions above, you guys may check if pther export scripts are working alongside the Rhino/TelemFFB and disable them for testing.
GI know I’ve got export scripts going to SRS, Simshaker(need to clean that), SimHaptic(replacement for Simshaker), DCRealistic and I think that’s it. I’ll try remove them and test this weekend.
NExport scripts *shouldn’t * have anything to do with it. It’s not related to TelemFFB and happens without it running, unless I misunderstood @Greekbull
HJust shooting in the blue and trying to eliminate variables. Basic housekeeping doesn’t harm when troubleshooting. I don’t necessarily think this is the issue here but scripts have been causing all kinds of issues in the past.
HMaybe it should also be noted, that it is normal for the Phantom to have the stick trimmed quite a lot forward at speed. So don’t expect it to be in the middle position. Of course it should (must) still be possible to maintain level flight.
MNew and at a loss here. In the DCS A-10C II, my Pitch Axis is way too high (see image), there's very little forward motion left - no matter if in flight or on the ground. Most other modules are fine. I have FFB on in DCS, telem-ffb is off and the only effect in use is 'Spring'. What could be the cause?
WIt looks like I found the issue in my case - disabling "Balance Spring" and enabling "Force Trim" made the stck and aircraft handle like I expected. DCS FFB is enabled, along with Spring, Inertia, and Damping effects from the configurator. Spring strength is adjusted via pot 1, which I normally keep at 15% (it was higher when this screen snap was taken).
HGood that you got it solved for you! However, I don’t think that Hardware trim needs to be enabled, because I only use that for Helicopters and still the Phantom flies fine for me without it.
On the other hand, I happen to use balance spring on all my profiles - including the Phantom….
So - whatever the problem was, changing those settings probably only seemed to solve it by chance.
On the other hand, I happen to use balance spring on all my profiles - including the Phantom….
So - whatever the problem was, changing those settings probably only seemed to solve it by chance.
KIf you have added curves to your axis in DCS this might lead to trouble. Try to deactivate them.
1
I would bet my left arm you’re in takeoff Trim. Once you take off you’ll have to retrim for level flight…… to test Trim it center and hold the “takeoff trim” button just left off the throttle and see if the stick moves back to that location
OHas there been any firmware update recently to add the fan control option?
WIRL doesn't the F-4s stick move with trim adjustment? Selecting Force Trim is the only way this occurs with the default F-4 telemffb profile or am I misunderstanding something?
NThere’s som misunderstandings here. The force trim setting in configurator won’t do anything when DCS is running unless you had “sticky” enabled on the spring effect.
The trim movement for all DCS aircraft (that support it) comes from the native FFB and binding the trim in the game.
The trim movement for all DCS aircraft (that support it) comes from the native FFB and binding the trim in the game.
HIt does, no, probably….
HI wouldn’t bet blood on it without trying, but I think this only 50% correct. IIRC you can enable „override trim“ without making the spring sticky. I maybe wrong so. Need to test again.