Whats the difference between ILST and ILSN on the left side of the right display?
It is necessary to distinguish the 4 modes:
-TCN: When you are capturing stations based on TACAN channels, in this case NAV will use TACAN over VOR or GPS.
-ILSTCN: when you have an active tacan channel + a valid ILS frequency, in that case NAV will disable TACAN or GPS so you can capture the GS (an example would be trying to approach the KLAX using a valid TACAN channel plus an ILS frequency for the final approach, Tacan navigation will be interrupted so you can capture the GS with APP).
-NAV: Normal VOR navigation when TACAN is disabled or no valid Tacan channel is active.
-ILSNAV: the same as NAV but for ILS approaches without TACAN navigation active. for example, you have a vor frequency in NAV1 and ILS in NAV2 or viceversa or just an ils frequency and nothing else.
Unfortunately there are hardly any TACAN frequencies you can experiment with in MSFS, with ILSNAV being the most widely used method.
what you will notice is the following: if you tune to an ILS frequency and try to activate ILSNAV outside the capture radius it will not let you, you will have to activate NAV meanwhile until you are close enough. Once done, you can enable ILSNAV so you will display all the info in the HUD (CDI and GSI).
Ok i see. Tacan over rides other navs, that may explain why i have trouble capturing ILS/GS.
I tend to fly mostly from military to military runways so i use Tacan more often than gps or vor.
So if i disable TCN il be able to capture ILS or RNAV approach.
As im on xbox this is a whole new curve to climb so i may be picking your superior noodle often lol
Cheers Jack always appreciate your help
I had this issue, and others (see my earlier post in this thread). Everything started working correctly when I removed the enhanced F18 Super Warrior mod from flightsim.to from my community folder. I think its a messy mod that in terms of its coding. Its clearly having an effect on others things.
Yeah, TACAN DRIVES NAV and GPS DRIVES NAV.
For example i take off from EGUL heading to EGOV,
Before take off i set TCN to CH21X for EGOV and input 108.550MHz into nav2.
When i reach about 30miles from EGOV i disable TCN and swap navs 1&2 over to pick up LOC DME. Then follow the VOR bearing (OBS) to find start of approach. Then drop gear(below 300kts) and wait for ILS to show on HUD or MFD and follow it down?
At which point would i (if inclement weather) engage ACLS?( sorry if that F14 version im not infront if it today)
I have noticed that the afterburner cone appeared to vanish at night on my flights. Iâm wondering if it is something to do with the way the old cones worked, they were invisible during the day but visible at night, and something has got lost in translation?
Excuse me sir you have parked in a restricted space could you please âMOVE IT!â
Now im gona be singing Reel to Reel ft the mad stuntman all day.
Thanks
probably this image better be post there What do you do with military aircraft?
For me, the new afterburner effect doesnât show day or night, when it chooses not to work. When it does work itâs fine no matter the time of day. I actually started that flight during the day, but moved it to night just to make it clear for the photo.
Ahh I see what you mean now. No I donât have it either. Just the flame on and off. It doesnât eject out the back like the F/A 18.
This sounds like just another one of those â â â â â â MSFS bugs that have no apparent rhyme or reason. The burner cone effect is Asoboâs, like the G-vapor and contrails, so it should work as advertised. Very hard to know why it does not ( works fine here, day and night ).
assuming that tacan channel works is an example of tcn and ilst. always use the HSI as a reference. if you activate tcn in the HSI you wonât have to adjust the crs manually when using nav (it adjusts itself). when you are within range of the GS the Tcn function will be deactivated, that is when you can press ILST. As long as you have the function activated, the info will appear on the HUD. in the case of ILS you will see the GS, when you position yourself correctly in altitude, you know, when the GSI is aligned, you proceed with approach.
@CodenameJack447 I just found this forum and I really appreciate you and Deanâs updates. Iâve learned a ton about the update from your posts the past couple weeks and the more we can get this to be like the real thing Iâm all for! I have a couple questions regarding hotkeys and if itâs possible in MSFS. I have a keyboard hooked up to my xbox and I like starting cold and running down the sequence.
I canât seem to get the Main power switch hooked up (i.e animating) when I have the toggle master battery and master alternator hotkey tied to it. On the actual switch it says Main Power and GPU so I feel like there is another element I need to add to the toggle. Otherwise it might be custom made from you guys and not possible to hotkey. When I try to hotkey it it just turns on then off again.
The JFS starter switch can be bound by the APU toggle hotkey right? From your cold start video it looked it that was the case.
Another thing I noticed is when I hotkey the âArm autothrottleâ it doesnât work the first time, but ONLY the first time. When I engage autopilot, I will then hit that hotkey the ded will say âautothrottle onâ however the speed doesnât change. I need to go in cockpit and manually flip the IAS switch. It will then immediately go to my set speed. After that initial manual flip switch, I can THEN hit the hotkey and the switch will flip back and forth in the cockpit and turn the autothrottle on and off in the ded as expected. I donât know if this is intentional or a odd quirk.
Lastly, since jets are such a different beast, is there a way to hotkey the ILSN, AWLS or any of the other MFD buttons at this point in time?
I know this was a lot, Iâm having a great time putting the F16 through itâs paces, Iâm just seeing if I can streamline my experience. Thanks in advance!
Welcome to the channel! Iâm glad youâre liking the updates! I will try to help you or at least clarify the doubts.
MainPower switch has 3 positions:
0: toggles off battery, avionics and external power.
1: toggles on battery, avionics and toggles off external power.
2: toggles on battery, avionics and external power.
What happens is that it is a switch that implements a local variable that constantly checks the status of these 3 Simvars and therefore, no matter how much you want to turn on the battery for example, it will turn off according to the position of the switch. I am studying another way to do it, which is that the Simvars update the state of the switch and not the other way around. I think that this way could allow users to map the key events in the future.
the JFS starter if you could map it but there are three events too:
- APU_GENERATOR_SWITCH_SET
- APU_BLEED_AIR_SOURCE_SET
- ENGINE_BLEED_AIR_SOURCE_SET
that is, to finally be able to use the normal starter you must activate the APU, and bleed both the apu and the main engine.
This has an explanation. the autothrottle arm event only arms the autothrottle but doesnât enable airspeed hold (or mach hold), thatâs the second event you miss here and what the IAS switch or the DED buttons do.
But in DED case:
- ATHR ON, arms autothrotle and hold current speed.
- THR value, arms autothrotle and set the desired speed.
- AWLS simply sets the calculated landing speed, but it is still a local variable and therefore cannot be mapped. It doesnât actually activate Athr on its own. It only calculates the speed and fixes it when athr is activated
this part is the same, MFD functions trigger local variables or HTML events, not system events, so they are not mappable.
I just want to thank you for such an in depth, informative answer so quickly. Totally makes sense about the MFD functions. I wish it were easier pressing those tiny buttons on xbox!
In theory, for the main power, could I use three different buttons with the functions tied to each state of the switch in the cockpit? And good to know about the jfs switch, Iâll map those functions tomorrow.
Regarding the auto throttle, I guess there is no way to hotkey the IAS separate from arming the auto throttle in MSFS right?
Again, thanks for a quick reponse and have a great weekend!
No thanks needed! Happy to help :).
Yes, but it wonât do you any good for now until I implement it that way. Probably in the future you will be able to if I release the local variable to automatically change the states of Avionics, battery and gpu.
You can, just map airspeed hold in addition to autothrottle. You can also add spd + and spd - to control desired airspeed