Cycles: Split kernel error with OpenCL #84461

New Issue

Robert Guetzkow · 2021-01-06T14:57:39+01:00

Robert Guetzkow commented

2021-01-06 14:57:39 +01:00

System Information
Operating system: Windows 10
Graphics card:

Radeon RX 570 Series
RX480 8G, 20.2.2 driver version
Radeon RX550/550 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.Q4 27.20.11027.5002

Blender Version
Broken: 2.91.0, 2.92.0
Worked: ?

Short description of error
GPU rendering fails with a split kernel error and often in combination with an OpenGL shader compilation issue due to seemingly incorrect reported extensions by the device.

Exact steps for others to reproduce the error

Configure the user preferences to use OpenCL
Set the Device to GPU in the Render Properties
Either set the Viewport Shading to Rendered or render the scene {key F12}

**System Information** Operating system: Windows 10 Graphics card: - Radeon RX 570 Series - RX480 8G, 20.2.2 driver version - Radeon RX550/550 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.Q4 27.20.11027.5002 **Blender Version** Broken: 2.91.0, 2.92.0 Worked: ? **Short description of error** GPU rendering fails with a split kernel error and often in combination with an OpenGL shader compilation issue due to seemingly incorrect reported extensions by the device. **Exact steps for others to reproduce the error** - Configure the user preferences to use *OpenCL* - Set the *Device* to *GPU* in the *Render Properties* - Either set the *Viewport Shading* to *Rendered* or render the scene {key F12}

Robert Guetzkow commented

2021-01-06 14:57:39 +01:00

Added subscribers: @rjg, @draegdrwg, @filedescriptor, @KetoSuuja, @Flampcakes, @lightbl, @AlexanderProcenko, @ridberg, @Ixed91, @untz_the_bard, @noureldin, @Brunomendesgussoni, @Atlas020, @k3ziah, @Raoni1212, @Ali420, @Balaji_X, @Streak, @Roykz792, @dgosling, @Defess, @Synergeia, @FancyRacoon, @AaronB-4, @darksmokei666, @xiq, @JSartu, @Mateja, @KainThornn, @aftamat4ik, @iamcapmurica, @MCAN, @paracosm-1, @maSK, @Askinperson5423, @Bobo_The_Imp, @gevorgsargsian, @polybots, @Hannah-Umit, @BykovSer, @devsgamingzone, @DrkCrb, @kurisuna, @Jamexx, @Valentix, @CreatorSiSo, @dixson3, @chub321, @JYoshi, @Khaled4te, @BanannedDude, @iss, @Mefwhesk, @HamzaYigitKultur-1, @KenzieMac130, @GoldyTheClown, @Wynbax, @RoyKCarollJ456, @elasesinoanda, @john-vi-cryde, @Wovchick, @Danfer-Adrian, @FelixKutt, @Attryst, @mano-wii, @user1, @ToyMaster, @brick1ng5654, @GoldWings, @Alirion-2, @emmanuelbarros43, @ShadowGaster, @Estefano, @Wanalienc, @Realowlg, @RetroVertex, @JSpeling, @recalcitrantReaper, @EAW, @AdriGG16_VTS, @KalleNaksi, @oxfefi, @earthsam, @ALCATRANZ, @Bigman, @DoctorRyanB1, @Marcelo, @chingis, @bugsheep, @Ajkad, @KuroChu, @ODoutor, @Panfranco, @Ryujin, @takytube, @leomiranda518, @greydemon, @SmokyDVI, @gsdkskhs, @VestaPhoenix, @Horkos, @gartist41, @YuriAOF, @SOLO444K, @Razvan, @gilgaMesh98, @BlenderMaster-2, @Jeroen-Bakker, @danni-4, @Alegol, @Alaska, @lichtwerk, @maxdemon, @aaj

blender-admin commented

2021-01-06 14:57:39 +01:00

#86916 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#87726 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#86897 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#86305 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#86178 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#86018 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

blender/blender-addons#85667 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#83600 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#84812 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#84688 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#84040 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#83984 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#83130 was marked as duplicate of this issue

blender-admin commented

2021-01-06 14:57:39 +01:00

#83734 was marked as duplicate of this issue

Robert Guetzkow commented

2021-01-06 14:58:18 +01:00

Added subscribers: @tymmesyde, @Melancholic.blend, @Sharacann, @arvidjonas, @jangst.1024, @SomeAB, @95pixels, @Artharus_Dominus, @Lingfox, @PanJake, @miki66, @GligDav, @GuillermoEspertino, @NoBlahBlah, @Harti, @SkarabeyDM

Robert Guetzkow commented

2021-01-06 15:11:18 +01:00

The problem with the OpenGL extension issue might be unrelated to the split kernel problem as this reportedly occurred with 20.11.1 in #84137

Robert Guetzkow commented

2021-01-11 15:34:28 +01:00

Added subscriber: @Ryder

Rafael commented

2021-01-14 14:06:53 +01:00

I ticked experimental and started to work, tried to render and crashed, just Blender this time.

I ticked experimental and started to work, tried to render and crashed, just Blender this time. ![CyclesPrroDriversNotLoading__Experimental.png](https://archive.blender.org/developer/F9578689/CyclesPrroDriversNotLoading__Experimental.png) ![CyclesPrroDriversNotLoading__Experimental-Crash.png](https://archive.blender.org/developer/F9578688/CyclesPrroDriversNotLoading__Experimental-Crash.png)

Robert Guetzkow commented

2021-01-18 11:34:44 +01:00

Added subscriber: @Bodi

Germano Cavalcante commented

2021-01-18 15:22:20 +01:00

Added subscriber: @Baszczer

Daniel Grauer commented

2021-01-26 23:59:51 +01:00

Added subscriber: @DanielGrauer

Hannah Ümit commented

2021-01-27 18:36:41 +01:00

Removed subscriber: @Hannah-Umit

Agustin commented

2021-01-29 14:30:24 +01:00

Added subscriber: @SonidosEnArmonia

Agustin commented

2021-01-29 14:30:24 +01:00

Having the same problem.. Recerting to blender 2.9.0 fixed it. But I wonder if it will work on future releases.

Davide Baldaro commented

2021-01-29 15:33:24 +01:00

Removed subscriber: @Ixed91

Germano Cavalcante commented

2021-02-17 17:49:54 +01:00

Added subscribers: @VinceOrigami, @leonardos

Bodhi commented

2021-02-25 19:58:17 +01:00

System Information
Operating system: Windows 10 Home
Graphics card: AMD Radeon Vega 3 graphics

Blender Version
Broken: 2.92.0

Short description of error
GPU rendering fails (most often Rendered Viewport Shading in the Viewport) with a split kernel error ... Split kernel error: failed to load kernel_indirect_background
....Compiling render kernels
...Split kernel error: failed to load kernel_indirect_background
Cube doesn't render (100% transparent)
Changing modes causes freeze

Exact steps for others to reproduce the error

Configure the user preferences to use OpenCL
Set the Device to GPU in the Render Properties
Either set the Viewport Shading to Rendered (or render the scene, except rendering works sometimes)

**System Information** Operating system: Windows 10 Home Graphics card: **AMD Radeon Vega 3 graphics** **Blender Version** Broken: 2.92.0 **Short description of error** GPU rendering fails (most often Rendered Viewport Shading in the Viewport) with a split kernel error ... Split kernel error: failed to load kernel_indirect_background ....Compiling render kernels ...Split kernel error: failed to load kernel_indirect_background Cube doesn't render (100% transparent) Changing modes causes freeze **Exact steps for others to reproduce the error** Configure the user preferences to use OpenCL Set the Device to GPU in the Render Properties Either set the Viewport Shading to Rendered (or render the scene, except rendering works sometimes)

Steven Pickles commented

2021-02-26 07:57:35 +01:00

Removed subscriber: @xiq

Germano Cavalcante commented

2021-03-02 13:57:06 +01:00

Added subscriber: @GregAnico

Germano Cavalcante commented

2021-03-03 21:22:41 +01:00

Added subscriber: @PRAYTHEPO

Simon Sommer commented

2021-03-03 21:46:54 +01:00

Removed subscriber: @CreatorSiSo

Germano Cavalcante commented

2021-03-08 20:22:10 +01:00

Added subscriber: @Null69

Manuel Fernando Ortega Ruiz commented

2021-03-09 05:12:41 +01:00

Added subscriber: @Amerr

ersin commented

2021-03-14 17:19:44 +01:00

Added subscriber: @kadboblend

ersin commented

2021-03-14 17:19:44 +01:00

Hey there,

had the same problems with cycles viewport render with my RX580 since blender 2.8
This solution worked for me blender 2.92:
Render your image to load all the kernels F12. After the kernels are loaded you can cancel the render.
Now the render preview in the Viewport should work.

Hey there, had the same problems with cycles viewport render with my RX580 since blender 2.8 This solution worked for me blender 2.92: Render your image to load all the kernels F12. After the kernels are loaded you can cancel the render. Now the render preview in the Viewport should work.

I did must have done it commented

2021-03-19 13:39:55 +01:00

i can cofnirm that in latest 21.3.1 Beta as of time of posting this it is still broken, i understand it is a difficult problem but it is so disappointing that AMD has no regard to make it work on softer they invest money on and actually donate their own developers to help develop it but they cant enable it to work in their own driver for 6 months now. what a disappointment from amd, if i get a chance to sell my rx 6800 and buy nvidia i will certainly do it without so much as a blink. someone please remind me to not buy amd gpu every again!

Manuel Fernando Ortega Ruiz commented

2021-03-19 14:29:59 +01:00

In #84461#1132548, @leonardos wrote:
i can cofnirm that in latest 21.3.1 Beta as of time of posting this it is still broken, i understand it is a difficult problem but it is so disappointing that AMD has no regard to make it work on softer they invest money on and actually donate their own developers to help develop it but they cant enable it to work in their own driver for 6 months now. what a disappointment from amd, if i get a chance to sell my rx 6800 and buy nvidia i will certainly do it without so much as a blink. someone please remind me to not buy amd gpu every again!

Not even sure this is entirely on AMD given that 2.90 and down still work perfectly.

> In #84461#1132548, @leonardos wrote: > i can cofnirm that in latest 21.3.1 Beta as of time of posting this it is still broken, i understand it is a difficult problem but it is so disappointing that AMD has no regard to make it work on softer they invest money on and actually donate their own developers to help develop it but they cant enable it to work in their own driver for 6 months now. what a disappointment from amd, if i get a chance to sell my rx 6800 and buy nvidia i will certainly do it without so much as a blink. someone please remind me to not buy amd gpu every again! Not even sure this is entirely on AMD given that 2.90 and down still work perfectly.

I did must have done it commented

2021-03-19 15:34:38 +01:00

In #84461#1132583, @Amerr wrote:

In #84461#1132548, @leonardos wrote:
i can cofnirm that in latest 21.3.1 Beta as of time of posting this it is still broken, i understand it is a difficult problem but it is so disappointing that AMD has no regard to make it work on softer they invest money on and actually donate their own developers to help develop it but they cant enable it to work in their own driver for 6 months now. what a disappointment from amd, if i get a chance to sell my rx 6800 and buy nvidia i will certainly do it without so much as a blink. someone please remind me to not buy amd gpu every again!

Not even sure this is entirely on AMD given that 2.90 and down still work perfectly.

ofcourse its amd. my eevee shaders take 10 minutes to compile but on opensource shaders in linux they take 30 seconds. if they bothered to take a clue from open source drivers they would made it 20 times better but they cba with that, important thing cyberpunk works properly with radeonboost and antilag works with dx12

> In #84461#1132583, @Amerr wrote: >> In #84461#1132548, @leonardos wrote: >> i can cofnirm that in latest 21.3.1 Beta as of time of posting this it is still broken, i understand it is a difficult problem but it is so disappointing that AMD has no regard to make it work on softer they invest money on and actually donate their own developers to help develop it but they cant enable it to work in their own driver for 6 months now. what a disappointment from amd, if i get a chance to sell my rx 6800 and buy nvidia i will certainly do it without so much as a blink. someone please remind me to not buy amd gpu every again! > > Not even sure this is entirely on AMD given that 2.90 and down still work perfectly. ofcourse its amd. my eevee shaders take 10 minutes to compile but on opensource shaders in linux they take 30 seconds. if they bothered to take a clue from open source drivers they would made it 20 times better but they cba with that, important thing cyberpunk works properly with radeonboost and antilag works with dx12

ersin commented

2021-03-19 21:52:22 +01:00

Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals

I did must have done it commented

2021-03-20 06:28:51 +01:00

In #84461#1132838, @kadboblend wrote:
Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals

if you can tell me where i can get this pro driver then i will go download it, but to my knowledge there is no such thing on amd.

> In #84461#1132838, @kadboblend wrote: > Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals if you can tell me where i can get this pro driver then i will go download it, but to my knowledge there is no such thing on amd.

Manuel Fernando Ortega Ruiz commented

2021-03-20 06:40:31 +01:00

In #84461#1133006, @leonardos wrote:

In #84461#1132838, @kadboblend wrote:
Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals

if you can tell me where i can get this pro driver then i will go download it, but to my knowledge there is no such thing on amd.

Here you go https://www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q4

> In #84461#1133006, @leonardos wrote: >> In #84461#1132838, @kadboblend wrote: >> Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals > > if you can tell me where i can get this pro driver then i will go download it, but to my knowledge there is no such thing on amd. Here you go https://www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q4

I did must have done it commented

2021-03-20 07:12:31 +01:00

In #84461#1133009, @Amerr wrote:

In #84461#1133006, @leonardos wrote:

In #84461#1132838, @kadboblend wrote:
Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals

if you can tell me where i can get this pro driver then i will go download it, but to my knowledge there is no such thing on amd.

Here you go https://www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q4

Those are for radeon pro series graphics cards. It clearly says on its page the list of supported gpu's and rx 6000 series is not on that list. Is there a good reason why you suggesting me a driver that is not supported on my gpu? What am I missing?

> In #84461#1133009, @Amerr wrote: >> In #84461#1133006, @leonardos wrote: >>> In #84461#1132838, @kadboblend wrote: >>> Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals >> >> if you can tell me where i can get this pro driver then i will go download it, but to my knowledge there is no such thing on amd. > > Here you go https://www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q4 Those are for radeon pro series graphics cards. It clearly says on its page the list of supported gpu's and rx 6000 series is not on that list. Is there a good reason why you suggesting me a driver that is not supported on my gpu? What am I missing?

Manuel Fernando Ortega Ruiz commented

2021-03-20 08:04:34 +01:00

In #84461#1133015, @leonardos wrote:

In #84461#1133009, @Amerr wrote:

In #84461#1133006, @leonardos wrote:

In #84461#1132838, @kadboblend wrote:
Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals

if you can tell me where i can get this pro driver then i will go download it, but to my knowledge there is no such thing on amd.

Here you go https://www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q4

Those are for radeon pro series graphics cards. It clearly says on its page the list of supported gpu's and rx 6000 series is not on that list. Is there a good reason why you suggesting me a driver that is not supported on my gpu? What am I missing?

It's not on the list but it should work, at the very least I know they work for the series 5000 and down

> In #84461#1133015, @leonardos wrote: >> In #84461#1133009, @Amerr wrote: >>> In #84461#1133006, @leonardos wrote: >>>> In #84461#1132838, @kadboblend wrote: >>>> Make sure you installed the latest amd pro driver as it’s suggested in the blender manuals >>> >>> if you can tell me where i can get this pro driver then i will go download it, but to my knowledge there is no such thing on amd. >> >> Here you go https://www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q4 > > Those are for radeon pro series graphics cards. It clearly says on its page the list of supported gpu's and rx 6000 series is not on that list. Is there a good reason why you suggesting me a driver that is not supported on my gpu? What am I missing? It's not on the list but it should work, at the very least I know they work for the series 5000 and down

ersin commented

2021-03-20 08:12:08 +01:00

Unfortunately the rx6800 is not supported. For my rx580 it solved the issue with open cl GPU rendering and viewport rendering.

I did must have done it commented

2021-03-20 08:42:51 +01:00

In #84461#1133046, @kadboblend wrote:
Unfortunately the rx6800 is not supported. For my rx580 it solved the issue with open cl GPU rendering and viewport rendering.

Interesting.. why dont they list it then? I imagine a lot of people with rx 400 and 500 would solve the problem if they knew it worked

> In #84461#1133046, @kadboblend wrote: > Unfortunately the rx6800 is not supported. For my rx580 it solved the issue with open cl GPU rendering and viewport rendering. Interesting.. why dont they list it then? I imagine a lot of people with rx 400 and 500 would solve the problem if they knew it worked

Alexander commented

2021-03-20 08:44:15 +01:00

AMD RX590 video card, system crash on any driver version in Cycles. I gave up the idea of buying AMD video cards forever. This problem has not been solved for a very long time.

Rafael commented

2021-03-20 18:32:24 +01:00

In #84461#1133072, @aaj wrote:
AMD RX590 video card, system crash on any driver version in Cycles. I gave up the idea of buying AMD video cards forever. This problem has not been solved for a very long time.

Use LuxCore Render, way better than cycles, faster and godly stable with amd cards, it's free you can put inside Blender or use it as standalone. \o/
BF invested too much on cycles, don't know why they just don't absorb LuxCore Render as it works with all brands, i don't think that's gonna change before 3.0... anyway... the fun fact that a open source program relies heavily and almost esclusively with proprietary tech... other thing that i don't understand is why they don't hire the creator ofLuCore render as that guy really knows how to render with opencl, gl, etc.

https://luxcorerender.org/

> In #84461#1133072, @aaj wrote: > AMD RX590 video card, system crash on any driver version in Cycles. I gave up the idea of buying AMD video cards forever. This problem has not been solved for a very long time. Use LuxCore Render, way better than cycles, faster and godly stable with amd cards, it's free you can put inside Blender or use it as standalone. \o/ BF invested too much on cycles, don't know why they just don't absorb LuxCore Render as it works with all brands, i don't think that's gonna change before 3.0... anyway... the fun fact that a open source program relies heavily and almost esclusively with proprietary tech... other thing that i don't understand is why they don't hire the creator ofLuCore render as that guy really knows how to render with opencl, gl, etc. https://luxcorerender.org/

I did must have done it commented

2021-03-20 19:40:15 +01:00

In #84461#1133170, @DrkCrb wrote:

In #84461#1133072, @aaj wrote:
AMD RX590 video card, system crash on any driver version in Cycles. I gave up the idea of buying AMD video cards forever. This problem has not been solved for a very long time.

Use LuxCore Render, way better than cycles, faster and godly stable with amd cards, it's free you can put inside Blender or use it as standalone. \o/
BF invested too much on cycles, don't know why they just don't absorb LuxCore Render as it works with all brands, i don't think that's gonna change before 3.0... anyway... the fun fact that a open source program relies heavily and almost esclusively with proprietary tech... other thing that i don't understand is why they don't hire the creator ofLuCore render as that guy really knows how to render with opencl, gl, etc.

https://luxcorerender.org/

Problem with all addon renderers for blender is that they use double the amount of vram then cycles because data has to be duplicated one instance of data on blender and one instance of exact data on renderer. if you have 8gb of vram effectively you have 4gb of vram etc. that in itself is horrible limitation that all additional renderers suffer from. cycles doesnt have this problem since it is tightly integrated with blender. furthermore, luxcore is sure nice for architecural interior renderings but there is no way it can keep up pace of development that cycles have since luxcore has virtualy no funding. while yes it can produce some nice renders and has some advanced edges over cycles, it is imbalanced like its better in some areas worse in some others, overall it is more bare bones renderer with some nice bells and whistles that will come to cycles sooner or later like light cache and stuff. and luxcore is not exempt from kernel errors, its just that in luxcore you dont know when they will strike. here at least i know it doesnt work and thats the end of it.

give your rx 6800 to your niece to play cyberpunk without raytracing thats the only thing its good for, like what does she know what raytracing even is at least she will have radeon boost and antilag will be O K im sure she will figure out what radeon boost is since amd control panel is getting more and more intrusive on each version. first they start with annoying overlays next thing they are displaying ads in your brain to justify lower price of already over expensive hardware mark my words your niece is not safe when amd gpu division strikes back.

bottom line - get nvidia for professional work at least renderer will fire up if nothing else.

> In #84461#1133170, @DrkCrb wrote: >> In #84461#1133072, @aaj wrote: >> AMD RX590 video card, system crash on any driver version in Cycles. I gave up the idea of buying AMD video cards forever. This problem has not been solved for a very long time. > > Use LuxCore Render, way better than cycles, faster and godly stable with amd cards, it's free you can put inside Blender or use it as standalone. \o/ > BF invested too much on cycles, don't know why they just don't absorb LuxCore Render as it works with all brands, i don't think that's gonna change before 3.0... anyway... the fun fact that a open source program relies heavily and almost esclusively with proprietary tech... other thing that i don't understand is why they don't hire the creator ofLuCore render as that guy really knows how to render with opencl, gl, etc. > > https://luxcorerender.org/ Problem with all addon renderers for blender is that they use double the amount of vram then cycles because data has to be duplicated one instance of data on blender and one instance of exact data on renderer. if you have 8gb of vram effectively you have 4gb of vram etc. that in itself is horrible limitation that all additional renderers suffer from. cycles doesnt have this problem since it is tightly integrated with blender. furthermore, luxcore is sure nice for architecural interior renderings but there is no way it can keep up pace of development that cycles have since luxcore has virtualy no funding. while yes it can produce some nice renders and has some advanced edges over cycles, it is imbalanced like its better in some areas worse in some others, overall it is more bare bones renderer with some nice bells and whistles that will come to cycles sooner or later like light cache and stuff. and luxcore is not exempt from kernel errors, its just that in luxcore you dont know when they will strike. here at least i know it doesnt work and thats the end of it. give your rx 6800 to your niece to play cyberpunk without raytracing thats the only thing its good for, like what does she know what raytracing even is at least she will have radeon boost and antilag will be O K im sure she will figure out what radeon boost is since amd control panel is getting more and more intrusive on each version. first they start with annoying overlays next thing they are displaying ads in your brain to justify lower price of already over expensive hardware mark my words your niece is not safe when amd gpu division strikes back. bottom line - get nvidia for professional work at least renderer will fire up if nothing else.

Falk David commented

2021-03-21 14:33:40 +01:00

@DrkCrb @leonardos Friendly reminder that this is the bug tracker and that all discussions should stay on the topic of this task. Any other discussions can be continued on our community websites.

I did must have done it commented

2021-03-21 18:29:51 +01:00

In #84461#1133461, @filedescriptor wrote:
@DrkCrb @leonardos Friendly reminder that this is the bug tracker and that all discussions should stay on the topic of this task. Any other discussions can be continued on our community websites.

Yes thankses for remind me! I had totally forget this its a bug tracker! Silly me! EDIT: but i think that such a severe bug not be fixed so long contributed significantly to my dementia, so i think i can be forgiven, yes?

> In #84461#1133461, @filedescriptor wrote: > @DrkCrb @leonardos Friendly reminder that this is the bug tracker and that all discussions should stay on the topic of this task. Any other discussions can be continued on our community websites. Yes thankses for remind me! I had totally forget this its a bug tracker! Silly me! EDIT: but i think that such a severe bug not be fixed so long contributed significantly to my dementia, so i think i can be forgiven, yes?

Gary Thornburg commented

2021-03-21 20:19:50 +01:00

Removed subscriber: @KainThornn

Germano Cavalcante commented

2021-03-26 19:51:27 +01:00

Added subscriber: @Sveen

blender-admin commented

2021-03-29 22:58:19 +02:00

This issue was referenced by 91c44fe885

This issue was referenced by 91c44fe88547ee4e4d78858d816068876a3db3c4

Brecht Van Lommel commented

2021-03-30 00:10:53 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2021-03-30 00:10:53 +02:00

Possible workaround in 91c44fe885.

I could not reproduce the issue myself, so any confirmation if this avoids the problem would help. (Once the Buildbot is updated, the Windows one seems to be down right now but should be up again soon.)
https://builder.blender.org/download/

Possible workaround in 91c44fe885. I could not reproduce the issue myself, so any confirmation if this avoids the problem would help. (Once the Buildbot is updated, the Windows one seems to be down right now but should be up again soon.) https://builder.blender.org/download/

I did must have done it commented

2021-03-30 02:53:50 +02:00

In #84461#1138142, @brecht wrote:
Possible workaround in 91c44fe885.

I could not reproduce the issue myself, so any confirmation if this avoids the problem would help. (Once the Buildbot is updated, the Windows one seems to be down right now but should be up again soon.)
https://builder.blender.org/download/

looks like amd is back on cycles after long hiatus. i can confirm that cycles its working since your patch on my amd gpu. i dont even know what nanovb is? is it something to speed up volumetrics? well at least it works now, not everyone needs faster volumetrics.

anyways, works fine now. thanks !

> In #84461#1138142, @brecht wrote: > Possible workaround in 91c44fe885. > > I could not reproduce the issue myself, so any confirmation if this avoids the problem would help. (Once the Buildbot is updated, the Windows one seems to be down right now but should be up again soon.) > https://builder.blender.org/download/ looks like amd is back on cycles after long hiatus. i can confirm that cycles its working since your patch on my amd gpu. i dont even know what nanovb is? is it something to speed up volumetrics? well at least it works now, not everyone needs faster volumetrics. anyways, works fine now. thanks !

I did must have done it commented

2021-03-30 08:29:00 +02:00

In #84461#1138142, @brecht wrote:
Possible workaround in 91c44fe885.

I could not reproduce the issue myself, so any confirmation if this avoids the problem would help. (Once the Buildbot is updated, the Windows one seems to be down right now but should be up again soon.)
https://builder.blender.org/download/

actually after some more testing it appears it still has severe problems with compiling opencl kernels. at least in my case, it appears to work correctly if i 1st plug in an exr map into the background node and then into world. BUT, if i just open blender and just switch to gpu rendering with only background node plugged in then it will fail again :

OpenCL error (-52): CL_INVALID_KERNEL_ARGS in clEnqueueNDRangeKernel
OpenCL error: CL_INVALID_KERNEL_ARGS in clEnqueueNDRangeKernel()
OpenCL error: CL_INVALID_KERNEL_ARGS in clEnqueueNDRangeKernel(cqCommandQueue, kernel, 2, NULL, global_size, NULL, 0, NULL, NULL) (D:\_blender\_git\2.93\blender\intern\cycles\device\opencl\device_opencl_impl.cpp:1263)

so again, it works if map is plugged into background and it appears to work also if you disconnect the map from background but it errors if you try to use just background without first plugging in anything into it

> In #84461#1138142, @brecht wrote: > Possible workaround in 91c44fe885. > > I could not reproduce the issue myself, so any confirmation if this avoids the problem would help. (Once the Buildbot is updated, the Windows one seems to be down right now but should be up again soon.) > https://builder.blender.org/download/ actually after some more testing it appears it still has severe problems with compiling opencl kernels. at least in my case, it appears to work correctly if i 1st plug in an exr map into the background node and then into world. BUT, if i just open blender and just switch to gpu rendering with only background node plugged in then it will fail again : ``` OpenCL error (-52): CL_INVALID_KERNEL_ARGS in clEnqueueNDRangeKernel OpenCL error: CL_INVALID_KERNEL_ARGS in clEnqueueNDRangeKernel() OpenCL error: CL_INVALID_KERNEL_ARGS in clEnqueueNDRangeKernel(cqCommandQueue, kernel, 2, NULL, global_size, NULL, 0, NULL, NULL) (D:\_blender\_git\2.93\blender\intern\cycles\device\opencl\device_opencl_impl.cpp:1263) ``` so again, it works if map is plugged into background and it appears to work also if you disconnect the map from background but it errors if you try to use just background without first plugging in anything into it

I did must have done it commented

2021-03-30 22:35:57 +02:00

it appears that the error happens if 1. scene is empty 2. only background node is plugged in the world output. so i guess, its not a big problem since nobody needs an empty scene. it seems to work if there is stuff in the scene or if a map is plugged in the background

Evan Wilson commented

2021-03-31 04:25:03 +02:00

In #84461#1133069, @leonardos wrote:
Interesting.. why dont they list it then? I imagine a lot of people with rx 400 and 500 would solve the problem if they knew it worked

While it frustratingly isn’t listed on the driver webpage, it is listed on page 12 of the full release notes.

The latest Pro Driver was released March 24. Link

Under “Fixed Issues” it lists:

Image corruption and stability issues in Blender application.

> In #84461#1133069, @leonardos wrote: > Interesting.. why dont they list it then? I imagine a lot of people with rx 400 and 500 would solve the problem if they knew it worked While it frustratingly isn’t listed on the driver webpage, it is listed on [page 12 of the full release notes.](https://drivers.amd.com/relnotes/amd-radeon-pro-software-for-enterprise-21.Q1.pdf) The latest Pro Driver was released March 24. [Link](https://www.amd.com/en/support/kb/release-notes/rn-pro-win-21-q1) Under “Fixed Issues” it lists: >Image corruption and stability issues in Blender application.

I did must have done it commented

2021-03-31 09:30:56 +02:00

In #84461#1138793, @EAW wrote:

In #84461#1133069, @leonardos wrote:
Interesting.. why dont they list it then? I imagine a lot of people with rx 400 and 500 would solve the problem if they knew it worked

While it frustratingly isn’t listed on the driver webpage, it is listed on page 12 of the full release notes.

The latest Pro Driver was released March 24. Link

Under “Fixed Issues” it lists:

Image corruption and stability issues in Blender application.

I gave it a try. It makes no difference for my gpu and arguebly its run worse .

> In #84461#1138793, @EAW wrote: >> In #84461#1133069, @leonardos wrote: >> Interesting.. why dont they list it then? I imagine a lot of people with rx 400 and 500 would solve the problem if they knew it worked > > While it frustratingly isn’t listed on the driver webpage, it is listed on [page 12 of the full release notes.](https://drivers.amd.com/relnotes/amd-radeon-pro-software-for-enterprise-21.Q1.pdf) > > The latest Pro Driver was released March 24. [Link](https://www.amd.com/en/support/kb/release-notes/rn-pro-win-21-q1) > > Under “Fixed Issues” it lists: >>Image corruption and stability issues in Blender application. I gave it a try. It makes no difference for my gpu and arguebly its run worse .

Karol Szczerba commented

2021-03-31 09:33:50 +02:00

Removed subscriber: @Baszczer

Muhammadali commented

2021-03-31 11:15:47 +02:00

Added subscriber: @raining3D

Muhammadali commented

2021-03-31 11:15:47 +02:00

ok so I don't know if its work for you but it did work for me and I hope it should work for you.

I have the same problem in blender:

split kernel error: failed to load kernel_indirect_background

etc.

and the solution I got is that download blender 2.8 because 2.8 work with amd gpu now I know most of u don't want to use blender 2.8 so now go to file explorer and open blender 2.8 folder and search amd now copy all of the files in result bar and now go to blender which "version you wanna use" and go to that version of blender open file location and paste it and you are done now you can use cycles rendering with amd gpu I hope this work for you

ok so I don't know if its work for you but it did work for me and I hope it should work for you. I have the same problem in blender: split kernel error: failed to load kernel_indirect_background etc. and the solution I got is that download blender 2.8 because 2.8 work with amd gpu now I know most of u don't want to use blender 2.8 so now go to file explorer and open blender 2.8 folder and search amd now copy all of the files in result bar and now go to blender which "version you wanna use" and go to that version of blender open file location and paste it and you are done now you can use cycles rendering with amd gpu I hope this work for you

Falk David commented

2021-03-31 12:36:59 +02:00

Removed subscriber: @filedescriptor

Lingfox commented

2021-03-31 13:14:29 +02:00

In #84461#1138953, @raining3D wrote:
ok so I don't know if its work for you but it did work for me and I hope it should work for you.

I have the same problem in blender:

split kernel error: failed to load kernel_indirect_background

etc.

and the solution I got is that download blender 2.8 because 2.8 work with amd gpu now I know most of u don't want to use blender 2.8 so now go to file explorer and open blender 2.8 folder and search amd now copy all of the files in result bar and now go to blender which "version you wanna use" and go to that version of blender open file location and paste it and you are done now you can use cycles rendering with amd gpu I hope this work for you

Not exactly the solution I'm looking for. For me, Cycles was also working on blender 2.91.2

> In #84461#1138953, @raining3D wrote: > ok so I don't know if its work for you but it did work for me and I hope it should work for you. > > I have the same problem in blender: > > split kernel error: failed to load kernel_indirect_background > > etc. > > and the solution I got is that download blender 2.8 because 2.8 work with amd gpu now I know most of u don't want to use blender 2.8 so now go to file explorer and open blender 2.8 folder and search amd now copy all of the files in result bar and now go to blender which "version you wanna use" and go to that version of blender open file location and paste it and you are done now you can use cycles rendering with amd gpu I hope this work for you Not exactly the solution I'm looking for. For me, Cycles was also working on blender 2.91.2

Alexander Popov commented

2021-04-02 06:23:05 +02:00

Added subscriber: @alexanderpopov

Brecht Van Lommel commented

2021-04-12 16:00:32 +02:00

Can anyone confirm that they still have this issue? I got no clear replies so far. I can't reproduce any issue with my RX 5700 XT card with latest master.

If you do still have an issue, please provide complete information so we can determine what exactly is different and try to reproduce that setup. In particular:

Graphics card name
Driver version
.blend file scene used for testing
Test with with latest Blender 2.93 from https://builder.blender.org/download/ and mention the exact git hash
Test with Blender 2.92
If using multiple GPUs, test if using just one works

The issue with empty scenes mentioned by @leonardos I have not been able to reproduce so far.

Can anyone confirm that they still have this issue? I got no clear replies so far. I can't reproduce any issue with my RX 5700 XT card with latest master. If you do still have an issue, please provide complete information so we can determine what exactly is different and try to reproduce that setup. In particular: * Graphics card name * Driver version * .blend file scene used for testing * Test with with latest Blender 2.93 from https://builder.blender.org/download/ and mention the exact git hash * Test with Blender 2.92 * If using multiple GPUs, test if using just one works The issue with empty scenes mentioned by @leonardos I have not been able to reproduce so far.

Brecht Van Lommel commented

2021-04-12 16:00:55 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Germano Cavalcante commented

2021-04-12 17:38:55 +02:00

I was able to replicate the problem the first time today with the Default Cube.

Split kernel error: failed to load kernel_holdout_emission_blurring_pathtermination_ao

But after the kernels compiled again when reloading the file, the problem disappeared.

I was also able to replicate in this simple file:
absorption_ocl_bug.blend

Split kernel error: failed to load kernel_do_volume

But the second time I tried it, the kernels compiled, however it takes forever to start previewing in the viewport.
Works well rendering via F12.

Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001
Blender Version: 2.93.0 Alpha, branch: master, commit date: 2021-04-11 20:10, hash: 09d7d88cc4

I was able to replicate the problem the first time today with the Default Cube. ``` Split kernel error: failed to load kernel_holdout_emission_blurring_pathtermination_ao ``` But after the kernels compiled again when reloading the file, the problem disappeared. I was also able to replicate in this simple file: [absorption_ocl_bug.blend](https://archive.blender.org/developer/F9930650/absorption_ocl_bug.blend) ``` Split kernel error: failed to load kernel_do_volume ``` But the second time I tried it, the kernels compiled, however it takes forever to start previewing in the viewport. Works well rendering via F12. --- Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 Blender Version: 2.93.0 Alpha, branch: master, commit date: 2021-04-11 20:10, hash: `09d7d88cc4`

Manuel Fernando Ortega Ruiz commented

2021-04-12 18:34:57 +02:00

The problem is still present for me in both 2.92 and 2.93 Alpha 09d7d88cc4

When I try to do a viewport render with GPU Compute enabled it takes a while before throwing out a Split kernel error: failed to load kernel_indirect_background error

Rendering via F12 seems to work fine in both versions

Graphics card: Radeon RX 470
Driver Version: Driver Version 20.50.03.05-210326a-365573E-RadeonSoftwareAdrenalin2020

The problem is still present for me in both 2.92 and 2.93 Alpha 09d7d88cc42a When I try to do a viewport render with GPU Compute enabled it takes a while before throwing out a `Split kernel error: failed to load kernel_indirect_background` error Rendering via F12 seems to work fine in both versions Graphics card: Radeon RX 470 Driver Version: Driver Version 20.50.03.05-210326a-365573E-RadeonSoftwareAdrenalin2020

Alexander Popov commented

2021-04-12 20:19:18 +02:00

The issue still occurs. Tested with Blender 2.93 hash 09d7d88cc42a and Blender 2.92. Here is a screen capture in case it's helpfull. I have 2 GPUs and for the test purpose I disabled one of them in the preferences.

Graphics card name: Radeon RX 580 Series
Driver version: 20.50.03.01-210310a-365275C-RadeonSoftwareAdrenalin2020 (21.3.1)
.blend file scene used for testing:

mine.blend

The issue still occurs. Tested with [Blender 2.93](https:*builder.blender.org/download/blender-2.93.0-09d7d88cc42a-windows64.zip) hash `09d7d88cc42a` and Blender 2.92. Here is a [ screen capture](https:*www.dropbox.com/s/igkj7qgs1wpmf0g/Blender-#84461.mp4?dl=0) in case it's helpfull. I have 2 GPUs and for the test purpose I disabled one of them in the preferences. - Graphics card name: Radeon RX 580 Series - Driver version: 20.50.03.01-210310a-365275C-RadeonSoftwareAdrenalin2020 (21.3.1) - .blend file scene used for testing: [mine.blend](https://archive.blender.org/developer/F9930859/mine.blend)

Lingfox commented

2021-04-13 17:04:41 +02:00

I still have this problem, if that helps.
(Sapphire Pulse) RX 5700 XT (with driver version from adrenalin 21.3.2); Blender 2.92; Default scene, viewport just won't work. Although, rendering will work.
EDIT: I still have this issue with the Adrenalin version 21.4.

I still have this problem, if that helps. (Sapphire Pulse) RX 5700 XT (with driver version from adrenalin 21.3.2); Blender 2.92; Default scene, viewport just won't work. Although, rendering will work. EDIT: I still have this issue with the Adrenalin version 21.4.

Joshua Blömer commented

2021-04-16 22:10:40 +02:00

Removed subscriber: @JYoshi

Henny Bergsma commented

2021-04-20 11:02:42 +02:00

Added subscriber: @HennyBergsma

Henny Bergsma commented

2021-04-20 11:02:42 +02:00

I have the same problem with a Radeon (TM) R7 M340. using Adrenaline 2020.

It began medio December and then it was fixed for a while mid januari. But with newer releases of Blender it came back. Ik cannot use the realtime GPU render, nor render any image with it due to a split kernel error. Today I clean reinstalled all AmD drivers, but it did not change a thing.

I have the same problem with a Radeon (TM) R7 M340. using Adrenaline 2020. It began medio December and then it was fixed for a while mid januari. But with newer releases of Blender it came back. Ik cannot use the realtime GPU render, nor render any image with it due to a split kernel error. Today I clean reinstalled all AmD drivers, but it did not change a thing.

Germano Cavalcante commented

2021-05-06 21:55:58 +02:00

Added subscribers: @PANCHO7532, @enenra

Ahmed Jarad commented

2021-05-15 09:19:35 +02:00

Added subscriber: @end_ahmed

Pratik Borhade commented

2021-05-24 18:14:57 +02:00

Added subscribers: @Punchezzzz, @PratikPB2123

Brecht Van Lommel commented

2021-05-25 12:07:45 +02:00

This may have been worked in around in 3e472d87a8, which solves an issue that could happen specifically in the viewport.

This may have been worked in around in 3e472d87a8, which solves an issue that could happen specifically in the viewport.

Philipp Oeser commented

2021-06-04 13:44:34 +02:00

After Brechts comment: just checking if this is still an issue?

Pratik Borhade commented

2021-06-04 13:53:30 +02:00

@lichtwerk , check #88521#1165792 (Author of the ticket said the problem is fixed in 3.0.0)

Lingfox commented

2021-06-05 13:00:11 +02:00

In #84461#1170898, @lichtwerk wrote:
After Brechts comment: just checking if this is still an issue?

not for me, on blender 2.93.0 (release).
But then again, the issue was also fixed back in 2.92.0 and then came back on 2.92.1 onward.

> In #84461#1170898, @lichtwerk wrote: > After Brechts comment: just checking if this is still an issue? not for me, on blender 2.93.0 (release). But then again, the issue was also fixed back in 2.92.0 and then came back on 2.92.1 onward.

Brecht Van Lommel commented

2021-06-07 14:02:00 +02:00

Changed status from 'Needs User Info' to: 'Resolved'

Brecht Van Lommel closed this issue

2021-06-07 14:02:00 +02:00

Brecht Van Lommel self-assigned this 2021-06-07 14:02:00 +02:00

Brecht Van Lommel commented

2021-06-07 14:02:00 +02:00

I'll assume it's solved then, if it comes back we can reopen the report.

Sign in to join this conversation.