February 7, 20197 yr Anybody tried the new Nvidia driver (418.81)? Gigabyte x670 Aorus Elite AX MB; AMD 7800X3D CPU; Deepcool LT520 AIO Cooler; 64 Gb G.Skill Trident Z5 NEO DDR5 6000; Win11 Pro; P3D V5.4; 1 Samsung 990 2Tb NVMe SSD: 1 Crucial 4Tb MX500 SATA SSD; 1 Samsung 860 1Tb SSD; Gigabyte Aorus Extreme 1080ti 11Gb VRAM; Toshiba 43" LED TV @ 4k; Honeycomb Bravo.
February 7, 20197 yr I have had a problem when using G-Sync switched on in Nvidia Control Panel with my Freesync monitor using this driver and variable refresh rates. An intermittent black screen occurs for a few seconds in either windowed or full screen mode with Prepar3D v4.4. Rolling back to driver 417.71 has fixed this issue (no more black screens). There have been no such issues with X-Plane 11, however, suggesting that the issue is software dependent, i.e. an incompatibility with Prepar3D v4.4. Hopefully this will be fixed in a later driver release. Whilst on the subject, has anyone had any success with the G-Sync option in the latest drivers if using a Freesync monitor with variable refresh rates? My experience is that it has radically changed the behaviour in Prepar3D v4.4, with much smoother performance and less noticeable stuttering, although I have found that the latter is only really achieved if I have VSync on in the Nvidia Control Panel (which seems to be the recommendation of AMD in the use of a Freesync monitor). Edited February 7, 20197 yr by LecLightning56
February 7, 20197 yr 57 minutes ago, LecLightning56 said: Whilst on the subject, has anyone had any success with the G-Sync option in the latest drivers if using a Freesync monitor with variable refresh rates? My experience is that it has radically changed the behaviour in Prepar3D v4.4, with much smoother performance and less noticeable stuttering, although I have found that the latter is only really achieved if I have VSync on in the Nvidia Control Panel (which seems to be the recommendation of AMD in the use of a Freesync monitor). I've experienced the same result.
Archived
This topic is now archived and is closed to further replies.