MBut the rhino is way different
WI guess that's with the Brunner's telemetry software?
MYeah. You don’t even need hardware trim. Xplane automatically sends the data to brunner. If you are interested with anything brunner, ask me. I have their pedals and stick. If you even want to test it I can help with that.
MAs I am moving to rhino now.
Nam I correct in my understanding that for X-Plane it requires you to edit each aircraft to change the trim behavior so that it works properly (software trim method)?
MYes. It sucks but in the end it’s really nice, and realistic.
TJust got my Rhino today, reading the readme and trying to get things working, first order of business seems to be an error when trying to run TelemFFB?
Currently running Windows 10 (latest version).
Currently running Windows 10 (latest version).
Nwhat do you see here when you look at the configurator?
THang on, will advise
T2055
TAnd I did store settings in the configurator, heard an audible "blip" from the base when I did so.
Nwhat version of telemFFB are you running?
TCurrently the newest stable version, 0.1.3
Nlikely not related since afaik the older 'stable' version should still at least connect to the Rhino.. but you'll probably want the latest from here: https://vpforcecontrols.com/downloads/TelemFFB/?C=M;O=A a lot has been updated since 0.1.3
TOk, I only went with a github link, will try that one!
Have been unable to find the repository you just linked
Have been unable to find the repository you just linked
NNyou can also check out the documentation for TelemFFB in the Rhino Manual https://discord.com/channels/965234441511383080/1091401951951982602
Nit is by no means complete but may help get acclimated
TManual is where I found the github link in which I found the download link for 0.1.3.
Regardless, much obliged, I shall make all efforts to stay tuned!
Regardless, much obliged, I shall make all efforts to stay tuned!
Nthe new version may give more info as to why it is failing to connect
TUnfortunately the newest telemffb has the same issue, but as you said, probably not related
TThe log states:
"2023-09-22 20:37:49.550 - INFO - TelemFFB (version 2d71680a) Starting
2023-09-22 20:37:49.551 - INFO - Found Saved Games directory: C:\Users\Tore\Saved Games
2023-09-22 20:37:49.551 - INFO - Checking C:\Users\Tore\Saved Games\DCS\Scripts
2023-09-22 20:37:52.4 - INFO - Writing to C:\Users\Tore\Saved Games\DCS\Scripts\TelemFFB.lua
2023-09-22 20:37:52.4 - INFO - C:\Users\Tore\Saved Games\DCS.openbeta does not exist, ignoring
2023-09-22 20:37:52.5 - INFO - Open Rhino HID FFFF:2055"
"2023-09-22 20:37:49.550 - INFO - TelemFFB (version 2d71680a) Starting
2023-09-22 20:37:49.551 - INFO - Found Saved Games directory: C:\Users\Tore\Saved Games
2023-09-22 20:37:49.551 - INFO - Checking C:\Users\Tore\Saved Games\DCS\Scripts
2023-09-22 20:37:52.4 - INFO - Writing to C:\Users\Tore\Saved Games\DCS\Scripts\TelemFFB.lua
2023-09-22 20:37:52.4 - INFO - C:\Users\Tore\Saved Games\DCS.openbeta does not exist, ignoring
2023-09-22 20:37:52.5 - INFO - Open Rhino HID FFFF:2055"
NTwill attempt
TYes
TShould I attempt firmware update?
KIaam sorry folks, I know I am, a noob when it comes to problems solving with my PC... my problem this time is that when I connect to the webpage (via edge) I get this: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface.
T@Kreytfire Have you tried via Chrome?
Kwell ,microsoft edge and it worked last time... connected the rhino to a seperate usb port to make sure its not the usb hub
TWhen I attempt to update firmware, it states: "Error: NetworkError: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface."
TIt connects, but other than that, no go.
KSuper Walmis!! thanks, I will try! so it was not me messing something up completely.. what a relief 
TI just tried that, unfortunately still have the same issue.
TOk I got it working, the stick was connected to a USB hub, it obviously did not like that.
TTelemFFB works as well now.
WDid you manage to update to v16 ?
TYessir!
All problems got instantly solved, IL-2 detected the stick too.
Now I know my USB hub is a whicked shimmy.
All problems got instantly solved, IL-2 detected the stick too.
Now I know my USB hub is a whicked shimmy.
TA new issue popped up now, the VKB>Rhino adapter (VKB box is connected to normal USB port) is being a little weird in that triggers and other buttons are registered as POV buttons in IL-2, rather than, say, "Button 1" like the trigger would normally be, and they don't work in-game.
TTry as I might, I can't get the stick buttons to work in-game in IL-2, they register as buttons in options in IL-2, but they don't actually do anything once in-cockpit and actually flying.
WI'm not very familiar with VKB software, but maybe worth a check via the VKB native software?
WThe hardware is very simple - just a pass through cable connection
TAll is well according to VKB software.
So i reset all in-game controls to default and set everything up again, now nothing works in game, no pitch no roll etc
So i reset all in-game controls to default and set everything up again, now nothing works in game, no pitch no roll etc
TRegisters just fine when mapping, just doesn't actually work in-flight
THad no issues until today.
TNow not even the MSFFB2 works in IL-2, I can't actually play the game, non VKB stuff is affected by this issue.
Had no issues, for years, up until the Rhino was physically connected to the computer, after that, everything went biscuits.
Had no issues, for years, up until the Rhino was physically connected to the computer, after that, everything went biscuits.
NSurely something foundational is going on that’s causing the issue? Did you reboot after running the command suggested to fix the connecting issue before you discovered the usb hub was the problem?
TI did.
This took a few hours to figure out, but I couldn't leave it on a sour note, that would be unfair.
I took the stick off and unplugged it, running just the VPForce, rudder and throttle quadrant, and it all worked again.
So that left the stick, I changed the Warthog stick from VKB adapter to stock Thrustmaster Warthog, and plugged it in it worked, all inputs worked, game works.
Now I finished a round of testing after changed it back to VKB adapter with Rhino Adapter, which again didn't work, then back to Thrustmaster which works, so the issue appears to be the adapter between the Rhino and the VKB.
This took a few hours to figure out, but I couldn't leave it on a sour note, that would be unfair.
I took the stick off and unplugged it, running just the VPForce, rudder and throttle quadrant, and it all worked again.
So that left the stick, I changed the Warthog stick from VKB adapter to stock Thrustmaster Warthog, and plugged it in it worked, all inputs worked, game works.
Now I finished a round of testing after changed it back to VKB adapter with Rhino Adapter, which again didn't work, then back to Thrustmaster which works, so the issue appears to be the adapter between the Rhino and the VKB.
TI don't know why the Rhino>VKB adapter>Warthog combination doesn't work, maybe it's just not written in the code.
Either way, it works now
Either way, it works now
