Jump to content

Recommended Posts

Posted
Ah, it should display whenever pitch trim is changed, stay for 3 seconds, then declutter.

Yep, just noticed. Comes back up also at pitch change, its improved I think. Don't really need it but its OK.

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted
Yep, just noticed. Comes back up also at pitch change, its improved I think. Don't really need it but its OK.

 

Are you guys on the same channel?

@ majapahit: What version of DCS Hornet are you talking about. I don't ever remember seeing the 'aoa preset" readout in any build. Perhaps I wasn't paying attention.

Posted (edited)
.. @ majapahit: What version of DCS Hornet are you talking about. I don't ever remember seeing the 'aoa preset" readout in any build. Perhaps I wasn't paying attention.

DCS F18 is now 2.5y. I can remember AOA popped up in all kinds of different ways during this period, coming and going erratically did not make much sense periodically, so not much use to that and I started to ignore it. It's in the HUD of course, the alpha-thing number, that sometimes shows, or not, disappears unrequested, and appears equally uninvited, and repeats this several times in fast patterns.

The E-bracket is a lot more useful of course, and else when your descend angle is 3° and you onspeed AOA supposed to be around 8°, thus your W should be on the 5° bar, while your VV is pointing on the deck -3°, which is actually the right measurement to make per how the designers and test pilot godfathers proscribed the trap angle.

Edited by majapahit

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted
DCS F18 is now 2.5y. I can remember AOA popped up in all kinds of different ways during this period, coming and going erratically did not make much sense periodically, so not much use to that and I started to ignore it. It's in the HUD of course, the alpha-thing number, that sometimes shows, or not, disappears unrequested, and appears equally uninvited, and repeats this several times in fast patterns.

The E-bracket is a lot more useful of course, and else when your descend angle is 3° and you onspeed AOA supposed to be around 8°, thus your W should be on the 5° bar, while your VV is pointing on the deck -3°, which is actually the right measurement to make per how the designers and test pilot godfathers proscribed the trap angle.

 

So you're talking about your actual alpha readout that shows anytime you're outside of the bracket limit which is correct behavior (in PA mode).

I think FightsOn was referring to "desired AOA" display that pops up in the right bottom corner of the HUD whenever the trim hat switch is pressed. Say you've just rolled out on downwind with gear and flaps with lots of extra a/s, you can press the trim switch and watch the target AOA numbers scroll up to... 8.1 (if that's what you want) The FCS logic will not make you balloon to this value immediately (same goes for flaps:smilewink:) It all happens pretty smooth from what I hear. One you're within onspeed parameters the alpha value on the left side of the HUD disappears (you're within AOA bracket)… all is left is power control and bank with occasional tap on the trim if required. if you get wild with the stick and fall outside of the AOA bracket, the alpha on the left of the HUD shows up.

Posted
So you're talking about your actual alpha readout that shows anytime you're outside of the bracket limit which is correct behavior (in PA mode).

I think FightsOn was referring to "desired AOA" display that pops up in the right bottom corner of the HUD whenever the trim hat switch is pressed. Say you've just rolled out on downwind with gear and flaps with lots of extra a/s, you can press the trim switch and watch the target AOA numbers scroll up to... 8.1 (if that's what you want) The FCS logic will not make you balloon to this value immediately (same goes for flaps:smilewink:) It all happens pretty smooth from what I hear. One you're within onspeed parameters the alpha value on the left side of the HUD disappears (you're within AOA bracket)… all is left is power control and bank with occasional tap on the trim if required. if you get wild with the stick and fall outside of the AOA bracket, the alpha on the left of the HUD shows up.

This sums up theory nicely about how things can workout according to the supposed design, but practicing trap, launch, bank left, go 600ft 220-250kts 0.9 DME abeam, break base, merge groove, this is not quite how this works out, neither the HUD read outs, neither 'the FCS will take care of things' (sometimes it does). 'Only use throttle and bank' that also is theoretic flying of numbers, but actual footing on YT pilots performing a fast break, nope that's not how you fly an in-a-hurry.

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

  • Recently Browsing   0 members

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