Kuky

I think you have some loading issue, as in, RAM or maybe vRAM runs out and it has to use HDD or load new textures, something of that sort. I think the sudden and drastic drops in FPS are caused by that. You could use GPU-Z to monitor what your video card is doing, how much vRAM is used... change a few settings in game (always do one at the time and see how it affects performance). On my GTX980 I saw all of vRAM utilised fully in DCS with only few MB left.

No one says Allo in Australia :) G'day :D

Changing should not affect your FPS, it will most likely just use little more vRAM.

Yes there is setting for individual vehicles also. Change as you wish.

Please note increasing this value noise1PerSquare has side effect of bad units spotting in TGP/FLIR (more sharp textures mean more pix-elation of the terrain, in which ground units are very hard to see) and also you might end up with more tiling effect of the terrain textures. So use at your own risk ;)

Read again what I wrote already. Settings were tweaked because they weren't good. Once more... if you have bad fps lower your visibility setting. I use 4K resolution and high setting is still very playable. If for you it is not, use medium or even low setting. Thats all there is to it.

That one is in here also, you just missed it in the first post http://forums.eagle.ru/showpost.php?p=2655680&postcount=24

See this thread for modified smoke which you can use to get what you want http://forums.eagle.ru/showthread.php?t=158404

Once again, because the "high" setting in 1.5.2 wasn't really high :music_whistling: If you have low end PC you should be using low setting. Just because the setting name was called high, doesn't mean its actually representing high settings, which is why it was tweaked. The setting naming is supposed to be self-intuitive. The Ultra and Extreme are for future proofing, or for someone that doesn't need very high FPS and prefers even higher visuals. Now, I will also add that this can likely be tweaked again as Caucasus is merged into 2.0.0 / EDGE, and also there are some issues with current game engine that doesn't allow better tweaking (or reducing) some of the settings. Lastly, please use low visibility setting, you won't be disappointed (it is not as "low" as you might expect) and you will get better FPS.

That's what I thought also... but after that case of my HDD blowing up, I stick with original cables that come with the PSU only :)

One thing that can make you psu or other component fry is if you use cables from one psu. Happened to me once when I used cable for hdd from another psu... which ended up in hdd blowing up in smoke. The pins are not always the same even if connector fits (talking about psu with detachable cables)

By the way the change of these config files was in the log, but change was not explained in detail.

Thats because Nevada map uses different config files which weren't changed.

You know if you want to change some values, you should do so for all the settings, not just one. You never know what setting others use :)

CPU usage will not increase because DCS would already be using the CPU to its max - keeping in mind DCS doesn't use all of the cores, it is still only single thread (meaning single core) application. So with 4 cores and 1 core used for DCS fully, when you add other things running on your system, seeing 30-40% CPU utilization is normal and expected. When mirrors are on and the scene has to be rendered (calculated) again... your CPU usage will not go up, but because CPU now has more things to calculate and DCS can't use more than 1 core, which is used already to its max, the FPS will go down.

Lower your visibility setting. The terrain config files have been adjusted recently. You should probably use Medium setting (you will still have nice visibility in game)

Its new effect added for the afterburner, it is actually more realistic then before.

Some short while ago for 1.5.3 the terrain config settings were adjusted for better visibility across all settings. So you need to understand 1 thing. Do not use high, and especially not ultra and extreme settings for visibility distances, or forests distance, if you do not have a top of the line PC (which includes very fast, later gen 4 core (or more) o/c CPU, and top of the line video card. The high setting is still very pleasant and has very decent visibility distance, you can't expect ultra and extreme (just think about what this work means!) setting... and expect good FPS when flying over cities and very dense forests, with high MSAA and what not else. People's expectations need to be re-adjusted after this terrain visibility settings adjustments. High would be plenty for most users, if on lower and medium end PC's... you should use low and medium settings, not high, and most definitely not ultra or extreme. HIGH settings should be used for high end PC's (the whole lot, not just one component) MEDIUM should be used for medium, and LOW for low end PC. Disable mirrors, use flat shadows, don't use depth of field, and don't use high MSAA... just to name a few. Start from there and see how each setting affects your FPS, and adjust (one by one) to suit.

I use PayPal also.

Guys.... few notes from me: DCS 1.5.3 is being slowly changed to work with 2.0.0 Some short while ago the terrain config settings were adjusted for better visibility across all settings. So you need to understand 1 thing. Do not use high, and especially not ultra and extreme settings for visibility distances, or forests distance, if you do not have a top of the line PC (which includes very fast, later gen 4 core (or more) o/c CPU, and top of the line video card. The high setting is still very pleasant and has very decent visibility distance, you can't expect ultra and extreme (just think about what this work means!) setting... and expect good FPS when flying over cities and very dense forests, with high MSAA and what not else. It just won't be playable with everything high. Anything more than 4x MSAA over forests is a killer... just think about it... hundreds if not thousands of tree textures, all needed to have MSAA applied... it will simply kill your FPS. The more MSAA, the more vRAM you need to have. Than add to that dynamic shadow (non flat shadows) and you are asking for trouble. MSAA also uses lot more vRAM.. keep that in mind. 2GB of vRAM, flying low over forests... with MSAA and high visibility settings, it will just not run smoothly. I think people's expectations need to be re-adjusted after this terrain visibility settings adjustments. High would be plenty for most users, if on lower and medium end PC's... you should use low and medium settings, not high, and most definitely not ultra or extreme. Now, I'll add more as to why you sometimes see forest trees shadows when trees are not rendered... it is because of change in FoV as you enter cockpit. By default, I think a 60° FoV and the distance at which objects are rendered as well as shadows, match. As soon as you start to increase your FoV (which happens at every mission start) the distance of rendered objects decreases, while shadows do not. This is why there is a discrepancy (and I hope this will be addressed by ED sometimes in the future). Keep in mind the sim graphics engine is still being worked on and improvements come slowly, I wish it would be quicker, but it is what it is.

No, because mirrors scene rendering (not graphical, but positional/calculations/etc) is on the CPU, while the MSAA is on video card, and scales with resolution (what you see on the monitor), so with or without mirrors, the scene size (your resolution) is the same.

Nothing else should be made free.

I don't need to see any articles, I have tried the effect using large values and I saw what was happening. You can stop talking now.

Well there is no image rendered over the model, the model itself changes. You can see this if you try increase max value to something large to make the impostor pop up very early.

Please check things before making such claims, I am not confusing anything. Impostors work in such a way that once 3D model of an object reduces to certain pixel size, and it reaches max value in impostors.lua settings, at this point the 3D model switches to impostor effect and then reduces in size (up to min value in impostors.lua settings) and then stops reducing in size and just starts fading (increase opacity) until its no longer visible. You can clearly see how this works if you change the min and max value to something like 100 & 300 pixels.