Jump to content

Recommended Posts

Posted (edited)

Hi,

I am having this repeating problem with ACLS needle off to the right, although pilot reports needles ON and ON.

It actually is off the left when over the deck resulting in bolter. I have this every single time.

See my track; attaching mission too.

on version Openbeta 2.8.4.39313

image.png

 

CASEIII_ACLS_OFF_BOLTER.trk Test Flight F-14B Guam - ICLS ACLS.miz

image.png

Edited by Shaman

51PVO Founding member (DEC2007-)

100KIAP Founding member (DEC2018-)

 

:: Shaman aka [100☭] Shamansky

tail# 44 or 444

[sIGPIC][/sIGPIC] 100KIAP Regiment Early Warning & Control officer

Posted (edited)
3 hours ago, Shaman said:

Hi,

I am having this repeating problem with ACLS needle off to the right, although pilot reports needles ON and ON.

It actually is off the left when over the deck resulting in bolter. I have this every single time.

See my track; attaching mission too.

on version Openbeta 2.8.4.39313

 

First thing I would check would be for gyro drift.  In level, unaccelerating flight, you can look at your right knee area at the little line indicator with a round button next to it, it should be pointing straight up, or you can also look on your radar display - you are looking for a steady IM on the right middle.  If it's flashing IM / MG (don't quote me on those) you need to press the little round button and align your compass card.

From the screenshot it's not possible to see where your switchology is, but make sure datalink is set to the carrier, and the TACAN / Destination / AWL/PCD button should be on AWL/PCD.
And the two AWL switches for HUD and VDI should be in ACL.

Cheers,

Edited by cw4ogden
Posted

Hi, I have tried your suggestions. I have checked the little line indicator, it is straight up. I have attached also track and mission file to my post so maybe have a look on it? Thx!

 

51PVO Founding member (DEC2007-)

100KIAP Founding member (DEC2018-)

 

:: Shaman aka [100☭] Shamansky

tail# 44 or 444

[sIGPIC][/sIGPIC] 100KIAP Regiment Early Warning & Control officer

Posted (edited)

@Shaman

Ideally it's preferable to solve a problem without investing an hour into downloading a track and going thru every detail.  Most problems are little user errors.
Add in the fact track replays are sketchy at best, I was hoping we could find an easy fix.

In your case, since you confirmed it's not the easy stuff, I just spent the hour, coupled with writing this, it turned into two. 😆 
Here's what I found:

Two of four replays I watched, you just fly into the ocean. 
Nothing you did, in fact, the first replay was exactly as you described.  But that's why many aren't willing to review replays.  It's difficult to get much more from a replay that a few questions can't solve.  And they can bug out.  Twenty minutes of my morning was watching replays that ultimately just crashed into the ocean, a 50% failure rate which is impressive in and of itself.  Probably time compression related, but no useful data obtained from those.

With all that said, I can find no significant user errors you made that would account for the needle indications.  

After watching your replay all the way to the deck, I took control on the 2nd of the four replays.  I was curious if engaging the system later, i.e. closer to the boat or if having centered needles at the beginning would help.   Neither did.  

Watching the one replay that worked, and flying out of another replay: Same needle right all the way to the deck indication.  I did not bolter, but I suspect that is purely the luck of draw on the auto-throttle oscillation cycle.

Next I checked a couple of youtube videos to see if maybe it was always like this.  No.  Many videos show it clearly holding centered needles right up until crossing the stern or so.
Crazy wind?  No.  The wind is neither strong, nor far off from BRC.  Your aircraft is in perfect trim.

The only other things I want to check are, is it map related?  Meaning just Marianas, or is it related to your .miz?  Meaning do you get the same result in other missions, maps?

Unless someone else sees a cause, this looks like a potential bug.  

 

Edited by cw4ogden
to include trim was considered
  • Like 1
  • Recently Browsing   0 members

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