Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. I don't think I've ever heard this guy as underwhelmed by an add on as this. He's normally overly impressed by pretty much anything.
  3. 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
  4. Please release now! SImple reasons are that it surely will motivate the developer to get good feedback and good money (if its product is good!) A full release is aimed to end of 2024 or later if several betatesters have said, so still a long road. I have no problem with a kind of early access when I know what I get and I know what I can expect. That is a big difference to FSHud as example, wich released a completely buggy product, then make an open official beta, which tooks also more then a year and the outcome is still unsure.
  5. FSHUd is The best investment I have made since the start of 2024! Easy to use and effective.
  6. Only the voices are AI, the traffic managing part is scripted.
  7. Today
  8. @Murmur Thanks for the detailed info. Going to set it up tonight, long weekend this week. One question though not related to or maybe related to the the cyclic or the rotor rpm. The default R22 tends to pitch up if I leave the cyclic, it needs constant forward push, the center spring from the stick has been removed and even the calibration is fine.
  9. I now fly Heli/combat and drive car/trucks almost exclusively in VR(Q3). But my daily 2~3hr jet flight is still in flat screen with TrackIR.
  10. The last time i installed AIG the models looked terrible. This was well over a year ago but they looked bad. I wondered if maybe something was up, because the FSLTL liveries look so nice.
  11. How do I get the display of the GPU. Do I have to install GPU Z in a special folder or does GPU have to already be started.
  12. I guess you probably updated the XP11 but didn't update LittleNavmap simulator database. You have to reload library scenery, it's described in point 51.3 of LNM manual, here: https://www.littlenavmap.org/manuals/littlenavmap/release/2.8/en/SCENERY.html I hope it helps you 🙂 Regards, Piotr ps. general info about LNM navigation databases is available here: https://www.littlenavmap.org/manuals/littlenavmap/release/2.8/en/NAVDATA.html
  13. Do it like Fenix. Block1 now and Block 2 later. Weeks, not months. 🙂
  14. Try the FBW A320 Neo. It is free and has plenty of depth.
  15. Here I am using large 4K TV’s as displays and they are running at 60 hertz. If I limit MSFS to 57-60 ( incl FG ) than I see small stutters now and then, which I do not see when running MSFS at Unlimited. Not using FG and running at 30 fps / Limited is less smooth, especially when banking or making turns. However, 2 displays are connected to the 4090.
  16. Interesting, how do you achieve this? Simply remove the FSLTL model library? The injector then basically uses the fallback for each and every plane? I currently have both FSLTL and AIG fully installed and I still think that the fallback does not really work well comparing the variability of textures and models of both FSLTL and AIG on a given airport at a given time.
  17. Well written. If you are seeing 20 fps ( in your case 25 ) without any long frames and FG doubles that, then you will have a smooth sim. As long as the total FPS is at least 30 ( some say 25 )….
  18. Thanks , yes this is really not a flexible way for sure. Michael Moe
  19. I dont see what you mean with procents, there are several questions asked when you run the installer.... did you not see them?
  20. I had this happen to me once. When it did happen I did not wait for the sim to load all the way to the MSFS menu, ever since then, as long as I wait til the menu loads before I press ALT + ENT, it works fine.
  21. What is the difference between the G1000 and the WTG1000 NXi ?
  22. Awesome. I will just give it a couple of days to see if any ugly bugs come crawling out that need squashing, but otherwise this one is looking good for formal release.
  23. so far so good with this version nomore stutters. thank you
  24. I replaced my dying Reverb G2 with a Quest 3 today and so far it seems to have solved my long pause/black screen issues I was getting with the former. Also good news is I am getting similar performance with the Quest 3, the optics, and hence MSFS visuals, are far superior to the Reverb G2 because of the pancake lenses, and SSW (motion reprojection) works so good that I am actually going to use it (it was a flubbery mess with the Reverb G2). The relevance of this is that with SSW, I effectively have an FPS cap of 40 (doubled to 80) so I have finally got to experience having an FPS cap with AutoFPS. I initially set my FPS target to 40 and, as expected, TLOD did not move up at all. Setting it to 38 resulted in small TLOD increases and did not seem to have any noticeable effect on achieving a stable enough FPS for SSW to do its magic, so I am pretty happy with that. If it does turn out that I get SSW issues, I will just switch to using DynamicLOD_ResetEdition which doesn't care about FPS, but so far so good. Finally, regarding the change to make VFR behave like IFR for TLOD automation, just with different default settings, effectively means that these terms are not really applicable with expert settings as you can configure the expert settings however you want for each. The thing that is stopping me just renaming them to something like profile 1 and 2 is that non-expert mode actually sets VFR-like and IFR-like parameters by default so these two terms are still valid for non-expert mode and naming them profile 1 and 2 is so sterile IMO. Also, I expect most users using expert settings will still use a VFR-like and IFR-like profile anyway, so I am leaning towards just leaving the naming convention as is.
  1. Load more activity
×
×
  • Create New...