2.8 not starting #59853
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#59853
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?
Blender 2.8 doesn't start. I'm on windows 32 bit, Lenovo IdeaPad miix 300, one of these old 2 in 1 tablets.
With Intel graphics, Intel atom and 2gb ram, it could be that it doesn't meet the requirements. It supports up to OpenGL 4.0 so it shouldn't be a problem.
2.79 and the 2.79 daily builds work fine ("fine")
Either the requirement of OpenGL 3.3 ist false or it's a bug. I've tried yesterday's and today's daily 2.8 build bot build, both show up a terminal without contents for a couple seconds and then close, no error message whatsoever. 2.79 has been proven surprisingly useful on such a weak tablet and it'd be cool to get 2.8 on there since it should technically be supported anyway.
Added subscriber: @paperbenni
Added subscriber: @StephenSwaney
Generic advice:
Run blender from a terminal window so you can see any error messages.
Use updated graphics driver - preferably from your card's manufacturer.
Please mention what version of Windows and your specific graphics card.
I did run it from terminal. No output there, just a blank line and then it quits.
blender.exe --help and --version works, so at least it's not completely broken.
I'm on windows 10 home 1803 32 bit
The graphics is intel integrated.
Here is the output of dxdiag, maybe that can help. There's something about blender crashes in there too.
DxDiag.txt
Added subscriber: @ChristopherAnderssarian
There should be an output from the terminal...
Open Command prompt:
Drag and drop blender.exe and add
to the end hit enter.
It should look something like this (not the exact filepath):
If that doesn't work then here's a general (paste) list of things to check/do:
It started with --debug enabled for some strange reason.
So I tried deleting the 2.8 prefs from the appdata. Didn't work.
So I went all out and deleted the entire blenderfoundation folder including 2.79 prefs although the 2.8 prefs were already gone.
And it started without issues. Could there be some permission issues? I thought every app could write to the appdata.
But here's another issue: The viewport performance and responsiveness was about half of what 2.79 delivers. Is the new viewport just that much slower?! Here is the output of blender.exe -d
log.txt
Added subscriber: @iss
I had similar problem on windows 10 64bit, on both 64 and 32bit builds. After deleting userpref.blend file blender started, but it keep failing on exit and load file.
Here is output of start blender then immediately exit:
In debugger I saw fail on free studiolights
Here is output of start blender, save file, open saved file.
I can add stack trace...
for first case
for second case
on line
id was
all other fields were NULL
Added subscriber: @brecht
@paperbenni, can you attach the output of Help > System Info in Blender 2.79?
It's not clear to me that this graphics card does fully support OpenGL 3.3. When it was released it only supported only 3.2, while OpenGL was already at 4.4 at the time. Maybe it got added later in the driver, but it's odd.
@iss, that seems like a different bug.
system-info.txt
There it is.
Opengl extensions viewer also shows opengl 4.0
I really hope it is unable to use OpenGL for some reason, otherwise this is deeply concerning. Should I open another bug report or is 2.8 just half as fast as 2.79?!
Blender 2.8 is optimized for modern GPUs, this system will likely soon be below our minimum requirements. 32 bit support will likely be dropped soon as well. So we're unlikely to invest time optimizing for this system, and would not handle poor performance on this system as a bug.
Changed status from 'Open' to: 'Archived'
I missed that removing the old settings seems to solve the crash. So I'm not sure there is anything remaining here that we can fix.