Announcement

Collapse
No announcement yet.

NVIDIA 440.82 Linux Driver Brings DOOM Eternal Performance Fix, Linux 5.6 Compatibility

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • V1tol
    replied
    Don't care about any fancy stuff like Wayland etc. The only question - did they fix Alt+Tab issues on any fullscreen Vulkan application? That includes everything using DXVK. I thought this is only Kwin exclusive bug, but the same happens on GNOME 3 and even XFCE. It is even mentioned on Arch wiki. On Intel there is no such issue.

    Leave a comment:


  • MastaG
    replied
    Gnome(mutter) on Wayland works using eglstreams out of the box.
    However Xwayland doesn't support eglstreams I guess? Anyways X11 apps will fall back to software rendering.
    I hope they fix that, so we can have the full Xwayland experience on Nvidia as well.

    Leave a comment:


  • birdie
    replied
    Added a workaround for Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory.

    Looks like there's a major bug in the game. Someone please ping idSoftware.

    Leave a comment:


  • increasechief
    replied
    On the best setting "Ultra Nightmare" it was using about 1.5Gb of video memory.

    Leave a comment:


  • treba
    replied
    I wished they'd simply allow distributing their firmware, allowing us to use the mesa drivers instead. Debugging against a proprietary driver is so tiresome
    But I guess they know that in the moment they do, many foss devs will start closing any issues concerning the proprietary driver as wontfix and drop or not add extra hops for it any more.

    Leave a comment:


  • bosjc
    replied
    Originally posted by aufkrawall View Post
    If they'll ever fix broken triple buffered vsync in GPU bound scenario?
    Or Wayland/XWayland. Or Freesync. Or HDR. Or Optimus. The list goes on.

    Leave a comment:


  • aufkrawall
    replied
    If they'll ever fix broken triple buffered vsync in GPU bound scenario?

    Leave a comment:


  • vhaarr
    replied
    Originally posted by eydee View Post
    It isn't Mozilla to bump the number by 10 for each new line of code. They're gonna bump the number when a major feature comes, e.g. new GPU support or anything like that.
    Mozilla doesn't bump the version number in response to anything except time, though. Releases have been on a rolling schedule since 2011.

    In other words, if the repository had no changes for 3 months, a new version would still theoretically be released.

    That said, these days Mozilla is too littered with politics for me to defend, really.

    Leave a comment:


  • bosjc
    replied
    Originally posted by eydee View Post

    It isn't Mozilla to bump the number by 10 for each new line of code. They're gonna bump the number when a major feature comes, e.g. new GPU support or anything like that.
    Historically Nvidia gets a new feature release branch out every other month with the same cadence for Betas. It has been six months since a new beta release, and five months for a new stable feature branch. No on is talking about Firefox.

    Leave a comment:


  • eydee
    replied
    Originally posted by bosjc View Post
    Been a very long time since a new feature Beta for their driver, or a new series release.
    It isn't Mozilla to bump the number by 10 for each new line of code. They're gonna bump the number when a major feature comes, e.g. new GPU support or anything like that.

    Leave a comment:

Working...
X