Pink background color sometimes in eevee #68585
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#68585
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-8.1-6.3.9600 64 Bits
Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 10.18.14.5067
Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash:
f6cb5f5449
Worked: (optional)
Short description of error
Sometimes it renders a pink background.
Exact steps for others to reproduce the error
Open blender, change to "shading workspace". In the cube's material I add a voronoi texture (I tried with wave or noise and it happens too) and a "color ramp" to the color of the default "principled shader"
I move ONLY the sliders or the interpolation of the "color ramp" and render with f12, default eevee. Sometimes the final render render is gray, sometimes is pink.
Everithig is the dafault scene except the "voronoi texture" and the "color ramp"
pruebas.blend
Added subscriber: @JoseAntonio0
Added subscriber: @JacquesLucke
I cannot reproduce the issue. When I open the file and render it, there is no pink.
Can you check that your driver is up to date?
Also, when I open the file, the pattern on the cube looks quite different.
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.
Added subscriber: @ZedDB
@ZedDB is this supported hardware?
Added subscribers: @fclem, @Jeroen-Bakker
@JacquesLucke yes it is supported.
@fclem, @Jeroen-Bakker 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.
BUTif I restart blender and open a file (I can use the default file, my file or any other file) andimmediately 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.
after this "normal" render if I switch the viewport to "render preview" I get this pink preview.
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.
Added subscriber: @rvectors
System Information
OS: win 10 1903
GPU 1070 GTX
Blender Version
2.80 (sub 75)
This bug seems to be as reported in #64363
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.
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.
Added subscriber: @asingh
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
Added subscriber: @iss
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
@JoseAntonio0 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
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
@JoseAntonio0 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 itIS 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.
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscriber: @Nis2
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. blender.zip
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
@Nis2 What is your system-info.txt? I could not load your apitrace here (seems like the shaders don't compile).
It seems the original issue is linked to the Intel Driver being old, buggy and deprecated (because of windows 7/8).
It is indeed on intel windows 7 (i reinstalled 2.83 and the issue is still there).system-info.txt
Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs User Info'
https://downloadcenter.intel.com/product/81496/Intel-HD-Graphics-4600 mentions the current driver version being at 15.36.40.5162, yet your system-info.txt mentions 10.18.14.5074.
Not totally sure we are talking about the same numbers here, but as a last chance to proceed with this report, could you check if installing drivers from that site has a positive impact?
This is a DELL computer. I can't install Intel's driver, the installation program checks for the configuration and reject my system.
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
@fclem: out of ideas, is there anything more we can do here?
I tried on 2.90.1 and cannot reproduce anymore (or at least cannot reproduce easily).
Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Nice to know latest versions are more stable! Closing then.
Feel free to reopen if the bug comes back.
If the problem appear again, post the result of launching blender using the
blender_debug_gpu.cmd
batch file.I tried on 2.90.1 too and this problem seems totally solved.
Thank you very much.