tecumseh

Long time CV1 user, and I'm now trying the Quest 2 with PC link. It looks great, but when I am in the cockpit and move my head slightly, the cockpit moves slightly too, the wrong way. So if I nod my head down a tiny bit, the cockpit around me goes up a tiny bit. Makes the cockpit unnaturally jittery. In comparison an IL-2 cockpit feels locked in place. This doesn't happen in any other view or any other game. I tried turning graphics settings down, it's not an FPS thing. I went back to CV1, problem gone. Any one have any ideas? Thank you.

Thanks Flappie for fixing my problem too without needing a reinstall. You're a legend.

I just switched from Stable to the latest Open beta and flew the F-16 and it became incredibly sensitive and wallowy to the point I couldn't land. It was some kind of bug, I have flown and landed the F-16 many times before. I'll try again tonight. So, might be connected to your issue. Normally the F-16 is a pleasure to fly with minimal trim needed.

Same issue here for me, with the latest stable patch. In the previous stable version I could assign mouse buttons to the UI Layer, eg VR zoom. Now the entire Mouse column is grayed out and can't be selected. Fixed by Flappie's hack above. Thank you Flappie!

Thank you for this. This is the solution to a bug that has been bothering me for years.

- edit, never mind I fixed it :doh:

I think the quality of your joystick makes a huge difference. My old joystick sends jerky signals so there is no way I can vertically land accurately unless I set huge dead-zones and curves. But that is no good for flying. If there's no wind, and you have a twist-stick rudder, unbinding rudder completely actually makes hover easier.

Try removing all bindings from Engine Auto Shutdown and see if it still happens.

With two kids under 5 running around a small apartment, it's usually easier to keep the track IR in the cupboard :)

I had the same thing. For me it was finally understanding the relationship between the AP channels and the FC and the trimmer and the auto-hover and the route following mode. Then it was like a light bulb turned on. Took me 2 years though...:huh: Also OP, I have a track-ir but I actually choose to fly without it most of the time. If you set up good snap views it's fine. Except for the A10-C where you need all your stick buttons & hats. I also don't have pedals, and the helicopters are my favorite. Good luck, it's worth sticking with.

I couldn't get it to work, ended up buying BS2 stand-alone. That fixed all problems immediately and I could install straight into 2.0. Getting NTTR for free just because I bought A-10C many years ago is such insane value I am not going to sweat an extra $40 for ED.

Heh I was kidding. I like ED too much to be displeased. I asked them very nicely in 2012 if I could get a BS 2 key in exchange for my two keys and was greeted with 3 years of silence. So I guess it's $40 more into their coffers...

But this is a gaming forum so can't I rant and rage about spending $40 on BS1 and then $20 on the upgrade and then compare this to random other purchases that went smoother like buying a burger today, and say things like UNACCEPTABLE and stuff?!

Yeah same problem here. Ka-50 is my favorite aircraft and I can't load it into 2.0 because I bought BS1 and the upgrade, rather than BS2.

One thing to check is you haven't moved the switch into the neutral position by mistake. It's a 3-position switch and for DT it needs to be down.

Every PC gaming instinct I have, honed from decades of frustrations and disappointment, tells me it is impossible for a game to be this complex, this niche, this beautiful, and this bug free. Normally you can be one, or two of these things. But all four?! I don't know how you do it. Every mission I fly at some point I shake my head in amazement at the achievement. Salut.

The vsync setting in-game didn't used to work. I had to set it in the config file. Is that fixed? I ask because I'm now getting a lot of tearing, with vsync set to on. Thanks EDIT - never mind, I forced vsync on with the nvidia control panel and the tearing went away.

"...tankers will no longer fly into oblivion." Nice writing Wags :)

I had similar problems off and on with my X52pro. In my opinion, you're better off to uninstall everything Saitek, let windows install generic X52 drivers (when you first plug the stick in after the uninstall this should happen automatically) then assign every button and axis in DCSA10C. You'll know you've done this right when the LCD is blank. By ditching the saitek software you lose the modes and "bands", but you gain fps and stability. You can use the in-game modifier function to give you a lot of options. I set pinky as a modifier and that's enough options to cover all the HOTAS functions. Hope this helps