homepage Forums Air Combat & Civil Aviation SAM Simulator Bug reports

Thanks for the 1st bug report!

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?

Just to say, that there is a topic for bug reports....

Corrected.
v930.1 is available.

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.

Well, at least these are my 2 cents on the subject...

...or maybe name it in another way, just to not spoil the "Realistic to the switch" slogan....

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?

Mine is also WIN10, so it is unrelated.
Try to unpack it into a different directory, than run setup from there

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)?

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.

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.

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

Thanks, it works now!

I'll report on my impressions of the new jamming effects later.

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.

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.

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...

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.....

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

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...

Target radial speed: 289 m/s.

Radial speed setting: https://imgur.com/a/OaYQUbV

As before, target invisible with circular and sector search.