is anyone getting an idle oscillation (slight one that doesn't get out of control) since latest firm
is anyone getting an idle oscillation (slight one that doesn't get out of control) since latest firmware and calibration software update
BI updated the Rhino Firmware to v1.0.17b4 and now when I open VPforce Configurator I get this message. When I click OK the app closes. What did I do wrong?
RThank you Walmis, I'm trying it now. First I tried to move the joystick bask to the hub to see if the problem comes back, so far the the Fedit and DCS is working as normal (Strangely, and kinda expected, the "DCS generated FFB getting inhibited issue" is not coming back). But the other issue I reported earlier comes back when I tried to plug both the Joystick and the Pedal (Mutual exclusion issue for USB connecting Joystick and Pedal). I'm about to update the firmware to Latest Firmware: v1.0.17b4 and see how it goes.
RThe firmware v1.0.17b4 appear to have addressed "Mutual exclusion issue for USB connecting Joystick and Pedal" issue, I'm flying both the Joystick and Pedal connected via Sabrent USB hub now. Thank you again Walmis, flying with VP-FORCE Feedback is such a joy!
HYou just need to do a new calibration in VP config. That‘s all.
KCan someone point me towards explanation what exactly this "Spring Dynamics" setting is doing? I'm mainly flying F-4 in DCS and can't tell the difference between it on and off. I get the description but there is no explanation in manual, I'm not sure if this is working or not.
Shello, after update the rhino Firmware and the Configurator to the lastest version my rhino stopped registering the button in the app and ion the game controllers windows app. any ideias? the axis are ok.
SI can't have button actuation in the Rhino FFB WebUSB Tool too.
Sps: i'm using the A10 warthog stick and was working before.
Sok got it, just changed to generic grip 
NMaps the input spring gain (from game) to a desired output spring gain. With a linear 1.0 to 1.0 line, the output will always equal the input.
TI did, but was able to tune it out with some changes to friction/inertia. I would recommend loading the Rhino defaults with the new firmware/app and then seeing if the oscillation goes away. Then tweak back to your original settings one at a time and see what induces the instability.
IThanks
WIt's fine. Just download the latest configurator package .zip 
MTodays firmware update did the trick for me too. Apache trims as usual. Thanks Walmis!
HThanks mate! Yeah I was thinking the same with reintroducing one at a time from default. Nice to hear you got a fix too. I was hoping I wasn't the only one!
Ohmm mine also stopped showing up in DCS/game controllers
Ono dice just yet on getting it back
telemetry is fine in configurator
telemetry is fine in configurator
Orestarted, now motor x/y n/d and config seems to be wiped
Ogiving it a rest for now as I seem to be going backwards
Oon win 10 if that matters
Ohmm, it is showing up in the system tray under "safely remove hardware and eject media"
O
Ostill can't get it to show in game controllers. actually going to bed this time. any help much appreciated! thanks all.
THi. I'm getting this message when I try to set a config for an aircraft. I can only set the Joystick, when I click on Pedals or Collective it won't let me set a config with this message.
NOpen the individual instance windows and do it from there. I’m not sure setting the profile overrides across instances (or things like button bindings) will work from the offline editor.
NThe offline editor is in need of an overhaul.
TI'm going to order some more throw limiters but I'm a bit confused as to the degree's of movement. I first ordered the 11 degree default but felt like I needed more throw so I ordered the 20 degree and now I have to much throw. When I order my next set I want to order less throw on the nose up pitch and a little more for the nose down pitch. Was the 20 degree that ordered both ways - and + 20 X and Y or was that just 20 total? like +10 -10 on the X and Y? I need to know this so when I place the order for the next set I don't mess up and get totally the wrong size.
TUntil the last update I've always done it like this. What do you mean "Individual Instance"? It seems not to matter what I click, Joystick remains as the Master Instance. Have tried with DCS running still won't work.
FWhat I do is I play with the end stops settings until I find the throw I want. Then I apply those percentages to the 22 degrees of throw and that's the limiter I order.
FThe 20 degrees that you ordered is 20 forwards and 20 backwards (+-) so 40 degrees in total.
Tso does this make sense that I order this more more push less pull and a little less roll throw I would like to order some more throw limiters. I would like to order 3.
- X +/- 15 and Y -11 +20
- X +/- 16 and Y -11 + 20
- X +/-17 and Y -11 + 20
TI used the 11 on bottom and 20 on top and liked it for pitch but I want a little less roll so I ordered 3 throw limiters
FThose make sense and you mean less roll not yaw.
FAnd more push or more pull those are reversible so you can flip them over to experiment if needed.
FBut again. I'd test those with the end stops before ordering so you can see if you like the results or not.
Tok that makes sense right now I dont have the end stops on but I did mess with the axis scaling
Tso at 75% I would want to order -15 for the nose up pitch
NWindow menu->show child instance windows.
Additional checks were put in the latest release to prevent accidental selection of a profile that changes the PID or device name. Doesn’t appear it is properly accounting for the device configuration context.
Additional checks were put in the latest release to prevent accidental selection of a profile that changes the PID or device name. Doesn’t appear it is properly accounting for the device configuration context.
OYa mine is still unrecognized in Windows/game
TYou can calculate the throw with math. Measure the distance from the center of rotation to the top of the grip (or center of your hand) - that will be your radius, R.
Then 2 x 3.1416 x R = total circumference C. Multiply C by the limiters’ percents from opposite sides (say 11 pull and 20 push for pitch = 0.31) and you’ll have the throw distance. (Edit to fix Discord format changing formula...)
Then 2 x 3.1416 x R = total circumference C. Multiply C by the limiters’ percents from opposite sides (say 11 pull and 20 push for pitch = 0.31) and you’ll have the throw distance. (Edit to fix Discord format changing formula...)
RI used chatgpt to manage my throw distance per degree based on my setup, let it do its calcuations then had it spit out a graph showing different throw differences per degree, picked what i wanted and printed it in PLA plus, perfection.
RHere’s a simplified representation of the data for total throw length at different degree limiters:
Total Throw Length for Different Degree Limiters:
Limiter Angle (Degrees) Total Throw Length (inches)
6 ~5.52
7 ~6.44
8 ~7.37
9 ~8.29
10 ~9.21
11 ~10.13
Description:
• X-axis (Limiter Angle): The angle of the throw limiter, ranging from 6 to 11 degrees.
• Y-axis (Total Throw Length): The corresponding throw length in inches for each degree.
Total Throw Length for Different Degree Limiters:
Limiter Angle (Degrees) Total Throw Length (inches)
6 ~5.52
7 ~6.44
8 ~7.37
9 ~8.29
10 ~9.21
11 ~10.13
Description:
• X-axis (Limiter Angle): The angle of the throw limiter, ranging from 6 to 11 degrees.
• Y-axis (Total Throw Length): The corresponding throw length in inches for each degree.
TThat works!
Rthat is for my length extension
TI've been experimenting with which USB ports the Rhino is plugged into. With some ports it will turn itself off (even though USBLogView doesn't show it disconnecting) and TelemFFB console shows it as not connected after an Exception. I thought this was probably related to hitting a limit for USB resources but I don't get any errors about that. I can work around this by choosing the ports and/or hubs it DOES work on, so I have a workaround, but I've noticed some odd details and wanted to check if something else might be going on.
- Looking at USB Device Tree Viewer, I see the Rhino's top level node as "Taiwan OEM - OBSOLETE VPforce Rhino FFB Joystick". Does this mean that possibly the correct drivers for it aren't running?
- With one of my USB hubs (Startech industrial 3.0 10 port hub w/ 65 watt power adapter) plugging in the Rhino (or booting up with it connected) to that hub (or sometimes a different 3.0 hub) will cause either one or ALL of the devices on that hub to disconnect. They then sometimes reconnect, and sometimes stay disconnected. Think this is just a hub issue, or could something else be going on?
- I can connect the Rhino USB directly to a USB port on a PCIE card if that might help, but that would mean extending an already long USB cable from 8 feet to 12 feet - though I can maybe use an extra VR headset USB fiber optic cable. Long cable to mobo pcie usb okay?
Dstupid question. Is there an easy way to update an older build of the VPforce configurator software? Or does it require a new install
Oconfigurator just runs the .exe doesn't it
Olike you just run the new one
Dyeah but then it deletes all my old settings
Dnevermind i got it. I had the wrong firmware