homepage

Re: Bug reports

Posted By: P47Thunderbolt

Re: Bug reports - 08/01/12 02:37 AM

Hi Hpasp,

I encountered this “bug” today using the SA-4 in El Dorado Canyon. The invulnerable mode apparently does not work correctly for SA-4. Kept the SNR active and eventually a single HARM quickly ended the simulation.
Posted By: Lonewolf357

Re: Bug reports - 08/09/12 12:36 PM

I think I found a few bugs.

First, when I try to open a 3DAAR in Google Earth, it shows me this:



This happens only with these new Serbian missions.

Another is an old one, that I mentioned a long time ago and that appears to happen only with me: with S-125 system, the first salvo of 2 missiles always fires OK, but during subsequent shots, either one, or both missiles are often lost. You hear the sound of them starting, then a tiny mark appears at the very base at SNR screen and quickly disappears...


...And nothing. They simply do not appear. About 25 to 50% of missiles are lost that way.

There is also a few questions. First, how many IRZ devices does each S-125 battery has? And, if I select the "non-historical" mode and use, say, S-75, will the IRZ be available in this case? It doesn't look like they are available... nope

And another one: When I'm using the S-75, the RPK light turns on when I select the 75 km mode, and keeps illuminating even if main transmitter is off:

And it looks like it actually transmitting, even when switched to EKV, because HARMs keep coming... nope
Posted By: Alien_MasterMynd

Re: Bug reports - 08/09/12 01:46 PM

Regarding Volkhov, I think it is standard behavior when you are in 75km AND BR mode.
Posted By: piston79

Re: Bug reports - 08/09/12 01:56 PM

Originally Posted By: Alien_MasterMynd
Regarding Volkhov, I think it is standard behavior when you are in 75km AND BR mode.


Yes, it is, but it shouldn't transmit when ANT/EKV is in EKV...

EDIT: In the manual of the S-75M is written that the green lamp is lit only when transmitting true antena.
http://www.mediafire.com/download.php?1pqacrwgddpkd5p
I believe it's an old issue in the SIM... frown

Here, Vintorez extended manual:

Quote:
4 – RPK (Radio transmiter for missile commands)
Battle value: Two positions – left: „Dummy load”; Right „Antenna”. It is used to transmit fake launch signals to enemy formations, forcing them to break the battle formation and drop it’s loads.The RPK system is continuously calculating and creating the missile guidance commands, even when they are not launched.Those signals could be sent to the dummy load, or emitted by the P16 antenna.
With this switch, you can select between dummy load (EKV) or the P16 (ANT).When missile is launched, this switch is overruled and the commands are emitted via the P16. If the P16 is selected (manually or automatically), it is indicated by the green lamp.At the Volkhov, if the system is in BR and 75 km mode, the RPK signals are automatically sent to the P16 to frighten the enemy. In all other modes, you may use it manually at will.
RPK - EKV/ANT switch should not be used in real combat, as the BR/75 km mode has the same effect.


Not sure, but it looks sealed here...
Click to reveal..

Posted By: Hpasp

Re: Bug reports - 08/09/12 05:43 PM

Originally Posted By: Lonewolf357

And another one: When I'm using the S-75, the RPK light turns on when I select the 75 km mode, and keeps illuminating even if main transmitter is off:
Click to reveal..

And it looks like it actually transmitting, even when switched to EKV, because HARMs keep coming... nope


When you are in 75km and BR, the Volhov starts sending fake launching signals automatically.

The EKV/ANT switch is used only during maintenance.
Its default setting is EKV (used to be sealed).

System is automatically overriding it, and its override is shown by the RPK green lamp.

Originally Posted By: Lonewolf357

There is also a few questions. First, how many IRZ devices does each S-125 battery has? And, if I select the "non-historical" mode and use, say, S-75, will the IRZ be available in this case? It doesn't look like they are available... nope


There should be, just do not forget to switch off SNR in time, to let the IRZ lure it away.
Posted By: Lonewolf357

Re: Bug reports - 08/09/12 05:52 PM

Originally Posted By: Hpasp
Originally Posted By: Lonewolf357

And another one: When I'm using the S-75, the RPK light turns on when I select the 75 km mode, and keeps illuminating even if main transmitter is off:
Click to reveal..

And it looks like it actually transmitting, even when switched to EKV, because HARMs keep coming... nope


When you are in 75km and BR, the Volhov starts sending fake launching signals automatically.

The EKV/ANT switch is used only during maintenance.
Its default setting is EKV (used to be sealed).

System is automatically overriding it, and its override is shown by the RPK green lamp.

Originally Posted By: Lonewolf357

There is also a few questions. First, how many IRZ devices does each S-125 battery has? And, if I select the "non-historical" mode and use, say, S-75, will the IRZ be available in this case? It doesn't look like they are available... nope


There should be, just do not forget to switch off SNR in time, to let the IRZ lure it away.


OK, now I see why IRZ didn't help me a bit when I'm using Volhov. It looks like the only way to get rid of that problem is to use the 150 km mode... Thanks for clarification, because those HARMs comin' out of vacuum and hitting my supposedly silent SNR in both Libya and Serbia have really annoyed me a lot... I really thought its a bug.
Posted By: Hpasp

Re: Bug reports - 08/09/12 05:59 PM

Originally Posted By: Lonewolf357


Another is an old one, that I mentioned a long time ago and that appears to happen only with me: with S-125 system, the first salvo of 2 missiles always fires OK, but during subsequent shots, either one, or both missiles are often lost. You hear the sound of them starting, then a tiny mark appears at the very base at SNR screen and quickly disappears...
Click to reveal..


...And nothing. They simply do not appear. About 25 to 50% of missiles are lost that way.


I massacred 5 LA-17M (A4) in Asuluk, and every missile was guiding.

Click to reveal..

Asuluk training ground.

Practice target:
LA-17M [program-1] simulating A-4 Skyhawk
LA-17M [program-1] simulating A-4 Skyhawk
LA-17M [program-1] simulating A-4 Skyhawk
LA-17M [program-1] simulating A-4 Skyhawk
LA-17M [program-1] simulating A-4 Skyhawk

S-125M1 Neva


00:00, Practice target LA-17M [program-1] simulating A-4 Skyhawk launched

01:00, Practice target LA-17M [program-1] simulating A-4 Skyhawk launched

02:00, Practice target LA-17M [program-1] simulating A-4 Skyhawk launched

00:02:40, V601P 5V27U Missile launched on Channel-1
Target distance: 23km
Target azimuth: 78°
Target elevation: 1°
Target altitude: 768m
Missile guidance method: PS (Lead)


00:02:45, V601P 5V27U Missile launched on Channel-2
Target distance: 22km
Target azimuth: 79°
Target elevation: 1°
Target altitude: 768m
Missile guidance method: PS (Lead)


03:00, Practice target LA-17M [program-1] simulating A-4 Skyhawk launched

00:03:04, Missile exploded on Channel-1
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 3m)

00:03:08, Missile exploded on Channel-2
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 105m)

00:03:34, V601P 5V27U Missile launched on Channel-1
Target distance: 24km
Target azimuth: 61°
Target elevation: 2°
Target altitude: 978m
Missile guidance method: PS (Lead)


00:03:40, V601P 5V27U Missile launched on Channel-2
Target distance: 22km
Target azimuth: 62°
Target elevation: 2°
Target altitude: 978m
Missile guidance method: PS (Lead)


00:03:59, Missile exploded on Channel-1
Practice target LA-17M [program-1] simulating A-4 Skyhawk hit by SAM. (miss distance: 101m)

04:00, Practice target LA-17M [program-1] simulating A-4 Skyhawk launched

00:04:03, Missile exploded on Channel-2
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 111m)

00:04:46, V601P 5V27U Missile launched on Channel-1
Target distance: 22km
Target azimuth: 75°
Target elevation: 1°
Target altitude: 787m
Missile guidance method: PS (Lead)


00:04:52, V601P 5V27U Missile launched on Channel-2
Target distance: 21km
Target azimuth: 73°
Target elevation: 2°
Target altitude: 787m
Missile guidance method: PS (Lead)


00:05:11, Missile exploded on Channel-1
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 14m)

00:05:16, Missile exploded on Channel-2
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 13m)

00:05:37, V601P 5V27U Missile launched on Channel-1
Target distance: 24km
Target azimuth: 71°
Target elevation: 2°
Target altitude: 1,1km
Missile guidance method: PS (Lead)


00:05:43, V601P 5V27U Missile launched on Channel-2
Target distance: 22km
Target azimuth: 72°
Target elevation: 2°
Target altitude: 1,1km
Missile guidance method: PS (Lead)


00:06:02, Missile exploded on Channel-1
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 6m)

00:06:06, Missile exploded on Channel-2
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 6m)

00:06:55, V601P 5V27U Missile launched on Channel-1
Target distance: 23km
Target azimuth: 74°
Target elevation: 1°
Target altitude: 559m
Missile guidance method: PS (Lead)


00:07:00, V601P 5V27U Missile launched on Channel-2
Target distance: 22km
Target azimuth: 72°
Target elevation: 1°
Target altitude: 584m
Missile guidance method: PS (Lead)


00:07:20, Missile exploded on Channel-1
Practice target LA-17M [program-1] simulating A-4 Skyhawk hit by SAM. (miss distance: 107m)

00:07:24, Missile exploded on Channel-2
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 49m)

Total, SNR On Air Time: 6min 18sec



Just rename it to gpx...
Posted By: piston79

Re: Bug reports - 08/09/12 06:12 PM

Originally Posted By: Lonewolf357
It looks like the only way to get rid of that problem is to use the 150 km mode...

Or 35 km mode... thumbsup
Posted By: Lonewolf357

Re: Bug reports - 08/09/12 06:57 PM

Originally Posted By: Hpasp

I massacred 5 LA-17M (A4) in Asuluk, and every missile was guiding.

I tried installing SAM Sim on two different computers, with different OS's, but the problem is always there... It is a real mystery... Probably Neva avenges me for my love of Volhov smile . Will try a third computer tomorrow...

Quote:


Just rename it to gpx...

???
Is this a 3DAAR? Server says that file does not exist... Never mind though...
Posted By: Alien_MasterMynd

Re: Bug reports - 08/10/12 06:22 AM

Originally Posted By: piston79

Here, Vintorez extended manual:

Quote:
4 – RPK (Radio transmiter for missile commands)
Battle value: Two positions – left: „Dummy load”; Right „Antenna”. It is used to transmit fake launch signals to enemy formations, forcing them to break the battle formation and drop it’s loads.The RPK system is continuously calculating and creating the missile guidance commands, even when they are not launched.Those signals could be sent to the dummy load, or emitted by the P16 antenna.
With this switch, you can select between dummy load (EKV) or the P16 (ANT).When missile is launched, this switch is overruled and the commands are emitted via the P16. If the P16 is selected (manually or automatically), it is indicated by the green lamp.At the Volkhov, if the system is in BR and 75 km mode, the RPK signals are automatically sent to the P16 to frighten the enemy. In all other modes, you may use it manually at will.
RPK - EKV/ANT switch should not be used in real combat, as the BR/75 km mode has the same effect.



You have answered yourself thumbsup
At the Volkhov, if the system is in BR and 75 km mode, the RPK signals are automatically sent to the P16 to frighten the enemy. In all other modes, you may use it manually at will.
Posted By: Vympel

Re: Bug reports - 08/10/12 02:44 PM

I think I found a bug. In new Allied force scenario May 2. No matter which site i choose my SNR always gets hit by LGB, and always by the same plane and at the same time.
Here is one of the AARs:
Click to reveal..

02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV

S-125M1 Neva

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, wth LGB.
00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.



And at that time the Hammer-34 is not over the site, I checked in 3DAAR.
Posted By: Hpasp

Re: Bug reports - 08/10/12 03:09 PM

Originally Posted By: Vympel
I think I found a bug. In new Allied force scenario May 2. No matter which site i choose my SNR always gets hit by LGB, and always by the same plane and at the same time.
Here is one of the AARs:
Click to reveal..

02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV

S-125M1 Neva

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, wth LGB.
00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.



And at that time the Hammer-34 is not over the site, I checked in 3DAAR.


F-16CG is only sent into the SAM rings when the SAM site is located, either by the F-16CJ with the HTS pod, or by other intelligence agencies by locating the approximate location of the battalion P-18.

The LGB can fly several miles, so the F-16CG is not required to actually overfly the battery.

biggrin

PS: of course it should be valid only for the 3/250rd PVO. All other LGB hit is a bug.
Posted By: Lonewolf357

Re: Bug reports - 08/10/12 03:20 PM

OK, I tried the new sam.exe file. here's results:

Click to reveal..
Asuluk training ground.

Practice target:
LA-17K simulating BGM-109 Tomahawk
LA-17K simulating BGM-109 Tomahawk
LA-17K simulating BGM-109 Tomahawk
LA-17K simulating BGM-109 Tomahawk
LA-17K simulating BGM-109 Tomahawk

S-125M1 Neva


00:00, Practice target LA-17K simulating BGM-109 Tomahawk launched

00:00, Practice target LA-17K simulating BGM-109 Tomahawk launched

00:00, Practice target LA-17K simulating BGM-109 Tomahawk launched

00:00, Practice target LA-17K simulating BGM-109 Tomahawk launched

00:00, Practice target LA-17K simulating BGM-109 Tomahawk launched

00:02:57, V601P 5V27U Missile launched on Channel-1
Target distance: 19km
Target azimuth: 81°
Target elevation: 0°
Target altitude: 163m
Missile guidance method: TT (Three Point)


00:03:02, V601P 5V27U Missile launched on Channel-2
Target distance: 18km
Target azimuth: 82°
Target elevation: 0°
Target altitude: 163m
Missile guidance method: TT (Three Point)


00:03:18, Missile exploded on Channel-1
Practice target LA-17K simulating BGM-109 Tomahawk killed by SAM. (miss distance: 2m)

00:03:22, Missile exploded on Channel-2
Practice target LA-17K simulating BGM-109 Tomahawk killed by SAM. (miss distance: 4m)

00:03:33, V601P 5V27U Missile launched on Channel-1
Target distance: 20km
Target azimuth: 56°
Target elevation: 0°
Target altitude: 133m
Missile guidance method: TT (Three Point)


00:03:38, V601P 5V27U Missile launched on Channel-2
Target distance: 19km
Target azimuth: 53°
Target elevation: 0°
Target altitude: 133m
Missile guidance method: TT (Three Point)


00:03:52, V601P 5V27U Missile launched on Channel-1
Target distance: 15km
Target azimuth: 50°
Target elevation: 0°
Target altitude: 133m
Missile guidance method: TT (Three Point)


00:03:57, V601P 5V27U Missile launched on Channel-2
Target distance: 14km
Target azimuth: 49°
Target elevation: 0°
Target altitude: 133m
Missile guidance method: TT (Three Point)


00:04:10, Missile exploded on Channel-1
Practice target LA-17K simulating BGM-109 Tomahawk killed by SAM. (miss distance: 13m)

00:04:14, Missile exploded on Channel-2
Practice target LA-17K simulating BGM-109 Tomahawk killed by SAM. (miss distance: 2m)

00:04:35, V601P 5V27U Missile launched on Channel-1
Target distance: 7km
Target azimuth: 312°
Target elevation: 1°
Target altitude: 142m
Missile guidance method: TT (Three Point)


00:04:40, V601P 5V27U Missile launched on Channel-2
Target distance: 8km
Target azimuth: 308°
Target elevation: 0°
Target altitude: 142m
Missile guidance method: TT (Three Point)


Total, SNR On Air Time: 3min 43sec


Of 8 missiles fired, 4 failed to appear. No NE ZAHVAT messages. They are also do not appear in 3DAAR.
Posted By: Hpasp

Re: Bug reports - 08/10/12 03:38 PM

Originally Posted By: Vympel
I think I found a bug. In new Allied force scenario May 2. No matter which site i choose my SNR always gets hit by LGB, and always by the same plane and at the same time.
Here is one of the AARs:
Click to reveal..

02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV

S-125M1 Neva

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, wth LGB.
00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.



And at that time the Hammer-34 is not over the site, I checked in 3DAAR.


This bug is fixed.
You can download the fixed exe here:

http://www.mediafire.com/?iput2buhmisdyf3

Just replace the installed sam.exe...
Posted By: piston79

Re: Bug reports - 08/10/12 04:29 PM

Originally Posted By: Hpasp

This bug is fixed.
You can download the fixed exe here:

http://www.mediafire.com/?iput2buhmisdyf3

Just replace the installed sam.exe...


Did you replace this in your home site download link?
What about LGB in 3D AAR?
Posted By: Hpasp

Re: Bug reports - 08/10/12 05:20 PM

Originally Posted By: piston79
Originally Posted By: Hpasp

This bug is fixed.
You can download the fixed exe here:

http://www.mediafire.com/?iput2buhmisdyf3

Just replace the installed sam.exe...


Did you replace this in your home site download link?


No this is just a test sam.exe, provided for this community.

Originally Posted By: piston79
What about LGB in 3D AAR?


As I will leave on holiday soon, I tried to fix the easy bugs.
LGB/GAM/dumb bomds are not planned to be simulated in 3DAAR.
Posted By: Vympel

Re: Bug reports - 08/10/12 06:10 PM

Originally Posted By: Hpasp

This bug is fixed.
You can download the fixed exe here:

http://www.mediafire.com/?iput2buhmisdyf3

Just replace the installed sam.exe...


Thank you, I can confirm that now only 3/250 gets hit.
Posted By: Cat

Bug reports - 08/14/12 11:44 PM

Put your bug reports here.
Posted By: xxJohnxx

Re: Bug reports - 08/19/12 10:41 PM

I am new to this forum, so I wanted to say Hello to everybody!
I followed the thread, which was linked on the Samsim website a little while now, and today, as the link seems to have changed on the website I think, I found this subforum. Nice to see that there is a place to chat with other virtual SAM operators wink
But the reason I registered here is that I am having a problem with the Vega. First I have to say I prefer the Vega over all the other simulated systems, however I am a really bad virtual operator as it seems.
However, sometimes I even get to the point where it is time to do so. I don't have a problem with launching a missile, however afterwards I get a software problem as it seems.
For instance, I tried to shoot the SR-71, as descriped erlier this thread. First I launch a missile, to freigthen the SR-71 (like I said, as described wink ) however once it turns on it's jammer i get a "Runtimeerror 11" from Windows which says: "Devided by zero" and then Samsim quite, without an AAR to be shown.
The same happened as I tried to shoot a jamming Scud missile. I was (as I assumed) correctly tracking the jamming target, launched 4 or five missiles and one of them actually seemed to hit (Target was at computed impact point), and like it did the jammer would be 'dead' now and no jamming would be recived any more. However, as the missile is about to hit, I get the Runtimeerror 11 again.
The third conditon I get this error is, when I switch the radar back to K7 (At the dial at the right of the 4 System start switches)(at least it looks like the letters K and 7, could be something diffrent too, unfortunatly I can't read Russian letters) while a target is beeing fully tracked. I know, there is no point in doing so, but may it helps to reproduce the error.

I just wanted to point that out, as somthing seems to be faulty there, altought it could be me too. I did several reinstallations, however nothing changed.

I am using version .925

Many thanks for this great simulator, and best regards from Austria

Jonathan
Posted By: farokh

Re: Bug reports - 08/20/12 08:20 AM

hi jonathan... very wellcom thumbsup

Originally Posted By: xxJohnxx

The same happened as I tried to shoot a jamming Scud missile. I was (as I assumed) correctly tracking the jamming target, launched 4

huuuum? are u serious ??? in this real life scud balestic missile use jamming pod? thumbsup
Posted By: piston79

Re: Bug reports - 08/20/12 10:06 AM

Hi, probably should move your posts here:
http://simhq.com/forum/ubbthreads.php/topics/3626538/Bug_reports.html#Post3626538
Posted By: Cat

Re: Bug reports - 08/20/12 09:57 PM

I moved it already. Whoever sent me the heads up, thanks.
Posted By: Mdore

Re: Bug reports - 08/21/12 03:08 AM

Just thought I'd make two quick bug reports both minor.

You've spelled "Libya" wrong on the options dialogue box for the SA-5. You've spelled it "Lybia"

And second. I'm not sure if this is a bug, or if you're just playing a joke on people. If you disable sound in the options dialogue, it disables all sounds EXCEPT for nuclear explosions. The unexpected boom scared me half to death. Thanks Hpasp! smile
Posted By: Hpasp

Re: Bug reports - 08/23/12 12:48 PM

Originally Posted By: Mdore
Just thought I'd make two quick bug reports both minor.

You've spelled "Libya" wrong on the options dialogue box for the SA-5. You've spelled it "Lybia"

And second. I'm not sure if this is a bug, or if you're just playing a joke on people. If you disable sound in the options dialogue, it disables all sounds EXCEPT for nuclear explosions. The unexpected boom scared me half to death. Thanks Hpasp! smile


It was an unintentional "bombastic" mistake, but I will fix it.
thumbsup
Posted By: Hpasp

Re: Bug reports - 08/23/12 03:54 PM

SAMSIM v925.3 exe can be downloaded...

http://www.mediafire.com/?gs2r4scgyqd6uq5

It has several bug fixes...

- Nuclear blast audible even if No Sound selected.
- Libya typo is corrected

... and enhancements...

- AAR is saved with the 3DAAR
- SNR ON/OFF AIR is timestamped on the AAR
Posted By: piston79

Re: Bug reports - 08/23/12 04:14 PM

925.3, maybe....
Posted By: farokh

Re: Bug reports - 08/24/12 12:57 PM

why for attack to jamming target in sa-2 F or E we have to switch off transmitter but at sa-3 no need to switch off transmitter ?
i never seen any notice in sa-3 PDF about it !
is this a bug? confused

because sa-2 and sa-3 using one method for guidance (command guided) !
Posted By: Hpasp

Re: Bug reports - 08/24/12 04:46 PM

Originally Posted By: milang
why for attack to jamming target in sa-2 F or E we have to switch off transmitter but at sa-3 no need to switch off transmitter ?
i never seen any notice in sa-3 PDF about it !
is this a bug? confused

because sa-2 and sa-3 using one method for guidance (command guided) !


It is again related to the two coordinate systems the Neva use, compared to the Dvina/Volhov.
If the Neva looses its target, it looses all launched missiles, while the Dvina/Volhov could reacquire the target.
Posted By: Vonzeppelin

Re: Bug reports - 08/24/12 04:52 PM

Thanx xxJohnxx

Then it´s not just me. I have also tried several re-installs (and re-downloads) with the same results. The second the SA-5 warhead detonates I get the runtime error and crash. It didn´t do that in v924 (I´m using v925 now), so this smells a lot like a bug. Hope it can be fixed quickly, as I love the SA-5 and is finally starting to master the system.
BTW. Can´t wait until the Nike Hercules get´s implemented. A SAM system where you can actually read the labels on the buttons would be great. Have started to learn Russian just because of this SIM but it´ll be a while before I can understand all the buttons as easily as if they were in English.
Posted By: xxJohnxx

Re: Bug reports - 08/24/12 05:02 PM

Hi Vonzeppelin

Originally Posted By: Vonzeppelin

Then it´s not just me. I have also tried several re-installs (and re-downloads) with the same results. The second the SA-5 warhead detonates I get the runtime error and crash. It didn´t do that in v924 (I´m using v925 now), so this smells a lot like a bug. Hope it can be fixed quickly, as I love the SA-5 and is finally starting to master the system.
BTW. Can´t wait until the Nike Hercules get´s implemented. A SAM system where you can actually read the labels on the buttons would be great. Have started to learn Russian just because of this SIM but it´ll be a while before I can understand all the buttons as easily as if they were in English.


The bug I mentioned has been fixed in v925.2. Some posts above yours you can find the v925.3 version, which will fix the SA-5 problem. wink
Posted By: piston79

Re: Bug reports - 08/24/12 07:35 PM

Originally Posted By: milang
why for attack to jamming target in sa-2 F or E we have to switch off transmitter but at sa-3 no need to switch off transmitter ?
i never seen any notice in sa-3 PDF about it !
is this a bug? confused

because sa-2 and sa-3 using one method for guidance (command guided) !


http://simhq.com/forum/ubbthreads.php/topics/3498046/Re_SAM_Simulator.html#Post3498046
Posted By: farokh

Re: Bug reports - 08/24/12 10:54 PM

i guess i found a bug thumbsup

with sa-2 f dvina in first libyan scenario when i want shot down that f-18
.... my trasmiter going to be off and set to jamming attack but when i launch missiles' my missile goes wrong way and so close from that f-18 and do no explode

but when i let my transmiter stiil on ... i lock on f-18 and i launch missile and killed by sam
but why when my transmiter off and set to jamming target my missile goes wrong way???? rolleyes

it is not logical......

edit: check my 3daaar!!!!

https://rapidshare.com/files/2929409684/3DAAR-2002-09-24_15-23-48.gpx

and my twice repeat

https://rapidshare.com/files/4256092071/3DAAR-2002-09-24_15-39-34.gpx
Posted By: piston79

Re: Bug reports - 08/25/12 10:02 AM

Some AAR, screenshots and 3DAAR will be usefull when bug reporting... End there is no jamming - so no tracking.... Just a blank shot?

EDIT: Which missile bothers you?

EDIT2: Could you do a video?
Posted By: farokh

Re: Bug reports - 08/25/12 10:19 AM

Originally Posted By: piston79
Some AAR, screenshots and 3DAAR will be usefull when bug reporting... End there is no jamming - so no tracking.... Just a blank shot?


nooo..... i lock on jamming line ! at first move i shoted down on agm harm and i flowing that jamming line ... and i twice move i lock on jsmming target ... so i have to swich off tramister ... i do it ... but at scope i do not any sign from any jamming line!!!!!!!! eek2

edit dude i shoted down some aircraft in line break! with sa-2F ... when i lock on jamming target .. i switch off my transmiter but sign of jamming line still on my scopes!
but at first libyan scenario when i swich off my transmiter i have no sign of jamming line on my scopes!
Posted By: piston79

Re: Bug reports - 08/25/12 10:23 AM

Originally Posted By: milang
but at first libyan scenario when i swich off my transmiter i have no sign of jamming line on my scopes!


Not a bug - just better jammers (reacts only when transmition is against them, not like in Vietnam.
Posted By: farokh

Re: Bug reports - 08/25/12 10:27 AM

Originally Posted By: piston79
Originally Posted By: milang
but at first libyan scenario when i swich off my transmiter i have no sign of jamming line on my scopes!


Not a bug - just better jammers (reacts only when transmition is against them, not like in Vietnam.


so... if it's not a bug... where is the solution ??? i have to attack to jamming target with transmitter switch on? confused
edit: because when my transmitter still on... i can hit f-18 !!! this is realistic ? ? ? .........
Posted By: Muggs

Re: Bug reports - 08/25/12 10:39 AM

Hpasp, thanks for v923.3 thumbsup
Posted By: piston79

Re: Bug reports - 08/25/12 10:52 AM

Originally Posted By: milang
[edit: because when my transmitter still on... i can hit f-18 !!! this is realistic ? ? ? .........


Yes, it is super realistic to use your radar to find a target... biggrin
Posted By: Vonzeppelin

Re: Bug reports - 08/29/12 04:09 PM

Thanks a lot xxJohnxx

Downloading it right now.
Posted By: Hpasp

Re: Bug reports - 08/29/12 05:16 PM

Could you help me on the disappearing Neva missiles bug, by describing how can I recreate those situation?

Thanks,
Posted By: Lieste

Re: Bug reports - 08/29/12 05:51 PM

Originally Posted By: milang
Originally Posted By: piston79
Originally Posted By: milang
but at first libyan scenario when i swich off my transmiter i have no sign of jamming line on my scopes!


Not a bug - just better jammers (reacts only when transmition is against them, not like in Vietnam.


so... if it's not a bug... where is the solution ??? i have to attack to jamming target with transmitter switch on? confused
edit: because when my transmitter still on... i can hit f-18 !!! this is realistic ? ? ? .........


Yes, you use home on jam, but you need to give the threat aircraft a reason to use jamming... With the radar off he is silent ~ "ECM on" merely authorises the pod to jam when illuminated. Because of the jamming you have to use the less efficient T/T mode rather than half-lead as range information is denied, which reduces maximum engagement range considerably, and increases missile manoeuvre requirement in the end-game. Of course the most important difference to Vietnam is that you can't just 'aim for the strobe' with impunity ~ by needing to illuminate the target to get a valid target of any type you become vulnerable to ARM, and HARM is far more responsive than Standard ARM or Shrike.
Posted By: farokh

Re: Bug reports - 08/29/12 06:12 PM

Originally Posted By: Hpasp
Could you help me on the disappearing Neva missiles bug, by describing how can I recreate those situation?

Thanks,


excuse me what? screwy this is my first time mr.hpasp say help! eek2
i guess neva have some bug,, witch one u want??? that bug when launch missile... and i hear sound launch, but i never seen any missile in my scope!!!!!? this situation ?
Posted By: Hpasp

Re: Bug reports - 08/29/12 06:42 PM

Originally Posted By: milang
Originally Posted By: Hpasp
Could you help me on the disappearing Neva missiles bug, by describing how can I recreate those situation?

Thanks,


excuse me what? screwy this is my first time mr.hpasp say help! eek2
i guess neva have some bug,, witch one u want??? that bug when launch missile... and i hear sound launch, but i never seen any missile in my scope!!!!!? this situation ?


Correct.
I would like to release a v0.925B version during the weekend, including the fixes of v0.925.3, just this bug is not found/fixed yet, and I cannot recreate it...
Posted By: PN79

Re: Bug reports - 08/29/12 06:50 PM

Originally Posted By: Hpasp
Could you help me on the disappearing Neva missiles bug, by describing how can I recreate those situation?

Thanks,


Hallo
I can help only during weekend. So if it is not solved by then I will try to help you. Anyway I also saw that problem. So far my experience is that when I shoot missile against the first target everything is ok but if I very quickly acquire next target in significantly different bearing and I launch missile against it without much delay sometimes I hear only sound of starting missiles but no missiles are actually launched. It also messes 3DAAR if I remember correctly. I recommend to you to start Asuluk mission with targets coming from all sides and try to launch against them as much missiles as possible. Then bug can be may be seen.
Posted By: farokh

Re: Bug reports - 08/29/12 07:02 PM

i remember... at one situation in vietnam...when i lock on, one f-4 around east... but i choose western launcher ... to launch
when i launch first missile... my missile missed but when i launch my twice missile... without no problem can get target!
maybe at different situation ... some launcher cant support some azimuth degrees !!!!! example: launch west to east OR launch south to north!
this is my guess sigh
Posted By: farokh

Re: Bug reports - 08/29/12 08:40 PM

an another problem is ....... kill frame after passed 10min on vietnam scenarios!,,, this is bug hpasp... i dont know why after 10min passed on vietnam scenario's kill frame is begin.. no antivirus no scaning,,, just sam sim frown this is serious bug....
hpasp.. when u creat scenario... did u add any (time limit) code for scenario's????
something going to be wrong when 10min passed and u still on scenario's (my frame going down under 7fPS) screwy
Posted By: Alien_MasterMynd

Re: Bug reports - 08/30/12 06:13 AM

Hpasp: Regarding Neva bug - just select Ashuluk, five targets, shoot the first one down, do not change launcher, acquire the second target and shoot at it. Either one or both missiles will not be shown on indicator (neither in 3DAAR and nothing will be hit).
Posted By: Hpasp

Re: Bug reports - 08/30/12 10:10 AM

I suspect that the lost missile case, has some relation to the previous missile launched before (and ended its flight)...
Posted By: Alien_MasterMynd

Re: Bug reports - 08/30/12 10:51 AM

And I forgot to mention - when you fire another pair of missiles, they will fly correctly (and in this lost missile case does not matter whether you change launcher or not, they will be lost in any case).
Posted By: piston79

Re: Bug reports - 09/01/12 07:38 PM

Crack-71 shot's a HARM, which was invisible on 3D AAR:
Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


1/250 rd PVO, Ugrinovci ( 83m)
S-125M1 Neva


+++++++++++++++++
00:02:01, SNR ON AIR


00:02:19, F-16CJ Weasel Falcon SEAD Crack-71 launched AGM-88 HARM missile No. 1
00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.

00:02:56, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:04:31, SNR ON AIR


00:04:44, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:05:24, SNR ON AIR


00:05:31, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:05:46, SNR ON AIR


00:05:54, V601P 5V27U Missile launched on Channel-1
Target distance: 24km
Target azimuth: 274°
Target elevation: 19°
Target altitude: 8km
Missile guidance method: TT (Three Point)


00:06:04, V601P 5V27U Missile launched on Channel-2
Target distance: 24km
Target azimuth: 273°
Target elevation: 22°
Target altitude: 9km
Missile guidance method: TT (Three Point)


00:06:15, Missile exploded on Channel-1
AN/ALE-50 Towed Decoy killed by SAM. (miss distance: 3m)

00:06:24, Missile exploded on Channel-2
AN/ALE-50 Towed Decoy hit by SAM. (miss distance: 96m)

00:06:40, V601P 5V27U Missile launched on Channel-1
Target distance: 12km
Target azimuth: 262°
Target elevation: 32°
Target altitude: 6,9km
Missile guidance method: TT (Three Point)


00:07:04, Missile exploded on Channel-1
F-16CG Night Falcon DEAD Hammer-34 hit by SAM. (miss distance: 69m)

00:07:17, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 2min 45sec




Also a question... How much is the RCS of the AN/ALE-50?
Posted By: Hpasp

Re: Bug reports - 09/02/12 10:05 AM

Originally Posted By: piston79
Crack-71 shot's a HARM, which was invisible on 3D AAR:
Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


1/250 rd PVO, Ugrinovci ( 83m)
S-125M1 Neva


+++++++++++++++++
00:02:01, SNR ON AIR


00:02:19, F-16CJ Weasel Falcon SEAD Crack-71 launched AGM-88 HARM missile No. 1
00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.

00:02:56, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:04:31, SNR ON AIR


00:04:44, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:05:24, SNR ON AIR


00:05:31, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:05:46, SNR ON AIR


00:05:54, V601P 5V27U Missile launched on Channel-1
Target distance: 24km
Target azimuth: 274°
Target elevation: 19°
Target altitude: 8km
Missile guidance method: TT (Three Point)


00:06:04, V601P 5V27U Missile launched on Channel-2
Target distance: 24km
Target azimuth: 273°
Target elevation: 22°
Target altitude: 9km
Missile guidance method: TT (Three Point)


00:06:15, Missile exploded on Channel-1
AN/ALE-50 Towed Decoy killed by SAM. (miss distance: 3m)

00:06:24, Missile exploded on Channel-2
AN/ALE-50 Towed Decoy hit by SAM. (miss distance: 96m)

00:06:40, V601P 5V27U Missile launched on Channel-1
Target distance: 12km
Target azimuth: 262°
Target elevation: 32°
Target altitude: 6,9km
Missile guidance method: TT (Three Point)


00:07:04, Missile exploded on Channel-1
F-16CG Night Falcon DEAD Hammer-34 hit by SAM. (miss distance: 69m)

00:07:17, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 2min 45sec




Also a question... How much is the RCS of the AN/ALE-50?


Nobody knows, but theoretically it should be bigger than its carriers (F-16, B-1B).
In SAMSIM, it is selected to be 10sqrm.
Posted By: max2012

Re: Bug reports - 09/02/12 11:42 AM


Version .925 or .925В

I download simply .925
Posted By: max2012

Re: Bug reports - 09/02/12 11:43 AM


Version .925 or .925B

I download simply.925
Posted By: Hpasp

Re: Bug reports - 09/02/12 11:45 AM

Just few minutes before new version getting available...
Posted By: max2012

Re: Bug reports - 09/02/12 11:46 AM


I understood without problems!
Posted By: max2012

Re: Bug reports - 09/02/12 11:48 AM


Question, and about Volkhov the problem was corrected or not.

I about the Zone of Defeat in El Dorado not truly display of Lines.
Posted By: max2012

Re: Bug reports - 09/02/12 11:54 AM


While any errors I do not see in version 923.3 didn't see while.

About Volkhov in El Dorado I don't know it is possible to call it the Error incorrectly Lines layout of the Zone of Defeat.
Posted By: Hpasp

Re: Bug reports - 09/02/12 11:55 AM

In release v925B (v925.4), two bugs are fixed compared to the v925.3:

- Neva missiles lost after launch (hopefully)
- F-15C not reacting to incoming missiles during OAF
Posted By: piston79

Re: Bug reports - 09/02/12 02:54 PM

Originally Posted By: Hpasp

Nobody knows, but theoretically it should be bigger than its carriers (F-16, B-1B).
In SAMSIM, it is selected to be 10sqrm.


I've noticed on "C" screen of NEVA, that the beam iluminates somethin', just slight away form the jamming area, but when check it ot the FCO screens, nothing can be seen, thought it just iluminates ALE-50 only...

By the way, I've posted in the old topic a question about changed APP-75 behaviour (vissible against the Libyan SR-71), but still no comment about it... sigh
Posted By: Hpasp

Re: Bug reports - 09/02/12 03:38 PM

Originally Posted By: piston79

By the way, I've posted in the old topic a question about changed APP-75 behaviour (vissible against the Libyan SR-71), but still no comment about it... sigh


I not seen any problem with those screenshots.

APP behavior was not touched quite a long ago...
... so I need more detailed bug description to be able to track this issue down.
Posted By: piston79

Re: Bug reports - 09/02/12 04:03 PM

Originally Posted By: Hpasp

APP behavior was not touched quite a long ago...
... so I need more detailed bug description to be able to track this issue down.


It's not a bug or tuning APP-75 (probably there is a change on other stuff, which influent the difference), I believe, but there is a difference in every new version. Here my post (it was moved to SA-2 topic):

Click to reveal..
Originally Posted By: piston79
This is what I meant:
Previouse version:


Current version:


Mission: El Dorado Canyon
Target: SR-71 Blackbird
Method: T/T87B

EDIT: This was noticed thanks to MAX2012... thumbsup

EDIT2:Destruction zone was displayed in a different way and size (see range marks on the right of the epsilon screen), so there is some change in the algorytm of the S-75M3-OP APP-75M work!!!


There was another thing which I believe is not correct, but also leaved without attention/answer - Using UPR mode in T/T87. Using Libyan SR-71 is a good ilustration - missiles didn't lead against azimut boresight, but actually they are trailing behind... It shouldn't be like this, I believe...

EDIT:
The "always hitting with LGB" bug appears again with Dvina:
Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


3/250 rd PVO, Karlovcic ( 82m)
SA-75M Dvina

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, with LGB.00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.


EDIT2:
"Volkhov" also...:
Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


3/250 rd PVO, Karlovcic ( 82m)
S-75M3 Volkhov


+++++++++++++++++
00:00:53, SNR ON AIR


00:01:11, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:01:15, SNR ON AIR


00:01:23, SNR OFF THE AIR
-----------------

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, with LGB.
00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.

Total, SNR On Air Time: 1min 26sec


EDIT3:"Krug" also:
Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


3/250 rd PVO, Karlovcic ( 82m)
2K11 KRUG-M1


+++++++++++++++++
00:00:44, SNR ON AIR


00:01:20, Missile launched
Target distance: 23km
Target azimuth: 208°
Target elevation: 9°
Target altitude: 3,9km
Missile guidance method: TT (Three Point)


00:01:54, Missile exploded
RQ-1 Predator UAV killed by SAM. (miss distance: 0m)

00:01:54, F-16CJ Weasel Falcon SEAD Crack-71 launched AGM-88 HARM missile No. 1


00:02:05, Missile launched
Target distance: 24km
Target azimuth: 207°
Target elevation: 8°
Target altitude: 3,6km
Missile guidance method: TT (Three Point)


00:02:40, Missile exploded
RQ-1 Predator UAV killed by SAM. (miss distance: 12m)

00:02:42, F-16CJ Weasel Falcon SEAD Crack-73 launched AGM-88 HARM missile No. 1


00:02:44, SNR OFF THE AIR
-----------------

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, with LGB.

Total, SNR On Air Time: 6min 42sec
Posted By: max2012

Re: Bug reports - 09/02/12 08:17 PM


Watch this video S-125 Neva

Rather Error!

http://www.mediafire.com/?d9wygyv5e86fpdb
Posted By: Hpasp

Re: Bug reports - 09/02/12 09:27 PM

Originally Posted By: piston79
Originally Posted By: Hpasp

APP behavior was not touched quite a long ago...
... so I need more detailed bug description to be able to track this issue down.


It's not a bug or tuning APP-75 (probably there is a change on other stuff, which influent the difference), I believe, but there is a difference in every new version. Here my post (it was moved to SA-2 topic):

Click to reveal..
Originally Posted By: piston79
This is what I meant:
Previouse version:


Current version:


Mission: El Dorado Canyon
Target: SR-71 Blackbird
Method: T/T87B

EDIT: This was noticed thanks to MAX2012... thumbsup

EDIT2:Destruction zone was displayed in a different way and size (see range marks on the right of the epsilon screen), so there is some change in the algorytm of the S-75M3-OP APP-75M work!!!


I do not see a bug here. The difference is caused by the difference in P.


Originally Posted By: piston79


There was another thing which I believe is not correct, but also leaved without attention/answer - Using UPR mode in T/T87. Using Libyan SR-71 is a good ilustration - missiles didn't lead against azimut boresight, but actually they are trailing behind... It shouldn't be like this, I believe...


You shouldn't use UPR with I87V!
In T/T, they should try to fly on the boresight, they should not lead it.

Originally Posted By: piston79


EDIT:
The "always hitting with LGB" bug appears again with Dvina:
Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


3/250 rd PVO, Karlovcic ( 82m)
SA-75M Dvina

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, with LGB.00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.


EDIT2:
"Volkhov" also...:
Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


3/250 rd PVO, Karlovcic ( 82m)
S-75M3 Volkhov


+++++++++++++++++
00:00:53, SNR ON AIR


00:01:11, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:01:15, SNR ON AIR


00:01:23, SNR OFF THE AIR
-----------------

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, with LGB.
00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.

Total, SNR On Air Time: 1min 26sec


EDIT3:"Krug" also:
Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


3/250 rd PVO, Karlovcic ( 82m)
2K11 KRUG-M1


+++++++++++++++++
00:00:44, SNR ON AIR


00:01:20, Missile launched
Target distance: 23km
Target azimuth: 208°
Target elevation: 9°
Target altitude: 3,9km
Missile guidance method: TT (Three Point)


00:01:54, Missile exploded
RQ-1 Predator UAV killed by SAM. (miss distance: 0m)

00:01:54, F-16CJ Weasel Falcon SEAD Crack-71 launched AGM-88 HARM missile No. 1


00:02:05, Missile launched
Target distance: 24km
Target azimuth: 207°
Target elevation: 8°
Target altitude: 3,6km
Missile guidance method: TT (Three Point)


00:02:40, Missile exploded
RQ-1 Predator UAV killed by SAM. (miss distance: 12m)

00:02:42, F-16CJ Weasel Falcon SEAD Crack-73 launched AGM-88 HARM missile No. 1


00:02:44, SNR OFF THE AIR
-----------------

00:02:44, SNR bombed by F-16CG Night Falcon DEAD Hammer-34, with LGB.

Total, SNR On Air Time: 6min 42sec


Why is it a bug?
LGB do not need illumination at all.
Posted By: Hpasp

Re: Bug reports - 09/02/12 09:32 PM

Originally Posted By: max2012

Watch this video S-125 Neva

Rather Error!

http://www.mediafire.com/?d9wygyv5e86fpdb


Target flown out of the Neva firing zone, and APP worked as advertised.
Not an error, just a feature of Neva!
Posted By: piston79

Re: Bug reports - 09/03/12 04:38 AM

Originally Posted By: Hpasp

Why is it a bug?
LGB do not need illumination at all.


I don't see why should report bugs, when you didn't even take an effort to READ what I've post... All LGB hits are exactly at 00.02.44, no mather which site I used to occupy... Probably added some "GOD mode" for F-16''s LANTIRN system? Or just cooling our pasion to use something else but "Neva" in this scenario?

I wish to point it up that THERE WAS the same kind of bug in the first 0.925 release, probably mistekanly worked on the old .exe for this version...

Posted By: max2012

Re: Bug reports - 09/03/12 09:59 AM


And how then to shoot at Dogon?
Posted By: Hpasp

Re: Bug reports - 09/03/12 03:28 PM

Originally Posted By: max2012

And how then to shoot at Dogon?


The APP will automatically launch only if the probability of destruction is 98%.
(with two missiles, against a non jamming and maneuvering target)

Any other case, you need to launch missiles manually, and accept lower probability of hit.
Posted By: Hpasp

Re: Bug reports - 09/03/12 03:36 PM

Originally Posted By: piston79
Originally Posted By: Hpasp

Why is it a bug?
LGB do not need illumination at all.


I don't see why should report bugs, when you didn't even take an effort to READ what I've post... All LGB hits are exactly at 00.02.44, no mather which site I used to occupy... Probably added some "GOD mode" for F-16''s LANTIRN system? Or just cooling our pasion to use something else but "Neva" in this scenario?

I wish to point it up that THERE WAS the same kind of bug in the first 0.925 release, probably mistekanly worked on the old .exe for this version...



Dear Piston,

That mission is elected to be a DEAD one, meaning, that the F-16CG knows the SAM site approximate location, regardless of SNR emission...
(During the war, this happened to several SAM units. 1/250, 6/250, 8/250, ...)
... and will bomb it if flies into range.

(Probably the EA-6B's are helped triangulating the P-18 radars.)

Br,
Hpasp

PS: to be able to correct a bug, first I need to understand it, than be able to reproduce it.
Posted By: piston79

Re: Bug reports - 09/03/12 04:11 PM

Originally Posted By: Hpasp

I do not see a bug here. The difference is caused by the difference in P.


There is no such a thing like "difference in P"... This is the same scenario with the same batterie, screenshot on the same distance against the same (and only) target.


Quote:
You shouldn't use UPR with I87V!
In T/T, they should try to fly on the boresight, they should not lead it.


I know. This is against the rule. Now what? Court martialed?


EDIT:

I apologise for missleading:
It appears that when we are in the position of 3/250 rd PVO, Karlovcic, Hammer-34 kills you... So, it's not a bug, but a dead end (exept killing Hammer first...
Does killing the carrier kills the LGB mission??? wink
Posted By: Vympel

Re: Bug reports - 09/04/12 11:30 AM

Originally Posted By: piston79

EDIT:

I apologise for missleading:
It appears that when we are in the position of 3/250 rd PVO, Karlovcic, Hammer-34 kills you... So, it's not a bug, but a dead end (exept killing Hammer first...
Does killing the carrier kills the LGB mission??? wink


Maybe, but hammer kills you way before he is in range of your missiles.
Posted By: Hpasp

Re: Bug reports - 09/04/12 11:56 AM

Originally Posted By: piston79
Originally Posted By: Hpasp

I do not see a bug here. The difference is caused by the difference in P.


There is no such a thing like "difference in P"... This is the same scenario with the same batterie, screenshot on the same distance against the same (and only) target.


Quote:
You shouldn't use UPR with I87V!
In T/T, they should try to fly on the boresight, they should not lead it.


I know. This is against the rule. Now what? Court martialed?


EDIT:

I apologise for missleading:
It appears that when we are in the position of 3/250 rd PVO, Karlovcic, Hammer-34 kills you... So, it's not a bug, but a dead end (exept killing Hammer first...
Does killing the carrier kills the LGB mission??? wink


Killing Hammer first is the solution.
Posted By: piston79

Re: Bug reports - 09/04/12 01:11 PM

Originally Posted By: Hpasp
Click to reveal..
Originally Posted By: piston79
Originally Posted By: Hpasp

I do not see a bug here. The difference is caused by the difference in P.


There is no such a thing like "difference in P"... This is the same scenario with the same batterie, screenshot on the same distance against the same (and only) target.


Quote:
You shouldn't use UPR with I87V!
In T/T, they should try to fly on the boresight, they should not lead it.


I know. This is against the rule. Now what? Court martialed?

EDIT:

I apologise for missleading:
It appears that when we are in the position of 3/250 rd PVO, Karlovcic, Hammer-34 kills you... So, it's not a bug, but a dead end (exept killing Hammer first...
Does killing the carrier kills the LGB mission??? wink
[/spoiler]

Killing Hammer first is the solution.


Only for 1/3 of my post... wink
Posted By: Hpasp

Re: Bug reports - 09/04/12 01:23 PM

NATO DEAD tactic can be pretty effective...

Click to reveal..
Originally Posted By: Hpasp
Originally Posted By: piston79
Originally Posted By: Hpasp

So far, no bombs are simulated, but I will give it a thought.


I could send you some test data for S-75 and S-125 against bombs (Walleye?)...

Originally Posted By: Hpasp

Dvina was never used operationally during OAF, the 6/250 was far from using it.


How far? She was on a wartime position....


The 6/250rd PVO was a Neva SAM Battery, located in Smederevo before OAF.




They launched 2-2 Neva missiles against 1-1 targets during the 7th and 23rd day of the war.
(probably they scored some AN/ALE-50's)

During the 26th day of the war, while they tracked a target from their Lipe firing position they suffered a direct HARM hit, followed by an LGB bombing on their location. (typical DEAD attack)

2 soldiers died during the attack, (Robert Lajcak 31 years old, and Blagoja Radic 38 years old) RIP...

... and 4 was injured.

The battery Neva SAM equipment was destroyed beyond repair.

The shaken crew was given the task of reactivating one of the ancient SA-75MK Dvina (SA-2F) system from the Aviation Museum.
This activity was taken place in the Simanovci firing position.

On the 50th day of the war, their equipment was bombed again, destroying the Dvina PAA cabin (Fan Song-F) with a direct LGB hit.
That antique equipment was pretty far from battle ready, when it was destroyed, but at least this time, nobody was hurt.






Serbian Air Defense units lost 40 dead, and 110 injured during OAF.
Posted By: Hpasp

Re: Bug reports - 09/04/12 03:20 PM

... solved?

I launched 10 Neva missiles against 5 targets in Asuluk, and each of those scored a hit.


Click to reveal..

Asuluk training ground.

Practice target:
LA-17 simulating F-86 Sabre
LA-17 simulating F-86 Sabre
LA-17 simulating F-86 Sabre
LA-17 simulating F-86 Sabre
LA-17 simulating F-86 Sabre

S-125M1 Neva


00:00, Practice target LA-17 simulating F-86 Sabre launched

+++++++++++++++++
00:00:20, SNR ON AIR


00:00:39, SNR OFF THE AIR
-----------------


01:00, Practice target LA-17 simulating F-86 Sabre launched

+++++++++++++++++
00:01:44, SNR ON AIR


02:00, Practice target LA-17 simulating F-86 Sabre launched

00:02:46, V601P 5V27U Missile launched on Channel-1
Target distance: 23km
Target azimuth: 72°
Target elevation: 20°
Target altitude: 8,1km
Missile guidance method: PS (Lead)


00:02:51, V601P 5V27U Missile launched on Channel-2
Target distance: 22km
Target azimuth: 72°
Target elevation: 21°
Target altitude: 8,1km
Missile guidance method: PS (Lead)


03:00, Practice target LA-17 simulating F-86 Sabre launched

00:03:10, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 6m)

00:03:14, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 4m)

00:03:31, V601P 5V27U Missile launched on Channel-1
Target distance: 23km
Target azimuth: 133°
Target elevation: 18°
Target altitude: 7,4km
Missile guidance method: PS (Lead)


00:03:37, V601P 5V27U Missile launched on Channel-2
Target distance: 21km
Target azimuth: 132°
Target elevation: 19°
Target altitude: 7,4km
Missile guidance method: PS (Lead)


00:03:56, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 6m)

04:00, Practice target LA-17 simulating F-86 Sabre launched

00:04:00, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 6m)

00:05:30, V601P 5V27U Missile launched on Channel-1
Target distance: 12km
Target azimuth: 146°
Target elevation: 53°
Target altitude: 10km
Missile guidance method: PS (Lead)


00:05:36, V601P 5V27U Missile launched on Channel-2
Target distance: 12km
Target azimuth: 134°
Target elevation: 52°
Target altitude: 10km
Missile guidance method: PS (Lead)


00:05:52, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre hit by SAM. (miss distance: 86m)

00:05:59, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 92m)

00:06:05, V601P 5V27U Missile launched on Channel-1
Target distance: 17km
Target azimuth: 80°
Target elevation: 29°
Target altitude: 8,5km
Missile guidance method: PS (Lead)


00:06:11, V601P 5V27U Missile launched on Channel-2
Target distance: 15km
Target azimuth: 82°
Target elevation: 32°
Target altitude: 8,5km
Missile guidance method: PS (Lead)


00:06:24, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 8m)

00:06:29, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 6m)

00:06:50, V601P 5V27U Missile launched on Channel-1
Target distance: 23km
Target azimuth: 127°
Target elevation: 25°
Target altitude: 10,3km
Missile guidance method: PS (Lead)


00:06:55, V601P 5V27U Missile launched on Channel-2
Target distance: 22km
Target azimuth: 126°
Target elevation: 27°
Target altitude: 10,3km
Missile guidance method: PS (Lead)


00:07:15, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre hit by SAM. (miss distance: 112m)

00:07:19, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 8m)

00:07:25, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 5min 55sec


As I was unable to reliably recreate this bug, I would like to ask you to recreate, and confirm if it is disappeared.
Posted By: farokh

Re: Bug reports - 09/04/12 05:47 PM

did u try launch missile from south to north or west to east???
at sam time ... of course at v.0925 i launched missile from south launcher to north... but my missile missed!

Originally Posted By: Hpasp
... solved?

I launched 10 Neva missiles against 5 targets in Asuluk, and each of those scored a hit.


Click to reveal..

Asuluk training ground.

Practice target:
LA-17 simulating F-86 Sabre
LA-17 simulating F-86 Sabre
LA-17 simulating F-86 Sabre
LA-17 simulating F-86 Sabre
LA-17 simulating F-86 Sabre

S-125M1 Neva


00:00, Practice target LA-17 simulating F-86 Sabre launched

+++++++++++++++++
00:00:20, SNR ON AIR


00:00:39, SNR OFF THE AIR
-----------------


01:00, Practice target LA-17 simulating F-86 Sabre launched

+++++++++++++++++
00:01:44, SNR ON AIR


02:00, Practice target LA-17 simulating F-86 Sabre launched

00:02:46, V601P 5V27U Missile launched on Channel-1
Target distance: 23km
Target azimuth: 72°
Target elevation: 20°
Target altitude: 8,1km
Missile guidance method: PS (Lead)


00:02:51, V601P 5V27U Missile launched on Channel-2
Target distance: 22km
Target azimuth: 72°
Target elevation: 21°
Target altitude: 8,1km
Missile guidance method: PS (Lead)


03:00, Practice target LA-17 simulating F-86 Sabre launched

00:03:10, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 6m)

00:03:14, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 4m)

00:03:31, V601P 5V27U Missile launched on Channel-1
Target distance: 23km
Target azimuth: 133°
Target elevation: 18°
Target altitude: 7,4km
Missile guidance method: PS (Lead)


00:03:37, V601P 5V27U Missile launched on Channel-2
Target distance: 21km
Target azimuth: 132°
Target elevation: 19°
Target altitude: 7,4km
Missile guidance method: PS (Lead)


00:03:56, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 6m)

04:00, Practice target LA-17 simulating F-86 Sabre launched

00:04:00, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 6m)

00:05:30, V601P 5V27U Missile launched on Channel-1
Target distance: 12km
Target azimuth: 146°
Target elevation: 53°
Target altitude: 10km
Missile guidance method: PS (Lead)


00:05:36, V601P 5V27U Missile launched on Channel-2
Target distance: 12km
Target azimuth: 134°
Target elevation: 52°
Target altitude: 10km
Missile guidance method: PS (Lead)


00:05:52, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre hit by SAM. (miss distance: 86m)

00:05:59, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 92m)

00:06:05, V601P 5V27U Missile launched on Channel-1
Target distance: 17km
Target azimuth: 80°
Target elevation: 29°
Target altitude: 8,5km
Missile guidance method: PS (Lead)


00:06:11, V601P 5V27U Missile launched on Channel-2
Target distance: 15km
Target azimuth: 82°
Target elevation: 32°
Target altitude: 8,5km
Missile guidance method: PS (Lead)


00:06:24, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 8m)

00:06:29, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 6m)

00:06:50, V601P 5V27U Missile launched on Channel-1
Target distance: 23km
Target azimuth: 127°
Target elevation: 25°
Target altitude: 10,3km
Missile guidance method: PS (Lead)


00:06:55, V601P 5V27U Missile launched on Channel-2
Target distance: 22km
Target azimuth: 126°
Target elevation: 27°
Target altitude: 10,3km
Missile guidance method: PS (Lead)


00:07:15, Missile exploded on Channel-1
Practice target LA-17 simulating F-86 Sabre hit by SAM. (miss distance: 112m)

00:07:19, Missile exploded on Channel-2
Practice target LA-17 simulating F-86 Sabre killed by SAM. (miss distance: 8m)

00:07:25, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 5min 55sec


As I was unable to reliably recreate this bug, I would like to ask you to recreate, and confirm if it is disappeared.
Posted By: Lieste

Re: Bug reports - 09/04/12 06:15 PM

If I recall the manual correctly each missile launcher fires only 'out', plus the SNR azimuth is limited to +/- 240 degrees.
Posted By: Lonewolf357

Re: Bug reports - 09/05/12 07:23 PM

Originally Posted By: Hpasp
... solved?

I launched 10 Neva missiles against 5 targets in Asuluk, and each of those scored a hit.

As I was unable to reliably recreate this bug, I would like to ask you to recreate, and confirm if it is disappeared.


Hi, Hpasp!

Yes, the problem is finally solved, at least in my case.
thumbsup cheers
Posted By: piston79

Re: Bug reports - 09/06/12 04:50 PM

There was an old bug in "War of attrition" - missiles sometimes goes underground, it was with V-760 misiile, today I just used "Krug" and it does it too... Can someone test it, to be sure it's a bug? (Clearly, first mission should be used).

Posted By: Lonewolf357

Re: Bug reports - 09/06/12 07:40 PM

Indeed, the problem exists. Tried Krug in TT mode: the missiles are often go underground:

Posted By: jazjar

Re: Bug reports - 09/06/12 09:24 PM

Wow, my Neva is wacking out in the second OAF scenario. First, very strange, for the F-16 target in the north ( northernmost battery ), if I detect him in the 82.5km mode, then switch to the 37km mode, I can see his jamming spike fine, BUT... If I try to detect him in 37km mode alone, he doesn't show up. Also, when I finally got to launching a missile at 13km, he predictably launched an AGM-88C missile, it showed in the jamming spike, and also I lost lock on the F-16, losing my missiles as well.
Posted By: piston79

Re: Bug reports - 09/09/12 08:03 PM

This seems an old bug reborn... But now it is only for AGM-45 tracks...:

EDIT: This is in first Linebacker scenario, but it could be on everyone of them, will test it tommorow (if someone do that dor me, or Hpasp find that bug and kill it with a folded newspaper wink )


Quote:
Wow, my Neva is wacking out in the second OAF scenario. First, very strange, for the F-16 target in the north ( northernmost battery ), if I detect him in the 82.5km mode, then switch to the 37km mode, I can see his jamming spike fine, BUT... If I try to detect him in 37km mode alone, he doesn't show up. Also, when I finally got to launching a missile at 13km, he predictably launched an AGM-88C missile, it showed in the jamming spike, and also I lost lock on the F-16, losing my missiles as well.


Could you be more specific, like which F-16 (Nammer - xx) and so...?
Posted By: farokh

Re: Bug reports - 09/09/12 08:43 PM

attention attention

from here... i want from all of sam simulator users...
test something in your system
i think i find a bad bug in sam sim!


kill frame after around 10 minutes in sam simulator begin for me


this happened done for me very much .....

please check it on your pc : run sam simulator ... choose sa-3 goa and move to line break II scenario's
choose first night please.... fight there and try to still alive around 10 minutes... after 9 or 10 minutes u feel heavy kill frame on your system ! evry thing is going down...

please check it and soul it in this topic.

best regard

milang

Posted By: jazjar

Re: Bug reports - 09/09/12 09:14 PM

Um OK. It is 3/250 rd battery. It says F-16CJ Falcon SEAD Number-2. It comes from the northeast. scenario 2
Posted By: Hpasp

Re: Bug reports - 09/10/12 06:35 PM

Originally Posted By: piston79
There was an old bug in "War of attrition" - missiles sometimes goes underground, it was with V-760 misiile, today I just used "Krug" and it does it too... Can someone test it, to be sure it's a bug? (Clearly, first mission should be used).
Click to reveal..



I will check this bug out...

Originally Posted By: piston79
This seems an old bug reborn... But now it is only for AGM-45 tracks...:
Click to reveal..

EDIT: This is in first Linebacker scenario, but it could be on everyone of them, will test it tommorow (if someone do that dor me, or Hpasp find that bug and kill it with a folded newspaper wink )

Could you be more specific, like which F-16 (Nammer - xx) and so...?


I think, that this bug was never fixed earlier (just a rare one).
I check it out.

Originally Posted By: milang
attention attention

from here... i want from all of sam simulator users...
test something in your system
i think i find a bad bug in sam sim!


kill frame after around 10 minutes in sam simulator begin for me


this happened done for me very much .....

please check it on your pc : run sam simulator ... choose sa-3 goa and move to line break II scenario's
choose first night please.... fight there and try to still alive around 10 minutes... after 9 or 10 minutes u feel heavy kill frame on your system ! evry thing is going down...

please check it and soul it in this topic.

best regard

milang



Please try to redetect Milang bug, as I personally never faced it...
(I suspect some background virus/virus buster running.)
... during startup, SAMSIM loads all required files into memory, while it shows 0..100%.

Later it does not load anything from the disk.
Posted By: piston79

Re: Bug reports - 09/10/12 06:49 PM

Originally Posted By: Hpasp
I think, that this bug was never fixed earlier (just a rare one).
I check it out.



That was long time before - April 2012...

Quote:
Please try to redetect Milang bug, as I personally never faced it...
(I suspect some background virus/virus buster running.)
... during startup, SAMSIM loads all required files into memory, while it shows 0..100%.

Later it does not load anything from the disk.


Same with me - after 9-10 minutes in first night, first wave it starts lagging...
Posted By: Hpasp

Re: Bug reports - 09/10/12 07:03 PM

Same with me - after 9-10 minutes in first night, first wave it starts lagging...

Could you try running "resmon.exe" and find it out, what process or system resource cause this issue?

http://technet.microsoft.com/en-us/video/windows-7-screencast-resource-monitor-resmon.aspx
Posted By: piston79

Re: Bug reports - 09/10/12 07:21 PM

Nope... I am on XP... wave2
Posted By: farokh

Re: Bug reports - 09/10/12 08:32 PM

here is my best try with resmone.exe result

image mode

normal mode


one pic from memory tab



PS: i guess after exactly one time! maybe after 9 min or 10 min pass still in scenario's... one bad software start up!
maybe one Intelligent and clever bad ware Breach to basic sam sim setup! sigh

here is my this aaar from this test

Click to reveal..
S-125M1 Neva

00:00:00, B-52D Snow-01 bombed Hoa Lac AFB.
00:00:00, B-52D Brown-01 bombed Hoa Lac AFB.
00:00:00, B-52D Maple-01 bombed Kep AFB.
00:00:08, B-52D Snow-02 bombed Hoa Lac AFB.
00:00:08, B-52D Brown-02 bombed Hoa Lac AFB.
00:00:08, B-52D Maple-02 bombed Kep AFB.
00:00:40, B-52D Snow-03 bombed Hoa Lac AFB.
00:00:40, B-52D Brown-03 bombed Hoa Lac AFB.
00:00:40, B-52D Maple-03 bombed Kep AFB.

+++++++++++++++++
00:00:44, SNR ON AIR


00:01:15, F-105 Wild Weasel number 2 of pair-1 launched AGM-45 Shrike missile.


00:01:21, V601P 5V27U Missile launched on Channel-2
Target distance: 20km
Target azimuth: 21°
Target elevation: 9°
Target altitude: 3.5km
Missile guidance method: TT (Three Point)

00:01:32, B-52D Gold-01 bombed Kep AFB.

00:01:39, Missile exploded on Channel-2
AGM-45 Shrike Anti Radiation Missile killed by SAM. (miss distance: 9m)
00:01:43, B-52D Gold-02 bombed Kep AFB.

00:01:53, V601P 5V27U Missile launched on Channel-1
Target distance: 18km
Target azimuth: 21°
Target elevation: 12°
Target altitude: 3.9km
Missile guidance method: TT (Three Point)

00:01:59, B-52D Gold-03 bombed Kep AFB.

00:02:00, F-105 Wild Weasel number 2 of pair-1 launched AGM-45 Shrike missile.

00:02:08, B-52D Purple-01 bombed Phuc Yen AFB.
00:02:11, B-52D Purple-02 bombed Phuc Yen AFB.

00:02:17, Missile exploded on Channel-1
F-105 Wild Weasel number 2 of pair-1 killed by SAM. (miss distance: 1m)

00:02:20, SNR OFF THE AIR
-----------------

00:02:25, B-52D Purple-03 bombed Phuc Yen AFB.

+++++++++++++++++
00:02:39, SNR ON AIR

00:02:54, B-52G Rose-01 bombed Kinh No Complex.
00:03:00, B-52G Rose-02 bombed Kinh No Complex.
00:03:03, B-52G Rose-03 bombed Kinh No Complex.

00:03:10, V601P 5V27U Missile launched on Channel-1
Target distance: 18km
Target azimuth: 8°
Target elevation: 20°
Target altitude: 6.6km
Missile guidance method: TT (Three Point)


00:03:34, Missile exploded on Channel-1
F-4 number 2 of pair-1 blocking Noi Bai airfield hit by SAM. (miss distance: 105m)

00:03:46, V601P 5V27U Missile launched on Channel-2
Target distance: 16km
Target azimuth: 20°
Target elevation: 21°
Target altitude: 5.9km
Missile guidance method: TT (Three Point)

00:03:56, B-52D Green-02 bombed Kep AFB.
00:03:58, B-52D Green-01 bombed Kep AFB.

00:04:09, Missile exploded on Channel-2
F-4 number 2 of pair-1 blocking Noi Bai airfield killed by SAM. (miss distance: 116m)
00:04:11, B-52D Green-03 bombed Kep AFB.

00:04:29, V601P 5V27U Missile launched on Channel-1
Target distance: 18km
Target azimuth: 27°
Target elevation: 21°
Target altitude: 6.8km
Missile guidance method: TT (Three Point)

00:04:34, B-52G Lilac-01 bombed Kinh No Complex.
00:04:44, B-52G Lilac-02 bombed Kinh No Complex.
00:04:47, B-52D Walnut-02 bombed Phuc Yen AFB.

00:04:52, Missile exploded on Channel-1
F-4 number 1 of pair-1 blocking Noi Bai airfield killed by SAM. (miss distance: 30m)
00:04:54, B-52G Lilac-03 bombed Kinh No Complex.
00:04:57, B-52D Walnut-01 bombed Phuc Yen AFB.

00:04:59, V601P 5V27U Missile launched on Channel-2
Target distance: 15km
Target azimuth: 37°
Target elevation: 7°
Target altitude: 2km
Missile guidance method: TT (Three Point)

00:04:59, B-52D Walnut-03 bombed Phuc Yen AFB.

00:05:53, V601P 5V27U Missile launched on Channel-2
Target distance: 7km
Target azimuth: 93°
Target elevation: 15°
Target altitude: 2km
Missile guidance method: TT (Three Point)


00:06:04, Missile exploded on Channel-2
F-4 number 1 of pair-1 blocking Zea Lam airfield killed by SAM. (miss distance: 24m)

00:06:29, V601P 5V27U Missile launched on Channel-1
Target distance: 6km
Target azimuth: 110°
Target elevation: 18°
Target altitude: 2km
Missile guidance method: TT (Three Point)


00:06:39, Missile exploded on Channel-1
F-4 number 2 of pair-1 blocking Zea Lam airfield hit by SAM. (miss distance: 106m)

00:07:21, V601P 5V27U Missile launched on Channel-1
Target distance: 4km
Target azimuth: 141°
Target elevation: 27°
Target altitude: 2km
Missile guidance method: TT (Three Point)


00:07:28, Missile exploded on Channel-1
F-4 number 2 of pair-1 blocking Zea Lam airfield killed by SAM. (miss distance: 114m)
00:07:42, B-52G White-01 bombed Kinh No Complex.
00:07:53, B-52G White-02 bombed Kinh No Complex.

00:07:59, V601P 5V27U Missile launched on Channel-1
Target distance: 20km
Target azimuth: 273°
Target elevation: 9°
Target altitude: 3.2km
Missile guidance method: TT (Three Point)

00:08:02, B-52G White-03 bombed Kinh No Complex.

00:08:45, V601P 5V27U Missile launched on Channel-2
Target distance: 12km
Target azimuth: 320°
Target elevation: 19°
Target altitude: 4km
Missile guidance method: TT (Three Point)


00:09:34, V601P 5V27U Missile launched on Channel-2
Target distance: 19km
Target azimuth: 351°
Target elevation: 10°
Target altitude: 3.6km
Missile guidance method: TT (Three Point)

00:09:37, B-52G Charcoal-01 bombed Yen Vien Railroad.
00:09:39, B-52G Charcoal-02 bombed Yen Vien Railroad.
00:09:41, B-52G Charcoal-03 bombed Yen Vien Railroad.
00:09:58, B-52G Rust-01 bombed Kinh No Complex.
00:10:11, B-52G Rust-02 bombed Kinh No Complex.

00:10:19, V601P 5V27U Missile launched on Channel-1
Target distance: 20km
Target azimuth: 20°
Target elevation: 8°
Target altitude: 3km
Missile guidance method: TT (Three Point)

00:10:20, B-52G Rust-03 bombed Kinh No Complex.
00:12:12, B-52G Ivory-01 bombed Yen Vien Railroad.
00:12:14, B-52G Ivory-02 bombed Yen Vien Railroad.
00:12:16, B-52G Ivory-03 bombed Yen Vien Railroad.
00:12:26, B-52G Black-01 bombed Kinh No Complex.
00:12:39, B-52G Black-02 bombed Kinh No Complex.
00:12:48, B-52G Black-03 bombed Kinh No Complex.

00:13:40, F-105 Wild Weasel number 1 of pair-1 launched AGM-45 Shrike missile.


00:13:48, SNR OFF THE AIR
-----------------

00:14:47, B-52G Ebony-01 bombed Yen Vien Railroad.
00:14:48, B-52G Ebony-02 bombed Yen Vien Railroad.
00:14:50, B-52G Ebony-03 bombed Yen Vien Railroad.

Total, SNR On Air Time: 12min 42sec

Posted By: Hpasp

Re: Bug reports - 09/11/12 05:59 AM

Originally Posted By: milang
here is my best try with resmone.exe result

image mode



I see only CPU overload here...
... click on "CPU" tab (second from left), then organize the "Processes" window by "Average CPU" (larger numbers at the top).
Do some screenshot while you experience the slowdown.

Also there are some peaks on the Hard disk, so click on "Disk" tab, then on the "Disk Activity" window and arrange it by "Total (B/sec)".
(higher on the top)
Do some screenshot while you see those peaks happening.
Posted By: farokh

Re: Bug reports - 09/11/12 07:34 AM

Originally Posted By: Hpasp


I see only CPU overload here...
... click on "CPU" tab (second from left), then organize the "Processes" window by "Average CPU" (larger numbers at the top).
Do some screenshot while you experience the slowdown.


Also there are some peaks on the Hard disk, so click on "Disk" tab, then on the "Disk Activity" window and arrange it by "Total (B/sec)".
(higher on the top)
Do some screenshot while you see those peaks happening.



consider your done sir....

from cpu tab



from disk tab
Posted By: Hpasp

Re: Bug reports - 09/11/12 07:59 AM

Originally Posted By: milang
Originally Posted By: Hpasp


I see only CPU overload here...
... click on "CPU" tab (second from left), then organize the "Processes" window by "Average CPU" (larger numbers at the top).
Do some screenshot while you experience the slowdown.


Also there are some peaks on the Hard disk, so click on "Disk" tab, then on the "Disk Activity" window and arrange it by "Total (B/sec)".
(higher on the top)
Do some screenshot while you see those peaks happening.



consider your done sir....

from cpu tab



from disk tab



Please do not skip the last steps, as these screenshots are valueless...

click on "CPU" tab (second from left), then organize the "Processes" window by clicking on "Average CPU" till the larger numbers on the top.

click on "Disk" tab, then on the "Disk Activity" window and arrange it by clicking on "Total (B/sec)" till higher numbers are on the top.
Posted By: montieris

Re: Bug reports - 09/11/12 08:33 AM

I noticed more like small micro 0.5sec lags.
edit;
Captured it with normal / lag period
Click to reveal..
Posted By: farokh

Re: Bug reports - 09/11/12 09:32 AM

here !

some picture from some situation.....
cpu average image mode

cpu average image mode with more detail

cpu average normal mode



disk mode




memory


is it done sir???
wounded
Posted By: Hpasp

Re: Bug reports - 09/11/12 09:54 AM

Do you have this kind of slowdown without using Digital Elevation Mesh?
Using DEM is the most CPU intensive with the Neva.

Can you measure processor heating?
Posted By: farokh

Re: Bug reports - 09/11/12 10:14 AM

Originally Posted By: Hpasp
Do you have this kind of slowdown without using Digital Elevation Mesh?
Using DEM is the most CPU intensive with the Neva.

Can you measure processor heating?


mr.hpasp... i always run sam simulator with digital elevation mesh!
of course i dont think so digital elevatios mesh do not conect to kill frame!
because everything in sam sim lagging after 9 or 10 minutes!!!! target aqouistion radar sceen... SNR tracking room screen and elevation scope also with instrument's! and target mark designator on yk-31m1 indicator!

also with dvina this lagging begin after 9 or 10 minute's too!

i have a big cooler on my CPU and when i run FSX simulator i do not feel my CPU going to warm heating measure!

u meant is.. SAM simulator more than FSX simulator take a more proccess from CPU screwy
with FSX + Hundred's addon's i Take more than 30 FPS !!!!!!!!!!!...........
...

Posted By: farokh

Re: Bug reports - 09/11/12 10:58 AM

Originally Posted By: montieris
I noticed more like small micro 0.5sec lags.
edit;
Captured it with normal / lag period
Click to reveal..


yes....
kill frame begin with 0.5s lags but when u still more time in sam sim around 15minute's u feel kill frame within with 0.7 or 0,8 lags sigh when u want search for tracking target on scope's!!.......
Posted By: Hpasp

Re: Bug reports - 09/11/12 01:14 PM

Originally Posted By: milang
Originally Posted By: Hpasp
Do you have this kind of slowdown without using Digital Elevation Mesh?
Using DEM is the most CPU intensive with the Neva.

Can you measure processor heating?


mr.hpasp... i always run sam simulator with digital elevation mesh!
of course i dont think so digital elevatios mesh do not conect to kill frame!
because everything in sam sim lagging after 9 or 10 minutes!!!! target aqouistion radar sceen... SNR tracking room screen and elevation scope also with instrument's! and target mark designator on yk-31m1 indicator!

also with dvina this lagging begin after 9 or 10 minute's too!

i have a big cooler on my CPU and when i run FSX simulator i do not feel my CPU going to warm heating measure!

u meant is.. SAM simulator more than FSX simulator take a more proccess from CPU screwy
with FSX + Hundred's addon's i Take more than 30 FPS !!!!!!!!!!!...........
...



1, Do you have this kind of slowdown without using Digital Elevation Mesh?
Please try it without Digital Elevation Mesh, and see if the problem appears!
(It would be important to find this out)

2, Can you measure processor (over) heating?
It would be important to see how CPU temperature is rising degree by degree, to find out if there is some correlation to CPU heating and slowing down.
Some processors are slowing down, if CPU core temperature reaches some level...
Posted By: montieris

Re: Bug reports - 09/11/12 04:50 PM

This is weird, i tried now and it lags immediately and randomly with 3 sec duration.
Also got disc activity from sam.exe
Laptop was just turned on, temps in HWMonitor are low.

Click to reveal..


Posted By: Hpasp

Re: Bug reports - 09/11/12 05:42 PM

Originally Posted By: montieris
This is weird, i tried now and it lags immediately and randomly with 3 sec duration.
Also got disc activity from sam.exe
Laptop was just turned on, temps in HWMonitor are low.

Click to reveal..




And if you try without Digital Elevation Mesh?

Could you please check your Windows Performance Index?
Mine development system has: 5,9 (CPU:7,5 RAM: 7,6 Video: 7,3 Video 3D: 7,3 HDD: 5,9)
Intel Core i7 860 @ 2.8Ghz, 4Gb RAM

I will try to test it in my nootebook, with a way lower performance of 3,9 (CPU: 5.0 RAM: 5.0 Video: 3.9 Video 3D: 4.9 HDD: 5.1)
Intel Core2 Duo T7250 @ 2.0Ghz, 4Gb RAM
Posted By: montieris

Re: Bug reports - 09/11/12 06:29 PM

Forgot to type, that report was without Digital Elevation Mesh..
Not sure if changing this does something, sam.exe hangs anyway.

What is more weird;
Now all sam systems does hang on any scenario, Dvina and Volhov does hang a bit less, Krug screen goes black and hangs up completely after i click on turbine button, Vega hangs similarly like Neva. When i click on any button in simulator - sam.exe hangs for 3 sec.


edit;
Laptop specs; CPU C2D T9400 2.53ghz, 6GB RAM, GeForce M9600GT, HDD 7200rpm
WinExp score; 5,9 (cpu 6,2 ram 6,2 graphics 6,5 and 6,5 hdd 5,9)

Also CPU throttling doesn't matter, i tested SAMSIM with SuperPI calculation in background (to have 100% cpu load), SAMSIM still does hang(no cpu calculation); periodically and when i press any button.

edit2; fixed second screenshot

Should i just reinstall SAMSIM or keep bughunt?

Click to reveal..

Screenshots with Krug hanged;

Posted By: Hpasp

Re: Bug reports - 09/11/12 06:45 PM

Uninstall, delete folder, download, reinstall...
biggrin
Posted By: farokh

Re: Bug reports - 09/11/12 06:50 PM

guy's !!!!.......

edit: my cpu is a monster! AMD phenom II 1090 3.4ghz
+ ATI 5700 1GB + 2GB corsair GT ram (OC ready)


here is my test result!

CPU temperature with DEM is ON!

PS: i begin recording for 13min and 21s still my proccess staying in sam sim, u can check my elapsed time still down right of screen

i record my degree by degree with checker aida64 program




CPU temperature without DEM.. DEM was OFF

i feel again lagging without DEM too sigh

Posted By: WhoCares

Re: Bug reports - 09/11/12 09:38 PM

Discovered this little gem yesterday and I am very much enjoying it.
So far I primarily focus on the SA-75M Dvina with its fairly simple interface. By now I am reasonably familiar with it in the training, also reaching SNR Air times below 1min (for a single target).
As such I felt prepared for the challenge to start a historical engagement and selected the Sverdlovsk U2 as my target. Looking at the plotting board (screenshot, from base Kosulino), and if I understand the manual correctly (copied into the screenshot), I see three enemy flights:

5701: 1 Enemy 20.5km altitude, ~48km distance 219°
5702: 1 Enemy @20km altitude ~62km distance 210°
5703: 2 Enemies @11km altitude, ~75km distance 268°

Well, some Mig and Su pilots were a bit unfortunate to become subject of my confusion...

I would expect friendlies to be identified as such (1x, 5x) or if no IFF is available, then 9x.

Click to reveal..
08:46 1st of May 1960
CIA Operation Grand Slam.

SA-75M Dvina


+++++++++++++++++
00:01:24, SNR ON AIR


00:01:58, V-750VU 11DU Missile launched on Channel-1
Target distance: 34km
Target azimuth: 229°
Target elevation: 34°
Target altitude: 19.7km
SNR mode: 55km
Missile guidance method: K (Half Lead Elevated By Constans)


00:02:35, Missile exploded on Channel-1
Su-9 killed by SAM. (miss distance: 70m)

00:02:38, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 1min 8sec
Posted By: max2012

Re: Bug reports - 09/12/12 12:02 AM


How to shoot down U2 with Dvina!

Very simply there are three objectives of our 2 MIG and SU and that U2

The question how to find, explain. look at the design parameters Speeds

U2 is very little speed of 150 m/s

Mig and Su speed of 300 m/s

So attention to the Speed Targets!

How to find the target with a speed of 150 m/s display on the instruments V in the

U2 flies at an altitude of 20 km, but at a low speed of 150 m/s!

So it's available!

I also like the earlier you shoot down this SU-9
Posted By: piston79

Re: Bug reports - 09/12/12 04:50 AM

Quote:
I would expect friendlies to be identified as such (1x, 5x) or if no IFF is available, then 9x.


In fact, this event happens on 1-th of may, which is the international day of workers/labor and it was huge celebration in comunists countries. Most of the military personel was free of charge, and they forgot to change IFF codes for the 1-th of May, so that's why fighters are seen like "unfrendly" aircraft.


MAX2012 explained how you can distinguished targets (speed selection...) wink So, our posts should be moved to SA-75M/MK (SA-2F) section by the moderator...
Posted By: WhoCares

Re: Bug reports - 09/12/12 10:07 AM

Thanks both of you, piston79 for the perfect explanation of my observation on the plotting board, and max2012 to improve my target identification skill thumbsup
When I thought I might spice the report up with a "successful" friendly fire report, it happened to me that I scored multiple times in a row on the U2; in that process it already dawned on me that the speed indicator might hint me to the right target. The proximity and occasionally crossing path of Su-9 and U-2 does not help in the process, sometimes having both on both azimuth and elevation screens. That also explains the fast target accuisition in my example, as I already knew where to point the dishes before going active bump
I guess I will have to prepare me some reference tables on target speeds and system characteristics; I am not that versed i Cold War tech...

Regarding moving the posts - we should actually hide/delete them to make sure that all n00bs fall into this "trap" to realise how detailed the sim and the scenarios really are - so far this seems to have worked pretty well, as I searched the forum for information on the scenario and this "problem", but found nothing wink
Posted By: Hpasp

Re: Bug reports - 09/21/12 05:51 PM

SAMSIM not only tries to simulate the actual SAM systems "Realistic to the Switch", but also tries to simulate the "Fog of War"!!!

Over Sverdlovsk, the Soviet IFF system completely failed, and SAM operators were under intense pressure to shot anything that flies...
... they done it.

Over Libya the switched off P-14 radar at Tripoli caused the IADS not to show the real targets...
... all SAMs are failed.

Over Serbia, the Plotting Board never indicated any Stealth planes, only the batteries P18 detected it, causing confusion.
Col. Zoltan Dani "I see a plane at ..."
HQ "Are you sure? We do not see anything there"
Col. Zoltan Dani "I see it, and I assume its enemy"
HQ "Please repeat position!"
Col. Zoltan Dani "Can I fire on it?"
...

These are REAL historical traps.
biggrin
Posted By: farokh

Re: Bug reports - 09/21/12 06:57 PM

Originally Posted By: Hpasp

Col. Zoltan Dani "I see a plane at ..."
HQ "Are you sure? We do not see anything there"
Col. Zoltan Dani "I see it, and I assume its enemy"
HQ "Please repeat position!"
Col. Zoltan Dani "Can I fire on it?"
...


what a Effective sentence reading like a Cinematic famous dialog jamesbond
Posted By: jazjar

Re: Bug reports - 09/29/12 07:46 PM

So... Anybody look in to the SA-3 bugs?
Posted By: farokh

Re: Bug reports - 09/29/12 08:09 PM

Originally Posted By: jazjar
So... Anybody look in to the SA-3 bugs?


almost sa-3 bug is fixed also that bug where when u launch missile ... your missile was missed... but its fixed right now

of course lagging bug is still alive frown
Posted By: jazjar

Re: Bug reports - 09/30/12 05:00 AM

Hey, is there a randomness variable inserted when the SA-3 is fired at targets that are jamming with the ALE-50 decoy? I just woke up today after a long nap, fired up SAM simulator, picked OAF scenario 2, did the northernwestern most battery, ( 2/250rd) I believe? Shot the F-16 coming in from the northeast of that battery down in one shot, one shot at about 15km. I tried the same thing over and over again and it kept hitting the decoy, hitting the decoy, I shot at ~15km over and over again, but couldn't make that shot. And yes, Hpasp, I know you are dissapointed that we're not trying for the stealth aircraft, but for me, I just complete my challenges in order from easiest to toughest:)
Posted By: piston79

Re: Bug reports - 09/30/12 05:30 AM

Originally Posted By: milang

of course lagging bug is still alive frown


I think it has something common with paging file of Windows...
Posted By: farokh

Re: Bug reports - 09/30/12 09:24 AM

Originally Posted By: piston79
Originally Posted By: milang

of course lagging bug is still alive frown


I think it has something common with paging file of Windows...


i dont know nope

hpasp do not feel this bug but... me and you and montieris feel this bug after 9 or 10 minutes .... confused
It is strange bug

also when lagging begin....when i push f4 key... the lagging going to high level...........
Posted By: montieris

Re: Bug reports - 09/30/12 09:36 AM

Originally Posted By: milang

of course lagging bug is still alive


Just reinstall SAM SIM
Posted By: farokh

Re: Bug reports - 09/30/12 09:50 AM

Originally Posted By: montieris
Originally Posted By: milang

of course lagging bug is still alive


Just reinstall SAM SIM


are u sure with reinstall bug fixed?????
Posted By: montieris

Re: Bug reports - 09/30/12 10:22 AM

Probably not. Just don't use S-125 in Linebacker II.

That bug caused more severe corruption/lags for all sam systems, only fix was to reinstall. (see posts before)
Posted By: max2012

Re: Bug reports - 10/17/12 02:55 AM


Asuluk training ground.

Practice target:
RM-217 Zvezda [program-1] simulating Tornado

S-75M3 Volkhov


00:00, Practice target RM-217 Zvezda [program-1] simulating Tornado launched

+++++++++++++++++
00:00:05, SNR ON AIR


00:00:56, V-755 20DSU Missile launched on Channel-1
Target distance: 31km
Target azimuth: 94°
Target elevation: 6°
Target altitude: 3,5km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: K (Half Lead Elevated By Constans)


00:01:23, Missile exploded on Channel-1
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 19m)

Total, SNR On Air Time: 1min 57sec





Posted By: max2012

Re: Bug reports - 10/17/12 02:58 AM


Everywhere different target height

1. In the Report of 3.5 km.

2. In SAM 100 meters.

3. in 3D Report 338 meters.

Question so what is the height?
Posted By: piston79

Re: Bug reports - 10/17/12 06:38 AM

Originally Posted By: max2012

Everywhere different target height
1. In the Report of 3.5 km.
2. In SAM 100 meters.
3. in 3D Report 338 meters.
Question so what is the height?


338 meters... You can see it from 3DAAR of the TARGET TRACK!!!

Also in the old forum, this issue was discussed:
http://simhq.com/forum/ubbthreads.php/topics/3539199/Re_SAM_Simulator.html#Post3539199
http://simhq.com/forum/ubbthreads.php/topics/3535966/Re_SAM_Simulator.html#Post3535966

Hpasp said:
http://simhq.com/forum/ubbthreads.php/topics/3539451/Re_SAM_Simulator.html#Post3539451
Posted By: max2012

Re: Bug reports - 10/17/12 12:13 PM


I knew already that the example of the same "Tornado" at 300 meters, although in itself written

H = 100 m!

With Volkhov everywhere on small targets problem.

Well, I guess now it Hpasp generally better not to touch it, because it makes the "Shilka"

I think it is not necessary to unnerve Hpasp

And so he is now on the nerves of all this Shilka!
Posted By: farokh

Re: Bug reports - 10/17/12 02:44 PM

Originally Posted By: max2012

I knew already that the example of the same "Tornado" at 300 meters, although in itself written

H = 100 m!

With Volkhov everywhere on small targets problem.

Well, I guess now it Hpasp generally better not to touch it, because it makes the "Shilka"

I think it is not necessary to unnerve Hpasp

And so he is now on the nerves of all this Shilka!


this bug is one of them !
but we had to wait until mr.HPasp release next version and then .... we start to find that bug's is still alive thumbsup
Posted By: oban21

Re: Bug reports - 11/04/12 09:35 AM

Hello Everybody! wave Im "new" to this form (vell relatyvly speaking,as a registered member at lest) and just wants to say hello to evrybody who shares admiration to and enjoymanet in this beautifull little sim of our Hungarian friend (and my "neibhor", Im from Serbia) Hpasp! wave2 GREAT WORK!!!thumbsup I have allready done some "achivements" biggrin by counqering this wonderfull, but little bit strange and hard-to-learn russian technique, in missions like "Linenbeaker II" by downing both SR-71's with dvina (boy that was hard!!!), which im going to post here if somebody's like to see it! Now, I heave encountered a real problem whit this Sim,also!It's about my favorith SA-5 Gammon! I just can't shoot a single missile in Hungarian scenario beacouse the firing buttons are complitly DEAD in it! I understand that it's a training mission whit no real rockets meant to be launch, as I've allredy play it whit "dvina`s" and "volkhov`s"! And it`s preatty annoying, mad I must say, beacouse there wasn`t a word about procedure for that mission in manual for sa-5! Neither was there anything that I could find about it on this forum. sigh So if anybody could help...I will appreciate it,greatly!;) See you guys and... sorry for bad English!:(
Posted By: piston79

Re: Bug reports - 11/04/12 03:45 PM

You cannot shoot at Hungary, period!
Posted By: Hpasp

Re: Bug reports - 11/04/12 04:07 PM

Originally Posted By: oban21
Hello Everybody! wave Im "new" to this form (vell relatyvly speaking,as a registered member at lest) and just wants to say hello to evrybody who shares admiration to and enjoymanet in this beautifull little sim of our Hungarian friend (and my "neibhor", Im from Serbia) Hpasp! wave2 GREAT WORK!!!thumbsup I have allready done some "achivements" biggrin by counqering this wonderfull, but little bit strange and hard-to-learn russian technique, in missions like "Linenbeaker II" by downing both SR-71's with dvina (boy that was hard!!!), which im going to post here if somebody's like to see it! Now, I heave encountered a real problem whit this Sim,also!It's about my favorith SA-5 Gammon! I just can't shoot a single missile in Hungarian scenario beacouse the firing buttons are complitly DEAD in it! I understand that it's a training mission whit no real rockets meant to be launch, as I've allredy play it whit "dvina`s" and "volkhov`s"! And it`s preatty annoying, mad I must say, beacouse there wasn`t a word about procedure for that mission in manual for sa-5! Neither was there anything that I could find about it on this forum. sigh So if anybody could help...I will appreciate it,greatly!;) See you guys and... sorry for bad English!:(


As this is quite an interesting question, I will answer it at the relevant topic...
http://simhq.com/forum/ubbthreads.php/topics/3675106/Re_S_200VE_Vega_E_SA_5B_Gammon.html#Post3675106
Posted By: piston79

Re: Bug reports - 11/08/12 05:47 AM

A question:

When SAMSim stops generating info about the 3D AAR? When all targets gone or hit the ground?
Posted By: Hpasp

Re: Bug reports - 11/08/12 08:16 AM

Originally Posted By: piston79
A question:

When SAMSim stops generating info about the 3D AAR? When all targets gone or hit the ground?


It collects the info in memory, and only writes it out into the disk when you stop the situation.
Posted By: farokh

Re: Bug reports - 11/08/12 08:32 AM

hpasp... i guess i finde a little bug ...
i choose one A-6 with dm/cm jammer on ashuluk target.. as i see 2 missile explode near target but in AAR no where wrote hit or killed


aar

Click to reveal..
Asuluk training ground.

Practice target:
LA-17MV [Program-2] simulating A-6 Intruder

SA-75M Dvina


00:00, Practice target LA-17MV [Program-2] simulating A-6 Intruder launched

+++++++++++++++++
00:00:31, SNR ON AIR


00:02:57, V-750VU 11DU Missile launched on Channel-2
Target distance: 20km
Target azimuth: 72°
Target elevation: 0°
Target altitude: 130m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:03, V-750VU 11DU Missile launched on Channel-1
Target distance: 20km
Target azimuth: 68°
Target elevation: 0°
Target altitude: 145m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:08, V-750VU 11DU Missile launched on Channel-3
Target distance: 20km
Target azimuth: 64°
Target elevation: 0°
Target altitude: 163m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:19, Missile exploded on Channel-3

00:03:30, V-750VU 11DU Missile launched on Channel-3
Target distance: 20km
Target azimuth: 28°
Target elevation: 0°
Target altitude: 226m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:41, Missile exploded on Channel-3

00:03:47, V-750VU 11DU Missile launched on Channel-1
Target distance: 20km
Target azimuth: 357°
Target elevation: 0°
Target altitude: 260m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:04:40, V-750VU 11DU Missile launched on Channel-2
Target distance: 20km
Target azimuth: 293°
Target elevation: 0°
Target altitude: 107m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:04:51, Missile exploded on Channel-2

Total, SNR On Air Time: 4min 40sec



3daar
https://rapidshare.com/files/955032561/3DAAR-2002-12-07_22-57-01.gpx
Posted By: Alien_MasterMynd

Re: Bug reports - 11/08/12 09:57 AM

You attacked a jamming target? Why did not you enable I-87V? What was the fuse setting, it was K3, wasn't it? Why the target is at the same distance all the time? This should be solved by enabling I-87V, normal T/T mode is not sufficient.
Posted By: piston79

Re: Bug reports - 11/08/12 10:15 AM

Originally Posted By: Alien_MasterMynd
You attacked a jamming target? Why did not you enable I-87V? What was the fuse setting, it was K3, wasn't it? Why the target is at the same distance all the time? This should be solved by enabling I-87V, normal T/T mode is not sufficient.


SA-75M Dvina....

The problem is that 3Daar looks realy strange, please, compare it with the AAR. Look at where missiles exploded....
Posted By: piston79

Re: Bug reports - 11/08/12 10:22 AM

Quote:
It collects the info in memory, and only writes it out into the disk when you stop the situation.


So, I have a problem... I made a try to repeat the Milang's situation described above. Used 3 missiles, first and second exploded near the target, it falls on the ground, waited untill third missile reached the range boresight and exploded, then stopped the SIM.
When checking the 3DAAR it stops when the target hits the ground (third missile ws on the halfway to the it's crash site).

Where could be the problem, somthing with computer's memory??? Or it just stopping collecting data after no target is available???
Posted By: Alien_MasterMynd

Re: Bug reports - 11/08/12 10:26 AM

Originally Posted By: piston79

SA-75M Dvina....
The problem is that 3Daar looks realy strange, please, compare it with the AAR. Look at where missiles exploded....


Sorry, faster thinking than reading nope
Posted By: piston79

Re: Bug reports - 11/08/12 10:49 AM

I am suffering the same dessease.. wink
Posted By: farokh

Re: Bug reports - 11/08/12 12:10 PM

Originally Posted By: Alien_MasterMynd
You attacked a jamming target? Why did not you enable I-87V? What was the fuse setting, it was K3, wasn't it? Why the target is at the same distance all the time? This should be solved by enabling I-87V, normal T/T mode is not sufficient.


dude... i work with sa-2F not sa-2E... dvina do not armed with i-87v! banghead
Posted By: Hpasp

Re: Bug reports - 11/08/12 02:45 PM

Originally Posted By: milang
hpasp... i guess i finde a little bug ...
i choose one A-6 with dm/cm jammer on ashuluk target.. as i see 2 missile explode near target but in AAR no where wrote hit or killed


aar

Click to reveal..
Asuluk training ground.

Practice target:
LA-17MV [Program-2] simulating A-6 Intruder

SA-75M Dvina


00:00, Practice target LA-17MV [Program-2] simulating A-6 Intruder launched

+++++++++++++++++
00:00:31, SNR ON AIR


00:02:57, V-750VU 11DU Missile launched on Channel-2
Target distance: 20km
Target azimuth: 72°
Target elevation: 0°
Target altitude: 130m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:03, V-750VU 11DU Missile launched on Channel-1
Target distance: 20km
Target azimuth: 68°
Target elevation: 0°
Target altitude: 145m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:08, V-750VU 11DU Missile launched on Channel-3
Target distance: 20km
Target azimuth: 64°
Target elevation: 0°
Target altitude: 163m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:19, Missile exploded on Channel-3

00:03:30, V-750VU 11DU Missile launched on Channel-3
Target distance: 20km
Target azimuth: 28°
Target elevation: 0°
Target altitude: 226m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:41, Missile exploded on Channel-3

00:03:47, V-750VU 11DU Missile launched on Channel-1
Target distance: 20km
Target azimuth: 357°
Target elevation: 0°
Target altitude: 260m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:04:40, V-750VU 11DU Missile launched on Channel-2
Target distance: 20km
Target azimuth: 293°
Target elevation: 0°
Target altitude: 107m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:04:51, Missile exploded on Channel-2

Total, SNR On Air Time: 4min 40sec



3daar
https://rapidshare.com/files/955032561/3DAAR-2002-12-07_22-57-01.gpx


These missiles were popped by the ground echo.
You simply cannot engage targets reliably below 300m with radio proxy.
(check manual page 29)

This is why USU was developed for the Volhov.

The flags on the target path are bugs.
Posted By: piston79

Re: Bug reports - 11/08/12 05:05 PM

Originally Posted By: milang
Originally Posted By: Alien_MasterMynd
You attacked a jamming target? Why did not you enable I-87V? What was the fuse setting, it was K3, wasn't it? Why the target is at the same distance all the time? This should be solved by enabling I-87V, normal T/T mode is not sufficient.


dude... i work with sa-2F not sa-2E... dvina do not armed with i-87v! banghead


"Dude", I already corrected Alien Mastermind, no need to repeat and please keep your headbanging emotion for yourself... You are the guy which cannot handle "Dvina", not AlienMastermind... So stay quite! Thanks!
Posted By: max2012

Re: Bug reports - 11/08/12 05:47 PM


Dvina is my favorite system, so please don't hurt her!
Posted By: max2012

Re: Bug reports - 11/08/12 05:50 PM


But something that bugs in the emulator, well so and so clear without mistakes can not be more than one Program.

And I realized if tiak lower than 300 meters, use RAB po K3 at the 18 km distance.
Posted By: max2012

Re: Bug reports - 11/08/12 05:55 PM


Sorry for the one that the Shilka will not be available at the test site in Ashuluk!

Could make a bit boring in Ashuluk I was wondering down a Tomahawk missile!
Posted By: farokh

Re: Bug reports - 11/08/12 06:18 PM

Originally Posted By: milang

"Dude", I already corrected Alien Mastermind, no need to repeat and please keep your headbanging emotion for yourself... You are the guy which cannot handle "Dvina", not AlienMastermind... So stay quite! Thanks!


dont tell me what i should doing in here sweet boy.....

Click to reveal..
2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Tripoli.

Targets:
Bab al-Aziziyah barracks - 6 F-111F Aardvark, each armed with 4 GBU-10 LGB
Murat Sidi Bilal Naval base - 3 F-111F Aardvark, each armed with 4 GBU-10 LGB
Tripoli AFB - 5 F-111F Aardvark, each armed with 12 Mk.82/BSU-49 high-drag bombs

Supporting force:
6 A-7E Corsair-II SEAD (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
4 F-14A Tomcat CAP (VF-33 Starfighters, VF-102 Diamondbacks from the CV-66 USS America)
3 EF-111A Raven ECM
1 EA-6B Prowler ECM (VMAQ-2 Playboys from the CV-43 USS America)

SA-75M Dvina

00:00:36, F-111F Remit-31 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.

+++++++++++++++++
00:00:42, SNR ON AIR


00:01:00, A-7E Corsair-II No.1, VA-46 Clansmen launched AGM-88 HARM missile No. 1


00:01:10, V-750VKU 11DKU Missile launched on Channel-1
Target distance: 17km
Target azimuth: 354°
Target elevation: 0°
Target altitude: 50m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:01:16, V-750VKU 11DKU Missile launched on Channel-2
Target distance: 17km
Target azimuth: 359°
Target elevation: 0°
Target altitude: 49m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:01:37, Missile exploded on Channel-1
F-111F Remit-33 killed by SAM. (miss distance: 38m)

00:01:52, V-750VKU 11DKU Missile launched on Channel-1
Target distance: 19km
Target azimuth: 24°
Target elevation: 0°
Target altitude: 182m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:02:08, Missile exploded on Channel-1
AGM-88 (HARM) High Speed Anti Radiation Missile No. 1 launched from A-7E Corsair-II No.1, VA-46 Clansmen killed by SAM. (miss distance: 105m)

00:02:13, A-7E Corsair-II No.2, VA-46 Clansmen launched AGM-88 HARM missile No. 1


00:02:28, V-750VKU 11DKU Missile launched on Channel-2
Target distance: 28km
Target azimuth: 0°
Target elevation: 4°
Target altitude: 2.1km
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:19, V-750VKU 11DKU Missile launched on Channel-3
Target distance: 19km
Target azimuth: 352°
Target elevation: 0°
Target altitude: 50m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:43, SNR knocked out by HARM


00:03:45, SNR OFF THE AIR
-----------------


00:03:46, Missile exploded on Channel-3
F-111F Karma-51 killed by SAM. (miss distance: 39m)

Total, SNR On Air Time: 3min 3sec


Posted By: Hpasp

Re: Bug reports - 11/08/12 07:15 PM

Originally Posted By: milang
Originally Posted By: milang

"Dude", I already corrected Alien Mastermind, no need to repeat and please keep your headbanging emotion for yourself... You are the guy which cannot handle "Dvina", not AlienMastermind... So stay quite! Thanks!


dont tell me what i should doing in here sweet boy.....

Click to reveal..
2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Tripoli.

Targets:
Bab al-Aziziyah barracks - 6 F-111F Aardvark, each armed with 4 GBU-10 LGB
Murat Sidi Bilal Naval base - 3 F-111F Aardvark, each armed with 4 GBU-10 LGB
Tripoli AFB - 5 F-111F Aardvark, each armed with 12 Mk.82/BSU-49 high-drag bombs

Supporting force:
6 A-7E Corsair-II SEAD (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
4 F-14A Tomcat CAP (VF-33 Starfighters, VF-102 Diamondbacks from the CV-66 USS America)
3 EF-111A Raven ECM
1 EA-6B Prowler ECM (VMAQ-2 Playboys from the CV-43 USS America)

SA-75M Dvina

00:00:36, F-111F Remit-31 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.

+++++++++++++++++
00:00:42, SNR ON AIR


00:01:00, A-7E Corsair-II No.1, VA-46 Clansmen launched AGM-88 HARM missile No. 1


00:01:10, V-750VKU 11DKU Missile launched on Channel-1
Target distance: 17km
Target azimuth: 354°
Target elevation: 0°
Target altitude: 50m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:01:16, V-750VKU 11DKU Missile launched on Channel-2
Target distance: 17km
Target azimuth: 359°
Target elevation: 0°
Target altitude: 49m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:01:37, Missile exploded on Channel-1
F-111F Remit-33 killed by SAM. (miss distance: 38m)

00:01:52, V-750VKU 11DKU Missile launched on Channel-1
Target distance: 19km
Target azimuth: 24°
Target elevation: 0°
Target altitude: 182m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:02:08, Missile exploded on Channel-1
AGM-88 (HARM) High Speed Anti Radiation Missile No. 1 launched from A-7E Corsair-II No.1, VA-46 Clansmen killed by SAM. (miss distance: 105m)

00:02:13, A-7E Corsair-II No.2, VA-46 Clansmen launched AGM-88 HARM missile No. 1


00:02:28, V-750VKU 11DKU Missile launched on Channel-2
Target distance: 28km
Target azimuth: 0°
Target elevation: 4°
Target altitude: 2.1km
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:19, V-750VKU 11DKU Missile launched on Channel-3
Target distance: 19km
Target azimuth: 352°
Target elevation: 0°
Target altitude: 50m
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:03:43, SNR knocked out by HARM


00:03:45, SNR OFF THE AIR
-----------------


00:03:46, Missile exploded on Channel-3
F-111F Karma-51 killed by SAM. (miss distance: 39m)

Total, SNR On Air Time: 3min 3sec




Please cool down emotions...
00:03:43, SNR knocked out by HARM
... Dvina after hit:


Posted By: piston79

Re: Bug reports - 11/08/12 07:51 PM

Probably must be moved in another topic (and I'll delete this post)... Where is this - Lybia, Iraq?
Posted By: Alien_MasterMynd

Re: Bug reports - 11/08/12 09:58 PM

"Nice" picture, missing antenna is fascinating jawdrop Hpasp, you have a great inventory of interesting pictures.

PS: I'll delete my post also when it is moved.
Posted By: Mdore

Re: Bug reports - 11/23/12 11:58 AM

Very minor SA-4 / 2K11 Krug possible inaccuracy.

I've just watched this video. http://www.youtube.com/watch?v=My0Xr-ITrW8

At the 0:42 second mark you can see the operator selecting targets.

Pay VERY close attention to how the joystick and the cursor move together. SAM Simulator does it wrong.

In SAM Simulator, if you move the imaginary joystick a little bit to the left, the cursor will move slowly to the left and will keep moving even when the stick isn't being moved any more. The cursor only stops moving when the imaginary joystick is put back into the middle position.

But in the video the stick and the cursor seem to work differently. Moving the joystick to the right puts the cursor to the right immediately, and it stays where the joystick is. Then when the stick is moved forward, the cursor moves to the top of the scope immediately following the position of the joystick.

A very minor point, and maybe different 2K11 versions worked differently. But I thought I should point it out. Maybe you did it this way on purpose?
Posted By: Mdore

Re: Bug reports - 12/06/12 09:15 AM

Another possible bug in the SA-2F.

If you launch a missile with the proximity fuse off and with the switch in the approaching target position, and then after launch you move the switch to the receding target position, I think the missile is still detonating like it was set to detonate on approaching targets. And vice versa.

I'm not sure if this is a bug or if it's how the system works. But I thought I'd mention it.
Posted By: piston79

Re: Bug reports - 12/06/12 09:33 AM

Originally Posted By: Mdore

If you launch a missile with the proximity fuse off and with the switch in the approaching target position, and then after launch you move the switch to the receding target position, I think the missile is still detonating like it was set to detonate on approaching targets. And vice versa.


How you see the type of detonation (receiding/approaching)???
Posted By: Hpasp

Re: Bug reports - 12/06/12 09:41 AM

Originally Posted By: Mdore
Another possible bug in the SA-2F.

If you launch a missile with the proximity fuse off and with the switch in the approaching target position, and then after launch you move the switch to the receding target position, I think the missile is still detonating like it was set to detonate on approaching targets. And vice versa.

I'm not sure if this is a bug or if it's how the system works. But I thought I'd mention it.


We have only K1/2/3 commands with the Dvina system, so proximity fuse setting can never be changed, during missile flight.
(This feature would give a great opportunity for enemy jammers)

Fuse settings can be changed, while the missile is connected to the launcher via the OS-10 connector only.
Posted By: piston79

Re: Bug reports - 12/06/12 11:29 AM

Originally Posted By: Hpasp

We have only K1/2/3 commands with the Dvina system, so proximity fuse setting can never be changed, during missile flight.
(This feature would give a great opportunity for enemy jammers)

Fuse settings can be changed, while the missile is connected to the launcher via the OS-10 connector only.


But as "Rabota po K3" switch just controls the delay of K3 command, it should be changeable 'till the sending on K3 command..
Did I missed something in my education?... screwy
Posted By: max2012

Re: Bug reports - 12/06/12 07:01 PM


I had previously thought that the K3 is to ensure that at the time when the missile is in flight it controlled remotely!

Due to the fact that the target of the low and the rocket crashes into the ground.
Posted By: max2012

Re: Bug reports - 12/06/12 07:04 PM


As I understand the K3 must be used if the Dvina have objective flies lower than 300 meters, is a good example of the Tomahawk cruise missile and a short-range order in the 20 km.

Is this true or not?
Posted By: piston79

Re: Bug reports - 12/06/12 07:17 PM

Originally Posted By: Mdore
Another possible bug in the SA-2F.
If you launch a missile with the proximity fuse off and with the switch in the approaching target position, and then after launch you move the switch to the receding target position, I think the missile is still detonating like it was set to detonate on approaching targets. And vice versa.
I'm not sure if this is a bug or if it's how the system works. But I thought I'd mention it.


Hi, I did a little test with SA-2F...

Ashuluk training ground, 3 radar reflectors, missiles are launched one against each target.
Fuse settings where as follows:
1 - "Dogon"
2 - "Rabota po K3"
3 - "Dogon", changed on "Rabota po K3" during flight...

Here the 3DAAR:

Click to reveal..





Second test was the same, but with 4 missiles against 3 targets and the fuse settings was not changed during flight (the sequence starts again with "Dogon", than "Rabota po K3" and so on...).

Here the second 3D AAR screenshots:

Click to reveal..






As debries pattern should looks like this:

Click to reveal..

please, share your opinion about realistic behaviour of the K3 command detonation of the warhead...

PS. Due to poor quality of screenshots, i wish to mention that all measurments are in meters...
Posted By: Hpasp

Re: Bug reports - 12/06/12 07:32 PM

Originally Posted By: piston79
Originally Posted By: Hpasp

We have only K1/2/3 commands with the Dvina system, so proximity fuse setting can never be changed, during missile flight.
(This feature would give a great opportunity for enemy jammers)

Fuse settings can be changed, while the missile is connected to the launcher via the OS-10 connector only.


But as "Rabota po K3" switch just controls the delay of K3 command, it should be changeable 'till the sending on K3 command..
Did I missed something in my education?... screwy


Just do not mix Dvina with Volhov.

At Volhov, the length of the K4 command will set the delay timer of warhead, after receiving the K3 command.
At the Dvina, the delay is fixed on the launcher, as Dvina has no K4 command, only K3 (detonate with the timer set on the launcher).
Posted By: Alien_MasterMynd

Re: Bug reports - 12/07/12 10:47 AM

So the K3 command (when in RABOTA PO K3) is sent at the exact time regardless of DOGON mode. The actual delay is provided in the warhead timer (and set before flight, when the missile is on launcher), right?
Posted By: piston79

Re: Bug reports - 12/07/12 11:13 AM

Originally Posted By: Alien_MasterMynd
So the K3 command (when in RABOTA PO K3) is sent at the exact time regardless of DOGON mode. The actual delay is provided in the warhead timer (and set before flight, when the missile is on launcher), right?


That's what Hpasp said, but I am not sure about that....

Here comprasion between modes in SA-2F and SA-2E:
Quote:
At the Volhov, you have these methods...
ZEMLJA - ground - detonate missile by command
STAN - arm the fuse 300m before the range boresight - detonate by radio proxy fuse
RAB PO ADA - against spy balloons - detonate missile by command, well before the target
ZAGRUB RV - reduce fuse sensitivity to avoid detonation by chaff
ZAGRUB RV USU - reduce fuse sensitivity to avoid detonation by chaff with USU missiles
NLC USU - gate fuse sensitivity to 100m against low flying targets
NC USU - used with nuclear missiles
RAB OT VM - arm the fuse 11sec after launch - detonate by radio proxy fuse
RAB PO K3 - detonate missile by K3 command

At the Dvina, you have these methods...
ZEMLJA - ground - detonate missile by command
RAB PO ADA - against spy balloons - detonate missile by command, well before the target
11 SEC - arm the fuse 11sec after launch - detonate by radio proxy fuse
RAB OT RV - arm the fuse 300m before the range boresight - detonate by radio proxy fuse
RAB PO K3 - detonate missile by K3 command for incoming targets - used against low flying targets
DOGON - detonate missile by K3 command for receding targets (Dvina has no K4 command to transmit the missile/target closure speed)


Here also about SA-2E:

http://simhq.com/forum/ubbthreads.php/topics/3388928/Re_SAM_Simulator.html#Post3388928

And here - TOTALY DIFFERENT explanation about "Dogon" an "Rabota on K3" for SA-2F:

http://simhq.com/forum/ubbthreads.php/topics/3494150/Re_SAM_Simulator.html#Post3494150
Posted By: piston79

Re: Bug reports - 01/03/13 09:13 PM

I have a strange feeling about SA-4... Check this 3D AAR:

Click to reveal..
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<gpx xmlns="http://www.topografix.com/GPX/1/1">

<wpt lat="47.390250" lon="48.252803">
<ele>18252</ele>
<time>2012-01-01T00:04:10Z</time>
<name>Missile exploded</name>
<desc>Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer hit by SAM. (miss distance: 284m)</desc>
</wpt>
<wpt lat="47.270153" lon="47.723923">
<ele>18365</ele>
<time>2012-01-01T00:05:50Z</time>
<name>Missile exploded</name>
<desc></desc>
</wpt>

<trk><name>Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer</name><trkseg>
<trkpt lat="47.841335" lon="50.239263">
<ele>10</ele>
<time>2012-01-01T00:00:31Z</time>
</trkpt>
<trkpt lat="47.841278" lon="50.239012">
<ele>26</ele>
<time>2012-01-01T00:00:32Z</time>
</trkpt>
<trkpt lat="47.841182" lon="50.238588">
<ele>53</ele>
<time>2012-01-01T00:00:33Z</time>
</trkpt>
<trkpt lat="47.841045" lon="50.237991">
<ele>92</ele>
<time>2012-01-01T00:00:34Z</time>
</trkpt>
<trkpt lat="47.840870" lon="50.237222">
<ele>142</ele>
<time>2012-01-01T00:00:35Z</time>
</trkpt>
<trkpt lat="47.840657" lon="50.236280">
<ele>204</ele>
<time>2012-01-01T00:00:36Z</time>
</trkpt>
<trkpt lat="47.840403" lon="50.235165">
<ele>276</ele>
<time>2012-01-01T00:00:37Z</time>
</trkpt>
<trkpt lat="47.840111" lon="50.233876">
<ele>360</ele>
<time>2012-01-01T00:00:38Z</time>
</trkpt>
<trkpt lat="47.839779" lon="50.232415">
<ele>455</ele>
<time>2012-01-01T00:00:39Z</time>
</trkpt>
<trkpt lat="47.839409" lon="50.230781">
<ele>561</ele>
<time>2012-01-01T00:00:40Z</time>
</trkpt>
<trkpt lat="47.838997" lon="50.228974">
<ele>679</ele>
<time>2012-01-01T00:00:41Z</time>
</trkpt>
<trkpt lat="47.838549" lon="50.226995">
<ele>808</ele>
<time>2012-01-01T00:00:42Z</time>
</trkpt>
<trkpt lat="47.838059" lon="50.224842">
<ele>948</ele>
<time>2012-01-01T00:00:43Z</time>
</trkpt>
<trkpt lat="47.837532" lon="50.222515">
<ele>1099</ele>
<time>2012-01-01T00:00:44Z</time>
</trkpt>
<trkpt lat="47.836964" lon="50.220018">
<ele>1262</ele>
<time>2012-01-01T00:00:45Z</time>
</trkpt>
<trkpt lat="47.836357" lon="50.217345">
<ele>1436</ele>
<time>2012-01-01T00:00:46Z</time>
</trkpt>
<trkpt lat="47.835712" lon="50.214502">
<ele>1621</ele>
<time>2012-01-01T00:00:47Z</time>
</trkpt>
<trkpt lat="47.835026" lon="50.211483">
<ele>1817</ele>
<time>2012-01-01T00:00:48Z</time>
</trkpt>
<trkpt lat="47.834302" lon="50.208294">
<ele>2024</ele>
<time>2012-01-01T00:00:49Z</time>
</trkpt>
<trkpt lat="47.833539" lon="50.204931">
<ele>2243</ele>
<time>2012-01-01T00:00:50Z</time>
</trkpt>
<trkpt lat="47.832735" lon="50.201394">
<ele>2473</ele>
<time>2012-01-01T00:00:51Z</time>
</trkpt>
<trkpt lat="47.831893" lon="50.197685">
<ele>2715</ele>
<time>2012-01-01T00:00:52Z</time>
</trkpt>
<trkpt lat="47.831012" lon="50.193804">
<ele>2967</ele>
<time>2012-01-01T00:00:53Z</time>
</trkpt>
<trkpt lat="47.830091" lon="50.189748">
<ele>3231</ele>
<time>2012-01-01T00:00:54Z</time>
</trkpt>
<trkpt lat="47.829130" lon="50.185521">
<ele>3506</ele>
<time>2012-01-01T00:00:55Z</time>
</trkpt>
<trkpt lat="47.828131" lon="50.181120">
<ele>3792</ele>
<time>2012-01-01T00:00:56Z</time>
</trkpt>
<trkpt lat="47.827092" lon="50.176546">
<ele>4090</ele>
<time>2012-01-01T00:00:57Z</time>
</trkpt>
<trkpt lat="47.826014" lon="50.171801">
<ele>4399</ele>
<time>2012-01-01T00:00:58Z</time>
</trkpt>
<trkpt lat="47.824897" lon="50.166880">
<ele>4719</ele>
<time>2012-01-01T00:00:59Z</time>
</trkpt>
<trkpt lat="47.823742" lon="50.161788">
<ele>5050</ele>
<time>2012-01-01T00:01:00Z</time>
</trkpt>
<trkpt lat="47.822546" lon="50.156523">
<ele>5393</ele>
<time>2012-01-01T00:01:01Z</time>
</trkpt>
<trkpt lat="47.821311" lon="50.151085">
<ele>5747</ele>
<time>2012-01-01T00:01:02Z</time>
</trkpt>
<trkpt lat="47.820036" lon="50.145474">
<ele>6112</ele>
<time>2012-01-01T00:01:03Z</time>
</trkpt>
<trkpt lat="47.818724" lon="50.139690">
<ele>6488</ele>
<time>2012-01-01T00:01:04Z</time>
</trkpt>
<trkpt lat="47.817371" lon="50.133733">
<ele>6875</ele>
<time>2012-01-01T00:01:05Z</time>
</trkpt>
<trkpt lat="47.815978" lon="50.127603">
<ele>7274</ele>
<time>2012-01-01T00:01:06Z</time>
</trkpt>
<trkpt lat="47.814548" lon="50.121302">
<ele>7684</ele>
<time>2012-01-01T00:01:07Z</time>
</trkpt>
<trkpt lat="47.813077" lon="50.114826">
<ele>8106</ele>
<time>2012-01-01T00:01:08Z</time>
</trkpt>
<trkpt lat="47.811568" lon="50.108178">
<ele>8538</ele>
<time>2012-01-01T00:01:09Z</time>
</trkpt>
<trkpt lat="47.810018" lon="50.101356">
<ele>8982</ele>
<time>2012-01-01T00:01:10Z</time>
</trkpt>
<trkpt lat="47.808430" lon="50.094361">
<ele>9429</ele>
<time>2012-01-01T00:01:11Z</time>
</trkpt>
<trkpt lat="47.806803" lon="50.087195">
<ele>9865</ele>
<time>2012-01-01T00:01:12Z</time>
</trkpt>
<trkpt lat="47.805135" lon="50.079855">
<ele>10290</ele>
<time>2012-01-01T00:01:13Z</time>
</trkpt>
<trkpt lat="47.803429" lon="50.072341">
<ele>10703</ele>
<time>2012-01-01T00:01:14Z</time>
</trkpt>
<trkpt lat="47.801684" lon="50.064655">
<ele>11105</ele>
<time>2012-01-01T00:01:15Z</time>
</trkpt>
<trkpt lat="47.799900" lon="50.056797">
<ele>11496</ele>
<time>2012-01-01T00:01:16Z</time>
</trkpt>
<trkpt lat="47.798076" lon="50.048765">
<ele>11876</ele>
<time>2012-01-01T00:01:17Z</time>
</trkpt>
<trkpt lat="47.796213" lon="50.040559">
<ele>12244</ele>
<time>2012-01-01T00:01:18Z</time>
</trkpt>
<trkpt lat="47.794311" lon="50.032183">
<ele>12601</ele>
<time>2012-01-01T00:01:19Z</time>
</trkpt>
<trkpt lat="47.792369" lon="50.023631">
<ele>12947</ele>
<time>2012-01-01T00:01:20Z</time>
</trkpt>
<trkpt lat="47.790388" lon="50.014909">
<ele>13282</ele>
<time>2012-01-01T00:01:21Z</time>
</trkpt>
<trkpt lat="47.788367" lon="50.006011">
<ele>13606</ele>
<time>2012-01-01T00:01:22Z</time>
</trkpt>
<trkpt lat="47.786309" lon="49.996943">
<ele>13918</ele>
<time>2012-01-01T00:01:23Z</time>
</trkpt>
<trkpt lat="47.784210" lon="49.987701">
<ele>14219</ele>
<time>2012-01-01T00:01:24Z</time>
</trkpt>
<trkpt lat="47.782071" lon="49.978285">
<ele>14508</ele>
<time>2012-01-01T00:01:25Z</time>
</trkpt>
<trkpt lat="47.779895" lon="49.968698">
<ele>14787</ele>
<time>2012-01-01T00:01:26Z</time>
</trkpt>
<trkpt lat="47.777678" lon="49.958936">
<ele>15054</ele>
<time>2012-01-01T00:01:27Z</time>
</trkpt>
<trkpt lat="47.775423" lon="49.949002">
<ele>15310</ele>
<time>2012-01-01T00:01:28Z</time>
</trkpt>
<trkpt lat="47.773127" lon="49.938895">
<ele>15555</ele>
<time>2012-01-01T00:01:29Z</time>
</trkpt>
<trkpt lat="47.770792" lon="49.928617">
<ele>15788</ele>
<time>2012-01-01T00:01:30Z</time>
</trkpt>
<trkpt lat="47.768419" lon="49.918163">
<ele>16010</ele>
<time>2012-01-01T00:01:31Z</time>
</trkpt>
<trkpt lat="47.766007" lon="49.907538">
<ele>16221</ele>
<time>2012-01-01T00:01:32Z</time>
</trkpt>
<trkpt lat="47.763554" lon="49.896740">
<ele>16421</ele>
<time>2012-01-01T00:01:33Z</time>
</trkpt>
<trkpt lat="47.761063" lon="49.885769">
<ele>16609</ele>
<time>2012-01-01T00:01:34Z</time>
</trkpt>
<trkpt lat="47.758532" lon="49.874625">
<ele>16786</ele>
<time>2012-01-01T00:01:35Z</time>
</trkpt>
<trkpt lat="47.755963" lon="49.863306">
<ele>16952</ele>
<time>2012-01-01T00:01:36Z</time>
</trkpt>
<trkpt lat="47.753354" lon="49.851816">
<ele>17107</ele>
<time>2012-01-01T00:01:37Z</time>
</trkpt>
<trkpt lat="47.750705" lon="49.840153">
<ele>17251</ele>
<time>2012-01-01T00:01:38Z</time>
</trkpt>
<trkpt lat="47.748018" lon="49.828319">
<ele>17383</ele>
<time>2012-01-01T00:01:39Z</time>
</trkpt>
<trkpt lat="47.745291" lon="49.816310">
<ele>17504</ele>
<time>2012-01-01T00:01:40Z</time>
</trkpt>
<trkpt lat="47.742525" lon="49.804127">
<ele>17613</ele>
<time>2012-01-01T00:01:41Z</time>
</trkpt>
<trkpt lat="47.739719" lon="49.791772">
<ele>17712</ele>
<time>2012-01-01T00:01:42Z</time>
</trkpt>
<trkpt lat="47.736874" lon="49.779246">
<ele>17799</ele>
<time>2012-01-01T00:01:43Z</time>
</trkpt>
<trkpt lat="47.733989" lon="49.766545">
<ele>17875</ele>
<time>2012-01-01T00:01:44Z</time>
</trkpt>
<trkpt lat="47.731067" lon="49.753672">
<ele>17940</ele>
<time>2012-01-01T00:01:45Z</time>
</trkpt>
<trkpt lat="47.728104" lon="49.740625">
<ele>17993</ele>
<time>2012-01-01T00:01:46Z</time>
</trkpt>
<trkpt lat="47.725102" lon="49.727406">
<ele>18035</ele>
<time>2012-01-01T00:01:47Z</time>
</trkpt>
<trkpt lat="47.722062" lon="49.714015">
<ele>18066</ele>
<time>2012-01-01T00:01:48Z</time>
</trkpt>
<trkpt lat="47.718980" lon="49.700449">
<ele>18086</ele>
<time>2012-01-01T00:01:49Z</time>
</trkpt>
<trkpt lat="47.715862" lon="49.686711">
<ele>18094</ele>
<time>2012-01-01T00:01:50Z</time>
</trkpt>
<trkpt lat="47.712721" lon="49.672882">
<ele>18096</ele>
<time>2012-01-01T00:01:51Z</time>
</trkpt>
<trkpt lat="47.709592" lon="49.659100">
<ele>18097</ele>
<time>2012-01-01T00:01:52Z</time>
</trkpt>
<trkpt lat="47.706474" lon="49.645372">
<ele>18098</ele>
<time>2012-01-01T00:01:53Z</time>
</trkpt>
<trkpt lat="47.703369" lon="49.631695">
<ele>18099</ele>
<time>2012-01-01T00:01:54Z</time>
</trkpt>
<trkpt lat="47.700274" lon="49.618071">
<ele>18100</ele>
<time>2012-01-01T00:01:55Z</time>
</trkpt>
<trkpt lat="47.697192" lon="49.604497">
<ele>18101</ele>
<time>2012-01-01T00:01:56Z</time>
</trkpt>
<trkpt lat="47.694122" lon="49.590977">
<ele>18102</ele>
<time>2012-01-01T00:01:57Z</time>
</trkpt>
<trkpt lat="47.691063" lon="49.577506">
<ele>18103</ele>
<time>2012-01-01T00:01:58Z</time>
</trkpt>
<trkpt lat="47.688017" lon="49.564090">
<ele>18105</ele>
<time>2012-01-01T00:01:59Z</time>
</trkpt>
<trkpt lat="47.684981" lon="49.550724">
<ele>18106</ele>
<time>2012-01-01T00:02:00Z</time>
</trkpt>
<trkpt lat="47.681958" lon="49.537410">
<ele>18107</ele>
<time>2012-01-01T00:02:01Z</time>
</trkpt>
<trkpt lat="47.678947" lon="49.524146">
<ele>18108</ele>
<time>2012-01-01T00:02:02Z</time>
</trkpt>
<trkpt lat="47.675947" lon="49.510936">
<ele>18109</ele>
<time>2012-01-01T00:02:03Z</time>
</trkpt>
<trkpt lat="47.672958" lon="49.497777">
<ele>18110</ele>
<time>2012-01-01T00:02:04Z</time>
</trkpt>
<trkpt lat="47.669983" lon="49.484672">
<ele>18111</ele>
<time>2012-01-01T00:02:05Z</time>
</trkpt>
<trkpt lat="47.667017" lon="49.471617">
<ele>18112</ele>
<time>2012-01-01T00:02:06Z</time>
</trkpt>
<trkpt lat="47.664065" lon="49.458612">
<ele>18114</ele>
<time>2012-01-01T00:02:07Z</time>
</trkpt>
<trkpt lat="47.661124" lon="49.445661">
<ele>18115</ele>
<time>2012-01-01T00:02:08Z</time>
</trkpt>
<trkpt lat="47.658194" lon="49.432761">
<ele>18116</ele>
<time>2012-01-01T00:02:09Z</time>
</trkpt>
<trkpt lat="47.655278" lon="49.419915">
<ele>18117</ele>
<time>2012-01-01T00:02:10Z</time>
</trkpt>
<trkpt lat="47.652371" lon="49.407119">
<ele>18118</ele>
<time>2012-01-01T00:02:11Z</time>
</trkpt>
<trkpt lat="47.649478" lon="49.394374">
<ele>18119</ele>
<time>2012-01-01T00:02:12Z</time>
</trkpt>
<trkpt lat="47.646596" lon="49.381681">
<ele>18120</ele>
<time>2012-01-01T00:02:13Z</time>
</trkpt>
<trkpt lat="47.643726" lon="49.369042">
<ele>18121</ele>
<time>2012-01-01T00:02:14Z</time>
</trkpt>
<trkpt lat="47.640867" lon="49.356453">
<ele>18123</ele>
<time>2012-01-01T00:02:15Z</time>
</trkpt>
<trkpt lat="47.638019" lon="49.343916">
<ele>18124</ele>
<time>2012-01-01T00:02:16Z</time>
</trkpt>
<trkpt lat="47.635184" lon="49.331431">
<ele>18125</ele>
<time>2012-01-01T00:02:17Z</time>
</trkpt>
<trkpt lat="47.632362" lon="49.318998">
<ele>18126</ele>
<time>2012-01-01T00:02:18Z</time>
</trkpt>
<trkpt lat="47.629550" lon="49.306615">
<ele>18127</ele>
<time>2012-01-01T00:02:19Z</time>
</trkpt>
<trkpt lat="47.626750" lon="49.294286">
<ele>18128</ele>
<time>2012-01-01T00:02:20Z</time>
</trkpt>
<trkpt lat="47.623961" lon="49.282009">
<ele>18129</ele>
<time>2012-01-01T00:02:21Z</time>
</trkpt>
<trkpt lat="47.621186" lon="49.269782">
<ele>18130</ele>
<time>2012-01-01T00:02:22Z</time>
</trkpt>
<trkpt lat="47.618420" lon="49.257609">
<ele>18132</ele>
<time>2012-01-01T00:02:23Z</time>
</trkpt>
<trkpt lat="47.615668" lon="49.245485">
<ele>18133</ele>
<time>2012-01-01T00:02:24Z</time>
</trkpt>
<trkpt lat="47.612927" lon="49.233415">
<ele>18134</ele>
<time>2012-01-01T00:02:25Z</time>
</trkpt>
<trkpt lat="47.610199" lon="49.221397">
<ele>18135</ele>
<time>2012-01-01T00:02:26Z</time>
</trkpt>
<trkpt lat="47.607480" lon="49.209429">
<ele>18136</ele>
<time>2012-01-01T00:02:27Z</time>
</trkpt>
<trkpt lat="47.604774" lon="49.197515">
<ele>18137</ele>
<time>2012-01-01T00:02:28Z</time>
</trkpt>
<trkpt lat="47.602080" lon="49.185651">
<ele>18138</ele>
<time>2012-01-01T00:02:29Z</time>
</trkpt>
<trkpt lat="47.599398" lon="49.173839">
<ele>18139</ele>
<time>2012-01-01T00:02:30Z</time>
</trkpt>
<trkpt lat="47.596729" lon="49.162080">
<ele>18141</ele>
<time>2012-01-01T00:02:31Z</time>
</trkpt>
<trkpt lat="47.594070" lon="49.150371">
<ele>18142</ele>
<time>2012-01-01T00:02:32Z</time>
</trkpt>
<trkpt lat="47.591422" lon="49.138716">
<ele>18143</ele>
<time>2012-01-01T00:02:33Z</time>
</trkpt>
<trkpt lat="47.588788" lon="49.127111">
<ele>18144</ele>
<time>2012-01-01T00:02:34Z</time>
</trkpt>
<trkpt lat="47.586165" lon="49.115558">
<ele>18145</ele>
<time>2012-01-01T00:02:35Z</time>
</trkpt>
<trkpt lat="47.583553" lon="49.104058">
<ele>18146</ele>
<time>2012-01-01T00:02:36Z</time>
</trkpt>
<trkpt lat="47.580953" lon="49.092610">
<ele>18147</ele>
<time>2012-01-01T00:02:37Z</time>
</trkpt>
<trkpt lat="47.578366" lon="49.081212">
<ele>18148</ele>
<time>2012-01-01T00:02:38Z</time>
</trkpt>
<trkpt lat="47.575789" lon="49.069867">
<ele>18150</ele>
<time>2012-01-01T00:02:39Z</time>
</trkpt>
<trkpt lat="47.573225" lon="49.058574">
<ele>18151</ele>
<time>2012-01-01T00:02:40Z</time>
</trkpt>
<trkpt lat="47.570672" lon="49.047331">
<ele>18152</ele>
<time>2012-01-01T00:02:41Z</time>
</trkpt>
<trkpt lat="47.568131" lon="49.036143">
<ele>18153</ele>
<time>2012-01-01T00:02:42Z</time>
</trkpt>
<trkpt lat="47.565601" lon="49.025005">
<ele>18154</ele>
<time>2012-01-01T00:02:43Z</time>
</trkpt>
<trkpt lat="47.563084" lon="49.013917">
<ele>18155</ele>
<time>2012-01-01T00:02:44Z</time>
</trkpt>
<trkpt lat="47.560578" lon="49.002884">
<ele>18156</ele>
<time>2012-01-01T00:02:45Z</time>
</trkpt>
<trkpt lat="47.558084" lon="48.991900">
<ele>18157</ele>
<time>2012-01-01T00:02:46Z</time>
</trkpt>
<trkpt lat="47.555602" lon="48.980970">
<ele>18159</ele>
<time>2012-01-01T00:02:47Z</time>
</trkpt>
<trkpt lat="47.553131" lon="48.970092">
<ele>18160</ele>
<time>2012-01-01T00:02:48Z</time>
</trkpt>
<trkpt lat="47.550674" lon="48.959265">
<ele>18161</ele>
<time>2012-01-01T00:02:49Z</time>
</trkpt>
<trkpt lat="47.548226" lon="48.948489">
<ele>18162</ele>
<time>2012-01-01T00:02:50Z</time>
</trkpt>
<trkpt lat="47.545791" lon="48.937766">
<ele>18163</ele>
<time>2012-01-01T00:02:51Z</time>
</trkpt>
<trkpt lat="47.543368" lon="48.927093">
<ele>18164</ele>
<time>2012-01-01T00:02:52Z</time>
</trkpt>
<trkpt lat="47.540956" lon="48.916474">
<ele>18165</ele>
<time>2012-01-01T00:02:53Z</time>
</trkpt>
<trkpt lat="47.538556" lon="48.905906">
<ele>18166</ele>
<time>2012-01-01T00:02:54Z</time>
</trkpt>
<trkpt lat="47.536169" lon="48.895389">
<ele>18168</ele>
<time>2012-01-01T00:02:55Z</time>
</trkpt>
<trkpt lat="47.533793" lon="48.884925">
<ele>18169</ele>
<time>2012-01-01T00:02:56Z</time>
</trkpt>
<trkpt lat="47.531427" lon="48.874513">
<ele>18170</ele>
<time>2012-01-01T00:02:57Z</time>
</trkpt>
<trkpt lat="47.529076" lon="48.864151">
<ele>18171</ele>
<time>2012-01-01T00:02:58Z</time>
</trkpt>
<trkpt lat="47.526735" lon="48.853842">
<ele>18172</ele>
<time>2012-01-01T00:02:59Z</time>
</trkpt>
<trkpt lat="47.524405" lon="48.843586">
<ele>18173</ele>
<time>2012-01-01T00:03:00Z</time>
</trkpt>
<trkpt lat="47.522087" lon="48.833379">
<ele>18174</ele>
<time>2012-01-01T00:03:01Z</time>
</trkpt>
<trkpt lat="47.519781" lon="48.823227">
<ele>18175</ele>
<time>2012-01-01T00:03:02Z</time>
</trkpt>
<trkpt lat="47.517488" lon="48.813124">
<ele>18177</ele>
<time>2012-01-01T00:03:03Z</time>
</trkpt>
<trkpt lat="47.515205" lon="48.803074">
<ele>18178</ele>
<time>2012-01-01T00:03:04Z</time>
</trkpt>
<trkpt lat="47.512936" lon="48.793076">
<ele>18179</ele>
<time>2012-01-01T00:03:05Z</time>
</trkpt>
<trkpt lat="47.510677" lon="48.783129">
<ele>18180</ele>
<time>2012-01-01T00:03:06Z</time>
</trkpt>
<trkpt lat="47.508429" lon="48.773235">
<ele>18181</ele>
<time>2012-01-01T00:03:07Z</time>
</trkpt>
<trkpt lat="47.506194" lon="48.763393">
<ele>18182</ele>
<time>2012-01-01T00:03:08Z</time>
</trkpt>
<trkpt lat="47.503971" lon="48.753602">
<ele>18183</ele>
<time>2012-01-01T00:03:09Z</time>
</trkpt>
<trkpt lat="47.501761" lon="48.743862">
<ele>18184</ele>
<time>2012-01-01T00:03:10Z</time>
</trkpt>
<trkpt lat="47.499560" lon="48.734175">
<ele>18186</ele>
<time>2012-01-01T00:03:11Z</time>
</trkpt>
<trkpt lat="47.497373" lon="48.724539">
<ele>18187</ele>
<time>2012-01-01T00:03:12Z</time>
</trkpt>
<trkpt lat="47.495196" lon="48.714956">
<ele>18188</ele>
<time>2012-01-01T00:03:13Z</time>
</trkpt>
<trkpt lat="47.493031" lon="48.705424">
<ele>18189</ele>
<time>2012-01-01T00:03:14Z</time>
</trkpt>
<trkpt lat="47.490878" lon="48.695945">
<ele>18190</ele>
<time>2012-01-01T00:03:15Z</time>
</trkpt>
<trkpt lat="47.488737" lon="48.686515">
<ele>18191</ele>
<time>2012-01-01T00:03:16Z</time>
</trkpt>
<trkpt lat="47.486609" lon="48.677140">
<ele>18192</ele>
<time>2012-01-01T00:03:17Z</time>
</trkpt>
<trkpt lat="47.484492" lon="48.667814">
<ele>18193</ele>
<time>2012-01-01T00:03:18Z</time>
</trkpt>
<trkpt lat="47.482385" lon="48.658543">
<ele>18195</ele>
<time>2012-01-01T00:03:19Z</time>
</trkpt>
<trkpt lat="47.480291" lon="48.649321">
<ele>18196</ele>
<time>2012-01-01T00:03:20Z</time>
</trkpt>
<trkpt lat="47.478209" lon="48.640152">
<ele>18197</ele>
<time>2012-01-01T00:03:21Z</time>
</trkpt>
<trkpt lat="47.476140" lon="48.631034">
<ele>18198</ele>
<time>2012-01-01T00:03:22Z</time>
</trkpt>
<trkpt lat="47.474080" lon="48.621968">
<ele>18199</ele>
<time>2012-01-01T00:03:23Z</time>
</trkpt>
<trkpt lat="47.472034" lon="48.612955">
<ele>18200</ele>
<time>2012-01-01T00:03:24Z</time>
</trkpt>
<trkpt lat="47.469999" lon="48.603994">
<ele>18201</ele>
<time>2012-01-01T00:03:25Z</time>
</trkpt>
<trkpt lat="47.467976" lon="48.595083">
<ele>18202</ele>
<time>2012-01-01T00:03:26Z</time>
</trkpt>
<trkpt lat="47.465963" lon="48.586224">
<ele>18204</ele>
<time>2012-01-01T00:03:27Z</time>
</trkpt>
<trkpt lat="47.463965" lon="48.577418">
<ele>18205</ele>
<time>2012-01-01T00:03:28Z</time>
</trkpt>
<trkpt lat="47.461976" lon="48.568663">
<ele>18206</ele>
<time>2012-01-01T00:03:29Z</time>
</trkpt>
<trkpt lat="47.460000" lon="48.559961">
<ele>18207</ele>
<time>2012-01-01T00:03:30Z</time>
</trkpt>
<trkpt lat="47.458035" lon="48.551310">
<ele>18208</ele>
<time>2012-01-01T00:03:31Z</time>
</trkpt>
<trkpt lat="47.456082" lon="48.542710">
<ele>18209</ele>
<time>2012-01-01T00:03:32Z</time>
</trkpt>
<trkpt lat="47.454141" lon="48.534162">
<ele>18210</ele>
<time>2012-01-01T00:03:33Z</time>
</trkpt>
<trkpt lat="47.452213" lon="48.525668">
<ele>18211</ele>
<time>2012-01-01T00:03:34Z</time>
</trkpt>
<trkpt lat="47.450296" lon="48.517223">
<ele>18213</ele>
<time>2012-01-01T00:03:35Z</time>
</trkpt>
<trkpt lat="47.448390" lon="48.508831">
<ele>18214</ele>
<time>2012-01-01T00:03:36Z</time>
</trkpt>
<trkpt lat="47.446496" lon="48.500492">
<ele>18215</ele>
<time>2012-01-01T00:03:37Z</time>
</trkpt>
<trkpt lat="47.444614" lon="48.492203">
<ele>18216</ele>
<time>2012-01-01T00:03:38Z</time>
</trkpt>
<trkpt lat="47.442743" lon="48.483966">
<ele>18217</ele>
<time>2012-01-01T00:03:39Z</time>
</trkpt>
<trkpt lat="47.440885" lon="48.475782">
<ele>18218</ele>
<time>2012-01-01T00:03:40Z</time>
</trkpt>
<trkpt lat="47.439037" lon="48.467649">
<ele>18219</ele>
<time>2012-01-01T00:03:41Z</time>
</trkpt>
<trkpt lat="47.437202" lon="48.459567">
<ele>18220</ele>
<time>2012-01-01T00:03:42Z</time>
</trkpt>
<trkpt lat="47.435380" lon="48.451537">
<ele>18222</ele>
<time>2012-01-01T00:03:43Z</time>
</trkpt>
<trkpt lat="47.433568" lon="48.443561">
<ele>18223</ele>
<time>2012-01-01T00:03:44Z</time>
</trkpt>
<trkpt lat="47.431767" lon="48.435634">
<ele>18224</ele>
<time>2012-01-01T00:03:45Z</time>
</trkpt>
<trkpt lat="47.429980" lon="48.427760">
<ele>18225</ele>
<time>2012-01-01T00:03:46Z</time>
</trkpt>
<trkpt lat="47.428204" lon="48.419938">
<ele>18226</ele>
<time>2012-01-01T00:03:47Z</time>
</trkpt>
<trkpt lat="47.426439" lon="48.412168">
<ele>18227</ele>
<time>2012-01-01T00:03:48Z</time>
</trkpt>
<trkpt lat="47.424686" lon="48.404449">
<ele>18228</ele>
<time>2012-01-01T00:03:49Z</time>
</trkpt>
<trkpt lat="47.422946" lon="48.396783">
<ele>18229</ele>
<time>2012-01-01T00:03:50Z</time>
</trkpt>
<trkpt lat="47.421216" lon="48.389169">
<ele>18231</ele>
<time>2012-01-01T00:03:51Z</time>
</trkpt>
<trkpt lat="47.419499" lon="48.381605">
<ele>18232</ele>
<time>2012-01-01T00:03:52Z</time>
</trkpt>
<trkpt lat="47.417794" lon="48.374094">
<ele>18233</ele>
<time>2012-01-01T00:03:53Z</time>
</trkpt>
<trkpt lat="47.416100" lon="48.366635">
<ele>18234</ele>
<time>2012-01-01T00:03:54Z</time>
</trkpt>
<trkpt lat="47.414417" lon="48.359228">
<ele>18235</ele>
<time>2012-01-01T00:03:55Z</time>
</trkpt>
<trkpt lat="47.412748" lon="48.351872">
<ele>18236</ele>
<time>2012-01-01T00:03:56Z</time>
</trkpt>
<trkpt lat="47.411088" lon="48.344568">
<ele>18237</ele>
<time>2012-01-01T00:03:57Z</time>
</trkpt>
<trkpt lat="47.409441" lon="48.337316">
<ele>18238</ele>
<time>2012-01-01T00:03:58Z</time>
</trkpt>
<trkpt lat="47.407806" lon="48.330114">
<ele>18240</ele>
<time>2012-01-01T00:03:59Z</time>
</trkpt>
<trkpt lat="47.406184" lon="48.322966">
<ele>18241</ele>
<time>2012-01-01T00:04:00Z</time>
</trkpt>
<trkpt lat="47.404572" lon="48.315869">
<ele>18242</ele>
<time>2012-01-01T00:04:01Z</time>
</trkpt>
<trkpt lat="47.402971" lon="48.308824">
<ele>18243</ele>
<time>2012-01-01T00:04:02Z</time>
</trkpt>
<trkpt lat="47.401384" lon="48.301831">
<ele>18244</ele>
<time>2012-01-01T00:04:03Z</time>
</trkpt>
<trkpt lat="47.399808" lon="48.294890">
<ele>18245</ele>
<time>2012-01-01T00:04:04Z</time>
</trkpt>
<trkpt lat="47.398243" lon="48.288001">
<ele>18246</ele>
<time>2012-01-01T00:04:05Z</time>
</trkpt>
<trkpt lat="47.396690" lon="48.281162">
<ele>18247</ele>
<time>2012-01-01T00:04:06Z</time>
</trkpt>
<trkpt lat="47.395150" lon="48.274377">
<ele>18249</ele>
<time>2012-01-01T00:04:07Z</time>
</trkpt>
<trkpt lat="47.393621" lon="48.267642">
<ele>18250</ele>
<time>2012-01-01T00:04:08Z</time>
</trkpt>
<trkpt lat="47.392104" lon="48.260961">
<ele>18251</ele>
<time>2012-01-01T00:04:09Z</time>
</trkpt>
<trkpt lat="47.390597" lon="48.254331">
<ele>18252</ele>
<time>2012-01-01T00:04:10Z</time>
</trkpt>
<trkpt lat="47.389057" lon="48.247545">
<ele>18253</ele>
<time>2012-01-01T00:04:11Z</time>
</trkpt>
<trkpt lat="47.387574" lon="48.241019">
<ele>18254</ele>
<time>2012-01-01T00:04:12Z</time>
</trkpt>
<trkpt lat="47.386105" lon="48.234543">
<ele>18255</ele>
<time>2012-01-01T00:04:13Z</time>
</trkpt>
<trkpt lat="47.384645" lon="48.228121">
<ele>18256</ele>
<time>2012-01-01T00:04:14Z</time>
</trkpt>
<trkpt lat="47.383198" lon="48.221749">
<ele>18258</ele>
<time>2012-01-01T00:04:15Z</time>
</trkpt>
<trkpt lat="47.381763" lon="48.215429">
<ele>18259</ele>
<time>2012-01-01T00:04:16Z</time>
</trkpt>
<trkpt lat="47.380341" lon="48.209161">
<ele>18260</ele>
<time>2012-01-01T00:04:17Z</time>
</trkpt>
<trkpt lat="47.378929" lon="48.202945">
<ele>18261</ele>
<time>2012-01-01T00:04:18Z</time>
</trkpt>
<trkpt lat="47.377530" lon="48.196781">
<ele>18262</ele>
<time>2012-01-01T00:04:19Z</time>
</trkpt>
<trkpt lat="47.376142" lon="48.190668">
<ele>18263</ele>
<time>2012-01-01T00:04:20Z</time>
</trkpt>
<trkpt lat="47.374766" lon="48.184609">
<ele>18264</ele>
<time>2012-01-01T00:04:21Z</time>
</trkpt>
<trkpt lat="47.373401" lon="48.178600">
<ele>18265</ele>
<time>2012-01-01T00:04:22Z</time>
</trkpt>
<trkpt lat="47.372047" lon="48.172643">
<ele>18267</ele>
<time>2012-01-01T00:04:23Z</time>
</trkpt>
<trkpt lat="47.370708" lon="48.166738">
<ele>18268</ele>
<time>2012-01-01T00:04:24Z</time>
</trkpt>
<trkpt lat="47.369377" lon="48.160885">
<ele>18269</ele>
<time>2012-01-01T00:04:25Z</time>
</trkpt>
<trkpt lat="47.368060" lon="48.155082">
<ele>18270</ele>
<time>2012-01-01T00:04:26Z</time>
</trkpt>
<trkpt lat="47.366754" lon="48.149334">
<ele>18271</ele>
<time>2012-01-01T00:04:27Z</time>
</trkpt>
<trkpt lat="47.365461" lon="48.143636">
<ele>18272</ele>
<time>2012-01-01T00:04:28Z</time>
</trkpt>
<trkpt lat="47.364179" lon="48.137990">
<ele>18273</ele>
<time>2012-01-01T00:04:29Z</time>
</trkpt>
<trkpt lat="47.362909" lon="48.132395">
<ele>18274</ele>
<time>2012-01-01T00:04:30Z</time>
</trkpt>
<trkpt lat="47.361649" lon="48.126852">
<ele>18276</ele>
<time>2012-01-01T00:04:31Z</time>
</trkpt>
<trkpt lat="47.360404" lon="48.121363">
<ele>18277</ele>
<time>2012-01-01T00:04:32Z</time>
</trkpt>
<trkpt lat="47.359169" lon="48.115923">
<ele>18278</ele>
<time>2012-01-01T00:04:33Z</time>
</trkpt>
<trkpt lat="47.357945" lon="48.110537">
<ele>18279</ele>
<time>2012-01-01T00:04:34Z</time>
</trkpt>
<trkpt lat="47.356734" lon="48.105201">
<ele>18280</ele>
<time>2012-01-01T00:04:35Z</time>
</trkpt>
<trkpt lat="47.355533" lon="48.099918">
<ele>18281</ele>
<time>2012-01-01T00:04:36Z</time>
</trkpt>
<trkpt lat="47.354345" lon="48.094687">
<ele>18282</ele>
<time>2012-01-01T00:04:37Z</time>
</trkpt>
<trkpt lat="47.353169" lon="48.089506">
<ele>18283</ele>
<time>2012-01-01T00:04:38Z</time>
</trkpt>
<trkpt lat="47.352004" lon="48.084378">
<ele>18285</ele>
<time>2012-01-01T00:04:39Z</time>
</trkpt>
<trkpt lat="47.350853" lon="48.079303">
<ele>18286</ele>
<time>2012-01-01T00:04:40Z</time>
</trkpt>
</trkseg></trk>

<trk><name>Missile-1</name><trkseg>
<trkpt lat="47.426532" lon="48.063476">
<ele>538</ele>
<time>2012-01-01T00:03:36Z</time>
</trkpt>
<trkpt lat="47.426982" lon="48.071722">
<ele>855</ele>
<time>2012-01-01T00:03:37Z</time>
</trkpt>
<trkpt lat="47.427433" lon="48.079967">
<ele>1172</ele>
<time>2012-01-01T00:03:38Z</time>
</trkpt>
<trkpt lat="47.427883" lon="48.088211">
<ele>1490</ele>
<time>2012-01-01T00:03:39Z</time>
</trkpt>
<trkpt lat="47.427931" lon="48.096147">
<ele>1850</ele>
<time>2012-01-01T00:03:40Z</time>
</trkpt>
<trkpt lat="47.427329" lon="48.103338">
<ele>2287</ele>
<time>2012-01-01T00:03:41Z</time>
</trkpt>
<trkpt lat="47.426231" lon="48.109560">
<ele>2790</ele>
<time>2012-01-01T00:03:42Z</time>
</trkpt>
<trkpt lat="47.424827" lon="48.114660">
<ele>3353</ele>
<time>2012-01-01T00:03:43Z</time>
</trkpt>
<trkpt lat="47.423195" lon="48.119720">
<ele>3911</ele>
<time>2012-01-01T00:03:44Z</time>
</trkpt>
<trkpt lat="47.421804" lon="48.125906">
<ele>4408</ele>
<time>2012-01-01T00:03:45Z</time>
</trkpt>
<trkpt lat="47.420873" lon="48.133096">
<ele>4837</ele>
<time>2012-01-01T00:03:46Z</time>
</trkpt>
<trkpt lat="47.420563" lon="48.141083">
<ele>5190</ele>
<time>2012-01-01T00:03:47Z</time>
</trkpt>
<trkpt lat="47.420954" lon="48.148997">
<ele>5551</ele>
<time>2012-01-01T00:03:48Z</time>
</trkpt>
<trkpt lat="47.421604" lon="48.156180">
<ele>5987</ele>
<time>2012-01-01T00:03:49Z</time>
</trkpt>
<trkpt lat="47.421644" lon="48.162623">
<ele>6490</ele>
<time>2012-01-01T00:03:50Z</time>
</trkpt>
<trkpt lat="47.421097" lon="48.169072">
<ele>6989</ele>
<time>2012-01-01T00:03:51Z</time>
</trkpt>
<trkpt lat="47.419980" lon="48.175379">
<ele>7487</ele>
<time>2012-01-01T00:03:52Z</time>
</trkpt>
<trkpt lat="47.418399" lon="48.181102">
<ele>8009</ele>
<time>2012-01-01T00:03:53Z</time>
</trkpt>
<trkpt lat="47.416500" lon="48.186017">
<ele>8564</ele>
<time>2012-01-01T00:03:54Z</time>
</trkpt>
<trkpt lat="47.414473" lon="48.189960">
<ele>9156</ele>
<time>2012-01-01T00:03:55Z</time>
</trkpt>
<trkpt lat="47.412593" lon="48.192771">
<ele>9789</ele>
<time>2012-01-01T00:03:56Z</time>
</trkpt>
<trkpt lat="47.410986" lon="48.195002">
<ele>10445</ele>
<time>2012-01-01T00:03:57Z</time>
</trkpt>
<trkpt lat="47.409242" lon="48.198138">
<ele>11074</ele>
<time>2012-01-01T00:03:58Z</time>
</trkpt>
<trkpt lat="47.407414" lon="48.202477">
<ele>11658</ele>
<time>2012-01-01T00:03:59Z</time>
</trkpt>
<trkpt lat="47.405715" lon="48.208010">
<ele>12187</ele>
<time>2012-01-01T00:04:00Z</time>
</trkpt>
<trkpt lat="47.404527" lon="48.213726">
<ele>12721</ele>
<time>2012-01-01T00:04:01Z</time>
</trkpt>
<trkpt lat="47.403668" lon="48.218566">
<ele>13310</ele>
<time>2012-01-01T00:04:02Z</time>
</trkpt>
<trkpt lat="47.402455" lon="48.222943">
<ele>13912</ele>
<time>2012-01-01T00:04:03Z</time>
</trkpt>
<trkpt lat="47.400857" lon="48.227071">
<ele>14514</ele>
<time>2012-01-01T00:04:04Z</time>
</trkpt>
<trkpt lat="47.399112" lon="48.230465">
<ele>15136</ele>
<time>2012-01-01T00:04:05Z</time>
</trkpt>
<trkpt lat="47.397070" lon="48.233848">
<ele>15746</ele>
<time>2012-01-01T00:04:06Z</time>
</trkpt>
<trkpt lat="47.394913" lon="48.238384">
<ele>16308</ele>
<time>2012-01-01T00:04:07Z</time>
</trkpt>
<trkpt lat="47.392904" lon="48.244059">
<ele>16814</ele>
<time>2012-01-01T00:04:08Z</time>
</trkpt>
<trkpt lat="47.391505" lon="48.249671">
<ele>17349</ele>
<time>2012-01-01T00:04:09Z</time>
</trkpt>
<trkpt lat="47.390672" lon="48.254578">
<ele>17935</ele>
<time>2012-01-01T00:04:10Z</time>
</trkpt>
</trkseg></trk>

<trk><name>Missile-2</name><trkseg>
<trkpt lat="47.422682" lon="48.059637">
<ele>1206</ele>
<time>2012-01-01T00:04:20Z</time>
</trkpt>
<trkpt lat="47.421213" lon="48.064484">
<ele>1780</ele>
<time>2012-01-01T00:04:21Z</time>
</trkpt>
<trkpt lat="47.419746" lon="48.069332">
<ele>2354</ele>
<time>2012-01-01T00:04:22Z</time>
</trkpt>
<trkpt lat="47.418204" lon="48.074236">
<ele>2923</ele>
<time>2012-01-01T00:04:23Z</time>
</trkpt>
<trkpt lat="47.416015" lon="48.079540">
<ele>3443</ele>
<time>2012-01-01T00:04:24Z</time>
</trkpt>
<trkpt lat="47.413012" lon="48.085042">
<ele>3897</ele>
<time>2012-01-01T00:04:25Z</time>
</trkpt>
<trkpt lat="47.409287" lon="48.090296">
<ele>4301</ele>
<time>2012-01-01T00:04:26Z</time>
</trkpt>
<trkpt lat="47.405161" lon="48.094754">
<ele>4711</ele>
<time>2012-01-01T00:04:27Z</time>
</trkpt>
<trkpt lat="47.400703" lon="48.098357">
<ele>5126</ele>
<time>2012-01-01T00:04:28Z</time>
</trkpt>
<trkpt lat="47.395977" lon="48.101069">
<ele>5544</ele>
<time>2012-01-01T00:04:29Z</time>
</trkpt>
<trkpt lat="47.391053" lon="48.102849">
<ele>5962</ele>
<time>2012-01-01T00:04:30Z</time>
</trkpt>
<trkpt lat="47.386009" lon="48.103673">
<ele>6380</ele>
<time>2012-01-01T00:04:31Z</time>
</trkpt>
<trkpt lat="47.380927" lon="48.103521">
<ele>6796</ele>
<time>2012-01-01T00:04:32Z</time>
</trkpt>
<trkpt lat="47.375892" lon="48.102397">
<ele>7211</ele>
<time>2012-01-01T00:04:33Z</time>
</trkpt>
<trkpt lat="47.370984" lon="48.100309">
<ele>7624</ele>
<time>2012-01-01T00:04:34Z</time>
</trkpt>
<trkpt lat="47.366289" lon="48.097290">
<ele>8034</ele>
<time>2012-01-01T00:04:35Z</time>
</trkpt>
<trkpt lat="47.361888" lon="48.093384">
<ele>8441</ele>
<time>2012-01-01T00:04:36Z</time>
</trkpt>
<trkpt lat="47.357858" lon="48.088648">
<ele>8845</ele>
<time>2012-01-01T00:04:37Z</time>
</trkpt>
<trkpt lat="47.354269" lon="48.083159">
<ele>9245</ele>
<time>2012-01-01T00:04:38Z</time>
</trkpt>
<trkpt lat="47.351187" lon="48.077002">
<ele>9642</ele>
<time>2012-01-01T00:04:39Z</time>
</trkpt>
<trkpt lat="47.348666" lon="48.070270">
<ele>10034</ele>
<time>2012-01-01T00:04:40Z</time>
</trkpt>
<trkpt lat="47.346755" lon="48.063073">
<ele>10422</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.345495" lon="48.055517">
<ele>10803</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.344915" lon="48.047722">
<ele>11176</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.345035" lon="48.039802">
<ele>11540</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.345871" lon="48.031871">
<ele>11890</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.347433" lon="48.024042">
<ele>12223</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.349725" lon="48.016427">
<ele>12531</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.352750" lon="48.009141">
<ele>12805</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.356493" lon="48.002325">
<ele>13036</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.360916" lon="47.996139">
<ele>13215</ele>
<time>2012-01-01T::Z</time>
</trkpt>
</trkseg></trk>

<trk><name>Missile-3</name><trkseg>
<trkpt lat="47.419279" lon="48.045350">
<ele>1244</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.416189" lon="48.043393">
<ele>1837</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.413100" lon="48.041437">
<ele>2430</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.409965" lon="48.039378">
<ele>3018</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.406522" lon="48.036394">
<ele>3559</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.402898" lon="48.032231">
<ele>4039</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.399307" lon="48.026859">
<ele>4447</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.396093" lon="48.020612">
<ele>4822</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.393625" lon="48.014443">
<ele>5267</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.391088" lon="48.009076">
<ele>5764</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.387872" lon="48.003889">
<ele>6222</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.384371" lon="47.999530">
<ele>6702</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.380999" lon="47.996339">
<ele>7243</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.377873" lon="47.993620">
<ele>7816</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.374566" lon="47.989820">
<ele>8338</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.371219" lon="47.984811">
<ele>8795</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.368045" lon="47.978619">
<ele>9179</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.365250" lon="47.971355">
<ele>9484</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.362938" lon="47.963313">
<ele>9721</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.360323" lon="47.955846">
<ele>10017</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.357292" lon="47.949424">
<ele>10393</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.354022" lon="47.944135">
<ele>10839</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.350270" lon="47.939089">
<ele>11254</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.346606" lon="47.933005">
<ele>11591</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.343350" lon="47.925919">
<ele>11863</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.340862" lon="47.918605">
<ele>12192</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.338948" lon="47.911385">
<ele>12577</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.336378" lon="47.904068">
<ele>12898</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.333008" lon="47.896945">
<ele>13146</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.329329" lon="47.890514">
<ele>13443</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.326224" lon="47.883749">
<ele>13776</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.323614" lon="47.876060">
<ele>14039</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.321218" lon="47.868302">
<ele>14315</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.318156" lon="47.861041">
<ele>14588</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.314988" lon="47.853828">
<ele>14854</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.312387" lon="47.846091">
<ele>15111</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.309457" lon="47.838576">
<ele>15363</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.306655" lon="47.830917">
<ele>15608</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.303849" lon="47.823230">
<ele>15847</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.301059" lon="47.815497">
<ele>16080</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.298285" lon="47.807721">
<ele>16308</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.295527" lon="47.799906">
<ele>16530</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.292785" lon="47.792051">
<ele>16746</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.290058" lon="47.784162">
<ele>16957</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.287345" lon="47.776237">
<ele>17164</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.284647" lon="47.768281">
<ele>17365</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.281964" lon="47.760292">
<ele>17561</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.279294" lon="47.752274">
<ele>17753</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.276637" lon="47.744228">
<ele>17941</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.273994" lon="47.736156">
<ele>18124</ele>
<time>2012-01-01T::Z</time>
</trkpt>
<trkpt lat="47.271365" lon="47.728056">
Posted By: piston79

Re: Bug reports - 01/03/13 09:22 PM

I have a strange feeling about SA-4... Check this 3D AAR:

http://www.mediafire.com/?hau7ptsg3dqmpgk

Even after target dissapeared it continued to track (only gates were vissible) and when shot my last missile (missile-3) with armed radiofuse right after launch, it pop-s up in the middle of nothing....

Also when target goes over aquisition envelope of P-40, in case of "Prinimania CU" -ON, but without tracking on angle, nor range, when target overfliing the position, the SNR continuing to rotate and after going 180 degrees it iluminates target again in the same moment, when targt appeared on the P-40 screen.... I did an experiment over Hungary, used an ~0 parameter target, which does a 90 degree turn just over the "Krug" position, and it does it the same to the 180 degrees, then, when target pops-up on P-40, it quickly adjusted 90 degrees more.... Why so? (the Hungary looks more logical, exept rotating to 180 degrees....)...
Posted By: Hpasp

Re: Bug reports - 01/04/13 09:28 AM

Originally Posted By: piston79
I have a strange feeling about SA-4... Check this 3D AAR:

http://www.mediafire.com/?hau7ptsg3dqmpgk

Even after target dissapeared it continued to track (only gates were vissible) and when shot my last missile (missile-3) with armed radiofuse right after launch, it pop-s up in the middle of nothing....


It is a known bug, if no target is flying, that the missile 3DAAR is missing the seconds.
Will be corrected with the Shilka, where it is more easily obsevable.

Originally Posted By: piston79

Also when target goes over aquisition envelope of P-40, in case of "Prinimania CU" -ON, but without tracking on angle, nor range, when target overfliing the position, the SNR continuing to rotate and after going 180 degrees it iluminates target again in the same moment, when targt appeared on the P-40 screen.... I did an experiment over Hungary, used an ~0 parameter target, which does a 90 degree turn just over the "Krug" position, and it does it the same to the 180 degrees, then, when target pops-up on P-40, it quickly adjusted 90 degrees more.... Why so? (the Hungary looks more logical, exept rotating to 180 degrees....)...


When the target is above the the SNR, than several functions could return 0, so this issue should be investigated more.
Posted By: piston79

Re: Bug reports - 01/04/13 11:10 AM

Originally Posted By: Hpasp

When the target is above the the SNR, than several functions could return 0, so this issue should be investigated more.


I believe that when target goes out of P-40's detection, "Pat Hand" just must stop trackin it (when no range or angle track was established0, and when it appears again, should be reaquired with the joystick on p-40 and then send to "Pat hand'....

It is a quite an interesting issue how "Long track" is autotracking targets... confused
Posted By: Hpasp

Re: Bug reports - 01/04/13 12:41 PM

Originally Posted By: piston79
Originally Posted By: Hpasp

When the target is above the the SNR, than several functions could return 0, so this issue should be investigated more.


I believe that when target goes out of P-40's detection, "Pat Hand" just must stop trackin it (when no range or angle track was established0, and when it appears again, should be reaquired with the joystick on p-40 and then send to "Pat hand'....

It is a quite an interesting issue how "Long track" is autotracking targets... confused


Continued at the relevant topic...
Posted By: piston79

Re: Bug reports - 01/12/13 09:43 PM

Again about SA-4 Ganef (I believe an different occurance of above mentioned bug)... Just using Linebacker scenario with SR-71 approaching from south... It frezzes all screen exept "Long truck" one...(257/76 battery).
Posted By: Hpasp

Re: Bug reports - 01/14/13 11:58 AM

Originally Posted By: piston79
Again about SA-4 Ganef (I believe an different occurance of above mentioned bug)... Just using Linebacker scenario with SR-71 approaching from south... It frezzes all screen exept "Long truck" one...(257/76 battery).


Just check the ADAAR file with notepad, to see if the seconds were missing...
Posted By: Mdore

Re: Bug reports - 01/20/13 08:04 AM

A few bugs.

If you play the ZSU-23-4, and then play a different system, SA-2E/F, SA-3, SA-4 or SA-5, the range of the other SAM systems cannot be set over 15km. You have to completely exit and restart the programme to be able to go over 15km again.

Pause doesn't work on the ZSU-23-4, aircraft still move.

And there's an error in the manual on page 35. It says "get it into automatic angle tracking, by clicking with the left mouse button". But the left doesn't do that, it's the right mouse button that goes into automatic tracking.

I already posted the last two bugs in the ZSU-23-4 forum. Hope it isn't a problem to repost them here. Bug number 1, I've only posted here.
Posted By: Hpasp

Re: Bug reports - 01/20/13 12:38 PM

Originally Posted By: Mdore
A few bugs.

If you play the ZSU-23-4, and then play a different system, SA-2E/F, SA-3, SA-4 or SA-5, the range of the other SAM systems cannot be set over 15km. You have to completely exit and restart the programme to be able to go over 15km again.

Pause doesn't work on the ZSU-23-4, aircraft still move.

And there's an error in the manual on page 35. It says "get it into automatic angle tracking, by clicking with the left mouse button". But the left doesn't do that, it's the right mouse button that goes into automatic tracking.

I already posted the last two bugs in the ZSU-23-4 forum. Hope it isn't a problem to repost them here. Bug number 1, I've only posted here.


Thank you for the bug finding.

SAMSIM-926B patch can be downloaded from here:
http://www.mediafire.com/?1d28hcpmr779de0
Just replace the "sam.exe" file with this.

Corrected:
- Pause issue
- Range issue with other systems

New feature
- In Drégelypalánk, the Meteor-1s are arriving from two direction, randomly.
Posted By: Mdore

Re: Bug reports - 01/22/13 11:42 AM

More possible bugs.

In practice "Hungary", I can't enter automatic range tracking. I can automatically track the target's angle, but I can't track the target's range. It just will not lock on.

I only tried with some of the possible aircraft, the 737, Cessna and one of the military jets. None of them could be locked on in range.


It will track range! But only if the aircraft is set to fly at low altitude, not if the aircraft is at high altitude like the default setting for the Hungary practice aircraft. It will lock against an aircraft at 2,500m, but not one at 5,000m. So it might not be a bug. Is this on purpose?

Also, some of the aircraft sometimes are given the name "meteor-1" in the after action report.
Posted By: Alien_MasterMynd

Re: Bug reports - 01/22/13 11:44 AM

Two mistypes in manual for ZSU:
page 25 title hIdraulical instead of hYdraulical
page 35 get into automatic angle tracking, by clicking with the LEFT mouse button - should be RIGHT
Posted By: Alien_MasterMynd

Re: Bug reports - 01/22/13 12:43 PM

And one thing yet (maybe I have not read manual correctly) - when the target is destroyed (radar switched back to search mode) and even i switch off and back on ZU mode, the JEST DANNYE is still lit but fire cannot be opened when fire mode is set to SRP. Maybe it is normal behavior because of mechanical SRP but it is confusing a bit.
Posted By: Hpasp

Re: Bug reports - 01/22/13 04:42 PM

Originally Posted By: Mdore
More possible bugs.

In practice "Hungary", I can't enter automatic range tracking. I can automatically track the target's angle, but I can't track the target's range. It just will not lock on.

I only tried with some of the possible aircraft, the 737, Cessna and one of the military jets. None of them could be locked on in range.


It will track range! But only if the aircraft is set to fly at low altitude, not if the aircraft is at high altitude like the default setting for the Hungary practice aircraft. It will lock against an aircraft at 2,500m, but not one at 5,000m. So it might not be a bug. Is this on purpose?

Also, some of the aircraft sometimes are given the name "meteor-1" in the after action report.


I was perfectly capable of tracking this B-747 flying at 4400m.




Posted By: Hpasp

Re: Bug reports - 01/22/13 04:42 PM

Originally Posted By: Alien_MasterMynd
Two mistypes in manual for ZSU:
page 25 title hIdraulical instead of hYdraulical
page 35 get into automatic angle tracking, by clicking with the LEFT mouse button - should be RIGHT


I will correct it.
Posted By: Hpasp

Re: Bug reports - 01/22/13 04:45 PM

Originally Posted By: Alien_MasterMynd
And one thing yet (maybe I have not read manual correctly) - when the target is destroyed (radar switched back to search mode) and even i switch off and back on ZU mode, the JEST DANNYE is still lit but fire cannot be opened when fire mode is set to SRP. Maybe it is normal behavior because of mechanical SRP but it is confusing a bit.


Est Dannie will allow fire without the radar tracking anything also.

SRP only blocks the firing:
- if the Tu is not between 5,5 ... 0,2
- if the target is flying over 1500m
- if it is allowed to block it
Posted By: Mdore

Re: Bug reports - 01/23/13 08:24 AM

Originally Posted By: Hpasp
Originally Posted By: Mdore
More possible bugs.

In practice "Hungary", I can't enter automatic range tracking. I can automatically track the target's angle, but I can't track the target's range. It just will not lock on.

I only tried with some of the possible aircraft, the 737, Cessna and one of the military jets. None of them could be locked on in range.


It will track range! But only if the aircraft is set to fly at low altitude, not if the aircraft is at high altitude like the default setting for the Hungary practice aircraft. It will lock against an aircraft at 2,500m, but not one at 5,000m. So it might not be a bug. Is this on purpose?

Also, some of the aircraft sometimes are given the name "meteor-1" in the after action report.


I was perfectly capable of tracking this B-747 flying at 4400m.


I don't know what is happening. Today I can track the B-747 and B-737 in two tests I did. But couldn't track a Cessna. I recorded a video of the Cessna.



I click once, twice, three times, or a thousand times. It doesn't lock. Am I doing something wrong?
Posted By: Hpasp

Re: Bug reports - 01/23/13 11:34 AM

Originally Posted By: Mdore
Originally Posted By: Hpasp
Originally Posted By: Mdore
More possible bugs.

In practice "Hungary", I can't enter automatic range tracking. I can automatically track the target's angle, but I can't track the target's range. It just will not lock on.

I only tried with some of the possible aircraft, the 737, Cessna and one of the military jets. None of them could be locked on in range.


It will track range! But only if the aircraft is set to fly at low altitude, not if the aircraft is at high altitude like the default setting for the Hungary practice aircraft. It will lock against an aircraft at 2,500m, but not one at 5,000m. So it might not be a bug. Is this on purpose?

Also, some of the aircraft sometimes are given the name "meteor-1" in the after action report.


I was perfectly capable of tracking this B-747 flying at 4400m.


I don't know what is happening. Today I can track the B-747 and B-737 in two tests I did. But couldn't track a Cessna. I recorded a video of the Cessna.

Click to reveal..


I click once, twice, three times, or a thousand times. It doesn't lock. Am I doing something wrong?


Thank you for this video, it helped a lot finding this bug.
thumbsup

As it affects only few positions, so the fix will be included in the next version.
(I wait a little bit to collect more bugs)
Posted By: Markan

Re: Bug reports - 01/23/13 10:27 PM

Hpasp, in the Shilka manual on 28 page it state "When the required electrical power for the SRP operation is available, a yellow (1) lamp will illuminate." But in the sim it will illuminate only after you switch POWER switch to on. I don't know is this a bug in the sim, error in the manual or it should be like that?
wave
Posted By: Hpasp

Re: Bug reports - 01/24/13 05:09 PM

Originally Posted By: Markan
Hpasp, in the Shilka manual on 28 page it state "When the required electrical power for the SRP operation is available, a yellow (1) lamp will illuminate." But in the sim it will illuminate only after you switch POWER switch to on. I don't know is this a bug in the sim, error in the manual or it should be like that?
wave


Its a bug in the software, I will fix it.
That lamp shows that the required Voltages are available to switch on the SRP.
Posted By: piston79

Re: Bug reports - 01/24/13 10:11 PM

A bug:
Click to reveal..
Practice target:
Meteor-1
Meteor-1
Meteor-1
Meteor-1
Meteor-1

ZSU-23-4V1



00:02:22 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1542m
Target azimuth: 234°
Target elevation: 6°
Tu: 2.5s

00:02:23 ZSU-23-4V1 closed fire, and shot 68pcs.


00:02:24 Practice target Meteor-1 killed by OFZT.


00:02:25 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1508m
Target azimuth: 233°
Target elevation: 7°
Tu: 2.4s

00:02:25 Practice target Meteor-1 killed by OFZT.

00:02:25 Practice target Meteor-1 killed by OFZT.

00:02:26 Practice target Meteor-1 killed by OFZT.

00:02:26 Practice target Meteor-1 killed by OFZT.

00:02:26 ZSU-23-4V1 closed fire, and shot 108pcs.



00:04:15 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1958m
Target azimuth: 239°
Target elevation: 4°
Tu: 3.6s

00:04:15 ZSU-23-4V1 closed fire, and shot 124pcs.



00:04:15 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1950m
Target azimuth: 239°
Target elevation: 4°
Tu: 3.5s

00:04:16 ZSU-23-4V1 closed fire, and shot 140pcs.



00:04:17 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1937m
Target azimuth: 239°
Target elevation: 4°
Tu: 3.5s

00:04:17 ZSU-23-4V1 closed fire, and shot 172pcs.


00:04:21 Practice target Meteor-1 hit by BZT.


00:04:29 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1810m
Target azimuth: 235°
Target elevation: 4°
Tu: 3.2s

00:04:29 ZSU-23-4V1 closed fire, and shot 192pcs.



00:04:29 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1807m
Target azimuth: 235°
Target elevation: 4°
Tu: 3.1s

00:04:29 ZSU-23-4V1 closed fire, and shot 208pcs.



00:04:29 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1802m
Target azimuth: 235°
Target elevation: 4°
Tu: 3.1s

00:04:29 ZSU-23-4V1 closed fire, and shot 220pcs.



00:04:30 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1794m
Target azimuth: 235°
Target elevation: 5°
Tu: 3.1s

00:04:31 ZSU-23-4V1 closed fire, and shot 264pcs.



00:04:52 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1527m
Target azimuth: 229°
Target elevation: 5°
Tu: 2.4s

00:04:54 ZSU-23-4V1 closed fire, and shot 348pcs.


00:04:55 Practice target Meteor-1 killed by OFZT.

00:04:55 Practice target Meteor-1 killed by OFZT.


00:04:56 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1499m
Target azimuth: 229°
Target elevation: 5°
Tu: 2.4s

00:04:56 Practice target Meteor-1 killed by OFZT.

00:04:56 ZSU-23-4V1 closed fire, and shot 372pcs.



00:06:39 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1519m
Target azimuth: 207°
Target elevation: 7°
Tu: 2.4s

00:06:40 ZSU-23-4V1 closed fire, and shot 460pcs.


00:06:41 Practice target Meteor-1 killed by OFZT.

00:06:42 Practice target Meteor-1 killed by OFZT.

00:06:42 Practice target Meteor-1 killed by OFZT.

00:06:43 Practice target Meteor-1 killed by OFZT.


00:06:55 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1480m
Target azimuth: 209°
Target elevation: 7°
Tu: 2.4s

00:06:55 ZSU-23-4V1 closed fire, and shot 472pcs.



00:06:59 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1480m
Target azimuth: 209°
Target elevation: 7°
Tu: 2.4s

00:06:59 ZSU-23-4V1 closed fire, and shot 484pcs.



00:07:00 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1480m
Target azimuth: 209°
Target elevation: 7°
Tu: 2.4s

00:07:00 ZSU-23-4V1 closed fire, and shot 496pcs.



00:07:03 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1480m
Target azimuth: 209°
Target elevation: 7°
Tu: 2.4s

00:07:03 ZSU-23-4V1 closed fire, and shot 508pcs.


+++++++++++++++++
00:08:03, SNR ON AIR



00:08:07 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1663m
Target azimuth: 239°
Target elevation: 4°
Tu: 2.8s

00:08:07 ZSU-23-4V1 closed fire, and shot 520pcs.



00:08:08 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1651m
Target azimuth: 239°
Target elevation: 4°
Tu: 2.7s

00:08:08 ZSU-23-4V1 closed fire, and shot 536pcs.


00:08:10 Practice target Meteor-1 hit by BZT.


00:08:11 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1597m
Target azimuth: 237°
Target elevation: 4°
Tu: 2.6s

00:08:13 ZSU-23-4V1 closed fire, and shot 596pcs.



00:08:22 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1439m
Target azimuth: 233°
Target elevation: 5°
Tu: 2.2s

00:08:24 ZSU-23-4V1 closed fire, and shot 672pcs.


00:08:25 Practice target Meteor-1 killed by OFZT.

00:08:25 Practice target Meteor-1 killed by OFZT.


00:10:08 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1852m
Target azimuth: 239°
Target elevation: 4°
Tu: 3.2s

00:10:11 ZSU-23-4V1 closed fire, and shot 812pcs.


00:10:12 Practice target Meteor-1 killed by OFZT.

00:10:13 Practice target Meteor-1 killed by OFZT.

00:10:14 Practice target Meteor-1 killed by OFZT.

00:10:14 Practice target Meteor-1 killed by OFZT.


00:10:42 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:42 ZSU-23-4V1 closed fire, and shot 820pcs.



00:10:42 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:42 ZSU-23-4V1 closed fire, and shot 828pcs.



00:10:43 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:43 ZSU-23-4V1 closed fire, and shot 836pcs.



00:10:43 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:44 ZSU-23-4V1 closed fire, and shot 844pcs.



00:10:44 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:44 ZSU-23-4V1 closed fire, and shot 848pcs.



00:10:45 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:45 ZSU-23-4V1 closed fire, and shot 852pcs.



00:10:45 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:45 ZSU-23-4V1 closed fire, and shot 856pcs.



00:10:46 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:46 ZSU-23-4V1 closed fire, and shot 864pcs.



00:10:56 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:56 ZSU-23-4V1 closed fire, and shot 872pcs.



00:10:57 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:57 ZSU-23-4V1 closed fire, and shot 880p
cs.


Total, SNR On Air Time: 5min 37sec



Watching video of Faroukh, I haven't see the "ZU" red light to goes on on my "Shilka"...I was able to shoot even when target was killed, (that's where 1800 m shots come, I think..).

Oh, and a suggestion - as "Shilka has a small range, why we using big scale ploating boards?
Posted By: Hpasp

Re: Bug reports - 01/25/13 07:42 AM

Originally Posted By: piston79
A bug:
Click to reveal..
Practice target:
Meteor-1
Meteor-1
Meteor-1
Meteor-1
Meteor-1

ZSU-23-4V1



00:02:22 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1542m
Target azimuth: 234°
Target elevation: 6°
Tu: 2.5s

00:02:23 ZSU-23-4V1 closed fire, and shot 68pcs.


00:02:24 Practice target Meteor-1 killed by OFZT.


00:02:25 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1508m
Target azimuth: 233°
Target elevation: 7°
Tu: 2.4s

00:02:25 Practice target Meteor-1 killed by OFZT.

00:02:25 Practice target Meteor-1 killed by OFZT.

00:02:26 Practice target Meteor-1 killed by OFZT.

00:02:26 Practice target Meteor-1 killed by OFZT.

00:02:26 ZSU-23-4V1 closed fire, and shot 108pcs.



00:04:15 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1958m
Target azimuth: 239°
Target elevation: 4°
Tu: 3.6s

00:04:15 ZSU-23-4V1 closed fire, and shot 124pcs.



00:04:15 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1950m
Target azimuth: 239°
Target elevation: 4°
Tu: 3.5s

00:04:16 ZSU-23-4V1 closed fire, and shot 140pcs.



00:04:17 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1937m
Target azimuth: 239°
Target elevation: 4°
Tu: 3.5s

00:04:17 ZSU-23-4V1 closed fire, and shot 172pcs.


00:04:21 Practice target Meteor-1 hit by BZT.


00:04:29 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1810m
Target azimuth: 235°
Target elevation: 4°
Tu: 3.2s

00:04:29 ZSU-23-4V1 closed fire, and shot 192pcs.



00:04:29 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1807m
Target azimuth: 235°
Target elevation: 4°
Tu: 3.1s

00:04:29 ZSU-23-4V1 closed fire, and shot 208pcs.



00:04:29 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1802m
Target azimuth: 235°
Target elevation: 4°
Tu: 3.1s

00:04:29 ZSU-23-4V1 closed fire, and shot 220pcs.



00:04:30 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1794m
Target azimuth: 235°
Target elevation: 5°
Tu: 3.1s

00:04:31 ZSU-23-4V1 closed fire, and shot 264pcs.



00:04:52 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1527m
Target azimuth: 229°
Target elevation: 5°
Tu: 2.4s

00:04:54 ZSU-23-4V1 closed fire, and shot 348pcs.


00:04:55 Practice target Meteor-1 killed by OFZT.

00:04:55 Practice target Meteor-1 killed by OFZT.


00:04:56 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1499m
Target azimuth: 229°
Target elevation: 5°
Tu: 2.4s

00:04:56 Practice target Meteor-1 killed by OFZT.

00:04:56 ZSU-23-4V1 closed fire, and shot 372pcs.



00:06:39 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1519m
Target azimuth: 207°
Target elevation: 7°
Tu: 2.4s

00:06:40 ZSU-23-4V1 closed fire, and shot 460pcs.


00:06:41 Practice target Meteor-1 killed by OFZT.

00:06:42 Practice target Meteor-1 killed by OFZT.

00:06:42 Practice target Meteor-1 killed by OFZT.

00:06:43 Practice target Meteor-1 killed by OFZT.


00:06:55 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1480m
Target azimuth: 209°
Target elevation: 7°
Tu: 2.4s

00:06:55 ZSU-23-4V1 closed fire, and shot 472pcs.



00:06:59 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1480m
Target azimuth: 209°
Target elevation: 7°
Tu: 2.4s

00:06:59 ZSU-23-4V1 closed fire, and shot 484pcs.



00:07:00 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1480m
Target azimuth: 209°
Target elevation: 7°
Tu: 2.4s

00:07:00 ZSU-23-4V1 closed fire, and shot 496pcs.



00:07:03 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1480m
Target azimuth: 209°
Target elevation: 7°
Tu: 2.4s

00:07:03 ZSU-23-4V1 closed fire, and shot 508pcs.


+++++++++++++++++
00:08:03, SNR ON AIR



00:08:07 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1663m
Target azimuth: 239°
Target elevation: 4°
Tu: 2.8s

00:08:07 ZSU-23-4V1 closed fire, and shot 520pcs.



00:08:08 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1651m
Target azimuth: 239°
Target elevation: 4°
Tu: 2.7s

00:08:08 ZSU-23-4V1 closed fire, and shot 536pcs.


00:08:10 Practice target Meteor-1 hit by BZT.


00:08:11 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1597m
Target azimuth: 237°
Target elevation: 4°
Tu: 2.6s

00:08:13 ZSU-23-4V1 closed fire, and shot 596pcs.



00:08:22 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1439m
Target azimuth: 233°
Target elevation: 5°
Tu: 2.2s

00:08:24 ZSU-23-4V1 closed fire, and shot 672pcs.


00:08:25 Practice target Meteor-1 killed by OFZT.

00:08:25 Practice target Meteor-1 killed by OFZT.


00:10:08 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1852m
Target azimuth: 239°
Target elevation: 4°
Tu: 3.2s

00:10:11 ZSU-23-4V1 closed fire, and shot 812pcs.


00:10:12 Practice target Meteor-1 killed by OFZT.

00:10:13 Practice target Meteor-1 killed by OFZT.

00:10:14 Practice target Meteor-1 killed by OFZT.

00:10:14 Practice target Meteor-1 killed by OFZT.


00:10:42 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:42 ZSU-23-4V1 closed fire, and shot 820pcs.



00:10:42 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:42 ZSU-23-4V1 closed fire, and shot 828pcs.



00:10:43 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:43 ZSU-23-4V1 closed fire, and shot 836pcs.



00:10:43 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:44 ZSU-23-4V1 closed fire, and shot 844pcs.



00:10:44 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:44 ZSU-23-4V1 closed fire, and shot 848pcs.



00:10:45 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:45 ZSU-23-4V1 closed fire, and shot 852pcs.



00:10:45 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:45 ZSU-23-4V1 closed fire, and shot 856pcs.



00:10:46 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:46 ZSU-23-4V1 closed fire, and shot 864pcs.



00:10:56 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:56 ZSU-23-4V1 closed fire, and shot 872pcs.



00:10:57 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1800m
Target azimuth: 238°
Target elevation: 4°
Tu: 3.2s

00:10:57 ZSU-23-4V1 closed fire, and shot 880p
cs.


Total, SNR On Air Time: 5min 37sec



Watching video of Faroukh, I haven't see the "ZU" red light to goes on on my "Shilka"...I was able to shoot even when target was killed, (that's where 1800 m shots come, I think..).

Oh, and a suggestion - as "Shilka has a small range, why we using big scale ploating boards?


As far as I know, the PU-12 used the generic air picture generated by the Army level radio technical troops.
They worked on large scale, and not transmitted PU12 location specific information over the telecode channel.
Good sites about the PU12
http://forum.valka.cz/viewtopic.php/t/23991
http://www.flak11.de/PU12Start.htm
http://www.rwd-mb3.de/pages/pu12.htm
Posted By: piston79

Re: Bug reports - 01/25/13 10:52 AM

How about AAR (bolded paragraph)? I didn't shoot so much... nope
Posted By: Lieste

Re: Bug reports - 01/25/13 12:04 PM

So are you saying that it recorded bursts you didn't take, or discussing how many rounds expended?

Each of those bolded bursts is only 1-2 rounds (unless I missed one that was significantly longer) per tube, which is about the minimum possible to fire, if the number of bursts made is correct.

The shots fired is a cumulative number, not a "rounds in the burst" count.
Posted By: farokh

Re: Bug reports - 01/25/13 12:59 PM

Originally Posted By: Lieste
So are you saying that it recorded bursts you didn't take, or discussing how many rounds expended?

Each of those bolded bursts is only 1-2 rounds (unless I missed one that was significantly longer) per tube, which is about the minimum possible to fire, if the number of bursts made is correct.

The shots fired is a cumulative number, not a "rounds in the burst" count.


i killed one target from 2100m with one personal burst !
when u push the space for 1 second... shilka can fire in this period time around 55 bullets!
i guess best burst for shilka , push space for 1 or 1.5 second (55 till 70) bullets per each firing !

Posted By: Lieste

Re: Bug reports - 01/25/13 02:15 PM

Piston fired 12 bursts against the targets engaged. Of these only 8 were longer than 10 rounds per barrel, which I'd think was a reasonable minimum length for an engagement. 6 were only 3 rounds per barrel.

After engaging the targets he then expended (the bolded section) 17 rounds per barrel (around one second firing), in 10 bursts. These being one or two rounds per burst, sometimes twice in one second.

If this matches what was done, then there is no problem.
Posted By: Hpasp

Re: Bug reports - 01/25/13 07:31 PM

Originally Posted By: piston79
How about AAR (bolded paragraph)? I didn't shoot so much... nope


That is a bug, that will be also corrected.
The intention was to show the bullet count of each burst.
Posted By: piston79

Re: Bug reports - 01/25/13 07:55 PM

Originally Posted By: Lieste
After engaging the targets he then expended (the bolded section) 17 rounds per barrel (around one second firing), in 10 bursts. These being one or two rounds per burst, sometimes twice in one second.

If this matches what was done, then there is no problem.


Yes I had some bursts after killing the target, but not so many!!! Thanks for explanation about cumulative counting, dear Lieste, I didn't figure it out .... screwy

Dear Hpasp, do you need the 3D AAR about that case or you solve that bug completely?
Posted By: Hpasp

Re: Bug reports - 01/25/13 08:31 PM

Hopefully solved.

I plan to release an install full version, having all the fixes so far this weekend, so if you seen more bugs, don't be shy...
biggrin
Posted By: Mdore

Re: Bug reports - 01/26/13 02:10 PM

Possible bug in 0.926C

I'm not sure if this is a bug, or if it's how it's supposed to be.

If memory mode switch is on, and the target is shot and disintegrates, our radar loses target lock and the red light comes on showing it's in memory mode.

But the red light doesn't come on if the target disappears for other reasons. Like flying out of range, or hitting the ground.

Is that how it's supposed to work? Because the radar is still moving by itself even after the target is out of range, like it's still tracking it, or tracking in memory mode.
Posted By: WhoCares

Re: Bug reports - 01/26/13 06:46 PM

There is a minor bug in the 3D-AAR, placing some kill "waypoints" at coordinates 0-0 in 0.926c.

From Tripoli Shilka mission:
First, as a little show-off, 5 kills, Remit 32/33 and Karma 51/52/53.
Click to reveal..


Here the same 3D AAR zoomed out - maybe once a target is killed further hits are registered with 0-0 coordinates?
As a little note, there are actually more than the three hits shown there registered at this location.
Click to reveal..


Click to reveal..
2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Tripoli.

Targets:
Bab al-Aziziyah barracks - 6 F-111F Aardvark, each armed with 4 GBU-10 LGB
Murat Sidi Bilal Naval base - 3 F-111F Aardvark, each armed with 4 GBU-10 LGB
Tripoli AFB - 5 F-111F Aardvark, each armed with 12 Mk.82/BSU-49 high-drag bombs

Supporting force:
6 A-7E Corsair-II SEAD (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
4 F-14A Tomcat CAP (VF-33 Starfighters, VF-102 Diamondbacks from the CV-66 USS America)
3 EF-111A Raven ECM
1 EA-6B Prowler ECM (VMAQ-2 Playboys from the CV-43 USS America)

ZSU-23-4V1

00:00:36, F-111F Remit-31 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.


00:01:28 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4022m
Target azimuth: 267°
Target elevation: 1°
Tu: 5.8s

00:01:29 ZSU-23-4V1 closed fire, and shot 36pcs.



00:01:30 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3698m
Target azimuth: 270°
Target elevation: 1°
Tu: 5.4s

00:01:30 ZSU-23-4V1 closed fire, and shot 44pcs.



00:01:31 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3368m
Target azimuth: 274°
Target elevation: 1°
Tu: 5.1s

00:01:32 ZSU-23-4V1 closed fire, and shot 56pcs.



00:01:32 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3043m
Target azimuth: 280°
Target elevation: 1°
Tu: 4.8s

00:01:33 ZSU-23-4V1 closed fire, and shot 52pcs.


00:01:37 F-111F Remit-32 killed by OFZT.

00:01:37 F-111F Remit-32 killed by OFZT.
00:01:43, F-111F Remit-33 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.


00:02:02 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3956m
Target azimuth: 267°
Target elevation: 12°
Tu: 5.9s

00:02:03 ZSU-23-4V1 closed fire, and shot 44pcs.



00:02:04 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3549m
Target azimuth: 271°
Target elevation: 14°
Tu: 5.5s

00:02:05 ZSU-23-4V1 closed fire, and shot 48pcs.



00:02:06 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3183m
Target azimuth: 278°
Target elevation: 15°
Tu: 5.2s

00:02:07 ZSU-23-4V1 closed fire, and shot 52pcs.



00:02:07 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2857m
Target azimuth: 286°
Target elevation: 17°
Tu: 5.2s

00:02:08 ZSU-23-4V1 closed fire, and shot 52pcs.


00:02:10 F-111F Remit-33 killed by OFZT.

00:02:10 F-111F Remit-33 killed by BZT.

00:02:10 F-111F Remit-33 killed by OFZT.

00:02:10 F-111F Remit-33 killed by OFZT.
00:03:55, F-111F Karma-51bombed the French Embassy, with 4 GBU-10 LGB..


00:04:13 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4227m
Target azimuth: 260°
Target elevation: 11°
Tu: 6.3s

00:04:14 ZSU-23-4V1 closed fire, and shot 44pcs.



00:04:15 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3826m
Target azimuth: 264°
Target elevation: 13°
Tu: 5.7s

00:04:16 ZSU-23-4V1 closed fire, and shot 48pcs.



00:04:16 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3450m
Target azimuth: 268°
Target elevation: 14°
Tu: 5.3s

00:04:17 ZSU-23-4V1 closed fire, and shot 56pcs.



00:04:18 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3090m
Target azimuth: 275°
Target elevation: 16°
Tu: 5s

00:04:19 ZSU-23-4V1 closed fire, and shot 48pcs.



00:04:19 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2822m
Target azimuth: 282°
Target elevation: 17°
Tu: 5s

00:04:20 F-111F Karma-51 killed by OFZT.

00:04:20 F-111F Karma-51 killed by OFZT.

00:04:20 ZSU-23-4V1 closed fire, and shot 28pcs.


00:04:22 F-111F Karma-51 killed by OFZT.

00:04:22 F-111F Karma-51 killed by OFZT.

00:04:22 F-111F Karma-51 killed by BZT.

00:04:22 F-111F Karma-51 killed by OFZT.


00:04:43 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4365m
Target azimuth: 272°
Target elevation: 1°
Tu: 6.4s

00:04:44 ZSU-23-4V1 closed fire, and shot 48pcs.



00:04:45 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3920m
Target azimuth: 276°
Target elevation: 1°
Tu: 5.8s

00:04:46 ZSU-23-4V1 closed fire, and shot 56pcs.



00:04:47 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3527m
Target azimuth: 280°
Target elevation: 1°
Tu: 5.3s

00:04:47 ZSU-23-4V1 closed fire, and shot 52pcs.



00:04:48 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3170m
Target azimuth: 286°
Target elevation: 1°
Tu: 5s

00:04:49 ZSU-23-4V1 closed fire, and shot 52pcs.



00:04:49 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2901m
Target azimuth: 292°
Target elevation: 1°
Tu: 5s

00:04:50 ZSU-23-4V1 closed fire, and shot 56pcs.


00:04:51 F-111F Karma-52 killed by OFZT.


00:05:18 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4463m
Target azimuth: 271°
Target elevation: 0°
Tu: 6.5s

00:05:19 ZSU-23-4V1 closed fire, and shot 52pcs.



00:05:20 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4013m
Target azimuth: 275°
Target elevation: 1°
Tu: 5.9s

00:05:21 ZSU-23-4V1 closed fire, and shot 52pcs.



00:05:22 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3614m
Target azimuth: 279°
Target elevation: 1°
Tu: 5.4s

00:05:23 ZSU-23-4V1 closed fire, and shot 60pcs.



00:05:23 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3247m
Target azimuth: 284°
Target elevation: 1°
Tu: 5.1s

00:05:24 ZSU-23-4V1 closed fire, and shot 52pcs.



00:05:24 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2947m
Target azimuth: 291°
Target elevation: 1°
Tu: 5s

00:05:26 ZSU-23-4V1 closed fire, and shot 64pcs.


00:05:26 F-111F Karma-53 hit by OFZT.

00:05:26 F-111F Karma-53 killed by BZT.


00:05:26 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2646m
Target azimuth: 301°
Target elevation: 1°
Tu: 6s

00:05:26 ZSU-23-4V1 closed fire, and shot 12pcs.

00:05:36, F-111F Jewel-61 bombed Murat Sidi Bilal Naval base, with 4 GBU-10 LGB.
Posted By: piston79

Re: Bug reports - 01/26/13 07:45 PM

Please, check this:

http://dox.bg/files/dw?a=b546fcb3b1

Is it normal for 3 of meteors to dissapeared just like that?
Posted By: Hpasp

Re: Bug reports - 01/31/13 06:23 PM

checking those...
Posted By: piston79

Re: Bug reports - 02/03/13 02:52 PM

About SA-5:

Don't think it is a bug, but a non-logical behaviour for me.
After target (P~0 in my particular case) was tracked by the CVM (AS-RPC), missiles were launched and go for the target. As target was maintaining constant speed, I switched off the AS-RPC and RPC continued to iluminate the target without automated tracking on any coordinate (V,epsilon, beta, distance). At this moment KRO signals appeared on tne indicator, which, I believe is not logical (the target was completely in the middle of Doppler spectrograph screen!). All three missiles missed (no mather that they passed <100 meters from the target). I double checked situation and when in no AS mode I switched to AS-3, KRO signals dissapeared... In fact in one of mine experiments I switched AS-3 in the moment, when the last missile passed the target (I thought she was lost), and at AAR it appears that target was destroyed with 1 m miss, but in 3DAAR it was not so:

3D AAR


Click to reveal..
13:46 24th of March, 1986.
Operation Prairie Fire

S-200VE Vega-E


+++++++++++++++++
00:01:43, SNR ON AIR


00:04:22, Missile launched from launcher-1
Target distance: 89km
Target azimuth: 12°
Target elevation: 2°
Target angular speed: 275m/s (0.9 Mach)
Target altitude: 4.5km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 38.6dB


00:04:27, Missile launched from launcher-2
Target distance: 88km
Target azimuth: 12°
Target elevation: 2°
Target angular speed: 275m/s (0.9 Mach)
Target altitude: 4.5km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 38.7dB


00:04:32, Missile launched from launcher-3
Target distance: 86km
Target azimuth: 12°
Target elevation: 2°
Target angular speed: 275m/s (0.9 Mach)
Target altitude: 4.5km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 38.9dB


00:05:41, Missile exploded
F-14B Tomcat killed by SAM. (miss distance: 1m)

Total, SNR On Air Time: 4min 10sec

Posted By: Hpasp

Re: Bug reports - 02/03/13 07:32 PM

Originally Posted By: piston79
About SA-5:

Don't think it is a bug, but a non-logical behaviour for me.
After target (P~0 in my particular case) was tracked by the CVM (AS-RPC), missiles were launched and go for the target. As target was maintaining constant speed, I switched off the AS-RPC and RPC continued to iluminate the target without automated tracking on any coordinate (V,epsilon, beta, distance). At this moment KRO signals appeared on tne indicator, which, I believe is not logical (the target was completely in the middle of Doppler spectrograph screen!). All three missiles missed (no mather that they passed <100 meters from the target). I double checked situation and when in no AS mode I switched to AS-3, KRO signals dissapeared... In fact in one of mine experiments I switched AS-3 in the moment, when the last missile passed the target (I thought she was lost), and at AAR it appears that target was destroyed with 1 m miss, but in 3DAAR it was not so:

3D AAR


Click to reveal..
13:46 24th of March, 1986.
Operation Prairie Fire

S-200VE Vega-E


+++++++++++++++++
00:01:43, SNR ON AIR


00:04:22, Missile launched from launcher-1
Target distance: 89km
Target azimuth: 12°
Target elevation: 2°
Target angular speed: 275m/s (0.9 Mach)
Target altitude: 4.5km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 38.6dB


00:04:27, Missile launched from launcher-2
Target distance: 88km
Target azimuth: 12°
Target elevation: 2°
Target angular speed: 275m/s (0.9 Mach)
Target altitude: 4.5km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 38.7dB


00:04:32, Missile launched from launcher-3
Target distance: 86km
Target azimuth: 12°
Target elevation: 2°
Target angular speed: 275m/s (0.9 Mach)
Target altitude: 4.5km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 38.9dB


00:05:41, Missile exploded
F-14B Tomcat killed by SAM. (miss distance: 1m)

Total, SNR On Air Time: 4min 10sec



There is an inherited issue of these scenarios.

Currently the SAM Simulator only simulates FM modulated CW noise jamming.

In reality, there are ...

Denial Jamming:
- Barrage Noise Jamming
- Spot Noise Jamming
- Swept Spot Noise Jamming
- Cover Pulse Noise Jamming
- Modulated Noise Jamming

Deceptive Jamming:
- False Target Jamming
- Range Deception Jamming (Range Gate Pull Off)
- Angle Deception Jamming (Inverse Amplitude Modulation, Inverse Gain Jamming, Swept Square Wave Jamming)
- Velocity Deception Jamming (Velocity Gate Pull Off, Doppler Noise, Narrow-band Doppler Noise, Doppler False Targets)
- Mono-pulse Deception Jamming (Cross Polarization Jamming, Cross Eye Jamming)

... these methods are visible and effective on different SAM systems, but not simulated yet.
Posted By: piston79

Re: Bug reports - 02/03/13 07:46 PM

Originally Posted By: Hpasp

There is an inherited issue of these scenarios.

Currently the SAM Simulator only simulates FM modulated CW noise jamming.

In reality, there are ...


But there is no jamming here... nope
Posted By: farokh

Re: Bug reports - 02/03/13 09:10 PM

i guess i feel one bug in shilka mechanism ! cool

when i opened fire on target ! i was seat on commander position , and (memory mode) lamp. be ON and after few moments (memory mode) lamp turn ON again

my first damage was by BZT and then OFZT, im not sure but BZT bullets do no has any fuse to detonate and send signal to shilka (gun dish) ... right hpasp?... if u are not sure... just test and try to kill one target with BZT first

! based on bellow AAR ! (just check the end of aar)

Click to reveal..
2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Tripoli.

Targets:
Bab al-Aziziyah barracks - 6 F-111F Aardvark, each armed with 4 GBU-10 LGB
Murat Sidi Bilal Naval base - 3 F-111F Aardvark, each armed with 4 GBU-10 LGB
Tripoli AFB - 5 F-111F Aardvark, each armed with 12 Mk.82/BSU-49 high-drag bombs

Supporting force:
6 A-7E Corsair-II SEAD (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
4 F-14A Tomcat CAP (VF-33 Starfighters, VF-102 Diamondbacks from the CV-66 USS America)
3 EF-111A Raven ECM
1 EA-6B Prowler ECM (VMAQ-2 Playboys from the CV-43 USS America)

ZSU-23-4V1

00:00:36, F-111F Remit-31 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.


00:01:26 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4591m
Target azimuth: 263°
Target elevation: 0°
Tu: 6.7s

00:01:27 ZSU-23-4V1 closed fire, and shot 48pcs.



00:01:28 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4190m
Target azimuth: 266°
Target elevation: 1°
Tu: 6.1s

00:01:29 ZSU-23-4V1 closed fire, and shot 52pcs.



00:01:31 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3392m
Target azimuth: 274°
Target elevation: 1°
Tu: 5.1s

00:01:32 ZSU-23-4V1 closed fire, and shot 96pcs.



00:01:33 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2897m
Target azimuth: 283°
Target elevation: 1°
Tu: 4.7s

00:01:34 ZSU-23-4V1 closed fire, and shot 80pcs.



00:01:35 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2558m
Target azimuth: 295°
Target elevation: 1°
Tu: 5s

00:01:36 ZSU-23-4V1 closed fire, and shot 68pcs.



00:01:38 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2379m
Target azimuth: 318°
Target elevation: 1°
Tu: 7.9s

00:01:40 ZSU-23-4V1 closed fire, and shot 104pcs.

00:01:43, F-111F Remit-33 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.


00:01:57 ZSU-23-4V1 opened fire by all tubes.
Target distance: 5579m
Target azimuth: 257°
Target elevation: 8°
Tu: 8.4s

00:01:58 ZSU-23-4V1 closed fire, and shot 60pcs.



00:02:00 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4674m
Target azimuth: 261°
Target elevation: 10°
Tu: 6.9s

00:02:01 ZSU-23-4V1 closed fire, and shot 60pcs.



00:02:01 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4253m
Target azimuth: 264°
Target elevation: 11°
Tu: 6.4s

00:02:02 ZSU-23-4V1 closed fire, and shot 68pcs.



00:02:04 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3647m
Target azimuth: 270°
Target elevation: 13°
Tu: 5.6s

00:02:05 ZSU-23-4V1 closed fire, and shot 60pcs.


00:02:07 F-111F Remit-33 hit by BZT.

00:02:07 F-111F Remit-33 killed by OFZT

Posted By: farokh

Re: Bug reports - 02/05/13 08:34 PM

hit by OFZT ????????? jawdrop

Click to reveal..
2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Tripoli.

Targets:
Bab al-Aziziyah barracks - 6 F-111F Aardvark, each armed with 4 GBU-10 LGB
Murat Sidi Bilal Naval base - 3 F-111F Aardvark, each armed with 4 GBU-10 LGB
Tripoli AFB - 5 F-111F Aardvark, each armed with 12 Mk.82/BSU-49 high-drag bombs

Supporting force:
6 A-7E Corsair-II SEAD (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
4 F-14A Tomcat CAP (VF-33 Starfighters, VF-102 Diamondbacks from the CV-66 USS America)
3 EF-111A Raven ECM
1 EA-6B Prowler ECM (VMAQ-2 Playboys from the CV-43 USS America)

ZSU-23-4V1

00:00:36, F-111F Remit-31 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.


00:01:25 ZSU-23-4V1 opened fire by all tubes.
Target distance: 5061m
Target azimuth: 260°
Target elevation: 0°
Tu: 7.4s

00:01:30 ZSU-23-4V1 closed fire, and shot 280pcs.



00:01:32 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3224m
Target azimuth: 277°
Target elevation: 1°
Tu: 4.9s

00:01:36 ZSU-23-4V1 closed fire, and shot 244pcs.


00:01:37 F-111F Remit-32 hit by OFZT.
00:01:43, F-111F Remit-33 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.


00:01:58 ZSU-23-4V1 opened fire by all tubes.
Target distance: 5080m
Target azimuth: 259°
Target elevation: 9°
Tu: 7.5s

00:02:07 F-111F Remit-33 hit by BZT.

00:02:07 F-111F Remit-33 killed by OFZT.

00:02:07 F-111F Remit-33 killed by OFZT.

00:02:07 ZSU-23-4V1 closed fire, and shot 500pcs.


00:02:09 F-111F Remit-33 killed by BZT.

00:02:10 F-111F Remit-33 killed by BZT.
Posted By: piston79

Re: Bug reports - 02/05/13 09:41 PM

Quote:
hit by OFZT???


It would be better to stop writting and start reading:

http://simhq.com/forum/ubbthreads.php/topics/3693913/Re_ZSU_23_4V1_Shilka#Post3693913

http://simhq.com/forum/ubbthreads.php/topics/3707348/Re_ZSU_23_4V1_Shilka#Post3707348
----------------

P.S. It would be a lot easier to find some info if some community members stop flooding the forum.... yep
Posted By: Wolfhound

Re: Bug reports - 02/19/13 05:32 PM

I'm using Windows XP with SAMSIM version 0.926C

Ok I spent quite a bit of time testing and observing the SA-2F at the Asuluk range against the very low flying high speed FB-111 and here is what I have found.

Asuluk range parameters:
Missiles = 6 x V750VU 11DU
Targets = 3 x RM-207M (Simulating FB-111s) launched at 1 minute intervals starting at T+00min 10sec
dm, m jamming = none
cm jamming = none

This image shows my I-64 (Q - button) set-up.



This image shows my I-62 (Z - button) set-up.

NOTE:
Because I'm engaging a target flying below 300m, the K3 I, II & III red lights are illuminated signifying that the radio proximity fuse for all three missile channels has been switched OFF. Leaving the radio fuses on (K3 I, II & III lights off), is supposed to confuse the missiles radio fuse as it will be flying close to the ground and most likely interference from ground clutter would cause a premature detonation.


This images shows a typical missile flyout with 'K' guidance (Half Lead Elevated By Constants), with the red K3 lights.

NOTE:
Missile launch is at 30Km, the missiles will always initially stabilise at 3.5 to 4 degrees to the right of the radar beam, as indicated on the azimuth (Beta) display. The 3 green lamps, elevation, range and azimuth signify that auto-tracking has been initiated in all 3 dimensions.


The following two images show the missile at 'end-game'.


NOTE:
The missile begins it's end-game intercept turn towards the target very late and as a result misses. This occurs about 90% of the time.
Regardless of target azimuth motion observed on the azimuth screen and the right PAA dial (black three pronged pointer), the missiles always fly to the right of the radar beam by approximately 3.5 to 4 degrees. This occurs even if the target is moving to the left, which means the missile is not leading the target in azimuth.



The following test is exactly the same as the above, but in this instance the K3 I, II & III radio fuse lamps are off indicating that the radio fuses on all three missile channels have been switched ON.

This image was taken a few seconds after missile launch, which occurred at 30Km.

NOTE:
On this occasion the target was flying to the left which was indicated on the azimuth display and right hand PAA dial. As can be seen the missile is leading the target by flying to the left of the radar beam. Had the target been flying to the right, the missile would lead it to the right as other tests have shown. This is not the case with the radio fuse inactive (K3 red lights ON).


This images shows the missile continuing it's fly-out and still leading the target.

NOTE:
The movement of the ground clutter to the right and the slight change of the right PAA indicator (showing 45 degrees whereas it was almost 50 degrees in the previous image above this one), illustrates the target is moving to the left.


This images shows the missile a few moments before impact. Again note the ground clutter and right PAA indicator.



This images shows the target and missile just after impact. The target was killed.

NOTE:
With the radio fuse ON (red K3 lamps OFF), 'K' guidance mode has a pK of 1.0!!!


Using 'YNP' guidance (Half-Lead) with the radio fuse ON, there is a chance the missile will 'disappear' a couple of seconds after launch (perhaps being lead into the ground by the target losing altitude). If the missile survives the first couple of seconds, it will lead the target correctly and score a kill.
Using 'YNP' guidance with the radio fuse OFF, there is a chance the missile will 'disappear' a couple of seconds after launch (perhaps being lead into the ground by the target losing altitude). If the missile survives the first couple of seconds, it will fly with a profile very similar to the images posted of 'K' guidance with radio fuse OFF. So it will always fly to the right of the radar beam and will not lead the target correctly. The chances of scoring a kill are extremely low.

Using T/T guidance (Three-Point) with or without selecting the missile radio fuse has exactly the same effect as 'K' guidance with the radio fuse on, with the exception that the missile will fly directly line of sight on the radar beam to the target. Pk is 1.0!!! This is the most effective mode.


1) So from all of these observations and comparisons we can see that switching the missiles radio fuse OFF (red K3 lamps on) is altering the flight profile of the missiles when used in conjunction with the 'K' and 'YNP' guidance modes.

2) Ground clutter has no effect on the radio fuse regardless of target altitude.

3) Missile pK seems to be far too high, against a high speed low altitude target.

A few other points:
a) Pausing the simulation doesn't pause the missiles gyro, so if you pause the sim just after selecting the 'prepare missile for launch' knob on the I-64 (Q - button) panel, after around 30 seconds (with the sim still paused) the missiles ready lamp on the I-62 (Z - panel) will illuminate.

b) The missiles appear to detonate at the range line on the elevation and azimuth scopes with the radio fuse ON, if auto-tracking is deselected in range and the range line moved downwards (closer in range than the target). If the range line is move upwards (further in range that the target), the missile will not detonate at the range line, but will pass it and disappear after a few seconds of flight.
Considering the missiles are flying with active radio fuses, their proximity to the ground or a target should cause detonation, not their proximity to the range line.

c) Ground clutter doesn't seem to have an effect on target tracking. Ground clutter can make it more difficult for the user to separate a target from the background, but not the radar. If the user by chance happens to have the elevation, range or azimuth lines on a target deep behind clutter, auto-tracking can begin. Ground clutter also doesn't cause a loss of of auto-tracking (break lock).

d) 'T/T' guidance mode seems to be far too effective.


Cheers
Posted By: piston79

Re: Bug reports - 02/19/13 06:04 PM

Originally Posted By: Wolfhound

b) The missiles appear to detonate at the range line on the elevation and azimuth scopes with the radio fuse ON, if auto-tracking is deselected in range and the range line moved downwards (closer in range than the target). If the range line is move upwards (further in range that the target), the missile will not detonate at the range line, but will pass it and disappear after a few seconds of flight.
Considering the missiles are flying with active radio fuses, their proximity to the ground or a target should cause detonation, not their proximity to the range line.


This is the prove that ground clutters HAS effect on the radiofuse.... Just before "hiting" the range boresight, missile received K3 command to switch on radiofuse, and it detonates, because got a clutter.... The upward movement of the boresight in a constant angle of the antena should lead to a bigger height, so no detonation after K3... I am not 100% sure that there's no bug, but I suggest a closer examination of the 3D AAR...

Originally Posted By: Wolfhound
c) Ground clutter doesn't seem to have an effect on target tracking. Ground clutter can make it more difficult for the user to separate a target from the background, but not the radar. If the user by chance happens to have the elevation, range or azimuth lines on a target deep behind clutter, auto-tracking can begin. Ground clutter also doesn't cause a loss of of auto-tracking (break lock).


I've asked such a question long time ago.. wink The answer is in the next version of SA-2 - "Volkhov"... Just switch the 5 km magnification screen... wink

EDIT:

I did some tests and it really DO HAVE a strange behaviour!
Posted By: Wolfhound

Re: Bug reports - 02/19/13 07:03 PM

Originally Posted By: piston79
This is the prove that ground clutters HAS effect on the radiofuse.... Just before "hiting" the range boresight, missile received K3 command to switch on radiofuse, and it detonates, because got a clutter.... The upward movement of the boresight in a constant angle of the antena should lead to a bigger height, so no detonation after K3... I am not 100% sure that there's no bug, but I suggest a closer examination of the 3D AAR...


Your correct piston79 smile. I thought the radio fuse was armed not long after the missile had left the launcher, but what your saying makes much more sense. Against high altitude targets, with the range line set to the bottom of the display, the missiles don't explode because they are being launched at a higher elevation, so by the time the fuse activates (when the sustainer falls of?) the missile is well out of ground clutter.
Against medium altitude targets, the missile is launched at a more shallow angle, so moving the range line to the bottom of the display causes detonation as the missile is in ground clutter.

I've noticed that playing around with the range line while a missile is in flight causes some problems. There seems to be a limited amount of time after which the missile no longer excepts guidance commands and sometimes just disappears.

Originally Posted By: piston79
I've asked such a question long time ago.. wink The answer is in the next version of SA-2 - "Volkhov"... Just switch the 5 km magnification screen... wink


After the Dvina, the Volkhov will be my next system smile
Posted By: Wolfhound

Re: Bug reports - 02/19/13 11:02 PM

Originally Posted By: piston79
I suggest a closer examination of the 3D AAR...

How do you set-up a 3D AAR?


Originally Posted By: piston79
EDIT:

I did some tests and it really DO HAVE a strange behaviour!

Do you mean the missiles flight path or the fuse?

Cheers
Posted By: Lieste

Re: Bug reports - 02/20/13 01:07 AM

Load the .GPX (or was it .KML ?) into Googleearth.

Then zoom to the layer and pan/zoom to the area of interest, stepping forwards/back to watch the progress of the aircraft/missiles.

Bear in mind that 'extreme' wiggliness seen from the launcher (or close by) is actually barely weaving when viewed from side/above ~ you should at least 'glance' at the end view before deciding how good the guidance has been.

There was a GE bug with how the elevation and speed graph was displayed (maximum greater than axes scale values), but SAMSIM is "correct", and the error lies in the external program.
Posted By: piston79

Re: Bug reports - 02/20/13 05:51 AM

Originally Posted By: Wolfhound
Do you mean the missiles flight path or the fuse?


The missile path...
Posted By: Hpasp

Re: Bug reports - 02/22/13 01:59 PM

Originally Posted By: Mdore
Possible bug in 0.926C

I'm not sure if this is a bug, or if it's how it's supposed to be.

If memory mode switch is on, and the target is shot and disintegrates, our radar loses target lock and the red light comes on showing it's in memory mode.

But the red light doesn't come on if the target disappears for other reasons. Like flying out of range, or hitting the ground.

Is that how it's supposed to work? Because the radar is still moving by itself even after the target is out of range, like it's still tracking it, or tracking in memory mode.


If the target flies out of the range, than the SRP cannot follow it.
(Its just a mechanical calculator, if you reached the end of the cog wheel, that it is it.)

If the target is at the negative limitation of the SRP, it will not be able to track it either.
Posted By: Hpasp

Re: Bug reports - 02/22/13 02:01 PM

Originally Posted By: WhoCares
There is a minor bug in the 3D-AAR, placing some kill "waypoints" at coordinates 0-0 in 0.926c.

From Tripoli Shilka mission:
First, as a little show-off, 5 kills, Remit 32/33 and Karma 51/52/53.
Click to reveal..


Here the same 3D AAR zoomed out - maybe once a target is killed further hits are registered with 0-0 coordinates?
As a little note, there are actually more than the three hits shown there registered at this location.
Click to reveal..


Click to reveal..
2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Tripoli.

Targets:
Bab al-Aziziyah barracks - 6 F-111F Aardvark, each armed with 4 GBU-10 LGB
Murat Sidi Bilal Naval base - 3 F-111F Aardvark, each armed with 4 GBU-10 LGB
Tripoli AFB - 5 F-111F Aardvark, each armed with 12 Mk.82/BSU-49 high-drag bombs

Supporting force:
6 A-7E Corsair-II SEAD (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
4 F-14A Tomcat CAP (VF-33 Starfighters, VF-102 Diamondbacks from the CV-66 USS America)
3 EF-111A Raven ECM
1 EA-6B Prowler ECM (VMAQ-2 Playboys from the CV-43 USS America)

ZSU-23-4V1

00:00:36, F-111F Remit-31 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.


00:01:28 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4022m
Target azimuth: 267°
Target elevation: 1°
Tu: 5.8s

00:01:29 ZSU-23-4V1 closed fire, and shot 36pcs.



00:01:30 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3698m
Target azimuth: 270°
Target elevation: 1°
Tu: 5.4s

00:01:30 ZSU-23-4V1 closed fire, and shot 44pcs.



00:01:31 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3368m
Target azimuth: 274°
Target elevation: 1°
Tu: 5.1s

00:01:32 ZSU-23-4V1 closed fire, and shot 56pcs.



00:01:32 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3043m
Target azimuth: 280°
Target elevation: 1°
Tu: 4.8s

00:01:33 ZSU-23-4V1 closed fire, and shot 52pcs.


00:01:37 F-111F Remit-32 killed by OFZT.

00:01:37 F-111F Remit-32 killed by OFZT.
00:01:43, F-111F Remit-33 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.


00:02:02 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3956m
Target azimuth: 267°
Target elevation: 12°
Tu: 5.9s

00:02:03 ZSU-23-4V1 closed fire, and shot 44pcs.



00:02:04 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3549m
Target azimuth: 271°
Target elevation: 14°
Tu: 5.5s

00:02:05 ZSU-23-4V1 closed fire, and shot 48pcs.



00:02:06 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3183m
Target azimuth: 278°
Target elevation: 15°
Tu: 5.2s

00:02:07 ZSU-23-4V1 closed fire, and shot 52pcs.



00:02:07 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2857m
Target azimuth: 286°
Target elevation: 17°
Tu: 5.2s

00:02:08 ZSU-23-4V1 closed fire, and shot 52pcs.


00:02:10 F-111F Remit-33 killed by OFZT.

00:02:10 F-111F Remit-33 killed by BZT.

00:02:10 F-111F Remit-33 killed by OFZT.

00:02:10 F-111F Remit-33 killed by OFZT.
00:03:55, F-111F Karma-51bombed the French Embassy, with 4 GBU-10 LGB..


00:04:13 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4227m
Target azimuth: 260°
Target elevation: 11°
Tu: 6.3s

00:04:14 ZSU-23-4V1 closed fire, and shot 44pcs.



00:04:15 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3826m
Target azimuth: 264°
Target elevation: 13°
Tu: 5.7s

00:04:16 ZSU-23-4V1 closed fire, and shot 48pcs.



00:04:16 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3450m
Target azimuth: 268°
Target elevation: 14°
Tu: 5.3s

00:04:17 ZSU-23-4V1 closed fire, and shot 56pcs.



00:04:18 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3090m
Target azimuth: 275°
Target elevation: 16°
Tu: 5s

00:04:19 ZSU-23-4V1 closed fire, and shot 48pcs.



00:04:19 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2822m
Target azimuth: 282°
Target elevation: 17°
Tu: 5s

00:04:20 F-111F Karma-51 killed by OFZT.

00:04:20 F-111F Karma-51 killed by OFZT.

00:04:20 ZSU-23-4V1 closed fire, and shot 28pcs.


00:04:22 F-111F Karma-51 killed by OFZT.

00:04:22 F-111F Karma-51 killed by OFZT.

00:04:22 F-111F Karma-51 killed by BZT.

00:04:22 F-111F Karma-51 killed by OFZT.


00:04:43 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4365m
Target azimuth: 272°
Target elevation: 1°
Tu: 6.4s

00:04:44 ZSU-23-4V1 closed fire, and shot 48pcs.



00:04:45 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3920m
Target azimuth: 276°
Target elevation: 1°
Tu: 5.8s

00:04:46 ZSU-23-4V1 closed fire, and shot 56pcs.



00:04:47 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3527m
Target azimuth: 280°
Target elevation: 1°
Tu: 5.3s

00:04:47 ZSU-23-4V1 closed fire, and shot 52pcs.



00:04:48 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3170m
Target azimuth: 286°
Target elevation: 1°
Tu: 5s

00:04:49 ZSU-23-4V1 closed fire, and shot 52pcs.



00:04:49 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2901m
Target azimuth: 292°
Target elevation: 1°
Tu: 5s

00:04:50 ZSU-23-4V1 closed fire, and shot 56pcs.


00:04:51 F-111F Karma-52 killed by OFZT.


00:05:18 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4463m
Target azimuth: 271°
Target elevation: 0°
Tu: 6.5s

00:05:19 ZSU-23-4V1 closed fire, and shot 52pcs.



00:05:20 ZSU-23-4V1 opened fire by all tubes.
Target distance: 4013m
Target azimuth: 275°
Target elevation: 1°
Tu: 5.9s

00:05:21 ZSU-23-4V1 closed fire, and shot 52pcs.



00:05:22 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3614m
Target azimuth: 279°
Target elevation: 1°
Tu: 5.4s

00:05:23 ZSU-23-4V1 closed fire, and shot 60pcs.



00:05:23 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3247m
Target azimuth: 284°
Target elevation: 1°
Tu: 5.1s

00:05:24 ZSU-23-4V1 closed fire, and shot 52pcs.



00:05:24 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2947m
Target azimuth: 291°
Target elevation: 1°
Tu: 5s

00:05:26 ZSU-23-4V1 closed fire, and shot 64pcs.


00:05:26 F-111F Karma-53 hit by OFZT.

00:05:26 F-111F Karma-53 killed by BZT.


00:05:26 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2646m
Target azimuth: 301°
Target elevation: 1°
Tu: 6s

00:05:26 ZSU-23-4V1 closed fire, and shot 12pcs.

00:05:36, F-111F Jewel-61 bombed Murat Sidi Bilal Naval base, with 4 GBU-10 LGB.


Can you help to track this issue, I was trying to track it but was unable...
Posted By: Hpasp

Re: Bug reports - 02/22/13 02:02 PM

Originally Posted By: piston79
Please, check this:

http://dox.bg/files/dw?a=b546fcb3b1

Is it normal for 3 of meteors to dissapeared just like that?


Yes frown

I was unable to got more realistic flightplans so far.
If they were not hit, they were recycled in an elliptic path somehow...
Posted By: Wolfhound

Re: Bug reports - 02/23/13 04:05 PM

Originally Posted By: Lieste
Load the .GPX (or was it .KML ?) into Googleearth.

Then zoom to the layer and pan/zoom to the area of interest, stepping forwards/back to watch the progress of the aircraft/missiles.

Bear in mind that 'extreme' wiggliness seen from the launcher (or close by) is actually barely weaving when viewed from side/above ~ you should at least 'glance' at the end view before deciding how good the guidance has been.

There was a GE bug with how the elevation and speed graph was displayed (maximum greater than axes scale values), but SAMSIM is "correct", and the error lies in the external program.


It the .GPX or .KML a file saved with the after action report somewhere in the SAMSIM folder. If its not too much trouble, could you elaborate on the process of transporting them to Googleearth?

Thanks
Posted By: piston79

Re: Bug reports - 02/23/13 04:12 PM

Originally Posted By: Wolfhound


It the .GPX or .KML a file saved with the after action report somewhere in the SAMSIM folder. If its not too much trouble, could you elaborate on the process of transporting them to Googleearth?

Thanks


Just drop it in Google Earth and remove the bottom thick...
Posted By: CooLDoG

Re: Bug reports - 02/23/13 10:20 PM

file>open>(find samsim directory and click on the .gpx file)>open

untick bottom box as shown.
Posted By: Hpasp

Re: Bug reports - 02/24/13 12:02 PM

Originally Posted By: Wolfhound
Click to reveal..
I'm using Windows XP with SAMSIM version 0.926C

Ok I spent quite a bit of time testing and observing the SA-2F at the Asuluk range against the very low flying high speed FB-111 and here is what I have found.

Asuluk range parameters:
Missiles = 6 x V750VU 11DU
Targets = 3 x RM-207M (Simulating FB-111s) launched at 1 minute intervals starting at T+00min 10sec
dm, m jamming = none
cm jamming = none

This image shows my I-64 (Q - button) set-up.



This image shows my I-62 (Z - button) set-up.

NOTE:
Because I'm engaging a target flying below 300m, the K3 I, II & III red lights are illuminated signifying that the radio proximity fuse for all three missile channels has been switched OFF. Leaving the radio fuses on (K3 I, II & III lights off), is supposed to confuse the missiles radio fuse as it will be flying close to the ground and most likely interference from ground clutter would cause a premature detonation.


This images shows a typical missile flyout with 'K' guidance (Half Lead Elevated By Constants), with the red K3 lights.

NOTE:
Missile launch is at 30Km, the missiles will always initially stabilise at 3.5 to 4 degrees to the right of the radar beam, as indicated on the azimuth (Beta) display. The 3 green lamps, elevation, range and azimuth signify that auto-tracking has been initiated in all 3 dimensions.


The following two images show the missile at 'end-game'.


NOTE:
The missile begins it's end-game intercept turn towards the target very late and as a result misses. This occurs about 90% of the time.
Regardless of target azimuth motion observed on the azimuth screen and the right PAA dial (black three pronged pointer), the missiles always fly to the right of the radar beam by approximately 3.5 to 4 degrees. This occurs even if the target is moving to the left, which means the missile is not leading the target in azimuth.



The following test is exactly the same as the above, but in this instance the K3 I, II & III radio fuse lamps are off indicating that the radio fuses on all three missile channels have been switched ON.

This image was taken a few seconds after missile launch, which occurred at 30Km.

NOTE:
On this occasion the target was flying to the left which was indicated on the azimuth display and right hand PAA dial. As can be seen the missile is leading the target by flying to the left of the radar beam. Had the target been flying to the right, the missile would lead it to the right as other tests have shown. This is not the case with the radio fuse inactive (K3 red lights ON).


This images shows the missile continuing it's fly-out and still leading the target.

NOTE:
The movement of the ground clutter to the right and the slight change of the right PAA indicator (showing 45 degrees whereas it was almost 50 degrees in the previous image above this one), illustrates the target is moving to the left.


This images shows the missile a few moments before impact. Again note the ground clutter and right PAA indicator.



This images shows the target and missile just after impact. The target was killed.

NOTE:
With the radio fuse ON (red K3 lamps OFF), 'K' guidance mode has a pK of 1.0!!!


Using 'YNP' guidance (Half-Lead) with the radio fuse ON, there is a chance the missile will 'disappear' a couple of seconds after launch (perhaps being lead into the ground by the target losing altitude). If the missile survives the first couple of seconds, it will lead the target correctly and score a kill.
Using 'YNP' guidance with the radio fuse OFF, there is a chance the missile will 'disappear' a couple of seconds after launch (perhaps being lead into the ground by the target losing altitude). If the missile survives the first couple of seconds, it will fly with a profile very similar to the images posted of 'K' guidance with radio fuse OFF. So it will always fly to the right of the radar beam and will not lead the target correctly. The chances of scoring a kill are extremely low.

Using T/T guidance (Three-Point) with or without selecting the missile radio fuse has exactly the same effect as 'K' guidance with the radio fuse on, with the exception that the missile will fly directly line of sight on the radar beam to the target. Pk is 1.0!!! This is the most effective mode.


1) So from all of these observations and comparisons we can see that switching the missiles radio fuse OFF (red K3 lamps on) is altering the flight profile of the missiles when used in conjunction with the 'K' and 'YNP' guidance modes.

2) Ground clutter has no effect on the radio fuse regardless of target altitude.

3) Missile pK seems to be far too high, against a high speed low altitude target.

A few other points:
a) Pausing the simulation doesn't pause the missiles gyro, so if you pause the sim just after selecting the 'prepare missile for launch' knob on the I-64 (Q - button) panel, after around 30 seconds (with the sim still paused) the missiles ready lamp on the I-62 (Z - panel) will illuminate.

b) The missiles appear to detonate at the range line on the elevation and azimuth scopes with the radio fuse ON, if auto-tracking is deselected in range and the range line moved downwards (closer in range than the target). If the range line is move upwards (further in range that the target), the missile will not detonate at the range line, but will pass it and disappear after a few seconds of flight.
Considering the missiles are flying with active radio fuses, their proximity to the ground or a target should cause detonation, not their proximity to the range line.

c) Ground clutter doesn't seem to have an effect on target tracking. Ground clutter can make it more difficult for the user to separate a target from the background, but not the radar. If the user by chance happens to have the elevation, range or azimuth lines on a target deep behind clutter, auto-tracking can begin. Ground clutter also doesn't cause a loss of of auto-tracking (break lock).

d) 'T/T' guidance mode seems to be far too effective.


Cheers


Great bug-finding!!!

1, took quite a while to found, and correct.
It affected UPR and K method in case of K3, with the Dvina/Volhov/Neva systems.
(same code, from several years ago)

2, Still checking. (I'm pretty sure, that it was working some years ago...)

3, That target is flying in a straight path.
In case of maneuvering target, Pk is much lower.
(Just try the P15 in Poland, you will be surprised!)

a, It was never intended.

b, depending if the K3 was already emitted

c, it is similar to the reality. If a target got in the clutter, by playing gain, it was usually track-able.

d, T/T is the most effective method if the target is slow, and within the g limits of the missile.

The 9K33M3 OSA-AKM system is only using T/T method against their targets.
Posted By: farokh

Re: Bug reports - 03/10/13 11:52 AM

strange bug !
how its possible ? i launched one missile by PS "lead" method on jammer target ! but it hit and kill the target

Click to reveal..
Asuluk training ground.

Practice target:
RM-217 Zvezda [program-1] simulating Tornado
RM-217 Zvezda [program-1] simulating Tornado

S-125M1 Neva


00:00, Practice target RM-217 Zvezda [program-1] simulating Tornado launched

+++++++++++++++++
00:00:13, SNR ON AIR


00:00:15, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:00:29, SNR ON AIR


00:01:09, V601P 5V27U Missile launched on Channel-1
Target distance: 13km
Target azimuth: 118°
Target elevation: 0°
Target altitude: 167m
Missile guidance method: PS (Lead)


00:01:14, V601P 5V27U Missile launched on Channel-2
Target distance: 13km
Target azimuth: 121°
Target elevation: 0°
Target altitude: 200m
Missile guidance method: TT (Three Point)


00:01:29, Missile exploded on Channel-1
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 38m)


00:01:33, Missile exploded on Channel-2
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 4m)

02:00, Practice target RM-217 Zvezda [program-1] simulating Tornado launched

00:03:14, V601P 5V27U Missile launched on Channel-2
Target distance: 13km
Target azimuth: 90°
Target elevation: 0°
Target altitude: 211m
Missile guidance method: PS (Lead)


00:03:20, V601P 5V27U Missile launched on Channel-1
Target distance: 13km
Target azimuth: 90°
Target elevation: 1°
Target altitude: 270m
Missile guidance method: TT (Three Point)


00:03:35, Missile exploded on Channel-1
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 1m)

Total, SNR On Air Time: 3min 20sec
seehearspeak




twice little bug at sa-3
its about double fire switch !

as you see i mark rightest fire button switch by red mark ! i pushed it but just one missile fired !
PS: i turn up double fire switch to UP ! but its not work on rightest switch !



Posted By: Hpasp

Re: Bug reports - 03/18/13 06:15 PM

Originally Posted By: farokh
strange bug !
how its possible ? i launched one missile by PS "lead" method on jammer target ! but it hit and kill the target

Click to reveal..
Asuluk training ground.

Practice target:
RM-217 Zvezda [program-1] simulating Tornado
RM-217 Zvezda [program-1] simulating Tornado

S-125M1 Neva


00:00, Practice target RM-217 Zvezda [program-1] simulating Tornado launched

+++++++++++++++++
00:00:13, SNR ON AIR


00:00:15, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:00:29, SNR ON AIR


00:01:09, V601P 5V27U Missile launched on Channel-1
Target distance: 13km
Target azimuth: 118°
Target elevation: 0°
Target altitude: 167m
Missile guidance method: PS (Lead)


00:01:14, V601P 5V27U Missile launched on Channel-2
Target distance: 13km
Target azimuth: 121°
Target elevation: 0°
Target altitude: 200m
Missile guidance method: TT (Three Point)


00:01:29, Missile exploded on Channel-1
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 38m)


00:01:33, Missile exploded on Channel-2
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 4m)

02:00, Practice target RM-217 Zvezda [program-1] simulating Tornado launched

00:03:14, V601P 5V27U Missile launched on Channel-2
Target distance: 13km
Target azimuth: 90°
Target elevation: 0°
Target altitude: 211m
Missile guidance method: PS (Lead)


00:03:20, V601P 5V27U Missile launched on Channel-1
Target distance: 13km
Target azimuth: 90°
Target elevation: 1°
Target altitude: 270m
Missile guidance method: TT (Three Point)


00:03:35, Missile exploded on Channel-1
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 1m)

Total, SNR On Air Time: 3min 20sec
seehearspeak
twice little bug at sa-3
its about double fire switch !

as you see i mark rightest fire button switch by red mark ! i pushed it but just one missile fired !
PS: i turn up double fire switch to UP ! but its not work on rightest switch !
Click to reveal..





As in reality.
(check manual page 34/4)
Posted By: Mdore

Re: Bug reports - 03/24/13 08:03 AM

I've tried a few times with the SA-2E to destroy a target without ever locking onto it. And I'm pretty sure it's impossible.

I add a target reflector in practice mode, then line the crosshairs up precisely over the target, then switch to 5km mode and make sure I'm absolutely 100% on target.

If the missile is in proximity fuse mode, the missile just flies past, never detonates.

If the missile is in command detonated mode, the missile detonates when it reaches the crosshairs, but this never damages the target.

Is this a bug, or just the way you chose to write it? Or maybe I'm not doing something right?
Posted By: piston79

Re: Bug reports - 03/24/13 09:27 PM

It's not a bug, but it's some kind of observation... I believe that WEASELS in "Prairie Fire" does pretty awkward maneuvers, which (I am sure) are not possible for a real plane... Could - in the name of realism - be done something about?

Click to reveal..
trk><name>F/A-18A Hornet No.1, VMFA-314 Black Knights</name><trkseg>
<trkpt lat="32.578262" lon="20.291280">
<ele>462</ele>
<time>2012-01-01T00:00:01Z</time>
</trkpt>
<trkpt lat="32.578001" lon="20.291280">
<ele>642</ele>
<time>2012-01-01T00:00:02Z</time>
</trkpt>
<trkpt lat="32.577556" lon="20.291280">
<ele>822</ele>
<time>2012-01-01T00:00:03Z</time>
</trkpt>
<trkpt lat="32.576934" lon="20.291280">
<ele>1002</ele>
<time>2012-01-01T00:00:04Z</time>
</trkpt>
<trkpt lat="32.576129" lon="20.291280">
<ele>1174</ele>
<time>2012-01-01T00:00:05Z</time>
</trkpt>
<trkpt lat="32.575142" lon="20.291280">
<ele>1256</ele>
<time>2012-01-01T00:00:06Z</time>
</trkpt>
<trkpt lat="32.573976" lon="20.291280">
<ele>1284</ele>
<time>2012-01-01T00:00:07Z</time>
</trkpt>
<trkpt lat="32.572629" lon="20.291280">
<ele>1294</ele>
<time>2012-01-01T00:00:08Z</time>
</trkpt>
<trkpt lat="32.571102" lon="20.291280">
<ele>1298</ele>
<time>2012-01-01T00:00:09Z</time>
</trkpt>
<trkpt lat="32.569403" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:10Z</time>
</trkpt>
<trkpt lat="32.567667" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:11Z</time>
</trkpt>
<trkpt lat="32.565931" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:12Z</time>
</trkpt>
<trkpt lat="32.564196" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:13Z</time>
</trkpt>
<trkpt lat="32.562460" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:14Z</time>
</trkpt>
<trkpt lat="32.560724" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:15Z</time>
</trkpt>
<trkpt lat="32.558987" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:16Z</time>
</trkpt>
<trkpt lat="32.557251" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:17Z</time>
</trkpt>
<trkpt lat="32.555515" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:18Z</time>
</trkpt>
<trkpt lat="32.553780" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:19Z</time>
</trkpt>
<trkpt lat="32.552044" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:20Z</time>
</trkpt>
<trkpt lat="32.550308" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:21Z</time>
</trkpt>
<trkpt lat="32.548572" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:22Z</time>
</trkpt>
<trkpt lat="32.546835" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:23Z</time>
</trkpt>
<trkpt lat="32.545099" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:24Z</time>
</trkpt>
<trkpt lat="32.543363" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:25Z</time>
</trkpt>
<trkpt lat="32.541628" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:26Z</time>
</trkpt>
<trkpt lat="32.539892" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:27Z</time>
</trkpt>
<trkpt lat="32.538156" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:28Z</time>
</trkpt>
<trkpt lat="32.536419" lon="20.291280">
<ele>1299</ele>
<time>2012-01-01T00:00:29Z</time>
</trkpt>
<trkpt lat="32.534683" lon="20.291290">
<ele>1299</ele>
<time>2012-01-01T00:00:30Z</time>
</trkpt>
<trkpt lat="32.532947" lon="20.291315">
<ele>1299</ele>
<time>2012-01-01T00:00:31Z</time>
</trkpt>
<trkpt lat="32.531211" lon="20.291357">
<ele>1299</ele>
<time>2012-01-01T00:00:32Z</time>
</trkpt>
<trkpt lat="32.529476" lon="20.291422">
<ele>1299</ele>
<time>2012-01-01T00:00:33Z</time>
</trkpt>
<trkpt lat="32.527740" lon="20.291502">
<ele>1299</ele>
<time>2012-01-01T00:00:34Z</time>
</trkpt>
<trkpt lat="32.526004" lon="20.291602">
<ele>1299</ele>
<time>2012-01-01T00:00:35Z</time>
</trkpt>
<trkpt lat="32.524267" lon="20.291723">
<ele>1299</ele>
<time>2012-01-01T00:00:36Z</time>
</trkpt>
<trkpt lat="32.522531" lon="20.291865">
<ele>1299</ele>
<time>2012-01-01T00:00:37Z</time>
</trkpt>
<trkpt lat="32.520795" lon="20.292030">
<ele>1299</ele>
<time>2012-01-01T00:00:38Z</time>
</trkpt>
<trkpt lat="32.519060" lon="20.292224">
<ele>1299</ele>
<time>2012-01-01T00:00:39Z</time>
</trkpt>
<trkpt lat="32.517324" lon="20.292446">
<ele>1299</ele>
<time>2012-01-01T00:00:40Z</time>
</trkpt>
<trkpt lat="32.515588" lon="20.292699">
<ele>1299</ele>
<time>2012-01-01T00:00:41Z</time>
</trkpt>
<trkpt lat="32.513834" lon="20.292885">
<ele>1299</ele>
<time>2012-01-01T00:00:42Z</time>
</trkpt>
<trkpt lat="32.511916" lon="20.292180">
<ele>1299</ele>
<time>2012-01-01T00:00:43Z</time>
</trkpt>
<trkpt lat="32.509999" lon="20.291475">
<ele>1299</ele>
<time>2012-01-01T00:00:44Z</time>
</trkpt>
<trkpt lat="32.508082" lon="20.290769">
<ele>1299</ele>
<time>2012-01-01T00:00:45Z</time>
</trkpt>
<trkpt lat="32.506166" lon="20.290064">
<ele>1299</ele>
<time>2012-01-01T00:00:46Z</time>
</trkpt>
<trkpt lat="32.504249" lon="20.289359">
<ele>1299</ele>
<time>2012-01-01T00:00:47Z</time>
</trkpt>
<trkpt lat="32.502332" lon="20.288654">
<ele>1299</ele>
<time>2012-01-01T00:00:48Z</time>
</trkpt>
<trkpt lat="32.500413" lon="20.287949">
<ele>1299</ele>
<time>2012-01-01T00:00:49Z</time>
</trkpt>
<trkpt lat="32.498497" lon="20.287244">
<ele>1299</ele>
<time>2012-01-01T00:00:50Z</time>
</trkpt>
<trkpt lat="32.496580" lon="20.286539">
<ele>1299</ele>
<time>2012-01-01T00:00:51Z</time>
</trkpt>
<trkpt lat="32.494663" lon="20.285834">
<ele>1299</ele>
<time>2012-01-01T00:00:52Z</time>
</trkpt>
<trkpt lat="32.492745" lon="20.285129">
<ele>1299</ele>
<time>2012-01-01T00:00:53Z</time>
</trkpt>
<trkpt lat="32.490828" lon="20.284424">
<ele>1299</ele>
<time>2012-01-01T00:00:54Z</time>
</trkpt>
<trkpt lat="32.488911" lon="20.283719">
<ele>1299</ele>
<time>2012-01-01T00:00:55Z</time>
</trkpt>
<trkpt lat="32.486995" lon="20.283014">
<ele>1299</ele>
<time>2012-01-01T00:00:56Z</time>
</trkpt>
<trkpt lat="32.485078" lon="20.282309">
<ele>1299</ele>
<time>2012-01-01T00:00:57Z</time>
</trkpt>
<trkpt lat="32.483161" lon="20.281604">
<ele>1299</ele>
<time>2012-01-01T00:00:58Z</time>
</trkpt>
<trkpt lat="32.481243" lon="20.280899">
<ele>1299</ele>
<time>2012-01-01T00:00:59Z</time>
</trkpt>
<trkpt lat="32.479326" lon="20.280194">
<ele>1299</ele>
<time>2012-01-01T00:01:00Z</time>
</trkpt>
<trkpt lat="32.477409" lon="20.279489">
<ele>1299</ele>
<time>2012-01-01T00:01:01Z</time>
</trkpt>
<trkpt lat="32.475492" lon="20.278784">
<ele>1299</ele>
<time>2012-01-01T00:01:02Z</time>
</trkpt>
<trkpt lat="32.473574" lon="20.278079">
<ele>1299</ele>
<time>2012-01-01T00:01:03Z</time>
</trkpt>
<trkpt lat="32.471657" lon="20.277374">
<ele>1299</ele>
<time>2012-01-01T00:01:04Z</time>
</trkpt>
<trkpt lat="32.469740" lon="20.276669">
<ele>1299</ele>
<time>2012-01-01T00:01:05Z</time>
</trkpt>
<trkpt lat="32.467824" lon="20.275964">
<ele>1299</ele>
<time>2012-01-01T00:01:06Z</time>
</trkpt>
<trkpt lat="32.465907" lon="20.275259">
<ele>1299</ele>
<time>2012-01-01T00:01:07Z</time>
</trkpt>
<trkpt lat="32.463990" lon="20.274554">
<ele>1299</ele>
<time>2012-01-01T00:01:08Z</time>
</trkpt>
<trkpt lat="32.462072" lon="20.273849">
<ele>1299</ele>
<time>2012-01-01T00:01:09Z</time>
</trkpt>
<trkpt lat="32.460205" lon="20.273203">
<ele>1299</ele>
<time>2012-01-01T00:01:10Z</time>
</trkpt>
<trkpt lat="32.458514" lon="20.272763">
<ele>1299</ele>
<time>2012-01-01T00:01:11Z</time>
</trkpt>
<trkpt lat="32.456597" lon="20.272058">
<ele>1299</ele>
<time>2012-01-01T00:01:12Z</time>
</trkpt>
<trkpt lat="32.454681" lon="20.271352">
<ele>1299</ele>
<time>2012-01-01T00:01:13Z</time>
</trkpt>
<trkpt lat="32.452803" lon="20.270689">
<ele>1299</ele>
<time>2012-01-01T00:01:14Z</time>
</trkpt>
<trkpt lat="32.451093" lon="20.270226">
<ele>1299</ele>
<time>2012-01-01T00:01:15Z</time>
</trkpt>
<trkpt lat="32.449565" lon="20.269977">
<ele>1299</ele>
<time>2012-01-01T00:01:16Z</time>
</trkpt>
<trkpt lat="32.447912" lon="20.269576">
<ele>1299</ele>
<time>2012-01-01T00:01:17Z</time>
</trkpt>
<trkpt lat="32.445996" lon="20.268865">
<ele>1299</ele>
<time>2012-01-01T00:01:18Z</time>
</trkpt>
<trkpt lat="32.444079" lon="20.268156">
<ele>1299</ele>
<time>2012-01-01T00:01:19Z</time>
</trkpt>
<trkpt lat="32.442165" lon="20.267445">
<ele>1299</ele>
<time>2012-01-01T00:01:20Z</time>
</trkpt>
<trkpt lat="32.440249" lon="20.266736">
<ele>1299</ele>
<time>2012-01-01T00:01:21Z</time>
</trkpt>
<trkpt lat="32.438333" lon="20.266024">
<ele>1299</ele>
<time>2012-01-01T00:01:22Z</time>
</trkpt>
<trkpt lat="32.436418" lon="20.265315">
<ele>1299</ele>
<time>2012-01-01T00:01:23Z</time>
</trkpt>
<trkpt lat="32.434502" lon="20.264604">
<ele>1299</ele>
<time>2012-01-01T00:01:24Z</time>
</trkpt>
<trkpt lat="32.432586" lon="20.263895">
<ele>1299</ele>
<time>2012-01-01T00:01:25Z</time>
</trkpt>
<trkpt lat="32.430669" lon="20.263185">
<ele>1299</ele>
<time>2012-01-01T00:01:26Z</time>
</trkpt>
<trkpt lat="32.428755" lon="20.262474">
<ele>1299</ele>
<time>2012-01-01T00:01:27Z</time>
</trkpt>
<trkpt lat="32.426839" lon="20.261765">
<ele>1299</ele>
<time>2012-01-01T00:01:28Z</time>
</trkpt>
<trkpt lat="32.424922" lon="20.261054">
<ele>1299</ele>
<time>2012-01-01T00:01:29Z</time>
</trkpt>
<trkpt lat="32.423008" lon="20.260343">
<ele>1299</ele>
<time>2012-01-01T00:01:30Z</time>
</trkpt>
<trkpt lat="32.421092" lon="20.259633">
<ele>1299</ele>
<time>2012-01-01T00:01:31Z</time>
</trkpt>
<trkpt lat="32.419176" lon="20.258924">
<ele>1299</ele>
<time>2012-01-01T00:01:32Z</time>
</trkpt>
<trkpt lat="32.417259" lon="20.258213">
<ele>1299</ele>
<time>2012-01-01T00:01:33Z</time>
</trkpt>
<trkpt lat="32.415345" lon="20.257504">
<ele>1299</ele>
<time>2012-01-01T00:01:34Z</time>
</trkpt>
<trkpt lat="32.413429" lon="20.256793">
<ele>1299</ele>
<time>2012-01-01T00:01:35Z</time>
</trkpt>
<trkpt lat="32.411512" lon="20.256083">
<ele>1299</ele>
<time>2012-01-01T00:01:36Z</time>
</trkpt>
<trkpt lat="32.409598" lon="20.255372">
<ele>1299</ele>
<time>2012-01-01T00:01:37Z</time>
</trkpt>
<trkpt lat="32.407682" lon="20.254663">
<ele>1299</ele>
<time>2012-01-01T00:01:38Z</time>
</trkpt>
<trkpt lat="32.405765" lon="20.253952">
<ele>1299</ele>
<time>2012-01-01T00:01:39Z</time>
</trkpt>
<trkpt lat="32.403860" lon="20.253256">
<ele>1299</ele>
<time>2012-01-01T00:01:40Z</time>
</trkpt>
<trkpt lat="32.402098" lon="20.252725">
<ele>1299</ele>
<time>2012-01-01T00:01:41Z</time>
</trkpt>
<trkpt lat="32.400517" lon="20.252407">
<ele>1299</ele>
<time>2012-01-01T00:01:42Z</time>
</trkpt>
<trkpt lat="32.399118" lon="20.252302">
<ele>1299</ele>
<time>2012-01-01T00:01:43Z</time>
</trkpt>
<trkpt lat="32.397897" lon="20.252407">
<ele>1299</ele>
<time>2012-01-01T00:01:44Z</time>
</trkpt>
<trkpt lat="32.396858" lon="20.252725">
<ele>1299</ele>
<time>2012-01-01T00:01:45Z</time>
</trkpt>
<trkpt lat="32.396002" lon="20.253195">
<ele>1299</ele>
<time>2012-01-01T00:01:46Z</time>
</trkpt>
<trkpt lat="32.395324" lon="20.253672">
<ele>1299</ele>
<time>2012-01-01T00:01:47Z</time>
</trkpt>
<trkpt lat="32.394827" lon="20.254149">
<ele>1299</ele>
<time>2012-01-01T00:01:48Z</time>
</trkpt>
<trkpt lat="32.394513" lon="20.254625">
<ele>1299</ele>
<time>2012-01-01T00:01:49Z</time>
</trkpt>
<trkpt lat="32.394379" lon="20.255102">
<ele>1299</ele>
<time>2012-01-01T00:01:50Z</time>
</trkpt>
<trkpt lat="32.394424" lon="20.255579">
<ele>1299</ele>
<time>2012-01-01T00:01:51Z</time>
</trkpt>
<trkpt lat="32.394652" lon="20.256056">
<ele>1299</ele>
<time>2012-01-01T00:01:52Z</time>
</trkpt>
<trkpt lat="32.395060" lon="20.256533">
<ele>1299</ele>
<time>2012-01-01T00:01:53Z</time>
</trkpt>
<trkpt lat="32.395648" lon="20.257010">
<ele>1299</ele>
<time>2012-01-01T00:01:54Z</time>
</trkpt>
<trkpt lat="32.396417" lon="20.257487">
<ele>1299</ele>
<time>2012-01-01T00:01:55Z</time>
</trkpt>
<trkpt lat="32.397368" lon="20.257964">
<ele>1299</ele>
<time>2012-01-01T00:01:56Z</time>
</trkpt>
<trkpt lat="32.398499" lon="20.258441">
<ele>1299</ele>
<time>2012-01-01T00:01:57Z</time>
</trkpt>
<trkpt lat="32.399811" lon="20.258917">
<ele>1299</ele>
<time>2012-01-01T00:01:58Z</time>
</trkpt>
<trkpt lat="32.401305" lon="20.259394">
<ele>1299</ele>
<time>2012-01-01T00:01:59Z</time>
</trkpt>
<trkpt lat="32.402940" lon="20.259871">
<ele>1299</ele>
<time>2012-01-01T00:02:00Z</time>
</trkpt>
<trkpt lat="32.404587" lon="20.260348">
<ele>1299</ele>
<time>2012-01-01T00:02:01Z</time>
</trkpt>
<trkpt lat="32.406233" lon="20.260825">
<ele>1299</ele>
<time>2012-01-01T00:02:02Z</time>
</trkpt>
<trkpt lat="32.407881" lon="20.261300">
<ele>1299</ele>
<time>2012-01-01T00:02:03Z</time>
</trkpt>
<trkpt lat="32.409528" lon="20.261777">
<ele>1299</ele>
<time>2012-01-01T00:02:04Z</time>
</trkpt>
<trkpt lat="32.411174" lon="20.262254">
<ele>1299</ele>
<time>2012-01-01T00:02:05Z</time>
</trkpt>
<trkpt lat="32.412821" lon="20.262731">
<ele>1299</ele>
<time>2012-01-01T00:02:06Z</time>
</trkpt>
<trkpt lat="32.414467" lon="20.263208">
<ele>1299</ele>
<time>2012-01-01T00:02:07Z</time>
</trkpt>
<trkpt lat="32.416114" lon="20.263684">
<ele>1299</ele>
<time>2012-01-01T00:02:08Z</time>
</trkpt>
<trkpt lat="32.417760" lon="20.264161">
<ele>1299</ele>
<time>2012-01-01T00:02:09Z</time>
</trkpt>
<trkpt lat="32.419407" lon="20.264638">
<ele>1299</ele>
<time>2012-01-01T00:02:10Z</time>
</trkpt>
<trkpt lat="32.421053" lon="20.265115">
<ele>1299</ele>
<time>2012-01-01T00:02:11Z</time>
</trkpt>
<trkpt lat="32.422701" lon="20.265592">
<ele>1299</ele>
<time>2012-01-01T00:02:12Z</time>
</trkpt>
<trkpt lat="32.422925" lon="20.265581">
<ele>1299</ele>
<time>2012-01-01T00:02:13Z</time>
</trkpt>
<trkpt lat="32.421019" lon="20.264841">
<ele>1299</ele>
<time>2012-01-01T00:02:14Z</time>
</trkpt>
<trkpt lat="32.419111" lon="20.264099">
<ele>1299</ele>
<time>2012-01-01T00:02:15Z</time>
</trkpt>
<trkpt lat="32.417205" lon="20.263359">
<ele>1299</ele>
<time>2012-01-01T00:02:16Z</time>
</trkpt>
<trkpt lat="32.415297" lon="20.262617">
<ele>1299</ele>
<time>2012-01-01T00:02:17Z</time>
</trkpt>
<trkpt lat="32.413389" lon="20.261876">
<ele>1299</ele>
<time>2012-01-01T00:02:18Z</time>
</trkpt>
<trkpt lat="32.411482" lon="20.261134">
<ele>1299</ele>
<time>2012-01-01T00:02:19Z</time>
</trkpt>
<trkpt lat="32.409576" lon="20.260394">
<ele>1299</ele>
<time>2012-01-01T00:02:20Z</time>
</trkpt>
<trkpt lat="32.407668" lon="20.259653">
<ele>1299</ele>
<time>2012-01-01T00:02:21Z</time>
</trkpt>
<trkpt lat="32.405762" lon="20.258911">
<ele>1299</ele>
<time>2012-01-01T00:02:22Z</time>
</trkpt>
<trkpt lat="32.403855" lon="20.258171">
<ele>1299</ele>
<time>2012-01-01T00:02:23Z</time>
</trkpt>
<trkpt lat="32.401947" lon="20.257428">
<ele>1299</ele>
<time>2012-01-01T00:02:24Z</time>
</trkpt>
<trkpt lat="32.400039" lon="20.256688">
<ele>1299</ele>
<time>2012-01-01T00:02:25Z</time>
</trkpt>
<trkpt lat="32.398133" lon="20.255946">
<ele>1299</ele>
<time>2012-01-01T00:02:26Z</time>
</trkpt>
<trkpt lat="32.396225" lon="20.255206">
<ele>1299</ele>
<time>2012-01-01T00:02:27Z</time>
</trkpt>
<trkpt lat="32.394319" lon="20.254464">
<ele>1299</ele>
<time>2012-01-01T00:02:28Z</time>
</trkpt>
<trkpt lat="32.392412" lon="20.253723">
<ele>1299</ele>
<time>2012-01-01T00:02:29Z</time>
</trkpt>
<trkpt lat="32.390504" lon="20.252983">
<ele>1299</ele>
<time>2012-01-01T00:02:30Z</time>
</trkpt>
<trkpt lat="32.388598" lon="20.252241">
<ele>1299</ele>
<time>2012-01-01T00:02:31Z</time>
</trkpt>
<trkpt lat="32.386690" lon="20.251500">
<ele>1299</ele>
<time>2012-01-01T00:02:32Z</time>
</trkpt>
<trkpt lat="32.384782" lon="20.250758">
<ele>1299</ele>
<time>2012-01-01T00:02:33Z</time>
</trkpt>
<trkpt lat="32.382876" lon="20.250018">
<ele>1299</ele>
<time>2012-01-01T00:02:34Z</time>
</trkpt>
<trkpt lat="32.380969" lon="20.249276">
<ele>1299</ele>
<time>2012-01-01T00:02:35Z</time>
</trkpt>
<trkpt lat="32.379061" lon="20.248536">
<ele>1299</ele>
<time>2012-01-01T00:02:36Z</time>
</trkpt>
<trkpt lat="32.377155" lon="20.247794">
<ele>1299</ele>
<time>2012-01-01T00:02:37Z</time>
</trkpt>
<trkpt lat="32.375247" lon="20.247053">
<ele>1299</ele>
<time>2012-01-01T00:02:38Z</time>
</trkpt>
<trkpt lat="32.373339" lon="20.246311">
<ele>1299</ele>
<time>2012-01-01T00:02:39Z</time>
</trkpt>
<trkpt lat="32.371433" lon="20.245571">
<ele>1299</ele>
<time>2012-01-01T00:02:40Z</time>
</trkpt>
<trkpt lat="32.369526" lon="20.244830">
<ele>1299</ele>
<time>2012-01-01T00:02:41Z</time>
</trkpt>
<trkpt lat="32.367618" lon="20.244088">
<ele>1299</ele>
<time>2012-01-01T00:02:42Z</time>
</trkpt>
<trkpt lat="32.365712" lon="20.243348">
<ele>1299</ele>
<time>2012-01-01T00:02:43Z</time>
</trkpt>
<trkpt lat="32.363804" lon="20.242605">
<ele>1299</ele>
<time>2012-01-01T00:02:44Z</time>
</trkpt>
<trkpt lat="32.361935" lon="20.241910">
<ele>1299</ele>
<time>2012-01-01T00:02:45Z</time>
</trkpt>
<trkpt lat="32.360236" lon="20.241412">
<ele>1299</ele>
<time>2012-01-01T00:02:46Z</time>
</trkpt>
<trkpt lat="32.358718" lon="20.241126">
<ele>1299</ele>
<time>2012-01-01T00:02:47Z</time>
</trkpt>
<trkpt lat="32.357379" lon="20.241053">
<ele>1299</ele>
<time>2012-01-01T00:02:48Z</time>
</trkpt>
<trkpt lat="32.356223" lon="20.241192">
<ele>1299</ele>
<time>2012-01-01T00:02:49Z</time>
</trkpt>
<trkpt lat="32.355248" lon="20.241535">
<ele>1299</ele>
<time>2012-01-01T00:02:50Z</time>
</trkpt>
<trkpt lat="32.354452" lon="20.241938">
<ele>1299</ele>
<time>2012-01-01T00:02:51Z</time>
</trkpt>
<trkpt lat="32.353839" lon="20.242343">
<ele>1299</ele>
<time>2012-01-01T00:02:52Z</time>
</trkpt>
<trkpt lat="32.353405" lon="20.242746">
<ele>1299</ele>
<time>2012-01-01T00:02:53Z</time>
</trkpt>
<trkpt lat="32.353152" lon="20.243149">
<ele>1299</ele>
<time>2012-01-01T00:02:54Z</time>
</trkpt>
<trkpt lat="32.353081" lon="20.243552">
<ele>1332</ele>
<time>2012-01-01T00:02:55Z</time>
</trkpt>
<trkpt lat="32.353189" lon="20.243956">
<ele>1512</ele>
<time>2012-01-01T00:02:56Z</time>
</trkpt>
<trkpt lat="32.353479" lon="20.244360">
<ele>1692</ele>
<time>2012-01-01T00:02:57Z</time>
</trkpt>
<trkpt lat="32.353951" lon="20.244762">
<ele>1872</ele>
<time>2012-01-01T00:02:58Z</time>
</trkpt>
<trkpt lat="32.354601" lon="20.245166">
<ele>2052</ele>
<time>2012-01-01T00:02:59Z</time>
</trkpt>
<trkpt lat="32.355434" lon="20.245570">
<ele>2232</ele>
<time>2012-01-01T00:03:00Z</time>
</trkpt>
<trkpt lat="32.356448" lon="20.245972">
<ele>2304</ele>
<time>2012-01-01T00:03:01Z</time>
</trkpt>
<trkpt lat="32.357641" lon="20.246376">
<ele>2124</ele>
<time>2012-01-01T00:03:02Z</time>
</trkpt>
<trkpt lat="32.358018" lon="20.246423">
<ele>1998</ele>
<time>2012-01-01T00:03:03Z</time>
</trkpt>
<trkpt lat="32.356129" lon="20.245643">
<ele>1962</ele>
<time>2012-01-01T00:03:04Z</time>
</trkpt>
<trkpt lat="32.354371" lon="20.245015">
<ele>1782</ele>
<time>2012-01-01T00:03:05Z</time>
</trkpt>
<trkpt lat="32.352792" lon="20.244600">
<ele>1602</ele>
<time>2012-01-01T00:03:06Z</time>
</trkpt>
<trkpt lat="32.351396" lon="20.244396">
<ele>1428</ele>
<time>2012-01-01T00:03:07Z</time>
</trkpt>
<trkpt lat="32.350180" lon="20.244406">
<ele>1344</ele>
<time>2012-01-01T00:03:08Z</time>
</trkpt>
<trkpt lat="32.349145" lon="20.244627">
<ele>1315</ele>
<time>2012-01-01T00:03:09Z</time>
</trkpt>
<trkpt lat="32.348291" lon="20.244963">
<ele>1305</ele>
<time>2012-01-01T00:03:10Z</time>
</trkpt>
<trkpt lat="32.347617" lon="20.245301">
<ele>1301</ele>
<time>2012-01-01T00:03:11Z</time>
</trkpt>
<trkpt lat="32.347126" lon="20.245637">
<ele>1300</ele>
<time>2012-01-01T00:03:12Z</time>
</trkpt>
<trkpt lat="32.346814" lon="20.245975">
<ele>1300</ele>
<time>2012-01-01T00:03:13Z</time>
</trkpt>
<trkpt lat="32.346682" lon="20.246311">
<ele>1380</ele>
<time>2012-01-01T00:03:14Z</time>
</trkpt>
<trkpt lat="32.346733" lon="20.246649">
<ele>1534</ele>
<time>2012-01-01T00:03:15Z</time>
</trkpt>
<trkpt lat="32.345053" lon="20.245941">
<ele>1552</ele>
<time>2012-01-01T00:03:16Z</time>
</trkpt>
<trkpt lat="32.343172" lon="20.245118">
<ele>1552</ele>
<time>2012-01-01T00:03:17Z</time>
</trkpt>
<trkpt lat="32.341289" lon="20.244292">
<ele>1552</ele>
<time>2012-01-01T00:03:18Z</time>
</trkpt>
<trkpt lat="32.339407" lon="20.243469">
<ele>1552</ele>
<time>2012-01-01T00:03:19Z</time>
</trkpt>
<trkpt lat="32.337524" lon="20.242644">
<ele>1552</ele>
<time>2012-01-01T00:03:20Z</time>
</trkpt>
<trkpt lat="32.335642" lon="20.241821">
<ele>1552</ele>
<time>2012-01-01T00:03:21Z</time>
</trkpt>
<trkpt lat="32.333761" lon="20.240997">
<ele>1552</ele>
<time>2012-01-01T00:03:22Z</time>
</trkpt>
<trkpt lat="32.331878" lon="20.240172">
<ele>1552</ele>
<time>2012-01-01T00:03:23Z</time>
</trkpt>
<trkpt lat="32.329996" lon="20.239349">
<ele>1552</ele>
<time>2012-01-01T00:03:24Z</time>
</trkpt>
<trkpt lat="32.328113" lon="20.238524">
<ele>1552</ele>
<time>2012-01-01T00:03:25Z</time>
</trkpt>
<trkpt lat="32.326270" lon="20.237746">
<ele>1660</ele>
<time>2012-01-01T00:03:26Z</time>
</trkpt>
<trkpt lat="32.324595" lon="20.237165">
<ele>1840</ele>
<time>2012-01-01T00:03:27Z</time>
</trkpt>
<trkpt lat="32.323101" lon="20.236796">
<ele>2020</ele>
<time>2012-01-01T00:03:28Z</time>
</trkpt>
<trkpt lat="32.321789" lon="20.236640">
<ele>2200</ele>
<time>2012-01-01T00:03:29Z</time>
</trkpt>
<trkpt lat="32.320656" lon="20.236695">
<ele>2380</ele>
<time>2012-01-01T00:03:30Z</time>
</trkpt>
<trkpt lat="32.319707" lon="20.236957">
<ele>2416</ele>
<time>2012-01-01T00:03:31Z</time>
</trkpt>
<trkpt lat="32.318936" lon="20.237277">
<ele>2236</ele>
<time>2012-01-01T00:03:32Z</time>
</trkpt>
<trkpt lat="32.318347" lon="20.237597">
<ele>2056</ele>
<time>2012-01-01T00:03:33Z</time>
</trkpt>
<trkpt lat="32.317939" lon="20.237919">
<ele>2200</ele>
<time>2012-01-01T00:03:34Z</time>
</trkpt>
<trkpt lat="32.317711" lon="20.238239">
<ele>2308</ele>
<time>2012-01-01T00:03:35Z</time>
</trkpt>
<trkpt lat="32.317664" lon="20.238559">
<ele>2488</ele>
<time>2012-01-01T00:03:36Z</time>
</trkpt>
<trkpt lat="32.317798" lon="20.238880">
<ele>2668</ele>
<time>2012-01-01T00:03:37Z</time>
</trkpt>
<trkpt lat="32.318112" lon="20.239201">
<ele>2812</ele>
<time>2012-01-01T00:03:38Z</time>
</trkpt>
<trkpt lat="32.318609" lon="20.239520">
<ele>2992</ele>
<time>2012-01-01T00:03:39Z</time>
</trkpt>
<trkpt lat="32.319285" lon="20.239841">
<ele>2992</ele>
<time>2012-01-01T00:03:40Z</time>
</trkpt>
<trkpt lat="32.320143" lon="20.240162">
<ele>2992</ele>
<time>2012-01-01T00:03:41Z</time>
</trkpt>
<trkpt lat="32.321181" lon="20.240483">
<ele>2992</ele>
<time>2012-01-01T00:03:42Z</time>
</trkpt>
<trkpt lat="32.322400" lon="20.240802">
<ele>2992</ele>
<time>2012-01-01T00:03:43Z</time>
</trkpt>
<trkpt lat="32.323799" lon="20.241123">
<ele>2992</ele>
<time>2012-01-01T00:03:44Z</time>
</trkpt>
<trkpt lat="32.325381" lon="20.241444">
<ele>2992</ele>
<time>2012-01-01T00:03:45Z</time>
</trkpt>
<trkpt lat="32.327061" lon="20.241765">
<ele>2992</ele>
<time>2012-01-01T00:03:46Z</time>
</trkpt>
<trkpt lat="32.328741" lon="20.242084">
<ele>2992</ele>
<time>2012-01-01T00:03:47Z</time>
</trkpt>
<trkpt lat="32.330421" lon="20.242405">
<ele>2992</ele>
<time>2012-01-01T00:03:48Z</time>
</trkpt>
<trkpt lat="32.332101" lon="20.242726">
<ele>2956</ele>
<time>2012-01-01T00:03:49Z</time>
</trkpt>
<trkpt lat="32.333781" lon="20.243047">
<ele>2776</ele>
<time>2012-01-01T00:03:50Z</time>
</trkpt>
<trkpt lat="32.335461" lon="20.243368">
<ele>2632</ele>
<time>2012-01-01T00:03:51Z</time>
</trkpt>
<trkpt lat="32.337142" lon="20.243687">
<ele>2812</ele>
<time>2012-01-01T00:03:52Z</time>
</trkpt>
<trkpt lat="32.338822" lon="20.244008">
<ele>2992</ele>
<time>2012-01-01T00:03:53Z</time>
</trkpt>
<trkpt lat="32.340502" lon="20.244329">
<ele>2992</ele>
<time>2012-01-01T00:03:54Z</time>
</trkpt>
<trkpt lat="32.342182" lon="20.244650">
<ele>2992</ele>
<time>2012-01-01T00:03:55Z</time>
</trkpt>
<trkpt lat="32.343862" lon="20.244969">
<ele>2992</ele>
<time>2012-01-01T00:03:56Z</time>
</trkpt>
<trkpt lat="32.345542" lon="20.245291">
<ele>2992</ele>
<time>2012-01-01T00:03:57Z</time>
</trkpt>
<trkpt lat="32.347222" lon="20.245611">
<ele>2992</ele>
<time>2012-01-01T00:03:58Z</time>
</trkpt>
<trkpt lat="32.348902" lon="20.245931">
<ele>2992</ele>
<time>2012-01-01T00:03:59Z</time>
</trkpt>
<trkpt lat="32.350583" lon="20.246266">
<ele>2992</ele>
<time>2012-01-01T00:04:00Z</time>
</trkpt>
<trkpt lat="32.352263" lon="20.246608">
<ele>2992</ele>
<time>2012-01-01T00:04:01Z</time>
</trkpt>
<trkpt lat="32.353943" lon="20.246949">
<ele>2992</ele>
<time>2012-01-01T00:04:02Z</time>
</trkpt>
<trkpt lat="32.355623" lon="20.247292">
<ele>2992</ele>
<time>2012-01-01T00:04:03Z</time>
</trkpt>
<trkpt lat="32.357303" lon="20.247634">
<ele>2956</ele>
<time>2012-01-01T00:04:04Z</time>
</trkpt>
<trkpt lat="32.358983" lon="20.247975">
<ele>2776</ele>
<time>2012-01-01T00:04:05Z</time>
</trkpt>
<trkpt lat="32.360663" lon="20.248317">
<ele>2596</ele>
<time>2012-01-01T00:04:06Z</time>
</trkpt>
<trkpt lat="32.362344" lon="20.248658">
<ele>2416</ele>
<time>2012-01-01T00:04:07Z</time>
</trkpt>
<trkpt lat="32.364024" lon="20.249020">
<ele>2344</ele>
<time>2012-01-01T00:04:08Z</time>
</trkpt>
<trkpt lat="32.365704" lon="20.249382">
<ele>2524</ele>
<time>2012-01-01T00:04:09Z</time>
</trkpt>
<trkpt lat="32.367384" lon="20.249745">
<ele>2704</ele>
<time>2012-01-01T00:04:10Z</time>
</trkpt>
<trkpt lat="32.369064" lon="20.250108">
<ele>2884</ele>
<time>2012-01-01T00:04:11Z</time>
</trkpt>
<trkpt lat="32.370744" lon="20.250471">
<ele>2992</ele>
<time>2012-01-01T00:04:12Z</time>
</trkpt>
<trkpt lat="32.372424" lon="20.250834">
<ele>2992</ele>
<time>2012-01-01T00:04:13Z</time>
</trkpt>
<trkpt lat="32.374105" lon="20.251197">
<ele>2992</ele>
<time>2012-01-01T00:04:14Z</time>
</trkpt>
<trkpt lat="32.375785" lon="20.251574">
<ele>2992</ele>
<time>2012-01-01T00:04:15Z</time>
</trkpt>
<trkpt lat="32.377465" lon="20.251958">
<ele>2992</ele>
<time>2012-01-01T00:04:16Z</time>
</trkpt>
<trkpt lat="32.379145" lon="20.252342">
<ele>2992</ele>
<time>2012-01-01T00:04:17Z</time>
</trkpt>
<trkpt lat="32.380825" lon="20.252727">
<ele>2992</ele>
<time>2012-01-01T00:04:18Z</time>
</trkpt>
<trkpt lat="32.382505" lon="20.253111">
<ele>2992</ele>
<time>2012-01-01T00:04:19Z</time>
</trkpt>
<trkpt lat="32.384185" lon="20.253495">
<ele>2812</ele>
<time>2012-01-01T00:04:20Z</time>
</trkpt>
<trkpt lat="32.385866" lon="20.253879">
<ele>2632</ele>
<time>2012-01-01T00:04:21Z</time>
</trkpt>
<trkpt lat="32.387546" lon="20.254284">
<ele>2452</ele>
<time>2012-01-01T00:04:22Z</time>
</trkpt>
<trkpt lat="32.389226" lon="20.254690">
<ele>2272</ele>
<time>2012-01-01T00:04:23Z</time>
</trkpt>
<trkpt lat="32.390906" lon="20.255095">
<ele>2092</ele>
<time>2012-01-01T00:04:24Z</time>
</trkpt>
<trkpt lat="32.392586" lon="20.255500">
<ele>1912</ele>
<time>2012-01-01T00:04:25Z</time>
</trkpt>
<trkpt lat="32.394266" lon="20.255905">
<ele>1732</ele>
<time>2012-01-01T00:04:26Z</time>
</trkpt>
<trkpt lat="32.395946" lon="20.256311">
<ele>1552</ele>
<time>2012-01-01T00:04:27Z</time>
</trkpt>
<trkpt lat="32.397627" lon="20.256733">
<ele>1396</ele>
<time>2012-01-01T00:04:28Z</time>
</trkpt>
<trkpt lat="32.399307" lon="20.257159">
<ele>1333</ele>
<time>2012-01-01T00:04:29Z</time>
</trkpt>
<trkpt lat="32.400987" lon="20.257585">
<ele>1311</ele>
<time>2012-01-01T00:04:30Z</time>
</trkpt>
<trkpt lat="32.401950" lon="20.257778">
<ele>1305</ele>
<time>2012-01-01T00:04:31Z</time>
</trkpt>
<trkpt lat="32.400044" lon="20.257034">
<ele>1305</ele>
<time>2012-01-01T00:04:32Z</time>
</trkpt>
<trkpt lat="32.398138" lon="20.256291">
<ele>1305</ele>
<time>2012-01-01T00:04:33Z</time>
</trkpt>
<trkpt lat="32.396231" lon="20.255548">
<ele>1305</ele>
<time>2012-01-01T00:04:34Z</time>
</trkpt>
<trkpt lat="32.394325" lon="20.254805">
<ele>1305</ele>
<time>2012-01-01T00:04:35Z</time>
</trkpt>
<trkpt lat="32.392417" lon="20.254062">
<ele>1305</ele>
<time>2012-01-01T00:04:36Z</time>
</trkpt>
<trkpt lat="32.390510" lon="20.253319">
<ele>1305</ele>
<time>2012-01-01T00:04:37Z</time>
</trkpt>
<trkpt lat="32.388604" lon="20.252575">
<ele>1305</ele>
<time>2012-01-01T00:04:38Z</time>
</trkpt>
<trkpt lat="32.386698" lon="20.251832">
<ele>1305</ele>
<time>2012-01-01T00:04:39Z</time>
</trkpt>
<trkpt lat="32.384791" lon="20.251089">
<ele>1305</ele>
<time>2012-01-01T00:04:40Z</time>
</trkpt>
<trkpt lat="32.382885" lon="20.250344">
<ele>1305</ele>
<time>2012-01-01T00:04:41Z</time>
</trkpt>
<trkpt lat="32.380979" lon="20.249601">
<ele>1305</ele>
<time>2012-01-01T00:04:42Z</time>
</trkpt>
<trkpt lat="32.379072" lon="20.248858">
<ele>1305</ele>
<time>2012-01-01T00:04:43Z</time>
</trkpt>
<trkpt lat="32.377166" lon="20.248114">
<ele>1305</ele>
<time>2012-01-01T00:04:44Z</time>
</trkpt>
<trkpt lat="32.375258" lon="20.247371">
<ele>1305</ele>
<time>2012-01-01T00:04:45Z</time>
</trkpt>
<trkpt lat="32.373353" lon="20.246628">
<ele>1305</ele>
<time>2012-01-01T00:04:46Z</time>
</trkpt>
<trkpt lat="32.371445" lon="20.245885">
<ele>1305</ele>
<time>2012-01-01T00:04:47Z</time>
</trkpt>
<trkpt lat="32.369540" lon="20.245142">
<ele>1305</ele>
<time>2012-01-01T00:04:48Z</time>
</trkpt>
<trkpt lat="32.367632" lon="20.244399">
<ele>1305</ele>
<time>2012-01-01T00:04:49Z</time>
</trkpt>
<trkpt lat="32.365726" lon="20.243655">
<ele>1305</ele>
<time>2012-01-01T00:04:50Z</time>
</trkpt>
<trkpt lat="32.363819" lon="20.242912">
<ele>1305</ele>
<time>2012-01-01T00:04:51Z</time>
</trkpt>
<trkpt lat="32.361913" lon="20.242169">
<ele>1305</ele>
<time>2012-01-01T00:04:52Z</time>
</trkpt>
<trkpt lat="32.360007" lon="20.241424">
<ele>1305</ele>
<time>2012-01-01T00:04:53Z</time>
</trkpt>
<trkpt lat="32.358100" lon="20.240681">
<ele>1305</ele>
<time>2012-01-01T00:04:54Z</time>
</trkpt>
<trkpt lat="32.356194" lon="20.239937">
<ele>1305</ele>
<time>2012-01-01T00:04:55Z</time>
</trkpt>
<trkpt lat="32.354286" lon="20.239194">
<ele>1305</ele>
<time>2012-01-01T00:04:56Z</time>
</trkpt>
<trkpt lat="32.352381" lon="20.238451">
<ele>1305</ele>
<time>2012-01-01T00:04:57Z</time>
</trkpt>
<trkpt lat="32.350473" lon="20.237708">
<ele>1305</ele>
<time>2012-01-01T00:04:58Z</time>
</trkpt>
<trkpt lat="32.348568" lon="20.236965">
<ele>1305</ele>
<time>2012-01-01T00:04:59Z</time>
</trkpt>
<trkpt lat="32.346660" lon="20.236222">
<ele>1305</ele>
<time>2012-01-01T00:05:00Z</time>
</trkpt>
<trkpt lat="32.344754" lon="20.235478">
<ele>1305</ele>
<time>2012-01-01T00:05:01Z</time>
</trkpt>
<trkpt lat="32.342847" lon="20.234735">
<ele>1305</ele>
<time>2012-01-01T00:05:02Z</time>
</trkpt>
<trkpt lat="32.341006" lon="20.234068">
<ele>1302</ele>
<time>2012-01-01T00:05:03Z</time>
</trkpt>
</trkseg></trk>
Posted By: Mdore

Re: Bug reports - 03/29/13 03:59 PM

Okay, another bug.

If I track a target using the I87V for range, and guide the missiles in 1/2 lead mode, the missiles DO NOT lead the target, the missiles don't even fly a straight line, instead they trail the target.

Example, if I am tracking a target to the north of me that is going east to west <---, and I track the targets range normally, the missile flies to the left <--- of the centre line, leading the target. But if I track the target's range with I87V, the missile flies to the right ---> of the centre line!

Very odd.
Posted By: Hpasp

Re: Bug reports - 03/29/13 04:30 PM

Originally Posted By: Mdore
Okay, another bug.

If I track a target using the I87V for range, and guide the missiles in 1/2 lead mode, the missiles DO NOT lead the target, the missiles don't even fly a straight line, instead they trail the target.

Example, if I am tracking a target to the north of me that is going east to west <---, and I track the targets range normally, the missile flies to the left <--- of the centre line, leading the target. But if I track the target's range with I87V, the missile flies to the right ---> of the centre line!

Very odd.


I think, that this bug was already reported, corrected, just not released yet...
... still waiting more to be collected.
Posted By: Hpasp

Re: Bug reports - 03/29/13 04:31 PM

Originally Posted By: Mdore
I've tried a few times with the SA-2E to destroy a target without ever locking onto it. And I'm pretty sure it's impossible.

I add a target reflector in practice mode, then line the crosshairs up precisely over the target, then switch to 5km mode and make sure I'm absolutely 100% on target.

If the missile is in proximity fuse mode, the missile just flies past, never detonates.

If the missile is in command detonated mode, the missile detonates when it reaches the crosshairs, but this never damages the target.

Is this a bug, or just the way you chose to write it? Or maybe I'm not doing something right?


Might be the same bug.
I tried it with the new code, and with Volhov T/T - RabOtVM - auto-track on elevation - 5km display, and manually tracking the Ashuluk Radar Reflector in Azimuth, I was able to kill it. (Range bore-sight was well before the target)

Click to reveal..
Asuluk training ground.

Practice target:
Radar Reflector

S-75M3 Volkhov


00:00, Practice target Radar Reflector launched

+++++++++++++++++
00:00:06, SNR ON AIR


00:00:36, V-755 20DSU Missile launched on Channel-1
Target distance: 20km
Target azimuth: 73°
Target elevation: 18°
Target altitude: 6,4km
SNR mode: Wide Beam - 5km
Missile guidance method: T/T (Three Point)


00:01:06, Missile exploded on Channel-1
Practice target Radar Reflector killed by SAM. (miss distance: 86m)

Total, SNR On Air Time: 1min 11sec


Please try this patch.
http://www.mediafire.com/?2aavi4919229t7d
(it has some easter eggs)
biggrin
Posted By: Mdore

Re: Bug reports - 03/30/13 05:20 AM

I87V + 1/2 lead works. Yay! Thank you!

Also, great easter egg! I'm guessing it's too soon for any buttons to work?

Though you said eggS, so I wonder if I missed something.
Posted By: Mdore

Re: Bug reports - 03/30/13 06:01 AM

Okay, I should probably add a bug report, though you've probably spotted this already.

On 0.926D, the sim starts showing the SA-2E, and has Dregelypalank as the "Live Practice". Locking onto a meteor with an SA-2 was cool. But I couldn't add missiles to shoot it down. I'm still guessing it's a bug, even if it was fun hahaha

If you scroll to the SA-2F or the SA-5, the "Live Practice" fixes itself, and Asuluk and Ustka are available.
Posted By: Hpasp

Re: Bug reports - 03/30/13 07:09 AM

Originally Posted By: Mdore
I87V + 1/2 lead works. Yay! Thank you!

Also, great easter egg! I'm guessing it's too soon for any buttons to work?

Though you said eggS, so I wonder if I missed something.


Just two screens, "Y/Z", "X", and Escape buttons.
thumbsup
Posted By: piston79

Re: Bug reports - 03/30/13 08:13 AM

Originally Posted By: Mdore

On 0.926D, the sim starts showing the SA-2E, and has Dregelypalank as the "Live Practice". Locking onto a meteor with an SA-2 was cool. But I couldn't add missiles to shoot it down. I'm still guessing it's a bug, even if it was fun hahaha


Note the AAR - target is MiG-21 wink
Posted By: piston79

Re: Bug reports - 03/30/13 08:24 AM

Originally Posted By: Hpasp

Might be the same bug.
I tried it with the new code, and with Volhov T/T - RabOtVM - auto-track on elevation - 5km display, and manually tracking the Ashuluk Radar Reflector in Azimuth, I was able to kill it. (Range bore-sight was well before the target)



I believe that after passing the boresight, missile should receive second K3 and destruct itself... Do not know how it goes with Rab. ot VM, but as missile goes near a object (like chaffs in Linebacker) it pops-up)...Also about manual tracking - it should be the same from FCO and manual operators on RS (green indicators)....
Posted By: Hpasp

Re: Bug reports - 03/30/13 05:38 PM

Some corrections...
http://www.mediafire.com/?cq8xfwmdwrl1hh6
Posted By: max2012

Re: Bug reports - 06/08/13 05:48 PM


I found a bug!

Look at the pictures here with a tornado.

Click to reveal..







Posted By: max2012

Re: Bug reports - 06/08/13 09:53 PM


Volkhov errors more ...

Click to reveal..






Posted By: Muggs

Re: Bug reports - 06/09/13 12:06 PM

Using SA-2E it's possible to fire the first missile while in practice mode, it doesn't show up on the AAR.

disregard
Posted By: piston79

Re: Bug reports - 06/09/13 12:45 PM

Originally Posted By: Muggs
Using SA-2E it's possible to fire the first missile while in practice mode, it doesn't show up on the AAR.


It is electronic shot, no real missile inflight...
Posted By: Muggs

Re: Bug reports - 06/09/13 04:41 PM

Originally Posted By: piston79
Originally Posted By: Muggs
Using SA-2E it's possible to fire the first missile while in practice mode, it doesn't show up on the AAR.


It is electronic shot, no real missile inflight...


I understand now, thanks!
Posted By: piston79

Re: Bug reports - 06/17/13 10:42 AM

Originally Posted By: Hpasp
Originally Posted By: max2012

Hi hpasp!

As I understood the new release is scheduled for the end of this year?

Will the intermediate releases of correcting mistakes or not?

Error in Volkhov report low targets


Hi Max, please keep track of the bugs, and after releasing Osa, I will create a bugfix release, hopefully correcting all these issues...


Question: Do we need to keep track on the bugs? I think it is more convinient for the developer to write down newfound bugs reported by us in this topic, starting right after (any) new release, as he is the only one who knew how many of those bugs are solved. I wish when new version is released, that "readme" file could be included, which informs us which bugs are solved...

Personally I didn't know which bug is solved, as I just reported it and thought that developer put it in his "To Do list"...
Max2012 found AGAIN known bug, caused by 3 degrees boresight change because "<5 km" mode activated...

We really need a plan how to deal with it, as there is too much time to the new release, and should keep in mind that there are bugs not solved...


Again, my proposal is that this list of bugs must be kept by the developer....
Posted By: farokh

Re: Bug reports - 07/05/13 07:17 PM

hpasp salute
please check the sa-2E anthena .... when i launch missile by anthena without transmitter
they can open harm on me !
this happened do not done for me when i work with sa-2F !

please repair the sa-2E anthena
Posted By: Mdore

Re: Bug reports - 07/05/13 07:27 PM

I think the HARM can home on the missile command uplink. As soon as you launch a missile, you start transmitting guidance signals to it, even if your radar is off.
Posted By: Alien_MasterMynd

Re: Bug reports - 07/05/13 07:42 PM

Originally Posted By: Mdore
I think the HARM can home on the missile command uplink. As soon as you launch a missile, you start transmitting guidance signals to it, even if your radar is off.

Yes, HARM can lock on RPK signals too yep

--------------
Ha, piston79 was faster thumbsup
Posted By: piston79

Re: Bug reports - 07/05/13 07:50 PM

Originally Posted By: Alien_MasterMynd

--------------
Ha, piston79 was faster thumbsup


BUT WRONG AT THAT CASE!

To DEVELOPER:

Quote:
See, you're bussy with OSA, but if you noticed couple of last post of Faroukh and Milo11, they created havoc in "Prairie Fire" and "Allied force" missions, using "Dvina"... Also Faroukh complaining that it is impossible with "Volkhov"... I am starting to think, that when using "Dvina" in non-historical missions, where "HARM" are available, they somehow became "blind" for RPK signal (i.e. became "Shrike"-s)....
Posted By: Alien_MasterMynd

Re: Bug reports - 07/05/13 08:06 PM

Yes, I was thinking and writing faster than reading, I haven't read farokh's post to the end nope
Posted By: farokh

Re: Bug reports - 07/05/13 08:08 PM

Originally Posted By: Mdore
I think the HARM can home on the missile command uplink. As soon as you launch a missile, you start transmitting guidance signals to it, even if your radar is off.


it could be truth but what about sa-2F anthena ?
when i launch a missile by sa-2 dvina anthena , fighters cant open harm on me !
that is the question !!!!
Posted By: piston79

Re: Bug reports - 07/05/13 08:11 PM

Originally Posted By: farokh

it could be truth but what about sa-2F anthena ?
when i launch a missile by sa-2 dvina anthena , fighters cant open harm on me !
that is the question !!!!


I am starting to think, that when using "Dvina" in non-historical missions, where "HARM" are available, they somehow became "blind" for RPK signal (i.e. became "Shrike"-s)....
Posted By: farokh

Re: Bug reports - 07/05/13 08:28 PM

Originally Posted By: piston79
Originally Posted By: farokh

it could be truth but what about sa-2F anthena ?
when i launch a missile by sa-2 dvina anthena , fighters cant open harm on me !
that is the question !!!!


I am starting to think, that when using "Dvina" in non-historical missions, where "HARM" are available, they somehow became "blind" for RPK signal (i.e. became "Shrike"-s)....


gooood question ! reading
Posted By: Mdore

Re: Bug reports - 07/08/13 10:25 AM

It's possible to see targets on the ZSU-23-4's range display, when the radar is off.
Posted By: farokh

Re: Bug reports - 07/11/13 12:20 PM

im not sure that is was a bug but...mmmm is it possible ?

Click to reveal..

Targets:
Nat'l MOD HQ
FRY MUP HQ
MOD HQ South
Serb MUP HQ
Army HQ Facility A

Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


5/250 rd PVO, Brestovik ( 210m)
SA-75M Dvina


+++++++++++++++++
00:00:38, SNR ON AIR


00:00:43, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:00:47, SNR ON AIR


00:00:49, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:00:54, SNR ON AIR


00:01:03, V-750VMVK 11DMVK Missile launched on Channel-1
Target distance: 35km
Target azimuth: 204°
Target elevation: 17°
Target altitude: 10.4km
SNR mode: 55km
Missile guidance method: UPR (Half Lead)


00:01:08, V-750VMVK 11DMVK Missile launched on Channel-3
Target distance: 35km
Target azimuth: 205°
Target elevation: 18°
Target altitude: 10.8km
SNR mode: 55km
Missile guidance method: T/T (Three Point)


00:01:09, F-16CJ Falcon SEAD Number-3 launched AGM-88 HARM missile No. 1


00:01:35, Missile exploded on Channel-1
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 22m)


00:01:40, Missile exploded on Channel-3
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 17m)

00:01:43, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 58sec


UPR method could engage to target ????
Posted By: piston79

Re: Bug reports - 07/12/13 10:03 AM

Originally Posted By: farokh
im not sure that is was a bug but...mmmm is it possible ?

UPR method could engage to target ????


Could you doit again? If yes - probably a bug....
Posted By: farokh

Re: Bug reports - 07/12/13 10:36 AM

Originally Posted By: piston79

Could you doit again? If yes - probably a bug....


Click to reveal..
22:06pm 30th of April, 1999.
Operation Allied Force, B-2A raid on Belgrade

Targets:
Nat'l MOD HQ
FRY MUP HQ
MOD HQ South
Serb MUP HQ
Army HQ Facility A

Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


5/250 rd PVO, Brestovik ( 210m)
SA-75M Dvina


+++++++++++++++++
00:00:21, SNR ON AIR


00:00:27, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:00:34, SNR ON AIR


00:00:38, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:00:45, SNR ON AIR


00:00:49, V-750VMVK 11DMVK Missile launched on Channel-1
Target distance: 35km
Target azimuth: 201°
Target elevation: 15°
Target altitude: 9.4km
SNR mode: 55km
Missile guidance method: UPR (Half Lead)


00:00:54, V-750VMVK 11DMVK Missile launched on Channel-2
Target distance: 35km
Target azimuth: 202°
Target elevation: 16°
Target altitude: 9.8km
SNR mode: 55km
Missile guidance method: UPR (Half Lead)


00:01:01, F-16CJ Falcon SEAD Number-3 launched AGM-88 HARM missile No. 1


00:01:24, Missile exploded on Channel-1
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 21m)

00:01:28, Missile exploded on Channel-2
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 16m)

00:01:32, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 59sec



and i do it with sa-2E volhov and agin UPR could hunt target

Click to reveal..
22:06pm 30th of April, 1999.
Operation Allied Force, B-2A raid on Belgrade

Targets:
Nat'l MOD HQ
FRY MUP HQ
MOD HQ South
Serb MUP HQ
Army HQ Facility A

Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


5/250 rd PVO, Brestovik ( 210m)
S-75M3 Volkhov


+++++++++++++++++
00:00:09, SNR ON AIR


00:00:54, V-759 5Ya23 Missile launched on Channel-1
Target distance: 35km
Target azimuth: 202°
Target elevation: 16°
Target altitude: 9.7km
SNR mode: Wide Beam - 75km
Missile guidance method: UPR (Half Lead)


00:00:59, V-759 5Ya23 Missile launched on Channel-2
Target distance: 35km
Target azimuth: 203°
Target elevation: 16°
Target altitude: 10.1km
SNR mode: Wide Beam - 75km
Missile guidance method: UPR (Half Lead)


00:01:05, V-759 5Ya23 Missile launched on Channel-3
Target distance: 35km
Target azimuth: 205°
Target elevation: 17°
Target altitude: 10.6km
SNR mode: Wide Beam - 75km
Missile guidance method: UPR (Half Lead)


00:01:05, F-16CJ Falcon SEAD Number-3 launched AGM-88 HARM missile No. 1


00:01:28, Missile exploded on Channel-1
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 14m)

00:01:32, Missile exploded on Channel-2
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 33m)

00:01:37, Missile exploded on Channel-3
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 13m)

Total, SNR On Air Time: 1min 36sec


of course with sa-2E i do this hunt with different method against jamming that you can see in below pic
but im not sure that even this one could work on UPR any way


Posted By: piston79

Re: Bug reports - 07/12/13 10:43 AM

Does it work in another scenarios, like Ashuluk? Please, examine and report....
Posted By: farokh

Re: Bug reports - 07/12/13 10:52 AM

Originally Posted By: piston79
Does it work in another scenarios, like Ashuluk? Please, examine and report....

piston79 please checking my latest post about sa-2E bug ! .... i upload one image that maybe it could be important to find bog or not !

PS: would u help me to find other bug ? please you some try ! im so tiered from bugs goodnight
Posted By: Mdore

Re: Bug reports - 07/12/13 11:10 AM

I don't understand the bug you two are talking about.

I don't see any bug in what you say.
Posted By: piston79

Re: Bug reports - 07/12/13 12:56 PM

Do a video and link it here...
Posted By: Hpasp

Re: Bug reports - 07/12/13 01:04 PM

Originally Posted By: piston79
Do a video and link it here...


Could I ask a favor?
Can you collect and number the identified bugs?
After OSA first release (end of this year~first half of next year) I would like to correct those, but it would make easier if we would have a summarized buglist.
Posted By: farokh

Re: Bug reports - 07/12/13 03:26 PM

Originally Posted By: Hpasp

Could I ask a favor?
Can you collect and number the identified bugs?


yes dear hpasp

i found few bugs till now

number 1 :
problem with sa-2f and sa-2E anthena during launch and reflection during harm launch

number 2 :
problem with command guidance method against jamming target in sa-2F & E scenario that.....
you can hunt them with UPR method !

number 3 :
sa-3 missile during firing almost of time goes out from line of fly and missile rotating to left !
this happened done in lybia scenario also with alleid forces !

number 4 :
its about sa-3 again !
when u lock on jamming target and pusking ...
i moving the boresight for find explosion location and during this job
! sa-3 missile going out from fly line with move boresight !!!!

number 5 :
f105 wild weasels during vietnam war are miss with sa-2E !
when u switch to find them ... no one of them are in sky but with sa-2F they are visible !
{of course i test it only with first scenario at line break II .. no other scenarios ! please test}

part 2 of number 5 :
SNR ON AIR mode at After action report for sa-2E is missing !
for example when you are in ashuluk and switch on and off for several times then at after action report does not wrote
that when SNR goes to OFF or goes to ON

number 6 :


number 7 :
i see some bug in line break II
night-8 XII 26 / air defense battalion 274/86 not work ! (sa-2E.F)
night-9 XII 27 / air defense battalion 257/76 not work ! (sa-2E.F)

Posted By: max2012

Re: Bug reports - 07/30/13 06:37 PM


Error Dvina against the SR-71

Operation Linebacker-II

Day-2 XII 19. 13.45
Posted By: farokh

Re: Bug reports - 08/18/13 06:36 PM

in shilka PDF wrote ... TU= 4.17 is 2100 meters !

but look at my part of AAR !


00:07:39 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3264m
Target azimuth: 307°
Target elevation: 9°
Tu: 4.2s
darkcloud

4.2 = 3264 ? confused
Posted By: piston79

Re: Bug reports - 08/18/13 07:00 PM

Originally Posted By: farokh
in shilka PDF wrote ... TU= 4.17 is 2100 meters !

but look at my part of AAR !


00:07:39 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3264m
Target azimuth: 307°
Target elevation: 9°
Tu: 4.2s
darkcloud

4.2 = 3264 ? confused


Please, add you full AAR...
Posted By: farokh

Re: Bug reports - 08/18/13 07:31 PM

Click to reveal..
19:12pm 30th of June 1970
Second attack wave, against Cairo air defense.

Target:
10th Battery of the 5th Air Defense Missile Brigade

Attacking Force:
8 F-4E Kurnass
4 A-4E Ahit

ZSU-23-4V1


+++++++++++++++++
00:07:25, SNR ON AIR



00:09:04 ZSU-23-4V1 opened fire by all tubes.
Target distance: 3248m
Target azimuth: 148°
Target elevation: 2°
Tu: 4.2s

00:09:05 ZSU-23-4V1 closed fire, and shot 52pcs.



00:09:06 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2583m
Target azimuth: 147°
Target elevation: 3°
Tu: 3.1s

00:09:07 ZSU-23-4V1 closed fire, and shot 60pcs.



00:09:09 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1898m
Target azimuth: 145°
Target elevation: 3°
Tu: 2.1s

00:09:10 ZSU-23-4V1 closed fire, and shot 60pcs.



00:09:12 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1153m
Target azimuth: 138°
Target elevation: 5°
Tu: 1.1s

00:09:13 ZSU-23-4V1 closed fire, and shot 64pcs.


00:09:13 A-4E Ahit number 1 of flight-2 attacking 10th Battery of the 5th Air Defense Missile Brigade killed by OFZT.

00:09:13 A-4E Ahit number 1 of flight-2 attacking 10th Battery of the 5th Air Defense Missile Brigade killed by BZT.

00:09:13 A-4E Ahit number 1 of flight-2 attacking 10th Battery of the 5th Air Defense Missile Brigade killed by OFZT.


00:09:23 ZSU-23-4V1 opened fire by all tubes.
Target distance: 2053m
Target azimuth: 146°
Target elevation: 3°
Tu: 2.3s

00:09:24 ZSU-23-4V1 closed fire, and shot 52pcs.



00:09:26 ZSU-23-4V1 opened fire by all tubes.
Target distance: 1300m
Target azimuth: 141°
Target elevation: 4°
Tu: 1.3s

00:09:27 ZSU-23-4V1 closed fire, and shot 60pcs.


00:09:27 A-4E Ahit number 2 of flight-2 attacking 10th Battery of the 5th Air Defense Missile Brigade killed by OFZT.

00:09:27 A-4E Ahit number 2 of flight-2 attacking 10th Battery of the 5th Air Defense Missile Brigade killed by OFZT.

00:09:28 A-4E Ahit number 2 of flight-2 attacking 10th Battery of the 5th Air Defense Missile Brigade killed by OFZT.

00:09:28 A-4E Ahit number 2 of flight-2 attacking 10th Battery of the 5th Air Defense Missile Brigade killed by BZT.

00:09:28 A-4E Ahit number 2 of flight-2 attacking 10th Battery of the 5th Air Defense Missile Brigade killed by OFZT.
Posted By: piston79

Re: Bug reports - 08/18/13 08:50 PM

Target distance is where the target was when you opened fire.... As target approaches (with ~ 300 m/s at least), Tu in seconds is calculated where the target will be....

So if A-4 goes with zero parameter - 3284 meters - (Tu * Speed of A-4): 3284 - 4.2*300 m/s = 3284 - 1260 = 2024 meters....

I don't find a bug here.... Also, some of "bugs" you collect, are not bugs, like:

5, 6, 7...

3 and 4 - cannot understand what you're talking about....
Posted By: farokh

Re: Bug reports - 08/19/13 08:56 AM

Originally Posted By: piston79
Target distance is where the target was when you opened fire.... As target approaches (with ~ 300 m/s at least), Tu in seconds is calculated where the target will be....

So if A-4 goes with zero parameter - 3284 meters - (Tu * Speed of A-4): 3284 - 4.2*300 m/s = 3284 - 1260 = 2024 meters....

I don't find a bug here.... Also, some of "bugs" you collect, are not bugs, like:

5, 6, 7...

3 and 4 - cannot understand what you're talking about....


num 6 is my mistake but i test them again !
they already are bugs!

6.do u remember last month that we had one exercise in fb ?
and we test 5KM mode with K3 sa-2E !
but on our AAR no sign from SNR OFF time .... ! just test it man

7. still bugs ! please test them with sa-2 E . F

Posted By: piston79

Re: Bug reports - 08/19/13 10:07 AM

Originally Posted By: farokh

7. still bugs ! please test them with sa-2 E . F


No bug at all.... Please, check AAR....
Posted By: farokh

Re: Bug reports - 08/19/13 12:14 PM

Originally Posted By: piston79
[quote=farokh]
7. still bugs ! please test them with sa-2 E . F


+1 duh
Posted By: piston79

Re: Bug reports - 08/20/13 11:00 AM

Faroukh, please be more specific with 2, 3 and 4 from your bug list.... A video could be welcome....
Please, do not delete bugs from your initial list, even if they are proven false....
Posted By: farokh

Re: Bug reports - 08/20/13 11:16 AM

Originally Posted By: piston79
Faroukh, please be more specific with 2, 3 and 4 from your bug list.... A video could be welcome....
Please, do not delete bugs from your initial list, even if they are proven false....


about 3 and 4 i will create a video for future
but about 2 is so easy !
in real world could u fire sa-2 missiles by UPR method to a jammer target ?
if yes!!!
so its not a bug ! test it thumbsup
Posted By: piston79

Re: Bug reports - 08/20/13 06:53 PM

Originally Posted By: farokh

in real world could u fire sa-2 missiles by UPR method to a jammer target ?
if yes!!!
so its not a bug ! test it thumbsup


I did, but nothing happens... Could you test the same scenario with other systems? Did they behave like that?
Posted By: farokh

Re: Bug reports - 08/21/13 10:47 AM

Originally Posted By: piston79
Originally Posted By: farokh

in real world could u fire sa-2 missiles by UPR method to a jammer target ?
if yes!!!
so its not a bug ! test it thumbsup


I did, but nothing happens... Could you test the same scenario with other systems? Did they behave like that?


is it enough ?

Click to reveal..
22:06pm 30th of April, 1999.
Operation Allied Force, B-2A raid on Belgrade

Targets:
Nat'l MOD HQ
FRY MUP HQ
MOD HQ South
Serb MUP HQ
Army HQ Facility A

Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


5/250 rd PVO, Brestovik ( 210m)
S-75M3 Volkhov


+++++++++++++++++
00:00:00, SNR ON AIR


00:00:16, F-16CJ Falcon SEAD Number-3 launched AGM-88 HARM missile No. 1


00:01:46, V-759 5Ya23 Missile launched on Channel-1
Target distance: 35km
Target azimuth: 211°
Target elevation: 27°
Target altitude: 16.1km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: UPR (Half Lead)


00:01:57, F-16CJ Falcon SEAD Number-3 launched AGM-88 HARM missile No. 2


00:02:14, Missile exploded on Channel-1
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 34m)

00:02:27, IRZ knocked out by HARM


00:02:52, V-759 5Ya23 Missile launched on Channel-2
Target distance: 35km
Target azimuth: 150°
Target elevation: 24°
Target altitude: 14.3km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: K (Half Lead Elevated By Constans)


00:02:58, V-759 5Ya23 Missile launched on Channel-3
Target distance: 35km
Target azimuth: 148°
Target elevation: 25°
Target altitude: 14.8km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: UPR (Half Lead)


00:03:04, F-16CJ Falcon SEAD Number-4 launched AGM-88 HARM missile No. 1


00:03:29, Missile exploded on Channel-3
F-16CJ Falcon SEAD Number-4 killed by SAM. (miss distance: 30m)

Total, SNR On Air Time: 3min 32sec



Click to reveal..
02:04am 2nd of May, 1999.
Operation Allied Force, F-16CG Falcon DEAD mission against Belgrade Air Defense


Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


8/250 rd PVO, Stubline ( 89m)
S-75M3 Volkhov


+++++++++++++++++
00:00:00, SNR ON AIR


00:02:32, V-755 20DSU Missile launched on Channel-2
Target distance: 35km
Target azimuth: 124°
Target elevation: 20°
Target altitude: 12km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: UPR (Half Lead)


00:02:45, F-16CJ Weasel Falcon SEAD Crack-71 launched AGM-88 HARM missile No. 1

00:02:47, F-16CG Night Falcon DEAD Hammer-31 bombed AAA defending the Veliki Radinci reserve AFB, with LGB.

00:03:07, Missile exploded on Channel-2
F-16CJ Weasel Falcon SEAD Crack-71 killed by SAM. (miss distance: 48m)

00:03:51, V-755 20DSU Missile launched on Channel-1
Target distance: 35km
Target azimuth: 279°
Target elevation: 16°
Target altitude: 9.8km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: UPR (Half Lead)


00:04:24, Missile exploded on Channel-1
RQ-1 Predator UAV killed by SAM. (miss distance: 3m)

Total, SNR On Air Time: 4min 44sec
Posted By: piston79

Re: Bug reports - 08/21/13 06:11 PM

Is it same with SA-2F?
Posted By: farokh

Re: Bug reports - 08/22/13 01:08 PM

anything else ?

Click to reveal..
22:06pm 30th of April, 1999.
Operation Allied Force, B-2A raid on Belgrade

Targets:
Nat'l MOD HQ
FRY MUP HQ
MOD HQ South
Serb MUP HQ
Army HQ Facility A

Supporting force:
F-15C Eagle CAP
F-16CJ Falcon SEAD
EA-6B Prowler ECM
RQ-1 Predator UAV


5/250 rd PVO, Brestovik ( 210m)
SA-75M Dvina


+++++++++++++++++
00:01:44, SNR ON AIR


00:01:53, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:01:55, SNR ON AIR


00:02:05, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:02:09, SNR ON AIR


00:02:17, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:02:19, SNR ON AIR


00:02:23, V-750VMVK 11DMVK Missile launched on Channel-1
Target distance: 30km
Target azimuth: 244°
Target elevation: 34°
Target altitude: 17km
SNR mode: 55km
Missile guidance method: UPR (Half Lead)


00:02:34, F-16CJ Falcon SEAD Number-3 launched AGM-88 HARM missile No. 1


00:02:45, Missile exploded on Channel-1
F-16CJ Falcon SEAD Number-3 killed by SAM. (miss distance: 28m)

00:02:48, SNR OFF THE AIR
-----------------


00:02:54, IRZ knocked out by HARM


+++++++++++++++++
00:03:03, SNR ON AIR


00:03:10, SNR OFF THE AIR
-----------------


00:03:13, V-750VMVK 11DMVK Missile launched on Channel-2
Target distance: 30km
Target azimuth: 117°
Target elevation: 30°
Target altitude: 15.4km
SNR mode: 55km
Missile guidance method: UPR (Half Lead)


+++++++++++++++++
00:03:15, SNR ON AIR


00:03:23, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:03:27, SNR ON AIR


00:03:38, Missile exploded on Channel-2
F-16CJ Falcon SEAD Number-4 killed by SAM. (miss distance: 32m)

00:03:41, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 1min 26sec
Posted By: piston79

Re: Bug reports - 08/22/13 06:33 PM

yes.... which is your SAMSIM version? 0.926.x ?

And how about the video of your launching sequence? Does ANYONE could confirm that bug too?

Guys, help!
Posted By: farokh

Re: Bug reports - 08/22/13 08:50 PM

Originally Posted By: piston79
yes.... which is your SAMSIM version? 0.926.x ?

And how about the video of your launching sequence? Does ANYONE could confirm that bug too?

Guys, help!
my version is 926c
maybe for tommarow i make a short video from this ........
Posted By: Vadifon

Re: Bug reports - 08/22/13 11:09 PM

Taken from Manual Supplement by Vintorez:-
Rab-ot-VM is of some use when shooting at low-altitude jamming targets. A “chaff corridor”, which detonates your missiles before the target, is conceivable only for high-altitude targets. In such case, do not forget to switch radio fuse 100-m sensitivity on.

Video shows imitation shooting at the low-altitude jamming target [USU NLC + RAB OT VM + TT]. (Ideal conditions)
No hits, if the fuse in the switch "USU NLC"/"ZAGRUB RV"
The average miss distance -40m.
Probably bug

Posted By: Vadifon

Re: Bug reports - 08/23/13 12:44 AM

Probably bug
Click to reveal..



Posted By: piston79

Re: Bug reports - 08/23/13 04:45 AM

Originally Posted By: farokh
my version is 926c
maybe for tommarow i make a short video from this ........


Mine is 0.926.8, which, I believe, is last one....
Posted By: farokh

Re: Bug reports - 08/23/13 07:15 AM

Originally Posted By: Vadifon
Probably bug





hi dear .... what is your samsim version ?
also please tell me that you choose f-111 on ashuluk by jamming pod dm / cm or not ?
Posted By: Vadifon

Re: Bug reports - 08/23/13 10:02 AM

Originally Posted By: farokh

hi dear .... what is your samsim version ?
also please tell me that you choose f-111 on ashuluk by jamming pod dm / cm or not ?


SAMSim_v926_7
Volhov
Jamming free
if P>10km it happens in 100% of cases
Posted By: farokh

Re: Bug reports - 08/23/13 10:35 AM

Originally Posted By: Vadifon
Originally Posted By: farokh

hi dear .... what is your samsim version ?
also please tell me that you choose f-111 on ashuluk by jamming pod dm / cm or not ?


SAMSim_v926_7
Volhov
Jamming free
if P>10km it happens in 100% of cases


i try this... f-111 without jamming

i dont see nothing unnormal !

my missile exploded from 90+ meters of the target !

Click to reveal..
Asuluk training ground.

Practice target:
RM-207M Belka [program-2] simulating F-111 Aardvark

S-75M3 Volkhov


+++++++++++++++++
00:00:00, SNR ON AIR


00:00:06, SNR OFF THE AIR
-----------------


+++++++++++++++++
00:00:06, SNR ON AIR


00:10, Practice target RM-207M Belka [program-2] simulating F-111 Aardvark launched

00:01:31, V-755 20DSU Missile launched on Channel-1
Target distance: 22km
Target azimuth: 85°
Target elevation: 6°
Target altitude: 2.5km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: UPR (Half Lead)


00:01:36, V-755 20DSU Missile launched on Channel-2
Target distance: 22km
Target azimuth: 82°
Target elevation: 6°
Target altitude: 2.5km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: K (Half Lead Elevated By Constans)


00:01:42, V-755 20DSU Missile launched on Channel-3
Target distance: 22km
Target azimuth: 77°
Target elevation: 6°
Target altitude: 2.5km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: T/T (Three Point)


00:01:50, Missile exploded on Channel-1

00:02:01, Missile exploded on Channel-3
Practice target RM-207M Belka [program-2] simulating F-111 Aardvark killed by SAM. (miss distance: 94m)

00:02:08, Missile exploded on Channel-2

Total, SNR On Air Time: 2min 44sec


you think missiles fired by UPR and K method should kill the target like T/T?

ps: of course in RABOT VM method usually i JUST locked azimuth and elevation degree ! not range locker used by me !
and T/T can catch it very smooth

PS2 : really i dont get your problem ! would you explain about your problem ?
Posted By: Vadifon

Re: Bug reports - 08/23/13 11:52 AM

Originally Posted By: farokh

you think missiles fired by UPR and K method should kill the target like T/T?
ps: of course in RABOT VM method usually i JUST locked azimuth and elevation degree ! not range locker used by me !
and T/T can catch it very smooth
PS2 : really i dont get your problem ! would you explain about your problem ?


The problem is not a miss/hit (is the result of a strange missile trajectory)
It's only guidance problem.
video later

Click to reveal..

Posted By: farokh

Re: Bug reports - 08/23/13 12:33 PM

Originally Posted By: Vadifon
Originally Posted By: farokh

you think missiles fired by UPR and K method should kill the target like T/T?
ps: of course in RABOT VM method usually i JUST locked azimuth and elevation degree ! not range locker used by me !
and T/T can catch it very smooth
PS2 : really i dont get your problem ! would you explain about your problem ?


The problem is not a miss/hit (is the result of a strange missile trajectory)
It's only guidance problem.
video later



humm... i see
its not the bug at all
please read the advance manual completly !
in there wrote about UPR flight path !
usually ...
UPR flying to impact zone with 4 degree Further of target that missile and target will meet together at there
with UPR and K your missiles doing more maneuver
but T/t flying direct to the target !
thumbsup
Posted By: farokh

Re: Bug reports - 08/23/13 06:50 PM

bug number 7

hpasp... LORO mode is the subject
in sa-2E pdf wrote ... we can detect fighter between jamming line by LORO from 30km
but in libya and operation allied forces i cant detect them at all from 20 km or closer
Posted By: piston79

Re: Bug reports - 08/23/13 07:38 PM

Originally Posted By: farokh
bug number 7

hpasp... LORO mode is the subject
in sa-2E pdf wrote ... we can detect fighter between jamming line by LORO from 30km
but in libya and operation allied forces i cant detect them at all from 20 km or closer


Jamming pod detected...:

Quote:
The burn through range is depending on the target aspect (heading in relation to the radar) and the radar beam type:
Against fighter-sized targets:
using wide-beam mode: 5 ~ 10km
using narrow beam - LORO mode: 10 ~ 20km
Against bomber-sized targets.....


.... biggrin
Posted By: farokh

Re: Bug reports - 08/23/13 09:20 PM

Originally Posted By: piston79
Originally Posted By: farokh
bug number 7

hpasp... LORO mode is the subject
in sa-2E pdf wrote ... we can detect fighter between jamming line by LORO from 30km
but in libya and operation allied forces i cant detect them at all from 20 km or closer


Jamming pod detected...:

Quote:
The burn through range is depending on the target aspect (heading in relation to the radar) and the radar beam type:
Against fighter-sized targets:
using wide-beam mode: 5 ~ 10km
using narrow beam - LORO mode: 10 ~ 20km
Against bomber-sized targets.....


.... biggrin


check again ! 10 till 20 is for fighter size in LORO and 15 till 30 is for bombers in LORO

PS:... i download latest version of samsim... i try hit the A-4 in ashuluk target !
usually A-4 alt was around 400 till 700 ... but right now in this version in after action report wrote
ALT = 4 km !
please test it and put your result in here


killed by rabot-vm based on T/T

Click to reveal..
Asuluk training ground.

Practice target:
LA-17M [program-1] simulating A-4 Skyhawk

S-75M3 Volkhov


00:00, Practice target LA-17M [program-1] simulating A-4 Skyhawk launched

+++++++++++++++++
00:00:16, SNR ON AIR


00:02:26, V-755 20DSU Missile launched on Channel-3
Target distance: 31km
Target azimuth: 63°
Target elevation: 7°
Target altitude: 4.1km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: T/T (Three Point)


00:02:51, V-755 20DSU Missile launched on Channel-1
Target distance: 31km
Target azimuth: 60°
Target elevation: 8°
Target altitude: 4.4km
SNR mode: Wide Beam H<5 - 75km
Missile guidance method: T/T (Three Point)


00:02:56, Missile exploded on Channel-3
Practice target LA-17M [program-1] simulating A-4 Skyhawk killed by SAM. (miss distance: 36m)

00:03:10, Missile exploded on Channel-1

Total, SNR On Air Time: 3min 16sec
Posted By: piston79

Re: Bug reports - 08/23/13 09:26 PM

Originally Posted By: farokh

PS:... i download latest version of samsim... i try hit the A-4 in ashuluk target !
usually A-4 alt was around 400 till 700 ... but right now in this version in after action report wrote
ALT = 4 km !
please test it and put your result in here



This is an old bug, that reappeared again, 'caused by "<5 km" mode... Old code used, probably...
Posted By: Vadifon

Re: Bug reports - 08/29/13 01:09 PM

Originally Posted By: farokh

humm... i see
its not the bug at all
please read the advance manual completly !

Of course reading and many more in Russian
1) Why only 4 degree? 6 or 7 degrees would be more correct. [see attach]

Click to reveal..



Quote:

in there wrote about UPR flight path !
usually ...
UPR flying to impact zone with 4 degree Further of target that missile and target will meet together at there
with UPR and K your missiles doing more maneuver
but T/t flying direct to the target !
thumbsup


I think the current version has an incorrect missile flight path when impact point further than 4 degrees.
Therefore TT more effective than UPR in the case when P > 15-20 km. [at high-speed V/H=const target] ...should be conversely.

Incorrect flight path - because missile overstay at the edge of "+/-4° gate" until impact point will not be in the "+/-4° gate" [see attach]

Click to reveal..








Posted By: piston79

Re: Bug reports - 09/05/13 12:42 PM

Originally Posted By: Vadifon

Of course reading and many more in Russian
1) Why only 4 degree? 6 or 7 degrees would be more correct. [see attach]

Click to reveal..




Since now I don't find an exact explanation about that, just some thoughts about it:

1. The UPR method is a half-lead method, so no big lead is needed (compare with SA-5).
2. The missile is unguided right after launch, it must "hit" strobes, thus some oscilations during this initiation stage are in place (as it is relatively close), also launchers are "leading" too, depending of antena rotation speed, so this could be also a reason for such difference between lead angle and RPK diagram size....
3. Missiles aerodinamic matters too...

Anyway, lead angle is more than a half of RPK diagram (5-7.5 degrees), so no big difference IMHO...
Posted By: Vadifon

Re: Bug reports - 09/06/13 12:49 AM

...remained unconvinced smile
Posted By: piston79

Re: Bug reports - 09/06/13 05:55 AM

Originally Posted By: Vadifon
...remained unconvinced smile


If you found the reason, please, be so kind to share it with the community... I spoked with an ex-chief enginier of a AirDefence brigade and an officer, that served on Volkhov....
Posted By: Vadifon

Re: Bug reports - 09/09/13 09:38 PM

+/-8°=16°

SAM Sim: +/-4°=8°
Posted By: piston79

Re: Bug reports - 09/10/13 06:42 AM

Originally Posted By: Vadifon
+/-8°=16°

SAM Sim: +/-4°=8°


The attach is from the project documentation, probably they did not relize it at this way in reality....

http://simhq.com/forum/ubbthreads.php/topics/3834070/Re_S_75M3_Volhov_SA_2E_Guideli#Post3834070
Posted By: Hpasp

Re: Bug reports - 09/15/13 05:47 PM

Originally Posted By: Vadifon
...remained unconvinced smile


This is exactly why I require ex Fire Control Officers to help creating SAMSIM.
They were there and done that...

Live missile is flying to kill RS2US target at Ustka...

Posted By: piston79

Re: Bug reports - 09/15/13 06:44 PM

Originally Posted By: piston79


Since now I don't find an exact explanation about that, just some thoughts about it:

1. The UPR method is a half-lead method, so no big lead is needed (compare with SA-5).
2. The missile is unguided right after launch, it must "hit" strobes, thus some oscilations during this initiation stage are in place (as it is relatively close), also launchers are "leading" too, depending of antena rotation speed, so this could be also a reason for such difference between lead angle and RPK diagram size....
3. Missiles aerodinamic matters too...

Anyway, lead angle is more than a half of RPK diagram (5-7.5 degrees), so no big difference IMHO...


4. When bigger lead angle is needed, bigger overload capacity of the missiles is needed too....

-----------------------------

Click to reveal..



Looks like K method on P=0... wink
Posted By: Hpasp

Re: Bug reports - 09/15/13 07:11 PM

Originally Posted By: piston79


Looks like K method on P=0... wink


UPR method on P=0 RS2US missile.
Posted By: farokh

Re: Bug reports - 10/18/13 08:29 PM

little bug in ashuluk !

i hunt it under 300 meters!!!

Click to reveal..
Asuluk training ground.

Practice target:
RM-217 Zvezda [program-1] simulating Tornado

S-200VE Vega-E


00:44, Practice target RM-217 Zvezda [program-1] simulating Tornado launched

+++++++++++++++++
00:00:52, SNR ON AIR


00:01:09, Missile launched from launcher-1
Target distance: 48km
Target azimuth: 57°
Target elevation: 0°
Target angular speed: 419m/s (1.4 Mach)
Target altitude: 251m
RPC mode: FKM - Narrow Beam
GSN mode: Acquire target during flight
Received signal strength: 35.6dB


00:01:14, Missile launched from launcher-2
Target distance: 45km
Target azimuth: 57°
Target elevation: 0°
Target angular speed: 492m/s (1.7 Mach)
Target altitude: 186m
RPC mode: FKM - Narrow Beam
GSN mode: Acquire target during flight
Received signal strength: 35.9dB


00:01:40, Missile exploded
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 12m)

00:01:44, Missile exploded
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 9m)

Total, SNR On Air Time: 54sec
Posted By: Billsnavycareer

Re: Bug reports - 10/20/13 10:58 PM

I have a problem of error 52 from vb6 setup toolkit when I tried to install the simulator on my laptop. The OS is Win7/64-bit and I manually copied all the dll files to the system, but the still, the problem cannot be fixed. Hpasp, do u have any idea? It's quite weird that VB shall work fine with Win7/64-bit (unlike InstallShield 2x).
Posted By: Hpasp

Re: Bug reports - 10/21/13 09:11 AM

You need to register the DLL files, or install the program properly.
(installation does the DLL registration)
Posted By: farokh

Re: Bug reports - 11/07/13 09:47 AM

this one is missed

Posted By: piston79

Re: Bug reports - 11/10/13 04:17 PM

Originally Posted By: farokh
little bug in ashuluk !

i hunt it under 300 meters!!!

Click to reveal..
Asuluk training ground.

Practice target:
RM-217 Zvezda [program-1] simulating Tornado

S-200VE Vega-E


00:44, Practice target RM-217 Zvezda [program-1] simulating Tornado launched

+++++++++++++++++
00:00:52, SNR ON AIR


00:01:09, Missile launched from launcher-1
Target distance: 48km
Target azimuth: 57°
Target elevation: 0°
Target angular speed: 419m/s (1.4 Mach)
Target altitude: 251m
RPC mode: FKM - Narrow Beam
GSN mode: Acquire target during flight
Received signal strength: 35.6dB


00:01:14, Missile launched from launcher-2
Target distance: 45km
Target azimuth: 57°
Target elevation: 0°
Target angular speed: 492m/s (1.7 Mach)
Target altitude: 186m
RPC mode: FKM - Narrow Beam
GSN mode: Acquire target during flight
Received signal strength: 35.9dB


00:01:40, Missile exploded
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 12m)

00:01:44, Missile exploded
Practice target RM-217 Zvezda [program-1] simulating Tornado killed by SAM. (miss distance: 9m)

Total, SNR On Air Time: 54sec


According russian army S-200 manual from 1984, if the RPN has a stable track on target, the target could be engaged in altitudes less than 300 meters....
Posted By: piston79

Re: Bug reports - 02/12/14 08:01 PM

This Ganef will never work fine... banghead

What is wrong with damn missiles? Also last detonation (400 meters away and a kill?)..

https://www.mediafire.com/?39xgh4c742rhoy8
Posted By: milo11

Re: Bug reports - 03/11/14 07:11 PM

Hi guys, i´m back to this board after a forced break, and i´m starting to practice again with the sim. My question is, did the "Sa-2 Dvina no harm mistery in libian scenarios" got solved?

Anyway thx again for the sim, hoping the new version to arrive soon.
Posted By: piston79

Re: Bug reports - 03/11/14 07:57 PM

Originally Posted By: milo11
Hi guys, i´m back to this board after a forced break, and i´m starting to practice again with the sim. My question is, did the "Sa-2 Dvina no harm mistery in libian scenarios" got solved?


Hi milo1! nice to have you back here! Don't go away for long again! wink

There is no bugfix version yet.... Last instructions fom the developer were that SA-8 and fixes will be released together, but no 100% sure about that.... anyway, if any bugs appeared give them here!!!
Posted By: Hpasp

Re: Bug reports - 05/01/14 12:16 PM

OSA bugs so far...

1, Benghazi - 0 missiles loaded.
2, Libya - no ground clutter
Posted By: Mdore

Re: Bug reports - 05/01/14 12:34 PM

I did find another bug, if you use the SA-8, then use the SA-4 without restarting the programme, the SA-4 won't auto-point at targets you've selected.
Posted By: farokh

Re: Bug reports - 05/01/14 12:48 PM

Originally Posted By: Mdore
I did find another bug, if you use the SA-8, then use the SA-4 without restarting the programme, the SA-4 won't auto-point at targets you've selected.


mdore...@ can u create a video of this bug reading
Posted By: farokh

Re: Bug reports - 05/01/14 12:58 PM

wow... what a cool bug bump
i find another one !

in ashuluk site ... the helicopter do not explode at all !!! when i send several missiles to it
helicopter do not explode duck
Posted By: Hpasp

Re: Bug reports - 05/01/14 01:16 PM

Originally Posted By: farokh
wow... what a cool bug bump
i find another one !

in ashuluk site ... the helicopter do not explode at all !!! when i send several missiles to it
helicopter do not explode duck


You need to use METHOD-FI against helos...
Posted By: ePap

Re: Bug reports - 05/01/14 01:21 PM

When fly very low and very slow and closer to 7km range, HELOs engaged by (Fi) mode.
In all other cases are engaged like other targets.
Posted By: farokh

Re: Bug reports - 05/01/14 05:40 PM

i found 2 more bugs in OSA

first... in ashuluk page... wrote 3m33m2 !!!

second ... in first scenario of cairo ! exactly in 5.10 position... OSA doesnt arm with missiles..
hpasp... please fix this scenario for us frown
Posted By: Hpasp

Re: Bug reports - 05/01/14 05:43 PM

first scenario of cairo ! exactly in 5.10 position... OSA doesnt arm with missiles..

it does.
Posted By: max2012

Re: Bug reports - 05/01/14 06:53 PM


Question about Hpasp?

Training objectives where they are not present on the screen.

Greece there target AH-64 Apache where it on the radar as to see her.
Posted By: Mdore

Re: Bug reports - 05/04/14 06:19 PM

In practice, helicopters don't appear on camera.

When you shoot a target so it's leaving a trail of smoke. If it goes past 0 degrees, I.E. directly north of you, the smoke trail will instantly leave a 360 degree trail of smoke all around you.
Posted By: Hpasp

Re: Bug reports - 05/04/14 06:34 PM

Originally Posted By: Mdore
In practice, helicopters don't appear on camera.

When you shoot a target so it's leaving a trail of smoke. If it goes past 0 degrees, I.E. directly north of you, the smoke trail will instantly leave a 360 degree trail of smoke all around you.


Known one thumbsup
Posted By: Hpasp

Re: Bug reports - 05/09/14 01:19 PM

Originally Posted By: Amazon
Hello. How I can resolve problem with SA-8 error: Can't create autoredraw image?


Unfortunately OSA requires ~4GB of RAM.
If you use 32bit Windows, and have 4GB RAM, you can try this...

http://knowledge.autodesk.com/support/au...ndows-XP-s.html



... or buy more RAM and a 64bit OS.
Posted By: PN79

Re: Bug reports - 05/10/14 09:56 AM

Hello Hpasp,
at first big thanks for OSA. Now small bug report: when I start simulator with OSA in Hungary with one plane everything is OK but then I quit Hungary (but not simulator) and I start Hungary with another plane again for the second time - but in this second round planes are not seen on the plotting board and it seems there are not in the air. Can you please check it? Very thanks.
Posted By: Hpasp

Re: Bug reports - 05/10/14 11:12 AM

OSA less than 4Gb memory bug looks like this, when you start OSA sim:



This happens if you have less than 4Gb of RAM, or your 32bit OS doesn't allow SAMSIM to use 3Gb of it.
This is a generic OS problem, solution is to buy 4Gb RAM...
... or you can try this:



http://knowledge.autodesk.com/support/au...ndows-XP-s.html


Posted By: Sten_MkIIs

Re: Bug reports - 05/13/14 11:51 AM

May be it isn't a bug, but it looks like enemy HARM missiles can target SNR of S-75 while it ofF air ("PEREDATCHIK" is off, "AHT" is on). Provided manual says otherwise, but in any combat scenario i still got SNR knocked down by HARM.
Posted By: Alien_MasterMynd

Re: Bug reports - 05/13/14 12:41 PM

There are two factors which can lead to SNR destruction:

1) RPK transmitter, check that you are not transmitting missile command signals (also when BR and 75km mode without missiles in the air)

2) HARM has a target memory, so when you observe a HARM launch and turn the transmitter off too late (when the HARM is quite close) you will still suffer the hit....
Posted By: Sten_MkIIs

Re: Bug reports - 05/13/14 02:17 PM

RPK is off too. SNR got hit even if it weren't on air at all. That's why i'm posting this in BugReports.
Kinda weird...
Posted By: farokh

Re: Bug reports - 05/13/14 02:28 PM

its not a bug young boy !
you must turn off your trasmitter soon before harm missiles went to terminal phase !!!!
you have got only few seconds to do it !

please work with OSA first .. and go for dvina for line breake II
Posted By: Sten_MkIIs

Re: Bug reports - 05/13/14 04:29 PM

I'm not a young boy, i have played this sim from much older version than this. And you misunderstood my posts. Again - all transmitters is OFF from start, only ANTENNA is opened for receive. Still got hit. In older versions it worked better. It is a bug.
Posted By: piston79

Re: Bug reports - 05/13/14 04:55 PM

Originally Posted By: Sten_MkIIs
I'm not a young boy, i have played this sim from much older version than this. And you misunderstood my posts. Again - all transmitters is OFF from start, only ANTENNA is opened for receive. Still got hit. In older versions it worked better. It is a bug.


Which particular scenario?
Posted By: Sten_MkIIs

Re: Bug reports - 05/13/14 06:06 PM

Livia, Linebacker.
Posted By: Alien_MasterMynd

Re: Bug reports - 05/14/14 07:03 AM

Which SAM site and which mission? I will try it....
Posted By: Sten_MkIIs

Re: Bug reports - 05/14/14 08:21 AM

Linebacker II: night-1 wave 3 XII.19 04-40
257/77 Airdefence battalion
Posted By: Hpasp

Re: Bug reports - 05/14/14 06:29 PM

Originally Posted By: PN79
Hello Hpasp,
at first big thanks for OSA. Now small bug report: when I start simulator with OSA in Hungary with one plane everything is OK but then I quit Hungary (but not simulator) and I start Hungary with another plane again for the second time - but in this second round planes are not seen on the plotting board and it seems there are not in the air. Can you please check it? Very thanks.


Found this one, and will be corrected in 0.928.2
Posted By: Hpasp

Re: Bug reports - 05/14/14 06:30 PM

Originally Posted By: Sten_MkIIs
Linebacker II: night-1 wave 3 XII.19 04-40
257/77 Airdefence battalion


There were no HARM at that time.
Can you upload AAR, 3DAAR?
Posted By: Sten_MkIIs

Re: Bug reports - 05/14/14 07:15 PM

I was able to pinpont problem - RPK transmitter self activates and SNR getting hit. It cannot be turn off. Tested on Tripoli raid. Sorry for mislead - in vietnam this aint a problem.

In livia scenario:

2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Tripoli.

Targets:
Bab al-Aziziyah barracks - 6 F-111F Aardvark, each armed with 4 GBU-10 LGB
Murat Sidi Bilal Naval base - 3 F-111F Aardvark, each armed with 4 GBU-10 LGB
Tripoli AFB - 5 F-111F Aardvark, each armed with 12 Mk.82/BSU-49 high-drag bombs

Supporting force:
6 A-7E Corsair-II SEAD (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
4 F-14A Tomcat CAP (VF-33 Starfighters, VF-102 Diamondbacks from the CV-66 USS America)
3 EF-111A Raven ECM
1 EA-6B Prowler ECM (VMAQ-2 Playboys from the CV-43 USS America)

S-75M3 Volkhov

00:00:36, F-111F Remit-31 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.

+++++++++++++++++
00:00:54, SNR ON AIR


00:01:11, A-7E Corsair-II No.1, VA-46 Clansmen launched AGM-88 HARM missile No. 1

00:01:43, F-111F Remit-33 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.

00:02:14, SNR knocked out by HARM


00:02:15, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 1min 15sec

Screenshot:



So the final problem - self activation RPK.
Posted By: Hpasp

Re: Bug reports - 05/14/14 07:27 PM

Its a feature! Not a BUG!
salute

Background: In Vietnam the US planes were frightened by the Dvina emitting RPK signals, without missile launch.
US was busy calculating these electronic launches, and sometimes still citing more launched Dvina missile in Vietnam, than ever were fabricated smile

The Soviet designers believed that a good idea would be to introduce auto RPK (BR mode + 75km) at the Volhov.
US designers believed that a good idea would be to introduce HARM (guiding at RPK signal).

In Libya the two idea met each other with the following results...

Posted By: Sten_MkIIs

Re: Bug reports - 05/14/14 07:34 PM

Hey it's not fair! no really. How this sistem operates in this scenario? It is impossible to use. Not that i complaining about reality but it's uncontrollable. You got hit in any way on 2 minutes from start all the time, no matter what youve done.

UPD: Read your edit, thanks for answers. I just spent too much time with old version SAMSim, things were different :))
So its impossible to survive in Livia?
Posted By: Hpasp

Re: Bug reports - 05/14/14 07:39 PM

Click "BR" just before missile launch, or use 35km mode.
Posted By: Hpasp

Re: Bug reports - 05/14/14 07:54 PM

Originally Posted By: Sten_MkIIs
Hey it's not fair! no really.
So its impossible to survive in Livia?


Usually US pulls a new trick in each scenario, that was not fair at that time...

- Egypt - very low flying, aggressively maneuvering planes
- Vietnam - massive jamming, SAM site blanket bombing with B52
- Libya - HARM launched from the back, on RPK signal
- Yugoslavia - Stealth
...
- future war - AGM-88E AARGM - THAT will not be fair.
(only option left is to shoot it down)
Posted By: Alien_MasterMynd

Re: Bug reports - 05/15/14 07:41 AM

Originally Posted By: Sten_MkIIs
I was able to pinpont problem - RPK transmitter self activates and SNR getting hit. It cannot be turn off. Tested on Tripoli raid. Sorry for mislead - in vietnam this aint a problem.

In livia scenario:

2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Tripoli.

Targets:
Bab al-Aziziyah barracks - 6 F-111F Aardvark, each armed with 4 GBU-10 LGB
Murat Sidi Bilal Naval base - 3 F-111F Aardvark, each armed with 4 GBU-10 LGB
Tripoli AFB - 5 F-111F Aardvark, each armed with 12 Mk.82/BSU-49 high-drag bombs

Supporting force:
6 A-7E Corsair-II SEAD (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
4 F-14A Tomcat CAP (VF-33 Starfighters, VF-102 Diamondbacks from the CV-66 USS America)
3 EF-111A Raven ECM
1 EA-6B Prowler ECM (VMAQ-2 Playboys from the CV-43 USS America)

S-75M3 Volkhov

00:00:36, F-111F Remit-31 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.

+++++++++++++++++
00:00:54, SNR ON AIR


00:01:11, A-7E Corsair-II No.1, VA-46 Clansmen launched AGM-88 HARM missile No. 1

00:01:43, F-111F Remit-33 bombed Bab al-Aziziyah barracks, with 4 GBU-10 LGB.

00:02:14, SNR knocked out by HARM


00:02:15, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 1min 15sec

Screenshot:



So the final problem - self activation RPK.


And what I wrote before, BR + 75km :-)))))
Posted By: Hpasp

Re: Bug reports - 05/15/14 03:36 PM

Originally Posted By: farokh
Originally Posted By: Mdore
I did find another bug, if you use the SA-8, then use the SA-4 without restarting the programme, the SA-4 won't auto-point at targets you've selected.


mdore...@ can u create a video of this bug reading


Found this one, and will be corrected in 0.928.2
Posted By: piston79

Re: Bug reports - 05/15/14 04:22 PM

Originally Posted By: Hpasp
Its a feature! Not a BUG!
salute

The Soviet designers believed that a good idea would be to introduce auto RPK (BR mode + 75km) at the Volhov.




It is easy to solve that problem.... Really strange!
Posted By: ePap

Re: Bug reports - 05/15/14 04:30 PM

Dear Hpasp.
What else do you intend to include to this upgrade(0.928.2) concerning OSA AK? smile2
Posted By: Hpasp

Re: Bug reports - 05/15/14 05:13 PM

Originally Posted By: ePap
Dear Hpasp.
What else do you intend to include to this upgrade(0.928.2) concerning OSA AK? smile2


Lock on Jamming targets is somehow not working, but still not found it why...
banghead
Posted By: ePap

Re: Bug reports - 05/15/14 05:17 PM

Originally Posted By: Hpasp
Originally Posted By: ePap
Dear Hpasp.
What else do you intend to include to this upgrade(0.928.2) concerning OSA AK? smile2


Lock on Jamming targets is somehow not working, but still not found it why...
banghead


What do you mean ,lock on is not working on jamming targets?
What do you want from OSA AK to do?
Posted By: farokh

Re: Bug reports - 05/15/14 05:27 PM

Originally Posted By: ePap
Dear Hpasp.
What else do you intend to include to this upgrade(0.928.2) concerning OSA AK? smile2

epap cool you should ask it in future plan topic thumbsup
Posted By: ePap

Re: Bug reports - 05/15/14 05:48 PM

Originally Posted By: farokh
Originally Posted By: ePap
Dear Hpasp.
What else do you intend to include to this upgrade(0.928.2) concerning OSA AK? smile2

epap cool you should ask it in future plan topic thumbsup


Why,young boy ? smile2
Posted By: piston79

Re: Bug reports - 05/16/14 07:11 PM

Our forum mate Vadifon pointed at a strange thing with SA-2E (with F too, probably) - strange missile flight path in UPR/K mode....:

Originally Posted By: Vadifon
Probably bug






I am not sure how it was programed (only Hpasp knew), but definitely this is not a correct behavior. At first sight it looks like it is like K method, but in beta plane. Thanks to user Rackot from guns.ru I got some details about K1 and K2 commands and missile profiles:
Click to reveal..












http://forum.guns.ru/forummessage/71/1161030-92.html

We need some help from a russian speaking engineer to help with data, as I am not educated enough to "decode" principles of missile guidance....

Posted By: Hpasp

Re: Bug reports - 05/16/14 07:29 PM

I am not sure how it was programed (only Hpasp knew), but definitely this is not a correct behavior.
cowboy

- target is flying with great Parameter, from left to right.
- In this case of UPR/K method, the missile is leading the target in azimuth to the right(green arrow).
- This lead angle is limited by the Dvina/Volhov antenna system design.
- Missile is flying at the right limit (red line).
- When the target gets closer to the missile (blue arrow), the missile starts to aim the half lead point instead of the right limit. <-- this point could be the marked one at the comment above (white)



The red section is where the missile right lead is limited from the target azimuth.
Blue section is where the missile is flying ideal Half Lead.



If you have the 3DAAR, you can measure the azimuth limit of the Volhov/Dvina design...
cool

This is an advanced++ topic, but if you understand why the missile behaviour this way, you again stepped to a new level.
Posted By: piston79

Re: Bug reports - 05/16/14 07:43 PM

Yes, it is when P is above 10 km...

Still, this is not the right way, I think.... Tnagental speed gotta be increasing with aprroaching of the target to the ZRK (maximum is when target goes true the parameter line and start receding...

Thus the lead angle gotta be smaller and increasing with missiles approaching the target (max is 4 degrees)...

Posted By: Hpasp

Re: Bug reports - 05/16/14 07:52 PM

Originally Posted By: piston79
Yes, it is when P is above 10 km...

Still, this is not the right way, I think.... Tnagental speed gotta be increasing with aprroaching of the target to the ZRK (maximum is when target goes true the parameter line and start receding...

Thus the lead angle gotta be smaller and increasing with missiles approaching the target (max is 4 degrees)...



Target - Red line
T/T guidance - Green line
Ideal UPR guidance without antenna azimuth limitation - dark blue
Real limited UPR guidance - bright blue


Posted By: piston79

Re: Bug reports - 05/16/14 08:35 PM

Here VADIFON does some charts also:

http://simhq.com/forum/ubbthreads.php/topics/3828810/Re:_Bug_reports#Post3828810











Posted By: Hpasp

Re: Bug reports - 05/18/14 07:40 AM

Originally Posted By: piston79
Here VADIFON does some charts also:



3 points:

- This picture nicely shows what happens (talking about missile-1), just one part of the equation is missing here...
... instead of the theoretical path, missile actually flies the kinematical path.
(if you look at the the picture more closely, you can see that the missile started left turn earlier.)

- Another problem is that Google Earth is displaying events only by seconds, and interpolates between.
(What you see on Karat is the real missile flight path, and it is much flatter at Google Earth)

- As we are discussing HALF Lead instead of FULL lead, the targeted impact point is not fixed at the target path, but moving in the direction where the target flies, as the missile is getting closer.
Posted By: Hpasp

Re: Bug reports - 05/18/14 11:44 AM

Originally Posted By: piston79
Here VADIFON does some charts also:



RPK radiation pattern has nothing to do here, the main limitation of lead angle is the two wide-beam antenna, that tracks the missiles beside the target.
Posted By: piston79

Re: Bug reports - 05/18/14 04:07 PM

Originally Posted By: Hpasp


3 points:

- This picture nicely shows what happens (talking about missile-1), just one part of the equation is missing here...
... instead of the theoretical path, missile actually flies the kinematical path.
(if you look at the the picture more closely, you can see that the missile started left turn earlier.)

- Another problem is that Google Earth is displaying events only by seconds, and interpolates between.
(What you see on Karat is the real missile flight path, and it is much flatter at Google Earth)

- As we are discussing HALF Lead instead of FULL lead, the targeted impact point is not fixed at the target path, but moving in the direction where the target flies, as the missile is getting closer.


So, you believe this is the right behaviour and no bug? Does any officer confirms that?

EDIT: As the target is traveling with a almost constant speed, the system must calculate the impact point.... Because of the 4 degrees limit, the missile will go to this limit and when the point of impact (PoI) appears to be inside this 4 degrees angle, the missile will go for it... Here we have a factor which is the distance between missile and target (PoI). I think this is the factor which is the most important for the calculation....
Posted By: Hpasp

Re: Bug reports - 05/19/14 07:44 AM

Originally Posted By: piston79
Originally Posted By: Hpasp


3 points:

- This picture nicely shows what happens (talking about missile-1), just one part of the equation is missing here...
... instead of the theoretical path, missile actually flies the kinematical path.
(if you look at the the picture more closely, you can see that the missile started left turn earlier.)

- Another problem is that Google Earth is displaying events only by seconds, and interpolates between.
(What you see on Karat is the real missile flight path, and it is much flatter at Google Earth)

- As we are discussing HALF Lead instead of FULL lead, the targeted impact point is not fixed at the target path, but moving in the direction where the target flies, as the missile is getting closer.


So, you believe this is the right behaviour and no bug? Does any officer confirms that?

EDIT: As the target is traveling with a almost constant speed, the system must calculate the impact point.... Because of the 4 degrees limit, the missile will go to this limit and when the point of impact (PoI) appears to be inside this 4 degrees angle, the missile will go for it... Here we have a factor which is the distance between missile and target (PoI). I think this is the factor which is the most important for the calculation....


This is the correct missile behavior.
The only debatable part what I see is the lead angle limitation.
(if it is 4 degrees, or 3.5 or less than that)
Posted By: piston79

Re: Bug reports - 05/19/14 05:25 PM

Originally Posted By: Hpasp


This is the correct missile behavior.
The only debatable part what I see is the lead angle limitation.
(if it is 4 degrees, or 3.5 or less than that)



I think the answer is here: http://forum.guns.ru/forummessage/71/1161030-92.html

(formulas from 107)....

For half lead method (epsilon/Beta) it is equal minus angular speed of line of sight of the target multiplied on limit of distance "missile-target", whole divided by the speed "missile-target" (formula 113)
Posted By: ePap

Re: Bug reports - 05/20/14 08:57 AM

One thought .

Is it appropriate to use the terminology " bug report " when we have a simulation program which emulates a real system ?

In my opinion Hpasp is providing his best and he tries to include so much reality to OSA AK Samsim and so I say that all we request are possible upgrades and not "bugs".

So thumbsup to Hpasp and for his patience also ...
Posted By: piston79

Re: Bug reports - 05/20/14 05:15 PM

I think the half lead will keep the missile on the bisector of the target-SAM-point of impact angle (counting the limits due to main lobe size of SNR/RPK, as full lead will keep the missile of SAM-PoI line....)
Posted By: ePap

Re: Bug reports - 05/24/14 08:34 AM

A P-19/CASTA screen in "c" keyboard ,in Greece AEGEAN/NAMFI selection, maybe... rolleyes
Posted By: piston79

Re: Bug reports - 05/29/14 04:41 PM

Originally Posted By: piston79
I think the half lead will keep the missile on the bisector of the target-SAM-point of impact angle (counting the limits due to main lobe size of SNR/RPK, as full lead will keep the missile of SAM-PoI line....)


As a half-lead must keep the missile on bisector line of target-SNR-point of impact angle, when this angle became less than 8 degrees, the missile should leave the 4 degree limit mark and starts follow target-SNR-point of impact angle / 2....
Posted By: Hpasp

Re: Bug reports - 05/29/14 04:45 PM

Originally Posted By: piston79
Originally Posted By: piston79
I think the half lead will keep the missile on the bisector of the target-SAM-point of impact angle (counting the limits due to main lobe size of SNR/RPK, as full lead will keep the missile of SAM-PoI line....)


As a half-lead must keep the missile on bisector line of target-SNR-point of impact angle, when this angle became less than 8 degrees, the missile should leave the 4 degree limit mark and starts follow target-SNR-point of impact angle / 2....


I think that SAMSIM is coded like this, just not sure, what you mean on...
- bisector line
- when this angle became less than 8 degrees (why 8?)
- the 4 degree limit mark (why 4?)
... please describe these in drawing, that I could understood it more clearly.
Posted By: ePap

Re: Bug reports - 05/29/14 05:49 PM

Proximity fuse operation in OSA AK.

It is observed that easy targets present few meter miss distance followed by kill.
Harder targets ( maneuvering) present bigger numbers let's say 10-20 m miss distance followed by hit or kill.

The idle distance (well boresighed axis of missile towards the target) to detonate warhead is 8-12 m.
The radiation pattern of proximity fuse is 60 deg cone.

After the above it should be expected :
- easy targets to be closer to idle distance of operation and harder targets from 2-20 m with no kill/hit/kill results.
-2 or 3 or 4 m miss distance in my opinion is not necessarily a kill !Most probably is a hit,in best case .



Posted By: piston79

Re: Bug reports - 05/29/14 06:17 PM

Originally Posted By: Hpasp


I think that SAMSIM is coded like this, just not sure, what you mean on...
- bisector line
- when this angle became less than 8 degrees (why 8?)
- the 4 degree limit mark (why 4?)
... please describe these in drawing, that I could understood it more clearly.


OK. I'll do a last try (I am not good in drawings I used those from Vadifon)

This is full lead method (middle). Missile goes straight to the point of impact:




Bottom of picture - a half lead. So if we got HALF instead of FULL lead, the missile must fly with the half lead instead of full one (measuring it like an angles).

From the other side, due to transmitor/receiver limitation (and overload capability of the missile IMHO), the maximum lead angle for the missile is 4 degrees.

So, let's imagine that after targeting an object, the system will calculate that point of impact will be at, say, 10 degrees off our bore-sight (SNR-Target line). So if the system worked with a FULL lead method, the missile would go straight at the point of impact ( SNR-Point of Impact line - no target maneuvers, no height/speed change). So, the angle between those 2 lines is 10 degrees.

In HALF lead mode, the missile gonna follow the HALF of the FULL lead angle (the bisector of the angle) which divided the FULL lead angle on two (on HALF), which in our case is 5 degrees (10/2).

But we got the limitation of 4 degrees lead, so initially, the missile will go with 4 degrees, and it will keep this lead UNTIL the later moment+1 when our boresight line (SNR-Target line) during it's rotation in the side of the initial SNR-Point of Impact line, decreases the initial FULL lead angle from 10 degrees to 8 degrees... At this moment the bisector (needed HALF lead angle would be equal to the max. limit, allowed by SA-2 engineers and with further decreasing of this angle, the required lead in HALF LEAD mode will be less than max. lead limitation, i.e. the missile should leave the 4 degrees line a bit earlier than in this pictures:

http://simhq.com/forum/ubbthreads.php/topics/3954597/Re:_Bug_reports#Post3954597

Posted By: piston79

Re: Bug reports - 05/29/14 06:23 PM

Originally Posted By: ePap


After the above it should be expected :
- easy targets to be closer to idle distance of operation and harder targets from 2-20 m with no kill/hit/kill results.
-2 or 3 or 4 m miss distance in my opinion is not necessarily a kill !Most probably is a hit,in best case .



Some say SA-8, some say SA-7...

Posted By: ePap

Re: Bug reports - 05/29/14 06:41 PM

Originally Posted By: piston79
Originally Posted By: ePap


After the above it should be expected :
- easy targets to be closer to idle distance of operation and harder targets from 2-20 m with no kill/hit/kill results.
-2 or 3 or 4 m miss distance in my opinion is not necessarily a kill !Most probably is a hit,in best case .



Some say SA-8, some say SA-7...



I say,lucky very lucky pilot ...
SA-8 ,definitely .Fits to what I wrote in my previous message...
Posted By: Hpasp

Re: Bug reports - 05/29/14 08:01 PM

Originally Posted By: piston79
Originally Posted By: Hpasp


I think that SAMSIM is coded like this, just not sure, what you mean on...
- bisector line
- when this angle became less than 8 degrees (why 8?)
- the 4 degree limit mark (why 4?)
... please describe these in drawing, that I could understood it more clearly.


OK. I'll do a last try (I am not good in drawings I used those from Vadifon)

This is full lead method (middle). Missile goes straight to the point of impact:



Bottom of picture - a half lead. So if we got HALF instead of FULL lead, the missile must fly with the half lead instead of full one (measuring it like an angles).

From the other side, due to transmitor/receiver limitation (and overload capability of the missile IMHO), the maximum lead angle for the missile is 4 degrees.

So, let's imagine that after targeting an object, the system will calculate that point of impact will be at, say, 10 degrees off our bore-sight (SNR-Target line). So if the system worked with a FULL lead method, the missile would go straight at the point of impact ( SNR-Point of Impact line - no target maneuvers, no height/speed change). So, the angle between those 2 lines is 10 degrees.

In HALF lead mode, the missile gonna follow the HALF of the FULL lead angle (the bisector of the angle) which divided the FULL lead angle on two (on HALF), which in our case is 5 degrees (10/2).


Bisector of angle is true only before missile launch. As the missile is flying towards the target, this half-lead point is moving towards the target. (Its not static!)
If you calculate this movement, you will got the path depicted by the sim.
Posted By: piston79

Re: Bug reports - 05/30/14 07:12 PM

Originally Posted By: Hpasp


Bisector of angle is true only before missile launch. As the missile is flying towards the target, this half-lead point is moving towards the target. (Its not static!)
If you calculate this movement, you will got the path depicted by the sim.


I don't get it - the half-lead point is the point of impact or what?
It must be the opposite - target and missile are going toward the final point of impact...

See here (middle and bottom diagrams):




In half-lead Method Po (missile o - "Racketa o") and Co (target o - "tzel o"). At moment 0 missile goes with angle (gamma? - cannot see well)/2, and it points at point of impact 0 ("vstrecha 0"). But as this is not the true point (because of the limitation in lead), and at next moment (say moment 2) it goes to the new point of impact, which is closer to the real (final) one, etc.... (Note moment 4, when it is shown what would happen with trajectory of the missile if target do a 180 degrees turn....)
Posted By: max2012

Re: Bug reports - 05/30/14 08:19 PM


Hi everyone!

Question is version 928.2 I noticed in training in Greece shooting AH-64 Apache .

Fixed bug 10 meters high, 25 meters now , very happy!

Why no target on screen, I do not even know on the TV screen also does not have a purpose and I do not even know where to look on the radar also is not only reflected from the Earth.

Next thing I noticed strange reflections from the ground changes as it may be that appears and disappears question how this could be.

It is not clear how this could be, if you look closely on the radar screen , I noticed it , maybe it is a feature not even know.
Posted By: ePap

Re: Bug reports - 05/31/14 08:32 AM

Originally Posted By: ePap
Originally Posted By: max2012

Hi everyone!

Question is version 928.2 I noticed in training in Greece shooting AH-64 Apache .

Fixed bug 10 meters high, 25 meters now , very happy!

Why no target on screen, I do not even know on the TV screen also does not have a purpose and I do not even know where to look on the radar also is not only reflected from the Earth.

Next thing I noticed strange reflections from the ground changes as it may be that appears and disappears question how this could be.

It is not clear how this could be, if you look closely on the radar screen , I noticed it , maybe it is a feature not even know.


Which site(position) you choose?
How far from OSA AK you put your waypoints of AH-64 ?
With out these you cannot say if the target is visible in the PPI (screen).

Also other factors could produce clutters in screen.Could be random generation of clouds...Adjust your frequency for better video ... smile2

PS: how you can shoot in training scenario ?
Posted By: max2012

Re: Bug reports - 05/31/14 09:25 AM


Over the sea can not see anything like this could be on the TV screen.

At the bottom I choose the route over the Sea.

On the TV screen can be seen that all the dark fragment and target present.

On the radar screen, too, there's nothing but the reflection of the Earth.

How to adjust the frequency of the TV screen?, The documentation on this is not the word.
Posted By: ePap

Re: Bug reports - 05/31/14 09:41 AM

Originally Posted By: max2012

Over the sea can not see anything like this could be on the TV screen.

At the bottom I choose the route over the Sea.

On the TV screen can be seen that all the dark fragment and target present.

On the radar screen, too, there's nothing but the reflection of the Earth.

How to adjust the frequency of the TV screen?, The documentation on this is not the word.


Beware of the altitude of your OSA site .
If it's high (let's say ~ 250 m) and you put your waypoints or your plane is close to OSA (let's say 10 km), you will never see on radar screen PPI the target because the the radiation lobe pattern of TAR cannot see it (0-4 deg +/- 1 deg).

For me the OSA AK ,in that specific area works fine.

PS:I said the TAR frequency has to be adjusted.This is not implemented yet.Hope Hpasp to include it in next patches .... smile2
Posted By: piston79

Re: Bug reports - 05/31/14 10:16 AM

MAX2012, please, in future, ALWAYS do a PRINTSCREEN and/or VIDEO and include it in the message!

Thanks!
Posted By: max2012

Re: Bug reports - 05/31/14 11:21 AM


Well, I agree!
Posted By: Alien_MasterMynd

Re: Bug reports - 09/09/14 02:03 PM

So I suppose the AS-3 is also lost.

There is one thing to think of - the target is flying and even if it does not manoeuvre and flies directly to the RPC (P=0), then it quite quickly slips out of the beam (1,4 or 0,7 degrees wide) when there is no AS mode.

I would like to test it with a target with P=0 flying at low speed (simulation in Hungary) to see how long it takes to lighten the PROLONG light (and for KRO signal to appear).

In your test, what was target parameters? Was there any noticeable delay between AS-RPC switching off and PROLONG light?


PS: Android port of SAMSIM is something I dream of yep Nowadays the resolution of display is not a problem, but we have a let's say personal problem. Simply said who will do it....
And imagine clicking the switches with your finger using the touch screen. A strong motivoation for a new notebook computer with a touch screen thumbsup
Posted By: Alien_MasterMynd

Re: Bug reports - 09/09/14 02:12 PM

Apparently I wll not test it in Hungary, since I will be unable to launch the missile sigh

So I will try it in Ashuluk with an LA-17 flying straight on.
Posted By: piston79

Re: Bug reports - 09/09/14 02:40 PM

I Used Tallin scenario....
Posted By: Alien_MasterMynd

Re: Bug reports - 09/09/14 02:48 PM

So now I understand why there is immediate PROLONG after AS off in your case - the Mach 3 SR-71 jumps out of the static beam from the RPC virtualy immediately. Even if it is still pointing in the right direction - you have to think in 3D - beam directs from the ground level up under some angle (which is constantly increasing as the target is coming close to the RPC). By the way, look what elevation marker does when you track such a high speed closing target.
Posted By: piston79

Re: Bug reports - 09/09/14 03:14 PM

There is always PROLONG, no matter of target smile
PROLONG is used when target goes thru rejection filter speed zone (i.e. <50 m/s radial speed).

Also suitable scenario is against both F-14's in Libya....
Posted By: Alien_MasterMynd

Re: Bug reports - 09/09/14 04:54 PM

Now you led me to the interesting idea - PROLONG is activated whenever the target is lost (either velocity filter, or blocked line of sight or something) and it should mean that CVK is moving the RPC according to the computed target's track because the RPC can't see the target.

So I do not understand the PROLONG when AS-RPC is manually switched off and thus CVK can not control position of RPC. In this situation in my opinion the PROLONG should not be activated....
Posted By: Alien_MasterMynd

Re: Bug reports - 09/10/14 11:03 AM

I just tried the following - locked target in velocity (AS-3), measured distance and enabled AS-RPC (usual procedure). No missile launched (button lights indicate readiness for launch). I disabled AS-RPC, AS-3 is in enabled state so I suppose RPC is tracking the target (with exception of range computation from RPC position). PROLONG was immediately activated. But missile can be launched and succesfully intercept the target as expected since the target was continuously illuminated by RPC.

What is the correct meaning of PROLONG? It looks like it indicate lack of any tracking information. So it seems that lack of range information from CVK is sufficient for PROLONG to activate even the target is still tracked by RPC and can be fired upon.

Without range measurement and AS-RPC activation missile can not be launched (DO STARTA mode) as expected, because the system does not know which flight program to choose.
Posted By: piston79

Re: Bug reports - 09/12/14 04:38 AM

Originally Posted By: Alien_MasterMynd
I just tried the following - locked target in velocity (AS-3), measured distance and enabled AS-RPC (usual procedure). No missile launched (button lights indicate readiness for launch). I disabled AS-RPC, AS-3 is in enabled state so..........


I think all after AS-RPC is off AS-3 is off also.....
Posted By: Alien_MasterMynd

Re: Bug reports - 09/13/14 05:57 AM

I tried it in SAMSIM and AS-3 stayed on and after AS-RPC off I was able to launch a missile and succesfully intercepted the target.... But question to Hpasp is if this is a correct behavior. It seems so, because CVK already has some range info, but I do not know if CVK really permits a launch when AS-RPC is disabled (edit - I mean a real CVK in a real Vega).
Posted By: Hpasp

Re: Bug reports - 09/13/14 09:53 AM

AS RPC is required before launch, as the CVK should select a flight program of the SRP from the available 97 (flight program number 104..201).

On the other hand you can launch with AS-2 also, without measured range or speed information.
Posted By: piston79

Re: Bug reports - 09/13/14 04:48 PM

Just refreshing memories:

Quote:
Easiest answer is that Plamya use different program codes, for the different tasks.
(manual page 17)
Plamja-KV CVM (digital computer)
The digital computer has a 16bit processor, running at 64kHz frequency.
It has 256 bytes of RAM, and 4,096 bytes of ROM.
It has five built-in programs:
1. Idle
In this mode, the Plamja-KV is calculating the firing solution using the instantaneously available data from the RPC.
2. IADS target acquisition
In this mode, the Plamja-KV is interpolating the target's predicted position, between the 10Hz updates received from the IADS information.
3. Target tracking
In this mode, the Plamja-KV is continuously calculating the target's predicted path, and figuring the firing solution based on this information.
4. Tracking Jamming Target
In this mode, the Plamja-KV is calculating the firing solution using a manually preset target range. This mode is called AS-2.
5. Self Test




I think, that CVK always DO a firing solution, no matter how the data is inputed on it (manually, by "local sensors" (those MD buttons and red lights) or by IADS.

The real behaviour of the system is a mystical process for me, understanding the behaviour is a key for a bug findings or some mistery solving (04.10.2001 - Tu-154M)...
Posted By: Alien_MasterMynd

Re: Bug reports - 09/13/14 05:09 PM

Yes, the poor Tu-154, I do not understand if the measured range was real range of VR-3 how the missile could get so far. Maybe error of a tracking officer who mistakenly entered wrong range?
Posted By: Alien_MasterMynd

Re: Bug reports - 09/13/14 05:13 PM

Yes, the CVK for a launch must have some range information, but in SAMSIM when I completely track target, then I switch AS-RPC off, PROLONG is thus active and apparently CVK is not computing track range data. But I am able to launch and successfully kill the target. So in this case CVK seemingly has the last range information and uses it for the missile.
Because when I track the target only in velocity, I am unable to launch as there is no any (even not some last estimate) range information.
Posted By: Alien_MasterMynd

Re: Bug reports - 09/13/14 05:35 PM

Originally Posted By: Hpasp
AS RPC is required before launch, as the CVK should select a flight program of the SRP from the available 97 (flight program number 104..201).


This is a completely new information for me (97 flight programs), please clarify a bit and please go very deep in explanation thumbsup
Posted By: Alien_MasterMynd

Re: Bug reports - 09/13/14 05:36 PM

Maybe we could move the last posts into a Vega theme.
Posted By: Hpasp

Re: Bug reports - 09/13/14 05:48 PM

Do not mix Plamya-KV (CVM) programs (5) with the available 97 flight programs of the SRP.
Before launch, CVM in program 2 (IADS - AS4), 3 (P14 - AS4), or 4 (Jamming - AS2) should supply onboard SRP with the selected flight program 104..201.
Posted By: Hpasp

Re: Bug reports - 09/13/14 05:54 PM

I give up moving posts...
sigh
Posted By: piston79

Re: Bug reports - 09/23/14 06:26 PM

1S12 screen - OAF scenario: the Ashuluk is drawn on the glass. The drawing is appearing only when the power is on...
Posted By: piston79

Re: Bug reports - 09/27/14 10:55 AM

SA-5

According to "Manual of battle work of S-200B", page 146,- "RABOTA PO V" knob must be in "AVTOPEREZAHVAT VIKL" mode by default....


Link



Posted By: Hpasp

Re: Bug reports - 09/27/14 11:14 AM

Originally Posted By: piston79
SA-5

According to "Manual of battle work of S-200B", page 146,- "RABOTA PO V" knob must be in "AVTOPEREZAHVAT VIKL" mode by default....


Link


That switch behavior is not simulated.
Posted By: piston79

Re: Bug reports - 09/27/14 11:17 AM

Originally Posted By: Hpasp


That switch behavior is not simulated.


So, does it mean that it must stay wrong???
As it is like now, we had AS on epsilon/beta only...

Posted By: Hpasp

Re: Bug reports - 09/27/14 11:17 AM

Originally Posted By: piston79
1S12 screen - OAF scenario: the Ashuluk is drawn on the glass. The drawing is appearing only when the power is on...


On what date/position?
Posted By: piston79

Re: Bug reports - 09/27/14 11:20 AM

Originally Posted By: Hpasp
Originally Posted By: piston79
1S12 screen - OAF scenario: the Ashuluk is drawn on the glass. The drawing is appearing only when the power is on...


On what date/position?


2-th of may.... But I think it is for all of dates...
Posted By: piston79

Re: Bug reports - 09/27/14 11:45 AM

SA-5:

On Tallin scenario, managed to shoot at receding SR-71 and got it down... According to manuals, we could engage receding targets with 300 m/s....
Posted By: Hpasp

Re: Bug reports - 09/27/14 12:18 PM

Originally Posted By: piston79
SA-5:

On Tallin scenario, managed to shoot at receding SR-71 and got it down... According to manuals, we could engage receding targets with 300 m/s....


Hmmm, a lucky shot.
rolleyes
Posted By: piston79

Re: Bug reports - 09/27/14 01:02 PM

Originally Posted By: Hpasp


Hmmm, a lucky shot.
rolleyes


As target and missile speeds are almost equal (1000 m/s), thus most of the time the return signal frequency would be with ~ 0 doppler shift, i.e. targt cannot be tracked successful
Posted By: max2012

Re: Bug reports - 09/27/14 01:08 PM


And what if you can not track it.

 Target speed of almost 1000 m / s this is true, it is strange that in Operation Tallinn grab this goal is very difficult, I tried a lot of times, it was possible only very rarely.

 Strange if another shoot at moving away goal, then the maximum speed of 300 m / s, why do Volkhov then 420 m / s, Volkhov system older than Vega rocket and she also weaker.

 At the C-200 'Vega' Hypersonic missile, the idea should not be a problem, it just easily catch up with the target.

 
Posted By: piston79

Re: Bug reports - 09/27/14 01:26 PM

Originally Posted By: max2012

 Strange if another shoot at moving away goal, then the maximum speed of 300 m / s, why do Volkhov then 420 m / s, Volkhov system older than Vega rocket and she also weaker.

 At the C-200 'Vega' Hypersonic missile, the idea should not be a problem, it just easily catch up with the target.

 


No idea... Probably due to SARH method...
Posted By: scrim

Re: Bug reports - 09/27/14 02:01 PM

Originally Posted By: Hpasp
Hmmm, a lucky shot.
rolleyes


You think that's a lucky shot? Then you obviously ain't seen this AAR yet:

Click to reveal..
14:40 19th of December, 1972.
SR-71 bomb damage assessment flight number two.

SA-75M Dvina


+++++++++++++++++
00:00:43, SNR ON AIR


00:03:27, V-750VMVK 11DMVK Missile launched on Channel-1
Target distance: 58km
Target azimuth: 264°
Target elevation: 24°
Target altitude: 24,2km
SNR mode: 110km
Missile guidance method: UPR (Half Lead)


00:03:33, V-750VMVK 11DMVK Missile launched on Channel-2
Target distance: 58km
Target azimuth: 267°
Target elevation: 26°
Target altitude: 26,4km
SNR mode: 110km
Missile guidance method: T/T (Three Point)


00:03:40, V-750VMVK 11DMVK Missile launched on Channel-3
Target distance: 58km
Target azimuth: 271°
Target elevation: 30°
Target altitude: 29,6km
SNR mode: 110km
Missile guidance method: T/T (Three Point)


00:03:52, V-750VMVK 11DMVK Missile launched on Channel-1
Target distance: 58km
Target azimuth: 282°
Target elevation: 36°
Target altitude: 35,4km
SNR mode: 110km
Missile guidance method: T/T (Three Point)


00:04:36, V-750VMVK 11DMVK Missile launched on Channel-2
Target distance: 58km
Target azimuth: 38°
Target elevation: 57°
Target altitude: 49,7km
SNR mode: 110km
Missile guidance method: T/T (Three Point)


00:04:46, V-750VMVK 11DMVK Missile launched on Channel-3
Target distance: 58km
Target azimuth: 62°
Target elevation: 49°
Target altitude: 44,7km
SNR mode: 110km
Missile guidance method: T/T (Three Point)


00:04:49, Missile exploded on Channel-1
SR-71 Habu killed by SAM. (miss distance: 88m)

00:06:32, V-750VMVK 11DMVK Missile launched on Channel-1
Target distance: 42km
Target azimuth: 89°
Target elevation: 20°
Target altitude: 14,6km
SNR mode: 110km
Missile guidance method: K (Half Lead Elevated By Constans)


00:09:07, SNR OFF THE AIR
-----------------


Total, SNR On Air Time: 8min 21sec


TL;DR Shot down a Blackbird with an SA-2F biggrin. To be fair though, something must've glitched because the jammer wasn't on, or at least not having any effect on me. I'm guessing the same goes for the various other anti SAM systems that have been mentioned in this sub forum if they're modeled as well.
Posted By: max2012

Re: Bug reports - 09/27/14 03:35 PM


00:04:36, V-750VMVK 11DMVK Missile launched on Channel-2
Target distance: 58km
Target azimuth: 38°
Target elevation: 57°
Target altitude: 49,7km
SNR mode: 110km
Missile guidance method: T/T (Three Point)

This is a mistake, this can not be the SR-71 did not fly so high!
Posted By: scrim

Re: Bug reports - 09/27/14 04:07 PM

Yeah, weird now that I look at it. I didn't pay any attention to that before, but I'm guessing that since it didn't even jam me until a few seconds before impact, altitude was a tad or two glitched as well.
Posted By: piston79

Re: Bug reports - 09/27/14 04:24 PM

Originally Posted By: scrim
Yeah, weird now that I look at it. I didn't pay any attention to that before, but I'm guessing that since it didn't even jam me until a few seconds before impact, altitude was a tad or two glitched as well.


Could you do it again, and make a video + share again AAR/3DAAR?
Posted By: scrim

Re: Bug reports - 09/27/14 05:28 PM

Fairly certain it was a one off, but I'll try again. Not playing SAM sim so much any longer though, since I've got a 27" screen which means I have to muck about with the resolution every time I play it. If it gives me the same altitudes, I'll record and such.
Posted By: scrim

Re: Bug reports - 09/27/14 05:37 PM

Did it again, and I'm starting to guess it's restricted to the AAR. The EWR screen consistently called out his altitude as being 24.000m. I'll do a recording if Hpasp feels there's a reason to suspect something is broken.
Posted By: scrim

Re: Bug reports - 09/27/14 05:43 PM

Actually, I found out the reason, at least I'm pretty sure. Though the jammer was never on at first, he turned it on when the missiles were close. Due to that the range gate lost track of him, and stayed where it last saw him. So when he came closer the AAR correctly registered that I'd been firing at a target that was far above 24.000m altitude according to the settings I'd inadvertently been feeding the Fan Song.

So no problem, just a user bug duh
Posted By: Hpasp

Re: Bug reports - 09/28/14 06:54 AM

Originally Posted By: piston79
SA-5

According to "Manual of battle work of S-200B", page 146,- "RABOTA PO V" knob must be in "AVTOPEREZAHVAT VIKL" mode by default....


Link





In all switches, red dot shows the "forced" default setting on the Vega panel.
That switch albeit mentioned in the manual, and that setting is a reasonable one, before switching POMEHA, you need to anyway select the correct value based on the detected jamming type, thus there is no "forced default" red dot on the panel.
As in SAMSIM we have only noise jamming, the AS VIKL is a good selection.
Anyway, that switch has no effect in SAMSIM.
Posted By: Hpasp

Re: Bug reports - 09/28/14 12:07 PM

Originally Posted By: piston79
Originally Posted By: Hpasp
Originally Posted By: piston79
1S12 screen - OAF scenario: the Ashuluk is drawn on the glass. The drawing is appearing only when the power is on...


On what date/position?


2-th of may.... But I think it is for all of dates...


Found it, will be corrected.
Posted By: piston79

Re: Bug reports - 09/28/14 12:48 PM

Originally Posted By: Hpasp

As in SAMSIM we have only noise jamming, the AS VIKL is a good selection.
Anyway, that switch has no effect in SAMSIM.


1. One day we could have other type of jammings.
2. It is not "realistic to the switch" in that way wink
Posted By: piston79

Re: Bug reports - 10/14/14 07:10 PM

SA-2E bug (thanks to MAx2012):

1. When in "<5km" mode turn on "Podsvet" or "Narrow beam", "<5km" mode is turned off...

2. When switch on "<5km" the antenna pop-up by 3 degrees, but in KARAT target is still in cross hair....?
Posted By: Hpasp

Re: Bug reports - 10/15/14 09:38 AM

Originally Posted By: piston79
SA-2E bug (thanks to MAx2012):

1. When in "<5km" mode turn on "Podsvet" or "Narrow beam", "<5km" mode is turned off...

2. When switch on "<5km" the antenna pop-up by 3 degrees, but in KARAT target is still in cross hair....?


1. It will be more complex, when Karat will be introduced...
(it also affects H<5 behaviour)

2. ???
Posted By: piston79

Re: Bug reports - 10/15/14 10:51 AM

Originally Posted By: Hpasp


1. It will be more complex, when Karat will be introduced...
(it also affects H<5 behaviour)

2. ???


1. It is not possible tho switch off "<5km" mode with other switch....

2. As antenna and KARAT are aligned, what is happening with antenna when "<5km" is switched? What will happen with the view in KARAT? screwy
Posted By: Hpasp

Re: Bug reports - 10/26/14 05:24 PM

Answered in the Volhov topic.
Posted By: piston79

Re: Bug reports - 11/22/14 11:10 AM

0.929 - bug S-200VE in jamming environment...

After launch, when target start using noise jamming, we observe KRO signals.... After reacquiring target on AS-2 and AS-RPC, the first missile reacquired the target too.... it is observed in Giant Reach and Vladivostok scenario, but sure it would be the same in others too...

P.S. Is this because on "Rabota on V" it is AS VYKL?
Posted By: KostasAK

Re: Bug reports - 01/07/15 11:52 PM

I haven't played the SAM sim since some weeks and today when I double clicked the desktop icon a message appeared:

"Your current resolution is 1536x864, program requires screen resolution 1280x1024 or higher".

My screen resolution is not 1536x864 but 1920x1080. Why the sim can't recognize the real resolution? I haven't this bug before.

I use the 929 version. Any thoughts?
Posted By: Hpasp

Re: Bug reports - 01/08/15 01:08 PM

You need to set Windows screen magnification back to 100%.
Posted By: piston79

Re: Bug reports - 03/18/15 05:35 PM

Originally Posted By: piston79
0.929 - bug S-200VE in jamming environment...

After launch, when target start using noise jamming, we observe KRO signals.... After reacquiring target on AS-2 and AS-RPC, the first missile reacquired the target too.... it is observed in Giant Reach and Vladivostok scenario, but sure it would be the same in others too...

P.S. Is this because on "Rabota on V" it is AS VYKL?


Any comments about this report?
Posted By: Hpasp

Re: Bug reports - 03/20/15 08:51 AM

Originally Posted By: piston79
Originally Posted By: piston79
0.929 - bug S-200VE in jamming environment...

After launch, when target start using noise jamming, we observe KRO signals.... After reacquiring target on AS-2 and AS-RPC, the first missile reacquired the target too.... it is observed in Giant Reach and Vladivostok scenario, but sure it would be the same in others too...

P.S. Is this because on "Rabota on V" it is AS VYKL?


Any comments about this report?


In theory the big new advanced feature of the S-200V Vega system is the jamming target reacquiring capability from the V-860PV missiles onward. (manual page 34.)

There were a bug in the code considering this reacquiring capability as 360 azimuth earlier, but it was fixed earlier.
Posted By: piston79

Re: Bug reports - 03/22/15 09:26 AM

Originally Posted By: Hpasp
Originally Posted By: piston79
Originally Posted By: piston79
0.929 - bug S-200VE in jamming environment...

After launch, when target start using noise jamming, we observe KRO signals.... After reacquiring target on AS-2 and AS-RPC, the first missile reacquired the target too.... it is observed in Giant Reach and Vladivostok scenario, but sure it would be the same in others too...

P.S. Is this because on "Rabota on V" it is AS VYKL?


Any comments about this report?


In theory the big new advanced feature of the S-200V Vega system is the jamming target reacquiring capability from the V-860PV missiles onward. (manual page 34.)

There were a bug in the code considering this reacquiring capability as 360 azimuth earlier, but it was fixed earlier.



nope

OK, once more...

Target is SR-71 in Giant Reach. After first missile is in the air, the target starts jamming. Thus the missile's GSN lost velocity lock on the target and KRO signals appeared. RPN should lost tracking on velocity as cannot discriminate the target in the noise enviroment.

Here must apply some settings to prepare the second missile to work in jamming environment. Here we must unlock tracking in velocity for RPN (which is achieved by POMEHA switch IMHO), also select on selector switch tracking in velocity OFF (for GSN). So after that we could fire a missile in HOJ mode.

BUT when the RPN locked target again in AS-2 mode, the first missile (which is in the air already, and which started in non-jamming enviroment with velocity tracking ON), suddenly reacquires the target all by itself... screwy(which IMO is impossible). Also CU feature could be affected in initiating such behaviour.

Please AlienMastermind to help in additional testing as my computer is barely working recently...
Posted By: Alien_MasterMynd

Re: Bug reports - 03/22/15 05:58 PM

piston: I will test it during this week.

I think this is not possible in reality too, because there is no uplink channel to tell the already launched missile to switch to home on jam mode.
Posted By: Alien_MasterMynd

Re: Bug reports - 03/23/15 10:14 AM

It is really strange, at first I thought it is a purely KRO bug.

But finally I have conducted one test - acquired SR-71 (AS-3), launched a missile, when the target started jamming I switched on POMECHA switch and re-acquired the target (AS-4) and waited.
The only launched missile (with POISK V VKL and AS-3) in the moment of reacquistion of the target switched off KRO transmitter and GSN reacquired the target! After some time the target was destroyed with this missile. No other missile was launched.

So this behavior is strongly unprobable. How the missile could know that GSN of missile in flight has to switch to home on jam mode?

-----
EDIT
After SR-71 started jamming I have not touched anything except POMECHA switch, AS-4 switch (fi indicator is lit) and AS-RPC.
NO PROLONG, NO GSN mode change or anything else. Everything remained in the same positions as in the moment of launch.
Posted By: Mdore

Re: Bug reports - 03/24/15 02:16 PM

I assume you know and just didn't choose to simulate it, but the fuse settings knob for the SA-2 doesn't really do anything different with most settings.

The proximity fuse will never detonate from ground reflections, no matter how low your target is, even if you have the fuse set to normal. And the proxmity fuse will still trigger against targets beyond 100m, even if the fuse is set to low sensitivity mode.
Posted By: piston79

Re: Bug reports - 03/24/15 05:16 PM

Originally Posted By: Mdore
I assume you know and just didn't choose to simulate it, but the fuse settings knob for the SA-2 doesn't really do anything different with most settings.

The proximity fuse will never detonate from ground reflections, no matter how low your target is, even if you have the fuse set to normal. And the proxmity fuse will still trigger against targets beyond 100m, even if the fuse is set to low sensitivity mode.


Hi, Mdore!

Could you be more specific about the mission, type of missiles used etc...
A good old AAR is also welcome!.. yep

P.S. Gotta have a PM from me.... wink
Posted By: Alien_MasterMynd

Re: Bug reports - 03/25/15 08:10 AM

The second test - I have not reacquired the target in POMECHA mode and the launched missile was lost - once the target slips out of the RPC beam, the missile is lost.

I will now try to launch a missile in home on jam mode and switch off the RPC to see if it will hit the target.
Posted By: Alien_MasterMynd

Re: Bug reports - 03/25/15 09:02 AM

It is strange, missile launched in home on jam mode, transmitter switched off, also CU off and there were TWO KRO signals appeared.
Either there is a bug or the missile must keep receiving RPC signal even when in home in jam mode.
Posted By: Alien_MasterMynd

Re: Bug reports - 03/25/15 09:21 AM

Another bug, which accounts probably to lack of variable resetting when SAMSIM is not restarted after a mission (some knobs and switches remember their settings when replayed the same SAM system).

I have finished testing in Giant reach scenario and then selected Osa in Asuluk, added missiles and targets and during start only the ona panel with SOC indicator was displayed along with an error message (Invalid procedure call) and SAMSIM quits.
Then I run SAMSIM again, selected missiles and targets (the same way as above) and everything was OK.
Posted By: piston79

Re: Bug reports - 03/25/15 06:16 PM

Originally Posted By: Alien_MasterMynd
It is strange, missile launched in home on jam mode, transmitter switched off, also CU off and there were TWO KRO signals appeared.
Either there is a bug or the missile must keep receiving RPC signal even when in home in jam mode.


I think it is necessary to illuminate the target even when the missile is in HOJ mode (at least in case the jamming is canceled)....

Another bug - on USTKA KARAT is not working...
Posted By: Alien_MasterMynd

Re: Bug reports - 03/26/15 07:29 AM

Yes, probably the missile still needs to receive reference signal directly from RPC using the tail antennas, but I am not sure.
Posted By: piston79

Re: Bug reports - 03/26/15 05:21 PM

Originally Posted By: Alien_MasterMynd
Yes, probably the missile still needs to receive reference signal directly from RPC using the tail antennas, but I am not sure.



Tail antenna? screwy
Posted By: Alien_MasterMynd

Re: Bug reports - 03/27/15 02:17 PM

Yes, antennas on the tail wings which is needed to receive base frequency RPC signal for GSN to be able to correctly compute doppler frequency and so on.
Posted By: piston79

Re: Bug reports - 03/27/15 06:21 PM

Originally Posted By: Alien_MasterMynd
Yes, antennas on the tail wings which is needed to receive base frequency RPC signal for GSN to be able to correctly compute doppler frequency and so on.


Are you sure??? Could you show me where it is?
Posted By: Hpasp

Re: Bug reports - 03/27/15 10:13 PM

Originally Posted By: Alien_MasterMynd
Another bug, which accounts probably to lack of variable resetting when SAMSIM is not restarted after a mission (some knobs and switches remember their settings when replayed the same SAM system).

I have finished testing in Giant reach scenario and then selected Osa in Asuluk, added missiles and targets and during start only the ona panel with SOC indicator was displayed along with an error message (Invalid procedure call) and SAMSIM quits.
Then I run SAMSIM again, selected missiles and targets (the same way as above) and everything was OK.


Yeah, I put extraordinary efforts on resetting situations, but it still not 100%.
Sorry I feel piggy
Posted By: Hpasp

Re: Bug reports - 03/27/15 10:19 PM

Originally Posted By: piston79
Originally Posted By: Alien_MasterMynd
It is strange, missile launched in home on jam mode, transmitter switched off, also CU off and there were TWO KRO signals appeared.
Either there is a bug or the missile must keep receiving RPC signal even when in home in jam mode.


I think it is necessary to illuminate the target even when the missile is in HOJ mode (at least in case the jamming is canceled)....

Another bug - on USTKA KARAT is not working...


Ustka Karat (target launching ship)



Can you be a bit more specific?
Posted By: piston79

Re: Bug reports - 03/28/15 05:17 AM

Originally Posted By: Hpasp


Ustka Karat (target launching ship)



Can you be a bit more specific?


Yep, sorry...

Choose P-15 as a target and work on it.... no target, no missile trails...
Posted By: farokh

Re: Bug reports - 03/28/15 08:49 AM

I finds something strange in sa8 non historical scenario....
When u play you missions in Libya
For example sa2... You take harm missile after few seconds
Its normal !! Okay

But in Libya with sa8 ...you take a harm exactly right after turning on transmitter
Without any delay !!!
Posted By: piston79

Re: Bug reports - 03/28/15 03:26 PM

Originally Posted By: farokh


But in Libya with sa8 ...you take a harm exactly right after turning on transmitter
Without any delay !!!



A good old AAR is always welcome...
Posted By: Alien_MasterMynd

Re: Bug reports - 03/28/15 10:58 PM

farokh: after WHICH transmitter on did you receive a HARM? Remember that even a SOC is a magnet for HARM (works in a cm range).
Posted By: Alien_MasterMynd

Re: Bug reports - 03/28/15 11:00 PM

piston: you can notice them on the following pictures (and also other on the net, they can be clearly seen - their shape is similar to those on top of F-15's vertical tail stabilizers):





Posted By: farokh

Re: Bug reports - 03/31/15 09:01 PM

Originally Posted By: farokh
I finds something strange in sa8 non historical scenario....
When u play you missions in Libya
For example sa2... You take harm missile after few seconds
Its normal !! Okay

But in Libya with sa8 ...you take a harm exactly right after turning on transmitter
Without any delay !!!



Originally Posted By: piston79
Originally Posted By: farokh


But in Libya with sa8 ...you take a harm exactly right after turning on transmitter
Without any delay !!!



A good old AAR is always welcome...






this is my result !

2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Benghazi.

Targets:
Jamahiriyah barracks - 6 A-6E Intruder (from the CV-66 USS America)
Benghazi AFB - 6 A-6E Intruder (from the CV-43 USS Coral Sea)

Supporting force:
8 SEAD F/A-18A Hornet (VMFA-314 Black Knights, VMFA-323 Death Rattlers from the CV-43 USS Coral Sea)
2 SEAD A-7E Corsair-II (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
6 CAP F/A-18A Hornet (VFA-131 Wildcats, VFA-132 Privateers from the CV-43 USS Coral Sea)
3 ECM EA-6B Prowler (VAQ-135 Rooks, VMAQ-2 Playboys from both carriers)
1 SIGINT EA-3B Skywarrior (VQ-2 Sandeman from the CV-43 USS Coral Sea)
2 AWACS E-2C Hawkeye (VAW-127 Seabats from the CV-43 USS Coral Sea)

9K33M2 OSA-AK


+++++++++++++++++
00:00:02, SNR ON AIR


00:03:54, F/A-18A Hornet No.1, VMFA-314 Black Knights launched AGM-88 HARM missile No. 1


Total, SNR On Air Time: 3min 52sec

dizzy
Posted By: Alien_MasterMynd

Re: Bug reports - 03/31/15 11:15 PM

I can see the HARM was launched 3:52 after SNR on confused
Posted By: piston79

Re: Bug reports - 04/01/15 05:08 AM

Originally Posted By: farokh
Originally Posted By: farokh
I finds something strange in sa8 non historical scenario....
When u play you missions in Libya
For example sa2... You take harm missile after few seconds
Its normal !! Okay

But in Libya with sa8 ...you take a harm exactly right after turning on transmitter
Without any delay !!!



Originally Posted By: piston79
Originally Posted By: farokh


But in Libya with sa8 ...you take a harm exactly right after turning on transmitter
Without any delay !!!



A good old AAR is always welcome...






this is my result !

2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Benghazi.

Targets:
Jamahiriyah barracks - 6 A-6E Intruder (from the CV-66 USS America)
Benghazi AFB - 6 A-6E Intruder (from the CV-43 USS Coral Sea)

Supporting force:
8 SEAD F/A-18A Hornet (VMFA-314 Black Knights, VMFA-323 Death Rattlers from the CV-43 USS Coral Sea)
2 SEAD A-7E Corsair-II (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
6 CAP F/A-18A Hornet (VFA-131 Wildcats, VFA-132 Privateers from the CV-43 USS Coral Sea)
3 ECM EA-6B Prowler (VAQ-135 Rooks, VMAQ-2 Playboys from both carriers)
1 SIGINT EA-3B Skywarrior (VQ-2 Sandeman from the CV-43 USS Coral Sea)
2 AWACS E-2C Hawkeye (VAW-127 Seabats from the CV-43 USS Coral Sea)

9K33M2 OSA-AK


+++++++++++++++++
00:00:02, SNR ON AIR


00:03:54, F/A-18A Hornet No.1, VMFA-314 Black Knights launched AGM-88 HARM missile No. 1


Total, SNR On Air Time: 3min 52sec


dizzy





Total, SNR On Air Time: 3min 52sec


Faroukh, you are the only one here who cannot build any basic knowledge about SAM-s... That's unbelievable.... deadhorse
Posted By: farokh

Re: Bug reports - 04/01/15 08:52 AM

Originally Posted By: piston79
Originally Posted By: farokh
Originally Posted By: farokh
I finds something strange in sa8 non historical scenario....
When u play you missions in Libya
For example sa2... You take harm missile after few seconds
Its normal !! Okay

But in Libya with sa8 ...you take a harm exactly right after turning on transmitter
Without any delay !!!



Originally Posted By: piston79
Originally Posted By: farokh


But in Libya with sa8 ...you take a harm exactly right after turning on transmitter
Without any delay !!!



A good old AAR is always welcome...






this is my result !

2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Benghazi.

Targets:
Jamahiriyah barracks - 6 A-6E Intruder (from the CV-66 USS America)
Benghazi AFB - 6 A-6E Intruder (from the CV-43 USS Coral Sea)

Supporting force:
8 SEAD F/A-18A Hornet (VMFA-314 Black Knights, VMFA-323 Death Rattlers from the CV-43 USS Coral Sea)
2 SEAD A-7E Corsair-II (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
6 CAP F/A-18A Hornet (VFA-131 Wildcats, VFA-132 Privateers from the CV-43 USS Coral Sea)
3 ECM EA-6B Prowler (VAQ-135 Rooks, VMAQ-2 Playboys from both carriers)
1 SIGINT EA-3B Skywarrior (VQ-2 Sandeman from the CV-43 USS Coral Sea)
2 AWACS E-2C Hawkeye (VAW-127 Seabats from the CV-43 USS Coral Sea)

9K33M2 OSA-AK


+++++++++++++++++
00:00:02, SNR ON AIR


00:03:54, F/A-18A Hornet No.1, VMFA-314 Black Knights launched AGM-88 HARM missile No. 1


Total, SNR On Air Time: 3min 52sec


dizzy





Total, SNR On Air Time: 3min 52sec


Faroukh, you are the only one here who cannot build any basic knowledge about SAM-s... That's unbelievable.... deadhorse




you were always in nerve nope
because you judge always soon !

Total, SNR On Air Time: 3min 52sec
in OSA
"is only SOC transmitter ! not SCC !"

problem is SCC ON OFF timing is not simulated at all in AAR

and that one 2 seconds SNR i thouth that was SCC wrongly
because after two second of SCC ON.. missile come !

they can catch you only on SCC

in libya war... no wild weasel cant hunt any OSA system by SOC with HARM !
and i test it smile

Click to reveal..
2:00am 15th of April, 1986.
Operation El-Dorado Canyon raid against Benghazi.

Targets:
Jamahiriyah barracks - 6 A-6E Intruder (from the CV-66 USS America)
Benghazi AFB - 6 A-6E Intruder (from the CV-43 USS Coral Sea)

Supporting force:
8 SEAD F/A-18A Hornet (VMFA-314 Black Knights, VMFA-323 Death Rattlers from the CV-43 USS Coral Sea)
2 SEAD A-7E Corsair-II (VA-46 Clansmen, VA-72 Blue Hawks from the CV-66 USS America)
6 CAP F/A-18A Hornet (VFA-131 Wildcats, VFA-132 Privateers from the CV-43 USS Coral Sea)
3 ECM EA-6B Prowler (VAQ-135 Rooks, VMAQ-2 Playboys from both carriers)
1 SIGINT EA-3B Skywarrior (VQ-2 Sandeman from the CV-43 USS Coral Sea)
2 AWACS E-2C Hawkeye (VAW-127 Seabats from the CV-43 USS Coral Sea)

9K33M2 OSA-AK


+++++++++++++++++
00:00:02, SNR ON AIR

00:04:15, A-6E Intruder No.1 (from the CV-66 USS America) bombed Jamahiriyah barracks.
00:04:16, A-6E Intruder No.1 (from the CV-43 USS Coral Sea) bombed Benghazi AFB.
00:05:01, A-6E Intruder No.2 (from the CV-66 USS America) bombed Jamahiriyah barracks.
00:05:02, A-6E Intruder No.2 (from the CV-43 USS Coral Sea) bombed Benghazi AFB.
00:05:47, A-6E Intruder No.3 (from the CV-66 USS America) bombed Jamahiriyah barracks.
00:05:48, A-6E Intruder No.3 (from the CV-43 USS Coral Sea) bombed Benghazi AFB.
00:06:33, A-6E Intruder No.4 (from the CV-66 USS America) bombed Jamahiriyah barracks.
00:06:34, A-6E Intruder No.4 (from the CV-43 USS Coral Sea) bombed Benghazi AFB.
00:07:19, A-6E Intruder No.5 (from the CV-66 USS America) bombed Jamahiriyah barracks.
00:07:19, A-6E Intruder No.5 (from the CV-43 USS Coral Sea) bombed Benghazi AFB.
00:08:05, A-6E Intruder No.6 (from the CV-66 USS America) bombed Jamahiriyah barracks.
00:08:05, A-6E Intruder No.6 (from the CV-43 USS Coral Sea) bombed Benghazi AFB.

Total, SNR On Air Time: 17min 38sec


in this test .. i do not turning ON SCC at all !



Posted By: farokh

Re: Bug reports - 04/17/15 09:45 AM

why my twice missile does not impaced tp target ?

Click to reveal..
Asuluk training ground.

Practice target:
Radar Reflector

9K33M2 OSA-AK


00:00, Practice target Radar Reflector launched

+++++++++++++++++
00:00:02, SNR ON AIR


00:00:41, 9M33M2 Missile launched on Channel-1
Target distance: 15km
Target azimuth: 22°
Target elevation: 14°

00:00:46, 9M33M2 Missile launched on Channel-2
Target distance: 15km
Target azimuth: 23°
Target elevation: 14°

00:00:57, Missile exploded on Channel-1
Practice target Radar Reflector killed by SAM. (miss distance: 1m)

Total, SNR On Air Time: 1min 4sec


PS: training target armed with CM jam

hpasp .. hum?
Posted By: tramker

Re: Bug reports - 06/03/15 07:53 PM

Hi, I get

Run-time error 11: Division by zero

S-75M3

- power on
- press missile launch (PUSK)
- TAKT illuminates, then crash

SAMSIM v0.929
Posted By: piston79

Re: Bug reports - 06/27/15 03:04 PM

Something's wrong with the B-1 type target at Ashuluk...


Click to reveal..
Asuluk training ground.

Practice target:
RM-217 Zvezda [program-4] simulating B-1B Lancer

S-200VE Vega-E


00:30, Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer launched

+++++++++++++++++
00:00:47, SNR ON AIR


00:02:20, Missile launched from launcher-1
Target distance: 97km
Target azimuth: 76°
Target elevation: 10°
Target angular speed: 959m/s (3.4 Mach)
Target altitude: 18.1km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 25.8dB


00:02:27, Missile launched from launcher-3
Target distance: 91km
Target azimuth: 76°
Target elevation: 11°
Target angular speed: 929m/s (3.3 Mach)
Target altitude: 18.1km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 27dB


00:02:38, Missile launched from launcher-2
Target distance: 81km
Target azimuth: 76°
Target elevation: 12°
Target angular speed: 880m/s (3.1 Mach)
Target altitude: 18.1km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target during flight
Received signal strength: 29dB


00:03:09, Missile exploded
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 20m)

00:03:14, Missile exploded
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 9m)

00:03:22, Missile exploded
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 1m)

Total, SNR On Air Time: 3min 4sec



Also the 20DSU missile doesn't work well with USU option on:

Click to reveal..
00:03:39, Missile exploded on Channel-1
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 96m)

00:03:43, Missile exploded on Channel-2
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 12m)

00:03:49, Missile exploded on Channel-3
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer hit by SAM. (miss distance: 220m)
Posted By: Hpasp

Re: Bug reports - 06/28/15 04:52 PM

Originally Posted By: piston79
Something's wrong with the B-1 type target at Ashuluk...


Click to reveal..
Asuluk training ground.

Practice target:
RM-217 Zvezda [program-4] simulating B-1B Lancer

S-200VE Vega-E


00:30, Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer launched

+++++++++++++++++
00:00:47, SNR ON AIR


00:02:20, Missile launched from launcher-1
Target distance: 97km
Target azimuth: 76°
Target elevation: 10°
Target angular speed: 959m/s (3.4 Mach)
Target altitude: 18.1km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 25.8dB


00:02:27, Missile launched from launcher-3
Target distance: 91km
Target azimuth: 76°
Target elevation: 11°
Target angular speed: 929m/s (3.3 Mach)
Target altitude: 18.1km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target before launch
Received signal strength: 27dB


00:02:38, Missile launched from launcher-2
Target distance: 81km
Target azimuth: 76°
Target elevation: 12°
Target angular speed: 880m/s (3.1 Mach)
Target altitude: 18.1km
RPC mode: MHI - Narrow Beam
GSN mode: Acquire target during flight
Received signal strength: 29dB


00:03:09, Missile exploded
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 20m)

00:03:14, Missile exploded
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 9m)

00:03:22, Missile exploded
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 1m)

Total, SNR On Air Time: 3min 4sec




It is Program-4 of the RM target, simulating the expected (and never fielded) B-1A.

Please note, that the aim of this program was to simulate high altitude and fast target.
Simply the RM missile accelerated well above Mach3 at 18km.


Posted By: piston79

Re: Bug reports - 06/28/15 05:20 PM

Yes, I forgot it is not real B-1.... screwy

Anyway the second one (about USU missiles) is a sure bug....

Quote:

00:03:03, Missile exploded on Channel-1
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer killed by SAM. (miss distance: 99m)

00:03:07, Missile exploded on Channel-2

00:03:16, Missile exploded on Channel-3
Practice target RM-217 Zvezda [program-4] simulating B-1B Lancer hit by SAM. (miss distance: 212m)


Total, SNR On Air Time: 3min 17sec
Posted By: piston79

Re: Bug reports - 07/04/15 05:13 PM

Originally Posted By: Hpasp
Originally Posted By: piston79
SA-5

According to "Manual of battle work of S-200B", page 146,- "RABOTA PO V" knob must be in "AVTOPEREZAHVAT VIKL" mode by default....


Link





In all switches, red dot shows the "forced" default setting on the Vega panel.
That switch albeit mentioned in the manual, and that setting is a reasonable one, before switching POMEHA, you need to anyway select the correct value based on the detected jamming type, thus there is no "forced default" red dot on the panel.
As in SAMSIM we have only noise jamming, the AS VIKL is a good selection.
Anyway, that switch has no effect in SAMSIM.


I wish to point out again in this old "not a bug" but "not a realistic to the switch" knob position.... I target is not jamming, firing with this option on would cause a missile loss...



I guess AS VYKL effect is simulated already, because we have some new behavior when shooting jammers (see my previous bug report about S-200)...


rolleyes
Posted By: Alien_MasterMynd

Re: Bug reports - 07/04/15 08:28 PM

I will finally have to read it completely. Unfortunately my russian is not good, but thanks to very close similarity to czech it is quite understandable for me (although reagarding the speech I would almost not say a word banghead)
Posted By: Hpasp

Re: Bug reports - 07/07/15 08:11 PM

One serious bug was found by Robert from Poland...

Nightime situation shooting with OSA, cause system crash.


Here is the quick fix. Just overwrite the exe.
http://www.mediafire.com/download/eyw5zh528yg68ty/samsimv929b.rar
Posted By: piston79

Re: Bug reports - 07/08/15 08:07 AM

Originally Posted By: Hpasp
One serious bug was found by Robert from Poland...

Nightime situation shooting with OSA, cause system crash.
Here is the quick fix. Just overwrite the exe.
http://www.mediafire.com/download/eyw5zh528yg68ty/samsimv929b.rar


How about the other bugs?
Posted By: Hpasp

Re: Bug reports - 07/08/15 01:07 PM

Can you collect and list those? I will fix them also.
Posted By: piston79

Re: Bug reports - 07/08/15 06:07 PM

Originally Posted By: Hpasp
Can you collect and list those? I will fix them also.


http://www.mediafire.com/view/zs2ggfaji54ymzw/BugsFindings.xls


(please look page 2)
Posted By: Hpasp

Re: Bug reports - 07/09/15 10:21 AM

Thanks, there are 7 bug reports, I will try to replicate those, to be able to pinpoint the bug...
... if unable to do so, I will request for a video showing the bug.

These will be tried to be replicated.

1, SA-5B After launch, when target start using noise jamming, we observe KRO signals.... After reacquiring target on AS-2 and AS-RPC, the first missile reacquired the target too....

2, "Another bug, which accounts probably to lack of variable resetting when SAMSIM is not restarted after a mission (some knobs and switches remember their settings when replayed the same SAM system).

I have finished testing in Giant reach scenario and then selected Osa in Asuluk, added missiles and targets and during start only the ona panel with SOC indicator was displayed along with an error message (Invalid procedure call) and SAMSIM quits.
Then I run SAMSIM again, selected missiles and targets (the same way as above) and everything was OK."

3, SA-8B SOC is imune to HARM

4, SA-2E Run-time error 11: Division by zero

5, SA-8B jamming target
6, SA-2E P-15 Ustka - no KARAT view
7, SA-2E V-755 fuse settings are not OK/USU mode detonates even at more than 100 meters
Posted By: Hpasp

Re: Bug reports - 07/09/15 10:48 AM

found&fixed this one:

4, SA-2E Run-time error 11: Division by zero
Posted By: piston79

Re: Bug reports - 07/09/15 10:58 AM

Originally Posted By: Hpasp


These will be tried to be replicated.

1, SA-5B After launch, when target start using noise jamming, we observe KRO signals.... After reacquiring target on AS-2 and AS-RPC, the first missile reacquired the target too....


It should work on that way if Rabota po V is in AS VYKL mode still reaquiring the target from GSN has no conection with the AS RPC modes... Thus no bug, but the position on RABOTA po V switch is in AVTOPEREZAHVAT VIKL (OFF).....


Quote:
6, SA-2E P-15 Ustka - no KARAT view



As my computer is really crappy this could be because of it...
Posted By: Hpasp

Re: Bug reports - 07/09/15 06:33 PM

As I was able to see the P15 in Ustka, I left with the following open ones:

2, "Another bug, which accounts probably to lack of variable resetting when SAMSIM is not restarted after a mission (some knobs and switches remember their settings when replayed the same SAM system).

I have finished testing in Giant reach scenario and then selected Osa in Asuluk, added missiles and targets and during start only the ona panel with SOC indicator was displayed along with an error message (Invalid procedure call) and SAMSIM quits.
Then I run SAMSIM again, selected missiles and targets (the same way as above) and everything was OK."

3, SA-8B SOC is imune to HARM <- all target acquisition radars are immune in SAMSIM, will need to think about...

5, SA-8B jamming target <- behavior corrected

7, SA-2E V-755 fuse settings are not OK/USU mode detonates even at more than 100 meters
Posted By: piston79

Re: Bug reports - 07/09/15 06:37 PM

At least P-40, P-15 and OSA SOC should not be immune(still P-40 performed well in OAF, I think)...
Posted By: Hpasp

Re: Bug reports - 07/09/15 07:10 PM

2, "Another bug, which accounts probably to lack of variable resetting when SAMSIM is not restarted after a mission (some knobs and switches remember their settings when replayed the same SAM system).

I have finished testing in Giant reach scenario and then selected Osa in Asuluk, added missiles and targets and during start only the ona panel with SOC indicator was displayed along with an error message (Invalid procedure call) and SAMSIM quits.
Then I run SAMSIM again, selected missiles and targets (the same way as above) and everything was OK."


Unable to replicate.
Done the Tallin situation, killed the HABU with the Vega, than started Ashuluk, where killed a Tornado with the Osa.
Would be nice if it is still reproducible to record it in video.
Posted By: Hpasp

Re: Bug reports - 07/10/15 08:31 AM

Originally Posted By: piston79
At least P-40, P-15 and OSA SOC should not be immune(still P-40 performed well in OAF, I think)...


Yes, but keep in mind, that originally SAMSIM is created as a fire control radar (fcr) simulator, never intended to fully simulate the capabilities of any target acquisition radar (tar). Tar indicator was just shown as an information source only for the fco, not simulated "realistic to the switch".
This approach changed with the introduction of the OSA system, that has self integrated tar, so its capabilities had to be simulated much more accurately than ever planned earlier, with "indicator only" independent tar's.
From programming point of view, the SOC still use a completely different code section (object) than the rest of the fcr's, and ARM part is completely missing from it.
Posted By: piston79

Re: Bug reports - 07/10/15 10:17 AM

Yes, and now I believe it should stay on that way, as loosing TAR will make target search imposible (especially for "OSA", "NEVA" and "Krug")....

yep
Posted By: Hpasp

Re: Bug reports - 07/10/15 01:46 PM

My actual plan is to have the OSA tar also HARM capable, as it is fully simulated, and let the other tar's as it is today...
Posted By: piston79

Re: Bug reports - 07/10/15 02:30 PM

Originally Posted By: Hpasp
My actual plan is to have the OSA tar also HARM capable, as it is fully simulated, and let the other tar's as it is today...


I am thumbsup

Hope others too...
Posted By: Hpasp

Re: Bug reports - 07/10/15 03:07 PM

U will have tough life in Benghazi...
Posted By: piston79

Re: Bug reports - 05/17/16 07:34 PM

USU mode doesn't work again (Ashuluk against simulated B-1)

Also no HARM track visible in 3D AAR in third mission in Serbia (in Lybia they are ok)
Posted By: Hpasp

Re: Bug reports - 06/03/16 10:04 AM

checking it...
Posted By: piston79

Re: Bug reports - 10/19/16 05:27 PM

guys, any problems with SA-8 in non-historical scenarios? A friend reports a crash of SAM Sim when target was hit...
Posted By: Hpasp

Re: Bug reports - 10/20/16 01:29 PM

What situation?
Posted By: piston79

Re: Bug reports - 10/20/16 09:51 PM

Originally Posted By: Hpasp
What situation?


Libya for sure, maybe in other non-historical too...
Posted By: Hpasp

Re: Bug reports - 10/30/16 08:18 AM

Did he used Invulnerable mode?
What situation/location (city - battery) did he used?
On what direction/range the target was when the hit (and the game crash) happened?
Did he used the Karat?

I have a theory about this crash...
Posted By: piston79

Re: Bug reports - 10/30/16 03:58 PM

I asked, waiting... yep
Posted By: Hpasp

Re: Bug reports - 10/31/16 12:47 PM

Is this quick fix installed?
Posted By: piston79

Re: Bug reports - 10/31/16 05:03 PM

Originally Posted By: Hpasp


If the fix is inside the install package....
Posted By: Hpasp

Re: Bug reports - 10/31/16 06:05 PM

Ok ask the version of the SAMSIM, if it is less than v929b than shall download the fix from:
http://sites.google.com/site/samsimulator1972/home
Posted By: piston79

Re: Bug reports - 10/31/16 06:29 PM

Originally Posted By: Hpasp
Ok ask the version of the SAMSIM, if it is less than v929b than shall download the fix from:
http://sites.google.com/site/samsimulator1972/home



It must be the recent one, as he just discovered the SAm Sim..
Posted By: piston79

Re: Bug reports - 11/01/16 02:12 PM

Originally Posted By: Hpasp
Did he used Invulnerable mode?
What situation/location (city - battery) did he used?
On what direction/range the target was when the hit (and the game crash) happened?
Did he used the Karat?

I have a theory about this crash...


1. No
2. Bengazi
3. west - F-111
4. Nope. Night mission...

With your first fix - no problem, except some missiles dissapeared... Asked for more specific info... Waiting...
Posted By: piston79

Re: Bug reports - 11/09/16 03:52 PM

Hi there....

Some old issue with missiles..(just delete .jpg and unpack)

As I wouldn't use SAM Sim until a week later I cannot verify this bug, but it looks familiar to me...
Also at that scenario PNS doesn't work (maybe due to jamming)

Posted By: Hpasp

Re: Bug reports - 11/11/16 08:33 AM

Cannot download it.
Posted By: piston79

Re: Bug reports - 11/12/16 12:03 PM

Originally Posted By: Hpasp
Cannot download it.


https://www.mediafire.com/?1k7bxwlt4z9cpck
Posted By: KJakker

Re: SAMSIM ANNOUNCEMENTS - 02/26/17 08:55 PM

A little issue I found. I think you forgot to turn off one of your diagnostics tools.

Secondly, what is up with the S-300PS Volhov-M6/SA-10B? I thought the next system was the S-25 Berkut/SA-1

[Linked Image]

Attached picture CaptureSAMSim.JPG
Posted By: Hpasp

Re: SAMSIM ANNOUNCEMENTS - 02/27/17 07:46 AM

Thanks for the 1st bug report!
biggrin
I will compile another version tonight.

S-300 is just an idea, as I have no operations manual, nor access to Officers working on that system, nor good quality photos of the panel...
... I have enough idea for a coarse sim, certainly not at "Realistic to the Switch" level.
Question if it has any value for the community?
Posted By: piston79

Re: SAMSIM ANNOUNCEMENTS - 02/27/17 01:32 PM

Originally Posted by Hpasp
Thanks for the 1st bug report!
biggrin
I will compile another version tonight.


Just to say, that there is a topic for bug reports....
Posted By: Hpasp

Re: SAMSIM ANNOUNCEMENTS - 02/27/17 04:28 PM

Corrected.
v930.1 is available.
Posted By: ricnunes

Re: SAMSIM ANNOUNCEMENTS - 02/27/17 05:02 PM

Originally Posted by Hpasp

S-300 is just an idea, as I have no operations manual, nor access to Officers working on that system, nor good quality photos of the panel...
... I have enough idea for a coarse sim, certainly not at "Realistic to the Switch" level.
Question if it has any value for the community?


IMO, I think it's always a great idea to have more systems modeled in SAM Simulator.

I believe that with your great talent coupled with some (many?) information that you managed to gather (ranging from images, videos, manufacturer specs, etc...) about the S-300 system that you'll be able to build and model a good and even "realistic enough" S-300 system within SAM Simulator.
It may not be as "Realistic to the Switch" as other systems (like the SA-2, SA-3, etc...) but I'm sure that it will give a "realistic enough" experience to any SAM Simulators players.

Besides if you decide to model the S-300 system in SAM Simulator this wouldn't be the only "half realistic" system modeled in SAM Simulator - Look for example at the ZSU-23-4 Shilka in SAM Simulator where it doesn't have major features modeled in it such as Visual engagement modes and/or the ability to drive/move the vehicle around.

Therefore I strongly believe that a S-300 built/designed by you wouldn't be that "much less realistic" compared to the current ZSU-23-4 Shilka in SAM Simulator, this if taking into account all the realistic features/factors for each system.

So, please go ahead and model the S-300 in SAM Simulator. thumbsup

Well, at least these are my 2 cents on the subject...
Posted By: piston79

Re: SAMSIM ANNOUNCEMENTS - 02/27/17 06:18 PM

Originally Posted by ricnunes


So, go please go ahead and model the S-300 in SAM Simulator. thumbsup

...



...or maybe name it in another way, just to not spoil the "Realistic to the switch" slogan.... neaner
Posted By: Jonas85

Re: Bug reports - 03/03/17 12:31 PM

On installation I got this error:

Run-time error '52': Bad file name or number

Any ideas?

My system is Win 10. Could this be related to the fact that I chose to keep old .dll files when uninstalling the previous SAM Simulator version?

Attached picture error.png
Posted By: Hpasp

Re: Bug reports - 03/03/17 12:48 PM

Mine is also WIN10, so it is unrelated.
Try to unpack it into a different directory, than run setup from there
Posted By: Jonas85

Re: Bug reports - 03/03/17 02:20 PM

No joy.

Re-downloaded the package two times from Mediafire, tried to unpack with different archiver, tried to unpack and install into different folders in different disks.

Does the installer uses data cache or something, or there could be any path corruption due to the different installer/system locales (I am using us-american language settings)?
Posted By: Hpasp

Re: Bug reports - 03/03/17 02:30 PM

Anybody else facing similar behaviour? (installed it successfully?)

Last chance tip:
As you already installed older SAMSIM versions, it is enough if you unpack files from the CAB files, and overwrite earlier installation.
All dat file (with numbered extensions 000...999) goes to data directory, and the sam.exe goes a directory above.
Posted By: Jonas85

Re: Bug reports - 03/03/17 03:48 PM

I uninstalled the previous version, before installing a new one.

Could you upload the screenshot of the folder structure? So I know what goes where.

If your application does not use any registry values, that might work.
Posted By: Hpasp

Re: Bug reports - 03/03/17 04:36 PM

In SAMSIM directory...
sam.exe
data <- directory (all files with *.dat extension)


Here you go with the RAW directory. Just extract it to a folder, and run sam.exe. (in case you already played samsim on your computer)
http://www.mediafire.com/file/89bib6hvso56kj1/SAM_Simulator_9301_RAW.rar
Posted By: Jonas85

Re: Bug reports - 03/03/17 05:36 PM

Thanks, it works now!

I'll report on my impressions of the new jamming effects later.
Posted By: Hpasp

Re: Bug reports - 03/03/17 08:49 PM

Thanks!
So far nobody seems to report any success on those...
Posted By: piston79

Re: Bug reports - 01/04/18 11:00 PM

Originally Posted by Hpasp
Thanks!
So far nobody seems to report any success on those...



Lot of bugs...

1. On RANRAP jamming - if lock the nearest target return, the missile is armed with K3 command and then after passing the first target mark it always detonate near real target (which is always the second mark), but when lock the last return, the missile just passes away, so it is good to use "Rabota ot V" fuse settings, but than when the missile detonates on real target (which is the second nearest mark in the slant range), than all false return dissapeared and miraculously the AS on range jumps to the real target (which is the second nearest mark in the slant range).

2. About angle deception jamming - LORO and it's gone...(not a bug)

3. Range gate Pull-Off - when locked on epsilon and beta only with "Rabota ot V" - no problem at all, except that when AS on range was on the jamming signal it again jumps on the real target after missile detonation...

Tested with SA-2E against baloons.
Posted By: Milten

Re: Bug reports - 05/13/18 09:58 PM

Not sure if it's bug, but now I am providing much more comprehensive report about this strange anomaly. Don't have video, but I think these screens would prove that something is off. (Or maybe I did some humilitating mistake..)
Place: Asuluk. Target: LA-17 Imitating F-86 (basically, easiest target of all)

Picture 1 : https://imgur.com/a/FyBwgwK 100 km range, showing how damn close this target is.P-18 indicator is directly on target all the time. But it's simply not appearing. Using sector or circular search does nothing.
Picture 2: https://imgur.com/a/auCWZnx (commanders' cabin settings)
Picture 3 https://imgur.com/a/iFcheDQ (Range gate and radial velocity indicator for this subsonic target)

Same thing happening for B-52, basicall all subsonic Asuluk targets are completely invisible for VEGA. Supersonic targets can be aquired. IADS aquisition works perfectly for both.
Posted By: piston79

Re: Bug reports - 05/14/18 10:51 AM

Originally Posted by Milten

Picture 3 https://imgur.com/a/iFcheDQ (Range gate and radial velocity indicator for this subsonic target)



How about lock by IADS, then brake the lock and reaquire? How about in historical scenarios?

I have no SIM installed on my devices right now, will check it ASAP...
Posted By: piston79

Re: Bug reports - 05/14/18 10:56 AM

Leaning back on your previous description, it looks like targets are leaving the beam (0.7 to 1.4 degrees).

..and you haven't provided AAR.....
Posted By: Milten

Re: Bug reports - 05/14/18 01:58 PM

Historical missions have supersonic targets (habu, F-14) so these can be aquired fine. "How about lock by IADS, then brake the lock and reaquire?" and weirdly, it made everything fine! I locked by IADS, unlocked and manual mode suddenly works. You can lose and then aquire it fine in manual after using IADS. But before using IADS, target is simply invisible. (IADS is not changing beam's direction even for a degree. It's just make target suddenly appear, without changing any parameter on SAM).

Asuluk training ground.

Practice target:
LA-17 simulating F-86 Sabre

S-200VE Vega-E


00:00, Practice target LA-17 simulating F-86 Sabre launched

+++++++++++++++++
00:00:12, SNR ON AIR


Total, SNR On Air Time: 17sec
Posted By: piston79

Re: Bug reports - 05/15/18 11:00 AM

On historical scenario there are subsonic targets (E-2, E-3 etc.)
Also it is important to note that the closer velocity (radial speed) is important, not the target's own speed.

As I am unable to switch on my SAMSIM computer, try this - do a mission with IADS (Ashuluk), then pick up the target's speed value from the AAR. Than restart the SIM and do same mission manually, so you could input the radial speed manually. Please do a photo of the velocity indicator, but only the upper part (S or D key if I remember correctly). Try circle scan...
Posted By: Milten

Re: Bug reports - 05/18/18 05:15 PM

Target radial speed: 289 m/s.

Radial speed setting: https://imgur.com/a/OaYQUbV

As before, target invisible with circular and sector search.
Posted By: piston79

Re: Bug reports - 05/19/18 07:51 AM

Originally Posted by Milten
Target radial speed: 289 m/s.

Radial speed setting: https://imgur.com/a/OaYQUbV

As before, target invisible with circular and sector search.



At last I got my SIM computer, and yes - there is a bug with those (on Hungary it is OK, also in GIANT REACH).

UNFORTUNATELY HPASP ABANDONED THE PROJECT AND THIS CANNOT BE FIXED... AFAIK HE EVEN DON'T READ THE FORUM ANYMORE...
Posted By: Milten

Re: Bug reports - 05/19/18 10:56 AM

Ah, yeah. I know that Hpasp abandoned project. Just wanted to know if it's bug or I am doing something wrong. Good thing that you confirmed that historical mission works properly. Thanks, piston.
Posted By: piston79

Re: Bug reports - 07/02/18 05:06 PM

Some minor issues......

1. E-3 changes it's altitude, but it doesn't being noted on ploating board
2. SR-71 starts jamming, but it doesn't being noted on Ploating board.. (code change frome 31 to 01)

(Giant Reach mission)
Posted By: piston79

Re: Bug reports - 12/12/19 10:48 AM

Guys, as I usually work with SA-5 and SA-2E, please, those who are proficient in other systems (SA-3/4/8) check the new jamming with those systems, please...
Posted By: piston79

Re: Bug reports - 12/14/19 06:14 PM

So far managed to check SA-4:

- again with RANRAP jamming after the target is destroyed, the lock jumps from a false target to the real one ( I locked on the furthermost target return and activate missile fusing right after firing)

- when transmitter is off, the jamming is visible on screen with the real target (which is impossible in reality). Screenshots provided for better understanding.

- miss distance is always zero on radar reflectors. I can kill them even in 1/2 guiding method


About SA-3:

- same as SA-2 and 4 about RANRAP
- not sure a bug: missiles detonates with huge miss distance and still manage to kill the target- first - the huge miss distance is strange as I used only radar reflector targets, also kill is strange

Pic 1

[img]https://www.mediafire.com/view/qtqox62q4yss7q9[/img]
Posted By: piston79

Re: Bug reports - 12/14/19 06:15 PM

So far didn’t tested SA-8 and Shilka
Posted By: piston79

Re: Bug reports - 01/07/20 07:44 AM

Ploating board on Linebacker II doesn't work:

night1 wave 3
© 2020 SimHQ Forums