Brisse

Tried switching between multi-threading binary and the standard one? I'm not using VR, nor am I using Windows, but I have a similar problem when launching the game using the multi-threaded version. The standard version works better for me.

So it's a feature, not a bug. Got it A tiny bit frustrating though, that the instant action missions can't be used for setting up an ILS approach.

I saved a replay of the last try and now that I'm rewatching it, I realized ATC told me to use runway 25. Does that matter in any way? Does that mean ILS for runway 07 is turned off by ground personnel?

Loaded up A-10C instant action "night landing" in the mission editor. Here are the wind settings, 2m/s at 250° on ground level. https://imgur.com/DcZsm5x I also tried setting up a similar scenario from scratch in the mission editor, this time also at Kobuleti, and now ILS is working. Went back to try the instant action missions once more, and its broken. I don't see any failure states or anything applied to the aircraft in the mission editor so I wonder if those missions are somehow bugged. Edit: Yes, I'm using runway 07.

Been away from DCS for many years but recently got back into it a bit. Been learning (relearning?) the A-10C and was trying to get the ILS system to work while loading up the "landing" and "night landing" instant action scenarios. Both are set at Kobuleti. Tried many times without getting the ILS, supposedly at freq. 111.50MHz, to work (TACAN is working though). After looking up a few online guides I noticed they do the exact same procedure, but in their screenshots/videos the ILS was working as expected. They were not using Kobuleti though. I thought this was suspicious so I set up a similar scenario at Batumi using the mission editor, and I instantly got the ILS working.

Most of you probably assume these are socket 1151. They are not. These are the Kaby Lake-X models for socket 2066.

Well, technically you are already over-clocking the memory since the memory controller in the i5-6600K only officially supports up to DDR4-2133. Keep that in mind if you start getting random mysterious blue-screens of death at some point. http://ark.intel.com/sv/products/88191/Intel-Core-i5-6600K-Processor-6M-Cache-up-to-3_90-GHz Happy flying with the new rig! :)

Now that we have ReLive, you should use that instead. It's developed by AMD themselves and neatly implemented in the driver interface since driver update 16.12.1 and forward. It works very well in my opinion and Plays.tv is pretty much obsolete now.

There's nothing stopping you from getting a 1070 now. Your system might not be able to use it to it's full potential, but it will still be a big improvement over your current graphics card, and you can always upgrade the rest of the system later. A word of caution though: Now is not a good time to buy high end PC parts. Intel and Nvidia has a monopoly on the high-end segment right now, but AMD have both an high-end CPU and GPU coming out soon, and even if you're not interested in AMD, it still affects you because Intel and Nvidia will have to drop their prices. I expect prices to drop significantly in the coming 3-6 months.

Thanks Cobra847!

The results from such a test can wary widely depending on how it's done and what sort of movement there is on screen. One of the more obvious cases where high frame-rate is of benefit in DCS is when using head tracking such as TrackIR, which is much smoother and more responsive at higher frame-rates. Personally I prefer it to never drop below 75fps when using TrackIR on my 144hz monitor. The TrackIR itself runs at 120fps. On the other hand, if you are just staring at a scene with a static camera and a vehicle driving by 100m in front of you, there is very little actual movement happening in the image, so 35fps could look perfectly smooth under these circumstances. So you see, it all depends on a lot of factors! I'm absolutely certain I could come up with a test where anyone would be able to distinguish 60fps from 120fps. Actually, I've done blind tests like that on friends and family, and they can always spot the differences, and end up looking really surprised afterwards, but it's all about coming up with a test where the difference is obvious. I could make it very difficult if I wanted, but what's the point in that? The point is that the human eye can definitely surpass common monitor refresh rates when there's ample movement on the screen. There's a lot of people feeding the old myth that "the eye cant see more than 30fps" but they are wrong and it's easy to prove it. In reality, our eyes are not digital, so it's actually impossible to say where the limit is. I'd say it's infinite, but of course there's also diminishing returns.

Can we have the Su-33 PFM today pleeeeeeeeease ED :)

The feature was recently added a few months ago, and I think the F-15C is the only one that has it so far. It's possible they will add it to more aircraft in the future.

Aaaaahahaha, good kill :) I think you broke a few safety regulations though.

Two pages ago, Cobra847 wrote this comment and it was specifically directed at you RaXha. Seems like you must have missed it :)