steveropa

Nope, it was the wheel chocks. I had the crew chief remove them and everything was fine. I guess the "bug" would be that from an external view there weren't any, but the plane wouldn't move till i had the crew chief remove them. More of a minor quirk than anything.

I don't know if this is so much a bug as a note. I was doing the "TAD familiarity mission"(don't recall the mission number) and could not taxi for some reason. Then i remembered that DCS recently introduced wheel chocks on cold start for the A10C-II. I asked the crew chief to remove them, even though an F2 view did not show any chocks there, and all was well.

I read his comment differently. As in v1 of the G2 headset. I got an early release of the G2 headset and had to upgrade my cable from the one it came with as well.

I just replaced mine, and was getting just as frustrated. Turned out that what i though was "all the way in" for the plug on the headset side, was not. Once I got it seated all the way in, well past where I thought it would be, I was good. Also, you probably already did this, but make sure the power button is on.

Just got mine today, have to wait till after work to try 'em. Any gotchas I should be aware of?

I was successful with a similar setup, although from what im seeing on these fora is that I am not as demanding as many. I was getting about 20-30 fps with somewhere between the "high" preset and the "vr" preset. I did end up upgrading to RTX2060, but only to go from good to better. by 2.something to 1.5, are you referring to pixel density? Also, it depends on which map. channel map is brutal, I was getting between 1 and 5 fps on my usual settings.