Yes that would be appreciated I have the H6 and I'm having to redesign the sim so I will fit this st
Yes that would be appreciated I have the H6 and I'm having to redesign the sim so I will fit this stick
AThank you. I do have the Rudders assigned to the X axis. I can set Spring/Dampening effects etc. through the configurator. But there is no noticable effect through Telem, except for some added dampening. The Effect monitor also only shows engine rumble.
Does anyone have a config file they use for Rudders with MSFS2020?
Does anyone have a config file they use for Rudders with MSFS2020?
AI do get the engine rumbling, when i turn up the periodic effects. Is it possible to make this dynamic? F.e. more rumbling when on the ground, kess in the air, etc.?
I dom’t get any of the other effects. My guess is, i’ll first have to get Telem to control the Axis correctly through Simconnect. Currently i have to assign the Rudder Axis through the MSFS UI or FSuipc, to get Rudder movement.
I dom’t get any of the other effects. My guess is, i’ll first have to get Telem to control the Axis correctly through Simconnect. Currently i have to assign the Rudder Axis through the MSFS UI or FSuipc, to get Rudder movement.
NPossible yes, but not supported currently. For fixed wing prop aircraft the engine rumble is based on the prop RPM and varies between stronger intensity at low RPMs and lower intensity at high RPMs (the intensities and RPMs are configurable). For helicopters it is based on the rotor RPM.
If you have telemFFB set to control the axes, it actually sends the simconnect events itself. As long as you have an instance of TelemFFB running for your pedals using the -D and -t runtime options, TelemFFB will send the axis position to MSFS for the pedals (again, assuming you have it enabled in your config you are using for the pedal instance of telemFFB - which can be the same as your config for the joystick instance)
Running TelemFFB with additional devices: https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y/edit#heading=h.vq9olbg3m4ll
Configuring TelemFFB for axes control: https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y/edit#heading=h.c5s96swhnk4f
If you have telemFFB set to control the axes, it actually sends the simconnect events itself. As long as you have an instance of TelemFFB running for your pedals using the -D and -t runtime options, TelemFFB will send the axis position to MSFS for the pedals (again, assuming you have it enabled in your config you are using for the pedal instance of telemFFB - which can be the same as your config for the joystick instance)
Running TelemFFB with additional devices: https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y/edit#heading=h.vq9olbg3m4ll
Configuring TelemFFB for axes control: https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y/edit#heading=h.c5s96swhnk4f
AI'm only running the FFB Pedals, so no Rhino Stick. But i did assign PID 2054 in the configurator and use the -D and -t options. Telem shows FFB Type Pedals.
ABtw, when i don't change the FFB type -t, the X-Axis moves the Aileron axis in MSFS, so the Simconnect connection seems to work.
NWhat aircraft are you flying?
ADefault aircraft. To test if axis_rudder_set is actually used by the Aircraft, i assigned it through FSUIPC and then the Rudders do move.
Nhmm.. I am scratching me head here.... I wrote that code so I'm pretty familiar with how it works internally in TelemFFB (but that also means there are probably corner-case bugs still 
)... drawing blank trying to to think of a config setup that would cause it to work as x-axis when TelemFFB thinks its a joystick, but not pedals.
I was asking about which aircraft since there are some helicopters (like the FlyInside ones) that don't understand the "tail rotor axis" or the helicopter specific cyclic axes so they need the "legacy bindings" option enabled.
For any other aircraft though.. it should just work.... Only exception being helicopters. There is logic in the helicopter pedal support that tries to initialize the pedals to a "good position" using spring force before it starts sending the axis position. This will be neutral on the ground or last position before pause if you are coming off pause. If you have spring force disabled and 'sticky spring' enabled in Configurator, then TelemFFB can't use the spring force to initialize the pedals. (but if you manually centered the pedals, telemFFB would see that and consider the initialization complete and then start sending the position).
)... drawing blank trying to to think of a config setup that would cause it to work as x-axis when TelemFFB thinks its a joystick, but not pedals. I was asking about which aircraft since there are some helicopters (like the FlyInside ones) that don't understand the "tail rotor axis" or the helicopter specific cyclic axes so they need the "legacy bindings" option enabled.
For any other aircraft though.. it should just work.... Only exception being helicopters. There is logic in the helicopter pedal support that tries to initialize the pedals to a "good position" using spring force before it starts sending the axis position. This will be neutral on the ground or last position before pause if you are coming off pause. If you have spring force disabled and 'sticky spring' enabled in Configurator, then TelemFFB can't use the spring force to initialize the pedals. (but if you manually centered the pedals, telemFFB would see that and consider the initialization complete and then start sending the position).
SI have an extension coming already, Hopefully that will allow me to twist. Thanks!
In case it doesnt... does the vipil extension work with the warthog??
In case it doesnt... does the vipil extension work with the warthog??
BYup
WIt should!
AI just tried it again. Switching back to Joystick FFB, and moving the Rudder pedals (X Axis), moves the Aileron Axis in the sim. Switching back to Pedals FFB: no rudder movement.
In the Log console, there are only info messages. (set telemffb_controls_axes=true, use legacy_bindings=false).
In the Log console, there are only info messages. (set telemffb_controls_axes=true, use legacy_bindings=false).
ABtw, setting pedal_spring_mode, aircraft_vs_speed, aircraft_vs_gain, aircraft_vne_speed, aircraft_vne_gain produces an Error in the Log Console, when placed under Aircraft Definitions or Aircraft types. (WARNING: Unknown parameter pedal_spring_mode).
NNone of thse are applicable to MSFS, hence the MSFS effects module doesn't understand them.
The pedal spring mode is not applicable to MSFS (DCS only setting), . In MSFS it auto-switches based on aircraft type. I plan to update DCS to do the same eventually.
The rest of those aren't even meant to be user exposed settings, you must be looking at the source? They shouldn't be in the default config (and they only apply to DCS since we can get the aircraft v speeds from simconnect in MSFS). The DCS aircraft v-speeds are hard coded into the lua export script based on limited research used to get that data for the DCS aircraft. You could add them to a DCS aircraft to override the data that is hardcoded into the telemetry stream. For MSFS, we get Vs0/Vs1/Vc from simconnect.
The pedal spring mode is not applicable to MSFS (DCS only setting), . In MSFS it auto-switches based on aircraft type. I plan to update DCS to do the same eventually.
The rest of those aren't even meant to be user exposed settings, you must be looking at the source? They shouldn't be in the default config (and they only apply to DCS since we can get the aircraft v speeds from simconnect in MSFS). The DCS aircraft v-speeds are hard coded into the lua export script based on limited research used to get that data for the DCS aircraft. You could add them to a DCS aircraft to override the data that is hardcoded into the telemetry stream. For MSFS, we get Vs0/Vs1/Vc from simconnect.
NAre you running from source? Will be a lot easier for me to help debug if so... as opposed to having to spin a special exe wth extra debug logging.
AI'm currently running the latest auto-build from the development branch.
AThese settings are in the config.ini and i wrongly assumed they were for DCS and MSFS.
Nnow I'm really perplexed because those settings (aircraft_vs_speed, aircraft_vs_gain, aircraft_vne_speed, aircraft_vne_gain) are not in config.ini.
Oh.. OK, you must have read this part of the manual which talks about overriding those values in DCS..
pedal_spring_mode is, in the DCS section. But the other settings don't exist in the config....Oh.. OK, you must have read this part of the manual which talks about overriding those values in DCS..
Ayes, that’s it.
Ncan you send me a screenshot of the TelemFFB window with the 'effects monitor' option selected when it is not working? Also if you could drop the log file in here too that might help.
NI think I may have figured out whats wrong... at least its the only thing that would explain what you are seeing... in the command line,
-t pedals needs to be all lowercase. -t Pedals will not work. An oversight for sure (and a simple fix in the next version).
P@jehlybean I sent 8020 an email this morning directly to the rep I dealt with last time and didn't get a response yet (they may have been off today, because typically the responses have been very quick). I'll follow up with their main number tomorrow by phone.
AGot it working. I used <pedals> (with the parenthesis, as shown in the manual). Which starts Telem in pedals mode with no problem, but obviously causes problems. Leaving the < > away, solved the problem. Thank you for your help.
RSorry, is there any tracking for this please? Just want to make sure I don’t miss any import charges and I’ve not had any update emails or anything…
BLargely in my experience the shipping company prepays any import/vat fees to expedite the handling shipping, the bill for this has come for me a few different ways, it can be added in with the shipping labels, come few days later in the mail, or lately an electronic bill just sent straight to my bank.
RJust me worrying 
Had the Rhino base sitting on my desk for a week but I’m not able to use it without a working winwing adapter (this tracking is for the replacement walmis is shipping) - so eager to make sure it’s not delayed for no reason 
Had the Rhino base sitting on my desk for a week but I’m not able to use it without a working winwing adapter (this tracking is for the replacement walmis is shipping) - so eager to make sure it’s not delayed for no reason 
RTracking received from walmis via DM. Thank you again!
B
CJust to verify, the Vkb adapter is for mkIII grips.
MCorrect
MWalmis has not yet released a MKIV adapter, as afaik, he does not have a MKIV grip on hand
CThanks! I was worried for a second that I needed to order the mkIV upgrade kit.
RHmmm... How do you assign buttons as hats when using shift register boards (generic grip or VPForce shift register board profiles)?
LAfter calibrating my stick and sending the settings to the device, the stick doesn't center. It's reading -24 in x and 166 in y. This is with Spring force enabled at 100% in both screens. How do I get these to zero out? It's resulting in a slight nose up input in DCS that I'm having to fight constantly.
LI imagine it has something to do with the assymetrical physical stops I've installed on the base to mimic the range of the F/A-18 stick
LBut what I don't understand is why the FFB isn't driving the stick to the zero position anyway
LTurning adaptive recentering will hold it in the center position if I move it there and let go, otherwise it oscillates around center at about 4Hz
LSetting the Spring Force LPF to 25Hz (Max) helps reduce the amplitude of the oscillation, but doesn't eliminate it
LOk, Adaptive Recentering + about 30% Damping and Inertia has sorted it. I don't love the feeling of the adaptive recentering though
LDefinitely going to have to do more tweaking. Hooking up to the tanker was not easy :S
LAnyone have settings they can share that makes for good "finger flying"?
WWhat grip/extension are you using? Sounds like it could be a balancing issue.
TGuys, does DCS have its own spring strength? It seems like I dial in my setting in the configurator and save it. But when I start flying a module in DCS, it feels -5% to -10% lighter with regards to spring strength.
LThanks walmis! I’m using a TM Hornet grip with the VPC 200mm Flightstick Extension so that would make sense.
LI believe so Tinman. You could try checking off “Sticky” in the configurator for Spring Force. I’m not sure if that overrides only the spring effect in DCS or all effects generated by TelemFFB though.
Ngood practice to tune the balance force settings first, so that your stick more or less stays where you put it, even with no spring force enabled... then the adaptive centering will have to work a lot less to fully center the stick and you won't feel it as much or at all...
See this post for a general how-to.. 🧰support
See this post for a general how-to.. 🧰support
LMuch appreciated! I’ll experiment with that tonight. I swear I did RTFM cover to cover
TYeah thats what I was afraid of. But I will try. TY
NThat is the nature of FFB. DCS has native FFB support and each module has its own unique implementation.
If you enable sticky spring, you will lose the entire dynamic aspect of FFB (if the aircraft has such, aka non-FBW) including trim movement.
Don’t try to set up the rhino for a specific aircraft outside of the sim. Do it while the sim is running and you are loaded in the aircraft.
As a simplified explanation, if DCS says “set %85 spring strength”, that %85 is not related to the maximum force your joystick can output, it is related to the maximum force you have configured in vpf configurator.
So if you had your slider at %50, and DCS said “set %85”, that actually results in %85 of %50.
If you enable sticky spring, you will lose the entire dynamic aspect of FFB (if the aircraft has such, aka non-FBW) including trim movement.
Don’t try to set up the rhino for a specific aircraft outside of the sim. Do it while the sim is running and you are loaded in the aircraft.
As a simplified explanation, if DCS says “set %85 spring strength”, that %85 is not related to the maximum force your joystick can output, it is related to the maximum force you have configured in vpf configurator.
So if you had your slider at %50, and DCS said “set %85”, that actually results in %85 of %50.