were you on the very latest version before you updated to this version?
were you on the very latest version before you updated to this version?
Nwhy did you enable auto launch for a device you dont have? 
OK.. so it shouldn't let you save under that condition but....
OK.. so it shouldn't let you save under that condition but....Nif so.. check this folder for your backup... if not.. well... moving forward... you can check this folder for the backup from the previous version
Ithnaks for the tip about the last version, I didn't know
NIts a brand new feature that I shoved into the very last commit before this new version and didn't document anywhere.. 
NWere you able to get the new version started with only the pedals selected in the launch options? Because of the error state you may need to delete the system settings from the registry... Computer\HKEY_CURRENT_USER\Software\VPforce\TelemFFB you can just delete the whole TelemFFB key
Njust pushed a new build that should fix the DPI scaling, disallow erroneous autolaunch configs and allow you to at least startup with your corrupted registry settings (though you will see "cant connect to "FFFF:" errors)...
E@walmis Recently, I've been experiencing frequent protective shutdowns on the Y-axis. I will make a video to show the situation. At that time, I will also share my debugging and configuration files. Could you help me take a look and see where the problem might be?
E@walmis Recently, I've been experiencing frequent protective shutdowns on the Y-axis. I will make a video to show the situation. At that time, I will also share my debugging and configuration files. Could you help me take a look and see where the problem might be?
EThis issue often occurs during stall shuddering and the instant of firing the machine gun, and it always results in a shutdown of the Y-axis.
WHey, try reducing the damper/inertia/friction LPFs in the configurator, I see you use all the effects simultaneously (damper/inertia/friction) so that might cause instabilities with the current settings.
EWhat would be the appropriate values to set for each LPF?
WTry experimenting, but I've found down to 2Hz is slow, but reliable
WNo worries, your Rhino is safe, motors enter into self protection if there is unusual stuff happening.
You can follow the manual to retighten the belts:
https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y/edit#heading=h.z337ya
You can follow the manual to retighten the belts:
https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y/edit#heading=h.z337ya
PHey guys how do I go about downloading & installing the new TelemFFB software? can I just do a git pull? or should I reinstall?
Plol, nvn I used my brain & found the download
Nif you're running the exe package, it will auto-update
Poh I've just been using the python install of telemffb & doing a git pull to update, but I just dl'ed the new version & used the .exe, will that be ok? cheers
Palso thanks heaps for all the work you & others done with this
Nyeah, just make sure you grab the latest zip from #VPforce-TelemFFB . The 'stable release' posted on GitHub is a snapshot of the WiP branch from a couple days ago.
Poh the bottom link?
P3017d8df
Nyeah.. or you can hit the link in the pinned messages in that channel which should bring you to the download site with the page already sorted by newest
Pyeah sweet looks like I dl'ed the 3017d8df one, so I'm on the new one?
Nyessir
Nhah.. runway rumble is one of those weird effects that didn't blow up if you set the value higher than 1.0 in the original configs and I think there were some aircraft that had that set as the default.
One of the new aspects of this new UI is that the settings sliders can be made so that they only offer a useful range, even though they display %0-100.
So many of the usable effect intensity values are in the 0.1-0.2 range, that the sliders are actually applying a scaling factor under the hood to 1.) only provide a usable setting range and 2.) give more granularity inside that setting range.
So there are some artifacts like that (%750) on a few of the old default values.
One of the new aspects of this new UI is that the settings sliders can be made so that they only offer a useful range, even though they display %0-100.
So many of the usable effect intensity values are in the 0.1-0.2 range, that the sliders are actually applying a scaling factor under the hood to 1.) only provide a usable setting range and 2.) give more granularity inside that setting range.
So there are some artifacts like that (%750) on a few of the old default values.
Nthe slider range for the runway rumble may need to be adjusted (in a subsequent version)
Pahh ok lol, once I touched that slider & set it to full it's at 100%, hiting the 'x' will put it back to 750%
Nyeah, the x button reverts the setting to what is in the default config
NBTW, since you migrated from source.. you can take your old user config and drop it in the exe folder. If it is named
If it has a different name, you will need to start telemFFB with the
config.user.iniIf it has a different name, you will need to start telemFFB with the
-o <userconfig filename>oh I never editied the .ini
Tvirus detected on Windows 11
VPforce-TelemFFB-wip-3017d8df (latest release)
VPforce-TelemFFB-wip-3017d8df (latest release)
MJust updated to TelemFFB 1.0, getting this error on trying to convert the user.ini, halp?
J@walmis @Number481 The latest auto update has made a mess. It did not restart after the update and the updater now enters a continuous cycle of updating from the former start shortcut. No new install location can be found. Is there a manual version of importing the previous *.VPconf files and User.ini?
Mexept in my case it does not work?
Ncommon occurence for apps bundled with pyinstaller.. Windows defender and some other AV tools will sometimes flag a given build as a virus. This is because it is written in Python and compiled with ‘pyinstaller’ which can sometimes result in certain partial file hashes that have been previously found in low tech malware that is commonly also written in Python and compiled with pyinstaller
Nmore info needed.... does it crash? does it say it did something but nothing happened? does it do nothing at all?
Nrecommend trying not launching from a shortcut. launch directly from the exe.. but if the in-pace install is already corrupted, it might be easier just to grab the latest zip distribution and start fresh https://vpforcecontrols.com/downloads/TelemFFB/?C=M;O=D
Mmh, it crashes and the .xml config has nothing in it.
Mif I say "no" to the initial config.user.ini conversion prompt it behaves normally.
MI mean, it starts, but if I try the conversion from Utility it crashes silently before doing anything
Ninteresting... send me your userconfig if you don't mind... I'd like to investigate why its failing. If the config worked with the previous TelemFFB without error, it should convert over.
Msure, DM?
Nthat works
TTelemFFB (3017d8df) shows errors for HPG160 and MSFS
But telemffb_controls_axes is enabled and cyclic axes are not bind.
How can I solve this?
But telemffb_controls_axes is enabled and cyclic axes are not bind.
How can I solve this?
Ttelemffb_controls_axes = enable in the 2 locations.
TNot working 
Nresolve the issue in the log message....
and
I'll look to see if there's an issue with the default settings because the axis control should be enabled by default for those helicopters
and
I'll look to see if there's an issue with the default settings because the axis control should be enabled by default for those helicopters
T
Axis control checked now! And button configured!Thanks!