okopanja

the former is gap filler radar, not a SAM, the later is simply short range sam.

P-12 and P-18 can be and were used with SA-3 as well. As for P-14 was used in 1999 and damaged in the first attack wave near Pancevo by means of cruise missiles. While great range, it is poor when it comes to moving, it's most critical fault. No causalities since it was willingly sacrificed. In following days the repeated attacks saw a definite end to it.

@tavarish palkovnik

This is all fine, but it still sounds like a table based approach, employed by FC3, and we should nit ecourage that with FF. Btw the range you gave hornet exceeds the range f15c(better radar) detected mig-29(higher RCS) in 1999. So yes there are huge variations in practical range compared to what you get in ideal case. Furthermore this will still be changed in future.

Idea: how about doing a calculation based on ED's white paper? Also if I recall correctly phase 3 rework is not yet completed, so probably bug report should be checked afterwards.

@Flappie I gather you manage to reproduce now with some effort, but see screenshots from Tor SAM i spawned which apparently was the source of the broken texture. I believe there was a similar reported problem with one of the desert textures for KUB or Tor.

I observed long range shot in MP, where the Tor was folded and Harm still hit it. In addition I have also seen a long range HARM hit exact point where Tor was 30 seconds earlier hit.

I just spawned into TOR which appears to be source of the texture bug. I could move the head and see that the source is where I stand. I could see it from first person view, but not outside. null null Just got killed before I could make more screenshots. Please check the desert texture of Tor, there is already a bug report for that!

Just had the texture, was flying Ka-50 and it showed. My PC is freshly installed Win11 and freshly installed.

Will try. I am mostly on contention and a day or two ago, one person complained in the chat on Syria map.

Interesting... I can not replicate it anymore. Part of the problem is that I switched to Windows 11 and got everything reinstalled. Still have an old NVME with Win10, so I might boot it and check that as well.

I limited the choice of modules to the one I have. At the moment I have very little extra time, so I do not go into new modules. I will do some feasibility checks and estimate the effort based on Kiowa manual and what sort of way-points it supports. If you are familiar with lua, contributions are welcome.

This dude drove both Trabant and Zastava: Also where the bicycles all baby-blue in DDR?

A air bases in Czech Republic/Poland planned at all?

Most of the modules have at least one type of navigation means. Even in cold war most of them can use some sort of radio beacons. The most simple navigation aid kind is by using a compas and dead reckoning. E.g. you can set even the indicator on some of devices pointing at azimuth you need. E.g. Mi-8 has this and it is trivial tu use. F10 in main window is very unlikely to be implemented.

So the missiles stopped tracking, despite holding lock all the time? Adding your tacviews... Tacview-20250312-194705-DCS-nerfed_r27.trk.zip.acmi Tacview-20250312-194217-DCS-nerfed_r27_mig29.trk.zip.acmi

Please explain but calmly, what is wrong and since when

All I can tell you is that it is related to: - Large servers (contention) - Normally I do use only 2 mods: Clickable FC3 (I can disable this, and based on the code it only activates for certain aircrafts) and my own mod (which is essentially an export script for entering nav points SharkPlanner ). I can disable both and let you know, but I am almost certain these are not the root cause. - it happens in places where CA unit was destroyed (might happen also with flying units) - its more likely to be reproduced with helicopter (I fly gazelle often, but I have seen it in Mi-8), but e.g. can happen even with low flying FC3 flanker. - Even though the texture looks like it stretches to infinity or is displayed a large flat explosion, as soon as you move the affected point from your FOV, the whole thing will disappear. Similarly, you move FOV back and its there again. I suspect that this is caused one of the objects which models the debris, which for some reason may have a broken geometry or incorrectly applied texture. It may be that the object is not removed from the scene for some reason. - Orientation is usually horizontal or vertical, but I have seen angled. When the thing started happeing back few months ago it was usually vertical and with finite 2D dimensions, but now it displays to infinity. - Also the texture is one sided, if you pass to the "other" side everything will look normal even if you look to the object that is causing this. - I think the only difference between crater and the monolith appearance is how the texture itself got applied (colors of both kind of match).

I saw it last week. If I remember correctly last updated was only about mission content, so the issue is still live and kicking.

https://tekcreations.slab.com/public/posts/dcsbios-installation-skunkworks-byjgzhpu

Its just my joke on practice to display new weapons in soviet times. Nothing really solid on release day.

If we are talking about licensing you can have least restrictive contracts where you as a company license and pay for fixed period. E.g. 1 year. When renewal is due, vendor may ask for more, e.g. by quoting inflation or other difficties which increase their costs. You can also license for multiple years with full upfront or periodic down payments (e.g. every year). Here vendor defines minimal duration after you can cancel. All has pros and cons. Lets hope this is just about money and not something more difficult.

Actually ot looks like there is actually a bug here but in opposite direction. It appears that the missile can get close to 40-60m to the aircraft, explode and not kill the target.

It's nowhere stated, so lets wait and see...

May 9th is the date.