Crash after enabling Shadow in the viewport #66670

Closed
opened 2019-07-10 17:40:30 +02:00 by Alan · 15 comments

System Information
Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce GT 330M OpenGL Engine NVIDIA Corporation 3.3 NVIDIA-10.4.14 310.90.30.05b27

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-10 10:32, hash: 12ceea0434

Short description of error
If I enable shadows in the viewport, Blender crashes immediately.

Yes, I know, this graphics card is not supported and Eevee is not working, but still... Maybe the solution is just to hide this function from a user, if the system can't handle it.

Exact steps for others to reproduce the error

  • Open Blender
  • Make sure that Viewport Shading method is set to Solid. It doesn't matter which render engine is in use

Expand Viewport Shading options in the header, then enable Shadow

Another way to reproduce the error

  • Open Blender
  • Set render engine: Workbench
  • Switch shading method to Rendered (if it's Solid, it wouldn't crash until you switch it to Rendered after enabling shadows!)
  • Go to Properties region -> Render tab -> Options panel -> enable Shadow
**System Information** Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits Graphics card: NVIDIA GeForce GT 330M OpenGL Engine NVIDIA Corporation 3.3 NVIDIA-10.4.14 310.90.30.05b27 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-10 10:32, hash: `12ceea0434` **Short description of error** If I enable shadows in the viewport, Blender crashes immediately. Yes, I know, this graphics card is not supported and Eevee is not working, but still... Maybe the solution is just to hide this function from a user, if the system can't handle it. **Exact steps for others to reproduce the error** - Open Blender - Make sure that Viewport Shading method is set to *Solid*. It doesn't matter which render engine is in use # Expand Viewport Shading options in the header, then enable *Shadow* **Another way to reproduce the error** - Open Blender - Set render engine: *Workbench* - Switch shading method to *Rendered* (if it's *Solid*, it wouldn't crash until you switch it to *Rendered* after enabling shadows!) - Go to Properties region -> Render tab -> Options panel -> enable *Shadow*
Author

Added subscriber: @dxmind

Added subscriber: @dxmind

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sebastian Parborg self-assigned this 2019-07-11 12:33:37 +02:00

We won't stop users from running out program on unsupported hardware, but we do not handle bug reports of issues that happen when doing so.

We won't stop users from running out program on unsupported hardware, but we do not handle bug reports of issues that happen when doing so.
Author

Removed subscriber: @dxmind

Removed subscriber: @dxmind
Author

Hello again. It looks like I was wrong, sorry! GeForce GT 330M is supported according to the https://www.blender.org/download/requirements/
It's weird, maybe I was hallucinating, I thought that GPU must support OpenGL 4, but now I see, it's 3.3 :)

So, now I am confused. Should I create new reports when something goes wrong? Blender is still crashing when I enable shadows, Eevee is not working, viewport performance is good in 2.80, but is very slow in 2.81 and 2.82 alpha...

Or 330M is indeed unsupported and developers should not spend time trying to resolve these issues?

Hello again. It looks like I was wrong, sorry! GeForce GT 330M is supported according to the https://www.blender.org/download/requirements/ It's weird, maybe I was hallucinating, I thought that GPU must support OpenGL 4, but now I see, it's 3.3 :) So, now I am confused. Should I create new reports when something goes wrong? Blender is still crashing when I enable shadows, Eevee is not working, viewport performance is good in 2.80, but is very slow in 2.81 and 2.82 alpha... Or 330M is indeed unsupported and developers should not spend time trying to resolve these issues?
Author

Added subscriber: @dxmind

Added subscriber: @dxmind

Added subscriber: @MaciejJutrzenka

Added subscriber: @MaciejJutrzenka

are u on windows 7?

are u on windows 7?

He is on Mac.

I'm going to be honest: We do not have your specific Nvidia GPU and it seems like Nvidia will not fix GPU issues on Mac as Apple dropped them and went with AMD instead.
Therefore it is highly unlikely that we will fix this.

We will probably increase the system requirements in the future.

I can just recommend you to either install windows on your Mac and hope it works better or buy an new computer.

He is on Mac. I'm going to be honest: We do not have your specific Nvidia GPU and it seems like Nvidia will not fix GPU issues on Mac as Apple dropped them and went with AMD instead. Therefore it is highly unlikely that we will fix this. We will probably increase the system requirements in the future. I can just recommend you to either install windows on your Mac and hope it works better or buy an new computer.
Author

I am on macOS High Sierra (10.13.6)
Computer is MacBook Pro (15-inch, Mid 2010)
Processor: 2.66 GHz Intel Core i7
Memory: 8 GB 1067 MHz DDR3,
Graphics: NVIDIA GeForce GT 330M 512 MB

I am on macOS High Sierra (10.13.6) Computer is MacBook Pro (15-inch, Mid 2010) Processor: 2.66 GHz Intel Core i7 Memory: 8 GB 1067 MHz DDR3, Graphics: NVIDIA GeForce GT 330M 512 MB
Author

I understand that. The driver is obsolete on macOS. Just wanted to say that on my system viewport performance decreased in 2.81. Now it's ~10 fps in the default scene (compared to ~30 in 2.80.) Maybe this information will help you to optimize the program somehow! I am already happy that 2.80 is working fine! There are only 2 problems: eevee and shadows, but I can live without them :)

I understand that. The driver is obsolete on macOS. Just wanted to say that on my system viewport performance decreased in 2.81. Now it's ~10 fps in the default scene (compared to ~30 in 2.80.) Maybe this information will help you to optimize the program somehow! I am already happy that 2.80 is working fine! There are only 2 problems: eevee and shadows, but I can live without them :)

Ok, thanks for the info! :)

Ok, thanks for the info! :)

Added subscriber: @ArkadeN

Added subscriber: @ArkadeN

Hi, i have the same issue, i did the same post

Hi, i have the same issue, i did the same post
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#66670
No description provided.