paradox64

aaaahh ok ! I didn't ask you because i was pretty sure you saw it lol BUT I also saw a thread somewhere who said that 2.5 is not a true fullscreen but a bordeless windowed mode due to game engine so i I thought you talk about this sorry for my english lol

I spent hours looking for the parameter responsible of clouds flickering and I'm sure it's this one, regardless of all the others. I created a mission at dawn spring morning with clouds at 6000 feets and I was able to reproduce the flickering all the time with immediate result. I changed every parameters in all ways possible AFR/AFR2/SFR, sync, AA, etc... and always same flickering. I saw that the intensity (the speed of blinking) was in connection with the SLI COMPATIBILITY BITS (DX10 DX11) and finally, with this setting (crysis/arma3/ etc ...) the problem has disappeared instantly

I'm pretty sure i had it one time without sli. I don't find too. It start when i recreate shaders but i put back the old one and same problem.

Thanks it's a bit better with smooth afr. I also deal now with clouds flickering. I tried your settings but the same... damned

Same here !

I tried alt-enter but it introduces hard stutters for me. I think each settings are very personnals cause of hardware. I tried and retried and now I m very happy with this ones. Also, since I have 32GB RAM I shutdown the pagefile and increase the preload radius to 300.000 in the "options.lua". It works very good for me. edit : I think G-sync is a problem for me too so I switched to fast sync and it works better

It's seems many settings are working more or less... i didn't test in windowed mode, i will take a look.

I found this elsewhere : For 8Mbit down and 2Mbit up connections: if not net then net = {} end net.download_speed = 1024*1024 net.upload_speed = 256*1024 or For 2Mbit down and 1Mbit up: if not net then net = {} end net.download_speed = 256*1024 net.upload_speed = 128*1024 Adjusted to my bandwidth it works perfectly for me. Thanks !

Thanks a lot ! The ProcessLasso tweak work perfectly. This v2.5 is far beyond my expectations !! :cheer3nc:

I did the same in almost all ways possible and I agree, SLI does not really improve a lot but for me, there's no stutters at all when I use 2 cards. I think it's a bit better with 2 cards. Take a look to this NVI settings but adjust AA to meet your actuals settings, just to see if there is an improvement DCS_Test_SLI.zip

Hi ! I noticed that I regularly hear the "release click sound" even when I have nothing under the plane. A bit like when you lose a GBU after a turn too fast except that I have no carriage.

Hi ! also, briefing tell to go on green channel 3 but I think it's a mistake because all the mission is on channel 1 Thanks !

OK guys you were right ! I just realized in 2.5, the tweak affinitymask I used is no longer useful and even harmful. I did a test without the tweak with only one card and it's the same but not better (not any more fps with one card against two for me). DCS or Windows better handles cores than before. But for sure SLI is wast of money in this case, fortunally I use it otherwise.

I did and you put me in doubt :laugh: In both case i start game around 45-50 fps until 120-140 fps regarding where i look with track-ir. Very similar results. There is no significant gain in terms of fps with two cards compared to one BUT on the other hand, the flow of images is clearly more fluid and more stable with two cards in particular during heavy scenes (low altitude / high speed) With a card, the gpu is used at nearly 100% while with two is 2 x 50% Maybe this is due to the fact that two gpu at half load are more cooler and working more fluid. clearly, the game is CPU bottleneck and cards are very under utilized. I also specify that I have a 40 lines PCI-E CPU, maybe it also plays in this case. So I made the tests in all directions until physically remove a card to understand and also to check why in the game's fps counter (RCTRL + PAUSE) tell about 12500 mb but I found it tell the same thing with a single card boarding 8 Go. So it's another thing... I think the game is more smooth with 2 cards for me but I agree, it's not very significant... Here my settings

Same problem here with M2000 and KC-130 !

Hi everybody ! Now that I finally have a simulator that run perfectly, I would like to share with you my feelings about it. Already, I use DCS on a M.2 SSD and a clean Win 10 operating system, excusively dedicated and a second small SSD for pagefile (swap memory). I don't know for quad core but for 6 cores like me, whether with my old 5820k or with my new 6850k disabling hypertreading and creating an autoexec.cfg file with the only line : affinity_mask = 63 permanently suppressed stutters. Regarding the SLI, it works perfectly with Nvidia inspector and the option SLI compatibility bits (DX1x) on 0x081000F5 (Dirt 3, Dirt Rally). I also disable the vsync in the game but use the nvidia inspector fps limiter at 40 fps. It does not sounds a lot of fps but in reality the game is PERFECTLY fluid even at low altitude and high speed. Regarding my settings in the game, it's simple, everything is at the maximum except depth of field which is off. I specify that I use a screen in 3440x1440. It's just... wonderfull :thumbup: A great thank you for the hard works of developers !! Hope it could help and sorry for my english...

Hello ! Juste a small post to thank you for this campagn. I just loved it ! I really hope we will have news of Berger in the new campagn ;-) I can't wait !!

Yes, no problem at all with affinitymask at 1365 (HT = on on bios) I created a autoexec.cfg in C:\Users\MYNAME\Saved Games\DCS\Config with this only line : affinity_mask = 1365 Sure it's a MotherBoard or a CPU architecture problem

I precise because I hesitated, the difference between x99-A/5820k/SSD AHCI and R5e10/6850k/SSD NVMe is spectacular. No stutters at all. A real pleasure. But all that only with the affinity mask tweak.

Hi everybody, Glad to join your community Hello John, I have exacly the same problem as you : crash at second time and affinity mask problem. On a very fresh install Windows 10 Pro 1703 x64, DCS world 1.5.6 and 2.1.0 as only softwares except for Eset Nod32 Antivirus 9 with Eagle Dynamics folders exclusions Here the exact configuration : Asus Rampage V Edition 10 (bios 1701)/ i7-6850k @4.4 / 16 Gb Ballistix 2400 / Asus Strix GTX 1080 x2 SLI / NVme SSD Samsung Pro 512 for Os & DCS / SSD Samsung Pro 128 for swap file G-Sync 3440x1440 I precise I didn't install any asus sofwares Also, I didn't have this problem with my previous configuration : Asus X-99a / i7-5820k / Samsung Pro 512 (Sata but no NVme) with Windows 10 1607 and the rest all the same I was pretty sure it was a Windows 10 Creator Update 1703 problem since I saw you post... We have the same motherboard and almost the same CPU (Broadwell-E). If I don't create an autoexec.cfg and set manually affinity mask, only core 0 is selected. Same, if I set affiniy mask to 0, only the core 0 is selected The strange thing is when I set affinity mask to 63 (all core with HT off in bios) game crash 9/10 time and when it launch and I start tasks manager, I see that only core 0 is selected. The only way to play with all core activated is to set Hyper Threading ON and set affinity mask to 1365 (010101010101) The problem is exactly the same for both versions : 1.5.6.5199 and 2.1.0.6002 The second strange thing is if I disable pagefile (swap memory) the game crash at startup and it wasn't the case with my previous configuration with the same amount of RAM. I really don't understand... mystery, mystery.. lol Sorry for my english Cordially