I’ll give it a try, I have the same setup. Are you printing directly on the glass? Any glue stick?
I’ll give it a try, I have the same setup. Are you printing directly on the glass? Any glue stick?
BDirect on the glass, no glue, hairspray or anything. At least not in the end.
1I gave 300 bucks for a piece of shit
1didnt last 1 month
NThe Configurator being reset to factory setting has indeed fixed all my issues I was having and brought all my aircraft to life. So it seems a bad setting in the configurator was the issue, Thanks to you and others for your help!
SWhat do the "4-Way Hats" checkboxes on the Settings page in the FFB Configurator do? I have a TM F-16 grip, and have selected "Generic Grip" as the grip type, since there was no direct match. At least for this setup, the checkboxes don't seem to do much anything whether they're checked or not. Manual says nothing about the checkboxes.
TIf your buttons are working as they should I wouldn’t worry. Generic Grip is the correct setting for TM. Also make sure you are storing config when making changes.
NIf you are using “hats as buttons”, it blocks the diagonal combinations like U/L, U/R, etc. if you are not using the hats as buttons, it doesn’t send the diagonal pov events that would be part of an 8-way hat.
SDid I get this right: The "Hats as buttons" checkboxes will make it so that when you push the hat to (say) upper right, then it will put out either the button for right or button for up, but not up and right simultaneously. Whereas the "4-Way Hats" checkboxes will just disable the diagonals from 8-way hats. Is this correct?
NNormally, a hat will generate hat specific events like “pov_l” or “pov_ur”. The hats as buttons feature will generate generic button numbers in stead.
The 4-way feature will block the diagonals, turning what might be electrically an 8-way into a 4 way.
The 4-way feature will block the diagonals, turning what might be electrically an 8-way into a 4 way.
SCopy that 
. Looks like the generic grip will just generate only button events for the hats regardless, so it doesn't matter for my current setup. I'll have to remember this when changing grips though.
. Looks like the generic grip will just generate only button events for the hats regardless, so it doesn't matter for my current setup. I'll have to remember this when changing grips though.
Smy emergency button stopped working , so rhino is all the time powered
Ago big or go home
SRelated to my previous question: Are there plans to increase the number of directly supported grips in the configurator, e.g. for the TM grips or the new Virpil Flanker grip? And is there much benefit in having direct support for a grip, except for possible additional axes like analog hats or such?
![Prometheus [Prom]](https://cdn.discordapp.com/avatars/777496628579401739/90d1e9e0a05c7bafd59a74ba942bd870.webp?size=40)
PI have to import a vpforce configurator file (.vpconf) each time vptelemeffb is started. Things like changes to the settings page etc. I assumed these are stored in the usb perm memory and load on start of the device (so reading from device to the VP configuration). Must be doing something wrong. Anyone any ideas? Just to note it does have changes I made when I first set up the device such as using the wingwin grip - clearly something I've done is the problem 
![Prometheus [Prom]](https://cdn.discordapp.com/avatars/777496628579401739/90d1e9e0a05c7bafd59a74ba942bd870.webp?size=16)
PJust noticed if I open VP configurator directly it populates settings correctly, so it seems this happens when I open the configuration from the telemffb program's menu. possibly a program location issue?
NThere is no functional difference between launching configurator from the TelemFFB menu or launching it directly.
Are you using the vpconf startup feature in the TelemFFB system settings? That will push whatever profile you have chosen every time TelemFFB starts.
Are you using the vpconf startup feature in the TelemFFB system settings? That will push whatever profile you have chosen every time TelemFFB starts.
PThanks. just figured it out (reading the manual again), registry settings set the config location that telemffb uses to locate the config files - I must have moved the location of the configs....[edit] in settings too meh 
TTM is already supported, and Walmis has said directly that FLNKR will be supported.
SCan’t find the any TM grip listed on the configurator pulldown selector, how do I access them?
T“Generic Grip”
TWill work for all CD4021B shift register based grips.
GHi everyone
GThe vkb apdater will that work on a moza ab9?
DI recently started using a physical throw limiter. After calibration the axis all match up correctly in the configurator, but once I get into certain modules the y axis is rescaling by itself. The full Y axis throw is limited down to 50% once the ffb telem kicks in. The limited range is reflected in the configurator and in DCS. If I close out FFB telem I get the full axis again. I have nothing in the effects tab of the configurator turned on. Any help would be appreciated. Thanks.
KDid you use TelemFFB to load an old configuration file?
VHow do I setup trim stick following for DCS OV-10A mod? In game elevator and aileron trim work but stick doesn’t follow trim input.
Nthe community mods (excepting the OH6) don't support FFB. You'll have to either use "Sticky" spring + override trim in the configurator software, or you can use the "Override DCS Spring" feature in TelemFFB and then set your trim bindings in the sub config.
VOk I’ll give that a try. Thanks!
VWill any of the telemffb effects work with the OV-10
V?
NMost stuff should work. I think.
VOkay. Something to play with.
DI dont believe so. So what I noticed today is that its for aircraft that have asymmetric y axis. the F18n has about twice as much pull as it it does push. Whats currently happening is the pull side of the Y axis is being reduced instead of shifting the center point forward.
KThe F/A-18C in DCS has no asymmetric y axis. I have that problem with the A-10CII if I use curves. And I've read the F-5 has the same problem. But F/A-18C in DCS works for me without any problem. But I use virtual end stops and axis resizing at the moment. But I will create a physical end stop soon.
Vso after adding force comp. my stick starts to oscillate on the x axis what can i do to go around that? i only get it when i put force comp im pretty new sorry the questions
AUpdate on this issue - happened while not running Configurator but has not happened since cutting TelemFFB out (4-5 flights).
IIs it possible to upgrade the motors in the Rhino? DCS WWII fighters , the stick gets real soft after a while dogfighting, and the fans turn ON. More powerful motors should help with tis issue.
TNot possible in the stock housing, requires an upsized case. https://discord.com/channels/965234441511383080/1145651561578647582/1284569338996850828
CCan someone explain what I need to tick to make hardware trim work in dcs, trying it out on the viggen and the stick moves the wrong way when I trim. VKB grip.
IBummer, so will need to sell mine and buy a Monster Rhino , have you tried the stronger motors? worth it?
CCant find it in the manual
CWhat do you mean hardware trim in the Viggen?
CI mean, when I trim nose down, the stick travels backwards, and becuase everything is off center after trimming, the "autopilot" cant be engaged, since letting go of the stick will command nose up or down if you have used any trim
CSound like you trim bindings are backwards
CThey are good ingame, any way to flip them in the rhino sw then?
CWhat else did you change in DCS or Vpconfig? This is not the normal usage. I just trim like normally and my stick follows
TI have, but have never tried the standard Rhino to compare to. The regular 60/15 gear ratio of the monster makes it about 1.7x more torque than the standard Rhino but I recently upgraded to 72/15 which is just a hair over 2x the torque of the standard Rhino.
TThe Winger kits are in fact kits though, so you do have to assemble yourself. Plus buy the 86 series motors from Walmis.
TMake sure if you are inverting your pitch axis that it is inverted in the VPForce configurator. And not inverted in DCS.
CAble to fix it?