XPACT

Biggest problem here is not the crashes, current problem is that developers and even closed beta testers can't recreate these from 14th April, this is to say the least a bit worrying. There is no fix in the progress since they can't recreate crashes and I don't see that changing anytime soon to be honest. Good thing is that we have some bandaging solutions like deleting FXO to keep us going...

That's what I am thinking about, I think we are only getting "dumb" hey missile is coming at you warning and its direction with warning sound. There will be no automatic action taken or suggestion given on how to defeat the threat which full President-S suite would do. So this new MWS will probably be on/off type of thing so there won't be need for fancy options and settings.

On AMD side it doesn't make a difference Vsync on/off, FreeSync on/off, Radeon control panel settings default or not I am currently running windowed with vsync enabled @144Hz and I am again in a phase where game won't crash whatever I do but it will return at some point, that is obvious now.

I think it won't be integrated into ABRIS, but ABRIS display will be used for it, since new switch is right next to ABRIS display common sense tells me that behind there is probably simple video signal switcher, two inputs one output, that will switch MWS video output to ABRIS display when threat is detected, when there is no threat you are switched back to ABRIS automatically, now of course if something bugs out you always have that manual switch to show only ABRIS video out on the display. That would be most realistic way to implement it.

That didn't age well... He is still having crashes. Major system changes like driver updates, changing page file, updating windows seem to flip the coin but so far it seems that if you had crashes before they will come back at some point.

You are using steam version, there is no DCS_updater.exe

Guess what we need is "clear FXO folder at mission end/quit to desktop" checkbox in options Just to keep frustration at the minimum until proper solution is found.

I don't like to be party breaker but if you already encountered d3d11.dll or dx11backend.dll errors there is massive chance that they will return at some point. All fixes so far seem like placebo. I had my fair share of no crashes (5 days of heavy use) but now they returned at almost every second mission load.

I agree with that, it's after all a game and some like the idea of doing stuff that wasn't possible at the time or even carry stuff that wasn't possible. I am not against it if that is the way you want to play, I couldn't care less about something I won't encounter in my gameplay. I am just telling if that is the case where development of modules is going we need additional tools to easily filter out what we don't want in our missions. I am sure there is plenty of us who want fully realistic timeline and also only what was really utilized IRL loadouts wise in those modules that we intend to fly or fly against

Of course date/time based weapons should be a thing that's great from mission creator point of view. What I am saying if something isn't wired in simulated version/model of aircraft you shouldn't be able to use the weapon in DCS also, carry it yes, jettison yeah but use it like a weapon big no. You can also find images with MiG-29s carrying four R-27Rs but ones on the outer pylons can't be fired, everyone knows that. If DCS wants to be another arcade type game sure go that way but if they actually want to keep some standard and stand by the words how the product is described decisions like that should be revised.

Hope that those who have problem with three pylons on Ka-50 also didn't support quad mavericks on F-16 or other fantasy loadouts that are sadly beginning to be a standard around here. Basically recipe for fantasy loadout: just cry on the forums out loud, show some testing photos when weapons were carried for aerodynamic and maneuverability evaluation but they were never fired or even wired for. I am just asking for same standards everywhere, I think we are at the point in time where we need "Allow only realistic loadouts" in the mission editor.

Yeah own SAMs shooting at him is possibility it did happen before, also confirmed with one MiG-29 that was taken down by air defense while he was about to land at Nis airport... Communication was very troublesome it seems and airforce was deployed in chaotic manner without good intel Now there were many fake targets appearing due to EW usage, other pilot in the documentary talked about it, don't think that was the case here because 3 of them first going very fast hot then something shot at him and then they were cold running away and at last that split near border seems like to much

First time he was at lower altitude, after first evasion he ended up at 8000m, at the point he found them with his radar he was at 6000m and they were showing on heading between 130-140 (with that info I can try to find their actual position), on last evasion I don't know where he ended up but I guess low again, he sadly didn't say their altitude and speed when he first managed to STT closest one but I guess they were at least co altitude or higher but he did say distance and it was 35km. He also said they were going very fast towards each other and that he flipped/switched something on the stick to get ready for missile launch, don't know how to exactly translate that part in English.

Thank you well first thing I would do if I had another decently sized SSD would be to reinstall Windows, install every driver and DCS only. If it doesn't crash after 3-5 days of usage than I will also join the hunt with trying to pinpoint exact conflicting software, on the other hand if it still happens then pulling out memory sticks, putting them in single channel only etc I would focus on memory configuration first

I think I can actually, even hour. Hmm, he very clearly said that it was beeping (in his helmet) and flashing on panel and then explained what that means by saying that missile was at that point already launched at him and that he has very low amount of time to do something about it. Btw here are all MiG-29s at that time in Yugoslav Army Airforce inventory with their serials and dates of manufacture 18101 manufactured 29.11.1987 (serial number 3402), 18102 manufactured 24.11.1987 (3403), 18103 manufactured 28.11.1987 (3404), 18104 manufactured 04.12.1987 (3405), 18105 manufactured 05.12.1987 (3406), 18106 manufactured 07.12.1987 (3407), 18107 manufactured 08.12.1987 (3408), 18108 manufactured 07.12.1987 (3409), 18109 manufactured 11.12.1987 (3410), 18110 manufactured 14.12.1987 (3411), 18111 manufactured 10.03.1988 (3510), 18112 manufactured 11.03.1988 (3511), 18113 manufactured 16.03.1988. (3512) and 18114 manufactured 18.03.1988 (3513). Doubleseater 18301 manufactured je 13.08.1987. dok je 18302 manufactured 01.09.1987. Last four single seaters were from different "batch" EDIT: @GGTharos That flight happened at DD/MM/YYYY 07/04/1999 at around 23:00 local time

By going so up to date my game is now crashing again... Now I am at point where I can't believe that nobody managed to reproduce it, your testers should try fiddling with drivers, pulling memory sticks out, changing pagefile size, at some point since this is obviously memory related it will happen to someone.

If you are talking about NATO campaign against Yugoslavia in 1999, yes almost all of the MiG-29s had some kind of failure in flight usually radar or rwr (radar wouldn't be of much use anyway) they were all hoping to get close enough for WVR and use R-73s, equipment was working on paper but in combat conditions proved to be unreliable. Now all those jets were to be, I don't know the right word for it, refurbished and modernized in 1996 but due to no funding because of sanctions and what not that was skipped. I must re watch the documentary but there was one pilot which had everything working. I will actually try to transcript his whole flight once. Long story short first time when he didn't have any info on the enemy at one point RWR was immediately in beeping and flashing mode signalizing missile launch he started doing avoidance maneuvers with high G turns left and right while climbing up since he was pretty low when that happened, missile/s missed I guess AIM 120C?, and after RWR stopped beeping and flashing he started "free hunt" since ground wasn't responding to his calls, spotted 3 targets on HUD and locked closest one in STT successfully, (now at some point he mentions it that while you have STT lock on someone RWR is not operational, the way he said it doesn't conclude if whole RWR doesn't work or just missile launch warning), now he knew their altitude and speed but at distance of around 30km his radar drops from STT, immediately continuous beep was heard form RWR and then shortly after flashing and beeping again, he evaded those also and when he turned back to previous bearing they were now going cold (3 targets on his HUD) so he put radar in D (dagon) and started chasing after but at some point close to Bulgarian border they split up, two went left and right and remaining one continued at same course that was the point he decided to RTB, that was longest flight and it lasted 40mins From his story I am led to believe that SPO-15 managed to pick up those missile launches Anyways documentary seems very good and most importantly there is no biased BS that I could detect khmm (like in many western reconstructions of various events)

As I understand there were revisions of SPO-15, as far as we know he might be talking about earlier version

They say curiosity killed the cat... well... I updated my drivers (AMD card) to the latest 21.4.1 and guess what, crashing is back hahaha I had 5 days without single one since I changed page file to fixed 32768MB yet I am now at square one again because I like to fiddle with things that "work" I am pretty sure that rolling back won't bring me to previous state of no crashes

Are your terrain shadows set to flat by any chance? I noticed they don't quite work as expected in 2.7 at least for me That's probably this and seems like another issue

60degC is not hot for GPUs nor any semiconductor and conductor in general one thing tho, it depends where the temperature is read, for example you could have 60degC core but 100degC hotspot somewhere on the GPU at the same time which could cause problems in some architectures. Usual artifacting culprit is video memory either it is running too hot or more likely speed for those timings is set too high. Overall I wouldn't be so concerned about those since a lot of users are experiencing some kind of artifacting with 2.7, especially on AMD side.

SPO 15 is not simulated correctly in FC3, IRL you can know exact model of aircraft that is illuminating you based on lights that light up on the bottom it is even programmable

More that I think about it, it may be working as I said haha because in STT all four antennas will end up illuminated since signal level will be too strong em waves would inevitably bounce all around the jet, accuracy will be lost and every antenna will detect it and since there is no advanced processing circuit to determine timings that I know of I think everything would light up haha that is 60s for you but I will try to find some documentation and report back SPO 15 is like alien ship to SPO 10

You should be right on this one, my mistake. And yes every radar in DCS has same characteristics that's a problem since SPO 10 tone pitch relies on that so you could in theory tell even exactly what radar model it is. Also there is modern stuff SPO 10 couldn't even detect since it would be out of its frequency range. All these are not simulated in DCS DCS generally needs radar tech rework on a massive scale...

Seems like nobody wants to answer your question. Yes SPO-10 is somewhat primitive here is what it can do, I still think it's fine. It doesn't tell friendly from foe, lights blink (there is 4 lights but for example 2 can be lit simultaneously if that radiation source is in between two quadrants) and sound is heard when radar em wave hits your aircraft, by hearing amount of pulses and their length you can judge how many of them are and what type of radar it is airborn/ground etc It will show STT lock by turning all four light signalization with a constant beep, but it cannot detect moment and if something is launched at you