Sorted. It wants [Shrike.\*] not [530F.\*]. Like I said I couldn've sworn it was working before, but
Sorted. 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.
NYa. You can ignore it. There isnβt a default βjetβ section in the config for MSFS (though there will be in my next update). The part that tells you it is properly loading your config is
NItβs stil picking up the relevant jet configs from the default MSFS section, but there is currently no separate default section for the jet type.
οΏ½@walmis I'm having no luck getting my Rhino to recognize my WinWing F-16 grip. I have the Grip at the end of a Virpil Z-extension and the WinWing adapter. I thought it might be the Grip going bad but I just received a new Grip from WW and still no joy. I've previously attached the Grip directly to the Rhino via the adapter (without the extension) and that didn't work. If I connect a Virpil Alpha directly or via the Z-extension, it recognizes the buttons. All of these problems started after I updated 1.0.16. Can I roll back to 1.0.15? Any other suggestions? Screenshots below of my settings and debug output.
WFrom the log it looks like the adapter itself works, but it doesn't detect the WW grip via the 6pin connector. Is the WW cable fully seated?
οΏ½Yes, I've got it down in there as far as it will go. Could the issue be with the adapter even though it shows up? I'm sending one of my WW Grips to a friend that also has a Rhino and WW Adapter to test.
WIt's possible. I've found the socket pins on the 6pin connector sometimes could be in too deep (I've made a video on how to fix it: https://photos.app.goo.gl/um8ZC7NgLJRGkY5U7). The newest adapters (after 2023 July) don't have this problem. If you have a multimeter I could guide you how to test it. If all else fails, I could mail you a new core PCB with connectors.
οΏ½I do have a multimeter so please DM the guide. Thx.
WWill do tomorrow, cheers
MOkay I set the setting to loopback and when I go to the trim buttons I canβt figure out how to map them. I click the buttons but nothing happens.
MIs there something else I need to do? I have just set grip type to loopback and then tried ti set the buttons.
MNever mind I figured it out! It was in the manual haha.
SSo, I'm finally back in front of the pc
Here are my current settings
General feeling : way too light
Here are my current settings
General feeling : way too light
SThis feels better actually
SI guess it's gonna need some fine tuning 
AThose settings seem way off 
how long is your extension?
how long is your extension?S20 cm
SWay off for what ?
SI'm just trying to get a "good" feeling, I must admit I have no clue what I'm doing 
A20cm is a bit on the longer side, but thatβs a lot of effects I feel like
W@simon2012 I guess you're after center stiffness? Currently the whole force is distributed linearly through the whole throw range, so with an extension it might feel sloppy. Try "Axis scaling" at 50% and see how that goes.
SYes, what I'm definitely missing with the out-of-the-box settings is center stiffness
I'll give a try with axis scaling
I'll give a try with axis scaling
SBy the way, I love the fact you can modify the settings on the spot, super convenient for testing !!! 
TTried DCS with the Rhino for the first time today, the P-51D.
Is there a way to turn down/off engine & gunfire FFB?
Is there a way to turn down/off engine & gunfire FFB?
TIts rattling like h3ck for just barely making a slight bank left or right, whereas in IL-2 it starts rattling when getting close to the limit/edge, at that same point in DCS it nearly knocks a hole in my floor, obviously that's not a tenable situation 