Default to Absolute Paths preference breaks when saving a new file #101219

Closed
opened 2022-09-20 17:03:49 +02:00 by Andrew Weidenhammer · 11 comments

System Information
Operating system: Windows 10
Graphics card: GTX 3090

Blender Version
3.3.0

Short description of error
When unchecking the preference "Default to Relative Paths" expected behavior is to default to absolute paths. When I save a new file, the Remap to Relative Paths option remains checked in the save options and all files with textures are now broken as we are expecting absolute paths

Exact steps for others to reproduce the error
Start a new scene
Set preferences to Default to Relative Paths OFF
import textures from a server location on another drive and apply to object
save
Then save as a new file with a new name without adjusting the save options (all of our artists ignore those options under the gear when they save files).
Open the new file and textures are missing.

This has been really breaking our workflow which requires absolute paths.

**System Information** Operating system: Windows 10 Graphics card: GTX 3090 **Blender Version** 3.3.0 **Short description of error** When unchecking the preference "Default to Relative Paths" expected behavior is to default to absolute paths. When I save a new file, the Remap to Relative Paths option remains checked in the save options and all files with textures are now broken as we are expecting absolute paths **Exact steps for others to reproduce the error** Start a new scene Set preferences to Default to Relative Paths OFF import textures from a server location on another drive and apply to object save Then save as a new file with a new name without adjusting the save options (all of our artists ignore those options under the gear when they save files). Open the new file and textures are missing. This has been really breaking our workflow which requires absolute paths.

Added subscriber: @MotR

Added subscriber: @MotR

This is my very first bug report on Blender Devs. Be gentle and let me know how to better report issues;)

This is my very first bug report on Blender Devs. Be gentle and let me know how to better report issues;)
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

When unchecking the preference "Default to Relative Paths"
Set preferences to Default to Relative Paths OFF

Thanks for the report. I couldn't find the exact option you're referring to. Could you reveal where exactly it's located in preferences tab?

> When unchecking the preference "Default to Relative Paths" > Set preferences to Default to Relative Paths OFF Thanks for the report. I couldn't find the exact option you're referring to. Could you reveal where exactly it's located in preferences tab?

I'm actually having trouble reproducing it from a base scene. We've been having a lot of relative path textures revert to relative, even when the preference is set to absolute. However I am not getting it to break from a clean scene, so maybe have to take this ticket down until I can reliably reproduce.

Here's the preference
image.png

And here's the save dialog option that always stays set to "Remap Relative"
image.png

I'm actually having trouble reproducing it from a base scene. We've been having a lot of relative path textures revert to relative, even when the preference is set to absolute. However I am not getting it to break from a clean scene, so maybe have to take this ticket down until I can reliably reproduce. Here's the preference ![image.png](https://archive.blender.org/developer/F13544801/image.png) And here's the save dialog option that always stays set to "Remap Relative" ![image.png](https://archive.blender.org/developer/F13544841/image.png)

Added subscriber: @mano-wii

Added subscriber: @mano-wii

I am not able to replicate the problem.

If I'm not mistaken, if a file already has textures pointing to Relative Paths, they will continue to point to Relative Paths even if you save the file again.

You need to first execute the Make Paths Absolute operator.

I am not able to replicate the problem. If I'm not mistaken, if a file already has textures pointing to Relative Paths, they will continue to point to Relative Paths even if you save the file again. You need to first execute the `Make Paths Absolute` operator.

Understood. I'm unable to replicate myself reliably. I'll try to track the issue down more closely. We use the Make Paths Absolute option all the time. We have been forcing ourselves to do it every time we save a new file as sometimes our paths just go back to relative. But it's not precisely understood. You can close this ticket if you want and I'll reopen one if I can whittle down the issue.

Understood. I'm unable to replicate myself reliably. I'll try to track the issue down more closely. We use the Make Paths Absolute option all the time. We have been forcing ourselves to do it every time we save a new file as sometimes our paths just go back to relative. But it's not precisely understood. You can close this ticket if you want and I'll reopen one if I can whittle down the issue.

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'

Thanks for the report. Unfortunately unless there are clear instructions on how to reproduce the problem we cannot debug this any further.

Please open a new report when you identify how to replicate the problem.

Thanks for the report. Unfortunately unless there are clear instructions on how to reproduce the problem we cannot debug this any further. Please open a new report when you identify how to replicate the problem.
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
3 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#101219
No description provided.