36 degrees isn’t too much? Usually travel is around 20-25. Right?
36 degrees isn’t too much? Usually travel is around 20-25. Right?
TNote that the 86series have a 1/2" shaft, and the smallest off the shelf pulley I found for that was 15T (for 5M). So to get 10:1 you're going to need a big pulley on the other end. I'm curious how much of a difference such a ratio would make? I've got my base at about 6.6:1, with a +/- 15° throw and that gets me a little over 1000 steps in each direction. Even with the longish extension I have, that works out to a single step of the ADC being about 100microns movement of the grip. I can't reliably make a motion of the stick small enough to move only one step. But maybe I'm just a bad pilot...! I also haven't tried helicopters, but will soon.
SSo which is a good ratio for helicopters? For a grip with extension about 40cm.
RI printed 12* limiters and it’s perfect for my 32cm extension
Si just used 36 to make the math easy to show, you can put in whatever numbers your stick moves
SDumb question: no matter how much I tighten it, it seems that the winwing adapter has a bit of play on the rotational axis: is this intended?
WLooks like the cup edge reaches the top attachment first and there's no friction lock. What kind of extension is that?
WProbably easiest would be to print a 1mm spacer/washer to put in between the adapter and extension
JWalmis, as I was thinking about my DIY build I am still planning, I asked myself if the control board has a certain maximum resolution of the output current and thus the output force? With the total pulley ratio that might make my force resolution especially in the lower quarter I would most often only use quite stepp-ish.
Just wondering if it is possible to quantizise this.
Just wondering if it is possible to quantizise this.
WCurrently positional resolution is 4096 steps/rev, output current resolution is not dependent on input resolution (internally it's in 10mA steps)
JThanks!
ADoes TelemFFB also need an updating along with the .15 FFB Configurator or has something changed with regards to periodic effects?
AI'm having to push values in the config.ini through the roof to get any noticeable effect, e.g. gun vibration and weapons release was at 0.2 on the Gazelle before today's update, and now I've had to put them both at 1.0 to even notice anything on either effect
Nnothing to my knowledge.. I also haven't had a chance to check out the new firmware yet
Nhmm.. a really quick test in the spitfire and it seems normal to me...
blatantly obvious questions.. periodic effects gain in VPfC turned up? And you don't accidently have the pot knob assigned to periodic effect gain but turned down?
blatantly obvious questions.. periodic effects gain in VPfC turned up? And you don't accidently have the pot knob assigned to periodic effect gain but turned down?
AYeah, double checked that
Nreally strange.. I just checked out the gazell, which I never fly, but it seemed normal to me.
AHmm. Hella late here, I’ll unplug it, have another look tomorrow and report back
Jive been trying to work out settings for the force trim to behave in the DCS AH-64 for some time now. The issue I have seems to be around the new center once the force trim is activated. If I activate force trim the controls do not hold exactly where I set the new trim, it always springs back slightly toward center. I'm not sure whats wrong and i've tried all sorts of combination of settings to no avail.
MGot my kit build up and running today (at least to see outputs on my laptop, desktop is down, so no real testing).
I plugged my realsimulator F/A-18 in to it, expecting to just run it for power and BTLE in, as normal. To my surprise, the Rhino software detects button inputs from it! However, it does not detect the SCS depress, the actual RECCE depress, or the TRIM depress (so the hats on the face, it does detect pickle depress).
Any idea why it might be missing those buttons, or any way to fix it?
I plugged my realsimulator F/A-18 in to it, expecting to just run it for power and BTLE in, as normal. To my surprise, the Rhino software detects button inputs from it! However, it does not detect the SCS depress, the actual RECCE depress, or the TRIM depress (so the hats on the face, it does detect pickle depress).
Any idea why it might be missing those buttons, or any way to fix it?
MIt looks like the grip is sending those as DX buttons 61-63, if the Rhino does not look for those buttons, is there any way to do a remap on the Rhino side, or expand what it sees?
NI had this problem initially when I had a curve set on the cyclic axis' in the apache
HI was hoping this would be fixed as well. Along with the force 8 way hats to 4 way
Jit was my understanding that setting a curve in DCS conflicted with other FFB settings
Nmy rote understanding of it is that FFB doesn't understand the curve exists, so when the in-game stick movement is not 1:1 with the physical stick movement, FFB sets the center point based on the virtual stick position, not the physical stick position.
Nhence, if your physical stick has moved farther than the virtual stick, the new trimmed position, based on the virtual stick position, is closer to center than the physical stick actually is.. thats why the new center doesn't match where you had the physical stick
Nthats a really long winded way of saying that might be the problem, unless you don't have any curves set, in which case I don't know because I dont have the issue (without any curves set)
Jalthough, I see that I get the same effect inside the VPForce software. Are you saying that setting the curve in DCS is what is correcting the behavior?
Nno.. the opposite.. If you have a curve set, it will behave as I describe
Nyou mean with no sim running and just using the hardware force trim?
Jyes, no sim running.
Ji get the offset effect to where I trim
JI almost feel like its a balace issue. But when I try to use the balance spring, I cant get a reliable new center when off center either.
Nhave you tried the new firmware with the dynamic centering? working pretty well for me
Nsorry.. "adaptive" centering
Jyes, it just re centers to the wrong position
Nhmmm Im sure walmis would be able to tell you whats up in 2 seconds. So the blue-dot doesn't stay in the middle of the blue circle? Or, the blue-circle ends up in the wrong spot when you release the trim?
JJno, it doesn't hold center.
Nthats really bazar. I've got a pretty heavy grip on a 20cm extension with 100mm rear offset and it holds center of dot pretty damn good
JI've tried 200mm - 250mm extensions. Virpil Alpha grip, The virpil extension... Currently running QR4rigs 200mm with 75mm offset extension.
Jthey all behave the same way.
Nif you want, post your vpconf export and I'll try to reproduce..
NI've gotta hit the sack, but you can try mine
WYeah this looks puzzling. If you completely turn off spring, how does it feel by itself? On the right side of the gimbal there is the grip cable (under the leather cover), it's possible it can twist on itself an give a springiness by the edge.
WCan you select generic grip (debug), and post some data from the debug tab when clicking those buttons?
WMaybe you have pot set for periodic effects and it's turned down? Otherwise if you could post your settings might give some clues.
Ais there a way to change the volume on the latest firmware update?
Aalso, the new firmware seems to report a bunch of buttons and pov hats to windows that dont actually exist. I have the virpil alpha grip, and this is what it show as buttons i have available, and the blue items are what i've managed to actually press
Asettings are:
Aalso, if i have something like this for settings, will the adaptive spring centering now be enabled in games that apply springs? or is this only an affect related to stuff applied by the configurator app?
