2.93 does not load Nishita Sky settings correctly from 2.92 #87850
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#87850
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
Graphics card: 2080 Ti
Blender Version
Broken: 2.93.0 Beta Date: 2021-04-15 17:14 Hash:
fa8d566c3b
Worked: (newest version of Blender that worked as expected) 2.92.0 2021-02-24 16:25 Hash:
02948a2cab
Short description of error
Added subscriber: @chippwalters
Added subscriber: @deadpin
This changed for 2.93 because the units were unclear.
In 2.92 (https://docs.blender.org/manual/en/2.92/render/shader_nodes/textures/sky.html) the altitude was in kilometers.
In 2.93 (https://docs.blender.org/manual/en/2.93/render/shader_nodes/textures/sky.html) the altitude is in meters and the input is now marked as a Distance so you see the 'm' there.
So from that angle it looks like things are working correctly. If you have a file which is now rendered differently, is it possible to attach it?
When going back from 3.0 to 2.92 you will find it does not track the altitude correctly. It will take an altitude set at 1000 m in 3.0 and turn it to 1000 units (way up in space) in 2.92. Please check it out.
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Archived'
@chippwalters, to resolve this we would need to re-release previous versions with back versioning code.
Although it would solve these cases, not everyone would re-download a blender with an older version to solve this.
So for many who would not "update" the old version blender, it would still seem like a bug.
Thus, although it is allowed, unexpected behavior when loading files from newer versions is not avoided.
We could completely block the loading of newer files if the best.
But for now, we don't consider this a bug.