most things you can edit/save the config or the user config live (keeping in mind that userconfig wi
most things you can edit/save the config or the user config live (keeping in mind that userconfig will override primary config)
BI did not know that!
NYessir.... the only things you cant modify on the fly are the system variables (like enabled sims, etc).
Also, you can't add a new aircraft section while live either. That will require a restart (of telemFFB).
Also, you can't add a new aircraft section while live either. That will require a restart (of telemFFB).
Ai would say in general, avoid using friction, use damper instead
Ai.e. jack damper back up to 100%, (probably worth doing the same with inertia as well), and maybe keep friction in the Settings tab at 10% or lower, and also yeet it from the effects tab and instead add some damper to give it that mechanical feeling
Sthe thing is that I had friction all 100 with no issues prior the last update from TelemFFB
Sshould I remove Friction in the effects tab too?
Swhat is this? often it happens and I have to restart TelemFFB.
STraceback (most recent call last):
File "main.py", line 449, in process_data
File "aircrafts_msfs.py", line 712, in on_telemetry
File "aircrafts_msfs.py", line 680, in on_telemetry
File "aircrafts_msfs.py", line 571, in _update_flight_controls
File "simconnect\sc.py", line 197, in send_event
File "simconnect\datadef.py", line 137, in map_event_id
File "simconnect\sc.py", line 66, in _callable
File "_ctypes/callproc.c", line 993, in GetResult
OSError: [WinError -1073741648] Windows Error 0xc00000b0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "traceback_with_variables\print.py", line 67, in printing_exc
File "traceback_with_variables\print.py", line 98, in wrapper
File "main.py", line 488, in run
File "main.py", line 453, in process_data
File "traceback_with_variables\print.py", line 39, in print_exc
AttributeError: 'NoneType' object has no attribute 'write'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "threading.py", line 1009, in _bootstrap_inner
File "traceback_with_variables\print.py", line 92, in wrapper
File "contextlib.py", line 153, in exit
File "traceback_with_variables\print.py", line 70, in printing_exc
File "traceback_with_variables\print.py", line 39, in print_exc
AttributeError: 'NoneType' object has no attribute 'write'
File "main.py", line 449, in process_data
File "aircrafts_msfs.py", line 712, in on_telemetry
File "aircrafts_msfs.py", line 680, in on_telemetry
File "aircrafts_msfs.py", line 571, in _update_flight_controls
File "simconnect\sc.py", line 197, in send_event
File "simconnect\datadef.py", line 137, in map_event_id
File "simconnect\sc.py", line 66, in _callable
File "_ctypes/callproc.c", line 993, in GetResult
OSError: [WinError -1073741648] Windows Error 0xc00000b0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "traceback_with_variables\print.py", line 67, in printing_exc
File "traceback_with_variables\print.py", line 98, in wrapper
File "main.py", line 488, in run
File "main.py", line 453, in process_data
File "traceback_with_variables\print.py", line 39, in print_exc
AttributeError: 'NoneType' object has no attribute 'write'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "threading.py", line 1009, in _bootstrap_inner
File "traceback_with_variables\print.py", line 92, in wrapper
File "contextlib.py", line 153, in exit
File "traceback_with_variables\print.py", line 70, in printing_exc
File "traceback_with_variables\print.py", line 39, in print_exc
AttributeError: 'NoneType' object has no attribute 'write'
NIf you have friction enabled, and your hand is the only thing moving the stick, the oscillations might not occur. However, s soon as the trim/AP following in latest TelemFFB is moving the stick by itself without your hand on it to stop the oscillations from beginning to amplify.. that can absolutely start the oscillations.
Also... while your friction slider is %100.. you are limiting it to %20 in the effects tab.. important to understand how the two tabs work together.
Also... while your friction slider is %100.. you are limiting it to %20 in the effects tab.. important to understand how the two tabs work together.
NCan't say for sure. I've not seen that myself nor had any other reports of similar errors...
It looks like an issue with the simconnect code sending the axis position to MSFS.
How is the stability of your USB connection to the Rhino? Does it ever momentarily disconnect/reconnect by itself?
It looks like an issue with the simconnect code sending the axis position to MSFS.
How is the stability of your USB connection to the Rhino? Does it ever momentarily disconnect/reconnect by itself?
Sno, just happens in the sim
W0xC00000B0 is a Windows kernel "disconnected pipe" error. Simconnect should recover automatically and probably would be a good idea to put the
send_event
Neasy enough!
Sglad to help 
Sok, I believe its the engine rumble effect that causing the disconnect of X axis
WCan you check the fault code when the axis disconnects? It's in the bottom right in the status bar of the VPConf application
Ssdby i'll do it again, I'm in Vr and i doesnt help to this kinds of tests
S
Shere better than copy the text
Shope not too much serious.. to my end......
Sthats why I could recover from it by pressing the red button and then restart it
WThe safety algorithm is a bit too sensitive, I'll send you a firmware update later
Sthanks
Scan I reduce the engine tumble too in telemFFB? Look too much
Smeanwhile I turn it off
WYeah, there are parameters for reducing the engine rumble
Nyou can add these to the msfs propeller aircraft config, or to a specific aircraft section:
Nintensity decreases as RPMs increase (defined by the high/low RPM and intensity settngs)
NI should (and will) add the defaults to the MSFS section
WThere's also jet engine and afterburner rumble parameters
Nwas just assuming they were still flying the comanche based on previous discussions 
Syes yes always the comanche!!! i'm true love this month!!! I personally like more the Dash 8 Q200 but i'm on vacation 
A@walmis do you know if there's any way to get rid of those chrome/edge webusb notifications? is this just a by product of the type of APIs used by the firmware?
Ai.e. whenever a rhino is plugged in, they pop up
Nuninstall all traces of Edge from your machine and then call a witch doctor to make sure it is pure... then install Brave
NI can't get Edge to stop it either... then the notifications get 'stuck' and the only way to get them to go away is to kill all the edge processes
Achrome does it too lol, so i get double
Abut none of my other controllers have this problem, i assuming it's something related to a webusb api?
Ayeah, if i forget to close it, it seems to get stuck heh, and with an ultrawide, it's something that can sometimes be missed lol
NOnly have Edge and Brave (my default).. Brave will popup if you plug/replug.. but it goes away by itself or you can close it.. edge is a PITA and I think their WebUSB is messed up
Auninstalling the browsers isn't something i can really do given my line of work/job
NI did find some documentation on hard-disabling WebUSB in Edge via GPO but never went very far down that path
WThere's a chrome flag that might help:
Nedge seems to ignore that (I have it disabled)
Aoh sick, will def shut this off in chrome
Ai'll try both of these! much appreciated!
Adoing this in chrome and edge appears to have fixed the problem! thanks!
Shi, with the new version and after testing, the engine rumble makes the rhino rumble a lot making it disconnect the X axis as before. but I noticed that if I cut the engine the effect goes away in the TelemFFB but the rhino keeps rumble. any idea? I'll turn it down at low RPM and check. if not I have to turn it off for now
Nit is unlikely that any of the rumble effects are causing your axes to go into protection mode and disconnect. If your screenshot above 🧰support is still accurate, you have the "Periodic Effects LPF" set to 0Hz.. I can't give you a technical explanation, but I can tell you that that will not play nicely with the effects in TelemFFB. The default is 20Hz I believe
WOh yea, didn't notice that! 0Hz on periodic will definitely cause problems, set it to 20Hz @snooperoldschool