SAM Markpoints at SA page

Matt, can u comment this, pls. :noexpression:

A new datalink / SA page element was added today to support for SAM threat zones. These are determined before hand and are static indications based on Mission Editor settings. If the unit is hidden it will not appear on the SA display, if it is not hidden, it will display. Just like the real system, this is NOT a dynamic indication based on RWR or any sensors. It simply alerts the pilot of a reported SAM threat that was entered in the mission file before they even took off.

Is it just ABRIS way and EVERY not hidden SAM will be mark at this mode and we don't able to choose what unit (group) will be marked manually without hiding it?

Maybe u can make some alt way? Like just preset some reference points at editor. Like A-10C reference points tool? Or setup F10 Map Marks with special text. It will be more flexiable for mission designers.

And other question: are there some limitation at aircraft NAV database? and if I understood right, this marks are just different type of way / mark points in common nav database, right? So what's maximum amount for this?

P.S: For example auto detection of threats at Ka-50 is still problem in multiplayer, because u can't make some ambush or set mobile SAMs in safety. (usually don't use hide function because most scripts and commanders can't interact with hidden units :( ) At Hornet it will be some catastrophe, because this craft can easy detect and kill any hidden (at terrain) units with different weapons. So, please, can u think about making this like option? Manual Marks (F10 and ME) or even just unit flag like "non detect for hostiles"

Thank you.

Air defence threat rings are only loaded onto the aircraft from the data cartridge before flight, nothing is automated about it. You can only place threat rings on known or suspected locations of air defence systems.

The threat circle may require pre-target loading, but for terrestrial SAM traces, it can be transmitted via link16 J3.5. For example, the F-16 has this situation. (F-16 MLU "Link 16 and IDM SEAD Threats")

What he is trying to say is that, in the Ka-50, every time you respawn in a new chopper, your ABRIS is populates with the locations of all the enemy ground forces. It is pretty much like a wallhack.

Let's be honest, DCS, especially in MP and its ground forces are not dynamic. So when someone places down a MANPAD or a mobile SAM and the choppers respawns, the chopper already knows those locations, no matter that no one has seen those units or knows their exact location.

You can imagine how much more devastating that can be in a multi-role jet, although just for SAMs.

If a system can be developed for reporting units somehow and then on spawn aircraft take that data for their maps it can be a lot better. This will also be opportunity for scouting roles in DCS and aircraft which gather data.

You can hide units on the mission editor that will not be visible in the Abriss

You can hide units on the mission editor that will not be visible in the Abriss

And for other side commander too... + for example MOOSE scripts cann’t operate with hidden units, it is problem for multiplayer.

What he is trying to say is that, in the Ka-50, every time you respawn in a new chopper, your ABRIS is populates with the locations of all the enemy ground forces. It is pretty much like a wallhack.

 

Let's be honest, DCS, especially in MP and its ground forces are not dynamic. So when someone places down a MANPAD or a mobile SAM and the choppers respawns, the chopper already knows those locations, no matter that no one has seen those units or knows their exact location.

 

You can imagine how much more devastating that can be in a multi-role jet, although just for SAMs.

 

If a system can be developed for reporting units somehow and then on spawn aircraft take that data for their maps it can be a lot better. This will also be opportunity for scouting roles in DCS and aircraft which gather data.

Thank u, bro! :thumbup:

Let's be honest, DCS, especially in MP and its ground forces are not dynamic.

You're obviously not playing on the right servers - they're very dynamic on the DDCS servers, players can spawn new SAMs and move them around, including taking direct control if the model supports it (like the SA-15).

You're obviously not playing on the right servers - they're very dynamic on the DDCS servers, players can spawn new SAMs and move them around, including taking direct control if the model supports it (like the SA-15).

Didn’t play on DDCS for a long time, but I remember rules there.

For example, u want to cover your fighters and set some SAM point in 20-30 km from farp (or if u can’t... near the farp in forest) for example 2 x SA-15. Turn off their radar and just wait, when your fighters need help in defensive, and u will tell them go to this point.... so

If this system will be released like in Ka-50.... just after spawn... F/A-18C will get actual info about EVERY sam on the map (even SA-15 with turned off radar). And u know.... i think u can choose this markpoint like target, and it will be JUST at your Tor... lol... Ka-50 has 100 percents of accuracy, why not here... but Ka-50 don’t have capability fly on 40k feets with TGP and GBU-38 :D

Seriosly, way with map marking is more realistic... Commander or other pilot marks point on map with title of thread.

Suggestion:

If player detect some sam position, he can calculate this at F10 map and then mark it. Same for Commander, but he has additional capabilities, because can see data from AI planes or ground troops.

Selecting every mark with preset titles + toLowerCase() (sa-15, sa-2 and others) Then any F/A-18C at this coalition will get this data in next spawn.

In improved variant can be additional marks for this task. Where player can choose preset sam variants in some list. This will give more reliability. + this marks can be with thread zone indication on F10 map (like at SA page).

If mission designer want to preset some points in editor, can set points (which used for A-10C or make new type)

Yeah I can see how the Hidden/Non-Hidden thing for threat rings might be an issue online. Possibly a different way would be better, as suggested.

So... nobody wants to honest system realisation.... so... ok, why not

elaborate more on what you even mean redshirted shrug man

elaborate more on what you even mean redshirted shrug man

¯ \ _ (ツ) _ / ¯

bigger problem....if you have an Airfield defended by 2 SA8, 1 SA2 and 1 SA3.... it will clutter up the SA page like nobodys buisness on multiplay servers like BlueFlag

what is really needed is an actual 2d planning layer, so that you can actually plan missions. then this would be a moot point as you would have total control over which markpoints / steerpoints / threat steerpoints you would have on any given flight.