Jump to content

poplar

Members
 View Profile  See their activity

  • Content Count

    141

  • Donations

    $0.00 

  • Joined

  • Last visited

Everything posted by poplar

  1. poplar
    Nice!
  2. poplar
    Or, if this applies to your install, open the Xbox app, choose MSFS2020 on the left, on the right, click the three dots and choose 'Manage', this will help to restore the application. Well it did for me anyway, after I rolled back Windows 11
  3. poplar
    Same happened to me when I rolled back, this helped me fix it...
  4. poplar
    This happened to me when I rolled back - try this first, it worked for me, didnt have to reinstall
  5. poplar
    Based on my experience, I'd recommend you roll back from 22H2. This solved so much for me. SU10 running great now.
  6. poplar
    Are you running Windows 10, or perhaps Windows 11 without the latest 22H2 OS update?
  7. poplar
    Just wanted to update this thread with my solution - I rolled back the latest Windows 11 update (22H2) and all my panning stuttering, weird error messages and CTDs are gone. Loving SU10 now.
  8. poplar
    Please report back with how you got on with the Studio driver. There are lots of us ex SU9 users going slightly mad over this occuring in SU10 - feels like 5 steps backwards, SU9 was amazing for my rig.
  9. poplar
    The following might help some people encountering this error and CTD - try setting the off screen terrain pre-caching to Ultra https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem-again/543820/37?u=thinkglobal
  10. poplar
    Here is the thread over in the Microsoft forums discussing this error message: https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem-again/543820/13 Here is a similar thread from the SU10 Beta discussing the same error: https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/10
  11. poplar
    You're right, lots of discussion here during the beta about this exact error message: https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/41
  12. poplar
    Same error with me https://imgur.com/siPrhmT Ryzen 5 3600, 3080, 32gb RAM running on SSD MSFS ran smooth as silk before SU10
  13. poplar
    Very welcome. We SideWinder owners need to stick together 🙂
  14. poplar
    I've got the throttle mapped well in the Cessna 152, but not the airliners, still working on that.
  15. poplar
    Hello fellow SideWinder owner. I've kept mine pristine for the past 20 years. The following is working for me, have a look at my settings here.
  16. poplar
    I absolutely did not think I'd ever use the word "breathtaking" in relation to a video game, however, some of the moments that I've experienced over the past 24 hours with this have been nothing short of "breathtaking". It truly is, undoubteldly, a masterpiece of software engineering.
  17. poplar
    Couldn't agree more. Phenomenal. Realise there will be inaccuracies, overall though, just awesome.
  18. poplar
    Sebastian Wloch: "A cluster of servers is a place where we have data in a data center" Thank you Sebastian for not using the buzzword "cloud technology", which could have been confused with Asobo's actual "volumetric cloud" rendering technology. It's this high level of clarity and common sense with community communication from Asobo which has to be appreciated.
  19. poplar
    Thank you for taking the time to directly update us. Keep safe. Sincerely, Your loyal fanbase
  20. poplar
    Not yet, perhaps they are working to Pacific Daylight Time (Seattle) where its only approaching 06:00 just now.
  21. poplar
    Two phenomenal screenshots (from the Airports video) which make me most excited are: And The accuracy of the lighting in each photo is outstanding. The level of detail in both is unbelievable.
  22. poplar
    “Having a rough week?” It’s almost like Asobo know the pain and anxiety non invited Alpha testers are feeling right now.
  23. poplar
    Except the Epic vs Sykes lawsuit was for “misappropriation of trade secrets” and pretty sure this leak didn’t show anything that Asobo hadn’t made public already. I’m not suggesting what the leaker did was right or that any Alpha tester should disobey the NDA. I firmly believe Microsoft / Asobo will have prepared and rehearsed for this situation, you wouldn’t run an Alpha (and 10k users in an Alpha forum) without having thought through the risks. It was inevitable.
  24. poplar
    Exactly. Mega corporation takes on an individual who they invited to test in another legal jurisdiction? Unlikely.
  25. poplar
    So odd to see a tester test an Alpha so poorly but then I guess testing variety is the name of the game. Just sad to see such poor piloting skills.
×
×
  • Create New...