June 13, 20178 yr Hi all, On my system I Always had Prepar3Dv3 at Unlimited , vsync on , monitors at 25 hrtz and DxTory at 25 fps. Nvida CP vsync at 3D application Now with P3Dv4 My fps are at 35-60 and no difference with vsync on or off. Also DxTory has no influence on the framerate ... All suggestions are welcome. 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv. 13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degrees My flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
June 13, 20178 yr 26 minutes ago, GSalden said: Hi all, On my system I Always had Prepar3Dv3 at Unlimited , vsync on , monitors at 25 hrtz and DxTory at 25 fps. Nvida CP vsync at 3D application Now with P3Dv4 My fps are at 35-60 and no difference with vsync on or off. Also DxTory has no influence on the framerate ... All suggestions are welcome. Are you using EZCA or Chaseplane ? For reasons i dont know sometimes when i used EZCA2 for outside view the FPS would exeed my 25HZ scenario like yours and give me 30-40 fps with bad stutter but only outside views. Switching back to VC and back at 25fps Michael Moe Michael Moe
June 13, 20178 yr Author Hi Michael, Here I use Prosim with their flightmodel. My view is the custom VC without instruments devided over 3 seperate views. So I set my monitors first to 25 and then back to 25 hrtz in the Nvidia CP . Now with vsync enabled they stay at 25 hrtz. However , DxTory, even if it sees P3Dv4 does nothing to limit the framerate. I set the monitors to 50 hrtz and DxTory to 25 and the framerate was 30-45 ... regards Gerard 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv. 13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degrees My flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
June 13, 20178 yr Author 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv. 13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degrees My flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
June 13, 20178 yr I think I remember reading somewhere in these forums that v-sync doesn't work in windowed mode. Even though p3d is expanded to cover your monitor, it is still not in genuine fullscreen mode? I'm probably talking out of my arse, so I invite the experts in at this point Stu i7 12700K , DDR4 64GB RAM @3600MHz, Asus Z690-Plus D4 MB, Gainward 4090 RTX Graphics, 850W Corsair PSU, Kraken AIO watercooler, Nvme 1TB ssd, 1TB ssd, 500GB ssd.
June 13, 20178 yr For some reason I have never seen the issue of screen tearing in P3D when panning in the VC - which (as I understand) is one of the things that Vsync, addresses - so I have been running with it "off". I have recently upgraded to a 1080 Ti GPU and a 4K Samsung 28-inch 60 Hz monitor. I am running textures at 4096, which, combined with the high-res monitor, allows me to run only 2X MSAA with perfectly acceptable results anti-aliasing wise. I still see no sign of screen tearing. Is there any particular reason why I should use Vsync? Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
June 13, 20178 yr Commercial Member I've noticed the same thing... hardly any difference with it on or off. Dave Hodges System Specs: I9-13900KF, NVIDIA 4070TI, Quest 3, Multiple Displays, Lots of TERRIFIC friends, 3 cats, and a wonderfully stubborn wife.
June 13, 20178 yr Commercial Member 5 hours ago, GSalden said: Hi all, On my system I Always had Prepar3Dv3 at Unlimited , vsync on , monitors at 25 hrtz and DxTory at 25 fps. Nvida CP vsync at 3D application Now with P3Dv4 My fps are at 35-60 and no difference with vsync on or off. Also DxTory has no influence on the framerate ... All suggestions are welcome. You are absolutely correct Gerard with your analysis, seems to be a problem there with your setup. On my system I get 100+ fps with P3D Display Settings VSync=Off and near stable 59fps with VSync=On - my monitor is 59Hz. To the uninitiated, P3D Vsync is not in charge of 'screen tearing' like we see with what we usually consider VSync to control. In P3D Display Settings VSync is in charge of timing your frame rate output to that of the monitor refresh frequency only, the desktop timing vsync is in charge of avoiding screen tearing. Steve Waite: Engineer at codelegend.com
June 13, 20178 yr 28 minutes ago, SteveW said: You are absolutely correct Gerrard with your analysis, seems to be a problem there with your setup. On my system I get 100+ fps with P3D Display Settings VSync=Off and near stable 59fps with VSync=On - my monitor is 59Hz. To the uninitiated, P3D Vsync is not in charge of 'screen tearing' like we see with what we usually consider VSync to control. In P3D Display Settings VSync is in charge of timing your frame rate output to that of the monitor refresh frequency only, the desktop timing vsync is in charge of avoiding screen tearing. Is this why I never seem to notice tearing in P3D ? I also think tearing is related to speed of panning (I may be wrong) and in a flight simulator, unlike a FPS game, sudden panning movements are very limited. Mark CYYZ
June 13, 20178 yr Commercial Member That's right Mark. Without monitor vsync we might see an upper proportion of the screen image shifted slightly horizontally to the previous frame showing in the remainder of the image below. P3D DIsplay settings VSync=On only 'steers' the GPU output to at or near the monitor frequency. Steve Waite: Engineer at codelegend.com
June 13, 20178 yr Commercial Member Gerard, try the NVidia Control Panel profile resets, and if no joy try reinstalling the drivers. Steve Waite: Engineer at codelegend.com
June 13, 20178 yr Author Just found out that there are newer versions ( yes , I know I should have looled at that first .. ) and after I installed the latest version ( 2.0.142 ) it worked right away. This one has W10 support... I was still using version 2.0.127 which worked fine with P3Dv3... 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv. 13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degrees My flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
June 13, 20178 yr Author 2 hours ago, SteveW said: Good news! Steve , I did not try an AM yet because I am awaiting your opinion ... Without AM , but with addons via Proces Lasso it is already running very smooth. However these addons are still grouped across my 5820 cpu like it has an AM of 340.. regards Gerard 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv. 13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degrees My flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
June 13, 20178 yr 4 hours ago, SteveW said: You are absolutely correct Gerard with your analysis, seems to be a problem there with your setup. On my system I get 100+ fps with P3D Display Settings VSync=Off and near stable 59fps with VSync=On - my monitor is 59Hz. To the uninitiated, P3D Vsync is not in charge of 'screen tearing' like we see with what we usually consider VSync to control. In P3D Display Settings VSync is in charge of timing your frame rate output to that of the monitor refresh frequency only, the desktop timing vsync is in charge of avoiding screen tearing. Now I understand. I limit my frame rate in-sim to 30. I know from testing that the new card is capable of much higher frame rates in non-complex areas. I assume that with P3D Vsync I would normally get 60 FPM unless the graphics workload gets too high, in which case it would throttle back in 1/2 multiples of 60 - to 30 or 15 etc. Seems to work fine as I currently have it. I think I will leave Vsync off for the time being. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
Archived
This topic is now archived and is closed to further replies.