blender
/
blender
133
398
Fork 578
Code Issues 6.3k Pull Requests 746 Projects 19 Wiki Activity

Regression: Unable to move camera/area light with gizmo (intel GPU) #98932

New Issue
Open
opened 2022-06-16 13:09:35 +02:00 by bryce · 56 comments
bryce commented 2022-06-16 13:09:35 +02:00
Copy Link

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 30.0.101.1122

Blender Version
Broken: version: 3.2.0, 3.3
Worked: 3.1
Caused by 5045968f24

Short description of error
i cant move my camera using move tool or tranform tool on left side bar

Exact steps for others to reproduce the error

  • select camera
  • Choose move or transform tool
  • Move camera with gizmo (won't be able to move)

bug camera.blend
blender 3.2.mkv

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 30.0.101.1122 **Blender Version** Broken: version: 3.2.0, 3.3 Worked: 3.1 Caused by 5045968f24 **Short description of error** i cant move my camera using move tool or tranform tool on left side bar **Exact steps for others to reproduce the error** - select camera - Choose move or transform tool - Move camera with gizmo (won't be able to move) [bug camera.blend](https://archive.blender.org/developer/F13173546/bug_camera.blend) [blender 3.2.mkv](https://archive.blender.org/developer/F13177933/blender_3.2.mkv)
bryce commented 2022-06-16 13:09:35 +02:00
Author
Copy Link

Added subscriber: @Bryce-B

Added subscriber: @Bryce-B
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#103907 was marked as duplicate of this issue

#103907 was marked as duplicate of this issue
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#103720 was marked as duplicate of this issue

#103720 was marked as duplicate of this issue
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#103134 was marked as duplicate of this issue

#103134 was marked as duplicate of this issue
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#102936 was marked as duplicate of this issue

#102936 was marked as duplicate of this issue
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#101156 was marked as duplicate of this issue

#101156 was marked as duplicate of this issue
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#101158 was marked as duplicate of this issue

#101158 was marked as duplicate of this issue
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#99594 was marked as duplicate of this issue

#99594 was marked as duplicate of this issue
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#99747 was marked as duplicate of this issue

#99747 was marked as duplicate of this issue
blender-admin commented 2022-06-16 13:09:35 +02:00
Copy Link

#99177 was marked as duplicate of this issue

#99177 was marked as duplicate of this issue
bryce commented 2022-06-16 13:10:23 +02:00
Author
Copy Link

ill have to switch to 3.1 till fixed

ill have to switch to 3.1 till fixed
Philipp Oeser commented 2022-06-16 13:29:22 +02:00
Member
Copy Link

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Philipp Oeser commented 2022-06-16 13:29:22 +02:00
Member
Copy Link

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

Changed status from 'Needs Triage' to: 'Needs User Info'
Philipp Oeser commented 2022-06-16 13:29:22 +02:00
Member
Copy Link

Cannot reproduce here.

  • Please try with File → Defaults → Load Factory Settings to see if you still can reproduce this issue.
  • if that does not fix the issue, can you show this in action? (screencast might help here)
Cannot reproduce here. - Please try with File → Defaults → Load Factory Settings to see if you still can reproduce this issue. - if that does not fix the issue, can you show this in action? (screencast might help here)
bryce commented 2022-06-17 08:52:15 +02:00
Author
Copy Link

ok

ok
bryce commented 2022-06-17 09:16:12 +02:00
Author
Copy Link

blender 3.2.mkv

[blender 3.2.mkv](https://archive.blender.org/developer/F13177933/blender_3.2.mkv)
bryce commented 2022-06-17 09:33:55 +02:00
Author
Copy Link

hope it helps

hope it helps
bryce commented 2022-06-17 09:34:54 +02:00
Author
Copy Link

also i deleted and reilstaled blender but no fix

also i deleted and reilstaled blender but no fix
Pratik Borhade commented 2022-06-17 11:56:27 +02:00
Member
Copy Link

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Pratik Borhade commented 2022-06-17 11:56:27 +02:00
Member
Copy Link

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

Changed status from 'Needs User Info' to: 'Confirmed'
Pratik Borhade commented 2022-06-17 11:56:27 +02:00
Member
Copy Link

Seems iGPU specific issue. I've been able to confirm this in both 3.2 and 3.3 (works fine in 3.1)
GPU drivers of mine are one update behind. Will update them too. Confirming for now

Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1660```

---
Can not replicate with dedicated GPU
```Operating system : Windows-10-10.0.18362-SP0 64 Bits
Graphics card : AMD Radeon(TM) 535 ATI Technologies .```

---
Will investigate this later today
Seems iGPU specific issue. I've been able to confirm this in both 3.2 and 3.3 (works fine in 3.1) GPU drivers of mine are one update behind. Will update them too. Confirming for now ```Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1660``` --- Can not replicate with dedicated GPU ```Operating system : Windows-10-10.0.18362-SP0 64 Bits Graphics card : AMD Radeon(TM) 535 ATI Technologies .``` --- Will investigate this later today
Pratik Borhade changed title from camera doen't move to Unable to move camera with gizmo 2022-06-17 11:58:33 +02:00
Pratik Borhade commented 2022-06-17 20:32:36 +02:00
Member
Copy Link

Can confirm with newer drivers too 30.0.101.1994
Raising the priority (Will bisect this tomorrow)

Can confirm with newer drivers too `30.0.101.1994` Raising the priority (Will bisect this tomorrow)
Pratik Borhade changed title from Unable to move camera with gizmo to Regression: Unable to move camera with gizmo 2022-06-17 20:32:52 +02:00
Pratik Borhade commented 2022-06-22 10:41:33 +02:00
Member
Copy Link

Added subscribers: @Jeroen-Bakker, @ideasman42

Added subscribers: @Jeroen-Bakker, @ideasman42
Pratik Borhade commented 2022-06-22 10:41:33 +02:00
Member
Copy Link

Came with 5045968f24
cc @ideasman42
cc @Jeroen-Bakker

Came with 5045968f24 cc @ideasman42 cc @Jeroen-Bakker
Pratik Borhade commented 2022-06-26 06:35:35 +02:00
Member
Copy Link

Added subscriber: @YokaiBird

Added subscriber: @YokaiBird
Pratik Borhade changed title from Regression: Unable to move camera with gizmo to Regression: Unable to move camera/area light with gizmo 2022-06-26 06:35:57 +02:00
Campbell Barton commented 2022-06-28 12:52:00 +02:00
Owner
Copy Link

I can't redo this bug (works on Linux with Radeon RX 5600), this is a difficult area as changes here seem to cause problems for some GPU's and not others.

I can't redo this bug (works on Linux with `Radeon RX 5600`), this is a difficult area as changes here seem to cause problems for some GPU's and not others.
Jesse Yurkovich commented 2022-07-17 04:13:07 +02:00
Member
Copy Link

Added subscriber: @Oliver-9

Added subscriber: @Oliver-9
Jesse Yurkovich commented 2022-07-17 04:14:44 +02:00
Member
Copy Link

Added subscriber: @deadpin

Added subscriber: @deadpin
Jesse Yurkovich commented 2022-07-17 04:14:44 +02:00
Member
Copy Link

Confirmed here as well using a device with Intel graphics on Win10.

Mesh objects, Curve objects, Point lights, Sun lights work correctly.

Cameras, Area lights, and Reference Images do not work.

Confirmed here as well using a device with Intel graphics on Win10. Mesh objects, Curve objects, Point lights, Sun lights work correctly. Cameras, Area lights, and Reference Images do not work.
Pratik Borhade commented 2022-07-18 07:15:24 +02:00
Member
Copy Link

Added subscribers: @goldpasma, @Patnard

Added subscribers: @goldpasma, @Patnard
Pratik Borhade changed title from Regression: Unable to move camera/area light with gizmo to Regression: Unable to move camera/area light with gizmo (intel GPU) 2022-07-18 07:15:43 +02:00
Rex commented 2022-08-02 15:56:25 +02:00
Copy Link

Added subscriber: @jacksonhomeza

Added subscriber: @jacksonhomeza
Rex commented 2022-08-02 15:56:25 +02:00
Copy Link

Hi Pratik,

   Do you have any feed back on this issue yet.

Regards,
Rex

Hi Pratik, ``` Do you have any feed back on this issue yet. ``` Regards, Rex
Pratik Borhade commented 2022-08-02 16:07:06 +02:00
Member
Copy Link

Hi @jacksonhomeza, this is hardware specific issue.
As far as I can tell, developers need access to similar setup to fix such problem.
Wait until they get access to a system where they can redo this bug :)

Hi @jacksonhomeza, this is hardware specific issue. As far as I can tell, developers need access to similar setup to fix such problem. Wait until they get access to a system where they can redo this bug :)
Jesse Yurkovich commented 2022-09-17 23:59:57 +02:00
Member
Copy Link

Added subscriber: @hsm.graphic

Added subscriber: @hsm.graphic
bryce commented 2022-09-19 04:07:48 +02:00
Author
Copy Link

The issue has been fixed for me in the latest version of blender

The issue has been fixed for me in the latest version of blender
Patrick commented 2022-09-20 17:54:38 +02:00
Copy Link

Removed subscriber: @Patnard

Removed subscriber: @Patnard
Jeroen Bakker commented 2022-11-08 11:41:13 +01:00
Member
Copy Link

I am able to reproduce on 642ff82f7, only affects translate operation on camera. Seems like the control doesn't highlight, which might be a focus test issue. It is working for meshes...

system-info.txt

I am able to reproduce on 642ff82f7, only affects translate operation on camera. Seems like the control doesn't highlight, which might be a focus test issue. It is working for meshes... [system-info.txt](https://archive.blender.org/developer/F13867598/system-info.txt)
Jeroen Bakker commented 2022-11-21 15:58:39 +01:00
Member
Copy Link

I have been able to reproduce, but haven't found a solution yet or a cause what is happening.
Will tag it as known issue for now.

I have been able to reproduce, but haven't found a solution yet or a cause what is happening. Will tag it as known issue for now.
Jesse Yurkovich commented 2022-12-05 04:51:03 +01:00
Member
Copy Link

Added subscriber: @Sonario648

Added subscriber: @Sonario648
Pratik Borhade commented 2022-12-12 05:28:23 +01:00
Member
Copy Link

Added subscriber: @IMRAN91

Added subscriber: @IMRAN91
Abdillah Prasetyo commented 2023-01-01 04:05:01 +01:00
Copy Link

Added subscriber: @yokski

Added subscriber: @yokski
Jesse Yurkovich commented 2023-01-07 22:20:55 +01:00
Member
Copy Link

Added subscriber: @prasadsanctuary

Added subscriber: @prasadsanctuary
Jesse Yurkovich commented 2023-01-16 04:00:21 +01:00
Member
Copy Link

Added subscriber: @sloloo

Added subscriber: @sloloo
Philipp Oeser removed the
Interest
EEVEE & Viewport
 label 2023-02-09 15:12:33 +01:00
law ho chung commented 2023-03-06 18:57:26 +01:00
Copy Link

I think I found some clues about why this bug happens.

Attached is a video.
In the video, you can see if I click-select the default camera, the gizmo won't work. But if I click-select the default cube, and then drag-select the default camera, the gizmo magically works again.

I think it also confirms that the bug relates to the yellow rectangle UI that is used for changing the focal length of the camera. There are something strange about the yellow rectangle UI also. If I press A twice, I suppose everything in the viewport should be deselected but the focal length UI will be still active and colored yellow.

I hope this information may help the debugging or at least provide a workaround to move the camera with the gizmo. You just need to make sure you deselect everything including the focal length UI of the camera, and then drag-select the camera.

@Jeroen-Bakker I wonder if this may give you some clues for the cause. Thank you for looking into this issue.

I think I found some clues about why this bug happens. Attached is a video. In the video, you can see if I click-select the default camera, the gizmo won't work. But if I click-select the default cube, and then drag-select the default camera, the gizmo magically works again. I think it also confirms that the bug relates to the yellow rectangle UI that is used for changing the focal length of the camera. There are something strange about the yellow rectangle UI also. If I press A twice, I suppose everything in the viewport should be deselected but the focal length UI will be still active and colored yellow. I hope this information may help the debugging or at least provide a workaround to move the camera with the gizmo. You just need to make sure you deselect everything including the focal length UI of the camera, and then drag-select the camera. @Jeroen-Bakker I wonder if this may give you some clues for the cause. Thank you for looking into this issue.
system-info.txt
14 KiB
2023-03-06 09-42-43.mp4
3.1 MiB
Jeroen Bakker commented 2023-03-07 07:24:37 +01:00
Member
Copy Link

drag select uses a different approach to selection than click select. Thanks for your research.

currently we are resesigning selection , but it is unclear when that will land. When that is a bit further I will check if it solves this issue.

drag select uses a different approach to selection than click select. Thanks for your research. currently we are resesigning selection , but it is unclear when that will land. When that is a bit further I will check if it solves this issue.
Jeroen Bakker added
Priority
Normal
 and removed
Priority
High
 labels 2023-03-07 07:24:51 +01:00
Rex commented 2023-06-08 10:44:30 +02:00
Copy Link

Hi Guys,
Any update on this bug.

Regards,
Rex

Hi Guys, Any update on this bug. Regards, Rex
Oluwatowo-Rosanwo commented 2023-06-10 20:41:08 +02:00
Copy Link

I am experiencing this issue in Version 3.5.1

I am experiencing this issue in Version 3.5.1
unknown-1 commented 2023-06-15 22:46:29 +02:00
Copy Link

Meow?
Okay I have the exact same issue, you could swap devices and there will be no change. here is a little thing that's interesting though (at least to me) when I first got blender (the latest version as in the version as of now. meaning I'm a noob (however I'm learning fast)) both the light and the camera worked perfectly fine.

they could slide on any axis at my will. however, now I have to move the light off of all the axis which drives me crazy. while An expert can make quick work I would prefer it on the axis please. to make this issue simpler. all you have to do is open a new file and click on them then try the slide.

it won't work.

Meow? Okay I have the exact same issue, you could swap devices and there will be no change. here is a little thing that's interesting though (at least to me) when I first got blender (the latest version as in the version as of now. meaning I'm a noob (however I'm learning fast)) both the light and the camera worked perfectly fine. they could slide on any axis at my will. however, now I have to move the light off of all the axis which drives me crazy. while An expert can make quick work I would prefer it on the axis please. to make this issue simpler. all you have to do is open a new file and click on them then try the slide. it won't work.
unknown-1 commented 2023-06-29 04:08:31 +02:00
Copy Link

hey Pratik Borhade. I can confirm the hot key G is a way around this bug however I still prefer to move my light and camara around on the axis. I hope this helps further help with the bug. and dare I trust my instincts its a bug that effects just the axis and not the movement it's self. (If I'm wrong sorry. about my rabbit trail. I truly am trying to help and I don't like this bug at all (even thought I currently only use blender for 3D printing I would like to further my learning into learning how the video creating stuff works))

hey Pratik Borhade. I can confirm the hot key G is a way around this bug however I still prefer to move my light and camara around on the axis. I hope this helps further help with the bug. and dare I trust my instincts its a bug that effects just the axis and not the movement it's self. (If I'm wrong sorry. about my rabbit trail. I truly am trying to help and I don't like this bug at all (even thought I currently only use blender for 3D printing I would like to further my learning into learning how the video creating stuff works))
Errant commented 2023-07-06 17:46:27 +02:00
Copy Link

Can confirm this bug on Intel Iris Xe Driver Version 31.0.101.4502 (latest from intel)

Oddly enough moving lights with the gizmo works in Blender 3.3.8, but moving a camera with the gizmo is still a no-go.

Latest version that works with both lights and cameras using the gizmo (that I've tested) under my conditions is 3.1.2.
...
I know that many factors go into whether an issue gets a fix or not, the most important being commonality - but his may be an extremely frustrating issue for anyone who uses a lower-powered system for remote work. And EXTREMELY frustrating for anyone with a disability (like me) that makes the typical Blender multi-key shortcuts practically unusable. I use an addon called Lazyviewport and an altered keymap. And my keymaps and preferences from 3.3.8 will not import into 3.1.2. Reverting back this far is massively disruptive. Not that that will motivate anyone to address this more - this bug just significantly affects me due to my particular and unavoidable reliance on the gizmo, and I doubt that my needs are going to be very common.

Can confirm this bug on _Intel Iris Xe Driver Version 31.0.101.4502_ (latest from intel) Oddly enough moving lights with the gizmo works in _Blender 3.3.8_, but moving a camera with the gizmo is still a no-go. Latest version that works with both lights and cameras using the gizmo (that I've tested) under my conditions is _3.1.2_. ... I know that many factors go into whether an issue gets a fix or not, the most important being commonality - but his may be an extremely frustrating issue for anyone who uses a lower-powered system for remote work. And EXTREMELY frustrating for anyone with a disability (like me) that makes the typical Blender multi-key shortcuts practically unusable. I use an addon called Lazyviewport and an altered keymap. And my keymaps and preferences from 3.3.8 will not import into 3.1.2. Reverting back this far is massively disruptive. Not that that will motivate anyone to address this more - this bug just significantly affects me due to my particular and unavoidable reliance on the gizmo, and I doubt that my needs are going to be very common.
unknown-1 commented 2023-07-13 23:04:00 +02:00
Copy Link

I decided to dig through this bug a bit more. and in the attached file I have every light and camara in version 3.1.5. here is the interesting part: only the thing able to move in this file on the axis without hotkey G is. fingers crossed this info helps.

I decided to dig through this bug a bit more. and in the attached file I have every light and camara in version 3.1.5. here is the interesting part: only the thing able to move in this file on the axis without hotkey G is. fingers crossed this info helps.
bug aid.blend
851 KiB
Slippy commented 2023-08-22 04:28:11 +02:00
Copy Link

I'm running into this in Blender 3.6.3 (Aug 20th build)

Card: A770 16gb
Arc driver 4633
OS: Win11 version 22h2

I'm running into this in Blender 3.6.3 (Aug 20th build) Card: A770 16gb Arc driver 4633 OS: Win11 version 22h2
CannotMoveLight_A770.mp4
496 KiB
law ho chung commented 2023-08-22 20:14:12 +02:00
Copy Link

drag select uses a different approach to selection than click select. Thanks for your research.

currently we are resesigning selection , but it is unclear when that will land. When that is a bit further I will check if it solves this issue.

@Jeroen-Bakker thanks so much for the info! I have a rough idea for a workaround.

When I compared the main difference of the outcomes of "click select" and "drag select", I noticed for "drag select", it will disable

  1. a camera's focal length selection box
  2. a light's radius selection circle

So I wonder if we can add a preference to disable these selection UIs as a workaround? Assuming hit detections of these UIs might have caused the gizmo to fail.

Can anyone implement this preference? Or if someone can point me to the info about how I may add this preference I would love to work on this.

> drag select uses a different approach to selection than click select. Thanks for your research. > > currently we are resesigning selection , but it is unclear when that will land. When that is a bit further I will check if it solves this issue. > > @Jeroen-Bakker thanks so much for the info! I have a rough idea for a workaround. When I compared the main difference of the outcomes of "click select" and "drag select", I noticed for "drag select", it will disable 1. a camera's focal length selection box 2. a light's radius selection circle So I wonder if we can add a preference to disable these selection UIs as a workaround? Assuming hit detections of these UIs might have caused the gizmo to fail. Can anyone implement this preference? Or if someone can point me to the info about how I may add this preference I would love to work on this.
Slippy commented 2023-08-28 00:48:05 +02:00
Copy Link

Would it be better to have both the Camera Focal Length and Light Radius functions available only when a modifier key is used?

Without modifier keys, the default (expected?) move gizmo can be implemented on these type of objects.

Would it be better to have both the **Camera Focal Length** and **Light Radius** functions available only when a modifier key is used? Without modifier keys, the default (expected?) move gizmo can be implemented on these type of objects.
Rex commented 2023-09-23 11:32:27 +02:00
Copy Link

Just another comment. I used a force field during the week. The move gizmo does not work on force field wind as well, in versions 3 and 4. It does work in version 2.

Just another comment. I used a force field during the week. The move gizmo does not work on force field wind as well, in versions 3 and 4. It does work in version 2.
Neylz commented 2024-02-03 19:39:59 +01:00
Copy Link

I can confirm the issue on Latest 4.0.2 with an Intel(R) Iris(R) Xe Graphics with the latest graphics driver available 31.0.101.4644.

I can confirm the issue on `Latest 4.0.2` with an Intel(R) Iris(R) Xe Graphics with the latest graphics driver available `31.0.101.4644`.
system-info.txt
12 KiB
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
brush-assets-project
universal-scene-description
fix-121021
blender-v4.1-release
blender-v3.3-release
blender-v3.6-release
blender-v3.6-temp_wmoss_animrig_public
temp-sculpt-dyntopo
gpencil-next
anim/animation-id-113594
blender-v4.0-release
blender-projects-basics
bridge-curves
sculpt-blender
asset-browser-frontend-split
asset-shelf
tmp-usd-python-mtl
tmp-usd-3.6
blender-v3.5-release
blender-v2.93-release
realtime-clock
sculpt-dev
bevelv2
xr-dev
v4.1.1
v3.6.11
v3.3.18
v4.1.0
v3.3.17
v3.6.10
v3.6.9
v3.3.16
v3.6.8
v3.6.7
v3.3.14
v4.0.2
v4.0.1
v4.0.0
v3.6.5
v3.3.12
v3.6.4
v3.6.3
v3.3.11
v3.6.2
v3.3.10
v3.6.1
v3.3.9
v3.6.0
v3.3.8
v3.3.7
v2.93.18
v3.5.1
v3.3.6
v2.93.17
v3.5.0
v2.93.16
v3.3.5
v3.3.4
v2.93.15
v2.93.14
v3.3.3
v2.93.13
v2.93.12
v3.4.1
v3.3.2
v3.4.0
v3.3.1
v2.93.11
v3.3.0
v3.2.2
v2.93.10
v3.2.1
v3.2.0
v2.83.20
v2.93.9
v3.1.2
v3.1.1
v3.1.0
v2.83.19
v2.93.8
v3.0.1
v2.93.7
v3.0.0
v2.93.6
v2.93.5
v2.83.18
v2.93.4
v2.93.3
v2.83.17
v2.93.2
v2.93.1
v2.83.16
v2.93.0
v2.83.15
v2.83.14
v2.83.13
v2.92.0
v2.83.12
v2.91.2
v2.83.10
v2.91.0
v2.83.9
v2.83.8
v2.83.7
v2.90.1
v2.83.6.1
v2.83.6
v2.90.0
v2.83.5
v2.83.4
v2.83.3
v2.83.2
v2.83.1
v2.83
v2.82a
v2.82
v2.81a
v2.81
v2.80
v2.80-rc3
v2.80-rc2
v2.80-rc1
v2.79b
v2.79a
v2.79
v2.79-rc2
v2.79-rc1
v2.78c
v2.78b
v2.78a
v2.78
v2.78-rc2
v2.78-rc1
v2.77a
v2.77
v2.77-rc2
v2.77-rc1
v2.76b
v2.76a
v2.76
v2.76-rc3
v2.76-rc2
v2.76-rc1
v2.75a
v2.75
v2.75-rc2
v2.75-rc1
v2.74
v2.74-rc4
v2.74-rc3
v2.74-rc2
v2.74-rc1
v2.73a
v2.73
v2.73-rc1
v2.72b
2.72b
v2.72a
v2.72
v2.72-rc1
v2.71
v2.71-rc2
v2.71-rc1
v2.70a
v2.70
v2.70-rc2
v2.70-rc
v2.69
v2.68a
v2.68
v2.67b
v2.67a
v2.67
v2.66a
v2.66
v2.65a
v2.65
v2.64a
v2.64
v2.63a
v2.63
v2.61
v2.60a
v2.60
v2.59
v2.58a
v2.58
v2.57b
v2.57a
v2.57
v2.56a
v2.56
v2.55
v2.54
v2.53
v2.52
v2.51
v2.50
v2.49b
v2.49a
v2.49
v2.48a
v2.48
v2.47
v2.46
v2.45
v2.44
v2.43
v2.42a
v2.42
v2.41
v2.40
v2.37a
v2.37
v2.36
v2.35a
v2.35
v2.34
v2.33a
v2.33
v2.32
v2.31a
v2.31
v2.30
v2.28c
v2.28a
v2.28
v2.27
v2.26
v2.25
Labels
Clear labels   
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
This issue affects/is about backward or forward 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
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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 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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
16 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#98932
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?