@Alaska (Alaska) Thank so much so detailed explanation! So we don`t must losing hope for supporting HIP on old AMD GPU and LINUX in near future?

In T96651#1326574, @Thomas Dinges (dingto) wrote:

You can disable the Denoiser in the Render Properties, just disable the checkbox. https://docs.blender.org/manual/en/latest/render/cycles/render_settings/sampling.html#denoising

@Alaska (Alaska)
Thanks a lot for calm and detail explanation! And why you drop OpenCL if it works with new and old Radeons? So "green camp"(nvidia) with CUDA for you is looking attractive than amd, why? Because nividia have better drivers and technologies like cuda? So more open politics of Amd and GNU FSF philosophy is loosing to proprietary world?

In T96651#1326281, @Thomas Dinges (dingto) wrote:

Just disable Open Image Denoiser, this requires a CPU with SSE4.1. Rendering with Cycles (without Denoiser) is still possible with SSE2 and up.

In T96614#1325799, @Alaska (Alaska) wrote:

Feature requests are not to be made on this website. This website is for reporting bugs and for developers to make tasks detailing projects they're working on. This post is not one of those. Hence I will close it.

In T93837#1267755, @Thomas Dinges (dingto) wrote:

See the release schedule here: https://developer.blender.org/project/view/135/

EEVEE is not affected by this change, never used OpenCL.

In T93837#1267730, @Thomas Dinges (dingto) wrote:

https://wiki.blender.org/wiki/Reference/Release_Notes/3.0/Cycles

We are working with AMD to add support for Linux and investigate earlier generation graphics cards, for the Blender 3.1 release.

In T90679#1206550, @Jesse Yurkovich (deadpin) wrote:

If things still work using the nVidia drivers directly, this question/report should be directed to the Nouveau project instead. It might be an issue in their driver. You can also try upgrading your system's Mesa drivers as well as the 18.x version you show is very old.

As far as support, the Blender requirements only state the following[1]: Always make sure to install the latest drivers from the graphics card manufacturer website.

Besides all that, yes, the card is very old. It was released 2 years before OpenGL 3.3 was even standardized so it will most likely experience various odd issues with modern blender versions regardless of driver.

[1] https://www.blender.org/download/requirements/

21.1.1 driver Again same issue

21.1.1 driver Again same issue

@Jeroen Bakker (jbakker) Thank You, this is good news! And if speak simply words, for casual people, how complex this problem? And how long it can take to resolve?

As we all know, amd write bad drivers all time. Thus amd can take years for fix own problems.

Why Blender team must resolve amd problems?

Its a mirracle! Last alfa daily build of Blender good working on 20.12.1! rx580 I LOVE YOU!:)

The daily builds of Blender 2.92 can be downloaded from here. You will have to wait until tomorrow though, as the build bot will create the new build around midnight.

When this issue will be fixed? AMD say that Blender team must do patch for Blender. What say Blender team?

Wow! it's a miracle! How you do that? I am launch Blender 2.82 at Windows and Linux with gf9800gtx+ using old 340xx drivers - its working like a charm, Blender launch and even EEVEE correcting works!:)

Thanks a lot for reply and explanations. Its very important and helpful for me.

In T65250#690086, @Brecht Van Lommel (brecht) wrote:

This graphics card is outside the range of cards that we support:
https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/

In T60425#623463, @Artyom Abgaryan (AbgaryanFX) wrote:

This happens with BSDF Shaders

also i can report that on nouveau(kernel 4.19-4.20) i have this issue with specular https://youtu.be/LFdSW_VYpBc

I am understand thx. But in Debian 9 with nouveau on this videocard all work fine. I want to know why on tumbleweed i have issue?

And what about similar Radeon cards issue? Who can chek?

Holly sh.., unbelievable, its miracle! Its working on nouveau!
https://drive.google.com/open?id=1WbSqw13Q71okJ_uNa5OAJTNKMUQasyWm

tomorrow i try on Debian 9 with nouveau drivers and inform about result

In T57292#544150, @Philipp Oeser (lichtwerk) wrote:

Can confirm in 2.79b (official release), but not in 2.8 nor 2.79 master.

@Alexander (deepforest) : havent tracked down a particular commit, but this might be solved already.
Could you try a new 2.79 build from https://builder.blender.org/download?

If you can confirm the new build works, then this could be closed as resolved...

Yes, if i save before step 11, close blender and load it up again - no crash. But why it crashes if i not saving, closing and loading?

Who are you? Developer? My last video its clear to understand what steps needed to reproduce the bug.

Why you so angry? Look another video. To reproduce, needed duplicate curve 2-3 times.
https://youtu.be/dOEPABg2DS4

In T51342#543555, @Ray Molenkamp (LazyDodo) wrote:

can't reproduce, anyway you can shorten the reproduction from 'do random stuff for nearly 2 minutes' to

1 open file
2 click add new material
3 crash.

Confirmed. Blender 2.79b, Win7x64

1. Solid - viewport shading
2. several times duplicate curves
3. add Shape - Full, Fill Deformed, Depth, Extrude, Resolution
4. apply material
5. Crash

video https://youtu.be/Uv1hnFN_zqI
blend file, log https://www.mediafire.com/file/8z3390gi0pv8fne/crash-curve-material.zip/file
screenshot https://imgur.com/a/FgO1umY