homepage Forums Air Combat & Civil Aviation SAM Simulator

Unsure, but I'd expect that the much higher accuracy of SARH would allow a guiding missile to pass very close to the target, while a missed turn or lost target would only allow a very narrow range of conditions before the fusing range was exceeded.

The fusing area is a conical section slightly ahead of the beam position to give target/warhead fragment collision on as many shots as possible (these fragment patterns tend to also be slightly ahead of the beam position, and to have a narrow angle of spread), and with a close pass the fusing range will tend to very low values.

Pictures just super !

I really liked on !

Thank you again Hpasp!

max2012, you love Pics ?
these Pics are for you!

the fist and second - no comment - all know what is it !



artistic angle!

artistic angle!

Could you send me more about the third type?
(Not so artistic?)

This still doesn't justify the fact that with the SA-5 you either hit the target at very close ranges (so far the highest detonation range that I experienced was 18 meters) OR you completly miss the target - there's NO "middle term" like a 50 or 100 meter (or even longer) detonation like happens with the other SAM systems (SA-2 and SA-3 for example) and this happens either when firing against a SR-71 or against target drones in the firing range (and both with or without jamming).
I would expect that at least when shooting drones in the firing range that some longer distance detonations (again with values like 50 to 100 meters or even more) would be experienced but I haven't experienced NONE and believe me I've been shooting a lot with the SA-5 latelly (specially in the firing range).

I checked the code, and the Vega part still has the 300m sensitivity. (bit too much)
Did you receive KRO signals during missile flight?
If the set range is far from the real target range, the missile engine program might cause the missile to burn.
Also, as the missile decelerate during unpowered glide, the chance to hit anything is reduced.

I think your missiles that not scored, avoided the target by far margin.

Hpasp, can you explain more deeply, how do radio fuses work? If one has a, say, 300 m sensitivity, and missile explodes at, say, 15 m, why it did not earlier? Of course, if the target is still closing, the fuse should wait, since delay raises chance for kill. So, when the fuse makes warhead explode? (I would suspect that when target distance starts to grow again, which means that minimum distance has JUST been reached, or reflected signal has reached some particular strength, which means that the distance is sufficiently small).

This one with artistic angle - a S-300 P/PM? More of that please!

The fuse detects targets to the side of the missile, not directly ahead - the sensitive area is essentially between two (conical) surfaces near to and slightly ahead of the missile beam area.

With sloppy guidance this allows the whole fuse sensitivity to be used on a regular basis (once the missile is at the correct relative range from the launcher, the lateral offset may approach the fuse sensitivity limit), with tighter guidance of at short ranges the correct relative range will occur with either a direct hit or a very close miss.

Photos are very good

I really liked

The question of where they filmed the Volkhov, the Neva .

What is your opinion about a 3D After Action Report using Google Earth?

After a mission, you could save a file...

http://www.mediafire.com/file/ege4q3oaivahaag/Asuluk.gpx

... drop it into Google Earth.
Uncheck "Adjust altitudes to ground height"



Pull the time slider to leftmost.
Click on play.



Please share your view...

Very nice and useful feature - full support! I wonder if this could be supplemented by 3d (toroidal) projection of fire zone (launch envelope + kill envelope) of given system, similar to this one:



This would enable us to evaluate what was relative position of impact point versus missile range (kill zone) -

If you switch the leftmost one, the angle tracking control is given to the two optical angle tracker officer, sitting at the top of the SNR, in the "doghouse".
[not simulated]

Middle one is the jamming target identification switch.
(if you have more than one jammer strobe in the screen, you can highlight it at the other display)
[not simulated]

Easy and clear! Like it!

I already knew the switch on the left "Vizir" is a dog house!

Doghouse and there is optical channel viewing purposes!

I realized everything is!

Good idea, but how bad would the slow down be if you wrote data out more frequently - the elevation profile is potentially useful and interesting, but currently shows very coarse steps because of the widely spaced discrete intervals and lack of smarts in GE.

As I understand there is shown the affected area SAM KRUG.

As I understand it should be left to -10 km, -20km-, -30km affected area in a DOGON!

As I understand minimum target height of 150 meters (0,15)

Maximum distance of 50 km.

Target height is 24.5 km in the boost phase missile.

On the passive can be all of 26 km.

In the DOGON worse as always!

Good idea, but how bad would the slow down be if you wrote data out more frequently - the elevation profile is potentially useful and interesting, but currently shows very coarse steps because of the widely spaced discrete intervals and lack of smarts in GE.

At the current test, it is one coordinate per 10 second, for each flying object.
I can change it to one coordinate per each second, to have more granularity, and nicer missile path...

http://www.mediafire.com/file/54rzne02fi6e3un/Asuluk2.gpx

Just do not forget to click on settings...



... and pull the "animation speed" to the leftmost.

More detail in the missile path. Some spiking from the velocity profile, unsure if this is data provided by you or computed by GE.

Launcher Height is given as 5m, with the terrain set at -19m. Is this correct? It is possible that the launcher is on an elevated platform, but 24m seems a large value for the missile height above 'flat' ground around, given that most seem to be in revetments in their 'war' positions.

I think that a better solution could be found or built for the purpose later, particularly with navigating and viewing the data (GE is clumsy for working with these tracks, as it can only display one at a time and navigation of the 3d world is not as convenient as some games have managed. - I recall the Falcon ICMI being quite flexible, with view points pinnable to a single unit, padlocked to another, or free flying/steerable... Still hugely better than nothing, and would be really useful with a 'parameter/range' model for the missile overlaid for the currently selected missile, if that was possible...

Launcher Height is given as 5m, with the terrain set at -19m. Is this correct? It is possible that the launcher is on an elevated platform, but 24m seems a large value for the missile height above 'flat' ground around, given that most seem to be in revetments in their 'war' positions.

No.

The program calculates the steps in 100ms.
What you see is the first round second (missile could theoretically fly for 100~900ms) before the first point.

(GE is clumsy for working with these tracks, as it can only display one at a time

No.

It can display more than one.

Unclear of me... only query/display the velocity/height profile for one at a time, both are displayed as paths in the 3d world - and there are tools that allow the time history to be interpreted - each node of the track can be marked, the 'length' of the displayed portion of the track can be shortened by dragging the partial 'left bracket' on the playback track, and the 'current' point of the velocity/height profile will display as a red arrow with it's associated parameters displayed.

The first data point was (IIRC) listed as 20.1 m/hour, so ~20+m height gain seems improbable? I'll check it again later, but this was my initial impression - the velocity was negligible, but the position seemed 'out'.