Jump to content

MrFuzzy

Members
  • Content Count

    1,707
  • Donations

    $15.00 
  • Joined

  • Last visited

Everything posted by MrFuzzy

  1. Personally, I only use their liveries and stick to MSFS traffic. Lighter on the CPU and the ATC.
  2. VSync off in MSFS, forced on in NVCP. Graphics settings: Motion blur off, lens flare and correction off, 3440x1440 Ultra / TAA 100% / AMD sharpening 100 and the following changes in Usercfg.opt {Graphics Version 1.1.0 Preset Custom {Shadows MaxSliceCount 4 Size 4096 {ReflectionProbe Size 512
  3. Were you in the beta, just in case? Happened to me too with SU14, I resolved only with a full reinstall. Which also resolved the long loading time issue. AAAAND (but on this one I want to cross my fingers because it could reappear any moment) the airport texture issue with DX12. It took me an entire day, painful but beneficial.
  4. No issues in the cockpit here. Tested on several aircraft including PMDG737, A32NX, G1000s... 546.31 drivers, framerate capped at 60 fps via NVCP.
  5. I have artifacts only on the 2D elements (ATC window, HUD overlay, top toolbar...). Aircraft and scenery look exactly as without FG.
  6. USB and BT devices have nothing to do with this feature... Personally I have experimented many problems after SU14 but after a clean install, 546.31 hotfix drivers (I am avoiding 546.33 for now, due to the overwhelmingly negative feedback of the community), I am using both FG and DynamicLOD without issues and MSFS has never been so smooth and enjoyable for me. No hardware upgrade that money could buy would have brought such an improvement as these two free tricks.
  7. Try this: Open Start. Type regedit and click the top result to open the Registry Editor. Browse the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity Double-click the Enabled key and change its value from 1 to 0. Click the OK button. Reboot the PC
  8. Absolutely, and not only for gaming. I've even disabled the TPM hardware completely in BIOS, along with virtualization.
  9. https://support.microsoft.com/en-us/windows/device-protection-in-windows-security-afa11526-de57-b1c5-599f-3a4c6a61c5e2
  10. There are conflicts currently, so either one or the other. IIMHO ORBX Dubai is better, with Inibuilds Palm Jumeirah for example is totally flat apart from 2-3 custom buildings, whereas ORBX has also autogen and the Palm is much more realistic. Also, in Inibuilds Dubai the Jebel Ali port with all its cranes is totally missing. These are just my notes after a 10 minute flight, but I had the clear impression that ORBX is better.
  11. I can appreciate the difference between 30, 48 and 60 fps (before I used to limit the framerate to 48) even with GSync. I can even tell the difference between 60 and 120 fps, that I can reach in certain conditions with FG, however I decided to cap the framerate at 60 to limit the GPU fan noise. Everything is subjective, however as you and others have observed, if you get 15 fps on the ground you need to drop your TLOD or traffic settings first of all (the auto LOD tool can be handy in this case), because in that case FG will generate many artifacts and the experience won't be smooth anyway.
  12. Wow, as usual with the PC version of MSFS there is a wide range of feedback. Personally I found FG a game changer and I understand how it is a major selling point for 40 series cards. However FG is not to be considered a miracle cure and a pass for cranking up resolution scale and graphics settings even on dated PCs. As I mentioned before, being the additional frames generated by the AI, the smaller the difference between two consecutive real frames, the better the result will be. "Small difference between frames" means basically that the image doesn't change much from a frame to another, and this is achieved when a short interval of time passes between the two frames. That's why I don't recommend limiting the framerate to 30 fps: in this case only 15 real fps are rendered and the interval between two consecutive real frames is 67 ms. When you pan the view rapidly, many things change on your screen in 67 ms and artifacts may be displayed. Your PC should be able to deliver a decent framerate to begin with. My PC normally delivers 37-45 fps in the worst-case scenarios (taxiing in busy international airports with heavy airliners and real traffic and liveries) but if in these conditions you see 15-20 fps without FG, don't expect FG to make miracles. I use the NVCP frame limiter at 60 fps and with GSync the experience is very smooth, certainly better than without FG. As for the artifacts, I believe that the reason why 2D elements and windows generate the most terrible ones is that the algorithm expects them to move with the other elements and starts to move them when you rotate the view, only to realize a frame later that they are still in the original position, hence the psychedelic ghosting effect. I am sure that these elements can be excluded from the frame generation (I don't think that 40 series owners see that) and when FSR3 frame generation is supported natively in MSFS, the issue will be resolved.
  13. PG and handcrafted landmarks, monuments, etc... https://www.flightsimulator.com/city-update-v-european-cities/
  14. 30 is jerky, try 60 fps or remove it at least for the purpose of testing. With 30, your system is rendering only 15 "real" fps (1 each 67 ms) and I am not sure FG can cope with it... when you pan the view, the image changes a lot in a 67 ms time.
  15. VSync must be forced ON in NVCP for FlightSimulator.exe and OFF in the sim graphics settings. It would be nice if it were possible to disable nVidia Reflex to save some watts, but even in its current status if you disable the 2D interface elements it's 100% playable. It works very very well for me. I am also using the frame limiter at 60 fps in NVCP. 747 at EDDF, where previously I was stuck at around 45 fps with some drops to 35-37 (main thread bottleneck). The framerate with FG is very stable and my system is chilling as if it were generating 30 fps only (it is indeed!), with some headroom left both on the main thread and the GPU.
  16. The previous thread was closed and had an incorrect title so... Remember to update the in-game content once the sim loads.
  17. Frame generation does not affect the gauges, DLSS does. You can use FG with TAA.
  18. It should be: For Steam: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator For MS Store: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_VERSION NUMBER__8wekyb3d8bbwe
  19. Have you rebooted the PC after enabling HAGS and are you using DX12? Also check if you copied the files in the right directory. For Steam it is C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\ You have to copy the files in the folder where FlightSimulator.exe is.
  20. VSync must be forced ON in NVCP. Are you using TAA and 100% render scaling? I noticed that if render scaling is increased, artifacts affect not only the interface but also the graphics.
  21. Did a full reinstall of Windows 11 and the sim with the following results: Long loading times: fixed A310 periodic stuttering: fixed (for now) Freeze when trying to return to main menu: NOT fixed
×
×
  • Create New...