Isn’t the auto switch a function of TelemFFB, not the configurator?
Isn’t the auto switch a function of TelemFFB, not the configurator?
CGot it working, thanks!!
GYeah TelemFFB is auto switching between profiles ok but VPforce no longer is ???..
BThe configurator never had auto switching, it was always telmeffb.
GThat's strange, for the the past month up until this morning my configurator was changing profiles ???. Which was great, now i have to change the aircraft profile manually, which is no big deal as i only ever really play the same three modules..... but having the automation was nice whilst it lasted :)...
Fyou can set and adapt profiles in TelemFFB which is way better in my opinion because it changes profiles automatically.
GYeah i notice in TelemFFB that there is a configuration override option where you can adjust the spring, damper, master gain etc etc. The trouble is that i make use of a feature called "Gain map" within the configurator "effects" tab where i can adjust the spring gain curve of the "aileron" individually for instance. My preference is to generally set the pitch axis spring gain to feel stonger than the aileron axis as i prefer a lighter feel on the ailerons.
BThere's also a spot where you can select a vpconf file to load.
GYeah that's what i've been using over the past month, my understanding was that i can configure my profile to my liking in VP configurator and then tell TelemFFB to load that profile for that particulur aircraft. It's been working fine up to now, however it dosen't seem to be doing that anymore . Whatever profile i have imported in to VP Configurator is the one that it will continue to use regardless if i change my aircraft in DCS to a helicopter, WW2 bird or a jet..... i need to investigate this further and maybe try and uninstall/reinstall TelemFFB again.... somethings amiss here...
NCheck the log. If there’s an issue loading or finding the file, it will tell you.
Salso, while playing the game telemffb has to remain running, but configurator does not.
CNeed help I'm getting this error
C
SI unplugged my vpforce for a moment as it was conflicting on a game, now i'm back flight simming and i get this and no feedback at all. i have updated telemffb, i have tried multiple planes, restarted msfs twice and started in the correct order. And reset effects
Swhen you open configurator, does it present you a selection like this? then, enter your numbers in telemffb
GYeah that was the problem, for some reason it was no longer recognising my .vpconf files in their original location. Moved them elsewhere and TelemFFB is now loading them ok..... thanks for everybodies input 
CNo, only in telemffb but can't open it anymore
Smight be a usb issue if none of the apps see it
CI entered the wrong PID. Is there a way to delete and start over
Syou can edit the numbers in regedit
CThanks will try it
Sto really start over, you can delete that whole TelemFFB registry folder (its only for the system settings, your planes and profiles are stored elsewhere)
CIt worked. Thanks so much
VDoes anyone ever have problems with the buttons not all working on your stick?
KNo. Which Stick do you have? I use a Thrustmaster Warthog Stick and all is working.
VWinwing stick with attachment
Vto make it work. most buttons work but not all. guess i’ll have to get a TM. Seems something is always up with the winwing and the vp force unless i’m doing something wrong in the configurator
WWhich buttons do not work? WW F-16EX?
VYea F16EX. I will have to check the WW simapppro and find the exact button numbers but the gray (trim) hat switch in all 4 directions plus pressing down doesn’t work. As well as the black 4 way hat switch below it and to the left of it. But again i will have to get back on here in a bit and see which exact buttons don’t work.
THave you tried using the option for hats as buttons? Either checked/unchecked.
VI will try that here shortly and report back. Thanks!
WAlso make sure to select WW adapter grip profile
VI just saw that in the manual as well! Thank you! I will check the manual better next time before reaching out.
Absolutely love my Rhino!
Absolutely love my Rhino!
VThis was it! Thanks again!
MI had a look around and I could not find an answer, only somebody asking a similar question before: I can not get the configurator to recognize the brake lever as well as some of the buttons on my first generation T-50CM, when using the T-50CM2 grip type. Is there any workaround, or solution?
T@Touch_Of_Legend may be able to help if not Walmis himself
TI’m using that grip (Virpil CM not the CM2) but I’m not home at the moment.
I remember you have to select the CM2 and someplace in the configurator you select (something) and it brings up the box so you can calibrate the brake lever as Axis.
I got it all working great but it’s been awhile since I did it so it “might” be in my previous posted comments or else I’ll try to dig the info out for ya later today
I remember you have to select the CM2 and someplace in the configurator you select (something) and it brings up the box so you can calibrate the brake lever as Axis.
I got it all working great but it’s been awhile since I did it so it “might” be in my previous posted comments or else I’ll try to dig the info out for ya later today
CHello all. I have been having a problem with the Rhino.
Sometimes when I start DCS, the stick loses all motor function untill I reboot DCS and the telemffb software.
Also, when flying the Apache in DCS, if change seats to the gunner position and spend too much time without using the stick, when I return to the pilot's seat the stick is dead as well.
How do I go about determining if this is a Windows issue, DCS issue or otherwise in the software?
The only steps i have taken so far is to verify that USB Selective Suspend is disabled
Sometimes when I start DCS, the stick loses all motor function untill I reboot DCS and the telemffb software.
Also, when flying the Apache in DCS, if change seats to the gunner position and spend too much time without using the stick, when I return to the pilot's seat the stick is dead as well.
How do I go about determining if this is a Windows issue, DCS issue or otherwise in the software?
The only steps i have taken so far is to verify that USB Selective Suspend is disabled
MIf it is the boxed option, then that is the problem, it reads no raw value, so calibrating it yields no result. The raw buttons are recognized, but the configurator isn't picking them up as the Virpil axis. One of the 4 way hats is also not recognized
MFunnily enough, if I set the grip type to VPC V.F.X, it recognizes all buttons and the lever is assigned as the twist axis
HDo you hear the disconnect chirp?
TI’m sure you could use it this way, doesn’t have to be bound as twist in game.
TCheck the debug/log file. Sounds like maybe a timeout issue on the gunner seat. But stick does go limp when starting DCS until a module/mission is loaded.
MIt is almost a solution, yes, but even then I have been unable to tune it so that it actually uses the entire range. I tried several tunings, but I could only get it to give me 1/4 of the axis
TTry selecting the debug grip and post a screenshot of the debug tab. Walmis will able to ID right away if he sees it but for my sake flex the brake axis a bit while the debug is running to show how the bits are processing.
TYou could also try the warbrd profile.
CNo chirps or anything on either problem and the software shows motors OKAY
CI will test tonight.
If it is a timeout issue, is there anything workaround or setting I'm missing?
If it is a timeout issue, is there anything workaround or setting I'm missing?
MHere you can see the 4th byte being the lever, then me using the missing 4-way, doing its thing on the bits 20-24
TIt looks like bits 5-8 are getting involved too. FF to FB when byte 4 is changing.
Unfortunately I don’t have a fix for you. I am more up on TM/WW protocols with VPF. My hope was it would look more like one of those. Might be time to ping Walmis.
Unfortunately I don’t have a fix for you. I am more up on TM/WW protocols with VPF. My hope was it would look more like one of those. Might be time to ping Walmis.
MOh, the early bit is the lever "button" which works, so that ain't an issue and can be ignored.I had a feeling there was no easy fix, this is on the driver-isch level