Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Which aircraft are you using that experiences this issue?
A320neo v2
Brief description of the issue:
When hand flying an ILS approach from fully configured at 2,500’ with Auto Thrust engaged, following the flight director cues results in chasing the ILS. The flight director lags the aircraft and does not anticipate either the flight path or the pilot. This is very much unlike other airliners in MSFS, i.e., 787-10 or the PMDG 737.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Get established on an ILS from IAF in managed modes. Configure the aircraft for landing. When fully configured, but no later than 2,500’ disconnect the A/P leaving auto thrust engaged and hand fly the approach. Watch as flying the cues lead to greater and greater oscillations similar to “chasing the needles” when flying an ILS from raw data. Indeed, the FD is perhaps too close to raw data and not really of much use helping the pilot stay ahead of the airplane.
PC specs and peripheral set up:
Xbox Series X 2TB. TM Boeing TCA Quadrant. TB VF1 Rudder pedals (all other inputs null).
Are you using DX11 or DX12?
Are you using DLSS?
For anyone who wants to contribute to this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
Are you using DX11 or DX12?
Are you using DLSS?
If relevant, provide additional screenshots/video: