Reorganize 3D View Menus: View, Add and Object Menu #46853

Closed
opened 7 years ago by BrendonMurphy · 55 comments
Collaborator

Moved to D2876

Moved to [D2876](https://archive.blender.org/developer/D2876)
Poster
Collaborator

Changed status to: 'Open'

Changed status to: 'Open'
JulianEisel was assigned by BrendonMurphy 7 years ago
Poster
Collaborator

Added subscriber: @BrendonMurphy

Added subscriber: @BrendonMurphy
Sergey commented 7 years ago
Owner

Added subscriber: @Sergey

Added subscriber: @Sergey
JulianEisel changed title from space_view_3d_patch View Menu, Add Menu, Object menu. to Reorganize 3D View Menus: View, Add and Object Menu 7 years ago
jta commented 7 years ago
Collaborator

Added subscriber: @jta

Added subscriber: @jta

Added subscriber: @PawelLyczkowski-1

Added subscriber: @PawelLyczkowski-1
Collaborator

Since I usually don't have Blender open for more than a few seconds, we need some users to test and give feedback on this. It can be easily tested by replacing the space_view3d.py in [blender_build_dir]/[release_version]/scripts/startup/bl_ui with the one attached in the task description.

Since I usually don't have Blender open for more than a few seconds, we need some users to test and give feedback on this. It can be easily tested by replacing the `space_view3d.py` in `[blender_build_dir]/[release_version]/scripts/startup/bl_ui` with the one attached in the task description.
lamoot commented 7 years ago

Added subscriber: @lamoot

Added subscriber: @lamoot
lamoot commented 7 years ago

I tested it and find it an overall improvement over the existing menus (to the point I'm keeping it from now on :) It's indeed compact and easier to navigate, especially when you're no longer greeted by a long list of options and have to scan through them to find what you're after. I also like the add menu, somehow it's easier to navigate despite only a few layout changes.

From what I can tell, there don't seem to be any entries missing, just a different layout.

One thing that I'd tweak is the name of the relations submenu in the object menu. "Relations" sounds like a parent-child relationship, whereas the menu holds operators that deal with linking and transfering data (if you read tooltips of the entries many include the word "linked"). So something with data/transfer/linked. Link and transfer data perhaps?

Good job though, thanks for the script!

I tested it and find it an overall improvement over the existing menus (to the point I'm keeping it from now on :) It's indeed compact and easier to navigate, especially when you're no longer greeted by a long list of options and have to scan through them to find what you're after. I also like the add menu, somehow it's easier to navigate despite only a few layout changes. From what I can tell, there don't seem to be any entries missing, just a different layout. One thing that I'd tweak is the name of the **relations** submenu in the object menu. "Relations" sounds like a parent-child relationship, whereas the menu holds operators that deal with linking and transfering data (if you read tooltips of the entries many include the word "linked"). So something with data/transfer/linked. **Link and transfer data** perhaps? Good job though, thanks for the script!
Collaborator

Added subscriber: @Blendify

Added subscriber: @Blendify
Collaborator

On question I have is why is Add camera put into a sub menu when there is only one type of camera. As with outlining you should not have sub point with just one point under it e.g.

Correct:

  • Thing 1
    • Sub thing 1
    • Sub thing 2
  • Thing 2
    • Sub thing 1
    • Sub thing 2

Incorrect:

  • Thing 1
    • Sub thing 1
  • Thing 2
    • Sub thing 1

Other then that LGTM

On question I have is why is Add camera put into a sub menu when there is only one type of camera. As with outlining you should not have sub point with just one point under it e.g. Correct: - Thing 1 - Sub thing 1 - Sub thing 2 - Thing 2 - Sub thing 1 - Sub thing 2 Incorrect: - Thing 1 - Sub thing 1 - Thing 2 - Sub thing 1 ------------- Other then that LGTM
Collaborator

This may be a little off topic but why are there game options even when I am not in game engine mode. There are other examples in headers in Blender that are only available in the game engine why are we inconstant in the UI here?

This may be a little off topic but why are there game options even when I am not in game engine mode. There are other examples in headers in Blender that are only available in the game engine why are we inconstant in the UI here?
Poster
Collaborator

hi,
@Blendify The add camera change to menu item is similar behavior to add armature. The single menu item allows for addons to expand this as a sub menu. An example or this is the Rigify addon which uses the add armature. Similarly in contrib the surround cameras addon could use this expanded menu.

@lamoot yes, there's no going back once you use the new menu's, they are designed with the Blender user in mind. Thanks. your right about the use of Relations maybe Link/Transfer would be better. I think it is.

Keep in mind this is just a small section of what needs fixing, Edit Mode entries are far more challenging.

hi, @Blendify The add camera change to menu item is similar behavior to add armature. The single menu item allows for addons to expand this as a sub menu. An example or this is the Rigify addon which uses the add armature. Similarly in contrib the surround cameras addon could use this expanded menu. @lamoot yes, there's no going back once you use the new menu's, they are designed with the Blender user in mind. Thanks. your right about the use of Relations maybe Link/Transfer would be better. I think it is. Keep in mind this is just a small section of what needs fixing, Edit Mode entries are far more challenging.
Collaborator

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez
Collaborator

Nice!

I really like the Add Menu. Icons that make more sense are always good. For 'Force Field" I'd change it to "FORCE_FORCE", since it looks like now it's using the particle strand select mode (better than the current Empty icon anyway).

I particularly like the fact that you're adding 'Camera' as its own menu, this will encourage users and developers to make more Camera types.

The addition of Quick Effects to the Add Menu will blow some minds! I know of people that still are not familiar with that feature.

Agree with the point @Blendify makes about 'Relations', it feels more like Parent/Child. Besides that, the patch looks good to me.

This will essentially make lots of documentation and tutorials incompatible, so I assume this is for the 2.8 branch?

Nice! I really like the Add Menu. Icons that make more sense are always good. For 'Force Field" I'd change it to "FORCE_FORCE", since it looks like now it's using the particle strand select mode (better than the current Empty icon anyway). I particularly like the fact that you're adding 'Camera' as its own menu, this will encourage users and developers to make more Camera types. The addition of Quick Effects to the Add Menu will blow some minds! I know of people that still are not familiar with that feature. Agree with the point @Blendify makes about 'Relations', it feels more like Parent/Child. Besides that, the patch looks good to me. This will essentially make lots of documentation and tutorials incompatible, so I assume this is for the 2.8 branch?
Owner

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Owner

Note that adding a camera can show as a sub menu once its extended, see: P302

Note that adding a camera can show as a sub menu once its extended, see: [P302](https://archive.blender.org/developer/P302.txt)
Collaborator

Calling it linked and transfer data seems a bit long of a name to me.

Calling it linked and transfer data seems a bit long of a name to me.
Poster
Collaborator

hi, thanks very much for input. There's very valid suggestions that I will take into account when I update the task shortly.

@Blendify thanks for writing the patch, I'm really not good with them.
@venomgfx thanks, your point is taken about documentation changes. I think the changes are logical enough that people will not get very lost or adapt quickly.
One consideration here is to introduce these menu changes sooner, rather than later. When the 2.8 redesign starts I think it would be good to have most menu restructuring done first, then build the new features on top.
@ideasman42 thanks for P302, If you could commit this I could use right away and make updated patch.

Thanks again, I'll update the patch with everyone's suggestions within the next few days.

hi, thanks very much for input. There's very valid suggestions that I will take into account when I update the task shortly. @Blendify thanks for writing the patch, I'm really not good with them. @venomgfx thanks, your point is taken about documentation changes. I think the changes are logical enough that people will not get very lost or adapt quickly. One consideration here is to introduce these menu changes sooner, rather than later. When the 2.8 redesign starts I think it would be good to have most menu restructuring done first, then build the new features on top. @ideasman42 thanks for [P302](https://archive.blender.org/developer/P302.txt), If you could commit this I could use right away and make updated patch. Thanks again, I'll update the patch with everyone's suggestions within the next few days.
Poster
Collaborator

updated to fix mentioned issues.
file: space_view3d.py

Proposed Changes

View menu === (unchanged from original patch)

  • Merge base directional numpad operators: Top, Bottom, Front, Back, Left, Right into new menu: "Directions"
  • Remove duplicate Camera menu enty(numpad 0)
  • Merge border operators: Render, Zoom, Clipping into new menu: "Set Border"
  • Merge view toggle Fullscreen, maximize & Quad views into new menu: "View Toggle"

Re-organize layout

view_menu.jpg

3D View: Add Menu

  • "Camera" move from direct operator to menu: Camera.
  • Move "Quick Effects menu" from Object Menu to Add menu.
  • Re-organize layout
  • Change Icons
    add_menu.jpg

Object Menu

  • Move "Quick Effects menu" from Object Menu to Add menu.
  • Merge transfer mesh data, make local, make single user, make proxy, make dupliface into new menu: "Object Data"
  • Move Duplicate object & duplicate linked to new menu: "Duplicate"
  • Re-organize layout
    object_menu.jpg

thanks for feedback.

updated to fix mentioned issues. file: [space_view3d.py](https://archive.blender.org/developer/F277474/space_view3d.py) ## Proposed Changes ### View menu === (unchanged from original patch) - Merge base directional numpad operators: Top, Bottom, Front, Back, Left, Right into new menu: "Directions" - Remove duplicate Camera menu enty(numpad 0) - Merge border operators: Render, Zoom, Clipping into new menu: "Set Border" - Merge view toggle Fullscreen, maximize & Quad views into new menu: "View Toggle" # Re-organize layout ![view_menu.jpg](https://archive.blender.org/developer/F277476/view_menu.jpg) ### 3D View: Add Menu - "Camera" move from direct operator to menu: Camera. - Move "Quick Effects menu" from Object Menu to Add menu. - Re-organize layout - Change Icons ![add_menu.jpg](https://archive.blender.org/developer/F277482/add_menu.jpg) ### Object Menu - Move "Quick Effects menu" from Object Menu to Add menu. - Merge transfer mesh data, make local, make single user, make proxy, make dupliface into new menu: "Object Data" - Move Duplicate object & duplicate linked to new menu: "Duplicate" - Re-organize layout ![object_menu.jpg](https://archive.blender.org/developer/F277484/object_menu.jpg) thanks for feedback.

Added subscriber: @BartekMoniewski

Added subscriber: @BartekMoniewski

Clear and well organized. Good job. :)

Clear and well organized. Good job. :)

Added subscriber: @blend-it

Added subscriber: @blend-it

Added subscriber: @quollism

Added subscriber: @quollism

Like this a lot - it's a lot like before but different enough to constitute a genuinely useful improvement. Top stuff!

Like this a lot - it's a lot like before but different enough to constitute a genuinely useful improvement. Top stuff!

Added subscriber: @intracube

Added subscriber: @intracube

Nice work. Much cleaner and easier to scan through.

There is an increased number of clicks needed to get to some operations, but IMO this isn't a problem. If you use an option often enough, the keyboard shortcut is the way to go. This proposal looks better for new users.

Nice work. Much cleaner and easier to scan through. There is an increased number of clicks needed to get to some operations, but IMO this isn't a problem. If you use an option often enough, the keyboard shortcut is the way to go. This proposal looks better for new users.
Owner

Seems this is ready for review from the UI design team?

Seems this is ready for review from the UI design team?
Poster
Collaborator

@ideasman42
updated patch is here https://developer.blender.org/D1741 thanks to Blendify
I am always available in irc to discuss & help with this patch.
I would hope this could be reviewed shortly after 2.77 release.
Thanks to everyone for feedback & positive comments,

@ideasman42 updated patch is here https://developer.blender.org/D1741 thanks to Blendify I am always available in irc to discuss & help with this patch. I would hope this could be reviewed shortly after 2.77 release. Thanks to everyone for feedback & positive comments,

Added subscriber: @JonathanWilliamson

Added subscriber: @JonathanWilliamson

This looks good to me @meta-androcto. The latest revision is a very good improvement on 2.76, and the updates for Object Data in place of Relations is much clearer to me as well.

Commit at will, now that Git is reopened after 2.77.

This looks good to me @meta-androcto. The latest revision is a very good improvement on 2.76, and the updates for *Object Data* in place of *Relations* is much clearer to me as well. Commit at will, now that Git is reopened after 2.77.

My review:

I like most of it, but I wouldn't group the View directions. That's because these are pretty important, and need quick access IMO. I suspect many people use the menu instead of the numpad or a pie. Also, the View menu isn't overflowing anyway, so there is no pressing need to bundle them up into Directions.

My review: I like most of it, but I wouldn't group the View directions. That's because these are pretty important, and need quick access IMO. I suspect many people use the menu instead of the numpad or a pie. Also, the View menu isn't overflowing anyway, so there is no pressing need to bundle them up into Directions.
Collaborator

I'm still a bit wary of applying this for 2.7x. As @venomgfx said earlier, this will make many tutorials, manuals, etc. obsolete, which is still an important point. Actually I think this could go into 2.8 master branch right away (still didn't check code details though).

I'm still a bit wary of applying this for 2.7x. As @venomgfx said earlier, this will make many tutorials, manuals, etc. obsolete, which is still an important point. Actually I think this could go into 2.8 master branch right away (still didn't check code details though).
Poster
Collaborator

hi,
@JonathanWilliamson thanks so much. I'll wait until UI Team meeting to discuss final concerns before any commit, primary concern it tutorial writers, I feel this patch will have minimal impact. I would appreciate your thoughts on this. Thanks again.
@PawelLyczkowski-1, the Directions menu merges 6 menu items into 1 easily discover-able menu, for menu user's there's a significant speed up once accustomed to this. For new users they are given easy to understand "Directions" sub-menu, rather than wall of menu entries. For Addons & Pie menu's there's the benefit of just calling the menu. all sub-menu items are not changed so they are unaffected.
@JulianEisel, @venomgfx I understand your concerns, the workflow in general has not changed, everything is readable & understandable enough that even new users should have little trouble following older tutorials.

Please note: I am trying here to make changes to the ui that are tidy, clean, & consolidate the structure we already have. The changes prepare the ui code & the users for future changes. Incremental restructuring of menu;s should be done sooner, rather than later. The benefits for users are to prepare them for change, the benefits for developers is they can build upon the new menu structures & the over all impact of 2.8 is somewhat lessened for everyone.

hi, @JonathanWilliamson thanks so much. I'll wait until UI Team meeting to discuss final concerns before any commit, primary concern it tutorial writers, I feel this patch will have minimal impact. I would appreciate your thoughts on this. Thanks again. @PawelLyczkowski-1, the Directions menu merges 6 menu items into 1 easily discover-able menu, for menu user's there's a significant speed up once accustomed to this. For new users they are given easy to understand "Directions" sub-menu, rather than wall of menu entries. For Addons & Pie menu's there's the benefit of just calling the menu. all sub-menu items are not changed so they are unaffected. @JulianEisel, @venomgfx I understand your concerns, the workflow in general has not changed, everything is readable & understandable enough that even new users should have little trouble following older tutorials. Please note: I am trying here to make changes to the ui that are tidy, clean, & consolidate the structure we already have. The changes prepare the ui code & the users for future changes. Incremental restructuring of menu;s should be done sooner, rather than later. The benefits for users are to prepare them for change, the benefits for developers is they can build upon the new menu structures & the over all impact of 2.8 is somewhat lessened for everyone.

Sounds good @meta-androcto. I see no issue with waiting 'til 2.8 for merging.

As a tutorial author myself, this is a pretty minor change and I don't believe that's a strong enough argument to hold off on committing (but also not a reason to rush it in, of course). The manual changes are more of a concern, though, and gives more validity to push for 2.8.

Sounds good @meta-androcto. I see no issue with waiting 'til 2.8 for merging. As a tutorial author myself, this is a pretty minor change and I don't believe that's a strong enough argument to hold off on committing (but also not a reason to rush it in, of course). The manual changes are more of a concern, though, and gives more validity to push for 2.8.
Poster
Collaborator

Hi, resolution at UI team Meeting was to apply this patch to 2.8 branch when it's available.
I'll leave this open as it will need updates until that time.
Thanks to UI Team for help & feedback.

Hi, resolution at UI team Meeting was to apply this patch to 2.8 branch when it's available. I'll leave this open as it will need updates until that time. Thanks to UI Team for help & feedback.
Collaborator

I don't think the manual will be a big issue for me or anyone else to mannage.

I don't think the manual will be a big issue for me or anyone else to mannage.
Poster
Collaborator

Added link to the file via my github in the first post. The file will be maintained & updated there.
Updated to 2.77

Added link to the file via my github in the first post. The file will be maintained & updated there. Updated to 2.77
italic commented 7 years ago

Added subscriber: @italic

Added subscriber: @italic
Collaborator

Added subscriber: @VukGardasevic

Added subscriber: @VukGardasevic
Poster
Collaborator

hi, it's quite surreal that this is already 1 year old.
currently i've rewritten the original patch for 2.79 after.
also written new edit modes 'w' key, v/e/f menus,
new space info header,
new file menu,
compact the node editor,
various ui tweaks
new patches to follow soon.
thanks.

hi, it's quite surreal that this is already 1 year old. currently i've rewritten the original patch for 2.79 after. also written new edit modes 'w' key, v/e/f menus, new space info header, new file menu, compact the node editor, various ui tweaks new patches to follow soon. thanks.
jta commented 5 years ago
Collaborator

Ok, I've been working on Fracture Modifier speed of workflow improvements. So I've been spending a lot of time in blender. I've also kept in regular contact with Meta on this subject.

I am convinced now more than ever because of my huge number of repetitions in the menu system that this specific topic needs to be addressed and not suffer the oft accused slow death of neglect.

I have repeatedly over the course of the last few weeks shook my head in frustration at the current menu setup. And after just discussing this with Meta just minutes ago and seeing the screen shots again with my current context I am convinced this type of change, if not this exact change, needs to happen for 2.8.

I and many others have worked hard at helping blender shed it's little toy image. This change is one of the things that contributes to blender putting on its big boy pants. Aside from the politics and mechanisms of the "UI Mafia" as we affectionately call it and fulfilling any requirements there, the UI team and responsible devs would be silly not to make this a priority, IMO as a professionally experienced UI/UX developer.

Thanks for letting me spin the squeaky wheel, hopefully it will make a difference.

Ok, I've been working on Fracture Modifier speed of workflow improvements. So I've been spending a lot of time in blender. I've also kept in regular contact with Meta on this subject. I am convinced now more than ever because of my huge number of repetitions in the menu system that this specific topic needs to be addressed and not suffer the oft accused slow death of neglect. I have repeatedly over the course of the last few weeks shook my head in frustration at the current menu setup. And after just discussing this with Meta just minutes ago and seeing the screen shots again with my current context I am convinced this type of change, if not this exact change, needs to happen for 2.8. I and many others have worked hard at helping blender shed it's little toy image. This change is one of the things that contributes to blender putting on its big boy pants. Aside from the politics and mechanisms of the "UI Mafia" as we affectionately call it and fulfilling any requirements there, the UI team and responsible devs would be silly not to make this a priority, IMO as a professionally experienced UI/UX developer. Thanks for letting me spin the squeaky wheel, hopefully it will make a difference.
brecht commented 5 years ago
Owner

Added subscriber: @brecht

Added subscriber: @brecht
brecht commented 5 years ago
Owner

It seems the conclusion was that it's ok to commit this to the Blender 2.8 branch, and @BrendonMurphy has commit rights for that as far as I can tell. So I'm not sure what this is waiting on?

It seems the conclusion was that it's ok to commit this to the Blender 2.8 branch, and @BrendonMurphy has commit rights for that as far as I can tell. So I'm not sure what this is waiting on?
Poster
Collaborator

@brecht
i guess waiting on me then, i'll update and port the parch over to 2.8 and submit new diff.
I would be very happy to go ahead with this next week.
thanks

@brecht i guess waiting on me then, i'll update and port the parch over to 2.8 and submit new diff. I would be very happy to go ahead with this next week. thanks
Poster
Collaborator

space_view3d.py
Current file based off 2.79 master.

File for 2.8 to follow and update to task images

[space_view3d.py](https://archive.blender.org/developer/F919367/space_view3d.py) Current file based off 2.79 master. File for 2.8 to follow and update to task images
Poster
Collaborator

space_view3d.py
this second file includes shorter w key edit mode menu and vert edge face menu redesign
faces menu.jpg

vert menu.jpg

[space_view3d.py](https://archive.blender.org/developer/F919524/space_view3d.py) this second file includes shorter w key edit mode menu and vert edge face menu redesign ![faces menu.jpg](https://archive.blender.org/developer/F919526/faces_menu.jpg) ![vert menu.jpg](https://archive.blender.org/developer/F919528/vert_menu.jpg)

Added subscriber: @JoshuaLeung

Added subscriber: @JoshuaLeung
Poster
Collaborator

just an update that we are still working on some code cleanup before commit to master.
thanks

just an update that we are still working on some code cleanup before commit to master. thanks
Collaborator

space_view3d.py

  • Cleanup version.

  • Slight adjustments of the menus entries here and there.

  • Make the delete options always separated in menus and more consistent in locations.

  • Try to separate longer blocks of entries.

  • Fix some duplicated separators.

[space_view3d.py](https://archive.blender.org/developer/F979498/space_view3d.py) - Cleanup version. - Slight adjustments of the menus entries here and there. - Make the delete options always separated in menus and more consistent in locations. - Try to separate longer blocks of entries. - Fix some duplicated separators.
Collaborator

@VukGardasevic is this the "final" version ready for review?

@VukGardasevic is this the "final" version ready for review?
Poster
Collaborator

@Blendify @JulianEisel yes, this is final version for this round of changes. (other menus may follow)

@Blendify @JulianEisel yes, this is final version for this round of changes. (other menus may follow)
Owner

Apparently this is ready for review but the link: https://github.com/meta-androcto/blenderpython/raw/master/scripts/startup/bl_ui/space_view3d.py is giving me a 404.

Or are you referring to this post #46853#464607 ? space_view3d.py

Would rather this go via differential, people uploading files in different places is too haphazard, its also not clear what differences are intended, since some changes have probably been made in master since.

Apparently this is ready for review but the link: https://github.com/meta-androcto/blenderpython/raw/master/scripts/startup/bl_ui/space_view3d.py is giving me a 404. Or are you referring to this post #46853#464607 ? [space_view3d.py](https://archive.blender.org/developer/F979498/space_view3d.py) Would rather this go via differential, people uploading files in different places is too haphazard, its also not clear what differences are intended, since some changes have probably been made in master since.
Poster
Collaborator

new diff in first comment at bottom of updated description

new diff in first comment at bottom of updated description
Owner

Applied most of the changes to the "View" menu, but have some concerns with other changes.

See: D2876#67809


Note, there are 3 places this patch has been discussed.

D2876, D1741 & this task. Closing all except for D2876 since this gets confusing.

Applied most of the changes to the "View" menu, but have some concerns with other changes. See: [D2876](https://archive.blender.org/developer/D2876)#67809 ---- Note, there are 3 places this patch has been discussed. [D2876](https://archive.blender.org/developer/D2876), [D1741](https://archive.blender.org/developer/D1741) & this task. Closing all except for [D2876](https://archive.blender.org/developer/D2876) since this gets confusing.
Owner

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
ideasman42 closed this issue 5 years ago
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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
18 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#46853
Loading…
There is no content yet.