"saved as a copy" confuses Blender when loading scenes #57989
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#57989
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
Win x64 10
Blender Version (same with release 2.79b)
2.79
dca3d3ef0e
When I load the attached scene , Blender does not show the scene file name at the top, when I try to save the file while it is open, it tries to save over a previously opened/saved file, not the one that is currently open. These files are saved temporarily as "copies" using the py line below
It is by accident that I found about this behavior, not intentional really.
I am not sure if this is an intentional behavior but to me it does not make sense that Blender would care if a file was saved as a copy or or not after a complete restart.
Make a new scene with simple suzanne
Save it as a copy from the file menu
Close Blender
Open Blender
Open the scene you just saved as copy
Check the title line, no name there as if the scene is nameless
Press Ctrl-S to save it again
Observe where and how it tries to save it. It normally should save it over the currently opened scene but it does not, it either asks for a name (since it is missing a name), or tries to save ver the previously opened file.
thanks
BLENDER.blend
Added subscriber: @kursadk
I actually just tested this with regular "Save Copy" from the file menu, there is the exact same issue. So this does not seem to be anything about the Python call, might be either a design thing or an issue that was overlooked all this time, I cant be sure.
In my opinion saving a copy means you save it with a different name so you do not change the current file name, but that should not interfere with how a file should behave next time it is opened. Quite a curious situation.
I just added repeat steps to the original entry.
This issue was referenced by
c66570f519
Changed status from 'Open' to: 'Resolved'
@ideasman42 thanks for the speedy fix. Had this bug(or a feature) been recent introduction or been there for quite some time?
Added subscriber: @ideasman42