Viewport - World Background does not work in Solid Mode #102758
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#102758
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: RTX 3080 Windows 10
Blender Version
Broken: 3.2.1, 3.1, 3.4
Worked: 2.79
Short description of error
World Background does not work in solid mode
Exact steps for others to reproduce the error
Expected Behaviour : Switching to World, would act like World Background in 2.79 which allows artists to manipulate the rotation of the HDRI without having to switch to material mode (which on production scenes can be problematic)
Added subscriber: @candreacchio
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Needs User Info'
Do you mean add a texture to the World material?
If so it's not a bug.
The
World
shading option makes the Workbench use the color defined inViewport Shading
.In 2.79, the Workbench is equivalent to the Solid view, which also does not use a Texture for the World.
Hi there,
Yes
Yes it does, in 2.79 there is an option to have a texture for the world
This is very useful for infrastructure animations, where material mode (and eevee) are horribly slow.
Changed status from 'Needs User Info' to: 'Archived'
Thanks for the report, but this is something that should have been discussed during planning for 2.8.
For user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
I tried to report issues during 2.8 development, but was told that it was bug fixes only (look at my bug report history).
I was assured that any regressions from 2.79 which were valid (which this is) would be tackled later.
Now I am being told that I should have reported it during 2.8's development. This is contradictory.
It should have been discussed in the proper channels, not as a bug report, as a feature being removed or moved is not necessarily a bug.