Kuky

Hold on a second mate... I don't think I need to look at how DirectX works. Common sense would dictate that software (which DirectX is) in order to get full capability and instruction set to work on the hardware... need hardware fully supporting this instruction set. Like I said, everything that happens on your system, must go through the CPU. I think I will leave it now as I think I am right and have given the reasons for that. If you think otherwise and that motherboard chipset and CPU type does not matter (in this case) then so be it... I will only agree to disagree.

Tonike, it's interesting that your motherboard (MB P8P67 PRO rev 3.1) is same 1155 chipset, same as msalama's motherboard. Maybe your m/b is DX10.1 also? EDIT: my motherboard is socket 2011 and 1 gen later CPU

Yes, I have 1.5.3 version, as well as 2.0.1 version as well as what testers have.. which is not available to public.

You do know that any executable is run on the CPU? And only way that this executable and any graphics effect/whatever has to be going through the CPU? Its the CPU that talks to all of the hardware in the system and "tell it" what to do. In case of video card, it passes on instruction of the game engine to the GPU and then GPU handles it part of the job. In LOMAC days, or DCS prior to move to DX11, the CPU was handling most of the work and GPU was not. Now this is shifting and more work is offloaded to the GPU. But regardless, which hardware does what, still all things have to pass through the CPU as CPU is the heart (or should I say brain) of the system. Anyway... if you think you are right, and you say this doesn't matter, then what else could it be that we have this "mystery reason" why DCS runs worse on his PC compared to mine?

Well, there is a difference between being able to run DX11 and using DX11 to its fullest potential. The CPU can emulate things, but this is at some performance cost (because emulating means more CPU usage). So yes, you don't need new motherboard/cpu, as clearly you are able to run DCS which is now DX11, but I am very certain that this is at some performance cost. The man has same video card as mine, he has his CPU running at slightly higher clock then mine, but says that even with reduced visibility settings (and maybe he tried reducing other things) he can't get DCS to run smooth, while I can (and I run 4K resolution, not HD which add more performance hit). If CPU clock is the king and fact that i7 2600 and m/b is not DX11 hardware which you say doesn't matter, shouldn't he be able to have same performance as me (or better as he is not using 4K resolution)? Fact that he doesn't... shouldn't that incline to think that I am most likely right?

I wouldn't be sure about that. The GPU can only get instructions from the application/sim, through the CPU/motherboard. If some sim instructions are in DirectX 11 and CPU can't talk in DX11, then the GPU won't be getting what it needs to run DX11 (I think). I would say developers (of any game) can respond to this as they know best how their game is coded.

wait, you have 12GB of system RAM? and GTX980... with 4GB vRAM? Is this right? SSD won't help if accessing Page File is the case. Also more sticks of RAM is not better, it means more devices for CPU to talk to and that only slows it down a bit... it's better to have 2x 8GB RAM sticks then 4x 4GB RAM. Can you first try (download if yo don't already have) GPU-Z and keep it running as you play DCS, and monitor how much vRAM usage it has. If vRAM is maxed out try lowering some settings first. Also post your in game settings.

If you are hearing HDD load that is not a good sign, it most likely means the RAM is not enough a system starts using page file on the HDD, and HDD are very slow compared to RAM.

I'll tweak the file now and upload it, I will reduce few values, I want to see if it helps you EDIT: its attached now... I changed few values in LOW setting. Please try it and let me know how you go Low.lua goes in ...Config/Terrain folder (I have reduced districts distances) Shadows.lua goes in ...Config/Effects folder (I have reduced the max distance of shadows) Don't use forests slider to large distance (9000m is enough to match this Low.lua file) Low.lua shadows.lua

I just had a look at your motherboard specs, it shows on the board itself DirectX 10.1 (http://www.pcgameware.co.uk/images/ASRock-Z68-Extreme4-Gen3-21.jpg)? The i7 2600 is also bit old CPU now, I am thinking this is your bottleneck, it would make sense that object count is your most affecting FPS factor. I would recommend you use LOW visibility setting. But this also makes me wonder if your motherboard actually supports DirectX 11 which EDGE is now using?

Whatever

I disagree completely. 1. setting were adjusted because they needed adjusting (there is more reasons why which you simply don't know anyway) 2. if people with low and medium PC could play with high FPS on high settings then clearly these settings did not fit the description they represent 3. if it's a psychological thing, as you say, then accept that it is psychological effect on the user which user needs to understand and adopt, and not a problem with the software. 4. if settings user picks do not give good fps and user has option to lower them (provided user's PC meets the minimum specs), then it is user error if the user does not chose to do so. and I will repeat one more time: The tweaked values of the terrain config files are NOT the reason why users have bit of stuttering in areas with large forests when they have dynamic shadows on. People should quite frankly stop blaming these changes to their problem with this as they are NOT RELATED! The tweaked values also give better visuals for lower visual distance setting... so user should not feel shy or offended if user needs to pick lower name setting then what they had before the update. There is no difference in Low setting in 1.5.3 compared to High (or even Ultra) settings in most areas... if user can't distinguish this this is again user error! When someone shows a video of them using highest setting in game and then complain they have not 60fps... this is user error because this user did not know/see/understand, or refuses to, chose appropriate setting for his/hers PC. This user can pick lower setting that is SUITABLE for his/her PC, but chooses not to... and then complains. wow. FACT is, on my 3 year old system (and graphics card which is not the most top hardware) can play on 4K resolution and High visibility setting, and get good FPS... this proved that DCS 1.5.3 is NOT a hog or plays like shit, as some people make it out to be. I have no more patience with these kinds of people.

Alright, I checked the view when ejecting in F-15C in MP (with DCS 1.5.3) and it looked correct. The first person view was on the pilot the whole time. So I see this bug is definitely fixed. PS: I have found only on dual seat aircraft like L-39, when ejecting the view switches first to back seat, but I have already reported this. As far as single seat aircraft goes, its definitely fixed. I would suggest you run a repair of your DCS and not use any mods and recheck.

You can lower visibility distance to low. You can lower shadows to flat only. Just to name a few. If your pc cant run it on high settings then common sense would be to use lower settings... whuch you haven't done but you complain anyway.

So this issue could be for either F-15 or MP. I think later... I'll check that one also.

yes

This looks already fixed. I just flew Su-27 in latest 1.5.3 OB and I ejected and my first person view was there all the way throughout the whole ejection sequence.

Yes please, set it to 100000 and share your amassing findings with us all :)

One tip when you are submitting logs/crash files. I see you have archived crash files back from 2014... why? They are not relevant to the crash you are getting now, right? What it doesn't have is crash file from today, which is what we need if you are getting crashes now/today! So... Please do this from now on when you submit logs When you get a crash, if you can replicate it again, delete your logs folder, start DCS again and run a mission (or track) where you get the crash, and once the crash happens, submit the relevant crash file from the log folder as well as mission and ideally, last saved mission from ...C:/Users/YourName/AppData/Local/Tesmp/DCSVersion/LastMissionTrack.trk This track file along with crash file is what is most helpful The track can be used to run by developer (or tester) PC and if crash can be replicated, ED will have best idea what causes it

I think I have solution for that also. Try this Shadows.lua file attached (it goes into ...DCS*/Config/Effects folder - whatever the DCS version it is) and set Shadows in Options to LOW shadows.lua

Can you please try setting Shadows option to Flat Only. See here: http://forums.eagle.ru/showpost.php?p=2690847&postcount=133

Can you please try setting Shadows option to Flat Only? See here: http://forums.eagle.ru/showpost.php?p=2690847&postcount=133

Alright, I think I have the solution. Please see my DCS Options Setting in attached image Note I have High settings (including visibility distance) and trees at at 25Km... so nothing shabby or low in the setting. My FPS was stable 60fps and I did not have any stuttering The Terrain Flat Shadows are disabled, but Shadows are set to FLAT ONLY Please try it and see how you go :joystick:

I've just taken off my fps limit and let the DCS run up to 60fps. On high settings (I had forests on 30km distance and only disabled mirrors, depth of field and sun glare... MSAA at 4x and still 4K resolution) and it was stable at 60fps and only went down to 40fps over large forests when I am low. I am certain now that tree shadows are the cause in lower FPS. But see, if I leave my fps limit at 38 I won't even notice this and DCS will be smooth pretty much all the time. I had GPU-z running and it was showing high GPU usage, up to 99% and vRAM was around 2.6GB so all working fine. There's one more thing you could try... check if your video card is actually in 16x PCI-E slot? GPU-z can do this for you, or you can check your motherboard manual and see what PCI-E slot is the main one that has 16x Bus Interface and make sure the video card is in that slot.

See my PC is very similar to yours, the CPU, well and motherboard, are only different. I presume you don't use 4K resolution and if so, I don't see you should be having issues running smooth FPS on at least, medium visibility settings. I cap my FPS at 38 using autoexec.cfg and running High visibility its mostly stable at that limited 38fps (I don't really need 60fps now anyway) and I use max distance for forests also and no flat shadow. Over cities it does go down to high 20's but its not stutter fest, either. If I turn on mirros for example, yeah, that'll start to stutter. I really don't know, if you have tried flat shadow, just HD resolution and Medium visibility distance setting, you should see nice FPS. Something is up with your PC config... some BIOS config maybe, or graphics driver setting... I just don't see you with such similar PC having so much worse performance then mine? :noexpression: