Jump to content

Virtual-Chris

Members
  • Content Count

    997
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by Virtual-Chris

  1. Do you have other games you can try to determine if this is unique to MSFS or your TV?
  2. My suggestion: Turn off V-sync in the game, and in NV CP set it to FAST. Turn off any frame cap. Set your refresh rate to 120Hz if that's what your TV runs at. You should have no tearing and no flicker if you just let it run uncapped - using v-sync FAST in NV CP.
  3. I'm also a long-time Nvidia customer, having used their products for the last few decades, but agree... any malaise coming their way is well deserved. I really hope AMD can produce some competitive products (at a much better price).
  4. If using frame generation with a 4090/4080… - Are you locking FPS to keep it at or below your display refresh rate? I recall reading it’s ideal to keep FPS at like 118 on a 120Hz display. I’m not currently using this. - Or are you using v-sync? I understand v-sync eliminates tearing if FPS > refresh rate… true? I’m currently using NV CP set to Fast - not sure if that’s ideal. - Are you using G-Sync on an OLED? Any flicker in dark scenes? It seems frame generation keeps the FPS high enough to mitigate OLED flicker. - Are you running 4K? If so what TLOD? I can run 4K LOD 400 and still have 60-90FPS (after FG) although LOD 200 or even 300 is less CPU bound on my 5800x3D - Are you using DLSS or any other scaling? I’m currently not using any scaling. - My frame generation setting is greyed-out in MSFS. I had to use the Useropt.CFG file to enable it. Apparently a known bug. - What artifacts have you noticed? I’ve noticed the Garmin speed and elevation ticker tape digits are a bit blurry and the flight director can also get a bit soft when moving. - Are you using TrackIR? How does it work with FG and artifacting? I haven’t got to this yet - What else?
  5. No noteworthy differences I think… just get the cheapest one you can get your hands on.
  6. This sim is so frustrating. Two steps forward, one back with every release. Although I guess it’s better than the early days where it was one forward and two back 😛
  7. I had a very similar issue tonight by the sounds of it. I’ve been away from the sim for a month, and got a new 4090 today, so updated the sim, drivers, disabled all add-ones (except GAIST which I forgot was in my actual community folder and not symbolically linked). I then flew a 30 min VFR flight in the Kodiak, and for the first time ever, experienced an episode of 15-30 seconds of single digit frame rates. I seriously thought the sim had crashed and was about to bail, but it came back to life. It was the oddest thing. I was very concerned my new GPU was borked. 🥵 So I ran a number of other benchmarks and games this evening without incident. I hope it’s something in the sim. Maybe GAIST? But if so, this software is such an unpredictable mess. 🤬
  8. I think as a 4090 owner, you have the luxury of doubling your FPS with frame generation, which requires DX12. So even though DX12 offers less FPS, after you double it, you’re way ahead of DX11.
  9. Would be interested in your FPS in both cases.
  10. What FPS difference do you see between DX11 and DX12? Back when SU10 launched, I noted that DX12 wasn’t noticeably better than DX11 but ran with it. I just got a 4090 and did some more testing (with my 5800x3D). I actually get 5-10FPS less using DX12 with 4K Ultra and LOD 300 or 400 (TAA). Drone view goes from around 86FPS to 78FPS (using LOD 300) with the Kodiak on the runway. Am I alone in seeing FPS go down with DX12 now?
  11. Yeah, I guess if time is money on a heavily multi-threaded task, the added investment in a 12-16core CPU is worth it, but if it’s just a hobby PC, that does a variety of workloads, the 5800x3D will do pretty much any multi-threaded task and give you the best performance in MSFS - it’s good bang for the buck. My guess is the sheer volume of data that MSFS has to process, even at low LOD to render the scene is why memory latency, and thus cache size, is so helpful.
  12. But multi-core performance means very little in this sim. Cache and singe-threaded performance is king. I actually get better performance by turning off SMT (hyper-threading) as it just means less cores competing for the same precious cache.
  13. @Watsi can you comment on the possibility of VNAV ever making it out of the experimental version?
  14. In my case, I want to be able to have the plane fly the glide slope on an RNAV approach, which I would expect is pretty common?
  15. If it’s on bright scenes, that’s probably some other issue. OLED G-sync flicker should only be noticeable on dark scenes. If I was you, I would start with a baseline of settings and only turn on additional settings one at a time after thorough testing. For example, try your display on its native refresh, no vsync in game or NVCP, no g-sync, and no frame limiter. Your only issue should be tearing. If you have other problems, then it’s probably time to try another game. It may be hardware, Windows, or drivers. Then enable Vsync fast in NVCP and tearing should disappear. Then try g-sync and check dark scenes for OLED flicker.
  16. It's important to note that the flickering issue I had is the result of a combination of a dark scene, g-sync, and low FPS. This issue is a well known problem with OLED displays. In a bright scene, no VRR, or higher FPS, you shouldn't have an issue. I think the solution is a 4000 series Nvidia card with frame generation to increase FPS up to the 100+ range. Then the flickering shouldn't be an issue with G-Sync enabled. Until then I will run with VSYNC set to FAST in NVCP and G-Sync disabled. I don't have any issues with this.
  17. Last gen, the 3080 was a relative bargain. The 4080 is now double the 3080s launch price. I think if you can stomach the cost of the 4080, you might as well just spend marginally more for the 4090 to get the best. It has substantially more cores and vram. The 4080 is 2/3rds the capability of the 4090 for 3/4 the price. It’s not a good value. Certainly not like the 3080 was. It’s in stock for a reason. Few are buying it. Get the Nvidia FE 4090.
  18. I guess my point was that if you can afford the 4080 at £1,300-1,500, what's another few hundred for the 4090?... either one is basically an admission that money is no object when it comes to your graphics card - just get the best.
  19. Lots of reports on Reddit of 4080s in stock at many retailers. So I think people are smartly avoiding this card. It’s not good value. If you can afford a $1200USD graphics card, you can probably also afford the 4090 or just save a bit more for it.
  20. Sounds like it’s largely down to owners not seating the cable in the socket fully... User error.
  21. That wouldn’t surprise me. When the 30-series released, there were reports of some cards locking up at high boost clocks… so they lowered the max boost in a driver update. I expect they will solve this the same way: Lower performance to reduce the fire hazard rather than fix the connector.
×
×
  • Create New...