Announcement

Collapse
No announcement yet.

Blender 2.90 Released With Intel Embree Usage, Broader NVIDIA OptiX Support

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

  • Blender 2.90 Released With Intel Embree Usage, Broader NVIDIA OptiX Support

    Phoronix: Blender 2.90 Released With Intel Embree Usage, Broader NVIDIA OptiX Support

    Blender 2.90 is out as a huge feature update to this widely-used, cross-platform and open-source 3D modeling solution...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Nothing for AMD, CPU or GPU ?

    Comment


    • #3
      Originally posted by Danny3 View Post
      Nothing for AMD, CPU or GPU ?
      Afaik in 2,90 Optix denoiser can be used on any GPU and CPU.

      Comment


      • #4
        Originally posted by Danny3 View Post
        Nothing for AMD, CPU or GPU ?
        Specifically like the CUDA stuff, not that I remember, but embree should run smoothly on ryzen CPUs, several years ago AMD had split the uber OpenCL kernel from Cycles in several pieces, which improved it's perf on AMD GPU.

        Maybe with the release of CDNA, AMD will invest moreon Blender, but there's a limit on what they can do simultaneously with the amount of devs they have

        Comment


        • #5
          Remember all the Optix and Cuda base denoiser was contributed by Nvidia, so it works only on Nvidia cards. What is new, is support for all cards from maxwell to current gen, since before, only RTX cards were supported. For AMD just use the Open Image Denoiser. It works on all kind of CPU's. It's not a bias towards nvidia, it just nvidia contributed themselves with the code.

          For AMD Cycles, unfortunately OpenCL limitations are the showstopper. Devs are doing their best, but there's hope the next gen of GPU from AMD can allow feature parity between Nvidia and AMD.
          Last edited by stargeizer; 31 August 2020, 06:06 PM.

          Comment


          • #6
            Originally posted by stargeizer View Post
            Remember all the Optix and Cuda base denoiser was contributed by Nvidia, so it works only on Nvidia cards. What is new, is support for all cards from maxwell to current gen, since before, only RTX cards were supported. For AMD just use the Open Image Denoiser. It works on all kind of CPU's. It's not a bias towards nvidia, it just nvidia contributed themselves with the code.

            For AMD Cycles, unfortunately OpenCL limitations are the showstopper. Devs are doing their best, but there's hope the next gen of GPU from AMD can allow feature parity between Nvidia and AMD.
            Theoretically HIP can be used to substitute CUDA, but first we need to have ROCm on RDNA.
            Meanwhile I don't think OSS developers will purchase any CDNA card, unless there are <500$ options

            Comment


            • #7
              Usually, Blender Foundation get GPU's directly from AMD and Nvidia, and then they send them to the main developers who required them. Since they are working on the Amsterdam headquarters, they have access to hardware. (Even Apple had sent to BF development machines and granted dev accounts, until Apple revoked and asked their machines back, some time ago).

              Of course there's the problem of platform support (Linux, windows), but AMD has hired OSS developers working on it, so i think is just a matter of time proper support is added, at least the required support to allow GPU accelerated software to run on AMD cards on Linux, that is.

              Comment


              • #8
                Michael, I think you missed that it also has initial Wayland support! I had to go through their entire news post to find it, but it is there, hidden in the depths!



                Linux
                • Linux now has initial Wayland support, when building the WITH_GHOST_WAYLAND option. Some features are still missing in this implementation and X11 remains used by default for now.

                Comment

                Working...
                X