XPACT

Not sure honestly. I've heard it long time ago from MiG29 pilot in a documentary and didn't think much of it but few days ago saw a post here on the forums from ex MiG29 pilot and he also mentioned that you lose RWR in STT and now I can't find that post... Another thing tho in the documentary pilot says it in a way that can be interpreted like you only lose missile launch warning but other parts of RWR might stay operational

They could do this but you would be unable to join MP as it would give you drastic advantage. Clouds, especially when there is combat involved, must be the same for everyone (opaqueness and shape) and in sync. Precision of rendering is already defined from LOW to ULTRA and doesn't give much advantage to someone using lower quality preset. I know many wouldn't care because after all DCS is played in SP mostly. So I am not against it but honestly think that new clouds are major thing in adding realism to the sim and I wouldn't ever fly without them. This one is probably due to people having very strong GPUs and playing on lower resolutions (example RTX 3080 on 1440p monitor), their graphics cards weren't utilized to their maximum in the first place and were limited by CPU. I for example feel the impact of new lighting and clouds, lost around 20 FPS both min and max with Vega 64. What I do know tho is that Vulkan if properly implemented will boost our frames much more than we lost now and there will even be room for much greater visual fidelity and will also help people with lower end CPUs due to reduced overhead. How I know that? GPU power draw is the key, currently my graphics card is using only 150 watts with 100% usage yet DX12 and Vulkan titles (even DX11) you can see that power draw go to 240W easily, that points out that DCS rendering engine is incapable of utilizing our GPUs fully, which is no news really it's old and in need of replacement and ED is working on it.

Exactly why I pointed you to official response on the matter that something isn't right with DCS and is reported as problem, team is working on fixing it, that is the point where this discussion should've ended. Nobody will fix nor investigate something that isn't broken I can assure you to that. Again I am not here to argue, I was never trying to insult you or be rude in the first place, if you felt like that I am truly sorry, I was just trying to point out that they are aware of the issue and that it isn't either driver or hardware issue since it happens on all possible configurations of hardware from different manufacturers (Intel, AMD, Nvidia)

Don't worry about harshness it's internet after all I have my own interpretation of course but you are quoted for a reason, everyone can read what you said and what I said and can figure out on their own what they think about it. It could be due to language barrier but this sentence sounds to me like you don't want hot fix, or any kind of fix for that matter, simply because you are "scared" it will break the game for you. Now my question is why would ED hot fix something that isn't broken in the first place? I am not here to argue I just found your post non productive to the discussion, like if it doesn't crash for you great but don't point fingers and wish to people to sort their systems out, surely he (OP) is a bit over dramatic it's still open beta and we are all testers here, guess he didn't pick that one up. And for a fact I know many other instances when game instabilities are due to very basic "slider overclocking" without any kind of system stability testing that many fall victim to and then fill forum threads about it. Long story short, I never had a single crash in 2.5.6 now they are happening and are inconsistent, something is broken and will eventually get fixed

I will tho my ping to the server is a bit on the higher side for my taste (135) I guess it will impact formation flying the most but we will see

Most aren't getting crashes doesn't mean that everything is ok. Especially when this, as it seems for now, probably has something to do with memory de/allocation That stance would get us nowhere... I can give you multiple explanations why some are getting crashes and others don't even tho their systems work correctly. There is definitely something broken and even BIGNEWY managed to get the same crash that some of us are experiencing from time to time. Currently my game won't crash at all, but then there are days where I can't load mission two consecutive times even after multiple launches of the game.

I just tried it out using two extreme values one is around 450m and other was 2940m there is definitely difference between the two presets regarding cloud position in 3D space. I reached first layer of the clouds in the first one at around 500m and around 2500m in the second case

Could be that it's WIP then, I changed slider few times in custom missions but didn't really measure/compare it with different setting

There is base layer slider under preset selector/picture, I guess it does just that EDIT: Also not every preset has the same height limits

One more thing that adds to confusion, as far as I know in the real aircraft there is no single button to change between nav, return and land everything is physical switch same goes for radar modes etc... We will have to wait for that full fidelity MiG-29 goodness but then again we will lose some other stuff with it that are currently oversimplified, for example RWR (SPO-15) shuts off when you get someone in STT lock, so you always have to keep in mind that missiles may already be launched at you

+1 I don't see why this shouldn't be feasible at some point

Long story short he is trying to tell you that human eye doesn't work quite like a camera. I am currently typing this under cloud shadow, it's day and I see everything it's not dark at all plenty of light is here but from above it would look much much darker due to exposure of the eye.

Well hopefully that fix for Vigen respawn, mission reload and track replay will fix everything else also, at least ED is looking into it...

It's not the page file. E_OUTOFMEMORY is usually associated with it but why am I so sure it isn't pagefile in this case, well because I saw first hand dxdiag of a member that has 64GB of RAM and the same amount of page file yet it crashes in the same manner for him too. Both CPU and GPU vendors can be affected... Intel, AMD and Nvidia so that is also out of the equation.

Probably no, I tried suggested stuff and much more but nothing seems to fix it permanently. I am currently out of ideas... Yesterday game didn't crash at all, I started game multiple times throughout the day, abused loading missions left and right and no crashes but 30mins ago it started crashing at loading again... two consecitive times in a row on second mission load. Crazy how inconsistent it is.

2.7.0.4625 Open Beta Su-27, MiG-29 HUD Filter doesn't render when rain droplets are rendered on the windshield or you are flying through rain clouds on "overcast with rain 1 and 2" cloud preset At the beginning of the track I put the hud filter down and it is not rendered for me, later after takeoff when I punch through clouds it will suddenly appear and after going down disappear again I am using AMD Vega 64 with 21.3.1 WHQL drivers It could be GPU vendor/ driver specific issue so here is the track and some pictures... HUDvisorvisualbug.trk

Majority of people that get crashes in this update aren't mid flight they are on loading screens, exiting the game etc. Of course first step when something starts misbehaving like this is to undo all overclocks and test for stability just to be sure, but it's not the case here, it seems that something is wrong on code level and if my suspicion is correct and it has to do with memory allocation that issue can manifest differently on every single configuration. Some PCs would seem unaffected because crash would happen once in 10000 times but others will experience it once in 5 times, that's why those type of things are hard to track without configuration that is having issues you can't use debuggers effectively to find broken line of code. I am also dealing with crashes and currently whatever I do I can't seem to make it crash, yet yesterday it was misbehaving all day. Hope it's not cosmic rays affecting my PC

Here you go a way to avoid hard rebooting when other windows don't render properly when it crashes

Yeah, I later found out that it affects every CPU/GPU combo AMD/Intel/Nvidia

Yes, but sadly it doesn't do it for me. I tried your alt+enter solution also. Even if I get some custom mission to consecutivly load, I just switch to another instant mission and then go back to the first one and it will crash at loading with the same errors.

Try to switch between different ones with different jets that almost always triggers it for me.

We all have exactly the same crashes that are happening at exactly the same conditions, this is just an example Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 2.7.0.4625 Application Timestamp: 6075e58f Fault Module Name: d3d11.dll Fault Module Version: 10.0.19041.746 Fault Module Timestamp: fc177b9d Exception Code: c0000005 Exception Offset: 00000000000a77a4 That points out that there is something broken in DCS.exe I am suspecting stale pointers at this point or some array issues in the main game code. For me it never crashed on the first load and that solidifies this theory for now.

I just found out that it's crashing for one member who has AMD 5600X and RX 6700 XT so that assumption goes out of the window... Basically it can affect every combination of CPU/GPU Intel/AMD/Nvidia as far as we know for now.... but many people don't have this issue at all and that is good for them but at the same time bad for us haha eh... we will figure it out

I see you got around to it, thanks for dxdiag you can always run dxdiag, you just need to type it into search and when it opens up click on save all information, but LShift+R in DCS will work too for now haha You are the first that posted dxdiag that is using newest AMD CPU so my assumption that it's only Intel 9th and 10th gen is incorrect afterall... You have 64GB of ram and hefty amount of page file so that is out of the question also, I am mind boggled how it isn't affecting everyone... Just flew in MiG-29S for an hour and I reloaded the mission and then flew another 20mins without issues. Very weird issue we got on our hands here...

So far all DxDiags that I've seen including mine are based on Intel 9th and 10th gen processors, that is the only thing our builds share at this point.