Saving a blender file is bugged #84178
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#84178
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-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00
Blender Version
Broken: version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash:
0f45cab862
Worked: Haven't tested that yet.
Short description of error
When I save a file, then exit and re-open blender with the file,
3 I'm having to remake the entire project, and then I re-open it to work again and I have to start over.
There are probably many more issues that I don't know yet, it seems to be a problem for only me, and I have no idea why its happening
Exact steps for others to reproduce the error
Doughnut.blend1
Doughnut.blend
Added subscriber: @Trovvie
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs User Info'
Cannot reproduce here.
I see there are no materials on the doghnut, but adding those will survive saving/reloading here.
Just to make sure:
Please try with File → Defaults → Load Factory Settings to see if you still can reproduce this issue.
Please try this in a fresh 2.92 build from https://builder.blender.org/download/
Changed status from 'Needs User Info' to: 'Needs Triage'
I have installed the newest build and tried to load up my save file. It is still bugged, and though my engine is set to cycles, I am stuck on Eevee.
I have asked a friend to open these files on their PC, and it worked fine. I have no clue why it's bugged on mine :(
Any way to fix it?
I'm willing to screenshare on discord
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Needs User Info'
Can't reproduce either. I would suggest you rename
C:\Users\<your username>\AppData\Roaming\Blender Foundation\Blender\2.91
and then try again.If it still doesn't work, then open Blender's installation directory and double click on the
blender_debug_log.cmd
. This will start Blender in debug mode and create log files. Try to make Blender fail to switch render engines again or fail to load the file properly. Once it does, close Blender. The Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop.The path is already with the same name.
Log Files:
blender_debug_output.txt
blender_system_info.txt
Changed status from 'Needs User Info' to: 'Needs Triage'
The log file doesn't contain anything that would indicate an error. Did you try to switch the render engine and it failed while the debug session was in progress or did you only try to save the file? If it is the latter please start double-click on the
blender_debug_gpu.cmd
, load the file and try to perform one of the operations that fail on your system.In my last comment I meant rename the folder to something else, like
2.91_original
. This prevents Blender from attempting to load anything from the old directory. This is very similar to Philipps suggestion to load the factory settings, but you can switch back to your original user preferences by given the directory its original name, if the user preferences are not the cause of the problem.Changed status from 'Needs Triage' to: 'Needs User Info'
Changed status from 'Needs User Info' to: 'Needs Triage'
Yes I tried to switch render engines and it still doesn't work.
I've tried renaming the folder as well, also doesn't work. It did however change back to factory settings. Blender is still broken. This is also the case with my fresh install of 2.83 LTS from the windows store. I have no idea what's happening here.
I'm willing to screenshare if you'd like
@Trovvie For liability and privacy reasons I wouldn't want you to screenshare or do anything that requires remote access to your machine. You could upload a (short) screen recording of the issue you're describing though.
I was thinking more of discord screen share and no remote access, but yeah I understand.
https://i.imgur.com/wGzmgtM.gif
You have configured that Cycles should use the GPU as Device in the project. It's grayed out because you haven't selected CUDA or OptiX in the user preferences, at least that is what appears to be happening. Please try the following:
This isn't the problem, I've tested it with enabling as well. The option is greyed out as I had reset user preferences.
The render engine isn't the only problem, materials, colors and other options also do not work.
I've tried doing what you said and that has also not helped.
Added subscriber: @filedescriptor
Changed status from 'Needs Triage' to: 'Needs User Info'
Is this still an issue? Have you tried the latest builds from https://builder.blender.org?
Changed status from 'Needs User Info' to: 'Needs Triage'
Yes, I've tried the new build as well. Still an issue.
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Archived'
This report has been open for a long time with no progress.
I downloaded the files but the steps are inconsistent. For example
"Take the basic donut that I've made and try changing it to cycles"
, both files have Cycles as the engine set.I took a look at this video and it didn't show anything that could help identify the problem.
Doughnut.blend
file hadCycles
as engine set.About materials and colors disappearing, could they have been saved without "users" or without the "fake user" option? When saving and reopening the file, they are automatically deleted.
See https://docs.blender.org/manual/en/latest/render/materials/assignment.html?highlight=fake%20user#deleting-a-material
While this can be a real issue, it is only happening to a few people so far. And to troubleshoot it developers needs to have direct access to hardware. And even then it is not clear whether if it's really a bug on Blender side...
So thanks for the report, but doesn't look like we can solve this issue.