Jump to content

MrFuzzy

Members
  • Content Count

    1,714
  • Donations

    $15.00 
  • Joined

  • Last visited

Posts posted by MrFuzzy


  1. 14 hours ago, Sonosusto said:

    (Incidentally, for those who have been around for a while: We were chuckling in-house today about the time we changed our whole website to reflect "PMDG. A Boeing Company" and issued a fake statement saying that we had been bought by Boeing, who was interested in our simulation technology. It was all well and funny until an aviation reporter called to ask us about it... When I didn't take the call, he called Boeing. The the Boeing lawyer called... That was when it stopped being funny! 🤣🤣)

    That's crazy because the news would have rather damaged PMDG's reputation 😄 


  2. TAA for quality, DLSS if your GPU is the bottleneck.

    DLSS / DLAA is deep learning AA at native resolution and does not bring any performance benefit.

    Displays and water from low altitude will look bad in both cases and there is no remedy.

    It's just a subpar implementation in this game, as well as DX12. 


  3. 11 hours ago, F737MAX said:

    What's the LOD like in this version?

    Plenty of complaints in a thread on the official forums that v1.37.7.0 saw a big drop in the visual experience compared to prior beta versions and SU14.

    LOD & draw distance will continue to be sacrificed for payware addons, to accommodate the needs of XBox users who lately experienced avionics shutdowns and other issues on addon aircraft.

    The "memory optimizations" that Asobo boasted in the last interviews are aimed to that. Something must be offloaded when the shared memory is full and scenery elements are more expendable than avionics. Hence the reduced draw distance and the stuttering when panning the view and reloading the assets.

    There was no need to "optimize" memory usage on PC, where we have many sliders to accommodate every kind of configuration and also considering that on high end PCs both RAM and VRAM are underutilized. 

    The only hope is that FS 2024 will have this aspect improved, even though FS 2024 will be an XBox Series S title as well.

    Sadly, we will never see again in MSFS the graphics quality that it had when it was still a PC game only:

     


  4. LOL, I posted the pre-alpha video in the reduced LOD thread today, to show how the graphics and LOD / draw distance have been degraded through the years, and it's been removed completely after a few minutes, without even a notification on my account or a "tagged by the community". 

    Now they started removing posts without leaving any trace. Absolutely pathetic.

    Enjoy and share 😄

     

     

    • Like 2

  5. 28 minutes ago, bobcat999 said:

    It is complex software and not easy to iron out all bugs, but it feels like it has been a beta for MSFS2024 for the last three and a half years.  I have never known users face so much frustration with any other piece of software.

    Idem...

    Hopefully FS 2024 won't be a beta for FS 2028 😄

    • Like 1

  6. On 2/24/2024 at 9:48 PM, CaptKornDog said:

    I haven’t been; more often than not, loading the A310 results in a CTD for me.  Only way for me to resolve them has been a full reboot and loading into another default aircraft it seems.

    Annoying.  I can’t wait for a fix.

    Same here. Don't hold your breath, it's pretty much abandonware since the payware A300 release.


  7. For me it's smooth and stable for now, even horizon panning and bloom stuttering seem improved.

    One thing I noticed - and found confirmation in another thread - is that ground handling and landings have become even easier than before. Even small GA aircraft seem to be on rails.

    I will have a better idea after further testing anyway.


  8. 58 minutes ago, Mace said:

    Can't -2 and -3 series card owners already do that with the frame gen mod?   Or is this some more "official-ish" way of doing it?

    Yes, when implemented it will be not only more official and supported, but also not affected by flickering of static elements (ATC window, handlebar, subtitles...), which will be excluded from the frame elaboration. 

    • Like 1
    • Upvote 1

  9. 1 hour ago, bobcat999 said:

    Those interrupts have no advantage in my opinion, and in fact can be quite detrimental.  I already have one - it's called the wife - she seems to interrupt me every few minutes when I'm on MSFS!  :unsure:

    But remember... no interrupts, no in-put!!! 🙂

    • Like 1

  10. 39 minutes ago, sonny147 said:

    Oh DooooH haha 😁, thanks for the info !. by the why my NCP/SYS Info says IRQ not used , so has you said i think the MSI tool is no use to me ? , thanks again for the explanation

    Correct, save the time and ignore the MSI utility for your GPU. Welcome

    • Like 1

  11. 51 minutes ago, sonny147 said:

    oh i wished i knew what you talking about !! lol 🥴

    Basically interrupts are needed in order to process any input (for example a keypress). Each time you do something (move your mouse, press a key, move your stick, etc.) the system has to stop its elaboration for a short time in order to process the input. 

    With the old-style interrupt request (IRQ) system, there is a limited number of hardware lines that can address the requests and peripherals and devices can cause overlaps, since IRQs are shared.

    With the MSI system, the interrupts are requested by writing a value in memory. Having a portion of memory at its disposal, the command is delivered along with the interrupt request, preventing a device query on what is the nature of the input and thus minimizing the latency.

    P.S. MSI = Message Signaled-Based Interrupts, not the motherboard manufacturer 🙂

    • Like 2
×
×
  • Create New...