Lord Vader

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.

Hi @Beciak As I can't reproduce this issue, this can be caused by a local setting. That screen resolution, is it the same in Windows? Have you tried other resolutions? It seems a bit small to me. I would also remove reshade for your tests and try again if changing resolutions doesn't do much.

Hi, @DmitriKozlowsky I don't think you truly need to buy Track IR or a VR headset. It is, however, recommended if you are using a system like the Helmet Mounted Display, since it requires a head movement in the real aircraft to provide proper tracking. In fact, this is how the AH-64 helicopter was designed and the reason it doesn't have a traditional HUD. But, like others here have suggested, you can align the IHADSS boresight using the camera translation movement. So it is possible to correctly line up the sight for the HMD without a headtracking device. So, there isn't really anything to correct, you just need to align your point of view and the sight itself, in your case using the key @Floyd1212suggested.

@DarkSideMaster I was intrigued with what you said about the manual not referencing this, because I was almost sure it did. Please check page 407 of our Early Access manual: Again, we may consider a refinement for this explanation, but it is referenced correctly in the manual.

Although we may consider a reference in the manual regarding parallax or other limitations, it is common sense that sensor operation need to take this into account. The sensors are not positioned in the same spot on the aircraft, the TPOD is set up on the right chin hardpoint, while the Mavericks are on the wing pilots. They will have different perspectives if you align too close. And that will add up if you then aim in longer distances afterwards. The consideration must be: at what range will I fire a Maverick missile? Certainly above 2nm. So that's where my alignment focus must be.

Hello @DarkSideMaster What @razo+rsaid is true. You do need to have a considerable distance from the aircraft to your selected TGP point in order to align the boresight properly. It is advised to choose targets above 2nm to align the boresight (airborne or on ground), anything below that may have a considerable error. If you still believe you're making a correct alignment above 2nm, please share a track for our analysis. The parallax effect is a realistic feature of our simulation. It will not be removed unless the laws of physics change in our reality.

Hey @Lekaa Like @Tholozor said, this does seem to be a gimbal limit situation. It doesn't look like an error. However if you have public information to support the idea this is a bug, feel free to send it via DM to @BIGNEWY.

Hi again The "FUEL XFER FAILURE" bug is known but thanks for referring to it. We'll look into this external fuel tank item a bit further. Thanks for your patience.

Hi @Antix70 I too cannot replicate what you are referring to. I suggest you run a repair on your DCS World installation. If the problem persists, share your track file with the issue for further analysis.

Hi @gdotts As much as you can explain with words, we would rather see it happening to understand what the circumstances are. For that, we require a track file with the alleged bug occurring, something short to demonstrate the potential issue. That being said, like others have mentioned, do not operate the power levers in flight. I would suggest you try to fly with that axis disabled and report back to see if your problems persist.

Hey @Gunslinger52 Your "hilltop" is at 7000ft! It's a bit high for normal startups. But we'll get back to you after some further analysis.

Hi @nyanrata I have raised this for internal analysis. Even though I was able to reproduce this, it's good practice to include a small track of the issue to allow us to review the bug and your operation. Thanks.

Hi @GumidekCZ We are aware the EPU isn't currently working as intended. We are still working on it, including Hydrazine consumption. We should consider these non-normal procedures as work in progress for now. Thank you for your patience.

Hi @PlaceboC6 We are already aware of this bug. It's reported internally and will be addressed in the future. I am requesting a merge of this report with the original one. Thanks.

Hey again @Altair89 Alright, this is something else. I can indeed see an issue there. I've raised this internally for analysis.

Sorry, nothing new to report so far. It doesn't mean we're not looking into it, just means it's still under investigation. Some items take more time than others and sometimes they are waiting for other items to be improved. If anything changes, you'll certainly know in future changelogs.

We will need to take a better a look at this. Thanks for letting us know.

Hi @Ergo 1-1 Sharko I am a bit confused with what you are describing. What is reported is the fact that system tracks are being dropped too easily in STT, especially in ACM modes. This is still being addressed internally. Although the bug may interfere with BVR modes, you're referencing something different. You're talking about the "data ageing" setting, which is something different. Observing your track, you lock the target with TWS and crank to the left, losing that system track. when you return, however, you're at 80nm range scan, when the target is about 90+nm. I took over then and was able to observe the brick in position. Note that you can see the "memory" track and the new ping from the first sweep, creating "two" contacts: I was then able to lock again as a system target with TWS, unlock it, crank again, retain target general position in memory within the 32 seconds setting and recovered it once more. What am I missing here? Thanks.

Hi @Atazar SPN The pilot model for the F/A-18C is being updated. When the new model is released, we'll revisit all stages, including the ejected.

Hi @ContraStorm I am unable to reproduce the issue as you mention it. I would suggest you run a repair on your system as you mention you haven't played DCS for a while. Also make sure to temporarily remove any mods you may have and try again. After that, try again. If your problem persist, please let us know.

Hello @Altair89 What do you mean "not working"? The missile doesn't retain desired altitude prior to impact? Can you supply a track of the engagement and describe what doesn't work?

Hey @ThoWmas31 We will require a track to understand what you are doing. However, have you tried to press CZ on the TPOD after the target creation on the FCR? Regarding that second observation, when in CCIP the TPOD will cue to the pipper, not to a steerpoint or target point. In this case if pressing the CCRP option cues the TPOD, it's working as intended and it's not a bug.

Hi @OldFlyer I was going to suggest a repair for the Maverick issue. Good thing you did it and solved your problem. Regarding the snowplow feature, you said it yourself that you haven't flown the F-16 for some time. The Snowplow logic was updated and improved. Some of the TPOD functions still require some additional system logics that are still being worked on incrementally. But we are confident this is working much closer to the logics of available documentation. Take a look at my comment here, it should help you understand how it works now:

Hola @Atazar SPN I have raised this internally for a future fix. It will be a low priority item, though. Muchas gracias.