Ill have to play around with that to see how it can improve the A10. Gotta go now, it's late here.
Ill have to play around with that to see how it can improve the A10. Gotta go now, it's late here.
PI haven't used it myself yet, I was just guessing that might be the setting to move the axis center? Cheers m8, cya later
HIt's definitely noticeable in the F-14 that the centerpoint with neutral trim is way far forward, but it matches the actual control indicator in-game (Right Ctrl + Enter)
MYou need to change the calibrated axis end for the push part of the y axis. I cant imagine how far forward your stick goes in the 29 at high mach
HTo be honest, I never tried modifying the calibration beyond making sure it was actually centered, since the stick always seems to match the control throw of the in-game aircraft
MTry it. I know I won’t go back. My calibration only goes like 15 degrees past vertical. However I have a large extension
MI only got to doing that by correlating vr stick position with the rhino one
PSorry just to clarify are we talking about changing the Axis Scaling setting in Effects tab?
MNo just when you calibrate the whole thing
HI'm confused about why/to what extent I'd recalibrate the center to change it
HSince I actually prefer having a much shorter forward throw
HHaving the neutral position shift itself forward is honestly quite nice
MYou recalibrate the end of the Y axis. Try a few values till you get one that feels right
PSorry m8, do you mean change the max setting in there
MYeah
HI'm still skeptical here. You're either saying to desaturate one side of the pitch axis, which would just reduce the total usable throw range, or move the center calibration point, neither of which seem like something I'd want
Pahh ok, so that will change the physical axis limit & then the software will soft it out so you still hit 4096 when you reach the physical limit?
MIts personal preference for sure, but it's the fix to the issue you describe
MYeah, that's why walmis is now making physical end stops
MSo you set it to like 2500 or 3000 or something that feels good for your ergonomics
MLike we all have different stick lengths and Sim pit seating arrangements
MSo just try to correspond what you see in VR with a usable axis
MAnd you won't notice the difference for the aircraft that currently feel good
And the shonky ones like the A10 and the Ka-50 and the F5 and the tomcat feel right
And the shonky ones like the A10 and the Ka-50 and the F5 and the tomcat feel right
HI don't actually think it's an issue
MAh sweet as, keep it the way it is then!
HYeah, I'd actually prefer all my center stick aircraft be that way, since it more closely mimics how real aircraft are setup
HGiving you all that extra room on the pull gives you a lot better control and feel for how hard you're pulling
MMakes sense, do you have an extension?
HI do
PI think most people are restricting the push of the Y axis as a lot of aircraft have less forward throw than rearward.
Show do you know about the real aircraft? The neutral position only happens in flight and that's where you would see your stick pitched forward.
S@walmis I realized that the axis scaling is supposed to adjust this but it would be far easier if I could just drag the center point in game. The necessary change in vpconfigurator would be a button to adjust center. Like the auto calibrate button but simpler. Click the button, drag the blue circle, click the button again. This could even be automated. Although that might sound complex, DCS actually can export values in game, specifically the name of the aircraft. Simshaker and DCS exports do this through the export.lua. So the Rhino firmware could poll the export lua every 5 minutes, read the data (which aircraft) and set the center point according to an aircraft specific adjustment (like simshaker does). This aircraft specific adjustment can be stored in the firmware and modifiable by the user.
Salso tried running the latest executable version of TelemFFB through the executable. Got this error:
STraceback (most recent call last):
File "main.py", line 282, in <module>
File "main.py", line 261, in main
File "utils.py", line 286, in install_export_lua
File "utils.py", line 266, in write_script
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\Stefan\Desktop\telemffb/export/TelemFFB.lua'"
File "main.py", line 282, in <module>
File "main.py", line 261, in main
File "utils.py", line 286, in install_export_lua
File "utils.py", line 266, in write_script
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\Stefan\Desktop\telemffb/export/TelemFFB.lua'"
SI put the script from the master into the empty folder and that fixed it
G
Ganybody else get this with the new software?
Adid you update the firmware yet from the website?
A(visit this url in chrome to actually also update the firmware: https://vpforcecontrols.com/usb/rhino/ )
TTagging my fellow @FFB/Kit Owner for visibility.
WI'd recommend tapping them to M6
GYes, M6 screws. I used flat hex head bolts
GAnything taller head may start running into the belt. I also added an idler bearing for belt tension on the upper forward bolt of the pitch motor. I can add pics and details after work when I get home if anybody wants
TI’d like to see how you did it. I’ve got my gimbal made and moving on to the housing. I think all the bases are modeled for the 57 series motors so I am looking into how to implement the 86 series.
GOh, the 86 series. Sorry, I didn't read that correctly. I have the 57s
GIt should just take a cad adjustment and bigger hole pattern. You will however run into interference with the gimbal arms and the roll motor. My 57 motor hits the gimbal, but it ends up hitting past where the end stops are so it's fine.
GThe 86s might need some cad readjustment and different belts
TWhich part does the gimbal hit? I’ve got an idea how I want to modify it. Just getting ready to start on modeling it. I’m thinking v-slot extrusion frame with printed panels.
GThe lower arms of the gimbal arm at full throw. Even the 57 motors have bigger cases than the basic cad file case has, but it's not enough to cause problems
WI used M5 hex bolts with a lock nut on the back.