BarTzi

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.

Stable should be stable... The truth is the recent OB versions just weren't stable enough. There was a massive improvement with the SC build.

The AoA brightness knob now allows you to turn the indexer off (as intended). However, it still doesn't allow you to change the brightness. This was tested using all cockpit lighting modes (day, night and nvg). AoA indexer.trk

For all of you who are having issues with bort numbers since the latest update, please check this thread and the informative comments by Dgambo (ED team): https://forums.eagle.ru/showpost.php?p=4341890&postcount=72

It's better to wait for the next update (planned for June third), to get a more complete set of explanations and video tutorials. LITENING additions are mostly the new symbology, and I bet WAGS will cover it with the next batch of changes planned for the next update (which should make the pod complete).

It was changed. You will have to move the piece at the top and have it cover the 'holes' below. See attached pic:

Updated to v1.0: -Fixed the issue with bort numbers introduced in the recent patch -Added the intake bort numbers (light blue), with a representation of the font used by the IAF (still WIP. It's very similar to the one provided by ED, except the numbers 2, 3 and 5 are different. The IAF uses a different font for the intake numbers and I'm still researching in order to get the most accurate result). -Adjusted the position of several decals including the 117th logo, which was too big. -Added a Barak 2020 version of the livery (see details below). -The bort numbers on the tail are now placed symmetrically. Before addressing the changes, I'd like to thank ED for going above and beyond here, providing us with alternative bort number positions. This will help greatly increase the realism of the liveries of the export versions. Changes to the folder structure: Each skin has a main folder (for example: IAF 101st squadron). All subversions of the skins (60th anniversary, or Barak 2020) use most of the main folder files, and their folders only contain the unique files for that skin. Ths result is a massive reduction in file sizes, but the downside is that you can't change the names of the folder (otherwise you will have to edit some entries in the description files). Barak 2020: The IAF upgraded older block 30's with an avionics suite that is on par with their latest blocks of F16's. Some planes that were upgraded in that program have an additional logo (which reads 'Barak 2020' in Hebrew). That small logo is placed on the intake, just before the bort number. Barak in Hebrew means lightning, in case you are wondering why it has a lightning symbol on it. I've decided to add a subversion of each skin with the decal for the sake of realism. It's totally optional and you can delete that folder if you don't intend to use it. A picture of v1.0 with the new intake bort numbers and the Barak 2020 decal: I plan to go over the livery pages and update them with new pictures, but I don't have a lot of free time on my hand so it will take a while.

Hi Nine, you said on discord that you are legally allowed to use the Spanish docs. I take it as the team had no access to US docs or were not legally allowed to use those. Are you legally allowed to use US docs for the ATFLIR / has access to those documents at this time, or is it still in the gathering phase?

The question that should be asked is what qualifies as good evidence here. Apparently the videos are not enough, even though I think that for a simulating a pod, youtube is a great source. I wouldn't mind as long as the pods shared the same set of features, but as we learned recently they might not.

The scratches, dirt, and weathering layers do not cover that area in the texture template, since originally that spot was mapped elsewhere. The same goes for roughmet.

Thank you so much for explaining this! I have two additional questions: 1. I'm struggling with aligning logos that cover the entire tail fin - they always seem to have an angle when covering the rudder. Do you happen to know the angle between those parts or have any tips on how to place textures that cover the entire tail correctly? 2. Will the template be updated to reflect the recent changes to the tail texture? One example is that area, which seems to be mapped to somewhere else now:

When you box RTCL it should display the reticle (source: ). When it's unboxed no reticle should be displayed. In DCS it currently does the opposite. When you box RTCL, the reticle disappears.

I wasn't expecting that. I've never seen that symbology before on a US hornet. Well, those videos don't show target coordinates and compass even when the pod points to a target. I guess we shouldn't expect those at this time. I don't think I will ever use the LITENING if it really ends up being incapable of displaying the two features mentioned above. It makes me feel bad for the devs putting their time into it.

+1

Yes: --F16_bl50_FIN_DECAL {"F16_bl50_FIN_DECAL", 0, "f16_bl50_tail_IAF_117", false}; {"F16_bl50_FIN_DECAL", 1, "f16_bl50_kil_normal", true}; {"F16_bl50_FIN_DECAL", ROUGHNESS_METALLIC, "f16_bl50_tail_IAF_117_roughmet", false}; {"F16_bl50_FIN_DECAL", DECAL, "empty", true};