Eihort

As in the post linked previously, removing the "MAX FPS" line in the graphics.lua worked wonders for me.

I'm having pretty much the exact same problem now for a while. Even after loading in, I look around and it'll stutter while paused even. Once flying, if I do a fly-by view, the game will hitch again as the plane get's close. I'd almost say it's when the LOD changes or something. I've tried a whole slew of changes. I even had the installation running on an SSD now and the page file on the system SSD set to 150% my system ram. No idea what's causing this or why, and makes the game rather unenjoyable. DX Diag would be attached, but apparently I've uploaded it in another thread and the forums doesn't like that I'm trying to upload again, but yet won't provide me a quicklink to insert into *this* post. Thanks ED. Hopefully this will work: https://forums.eagle.ru/attachment.php?attachmentid=147775&d=1473208518

Everyone knows Mi-8s and Mi-24s are just French Pumas in different clothes... http://urbanpk.com/pakdef/pakmilitary/army/gallery/images/puma_mi.jpg

Half right. Average power goes down, but peak power doesn't.

Nao pls.

That's almost Automatic Gain Control but not quite, probably what Red_Core was hinting at.

Based on what?

I'll just leave this here because it has lots of good info. http://www.ausairpower.net/APA-Flanker-Radars.html#mozTocId612676

The kneeboard contains taxi maps of all the airfields. It is not updated at all with your position. You have to know where you're starting from.

Really the problem is that it's incredibly difficult online to model something close enough to the real thing to use a lot of tactics used in the real world. No radio comms with more than a handful of people and no real GCI/AWACS and no IADS, AI or player monitored all contribute to this. What ends up happening is you basically have a handful of pilots, who have difficulty using comms (not everyone is on TS, and sometimes it's more fun to talk stupid stuff than ACTUAL tactics), most of whom are flying around only looking to score kills with little to no regard for their personal or aircraft safety. Flying low, practicing good EMCON, sticking to the mountains is the response to this.

Here's my dxdiag. Everything was decent, the only thing that changed was adding the GTX 1070, and things got worse. DxDiag.txt

Okay... so I upgraded to a single GTX 1070 from two 970s in SLI (which had issues because SLI)..... and now my performance is worse than ever with DCS. Constant hitching on relatively empty maps in (both latest updates) 1.5x and in 2.0x. The F-5 instant action in 2.0 on Nevada is nearly unplayable. Outside of VR it's pretty smooth, but still some hitching. We get a bad patch? It's been a few weeks since I tried it when I realized the 970s weren't cutting it.

Eye In The Sky - Apparently Predator trailers have Saiteks.... >_>

I'm only going to say I know a thing or two about this stuff. The problem isn't just simply "Hey, let's make it more realistic one thing at a time." Once you breach a certain level of complexity with just one system on one aircraft, you now have a whole host of variables that must be applied to all aircraft/systems in order to properly represent the EW environment, and allow the more advanced EW techniques beyond noise jamming to have purpose. We're talking every pod (external and integrated like MiG-29 and F-15) and every radar (ECCM). What's the point if you're going to add velocity-gate/range-gate techniques if the radars you're trying to jam don't have the proper victim response or ECCM response modeled? Let's not even get started on individual blocks/versions of radars and what was added to them for ECCM. Some of these variables include what's the jammer set to jam, because a lot of them can't do everything they're built to do, all the time. A lot of times, this is only configurable on the ground. What exact channel is each individual A/C operating their radars on so they don't interfere? How fast does a particular pod figure out what it's getting hit with and then counter? There's -so- many variables, the complexity of the sim will increase exponentially the more aircraft you throw at it. As "trollish" as GG sounds sometimes, he's asking very pertinent and important questions, to which the answer will almost always be "I don't know, and there's no way we can find out, because EW is the blackest of black boxes, next to the radars themselves." So where does this leave the game? Break it down into the most basic ideas. 1. Since all ECM on player aircraft is self-protection, what capability does it provide? It denies a shot and/or fouls one taken and obscures what the aircraft is actually doing. 2. Can this be counter-acted upon? Yes. You either burn through for the most part or develop techniques in the radar to automatically or semi-auto sort itself out. The later requires an individual radar to be a generation, at least, ahead of the system that's trying to jam it. It's a constant back and forth between "measures" and "countermeasures". 3. Do pilots have control over what these systems are doing? No, not really. The system is either on or off for the most part and all the signal analysis and transmission is almost completely automatic, and most functions are only able to be programmed on the ground. Often, some intel officers are the ones that determine what capabilities the pods are loaded with, based upon ELINT in-theater. When you distill what's going on to the above, the current model, while not realistic, provides a decent abstraction of what's going on, in a way that's manageable for the developers to implement. Remember, especially in multiplayer, you have people borking up all the time in the A-10C their individual aircraft IDs. Now you're asking these same people to throw a jammer on their aircraft and, should we stick to realism, figure out what to load it with so it's useful in the field? It would be a cluster bunch, and a bunch of radars operating with identical settings messes it up for everyone. It wouldn't be up to the pilot, but the mission planners anyway, especially in Russian doctrine. It's hard to justify the value-added vs the cost and effort of further developing the EW environment, just to get nearly the same effect of "Push to WVR to nullify ECM".

I played the hell out of this and Apache.

Is there any way to turn it off? I don't want this glove floating where I set it on my desk or other strange places while I play.

What you were told about the Vive safety function is true. If a game stops sending frames to the headset, it will show the homespace. This is a function of DCS and not a limitation on the Vive itself. What's your video card setup?

If this is the light I'm thinking of, you need to go to the left rear panel and cycle the FBW self-test switch to clear it. It has a safety cover on it.

You found the beta update. That solved a lot of problems for me as well. Running dual 970s. Turning off mirrors on the ground helps immensely. For some reason, the 21 runs like garbage in VR, but other jets (2000C, 27, Ka-50 even) run soooo much better. I wanted to wait for more patches targeting VR performance before I said anything to Leatherneck about it.

Vive. The latest VR quality of life updates were great. I saw a dramatic improvement with SLI turned on. Thank you so much for supporting SLI better. Frankly I'm quite disappointed at how many titles choke if you turn it on.

*BUMP* Okay, I had no problem making this work before but something changed. I know it's not my weapons employment methods because I can still shoot everything else just fine. I can't get the smokewinders to fire for the life of me. What's changed/What am I doing wrong now? Apparently the same procedure to fire a magic isn't working to get the pods to activate.

Share profile? :O Please? ;_;

This is nice for VR as well with our unreadability problems. :D

Night time conditions thoroughly break KA-50 capabilities.