I have been experiencing some very concerning frame loss scenarios when ulocking (undocking?) a window such as AS, VoxAtc or FS2crew and dragging them to my second monitor. They would literally drop to between 12-15fps! At first I thought it had something to do with Vsync or locked framerates and then of course, why should that suddenly appear out of nowhere? Sooo.... it appears that the Nvidia control panel is the culprit. I had been trying out limiting frames, using adaptive Vsync and a couple of other things in the list and saving the changes specific to P3d. First I thought the issue was limiting framerates in NCP and then perhaps using adaptive Vsync, but it seems, after confirming about a dozen flights that if any one of the options is used and saved, then the framerates continue to drop down to, in some instances, as low as 12-15fps! Once I had unchecked all the options and made them global, things went back to normal in P3d. However, what I did, and I'm unsure whether this needs to be done, but once I had gone back into the graphics options of P3d, I made a change, it doesn't matter what it is, as long as you then save the option in the control panel. I have read similar experiences among other simmers on several forums, so I hope this helps. 😃

Edited November 21, 20205 yr by Rockliffe

Yes Howard, I always had that problem with P3D, RTSS did not work also. P3D own FPS limiter is the way to go.