Just a normal workday in the Harrier...

Holbeach · March 10, 2019

The people saying "yea asl is bugged but its fine anyway" No. Thas not an acceptable answer. It should work correctly.

Is there anybody actually saying that, or did you just make it up?

Why would anybody not want it to work correctly?

..

Jester986 · March 10, 2019

Isn´t that great?!
Tho not at all surprising; I´m just that good.

The ASL line was never working correctly. Still, anyone should be able to fly a straight line at a given heading, that´s just basic airmanship.

People ask the Devs to deliver the most accurate and realistic Simulation ever - only to use it in the most inaccurate and unrealistic way possible.

Yes, the ASL is broken, but that's never prevented me from putting four GBU-12s down the TC hatches of four tanks.

Where was I smug?

Just because I don't have problems using the ASL line doesn't mean that hundreds of other Harrier pilots don't as well. (I jester986 messed up the qoute here. It was nealius)

Is there anybody actually saying that, or did you just make it up?
Why would anybody not want it to work correctly?

..

Mech · March 10, 2019

There is something definitely fishy going on with the Harrier. On the discord channel is all fine and cute as long as the chat is about "can i press action down for this..." or "here is a nice picture". If a more on the subject question pops up about the Harrier its almost guaranteed that it will result in an allergic reaction. Witnessed one just yesterday. And the question was raised in the most polite way possible, so no, the "you were rude , that's why you got what you got" line doesn't hold any water.

Plus there is a strange pattern, if you look closely.

Heavy debate about ASL behavior for months, asking for a fix -> Switches got updated. Never seen anybody to complain about switch behavior.

Tpod broken for a year now -> we got Betty.

3D model has several issues in the front part (not even acknowledged by the dev team) -> what you will get? new textures for the joystick in the cockpit.

So yes, work is ongoing on the module, but nothing essential, only cosmetics.

Maybe somehow the Harrier code doesn't fit in the DCS world, and they need to wait until becomes possible? Maybe the early access was too...early?? This puts them between the hammer and anvil.

Anyway, i dont't see it finished in the foreseen future. (God i hope, I'm wrong).

Harlikwin · March 10, 2019

Code wise nothing on the harrier is inherently more complicated than the hornet, in fact most systems are simpler or identical between the two. In fact they get code from ED for things like the tpod as i understand it. Maybe they should just outsource the coding to ED.

Nealius · March 11, 2019

Oh for ****'s sake. I say there's a work around for one bug and suddenly the other five user-error issues are invalid? I'm done with this dumpster fire of a thread.

Edited March 11, 2019 by Nealius

arturojgt · March 11, 2019

I was able to drop 14 gbu with the tpod, after the the 5th didn’t picked up the original laser code so for the 6th I changed to a different one and works perfectly again.

Killing time in the bathroom, honey bring me some matches...fewwwwww.

toilet2000 · March 11, 2019

User made mistake by pressing TDC. Just slew the TPOD over to the target area and leave it.

According to the TAC manual (TAC-000, 1-386), you are wrong as it is not a user mistake. TDC pressed down should simply set an aircraft designation, leaving the TPOD format page. It should never revert to the DMT page.

User not flying correctly with asymmetric loads. I have no problems with enough smash and avoiding certain high-G maneuvers.

According to real world AV-8B pilots, asymmetric loadout should be hardly noticeable, apart when landing.

Yes, the ASL is broken, but that's never prevented me from putting four GBU-12s down the TC hatches of four tanks.

GBUs maybe. But the AV-8B N/A was used as the dumb bombs truck. Because of the ARBS, it was often more precise than AV-8B+ with radar ranging and was the preferred aircraft for delivering dumb bombs. With the ASL we currently have, that's a big problem.

I have no problems lasing four GBUs. If you're carrying any more than four you should go back to Ace Combat.

Doesn't matter how many GBUs you have, it's a matter of time with laser on. The Lightening should never overheat, and in the rare case of a failure and overheat, the "flashing L" would not stay on.

Now that part about Ace Combat: c'mon dude, what's with the attitude... And anyway, TERs rack and GBU-12 loadouts are certified, according to said TAC manual (2-38 ).

User failed to set Chaff release to 'P' in the EW page.

The default Chaff setting (I think it is "S") should still release a Chaff, just not a "Program", but a "Single". Again, no user error here, simply a bug.

Good job on trying to discredit OP though. I do suggest you do some research beforehand.

viper2097 · March 11, 2019

Thank you toilet2000, you nailed it.

However, I'm surprised that there are really so many people who say that the mistake is by my side or that everything is fine. I'm still able to do AAR and drop bombs with a broken ASL, but that does not change that fact that something is bugged.

For that people, I would like to sum up something:

Bug 1: As toilet2000 mentioned, pressing the TDC should not return you to the DMT. However, the problem is somewhere else:

Slew the designator with the TDC buttons and you will notice that all info (like coordinates) is missing while slewing. As soon as you stop slewing and the pod stands still, this info is shown again. Then it works and targets are designated correct.

When using an axis to slew, the pod gets stuck in the slewing state and as slewing already stopped and the info should come back again, it does not.

So it is not possible to designate any targets when slewing with an axis. The pod does not recognize when you stopped slewing and when you press tdc action, it goes out to the DMT.

So, this is clearly a bug, or better saying two. No fault on my side.

Bug 2: Slewing with an axis still does not work. It does not processes the input commands correct and sometimes it works and sometimes it does not.