crash in materials (new material) and shading #69369
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#69369
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 4000 Intel 4.0.0 - Build 9.17.10.4229
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
and crash in shading too.
Exact steps for others to reproduce the error
listen i'm a beginner and this problem broken my will please help to continue with blender.
[Based on the default startup or an attached .blend file (as simple as possible)]
and THANK YOU BLENDERS
Added subscriber: @faris-3
Added subscriber: @rjg
Your graphics driver is very old, the current version is 15.33.48.5069. Try to [update it ]] and check if that resolves the issue. Also make sure that your system fulfills the [ https:*www.blender.org/download/requirements/ | minimum requirements for running Blender 2.8.
Robert Guetzkow (rjg)
i update it and i have the minimum requirements
and it's still crash
Added subscriber: @dark999
@faris-3 Your Ivy Bridge GPU not meet (actually 2019-09-01 08:42 UCT) minimum Blender requirement as screenshot. You use an two generation older architecture than minimum Haswell, other screenshots
screenshot from Wikipedia
thank you
Added subscribers: @mano-wii, @nokipaike
@dark999 came on!
do you want to stop it?
you are providing false information, because you are not well informed about the facts.
These video cards play very well on Windows, because one of the developer @mano-wii worked directly on their stability through workarounds.
Don't make people sad with this news, and don't confuse other developers who then close bug reports for the wrong reasons.
from the driver version it is clear that it is obsolete.
the correct working version is:
renderer: 'Intel(R) HD Graphics 4000'
vendor: 'Intel'
version: '4.0.0 - Build 10.18.10.5069'
so @faris-3 download last drivers
https://downloadcenter.intel.com/product/81499/Intel-HD-Graphics-4000
and tell us if the problem is solved
(if you continue to crash then you think you could switch to windows 10, you will definitely not crash, I tested it directly.)
@nokipaike I've already linked the driver update in my answer and apparently it didn't fix the issue. BTW the most recent version is
15.33.48.5069
not10.18.10.5069
or did you mean that this is a specific version that is known to work properly?Added subscriber: @OmarEmaraDev
@rjg it's the same driver, on blender system-info.txt is reported
on my hardware, which is precisely an intel hd 4000 with these drivers, official blender 2.80 works perfectly (I'm on windows 10)
while I did tests with blender 2.81 last builds and on some more intense and heavy scenes now we have crashes when compiling shaders ...
probably due to this change by @OmarEmaraDev
GPU: Split gpu_shader_material into multiple files.
https://developer.blender.org/rB8cd0da88e55a0c0f88297a5f0f770eb40acc6219
@mano-wii do you still have the chance to check on this hardware?
@nokipaike Did you report those crashes somewhere? Can you elaborate?
This comment was removed by @nokipaike
@OmarEmaraDev
if I try to create some objects, add simple materials, and play with them, even going through the various render modes from solid to de eevee I have no crashes ..
while if I try to load some heavier scenes, like race_spaceship or mr_elephant, https://www.blender.org/download/demo-files/ as soon as I go into shader mode, or eevee_mode after a few seconds that calculates shading I get a crash.
this does not happen with official blender 2.80
here are the files that blender gives me on the gpu.
better than asking advice @mano-wii it knows this gpu well.
blender_debug_output.txt
blender_system_info.txt
here the logs of the same file, but with the other gpu (radeon hd 7600) that doesn't crash.
blender_system_info_AMD.txt
blender_debug_output_AMD.txt
if you need anything else, ask
@nokipaike This looks like an issue in Intel's OpenGL driver. I don't think I can help here, sorry.
@OmarEmaraDev GOOD NEWS. (on blender 2.81 last build)
I tried to perform the same operations starting blender with "blender_debug_gpu_glitchworkaround.cmd" file and now all works fine, no crash.
Probably with the updates you've made, you've bypassed the workarounds that were created.
here logs of same scenes but all works.
blender_system_info.txt
blender_debug_output.txt
@nokipaike Please create a new bug report in the future when you're experiencing issues, instead of adding them to an existing ticket that deals with an unrelated problem.
@rjg this happened because I investigated on this question ...
starting from this bug report.
I don't usually use this intel gpu to make 3D
Added subscriber: @brecht
@faris-3, please attach the output of Help > Save System Info.
@nokipaike, the bug report here is using the official 2.80 release. If you found new issues in 2.81, please create a separate bug report.
done.
https://developer.blender.org/T69382
@brecht
system-info.txt
system-info1.txt
@nokipaike
the problem is solved
with
last drivers
https://downloadcenter.intel.com/product/81499/Intel-HD-Graphics-4000
thank you so much you are the best @nokipaike
and thanks developers
now i can go a head with blender wohoo
@nokipaike
Changed status from 'Open' to: 'Resolved'
Closing this as resolved. @faris-3 I linked you the very same driver update in my first comment, why didn't this work for you compared to the other link?
I can test as soon as I can. But it would be nice to have a file to reproduce the problem (and create another report).
EDIT:
I just saw the new report, thanks