ILS NOT WORKING IN NEVADA MAP

THE ILS IS NOT WORKING IN NEVADA MAP...

 

Was driving me crazy, what was I doing wrong....

Frequency and Tacan corrects, but the glideslope oand localizer do not appear.... :cry:

 

Then I installed the C-101 in DCS World 1.5 did everything the same but in Batumi ILS.. and there it works! Frequency gives localizer and glideslope,

Tacan gives the distance...

 

And by the way communications menu does nor work either, and one can not map many commands like Landing lights for example...

Great aircraft but.. very annoying bugs.

 

And needless to say, in the very same situation both the A-10 and the Mirage2000 catch perfectly localizer and glideslope

(Groom Lake), and with both the communication menu work perfectly.

Edited January 20, 2016 by ac5

I just recently installed 2.0 so I don't have that much time playing on the Nevada terrain, but I don't think Nellis - if that's the airstrip you're referring to - has an ILS. Click on the airbase in the F10 view and you will see that there is no listed ILS frequency.

I am talking about Groom Lake.

If you read at the bottom of my message.....

"And needless to say, in the very same situation both the A-10 and the Mirage2000 catch perfectly localizer and glideslope

(Groom Lake), and with both the communication menu work perfectly".....

I just recently installed 2.0 so I don't have that much time playing on the Nevada terrain, but I don't think Nellis - if that's the airstrip you're referring to - has an ILS. Click on the airbase in the F10 view and you will see that there is no listed ILS frequency.

 

The F10 view is missing the ILS data. In the A10 NAV-DIVERT page, Nellis is listed as 109.10, and it works in the A10. I can't get a thing working in this aircraft either, I think we are missing a navdata file update.

As far as I can see no navigation working in Nevada for C101.

Devs know about it.

Indeed... but I am wondering what is Aviodev doing about it...

And also wondering why it works with the Mirage which is also Beta and appeared much later.....

The C-101 was released a Y E A R ago, and I don't see much improvement since then. For example: one can not map many commands like Landing lights. Aviodev ? Alguien quere hacer el favor de comentar algo?

FWIW, I've modified the navdata.txt file for the C101 and TACAN does function in the Nevada map. I don't have a clue what to do for ILS, though.

Indeed... but I am wondering what is Aviodev doing about it...

And also wondering why it works with the Mirage which is also Beta and appeared much later.....

The C-101 was released a Y E A R ago, and I don't see much improvement since then. For example: one can not map many commands like Landing lights. Aviodev ? Alguien quere hacer el favor de comentar algo?

 

DCS 2.0 is an alpha product... many modules lack or missed something.

OK thanks...

DCS 2.0 is an alpha product... many modules lack or missed something.

OK.. DCS 2.0 is an alpha product... many modules lack or missed something.....

But it seems that the A- 10 is missing nothing, and so the Mirage, at least in what the navigation / ILS / Tacan concerns.

Only ED, BST and Razbam use the "standard files" for navigation in DCSW maps.

 

Other 3rd parties use "custom" navigation systems for now.

 

It could be much better if all of them make use of the "standard files" but it´s a decision of the developers.

 

Regards.

FWIW, I've modified the navdata.txt file for the C101 and TACAN does function in the Nevada map. I don't have a clue what to do for ILS, though.

 

Please share with the rest of us while we wait for a fix:megalol::megalol:

OK.. DCS 2.0 is an alpha product... many modules lack or missed something.....

But it seems that the A- 10 is missing nothing, and so the Mirage, at least in what the navigation / ILS / Tacan concerns.

 

Actually the Mirage is far from beign finished. The Mig21 has a lot of problems too, so...

 

I know Aviodev is taking too long to delivery the EFM, BUT, you should not take into account whatever it is in NTTS, people use to misunderstand this.

 

NTTS is for testing only, if you play and something is wrong, do not complain, just report the bug so the devs can fix it.

Please share with the rest of us while we wait for a fix:megalol::megalol:

 

If you are comfortable editing the navdata.txt file...

 

Increase the number in the first line by one - this is a beacon counter I believe. Add the following to the end of the file:

 

TCN

000000

012

X

LSV

1

36.244644

-115.025113

564.647034

0.0

0.0

0.0

0.0

 

and save it That should give you TACAN at Nellis. I'm not clear if the elevation (564.647034 meters I assume) should be expressed that way or in feet. That might be why I'm having trouble with ILS. The raw data comes from Beacons.lua. The format of the entries is in the Read Me.txt in the data forlder.

FACT is, dear ESAc_matador, that the A-10 and the Mirage have a properly

working ILS and tacan, IN NTTS, as should the C-101.

And yes, that might sound as a complaint, but I am reporting a bug here.

Another fact is that in one year Aviodev has done almost nothing to pull that bird out of beta. Just FACTS.

Another fact is that in one year Aviodev has done almost nothing to pull that bird out of beta. Just FACTS.

Unless you've been watching over their shoulder every minute of the day, you really can't say what they have or haven't done. They've had major set backs and as customers we're entitled to be disappointed and complain about lack of progress but to say they've done nothing is pretty baseless.

At least I have seen no improvement. You can still

not map the most basic commands like Landing lights, the weapons systems has not been implemented, etc. And now the nav / ILS not working in NTTS.

I see a much higher dynamic with the other developers. Period.

If you are comfortable editing the navdata.txt file...

 

Increase the number in the first line by one - this is a beacon counter I believe. Add the following to the end of the file:

 

TCN

000000

012

X

LSV

1

36.244644

-115.025113

564.647034

0.0

0.0

0.0

0.0

 

and save it That should give you TACAN at Nellis. I'm not clear if the elevation (564.647034 meters I assume) should be expressed that way or in feet. That might be why I'm having trouble with ILS. The raw data comes from Beacons.lua. The format of the entries is in the Read Me.txt in the data forlder.

 

Thanks Livers..that worked:thumbup:

Maybe we can have ILS in Nevada, along with all the VOR/TACAN. I've attached a file for all to test. Note - for the NTTR map only, no Georgia locations included. As there are some discrepancies between the 'map' and the locations published in beacons.lua, I've stayed with Beacons.lua for the moment. As always, save away your original as an update or repair will no doubt overwrite this. Any problems, let me know. ILS locations added are:

 

Nellis RWY 21L, 109.01

McClarren RWY 25R, 110.30 - RWY 25L, 111.75

Groom Lake RWY 32R, 109.30

Creech RWY 08, 108.70 - RWY 13, 108.50

 

Fair warning, getting the ILS to work required using some magic numbers for localizer and GS bearings to get them on the runways. No doubt they could use some tuning. A big thanks to uboats for all his navigation work in DCS - I've read them all and used a lot of his work to figure this out.

navdata.txt

TO the devs:

Are there any plan for the C-101 and your future Aircraft to use the nav database that comes with DCS world?

It seems very back way around having to update them every time ED does, and possibly ending up with errors vs what is shown in F10 map or mission editor

same question too

hope this can be addressed ASAP

I really thought Aviodev would fix that ILS not working in the

Nevada map in DCS 2.02.

But it still does not work! All other planes are ok.

And so is the C-101 in 1.5 Caucasus map.

DISAPPOINTING......