[4.34.1] "TRBMS 06 ILS WEATHER", ILS fail?
-
I was trying the “TRBMS 06 ILS WEATHER” training mission and the ILS doesn’t work and tower give you vectors to RWY 14, can anyone check it?
-
Yeah, I’m having the same issue. I was practicing that over and over again before the new 4.34.1 update and it worked fine. I thought it was just me missing something after the update, since I’m new and still learning, but I double checked all the settings and ILS frequency and it was all correct.
-
ILS rotary on the “on” position?
I used the ILS yesterday without any issue
-
Flow, did you try the training mission 6 in 4.34.1? It seems to be specific issue for that mission. I have the same problem, squadron mate of mine too. It seams mission specific (or perhaps airbase?): other ILS missions work fine. ILS is on ,correct frequency. The captains bars appear in the hud; but the ILS is never ‘picked up’ (no command steering; and ils flags in the ADI), even when just a couple of miles out of base.
-
Update 1 chaged the Taegu frequency apparently:
therefore the charts, training missions and docs are not correct anymoreNo idea what was the purpose of this
Here’s the stations.dat line for Taegu 4.34.1# Taegu (K-2) - ex Taegu (Daegu) 778 125 X 21 35 1 365000 126200 11190 0 10870 10870 240600 275800 346300 0 127650 2530 2438 2484
and the 4.34;
# Taegu (K-2) - ex Taegu (Daegu) 778 125 X 21 35 1 365000 126200 0 10870 0 0 240600 275800 346300 0 127650
As you can see, Taegu in 4.34 only has 1 ILS freq 108.700 and 4.34.1 has 3: 111.9; 108.7 and 108.7
Since Taegu in 4.34.1 only has 1 runway and therefore no need for 3 ILSSo the new - wrong frequency should now be 111.9
This isn’t in the changelog, so I guess it was a copy paste mistake from a more advanced versionIf you want to correct this, Use this line in your stations.dat file:
# Taegu (K-2) - ex Taegu (Daegu) 778 125 X 21 35 1 365000 126200 0 10870 0 0 240600 275800 346300 0 127650 2530 2438 2484
Not yet tested but that should again sync the nav data and the docs and the charts
If the copy paste error is what actually happened, chances are that others airbases will suffer from the same issue
-
I went and checked training mission 4 and the ILS works fine there. I went back to mission 6 and checked the ILS rotary was on. It is on by default when the mission starts. The DED displays ILS on, and when I rotate the knob off, it displays off on the DED and the ILS bars disappear on the HUD. The ILS bars remain dashed on the HUD no matter how precise I try and fly the DME ARC.
-
If the copy paste error is what actually happened, chances are that others airbases will suffer from the same issue
As I expected,
Beside Taegu, the following airbase ILS order changed:
Choongwon, Seoul, Suwon and YechonHaven’t checked for navigation data impact yet, but I suspect it’s simply an unthought stations.dat file copy paste from another version, rather than a specific modification for 4.34.1 airbase frag code addition as mentionned in the changelog
Will investigate further in the coming days
-
I went and checked training mission 4 and the ILS works fine there. I went back to mission 6 and checked the ILS rotary was on. It is on by default when the mission starts. The DED displays ILS on, and when I rotate the knob off, it displays off on the DED and the ILS bars disappear on the HUD. The ILS bars remain dashed on the HUD no matter how precise I try and fly the DME ARC.
Mission 4 is at Kunsan and the lines for that airbase are fine, so that is normal.
Did you try frequency 111.9 at mission 6?
I bet it works, but since it doesn’t match documentation, it is not productive -
Time for a small documentation update then
-
I’d rather vouch for a quickfix with a correct stations.dat file
It’s much quicker and more efficientbut in the meantime, it can be fixed with the above statiosn.dat changes for Taegu
-
No idea what has changed in 4.34 stationILS (?) … I do only work on 4.35 … I can’t do anything for the 4.34, but I will take a look on the DEV branch.
If needed, I think a “hot fix” will be very easy.
-
No idea what has changed in 4.34 stationILS (?) … I do only work on 4.35 … I can’t do anything for the 4.34, but I will take a look on the DEV branch.
If needed, I think a “hot fix” will be very easy.
no hotfix if those changes are justified for next version
Doc might need update
-
Dj, I think the whole file has been copied from 4.35 to 4.34 update 1
Might be wrong as I didn’t follow update 1 dev, but that’s seems coherent since update 1 Taegu is still a single airbase runway and the stations.dat clearly have ILS frequencies for a double runway airbaseIMHO a hotfix would be nice.
If needed, I can have a new file tested and checked ASAPI haven’t checked the différences at the other airbases I mentionned above
Doc might need update
the problem you refuse to understand is the impact such tiny mistakes have on the whole documentation suite
These references are used all over the place in the charts, AIP, training docs, Training missions, coms and nv book, dash1 etc etc
By the time all these docs are updated for that small mistake, then 4.35 will be out so it is not productive, and not efficient to let the Community with such a gap for 6 months or moreThe docs will be of course updated for 4.35
-
@Red:
Dj, I think the whole file has been copied from 4.35 to 4.34 update 1
Might be wrong as I didn’t follow update 1 dev, but that’s seems coherent since update 1 Taegu is still a single airbase runway and the stations.dat clearly have ILS frequencies for a double runway airbaseIMHO a hotfix would be nice.
If needed, I can have a new file tested and checked ASAPI haven’t checked the différences at the other airbases I mentionned above
you are right
Dont know if this worth a hotfix though
affected airbase
Yechon
Taegu
Suweon -
@Red:
Dj, I think the whole file has been copied from 4.35 to 4.34 update 1
Correct. I am with Jp … he will explain … but it is indeed an accident! (working too much!)
But you have seen that there will be some initial changes for 4.35 (because of, you know why ) … of course, if you need to re-apply some modifications … your option.Hotfix is a good idea … and easy stuff.
(Lets wait a little, 4.34.1 feedback just starts, maybe we could have other things to add in possible hotfix?)…
Or … lets publish a NOTAM on the main forum section.
-
Just bundle up the correct files in a ZIP which I can attach to the 4.34 U1 release thread with the corresponding info where to put it in the BMS installation, that should suffice. No need to build a full-blown update installer for this I suppose. Unless there are multiple files in different locations affected. Just PM me over in the DEV forum once you have decided how to proceed. Thanks!
-
Correct. I am with Jp … he will explain … but it is indeed an accident! (working too much!)
But you have seen that there will be some initial changes for 4.35 (because of, you know why ) … of course, if you need to re-apply some modifications … your option.I’m sure it is
Mistakes are only done by ppl working, so it can and will happen, that’s expected
The important thing is IMHO how we fix our mistakesI’ll have a correct station.dat file ready soon. We can also post this on the forum and refer to it whenever someone ask or report the same subject as this topic.
Either way, it is not for me to decide how you guys want to have itOr … lets publish a NOTAM on the main forum section.
hehe, good idea
-
Just bundle up the correct files in a ZIP which I can attach to the 4.34 U1 release thread with the corresponding info where to put it in the BMS installation, that should suffice. No need to build a full-blown update installer for this I suppose. Unless there are multiple files in different locations affected. Just PM me over in the DEV forum once you have decided how to proceed. Thanks!
Will mod the stations.dat and send to dev for decision
-
@Red:
hehe, good idea
Well … yep it could be. Sort of “what’s up there!” on the main forum section, largely visible to inform ppl of important stuff such as announcements, known bug … . And/or using the "notification “system”. (?) … It could be something interesting to think about.
-
I went and checked training mission 4 and the ILS works fine there. I went back to mission 6 and checked the ILS rotary was on. It is on by default when the mission starts. The DED displays ILS on, and when I rotate the knob off, it displays off on the DED and the ILS bars disappear on the HUD. The ILS bars remain dashed on the HUD no matter how precise I try and fly the DME ARC.
My ILS and TACAN rotary (the one beside the HSI) is missing. No idea what happened, but every model of f16 is missing the rotary.