BarTzi

That's not what he asked. I think he knows when the next update is planned to be released. What he is asking for is a mini-update. All we know is that they focus heavily on bug fixing at the moment. I don't think we should expect any major feature/addition in the next update.

I was wondering if there's anything I can do to improve the accuracy of the multiplayer tracks (replays). The problem I'm having is that my plane (and only my plane) is out of position. I know that the combat portion of the tracks is somewhat random (A/A for example), but I can't even replay a track of me flying in formation with two of my friends, because my plane flies nowhere near the original position and ends up in the ocean. Why is that happening?

This isn't an aircraft, it's a software simulating one. They have to pick a timeframe and stick with it. Everything else is outside of the scope of the program. Do you want them to never finish it?

Is that a livery you made? The background is hard to understand at first - but it's actually determined in the description.lua of the livery. Sharing the description file itself will help us point you in the right direction. That's why I asked if you made the livery. If you didn't it's best to try and contact the original creator and have him update the skin (I'm not a huge fan of modifying someone else's work like that - but that might be only me).

Did you set your T/O trim properly?

Thanks for looking into it Bignewy. Here's an additional link (VFA-113 from 2004) which shows the same behavior of the target diamond. However, due to the poor quality of the video, to notice it you have to slow the video down (X0.25-X0.5 in youtube speed settings)

"Everything is subject to change", and yet- T4 (Tiyas Military Airbase) is noticeably absent from the layout and airfield list that was posted earlier. Since T4 is well within the detailed area of the map, I just wanted to ask if there's an intention to include it with the initial release. Thank you for your outstanding work so far, Ugra Media :)

Hi guys, I recently watched a clip from Jetstream that might indicate a small error that relates to the symbology in AUTO mode. As depicted in Jetstream, the target diamond should be displayed above the release line - in such a way that the line never covers the inner part of the diamond. The following pictures from the show will help you understand what I'm talking about: Watch the places where the release line intersects with the target diamond. Additionally- you can watch the full clip here: (start at the timestamp and watch what happens as the diamond crosses the release line both when it's full and when it's dashed). In DCS, however- it's the other way around. This makes it difficult when you want to mark a new target, since the line obscures the new target position (the dot inside the dashed diamond) I know that Jetstream isn't the best source, and that you need evidence from the USN Lot20 - but I think it's worth looking into.

Tiyas military airbase (AKA T4), was noticeably absent from the airfield list. Is it a complete list of all of them?

This is one of the default liveries of DCS. I don't think you should change anything since it might break the integrity check. The best-case scenario is to wait for ED to adapt their liveries to the new bort number system they introduced. I don't think it will be too long before they address this.

I've had no issues with it. Anyhow, some tips: If you are having issues with a weapon system, it would be wise to create a track where you start from the air. You did many things unrelated to the MAV-E and I had to speed it up for a while before I reached the parts that were relevant. In the track itself, no laser codes were changed (pod is lasing at 1688, and the Missile is tracking 1111). The word CODE is flashing on the hud to indicate that. When I took control, changed the laser code, and made sure the laser was armed - it fired with no issue (long pickle).

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?