Tusky

Oh well, I remember listening to Dino's interview in October 2020 and to this point, a few more weeks do not make a difference. They may as well tweak and correct last minute bugs in the meantime. The interview is here

I believe the 339 will be released in conjunction with the next open beta update...not before next month I'm afraid.

Wind on deck is a trigonometry problem and it is up to you to decide what parameters to use. You can use this link https://www.calculator.net/triangle-calculator.htm where: Angle A: angle of relative wind calculated from BRC Angle C: angle of wind calculated from BRC (actually it is 180°- angle C) Side a: speed of relative wind Side b: ship's speed Sice c: speed of wind Example: Relative wind direction: 9° left of BRC (this way the relative wind will blow down the runway centerline) Relative wind speed: 27kn (headwind - between 25kn and 30kn) Ship's speed: 15kn Using the link above: Set 9° on angle C (upper angle) Set 27 on side a (right side) Set 15 on side b (left side) Press calculate The result is (to be set in the mission editor): Wind speed: 12.4kn (side c) Wind direction: 180°-160 = 20° to the left of BRC (180°- angle A) You can also use: - a piece of paper, a pen, a ruler (e.g. 1cm=1kn) and a protractor - the wind side of a flight computer

Hi all! When setting Chaff/Flare to 90/30 on deck, the figures I get in the SA and EW pages are 88/28. Am I missing something? Thank you!

Yep. Disappearing as soon as you are overshooting (on the right side of) the centerline. Maybe related to some ICLS parameter which was introduced a couple of patches ago?

Issue still there after the latest patch. Very easy to reproduce.

Last time I checked, the ADV-RSET on the left DDI was removed by selecting the BIT page on the right DDI (but I believe any DDI would do). Do that after start-up and before taxing out. I don't know if it intended to be like that in the real aircraft though. As a side note, you may also want to press the STOP OSB in the BIT page to stop the blinking.

Flight Directory not functional. Will that affect ILS approaches or is it a differet system?

Bug still present after the last open beta update.

It is for sure related to the different position of the aircraft symbol within the compass rose in the HSI (where TAS and GS are also indicated) and SA but is this intended? When setting a radial to/from a waypoint, the switching from HSI to SA creates a significant difference (assuming the radial indication/offset on the HSI is the correct one).

Hi all! I don't know if this has been posted before or it is somehow connected to any already reported issue. Sorry for any duplication... When selecting a waypoint, the switching from HSI to SA and back shows a different graphical position of the aircraft in the compass rose of HSI/SA relative to the waypoint. This happens even if the distance/bearing to the waypoint on the upper right corner remains the same and the waypoint symbol (triangle with inscripted circle) on the compass edge does not move. To better appreciate the issue: - switch from HSI to SA and back by using the SCS towards the DDI where the HSI/SA is displayed - have the waypoint relatively closed to the aircraft I have included a track. SA HSI BUG.trk

Well, let's hope something is being done. @BIGNEWY any news from your side?

Realistic basket's behaviour would be top but for now I'd be grateful for the proposed first step... I don't think it is that hard to implement...I mean, once the drogue is connected, keep it connected until the pilot does disconnect it "voluntarily"...

Hi all! Would it be possible to have the air-refuelling basket NOT become "substanceless/aethereal" and end up in the cockpit at "refuelling complete"? I believe this issue could be solved by stopping the fuel flow at "refuelling complete" while still having the probe/basket connected in "contact". Disconnection would then be effected by the actual slowing down of the aircraft (like in an accidental "disconnect" while refuelling). Thank you!

1) Set the elevation to a reasonable value (you said something between 1000ft and 3000ft) 2) Use the TGP to look for the target 3) Designate it If the mission designer didn't provide you with exact coordinates/elevation (probably it was intended), you need to acquire the target visually (TGP or helmet) and designate it manually if you want to use GPS/laser-guided bombs or CCRP. No other way round, I believe. Sometimes you do not get all info necessary for an easy-peasy run.

I'm having the same issue and it does come back when on CL again.

It would be cool if they implemented a few shaded visors with different tints (e.g. brown, yellow, etc - the ones actually available) that you could select/install while on ground.

Hi all! I find the new kneeboard information very useful but it's not been implemented as promised in Wags' 2nd of May mini-update: BRC, final heading ("bearing" more correct) and Wind over deck are missing. Have these items been dropped or will they be implemented in the future? Thank you!

Did you select GUN in the STORE page of the DDI?

Because it is available in DCS and it is possible to install it in the real plane Not fundamental but a nice addition

Maybe announcing a release date (e.g. next OB update)

Hi all! When cold&dark, the HUD "projector" (the horizontal glass on the UFC projecting onto the HUD) has a light glow when viewed from the outside. From within the cockpit, the glass is unlit. Pictures attached. P.S. Not a game-changer but I thought I'd let you know

Hi all! As the title says, the fuel dump trail/marking of other human controlled aircrafts (leader/wingman) is not visible. Own dump trail/marking is visible. Easy to reproduce.

Hi all! I noticed that when: 1) Entering a hot plane 2) Shutting it down 3) Restarting it the FCS BIT cannot be completed and it stops at the values indicated in the screenshot here below. It happens both in single and multiplayer and with both flaps at HALF or FULL at shutdown (the latter being indicated in NATOPS).

Nothing to do with the discussion here. The turbulence is fine and to be honest, between 22-36 ft/s is significant... My post (I speak for myself only) was about the change of attitude of the aircraft just before it touches down: sudden decrese of AoA (marked by the AoA indexer) with nose going down (and tail going up).