Wali763

Im "only" 2000km away from Moskow. Thats about one day of driving with a car. But because of Covid, a job, a family, customs....... you name it, I cant go. But I already thought about it. Maybe in July when Im totally desperate! But that would be a reallly interesting thing.... Not sure, if ED want to get so close to custumers though.... Cant you elevate somebody with some software-skills to be interim closed-beta-tester?

Yes, I did a few times when I was stuck, but it never worked for me. EDIT: Just tried it once more and now it worked. Thx.

I have got a 12GB 6700XT and my DCS crashes all the time. Over night I did a complete reinstall of DCS. First installed Stable (after deleting the DCSOpenbeta-folder) and then Openbeta, which copied many files over from Stable and downloaded the rest. Since somewhere above stated, that only the one system with an update to 2.7 and not a direct download of 2.7 worked for him, I thought this way it could help. Then I renamed my old SavegamesFolder and started DCS. Loaded the FW-190D Takeoff-IA on the Caucasus-map and after one TO and landing hit LShift+R. Guess what..... The loading got stuck at "Mission load done" like in most instances. At least I was able to send a Crashreport. Usually, DCS and most of Windows does not react anymore (except for the taskmanager, where I still cannot quit DCS) so I have to log out of the local Win-account and back in to get back going.

Well, that dont work for me either. Did go to Stable last week, and there got a supposedly rare "second misson" graphical glitch. My respective post is on page 11 of this thread. That problem on stable was by far not as bad as the crashes in Openbeta, but since both made trouble, I decided to go with the "newer" Openbeta.

Considering, that this thread already has 22k+ views I dont think a tiny minority has this problem. But there has to be a problem and its in EDs intrest to find it. Maybe a new Windowsupdate or DCS-Update all oft a sudden makes it affect many more people? Still would not expect any remedy in the immediate future.... The good thing about this situation is, that my intrest buying the Hind is gone for now. Already have my eyes on others games with the saved money....

Actually I was not expecting this, since HWUnboxed stated that this phenomenon (older Radeon being faster than eg 3080s when coupeled with weaker CPUs) only applys to games, where the CPU is completly used, as of meaing ALL threads at alomost 100%. But since DCS is requiring mostly singlethreaded performance and most of the cores of our CPUs actually dont have to do anything, such a situation should not arise. Not sure exactly, what it is, but it just works visibly better then before with the 2070S in my situation. YMMV of course.

Hi. 2D with 1440p monitor here. I upgraded from a 5,0 GHz 9600k to a stock 9900k (gave it back) and than to a 5600x in February. Also added additional 32GB Ram. In some scenarios I was often having stutters (MP or the SC). Not low FPS but stutters, where eg the antenna on the island would not smoothly rotate but often briefly stop. 9900k did nothing at all, 5600x and RAM only a bit. What cured the stutters was going from a 2070S to a 6700XT. Very interesting considering the stutters were clearly CPU-related. Could be SAM or the supposed less CPU demands of Radeon-GPUs.... Anyway, Im happy now (if DCS does not crash of course), even the 6800 would have been perfect but I was unable to get one at a not completly insane price. In hindsight Id say much financial effort for very little gain.........As always in DCS.... Still, I could not recommand any way. Depends too much upon the personal situation. Still the IPC-advantage for sure would support going AMD. Also considered the 10700 or 10600K but since the 9900k helped zero I went for AMD. With Intels 10th vor 11th gen Id get a non-K CPU, since differences in stock are tiny and OC requires a massive cooling solution, still offering very little more perf. EDIT 2 Hours later: I attached a pic to demonstrate the change the 6700 made. The problem was mostly with the Tomcat (A and B more or less the same) and not with the Hornet, that had a straigt frametime-curve. Every large spike in that curve meant a stutter. In the last line (with the 6700XT) one can see, that those spikes from above (then with the 9600K) were gone; with the 9900K there was no change and with 5600X they seemed less (not conclusive though) and still some stutters. Even though I made the last curve with 2.7 and the other curves are from 2,5.6, I witnessed the same with 2.5.6 on the 6700XT.

Thats the general problem of DCS, that no matter what hardware you throw at it (even in 2D), you still will have to make compromises. At least, if you match the hardware correctly, meaning, getting a 3090 for a 4K and not for a 1080P monitor eg. Anyway. We got our son a few days ago a 32Inch-4K-monitor for his Switch/PS5 and I also tested it with DCS instead of my normal 144Hz-1440p-monitor. I have to state first though, that Im capping fps with my monitor to 60 for best TrackIR-compatibility, which also makes this comparison kind of more even. IMO 4K looks crispier than 1440p, still the difference being far from big. Most visible to me is the difference on dials ans screens. I mostly did not have problems reading them with my 1440p-monitor, but going to 4K it suddenly seems much clearer. Genral textures look a bit finer, but there the difference is much smaller. But there are also certain drawbacks, first of course hardware-wise. I have a 6700XT (which is supposed to be 5-10% slower than a 2080Ti/3070) and I cant drive the montior in a way I would like it to. I found a setting (no MSAA and medium textures) that is getting fps-wise to a spot, where it gets ok for me, but what is the use of having 4K, if you have to look at poor textures and some aliasing? Even when I was having 55-60fps (freesync enabled) constantly, is felt more stuttery than on my 1440p-monitor with 60fps. Overall Id say, if you got the hardware, and Id say a 3070/2080Ti is not enough, go for 4K. It is definitly a increase in visual fidelity. If you have to make compromises like I do, I dont think its worth it. Still Id not expect a big increase in overall experience. Especially if your concentrated doing things like flying, dropping bombs etc, the difference will get even smaller. But I guess that is very much dependable of the individual user. What I also found out it, that I do prefer curved monitors. Going from my curved to the flat 4K at first was a bit strange and even after 2-3hours is still did not feel "right". But again, thats mostly personal preference.

Just installed in the new update with no change. First LShift+R ended in a crash, the second at least produced a crash-report, that I could send. Using RadeonChill to cap FPS to max of 60 because of TrackIR. Also am using a slight undervolt on my CPU (PBO Curve optimizer) and on my GPU. Yesterday, when I both CPU and GPU set to default and clearing all the mentioned folders it did not take long to witness the first crash, or freeze, as somebody here called it, that does not get crashes......

I did all of those things mentioned above. Del Temp-folder, clean FXO and metashader2-folder, did a repair and install the optional Windowsupdate, reduced the loadradius to 99000 and even just renamed the Savegame-folder so a new one got created. Since I have a Radeon-GPU I did not do any of the NV-related stuff. But I have the most recent Radeon-drivers installed. First start of DCS: did not get a second-mission-load-crash. Got it right at the first load! Sarcastically I could say, so it partly did work. Had this first-Mission-crash three times in the last week, when tweaking for a solution for the second-mission-load-crashes. that I still get quite often. Crashreport No 577 (or so) was sent.

Thx for the info.

Hi. Anyone got an idea how to get past mission 5? There does not seem to happen anything. After I pass WP3 I should make a CAP between WP2 and WP3 and thats it. Nothing else happening, other than the odd SAM-launch, if I venture too much east at WP3. No Migs ever in sight. At least not on my RWR or Radar. The Hornets just fly circles and never attack. And I cant even refuel, since there is only a BoomTanker around. Any ideas? Thx.

Out of curiosity, would you plz report back in three or five days? I also had some "solutions", that I thought, "now it works" and two starts later it was the crashing was back.

What pagefile-size would you recommand vor a 64GB-System? I tried 33554MB which did not help...

OK thx. Still very strange, that this behaves just like 'our' problem in 2.7. And great, that this is not my GPU. As a sidenote. Since the update to 2.7 I had 3 or 4 instances where I had a tiny flicker. Only one small part oft the screen (like a large leaf on the canopy) went black for a moment. But only a few times in a 5+ hours. So actually not a problem...

Now, this is getting really, really strange for me. Or with my system..... Because of all the troube Im having with the second-mission-crash, I installed Stable and installed all modules again and left OpebBeta with only the basic CaucasusMap and my most important planes like A10/F14/F16/F18/FW190Dora.... Just to be able to check, if the problem still exists. Today it did several times. Now this evening on Stable I witnessed some strange graphical glitches when doing Takeoffs with the Dora. Right after starting the mission the screen started to flicker. I then was able to "catch" such a frame, which is actually only one in a few seconds. See pic below. At first I though my GPU (a new 6700XT) was the reason, but then I found out, that those glitches only happend in the second mission!!! I did this for over 5 times and always at the first mission after loading DCS it was ok, and upon hitting LShift+R they came back. Only once I had to hit LShift+R for a second time to get to the glitches! Again: this was on Stable! Then I did two Hornet- and two Viper-Missons in Caucasus (takeoff or freeflight from IA-Missions). No glitches upon reloading the mission twice or more times. But when I opened the Dora-Caucasus-Takeoff-mission in the ME and changed it for the Hornet and then for the Viper, those glitches also happened. But guess...... only in the second mission! Also had some glitches on the Anton-Freeflight-mission but those were much rarer and much less noticable. Could this be related to my system? As stated above my OpenBeta is about 1 month old and the Stable was installed two or three days ago, but the modules were all installed yesterday, where some files of OpenBeta were copied over. Still had to download some 60+GB. My core-parts (MB, CPU and GPU) are all pretty new. Along DCS Ive been playing some MetroExodus and there I had now trouble at all. In the next days, Ill will do some further testing with the Stable to confirm my findings.

Lastest dcs.log dcs.20210426-182147.dmp dcs.log

Hi. I just did a cleanup, emptyed the Temp, the fxo and metashaders2-folder, then set my pagefile to 32GB (even I have 64GB Ram). First mission-reload ended in a crash. Then unchecked the Fullscreen in the settings. Again. First Mission-reload => crash. Both times with no crashreport-dialoge and I had to log out and back into my windows-account.... Yesterday, by making a a DCS-cleanup my system worked for some time, for sure more than 20 reloads- without a problem, but then it started again.

Not for me..... Just a brief history of my system: New CPU/MB in March, new GPU in April. With the Systemchange also new Windows and complete fresh install of DCS. No mods except for SRS. Did a repair of DCS, renamed Savegame-folder. Used Fullscreen off or on. Tapped Alt+enter numerous times. Nothing worked. Lshift+R will kill DCS in most cases. I just started the download of Stable. Also did a cleanup of DCS removing SRS. Maybe this will help and I dont have to move to Stable.

Hi. I first witnessed this in the L-39, where artifacts showed up on the edge of the frontpanelcover. Then I saw it in the F-86, all starting in the Take-off-IA-Mission in Cauasus. Turning SSAO off resolved this, turning SSAO on, brought the issue back. See attached pics. Those squares do flicker all the time and sometimes go away, but then come back again.

No change for me after the Update. LShift + R often causes a crash. Also had an odd crash upon shutdown, when the whole screen stayed black. Opening the Task-manager to quit DCS was not possible, but hitting Win-Key opened the Startmenu. Had to log out and in again to shut down DCS.

I need to give this a try. Tomorrow. Still keep getting crashes constantly. Most time since last years faulty February-batch Im was not able to use "Fullscreen" by default (checked in the settings) anymore. Usually just got stuck during the loading-screen (DCS not a single mission). It seemed, the game went to the menu, but display stayed at the DCS-loading-logo. Only late last year I went back to "fullscreen" and only had a few problems since then. With 2,7 I instantly had perf problems after tabbing out to Discord or SRS or something else, which caused DCS to not be in fullscreenmode after going back to the game. Alt+Enter solved that and also the stutteryness because of Freesync not working in windowed mode. Still am using Fullscreen checked but will give this a try and uncheck it. Even this is a PITA to me. BTW all my friends in the squad dont have this problem, but they all use VR and I dont... Maybe this problem is only related to 2D-use? Anyway, I just recently wrote quite a few lines in a new thread about how Alt+Enter should be a thing of the past but still keeps creeping up everywhere.... but then I deleted it before posting. I hope Vulcan next year (ED said Q4 this year I think and with their usual delay Im guessing mid next year) can solve all of this ancient Alt+Enter annoyance.....

Strange here. I just tested DCS again (had no time on weekend) and loaded fore sure 20+ missions and reloaded them (Lshift + R or via Debriefing-screen) and all went well. The exited DCS, restarted it and right at the firts missin the reload crashed...... By now ED has about 10+ crashreports from me alone.

Hi. I went from 32GB to 64GB in hope to cure some stutters. Always had 28-30GB Ram-usage before, now up to 36GB. Did not change a thing. I dont think having 30GB RAM in use also means your low on RAM. I think the system just uses the RAM if its there even its not really nessecary....

Strange thing is also, that sometimes DCS.exe stays in the tasklist, so when starting again, you get the message of the second instance, that is not allowed. So you need to manually quit dcs.exe to be able to restart it. Also happened, when I choose at the end of a mission "Quit to desktop", so after a "normal" closedown.