I can’t reproduce it on 500 so if you can try 499 to see if that is the issue, it would help.
I can’t reproduce it on 500 so if you can try 499 to see if that is the issue, it would help.
HCan't reproduce it on build 500 meaning it is only happening to you on build 499?
NCan’t reproduce it at all. But sounds similar to an issue that was seen on the latest 160 build. Dave said he made the same changes to 160_b83 and 145_b500. I’ve not heard of anyone with issues on b500 but that doesn’t mean there isn’t something unique triggering it.
HCan you export both your vp config file and the file for the telemffb and send over to me? Let me try that and see if the issue is gone.
HOkay tried with Build 499 exactly as shown above same issue.
Nthats good.. means it should be something simple...
My configurator profile won't do you any good. The only important thing is that you have sufficient spring force enabled in the settings tab and that your centering is sufficient, which yours appears to be. Do disable the "override trim" though as that will only mess things up further and make it impossible to find the issue.
From a TelemFFB perspective, literally the only thing you should have to do from the default config is bind your TR button.
Did you go through the basics steps above?
My configurator profile won't do you any good. The only important thing is that you have sufficient spring force enabled in the settings tab and that your centering is sufficient, which yours appears to be. Do disable the "override trim" though as that will only mess things up further and make it impossible to find the issue.
From a TelemFFB perspective, literally the only thing you should have to do from the default config is bind your TR button.
Did you go through the basics steps above?
HI did disable override trim. As for telemffb that's exactly what I did initially was simply bind the TR. Yes I went through the steps in the exact both in build 499 and 500. Same issue. I know the spring force is set properly. No issue when telem ffb isn't running
NI need to know which part of the steps I outlined doesn't work. The entire AFCS implementation in TelemFFB is dependent on all of what I wrote working as described.
HThe stick did not go limp when I started telem ffb
HIs there a way to default the entire telemffb?
Nthen restart it
HI'll give that shot and then just bind the TR button but from what I understand axis control and trim follow is not on by default. Correct?
Nits on by default for the HPG Helicopter type since its required for the AFCS implementation... which brings another point.. I believe you said you were using the default HEMS livery.. but just in case.. make sure TelemFFB is matching on the default profile (i.e., it doesn't pop up and want you to create a new profile). If you're seeing the new aircraft popup.. let me know.
HIt hasn't prompted me to create a new profile and did show matched
Nalso remember that the tablet settings are per livery
HThis I know because I had changed them for each type as described in the vp force manual.
Nanother stupid question.. the axis dot in configurator moves in the correct direction as you manipulate the stick (ie not reversed)? I know this is a stupid question because you already said you don't have anything mapped in the sim and I'm pretty sure you'd have noticed if the stick was moving backwards in the sim 
but if the direction was reversed it could cause a runway condition, so I gotta rule it out...
but if the direction was reversed it could cause a runway condition, so I gotta rule it out...HOkay so I reset the config in telemffb. Exit. Went in fs2020. Loaded aircraft, waited for avionics to fire up. Paused. Started telemffb. Mapped my TR button, verified that the heli has a match in telemffb. Unpause sim, same issue.
Yes the direction of my movements move in the direction I move the cyclic. Nothing is reversed
Yes the direction of my movements move in the direction I move the cyclic. Nothing is reversed
HWhen I load into the aircraft the stick does not move. Stays put but the 2nd I hit the trim release that is when my heli went to the bar and had a few to many
HTrim follow is not on by default. I have it off currently
Nin TelemFFB can you quickly try binding TR to some other button than your usual TR button? any other button on your cyclic will do... just to see if the behavior is any different.
What you are seeing is not something I have ever seen or every heard of anyone else seeing
What you are seeing is not something I have ever seen or every heard of anyone else seeing
HTried a different button. Same result.
HI don't know what's going on and why this happening. I can also try my laptop. I have an instance of fs2020 on it. I can hook up just the stick to that and try and see if I have the same issue.
HSince the memory is stored in the stick shouldn't be an issue
Nmy next best suggestion is if you can screen share with me so I can look at TelemFFB, configurator and the sim at the same time to see what's going haywire. We can try the discord voice chat but the only time I've tried that, the screen sharing resolution was pretty bad (may have been a bandwidth issue from the other user.. not sure)
HLet me try the laptop. Booting up now. This will rule out a pc issue. Next I have another stick I can try to
Nare you using a USB hub? If so, any chance you can try direct attach to motherboard? (I know your setup isn't exactly portable 
). I've not seen issues specific to MSFS or the 145.. but some folks did have wierd force trim centering issues on the latest rhino firmware that were ultimately caused by their USB hubs (grasping at straws here).
). I've not seen issues specific to MSFS or the 145.. but some folks did have wierd force trim centering issues on the latest rhino firmware that were ultimately caused by their USB hubs (grasping at straws here).HOkay same issue happens on the laptop. No USB hub. Plugged directly into the laptop
HOkay I just tried a different random joystick. I mapped a button to TR. Same issue. This it not a pc or joystick hardware issue.
HI wonder is dracks is having the same issue and he gets around it because he has hardware force trim on
Nwhat do you mean another random joystick
Nno.. hardware force trim has nothing to do with it.. it is all modeled in TelemFFB
HI wanted to rule out that my max flight stick cyclic top wasn't the issue so what I did was unplug ghr max flight take a VKB joystick plug that in, ran loop back, found a button, bound, set it in telemffb and press the button on the vkb while I phsycially moved the joystick gimbal with my other hand. Same issue
HBy using the laptop this also rules out FSUIPC and Mobiflight. I don't have any of that extra stuff on the laptop
Nif you want to jump in voice https://discord.com/channels/965234441511383080/965234441511383084 we can try to screen share and I can look at it live.. I can't think of what else to have you try but if I see it live and can watch TelemFFB data and configurator it might jump out at me
HWould zoom call be easier?
HI use discord on my phone not sure how screen share works
Nzoom/teams/whatever will work.. as long as I can see your desktop will DM you
Nif you don't use discord on your PC I dont think it will work well to try to screen share
HJust an update guys, @number481 helped me get the cyclic drift issue resolved. He had me set the hands off detection from 2% to 5% and he had me run a bunch of tests and all is working.
H@Dracks I can confirm that hardware force trim does not need to be checked off in order to function. In the screenshots you sent me I saw it was on.
MWow……hats off to Number481
…..tremendous support!
…..tremendous support!
HAgreed! Amazing people here. We jumped on call together and we walked through a bunch of scenarios and tests. Love this group!
M“Hands off detection”……is that the “Hans on and off dead zone under Axis control in Telemffb??? Can’t see it anywhere else?
HHold on I'll get you a screenshot
NI'm not entirely convinced that the hands-off detection zone was the original culprit, but it is really the only setting we changed from default.. either way I'll take it as a win.
In general however, it is important to make sure that you get reliable hands on/off detection ("OVERRIDE" visible/absent on the PFD) when deflecting the stick against the spring and then releasing it back to center. If you don't reliably get "hands off" (OVERRIDE goes away), AFCS thinks you are still manually overriding and so won't "do its thing".. however simply being in a constant override state should not cause the runaway condition that was originally being seen.
In general however, it is important to make sure that you get reliable hands on/off detection ("OVERRIDE" visible/absent on the PFD) when deflecting the stick against the spring and then releasing it back to center. If you don't reliably get "hands off" (OVERRIDE goes away), AFCS thinks you are still manually overriding and so won't "do its thing".. however simply being in a constant override state should not cause the runaway condition that was originally being seen.
FSo it was something simple! Just had to figure out what it was 
FThe fact that the software can detect a hands on/hands off setting is amazing to me. So cool.
HYeah, so odd. We really only changed one thing but here's the kicker I went and plugged the rhino into the laptop. Completely separated from my desktop. It did the same exact thing where it drifted. 1 usb cable, no extra programs besides loop back and telem.
Ssystem menu, open config/log directory. rename userconfig.xml to somethign else. reopen telemffb