After upgrading my project from 2023 to 6.3, I immediately noticed that there is a significant screen tearing both in scene view and game view both during edit mode and play mode.
When I enabled vSync option in Game view settings, this time there happens to be a huge mouse input lag. When I drag my game map around via mouse, it moves significantly late.
When I go back to 2023 and enabled vSync option (which is not necessary because there is no screen tearing in 2023) it doesn’t cause input lag.
Can you please check this and fix it if possible? 6.3 LTS is supposed to be a stable version. Why is it still getting broken for the old and good features.
Same problem happens on Unity 6.0.61 and 2023 too when I make D3D12 the first option in the API list.
This must be a very long ongoing issue with D3D12 and/or Unity’s implementation for it. I am surprised that nobody noticed this and got it fixed over many years. The reason I notice it now is because, the default API is D3D12 on Unity 6.3.
Like I said in the other thread, there are numerous reported DX12 quirks ever since Unity 6.1 started to default to DX12 for new projects.
Currently it’s not looking like it’s a particular Unity issue but rather some incompatibility. Certain issues are very easy to explain, such as old Intel “HD Graphics” GPUs reporting as DX12 capable when in fact they aren’t, or just not powerful enough to handle it.
The rest .. mysterious to this point. What’s your GPU specs and your monitor (Hz, Gsync or Freesync)?
If you use Help => Report a bug that’ll also send your machine specs to Unity which I think is helpful in those issues.
After updating my nVidia drivers, the hub reopening problem (which I linked) is gone but this screen tearing and input lag when vSync was on problem still happens in full force.
Anyways. I can live with using D3D11 for a long time I guess.
