RHas anybody printed the propelor gimbal and have slight play in the roll axis?
WThat center part with bearing needs to be tight
RThe long m5 bolt with 2 x flange bearings? In order I have m5 bolt, m5 nut, 2 x flange bearings up top. Seams the threaded part of the bolt barely protrudes the bearings..
R
WYou need to preload the whole sandwitch with a nut on top
RI don't have enough thread to have a nut underneath and on top. I'm using an m5 x 50 as per the github plans. Should I use a long bolt? Or should I only have one nut on top of the sandwich?
R*longer bolt
WI think you might need m5x60
RI'll give that a go 
WI like to think more in positive terms 
PSorry might want to check S/N again that's mine lol 
Pwhichever is easier to wrap your head around
W@pinksht S/N 0025
@flight_dojo S/N 0023
@flight_dojo S/N 0023
P
JOf course, it was just bad geek’s joke
PSo was his.
SI'm planning to order a Rhino base, been wanting to get another FFB stick ever since the glory days of the Sidewinder and Wingman Force. One question... I use Joystick Gremlin pretty extensively for all my button mapping... will that work with the force feedback? Or how are other people doing things like setting up shift/mode buttons with the Rhino?
SI found a comment by the Joystick Gremlin dev on reddit that seems to indicate Joystick Gremlin won't work with FFB... https://www.reddit.com/r/hotas/comments/lnf8g6/knowledge_about_force_feedback_with_vjoy/ I would be fine if I can use the base as one controller device and the grip as another, but I'm not sure that's possible with the Rhino?
ASo you want to combine several devices into one?
AI'm just guessing here, but is the poster's problem that when he makes a combined device with vjoy, games don't understand that the vjoy device is ffb
SNope, the way I have mine set up is to have one vJoy device per physical controller, and use JG to add things like a shift button, and add button press emulation for the ministicks (so they work as both axes and buttons). then I use HidHide to hide the physical devices and the game sees only the vJoys. If the base is a separate controller though, it would be no problem for the game (DCS) to take the pitch/roll from the base and everything else from the vJoy devices.
SI did all that because I have Virpil, VKB, and Thrustmaster hardware, and didn't want to have to learn 3 different proprietary joystick programming interfaces...
AI have those AND winwing, I'm working on a review so I understand why you use gremlin
AIf you're only looking at dcs, shouldn't it be ok even if you don't hidhide?
Ait would see the rhino base in every case?
Athen you just bind the buttons to the vjoy device
SI saw in the FAQ that the VKB adapter for the Rhino is basically just a hardware connector, not electrical, so the VKB grip will have a wire that goes to its special controller box and will still be seen as a separate device from the base, and that would work, but I'm thinking about changing to the Virpil grip, and it sounds like that would communicate directly through the Rhino base controller device.
SYes, DCS works fine if you don't use HidHide, but it makes for a pretty cluttered control setup screen in the game. Il-2 is more picky though, and I would have to use JG's input repeater function to map buttons to controls in the game, which is a real pain.
SIt should still work if you only want to use buttons via Gremlin and bind the axis to the actual base controller or am I wrong?
AIl-2 definitely much more of a problem
Athat thing has the most hideous controller handling I've seen
Abut I think they're working on improving it
SMy concern is that with a Virpil grip plugged into the Rhino base, Windows would only see the Rhino base, from which it would get all axis movement as well as buttons. If I set up a vJoy device for it and used HidHide, then it sounds like the FFB data wouldn't get passed through. Whereas if I had a VKB grip on the Rhino base, Windows would see 2 devices: Rhino base and VKB joystick. It wouldn't get any axis movement from the VKB, but that wouldn't matter.
Awhat's the worst case scenario if you can't hidhide the rhino + virpil in Il-2 and you have to use it as a axis + buttons -style device directly?
AI think that is a possibility
SThe latest Il-2 dev update from Jason Williams suggests that the new control interface is getting closer, and i'm really looking forward to it, but one never knows when something like that is going to come out, or whether it'll be exactly what I need...
Ait might not be what we need, but it can't possibly be worse than what we have now
Aalso note that currently, just adding one extra device might be enough to clunk the whole system as far as Il-2 controller config is concerned
SWhat I get from my vJoy/HidHide/Joystick Gremlin setup is the ability to map one button on my joystick as the shift button, and while its held, any button on my joystick or throttle can then be mapped as another button.
SI haven't noticed that Il-2 has a device limit, but it definitely has a button limit of 64. More than 64 buttons on a device is not supported.
AI don't know if it has a hard device limit, but a friend of mine has to unplug half of his stuff before starting up Il-2 or nothing will work
Afor me if Il-2 notices any changes it instantly throws a fit
Athe system is currently buggy and dodgy as hell
AI'm so looking forward to the new system
SIt seems to work fine with my 3 vJoy devices (stick, throttle, and collective), plus the rudder pedals which I just run straight (no vJoy). But yeah, I was intimidated a bit by the DCS control setup screen at first, but I've really come to appreciate it.
Abasically what I do is program each of the TM, WW, VKB, and VP sticks in gremlin so that I can swap them freely and Il-2 only ever sees the one single vjoy device
ADCS system has its annoyances, but it's quite reliable
Abut yeah anyway you raise a valid point I didn't think of before with vjoy devices (potentially?) not working as ffb controllers
SI would think that with a single vJoy device, you'd run into the 64 button limit in Il-2 pretty quickly... anyway, it sounds like I might want to go with the VKB adapter on the Rhino base if I want to keep using my current setup, unless the Rhino can do a straight passthrough of the grip alone as its own separate device.