Eziocin

Guess what ? I am almost 100% sure that my stutters cause was GSX… I tested pushing back with and without it and the difference in terms of smoothness is significant… I know there is an open thread on this issue on the FSDT forum…

OK... I have found my sweet spot... DSR 1.75, DLSS Ultra Quality, Vsync "Force On" in Nvidia Inspector.. some other settings "high Quality" on NI, of course DX12 and FG ON. The result is a stable and very smooth 60 fps, no shimmering at all...some minor stutter every now and then associated with panning or turning n the ground with lot of vatsim traffic at heavy airport, but nothing major...hopefully they might be mitigated by the improved memory management coming with SU15......honestly I have no idea what caused my previous issues and FPS drop....most likely a setting I had overlooked...now overall very enjoyable and immersive experience.. the only caveat is the GPU is always working around 95%-98%.... the workaround for this is to set the monitor refresh rate to 30... Vsync will then cap the frame at 30...same smoothness and no noticeable difference in Sim behaviour, but GPU loads reduce to 65% max (less frame to deliver). One extra info.... I disabled multithreading (or whatever is the AMD equivalent for this), and this seems to have had a slight positive impact. @Cpt_Piett Quite tempted to replace my 8 yrs old LG Ultrawide monitor with some HDR/GSync same size monitor.... 😀

I have tested different Vsync options with a FPS hard cap under all conditions and I didn't like the results...

Following the discussions above, would a Gsync monitor be a good option for MSFS ? I have conflicting reports... is it really a game changer ?

No, this is not what I do...let me clarify: I ALWAYS use Vsync, because it is the only way to avoid screen tearing unless you have a G Sync monitor or similar, which is not my case. To put it simple the Vsync avoids screen tearing by synchronizing the rendered frames with the monitor refresh rate... so in a 60hz monitor the Vsync will ideally sync the frames at 60 fps, provided that the system is capable of delivering 60 fps. If the actual fps are higher than 60 then the Vsync will cap fps at 60 (there is no need to use a hard cap at 60 fps in this case), but if they are lower, there is no way they can be syncd at 60, and in that case the Vsync will anyway continue to avoid tearing but stutters may occur depending on how large the gap between the Sim fps and the monitor refresh rate is. Here is the benefit of the "1/2 Refresh rate Vsync": it syncs the frame with half of the monitor refresh rate, so in a 60 hz monitor, if the system is able to deliver at least 30 fps, then the result will be a perfectly smooth, stutter free 30 fps rendering. What happens in my case is that even if I select "1/2 refresh rate Vsync" in NVCP, whenever I increase the monitor native resolution using DSR either 2.25 or 1.75, the "1/2 refresh rate" feature doesn't work, and Vsync continues to work as a standard Vsync, that is trying to sync at 60 fps, and in heavy scenarios, my system is not always able to provide stable 60 fps, and here is where the stutters come from, at least this is my conclusion.... for the time being... however, it is good to know that with my same hardware and my same MSFS settings you don't have this issue...in the end, I have built my rig just very recently, so maybe I still need to fine tune some settings...

Thanks for the advice… will try it as soon as I will be back in front if my Sim PC, that is after Easter…☹️ I am not on Beta either..

Actually this is strange and I am struggling to understand the rationale of what happens: at upscaled resolutions the 1/2 refresh rate Vsync doesn’ t work, that is even if I select it in Nvidia Insoector I only have the full vsync active which caps the FPS to the 60 native monitor resolution… but if I lower the monitor refresh rate to 30 then the 1/2 refresh rate kicks in and caps the frame at 30…have no idea why this happens.. and the other interesting thing (maybe that’ s obvious) I have found is that once the frames are capped the consequence is that the GPU load drops significantly (most likely because less frames needs to be rendered)… from 95% to 60% roughly.. in both cases I have Frame Generation ON, and it works, not doubling the frames of course, but giving that extra boost which allows me to keep 30 Frames… with FG OFF the performance decay is noticeable.. one curious thing happened today: at Inibuilds EGLL, departing from Terminal 5 with all the T5 stands busy with Vatsim traffic (FSTL aircraft), with DLDSR @1.75 and DLSS quality, normal Vsync (not 1/2 rr), I had stable 55-57 fps at all time from flight preparation, to push back, taxi and take off, with almost no stutter whatsover.. the only difference vs previous flights was that I didn’ t use GSX…. Didn’ t have the time for another test, but that’s an interesting clue… more to come with further tests.. cheers ezio

No...no G Sync monitor...in the plans for the future, but not at the moment...

Great discussion here and a great contribution to a better and better sim experience.... I just want to share my recent experience. I have a Ryzen 7800X3D paired with an Asus RTX4090 and a 21:9 Ultrawide 3440x1440 60hz monitor.. I have tested the DLDSR 2.25x option + DLSS Quality.... vs just DLSS Ultra Quality.... Frame generation enabled in both cases... nvngx_dlssg and nvngx_dlss updated to 3.6 version.. all MSFS settings to Ultra and TLOD/OLOD 150.....no question about the performance in terms of FPS...in both cases the FPS and Image quality are great, but.... I need to enable Vsync (through Nvidia Inspector) to avoid screen tearing (and doing so I have my FPS capped to 60), and every time the FPS drop below 60, even just around 56 or so, I have got heavy stuttering... this is particularly occurring in cases such as Inibuilds EGLL, with Vatsim traffic, using Fenix, where I have fps ranging from 45 to 57.. the only way to have a perfectly smooth sim also in those conditions is to set my monitor refresh rate to 30hz and use Adaptive Vsync 1/2 refresh rate...this caps the FPS to 30 and everything is perfectly smooth even in the heaviest conditions, and visually stunning. I know that most people will scream that it is meaningless to have such hardware to run at 30 fps, but whoever has experienced this has realized that 30 FPS smooth, and I repeat again "smooth", is the sweet spot for heavy addon scenarios and aircraft in MSFS. Having said that, I have made three flights in the last few days, one with just DLSS Ultra Quality, and two with DLDSR 2.25 + DLSS Quality, and while the first one was successful, both the ones with DLDSR, although giving a slightly better visual quality, ended up with a screen freeze and a video driver error message. So to summarise my experience so far: DLSS Ultra Quality great performance and visuals..... DLDSR+DLSS Quality similar performance, with slightly better visuals but still some fine tuning to be done to avoid issues... I will need to build up a more significant number of test flights. Ezio

Does it work also on RTX 2080 series ?

I have a networked configuration with FSX/P3D working on the server and ASN, EFB and vPilot running on the client. Everything works quite fine. On the server I have two parallel OS installation on two separate SSDs, one for FSX and another one for P3D...actually it is as if I had two different computer, as I have two different "computer names". On the client I have the simconnect.cfg file that I have to modify every time I swich from FSX to P3D to take into account the fact that the server name (or IP) has changed. Not a big issue, but I would like to know if it is possible to list in the simconnect.cfg on the client multiple servers names, as indicated here below, in order to avoid editing the file every time: [simConnect] Protocol=IPv4 Address=xxxxx Port=500 MaxReceiveSize=4096 DisableNagle=0 [simConnect.1] Protocol=IPv4 Address=yyyyy Port=500 MaxReceiveSize=4096 DisableNagle=0 ........ I have seen somewhere in the forums this format is possible, but the point is if I modify my simconnect.cfg accordingly on the Client, it doesn 't work, i.e. ASN is no longer able to connect to FSX (or P3D). What am I missing ? Should I also modify something on the simconnect.xml file on the server in order to make it work ? Thanks for your suggestions Regards Ezio

Great job PMDG !!! Very well done..!! As well as many other users I can happily confirm a significant VAS footprint reduction and a subtle yet tangible overall handling improvement on both FSX-SE and P3D verions. Just one observation: in the last few days I have completed a LHR-IAD-LHR rotation, flying LHR-IAD on FSX-SE and IAD-LHR on P3D V3.1. I noticed that on FSX-SE the VAS remained perfectly constant throughout the flight and slightly increased during approach (as it would be normally expected), while in P3D it increased slowly but constantly during the flight, even though I landed in LHR with 900 Mb VAS remaining. Installed addons were mostly the same on both Sims (Aerosoft EGLL, Flightbeam KIAD, ASN SP4, UTX Europe/USA V2.1, REX4 Soft Clouds, AivlaSoft EFB, FSGlobal 2010 mesh, etc....). The only difference is all addon airports except departure and destination deactivated in FSX via Scenery Config Editor, while all addons left activated in P3D. Again, really not an issue at all (900+ Mb remaining after an 8 hours flight with all addons in and textures @2048 would have been impossibile, but it is just a curiosity to understand if this is normal and caused by the different architecture of the two sims or if it is something related to my settings. Regards Ezio Cingolani

Greg, this is weird....the disk(s) are OK...I ran sfc/scannow and they passed OK. The point is not the hardware...it must be a compatibility issue of some sort or something I am doing wrong during install. It cannot be a hardware issue as the disk runs ok with Win 7 and becomes corrupted after a few hours on Win 10.....and this happened on three different SSD....! I noticed that during all the Win 10 installations I have done in the last few weeks I have never installed the Intel Chipset drivers. I realized it tonight looking at the device manager. I don't know if this may be a cause for my problems....another think I am looking at is CCleaner : I have used also the registry cleaner feature and my problems have started shortly after it....quite frankly I don't know where to look at....I am not a PC novice but this is driving me crazy.... Regards

I have recently decided to move to Windows 10. I have plenty of drive bays in my case, so I dedicated two SSDs (one for the OS and one for FSX/P3D) for a "Windows 10 system". I left untouched on two other separate drives the Windows 7 system on which I am currently running FSX-SE. I made a fresh install (updated first, then wiped everything out and made a fresh install)...everything went smoothly...love at first sight...very fast and eye candy system....and when I had FSX with all my addons up and running and made my first flight in the new system I was delighted by how smooth FSX was. It took a few days for the honeymoon to finish.....the first problem to appear was the infamous Start menu issue that seems to have affected several users: start menu not working and several icons on the desktop not working unless "run as administrator"... I tried a few solutions found on the web but none of them fixed the issue. I eventually found out that creating a new user account and logging on this account would solve the problem... Very good....it took me some time to have everything again up and running but at the end everything returned normal. A few days later I ran again into the same start menu problem.....quite annoyed I created a new user account again, but on the next startup I had a "chkdsk" warning ...I let the system run the "chkdsk" which took about a couple of hours to finish with several errors and replacing a huge number of file security IDs. When chkdsk was completed I found that I could not log on Windows 10 any more.... I logged on the parallel Windows 7 system and I tried to access to the Win 10 drive to see if the files were damaged, but I received a message of unreadable (corrupted) disk...this was surprising as this is a brand new disk, so I tried to make a fresh installation of Windows 7 on that disk, and..guess what ?....it worked very well and it has been now up and running with no issues whatsoever for some days. My PC hardware components are ok, as my "parallel" FSX/Win7 system is working pretty well even for continuous hours on overclocking (I7-2600k @4.8Ghz) so I have no reason to believe it may be a hardware failure. SSD failure ? I don't think so as it is now working well...I have also tried some SSD status software to check the health of the disks and all of them seem quite healthy. What else to point fingers at ? I would love to keep Windows 10 but unless I find an explanation for what happened and I have the confidence that Microsoft has found a solution for start menu bug I am not going to make a full reinstall.....I have enough of OS install in the last few weeks... :smile: Any useful suggestion would be mere than appreciated.. Regards Ezio

This is the same problem I have: I have installed P3D V3 on a clean system (Win 7 64b), no previous P3D versions installed. There is no way I can initialise the panels (everything is dark, but the engines are running, start levers are ON and I can hear the engines sound). The only way I can make it work is by loading a default aircraft, launch the flight and once I am sitting at a stand/gate, I load the NGX via the Vehicles menu. In this way everything loads perfectly and from then on it works flawlessly. As the OP above I have correctly installed all the various Simconnect version and both P3D and the NGX have been "installed as administrator". I tried to uninstall and reinstall, but no change. Any idea is more than welcome. Regards Ezio Cingolani

Steve, thanks for the prompt reply. Have a nice day Ezio

Steve, my FSX has now been happily running in DX10 mode for some time using your Fixer, with various options selected in the Fixer sections, such as V2.0 Transparency logic ticked in the Legacy section and so on. Yesterday I installed a new addon airport and for reasons that I don't quite understand when I launched the Fixer to check and convert the effects that were installed with such new airport I noticed that the Fixer had switched to DX9. I switched back to DX10, and my questions is: when I switch back to DX10 do I have to "apply" again all the formerly selected options in the various Fixer sections (i.e., clicking "Apply" in every section) or if the options are ticked they are automatically applied when switching back to DX10 ? I am not sure I explained it well.... Thanks Regards Ezio

Brian, tested SOP3 tonight.....just two words: truly outstanding..!! Thanks for giving us another excellent FS2Crew product..! Ciao Ezio

Thanks a lot Steve...very clear insight..! I use those lights for AI only (UT2 aircraft) so based on your post, I should not convert them. Regards Ezio

Kyle, thanks for your answer....however after I opened this topic, I found in this very same forum another one dealing with what I think is the same issue (the topic title is "Jerky banking turns 777 only") and it looks like some people were experiencing something similar long before ASN SP3 was released. Such topic stops around January '15 (the last post is from you), so I'd like to understand if some sort of solution was found. Regards Ezio

Hello, I am experiencing on a random basis an issue with the T7 which I had never had before: during a turn, although there is a bank angle the aircraft doesn't turn, i.e. the heading remains unchanged, then all of a sudden it starts moving to the new heading but rather than in a smooth way she turns via a series of jerky steps. It is not a problem of FPS drop, as the FPS remain stable during the turn. It happens absolutely randomly and not on every flight, and I don't have any clue on what can trigger it. This issue started to occur after I installed ASN SP3. I have posted the same question on HiFi forums and in the meantime I will revert to the ASN SP2C and see what happens but I just wanted to share this also on PMDG forums to understand if other users have ever had this issue regardless of the weather engine they use. Thanks in advance for any feedback. Regards Ezio Cingolani

Any answer ?

Glad to know you are now running a stable OC. When running FSX it is very unlikely that your CPU will run at idle load. So just set up an OC profile for FSX in the Bios and load it at PC boot up when you want to run FSX. For all other sessions do not OC your PC..it will save some life for your processor and you will not need to take care about Vcore values when you run at idle speed. Regards Ezio

I can't open the attached picture, but if you have the manufacturer and model number you can easily find these values in the manufacturer's website. Another option is, if your RAM is XMP rated (again, you can find this info either on the RAM module itself or on the Manufacturer's website), you can select XMP in the AI Overclock Tuner dropdown menu in the Bios (see the picture in the guide in the same page where the memory timings are shown) and they will be automatically loaded. However I'll see if I can open your picture from my home PC this evening. Also, although I don't think that your BSOD are caused by your processor running at 70 deg. I would take a look at the H60 radiator. The H60 is a little bit marginal for an overclocked I72600K , and if on top of this you have dust accumulation on the radiator you may end with very poor cooling action which is not good anyway. I recently noticed an increase in my CPU temperatures at high load and found out that my H100 radiator was almost completely clogged with dust on the suction side. Once I cleaned it I regained my usual temps (50-55 deg running FSX or P3D @4.8 Ghz). Regards

Robin, I have a similar rig as yours: I7-2600k @4.8 Ghz Asus P8P67 Deluxe Ram 8Gb Videocard EVGA GTX970 (but have been running for more than one year on the 680) Processor cooling: Corsair Hydro H100 I have now been running for almost three years and I didn' t have issues (keeping my finger crossed as you may never allow your PC to hear you saying that they are running well... :-) ). Have a look at this guide : http://www.scribd.com/doc/94305186/P67-Sandy-Bridge-Over-Clocking-Guide-for-Beginners#scribd It might be very helpful (it was very helpful for me at the beginning)... I am not at home today but if you want I can share with you my BIOS settings for the Mobo later on tomorrow. Feel free to ask if you need more detailed info. Regards Ezio