Link 16 things you want in the next update
-
Morse Code identifier for TACAN and ILS
Question:
.– … .- - / … … / – — .-. … . / -.-. — -… . …–…
-
-
-
I’ll help, he is asking “What is Morse Code?”
It was a pun it’s not even funny anymore with all the translators online
-
Question:
.– … .- - / … … / – — .-. … . / -.-. — -… . …–…
-
Question:
.– … .- - / … … / – — .-. … . / -.-. — -… . …–…
QRK 5 … yes I wondered what it was aswell but seeing as most modes are Digital now on most bands i think Samual Morse was a visionary … 73s DE Haggis
-
in general Mavericks behave good but on locking targets it locks it’s own then I have to unlock and re-lock which wastes lots of time. Why would it lock a target farther from what I put the cross hair on? doesn’t make any sense. Can we have a fix for that?
-
Did you do a Boresight? If not it’s simply going to grab the most significant heat source in the scene once it’s uncaged…or after a break-lock.
-
Morse Code identifier for TACAN and ILS
That would be cool.
I wonder if any of the Korean air bases broadcast the ATIS on the ILS freq instead of the morse code identifier?
I don’t believe so but the world is at your finger tips to confirm here(although the UHF freqs aren’t always available):
https://skyvector.com/
@HaggisHero:That`s also a good Point . that leads me to another point. ATIS audio sounds too clean, rich and non Radio quality, as it is TTS.
I have software here that can generate audio files for morse code and also make TTS sound more radio like… if ATIS and Morse can be implemented in an audio file way then i have no problem getting this done if askedYeah it is missing some of the background carrier noise that IVC adds and the ATC sound files kinda have baked in.
@Stevie:AFAIK, ATIS is always broadcast on it’s own discrete VOX freq, as keeping it updated and current falls to the local Command’s Weather Office. I used to have an office mate that was a USAF weather guy in Viet Nam…then he came home, went to flight school, and went back in the back seat of F-4s.
Yeah, or in the civilian world that doesn’t have computerized text to speech, the controller that drew the short straw. Unlike in the 60-70s, you pretty much check the weather stations readout from the latest METAR/SPECI and read that in to the recorder with the NOTAM etc.
Well, the reason I ponder is that a few of the local navaids in Australia operate that way.
That’s kinda useful, I’ve know a few U.S. airports to have ATIS/AWOS/ASOS if it is an on the field navaid, but they were rare and now most of the on the field VORs are killed off or are dying.
-
Did you do a Boresight? If not it’s simply going to grab the most significant heat source in the scene once it’s uncaged…or after a break-lock.
let me try that
-
Did you do a Boresight? If not it’s simply going to grab the most significant heat source in the scene once it’s uncaged…or after a break-lock.
it worked fine with SA6 but had somewhat the same problem with SA11
-
can we make the taxi & landing lights accurate per block please? The older blocks had a round lighting on the main gear struts the newer blocks (I think 40 and up) have them rectangular on the NW gear door. Thank you
-
AmbientMin should have a Defined by Server option.
-
SA-8 range circle in ppt.ini modified for 8 nm once for all.
-
-
SA-8 range circle in ppt.ini modified for 8 nm once for all.
Same question here. According to my brother who serves as Officer in a Luftwaffe Patriot Regiment. We took over serveral SAM systems from the former NVA in 1990. The range of the 9M33 is < 10km so less than 5.3 NM. So it more that BMS tactical reference is wrong which shows 9NM for the 9M33 as well as the ceiling is to high
-
Same question here. According to my brother who serves as Officer in a Luftwaffe Patriot Regiment. We took over serveral SAM systems from the former NVA in 1990. The range of the 9M33 is < 10km so less than 5.3 NM. So it more that BMS tactical reference is wrong which shows 9NM for the 9M33 as well as the ceiling is to high
The answer is not simple.
1. I have quite clear memories of SA-8 engaging and guiding above 4 nm. That was in 4.33, and 4.34 probably? Not sure. I have no clear recording of that. I also have at least one report of such a thing.
https://www.falcon-lounge.com/falcon-bms-essentials/threats-guide/surface-to-air-missile-sa-8/
The first weakness we can exploit is the SA – 8’s relatively short range, about 5 – 7nm in BMS. Because of this and the AIs tendency to prosecute at maximum range one can react quickly to the incoming threat by performing a maximum performance brake turn away from the missile while descending sharply before rapidly exiting the threat envelope. While conducting the defensive turn chaff should be used liberally. Additionally the system has a shallow launch angle, one can use this against the SA – 8 by performing a rapid climb then a rapid descent which should drive the missile into the ground.
2. Public sites give ranges above 4 nm.
3. I tested again in 4.35.2. The SHORAD SA-8 site didn’t engage above 4 nm. For that reason, there’s no reason to change the ring, thus we agree on that.
4. I have a strong doubt SA-8 were labeled as SHORAD in previous versions.
5. I am pretty sure there was a search radar assisting the TELAR, labeled as “Oscar” on our usual RWR.
I highly suspect something changed between 4.34 and 35 (maybe 33 - 34 but I doubt it), which I didn’t find in any log, concerning SA-8 battalions and maybe vehicles. I can’t check easily.
-
What is the current range of the ring ? … Normally it should be about 6-7Nm or so …
-
It is 4 Nm. Testing in 3D is consistent with this value.
-
…
Indeed … most (if not all) SAM RING are bullshit. I don’t know who changed them but system has not been designed around those values.
So I will (one more time) set them back to what they should be (by design, not by experience which is irrelevant now anyway since IA brain has changed a lot and now SAM top no fire at the same distance all the time as it was before).
Then I hope nobody will change them again afterward without know how systems has been designed in database.