Texture painting data get lost on Blender crash despite autosave and manual file saving #92284
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#92284
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: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12
Blender Version
Broken: version: 2.93.4, branch: master (modified), commit date: 2021-08-31 09:23, hash:
b7205031ce
Short description of error
I keep losing texture painting data, literally hours of work, because Blender is very unstable in texture paint mode combined with Eevee and crashes a lot. This would be fine if autosave and manual file saving worked as expected, but neither of these saves modified internal image datablocks, so when Blender crashes, all the work is lost, even if the user saves very frequently.
Exact steps for others to reproduce the error
Result: The texture paint changes to the image block are lost.
Expected: Blender has an option to save modified image datablocks when the file is saved, so the users do not lose their work.
Added subscriber: @Rawalanche
Added subscriber: @lichtwerk
The question whether to always do the auto-image-saving always (not only on quitting / leaving the file -- which has been added for 2.8) has come up before, see #45636.
So in essence, this is a duplicate of #45636 (Texture paint doesn't prompt user to save painted textures).
All relevant discussion has already taken place there (there is no new information here).
I agree this is still an issue, it should be solved at some point, but devs responsible in this area have classified this as not a bug.
To keep this bugtracker organized, I am afraid I will have to merge this with #45636.
Feel free to raise your concerns in that report again, but there is no point in having two separate task for this.
Note that the API is there, the change would be quite minimal, I think the main question is how to have this implemented:
But lets please continue discussion in #45636 (think it makes more sense / raises the pressure there)
Thx reporting anyways!
Closed as duplicate of #45636
This comment was removed by @Rawalanche