RedShoes

Esac_mirmidon, your patch did not work for me. Or perhaps I just did not know how to apply it.... your patch had 1 file "bf109cpt_glass.rar", which I was supposed to put to the directory "DCS World 2 OpenAlpha\CoreMods\WWII Units\Bf-109K-4\Textures". I did exactly that and it did not work. Was I supposed to unrar your archive and place the contained "bf109cpt_class.dds" in to the directory??? I tried also that but it did not work. My directory "DCS World 2 OpenAlpha\CoreMods\WWII Units\Bf-109K-4\Textures" contains only one file "Bf-109K-4.zip". That zip file contains several .dds files. One being named "Bf-109K-4_glass.dds" i.e. different name as the one in your rar. So how exactly should I apply your patch?

What is the process of capturing a airfield, city or a comms centre? I killed all the ground targets around Isigny once and got a message saying something about helicopters needed to transport troops there. But there are no coppers in the WW II Blue Flag. Sorry if this was already written down somewhere and I just did not find the info. Like them armed watch towers! They lite up like candles with couple of bursts ;-)

I’m on EKWB custom build water cooling and have checked my temps with realtemp and hwinfo64. The temps are definitely ok and I generally keep dust out of my system. I hope it’s being addressed, but that is really not the impression I get during the last several weeks! Actually the impression I got is that the developers have been on summer vacation and pretty much nothing has been done at least for a month now. The last update on DCS 2 change logs is from 21. June. https://forums.eagle.ru/showthread.php?t=146968&page=3 I have not noticed any improvement for several weeks now. I sincerely hope that my impression is wrong and the issues are being addressed with the highest priority within ED development team. I have play with 1 monitor and have not used any multi monitor setups with DCS 2. I usually have a 2nd auxiliary monitor connected to my PC for teamspeak, browser, resource monitor, task manager,… or whatever, but have also tested with only one monitor connected to my PC. I have several monitors at home and have tested several resolution setups. For me they all have stutter and freeze. I also initially thought that resolution has a direct impact on stability, but I have not been able to confirm that. In fact, my current view is that the resolution does not really make a difference for me. I get stutter and freeze on all resolutions I have tested. I have tested e.g.; BenQ XL2411z @ 60Hz 1280x720, 1600x900, 1920x1080 BenQ XL2411z @ 144Hz 1280x720, 1600x900, 1920x1080 DELL U2711 @ 60Hz 1920x1080, 2560x1440 Asus pg348q @ 60Hz 2560x1080, 3440x1440 (w and wo g-sync) Asus pg348q @ 100Hz 1920x1080, 2560x1080, 3440x1440 (w and wo g-sync) Oculus Rift CV1 i.e. 2160x1200 As I said, I get stutter and freeze on all the above resolutions. I’ve tried numerous combinations of different in-game settings for textures, terrain textures, water, visib range, shadows, MSAA, lens effects, HDR, clutter/grass, trees visibility, preload radius, anisotropic filtering,….. deferred shading on or off,…. I’ve tried different settings on n-vidia control panel based on suggestion on other DCS 2 stability related forum threads. I’ve also tried different sound devices (as there are a lot of sound related errors in the logs). Did not make a noticeable difference. I’ve tried re-installing the game, repairing and re-updating the game, removing all mods, removing tacview, un-installing the game, CCleaner to remove any windows registry entries, re-installing, removing all usb-device except keyboard and mouse. Different n-vidia drivers, with and without n-vidia experience, cleaning old drivers with DDU,… I’ve tried 3 different PCs. Windows 7 and windows 10, 2 different cable-modems, tried having a older sitecom 100mbit router with only IP4 connectivity (instead of 1gigabit with IP6 support), tried GTX 980, GTX 980ti and GTX 1080ti on my main gaming PC…. After all this testing and pissing about with settings I went and did a completely new clean install of Windows 10 on my PC. Installed latest nVidia drivers, TrackIR, new DCS world 2 installation and gave it a try. Bf-109 Normandy instant action take off hot. After 3 minutes in the air complete game freeze! It seems to be that whatever I do, whatever tweak, all I get is stutter and freeze. Stutter is when the time between frames noticeably vary, sometimes up to 1sec micro freeze. Freeze when the game completely freezes up. The last frame is displayed, the sound is stuck, i.e. playing the sound from the last moment or frame of the game, no reaction to controller inputs or key presses. Often task manager shows DCS not responding. This game freeze can take from several seconds to a minute or two or even longer. Sometimes it recovers. Sometimes it ends on my plane crashing (depending on course at the time of the freeze). Sometimes it ends in a disconnect / timeout from the server. Sometimes it ends in a DCS crash with crash logs. I have attached several of these crash logs to this thread already. Often I end up killing the DCS manually from the windows task manager after a minute or two freeze. Sometimes I can fly for a while with no problems, sometimes (although rarely) I can even get a good dogfight on multiplayer server and it work just fine. But very often when I get engaged on a multiplayer I get bad stutter and shortly after a complete game freeze. I also get that sometimes on single player, like the 109 or Spit instant action dogfight or just flying alone on Huey or Gazelle, but I do feel I get the problems more frequently on multiplayer. I have talked to people on TeamSpeak asked about their experience and their settings. I’ve had couple of cases where the game froze simultaneously for all three of us on the server, but mostly people seem to experience some stutter, but more rarely a complete game freeze, like I’m suffering about. To me DCS 2.1.1 alpha is buggy and currently not really playable. I’d say "No Joy!" Luckily it’s summer and there are better things to do than getting frustrated with this unstable game…. and for the rainy days there are other games that run stably in my system, like IL-2 BoS and DCS 1.5.7. Hopefully, some sunny day, the devs get back from summer vacations and fix their bugs. #EndRant #EndOfPayingCustomerFeedback

One more crash log attaced. Again some stutter and then a crash. This time windows pop-up "DCS has stopped working" Crashlog shows; 03862.089 INFO EDCORE: try to write dump information 03862.092 INFO EDCORE: # -------------- 20170711-212516 -------------- 03862.092 INFO EDCORE: �� 03862.093 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 00000000 00:00000000 03862.096 INFO EDCORE: 00000000 00000000 0000:00000000 03862.100 INFO EDCORE: 00000000 14E6F880 0000:00000000 03862.100 INFO EDCORE: F22B2E0D 14E6F8B0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+14838D 03862.100 INFO EDCORE: F22B2CB6 14E6F900 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+148236 03862.100 INFO EDCORE: F22AB7ED 14E6F930 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+140D6D 03862.101 INFO EDCORE: F294887A 14E6F960 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+986CA 03862.101 INFO EDCORE: F2D216C3 14E6F990 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+471513 03862.102 INFO EDCORE: F2D2186A 14E6F9C0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+4716BA 03862.102 INFO EDCORE: 76DF59CD 14E6F9F0 0000:00000000 C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 03862.102 INFO EDCORE: 76F2A561 14E6FA40 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 03862.274 INFO EDCORE: Minidump created. please fix Logs-7.zip

Another crash log attached. Again some stutter then freeze, this time it created a crash log. Most often it just hangs and I'll have to end dcs from the task manager. Crash log shows; 03020.205 INFO EDCORE: try to write dump information 03020.207 INFO EDCORE: # -------------- 20170711-195447 -------------- 03020.207 INFO EDCORE: D:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\dx11backend.dll 03020.208 INFO EDCORE: # C0000005 ACCESS_VIOLATION at E7B8E3FA 00:00000000 03020.211 INFO EDCORE: 00000000 00000000 0000:00000000 03020.214 INFO EDCORE: E7B8E3FA 001BD250 0000:00000000 D:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\dx11backend.dll ?interframeResourceSync@DX11Renderer@RenderAPI@@UEAAX_N@Z()+259A 03020.215 INFO EDCORE: E7491D09 001BD2B0 0000:00000000 D:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\NGModel.dll ?resetMults@NGModelLods@model@@UEAAXXZ()+9529 03020.215 INFO EDCORE: EC0A5311 001BD2F0 0000:00000000 D:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\Visualizer.dll ?DrawFlatShadows@RenderParserImpl@@QEAAXXZ()+1A1 03020.216 INFO EDCORE: EC0A9A35 001BD9F0 0000:00000000 D:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\Visualizer.dll ?drawDots@RenderParserImpl@@QEAAXXZ()+39F5 03020.216 INFO EDCORE: EC0D0E1C 001BF170 0000:00000000 D:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\Visualizer.dll ?Render@SceneManager_Implement@@UEAAXXZ()+19EC 03020.216 INFO EDCORE: 3FC920A6 001BF1E0 0000:00000000 D:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\DCS.exe Please fix. Logs-6.zip

Thanks for the suggestion. I have tried different windows paging file sizes or even disabling it completely. Did not make any noticiable difference. My paging file is on C: drive, windows system SSD. All the info should be in the dxdiag files I have attached earlier, but here is my system specs again. Currently nothing is overclocked as I'm experiencing these stability issues in DCS 2.1; MSI Z97 Gaming 5 Motherboard i7-4790K (not OC'ed, so running boost at 4.4GHz) - EKWB custom loop water cooling 32GB Corsair Vengeance DDR3 DRAM 2400MHz C11 PNY NVIDIA GeForce GTX 1080 Ti Founders Edition - EKWB custom loop water cooling EVGA SuperNOVA 1000 G2, 80+ GOLD 1000W Power Supply 2 x Crucial 250MX SSD - 1 for Windows, 1 for the game HGST HDN724040ALE6400 4TB HardDrive for data Asus PG348Q 3440x1440 Monitor @ 100Hz DELL U2711 2560 x 1440 secondary monitor @ 60Hz Oculus Rift CV1 Inateck USB 3.0 PCI Expresscard 7 (w 15pin Sata Power Connector) MS SideWinder Force Feedback 2 Joystick Saitek X52 Pro Flight Controller (Throttle only) Saitek Pro Flight Quadrant MFG Crosswind Rudder Pedals TrackIR5 About display resolution; earlier in 2.1 3440x1440 was running much more unstable for me than 2560x1080. Now in 2.1.1 I can not really say if there is a difference. In both cases I do get stutter and freeze problems. I do get stutter and freeze both in single player (e.g. Normady Bf109 instant action dog fight) or in multiplayer. Sometimes I can play fairly long 30 - 60 minutes with only minor stutter until freeze/crash. Sometimes I get the freeze in just a couple of minutes. DCS 1.5.6, 3DMark benchmark, IL2 BoS,... all run stably in my system.

Please take this with a grain of salt as I do not really know what I’m talking about, but… Could it be that you voltage drop is not the problem, but a consequence? i.e. the game stutters and freezes up due to some software bug in 2.1 alpha code. As a consequence, your graphics card does not have anything to do. It is not being fed by your CPU with data to crunch. So your FPS drops to 0, your GPU load drops, your GPU clock frequency drops and your GPU voltage drops as it does not need the voltage as it has nothing to do?!? I’m experiencing similar stutters and freezes myself and I read the forums and online chat in multiplayer that so are several other people. DCS 2.1 alpha is still not very mature. I’m not sure if GTX 1080 actually has a load based voltage control, but I could well imagine that. To my understanding GTX 1080 ti has something like that implemented. One overclocking method is to tune the GPU load based voltage curve. That can be done with for example MSI Afterburner, which I assume is basically very similar to EVGA Precision X. Before you go purchasing an another Power Supply, I’d suggest that you at least give a try to DCS 1.5. (the old Caucasus map). Try flying there a bit and see if it runs more stably. If you are not having the issue there, I would bet you just have to wait for the devs to iron out the SW bugs in DCS 2.1. …as I said in the beginning, I do not really know myself. It could of course be that you PSU (or your GPU) is kaput and you need a new one. But if it is, I would expect you to see problems with other programs too (watchdogs, DCS 1.5.6 or graphics benchmarks). I’ve got other things to do during the weekend, but as I’m experiencing very similar freeze issues myself, I’ll take a look at what MSI Afterburner reports for GPU voltage during such a freeze on my system (w GTX 1080 ti) sometime next week.

No TacView or any other mods or exporting plug-ins installed. Simply to keep to game as clean as possible. I do use TacView and some other plug-ins and mods in 1.5.6 and do not have these problems there. 1.5.6 is stable for me. I'm having the stutters and freeze / crash issues also in single player mode, so it is not only multiplayer or Burning Skies server related. My assumption is that there are simply still several SW bugs in the 2.1 alpha code / Normady map that need to be ironed out. From my limited understanding, several crash logs look like memory crappers / null pointer access, but that of course is just pure speculation. The devs need to sort this out. I assume we as users just have to keep reporting these, post as many crash logs from different systems as possible and keep waiting for the fixes. I have also noticed that the stutters and crashes seem to be much more frequent when I get in to a dog fight. Sometimes I can happily fly around with no problems looking for a enemy and as soon as I find one the stutter fest starts. Not exactly my idea of multiplayer fun.

Had to land for repair and rearm/refuel. Parked my 109 on the close by hangar as there were some pesky spitties flying close to our AF. Called the ground crew to repair. After they got the job done, instead of lowering my 109 back to ground, they raised it to the roof of the hangar. It very slowly slid sideways back to the ground and crashed :megalol: Burning skies server. Unfortunately it does not save a mission track file. Couple of screen shots attached. Please fix.

another crash. Few stutters during must have been my record so far of couple of hours of gameplay. Then DCS freeze completely and crash. This time in nvwgf2umx.dll DCS crash logs and dxdiag attached. Please fix. Logs (5).zip

A game freeze of about 1 minute, during a dogfight in the Burning Skies server. Needless to say that 1 minute freeze caused me to crash :( Anyhow, the game continued. I exited the server and quit the game. dcs.log and dxdiag attached. The log has more than 8000 errors like I mentioned on the first post, i.e; 04579.908 ERROR SOUND: source_add(host:woLA-16777990, proto:Aircrafts/Engines/RollsRoyceMerlin/MotorDry, alt_proto:): can't find proto MSI Afterburner screen shot shows the GPU usage and FPS drop to zero for about 1 minute. Resource Monitor from Windows Task Manager showed DCS.exe as Not Responding during this time. Please fix. Logs (4).zip

Again an another crash. Few stutters of 1-2 sec and then complete freeze & crash. Occured after ~50 mins of online gameplay at Burning Skies server. Crash log attached. Please fix. Logs (3).zip

Another crash. Online game, Burning Skies server. Had quite some stutter, at least 4-5 times for more than 1 sec. Then finally the whole game just crashed. Managed to get almoust one hour of gaming. DCS Crash logs and dxdiag attached. Please fix. Logs (2).zip

I'm having a frequent (several times during a half an hour fligth) stutter & freeze. Here the game simply stops for a second or longer. I've had freezes up to 15-20 seconds, that then still recover. Sometimes the game just crashes completely. When I look at the dcs.log file, I have noticed that often there seems to be a huge amount of sound related errors in there approximately when the freeze occurs. Errors like; 02286.803 ERROR SOUND: source_add(host:woLA-16779019, proto:Aircrafts/P-51D/MotorDry, alt_proto:): can't find proto If the freeze takes couple of seconds or longer, Windows resouce monitor shows dcs.exe as "not responding" MSI Afterburner shows GPU usage going to zero and frame rate going down. Logs and dxdiag attached. I have done DCS_updater.exe cleanup and DCS_updater.exe repair just before gaming. I suspect that the thousands of ERROR SOUND: source_add(....., alt_proto:): can't find proto are somehow related / causing the problem Please fix. In this particular case, It was a on-line game at Burning-Skies server. I exited the game after the freeze. Game returned to main game menu. I then pressed Quit. This lead to game crash. Crash log included in the log.zip file. Please fix that too. Logs.zip

Can't get Normady to run stably at 3440x1440 resolution Runs fine with good fps for about 10-15 minutes, then typically after a few stutters (freeze for about sec or two) the game finally freezes up / crashes completely. Occured to me pretty much every time I play for 10-15 minutes. Managed to get about 1 hour game play when I switched to lower resolution 2560x1080 and lowered textures to mediuim. Crashlog shows; C:\Windows\system32\d3d11.dll # C0000005 ACCESS_VIOLATION at F4912D72 Logs folder and dxdiag attached. PC specs; MSI Z97 Gaming5, i7-4790K, 32GB RAM, GTX 1080Ti, NO OC during testing Normady. Game settings Logs.zip

same for some other sounds too. e.g. Mistral model IR seeker or lock sound. If you crash with IR seeker "bleep, bleep" sound, the same sound continues after a respawn. Does not make a difference if you open and close the aiming reticle.

Thanks for that :thumbup: I was having the same problem and could not get it to work. The problem was that I selected the Altitude mode on the switch and then hit the AP button on the stick. No, you need to get it to straight line, no climbing/diving, over 120 kph and then hit the altitude hold mode on the switch in autopilot panel.... bang, and it's enabled and working. Some old video tutorials and Chuck's guides explain that you need to hit the Autopilot button on the stick. Does not seem to be the case anymore.

give the Ai max fuel (as suggested above), ground ordinance, ground attack task, slow speed, no MW-50 and average skill set. give yourself a good altitude and speed advantage if that is not enough, put the Ai on the same side, give it some way points to fly to practice your shooting skills against a non-maneuvering target. You will get get some friendly kill indications or what ever, but who cares?

I have also not seen any adverse effects of flying the Spit at 20K+ feet with empty o2 tank.

Please remember that youtube videos are highly compressed. You will not necessarily see the dot in a youtube video that the player himself did see on the screen while playing. What kind of monitor are you using? resolution and refresh rate? What are your game settings. I find that for the best spotting and target tracking you should run native monitor resolution with; MSAA x2 or x4 (off, is even better for spotting, but looks too ugly for me) Anistrophic Filtering x2 or x4 HDR, Depth of Field & Lens effects off. removing clutter/grass and low trees visibility can help on spotting against ground as a last resort for spotting the dot, you can try running the game at a resolution lower than your monitor native resolution, i.e. if you have a 2560x1440 monitor, try it at 1920x1080. It makes it look very ugly, but you might see the one pixel dot now easier as it is scaled up to several pixels on your 2560x1440 screen. Remember, spotting and target tracking is a skill that you develop over the time. You learn to spot the dot and you learn to anticipate aircraft movement and know where to look for the enemy as you improve your skills. It might help in the beginning to pratice spotting in single player with labels changed to just red dots (instead of black/gray dots as in BS server). Edit your labels.lua file for that under C:\Users\[user name]\Saved Games\DCS\Config\View

This is how mine looks like; ...and after doing this, I would say aftermarket Air Heatsink :) Custom water loop is good, neat, nice, quiet and achieves the best cooling effect especially for OC'ed CPU & GPU, but in my view it is over priced and involves too much work both building it and maintaining. Yes, you can perhaps squeeze the last Hz out of your CPU & GPU with it, but you might just as well get un-lucky with the silicon lottery and get a CPU that would not OC any higher with water cooling as with after market air heatsinks. Building you own water loop is a nice hobby though. If you like building your own PC, you prolly enjoy building a custom water loop for it too.

Yes, it is pretty obvious what the ground targets are. Just fly over them at low altitude and they should be shooting at you. ;-) If you can't still find them, check out the saved track either in tacview or mission editor. Do you have tacview installed? If not, check it out. The saved track should be saved in C:\Users\[user name]\Saved Games\DCS\Tracks\Multiplayer and for the BS server mission it should be named something like NORMANDY1944_ANTICIPATION-[date]-[time].trk You can check it on tacview or you can rename it to .miz and look at it on the mission editor in game. If I remember correctly, the BS server exports only current player data, so you can not really review aerial battles from BS server in tacview at the moment (as you see only your own aircraft), but there are other servers that save all the planes including opponents (mostly with 10 minute delay to avoid cheating). That is a great way after a mission to analyse what went wrong or what was well done during a mission. As indicated earlier by others, just jump on the TS of the online server you are logging in to and talk to people there. Mostly people are very helpful and friendly. If you feel you still struggle too much with multiplayer for your liking, play around a bit with the DCS mission editor. Check a youtube video or two on the mission editor and after couple of hours you should be able to setup simple missions your self or for example play a multiplayer online mission alone attacking ground targets or AI units if you rename the .trk to .miz as I wrote above in the first chapter.

My understanding is that the DCS Bf-109 K-4 does out climb the DCS Spitfire Mk. IX LF. Especially at low altitudes (before the Spit 2nd stage supercharger kicks in) and at least as long as the K-4 has not used up the MW-50 it carries. The difference may be bigger or smaller also depending on fuel loading. I did not read all the Reddit thread, but there was something about +25lbs boost on Spit in there. In DCS Spit you can not pull that much. Max climb is rated at 2850 rpm +9lbs boost. You can pull more, like 3000 rpm +12lbs, but definetely not +25lbs for extended periods. Anyhow, the K-4 does not out climb the 20mm hispano shells the Spit can sent it's way ;-) ...and there is one more thing, that might lead to mis-understandings here; When a on-line mission starts (i.e. Multiplayer server re-start with people on the server), the Spit is faster off the ground due to faster start-up procedure. No need to wait for the ground crew to crank up the starter. This gives the Spit a head start for the initial climb at the start of a mission. I have regularly out climbed the German team in my Spit at a start of the mission on the burning skies server simply by being fast at the start of the mission. I do not have hard data available, but there is really only one way to find out. If you are interested, I would be happy to jump in a multiplayer server together with you and give it a try. I have both the Spit and the K-4 on DCS 1.5.6. I'm available prime time EU (19:00 - 24:00 CEST). If you are interested, drop me a pm or let me know which teamspeak I should join and when.

I'm new to Gazelle, just bought it couple of days ago on Easter Sale. Like it a lot already! I would be more than happy to put on my Rift and jump on board with a experienced pilot to go bust some tanks. I bet I would learn a lot :-) I'm available prime time EU (18:00 - 24:00 Zulu). Drop me a pm or let me know what teamspeak server I should join and when and we'll give it a try.

+1 Yes, That's exactly what I would like to see! Large B-17 formation being attacked by Bf109s. Show us how they keep their box formation, proceed towards their target and defend with the .50 cals as the first one attacked goes thumbing down.