Brisse

Yes, that is possible in the nvidia driver. They call it adaptive v-sync (not to be confused with adaptive sync). Here's how to enable it: http://www.geforce.com/hardware/technology/adaptive-vsync/technology

Yes, of course. Not sure why piXel496 doesn't mention that. The whole point behind v-sync is to eliminate screen tearing, so just a simple fps limiter is not a substitute for v-sync.

But there were two more hints in the form of ground mapping radar and advanced missiles. I guess it could work though, with some fictional extra equipment. Da Vinci Aerial Screw confirmed!

With the current 1.5 and black sea map, you could potentially see a performance improvement going from 4gb to 8gb, but going from 8gb to 16gb should do exactly nothing. Personally I have been seeing usage around 4,3gb with the 1.5 open beta on my PC which has 16gb of RAM.

"Nothing" is exactly what you should expect right now. As for the Nevada map, that could be a different story.

Yea. Choose your poison :)

Okay, so we now know the issue can happen on both AMD and Nvidia cards. As far as I know, the new version is dx11 only, so the sim shouldn't be able to run at all unless your system is dx11 compatible. That would mean this particular problem cannot be caused by non dx11 compatible cards.

The plume in the screenshot is being masked by the bright background though. That comparison is not fair. Completely different conditions in the screenshot and the picture.

Nonono. They never forced anyone to install raptr. During installation, choose "Custom installation" and just uncheck "AMD Gaming Evolved" to get rid of all the bloatware. They should have been more clear about it though, and in an ideal world, I would like to see such software banished, or at least separated from the driver installation.

Yup, same here using Freesync on a 144hz monitor. It's smooth as baby skin since 1.5 update.

Oh, sorry. I though you meant the dof when you said blur. Not sure what you are seeing then. I assume you view distance setting is properly tweaked? At high, I personally feel that I can see further and more clearly than in 1.2, especially from high altitude.

The current version of 1.5 defaults to borderless window mode. Lalt + enter is a keybind that will put the sim into exclusive fullscreen mode, which might fix the issues you are having.

The FOV problem? Care to explain? :)

I'm seeing exactly the same framerate as you on 1440p with a FX-8350 @4,6ghz, so I'm pretty sure a mid range CPU is enough, and you won't see much more improvement from having a high end CPU. Clearly the GPU is more important in the new engine. Speaking of GPU's! The author of the topic never told us what GPU the CPU was going to be paired with, which makes it impossible to give a proper answer.

The way I see it, the blur is to emulate a camera for those that want to take nice screenshots and make videos. Same thing with lens flare and lens dirt. Just go into the settings and turn all that stuff off.

Lol, I'm sorry, but why would they focus their promotion towards video gamers? They are not selling any products targeted at that audience. YouTube is a very wide platform, and is actually useful for them in promoting their products to the target audience, which mostly consists of governments around the world. I also belive there is a disclaimer on the DCS loading screen saying something along the lines of "The manufacturers and intellectual property right owners of the vehicles, weapons, sensors and other systems represented in DCS World in no way endorse, sponsor or are otherwise involved in the development of DCS World and it's modules".

Neither of those fit the hints given by Leatherneck. Haven't you been reading the speculation threads? :)

Slightly off topic, but I just wanted to say that I prefer a little more than 60fps when I use the TrackIR. 75-90hz is a good sweetspot for me. At 60fps the latency of the head movements is just a little too much for me :) That's on a 144hz monitor though. If I had a 60hz monitor I would cap at 60fps, but I'm glad I don't have to do that. :)

Microstuttering https://en.wikipedia.org/wiki/Micro_stuttering

What I'm saying is that v-sync works, but I am using the ingame setting, not the one in catalyst.

Yes, VEAO has it on their list, but that list is long with unfinished, and unstarted projects and I think the Gripen is far down the list when it comes to their priority, so I doubt I'll see it in my lifetime.

Works fine for me with a 290X and driver version 15.8. I'm using freesync/adaptive sync though. Only works in fullscreen but that is to be expected and applies to any game/sim/3d application.

Yes, I know why, and I have answered the same question multiple times. :cry:

Let's try to narrow down the cause of the issue. Is anyone seeing this problem on AMD gpu's or is it only on nvidia? Personally, I am not having this issue on my AMD 290x with 15.8 driver.

There has been more reports of this on the forum. Smoke is working for most of us, but is missing for some people. Not sure what causes it.