BritTorrent

This document is such a valuable Tool, all virtual Harrier pilots should at least flick through it.

Looking good Prowler. Is that an updated HUD colour I see?

Thanks for the info. That actually sounds pretty intuitive to be honest. Just need to keep track of which grids are where in relation to you. Sent from my ONEPLUS A3003 using Tapatalk

Cool, thanks for the response. The other thing, how will we eventually enter UTM coordinates in the Harrier? The Hornet has some strange system where you have to slew over a grid to select the UTM prefix for the area you're in? Is it a similar setup in the Harrier nav system? I couldn't remember it being mentioned in the NATOPS manual. Sent from my ONEPLUS A3003 using Tapatalk

Really excited for this update. Its going to make the Harrier much more capable in its primary role. What's the maximum number of waypoints the Harrier can store in the computer?

Cheers Zeus, keep up the good work. Sent from my ONEPLUS A3003 using Tapatalk

To be honest, there are so many features missing from the RWR/ECM/CM system that it's going to need a lot of work before the module releases. It's only partially implemented. If you look at the Hornet and how the counter measures system works there, that's pretty much how the AV-8's is supposed to work. It's the same system I believe? I imagine Zeus is waiting until he gets to this to fix any bugs with the RWR.

Hi guys, The behavior for the TOO push button is incorrect. As per section 2.4.6.2 of the NWP 3-22.5-AV8B, Vol. I manual. However in DCS, when you press the TOO button it creates a target point at your exact position in space. So if you press it at 10,000ft then the target point will be at 10,000ft instead of on the ground. I've attached a track showing the behavior. I press the TOO button and when I turn around to engage the target, it's floating in the sky. Bug-Report.trk

Any feedback from ED on this? I'm willing to accept that I'm doing something wrong here, but I've spoken to several experienced mission builders and nobody can explain this behavior. I can only assume it's a bug with the AI.

Prowler I'm a bit confused about your Harrier NATOPS statement. The NATOPS version we have is from 2011. It regularly references systems that the day attack Harrier doesn't have such as NAVFLIR, radar, night vision devices etc. The TAC manuals we have talk about FLIR and radar too. Unless you've got access to even more recent documents than we have, which I accept is a possibility, I don't understand how your statement makes sense. Our manuals are very clearly written for Night Attack Harriers.

I honestly don't know why there's a release branch and an open beta branch to be honest. Release branch has the same bugs as open beta, and every module in DCS seems to be in a constant beta state anyway. I don't know why they have the distinction. Sent from my ONEPLUS A3003 using Tapatalk

Hopefully a fix for this will come with the upcoming navigation systems update. Sent from my ONEPLUS A3003 using Tapatalk

Any update on this Zeus? It's still not working.

Interesting, I've been looking for a good virtual Navy squadron. Are you guys still recruiting for Hornet drivers? Sent from my ONEPLUS A3003 using Tapatalk

What timezone do you guys fly in?

T4 is the new DCS terrain engine standard. The one that is used for all the new maps, and the 2.5 Black Sea map. The intention was that he would also create textures for the new 2.5 Black Sea map. But he's been inactive since last year so who knows. Sent from my ONEPLUS A3003 using Tapatalk

I noticed that I'm not getting the 3 digit identifier for TACAN stations anymore in this patch. I have attached a track showing this behavior. I tune into the TACAN for the Carrier on 1X, the name of the station that I set in the mission editor is C74. This identifier doesn't appear on the HUD or the AMPCD. Is this a bug, or has the process for getting this information to display changed? Bug-Report.trk

EDIT: I'll create a new thread, my issue is slightly different to this one.

Yeah, a condition of earning above a certain amount was that he'd release textures for 2.5 as well. If he doesn't and he's still took the money, kinda a scumbag move. The quote, from the front page "When the amount of donations will reach 3000 $, I will release the T4 package under the same conditions." He earned above the specified amount. Sent from my ONEPLUS A3003 using Tapatalk

Mirage still doesn't have this? I haven't flown it in a year or so. You'd have thought this would be implemented by now. Sent from my ONEPLUS A3003 using Tapatalk

Any feedback from ED on this? I may well just be doing something wrong, but I've tried multiple different approaches to stop this behavior and nothing I do works. One thing I have noticed is that it doesn't effect all aircraft. The F-14, E2 and E-3 seem to work absolutely fine. It might be something specific to the MiG-29.

Thanks guys!

Issue is still here as of the latest open beta patch.

Yeah I second this. Other aircraft will taxi to their parking spots on the starboard side of the carrier. The SH-60 just sits right there at the end of the box.

[OPEN BETA, LATEST VERSION] I've recently noticed an issue with the AI. When I have a pair of aircraft in an orbit, they throttle back to idle during the turns. This leads to problems with them staying airborne. Have a look in the first attached track file (BugReport). I have a 2 ship of MiG-29's cruising at 500kts GS and at 29,000ft. After a few seconds (the track is sped up) they turn north onto the racetrack orbit. After a few more seconds they start the first turn of the orbit. Notice how they throttle back to 60%RPM at the start of the turn. They enter the turn at around 310kts IAS and they leave the turn at about 210kts IAS. Now, because I have this flight at 500kts GS, they manage to maintain enough airspeed to continue level flight. If you set the cruise to a more realistic speed, say 420-450kts, then they lose so much airspeed in the turn that they hit stall AoA and begin to descend. Have a look at the second track file (BugReport2). In this one they're set to orbit at 450kts GS. They enter the turn at 280kts, and they lose so much airspeed they begin to descend at a really high AoA. It's pretty odd. If I only set a single aircraft in the flight, they make the turn at the correct rpm setting and maintain speed throughout the turn. This only seems to apply to multi-ship flights. I tested this with an F-5 and an F-15 as well, and experienced the same results. I've also attached the mission file I used for testing. I don't think this issue has always been here. I've been able to set pairs to orbit before with no issues. For whatever reason they just seem to throttle all the way down during the turn. Bug.miz Bug-Report.trk Bug-Report2.trk