Bravo

OK, I will wait for another update and try to explain it better if it persists past the next update. But since then I noticed that when flying an ILS the dot or sperm without the tail gives you where to put your FPM to intercept and fly the cross, while in steerpoint mode when I try to put my FPM such that the tadpole is inside the FPM I overshoot. I Believe it should be guiding in the same way

ILS can be turned off by the ILS volume knob

Thank you for the info :)

Yes 15-20 NM I have seen myself, but for my own curiosity do you by any chance have an AIP reference for that 50 NM or anything beyond 20 NM? Also, just to be clear when you say intercepting the ILS at 15-20 was that the LOC or GS part?

You should be entering the frequency in the default window when the T-ILS page jumps up. any number with tre numbers will be entered as TCN while any number with 4 or 5 will be entered in ILS. 0 in this window will change between X and Y band on the TCN. besides that you should enter the course in it respective window. that said the bug is not that you press 0 the bug appear when you have this window selected and press enter

In RL its very few approaches with GS intercept outside 12 NM to my knowledge. So it theory yes you should be able to intercept it at 20 NM, you would probarly not fly it in RL as it might be unreliable until you are inside where the approach tells you to intercept it. Also note that glide slopes can be more than 3 degrees IRL

Tadpole should position to give you an intercept angle and bank angle guidance to the steerpoint. Now it is pegged until you pass the steerpoint and then goes to the other side, just hovering over the steerpoint instead of working like a flight director. tadpole.trk

This might be because it duals up as the brightness knob as well. I can use it with VR controllers but if i press it, it changes to adjusting brightness

This should be moved to bug section, just tested it and yes the TACAN behavior is off. The ILS is sluggish but it works and I am not sure if there is a fault with it without more testing

This shows how the frq should be entered first and then I move the rocker and press ENTER and the game crashes

Seems to happen the second time you hit enter button after trying to select a freq. moving the rocker down to the FRQ window of the DED T-ILS. I know you should enter the frq in the numpad/area which is highlighted at the start but the bug is relatedtot the FRQ part of the DED eg moving the rocker to FRQ and then pressing enter. So in essence the bug occurs since ppl are trying to insert the frq in the wrong part of the DED

Track file added

If MRM mode has been activated or AIM-120 selected in A-A mode. DGFT Override mode will maintain AIM-120 selection instead of selecting SRM (AIM-9) by default.

Not sure if this is a bug but: After using DFGT mode and HMCS I would still get sidewinder tune when it was pointing at the sun after going back to NAV mode. There was no Sidewinder or HMCS boresight symbology present. Happend on ACM 2 vs 1 instant action. will test more modes and update Sidewinder sound and dfgt mode.trk

I don't know. I will have to investigate further, but there might be others here who knows

I believe the F/A-18s had Link-4 (TADIL) earlier.

In the first mission for the UH-1 UN mission they call that the wind is 280/X when you are comming in to land. in reality the wind is comming from E as seen on the windsock and would correspond with the "tailwind at altitude". Now I find this really confusing. Real world aviation always calls wind in the TRUE direction it is comming from. Also is it possible that ATC always state wind when given cleared to land?

I would almost call that to be two bugs. 300nm range on a ship TACAN is further than the specs should warrent. Both in the power availability, and tactical consideration for that range and also the fact that unless you are flying at above 50,000ft you will not have Line-of-sight to that station. But I can also concur that I have suddently lost the TACAN channel from the Ship either after landing or take off or comms with the ship.

I understand that in a event where it is coordinated how people enter this might be a good option. But for other multiplayer servers there might be other needs and I would like to add another option which would be to have aircraft spawn on all elevators. But there has to be a limitation with that spawns are disabled for an elevator if any aircraft taxi within the frame of the elevator, which after all is very easy for everyone to see. Another option would be to have spawning at elevators 2,3,4 while leaving the area between 1 and 2 and elevator 1 for rearm and refuel. (It seems to be the largest space that would be rendered useless if all elevators were spawnable.) The reason is that when you start cold it would take many minutes before the next person could spawn in and this would create a low sortie rate/ launch rate unless everyone land to rearm and refuel. One thing I would like to add as something I would like to see, since we are seeing a lot rubberbanding deaths on joining, is; When you have your chocks on the server desides your location and basicly lock you to the fixed position on the carrier as if you were chained to the deck. Once you remove the chocks the transfer to the client happens.

Actually, I would call it a bug, but only from a catapult. I don’t believe there is a shooter in the world that would launch a Hornet with a pilot in it before he unfolded and locked his wings. Aerodynamically it might just be the biggest winglets to wing configuration in the world. After all the most efficient wing would be circular.

I acutally think ED did a good move to only limit spawn to two points at the catalpults. If its meant for MP you might have someone landing and that would render Cat 3 & 4 occupied for the landing pattern or someone would spawn in where someone actually was landing. I'm sure ED are working hard on this and will give us a good solution My observartions so far is that there seem to fit 2 Hornets on each elevator(with wings folded) and, if they decide to go for it, that should leave 8 spawn points for MP with a clear red line that other can see where people will spawn. So maybe this could be an option?

Correct. you can see what it is with the sign after the numbers. N65°25.5' would be decimal minutes as depicted by ' N65°25'30" would be in degrees,minutes and then seconds. both of these coordinates are the same Latitude.

https://www.colorspire.com/rgb-color-wheel/ If you change the 3 first values and add them in the order top to bottom(RGB) you can check what color you will get and change it to your desired color :)

I have seen this myself and it seems you have to go in and edit waypoint 0 "Advanced waypoint action" options after you have added the TCN to get it to work.

The confusion here is that the ADF in the Hornet doesnt work With NDB but With VORs. which I must admit I would like to check further as their Properties are different and the VOR actually sends out radial information while the NDB gives out the same onmidirectional signal. In other Words: You should not be able to tune NDB or their frequencies in the Hornet. You can however use VOR frequencies and navigate to them. Wags: is there a plan to implement that you can use the paired freq from a DME in the TCN to get range? http://e-haf.org/PublicFTP/320/UPLOAD_FOLDER/Charts/VOR%20Frequencies%20to%20TACAN%20Channel%20list.pdf Edit: to remove the noise after selecting a radio as ADF, click the radio button to Select it and then press squelch to reselect squelch.