Jump to content

ASL behaving strange


Flagrum
 Share

Recommended Posts

Before the latest patch, the ASL moved to the opposite direction of where you would have to steer the aircraft to. This seems to be fixed now, thank you Zeus!

 

But ... it is still not really working as it should (I suppose). Now, after the patch and after applying the HUD lines quickfix, the ASL moves in the correct direction, but is (and probably also was already before the patch) somehow strangely related to the banking angle.

 

If I follow the ASL with my FPM - and therefore have to bank a bit - the ASL moves further out. So, "chasing" the ASL makes me turn further and quicker away, the more I try.

 

See the screen shot: target is to the left, but I am still supposed to bank right - but will never catch the ASL as I am off target eventually.

If I level out, the ASL moves back in direction to the target and once I am completely level - in case of the example of the screen shot - the ASL coincidences with the target, but ofc left of my flight path.

Screen_171216_090154.png.6f5b0c8920a056fc9043992c79c714d3.png

Link to comment
Share on other sites

Looks like it's still attached to the wrong point, it should be perpendicular to the horizon at all roll angles while not leaving the target diamond.

Might be why the release cue is also misaligned.

It actually is always perpendicular to the horizon, but yes, if it were connected to the target diamond, it would indicate where to fly to, even if the target disappeared beneath the nose. That would make sense, I think.

Link to comment
Share on other sites

  • 1 month later...

I would love to see this bug getting some priority ... ;-)

 

Especially when using the TPOD, this issue makes it almost impossible to drop bombs somewhere near the designated target. The added flexibilty of the TPODs gimbals is somewhat nullified if you can not really line up with the target. Any bank angle > a few degrees makes the ASL appear at positions on the HUD that have nothing to do with the actual target. That makes it almost impossible to perform a turn, using the TPOD pipper as cue, in order for a proper line up. You always turn too far ... or have to turn sloooooooooowly, degree by degree ...

 

Please, some love for the ASL cue! :D

Link to comment
Share on other sites

The ASL bug will be dealt with as soon as possible.

I am collecting all available info, basically you tube videos, to determine how it really works, specially during heavy maneuvers.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

Thank you Zeus!

 

Granted, I am only an armchair pilot, but after I read through the chapter 2.5.1 AUTO Delivery Mode of the NWP 3-22.5-AV8B Vol.I, I am somewhat confident that the ASL just needs to be attached/go through the designated point cue of the HUD (and stay perpendicular to the horizon, as it is already today. No complicated swinging or swaying of the ASL neccessary - just roll-stabilized.) While this behaviour is not explicitely stated in the manual, it just makes sense, imo. And all pictures depicting an ASL have it all showing it going through the designated target point.

  • Like 1
Link to comment
Share on other sites

  • 3 months later...

After the 2.5.2 patch it seems, as if the ASL behaving a bit better now. It is not so finicky anymore to line up properly.

 

 

[edit: take my follow up posting below into account when reading this ... seems that I am wrong in this posting!]

 

 

But ... still ... it seems that there is a dependence on the banking angle of the a/c. The position of the ASL is different at different angles of bank: the steeper the bank, the bigger the distance ASL - Target point.

 

And that relation seems not to be linear - small bank angles produce only tiny derivations, but anything greater than 10°...15° and the ASL is hundreds of meters off and swaying even to the opposite side of the VV (should always be between designated target and VV, no?)

 

I am not sure, if the ASL shall work as a flight director that leads you smoothly to the desired azimuth, which would allow the ASL and designated target to separate (until getting closer). Or if it just points you where the designated target is - i.e. the ASL stays connected to the desig. target all the time.

 

But anyhow,the dependence on the banking angle seems wrong.

Screen_180526_172803.png.4831b332550443cb8073832406d90b18.png


Edited by Flagrum
Link to comment
Share on other sites

ASL behaving strange

 

I agree. It seems any amount of bank while tracking the ASL makes it swing in the opposite direction of bank or incorrectly cue the correction. That makes any corrections by the pilot extremely difficult especially when tracking in close to the target. Further out its easier because you can see target designator diamond. The ASL should always be perpendicular to the horizon and should steer the pilot towards the diamond. The behavior is better, but still not home yet.

 

 

Sent from my iPhone using Tapatalk Pro


Edited by Eagle7907

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Link to comment
Share on other sites

I tried it out in the A-10C:

There the ASL is also not fixated at the designated target point and actually behaves similar to the ASL of the AV-8B! That includes also the dependance on the bank angle! Larger angle results in a larger displacement of the ASL, up to the point where it is show on the opposite side of the velocity vector (i.e. tgt - VV - ASL).

 

So my assumptions that

 

a) the ASL location may be depending on the bank angle, and

b) the ASL should always be located between target and velocity vector

 

are seemingly wrong / not necessarily feasible.

 

One thing I did notice though where the AV-8B ASL behaviour still seem to differ significantly from that of the A-10C. The ASL displacement related to the bank angle seems to be limited. It never happened that the ASL swayed to the edge of the HUD just because of the bank angle. It always stayed within maybe 20% of the HUD width away from the designated target point. This limited displacement then was also responsible for a way smoother and easier trackable movement speed of the ASL. Maneuvering did not cause so much swaying left and right and left and right of the ASL.

a10c_asl.jpg.a6362eb4ba154acd78baabe5b631c2ab.jpg

Screen_180527_002237.png.bf0c1c5c6b103a32b55c46e7275ae9df.png

Link to comment
Share on other sites

Yeah you’re right. In my head I was thinking ‘no wind’. That’s the only case where the ASL would be over the target. But both of your examples show the ASL perpendicular with the horizon and doesn’t wildly swing out of view when correcting/tracking to target. How can a pilot properly gauge correction needed when the ASL disappears?

 

 

Sent from my iPad using Tapatalk Pro

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Link to comment
Share on other sites

Yeah you’re right. In my head I was thinking ‘no wind’. That’s the only case where the ASL would be over the target. But both of your examples show the ASL perpendicular with the horizon and doesn’t wildly swing out of view when correcting/tracking to target. How can a pilot properly gauge correction needed when the ASL disappears?

 

 

Sent from my iPad using Tapatalk Pro

Wind has nothing to do with anything here, I think. When flying level, the ASL actually overlays the target point perfectly in the AV-8B, even with crosswind.

 

 

Also, the ASL does not disappear, but can move to the very edge of the HUD FoV. Depending on your baning angle, that can mean that you onls see a small bit of it, clamped in some corner of the HUD. In the A-10C this effect is much reduced, as the total displacement of the ASL has a maximum which is a good way inside the HUD FoV.

Link to comment
Share on other sites

  • 1 month later...

The ASL should not move if you bank and keep the VV in the same spot (i.e. no back pressure on the stick). It is almost impossible right now to correct to an ASL from a tip in because as soon as you roll out the ASL moves with the roll. Hopefully it gets fixed, as it should be independent of roll.

Link to comment
Share on other sites

  • 4 months later...
The ASL should not move if you bank and keep the VV in the same spot (i.e. no back pressure on the stick). It is almost impossible right now to correct to an ASL from a tip in because as soon as you roll out the ASL moves with the roll. Hopefully it gets fixed, as it should be independent of roll.
Exactly. I'm able to use AUTO delivery rather accurately so long as I can see the target, VVI, and ASL in the same FOV. It's more just flying the the VVI over the actual target. Make a correction, roll out, check the ASL then make another correction. But the ASL does need to be fixed.

 

Sent from my SM-G960U using Tapatalk

Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift

Link to comment
Share on other sites

  • 4 months later...

In the next patch?

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...