FalconFSX

In my testing I think its the left brake. I've had another verify that the amount of braking appears much better on the right over the left. If you try rolling and jam on left break vs right we get different behavior. I also think when I got to 80%+ power it starts rotating right (because left break isn't holding).

I had this problem today using the A10A for the first time. I noticed that steering worked when "Power" was turned off. Then I would turn power on and only the rudder would move, not the wheel. I'm pretty sure there is some bug here.

Thats great info. I'm curious as to what card I should get to drive the setup. Probably looking at the 2080 but wondering if the 2080 TI is worth it given that much resolution (and I use VR as well).

I'm going to be buying some extra monitors in the future and wanted to know how much resolution would play into that decision. Currently running a 2k IPS 27" monitor as my main. I'm assuming I should get IPS (to better match the display of the main), but would 2k matter or could I drop to 1k on the sides to save some money (and I assume easier to drive from a GFX card perspective)? Thoughts?

I assume the new JetSeat Sim Edition model would fit, but this is what I use and would be interested to make sure it worked well in: http://obutto.com/gaming-cockpits/r3volution-gaming-cockpit/

Seems like no matter what I do it thinks easy communication is enabled. I've attached a jpg with the log I see on start.

So is my problem that VIACOM is always using "\"? Meaning it thinks Easy Comms is on? How do I disable that? Again, using the P51D module if that matters.

Newbie Questions I've been giving VAICOM a try and have a couple questions. Specifically, I'm using the P51D module with Easy Communication = OFF. 1) When I say start mission, it always auto-pauses (and then I have to hit PAUSE/BREAK to actually start the mission). Is this expected and is there a way to disable the pause if so? 2) I'm using the NUM1 key to talk to ATC when on the ground which works fine. However, I really should be using the Push To Talk button i believe. This shows up when in the air as the NUM1 button doesn't communicate with the ground. However using the Push To Talk button succeeds. Am I missing something in the setup where VIACOM should be using the Push To Talk (defaults to "RAlt + \") instead of the Communication menu ("\"). Thanks in advance.

Submission: Evening over Vegas

Thanks for the info. Is it any more valuable for the WW2 planes then modern? I was thinking the left/right feel might help in the prop planes as you push them (assuming you can feel the vibration from tight turns, etc).

I'm interested in getting this setup for myself. Currently have an Obutto Rev desk that I would be attaching the transducers to. What should I buy? It seems like the Buttkicker Gamer 2 is the easiest solution, but it will only ever support 1x transducer. I don't plan on sim racing, so won't ever need 4. But is there any need for more then 1 with DCS?

Mostly stays right around 1400 with minor bumps no lower then 1300 for a short period. The GPU usage % is moving a fair amount, 40-65%.

I went into my NVIDIA control panel and vsync was enabled for global profile (not adaptive, I don't see the option). I turned it off and it doesn't appear to have any effect. As for GPU clocks, using MSI Afterburner, my Core clock goes to 975 when Oculus is launched, then 1400 when DCS is launched. So I don't think that is the problem. Any other suggestions?

I'm using CV1 and I've using the Instant Launch Free Flight over Poti in the P51 to test. Using DCS v1.53 (Steam) with a GTX970. I get 90 FPS unless I look in certain directions, then it will drop as low as 45. Specifically looking about 45 degrees to the right (from the start of the mission) and then will notice it if I turn right toward the landing strip the ally P51 lands at. Is there an option I'm missing or is this something else?