Eevee and pixelated render #72447
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#72447
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-7-6.1.7601-SP1 64 Bits
Graphics card: Intel(R) HD Graphics P530 Intel 4.4.0 - Build 20.19.15.4285
Blender Version
Broken: version: 2.82 (sub 5), branch: master, commit date: 2019-12-13 20:35, hash:
c6ba941339
Worked: (do not have the version at hand, but will obtain one if needed). It worked fine with the version a few days ago.
Short description of error
The #72439 thread has been closed so I'm not sure if I should start a new bug report or open a new one....
I had logged this as a bug, but it was apparently due to old drivers (?) it worked in a version a few days ago. I have updated the drivers and it is still rendering pixels.
It does not show in this bug report but I do have an NVIDIA quadro card in this computer. And 2.81 renders juts fine. Also the version of 2.82 early this week renders just fine as well.
Exact steps for others to reproduce the error
Open up blender with default cube. Use viewport render, and move the principled shader setting to greater than zero.
Added subscriber: @Lteng
Added subscriber: @EAW
Hi @Lteng,
Thank you for the clarification.
Could you attach a system-info.txt to this report? You can generate one by selecting
Save System Info
under theHelp
menu.I am not able to reproduce your bug using a less powerful card and an older version of Windows.
System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35
Blender Version
2.82 (sub 5), branch: master, commit date: 2019-12-13 17:59, hash:
c4203ef17d
Hi, I have attached the system info: (don't know if its because this computer is a laptop with laptop versions of quadro...). But as I've mentioned it worked a few days ago. Very fast and nice too. But this version I used last night does this 80's ATARI thing.
system-info.txt
The settings under CUDA are just for Cycles rendering, unchecking them won't (at least shouldn't) affect EEVEE.
For EEVEE rendering, Blender is using
Hi Evan.
Your suggestion worked. However I never had to do this before. Did this version of 2.82 overlook my card for some reason? Is this still considered a "bug" then or is this some user setting thing that needs instructions (I would never have known to do this without your suggestions). Thanks for you help.
Added subscriber: @Regnas
Yes, I can confirm this bug. It used to work just fine a few days ago.
Now when switching to rendered view this error appears. Also if you render the image, it will render a "broken" image.
See:
2019-12-15_04-07-35.mp4
Added subscriber: @mano-wii
This issue has been reported at other times, and has been resolved by updating the Intel graphics driver.
https://downloadcenter.intel.com/product/88350/Intel-HD-Graphics-P530
No it's not the graphics driver update only. I have done that and it is still rendering wonky. What solved it for me was actually telling Blender to use my Nvidia card for rendering and NOT to auto select. Because for some reason this version is ignoring my graphics card. This problem did not exist in a version a few days before, so this driver thing can't suddenly become a problem... can it?
The computer settings that define which GPU to use.
Each application has a configuration in favor of power consumption or performance.
The GPU is chosen based on this configuration.
Probably something has changed outside of Blender.
The reported case is a problem with the Intel driver and has probably been fixed in later versions.
HI,
My computer settings did not change between these versions. These two versions are a few days apart, and updating my driver did not help. However, Regnas' suggestions fixed it for me. So the thing now is that I have no idea if this is considered a user setting error (which will help if there is some documentation / instructions for it) or if this is a bug bug, or something else unrelated to either.
Changed status from 'Open' to: 'Archived'
Apologies, due to a family medical emergency I wasn't able to finish my triaging of this report.
@Lteng It might be the case that EEVEE always has been running the Intel(R) HD Graphics P530 as OpenGL render, and there was a patch to Blender that happened last week that caused this display issue with that chip and driver. But for you, the real issue (as I see it) was that your OS was telling Blender to use the integrated graphics instead of your dedicated NVIDIA hardware. This is documented in the manual, but perhaps that section could be better fleshed out with a picture or a link telling users more specifically how to change the setting. Also, this documentation is harder to find in the 2.82 manual than it was in the 2.80 in my opinion.
https://docs.blender.org/manual/en/dev/troubleshooting/gpu/windows/nvidia.html#laptops
I will look into improving that section of the manual, and close this report.
Changed status from 'Archived' to: 'Resolved'
Good news @Lteng! Your report in combination with another user's supplied working version in their report allowed us to narrow down when this issue started occurring to a 48 hour period.
This issue has now been resolved by D6563
See https://developer.blender.org/T73296#857222 for more details if you are curious.
Awesome! Thanks.