Jump to content

Mobile TACAN Beacon...How About ILS?


WytchCrypt

Recommended Posts

Hi all,

 

I just stumbled across the mobile TACAN beacon (Ground Units->Fortifications->TACAN Beacon TTS3030).  Just tested it on a Caucasus airfield without existing TACAN and it worked perfectly.  Got me thinking though, is there also (or plans for) a mobile ILS unit? 

 

I fly the Caucasus map 99% of the time and it would be great to get TACAN+ILS on those airfields even if I have to put some kind of mobile units there to get the job done.

Alienware Area-51M: i7-9700K, 165Hz 27" ASUS Swift PG279 IPS with G-SYNC, 32GB DDR4 Ram, 1TB M.2 PCie x4 SSD, 1TB SSHD, NVIDIA GeForce RTX 2070 8GB GDDR6, Windows 10, CH Eclipse...

 

Check out my fictional F/A 18-C Hornet and Su33 Flanker skins at: https://www.digitalcombatsimulator.com/en/files/?CREATED_BY=WytchCrypt&set_filter=Y

Link to comment
Share on other sites

7 hours ago, TonyG said:

I’ve added ILS signals to Anapa so far. 
https://github.com/madmoney99/Caucasus-and-NTTR-ICLS-Mod

 

Hi Tony,

 

I've been using your excellent Caucasus and NTTR ICLS Mod for quite awhile now.  Very happy to see you've added Anapa to the ICLS list and will give it a fly.  I'm wondering, is it not possible to add ICLS channels to the other missing coastal airfields like Gudauta, Sukhimi, Novorossiysk & Gelendzhik?

 

Thanks,

Dennis

Alienware Area-51M: i7-9700K, 165Hz 27" ASUS Swift PG279 IPS with G-SYNC, 32GB DDR4 Ram, 1TB M.2 PCie x4 SSD, 1TB SSHD, NVIDIA GeForce RTX 2070 8GB GDDR6, Windows 10, CH Eclipse...

 

Check out my fictional F/A 18-C Hornet and Su33 Flanker skins at: https://www.digitalcombatsimulator.com/en/files/?CREATED_BY=WytchCrypt&set_filter=Y

Link to comment
Share on other sites

It is a laborious process of getting the coordinates for each beacon (localizer and glideslope).  It can be done for every runway in all the maps, t would just take time.  
 

Adding them where there are existing ILS is easy, just copy/paste and bit of editing.  Creating them from scratch is the time consuming process. 

Link to comment
Share on other sites

26 minutes ago, TonyG said:

It is a laborious process of getting the coordinates for each beacon (localizer and glideslope).  It can be done for every runway in all the maps, t would just take time.  
 

Adding them where there are existing ILS is easy, just copy/paste and bit of editing.  Creating them from scratch is the time consuming process. 

 

Got it.  Another question...I notice that you changed some of the TACAN codes from your previous 2019 "Caucasus and NTTR ICLS Mod":  

 

Anapa 45X -> 59X

Belsan 50X -> 51X

Krasnodar-Centre 94X -> 39X

Maykop 40X -> 53X

etc...

 

And also some of the ILS Channels as well:

Krasnodar-Centre CH9 -> CH17

Batumi CH13 -> CH16

etc...

 

Can you comment on why it was necessary to change those?

 

Thanks!

 

Alienware Area-51M: i7-9700K, 165Hz 27" ASUS Swift PG279 IPS with G-SYNC, 32GB DDR4 Ram, 1TB M.2 PCie x4 SSD, 1TB SSHD, NVIDIA GeForce RTX 2070 8GB GDDR6, Windows 10, CH Eclipse...

 

Check out my fictional F/A 18-C Hornet and Su33 Flanker skins at: https://www.digitalcombatsimulator.com/en/files/?CREATED_BY=WytchCrypt&set_filter=Y

Link to comment
Share on other sites

1. I downloaded this info Excel and had it feed me frequencies as I made a few of the TACANs into VORTACs. 
2. For Anapa I was chasing a bug that ended up being something totally unrelated.  
3. The ICLS I wanted to keep away from ones I was using in missions that conflicted with the land based ones. 
 

https://www.tele.soumu.go.jp/resource/e/search/share/pdf/a2-2.pdf

Krasnodar is actually 94X, readme is incorrect. 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...