Lord Vader

Awesome work, @Floyd1212beat me to it. If there's anything you need further, @Dragzor, let us know.

Good to know. Thanks.

Hi @bephanten What do you mean? The commands are there.

Hi @Dragzor Like mentioned above, we need a track to visualize what you are stating. We don't really see this behaviour on our side.

This is the wrong section. This should be on DCS wishlist. Thanks for the suggestion. I am asking for this to be moved there.

Thanks for the new images @ring_H₃PO₄, I think we got it. It's been reported, thanks.

Hi @ring_H₃PO₄ Can you specify where the nose issue is occurring? I can't seem to find it in my tests. I did however found the glitch in the left fin.

I am investigating this behaviour. Thanks for the track, @Moonshine.

We hope to have this inconvenience addressed soon. Stay tuned for future updates.

@Pyrocumulous This is really a weird find. It is my belief the next updates may bring a fix to this weird bug. Please report back if after the updates you still have the issue. Thanks for your patience and support.

As we're updating the pilot body and animations, some of these issues will be resolved. Stay tuned.

The AGM-65F lock depends on optic contrast between target and background. We require a track of what you're doing to either verify a possible bug or identify what you may be doing wrong.

Hi @dreaux88 I cannot reproduce the behaviour you're describing. Like @razo+rsuggested, check your keybinds for conflicts.

According to our documentation, it literally states "cycled from up to down to up". If you have a different phrasing from a publicly available non-classified document, please feel free to send to @BIGNEWY.

Hi @Voy We will need to analyse this internally. Thanks for bringing this up.

Hi, @Voy If you take a look at the data that is displayed on the HUD when selecting CRUISE/HOME, it's not the bullseye range. This is a different value. What you are seeing is the estimated fuel above Home point in hundreds of pounds. If you go below bingo, you should also see a "FUEL" warning on the left of it. This is correct behaviour and does replace the bullseye information on the HUD.

Hello @SickSidewinder9 Just like @Tholozormentioned, in order to have the HOME FUEL advisory removed with gear operation, a full gear cycle is needed (from up to down, back to up). Is this what you are doing? If so, please supply a track with the issue occurring and we'll take a look.

Hi @Devil-101 The RPM must reach above 20% to move the throttle to idle. The best procedure, however, is when it goes above 20% look below to the annunciator panel and check when SEC light goes out and then move the throttle lever to idle. If you do that before the SEC light extinguishes, you'll have a hung start. If you still believe there is an error in the logic, please create a small track for us to observe what you are doing.

Hi @Captain Orso I won't comment on third party logics. Regarding DCS, like it was said above, whenever you request refuelling you are opening the Rearm and Refuelling window. Therefore, when you press ok, even if you don't change the loadout, it will... rearm and refuel the plane. This instruction is meant to be simplified, to make sure the servicing is done only once. There could be changes in the future to make refuelling independent if nothing is changed in the weapon options, for example. I will pass the suggestion to the team.

Hi again. Like I said, this is all being tweaked. I believe, at some point, you will see improvements on this system and overall dynamics.

Hi @papaz I ran your track and I saw you only engage the attitude hold. I did observe the SAS pushing forward but you're not compensating the vertical axis by also engaging altitude hold while cruising. The pitch will be maintained, accelerating and adding negative VS. We need to think in three axis, not just two. Also, remember you trim to speed, not altitude. That being said, the SAS and overall autopilot systems are currently being reviewed and fine tuned by the team. Look forward to further updates.

Hi @Nealius Most of the times, most people just bump to afterburner and pick up the stick after wheels up, so maybe most will miss this difference. I believe there is something going on here and have raised this internally. Thanks for the report.

Hello @Zyll I tested your track and I can see that heavy frame drop you describe using the TV optic on the TADS in zoom mode. However, your mission here is extremely heavy scripted, I had to close several windows of non-running scripts. You say these scripts "don't affect results" but I am not sure. You see, I ran a simple mission in Caucasus, no scripts or mods, and I was unable to reproduce the issue. There was a slight oscillation when changing modes, but certainly not as abrupt and clearly not as low. What I would advise is that you try a clean mission yourself in the Caucasus as I did and check if you have the same issue without all these mods running or in that heavily loaded mission. If the problem persist, please do share a new track and we'll continue to analyse this situation.

Hi @Alpiinoo Previously, when you pressed "remove payload" in ME for those stations, it would wrongly add an empty fuel tank pylon. This was corrected some revisions ago, because the pylon is mounted with the tank itself, that's why when you jettison those stations the pylon is dropped with the tank. The current limitation of not having any weapon pylon in those stations in a "empty" configuration, reflects our documented references for weapon pylon usage. If you have other documentation that contradicts this, please feel free to send it to @BIGNEWY. Currently, the "Remove Pylon" for those stations is redundant to make sure older created missions are still compatible.

Stay tuned for further improvements in the Multi-threaded version. The wait will be worth it.