Benjamin H

I helped someone else with this behaviour a good while ago and in his case the cause of the issue was a corrupt hosts file due to using the Map Enhancement program which edits that file on each launch and reverts the changes upon closing it down, but sometimes that process doesnt do it and the hosts file goes into almost a loop where it just edits the file, but does not revert the changes and the file gets filled up and if those entries are still there during startup without using the Map Enhancement, the sim does not have access to the servers needed for loading in scenery. The hosts file is located here "C:\Windows\System32\drivers\etc\hosts" and here is a guide for resetting the file to default state. I would give that a go if you see that the file has been edited recently or has different dates than the other files in the same location. https://www.majorgeeks.com/content/page/how_to_reset_your_hosts_file_to_default.html

Installed the latest test version today and even though I have a 7800X3D I was curious about the priority setting and the power plan adjustment, but noticed in the logs and whilst in the sim on the first attempt that the power plan did not change dynamically, but managed to find a workaround and what was causing it. I am running the norwegian version of Windows and AutoFPS was looking for "high performance" or "ultra performance" specifically, but mine is named "Optimal Ytelse" in norwegian. I figured out how to change the power plan name using cmd or powershell and ran the command powercfg -changename 1eacde4f-8de7-4761-bb8f-1c2249ce4e31 "Ultimate Performance". That did the trick, but the GUIDs for the power plans does not change from language to language so my suggestion would be that AutoFPS instead looks for these two GUIDs: 1eacde4f-8de7-4761-bb8f-1c2249ce4e31 (Ultimate Performance GUID) and 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High Performance GUID). GUIDs can be verified by first running the command powercfg /L that lists the power plans available.

I find the Nvidia Sharpening too aggressive even at a very low setting, but all systems are different and there are many factors that does effect each and everyones result. My preferred setting is now to set Sharpen = 0 in my usercfg.opt in the postprocess section and I have enabled sharpening only in my monitors OSD menu. Before I had the OSD monitor setting at 0 and also at 0 when trying the Nvidia Sharpening and still it was too much for me. Searched a bit and someone suggested only via the OSD and that gave me a mild, but very good sharpening that didn't introduce shimmers etc.Very difficult to showcase how it looks, but this image below is the best I have for now as to showing what I see on my monitor. Image isn't grainy of course as this is, but sharpening is quite well showcased here.

Just updated both my utilities today, and wondering if DynamicLOD is supporting the latest 2020 update in the most recent build (did not see if release version or test version, but opted in for the tests if that is so)?

I do enjoy spending almost a criminal amount of hours to get the absolute most out of my hardware and the capabilities it has available, but I also like to provide something to show for when coming with tips for others, and yes, I am still on 2020, but it is relevant for 24 as well. Task manager graphs, RTSS overlay and devmode values are almost therapy for us who seek the absolute best performance. My system is set up in a way that it has a healthy amount of headroom so it can handle the most demanding scenarios I throw at my system. Some would say underutilized, but this is balance for me and does give me a lot more smoothness as the frametime graphs clearly shows.

I notice that you have your iGPU enabled, but it isn't in use. Unless you use it specifically for other programs under graphics settings within windows, I would disable that as well. Even though there isn't that much resources being saved, there are still just the fact that every resource can affect the sims these days, and a minimal save is always better than loosing out on the small benefit.

Copied in from my response in the MSFS forums. I have understood that something was causing this, but I would say that this approach below would reduce the stutters even on the SU5 beta. Beta is a beta, and we take part for these reasons, and it's up to each and everyone to take part, and you just can't know what you will experience, but the team gets feedback which is what they are seeking for those who participate, and if you have a sim that runs very well on a stable version, do a proper and an extra evaluation if you want to give up something that is working. "I have one tip that is almost the most basic one in the book, but that might have significant effect. By the videos it looks like your sims are running unlimited FPS or a lock that is too high and therefore doesn’t really do much and your hardware doesn’t have any form of headroom since I would assume that they are close to or at 100% load, especially your GPUs. My CPU and GPU are always running with lots of headroom and at 50-70% on the ground and when the most demanding situations is thrown at them, they have the headroom to deal with it, and panning quickly whilst already running your hardware at an unnecessary high load, it often can be a large cause to stutters. I have capped my FPS at the lowest I see whilst heavily panning around which is 60 that actually matches perfectly with my old 60Hz fixed refresh rate monitor. Yes, there are difference to 60 and 110-120FPS, but I would rather sacrifice that when the reward is an FPS that always stays at the same number and naturally has a lot less stutters (RTSS and the FPS display has a flat frametime graph) , but I know that even if I can reach 110FPS at times, the sim will get close to 60 in the most demanding scenarios (I am running much lower specs than you are with a 7800X3D together with a 2080Ti). Pay attention to the devmode FPS display and try and set a cap below your lowest FPS seen and afterwards adjust it."

Simple fixes are sometimes the best solution to things, and I fully support your last part of this. To just go for it is as good as a more time consuming solution in many cases, like this one.

Thanks a lot, I can now confirm the UI working as intended if closing it in the most compact mode. Appreciate the quick fix, and out of pure curiosity, what was the cause of it? Of course no need for full details etc, just a short explanation will do, and no explanation is of course accepted as well, it works, and I am very satisfied with how the UI is behaving now. And again, hats off to you for keeping those of us who prefers some more control over parameters satisfied by continously updating both softwares side by side. Attached some images that shows what's possible to achieve with some very finetuned steps. A quite heavy test over Aerosoft ENGM above FL200 where I have TLOD 400. On the ground at ORBX Arlanda in the Fenix cockpit My sim can have a higher VRAM usage at cruise compared to on the ground, and I hope that these images almost showcases textbook usage of your software. Above FL200 Descending Close to ground level again, same flight And at the gate again, but not sure if this was the same flight, but I can confirm that VRAM usage was exactly the same on the ground after a descend compared to starting the flight

I had actually come to peace with missing out on the A340 initially since I am still on MSFS 2020, but in case anyone has done the same, I just came across the developer confirming it being released for both sims. It doesn't seem to be mentioned too often, so hopefully this gives others some good news. This is a paste from AS' discord server. "2020 and 2024, we will go more into the details here what to expect from which simulator later down the road 🙂"

Topic on the norwegian FS forum originally regarding the Dash 8-100 might be of positive reading since a reliable source on the Dash (I believe ex-pilot on it) actually has written that 2026 will be a good year for Dash lovers. He already wrote in october last year that some patience is needed, but something much better is coming followed by some recent activity that it might still be some time away, but 2026 is much better than nothing. https://flightsim.no/topic/89901-dash-8-100-i-morgen/

A little update after trying the new UI window positioning out more properly (might have done the testing a bit too fast the first time, but hangover as the cause) and I might have found a potential bug if you end the sim whilst the UI window is in the most compact state. When starting DynamicLOD up again I am not able to click myself back to the initial full UI window, and I have attached a few images below as well as what I had to do to make it work as it should again. Changed the state from 2 to 1. Hopefully this can be recreated (if it is indeed a bug). Before shutting the sim down After shutting the sim down and starting the program up again (this happens if auto-starting with the sim as well), and this is where the UI is not responding to clicking the window for the UI to go back to full After edit

I will let the pictures speak for themself this time. I was only connected as an observer and therefore not real weather in use, and the reason for that was that I looked at the preview of the weather and decided that I wanted to be sure to at least see more than 4 aircrafts at a time. I got the code of conduct rules as first comment on VATSIM's FB page, so I am not taking any chances. Made me read the code of conduct, and you are encouraged to use real time weather, but you need to meet a minimum requirement of having the winds, temperature and pressure as real life, so you can have clear skies during a storm as long as you have those 3 components, and it is not often I go into a proper long reply to those comments, but in this case I did it. The VATSIM network would be reduced quite a bit if the supervisors had info about your simulators weather. Sometimes it's best to think your replies through entirely before commenting in a way where you are confident to be correct.

I must have opened the program at the right time, I updated my version half an hour ago and can confirm that it works very well. Images are not taken while in the sim, but it works there as well. Only small thing, which I noticed due to opening it up before the sim to try the resizing was that the window adjusts itself by the smallest bit straight after start, but don't make that a priority to sort, you have to be literally looking straight at the program outside of the sim and if the window shows up directly and not going to the task bar, you might not even notice it. Today I have gotten more than I could ever hoped for when writing the request, so highly appreciate it.

Yes, I see that I mentioned a few pints as the edit reason, and I noticed that I posted in the wrong thread afterwards, but really appreciate getting it in here and also sharing the great news, and actually, this was just about exactly how I thought it could be solved (but I took a professional decision of not attempting an explanation of that at the current time😇) so I am really looking forward to it, and I can also test it out since I opted in for the test versions a little while ago. How it should be really when you request a feature, participate in it and provide feedback.