Hello. I have an Intel program that checks for drivers and it says everithing is up to date.

the pattern on the cube is different because I saved the file once with that pattern BUT then I play with the sliders of the color ramp, the pattern changes every time i move the sliders and in some of the renders there is a pink colour and in other renders there is not the pink colour. It does not afect if there is a lot or black or white over the cube.

I had a lot of problems with the betas of the new 2.8 (it seems that Intel(R) HD Graphics 4600 Intel 4.3.0 is a pain) and I still have some of that betas that worked.

I opened the same blend file in this beta: "blender-2.80.0-git.411b5f3b100e-windows64" and I have taken more than 20 renders of the cube playing with the sliders, all of the renders have weird shadow edges and are darker but NONE of them is pink.

I hope I have explained it well, English is not my native language. Thank you very much for your interest.

@Sebastian Parborg (zeddb) is this supported hardware?

@Jacques Lucke (JacquesLucke) yes it is supported.

@Clément Foucault (fclem), @Jeroen Bakker (jbakker) do you have any Haswell GPUs you can test with?

Hello everybody.

I have found something interesting: the problem is not related with the "color ramp" because I rendered the default file (default cube with default material) and after a couple of renders (with the viewport in solid mode or look dev mode) the render is pink again, and then if I switch the viewport to "render preview" it is pink too.

BUT if I restart blender and open a file (I can use the default file, my file or any other file) and immediately switch the viewport to "render preview" this preview is normal now and, after this, if I render the file several times (I have done more than 20 with the viewport in any mode) the "pink problem" never happens again during the session.
All of this happens with eevee.

It seems like switching the viewport to "render preview" just after opening a file activates "something in eevee" that fixes the "pink problem"

Thank you very much.

This maybe due to texture garbage collection.. try changing the related timings in the preference panel to verify this.

I have changed the values of Blender Preferences > System > Memory & Limits "Texture Time Out" and "Garbage Collection rate" I have tried lower and higher values (I have tried it opening the default cube) and get always theese two results:

1- If I open blender, hit f12 to render the default cube. I get a "light grey" render of the cube.

If i render it more times the renders are sometimes "light grey" sometimes pink, the pink preview remains.

2- If I open blender, switch the viewport to "render preview", then there is no pink preview there. I hit f12 to render the default cube. and I get a "dark grey" render of the cube. if i render it more times the renders are all "dark grey" Everything seems OK, no pink at all.

The only diference between "light grey" and "dark grey" is switching the viewport to "render preview" before the first render. I dont know which one is the correct.

Thank you.

System Information
OS: win 10 1903
GPU 1070 GTX

Blender Version
2.80 (sub 75)

This bug seems to be as reported in T64363

For brevity, and in case others come here.

I can reproduce this error although its using Blender branch supplied by Octane (Prime 2019.1 RC3 Engine v20)

Console Error when picking render preview with EEVEE selected, default startup cube.

+++++
GPUShader: compile error:
0(12958) : error C1104: too many parameters in function call

GPUShader: compile error:
0(6532) : error C1104: too many parameters in function call

GPUShader: compile error:
0(12958) : error C1104: too many parameters in function call
+++++

Bug seems fixed in later Official branch versions.

I am using the official 2.80 version (the zip) i also used a couple of 2.81 betas and everything is the same:

Default scene, If I don't switch the viewport to "render preview", before pushing the f12 key for the first render the render is light grey and after that sometimes is pink and the "render preview" is always pink too.

If switch the viewport to "render preview", before pushing the f12 key for the first render the "render preview" is normal and the render is dark grey and after that it is never pink

Can somebody send a render of the default cube to see if it is dark or grey?

Thanks.

In T68585#756081, @D N (rvectors) wrote:

System Information
OS: win 10 1903
GPU 1070 GTX

Blender Version
2.80 (sub 75)

This bug seems to be as reported in T64363

For brevity, and in case others come here.

I can reproduce this error although its using Blender branch supplied by Octane (Prime 2019.1 RC3 Engine v20)

Console Error when picking render preview with EEVEE selected, default startup cube.

+++++
GPUShader: compile error:
0(12958) : error C1104: too many parameters in function call

GPUShader: compile error:
0(6532) : error C1104: too many parameters in function call

GPUShader: compile error:
0(12958) : error C1104: too many parameters in function call
+++++

Bug seems fixed in later Official branch versions.

System Information
OS: win 10 1903
GPU 1070 GTX
driver 436.15

Blender Version
2.80 (sub 75)

Apologies for missing your last post - just saw a status change in my junk folder.
The pink render happens whatever the viewport viewing selection.
Disabling use nodes for the background sees the issue go away, or when adjusting material settings, sometimes the pink disappears (milliseconds) and the default colours return, then flashes back to what is seen in the image below.

I was having the same problem and found the solution. For some reason if you plug in an HDRI for one of your files under the world tab surface section. It stores it there and makes it the default startup file. Just go to the World>surface and then press remove. Everything should be back to normal then.

Thank you, I have tried in but it doesn´t work for me, only switching to render mode before the first render works

In T68585#843587, @Richard Antalik (ISS) wrote:

@jose_antonio (jose_antonio) Is this still an issue with latest build? https://builder.blender.org/download/

I can not reproduce this on Windows.

I am using official portable 2.81 since december and I have tried blender-2.82-3a35301fd16d-windows64 and it is the same, the second or third render with blender just opened is pink as always,.

BUT something very weird happens:

Today I tried official portable 2.80 again, the SAME of all the renders I posted here , (I stopped using it in december because it crashed when i wanted to use an image texture) and now 2.80 doesn't render the pink image
I did something, I don't know what, betwen october and december in 2.80 that i think fixed it but I can´t redo it again in 2.81 or 2.82

In T68585#854324, @Richard Antalik (ISS) wrote:

@jose_antonio (jose_antonio) I am going over reports, and I am not sure if I understood you.

Do you mean, that if you try to render file that is uploaded to this report it is no longer pink?

I render today the file that is uploaded to this report in the exact same blender 2.80 that saved it 5 months ago and it IS NO longer pink, but:

In blender 2.81 IS pink
In blender-2.82-902209eda527-windows64 IS pink,
In blender-2.83-2e9d5ba2115c-windows64 IS pink,

I did something in 2.80 after Oct 14 2019 that changed it but I can´t reproduce it again in 2.81, 2.82 or 2.83

Thanks.

When this happens (even in 2.90 git) you get (1.0, 0.0, 1.0, 1.0) pixels from GPU_framebuffer_read_color in eevee_render_color_result. Attached is a smallish apitrace with the issue . I hope that can help.

It is indeed on intel windows 7 (i reinstalled 2.83 and the issue is still there).

This is a DELL computer. I can't install Intel's driver, the installation program checks for the configuration and reject my system.

I tried on 2.90.1 and cannot reproduce anymore (or at least cannot reproduce easily).

I tried on 2.90.1 too and this problem seems totally solved.

Thank you very much.