BarTzi

Works in area track as well. Just hit SCS twice in the direction of the pod (it will go to point track first, and then to the offset point)

JDAM symbology completely disappears when you switch the HSI to DCTR mode. Track is attached. Jdam DCTR.trk

Long pickle will lase and then fire the missile. Press it until it leaves the rail. 5 -> that's how it's supposed to work 1-4 -> I have no idea.

Because the pod has to lase first.

Or, you can hit pickle one time and hold it until the missile leaves the rail. Both methods work.

That whole 'caps lock to make my point, in case it isn't obvious to you' doesn't make you sound much older than him. Even though you do have some valid points.

We have more than a few weapons that share a very similar designation (the difference at times is one letter). This can cause confusion when using the mission editor / rearm menu, especially for new players, and especially in cases where that one letter is the difference between an anti-ship missile and a man in the loop cruise missile. My request is to consider adding the weapon name to the designation of some weapons. I'm specifically talking about AGM-88C,84D,84E (and 84H). It would really help if the names followed the designation (AGM-88C Harm, AGM-84D Harpoon, ADM-84E Slam , and so on).

+1

It seems to be consistent with the following (still need to do more tests): The position in which you start a 10 degrees nose down descent, to fly over the TACAN at around 2,000 feet. Edit: My bad, not consistent at all...

Ah, now I understand what you are saying... I'm sure ED will consider changing this if it's accurate and if sufficient documentation is provided.

The device mounted on the nose of the bomb to help it track the laser (called CCG), restricts the usage of the nose fuze. I don't think it even exists on laser-guided bombs (I have charts showing the assembly and no mfuze is shown). They all have electronic fuzes placed near the tail of the bomb. So in our hornet, if you set Mfuze to anything other than off, you are asking the system to do something it can not.

You can't turn on something that is unavailable. The CCG precludes the usage of the nose fuze.

All of the changes should be applied only to the description.lua of the livery in question. I attached the description file to my post. It's really just a simple copy-paste of the arguments to the end of the file. It would be easier to contact the original creator and have him update the files. description.lua

Bunny Clark and Santi - thank you very much. You learn something new every day. Why can't you slew the radar cone sideways in that mode, is it a limitation of the hardware at the time, or something that simply was not needed?

Great, then that's a bug. Thanks for confirming. Do you know if the scanned zone should center around the TDC?

Fair enough. Can you designate a location outside the cone?

Trying to figure out if I'm encountering a bug, or if the A/G radar is planned to work that way. 1. In A/A mode, you can't use the radar to lock anything outside the area that you are scanning. This makes sense. However, in A/G mode, you can 'lock' a target outside of the radar cone (when scanning less than 120 degrees). How is this done, and is it even possible? 2. The cone does not center around the target you marked. This means maneuvering the plane can move the designated target outside of the area the radar is scanning. I understand this is something you can't compare to STT mode (where you continuously have to update target parameters), but I'm wondering if that's the way it's supposed to work? 3. Finally, should the cone center around the TDC, allowing you to slew it left and right? Currently, it's centered on the nose, and you can't move it sideways.

Radar scanned elevation, which is presented above and below the cursor (| |), now changes as the radar goes through each individual bar. This will occur in A/A mode. A track is attached. Radar elev.trk

Hook bypass goes to carrier automatically when you deploy your hook, so to be more accurate: Hook bypass to field will make the AOA indexer not blink when you try to land without the hook deployed.

Are you sure about that? Custom made bort number on a tail that isn't gray.

Post your lua file so we can have a look and tell you what to change. If you are not the maker of that livery, check the user files section incase the creator updated it already. If you didn't read it by now - here's the official explanation on how to change it: https://forums.eagle.ru/showpost.php?p=4341890&postcount=72

I swear there's a cruise video out there where they use a similar display to play clips from top gun.

Feel free to share your original comment :)

To everyone who complains about it. I made the IAF liveries, and I'm grateful for that change. It allows for more flexibility and realism when creating export (and also USAF aggressors) versions of the liveries. Livery makers should accept the possibility of changes to the 3d model, especially during the early stages of EA. Those liveries have to be properly maintained over time, just like pieces of code.

Have you played OB since 2.5.6? You should be thanking them, trust me. There was a massive performance hit, 2.5.6 issues, carrier issues, and so on.