May 20, 201313 yr I made a backup of my fsx.cfg which was based on bojote's mods and proceeded to try to re-optimize based on Word Not Allowed's guide. After going through Word Not Allowed's guide, upon startup, the aircraft selection had a white aircraft. Then, I go blocks for trees and VASI. Also, the windshield was just green and not transparent. I tried some more changes going through the guide again, then I started getting a black screen after the aircraft selection. At that point, I went back to my original config. So with bojote's config, I checked it against Word Not Allowed's guide. My buffer pool was like 865456. So, I set that to 0. I also had a second video card entry, which I removed the three or so lines. I also added a line for 1920x1???x32. I also checked nvidia inspector, which somehow was wrong, as well as lowered my AA to the level just below 8xS or so. Performance seemed to be a bit better. Now to the point, I notice when in window mode compared to full screen, windowed is slightly slower than full screen. Is there any way to get windowed closer to full screen performance? 10700k / Gigabyte 3060
May 20, 201313 yr Commercial Member Now to the point, I notice when in window mode compared to full screen, windowed is slightly slower than full screen. Is there any way to get windowed closer to full screen performance? Is your full screen setting (screen resolution) the same as your Windows screen? If not that could easily explain the difference. With recent nVidia drivers I am finding maximised Windowed mode nearly 50% faster than full screen mode! Weird -- I'd never expect anything like that. I thought it must somehow be because of some nVidia Inspector "quality" setting wasn't activated in Windowed mode, but I can see any difference apart from the title bar at the top (which doesn't both me as it is too high on the projected screen to see easily from inside my cockpit). So, does anyone here have an opposite theory -- how can Windowed made be so much faster? BTW I tried DX10 mode again, and it isn't faster than either of those modes in DX9. Not slower either. maybe I could rack up some of the sliders more in DX10. I don't know. I'm happy enough where they are in anycase. Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
May 20, 201313 yr This part of Kostas guide is important [GRAPHICS] ForceWindowedVsync=1 To restart Aero, there are more possibilities, choose yours: 1) manually – quit dwm.exe (task manager, Desktop Windows Manager), it will restart itself, and Aero will be enabled 2) create a batch file containing: @echo off start “” “E:\FSX\FSX.exe” (insert here the link to your FSX.exe) net stop uxsms net start uxsms and run it. FSX is going to start, Aero is going to get started after FSX, and voila… 3) elegant solution, through FSUIPC (only works with registered version): a) create a batch file containing: net stop uxsms net start uxsms B) set the FSUIPC to run the batch file automatically, edit the FSUIPC.ini and enter: [Programs] Run1=HIDE,”E:\FSX\Modules\FSX.bat” (insert here the link to your FSX.bat) This solution is going to do everything silently. No CMD popup windows, only visible Aero activation. Reference post: Link
May 20, 201313 yr Author Is your full screen setting (screen resolution) the same as your Windows screen? If not that could easily explain the difference. Yes, I checked that they were the same. I have a somewhat recent nvidia driver from last Fall or so. This part of Kostas guide is important [GRAPHICS] ForceWindowedVsync=1 To restart Aero, there are more possibilities, choose yours: 1) manually – quit dwm.exe (task manager, Desktop Windows Manager), it will restart itself, and Aero will be enabled 2) create a batch file containing: @echo off start “” “E:\FSX\FSX.exe” (insert here the link to your FSX.exe) net stop uxsms net start uxsms and run it. FSX is going to start, Aero is going to get started after FSX, and voila… 3) elegant solution, through FSUIPC (only works with registered version): a) create a batch file containing: net stop uxsms net start uxsms B) set the FSUIPC to run the batch file automatically, edit the FSUIPC.ini and enter: [Programs] Run1=HIDE,”E:\FSX\Modules\FSX.bat” (insert here the link to your FSX.bat) This solution is going to do everything silently. No CMD popup windows, only visible Aero activation. Reference post: Link I don't run Aero, rather the standard old style Windows 2000 look and feel. I did add this in to fsuipc.ini, but I don't know if it will help? I'm not seeing the tell tale flash of the restart. 10700k / Gigabyte 3060
May 20, 201313 yr Is there any way to get windowed closer to full screen performance? I have not found a way. I have always run in fullscreeen mode for optimum performance on a dedicated sim computer.
May 20, 201313 yr Make sure your FSX window is not touching the taskbar. Either set it to 'autohide' or move it to a second monitor. Jay
May 20, 201313 yr Commercial Member I don't run Aero, rather the standard old style Windows 2000 look and feel. I did add this in to fsuipc.ini, but I don't know if it will help? I'm not seeing the tell tale flash of the restart. I don't run Aero either -- it's a PC dedicated to FSX. No need for Aero. So there's no point in running anything to stop it and restart it. I wonder if my Windowed use is faster simply because I don't have: ForceWindowedVsync=1 in my FSX.CFG. I haven't really noticed any "tearing" or the imiage so i didn't add it. Does the nVidia Inspector Vsync setting only affect full screen mode? Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
May 20, 201313 yr Commercial Member I wonder if my Windowed use is faster simply because I don't have: ForceWindowedVsync=1 Hmm. set that and whilst it limits the top fps, it's still faster in those instances where I've always had a big dip. I think I'll stick with Windowed mode for now. I'm sure it must be down to some change in the nVidia drivers. Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
Create an account or sign in to comment