Recently got an email telling me my preorder was almost ready, wasn’t expecting it nearly this early so I wanted to ask do you need to fully pay within 10 days or just confirm the order via the link?
For the first email with the link to the order form you just have to fill out the order form and add any additional parts you want to order (adapter...). That's the actual placing of your final order. When all parts are available you will get another email (New invoice...) containing the invoice of your ordered parts and the clear instructions how to pay.
Be aware the invoice will come soon after you place that order. For me it was, I got mail on Wednesday, and placed the order on Fri and on Monday I had the invoice with a few days to pay, which I paid, and 2.5 days later it was in my hands in Florida USA. But as you noted their list seems to be moving much faster, My order only took about 3 mos total so if you can't do it now get back on the list.
Thanks for sharing your settings, much appreaciated. In the VPForce manual, there is nothing explaining the Trim Release Damper, and all the mentions to Trim Release seemed to be related to MSFS, so I had just totally skipped this one. I will need to read more about it, to understand what is supposed to do, and see how to configure it. I went to the release note and found this: - Helicopter Trim Release Damper - This is not a replacement of the in-game trim release functionality. It is a simple spring based dampening effect, identical to the one for MSFS. - To configure, simply enable the effect and bind the same button that you have configured for TR in the sim. While the button is depressed, TelemFFB will add the dampening effect and will remove it when the button is released. The actual trimming and centering offset is still completely handled by DCS. Thanks again
Yeah that’s the case for native DCS FFB, I don’t use it all I control all my FFB through TelemFFB. To set the spring, use override DCS spring. Then you get access to two more sliders, spring gain and then a separate trim damper slider too, as well as binds for FT release, FT re-centre and a 4 way trim hat
I've got the same issue with Loopback not saving the selection. I am using the PumaX as a Button/Hat Source but on every reloading of the tool it defaults back to the Rhino. Also after a certain time flying the HPG H145 in FS2020 the Loopback tool crashes, but in the process it also kills the PumaX driver. You instantly notice this as only the stick lat/long axis (Rhino) work and everything else is dead. Any ideas?
I am not sure how the effect of Trim Release Damper is supposed to feel. Do you need to have also some higher Damper Gain selected in order for to work? Because Force Trim is working in the game, but I cannot feel any difference, which point to me having probably miss something in the configuration somewhere. Thanks again.
I’m not near my PC for the next few days or so apologies.
With a higher damper force and master gain turned up in VPConfig, the faster you move the cyclic the higher the force opposing it becomes. It simulates hydraulics quite well tbf.
Trim release damper is a spring based effect. When you press TR and the game spring goes to 0, TelemFFB starts a temporary spring effect that feeds the center position back into itself that results in a damping feeling. It’s a different sensation than straight damper effect would be.
When you release TR, TelemFFB stops the effect and hands the spring back to the game.
Pots are not wired at all so only the values on the screenshots are applied. I am using Release 20250101 which I believe is the latest. Now I guess the problem of me not feeling the effect was because I had spring gain to 0.
First of all thank you both CaptainNel and Number481 for your help with this. I wish the manual was up-to-date, and this function explained better. I changed the Spring to 40% and the Damper to 15%, and now I can feel the effect. Whenever I push Trim Release I can move the Cyclic freely, when i push force trim, it creates a "new center" with some "spring effect" recentering the stick around this "new center", then if I push Trim Release the artificial center disappear and I can move again freely. Now the big problem I have is that when I push the Force Trim button, it does not create the new center at the exact same point the cyclic is when I push Pilot Timmer/Trim, it seems to put it at some arbitrary point instead, and not immediately. Is it supposed to be one single push or continuous push and release? I am suspecting some conflict between the Pilot Trimmer button defined in DCS and the Trim button defined in VPForce Configurator, are we supposed to configure it in both?.
I haver used the tlelffb trim solution in the past, but have swapped over to dcs implementation as each supported airframe feels different. The 60 and still use the teleffb solution. works well for me. havetn had any issues.
I use telemffb because everything feels the same I prefer things to feel the same but I don’t really have anyt of the effects turned on or that it’s literally just for force trim ¯\_(ツ)_/¯
Is there any use to the Trim button defined in VPForceConfigurator? The problem with TelemFFB is that it does not force trim the position of the pedals, does it?
★ Newest Generation Rudder Pedals★ Perfect for All Simulations★ 3-Axis Input (Yaw and Toe Brakes)★ All Metal Construction★ Adjustable Cam-Centering Mechanism★ VPC Contactless Digital Proximity Sensors R1 Pedals Damper Upgrade Kit Available Here
The two cut outs on the lateral sides of each metal foot rest look interesting almost like you could put a switch in there that could be depressed when you put your feet on the pedals almost like for a trim release for petals or PTT
Anybody here flying the T-45 or Hawk T1 in MSFS2020? The Rhino feels so limp on the ground and at slow speed. It seems that TelemFFB isn't recognising the module and can't set any sensible settings. Any ideas how to fix this?
What do you have off exactly? The Force Trim in VPForce Configurator? VPForce Configurator Trim works well for me, but then it offset the center for the curves defined in DCS, which is not good, so I rather use the implementation of DCS, although I cannot get it to work properly anylonger