what aircraft are you flying? You have TelemFFB setup and connecting to MSFS (showing telemetry)?
what aircraft are you flying? You have TelemFFB setup and connecting to MSFS (showing telemetry)?
Myeah I know joystick gremlin like, a lot, I was just hoping in a native solution...
MAnother question, I have pulled the TelemFFB (the python version), installed the requirements and all but when I try to launch it I get
..\python main.py
Traceback (most recent call last):
File "..\Desktop\Joystick\VPforce-TelemFFB\main.py", line 81, in <module>
from PyQt5 import QtWidgets
ImportError: cannot import name 'QtWidgets' from 'PyQt5' (unknown location)
..\python main.py
Traceback (most recent call last):
File "..\Desktop\Joystick\VPforce-TelemFFB\main.py", line 81, in <module>
from PyQt5 import QtWidgets
ImportError: cannot import name 'QtWidgets' from 'PyQt5' (unknown location)
Many idea?
MI'm trying to install the latest version I can find, from python (3.11.5 ?)
Mnevermind, Updating python, doing a git reset and pull seems to have fixed the issue.
JFlying a helo. Yeah it’s connected, at least it says it is
Nwhich helo? Unlike DCS, there aren’t a lot of default aircraft profiles inside the config. You need to make sure there’s an entry and that it’s identified as a helicopter.
NAnd for helicopters you will either have to use the VPf configurator sticky spring + force trim. Or you can enable the force trim implementation in TelemFFB MSFS.Helicopter section.
JI bought the H145.
JI'll research this
KQuick question, of course I did edit the normal user.ini and not the README.ini… is there a way to correct it and get the original back? Sorry if that’s a stupid question, maybe there is a button to reset it but I am not home at my PC these days.. just re-reading the manual again and thought I should better follow the correct way with both .ini
NThere is no harm in editing config.ini directly. Only that it will get overwritten if you unzip a new version on top of it.
You can simply rename your current one to config.user.ini and then copy the default config.ini out of the original zip file if you want.
You can simply rename your current one to config.user.ini and then copy the default config.ini out of the original zip file if you want.
BI didn't know you could turn on h/w trim in the TelemFFB config.user.ini file. What do I need to add to the ini file to turn on h/w trim in MSFS without having to switch it on and off in the Configurator app? (I bounce between MSFS and DCS constantly.)
BSorry I totally missed that note. Thanks!
Nyou mean you don't monitor the discord like a hawk and take notes on every post?? SHAME!.. 
BWell I surely didn't realize that config.ini had been enhanced so much since the last time I copied it to config.user.ini!!! Suggestion: add a version note to the top of config.ini...
Sthe user.ini shouldnt be a copy of config.ini, it should just have the things you are overriding.. mine has msfs_enabled=1 and a couple heli configs.
B<slaps forehead> you're completely correct. Sometimes I wonder how I got through high school, let alone college 
NIt can be a full copy..but it doesn’t need to be.
BI much prefer just having the changed stuff in the user .ini. It's much much easier to find stuff! I just deleted all of the stock content in the file; hopefully I didn't screw anything up.
BSo I couldda sworn I had the Shrike MD530 working with TelemFFB, but I'm getting exceptions now. One line leads me to believe that it's not picking up the "530F.*" entry that I added. But what's weird is that the Cowansim MD500E works fine, and their entries are identical.
The line that makes me think that is this: INFO - Creating handler for Shrike Simulations 530F Default: aircrafts_msfs.Aircraft
I get three exceptions when the aircraft starts. Here is the first:
Exception in thread Thread-2:
Traceback (most recent call last):
File "main.py", line 391, in process_data
File "aircrafts_msfs.py", line 383, in on_telemetry
File "aircraft_base.py", line 351, in _update_buffeting
File "utils.py", line 401, in scale_clamp
File "utils.py", line 393, in scale
ZeroDivisionError: float division by zero
config.user.ini entries:
[500E.*]
type=Helicopter
runway_rumble_intensity = 0.5
rotor_blade_count=5
etl_start_speed = 15kt
etl_stop_speed = 25kt
etl_effect_intensity = 0.40
overspeed_shake_start = 120kt
overspeed_shake_intensity = 0.2
[530F.*]
type=Helicopter
runway_rumble_intensity = 0.5
rotor_blade_count=5
etl_start_speed = 15kt
etl_stop_speed = 25kt
etl_effect_intensity = 0.40
overspeed_shake_start = 120kt
overspeed_shake_intensity = 0.2
Maybe it's something with the 530F header. How do I determine the string that I should put in there -- is it something in the aircraft's manifest.json, or something else?
The line that makes me think that is this: INFO - Creating handler for Shrike Simulations 530F Default: aircrafts_msfs.Aircraft
I get three exceptions when the aircraft starts. Here is the first:
Exception in thread Thread-2:
Traceback (most recent call last):
File "main.py", line 391, in process_data
File "aircrafts_msfs.py", line 383, in on_telemetry
File "aircraft_base.py", line 351, in _update_buffeting
File "utils.py", line 401, in scale_clamp
File "utils.py", line 393, in scale
ZeroDivisionError: float division by zero
config.user.ini entries:
[500E.*]
type=Helicopter
runway_rumble_intensity = 0.5
rotor_blade_count=5
etl_start_speed = 15kt
etl_stop_speed = 25kt
etl_effect_intensity = 0.40
overspeed_shake_start = 120kt
overspeed_shake_intensity = 0.2
[530F.*]
type=Helicopter
runway_rumble_intensity = 0.5
rotor_blade_count=5
etl_start_speed = 15kt
etl_stop_speed = 25kt
etl_effect_intensity = 0.40
overspeed_shake_start = 120kt
overspeed_shake_intensity = 0.2
Maybe it's something with the 530F header. How do I determine the string that I should put in there -- is it something in the aircraft's manifest.json, or something else?
NIt shouldn't be throwing exceptions (I'll have to DL some freeware helis and see if I can reproduce it). But generally you can get the "simconnect name" (my madeup name for it) by loading the aircraft in TelemFFB and seeing what is listed in the telemetry window. If it is erroring out before that happens, take a look at the log to see what it says about the aircraft name when it is looking for a match in the config.
BSorted. It wants [Shrike.*] not [530F.*]. Like I said I couldn've sworn it was working before, but... I might be wrong.
Ninteresting... are these two variants of the same aircraft/developer? What does the telemetry say about "StallAoA"? Looking at the exception logs you posted origionally trying to determine whats causing it to bomb out.
BNo -- two different devs (CowanSim and Shrike). Stall AOA is 0.00. But note that when I have the header as 530F.* these lines are logged:
2023-09-30 12:42:56.524 - INFO - Loading parameters from 'MSFS2020' section
2023-09-30 12:42:56.527 - INFO - Creating handler for Shrike Simulations 530F Default: aircrafts_msfs.Aircraft
But with Shrike.*, I get
2023-09-30 12:41:12.666 - INFO - Loading parameters from 'MSFS2020' section
2023-09-30 12:41:12.669 - INFO - Found section [Shrike.*] for aircraft 'Shrike Simulations 530F Default' in config
2023-09-30 12:41:12.670 - INFO - Loading parameters from [MSFS2020.Helicopter] section
2023-09-30 12:41:12.670 - INFO - Creating handler for Shrike Simulations 530F Default: aircrafts_msfs.Helicopter
So it's like if it can't find a valid entry for the aircraft, it doesn't see it as a helicopter. Everybody knows that helicopters that self-identify as an airplane will cause exceptions to be thrown
2023-09-30 12:42:56.524 - INFO - Loading parameters from 'MSFS2020' section
2023-09-30 12:42:56.527 - INFO - Creating handler for Shrike Simulations 530F Default: aircrafts_msfs.Aircraft
But with Shrike.*, I get
2023-09-30 12:41:12.666 - INFO - Loading parameters from 'MSFS2020' section
2023-09-30 12:41:12.669 - INFO - Found section [Shrike.*] for aircraft 'Shrike Simulations 530F Default' in config
2023-09-30 12:41:12.670 - INFO - Loading parameters from [MSFS2020.Helicopter] section
2023-09-30 12:41:12.670 - INFO - Creating handler for Shrike Simulations 530F Default: aircrafts_msfs.Helicopter
So it's like if it can't find a valid entry for the aircraft, it doesn't see it as a helicopter. Everybody knows that helicopters that self-identify as an airplane will cause exceptions to be thrown
NIf you're able to reproduce the exception.. I'd love to have a copy of the stack trace from the log.
BIs this what you need?
exception_snippet.txt2.64KB
NYep.. thats from the shrike? (same error for likely the same reason as Cowan if so)
NI figured out why its happening if you want to know how the sausage is made :). Well, I pretty much knew why it was happening but I didnt understand why simply setting the aircraft type fixed it.. now I understand.
Mis there a way I can map another usb device's buttons to control hardware trim, as one of my joysticks has a wire running down to a leo bodner card?
BExcellent, and yes that was from the Shrike. Most of the time, it's fun to gather data and figure out something that's not working.
Nwithout the aircraft type, the app assumes "generic aircraft" and loads all the default parameters. One of these paremeters is the buffeting intensity. The buffeting effect uses the reported stallAoA from the telemetry to calculate the effect... Aircraft is reporting 0.0 so that results in a divide by zero error.
With aircraft type, the helicopter type doesn't have the buffeting intensity defined, so the effect is skipped, so no error.
With aircraft type, the helicopter type doesn't have the buffeting intensity defined, so the effect is skipped, so no error.
Mone more thing, I downloaded telemffb and I try to edit the file for msfs suport but can't find the entry. where is it?
Bconfig.ini has sections for MSFS, both for the sim and (further down) entries for some of the default aircraft. Search for [MSFS2020].
You can create a config.user.ini to override most anything (if not anything; I'm not sure) in config.ini. I prefer treating config.ini as a read-only file.
You can create a config.user.ini to override most anything (if not anything; I'm not sure) in config.ini. I prefer treating config.ini as a read-only file.
NStep one is make sure you have the right version. The "release" build (0.1.3) didnt have support for MSFS. Grab the latest from the pinned post in #VPforce-TelemFFB and then do as blave says
MThanks so much!
Mah. anytime i open fs2020 it crashes on flight loading then once its in safe mode its fine.
NAre you saying TelemFFB is causing MSFS to crash? That would be very unlikely. All it does is request sim connect data.
MYeah that’s what’s happening
MI have excluded every other possible issue
Nbut TelemFFB works with MSFS when its in safe mode? I dont know if MSFS disables simconnect in safe mode or not. AAIK, it just doesn't load any mods whatsoever. If so, it is something else causing it to crash.
MYeah
MI figured
NMay have to start with an empty community folder and start moving things back in until you find out what combination is causing it to crash.
MYeah. Good idea. And is there any way possible to map force trim buttons to a usb device that is not connected to the rhino? Like I have a real aircraft grip and there’s a wiring harness that runs down to a usb circuit board. Can I map the motorized trim to something like that?
NMight be possible with the rhino loop back app. I’ve never tried to use it.
WYeah, you can use the loopback app that's included in the VP configurator app package. Set the grip type to loopback and you're good to go.
Mthanks!
BI'm trying to add the freeware Cessna T-37 to the TelemFFB user config file. This is what the log says:
2023-10-01 10:05:13.375 - INFO - Loading parameters from 'MSFS2020' section
2023-10-01 10:05:13.378 - INFO - Found section [Cessna T37.*] for aircraft 'Cessna T37 B Tweet' in config
2023-10-01 10:05:13.379 - INFO - Loading parameters from [MSFS2020.JetAircraft] section
2023-10-01 10:05:13.379 - WARNING - Section [MSFS2020.JetAircraft] does not exist
2023-10-01 10:05:13.379 - INFO - Creating handler for Cessna T37 B Tweet: aircrafts_msfs.JetAircraft
Is the warning significant, or can I ignore it? It's not clear to me if it's actually picking up the data in the Cessna T37.* section.
2023-10-01 10:05:13.375 - INFO - Loading parameters from 'MSFS2020' section
2023-10-01 10:05:13.378 - INFO - Found section [Cessna T37.*] for aircraft 'Cessna T37 B Tweet' in config
2023-10-01 10:05:13.379 - INFO - Loading parameters from [MSFS2020.JetAircraft] section
2023-10-01 10:05:13.379 - WARNING - Section [MSFS2020.JetAircraft] does not exist
2023-10-01 10:05:13.379 - INFO - Creating handler for Cessna T37 B Tweet: aircrafts_msfs.JetAircraft
Is the warning significant, or can I ignore it? It's not clear to me if it's actually picking up the data in the Cessna T37.* section.