Brisse

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.

Only on your PC apparently :) What are your graphics settings, graphics card and driver version?

Temporarily disabled due to heavy load on the servers. Should be back soon.

ED halted updates for a while because the load on their servers were too heavy. Maybe your problem is related to that? http://forums.eagle.ru/showpost.php?p=2501438&postcount=5

That would be one city if I understand things correctly. Still, I have seen Wags fly over it on his streams and videos and performance doesn't seem to take too much of a hit above Las Vegas. I'm still optimistic :) But then again, I'm seeing 70 - 125 fps under all types of conditions on the black sea map in the new engine, so there is a lot of headroom, if the performance were to be slightly worse on NTTR.

I don't think NTTR performance will be that bad. It's mostly desert with few trees. When Wags was streaming from NTTR, the framerate has been good. Sure, he has a beastly PC, but still.

There you go. That 1.5 screenshot is more representative of what I see ingame. There's a clear difference between 1.2 and 1.5 there.

I'm still seeing the black engine smoke.

They do actually, but when I fire up the sim, it doesn't look like the screenshots. Not sure if it's caused by image file compression or something. I could never get the sim to look as dark as the screenshots.

Hey, I couldn't wait until tomorrow so I went ahead and checked under some different conditions. I use a high end IPS monitor, hardware calibrated according to sRGB standard, gamma 2.2 (0% deviation) and average dE 0.4. This is excellent hardware for the purpose of this test. As I suspected, it's not as dark as what you are seeing, and certainly not too dark. I cannot under any circumstances make it pitch black even with heavy clouds and no moon. Conclusion: Your (BackboneOne) monitor is not calibrated properly. Also, I would like too see more pronounced difference between no moon and full moon. Heavy clouds and no moon should be pitch black, but it isn't.

There is currently no such option for Freesync, and AMD has made some hints that it is not planned to be implemented in the future either.

If the monitors are the same size and aspect ratio, 4 pixels on 2160p looks exactly like 1 pixel on 1080p.

The problem with that is that different monitors have different pixel sizes, and people sit at different distances from their monitors. I'm not sure there is any way to make this fair, but I quite like the current solution. I for one would never lower my resolution below native to cheat, and I think most people in DCS are fairly mature about things like this.

Are you using a calibrated monitor to come to these conclusions? I haven't tested flying at night yet in 1.5, but I'm just saying, that a properly calibrated monitor with decent accuracy is absolutely critical when judging these things. Maybe I will try a night flight tomorrow and see for myself :)

That does sound wierd, but there is a possibility that you have stutters that are not visible on the framerate counter. This is because the number you see on the framerate counter is an average over a certain amount of time, or a certain amount of frames, so if you have a stutter that only lasts one or two frames, you will not see it on the framerate counter. These are often called microstutters. To analyze the problem further, you will need to look at the render times of each individual frame. The reason you might not see this with v-sync on is because with v-sync there is a frame buffer. It could be possible that the frame buffer filters out the microstutters.

What.... Did the heat seeker go for your GPU? :megalol:

You english is fine but it is still very hard to comprehend becouse some of the things you say are not technically possible. I think when you say stutter, you really mean tearing, right? If I replace stutter with tearing in your text, it starts to make sense. Stutter: Drops in framerate caused by v-sync when graphic card cannot keep up with the monitor refresh rate. Tearing: Broken frame caused when graphic card sends new frame to monitor in the middle of the monitors refresh cycle.

Gripen has conventional means of thrust, so no. It's going to be the Viggen. :)