bxlplk

I followed the workaround here ( https://forums.eagle.ru/showthread.php?t=170221&highlight=ffb ) to get the trim working for forcefeedback. But the position it trims to is 100% forward. If I release the stick from the center position, it will push forward all the way. If I release it from the center left, it will move foward-left. Ditto on the right. No matter where I push "set pilot trim," it will keep moving forward, always enough to crash me into the ground. I have trim set to FFB under the Special tab. My Sidewinder pulls towards the center from all directions, so I'm guessing it's OK. The joystick is a bit "grindy," like it's running over gears, but it's my first FFB so I don't know if it's normal. Ideas?

Snap view / head positions would be very helpful for VR. VR is a tease in the Huey, because I can turn my head so see the left panels (but I really have to crank my neck), but things are illegible unless I i turn my whole body, put my face right near the controls, and subsequently smack my face on my throttle. Sometimes I try to reset the view from a point that makes looking at the panel more comfortable, but I have to do it every time. Also a +1 to engine damage.

Maybe this will help? https://forums.eagle.ru/showthread.php?t=150129 Good luck.

LimaSierra: I don't see the links to your vids.

On the pad? Check. No flames? Check. Success!

I thought the VKB T-Rudder was expensive until I saw the prices for the plastic pedals. Then it seemed like a bargain. For an extra sixty bucks, I could get an all-metal construction, frictionless performance, little maintenance, and no user mods for basic functionality. I've been very happy using it in the UH1 (where toe brakes are not needed). I actually would have bought the Pro Flights, but fortunately they were out of stock. Here's the video that sold me on VKB: That smooth action is delicious. Good luck with whatever you get; it'll be a big step up from a twist.

Yup! I got a Sidewinder (FFB) and unplugged the power, and it does exactly what yours does -- stays where I leave it and gives very little resistance to move. Trying to hover with a spring joystick is absolutely maddening.

Related tothis thread. Getting bad judder in flying low in built-up areas on my Vive&R9 390 (but not in 2D). My comments (now in the proper thread): ETA: Think I may have overstated it. It's visuals in Harbor Tour are particulaly bad when rising up over the bunker, but it settles down to blur with some minor judder with moderate head movement. My hot fix solutions: 1) Don't look at the area. 2) If you do have to look at the area, don't move your head. It'll be just like playing the game in the old days without trackIR. 3) If you have to work in the vicinity of a low-FPS area, plan your activity to keep the problematic zone to the rear of the aircraft.

Bluelight -- I just realized this isn't a VR-thread. I'm having this problem with my Vive. 2D DCS has always worked fine. But, still, it's weird because plenty of people are saying they have no trouble, so something is up.

I think I've seen this wish before, but I'm going to +1 it. Fixed cursor location *somehow*. Ideas: 1) Sticky cursor with button press. If you find a spot for the cursor, press the lock button. When you want the cursor back to gaze-directed, press the button again (and reset after a delay). 2) Sticky cursor for scroll wheel and left/right mouse button options, but not left-click only options. So a dial would automatically lock the cursor, and so would any feature the includes a left and right button. These are the functions that are going to take the most time to fiddle with. After a certain amount of time, the lock is released. Left-click only options are going to be one-and-done, so there's no reason to linger. Also, an un-wish: I though wand integration would be the holy grail of cockpit interaction, but I think gaze-directed + sticky cursor would be way better.

Just checking in. Having the same problem with the UH1 Harbor Tour (and other areas). Looking out over the water is fine, but as soon as I look left toward the town it starts to judder. It got so bad at some points that I actually got black bars on the leading edge of my vision. CPU usage is at 40-60% for most of it. I can't tell on the GPU usage, unfortunately, because my AMD card doesn't report utilization properly. Tried the lowest settings and still unplayable. Deleting options.lua did nothing. It's definitely a bummer, though, because 95% of the map is perfectly playable. I flew threw the UN Pilot career mission for a good hour without any trouble. But when I got to the LZ the chunking got so bad I botched the landing. Well, maybe I would have crashed anyway, but it certainly didn't help. So now I'm left with the possibility of playing missions, with a creeping anxiety that it's going to end in disaster if I ever get near a problem area. The contrast between these areas and the rest of the map is nuts. I've been running 4x MSAA, and high textures and have had no problems. Hit one of these towns, and there isn't any setting that they work at. What I'd like to know: a) What's the time line to fix it? Or, if not a time-on-the-clock, what release is it expected to be fixed? b) What's the min spec to not have this problem right at this moment? I've got one vote for a 980ti from this thread, but I'd like to know about the 1070. Specs: i5-4690 R9 390 16 GB RAM

From what I understand, LeapMotion is working on integrating their features into a headset, not on creating new stand-alone hardware. So while they are still innovating, as far as us Rift/Vive users go, Leap Motion v1 is what we'll have to play with for the foreseeable future.

You might be running into Vortex Ring State, it will drop your helicopter right out of the sky if you're flying too slow without enough lift. You might be confusing that with a sensitive collective. But, yeah, even knowing that, the Huey collective is insanely sensitive. I built my own collective just so I could have the extra travel distance to make finer grained inputs. [ame=https://www.youtube.com/watch?v=hZYMkG63cJU]Here's a video on the DCS Huey from an ARMA pilot that I found extremely helpful. [/ame]

Regarding FFB for helicopters: trimming is a foreign concept to me. I use an unplgged sidewinder. It has smooth travel in all directions, no centering force, and enough friction to stay in place if I need to scratch my nose. From my understandings, thats a lot closer to how real helicopter cyclics behave than using FFB with trim. And if it's wrong, I don't care because it feels so right. Definitely give it a try.

I can't use the mouse to aim the flex sight if I've had Opentrack on at *any* point during the mission. I've stopped Opentrack. I've "frozen" opentrack using the toggle. I've disabled/renabled the aim with track IR option in Special options.. I've tried Alt-C. I've tried loading and reloading missions, and restarting DCS. There is just no way to get the mouse to aim the flex sight and use Opentrack in any capacity during a mission. And that's bad news, because Opentrack is sloppy as hell when trying to hit a 2x6 pixel-sized target. Running DCS 1.5. Opentrack 2.3-rc19, ftnoir plugin 1.1.

I am unable to fly or get into cockpit view of my Huey after going into the briefing menu. A member of /r/hoggit describes it in more detail: Confirmed with UH1 and Su-25T.