pikmin124

I sorta just turn around in my seat. I usually have to let go of either the stick or throttle to turn around far enough, but I think ultimately it's still easier than doing it in real life. Or, better yet, don't let things get behind you :P. Unless it's Knight. He is every mirage nails on your six. He is every missile launch you weren't expecting. I swear that guy can teleport.

Hi all, At present, I find DCS's desktop mirror to be too low res to be useful for recording or streaming while in VR. I like to record my flights, and my girlfriend occasionally wants to watch over steam's streaming service, and I'd like them to look a bit better in both cases. The solution given here has provided a fix, but for me it feels a little dirty and makes me feel gross inside. It also forces me to change my desktop resolution every time I want to play DCS. https://forums.eagle.ru/showthread.php?p=3139520 My research suggests that the properties of the desktop mirror are controlled by the applications being run. I'm wondering if there's a .lua file or something I can use to access these properties, or if there's another way to change the resolution of the mirror without messing with my desktop. As a side note, it would also be nice to change the window size, as I currently have to move my taskbar in order to click on menu options near the bottom of the screen. I am running windows 10. Thanks

Just one tank, and I dropped it before the intercept. I'm aware of how altitude affects performance, but at MIL power at 30,000 ft I should be accelerating when I'm below 300 knots IAS, shouldn't I? In the track I linked I was losing speed in level flight at 200 knots (at MIL power - I had to keep going into afterburner to keep up with an IL-76). I mean according to the manual the flight envelope under those conditions goes up to a little over Mach 0.9, which I believe is somewhere between 300 and 350 IAS. I don't know why it was weird the one time, but I ran that mission again today and everything was fine other than the autopilot thing.

Really? I could have sworn it worked fine a couple days ago, and I couldn't find any mention of it in the bug reports. I guess I can stop trying to fix it then, haha. Thanks for the quick response.

I'm posting this here because I'm pretty sure it's on my end, and therefore not a bug to report. This issue did not exist yesterday, and the game hasn't updated since. Furthermore, I can't find any references to this issue in the bug reports. If it were an issue with the beta itself, I would imagine it would have been an issue yesterday and for other people. Also, disclaimer, I'm pretty new and only know how to fly the F-15, so testing to see if this issue exists for other planes would require learning to fly said plane. I'm also running the beta through Steam, if that matters at all. Anyway, the autopilot is behaving very strangely. Engaging attitude hold will work more or less, but the plane will slowly roll to the right and the way it responds to stick input seems off. Altitude hold doesn't seem to work at all, and when it's engaged the plane will just pitch down. Disengaging either autopilot causes the plane to abruptly pitch down. Also, when I was recording the track attached below, I noticed that thrust seemed to be behaving oddly as well. You can see that at 30,000 ft at MIL power, the plane won't go above 250 knots IAS, and the acceleration resulting from advancing to MAX power seems very slow (during the bit where I'm catching up to the jet I'm supposed to intercept I'm in full afterburner the whole time). I am pretty new, so I may just have a bad feel for how the plane flies, but I'm pretty sure it's not supposed to behave like that. That's the only time I've noticed anything funny with thrust, but the autopilot issue has persisted across different mission and survived restarts of the game and of my computer. I have tested my copy of 1.2, which I have as a standalone, and everything works fine there. The attached track is me running the first mission of the 'An Eye for an Eye' campaign by Feefifofum. I start playing around with the autopilot once I level out (at 30,000 ft), so you can fast forward to that. The intercept bit (from reaching waypoint 2 to shooting down the target) demonstrates the airspeed thing pretty well, especially when I'm diving after the plane in search of pretty fire and smoke and still accelerating fairly slowly considering. Then I do a bit more with the autopilot on the way to waypoint 5, engaging it then not touching the controls to see what happens. The landing really just serves to illustrate how bad I am at landing, so fast forward through that. At the very end there's a funny thing where the engines take forever to shut down that appears to be bugged as well Any ideas anyone can provide would be great. All I can think of at this point is to reinstall the beta version, and on my internet connection that would be incredibly inconvenient. Thanks P.S. The only thing I did between yesterday and today was disassemble my laptop to clean the fan, but I really don't see what I could have messed up doing that that wouldn't have broken everything, so I would guess the problem is somewhere else. An Eye for an Eye 01-07 (1-5) (notice autopilot and airspeed issues, and why did engines take so.trk