Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "Solidify Modifier wrong solidification normals in some cases\nOperating system: Windows 11\nGraphics card: ATX4000\n\nBroken: 3.5.0\n\nIn some corner cases, the Solidify modifier uses wrong solidification normals.\n\nWith the \"Faces linked only by one vertex.obj\" object, where some faces are sharing only one vertex and no edge, the solidification behaves as if ignoring that shared vertex.\n\nWith the \"Triangulated mesh wrong solidification.obj\" object the vertex in coordinates (-1, 1, -1) does not solidify properly, while the exact same mesh, but not triangulated (\"Triangulated mesh right solidification.obj\" object) solidifies right.\n\n", "Remesh Modifier in Voxel mode produces surface artifacts when Adaptivity enabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: \n - 2.83.9\n - 2.91.0 Beta\n - 2.92.0 \nWorked: never\n\nRemesh modifier produces artifacts on mesh which look like a result of bad triangulation.\n\n1. Open attached blender file\n2. Open modifier panel and select testMesh\n3. Change adaptivity value from 1 to 0 cm and back\n4. Observe black shading artifacts \n[remesh_bug.blend](remesh_bug.blend)\n", "Custom Normals: some operations that alter topology (bisect, loopcut, subdivide, knife, triangulate modifier) destroy them while other operations (e.g. Connect Vertex Path, triangulate operator) preserve them\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.2\nWorked: unknown\n\nMesh bisect generates incorrect normals when applied to a face generated using bevel with \"harden normals\" applied\n\n1. Start with the default cube\n2. In the cube properties, enable auto smooth normals (Object Data -> Normals -> Auto Smooth)\n3. Enter edit mode\n4. Select one edge and bevel it\n5. In the operator panel, ensure that \"harden normals\" is enabled\n6. Select the whole model\n7. Bisect the cube so the bevelled edge is split in half\n\nThe bad normals should now be visible. You can enable normal indicators in Overlays -> Normals -> Split face normals (the second option of the three icons). You can also go to object mode to remove the wireframe and make the bad shading more obvious.\n\n[bevel and bisect.mp4](bevel_and_bisect.mp4)\n\nNote that traditionally, topology altering operations were not expected to preserve custom normals, see for example \n- #69290 (Loop cut and knife tools makes wrong shading on the mesh)\n- #53763 (Operations that alter topology (e.g. Mirror modifier AND mirror operator, loopcut, subdivide, knife) destroy custom normals)\n\nThen there has been 93c8955a72 which was a nice improvement for some operators (but was missing others afaict).\n(check usages of `BM_custom_loop_normals_to_vector_layer`)\n\nSo this now leaves us in the situation which feels puzzling/inconsistent:\nOn the reported geometry for example `Connect Vertex Path` works as expected, whereas `Knife` doesnt:\n[#97698.webm](T97698.webm)", "Mirror threshold too high, values less than 0.00002 are snapped to center\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.83.3\nWorked: 2.79b\n\nBlender 2.8x has a bug that forces it to snap to the YZ plane with a value less than 0.00002.\nThe above is occurring with the snap off.\nThe bug occurs even if the vertex's X coordinate is moved to more than 0.00002.\nDuplicating the object does not eliminate the bug.\n\n3D Viewport / Edit Mode.\nCreate an object with the following vertices:\n```\nObject-1 = {\n Vertex-A x = 0.00002, y = 0.00005, z = 0.0\n Vertex-a x = -0.00002, y = 0.00005, z = 0.0\n Vertex-B x = 0.000019, y = -0.00005, z = 0.0\n Vertex-b x = -0.000019, y = -0.00005, z = 0.0\n}\n```\n3D Viewport / Edit Mode / Tool / Options / Mirror X [enable].\n3D Viewport / Edit Mode / Snap [disable].\nSelect Vertex-A and Vertex-B.\nMove Vertex-A and Vertex-B.\nBlender 2.8x has a bug that forces it to snap to the YZ plane with a value less than 0.00002.\n\n3D Viewport / Object Mode.\nDuplicate the Object-1 to obtain the Object-2.\n3D Viewport / Edit Mode.\nMirror the vertices of object 2 as if they were object 1. This causes the same problem.\n\nEnlarge the Object-2 sideways.\nMirror the vertices of Object-2. The same problem still occurs. The problem occurs even if the Vertex-B x-coordinate is greater than 0.00002 after magnification.\n\n\n[X-Mirror_bug.blend](X-Mirror_bug.blend)\nThe objects in the X-Mirror_bug.blend file are very small, so zoom in on the view to the maximum size.\n\n\nThis is a 2.79b file with the X-Mirror working correctly:\n[X-Mirror_2.79b.blend](X-Mirror_2.79b.blend)\n\n\nThe difference in x-mirror behavior between 2.8x and 2.79b is shown in the following video:\n[Blender 2.8x BUG_X-Mirror.mp4](Blender_2.8x_BUG_X-Mirror.mp4)\n\n[Blender 2.79b X-Mirror.mp4](Blender_2.79b_X-Mirror.mp4)\n\n\nIf it is unintentionally aligned to the YZ plane like 2.8x, it will not be possible to edit it (if this behavior is a specification, it will be useful if you can implement it as a function separate from the mirror, align it to the YZ plane, and set a threshold to align).\n\n**When importing model data from the outside and editing a mirror, all vertices with an X coordinate of less than 0.00002 are already implicitly aligned to the YZ plane, so editing with an X mirror is no longer possible at all. Hence, until this bug is fixed, edits involving X mirrors should use 2.79b.**\n", "The object is not zoomed in Sculpt Mode when you click on Frame Selected\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel 4.5.0 - Build 23.20.16.4944\n\nBroken: version: 2.91.0\n\nI don't know if it's a bug or if it should be. In Object Mode, when you click on Frame Selected, the object is centered and zoomed to the full screen, but in Sculpt Mode, the object is only centered on the screen, but not zoomed.\n\n[Frame_Selected.mp4](Frame_Selected.mp4)", "Strange shading behaviour when using boolean modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nWhen using a boolean modifier with an object that on a target object it uses the normals of the boolean object on the target object to determine the shading on the affected areas of the target object.\n\nWhen using a boolean modifier with an object that on a target object it uses the normals of the boolean object on the target object to determine the shading on the affected areas of the target object.\nThis means, that when using a boolean object that has shade flat on a target object that has shade smooth, the resulting object will have smooth shading everywhere except where the boolean operation happens.\nAdditionally, when using custom split normals (like e.g. weighted normals) it applies the custom split normals on the target object.\n\nThis behavior already seems pretty strange to me, since it almost always gives strange results since oftentimes the normals from the boolean object and the target object don't perfectly match, causing weird shading issues.\nI can understand that this may be an intentional feature, but it just brings so many problems, since normal editing modifiers after a boolean modifer like weighted normals don't affect the areas affected by the boolean modifier, meaning to tweak shading in these areas you have to tweak the normals of the boolean object and somehow make a seamless transition to the target object...\nApart from that it also causes some other problems, that are a worth a seperate bug report, which i will write shortly.\n\nAn additional problem with this is that shade smooth and shade flat aren't considered custom spilt normals, so after applying the boolean modifier the areas affected by the boolean modifier will change it's shading to that of the target object, since the shade smooth isn't applied as a custom normal.\nFor some reason that doesn't happen automatically, since directly after you aplly the boolean modifier the shading doesn't change immediately, instead it only changes when you \"recalculate\" the normals when using left click -> shade flat or shade smooth.\n\nA test file to demonstrate this behavior:\n[Test_file3.blend](Test_file3.blend)\n\nAfter applying the boolean modifier and \"recalculating\" the normals using left click -> shade flat or shade smooth the normals left from the boolean modifier will have vanished.\n\n\n", "Custom normals design for curves\nCurrently curve normals are calculated automatically. We have two modes, Z-Up, and \"Minimum Twist\".\nWe probably want to introduce X-Up and Y-Up too, just for consistency, but this won't give enough control in some cases still. So we still need some ability to make normals more custom.\n\n**Option 1: Custom Normals**\nOne solution is to use a \"Set Custom Normals\" node. However, that requires accepting that the normals might not be orthogonal to the tangent, or making it a lossy operation.\n\n**Option 2: \"up\" Attribute**\nAnother option is adding another attribute that influences the automatic calculation of normals like `tilt` does currently.\nThe `up` attribute would be an initial starting direction for the normal. The final normal would be the direction most aligned with the up direction that's still orthogonal to the tangent.", "Z-fight with invisible face in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nWorked: \n\nI have 2 cubes. Bigger one is set viewport display as wire. Both share the same XZ plane. In Object mode shading is fine, but if I enter in Edit mode with smaller cube artifacts are appear.\n\n[ladder_01.blend](ladder_01.blend) \n\n", "Remove normalization from original coordinate attribute (CD_ORCO)\nFrom #95776:\n\n> The internal CD_ORCO attribute is normalized to 0..1 which is not really helpful, not even as default texture coordinates. It would be good to do some refactoring so these are stored unnormalized and then applying any additional texture space scaling for rendering only.", "Mirror expand with asymmetric objects\nOperating system: Linux-5.4.0-99-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.0 Alpha\n\nThis has been an issue ever since the feature was introduced in Blender 2.93. The expand operators like Mask Expand (Shift + A) and Face Set Expand (Shift + W) in Sculpt Mode are fully working with the default mirror settings enabled.\nBut if the model is not symmetrical it will try to find another nearby surface to mirror the expand operator on.\nBut there is no distance limit to this. The operator will be mirrored, even if the nearest surface is somewhere completely different.\nThis even happens if the entire object is only on the -X side of the origin and there is nothing left to mirror to.\n\n\n\n- Open attached file or:\n - Add Suzanne and remove one ear\n - Subdivide or remesh the result so there is a higher vertex count\n - Enter Sculpt Mode\n- Use the Shift + A mask expand operator on one ear\n- See where the expansion is mirrored\n[sculpt_suzzane_ear.blend](sculpt_suzzane_ear.blend)\n\n", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "Modifiers added in edit mode are undone out of order if you go back to object mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 13)\nWorked: Never (2.8+)\n\nModifiers added in edit mode are undone out of order if you go back to object mode and then start undoing.\n\nAffects both old and new undo system. There's often mentions of edit<->object transitions being problematic but just in passing; I think this is a long standing issue. Just wanted to note it down as I test out the undo systems.\n\nHoping the new undo system can account for this now.\n\n- Default scene\n- Go to edit mode on the default cube\n- Add any modifier (bevel, subdivision, etc.)\n- Add any loop cut 1\n- Add another loop cut 2\n\n- Go to object mode\n- Undo --> Modifier is removed first (out of order)\n- Undo --> Loop cut 2 is removed\n- Undo --> Loop cut 1 is removed\n\n\n", "Contradictory labels in UI. Naming of boolean properties sometimes positive, sometimes negative.\nOperating system: Any\nGraphics card: Any\n\nBroken:\nBlender 2.80.74 aka rc2\n\nInconsistency in naming leads to contradictory info.\n\n- Open Blender\n- Select an object on the scene (add one if you have nothing...)\n- Go to Object properties panel\n- Scroll down to Visibility\n- Hover \"Show in Renders\"\n- A pop-up info label reads \"Globally disable in renders\", so now you're not sure what happens if you check the box\n- Check the box\n- Open the Info Editor, the last line will read \"bpy.context.object.hide_render = True\"\n\nSo now we have three different nomenclatures for the same thing. Two that are contradictory within the UI and one that is the opposite naming of what's in the UI.\n\nInstead of having properties named \"show_name\" and some others \"hide_viewport\", all such boolean properties could be named \"show_function\" or \"enable_function\" so that you don't have to negate the negation as in hide_viewport = False\n\nSince Blender 2.8 is a breaking release, it is the time when you can implement coherent naming. After that, it's going to be much more difficult.\n\nOf course that's by far not a priority since it doesn't break Blender.", "Linked Mesh Editing Doesn't Work As Expected When Using Data Transfer Modifier\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.81 (sub 16)\n\nObject instances doesn't work as in blender 2.81\n\n\nIn blender 2.81, after entering the edit mode, all instances become active. You can see changes in real time.\nScreen below:\n\n\nIn Blender 2.82 it work ok till some time. I couldn't determine at what moment it breaks...\n\n\nChanges appears only after You enter to object mode.\n\n\n\nHere is blend file to test\n[instances_issue.blend](instances_issue.blend)\n\n\n", "Apply Parent inverse dose not take scale in to account\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.1\n3.6 alpha\n\nApply Parent inverse dose not take scale in to account while using alt+g , alt+r , alt+s to restore the coordinate\n\nnot sure if this is design intended.\n\n**Exact steps to reproduce the error**\n\nBased on the default startup\n1. create 2 cubes in same size ( display in wire frame mode for easier visual)\n2. Scale 2 cube independently in any size\n3. Parent them in either way , using any following parenting method below.\n\nParent object \nParent object Keep transform\nParent object (keep transform without inverse)\n\n*** Parent object (without inverse) works fine as intended there is no need to try on this ***\n\n4. Select child cube Apply Parent inverse\n5. Select both cube alt+g , alt+r , alt+s restore the coordinate , you will see child cube is not at the same size as parent\nbut the transform panel is displaying 1,1,1 both on the child and parent cube\n\n--------------------------------------------------------------\nrelated issue been reported \n97648\n\n" ]

[ "scaled object, mirror, applay scale -> result do have a unexpected face orientation\n{[F11322410](mirrofaceflip.blend)}Operating system: Linux-5.13.19-2-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.63.01\n\nBroken: version: 2.93.5\n\nMirroring a scaled object and apply the scale after mirroring. The apply scale flip also the faceorientation. A untouched faceorientation is expected, cause only the scale is to apply, not a apply mirro faceorientation. \n\n\n\nStart with default settings. \ndelete cam and light, \nViewport overlays -> check the Faceorientation field in the menu \n(I've done this for you in the uploaded blend file. It's needed to see what is not expected.)\n\nclick on cube\n- > press **s** (scale cube in my case)\n~x1.5\n~y1.5\n~z1.5\n- >menu Object -> Mirro -> x Local -> click on cube (the cube is mirrored now)\n(Notice the faces are in the expected orientation, everything is ok)\n- > press **shift +a** -> press **s** (to Apply scale,)\n(Notice the faces do change flip the orientation. This is not like expected, i do apply scale and not the faceorientation to the object.) \n\nPlease note the face orientation is flipped xyz local or global mirroring over the main menu bar after apply scale i do not test other apply possibilities.\n\nThank you for the very cool blender program.\nHave a nice day\nJan\n\n" ]

[ "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "GPencil: Hardlight blend issue\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83.0\n\nThe semi-transparent textures of Grease Pencil material turn black when their layer is in HardLight blend mode.\n\n- open the provided blend file\n- see, wrong alpha blending\n- NB: change the blend mode and it works as expected\n\n[GP-hardlight-blend-issue.blend](GP-hardlight-blend-issue.blend)\n\n", "Ambient Occlusion node with image texture\nOperating system: macOS 12.6.8 – 16GB\nGraphics card: Apple M1 8/4-4\n\nBroken: 3.6.3 RC\n\nWhen I mix an image texture (here a PNG) with Ambient Occlusion node, its not working, or results a weird render at least.\nIn the render-preview the image is disappearing, but in the final render is there but partially and broken (i think).\n\nAttached a screenshot and a very simple blend file.\n\nI hope I am the idiot and doing something wrong, but after a full week I didn't find the answer to this strange behavior.\n\n**Edit: it seems an earlier resolved problem is back:** [#94050](94050)\nIf I switch to CPU-rendering, its working fine... :(\n\n", "Can't display .blend thumbnail in the Windows explorer\nwindows 7 64 bit\n\nBroken: blender 2.75a c27589e\n\nCan't display .blend thumbnail in the Windows explorer!\n\nboth v2.75 and 2.75a all can't display .blend thumbnail in the windows explorer! I have install and uninstall again and again ,it's still don't display thumbnail. \n", "Switching image color space doesn't work on grayscale images in Cycles\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1060\n\nBroken: 3.0 release, 3.1 daily build (e6ca0b33e920)\n\nSwitching image's color space doesn't work on grayscale images in Cycles. Eevee and image editor displays image correctly, RGB images are also displayed correctly.\n(Tested on current 3.0 release build and today's 3.1 daily build, haven't checked older blender versions)\n\n[Test.zip](Test.zip)\n1) Open the attached file, go into rendered view\n2) Compare rendered image to the one opened in the image editor\n3) Switch to Eevee, image now displays as it should\n4a) Interesting thing, if you pack the image into the blend file using External data>Pack resources and switch to solid view and back to rendered, image updates and displays correctly", "If Grease Pencil is set to \"Stroke Depth Order: 3D Location\", blending always with the background and not with previously painted strokes\nOperating system: Ubuntu 20\nGraphics card: GT 1030\n\nBroken: 3.0\n\nIf Grease Pencil is set to \"Stroke Depth Order: 3D Location\", brush color blending seems to use only 1-bit transparency in many cases.\n\nIt is a known issue (see T75684). The linked bug is closed as a presumed limitation of Grease Pencil. However, what the dev calls a limitation there seems to be an unrelated feature (from user perspective, possibly not from a technical perspective). Namely, \"the strokes are always drawn as a billboard face to point of view\" prevents them from looking flat, despite being drawn with a brush defined in 2d space.\n\nI do not know Blender internals, but visually it looks like the problem is elsewhere: blending of colors in \"Stroke Depth Order: 3D Location\" binarizes (at least in some cases) the brush' alpha (opacity) channel. In effect, a hardly visible pixel may completely replace what is behind it. Possibly there is a way to make the scene look correctly at least when rendered.\n\nSee the model attached to the linked bug.", "gpu.types.GPUOffscreen renders nothing when samples > 0\nOperating system: Linux-5.3.0-55-lowlatency-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83.0\nWorked: None known 2.90 alpha has same issue\n\nOffscreen rendering from Python fails if GPUOffscreen buffer is created with any number of of samples > 0. If samples > 0, nothing is drawn (nor is there any error)\n\nRun the small script in the attached .blend (it is the sample script for offscreen rendering from the documentation but with samples>0)\nThe generated image is empty.\n\n(full system info also in .blend in text buffer system-info.txt)\n[MSAA bug.blend](MSAA_bug.blend)\n", "shadow catcher appearing in vector pass\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nvector data is present for the shadow catcher objects. This needs to be omitted otherwise the vector blur node can't be used to add motion blur to the 3d elements, because unwanted motion blur will be added to the environment pass. If it a backplate was used then it wouldn't be a problem, transparent film could be set, and the blur would only affect the geometry. This also has an issue though, because the vector blur pass modifies the alpha too, so the shadow catcher vector could still affect the blur of the 3d geometry even if it's hidden by transparency.\n\n\n1. open attached file\n2. go to frame 10\n3. open the compositor\n4. render still frame\n5. check the compositor backdrop (shows vector data for the shadow catcher).\n\nSame result if film is set to transparent.\n\n", "MNEE shadow/caustic do not respect transparency (dark spots)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.04\n\nBroken: version: 3.2.0 Beta\n\n**Short description**\nIf refractive shader mixed with transparent and body is mostry transparent, MNEE still produce very dark spots of shadow.\nLike this:\n\n\nFile:\n[test caustic.blend](test_caustic.blend)", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "Cycles: transparent object has black line where it intersect with other objects\nOperating system: Windows-10-10.0.18363 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 461.40\n\nBroken: 2.91.2\n\n\nWhen rendering transparent objects that intersect with other objects, black lines will appear on the intersecting area.\n\n1. Open a default scene.\n2. Add a plane to the scene.\n3. Rotate the plane a little.\n4. Move the plane up to make it intersect with the top face of the default cube.\n5. Make sure the view or camera view is very close to the intersecting area and lower the Clip Start value to 0.00001\n6. Set the renderer to Cycles and render the view.\n\n\n\n[Cycles_Black_Line_Transparency.blend](Cycles_Black_Line_Transparency.blend)", "Improve thumbnail loading from blend files.\nThumbnails are cached in tmp folder but can be outdates or not available. When this is the case the thumbnails are extracted from the blend file.\n\nCurrently the logic is as follow\n\n```\nfor each thumbnail to load:\n open file\n read all names of the same category\n read all preview images of the same category\n find the preview image that was needed as it is assumed that the name list and preview list are in the same order!\n discard the rest of the preview images (that will probably be reread in the following loop)...\n```\n\nRelated functions:\n* `IMB_thumb_load_blend`\n* `BLO_blendhandle_get_previews`\n\nOther improvements are:\n* - [ ] store preview images closer to the bhead.\n* - [x] [D12312: #90908: Reduce loading times when extracting thumbnails from Blendfiles.](D12312)\n* - [ ] add an preview index at the end of the blend file that can act as a hashmap between IDname and preview index. So we don't need to go over the whole file. \n\n", "ShaderToRGB Node plugged to alpha does not work with Alpha Clip or Alpha Hashed mode in 2.90\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.90.0\nWorked: 2.83\n\nIf ShaderToRGB Node is plugged to alpha socket of another princepled BSDF, it does not work if blend mode is alpha clip or alpha hashed in blender 2.90.\nThis combination worked in 2.83\n\nI attached a snapshot image in both cases 2.90 and 2.83.\n\n\n\nLeft image is 2.90, and Right image is 2.83.4.\nThe object becomes fully transparent in 2.90 case.\n(Though, It works if blend mode is alpha blend. \nThe problem is only in alpha clip or alpha hashed mode.)\n\n- Open the attached file in blender 2.83 and 2.90\n- Compare the viewport of both\n[ShaderToRGB_Problem.blend](ShaderToRGB_Problem.blend)", "Material Preview (and final render in EEVEE) purple\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7263\n\nBroken: version: 2.83.0\nWorked: I don't remember this bug occuring in previous versions.\n\nI know, that materials should become purple when the texture is missing.\nBut the problem is that they not behave as they should even without applying textures and also with the default material.\nThis bug occurs in EEVEE:\n1) In material preview in properties\n2) In render\n3) Sometimes - in viewport\n\nIn a render, it is also a problem with the scene surface material.\nI attach some screenshots from material preview: they are all the same default material.\n\n\n1) Open Blender\n2) Press F12 or go to material preview in object settings.\n3) ... see the bug\n\n\n\n\n\n\n\n\n", "Missing icons for the release\nThere are typically a few new features for each release that need an icon. We can collect them here and make sure they are added before the release (before Bcon3 really).\n\nCurrently missing:\n\n- [x] Geometry Nodes Editor\n- [x] Line art modifier\n- [ ] Attribute domains {[F10162715](image.png) size=full}\n - Face corner icon is using a node snapping icon\n - Points probably shouldn't have a line\n - An icon for curve control points would be great\n- [ ] Asset icon (? Could re-use the Asset Browser icon, but rather have a dedicated one)\n- [ ] Asset Browser \"Unassigned\" catalog item\n- [ ] Asset Browser \"All\" catalog tree item (? Could also just be a regular parent item)\n- [ ] Asset Browser \"Open Blend File\" button\n\n- [x] Blender File (`FILE_BLEND` currently uses the Blender logo, which is wrong)\n\n**Sculpt tools:**\n*Postponed for the next release.*\n* - [ ] ~~Mask Filter Tool~~\n* - [ ] ~~Scene Project Brush Tool~~" ]

[ "Regression: Image thumbnails in file browser sometimes do not show up\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.6.0 Alpha\n\nCaused by aa3bdfd76a3\n\nImage thumbnails in file browser sometimes do not show up.\n\nMissed during testing as the `.thumbnails` folder already had existing thumbnails for the images I was browsing, effectively hiding the issue entirely :(\n\n" ]

[ "Eevee Alpha Blend artifacts in lookdev and VR with Viewport Denoising enabled\nOperating system: Windows 10\nGraphics card: Nvidia GTX 970\n\n\nBroken: version: 3.0.0 Alpha, branch: master (modified), commit date: 2021-07-26 13:54, hash: 3059853732d7\nBroken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: 1b8d33b18c2f, type: release\nBroken: version: 2.83.16, branch: master, commit date: 2021-06-15 08:46, hash: 051567553d29, type: release\nWorked: Unknown\n\n\n\nNavigation within a viewport (such as panning / orbiting the scene) with objects that have a material with Alpha Blend enabled results in visual artifacts for those materials, seemingly regardless of the alpha channel itself (i.e. it affects materials with an alpha of one).\n\nIn my case I first saw the artifacts while using the VR mode in blender where these artifacts feel extremely exaggerated in some cases. I have an environment with foliage billboards that appear like they are slightly head-locked and they sway around a lot when moving in VR. I later realised I could reproduce similar artifacts outside of VR and then realised that disabling denoising avoided the artifacts in the editor and in VR.\n\nIt seems that Eevee's denoising introduces some kind of latency related to how the alpha blending is handled which results in temporal, visual artifacts while the viewport's perspective is changing.\n\nI'd say the reproduction below probably doesn't represent how significant the artifacts feel in VR but I think it highlights the same underlying issue (the same two workarounds that affect the editor, also help in VR).\n\nTurn on Viewport Shading: Material Preview or Rendered\n\nDelete cube\nAdd plane\nAdd material (default principled BSDF is fine, though in my case I'm working with emissive shaders and I have a modified build of Blender supporting equirectangular image textures that let me access their alpha channel)\nSet material Base Color to an Image Texture.\nCreate a new image and generate a Color Grid to set as the base color. (with or without Alpha)\nSet material blend mode to 'Alpha Blend'\n\nGyrate/pan/orbit the viewport view. (Note the artifacts are related to the viewport navigation that needs to move around, and just moving/rotating the plane itself won't show artifacts)\n\n(For the Color Grid the artifacts mainly look like shimmering, and glints on the white letters. That's quite different to the original artifacts I saw in VR for my use case but still it seems to represent the same underlying issue.)\n\nUnder render properties, toggle Viewport Denoising and perform the same viewport movements to compare.\nWith Viewport Denoising back on, switch to using Alpha Clip instead of Alpha Blend and again compare.\n\n[eevee-denoise-artifacts.blend](eevee-denoise-artifacts.blend)", "Blender 2.81 — Shadow glitches with Workbench render-engine (in viewport and same at render)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.81 (sub 9)\n\n\nBroken shadows \"traced path\" glithc effect in the air in places where geomety have \"complex area\" (when you use shadows from Workbrench render and same in viewport).\n[Screenshot ](l2ZRNEjhzLYbl2.jpg)\nHere is on [video ](#!0OoB2I7R!h1qq3DB20nOOgoxoYw9QT_kyoZO-a-1C7OSqRifExcs) uou can see it. Sorry for broken english.\n\n\nDon't know how to reproduce it step by step, so I've put the file here: \n[broken.blend](broken.blend)\n\n\n", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "Regression: broken normal shading, sharp edges appear on smooth surfaces.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: 2.93, version: 3.0.0 Alpha\nWorked: 2.83.9, 2,92\n\nCaused by 1c22b551d0\nTo fix this, 5c4d24e1fd got reverted\nProblem still persists though...\n\n\nIn newer versions normal mapping looks broken, sharp edges appear.\nEevee and Cycles have same bug.\n\nupdated: [untitled.blend](untitled.blend)\n\ndifference in shading\n**2.93 on top, 2.8 down below:**\n\n\nThis effect appears even with very small angle of clean surface (without normal maps)\n\n\n\n<video src=\"2021-05-18_16-17-05.mp4\" title=\"F10122604/2021-05-18_16-17-05.mp4\" controls></video>", "Eevee alpha blend mode bug\nOperating system: Linux-5.4.0-74-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\n\nThis bug happened since blender 2.90\n\nIn the scene the two objects with alpha blend mode, flip the transparency depending on the point of view.\n\n[0000-0050.mp4](0000-0050.mp4)\n\nTest file:\n[Ui1.blend](Ui1.blend)\n", "Topbar glitch when the Status Bar is hidden due to the process bar display\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: 2.81a, 2.82a, 2.83.0, 2.90, 2.93.3, 3.1.0\nWorked: not found\n\nIf the Status Bar is hidden, when you invoke a process that displays a progress bar, it causes a glitch.\n\nThis has something to do with the fact that the *arena* is divided into *regions*, so for example,\nthis works fine when `template_running_jobs()` is moved from `draw_right()` to `draw_left()`.\n\n\n- Hide the Status Bar\n- Press F12\n\n{[F8577145](topbar-glitch.png), size=full}\n\n[topbar-glitch.mov](topbar-glitch.mov)\n\n\n- Hide the Status Bar\n- Invoke the File Browser with File > Import or Add > Image > Background.\n\n{[F10340167](bug.mp4), layout=link}", "Texture Paint tools lead to incorrect colors on bright HDR textures in 3D\nOperating system: Linux-5.12.0-19.1-liquorix-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon RX 5700 (NAVI10, DRM 3.40.0, 5.12.0-19.1-liquorix-amd64, LLVM 11.0.0) AMD 4.6 (Core Profile) Mesa 21.0.1\n\nBroken: version: 2.93.0\nBroken: version: 3.0.0 Alpha\nWorked: N/A\n\nI am trying to touch up an HDR lightmap using the Texture Paint mode.\nAttempting to soften, smear or clone HDR images in 3D view in Texture Paint mode will lead to pixel values being clamped up to 1.0, unexpectedly removing bright spots. 2D view is not affected and the tools behave as expected. See video:\n[blendertexpaint.mp4](blendertexpaint.mp4)\n\nI have found that this line is responsible for this issue. Commenting it out fixes the problem.\nimageprocess.c#l219\nLine 219: `clamp_v4(outF, 0.0f, 1.0f);`\n\nI am unsure about the purpose of this line, or any unintended consequences of removing it. Someone else needs to take a look.\n\n1. Assign an HDR texture to an object's material.\n2. Enter Texture Paint mode\n3. Attempt to use the Soften, Smear or Clone tools to edit the texture in 3D view, in spots where the value of a pixel's R, G or B component is greater than 1.0\n4. The bright spots will unexpectedly become dark as they are touched by the tools.\n[Sample.blend](Sample.blend)\n\n", "Light clamping from Normal or Bump maps near shadow terminator in Cycles\nOperating system : Windows 11\nCPU : AMD Ryzen 9 3900X\nGraphics card : RTX 3090\nRAM : 32GB\nHas also been tested on a Ryzen 7 Laptop with Ubuntu.\n\nHas been tested on every major release post 2.9, and on 3.6 build d5fc1b9ba4b8, identical behavior on all of them.\nAll provided screenshots of the test file (and the test file itself) were made with 3.5.1 Stable (build e1ccd9d4a1d3)\n\nAll normal information from a Height map passed through a Bump Node or from a Normal Map passed through a Normal Map node introduces some sort of light-clamping around the shadow terminator. The effect starts being visible at an angle of around 66° from the light source.\nThis is especially visible when the target object is Cylindrical and/or Spherical, and lit by a single Light source (Sun Lamp).\nIt looks like this behavior doesn't affect the Displacement node, since using it in Bump Only mode instead of the Bump node gives different results (they should both give identical results, as I understand it).\n\nFrom looking at other renderers (and aesthetically speaking) it looks like the way the Displacement node does it is supposed to be the correct one.\n\nA test Blend file is provided.\n\nSimplest way to reproduce it from scratch is to put a simple repeating height pattern on a smooth cylinder, using a bump node and a simple diffuse node, and lighting that cylinder from the side with a single Sun lamp.\n\nThe behavior of the Displacement node can be tested (and compared with the Bump/Normal) by plugging the same Height pattern into a Displacement node with the Shader Option set to \"Bump Only\", and plugging that displacement node into the Material Output.\n\nI was initially thinking it to be related to (or the same issue as) this one :\n95729\nBut it has apparently been fixed (105776), while the clamping is still clearly visible even in very recent builds.\n\n", "Visual bug when using strenght tool in 3D space left for Tool Panel\nOperating system: Windows 10 64Bit\nGraphics card: Nvidia GTX 960M\n\nBroken: 2.80 RC\n\nVisual bug in Sculpt mode, Vertex Paint, Weight paint and Texture paint\n\n1. Go to Texture Paint mode\n2. Set strength tool to 1.0 (shift F)\n3. Use strenght tool hotkey (Shift F) in the narrow 3D space left for the Tool Panel\n\n", "Selected object color is weird in wireframe mode if the object color isn't single.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 3.0.0 Alpha\n\nOutline overlay seems to be drawn under wireframe.\n\n[#91619.blend](T91619.blend)\n\nImmediately visible in provided file.", "Multires spikes\nOperating system:\nGraphics card:\n\nBroken: Blender 3.00\nWorked:\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Sculpt while having multires modifier on\n2. Move \"sculpt\" level up and down\n3. Go into edit mode? I am not sure if I did do this, but I read that some people did do it to cause the artifact to appear. \n4. Artifact appear\n5. Unable to fix, without restarting [Handle safeguard v2.blend](Handle_safeguard_v2.blend)\n\nI can read online that this seems to have been a bug for long, but I couldn't find a fix. \n\nCan I use multires on my objects? What exactly caused this, and how can I fix it? \n\n", "Glitches on Video Sequence timeline\nOperating system: Linux 5.9.11\nGraphics card: Intel Haswell\n\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nShowing glitches on video sequence timeline when area of Video Sequencer resizing\n\nSteps shown on video\n\n[2020-12-02_15-19-26.mov](2020-12-02_15-19-26.mov)", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Booleans causing shadow artifacts in solid render mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 3.0.0 Alpha\nWorked: Unknown\n\nI built up a random shape using a bunch of booleans via the box cutter addon.\nThis seems to have introduced artifacts when the shape is viewed from certain angles.\n\nThe artifacts remain when applying all the modifiers. I also tried to reset various edge data like bevel weight and crease without any effect.\nAdding a triangulate modifier however cleans it up, so maybe something about the automatic triangulation is off.\n\nI compared the output with the stable release: It also shows artifacts but they look slightly different, at least with my current configuration.\n\nv.2.93.1\n\n\nv.3.0.0 (see version info above)\n\n\nIn motion from another angle, showing convergence on a point and something that looks like an [even/odd fill rule](Even%E2%80%93odd_rule) of a shape being used to draw the shadow:\n[streaks.mp4](streaks.mp4)\n\n\nI cannot offer concrete steps; my default file also has certain settings already applied.\nHere is the file that may help show the issue: [shadow-streaks.blend](shadow-streaks.blend)\n", "Trembling when selected cube in edit mode\nOperating system: MacOS Sierra - Versione 10.12.6\nGraphics card: NVIDIA GeForce GTX 680MX 2048 MB\n\nBroken: 2.83.0 (2020-06-03), 2.90 (2020-06-12)\nWorked: 2.82a\n\nA strange flicker happens when I select the faces of the cube.\n\nI select the cube.\nI change the visualization in Edit Mode.\nI set select mode to Face.\nI select the faces of the cube but they do not remain selected instead, a strange flicker of the object occurs. Here a video example:\n\n[blender_283_bug.mp4](blender_283_bug.mp4)" ]

[ "texture flickering on objects with shape keys when armature in BGE mode\n**Category**: Animation\n\n\n%%%the following issue still exists in (2.68a/windows8) :\n\n. create a mesh object with shape keys, attach a diffuse texture*\n. create an armature, set 'deform' to BGE\n. rig the object to the armature, create bone weight groups\n. setup an armature action, add bricks to play it\n- > texture flickering\n\n. set 'deform' to blender\n- > OK\n\nor :\n\n. delete every shape key\n- > OK\n\nshowthread.php?278398-Armature-causes-shapekeys-to-mess-up-object-textures-in-game\n\n* I have several texture attached to the object (diffuse, intensity, alpha, normal) so if you can't reproduce please let me know I will whare a test file.\n\nusing a GL shader, provided you don't use texture in it, it's ok too. else it's the same issue.\nif the armature is idle, the texture glitches does not move, it's like the order of verts, faces or uv is changed at every tics, when the mesh is deformed by the rig.%%%" ]

[ "Alpha bug on Principaled BSDF with GPU\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA RTX A2000 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.92\n\nBroken: version: 3.2.1\n\nDecreasing alpha makes material black in the Principaled BSDF shader when using GPU compared to CPU \n\n\n\n - Decrease \"Alpha\" on the Principaled BSDF shader\n - Change to device to either \"GPU Compute\" or \"CPU\" \n - Adjust alpha value to discern difference if not apparent when switching Device property\n\n\n**Notes**\nCPU appears to work correctly with this value, it's only on GPU on my machine that causes alpha to make the material black. Bug appears in rendered images too and not just viewport, and is present in both CUDA and Optix. \n\nMake my alpha 0% if duplicate.\n\n[Blender GPU Alpha Bug.blend](Blender_GPU_Alpha_Bug.blend)", "Backfacing wireframes show gaps in Edit Mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.1\n\nIn Edit Mode backfacing wireframes are sometimes hardly or not visible. This is especially noticeable when an edge loop is selected (see attached video). It seems as if they are covered by edges that are actually behind them. Maybe I'm missing something, but I've played with a lot of settings.\n\n[Blender Wireframe Gaps 01-1.m4v](Blender_Wireframe_Gaps_01-1.m4v)\n\n", "CPU + GPU render precision differences for small, far away area light\nOperating system: Linux-4.19.0-5-amd64-x86_64-with-debian-10.0 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74\n\nBroken: version: 2.81 (sub 8)\nWorked: (optional)\n\nThis was recently reported in this thread : \n2\n\n I can at least say, that when using small area lights below a size of 1 (e.g. meter), and it’s getting darker (the light source is far away from the object) you can clearly see this problem: CPU renders the tiles darker than the CUDA GPU.\n\n\n\nCreate a new scene with the cube, remove the default light, create an area light, resize it to lets say 10% (or 1%… the smaller the bigger the effect) and rotate it that it lights the default cube.\nHere is a .blend that reproduce the issue :\n[TileProblem.blend.blend](TileProblem.blend.blend)\n\n", "Scene Line Art problem when used with Grease Pencil objects.\nOperating system: Windows 10\nGraphics card: Radeon RX 590\n\nBroken: (2.93.0 Beta, 0f66dbea904f, master, 2021-04-21)\nWorked: ()\n\nScene Line Art or Object Line Art are located in front of the Grease Pencil objects.\n\n\n[SceneLineArt_and_GPencil.blend](SceneLineArt_and_GPencil.blend)", "Camera texture coordinate output in orthographic view is different from orthographic camera\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\n\nTexture coordinate camera output does not give expected results in the z component when viewing through the viewport in orthographic mode\n\nTexture coordinate camera output does not give expected results in the z component when viewing through the viewport in orthographic mode.\nTo see this seperate the z component and the problems will be directly visible.\nThis issue does not appear when viewing through a camera.\n\nTest file:\n[Camera_test.blend](Camera_test.blend)\n\nThank you and have a nice day!\n", "Regression: Strange crease when using proportional editing with the \"connected only\" option turned on (edge selected)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nPretty sure this is caused by 21b9231d7f\n\nWhen using proportional editing, there is a strange pinching/creasing that is going on where it should be smooth. It seems to only happen when \"Connected Only,\" is turned on\n\n1. Open new file\n2. Add plane\n3. Add a whole bunch of edge loops\n4. Enable proportional editing + \"Connected Only,\" option\n5. Grab one edge and move it up || down\n\n\n\nTest File:\n[#89968.blend](T89968.blend)", "Extreme Normal editing causes flat shading\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 2.93.0 Beta\nWorked: 2.92.0\n\nCaused by 1c22b551d0\n\n---\n\n## Short description of error:\nExtreme Normal editing(like flipping the normal and using other normal editing modifiers) causes flat shading.\n\n\n\nIn the image above,the sphere has a Data Transfer modifier which is receiving the Normals of the plane.\nAs in the upper image(2.92.0),the sphere is shaded smooth while in the lower image(2.93 beta) it gets flat shading at some faces.\n\n---\n## Exact steps for others to reproduce the error\n{icon fa-plus} OS Conditon: **WIN 10** |Blender: **2.93.0 Beta**\n- Default scene with default cube deleted.\n- Add a sphere object and a plane,add a Data Tansfer modifier to the sphere which transfers the normals of the plane to the sphere.\n- Have the sphere some negative Z axis transformation then observe its normal,the flat shading should be appearing at some angle.\n{icon bicycle spin} Below is a blend file with the setup above with an additional shading node in the material:\nThis is the additional node which filps the normals of the geometry:\n And the results in the respective versions:\n\n\n\n[NormalFlatShadingBug.blend](NormalFlatShadingBug.blend)\n\n---\nFrom #111805:\n| 2.92 | 2.93 |\n| --- | --- |\n|  |  |\n\n[shadingBug.blend](attachment)", "clay strip brush (and probably any brush) create some strange shading and geometry artifacts...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\n\nclay strip brush (and probably any brush) create some strange shading and geometry artifacts...\n\n1. open blender, subdivide the default cube in edit mode a few times,\n2. add subdiv modifier with 3 levels (25,1 million in total) and apply modifier.\n3. go to sculpt mode and start playing with the clay strip brush and brush settings a little bit...\n4. change the sculpt plane to view plane, and add a stroke continuously in the edge of the cube, and some transparent shading bug appears when i go to check the back side of the stroke made, but this get fixed when i use the smooth brush a little bit in those boundary edges...\n\n\n5. change the sculpt plane to area plane again, and try on other edge the same again, and some grid topology starts to appear suddenly in the first stroke when drawing, but when i keep drawing it was less noticeable the artifact but was still there...\n\n\n\n", "Object properties In-front doesn't work in viewport shading\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nObject properties In-front doesn't work in viewport shading\nAll the other options works in Object properties/viewport display, except for In-front \n\n\n- Open attached file\n- Go to Viewport Shading\n[lookdev_in_front_bug.blend](lookdev_in_front_bug.blend)\n", "Dae parsing issue\nOperating system:Windows 10\nGraphics card: NVidia gforce GTX660\n\n 2.79\n\n\nIt is a common error, when trying to upload an object to Second-life or Opensim, to be unable to upload a model,created in Blender, due to a \"DAE parsing issue\"\nThis object is one that is effected.\n\n[lowpol.blend](lowpol.blend)\nExport as .DAE file and upload to Opensim or Second-life", "Collection instance set to Display As Wire doesn't show in Solid mode when not selected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nCollection instanced to scene display options are probably wrongly addressed in code. I'm attaching screenshots with descriptions (JPEGs).\n\n\n\n\n\nCreate an object inside a *Collection*. Instance *Collection*to scene and change its *display as* options to *Wire* and/or *Bounds*. You'll see that *display as bounds* shows wireframe while *display as wire* doesn't show anything. I'm attaching my file to help you investigate.\n\n[displayAsBug.blend](displayAsBug.blend)\n\n(Why hunting bugs feels so good?! Glad I can help with developing Blender 💘)\n\n", "Wireframe opacity doesn't work if object is \"in front\" and viewport shading is set to material preview or rendered.\nBroken: 3.0\nWorked: \n\nWireframe opacity slider doesn't work if the object is \"in front\" and \"texture space\" is checked and viewport shading is set to material preview or rendered.\n\nSelect Cube\nObject properties-> viewport display -> in front ON\nObject properties-> viewport display -> texture space ON\nIn the viewport overlay panel, drag the wireframe opacity to lower the value.\nchange the viewport shading to preview or rendered, wire will have full opacity.", "Inconsistencies in GPU subdivision info message\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: n/a\n\nThis feature is introduced with 4d3bfb3f4195ac879b7330e981829122b2633e93\n\n1. Message does not update accordingly when...\n\n1-1. enabling and disabling GPU Subdivision in the preferences\n\n\n\n1-2. changing modifier visibility\n\n\n\n1-3. enabling and disabling auto smooth\n\n\n\n2. I don't know the technical details, but I feel that \"Using both CPU and GPU Subdivision\" contradicts to what the tooltip for GPU Subdivision says (\"Enable (...) for the last subdivision subsurface modifiers in the stack\").\n\n(On a related note, I think [documentation](viewport.html#subdivision) could be more descriptive about GPU Subdivision than just \"Under certain circumstances\".)\n\n", "Workbench: Random object color disables transparency in solid view\nOperating system: Windows 10 64bit\nGraphics card: Nvidia RTX 2080ti\n\nBroken: 2.83.1 official\n\n\n\n\nWhen setting the color of the material in the viewport to be semitransparent (Alpha value = 0.1) it works if the color of the viewport objects is set to \"Material\" it works, while if the color is set to \"Random\" the object is not semitransparent anymore.\n\nBlend file to test:\n[bug.blend](bug.blend)", "Realtime mode for line art (And more!)\nCurrently line art is still slow to a point where a slightly complex scene will not be previewed in real-time. This is a problem needing to be addressed.\n\nBecause at the moment the line art modifier is a vector calculation, it's not as fast as GPU shaders, and works in a different way as well, which means there will be a lot of differences as of how the line is shaded and what kind of style can we apply.\n\nThere are some existing way of showing line art in real-time. The outline and mesh boundary \"look\" in the viewport is already a good example of real-time line art. Other method can be implemented as well for a real-time line art that \"looks good enough\", such as:\n\n- The GPU mode code in the soc 2018, which is from this paper: cole_2009_fhl.pdf Robust, needs adjacent geometry info, pixel-level depth visibility test, need chaining for stylization.\n- Classic \"inverted hull\" approach, but this can potentially be implemented into a render engine automatic operation (just like when you plug in a displacement node). This method looks natural for organic shapes, but lack of stroke stylization.\n- Various ways to get real-time intersections, which can include involving CUDA and some newer APIs (4.x+?) in OpenGL that allows random access of lists (Not widely supported by older drivers). The most efficient way of doing intersections can be using inverted hull method and with some blending tricks in the depth buffers.\n- Image filtering and tracing, this gives flexibility with styling but as the soc 2018 code shows the performance is limited by the bandwidth of client/gpu data transfer, making it not very much desired in the first place.\n\nCurrent line art code is getting more and more parallel, so it may eventually run on CUDA. All the \"real-time\" tricks we did up there won't be significantly faster if there's a large scene either.\n\nPlease give your thoughts on this :)\n\n------\n\n**More stuff?**\n\nBecause the workings of line art directly correlates to how people draw, this would naturally leads to shading and other advanced way of expressing geometry and shape forms. This could happen in current line art architecture, but could also be another module on top that get those results that are hard for conventional render engines to handle. With possible help from geometry nodes, some work can be done, we'll see.\n\n" ]

[ "Weird glitch at some models\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.44.05 27.20.11044.5003\n\nBroken: version: 2.93.0\n\nWhen importing collada(dae) models, some weird glitch shows up (this might also happen with the other models).\n\n- Open Blender\n- File -> Import -> Collada (Default) (.dae)\n- Import a file (I used Silver the Hedgedog)\n\n[Silver_ColladaMax.DAE](Silver_ColladaMax.DAE)\n\n\n" ]

[ "Low unit scale values show wrong Values and Units in sliders\nOperating system: Linux-5.8.0-2-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: not in 2.80 or 2.83\n\nWhen the unit scale is too low (< 0.0001 e.g. 0.00009), the values in all sliders will jump up to the value they would have with a unitscale of 1.0. This causes problems with the clipping planes of the viewport camera (didn't do this in 2.80). This seems to be independend of the unit system (metric/imperial).\n\nIf this is a known limitation then the shown precision of the unit scale slider should reflect that. Also a fix for the clipping plane issue is needed as that did work in 2.80.\n\nBased on default startup.\n1. In Scene Settings: enable seperate units\n2. set unitscale of 0.00009 or less (metric r imperial)\n3. observe what the dimensions sliders tell you about the dimension of the default cube.\n4. observe the buggy floor grid in the viewport probably due to the same bug in the clipping sliders (wasn't there in 2.80)\n", "Random crashes with NVidia + GPU Subdivision (sometimes when activating X-Ray or Wireframe overlay)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\n| Graphics card: | Driver : | User:\n| --- | --- | ---\n| NVIDIA GeForce RTX 3090/PCIe/SSE2 | 4.5.0 NVIDIA 516.94 | @GabrielMoro\n| NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 | 4.5.0 NVIDIA 512.15 | @STYXtheMUTT\n| NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 | 4.5.0 NVIDIA 516.94 | @Jojolix\n|NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2|NVIDIA 516.59|@MassimilianoPuliero\n|NVIDIA GeForce RTX 3090|NVIDIA 516.94|@The5\n\nBroken: version: 3.2.2\n\nOn some seemingly random occasions, Blender crashes with the following stack:\n```lines=10\nStack trace:\nblender.exe :0x00007FF77C1458B0 BKE_subdiv_free\nblender.exe :0x00007FF77C147880 BKE_subsurf_modifier_subdiv_descriptor_ensure\nblender.exe :0x00007FF77BFFC3D0 <lambda_c000e58b9a8caf72c54e0e02a46effdb>::operator()\ntbb.dll :0x00007FFDBAF64FD0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF77BFFC6F0 BKE_mesh_wrapper_ensure_subdivision\nblender.exe :0x00007FF77CB38FA0 raycast_obj_fn\nblender.exe :0x00007FF77CB375E0 iter_snap_objects\nblender.exe :0x00007FF77CB3E530 transform_snap_context_project_view3d_mixed_impl\nblender.exe :0x00007FF77CB3F0E0 ED_transform_snap_object_project_view3d\nblender.exe :0x00007FF77CB5E7C0 applyFaceProject\nblender.exe :0x00007FF77CB5EE00 applySnappingIndividual\nblender.exe :0x00007FF77CB72F70 recalcData_objects\nblender.exe :0x00007FF77CB81010 applyTranslation\nblender.exe :0x00007FF77CB46BE0 transformApply\nblender.exe :0x00007FF77CB41920 transform_modal\nblender.exe :0x00007FF77C229D30 wm_macro_modal\nblender.exe :0x00007FF77C20F9E0 wm_handler_operator_call\nblender.exe :0x00007FF77C210BD0 wm_handlers_do_intern\nblender.exe :0x00007FF77C210000 wm_handlers_do\nblender.exe :0x00007FF77C216590 wm_event_do_handlers\nblender.exe :0x00007FF77C1FC380 WM_main\nblender.exe :0x00007FF77B2F12A0 main\nblender.exe :0x00007FF7814128B0 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDC7B67020 BaseThreadInitThunk\nntdll.dll :0x00007FFDC85A2680 RtlUserThreadStart\n```\n```lines=10\nStack trace:\nblender.exe :0x00007FF7A50C5B10 BKE_subdiv_update_from_mesh\nblender.exe :0x00007FF7A50C7880 BKE_subsurf_modifier_subdiv_descriptor_ensure\nblender.exe :0x00007FF7A52A1110 draw_subdiv_create_requested_buffers\nblender.exe :0x00007FF7A52A2080 DRW_create_subdivision\nblender.exe :0x00007FF7A52D1870 DRW_mesh_batch_cache_create_requested\nblender.exe :0x00007FF7A52C6000 drw_batch_cache_generate_requested\nblender.exe :0x00007FF7A529F1A0 drw_engines_cache_populate\nblender.exe :0x00007FF7A529B8C0 DRW_draw_render_loop_ex\nblender.exe :0x00007FF7A529C9B0 DRW_draw_view\nblender.exe :0x00007FF7A5D3FA00 view3d_main_region_draw\nblender.exe :0x00007FF7A5551070 ED_region_do_draw\nblender.exe :0x00007FF7A51A3700 wm_draw_window_offscreen\nblender.exe :0x00007FF7A51A3560 wm_draw_window\nblender.exe :0x00007FF7A51A2FB0 wm_draw_update\nblender.exe :0x00007FF7A517C380 WM_main\nblender.exe :0x00007FF7A42712A0 main\nblender.exe :0x00007FF7AA3928B0 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFD1C4A54D0 BaseThreadInitThunk\nntdll.dll :0x00007FFD1D524830 RtlUserThreadStart\n```\n\nOccasions observed:\n- try to snap objects on faces (the object that shall be snapped to is usually a complex mesh with modifiers like subdivisions, mirror, solidify, bevel and booleans)\n- toggle the shading mode between shaded and wireframe or between X-Ray and Wireframe Overlay.\n[intro.crash.txt](intro.crash.txt)\n\n\n- open attached file\n- disable and enable X-Ray multiple times\nIt happens specially when working fast.\n\n[BLENDER_Youre_Alive_v67.blend](BLENDER_Youre_Alive_v67.blend)\n\n", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Fix operators that affect hidden geometry\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar .\n\nThere are a number of operators in sculpt mode that affect hidden geometry. As a general rule this should be avoided.\n\n- [ ] `bpy.ops.sculpt.face_set_edit` to Grow/Shrink, Fair or Delete face sets needs to have the \"Modifiy Hidden\" property disabled by default and disabled in all menu and keymap entries.\n\nList of further operators:\n- [ ] `bpy.ops.sculpt.face_sets_init` \n- [ ] `bpy.ops.sculpt.face_sets_create(mode='SELECTION')`\n- [ ] `bpy.ops.mesh.paint_mask_extract()`\n- [ ] `bpy.ops.mesh.paint_mask_slice()`\n\n", "Wireframe modifier strange behaviour\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.2\n\nStrange behaviour from wireframe modifier\n\n\nTook a plane and subdivided, added a wireframe modifier, unsubdivided. Some corner vertices are pushed to the edge of scene.\n[Based on the default startup or an attached .blend file (as simple as possible)][Wireframe.BugReport.blend](Wireframe.BugReport.blend)\n\n", "Smoke sim glitch in Cycles\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.12\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nWhile rendering in cycles my smoke is missing pieces and is very blocky.\n\nMake a quick smoke sim above 60 res or up with adaptive domain (not sure if has to be with a smoke collision object) then add a principled volume to world output and change density to .03 or up. Once a light source is added like a sun and you give it a second to render you can see the weird distortions. \n\nFrom the file attached just click render and you can see the weird issue\n\nIf you want to know what this looks like in a rendered video here is one watch?v=pOM5uJ_plng&feature=youtu.be\n\n\n\n\n[smokeglitch.blend](smokeglitch.blend)\n\n\nOk so I did some more testing and it looks a principled volume smoke sim cant be in the same space as an existing principled volume area (world or just a cube)\n\n\n\n\n", "weird viewport visual glitch\nOperating system: Windows 11 64 bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti Gaming X Trio\n\nBroken: version: 3.3.1\nWorked: cant bother sorry\n\nits like the position of the viewport has an offset relative to the orientation of the camera, and the viewport has a set size and cant change.\n\nfirst go to the layout workspace and have an animation playing (must have an animation playing for the bug to happen), then create a new viewport by sliding it like im doing in the video. then change the viewport into rendering mode like im doing in the video and when you resize the viewport, it has a set size and cant be changed and the position of all parts have an offset according to the position and orientation of the camera.\n\n", "gpu module in CustomRenderEngine causes segfault\nOperating system: Linux-5.4.2-arch1-1-x86_64-with-glibc2.29 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.7\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nUsing gpu module in CustomRenderEngine render function causes segfault\n\n- Open attached blendfile\n- Run the python script from text editor\n - it is based on the example bpy.types.RenderEngine.html\n - only difference is, importing gpu module and doing a gpu.matrix.push_pop() in the render function\n - also added faulthandler to see where it crashes\n- change render engine to custom\n- hit f12 (blender crashes)\n\nIs the GPU module not suited for use in CustomRenderEngine ?\nAlso testet drawing a gpu.types.GPUBatch to a framebuffer object without doing matrix.push_pop(), it also caused a segfault. The matrix thing is just the simplest case to reproduce.\n\n[CustomRenderBug.blend](CustomRenderBug.blend)\n\n", "Extra rotation exporting to collada\nOperating system: Ubuntu 18.04\nGraphics card: Intel, Nvidia\n\nBroken: 2.79b\n\nWhen exporting to collada format it seems to add extra rotation to objects.\n\n\nI've created a single plane (file planos.bend) and exported it to file planos2.dae. Then imported and exported it 2 more times (attached results). End situation is added as planos_bug.blend.\nI'm unable to export and object in the same position I have it on blender.\nMy target is google earth and it seems imports of .dae behave identically both in GE and in Blender\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n[planos.blend](planos.blend)\n\n[planos_bug.blend](planos_bug.blend)\n\n[planos2.dae](planos2.dae)\n\n[planos2-1.dae](planos2-1.dae)\n\n[planos2-2.dae](planos2-2.dae)", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "Library Override broken for Snow character rig\nOperating system: Linux-5.15.0-73-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: 3.0 to 4.0\nWorked: never?\n\nI tried to use the Snow character, following the guidelines. But every time I use the Libary Override, the character's eyebrows and neck get stretched and distorted. When the bug does not happen at the time, when saving and reopening the file it appears\n\n- Link the CH-snow collection\n- Object -> Relations -> Make Library Override\n- Save file then reopen it\n", "Render errors [glitchy frames] with baked cloth [from the UI, commandline as well as rendering with 'Lock Interface' is OK]\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77\n\nBroken: version: 2.91.0 Alpha, branch: master, commit date: 2020-10-07 21:43, hash: d8fcd8a316\n\n\nI have a simple scene I press render animation and some of the frames come out messed up. \nIt looks like some sort of motion blur bug. Looks similar to this bug #74457 (Mantaflow foam particles as objects break motion blur)\nI have rendered this on two different PC's, the problem is the same.\nWith baked cloth physics.\n\n\n\n[Jelly Jery (buggy render) - Cycles 256 samples Intel denoised.mov](Jelly_Jery__buggy_render__-_Cycles_256_samples_Intel_denoised.mov)\n\n\n[Jelly Jery.blend](Jelly_Jery.blend)\n\n\n\n\n | cycles | glitchy |\n | -- | -- |\n | cycles command line render | OK |\n | cycles with Lock Interface | OK |\n | eevee | glitchy |\n | eevee without motion blur | glitchy |", "Mantaflow: OpenVDB glitches due to Adaptive Domain\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 650 Ti\nProcessor: Intel® Core™ i7-3770\n\nBroken: Blender 2.91.0 (b522e834ec30)\nWorked: never\n\nThe Adaptive Domain causes the smoke to shift when imported as a volume object (Import OpenVDB)\n[VDB_Ad_D-vid-C.mp4](VDB_Ad_D-vid-C.mp4)\n\n**Exact steps to reproduce the error (based on the .blend file)**\n[VDB_Adaptive_Domain.blend](VDB_Adaptive_Domain.blend)\n1. Enable Adaptive Domain.\n2. Bake the smoke simulation.\n3. The file uses relative paths, so it should import the cache automatically after the first step, but if it doesn't, select fluid_data_0001 and load the cached files.\n4. Play the animation.", "World with HDR renders different in EEVEE from 2.82 and 2.83\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.83 (sub 17), branch: blender-v2.83-release, hash: `1d2b89304a`\nWorked: 2.82\n\nIn the viewport or render the result I get is different from 2.82 and 2.83. If I remove the HDR image from the world nodetree, the issue seems to disappear.\n\nNote: Because of another bug (#73131?) you need to save and re-open the file to be sure the results are still different.\n\nThis is a simplified version of the Mr Elephant EEVEE demo:\n\n[simplified.blend](simplified.blend)\n\n\n**2.82:**\n\n\n\n**2.83:**\n\n\n**diff:**\n", "Sculpting produces weird shading artifacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\n\nWhen sculpting a low poly mesh, weird shading artifacts appear. \nIf you remove them with a modifier, then over time they reappear when sculpting\n[X9Tkiufd2w.mp4](X9Tkiufd2w.mp4)\n\n|.blend file showing in the video:|[test.blend](test.blend)\n| -- | -- |\n\n- In a clean scene with no objects, Add a cylinder (or any low poly object, preferably with N-gons)\n- Enable Shade Smooth on the object. {nav Object > Shade Smooth}\n- Go to Sculpt Mode\n- Use a brush anywhere - the affected vertices will have their normals updated and change their look\n\n||\n| -- | -- |\nIf you undo or do any operation that affects the entire mesh it will change the shading everywhere\n|\n| -- |\n" ]

[ "Strange graphical issue in solid shading mode for .dae file (collada)\nOperating system: Windows 10 Pro\nGraphics card: Radeon RX550 2GB\n\nBroken: 2.92.0, 02948a2cab44, master, 2021-02-24 16:25\nWorked: Not tested in previous versions.\n\n\nWeird graphical issue that persists when rotating the camera and moving around the scene with Solid shading turned on (pictures attached) looks like a graphical bug related to the GPU, but I have tested and updated my GPU drivers to rule this out. It renders correctly with any shading mode including edit mode, except Solid shading.\n\nRun Blender - Import the attached .dae file (3d model of an airplane interior) - Select the \"Solid\" viewport shading option - Observe the issue.\n\n[model.dae](model.dae)\n\n\n\n" ]

[ "Select next active fails in some cases (default cylinder, cube)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro K2100M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 3.1.2\n\nWhen adding object: circle or cylinder, when selecting vertices, it does not select the next vertex at command: shif + ctrl + (+).\nif I select several vertices manually and give the command: shift + ctrl + (-) deselect, it works perfectly.\n\nany other option works, works well with other objects, sphere, monkey sesame, the circle object works if you select two consecutive vertices, if you select one vertex yes one no, it no longer works. .]\n\n- add cylinder object\n- Edit mode\n- Select 2 vertices then {key shift ctrl +}\n\n[2022-05-24 19-58-17.mp4](2022-05-24_19-58-17.mp4)", "Operator Confirmation Configuration\nNote that this is not about the code that creates the confirmations (I have another proposal for that, #106691).\n\n**Background**\n\nSome operators ask a user to confirm their intentions before they proceed, as a safety measure when the operation could cause unintended damage. A simple example is the \"OK?\" you get when deleting an object by pressing the \"x\" key. The fact that doing so by pressing \"Delete\" instead does not warn is integral to this proposal.\n\nSome of these operators define a property called \"confirm\". `OBJECT_OT_delete` then uses an \"invoke\" callback called `WM_operator_confirm_or_exec` that checks this property and, if set, will show the confirmation message.\n\nIn the keymap editor we see this property as a \"Confirm\" checkmark. In this case \"X\" has it enabled and \"Delete\" has it disabled. We usually justify this difference because the \"delete\" key is nicely separated from other keys while \"x\" can more easily be hit accidentally.\n\n**Immediate Issues**\n\nThe Modelling module has brought up that some operators have confirmations that cannot be configured. These are mostly operators that have their \"invoke\" callback set to `WM_operator_confirm`. That function does not check for a \"confirm\" property and so asks for confirmation every time and cannot be turned off in the keymap. These include \"delete keyframe\", \"delete bone\", \"delete curve\", \"delete track\", \"delete marker\", \"separate bones\", \"separate curves\", \"delete mask\", \"make vertex parent\", etc.\n\nA simple solution to this is to simply fix the operators as needed. Each can call `WM_operator_properties_confirm_or_exec` to add the \"confirm\" property, and then use `WM_operator_confirm_or_exec` for \"invoke\" instead of `WM_operator_confirm`. This would then allow these confirmations to be turned off in the keymaps.\n\n**Proposed Solution**\n\nI don't think these should be configured in the keymap. Most users would find it very difficult to do so. And it doesn't seem to fit this kind of preference. If I desire a warning about an operation it is about the _operation itself_ and not the way it was launched.\n\nI think we should abandon the use of having an operator \"confirm\" property and instead move this configuration to a new section of user Preferences. I think we should have a new \"Warnings\" section with checkmarks to allow quickly enabling and disabling.\n\nIt is worth considering making this more than just a binary choice. For example, it might be nice if `OBJECT_OT_delete` could allow a choice between \"Never\", \"Always\", and \"When more than one selected\". \n\n**Longer Term**\n\nUltimately, I would prefer that more operators have optional confirmations, disabled by default. That is the reason for #106691. And have a fairly large \"Warning\" Preferences section that allows users to make Blender suit their needs. I think we should use our best judgement to set the defaults for these, but I would prefer to allow users to do things that we don't like. Allow them have no warnings at all or be nagged for every little thing. We are all different and it would be nice to allow for these differences.\n\n", "Proportional editing lag\nWin7 x64, GTX 460\n\nBroken: 2.73, 2.74\nWorked: 2.63 \n\nWith proportional editing on, I get a few seconds freeze when activate translating (G); than after freeze, \neverything goes ok. I thought that the problem was a large mesh, but 2.63 works great and without lags in the same file. \n\nMy \"bugged\" file is the one, I am working with. If it is possible, can i sent it in private and not give it to the world here?\n\nThank you!", "Reordering menu or modifier in Properties Panel spams modal events until Blender restart.\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.1\nWorked: I'm not sure the newest but tested 2.90 and it worked correctly there.\n\nIf you run *bpy.app.debug_events=True* from the Py Console, then click to move a menu or modifier in the Properties Panel, that is, drag to reorder it, you'll note that Blender goes from reporting event input data in the System Console to non-stop spamming of event.type as \"TIMER\" and event.value as \"NOTHING\" and it won't quit until you restart Blender. This can be seen by running bpy.app.debug_events, as well as in any additional addon or script that prints event.type and event.value during its modal function while running after clicking to reorder a menu or modifier in the Properties Panel.\n\nThis spamming can cause unexpected behavior in addons or scripts the user is running. For another example, if you click a menu or modifier to reorder it in the Properties Panel and then run the template code that comes with Blender \"operator_modal.py\" and paste this line within the modal function *print(event.type,event.value)* you'll see the spamming. This also happens in the latest builds of 3.1 and 3.2. \n\n\n\n\n\n\n - Open a vanilla install of Blender.\n - Go to the Scripting Workspace.\n - Enter this line into the Py Console \n\n\n```\nbpy.app.debug_events=True\n```\n\n\n - Press Enter.\n - Go to Window and press Toggle System Console.\n - Note the normal behaivor of debug_events\n - Now click and drag to reorder a menu or modifier in the Properties Panel.\n - System Console gets spammed with event.type \"TIMER\" event.value \"NOTHING\" until restart.\n - Event data of addons or scripts running modals also get spammed until restarting Blender.\n\n\n\n\n\n\n", "Splash Screen: \"Updated Preferences\" Infobox\nFor Blender 4.0 there will be various default keymap updates (#105298) that users should be aware of when loading their 3.6 preferences.\nThis task will become necessary once those patches are merged.\n\nThe idea is to add a popup to make users aware and point them towards resources to inform themselves. This will avoid frustration and many invalid bug reports.\n\n### Mockups\n\nThe addition of an info icon to the operator button that loads the previous preferences (As an indication that this will open a popup with more info).\n\n\n\nA possible layout for the main popup.\nThis info might be very important for some users, so the popup can only be closed with an explicit button press.\n\nThis also includes a an operator button \"Read more...\" that links to the relevant release notes page without closing the popup itself. An added border would make this more recognisable as a button.\n\n\n\nThis popup could then be used for future releases and other important changes (only if absolutely needed).\n\n", "Unable to fix broken linked IDs when renamed in libfile\nWindows 10\nWindows 7 x64\n\nWorked: 2.82\nBroken: 2.83.0\n\nCant rename linked collection. Error: Cannot edit external library data\n\nDefault Blender setup (first file lets call it assets.blend)\nCreate a collection and name it \"Test\" \nCreate a cube and move it to \"Test\" collection\nSave the file\n\nCreate another file (lets call it level.blend)\nLink the \"test\" collection from the assets.blend\nCheck all linking options before hiting link\nSave the file\n\nNow open assets.blend again and rename \"Test\" collection to \"Cube\"\nAnd save it again.\n\nOpen level.blend\nA message appears that link is broken\nGo to Outliner and change Display mode to Blender File\nNow go down to the linked collection\nDouble click broken collection to rename it\nError message appears \"Cannot edit external library data\"\n\nRenaming linked collections works fine in 2.82\n", "Regression: Mouse cursor jumps to the left when keep clicking on the colour circle under Windows\nOperating system: Windows 10, 21H2\nGraphics card: Intel A770\n\nBroken: 3.4, 3.6.0\nWorked: 3.3\n\nIf I keep clicking random place in the colour circle, the mouse pointer randomly jumps to the left edge of the circle. This seems to be happening only under Windows, not under Linux. \nI have only one Windows installation, so I am not sure if this would happen on other computers. Please check for it.\n\n- Just keep clicking random places on the color circle for about 10 seconds. (See the attached screen recording.)\n\nNot necessary: ~~I was using a 4K monitor with 200% scaling and Blender interface scaling was 1.0.~~", "Click Inserting Keyframes in the Graph Editor should obey Automatic Time Snapping\nCurrently in the Graph Editor, ctrl-right click allows the animator to insert a new keyframe into an f-curve. The new keyframe is inserted directly under the mouse pointer.\n\nThe problem is that the inserted keyframe is almost certainly on a non-integer frame:\n\n - breaks workflow - animators are usually not trying to animate subframes (until they are), and results in a need to clean up each frame after ctrl clicking: first ctrl click, then snap to nearest frame immediately after\n - or confuses new users who might not understand why keyframing very close to the recently inserted keyframe results in discontinuity or jumps since the 'replace' part of add and replace doesn't work when the keyframe is not exactly the same.\n\nSince the Graph Editor already has a setting for auto snapping in the header, it makes sense that ctrl right click inserting should just use the current setting (which defaults to nearest frame and eliminates the previous problems in the default setting), however new issues arise:\n\n**No Auto Snap**\nNo change from current behavior, nothing to be done.\n\n**Nearest Frame**\nThe default and most often used setting. Here we should create the new inserted keyframe to the frame nearest to the mouse. This can result in one of the following situations:\n\n\n - **best case:**animator clicks close to the snapped frame - the created keyframe is only slightly off from where the mouse was, which is ideal (fig 1), and would almost always be the case when zoomed out far enough.(fig 1)\n - **middle case:** animator clicks far from an snapped frame (perhaps we're zoomed in or are using a snap option with bigger distances, e.g. nearest marker) - the keyframe jumps a lot. (fig 2)\n # **worst case:** animator clicks far from the snapped frame which is *outside the view* - the keyframe now gets created so far away that the animator doesn't see it (no visual indication) which feels like a bug. (fig 3)\n\n\n**Frame Step**\nDoesn't map to inserting keyframes at all! perhaps we should just adopt / fall back to the same behavior as Nearest Frame\n\n**Second Step**\nDoesn't map to inserting keyframes at all! perhaps we should just adopt / fall back to the same behavior as Nearest Second\n\n**Nearest Second**\nThis maps well, however, since seconds are further apart than frames, it's more likely we'd run into the undesirable cases in Nearest Frame. We could also consider falling back to Nearest Frame as well, depending on the zoom level.\n\n**Nearest Marker**\nThis could work the same, but it feels weird/ likely to result in undesirable cases. We could fall back to nearest frame or nearest second, and have a sperate command for 'insert keyframe at marker'\n\n**Solving the problems for middle and worst case snapping**\n\nWe have some options:\n\n - Highlight keyframe location before clicking: While holding control, but before right clicking, highlight the nearest snap-target, and use an indicator to the left or right of the view if the keyframe is out of view (like a gradient or a glow). **problem** could result in annoying noise when the user presses control for other reasons, e.g. to select keyframes to the right or left (control left click)\n - Animated highlight after clicking: an attention grabbing glow that animates on and fades off after clicking, on the frame where the new keyframe is added, tells the user \"this is what you added\" after the fact. we can also borrow the idea of the glow to the left or right of the graph editor when the new keyframe is off screen.\n\n**Solving the problems for snapping settings that may not make sense for click insert keyframe**\n\n\n - Using 'fall backs' as suggest above\n - Having a different setting just for ctrl click (potentially a user preference)\n\n\nThe above is intended as a problem statement and start of discussion, not a final design. Once we decide on UX design, we could generate mockups for how it should look (UI)\n\n\n\n\n\n\n\n\n\n", "Collection visibility animated\nI need to recap with @brecht and @Sergey why we didn't push for this in 2.80. If it is doable and doesn't break our design, we should support this.\nBasically only the datablock settings (global viewport visibility, and renderability).", "Box select shortcut is missing deselect tool tips\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 1080 Ti\n\nBroken:\nBroken: 2.80, 2018-11-30\n\n\nThe circle select shortcut shows tool tips for deselect, the box select does not despite having the functionality.\n\n\n* Open blender, select new and pick \"General\".\n* Select the cube. (left click)\n* Enter edit mode. (tab)\n* Deselect all. (alt-a)\n* Enter box select mode. (b)\n* Select a vert (left click and drag)\n* Enter box select mode. (b)\n* Deselect a vert (shift left click or middle click)\n* Notice the vert has been deselected despite there being no tooltip\n\n", "After setting a shortcut for the \"Auto Keyframe\" button, there is an exception in the status display.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\nWorked: none\n\nSee below\n\nUse right click->assign shortcut key\nCreate a shortcut for the auto keyframe button e.g. ctrl+alt+n\nThen test the shortcut in a different viewport and you will see that it looks like nothing is happening.\nBut,**The auto keyframe state is actually changed**, but the button display is not refreshed, and the button dispaly state is changed only when the mouse moves to the timeline window.\n\n", "Breaking nodes API changes for 4.0\n- [x] Remove `Node.width_hidden`\n- [ ] Complete \"Spline\" to \"Curve\"/\"Curves\" rename in geometry nodes\n- [ ] Stop storing node locations relative to their parents\n- [ ] Use a separate type for internal links (in RNA too) (see [D16960](D16960))\n- [ ] Use a separate type for node group interface inputs and outputs and node sockets\n- [ ] Use dynamically allocated `char *` array to store string socket default values", "Grease Pencil: Erasing/Cutting does not auto-key layers\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.5.0 Alpha\n\nUsually whatever edits are done in Edit, Sculpt or Draw mode result in creating a new keyframe, if auto keying is enabled in the timeline.\nThe issue is that the Eraser brush and the Cutter tool in Draw Mode do not result in auto-keying.\nThis is easily resulting in lost work.\n\nNote: This is the same issue with the Annotate tools\n\nOn the other hand if \"Use Additive Drawing\" (Snowflake icon) is enabled in the header, erasing will result in correct auto-keying behaviour.\nThis inconsistency doesn't seem intentional.\n\n- Create a grease pencil object\n- Enable auto-keying in the timeline\n- Switch to draw mode\n- Go to the next frame and draw a stroke (It will correctly create a new keyframe)\n- Go to the next frame and erase part of the stroke (No new keyframe was created)", "Dissolving edge doesn't work as expected\nOperating system: Windows 10\nGraphics card: RTX 2070 SUPER\n\nBroken: 3.2.1\nWorked: not sure\n\n\nDissolving edges doesn't work as expected.\n\n\n\n\n\n[untitled.blend](untitled.blend)", "Properly handle file links (as in symlinks)\nWhile it should be fairly straight forward, I didn't fully port the file linking support to the new file-list design yet. Most work should already be done however." ]

[ "KeyMapItem collapses everything in it when changing a property of a ModalMap\nWindows 7 x64\nGeForce GTX 1070\n\nBroken: 2.78a\n\nChanging any property of a modal keybing in User Preferences results in parent entry collapsing. Additionally, previously collapsed entries get expanded.\n\n\n1. Go to User Preferences -> Input\n2. Expand any entry that has modal bindings (for expample, 3D View -> 3D View (Global) -> Circle Select)\n3. Change any property of a modal binding (for example, deactivate it).\n4. See the containing entry (Circle Select) get collapsed.", "Changing keys in Transform Modal Map collapses menu\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14800 Core Profile Context 22.3.1 30.0.15002.1004\n\nBroken: version: 3.2.0\nWorked: Perhaps never worked\n\nIn the keymap editor if you try to change hotkeys in Transform Modal Map, menus that you just expanded will collapse back to default state as shown in video.\n\nOpen Blender → Go to Preferences → Keymap → 3D View → 3D View (Global) → Move → Transform Modal Map.\nThen change any hotkey (example X to A).\nAfter that expanded menu will collapse.\n\n[0aX7cATEU9.mp4](0aX7cATEU9.mp4)\n", "Modifying any View3D Move Modal Key Configuration sub-options immediately results into close of entire Move View dropdown\nWindows 10 + GTX970\n\nBroken: 2.78a\n\n\nWhen modifying any View3D Move Modal Key Configuration sub-options, as soon as anything is modified, entire move view rollout collapses on its own.\n\n1, Go to User Preferences>Input>3D View>3D View (Global)>Move View>View 3D Move Modal\n2, Perform any change to View 3D Move Modal, for example adding new item\n\nResult: Entire Move View rollout immediately collapses\nExpected behavior: Rollout should remain open\n", "The keymap editor loses focus/ jumps around when editing modal hotkeys\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken: 2.83-3.0\n\nWhen editing modal hotkeys, the keymap editor loses focus of the item that is currently edited, in other words, it jumps around. \nThe reason for this is that if one modal hotkey section is expanded, the others are expanded too. Meaning, if I add/ remove items, it does so in these expanded sections too, causing the view to jump around.\nFurthermore, Blender collapses the section after subsequent edits, this causes all of the modal sections for a certain tool to collapse, again causing the view to jump.\n\n\n1. Go to the keymap editor\n2. Go to 3dview > Mesh > 3D View Tool: Move\n\n3. Expand the Transform Modal map section\n4. Edit the X/ Y/ Z plane to be Alt + X/ Y /Z instead of shift + X/ Y/ Z\n5. Notice the editor changes location as soon as you either:\nA) Check the Alt key\nB) Uncheck the Shift key\nC) Change the input method to mouse\nD) Restore the item after an edit using the \"←\" button\nE) Remove an item with the \"X\" button\n\n[Keymap jumps around.mp4](Keymap_jumps_around.mp4)\n\nAlso notice that both the Object and Mesh 3D view Tool: Move are expanded collapsed simultaneously in addition to the Transform Modal Map at the bottom (3rd instance) when the \"Transform Modal Map\" is expanded below the 3D view Tool: Move.\n\n**Expectation**\nI would expect the view not to change when I edit keymap items in the modal section. \n\n" ]

[ "Crash with Boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.1.2 (appears to have been broken since 3.2.0)\n\nBlender crashes when performing an Intersection Boolean between a cube and a bunch of loose faces. (Granted, this is probably not something you should do in the first place, but at least it should be limited to producing a bad result, not a crash.)\n\nI didn't find a crash log, but it's easy to reproduce.\n\n* Load the attached .blend file.\n* Scrub the timeline to frame 209. Blender crashes.\n\n[crash.blend](crash.blend)\n", "Render Artifacts with SSS + Motion Blur + Use Spacial Splits\nWhen you have the \"perfect storm\" of Subsurface Scattering, Motion Blur, and \"Use Spacial Splits\" (Render>Performance) all applied to an animated mesh, the rendered image will exhibit some pretty severe artifacts and mesh cracking on certain frames of an animation.\n\nThe main issue appears to be related to \"Use Spacial Splits\"\n\nOpen the attached zip - watch the comparison video. Open the .blend file, hit F12 to render (frame 34 is a good example)[Spacial Splits +Motion Blur Artifact Bug.zip](Spacial_Splits__Motion_Blur_Artifact_Bug.zip)\n\n[Render Bug - Spacial Splits + Motion Blur + Sss-1.m4v](Render_Bug_-_Spacial_Splits___Motion_Blur___Sss-1.m4v)", "Clicking \"Particle Edit\" mode causes Blender to crash\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.89\n\nBroken: version: 3.5.0\nWorked: I dunno\n\nCan't enter into the Particle Edit mode.\n\nThis issue is probably related to: 106927#issue-96303\n\nIn the sample file, in the Curves Sculpt mode, after converting my Curves (name of the layer: \"my_test_4\") to a particle system, then select the newly converted particle system and enter into the Particle Edit mode, and Blender crashes.\n\n\n\nA sample file is attached. Thank you!\n\n", "soft body issue\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nWith some soft body basic setting sometine the object go crazy and disappear, with almost same setting sometime it work fine. \n\nMake a Suzane and a subsurf by 3 applied, make a plane for the floor and make it collision.\nMake Suzane softbody and uncheck the goal button. Make pull and push a hight value (9.5 for exemple) and a hight Bending value (like 9). Bake it and see what append, if it work just tweak a little bit the setting and sometime the scene go crazy (Suzane disappear at frame 2 or 3).\nIf I reduce the poly count (suzane with subsurf at 2) it append less but sometime the same thing append.\n\n\n", "VSE: Overlap during handle transform fails\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha\n\nOverlap during handle transform fails:\n{[F11318256](overlap_fail.gif), size=full}\n\nEx.\n- Import a bunch of images.\n- Select the strip. \n- Separate the images(y)\n- Select all strips.\n- Select the right handle.\n- Hit G to transform.\n- Make the strips overlap in both Overwrite and Extend.\nThe result it that it is shuffling, where it was expected to Overwrite or Extend.\n\n**Slideshow**\nAn example of where the Extend in the same channel would be useful is when making slideshows, where the steps from above and Extend in the end should allow users to batch extend all strips in one go. Combined with this patch: [D10207](D10207) slideshows would be much easier to do. \n\n", "Ngon with more edge crash blender when using Multires/Subdivision Modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha, 2.93.2, \nWorked: None\n\nPlease check the video, it shows the difference when blender deal will small ngon(edge < 10) and large ngon (~=600).\nI think it should take over aleast 5000 points ngon(for some svg file)\n[2021-08-15 17-50-41.mp4](2021-08-15_17-50-41.mp4)\n\nCreat a ngon with more than 600 points\nextrude it and add Subdivision Modifier\ncrash\n[test.blend](test.blend)\n", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "Multires: Artefacts from lower subdiv level changes\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.90 (sub 0)\n\nWhile I was testing MultiRes in 2.90, I found a bug when sculpting on lower subdiv levels which recently got activated. If you for instance smooth the sculpt at a lower subdiv level and save your sculpt while at any lower subdiv level that isn't the highest one, your sculpt will deform with artefacts. Here's a demonstration:\n\n[Desktop 2020.05.03 - 17.27.17.02.mp4](Desktop_2020.05.03_-_17.27.17.02.mp4)\n\n\nHere's the file I was working on.\n[Urbosa Sculpt.blend](Urbosa_Sculpt.blend)\n\nHere's what you need to do to reproduce:\n\n1) Smooth an area with a lot of sharpness to it at the current subdiv level (it can be any level except 5 which is the highest one).\n\n2) Save the project.\n\n3) Artefacts should appear now. Change to other subdiv levels, including level 5 and repeat the save just to compared the results. The highest subdiv level should always work. An alternative way to not reproduce the bug is to smooth at a lower subdiv level and then go to the highest level available and save. Then the artefacts don't appear either.", "Sculpt. Mesh/color filters. RMB do not cancel operation immediately\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.6.0 Alpha\n\nIf i press and drag with left mouse button, right click do not cancel operation and revert it immediately. It is a bug and inconsistency with grab/rotate/scale for example. RMB works with GRS awesome, as it should!\n\n", "click-drag-releasing cursor breaks its surface projection\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.2.1, 2.93.9\n\nAlthough cursor surface project is enabled, click-drag-release breaks the projection on the object. Simply clicking once without moving works.\nThis happens either by shift-RMB or with the cursor tool.\n\n**Steps to Reproduce**\n- Open default scene -> select 3D cursor from toolbar\n- Enable `surface project`\n- Click and drag mouse to place 3D cursor over object", "Sculpt: Paint tool cavity custom curve crash\nOperating system: Windows 10\nGraphics card: NVDIA RTX 2060 Super\n\nBroken: 3.4, 3.5\n\nSteps to reproduce the issue:\n - Switch to Sculpt Mode or open default sculpting template file\n - Choose the Paint Tool\n - Click on Brush dropdown\n - Enable Cavity by clicking on Advanced >> Cavity in the \"Brush\" dropdown\n # Enable Custom Curve under Advanced >> Cavity in the \"Brush\" dropdown\n\n\n\nResult:\nNo **Custom Curve** is shown as in other Sculpting Tools & after trying to paint with the **Paint** tool setup this way blender instantly crashes.", "Applying Subdivision/Multires Modifier De-merges UV's\n### Update\n\nThe issue of custom-data (UV's specifically) becoming detached remains, this problem existed before b88dd3b8e7, it was just less obvious since selection connected near-by UV's. Now UV's are merged by default at a very low threshold when applying modifiers to mitigate the problem. Keeping this report open as it would be good if subdivision-surface didn't separate UV's, replies to this report contain some notes that could lead to a solution. In practice users should not experience problems caused by this behavior, so marking low priority. ~ @campbellbarton.\n\n----\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha \nWorked: working in 2.90 \n\nCaused by b88dd3b8e7\n\nWhen applying a subdivision modifier, certain UV's points disconnect from their neighbors. This does not seem to occur with the F3 menu subdivide operation.\n\n- Open default blender scene.\n- Subdivide cube - 1 level and apply it. Do this step 4x\n- In the UV editor use \"Alt select\" to select face loops at random.\n- Alt click around until a face loop is not fully completed, this will reveal unmerged vertices.\n- Check area that did not complete by moving faces, vertices, edges etc to confirm unmerged UV's.\nThis does not seem to be an issue with the newly added 9a52b30cc0 in my eyes, rather an issue with subdividing.\n[UV Disconnect.blend](UV_Disconnect.blend)\n\n", "Mulitres: Grab brush + 'Grab Active Vertex' option seems not intuitive or broken 3.2\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0\nWorked: (In 3.1 sort of?)\n\nI am not sure if its a bug but here we go:\nWhen you add a mulitres modifier to an object and try to sculpt on it with the grab brush it works.\nIf you enable Grab active vertex in the Brush settings it looks broken to me. Even in 3.1 the vertex are displaced from the original and impossible to grab. \n\n1. Start blender\n2. Add a sphere\n3. Add a multires on lvl 1 or 2\n4. Using the grab brush in sculpt mode works until you enable the grab active vertex option.\n\nThe blend file has the setup just try in sculpt mode the grab brush and the options.\n\n\nOn a side note the bug report said win 10 but i run win 11. It seems not to recognized my system.[GrabActiveVertexBUG.blend](GrabActiveVertexBUG.blend)", "Some transform modes don't apply absolute grid snaping \nOperating system: Windows 10 \nGraphics card: GTX 1080 ti \n\nBroken:\nBlender 2.8 January 31, 01:48:40 - 8c8979067490 Beta\nBlender 2.79 (It worked)\nBlender 2.77 (It worked)\n\nAbsolut grid snaping dont work with \"Face Inset\" and neither with loop cuts. \n\nTurn on the snaping (increment) -> turn on absolut grid snaping -> spawn a plane -> try to snap while loop cutting or inseting faces.", "unsubdivide of Multires bug\n**Blender Version**2.91\n\nI try to use unsubdivide of Multires function in blender ,but the result is error.So I test in Zbrush with same modle, it work rightly.\n\nThe thing is,I want sculpt with tank top with no thickness,and add thick ness at last.So I first sculpt with Multires (3 level subdivide),and apply it,and I loop cut the edge with 7 loop cut.After that I add Multires,and use unsubdivide,the result go wrong.\n\nI use the same modle in Zbrush,it work rightly.[unsubdivide error.zip](unsubdivide_error.zip)" ]

[ "Multiresolution behavior when using crease edge\n\nOperating system: windows10 pro 64bit　Version 1803 os build 17134.706\nGraphics card: GTX1080ti\n\n\nBroken: 2.80, b46245470f79, 2019-04-17, as found on the splash screen\nWorked: (optional)\n\n\nMultiresolution behavior when using crease edge\n\n\n\n1, set the crease edge.\n2. Set up multi resolution.\n3. Set to sculpt mode.\n4. Click Subdivide three times.\n" ]

[ "Schrodinger's Animation errors\nOperating system: Windows 10\nGraphics card: GTX 760\n\nBroken: 2.80, Hash: d30f72df8ac, 2019-06-19\n\nIf you filter the action editor by errors it will not show any unless you have seen them. This makes it very tedious to find errors with my keyframes. I've added a gif to show the problem better.\n\nMake an armature with several bones and create an action with keyframes for all of the bones. \n\nDelete one of the bones. \n\nIf you don't have enough space to show all the channels in the action editor then the filter by error thing will not correctly show you the keyframes for the missing bone.\n\nIf you scroll down and see the errors with your own eyes, the filter will work.\n\n", "Regression: Quad View Gizmo Tooltips at wrong position\nOperating system: Windows\n\nBroken: 2.93.0, `92b0803f35a7`\nWorked: 2.93.0, `0876829e7a77`\nSuspected: cf6d17a6aa\n\nIn Quad View mode gizmo-tooltips are shown at the wrong position (always at lover-left view gizmos)\n\nStart Blender, in 3D viewport press Ctrl-Alt-Q, hover mouse over gizmos.\n", "Constraints: Scaling operator do not affected by min scale limits\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: Current master.\nWorked: Never.\n\nThe scale limiter does not affect the operation of the scale operator.\n\n1. Add `Limit Scale` constraints on object.\n a. Set some `Minimum` to ON.\n2. Try to scale object by pressing `S`.\n\n[scale bug.blend](attachment)\n\n", "Regression: Damaged normals in sculpting with Multires modifier\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nWhen sculpting, sometimes breaks normals. Switching between modes fixes this.\n| Edited sculpture | Object mode |\n| -- | -- |\n|  |  |\n\n1. Open attached file.\n2. Go to Sculpt mode.\n3. Do something.\nLook at the fact that in some places the normals are damaged.", "Animation: create a full separate copy of BoneCollections while in armature edit mode\nThis is to avoid touching the main data structures in the Armature datablock while in edit mode, which interacts badly with undo.\n\nRelevant:\n- #111965\n\n", "Remove normalization from original coordinate attribute (CD_ORCO)\nFrom #95776:\n\n> The internal CD_ORCO attribute is normalized to 0..1 which is not really helpful, not even as default texture coordinates. It would be good to do some refactoring so these are stored unnormalized and then applying any additional texture space scaling for rendering only.", "GPU Subdivision not optimized in Weight Paint mode\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\nI'm not sure if it's unimplemented/unplanned or just overlooked, so I'm here to report in case.\nWhen you have a mesh using an Armature modifier and Subdivision modifier, the Subdivision will affect performance while posing the armature but enabling GPU Subdivision will noticeably improve performance during posing and animation. \n\nHowever, if you select the armature and the mesh and go into weight paint mode, allowing you to pose the rig, the GPU Subdivision will not boost performance with the Subdivision modifier. Weight Paint Pose is slower regardless as to the Subdivision modifier, just GPU Subdivision seems to be disabled here. \n\n- Open attached .blend file\n- Make sure `GPU Subdivision` is enabled in Preferences\n- in Weight Paint Mode, pose the rig (move any bone)\n- Go to object mode, select the rig and go to Pose mode\n- Compare performance when posing the rig\n\n[#101485.blend](T101485.blend)\n", "Rendering in cycles causes objects with materials to go black and shiny when using the GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 7900 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\nWorked: N/a\n\nWhen my render engine is set to cycles and device is set to GPU Computer (with HIP and my 7900 XT selected), if I look at an object with a material applied in either viewport shading or as a rendered image the model will appear black and shiny or occasionally will just show as a flat blue colour. \n\nThis issue does not occur when using the CPU as the device instead and also did not begin to occur until a few days ago (prior to which it was working fine).\n\nI've checked the same blender file on a laptop with a 3060 GPU which worked correctly so I don't think the file itself is corrupted.\n\nI have also checked multiple blend files, some of which work fine, others do not, one file has some things working and other things broken (I will attach it to this bug report)\n\n\n1. Load the attached blend file \"ArkenV1R1_Interior.blend\".\n2. Go to edit > preferences > system > cycles render devices, set it to HIP with RX 7900 XT selected.\n3. Under scene settings, change the render engine to cycles and device to GPU compute.\n4. Switch to Viewport shading.\n5. Observe that the bullets and floor panel are shown as black and shiny while the table renders correctly (grey and blue).\n6. Press F12 and observe that the rendered image also shows the bullets and floor panel as black and shiny.\n\n\n**Additional**\nIncorrectRender.png was rendered using GPU\nCorrectRender.png was rendered using CPU\n\nI will be happy to provide anything else needed to figure this out, thanks!\n\n", "Connected child bone's nominal location values affected when transformed about 3D cursor\nBroken: 2.79, 2.90.1\nWorked: N/a\n\nAs expected, when moving a single connected child bone, its location is not affected, only the rotation.\nBut it is still possible to affect them accidentally if transforming about the 3D cursor.\nThis is a minor bug, but it's a definite inconsistency.\n\n - Open attached file.\n - Move/Rotate/Scale the child bone about the 3D cursor.\nNote the bone's nominal location values in the side panel.\n\n[Connected Bone Pose Bug.blend](Connected_Bone_Pose_Bug.blend)", "Render problems\nOperating system: Windows 10 Pro Ameliorated\nGraphics card: RTX 3070 driver version 472.12\n\nBroken: v3.6 and v3.61\nWorked: v3.51 <- Using the same file created in v3.61\n\nWhile rendering a frames of an animated character, the current rendered animation frame usually shows in the 3D viewport in v3.51. However, in the broken version, it fails to show the current frame being rendered, nothing gets updated visually. Then eventually in the 3D viewport the character goes into its T pose for a few frames then the character starts losing visibility of its layers, at that point Blender crashes. \nI will create a .blend file if I am the only one getting this bug.\n\n", "Bone's Transformation constraint numbers won't be symmetrized correctly.\nOperating system:Windows 10\nGraphics card:RTX 2070\n\nBroken: 3.3.1\n\n[Use this file](https://projects.blender.orgattachment)\n\nThis will break:\n\n- open the blend file\n- delete the selected Left bone\n- select Right bone and symmetrize it\n- check both Right and Left bones' Transformation constraint setting. Numbers on the Left one will be messed up.\n\nBut this works:\n\n- delete the selected Left bone\n- go to pose mode\n- select the Right bone\n- go to edit mode again and symmetrize it\n- Transformation numbers are both fine. \n\n------\n\nOriginal description:\n\nWhen Bones have Transformation constraint and are symmetrized in edit mode, its numbers are symmetrized correctly too.(Map from numbers like Location X min , Location X max and Map to numbers like Location min max etc) but if Transformation constraint's Target and Owner space are set as not Local those numbers are totally messed up and broken.\n\n", "Adjust modifier values when using \"Apply scale\"\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nWhen using \"Apply scale\", the modifier values are not adjusted if the object scale is not [1,1,1]. I would like to suggest that the operator \"Apply scale\" iterates through all modifiers of the selected objects and adjusts all values related to scale\n\nFor example\nBevel modifier - Amount\nDisplace - Strength\nData transfer - max distance, ray radius\nUV project - Scale X, Scale Y, \netc\n\n---\n\nCurrent behaviour\n{[F9849514](image.png), height = 700}\n\n---\n\nDesired behaviour\n{[F9849529](image.png), height = 700}\n\n---\n\nsuggested Operator mockup\n\n{[F9852183](image.png), height = 300}", "Black render artifact with CPU+GPU rendering in viewport\nWindows 7 Pro\nNvidia Quadro P6000\nIntel Xeon E5-2690 v4\n\nBroken: daily builds 2.79 since at least 25.10.2017.\nWorked: -\n\nIf I enable combined CPU+GPU rendering, a black rectangle shows up on one of my objects. It shows up in viewport rendering, and also in the final render. This seems to be independent of the material used. I have provided a stripped down version of the scene where it is still visible. This time only in the viewport, the final render works for this simplified scene. \n\nThe artifact seems to be \"locked in space\", I can move or rotate the object away, so that it disappears. In some rotation angles it is not a black rectangle, but dense black lines. \nWhat is also interesting is that the surface of the object in not only black, but partly transparent. I have put a lamp and a cube inside the object in the demo scene, these should not be visible from outside, but they are.\n\n- Open file. In the render settings GPU compute should be turned on, and in the user preferences CUDA should have both the CPU and GPU selected.\n- Turn on viewport rendering. --> black box visible.\n- Then switch to CPU rendering. No more black box.\n\n[black_artifact_bug3.blend](black_artifact_bug3.blend)\n\n", "2.93 texture coordinate display bug\nOperating system: win10\nGraphics card: 2070 super\n\nBroken: 2.93.0-321eef6a0c0f 4/2\n\n\n\ntexture coordinate display bug differently in viewport compared to render\n\ni used a generated coordinate. in the viewport it seems that blender applied the coordinate after the curve modifier (maybe)\n\nbut in render it will apply the coordinate before the curve modifier, so the gradient is able to follow the curve which is my desired look.\n\nsometimes it will display the coordinate correctly but I don't know how I achieved it\n[bug.blend](bug.blend)\n\n", "Panoramic Render in Cycles. Bump bug.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.1\n\nWhen using a material with fine bump and a panoramic camera the bump appears inncorrectly in rendered view.\n\n- Give an object a material with a fine bump (e.g. noise texture 15 detail, .8 roughness. Bump strength 1, distance 1)\n- Bring camera in really close.\n- Set to cycles.\n- Switch camera between panoramic and perspective mode.\n\nPlease let me know if there are any work-arounds, this bug is causing me problems.\nThank you.\n\n" ]

[ "Odd Graphic in 2.80 User Preferences > System\nOSX 10.12.4\niMac 2.7 Ghz Intel Core i5\n32GB ram\nAMD Radeon HD 6770M 512MB\n\nBroken: blender-2.80.0-git20170419.94d5ca7cdb-x86_64\nWorked: (optional)\n\n\nOdd graphic appears in File > Preferences > System\n\n\n\n----\n\nUpdate: bisected this down to: cb2c4bfb74 this also impacts armature drawing, see: #51254" ]

[ "Texture properties not working with OSL enabled and unpacked textures\nOperating system: Linux-5.11.7-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 520 (SKL GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.92.0\nBroken: version: 2.93.0 Alpha\n\nI have a texture with RGB channels set to 1 and alpha set to 0. When trying to use this texture with OSL, the alpha property (at least) of the image texture node does not work when the texture is unpacked. I set it to channel packed, expecting the color data to be always white. The problem is that when the texture is unpacked, the color data is black.\n\n1. Open the attached file.\n2. Set viewport shading to rendered.\n3. The plane shows as white (as it should).\n4. Unpack the texture.tga file.\n5. Toggle between preview and rendered viewport shading to refresh.\n6. The plane now shows as black.\n7. Pack the texture again.\n8. The plane shows as white again.\n\n[bug.blend](bug.blend)", "Alembic export animated vertex color exports only first frame vertex color\nDebian, Nvidia GTX 1080ti\n\nBroken: 2.78-58a0c275464 and the newest ones\n\nWhen you create an animated vertex color on a mesh with dynamic paint for example, you expect it to be written into alembic while exporting it with vertex colors checked, but instead you have only first frame vertex color baked in it.\n\n1. Open attached blend file\n2. Bake dynamic paint\n3. Export abc with vertex colors checked\n4. Import that abc file and have no animated vertex color\n\nI'm also attaching that abc file.\nDon't know if it's a bug or a thing to do, sorry.\n[alembic_anim_vertex_color.blend](alembic_anim_vertex_color.blend)\n[alembic_anim_vertex_color.abc](alembic_anim_vertex_color.abc)", "Find solution to unify color picking methods with options for sample space\nReopened as, though the initial issue is invalid, the current solution, as it is, is problematic.\nThe sample_color paint operator {key S} has a problem with discoverability and is separate from both the general UI color picker and the sample tool. This needs a better design solution.\n\n**Old Description** (resolved by sample_color operator)\n\nRight now all color picking is using the display space, which usually makes it (almost) impossible to accurately pick colors from an image that is not sRGB for texture painting.\nSimilarly, for texture painting in the 3D viewport the picked color is that after shading and display transformation. This can be useful, but it should be optional. In a lot of cases the user wants to pick and draw a color from within the same image texture, without any additional color space conversion.\n\nThe View mode of the image editor already has a sample tool, which has the functionality to show the color data in image space without additional color management. So simply using this tool in paint mode for picking color with the option to select the color space would already be a huge benefit.\n\nFurther, having a similar tool for 3D texture painting would be even better, but I assume that this might have more difficult implications for the implementation. Tackling this for the image editor first using the Sample tool, might me a good trade-off for investing a small amount of work for maximum impact.\n\n[color_picker_behaviour-2021-03-02_15.50.34.mp4](color_picker_behaviour-2021-03-02_15.50.34.mp4)\n[non-color_picker.blend](non-color_picker.blend)", "Cycles Bake Selected to Active with transparency gives undesirable results\nSystem Information:\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GT 635M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\nBroken: version: 2.81 (sub 16)\n\n\nBug or unintended behavior:\nBaking using \"Selected to Active\" does not take into account transparency \n\nHow to reproduce:\nCreate two objects with materials and textures assigned to each;\n```\n One texture to be baked to\n One texture with an alpha channel (optionally a normal map)\n```\n\nIn the shader editor, modify the material of the object with a transparency channel\n```\n Join the transparent textures' alpha into the alpha of the shader that is being used\n (optionally join the color of a normal map)\n```\n\nIn render properties, enable Selected to Active and use an appropriate ray distance\n```\n Finally bake.\n```\n\nResult:\nWhen baking combined or most channels, the transparent areas will assume the color as if it were completely opaque,\nWhen baking normals with transparency, the transparent areas will mix with the normal of the geometry that is being baked to the active selection.\nBoth outcomes are unfavorable when working with transparent cards/ribbons.\n\n[bugreport.blend](bugreport.blend)\n\nI packed the textures edited the project to make the issues that I am having more clear.\n\n{[F8286028](image.png), size=full}\nThere are now 3 overlapping objects with transparency.\nAfter baking normals or color, none of the colors or normals behind the transparent objects appear because the object appears to draw over top without transparency.\nThis example also shows that with full normal transparency, the normal will then be the geometry normal of the object rather than a flat normal or anything that is below the object.", "Regression: Some particles have darker faces\nOperating system: Windows 10 1909\nGraphics card: GTX 1070 512.15\n\nBroken: 3.1 (also 3.1.1 RC)\nWorked: 3.0.1\n\nSome object instances, in a hair particle system, have darker faces\n\n3.0.1\n\n\n3.1 and 3.1.1 RC\n\n\nPress F12 in this test file:\n[Dark Particles.blend](Dark_Particles.blend)", "Retopology Overlay Color Location\nA user noted that the overlay can be difficult to see when using random object colors: 15\n\nOne solution would be to move the color from the theme to the workspace, and expose it in the overlays popover.\nI think that just exposing the color isn't enough, because editing a preference outside of the preferences window does not autosave.\nMeaning that if you change the color in the popover, save your project, and restart Blender, the color would be back to default.", "Incorrect combined texture baking with subsurface material\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nBaking result is different from what I have seen in render and has strange artifacts.\n\n\nOpen attached file and run combined baking with default settings.\n[test_bake_2_79.blend](test_bake_2_79.blend)", "USD Export don´t export Vertex Colors ( Color Attributes )\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40\n\nBroken: version: 3.2.0\nWorked: Not known\n\nUSD Exporter don´t export Vertex Colors ( Color Attributes )\n\nJust paint some VC on the default cube with Vextex Paint Mode, then try to export the cube. \nExporter don´t have the \"Color Attributes\" checkbox ( Importer has it )\nYou can then try to reimport the USD file and check that your VC aren´t there.[CUBE.blend](CUBE.blend)\n\n\n", "Allow OpenGL image drawing in UI colour space\nSince 7ad802cf3a images are stored with premultiplied alpha and in scene linear space. This produces the wrong colours when used for drawing UI elements.\n\nExample from the Blender Cloud texture browser, with the post-7ad802cf3a drawing on the left and the expected colours on the right:\n\n\n\n@brecht proposed adding a new shader that can be used from Python and that draws the textures in the correct colour space.\n", "Face orientation - no colors in X-Ray\nOperating system: windows 10\nGraphics card: NVIDIA GeForce GTX 1070 \nsame issue on different pc Samsung NP900X3C\n\nBroken: 2.83.2 and 2.90.0-f319eec88186 (latest 2020 jul 14)\nWorked: 2.80 ~ 2.82\n\n**Face orientation in X-Ray view does not show transparent colors(blue and red)**\n\n1) turn on face orientations ; \n2) turn on toggle X-Ray\n\n![2020-07-14 21-26-43.mkv_snapshot_01.48_[2020.07.14_21.57.56].png](2020-07-14_21-26-43.mkv_snapshot_01.48__2020.07.14_21.57.56_.png)\nhere how it works in 2.83.2 & 2.90.0 [2020-07-14 22-43-43.mkv](2020-07-14_22-43-43.mkv)\nand how it should like in 2.80 ~ 2.82 [2020-07-14 22-49-24.mkv](2020-07-14_22-49-24.mkv)", "Roundness fails for top corners of lighting subpanel\nWindows 11 OS\nBlender 3.0.1\n**Under 3DViewport Theme Settings, ''MenuBack\" Roundness slider only rounds the bottom part of matcap/studio light SubPanel)**\n\n", "Allow user to change the shading parameters of the asset preview generation scene\nUsers should be able to have some control over the render settings of generated asset preview icons.\n\nPersonally, I want to be able to turn off the specular lighting because it makes my assets look ugly in the previews (note the big shiny surfaces on these bushes).\n\n", "Themes: Spreadsheet Editor \"Region Text Highlight\" setting does not work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0 Alpha\n\nIn the spreadsheet editor the leftmost element where you can select the different contexts is called \"region\".\n\n\nThe text color is controlled by the \"Region Text\" property.\nThe text highlight color seems to be hardcoded to black, even though there is a \"Region Text Highlight\" setting.\n\n", "Selected Objects render state (hidden in renders) causes baking of black images (also these are visible in renders after baking, setting is not as it was before)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0\nWorked: Cannot find any - tested back to 2.81\n\nIf rendering of the selected object is not enabled, then the baking will fail with a black image created.\nStrangely the rendering icon for this object will be automatically turned-on in the outliner - if you hover your mouse over.\nBaking will still fail - even though the icon now shows that rendering is enabled.\nTurning off render, then turning it back on again will fix the problem so that baking will now work.\n\nLoad the blend file attached (or use your own scene set-up for baking).\n[Bake selected to active has black image.blend](Bake_selected_to_active_has_black_image.blend)\nClick on Bake to confirm that the baking is successful.\n\nDisable render for the Selected object.\n\nClick on Bake again, and a black image will be created.\n\nNote that the Selected object still has rendering disabled.. Move your mouse into the Outliner above the render icon, and observe that rendering for the Selected object automatically becomes enabled.\n\nClick on Bake again and observe a black image is still created.\nDisable rendering for the Selected object, then enable it again.\nClick on Bake again and the baking will be successful.\n\n\nObservations:\n1) If rendering is disabled for the active object, then this error is shown.\n\n2) The bake duration is the same whether the rendering is enabled for the selected object or not. (Mine was taking a 2.5 minutes, and it took a long time to figure out what the problem was.)\n3) Saving the blend file and reloading fixes the problem - the state is persisted as render==enabled.", "Research: refactor dotted/dashed lines to support line width.\n Almost all line types in the UI are using shaders that add geometry, so they can be any width even on some Macs that don’t otherwise support line_width greater than 1. Except for one: dotted/dashed lines. We still use these in quite a few places, sometimes even using them as solid lines. Anyway this one shader always makes 1-pixel wide lines on these problematic Macs, and those users quite often have high-dpi displays, making them almost invisible. And then we have some people who need large UI scale and/or wide lines for accessibility reasons, like one fellow who is almost blind. So just hoping that a refactor of that one shader could be on your “to do” list. " ]

[ "bake procedual material to texture not work \nOperating system: Windows 10 \nGraphics card: NVIDIA GTS 450 \n\nversion 2.93.3\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nI try to bake a procedural material to a texture and I follow many tutorials because nothing works.\nSee this example: watch?v=LLQFopN--LY\nThe resulting texture is black.\nSee my blend file : [GoldFoil.blend](GoldFoil.blend)\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "GPencil: Airbrush draw tool with solid stroke has transparency artifacts\nOperating system: Win 11, GTX 3080, Wacom Tablet\n\n\n\nBroken: 2cd7e70c18a8\nWorked: ~~3.3.0~~\n\nThe airbrush tool has artifacts around the stroke during drawing. Also what is drawn during stroke has nothing to do with the final result visually. Please see the video for the issue.\n\n\n\n- New scene -> 2d Animation\n- Select Airbrush tool from the tool pane\n- Switch to `solid stroke` material from header\n- Draw\n\n[image](attachment)\n[blender_lOlSgoorkK.mp4](attachment)\n", "Working sliders are faded in the overlays panel\nBroken: 3.0\n\n**Short description of error** \nthe wireframe and wireframe opacity sliders are faded in the overlays panel even when they're working.\n\nFor better visibility, delete the cube, add a suzanne, press ctrl+3 to subdivide it, then apply the modifier.\nIn the Object Properties, under viewport display, turn on \"show edges\" OR set the object to \"Display As: Wire\".\nIn the viewport's Overlays panel, drag the wireframe threshold and wireframe opacity sliders. Make sure that you are in solid shading and the wireframe option is off in the overlays panel. \nThe sliders are faded even though they are working.", "Blender Crashes on Render (Save As), then refuses to start\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1\nWorked: N/A\n\nFirst observed with the attached file. I tried to save a png image render from it; when I clicked \"Save As,\" Blender crashed and then... wouldn't open. It seemed to initiate startup, because the little black window that usually notified me that it was reading my userprefs.py file would blink into existence just long enough for me to register what it said, then close itself and act like I hadn't clicked it.\n\nRestarting my computer fixes the problem temporarily, until the next crash. The crashes are inconsistent, but seem to happen only when I hit main menu items like Open or Save. This includes previous versions, apparently, as I still had 3.5 installed and it does the same quick blink.\n\nThe only thing I could think of was that that Read line in the black window referred to finding the userprefs file in C:\\ when I installed everything into M:\\, but I tried copying the required path over to C:\\ with no effect and also it gives me that same message when it's working and starts up fine.\n\nI also tried repairing the 3.6.1 install, and uninstalling/reinstalling, to no effect.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "New AMD Drivers (Adrenalin 22.7.1 or 22.8.2) for Windows 10 cause toolbars to be completely black\n\nBroken:\nOperating system: Windows-10-10.0.19044-SP0\n|Graphics card:|Driver:|User:\n|---|---|---\n|Radeon RX 580 Series|4.5.0 Core Profile Context 22.7.1.220725|@GKPrasad\n|Radeon RX 580 Series|4.5.0 Core Profile Context 22.8.1.220810|@Vaskos\n|AMD Radeon RX 5600 XT|4.5.0 Core Profile Context 22.7.1.220725|@ShockHazard1\n|Radeon(TM) RX 460 Graphics|4.5.0 Core Profile Context 22.7.1.220725|@patrickshyee\n|AMD Radeon(TM) Vega 3 Graphics|4.5.0 Core Profile Context 22.8.2.220819|@Alenda\n|AMD Radeon(TM) RX Vega 10 Graphics ATI Technologies Inc.|4.5.0 Core Profile Context 22.10.1.221003|@JaedenREE\n\nWorks fine on:\nOperating system: Windows-10-10.0.22000-SP0 (Windows 11)\n|Graphics card:|Driver:|User:\n|---|---|---\n|Radeon (TM) RX 480 Graphics|4.5.0 Core Profile Context 22.7.1.220725|@mano-wii\n\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\n|Graphics card:|Driver:|User:\n|---|---|---\n|Radeon (TM) RX 480 Graphics|4.5.0 Core Profile Context 22.8.2.220819| @Jeroen-Bakker \n---\nBroken: (3.2)\n\nnon of the tabs are visible. as u can see in the image its entirely black. I wont be able to use the program at all. Please do fix this.\n\nThe error exists as soon as i open blender program\n", "Workbench: Random object color disables transparency in solid view\nOperating system: Windows 10 64bit\nGraphics card: Nvidia RTX 2080ti\n\nBroken: 2.83.1 official\n\n\n\n\nWhen setting the color of the material in the viewport to be semitransparent (Alpha value = 0.1) it works if the color of the viewport objects is set to \"Material\" it works, while if the color is set to \"Random\" the object is not semitransparent anymore.\n\nBlend file to test:\n[bug.blend](bug.blend)", "GHOST:: m_windows not clearing list of fullscreen windows \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 8)\n\nI just wanted to warn you about a potential bug in GHOST when we close a fullscreen window. The problem is that I don't know how to reproduce it in blender official.\nThen this is just if someone is interested...\n\nWhen we close a fullscreen window, GHOST::m_windows list doesn't erase the fullscreen window. Then m_windows list size increases.\nWhen I erase the fullscreen window from m_windows list, it is fixing a crash with our fork of blender (upbge)\n\nI describe the steps to reproduce the bug here: 4fc32990010d5765ba1abd523d57b252be73a657\n\nThis needs to compile restart_hacks branch from upbge github: upbge\n\nThere's a link to the testfile in the commit in mentionned.\n\nJust in case:\n\n[ledi.blend](ledi.blend)\n\n", "Black Artifacts While Using Adaptive Subdivision\n{[F7718097](bug.png)}Operating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\n\nBroken: version: 2.80 (sub 75)\n\n\nBlack artifacts on edges of geometry while using adaptive subdivision. I was trying to duplicate my workflow from other 3d software. Extruding geometry from 2d curves creates extra edges on the model. And extra edges create weird shadows on displacement.\n\nImport curve from dxf file. Use extrude Object Data > Geometry. Fill mode: Both. Use subdivision and displacement.\n\n[1.blend](1.blend)\n", "Blender 3.5.0 Win11 RTX3090 Fatal Crash on activating Cycles\n@deadpin thanks for replying.\n\nDriver Version: 31.0.15.3161 (NVIDA 528.24) DCH Win1164 installed\n\nCycles now working without issue thank u.\n\n_Originally posted by @Jaymi-McManus in /blender/blender/issues/106953#issuecomment-923094_\n\n>>>>>\n\nUpdate: \n\n1. Closed the ticket too soon, after adding some simple color, specular, metallic, changes in BSDF and then navigating between layout and other tabs, fatal crash occurs again\n\n2. Updated NVIDIA drivers to 31.0.15.3161 (NVIDIA 531.61) DHC / Win11 64 the issue still persists\n\nUpdate logs attached.", "Broken textures and shading\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nBroken textures when starting up blender and loading object textures and shading issues\n\n[Blender Texture Bug.mp4](Blender_Texture_Bug.mp4)\n\nPossible causes:\n * Not loading the parent asset blend file before the asset in another scene (opening it first seems to fix the issue in my testing) \n * 4k textures (i've heavily used 4k textures in the asset)\n * Viewport Texture size limit setting (Changed it to 2k)\n\n\n[untitled.blend](untitled.blend)\n", "UI: Image/UV Editor\nThe UI of the Image and UV Editor can be improved.\n\n* Move smooth edges option to user pref\n* Move overlays to an overlay popover\n\n\n\n\n* Move display settings to a popover\n* Change the Pixel Coordinates toggle into an enum to choose between Pixels or Normalized\n\n\n* Slightly re-arrange the header:\n\n* Move th UV Vertex panel away from the Image Sidebar category and into Item, and include Coordinates option here too:\n\n", "Textures messed up when rendering with Cycles HIP on AMD Radeon RX 7900 XTX\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (I'm actually using Windows 11 22H2 22621.1265 by winver)\nGraphics card: AMD Radeon RX 7900 XTX ATI Technologies Inc. 4.5.0 Core Profile Context 23.2.2.230217\nCPU: AMD Ryzen 9 7950X\n\nBroken: version: 3.4.1\nWorked: None. I've tried *3.3* (GPU rendering is not working, blender said like a HIP binary is missing, sorry I forgot the details), *3.4.1* (GPU rendering is working, but has this issue) and today's *3.5.0 beta v35.83f28793c0b3* (same as 3.4.1)\n\nWith Cycles HIP, when rendering a basic scene (any mesh, simple Principled material with 1 albedo and 1 normal map) on an AMD Radeon RX 7900 XTX, the rendered result is totally wrong: either 1) the mesh appears that it's wrongly colored by the normal map, the albedo is missing, or 2) has no normal maps, only base color is showed.\n\nHere's a scene I made, rendered with CPU (same result on a RTX 2060 Super GPU):\n\n\n\nHere's one possible GPU rendered result (missing albedo, case 1 above):\n\n\n\nHere's another possible result (missing normal map, case 2 above):\n\n\n\nBoth of the 2 cases above are possible, and may change to the other each time you start rendering.\n\nThis issue also happens when environment texture (HDRI) is used. Simply put: it seems to me that only one \"randomly chosen\" texture can be handled at a time, and all other textures in the scene are replaced by that.\n\nTurning off Smart Access Memory does not help.\n\nOn a computer with RX 7900 XTX, and with blender Cycles Render Devices > 7900XTX ticked:\n\n1. Open [project.blend](attachment)\n2. Press F12 to render the scene\n\n---\n\nWith regards,\nOasin\n\n", "System UI Freeze and blender UI blinks\nOperating system: Linux-6.4.12-zen1-1-zen-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) HD Graphics 630 (KBL GT2) Intel 4.6 (Core Profile) Mesa 23.1.6-arch1.4\n\nBroken: version: 3.6.2\n\nblender often freezes (with the entire UI of the System), sometimes blender comes back to control, but, there are times when doesn't, the blender UI blinks to come entirely black and unresponsive.\n\nThis happens when I was using a graphic tablet to sculpt something.\nJust opened blender and started to sculpt, eventually the situation occur.\n\n", "\"Reset to Default Value\" sets alpha incorrectly in [Material Properties > Viewport Display > Color]\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.5.0\n\nRight-clicking \"Reset to Default Value\" on [Material Properties > Viewport Display > Color] sets both the color's \"value\" and \"alpha\" bars to 0.8, when the alpha one specifically should reset to 1. Alpha resets incorrectly.\n\nRight-click \"Reset to Default Value\" on [Material Properties > Viewport Display > Color] on any material.\n\n", "Texture painting: Brush and fill miss some pixels.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.4 Release Candidate\n\nFinally I can reproduce this bug each time (and it annoys me every time I work with characters).\nTere is file with example: [fill testblend.blend](fill_testblend.blend)\nTry to fill selection \nOperation will leave randomly scattered pixels.\n\nYou can overpaint some of them, but another few pixels you can`t overpaint or you can only from specific camera angle.\n\nDemos:\n[2021-08-22_03-27-01.mp4](2021-08-22_03-27-01.mp4)\n[2021-08-22_03-22-39.mp4](2021-08-22_03-22-39.mp4)\n\nMake lowpoly.\nUnwrap to few islands.\nAdd Multiresolution (4-5 levels)\nAdd black texture (4k)\nSelect some islands in edit mode\nGo to texture paint mode, enable paint mask\nFill with white\nInspect result, you will find missed pixels\n\n\nFrom #95663: this is also true for orthographic view (if zoomed in far enough):\n- brushes wont paint pixels at all\n- fill tool will leave black pixels\n\n- Open .blend file\n- Use fill tool on object in 3DView (will leave black pixels) or\n- Use paint brush (wont paint pixels at all)\n\n\n\nTest File:\n[#95663.blend](T95663.blend)", "Black render artifact with CPU+GPU rendering in viewport\nWindows 7 Pro\nNvidia Quadro P6000\nIntel Xeon E5-2690 v4\n\nBroken: daily builds 2.79 since at least 25.10.2017.\nWorked: -\n\nIf I enable combined CPU+GPU rendering, a black rectangle shows up on one of my objects. It shows up in viewport rendering, and also in the final render. This seems to be independent of the material used. I have provided a stripped down version of the scene where it is still visible. This time only in the viewport, the final render works for this simplified scene. \n\nThe artifact seems to be \"locked in space\", I can move or rotate the object away, so that it disappears. In some rotation angles it is not a black rectangle, but dense black lines. \nWhat is also interesting is that the surface of the object in not only black, but partly transparent. I have put a lamp and a cube inside the object in the demo scene, these should not be visible from outside, but they are.\n\n- Open file. In the render settings GPU compute should be turned on, and in the user preferences CUDA should have both the CPU and GPU selected.\n- Turn on viewport rendering. --> black box visible.\n- Then switch to CPU rendering. No more black box.\n\n[black_artifact_bug3.blend](black_artifact_bug3.blend)\n\n" ]

[ "Themes don't work on Windows\nOperating system: Windows-10\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies 19.12.1 26.20.13031.20012\n\nBroken: version: 2.83 (sub 2)\nWorked: (optional) sub1\n\nReset the theme or pick a different theme and it will show wrong colors\n\nSwitch to light theme\n\n\n\nOr reset the default theme\n" ]

[ "Random crashes with NVidia + GPU Subdivision (sometimes when activating X-Ray or Wireframe overlay)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\n| Graphics card: | Driver : | User:\n| --- | --- | ---\n| NVIDIA GeForce RTX 3090/PCIe/SSE2 | 4.5.0 NVIDIA 516.94 | @GabrielMoro\n| NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 | 4.5.0 NVIDIA 512.15 | @STYXtheMUTT\n| NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 | 4.5.0 NVIDIA 516.94 | @Jojolix\n|NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2|NVIDIA 516.59|@MassimilianoPuliero\n|NVIDIA GeForce RTX 3090|NVIDIA 516.94|@The5\n\nBroken: version: 3.2.2\n\nOn some seemingly random occasions, Blender crashes with the following stack:\n```lines=10\nStack trace:\nblender.exe :0x00007FF77C1458B0 BKE_subdiv_free\nblender.exe :0x00007FF77C147880 BKE_subsurf_modifier_subdiv_descriptor_ensure\nblender.exe :0x00007FF77BFFC3D0 <lambda_c000e58b9a8caf72c54e0e02a46effdb>::operator()\ntbb.dll :0x00007FFDBAF64FD0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF77BFFC6F0 BKE_mesh_wrapper_ensure_subdivision\nblender.exe :0x00007FF77CB38FA0 raycast_obj_fn\nblender.exe :0x00007FF77CB375E0 iter_snap_objects\nblender.exe :0x00007FF77CB3E530 transform_snap_context_project_view3d_mixed_impl\nblender.exe :0x00007FF77CB3F0E0 ED_transform_snap_object_project_view3d\nblender.exe :0x00007FF77CB5E7C0 applyFaceProject\nblender.exe :0x00007FF77CB5EE00 applySnappingIndividual\nblender.exe :0x00007FF77CB72F70 recalcData_objects\nblender.exe :0x00007FF77CB81010 applyTranslation\nblender.exe :0x00007FF77CB46BE0 transformApply\nblender.exe :0x00007FF77CB41920 transform_modal\nblender.exe :0x00007FF77C229D30 wm_macro_modal\nblender.exe :0x00007FF77C20F9E0 wm_handler_operator_call\nblender.exe :0x00007FF77C210BD0 wm_handlers_do_intern\nblender.exe :0x00007FF77C210000 wm_handlers_do\nblender.exe :0x00007FF77C216590 wm_event_do_handlers\nblender.exe :0x00007FF77C1FC380 WM_main\nblender.exe :0x00007FF77B2F12A0 main\nblender.exe :0x00007FF7814128B0 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDC7B67020 BaseThreadInitThunk\nntdll.dll :0x00007FFDC85A2680 RtlUserThreadStart\n```\n```lines=10\nStack trace:\nblender.exe :0x00007FF7A50C5B10 BKE_subdiv_update_from_mesh\nblender.exe :0x00007FF7A50C7880 BKE_subsurf_modifier_subdiv_descriptor_ensure\nblender.exe :0x00007FF7A52A1110 draw_subdiv_create_requested_buffers\nblender.exe :0x00007FF7A52A2080 DRW_create_subdivision\nblender.exe :0x00007FF7A52D1870 DRW_mesh_batch_cache_create_requested\nblender.exe :0x00007FF7A52C6000 drw_batch_cache_generate_requested\nblender.exe :0x00007FF7A529F1A0 drw_engines_cache_populate\nblender.exe :0x00007FF7A529B8C0 DRW_draw_render_loop_ex\nblender.exe :0x00007FF7A529C9B0 DRW_draw_view\nblender.exe :0x00007FF7A5D3FA00 view3d_main_region_draw\nblender.exe :0x00007FF7A5551070 ED_region_do_draw\nblender.exe :0x00007FF7A51A3700 wm_draw_window_offscreen\nblender.exe :0x00007FF7A51A3560 wm_draw_window\nblender.exe :0x00007FF7A51A2FB0 wm_draw_update\nblender.exe :0x00007FF7A517C380 WM_main\nblender.exe :0x00007FF7A42712A0 main\nblender.exe :0x00007FF7AA3928B0 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFD1C4A54D0 BaseThreadInitThunk\nntdll.dll :0x00007FFD1D524830 RtlUserThreadStart\n```\n\nOccasions observed:\n- try to snap objects on faces (the object that shall be snapped to is usually a complex mesh with modifiers like subdivisions, mirror, solidify, bevel and booleans)\n- toggle the shading mode between shaded and wireframe or between X-Ray and Wireframe Overlay.\n[intro.crash.txt](intro.crash.txt)\n\n\n- open attached file\n- disable and enable X-Ray multiple times\nIt happens specially when working fast.\n\n[BLENDER_Youre_Alive_v67.blend](BLENDER_Youre_Alive_v67.blend)\n\n", "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "Fractured object crashes Render\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.10.12\n\nBroken: version: 3.4.1\n\nRendering image crashes Blender\n\nThe attached file is the output of a fractured cube using RBDLabs, nothing else. It's a series of 965 simple static meshes. When displaying rendered shading in viewport, all is well. When doing Render > Render Image, then Blender crashes. Happens on my Mac M1 and Mac Intel, on Blender 3.3.4, 3.4.1, 3.5 and 3.6 alpha. If I delete the 115 last cells or the 134 first ones, then the render will properly happen. Thanks !\n\n", "Texture Paint - bad behaving operator \"Save All Images\"\nGo to Texture Paint Mode with some Textures loaded. In T-Panel go to the Slots Tab. There you will find a Button labeled \"Save All Images\". However, do not push this Button !\nThis Button overwrites all involved/edited Textures in the Texture Paint Slots at once and instantly, without further inquiry, to the directory of the origins.\n\nIt's not a bug, it's working pretty well !\n\n \n", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n", "Cycles GPU CUDA rendering high number of points seems broken in LTS (main is fine, request for backport)\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.3.3\nWorked: latest 3.5 alpha\n\nRendering point \"clouds\" with Cycles - CUDA seems to make some chunks of points disapear randomly\nThis looks like this has been fixed in 3.5, but i didn't find when. Can this be fix in LTS ?\n\nDelete the default cube and add a plane\nAdd a Geonode Modifier on that plane\nDistribute Points on Faces > Density : 250'000\nSet Point Radius > 0.0025 (for convenience)\n \nSwitch to Cycles, GPU\nSwitch the render device to CUDA\n\nResults with :\n\n|  CPU |  CUDA |  OPTIX\n| -- | -- | -- |\n\n\n\nBug is visible in both viewport shading and Render.\n\n", "Randomize Transform + Affect Only Origins, not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\n\nRandomize Transform not working as expected with Affect Only = origin. Whole object is transformed rather than just origin.\n\nin the 3d view port go Options > Affect Only and tick Origins\nselect default cube\nTransform the cube using Object>Transform>Randomize Transform\n\nCube moves/rotates/scales when I'd expect only the origin to be affected\n\n", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "Affects only origins does not work for Point Cloud, Curves, Text objects\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: n/a\n\nAffects only origins does not work for Point Cloud, (new hair) Curves and Text objects.\n\n- Add Point Cloud (experimental), Curves or Text object\n- Set Affect Only: Origins\n- Try to move\n\n[AffectOnlyOrigin.mp4](AffectOnlyOrigin.mp4)", "Multiresolution - Crash when Linear Subdivision level is above 1\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.91.0\nWorked: Never? (2.90 and 2.92 dailies seem to crash on this one as well)\nWhen using multiresolution modifier on this part of my model and using linear subdivision level above 1, Blender crashes.\nThis does not happen with other subdivision methods, as shown in video.\nI've also tried to make this mesh manifold, but Blender crashed either way.\n\n\n1. Open attached Blend file\n2. Add multiresolution modifier to a mesh\n3. Press on \"linear\" button twice\n\n[Crash_SampleFile.blend](Crash_SampleFile.blend)\n\n[MultiresCrash0001-2375.mp4](MultiresCrash0001-2375.mp4)\n\n", "Sculpt mode: annotation and unhide conflicts with Multiresolution modifier\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\n**Broken: version:**\n2.93.0 Alpha.\n3.0.0 Alpha\n\nUse of annotation tool unhides the hidden face\n\n**Steps to Reproduce the error**\n- Open .blend file\n- Hide the faces with Box Hide tool\n- Erase the word \"Erase\" with annotation tool (hidden part will appear)\n- Repeat step 2.\n- Draw a line with annotation tool. (Hidden part will reappear)\n\nTest File:\n[#87821.blend](T87821.blend)\n[Blender [C__Users_Pratik_Downloads_T87821.blend] 2021-07-12 09-55-06.mp4](Blender__C__Users_Pratik_Downloads_T87821.blend__2021-07-12_09-55-06.mp4)\n", "Regression: Crash on deleting shape key from Blender File view.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0, 3.2\nWorked: 3.1\n\nCaused by a71a513def202b119328035dbd68e86c2c47f7ac\n\nOutliner on Blender File when delete cause crash guide.\n\n- Open attached file\n- Add shape key\n- Switch outliner to Blender file display mode\n- Expand Shape key\n- select `key` then delete it from context menu\n\nr2jrCca\n\nYoutube:\nOlegeJrBbmE\n\nMy Dropbox file:\nLola%20Bunny.zip?dl=0\n\n- - -\nFirst create new ticket I unable to paste picture this here.\nI did drag there 250MB and (Remove) cause appear <html><head></head><body></body><html> please fix without <html> k5RFuuy\n\n", "Knife Tool produces bad geometry in certain cases (disconnected edges/vertices, overlapping faces)\nif i use tools knife i see this bug.\n\n\n\n", "Access violation when running multiple quick liquid bakes (Python API)\nOperating system: Windows 10\n\nBroken: 3.3 alpha, 3.3, 3.4 alpha, 3.4\nWorked: Not any recent releases\n\nSeems related to T98427 , but the fix for that issue did not fix this.\nAccess violation when running multiple quick liquid bakes\n\n```lines=18\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF9DE2B9224\nException Module : python310.dll\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x0000000000000008\n\n\nStack trace:\npython310.dll :0x00007FF9DE2B9220 PyDict_GetItem_KnownHash\npython310.dll :0x00007FF9DE2CF200 PyFrame_GetBack\npython310.dll :0x00007FF9DE430410 PyRun_FileExFlags\npython310.dll :0x00007FF9DE430410 PyRun_FileExFlags\npython310.dll :0x00007FF9DE430270 PyRun_StringFlags\nblender.exe :0x00007FF64D0F4E60 MANTA::runPythonString\nblender.exe :0x00007FF64D0DAF70 MANTA::~MANTA\nblender.exe :0x00007FF64D0DB340 MANTA::`vector deleting destructor'\nblender.exe :0x00007FF6484EB4D0 BKE_fluid_modifier_freeDomain\nblender.exe :0x00007FF6484EB4A0 BKE_fluid_modifier_free\nblender.exe :0x00007FF648274A00 BKE_modifier_free_ex\nblender.exe :0x00007FF648488760 BKE_object_free_modifiers\nblender.exe :0x00007FF6484834A0 object_free_data\nblender.exe :0x00007FF6487EB890 blender::deg::deg_free_copy_on_write_datablock\nblender.exe :0x00007FF6487ECA40 blender::deg::IDNode::destroy\nblender.exe :0x00007FF6487E1F70 blender::deg::Depsgraph::clear_id_nodes\nblender.exe :0x00007FF6487E21E0 DEG_graph_free\nblender.exe :0x00007FF64D64FA80 BLI_ghash_free\nblender.exe :0x00007FF648450510 scene_free_data\nblender.exe :0x00007FF64846F120 BKE_id_free_ex\nblender.exe :0x00007FF64826E980 BKE_main_free\nblender.exe :0x00007FF6482628F0 BKE_blender_free\nblender.exe :0x00007FF6486F1AB0 WM_exit_ex\nblender.exe :0x00007FF6486F1A60 WM_exit\nblender.exe :0x00007FF6477F1260 main\nblender.exe :0x00007FF64D8788C0 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThreads:\nThread : 00004eb4\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000051dc\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004114\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004ab8\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000033dc\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00005b3c\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000044b0\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000033f0\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000031f8\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004aa4\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000049b8\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00005340\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00002654\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004c64\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000024a4\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00005664\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000048c4\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00005b4c\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004eb0\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 0000446c\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF647680000 3.3.0.0 blender.exe C:\\Users\\ecl25031\\blender-3.3.0-alpha+master.4c3b984b3daa-windows.amd64-release\\blender.pdb \n0x00007FFA49BF0000 10.0.19041.1741 ntdll.dll \n0x00007FFA48380000 10.0.19041.1741 KERNEL32.DLL \n0x00007FFA47810000 10.0.19041.1741 KERNELBASE.dll \n0x00007FFA48E00000 10.0.19041.546 WS2_32.dll \n0x00007FFA499D0000 10.0.19041.1706 RPCRT4.dll \n0x00007FFA47C50000 10.0.19041.1503 USER32.dll \n0x00007FFA47B10000 10.0.19041.1766 win32u.dll \n0x00007FFA373B0000 tbb.dll \n0x00007FFA48790000 10.0.19041.1620 GDI32.dll \n0x00007FFA2BF10000 tbbmalloc.dll \n0x00007FFA47B40000 10.0.19041.1706 gdi32full.dll \n0x00007FFA47310000 10.0.19041.789 msvcp_win.dll \n0x00007FFA473B0000 10.0.19041.789 ucrtbase.dll \n0x00007FFA48EA0000 10.0.19041.1682 ADVAPI32.dll \n0x00007FFA48440000 7.0.19041.546 msvcrt.dll \n0x00007FFA486F0000 10.0.19041.1586 sechost.dll \n0x00007FFA49040000 10.0.19041.1741 SHELL32.dll \n0x00007FFA48F50000 10.0.19041.1706 SHLWAPI.dll \n0x00007FFA2FB80000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFA477C0000 10.0.19041.1620 CFGMGR32.dll \n0x00007FFA15BF0000 14.29.30139.0 MSVCP140.dll \n0x00007FFA43A40000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFA47AE0000 10.0.19041.1023 bcrypt.dll \n0x00007FFA485C0000 10.0.19041.1202 ole32.dll \n0x00007FFA35C50000 10.0.19041.867 dbghelp.dll \n0x00007FFA48A40000 10.0.19041.1741 combase.dll \n0x00007FFA49870000 10.0.19041.546 PSAPI.DLL \n0x00007FFA49B00000 10.0.19041.1741 shcore.dll \n0x00007FFA484E0000 10.0.19041.546 IMM32.dll \n0x00007FFA03B30000 10.0.19041.1741 OPENGL32.dll \n0x00007FF9D3660000 9.0.0.0 openvdb.dll \n0x00007FF9D19D0000 59.18.100.0 avcodec-59.dll \n0x00007FF9F78D0000 59.16.100.0 avformat-59.dll \n0x00007FFA2D720000 59.4.100.0 avdevice-59.dll \n0x00007FF9F8750000 57.17.100.0 avutil-57.dll \n0x00007FFA48970000 10.0.19041.985 OLEAUT32.dll \n0x00007FF9FBCC0000 1.21.1.0 OpenAL32.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFA0FA30000 6.4.100.0 swscale-6.dll \n0x00007FF9F7770000 2.0.20.0 SDL2.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFA41050000 libgmpxx.dll \n0x00007FFA47F10000 10.0.19041.1741 SETUPAPI.dll \n0x00007FFA40FF0000 tbbmalloc_proxy.dll \n0x00007FF9DE1A0000 3.10.2150.1013 python310.dll \n0x00007FFA30660000 6.10.19041.1110 COMCTL32.dll \n0x00007FFA2AB80000 10.0.19041.1 AVIFIL32.dll \n0x00007FFA415D0000 10.0.19041.546 VERSION.dll \n0x00007FFA44B10000 10.0.19041.746 dwmapi.dll \n0x00007FFA2A530000 10.0.19041.1741 GLU32.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFA29450000 4.3.100.0 swresample-4.dll \n0x00007FFA3D230000 10.0.19041.546 Secur32.dll \n0x00007FFA2EAF0000 10.0.19041.1 AVICAP32.dll \n0x00007FFA39CA0000 10.0.19041.546 WINMM.dll \n0x00007FFA28820000 10.0.19041.1 MSACM32.dll \n0x00007FFA291F0000 10.0.19041.1 MSVFW32.dll \n0x00007FFA37020000 10.0.19041.1 winmmbase.dll \n0x00007FFA47200000 10.0.19041.1586 SSPICLI.DLL \n0x00007FFA45AD0000 10.0.19041.546 kernel.appcore.dll \n0x00007FFA452E0000 10.0.19041.1741 windows.storage.dll \n0x00007FFA46D70000 10.0.19041.1682 Wldp.dll \n0x00007FFA47250000 10.0.19041.844 profapi.dll \n0x00007FFA47610000 10.0.19041.1415 bcryptPrimitives.dll \n0x00007FFA48510000 2001.12.10941.16384 clbcatq.dll \n0x00007FFA3FB50000 10.0.19041.1503 MMDevApi.dll \n0x00007FFA470C0000 10.0.19041.1620 DEVOBJ.dll \n0x00007FFA3FC00000 10.0.19041.1741 AUDIOSES.DLL \n0x00007FFA468E0000 10.0.19041.546 powrprof.dll \n0x00007FFA46750000 UMPDC.dll \n0x00007FFA44880000 10.0.19041.1620 uxtheme.dll \n0x00007FFA2D140000 10.0.19041.1566 MPR.dll \n0x00007FFA415E0000 10.0.19041.546 drprov.dll \n0x00007FFA45F70000 10.0.19041.546 WINSTA.dll \n0x00007FFA2ED10000 10.0.19041.1566 ntlanman.dll \n0x00007FFA2EB50000 10.0.19041.546 davclnt.dll \n0x00007FFA22F70000 10.0.19041.546 DAVHLPR.dll \n0x00007FFA46500000 10.0.19041.1645 wkscli.dll \n0x00007FFA27030000 10.0.19041.546 cscapi.dll \n0x00007FFA467B0000 10.0.19041.546 netutils.dll \n0x00007FFA46CC0000 10.0.19041.546 CRYPTSP.dll \n0x00007FFA462D0000 10.0.19041.1052 rsaenh.dll \n0x00007FFA46CE0000 10.0.19041.546 CRYPTBASE.dll \n0x000002627AAF0000 3.10.2150.1013 python3.DLL \n0x00007FFA2CA10000 3.10.2150.1013 _bz2.pyd \n0x00007FFA28ED0000 3.10.2150.1013 _lzma.pyd \n0x00007FFA2C980000 3.10.2150.1013 _socket.pyd \n0x00007FFA46770000 10.0.19041.546 IPHLPAPI.DLL \n0x00007FFA40E90000 3.10.2150.1013 select.pyd \n\n# Python backtrace\n\n```\n\nPut this ins a file called test.py\n```\n\nimport bpy\n\nCUBE = bpy.data.objects[\"Cube\"]\nCUBE.select_set(True)\nbpy.ops.object.quick_liquid()\nbpy.ops.fluid.bake_all()\n\nbpy.ops.object.select_all(action='DESELECT') \nmesh = bpy.data.meshes.new('Basic_Cube')\nCUBE2 = bpy.data.objects.new(\"Cube2\", mesh)\nCUBE2 = bpy.data.objects[\"Cube2\"]\nbpy.context.scene.collection.objects.link(CUBE2)\nCUBE2.select_set(True) \nbpy.ops.object.quick_liquid()\nbpy.ops.fluid.bake_all()\n```\n\nthen, in terminal, run:\n\n```\nblender -b --python test.py \n```", "Memory Leak: Render Animation Sequence\n**System Information** Mac Studio Max, 64 GB Ram\nOperating system: Mac OS Ventura 13.3.1\nGraphics card: Metal 32 core GPU\n\nBroken: 3.5.1.\nWorked: N/A\n\nWhen attempting to render out 100 frame sequence to Tiffs... after 25 to 30 renders @2K using Cycles GPU only (Metal) the Ram usage is through the roof and Blender crashes. It appears that it doesn't flush the RAM between each render... by frame 25 Blender is using all the system RAM and has a swap file of over 100GB. The scene contains a single simple character sculpt with 4 fur curve nodes applied. Average render time when applied to single frame at .1 sampling is about 25 seconds.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n" ]

[ "Blender crashing in Edit mode.\nOperating system: Linux-5.12.15-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.31\n\nBroken: version: 3.0.0 Alpha\nCaused by 4ed029fc02\n\nBlender crashes in Edit mode.\n\nIts crashing in default scene. \nSelect default cube.\nGo to Edit mode.\nDelete Cube faces one by one.\nIt will crash randomly when deleting faces.\n\nAlso it will crash on Select Linked Flat Faces when increasing sharpness.\n\n[blender.crash_delete.txt](blender.crash_delete.txt)" ]

[ "Multiresolution displacement baking do not work properly\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Beta\n\nOriginal on the left produces map, thad displace surface like on the right.\nI suppose, there is wrong gamut/ color conversion or baking ray shoots from Hipoly to lowpoly instead measuring height difference from lowpoly to hipoly. Displacement baking is not equal to normal baking!\n\n{[F10039179](изображение.png) size=full}\n\n[mr bake.blend](mr_bake.blend)\n\n[2021-04-26_15-44-07.mp4](2021-04-26_15-44-07.mp4)", "Cycles render artifacts relating scene scale\nOperating system: Windows 10\nGraphics card: tested multiple graphics cards with same issue\n\nBroken: 2.83.6 (file originally made in 2.79 and had the same issue)\n\nThere exists in the blend file data only two objects - the camera and a simple plane. Yet when rendering, the result does not match the viewport and there seems to be another ghost object appearing in the scene.\n\nBased on the following startup file: [strange-error.blend](strange-error.blend)\n\n1. Switch to rendered view in the viewport. This is how things should look.\n2. Now render the current frame at frame 97. Notice the strange ghosting effect in the center of the frame.", "Low unit scale values show wrong Values and Units in sliders\nOperating system: Linux-5.8.0-2-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: not in 2.80 or 2.83\n\nWhen the unit scale is too low (< 0.0001 e.g. 0.00009), the values in all sliders will jump up to the value they would have with a unitscale of 1.0. This causes problems with the clipping planes of the viewport camera (didn't do this in 2.80). This seems to be independend of the unit system (metric/imperial).\n\nIf this is a known limitation then the shown precision of the unit scale slider should reflect that. Also a fix for the clipping plane issue is needed as that did work in 2.80.\n\nBased on default startup.\n1. In Scene Settings: enable seperate units\n2. set unitscale of 0.00009 or less (metric r imperial)\n3. observe what the dimensions sliders tell you about the dimension of the default cube.\n4. observe the buggy floor grid in the viewport probably due to the same bug in the clipping sliders (wasn't there in 2.80)\n", "Realtime compositor: Texture node output textures with artifacts\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nTexture node support was introduced in 151a53110c\n\nIn realtime compositor, Texture node outputs textures with artifacts.\n\n\n\nIt happens with most procedural textures I tested. This does not happen when a custom image is used, or when Blend texture is connected from the Value output (instead of the Color output) of the node. (With other textures it happens with both outputs.)\n\nThis does not happen when running Blender with a single thread (`blender -t 1`)\n\nFile for quick test: [TextureNodeTest.blend](attachment)\n\n", "Textures mapped on UVs with very high location values appear emissive when rendering on CPU\nTextures mapped on UVs that have vertices with very high location values appear emissive or black with CPU rendering. The UV vertex location values are around the range -3960966. \n\n### Original Report\n\nOperating system: macOS Monterey 12.4\nGraphics card: Apple M1 Max\n\nBroken: In every version I can find but for example in 3.2.1 2022-07-06 and 2.80 2019-07-29 as well as the nightly alpha 3.3.0 2022-07-17\nWorked: Cannot find a version in which it works.\n[system-info.txt](system-info.txt)\n\n**Background**\n\nI'm generating images in python using a script and I load objects from a dataset called SceneNet. Some of these objects have poor UV mapping, which is not a big deal, but it's causing rendering artifacts which are a problem.\n\n**The Bug**\n\nWhen a surface has incorrect UV mapping and has a stretched out texture, it leads to the surface becoming extremely bright. It does not *emit* light, the issue only occurs when there is a light source, emissive surface, or world background in the scene. The surfaces with stretched textures seem to multiply the reflected light by a high factor.\n\n**In the viewport** the issue only occurs when rendering on CPU. When rendering on GPU, the texture looks stretched out but with the correct color and not bright.\nExample 1:\nGPU ONLY  CPU \nExample 2:\nGPU ONLY  CPU \nExample 3, the same scene but with UV mapping fixed for part of the wall:\nCPU \nExample 4, blender 3.3.0 2022-07-17:\nGPU  CPU  Replaced problem faces with 100% white diffuse material \n\n**When rendering to file**, I have seen two cases:\n - The image looks like in the viewport while rendering, but when finishing the render the image becomes black.\n - When rendering with mixed CPU+GPU in Blender 3.1.0, the upper part of the image has the lighting issue from the CPU, and the rest of the image looks fine. \n\n**Desired behavior:**\nThe result from pure GPU rendering is the desired behavior.\n\nOpen attached .blend file, change viewport to render, switch between GPU and CPU rendering to see the difference. Try render to file using CPU/GPU/Mixed.\n[bug-textures.blend](bug-textures.blend)", "2.83lts Regression: Viewport render image ignores colormanagement, and appears to be hardcoded to use sRGB.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBisect points to 190fd795a9\nBroken: version: 2.83.0\nWorked: 2.82a\n\n`Viewport Render Image` ignores color management. The image produced is clamped to 1.0 according to the color sampler. It appears to be hard coded to sRGB.\n\nCreate a Scene that has scene linear color values above 1.0. Render with Filmic. Then do `viewport render image` and see how it produces an image with blown out highlights.\n\n2.82a:\n\n\n2.83:\n\n\n\n[test.blend](test.blend)\n\n", " Greasepencil Hue/Saturation modifier\nOperating system:windows 10\nGraphics card:GTX 1060\n\nBroken:2.93beta\n\nHue/Saturation modifier can not take effect on fill-gradient", "Baked Normal Map Is Not Equal To The Original Normal Map.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.Q4.221025\n\nBroken: version: 2.93.2\n\nThe problem that after I bake the normal it appears different than the original\n,Is this a bug ? , and why it appears different .\n\n1. Open blender\n2. Go to the shading window\n3. Select The cube \n4. Add normal map image connect it to the normal map after you add it , Then to the BSDF node \n5. create image to bake to it and select it \n6. bake the normal and see the result\n\n", "Normal map node worked is not correct\nOperating system: win10 x64\nGraphics card: gtx 1650\n\nBroken: 3.5.0, 1be25cfff18b, 2023-03-29\nBroken: 2.93\nWorked: 2.92\n\nCaused by 1c22b551d0\n\n\nI do not think that this is an error or a bug, rather it is not a refinement. \nIn some cases, the normal map node does not display them as you would like. \n\n\nI created a Hight poly model and bake it into a plane. Then I applied the resulting texture to the Low poly base mesh. It didn't display correctly there, only part of it smoothed out, but the other part showed sharp edges, very similar to the Fresnel effect\n\n", "USD Alab v2 import errors\nWhen loading the latest version of the Alab scene (v2), materials don't render correctly. I've narrowed the problem down to the following issues:\n\n - Some of the UV primvars in the Alab scene are of type `Float2Array` which is unusual. The Blender USD importer expects UV primvars to be of type `TexCoord` (e.g., `TexCoord2fArray`). Hence, some of the Alab UV maps are not getting imported, resulting in the wrong UVs getting applied in the Blender scene. The importer logic should be extended to import `Float2Array` primvars as texture coordinates as well.\n - The USD importer is attempting to read the `varname` input of the `UsdPrimvarReader_float2` shader as a `TfToken`, which conforms to the original `UsdPreviewSurface` specification. However, in the latest specification, `varname` is a string. This type mismatch when reading the input can result in an empty map name in the `UV Map` node in Blender and the wrong texture coordinates getting applies. \n - For materials that have an authored opacity value, the importer sets the material `Blend Mode` to `Alpha Blend`. In the Alab scene this causes artifacts due to object sorting issues. Setting the `Blend Mode` to `Alpha Hashed` provides improved results.\n\nTo reproduce the issue, the Alab USD can be downloaded here:\n\nalab/\n\nI created branch `tmp-usd-alab-v2-#100452` with work in progress on fixes so far.", "EEVEE AOV of full transparency is bad compared to Cycles\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4\n\nAOV of full transparent shader is barely noticeable. Cycles works fine.\n\n\n[eevee_aov_transparent.blend](eevee_aov_transparent.blend)\nFor default scene:\n\n - Set fully transparent shader (alpha clip or hashed) and add AOV layer for it\n - Render EEVEE -> AOV layer is bad\n\n", "the Unwrapping function doing wrong calculation\nOperating system: Windows 10\n\nBroken: 2.79, 2.80\n\nwrong size calculation uv shells\n[uv_unwrapping_wrong.blend](uv_unwrapping_wrong.blend)\n\n\nPS in other software\nmaya\n\n\n\nrizom uv\n", "Environment Importance Sampling gives too much noise\nWhen using importance sampling for environment maps in Cycles, the default/recommended resolution gives too noisy results when texture interpolation other than \"closest\" is selected.\n\nBlender version: 2.80\n\nTo reproduce:\n* Open attached file\n* Render in Cycles\n* Set the texture interpolation of the background map to \"linear\"\n* Render again\n\nActual result:\nSecond render has much more noise.\n\nExpected result:\nLittle to no difference in noise.\n\n\n\n\nAdditional testing:\n* Set texture interpolation to \"linear\"\n* On the background tab, set Settings/Surface/Sampling to Manual\n* On the background tab, set Settings/Surface/Resolution to 2048\n* Render again\n\nResult: Reduced noise again.\n\n[envmap.blend](envmap.blend)\n\n(HDRI image by Greg Zaal, HDRI Haven, CC0 license)", "Cycles misses intersections when objects are too close\nBroken: 2.79b\n\nWhen two objects are too close, Cycles can miss intersections.\nIn the attached file, there are two intersecting semitransparent planes (at the center).\nIf the color is green or pink it indicates that the ray only intersected one plane.\n\n- Open the attached .blend file and render.\nNote how the line where the planes intersect has a coloured border.\n[transparent_planes.blend](transparent_planes.blend)", "Bevel modifier UV problem with corners\nBroken: 2.79. 2.8*\n\n**Description**\nImportantly for games with Weighted Normals and Bevels workflow it would be very desirable for Corners of UV to scale and connect correctly so there are minimal distortions and UV disconnections. \n\n\nThis is how it opens in max post export:\n\n\nPlease also note that in 2.8 Bevel modifier completely distorts UVs in \"Vertex average\"(and possibly other) Normal Modes. Works as in 2.79 without any normal mode.\n\n\nPrepared debug scene (as requested by Howard): \n\n[debug_bevel_uv.blend](debug_bevel_uv.blend)\nAlso available here: debug_bevel_uv.blend\n\nThank you!\n" ]

[ "Cycles rendering, packed images render differently from unpacked\nWindows 64 bit, NVIDIA 750M Blender Version: 2.74.5 eb81153\nalso confirmed on:\nLinux 64-bit, CPU rendering, Blender Version: 2.74 b50c6e3\n\nBroken: Blender Version: 2.74.5 eb81153 , also Blender Version: 2.74 b50c6e3\n\n\nIf textures get packed into the .blend file, they get distorted in a way that the uv seams become visible (although the textures itself do not have seams). This is especially noticable with normal maps. \n\nI have provided an example .blend as well as example textures. Download the .blend and the textures seperately. First, make sure, you have \"automatically pack in .blend\" (under File > External Data) unchecked. In the shader, connect the normal map (texture node, set to Non-Color-Data) with the glossy shader, using a normal map node. Now save your file and render or use render preview. The texture won't show seams. \n\nThen check \"automatically pack into .blend\". Blender will tell you that it has packed one file - the normal map. Now render. You will see that the texture has gotten seams where the seams were set for unwrapping. You can use the linked color map to make this more visible. Please use an HDRI for lighting to view the error better.\n\nTest .blend file: [blender_bug_test.blend](blender_bug_test.blend)\nNormal map: \nColor map: " ]

[ "Eevee preview nodes with drivers performance drop Round 2\n[NodesPerformanceDropRound2.blend](NodesPerformanceDropRound2.blend) this is extend of previos task #71214\nSystem Information\nOperating system:Windows 10\nGraphics card: GeForce GTX 1060\n\nBlender Version\nBroken: Blender 2.81 Beta aff6446e064f and 2.82 Beta 092deb88b074\nWorked: 2.8\n\nShort description of error\nComplex shader with large amount of math nodes and with drivers slow down performance\nin 2.8 60 fps\nin 2.82 30 fps\n\nExact steps for others to reproduce the error\nCreate material with 30 node groups contains 30 math nodes, add driver to shader. Set viewport to material preview and watch performance droping", "Cycles: Bump node doesn't generate anything in certain conditions\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.3.0\nWorked: all versions from 2.79 to 3.4.0 alpha are affected, there is no working build\n\nI'm trying to generate a normal map using Bump node and color output of the env map as height map, it doesn't work on Cycles while it works on Eevee. Seems like the \"reflection\" output of Texture coordinate node is broken, but it works fine when I'm using another outputs though\n\nOpen the project, then click on viewport Rendered mode button - it'll start Cycles which for some reason can't generate bump map, then switch to Material preview mode - it'll start eevee which works as expected\n[bug_report.blend](bug_report.blend)\n\nEdit: typos and bad english grammar fixed, I believe", "Cycles does not respect the texture alpha mode\nOperating system: Gentoo Linux \nGraphics card: AMD 290x\n\nBroken:\n2.79b\n2.80 f15205b93f56e454b76d5a222fdb9a9665b99907 2018-01-02\n\nEevee respect the alpha mode in the texture settings, however cycles does not.\n\n[alpha_test_pack.blend](alpha_test_pack.blend)\n\n1. Load the attached .blend file\n2. Change the texture settings for the `Alpha:` setting for the image texture node (with use alpha on).\n3. Notice that in cycles the `Alpha:` setting has not effect, the texture alpha is always premultilied.", "Geometry-node object-info rotation&scale outputs values are False if scale is negative \nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0\n\nthe object info rotation & scale values are false if the scale of the sampled object is negative \nsee video, where i compare with simple drivers of the object transforms\n\n[dffdsdfdsfsfd.mp4](dffdsdfdsfsfd.mp4)\n[buggy transforms.blend](buggy_transforms.blend)\n\n", "Can't drag and drop node from asset library if the node doesn't have geometry input\nOperating system: Windows-10-10.0.25330-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Alpha\n\n\nSome nodes I created don't have geometry input since they just generate completely new geometry, so I hide the geometry input.\nHowever if I want to drag and drop the node from the asset library I get the following message, it's possible to add the node if it exists in the file and I pick it through the modifier panel.\n\n* Make a GN node that doesn't have \"geometry\" in the group inputs\n* Make it an asset\n* Drag and drop from the asset library\n* Observe the message\n\n", "Blender FBX won't export Mesh Geometry converted from Curve with geometry nodes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\n\nWhen creating meshes procedurally using geometry nodes modifier on a curve object, this object won't get exported by FBX exporter even if the result is a mesh, not a curve.\n\n1. Create a curve object\n2. Add geometry nodes modifier, create new GN node network \n3. Convert the curve to a mesh and add some topology (for example using curve fill)\n4. Export this object using FBX\nResult: The mesh is not exported\nExpected: The mesh is exported\n\n", "Outliner Floating window Drag & Drop to Geometry Nodes editor not working\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: I don't know if it ever worked\n\nDragging and dropping objects from the outliner to the geometry node editor is not working\n\nFloat outliner to be its own window\ndrag and drop an object from the node editor to the geometry nodes\ndoesn't work.\n\n", "node editor: Texture preview refresh with cursor selection\nOperating system: 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux\nGraphics card: RTX 2070\n\nBroken: Blender 2.93.0, Commit date: 2021-02-17 06:07, Hash 17dddc941714\n\nwhen selecting things in geonodes space the texture preview refresh anomaly.\n\n- Open blender default file.\n- Open the geometry nodes editor\n- Add a geometry node group\n- Open the texture tab ( property panel )\n- Add a texture for the current brush\n- Change to cloud texture\n- Try to select things with cursor select ( Key : C ) in the geometry nodes area.\n- It will refresh the texture preview\n\n[untitled.blend](untitled.blend)\n[Kazam_screencast_00003.mp4](Kazam_screencast_00003.mp4)", "Some areas do not use modified (by geometry nodes) curve\nOperating system: Windows 10 - Probably irrelevant.\n\nBroken: 3.0.0 (not checked earlier versions).\nWorked: (none)\n\nThe Curve modifier on mesh objects does NOT use the modified version of a curve\n\nSee attached blend file for easy example: [bug - curve with modifier.blend](bug_-_curve_with_modifier.blend)\nExample screenshot of that blender: \nThe thin line is the curve, which has geometry nodes modifying it.\nThe thick (square) line is the mesh, which targets the curve but doesn't use the modified version.\n\n - Add BezierCurve, with a few points.\n - BezierCurve: Add geometry nodes (or any other modifier, like wave or whatever) that changes the curve.\n - BezierCurve: (for visibility) add geometry.\n - Add Cube .1m \n - Cube: Add Array modifier and Curve modifier, targeting the BezierCurve\n\n**Expected result**: Mesh follows modified curve.\n**Actual result**: Mesh follows original (unmodified) curve.\n\nThe blender file shows this very easily, the modified curve is round, the mesh is in the \"old location\" that the curve would have without the modifier on the curve.\n\n\nYes, this is a duplicate of: 93702/ - Where apparently there is confusion on what the issue is. I could not find a way to un-archive a ticket.\n\n\n**Areas Affected**\n- Curve modifier\n- Spline IK", "Eevee Light Limitation testcase T91611 crashes on Win11 Intel Arc GPU \nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Intel(R) Arc(TM) A770 Graphics Intel 4.5.0 - Build 31.0.101.4090\n(note: also tested on driver .4032 latest stable, which also crashes)\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: 3.3.2, 3.4.1\n\n \n\nWhile tracking down another bug (direct lights not appearing in Eevee), I found that the test case for #91611 hard crashes blender.\n\nAnalyzing the code, the crash happens because the GPU module cannot create a 3D texture with dimensions `4096x4096x576`. The result is `nulltptr`\n```\nif (!success) {\n delete tex;\n return nullptr;\n}\n```\n\nbacktrace:\n\n```\n>\tblender.exe!blender::gpu::Texture::attachment_type(int slot) Line 257\tC++\n\n \tblender.exe!GPU_framebuffer_texture_attach_ex(GPUFrameBuffer * gpu_fb, GPUAttachment attachment, int slot) Line 316\tC++\n \tblender.exe!GPU_framebuffer_texture_layer_attach(GPUFrameBuffer * fb, GPUTexture * tex, int slot, int layer, int mip) Line 331\tC++\n \tblender.exe!EEVEE_shadows_draw_cubemap(EEVEE_ViewLayerData * sldata, EEVEE_Data * vedata, int cube_index) Line 203\tC\n \tblender.exe!EEVEE_shadows_draw(EEVEE_ViewLayerData * sldata, EEVEE_Data * vedata, DRWView * view) Line 316\tC\n \tblender.exe!eevee_draw_scene(void * vedata) Line 247\tC\n \tblender.exe!drw_engines_draw_scene() Line 1111\tC\n \tblender.exe!DRW_draw_render_loop_ex(Depsgraph * depsgraph, RenderEngineType * engine_type, ARegion * region, View3D * v3d, GPUViewport * viewport, const bContext * evil_C) Line 1767\tC\n \tblender.exe!DRW_draw_view(const bContext * C) Line 1637\tC\n \tblender.exe!view3d_draw_view(const bContext * C, ARegion * region) Line 1552\tC++\n \tblender.exe!view3d_main_region_draw(const bContext * C, ARegion * region) Line 1587\tC++\n \tblender.exe!ED_region_do_draw(bContext * C, ARegion * region) Line 551\tC\n \tblender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 960\tC\n \tblender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 1127\tC\n \tblender.exe!wm_draw_update(bContext * C) Line 1385\tC\n \tblender.exe!WM_main(bContext * C) Line 648\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 589\tC\n \t[External Code]\t\n\n```\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n- Download and open any of the test cases bellow\n- Click Render Preview in viewport\n\n[Light ViewportRender ERror.blend](Light_ViewportRender_ERror.blend)\n[lighttest2.blend](lighttest2.blend)", "Geometry Node: Input Color node: Custom color and value color is the same property\nOperating system: Linux-5.15.0-60-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.4.1\nWorked: Never.\n\n\nCustom color and value color is the same property. Impossible to set custom color to node, always edited value color.\n\n1. Create Geometry Node tree.\n2. Create `Input Color` node\n3. In `N` panel, `Node` page:\n a. Enable `Custom Color` button.\n b. Try to change custom color.", "Node Operators: Add Selection input node\n_No response_\n\n", "GeoNodes: Getting animated/driven Curve Radius doesn't work if curve has shape key\nOperating system: Linux-6.2.2-gentoo-x86_64-Intel-R-_Core-TM-_i9-9900K_CPU_@_3.60GHz-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\n\nBroken: version: 3.6.0 Alpha\nWorked: Likely never\n\nThis is a pretty specific set-up on the old Curves, so I'm not sure if it's something that needs to be fixed or if this datablock is getting replaced anyways, but I thought it would at least be good to be aware of.\n\nIf a curve has a shape key, the GeoNodes \"Radius\" node seems to fail to return the correct radius value.\n\nI don't know for sure if this is really a GeoNodes issue, though, because from my testing, the way the Radius value works with shape keys just seems pretty weird. It makes a fair amount of sense until the Radius value gets a driver. At that point, the shape key seems to take on whatever value the Radius had when leaving edit mode.\n\n- File: [radius_driver_not_working.blend](attachment)\n- Scale the bone; The curve point's radius is hooked up to be driven by the bone's scale, and the sphere is created by GeoNodes based on that curve point's radius. So, when you scale the bone, the sphere gets bigger.\n- Add 2 shape keys to the curve\n- Scale the bone again; Sphere doesn't scale any more.\n\nFor my use case, I don't actually need shape keys on my curve, so this won't be an issue for me at all, I just ran into it because I happened to have a temporary shape key on there and I thought I would report it.\n\n", "Geometry Nodes modifier input: Show More descriptive names in the dopesheet\nRight now animated geometry nodes modifier properties get an infamous label such as \"Input_2\". It should instead show the name that is shown in the UI, just like the other (non-geometry nodes) modifier properties.\n\n{[F13048799](image.png), size=full}\n\n[modifier.blend](modifier.blend)\n\nA proposed solution by @HooglyBoogly + @JulianEisel is to introduce \"labels\" to the UI data of ID Custom Properties.\n\n*This doesn't touch the Python API.*", "Eevee Incorrect rendering of the volume\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.0 Alpha\n\n\n\n[bug_volume_eevee.blend](bug_volume_eevee.blend)\n" ]

[ "Eevee does not detect changes of a color attribute\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 25.20.100.6471\n\nBroken: version: 2.93.0 Alpha\n\nEevee unlike `cycles` does not detect changes of a color attribute if they were made via geometry nodes modifier.\n\n[2021-02-08 15-24-23.mp4](2021-02-08_15-24-23.mp4)\n\n[test2.blend](test2.blend)\n\n1. Donwload the file\n2. Choose `eevee` render\n3. Change color value of the `Attribute fill` node (nothing happend)\n\n" ]

[ "View -> Lock Time to Other Windows does not maintain scale when CTRL+TAB between two animation editor modes.\nOperating system: Manjaro Linux\nGraphics card: nVidia\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nView -> Lock Time to Other Windows does not maintain scale when CTRL+TAB between two animation editor modes. \n\nExpand open the Timeline editor, now adjust the horizontal scale of the view (squeeze or expand), then Ctrl+TAB to swith to Graph Editor mode. Notice the scale does not stay in sych as it does when they are separate windows. ", "Non Uniform Scaling possible when Camera is parented\nOperating system: Win 10\nGraphics card: Geforce 2070\n\nBroken: 2.82-3.2\n\n\nIf you parent a Camera to an Object and scale the parent non uniformly, the Camera View gets scaled and distorted too.\n\n\nCreate an Empty, parent the Camera to an Empty, scale the Empty. The Camera View gets distorted.\n\n[blender_camera_scaling_bug.blend](blender_camera_scaling_bug.blend)", "Generated cordinates from instancer\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Alpha\n\nDocs says, that it should work, but do not give any example.\nGenerated from instancer gives -0.5 value on all instances and points.\nI expect to have correct vector field, the same as instancer have.\n\n{[F9500816](59614942.png) size = full}\n[from instancer.blend](from_instancer.blend)\n\n[2020-12-10_23-36-48.mp4](2020-12-10_23-36-48.mp4)", "Can't select camera from camera view by clicking on the border if the camera object is too small\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.119.03\n\nBroken: version: 2.93.1\n\nCan't select camera from camera view by clicking on the border if the camera object is too small.\nWatch the video\n[2021-06-27_15-35-32.mp4](2021-06-27_15-35-32.mp4)\n\nOpen the file and scale the camera back and forth trying to select it from the cam veiwport.\n[camera_select_bug.blend](camera_select_bug.blend)\n\n", "Remeshing object with subdivision modifier hangs Blender\nOperating system: macOS 10.14.6\nGraphics card:\n\nBroken: All versions of Blender but tested on Version 2.93.0 (2.93.0 2021-02-25) & Version 2.92.0 (2.92.0 2021-02-25)\nWorked: ?\n\nRemeshing object with subdivision modifier hangs Blender\n1 Add a subdivision modifier to the default cube, set it to 2 or more.\n2 Jump into Sculpt mode and remesh with default voxel settings, it should work fine.\n3 Undo the last remesh and now change the voxel size to 0.002 m and remesh again, it hangs.\n\n\nDo step 1 again, this time apply subdivision modifier and then try to remesh with voxel size of 0.002 m, it should work\n\n\n\n", "Add Object Tool, Resolve UI Issues & Polish\nThis task is to track the add-object tool.\n\n- - [x] Resolve behavior when axis aligned, see: #57210 (currently creates very large object). Done 1501c3adad\n- - [ ] Review design changes proposed by @DanielBystedt #57210#1010083", "Alembic import with animated normals causes incorrect shading\nOperating system: Linux-5.15.0-43-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.4.0 Alpha\n\nI noticed that the shading of a simulation imported as an Alembic from Houdini shows incorrect vertex (or face varying) normals:\n\n\n\nThe same frame of the animation transferred with OBJ looks correct:\n\n \n\nI re-imported the Alembic in Houdini and also in Fusion 9 (these were the only two apps with Alembic support I have access to here). Both look and render correct, too:\n\nHoudini\n\n\nFusion\n\n\nThe normals themselves aren't even animated but according to abcinfo they are marked as \"animated\":\n\n```\n/home/steffen/Downloads/explosion_small.abc, version: 10803 (2 timings)\n TimeSample[0] 1 samples: t0=0 (frame 0.0 @ 24fps)\n TimeSample[1] 2 samples: t0=1.36 (frame 32.6 @ 24fps)\n\nObjects:\n/alembic1 (Xform)\n Constant-Identity\n/alembic1/alembic1 (PolyMesh)\n Attribute Animation t0=1.36 (frame 32.6 @ 24fps)\n box fpreal64 .selfBounds[6] (animated[2]) t0=1.36 (frame 32.6 @ 24fps)\n int32 .face-counts\n int32 .face-indices\n point float32 P[3] (animated[2]) t0=1.36 (frame 32.6 @ 24fps)\n FaceVarying float32 N[3] (animated[2]) t0=1.36 (frame 32.6 @ 24fps)\n vector float32 v[3] (animated[2]) t0=1.36 (frame 32.6 @ 24fps)\n/alembic1/alembic1/glass_radialinside (FaceSet)\n/alembic1/alembic1/glass_concentricoutside (FaceSet)\n/alembic1/alembic1/glass_radialoutside (FaceSet)\n/alembic1/alembic1/glass_chips (FaceSet)\n/alembic1/alembic1/glass_chippinginside (FaceSet)\n/alembic1/alembic1/outside (FaceSet)\n/alembic1/alembic1/glass_concentricinside (FaceSet)\n/alembic1/alembic1/inside (FaceSet)\n/alembic1/alembic1/glass_chippingoutside (FaceSet)\n\n11 Objects displayed\n``` \n\n- Import the attached Alembic (boiled down to only two frames to keep the data size small)\n[explosion_small.abc](explosion_small.abc)\n- Look at the shading\n- Now import the OBJ coming from the same simulation\n[explosion_frame_34.obj](explosion_frame_34.obj)\n\n\n", "GPU subdivision: Wrong object's size when using subdivision surface modifier with GPU subdivision\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia Geforce GTX 660\n\nBroken: 3.1\nWorked: 3.0\n\nWhen GPU subdivision is activated, the object with subdivision surface doesn't show the correct size on the dimension section of the properties' sidebar.\n\nSelect the default cube.\nAdd Subdivision surface modifier\nOpen the properties' sidebar with N, the dimensions should be 1,68m (for X, Y and Z) but it shows 2,0m for all the axes. By deactivating the \"GPU subdivision\" the panel shows the correct dimensions.\n", "`bpy.context.space_data.overlay.grid_scale` returns inconsistent view3D grid scale in multi-view\nOperating system: win 10\nGraphics card: RTX 3090\n\nBroken: This was observed in 3.5 alpha but I don't think that is relevant \nWorked: N/A\n\n`bpy.context.space_data.overlay.grid_scale` does not apply to multi-view functionally, and any interaction with the 3D navigation sphere only effects the main window portion of multi-view.\n\nSee attached video for a demonstration of some of the odd behavior.\nSee attached blend to reproduce the error.\n\nEnter multi-grid view: **ctrl+alt+q** (mismatched transform grid) The main window is top right.\nClick any axis sphere in any 3D view that isn't the top right quadrant, only the main window transforms.\nYou will also notice that the main window also inherits the grid scale of the multi-view windows.\n\nPlaces to look maybe? [A](overlay_grid.cc#L86) [B](space_view3d)\n\n", "Incorrect parent tree when exporting and importing scene with multiple rigged objects\nArch GNU+Linux, Kernel 4.18.5\n\nBroken: 2.79.6, Git 19c65cd (branch master)\nWorked: None that I'm aware of\n\n\nIf you have a scene with multiple rigged objects, the armatures and meshes are incorrectly parented upon exporting then importing them. Rather than there being two armatures at the root of the scene with each one containing a single mesh, there will be (if you have two objects) one armature at the root, the other armature as a child of it, with both meshes attached to the inner-most armature.\n\nNote that this certainly seems to be a fault of the importer and not the exporter: I've manually reviewed the exported model and it appears fine. Additionally, upon attempting to import a Collada file generated by custom software I've got the exact same problem as importing the file generated by Blender.\n\n\nStart with an empty scene, and create a cube. Add a single bone. Make the cube a child of the bone, using the armature deform with automatic weights option (not using any weights prevents this problem from occurring).\n\nRepeat this a second time.\n\nExport the scene as a Collada file.\n\nOpen a new instance of Blender, and import the scene with Collada.\n\nThe objects will have incorrect parents, and this has consistently occurred each time I have tried it:\n\nHere are the screenshots of the scene, before exporting (matches attached blend file): \n\nAnd after export/import: \n\nSample Blender file before export: [expimptest.blend](expimptest.blend)", "Solidify Modifier wrong solidification normals in some cases\nOperating system: Windows 11\nGraphics card: ATX4000\n\nBroken: 3.5.0\n\nIn some corner cases, the Solidify modifier uses wrong solidification normals.\n\nWith the \"Faces linked only by one vertex.obj\" object, where some faces are sharing only one vertex and no edge, the solidification behaves as if ignoring that shared vertex.\n\nWith the \"Triangulated mesh wrong solidification.obj\" object the vertex in coordinates (-1, 1, -1) does not solidify properly, while the exact same mesh, but not triangulated (\"Triangulated mesh right solidification.obj\" object) solidifies right.\n\n", "USD Shape IO Support\nOn the most basic level, this feature would allow importing USD shapes (capsule, cone, cube, cylinder, sphere) as Blender meshes. More advanced implementations could include options for alternate, lightweight representations of shapes in the Blender scene, e.g., exploiting instancing, custom viewport rendering that does not require importing the mesh data, etc.\n\n@charlesfleche discussed the following suggestions re USD shape support on the `pipeline-assets-io-module` Blender chat channel on 22 Sep 2022.\n\n---\n\nOur main use case is to represent collision objects. For performance reasons we can feed simple collision objects to the physic component of the game engine. For example, rather that computing a collision with a complex character head that as many faces, you can define a simple sphere that is much faster to compute collision against.\n\nBut sometimes simple shapes are not enough: in this case we still want as fast as a collision computation as possible, and use a convex mesh to approximate the visual shape as much as possible. And when we really, really require high precision we'd use a mesh that can be complex and convex.\n\nWe also have the concept of collision Level Of Detail. The typical example is a fence:\n\n- you don't the player to walk through the fence, but for that purpose you can approximate the shape of the fence with a single parametric box\n- but you still want a bullet to go through the holes of the fence: for collision with ammunitions, you'd use a more detailed mesh\n\nBut not all DCC support parametric shapes, so for simplicity (and for now), we are still importing USD shapes as meshes in the DCCs, but on way back to USD we compute the bounding volumes of the requested shape. In practice, it looks like this:\n\n- In USD: `UsdGeomCube` MyObject_BOX with a size attribute + xform\n- In the DCC: we extract the dimension of the box from the scale component of the transform and generate a box mesh, with custom code ran at import time\n- DCC user is editing the box\n- In the DCC: the object is a _BOX, we compute the Box Bounding Volume and store the x, y, z dimensions as in the xform as scale\n- In USD: `UsdGeomCube` MyObject_BOX wih a size attribute + xform\n\nIt is not great because the users don't have the same representation in engine vs the DCC. In engine they'd handle Radius and Height parameters, in the DCC it's a bunch of vertices.\n\nSo the idea, for Blender, would be to leverage the geometry nodes to give the user parameters to play with (radius, height), even if the actual object in Blender is still a mesh.\n\n`Geometry Nodes` presets should be enough for now. After all, you can already generate those shapes in the `Geometry Nodes` already. What is important would be to have control, even if purely manual at import time, on how the Shape will be presented in Blender. For example, most users will want a Box to be defined with three parameters: `sizeX, sizeY, sizeZ`. However, depending of the physics engine you are dealing with, sometimes boxes are represented by two vectors: `bottom-left` and `top-right`. To match the Engine representation in the DCC, we'd need to be able to replace the default Geometry node by ours, where we'd expose the `bottom-left` / `top-right` vectors to the user.", "Remesh Voxel Size can be much to small by default (leading to crashes). 'Edit Voxel Size' operator can have wrong range\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\nProcessor: AMD Ryzen 7 3800x 8-Core Processor 3.90 GHz\n\nBroken: version: 2.90.0 Alpha\n(Also with Blender 2.83 BETA)\n\nSelecting the \"Remesh\" modifier, selected \"Voxel\", Voxel size below \"0.01m\" = PC Crash. Needed to restart the PC.\n\n1. Start Blender.\n2. Let the default Cube alive and add the \"Remesh\" modifier.\n3. Make the \"Voxel Size\" below \"0.01m\".\n4. Did it crashed?\n(Found out in my Blender Project, but I tested it then in a default Scene. Same thing happened.)\n\n(Why I set the Voxel Size below \"0.01m\"?\nIt happens accidentally, when I have it like \"0.42m\", but I hold my left click and slide it to the left, so I accidentally go below \"0.01m\".)\n\n{[F8619727](image.png), size = full}\n\nGood Luck!\n", "Regression: Blender 3.1 UI editor resize /border dragging performance\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\nWorked: 3.0.1\n\nCaused by {6738ecb64e8b6d0c1f5a79f1e63f468b4138de19}\n\nResizing UI editor panels in Blender 3.1 is significantly slower (framerate) and laggier than it was in 3.0. This is not related to the UV Editor performance regression as it happens even when there's no UV editor displayed in the given workspace. \n\nHere's a video of the issue, recorded at 60FPS and slowed down to 50% so the issue is more apparent: watch?v=a0wzLgkf6mk\n\n1. Open blender with a new empty file \n2. Drag the top of the Timeline Editor UI area around\nResult: The UI redraw framerate and input response (lag) are worse than in Blender 3.0\nExpected: The UI redraw framerate and input response (lag) are same or better than in Blender 3.0\n\n", "Consider using more explicit names instead of the generic 'Size' value for Empties.\nWhen creating an Empty, the pop-up window specifies the `Radius` for the Empty, presumably because the shape chosen could be a sphere, arrows, or any number of different types.\n\nHowever, when viewed in the Object Data Properties, the radius is displayed as a more generic `Size` value.\n\n\n\nThis leads to confusion, especially when comparing an Empty to a Cube. In the example below, the visual scale of these two items is identical, yet looking at their `Size` tells a different story.\n\n\n\nFor context, this came up as a point of confusion for a use case where I'm using non-scaled empties as a 'holder' for position/rotation/scale while applying a set of custom properties to be exported as .glb and used in threejs.\n\nMy suggestion would be to continue the use of `Radius` as the label in the Object Data Properties, instead of `Size` since that's what is actually meant by the value.\n\n" ]

[ "Blender units on exported mesh\nOperating system: windows 10\nGraphics card: Gtx 960\n\nblender 2.8 commit date: 2019-05-26 \n\nbad scale when exporting in different formats\n\n\nblender 2.8 now work on meter units from default, but Problem with scale objects on exported formats\n\ndefault cube on blender 2m\n\nblender cube 2m> .fbx >maya,max 200cm \nblender cube 2m> .dae >maya,max 200cm\n ###problem here###\nblender cube 2m> .abc >maya,max 2cm\nblender cube 2m> .obj >maya,max 2cm \n\n\n\n\n\n" ]

[ "Linked Mesh Editing Doesn't Work As Expected When Using Data Transfer Modifier\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.81 (sub 16)\n\nObject instances doesn't work as in blender 2.81\n\n\nIn blender 2.81, after entering the edit mode, all instances become active. You can see changes in real time.\nScreen below:\n\n\nIn Blender 2.82 it work ok till some time. I couldn't determine at what moment it breaks...\n\n\nChanges appears only after You enter to object mode.\n\n\n\nHere is blend file to test\n[instances_issue.blend](instances_issue.blend)\n\n\n", "Regression: GPU Subdivision: EEVEE doesn't refresh viewport correctly with Armature modifier\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3LTS, master\nWorked: 3.2.2\n\nGPU Subdivision doestn't refresh viewport correctly an object when Armature and Subdivision Surface Modifiers are used.\n\n1) Start Blender.\n2) Add Armature object\n3) Switch to \"Shading\" workspace.\n4) Select the Cube and add `armature modifier` then `Subdivision Surface Modifier`.\n5) Switch to Properties Editor to \"Modifier Properties\"\n6) Add armature in armature modifier's object property. \n7) Switch between object-edit mode\nIt works fine when \"GPU Subdivion option\" is turned OFF (Prefrences > Viewport > Subdivision > GPU Subdivision)\n\nI added \"BeforeGPUSubDBug.blend\". You can reproduce this issue by loading the blend file and doing step 7)\n", "\"RENDER_OT_render\" called with \"EXEC_DEFAULT\" freezes Blender with Eevee motion blur enabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0 Beta\n\nbpy.ops.render.render() called without 'INVOKE_DEFAULT' from the Python Console or script freezes Blender when Eevee motion blur is enabled.\nAnd the same issue is in the 2.91 Alpha version.\n\n----\n\n- Open Blender\n- Make sure context scene render engine is Eevee\n- Turn on motion blur\n- Open Python console\n- type in bpy.ops.render.render() and hit enter\n\n----\n\n*Edit* (added method that doesn't activate via Python).\n\n**Exact steps to reproduce the error without activating from Python.**\n- Open Blender\n- Make sure context scene render engine is Eevee\n- Turn on motion blur\n- Run this script in the text editor\n\n\n```\nimport bpy\ndef menu_func_import(self, context):\n layout = self.layout\n layout.operator_context = 'EXEC_DEFAULT'\n layout.operator(\"render.render\", text=\"Blocking Render\")\nbpy.types.TOPBAR_MT_render.append(menu_func_import)\n```\n\n- Run \"Render -> Blocking Render\" from the top-bar.", "Copying in edit-mode copies the entire object, not the selection\nthere is an issue occurs when a part of (mesh) is copyed in the edit mode \nwhat happens when copying one part of a (mesh) and pasting it\nyou suppose to get this part only pasted ,but instead you get the whole (mesh) pasted\n\nfor examble if you have a cube model with a single face selected in the edit mode \nif you copyed then pasted it the result is the whole cube modele is pasted rather than the single face \n \n \n\n", "Eevee volume ghosting on animation playback\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\n\nBroken: version: 2.83 (sub 13)\nWorked: not known VDB imports only in 2.83\n\nPlay back of imported VDB in eevee creates ghosting \n\nImport VDB\n>scale to 0.01 \n>edit frame range to match sequence ie 240 \n> add Sun \n> edit Volume Shadows \n> Edit Blackbody emission to 10 show fire from temperature \n>play sequence \n\n\n\n\n\n\n\n", "Retopology: Active Object Geometry gets Occluded by Semi-Transparent Reference Object in Edit Mode\nOperating system: Linux Ubuntu 16.04\nGraphics card: Nvidia GeForce MX130\n\nBroken: 2.83.0\nWorked: 2.82.a\n\nActive mesh is occluded by high poly or another reference mesh in Edit mode. This is: I want to edit mesh A. I need mesh B to get a reference. So I make B to have a semi-transparent material for Viewport view. I select A and go to Edit mode to edit it. However, its edges and vertexes are occluded by B. We can see a comparison of 2.83.0 (first image) with 2.82a (second image): version: 2.83.0 does not show active object geometry so that we can not edit it. On the other hand 2.82a does show required geometry.\n\n \n\n1. Open Blender 2.83.0\n2. Create a Sphere mesh in the world origin so that it fits inside the default cube.\n3. Assign a semi-transparent viewport display material to the Cube so that we can see the Sphere inside. Change color also to have a better view.\n4. Select Sphere and go to Edit mode.\n5. Press A to select all vertexes.\n6. We can see that Edges and Vertexes are occluded by the Cube so that we can not edit the Sphere properly.\n\n\n[bug-report.blend](bug-report.blend)\n", "Cycles not really excluding lights from volume MIS calculation\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nI noticed that cycles, when using volume lights, if we exclude lights from the volume contribution it still affects the sampling of the visible volume lights.[Volumeissue.blend](Volumeissue.blend)\n\nIve included the blend file and also described the issue visually in this thread:\n10982\n\nTo check the issue just turn on and off the Volume Scatter ray visibility and compare the result by hiding the lights instead.\n\nI think this is a serious performance issue in scenes with multiple lights, with some lights contributing to volume while others not, which forces the user to unnecessarily throw a lot of volume samples to get rid of the noise.\n\n\n", "Occasional render glitches when using simulation zones on an object without a material.\nThis bug has an easy workaround, mostly posting this so anyone running into the same issue knows the solution.\n\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.30.02\n\nBroken: version: 3.6.2\nWorked: N/A, 3.6 is the first version with simulation nodes.\n\nIn Eevee, rendering an object with a simple simulation zone applied in geometry nodes and no material assigned to the object results in some rendered frames being blank or displaying odd glitches.\n\nThe workaround is to simply assign a material to the object.\n\nCheck out the attached .blend file for reproduction.\n\n", "Some modifiers do not consider freshly added vertex group as empty\nOperating system: Win 10\nGraphics card: 1050 ti\n\nBroken: 3.2.0 Alpha\n\nEmpty vertex group was added to mesh in object mode without weight assigning and modifiers in stack are using this vgroup.\nSomehow some modifiers follow restriction and others don't. But if you assign zero weight for this vgroup in edit mode, then all modifiers are limited in execution as expected.\n\nFor example, open file and enable viewport rendering for every modifier in stack. \n[empty_vgroup.blend](empty_vgroup.blend)\n\nList of modifiers with this behavior:\nCast\nCurve\nDecimate\nLattice\nSmooth\nSmooth Corrective\nSmooth Laplacian\nWeld\nWave\n\n\n- Open new General template\n- Add monkey\n- Create new vertex group, but don't assign any vertices or weight\n- Add Smooth modifier\n\nIt should not deform mesh, because of empty vertex group, but it does", "Undo doesn't work with image type empty\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\n\nUndo doesn't work with image type empty (reference image) when you use the bracket or the centre cross to scale or move the empty image, that is very annoying when you accidentally modify your reference image image. A working undo or an option to disable the direct moving/scaling possibility (yellow gizmo) for such empty will be welcome. The undo is active when we use the normal scaling or moving gizmos or panels. \n \n\n- Create an image reference (drag and drop an image in the viewport) \n- Change size and position using the yellow gizmo on the object itself \n- Undo. \n\n", "GeometryNodes: Attributes in shader not visible in Eevee \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\n\nWhen an attribute is used in the shader editor, it will render in Cycles but not Eevee. \n\nHave an attribute in a shader as a render output with the Eevee render engine enabled. \n\n[Possible Attribute Bug.blend](Possible_Attribute_Bug.blend)\n\n", "Alpha Blend material has inconsistent behavior with Geometry nodes\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nAlpha Blend material renders differently on the object, which is referenced inside Geometry Nodes tree of another object, despite this another object is already hidden and has muted GN modifier.\n\nIn attached file:\n* Remove/Select *Shell* object inside GN tree of object *Mesh*\n* Activate/Deactivate *Viewport Disable* for *Collection* or object *Mesh*\nIn both cases material becomes transparent or not\n\n", "Add object redo: exits local view if there are no other objects in local view\nBroken: 2.80 to 2.92 master\nWorked: 2.79b\n\n\nIf you're in local view and there are no objects, add an object and attempt to adjust any property in the redo panel, Blender drops out of local view. However, if you don't touch the redo panel and instead e.g. transform the object, local view is retained.\n\n\nIn the default scene with cube selected:\n\n- enter local view\n- delete the cube\n- add a new object\n- attempt to adjust any property in the redo panel", "EEVEE: Volumetric simulation show ghosting in playback\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: ALL versions up to and including version: 2.91.0 Alpha\n\n\n\nHere's the video of the problem, as can be seen, I have to stop playback to clear the viewport vdb data from the previous frames. Left is EEVEE viewport, right is solid mode (so you can see what the eevee viewport should be displaying:\n\nIt isn't related to EEVEE volume optimisation as I have tried reducing the number of voxels displayed and also reducing the volume samples, viewport samples, and turning off the denoiser. \n\nlatest gpu driver and blender version, resetting blender to factory defaults doesn't help.\n\n[2020-08-20 04-22-55.mp4](2020-08-20_04-22-55.mp4)\n\nHere's the blend file:\n\n[vdb playback bug.rar](vdb_playback_bug.rar)\n```\n\n```\nP.S, the fps is Extremely slow compared to other 3d apps I've tested this sim in (with shading). Is this due to all of the surplus vdb data not being cleared? Perhaps there needs to be an option to cache to RAM if reading from disk is the cause?\n", "Cycles Motion Blur disappears for Rotating object with speed 360˚/frame or its multiples\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nIt has been found that**Motion Blur**on **Cycles Render Engine** completely **disappears** for a rotating object with speed 360˚/frame or its multiples like 720˚/frames etc. and rendering it like a still object.\nPlease find the attached Rod.blend file where a rectangular cuboid rod is rotating at speed 360˚/frame i.e. 1,440 RPM for a 24 FPS animation but I am unable to apply cycles motion blur on it. Framerate can be increased to resolve the problem temporarily but it will not solve the problem permanently as at higher RPM the same problem will appear again.\nKindly look into the issue and if any solution exists please guide me on that. \n[Rod.blend](Rod.blend)\nRod.blend example file attached with this description.\n" ]

[ "Volume Displace blocky\nOperating system: Windows 10\nGraphics card: GTX 970\n\n2.91 Beta\n\nWhen using the Volume Displace you get weird blockyness when rendering in Cycles. \nThis is a suzanne turned into a volume with a displace turned to 0 (doesn't matter what value I use, still looks the same)\n\n\nAnd this is with the modifier turned off\n\n\nCreate monkey, create an empty volume, add a Mesh to Volume modifier (bump up the voxel amount higher for clearer effect of the bug), add a Volume Displace modifier, render in Cycles.\n[volbug.blend](volbug.blend)" ]

[ "Adding Clearcoat freezes Blender with error \"Execution of the command buffer was aborted due to an error during execution\"\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 5700 XT 1.2\n\nBroken: version: 3.5.0\nWorked: Unknown\n\nAdding Clearcoat to a Surface freezes Blender, with Console logs showing only an \"Execution of the command buffer was aborted due to an error during execution. <private>\" error.\n\nOnly appears to happen when using Metal, using Blender in OpenGL mode doesn't have this issue. The issue is also present on brand-new projects with just the default cube.\n\n1. Create new file (Eevee renderer)\n2. Change the Clearcoat amount of the default cube from the Materials tab.\n3. Blender crashes usually within seconds, with the default cube I've found it freezes more easily if you use the sliding mechanism to change the Clearcoatness.\n\n", "Crash with certain file. Sculpt mode. Vertex color fill + edge.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nWhen I try to apply vertex color Fill (Sculpt mode) on edge in this particular file, I get crash\nAnd all fine for shapes/triangle.\n\n[VC + edge crush.blend](VC___edge_crush.blend)\n\n[debug_logs.7z](debug_logs.7z)\n", "Expand face sets crashes blender when mesh has no faces\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.5.0 Alpha\n\nif the mesh doesn't contain faces, the expand face set operator will crash blender.\n\n- Open .blend file\n- Enter sculpt mode\n- Press {key Shift W}\n[#102290.blend](T102290.blend)\n\n```\nStack trace:\nblender.exe :0x00007FF6EDD094F0 sculpt_expand_invoke C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\blender\\editors\\sculpt_paint\\sculpt_expand.c:2142\nblender.exe :0x00007FF6ED4EF700 wm_operator_invoke C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:1446\nblender.exe :0x00007FF6ED4ED030 wm_handler_operator_call C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:2478\nblender.exe :0x00007FF6ED4EEA90 wm_handlers_do_keymap_with_keymap_handler C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:2875\nblender.exe :0x00007FF6ED4EE220 wm_handlers_do_intern C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3196\nblender.exe :0x00007FF6ED4ED640 wm_handlers_do C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3337\nblender.exe :0x00007FF6ED4F3970 wm_event_do_handlers C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3979\nblender.exe :0x00007FF6ED4D9C50 WM_main C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\blender\\windowmanager\\intern\\wm.c:643\nblender.exe :0x00007FF6ED1C6B80 main C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\blender\\source\\creator\\creator.c:580\nblender.exe :0x00007FF6EE7A1274 __scrt_common_main_seh D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nKERNEL32.DLL :0x00007FF9E1BB54D0 BaseThreadInitThunk\nntdll.dll :0x00007FF9E25C4830 RtlUserThreadStart```", "GPencil: Selecting textured brushes will crash Blender\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92.0\n\nWhen appending the textured brushes from the [Blender Cloud](5ccfe64353b85e279cf72acd) into a file, Blender will crash when trying to preview the brushes in the tool settings.\n\n\n - Open Blender 2.93 and select the \"2D Animation\" template.\n - Go to *File*>*Append* and browse to the `pepeland_GP_brush_pack_V1.blend` file. Go into the *Brush* folder and append the brushes `GBrush_001` through `GBrush_010`.\n # Click the brush icon in the tool settings. Blender crashes.\n\n\n\n", "Python Operators that add/remove ID data without an undo step crash Blender\nOperating system: Win 10\nGraphics card: GTX 1070\n\nBroken: 2.8.3, 2.9 aed11c673efe\nWorked: 2.8.0\n\nUndoing after object linking to the scene crashes blender. I used the latest daily build\n\n1. Load the crash blend file [crash_modal.blend](crash_modal.blend)\n2. Run the script attached\n3. Click in viewport to add a new object, and then press ESC\n4. Press Ctrl+Z to undo\n5. Crash..\n\n", "Intermittent Segfault When Programmatically Creating Node Group\nThere have been intermittent crashes plaguing some of my addons. I think I have narrowed it down to creating node groups using the Python API. Specifically, to connecting something to a new node output.\n\nEnclosed [ldo_node_crash.py](ldo_node_crash.py) is a simple script that seems to reliably reproduce the problem for me; I hope it does for you, too. Open it in, or paste it into, Blender’s text editor, and run with ALT-P. I set the loop to run for 10 iterations, but for me, so far, it has always crashed before that.\n\nI am currently normally running Blender 2.82 on Debian Unstable AMD64; I tried a Blender build from the latest master branch, and the crash happens there, too. The backtrace looks like this:\n\n```\nblender-build-latest-debug/bin/blender(BLI_system_backtrace+0x26) [0x8257e79]\nblender-build-latest-debug/bin/blender() [0x2a09cfc]\nblender-build-latest-debug/bin/blender() [0x2a09efc]\n/lib/x86_64-linux-gnu/libc.so.6(+0x3b7e0) [0x7f5c97ff07e0]\nblender-build-latest-debug/bin/blender() [0x3919d1c]\nblender-build-latest-debug/bin/blender() [0x3919e13]\nblender-build-latest-debug/bin/blender(node_connected_to_output+0xf6) [0x391a0a6]\nblender-build-latest-debug/bin/blender(ED_node_tag_update_nodetree+0x41) [0x390df93]\nblender-build-latest-debug/bin/blender() [0x321f7c6]\nblender-build-latest-debug/bin/blender(NodeLinks_new_call+0x98) [0x323b5c9]\nblender-build-latest-debug/bin/blender(RNA_function_call+0x47) [0x3159a88]\nblender-build-latest-debug/bin/blender() [0x334374e]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyObject_FastCallKeywords+0xd7) [0x7f5c9890c887]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(+0x6dfc3) [0x7f5c9871bfc3]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x68a2) [0x7f5c98722c42]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x92d) [0x7f5c988443dd]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(PyEval_EvalCodeEx+0x3e) [0x7f5c9884465e]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(PyEval_EvalCode+0x1b) [0x7f5c98844e8b]\nblender-build-latest-debug/bin/blender() [0x333463c]\nblender-build-latest-debug/bin/blender(BPY_execute_text+0x39) [0x33348cc]\nblender-build-latest-debug/bin/blender() [0x3969d26]\nblender-build-latest-debug/bin/blender() [0x3969dfb]\nblender-build-latest-debug/bin/blender() [0x2ce7313]\n```", "Rendering object in Cycles X preview hard crashes whole system\nOperating system: Windows 10 x64\nGraphics card: nVidia RTX 8000\n\nBroken: blender-3.5.0-alpha+universal-scene-description.1f9e90bb1cf3-windows.amd64-release\n\nRendering of scene in Cycles preview hard crashes whole system. System screen goes to black and the fans go to max.\n\nLoad blend file at link: brutes_set1C_trimmed.blend?dl=0\n\nSet screen to Render preview and navigate around.\n\n", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "Crash when shading\nModel: HP Probook x360 435 G7 (independently upgraded SSD and RAM)\nOperating system: Windows 11 Pro 22H2 22621.1555\nGraphics card: AMD Radeon Graphics (Built-in graphics of AMD Ryzen 5 4500U with Radeon Graphics)\n\nBroken: 3.5.1 and 3.3.1 were tested, both had this issue.\nWorked: 3.1.2 – At the time of issue creation, there are no newer versions that have worked, including the latest build of 3.6.0 Alpha.\n\nBlender freezes for a second or so, and then crashes.\n\nI don't know if it *is* reproducable, but I have tested multiple conditions under which it crashes. These conditions are accompanied with the crash logs of that test. The problem does not seem to be (V)RAM usage, as the usage remains constant from before Blender is opened to long after.\n- Press F12 to Render Image: Crash [Log](itihmb)\n- Select Default Cube, Click on Shading workspace: Crash [Log](nxyeck)\n- Select Default Cube, Go to Materials tab: Crash [Log](ixgrhp)\n- Change Viewport Shading mode to Material Preview: Crash [Log](diwmma)\n- Change Viewport Shading mode to Render Preview: Crash [Log](ztajes)\n- DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: Crash [Log](gcaded)\n- Change Render Engine to Cycles, Press F12 to Render Image: **No** crash\n- Change Render Engine to Cycles, Click on Shading workspace: Crash [Log](chmkgj)\n- Change Render Engine to Cycles, Go to Materials tab: **No** crash\n- Change Render Engine to Cycles, Change Viewport Shading mode to Material Preview: Crash [Log](fhfyfo)\n- Change Render Engine to Cycles, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Cycles, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\n- Change Render Engine to Workbench, Press F12 to Render Image: **No** crash\n- Change Render Engine to Workbench, Click on Shading workspace: **No** crash\n- Change Render Engine to Workbench, Go to Materials tab: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Material Preview: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Workbench, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\nThank you for your help.\n\n", "Blender 3.5.1 keeps crashing on occasion\nOperating system: Mac OS Ventura 13.3.1 (a) (22E772610a)\nGraphics card: Apple M1 Ultra (64-Core GPU)\n\nBroken: Version 3.5.1 (3.5.1 2023-04-25)\nWorked: N/A\n\nBlender occasionally crashes on my new Mac Studio (I used to work on a Windows PC beforehand and never had that problem). I'm guessing it is a saving error.\n\n- Download and open the demo-file `Blender 3.4 – “Charge” Open Movie` from demo-files/\n- Change the engine from Eevee to Cycles GPU\n- Set \"Viewport Shading\" to \"Rendered\" - nothing happens\n- Go back to Solid View - blender freezes\n\nAttached is is a video demonstrating what is happening, but in a few words:\n\nThe same happens with some of my heavy(ish) project in 3.6.0 beta\n\nIn 3.5.1 the same project responds in render view as it should be.\n\nWhen I try to reopen the same project blender doesn’t load the project but either freezes or crashes ( one of these crash logs is also attached)\nI manage to reopen the project after a few crashes.\n\nI hope it helps! \n\n\n", "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "Crash/Assert with two modifiers that require normals data [e.g. DataTransfer]\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.90.0\n\nCrash/Assert with two modifiers that require custom normals data [e.g. DataTransfer]\n\nIn a Debug build:\n\n[#84664.blend](T84664.blend)\n- Open File\n- add another modifier that requires normal data (e.g. Displace), or just duplicate the existing modifier\n\n[un2.blend](un2.blend)\n- Try to go to edit mode of \"Vert.011\"\n- Blender will crash.\n\n", "Blender 3.4 Random Crashing Since GPU Replacement\nOperating System: Windows-10-10.0.19044-SP0\nGPU: NVIDIA GeForce RTX 3060/PCIe/SSE2 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0, branch: blender-v3.4-release\n\n**Short Description**\nI have replaced my RX580 with an RTX3060 earlier and ever since that replacement, I have been having constant crashes whenever I attempt to use Blender, do note that I've been in edit/object mode during these crashes as I'm working on a subd model, I have tried a handful of fixes such as upping TDR values but it didn't seem to fix the issue.\n\nRyzen 5 2600, RTX3060, 16gb RAM, no temperature exceeds 60 degrees Celsius and nothing is active besides Blender 3.4 along with addons I have installed.\n\nHere are the logs I get when I run Blender via the gpu debug cmd: \n\nEdit: I did try disabling UV Packmaster as per the error logs, but that didn't stop the crashing.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[gunflipped.crash.txt](gunflipped.crash.txt)", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "Crash when auto script execution is enabled\nOperating system: Windows 10 64-bit operating system, x64-based processor\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: Blender 4.0.0 7372b3bdda35 and later\nWorked: never? 2.93 fails too\n\nBlender daily build crashes immediately on launch. The blender start screen isn't shown at all, only a grey window which then immediately closes. The crash log indicates that it is a memory EXCEPTION_ACCESS_VIOLATION (see log file attached).\n\n- Open preferences, enable `auto script execution`\n- Save prefs and close blender\n- Rename attached file and replace it with existing startup file\n- Launch blender (crash)\n\n- - -\n<details>\n <summary> Original report </summary>\nStart Blender through Steam, Blender Launcher, blender_debug_log.cmd, blender_debug_gpu.cmd, or blender_debug_gpu_glitchworkaround.cmd.\nA grey window opens with the Blender logo in the top bar.\nThe window closes as Blender crashes.\n\n[ Crashing_4-0-0_daily.blend](https://projects.blender.orgattachment)\n</details>" ]

[ "Crash when loading addons\nOperating system:\nGraphics card:\n2080s, 12.15 version the studio driver\n\nBroken: (example: 2.92, 977bd7937a07, master,\n\nCrash when the cmd show and give the below information\nRead prefs: C:\\Users\\atticus\\AppData\\Roaming\\Blender Foundation\\Blender\\2.92\\config\\userpref.blend\nregister_class(...):\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF6900A65C0\nModule : blender.exe\nThread : 00001e74\nWriting: C:\\Users\\atticus\\AppData\\Local\\Temp\\blender.crash.txt\n[blender.crash.txt](blender.crash.txt)\n\n", "Crash when opening the Add > Mesh menu or pressing SHIFT+A\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.92.0 Alpha\n\nSHIFT+A crashes latest experimental build of Blender. \n\n- Open Blender\n- Enable Archipack\n- Press SHIFT+A\n\nThe problem can be reproduce by pressing {key F3}.\n\n[blender.crash.txt](blender.crash.txt)\n[exp crash.blend](exp_crash.blend)\n\n```lines\nBKE_previewimg_id_supports_jobs(const ID * id) Line 436\tC++\nicon_set_image(const bContext * C, Scene * scene, ID * id, PreviewImage * prv_img, eIconSizes size, const bool use_job) Line 1419\tC\nui_id_preview_image_render_size(const bContext * C, Scene * scene, ID * id, PreviewImage * pi, int size, const bool use_job) Line 1951\tC\nui_icon_ensure_deferred(const bContext * C, const int icon_id, const bool big) Line 1358\tC\nui_def_but_icon(uiBut * but, const int icon, const int flag) Line 4128\tC\nuiDefIconTextMenuBut(uiBlock * block, void(*)(bContext *, uiLayout *, void *) func, void * arg, int icon, const unsigned char * str, int x, int y, short width, short height, const unsigned char * tip) Line 6396\tC\nui_item_menu(uiLayout * layout, const unsigned char * name, int icon, void(*)(bContext *, uiLayout *, void *) func, void * arg, void * argN, const unsigned char * tip, bool force_menu) Line 2882\tC\nuiItemM_ptr(uiLayout * layout, MenuType * mt, const unsigned char * name, int icon) Line 2929\tC\nuiItemM(uiLayout * layout, const unsigned char * menuname, const unsigned char * name, int icon) Line 2939\tC\nrna_uiItemM(uiLayout * layout, const unsigned char * menuname, const unsigned char * name, const unsigned char * text_ctxt, bool translate, int icon, int icon_value) Line 442\tC\nUILayout_menu_call(bContext * C, ReportList * reports, PointerRNA * _ptr, ParameterList * _parms) Line 2304\tC\nRNA_function_call(bContext * C, ReportList * reports, PointerRNA * ptr, FunctionRNA * func, ParameterList * parms) Line 7529\tC\npyrna_func_call(BPy_FunctionRNA * self, _object * args, _object * kw) Line 6317\tC\n \t[External Code]\t\nbpy_class_call(bContext * C, PointerRNA * ptr, FunctionRNA * func, ParameterList * parms) Line 8522\tC\nmenu_draw(const bContext * C, Menu * menu) Line 875\tC\nUI_menutype_draw(bContext * C, MenuType * mt, uiLayout * layout) Line 5745\tC\nui_item_menutype_func(bContext * C, uiLayout * layout, void * arg_mt) Line 2825\tC\nui_block_func_POPUP(bContext * C, uiPopupBlockHandle * handle, void * arg_pup) Line 182\tC\nui_popup_block_refresh(bContext * C, uiPopupBlockHandle * handle, ARegion * butregion, uiBut * but) Line 590\tC\nui_popup_block_create(bContext * C, ARegion * butregion, uiBut * but, uiBlock *(*)(bContext *, ARegion *, void *) create_func, uiBlock *(*)(bContext *, uiPopupBlockHandle *, void *) handle_create_func, void * arg, void(*)(void *) arg_free) Line 824\tC\nui_popup_menu_create(bContext * C, ARegion * butregion, uiBut * but, void(*)(bContext *, uiLayout *, void *) menu_func, void * arg) Line 356\tC\nui_block_open_begin(bContext * C, uiBut * but, uiHandleButtonData * data) Line 4094\tC\nbutton_activate_state(bContext * C, uiBut * but, uiHandleButtonState state) Line 8007\tC\nui_handle_button_event(bContext * C, const wmEvent * event, uiBut * but) Line 8797\tC\nui_handle_menu_button(bContext * C, const wmEvent * event, uiPopupBlockHandle * menu) Line 9520\tC\nui_handle_menu_event(bContext * C, const wmEvent * event, uiPopupBlockHandle * menu, int level, const bool is_parent_inside, const bool is_parent_menu, const bool is_floating) Line 10151\tC\nui_handle_menus_recursive(bContext * C, const wmEvent * event, uiPopupBlockHandle * menu, int level, const bool is_parent_inside, const bool is_parent_menu, const bool is_floating) Line 10642\tC\nui_handler_region_menu(bContext * C, const wmEvent * event, void * UNUSED_userdata) Line 10787\tC\nwm_handler_ui_call(bContext * C, wmEventHandler_UI * handler, const wmEvent * event, int always_pass) Line 636\tC\nwm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2762\tC\nwm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 2870\tC\nwm_event_do_handlers(bContext * C) Line 3293\tC\nWM_main(bContext * C) Line 638\tC\nmain(int argc, const unsigned char * * UNUSED_argv_c) Line 526\tC\n \t[External Code]\n```\t\n```\n", "Crash with any acction on blender 2.92 or Asset Browser branch\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: (example: 2.92 2020-12-15 32:20 )\n\n\n\nmy application is closed when press right click, or shift + A or some acction. Same problem with Asset Browser version.\n\n" ]

[ "Strokes in front of a 3d object will change and become jagged after it is placed\nOperating system: windows 10\nGraphics card: 2070 super\n\nBroken: 2.93.0\n\n\nIn front of a 3d object like a plane, the strokes will alter itself and become jagged after you let go of the stroke to place it. On full screen in my video it becomes very apparent especially the second time I do it.\n\nTest File:\n[#91204.blend](T91204.blend)\n[stroke becomes wavy after leting go of the pen this one.mp4](stroke_becomes_wavy_after_leting_go_of_the_pen_this_one.mp4)", "bump map off/wrong for panoramic camera\nMy apologies if I overlooked a bug report while searching for an existing one. I wasn't able to find one about the problem described below however, so here goes:\n\nWindows 7/CPU and Windows 10/GTX 1060\n\nBroken: 2.79b and build 9d59851ca3d\n\n\nWhen using a bump map with a panoramic camera, the bump map looks like a an overlay of itself with a shifted copy. See image below, which is just a plane with a bump map texture to simulate engraving.\n\n\nWith a perspective camera, the bump map looks as expected:\n\n\nSee attached .blend file.[bump_pano_perspective.blend](bump_pano_perspective.blend)\n\nRender the scene or turn on rendered preview, with the fish eye camera selected. The result is the first image. \nThen switch to perspective camera in the scene tab and render again or see the preview. The result is the second image. \n\nThanks a lot for looking into this!\n", "Overlapping Smoke Volume Cycles render bug\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: \nversion: 2.91.0\nversion: 2.92.0 Alpha\nWorked: \n\n\n\nI have simulated smoke volume, flipped the volume, then linked duplicated and placed volumes overlapping each other.\n[wf.blend](wf.blend)\n\n", "VSE UI Regression: Text of transformed strips is colliding with text of non transformed strips\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\n\nDrag a strip over another strip:\n{[F10136750](text_overlap.gif),size=full}\n\nThis is 2.49:\n{[F10138081](2-49.gif),size=full}", "Selected object color is weird in wireframe mode if the object color isn't single.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 3.0.0 Alpha\n\nOutline overlay seems to be drawn under wireframe.\n\n[#91619.blend](T91619.blend)\n\nImmediately visible in provided file.", "(Grease pencil) Blender freezes indefinitely when drawing using stabilize stroke function. \nOperating system: Windows 10 business 64bit\nGraphics card: Intel UHD 620/630\n\nBroken: both 3.2.2 and the experimental build 3.4.0 alpha\n\n\nWhile drawing using the stabilize stroke function (in blank grease pencil object), after some times blender freezes and stop responding, tested on both an HP prodesk g5 ( I5 8500, intel IGP UHD 630 and 8 GB of RAM) and asus zenbook (I5 7200U, UHD 620, 8GB RAM).\n\nThis only happened on both PCs equipped with intel IGP, I redid the same test on my home PC (I5 9400f, GTX 1060, 16GB RAM) and everything worked fine.\n\nIs this purely a performance issue ?\n\nJust create a blank grease pencil object and directly start drawing using the stabilize stroke function, test setup must be similar or close to the two PCs equipped with Intel IGP.", "Mode hotkeys - different hotkeyset for grease pencil object required, entries in keymanager problem\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 51)\nWorked: (optional)\n\n\n\nThe grease pencil object doesn't show the general object mode hotkeys when you assign some. It requires its own hotkey set for the modes. But in the keymanager they will appear as the exact same entries. Except draw mode, which doesn't exist for other object types. \n\nThere is a problem then with the display in the key manager. When you add the extra set for the grease pencil type, then you can't see the mode anymore for the mesh object type modes. I guess it's because it is in fact a double entry with the ones created for the grease pencil object.\n\nI also managed to mess up the object mode hotkeys then with saving the preferences. All modes except object mode had the same key assigned then. But this wasn't reproduceable so far. And might be another issue.\n\n\nCreate a set of hotkeys for the modes with a mesh object. Create a grease pencil object, have a look at the modes. No hotkeys except object mode.\n\nCreate a set of hotkeys for the modes with the grease pencil object.\n\nHead over to the preferences into the keymap tab. Search for mode. Have a look at the Object Non-Modal section. Here you can find the mode hotkeys. Open the first ones up, have a look for the modes. No mode content in the boxes ...\n\nI wonder why the grease pencil object doesn't find the other mode hotkeys from the mesh object at all. That's the second thing. There is no visible difference in the keymanager, it's in the same category ...\n\n\n\n\n\n\n\n\n", "Grease Pencil keyframes not updating after GPencilFrames.copy()\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha\n\nCopied keyframes do not update with Grease Pencil Layer\n\n- Create a new document with the 2D Animation template\n- Draw a shape \n- (Note by @iss) It may be necessary to make new keyframe at later frame, see video\n- Run the below script in the Text Editor\n# Run the \"Grease Pencil Test Script\" command from the Draw Menu\n\nThe Grease Pencil data isn't updating in the Viewport unless the playhead is going backwards, a keyframe is deleted, or if the keyframes are added to a new `GPencil` object. I believe the issue is because the keyframes generated with `GPencilFrames.copy` are missing the layer update for some reason. If I use `GPencilFrames.new()` and copy every attribute manually, this issue does not happen. In the below code, I am updating all of the data I know to be possible.\n\n```\nimport bpy\n\ndef main(context):\n active_layer = context.active_gpencil_layer\n frames = active_layer.frames\n start_frame = frames[0]\n frame_numbers = [frame.frame_number for frame in frames]\n\n for frame in range(start_frame.frame_number, context.scene.frame_end+1):\n if frame in frame_numbers:\n continue\n new_frame = frames.copy(start_frame)\n for i,start_stroke in enumerate(start_frame.strokes):\n new_stroke = new_frame.strokes[i]\n for p,start_pt in enumerate(start_stroke.points):\n new_pt = new_stroke.points[p]\n new_pt.co[0] = start_pt.co[0]+(frame*0.5)\n new_frame.frame_number = frame\n\n gpencil = context.object\n gpencil.data.layers.update()\n for l in gpencil.data.layers:\n l.frames.update()\n for f in l.frames:\n f.strokes.update()\n for s in f.strokes:\n s.points.update()\n\n gpencil.data.update_tag()\n context.view_layer.depsgraph.update()\n context.view_layer.update()\n bpy.ops.gpencil.recalc_geometry()\n\nclass GPENCIL_OT_simple_operator(bpy.types.Operator):\n bl_idname = \"gpencil.simple_operator\"\n bl_label = \"Grease Pencil Test Script\"\n\n def execute(self, context):\n main(context)\n return {'FINISHED'}\n\ndef draw(self, context):\n self.layout.operator(GPENCIL_OT_simple_operator.bl_idname)\n\ndef register():\n bpy.utils.register_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.append(draw)\n\ndef unregister():\n bpy.utils.unregister_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.remove(draw)\n\nif __name__ == \"__main__\":\n register()\n```\n\nPlease disregard the step where I put the GP Object into Edit mode & create a new keyframe. This step is not necessary to seeing the `GPencilFrames.copy` bug.\n[duplicated_frame.mp4](duplicated_frame.mp4)\n\nNot sure if the bug will show consistently, but here is the scene file:\n[Grease_Pencil_Data_Bug.blend](Grease_Pencil_Data_Bug.blend)", "Shadow catcher causes artifacts in PNG exports with denoising\nOperating system: Manjaro Linux\nGraphics card: AMD Radeon 535\n\nBroken: 3.1.0\n\n\nIn Cycles, rendering a scene with transparent world background and shadow being projected into a shadow catcher causes a ring of pixels with very little opacity to be created around the render's edges when exporting it as a PNG. These artifacts go away when re-rendering the scene with the shadow catcher turned back into a normal plane.\n\nI'm aware of #93865 (Artifacts around shadow catcher object) but created this one because it wasn't clear to me if this was the same issue, as that one seems to be considered a property of the 'Fast' denoiser. These artifacts were recorded on the 'Accurate' one.\n\n- In Cycles, make the world background transparent\n- Move the default cube slightly up and add a plane, scale it up a bit. \n- Point the camera so that your render captures the cube projecting a shadow into the plane, but still has the transparent world background showing around the edges\n- Turn the plane into a shadow catcher and render the scene with denoising on. Export it as a PNG; color depth and compression don't affect this issue.\n- Save the render and open it in Krita (other image editing applications may have the following feature too)\n- On the Select menu, use Select Opaque to highlight all pixels with some opacity. You will notice pixels very close to the image border all around the edges. These are normally invisible, being of very low alpha, but if you stack many renders produced like this they will be revealed as being grayscale.\n- Now, change nothing else, but turn the shadow catcher into a normal plane. Render the scene again, save it with the same settings. The ring of noise around the image edges will have disappeared.\n\nScreenshot of Krita showing the opaque pixels on a normal render:\n\n\n\nOpaque pixels on the same scene rendered with the plane made into a shadow catcher and denoising set to Accurate. Note the barely visible artifacts selected around the plane and image edge. These can be observed no matter what shape the render output takes.\n\n\n\nAnd now the same scene, denoising turned off. No ring around the edges.\n\n\n\nBlender file used for the renders above: [democatcherbug.blend](democatcherbug.blend)", "full scene copy does not duplicate obdata of objects in Edit mode\nOperating system:\nGraphics card:\n\nBroken: 3.3 LTS and 3.3.1 LTS\n\n\nif you make a full screen copy of a 2D blend file with some objects in edit mode, the objects in edit mode are linked to the original scene i.e.not independent.\n\nCreate a new 2D project and add a blank grease pencil object\nSelect draw mode and add a stroke say a square\nSelect edit mode and select the stroke for point editing\nCreate a full copy of the scene still in edit mode\nMove a point on the selected stroke in the new scene and observe that the same point moves on the original scene. This means the two scenes are linked.\nCarry out the same steps but before creating the new full copy change the mode to object mode.\nagain move one of the points of the stroke in the second scene and note that the object in the original scene does not change i.e. a full copy.\n\nSame is true at least for meshes and curves, so presumably all obdata.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "pixelated Artifacts displayed in 3D view port on the wire frame with 'Outline Selected' On or 'smooth wires overlay' turn on.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.42.01.221031\n\nBroken: version: 3.5.1\n\nPixelated Artifacts are displayed on the selected object's wire frame in the 3D view port, in object mode when viewed through the camera with 'Outline Selected' turned On. The grid floor also has pixelated artifacts on it's wire frame in both edit and object mode when viewed through the camera and 'smooth wires' overlay is turned on in preferences -> view port -> quality. When you rotate the view and it brakes from the camera view the artifacts disappear.\n\nIn 3D view turn on 'Outline Selected' On and or in preferences -> View port -> quality turn on 'smooth wires' overlay.\nBased on the attached .blend file (as simple as possible)\n\n", "Library Overrides: Making an override (for a linked object in the scene collection) creates a duplicate object\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\nLibrary Overrides: Making an override (for a linked object in the scene collection) creates a duplicate object\n\n- open `main.blend`\n- (there is a linked object in the scene collection)\n- `Object` > `Library Override` > `Make`\n- A separate (overridden) Cube object is created in the scene collection (along with the linked object still there)\n\nNOTE: doing the same from the Outliner (RMB > `Library Override` > `Make` > `Selected`) seems to work as expected\n\nas a comparison:\n- open `main_with collection.blend`\n- (there is a linked object in a collection [not the scene collection])\n- `Object` > `Library Override` > `Make`\n- The overriden Cube object is just there without the linked object Cube being present\n\n", "LineArt: New module to generate lines over meshes using grease pencil as target\nThis is the main Line Art task, includes the implementation of following functions:\n\n- Line Art cpu calculation code and UI.\n- Line Art modifier for Grease Pencil.\n- Other additional data structures in Object/Collection/Materials.\n", "GPencil: Hard to erase drawing when layer parented to animated object\nOperating system: MacOs 10.15.4\nGraphics card: AMD Radeon Pro 5500M 8 GB\n\nBroken: Version 2.90 (2.90 2020-05-20)\nWorked: ?\n\nSorry for the potentially misleading title. I think that when a Grease Pencil drawing is parented, and the parent animated, the erase tool (using control/Alt/Right Click or the Brush eraser) is somehow offset and it's near impossible to erase precisely. Going in Edit mode and Selecting/Deleting the vertices/strokes works though... \n[GP_EraseWhenParentedIssue.mp4](GP_EraseWhenParentedIssue.mp4)\nHere is the Blend file.\n[GP_EraseWhenParentedIssue.blend](GP_EraseWhenParentedIssue.blend)", "Grid lines showing up when origin is far from mesh\nOperating system: Win 10 Home\nGraphics card: GTX 1070\n\nBroken: (example: 3.2.1, a2d59b2dac9e, master, 2022-07-05, as found on the splash screen)\n\n\nGrid lines showing up when origin is far from mesh but only when bumping out the normals in the shader editor, more testing required. (only happens in cycles regardless of optix/cuda or cpu rendering)\n\nopen the attached blend file and go to camera view, then switch to viewport shading or render an image. you will notice a grid on the surface of the plane in certain areas. And the grid goes away when origin is set to centre of mesh. Or you disable the bump node in the shader editor. Seems to be a rendering bug." ]

[ "GPencil: Texture Image Alpha pass through grease pencil strokes\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83.1\n\nContext: Using texture image to make some kind of 2d fur on top of a GPencil Object\n\nThe Image Texture used to make some fur is mostly transparent and the brush used to make the colored part is a texture paint brush with Cloud Mask (it was made entirely in Blender with Blender tools).\n\nWhen on top of the GPencil object, the part of the Image Texture that is only half transparent(between 99%-1% transparent), makes the GPencil color disappear, even when moving the center point behind the one of the fur images.\n\nOn the contrary, when on top of another Image Texture (imported to be used as camera mapping), the Image Texture of the fur doesn't impact the transparency of that one.\nNotice that the Image texture boundary, even from the imported one, has problems with clipping and always makes a white line appear.\n\n- Open attached .blend file\n- Zoom in and out to notice the alpha transparency influencing the GP object\n\nThanks for your help!\n\n\n\n\n\n\n\n[bug_alpha.blend](bug_alpha.blend)" ]

[ "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "Compositor artifacts from image wrapping\nOperating system: Linux-5.15.13-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46\n\nBroken: version: 3.1.0 Alpha\nBroken: 2.80 upwards\nWorked: 2.79\n\nIn the compositor, when using a Scale node with a value of < 1.0 after a Translate node with wrapping enabled, a strange pattern can be sometimes seen in the final render (sort of like Z-fighting). Also, re-rendering with the same settings doesn't always yield the same results with this setup.\n\nChanging the chunksize to anything other than 256 seems to fix this for me.\n\n\n\nI've created and attached a .blend file that has the compositor setup in the right way to display this bug. So all that's required is to render the scene - possibly refreshing the compositor a few times as the bug doesn't always occur.\n\n[blender-bug-report.blend](blender-bug-report.blend)", "Compositor: Viewport issues when zoomed in\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera is not fully in view.\n\n\n* Open this file: [zoomed_in.blend](attachment)\n* Notice that in the viewport the view is zoomed in inside the camera view.\n\nCurrent buggy result:\n\n\nThe mask only matches when the entire camera is in view:\n\n\n", "VSE: Adding packed sound via python API produces strip with incorrect length\nBroken: Blender 3.4.1\n\n\n\n**Steps to reproduce**\n[#103662.blend](T103662.blend)\n\n- Open file\n- Run script\n# Look in console\n\nIt prints `Strip duration is 1` which is incorrect.\nThis is because `BKE_sound_info_get()` does not work correctly with packed sound.\n", "Unbaked Dynamic Paint Not Displayed in Rendered Output but Shows in Viewport\nOperating system: Manjaro 18.0.1 Illyria / x86_64 Linux 4.14.90-1-MANJARO\nGraphics card: Nvidia 1080 Ti\n\nBroken: 2.80 (sub 39), Commit date: 2018-12-29 18:10, Hash 266b1e2cdbc1\nWorked: 2.79 (sub 6), Commit date: 2018-10-22 16:17, Hash 86dbbd156fa\n\nUnless baked, dynamic paint does not affect the final rendered image but is properly displayed in viewport.\nThe default and expected behavior is to be able to render the effect regardless if baked or not. This is how 2.7x operated in the past.\nMoreover this problem, which I assume has something to do with vertex colors [has caused other issues ]] with different [[ https:*github.com/hsab/tensionmap | addons ](https:*github.com/JacquesLucke/animation_nodes/issues/989) that depend on similar workflows of modifying the vertex color using the python API (eg. proximity, stress mapping etc.) \nNot sure if #51214 is related since it's from April 2017. If so please close as a duplicate.\n\nTwo blend files attached, one for 2.8 and one for 2.79.\n2.79 file works as expected.\n2.8 file is broken unless baked.\n\n2.79.6 Render:\n\n\n2.80.0 render:\n\n\n[dynamicpaint2.8.blend](dynamicpaint2.8.blend)\n[dynamicpaint2.79.blend](dynamicpaint2.79.blend)", "VSE UI Regression: Text of transformed strips is colliding with text of non transformed strips\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\n\nDrag a strip over another strip:\n{[F10136750](text_overlap.gif),size=full}\n\nThis is 2.49:\n{[F10138081](2-49.gif),size=full}", "I export a pyro from C4D as VDB but the rendering time is not displayed with the cycle?(only cycle)\nOperating system: win 11.x64\nGraphics card: rtx 3070ti\n\n3.5.0, 2023-04-26\n\n**I checked in different modes and tested with other VDB files, they are fully rendered in the rendering cycle, but this file, which was output from Cinema 4D, only works in Eevee mode.**\n", "Freestyle > \"Render Animation\" uses only the widest keyframed focal length for all the frames\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.81 (sub 16)\nBroken in the most current 2.83, date: 2020-02-17 00:09:39, hash: `819af2094b21\nWorked: 2.8\n\n\nWhen the focal length of the camera is keyframed to different values over several frames, Freestyle takes only the widest focal length and uses it for all keyframes\n\n[Freestyle_Test.blend](Freestyle_Test.blend)\n1. Open the attached blend file\n2. Set the Output location for the rendered images\n3. Select \"Render Animation\" and check the finished frames\n\nThanks so much for your help! Highly appreciated\n\n", "VSE Scene strip's color profile is overridden by sequencer settings\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nThere are two scenes:\n1. **Scene.001** is VSE sequencer with *RGB* profile in color management\n2. **Scene** is used as *Scene Strip* and has *XYZ* color profile\n\nWhen rendering **Scene** strip from **Scene.001** sequencer, it overrides original *XYZ* with its *RGB*, but OpenGL preview shows correct mode.\n\nIn attached file render separately **Scene** 3d view and **Scene.001** VSE sequencer to see the difference\n\n", "Vector pass not being saved correctly when using the File Output node\nOperating system: Win 10\nGraphics card: RTX 3090\n\nBroken: 3.3\nWorked: Not sure\n\nAccording to doc, vector pass is a 4-component vector, but when it's being piped through to a File Node in the compositor, it seems only 3 components are saved. This causes some motion data to be missing in the final multilayer exr.\n\n- Open attached file\n- `Render` > `Animation` - it will render 1 frame and save 2 exrs.\n 1. One using the blender native file output\n 2. Another using the file Node\n\n- Once it's rendered, the compositor should auto update to load these 2 exrs files below. If not, refresh the input nodes.\n- Check the vectorblured output. They are different.\n[mblur-bug.blend](mblur-bug.blend)", "EEVEE: Volumetric simulation show ghosting in playback\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: ALL versions up to and including version: 2.91.0 Alpha\n\n\n\nHere's the video of the problem, as can be seen, I have to stop playback to clear the viewport vdb data from the previous frames. Left is EEVEE viewport, right is solid mode (so you can see what the eevee viewport should be displaying:\n\nIt isn't related to EEVEE volume optimisation as I have tried reducing the number of voxels displayed and also reducing the volume samples, viewport samples, and turning off the denoiser. \n\nlatest gpu driver and blender version, resetting blender to factory defaults doesn't help.\n\n[2020-08-20 04-22-55.mp4](2020-08-20_04-22-55.mp4)\n\nHere's the blend file:\n\n[vdb playback bug.rar](vdb_playback_bug.rar)\n```\n\n```\nP.S, the fps is Extremely slow compared to other 3d apps I've tested this sim in (with shading). Is this due to all of the surplus vdb data not being cleared? Perhaps there needs to be an option to cache to RAM if reading from disk is the cause?\n", "Some particles are not being rendered during the first render\nOperating system: Windows 10\nGraphics card: I tried on two different computers with different GPUs - Nvidia RTX3070 and Mobile Nvidia RTX2060, same behaviour.\n\nBroken: 2.93.6, 3.0.0 Release Candidate, 3.1.0 Alpha\n\n\nBlender is not rendering some particles (in my case this is a grass) during the first render.\nIt does after re-rendering the scene, but this is quite confusing and inconvenient, especially in the moments when I have to resume render of animation.\nApparently this only happens when we add a force field to control the particles.\n\nOn top of this, 3x does not render trees (particles).\n\nOpen the blend file and press F12 to render. You should have similar result as on the screenshot:\n\n\n\nRender again, and the grass will appear:\n\n\n\nI attach results also from 3.0:\n\n\n\n\n\nand 3.1:\n\n\n\n\n\n- Open attached file\n- Render (F12) - See the particles issue\n- Render again - Now it is ok\n\n[turbulence_particle_eevee_bug.blend](turbulence_particle_eevee_bug.blend)\n\n---\nOriginal File:\nBecause file is big (260M) I have decided to share the link: view?usp=sharing <- if you would prefer me to upload it anyway here, please just let me know.", "Image.save_render saves OpenEXR Multilayer as a regular OpenEXR with no layers\nOperating system: Windows 10\nGraphics card: (2x) NVIDIA GeForce GTX 1070\n\nBroken: (2.80 release)\n\nWhen exporting a **Multilayer OpenEXR** file using Blender's Python API and the [bpy.types.Image.save_render ](bpy.types.Image.html?highlight=save_render#bpy.types.Image.save_render) function, the image is exported as a **regular OpenEXR** file with neither layers nor passes.\nThis is NOT an issue with the way Blender reads Multilayer OpenEXR files because exploring the EXR files with other software yields missing layers and passes as well.\n\n1. Download and open the attached .blend at the bottom of this file (openexr_bug_24_10_19.blend)\n2. Note that there are multiple passes being rendered (Combined, Z, Mist, etc.) and there are also multiple layers being rendered (View Layer and Composite)\n2. Click \"Run Script\" in the text editor. This script will render an image, configure its output settings to be a Multilayer OpenEXR, then write it to the same directory that the Blender file is in.\n3. Import the exported OpenEXR (named \"script_output.exr\") into Blender's compositor either by clicking and dragging it in, or by opening it in an image node\n4. Note that the image is missing the extra layers that should be included (Normal, AO, Mist, etc.)\n\nIt may be useful to note that if you actually tear apart the exported OpenEXR file, the only channels included are 'R', 'G', 'B', and 'A'.\n\n**Expected behavior, for comparison**\n1. In the Image Editor with the rendered image, select Image > Save As and save it somewhere using the settings detailed in the script (Multilayer OpenEXR, RGBA, 32-bit depth, No Codec)\n2. Import the saved OpenEXR in Blender's compositor either by clicking and dragging it in, or by opening it in an image node\n3. Observe how there is an additional \"Layer\" option in the image node, and depending on the layer that is selected, different passes appear as outputs from the node\n\nIt may be useful to note that if you tear apart this OpenEXR file, the channels included are: 'Composite.Combined.R', 'Composite.Combined.G', 'Composite.Combined.B', ... all the way through all of the image layers and passes.\n\n**Included Files**\n[openexr_bug_24_10_19.blend](openexr_bug_24_10_19.blend)\n", "VSE: Frame Rate Base Rounding Leads To Vid / Audio Strips Out Of Sync by 1 Frame\nOperating system: Windows 10\nGraphics card: RTX 3090\n\nBroken: since 3.0 until now in 3.6.1 hash 8bda729ef4dc\nWorked: 2.93.18\n\nIt looks like the same bug #21138 is reappearing in the 3.x series and since the bug report is 14 years old, I created a new one.\nOld bug report: 21138\n\nMy description:\nI have a lot of projects with 29.97fps (30000/1001) and those work correctly with Blender 2.9x but since Blender 3.0 all video clips are 1 frame shorter and my projects are a mess, because the frames in all clips are also shifted 1 frame !!\nIf I set the base to 1.0009 instead of 1.001 its all fine in the Timeline, but if I set 29.97 from the drop-down menu, all clips are 1 frame shorter and shifted.\nI have this also tested with videos without any audio and that makes no difference.\nThe audio length btw is alway correct.\nI also noticed that the trick with 1.0009 is not good, because this value is then transferred to the exported video and thats wrong!\n\nI think the problems in the following posts also have the same cause?\n[audio-is-1-frame-off](https://blender.stackexchange.com/questions/51650/audio-is-1-frame-off)\n[blender-3-0-vse-audio-and-video-out-of-sync-bug](https://blender.stackexchange.com/questions/250718/blender-3-0-vse-audio-and-video-out-of-sync-bug)\n\n", "blender3.4 alpha new eevee a rendering on the flashback\nOperating system:windows10 21h1\nGraphics card: amd 6800xt （22.7.1 driver opengl doubled the performance of a version)\n\nBroken: blender-3.4.0-alpha+master.ca172677b1a7-windows.amd64-release\nWorked: There is no version that can be tested\n\n\nScene any scene including cube, whether window rendering or f12, directly exit the software." ]

[ "\"Render Audio...\" does not always render keyframe transitions that have been placed in Volume, Pitch or Pan. \nOperating system: Ubuntu 18.04.03 LTS\nGraphics card: GTX 1060 6GB\n\n2.80.75\n\n\"Render Audio...\" does not always render keyframe transitions that have been placed in Volume, Pitch or Pan. \n\nWhen you set keyframes in volume, pitch or pan, it will animate the the audio transition in the preview. But, if you export that audio in the Render Menu, using the \"Render Audio...\" option, sometimes it will render the keyframed transition and sometimes it won't -- it is behaving erratically.\n\nThings that I have tried include clearing the cache with CTRL+R before I \"Render Audio...\". I have also tried setting the keyframes with \" i \" shortcut as well as clicking the animate property dot. Both seem to sometimes work and sometimes not work. \n\nI am rendering audio with the following settings:\n\naccuracy: 1024\nContainer: wav \nFormat: F32\n\n\n1) Import a video into the VSE\n2) Pick 3 frames in the audio strip and insert a Volume keyframe into each -- creating a transition 0, 1, 0.\n3) You will be able to hear the transition in the preview playback\n4) Go to Render -> \"Render Audio...\"\n5) Set Container to \"wav\" and Format to F32\n6) Mix it down and listen to it. \n\nrepeat this process 3 times, sometimes inserting keyframes with the \" i \" shortcut and sometimes using the animate properties dot. " ]

[ "Proposal for sequencer tool interactions \nThis task is intended to address design issues necessary for adding tool-system tools to the sequencer.\n\nCurrent state:\n\n- Immediately activating actions with keys operates on the selection.\n- The only tool that isn't selection (Blade), operates on the sequence strip directly under the cursor (not the selection).\n\nThe patch proposed to add the Slip tool, was also isolating the strip under the cursor, which I think is overly limiting since it means tools which behave this way can't operate on more than one item at a time. see: [D7063: VSE: Add slip tool](D7063)\n\n----\n\n## Proposes Solution\n\nTools should behave like the \"Tweak\" tool, unless there is a good reason not to *(The blade tool could be kept an exception - although cutting multiple strips vertically might be useful to support too)*.\n\n- A single click selects (with Shift-Click to toggle... etc).\n- A click-drag action runs the tool on the selected strips.\n\nThis means the Slip tool (in this case), would behave much the same as the tweak tool. Where you could quickly operate on many different sequence strips by clicking and dragging on them. With the ability to select multiple then click-drag on any one of them to operate on all strips.", "3D Cursor don´t take into actcount the face orenration with keyboard shortcut ( Shift + RClick)\nversion: 2.80 (sub 51), branch: blender2.7, commit date: 2019-03-25 00:55, hash: 07f6be87a97e, type: Release\nbuild date: 24/03/2019, 18:03\nplatform: Windows\n\n3D Cursor don´t take into account the Geometry orentation (topbar options ) with keyboard shortcut\n\n- Open blender and select 3D cursor tool\n- Set \"Geometry\" in the topbar 3D Cursor options\n- Use Shift + RClick to set your 3D cursor on top of default cube\n\nResult:\n\n3D Cursor don´t take into actcount the face orenration \n", "emulate numpad disables modifier keys on smaller keyboards.\nOperating system: Darwin-20.1.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.0.36\n\nBroken: version: 2.91.0 Alpha Also, 2.83.5\n\nShortcut CTRL-1 for mac not work (Subdivision Set) when emulate numpad is enabled.\nNo modifier key (ctrl, command) takes effect when used with number keys.\n\n- Turn off these four shortcuts for desktop switching in system preferences: \n\n- Turn on emulate numpad.\n- Press 1, change the view to some arbitrary view, press command 1, change the view to some another arbitrary view, press ctrl 1. \n\nMacOS 11 Beta\nBlender 2.91 Alpha\nSeptember 14, 23:31:19- 26a827f25448\nmacOS 64 bit\n\nPush the Control + 1 not work for Mac make Subdivision Set\nsubdivision_surface.html#keyboard-shortcuts\n\nYoutube: 9f-bVIP0xDE?t=158\nTime: (2:40) \n\"CTRL - 1\"\n\nFor Mac only Not for Windows.", "Support for binding additional keys\nThere are keys which aren't included in Blender's keymap.\n\nHowever it doesn't make sense for us to include all possible keys, as there are many which don't make sense (system-wake, calculator, eject, brightness-up, ... [see a full list ](keycodes)).\n\nRecently we have added some keys which can be useful.\n\n- Application key (used for context menu)\n- F20-24 (for users to have keyboards with additional F-Keys).\n\nThis task is to keep track of other possible additions to the keymap.\n\nOpen Topics:\n\n- How to handle non US keymaps?\n - We could support binding raw keycodes *(so we don't need to expand our fixed table of keys to include keys from all keyboard layouts).*\n - We could support keyboard layouts, which all include the US keymap, extending on it for keys it doesn't include. This could be selected as a preference.", "Implement Driver Workflow Changes\nFollowup task to #54653 to work on implementing the workflow changes proposed.\n(Note: This is currently a lower priority item than fixing bugs to get 2.8 into a usable state for Spring team. But, I'll be working on this when I get time). \n\nThere are the following sub-tasks:\n* ~~**Create operator for \"Open Drivers Editor\" functionality.**~~ c685c19df9\n * ~~Basic opening functionality~~\n * ~~Filtering support to get driven property under mouse at the time the \"active\" driver~~\n * Abstract out the \"Setup Drivers Editor\" and \"Show this channel\" functionality\n * Sub-editor mode for drivers in the mode selector\n\n* **Eyedropper support for clicking in 3D view and getting menu of common properties to drive, based on item under mouse.**\n * Basic object support\n * Investigate possibility of bone support too. (NOTE: Last time this was tried, it turned out being too complex to accomplish)\n * Restore cursor feedback when eyedropper is active (#55147)\n * Solve context/src button problems preventing eyedroppers from working in the popover\n\n* **Clean up drivers editor ui** - 57b47ebb28 (and followup commits)\n * ~~Add more space for expressions box~~\n * ~~Remove \"Show Debug Info\" checkbox - it's always needed~~\n * ~~Remove \"Update Dependencies\" button by making it redundant~~ - Should be ok now without out. It's still in the UI, but will be removed soon\n * Remove \"Use Self\"? Or rename?\n * Add optional display of useful hints about syntax for expressions and/or what can be used\n\n* **New persistent floating panel UI for editing driver settings**\n * ~~Basic layout~~ - 7e7680e33b - Use a modified version of the existing drivers editing panel, and make it a popover\n * ~~Floating panel~~ - 7a88a7742b - This makes the panel a popover. But, it doesn't stay open, or let you open the drivers editor\n * ~~Make floating panel stay open~~ - b11a1d5da2\n * ~~Get \"Open Drivers Editor\" button working in the popup (i.e probably missing button context info for source property)~~ - 1ff28c2650\n * ~~Get Copy/Paste dvar operator buttons working (currently always greyed out)~~ - 3e086af79c\n * ~~Fix issues where popover still goes away too easily sometimes~~ - Seems to be fixed with 17ee4836ab now. It may still happen, but it happens a whole lot less now.\n\n* **Reduce friction of adding new driver variables / setting up basic single-target drivers**\n * ~~Replace 'Add Drivers' Menu with Popover Panel ~~ - 4605e57b0f\n * Remove old (menu-based) operator\n * \"Mapping\" settings properties (see proposal)\n * ~~Make setting driver input-target easier~~ (i.e. no more need to change default expression first) - 9ab26bec27\n * Eyedropper for populating input variable settings (see above)", "Annotations (D) do not work with 3d cursor tool (keymap issue)\nMacBook Pro (Retina, 15-inch, Mid 2015)\n2.5 GHz Intel Core i7\n16 GB 1600 MHz DDR3\nAMD Radeon R9 M370X 2048 MB\nIntel Iris Pro 1536 MB\n\nBlender 2.80 Alpha 2\nHash: c94f806dc73\n\ndate: 2018-11-14 22:51\n\nAnnotation tool does not work when pressing D and LEFT MOUSE BUTTON.\n\nAnnotation tool will work when searching with CMD+F; but also within the search, if you click ENTER the annotation tool will pop up for a split second and disappear. \n\nAttaching a short video.\n[Annotation Bug.mov](Annotation_Bug.mov)\n", "Add-on preferences panel should open on activation\nBroken: 2.78 testbuild 1\n\n\n**Description of issue**\nAccording to the [new protocols for add-ons](Add-ons#New_Protocols), certain add-ons need more actions from the user than simple activation, before they do anything. This is an excerpt from the pie menu example:\n\n* With Pie menus, First you activate the addon & nothing happens!\n* You need to expand the Addons Preferences.\n* From here you can individually activate the menus you like to use. \n\nThis is bad UI design, as it requires the user to *know* that activating the add-on does nothing. Blender also requires them to click a button that doesn't appear any different than before (and thus doesn't visually indicate there is something else to see there now).\n\n**Possible solution**\nAutomatically opening the add-on's preferences panel when it is activated would help a lot. At least this allows the user to see that there are options to inspect, and possibly activate.\n", "Macro operators [e.g. Loop cut and slide]: \"adjust last operation\" fails completely [when called from the menu -- F9 is fine]\nBroken: 2.8x\nWorked: 2.79b\n\nThis might fall into the same boat as anything related to #45964, although it does seem to be \"new\" in 2.8x.\nAfter performing a loop cut and slide operator, you can adjust the properties in the operator panel (albeit with caveats from #45964). However, if you instead open the Adjust Last Operation panel, it will list a different operator name (Loop Cut, not Loop Cut and Slide), and while you can change properties there, those changes have no effect, even though they are reflected by the operator panel.\nThis didn't use to happen in 2.79b, though IIUC the \"Adjust...\" panel is different in 2.8x from the \"Redo Last\" of the 2.7x era.\n\n1. Load the default scene.\n2. Go into edit mode on the cube.\n3. Add a loop cut, e.g. via the shortcut or using the active tool\n4. Expand the operator panel in the bottom left and adjust properties. Note how those adjustments do have an effect on the result.\n5. Go Edit -> Adjust Last Operation\n6. Note the different operator name in that newly opened panel (Loop Cut vs. Loop Cut and Slide).\n6. Try adjusting any properties in the newly opened panel. Note how the operator panel in the bottom left picks up these changes, but at the same time they have no effect on the operation.\n\n[Demo video ](eAlL08M8AZA)", "Eyedropper in object selection box doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce 920M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nBroken: version: 2.83 (sub 17)\n\nBroken: version: 2.90 (sub 2)\n\n\nI click on a specific eyedropper and then it doesn't work. Other eyedroppers that I know seem to work fine.\n\n3D Viewport > Sculpt Mode > Top Header Panel > Options > Orientation > Eyedropper in object box selection > Click on it\n\n[Based on the default startup]\n\n[2020-05-17 13-21-02.mp4](2020-05-17_13-21-02.mp4)\n\n", "Enhance ways of accessing active modifier for poll functions of operators\nCurrently, poll function of operators can only get the modifier they are supposed to work on from the context. This is often missing (when called from shortcuts e.g., also with drag-n-drop of modifier panels...).\n\nThis is a sever problem for liboverrides, as some modifiers should then be edited (the locally added ones), and others not.\n\nI can see two ways to solve that: \n \n- Add current 'active' modifier to context (not sure how, or even if, this is always possible).\n- Work around the issue by adding some kind of second 'polling' helper function to be used from invoke/exec functions (since when not found in context, those use event to get the modifier to work on, but events are not passed to poll functions).\n", "Undoing 'create transformation orientation' makes selected transform orientation blank.\nLinux 64bit\n\nBroken: 2.72b, 2.71 (and lower?)\n\n\nCreating custom transformation orientation can be undone, but doing so will set transformation orientation dropdown in 3D view header to blank value.\n\n\n1. Create new file\n2. Run 'create transformation orientation' operator (ctrl+alt+space in default keymap): transformation orientation dropdown in 3D view header should change to show the name of newly created orientation\n3. Undo (ctrl+z): transformation orientation dropdown becomes blank.\n", "Segfault on unregistering operator/menu with open props dialog.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92, 2.93\n\n\nWhen an operator currently has a `wm.props_dialog_(self)` open, unregistering it will cause a segfault.\n\nThis only seems to happen reliably when the module it's from has at least one `bpy.types.Menu` subclass that's also been registered.\n\nThe displayed values of property fields in the dialog will sometimes flicker and switch values with each other for a split second before the segfault.\n\n\n[InvokeSegfault.blend](InvokeSegfault.blend)\n\n1. Open the attached file.\n\n2. Invoke the operator from the 3DView toolbar.\n\n3. Use a system hotkey (E.G. `ALT`+`TAB`) to switch to the window with the text editor space while leaving the props dialog open.\n\n4. Run the script again from the text editor window.", "Online Manual doesn't work for Panel Pin property\nSystem Information\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBlender Version\nBroken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: blender/blender@b292cfe5a9\nWorked: Was not working since 2.93 LTS, haven't tested lower ones, but I am pretty sure it is not working there as well\n\nShort description of error\nBlender Online Manual operator is not working for Panel Pin property, though it works for any other pinning property.\n2022-11-23 22-16-34.mp4\n\nExact steps for others to reproduce the error\n\n Open Sidebar (in any editor with Sidebar, shortcut {key N})\n Hover over panel header and press RMB -> You will see Pin property,\n press RMB in the Pin property to see it's context menu\n then press Online Manual or just press F1 key.\n\nNote that in the property editor the Online Manual works.\n\n\n------\n\nThis issue has been transferred from 102727\n\n", "Modal keymap for snapping in the `Corner Pin` widget has no effect\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nThe bottom bar states that pressing ^ will enable snapping, but it seems it does nothing.\n\n\n\n1. Create a new default file;\n2. Go to the compositor;\n3. Enable nodes;\n4. Add a viewer node (this allows you to resize and test different sizes for the `Corner Pin` Gizmo);\n5. Add a `Corner Pin` node;\n6. Edit the `Corner Pin` widget and try to snap.\n", "Eyedropper for props does not work in dialog boxes\nBlender 2.81, 71f2229b0d82\nfor example, in Texture Paint Context Menu\nI wanted to implement something using Operator and context.window_manager.invoke_props_dialog()\nThis is not a bug, but why not do it at the dialog level.\n" ]

[ "Flip Region operator is not discoverable in 2.90\nOperating system: Ubuntu 18.04\nGraphics card: NVIDIA titan Black\n\nBroken: 2.90 fd8d245\nWorked: 2.83\n\nNew search is not able to find Flip Region operator.\nIf you type Flip Region in it, it is not found.\n\nCalling this operator by search was the only way to do it with default keymap of previous releases and master.\nBecause of Region Overlap preference enabled by default, it is not possible to access Right Click menu relative to a region in 3DView operator.\n\nSo, if a new user wants to flip toolbar to right side, he will conclude that operator was removed or limited to Tool Settings bar and Header.\nBut it is not the case, user can still create a shortcut to flip toolbar and sidebar.\n\n( It would be appreciated to be able to flip Adjust Last Operation panels and navigation gizmos, too.\nAdjust Last Operation panel is taking space. \nIt would be great to be able to automatically fuse it in Sidebar when it is on same side or completely opened Toolbar like in 2.79.)\n\nPress F3 & type \"Flip\" in search." ]

[ "Line Art doesn't exclude object's instanced by geo node\nOperating system: Linux-6.0.6-76060006-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.3.1\nBroken: version: 3.5.0 Alpha\n\nCollection Line Art includes instances that are distribute my geometry nodes, even if that object is not within the Line Art target collection.\n\n\n[Line_art_Geo_Nodes_instance_bug.blend](Line_art_Geo_Nodes_instance_bug.blend)\n**Exact steps for others to reproduce with example file**\n1. Open Attached File \n2. Observe Line Art is on objects outside target collection\n\n**Exact steps for others to reproduce the error from Startup**\n1. Distribute Objects from a collection with Geo-Nodes\n2. Create a second collection with a Line Art Target Object only\n3. Add Collection Line Art and target collection from step 2\n4. Line Art will be drawn on Geo-Nodes instanced objects\n\n\n\n", "Outliner: Data API view can expand non expandable properties\nThe Data API view in the outliner let you click on the (invisble) expand arrow on non expandable properties.\n\nThis result in the property value to become invisible. You can click to bring it back, so I think it's only a display issue.\nNot all properties seems to be affected.\n\nBefore:\n\nAfter:\n", "Grease Pencil Blur makes a tight white line beteween to diferent GP Objects.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.6.0 Alpha\n\nWhen I use Blur effects on a GP object, it makes a tight white line between to different GP Objects. But, depends on which angle you look at, and this bug disappears.\n\n\njust added a blur effect on a grease pencil on render preview mod.\n\n", "Some Overlays are not rendered in Viewport Render (Text Info incl object name, Statistics, 3D Cursor)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.1\nAlso 3.1.0 Alpha\n\nUsing viewport render (or workbench) I'm unable to view object or empty names \n```\n(bpy.data.objects[\"NAME\"].show_name)\n```\n\nEnable show name on a visible object, and make a viewport render (bpy-ops-render-opengl)\nThe text isn't rendered in the image like it is in the viewport.\n\n", "GPencil: Randomize brush's 'Position' attribute doesn't work when camera is too close to Grease Pencil object\nOperating system: Win10 Home 64\nGraphics card: rtx3070\n\nBlender Version\nBroken: 2.93, 3.1.0\nWorked: N/A\n\nExact steps to reproduce the error:\n\n- Open file\n- try to use Randomize brush\n- Strength and Thickness work, but not Position \n- Switch to the other camera that's farther away from the GP object, and randomizing the position works fine.\n\n[randomize_not_working_close_NEW.blend](randomize_not_working_close_NEW.blend)\n\n\nwatch?v=4pTrEm5HqVU", "Grease pencil object in some cases look like low poly.\nOperating system: Linux-4.4.0-176-lowlatency-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 11)\nWorked: 2.82 (sub 7)\n\nIn some cases GP objects looks blocky, like a low poly objects.\n\nOpen attached file and render it.\nCompare render result with previous worked blender version.\n\n\n[2.83_bug.blend](2.83_bug.blend)\n", "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "GPencil: A layer used as mask for 2 or more other different layers makes the GP object partially unselectable in the viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.74\n\nBroken: version: 2.83.0 Beta\nWorked: /\n\nA layer (let's call it layer A) is masking more than one layer (B and C, for example; so B and C have in their \"mask(s) list\" layer A in it). Doing it makes the grease pencil object unselectable in the viewport unless you click on the shapes that have been drawn on layer A (or, at the precise point where the origin of the grease pencil is located, but only if the origin is displayed in the viewport).\n\nStrangely, saving with \"ctrl+S\" makes everything works as expected, but only until the file is closed. Opening it again and the problem is back.\n\nIn a concrete case scenario, it is a problem since if you use a layer as an invisible mask to hide strokes that go beyond certain limits, it makes it random to select the GP object (or forces to use the outliner).\n\n- Create a GP monkey\n- Create a new layer (layer A) that will mask the 2 already existing layers (\"Lines\" and \"Fills\")\n- In \"Lines\" and \"Fills\" layer, check the \"mask(s)\" option and add \"Layer A\" in each list\n- Back in \"Layer A\", draw a filled shape anywhere\nNow, in object mode you can only select the GP monkey by clicking on the filled form in layer A. You can invert the mask layer in the mask list of the layer named \"Fills\": It seems that it doesn't matter whether the masked parts are visible or not.\n\nBased on the attached .blend file:\n- Open file\n- Try to select the monkey by clicking on the part supposed to act as a mask (the \"selectable\" part in the screenshot)\n- Try to select the monkey by clicking in any other part of the monkey.\n\n{[F8563683](select_bug.png), size=full}\n\n[mask_selection_bug.blend](mask_selection_bug.blend)", "Extrude Edge Along Axis is not clearly visible in Blender 2.80\nOperating system:\nGraphics card:\n\nWindows 7\nGeForce GTX 650Ti\n\nblender-2.80-b4db7d80f18b-win64\n\n\nIn Blender 2.80 if you have just an edge and want to extrude that edge on side orthographic view along an axis, what you are extruding is not clearly visible. In Blender 2.79 i just have to scroll the mouse to zoom in and from that moment, even if i zoom out, the extrusion along axis will be clearly visible.\n\nJust extrude an edge in side orthographic along an axis and the edge being extrude will not be clearly visible even if you zoom in.", "Grease Pencil: various issues\n*Note: this tasks can be split up once we get feedback on issues, for now this is to discuss changes to make.*\n\n----\n\n\n- Brush pixels are not pixels,\n```\nshouldn't we use a meaningful value?\n(pixels or blender units).\n```\n\n- Grease pencil brushes have material pointers which are globally overwritten.\n\n```\nWhen you set a material, all brushes are looped over and have their material values clobbered.\n```\n\n```\nWhy have a material attached to the brush at all? This could be a scene level setting (or at least not stored per-brush).\n```\n\n```\nSee: `BKE_brush_update_material` called by rna `rna_Brush_material_update` when setting any material.\n```\n\n- Grease pencil sculpt uses it's own brush system,\n```\nis there a good reason for this?\n```\n\n```\nSince these brushes are fairly advanced (pressure & curve mapping options)\nwouldn't it be better to use the existing brush system?\n```\n\n *Note: while particle system for eg: has 'simple' brush types like this, grease-pencil sculpt brushes are more advanced and duplicate more of what we have for regular brushes used elsewhere.* \n\n- Grease pencil weight brush seems to have no way to paint a weight value (only add weight).\n\n```\nAs with mesh weight paint we should be able to paint a weight.\n```\n\n- In edit-mode, vertex selection exists but is hidden by default (0.0 opacity).\n\n```\nShouldn't they be visible?\n```\n\n----\n\n### Lower Priority\n\n- Internally grease pencil sculp is called:\n\n - grease pencil edit (`GP_BrushEdit_Settings`, `GP_EditBrush_Data`, `GP_BRUSHEDIT_FLAG_APPLY_UV`)\n\n```\nThis is highly confusing since we have grease pencil edit-mode, can't we rename these `GP_Sculpt*`. ?\n```\n\n - grease pencil paint (`GPENCIL_OT_brush_paint`)\n\n```\nPaint is easily confused with draw, seems this is for sculpt/weight painting.", "Fluid domain renders as the original object when particle mesh is momentarily disappear\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0\n\nIf there is no mesh generated from active particles within the domain, the frame will render with the domain as its original surface.\n\nI have an emitter object that periodically (cycles) emits fluid into the domain. At times when there is no mesh generated from particles in the domain the rendering is correct -- the fluid mesh:\n\n\n\nAt some point when there is no mesh generated particles inside the domain, the render is incorrect -- the surface coloring on the domain boundary:\n\n\n\nIn the attached file, I would know when I might start to include the Fluid Domain in the rendering, but it would be rather difficult to tell when there are no more particles if velocities or emissions are complicated with noise.\n\nHere is the [StackExchange ](fluid-simulation-gives-a-obscured-render-when-active-fluid-particles-are-absent) discussion and an example blend file.[fluid render problem.blend](fluid_render_problem.blend)\n\n\n\n", "Color Management / Use curves : Setting clipping option to Min = Max causes CRGB curves to go blank.\nWindows 10, GTX 1660\n\nBroken: Blender 2.82 release.\nBroken: Blender 2.83 daily update\n\nThis will recreate the black CRGB Curve display to go blank.\n\n1. In the Properties Panel, Select Color Management.\n2. Enable 'Use Curves'\n3. Select the 'Clipping Options'\n4. Set 'Max Y' to 0.00\n5. Now select anywhere in the CRGB curve display. It goes blank.\n", "Grease Pencil drawing sticks to Camera (when stroke placement is Surface and drawing outside of camera border)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nGrease Pencil drawing sticks to Camera (when stroke placement is Surface and drawing outside of camera border)\n\n[#92351.blend](T92351.blend)\n- open .blend\n- start a stroke inside camera bounds and end it outside camera bounds\n- stroke will stick to the camera on the end\n\n\n", "Can't resize node in visible bounds\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\n\nWhen trying to resize a node, the node cannot be resized if the mouse is precisely on the edge of the node\n\nAdd any node in shader o geometry node editor and try to resize the node with the cursor in the border line of the node\n<video src=\"attachment\" title=\"2023-07-11 14-28-46.mp4\" controls></video>\n\n", "3D Paint Mode stencil disappears when panning viewport.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 2.93.4\n\nWhen panning viewport in 3D paint mode with stencil mask enabled, the stencil mask disappears when moving the viewport, however does not disappear when zooming it, which indicates it's not a technical limitation.\n\n1. Enter 3D paint mode\n2. Enable texture mask, select some texture and set mapping to stencil\n3. Navigate the viewport\nResult: The stencil disappears when moving the viewport, which makes it very difficult to line up stencil projection with the 3D geometry\nExpected: The stencil does not disappear when navigating the view\n\n" ]

[ "Grease pencil strokes are partially/fully hidden behind reference image until released\nOperating system: Windows 10 Pro 19043.2130\nGraphics card: GTX 980\n\nBroken: 3.3.1\n\nDrawing over a reference image does not always show the stroke as it is being drawn, making it difficult to draw above reference. Using the images as planes addon as a temporary workaround.\n\nThe strange triangle shape shown in the video is pretty consistent. E.i. I can move the camera around slightly and as long as it's relatively head-on the exact same triangle shape appears while drawing. The shape is relative to the reference image. Panning the camera does not pan the glitched triangle area. Moving too much to the side makes it go from partial visibility in front of the ref until the stroke is finished, to no visibility at all in front of the ref until the stroke is finished.\n[untitled.bug_report.blend](untitled.bug_report.blend)\n[2022-11-26 20-52-01.mp4](2022-11-26_20-52-01.mp4)", "GPencil: Stroke not visible until the release of mouse/pen\nOperating system: MacOS 12.4\nGraphics card: M1 Pro\n\n**Blender Version** \nBroken: 3.2, 2.93\nWorked: not known\n\ngrease pencil lags and do not registers draw until the release of mouse/pen\n\nafter importing PNG image as reference image then grease pencil on top on it causes very bad lag\n[52a7925258d4b4c8d8f141e49068d281e65e19a5.m4v](52a7925258d4b4c8d8f141e49068d281e65e19a5.m4v)" ]

[ "Trembling when selected cube in edit mode\nOperating system: MacOS Sierra - Versione 10.12.6\nGraphics card: NVIDIA GeForce GTX 680MX 2048 MB\n\nBroken: 2.83.0 (2020-06-03), 2.90 (2020-06-12)\nWorked: 2.82a\n\nA strange flicker happens when I select the faces of the cube.\n\nI select the cube.\nI change the visualization in Edit Mode.\nI set select mode to Face.\nI select the faces of the cube but they do not remain selected instead, a strange flicker of the object occurs. Here a video example:\n\n[blender_283_bug.mp4](blender_283_bug.mp4)", "Regression: Crash with boolean modifier\nOperating system: Fedora Linux 36 (Workstation Edition)\nGraphics card: Nvidia Geforce RTX 3080\n\nBroken: 3.2.1, 3.3 alpha\nWorked: 3.1\n\nCrash with boolean modifier\n\n- Open .blend file\n- In boolean modifier tab -> select `dot cutter` for boolean operation\n[yin_yang-v1.blend](yin_yang-v1.blend)\noriginal file: [F13292564](yin_yang.blend)", "How to handle edit-mode face/edge select-modes without any face/edges.\nBased on this report #41562,\n\n----\n\nSimple example of the problem:\n\n- Add a Circle\n- Enter EditMode\n- Select Face Mode\n- Select All (AKey)\n- Grab *(Nothing happens)*\n\n----\n\nIf you have a mesh without faces in edit-mode and use face-select for example,\nQuite a lot of tools don't work usefully.\n*(same for edge select-mode on a mesh containing only vertices, but for purpose of discussion - just talking about faces for now).*\n\nLists of tools which fail when edges/vertices are selected but no faces exist.\n\n- Transform Grab/Rotate/Scale does nothing.\n- Extrude does nothing.\n- Inconsistent de-select-all verts and edges (AKey) - *(but border/circle/mouse select dont work).*\n- *...Likely others exist, off hand these are the ones I can find...*\n\nThere are some possible solutions.\n\n- Automatically switch out of face mode *(when entering edit-mode - doesn't solve problem completely since you can remove all faces while editing)*\n- Make tools support this configuration *(need to check how to support for each tool).*\n# Make tools report a warning when its not supported (or add support when it makes sense), *otherwise - assume users know what they're doing and not attempt to second-guess their actions.*\n\nFor this design issue, Id like to come to some agreement on a good way to handle this case.\n\n----\n\nSome things to consider regarding automatic select-mode switching:\n\n- Users may temporarily remove all faces, so changing select-modes automatic for the users could disrupt their workflow.\n- Switching modes automatically could break scripts (and generally give unpredictable behavior).\n- Checking if the mesh has faces isn't really reliable since you may have hidden faces which is like having no faces from the users POV.", "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "Unable to select certain vertices (regression from 2.79)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nSome vertices are impossible to select.\n\nAt first I thought it was because the vertices formed a concave area (see first file) but then I hit a second concave case (see second file).\n\n\nWithout rotating or zooming the view try to select one of the marked vertices in both files.\n[Select1.blend](Select1.blend)\n[Select2.blend](Select2.blend)\n\n----\n\n2.79 worked in this case, open this file in 2.79 to test.\n\n[Select1(1)_279.blend](Select1_1__279.blend)", "Mirror select doesn't select appropriate vertices where there are overlapping verts\nOperating system: Windows 10 Pro\nGraphics card: GTX 1070 + GT710 for extra outputs\n\nBroken: 2019-03-10 22:28\nHash 6fd11a21f5c5\n\n\nCtrl-Shift-M (or using the menu to select mirrored) doesn't select all mirrored verts where there are overlapping verts.\n\n\n[63Stingray.zip](63Stingray.zip)\n\nOpen blend file, hopefully it'll already be in edit mode with the appropriate vertices selected.\n\nShould look like this;\n\n\nFrom there select mirrored from either the select menu, or Ctrl-Shift-M, doesn't matter, and enable the following settings;\n\n\n\nObserve incomplete selection;\n\n\n\nThe area's of incomplete selection are here, where the overlapping underbody verts are in the same location as the verts for the body;\n\n\n\n", "Some transform modes don't apply absolute grid snaping \nOperating system: Windows 10 \nGraphics card: GTX 1080 ti \n\nBroken:\nBlender 2.8 January 31, 01:48:40 - 8c8979067490 Beta\nBlender 2.79 (It worked)\nBlender 2.77 (It worked)\n\nAbsolut grid snaping dont work with \"Face Inset\" and neither with loop cuts. \n\nTurn on the snaping (increment) -> turn on absolut grid snaping -> spawn a plane -> try to snap while loop cutting or inseting faces.", "Add modifier error message for attribute name clashes\nIf user has a UV and a vertex color groups with the same name things behave in non predictable ways.\n\nThe nodes modifier should check for this and add an error message when this happens.", "Edit-Mesh \"Select Next Active\" doesn't handle a wire edge loop (vertex mode)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nIt works with loop ,that surrounden by others, but can`t deal with single circle, when I am trying to select one per one.\nPlease watch video:\n[2020-01-17_19-06-34.mp4](2020-01-17_19-06-34.mp4)\n\n[untitled.blend](untitled.blend)", "Mirror Modifier On Cage Selection Papercut \nBroken: 2.93.4\nWorked: Maybe never.\n\nWhen in edit mode, using the \"On Cage\" option for the mirror modifier results in some unintuitive behavior when selecting vertices created by the bisect feature. The vertices created by the by the bisection are mapped to the original mesh data in a way that appears to be based on blenders internal representation of the mesh and not based on something observable to the user.\nThe behavior when selecting should feel consistent to the user. To fix this, I suggest that the vertices created by the bisection should always map to the vertices on the original mesh that are on the removed side of the bisection plane. This way users would be able to tweak the centerline of the mirrored mesh in while using \"On Cage.\" As it is currently implemented, there are vertices that affect the mesh that cannot be accessed through normal click selection unless \"On Cage\" is off.\n\n**Example**\n\n\nSelect the +X or -X face of the default cube and scale it by 0.5.\nAdd the mirror modifier and select bisect for the X axis so that the object is mirrored and bisected about the X axis.\nTurn on \"On cage\" for the mirror modifier then enter edit mode for the object.\nWhen selecting the vertices on plane X=0, you should notice that two of the vertices correspond to visible mirrored vertices and two correspond to vertices removed by the modifier. \n\nSimple scene showing the behavior. \n[MirrorSelectOnCagePapercut.blend](MirrorSelectOnCagePapercut.blend)\n", "Occasional render glitches when using simulation zones on an object without a material.\nThis bug has an easy workaround, mostly posting this so anyone running into the same issue knows the solution.\n\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.30.02\n\nBroken: version: 3.6.2\nWorked: N/A, 3.6 is the first version with simulation nodes.\n\nIn Eevee, rendering an object with a simple simulation zone applied in geometry nodes and no material assigned to the object results in some rendered frames being blank or displaying odd glitches.\n\nThe workaround is to simply assign a material to the object.\n\nCheck out the attached .blend file for reproduction.\n\n", "Exact Boolean (Union & Self Intersections -- to remove inside geometry) bad performance/memory footprint\nOperating system: Linux-5.15.0-67-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.2.6\n\nBroken: version: 3.5.0 Beta\n\nI have a group of nodes that gets rid of internal geometry by creating a \"mold\" of an object.\n\nBut it crashes on some meshes and not on other meshes and the crash doesn't give any real information why.\n\nIs there a work around for this?\nNodes works with certain meshes and crashes with others.\n\nWorking mesh and blend file.\n\n**Left side shows internal / overlapping geometry and Right side is free of this after using node network.**\n\n\n\n[doesn't crash.blend](attachment)\n\n\nCashes when I **click the switch node to enable it** (**see red arrow**).\nCrashes in 3.4.1 and 3.5.\n\n\n\n\n\n[this one crashes.blend](attachment)\n\nCrash text files attached below\n\n\nIs there a work around for this?\n\n", "Applying Subdivision/Multires Modifier De-merges UV's\n### Update\n\nThe issue of custom-data (UV's specifically) becoming detached remains, this problem existed before b88dd3b8e7, it was just less obvious since selection connected near-by UV's. Now UV's are merged by default at a very low threshold when applying modifiers to mitigate the problem. Keeping this report open as it would be good if subdivision-surface didn't separate UV's, replies to this report contain some notes that could lead to a solution. In practice users should not experience problems caused by this behavior, so marking low priority. ~ @campbellbarton.\n\n----\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha \nWorked: working in 2.90 \n\nCaused by b88dd3b8e7\n\nWhen applying a subdivision modifier, certain UV's points disconnect from their neighbors. This does not seem to occur with the F3 menu subdivide operation.\n\n- Open default blender scene.\n- Subdivide cube - 1 level and apply it. Do this step 4x\n- In the UV editor use \"Alt select\" to select face loops at random.\n- Alt click around until a face loop is not fully completed, this will reveal unmerged vertices.\n- Check area that did not complete by moving faces, vertices, edges etc to confirm unmerged UV's.\nThis does not seem to be an issue with the newly added 9a52b30cc0 in my eyes, rather an issue with subdividing.\n[UV Disconnect.blend](UV_Disconnect.blend)\n\n", "Connect failed in certain case\nWin8 64bit | GTX680 \n\nBroken: 2.71.6 a0b3604\n\nWhen select two vertices and press J to connect, it fails to add vertices to edges in between.\n\nPlease see the attached case for example. Thanks for checking.\n\n\n\n[vertex_connect.blend](vertex_connect.blend)", "Loop Cuts and Inset Faces cutting Meshes\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 750 TI\n\nBroken: 3.2\n\nTrying to add regular edge loops with Control + R, or even trying inset a face, they are cutting my mesh, or merging the ends. (I shared this on reddit, and it was suggested I create bug for it. \n\nAll I did was delete the bottom face of the mesh since I would not need it, but somehow I created invalid geometry and when I add an edge loop near the end it merges. If I try to inset the faces, it gives me weird end geometry.\n\n(This is what was noted from someone on Reddit: Update: just checked the file and here are my findings:\n\n```\n Adding a loop, be it length ways, long ways, or any other way seems to works just fine with the CTRL-R shortcut\n```\n\n```\n The loop cut tool also works just fine.. except if you try and loop cut around the XY plane instead of the XZ plane (drawing a line around the thinnest faces) at which point the mesh seems to collapse to zero height\n```\n\n```\n Insetting faces also works fine, be it via the tool or pressing I... but if you then try and extrude the inset suddenly the model collapses\n```\n\nOther things of note: the face orientation is inside out for this mesh (turning on Face Orientation in the Overlays menu (two overlapping circles in the header) shows them as red) and the object-level scale hasn't been applied. Fixing both of these doesn't correct any of the above issues -- although it IS normally advised since it prevents a few shading and modelling issues -- but it does, for some reason, change how the errors manifest, like the model collapsing in a slightly different way or the CTRL-R shortcut suddenly causing the same issues the tool version of loop cut and slide has.\n\nConclusion: you've somehow managed to turn this mesh into some form of invalid geometry that Blender can't seem to handle properly. You may wish to report it as a bug, including this file as a demonstration.\n\n- Open .blend file\n- enter edit mode and select face mode\n- press numpad 3 for YZ plane view\n- Add loopcut on visible face side (it'll merge the edges)\n\n---\n- repeat first 2 steps from above\n- press numpad1 for XZ plane view\n# select visible face -> extrude + scale (will merge edges). Works with inset tool\n\nTest File:\n[Issues Build2.blend](Issues_Build2.blend)" ]

[ "Boolean modifier mangles the mesh\nOperating system and graphics card\n\nWindows 10\nNVidia GeForce GTX 1060\nMSi Dominator GT62VR laptop\n\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\n\n2.78a, 2.79, blender-2.79.0-git.a8f11f5-windows64\n\nWorked: (optional)\n\n\nWhen performing a boolean operation, sometimes it drops faces, creates vertices where there should be none, and generally mangles the output mesh. I was able to reproduce one of the problems with a very simple test scene. In this test scene, there is a box cut out of a triangular box object. The cutout looks successful as far as vertices go, but the inside face is not filled so it creates non-manifold edges.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n\n[BooleanFuckupExample1.blend](BooleanFuckupExample1.blend)\n\nThe object \"InfillNegative\" has a Boolean Difference modifier for the hideen \"ToeCutout\" object. There are two missing faces where the \"ToeCutout\" object has been subtracted, leaving a non-manifold \"InfillNegative\" object.", "BMesh boolean fails with zero area faces\nLinux 64\n\nBroken: 5b33115\n\n\nHere's a heavy boolean construction that currently fails at many points. Feel free to enable bmesh boolean in any modifier and notice the differences :)\n\n[BMeshBoolean.blend](BMeshBoolean.blend)\n\nSimplified example with 3d cursor located at root-cause:\n\n[BMeshBoolean_zero_area.blend](BMeshBoolean_zero_area.blend)\n\n[BMeshBoolean_zero_area_animated.blend](BMeshBoolean_zero_area_animated.blend)\n\n----\n\nUpdated for 2.9x [BMeshBoolean_zero_area_animated_290_update.blend](BMeshBoolean_zero_area_animated_290_update.blend)" ]

[ "Crash opening file using Clump Curves on Particle Children \n****\n\nversion: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: f1aa4d18d49d, type: Release\nbuild date: 2019-12-04, 14:30:40\nplatform: Windows\n\n***********************************************************\n\nWhen I worked on a project using particles, after a short break I wasn´t able to reopen the project. The project crashed right after opening. When starting Blender from console the only error I could find was:\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF706DC271E\n\nno Blender log file was written!\n\nEven in debug mode there were no more hints but his one. I opened the project in an Ubuntu VM and it also crashed there. No chance to recover the file.\n\n\nUsing Particle following a nurbspath with Force Field \"Curve\".\nParticles rendered as objects.\nUsed Simple Children.\nWhen ticking the box: Use Clump Curve it crashes.\n\nEither Blender crashes right after ticking the box or when reopen the project. The latter then means that I´m not able to recover my work at all.\nI might have to do with particles already baked or not. Not sure. \n\n[T72763_crash_log.txt](T72763_crash_log.txt)\n\nfile written from c2a37867f2 that crashes on file read:\n[#72763.blend](T72763.blend)\nfile written from 2.79b that crashes on file read:\n[T72763_279.blend](T72763_279.blend)", "Segfault pasting stale driver.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92\n\n\nDrives copied and pasted with significant change in file data in between can trigger segfaults. \n\n```\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nblender(BLI_system_backtrace+0x34) [0x55dfd70fd084]\nblender(+0xe151bd) [0x55dfd4bd41bd]\n/usr/lib/libc.so.6(+0x3cf80) [0x7f9b26870f80]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder26build_object_data_geometryEP6Objectb+0x170) [0x55dfd7000380]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder17build_object_dataEP6Objectb+0x54) [0x55dfd6ffb4b4]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x1d3) [0x55dfd6ffe2c3]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder22build_driver_variablesEP2IDP6FCurve+0x77) [0x55dfd6ffad87]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder14build_animdataEP2ID+0x1f9) [0x55dfd6ffe8b9]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x228) [0x55dfd6ffe318]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder16build_view_layerEP5SceneP9ViewLayerNS0_26eDepsNode_LinkedState_TypeE+0xb2) [0x55dfd7003892]\nblender(_ZN7blender3deg23AbstractBuilderPipeline16build_step_nodesEv+0x76) [0x55dfd6fea296]\nblender(_ZN7blender3deg23AbstractBuilderPipeline5buildEv+0x42) [0x55dfd6fea4b2]\nblender(DEG_graph_build_from_view_layer+0x33) [0x55dfd6fd24e3]\nblender(+0xef501a) [0x55dfd4cb401a]\nblender(wm_event_do_depsgraph+0xc5) [0x55dfd4f59245]\nblender(wm_event_do_refresh_wm_and_depsgraph+0x92) [0x55dfd4f593b2]\nblender(wm_event_do_notifiers+0x36a) [0x55dfd4f6055a]\nblender(WM_main+0x2b) [0x55dfd4f5532b]\nblender(main+0x367) [0x55dfd4b9da67]\n/usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f9b2685bb25]\nblender(_start+0x2e) [0x55dfd4bd056e]\n\n# Python backtrace\n```\n\n\n* Add a custom property to the Scene.\n\n* Right click on its value field, and run \"Copy as New Driver\".\n\n* Run `CTRL`+`N` or \"File\" —> \"New\" —> \"General\".\n\n* Right click on any value field, and run \"Paste Driver\".", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "GPencil: Selecting textured brushes will crash Blender\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92.0\n\nWhen appending the textured brushes from the [Blender Cloud](5ccfe64353b85e279cf72acd) into a file, Blender will crash when trying to preview the brushes in the tool settings.\n\n\n - Open Blender 2.93 and select the \"2D Animation\" template.\n - Go to *File*>*Append* and browse to the `pepeland_GP_brush_pack_V1.blend` file. Go into the *Brush* folder and append the brushes `GBrush_001` through `GBrush_010`.\n # Click the brush icon in the tool settings. Blender crashes.\n\n\n\n", "Screen flickers / goes black/ red when starting up Blender in fullscreen via startup file.\nOperating system: macOS Big Sur 11.0.1\nGraphics card: Radeon Pro Vega 48 8GB\nProcessor: 3.6 GHz 8-Core Intel Core i9\niMac (Retina 5K, 27 inch, 2019)\nMemory: 72GB 2667 MHz DDR4\n\nBroken: Blender 2.83.9, 2.92 alpha `ba740ad2abc6`, 8dc95f61f3\n\nThe screen flickers/ goes black/ goes red for about 2-3 seconds if the startup file was saved with Blender in full screen. Opening the startup file's again after Blender becomes usable doesn't cause this.\n\n\n- Delete the 2.83 config file or start from Factory Settings\n- Start Blender and the splash screen is displayed correctly\n- Now Click the Green button at the top left hand corner to Maximise the screen to full\n- Save the Default Startup File\n- Reopen Blender and the screen turns red apart from the header bar which is displayed correctly\n- The screen stays red for about 3 seconds\n# The splash screen is now displayed correctly and I can use Blender so far without any issues\n\nRestarted the iMac and restarted Blender with the same red screen error as above\n\n**Workaround**\nPress the Green Button so that Blender is not maximised anymore\nSave the Default Startup File\nRestart Blender and the splash screen is displayed (without the red screen)\n\nThis is my first bug report, so I hope I have filed this correctly.\n\n\nKind Regards,\n\nClayton", "Crash on Changing Repeat value to -1 in Corrective Smooth modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 2.93.5\n\nNot Responding when I change the Repeat value to -1\n\n{[F11810617](image.png), size=full}\n\n", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "2.9.1 Close without error message\nOperating system: Windows 10, 10gb ram, ssd\nGraphics card: Nvidia GTX 650 1gb vram\n\nBroken: (2.83 LTE and 2.90 current available version)\nWorked: (2.82)\n\nWhen rendering with GPU AND CPU, the app crashes, works perfectly fine on CPU only. On GPU only too but slower than older versions.\n\n\n```\nblender.exe :0x00007FF7A5B76440 ccl::kernel_cpu_sse41_filter_finalize\nblender.exe :0x00007FF7A57A9220 ccl::CPUDevice::denoising_solve\nblender.exe :0x00007FF7A57DA470 ccl::DenoisingTask::reconstruct\nblender.exe :0x00007FF7A57D8ED0 ccl::DenoisingTask::run_denoising\nblender.exe :0x00007FF7A57A7240 ccl::CPUDevice::denoise_nlm\nblender.exe :0x00007FF7A57AB590 ccl::CPUDevice::thread_render\nblender.exe :0x00007FF7A57ABA30 ccl::CPUDevice::thread_run\nblender.exe :0x00007FF7A57A60B0 ?_Do_call@?$_Func_impl_no_alloc@V<lambda_d884e08a7877f415f05ce8ffda8f97b4>@@X$$V@std@@EEAAXXZ\nblender.exe :0x00007FF7A7D5F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5EF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFBF5EFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFC08611FA0 o_exp\nKERNEL32.DLL :0x00007FFC0B647960 BaseThreadInitThunk\nntdll.dll :0x00007FFC0B7AA250 RtlUserThreadStart\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "Evee crashes when rendering \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.3\n\nRendering this file with evee causes a crash. Cycles is able to render the file.\nThe mesh was originally created in blender 2.6x with blender internal textures down loaded from blend swap 6618\nI was updating the textures for 2.9.3. \n\nRender the image.[crash.txt](crash.txt)\n\n[debug.blend](debug.blend)\n\n", "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n", "Blender GUI freezes when using activate_init = True\nOperating system: W10 64bit\nGraphics card: nVidia GTX 970\n\nBroken: blender-2.83-71b1ee940bb0-windows64\n\n\nOnce this bug T71112 was fixed I tried to \"use activate_init = True\" in my addon, but I'm still getting Blender GUI to freeze.\n\n* Open up [bugreport.blend](bugreport.blend) and run the script in Text Editor\n* Search for \"Name Location\" operator and run it\n* Type a text and hit OK. An Empty object is placed into the scene, named by what you typed in, but whole GUI becomes unresponsive.\n", "Regression: Crashes when uses preview or final render modes\nOperating system: Mac Os Monterey 12.6.1\nGraphics card: AMD Radeon R9 M380 2 GB\n\nBroken: blender 3.6.2\nWorked: Blender 3.4.1\n\nBlender 3.6.2 crashes on MacOS when you change between preview or final render modes. I Think is a problem related with the Realtime Viewport compositing. I think it is not enabled at all on MacOS but maybe developers did not do it correctly and some render features are requesting missing elements.\n\nSimply make 3 or 4 render previews and then press F12 to obtain a final render (or viceversa). Blender Crashes immediately.\n\n", "Factory reset does not reset data for add-ons\nSystem Information\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03\n\nBlender Version\nBroken: version: 4.0.0 Alpha\n\nShort description of error\n\nConfigurations of addons are not restored when calling factory reset.\n\nSee video for demonstration:\n\n", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n" ]

[ "Crash in icon_preview_startjob_all_sizes()\nOperating system: Linux-5.4.0-7634-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.92.0 Alpha\nWorked: Probably before e3068f38c8c8df8cf, or at least a couple days ago.\n\nI crashed when running Menu Search. Disabling the Blender Cloud addon stopped this. Enabling the Blender Cloud addon causes the same crash:\n" ]

[ "Weird Tab and redraw behavior in color popup\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA TITAN V/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.27\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93 has weird Tab behavior, but not redraw artifacts\n\nTab and redraw is not happening correct for RGBA color wheel popup. Almost as if sliders from different modes are drawn on top of the active ones.\n\n\n1. blender --factory-start\n2. World buttons\n3. Click on the Color to open color wheel popup\n4. Switch to RGB\n5. Click on the first slider (R)\n6. Start hitting Tab and see what happens with the values in the sliders (takes 4 times to tab from Blue channel to Alpha)\n\nIf you type values in the sliders things gets even more confusing.", "Linked Instances Across Scenes have unreliable updates when editing their common mesh data.\n\nBroken: 2.93.4 LTS;\nBroken: master\n\nWith two different objects in two different scenes sharing a same obdata Mesh, editing the mesh in one of the scene can fail to properly update object in the other scene.\n\n- Open attached file.\n- Go to scene 2.\n- Switch to Edit mode.\n- Assign the red material (first slot) to the cube in edit mode.\n- Switch back to Object mode.\n- Go to Scene 1, the Cube in Scene one still uses the second slot material (green).\n# Switch to edit mode and back, now the cube is shown with expected first material slot (red) as well.\n\nNOTE: If you replace step 4 by a mesh geometry editing (e.g. rotate the mesh in Edit mode), in current master there is the same missing update issue in Scene 1, but in 2.93LTS it is properly updated... Regression introduced by 51568030e9.\n\n[Example.blend](Example.blend)\n\n------------------------\n\n# Original report\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.0\n\nIf you link an instanced object to another scene, having it's material link to object, it can have a different material from the non-instance. However upon saving and re-opening the scene, the instance's material will revert to that of the non-instance. \n\n- Open attached file or\n - Take the default cube and assign a material to it. In the viewport display settings assign a color for the material, this will give feedback in the viewport to highlight the issue. \n - Create another material on the same cube and once again assign a color in the viewport display settings.\n - Set both materials to Object Link in the material properties. \n - Name the current scene \"Scene 1\" and proceed to create another scene named \"Scene 2\".\n - Return to Scene 1, and using Alt+D instance the cube.\n - Using Ctrl+ L, link the instance to Scene 2. Delete the newly created instance in Scene 1.\n- In Scene 2, assign the instance a different material than Scene 1 in edit mode. You now have 2 scenes, with 2 cubes that share mesh data, but that are using 2 different materials. This is the desired goal in practice.\n- Save the file and re-open it. Blender will have automatically assigned both cubes to 1 material.\n[Example.blend](Example.blend)\n", "Cleanup: Explicit Colors\nAnnotating colors in `BLI_color.hh` with the goal that it becomes more clear in the code what color and alpha association is used.\n\nSee proposal-explicit-colors/\n\n- Changes to BLI_color.h + migration of existing code (Function + Geometry nodes): [D10978: Blenlib: Explicit Colors.](D10978)\n- Compostor: Is already CPP and some operations use color space conversions.\n- Color picker: There is an effort to move more UI code to CPP Color picker is one that would benefit in readability.\n- Draw manager: Although this is in limited places.\n- Blenkernel: blenkernel (colorband, gpencil, image_gen, studiolight) seems like small tweaks.\n", "3D Texturing: When changing the texture resolution, the pixel data isn't recreated\n* Start painting\n* Change image resolution\n* Continue painting.\n\nWe have a safe guard for this, but it doesn't seem to work anymore.\n", "Scene update bug\nSystem Information\nwindows7 64\nASUS ATI Radeon HD6870\n\nBlender Version\nBroken: (All)\nWorked: (None)\n\n\n\n\n\n\n\n\nopen this file, select plane and try to select for this plane any mesh - all this meshes don't have users, but was saved, try to select material - materials was saved, but don't have users, \nwe can revert, close and open again many times - materails and meshes will be saved.\ntry to add gruop instance - we will have all this groups is empty.", "Support Scenes Overrides\nCurrently Scenes liboverrides are not really working, changes to its master collection will be lost, resync of scene itself is not possible when the override is the active scene, etc.\n\nSee e.g. #89963 (crash when library override is applied to an object)", "Texture Paint - bad behaving operator \"Save All Images\"\nGo to Texture Paint Mode with some Textures loaded. In T-Panel go to the Slots Tab. There you will find a Button labeled \"Save All Images\". However, do not push this Button !\nThis Button overwrites all involved/edited Textures in the Texture Paint Slots at once and instantly, without further inquiry, to the directory of the origins.\n\nIt's not a bug, it's working pretty well !\n\n \n", "EEVEE-Next: Refactor renderpass storage\nCurrently render-passes are allocated in multiple texture buffers.\nThey take a lot of binding points and currently prevent the deferred pipeline to output diffuse color correctly.\n\nThe plan is to combine all render-passes into the same array texture and use an associated UBO containing offset to the layer of each pass type.\n\nThis would very similar to the AOV support.\n\nAnother direct benefit of this would be that the GBuffer encoding could be simplified.\n\n", "Shader compilation is crash\nOperating system: Linux-6.3.0-1-MANJARO-x86_64-with-glibc2.37 64 Bits, X11 UI\nGraphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 23.0.3\n\nBroken: version: 3.5.1, 3.6.0\nWorked: 2.93.17, 3.3.6\n\n\nI am creating a shader and I need to use a lot of color mix node:\n| Version | Result |\n| -- | -- |\n| 2.93.17 |  |\n| 3.3.6 |  |\n| 3.5 |  |\n\n\nLaunch attached blend in different the Blender versions", "Theme > Shader Editor, Sidebar > Alpha value does not work\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A3000 12GB Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.1\n\nIn side of the Shader editor, if you want to change the color works correctly, but if you want to change the Alpha value, is not working.\n\nGo to Preferences > Themes > Node editor > Theme space > Region Background\n\n", "Cycles shading glitch\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.4.1\nWorked: ?\n\nCycles shows incorrect shading, also different from Eevee. (The file is very simplified just to showcase the problem)\nI'm thinking it is a variation of T99933 bug but not sure so tell if that's the case\n\n[bug.blend](bug.blend)\n1) Open the file, switch to rendered view. Normals should look like this\n\n2) In the material disconnect the alpha socket, now it should look different.\n\nIs alpha supposed to affect normals at all?\n3) Repeat the same in Eevee, results look consistent", "Vector pass not being saved correctly when using the File Output node\nOperating system: Win 10\nGraphics card: RTX 3090\n\nBroken: 3.3\nWorked: Not sure\n\nAccording to doc, vector pass is a 4-component vector, but when it's being piped through to a File Node in the compositor, it seems only 3 components are saved. This causes some motion data to be missing in the final multilayer exr.\n\n- Open attached file\n- `Render` > `Animation` - it will render 1 frame and save 2 exrs.\n 1. One using the blender native file output\n 2. Another using the file Node\n\n- Once it's rendered, the compositor should auto update to load these 2 exrs files below. If not, refresh the input nodes.\n- Check the vectorblured output. They are different.\n[mblur-bug.blend](mblur-bug.blend)", "Invisible color picker in the preferences menu\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\n\n**Short description of error**\nDepending on your position in the preferences menu the colour picker becomes invisible\n\nDepending on your position in the themes menu (preferences/themes), the colour picker may be above or under the setting you want to change, but there is a specific position in which the colour picker becomes invisible. This bug only occurs if there are multiple settings above, at least one submenu open and you edit one of the settings in the middle. E.g. \"Inner\" and \"Inner selected\" in the user interface section. The colour picker is not only invisible but also not functioning. The \"RGB\" and \"HSV\" sliders work as well as the \"HEX\" section.\nClosing the picker and scrolling down the page, only by a single line (up or down) fixes the glitch, also resizing the window works. \n\nBased on the default startup\n\n", "Shader editor material name on title bar doesn't follow pinned material\nBlender 3.5.1\n\nAs you can see on the screenshot it's displaying material \"Material\" when current node tree is for another material (you can distinguish it by the different base color).\n\nWay to reproduce:\n\n- open attached blend file\n- run the following code in python console\n\n```python\nshader_editor = bpy.data.screens['Shading'].areas[3].spaces.active\nshader_editor.pin = True\nshader_editor.node_tree = bpy.data.materials['Second_material'].node_tree\n```\n\n\n", "Unexpected behavior when applying Geometry Nodes modifier on top of the Multires.\nThis is a more comprehensive report on a bug that was recently posted and closed [HERE ](T97603)\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1+\n\nApplying Geometry Nodes on top of the Multires modifier does not give expected results. Multires is an exception from the \"Applying a modifier will apply it as if it was first in the stack\" rule, when a modifier is applied on top of the Multires, the mesh changes will be applied to the currently visible subdivision level. Quick video below.\n[Multires GNodes Bug.mp4](Multires_GNodes_Bug.mp4)\nAnd the Example .blend file > [Multires GN Bug.blend](Multires_GN_Bug.blend)\n\nHow should applying the Geometry Nodes behave ? When the Geometry Nodes modifier doesn't change the vertex count and simply deforms the mesh, it should behave just like any other modifier, see example video with the Shrinkwrap modifier. \nSo what when Geometry Nodes does change the vertex count ? I say we keep the same behavior that solidify modifier has, it skips Multires and applies it as it would be first in the stack. While of course this will bring broken results, this is a already an existing behavior so i think it would be completely fine.\n\nSeries of images presenting how applying a Solidify modifier on top of Multires behaves. (Intended behavior)\n\n\n\n\n\n\n\n" ]

[ "Node Editor: value stuck after setting a keyframe and clearing clearframes again\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken: 2.80 Beta, 893fa598319e, blender2.7, 2019-02-24\nWorked: 2.79\n\nWhen adding the vector mapping to an image texture using the Ctrl-T shortcut from node wrangler, the mapping node added doesn't not behave like mapping nodes added with Shift-A. \nUpdate (@lichtwerk ): this is apparently unrelated to NodeWrangler, but instead can be reproduced by setting a keyframe on a node on clearing keyframes again...\n\nLeft click the X scale and drag down to select the Y and Z values. Type a new number and press Enter.\n\nExpected: All 3 values should be updated with the new value, as they are in a Shift-A added vector mapping node.\n\nActual: Only the first value gets updated." ]

[ "Rigid Body Constraint - Generic Y axis problem\nOperating system: Windows 10\nGraphics card: Gigabyte RX 590 gaming x 8 gb\n\nBroken: 3.2.0\nWorked: I don't know. I haven't tested in previous versions.\n\nWhen using \"Rigid Body Constraint - Generic\", a problem occurs when I restrict rotation in the y-axis. When I try other axes they are fine. I haven't tested this on other versions. Or I'm causing the physics to be miscalculated, I'm not sure. I leave the file below;\n\n**Steps to Reproduce**\n- Open .blend file\n- Play animation\n[Rigid Body Constraint - Generic.blend](Rigid_Body_Constraint_-_Generic.blend)\nVideo: [F13411735](2022-08-22_21-41-37.mp4)", "Remesh Voxel Size can be much to small by default (leading to crashes). 'Edit Voxel Size' operator can have wrong range\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\nProcessor: AMD Ryzen 7 3800x 8-Core Processor 3.90 GHz\n\nBroken: version: 2.90.0 Alpha\n(Also with Blender 2.83 BETA)\n\nSelecting the \"Remesh\" modifier, selected \"Voxel\", Voxel size below \"0.01m\" = PC Crash. Needed to restart the PC.\n\n1. Start Blender.\n2. Let the default Cube alive and add the \"Remesh\" modifier.\n3. Make the \"Voxel Size\" below \"0.01m\".\n4. Did it crashed?\n(Found out in my Blender Project, but I tested it then in a default Scene. Same thing happened.)\n\n(Why I set the Voxel Size below \"0.01m\"?\nIt happens accidentally, when I have it like \"0.42m\", but I hold my left click and slide it to the left, so I accidentally go below \"0.01m\".)\n\n{[F8619727](image.png), size = full}\n\nGood Luck!\n", "Sculpt crash in certain scenario (PBVH vert number does not match)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 2.93.6\n\nCrash upon altering the model in any way.\n\n1. Open file\n2. Use a tool/brush to alter the model.\n3. Instant Crash\n\nI have updated GPU drivers and the latest Blender version as of today, still crashes.\n\nCould not find any duplicate bugs of crashes when interacting with models, only crash on startup and others. \n\nI expect my GPU is just too trash.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Goblin.crash.txt](Goblin.crash.txt)\n\n[Goblin.blend](Goblin.blend)\n", "Boolean modifier produces unexpected result\nOperating system: Debian bookworm / sid\nGraphics card: Intel WhiskeyLake-U GT2, but most likely doesn't matter\n\nBroken: 3.3.1 (from Debian), 3.4.1RC (Daily Build from blender.org, b87bcd3f8fe1), 2.93.12 RC (Daily Build, 1f30e…)\nWorked: unknown\n\n\nIteratively generating the difference between a mesh (in this case a plain torus) and a rotated version of its copy seems to work fine initially but results in broken meshes after a few steps. Artefacts include non-manifold bits and pieces of the original mesh, or a DIFFERENCE step that ends up adding the mesh that it just subtracted to the result.\n\nAlso discussed at 1427102 (page contains images showing said broken results).\n\n[problem.blend](problem.blend)\n\nInspect file above.", "Cycles rendering artifacts with fluid particles + Vector pass (missing particles)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nSections of fluid particles are missing when rendering in cycles.\nThe issue occurs when you enable the vector render pass.\nThere are no issues when rendering in the viewport, only during the final render.\nThe parts that are missing changes every frame.\nIt also happened on the same computer with a different graphics card (RTX 2060). \n\nViewport render\n\ncycles render\n\nrendered only the particles\n\n\n- Open attached file\n- Bake fluid simulation data and particles\n- In {nav View Layer Properties > Passes > Data} enable `Vector`\n- Render scene\n\n[FluidSplash2.blend](FluidSplash2.blend)\n\n", "GPencil: Fill tool Ignore Transparent strokes setting broken\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Beta\n\nFill tool not ignoring transparent strokes when the settings is enabled. When you enable Show boundary lines, it shows that transparent strokes are not a boundary but the fill still uses them as boundaries.\n\n- Open attached file and try the fill tool. Under the Advanced menu 'Ignore Transparent' and 'Show Lines' are enabled.\n\n", "`bpy.context.space_data.overlay.grid_scale` returns inconsistent view3D grid scale in multi-view\nOperating system: win 10\nGraphics card: RTX 3090\n\nBroken: This was observed in 3.5 alpha but I don't think that is relevant \nWorked: N/A\n\n`bpy.context.space_data.overlay.grid_scale` does not apply to multi-view functionally, and any interaction with the 3D navigation sphere only effects the main window portion of multi-view.\n\nSee attached video for a demonstration of some of the odd behavior.\nSee attached blend to reproduce the error.\n\nEnter multi-grid view: **ctrl+alt+q** (mismatched transform grid) The main window is top right.\nClick any axis sphere in any 3D view that isn't the top right quadrant, only the main window transforms.\nYou will also notice that the main window also inherits the grid scale of the multi-view windows.\n\nPlaces to look maybe? [A](overlay_grid.cc#L86) [B](space_view3d)\n\n", "Discrepancy between CPU and GPU rendering/material behaviour\nOperating system: macOS 13\nGraphics card: AMD W6800X Duo MPX module\n\nBroken: 3.3.1 (latest full release)\n\nI bought some assets which render with weird artefacts with the GPU, but work fine with CPU.\n\nThe assets are made by Bproduction (Florian Benedetto) on Blender Market. They are trees and vegetation models, which can be used individually or with Scatter 5.3. Simply put: they render properly with the CPU (Mac Pro, 24-core Intel), but render with horrible artefacts using the dual GPU. This doesn't happen with any other assets or materials I have.\n\nThe images below show the issue. I believe it's something to do with the material setup, but in any case it should render properly under both systems. Maybe it's an issue with macOS drivers?\n\n\n\n", "Bump map isn't generating bump from ambient occlusion height input\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 2)\nWorked: (optional)\n\nbump map isn't generating bump from height input\n\nSee screenshots and then open file to see configuration:\n\n[ambient occlusion to bump map bug.blend](ambient_occlusion_to_bump_map_bug.blend)\n\n\n\nThe mask generated from the ambient occlusion:\n\n\n\n\nThe normals generated by the bump node:\n\n\n\n\n\nThe result (no bump):\n\n", "Mantaflow 'Dissolve' broken for Flame smoke\nOperating system: Win 10 64bit\nGraphics card: Dual Titan RTX\n\nBroken: 2.83 2020-02-24 a322b43e3d08\n\nEnabling 'Dissolve' in Mantaflow Gas with any emitter producing fire, will completely disable the smoke normally produced by the fire.\n\n\nSet default cube to a Fluid>Gas>Domain\nCreate a plane inside. Set to Fluid>Flow, and set the flow type to Fire.\nIn the domain settings, under Smoke set the Dissolve to 150.\nThe fire will render, but there will be zero smoke.\nDownload Attached Blend: [bug_dissolve.blend](bug_dissolve.blend)\n\n\n\n\n\n\nThe correct functionality would be for the smoke to dissolve from the time of it's birth - not of the emitter, but when the flame created it. \n\nThis is crucial to achieving realistic explosions, as the smoke looks patchy due to the varied times it was created from the flames.\n\nReference video of real explosion. Note how the smoke looks patchy towards the end:\n[Gas_Explosion_7_1920.mp4](Gas_Explosion_7_1920.mp4)", "Mantaflow liquid collisions not working properly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.90.1\n\nUnless a liquid collision effector's Surface Thickness is set to at least 0.5 or set to \"Is Planar\" it is not used.\n\nI reference two examples for liquid and smoke+fire [examples ]] and there are several issues logged in [[ https:*blender.stackexchange.com/search?q=liquid+collision | Blender stackexchange ]], along with my [[ 111042 | investigation ](http:*optionpeer.com/jimtpersonal/collisions.zip).\n\nA collision effector is ignored unless Surface Thickness is set to at least 0.5 or set to \"Is Planar\". However as [docs ](effector.html) state Surface Thickness is \"Additional area around the effector\".\n\nIn my first example \"liquid collision.blend\" the results (show in \"liquid collision.png\") shows how the extra Surface Thickness effects the liquid that becomes more confined in the container, whereas setting it to less than 0.5 will cause the liquid to fall through the container.\n\nThe same is true in the \"muzzle*.blend\" file where the flash & smoke comes through the collision object unless Surface Thickness is set (incorrectly) to at least 0.5\n\n[liquid collision.blend](liquid_collision.blend)\n[muzzle flash no projectile.blend](muzzle_flash_no_projectile.blend)\n", "Non animatable properties\nBroken: version: 3.3.0 Alpha\n\nWorking on refreshing the in-built AnimAll addon by adding the latest properties supported in Blender.\n@ideasman42 asked me to file a task\n\nCertain properties are missing animation capabilities:\n\n - Lattice Vertex Groups\n - Mesh Vertex Creases", " Freestyle renders extra lines\n%%%--- Operating System, Graphics card ---\n1st PC: Win7 64bit & Quattro 2000\n2nd PC: Win7 64bit & Nvidia 560ti\n\n\n\n - Blender version with error, and version that worked ---\n2.68a\n\n - Short description of error ---\nFreestyle produces lines through objects as they are transparent\nI build a moving staircase and some lines of the glass roof appear \"randomly\" through the walls.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\n\n\nI just created objects + render. %%%", "Brushes: Smooth algorith is not consistent.\nCurrent smooth algotithem overwrites input data that can then be used during the same iteration. Meaning that the smooth operation is not consistent.\nDuring usage this is not that noticeable as smoothing is done per brush evaluation step. But it could be improved.\n\nThe memory could be allocated per thread and not per work item to reduce the overhead introduced.", "Flashes in Eevee render with Mantaflow viscosity enabled and Motion Blur\nWindows 7 Pro 64-bit\nNvidia GeForce GTX 1060 6gig\n\nBroken: Blender 2.92.0 alpha / c7e92e379d62 / 2021-01-02\n\nExperimented with the new viscosity setting in Mantaflow.\nRendered the test with Eevee and ended up with output where the surface of the fluid was occasionally 'flashing' in certain frames.\nMy only suspicion is that something it going wrong with the normals of the mesh created by Mantiflow.\nPlease see attached video clip and Blend file.\n[viscosity flashes.mp4](viscosity_flashes.mp4)\n\n- Open attached file\n- Bake simulation (maybe you need to set `modular` and `Is Resumable`)\n- Bake Mesh (maybe you need to set `modular` and `Is Resumable`)\n- Render Animation in Eevee\n\n[viscosity flashes.blend](viscosity_flashes.blend)\n\n\n" ]

[ "Mantaflow - liquid refuses to rise above level of inflow object\nOperating system: Windows 7 Pro - 64-bit\nGraphics card: Nvidia GeForce GTX 1060 6gb\n\nBroken: blender-2.90.0-fd8d245e6a80-windows64\nWorked: 2.83\n\nHere is what appears to be a bug in the Mantaflow liquid calculations in Blender 2.90\n\nIn the first Blender file - **manta_vol_bug.blend** - the inflow object is within an effector-collision object. When the simulation runs the level of the fluid refuses to rise above the Z-axis of the inflow object. This behaviour does not happen with this file in Blender 2.83\n\nIt must also be noted that there is a severe difference of the liquid inflow rate using the same simulation numbers between version 2.83 and version 2.90. That may be a problem on its own, but I cannot say if this has any influence on the Z-axis volume bug that I am seeing.\n\nI have uploaded two video files of the rendered results of this file. \n\nI have also uploaded a second Blender file - **mantaflow volume_bug 02.blend** - where the volume flow relative to the Z-axis of the inflow object is more obvious. Strangely enough, this file when loaded into Blender 2.83 will show the same incorrect behaviour.\n\n[manta_vol_bug.blend](manta_vol_bug.blend)\n[manta_volume_bug_283.mp4](manta_volume_bug_283.mp4)\n[manta_volume_bug_290.mp4](manta_volume_bug_290.mp4)\n[mantaflow volume_bug 02.blend](mantaflow_volume_bug_02.blend)\n[liquid flow bug_290.mp4](liquid_flow_bug_290.mp4)\n" ]

[ "2.9.1 Close without error message\nOperating system: Windows 10, 10gb ram, ssd\nGraphics card: Nvidia GTX 650 1gb vram\n\nBroken: (2.83 LTE and 2.90 current available version)\nWorked: (2.82)\n\nWhen rendering with GPU AND CPU, the app crashes, works perfectly fine on CPU only. On GPU only too but slower than older versions.\n\n\n```\nblender.exe :0x00007FF7A5B76440 ccl::kernel_cpu_sse41_filter_finalize\nblender.exe :0x00007FF7A57A9220 ccl::CPUDevice::denoising_solve\nblender.exe :0x00007FF7A57DA470 ccl::DenoisingTask::reconstruct\nblender.exe :0x00007FF7A57D8ED0 ccl::DenoisingTask::run_denoising\nblender.exe :0x00007FF7A57A7240 ccl::CPUDevice::denoise_nlm\nblender.exe :0x00007FF7A57AB590 ccl::CPUDevice::thread_render\nblender.exe :0x00007FF7A57ABA30 ccl::CPUDevice::thread_run\nblender.exe :0x00007FF7A57A60B0 ?_Do_call@?$_Func_impl_no_alloc@V<lambda_d884e08a7877f415f05ce8ffda8f97b4>@@X$$V@std@@EEAAXXZ\nblender.exe :0x00007FF7A7D5F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5EF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFBF5EFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFC08611FA0 o_exp\nKERNEL32.DLL :0x00007FFC0B647960 BaseThreadInitThunk\nntdll.dll :0x00007FFC0B7AA250 RtlUserThreadStart\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).", "EEVEE baking\n", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n", "Realtime compositor: Texture node output textures with artifacts\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nTexture node support was introduced in 151a53110c\n\nIn realtime compositor, Texture node outputs textures with artifacts.\n\n\n\nIt happens with most procedural textures I tested. This does not happen when a custom image is used, or when Blend texture is connected from the Value output (instead of the Color output) of the node. (With other textures it happens with both outputs.)\n\nThis does not happen when running Blender with a single thread (`blender -t 1`)\n\nFile for quick test: [TextureNodeTest.blend](attachment)\n\n", "No way to edit baked cloth simulation with particle edit mode.\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 680\n\nBroken: 2.82\n\nCan not edit the cloth cache inside of particle edit mode. I am aware of the fade time error inside of options, I am not using fade time I am purely just seeing if what the manual says is possible, editing a cloth sim cache\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. add a cloth sim\n2. Bake cloth sim\n3. go into particle edit mode\n4. no way to edit cloth sim\n\n[ClothEditTest.blend](ClothEditTest.blend) I have uploaded the file I am testing it with", "Baking Procedural Wave Textures\nOperating system: Win10\nGraphics card: Nvid 2080ti / 3090 \n\n3.4 (and others)\n\nCannot bake these textures correctly. \n\nCreate an object. \nAdd a wave texture, set it to uv, and scale it to show many even lines. \nAdd a color ramp to tighten those lines, setting it to constant. \nPlug this into the bump/normal to make raised lines. \nNow bake this. \n\nThe lines will be a broken mess most of the time. I have tried almost every trick I can find/think of, and nothing makes this better. \n\nI am not sure it's a bug, but it is certainly a problem.\n\n", "Baking workflow revamp\n*(This design doc is work in progress)*\n\n### Goal\nBaking is hard to use and requires one map to be baked at a time. Each time configuring appropriate settings and selecting the right objects and shader nodes.\n\nBlender should natively have a baking workflow that is more efficient and powerful.\n\n### Existing Work\n\nMultiple add-ons exist to make this workflow easier.\n\nA patch for object-based baking and long discussion about various other options is here:\n[D3203: Baking system overhaul: Move baking settings from render settings into BakePasses](D3203)\n\n### Use Cases\n\n* Baking a set of maps for game assets.\n**Typically includes maps like base color, metallic, roughness, normal map, AO.** The assets may use complex procedural texture nodes, multiple blended shader nodes and multiple materials, all to be baked down to a single set of maps and material that the game engine understands.\n**Exporters like FBX or glTF would typically want to export this baked material representation.** Efficiently re-baking objects, inspecting the results in the viewport, and applying the same settings to other assets is important.\n* Baking to optimize rendering\n**Some part of a shading network may be baked down for more efficient rendering, either as a viewport approximation or final render. Maybe a complex procedural texture, static background or ray-traced AO/curvature.** Light maps may also be considered part of this, though I personally would not recommend to use them for Cycles or Eevee and not focus on this use case.\n* One-off bakes\n**Examples may be to create a base to start texture or vertex painting, to use in geometry nodes, etc.** The current workflow is reasonably well suited to this, but automatic creation of images or vertex color layers and preview of the result would be helpful.\n** Perhaps best integrated as an operator/tool in paint or edit modes.\n* Other\n**Light map baking for export: how important is this still in modern game engines?** Baking as a part of a geometry nodes network?\n**Baking to transfer attributes between objects: use Data Transfer modifier instead?** ... ?\n\n### Proposal\n\nThere is not a single workflow that is ideal for all uses cases. I suggest to have two workflows that I think will handle the most important ones well, and can work for others with some extra effort. The Bake panel in the scene render properties would be removed.\n\n**One-Off Bakes**\n\n* New operator to quickly bake to images or attribute\n* Operator pops up a dialog, with choice for bake type and relevant settings\n* No settings stored in the scene. Only operator properties, remembered for the next operator execution\n* Operator creates new images or attribute if none exists, or bake to active one\n* Likely exposed in vertex, sculpt, texture paint mode, and in the vertex colors panel\n* No selected to active baking support here\n\n**Material Based Bakes**\n\n* New Bake Texture shader node\n**Bake type and relevant settings** One bake type is an input socket with arbitrary shader nodes plugged in\n**Image or attribute to bake to** Bake/Clear button\n* New Material datablock settings\n**Bake panel in material properties shader node editor, visible when there are any Bake Texture nodes** Bake/Clear button for the entire material\n**Collection property for \"selected to active\" baking, no use of selection state.** Any other shared settings\n\nWith this system, it's possible to create a reusable shader node group for a baked material, or manually add a few Bake Texture nodes for specific cases.\n\nA big advantage of this approach is that the baked result is also immediately previewable in the viewport and usable in the final render. No need to set up bake settings in one place, and a preview shader node setup in another place.\n\nMore details to be worked out\n* Likely need an Image socket type, to make shader node groups really reusable?\n* How to handle baking multiple materials into one, special material slot that all materials bake into? \n** Potentially confusing to have two ways to bake, using either this special slot or as part of regular material slot\n* Precise workflow to clear bakes and decide if baked/unbaked is show in viewport and render\n\n### Python API\n\nWe expect add-ons will continue to be needed for more advanced use cases and automation. Currently these use the Bake operator, but a lower level Python API function could be added, which does not rely on selection state, but rather accepts specific objects, materials, attributes, etc.\n\n### Missing Features\n\n* Metallic, Base Color and possibly other types\n* Packing bakes into specific channels, and multiple maps into one image or attribute", "Cycles and Eevee Significant Difference in Texture Output\nOperating system: Ubuntu 20.04\nGraphics card: GTX 1060 3Gb\n\nBroken: 2.80 and on (3.0.0 is still affected)\nWorked: 2.79\n\nFrom Blender 2.80, Cycles produces incorrect output for some procedural textures, while Eevee produces correct ones.\n{[F12696991](Cycles.png)}\n\nTest file (I assume there might be other files affected too). [Carbon_90.blend](Carbon_90.blend)", "OpenGL error in console\nOperating system: Windows 10, 11\nGraphics card: 6700 XT, 6800 XT, driver 23.7.2 \n\nBroken: 4.0.0, ecb3262bf04, main, 08.08.2023\nWorked: no information.\n\nFirst of all it's better to run Blender with USD built with this fix 2550 since it fixes a lot of other OpenGL errors in console.\n\nThere is an error in console `Runtime Error: in HgiGLPostPendingGLErrors at line 91 of C:\\GPUOpen\\RPRHydraRenderBlenderAddon\\USD\\pxr\\imaging\\hgiGL\\diagnostic.cpp -- GL error: invalid framebuffer operation, reported from __cdecl pxrInternal_v0_23__pxrReserved__::HgiGLBuffer::~HgiGLBuffer(void)` If you select `Render Engine = Hydra Storm` and run Viewport Shading and stop it.\n\nBut if you start Blender with `--debug-gpu` flag you will an error in console `ERROR (gpu.debug): : GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9` and above error with `HgiGLBuffer::~HgiGLBuffer` won't appear anymore.\n\nI put some `debug::check_gl_error` in `detect_mip_render_workaround` and one of them returns `GL_INVALID_FRAMEBUFFER_OPERATION` right after `glClear(GL_COLOR_BUFFER_BIT);` and one more error `GL_INVALID_VALUE` after `glGetTexImage`.\n\nAlso `glCheckFramebufferStatus(GL_FRAMEBUFFER)` returns `GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT`.\n\nI tried to get rid of `HgiGLBuffer::~HgiGLBuffer` error via calling `glGetError`. There are only 2 places worked for me: \n1. ViewportEngine::~ViewportEngine;\n2. End of the `detect_mip_render_workaround`.\n\nDefault startup. \nFirst:\n1. Select `Render Engine = Hydra Storm`\n2. Start Viewport Shading\n3. Stop Viewport Shading\n4. Look in the console\n\nSecond:\n1. Start Blender with `--debug-gpu` flag\n2. Look in the console\n\n", "Painting on pixel-textures do not allow to paint some faces\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: \n- 2.92.0\n- 2.91.0\n- 2.90.1\n\n\nI can paint one face but can`t do it with another, and third one transfer color to wrong place of texture.\n[2020-12-21_11-51-55.mp4](2020-12-21_11-51-55.mp4)\n\nHere the file\n[1pxTexturePaint.blend](1pxTexturePaint.blend)\n", "Baking of normals show different results between versions\nOperating system: Win 10\nGraphics card: Geforce 3060\n\nBroken: 3.5.1\nWorked: 3.4.1\n\nThis changed in 75ad8da1ea6799e3983e4146f4b20dc4bfbb8415\n\n\nBaking of normal map differnet between Blender versions\n\nThe Attached blend file will output differnt result when trying to bake the normals.\nThe Mesh is part of a comercial mesh I use, therefore I cannot share the whole mesh, but in the blendfile you just need to bake the normals in blender 3.4.1 and then in 3.5.1\nThe results are differnet.\n\nBlender 3.5.1 seams to have some bug in the baking or handles the baking differnt.\n\nEdit:\nSeams like the Auto-Smooth of meshes bauses this difference between the versions", "bake hair dynamics issues\nOperating system: wind 10\nGraphics card: gtx 1070\n\nBroken: blender-2.80-79f67acccb36-win64\nWorked: idk\n\nunable to bake hair dynamics. i click the button but nothing happens. in particle edit mode particle hair still looks as if it was not simulated.\n\n", "Cycles GPU/CPU render difference with more than 64 transparent bounces and coplanar faces\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\n\n\nWhen using particle plane with transparency ( to fake volume scatter ), we have a color mismatch between CPU and GPU rendering. \n\n\n see attach file\n\n\n\n[cpu_gpu_issue.blend](cpu_gpu_issue.blend)\n \n", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "different generation of graphic card won't utilise together.\nOperating system: Windows 10\nGraphics card: Radeon R9 295X2 (secondary chip) + Radeon RX560 4GB\nAMD Ryzen 1700X\nMSI X370 Gaming Pro Carbon\n3 * 8GB DDR4-2400\n\nBroken: 2.82.7 to 2.83.3 <--- where x is from 0 to current stable version\nWorked: 2.8, 2.83.4 (partly worked, may end up sudden wattman reset)\n\nRadeon Version: 20.7.2\n\nafter the 3rd step, the render did not show anything, switching back to material viewport, the whole program was frozen. not sure if that is graphic card problem, but that way i could not even render anything. on 2.82.7, this also happened and the render kernels failed to work.\n\n\n1. open up a file of as shown\n2. set the preferences that would use OpenCL to render with R9 295X2 (and RX560)\n3. preview in Cycles\n4. unable to load the preview, switch back to material viewport.\n\n[zeta school 1.blend](zeta_school_1.blend)" ]

[ "Cycles Rendering Drastically Slower Since 2.8 Update\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nAll rendering done with the cycles engine has been much slower in 2.8 than it was in 2.79. A quick test using suzanne and simple AO baking put the 2.8 render at about 1/4th the speed of the 2.79 render. This is consistent with normal render results I've been getting since the update.\n[Simple AO Bake.blend](Simple_AO_Bake.blend)\n\nShould also mention that during GPU rendering in 2.8, CPU usage shoots up to 100% while GPU usage hovers around 15-20%. In 2.79, CPU usage hovers around 35-40% and GPU usage shoots up to 20% when the bake starts and then drops back down.\n\n" ]

[ "Linux todo list\nNOTE: this is a direct dump of Install-OS\n\n- [ ] Drives could be auto-mounted as they are in Ubuntu's file manager (selecting an unmounted drive mounts it). see #30518\n- [ ] Support Freedesktop clipboard management, see #38674\n- [ ] Support xkbset accessibility #39047\n- [ ] Support XINPUT matrix for cursor warping #48901 (edit: this depends on a bug-fix in xorg, see task)", "Proportional editing lag\nWin7 x64, GTX 460\n\nBroken: 2.73, 2.74\nWorked: 2.63 \n\nWith proportional editing on, I get a few seconds freeze when activate translating (G); than after freeze, \neverything goes ok. I thought that the problem was a large mesh, but 2.63 works great and without lags in the same file. \n\nMy \"bugged\" file is the one, I am working with. If it is possible, can i sent it in private and not give it to the world here?\n\nThank you!", "Mouse cursor is not updated after coming to a full stop while panning in the Blender render window\nOperating system: Fedora Linux (Wayland, Gnome Shell 44.1) \nGraphics card: AMD\n\nBroken: 3.5.1\n\nWhen panning in the final render and coming to a full stop before releasing the middle mouse button, the cursor is left on the screen. (See video)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nRender image\nHit F11\nPan with middle mouse button, come to a complete stop\nRelease middle mouse button\n\n", "Can't type tilde (~) in text editing mode - Blender enters fly/walk navigation immediately\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\nOS Language: Brazilian Portuguese\nKeyboard layout: United States (international)\n\nBroken: version: 2.90.0\nWorked: don't know\n\nUsing the `ENG` layout the tilde (~) is in this position on the keyboard:\n\n\nIt can be entered by pressing {key Shift `}.\nHowever, this is the shortcut of another operator:\n\n\nThis conflict causes the `VIEW3D_OT_navigate` operator to run instead of the `FONT_OT_text_insert`.\nPressing {key Shift `} (grave accent) enters into fly/walk navigation even when in text editing mode. This makes it impossible to type letters with tilde (i.e. \"**ã**\") directly into Blender.\nThe workaround for now is typing the text I need in another program and then pasting into Blender.\nThis is quite annoying, specially for someone who speaks another language, or has the tilde in his name, even if one uses the English user interface.\nThis bug might be related to #66607.\n\n\n - Open Blender with a new file.\n - Add a text object.\n - Enter text mode ({key TAB}).\n - Press {key Shift `}\n\nThis enters the fly/walk navigation mode immediately, instead of registering the tilde deadkey.\n\n", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "Float slider in the redo panel of the \"add object\" operator does not hide the mouse cursor\nBroken: 2.79b, 2.83\nWorked: (None)\n\nThe problem is not seen in editing mode, but in object mode when adding an object\nand changing the properties in the redo panel, the mouse cursor does not disappear.\n\n\n", "UI: Wrong text cut-off without \"…\"\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\nBroken: version: 2.80 (where `…` first appeared)\nWorked: never\n\nWhen text can't fit into designated area Blender will cut off last characters and adds `…` at the end. However in some cases it will not add it, instead plainly showing incomplete test.\nAdditionally with long text and limited space Blender will cut middle of a text like this: `start text … end text`. Issue also affecting this case and sometimes will make text to look like this: `start text … end tex`, without last letter.\nThat works for other areas like `Properties Editor`.\n\n1. Open preferences, go to `Keymap`.\n2. Resize window carefully and look how end of a text is behaving.\n[Wrong cut-off with ...2022-01-19 14-02-00.mp4](Wrong_cut-off_with_...2022-01-19_14-02-00.mp4)\n", "Can not selection Armature in MacOS Backend Metal.\nOperating system: Macbook pro 14\nGraphics card: Apple M2\n\n3.6.2\n\n\n\nCan not selection wire Armature in MacOS Backend Metal.\n\nrecorded video\n\nview?usp=sharing\n\nWhen Macos' Backend is set to Metal and the Armature object Viewport Display is wire, objects cannot be selected in bone areas other than the root bone at the location of the origin point.\n\n- Open attached .blend file\n- Try to select any bone in wireframe mode", "Text strip duplication with madeup driver\nOperating system: Linux neo 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux\nGraphics card: nvidia GTX 970\n\nBroken:\n```\n3.0.0-alpha+master.a3027fb09416-linux.x86_64\n```\nWorked: (?)\n\nI duplicated a Text strip via <shift><D>. Then the clone had a driver on 'Location X' set, that the original has not. If You delete that driver, blender crasches (see #91912)\n\n\n- Load attached file\n- Duplicate the Text strip with <Shift><D>\nThe new Text strip now has a driver on Location X\n\n[driver_duplicate_bug.blend](driver_duplicate_bug.blend)", "Cannot input non-ASCII characters with third-party software on Windows\nOperating system: Windows 10\nGraphics card: any\n\nBroken: master\nWorked: n/a\n\nBecause Blender exclusively relies on WM_INPUT for text input and ignores WM_CHAR, any characters provided by third-party software are silently ignored. Such software includes [AutoHotKey ]] or [[ http:*wincompose.info/ | WinCompose ](https:*www.autohotkey.com/).\n\n\nSteps to reproduce with AutoHotKey:\n * Install AutoHotKey\n * Create a simple hotkey in `%USERPROFILE%/Documents/AutoHotkey.ahk` containing non-ASCII characters, for instance: `^!p::Send déjà-vu`\n * Run AutoHotKey; it will automatically register the hotkey for Ctrl-Alt-P\n * Observe that Ctrl-Alt-P in *e.g.* Notepad will write `déjà-vu`.\n * Observe that Ctrl-Alt-P in a Blender text control will write `dj-vu`.\n\nSteps to reproduce with WinCompose:\n * Install WinCompose; it will automatically run and use Right Alt as the compose key.\n * Observe that Right Alt followed by A E in *e.g.* Notepad will write `Æ`.\n * Observe that Right Alt followed by A E in a Blender text control will write nothing.\n", "Cannot use keyframes, File select, File picker (eyedropper), etc. in modal Operators/Panels called by WindowManager\nOperating system: Win10\nGraphics card: Nvidia GTX 1060 6G\n\nBroken: 2.82\nWorked: None\n\nCannot use keyframes, File select, File picker (eyedropper), etc. in modal Operators/Panels called by WindowManager\n\nFor example, this is an operator called by WM to manipulate the location of the selected object. We cannot insert keyframes to the property from RMB > Insert Keyframe or from the anim dot after the property\n\n```\nimport bpy\n\nclass HelloWorldOperator(bpy.types.Operator):\n \"\"\"Creates a Panel in the Object properties window\"\"\"\n bl_label = \"Hello World Modal Operator\"\n bl_idname = \"test.hello\"\n\n def draw(self, context):\n layout = self.layout\n layout.use_property_split = True\n layout.use_property_decorate = True\n\n obj = context.active_object\n\n layout.label(text=\"Hello world!\", icon='WORLD_DATA')\n layout.prop(obj, 'location')\n \n def execute(self, context):\n return {'FINISHED'}\n \n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_dialog(self)\n\n\ndef register():\n bpy.utils.register_class(HelloWorldOperator)\n\n\ndef unregister():\n bpy.utils.unregister_class(HelloWorldOperator)\n\n\nif __name__ == \"__main__\":\n register()\n bpy.ops.test.hello('INVOKE_DEFAULT')\n\n```\n\nThis kind of problem exists in all modal-like panels or operators called by WM. The file picker from file_select is also not working. Is it RNA problem? I hope developer can generate its error message in the console. For now, I don't know what to do next. Please let me know how can I insert keyframes to properties in such panel/operators with right click\n\nBest wishes, thank u", "Rebind default 'Set 3D Cursor' hotkey to Shift+Alt+Middle doesn't work\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nBroken: version: 2.93.0, 3.4\nWorked: it was working with 2.92\n\nRebinding the default Shift+Right press hotkey to Shift+Alt+Middle press hotkey doesn't work. It moves the 3D cursor but I can't drag it everywhere I want like the default behavior.\n\n- Find the default shorcut by typing cursor to the search bar\n- Under 3Dview there is Set 3D Cursor (view3d.cursor3d)\n- Change the default to Shift+Alt+Middle\n- It doesn't work as expected\nioGcz_mV78k", "In Particle Edit mode, Emitter particles are not visible in the viewport\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.83 (sub 0)\nWorked: 2.79.7, 2.79b\n\nThe Particle Edit mode does not work with Emitter type particle. The particle (particle paths) are not visible in the viewport.\n\n- Open this file: [#73168-particle-edit-crash.blend](T73168-particle-edit-crash.blend) (or add a particle system, Emitter type, and bake to memory)\n- Switch to \"Particle Edit\" mode (particle disappear).\n- Click on Sidebar > \"Tool\" > \"Options\" > \"Viewport Display\" > \"Particles\" (blender crash).\n\nReports:\n\n[blender.crash.txt](blender.crash.txt)\n[macos.crash.txt](macos.crash.txt)", "Cursor's icon doesn't update correctly when going from panel to scene\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.2.0 Alpha\nWorked: Never (introduced/discovered with new design for 2.8 series)\n\nThe cursor icon doesn't update properly when returning it to the scene fast enough after tweaking in panels, and on it's way passing over text panels.\n\n- Go edit mode and select a vertice/edge/face to activate the transform panel\n- Place the cursor in the panel where its icon displays the OS default one\n- Move the cursor fast enough onto the scene. On its way pass over text panels.\n- The cursor icon is the default's one, not the cross as it should.\nSee the .gif for visual explanation:\n", "Text object Tab glyphs need special handling\nWhile we have special handling for the horizontal displacement of tabs, it seems most system fonts actually do not have a tab glyph itself, and they are doing something different than bfont with regards to the reference to .notdef -- leading blender to place the missing-tab glyph in their place. I've evaluated numerous fonts, and searched my entire system font folder for those with tab glyphs, and almost none actually have them. This leads me to believe that, I believe, we need some additional handling, at least for the tab character, to handle the missing glyph(s) in Text Objects.\n\nAttached is a blend with FreeSerif.ttf, FreeSans, Liberation something, and FreeSans.otf:\n(Linux, Debian, different versions. 2.90, 2.91 alpha... Standard system fonts from /usr/share/fonts/truetype/ and /usr/share/fonts/opentype/\n[tab.blend](tab.blend)\n\nThe attached shot is blender with FreeSerif (same with most others).\n\n\nBfont works fine. It is missing the glyph, but 9 refers to U+fffd / .notdef:\n\n\nBfont's 9 (with the .notdef ref):\n\n\nFreeSerif, at U+fffd (I don't see it specifying .notdef, but it is set as a replacement char):\n\n\nFreeSerif's tab (9)\n\n\nDejaVuSans.ttf (9)\n\nDejaVuSans.ttf (U+fffd)\n\nDejaVuSans in Blender with tabs\n" ]

[ "Input Cursor has a backgound square, input cannot be seen completely\nMac OS High Sierra, V10.13.1\n2,2 GHz Intel Core i7\n16 GB 1333 MHz DDR3\nAMD Radeon HD 6750M 1 GB\nIntel HD Graphics 3000 512 MB\n\n2.797 56bd8ac9\n\nInput Cursor shows background square and therefore input cannot be seen completely e.g. when using grease pencil or doing number input in tool shelf or properties (see attached images).\n\ninput cursor shows square while using greas pencil or doing number input on toolshelf or properties (see attached images)\n\n\n\n" ]

[ "blender 3.0 cannot render this file with audio\nProcessor\tIntel(R) Core(TM) i7-10750H CPU @ 2.60GHz 2.59 GHz\nInstalled RAM\t16.0 GB (15.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\n\nEdition\tWindows 11 Home\n\nGraphics Card: NVIDIA GeForce RTX 2060 \n\nThis problem happens only with these files, It works fine with other files.\n\nI think that I have setup rendering props ok, Using mp3 for audio output.\nThis file will render video only. It will also render audio audio only from the render tab. \nI have tried any number of combinations of audio and video output (mp4, mp3, etc).\n\nI have tried for weeks to solve this, with no success. Please help. \n\nThank you for your attention,\n\nRoberto Collins Lazo\n\nKept trying different starting and ending points for the video. Rendering only audio crashes with more than a short starting and ending points.\n\n\n**Steps to reproduce**\n[#94586.blend](T94586.blend)\n\nOpen file and render animation. No sound is rendered.", "EXR output color options do not work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nWhen choosing OpenEXR or OpenEXR Multilayer output format we have options for BW | RGB | RGBA\n\n\n\nHowever EXR files are always written as RGBA no matter what, meaning there is not way to save a 3 channel RGB image without alpha or a single channel BW grayscale image.\n\nAnother related issue is the inconsistency in output options.\n\nAs mentioned above the render output does show BW | RGB | RGBA options:\n\n\nBut saving an image from the image editor only shows RGB | RGBA options\n\n\nThe same is true for the options available in the compositor File Output node\n\n\n\n", "Alembic export animated vertex color exports only first frame vertex color\nDebian, Nvidia GTX 1080ti\n\nBroken: 2.78-58a0c275464 and the newest ones\n\nWhen you create an animated vertex color on a mesh with dynamic paint for example, you expect it to be written into alembic while exporting it with vertex colors checked, but instead you have only first frame vertex color baked in it.\n\n1. Open attached blend file\n2. Bake dynamic paint\n3. Export abc with vertex colors checked\n4. Import that abc file and have no animated vertex color\n\nI'm also attaching that abc file.\nDon't know if it's a bug or a thing to do, sorry.\n[alembic_anim_vertex_color.blend](alembic_anim_vertex_color.blend)\n[alembic_anim_vertex_color.abc](alembic_anim_vertex_color.abc)", "Blender Opens Window then Closes/crashes\nOperating system: Windows 10\nGraphics card: AMD FirePro W2100\n\nBroken: 3.5.1 2023-04-24 18:11 Hash:e1ccd9d4a123 Branch: Blender -v3.5-release\nWorked: first version used on this computer\n\n-First attempted to run blender, found error by running the debug, error:\n\n_EXCEPTION_ACCESS_VIOLATION_\n\n- Did specific driver updates for AMD FirePro W2100 and Intel CPU\n\n- Then ran dell command update\n\n- New error appeared after driver updates and running blender:\n\n_A graphics card and driver with support for OpenGL 3.3 or higher is required.\nInstalling the latest driver for your graphics card might resolve the issue._\n\n- Then downloaded GPU-Z to figure out OpenGL version\n- Open GL version was 1.1 when monitor DisplayPort was plugged into the motherboard\n- Open GL version was 4.5 when monitor DisplayPort was plugged into GPU\n\n- Now blender window would appear but closes immediately\n- running blender_debug_gpu_glitchworkaround.cmd in the Blender file worked to make Blender run but is NOT the overall fix\n- updated python\n- did windows updates\n\nunsure\n\n", "VSE - Bad interpolation in exported audio\nBroken: 2.80\n\nExported audio from the VSE is not properly interpolated, creating a 'stair-stepped' pattern when it should be smooth.\n\nChannel 1 is the original waveform with keyframe applied, channel 2 is the timeline exported to wav, and imported back in.\n\nAlso, there appears to be a delay on the animation by a frame - the fade in should be at full volume on frame 7, but it reaches full volume at frame 8 on the exported waveform.", "System Hangs while Interacting with the Viewport\nOperating system: Manjaro KDE Plasma\nGraphics card: Intel HD Graphics (Cherry Trail) Atom X7-Z8700\n\nBroken: 3.5.0, 3.4.0, 3.4.1\nWorked: 3.3.2 (Haven't tried newer versions in the 3.3.x series)\n\nBlender causes the entire system to hang periodically while performing any task. Simply rotating the camera or zooming in or out results in the system freezing for minutes at a time. The mouse cursor responds to mouse and touchpad movement, but the system does not respond to mouse button clicks or keyboard input for long periods of time. Neither Blender nor the desktop respond.\n\nWhen rotating, moving or zooming the camera text overlays in the viewport flicker, sometimes the entire viewport flickers, then the system hangs. There are no errors or warnings printed to the terminal\n\nDoesn't appear to be related to a specific file. The issue is present in all blend files and when starting with the default setup.\n\n", "Optix: Motion Blur seems to glitch out while rendering\n\nOperating system: Windows 11 Pro 22H2 22621.525\n\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\n\nBroken: version: 3.3.2 LTS / 3.5.0 Alpha (Broken in both)\n\n\nHaving motion blur on while rendering with Optix seems to not work as expected in this scene. It renders out with artifacts (Alpha / black squares). Things work fine **when you turn off motion blur or switch to Cuda**.\n\n \n\n**Steps to reproduce the bug:**\nOpen the attached fine and render frame #82 with Optix enabled.\n\n[Keyframe remove 1_010.blend](Keyframe_remove_1_010.blend)\n", "The light and smoke is not rendering in 3.4\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.3 with motion blur off.\n\nThe light and smoke is not rendering in 3.4\n\n\n\n\n**Steps to reproduce**\n[other other.blend](other_other.blend)\n\n- Open file\n- Bake smoke domain\n# Render image\n\n\n\n\n\n\n", "Mist pass saves as black using full OpenEXR\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.6.0\n\nEven though the Render Results clearly show a greyscale image in the Mist pass, when you attempt to save it to an OpenEXR format (full float) the result is all black.\n\n1. Open the attached file\n2. Render image\n3. Switch to the Rendering workspace (already showing mist)\n4. Save As from the Image menu and choose OpenEXR full float\n\nResult:\n\nFile is all black\n\nExpected:\n\nThe greyscale Render Result should be saved as a 32-bit image\n\n", "GPencil: Add multiframe support to Move to Layer\n", "Crash when rendering animations (GPU Subdivision ON, OFF is fine)\nSystem Information\nOperating system: WIndows 11 22H2\nGraphics card: Nvidia GeForce RTX 4080\n\nBlender Version\nBroken: 3.4.1, 3.5, 3.6\n\nForce closes when rendering animation after a number of frames and when opening larger blend files. Happens with all files. All drivers up to date and tested memory with no issues. Worked without issue for 6 months, crashing started 1 week ago.\n\nRendering animation with GPU Subdivision unchecked did not trigger a crash", "Avoid graphical glitches during threaded preview generation\nWhen previews are generated using an OpenGL engine, there can be a number of glitches until the preview is done. That's because some data is accessed/modified that is not thread safe. E.g. `object_preview_render()` modifies `U.pixelsize`. I think other glitches are caused by overriding the active theme in `ED_view3d_draw_offscreen()` - although when I avoided this some time ago for similar work on threaded offscreen drawing for VR, this didn't solve the color flickering.\nThe active theme should probably use thread local storage.\n\nBesides that, the preview generation should be thread safe with OpenGL:\n* It uses the draw-manager's own context, which is mutex protected.\n* The non-thread-safe immediate mode API is not used inside the draw-manager.\n* The draw-manager already has workarounds for GPU driver issues with threaded drawing.\n\nA note: We could also speed up Eevee preview generation significantly by using viewport render quality, not final render quality. The `_imbuf` offscreen rendering functions don't expose the `is_image_render` option for that, which they probably should.", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "EEVEE: Volumetric simulation show ghosting in playback\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: ALL versions up to and including version: 2.91.0 Alpha\n\n\n\nHere's the video of the problem, as can be seen, I have to stop playback to clear the viewport vdb data from the previous frames. Left is EEVEE viewport, right is solid mode (so you can see what the eevee viewport should be displaying:\n\nIt isn't related to EEVEE volume optimisation as I have tried reducing the number of voxels displayed and also reducing the volume samples, viewport samples, and turning off the denoiser. \n\nlatest gpu driver and blender version, resetting blender to factory defaults doesn't help.\n\n[2020-08-20 04-22-55.mp4](2020-08-20_04-22-55.mp4)\n\nHere's the blend file:\n\n[vdb playback bug.rar](vdb_playback_bug.rar)\n```\n\n```\nP.S, the fps is Extremely slow compared to other 3d apps I've tested this sim in (with shading). Is this due to all of the surplus vdb data not being cleared? Perhaps there needs to be an option to cache to RAM if reading from disk is the cause?\n", "Eevee: Soft shadows causing flickering in animation and temporal AA in scenes\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.80\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nEevee soft shadows in objects with thin reflections causes flickering in animation and temporal AA in still images. This type reflections common in interior Arch Viz.\n\nScene 1 example of flickering of soft shadows in animation. I have remove all light probes and effects to focus only light and shadows. Open attach file \"Scene1_AA_eevee.blend\".\nRender the animation with Soft Shadows ON. Then Render animation with Soft Shadows OFF.\n[Scene1_AA_eevee.blend](Scene1_AA_eevee.blend)\n\nAnimation with Soft Shadows ON. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_eevee.mp4](Scene1_AA_eevee.mp4)\n\nAnimation with Soft Shadows OFF. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_No_SShadow_eevee.mp4](Scene1_AA_No_SShadow_eevee.mp4)\n\nAnimation in Cycles for comparison. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_cycles.mp4](Scene1_AA_cycles.mp4)\n\n******************************************************************************************************\nScene 2 example of temporal anti-aliasing cause by soft shadows. I have simplify the scene 2 to focus only light and shadows. Open attach file \"Scene2_AA_eevee.blend\".\nRender Image with Soft Shadows ON. Then Render Image with Soft Shadows OFF.\n[Scene2_AA_eevee.blend](Scene2_AA_eevee.blend)\n\nRender image with Soft Shadows ON. Make sure to view at full size. Notice the temporal AA on the edges on horizontal counter, vertical counter, oven handle and oven racks.\n\n\nRender image with Soft Shadows OFF. Make sure to view at full size. Notice the temporal AA is gone.\n\n\nRender image with Cycles for comparison. Make sure to view at full size.\n\n\n" ]

[ "[Eevee] [Flicker Warning] Render View flickers gray until the render is completed\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0 Alpha\nWorked: I noticed this a few days ago too but figured it might be a side effect of the Eevee rewrite and let it be. But with 3.2 hitting beta now, this is still here. Not sure if intended.\n\nRendering in Eevee flickers grey instead of showing the denoising progress.\n\n1. Create anything in Eevee.\n2. Render.\n\n**FLICKER WARNING**\n[blender_X4RNvR1nsV.mp4](blender_X4RNvR1nsV.mp4)", "Regression: rendering image or animation displays grey flickering instead of rendered image\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX330/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.91\n\nBroken: version: 3.2.0 Alpha\nWorked: 3.1.2, even in 3.2 a week ago\n\nCaused by cc6db8921b\n\nSee video attached\n[2022-04-25 11-06-08.mp4](2022-04-25_11-06-08.mp4)\n\nJust render an image or video, in video is even more noticeable because it does not show frames at all" ]

[ "Data changes in pre and post scene evaluation handlers not recognised by Cycles, plus occasional ACCESS VIOLATION and inconsistent scene properties.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.4.0 Alpha\nWorked: (Unsure)\n\nCycles is not using the evaluated scene following scene modifications via handlers that fire before scene evaluation, and some data refers to the previous frame whilst other data refers to the frame currently being rendered..\n\n\nHi, we're trying to get Blender fully integrated into our studio, but we're running into quite a lot of issues with handlers. It seems that Cycles is only partially recognising changes made to the scene in the pre_render, pre_frame, and post_frame handlers. \n\nIn the below zip file there are 3 directories, each containing a blend file with a simple script to demonstrate the issue. The script changes the file output node's base path, and it also changes blender own render.filepath in the output properties panel. The new file name includes the scene camera name (which changes on frame 1 and 3 using markers) and the frame number when the handler updated the filepath/base_path properties, followed by the __0001 added by Blender. For example frame one should read: left cam_updated_path_on_frame_1__0001.png\n\n**Steps to reproduce problem**\n\n\n\n - Unzip [cycles handler bug.zip](cycles_handler_bug.zip)\n - open each of the blend files in place (use 'load UI' as I've set up the workspace for the easiest testing)\n - notice that the blender output is set to 'not set yet', as is the file output node in the compositor.\n - choose to render the animation\n # In the folder where the current blend file resides there will now be two additional folders, one for blender's output, and another for the file output node's results.\n\n\n**Results**\n\n**pre_render handler**\n\nAs expected the camera is incorrect because the pre_render handler happens before the scene has been evaluated. Although strangely some of the information is for the unevaluated frame that the playhead has just moved to (the frame number) and some is for the frame the playhead was on prior to beginning rendering (the camera name which was active on frame 4 before the playhead moved to the beginning of the animation ready for rendering in this example).\n\nBlender's own image sequence output does use the new path which was assigned whilst in the first frames pre_render handler, but on the first frame, the camera name is incorrect and the frame number is correct:\n\n\nThe file output node images however show that cycles didn't recognise that the base_path property had been updated until the next frame. We can see here that the file ending in __002.exr was updated on frame 1, but not used until frame 2, and this continues all the way through.\n\n\n\n**pre_frame handler**\n\nStrangely, although this handler also fires prior to the scene being evaluated (directly after the pre_render handler), this time Blender's own output shows the camera name is now correct, but again, the updated file output node is still not being used until the following frame:\n\nblenders output:\n\n\nfile output node's output:\n\n\n\n**post_frame handler**\n \nBlender's output again is correct, but the file output node's new path is not being recognised:\n\nBlender's output:\n\nFile output node's output:\n\n\n\nThe above can be worked around with code by grabbing the camera from the marker list instead of the active scene camera, but one really major issue for us is that even when locking the viewport prior to rendering, if we update the file output node's base_path, we start experiencing occasional Access Violations and instant crashes, this happens even if the file output node's path is not visible to UI. (perhaps this is related to the reason why the base path isn't being recognised until the next frame?)\n\n\n", "Geometry Nodes: Going back to frame before simulation cache returns no geometry if frame is out of scene frame range\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 4.0.0 Alpha\n\nOut of scene frame range:\n\n\nInside scene frame range:\n\n\n- Add geonodes modifier\n- add simulation zone\n- run simulation to build up the cache\n- Go to frame 0\n\n", "Application Template: Cannot get rid of \"Metadata\" panel\nOperating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-12.9.22\n\nBroken: version: 2.83.1\n\nWhen wiping the whole UI, the \"Metadata\" panel remains.\n\n- Install application template: [bug.zip](bug.zip)\n- Load it.\n- The UI is empty but the \"Metadata\" panel remains when it should have been unregistered.\n\n", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "Breaking nodes API changes for 4.0\n- [x] Remove `Node.width_hidden`\n- [ ] Complete \"Spline\" to \"Curve\"/\"Curves\" rename in geometry nodes\n- [ ] Stop storing node locations relative to their parents\n- [ ] Use a separate type for internal links (in RNA too) (see [D16960](D16960))\n- [ ] Use a separate type for node group interface inputs and outputs and node sockets\n- [ ] Use dynamically allocated `char *` array to store string socket default values", "Entering names in Object pointer parameter and confirming with the mouse in the right part of the button will clear user input immediately again\nWin 8.1x64, 3x gtx580\n\n2.79a\n\nIn a node's Object parameter, on entering the text manually, after pressing enter to confirm, if the mouse happened to be located where normally the \"X\" button to clear the parameter is, the field gets cleared.\nAlso applies to other object pointer fields.\n\nWhen entering names in Node Editor, (at least for me) it is common to move the mouse slightly sideways, so that the cursor is not over the field being typed in. As a result it happens to be over said clear button quite often. Given that it is currently impossible to undo a single name change #54580 , it turns into either loosing the name and having to search/type it again, or more often - by automatically pressing Undo - losing a whole row of changed fields.\n\n[rename.blend](rename.blend)\n - Click the Object parameter to type manually,\n - Move the mouse to the right side of the field, where the \"X\" was located before starting to type,\n - Enter a new object and press enter,\n - The Object parameter field is empty.", "Bevel/Crease lost after joining geometries in the Geo-Node\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nJoining the geometry in the node tree removes the bevel weight and crease data.\n\n\n\n\n\n[Geo-Node Bevel_Crease.blend](Geo-Node_Bevel_Crease.blend)\nOpen the given file and try toggling the modifiers.\n\n\n", "Geometry Nodes: Mismatching data types connections work differently from other node editors\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.5.0\n\nFloat math node overrides color data, even though it is muted. Same setup works in shader editor without problems.\n\nOpen file and activate *Viewer* in GN. Expected result: colored output (judging by shader area behavior)\n\n", "Metaballs particles with drag force disapearing\nOperating system: Linux-5.3.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.33.01\n\nBroken: version: 2.83.2\nWorked: Never (2.8+)\n\nHi Guys,\n\nas you could see in the atachment file, the metaballs instances particles disapears on certains frames ...\nThere is no problem when Drag Force is not applied\n\nThanks in advance for your help !\nYour Software is amazing !! We love it !\n\n[MetaballsParticlesBug.blend](MetaballsParticlesBug.blend)\n\n- Open file\n- Play animation", "Improvement ideas for using Driver Context Properties to access scene custom properties\nThe #105132 pull request introduces access to properties of the current scene and view layer via an implicit rather explicit reference.\n\nThe existing implementation is perfectly fine for built-in properties, but I have some additional ideas aimed at making it easier and more convenient to allow scene-global custom settings via custom properties.\n\nBasically, since the properties have to be added by the user, it would be convenient to support the case when it doesn't exist. It also may be nice to allow setting overrides at several different levels of abstraction.\n\nThus:\n\n* Allow an optional default value that would be returned by the variable if the referenced property doesn't exist, instead of failing with an error.\n\n* Allow fallback from Layer to Scene, and then World: one World can be used by multiple Scenes, which can have multiple Layers.\n\nSince this all only makes sense for *custom* properties, maybe it can be a new mode specifically aimed at them, e.g. some kind of \"Layer/Scene/World Custom Property\", which has options for the custom property name (without the `[\"...\"]` quoting), channel index (for vectors), and default value.\n\nThese are things missing for the new driver things to fully cover the features of the View Layer mode of the Attribute material node.", "Add Active Camera geometry node\nSince geometry nodes is always processed in the context of a scene (at least it is now), there is typically a single camera object that's currently used for rendering. It can be useful to extract information from it, and the first step is just being able to access its transform.\n\nVQ2W/\n\nAdd a node that outputs the active camera object. Users can then use the object info node to retrieve data about the object's transform. The task includes investigating and adding dependencies between the two objects so that geometry nodes reevaluates when the active camera is moved. That is done in `process_nodes_for_depsgraph`.\n\n", "Data lost to a severe crash was auto-recovered and forcefully overrid data that was saved to disk even tho no recovery options were used\nOperating system: Windows 11\nGraphics card: Gigabyte Windforce RTX 2060 OC Super 6GB\n\nBroken: (steam 3.4.x-3.6.2)\nWorked: ()\n\nnote: this is not related to the recovery or auto recovery systems but about pre-crash data being used from ram instead of reading saved data from disk\n\nnote 2: i verified it's old data as it happened with a mask this time and the vertex ids it was assigned after the crash corresponded to the ones that the mask was assigned to after the bug, but was improperly recovered as ids changed due to changes to the mesh, and unmasking those vertices caused them to be moved a random locations as the shapekey they where assigned to did not exist anymore\n\nAfter a severe crash that was not induced by hardware crashes(ie: out of memory/vram, ran out of pagefile memory etc)\nbut from an error internal to blender, even tho data and changes where saved to disk, blender auto recovered data that was not saved and lost to a crash, and it possibly corresponded to a block of ram that was not freed reported by blender in the cmd window;\nafter the unprompted recovery the data even tho it was corrupted it forcefully overrid the data that was saved to disk upon load\n\nthis error seems to recover all kinds of data, it restored a sculpt mask that had been corrupted and was after deleted and saved the file to disk as not having said mask, to even internal textures/texture paint, and changes to properties\n\ni came to this correlation as this type of forceful recovery seems to specifically happen before the ram drops in utilization after a save and a sizable chunk of ram sometimes in the gigabytes is reported as not freed upon closure from the crash\n\nthis also seems to cause blender to not generate crash.log files\n\n\n\nimportant: blender has to terminate from an internal system and not the OS, as even tho blocks of ram still weren't freed windows took care of it in the cases of hardware related crashes causing this error to not happen\n\n\n\nobtain a crash from any of blender's systems not the OS(import, sculpt mask, operators/geometry nodes with faulty input seem to be the most reliable)\n\nif the file is still saving and completes but the ram has not yet been cleared and a crash happens there is a very high chance the old data will be used instead of the data saved to disk\n\n**regarding a blend file:**\nthere is no way for me to provide a blend file as it's dependent on data that is left in the ram by the crash and happened the same way regardless of file, and would require me to find a reliable way to crash blender in this specific conditions, which is out of my knowledge.\n\n", "Blender saves malformed png files that can't be opened by exiv2 library\nOperating system: Windows-7/10\n\nBroken: version: 3.6.0 - 3.6.2\nWorked: 3.4.1 for sure, most probably 3.5\n\nBlender saves malformed png files that can't be opened by exiv2 library.\nMore in-depth analysis: 2745\n\n> There are actually 2 (identical!) eXIf chunks in this PNG file, but very short so might not carry any significant metadata:\n\n>Btw, exiftool -v3 also warns about overlapping TIFF directories, so at least that should be reported to Blender as well\n\n>Ok, so the TIFF signature 4d 4d 2a 00 is invalid for this eXIf chunk. For big-endian encoding, it must be 4d 4d 00 2a.\n>This is a Blender (or whatever library they use to write PNGs) bug.\n\n1. Render image\n2. Save as png\n\n", "Geometry Nodes socket is not showing relevant value info for current modifier\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.3.0 beta\n\nUsing many modifiers with the same GN node tree (multiple users) has some issue with data updating.\nIf you bring cursor over socket to see its value, then it shows only data from first GN modifier, no matter what modifier is selected at the moment. Seems to be only interface problem, as internally processed data is correct.\n\nIn attached file bring cursor over orange socket (Object type) and it will show same object for both modifiers, when in fact they are different.\n[socket_info_issue.blend](socket_info_issue.blend)", "Geo Nodes lose instances during a Cycles animation render\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1\nWorked: 3.0.1 is the oldest version of Blender that can use the nodes needed for the project to take place.\n\nGeo Nodes lose instances during a Cycles animation render\n\nFollow the tutorial detailed in this video: watch?v=rRGq4C1KPOE \n\nThe following are a screenshot of my Geo Nodes group and blend file of the offending Geo Node group.\n\n\n\n[Bridge run.blend](Bridge_run.blend)\n\n" ]

[ "Experiment: Compositor meta data to support different workflows.\nTo test a new workflow at the blender institute we want to use the same meta data as stored in the input file.\nThe compositor already has the ability to keep the meta data when using cryptomatte which we want to use.\nThis is just an experiment and not intended to land in blender master ATM.\n\n\nMetadata for single layered textures are stored as `ImBuf.metadata` (Properties)\nI expect that in `void OutputSingleLayerOperation::deinit_execution` we could fill them with information that we get from COM_MetaData.\nWe should then also fill the meta data in `ImageOperation`." ]

[ "Segmentation fault when selecting context.area.type before applying operator (scripting)\nOS: Ubuntu 16.04.4 LTS\nHW: Dell XPS 9550 notebook, using Intel HD GPU (nvidia deactivted)\n\nBroken: 2.83\n\nExecuting the operator `bpy.ops.transform.translate` causes a crash if `bpy.context.area.type` is set manually before.\nCrash in `setTransformViewMatrices` because `t->ar->regiondata` is `NULL`\n\nRunning the following script causes the crash:\n```\nimport bpy\nimport bmesh\n\n# Create object\nbpy.ops.mesh.primitive_plane_add(size=1, enter_editmode=False, location=(0, 0, 0))\n\n# Enter edit mode\nbpy.context.area.type = 'VIEW_3D' # If this is not set, crash does not occur\nbpy.ops.object.mode_set(mode='EDIT', toggle=False)\n\n# Modify vertices\nmesh = bmesh.from_edit_mesh(bpy.context.active_object.data)\nmesh.verts.ensure_lookup_table()\nmesh.verts[0].select = True\n\n# Next call causes crash:\nbpy.ops.transform.translate(value=(0, 0, 1), constraint_axis=(False, False, True),\n mirror=False, use_proportional_edit=True,\n proportional_edit_falloff='SHARP')\n```\n", "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "Adjust Last Operation: Other changes outside that panel are reverted back automatically\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\n\nHere the demo and file\n[2020-06-23_20-30-11.mp4](2020-06-23_20-30-11.mp4)\n[Scene state reset.blend](Scene_state_reset.blend)\n\n1. Add some objects, add last one\n2. Change visibility for other objects via outliner\n3. Change property in adjustment popup\n4. Scene settings resetted to previous", "Crash when adding materials\nOperating system: Linux-5.18.9-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics 630 (CFL GT2) Intel 4.6 (Core Profile) Mesa 22.1.3\n\nBroken: version: 3.2.0\n\nBlender crashes when adding a second material (sometimes you need to add some more to crash it)\n\n1. Open the appended .blend file.\n2. Select the object.\n3. Go to material tab.\n4. Try to add a second material.\n\n[crash.blend](crash.blend)", "Hard crash while resizing packed multichannel EXR\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nWorked: unknown\n\nTrying to resize this particular image crashes blender instantly. There's 2 unusual things about the image, not sure if they're relevant\n\n\n - it's a packed multichannel EXR\n - it has some very large values (it's an SDF, so some values are like 9999) \n\n\n\n # Load the file\n[image_resize_crash_004.blend](image_resize_crash_004.blend)\n - Resize the image\n - Crash!\n```\n\n```\nSee video:\n\n[Blender image resize crash 2022-12-08 15-41-15.mp4](Blender_image_resize_crash_2022-12-08_15-41-15.mp4)\n\n\n", "Combine crash\nOperating system: win 10\nGraphics card: 3090\n\nBlender Version 3.5.1 \n\nWhen using ctrl+j to combine components, blender will crash.\n\n", "Remove and re-add the rigid body world causes Blender to crash.\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.3.1\nWorked: I dont know.\n\nWhen the physical world is removed and added again, playback will cause the program to crash.\n\n\n1. Download the 2.blend and open it.\n2. Play 5 frame.\n3. Click the Remove Rigid Body World button.\n4. Click the Add Rigid Body World button.\n5. Click the rigid body world setting Collection. Then select RigidBodyWorld .\n6. Click the rigid body world setting Constraints. Then select RigidBodyConstraints .\n7. Move to 1 frame.\n8. Play 5 frame. Blender will crash immediately.\n\n[2.blend](2.blend)", "Image Editor Blank After Switching Slots, Even If There Is A Render In That Slot\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: (2.80, 79f67acccb36, blender2.7, 2019-03-24)\n\nSwitching the slots in the image editor for the render result (hotkey \"j\") can show a blank image, even if there is an image available in that slot.\nSelecting the render layer in the dropdown menu brings it back.\nThis is irritating, especially since the image is shown right after rendering.\nThis only happens if the compositor is disabled.\n\n- Load [bug.blend](bug.blend).\n- Press F12 to render. The image editor comes up.\n- Press \"j\" to switch to switch the slot.\n- Press F12 to render again.\n- Press \"j\" to switch back to the previous slot. It now appears blank.", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "Rendering object in Cycles X preview hard crashes whole system\nOperating system: Windows 10 x64\nGraphics card: nVidia RTX 8000\n\nBroken: blender-3.5.0-alpha+universal-scene-description.1f9e90bb1cf3-windows.amd64-release\n\nRendering of scene in Cycles preview hard crashes whole system. System screen goes to black and the fans go to max.\n\nLoad blend file at link: brutes_set1C_trimmed.blend?dl=0\n\nSet screen to Render preview and navigate around.\n\n", "Blender crashes: OpenVDB math::Transform::read throws exception. \nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.2\n\nBlender keeps crashing.\n\nI have a project were I created an animation of modified arrays. Everytime I play it it crashes\n\nCrash report: P1536\n\ncrashed thread: \n```\n\tThread 35 Crashed:\n0 libsystem_kernel.dylib \t0x00007fff726c733a __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff72783e60 pthread_kill + 430\n2 libsystem_c.dylib \t0x00007fff7264e8a2 __abort + 139\n3 libsystem_c.dylib \t0x00007fff7264e817 abort + 135\n4 libc++abi.dylib \t0x00007fff6f8ae458 abort_message + 231\n5 libc++abi.dylib \t0x00007fff6f89f8bf demangling_terminate_handler() + 262\n6 libobjc.A.dylib \t0x00007fff713da5b1 _objc_terminate() + 104\n7 libc++abi.dylib \t0x00007fff6f8ad887 std::__terminate(void (*)()) + 8\n8 libc++abi.dylib \t0x00007fff6f8b01a2 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27\n9 libc++abi.dylib \t0x00007fff6f8b0169 __cxa_throw + 113\n10 org.blenderfoundation.blender \t0x0000000110291c61 openvdb::v7_0::math::Transform::read(std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 4801\n11 org.blenderfoundation.blender \t0x000000011026082b openvdb::v7_0::io::Archive::readGrid(std::__1::shared_ptr<openvdb::v7_0::GridBase>, openvdb::v7_0::io::GridDescriptor const&, std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 1787\n12 org.blenderfoundation.blender \t0x0000000110286589 openvdb::v7_0::io::File::Impl::unarchive(openvdb::v7_0::io::File const&, std::__1::shared_ptr<openvdb::v7_0::GridBase>&, openvdb::v7_0::io::GridDescriptor const&, openvdb::v7_0::io::File::Impl::NoBBox) + 57\n13 org.blenderfoundation.blender \t0x0000000110282c91 openvdb::v7_0::io::File::readGridByName(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, openvdb::v7_0::math::BBox<openvdb::v7_0::math::Vec3<double> > const&) + 465\n14 org.blenderfoundation.blender \t0x0000000110282ab6 openvdb::v7_0::io::File::readGrid(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 54\n15 org.blenderfoundation.blender \t0x00000001128a2cc9 MANTA::updateGridFromVDB(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 361\n16 org.blenderfoundation.blender \t0x0000000112890985 MANTA::updateGridFromFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 869\n17 org.blenderfoundation.blender \t0x0000000112890cee MANTA::updateNoiseStructures(FluidModifierData*, int) + 558\n18 org.blenderfoundation.blender \t0x000000011287e2b5 manta_update_noise_structures + 21\n19 org.blenderfoundation.blender \t0x000000010df34cd0 BKE_fluid_modifier_processDomain + 3168\n20 org.blenderfoundation.blender \t0x000000010df316ce BKE_fluid_modifier_do + 142\n21 org.blenderfoundation.blender \t0x000000010e3ad4f6 applyModifier + 54\n22 org.blenderfoundation.blender \t0x000000010dea5b0a mesh_calc_modifiers + 2778\n23 org.blenderfoundation.blender \t0x000000010dea4d6b mesh_build_data + 123\n24 org.blenderfoundation.blender \t0x000000010dea4035 makeDerivedMesh + 133\n25 org.blenderfoundation.blender \t0x000000010dfe1281 BKE_object_handle_data_update + 1089\n26 org.blenderfoundation.blender \t0x000000010dfe1704 BKE_object_eval_uber_data + 52\n27 org.blenderfoundation.blender \t0x000000010e9f36ba DEG::(anonymous namespace)::deg_task_run_func(TaskPool*, void*, int) + 138\n28 org.blenderfoundation.blender \t0x00000001142cadbc task_scheduler_thread_run(void*) + 364\n29 libsystem_pthread.dylib \t0x00007fff72784109 _pthread_start + 148\n30 libsystem_pthread.dylib \t0x00007fff7277fb8b thread_start + 15\n```\n", "MultiRes+Solidify while trying to use Sculpt Mode cause Blender to crash\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nI tried deactivating one modifier while keeping the other one active to see if Blender would crash, but this was not the case. Only when I used both simultaneously did the program reliably crash every time, regardless of brush.\n\nAdd the modifiers that are active in the video and follow along. \n[Desktop 2019.09.23 - 00.49.39.02.mp4](Desktop_2019.09.23_-_00.49.39.02.mp4)\n", "LineArt; Crash after press play in a scene with LineArt modifier\nOperating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\nNo idea what crashes blender. Just press play and wait some seconds.\n\nI would love to help solving this issue, so when someone could remind me where the crashreport usually lands in Linux, i could share that as well.\n[Narrator.blend](Narrator.blend)\n\n", "Unable to execute Toggle Edit Mode - error changing modes\nOperating system: Linux-5.15.11-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.3.2\n\nBroken: version: 3.1.0 Alpha\n\n\nIt happens when I try to toggle to Edit Mode on second scene if first scene has edit mode a object\n\n\n\n1) Open file\n2) Select scene \"Scene.001\" and try to toggle to Edit Mode\n3) Get a error\n\nIt is issue or planned (user) error? Getting the error don't full inform an user. Why the error happens? A user may be confused :)\n\nP.S. For fix the error need in scene \"Scene.002\" to disable Edit Mode and than can be to switch to edit mode in \"Scene.001\"\n\n[edit-mode.blend](edit-mode.blend)\n" ]

[ "Nesting Scene make Blender trash\nOperating system: Windows 7\nGraphics card: GTX 1080 and RTX 2080 Ti\n\nBroken: 2.80 (sub 45), branch: blender2.7, commit date: 2019-02-24 22:02, hash: 893fa598319e, type: Release\nWorked: (optional)\n\nI've created complex scenes and it crashes when adding them as background scene.\n\n[BSM-04.zip](BSM-04.zip)\nI'm providing a file where the problem happened. Don't worry about missing files.\nTo make Blender crash:\n\n\n - Open file\n - Tab Scene, Scene, Background Scene: (set to) Environnement\n # Crash!\n\nUsually, it works fine, but not here. Why? Thanks for your help!\n\n\n", "Crash on selecting \"Background Scene\"\nOperating system: Windows 10\nGraphics card: GTX 980 Ti\n\nBroken: 2.80, 9315cc443b1d-win64, blender2.8, 2018-02-20\nWorks: 2.79\n\nOpen Blender with any file. Create an extra Scene. Select the other scene as a \"Background Scene\" in the Scene tab. Blender crashes.\n\nThis happens on all my files with 2.8 and has done so for awhile. 2.79 works fine.", "Crash when using linked scene as Background Scene\nOperating system: elementaryOS 0.4.1\nGraphics card: GTX 1080\n\nBroken: 2.80, cf75aea21857\n\nWorked: 2.79\n\nWhen using a scene linked from another file as Background Scene, Blender crashes. \n\nExtract the two Blendfiles from this archive: \n[scene_link_test.zip](scene_link_test.zip)\nOpen \"scene_link_test.blend\".\nI have already linked in the scene \"source_scene\" from source_scene.blend.\nIf I try to choose \"source_scene\" as Background Scene, Blender crashes." ]

[ "Area Light Leave light border traces on surfaces (less noticable on CPU)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.0 Beta\nBroken: 3.1, 3.0\nWorked: never?\n\nArea light leaves visible trailing light on wide surfaces\n\n\n[Area light trails_render.blend](Area_light_trails_render.blend)\n\n 1.open Blender\n 2.add a plane scale it by 30\n 3.change point light to area light\n\n\n", "Unable to accurately sample colors in Vertex Paint mode\nOperating system: Linux-5.10.11-arch1-1-x86_64-with-arch 64 Bits\nGraphics card: GeForce GTX 660M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.92.0\nBroken version: 2.83.1\nWorked: 2.79b\n\nSampling colors in Vertex Paint mode is unreliable even in flat shading or when utilizing an emission shader and standard color management (although this reports the correct color some of the time) in both Cycles and Eevee.\n\n1. With the default cube selected, enter Vertex Paint mode.\n2. Switch the viewport shading to Solid, the lighting to Flat, and the color to Vertex.\n3. Change the brush color to #000003.\n4. Go to the Paint menu and select Set Vertex Colors (or press Shift+K)\n5. Sample the color on the cube by either using the eyedropper from a color picker, or pressing S with the mouse hovering over the cube (doesn't matter if Sample Merged is checked or not)\n6. Check the brush color and see that it has changed to some other color (#010103 on my machine)\n", "Allow user to change the shading parameters of the asset preview generation scene\nUsers should be able to have some control over the render settings of generated asset preview icons.\n\nPersonally, I want to be able to turn off the specular lighting because it makes my assets look ugly in the previews (note the big shiny surfaces on these bushes).\n\n", "Burned Out Screen Space Reflections in Eevee Viewport - Nvidia GT 750M\nOperating system: macOS 10.14.3\nGraphics card: NVIDIA GeForce GT 750M 1024 MB\n\nBroken: 2.90.0\nWorked: 2.79\n\nIn some cases I detected that the Screen Space Reflections in Eevee Viewport gets out of control.\nA few seconds after switching to the viewport (even when viewport samples are set to 1) the issue kicks in and – as the sampling continues – an increasing percentage of the reflections get totally white.\n\n\n\nThe renders are correct.\nSurfaces affected by reflection planes are correct.\nHiding the chandeliers meshes solves the problem. Switch tab and back for this to work.\n\nI was able to strip down the scene and identify the source of the problem: Originally I set up the glass material with \"multiply\" blending. This was converted (when opened with belnder 2.82 alpha) to a \"Shader to RGB\" and a \"Transparent BSDF\" node. [1]\n\nThe \"Shader to RGB\" causes the problem in 2.82.\nThe \"multiply\" blending of the material causes it in 2.8.\n\nOpen the attached file.\nSwitch to LookDev or Rendered viewport.\nWait.\n\n[Chandelier.blend](Chandelier.blend)", "Improve custom shader AOVs\n- [ ] Autocomplete AOV names in the AOV output node\n- [x] Unique naming and adding .001 does not work correctly in all cases\n- [ ] Add vector AOV output type\n- [ ] View layer level material or shader node group that can be set to output AOVs for all objects\n- [ ] Viewport display of custom shader AOVs\n- [ ] OSL support\n- [ ] Add filtering options (mainly to use either transparency or not, min, max, ..)", "Several inconsistencies in Cycles BSDF\n1. Defensive sampling\n ~~in `bsdf_microfacet_sample()` it is checked against `(path_flag & PATH_RAY_CAMERA)`, but `bsdf_microfacet_eval()` is always using the pdf of defensive sampling, except when fresnel is one. Also, it's worth verifying if defensive sampling is still practical.~~ (bf82f9442c)\n2. `sd->Ng` or `sd->N`\n ~~both `bsdf_microfacet_sample()` and `bsdf_microfacet_eval()` have an argument `Ng`, but we pass `sd->Ng` to the former and `sd->N` to the later, so checks like `dot(Ng, wo) > 0` don't give the same result.~~ (063a9e8964)\n `bsdf_is_transmission(sc, wo)` checks using smoothed normal `sc->N`, but in BSDF sampling and evaluation `(sd->type & PRIMITIVE_CURVE) ? sc->N : sd->Ng` is used.\n3. `ClosureLabel`\n * In `surface_shader_bsdf_sample_closure()`, we accumulate the result of all the closures, but `label` is solely determined by the closure chosen by `bsdf_sample()`. Maybe this is fine but the logic seems weird.\n * For `CLOSURE_BSDF_HAIR_CHIANG_ID`, the label is determined by the `wo` direction in `bsdf_label()`, but determined by the interaction number in `bsdf_sample()`. Maybe `label` should always be `LABEL_REFLECT` because hair closure handles internal absorption itself.\n4. Anisotropy\nBehaves differently for Glossy and Principled BSDF. Principled BSDF uses remapping from [Disney]() and only allow positive anisotropy. Glossy BSDF does not use remapping, allow both negative and positive anisotropy, and treat the distribution as isotropic if `anisotropy < 1e-4f`. The last piece of logic is repeated in svm, osl and `shader_nodes.cpp`\n5. `eta` and `label` required by path guiding\nis inconsistent in BSDF sampling and evaluation.\n", "Tasks after BI removal\n* Code cleanup\n * Preview render code could be simplified, not used old preview.blend** Customdata mask handling still assumes old draw types\n * Move camera matrix code out of Render and into Freestyle, the only user\n * ~~Remove BLENDER_RENDER compat engine, find better system~~\n * Simplify GLSL shader coordinates, originally designed for camera space shading\n\n* Bigger tasks\n * #54696 (Blender Internal displacement baking move to Cycles)\n * [x] #54697 (Vertex color baking for Cycles)\n * #54656 (Cycles/Eevee texture nodes for modifiers, painting and more)", "UV: Add 3D Gizmos for UV projections, Cube, Cylinder and Sphere projection\nThe \"Unwrap > Projection\" operators are powerful, but would be even better with artist control over exact placement in 3D space.\n\nPropose to add gizmos in the 3D viewport to allow precise artistic control over the cube, sphere and cylinder.\n\nConsider adding Planar Projection as well.\n\nThanks @BlenderBob for the suggestion!\n\n", "Cut brush - curve sculpting\nSee #96259.\n\nThis initial implementation doesn't need yet to have the Knife overlay control (similar to mesh edit knife).", "Strange shading behaviour when using boolean modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nWhen using a boolean modifier with an object that on a target object it uses the normals of the boolean object on the target object to determine the shading on the affected areas of the target object.\n\nWhen using a boolean modifier with an object that on a target object it uses the normals of the boolean object on the target object to determine the shading on the affected areas of the target object.\nThis means, that when using a boolean object that has shade flat on a target object that has shade smooth, the resulting object will have smooth shading everywhere except where the boolean operation happens.\nAdditionally, when using custom split normals (like e.g. weighted normals) it applies the custom split normals on the target object.\n\nThis behavior already seems pretty strange to me, since it almost always gives strange results since oftentimes the normals from the boolean object and the target object don't perfectly match, causing weird shading issues.\nI can understand that this may be an intentional feature, but it just brings so many problems, since normal editing modifiers after a boolean modifer like weighted normals don't affect the areas affected by the boolean modifier, meaning to tweak shading in these areas you have to tweak the normals of the boolean object and somehow make a seamless transition to the target object...\nApart from that it also causes some other problems, that are a worth a seperate bug report, which i will write shortly.\n\nAn additional problem with this is that shade smooth and shade flat aren't considered custom spilt normals, so after applying the boolean modifier the areas affected by the boolean modifier will change it's shading to that of the target object, since the shade smooth isn't applied as a custom normal.\nFor some reason that doesn't happen automatically, since directly after you aplly the boolean modifier the shading doesn't change immediately, instead it only changes when you \"recalculate\" the normals when using left click -> shade flat or shade smooth.\n\nA test file to demonstrate this behavior:\n[Test_file3.blend](Test_file3.blend)\n\nAfter applying the boolean modifier and \"recalculating\" the normals using left click -> shade flat or shade smooth the normals left from the boolean modifier will have vanished.\n\n\n", "Eevee viewport soft shadows are broken on higher sample count\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: ---\n\nEevee soft shadows in viewport have color spills. But it works fine on final render (F12)\n\n\n\n- Open .blend file\n\n[bug_soft_shadows.blend](bug_soft_shadows.blend)\n\n- Switch to Rendered Mode of Viewport Shading\n- Wait half a min and see the problem(", "Custom Shading Modes\nThis is a design task for creating custom presets for the workbench, eevee and cycles viewport rendering.", "CYCLES: Surfaces inside volumes are Not Lit or Shadowed by the volume if the volume is not visible to Camera Rays\nLinux Mint Mate\nGTX 1050\n\n\nBlender 2.81 Alpha\n2019-09-27 22:44\nHash: 1c1a3198af9d\n\n\nDiscovered while trying to catch shadows from volumes on surfaces for compositing.\n\nSurfaces inside of volume meshes are not shaded (lit/shadowed) by the volume if the volume is invisible to camera rays\n(checkbox in Object Properties -> Visibility -> Ray Visibility -> Camera)\nAs far as i can tell this also affects Holdout.\n\n\n\n\nCurrent workaround: make sure volume IS visible to camera rays, and instead bypass it in the volume shader using the Camera Ray socket on the Light Path node\n\n\nTo Reproduce:\n\nOpen attached .blend , press render\nNote the missing shadow/light where the volume cubes intersect the default cube.\n\nI have in the .blend also included the \"expected behaviour\" by using the workaround, switch the Scene from \"Bug\" to \"Workaround\" and press render again.\nNote the shadow/light now covers the default cube properly.", "Cycles: adaptive sampling improvements\n- [x] Optimize PMJ pattern generation, and generate more samples\n- [x] Solve issues with combined CPU and GPU not using the same amount of samples. Possibly by using a higher adaptive step for both CPU and GPU.\n- [x] Render multiple small times at the same time for GPU, to allow adaptive sampling to stop and match CPU without too much performance impact.\n- [x] Denoising can detect patterns due to adaptive sampling only working per tile. (#79190)\n\n- [ ] Detect errors in larger windows or using some hierarchical methods, as the simple 3x3 window fails for noisy scenes \n- [ ] Analyze different error metrics, and consider adding some user control over this", "Eevee - visual artifacts during irradiance volume baking\nWindows-10-10.0.16299 64 Bits\nGeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\nBlender 2.80 (sub 51)\n\n[irradiance_volume_bake_artifacts.blend](irradiance_volume_bake_artifacts.blend)\n - Open attached file\n - Switch to rendered mode (Eevee)\n - Press \"Bake Indirect Lighting\"\n\nYou should see squares flickering:\n\nVideo:\n[Desktop 2019.03.27 - 09.18.07.01.avi](Desktop_2019.03.27_-_09.18.07.01.avi)" ]

[ "Velvet BSDF\nRecent publication from Siggraph 2019 indicates that fitting LTC against Ashikmin is doable. Need further investigation.\n\nEstimate : 1 week\n" ]

[ "Blender 3.5 Image editor does not fully refresh on some zoom levels while painting\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.1\nWorked: 3.3.2\n\nBlender 3.5 Image editor does not fully refresh on some zoom levels while painting\n\n\n- Open attached file\n- Scribble on the top left image editor\n- On 3.4.1, 3.5.0 and 3.5.1, the image editor being painted doesn't seem to update the view fully, both only below that uv seam line, and 3.5.0 had more portions that aren't updated compared to 3.5.1.\n- Zoom in/out, it refreshes back to normal.\n\nNote:\n\n- This only happens on some particular zoom levels, sometimes I can get a lower zoom level to produce this error too, by zooming in and out and draw, you could probably find some more zoom levels where the image update region isn't complete.\n- When you zoomed out to some level and it works, and then you could zoom to some other level it could fail again.\n\n| 3.3.2 (correct) | 3.4.1 | 3.5.0 | 3.5.1 |\n|--|--|--|--|\n|  |  |  |  |\n\n------\n\nOriginal description:\n\nWhen zoomed in at a particular level the real time properties of the image editor stop working, In the short video i sent I am painting a texture using the Image editor window, it updates the texture on the model and the UV editor below, but the image editor window doesnt update until I either zoom in or zoom out, At first I thought it was random but then I found it can be easily replicated by simply being zoomed in at the level that I was when the bug was happening.\n", "VSE: Operators missing cache invalidation\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.1.0 Alpha\n\n\nThese things were also reported in: #90415 but not fixed yet. Invalidate cache = restart prefetch frames. \n\nScene Strips:\n - 3D View object changes in referenced Scene strip need to invalidate cache.\n - Changing the Post Processing setting in the referenced scene in a scene strip needs to invalidate cache.\n - Changes in Compositor need to invalidate cache.\n\nText Strips:\n - Doesn't update while entering text, but do when changing Wrap Width.\n\nSnap Strips to Current Frame:\n - Is not caching from the Playhead position. It actually makes prefetch caching stop. And it will only start again if Show Cache is disabled and reenabled. \n\n\nModifiers:\n - Curves doesn't update Preview while dragging curve points, only on release.\n\nUnmute Strips:\n - Need to invalidate cache.\n\nBtw. caching still needs to work when reverse playing and also needs to keep some frames cached on the left side of the playhead for quick reverse playing. There might be an old report open for this, but I can't remember.\n\n\n", "Edge-slide seems to highlight an edge now (visually noisy and inconsistent)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Beta\nBroken: version: 2.91.0 Alpha\nBroken: version: 2.91.0 Alpha\nWorked: not sure, maybe early july?\n\nEdge-slide seems to highlight a split edge now which seems a bit visually noisy and inconsistent. It's visually noisy since it's not adding much for the user (it's not an indication of snapping target for instance) and represents another visual color change that distracts the user from the primary operation. Inconsistent because it's based on the location of your mouse when invoking the operation which leads to really weird cases like the following.\n\nA hidden edge being highlighted on this cube:\n\n\nOr different edges depending on slight differences in mouse position between edge-slide attepts:\n\n\n\n\n\n- Go into edit mode on default cube in default scene\n- Add an edge loop and attempt to slide it\n\n", "The viewport lock modes are super glitch (in general) with zooms and centering\nOperating system: Windows 10\n\n\nBroken: blender-3.0.0-alpha+master.eae4e2251839-windows.amd64-release\n\n\n\nThe viewport lock modes like 3d cursor or object locking is super glitchy in general which creates a disorienting experience. The main issue is sudden jumps in zooms also sometimes the center or rotation becomes jumpy as well. Some jumps in the video is worse than the others. Bear in mind that I am not zooming intentionally when there is a sudden jump.\n\nThis gets even worse in different scene scales and scene layouts. Here I am demonstrating it only with the cursor but this erratic behavior happens with object locking too. This becomes even worse with a Wacom tablet since it is harder to keep the pen movement as static as the mouse while zooming.\n\n\n- Load the attached .blend file\n- Make sure the viewlock is set to the cursor, and have similar preferences as shown in the pictures\n- Try repositioning the cursor, just move the cursor to different objects.\n- Move the cursor to the surface of another object then try ctrl+single middle click to activate the zoom\n\n\n\n\n\n\n\nTest File:\n[glitchy_lock_modes_28082021_2053_04.blend](glitchy_lock_modes_28082021_2053_04.blend)\n\n[A7ysxb6GVc.mp4](A7ysxb6GVc.mp4)", "Grease Pencil Color Management inconsistencies\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.81 (sub 14)\nWorked: (optional)\n\nBlender CM for GP is inconsistent between viewport and render. Viewport is not affected by Filmic, but render is.\n\nIn a new file, add a GP Suzanne. Change viewport to RENDERED. Render and compare colors/contrast: they are different.\nChange CM from Filmic to Standard. Render and compare again: they match.\n\n\n\n\n", "Keyed Particle Physics Incorrectly Rendered Under Eevee and Cycles, but Correctly Rendered in Viewport Render\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nCreate two objects. Attach a normal particle system to the first one. Attach a keyed particle system to the second one, with the two relations \"first object\" then \"second object\". Therefore, particles should move from the first object to the second object. If the starting velocities are non-trivial and the keyed particles are generated over three or more frames (e.g., start time 10, end time at least 12) then the particles of the keyed system are correctly rendered in the viewport (rendered mode) but appear in different positions when actually rendering (pressing F12).\n\nI first discovered this with a more complicated example, and the same behaviour occurred under both 2.90 and 2.83 (normal releases). Googling did not turn up anything relevant. (Motion blur is off.)\n\nI have been able to recreate it with a simple .blend file attached. Included are two screenshots at frame 20, one of the viewport, one of the rendered image. While the difference is just one particle here (a red particle is over the left square in the viewport but off the square in the rendered image), vastly different behaviour can be achieved by increasing the difference between start and end times. \n\nIn the more complicated example, not included here, a particle would appear at the top of the screen and move towards its final destination. When rendered though, it would appear in the correct place on that frame but then immediately jump to a very different location on the next frame.\n\nNote: This bug might depend on the first object's particles having a short lifetime - the original motivation is having one object explode then morph into another object. The rendered animation looked very different (and incorrect) from the viewport animation.\n\n[system-info.txt](system-info.txt)\n\n\n\n\n\n\n[Debug 2.blend](Debug_2.blend)\n1) Open it.\n2) Set viewport to Rendered mode.\n3) Move playhead to frame 20.\n4) Observe the locations of the 4 red particles near Plane.001. (They form a loose \"T\" shape and none are touching Plane.001.)\n5) Press F12.\n6) Observe the locations of the 4 red particles near Plane.001 are very different. (Two are touching Plane.001 and the other two are in line ready to arrive at Plane.001.)\n\n", "FCurve editor: Inconsistent/unclear display of group visibility state\nWin7/64, GTX 750 Ti\n\n2.74 official\n\n\nThe group visibility icon (in red circle) makes no useful statement about the visibility of the contained channels.\n\n - Open [FCurveVisibleState.blend](FCurveVisibleState.blend)\n - As you can see in the FCurve window, all three channels are visible (True), so is the group.\n - If you click the visibility of the \"X Location\" channel in order to hide it, the group visibility is still True.\n - If you additionally hide the Y and Z location, the group visibility state is still True.\n\nThis means that the group visibility icon is True if either all, some or none channels are visible. In other words, it does not reflect anything useful. It only acts as a button to toggle the state of the channels.\n\nIf the group icon is not to display an intermediate state (some but not all channels are visible), the True state should indicate that at least one channel is visible. Consequently, the only required change is: If no channel is visible, the group icon should also be set to False. Otherwise, if the group is collapsed and the group icon displays True, we always have to expand the group in order to find out if any channel is visible at all.\n", "Boolean - Animation - Viewport works correctly render view doesnt\nUbuntu 18.04, Win 7 x64\n\nBroken: d53093953f8\n\nBooleans dont match between Viewport and Render\n\n1. Open attached blend file\n2. Preview render (shift z)\n3. Notice the green on top\n4. F12 Render\n5. Notice how the green is no longer there\n\n[booleansBug.blend](booleansBug.blend)", "Move cache visualization to draw overlay\nCurrenlty the cache visualization isn't updated during playback, only when the screen is redrawn.\nThis needs an optimization of the drawing of the cache lines.", "Color managment applyed twice when render from viewport\nOperating system: Linux-5.19.0-32-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 4080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.78.01\n\nBroken: version: 3.4.1\n\nThen rendering from viewport, color management is applied twice.\n\nThis is undesirable since it creates a disconnect between the visible result in the 3D Viewport and the render output.\n\n\n\n\n\n- Open blend file\n- Click View -> Viewport render image.\n\n", "UI: Cursor flickering when hovering over properties\nBroken: version: 3.0.0 Beta\n\nWhen hovering from one property to another in property area, sometimes cursor changes from <--> to standard cursor. There are no instances where you stop moving it and it stays as standard one - it always changes to <--> after a fraction of a second. UI scaling does not affect it.\n\nNote that when tried without recording problem was more apparent, almost always cursor was flickering.\n[UI Cursor flickering take 2 2021-11-27 10-58-42-112.mp4](UI_Cursor_flickering_take_2_2021-11-27_10-58-42-112.mp4)", "2.83 3D viewport performance\nOperating system: Ubuntu 20.04 LTS\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2), version: 4.5 (Core Profile) Mesa 20.0.4\n[system-info.txt](system-info.txt)\n\nBroken: 2.83\nWorking: 2.82\n\nProblem seen in Workbench, Wireframe and Eevee.\nViewport performance it's really bad, I'm moving around just the initial cube scene at 15-20 Fps, older Blender versions movement is perfectly smooth.\nNo matter the scene/blend file, 2.83 offers worse viewport movement performance compared to older versions,\nIt's important to mention that only the viewport movement is being affected by this performance drop, everything else including rendering works smooth as butter just like older versions or even better. Splitting up the scene in windows kinda fixes this problem.", "Asset Browser preview generation not updating untill hovering over Preview menu\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.1\n\nWhen trying to generate an asset preview using `Render Active Object` the preview **won't display** until hovering over the `Preview` menu.\n\nOpen `Blender` -> Open `Asset Browser` -> Mark any **object** as asset -> Open `Asset Details` -> In the `Preview` Menu you will find `Render Active Object Button`\n\n[2022-12-08 21-59-59.mp4](2022-12-08_21-59-59.mp4)", "Viewport header menu, late/wrong responce to hover and click\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\n\n\nSometimes menu stucks when mouse pointer already over another menu.\n[2021-11-12_14-21-18.mp4](2021-11-12_14-21-18.mp4)", "EEVEE is ghosting with viewport denoising enabled.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nHere's a viewport render:\n[EEVEE ghosting0001-0090.mp4](EEVEE_ghosting0001-0090.mp4)\n\nHere's what it looks like during playback if viewport denoising is enabled:\n[2021-10-23 17-07-44.mp4](2021-10-23_17-07-44.mp4)" ]

[ "Using viewport visibility as a driver doesn't work without constantly updating it in the driver property\nBroken: version 2.93\nWorked: Never (2.8+)\n\n\nUsing viewport visibility as a driver from another object doesn't works unless you constantly hit \"update dependencies\" it in the driver property.\n \n \nFor this, i used the cube's visibility as a driver on the shape key of the sphere.\n[The not working file.blend](The_not_working_file.blend)\nIn the outliner, enable the viewport visibility for the cube, then disable it again. The shape key doesnt update unless you go into the driver property and hit the update dependency button.\n\n\n\n[The working one.blend](The_working_one.blend)\nThis is what i was hoping it would do. The only way I could use viewport visibility as a driver is to use a custom property on that object then use the custom property as a proxy.\n\nIs there a reason why it dont update if you use visibility as a driver from another object or is that a bug?\n\n**Steps to reproduce**\n[The not working file.blend](The_not_working_file.blend)\n\n- Open file\n- Click on Disable in Viewports icon on Cube object in outliner\nSphere shape should be change, but it doesn't" ]

[ "Eevee in VSE as Scene strips - erratic behaviour\nOperating system: Win 10\nGraphics card: Radeon RX580\n\nBroken: 2.80 version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-16 23:08, hash: 12da679fa094, type: Release\nbuild date: 16/06/2019, 17:07\n\nWhen using Eevee Scene Strips in VSE , the VSE viewport shows the wrong items on screen in OpenGL preview, and then the Render also does not show correct layering or camera moves\n\nOpen Blend file\nSee 3 scenes. \n- 2x animated (linked) scenes that render several layers in Eevee properly, then composite as expected\n- 1x Edit scene that has those linked scenes as Scene Strips in the VSE.\n\na) Observe in VSe that the viewport doesn't not reflect each Eevee scene in preview.\nb) Press render in VSE scene, and observe the render layers are broken and don't match the orig scene.\n\n[20190626.blend](20190626.blend)", "Background scene cause a crash in render animation\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: \n - 2.92.0 Alpha\n - 2.91.0\n - 2.90.1\nWorked: 2.83.9\n\nBackground scene makes blender unstable and cause a crash in render animation\n\n- Open default startup file.\n- Create a new scene named \"Scene.001\".\n- Assign default scene \"Scene\" as the background scene of \"Scene.001\" in scene properties.\n- Assign default camera as the camera of \"Scene.001\" in scene properties.\n- Hit render animation from render menu.\n- After a couple of frames rendered, blender crashes.\n\nTested in different situations i had some problems.\nI think assigning a background scene makes blender unstable in general.\nOccasionally crashes when opening a file which has background scene.\nThe worst case is render animation.\n\n[Background_Scene_Crash.mp4](Background_Scene_Crash.mp4)\n\nReproduction steps with this file:\n1. Open file.\n2. Start Render Animation.\n[#83852.blend](T83852.blend)\n", "OpenEXR pipeline improvements\n- [ ] Camera metadata\n- [ ] Chromaticity metadata\n- [x] Naming (more) compatible with other software\n- [x] Support outputting metadata from File Output in compositor", "weird viewport visual glitch\nOperating system: Windows 11 64 bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti Gaming X Trio\n\nBroken: version: 3.3.1\nWorked: cant bother sorry\n\nits like the position of the viewport has an offset relative to the orientation of the camera, and the viewport has a set size and cant change.\n\nfirst go to the layout workspace and have an animation playing (must have an animation playing for the bug to happen), then create a new viewport by sliding it like im doing in the video. then change the viewport into rendering mode like im doing in the video and when you resize the viewport, it has a set size and cant be changed and the position of all parts have an offset according to the position and orientation of the camera.\n\n", "EEVEE-Next: Known Issues\nThis task lists the minor missing features that are known for not yet working with EEVEE-Next.\n\nPriority of each task needs to be assessed and assigned.\n\n# LookDev\n- [ ] camera world alignement isn't working.\n- [ ] blur background isn't working.\n- [ ] diffuse contribution isn't taken into account.\n\n# Shadow\n- [ ] big performance bottleneck caused by rendering method\n\n# Hardware support\n- [ ] Metal backend doesn't support shadow rendering and GI baking yet", "Line Art - Freestyle Edges disappear when boolean solver is set to 'Exact'\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.75\n\nBroken: version: 2.93.0\n\nEdges marked as 'Freestyle Edge' disappear in the Line Art when there is a boolean modifier on the object that is set to 'Exact' as a solver. When the boolean is set to 'Fast' the lines appear. \n\n\nI just created a sphere that gets a boolean from a cube. I marked a few edges as 'Freestyle Edge' and when I switch between Fast and Exact it removes the lines. \n[Based on the default startup or an attached .blend file (as simple as possible)][LineArtBoolean_Bug.blend](LineArtBoolean_Bug.blend)\n", "Set as Background crashes blender instantly.\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080 Ti and RTX 3060\n\nBroken: 3.62\n\nI'm trying to do object tracking. Have tracked an object and clicked Solve Object Motion, then when I click on Set as Background Blender crashes instantly. Trying to load in a 400 frame 1920x1080 png sequence. Blender also crashes if I try to load the background image sequence via the camera properties (Background Images > Add Image).\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "EEVEE: Alpha Blend + Show Backface material is out of focus.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIn EEVEE when the DOF is on, and the focus is on the glass object, it is blurred.\nOnly when you set the focus on an object that can be seen through the glass, it becomes sharp.\n\nI set up a simple animation in the blender file, where the camera's DOF is fixed on the glass ball, and the background moves forward and backward.\nFocus is only caught when the background overlaps with the ball.\n\n- Open Attached File\n- disable and enable`Show Backface`\n[focus bug.blend](focus_bug.blend)\n\n", "persisting issue: MacOS, Blender's system device usage rights (info.plist) add camera & mic usage descriptions\nOperating system: MacOS (13.2.1) \nGraphics card: any\n\nBroken: (All Blender addons that would need external peripheral like camera or microphone access, will cause Blender to CRASH, because of MacOS)\nWorked: (it's a MacOS dependent issue (since maybe macOS 12?)\n\n*\n\"Termination Reason: Namespace TCC, Code 0\nThis app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an com.apple.security.device.camera key with a string value explaining to the user how the app uses this data.\"*\n\n\nInstall an anddon that would need camera / microphone access. After checking the checkbox in blender addon menu, Blender crashes (or at the point that addon is running code that would need such peripheral. Nowadays you cannot add it manually and this needs to be addressed globally.\n\nFIX:\nglobally add info.plist usage rights for camera, mic and other widely used peripherals for blender's MacOS version, since the current state of MacOS, doesn't allow addon's to access any of those, and it really hinders the blender as a core, those of course aren't used if not needed, but at the moment addon developer cannot have any modules that use any of those without MACOS causing the blender to literally crash. I hope this could be corrected asap. Before it was still possible to manually grant access to applications via macos settings, but alas, its not anymore possible.\n\n", "Alpha mode 'Straight' on Image Texture node behaves differently between Cycles and Eevee\nOperating system: Windows 10 Pro x64\nGraphics card: GTX 1080Ti for display, RTX 3090 for render\n\nBroken: 3.3.1\nWorked: I don't know\n\nWhen the `Alpha` property is set to `Straight`, the result is different between Eevee and Cycles.\n\n\n- Open the .blend file provided\n- Set one of the viewports to Material Preview and the other to Rendered\nNote that the results of the images are different\n[alpha_mode_eevee_vs_cycles.blend](alpha_mode_eevee_vs_cycles.blend)\n\nOriginal file\n[test leaking_ori.blend](test_leaking_ori.blend)\n", "Slow camera view navigation in Cycles rendered shading mode with many instances\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\n\nWhen looking through camera and navigating the viewport (with Lock Camera to View for example), the movement is much slower than a regular perspective view. This happens in rendered shading mode with Cycles, when many object instances are in the scene. Instances can be generated with Geometry Nodes or the old particle system. Also they don't even have to be visible on screen, you could be looking at a single cube somewhere to the side, and the camera navigation will still be slow.\n[camera navigation bug.blend](camera_navigation_bug.blend)\n\n\n - Use the provided file\n - Switch to rendered mode and disable overlays\n - Try looking around\n - Switch to camera view\n # Navigation should be much slower and unresponsive\n\n\n\n", "Cycles doesn't render smoke properly with adjusted clipping distances\nWindows 10 / AMD Radeon 6800 Series \nBroken: 2.79.1 1802d14\n\nI need to render a cross section of a smoke simulation. I set up the simulation and adjust the start/end clipping distances of the active camera to the desired values and in OpenGL viewport it works fine, renders exactly the cross section I want.  \nHowever, when I go into cycles and render it out, I get nothing: [*The second camera next to the active one is just for the convenience sake, mimicking the clipping values. Cycles behaves the same without it.*] \nI know that the materials are working fine because I can render it outside the camera's view: \nIf it helps, here's something else that I've found. When the end clipping distance goes beyond the Flow mesh (emitter) I get this weird result: \nAnd when it (end clipping distance) goes even outside the adaptive domain box, then it renders the smoke: \n[smoke.blend](smoke.blend)", "Wrong render region widget after MMB pan\nOperating system: Linux-5.10.0-7-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA TITAN V/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.27\n\nBroken: version: 3.0.0 Alpha\nWorked: N/A, probably never\n\n\nUsing MMB to pan Camera view to a User Perspective does not update the render region widgets from camera border to viewport border.\n\n\nWith the file attached:\n- Open the file\n- MMB in viewport to navigate from camera view to user perspective\n- Note how the render region widget still corresponds to the camera render region, not the viewport render region\n\n[render_region.blend](render_region.blend)\n\n", "Can't setting camera.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.19\n\nBroken: version: 3.6.1\n\n\nWhen I render, will jumpback to the camera.002\n\n", "Defocus Node with timeline camera change (Camera markers), problem\nOperating system: Windows\nGraphics card: GTX1060\n\nBroken: 3.4.1\n\nOn the frame where a camera changes (frame 3 in example), the defocus node returns a blurry image if rendering as animation\nNo problem if rendering the frame (frame 3 in example) as an image\n\n*from linked file:* Render as Animation (ctrl+F12)\n\n*from scratch:*\n- add 2 cameras with depth-of-field enabled\n- bind cameras to markers\n- add defocus node in compositing with z-buffer\n- render as animation (ctrl+F12)\n\n[camera_change.blend](camera_change.blend)" ]

[ "Freestyle Edges renders lines from cCurrent frame on all frames of an animation\nWhen rendering a sequence of frames using Freestyle, the lines from the current frame are rendered and place over every frame in the sequence. \n\n\n\nBlender 2.8 \nDate 2019-01-24 01:12\nHash: 1d908bffddb4\n\n**Steps to reproduce:**\n\n1. Load Factory Settings\n2. Set the timeline to 2 frames\n\n3. With the timeline marker at Frame 1, select the camera and add a LocRot key by pressing I\n\n4. Move the timeline to Frame 2.\n4. Rotate around the default Cube and Align Camera to View by pressing Ctrl+Alt+0\n\n5. With the camera still selected, add a LocRot key by pressing I\n6. In the Render tab, select Freestyle\n\n7. In the Output tab, select a file location for rendered output\n\n8. Move the timeline marker to Frame 1\n9. Render the Animation\n\n\n*Result*:\nThe lines from frame 1 carry over and are rendered on top of frame 2.\n\nFrame 1:\n\n\nFrame 2:\n\n\nAdditionally, if the timeline marker is set to Frame 2, the lines from Frame 2 are carried over and rendered on top of the other frame. The lines are only rendered from where the current timeline marker is set.\n\n\n\n\n*Expected Result*:\n\nEach frame is rendered with its own unique lines.\n\n**System Info:**\nOS: Windows 10 Education\nGraphics Card: NVIDIA GeForce GTX 1070", "freestyle camera not synched at rendertime\nOperating system: Windows 10 \nGraphics card: GTX 1080 TI\n\nBroken: 2.8, 91a155833e59\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n**Short description of error** \nFreestyle strokes are not aligned with the camera when the camera is animated. The lines are synched (line up with geometry) for single frame (F12) renders, but if the camera is animated, all the freestyle strokes are lined up only with the current frame at time of render-animation (Ctrl+F12)\nBased on the default startup or an attached .blend file (as simple as possible). Put a freestyle stroke on the default cube. Animate the camera position. Render animation. ", "Outline do not follow camera in workbench render sequence\n\n\n{[F6308987](0090.png)}{[F6308976](https://archive.blender.org/developer/F6308976/WorkbechBugReport.blend)}Operating system: Win 10 pro - ver 1803\nGraphics card: Nvidia Quadro K2100M\n\nBroken: 2.80, 7707bf203c0f, 2019-01-14\nWorked: (optional)\n\nOutline do not follow camera in workbench render sequence.\nWhen rendering a single image in the sequence, the outline do follow camera movements.\n\nRender the sequence in the attathed .blend file - error start at frame number 84" ]

[ "Blender crashes with Segmentation fault when selecting Render Preview in Cycles with GPU Compute\nOperating system: Linux-6.1.46-gentoo-gentoo-dist-x86_64-12th_Gen_Intel-R-_Core-TM-_i3-12100F-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 6400 (navi24, LLVM 16.0.6, DRM 3.49, 6.1.46-gentoo-gentoo-dist) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 3.6.0\nWorked: - (read description)\n\nWhen I try to render using Cycles on my GPU, blender immediately crashes with Segmentation fault, as the error message. Here are the logs that were shown right before the Segmentation fault:\n```\nI0903 17:06:40.864868 14239 device.cpp:511] Mapped host memory limit set to 12,302,073,856 bytes. (11.46G)\nI0903 17:06:40.865039 14239 device_impl.cpp:62] Using AVX2 CPU kernels.\nWriting: /tmp/blender.crash.txt\nzsh: segmentation fault blender-3.6 --debug-all\n```\nIt worked with =dev-libs/rocm-comgr-5.3.3-r2, but started happening after the new update of the package. I used to apply a patch that solved the problem of being unable to select the render device in Blender's options (27552#issuecomment-1379233453), but with the new rocm-comgr package, the original problem solved itself. The old version of Blender (version 3.5.1) that worked before rocm-comgr got the new update, doesn't work now.\n\n1. Open the Render properties tab and set the Render Engine to Cycles.\n2. Set the device to GPU Compute.\n3. Set the viewport shading to Rendered.\n\n", "Mantaflow - Bake not showing (when noise is used)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.7262\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.83\n\nEnabling Noise and then Baking Noise, the preview no longer shows. \n\nFrom Attached Blend\n\n\n - Bake Data\n - Play Animation (see preview)\n - Enable Noise\n - Bake Noise\n - Play Animation (No preview is shown)\n - Disable Noise \n - Play Animation (see preview)\n\n [smoke_noise.blend](smoke_noise.blend)\n", "Blender crashing when rendering with eevee, not with cycles however.\nOperating system: Linux-5.15.82-1-lts-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.42, 5.15.82-1-lts) AMD 4.6 (Core Profile) Mesa 23.0.0-devel (git-e20564cfdb)\n\nBroken: version: 3.3.2\nWorked: None, I've tried 3.3-LTS, 3.4 (both the default version provided through steam and manually selecting 3.4 LTS) and the daily-alpha build (with the daily-alpha build I reset settings all to default as well) All of these versions are the ones provided through Steam.\n\nWhen rendering in eevee some of my meshes completely bug out as if only part of them are rendering (I've looked at my normals and they're all fine) and after that my entire PC crashes, forcing a power cycle. The viewport display, when in rendered mode, looks fine in eevee but after rendering and before my PC crashes the viewport also messes up with my meshes looking bizarre. This issue does not occur in cycles when using CPU or GPU compute and other blender files work fine in eevee / cycles both in the viewport and when rendering. I also tried applying all modifiers despite needing a displacement on my torches to animate them but no luck. My blend file also becomes corrupt sometimes after the crash.\n\nSimply just hitting the render button with my current .blend file when in eevee. Sometimes the render goes through with broken meshes (which then I can close the render window and switch to eevee in my viewport display but my meshes will be all messed up and then my PC will crash, sometimes it crashes before the render output. \n\n\n[Dungeon Course.blend](Dungeon_Course.blend)\n\n[Dungeon Course.blend1](Dungeon_Course.blend1)\n\n[3.4 config.7z](3.4_config.7z)", "Blender just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "Wintab rarely gets into a bad state and prevents Blender startup\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked:\n\nFor a few months now, I have been getting a fairly rare, but reoccurring issue (maybe once a week on average) where Wintab gets into some erroneous state and prevents Blender from starting if the Tablet API setting of the Input preferences is set to `Wintab` or `Automatic`.\nWhen Wintab gets into this erroneous state and Blender is already open, Blender will crash if I attempt to open the User Preferences. I'm not sure what else might cause a crash when Blender is already open.\n\nBy adding extra logging to a custom build of Blender, I've determined that the crash when starting Blender occurs when calling the `open` (`WTOpenA`) function: GHOST_Wintab.cc#L85\n\nMy drawing tablet's software also reports an exception in `WTOpen`, the value of which appears to equal 0xC0000005 which I think indicates a `STATUS_ACCESS_VIOLATION` according to 596a1078-e883-4972-9bbc-49e60bebca55.\n\n\nIn the drawing tablet's software, this exception only occurs if I actually connect the tablet to my PC, whereas Blender crashes even when the tablet is not connected.\n\nCurrently, if I don't actually need my tablet, I'm working around the issue by starting Blender headless, changing the Tablet API setting to Windows Ink, and then starting Blender normally.\n\nI have already tried updating the drivers for my tablet to the newest version and it made no difference.\n\nIf I start Blender with `--debug-wintab`, all that's printed is:\n```\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release> .\\blender.exe --debug-wintab\nRead prefs: \"C:\\Users\\Thomas\\AppData\\Roaming\\Blender Foundation\\Blender\\4.0\\config\\userpref.blend\"\nLoading Wintab for window 00000000000910C4\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release>\n```\n\nEvery version of Blender I've tried between 2.79 and 4.0.0a crashes unless I have the Tablet API set to `Windows Ink`.\n\nI don't know the specifics of how Wintab is handled, but could it be possible to either catch the exception in `WTOpen` and allow Blender to continue loading, or to check for a connected tablet before attempting to call `WTOpen`, similar to what my tablet's software appears to be doing?\n\nUnfortunately, Wintab getting into this erroneous state where it crashes in `WTOpen` occurs too rarely for me to figure out how to reproduce it and I'm not even sure if it's Blender that is causing it to get into this state in the first place.\n\n", "object display as wire , invisible when overlay is turned off \nwin 10\nintel i5\namd radeon \n\nblender 2.8 \n6b39dc7672eb\n\n\nNot sure if it's abug or intended behaviour \n\nWhen an object is set to wireframe ( object properties , viewport display ) , when overlays is turned off , the object is not shown ", "Volumes look much much different in master compared to 2.79b\nWindows 10 pro x64\nGTX 970\nThread Ripper 1950x\n\n\n\nBasic volume shader with noise texture from build bot today doesnt look the same as 2.79b\n\n\n\n[untitled.blend](untitled.blend)\n", "Windows Lock Screen (Windows+L) writes a single character 'l' in the Text Editor\nOperating system: Windows 10 Pro 64-bit (10.0, Build 18363)\nGraphics card: NVIDIA GeForce 920M\n\nBroken: 2.83.3\n\nWindows Lock Screen (Windows+L) writes a single character 'l' in the Text Editor.\n\n- Open Blender.\n- Open a Text Editor.\n- Create a new text by pressing the \"+ New\" button.\n- Move your mouse on the Text Editor area.\n- Press Windows + L\n- Login by entering your password if you have.\n- Check that there is a letter l (lowercase of L) in the Text Editor.\n\nI'm a coder with python script and I can no longer use Windows + L, it's dangerous. The thing that makes me confuse is I used Blender Script since a few years, I always press Windows+L all the time, since Blender 2.79 which also have the bug, but I've never remark that bug, but I remark it today. If I understand, my code is full of letters 'l'. I tried to restart Windows but the bug is still there. I updated Windows recently about a couple weeks ago.", "3D View - removing Hotkeys for Toolbar/Sidebar throws empty keymap 3D View Generic error\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\n\n3D View - removing Hotkeys for Toolbar/Sidebar in the View menu throws empty keymap 3D View Generic error in the console.\n\n\nOpen Blender. In the View menu of the 3D View remove the hotkeys for Toolbar and Sidebar. Open the Console ...\n\n\n\n", "Blender Freezes and Crashes on AMD Laptops with White and Black boxes\nOperating system: Windows 10 & 11\nGraphics card: Radeon RX 6600M ATI Technologies Inc. 4.5.14800 Core Profile Context 22.4.2 30.0.15021.7000\n\nI've been using Blender with many versions. From 2.8, to 3.1 and the laptops have issues with all of them.\n\nBlender will freeze, white and black boxes will appear, and then Blender will crash and Windows will close it.\n\nI don't have exact steps, because it happens infrequently. It can happen as quickly as opening Blender, or take an hour of work.\n\nI am a teacher using HP Omen laptops with AMD CPU's and graphics cards. I have 21 laptops, and about 5-7 of them have issues with Blender. I have done a clean install of the graphics drivers, updated Blender to the most recent version, and tried everything I can think of. My personal laptop rarely ever crashes, so it's hard for me to replicate the issue.\n\nI have attached log files from crashes from multiple laptops. Half the laptops have been upgraded to Windows 11, and that doesn't seem to make it more or less likely to crash. My hope is these logs can pinpoint what's happening so I can fix it. I\n\nLog files created with `blender_debug_gpu_glitchworkaround.cmd`\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\nLog files created with `blender_debug_gpu.cmd`\n\n[blender_debug_output (1).txt](blender_debug_output__1_.txt)\n\n[blender_system_info (1).txt](blender_system_info__1_.txt)\n\nWarning and errors:\n```lines=10\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_multi_rect_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_multi_rect_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_text VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_text FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_uniform_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_uniform_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_INST_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_INST_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_rect_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_rect_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_flat_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_flat_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_LINE_DASHED_UNIFORM_COLOR_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_LINE_DASHED_UNIFORM_COLOR_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_3D_uniform_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_3D_uniform_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_desaturate_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_desaturate_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_composite_studio VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_composite_studio FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_merge_infront VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_merge_infront FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transparent_resolve VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transparent_resolve FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_effect_outline VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_effect_outline FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_taa VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_taa FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_1 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_1 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_2 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_2 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_antialiasing_263 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_antialiasing_263 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_414 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_414 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_449 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_449 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_401 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_401 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 GeomShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n | \n 6 | #define DFDY_SIGN 1.0\n | ^\n | (#310) Inputs that are integers should be qualified with the interpolation qualifier \"flat\"\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_wire_469 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_wire_469 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_wire_538 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_wire_538 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_solid_559 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_solid_559 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_stick_518 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_stick_518 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_499 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_499 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_489 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_489 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_wire_579 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_wire_579 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_background_276 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_background_276 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_uniform_color_1465 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_uniform_color_1465 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_grid_905 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_grid_905 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_885 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_885 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_groundline_924 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_groundline_924 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_loose_point_983 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_loose_point_983 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_point_1004 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_point_1004 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_facing_1022 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_facing_1022 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_grid_1055 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_grid_1055 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 GeomShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_vert_1170 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_vert_1170 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_1204 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_1204 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_pointcloud_1257 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_pointcloud_1257 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_gpencil_1230 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_gpencil_1230 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_detect_1272 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_detect_1272 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_dot_1410 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_dot_1410 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_shape_1429 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_shape_1429 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_wireframe_1589 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_wireframe_1589 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nERROR (gpu.debug): : GL_INVALID_VALUE : generated before glGenTextures\n```\n\nStack trace:\n```lines=10\nblender.exe :0x00007FF6F22F7D90 bli_windows_system_backtrace_stack_thread\nblender.exe :0x00007FF6F22F7010 BLI_system_backtrace\nblender.exe :0x00007FF6F228C530 blender::gpu::debug::debug_callback\nblender.exe :0x00007FF6F228C3F0 blender::gpu::debug::check_gl_error\nblender.exe :0x00007FF6F220EE50 blender::gpu::GLTexture::GLTexture\nblender.exe :0x00007FF6F21F8420 blender::gpu::GLBackend::texture_alloc\nblender.exe :0x00007FF6F21F2E20 GPU_texture_create_2d\nblender.exe :0x00007FF6ED267400 DRW_texture_create_2d\nblender.exe :0x00007FF6ED267810 DRW_texture_ensure_fullscreen_2d\nblender.exe :0x00007FF6ED2A4F90 workbench_cache_finish\nblender.exe :0x00007FF6ED25E4D0 DRW_draw_render_loop_ex\nblender.exe :0x00007FF6ED25F5A0 DRW_draw_view\nblender.exe :0x00007FF6EDBC7820 view3d_main_region_draw\nblender.exe :0x00007FF6ED56D940 ED_region_do_draw\nblender.exe :0x00007FF6ED1660C0 wm_draw_window_offscreen\nblender.exe :0x00007FF6ED165F10 wm_draw_window\nblender.exe :0x00007FF6ED165A10 wm_draw_update\nblender.exe :0x00007FF6ED1488F0 ghost_event_proc\nblender.exe :0x00007FF6EDCB1E10 GHOST_CallbackEventConsumer::processEvent\nblender.exe :0x00007FF6EDCFD680 GHOST_EventManager::dispatchEvents\nblender.exe :0x00007FF6EDCFE2E0 GHOST_System::dispatchEvents\nblender.exe :0x00007FF6ED14A980 wm_window_process_events\nblender.exe :0x00007FF6ED140110 WM_main\nblender.exe :0x00007FF6ECDA03C0 main\nblender.exe :0x00007FF6F246FE74 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFF7DCC7020 BaseThreadInitThunk\nntdll.dll :0x00007FFF7E582630 RtlUserThreadStart\n```\n\n----\n\n[blender_system_info_1.txt](blender_system_info_1.txt)\n\n[blender_system_info_2.txt](blender_system_info_2.txt)\n\n[blender_system_info_3.txt](blender_system_info_3.txt)\n\n[blender_debug_output_2.txt](blender_debug_output_2.txt)\n\n[blender_debug_output_1.txt](blender_debug_output_1.txt)\n\n[blender_debug_output_3.txt](blender_debug_output_3.txt)", "Blender 3.6 problem by rendering scene on EEEVEE (Freeze and crash GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9)\nOperating system: Windows 11 Home\nGraphics card: Radeon Graphics\n\nBroken: (example: 3.6, as found on the splash screen)\n\n\nBlender 3.6 doesn't render the scene as blender demo file in EEVEE\nOpen Blender splash fox of blender 2.90\nRender the scene\nFreeze and crash of blender when rendering on EEVEE\n\n", "CommandBuffer Failed: cycles metal integrator_ shade_volume --MacOS--\nOperating system: macOS-13.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 4.0.0 Alpha\n\nStarts rendering fine until the error. About 2-3 min. into the render.\n\n\nOpen the ziped blend file with 'Intel MacOS' blender 4.0a and hit render in the compositor!\n\n\nProbably related to: 104744\n\nPS: MacOS blender fails with most Volumes on latest major addons like PureSky, CloudScapes, etc... since blender 3.x .... ! The same applies when creating Volume emtys and volume Modifiers (mesh to volume & volume displace). At some point, blender will quit when clicking on the data tab (cloud icon) for volumes, as reported before.\n\n", "GPencil: Blender crash when GP3 enabled & you open the default 2D animation file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6\n\nBlender crash when GP3 enabled & you open the default 2D animation file & use the Draw tool\n\n- enable GP3 under the experimental features\n- save preferences and restart Blender\n- do File > New > 2D Animation\n- try to draw something.\n\nSince my 2D animation file is customized, I included it below.\n\n", "Blender crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "Render will not load anything but a cube silhouette in a new untouched file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R4 Graphics ATI Technologies Inc. 4.5.14830 Core Profile Context 21.09.04 27.20.20904.1\n\nBroken: version: 3.6.2\n\nSo, when I open in a new file, new to blender and following a tutorial, I go to render the cube immediately, but instead of a gray cube with shading, it is a transparent silhouette. I have touched nothing, just installed from steam, and opened. Then that, IDK what's going on with it.\n\nIDK what to put here, since I didn't do anything.\n\n\n" ]

[ "Daily build fails to open\nOperating system: Windows 10\nProzessor & Graphics card: AMD A8-5500 APU with Radeon(tm) HD Graphics 3.2 GHz\n\nBroken: 2.92a (daily build\nWorked: 2.91\n\nEXCEPTION_ACCESS_VIOLATION\n\ndownloaded 2.92 daily, unpacked it to C:\\Program Files\\Blender Foundation\\blender_2.92a_x64 and started it. Window opens for a second and disappears immediately. When opened in terminal, it returns the ACCESS_VIOLATION as shown in screenshot. I also attached the Crashlog from AppData/local/temp.\n\n\n[blender.crash.txt](blender.crash.txt)" ]

[ "`user_remap` fails silently when object is in edit mode\nBlender 3.6\n\nWay to reproduce:\n1) Create new empty blender project\n2) Select cube\n3) Enter edit mode\n4) Run the code below\n\nResults - mesh wasn't replaced and no errors occured. Expected - to either mesh to change or get some warning/error.\n\n```python\nimport bmesh\nimport bpy\n\nobj = bpy.context.active_object\n\ndata = bpy.data.meshes.new('test')\nbm = bmesh.new()\nbmesh.ops.create_monkey(bm)\nbm.to_mesh(data)\nbm.free()\n\nobj.data.user_remap(data)\nassert obj.data == data\n```\n\n", "Visual Keymap Editor\nWhile Blender's keymap editor is very flexible, it isn't very easy to get a clear overview, to spot conflicts, or to edit in general. \n\nIssues with the current keymap editor:\n\n - It's hard to get an overview of the keyboard\n - You cannot easily see how a given keymap works\n - It's very hard or impossible to tell which keys are free vs used\n - No way to print out to get an overview\n - It's not possible to tell if there's a conflict\n - It's not easy to see which entries are custom vs 'original'\n\nWe can solve these issues with a new approach for how the keymap editor should work:\n\n\n\nRather than just listing entries in a long nested list, we can do something more visual that shows the layout of the keyboard.\n\nAbove the keyboard, users can choose which editor and which mode to see. You can also pick if you want to edit the main keyboard, the keypad, or the mouse buttons:\n\n\nAn example of how the Mouse section could work:\n\n\nIn the top right you can choose which modifiers to take into account for the keyboard below. In this case Shift is enabled, so we only show items that are activated while holding Shift. \n\n\nThe keys themselves highlight if there is a shortcut added. The blue key here is the one that is selected. The dot means that it was customized. The warning symbol means there is a conflict on this key.\n\n\nWhen a key is selected, you can see the operator assigned to it below. This is similar to the current keymap editor:\n\n\nOn the left we have a way to search for all operators, filtered by the current context, which you can apply to the current key in one of two ways:\n - Either by first selecting the key, then searching for an operator and clicking Apply.\n - Or, you could simply search for an operator and drag it directly onto a key\n\nNormally you see a list of all operators which apply in the current context:\n\n\nYou can search this list to narrow the results down:\n\n\n\n\n", "When you clear measurements through View > Annotations, they don't vanish immediately\nOperating system: Windows\nGraphics card: GTX-2080\n\nBroken: 3.4.1\n\n\nDeleting measurement annotations appears to be broken because the UI is not refreshed until you change tool.\n\n\n1. Create some measurements\n2. Open View settings Tab\n3. Remove ruler Annotations\n\nExpected behavior: Measurements are removed and action can be undone.\n\nCurrent behavior: The Annotation is no longer visible in the annotation list, but still shown in edit view.\n\nHere is a screen recording: 185530\n\n", "Saved keymap changes do not remove \"Restore\" button\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.0.0\n\nWhen editing Keymaps, the keymaps very often incorrectly show \"Restore\" button even though there is no difference between saved and active keymap. This is very frustrating as it constantly keeps the user uncertain about the state of the keymap and often leads to corruption of keymaps due to unintended changes.\n\n1. Make a copy of a default keymap and save it under a new name.\n2. Make modifications to this new keymap\n3. Using the + button, save the the modified keymap under the same name to overwrite it\n4. Notice the \"Restore\" buttons under keymap entries are still present\n5. Open any section with the \"Restore\" button and then click it. Observe no changes to the section.\nResult: Restore button is still present but it does not restore any changes. This makes user think the given section is modified, while it is not.\nExpected: Restore buttons do not appear next to section with no changed entries.\n\nOR:\n1. Make a copy of a default keymap and save it under a new name.\n2. Make modifications to this new keymap\n3. Export this new keymap into a file\n4. Import this keymap back from the file to overwrite it\n5. Notice the \"Restore\" buttons under keymap entries are still present\n6. Open any section with the \"Restore\" button and then click it. Observe no changes to the section.\nResult: Restore button is still present but it does not restore any changes. This makes user think the given section is modified, while it is not.\nExpected: Restore buttons do not appear next to section with no changed entries.", "Persistent Base of Layer brush resets when selecting another object\nOperating system: gentoo ~amd64\nGraphics card: 1060\n\nBroken: all\nWorked: none\n\nPersistent Base resets in local mode\n1 select default cube\n2 subdivide it (Edit mode > W> Subdivide to 100 > Object mode)\n3 go to sculpt mode\n4 select layer brush\n5 select \"Persistent\" chbox\n6 Push Set Persistent Base\n7 Draw\n8 Draw with CTRL (it now worked like undo brush)\nNow all good works, and i can change anu brush - super useful\nbut\n9a select any other object/collection\n9b go to other mode ant went tot sculpt mode\n9c go to local mode (hotkey /) and went back\n10 Draw with CTRL (now it don't work right - it draw without Persistent Base)\n\nPlease see my screencast\n[2020-05-26 09-58-50.mp4](2020-05-26_09-58-50.mp4)\nIn global mode all works perfect\nIn local mode Persistent Base was gone\nThank you for great opensource sculpt tool!\n\nUpdate\n[2020-05-26 10-09-57.mp4](2020-05-26_10-09-57.mp4)\nBug happend If object has been selected agane too", "Colorpicker: Hue is not saved if Saturation is on 0\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 3.0.0 Alpha\n\nThis is an interesting papercut I noticed a lot. When you start changing the hue of a color but the saturation is on 0, it won't remember that hue if you close and reopen the color picker.\nThis can be annoying at times, especially when using the Square (SV + H) color picker layout.\nMy guess is that this is because the values that are actually stored for the color are the RGB values and not the HSV values.\nSo if a color is (0.5, 0.5, 0.5) and you change the hue, it is meaningless.\nBut perhaps this can still be improved since other painting applications are actually saving the HSV values and artists would expect Blender to remember what Hue is chosen even if the color is essentially grey.\n\nThis can be easily shown by changing the hue on a color with 0 saturation. The 2 hue sliders are of course not actually changing the color but they are also disconnected and not remembered.\nBut once there is a bit of saturation this is fixed.\n\n[2021-05-13 18-50-05.mp4](2021-05-13_18-50-05.mp4)", "Edge/Vert Slide fail to properly \"redo\"\nCurrently vertex & edge-slide use the mouse input to calculate which edge to slide, the direction to slide, and the **Even** toggle is set at runtime.\n\nUsing operator redo is not re-running with the same options, so redoing the action fails.\n\nWe could simply disable redo with this operator, however being able to toggle **Correct UV** is important.\n\nAdding this report to merge in duplicates, since there are various reports on this, which all have the same root-cause.", "Hotkeys malfunction after leaving text field with no input using IME(Chinese/Japanese/Korean)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.0.0 Release Candidate\nWorked: Unknow\n\n---\n\n\nUsing IME(Input method editor) like Chinese/Japanese/Korean IME, activate a text field then go back to 3D viewport while inputing nothing will make some hotkeys malfunction.\n\n\n - Default scene with any IME listed in the following image.\n - Click the default cube's name text field to activate the text field.\n - No input, go back to 3D viewport by clicking the 3D viewport area or right-clicking to cancel the operation.\n - Test {key A-Z}, for example press {key G} to transform the cube, the keys shouldn't be functioning.\n\n**Notes:**\n\n - After pressing {key A-Z}, similar IME-poping-ups might be shown as in these images: {[F12405595](图片.png)} The inputs are handled by IME but not being properly functioning like {key G} would not move the selected object.\n - Some other keys like {key 1-9}, {key Shift}, {key Ctrl}, {key CapsLock} and {key Space} are still functioning.\n - After the bug is reproduced, it is able to press {key Shift} to switch the mode of IME to fix the malfunction. And if right after canceling the text field input operation, press {key Ctrl RightMouseBottom} to finish a lasso select can also walk around the bug (but if there are already some inputs after the operation is canceled, doing {key Ctrl RightMouseBottom} won't fix the bug).\n - I found at the time been, Blender will automatically switch the IME modes (sorry I am not sure about which patch brought this feature), that means if in 3D viewport, the IME is automatically set to \"English\" mode and all inputs will not be handled by IME (this is the proper function); while in text field the IME mode is automatically switched to for example \"Chinese mode\" in Chinese IME. This \"auto-switching\" behavior is lost if the said work around is used to fix the bug, and in my case only after restarting Blender will bring back this feature.\n - I have tested a 3rd party Chinese IME \"搜狗输入法\" and in my opinion it has the similar bug as \"Microsoft Pinyin\": ", "Lost hotkey with save preset\n2.80\n\n\nI finally can replicate problem from 2.7x and it is still problem in 2.80. When you change some combination of hotkeys and save it to the preset. You lose some of them. On my GIF example Numpad 1 dissapear.\n\nSometimes it come back after restart Blender, but sometimes it is just gone.\n\n\n\n", "Multiple CNTRL Z replaces properties in driver\nWin7 64bit\n\nBroken: 2.79\n\nI was copying drivers from one object to another and hiding (H) those with already pasted driver. At some point I wanted to unhide previous object, so used undo instead of ALT H to bring back only one object. After object was revealed, I do not re-copy driver just paste what was already in memory. I make three undo's (just the step before copying driver), so I didn't expect this will corrupt driver's data. Would be better to make \"paste\" not happen, rather than changing it.\n\n*Original driver*\n\n*Pasted driver after some undo's*\n\n\n1. Copy driver from texture slot of left cube\n2. Hide left cube in viewport\n3. Paste driver in texture slot of right cube\n4. Pres CTRL Z three times until left cube will appear back\n5. Then repeat pasting driver from stage 3 -> driver's properties have been replaced by another\n[Paste_driver.blend](Paste_driver.blend)\n", "Keymap - Different shortcuts & keymaps are mistakenly merged \nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken: Blender 3.0\n\nWhen swapping the Select Edgering and Pick Shortest path operators around in my custom keymap, the two functions were mistakenly merged by Blender, despite being two different operators and despite having different inputs associated. \n[Keymap items disappear.mp4](Keymap_items_disappear.mp4)\n\nAs you can see at the end, there no longer was any keymap with Pick Shortest path within the Mesh category. \nTo further help trouble shooting, these were all the keymap items that had Shift+LMB associated within the Mesh category.\n\n\n**Steps to reproduce**\n1. Go to Edit > Preferences > keymap editor\n2. Load my keymap: [SW_WindowV2_done_a.py](SW_WindowV2_done_a.py) > For some reason it doesn't occur in Blender when factory reset, the only difference with my version is that I added a shortcut to Edit > Preferences > Ctrl + K, changed some navigation settings and loaded my custom theme before saving preferences, so it is very very close to being factory reset.\n2. Go to > 3D view > Mesh > Mesh (Global)\n3. Locate the Edge Ring select and Pick Shortest path entries\n4. Copy the operator names to the clipboard\n5. Replace the \"mesh.shortest_path_pick\" operators with \"mesh.edgering_select\"\n6. Replace the \"mesh.edgering_select\" operators with \"mesh.shortest_path_pick\"\n7. Set the options like the image below:\n\n8. Notice that when the buttons are configured to be the same (shift + LMB), click and double click are merged across two different operators. \n\nSee: [Keymap items disappear - Steps to reproduce.mp4](Keymap_items_disappear_-_Steps_to_reproduce.mp4)\n\nE: This bug also occurs when I remove the old \"mesh.shortest_path_pick\" operators and edit the top two items under 3D view > Mesh > Mesh (Global) to become \"mesh.shortest_path_pick\" with Shift + LMB click and Ctrl+Shift + LMB Click.\n\nAlso, it does not occur if I remove the old operators and add new items to the keymap with these operators.\n[2022-01-17 15-28-30.mp4](2022-01-17_15-28-30.mp4)\n", "Opening the Preferences/Render window replaces the current opened window with the other interface\nBroken: version: 2.83 (sub 13) \nWorked: Never\n\nOpening the Preferences/Render window replaces the current opened window with the other interface.\n\n\nMethod 1:\n* Open a new scene/or an existing scene.\n* Press F11 to render the scene.\n* Once rendered, go to the menu “Edit | Preferences...”\n* The preferences interface replaces the render interface in the same window.\n\nMethod 2:\n* Open a new scene/or an existing scene.\n* Go to the menu “Edit | Preferences...”\n* Press F11 to render the scene.\n* The render interface replaces the preferences interface in the same window.\n\nThere is no reason to replace a window/interface by an interface of different functionalities or with a different purpose.", "Error \"NotImplementedError: bevel: keyword \"custom_profile\" type 4 not working yet!\" when attempting to use custom_profile keyword in bmesh.ops.bevel\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.1.2\nWorked: No previous working version known\n\nTried to call bmesh.ops.bevel with custom_profile keyword argument. Got \"NotImplementedError: bevel: keyword \"custom_profile\" type 4 not working yet!\" error.\n\n\nOpen the attached blend file.\nGo to the Scripting workspace\nCopy the text in the Text editor\nPaste it to the python console.\n[bmesh bevel bug.blend](bmesh_bevel_bug.blend)", "'Load Factory Settings' doesn't prompt you to save your file or warn you that your changes will be lost\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.6.1 Release Candidate\n\nFile > Defaults > Load Factory Settings gives you one confirmation prompt, but this prompt doesn't indicate that you will not be further prompted to save your current file, nor does it explicitly state that your unsaved changes will be lost. This is a data loss hazard in my opinion.\n\nMake changes to any blend file, then load factory settings. You are not prompted to save your changes, or given warning that your changes will be lost.\n\n", "Wrong property changing `matrix_world` and destructive undo via RMB.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken:\nversion: 3.6.1\nversion: 4.0.0 Alpha\nWorked: never\n\nReturning to the original state during editing (or canceling) does not give the result that was when editing was started.\n<video src=\"attachment\" title=\"2023-08-16 21-40-53.mp4\" controls></video>\n\n1. Copy script and run\n```python\nimport bpy\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Test Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n col = self.layout.column()\n ob = context.object\n col.prop(ob,'name')\n col.prop(ob,'matrix_world')\n\nif __name__==\"__main__\":\n bpy.utils.register_class(Panel)\n```\n2. Quickly change the scale value for the object matrix.\n3. Press Right mouse button.\n\n" ]

[ "[Industry Compatible Keymap] Selectionmode operator dosen't work on a custom keymap \nWindows10:\nNvidia RTX 2080:\n\nBroken: example: 2.80, edc1b0167518 (Date: 2019-04-16 , 06:07)\n\n\n 1. Open Blender, Open the User Preference and navigate to Keymaps\n 2. Switch to the Industry Compatible Keymap** and export it into the Keyconfig Folder in Blender (blender/2.80/scripts/presets/keyconfig) and save preference and \n```\nclose Blender.\n```\n 3. Open Blender, Open the User Preference and navigate to Keymaps and switch to your custom saved \"Industry Compatible Keymap\"**\n 4. Go to the Section 3D View -> Object NonModal\n\n\nThere should be than a error:\n\n\n\nIf you switch to the Industry Compatible Keymap and than back to your Custom Keymap the error should be gone for some strange reasons.\n\n\nAlso here a video: gzzdm\n\n\n\n\n\n\n\n\n\n\n", "Switch to Vertex, Edge or Face Mode from any mode (ic_keymap.mesh_select_mode) key binding only works with the industry compatible preset.\nBroken: blender-2.80.0-git.03672e77836d-windows64\nWorked: probably, never.\n\n`ic_keymap.mesh_select_mode` key binding only works with the `Industry compatible` preset.\n\n\n1. Delete the Blender settings folder.\n2. Launch Blender, select the Blender 2.80 key bindings.\n3. Create a new key binding at 3d view -> Object mode -> Object mode (Global)\n4. Paste `ic_keymap.mesh_select_mode` as identifier. Bind to `\\` (it's not used anywhere).\n5. Go to Object mode, pres `\\`.\n6. Nothing happens.\n7. Go back to preferences, select the `Industry compatible` preset. \n8. Immediately select the `Blender` preset again. \n9. Now it is properly renamed to `Switch to Vertex, Edge or Face Mode from any mode` and you can now select a mode from the drop-down menu.\n10. Go to Object mode, press `\\`. It switches from the object mode to the mode you selected.\n11. Save the preferences, restart Blender. \n12. `\\` doesn't work anymore, switch to `Industry compatible` and back to fix again.", "Custom keymap with shortcut for ic_keymap.mesh_select_mode doesn't work after restarting Blender\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.34\n\nBroken: version: 2.81 (sub 1)\n\nWhen creating a custom keymap based on the industrial keymap, the shortcuts for switching between vertex, edge and face select (`1`,`2` and `3`) don't work after restarting Blender. It seems that the identifier `ic_keymap.mesh_select_mode` isn't recognized which results in `Warning: property 'type' not found in keymap item 'OperatorProperties'` being displayed on the console. When the preferences are opened after restarting Blender the shortcut entry doesn't display the correct title or properties in the custom keymap, however switching to the industrial keymap and then back makes it work again. \n\nThe cause of the problem seems to be that the operator `IC_KEYMAP_OT_mesh_select_mode` is only registered when the industrial keymap is loaded.\n\nCorrect shortcut in the industrial keymap\n\n\n----\nShortcut in the custom keymap after creation\n\n\n----\nShortcut in the custom keymap after restarting Blender\n\n\nThis issue was identified by [clawjelly ]] and reported on [[ https:*blender.stackexchange.com/questions/147717/shortcuts-dont-work-after-restart | Blender's StackExchange ](https:*blender.stackexchange.com/users/74720/clawjelly).\n\n\n\n - Select the industrial keymap in the preferences\n - Create a new keymap using the plus icon next to the keymap dropdown\n - (Optional) Switch to edit mode and verify that the shortcuts `1`, `2` and `3` work as intended\n - Close Blender, then start it again\n # Switch to edit mode and verify that the shortcuts `1`, `2` and `3` do not work\n\n\n\n" ]

[ "Mantaflow -> random missing square-shaped chunks in generated foam particle cache\nOperating system: Windows 10 Pro x64\nCPU: Intel i7 8700k\nRAM: 64GB DDR4-3200\nGraphics card: Geforce GTX1070\n\nBroken: 2.91.2 (Steam) & 2.92 Beta Daily Builds from 06. - 11. Feb. 2021 \n(what i have tested so far)\n\nFoam generated by Mantaflow has random square chunks missing. These missing chunks randomly change position (mostly per frame, but some stay in position longer ... ~5 Frames). Denser foam seems to generate visibly more of these. \n\nFound two similar bugreports, but not directly related to this specific issue ... maybe a grid-issue too?\n\nIts a simple scene (flood gate simulation), fluid domain, two fluid emitters (for the different water heights), some enviromental assets (fluid affectors -> collision ... a wall, a floor, four gates and a boat ... not related to the issue besides generating foam via fluid collision) ... short overview ...\n\n***Scene:***\n- 3840x2160px\n- 50FPS\n\n***Fluid Domain:***\n- Size = 3.47m x 19.9m x 1.81m\n- Res. = 256\n- timesteps minimum = 2\n- delete in obstacle = enabled\n- generate foam particles only (no splash, no bubbles)\n- everything else uses default values\n\n***Cache:* **\n- manually set destination (external USB3 HDD)\n- Frames = 1 - 2000; \n- Modular (resumable)\n- Format Volumes = OpenVDB\n\n- final baked cache (guide particles + foam particles + mesh) = ~160 GB\n\nFirst time i noticed this issue after baking foam and mesh (Blender 2.91.2)  \n\nA few days later (today) after further working on the scene and having switched to 2.92 Daily Builds (hoping anything would change)\n \nTop Down View (foam particles only) \n\nI would have provided videofootage too (showing how the holes change based on current frame), but nvidia shadowplay refuses to record blender for some reason (record desktop is enabled)\n\nHere is the original project file (before i switched to 2.92 beta), but be warned, baking this takes some time... [AE Mantaflow Schleuse A1.blend](AE_Mantaflow_Schleuse_A1.blend)\n\nKind Regards", "Geometry Nodes: Weird RayCast Accuracy\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 531.61\n\nBroken: version: 4.0.0 Alpha\n\n\nThe black dots inaccuracy only appears on the point domain. On the face domain everything is expected.\n\n", "2.81 shadows are incompatible with flat toon shaders and Data transfer modifiers\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nNew shadows in EEVEE are incompatible with flat (toon) shaders and custom normals\n\nCreate a simple Toon shader in Eevee (Diffuse BSDF->ShaderToRGB->ColorRampConstant->Mix->Output\nShadows are jagged and unusable, even on maximum Cube Size and Cascade Size and high sample count. In previous version 2.8, the shader will appear clean and sharp even on low settings\nIn addition, the new shadows do not respect normal editing via Data Transfer Modifier. Attach a Data Transfer Modifier to an object with the shader, Check Face Corner Data, Custom Normals, add a source mesh to source mesh. In mesh data under normals check Auto Smooth. in 2.81 the shadows will not obey the custom normals and will add shadows where there are none on the source. In previous version 2.8, the shader will obey the custom normals and not add extra shadows. See attachments\n\n\n\n\n\n[BadShadowsExample.blend](BadShadowsExample.blend)\n\n", "Create the shadow catcher in eevee give a black result\nOperating system: Windows 10 64bits\nGraphics card: NVIDIA GeForce RTX 2060\nBroken: 2.90, 2.91, 2.92, 2.93\nWorked: 2.83.12\n\nI followed the tutorial how to make a shadow catcher on eevee (). But it makes the result totally black when using version 2.90 and i've tried 2.91, 2.92, and 2.93. But the result is the same\n\n\n\nIn 2.83 the result is like this\n\n\n\n[shadow_bug.blend](shadow_bug.blend)", "Hair BSDF\nThis is a tough topic, I need to investigate it more.\nIdea: Dual Scattering using shadowmaps.\n\nEstimate : 2 weeks\n", "Regression: broken normal shading, sharp edges appear on smooth surfaces.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: 2.93, version: 3.0.0 Alpha\nWorked: 2.83.9, 2,92\n\nCaused by 1c22b551d0\nTo fix this, 5c4d24e1fd got reverted\nProblem still persists though...\n\n\nIn newer versions normal mapping looks broken, sharp edges appear.\nEevee and Cycles have same bug.\n\nupdated: [untitled.blend](untitled.blend)\n\ndifference in shading\n**2.93 on top, 2.8 down below:**\n\n\nThis effect appears even with very small angle of clean surface (without normal maps)\n\n\n\n<video src=\"2021-05-18_16-17-05.mp4\" title=\"F10122604/2021-05-18_16-17-05.mp4\" controls></video>", "Cycles principled BSDF artifact with transmission and IOR 1.0 (GPU)\nOperating system: win 10 pro\nGraphics card: 1070\n\nBroken: 2.79b\n\ncircular banding with transmission and ior set to 1 using principle shader. (only happens in gpu rendering not cpu)", "Denoising + negative lamps = black and white artifacts\nOS X Sierra 10.12.6,\nNVIDIA GeForce GT 750M 2048 MB\nIntel Iris Pro 1536 MB\n\nBroken: 2.79\n\nSimple scene with negative lights gives bad artefacts with denoising enabled.\n\nJust render the attached .blend file.\n\nAttachments are:\n* Denoised image with artefacts\n* Non-denoised image without artefacts\n* .blend file\n\n  [denoising.blend](denoising.blend)", "Render artefacts with GPU / motion blur\nOperating system: Linux-5.4.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.80.02\n\nBroken: version: 2.91.0 Alpha + official releases and master from build bot.\nWorked: none that I tried so far\n\nI get weird rendering artefacts where some buckets render different than others. This only seems to happen when:\nRendering with motion blur AND rendering with GPU AND rendering under a Linux OS AND the shutter position is set to \"start\" or \"center on frame\". \"end of frame\" renders fine.\nIt's completely weird as it doesn't happen under Win10 (at least in my case). I completely reduced a production scene to the point where some basic geometry and particles with a sky shader show the problem.\n\n- Open the attached blend file:\n[SHOT060_MPS_v33.blend](SHOT060_MPS_v33.blend)\n- Press F12 to render\n- If you're under Windows (and maybe Mac) or render with CPU you should be fine. Otherwise you should get something like this:\n\n- Switch the motion blur position from \"center on frame\" to \"end on frame\" and render again:\n\nEverything fine\n- Now switch back to \"center on frame\" and switch the render engine to CPU and render again:\n\nFine again.\n\nSo it only affects Linux, \"start or center on frame\" and GPU rendering.\n\nP.S.: Might be somehow related to T76792 although I can't reproduce his problems. But the description sounds similar and he's on Linux, too.\n\n", "Viewport render still cannot render \"non-antialiased\" Outline overlay.\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nHi, I'm trying to get a non anti-aliased image out of the viewport render option, but the final image is still anti-aliased.\n\n\n\nUsing these settings in the preferences:\n\n\n\n\n", "Black outlines around animated Objects when Scrubbing/Playback.\nOperating system: Windows 10 64 Bits\nGraphics card: GTX 1080 TI.\n\nBroken: version: 2.83.8 hash: 7c027f9480a9\nWorked: version: 2.83.4 hash: `abb7364912` (commit date: 2020-02-23 23:00)\n\nThere are some weird black outlines popping out during anim playback or scrubbing. \n\n***P**\n{[F8400153](spot.jpg) size = full}\n\n\n* open the file\n* If it is not already set, set viewport shading to material preview (that's where you can easily spot them)\n* playback the animation or quickly move the object\n\nThe black outlines will appear but the moment you stop they'll disappear, so you can screen capture the moment to check their existence ***P**.\n\n[Black.blend](Black.blend)\n", "Shadows stop working properly when changing render pass in viewport.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1404\n\nBroken: version: 3.5.1\n\nWhen doing a certain shading setup and changing render pass, the shadows break.\n\n- Create a new project, keeping the render engine to eevee\n- Make a new material and apply on default cube\n- Connect any image texture into the color input of principled bsdf\n- Connect any image texture into the normal input of principled bsdf while setting its color space to non-color\n- Switch viewport shading to rendered\n- Switch render pass to shadow and then back to combined\n- The lights will now not produce any light unless their shadow setting is turned off\n\nAny other nodes added before or in-between the image texture node do not seem to affect the result.\nThe shadows will stay like this until blender is closed and reopened again.\n\n", "Baking Procedural Wave Textures\nOperating system: Win10\nGraphics card: Nvid 2080ti / 3090 \n\n3.4 (and others)\n\nCannot bake these textures correctly. \n\nCreate an object. \nAdd a wave texture, set it to uv, and scale it to show many even lines. \nAdd a color ramp to tighten those lines, setting it to constant. \nPlug this into the bump/normal to make raised lines. \nNow bake this. \n\nThe lines will be a broken mess most of the time. I have tried almost every trick I can find/think of, and nothing makes this better. \n\nI am not sure it's a bug, but it is certainly a problem.\n\n", "Mantaflow: Crash when setting a Guide Fluid Effector\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.3.0\n\nAfter setting a mesh as a \"Guide\" fluid effector, checking the \"Guides\" box in the fluid domain settings crashes Blender. \n\n- Open attached file,\n- go to the fluid domain settings\n- check the \"Guides\" box. \n[Fluid_Guide_Crash_01.blend](Fluid_Guide_Crash_01.blend)\n\n", "CYCLES: Surfaces inside volumes are Not Lit or Shadowed by the volume if the volume is not visible to Camera Rays\nLinux Mint Mate\nGTX 1050\n\n\nBlender 2.81 Alpha\n2019-09-27 22:44\nHash: 1c1a3198af9d\n\n\nDiscovered while trying to catch shadows from volumes on surfaces for compositing.\n\nSurfaces inside of volume meshes are not shaded (lit/shadowed) by the volume if the volume is invisible to camera rays\n(checkbox in Object Properties -> Visibility -> Ray Visibility -> Camera)\nAs far as i can tell this also affects Holdout.\n\n\n\n\nCurrent workaround: make sure volume IS visible to camera rays, and instead bypass it in the volume shader using the Camera Ray socket on the Light Path node\n\n\nTo Reproduce:\n\nOpen attached .blend , press render\nNote the missing shadow/light where the volume cubes intersect the default cube.\n\nI have in the .blend also included the \"expected behaviour\" by using the workaround, switch the Scene from \"Bug\" to \"Workaround\" and press render again.\nNote the shadow/light now covers the default cube properly." ]

[ "Smoke Shadow glitches in Cycles (workaround only with Fluid \"Empty Space\" option)\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D700](D700) OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.21\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79\n\n\nWeird artifacts and boxes appear in the shadows of smoke simulations\n\n\nI've seen this happening in different simulations with different results. Sometimes it is a big square in the shadows like in the image attached. Sometimes it's just little squares.\n\nGenerally speaking the workflow I'm following when I see these errors is the following:\n\nSet the scene to cycles\nCreate ground plane\nCreate Sun Light\nCreate smoke domain\nCreate smoke emitter with particles\nSet smoke flow to emit fire and smoke from particles\nCaches simulation\nRender with Cycles\nGlitches appear in the shadows of the smoke\n\nAttached is a blend file and the render result with glitches\n\n[VolumetricsTest.blend](VolumetricsTest.blend)\n\n" ]

[ "Greasepencil z fighting alpha issue\nHi,\nnot too sure if this is known issue or any fix but I am getting this alpha issue from certain angle when I have 2 different grease object. \n\n", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "Select Loop Inner-Region issue\nWin8 64bit | GTX680\n\nBroken: 2.77 509270e\n\nWhen working with face loop, this tool doesn't always work as expected.\n\n\n\n\nNot sure if this can be a bug. Please check.", "Collection visibility animated\nI need to recap with @brecht and @Sergey why we didn't push for this in 2.80. If it is doable and doesn't break our design, we should support this.\nBasically only the datablock settings (global viewport visibility, and renderability).", "crash when changing viewport shading to wireframe mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14760 Core Profile Context 21.2.3 27.20.14535.3005\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-04-23 20:25, hash: 17fca62fff9b, type: Release\nBroken: 2.81\nWorked: 2.80\n\n\nif you have a high poly mesh and try change the shading mode to wireframe. depending on the model it constantly crashes.\n\n\nI noticed this trying to make a retopo of a character. I tried to check what was causing de crash by deleting each object and testing the wireframe. \n\nI deleted everything but the main body mesh, without any uv map, vertex color or any other thing that could make it heavier, and also I tried reseting factory settings.\n\nI would send the file but its 200mb, the main mesh has about 4million vertices.\n\n\nthe crash doesn't happen when changing to eevee or solid view, it only happens when changing to wireframe.\n\nImportant note: if you DON'T move the camera after opening the file before changing to wireframe it doesn't crash even if you go to solid and wireframe back and forth as shown in the video bellow \n[2021-05-01 14-18-16.mp4](2021-05-01_14-18-16.mp4)\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[untitled.blend](untitled.blend)\n- open the file above\n- rotate it about 180degrees\n- activate wireframe", "Random rectangles 'missing' when rendering with optix + motion blur\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03\n\nBroken: version: 3.5.0\n\nEdit: I downloaded 3.5.1 and It still occurs there\n\nWhen I render a scene that uses motion blur with optix, there are randomly rectangles/sections where it skips straight to the background. Its random and only exists in some frames, and does not appear when using cuda. The object it appears on (or near) has motion blur disabled.\n\nIts very random and I'm not sure how to reproduce it in a simpler scene. I've had it happen in several different complex scenes and its always been an issue when ever theres an object that has motion blur disabled\n\nOptix with Motion Blur\n\n\nOptix without Motion Blur\n\n\nCuda with Motion Blur\n\n\n", "Broken material assigment after changing mesh-linking to object-linking\nWindows 11\nNvidia RTX 2060 super\n\nBroken: blender-3.2.0-stable+daily.e05e1e369187\n\n\nOn objects with multiple material slots, the currently selected slot gets bugged when switching from object-linking to mesh-linking. It allows the user to select a different material for each link type, which seems to trigger the bug and has lingering effects. For example, in geometry-nodes setting the material becomes unpredicatable, with material names seemingly swapped.\n\nFrom the provided blend file or startup scene:\n1. create a new material slot\n2. pick a material for this slot\n3. swap the material link type between object-link and mesh-link\n4. select a different material for the same slot\nThe material or slot is now bugged. Geo nodes 'set material' will become unpredictable.\n\n[bug_slots.blend](bug_slots.blend)", "Solid mode in EEVEE looks pixelated (NEW)/ CYCLES in GPU 3D AMD driver problem (OLD KNOWN Problem)\n**Xeon E3 1230 V2 - 16Gb RAM**\nOperating system: Windows 10\nGraphics card: AMD RX 570 8Gb VRAM\n\n**Blender Version 2.92.0**\n\n\nI opened an old work of mine that I was mading on same 2.92.0 before. Today when I opened the solid mode as default and appears very pixelated and like matrix effect, as AMD error was giving in Cycles before... \nMaybe is AMD driver problem or materials render data. \nSome months ago was Cycles incompatibility. Cycles is still working only on CPU and now Eevee have problems in solid mode. \nI've tested in 2.83.5 version and worked. \n\n\nattached photos. In 2.92.0 isn't \n\n**Work in a project\nfews days later (about 20 days) open the archive and solid mode was pixelated  \n\n[estilizada unir cabeca retopo.blend](estilizada_unir_cabeca_retopo.blend)\nBased on the default startup or an attached .blend file (as simple as possible).", "Modifiers disabled in viewport are not rendered if the object is in edit mode\nVersion 2.83\n\n\n - Open: [medieval_house_lights_camera.blend](medieval_house_lights_camera.blend)\n - Render with the object in edit mode and then in object mode.\nScene in object mode\n\nRender:\n\n\nScene in edit mode:\n\nRender:\n", "Wire objects that are being displayed on front only updates visibility after interaction\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.1 30.0.14023.7007\n\nBroken: version: 3.2.0 Alpha\n\nThis problem is similar to the one found in #84717, but in this case it is only affecting objects that are marked as in front and wired mode. I noticed it happening in a rig, but It can be applied at anything that is wire.\n\n\n- Using Any object go to viewport display and mark in front and set it to wire in the display as. (you can also use a rig with custom shapes, e.g. the one in rigify.)\n```\n{F12895660}\n```\n- Disable and then Enable Overlays\n[2022-03-03 11-21-26.mp4](2022-03-03_11-21-26.mp4)", "Edit mode. Wire become non-selectable dependent on resolution (regression)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWithout multisampling wire just disappear and with multisampling it is still visible but not selectable.\n\n[2019-09-14_23-07-53.mp4](2019-09-14_23-07-53.mp4)\n[2019-09-14_23-09-58.mp4](2019-09-14_23-09-58.mp4)\n\n\n\nTry to select loop and zoom in-out with and without viewport multisampling. Here the file, but bug will appear even with UV-sphere.\n[b.blend](b.blend)\n\n", "Objects with \"In Front\" don't appear when overlays are reenabled until viewport update\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBut works on:\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: Mesa Intel(R) UHD Graphics 620 (WHL GT2) Intel 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.91.2\n\nMight be the same as #102199 (Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)) (which was bisected down to 0f95f51361)\n\nWhen an object (specific ones) is set to be displayed in front of everything else, it will not come back immediately when reenabling the overlays. This happens only in solid shading mode as far as I can tell.\n\nThe objects affected by this are first off all objects which have some kind of lines, so camera, lights, the wireframes of meshes, outlines of reference images, empties, ...\nThen there is also the armature which is special in the way that it is rendered solid, but it also vanishes just like the lines.\n\n1. Add an armature\n2. set it to In Front in Armature > Viewport Display\n3. toggle the viewport overlays on and off (that button next to x-ray)\n4. if your rendering was set to solid shading, the armature should be gone now\n5. rotate the view, the armature will reappear\n6. you can do the same with the default camera and light and on the cube if wireframes are enabled (globally or locally on the cube) \n\n", "Mask invisible on object with modifiers when entering sculpt mode\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 3.0.0 Alpha\nWorked: unkown\n\nWhen selecting a previously unselected object with a modifier and a sculpt mask, the mask is invisible at first when entering sculpt mode.\nPainting the mask reveals it.\n\n- Create an object with a modifier (e.g. mirror or array) and paint a sculpt mask on it. Or use the file attached.\n- Outside the sculpt mode first make sure the object is unselected, then select it and enter sculpt mode.\n- The object appears with no mask visible, still you can not sculpt the masked parts.\n- Painting the mask reveals it.\n\n[mask.blend](mask.blend)\n\n[mask.mp4](mask.mp4)", "New geometry nodes viewer overlay makes mesh edit mode overlays invisible\nOperating system: Linux-5.19.10-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.4.0 Alpha, current master\n\n\n| {[F13588717](image.png) size=full} | {[F13588720](image.png) size=full} |\n| -- | -- |\n", "Fake Dependency Cycle: 'Disable in Viewport' depends on 'Disable in Renders'\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.2.2\n\nDriving hide_render from hide_viewport causes a dependency cycle\nwhile the error occurs on all objects, the driver does seem to work on some objects, but not others. In the default scene for example, the driver works with the camera, but not the cube or the light\n\n- in the outliner, edit the filter to display the `Disable in Viewport` option.\n- Right click the `Disable in Viewports` icon on any given object\n- Copy as New Driver\n- Right click the `Disable in Render` icon of the same object\n- Paste Driver\n[render visibility driver issue.blend](render_visibility_driver_issue.blend)\n\n" ]

[ "Wireframe Displays Strangely in Eevee (Rendered, material Preview)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92\n\nCaused by 000a340afa\n\nThe wireframe display in Eevee viewport is disappearing depends on the viewing angle. \n\nBased on default startup\n1. Delete default cube\n2. Shift A and add a grid\n3. Turn on wireframe in Viewport Overlays\n4. Switch to Rendered view mode\n5. Orbit the viewport around the grid, see how the wireframe disappear\n\n\n\n\n" ]

[ "High subsurface on principled bsdf causes glowing edges on polygons for walk\nBroken: Current main.\nWorked: Never.\n\nUsing high values for principled bsdf subsurface scatter causes glow effect on polygon edges. This happens with walk but not burley. \n\nAttached is a simple blender scene with a ball. Rendering you can see the squares polygons on the ball have glowing edges. I know that the walk radius calculations were changed around blender version 3.4. If you use burly the ball renders smooth. \n\nGraphics - set to optix, experimental, cycles.\nShape - make sure its set to smooth shading. You may have to recreate the stock sphere and set it to smooth shading.\n\n", "Geometry Nodes: Mismatching data types connections work differently from other node editors\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.5.0\n\nFloat math node overrides color data, even though it is muted. Same setup works in shader editor without problems.\n\nOpen file and activate *Viewer* in GN. Expected result: colored output (judging by shader area behavior)\n\n", "Selecting a Add Shader node in the Shader Editor window no longer highlights Shader Node line in Dope Sheet window\nOperating system: Windows 10\nGraphics card: RTX1050\n\nBroken: 2.91, 2.92, 2.93, 3.0.0\nWorked: 2.83\n\nCaused by c5bdbc340a\n\nSelecting an Add Shader Node containing keyframes would automatically highlight the corresponding Shader Node line in the Dope Sheet window\n\nAdd two or more \"Add Shader\" nodes to the Shader Editor window. Set a keyframe for each of the Add Shader nodes.\nOpen the Dope Sheet window and view the ShaderNodetree lines have been added with corresponding keyframes.\nVersion 2.83 - Clicking on each of the Add Shader nodes in the Shader Editor window will highlight the corresponding ShaderNodetree row in the Dope Sheet window.\nVersions after 2.83 - Clicking on each of the Add Shader nodes in the Shader Editor window no longer lighlights the corresponding ShaderNodetree row in the Dope Sheet window.\n", "Several inconsistencies in Cycles BSDF\n1. Defensive sampling\n ~~in `bsdf_microfacet_sample()` it is checked against `(path_flag & PATH_RAY_CAMERA)`, but `bsdf_microfacet_eval()` is always using the pdf of defensive sampling, except when fresnel is one. Also, it's worth verifying if defensive sampling is still practical.~~ (bf82f9442c)\n2. `sd->Ng` or `sd->N`\n ~~both `bsdf_microfacet_sample()` and `bsdf_microfacet_eval()` have an argument `Ng`, but we pass `sd->Ng` to the former and `sd->N` to the later, so checks like `dot(Ng, wo) > 0` don't give the same result.~~ (063a9e8964)\n `bsdf_is_transmission(sc, wo)` checks using smoothed normal `sc->N`, but in BSDF sampling and evaluation `(sd->type & PRIMITIVE_CURVE) ? sc->N : sd->Ng` is used.\n3. `ClosureLabel`\n * In `surface_shader_bsdf_sample_closure()`, we accumulate the result of all the closures, but `label` is solely determined by the closure chosen by `bsdf_sample()`. Maybe this is fine but the logic seems weird.\n * For `CLOSURE_BSDF_HAIR_CHIANG_ID`, the label is determined by the `wo` direction in `bsdf_label()`, but determined by the interaction number in `bsdf_sample()`. Maybe `label` should always be `LABEL_REFLECT` because hair closure handles internal absorption itself.\n4. Anisotropy\nBehaves differently for Glossy and Principled BSDF. Principled BSDF uses remapping from [Disney]() and only allow positive anisotropy. Glossy BSDF does not use remapping, allow both negative and positive anisotropy, and treat the distribution as isotropic if `anisotropy < 1e-4f`. The last piece of logic is repeated in svm, osl and `shader_nodes.cpp`\n5. `eta` and `label` required by path guiding\nis inconsistent in BSDF sampling and evaluation.\n", "Color Ramp node keyed colors and keyed positions jumps to the next color stop when adding or removing color stops\nBroken: 2.7x, 2.8x\n\nThe keyed color and position should be assigned to the color stop itself, not it's order. As of now it follows the order of stops, so the keyed color and position jumps from one color stop to next one when a color stop is added or removed.\n|[2020-06-16 17-27-47.mp4](2020-06-16_17-27-47.mp4)|[2020-06-16 17-13-58.mp4](2020-06-16_17-13-58.mp4)\n| -- | -- |\n\n- open blender \n- go the shader editor\n- make a new material\n- add a color ramp node\n- Press \"i\" with the mouse hovering the black bar to key the color.\nnow the white color stop and do the same, key the color by pressing \"i\" over it.\nnow select the black color stop and remove it by clicking the \"-\"\n- press space bar to play, the keyed color will jump from the black one that was removed to the white one.\nThe same happens if you key the color stop's position instead of it's color.\nIt also jumps when adding in a color stop instead of removing one.\n", "Cycles shading glitch\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.4.1\nWorked: ?\n\nCycles shows incorrect shading, also different from Eevee. (The file is very simplified just to showcase the problem)\nI'm thinking it is a variation of T99933 bug but not sure so tell if that's the case\n\n[bug.blend](bug.blend)\n1) Open the file, switch to rendered view. Normals should look like this\n\n2) In the material disconnect the alpha socket, now it should look different.\n\nIs alpha supposed to affect normals at all?\n3) Repeat the same in Eevee, results look consistent", "TexBlendNode Python property tooltip incorrect\nBlender 2.8 \n\nI can not change the Progression or the Flip Axis for the Tex Blend Node with python. \n\nIt returns with an error that says \" no attribute use_flip_axis\". I thought this was my fault so I reached out for help on the Stack Exchange> [here ](how-do-i-change-the-blend-node-to-vertical?)\n\nThey think this is a bug or missing API?.. I checked online but could not see this bug reported so I thought I would let you guys know.\n\nI have used a rotate node to work around the problem but I am sure you guys would be able to fix this issue with ease.\n\n[#69973.blend](T69973.blend)", "Ray Visibility (glossy, diffuse, transmission) on light sources generate a different result when using hit by the BSDF or next-event estimation \nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nWhen changing/disabling the ray visibilities on a light source (glossy, diffuse, or transmission), the result becomes\ninconsistent when using only BSDF sampling, next-event estimation, or MIS between both.\n\nThe reason for that is that the contribution of a light source is completely neglected when the type of the BSDF closure used for sampling the direction is disabled on the light source.\nDuring next-event estimation, on the other hand, the light source ALWAYS contributes. Only the BSDF evaluation components multiplied with the light contribution differ [ eg. instead: L*glossy + L*diffuse -> L*diffuse if glossy is deactivated].\n \nThe example shows a scene with one big rectangular light at the ceiling, where glossy rays are disabled on. \nAs you can see, the BSDF image is darker compared to MIS, and the NEE version is a little bit brighter.\n\n\nThe MIS image is more or less a blended version of BSDF and NEE.\nBecause both BSDF and NEE do not converge to the same result, the MIS one is inconsistent/biased.\nSince the blending factors/mis weights depend on the sampling strategies, the result changes when using path guiding or the light tree.\nThis makes these optimized strategies unpredictable and can confuse the artists.\nIn the worst case, they report bugs on for the light tree and path guiding.\n\nA WIP fix is proposed in [D16965](D16965)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Image Editor don't change to active texture if there is one texture node in material \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.4.0 Alpha\n\nWhen there are two texture nodes in Shader Editor Texture Editor switches to the active texture when you clicks on any Image texture node. But when there is only one texture node Image Editor ignores selecting that node. It makes it inconsistent and may confuse user with showing him the wrong texture\n\n\nCreate two materials. In one of them create one image texture node and a texture. In second one create two or more image nodes with textures. Try to switch between materials and texture nodes.\nOr open blend file.\n[texture-pick_bug.blend](texture-pick_bug.blend)", "File->Open Recent behaves different from Edit Override Library on Linked Object Materials\nOperating system: Windows 10\nGraphics card: AMD Radeon & NVidia 1060Ti\n\nBroken: 3.6.2\nWorked: Unknown\n\nWhen using File->Open Recent to change blend files, the overridden materials on a linked object are getting broken/changed. When using Edit Override Library on the linked object, the materials remain consistent.\nI am seeing a behaviour difference that breaks the material order when using File->Open Recent versus Edit Override Library. When using File->Open Recent it is changing the order of the materials destructively. This is related to linked objects and overriding their materials.\n\nDefault startup, 2 files needed.\nWhen using File->Open Recent the steps are:\n\n1. Create an object that will be linked. In this case, default cube\n2. Color it with 3 materials (Red, Blue, Green)\n3. Create a new blend file\n4. Link in the cube from step 1\n5. Make it a library override (Object->Library Overrides->Make)\n6. We are going to change material 3\n7. Select Material 3 change to Object Data\n8. Select the default material\n9. Change the color\n10. Save the file\n11. File->Open Recent->(File from step 1)\n12. File->Open Recent->(File from step 10)\n13. Notice that Material 1 and Material 3 are now the same materials\n\nWhen using Edit Override Library the steps are:\n\n1. Create an object that will be linked. In this case, default cube\n2. Color it with 3 materials (Red, Blue, Green)\n3. Create a new blend file\n4. Link in the cube from step 1\n5. Make it a library override (Object->Library Overrides->Make)\n6. We are going to change material 3\n7. Select Material 3 change to Object Data\n8. Select the default material\n9. Change the color\n10. Save the file\n11. Item->Edit Linked Library\n12. Item->Return to Original\n13. Notice that the Materials are in the order and color from step 7, no change\n\nThis requires several files as the initial set up gets broken. Easiest to follow the steps.\nFiles are included, they are:\n\nLinkedObjectMaterials.blend -> This is the file with the object that will be linked into the other files\nOverrideTest.blend -> File has a link to LinkedObjectMaterials.blend and it has a changed material that was set up and tested using EditOverride Method and the materials are OK\nFileOpenRecent.blent -> File has a link to LinkedObjectMaterials.blend and the 3rd material was changed and now both the first and third materials are the same.\n\nAsk if any clarifications are needed. It took me a while to narrow it down to this case.\n\n", "Improve UX for interaction of modifier stack and node editor\nWhen a non-nodes modifier is selected as active modifier there is no indication or way to change that in the geometry nodes editor and it's very confusing for the user, especially when the properties editor is not displaying the modifiers panel.\n\nThis is related to #84927\nA potential solution has been proposed there as well (move towards interface similar to shader editor and material slots).", "Remove 'Use Nodes'\nWhen using Cycles and editing materials, the user is presented with a button called Use Nodes. This is confusing and adds an extra step before being able to set up materials.\n\nIt might be nicer to simply have the material use nodes always. Materials without nodes doesn't even really make sense when using Cycles as they are central to material editing and creation.\n\n", "Allow node inputs named A and B to be swapped\nPossible fix to allow node inputs to be swapped.\n\nThis is defined in the `node_link_socket_match` function.\n\nReported in chat by @SimonThommes \n\nIt may be a better solution to add a swappable flag to sockets.", "Geometry Nodes: Curve primitives issues with object material\nBroken: version: 3.2.0 Beta, 3.3.0 Alpha\nWorked: n/a\n\nMaterials assign to the object don't work in some cases for curve primitives created in the geometry nodes tree.\n\nOpen file, you will see that the star doesn't get the red object material.\n\n[curve_object_material.blend](curve_object_material.blend)\n\nUnhiding any of the hidden nodes (Grid or Set Material) will make the object material show up.", "Design: Graph Editor Curve Display\nThere are a few issues with the display of curves in the Graph Editor mentioned in the Paper Cuts devtalk thread. However while technically simple to change the drawing, it needs to stay consistent and clear, which is why this Design task exists.\n\n**Issues**\n* Locked Curve keyframes look like they are active\n* Curves are drawn in the same thickness even outside the range they can be edited in ?sorting=hot#\n* Location/Rotation/Scale curves are not distuingishable at first glance 27?u=christophlendenfeld\n\n## Current State\n\nNormal\n\n\nDisabled\n\n\nLocked\n\n\n## Proposed Solution\n\n* Locked curves have crosses instead of keyframes to indicate that they can't be selected. [#106052](106052)\n* Locked curves are always drawn as if they were unselected since you can do nothing with them even though they are selected.[#106052](106052)\n* Increase the dash length and spacing to reduce visual noise [#106052](106052)\n* Add preferences to modify the colors of FCurves based on their type. Will default to the current standard to not confuse existing users.\n" ]

[ "Shortcut keys inconsistent.\nOSX 10.7\n\nBlender Trunk build 2.69.11\n\nIn node editor working with cycles shaders. When creating new glossy shader you can use shortcut keys Shift-A (brings up add window), H (select shaders tab), G (adds Glossy Shader).\n\nIn Materials tab in Properties. In Surface, opening shader dropdown and using shortcut G gives you a Glass shader. NOT A GLOSSY SHADER. Please make shortcuts consistent.\n\nThanks,\n\nJonathan Lax\nGecko\n" ]

[ "Snap to Grid in Perspective View performed only at ground level\nGenerally you are not sure which grid point the object is in the perspective view because you need to consider the current depth of the object on the screen.\nThis option would only limit movement at ground level under those conditions.", "Brush Management: setting a brushes tool [vertex_tool, weight_tool, ...] may leave you with unaccesible tools (when no corresponding brush is left)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.83.2\n\nSee attached gif. Scene is the default scene without camera and light. Once I start switching tools in Weight Paint Mode through the different methods shown in the gif, I eventually reach a point where I lose access to some tools. Notice that even though the brush menus initially show the expected brush as the one currently selected, it isn't the one performing the painting (shown in the gif as the desync between \"Active Tool\" and the brush that appears as selected). As the gif also shows, the side menu doesn't select the expected brush either. \n\nAs a side question: why is the Smear brush named \"Smear.001\"? instead of just \"Smear\" like the other brushes?\n\nSee gif. \n\nThanks.\n\n\n\n\n", "Update Tweak Tool behaviour on Right Click Select\nThis has been a long running known issue for the Active Tools when using right click select.\n\n## Issue\nOn RCS, the Tweak Tool in the toolbar is placing the 3D Cursor instead of tweaking elements.\nThis duplicates the behaviour of the Cursor Tool (right next to it in the toolbar).\n\nThe reason for this seemed to be that right click & drag is already using the tweak action.\nIf the Tweak Tool would tweak with left & right click then there is no way of setting the 3D cursor anymore.\n\nBut the Tweak Tool doesn't require the 3D cursor. And this workaround is breaking the tweak tools purpose.\n\n## Solution\n\nThe Tweak Tool needs to tweak with left click & drag.\nThis can be it's own keymap item in the preferences under the Tweak Tool.\nRight click & drag can still use the default tweak action in the preferences.\n\nThe benefits are:\n- The Tweak Tool can be used without a drag threshold with left click & drag, if the option \"Alt Cursor Access\" enabled in the preferences\n- There is a functional distinction between the Tweak Tool and the Cursor Tool.", "Library Overrides of the Same Linked Armature Cannot be Posed Simultaneously\nOperating system: Windows\nGraphics card: RTX 3070\n\nBroken: 3.3.1\nWorked: NA\n\n**Short Description**\nWhen linking a rig and making it into a library override twice in one scene, the rigs function properly as separate rigs but both linked from the same file. However, if you try to go into pose mode for both at the same time and pose the rigs, you cannot pose them separately. This is a pretty specific issue but if you had two identical rigs and wanted to animate them interacting in some way, it would become extremely bothersome.\n\n**Steps to Reproduce**\n- Open `example.blend`\n- Select both armatures\n- Switch to pose mode\n- Select any bone of any armature (this will also select same bone of another armature)\n[bug.zip](bug.zip)\n", "Move some parameters to Blender's DNA\nThese parameters are supported (or going to be) by EEVEE-Next, and we should avoid duplicating the settings for each engine:\n- Motion blur curve\n- Panoramic camera settings\n- View Layer material override\n\nThis is a big change and 4.0 should be the right time to do this.\n\n", "GP brush pin for fill only, makes both stroke and fill\nHi \nI want to have fill and stroke in different color but if I pin, I get both color same.\nSo that I cannot make custom brush, or I have to change it vertex mode every time.\nCan you please check?\n\n[image](attachment)\n\n", "Able to paint/select \"through\" disabled UI items.\nBroken: 2.80, 2.81...\n\nWith region overlap, if a UI element is diabled, clicks are passed through it, which can result in paint strokes.\n\n\n1. Load the default scene and enter Texture Paint mode on the cube.\n2. Add a paint slot and make a stroke.\n3. In the UV/Image editor, select the painted image, open the sidebar and switch to Image tab. The UI items should be disabled there now.\n4. Make sure that sidebar overlaps the image.\n5. Click on sidebar background.\n6. Click on any of the disabled items.\n\nIn (5), nothing happens. In (6), the click passes through and leaves a paint stroke on the image.\n\n", "Allow menus to be added referenced to another menu \n## Motivation\nAddon developers cannot add menus on specified place. \nThey are always added at the end (append), or at begin (prepend)\n\n## Analysis\nAfter a look at current code, i think a good approach should be allow to define a reference label on append function.\n\nWhen drawing the menu layout, a new RNA call should be done on a new function class, that should then execute the referenced drawing calls on py scope.\n\nIssue with this development is that for any but menu drawn two python calls are performed to allow addons draw before and after itself. Maybe this could be solved checking in C scope if it has post/pre functions added.\n\n## Development steps\n* {icon check-square-o color=green} Draw after label\n* {icon check-square-o color=green} Draw before label\n* {icon check-square-o color=green} Give warning if not used (label not found)\n\n## Know Issues\n* Issues with enums, if shown as submenu it's not working. Is shown on self menu, the label is the operator name, and considered a block\n\nFeedback is welcome!\n\n\n\n\n", "How to integrate multi-frames icons/preview images in UI code\nSo, to support one preview per pose of a PoseLibrary (first use case, many more are possible later), multi-preview (or preview frames) is being added to Blender (see [the branch]() for details). \n\nThe main issue I’m facing here is how to use those 'frames' of preview images. I can think of two solutions, neither are really ideal to my taste (went with first one in current branch):\n- Introduce the concept of 'frames' of an icon. You basically have to pass an extra value to UI API functions, the frame of the icon you want to use. This is simple and rather powerful, drawback here is that you'll ultimately have to change the whole UI API, which will be awfully… verbose.\n- Generate one icon ID per frame of the preview image. This is simpler, but can lead to a huge amount of generated icon id’s (with matching Icon data), imho it’s really not worth the overhead.\n\nWouldn’t mind having your feelings here, or even better if you have other ideas, before I change whole UI api…", "Flickering UI on MacBook M1 or external monitor MBP 13 M1\nOperating system: macOS-12.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.1\n\nBroken: version: 2.93.5\n\nWhen any action in blender (move viewport or oblects) - there is flickering UI. Not way to burn eyes, but noticeable. Problem happens only on external monitor that worked absolutely fine in any other apps.\n[IMG_2758.MOV](IMG_2758.MOV) - video in slow motion showing the problem. Some times it flicks a lot, some times not much.\n\nJust moving view point is enough to flick UI.\nThat happens with my first of two files. Second doesnt have that. Attach the file with problem.\n[domik.blend](domik.blend)\n", "Split up pose mode keymap to avoid weight-paint conflicts\nCurrently the \"Pose\" keymap us used in combination w/ weight paint.\n\nThis means we can't add key bindings for animation that conflict with weight painting for eg. F-Key. See: #63667 (Keymap: Weight Painting using the Pose Mode keymap)\n\n----\n\nProposal:\n\n- \"Pose Generic\" for basic selection operations.\n- \"Pose\" for more advanced animation actions.\n\n\"Pose Generic\" would co-exist with weight paint mode when weight painting is mixed with pose mode.", "Touchscreen 'Continuous Grab'\nOperating system: Linux-4.15.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Haswell Mobile Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.0.2\n(bug also tested on Windows 10)\n\n\nBroken: version: 2.80 (sub 74)\nWorked:\n\n\n* Activate a gizmo using the **touchscreen** on a computer. (The 3D navigation gizmo for example)\n* Drag your finger outside the original editor\n* The gizmo is manipulated incorrectly\nThis bug disappears if \"*continuous grab*\" is disabled in the User Preferences.\nI think it's a matter of auto-disabling *continuous grab* while receiving touch input, like how pen tablets are handled.", "Using viewport visibility as a driver doesn't work without constantly updating it in the driver property\nBroken: version 2.93\nWorked: Never (2.8+)\n\n\nUsing viewport visibility as a driver from another object doesn't works unless you constantly hit \"update dependencies\" it in the driver property.\n \n \nFor this, i used the cube's visibility as a driver on the shape key of the sphere.\n[The not working file.blend](The_not_working_file.blend)\nIn the outliner, enable the viewport visibility for the cube, then disable it again. The shape key doesnt update unless you go into the driver property and hit the update dependency button.\n\n\n\n[The working one.blend](The_working_one.blend)\nThis is what i was hoping it would do. The only way I could use viewport visibility as a driver is to use a custom property on that object then use the custom property as a proxy.\n\nIs there a reason why it dont update if you use visibility as a driver from another object or is that a bug?\n\n**Steps to reproduce**\n[The not working file.blend](The_not_working_file.blend)\n\n- Open file\n- Click on Disable in Viewports icon on Cube object in outliner\nSphere shape should be change, but it doesn't", "Polishing Correct Face Attributes\n- [ ] Initialize operators options based on the \"correct face attribute\" value (e.g., edge slide).\n- [ ] Unify naming of the option and the operator options.\n\nThe way we do Proportional Editing seems to be a good example to follow. These issues have been raised on 4387aff", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n" ]

[ "Update and Create Necessary Icons\nThere are many operators and other interface element across the board that need either updated icons or new icons entirely. Often this is due to duplicate usage of the same icon (such as Render and OpenGL Render). \n\nThis is a parent task to begin collecting tasks for necessary icon updates. \n\n**Note:** we do not currently have an icon designer that's available, and so I've set this to low priority until we're able to give it some real attention. If you wish to take a shot at icons feel free to submit patches for review. " ]

[ "Semitransparent grease pencil covers wireframe. Bug or limitation?\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nit looks like this \n\n[untitled3.blend](untitled3.blend)\nAnd it is difficuilt sometimes to work with wireframe and GP-sketch when I don`t see vertices\n", "Sculpting - Cloth brush - Snake Hook deformation not working\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\n\nBroken: version: 3.5.0 Alpha\n\nThis is the image I got after kept dragging my cloth brush around the same spot for a few times:\n\n\nand this is the file I'm using:\n[20221206_sculpt_cloth_brush_snake_hook_donot_work_0001.blend](20221206_sculpt_cloth_brush_snake_hook_donot_work_0001.blend)\n\nI personally think the option is 'wired' to a wrong block of code.\n\n", "GPencil: Texture Image Alpha pass through grease pencil strokes\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83.1\n\nContext: Using texture image to make some kind of 2d fur on top of a GPencil Object\n\nThe Image Texture used to make some fur is mostly transparent and the brush used to make the colored part is a texture paint brush with Cloud Mask (it was made entirely in Blender with Blender tools).\n\nWhen on top of the GPencil object, the part of the Image Texture that is only half transparent(between 99%-1% transparent), makes the GPencil color disappear, even when moving the center point behind the one of the fur images.\n\nOn the contrary, when on top of another Image Texture (imported to be used as camera mapping), the Image Texture of the fur doesn't impact the transparency of that one.\nNotice that the Image texture boundary, even from the imported one, has problems with clipping and always makes a white line appear.\n\n- Open attached .blend file\n- Zoom in and out to notice the alpha transparency influencing the GP object\n\nThanks for your help!\n\n\n\n\n\n\n\n[bug_alpha.blend](bug_alpha.blend)", "Grease pencil strokes are incorrectly blended with geometry in draw mode (depending on 'Fade Inactive Geometry' setting)\nOperating system: Win 10\nGraphics card: ATI Radeon 5700\n\nBroken: (example: 2.92b, 213f8*, master, 2021-01-28, as found on the splash screen)\n\n\nnote: this is due to `Fade Inactive Geometry` being ON\n\nWhen drawing grease pencil strokes with a black material the rendering style changes when...\n\n - ...switching between draw-mode and edit mode, or\n - ... toggling the overlay button in draw mode (even will all overlay options disabled).\n\n\nThis leads to noticeable rendering artifacts while drawing. Please consider the following screenshots:\n\noverlays on:\n\n\noverlay off:\n\n\nSome assumptions:\n- I assume that the blend modes are not correctly set and thus interfere with the MSAA.\n- The white artifacts are especially pronounced for thin strokes of all opacities. Increasing the thickness factor slightly decreases the problem.\n\nLoad the following blender file\n[stroke-test.blend](stroke-test.blend)\n\nStep by step:\n1. Start blender\n2. Create Cube\n3. Create Grease Pencil\n4. Add new material for grease pencil and change to black\n5. Draw strokes (with different opacities)\n6. Switch between Draw and Object mode or toggle Overlay-Toggle\n", "Line stroke method not working with Scene spacing\nOperating system: Linux-5.4.0-121-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 670MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.151\n\nBroken: version: 3.2.1\n\nLine stroke method not working with Scene spacing\n\nOpen blender, then open a new sculpt file, select any brush change the stroke method to line and chose scene spacing distance. \nIt only works when started and ended inside the object, but when coming from outside the object or end up outside the object it doesn't work, sometimes it gives an initial effect when it comes in contact with the object but only one sample.\nI the video you can see how it works with view spacing and then how behaves with scene spacing.\n\n[vokoscreen-2022-07-12_14-43-22.mp4](vokoscreen-2022-07-12_14-43-22.mp4)\n\n", "Greasepencil effect error\nOperating system:windows10\nGraphics card:GTX1060\n\nBroken: 2.93\n\n\n\nIf Greasepencil enters a 3D object\n\n1, A small part of the BLUR effect will overflow and the join part will be a little transparent\n2.The FILP effect will lose part of the image\n3.The RIM effect will change as the 3D object changes.\n4.The shadow effect overlays 3D objects and is partially missing\n5.The wavedristution effect will overwrite the 3D object in horizontal mode.Vertical is normal\n6.The swirl effect will lose some of its effect and will overwrite the 3D object\n\n[rim.blend](rim.blend)", "Grease Pencil keyframes not updating after GPencilFrames.copy()\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha\n\nCopied keyframes do not update with Grease Pencil Layer\n\n- Create a new document with the 2D Animation template\n- Draw a shape \n- (Note by @iss) It may be necessary to make new keyframe at later frame, see video\n- Run the below script in the Text Editor\n# Run the \"Grease Pencil Test Script\" command from the Draw Menu\n\nThe Grease Pencil data isn't updating in the Viewport unless the playhead is going backwards, a keyframe is deleted, or if the keyframes are added to a new `GPencil` object. I believe the issue is because the keyframes generated with `GPencilFrames.copy` are missing the layer update for some reason. If I use `GPencilFrames.new()` and copy every attribute manually, this issue does not happen. In the below code, I am updating all of the data I know to be possible.\n\n```\nimport bpy\n\ndef main(context):\n active_layer = context.active_gpencil_layer\n frames = active_layer.frames\n start_frame = frames[0]\n frame_numbers = [frame.frame_number for frame in frames]\n\n for frame in range(start_frame.frame_number, context.scene.frame_end+1):\n if frame in frame_numbers:\n continue\n new_frame = frames.copy(start_frame)\n for i,start_stroke in enumerate(start_frame.strokes):\n new_stroke = new_frame.strokes[i]\n for p,start_pt in enumerate(start_stroke.points):\n new_pt = new_stroke.points[p]\n new_pt.co[0] = start_pt.co[0]+(frame*0.5)\n new_frame.frame_number = frame\n\n gpencil = context.object\n gpencil.data.layers.update()\n for l in gpencil.data.layers:\n l.frames.update()\n for f in l.frames:\n f.strokes.update()\n for s in f.strokes:\n s.points.update()\n\n gpencil.data.update_tag()\n context.view_layer.depsgraph.update()\n context.view_layer.update()\n bpy.ops.gpencil.recalc_geometry()\n\nclass GPENCIL_OT_simple_operator(bpy.types.Operator):\n bl_idname = \"gpencil.simple_operator\"\n bl_label = \"Grease Pencil Test Script\"\n\n def execute(self, context):\n main(context)\n return {'FINISHED'}\n\ndef draw(self, context):\n self.layout.operator(GPENCIL_OT_simple_operator.bl_idname)\n\ndef register():\n bpy.utils.register_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.append(draw)\n\ndef unregister():\n bpy.utils.unregister_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.remove(draw)\n\nif __name__ == \"__main__\":\n register()\n```\n\nPlease disregard the step where I put the GP Object into Edit mode & create a new keyframe. This step is not necessary to seeing the `GPencilFrames.copy` bug.\n[duplicated_frame.mp4](duplicated_frame.mp4)\n\nNot sure if the bug will show consistently, but here is the scene file:\n[Grease_Pencil_Data_Bug.blend](Grease_Pencil_Data_Bug.blend)", "(Grease pencil) Blender freezes indefinitely when drawing using stabilize stroke function. \nOperating system: Windows 10 business 64bit\nGraphics card: Intel UHD 620/630\n\nBroken: both 3.2.2 and the experimental build 3.4.0 alpha\n\n\nWhile drawing using the stabilize stroke function (in blank grease pencil object), after some times blender freezes and stop responding, tested on both an HP prodesk g5 ( I5 8500, intel IGP UHD 630 and 8 GB of RAM) and asus zenbook (I5 7200U, UHD 620, 8GB RAM).\n\nThis only happened on both PCs equipped with intel IGP, I redid the same test on my home PC (I5 9400f, GTX 1060, 16GB RAM) and everything worked fine.\n\nIs this purely a performance issue ?\n\nJust create a blank grease pencil object and directly start drawing using the stabilize stroke function, test setup must be similar or close to the two PCs equipped with Intel IGP.", "Appending grease pencil brushes creates \"fake user\" unintentionally\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 3.0.0 Beta\nWorked: 2.93.4\nCaused by 3be5ce4aad\n\nWhen appending grease pencil brushes, they will be added to the file as a \"fake user\", even if this option is unchecked in the append window.\n\n- Open default 2D animation file\n- {nav File > append > fakeuserbug.blend > Brush > Shift select the custom brushes (start with \"pp_\")}\n# Change brush from `Active tool & Workspace settings` (notice it has been added as a fake user)\nappend brushes from another file\nThey will be added as a fake user, whether or not the \"fake user\" box is checked in the append window\n\n[fakeuserbug.blend](fakeuserbug.blend)", "Weight Painting intermittent issues with brush, not adding or subtracting weight, not influencing correct areas\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080ti + 3x GTX 1080Ti - Running 4 monitors and a pen tablet at three different resolutions using outputs from two GPUs (4k, 1440p, 1080p)\n\nBroken: 2.81 stable\nWorked: 2.80\n\n\nI have had numerous issues with weight painting in 2.81, however duplicating them has been problematic as this crops up intermittently. In this example, I saved this working file right at the moment I started having problems. Here I can neither add nor subtract weight with the brush in Weight paint mode from a certain distance from the model. \n\nIn other instances, I've had issues with the brush *not painting over the vertices it's over*. I use a hard falloff brush, so anything inside the circle gets painted, anything outside gets nothing. Essentially, it acts like the circle where the brush is being displayed, is not where the circle actually is, if that makes sense.\n\n\n*I tried exporting this to it's own file, but that seems to fix it. It has to be in the full working file I'll provide here. You should hopefully be able to open the file, already be in weight painting mode, with the brush set up, over some masked vertices ready to add or subtract. Try switching the brush to add, and zoomed in fairly close, add some weight, and nothing happens. However, zoom out and do the same thing, and watch weight be added.*\n\nYou can kind of jump around and try rigging other parts of the car, I've been having issues with it off and on for the past few days.\n\n[70sNewYorkers.blend](70sNewYorkers.blend)", "Grease Pencil Bezier points can't be deleted immediately after moving\nOperating system: Linux Mint 64-bit\nGraphics card: NVDIDA GTX 1080 ti\n\n2.93.5 (also broken in 3.0 alpha)\n\nDelete (X) does not work on Grease Pencil edit curve points if the previous operation was to transform them.\n\n - Enable curve editing in Edit Mode on a Grease Pencil object (attached)\n - Select and transform any bezier point (G, R, S)\n # Use Delete (X) on the selected point\nIt won't delete!\n[GPbug.blend](GPbug.blend)", "Collection holdout on grease pencil objects\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.4\nWorked: unknown\n\nHoldout option on collection doesn't work, if objects it is containing are grease pencil objects. Alpha of contained GP objects remains on 1 / solid in viewport as well as in render.\n\nPS: This behavior would help a lot with compositing linework made with \"linework modifier\" of grease pencil. In shots where characters are obscured by objects linework should obscure them as well but if in the same shot character comes in front of the object suddenly the opposite is needed.\n\nsample .blend file (steps included):\n[collection holdout grease pencil bug.blend](collection_holdout_grease_pencil_bug.blend) \n1. create GP drawing (GP Suzanne will work fine)\n2. create collection for it and move it in the colection\n3. repeate first two steps but move the new GP object in front of the first one (Default GP stroke might be mor suitable in this case)\n4. in collection settings of the collection made for second object (the stroke) check the holdout option.\n5. render image and you should see the second gp object remaining opaque.\n\n**given result**\n\n\n**expected result**\n[achieved by converting GP stroke to curve and extruding the curve]\n\n\n", "Grease Pencil problem in drawing short lines\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.1 26.20.15019.1003\n\nBroken: version: 2.83 (sub 10)\n\nThere is a problem with drawing short lines in this version\n\nDraw a very short line and then zoom in on it\n", "Broken curve drawing in normalized view in graph editor\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.1\nWorked: ?\n\nin the normalized mapping in the graph editor, the curve behaves strangely. In the normal display, everything is fine\n[2022-04-20 22-13-05.mp4](2022-04-20_22-13-05.mp4)\n\n- Open attached .blend file\n- In graphics editor pan view up and down\nDisable Normalized to hide the problem\n[bandit_anim.blend](bandit_anim.blend)", "Inconsistency in the behavior of 'Jump to next/previous keyframe' operator\nOperating system: Linux-5.4.0-124-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.3.0 Beta, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: as far as I know, none.\n\nWhen calling the 'Jump to next/previous keyframe' operator, there are inconsistency of behavior depending whether the active object is a Grease Pencil one or not.\nFor standard keyframes, it jumps to next keyframe if the object is active, regardless of if the object or any of its channels are selected.\nFor grease pencil layers keyframes, it jumps to next keyframe only if the layer channel is selected.\n\nReproduce the bug :\n - Open a new blender file,\n - Add one grease pencil object with two keyframes,\n - Add one 3D mesh (for example) with two keyframes (at different frames than the grease pencil ones),\n - Try to jump to next or previous keyframes, standard shortcut : up/down arrow in the viewport.\n\n[issue_jump_to_next_keyframe.mp4](issue_jump_to_next_keyframe.mp4)\n\n" ]

[ "Some Grease Pencil Sculpt tools break if GP object is transformed\nversion: 2.80 (sub 74), branch: master, commit date: 2019-06-20 22:36, hash: 197661c7334d, type: Release\nbuild date: 2019-06-20, 23:27:49\n\n[GP Sculpt Bug.blend](GP_Sculpt_Bug.blend)\n\nHow to reproduce:\n\n - Open the attached file\n - Enter sculpt mode for for each monkey\n # Try using the Push, Pinch, Twist, and Clone tools, specifically.\n\nThe Red Monkey is not transformed. All the tools work as expected.\nThe Blue Monkey is displaced. The effects of the Pinch, Twist, and Clone tools are WAY off.\nThe Green Monkey is rotated upside-down. This breaks the above tools, as well as the Push tool, which now works in the opposite direction.\n\nI haven't tested it, but scaling probably breaks sculpt mode in a similar way as well.\n\n" ]

[ "USDZ IO - Occlusion Texture gets stripped\nOperating system: Windows 11\nGraphics card: RTX 3090\n\nBroken: (3.60, 6daa3f6b8a9b)\nWorked: NA\n\n\nWhen importing a sample USDZ file it imports correctly but has no Occlusion applied on the shader. When exporting back out to USDZ the Occlusion map is not included inside the USDZ anymore. \n\nWhen checking the original file (extract the usdz via a 7zip) it does have the AO texture inside the directory.\n\n1. Download sample USDZ file from Apple: Rock.usdz\n2. Import USDZ into Blender\n3. Go to Shading Tab\n4. Export USDZ from Blender\n5. Extract USDZ file via 7zip to check for embedded textures\n6. The directory only contains color and normal maps\n\n", "Artifacts appear in texture bakes [stripe pattern]\nOperating system: Windows 10 Pro 64-bit\nCPU: i7 4790\nGraphics card: GTX 1050\n\nBroken: Every Blender Build on this PC, Baking.\nWorked: never\n\nWeird artifacts appear in bakes, especially visible in the AO bakes (see attached images)\n\n\n\n\n\n[AOArtifacts_Test.blend](AOArtifacts_Test.blend)\n- Open blend\n- hit `Bake`", "Viewport: Texture limit size generates artifacts during painting\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nWhen limit size is lesser than the actual image size, this will result in artifacts at paint region.\n\n- Open attached file\n- Change Texture limit size to 2k or less (`Edit > Preferences > Viewport > Textures > Limit size`\n- Paint the plane.\n", "UI BUG: Icons in the property editor \"flicker\" when you hover them or click on them\nOperating system: Windows 10, 64 bits\nGraphics card: Geforce 1080 8gb, Geforce 1070 8gb\n\nBroken: blender-2.90.0-874af5301cdf-windows64\nWorked: 2.83.0 LTS\n\n\nIcons in the property editor annoyingly flicker, they change border thickness 1-2 pixels upon hovering over or clicking on them.\n\nThin:\n\n\nThen they get thicker:\n\n\nIt's very visible if you use Icon border settings in your theme and many monochrome themes dop use that setting, because not everyone wants to see distracting rainbow colors in their UI.\n\n\nGo to Blender Preference, Themes.\nOpen Icon colors tab and set icon border to 1.\nEssentially use any bright theme as it is very visible when your theme is bright and icons have borders.\n\n\nHover over icons in the property editor, see the flickering.\n\nHere's the video of the bug:\n\n[2020-06-22 01-18-44.mp4](2020-06-22_01-18-44.mp4)\n\n\n", "Paint Mode: Alpha Auto-Masking\nNOTE: This design still needs to be further discussed and decided upon.\n\n# Goal\n\nThe very common brush setting in Blender to \"Affect Alpha\" should be revamped for the upcoming Paint Mode.\nThe main issue with the setting is that it is local to the brush. But in typical painting workflows you'd expect to have this be a more universal toggle that affects all tools!\nToggling this per brush is not a reasonable solution.\n\nThere are multiple approaches to fix this.\n\n## Proposal: Alpha Auto-Masking\n\nThere is already a design in place for sculpt and paint mode. There we use auto-masking to easily target specific areas as a mode setting.\nThese are meant to be instantly accessible with a pie menu on `Alt + A` and would affect all tools and brushes.\nThis would likely be the most intuitive and fastest option.\n\n## Image Editor Inclusion\n\nIf we decide to replace the brush option with an auto-masking option this puts further pressure on implementing the same options for the image editor.\nThis might be reason enough to lower the priority for now, until the image editor can be properly prioritised to mirror the 3D viewport paint mode features.\n\n## Long Term Alternative\n\nOther image painting applications such as Krita implemented this as a toggle for any individual layer to paint on.\nWhile this is not likely to implement this way right now, it could be kept in mind for the UI of the [layered textures design]().", "Display warning when exporting RGBA using PNG.\nRelated to #81390.\n\nWhen exporting a render to RGBA PNG the alpha isn't correct. The issue is related to the different color spaces and PNG (sRGB) not supporting pure emissive colors. We currently don't show a message to the user explaining that it could result into artifacts.\n\nThis task would be to add a message when user selects this combination. in the export panel. Or when saving an image that isn't sRGB encoded, using these settings.\n\nMessage still needs to be approved:\n`Saving/Exporting non sRGB but transparent images to PNG creates alpha differences.` With a warning icon.", "Unable to accurately sample colors in Vertex Paint mode\nOperating system: Linux-5.10.11-arch1-1-x86_64-with-arch 64 Bits\nGraphics card: GeForce GTX 660M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.92.0\nBroken version: 2.83.1\nWorked: 2.79b\n\nSampling colors in Vertex Paint mode is unreliable even in flat shading or when utilizing an emission shader and standard color management (although this reports the correct color some of the time) in both Cycles and Eevee.\n\n1. With the default cube selected, enter Vertex Paint mode.\n2. Switch the viewport shading to Solid, the lighting to Flat, and the color to Vertex.\n3. Change the brush color to #000003.\n4. Go to the Paint menu and select Set Vertex Colors (or press Shift+K)\n5. Sample the color on the cube by either using the eyedropper from a color picker, or pressing S with the mouse hovering over the cube (doesn't matter if Sample Merged is checked or not)\n6. Check the brush color and see that it has changed to some other color (#010103 on my machine)\n", "Color Management / Use curves : Setting clipping option to Min = Max causes CRGB curves to go blank.\nWindows 10, GTX 1660\n\nBroken: Blender 2.82 release.\nBroken: Blender 2.83 daily update\n\nThis will recreate the black CRGB Curve display to go blank.\n\n1. In the Properties Panel, Select Color Management.\n2. Enable 'Use Curves'\n3. Select the 'Clipping Options'\n4. Set 'Max Y' to 0.00\n5. Now select anywhere in the CRGB curve display. It goes blank.\n", "Material Preview (and final render in EEVEE) purple\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7263\n\nBroken: version: 2.83.0\nWorked: I don't remember this bug occuring in previous versions.\n\nI know, that materials should become purple when the texture is missing.\nBut the problem is that they not behave as they should even without applying textures and also with the default material.\nThis bug occurs in EEVEE:\n1) In material preview in properties\n2) In render\n3) Sometimes - in viewport\n\nIn a render, it is also a problem with the scene surface material.\nI attach some screenshots from material preview: they are all the same default material.\n\n\n1) Open Blender\n2) Press F12 or go to material preview in object settings.\n3) ... see the bug\n\n\n\n\n\n\n\n\n", "Sample texture color dialog isn't dismissed after use\nOperating system: W10\nGraphics card: GTX 970\n\n2.82a\n\nAfter use of the pipette in the Image Texture Editor, the 'F9' dialog box is not dismissed until an UNDO operation is performed.\n\n\nSample file included; Launch file. Switch to Texture Paint. In the Texture Image Editor, invoke the sample function with the S hotkey. Observe the dialog.[Sample Dialog Dismiss.blend](Sample_Dialog_Dismiss.blend)", "Image Texture sampling by int X and Y pixel indices\nImplement the ability to sample an image not only by the position vector, but also by the pixel coordinates.\n\nSince this implies some simplification of the already implemented code, it would be convenient to either reuse the existing sampling code for another node, or switch the mode of operation in the original node. The variant of the `image_closest_texture_lookup` method for `ImageFieldsFunction` with integer support looks as close as possible.\nThis also implies, there is no need for interpolation methods.", "EEVEE: Add support for extracting alpha channels from a color\nI mistakenly filed a bug report --> #72856 EEVEE transparency problem with mtpaint PNG\n\nI didn't fully understand the bug and attached a blender file that didn't show the bug properly.\nPacking the image file with blender command 'Pack' makes the image\nopaque so it is worthless to include a blender document. I will\ninclude a mtpaint PNG image instead and you can load it into\nblender 2.81 yourself and see how it renders in EEVEE versus cycles.\n\nI noticed that your forum converts the image to opaque if I try to attach to this post\nso I'll use a shareable link that preserves the transparency:\n\nopen?id=1TjfSjzabYEmVHXTODPFymGVNwuL02SnJ\n\nHere is how I created the mtpaint image to reproduce the problem...\n\n1) Launch GIMP -->new gimp document -no alpha channel - paint with brush\n2) save as PNG format with no alpha channel\n3) Launch mtpaint ---> open the PNG document\n4) 'Save as' to output the document - one color chosen to be transparent - PNG format\n5) Launch blender 2.81 (linux) - images > Images as planes\n\nEEVEE rendering doesn't respect the transparent region.\nCycles rendering does respect the transparent region.\n\n\nNot a high priorty.", "Rendered object in displayed as a transparent png\nOperating system: Windows-10-10.0.19043\nGraphics card: Radeon AMD Radeon HD 8500M (4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001)\n\nWorked: (3.2.0)\n\nidk if it is even a bug but when i render my object, it shows the object as a transparent png. how do i fix it?\n\n[donut.blend](donut.blend)", "Eye-dropper missing in texture paint mode.\nOperating system: Windows-10-10.0.22593-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.14800 Core Profile Context 22.5.2 30.0.21017.1000\n\nBroken: version: 3.3.0 Alpha\nThe same with version 3.2\n\neye-dropper is not appearing on the color selection whell when doing texture paint, both on the 3d view, or 2d texture painting.\n\nOpen blender, select the cube, go to texture paint mode, right click, left click on the color square on the top left corner, then you'll see the eye-dropper is missing. \nOpen blender, switch to texture paint workspace (or switch the tab to texture paint), create a new texture, right click, click on the color square on the top left corner, then you'll see the eye-dropper is missing. \n\n", "Displacement distorts textures\nOperating system: Windows 10\nGraphics card: RTX 3060Ti \n\nBroken: 3.6.0\nWorked: Never\n\nAll textures are distorted where displacement texture is greater than 0.\n\nWhen you plugin displacement as 'bump only' the box projected textures glitch out and start to stretch.\nSee attached file.\n" ]

[ "Texture paint: Artifacts on using fill tool\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon(TM) 535 ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013\n\nBroken: version: e6ad11f06dd7875c66b1c0a2bfabd2cd3eb1d8c7\nArtifacts on using fill tool when object is too close to the view (in orthographic view)\n\n- Open .blend file\n- Use fill tool on object in viewport\n\n\n\nTest File:\n[#95663.blend](T95663.blend)\n" ]

[ "FPS problem (movie import)\nOperating system: Windows 10\nGraphics card: rtx 2070\n\nBroken: \nWorked: Blender 3.5.1 \n\nWhen I import a 30 fps video in blender (in \"movie clip editor\"), this video will be interpreted as 120 fps per blender, making motion tracking impossible.\n\nimporting a 30fps video in movie clip editor\n\n", "Post processing dithering can't be saved in 16bit format\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: never worked possibly\n\nDither applies to final image only if you save it in 8bit format.\n\nIn attached file:\n* Render scene (F12) and save PNG file twice: in 8bit and 16bit formats\n\n", "When \"Pie Menu on Drag\" is enabled in user prefs, Ctrl + Z has a tendency to open the shading menu by accident\nversion: 2.80 (sub 74), branch: master, commit date: 2019-07-05 21:52\nbuild date: 2019-07-06, 01:03:01\nplatform: Linux\n\nThis may be more of a design issue than a bug, but it's happened to me about 100 times now and it's quite irritating.\n\n**To reproduce:**\n\n - enable User Preferences > Keymap > Preferences > Pie Menu on Drag.\n - open a complex scene (one where the undo operator will have a significant lag) \n - fill the undo history with events, as though you've been working for a while\n - Press Ctrl + Z a couple times while moving the mouse a bit, rolling your hand so that Ctrl is released just before Z (in the manner of a busy artist)\n\nIf the user happens to release Ctrl earlier than Z while moving the mouse, this can bring up the shading menu, interrupting the user's workflow. This may sound like an edge case, but when working quickly, it's actually really frequent and annoying! It seems to especially effect large scenes where there is a lag in the effect of the undo operator.\n\nIdeally, the \"Pie On Drag\" feature should not listen for key presses if those key presses were part of a different combination that has yet to be completely released. What do you think?", "Channel numbers becomes unreadable with extreme zoom\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 27.20.100.8476\n\nBroken: version: 2.91.0 Alpha\n\n\n{[F8909669](image.png), size=full}\n\n\n", "Volumes look much much different in master compared to 2.79b\nWindows 10 pro x64\nGTX 970\nThread Ripper 1950x\n\n\n\nBasic volume shader with noise texture from build bot today doesnt look the same as 2.79b\n\n\n\n[untitled.blend](untitled.blend)\n", "Animation: Exiting NLA tweak mode on empty action corrupts entire NLA track\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3060 Ti\n\nBroken: 3.3.0, 3.5.0\nWorked: Unknown\n\n\nWhen tweaking a strip on the NLA, if the user deletes all the keyframes of the action being tweaked, when the user exits tweak mode, all other NLA strips on that track will be moved in an unexpected and undesirable way.\n\n[tweakbug.mp4](tweakbug.mp4)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open the attached .blend file\n2. Delete the keyframes on the track being tweaked.\n3. Exit tweak mode by pressing Tab.\n4. Observe that the NLA strips have been moved.\n\n[tweakbug.blend](tweakbug.blend)", "Image Editor: Viewing a value buffer could use incorrect channel selector\nThis is a long outstanding issue in the image editor that should be fixed.\nWhen rendering a value based AOV and switching in the render result to the AOV would render incorrect as the wrong channel selector is selected (Still Color + Alpha).\n\nThis is also visible when reading single channel images or OpenEXR files.\n\n**Solution**\nAdd an option to view `Value` option to the channel selector and change RNA get/set/itemf + add support of this to the image engine.", "VSE: cursor for retiming stuck with undo/redo\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 4.0.0 Alpha\nWorked: n/a\n\nAlso broken for 3.6.\n\nRetiming tools was introduced in e1f6587f12\n\nThe cursor to indicate it's hovering over retiming handle does not return to the normal cursor in some situations. Both for move and eraser cursors.\n\n<video src=\"attachment\" controls></video>\n\n- Hover over retiming handle to change cursor to move or eraser cursor\n- While the cursor is hovering over it, hit Ctrl-Z or Ctrl-Shift-Z to undo or redo\n- Cursor does not come back to the normal one as long as it's inside the sequencer\n\n", "Multiple CNTRL Z replaces properties in driver\nWin7 64bit\n\nBroken: 2.79\n\nI was copying drivers from one object to another and hiding (H) those with already pasted driver. At some point I wanted to unhide previous object, so used undo instead of ALT H to bring back only one object. After object was revealed, I do not re-copy driver just paste what was already in memory. I make three undo's (just the step before copying driver), so I didn't expect this will corrupt driver's data. Would be better to make \"paste\" not happen, rather than changing it.\n\n*Original driver*\n\n*Pasted driver after some undo's*\n\n\n1. Copy driver from texture slot of left cube\n2. Hide left cube in viewport\n3. Paste driver in texture slot of right cube\n4. Pres CTRL Z three times until left cube will appear back\n5. Then repeat pasting driver from stage 3 -> driver's properties have been replaced by another\n[Paste_driver.blend](Paste_driver.blend)\n", "Support Undo for tweaking Gizmos\nSupport Undo for tweak gizmos, such as the Spin gizmo. Currently, the user may have performed many adjustments using adjustment gizmos, but if the user performs one undo, everything is lost.\n", "Quadriflow Remesh: Undoing the next operator also resets the mesh\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.83.4\n\nUndoing the operation after the remesh also undoes the remesh.\n\n- Quadriflow remesh the default cube\n- Execute any other operator (switch to edit mode, add curve, etc..)\n- Undo\n\nThe mesh will reset to its state before the remesh.\n\n", "Glitches on Video Sequence timeline\nOperating system: Linux 5.9.11\nGraphics card: Intel Haswell\n\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nShowing glitches on video sequence timeline when area of Video Sequencer resizing\n\nSteps shown on video\n\n[2020-12-02_15-19-26.mov](2020-12-02_15-19-26.mov)", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?", "Overlay: Edit-Mode: Anti-Alliasing not working with constructive modifiers\n```\nOperating system: Linux-4.15.0-50-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce 610M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n```\n\nthe bug is really intresting so... when you add mirror modifier to object.. and u enter edit mode and u select face or edges etc... the AA goes crazy it is so pixelised like even worse than tottaly without AA.\n\n\n\n\n\n\n\n", "Missing progress indicator for 'Render Audio'\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 570 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.83.4\n\nWhen we use the 'Render Audio' option from Render menu, after the rendering starts, there is no indicator about the rendering progress, how much time is left.\n\nIn any scene with audio in the Sequence editor, try using Render>Render audio command. There is no progress indicator. It is very vital specially for long length tracks.\n" ]

[ "VSE: Additional copy of audio strip appears in memory after undoing when using proxy and splitting\nOperating system: Linux-4.9.0-12-amd64-x86_64-with-debian-9.12 64 Bits\nGraphics card: Gallium 0.4 on AMD KAVERI (DRM 2.49.0 / 4.9.0-12-amd64, LLVM 3.9.1) X.Org 4.3 (Core Profile) Mesa 13.0.6\n\nBroken: version: 2.90.0 Alpha\n\nThis annoying bug with audio strips seems to affect Linux systems only. At first I thought that it's random, but then I noticed that it appears right after using undo. After several hours of investigating I narrowed down its cause to 3 triggers that have to be used together: using proxy, splitting movie strips and then using undo.\nI recorded a screencast with the steps to reproduce the bug:\nblender-audio-bug.mp4\nI hope my amateur investigation will help to find the root of the problem.\n\nThis bug is hard to reproduce, so please follow these steps strictly without doing any additional clicks/commands, on Linux. With those steps I managed to get the bug every single time.\nIf you mess the steps, it's necessary to restart Blender and start from the beginning. Do not use undo, except when it's in the steps:\n\n1. Add a movie strip (example.mp4)\n2. Set the end frame so that the strips fit in the range entirely.\n3. Select the video strip\n4. Set and generate 25% size proxy\n5. Go to the preview window and activate 25% size proxy\n6. We want to split both video and audio strips in half. Click in the sequencer to place the timeline somewhere in the middle of the strips and select the audio strip as well.\n7. Select Strip --> Split or press K\n8. Now we need to do some action to undo it later. In my example I add gamma cross, but it can be some other things. Although not every action seems to lead to the bug appearance, so, again, stick to these steps.\n9. Select the second half of the video strip and move it to the channel above, overlapping with the first half of around 200 frames.\n10. Select the first half of the video strip, then the second half and choose Add --> Transition --> Gamma Cross\n11. Now undo several times in a row using Ctrl+Z without clicking or pressing anything else, until the second half gets to its original place. \n12. What we got now is an additional invisible copy of the second half of the audio strip sitting in the memory. If you play the second half of the audio, you can notice that it got twice as loud because it's actually two identical audio strips playing at the same time. To reveal the invisible strip clearer, you can grab the visible second half and move it some frames to the right, so when you play, it will generate some echo because the visible and invisible strips would be playing with some delay between them. Or you can delete the visible second half of the audio and hear the invisible one still playing when there is no audio strips visible at all. Maybe it's the first part of the strip but overlapping the second one? Because when you use split it affetively creates a copy of the strip that has new strip offset marks.\n13. If you play the first part of the audio strip you can hear that it's intact. So the problem occurs only with the second part.\n14. So I assumed that maybe the problem is in the first part of the audio strip that overlaps the second one. Let's delete it. If you delete the first half of the audio strip, the hidden strip still plays, **but** if you delete the first part of the **video** strip, the hidden audio strip disappears.\nSo the fact that this bug only appears when using proxy, tells us that maybe **video** strips are involved in its cause.\nThe bug seems to be affecting only memory. If you save this file, after restarting Blender, the additional audio strip from the memory goes away.\n" ]

[ "Refactor: Replace socket declaration system for (Geometry) Nodes Panels\nThis is an internal refactor, follow up of #108897\n\n", "Crash Guide during render complete 2 December 9, 2022\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.4.0\n\nCrash Guide during render 2\n\nSame crash guide during render before and today.\nSee youtube: ZeCA2p5wISY\n\nHistory previous.\nT100691\n\n\n\n\n[Blender-2022-12-09-161546.ips](Blender-2022-12-09-161546.ips)\n\n[Horizontal Video.zip](Horizontal_Video.zip)", "CUDA misaligned address error when rendering the image\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nThe error occurs when rendering in a scene. It only occurs on the gpu and consistently occurs on optix and cuda. The scene starts rendering and gets to about 20/40 samples before the error occurs and it completely stops rendering. This happens both in viewport and render modes. Blender cannot be closed normally or go into viewport mode after the error occurs. It just crashes\n\nThe GPU is not running out of VRAM, Task manager shows blender barely uses 3GB VRAM before running into the error even though the gpu has 6GB\n\n`Misaligned address in CUDA queue copy_from_device (integrator_shade_volume integrator_queued_paths_array)`\n\n\n\n1. Open the scene\n2. Render image\n\nI have tried updating drivers, rolling back drivers, using previous versions (all the way back to 3.4)\n\nTest file: view?usp=drive_link", "The bridge tool fails in a situation with multiple rows of faces facing each other\nWin10 Pro 64 bit; AMD Ryzen 2700X; Nvidia GTX 1060 6GB; 32 gigs RAM\n\nBroken: hash d1be30f (buildbot build May 4).\nWorked: never\n\nIn a situation where you have multiple rows of faces that face each other across empty space (with other areas where they face away from each other). The bridge tool (even with*loop pairs* checked) is unable to give priority to the direction the normals are facing. The result of this is that instead of getting nice bridges among the multiple rows of cubes, the tool produces faces that overlap and have zero area. As hinted, the*loop pairs* checkbox in this case does not do anything and the result is the same.\n\nOpen the .blend, invoke the bridge operator (the result is the same whether or not \"loop pairs\" is selected.\n\n**blend**\n[IffyBridge.blend](IffyBridge.blend)\n\n[IffyBridge.blend](IffyBridge.blend) (updated blend)\n\nAn additional note; I submitted this issue years ago, but it was never fixed and I couldn't find my old report. If the bug is not going to be fixed, then just close this as a todo item or with a \"won't fix\" tag.\n", "Blender is crashing instantly to the desktop randomly (solid viewport)\n\nOS: Windows 10 Pro 64bit (Version 21H2, OS Build 19044.2006)\nGPU: Nvidia GeForce RTX 2070 (Driver: Version 517.48 (released 27th September 2022))\nCPU: AMD Ryzen 7 2700\nRAM: 64GB\n\n\nBroken: version: 3.3 (and versions for the last couple of years)\nWorked: none since 2020 approx.\n\n\nBlender crashes seemingly randomly when performing modelling actions such as moving vertices, clicking sliders or buttons, switching to wireframe view, or moving the viewport camera in any way. There may be other actions that cause crashes. Crashes cause Blender to instantly close to desktop, leaving no crash dumps. Crashes occurring over multiple versions since 2020, multiple reinstallations of the OS, and clean reinstallations of graphics driver.\n\nUsing blender_debug_gpu.cmd, I was able to retrieve a log from a crash that has some differences to a normal log:\n\n\"*INFO (gpu.debug): Notification : Buffer usage warning: Analysis of buffer object 82 (bound to GL_SHADER_STORAGE_BUFFER (1)) usage indicates that the GPU is the primary producer and consumer of data for this buffer object. The usage hint supplied with this buffer object, GL_STATIC_DRAW, is inconsistent with this usage pattern. Try using GL_STREAM_COPY_ARB, GL_STATIC_COPY_ARB, or GL_DYNAMIC_COPY_ARB instead.*\"\n\nCurrently, have no way to reproduce the crashes at will, they just seem to happen during my normal work. Load tests using OCCT do not cause crashes.\n\n**Debug log from crash**:\n[blender_debug_output2.txt](blender_debug_output2.txt)\n\n**Normal debug log**:\n[blender_debug_output_normal.txt](blender_debug_output_normal.txt)", "USD: Crash when loading the Intel Moore Lane demo asset (related to Color Attributes)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 528.24\n\nBroken: version: 4.0.0 Alpha\nBroken: version: 4.0.0 Alpha\nWorked: version: 4.0.0 Alpha\n\nCrashes during import of the Intel 4004 Moore Lane asset. Seemingly related to Color Attribute processing though the stack traces for the crash are not related.\n\n- Download the \"4004 Moore Lane v 1.1.0\" asset: 4004-moore-lane/\n- Attempt to import the `USD\\4004MooreLane_III_03_ASWF.usd` file with default settings --> observe crash\n- Attempt to import the same file but with the \"Color Attributes\" option unselected --> works\n\nOddly, the crashing stack occurs inside tbbmalloc and while seemingly dealing with mesh normals...\n```\n...\ntbbmalloc.dll!00007ffd7fa29f4e()\tUnknown\nblender.exe!MEM_lockfree_mallocN_aligned(unsigned __int64 len, unsigned __int64 alignment, const unsigned char * str) Line 310\tC\n[Inline Frame] blender.exe!blender::GuardedAllocator::allocate(unsigned __int64) Line 47\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::allocate(__int64) Line 425\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::get_buffer_for_size(__int64) Line 419\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::{ctor}(__int64) Line 122\tC++\nblender.exe!blender::bke::mesh::mesh_normals_loop_custom_set(blender::Span<blender::VecBase<float,3>> positions, blender::Span<blender::VecBase<int,2>> edges, const blender::offset_indices::OffsetIndices<int> faces, blender::Span<int> corner_verts, blender::Span<int> corner_edges, blender::Span<blender::VecBase<float,3>> vert_normals, blender::Span<blender::VecBase<float,3>> face_normals, const bool * sharp_faces, const bool use_vertices, blender::MutableSpan<blender::VecBase<float,3>> r_custom_loop_normals, blender::MutableSpan<bool> sharp_edges, blender::MutableSpan<blender::VecBase<short,2>> r_clnors_data) Line 1368\tC++\nblender.exe!blender::bke::mesh::mesh_set_custom_normals(Mesh * mesh, float[3] * r_custom_nors, const bool use_vertices) Line 1642\tC++\nblender.exe!blender::io::usd::USDMeshReader::process_normals_face_varying(Mesh * mesh) Line 797\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_mesh_sample(blender::io::usd::ImportSettings * settings, Mesh * mesh, double motionSampleTime, bool new_mesh) Line 853\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_mesh(Mesh * existing_mesh, USDMeshReadParams params, const char * * __formal) Line 1094\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_object_data(Main * bmain, double motionSampleTime) Line 249\tC++\nblender.exe!blender::io::usd::import_startjob(void * customdata, bool * stop, bool * do_update, float * progress) Line 288\tC++\n\n```\n\n", "Combine crash\nOperating system: win 10\nGraphics card: 3090\n\nBlender Version 3.5.1 \n\nWhen using ctrl+j to combine components, blender will crash.\n\n", "Shader compilation freeze Blender on Intel Arc770\nOperating system: Windows 10\nGraphics card: Intel Arc770 16Gb (Resizable Bar enabled)\n\n3.6.0\nDate: 2023-06-27 08:08\nHash: c7fc78b81ecb\nBranch: blender-v3.6-release\n\n**Intel driver version**\n31.0.101.4665\nReleased 11.08.2023 (latest on moment of this post)\n\nAll modes of viewport on new scene (default, for example) works fine: solid, material preview, display render. But, if I open my scene, works only 1 and 3 option. Building a shaders freezes Blender. It's around 800+ materials on scene, and GeForce cards works fine with that. The video card works at full power, with enabled Resizable Bar function. Cycles render (oneAPI) also works fine, but i can't switch the viewport on material preview. Blender freezes when shaders start compile.\n\n", "Crash on Mac when starting with `--debug-gpu` flag\nOperating system: Mac OS Ventura 13.1\nGraphics card: Apple M1 Max\n[system-info.txt](system-info.txt)\n\nBroken: 3.4.1\nWorked: 3.3.2\n\nBlender won't start on a Mac when starting with `--debug-gpu` flag.\nThe terminal output is this:\n\n```\n/Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\nRead prefs: /Users/vollstock/Library/Application Support/Blender/3.4/config/userpref.blend\nWARN (gpu.debug): source/blender/gpu/opengl/gl_debug.cc:165 init_gl_callbacks: Failed to hook OpenGL debug callback. Use fallback debug layer.\nzsh: segmentation fault /Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\n```\n\n\nStart with the flag\n\n```\n/Applications/Blender.app/Contents/MacOS/Blender --debug-gpu\n```", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Scripting: undo after mesh.separate causes crash\nOperating system: Linux\n\nLatest tested: blender-3.5.0-beta+v35.f23e3c7f04f3-linux.x86_64-release\nEarliest tested: blender-3.1.2-linux-x64\n\nTrying to undo `bpy.ops.mesh.separate(type='MATERIAL')` in a script crashes Blender.\n\n1. Create a cube and two materials. Go to edit mode and assign some faces to both materials. Go back to object mode.\n\n \n\n2. Open the Text Editor and run this script\n\n ```py\n import bpy\n bpy.ops.ed.undo_push( message = \"temp\" )\n bpy.ops.mesh.separate( type = 'MATERIAL' )\n bpy.ops.ed.undo()\n ```\n\n3. Crash (segmentation fault).\n\nSomewhat mysteriously if I save just before running the script, close Blender, then reopen the .blend and then run the script, I get non-determinstic results (sometimes the undo does nothing, sometimes the white part is gone). The only consistent way I found to get a crash was to create the cube from scratch every time. So no .blend is attached to this issue.\n\n", "Flashing vertices on screen updates\nWindows 10 Home, version 1909, 64-bit\n| Graphics card: | Author:\n| -- | -- |\n| GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 | @Code_Craft_Plugin\n| GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89 | @MontagueMGM\n\nBroken: 2.83.0 - 2.83.10 (still broken as of latest 2.92.0 alpha experimental build acbda123ad08)\nWorked: 2.82.7\n\nVertices flash when the screen is updating. Only on my desktop using a GTX 780, not my laptop using an i7-1065G7 (Intel Iris Plus)\n\nCreate an Ico Sphere with subdivisions set to 6. It happens at levels 5 and 7 as well, but not nearly as noticeable. It seems related to a specific vertex count, rather than proportional to the number of vertices.\n\n[Blender 2021-01-12 02-13-49.mp4](Blender_2021-01-12_02-13-49.mp4)", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "Knife tool fails on a non-planar n-gon\nBroken: 2.74 up to and including 2.92 master\nWorked: 2.73 (yes, I bisected that far back ;) )\n\n\nKnife tool fails to cut between verts in n-gons of certain configuration.\n\n\nLoad the attached .blend and try to make a knife cut between the two selected verts (i.e. try to create an edge connecting them).\n\n[knife_fail.blend](knife_fail.blend)\n\n(If you want to test in 2.73 yourself, copy the object from a running instance of 2.9x into 2.73 using ctrl+c/ctrl+v, then replace the mesh in another existing mesh object).", "UI: In Preferences, Invisible Execute Region in Nav_bar, blocks resize of area.\nBroken: 957b4547ae, 6b082278d1\nWorked: never?\n\nWhen you try to resize preferences, you grab the execute region edge instead(Only for nav_bar side).\nThe default state, has the area open but invisible. Blocking resize.\n\nSeparate preference window, does not have a problem.\n\n[2019-05-10 09-01-29.mkv](2019-05-10_09-01-29.mkv)" ]

[ "Assert when trying to section the Data Property area from top to bottom.\nThis is the assert:\n```\n13: BLI_system_backtrace - 0x7F2A5BE0\n12: GPU_viewport_draw_to_screen - 0x7E865840\n11: wm_draw_region_blit - 0x7DDE3060\n10: wm_draw_window_onscreen - 0x7DDE3510\n9: wm_draw_window - 0x7DDE38E0\n8: wm_draw_update - 0x7DDE1DA0\n7: WM_main - 0x7DD9DC60\n6: main - 0x7DD965B0\n5: invoke_main - 0x816FC870\n4: __scrt_common_main_seh - 0x816FC630\n3: __scrt_common_main - 0x816FC610\n2: mainCRTStartup - 0x816FC930\n1: BaseThreadInitThunk - 0x32233020\n0: RtlUserThreadStart - 0x33571530\n/src/blender/source/blender/gpu/intern/gpu_viewport.c:524, GPU_viewport_draw_to_screen(), at 'h == BLI_rcti_size_y(rect) + 1'\n```\n\nWith the mouse cursor in the upper left corner of the `Data Property` area try to section this area (without using the preview).\nThe assert message will be displayed indicating that the size of the 3dview area is different from the size of the viewport.\n" ]

[ "Eevee: Unknown bug when just create first shader \nStep to reproduce an issue (or bug?):\n1. Run latest Blender v3.4alpha (Experimental build) with Eevee Next integrated.\n2. Create scene with just one Cube.\n3. Go to Properties > Material panel > Create New material.\n4. Boom! Blender shut down imidetily.", "Particle Texture influence broken when using two particle system on the same object\nOperating system: Ubuntu 18.04\nGraphics card: GeForce 970GTX\n\nBroken: 2.90.1\nWorked: Never (2.8+)\n\n\nWhen using two particles system on the same object with an influencing texture, one particle system has a wrong influence (e.g. Particle System shrink to quickly)\n\nBlend File: [particle_texture_bug.blend](particle_texture_bug.blend)\n\n0. Set the animation start and end to 100 - 200\n1. Create an Emitter and a Particle Object\n2. Add a Particle System to the Emitter and use the Particle Object for rendering\n3. Set the Start and End to 100 - 200\n4. Give the Particle System a Blend Texture that influences the size with \"Strand/Particle\" as Coordinates\n5. Add another System and Duplicate the previous one to get the exact same setting\n6. Change the Start and End of the new System to 0 - 100\n7. Bake all Dynamics\n8. Render Frame 199 and compare to rendering of 101. The particles in 199 are tiny in comparison (or invisible). They should look near identical\n\nOptional: \n9. Remove the 0-100 Particle and Redo Baking\n10. Frame 199 now has normal sized particles\n", "Armature animation glitch when using collection instances across scenes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\nWorked: Probably never (2.90 is buggy still)\n\nWhen an armature is included in a collection, and that collection is instanced in another scene, selecting a bone or moving in the timeline creates a seemingly random time-jump in the posing/animation, until the bone is moved, at which point the whole armature snaps back into its real position.\n\nThis issue only occurs when an armature is included in a collection that is instanced in another scene. If the armature is not in a collection or is not instanced, the animation plays back as expected. The meshes under the armature does the same, if one mesh stays in the collection, the bug still happens, everything needs to be removed for the bug not to happen.\n\nWorkaround:\nMoving the bone causes the entire armature to snap back into its correct position, so this can be used as a workaround to keep the animation accurate. Alternatively, the armature can be removed from the collection and into the main scene hierarchy.\n\nThank you for looking into this issue.\n\n* Open attached file\n* Click on any bone\n\nThe pose will change. Change frame and pose will jump unexpectedly again.\n\nSome info that may be helpful: This issue seems to happen when persistent data is enabled and frame is rendered. Armature will then \"remembers\" last rendered frame. The cause may be linked to usage of Autorig pro addon.\n", "Material Preview (and final render in EEVEE) purple\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7263\n\nBroken: version: 2.83.0\nWorked: I don't remember this bug occuring in previous versions.\n\nI know, that materials should become purple when the texture is missing.\nBut the problem is that they not behave as they should even without applying textures and also with the default material.\nThis bug occurs in EEVEE:\n1) In material preview in properties\n2) In render\n3) Sometimes - in viewport\n\nIn a render, it is also a problem with the scene surface material.\nI attach some screenshots from material preview: they are all the same default material.\n\n\n1) Open Blender\n2) Press F12 or go to material preview in object settings.\n3) ... see the bug\n\n\n\n\n\n\n\n\n", "User Interface: Float Curve: bug when control points has same X position\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nUser Interface: Float Curve: bug when control points has same X position\n\nIf the points are located on the same X axis, then the result breaks.\n\n| [Set Curve Parameter Bug.mp4](Set_Curve_Parameter_Bug.mp4) | [2022-10-19 15-45-49.mp4](2022-10-19_15-45-49.mp4) |\n| -- | -- |\n\n[simple example float curve.blend](simple_example_float_curve.blend)", "Wrong result mixing 2 nodes of an image texture\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.3, 2.93\nWorked: unsure\n\nWhen using 2 nodes of the same texture and connecting the Color output from one and the Alpha from another, the result looks different in comparison when using both outputs from one node. Broken in EEVEE\n\n1) Open the file, switch to material preview/rendered\n2) Reconnect the color (or the alpha) link to another texture\n[Bug1.blend](Bug1.blend)", "Shadow catcher problem with holdout collection\nOperating system: *Windows 10 Pro 64 bits*\nGraphics card: *2x NVIDIA GTX Titan X*\n\nBroken: *master 2.81a*\nWorked: *Worked on blender 2.79b*\n\nWhen shadow catcher is activated in an object located in a collection with the holdout option, alpha is truncated.\n(more visible when there is motion blur)\n\nBased on the default startup :\n- set render engine to cycles\n- set Film parameters to Transparent\n- activate Motion Blur\n- set world backgound color to white (better visibility)\n- delete light\n- create a plane, scale x2\n- move plane to a new collection\n- set plane to shadow catcher\n- set collection 2 (called by default, with the plane) to holdout\n- animate camera for have motion blur (more visible when there is motion blur)\n- in viewport render, you will have that : \n- render.\n\nwithout motion blur :\n antialiasing problem\n\nwith motion blur :\n\n\nsame render result with and without alpha on composite node :\n\n\n\n.Blender here : \n[#73376.blend](T73376.blend)", "Volumetrics Doesn't Apply to other meshes created with the Array Modifier\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nIn evee, I have a cube with an array modifier and a volume scatter node in its material. The volume scatter only applies to the original object, not the objects created by the array modifier. However in cycles the volume scatter works as expected.\n\nCreate Cube with Fog material *see attached blend\nObserve where the volume scatter takes effect when switching between evee and cycles.\n\n\n\n[FogBug.blend](FogBug.blend)\n\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "\"Join Meshes\" changes the material slot assigned to faces of the original mesh\nOperating system: MacOs BigSur\n\nBroken: 2.91.2\n\nSee video:\n[Screen Recording 2021-02-12 at 12.04.24.mov](Screen_Recording_2021-02-12_at_12.04.24.mov)\n\n1) Create Mesh ONE with 2 material slots, with the same material, each slot assigned to different mesh island in mesh. \nSo faces on mesh islands have different material_indexes, although both use the same material (in different material slots)\n2) Create Mesh TWO without any materials\n3) Join Mesh TWO into Mesh ONE\n4) Check material indexes in resulted mesh. They wil ALL point to first material slots.\nFaces, that was linked to second material slot initially will be \"relinked\" to first slot, so theier material_index attributes are altered/messed \n\n**Expected behaviour:**\nFaces linked to second material slot initially should stay with the same material_index, join action has no reason to change them\n\n", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "Viewport display of multiple Dupli-Collections when different draw-types are used : wireframe might disappear (only selected are garuanteed to draw)\nOperating system: Windows 10 / Ubuntu 20.04\nGraphics card: GTX 1080 / RTX 3080\n\nBroken: 2d9d08677e a2d59b2dac \nBroken: all versions >= 2.8\nWorked: 2.79\n\nViewport display of Dupli-Collections is inconsistant.\nDigging deeper into it, it looks to be when there are different draw types on the same dupli-collection\n\n1. Open attached blend file\n2. select the empties in the middle of the screen which do not look like they have anything attached\n3. notice how they randomly appear / disappear upon selection.\n4. note that one of instancer is set to `Textured` draw type, the other to `Wire`, if all are set to `Wire` the issue is gone\n\nThis has happened in quite a few of our production scenes.[bug.blend](bug.blend)\n\nNOTE: Might boil down to be the same as #101822 (Collection instance set to Display As Wire doesn't show in Solid mode when not selected) or #86732 (Instanced wire objects are hidden in solid mode instead wire appearance)\n\n", "Hair with material using a non-existing attribute looks different between Eevee and Cycles\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.00.20.220516\n\nBroken: version: 3.4.0 Alpha\nWorked: -\n\nHair can be affected by materials that use attributes such as mesh.\nThe color of the mesh at the root position of the strand usually defines the color.\nBut that's not the case in Eevee if an attribute doesn't exist.\n\n\nThe actual color can be kind of undefined, but there should be a convention between the renders.\n\n- Open attached .blend file\n- Compare Cycles and Eevee\n[hair_material_with_non-existing_attribute__bug.blend](hair_material_with_non-existing_attribute__bug.blend)\n\n", "Linked Instances Across Scenes have unreliable updates when editing their common mesh data.\n\nBroken: 2.93.4 LTS;\nBroken: master\n\nWith two different objects in two different scenes sharing a same obdata Mesh, editing the mesh in one of the scene can fail to properly update object in the other scene.\n\n- Open attached file.\n- Go to scene 2.\n- Switch to Edit mode.\n- Assign the red material (first slot) to the cube in edit mode.\n- Switch back to Object mode.\n- Go to Scene 1, the Cube in Scene one still uses the second slot material (green).\n# Switch to edit mode and back, now the cube is shown with expected first material slot (red) as well.\n\nNOTE: If you replace step 4 by a mesh geometry editing (e.g. rotate the mesh in Edit mode), in current master there is the same missing update issue in Scene 1, but in 2.93LTS it is properly updated... Regression introduced by 51568030e9.\n\n[Example.blend](Example.blend)\n\n------------------------\n\n# Original report\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.0\n\nIf you link an instanced object to another scene, having it's material link to object, it can have a different material from the non-instance. However upon saving and re-opening the scene, the instance's material will revert to that of the non-instance. \n\n- Open attached file or\n - Take the default cube and assign a material to it. In the viewport display settings assign a color for the material, this will give feedback in the viewport to highlight the issue. \n - Create another material on the same cube and once again assign a color in the viewport display settings.\n - Set both materials to Object Link in the material properties. \n - Name the current scene \"Scene 1\" and proceed to create another scene named \"Scene 2\".\n - Return to Scene 1, and using Alt+D instance the cube.\n - Using Ctrl+ L, link the instance to Scene 2. Delete the newly created instance in Scene 1.\n- In Scene 2, assign the instance a different material than Scene 1 in edit mode. You now have 2 scenes, with 2 cubes that share mesh data, but that are using 2 different materials. This is the desired goal in practice.\n- Save the file and re-open it. Blender will have automatically assigned both cubes to 1 material.\n[Example.blend](Example.blend)\n", "EEVEE Shading: string sockets node group interface value doesn't work\nBroken: version: 3.0.0 Alpha\nWorked: n/a\n\nin shading, String sockets exposed via node group interface don't use the value from the node group interface\n\nSteps to illustrate the problem\n\n* Use a quick smoke effect on a cube\n* Add a principled volume and connect it to material volume output\n* Change the Density Attribute to other text\n* Group the principled volume\n* Change the Density Attribute back to density\n\n[volume.blend](volume.blend)\n\n" ]

[ "Blender 2.81 / 2.82 indirect only /holdout not work Mac OS mojave\nOperating system: Mac Os Mojave\nGraphics card: Radeon Provega 58 8 GB\n\n2.81 2.82\n\n\nit's becoming frustrating to work with blender with mac os, now i discovered that indirect only and holdout in the outliner, do not work, I attach video to show the problem, theissue is the same in 2.81 and 2.82. [indirect_only_bug.mp4](indirect_only_bug.mp4)\nindirect only and hold out they don't do what you expect, even if they are selected they are ignored in the render, the problem with the holdout i shown in the video. The problem is only with EEVEE in cycles all works fine.\n\n", "Weird behaviour of Holdouts in Eevee\nOperating system: Windows 10 Pro (1909)\nGraphics card: Quadro 4100M\n\nBroken: v2.82\nWorked: n/a\n\nHoldouts in Eevee sometimes work, sometimes don't.\nI've got four \"output\" projects total, and two libraries. All of the projects use Eevee as the render engine. Three out of four of the projects that use the Holdout setting in the Outliner work as expected, with the \"mask\" objects being within the file itself.\nOne project that does the same thing renders the mask objects with the default material, while the mask object's collection is linked from a library.\n\n1. Create lib.blend with a collection containing an object to serve as a holdout object. (My case was leaving the materials empty)\n2. Create proj.blend which links the collection from lib.blend, and set holdout on the parent collection\n\nIn Cycles, this will render as expected - the linked collection's objects will be used as holdout/mask objects.\nIn Eevee however, the linked collection objects will be rendered with the default material instead.\n\nAlso note, that in the rendered viewport, the holdout behaves as expected.\n\n**Workaround**\nIn lib.blend, set the material on the collection's objects to \"Holdout\".", "Collection's holdout works wrong in EEVEE if objects share same material across collections\nOperating system: Linux-4.15.0-72-generic-x86_64 ubuntu 18.04 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 5)\nWorked: not found\n\nCollection's holdout works wrong in EEVEE if objects share same material across layers\n\n* Setup scene with 2 objects in 2 collections with one material, or use the file\n[holdouttest.blend](holdouttest.blend)\n* Set Holdout to first collection in the list\n\n* Result - both objects are masked:\n\n* Set separate material for one of the objects - now it works as expected:\n\n\n" ]

[ "Able to paint/select \"through\" disabled UI items.\nBroken: 2.80, 2.81...\n\nWith region overlap, if a UI element is diabled, clicks are passed through it, which can result in paint strokes.\n\n\n1. Load the default scene and enter Texture Paint mode on the cube.\n2. Add a paint slot and make a stroke.\n3. In the UV/Image editor, select the painted image, open the sidebar and switch to Image tab. The UI items should be disabled there now.\n4. Make sure that sidebar overlaps the image.\n5. Click on sidebar background.\n6. Click on any of the disabled items.\n\nIn (5), nothing happens. In (6), the click passes through and leaves a paint stroke on the image.\n\n", "Sculpting Has Unexpected behavior when Saving work\n**Broken**: 2.83.4, 2.90 beta 97dc370c50ed\n**Worked**: 2.82\n\n\nGlitches in the non-active mesh after sculpting the active mesh, saving, and updating the viewport.\n\n\n[Ogre.blend](Ogre.blend)\n\n* Sculpt\n* Save\n* Refresh viewport (e.g., continue sculpting)\n\nThe artifacts should be visible immediately.\n\n**Original message**\n\nWhen I am sculpting and I go to save my work, after a successful save I get weird artifacts in the mesh that I havent made edits on in sometime. And it seems to be the same mesh every time. This has happened over 5 times so i figure its just a visual bug.\n\nGet 2 seperate meshes ready to sculpt, then sculpt on one and save your work. This is all i did to see the bug arise.\n\n\n", "Click selection and box selection in 3D view do not work properly in scenes with many objects\nOperating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\n[In my environment, if there are close to 100,000 objects, the objects can not be selected normally]\n[select_bug.mp4](select_bug.mp4)\n\nUploaded blend file has nearly 100,000 simple cubes\nClick on an object in the 3D view to select a distant object\nEven a box selection can make a crazy choice\nBut lasso selection and circle selection work fine\n[test_file.blend](test_file.blend)\n\n", "Mesh: Subdivide op flushes selection too eagerly\nBroken: 2.92 master\nWorked: N/A\n\n\nThe Subdivide operator selects geometry that it shouldn't. Consider this example:\n\n\n\nIt looks as if the op flushes selection a bit too much. Note that the 'Expected' selection is valid selection in edge mode, as the edge rings around the rims are **not** selected. Those edges should neither participate in the op, nor be selected as the result of it, if vertex selection mode is not enabled.\n\nA better example:\n\n\n\n...here in face mode, a lone edge is getting selected by the op.\n\n\n1. On the default cube, in face mode select top and bottom faces, inset and bridge them.\n2. In edge mode select vertical edge rings.\n3. Subdivide.\n\nAlternatively, load this simplified example file:\n\n[subdivide_selection_issue.blend](subdivide_selection_issue.blend)\n\n...and Subdivide. Resulting selection of the middle face is unwarranted.", "Wire objects that are being displayed on front only updates visibility after interaction\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.1 30.0.14023.7007\n\nBroken: version: 3.2.0 Alpha\n\nThis problem is similar to the one found in #84717, but in this case it is only affecting objects that are marked as in front and wired mode. I noticed it happening in a rig, but It can be applied at anything that is wire.\n\n\n- Using Any object go to viewport display and mark in front and set it to wire in the display as. (you can also use a rig with custom shapes, e.g. the one in rigify.)\n```\n{F12895660}\n```\n- Disable and then Enable Overlays\n[2022-03-03 11-21-26.mp4](2022-03-03_11-21-26.mp4)", "Edit mode. Wire become non-selectable dependent on resolution (regression)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWithout multisampling wire just disappear and with multisampling it is still visible but not selectable.\n\n[2019-09-14_23-07-53.mp4](2019-09-14_23-07-53.mp4)\n[2019-09-14_23-09-58.mp4](2019-09-14_23-09-58.mp4)\n\n\n\nTry to select loop and zoom in-out with and without viewport multisampling. Here the file, but bug will appear even with UV-sphere.\n[b.blend](b.blend)\n\n", "Alpha Blend material has inconsistent behavior with Geometry nodes\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nAlpha Blend material renders differently on the object, which is referenced inside Geometry Nodes tree of another object, despite this another object is already hidden and has muted GN modifier.\n\nIn attached file:\n* Remove/Select *Shell* object inside GN tree of object *Mesh*\n* Activate/Deactivate *Viewport Disable* for *Collection* or object *Mesh*\nIn both cases material becomes transparent or not\n\n", "Inconsistent tool selection and tool settings for different layouts\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Alpha\nBroken 2,83,9\n\nAs title said. Inside one layout all viewports have same settings and tool selection.\nExpected: global tool selection for SAME mode and editor. Different tool selection for different editors: 2D paint and 3d paint uses same brush inside one layout (and it is pain because zoom is different)\n\n[2021-02-09_04-19-36.mp4](2021-02-09_04-19-36.mp4)\n", "Cycles misses intersections when objects are too close\nBroken: 2.79b\n\nWhen two objects are too close, Cycles can miss intersections.\nIn the attached file, there are two intersecting semitransparent planes (at the center).\nIf the color is green or pink it indicates that the ray only intersected one plane.\n\n- Open the attached .blend file and render.\nNote how the line where the planes intersect has a coloured border.\n[transparent_planes.blend](transparent_planes.blend)", "3D Texturing: Fix seam bleeding non-manifold meshes\n", "Video Editing (outline on the border)\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\n\nSome images with an alpha channel have grey outline when scaled up and different bicubic or bilinear interpolation is used.\n\nIssue is visible immediately after opening .blend file\n[#86861.zip](T86861.zip)", "Aliased wireframes + modifier edit mode display issue\nOperating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 3.4.1\n2.90\nWorked: 2.79, 2.81\n\nEdit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range.\n\n**Steps to reproduce**\n\n* Open file\n* Disable all anti-aliasing and smoothing in preferences > Viewport > Quality\n\nSelection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.", "Select Loop Inner-Region issue\nWin8 64bit | GTX680\n\nBroken: 2.77 509270e\n\nWhen working with face loop, this tool doesn't always work as expected.\n\n\n\n\nNot sure if this can be a bug. Please check.", "Weight paint vertex select difficult to see (depends on surface color)\nThis is an issue since 3.2x\n\n**Short description of the issue**\nVertex selection is difficult to see in some cases, depending on the surface color.\n\nChanging the view-port shading \"Color\" can make the unselected vertex color match the selected vertices color.\n\n<video src=\"attachment\" title=\"screenshot.webm\"></video>\n\n**Exact steps for others to reproduce the issue**\n- Open attached .blend file.\n", "Greasepencil z fighting alpha issue\nHi,\nnot too sure if this is known issue or any fix but I am getting this alpha issue from certain angle when I have 2 different grease object. \n\n" ]

[ "Problems selecting vertices or faces in Blender 3.6\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nProblems selecting vertices or faces depending on the distance from the camera in Edit Mode\n\nI am modelling a door and in Edit Mode I have experienced errors in the selection of vertices or faces. Depending on the distance or angle of the camera from the object there are vertices that are not selected even with a Box Selection, and when I try to select a face of the geometry closest to the camera it selects the back face, as can be seen in the attached images.\n\nI have tried on another PC with the same version and the result is the same.\n\nIn version 3.5.0 it works perfectly on both PCs with the same object.\n\n" ]

[ "Blender crashes with Segmentation fault when selecting Render Preview in Cycles with GPU Compute\nOperating system: Linux-6.1.46-gentoo-gentoo-dist-x86_64-12th_Gen_Intel-R-_Core-TM-_i3-12100F-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 6400 (navi24, LLVM 16.0.6, DRM 3.49, 6.1.46-gentoo-gentoo-dist) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 3.6.0\nWorked: - (read description)\n\nWhen I try to render using Cycles on my GPU, blender immediately crashes with Segmentation fault, as the error message. Here are the logs that were shown right before the Segmentation fault:\n```\nI0903 17:06:40.864868 14239 device.cpp:511] Mapped host memory limit set to 12,302,073,856 bytes. (11.46G)\nI0903 17:06:40.865039 14239 device_impl.cpp:62] Using AVX2 CPU kernels.\nWriting: /tmp/blender.crash.txt\nzsh: segmentation fault blender-3.6 --debug-all\n```\nIt worked with =dev-libs/rocm-comgr-5.3.3-r2, but started happening after the new update of the package. I used to apply a patch that solved the problem of being unable to select the render device in Blender's options (27552#issuecomment-1379233453), but with the new rocm-comgr package, the original problem solved itself. The old version of Blender (version 3.5.1) that worked before rocm-comgr got the new update, doesn't work now.\n\n1. Open the Render properties tab and set the Render Engine to Cycles.\n2. Set the device to GPU Compute.\n3. Set the viewport shading to Rendered.\n\n", "AMD HIP with 7900XTX crashes using Cycles in Blender 3.6\nOperating system: Ubuntu 22.04.2\nGraphics card: RX 7900 XTX\nROCM/HIP is version 5.5.1\n\nBroken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: c7fc78b81ecb, type: release\nWorked: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b, type: release\n\nWhenever I try to render anything (default cube included) in 3.6 with Cycles using GPU compute I get the following error in the console:\n`:0:rocdevice.cpp :2788: 4112443167 us: 28547: [tid:0x7f38b247d600] Callback: Queue 0x7f3793600000 aborting with error : HSA_STATUS_ERROR_INVALID_ISA: The instruction set architecture is invalid. code: 0x100f\nAborted (core dumped)`\nDownloaded 3.5 and it works just fine there. Using CPU in 3.6 also works. Can't seem to find the coredump anywhere (did ulimit -c unlimited and even disable apport but in none of the directories where I would expect a coredump I got one). \n\nTo reproduce:\n1.Open Blender 3.6\n2.Change to Cycles with GPU compute\n3.Press F12\n\n", "Crash (Seg Fault) When Rendering Grease Pencil Stroke on Render Farm\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.1\n\nOur render farm of 70 iMacs has been running for 3 years through the 2.7x series up till 2.81a.\nWhen we switched to 2.83 last week it started crashing consistently when rendering Grease Pencil strokes.\nThe crash occurs when using Blender to do command line rendering via an SSH session on a machine without the user physically logged in. (Crashes on Mac and Linux)\n\nCommand Line Rendering on my own machine works fine.\nCommand Line Rendering on a remote machine via SSH works fine if I'm also logged into that machine.\nBut as soon as I log out of the machine so that the SSH session is the only active user on the machine, then the error shows up.\n\nI tested this on 2.81a and the error (below) shows up there too, but in 2.81a it doesn't also lead to the Segmentation Fault that crashes Blender.\nIt's only in 2.83 (and 2.83.1) that the error is followed by the Seg Fault 11\n\n\n**_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.\nWriting: /var/folders/jk/7b488ncn6c13t515bnt6q_8w68xcj1/T/test.crash.txt\nSegmentation fault: 11**\n\non Linux the error message is slightly different, but still a crash:\nUnable to open a display\nAborted (core dumped)\n\nContents of test.crash.txt (from the Mac crash)\n# Blender 2.83.1, Commit date: 2020-06-25 09:47, Hash 8289fc688b3e\n\n# backtrace\n0 Blender 0x00000001079eb9d7 BLI_system_backtrace + 55\n1 Blender 0x000000010159ddb8 sig_handle_crash + 392\n2 libsystem_platform.dylib 0x00007fff5db5fb3d _sigtramp + 29\n3 ??? 0x00007f8594802010 0x0 + 140211698802704\n4 Blender 0x0000000101a39da2 DRW_opengl_context_create + 66\n5 Blender 0x00000001018f47d5 WM_init_opengl + 37\n6 Blender 0x0000000101a374ff DRW_render_gpencil + 127\n7 Blender 0x0000000105de5ef4 RE_engine_render + 1156\n8 Blender 0x0000000105df06d3 do_render_all_options + 387\n9 Blender 0x0000000105df2a14 RE_RenderAnim + 2260\n10 Blender 0x000000010159c9dd arg_handle_render_animation + 141\n11 Blender 0x000000010797880d BLI_argsParse + 173\n12 Blender 0x000000010159a497 main + 855\n13 libdyld.dylib 0x00007fff5d974ed9 start + 1\n14 ??? 0x000000000000000a 0x0 + 10\n\n\n\n1) Make a new default file.\n2) Delete the Cube\n3) Add->Grease Pencil->Monkey\n4) Save as test.blend\n5) Copy test.blend onto a remote machine\n6) Make sure the machine is at the login prompt (showing the username password boxes).\n7) ssh into the remote machine\n8) command line render one frame from test.blend something like:\nBlender -b /test.blend -s 1 -e 1 -a\n\n", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "Render can not be cancelled and crashes\n\n\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nHello,\n\nI wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender hangs / crashes.\n\nI launched it using the GPU debug tool\n\nI'm assuming it comes from the hardware.\n\n\nThanks in advance.\n\n\n\n[eevee_logs.txt](eevee_logs.txt)\n\n\n[blender2.8.blend](blender2.8.blend)\n\n\n\n\n\n- Open the file\n- Render image {key F12}\n- Progress will hang at 0% for too long time\n- Cancel rendering\n\nRender job is not cancelled immediately / Blender crashes with low VRAM\n\n", "Freeze when using Object.ray_cast in a driver script\nOperating system: Linux-5.10.15-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.40.0, 5.10.15-1-MANJARO, LLVM 11.0.1) AMD 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.91.2, 8dc95f61f3\nWorked: Unknown, fails on at least as old as 2.83.10.\n\nRunning a driver that includes a call to Object.ray_cast will freeze the interface entirely. Still exits normally when sent a SIGTERM. It does not create a crash.txt. Blender crashes with a segmentation fault in version 2.83.10 (hash: `b439a155442b`), and does create a crash.txt (see attached). Blender version 2.93.0 Alpha (hash: `7a608f88a713`) also freezes in the same way as 2.91.2. Using the ray_cast function in a non-driver script appears to function as expected.\n\nIn the attached blend file, run the text block `TurretRayCasting.py`, to put the script into the driver namespace. Next, click \"update dependencies\" in the driver panel. The application should freeze entirely. If `return target.ray_cast(turretTargetSpace, direction)- [x]` is commented out and replaced with `return True`, the application does not freeze.\n\n[driver_freeze2.blend](driver_freeze2.blend)\n\n[driver_freeze2.crash.txt](driver_freeze2.crash.txt)\n\n[system-info-2.91.2.txt](system-info-2.91.2.txt)", "Topbar gliches\nOperating system: Windows 10\nGraphics card: RTX 3060\n\nBroken: 3.3 Beta\n\nThis only happened on windows.\nWhen Status Bar is hidden and Resolution Scale is greater than 1, the Top Bar sometimes becomes unusable. (look at the end of video)\nMy guess it has something to do with notifications that are now displayed at Top Bar.\n[bug.mp4](bug.mp4)\n\nSame as in the video\n- On the `Windows` tab disable `Show Status Bar`\n- Go to {nav Edit > Preferences... > Interface} and change the `Resolution Scale` to 1.2\n- Save Preferences\n- Close the Temporary Window\n- Reopen the `Blender Preferences` window ({nav Edit > Preferences...})\n- Press `Save Preferences`\n\nInvoking save as temporary window also causes this issue\n\nTrying to resize Top Bar area or maximizing some other area fix the issue.", "GPU Compute is not available\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: GeForce GTX 660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.6.2\n\nGPU Compute is not available in render device untill recheck\n\n\nAn interesting circumstance was discovered:\nIf open `preferences/System/CUDA` and just uncheck and check the checkbox of GPU Device, the problem is solved, then GPU Compute is accessible and fully functional.\n\nhad a similar problem: 94699\nThe solution is supposedly installing a newer version of nvidia driver. However, in fact, Blender works fine with the existing version.\n\n", "Correct link is shown as invalid\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIn the composer, after some actions, the link is displayed as incorrect, although there is no reason for this.\n\n**Exact steps for others to reproduce the error** \n\n0. Factory settings file (optional).\n1. Switch render engine to Cycles.\n2. Enable any `Scene > ViewLayer > Passes`. For example, this would be `... > Data > UV`.\n3. Enable the compositing nodes and connect the new socket to the \"Composite\" node.\n4. Switch render engine to Eevee.\n5. Make a Render.\n6. Switch render engine to Cycles.\n\n\n\n", "Eevee randomly causes system to crash when rendering\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23 (8GB memory)\nCPU: Intel Core i9 9900k\nRAM: 32GB DDR4\n\nBroken: 3.0.0\n\n\nI'm new to Blender and currently trying to switch from my usual C4D and Redshift workflow, just to let you know.\n\nI have a fairly simple scene with a 250 frame animation. Everytime I render the animation with Eevee as a .png sequence with an .exr file for the layers, the process causes my system to crash.\nThe amount of samples seems to correlate with the amount of frames I'm able to render before failure. So I guess it might have something to do with memory.\n\nI'm not sure how that can be as more complex scenes never failed me before using Redshift as a render engine.\n[ocean_final.blend](ocean_final.blend)\nThe scene makes use of a lot of volumetric light and I also calculate the bloom.\n\nThere aren't a lot of vertices involved in the scene, but I'm not sure how I can display a value to give you here.\n\nAll drivers are up to date and I also reinstalled Blender.\n\nNot sure, but I attached the .blend file as well as logs created in debug mode.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)", "Cycle gpu rendering crashes randomly\nOperating system: Win11\nGraphics card: Nvidia RTX 3070 Ti\n\nbroken: all 3.0 versions\n\nRenders keep crashing randomly when I’m using my gpu with cycles, I updated my drivers, my memory use is okay, I tried to not use denoiser, lower my samples, resolution etc but nothing works, sometimes it render 10 frames sometimes 100 but it can't render my whole animation without crashing (also for animations with low poly count and small textures tiles) \nDon't know how to read the crash log file.\n\n", "Segfault in CustomData_blend_read\nOperating system: Debian Linux, Stable\nGraphics card: GTX970\n\nBroken: 3.6.0 Alpha, branch: main (modified), commit date: 2023-04-05 18:55, hash: 92c9c1d4003e, type: Release\nWorked: Unsure. Old blend I loaded and worked on for a while. Errors on open now.\n\nSegfault on load.\n\n1. Load blend, or open blender and load blend\n\n(No idea what the gvfs error is.)\n```\nFailed to open dir (No such file or directory): /run/user/6001/gvfs/\n[New Thread 0x7fffe3ae9700 (LWP 2310937)]\n...\n[New Thread 0x7fffdb9fe700 (LWP 2310945)]\nRead blend: \"/tmp/segfault.blend\"\n\nThread 1 \"blender\" received signal SIGSEGV, Segmentation fault.\n0x0000000001009af9 in CustomData_blend_read (reader=0x7fffffffd498, data=0x7fffd9c471f0, \n count=5002)\n at /opt/src/blender-git/blender/source/blender/blenkernel/intern/customdata.cc:5194\n5194 if (layer->flag & CD_FLAG_EXTERNAL) {\n(gdb) l\n5189\n5190 int i = 0;\n5191 while (i < data->totlayer) {\n5192 CustomDataLayer *layer = &data->layers[i];\n5193\n5194 if (layer->flag & CD_FLAG_EXTERNAL) {\n5195 layer->flag &= ~CD_FLAG_IN_MEMORY;\n5196 }\n5197\n5198 layer->flag &= ~CD_FLAG_NOFREE;\n(gdb)\n```\n\n", "Render will not load anything but a cube silhouette in a new untouched file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R4 Graphics ATI Technologies Inc. 4.5.14830 Core Profile Context 21.09.04 27.20.20904.1\n\nBroken: version: 3.6.2\n\nSo, when I open in a new file, new to blender and following a tutorial, I go to render the cube immediately, but instead of a gray cube with shading, it is a transparent silhouette. I have touched nothing, just installed from steam, and opened. Then that, IDK what's going on with it.\n\nIDK what to put here, since I didn't do anything.\n\n\n", "Blender Instantly Crashes When Rendering Cycles Or Clicking Wrong Setting\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nCPU: 12th Gen Intel(R) Core(TM) i7-12700KF, 3600 Mhz, 12 Core(s), 20 Logical Processor(s)\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.9.1.230821\n\nBroken: version: 3.6.2\n\nWhenever Blender attempts to render in cycles mode it exits immediately. It doesn't try for a few seconds, there's no loading, just click and instantly the process dies. This happens whether Preferences>System>Cycles Render Devices is set to \"None\", \"HIP\" with my GPU selected, or \"HIP\" with my CPU selected. Regardless of the cycles render device setting when I turn on viewport shading it works as it defaults to Eevee. However, if I try to change it to cycles, the moment I click cycles Blender crashes.\n\nThis same instant crash happens when I try to click OptiX or CUDA in Preferences>System>Cycles Render Devices instead on None or HIP.\n\n\n- Start Blender with a default project\n- Press Z then 8 to go into rendering mode\n- On the sidebar click render properties\n- Click the dropdown to change render engine\n- Click Cycles\n- Should see it crash instantly\n\nTo see the settings crash\n- Start Blender with a default project\n- Navigate to Edit>Preferences>System>Cycles Render Devices\n- Click between None, HIP, and OneAPI without issue\n- Click CUDA or OptiX and see the instant crash\n\n", "different generation of graphic card won't utilise together.\nOperating system: Windows 10\nGraphics card: Radeon R9 295X2 (secondary chip) + Radeon RX560 4GB\nAMD Ryzen 1700X\nMSI X370 Gaming Pro Carbon\n3 * 8GB DDR4-2400\n\nBroken: 2.82.7 to 2.83.3 <--- where x is from 0 to current stable version\nWorked: 2.8, 2.83.4 (partly worked, may end up sudden wattman reset)\n\nRadeon Version: 20.7.2\n\nafter the 3rd step, the render did not show anything, switching back to material viewport, the whole program was frozen. not sure if that is graphic card problem, but that way i could not even render anything. on 2.82.7, this also happened and the render kernels failed to work.\n\n\n1. open up a file of as shown\n2. set the preferences that would use OpenCL to render with R9 295X2 (and RX560)\n3. preview in Cycles\n4. unable to load the preview, switch back to material viewport.\n\n[zeta school 1.blend](zeta_school_1.blend)" ]

[ "Batch Rendering Crashes if EEVEE set in scene\nOperating system: Windows 10\nGraphics card: Any or None\n\n2,83, 2,90, 2.92\n\nEEVEE is set as renderer in the scene file.\nThe scene is send to the render farm. \nOpenGL is not available as render farm is running as background service OR blades machines do not have any GPU at all.\nBlender in Commandline Crashes.\n\n(Side Note: Cycles works fine as CUDA is available within background service)\n\n\n**Expected Behavior**\nReport an error \"EEVEE requires OpenGL. Unable to find/initialize openGL32.dll\"\n\nTo reproduce the issue, you either need some helper service that starts Blender in commandline mode (I can provide one) OR you can use any machine that does not have a GPU installed.\nCreate a new scene with EEVEE as renderer.\nTry to commandline-render the scene.\n\nCommandline that we used:\n\"C:\\renderer_exe\\blender\\win_x64\\Blender_2.90\\blender.exe\" -b \"\\\\isilonai\\woodspeople\\Boar (With fur).blend\" -o \"\\\\isilonai\\woodspeople\\Boar (With fur)\\Brawler####\" -F PNG -x 1 -s 10 -e 10 -j 1 -t 24 -a -y\n\n\nCommandline output:\nR 6| >\"C:\\RR_localdata\\renderer_exe\\blender\\win_x64\\Blender_2.92\\blender.exe\" -b \"C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\" -o \"C:\\RR_localdata\\renderout\\A\\3D\\Blender\\render\\myOut####\" -F PNG -x 1 -s 2 -e 3 -j 1 -t 24 -a -y \nR 7| Blender 2.92.0 Alpha (hash 719bea0d6d06 built 2021-01-12 23:10:47)\nR 8| Read blend: C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\nR 9| Writing: C:\\RR_localdata\\temp\\A\\cube.crash.txt\nR 10| StdErr: Warning! Using result of ChoosePixelFormat.\nR 11| StdErr: Warning! Using result of ChoosePixelFormat.\nR 12| StdErr: Warning! Using result of ChoosePixelFormat.\nR 13| StdErr: Warning! Using result of ChoosePixelFormat.\nR 14| StdErr: Warning! Using result of ChoosePixelFormat.\nR 15| StdErr: Warning! Using result of ChoosePixelFormat.\nR 16| StdErr: Warning! Using result of ChoosePixelFormat.\nR 17| StdErr: Warning! Using result of ChoosePixelFormat.\nR 18| StdErr: Warning! Using result of ChoosePixelFormat.\nR 19| StdErr: Warning! Using result of ChoosePixelFormat.\nR 20| StdErr: Warning! Using result of ChoosePixelFormat.\nR 21| StdErr: Warning! Using result of ChoosePixelFormat.\nR 22| StdErr: Warning! Using result of ChoosePixelFormat.\nR 23| StdErr: Warning! Using result of ChoosePixelFormat.\nR 24| StdErr: Win32 Error# (127): The specified procedure could not be found.\nR 25| StdErr: Error : EXCEPTION_ACCESS_VIOLATION\nR 26| StdErr: Address : 0x00007FFF8DBA1C81\nR 27| StdErr: Module : VCRUNTIME140.dll\nR 28| StdErr: Thread : 00001c94\n[Boar.crash.txt](Boar.crash.txt)\n\n\n", "Blender crashes when rendering from the command line without display or remote display\nOperating system:\n* Ubuntu 20.04 x64 with NVIDIA Card 960m\n* Ubuntu 16.04 x64 with intel grafics.\n\nHowever, i run blender from snap, so libs should be the same on both installs\n\nGraphics card:\n\nBlender 2.91.2 (hash 5be9ef417703 built 2021-01-19 16:16:34) as delivered via snap install \n\nBlender crashes when trying to render an eevee scene from the command line\nwhen either DISPLAY is not set or when trying to launch via an remote X11 connection (ssh -C -X).\n\n\nThis run is with DISPLAY set (ssh -C -X):\n```\nhcw@mediasrv:~/work/Priv/FocusRail/HW/blend$ LIBGL_DEBUG=verbose blender --background ./focusrail-pack.blend --background --render-anim\nBlender 2.91.2 (hash 5be9ef417703 built 2021-01-19 16:16:34)\nBlender 2.91.2 (hash 5be9ef417703 built 2021-01-19 16:16:34)\n/run/user/1000/gvfs/ non-existent directory\nfound bundled python: /snap/blender/65/2.91/python\nRead blend: /home/hcw/work/Priv/FocusRail/HW/blend/./focusrail-pack.blend\nInfo: Read library: '/home/hcw/work/Priv/FocusRail/HW/blend/makerbean-parts.blend', '//makerbean-parts.blend', parent '<direct>'\nInfo: Read library: '/home/hcw/work/Priv/FocusRail/HW/blend/nema-17.blend', '//nema-17.blend', parent '<direct>'\nlibGL: screen 0 does not appear to be DRI2 capable\nlibGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/swrast_dri.so\nlibGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so\nlibGL: Can't open configuration file /home/hcw/.drirc: No such file or directory.\nlibGL: Can't open configuration file /home/hcw/.drirc: No such file or directory.\nlibGL error: No matching fbConfigs or visuals found\nlibGL error: failed to load driver: swrast\nfunction is no-op\nfunction is no-op\nfunction is no-op\nWriting: /tmp/focusrail-pack.crash.txt\nSegmentation fault (core dumped)\nhcw@mediasrv:~/work/Priv/FocusRail/HW/blend$ echo $DISPLAY\nlocalhost:10.0\n\nhcw@mediasrv:~/work/Priv/FocusRail/HW/blend$ cat /tmp/focusrail-pack.crash.txt\n# Blender 2.91.2, Commit date: 2021-01-19 16:15, Hash 5be9ef417703\n\n# backtrace\n/snap/blender/65/blender(BLI_system_backtrace+0x20) [0x84bbb90]\n/snap/blender/65/blender() [0xe529bd]\n/lib/x86_64-linux-gnu/libc.so.6(+0x354c0) [0x7f533550d4c0]\n/lib/x86_64-linux-gnu/libc.so.6(+0x8e0ee) [0x7f53355660ee]\n/snap/blender/65/blender(_ZN7blender3gpu9GLBackend13platform_initEv+0x53) [0x70af813]\n/snap/blender/65/blender(GPU_backend_init+0x7a) [0x709edba]\n/snap/blender/65/blender(GPU_context_create+0x82) [0x709ef12]\n/snap/blender/65/blender(DRW_opengl_context_create+0x2f) [0x1313bcf]\n/snap/blender/65/blender(WM_init_opengl+0x19) [0x11d2129]\n/snap/blender/65/blender(DRW_render_context_enable+0x75) [0x1314575]\n/snap/blender/65/blender() [0x6b00fd9]\n/snap/blender/65/blender(RE_engine_render+0x24e) [0x6b01a1e]\n/snap/blender/65/blender() [0x6b0b461]\n/snap/blender/65/blender() [0x6b0e460]\n/snap/blender/65/blender(RE_RenderAnim+0x29c) [0x6b0ef8c]\n/snap/blender/65/blender() [0xe4f5d0]\n/snap/blender/65/blender(BLI_argsParse+0xc7) [0x841b167]\n/snap/blender/65/blender(main+0x2c4) [0xd8d164]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f53354f8840]\n/snap/blender/65/blender() [0xe4f133]\n\n# Python backtrace\nhcw@mediasrv:~/work/Priv/FocusRail/HW/blend$ \n\n\n```\n\nThis run is without display:\n\n\n```\nhcw@mediasrv:~/work/Priv/FocusRail/HW/blend$ LIBGL_DEBUG=verbose blender --background ./focusrail-pack.blend --background --render-anim\nBlender 2.91.2 (hash 5be9ef417703 built 2021-01-19 16:16:34)\nBlender 2.91.2 (hash 5be9ef417703 built 2021-01-19 16:16:34)\n/run/user/1000/gvfs/ non-existent directory\nfound bundled python: /snap/blender/65/2.91/python\nRead blend: /home/hcw/work/Priv/FocusRail/HW/blend/./focusrail-pack.blend\nInfo: Read library: '/home/hcw/work/Priv/FocusRail/HW/blend/makerbean-parts.blend', '//makerbean-parts.blend', parent '<direct>'\nInfo: Read library: '/home/hcw/work/Priv/FocusRail/HW/blend/nema-17.blend', '//nema-17.blend', parent '<direct>'\nUnable to open a display\nAborted (core dumped)\nhcw@mediasrv:~/work/Priv/FocusRail/HW/blend$ \n\n```" ]

[ "World aov output nodes dont work unless background node's colour is >= 0.0001\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.3 Release Candidate\nWorked: Unknown\n\nWorld aov output nodes dont work unless background node's colour is >= 0.0001\n\n\n1. Open attached file\n2. go to the compositor of 'scene' and render still image\n3. the custom world aov is blank\n4. go to scene.001 and render\n5. the world aov now outputs correctly\n\nBoth scene's are identical, the only difference is scene.001's world background node's colour is set to 0.0001. The custom AOV is of type Value rather than colour. This is problematic because it breaks compositor setups that check for values > 0 etc.\n\n", "Curve tool in draw mode doesn't show number of points in the stroke \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.1.0\n\nCurve tool in draw mode doesn't show number of points in the stroke while DRAWING IT\n\n- Switch to 2D template\n- Select curve option from toolbar\n- Draw a curve in viewport \n(After drawing end points of curve, point count will disappear from status bar. This doesn't happen with other methods)\n\n\n\n", "Clipped text labels intermittently missing ellipses by Float properties\nBroken: 3.4\nWorked: -\n\nThere are no ellipses by node group parameters in all editors by unhidden values \n\n[2022-09-02 16-57-07.mp4](2022-09-02_16-57-07.mp4) \n\n- Open attached file\n[missing_ellipsis_bug.blend](missing_ellipsis_bug.blend)", "Channel numbers becomes unreadable with extreme zoom\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 27.20.100.8476\n\nBroken: version: 2.91.0 Alpha\n\n\n{[F8909669](image.png), size=full}\n\n\n", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "Texture Paint: paint in image editor missing updates on certain specific conditions\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.0?\n\nIn pre-3.5 versions updates are missing in other areas.\n\nPainting in image editor missing updates when specific conditions (probably making the image editor specific size to cause this issue?) are met (see steps below).\n\n[ImagePaintMissingUpdates.mp4](ImagePaintMissingUpdates.mp4)\n\n[ImagePaintMissingUpdates.blend](ImagePaintMissingUpdates.blend)\n\n- Download the above file\n- Use Blender with maximized window in a1080p monitor\n- In Preferences > Interface, set resolution scale to 1.05\n- Open the file, make sure not to change the zoom level in image editor\n- Try painting in image editor\n", "Broken textures and shading\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nBroken textures when starting up blender and loading object textures and shading issues\n\n[Blender Texture Bug.mp4](Blender_Texture_Bug.mp4)\n\nPossible causes:\n * Not loading the parent asset blend file before the asset in another scene (opening it first seems to fix the issue in my testing) \n * 4k textures (i've heavily used 4k textures in the asset)\n * Viewport Texture size limit setting (Changed it to 2k)\n\n\n[untitled.blend](untitled.blend)\n", "Blender file browser replaces dot with underscore\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.0.0 Alpha\nWorked: Never\n\nThe renderfarm service I'm using decides to use a dot in the middle of naming the frames. It's stupid but it is what it is and I don't have control over it.\n\n\n\nTry to set the render path like this\n\nAs soon as you press enter it decides to rename like this\n\n\nBlender keeps changing the dot for an underscore but only on windows, on linux it leaves the dot alone!\n\n\nOn a **Windows** machine:\n- Invoke file open dialog\n- Input filename `test.`\nFilename will be changed to `test_`\n", "UI: Annotate Tool - Missing Layer and Color Parameters\nOperating system: Windows 10\n\nBroken: 3.5.0, 3.6.0 (2023-04-06)\n\nIn some places, layer and color parameters are missing:\n\n\n", "Drivers of sub-ID properties do not get removed along with the sub-ID\nBy \"Sub-ID\" I mean things like Modifiers, Constraints (bone & object), custom properties, shape keys, bones, VSE strips, etc. Not sure how to get a complete list of these types of things.\n\nWhen one of these things, such as a modifier, is removed, drivers on its driven properties are not removed. This makes it easy to leave behind broken drivers that now target nothing. These can be cleared up in the Driver Editor UI fairly easily, but the fact that we must do so is annoying. Experienced users end up learning that you can't just remove a modifier or constraint without removing its drivers first - Just to save you a trip to the Driver Editor.\n\nForgetfulness in this habit results in console warnings, which in a production environment trickle down from assets to shot files, and contribute to the users' sense of \"console warnings aren't important, I will ignore them\".\n\nI always thought this was a known issue but @Sergey told me it's fixable and that I should make a report. Here ya go! \n\nThis would be a really, really welcome improvement for the studio and probably the whole world.\n\n", "overlays extras option being ignored\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Beta\nWorked: (unsure, definitely 2.8 possibly 3.0)\n\nbounding box representation of particle instanced geometry (hair) where the object being instanced is set to bounding box is not being hidden from the viewport when the 'extras' option is checked. \n\n\n", "Window title shows unsaved indicator while loading\nOperating system: Linux-4.15.0-45-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: May 18 2021, hash: `1f9eb7e2c6`\n\nWhile Blender loads a file, the window title shows the unsaved indicator: `Blender* [/path/to/blend]`.\n\n- Create a .blend file which takes long to load. A simple example involves creating huge amounts of geometry with Array modifier, then applying the modifier.\n- Open the startup file (ctrl+N) so the window title is cleared (makes it easier to see what changes, but not required).\n- Open the .blend you created earlier, you will see the unsaved indicator in the title until loading finished.\n\n", "VSE: The blend and opacity settings that strips are created with does not match the default values they revert back to\nOperating system: Linux-5.4.0-80-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108\n\nBroken: version: 3.0.0 Alpha\nWorked: Unsure\n\nStrips are created by default with blend method \"Cross\" and blend opacity \"1\", however reverting to default values results in \"Replace\" and \"0\".\n\n- Open VSE\n- Add/create any strip\n- Under strip properties in sidebar, note that blend method is \"Cross\", and opacity value is \"1\"\n- Choose \"Reset to default value\" from context menu for both of these settings\n- Blend method will change to \"Replace\"\n- Opacity value will change to \"0\"", "Outliner: Sorting not working for some types in Scene display mode\nBroken: Current master\nWorked: Never\n\n\nSorting elements in the outliner only works for objects. Scenes, collections, and other types are not sorted.\n\n<img src=\"https://projects.blender.orgattachment\">", "Add Driver : Clicking the pickers (object / input variable) dont work\nBroken:2.80, 4c31bed6b46, blender2.8, 2018-11-30\n\nClicking the object picker in the `Add Driver` should enter object picking mode, but does nothing.\n\n\nBased on the default startup :\n- Select the **Cube**\n- Right click on **Location/X** and **Add a Driver**\n- Into **Object field**, click on the **picker**\n\n\n> In #58341#702152, @angavrilov wrote:\n> This happens because `ui_context_rna_button_active` within operators and poll functions invoked for the popover UI elements can't find the actual UI control in the popover, and instead returns the property UI control through the context menu of which the popover was invoked. It seems there is a big issue with context and region management in some popovers, and may require a fix in the UI core rather than a specific operator.\n> \n> Edit: Note that this issue is different from the picker attached to the Add Input Variable - that one is simply not (re-)implemented yet to work with the new way Add Driver works.\n\n\nEven though `Object` picker vs `Input Variable` picker are slightly different issues, will keep them together here since from a user perspective this is so tightly related." ]

[ "vertical axis for Drivers window\nblender-3.2.0-alpha+master.eabdcdcd44b9-windows.amd64-release\nblender-3.0.0-windows-x64\n\ndocumentation clearly shows a vertical axis for the Driver F-curves:\nintroduction.html#graph-view\n\nhowever such axis values do not exist in blender as far as I can tell inside the driver window. are they hidden somewhere? I see them in the curve editor, but not the drivers.\n\nthere is also another confusion in the documentation here:\ndrivers_editor.html\n\nwhere it has a captioned image \"The Drivers Editor\" but it's clearly the curve editor displaying keyframed animation channels and not drivers?", "Driver Editor UI - Y-axis numbers missing\nOperating system: Windows 10\n\nBroken: version: 3.0.0, 3.0.1\nWorked: 2.93.8\nCaused by b3431a8846\n\nThe Driver Editor is currently missing the Y-axis unit display that existed before the UI changes in 3.0.0.\n\nOpen the driver editor.\n\n\n" ]

[ "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "2.8: Python API: Changing area type on frame change crashes Blender\nOperating system: Windows 10\nGraphics card: Quadro P4200/PCIe/SSE2\n\nBroken: 2.81a (also crashes in 2.79 and 2.80)\n\nI am attempting to sample the individual frames of an image on frame change, using a solution similar to the one described here: 5. I cannot seem to set the viewer area, however, from this context, as `bpy.context.screen` is `None`, and `bpy.context.window_manager.windows- [x].screen` seems to crash Blender in some situations.\n\nFrom the default startup file, run the following basic code:\n\n```\nimport bpy\n\ndef on_frame_change(scn):\n bpy.context.window_manager.windows[0].screen.areas[0].type = \"IMAGE_EDITOR\"\n\nbpy.app.handlers.frame_change_pre.append(on_frame_change)\n```\n\nRun the `Render Animation` operator to crash Blender.\n\nNote: This code runs fine when playing the animation in the 3D Viewport. It seems that this bug relates to the render context only.", "Blender becomes unstable/crashes after using \"Reload Scripts\" if using any \"ShaderNodeCustomGroup\" nodes.\nOperating system: Windows 10\nGraphics card: NVIDIA\n\nBroken: 2.81\n\nIf you manipulate a \"ShaderNodeCustomGroup\" node after having used the \"Reload Scripts\" operator (F8) Blender will become unstable.\n\nAttached is a small addon that implements a minimal custom node group.\n1. Enable the addon and switch to the shader editor.\n2. Create the custom node (Add->Test Category->TestNodeCustomGroup)\n3. Trigger 'Reload Scripts' (F8 key).\n4. Adjust the color input of the custom node.\n5. Repeat steps 3/4 until you crash (usually crashes on first or second try for me)\n[node_custom_test.py](node_custom_test.py)", "Crush while baking a cloth simulation\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.2\n\nI was performing the baking of a cloth simulation. During the initial and subsequent baking attempts, everything worked fine. However, when I tried to re-bake the simulation after moving the cursor in the timeline, the program crashes. I tries to bake that cloth in previous versions. It didn't work as well\n\nTo trigger the crash, you simply need to move the cursor in the timeline and then initiate the baking process.\n\nUnfortunately, i cannot add the file (size is 200mb and i can't make it smaller ), so than i added the crash txt file and a link to the file on google drive\nview?usp=sharing\nThank you!\n\n", "Error baking particles in OSX\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX TITAN X OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.135\n\nBroken: version: 2.83.1\n\nI have two particle emisor and when I try to bake it crash.\nI try it in Linux and work perfectly!\n[TEST_ERROR.crash.txt](TEST_ERROR.crash.txt)\n\n[TEST_ERROR1.blend](TEST_ERROR1.blend)\n\n- Open file\n- Bake particles\n\n", "Crash with mantaflow\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nBaking simulation causes crash\n\n[splash.blend](splash.blend)\n\nOpen file and bake liquid\n", "Crash when delete linked object in scenes outliner\nOperating system: Windows 10\n\nBroken: 3.6, 3.5, 3.3 LTS, 2.93 LTS\nBroken: 2.91.0\nWorked: 2.90.1\n\nCaused by b0741e1dcbc5e4549e95745b1f1b501f8cd33add\n\nBlender is crash when delete linked object in scenes outliner\n\n1. Open start scene\n2. Create new scene \"Scene.001\"\n3. Click on Cube, Ctrl+L, Link objects to scene \"Scene.001\"\n4. In Outliner switch to \"Scenes\"\n5. Select \"Cube\" object in Scenes Outliner in \"Scene.001\"\n6. Move cursor to Outliner, press key \"X\" or \"Delete\"\n7. Blender is crashing\n\n", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "Crashes when trying to mirror particles\nOperating system: Windows 11\nGraphics card: Nvidia RTX 2060\n\nBroken: 3.6.1\n\nWhen I try to mirror hair particles Blender crashes. I've tried it multiple times and it happens every single time. Ive tried applying the mirror modifier I have on the character but it still crashes.\n\nI have a retopologized character. I make a particle system for eyebrows. I try to mirror the eyebrows by selecting all the particles, going to particles and selecting mirror and blender crashes.\n\n", "Blender Crashes on Render (Save As), then refuses to start\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1\nWorked: N/A\n\nFirst observed with the attached file. I tried to save a png image render from it; when I clicked \"Save As,\" Blender crashed and then... wouldn't open. It seemed to initiate startup, because the little black window that usually notified me that it was reading my userprefs.py file would blink into existence just long enough for me to register what it said, then close itself and act like I hadn't clicked it.\n\nRestarting my computer fixes the problem temporarily, until the next crash. The crashes are inconsistent, but seem to happen only when I hit main menu items like Open or Save. This includes previous versions, apparently, as I still had 3.5 installed and it does the same quick blink.\n\nThe only thing I could think of was that that Read line in the black window referred to finding the userprefs file in C:\\ when I installed everything into M:\\, but I tried copying the required path over to C:\\ with no effect and also it gives me that same message when it's working and starts up fine.\n\nI also tried repairing the 3.6.1 install, and uninstalling/reinstalling, to no effect.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Crash when modifing materials after using BMesh in Depsgraph-Pre event\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\n\nBroken: version: 3.0.0\nBroken: version: 3.0.1 Release Candidate\nBroken: version: 3.1.0 Alpha\n\nI wrote a script with a function that copies a mesh via BMesh to another object and then changes it's materials. When I want to export the scene as an alembic, Blender crashes when the function gets called via the Depsgraph_Pre event. Depsgraph_Post and Frame_changed_Pre & Post all work fine.\n\n\n- Open the attached Depsgraph_Pre_Crash.blend file in Blender\n- Run the script\n- (Optional) Scroll on the timeline between frames 1 & 2 to check that the script works\n- Set the active frame on the timeline to 1\n- Export as alembic with default settings\n- Blender crashes\n[Depsgraph_Pre_Crash.blend](Depsgraph_Pre_Crash.blend)\n\n[Depsgraph_Pre_Crash.crash.txt](Depsgraph_Pre_Crash.crash.txt)\n\nHere is the callback registered in `depsgraph_update_pre`:\n```lines=10,lang=python\ndef updateFrame(scene): \n```\n emptyObject = bpy.data.objects[\"EmptyObj\"]\n firstOBJ = bpy.data.objects[\"Frame1\"]\n secondOBJ = bpy.data.objects[\"Frame2\"]\n```\n\n```\n if(scene.frame_current == 1):\n bmNew = bmesh.new()\n bmNew.from_mesh(firstOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n```\n\n #Doing anything with the materials crashes blender on alembic export\n```\n emptyObject.data.materials.clear()\n```\n\n```\n if(scene.frame_current == 2):\n bmNew = bmesh.new()\n bmNew.from_mesh(secondOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n \n emptyObject.data.materials.clear()\n```\n", "Crash choice asset library\nOperating system: Win 10\nGraphics card: RX460 2gb\n\nBroken: (3.2)\nWorked: (3.0)\n\n[Tests.zip](Tests.zip)\n\n- Extract archive and add `...\\Tests\\Test Asset\\` path to asset libraries\n- Open Asset library blend file\n- Open New file\n- Change any editor to Asset Browser\n# List contents of `Test Asset` library\n\nIt should crash.\nSometimes, omitting step 2 would prevent crash, but no assets would be shown.\nAlso omitting `tests` folder somehow prevented the crash, \n\nCrash log:\n[P3143: (An Untitled Masterwork)](P3143.txt)\n```\n# Blender 3.4.0, Commit date: 2022-08-14 18:40, Hash 659b63751d63\nbpy.context.space_data.params.asset_library_ref = 'Test Asset' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : UNKNOWN EXCEPTION\nException Address : 0x00007FFF3F66D759\nException Module : KERNELBASE.dll\nException Flags : 0x00000001\nException Parameters : 0x4\n\tParameters- [x] : 0x0000000019930520\n\tParameters- [x] : 0x000000FB7C5FD460\n\tParameters- [x] : 0x00007FF678278398\n\tParameters- [x] : 0x00007FF66CA80000\n\n\nStack trace:\nKERNELBASE.dll :0x00007FFF3F66D6F0 RaiseException\nVCRUNTIME140.dll :0x00007FFF283E63F0 CxxThrowException\nblender.exe :0x00007FF672BC42D0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC36C0 nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_string<char,std::char_traits<char\nblender.exe :0x00007FF672BC82B0 blender::io::serialize::JsonFormatter::serialize\nblender.exe :0x00007FF66E27B970 blender::ed::asset::index::AssetIndexFile::write_contents\nblender.exe :0x00007FF66E277D40 blender::ed::asset::index::update_index\nblender.exe :0x00007FF66E653B90 filelist_readjob_list_lib\nblender.exe :0x00007FF66E654370 filelist_readjob_recursive_dir_add_items\nblender.exe :0x00007FF66E653710 filelist_readjob_asset_library\nblender.exe :0x00007FF66DB341A0 do_job_thread\nblender.exe :0x00007FF672E5A810 _ptw32_threadStart\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThreads:\nThread : 00000448\nntdll.dll :0x00007FFF41D2C620 ZwDelayExecution\nblender.exe :0x00007FF672B3A220 BLI_thread_is_main\n\n\nThread : 000069ac\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003130\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069cc\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000054bc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000026c0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008788\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000aa4c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000608c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009c7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008d78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029c4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009918\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000162c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001478\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000040b4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000036d0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003468\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007444\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005208\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000059e4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a018\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000085a8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b1ac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000921c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005544\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad94\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067e0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000401c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b360\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008b38\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005884\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003334\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008c60\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a2e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nnvoglv64.dll :0x00007FFE819D057C Symbols not available\n\n\nThread : 00009be0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFF3F690C30 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003f9c\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007978\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ace0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ada4\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFF3012457B Symbols not available\n\n\nThread : 00009dbc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005f9c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009dac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000405c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000834c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000099e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00006284\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005ec8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a8fc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003240\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00000a10\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000082dc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000196c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004374\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007dec\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004294\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000559c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a90\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004cc8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000055f8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069a4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005c40\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001a80\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004308\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000081c8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b0d4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004bc0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009d28\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008010\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF66CA80000 3.4.0.0 blender.exe C:\\Users\\John\\Desktop\\blender-3.4.0-alpha+master.659b63751d63-windows.amd64-release\\blender.pdb \n0x00007FFF41C90000 10.0.19041.662 ntdll.dll \n0x00007FFF40620000 10.0.19041.662 KERNEL32.DLL \n0x00007FFF3F640000 10.0.19041.662 KERNELBASE.dll \n0x00007FFF40C70000 10.0.19041.546 WS2_32.dll \n0x00007FFF41310000 10.0.19041.662 RPCRT4.dll \n0x00007FFF41170000 10.0.19041.685 USER32.dll \n0x00007FFF1D640000 tbb.dll \n0x00007FFF3FCC0000 10.0.19041.662 win32u.dll \n0x00007FFF41940000 10.0.19041.685 GDI32.dll \n0x00007FFF1D600000 tbbmalloc.dll \n0x00007FFF3FAB0000 10.0.19041.685 gdi32full.dll \n0x00007FFF3FA10000 10.0.19041.546 msvcp_win.dll \n0x00007FFF3F910000 10.0.19041.546 ucrtbase.dll \n0x00007FFF417D0000 10.0.19041.610 ADVAPI32.dll \n0x00007FFF406E0000 7.0.19041.546 msvcrt.dll \n0x00007FFF41980000 10.0.19041.662 sechost.dll \n0x00007FFF3FED0000 10.0.19041.662 SHELL32.dll \n0x00007FFF283E0000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFF3AE70000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFF40F00000 10.0.19041.546 SHLWAPI.dll \n0x00007FFEC90D0000 14.29.30139.0 MSVCP140.dll \n0x00007FFF3FC70000 10.0.19041.546 CFGMGR32.dll \n0x00007FFF36DA0000 10.0.19041.488 dbghelp.dll \n0x00007FFF3FBC0000 10.0.19041.662 bcrypt.dll \n0x00007FFF40CE0000 10.0.19041.546 ole32.dll \n0x00007FFF41470000 10.0.19041.662 combase.dll \n0x00007FFEC8180000 10.0.19041.546 OPENGL32.dll \n0x00007FFF41440000 10.0.19041.546 PSAPI.DLL \n0x00007FFF41A20000 10.0.19041.662 shcore.dll \n0x00007FFF3FEA0000 10.0.19041.546 IMM32.dll \n0x00007FFEB74B0000 9.0.0.0 openvdb.dll \n0x00007FFEC5BE0000 59.16.100.0 avformat-59.dll \n0x00007FFEB4FB0000 59.18.100.0 avcodec-59.dll \n0x00007FFF1D5D0000 59.4.100.0 avdevice-59.dll \n0x00007FFF40FC0000 10.0.19041.546 OLEAUT32.dll \n0x00007FFEC9030000 6.4.100.0 swscale-6.dll \n0x00007FFEC5A00000 57.17.100.0 avutil-57.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFEC5190000 1.21.1.0 OpenAL32.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFEC29E0000 2.0.20.0 SDL2.dll \n0x00007FFF39630000 libgmpxx.dll \n0x00007FFEC0D70000 3.10.2150.1013 python310.dll \n0x00007FFF40780000 10.0.19041.546 SETUPAPI.dll \n0x00007FFF300E0000 tbbmalloc_proxy.dll \n0x00007FFF31280000 6.10.19041.488 COMCTL32.dll \n0x00007FFF1C490000 10.0.19041.1 AVIFIL32.dll \n0x00007FFF39120000 10.0.19041.546 VERSION.dll \n0x00007FFF3D210000 10.0.19041.546 dwmapi.dll \n0x00007FFF1C460000 10.0.19041.546 GLU32.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFF27EE0000 10.0.19041.546 Secur32.dll \n0x00007FFECB6B0000 4.3.100.0 swresample-4.dll \n0x00007FFECBF00000 10.0.19041.1 AVICAP32.dll \n0x00007FFF2EBF0000 10.0.19041.546 WINMM.dll \n0x00007FFF20660000 10.0.19041.1 MSACM32.dll \n0x00007FFECB5D0000 10.0.19041.1 MSVFW32.dll \n0x00007FFF24F20000 10.0.19041.1 winmmbase.dll \n0x00007FFF3F280000 10.0.19041.662 SSPICLI.DLL \n0x00007FFF3D240000 10.0.19041.546 kernel.appcore.dll \n0x00007FFF3D520000 10.0.19041.662 windows.storage.dll \n0x00007FFF3EE40000 10.0.19041.662 Wldp.dll \n0x00007FFF3CE80000 10.0.19041.610 uxtheme.dll \n0x0000022043090000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFF3F300000 10.0.19041.546 profapi.dll \n0x00007FFF41880000 2001.12.10941.16384 clbcatq.dll \n0x00007FFF38BE0000 10.0.19041.546 MMDevApi.dll \n0x00007FFF3F180000 10.0.19041.546 DEVOBJ.dll \n0x00007FFF38EF0000 10.0.19041.662 AUDIOSES.DLL \n0x00007FFF3E980000 10.0.19041.546 powrprof.dll \n0x00007FFF3E840000 UMPDC.dll \n0x00007FFF41AD0000 10.0.19041.662 MSCTF.dll \n0x00007FFF39850000 10.0.19041.662 AppXDeploymentClient.dll \n0x00007FFE80E80000 31.0.15.1640 nvoglv64.dll \n0x00007FFF3AE30000 10.0.19041.546 \n```\n\n\n - The conditions have been changed, but the error is still present. -----------------------------------------------------------", "Crash when scrubbing the timeline when using the line art modifier\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.0\nWorked: 3.4.1\n\nWhen scrubbing the timeline, blender will crash. This happens frequently when I have a project of sufficient complexity that uses the line art modifier. The provided blend file has been simplified as much as possible while still reproducing the crashing behavior.\n\n1. Open line_art_crash.blend\n2. Scrub the timeline. Jumping between frames makes it less likely to crash, but holding onto the playhead and slowly moving should have it crash in a few seconds.\n\n", "Support Scenes Overrides\nCurrently Scenes liboverrides are not really working, changes to its master collection will be lost, resync of scene itself is not possible when the override is the active scene, etc.\n\nSee e.g. #89963 (crash when library override is applied to an object)", "Blender 3.2 crashes on opening a specific file\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: 3.2.0\nWorked: unknown\n\n**problem**\nBlender immediately crashes when opening the file steam_engine.blend\n\nThe latest object I was working on, was UV-unwrapping a mesh which I think I called 'greenthingy' or something like that. There was no crash prior to re-opening the file. I attach the file (hope it's not too big and apologies for the mess...). crash report and system_info.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[steam_engine.crash.txt](steam_engine.crash.txt)\n\n**Steps for others to reproduce the error**\n[steam_engine.blend](steam_engine.blend)\n[#99105.blend](T99105.blend)\n\nAfter opening `steam_engine.blend` file Blender crashes. \n`#99105.blend` is same file as `steam_engine.blend`, but material preview panel has beeen collapsed. This file does not crash. Interestingly it does not crash even when panel is re-opened. Tested with GPU and CPU\n" ]

[ "crash when adding non-mesh object\nOperating system: Linux-4.15.0-54-generic-x86_64-with-LinuxMint-19.1-tessa 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.67\n\n\nBroken: version: 2.80 (sub 74)\nWorked: run as normal, reset to factory settings do not help either\n\n\nRight after adding text object to the scene, sudden crash. Repeated several times, system up-to date, after restart.\n\n1. Remove the cube.\n2. Shift+A, add Text\n3. Crash.\n\nI've included log generated by running blender as:\n./blender --factory-startup --debug-all >& crash.log\nand the file created by blender in /tmp/blender.crash.txt.\n[report.zip](report.zip)\n" ]

[ "Bone drivers do not copy when duplicated\nMac OSX 10.9.5 and NVIDIA GeForce GTX 470\n\nBroken: 2.77 (sub 3)\nWorked: ?\n\nIf a bone has any driver (on constraint or property) and it is duplicated (shift D in edit mode or \"symmetrize\") the drivers are not copied.\n\nBone constraints, however, copy perfectly and also try to find the correct .L or .R target if applicable.\nThis would save a lot of time if the drivers worked in the same way.\n", "NURBS: Repeat for Extrude doesn't repeat extrusion, selects all points\nBroken: 2.92\nWorked: ???\n\n\nAttempting to repeat (shift+r) extrusion in NURBS edit mode yields no result. Subsequent attempt results in all points being selected.\n\n\n1) Add a Surface -> NURBS curve\n2) In edit mode, select a point and extrude\n3) Attempt to repeat with shift+r (nothing happens)\n4) Attempt to repeat again (everything becomes selected)", "Add option to re-use or duplicate data for the Current File asset library\nAgreed on this alternative to [D12752: Asset Browser: Hide Import Types menu for \"Current File\" asset library](D12752). Currently dragging in data from the *Current File* asset library always reuses the existing ID. The option to duplicate the data could be quite useful and make it explicit what dragging in the asset will do.", "Colection instances can't render if duplicated while instanced on a mesh with array\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.1\n\ncol instances disapear from render view if duplicated when instanced on an array\n\nmake a plane, add aray modifier. \nput anythng in a collection, instance it \nput the instance as child of the aray, toggle face instances on.\nduplicate the col instance: the previous one(s) will disapear from render.\n\nin this blend file, just turn render view and you'll see only the lastest col instance renders.\n\n", "Quad View Exiting Behavior\nUsers coming from other software expect Quad View to behave a certain way. Since d71db08f6d, when exiting Quad View we always toggle to the *User Perspective* (top right) view, rather than the one the mouse currently hovers. That differs from what users probably expect (see #43523, #42462, #42368, #43452, #69717).\nIt should not be hard to get the (presumably) expected behavior to work again while addressing the reasons it was removed.\n\nQuick proposal:\n* Maximize the hovered view when exiting Quad View\n* Keep rotation of that view locked if it wasn't the *User Perspective* one\n* Keep the view transform of the *User Perspective* stored so when going back to Quad View, it shows that in the top right.\n\nFor more details, see d71db08f6d.", "Inconsistency in the behavior of 'Jump to next/previous keyframe' operator\nOperating system: Linux-5.4.0-124-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.3.0 Beta, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: as far as I know, none.\n\nWhen calling the 'Jump to next/previous keyframe' operator, there are inconsistency of behavior depending whether the active object is a Grease Pencil one or not.\nFor standard keyframes, it jumps to next keyframe if the object is active, regardless of if the object or any of its channels are selected.\nFor grease pencil layers keyframes, it jumps to next keyframe only if the layer channel is selected.\n\nReproduce the bug :\n - Open a new blender file,\n - Add one grease pencil object with two keyframes,\n - Add one 3D mesh (for example) with two keyframes (at different frames than the grease pencil ones),\n - Try to jump to next or previous keyframes, standard shortcut : up/down arrow in the viewport.\n\n[issue_jump_to_next_keyframe.mp4](issue_jump_to_next_keyframe.mp4)\n\n", "Redo panel overlaps part of the interface\nIn the image editor, the redo panel covers part of the pixel values. \nWould be nice if such panel could be dismissed, or if it would take into account the possible presence of the pixel value subheader.\n\n[open_image_overlay.mov](open_image_overlay.mov)", "When \"orbit around selection\" is enabled, the camera orbits around world origin instead of selected object's origin while nothing is selected in edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.6.0\n\nWhen \"orbit around selection\" is enabled, the camera will orbit around world origin instead of selected object's origin in edit mode while no verts, edges, or faces are selected.\n\nStep 1: Go to Edit>Preferences>Navigation> and then enable \"Orbit Around Selection\"\nStep 2: Add a cube to the scene and move it in \"Object Mode\" away from the world center\nStep 3: Enter \"Edit Mode\" and deselect everything, then try moving the viewport camera.\n\nIntuitively what you'd think would happen in this situation is the camera should orbit around the origin point of the selected object you're currently editing, but instead what happens is the camera orbits around the 0,0,0 point of the scene. Which feels really odd, like blender is just switching to a default behavior or something?\n\n", "File->Open Recent behaves different from Edit Override Library on Linked Object Materials\nOperating system: Windows 10\nGraphics card: AMD Radeon & NVidia 1060Ti\n\nBroken: 3.6.2\nWorked: Unknown\n\nWhen using File->Open Recent to change blend files, the overridden materials on a linked object are getting broken/changed. When using Edit Override Library on the linked object, the materials remain consistent.\nI am seeing a behaviour difference that breaks the material order when using File->Open Recent versus Edit Override Library. When using File->Open Recent it is changing the order of the materials destructively. This is related to linked objects and overriding their materials.\n\nDefault startup, 2 files needed.\nWhen using File->Open Recent the steps are:\n\n1. Create an object that will be linked. In this case, default cube\n2. Color it with 3 materials (Red, Blue, Green)\n3. Create a new blend file\n4. Link in the cube from step 1\n5. Make it a library override (Object->Library Overrides->Make)\n6. We are going to change material 3\n7. Select Material 3 change to Object Data\n8. Select the default material\n9. Change the color\n10. Save the file\n11. File->Open Recent->(File from step 1)\n12. File->Open Recent->(File from step 10)\n13. Notice that Material 1 and Material 3 are now the same materials\n\nWhen using Edit Override Library the steps are:\n\n1. Create an object that will be linked. In this case, default cube\n2. Color it with 3 materials (Red, Blue, Green)\n3. Create a new blend file\n4. Link in the cube from step 1\n5. Make it a library override (Object->Library Overrides->Make)\n6. We are going to change material 3\n7. Select Material 3 change to Object Data\n8. Select the default material\n9. Change the color\n10. Save the file\n11. Item->Edit Linked Library\n12. Item->Return to Original\n13. Notice that the Materials are in the order and color from step 7, no change\n\nThis requires several files as the initial set up gets broken. Easiest to follow the steps.\nFiles are included, they are:\n\nLinkedObjectMaterials.blend -> This is the file with the object that will be linked into the other files\nOverrideTest.blend -> File has a link to LinkedObjectMaterials.blend and it has a changed material that was set up and tested using EditOverride Method and the materials are OK\nFileOpenRecent.blent -> File has a link to LinkedObjectMaterials.blend and the 3rd material was changed and now both the first and third materials are the same.\n\nAsk if any clarifications are needed. It took me a while to narrow it down to this case.\n\n", "particle instancer modifier 20 years BUG \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0\n\n\n\nlook at particle instancer rotation of some parts. you can`t rotate this particles and can`t fix\n\n\n", "Inconsistent naming for modes in the undo history menu\nBroken: 3.4 alpha\n\nIn the undo history panel, the \"Object mode\" entry is registered with the name of previous modes. Switch from sculpt mode to Object mode will create an undo step with \"Sculpt Mode\" name\n\nAs for the other modes entries, they have no naming standard. Some entries have \"Toggle\" written before, some have \"Toggle\" after, some don't have \"Toggle\". Also they all have \"Mode\" written except for texture paint. \nThe entries are as follows:\n\n\"Texture Paint Toggle\"\n\"Weight Paint Mode\"\n\"Vertex Paint Mode\"\n\"Toggle Edit Mode\"\n\"Sculpt Mode\"\n\nBased on the default startup;\nChange modes; \nCheck \"Edit -> Undo History\" menu.\n", "Transfer shape key is only working for meshes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: Never\n\nTransfering shape keys is option in panel menu, but it only works for meshes. This is not mentioned in documentation and only evident after running the operator.\n\n\nDuplicate object in provided file and try to transfer shape keys.\n", "Asset Browser: F2 renames active object instead of the selected asset\nOperating system: Linux-6.5.3-gentoo-r1-x86_64-AMD_Ryzen_9_5950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.104.05\n\nBroken: version: 4.0.0 Alpha\n\n\nSpoke about this with @JulianEisel , it's not exactly a bug but I have his permission to report this regardless.\n\n- make some datablock an asset\n- go to asset browser and select it\n- press `F2`\n\n", " Convert to Grease Pencil overwrites Name\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro M2000M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.06\n\nBroken: version: 3.0.0 Alpha\nWorked: ? Was broken in 2.92 and 2.93\n\nUsing the Convert to Grease Pencil command on a curve, mesh, or text object overwrites the object name with GPencil \n\nSteps to reproduce: \n\n - Open up default blend file\n - Select default cube\n - Object>Convert>Grease Pencil\n - Observe the name change in the outliner\n # Have some coffee and ponder how to fix it \n\nThanks for all of your great work and this great program!\n", "Breaking change? Curve point tilt default orientation rotated by 90°\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\nWorked: 2.80\n\nThe default orientation (0°) of curve points has changed by 90°. If the curve is used for another object's curve modifier, the result between Blender 2.80 is different to newer versions (reproduced with 2.81...3.6). This is a change that I did not find listed in the release notes, so this is either a bug or by design. In any case, it's a breaking change.\n\n2.80 vs 3.6:\n\n\n\n1. Open the attached project in Blender 2.80 and in 3.6\n2. If you compare the two, you see that the normal orientation is different, consequently the result of the curve modifier affecting the mesh is different.\n\nAfter migrating a bigger project this causes several issues that would need to be fixed. Or Blender needs to be fixed.\nThis is an old issue, so I hope it's not a duplicate. Didn't find it.\nThank you.\n\n" ]

[ "Undoing 'create transformation orientation' makes selected transform orientation blank.\nLinux 64bit\n\nBroken: 2.72b, 2.71 (and lower?)\n\n\nCreating custom transformation orientation can be undone, but doing so will set transformation orientation dropdown in 3D view header to blank value.\n\n\n1. Create new file\n2. Run 'create transformation orientation' operator (ctrl+alt+space in default keymap): transformation orientation dropdown in 3D view header should change to show the name of newly created orientation\n3. Undo (ctrl+z): transformation orientation dropdown becomes blank.\n" ]

[ "Reflection of smoke on object surface has white box surrounding \nOperating system: win10\nGraphics card: GTX TITAN X\n\nBroken: (2.82, 2.83.10, 2.9, 2.91)\nWorked: (none)\n\nReflection of smoke on object surface has white box surrounding when a back light is added.\n\nLooks fine with front light only\n\n\n**With back light added:**\n2.83.10: Domain Empty Space = 0\n\n\n2.83.10: Domain Empty Spcace = 0.000001\n\n\n2.91: Domain Empty Spcace = 0\n\n\n2.91: Domain Empty Spcace = 0.000001\n\n\nSet shot with back light highlighted\n\n\nbake domain and render at around frame 200+ (when smoke touches the black object)\n\n[TEST.blend](TEST.blend)", "Add modifier error message for attribute name clashes\nIf user has a UV and a vertex color groups with the same name things behave in non predictable ways.\n\nThe nodes modifier should check for this and add an error message when this happens.", "Geometry Nodes: Going back to frame before simulation cache returns no geometry if frame is out of scene frame range\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 4.0.0 Alpha\n\nOut of scene frame range:\n\n\nInside scene frame range:\n\n\n- Add geonodes modifier\n- add simulation zone\n- run simulation to build up the cache\n- Go to frame 0\n\n", "Grease pencil over geometry occlussion problems\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.5\nBroken: version: 3.0.0 Alpha\n\nGP lines get incorrect occlussion in the render while looking fine in the viewport\n\nThe problem displays differently in the following 2 scenarios:\n\nThis file has a grease pencil stroke close over (but not really touching at all) a piece of geometry\n[GP Aliasing.blend](GP_Aliasing.blend)\nViewport Rendering\n\nRender\n*The line looks jagged in the render*\n\n\nThis file has a grease pencil drawing far behind a piece of geometry\n[Occlussion.blend](Occlussion.blend)\nViewport\n\nRender\n*The drawing that should be occluded is completely visible*\n\n", "Curves sculpting collision with surface.\n", "node editor: Texture preview refresh with cursor selection\nOperating system: 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux\nGraphics card: RTX 2070\n\nBroken: Blender 2.93.0, Commit date: 2021-02-17 06:07, Hash 17dddc941714\n\nwhen selecting things in geonodes space the texture preview refresh anomaly.\n\n- Open blender default file.\n- Open the geometry nodes editor\n- Add a geometry node group\n- Open the texture tab ( property panel )\n- Add a texture for the current brush\n- Change to cloud texture\n- Try to select things with cursor select ( Key : C ) in the geometry nodes area.\n- It will refresh the texture preview\n\n[untitled.blend](untitled.blend)\n[Kazam_screencast_00003.mp4](Kazam_screencast_00003.mp4)", "Denoising - artefacts when transparent background is enabled\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBroken: version: 2.81 (sub 4)\n\nWhen \"Transparent\" is enabled in \"Film\" tab, denoising (old blender denoiser) is producing dark pixels. It seems to happen only with an environment map. When \"World\" is set to flat color, problem disappears. Here's an example (zoomed in):\n\n\n\nThere seem to be holes in \"Denoising Depth\" pass which seem to coincide with the bad pixels.\n\n\n\nWhen you turn transparency off, those artefacts disappear:\n\n\n\nDenoising Depth also looks a lot cleaner, although there are still couple of bad pixels:\n\n\n\nHere's a file with the example above. It has env map packed in.\n\n[denoiser_artefacts_bug.blend](denoiser_artefacts_bug.blend)", "Python API: Geometry Nodes object and collection inputs appear disabled in custom panel\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nGeometry Nodes object and collection inputs appear disabled when they are shown in a custom panel. Other types of properties do work. The properties can be accessed as follows: layout.prop(modifier, '[\"Input_2\"]').\n\nBased on the attached file:\n\n1. Run the script in the text editor to create a panel into the sidebar into a category called \"Geometry Nodes\"\n2. See that the panel shows the object and collection inputs of the Geometry Nodes modifier of the active cube as disabled\n\n[geometry_nodes_object_and_collection_inputs_disabled_bug.blend](geometry_nodes_object_and_collection_inputs_disabled_bug.blend)", "Regression: Child hair particles set to \"Interpolated\" causes jittering when the based vertex changes position\nOperating system:win10\nGraphics card:RTX3060ti\n\nBroken: c8c6f62cf3a3,fca8df9415\nBroken: 3.5\nWorked: 3.4\n\nCaused by d20f9923224d2637374dd4390ae84c5041e3f9d3\n\nChild hair particles set to \"Interpolated\" causes jittering when the based vertex changes position\nThis problem seems to have been solved before,in #63534 and #56408\n\nOpen the file and render animation\n\n", "Geometry Nodes: Rendered glitch with Image Texture and Scene Time\nOperating system: Linux-5.15.0-76-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.0\nWorked: Never\n\n**Short description**\nGeometry nodes that use single images or image sequences are rendered inconsistently but usually look normal in the viewport.\nHigh-res images seem to be more unstable.\nHaving a connected/unconnected scene time node in the geo node group while using an image sequence with any number of frames also makes the rendered image/animation more unstable.\n\n|Expected render|Occasional render glitch|\n|--------------------------|--------------------------------------|\n|| |\n\n\n**Reproduction steps**\nThis is the most unstable setup:\n\n1. Create new project\n2. in the image editor window add a new image with resolution of around 1080x1080 pixels and set the source an image sequence \n3. add geometry nodes modifier to the default cube\n4. follow this node setup; in the image texture node use the created image sequence \n5. Render animation\n6. some of the rendered images will be glitched\n\nI've also tested this approach with face extrusion or instance selection instead of deleting faces. The resulting renders were also glitched. \n\nInside of this zip file is a blender project with a similar setup along with some sample images:\n[geo node groups that use images are rendered inconsistently.zip](attachment)\n\nThis reddit post seems to be describing a similar issue:\ngeometry_nodes_rendering_glitch_info_in_comments/\n\nThe workaround with disabling geo nodes modifier in the viewport mentioned there seems to be working in a simple setup. In the above project from the .zip file it is less effective.\n\n", "Join Geometry Node makes vertices unselectable + disappear on cage preview\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\n\nUsing Join Geometry makes the vertices unselectable when Geometry Nodes is being visualized in Edit Mode.\n\nWhen using geometry nodes to act as solidify I need to add a Join Geometry at the end. This makes my vertices both disappear and they are unselectable. This happens when the \"On Cage\" overlay is activated. It properly displays the wireframe but the vertices are gone and unselectable. Since it appears and works normally when I disable On Cage I figure this must be a bug.\n\n[Blender 2022-09-08 12-37-19.mp4](Blender_2022-09-08_12-37-19.mp4)\n[JoinGeometryBug3.3.blend](JoinGeometryBug3.3.blend)\n\n\n\n", "Geometry Nodes Mesh Boolean unexpected difference result\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 83\n\nBroken: version: 3.5.0 Alpha\nWorked: none\n\nGeometry Nodes Mesh Boolean Difference does not work as expected.\nNode setup:\n\n\nUnexpected boolean difference:\n\n\n- Open the attached .blend file\n- Press G to move the selected Cube.001 and the small cubes will flicker.\n# At certain positions of Cube.001 some of the small cubes will disappear when they should not.\nThanks!\n[test06.blend](test06.blend)\n", "Grease Pencil Blur makes a tight white line beteween to diferent GP Objects.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.6.0 Alpha\n\nWhen I use Blur effects on a GP object, it makes a tight white line between to different GP Objects. But, depends on which angle you look at, and this bug disappears.\n\n\njust added a blur effect on a grease pencil on render preview mod.\n\n", "Vertex/Edge Slide stuttering with modifier.\nOperating system: Windows 11\nGraphics card: RTX 3070\nCPU: Ryzen 5900x\n\nBroken: 2.83 and all other.\nWorked: 2.79b\n\nVertex/Edge Slide freezes a lot with subdiv modifier in a relatively simple object.\n\n| With `Use Limit Surface` | Without `Use Limit Surface` |\n| -- | -- |\n| https://projects.blender.orgattachment | https://projects.blender.orgattachment |\n\n1. Import attached fbx.\n2. Add subdivision modifier set to 1 subdivision.\n3. Select the loop in the middle.\n4. Edge slide.\n\n", "Metaball particles are handled inconsistently in Geometry Nodes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.7.1.220725\n\nBroken: version: 3.4.0 Alpha\nWorked: (n/a)\n\nMetaball rendered via particles are handled inconsistently in Geometry Nodes. It seems only mesh related nodes are generally working well with them.\n\nI wasn't sure about reporting this as a bug, because I assume that compatibility with the particle system is probably not intended use case. I guess ability to access metaball particles at all is an unintended bonus from eaa87101cd5a? I'd argue that if this can be easily \"fixed\" it will open up some interesting use cases before actual simulation/physics nodes arrive, but this is a borderline feature request and I guess developers will decide if this is worth to look at at this point.\n\n\n[MetaballParticles.blend](MetaballParticles.blend)\n[MetaballParticles.mp4](MetaballParticles.mp4)" ]

[ "Checker texture/white noise distortion with eevee \nOperating system: Linux-4.15.0-70-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.31\n\nBroken: version: 2.81 (sub 16)\nWorked: Never seen this problem with my older gfx card GTX 660 (driver 38x.xx), with updating to new gfx card and drivers 440.31 this first time happens. This happens in 2.80 too.\n\nUsing checker texture result in a distorted result. In preview and finally render this error occurs.\nThis error only seems to occure if \"texture coordinate\" is set to object. Setting rotation <>0 for x or y in mapping lets the error vanish.\n\nCreate a plane and set up material as seen in the screenshot.\n\n\nadded:\nThis happens with \"whith noise\" too:\n", "Noisey White Noise\nOperating system: Windows-10-10.0.15063 64 Bits\nGraphics card: Quadro M2000M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.94\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nIn EEVEE, the new White Noise shader node its output depends on the 3D world-space coordinate while its input vector is constant. I expect that the output of the node would be the same for the same inputs (like Cycles does).\n\nLoad the attached .blend file:\n[NoiseyWhiteNoise.blend](NoiseyWhiteNoise.blend)\nObserve the node tree and the output:\n\nThe node tree is set up to feed the same vector into the White Noise node for larger regions such that a randomized checkerboard pattern should result.\nNow switch to Cycles and the output is as expected:\n\nWhen (in EEVEE) the selected input texture coordinate 'Generated' is replaced by 'Object' or 'Normal', the issue is still there. The issue is gone when replacing 'Generated' by 'UV', 'Camera', 'Window', or 'Reflection'." ]

[ "Use draw manager for clip editor drawing\nCould be stalled to 2.93 as there isn't an real issue here as far as we are aware of. The compositor issues are more tangable.", "View Pan not working for smaller clip start value\nOperating system: win 10 pro\nGraphics card: rtx 2060\n\nBroken: 3.5, 2.83\nWorked: never?\n\nFor smaller `clip start` value when we zoom out, `View pan` does not work\n\n- Open .blend file\n- Pan around by any method\nIncrease `clip start` value, this will fix panning problem\n[Sand_003.blend](Sand_003.blend)", "Python exception typing units into a spinner that accepts units\nMac OSX\n\n2.79a\n\nTyping in \"10 px\" in a field that accepts units raises a Python exception\n\nSelect Blender Render\nGo go the render tab\nScroll down to \"Bake\"\nType in \"10px\" into the \"Margin\" spinner, hit enter\n\n('unexpected EOF while parsing', ('<string>', 1, 4, '10px'))\n\nInput value does not save\n\nInput value should accept and strip px and behave correctly", "Knife Project Resolution is View Dependent \nWindows 7, x64, gtx 580\n\nBroken: 85c38e7\n\nKnife project resolution seems to be based on the camera zoom level. Artists are expecting that it wouldnt operate like this, ending up with meshes which look inaccurate.\n\n1. Open attached file\n2. knife project\n3. zoom in a lot\n4. notice how horrible it is\n5. undo\n6. knife project\n7. notice the difference\n\n[knifebug.blend](knifebug.blend)", "Workbench: Cull before batch creation during viewport animation rendering\n\n## Current Situation\n\nWhen drawing an object (eg sending draw calls to the GPU) the object boundary sphere is tested against the active view). When the test fails the object isn't send to the GPU. Before this happens the GPUBatches were already generated.\n\nWhen doing animation playback this could lead to the situation that the GPU Batches are calculated, but not used.\n\n## Target Situation\n\nWhen using the Overlay engine/Workbench engine we could test the objects to the default view (e.g viewport). When this fails we could skip this object at all. This feature would be disabled when the shadows are turned on and only enabled when doing an image/animation render.\n\nA consistent framerate is more important to animators then having some frames faster.\n", "Very slow interaction with Armature, if GPU Subdiv is enabled\nOperating system: Ubuntu 20.04\nGraphics card: Gefore MX230\n\nBroken: 3.3, 3.2.2\n\nwith the enabled GPU Subdivision, interactions with the armature are much slower than with the disabled\n\n[2022-10-23 13-29-00.mp4](2022-10-23_13-29-00.mp4)\n\nmove the bones with GPU Subdivision on and off\n[kira_lite.blend](kira_lite.blend)", "Brushes Assets Viewport User Interface\n{[F13331829](image.png), size=full}\n\nAdditional Notes:\n\n{[F13331831](image.png), size=full}", "3D Texturing: When changing the texture resolution, the pixel data isn't recreated\n* Start painting\n* Change image resolution\n* Continue painting.\n\nWe have a safe guard for this, but it doesn't seem to work anymore.\n", "Affect origins indicator gizmo is not affected by unit scale\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.2\nWorked: never\n\nThe gizmo used to indicate affect origin feature of transform tool is enabled does not change with different unit scale. This makes the gizmo invisibly tiny when using unit scale of 0.01, which is mandatory for Unreal Engine export capability, as described here: scene_scale.mp4\n\n1. In a new .blend file, set unit scale to 0.01\n2. Create a new cube. Newly created cube should be sized appropriately for new unit scale.\n3. Select new cube, Activate move tool, and activate \"Origins\" Affect Only option.\nResult: The gizmo to indicate Affect Only Origins feature is enabled is invisibly tiny and requires extreme zoom in:\n\nExpected: The Affect Only Origins indicator gizmo scale changes appropriately with different unit scales.\n", "Dissolving edge doesn't work as expected\nOperating system: Windows 10\nGraphics card: RTX 2070 SUPER\n\nBroken: 3.2.1\nWorked: not sure\n\n\nDissolving edges doesn't work as expected.\n\n\n\n\n\n[untitled.blend](untitled.blend)", "GPencil: Brush and stroke size related issues\n**Description**\n\nWhen drawing in grease pencil, control over the brush size and the thickness of the stroke is of course extremely important. Currently, there are some inconsistencies and confusing behavior that need to be addressed. Here is a list of current issues and some new proposals.\n\n - **Brush Radius:** Currently, the brush size can be changed via this slider in draw mode.  The name displays \"Radius\" and the tooltip reads \"Radius of the brush in pixels.\", but this is not consistent with the thickness of the strokes. If the user sets the **radius** to 100px and the *Stroke Thickness* option in the object data properties is set to *Screen Space* the stroke has a **diameter** of 100 pixels. If the *Stroke Thickness* is set to *World Space* the stroke has a **diameter** of 0.1 meters. A simple solution is to change the UI name from \"Radius\" to \"Size\" and clarify in the tooltip that the thickness or diameter of the stroke is meant.\n - **Radial Control:** When the user changes the brush size via the radial control (shortcut {key F}) the control has a **radius** of the given pixel value, not (like mentioned before) a **diameter** of the pixel value set.  \n - **Brush size in World Space** When the *Stroke Thickness* in the object data properties is set to *World Space* the displayed thickness of the strokes in that grease pencil object are calculated via the following formula: `((line_change + stroke_thickness) * pressure * pixel_factor) / 1000.0f` E.g. when all adjustment values are set to their default value then **1px (stroke thickness) = 1mm (world space)**. Currently, there is no way for the user to know this. The UI gives no indication of this and the manual also does not mention it. A possible solution is to change the units of the brush from pixels to meters and also do the right conversion so that the size is correctly displayed in the UI.\n - **Drawing in screen space/world space:** The user can change the stroke thickness (screen space/world space) in the object data properties. That means that *all* strokes in the grease pencil object will be either drawn using the screen space thickness in pixels or the world space thickness in meters. But there is currently not a way to choose the brush size to be in screen or world space. In sculpt mode, the user can choose the brush size \"reference\" (Radius Unit).  This would also be useful for grease pencil. \n # **Brush size indicator:** At the moment there is no visual feedback on how big the current brush is. A solution could be a \"ring\" around the cursor and deactivate it during drawing so it only shows up before starting the stroke.\n\n---\n**Related reports:**\n#83675, ", "Drivers round to 0 when working in um range\nOperating system: Windows 11\nGraphics card: RTX 3090\n\nBroken: 3.0\n\nWhen a driver/scripted expression returns a value in the micrometer range (0.05/1000 for example), it rounds to 0.\nThis is fatal because I need to store a \"clearance\" value and want to control that with drivers, which is simply not possible now. Please enable an even lower range of floats before rounding down to zero.\n\nMake a new project\nSwitch to metric units\nAdd a solidify modifier to a small object\nAdd a driver that calculates or just returns a um value\n- > It rounds down to zero", "Wayland: Incorrect UI scaling on high-resolution screen under GNOME 42.5 w/ fractional scaling\nOperating system: Ubuntu 22.04\nGraphics card: Radeon 6800XT\n\nBroken: 3.4.0, branch: blender-v3.4-release, commit date: 2022-12-06 18:46, hash: a95bf1ac01be, type: release\nWorked: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a936, type: release\n\nWhen running Blender 3.4 on a display with a resolution of 5120x2160 pixels and a fractional scaling factor of 125% configured in GNOME settings, the user interface is rendered extremely small. This was not the case with Blender 3.3.1.\n\nThis is running under a vanilla Ubuntu GNOME session with GNOME 42.5. Display server is Wayland.\n\nFrom testing various combinations, it appears that using fractional scaling larger than 100% actually reduces the UI size in Blender instead of increasing it.\n\n1. Log in to a vanilla GNOME desktop session using Wayland under Ubuntu 22.04\n2. Under GNOME settings -> Displays turn on \"Fractional scaling\" and set the scaling value to 125%\n3. Launch Blender 3.3.1 and observe the UI size (e.g. see 0MLM8lz )\n4. Launch Blender 3.4.0 and observe the UI size (e.g. see RUmvg3O )", "GPU subdivision: Wrong object's size when using subdivision surface modifier with GPU subdivision\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia Geforce GTX 660\n\nBroken: 3.1\nWorked: 3.0\n\nWhen GPU subdivision is activated, the object with subdivision surface doesn't show the correct size on the dimension section of the properties' sidebar.\n\nSelect the default cube.\nAdd Subdivision surface modifier\nOpen the properties' sidebar with N, the dimensions should be 1,68m (for X, Y and Z) but it shows 2,0m for all the axes. By deactivating the \"GPU subdivision\" the panel shows the correct dimensions.\n", "Incorrect VRAM quantity in the Status Bar ( GNU/Linux AMDGPU )\nHello, first bug report :)\nA minor bug about the VRAM displayed in the status bar in my GNU/Linux AMDGPU system.\n\nOperating system: Linux-5.4.0-7642-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.35.0, 5.4.0-7642-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 2.90.1\nBroken: 2.91.0 alpha\nWorked: No\n\nDisplayed VRAM quantity in the status bar is wrong: 16 GB instead of 8 GB.\n\nIn a similar system enable the Video Monitor option to show the GPU usage in the status bar.\nUploaded an image and system info file:\n\n[system-info.txt](system-info.txt)" ]

[ "Adding units in Imperial setting results in inconsistent values\nWindows 7\n\nBroken: 2.69.0 r60995\n\nUsing arithmetic in the the properties panel does not function as expected when using units. Not assigning units defaults to feet in the Dimensions section of the Transform section under the Properties panel. However, using arithmetic causes the result to be inconsistent with what is expected.\n\nFor example, type in \"2\" in the X Dimension, and it will result in 2 feet. Typing in \"2+2\" will result in 4 feet. This is what you'd expect.\nHowever, type in \"2+2in\" and the result is 6.727 feet. The expected result would be 2(feet) plus two inches (2.167 feet), so this is not what you'd expect.\n\nThis affects any work using arithmetic and units.\n \n1. On the default start-up scene, go to the Scene panel on the Properties panel and set the units to Imperial.\n2. In the 3D View window's property panel, go to Transform, then Dimensions, and type in \"4\" in the X Dimension. It will result in 4' (four feet).\n3. If you type \"2+2 in\" into the X Dimension, it will result in 6.728' (over six feet). However, typing \"2 ft+2 in\" will result in the desired result of 2.167' (two feet and two inches).\n\n**Screen Recording of error**\nEmbedded gif \nLink to gif f2BZ6pK.gif\nLink to html5 NeatPerkyAssassinbug\n\nThank you." ]

[ "Move some parameters to Blender's DNA\nThese parameters are supported (or going to be) by EEVEE-Next, and we should avoid duplicating the settings for each engine:\n- Motion blur curve\n- Panoramic camera settings\n- View Layer material override\n\nThis is a big change and 4.0 should be the right time to do this.\n\n", "Spreadout enum in pie menu gives strange result\nWin7x64GTX660m\n\nBroken: 2.73\nWorked: (optional)\n\nIf \"select similar\" operator is launched from a pie, items are arranged in a weird fashion (happens only in vertex and edge mode), overlapping one another and showing index numbers such as 167.\n\nFrom file, just click run in text editor (replaced example operator in text editor's pie menu template with *pie.operator_enum(\"mesh.select_similar\", \"type\")*).\n\n[overlappingPies.blend](overlappingPies.blend)", "Gpencil: dopesheet selection issues [clicking in summary deselects corresponding ID channel, e.g. breaking \"Jump to keyframe\"]\nBroken: version: 2.92.0 Alpha\nWorked: n/a, tested with 2.91 and didn't work\n\nJump to keyframe command & shortcut doesn't work anymore when you duplicate a keyframe.\nDoesn't matter what amount of layers there are.\n\n1) Draw a keyframe\n2) Draw a nother keyframe at another time = works\n\nDuplicate 1) keyframe = doesn't work, please see the video\n\n\n[gp_duplicate_keyframe_jump.mp4](gp_duplicate_keyframe_jump.mp4)\n\nReason why this happens: clicking in the summary will deselect the corresponding greasepencil ID channel [on which the \"Jump to keyframe\" operator relies]\nClicking in the summary should not deselect every channel there is, but keep the channel representing the selected greasepencil object selected as well [same as for other object types such as meshes].\nThis goes hand in hand with selecting a grease pencil object in the 3DView or Outliner not selecting the corresponding ID channel [this should also be the case (same as for other object types such as meshes)]", " Verts/Faces instantiation recursion: child items reappear if they are collection instances\nOperating system: kubuntu\nGraphics card: nvidia\n\nBroken: 2.82a - 2.90.1\nWorked: I don't think it did in the 2.8 series\n\n\nThe lower plane is the face-instancer of a blue sphere, and a collection instance that consists only of the peg (the one to the right). When the plane gets instantiated, the sphere is hidden (as expected) but the collection instance of the peg appears.\n\n\n\n\n\n[instantiating-a-collection-vs-object.blend](instantiating-a-collection-vs-object.blend)", "different generation of graphic card won't utilise together.\nOperating system: Windows 10\nGraphics card: Radeon R9 295X2 (secondary chip) + Radeon RX560 4GB\nAMD Ryzen 1700X\nMSI X370 Gaming Pro Carbon\n3 * 8GB DDR4-2400\n\nBroken: 2.82.7 to 2.83.3 <--- where x is from 0 to current stable version\nWorked: 2.8, 2.83.4 (partly worked, may end up sudden wattman reset)\n\nRadeon Version: 20.7.2\n\nafter the 3rd step, the render did not show anything, switching back to material viewport, the whole program was frozen. not sure if that is graphic card problem, but that way i could not even render anything. on 2.82.7, this also happened and the render kernels failed to work.\n\n\n1. open up a file of as shown\n2. set the preferences that would use OpenCL to render with R9 295X2 (and RX560)\n3. preview in Cycles\n4. unable to load the preview, switch back to material viewport.\n\n[zeta school 1.blend](zeta_school_1.blend)", "Blender GUI freezes when using activate_init = True\nOperating system: W10 64bit\nGraphics card: nVidia GTX 970\n\nBroken: blender-2.83-71b1ee940bb0-windows64\n\n\nOnce this bug T71112 was fixed I tried to \"use activate_init = True\" in my addon, but I'm still getting Blender GUI to freeze.\n\n* Open up [bugreport.blend](bugreport.blend) and run the script in Text Editor\n* Search for \"Name Location\" operator and run it\n* Type a text and hit OK. An Empty object is placed into the scene, named by what you typed in, but whole GUI becomes unresponsive.\n", "Intel GPU: switching between applications when in full screen mode causes glitches or screen flickering\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 530 Intel 4.5.0 - Build 30.0.101.1340\n\nBroken: version: 3.1.2\n\nWhen in Fullscreen, switching to other program and then returning to blender, glitch(black screen or something else) occurs suddenly and disappears.\nThis is not critical bug, but it would be good if it is fixed.\n\n\n- Open default blender file\n- {nav Window > Toggle Window full screen}\n- Switch to another application and again back to Blender", "Cycle crash\n[System Information](https://projects.blender.orgattachment)\n\nBlender version: 3.4.1\n\nCrash when switching from Material Preview to Rendered in Viewport Shading and GPU Compute was set for Cycles. In CPU mode it's OK.\n\n\nOpen project.\nSelect CPU in Cycles settings.\nSwitch from Material preview to Rendered in Viewport shading.\nNow it works.\nChange to GPU Compute in Cycles settings.\nCrash...\n\n", "Multi-Object-Mode: EditMesh Tools\nNote, while these follow menus, duplicates have been removed.\n\n## Remaining\n\n- MESH_OT_select_similar_region ([D3672](D3672))\n- MESH_OT_knife_project (leave aside for now, too complex - see [D3637](D3637))\n- MESH_OT_knife_tool (leave aside for now, too complex - see [D3637](D3637))\n\n\n## Mesh Menu:\n\n- ~~MESH_OT_duplicate_move~~ 1ade071052\n- ~~MESH_OT_extrude_edges_indiv~~ d8f70a26fd\n- ~~MESH_OT_extrude_faces_indiv~~ 07774d4860\n- ~~MESH_OT_extrude_verts_indiv~~ 7c415e6fd7\n- ~~MESH_OT_extrude_edges_move~~ 1d7bdbd273\n- ~~MESH_OT_extrude_vertices_move~~ 1d7bdbd273\n- ~~MESH_OT_delete_loose~~ bfc9d426bb\n- ~~MESH_OT_decimate~~ 5b45d32f3a\n- ~~MESH_OT_dissolve_degenerate~~ (initial comsmit) bfc9d426bb\n- ~~MESH_OT_dissolve_limited~~ 09e14cb5bc\n- ~~MESH_OT_face_make_planar~~ 0e5a4f927a\n- ~~MESH_OT_vert_connect_nonplanar~~ b942106c73\n- ~~MESH_OT_vert_connect_concave~~4043e4b820\n- ~~MESH_OT_fill_holes~~ 69b95b45f4\n- ~~MESH_OT_symmetrize~~ 03a916e5b5\n- ~~MESH_OT_symmetry_snap~~ 7f9768cb80\n- ~~MESH_OT_bisect~~ f9eb2f29fe\n- ~~MESH_OT_sort_elements~~ ffb424c85f\n\n## Snap Menu:\n\n\n- ~~VIEW3D_OT_snap_selected_to_grid~~ 016ba0f38b\n- ~~VIEW3D_OT_snap_selected_to_cursor~~ ec3357e03a\n- ~~VIEW3D_OT_snap_selected_to_active~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_selected~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_center~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_grid~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_active~~ (no change required)\n\n\n## Vertex Menu:\n\n- ~~MESH_OT_merge~~ b73c7381cc\n- ~~MESH_OT_remove_doubles~~ 22b2bab702\n- ~~MESH_OT_rip~~ 9d0d7c375e\n- ~~MESH_OT_rip_edge~~ 6539c1fc41\n- ~~MESH_OT_split~~ fc8d903000\n- ~~MESH_OT_separate~~ 5e915baec4\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_vertices_smooth~~ d915aa57f8\n- ~~MESH_OT_vertices_smooth_laplacian~~ 1f30232aa7\n- ~~MESH_OT_blend_from_shape~~ 6ae09dfcad\n- ~~OBJECT_OT_vertex_group_smooth~~ 3dee8b4a12\n- ~~MESH_OT_shape_propagate_to_all~~ 3a43528274\n\n## Edge Menu:\n\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_subdivide~~ (initial patch)\n- ~~MESH_OT_subdivide_edgering~~ 853e55b043\n- ~~MESH_OT_unsubdivide~~ e245f7c09c\n- ~~TRANSFORM_OT_edge_crease~~ (initial patch)\n- ~~MESH_OT_mark_seam~~ 61f0608b4a\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_edge_rotate~~ 66ffbf9b7d\n- ~~MESH_OT_edge_split~~ 207b549d40\n- ~~MESH_OT_bridge_edge_loops~~ eb2226dde2\n- ~~TRANSFORM_OT_edge_slide~~ (wrapper to other operator, working)\n- ~~MESH_OT_loop_multi_select~~ df49155cfb\n- ~~MESH_OT_loop_to_region~~ 8b41999ea0\n- ~~MESH_OT_region_to_loop~~ 56d65719b3\n\n\n## Face Menu:\n\n- ~~MESH_OT_flip_normals~~ 4704f2687a\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_fill~~ b726ff4fc4\n- ~~MESH_OT_beautify_fill~~ e42b8c32ab\n- ~~MESH_OT_inset~~ 570455fb83\n- ~~MESH_OT_bevel~~ d9e04cb594\n- ~~MESH_OT_solidify~~ f309c34cfe\n- ~~MESH_OT_intersect~~ dffd37877d\n- ~~MESH_OT_intersect_boolean~~ 46aec45b2a\n- ~~MESH_OT_wireframe~~ a0a78f6da4\n- ~~MESH_OT_poke~~ 3a9669bfff\n- ~~MESH_OT_quads_convert_to_tris~~ (initial patch bfc9d426bb\n- ~~MESH_OT_tris_convert_to_quads~~ (initial patch bfc9d426bb\n- ~~MESH_OT_face_split_by_edges~~ b6a822d726\n- ~~MESH_OT_faces_shade_smooth~~ e4c4e8566f\n- ~~MESH_OT_faces_shade_flat~~ 9fc0c0c3de\n- ~~MESH_OT_uvs_reverse~~ 63951bc987\n- ~~MESH_OT_uvs_rotate~~ faaffc4011\n- ~~MESH_OT_colors_rotate~~ 42c5c20e54\n- ~~MESH_OT_colors_reverse~~ 753be0a2a5\n\n## Mesh Toolbar: (should be added to menu)\n\n- ~~MESH_OT_loopcut~~ e87dd9aa00\n- ~~MESH_OT_convex_hull~~ e1cee0ac71\n- ~~MESH_OT_delete~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_delete_edgeloop~~ 49be803ad6\n- ~~MESH_OT_dissolve_edges~~ 7f5c469716\n- ~~MESH_OT_dissolve_faces~~ 848d9cda0e\n- ~~MESH_OT_dissolve_mode~~ (wrapper of vert/edge/face dissolve)\n- ~~MESH_OT_dissolve_verts~~ 5f59a8bb11\n- ~~MESH_OT_drop_named_image~~ b4d23818c8\n- ~~MESH_OT_dupli_extrude_cursor~~ 68a719f1ea\n- ~~MESH_OT_duplicate~~ 1ade071052\n- ~~MESH_OT_edge_collapse~~ 2349b9777a\n- ~~MESH_OT_edgering_select~~ 7fa77cd31d\n- ~~MESH_OT_edges_select_sharp~~ dd93c80747\n- ~~MESH_OT_extrude_region~~ 1d7bdbd273\n- ~~MESH_OT_extrude_repeat~~ 9a125ca5fe\n- ~~MESH_OT_faces_select_linked_flat~~ 1bb9ccf887\n- ~~MESH_OT_fill_grid~~ 1cbe3b6e03\n- ~~MESH_OT_hide~~ 5d8937e8ba\n- ~~MESH_OT_loop_select~~ 7fa77cd31d\n- ~~MESH_OT_normals_make_consistent~~ 266638d783\n- ~~MESH_OT_offset_edge_loops~~ efd843b51c\n- ~~MESH_OT_reveal~~ f4c1685a16\n- ~~MESH_OT_screw~~ badd88ca02\n- ~~MESH_OT_select_all~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_axis~~ c899f21800\n- ~~MESH_OT_select_face_by_sides~~ 90c9458b2f\n- ~~MESH_OT_select_interior_faces~~ e161c51e7f\n- ~~MESH_OT_select_less~~ b6a7fa1880\n- ~~MESH_OT_select_linked~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_linked_pick~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_loose~~ eacb2eb423\n- ~~MESH_OT_select_mirror~~ 3ebe389605\n- ~~MESH_OT_select_mode~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_more~~ 2309131b4d\n- ~~MESH_OT_select_non_manifold~~ 4da2aec2bb\n- ~~MESH_OT_select_nth~~ 63c2397171\n- ~~MESH_OT_select_random~~ 847f028b71\n- ~~MESH_OT_select_similar~~ 75b2091d42\n- ~~MESH_OT_select_ungrouped~~ 1d8e6c5cd0\n- ~~MESH_OT_shortest_path_pick~~ c32cc3e43e\n- ~~MESH_OT_shortest_path_select~~ 5a431be629\n- ~~MESH_OT_spin~~ ab8dded330\n- ~~MESH_OT_vert_connect~~ 944054fbb6\n- ~~MESH_OT_vert_connect_path~~ fc7316fb54\n", "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "Eevee: Unknown bug when just create first shader \nStep to reproduce an issue (or bug?):\n1. Run latest Blender v3.4alpha (Experimental build) with Eevee Next integrated.\n2. Create scene with just one Cube.\n3. Go to Properties > Material panel > Create New material.\n4. Boom! Blender shut down imidetily.", "Title: CTRL-Z from edit into sculpt mode causes crash if mesh has shape-keys \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.82 (sub 7)\n\nBlender crashes when you CTRL-Z back to sculpt mode when the mesh has shape-keys. This bug happens in 2.83.0 and up, only in the Windows builds. Tested in Linux Mint 19.3 and had no crash there.\n\nAdd basis shape-key on any mesh -> change to sculpt mode -> Change mode to edit -> Undo back -> This causes a crash when it undoes back to sculpt mode.\n", "3DConnexion Mouse not working in new Blender instance\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon VII OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.81 (sub 5)\nWorked: (optional)\n\n3dconnexion mouse works only in one instance of Blender\n\nIf I open 2nd instance of Blender 3d mouse does not work in it, only in the original file. This behaviour is same in official 2.8. I have tested this in Rhino for Mac. There Mouse works in both instances, which ever is active of course.\n", "Random vertices light up as if they were selected (but they're not) when I select one vertice at a time\nOperating system: Linux-5.4.0-7634-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 780 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.83.0\n\n\n- See the GIF above (sorry my mouse cursor didn't get recorded :(\n- so, in short, when I select one vertex and then select another, random vertices light up as if they're selected but they're not. Really annoying.\n- this happened to me in 2.82a as well (but only in Linux, not in Windows)\n\n- load factory settings\n- subdivide the default cube 10 times, add subsurf modifier (CTRL+2), shade smooth\n- in EDIT mode, duplicate the mesh 6 or so times\n- select one vertex, select another vertex, the glitch seems to happen (like in the GIF above)\n\n**BLEND**\n[mesh_glitches_bugreport.blend](mesh_glitches_bugreport.blend)\n\n", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n" ]

[ "Outliner Bug (maybe)\nOperating system:Win 10 pro 64\nGraphics card:Zotac GTX 750Ti\n\nBroken:2.80\n(example: 2.79b release)\n(example: 2.80, 74db65e5424, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nOutliner toolbar switches from top to bottom.\nI uploaded a video for your convenience(Sorry for the audio, I don't record very often) \nBased on the default startup or an attached .blend file (as simple as possible).\nClick on changer editor button -> User Preference -> change Editor -> Outliner{[F5858799](Desktop_2018.12.06_-_21.43.29.01.mp4)}" ]

[ "Boolean merges CustomData inconsistently (UVs, VCols), breaks UV Map Node\nOperating system: Linux-5.0.0-25-generic-x86_64-with-Ubuntu-19.04-disco 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.34\n\nBroken: version: 2.81 (sub 2)\nWorked: (optional)\n\nThe UV Map of an object with Boolean Modifier doesn't work when the UV is assigned to the texture with the UV Map node. \n\nOpen this file:\n[boolean_uv_map.blend](boolean_uv_map.blend)\nThe UV layout of the bigger cube is not used. Once you unplug the custom UV Map node in the shader, the UV Map works again. It also works when you disable the Boolean Modifier. ", "Select next active fails in some cases (default cylinder, cube)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro K2100M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 3.1.2\n\nWhen adding object: circle or cylinder, when selecting vertices, it does not select the next vertex at command: shif + ctrl + (+).\nif I select several vertices manually and give the command: shift + ctrl + (-) deselect, it works perfectly.\n\nany other option works, works well with other objects, sphere, monkey sesame, the circle object works if you select two consecutive vertices, if you select one vertex yes one no, it no longer works. .]\n\n- add cylinder object\n- Edit mode\n- Select 2 vertices then {key shift ctrl +}\n\n[2022-05-24 19-58-17.mp4](2022-05-24_19-58-17.mp4)", "Color Attribute not affecting \"bump\" shader node\nOperating system: Windows 10\nGraphics card: RTX 3080\n\nBroken: 3.50 beta (03 March 23)\n\nUsing a mesh's color attribute as an input to the \"bump\" shader node does not result in the expected behavior. Using the color attribute for practically every other value (including the normal map node, roughness, metalness etc.) works as expected.\n\nCreate a mesh and paint a color attribute with, for example, a black-and-white pattern.\nGive the mesh a material and add the color attribute.\nPlug the color attribute into the \"height\" input of the bump node, and view the result. There is no difference compared to the \"height\" input being left disconnected.\n\nOther inputs (such as a noise texture) result in the expected behavior.\n\n", "Text strip duplication with madeup driver\nOperating system: Linux neo 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux\nGraphics card: nvidia GTX 970\n\nBroken:\n```\n3.0.0-alpha+master.a3027fb09416-linux.x86_64\n```\nWorked: (?)\n\nI duplicated a Text strip via <shift><D>. Then the clone had a driver on 'Location X' set, that the original has not. If You delete that driver, blender crasches (see #91912)\n\n\n- Load attached file\n- Duplicate the Text strip with <Shift><D>\nThe new Text strip now has a driver on Location X\n\n[driver_duplicate_bug.blend](driver_duplicate_bug.blend)", "Links persist invisibly after their source sockets are removed\nBroken: Probably forever (e.g. 3.0, 3.1)\nWorked: N/A\n\nIf the output socket of a node is removed, the input socket it was connected to does not show a button to input a value. It acts like it's still connected.\n\n**Detailed replication**\n1. Go into the Shader Editor\n2. Create the *Voronoi Texture* node and a *Math* node\n3. Set the *Voronoi Texture* node to 4D, and plug its new W output into the *Math* node\n4. Set the *Voronoi Texture* node to 3D. Observe that the input on the *Math* node still acts like it's connected\n5. Click and drag from that input on the *Math* node. A bogus wire will appear from the *Voronoi Texture* node, coming from where the W output used to be.\n\nYou can then plug this wire into another socket. It will disappear again once you let go. If you set the *Voronoi Texture* node back to 4D, the wires will re-appear.\n\nVideo example:\n\n[XwBMq60aMI.mp4](XwBMq60aMI.mp4)\n\n**Another example:**\n\n{[F13079601](free-socket.blend), size=full}\n\nIn this case you can even save the file in this state where you can't see or edit the value of the node until you disconnect it.\n\n", "The X or Delete button does not work in the outliner (Blender File)\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.6\n\n[The X or Delete button does not work in the outliner (Blender File)]\n\n- Open default startup file\n- {nav Outliner >Display Mode > Blender File}\n- In outliner {nav Brush > RMB > Delete > RMB > Assign Shortcut > X}\n- Attempt to delete any brush with hotkey (will not delete brush)\n- Change hotkey (eg {key Shift X}) and now attempt to delete brush with hotkey\n\nwhen you press X items in:\n| Broken | Brushes, Cameras, Images, Lights, Line Styles, Materials, Meshes, Palettes, Workspaces, Worlds |\n| -- | -- |\n| worked | Collections, Objects, Scenes |\n\n\n\n\n[Delete _X_ Button.blend.py](Delete__X__Button.blend.py)\n\n{[F12271213](Delete__X__Button.blend)}]\n\n", "Unify Image Texture node in geometry and shader nodes\nGeometry nodes added a new Image Texture node where the image datablock is a socket.\n\nWe should unify these two nodes. There are some design decision to make regarding how to deal with image users and the frame offset socket, see discussion in {[D12827](D12827).}. ", "Unlinked/deleted objects reappear, when deleted at startup in a python script (i.e. ./blender --python delete.py)\nDebian 7.4 64bit, also occurs on OSX\n\nBroken: 2.63, 2.69.0\n\n\nUnder certain conditions objects which have been unlinked from a scene do reappear.\n\n\n\n\n - Start blender with `./blender --python delete.py` (see below for the script) (blender just shows an empty scene)\n - Once the GUI is loaded, do: **Add -> Mesh -> Plane**\n # Immediately afterwards hit **F6** and adjust one Property of the newly added object (e.g. the radius)\n\nResult: the objects from the start scene (camera, lamp, cube) reappear.\n\n**Doesn't occur when...**\n - ... A second Mesh is inserted before hitting **F6** to change its properties\n - ... The script is executed in the Blender Editor (and not at startup with option `--python`)\n\n\n**Python script `delete.py`**\n\t\n\n\n\n```\n import bpy\n \n```\n - IMPORTANT: run as: ./blender --python delete.py\n - once blender started, here is what I did in Blender GUI:\n - - add a new mesh (Add -> Mesh -> Plane)\n - - Hit F6 immediately afterwards and modify radius\n # Result: Blender start scene (cube, light & camera) is visible again\n```\n \n```\n # the described bahaviour and result is the same for deleteScene1() - deleteScene3()\n```\n \n def deleteScene1():\n bpy.ops.object.select_all(action='SELECT')\n bpy.ops.object.delete()\n \n def deleteScene2():\n bpy.ops.object.select_by_type(type='MESH')\n bpy.ops.object.delete()\n bpy.ops.object.select_by_type(type='LAMP')\n bpy.ops.object.delete()\n bpy.ops.object.select_by_type(type='CAMERA')\n bpy.ops.object.delete()\n \n def deleteScene3():\n scn = bpy.context.scene\n for obj in scn.objects:\n scn.objects.unlink(obj)\n \n```\n - deleteScene1()\n - deleteScene2()\n```\n deleteScene3()\n\n```\n\n\n\n", "Knife tool fails on a non-planar n-gon\nBroken: 2.74 up to and including 2.92 master\nWorked: 2.73 (yes, I bisected that far back ;) )\n\n\nKnife tool fails to cut between verts in n-gons of certain configuration.\n\n\nLoad the attached .blend and try to make a knife cut between the two selected verts (i.e. try to create an edge connecting them).\n\n[knife_fail.blend](knife_fail.blend)\n\n(If you want to test in 2.73 yourself, copy the object from a running instance of 2.9x into 2.73 using ctrl+c/ctrl+v, then replace the mesh in another existing mesh object).", "Point Clouds only support one material\nOperating system: macOS-13.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken version: Current main.\nWorked: Never\n\nWhen using the `Join Geometry` node in Geometry nodes to join two points together, their material is reset to default. This only happens when joining two or more \"lone\" points.\n\n1. Recreate the geometry node setup found in the image below\n2. Change the render engine Cycles (necessary to see points with a material)\n3. Render the scene.\n4. Notice that the materials you assigned to the points are not applied.\n\nI have also included a .blend file with steps 1 and 2 done.\n[Missing Material - Join Geometry.blend](attachment)\n\n\n", "Compositor doesn't update when \"render region\" is used\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 2)\nAlso any previous version.\n - Open file:\n[border_render_comp_bug.blend](border_render_comp_bug.blend)\n - Render frame (F12)\n - Red background is confined to \"render region\":\n\n - If you refresh the compositor it will work. For example if you reconnect nodes or check and uncheck a box.\n", "Console traceback when using custom socket types on node groups\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nBroken: version: 2.93.0\nWorked: 2.92\n\nWhen creating custom node groups with inputs other than NodeSocketShader (and probably others), the console sends a traceback error warning to report this as bug.\n```\nCode marked as unreachable has been executed. Please report this as a bug.\nError found at C:\\Users\\blender\\git\\blender-v293\\blender.git\\source\\blender\\blenkernel\\intern\\node.cc:441 in write_node_socket_default_value.\n```\n\nStartup blender with this file and run the script in the text editor. The file is entirely gutted of data blocks besides the script. The console should now be spammed with the above error whenever the scene updates\n[create_vector_node_group.blend](create_vector_node_group.blend)\n", "Recursive Purge Orphans datablocks on file save\nFully deleting datablocks from a blend file doesn't happen as easily as most users might expect, since \"delete\" is often used in the UI when \"un-link\" is what is actually meant. This can cause a lot of confusion and uncertainty during production. Proper deletion of datablocks requires that they are first un-linked, then they can be purged via File->Clean Up->Recursive Unused Datablocks. This works beautifully, and I would like to propose adding an option to have this operation executed after existing deletion operators. For example, after deleting a collection of objects, it would then also delete everything that was used only by those objects, such as their mesh and shape key datablocks, materials, actions, textures, etc.\n\nMy previous proposal was to have an option to execute Recursive Purge only on file save, which seemed to make sense to everyone I talked to at the time. (@dr.sybren @mont29 @JulianEisel @SimonThommes ) \nI still think that solution would be a step forward, but the new proposal above would achieve the same goals in an even more foolproof way. \n\n### Use case\nCurrently, this can very easily happen:\n- Animator duplicates an overridden character. All its objects get a .001 suffix.\n- Animator deletes that copy, saves their file, and later re-opens it. Only one \"layer\" of unused objects has been cleaned, so there can still be orphan object datablocks lying around unseen.\n- Animator duplicates the character again. Now the number suffix of their objects are all over the place. Some of them have .001 and others have .002.\n\nAs they continue working and duplicating characters, the old, unused objects slowly get deleted, and the name suffixes really get all over the place. It's not nice to get your objects names all mixed up like this, as things get really confusing when trying to troubleshoot problems in a production file, since everywhere where one object references another, the mismatching suffixes give the troubleshooter anxiety and uncertainty. The only way to avoid this currently is to tell the entire production team to always run a recursive Purge after deleting anything, which is very error-prone. \n\n\n### Potential issues\n\n- ~~The current recursive purge purges Text datablocks, which is bad because they don't have the possibility of a \"Fake User\", so they should be excluded (or better yet, be included in the \"fake user\" system, and get a fake user by default). ~~ (Fixed by [D10983](D10983))\n- Actions don't have fake user enabled by default. The long standing issue of Action datablocks \"disappearing\" on users and making them lose hours of work if they forget to click Fake User would be exacerbated by this change. This could be trivially fixed by giving Actions a fake user on creation, and forcing users to clean up their unused Actions themselves.", "'Reset to Default Value' sets any property on a node to 0\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nIn shader editor gamma default is 1 when I do the hover over setting and press backspace to reset the default it goes to 0.0\nSame with hue/saturation/value.. and probably more.\nThe one with hue is pretty annoying as it has specific default settings .\nSame deal with groups - I set the defaults, it doesn't default .. goes to 0\n\n- in any node editor hover over any setting and press backspace to reset to default value.\nIt defaults to 0 instead of 1 or whatever it's default was in shader editor..\n\n", "Moving reroute nodes with click-drag behaves unpredictably\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.1.0 Alpha\n\nThe recent builds of Blender 3.1 add an option to finally move reroute nodes with mouse only, like any other node types. Unfortunately, there is no pre-selection highlight to let the user know which action they are about to perform on click-drag action. According to the anti-features page, pre-selection highlight section, if such feature does not behave reliably and predictably, it should be reported as a bug: AntiFeatures \n\nThis is why I am reporting it as such.\n\n[2022-01-24 11-25-05.mp4](2022-01-24_11-25-05.mp4)\n\nCurrent implementation suffers from following issues:\n1. The circular area/radius where move operation occurs is not visible. It is not visible how far from the reroute node position the node can still be transformed.\n2. Click dragging slightly outside the reroute node circle will still result in node wire drag rather than transform, further adding to the confusing behavior.\n3. It is not obvious that the click-drag transforms works **only** when the reroute node is selected first, which is inconsistent with click-drag transform behavior of the other nodes.\n\n1. Add a reroute node to any node graph\n2. Select the reroute node\n3. Click-drag around near the reroute node in various distances\nResult: What happens when LMB click dragging near the reroute node is not reliably predictable\nExpected: Outcome of LMB click-drag input operation near a selected reroute node can be reliably predicted\n\nProposed solution:\nWhen the reroute node is selected, and therefore can be transformed, draw a simple transform gizmo representing the screen area, which results in the transform operation when click-dragged, but only for reroute node closest to the mouse cursor, and only when the mouse cursor is near it (the same the scrollbars are dynamically drawn only in the close proximity of the mouse cursor):\n" ]

[ "ColorRamp mute is not working\n%%%--- Operating System, Graphics card ---\nW8 64b, GeForce 250 S\n\n - Blender version with error, and version that worked ---\nr61076\n\n - Short description of error ---\nWhen you mute ColorRamp node in Compositor, whole render is not visible not only ColorRamp muted.\n\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\nNode > Toggle node mute or press M with ColorRamp selected.\n%%%" ]

[ "\"Object Custom Properties\" Drivers don't work while Object Custom Properties are created with simple script.\n\n\n\n\n\n\n\n\n\n\n\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.0 Beta\n\n\"Object Custom Properties\" Drivers don't work while Object Custom Properties are created with simple script.\n\n1. Open Blender.\n2. Select the Default Cube.\n3. Run this code via Text Editor (it creates one Object Custom Property to Cube, and one Object Custom Property to Camera):\n\n\n```\nimport bpy\n\nob = bpy.context.active_object\n\nprop_name1 = ob.name + \"_Property\"\nob[prop_name1] = 0.0\nob.id_properties_ensure() # Make sure the manager is updated\nproperty_manager = ob.id_properties_ui(prop_name1)\nproperty_manager.update(min=0.0, max=1.0, soft_min=0.0, soft_max=1.0)\n\ncamera = bpy.context.scene.objects['Camera']\n\nprop_name2 = ob.name + \"_Property\"\ncamera[prop_name2] = 0.0\ncamera.id_properties_ensure() # Make sure the manager is updated\nproperty_manager = camera.id_properties_ui(prop_name2)\nproperty_manager.update(min=0.0, max=1.0, soft_min=0.0, soft_max=1.0)\n```\n4. Select Camera.\n5. Right Click on created Camera's Object Property \"Cube_Property\" and Left Click on \"Copy as New Driver\".\n6. Select Cube.\n7. Right Click on created Cube's Object Property \"Cube_Property\" and Left Click on \"Paste Driver\".\n8. Value is not drivered / updated. Unless you edit driver, click in Data Path Textbox or Name Textbox, click Enter - now everything works great, but... i didn't change anything there.\n\n", "Armature Object's \"Display As\" does nothing\nOperating system: Linux-5.3.0-26-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 6)\nWorked: version: 2.79 release.\n\nWhen I add an armature and change the Viewport Display Mode, nothing happens.\n\n\nOpen the blender;\nDelete the default objects;\nAdd an Armature, single bone;\nIn the Properties Panel, Object Properties, Viewport Display:\nChange 'Display As' to anything, it doesn't work.\n\n\n\n", "Object Info Random - inconsistent result\nOperating system: Win10 64\nGraphics card: gtx1050ti\n\nBroken: 2.79, 2.8\n\n*Random* output from **Object Info** depends on every object in scene, even *Empties*!\nThere are two identical scene sets with linked objects, but *Empty* belongs to *Scene.001* only. *Cube* is instanced via duplifaces and *Random* produces different result if *Empty* isn't linked in both scenes.\n\nOpen file, viewport render Scene and Scene.001\n[Obj_info_Random_out.blend](Obj_info_Random_out.blend)", "When changing the width of frame, it also changes frame location.\nIf you create frame and set it into (0,0) location. Then grab right side of the frame node and make frames width bigger. Now using python read the frame \nlocation again and it is not (0,0) anymore. \n\n", "Toggle to Edit Mode call error when the Blender use linked a object data from another file\nOperating system: Linux 5.10.2\nGraphics card: Intel Haswel (4-th Gen ) HD Graphics 4600\n\nBroken: 2.92\n\n\nToggle to Edit Mode call error when the Blender use linked a object data from another file\n\n\n1) Create any object in a scene and save this file \n2) Create a new blend file and link the object from previous saved a file with `File` → `Link..` and then select this object.\n3) Then convert linked object to local object with `Object` → `Relations` → `Make Local...` → `Selected Objects`\n4) Select the object and press Tab that go to Edit Mode. \n5) Error - Unable to execute 'Toggle Editmode', error changing modes\n\nor download both files and then open linked.blend:\n\n[source.blend](source.blend)\n[linked.blend](linked.blend)\n\n", "Generated texture coordinates missing when switching from solid to rendered mode\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.80.0-git.14884cda1ff5-windows64\nWorked: 2.79b f4dc9f9d68b\n\nThe \"Generated\" texture coordinates make textures \"stick\" to the surface, even if the object is being deformed.\nHowever, this does not work as expected in 2.80 with the Armature Modifier, neither in Eevee nor Cycles.\nIn 2.79 in works correctly.\n\nPossibly related: #59275.\nHowever, this bug affects both Cycles and Eevee, while that report only concerns Eevee (and Cycles works correctly).\nThe difference is that here an Armature is used, while that report uses Shape Keys.\n\n[generated.blend](generated.blend)\nThe scene contains a cube with an armature modifier.\n- Open in both 2.79 and 2.80.\n- Press F12 to render.\n- See how the texture mapping differs.", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "Design discussion: Add object instancing to support transforming linked objects?\nThis is an initial task to start discussion on this topic. More details would have to be looked into for an actual design.\n\n### Motivation\n\nLinking objects in Blender has the inherent design limitation that it also links the object's transform, which means you can't transform an object that was linked. This is a very basic and important operation. With library overrides, that issue is mitigated; however IMO we should look at this as a feature for production use-cases, not as something for more informal, low-overhead usages. This would be a complex solution for the user to manage for a simple problem. They need rather deep understanding of how Blender data-management works to manage library overrides.\n\nEspecially for the Asset Browser, it would be good to have a simple solution that behaves as users expect. Apparently what they do expect is that they can simply link objects, while being able to transform them still. Not being able to edit other object properties seems fine.\n\n### Possible Solutions\n\nFor collections we have actually addressed this issue by supporting linked collection instances. That means, while the collection and its contents are linked, the collection is placed relative to an emtpy that is local to this file. So by transforming the empty the entire collection is transformed. The idea of instancing can be brought to objects so transforming linked objects becomes possible in effect.\n\nSome ideas on how object instancing could be supported on linking:\n* **Object is made local, the mesh, materials, etc stay linked** Simple to implement - downside is that object properties, modifiers, constraints, physics and the like would not be linked anymore.\n* **Instancing via empty.** This would be very similar to collections. An empty can instance an object which means it acts as a parent of the object.\n* **Wrap into collection instance.** Effectively the same as instancing via an empty, but the user would see an intermediate collection. It's simple to add this, but kind of forces an implementation detail onto users.\n\n### Other Approaches\n\nInstead of trying to support object instancing, other things could be done on linking:\n* **Automatically create library overrides for transforms**. Another simple solution technically and at least saves the user from having to know about or setup the library overrides when linking. But obviously pushes users towards using library overrides, which they sooner or later will still have to deal with.", "Disabled objects still get evaluated if there is a driver on their hide_viewport property.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.90 (sub 0)\nWorked: I think never\n\nCurrently, when an object is hide_viewport==True, that object as well as any dependencies it has that are also hidden, will have not hinder viewport performance. But that's not the case when there is a driver on the object's hide_viewport property, even if that driver evaluates to True.\n\nThe use case is as a rigger, I would give animators options to hide parts of a character to gain viewport performance.\n\n[remesh_performance_depdendency_test.blend](remesh_performance_depdendency_test.blend)\n- In the blend file, simply start playback and notice(unless your computer is a beast) you should get fairly low fps, even though the objects are disabled.\n- Remove the driver from the sphere's hide_viewport, and performance goes back to normal.", "Application handler not executed when video sequencer contains a strip\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.4\n\nA registered handler for frame_change_post does not get executed while rendering an animation when there is a strip present in the video sequencer.\n\n1. Open the example file and turn on the system console\n2. Execute the example script present in the file\n3. Render an animation, note how you can see the handler getting called before each rendered frame in the console\n4. Add a strip to the video sequencer (for example a solid color)\n5. Render another animation, note how this time the handler doesn't get called per frame anymore\n6. Remove the strip again\n7. Render once more, note how it works again as expected\n\n**Example file**\n[bug_example.blend](bug_example.blend)\n", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "Changing the 'Render Region' when rendering with Python with 'Persistent Images' checked results in glitched renders\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 1)\nWorked: -\n\n\nI have a (simplified) script that moves to a specific frame, sets the render region to a specific position and renders, before repeating the process for the next frame with a new render region position. When the 'Persistent Images' option in *Render> Performance> Final Render* is on, some of the resulting renders are glitched (they open but have artifacts) and the objects do not seem to be in the correct position. \n\nTurning off 'Persistent Images' results in renders with the objects in the expected location and without artifacts.\n\nFor some context, I do not specifically *want* to have 'Persistent Images' on; I have an add-on which repositions the render border on a per-frame basis and a user reported glitching renders.\n\n**Frame 8** - Persistent Images **off**- Correct location in render\n\n\n\n**Frame 8** - Persistent Images **on**- Incorrect location in render and artifacts\n\n\n\n**Frame 7** - Persistent Images **off**- Correct location in render\n\n\n\n**Frame 7** - Persistent Images **on**- Incorrect location in render\n\n\n\n\n[Render Region + Persistent Images bug.blend](Render_Region___Persistent_Images_bug.blend)\n\n 1. Open the attached blend file and set an output directory for the render.\n 2. Press 'Run Script' in the open text editor to render out the images.\n\nImages 3, 7, 8 and 9 will probably have artifacts and for the other frames the objects will be in the incorrect location (the border should be positioned perfectly around them).\n\n**Note**: I have set the script to render 10 frames because it seems to depend on what was rendered previously as to whether the glitches/incorrect positions will appear. Rendering the glitched frames on their own does not produce the errors consistently.\n\n", "Meshes are invisible if any objects are set to display 'In Front'\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) HD Graphics 6000 Intel Inc. 4.1 INTEL-12.10.14\n\nBroken: version: 2.83.0\nWorked: 2.82\n\nIf any objects are set to display as 'in front' in a project, all meshes will display only as faint outlines. In edit mode, meshes display similar to how they would if they were set to display as wireframe.\n\nAdd a new mesh, curve, or armature to the scene.\nObject properties -> Viewport display -> Enable 'In Front'\n\n", "Multi-object-Mode: EditMode transform properties\nEdit-mode buttons currently only show median values for the active edit-object.\n\nThe Mean Crease value of the N panel doesn't work for multiple objects:\nHere i have 2 objects selected\n\nIn Edit Mode changing the Mean Crease value does change its effect only on the selected object:\n", "Instancing Performance Improvements\nPerformance of instances in the viewport is much worse than is should be. This task is mean to keep track of possible improvements.\n- [ ] Use a vector or similar data structure instead of an linked list for storing an objects instances.\n- [ ] Don't recompute an object's instance list on every redraw.\n- [x] Store bounding box in geometry so that it is not recomputed for every geometry instance (#96968).\n- [ ] Remove the nested instance limit, avoiding the need to realize instances in some cases\n- [ ] Support passing many instances of the same to the render engine at once to reduce per-instance overhead. " ]

[ "Keyframed properties do not update in 'Render' context\nOperating system: Windows\nGraphics card: Irrelevant\n\nBroken: 2.81a\nWorked: 2.79\n\n\nI recently discovered that ever since the 2.80 release, there has been a critical discrepancy between the viewport context and the rendering context with respect to the `location`, `rotation` and `scale` properties (and perhaps more) from frame to frame. Visually, everything behaves correctly, but when running very basic scripts on `app_handlers.frame_change_post`, the objects' transform properties seems to be frozen in time.\n\nBased on the default startup, with the System Console open:\n\n - Select the default cube, and add a `LocRotScale` keyframe\n - In the timeline, change the active frame and end frame to frame 50\n - Move, rotate, and scale the cube\n - Add a second `LocRotScale` keyframe\n - Run the following basic script from the Text Editor:\n\n```\nimport bpy\n\[email protected]\ndef update_values(scn):\n print(bpy.data.objects[\"Cube\"].location) # and/or 'rotation_euler'/'scale'\n\nbpy.app.handlers.frame_change_post.append(update_values)\n```\n\n - Play the animation, and note that the object's location will update every frame in the System Console.\n - From the `Render` dropdown, hit `Render Animation`. Notice now that the object's location does not change in the System Console.\n" ]

[ "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "crash when import fbx\nOperating system: Window 10 pro\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc\n\n\nCrash when I imported fbx file \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "Cycles Render with Intel UHD GPU Crashes\nOperating system: macOS Ventura 13.0.1\nGraphics card: Intel UHD Graphics 630 (built-in), AMD Radeon RX 6800 (eGPU)\n\nBroken: 3.4.0 (downloaded from the Blender website)\nWorked: the last 3.3.1\n\nIt is impossible to render in Cycles with the Intel GPU enabled: Blender crashes\n\nOn a Mac Mini 2018 (Intel) with 6-core i7 CPU and 32GB of RAM, with Stage Manager enabled, open Blender, load a file, then in the Preferences, enable only the Intel GPU (uncheck the eGPU), and start rendering. Note: unless it is the first attempt (that involves the loading of the kernels), unchecking the eGPU may not even be necessary.\nWhen the preliminary steps are finished (such as the BVH building, importance map, and so on), Blender will crash before the rendering proper starts (before anything appears in the render result output).\nThe subsequent error dump will look as follows: \n\nThe full dump is below:\n\n```lines\n-------------------------------------\nTranslated Report (Full Report Below)\n-------------------------------------\n\nProcess: Blender [4086]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.4.0 (3.4.0 2022-12-07)\nCode Type: X86-64 (Native)\nParent Process: launchd [1]\nUser ID: 501\n\nDate/Time: 2022-12-09 13:00:26.8303 +1000\nOS Version: macOS 13.0.1 (22A400)\nReport Version: 12\nBridge OS Version: 7.0 (20P420)\nAnonymous UUID: DA7E5727-A75F-6765-C417-804DFCD4552C\n\n\nTime Awake Since Boot: 5000 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 35\n\nException Type: EXC_CRASH (SIGABRT)\nException Codes: 0x0000000000000000, 0x0000000000000000\n\nID Vend/Dev\n8488 73bf1002\nSeconds Ago ID Type\n 5000.0 8488 Attach\n\n\nThread 0:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t 0x7ff8140160ce __semwait_signal + 10\n1 libsystem_c.dylib \t 0x7ff813f2ab4a nanosleep + 196\n2 libsystem_c.dylib \t 0x7ff813f2aa80 usleep + 53\n3 Blender \t 0x1069dd928 WM_main + 24\n4 Blender \t 0x106262b8e main + 878\n5 dyld \t 0x7ff813d21310 start + 2432\n\nThread 1:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 13:: caulk.messenger.shared:17\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 caulk \t 0x7ff81d7598f8 caulk::mach::semaphore::wait_or_error() + 16\n2 caulk \t 0x7ff81d73f664 caulk::concurrent::details::worker_thread::run() + 36\n3 caulk \t 0x7ff81d73f328 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 41\n4 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n5 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 17:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 18:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 25:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t 0x7ff8140136a2 mach_msg2_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff81402167d mach_msg2_internal + 82\n2 libsystem_kernel.dylib \t 0x7ff81401a71a mach_msg_overwrite + 723\n3 libsystem_kernel.dylib \t 0x7ff814013989 mach_msg + 19\n4 CoreAudio \t 0x7ff81635f8a5 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n5 CoreAudio \t 0x7ff8162384c1 HALC_ProxyIOContext::IOWorkLoop() + 3783\n6 CoreAudio \t 0x7ff816237029 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 63\n7 CoreAudio \t 0x7ff8163be630 HALB_IOThread::Entry(void*) + 72\n8 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n9 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 31:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t 0x7ff8140136a2 mach_msg2_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff81402167d mach_msg2_internal + 82\n2 libsystem_kernel.dylib \t 0x7ff81401a71a mach_msg_overwrite + 723\n3 libsystem_kernel.dylib \t 0x7ff814013989 mach_msg + 19\n4 CoreFoundation \t 0x7ff81412cd0e __CFRunLoopServiceMachPort + 145\n5 CoreFoundation \t 0x7ff81412b77a __CFRunLoopRun + 1360\n6 CoreFoundation \t 0x7ff81412abb0 CFRunLoopRunSpecific + 560\n7 AppKit \t 0x7ff8173ad696 _NSEventThread + 132\n8 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n9 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108d23ba5 ccl::Session::wait() + 101\n4 Blender \t 0x1081da316 ccl::BlenderSession::render(BL::Depsgraph&) + 3526\n5 Blender \t 0x1081d10e0 ccl::render_func(_object*, _object*) + 176\n6 Blender \t 0x112141552 cfunction_call + 130\n7 Blender \t 0x1120fa1b5 _PyObject_MakeTpCall + 373\n8 Blender \t 0x1121efcce call_function + 974\n9 Blender \t 0x1121eca4a _PyEval_EvalFrameDefault + 30570\n10 Blender \t 0x1121e51b1 _PyEval_Vector + 145\n11 Blender \t 0x1121efaaf call_function + 431\n12 Blender \t 0x1121eca4a _PyEval_EvalFrameDefault + 30570\n13 Blender \t 0x1121e51b1 _PyEval_Vector + 145\n14 Blender \t 0x106f00225 bpy_class_call + 1029\n15 Blender \t 0x106e433d1 engine_render + 113\n16 Blender \t 0x1079cb58c engine_render_view_layer(Render*, RenderEngine*, ViewLayer*, bool, bool) + 572\n17 Blender \t 0x1079cb0ca RE_engine_render + 954\n18 Blender \t 0x1079d097e do_render_full_pipeline(Render*) + 334\n19 Blender \t 0x1079d0566 RE_RenderFrame + 406\n20 Blender \t 0x108178e8f render_startjob(void*, short*, short*, float*) + 127\n21 Blender \t 0x1069f92f8 do_job_thread + 40\n22 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n23 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 34:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 35 Crashed:\n0 libsystem_kernel.dylib \t 0x7ff81401a30e __pthread_kill + 10\n1 libsystem_pthread.dylib \t 0x7ff814051f7b pthread_kill + 263\n2 libsystem_c.dylib \t 0x7ff813f9bd3f __abort + 139\n3 libsystem_c.dylib \t 0x7ff813f9bcb4 abort + 138\n4 libsystem_c.dylib \t 0x7ff813f9afbe __assert_rtn + 314\n5 Metal \t 0x7ff81d6acf32 MTLReportFailure.cold.1 + 43\n6 Metal \t 0x7ff81d687df9 MTLReportFailure + 529\n7 Metal \t 0x7ff81d5913ba -[_MTLCommandBuffer addCompletedHandler:] + 87\n8 Blender \t 0x10827ac38 ccl::MetalDeviceQueue::enqueue(ccl::DeviceKernel, int, ccl::DeviceKernelArguments const&) + 3352\n9 Blender \t 0x108dc338b ccl::ShaderEval::eval_gpu(ccl::Device*, ccl::ShaderEvalType, ccl::device_vector<ccl::KernelShaderEvalInput>&, ccl::device_vector<float>&, long long) + 267\n10 Blender \t 0x108dc2d48 std::__1::__function::__func<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0, std::__1::allocator<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0>, void (ccl::Device*)>::operator()(ccl::Device*&&) + 680\n11 Blender \t 0x10823c8af ccl::Device::foreach_device(std::__1::function<void (ccl::Device*)> const&) + 31\n12 Blender \t 0x108246740 ccl::MultiDevice::foreach_device(std::__1::function<void (ccl::Device*)> const&) + 64\n13 Blender \t 0x108dc296a ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&) + 154\n14 Blender \t 0x108c2a79f ccl::GeometryManager::displace(ccl::Device*, ccl::Scene*, ccl::Mesh*, ccl::Progress&) + 511\n15 Blender \t 0x108bb4769 ccl::GeometryManager::device_update(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&) + 3305\n16 Blender \t 0x108c51111 ccl::Scene::device_update(ccl::Device*, ccl::Progress&) + 1745\n17 Blender \t 0x108c52d73 ccl::Scene::update(ccl::Progress&) + 163\n18 Blender \t 0x108d246e3 ccl::Session::run_update_for_next_iteration() + 1395\n19 Blender \t 0x108d23c74 ccl::Session::run_main_render_loop() + 100\n20 Blender \t 0x108d24c13 ccl::Session::thread_render() + 259\n21 Blender \t 0x108d228c8 ccl::Session::thread_run() + 168\n22 Blender \t 0x10db3e413 ccl::thread::run(void*) + 19\n23 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n24 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 36:\n0 libsystem_pthread.dylib \t 0x7ff81404dc58 start_wqthread + 0\n\nThread 37:\n0 libsystem_pthread.dylib \t 0x7ff81404dc58 start_wqthread + 0\n\nThread 38:\n0 libsystem_pthread.dylib \t 0x7ff81404dc58 start_wqthread + 0\n\nThread 39:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108271985 ccl::ShaderCache::compile_thread_func(int) + 165\n4 Blender \t 0x108274dfd void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*) + 45\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 40:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108271985 ccl::ShaderCache::compile_thread_func(int) + 165\n4 Blender \t 0x108274dfd void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*) + 45\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 41:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108271985 ccl::ShaderCache::compile_thread_func(int) + 165\n4 Blender \t 0x108274dfd void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*) + 45\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 42:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108271985 ccl::ShaderCache::compile_thread_func(int) + 165\n4 Blender \t 0x108274dfd void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*) + 45\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 43:\n0 libsystem_pthread.dylib \t 0x7ff81404dc58 start_wqthread + 0\n\n\nThread 35 crashed with X86 Thread State (64-bit):\n```\nrax: 0x0000000000000000 rbx: 0x000070001368d000 rcx: 0x000070001368a7c8 rdx: 0x0000000000000000\nrdi: 0x000000000002c707 rsi: 0x0000000000000006 rbp: 0x000070001368a7f0 rsp: 0x000070001368a7c8\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x000070001368d000 r11: 0x0000000000000246\nr12: 0x000000000002c707 r13: 0x000000012feea028 r14: 0x0000000000000006 r15: 0x0000000000000016\nrip: 0x00007ff81401a30e rfl: 0x0000000000000246 cr2: 0x000000012feea000\n\n```\nLogical CPU: 0\nError Code: 0x02000148 \nTrap Number: 133\n\n\nBinary Images:\n 0x7ff814012000 - 0x7ff81404bff7 libsystem_kernel.dylib (*) <0c2fd2c9-777c-3355-b70f-7b1b6e9d1b0b> /usr/lib/system/libsystem_kernel.dylib\n 0x7ff813f1a000 - 0x7ff813fa2fff libsystem_c.dylib (*) <5efaf10b-2ec1-32ed-b077-80125e552c8d> /usr/lib/system/libsystem_c.dylib\n 0x1060c2000 - 0x116badfff org.blenderfoundation.blender (3.4.0) <de78ac19-6469-3e44-ab08-627697965862> /Applications/Blender.app/Contents/MacOS/Blender\n 0x7ff813d1b000 - 0x7ff813daf54f dyld (*) <28fd2071-57f3-3873-87bf-e4f674a82de6> /usr/lib/dyld\n 0x7ff813ed0000 - 0x7ff813f16ff3 libdispatch.dylib (*) <817339a1-d03e-3e54-9c47-acacf69f6193> /usr/lib/system/libdispatch.dylib\n 0x7ff81404c000 - 0x7ff814057ff7 libsystem_pthread.dylib (*) <13b5e252-77d1-31e1-888d-1c5f4426ea87> /usr/lib/system/libsystem_pthread.dylib\n 0x7ff81d73d000 - 0x7ff81d762fff com.apple.audio.caulk (1.0) <43ed8c13-59df-3c8d-b4d2-aee44e4939b9> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7ff816060000 - 0x7ff81675affd com.apple.audio.CoreAudio (5.0) <e9f27094-01cb-337a-8530-0cab0e2cc96d> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x136a29000 - 0x13a6b4fff libopenblas64_.0.dylib (*) <10431d8f-5e3b-3bbc-abd5-81f6a73a5269> /Applications/Blender.app/Contents/Resources/3.4/python/lib/python3.10/site-packages/numpy/.dylibs/libopenblas64_.0.dylib\n 0x7ff8140ae000 - 0x7ff814546fff com.apple.CoreFoundation (6.9) <dbc459f3-81bb-398a-8f74-3f7392392bb7> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7ff81720f000 - 0x7ff818213ff6 com.apple.AppKit (6.9) <817d572e-eb8c-3999-b7a0-68e1c4b47266> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7ff813fa3000 - 0x7ff813ffbff3 libc++.1.dylib (*) <06015868-b157-3745-889b-69e23c5034fd> /usr/lib/libc++.1.dylib\n 0x7ff81d570000 - 0x7ff81d73cffb com.apple.Metal (306.2.4) <4ac8bfa1-153f-3c2d-8f98-6831b7c643f8> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n\nExternal Modification Summary:\n```\nCalls made by other processes targeting this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\nCalls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\nCalls made by all processes on this machine:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n```\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\nWritable regions: Total=47.1G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=47.1G(100%)\n\n```\n VIRTUAL REGION \n```\nREGION TYPE SIZE COUNT (non-coalesced) \n**=======**\nAccelerate framework 256K 2 \nActivity Tracing 256K 1 \nCG backing stores 960K 4 \nCG image 228K 14 \nColorSync 228K 25 \nCoreAnimation 64K 14 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreUI image data 636K 9 \nFoundation 16K 1 \nIOAccelerator 12.8G 547 \nIOKit 148K 10 \nIOSurface 58.3M 8 \nKernel Alloc Once 8K 1 \nMALLOC 32.1G 1445 \nMALLOC guard page 48K 9 \nMALLOC_LARGE (reserved) 383.9M 11 reserved VM address space (unallocated)\nMALLOC_MEDIUM (reserved) 496.0M 10 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 176K 44 \nStack 69.8M 44 \nVM_ALLOCATE 158.7M 96 \nVM_ALLOCATE (reserved) 224.0M 3 reserved VM address space (unallocated)\n__CTF 756 1 \n__DATA 59.9M 642 \n__DATA_CONST 51.3M 373 \n__DATA_DIRTY 1753K 211 \n__FONT_DATA 2352 1 \n__GLSLBUILTINS 5174K 1 \n__LINKEDIT 274.5M 70 \n__OBJC_RO 65.1M 1 \n__OBJC_RW 1982K 2 \n__TEXT 989.1M 651 \ndyld private memory 512K 3 \nmapped file 298.9M 95 \nshared memory 447.1M 580 \n**=======**\nTOTAL 48.8G 4936 \nTOTAL, minus reserved VM space 47.4G 4936 \n\n\n\n-----------\nFull Report\n-----------\n\n{\"app_name\":\"Blender\",\"timestamp\":\"2022-12-09 13:00:27.00 +1000\",\"app_version\":\"3.4.0\",\"slice_uuid\":\"de78ac19-6469-3e44-ab08-627697965862\",\"build_version\":\"3.4.0 2022-12-07\",\"platform\":1,\"bundleID\":\"org.blenderfoundation.blender\",\"share_with_app_devs\":0,\"is_first_party\":0,\"bug_type\":\"309\",\"os_version\":\"macOS 13.0.1 (22A400)\",\"roots_installed\":0,\"name\":\"Blender\",\"incident_id\":\"C005C7B8-C72E-4093-B4F1-FAE90C2561DF\"}\n{\n```\n\"uptime\" : 5000,\n\"procRole\" : \"Foreground\",\n\"version\" : 2,\n\"userID\" : 501,\n\"deployVersion\" : 210,\n\"modelCode\" : \"Macmini8,1\",\n\"coalitionID\" : 1400,\n\"osVersion\" : {\n \"train\" : \"macOS 13.0.1\",\n \"build\" : \"22A400\",\n \"releaseType\" : \"User\"\n},\n\"captureTime\" : \"2022-12-09 13:00:26.8303 +1000\",\n\"incident\" : \"C005C7B8-C72E-4093-B4F1-FAE90C2561DF\",\n\"pid\" : 4086,\n\"cpuType\" : \"X86-64\",\n\"roots_installed\" : 0,\n\"bug_type\" : \"309\",\n\"procLaunch\" : \"2022-12-09 12:58:58.0017 +1000\",\n\"procStartAbsTime\" : 4965752889748,\n\"procExitAbsTime\" : 5054490072306,\n\"procName\" : \"Blender\",\n\"procPath\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n\"bundleInfo\" : {\"CFBundleShortVersionString\":\"3.4.0\",\"CFBundleVersion\":\"3.4.0 2022-12-07\",\"CFBundleIdentifier\":\"org.blenderfoundation.blender\"},\n\"storeInfo\" : {\"deviceIdentifierForVendor\":\"94D4C7AA-42A4-5C3F-8C08-A3A0F4499D46\",\"thirdParty\":true},\n\"parentProc\" : \"launchd\",\n\"parentPid\" : 1,\n\"coalitionName\" : \"org.blenderfoundation.blender\",\n\"crashReporterKey\" : \"DA7E5727-A75F-6765-C417-804DFCD4552C\",\n\"bridgeVersion\" : {\"build\":\"20P420\",\"train\":\"7.0\"},\n\"sip\" : \"enabled\",\n\"externalGPUInfo\" : \"ID Vend\\/Dev\\n8488 73bf1002\\nSeconds Ago ID Type\\n 5000.0 8488 Attach\\n\",\n\"exception\" : {\"codes\":\"0x0000000000000000, 0x0000000000000000\",\"rawCodes\":[0,0],\"type\":\"EXC_CRASH\",\"signal\":\"SIGABRT\"},\n\"extMods\" : {\"caller\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"system\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"targeted\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"warnings\":0},\n\"faultingThread\" : 35,\n\"threads\" : [{\"id\":64792,\"queue\":\"com.apple.main-thread\",\"frames\":[{\"imageOffset\":16590,\"symbol\":\"__semwait_signal\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":68426,\"symbol\":\"nanosleep\",\"symbolLocation\":196,\"imageIndex\":1},{\"imageOffset\":68224,\"symbol\":\"usleep\",\"symbolLocation\":53,\"imageIndex\":1},{\"imageOffset\":9550120,\"symbol\":\"WM_main\",\"symbolLocation\":24,\"imageIndex\":2},{\"imageOffset\":1706894,\"symbol\":\"main\",\"symbolLocation\":878,\"imageIndex\":2},{\"imageOffset\":25360,\"symbol\":\"start\",\"symbolLocation\":2432,\"imageIndex\":3}]},{\"id\":64803,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64804,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64805,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64806,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64807,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64808,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64809,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64810,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64811,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64812,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64813,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64814,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64817,\"name\":\"caulk.messenger.shared:17\",\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":116984,\"symbol\":\"caulk::mach::semaphore::wait_or_error()\",\"symbolLocation\":16,\"imageIndex\":6},{\"imageOffset\":9828,\"symbol\":\"caulk::concurrent::details::worker_thread::run()\",\"symbolLocation\":36,\"imageIndex\":6},{\"imageOffset\":9000,\"symbol\":\"void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*)\",\"symbolLocation\":41,\"imageIndex\":6},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64872,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64873,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64874,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64875,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64876,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64877,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64878,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64879,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64880,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64881,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64882,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64883,\"name\":\"com.apple.audio.IOThread.client\",\"frames\":[{\"imageOffset\":5794,\"symbol\":\"mach_msg2_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":63101,\"symbol\":\"mach_msg2_internal\",\"symbolLocation\":82,\"imageIndex\":0},{\"imageOffset\":34586,\"symbol\":\"mach_msg_overwrite\",\"symbolLocation\":723,\"imageIndex\":0},{\"imageOffset\":6537,\"symbol\":\"mach_msg\",\"symbolLocation\":19,\"imageIndex\":0},{\"imageOffset\":3143845,\"symbol\":\"HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int)\",\"symbolLocation\":111,\"imageIndex\":7},{\"imageOffset\":1934529,\"symbol\":\"HALC_ProxyIOContext::IOWorkLoop()\",\"symbolLocation\":3783,\"imageIndex\":7},{\"imageOffset\":1929257,\"symbol\":\"invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int)\",\"symbolLocation\":63,\"imageIndex\":7},{\"imageOffset\":3532336,\"symbol\":\"HALB_IOThread::Entry(void*)\",\"symbolLocation\":72,\"imageIndex\":7},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64909,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64910,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64911,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64912,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64913,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64992,\"name\":\"com.apple.NSEventThread\",\"frames\":[{\"imageOffset\":5794,\"symbol\":\"mach_msg2_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":63101,\"symbol\":\"mach_msg2_internal\",\"symbolLocation\":82,\"imageIndex\":0},{\"imageOffset\":34586,\"symbol\":\"mach_msg_overwrite\",\"symbolLocation\":723,\"imageIndex\":0},{\"imageOffset\":6537,\"symbol\":\"mach_msg\",\"symbolLocation\":19,\"imageIndex\":0},{\"imageOffset\":519438,\"symbol\":\"__CFRunLoopServiceMachPort\",\"symbolLocation\":145,\"imageIndex\":9},{\"imageOffset\":513914,\"symbol\":\"__CFRunLoopRun\",\"symbolLocation\":1360,\"imageIndex\":9},{\"imageOffset\":510896,\"symbol\":\"CFRunLoopRunSpecific\",\"symbolLocation\":560,\"imageIndex\":9},{\"imageOffset\":1697430,\"symbol\":\"_NSEventThread\",\"symbolLocation\":132,\"imageIndex\":10},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65215,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":46537637,\"symbol\":\"ccl::Session::wait()\",\"symbolLocation\":101,\"imageIndex\":2},{\"imageOffset\":34702102,\"symbol\":\"ccl::BlenderSession::render(BL::Depsgraph&)\",\"symbolLocation\":3526,\"imageIndex\":2},{\"imageOffset\":34664672,\"symbol\":\"ccl::render_func(_object*, _object*)\",\"symbolLocation\":176,\"imageIndex\":2},{\"imageOffset\":201848146,\"symbol\":\"cfunction_call\",\"symbolLocation\":130,\"imageIndex\":2},{\"imageOffset\":201556405,\"symbol\":\"_PyObject_MakeTpCall\",\"symbolLocation\":373,\"imageIndex\":2},{\"imageOffset\":202562766,\"symbol\":\"call_function\",\"symbolLocation\":974,\"imageIndex\":2},{\"imageOffset\":202549834,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30570,\"imageIndex\":2},{\"imageOffset\":202518961,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":2},{\"imageOffset\":202562223,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":2},{\"imageOffset\":202549834,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30570,\"imageIndex\":2},{\"imageOffset\":202518961,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":2},{\"imageOffset\":14934565,\"symbol\":\"bpy_class_call\",\"symbolLocation\":1029,\"imageIndex\":2},{\"imageOffset\":14160849,\"symbol\":\"engine_render\",\"symbolLocation\":113,\"imageIndex\":2},{\"imageOffset\":26252684,\"symbol\":\"engine_render_view_layer(Render*, RenderEngine*, ViewLayer*, bool, bool)\",\"symbolLocation\":572,\"imageIndex\":2},{\"imageOffset\":26251466,\"symbol\":\"RE_engine_render\",\"symbolLocation\":954,\"imageIndex\":2},{\"imageOffset\":26274174,\"symbol\":\"do_render_full_pipeline(Render*)\",\"symbolLocation\":334,\"imageIndex\":2},{\"imageOffset\":26273126,\"symbol\":\"RE_RenderFrame\",\"symbolLocation\":406,\"imageIndex\":2},{\"imageOffset\":34303631,\"symbol\":\"render_startjob(void*, short*, short*, float*)\",\"symbolLocation\":127,\"imageIndex\":2},{\"imageOffset\":9663224,\"symbol\":\"do_job_thread\",\"symbolLocation\":40,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65354,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65355,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"triggered\":true,\"id\":65357,\"threadState\":{\"r13\":{\"value\":5099135016},\"rax\":{\"value\":0},\"rflags\":{\"value\":582},\"cpu\":{\"value\":0},\"r14\":{\"value\":6},\"rsi\":{\"value\":6},\"r8\":{\"value\":0},\"cr2\":{\"value\":5099134976},\"rdx\":{\"value\":0},\"r10\":{\"value\":123145627947008},\"r9\":{\"value\":10000000},\"r15\":{\"value\":22},\"rbx\":{\"value\":123145627947008},\"trap\":{\"value\":133},\"err\":{\"value\":33554760},\"r11\":{\"value\":582},\"rip\":{\"value\":140703464268558,\"matchesCrashFrame\":1},\"rbp\":{\"value\":123145627936752},\"rsp\":{\"value\":123145627936712},\"r12\":{\"value\":182023},\"rcx\":{\"value\":123145627936712},\"flavor\":\"x86_THREAD_STATE\",\"rdi\":{\"value\":182023}},\"frames\":[{\"imageOffset\":33550,\"symbol\":\"__pthread_kill\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":24443,\"symbol\":\"pthread_kill\",\"symbolLocation\":263,\"imageIndex\":5},{\"imageOffset\":531775,\"symbol\":\"__abort\",\"symbolLocation\":139,\"imageIndex\":1},{\"imageOffset\":531636,\"symbol\":\"abort\",\"symbolLocation\":138,\"imageIndex\":1},{\"imageOffset\":528318,\"symbol\":\"__assert_rtn\",\"symbolLocation\":314,\"imageIndex\":1},{\"imageOffset\":1298226,\"symbol\":\"MTLReportFailure.cold.1\",\"symbolLocation\":43,\"imageIndex\":12},{\"imageOffset\":1146361,\"symbol\":\"MTLReportFailure\",\"symbolLocation\":529,\"imageIndex\":12},{\"imageOffset\":136122,\"symbol\":\"-[_MTLCommandBuffer addCompletedHandler:]\",\"symbolLocation\":87,\"imageIndex\":12},{\"imageOffset\":35359800,\"symbol\":\"ccl::MetalDeviceQueue::enqueue(ccl::DeviceKernel, int, ccl::DeviceKernelArguments const&)\",\"symbolLocation\":3352,\"imageIndex\":2},{\"imageOffset\":47190923,\"symbol\":\"ccl::ShaderEval::eval_gpu(ccl::Device*, ccl::ShaderEvalType, ccl::device_vector<ccl::KernelShaderEvalInput>&, ccl::device_vector<float>&, long long)\",\"symbolLocation\":267,\"imageIndex\":2},{\"imageOffset\":47189320,\"symbol\":\"std::__1::__function::__func<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0, std::__1::allocator<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0>, void (ccl::Device*)>::operator()(ccl::Device*&&)\",\"symbolLocation\":680,\"imageIndex\":2},{\"imageOffset\":35104943,\"symbol\":\"ccl::Device::foreach_device(std::__1::function<void (ccl::Device*)> const&)\",\"symbolLocation\":31,\"imageIndex\":2},{\"imageOffset\":35145536,\"symbol\":\"ccl::MultiDevice::foreach_device(std::__1::function<void (ccl::Device*)> const&)\",\"symbolLocation\":64,\"imageIndex\":2},{\"imageOffset\":47188330,\"symbol\":\"ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)\",\"symbolLocation\":154,\"imageIndex\":2},{\"imageOffset\":45516703,\"symbol\":\"ccl::GeometryManager::displace(ccl::Device*, ccl::Scene*, ccl::Mesh*, ccl::Progress&)\",\"symbolLocation\":511,\"imageIndex\":2},{\"imageOffset\":45033321,\"symbol\":\"ccl::GeometryManager::device_update(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&)\",\"symbolLocation\":3305,\"imageIndex\":2},{\"imageOffset\":45674769,\"symbol\":\"ccl::Scene::device_update(ccl::Device*, ccl::Progress&)\",\"symbolLocation\":1745,\"imageIndex\":2},{\"imageOffset\":45682035,\"symbol\":\"ccl::Scene::update(ccl::Progress&)\",\"symbolLocation\":163,\"imageIndex\":2},{\"imageOffset\":46540515,\"symbol\":\"ccl::Session::run_update_for_next_iteration()\",\"symbolLocation\":1395,\"imageIndex\":2},{\"imageOffset\":46537844,\"symbol\":\"ccl::Session::run_main_render_loop()\",\"symbolLocation\":100,\"imageIndex\":2},{\"imageOffset\":46541843,\"symbol\":\"ccl::Session::thread_render()\",\"symbolLocation\":259,\"imageIndex\":2},{\"imageOffset\":46532808,\"symbol\":\"ccl::Session::thread_run()\",\"symbolLocation\":168,\"imageIndex\":2},{\"imageOffset\":128435219,\"symbol\":\"ccl::thread::run(void*)\",\"symbolLocation\":19,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65398,\"frames\":[{\"imageOffset\":7256,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":5}]},{\"id\":65417,\"frames\":[{\"imageOffset\":7256,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":5}]},{\"id\":65494,\"frames\":[{\"imageOffset\":7256,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":5}]},{\"id\":65525,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":35322245,\"symbol\":\"ccl::ShaderCache::compile_thread_func(int)\",\"symbolLocation\":165,\"imageIndex\":2},{\"imageOffset\":35335677,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*)\",\"symbolLocation\":45,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65526,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":35322245,\"symbol\":\"ccl::ShaderCache::compile_thread_func(int)\",\"symbolLocation\":165,\"imageIndex\":2},{\"imageOffset\":35335677,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*)\",\"symbolLocation\":45,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65529,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":35322245,\"symbol\":\"ccl::ShaderCache::compile_thread_func(int)\",\"symbolLocation\":165,\"imageIndex\":2},{\"imageOffset\":35335677,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*)\",\"symbolLocation\":45,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65530,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":35322245,\"symbol\":\"ccl::ShaderCache::compile_thread_func(int)\",\"symbolLocation\":165,\"imageIndex\":2},{\"imageOffset\":35335677,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*)\",\"symbolLocation\":45,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65535,\"frames\":[{\"imageOffset\":7256,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":5}]}],\n\"usedImages\" : [\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703464235008,\n \"size\" : 237560,\n \"uuid\" : \"0c2fd2c9-777c-3355-b70f-7b1b6e9d1b0b\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_kernel.dylib\",\n \"name\" : \"libsystem_kernel.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703463219200,\n \"size\" : 561152,\n \"uuid\" : \"5efaf10b-2ec1-32ed-b077-80125e552c8d\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_c.dylib\",\n \"name\" : \"libsystem_c.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4396425216,\n \"CFBundleShortVersionString\" : \"3.4.0\",\n \"CFBundleIdentifier\" : \"org.blenderfoundation.blender\",\n \"size\" : 279887872,\n \"uuid\" : \"de78ac19-6469-3e44-ab08-627697965862\",\n \"path\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n \"name\" : \"Blender\",\n \"CFBundleVersion\" : \"3.4.0 2022-12-07\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703461126144,\n \"size\" : 607568,\n \"uuid\" : \"28fd2071-57f3-3873-87bf-e4f674a82de6\",\n \"path\" : \"\\/usr\\/lib\\/dyld\",\n \"name\" : \"dyld\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703462916096,\n \"size\" : 290804,\n \"uuid\" : \"817339a1-d03e-3e54-9c47-acacf69f6193\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libdispatch.dylib\",\n \"name\" : \"libdispatch.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703464472576,\n \"size\" : 49144,\n \"uuid\" : \"13b5e252-77d1-31e1-888d-1c5f4426ea87\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_pthread.dylib\",\n \"name\" : \"libsystem_pthread.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703622746112,\n \"CFBundleShortVersionString\" : \"1.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.caulk\",\n \"size\" : 155648,\n \"uuid\" : \"43ed8c13-59df-3c8d-b4d2-aee44e4939b9\",\n \"path\" : \"\\/System\\/Library\\/PrivateFrameworks\\/caulk.framework\\/Versions\\/A\\/caulk\",\n \"name\" : \"caulk\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703498108928,\n \"CFBundleShortVersionString\" : \"5.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.CoreAudio\",\n \"size\" : 7319550,\n \"uuid\" : \"e9f27094-01cb-337a-8530-0cab0e2cc96d\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreAudio.framework\\/Versions\\/A\\/CoreAudio\",\n \"name\" : \"CoreAudio\",\n \"CFBundleVersion\" : \"5.0\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 5211590656,\n \"size\" : 63488000,\n \"uuid\" : \"10431d8f-5e3b-3bbc-abd5-81f6a73a5269\",\n \"path\" : \"\\/Applications\\/Blender.app\\/Contents\\/Resources\\/3.4\\/python\\/lib\\/python3.10\\/site-packages\\/numpy\\/.dylibs\\/libopenblas64_.0.dylib\",\n \"name\" : \"libopenblas64_.0.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64h\",\n \"base\" : 140703464873984,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.CoreFoundation\",\n \"size\" : 4820992,\n \"uuid\" : \"dbc459f3-81bb-398a-8f74-3f7392392bb7\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreFoundation.framework\\/Versions\\/A\\/CoreFoundation\",\n \"name\" : \"CoreFoundation\",\n \"CFBundleVersion\" : \"1953.1\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703516651520,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.AppKit\",\n \"size\" : 16797687,\n \"uuid\" : \"817d572e-eb8c-3999-b7a0-68e1c4b47266\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/AppKit.framework\\/Versions\\/C\\/AppKit\",\n \"name\" : \"AppKit\",\n \"CFBundleVersion\" : \"2299\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703463780352,\n \"size\" : 364532,\n \"uuid\" : \"06015868-b157-3745-889b-69e23c5034fd\",\n \"path\" : \"\\/usr\\/lib\\/libc++.1.dylib\",\n \"name\" : \"libc++.1.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703620857856,\n \"CFBundleShortVersionString\" : \"306.2.4\",\n \"CFBundleIdentifier\" : \"com.apple.Metal\",\n \"size\" : 1888252,\n \"uuid\" : \"4ac8bfa1-153f-3c2d-8f98-6831b7c643f8\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/Metal.framework\\/Versions\\/A\\/Metal\",\n \"name\" : \"Metal\",\n \"CFBundleVersion\" : \"306.2.4\"\n}\n```\n],\n```\n\"sharedCache\" : {\n\"base\" : 140703460519936,\n\"size\" : 21474836480,\n\"uuid\" : \"840e528a-0c70-3c6a-b7b4-4f05f32ccc51\"\n```\n},\n```\n\"vmSummary\" : \"ReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\\nWritable regions: Total=47.1G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=47.1G(100%)\\n\\n VIRTUAL REGION \\nREGION TYPE SIZE COUNT (non-coalesced) \\n=========== ======= ======= \\nAccelerate framework 256K 2 \\nActivity Tracing 256K 1 \\nCG backing stores 960K 4 \\nCG image 228K 14 \\nColorSync 228K 25 \\nCoreAnimation 64K 14 \\nCoreGraphics 12K 2 \\nCoreImage 4K 1 \\nCoreUI image data 636K 9 \\nFoundation 16K 1 \\nIOAccelerator 12.8G 547 \\nIOKit 148K 10 \\nIOSurface 58.3M 8 \\nKernel Alloc Once 8K 1 \\nMALLOC 32.1G 1445 \\nMALLOC guard page 48K 9 \\nMALLOC_LARGE (reserved) 383.9M 11 reserved VM address space (unallocated)\\nMALLOC_MEDIUM (reserved) 496.0M 10 reserved VM address space (unallocated)\\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\\nOpenGL GLSL 256K 3 \\nSTACK GUARD 176K 44 \\nStack 69.8M 44 \\nVM_ALLOCATE 158.7M 96 \\nVM_ALLOCATE (reserved) 224.0M 3 reserved VM address space (unallocated)\\n__CTF 756 1 \\n__DATA 59.9M 642 \\n__DATA_CONST 51.3M 373 \\n__DATA_DIRTY 1753K 211 \\n__FONT_DATA 2352 1 \\n__GLSLBUILTINS 5174K 1 \\n__LINKEDIT 274.5M 70 \\n__OBJC_RO 65.1M 1 \\n__OBJC_RW 1982K 2 \\n__TEXT 989.1M 651 \\ndyld private memory 512K 3 \\nmapped file 298.9M 95 \\nshared memory 447.1M 580 \\n=========== ======= ======= \\nTOTAL 48.8G 4936 \\nTOTAL, minus reserved VM space 47.4G 4936 \\n\",\n\"legacyInfo\" : {\n\"threadTriggered\" : {\n```\n\n```\n}\n```\n},\n```\n\"trialInfo\" : {\n\"rollouts\" : [\n {\n \"rolloutId\" : \"5fb4245a1bbfe8005e33a1e1\",\n \"factorPackIds\" : {\n```\n\n```\n },\n \"deploymentId\" : 240000021\n },\n {\n \"rolloutId\" : \"62b4513af75dc926494899c6\",\n \"factorPackIds\" : {\n \"COREOS_ICD\" : \"62fbe3cfa9a700130f60b3ea\"\n },\n \"deploymentId\" : 240000014\n }\n],\n\"experiments\" : [\n```\n\n```\n]\n```\n}\n}\n\nModel: Macmini8,1, BootROM 1916.40.8.0.0 (iBridge: 20.16.420.0.0,0), 6 processors, 6-Core Intel Core i7, 3.2 GHz, 32 GB, SMC \nGraphics: Intel UHD Graphics 630, Intel UHD Graphics 630, Built-In\nDisplay: ASUS VG32V, 2560 x 1440 (QHD/WQHD - Wide Quad High Definition), Main, MirrorOff, Online\nGraphics: AMD Radeon RX 6800, AMD Radeon RX 6800, PCIe, 16 GB\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, HMA82GS6CJR8N-VK\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, HMA82GS6CJR8N-VK\nAirPort: spairport_wireless_card_type_wifi (0x14E4, 0x7BF), wl0: Sep 14 2022 18:10:05 version 9.30.489.3.32.5.84 FWID 01-31bf0e8d\nBluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports\nNetwork Service: Ethernet, Ethernet, en0\nNetwork Service: Wi-Fi, AirPort, en1\nPCI Card: pci8086,15f0, USB eXtensible Host Controller, Thunderbolt@13,0,0\nPCI Card: pci144d,a808, NVM Express Controller, Thunderbolt@73,0,0\nPCI Card: AMD Radeon RX 6800, gpu-controller, Thunderbolt@12,0,0\nPCI Card: pci1002,ab28, Audio Device, Thunderbolt@12,0,1\nPCI Card: pci1002,73a6, USB eXtensible Host Controller, Thunderbolt@12,0,2\nPCI Card: pci1002,73a4, Unknown, Thunderbolt@12,0,3\nUSB Device: USB31Bus\nUSB Device: USB31Bus\nUSB Device: USB3.1 Hub\nUSB Device: USB3.1 Hub\nUSB Device: USB2.0 Hub\nUSB Device: Microsoft® LifeCam HD-3000\nUSB Device: USB2.0 Hub\nUSB Device: Matias RGB Backlit Wired Keyboard\nUSB Device: USB2.1 Hub\nUSB Device: USB Storage\nUSB Device: Dell MS116 USB Optical Mouse\nUSB Device: T2Bus\nUSB Device: Headset\nUSB Device: Apple #2 Controller\nThunderbolt Bus: Mac mini, Apple Inc., 47.5\nThunderbolt Device: Node Titan, AKiTiO, 1, 50.1\nThunderbolt Device: Portable SSD X5, SAMSUNG ELECTRONICS CO., LTD, 3, 35.1\nThunderbolt Bus: Mac mini, Apple Inc., 47.5\n```\n\nCrashing Thread:\n```\nThread 35 Crashed:\n0 libsystem_kernel.dylib \t 0x7ff81401a30e __pthread_kill + 10\n1 libsystem_pthread.dylib \t 0x7ff814051f7b pthread_kill + 263\n2 libsystem_c.dylib \t 0x7ff813f9bd3f __abort + 139\n3 libsystem_c.dylib \t 0x7ff813f9bcb4 abort + 138\n4 libsystem_c.dylib \t 0x7ff813f9afbe __assert_rtn + 314\n5 Metal \t 0x7ff81d6acf32 MTLReportFailure.cold.1 + 43\n6 Metal \t 0x7ff81d687df9 MTLReportFailure + 529\n7 Metal \t 0x7ff81d5913ba -[_MTLCommandBuffer addCompletedHandler:] + 87\n8 Blender \t 0x10827ac38 ccl::MetalDeviceQueue::enqueue(ccl::DeviceKernel, int, ccl::DeviceKernelArguments const&) + 3352\n9 Blender \t 0x108dc338b ccl::ShaderEval::eval_gpu(ccl::Device*, ccl::ShaderEvalType, ccl::device_vector<ccl::KernelShaderEvalInput>&, ccl::device_vector<float>&, long long) + 267\n10 Blender \t 0x108dc2d48 std::__1::__function::__func<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0, std::__1::allocator<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0>, void (ccl::Device*)>::operator()(ccl::Device*&&) + 680\n11 Blender \t 0x10823c8af ccl::Device::foreach_device(std::__1::function<void (ccl::Device*)> const&) + 31\n12 Blender \t 0x108246740 ccl::MultiDevice::foreach_device(std::__1::function<void (ccl::Device*)> const&) + 64\n13 Blender \t 0x108dc296a ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&) + 154\n14 Blender \t 0x108c2a79f ccl::GeometryManager::displace(ccl::Device*, ccl::Scene*, ccl::Mesh*, ccl::Progress&) + 511\n15 Blender \t 0x108bb4769 ccl::GeometryManager::device_update(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&) + 3305\n16 Blender \t 0x108c51111 ccl::Scene::device_update(ccl::Device*, ccl::Progress&) + 1745\n17 Blender \t 0x108c52d73 ccl::Scene::update(ccl::Progress&) + 163\n18 Blender \t 0x108d246e3 ccl::Session::run_update_for_next_iteration() + 1395\n19 Blender \t 0x108d23c74 ccl::Session::run_main_render_loop() + 100\n20 Blender \t 0x108d24c13 ccl::Session::thread_render() + 259\n21 Blender \t 0x108d228c8 ccl::Session::thread_run() + 168\n22 Blender \t 0x10db3e413 ccl::thread::run(void*) + 19\n23 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n24 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n```", "2.9.1 Close without error message\nOperating system: Windows 10, 10gb ram, ssd\nGraphics card: Nvidia GTX 650 1gb vram\n\nBroken: (2.83 LTE and 2.90 current available version)\nWorked: (2.82)\n\nWhen rendering with GPU AND CPU, the app crashes, works perfectly fine on CPU only. On GPU only too but slower than older versions.\n\n\n```\nblender.exe :0x00007FF7A5B76440 ccl::kernel_cpu_sse41_filter_finalize\nblender.exe :0x00007FF7A57A9220 ccl::CPUDevice::denoising_solve\nblender.exe :0x00007FF7A57DA470 ccl::DenoisingTask::reconstruct\nblender.exe :0x00007FF7A57D8ED0 ccl::DenoisingTask::run_denoising\nblender.exe :0x00007FF7A57A7240 ccl::CPUDevice::denoise_nlm\nblender.exe :0x00007FF7A57AB590 ccl::CPUDevice::thread_render\nblender.exe :0x00007FF7A57ABA30 ccl::CPUDevice::thread_run\nblender.exe :0x00007FF7A57A60B0 ?_Do_call@?$_Func_impl_no_alloc@V<lambda_d884e08a7877f415f05ce8ffda8f97b4>@@X$$V@std@@EEAAXXZ\nblender.exe :0x00007FF7A7D5F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5EF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFBF5EFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFC08611FA0 o_exp\nKERNEL32.DLL :0x00007FFC0B647960 BaseThreadInitThunk\nntdll.dll :0x00007FFC0B7AA250 RtlUserThreadStart\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Crash guide during render complete August 29, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.44\n\nBroken: version: 3.3.0 Beta\n\nBlender 3.3 Beta crash guide during render August 29, 2022\n\n\nNot matter all version 3.0 to 3.4 keep me crash. Do not use Windows. Only for Macintosh.\n\n\n\n[Blender-2022-08-29-092340.ips](Blender-2022-08-29-092340.ips)\n\n[Armor wear 1.0.0.blend](Armor_wear_1.0.0.blend)\n\n\n\nT100328\n@Nurb2Kea\nRender 600 (complete render cause crash guide)\n", "use-after-free crash after setting scene's render.engine inside custom render engine context\nOperating system: Ubuntu 20.04.2LTS\n\nBroken: 2.93.0 Beta, branch: master, commit date: 2021-05-19 10:14, hash: a294670bacb1, type: release\nAlso Broken: 0efb627bbd3ac3e53afb95591ae4e244bd1f8af4\n\nBlender crashes when setting some scene's render.engine property inside `__init__` or the `view_update` context of a custom render engine to a different one than the custom engine.\n\n[T88404_asan_report.txt](T88404_asan_report.txt)\n**Code to reproduce the error**\n```\nimport bpy\nimport bgl\n\nclass CustomRenderEngine(bpy.types.RenderEngine):\n bl_idname = \"CUSTOM\"\n bl_label = \"Custom\"\n bl_use_preview = True\n \n def __init__(self):\n return\n scene = bpy.data.scenes.new(\"foo\")\n scene.render.engine = \"CYCLES\"\n bpy.data.scenes.remove(scene)\n\n def __del__(self):\n pass\n\n def view_update(self, context, depsgraph):\n scene = bpy.data.scenes.new(\"foo\")\n scene.render.engine = \"CYCLES\"\n bpy.data.scenes.remove(scene)\n\n def view_draw(self, context, depsgraph):\n pass\n\ndef get_panels():\n exclude_panels = {\n 'VIEWLAYER_PT_filter',\n 'VIEWLAYER_PT_layer_passes',\n }\n\n panels = []\n for panel in bpy.types.Panel.__subclasses__():\n if hasattr(panel, 'COMPAT_ENGINES') and 'BLENDER_RENDER' in panel.COMPAT_ENGINES:\n if panel.__name__ not in exclude_panels:\n panels.append(panel)\n\n return panels\n\n\ndef register():\n bpy.utils.register_class(CustomRenderEngine)\n\n for panel in get_panels():\n panel.COMPAT_ENGINES.add('CUSTOM')\n\n\ndef unregister():\n bpy.utils.unregister_class(CustomRenderEngine)\n\n for panel in get_panels():\n if 'CUSTOM' in panel.COMPAT_ENGINES:\n panel.COMPAT_ENGINES.remove('CUSTOM')\n\nif __name__ == \"__main__\":\n register()\n```\n\n1) Copy code from above into a new script file inside of Blender\n2) Run the script\n3) Select \"Custom\" as Render Engine inside Render Properties\n4) Select \"Material Preview\" as display method in the viewport.\n\n[crash.blend](crash.blend)\n\nCrash log:\n```\n# Blender 2.93.0, Commit date: 2021-05-19 10:14, Hash a294670bacb1\nEngine 'CUSTOM' not available for scene 'Scene' (an add-on may need to be installed or enabled) # Error\nbpy.ops.text.run_script() # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xa63c950]\n./blender() [0xf6082a]\n/lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f7ce17be210]\n./blender(GPU_framebuffer_blit+0x2f) [0x8664faf]\n./blender() [0x1485fc3]\n./blender() [0x14597fe]\n./blender(DRW_draw_render_loop_ex+0x242) [0x1459a72]\n./blender(view3d_main_region_draw+0x8f) [0x1d3570f]\n./blender(ED_region_do_draw+0x851) [0x189c771]\n./blender(wm_draw_update+0x52e) [0x130cc9e]\n./blender(WM_main+0x30) [0x130aa20]\n./blender(main+0x319) [0xe881c9]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f7ce179f0b3]\n./blender() [0xf5d1bc]\n\n# Python backtrace\n```", "The program crashes when texturing \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nWhen try texture object in texture paint mode, and there are another map in shader tab. Program crashes. \n\n1. In default (or other) scene go to Texture paint window, create new texture for paint. \n2. Apply this texture to diffuse color object in shader editor. (or in object properties)\n3. Go back to texture window. We make sure that everything is painted correctly\n4. Go to shading window and drag&drop any other texture to node window. (NOT APPLY TO DIFFUSE COLOR (or APPLY))\n5. Go back to texture paint window. For some reason, the dragged texture itself was assigned to the duffuse color.\n6. Change linced texture in image editor (in left window)\n7. Try paint on RIGHT window (3D viewport)\n8. Click on left texture editor (try paint in 2D ) program crash. \n\nVideo steps: 0Ophy4Lmx0A\n\nDebug logs:\n[blender.crash.txt](blender.crash.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Blender_crash.webm](Blender_crash.webm)\n\n", "Cycles freeze on render and texture baking (with packed textures)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.83\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nBlender freezes on render\nBlender also freezes on texture bake and rendered viewport\nTried on 3 different PCs, all the same\n\nIf textures are unpacked, rendering is fine.\n\nSimply open attached .blend file and hit F12\n\n[render_test2b_delmesh3_simplified.blend](render_test2b_delmesh3_simplified.blend)", "crash when changing viewport shading to wireframe mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14760 Core Profile Context 21.2.3 27.20.14535.3005\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-04-23 20:25, hash: 17fca62fff9b, type: Release\nBroken: 2.81\nWorked: 2.80\n\n\nif you have a high poly mesh and try change the shading mode to wireframe. depending on the model it constantly crashes.\n\n\nI noticed this trying to make a retopo of a character. I tried to check what was causing de crash by deleting each object and testing the wireframe. \n\nI deleted everything but the main body mesh, without any uv map, vertex color or any other thing that could make it heavier, and also I tried reseting factory settings.\n\nI would send the file but its 200mb, the main mesh has about 4million vertices.\n\n\nthe crash doesn't happen when changing to eevee or solid view, it only happens when changing to wireframe.\n\nImportant note: if you DON'T move the camera after opening the file before changing to wireframe it doesn't crash even if you go to solid and wireframe back and forth as shown in the video bellow \n[2021-05-01 14-18-16.mp4](2021-05-01_14-18-16.mp4)\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[untitled.blend](untitled.blend)\n- open the file above\n- rotate it about 180degrees\n- activate wireframe", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Curve / Geometry / Bevel Objects don't accept Mirror Curve\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\n[i try to use a curve with mirror modifier, to use it as Bevel Object in ObjectDataProperties Curve. Now i see the half , it miss the modifier]\n\nCreate curve with mirror modifier, add it to new curve inside ObjectDataProperties Bevel Objet\n[CurveBevelMirror.blend](CurveBevelMirror.blend)\n\n", "Sporadic boolean issues\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.2.0\nWorked: 3.0\n\nMeshes using the boolean modifier sporadically break in Blender 3.2.0, while they still worked in 3.0.\nThis would result in meshes that lack faces or even crash Blender\n\n\nUnfortunately I wasn't able to isolate the cause of the issue, as it seems to occur sporadically and randomly. What I have noticed is that sometimes meshes that were fine suddenly break once you enter exit edit mode.\n\n", "Custom Normals Render Artifact in Cycles \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.99\n\nBroken: version: 3.0.1\nWorked: Unknown\n\nWhen rendering a cube with custom normals in cycles the render result in cycles has artifacts. This is an issue for us because we also use cycles to bake Ambient Occlusion data to the vertex colors. Those artifacts are than also visible in the vertex colors. The same artifact occurs in previous versions of blender aswell (LTS Blender 2.93.7)\n\n\nBased on startup file:\n\n- Shade the default cube smooth\n- Apply Normals Auto Smooth\n- Add a single bevel using a bevel modifyer and apply it\n- Add a Weighted normal modifyer with weight 100 to the cube and appy it aswell\n# Render in cycles and behold render artifacts near the beveled edges\n\n[custom-normals-cycles.blend](custom-normals-cycles.blend)\n\n\n", "Crash going to material preview or rendered shading mode Blender 2.83.0\nMacBook Pro 15 inch Early 2013\n2.7 GHz Intel Core i&\n16 GB 1600 Mhz DDR3\n|Operating system:|MacOS 10.12.5 - @Tramfabriek\n| -- | -- |\n||Mac OS X 10.12.6 (16G2136) - @johan-eds\n|| macOS 10.12.6 - @UmbertoOldani\n\n|Graphics card:|NVIDIA GeForce GT 650M 1024 MB + Intel HD Graphics 4000 1536 MB - @Tramfabriek\n| -- | -- |\n||NVIDIA GeForce GTX 775M, PCIe, 2048 MB - @johan-eds\n|| NVIDIA GeForce GTX 680MX 2048 MB - @UmbertoOldani\n\nBisected to find the bad commit: 804e90b42d\n\nCrash when clicking on Viewport Shading >Material Preview or >Rendered\nThis did happen already in the 2.83 betas, but none of the 2.82 and earlier version had this problem on this computer running this same OS at least since Blender 2.79.\n\n**System crash report 1** (crash in `UI_draw_roundbox_aa` -> `GPU_batch_draw `. Probably the material render icon):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff909add42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff90a9b457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff909134bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff9091342f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff88cdbfbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff76297390 0x7fff7607a000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff88cdd524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff76385867 0x7fff7607a000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff763554fd 0x7fff7607a000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff76282a2b 0x7fff7607a000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff7626ee9a 0x7fff7607a000 + 2051738\n11 com.apple.GeForceGLDriver \t0x00007fff76289654 0x7fff7607a000 + 2160212\n12 com.apple.GeForceGLDriver \t0x00007fff7626af97 0x7fff7607a000 + 2035607\n13 com.apple.GeForceGLDriver \t0x00007fff763851ad gldUpdateDispatch + 1041\n14 GLEngine \t0x00007fff7ff1d32a gleDoDrawDispatchCoreGL3 + 520\n15 GLEngine \t0x00007fff7fecebd9 gleDrawArraysOrElements_Entries_Body + 128\n16 GLEngine \t0x00007fff7fecaab4 glDrawArraysInstanced_GL3Exec + 220\n17 org.blenderfoundation.blender \t0x0000000109614f2c GPU_batch_draw_advanced + 428\n18 org.blenderfoundation.blender \t0x0000000109614d6c GPU_batch_draw + 124\n19 org.blenderfoundation.blender \t0x0000000105218c51 UI_draw_roundbox_aa + 353\n20 org.blenderfoundation.blender \t0x0000000104f3d96c ED_region_do_draw + 1372\n21 org.blenderfoundation.blender \t0x0000000104b6d49c wm_draw_update + 2092\n22 org.blenderfoundation.blender \t0x0000000104b6b010 WM_main + 48\n23 org.blenderfoundation.blender \t0x0000000104827762 main + 962\n24 libdyld.dylib \t0x00007fff9087f235 start + 1\n\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5b521f78 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff5b521fa0 rsp: 0x00007fff5b521f78\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x000000011ab85cf8 r13: 0x0000000000000000 r14: 0x00007fff998033c0 r15: 0x000000011ab85000\n rip: 0x00007fff909add42 rfl: 0x0000000000000206 cr2: 0x00007fff960d0b58\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n\n**System crash report 2** (crash in `blf_batch_draw ` -> `GPU_batch_draw `):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff8b1dfd42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2cd457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff8b1454bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff8b14542f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff83587fbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff71040390 0x7fff70e23000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff83589524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff7112e867 0x7fff70e23000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff710fe4fd 0x7fff70e23000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff7102ba2b 0x7fff70e23000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff71017f8e 0x7fff70e23000 + 2051982\n11 com.apple.GeForceGLDriver \t0x00007fff7100b6bc 0x7fff70e23000 + 2000572\n12 com.apple.GeForceGLDriver \t0x00007fff7100bec2 0x7fff70e23000 + 2002626\n13 com.apple.GeForceGLDriver \t0x00007fff7101113f 0x7fff70e23000 + 2023743\n14 com.apple.GeForceGLDriver \t0x00007fff7143f25e 0x7fff70e23000 + 6406750\n15 com.apple.GeForceGLDriver \t0x00007fff7143f4e6 0x7fff70e23000 + 6407398\n16 com.apple.GeForceGLDriver \t0x00007fff7143f5d7 0x7fff70e23000 + 6407639\n17 com.apple.GeForceGLDriver \t0x00007fff71013d3d 0x7fff70e23000 + 2035005\n18 com.apple.GeForceGLDriver \t0x00007fff7112e1ad gldUpdateDispatch + 1041\n19 GLEngine \t0x000000011925232a gleDoDrawDispatchCoreGL3 + 520\n20 GLEngine \t0x0000000119203bd9 gleDrawArraysOrElements_Entries_Body + 128\n21 GLEngine \t0x00000001191ffab4 glDrawArraysInstanced_GL3Exec + 220\n22 org.blenderfoundation.blender \t0x000000010b288f2c GPU_batch_draw_advanced + 428\n23 org.blenderfoundation.blender \t0x000000010b288d6c GPU_batch_draw + 124\n24 org.blenderfoundation.blender \t0x000000010b283d82 blf_batch_draw + 418\n25 org.blenderfoundation.blender \t0x000000010b282359 BLF_batch_draw_end + 9\n26 org.blenderfoundation.blender \t0x0000000106fc2163 view3d_draw_region_info + 8515\n27 org.blenderfoundation.blender \t0x0000000106936dbd DRW_draw_callbacks_post_scene + 445\n28 org.blenderfoundation.blender \t0x00000001069376cd DRW_draw_render_loop_ex + 1757\n29 org.blenderfoundation.blender \t0x0000000106fc2668 view3d_main_region_draw + 136\n30 org.blenderfoundation.blender \t0x0000000106bb157e ED_region_do_draw + 366\n31 org.blenderfoundation.blender \t0x00000001067e149c wm_draw_update + 2092\n32 org.blenderfoundation.blender \t0x00000001067df010 WM_main + 48\n33 org.blenderfoundation.blender \t0x000000010649b762 main + 962\n34 libdyld.dylib \t0x00007fff8b0b1235 start + 1\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff598ab4b8 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff598ab4e0 rsp: 0x00007fff598ab4b8\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x0000000120bebcf8 r13: 0x0000000000000000 r14: 0x00007fff93fe13c0 r15: 0x0000000120beb000\n rip: 0x00007fff8b1dfd42 rfl: 0x0000000000000206 cr2: 0x00007fff8b1c727d\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n1. Open Blender\n2. Click to remove start up information panel\n3. Click on Viewport Shading >Material Preview or >Rendered\n\nResult:\nCrash" ]

[ "Cycles crash deleting (all) geometry in editmode [no bvh rebuild, tries to refit bvh instead]\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 4)\nWorked: (optional)\n\nBlender crashes when delete all faces from an object during the rendered mode is active in Cycles\n\n1. Select Render Cycles Engine\n2. switch to Rendered mode\n3. from default cube select all faces and\n4. Delete only faces \n5. BUM!!! \n\n" ]

[ "Cycles Render: Volume (Before Baked Simulation Starts) still trying to be rendered\nOperating system:windows 11\nGraphics card:nvidia geforce rtx 2060\n\nBroken: 3.4.1\n\nThe cycles render tries to use the volume cache to render if the frame is less than the start of the simulation. See video example.\n\n1. Default cube: Add Quick Smoke.\n2. Cache settings:\n a. Type: All.\n3. Start frame: 50, end: 100.\n4. Bake.\n5. Start render on 30~ frames.\nExpected: Simulation chunks will appear in different parts of the domain.", "Some particles do not appear in the render when the 'Vector' pass is enabled\nOperating system: Linux-5.19.17-2-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: 3.2.2 - 3.3.1\nWorked: 2.79\n\nParticles in Render don't match particles in viewport. Some particles do not appear. When they move very fast the issue is more visible.\nIt happens when we enable the pass `Vector`\n\n- Open attached file or:\n - In the default scene (with the Cube), add a Plane\n - Add a ParticleSettings toe the plane\n - In {nav Particle Properties > Render} set `Render As` to `Object`\n - For the `Instance Object` choose the Cube\n - In {nav Particle Properties > Field Weights} set `Gravity` to `0.0`\n - Optionally bake for cache\n - Set `Render Engine` to `Cycles`\n - In {nav View Layer Properties > Passes > Data} enable `Vector`\n - Move Cube out of camera view\n- Choose a frame in the middle and render\nNote that the particles closest to the plane disappear\n\n[particles displaced.blend](particles_displaced.blend)\n\n", "Physics / Simulation Nodes Baking User Interface\nThis proposal unifies the Physics panels to be closer to the modifiers. There is no functional change besides the user interface.\n\nThen it adds the Simulation panel as a panel which is always visible for the objects. It is not part of the Add Physics.\n\n\n\nOpen questions:\n* Should Delete / Bake All Dynamics also take into account Simulation Nodes?\n\n", "Cycles and Eevee Significant Difference in Texture Output\nOperating system: Ubuntu 20.04\nGraphics card: GTX 1060 3Gb\n\nBroken: 2.80 and on (3.0.0 is still affected)\nWorked: 2.79\n\nFrom Blender 2.80, Cycles produces incorrect output for some procedural textures, while Eevee produces correct ones.\n{[F12696991](Cycles.png)}\n\nTest file (I assume there might be other files affected too). [Carbon_90.blend](Carbon_90.blend)", "Animated properties of View Layers are not updated when View Layer is not Active\nOperating system: Windows 10, x64\nGraphics card: nVidia GTX 1660\n\nBroken: 3.1.0; 3.1.2; and 3.3.0-alpha (08a39d32)\nWorked: none\n\nI'm compositing separate View Layers of a single scene. To reduce render times, I want to not render View Layers which are currently completely hidden, so I'm animating the \"Use for Rendering\" property of some View Layers.\n\nWhen *rendering*, it always works as expected... but *in the editor*, it seems that View Layers which are not the active workspace view layer do not update their animated properties when I move around on the timeline.\n\n\n # Open attached `bugreport-useforrender.blend`\n ** [bugreport-useforrender.blend](bugreport-useforrender.blend)\n\n **There is one Scene, \"Scene\". There are two View Layers, \"View A\" and \"View B\".** Collection \"Common\" has a camera and light. Collection \"Layer A\" has a Cube. Collection \"Layer B\" has a Suzanne/monkey.\n\n * Set View Layer \"View A\" as active (it should be already in the example file).\n **Observe the active collections. \"View A\" includes only the \"Common\" and \"Layer A\" collections, thus including the cube, camera, and light.** Observe the Graph pane and Properties pane. View A is used for rendering from frames 1 to 60, and not used for rendering from frames 61 to 120.\n\n * Seek to a frame before 60. Render a frame with F12. Observe the monkey and the cube, as expected.\n * Seek to a frame after 60. Render a frame with F12. Observe only the monkey, as expected.\n\n * Set View Layer \"Layer B\" as active, while still on a frame after 60.\n ** Observe the active collections. \"View B\" includes only the \"Common\" and \"Layer B\" collections, thus including the monkey, camera, and light.\n\n * Seek to a frame after 60. Render a frame with F12. Observe only the monkey, as expected.\n * Seek to a frame before 60. Render a frame with F12. ***Observe only the monkey, but both a monkey and cube was expected.***\n\n * Set View Layer \"Layer A\" as active, without changing the current frame.\n * Render a frame with F12. ***Observe the monkey and the cube, as expected, but not as consistent with a moment ago.***\n\n * With either View Layer active, render the whole animation with Ctrl+F12. The resulting animation is always rendered as expected.\n", "Regression: Failure to render stereoscopy correctly in background (rendering of curve objects with cycles and motion blur)\nOperating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon Vega 8 Graphics (raven, LLVM 15.0.6, DRM 3.47, 5.19.0-41-generic) AMD 4.6 (Core Profile) Mesa 22.2.5\n\nBroken: version: 3.5.1\n\nCaused by b32f5a922f05989ff129c3d266ebbed14b751e2a\n\nIn stereoscopic rendering with cycles curve objects are missing (mesh objects are fine) for the right eye if motion blur is activated. This only occurs in rendering without GUI via command line.\n\nCreate new \"General\" file\nDelete Cube\nAdd Bezier-Curve\nSet Curve Data-Properties: Geometry-Bevel Depth to 0.1 m\n\nRender Properties: Cycles; Motion blur: ON\nOutput Properties: Stereoscopy ON\nSet Framerange from 1 to 1\nsave as \"test.blend\"\n\nRender animation from GUI -> works properly\nCommand line: \n$ blender --background test.blend -a\n\nproduces a frame without the curve for the right eye.\n\nThe bug has similarities to the one reported by @SimeonConzendorf in /blender/blender/issues/70114#issue-38464 several years ago (Version 2.81). The bug seems to have irregularities, I had a similar behaviour in version 3.0.0 where it occured not in every frame in a quite complex scene. But I was not able to reproduce it in a simple way. The uploaded file doesn't reproduce the bug in that version and 3.0.1, but after these in 3.1.0, 3.3.1 and the actual daily build blender-3.6.0-alpha+main.d5fc1b9ba4b8-linux.x86_64-release \n\nI uploaded smaller anaglyph images instead of the separated images for better illustration.\n\n", "Blender 2.90.1 crashes after rendering the first few frames of animation.\n**System Information** \nOperating system: windows 10 64 bit\nGraphics card: Nvidia GeForce GTX 1650\n\nBroken: (2.90.1 3e85bb34d0d7; master)\nWorked(didn't): (only tried on 2.8.3 and did not work at all)\n\nWhen I try to render the animation, after about 50 or so frames(varies randomly), blender crashes with no alerts or anything that tells me what the error is, it simply closes.\nI've rendered another project, and that did indeed render, so I'm left confused why this short animation would cause a crash.\n\nEdit: I disabled motion blur, and it rendered fine. However, I would really like to know why blender won't render if motion blur is enabled. The renderer is Eevee and while my laptop isn't a super computer, it should be able to handle it. Thank you all in advance!\n\n- Open attached file\n- render the animation\n[cube-loop-tut-V1.0.blend](cube-loop-tut-V1.0.blend)", "bpy.ops.object.transform_apply no working after physics simulation\nOperating system: Windows 10 Pro\nGraphics card: 2x Nvidia 1080 GTX\n\nBroken: 2.8, b46245470f79, 2018-04-18\nWorked: 2.7x\n\nWhen running a rigid body simulation, it is not currently possible to apply transformation to freeze a specific frame. If you start scrubbing in the timeline, the object either goes back to original position or jumps to random position that was generated during the simulation.\n\n - add a plane and add a passive rigid body\n - add a suzanne and add an active rigid body\n - run the simulation\n - choose a frame\n - select the suzanne object\n - apply transformation/apply visual transformation\n # scrub in the timeline\n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Particle Emitter - Particles collisions not accurate\nOperating system: Linux-5.11.0-40-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00\n\nBroken: version: 3.1.0 Alpha\nWorked: This has been an ongoing problem since starting with Blender from 2.8\n\n\nParticles are not respecting collision system in every case.\n\n- Create plane and add particle system\n- Give emitted particles a positive or zero gravity value in field weights\n- Add wind force field running roughly parallel to plane.\n- Add turbulence.\n- Add collision system to plane\n\nExpected behaviour is for the particles to bounce off the plane as they are emitted in a positive Z direction and blown by turbulence against the plane. Instead they often break through. In the past this has meant that particles are bypassing the collision system such that emitted bubbles break through the hull of a submarine, and in my current case, half my sand particles to be hidden from view in a desert scene.\n\nNote attached file which shows the behaviour. Watch the simulation side on and particles can clear be seen breaking through the mesh.\n\n[Sand Wind Test.zip](Sand_Wind_Test.zip)\n\n\n\n", "Cycles can not render parent particle hair, while Eevee can.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.0\nWorked: I duno\n\n\nIn Eevee, parent particles are successfully rendered both in viewport and final render.\n\n\nHowever, Cycles fail to render the parent particles both in viewport and final render.\n\nA sample Blender file has been attached below.\n\n", "Regression: Rendering hair instances size in animation bug with animated emitter object scale\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.2\nBroken: 2.93\nWorked: 2.92\n\nRegression from 50782df425.\n\nIncorrect rendered instanced object scale if rendering hair animation with animated object.\n\n1 Create Cube and object for instancing\n2 Set cube scale animation for some frame range\n3 Apply patricle system to cube (hair / rendered instances as object or collection)\n4 Try to render single frame and render animation, compare difference\n\n[hair_render.mp4](hair_render.mp4)\n[test_hair.blend](test_hair.blend)\n\nWill set to high prio to raise awareness this is a regression, but this can probably be lowered again since also involves the EOL particle system.\nNote: if you really need to render this, consider using Cycles (where this still works when the `Persistent Data` option is OFF.", "Blender Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at [email protected]\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file", "Scaled Rigid Body causes issue (moving origin or mesh breaks collision, double transforms on negative scale)\nOperating system: Ubuntu 18.04 LTS\nGraphics card: Intel HD 4000\n\nBroken: 3.0\nBroken: 2.90.1\nWorked: I don't know if this works with any other version, I created the file using 2.90.1.\n\n\nSee the attached .blend file. This file contains two errors with Rigid body simulation. I'm filing both errors in one bug because these may be related (both happen in one example simulation).\n\nError 1: object origin distance from another object changes interaction between objects\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that \"Ball\" is attached to the chain.\n3. Stop the animation and jump to first frame.\n4. Select object \"Ball\" and from menu Object - set Origin - Origin to Center of Mass (Volume)\n5. Play the animation to verify that \"Ball\" is no longer attached to the chain.\n\nError 2: Rigid body type \"Active\" changes orientation of the object\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that chain is attached to the object \"Cube\".\n3. Stop the animation and jump to first frame.\n4. Change \"Cube\" Physics properties - Rigid body - Type: Active and Settings: Dynamic\n5. Play the animation and notice that Cube is now rotated 180 degress around the X axis. Obviously this results in chain no longer connected to the cube as expected and chain and Ball drop directly down during the animation.\n\nExample .blend file (cannot simplify more because Blender seems to be unstable with this file):\n[physics-test.blend](physics-test.blend)\n\n**Additional information**\nIt seems that I can work around Error 1 by selecting all items and applying \"Rotation & Scale\". I think this should not be required to get two objects to interact during simulation so I'm reporting the problematic file as-is. I cannot figure out the reason nor workaround for Error 2.\n\n$ apt policy blender\nblender:\n```\nInstalled: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nCandidate: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nVersion table:\n```\n *** 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0 500\n 500 ubuntu bionic/main amd64 Packages\n", "Objects with physics referred to by PointerProperty throw find_node_operation: Failed for (RIGIDBODY_REBUILD, '') when rendering\nOperating system: Ubuntu 20.04, Windows 10\nGraphics card: GeForce GTX 2080, GeForce GTX 1080\n\nBroken: 3.1.2\nWorked: Unknown\n\n\nWhen you have a PointerProperty, and that property refers to an object that has a rigid body, the following is output to the console when rendering:\n\n```\nfind_node_operation: Failed for (RIGIDBODY_REBUILD, '')\nadd_relation(Rigid Body Rebuild -> Point Cache Reset) - Could not find op_from (OperationKey(type: TRANSFORM, component name: '', operation code: RIGIDBODY_REBUILD))\nadd_relation(Rigid Body Rebuild -> Point Cache Reset) - Failed, but op_to (ComponentKey(OBBox, POINT_CACHE)) was ok \n```\n\nThis doesn't seem to have any other adverse effects, as rendering still succeeds with the object in the correct simulated position, but these types of messages fill up the console extremely quickly.\n\nOpen the following blend file, and render a frame. For some reason this requires the file to be opened via the UI.\n[repro2.blend](repro2.blend)\nAlternatively, unzip the following and run with `blender -b --python repro.py`.\n[repro.zip](repro.zip)\n", "Self-referencing driver works in viewport, but not in render.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional) 2.79b\n\nRotation property of object is updated in viewport, but not in render.\nIf run same script in 2.79 - all works fine both in viewport and render.\n\n```\ndef rotator():\n var1=bpy.data.objects[\"Suzanne\"].rotation_euler.z\n var3=bpy.data.scenes[\"Scene\"].render.fps\n\n new_value=var1+math.radians(var3)\n\n return new_value\n```\n\n\n[Script_bug_2.8.2.blend](Script_bug_2.8.2.blend)\n\n- run the file Script_bug_2.8.2 ('Run script', 'Update Dependecies')\n- play in the viewport - the animation works correctly\n- render (Ctrl + F12) - the animation does not work;\n\nViewport:\n[bug_video_render0001-0050.mkv](bug_video_render0001-0050.mkv)\n\nRender:\n[bug_video_render_20001-0050.mkv](bug_video_render_20001-0050.mkv)\n\n2.79 file:\n[Script_work_2.79.blend](Script_work_2.79.blend)\n\n" ]

[ "CLI animation renders and GUI animation renders with Lock Interface do not take rigid body simulations into account\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.2.0, 3.2.1, 3.3.0 Alpha\nWorked: unknown\n\n\nCLI animation renders and GUI animation renders with Lock Interface enabled do not take rigid body simulations into account.\nThe reason seems to be that there is no cache baked for the simulation.\n\n\n1. Open the attached .blend\n2. Render an animation from GUI\n3. Render from CLI (Example: `.\\blender.exe -b --open-last -a`\n4. Compare the result\n\n[arm_smash.blend](arm_smash.blend)\n\nRendered from GUI:\n[0000-0061_GUI.mp4](0000-0061_GUI.mp4)\nRendered from CLI:\n[0000-0061_CLI.mp4](0000-0061_CLI.mp4)\n\n" ]

[ "LookDev: Add option to set the background color\nTheme, World, Viewport.\n", "Missing Face Set Operators\nThis task is a todo list for missing face set operators. - [x] means operator works on either a user-picked face set or all of them. A single arrow means conversion operator in one direction already exist (so, Mask to Face Set already exists).\n\n- Face Set- [x] `<->` Vertex Groups\n- Face Set- [x] `<->` Face Maps\n- Face Set- [x] `->` UV Seams\n- Face Set- [x] `->` Mask\n- Make Disconnected Face Sets Unique\n- Separate By Face Sets\n- Face Set- [x] `<->` Material Slots\n- Face Maps `<->` Face Sets", "Unable to select vertex paint face mask faces while retopology overlay is active\nOperating system: Ubuntu 23.04\nGraphics card: AMD Radeon RX 570\n\nBroken: `main` (`e151425c5c1085d7be5f8bb2ad694a869bc16dc7`)\n\nIf the new retopology overlay is active in edit mode, vertex paint faces can't be selected \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. With default cube in _Edit_ mode, enable the Retopology overlay\n2. Switch to _Vertex Paint_ mode\n3. Enable face selection masking\n4. Try to select a face\n\nA small video is attached, showing first successful selection of a vertex paint face mask while the retopology overlay is inactive, then the inability to select vertex paint face mask faces after it's activated.\n\n", "The colors of the vertices do not correspond to the values in which I paint them with vertex paint.\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.92.0\n\nthe vertex color values that I get from the vertices in the shader editor node called \"vertex_color\" do not correspond to the values that I write there using vertex painting.\n\n\nSet the viewport mode to render or material preview. And change the inputs from the manual value to the value taken from vertex color. As you can see, the values themselves should not differ, but the color change.\n\n[vertex_color_error.blend](vertex_color_error.blend)\n\nPerhaps this is due to this issue D10956, but I want to say that we then need the ability to convert from one color space to another.\nBecause I use a blender to create game models and would like to use vertex colors to mix materials. But I can't, because it doesn't correspond to the colors and values that I enter. And it will not match what I will see in the game.\nIn addition, I enter specific values using the color wheel and sliders. And I expect to get them unchanged. That would be logical.\n", "Color picker undo adds step when cursor exist\nRun blender, logging undo events:\n\n```\n blender --log \"bke.undosys.*\" --log-level -1 --log-show-basename\n```\n\n\n\nClick on the object color swatch and move pointer away from the popup.\n\nEven though no changes have been made, an undo step is added.\n\n----\n\nIsn't high priority, reporting so it's not forgotten.", "vertex paint sample color not working as intended.\nplatform: Windows-10-10.0.19042-SP0\nGraphics card: 1080\n\nBroken: 3.1.0 Alpha\ncommit date: 2021-11-14 00:26 hash: 7e82c840b7a4\nbuild date: 2021-11-15, 00:51:48\n\n**Short description**\nVertex color that is sampled changes.\nChange in sample color after moving mouse over panel\n\n**Steps to Reproduce**\n- Go into Vertex paint mode. (make sure viewport shading mode is set to rendered)\n- Select an object then press s to sample a vertex color and left click the mouse (to add to palette)\n# move the mouse over panel (selected color will be changed)\n\nThis seems to happen when you move the cursor over any part of the U.I.\n\n[Vcol.blend](Vcol.blend)", "Texture Paint: Wrong active Texture Slot\nOperating system:win10\nGraphics card:GTX 740m\n\nBroken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, build date: 2021-02-25, 09:31:14, hash: 02948a2cab\n\nVpqy7BmMKaA\n\n- Open attached file or:\n - Go to \"texture painting mode\" (in default workspace)･\n - Create 2 base color textures\n - Open Shader Editor\n- In the Shader Editor, select non -active texture (\"Material Base Color 2\")\n- in the View 3D, paint texture\n- Nothing happen in visual.\n- The other texture slot is changed instead of current active texture.\n[tex_slot_problem.blend](tex_slot_problem.blend)\n\n", "Image mask editing has a toolbar with no tools\nWe should at least have basic selection tools and cursor in the image spaces mask toolbar, currently it's completely empty.", "Add Driver : Clicking the pickers (object / input variable) dont work\nBroken:2.80, 4c31bed6b46, blender2.8, 2018-11-30\n\nClicking the object picker in the `Add Driver` should enter object picking mode, but does nothing.\n\n\nBased on the default startup :\n- Select the **Cube**\n- Right click on **Location/X** and **Add a Driver**\n- Into **Object field**, click on the **picker**\n\n\n> In #58341#702152, @angavrilov wrote:\n> This happens because `ui_context_rna_button_active` within operators and poll functions invoked for the popover UI elements can't find the actual UI control in the popover, and instead returns the property UI control through the context menu of which the popover was invoked. It seems there is a big issue with context and region management in some popovers, and may require a fix in the UI core rather than a specific operator.\n> \n> Edit: Note that this issue is different from the picker attached to the Add Input Variable - that one is simply not (re-)implemented yet to work with the new way Add Driver works.\n\n\nEven though `Object` picker vs `Input Variable` picker are slightly different issues, will keep them together here since from a user perspective this is so tightly related.", "Quick Explode operator messes with user materials\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0\n\nWhen using quick explode material, the operator messes with the user created materials present in the first material slot. This results in unintended and unexpected changes to already existing user materials. It also, without any warning, changes the Eevee material blend mode to Alpha Blend, creating severe shading artifacts for materials which were not supposed to be transparent.\n\n\n1. In a new, empty .blend file, create a sphere.\n2. Add new default material to the created sphere\n3. Using operator search, find Quick Explode operator and execute it\nResult: The user created material was changed without warning or user's permission\nExpected: Under no circumstances are user's materials adjusted without warning when running Quick Explode operator\n\n", "Collection usability\n- [ ] Viewport UI\n- [ ] Shortcuts to toggle visibility?\n[ ] . . .\n\nNeed a clear design on what to do.", "UV: select similar enhancements\nAdd support for UV Select similar:\n\n* Islands / Faces / Edges, crossing UDIM boundary\n* Islands / Faces texel density\n\nThanks @BlenderBob !\n\n", "New geometry nodes viewer overlay makes mesh edit mode overlays invisible\nOperating system: Linux-5.19.10-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.4.0 Alpha, current master\n\n\n| {[F13588717](image.png) size=full} | {[F13588720](image.png) size=full} |\n| -- | -- |\n", "User defined default color for images\n**The Default Color**\n\n_**If you map a texture in such a way that the image doesn't cover the entire model, the default color should show up.**_\n\nInterestingly Blender does have a default color and as far as I know the only way to see it is to set an image texture extension mode to _Clip_. In that case, any UVs mapped outside of the image space get the color black (0.0, 0.0, 0.0). However this default color can not be currently defined by the user.\n\n\n\n**The Panic Color**\n\nThe panic color for images AKA the bright magenta (1.0, 0.0, 1.0) appears when an image file has not been loaded correctly. It's meant as a visible warning for **missing images**.\n\n\n\n**The Problem With UDIMs**\n\nExternal texturing tools are able to _skip_ UDIM tiles that do not contain any valuable information apart from the base color value.\n\nBlender doesn't correctly support variable size UDIM sets and expects all UDIM sets to be of equal size.\n\nThe panic color currently shows up when dealing with **variable size UDIM sets** (color, normal, roughness, etc).\n\nAs a way of an extremely simplified example I've created the following file featuring a material with 2 UDIM sets, one for the Color and one for the Normal.\n\n\n\nThe problem appears because the 2 UDIMs are not conformed by the same number of tiles (images).\n\nThe Color UDIM with 3 tiles:\n\n\n\nThe Normal UDIM with 2 tiles:\n\n\n\nThe Normal UDIM delivers the panic color (magenta) in the non existing 1003 UDIM tile.\n\nThis is incorrect behavior since no image is really missing (there can not be a missing image if the tile does not exist in the first place).\n\n\n\n**The proposal**\n\nAllow for the default color to be user definable.\n\nIn the case of single image textures with extend mode set to clip, this color is applied to any UVs that exist outside of the (0.0, 0.0) - (1.0, 1.0) space.\n\nDefault color set to (0.28, 0.25, 0.2):\n\n\n\nIn the case of UDIMs this color is applied to any UVs that exist outside any tile.\n\n\n\nDefault color set to (0.5, 0.5, 1.0) AKA the bluish normal base color:\n\n\n\nFor existing tiles that have failed to load their image (missing images). The pink panic color is **still expected**.\n\n\n\nPanic color to be expected since the tile **exists** but it's image was not found.\n\n", "The image node in GeoNodes can't use UDIM tiles\nOperating system: Windows 11\n\nBroken: 4aac5b92c1bb\n\n\nIt seems like the image texture node is not able to access the UDIM uv range properly. As you can see in the image the objects have proper UDIM tiles that the regular textures can utilize . The image texture node of the geonodesseems to bound the UVs within 0-1 range and cant access the tiles.\n\nPassing the UVs from the modifier does not seem to help with it.\n\n\n\n\nload the attached .blend file\n\nselect the NOUDIM object\n\nopen the geometry nodes graph of the object's modifier\n\nenable the viewer node\n\n[_01122022_2239_12_02_2022.zip](_01122022_2239_12_02_2022.zip)\n" ]

[ "Eyedropper for props does not work in dialog boxes\nBlender 2.81, 71f2229b0d82\nfor example, in Texture Paint Context Menu\nI wanted to implement something using Operator and context.window_manager.invoke_props_dialog()\nThis is not a bug, but why not do it at the dialog level.\n" ]

[ "--addons does not enable the relative addon checkbox\nWindows 7\n\nBroken: 2.79\n\nBy using [--addons ](https:*docs.blender.org/manual/en/dev/advanced/command_line/arguments.html)*add-on*, the checkbox in the UI of*Blender User Preferences*\"Add-ons\" page is not enabled for*add-on//.\n\n - type `.\\blender.exe --addons mocap`\n - open *User Preferences*\n - click *Animation* under *Categories*\n - search for *Animation: Motion Capture Tools*\n - verify the checkbox is not enabled for this addon", "Old todos (to be checked)\nNOTE: this is a direct dump of Install-OS (without cherrypicking the valid items)\n\n- [ ] Add code to detect drives to change (usb connected, disconnected)\n- [ ] RNA library needlessly rebuilds every time in visual studio.\n- [ ] Blender doesn't recognize .lnk shortcuts or hidden files.\n- [ ] Symbolic links are not supported #37619.\n- [ ] NTFS junctions are not supported #52080.", "Pixels and resolution not for multilayer EXR and Render Result\nCentOS - GTX 1070\n\n2.79\n\nPixels and resolution are not available with multilayer EXR or Render Result images.\n\nimport bpy\ndata = bpy.data\nimage = data.images['Render result or multilayer EXR']\nprint(image.pixels) # length is 0\nprint(image.resolution) # return always Vector((0.0, 0.0))\n\nIt is working with regular EXR file.\n", "Crash on toggle bone layer\nOperating system: OpenSUSE Linux, kernel 5.10.7\nGraphics card: intel \n\nBroken: blender-2.92.0-a5637756491c-linux64\n\nBlender crashes when I'm trying to enable bone layer visibility.\n\n1) Open example file: \n[rig-bug3.blend](rig-bug3.blend)\n2) Click on the *second* rig bone layer: \n\nResult: blender crashes with backtrace:\n\n```\n# Blender 2.92.0, Commit date: 2021-02-05 15:23, Hash a5637756491c\nbpy.ops.outliner.item_activate(extend=False, deselect_all=True) # Operator\nbpy.ops.outliner.item_rename() # Operator\nbpy.ops.outliner.orphans_purge(num_deleted=40) # Operator\nDeleted 40 data-block(s) # Info\nbpy.ops.outliner.orphans_purge(num_deleted=10) # Operator\nDeleted 10 data-block(s) # Info\nbpy.ops.outliner.orphans_purge(num_deleted=1) # Operator\nDeleted 1 data-block(s) # Info\nNo orphaned data-blocks to purge # Info\nSaved \"rig-bug3.blend\" # Info\nbpy.context.space_data.context = 'DATA' # Property\nSaved \"rig-bug3.blend\" # Info\n\n# backtrace\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(BLI_system_backtrace+0x20) [0x865fd90]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0xeb3a2a]\n/lib64/libc.so.6(+0x3d6c0) [0x7ff5377926c0]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_displist_vertbuf_create_pos_and_nor+0x5e) [0x13d443e]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_curve_batch_cache_create_requested+0x4ea) [0x13d24ea]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0x85bf76b]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(BLI_ghash_free+0x4e) [0x85c00ee]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0x13840e7]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_draw_render_loop_ex+0x1ac) [0x138649c]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(view3d_main_region_draw+0x8f) [0x1c0442f]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(ED_region_do_draw+0x7e1) [0x17ab221]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(wm_draw_update+0x52e) [0x123c70e]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(WM_main+0x30) [0x123a5a0]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(main+0x31e) [0xdeb30e]\n/lib64/libc.so.6(__libc_start_main+0xea) [0x7ff53777ce0a]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0xeb03c3]\n\n```", "Some Overlays are not rendered in Viewport Render (Text Info incl object name, Statistics, 3D Cursor)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.1\nAlso 3.1.0 Alpha\n\nUsing viewport render (or workbench) I'm unable to view object or empty names \n```\n(bpy.data.objects[\"NAME\"].show_name)\n```\n\nEnable show name on a visible object, and make a viewport render (bpy-ops-render-opengl)\nThe text isn't rendered in the image like it is in the viewport.\n\n", "EEVEE and Workbench missing animatable properties\nOperating system:\tWindows 7\nGPU:\t\t\tRadeon Vega 64, Divider version: 19.12.2\nCPU:\t\t\tIntel Core i7-5960X\n\n\nWorking-ish*:\t\t`blender-2.79b-f4dc9f9d68b-windows64` (official release) \nBroken:\t\t\t`blender-2.80-f6cb5f54494e-windows64` (official release) and later\n\n\nEEVEE and Workbench's render properties (`Properties Editor --> Render Properties`) are, for the most part, not animatable.\nThis is in contrast to Cycles which, *for the most part*, has all settings set to be animatable.\nBack in 2.79b the OpenGL \"Workbench\" Render options were supported:\n\n\n\nSome of the panels like Film, Simplify and Colour Management (which exist in all render engines) work as expected from 2.7X to 2.8X.", "Noisy Mist and Depth Pass\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.6.0 Alpha\n\nProbably related to the same issue described in #65887 and #66149, that when there is a transparency in the material the mist pass produces noise on the object using transparency.\n\nIn this issue, the Mist pass gets noisy once it reaches a volumetric boundary.\n\nThe same with the depth pass, but with normalized values.\n\nDenoising depth node seems to partially fix the depth problem, but denoising mist pass may result in washed out image if the mist is strong over an area with transparency, like grass or something\n\n\n\n- Open attached .blend file\n- Render (`F12`)\n- Check Misty or Depth (normalized) pass\n\n[Test.blend](https://projects.blender.orgattachment)", "Float slider in the redo panel of the \"add object\" operator does not hide the mouse cursor\nBroken: 2.79b, 2.83\nWorked: (None)\n\nThe problem is not seen in editing mode, but in object mode when adding an object\nand changing the properties in the redo panel, the mouse cursor does not disappear.\n\n\n", "Unable to export/import EXR files after doing `import bpy` and when using the multiprocessing in Python (Blender freezes)\nI am trying to render depth maps and surface Normals using Cycles and store the results in OpenEXR format using nodes. I set up the nodes as follow using Blender's Python API:\n\n\n```\n#blenderClass.py\nimport importlib\n\nclass Blender(object):\n def __init__(self):\n self.bpy = importlib.import_module(\"bpy\")\n self.scene = self.bpy.context.scene\n self.scene.render.use_sequencer = False\n self.scene.display_settings.display_device = 'sRGB'\n\tself.scene.view_settings.view_transform = 'Raw'\n\tself.scene.sequencer_colorspace_settings.name = 'Raw'\n self.scene.render.engine = 'CYCLES'\n self.scene.use_nodes = True\n\tself.setupRenderNodes()\n\n def setupRenderNodes(self):\n\t\t\n\tfor node in self.scene.node_tree.nodes:\n\t\tself.scene.node_tree.nodes.remove(node)\n\trenderNode = self.scene.node_tree.nodes.new('CompositorNodeRLayers')\n\n\t# Depth map\n\tself.depthOutputNode = self.scene.node_tree.nodes.new('CompositorNodeOutputFile')\n\tself.depthOutputNode.format.file_format = 'OPEN_EXR'\n\tself.depthOutputNode.format.color_depth = '32'\n\tself.depthOutputNode.format.color_mode = 'RGB'\n\tself.depthOutputNode.format.exr_codec = 'ZIP'\n\tself.depthOutputNode.base_path = 'somePath/'\n\tself.depthOutputNode.file_slots[0].path = 'fileNameDepth#'\n\n\t# Link\n\tself.scene.node_tree.links.new(renderNode.outputs[2], self.depthOutputNode.inputs[0])\n\n def render(self, objPath):\n self.bpy.ops.import_scene.obj(filepath=objPath)\n self.bpy.ops.render.render(write_still=True)\n```\n\n```\n#main.py\nfrom multiprocessing import Process\nimport blenderClass import Blender\nblender = Blender()\n\nobjPaths = ['obj1.obj', 'obj2.obj', 'obj3.obj', 'obj4.obj']\n\nprocList = []\nfor path in objPaths:\n proc = Process(target=blender.render, kwargs={'objPath': path})\n procList.append(proc)\n proc.start()\n\nfor job in procList:\n job.join()\n```\n\nThe problem is when I do bpy.ops.render.render(write_still=True) Blender freezes and the results are not saved on disk. However, if I change OPEN_EXR_MULTILAYER and OPEN_EXR to PNG and change the color_depth to '16' everything works and I get the rendering results on disk. Note that I do not change any of my rendering engine settings like tile size, resolution etc. Does anyone know why Blender freezes and the rendering results are not on disk when using OpenEXR?\n\nThe strange thing is everything works normally when running Blender with GUI and setup the nodes and rendering engine the same way. It would be also useful if someone can try this and let me know if things work fine on their side.\n\nI'm not sure if this has something to do with the problem that I'm facing but I have compiled Blender manually and import it as a module in the Python installed on my machine. Here are the CMake settings I used to compile Blender 2.79b from source:\n\n\n```\ncmake blender \\\n -DCMAKE_INSTALL_PREFIX=/usr/lib/python3/dist-packages \\\n -DWITH_INSTALL_PORTABLE=OFF \\\n -DWITH_PYTHON_INSTALL=OFF \\\n -DWITH_PYTHON_MODULE=ON \\\n -DPYTHON_SITE_PACKAGES=/usr/lib/python3/dist-packages \\\n -DPYTHON_VERSION=3.5 \\\n -DWITH_OPENAL=ON \\\n -DWITH_CODEC_AVI=ON \\\n -DWITH_MOD_OCEANSIM=ON \\\n -DWITH_CODEC_FFMPEG=ON \\\n -DWITH_SYSTEM_GLEW=ON \\\n -DWITH_FFTW3=ON \\\n -DWITH_OPENCOLORIO=ON \\\n -DWITH_GAMEENGINE=OFF \\\n -DWITH_PLAYER=OFF\n```\n\nUpdate: I experience the same behavior with Blender 2.78 and 2.79, compiled with the same exact settings above.\n", "Console warnings when accessing subtype and default values of properties with python\nBlender 2.91.0\nOctober 30, 00:21:13- 9e85812acc88\n\nthank you for fixing #82167 so quickly @lichtwerk, most of my warnings are now gone.\nA few more still remain though, I've tried to track them down and I think these are all of them:\n\n```\nimport bpy\nbpy.types.Curve.bl_rna.properties['bevel_depth'].subtype\nbpy.types.Curve.bl_rna.properties['extrude'].subtype\nbpy.types.Curve.bl_rna.properties['offset'].subtype\n\nimport bl_operators\n# if I remove the options={'ENUM_FLAG'} from the operator these 2 don't throw a warning\nbl_operators.wm.BatchRenameAction.bl_rna.properties['strip_chars'].default \nbl_operators.wm.BatchRenameAction.bl_rna.properties['strip_part'].default\n\nimport cycles\ncycles.properties.CyclesRenderSettings.bl_rna.properties['denoiser'].default\ncycles.properties.CyclesRenderSettings.bl_rna.properties['preview_denoiser'].default\ncycles.properties.CyclesRenderSettings.bl_rna.properties['distance_cull_margin'].subtype\n\n```\n\nit gives me these errors\n\n```\nWARN (bpy.rna): C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1493 pyrna_enum_to_py: current value '65536' matches no enum in 'FloatProperty', 'bevel_depth', 'subtype'\nWARN (bpy.rna): C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1493 pyrna_enum_to_py: current value '65536' matches no enum in 'FloatProperty', 'extrude', 'subtype'\nWARN (bpy.rna): C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1493 pyrna_enum_to_py: current value '65536' matches no enum in 'FloatProperty', 'offset', 'subtype'\nWARN (bpy.rna): C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1493 pyrna_enum_to_py: current value '0' matches no enum in 'EnumProperty', 'strip_chars', 'default'\nWARN (bpy.rna): C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1493 pyrna_enum_to_py: current value '0' matches no enum in 'EnumProperty', 'strip_part', 'default'\nWARN (bpy.rna): C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1493 pyrna_enum_to_py: current value '1' matches no enum in 'EnumProperty', 'denoiser', 'default'\nWARN (bpy.rna): C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1493 pyrna_enum_to_py: current value '0' matches no enum in 'EnumProperty', 'preview_denoiser', 'default'\nWARN (bpy.rna): C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1493 pyrna_enum_to_py: current value '65536' matches no enum in 'FloatProperty', 'distance_cull_margin', 'subtype'\n```\n", "Image Sequence data disappears after certain properties are set\nOperating system:\nGraphics card:\n\nBroken: 2.83.6 (and all previous 2.8x versions)\n\n\nCannot access image sequence pixel data from 'Image Sequence' editor after certain properties are set.\n\nBased on the following startup file and bundled image sequence:\n\n\n1. Open the 'image_sequence_issue.blend' file from the following zip folder:\n[image_sequence_issue.zip](image_sequence_issue.zip)\n2. Run the active script in the text editor area\n3. Notice that an error is thrown - the image sequence has no data.\n4. Now comment out lines 8 & 9 (or line 12), and re-run the script. Notice that no error is thrown and the image has data.\n\nFor reference; the script bundled in the above file is copied below:\n\n```\nimport bpy\n\n# get the image editor space in the current screen\nviewer_area = next(area for area in bpy.context.screen.areas if area.type == \"IMAGE_EDITOR\")\nviewer_space = next(space for space in viewer_area.spaces if space.type == \"IMAGE_EDITOR\")\n\n# set properties on the image user\nviewer_space.image_user.frame_offset = 1\nviewer_space.image_user.use_cyclic = True\n\n# set the display channels to 'color'\nviewer_space.display_channels = \"COLOR\"\n\n# viewer_space.image.reload() # this line does not fix the issue\nprint(\"Before update:\", viewer_space.image.has_data)\nviewer_space.image.update()\nprint(\"After update: \", viewer_space.image.has_data)\n```", "Crash when updating image pixel data through python API\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.0, 2.90\nWorked: N/A\n\nBlender crashes with apparent memory corruption, when image pixel data and previous are updated frequently with python script.\nStack traces give no obvious answer, i have seen it happen in depsgraph eval, node graph code, imbuf, etc.\n\n*Note: i could not reproduce this issue in debug mode so far, only release or RelWithDebInfo seems to work.*\n\n 1. Open attacehd file\n - Run the script\n - Make sure the scene properties are visible (it seems to only crash when displaying image previews).\n - Grab the default cube and wiggle it around to force depsgraph updates.\n - If it doesn't want to crash, re-open Blender, it seems to be quite random.\n\nI'm using a node group to access image data blocks, so they can be displayed in a panel as pointers. The code generates data to replace the image pixels as well as the preview.\nI have also tried running a timer and deferring pixel updates using a queue as suggested [here ](bpy.app.timers.html#use-a-timer-to-react-to-events-in-another-thread), just in case the depsgraph post update is somehow not safe, but this doesn't change anything substantially. The bug happens in both cases.\n\n[crashtest.blend](crashtest.blend)", "shadow catcher data missing from diffuse passes when transparency is disabled, and shadow catcher object is masking environment when transparency is enabled (can't recombine moving scene envronment)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\n\nshadow catcher data missing from diffuse passes when transparency is disabled, and shadow catcher object is masking environment when transparency is enabled (can't recombine moving scene envronment). This makes it impossible to rebuild the image unless the shadow catcher pass is used, which is not suitable when using vector motion blur.\n\nOpen below blend file (choose to load ui)\ngo to scene 'no transparency'\nin the compositor press f12 to render a frame\ncompare the combined image and the rebuilt image\n\ngo to the second scene 'transparency'\nin the compositor hit f12 to render again\nthis time the environment is masked out by the shadow catcher, making it impossible to use the rendered environment (which is necessary if the camera is animated)\n\nrequired behaviour - \n\nshadows appear in diffuse passes when transparency is disabled, so the rebuilt image matches the viewport.\n\nshadow catcher object doesn't mask out the environment pass when transparency is enabled (so the environment can be added back to the image when the camera is moving (backplate cant be used here))\n\n\n\nThe only possible solution currently is to always render with transparency enabled, and then render your scene a second time with only the environment visible, which causes issues when rendering via scripts.\n\n", "LOAD UI - Checkbox Status Ignored\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked: (Unknown)\n\n\nWhen opening a file with a UI that does not match the default UI, the file's internal UI is loaded regardless of the LOAD UI checkbox being marked \"OFF\". More specifically, the MODE of a workspace is not respected and uses what ever mode is used within the file.\n\nIE, the default is \"Object\", while a scene can override it to something else - in this example, Texture Paint.\n\nAs the mode is part of the workspace setting, it should not be overriding when the scene is opened.\n\n\n\n\nSee screenshots.", "Denoise artifacts in Albdeo and Normal pass caused by material roughness\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Alpha\n\nThe `Denoise Data Albedo` shows gray flat colored areas if the `metallic/specular` material have the `roughness` value below `~0.274`.\nThis also affects the `Denoise Normal` pass because it can appear black in these areas.\nTo show these artifacts for `specular` and `metallic` materials, the depending values are: `Base Color`, `Metallic/Specular`, `Roughness` and the angle (between camera and face).\nAll of this leads to visible seams in the denoised image (NonLocalMeans and OpenImageDenoise). The more noise the more it is noticeable.\n\nRender passes of material with roughness on 0.0 (See Albedo and Normal pass):\n\nThis shows both the roughness dependent gray area overwriting the the camera dependent gray area.\n\nThis is just to show that irregular roughness inputs (like a noise) also create these. It is the same with Textures.\n\n\n**Edit (10.02.2021):**\nJust noticed and wanted to clarify. The Denoise Normal pass shows black in the top corner, because it reflects the background.\nHere is an example of an object being reflected in that area. \n\n\n**Steps for others to reproduce the error**\n- open attached file or:\n - create a plane\n - set Material to a Principled BSDF Node having: Base Color: 0.047; Specular: 1.0; Roughness: Linear Gradient.\n - set the camera to a viewing angle of 60° to the plane.\n - set the Worlds background shader color to a checker board to have something to reflect on the plane.\n- Render in Cycles with Denoise Data in the View Layer Properties activated.\n[Denoise_Layer_bug.blend](Denoise_Layer_bug.blend)" ]

[ "Cycles Python tooltip path is not complete\n**Original Title**\nAPI bug - enable/disable crypto passes\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe Python tooltip for Cycles properties (e.g., enable crypto pass) is broken:\n`bpy.data.scenes[\"Scenes\"] ... use pass_crypto_object`\n\n\n-------------------------------------\nNow to the original report:\n\n\nenabling or disabling Cryptomatte passes is inaccessible with python\n\nWhen enabling object crypto through the UI, the info panel displays it as *bpy.context.scene.use_pass_crypto_object = True*, but according to the console this expression doesn't exist: *AttributeError: 'Scene' object has no attribute 'use_pass_crypto_object'*\nI found another way to access this information: *bpy.context.scene.view_layers['View Layer']['cycles']['use_pass_crypto_object']* , but changing the value between 1 and 0 only makes changes to the UI, not the compositor\nSame goes for other cryptomatte passes and settings\n\n" ]

[ "Baking of normals show different results between versions\nOperating system: Win 10\nGraphics card: Geforce 3060\n\nBroken: 3.5.1\nWorked: 3.4.1\n\nThis changed in 75ad8da1ea6799e3983e4146f4b20dc4bfbb8415\n\n\nBaking of normal map differnet between Blender versions\n\nThe Attached blend file will output differnt result when trying to bake the normals.\nThe Mesh is part of a comercial mesh I use, therefore I cannot share the whole mesh, but in the blendfile you just need to bake the normals in blender 3.4.1 and then in 3.5.1\nThe results are differnet.\n\nBlender 3.5.1 seams to have some bug in the baking or handles the baking differnt.\n\nEdit:\nSeams like the Auto-Smooth of meshes bauses this difference between the versions", "Bump node bump converges to different result than displacement bump\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nUsing the same height map in combination with the bump node gives a different result than using the displacement node with bump only.\n\n\nWhen switching between the bump and displacement node one can notice a visible brightness difference in parts of the shape.\nWhat is perplexing however is that upon inspecting the normals used in rendering (switch render pass to normals), they are identical.\nSo the problem probably doesn't lie in how the shading normals are calculated but rather how cycles uses these.\n\n- Open attached file\n- Disconnect the displacement Map and connect the Bump Node to the `Principled BSFD` Node\nNotice the difference, (one receives less light)\n[test.blend](test.blend)\n\n\nThank you and have a great day!\n\n", "Regression: Ambient Occlusion causes shading artifacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.93.1\nWorked: 2.91, 2.92\n\n Under lookdev mode, when object has \"alpha blend\" turned on in the shader, \"ambient occlusion\" with \"bent normal\" option enabled will cause shading artifact that looks like the object is shading flat. \n\nSwitch the scene to lookdev mode. \nCreate a UV sphere\nShade it smooth\nTurn on Ambient Occlusion and make sure \"Bent Normals\" is checked. \nAssign a material to the sphere. \nUnder the material settings turn on \"Alpha Blend\". \nNow the object will look like it's shaded flat/without smoothing. \n\n[Eevee_bug_scene.blend](Eevee_bug_scene.blend)\n\n", "Regression: Pixels in render result appear blurry during rendering\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.4.1\n\nPixels in the render result can appear to be stretched into 1x2, 2x1 or 2x2 pixels depending on window resolution. \nThis is only the case while the render is still going; when it finishes the pixels appear as they should.\n\n\n1. Start rendering any scene, most noticeable in scenes with easily visible noise like this one: \n[noisebox.blend](noisebox.blend)\n2. Resize the window while the render is running\n3. Observe pixels changing size\n[blender_2023-02-07_04-11-02.mp4](blender_2023-02-07_04-11-02.mp4)\n", "Workbench/Solid : Texture interpolation not displaying properly in viewport (shared across all users of an image)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.0\nWorked: --\n\nLow resolution textures are no longer being correctly displayed as a sharp graphic in the viewport when the texture interpolation is set to \"closest\" in the material shader.\n\nfeature works as intended in rendered view so long as Eevee or Cycles is selected. Workbench does not work as intended in rendered view.\n\nplace object into scene. Locate a low resolution asset such as pixel art and map the texture to the object. \n\ntextures have always appeared blurry at first in the viewport but common pixel art practice is to set the interpolation from \"linear\"(or whichever is set to default) to \"closest\"\n\nWe have 4 materials each having individual Image Texture nodes (but all using the same image).\n\nIf you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.\n\n", "VSE Sequencer timecodes display almost correct values\nOperating system: Linux-5.4.0-94-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.0.0\n\nsometimes the timeline displays 1m60s instead of 2m. this is kind of correct but actually not correct. I have no idea what could cause this, this appears on various zoom levels and only on specific positions that seem to be fixed positions.\n[superstious.mp4](superstious.mp4)\n[2022-01-14 20-43-02.mp4](2022-01-14_20-43-02.mp4)\n\n\n[#94920.blend](T94920.blend)\n", "Orange tile boxes appear in the wrong place when using border render and viewing a different slot than the one being rendered in\n\nOperating system: Linux Mint 18.3 64-bit\nGraphics card: N/A; rendering on Intel i5-4460\n\n2.80 beta, 918941483f7e, blender2.7, 2019-02-27, 00:14\n\nWhen using border render (but not if rendering the full image), the orange tile boxes show up in the wrong place *when viewing another slot aside from the slot being rendered in*. They are a few hundred pixels too low.\n\n[F6720951](render-2019-02-26_21.28.51.mp4)\n\nOpen Blender.\nHit F12.\nAfter it renders, press CTRL+B, and select some portion of the render area.\nRender.\nPress J to switch to Slot 2 and render there too, so the canvas becomes visible.\nRender on either slot, and switch to the other.\nTake note of where the boxes are compared to where you set your render border at.\nCancel rendering/let it finish.\nSwitch back to Slot 1 to verify that the correct area was rendered and that the boxes were below it.\n\nI discovered this on 893fa5983193e from 3 days ago, but downloaded the latest version and did a quick test to make sure it still happens.\n\nI also noticed that after I rendered, set a render border, and started rendering again, it actually rendered the whole image - only the bordered area was visible, but it rendered everything else too. After that first time, it only rendered the bordered area, as it should.\n\n[F6721094](render-2019-02-26_22.08.33.mp4)\n\n(I set samples to 512 in order to slow rendering so I would have time to switch slots and show what happens before it finishes rendering.)\n", "Vertex paint + x-ray + polygon selection mode = weird shading\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\n\nFor me it looks like this\n\n\n\n[vertex paint x-ray strange shading.blend](vertex_paint_x-ray_strange_shading.blend)", "Eevee SSRefraction noisy at low roughness\nOperating system: Windows 10 Pro\nGraphics card: GTX 1050TI\n\nBlender 2.93 and 3.0\n\nScreen space refraction has a weird noisy ball on the center of it, with a kind of low quality pixelated look, only ways to get rid of it partially is by either increasing the IOR, increasing the Refraction Depth, or changing the roughness of the material to something that isn't between 0.01 - 0.3.\n**This applies to both the roughness and trasmission roughness**\n\nSide note : i tried changing all the settings in the render properties, nothing worked, speaking of which, Half Res Trace does NOT apply to Refraction, only Reflections.\n\nJust do a basic setup of SSRefractions, nothing more than that\n\n\n\n[SSRefractionsExample.blend](SSRefractionsExample.blend)\n\nMore extreme example:\n[#90307.blend](T90307.blend)", "Booleans causing shadow artifacts in solid render mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 3.0.0 Alpha\nWorked: Unknown\n\nI built up a random shape using a bunch of booleans via the box cutter addon.\nThis seems to have introduced artifacts when the shape is viewed from certain angles.\n\nThe artifacts remain when applying all the modifiers. I also tried to reset various edge data like bevel weight and crease without any effect.\nAdding a triangulate modifier however cleans it up, so maybe something about the automatic triangulation is off.\n\nI compared the output with the stable release: It also shows artifacts but they look slightly different, at least with my current configuration.\n\nv.2.93.1\n\n\nv.3.0.0 (see version info above)\n\n\nIn motion from another angle, showing convergence on a point and something that looks like an [even/odd fill rule](Even%E2%80%93odd_rule) of a shape being used to draw the shadow:\n[streaks.mp4](streaks.mp4)\n\n\nI cannot offer concrete steps; my default file also has certain settings already applied.\nHere is the file that may help show the issue: [shadow-streaks.blend](shadow-streaks.blend)\n", "Bump Map and Normal Map causes flat shading.\nOperating system: windows 10 1903\nGraphics card: 1080ti * 2\n\nBroken: 2.82.7 stable versioin\n\nThis issue appears both on eevee and cycles.\nWhile using smooth shading, simply add a bump map and the shading lookes flattened.\n\n\nThis problem will occur on a high poly model if the camera is close enough.\n\n\nBevel the cube with several segments and simply plug a bump map to the normal port of the shader node.\n\n[smooth shading issue.blend](smooth_shading_issue.blend)", "EEVEE Ambient Occlusion incorrect composition (affected by Bent Normals even at Factor of zero)\nOperating system: rx 6800\nGraphics card: windows 10\n\nBroken: blender-2.93.0-a9e7d503ddcd-windows64\n\nthe ambient occlusion does not appear to blend correctly both in viewport and in final renders\n\nno ambient occlusion\n\nao factor 1\n\nao factor 0\n\n[incorrect ao composition.blend](incorrect_ao_composition.blend)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Wrong result mixing 2 nodes of an image texture\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.3, 2.93\nWorked: unsure\n\nWhen using 2 nodes of the same texture and connecting the Color output from one and the Alpha from another, the result looks different in comparison when using both outputs from one node. Broken in EEVEE\n\n1) Open the file, switch to material preview/rendered\n2) Reconnect the color (or the alpha) link to another texture\n[Bug1.blend](Bug1.blend)", "Discrepancy between CPU and GPU rendering/material behaviour\nOperating system: macOS 13\nGraphics card: AMD W6800X Duo MPX module\n\nBroken: 3.3.1 (latest full release)\n\nI bought some assets which render with weird artefacts with the GPU, but work fine with CPU.\n\nThe assets are made by Bproduction (Florian Benedetto) on Blender Market. They are trees and vegetation models, which can be used individually or with Scatter 5.3. Simply put: they render properly with the CPU (Mac Pro, 24-core Intel), but render with horrible artefacts using the dual GPU. This doesn't happen with any other assets or materials I have.\n\nThe images below show the issue. I believe it's something to do with the material setup, but in any case it should render properly under both systems. Maybe it's an issue with macOS drivers?\n\n\n\n", "Strange shading behaviour when using boolean modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nWhen using a boolean modifier with an object that on a target object it uses the normals of the boolean object on the target object to determine the shading on the affected areas of the target object.\n\nWhen using a boolean modifier with an object that on a target object it uses the normals of the boolean object on the target object to determine the shading on the affected areas of the target object.\nThis means, that when using a boolean object that has shade flat on a target object that has shade smooth, the resulting object will have smooth shading everywhere except where the boolean operation happens.\nAdditionally, when using custom split normals (like e.g. weighted normals) it applies the custom split normals on the target object.\n\nThis behavior already seems pretty strange to me, since it almost always gives strange results since oftentimes the normals from the boolean object and the target object don't perfectly match, causing weird shading issues.\nI can understand that this may be an intentional feature, but it just brings so many problems, since normal editing modifiers after a boolean modifer like weighted normals don't affect the areas affected by the boolean modifier, meaning to tweak shading in these areas you have to tweak the normals of the boolean object and somehow make a seamless transition to the target object...\nApart from that it also causes some other problems, that are a worth a seperate bug report, which i will write shortly.\n\nAn additional problem with this is that shade smooth and shade flat aren't considered custom spilt normals, so after applying the boolean modifier the areas affected by the boolean modifier will change it's shading to that of the target object, since the shade smooth isn't applied as a custom normal.\nFor some reason that doesn't happen automatically, since directly after you aplly the boolean modifier the shading doesn't change immediately, instead it only changes when you \"recalculate\" the normals when using left click -> shade flat or shade smooth.\n\nA test file to demonstrate this behavior:\n[Test_file3.blend](Test_file3.blend)\n\nAfter applying the boolean modifier and \"recalculating\" the normals using left click -> shade flat or shade smooth the normals left from the boolean modifier will have vanished.\n\n\n" ]

[ "Regression: Wrong normalmaps on scaled objects\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.2.0 Beta\nWorked: 3.1.2\n\nCaused by 80859a6cb2\n\nWrong normalmaps on scaled objects\n\n[#98251.blend](T98251.blend)\n- open blend (two spheres of equal dimensions but different object scale)\n- observe the normalmap on the scaled sphere renders wrong\n\n{[F13093943](image.png) size=full}\n" ]

[ "Crash when change material on render with python\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.8+, 2.9 - 2.93.0 Alpha\n\nHey :)\nI’m trying to change material on a few objects during \"frame change\" with python.\nIn a viewport everything works fine but during Animation Rendering(cycles or eevee) it crashes immediately or a few frames later.\nMy system can’t handle more than 500 cubes.\n\n\n- Open \"change_mat.blend\"\n- Run script \"change_mat\" from Text Editor\n- Change Frame in Time-Line (0,1,2) // All cubes in the scene/viewport change their active material (Red, Green, Blue)\n- Press \"Render Animation\" => Crash // If it does not crash then duplicate more cubes\n\n[change_mat.blend](change_mat.blend)\n[change_mat.crash.txt](change_mat.crash.txt)\n\nMany Thanks!\n", "RAM fills up when switching scenes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\n\nIf the user switches from one scene to another the systems RAM fills up.\n\n1. open a task manager or something to watch RAM usage\n2. Create Suzanne and subdivide it to get a somewhat heavy object\n3. Duplicate Suzanne several 100 times to get a somewhat complex scene so that you can see your see RAM usage increase\n4. Click the \"New Scene\" Button and hit \"Linked Copy\"\n5. Repeat step 4 a couple of times and note that RAM usage will increase\n6. If RAM usage exceeds the available system RAM Blender will crash\n\nBlender apparently fails to clear the RAM from unused scenes when switching to or creating a new scene.\n\n\n", "Particle system removal\n- [ ] Convert hair particle system combs to curves objects with versioning\n- [ ] Remove explode modifier\n- [ ] Remove particle instance modifier\n- [ ] Remove non-hair particles\n\n\n**Needs agreement**\n\n- [ ] Decide how much of simulation and non-hair particle systems to replace with versioning vs. remove\n\n", "\"Add Modifier\" menu gets cut off inside narrow windows\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.5.0\n\nWhen the properties window is floated the modifier selection menu gets cut off\n\nShift click-drag the corner of an area type to float the properties area. \nGo to modifiers select a modifier menu is cut off.\n\n", "Crash on Changing Repeat value to -1 in Corrective Smooth modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 2.93.5\n\nNot Responding when I change the Repeat value to -1\n\n{[F11810617](image.png), size=full}\n\n", "Adjusting multiple properties at the same time doesn't work for all property types\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.90.1\n\nMost properties in blender can be changed for all selected objects by holding ALT while changing it. However, this doesn't work for all properties. For instance, the 'Rig Type' property in the Rigify add-on doesn't work. We can make it work by right click and selecting 'Copy to selected' but it should be possible with the ALT shortcut for consistency.\n\n**Steps to reproduce**\nWhile in Pose Mode select multiple bones\ngo into Bone Properties -> Rigify Type -> Rig type\ntry to change the Rig Type for all of them by holding ALT", "Armature modifier slows down any transforms on an object\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 2.92.0\n\nHaving the armature modifer on an object with a slightly high polycount slows down any transformations (move, scale, rotation) done to it in the viewport.\nEven with the modifier disabled in view still slows down its movement.\nThis slowdown is very impactful to the smooth playback framerate of projects.\n\nHere's a video of the steps (I started out in the default scene and deleted all the starting objects)\n0Bgx_1JEouc\n\n- Make a high poly mesh (Eg. Suzanne subdivided 5 times)\n- Add Modifier: Armature\n- Transform the high poly object (Mode, rotate ...) and note the delay in fps", "Fluid Sim Improve UI\nThis is a list of UI changes to discuss for the fluid sim for 2.83\n\n- [x] Move modular baking controls from settings to the cache rather than individual panels with they apply to???\n```\n I am not sure on this one, to have them all in one panel seems to make the most sense. \n```\n- [x] Create sub-panels of gas and liquid move appropriate panels within these\n- [ ] Mesh `Upres` rename to `Resolution`\n\n```\nThis makes it more clear which settings control all fluids and which control gas or liquids specifically \n```\n- [ ] Remove properties that do nothing: [D6770](D6770) and [D6760](D6760), `simulation_method`\n- [x] Use proper UI for viscosity presets.\n- [ ] Cleanup tooltips: example `\"PIC/FLIP Ratio. A value of 1.0 will result in a completely FLIP based simulation. Use a lower value for simulations which should produce smaller splashes\"`\n\n```\nThis example provides less information on what the property is then what it does.\n```\n- [x] Check for proper usage of `active` and `enabled`: Some props are using the wrong ones. `Enabled` should only be used for baking.", "GP: Time offset and Armature modifier causes glitches\nOperating system:WINDOWS10\nGraphics card:GTX1060\n\nBroken: 2.93LTS\n\n\n[#89433.blend](T89433.blend)\n\n- Open file\n- Move selected bone to left until it hits constraint, and then a bit randomly\n\nGP object will keep rotating in one direction and can be reset only by changing frame.\nSame happens when scrubbing in negative frame range.\n", "Crash/Assert with two modifiers that require normals data [e.g. DataTransfer]\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.90.0\n\nCrash/Assert with two modifiers that require custom normals data [e.g. DataTransfer]\n\nIn a Debug build:\n\n[#84664.blend](T84664.blend)\n- Open File\n- add another modifier that requires normal data (e.g. Displace), or just duplicate the existing modifier\n\n[un2.blend](un2.blend)\n- Try to go to edit mode of \"Vert.011\"\n- Blender will crash.\n\n", "Clearing library overrides from the object menu differs from the outliner\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.6.1 Release Candidate\n\nPlease see the attached movie. Using the \"wrong\" menu will cause the material properties panel to become unresponsive (beginning of movie) with overrides still in place until you use the outliner (end of the movie).\n\n1. Link some objects from a file\n2. Override them down to the materials\n3. Swap out some materials\n4. Use the clear library override from the object menu\n\nResult:\n\nThe material overrides aren't cleared, but you also can't access the properties panel anymore.\n\nExpected:\n\nThe material overrides should be cleared.\n\nWorkaround:\n\nUse the outliner instead.\n\n", "Text Object: D key is used for the Annotate Tool\nOperating system: Linux-5.4.0-104-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.0 Alpha\n\nIn the keymap preferences there is an option to use the Active Tools for shortcuts instead of the modal operation.\nIt's called \"Tool Keys -> Immediate / Active Tools\".\n\nIf this preference is used and you go into edit mode of a text object, you are unable to type in the letter `D`.\nIt will always make the Annotate Tool active instead.\n\n- Enable the \"Active Tool\" keymap preference\n- Add a text obejct\n- Enter Edit Mode\n- Type in a word with the letter `D` in it like \"Addon\" ", "Inconsistent naming for modes in the undo history menu\nBroken: 3.4 alpha\n\nIn the undo history panel, the \"Object mode\" entry is registered with the name of previous modes. Switch from sculpt mode to Object mode will create an undo step with \"Sculpt Mode\" name\n\nAs for the other modes entries, they have no naming standard. Some entries have \"Toggle\" written before, some have \"Toggle\" after, some don't have \"Toggle\". Also they all have \"Mode\" written except for texture paint. \nThe entries are as follows:\n\n\"Texture Paint Toggle\"\n\"Weight Paint Mode\"\n\"Vertex Paint Mode\"\n\"Toggle Edit Mode\"\n\"Sculpt Mode\"\n\nBased on the default startup;\nChange modes; \nCheck \"Edit -> Undo History\" menu.\n", "Sculpt Mode: Edit Voxel Size hotkey conflict\nOperating system: Win 10\n\nBroken: blender-2.90-51ac411ce80c-windows64\n\nThe \"Edit Voxel Size\" and the \"Repeat Last\" functions are using the same hotkey (Shift+R), and as a result, the \"Repeat Last\" command is not working in sculpt mode.\n", "Mistranslated Modifier Option on MacOS using Logitech Mouse\nOperating system: MacOS 12.6\nHardware: Mac Studio M1\nBlender Version: 3.3.0\n\nI use a Logitech M500s corded mouse (FW 53.00.0011) and I programmed the 4th and 5th buttons (on the side) using Logi Options (version 9.70.29) to Modifiers, Shift on one, and either Ctrl or Cmd (I have not settled on which is better) on the other. This has worked fine on all my software until Blender.\n\nAlso, since the Middle button on the mouse is critical in Blender, and since the M500s defaults to side scrolling (which I never use) when you tilt the wheel and these activate way too easily, I re-programmed both the tilts to emulate a Middle mouse button click. I left the normal wheel scrolling untouched. This allows me to click or tilt the wheel to get a Middle mouse click without worrying if I hit it correctly. This has worked great in Blender, both the normal scrolling and middle mouse clicks work as expected.\n\nWhat does not work in Blender is my using buttons 4 and 5 as modifiers when I combine them with other mouse actions. I was getting unexpected results, so I used Keymap to find out what was happening, and discovered the following:\n\nPressing button 4 (or 5) alone works: I see the appropriate \"Ctrl\" (or \"Shift\") appear but it does not map, of course, as I am only providing a modifier. I see the same effect on the status bar when I press the buttons in the editors. I see the guides correctly change for each modifier press.\n\nPressing button 4 (or 5) with a keyboard key works: Blender correctly maps the appropriate modifier (Shift, etc.) with the selected key. Same happens in the editors, e.g. when I use the modified mouse button for \"Shift\" and hit \"A\" on the keyboard, the Add menu pops up correctly.\n\nPressing button 4 (or 5) with mouse Left or Right buttons fails: Blender maps the appropriate modifier (Shift, etc.) but with button 4 (or 5) instead of with the pressed Left or Right button. If Blender is doing this elsewhere, it would explain why I am not getting expected results in the Editors.\n\nPressing button 4 (or 5) with a Middle mouse button (any as programmed) fails: Blender maps the appropriate modifier (Shift, etc.) but with \"Wheel Up\" instead of with the Middle button. Again, this could explain my unexpected results in the Editors.\n\nBy the way, when I press button 4 (or 5) and move the wheel, I get the same map, the appropriate modifier with the appropriate \"Wheel\" direction, although I can get \"Wheel Down\" with the actual wheel.\n\nAlso, when I press a Middle mouse button alone (any three): Blender correctly maps the Middle mouse button as pressed. As it does with any other mouse action except the buttons modified to be Modifiers.\n\nI tested for this problem on my Windows 11 system. Different mouse, G502, and different options software (G Hub vice Logi Options) but same Modifier settings (Shift and Ctrl) for buttons 4 and 5. It worked fine on my Windows system." ]

[ "Memory consumption beyond defined limit when entering-exiting Edit mode\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 2.93.0 Beta\nWorked: 2.79b at least with one hi-res mesh\n\nJust enter and exit edit mode consumes memory very fast.\nEditing UV in multiresolution object too.\nUndo memory limit do not help at all.\nI'll test more\n\n[leak.mp4](leak.mp4)\n\n" ]

[ "Grease pencil strokes are incorrectly blended with geometry in draw mode (depending on 'Fade Inactive Geometry' setting)\nOperating system: Win 10\nGraphics card: ATI Radeon 5700\n\nBroken: (example: 2.92b, 213f8*, master, 2021-01-28, as found on the splash screen)\n\n\nnote: this is due to `Fade Inactive Geometry` being ON\n\nWhen drawing grease pencil strokes with a black material the rendering style changes when...\n\n - ...switching between draw-mode and edit mode, or\n - ... toggling the overlay button in draw mode (even will all overlay options disabled).\n\n\nThis leads to noticeable rendering artifacts while drawing. Please consider the following screenshots:\n\noverlays on:\n\n\noverlay off:\n\n\nSome assumptions:\n- I assume that the blend modes are not correctly set and thus interfere with the MSAA.\n- The white artifacts are especially pronounced for thin strokes of all opacities. Increasing the thickness factor slightly decreases the problem.\n\nLoad the following blender file\n[stroke-test.blend](stroke-test.blend)\n\nStep by step:\n1. Start blender\n2. Create Cube\n3. Create Grease Pencil\n4. Add new material for grease pencil and change to black\n5. Draw strokes (with different opacities)\n6. Switch between Draw and Object mode or toggle Overlay-Toggle\n", "Strange shadow when rendering with GPU device\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\n\nThere's a shadow in the scene that doesn't make sense.\n\nI've attached a Blender file that I've tried to strip down as much as possible. Here's what I get (notice the strange shadow bottom middle)...\n\nThe odd thing is that if I delete/hide random objects in the scene, the shadow disappears.\n\nExample... hide any of the following objects:\nMISTY_MOUNTAINS_39_2k_c.001\nPlane.001\nAny object in the atmos folder\nObject_4.001\nthe whole quixel folder\n\nI know the shadow shape is cast from the volumetric cloud container shape (a spherical shape) but it's behaving very oddly and, as I use volumetrics in every single scene I ever create, I'm familiar with them behaving oddly. This is just a new one.\n\n[shadow error.zip](shadow_error.zip)\n", "Add option to show an image in black & white in image editor.\nCurrently we have channel sizzling in the image editor.\n\nAlthough this sounds an easy task I would prefer to have a color transform function for this OCIO. But that would need some discussion with Brecht + Troy.", "Frame counter while rendering does not respect blender's DPI setting\n4K screen, Windows 10, GEFORCE 960M\n\nBroken: bac1279\n\nThe cursor frame counter that displays while rendering is minuscule on a 4K screen, regardless of the DPI setting in Blender", "Fix preview flickering when using \"Adjust Last Operation\"\nTweaking properties in the \"Adjust Last Operation\" panel removes all previews for a moment, causing quite drastic and annoying flickering.", "Viewport: Texture limit size generates artifacts during painting\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nWhen limit size is lesser than the actual image size, this will result in artifacts at paint region.\n\n- Open attached file\n- Change Texture limit size to 2k or less (`Edit > Preferences > Viewport > Textures > Limit size`\n- Paint the plane.\n", "Artifacts around shadow catcher object\nOperating system: Win 10 PRO 19041.1348\nGraphics card: GTX 1080\n\nBroken: Official 3.0\nWorked: 2.9 lts\n\n{[F12718649](image.png),size = full}\n[头图制作B.blend](头图制作B.blend)\n\nLine is faintly visible at Y=472px height.\n\nThis doesn't happen when Denoise node Prefilter is set to Accurate, but when opening older files, Fast option is used by default.\n", "Blender renders wrong in viewport\nOperating system: macOS-11.2.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15\n\nBroken: version: 2.93.0 Alpha\n\n\n\n1) steps to reproduce:\n\nopen blend file [circular_circles_wave_emission.blend](circular_circles_wave_emission.blend)\n\n2) in viewport change to rendered view\n\n3) you will see:\n\n\n\n4) select the circles\n\n5) press tab and tab again\n\n6) you will see:\n\n\n\nwhich is correct\n\n", "Blender 2.91 - 2.92 beta - Image editor dither passes outside Render Result image\nOperating system: Linux-5.4.0-65-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa Intel(R) HD Graphics 5500 (BDW GT2) Intel 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.92.0 Beta\nWorked: version: 2.90.1\n\nDither seems to pass the outside image bounds in the image editor. It's only there if you are viewing the render result\n\n\n # **Load Factory Settings**\n - Top of the Blender window. Go to: File > Defaults > Load Factory Settings\n # **Go to Output properties inside the Properties Editor**\n - Bottom right editor > Output Properties Tab.\n # **Change dithering to 10 in Post Proccessing.** *It's same setting as image. As long as it isn't 0, it will give a dither to a rendered image.*\n - Inside Output Properties. Go to: Post Processing > Dithering > Set number\n # **Darken background in the World properties.** *If you don't change the background, both rendered background and UI blends in with itself.*\n - Go to: Properties Editor > World Properties [Tab]> Surface > Color [R,G,B]\n - I set my color to 0.01 value by clicking the color select\n # **Render Image**\n - Top of the Blender window. Go to: Render > Render Image\n - **Go to an Image Editor or find the newly opened Image Editor**\n - **Find the \"Render Result\" in the dropdown to view the newly rendered image.** *Dither specs/dark dots are found outside the rendered image.*\n\nA demo file isn't needed.\n\n[Dithering_Bug_1.mp4](Dithering_Bug_1.mp4)\n", "Render Animation in Video Editor doesn't warn that source video files are missing\nOperating system: Fedora 35\nGraphics card:\n\n\nBroken: 2.90.1\n\n\nThis is more of a feature request / usability improvement than a bug.\n\nI spent quite a few hours trying to figure out why a segment of a video from a Video Editing project was rendered all black. The segment looked fine in the video editor. It turns out that I had created a proxy for the video, then I accidentally deleted the non-proxy version of the video.\n\nIt would have been very helpful for Blender to open a dialog saying something like, \"Source video file foo.mp4 missing.\" It would have saved me literally hours.\n\n\n1. Create a proxy for a video in a Video Editing project.\n2. Delete the non-proxy version of the video.\n3. Render Animation\n", "Material rendered as black with motion blur and intersecting geometry (was:motion blur bug in geometry nodes)\nOperating system: Linux-5.13.0-23-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.2.2\n\nBroken: version: 3.0.0\n\nwhen i turned on motion blur seems that exactly when a instance intersects another instance is rendered as black\n\nwhen motion blur is turned on and two instances instect each other its rendered as black\nif frame 27 is rendered u are able to see the bug\n\n[domino line.blend](domino_line.blend)\n\nedit (Martijn) : Renamed to make the problem slightly clearer. \nIt doesn't happen every time, when rendering with Optix I can reasonably reliably reproduce it.\n", "KeyingScreen Compositor node emits \"black holes\" \nThe attacged folder shows a bug in the KeyingScreen compositor node.\n\nIn the Screenshot GreenPlateBug-Screenshot.png it can be seen in the above compositor window that some areas are filled with black\ninstead of grey / green.\n\nThat appeared after creating the \"last\" track marker (the selected / larger track marker in the below window).\n\nIf you remove that larger marker, the bug disappears.\n\nTo reproduce, open the attached blend file, close render window, disconnect / reconnect the viewer node to the keying screen node to\nsee in backdrop display.\n\nThe bug appeared in a different usage of the KeyingScreen node with much fewer track markers, but since the circumstances of\nthe bug to appear is unclear, i had to add a lot marker here.\n\n\nBlender version 2.80 (snap Ubuntu version).\nOS: Ubuntu 19.04 x86\nGraphics Card: Prime Laptop (NVidia / Intel combination) Dell Inspirion 4500 Laptop in Intel mode\n", "Color space seems wrong while painting in image editor.\nIn the image editor add a new image and with default settings just do a red line paint over a green line paint.\nDark zone appear in the falloff between red and green. it should not be there and should stay clear, not dark. \nI don't know why, but it looks like a color space issue. \n\ndark falloff not ok in blender:\n\n\nclear falloff ok in gimp:\n\n\nblender 2.8\nWindows 7 \n\n\n", "\"New Image\" UI improvement\nNOTE: This design is still under discussion and is incomplete.\n\n# Current Issue\n\nThe UI for image creation in Blender doesn't make it very easy to pick an optimal resolution and could be improved for usability.\n\n\nExperienced Blender users might know that you can:\n- Drag over both fields to edit both at the same time\n- Type `*` or `/` to multiply or divide the resolutions to keep standard resolutions\n\n# Proposal\n\nWe need to make these options more obvious and readily available:\n- Add a dropdown for common resolutions (128,256,512,1024,2048,...)\n- Add a toggle to either keep image square. When disabled choose resolution for both dimensions.\n- Add an option to type in a custom resolution\n\nThis still needs mockups and further discussion.", "clay strip brush (and probably any brush) create some strange shading and geometry artifacts...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\n\nclay strip brush (and probably any brush) create some strange shading and geometry artifacts...\n\n1. open blender, subdivide the default cube in edit mode a few times,\n2. add subdiv modifier with 3 levels (25,1 million in total) and apply modifier.\n3. go to sculpt mode and start playing with the clay strip brush and brush settings a little bit...\n4. change the sculpt plane to view plane, and add a stroke continuously in the edge of the cube, and some transparent shading bug appears when i go to check the back side of the stroke made, but this get fixed when i use the smooth brush a little bit in those boundary edges...\n\n\n5. change the sculpt plane to area plane again, and try on other edge the same again, and some grid topology starts to appear suddenly in the first stroke when drawing, but when i keep drawing it was less noticeable the artifact but was still there...\n\n\n\n" ]

[ "Screen Space Reflection rendered as black color\nOperating system: Win10\nGraphics card: GTX1080\n\n\nblender-2.80-40412499433e-win64\n\n\n\nScreen space reflections are rendered as black sometimes.\n\n\n\n\n\n" ]

[ "\"Emulate 3 Button Mouse\" conflicts with ALT left click, for instance to disable multipe modifiers on multiple objects\nOperating system: mac os ventura 13.4\nGraphics card: Apple M1 Max GPU 32cores Metal 3\n\n3.6\n\nEnabilng setting \"emulate 3 button mouse\" conflicts with ALT key left click operations, for instance when interacting with a panel. \nIn this case in the properties panel when ALT left clicking on an icon to disable multipe modifiers on multiple objects.\nthe cursor turns into a navigation cross and doesnt execute a click.\n\n\n\nGo to the settings menu/input - Enable \"Emulate 3 Button Mouse\" option.\n\nAdd a modifier to an object.\nDuplicate the object multiple times.\nSelect all the duplicated objects.\n\nGo to the modifiers panel.\n\nWhile holding down the ALT key, attempt to disable the modifier on all the selected objects by left clicking on the \"Display Modifier in Viewport\" icon or any other relevant modifier option.\n\nYou will find the cursor overtaken by the navigation mode, the cursor turning into navigation arrows and disabling a regular click operation.\n\n", "Vertex Selection Clipping Through Model\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.1\n\nWhen selecting vertices on an object, it will select the vertices on the face of the object and intermittently select all others behind as if in xray mode. \n\nGrab or scale icing vertices and pull.\n\n", "Transform cursor (patch included)\nRecently LMB-Drag was made to move the cursor *(edit, this has since been reverted)*.\n\nHowever this just moves the cursor under the mouse,\n\nit _could_ be useful to use transform here, it allows.\n\n- Drag, XKey to lock to an axis\n- ... Shift+Y to constrain to a plane.\n- ... Hold Ctrl to snap (snap to verts for example is handy)\n- ... Shift for more precise placement...\n... most other transform keys.\n\n\nOne reservation I have about this, is that you probably would often want to be able to snap to vertices and edges, and not have to depend on the current snap options in the 3d view header.\n\nSo we could override the snap options that transform uses.... but this seems a bit crappy too, since you may want to snap to faces in some cases, or even snap to grid.\n\nAs an alternative, we could just not bother attempting to integrate this with transform, and add snapping to the current modal operator (similar to how we have with the Ruler operator, which shares low level code with transform snapping)\nBut in that case we miss the axis constraints which seem like they would be nice to support.\n\n\nHere is a test patch to show how it works: [P87](P87.txt)\nNote, it crashes if you try to scale and its hard coded to LMB for cursor place, so its mostly a proof of concept.", "NLA: Support for Merge Strips\n**Preface:**\nI know this isn't the place for feature requests. However I plan on implementing this myself soon. This is more of a heads up and acts a way to get feedback before or while I'm working on it. Maybe I'm overlooking something or maybe the idea can be developed further. People can discuss problems and improvements here instead of within the patch comments itself. That way the important discussion can remain here for easier reference.\n\nEdit: Diff: [D8867: Feature: NLA Merge Strips](D8867)\n\n**Problem:**\nFor the animation layer workflow, the only way to combine strips into a single strip is to use the Bake Operator. However, it will always bake all active NLA strips to a single full replace strip. Effectively, this is a \"Merge All\" operator. There is no way to merge a selected set of strips. \n", "Select Loop Inner-Region issue\nWin8 64bit | GTX680\n\nBroken: 2.77 509270e\n\nWhen working with face loop, this tool doesn't always work as expected.\n\n\n\n\nNot sure if this can be a bug. Please check.", "Trim Tools: Depth location options\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar.\n\nThis is mostly based on the patch [D9622: Sculpt: Location option for lasso trim and depth info](D9622), which was never finished, even though the design is approved and requested.\nThe feature should add a \"Shape Location\" tool setting to define the placement of new geometry.\n\nThis task is for rebasing the patch and making any adjustments to make it work with the latest versions of the Lasso Trim and Box Trim tools.\n\n[2020-11-21 19-43-43.mp4](2020-11-21_19-43-43.mp4)", "Facedot Selection and Visibility Options\nGoal of this proposal is to have an alternative face selection style in x-ray shading for box, lasso, and circle selection tools. \nThe default right now is to have the facedot inside of the box/lasso/circle. \nMany users heavily requested an alternative similar to selection when Xray is off, where if the selection box/lasso/circle is inside any part of a face, it is selected. \n\n# Issues\n\nIt is useful to have an option, and sometimes necessary when a facedot selection is being difficult to deal with. \nA simple example: 499?u=lcas\nA more complex work example with big Ngon faces: watch?v=i9VUMvnFwkk\n\nThe only alternative to achieve this right now is to switch between vertex and face selection.\nHere's a visual example: 483\nBut this can also lead to unintentional results in the conversion of selections.\n\nHaving the ability to temporarily disable facedot visibility in x-ray can make it easier to look at a dense mesh as well.\n\n# Proposal\n\nFacedot display should be an option in X-ray. If face dots are visible in x-ray, they should be used for selection in box/lasso/circle. If facedots are not visible, use the alternative selection via their \"face area\" for box/lasso/circle. \n\nProbably don't carry this logic over when Xray is disabled though, because enforcing solid facedot select in this manner would disrupt the established method of \"face area\" selection in when Xray is disabled.\n\n# Open Questions\n\nDisabling facedot display in x-ray leads to at least two questions:\n1. Do you have two facedots (solid and xray) so that they can be toggled separately? I think this is good because it means if you want them on in xray only, and not in solid, you don't need to toggle them when going between solid and xray.\n\n2. Is the ability to disable xray facedots, and the alternative face area select in this mode, worth the potential confusion introduced for single click face select? \n\nI can't think of another way to select faces by single click in xray. So potential for not seeing facedots, and then needing them for single click, leads to some issues. If user wants to use the alternative \"face area\" select in x-ray, they will no doubt need to single click on faces in x-ray as well. I think another way to do this could be that instead of linking facedot selection with their visibility, we could have a checkbox somewhere like toolsettings. Or directional based (dragging clockwise vs counterclockwise or left/right) to choose either facedot or \"face area\" is also a pretty cool idea. This way you don't need to have facedots turned off to use the \"face area\" method, which alleviates some problems for single click selection of xray faces.\n\nOne more thing to consider is adding facedot selection to solid shading, this has some usefulness:\n514?u=lcas", "Tool with Dragmenu is hard to select using Stylus\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.1.0 Alpha\nWorked: (long time ago if ever)\n\nThe tools in the tools panel on the left, which have mutliple tools assgined to on button, are really hard to select using a tablet. This is because they open the menu on a timer and on even tiny drag input. (The timer seems to interact strangely with the tooltip timer, causing it to open immediatly sometimes, but that is not part of this report). The drag threshold for detecting a drag seems to be not influenced by the settings in the preferences (#92995, #84726). Also the drag causes the selection to be canceled on release leaving it not selected, while on normal tool buttons it is finished on release, meaning they will be selected. That is IMO the real bug here.\n\nI checked that the correct drag threshold is used by `WM_event_drag_threshold` on my device and it is! But the tool in the toolbar which is explicitly mentioned here seems to be not using it.\n\n\n\nself explanatory, just drag the toolbar buttons and observe. Also play with the setting \"Tablet/Mouse Drag Threshold\" to see that it in fact doesn't change anything.", "Missing visual representation of multiple selected color channels (`Blender Light` theme)\nOperating system: win10 64\nGraphics card: 1050ti\n\nBroken: (example: 2.91, default light theme)\nWorked: (2.79b)\n\nThis is how it was in 2.7x when selecting multiple RGB channels:\n\n In recent versions it misses visual representation of how many channels are selected until changing values to see if slider has been updated (left - nonselected, right - all channels are selected):\n\n\n\n - Open default scene\n - Go to material tab\n - Left mouse click any color slot\n - Left mouse click first color channel and hold it\n # While holding, slide cursor below to cover all channels\n\n\n", "Box Select Keyframes doesnt set an active keyframe\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Alpha\n\nWhen no keys are selected in the graph editor and you create a selection y box selecting no keyframe is set as active creating the dreaded issue of blender's having selection without active element to perform actions.\n\nopen the graph editor\ncreate several keyframe\ndeselect them all with a.\nselect with box select, none is active.\n\n**Expected solution**\n- When box selecting the keyframe that is closest to the mouse cursor (not the 2d cursor) should become the active one when box selecting, unless there is already an active keyframe in which case the active keyframe should remain.\n\n**Test builds for potential fix**\n\nThese builds not only fix the box/circle/lasso select by ensuring a keyframe is active, but also update the active FCurve so that the selection also contains the active FCurve.\n\n- [Windows](temp-#81874-box-select-active-keyframe-blender-2.91.0-87d654535c71-windows64.zip).\n- [Linux](temp-#81874-box-select-active-keyframe-blender-2.91.0-87d654535c71-linux64.tar.xz)\n", "Sculpt undo bug, mixing sculpt brush and multi-res modifier changes.\nWith current master (also 2.83).\n\nThe following steps show and error when redoing sculpt mode undo, when mixing multi-res subdivisions.\n\n- Startup file\n- Add multi-res modifier.\n- Enter sculpt mode.\n- *Repeat this 3-5 times.*\n - Multi-res subdivide.\n - Brush Stroke.\n\n- Now undo until the very beginning.\n- Now redo until the very end.\n\nWhen redoing, there are glitches where the multi-res has tearing/artifacts.\n\nSee video: [sculpt_undo_bug.mp4](sculpt_undo_bug.mp4)", "Setting/editing keyframes on multiple characters in pose mode doesn't work for Whole Character and Whole Character(selected Bones Only) options.\nOperating system: Windows 10 Home Edition\nGraphics card: GeForce RTX 2080\n\nBroken: 3.1.0 Master Build\nWorked: never\n\nSetting/editing keyframes on multiple characters in pose mode at the same time only affects the Active Character's Keys on certain insert key options.\nIdeally the insert key options work consistently for all selected characters bones.\n\n - Add two character skeletons to a new scene (Shift+a > Armature > single bone)\n - Select the first bone then Shift+Select the second one.\n - Switch to pose mode\n - hit \"a\" to select all. You should have both bones highlighted\n # hit \"i\" to insert a keyframe.\n - # if you choose Whole Character or Whole character \"Selected bones only\" it will only set a key on the bones for the Active Character.\n - # if you choose any other option it sets keys on both characters.\n\n\n\n\n\n\n**Additional comments:**\nIdeally Whole character would key all characters currently in pose mode.\nand Whole Character (Select bones only) would Key any currently selected bones regardless of which character they belong to.\n\nThe current functionality is confusing, if it is intended, the label should read \"Active Character\" and \"Active Character(selected Bones only)\"\n\nHowever when a user chooses to have multiple characters in pose mode it is because they are trying to pose and key them at the same time without having to switch back and forth with every adjustment. So having the ability to key multiple whole characters, or a random selection of bones belonging to multiple characters would be useful.\n\nThat said keying rotation/translation/scale&custom properties gets me what I need so this is not a blocker but it is something that could be improved for clarity as it will frustrate many animators unaware of this inconsistent behavior for the last two options.\nI was relying on \"Whole character\" and \"whole character (Selected bones only)\" to essentially key everything until I had to do multiple characters and I got confused for a while why my animations were looking janky until a dug into it.", "The bridge tool fails in a situation with multiple rows of faces facing each other\nWin10 Pro 64 bit; AMD Ryzen 2700X; Nvidia GTX 1060 6GB; 32 gigs RAM\n\nBroken: hash d1be30f (buildbot build May 4).\nWorked: never\n\nIn a situation where you have multiple rows of faces that face each other across empty space (with other areas where they face away from each other). The bridge tool (even with*loop pairs* checked) is unable to give priority to the direction the normals are facing. The result of this is that instead of getting nice bridges among the multiple rows of cubes, the tool produces faces that overlap and have zero area. As hinted, the*loop pairs* checkbox in this case does not do anything and the result is the same.\n\nOpen the .blend, invoke the bridge operator (the result is the same whether or not \"loop pairs\" is selected.\n\n**blend**\n[IffyBridge.blend](IffyBridge.blend)\n\n[IffyBridge.blend](IffyBridge.blend) (updated blend)\n\nAn additional note; I submitted this issue years ago, but it was never fixed and I couldn't find my old report. If the bug is not going to be fixed, then just close this as a todo item or with a \"won't fix\" tag.\n", "GPencil: Buffer stroke is only visible in the area that originated the drawing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.1 26.20.15019.1003\n\nBroken: version: 2.90 (sub 0)\n\nWhen creating two viewport, you can't watch the lines drawn at the same time\n\nCreate two viewport and move a little on the screen. Then start drawing. You will notice that the lines are not visible at the right time\n[bandicam 2020-04-21 14-03-29-287.mp4](bandicam_2020-04-21_14-03-29-287.mp4)", "Redo panel disappears during edits in Tweak tool\nOperating system: Win10 x64\nGraphics card: Nvidia 1070\n\n**Blender Version** \nblender-2.80.0-git.26d5a3625ed-windows64\n\nThe info panel for move disappears in edit mode if tweak mode is in action. This does not seem to happen if one uses \"g\" for grab instead.\n\n\n- Enable left click select, optionally select all toggles\n\n- In your space bar menu turn the select mode (W) on\n\n- Create a mesh and move into edit mode \n\n- Start grab and drag of verts and watch the move info panel at the left bottom\n\n- Now try the same thing with selecting a vertex then press \"g\" to move.\n\n" ]

[ "While in X-ray display, selection made via lasso select does not display properly\nOperating system: Darwin-18.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.8.38\n\n\nBroken: version: 2.80 (sub 51)\nWorked: (optional)\n\n\nWhile in X-ray display, selection made via lasso select does not display properly\n\n1 - Create a new general Blender file using the General template\n2 - Delete everything in the scene\n3 - Create a monkey mesh\n4 - Turn on x-ray display\n5 - Enter edit mode and make sure you're in vertex mode (I'm supplying a .blend file that starts at this state)[LassoXrayBug.blend](LassoXrayBug.blend)\n6 - Lasso select (ctrl-right drag) part of Suzanne (say, the chin)\n7 - **Observe that nothing appears to be selected**\n8 - Enter circle select (C)\n9 - Left drag the circle to any vertex\n10 - **Observe that the lasso select actually worked but was just not displaying**\n\n~chuck" ]

[ "Graph Editor - Multiple Windows Problem\nOperating system: Windows 10 - 64\nGraphics card: Radeon RX 5500 XT\n\nBroken: 2.93.0\n\nI split my single Blender window to two Graph Editor/Node Editor & 3D Viewport for my multiple screens. If my mouse hovering anything but node editor(Include Graph editor or 3D Viewport) and I press play that timeline cursor like starts twitching.\n\nCreate two different windows. Graph Editor and 3D Viewport. Than press play on 3D Viewport window selected.\n\nTest file:\n[Bugfile.blend](Bugfile.blend)\n\nVideo:\n[2021-06-10 15-35-41.mp4](2021-06-10_15-35-41.mp4)", "Alt modifier key to disable node auto-connection\nWe often get requests to make the behavior of auto-connection when placing nodes optional. This is because it can be tricky to place a node without connecting to overlapping links, among other reasons.\n\nA simple solution discussed in earlier [sub-module meetings ](22309) was is using the `alt` key to disable the auto connection.\n\n", "\"Add Modifier\" menu gets cut off inside narrow windows\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.5.0\n\nWhen the properties window is floated the modifier selection menu gets cut off\n\nShift click-drag the corner of an area type to float the properties area. \nGo to modifiers select a modifier menu is cut off.\n\n", "Wayland: Unable to access window position, finding the window under the cursor doesn't work\nWayland can't access window positions. From what I can tell this is an intentional limitation and there aren't ways to access this information.\n\nThis means functions such as `WM_window_find_under_cursor` doesn't work.\n\nFrom the user perspective the following functionality wont work.\n\n- \"Swap Areas\" / `SCREEN_OT_area_swap` isn't able to swap areas with another window.\n- Some \"Eyedropper\" functions such as `datadropper_win_area_find` wont be able to access other windows.\n- Dragging items between windows doesn't work (see `wm_event_cursor_other_windows`).\n\nCurrently `GHOST_SupportsWindowPosition()` has been added to prevent other windows being found when they shouldn't be.\n\n\n---\n\nNOTE: there is a proposed solution that might allow Blender to restore the positions of windows saved in a file: see: 18\n", "File browser buttons disappear on undo in another window\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\n- All versions since the new file browser was introduced are affected by this\nWorked: Never\n\nI've tried to save file with CTRL+S and by accident pressed my LMB on a viewport. Because of that mistake, I pasted object in my scene, instead of pasting file name in \"Blender File View\" window. So I tapped CTRL+Z (while still being active in a viewport) and whole panel with buttons \"Save file\", \"Cancel\" in \"Blender File View\" window disappeared. I've tested this on a completely new empty blender file. Pressing on a viewport didn't recreate that effect (probably, because nothing was there). But pressing on outliner or timeline have the same issue.\n\n- Open Blender\n- CTRL+S\n- Press LMB on an Outliner\n- CTRL+Z\n\n[UI bug.blend](UI_bug.blend)", "Outliner Floating window Drag & Drop to Geometry Nodes editor not working\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: I don't know if it ever worked\n\nDragging and dropping objects from the outliner to the geometry node editor is not working\n\nFloat outliner to be its own window\ndrag and drop an object from the node editor to the geometry nodes\ndoesn't work.\n\n", "Nodes: Node Name are overlap Icons in header\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: version: 4.0.0 Alpha\nWorked: 2.78...\n\nCropping text of node Name sometimes allows a collision of text and icons:\n\n\n1. Any node editor.\n2. Create node group.\n3. Change node scale to see effect for narrow header.\n\n", "Grease pencil. Mask not working when masking layer has more than one keyframe\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nWhen my masking layer has only one keyframe, masked layers display as expected. When my masking layer has more than one keyframe expected masking doesn't happen.\n\n* open .blend (the mask layer has two keyframes, both having the same filled shape)\n* expected result: the strokes on the 'marks' layer that intersect the shape on the mask layer are always visible\n* actual result: the strokes on the 'marks' layer that intersect the shape on the mask layer are only visible after i delete the second keyframe on the 'mask' layer\n\nWhile dragging the timeline play head the marks layer appears as expected, correctly masked. But when i release the mouse button the marks layer disappears entirely again.\n\n[isthisamaskbug.blend](isthisamaskbug.blend)", "Space Mouse not working properly\nOperating system: Mac OS Ventura 13.3.1 (a)\nGraphics card: Apple M1 Max\n\nBroken: 3.5.0\nWorked: 3.0.0\n\nNo buttons of the Spacemouse work anymore.\nEverything worked with Blender 3.0.0 and 3D Connexion Driver 10.7.0.\n\n1. Install latest 3D Connexion Driver 10.8.0.\n2. Set up some buttons in 3DxWare 10 like:\n a. \"Button 1\" = Keystroke \"Tab\".\n b. \"Button 2\" = Keystroke \"1\".\n c. \"Button 3\" = Keystroke \"2\".\n3. Start Blender.\n4. Try to switch between Edit and Object mode with \"Button 1\":\n a. No Function.\n5. Try to switch between select Modes with \"Buttons 2-3\":\n a. No Function.\n6. Try to select more Objects with holding \"shift\" on Space Mouse:\n a. No Function.\n\nI miss the combination so hard, it's impossible to work without my space mouse, I'm used to it for a decade. :(\nThe Space Mouse works fine in all other Programms, its an Blender Issue exclusively.\n\nAdditional Infos:\nSometimes restarting Blender multiple Times, re-installing it, fixes temporary the function of the basic Keys \"shift, cmd, etc\". The other buttons never work. They worked always in the past and still work in all other programs where I use the mouse. ", "creating a new collection in linked scene (same blend file) causes objects placed in it to dissapear from the outliner in the first scene.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\nWorked: unknown\n\nCreating a new collection in linked scene (same blend file) causes objects placed in it to disappear from the outliner in the first scene.\n\n1. Open default blender scene.\n2. Click the new scene button and choose linked copy.\n3. In the new scene, create a new collection and drag the cube into it.\n4. Go back to the first scene.\n5. The cube is gone and the new conllection not listed in the outliner.\n\n", "3D Paint Mode stencil disappears when panning viewport.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 2.93.4\n\nWhen panning viewport in 3D paint mode with stencil mask enabled, the stencil mask disappears when moving the viewport, however does not disappear when zooming it, which indicates it's not a technical limitation.\n\n1. Enter 3D paint mode\n2. Enable texture mask, select some texture and set mapping to stencil\n3. Navigate the viewport\nResult: The stencil disappears when moving the viewport, which makes it very difficult to line up stencil projection with the 3D geometry\nExpected: The stencil does not disappear when navigating the view\n\n", "Physics / Simulation Nodes Baking User Interface\nThis proposal unifies the Physics panels to be closer to the modifiers. There is no functional change besides the user interface.\n\nThen it adds the Simulation panel as a panel which is always visible for the objects. It is not part of the Add Physics.\n\n\n\nOpen questions:\n* Should Delete / Bake All Dynamics also take into account Simulation Nodes?\n\n", "GPencil: Modifiers don't work after separate strokes and use hide in outliner [issue with multiuser gpencil objects and modifiers]\nOperating system: Ubuntu 20.04\nGraphics card: Mesa Intel® HD Graphics 620 (KBL GT2\n\nBroken: (2.83.3)\n\n\nThe mirroring of a grease pencil object briefly stops being visible after performing a stroke separation.\n\n1. Boot up Blender's default 2D animation workspace\n2. Draw a stroke on the GP object \"Stroke\"\n3. Add a mirror modifier to the object.\n3. Draw another stroke\n4. Change to edit mode and select the new stroke\n5. separate said stroke with P, creating \"Stroke.001\"\n6. Still on edit mode, click on the 'eye' icon on the outliner to make \"Stroke\" invisible\n7. Click on the eye icon again, the mirroring will have stopped being visible.\n8. Clicking twice on the \"Display modifier on viewport\" button in the modifier tab fixes the issue.\n\n**Status**\nThe \"wrong usercount when separating\" is fixed, see 4251a87bf6, however the underlying issues with multiuser gpencil and modifiers still remains.\nTo reproduce:\n- add a gpencil stroke\n- {key Alt + D} duplicate linked\n- add a Thickness modifier.\n- Hide/Unhide the object in outliner.\n", "Hotkeys malfunction after leaving text field with no input using IME(Chinese/Japanese/Korean)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.0.0 Release Candidate\nWorked: Unknow\n\n---\n\n\nUsing IME(Input method editor) like Chinese/Japanese/Korean IME, activate a text field then go back to 3D viewport while inputing nothing will make some hotkeys malfunction.\n\n\n - Default scene with any IME listed in the following image.\n - Click the default cube's name text field to activate the text field.\n - No input, go back to 3D viewport by clicking the 3D viewport area or right-clicking to cancel the operation.\n - Test {key A-Z}, for example press {key G} to transform the cube, the keys shouldn't be functioning.\n\n**Notes:**\n\n - After pressing {key A-Z}, similar IME-poping-ups might be shown as in these images: {[F12405595](图片.png)} The inputs are handled by IME but not being properly functioning like {key G} would not move the selected object.\n - Some other keys like {key 1-9}, {key Shift}, {key Ctrl}, {key CapsLock} and {key Space} are still functioning.\n - After the bug is reproduced, it is able to press {key Shift} to switch the mode of IME to fix the malfunction. And if right after canceling the text field input operation, press {key Ctrl RightMouseBottom} to finish a lasso select can also walk around the bug (but if there are already some inputs after the operation is canceled, doing {key Ctrl RightMouseBottom} won't fix the bug).\n - I found at the time been, Blender will automatically switch the IME modes (sorry I am not sure about which patch brought this feature), that means if in 3D viewport, the IME is automatically set to \"English\" mode and all inputs will not be handled by IME (this is the proper function); while in text field the IME mode is automatically switched to for example \"Chinese mode\" in Chinese IME. This \"auto-switching\" behavior is lost if the said work around is used to fix the bug, and in my case only after restarting Blender will bring back this feature.\n - I have tested a 3rd party Chinese IME \"搜狗输入法\" and in my opinion it has the similar bug as \"Microsoft Pinyin\": ", "Resample Node Deletes All Curves.\nWindows\n\n3.2-3.4\n\nThe ResampleCurve node deletes curves it their lengths are less than the length of the ResampleCurve node. I expect it will leave Lines at least. In Houdini a resample node doesn't delete curves. Could you please check it out?\nProbably you could add a checkbox to leave curves with less length.\n\nMy Blend file:\n[tmp_1.blend](tmp_1.blend)\n\n\n\n\nOpen my blend file and mute/unmute the CurveResample node." ]

[ "Nodes teleports when the mouse touches the border of the editor\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14761 Core Profile Context 21.10.2 30.0.13025.5005\n\nBroken: version: I think this has been in blender for some time, but I first noticed it around 2.9x\n\n\nSometimes after adding a node, it pops out the frame to somewhere far from it was supposed to be. It doesn't happen when moving a node that was added before, because the view moves with the cursor(maybe it also should be moving when you add a node).\n\n\n- add a node with shift a and then bring it to the border of the editor.\n- bring it to the border of the frame and keep moving it, sometimes it happens instantly\n\n[2021-10-22 23-49-19.mp4](2021-10-22_23-49-19.mp4)" ]

[ "Geometry-node object-info rotation&scale outputs values are False if scale is negative \nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0\n\nthe object info rotation & scale values are false if the scale of the sampled object is negative \nsee video, where i compare with simple drivers of the object transforms\n\n[dffdsdfdsfsfd.mp4](dffdsdfdsfsfd.mp4)\n[buggy transforms.blend](buggy_transforms.blend)\n\n", "Hidden Particle paths draw solid [2.79 draws them half transparent]\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.81 (sub 15)\nWorked: (optional)\n\nComparison of particle hiding Blender 2.81 beta and 2.79. I wrote earlier that the particles are not hiding, and this is so fixed?\n\n", "When using mask modifier, particles get also generated from the origin\nOperating system: macOS-10.14.4-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.23 355.11.10.50.10.103\n\nBroken: version: 3.0.0\n\nI'm emiting particles from an object. I use the mask modifier so that the particles are generated only in some areas. Particles will be generated from the origin, even if there's no geometry there.\n\nPlay the animation from the attached file. You will see a column of particles coming from the origin. \n\n[Bug.blend](Bug.blend)\n", "Incorrect rotation using driver or constraint\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\n2.79, 2.80, 2.81, 2.82, 2.83\n\n\nBone \"target\" is animated on y-axis.\n\"Target\" turned close to gimbal lock gives the wrong result for Transformation constraint, Copy Rotation constraint, Driver.\nUsing the driver, you can see how the radian (degrees) value jumps and does not match the value of the target object.\nOnly using the driver via copy data path creates the correct result.\n\n[rotation.blend](rotation.blend)\n\n[rotation_.mp4](rotation_.mp4)\n", "particle system collisions stop working outside 255 blender units\nOperating system: windows 10\nGraphics card: gtx 1080\n\nBroken: 2.79b 2018-3-22, \nparticle systems do not interact with faces which are oriented in the axis where the face is more than 255 blender units away from the origin\n[name ]([particleproblem.blend](particleproblem.blend))", "Use proximity for edit mesh mirror and mirror selection operator\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nIt is hard to select the corresponding vertex on the flipped axis side when the topology is non symmetrical and the corresponding vertices on the flipped axis side is slightly offsetted.\n\nIn order to fix this, it would be great with a \"proximity slider\" that selects vertices on the axis flip side that is within the range of the corresponding coordinate of your current selection.\n\n---\nUI mockup for viewport options\n\n\nUI mockup for operator \"Select mirror\"\n\n---\n\nUse cases below:\n---\n\nCurrent behavior works great when **Topology mirror == True** and the mesh on both side of the axis is connected (and the topology was \"built symmetrical\"). Even if vertices on the axis flip side is slightly offseted.\n\n[topology mirror.mp4](topology_mirror.mp4)\n\n---\n\nCurrent behavior does not work when the topology is built symmetrical, but the topology on both side of the axis is not connected (like the eyes in this case). And the mesh is slightly offsetted on the axis flip side.\n\n[symmetry does not work.mp4](symmetry_does_not_work.mp4)\n\n---\n\nCurrent behavior does not work when the topology is not completely symmetrical and the vertices on the axis flip side is slightly offsetted.\n\n[slightly non symmetrical topology.mp4](slightly_non_symmetrical_topology.mp4)\n\n\n\n\n", "Object collision for particle nodes\nHere is the current status of the node particle collisions:\n\nIt currently handles:\n\n| Static objects| Moving objects | Objects with mesh deformations |\n| -- | -- | -- |\n| [recording_static.mp4](recording_static.mp4) |[recording_moving_plane.mp4](recording_moving_plane.mp4)|[recording_moving_wave.mp4](https://archive.blender.org/developer/F8571963/recording_moving_wave.mp4)|\n\n\nWhat is left to do is:\n- - [x] Add a recovery method for when particles are pushed or somehow gets inside colliders (when particles are less than their radius away from a collider). This will also allow particles to have a dynamic radius. (Haven't tried with dynamic radius yet, but it should work in theory)\n- - [x] Change how face normals are calculated. Now it simply uses the face normal. But this is an issue when the particles collides on the edges or verts of the triangles. This leads discontinuities in the collison mesh as the transition area between the faces is not smooth.\n- - [x] Make colliders be able to push particles along even if the dampening or friction is so high that the particle will not have any velocity.\n- - [ ] We will probably have to track acceleration in addition to velocity to get high quality simulation (like in the old particle system). Now I think some weirdness can be attributed to us lacking acceleration tracking. \n- - [ ] Look over and port older properties from the old particle system (friction, stickyness, and so on). Flocking (Boids) and other behaviors will be handled in other nodes (not inside this collision node).\n- - [ ] Hook up variables to the particle nodes themselves. Currently most things are hard coded.\n\n", "Blender 3.2.1 - Particles - Particles generate differently on Linux vs Windows\nOperating system: Linux-5.4.0-122-generic-x86_64-with-glibc2.31 64 Bits - Windows 10 x64\nGraphics card: NVIDIA GeForce GTX 1080 - NVIDIA RTX 3080\n\nBroken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac\nWorked: 2.7.9\n\nParticles render differently between windows and linux.\nLinux:\n\n\nWindows and MacOS:\n\n\n\n[particleTest_v001.blend](particleTest_v001.blend)\n\n1. Open attached blend file on a Linux machine\n2. press f12\n3. save image to network drive\n4. open attached blend file on a windows machine\n5. press f12\n6. open the image from the network drive in another window\n7. press alt tab to flick between them and see that the particles generate differently.\n\n", "Changing the seed value is not working for particle children hair\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.0\nWorked: I duuno\n\nEven changing the value of the seed, the position of the children's hair still remains the same.\n\n\n\n\nA sample blender file is attached below.\n\n", "TexBlendNode Python property tooltip incorrect\nBlender 2.8 \n\nI can not change the Progression or the Flip Axis for the Tex Blend Node with python. \n\nIt returns with an error that says \" no attribute use_flip_axis\". I thought this was my fault so I reached out for help on the Stack Exchange> [here ](how-do-i-change-the-blend-node-to-vertical?)\n\nThey think this is a bug or missing API?.. I checked online but could not see this bug reported so I thought I would let you guys know.\n\nI have used a rotate node to work around the problem but I am sure you guys would be able to fix this issue with ease.\n\n[#69973.blend](T69973.blend)", "Particles \"Numbered\" Incorrectly When Generation Time is Influenced by Texture\nSee attached - probably not relevant.\n\nBroken: 2.90 - see attached\n\nA keyed particle system sends particles from one particle system to another particle system. Normally the ordering is respected: the first-generated particle in one system gets sent to the first-generated particle in the second system, same for the second-generated particle, and so forth. This does not work though if a texture is used to generate a particle system. Various visual effects rely on the ordering being respected.\n\nCreate a plane mesh. Add a particle system to it, physics none, starting at time 1 and ending at time 10 with 10 particles. Add a blend texture so the particles are generated from one side to another. Add a second particle system on a second object. Now create a keyed particle system on the second object going from the first particle system to the second particle system, starting at time 15 and ending at time 24 with 10 particles. Display its particles in a distinct way (e.g., as red spheres). Step through the simulation frame by frame. Note the order that the particles appear on the plane mesh (first particle system). Then at frames 15, 16 and 17 note the order in which the keyed particles appear. They appear in a different order, whereas, if a texture is not used but the random seed is used, the keyed particles will be created in the same order that they were created in the first particle system regardless of the chosen random seed.\n\n[system-info.txt](system-info.txt)\n[Particle Numbering Bug.blend](Particle_Numbering_Bug.blend)", "Transform orientation undo is inconsistent.\n\nBroken: 3.0\nWorked: ?\n\nTransform orientation undo is inconsistent. It works in object mode, but doesn't work properly in edit mode. In edit mode it sometimes won't undo, or undoes together with another different step(like changing mode, or moving vertex).\n\n- Open default startup;\n- Change the Transform Orientation from Global to something else\n- Undo/redo - it works;\n\n---\n- Reopen default file\n- Go to edit mode\n- move vertex\n- Change the Transform Orientation\n- undo multiple times - Will never undo the Transform Orientation. (now deselect cube and perform undo operation: will revert selected transform orientation)\n\n", "Object rotation increases render time more than 10 times.\nTested with windows 7 64bit and windows 10 64bit.\nCPU ryzen 5 1600\nGPU GTX 780\nRAM 8GB GDDR4\n(bug appears on other computers too)\n\ntested with 2.79 and 2.8\nWorked: (optional)\n\nIf I rotate object for about 45 degrees around Z axis render time increases more than 10 times.\nBut in preview mode there is no difference in render time before and after rotation.[test.blend](test.blend)\njust rotate the object on attached blend file around Z axis about 45 degrees and compare render times before and after.\n10seconds for 2000 samples before rotation and about 10 minutes after.\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n", "Cycles: tapering hair transparency fails in '3D Curves' mode [regression] (probably caused by embree)\nOperating system: Ubuntu 20 LTS and MacOS Mojave\nGraphics card: Quadro p2000\n\nBroken: 2.92 and latest 2.93.0 alpha 5f1f233dc97de34f6be0f51edd3cbf2d8247fbda\nWorked: 2.82a and 2.83.4\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nSetting a transparent BSDF shader to hair in 3D curves mode yields a visible error where parts of the hair are black.\nThis issue is visible in the viewport and at render time. It affects both CPU and GPU rendering.\n\nIn ribbons mode, transparency works almost as expected. I noticed that when hair strands overlap and they have transparency, they are not transparent but they take the background opaque color instead, so the hair strands below are \"covered\" with background color.\n\nembree\n\nbefore embree\n\n\n[#86500.blend](T86500.blend)\nOpen file and switch to rendered view\n\n---\n\nOriginal report:\n\nInitial setup in viewport: a cube with 20 hair strands:\n\n\nRender in version 2.83.4:\n\n\nRender in version 2.92+\n\n\n\nAttached is a .blend file example (so that you don't need to reproduce the steps below). [transparent_hair_curves_issue.blend](transparent_hair_curves_issue.blend)\nIf you run it on Blender 2.82a, rendering should show only a cube. Blender 2.92+ will show the issue.\n\nSteps:\n- Open a new default blender scene with a cube\n- Choose Cycles renderer\n- Under Render Properties > Hair, select 3D Curves\n- Add a hair particle system to it\n- Lower particle count to 10\n- Set segments to 5\n- Enable Hair Dynamics, play the timeline for a while until hair bends\n- Go to simulated frame 30 (just an example)\n- Scroll down in psys panel to Render, enable b-spline with steps 2\n- In Timing, set start to 0.361 (just for testing purpose)\n- In Hair Shape, set Diameter Root 0.5, Tip 1, Radius Scale 1.00\n- Render in viewport or to an image (same result)", "Particles appear above where they should not appear (with rigid bodies)\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 780M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 2.92.0\nWorked: 2.79\n\nI have a cube that is an active rigid body that falls on a floor (another cube) that is a passive rigid body. The falling cube has a particle system. I tell the particles to start in the frame that coincides with the impact of the cube with the floor and to finish emitting one frame behind. The problem is that at the moment of impact this particle appears in the air, I attach an image of when it appears and then when it disappears everything continues normally. Particles only appear above when it coincides with the same frame in which there is a collision in the rigid body. In 2.79 this does not happen. In 2.92 and 2.93 if it happens. Greetings, I attach an example scene made with 2.92 stable.\n\n1 add cube an scale (this is the ground) \n2 add pasive rigid body to ground\n3 create a cube an put an raise it up a little\n4 add rigid body active to the cube above\n5 add particles to the cube above\n6 in the same frame as when the top cube collides with the ground and to finish broadcasting one frame later\n7 Now we play and we see that at the moment of impact, particles appear above where they should not appear.\n\n\n\n\n[particles_bug_when_collide_rigid_body.blend](particles_bug_when_collide_rigid_body.blend)" ]

[ "particle rotation option not working (10 reports)\n%%%Actions to redo:\nSet the physics to none, tick the particles rotation option, set the particles rotation to something other than none, untick the particles rotation. The particles rotation will remain....%%%", "particle rotation illogical\nOperating system and graphics card\nWindows 7 64 Bit\n550Ti\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\nBlender 2.67, 2.69\n\n\nHi,\ni wanted to create a mass of people standing randomly arround. Therefor i created a ground with a particle system and set up an object (human) as an replacement for the particles. 2nd i set up randomness for rotation arround z axis. But that doesn't work as aspected. The object which are duplicated by the particles have a wrong orientation. While my reference object (human) is standing, the duplicated objects are lieing. Try it out and you will see that its illogical using. So its nothing critical but its confusing when you use it the first time.\nI attached you a small scene showing the problem.\n(of course i've checked the transformation properties of my object, they are right)[problem.blend](problem.blend)\n\nGreets\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n", "Particle rotation is not working without ticking \"Dynamic\"\nLinux Ubuntu64, 16gb RAM, 2*GTX560ti OC 2GB, SSD\n\nBroken: 2.64up - Newest trunk\nWorked: 2.63 !\n\nAs you can see, the bug is pretty old already (maybe introduced with the reorganization effort of the rotation panel) - I would like to see it fixed for 2.70, but the assignee should decide. Will add Lukas so he could pick the right one or do his magic...\n\nBug1:\nParticle rotations should be possible without having to check \"Dynamic\" on the rotation panel - the description says \"Particle rotations are effected by collisions and effectors\" -> So I would understand that (read the manual too) this checkbox should only influence the rotation when particles are bouncing off or led through effectors. \nBut without ticking this box, no particles are rotating through their travel.\n\nI'll append a simple file with the default cube. Just hit alt+a one time with Dynamic checked and one time without it...\n\nBug2:\nApart from that it's really screwing the simulation oftentimes, so I have to change the particle count back and forth to reset the animation - it's really a mess from a users perspective.... Lukas_t, node particles to the rescue ;)\n\nGreetings, Thomas" ]

[ "Disabling Collections in the Outliner filters overlaps the Mode Column icons with the expansion arrows\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.4.0 Alpha\n\nIf you disable the \"Collections\" filter in the Outliner, the space of the Mode Column disappears even if the \"Show Mode Column\" filter is enabled, and the icons of the Edit Mode Column overlap with the object expansion arrows.\n\nAdd any mesh object, disable the Collections filter in the Outliner, enter edit mode.\n", "Assign Shortcuts: creates shortcut in the \"wrong\" space\n**OS**: Linux 5.3.8-arch1-1 x86_64\n\n**Blender version**\nBroken: 2.8x (up to and including fc79d27951)\n\nWhen using the context menu to assign shortcut to a button or checkbox, the shortcut is created in a wrong space, which may lead to error popups when pressing that shortcut with mouse hovering over a different space.\n\n\n1. Load the default scene.\n2. In 3D viewport, expand the Overlays popover, right-click the Wireframes checkbox and assign a shortcut through the context menu.\n3. Note that shortcut works while the mouse is over the 3D viewport.\n4. Move the mouse over the Properties and try pressing the shortcut. You'll get an error popup.\n\nThis is due to the shortcut being created in the Window space, not 3D View space.", "Can't undo the keyframe change in edit mode\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nWhile in edit mode, when you hit Undo in the graph editor after moving a keyframe, the graph doesn't change.\n\n- Animate anything using a couple of keyframes.\n- Change to edit mode in viewport\n- Switch timeline to the graph editor (not necessary, you can keep timeline as it is)\n- Select a keyframe and move it\n# Hit undo\n\nResult: The graph editor stays the same\n\nExpected: The move you just made in the graph editor should be the only thing being undone!\n\nTest file with first four steps included\n[#97700.blend](T97700.blend)", "Windows uninstaller does not cleanup its registry keys after uninstall, leaving a non functional open with entry.\nOperating system: Windows 10 2004\n\nBroken: 2.90.1\n\nAfter uninstallation of blender, non functional open with entry is left behind pointing to the location of blender.exe\n\nI dug around a bit and found the registry key responsible is \n```\nHKEY_CLASSES_ROOT\\blendfile\\shell\\open\\command\n```\nThis key should be deleted after uninstallation of blender\n\nUninstall blender and try to open a .blend file. This shows up: ", "Measure tool undo repitition\nOperating system: Arch Linux | Kernel: 5.11.8-arch1-1\nGraphics card: GTX 1070\n\nBroken: 2.93.0 alpha | Branch: master | Commit: 715c7462969e6075859f44a64bb4eb68d056345b | Date: Wed Mar 24 11:00:31 2021\nWorked: I also tested it in 2.91 and it is the same issue\n\nIf you draw multiple measurements with the measure tool and then try to undo one it instead undos the two most recent ones. Any further undo's after that will undo one as expected.\n\n1. Use the default startup file\n2. Take out the measure tool\n3. Draw a few lines (more than 1)\n4. Ctrl-z undo (two lines will disappear instead of one)\n5. Ctrl-z undo again (one line will disappear as expected)", "Crash. Script changing values of a prop attached to object by an operator popup crashes the app\nOperating system: Windows 10 Pro\nGraphics card: NVidia GTX 1070 Ti\n\nBroken:\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen used from a plugin, operator that uses wm.invoke_props_popup(self, event) to draw(and change) properties from a property group attached to an object (constantly) crashes the app.\nWhen same code is used from the blender scripting area, the app does not crash, but after initial change of the param, the property is grayed out(seems like a bug as well).\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7DDBEA080\nModule : c:\\Blender28\\program\\blender.exe\nThe terminal process terminated with exit code: 11\n\n1) Create a testing_grounds.py file\n2) Fill it with code provided below\n3) Install as an addon\n4) Select an object\n5) Launch the operator(through space, typing \"TEZZT\")\n6) Change the value of the property by clicking and dragging the value;\n7) Repeat step (6) a few times if the app hasn't crashed yet\n\n```\nbl_info = {\n \"name\" : \"TestingGrounds\",\n \"author\" : \"ChieVFX\",\n \"description\" : \"\",\n \"blender\" : (2, 80, 0),\n \"location\" : \"\",\n \"warning\" : \"\",\n \"category\" : \"Generic\"\n}\n\nimport bpy\n\nclass SomeParams(bpy.types.PropertyGroup):\n float_value : bpy.props.FloatProperty()\n\nclass TestOp(bpy.types.Operator):\n bl_idname=\"testing_ground.tezzt\"\n bl_label=\"TEZZT\"\n bl_options={'REGISTER', 'UNDO'}\n\n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_popup(self, event)\n \n def execute(self, context):\n print(\"Im fine\")\n return {'FINISHED'}\n \n def draw(self, context):\n layout : bpy.types.UILayout = self.layout\n obj = context.object\n some_params = obj.some_params\n layout.prop(some_params, \"float_value\", text=\"Prop popup test\")\n \nclasses = [\n SomeParams,\n TestOp\n]\n\ndef register():\n for cls in classes:\n bpy.utils.register_class(cls)\n \n bpy.types.Object.some_params = bpy.props.PointerProperty(type=SomeParams)\n\n\ndef unregister():\n for cls in classes:\n bpy.utils.unregister_class(cls)\n \nif __name__ == \"__main__\":\n register()\n bpy.ops.testing_ground.tezzt('INVOKE_DEFAULT')\n```\n", "Changing driven rigidbody constraint value does not invalidate cache\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\n\nChanging driven rigidbody constraint value does not invalidate cache.\n\n[0385-5151.avi](0385-5151.avi)\n\n[#83561.blend](T83561.blend)\n\n- Open file\n- Change Y location of Empty.006 - pinned in upper editor. This should change velocity of motor of Empty.005\nThis should invalidate rigidbody cache, but it doesn't\n\n[T83561_simplified.blend](T83561_simplified.blend)\n", "Custom property settings not preserved when changing its type\nBroken: version: 3.0.0 Alpha\n\n- Add integer property to default cube with a custom min/max/default value, and Is Library Overridable enabled.\n\n- `C.object['prop'] = 2.0`\n- The property's settings are all lost.\n\n\nIIRC, before the refactor, an integer property could have floats as its min/max so this would be allowed. Might be a bit of a pain point with the new system, but I think doing a best effort conversion between types would be nice when possible (even if some data is lost going from float to int, losing some data is better than losing all data).\n\n[#91256-2021-09-08_12.54.49.mp4](T91256-2021-09-08_12.54.49.mp4)\n\nTest File:\n[#91256.blend](T91256.blend)", "Non-keyboard shortcuts allowed to be set via context menu, but cannot be unset without going to user-preferences\nBroken: 2.79 or latest 2.80 (fa59346c13).\n\nAlthough I can easily (and often accidentally) assign non-keyboard shortcuts to menu items, I cannot easily undo it.\n\nFrom the viewport: View > Frame All [RMB] > Change Shortcut.\n\nAlthough the UI says \"Press a Key\", if you mouse click it (e.g., LBM) will register as the new shortcut.\nNow if you try to change the shortcut again it says it is a Non-Keyboard shortcut and cannot be changed.\n\nTooltip: *\"Only keyboard shortcuts can be changed that way (...)\"*", "mask animation is not undoable\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4454\n\n\nBroken: tested 2.79, 2.80\nWorked: non\n\n\nmask animation is not undoable\n\ncreate a mask and make an animation keyframe\npress ctl+Z or edit->undo : nothing happens!\n", "Factory reset does not reset data for add-ons\nSystem Information\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03\n\nBlender Version\nBroken: version: 4.0.0 Alpha\n\nShort description of error\n\nConfigurations of addons are not restored when calling factory reset.\n\nSee video for demonstration:\n\n", "Redo panel does not work for the 3d cursor\nUbuntu 18.04\n\nBroken: 7d38654\n\nRedo panel for moving the 3d cursor does not work as expected.\n\nStart moving the 3d cursor and then change the value in the redo panel.\n\n\n\nMy guess is that this happens because the 3d cursor is not effected by the normal undo.", "User's layout is destroyed when a Maximized Area Render is called with the wrong area\nOperating system: Linux-5.4.0-149-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.116.04\n\nBroken: version: 3.6.0\n\n\nShort reproduction steps:\n\n- Set Preferences > Interface > Temporary Editors > Render In to \"Maximized Area\"\n- Toggle Maximize Area (`ctrl space` in e.g. 3d viewport)\n- Move mouse pointer to top menu bar that has a \"Back to Previous\" button\n- F12\n- Click \"Back to Previous\". It doesn't remember original layout.\n - Expected: It will restore original layout.\n\n-----------\n\nOriginal description:\n\nWhen rendering, the user's layout will not be recovered after some specific conditions are met:\n- The `preferences.view.render_display_type` is set to \"SCREEN\"\n- The Screen in the current window has been maximized in any way (by a previous render call, or if the user has manually maximized some area)\n- A render is called with the Screen already maximized\n- The area passed to the render call is invalid or doesn't match the maximized area in the window.\n\n\n1) Set Preferences > Interface > Temporary Editors > Render In to \"Maximized Area\"\n2) Maximize the Screen in some way (call a render or maximize any area manually)\n3) With the maximized screen, call a new render, making sure to prevent the render operator from receiving the maximized area as context, that is, prevent the cursor from being on top of the maximized area. This can be done in several ways:\n - Put the cursor outside the active Blender window and call a render with F12 (the area passed to render operator will be None)\n - Put the cursor in an empty area of the Topbar and call a render with F12 (the area passed to the render operator will be of type \"TOPBAR\")\n - Call the render from the Topbar menu > Render > Render Image (the area passed to the render operator will also be of type \"TOPBAR\")\n4) The Screen Layout conflict has been created. Now click \"Back to Previous\" button on top trying to recover the original Layout. This will fail and the user's layout will be now lost. This always happens when the render operator doesn't receive the maximized area in its context.\n\n**This is commonly unnoticed because**\n\n- The user tipically has the cursor on top of the maximized area\n- The user rarely calls a new render from the Render menu. Using F12 is much more common.\n- It's rare to call a render with the window being in focus but with the cursor outside of its bounds.\n\nBut when it happens it's a shame, because there's no explicit way for the user to restore the original layout, and saving the blend file will also save this new broken layout.\n\nThis bug report is related to: #86708\n\n", "Sound stops playing after undo\nOperating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-12.9.22\n\nLinux has this issue as well, no problem on windows.\n\nBroken: 2.92.0 Alpha\n\nSound stops playing after undoing all actions back to original file state.\n\n[#84052.blend](T84052.blend)\n\n- Open file\n- Select strip\n- Undo selection, so file is in original state\n- Play animation\n\nThere will be no sound.\n", "Particles reset their position when using time stretching\nMinimal reproduction steps:\n- Add a particle system to the default cube and make it renderable.\n- Set the old time stretching setting to 20 and leave the new at 100.\n- Play the animation until frame 90 and render.\n- Find that the particles are sticking on the object as opposed to their correct position in the viewport.\n- Render again. They now have their correct position.\n- Play another 5 frames.\n- Render again, they are now sticking to the object again.\n\n[timeStretchingBadRender.blend](timeStretchingBadRender.blend)\n\n**Original Report**\n\nHello,\n\ni am using blender-3.1.0-linux-x64 and working on particles with time stretching but the viewport display is correct.\n\nattached is the blend file. [experiment with text.blend](experiment_with_text.blend) \n\nproblem seen in cpu/gpu/cycles/evee.\n\nregards,\nYaju" ]

[ "Adjust last operation: can't reset properties to default value\nBroken: 2.8x\n\nIn the Adjust Last Operation panel, the context menu for any property has the Reset to Default Value options disabled, although they are enabled in the operator panel.\n\n\n1. Load the default scene\n2. Enter edit mode on the cube\n3. Bevel an edge\n4. Expand the operator panel in the bottom left\n5. Right click any property, note that Reset to Default Value option is enabled and works\n6. Go Edit -> Adjust Last Operation\n7. Right click the same property in that panel, note that Reset to Default Value option is disabled" ]

[ "Nodes: Assert and crash: Editing nodes through the material panel and undo.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 27.20.100.8729\n\nBroken: 3.4, 3.3, ... 2.8\nWorked: never\n\nWhen I select certain nodes from the materials tab after pressing undo on the last node change, blender crashes. But only if the last click is made with my wired USB mouse. Or even if the cursor was left on the button to switch tabs before clicking with the touchpad.\n\n\n```lines=10\n# Blender 3.4.0, Unknown revision\nbpy.context.space_data.context = 'MATERIAL' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF717820508\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n\n\nStack trace:\nblender.exe :0x00007FF7178203F0 blender::ed::space_node::ui_template_node_link_menu F:\\Blender_build\\first\\blender\\source\\blender\\editors\\space_node\\node_templates.cc:659\nblender.exe :0x00007FF71736AAF0 ui_block_func_POPUP F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_menu_popup.cc:183\nblender.exe :0x00007FF717463480 ui_popup_block_refresh F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_popup.cc:566\nblender.exe :0x00007FF717463050 ui_popup_block_create F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_popup.cc:796\nblender.exe :0x00007FF71736CA60 ui_popup_menu_create F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_menu_popup.cc:358\nblender.exe :0x00007FF717397CC0 ui_block_open_begin F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:4224\nblender.exe :0x00007FF717391810 button_activate_state F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:8338\nblender.exe :0x00007FF71739CD50 ui_do_but_BLOCK F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:5982\nblender.exe :0x00007FF7173A7AB0 ui_do_button F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:8027\nblender.exe :0x00007FF7173A9D20 ui_handle_button_event F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:9189\nblender.exe :0x00007FF7173BA070 ui_region_handler F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:11275\nblender.exe :0x00007FF7156CFE60 wm_handler_ui_call F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:786\nblender.exe :0x00007FF7156D1CE0 wm_handlers_do_intern F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3217\nblender.exe :0x00007FF7156D01F0 wm_handlers_do F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3334\nblender.exe :0x00007FF7156CB580 wm_event_do_region_handlers F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3754\nblender.exe :0x00007FF7156CB440 wm_event_do_handlers_area_regions F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3784\nblender.exe :0x00007FF7156DCD90 wm_event_do_handlers F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3979\nblender.exe :0x00007FF7156A5E50 WM_main F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm.c:643\nblender.exe :0x00007FF714C52160 main F:\\Blender_build\\first\\blender\\source\\creator\\creator.c:579\nblender.exe :0x00007FF7186F9260 invoke_main D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF7186F9010 __scrt_common_main_seh D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF7186F8FF0 __scrt_common_main D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF7186F9320 mainCRTStartup D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThreads:\nThread : 00002514\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e60\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002ab8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e20\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000026a0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002404\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002234\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000ddc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000305c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002640\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ec4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002130\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ff0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000002f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000e8c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001b88\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001f10\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000132c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE58561C00 DrvValidateVersion\nnvoglv64.dll :0x00007FFE582EF73C Symbols not available\n\n\nThread : 000000c0\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFEA2020350 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE58597770 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE58597770 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002298\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE58561C00 DrvValidateVersion\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001e98\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002b4c\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002278\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000014f8\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFE8DD7458B Symbols not available\n\n\nLoaded Modules :\n0x00007FF712C80000 3.4.0.0 blender.exe F:\\Blender_build\\first\\ninja_lite_debug\\source\\creator\\Debug\\blender_private.pdb \n0x00007FFEA4250000 10.0.19041.2130 ntdll.dll \n0x00007FFEA2540000 10.0.19041.1889 KERNEL32.DLL \n0x00007FFEA1FD0000 10.0.19041.2130 KERNELBASE.dll \n0x00007FFEA3550000 10.0.19041.2130 USER32.dll \n0x00007FFEA1B50000 10.0.19041.2130 win32u.dll \n0x00007FFEA2600000 10.0.19041.2130 GDI32.dll \n0x00007FFEA1CC0000 10.0.19041.2130 gdi32full.dll \n0x00007FFEA19B0000 10.0.19041.789 msvcp_win.dll \n0x00007FFEA1A50000 10.0.19041.789 ucrtbase.dll \n0x00007FFEA2630000 10.0.19041.2075 SHELL32.dll \n0x00007FFEA30A0000 10.0.19041.2130 ADVAPI32.dll \n0x00007FFEA34B0000 7.0.19041.546 msvcrt.dll \n0x00007FFEA3790000 10.0.19041.1865 sechost.dll \n0x00007FFEA38B0000 10.0.19041.1806 RPCRT4.dll \n0x00007FFEA2410000 10.0.19041.1202 ole32.dll \n0x00007FFEA39E0000 10.0.19041.2130 combase.dll \n0x00007FFEA22B0000 10.0.19041.2075 SHLWAPI.dll \n0x00007FFEA3270000 10.0.19041.1865 shcore.dll \n0x00007FFE83ED0000 14.32.31332.0 MSVCP140D.dll \n0x00007FFE8C790000 14.32.31332.0 VCRUNTIME140D.dll \n0x00007FFE9CEF0000 14.32.31332.0 VCRUNTIME140_1D.dll \n0x00007FFE7F6C0000 10.0.19041.685 ucrtbased.dll \n0x00007FFE844B0000 6.10.19041.1110 COMCTL32.dll \n0x00007FFE9C5E0000 10.0.19041.546 VERSION.dll \n0x00007FFE9B860000 10.0.19041.867 dbghelp.dll \n0x00007FFE9F730000 10.0.19041.746 dwmapi.dll \n0x00007FFE8C310000 tbb_debug.dll \n0x00007FFE7EC20000 epoxy-0.dll \n0x00007FFE67340000 3.10.8150.1013 python310_d.dll \n0x00007FFEA2F50000 10.0.19041.546 WS2_32.dll \n0x00007FFE98DC0000 14.32.31332.0 VCRUNTIME140.dll \n0x00007FFEA2310000 10.0.19041.546 IMM32.DLL \n0x00007FFE9FA40000 10.0.19041.2130 windows.storage.dll \n0x00007FFEA12E0000 10.0.19041.2075 Wldp.dll \n0x00007FFEA18A0000 10.0.19041.844 profapi.dll \n0x00007FFE9F460000 10.0.19041.2130 uxtheme.dll \n0x00007FFE9F840000 10.0.19041.546 kernel.appcore.dll \n0x00007FFEA1C30000 10.0.19041.1415 bcryptPrimitives.dll \n0x00007FFE8B530000 tbbmalloc_debug.dll \n0x00007FFEA3150000 10.0.19041.2075 MSCTF.dll \n0x00007FFEA2FC0000 10.0.19041.985 OLEAUT32.dll \n0x00007FFE824C0000 10.0.19041.2075 OPENGL32.DLL \n0x00007FFE8C420000 10.0.19041.2075 GLU32.dll \n0x00007FFEA3400000 2001.12.10941.16384 clbcatq.dll \n0x00007FFE9ADF0000 10.0.19041.2075 AppXDeploymentClient.dll \n0x00007FFE57830000 30.0.14.9649 nvoglv64.dll \n0x00007FFEA3D40000 10.0.19041.1741 SETUPAPI.dll \n0x00007FFEA1960000 10.0.19041.1620 cfgmgr32.dll \n0x00007FFEA1FA0000 10.0.19041.1023 bcrypt.dll \n0x00007FFE9D780000 10.0.19041.546 WTSAPI32.dll \n0x00007FFEA1250000 10.0.19041.546 CRYPTBASE.DLL \n0x00007FFEA1470000 10.0.19041.546 msasn1.dll \n0x00007FFE9C570000 10.0.19041.906 cryptnet.dll \n0x00007FFEA1DD0000 10.0.19041.1889 CRYPT32.dll \n0x00007FFE9AEF0000 10.0.19041.1949 drvstore.dll \n0x00007FFEA1650000 10.0.19041.1620 devobj.dll \n0x00007FFEA1F30000 10.0.19041.2075 WINTRUST.dll \n0x00007FFEA0AA0000 10.0.19041.546 ntmarta.dll \n0x00007FFE93710000 10.0.19041.546 dxcore.dll \n0x00007FFEA17D0000 10.0.19041.546 powrprof.dll \n0x00007FFEA17B0000 UMPDC.dll \n0x00007FFEA1740000 10.0.19041.2075 WINSTA.dll \n0x00007FFE87CC0000 10.0.19041.1387 dataexchange.dll \n0x00007FFE9D990000 10.0.19041.2075 d3d11.dll \n0x00007FFE9E1C0000 10.0.19041.2075 dcomp.dll \n0x00007FFEA0340000 10.0.19041.2075 dxgi.dll \n0x00007FFE94780000 10.0.19041.1865 twinapi.appcore.dll \n0x00007FFE93EB0000 10.0.19041.2075 textinputframework.dll \n0x00007FFE9ED10000 10.0.19041.746 CoreMessaging.dll \n0x00007FFE9EF10000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFE9E060000 10.0.19041.2130 wintypes.dll \n0x00007FFE7E100000 10.0.19041.1949 explorerframe.dll \n0x00007FFE8DD60000 10.0.19041.1566 directmanipulation.dll \n0x00007FFEA1230000 10.0.19041.546 CRYPTSP.dll \n0x00007FFEA0960000 10.0.19041.1052 rsaenh.dll \n\n# Python backtrace\n```\n\n```lines=10\n# Blender 3.4.0, Commit date: 2022-10-20 00:36, Hash 3915f5300ad2\nbpy.context.space_data.context = 'MATERIAL' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF6E6FDF4EA\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x00000000000001A1\n\n\nStack trace:\nblender.exe :0x00007FF6E6FDF4C0 nodeRemLink\nblender.exe :0x00007FF6E80A8DA0 blender::ed::space_node::node_socket_add_replace\nblender.exe :0x00007FF6E80A9980 blender::ed::space_node::ui_node_link\nblender.exe :0x00007FF6E7EBCF50 ui_apply_but_funcs_after\nblender.exe :0x00007FF6E7EC87F0 ui_handler_region_menu\nblender.exe :0x00007FF6E7495810 wm_handlers_do_intern\nblender.exe :0x00007FF6E7494C40 wm_handlers_do\nblender.exe :0x00007FF6E749B1B0 wm_event_do_handlers\nblender.exe :0x00007FF6E7480BC0 WM_main\nblender.exe :0x00007FF6E65512F0 main\nblender.exe :0x00007FF6EC6F4380 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThreads:\nThread : 000032c8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000778\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000015a8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000018f0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000f34\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000265c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000458\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000fdc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000198c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000026e4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001088\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001234\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001aac\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002a14\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002228\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000030f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000c60\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002248\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00003084\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ff0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e60\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002514\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000b84\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000005dc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE4F811C00 DrvValidateVersion\nnvoglv64.dll :0x00007FFE4F59F73C Symbols not available\n\n\nThread : 00002fec\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFEA2020350 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE4F847770 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE4F847770 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001754\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE4F811C00 DrvValidateVersion\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000e54\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000029ac\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002474\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFE8DD7458B Symbols not available\n\n\nThread : 000007a4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002ed4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022dc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001410\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000154c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002bf4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000f78\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000031e0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF6E63E0000 3.4.0.0 blender.exe F:\\Диск I\\programm\\blenders\\свежак 24-14-9-11\\b \n0x00007FFEA4250000 10.0.19041.2130 ntdll.dll \n0x00007FFEA2540000 10.0.19041.1889 KERNEL32.DLL \n0x00007FFEA1FD0000 10.0.19041.2130 KERNELBASE.dll \n0x00007FFEA2F50000 10.0.19041.546 WS2_32.dll \n0x00007FFEA38B0000 10.0.19041.1806 RPCRT4.dll \n0x00007FFE98DA0000 tbbmalloc.dll \n0x00007FFE988A0000 tbb.dll \n0x00007FFEA3550000 10.0.19041.2130 USER32.dll \n0x00007FFEA1B50000 10.0.19041.2130 win32u.dll \n0x00007FFEA2600000 10.0.19041.2130 GDI32.dll \n0x00007FFEA1CC0000 10.0.19041.2130 gdi32full.dll \n0x00007FFEA19B0000 10.0.19041.789 msvcp_win.dll \n0x00007FFEA1A50000 10.0.19041.789 ucrtbase.dll \n0x00007FFEA30A0000 10.0.19041.2130 ADVAPI32.dll \n0x00007FFE8C700000 14.29.30139.0 MSVCP140.dll \n0x00007FFE999F0000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFEA34B0000 7.0.19041.546 msvcrt.dll \n0x00007FFE9A080000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFEA3790000 10.0.19041.1865 sechost.dll \n0x00007FFEA2630000 10.0.19041.2075 SHELL32.dll \n0x00007FFEA22B0000 10.0.19041.2075 SHLWAPI.dll \n0x00007FFEA1960000 10.0.19041.1620 CFGMGR32.dll \n0x00007FFE9B860000 10.0.19041.867 dbghelp.dll \n0x00007FFEA1FA0000 10.0.19041.1023 bcrypt.dll \n0x00007FFE68390000 5.7.0.7 sycl.dll \n0x00007FFEA2410000 10.0.19041.1202 ole32.dll \n0x00007FFEA39E0000 10.0.19041.2130 combase.dll \n0x00007FFEA3780000 10.0.19041.546 PSAPI.DLL \n0x00007FFE81390000 epoxy-0.dll \n0x00007FFEA3270000 10.0.19041.1865 shcore.dll \n0x00007FFE556F0000 cycles_kernel_oneapi.dll \n0x00007FFEA2310000 10.0.19041.546 IMM32.dll \n0x00007FFE53FA0000 9.0.0.0 openvdb.dll \n0x00007FFE67640000 59.16.100.0 avformat-59.dll \n0x00007FFE51AA0000 59.18.100.0 avcodec-59.dll \n0x00007FFE944D0000 59.4.100.0 avdevice-59.dll \n0x00007FFE7EBF0000 57.17.100.0 avutil-57.dll \n0x00007FFEA2FC0000 10.0.19041.985 OLEAUT32.dll \n0x00007FFE8C5C0000 6.4.100.0 swscale-6.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFE83E80000 1.21.1.0 OpenAL32.dll \n0x00007FFE82490000 2.0.20.0 SDL2.dll \n0x00007FFE99D20000 libgmpxx.dll \n0x00007FFEA3D40000 10.0.19041.1741 SETUPAPI.dll \n0x00007FFE67170000 3.10.2150.1013 python310.dll \n0x00007FFE99A30000 tbbmalloc_proxy.dll \n0x00007FFE942E0000 10.0.19041.1 AVIFIL32.dll \n0x00007FFE844B0000 6.10.19041.1110 COMCTL32.dll \n0x00007FFE9C5E0000 10.0.19041.546 VERSION.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFE9F730000 10.0.19041.746 dwmapi.dll \n0x00007FFE92F80000 10.0.19041.546 Secur32.dll \n0x00007FFE8C530000 4.3.100.0 swresample-4.dll \n0x00007FFE98880000 10.0.19041.1 AVICAP32.dll \n0x00007FFE936E0000 10.0.19041.546 WINMM.dll \n0x00007FFE9CED0000 10.0.19041.1 MSACM32.dll \n0x00007FFE8C420000 10.0.19041.1 MSVFW32.dll \n0x00007FFE96EB0000 10.0.19041.1 winmmbase.dll \n0x00007FFEA1820000 10.0.19041.2130 SSPICLI.DLL \n0x00007FFE9F840000 10.0.19041.546 kernel.appcore.dll \n0x00007FFE9FA40000 10.0.19041.2130 windows.storage.dll \n0x00007FFEA12E0000 10.0.19041.2075 Wldp.dll \n0x00007FFE9F460000 10.0.19041.2130 uxtheme.dll \n0x00007FFEA1C30000 10.0.19041.1415 bcryptPrimitives.dll \n0x00007FFEA18A0000 10.0.19041.844 profapi.dll \n0x00007FFEA3400000 2001.12.10941.16384 clbcatq.dll \n0x00007FFE9CFC0000 10.0.19041.1503 MMDevApi.dll \n0x00007FFEA1650000 10.0.19041.1620 DEVOBJ.dll \n0x00007FFE9D0C0000 10.0.19041.1865 AUDIOSES.DLL \n0x00007FFEA17D0000 10.0.19041.546 powrprof.dll \n0x00007FFEA17B0000 UMPDC.dll \n0x00007FFEA3150000 10.0.19041.2075 MSCTF.dll \n0x00007FFE80380000 10.0.19041.2075 OPENGL32.DLL \n0x00007FFE8B550000 10.0.19041.2075 GLU32.dll \n0x00007FFE9ADF0000 10.0.19041.2075 AppXDeploymentClient.dll \n0x00007FFE4EAE0000 30.0.14.9649 nvoglv64.dll \n0x00007FFE9D780000 10.0.19041.546 WTSAPI32.dll \n0x00007FFEA1250000 10.0.19041.546 CRYPTBASE.DLL \n0x00007FFEA1470000 10.0.19041.546 msasn1.dll \n0x00007FFE9C570000 10.0.19041.906 cryptnet.dll \n0x00007FFEA1DD0000 10.0.19041.1889 CRYPT32.dll \n0x00007FFE9AEF0000 10.0.19041.1949 drvstore.dll \n0x00007FFEA1F30000 10.0.19041.2075 WINTRUST.dll \n0x00007FFEA0AA0000 10.0.19041.546 ntmarta.dll \n0x00007FFE93710000 10.0.19041.546 dxcore.dll \n0x00007FFEA1740000 10.0.19041.2075 WINSTA.dll \n0x00007FFE87CC0000 10.0.19041.1387 dataexchange.dll \n0x00007FFE9D990000 10.0.19041.2075 d3d11.dll \n0x00007FFE9E1C0000 10.0.19041.2075 dcomp.dll \n0x00007FFEA0340000 10.0.19041.2075 dxgi.dll \n0x00007FFE94780000 10.0.19041.1865 twinapi.appcore.dll \n0x00007FFE93EB0000 10.0.19041.2075 textinputframework.dll \n0x00007FFE9EF10000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFE9ED10000 10.0.19041.746 CoreMessaging.dll \n0x00007FFE9E060000 10.0.19041.2130 wintypes.dll \n0x00007FFE7E100000 10.0.19041.1949 explorerframe.dll \n0x00007FFE8DD60000 10.0.19041.1566 directmanipulation.dll \n0x00007FFEA1230000 10.0.19041.546 CRYPTSP.dll \n0x00007FFEA0960000 10.0.19041.1052 rsaenh.dll \n0x00007FFE66EB0000 30.0.14.9649 nvcuda.dll \n0x00007FFE4D460000 30.0.14.9649 nvcuda64.dll \n0x00007FFE788A0000 30.0.14.9649 nvapi64.dll \n\n# Python backtrace\n\n```\n\nBlenders: 3.4, 3.2, 3.0, 2.9, 2.83\n```lines=10\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-14-8-11\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.4\\config\\userpref.blend\nWarning: File written by newer Blender binary (304.3), expect loss of data!\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFE8C723020\nModule : MSVCP140.dll\nThread : 0000207c\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-12-1\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.2\\config\\userpref.blend\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF73481F663\nModule : blender.exe\nThread : 000029c0\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-9-10\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.1\\config\\userpref.blend\nERROR (bke.node): C:\\Users\\blender\\git\\blender-vdev\\blender.git\\source\\blender\\blenkernel\\intern\\node.cc:2222 nodeAddStaticNode: static node type 200 undefined\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7A47ABC94\nModule : blender.exe\nThread : 00000674\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 22-14\\blender.exe\"\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF776C49221\nModule : blender.exe\nThread : 00000cc0\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 20-6\\blender.exe\"\nfound bundled python: F:\\╨Ф╨╕╤Б╨║ I\\programm\\blenders\\╤Б╨▓╨╡╨╢╨░╨║ 20-6\\2.83\\python\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF6508070ED\nModule : F:\\─шёъ I\\programm\\blenders\\ётхцръ 20-6\\blender.exe\n```\n\n1: Open blender to the default startup file.\n2: Go to the materials tab.\n3: Click on the button next to \"Surface\" labeled \"Principled BSDF\" and select a different node to switch it out.\n4: Press Ctrl + Z on the keyboard to undo the previous action.\n5: Repeat steps 3 and 4 with various nodes until it crashes.\n(There used to be a more consistent way of replicating this, making a mix shader, putting a glossy bsdf node in the top slot, then pressing undo and selecting an emission node instead, but it stopped crashing with that just before I sent this.\n. . . And it just started crashing with that again. I'm sorry I can't give you something more consistent.)\n\nBased on the default startup file.\n", "Industry Compatible keymap uses Ctrl + H for two separate actions resulting in only one action working\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.2.1\n\nThere's a keymap conflict here when using the Industry Compatible map:\n\n\nUnfortunately instead of resulting in both actions being done, this results in the \"hide unused\" shortcut not working at all by default.\n\n- switch to Industry Compatible keymap\n- create a material\n- select a node and try to use keyboard shortcuts for \"hide unused\" and \"collapse\"\n- note they're both Ctrl + H resulting in only \"collapse\" ever doing anything.\n\nEither should by default both actions happen upon that shortcut or there should not be a conflict by default.\n", "pressing z key to switch between extrusion \n intel i5 ,win ,amd radeon \nblender 2.8 \n490a385c8124\n\n\n\n\nThis happens when transform orientation set to Global \nCreate a sphere , select a face and extrude \nBy default it will extrude along the normal , when pressing z it will now extrude along the global but it won't go back to normal when pressing the 'z'key again \n \n\n\n ", "Non-keyboard shortcuts allowed to be set via context menu, but cannot be unset without going to user-preferences\nBroken: 2.79 or latest 2.80 (fa59346c13).\n\nAlthough I can easily (and often accidentally) assign non-keyboard shortcuts to menu items, I cannot easily undo it.\n\nFrom the viewport: View > Frame All [RMB] > Change Shortcut.\n\nAlthough the UI says \"Press a Key\", if you mouse click it (e.g., LBM) will register as the new shortcut.\nNow if you try to change the shortcut again it says it is a Non-Keyboard shortcut and cannot be changed.\n\nTooltip: *\"Only keyboard shortcuts can be changed that way (...)\"*", "When \"Pie Menu on Drag\" is enabled in user prefs, Ctrl + Z has a tendency to open the shading menu by accident\nversion: 2.80 (sub 74), branch: master, commit date: 2019-07-05 21:52\nbuild date: 2019-07-06, 01:03:01\nplatform: Linux\n\nThis may be more of a design issue than a bug, but it's happened to me about 100 times now and it's quite irritating.\n\n**To reproduce:**\n\n - enable User Preferences > Keymap > Preferences > Pie Menu on Drag.\n - open a complex scene (one where the undo operator will have a significant lag) \n - fill the undo history with events, as though you've been working for a while\n - Press Ctrl + Z a couple times while moving the mouse a bit, rolling your hand so that Ctrl is released just before Z (in the manner of a busy artist)\n\nIf the user happens to release Ctrl earlier than Z while moving the mouse, this can bring up the shading menu, interrupting the user's workflow. This may sound like an edge case, but when working quickly, it's actually really frequent and annoying! It seems to especially effect large scenes where there is a lag in the effect of the undo operator.\n\nIdeally, the \"Pie On Drag\" feature should not listen for key presses if those key presses were part of a different combination that has yet to be completely released. What do you think?", "Sculpt Mode: Edit Voxel Size hotkey conflict\nOperating system: Win 10\n\nBroken: blender-2.90-51ac411ce80c-windows64\n\nThe \"Edit Voxel Size\" and the \"Repeat Last\" functions are using the same hotkey (Shift+R), and as a result, the \"Repeat Last\" command is not working in sculpt mode.\n", "Text editor undo system, undo step limiting behavior\nCurrently having a linear undo stack has a limitation which is most obvious with text undo.\n\nTyping a character uses a single undo step, meaning if you are working in 3D sculpting for eg, then type a short paragraph over 32 characters - you'll loose all your undo steps.\n\nProposed solution is for undo systems to support counting their undo steps separately, so text editing operations wouldn't use up undo steps for edits in other modes.\n", "Undo/Redo shortcut still active in the Blender File View window\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Beta\n\nUndo/Redo shortcut still active in the Blender File View window\n\n* Open Blender with the default cube.\n* Move the cube a few times.\n* Open the “Preferences” window in the menu “Edit | Preferences...”\n* Then do Ctrl + Z to undo. The undo shortcut still works. It is the same for the redo shortcut.\n\nThe undo/redo is also active from any other windows of the “File” menu like “Open”, “Link”, “Save”, “Append”, etc. All links showing the “Blender File View”.\n\nIn the “Blender File View” window, I noticed that the buttons at the bottom disappear when doing the undo shortcut.\n\nI tried a few other shortcuts like Tab to go to edit mode and G to move the cube. They do not seem to be active when the focus is on the “Preferences” or “Blender File View” window.\n\nThe undo/redo is also active when the “Blender Render” has the focus.\n\nAs a consequence, someone accidentally hitting the undo shortcut will get his work being modified behind the window and probably will not notice.\n\n\n{[F9111517](BlenderFileView_Open.jpg) size=full}\n\n{[F9111519](BlenderFileView_AfterShortcut.jpg) size=full}", "Dead Keys failing (accented letters, double strokes)\nOperating system: Windows 10 X64 Enterprise\nGraphics card: Nvidia RTX 2070 MaxQ\n\nBroken: 2.73, 2.91.0\nWorked: Never\n\nIn a text editor window, using Unicode national characters (Greek in my case), there are accented vowels that register with two keys from the keyboard (eg: ά, έ, ό … etc).\nIf I type the 2 key sequence fast, the accent is missed, slower works. Is this a delay that can be set in Blender, or an interpreter lag that cannot be adjusted?\nActually I think it happens everywhere (not only text editor), but it’s especially nagging problem in a text window, where I may type whole paragraphs and almost each word has an accent.\n\n- In the text editor, press and hold the dead key\n- without releasing the dead key, press the key to be transformed. (this will fail)\n\nIf you release the dead key before pressing the key to be changed, it will work normally.", "lost 90% of my progress\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\ni was 90% through my build and had forgetten to save although i havent made saving every five minutes my priority anyways i was almost done when it freezes then crashes and all of mt work is now gone this has already happened once but i didnt lose anything so i therefore didnt report it\n\n", "GPencil: Shortcuts in Draw Mode are hardcoded\nMultiple keys in the `gpencil_draw_modal` function are hardcoded and (some) don't show up in the info bar. This makes it impossible for the user to know what certain keys do as well as impossible to change them in the keymap. All of those keys should be in the keymap with the default keys set as they are now.\n\nHere is a list of these (hardcoded) shortcuts:\n\n - {key Enter}, {key Pad_Enter}, {key Esc}, {key Space}, {key Ctrl Z} (?): Confirm\n - {key Mousewheel_Up}, {key Pad_Plus}: Increase size of eraser\n - {key Mousewheel_Down}, {key Pad_Minus}: Decrease size of eraser\n - {key O}: Set center of guide\n - {key V}: Turn off speed guide\n - {key M}: Alternate or flip guide direction\n - {key L}: Turn on line guide; {key Ctrl L}: Turn on line guide with angle = 0; {key Alt L}: Turn on line guide with last angle\n - {key C}: Turn on circular guide\n - {key K}: Turn line guide clockwise\n - {key J}: Turn line guide anti-clockwise\n", "Sample texture color dialog isn't dismissed after use\nOperating system: W10\nGraphics card: GTX 970\n\n2.82a\n\nAfter use of the pipette in the Image Texture Editor, the 'F9' dialog box is not dismissed until an UNDO operation is performed.\n\n\nSample file included; Launch file. Switch to Texture Paint. In the Texture Image Editor, invoke the sample function with the S hotkey. Observe the dialog.[Sample Dialog Dismiss.blend](Sample_Dialog_Dismiss.blend)", "Can't undo the keyframe change in edit mode\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nWhile in edit mode, when you hit Undo in the graph editor after moving a keyframe, the graph doesn't change.\n\n- Animate anything using a couple of keyframes.\n- Change to edit mode in viewport\n- Switch timeline to the graph editor (not necessary, you can keep timeline as it is)\n- Select a keyframe and move it\n# Hit undo\n\nResult: The graph editor stays the same\n\nExpected: The move you just made in the graph editor should be the only thing being undone!\n\nTest file with first four steps included\n[#97700.blend](T97700.blend)", "Sculpt brush Reverts to Default When Undoing\nOperating system: Windows-10-10.0.25336-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Alpha\nWorked: 2.79\n\n**Description of error**\n\nWhen using a non-default brush such as clay strips, then undoing, the brush switches to the default one (draw brush). Now this is frustrating to the user because you need constantly switch back to your brush after every ctrl + z. Stupid bug that interrupts the workflow.\n\nNow this bug is not limited to sculpt mode, it happens in vertex painting, weight painting, texture painting and hair sculpt mode.\n\nHowever this bug doesn't happen to most users because for it to happen you need to have two main windows.\n\n* Add a new main window (`Window > New Main Window`) and switch the workspace (say \"shading\")\n* In primary main window: switch to sculpt mode\n* Choose clay strips\n* Press ctrl + z\n* Observe the brush is draw brush and not clay strips 😵‍💫\n\nNote: I think this has to do something with workspace since switching them can fix this bug but also crash blender\n\n[video](https://projects.blender.orgattachment)", "Gizmos blink when selecting with right mouse button\nWindows 10 64 Bits.\nGraphics card GeForce GTX 1080 Ti.\n\nBroken: version: 2.82.6\nWorked: 2.79b, 2.80 & 2.81.\n\nWhenever you select or extend select the gizmos do a quick blink.\n\n - I have a custom keymap that changed the type of event from Click to Press for the default.\n - This issue can easily be replicated if you use the Right Click Select.\n - Default Cube subdivided then Select few Vertices in a normal manner like shown in the Gif. \n\n\n\n{[F8246599](Select.gif) size = full}\n" ]

[ "Undo and Two-Click Object Creation Not Working\nOperating system: Windows 10\nGraphics card: 280 GTX\n\n2.92.0 Beta Date 2021-01-13\n\nWhen starting from a fresh factory restart:\n1. There is no Undo function\n\n2. There is no two-click object creation\n\nI have activated developer extras and Experimental section. But there isn't a two-click creation there.\n \nBased on the default startup or an attached .blend file (as simple as possible).", "No undo\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Beta\n\nCtrl + Z does not undo, and undo is not present under edit menu. \n\nCtrl + Z does not undo, and undo is not present under edit menu. \n\n\n", "Undo/Redo Actions Missing\nOperating system: Windows 10 Pro\nGraphics card: Nvidia Geforce RTX 2060, driver 457.51\n\nBroken: (2.92.0 Beta, 5d826866a3, master, 2021-01-13)\nWorked: (2.91.0)\n\nUndo and Redo actions are missing from edit menu, and shortcuts (Ctrl+Z, Ctrl+Shift+Z) do not function\n\nCreate a new default blend file and perform any action. Undo and redo will not be available.\n\n\n\n", "Undo doesn't work after reverting of ID template changes\nOperating system: Linux-5.8.0-36-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: Caused by 2771dfd563\nWorked: ad4202a14f\n\nThere is no \"undo\" in the current master builds that I'm compiling...\n\nMove default cube and try to undo... nothing happens...\n\n" ]

[ "Improve Palette management in Paint Modes (Meshes and Grease Pencil)\nThis is not a task only related to Grease Pencil, but also to any Paint mode.\n\nAs part of the Vertex Paint development in Grease Pencil, we have detected some missing features in Palettes and we have decided to fix it, because Palettes look a little outdate and without improvements for several versions.\n\nMissing features/ WishList:\n\n* There is no default palette.\n* Swatches cannot be re-arranged\n* Colors cannot be sorted\n* Colors can't be named\n* Palettes cannot be merged\n* templatePalette control UI is outdated\n* No ability to import palettes from other software\n* No ability to export palettes to other software\n* Missing easy way to create palettes from images\n\nAbout default palette, in grease pencil we have implemented a default palette similar to Krita/GImp palette. This palette is required by GPencil, but it would be good idea to set this default palette in Texture Paint and Vertex Paint for meshes too.\n\n\nCurrently, I have solved the Sorting, Moving, Join and some Import modules in Grease Pencil branch, but the list above is the initial ideas.", "Grease pencil: unstable offset height (surface drawing)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\n\nWhen I use perspective camera, and try to drad on surface with GP, offset is unstable and depends on distance from camera.\n\nTest File:\n[#94735.blend](T94735.blend)\n[2022-01-08_10-23-37.mp4](2022-01-08_10-23-37.mp4)\n", "Grease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\n\n\nBroken: version: 3.3.0 Alpha\n\n\nWorked: Blender 3.2 \n\n\n\n\nGrease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\n\n\n\n\n - New scene.\n - Keep the cube.\n - Don't delete it.\n - Add an empty Grease Pencil Object.\n - Don't delete the cube.\n - Add a Line Art Modifier to the Grease Pencil Object,\n - Switch Source to Object, and select the cube.\n - Assign the default layer and material.\n - You should be seeing something like this\n\n\n\n - Add geometry nodes nodes to the cube.\n - yes keep the damn cube.\n - here is the simplest setup that involves instances that I could think of\n\n\n\n - as you can see in the viewport the grease pencil line art has dissapeared completely.\n\n\nThanks for looking into it.\n\n", "Grease Pencil phasing through objects even when 3d location is selected \nOperating system: Windows 10\nGraphics card: NVIDIA RTX 2060 SUPER\n\n3.1.2\n\nGrease Pencil strokes that should be under the floor/behind objects are phasing through with a weird grainy texture. Looks perfectly fine in viewport rendering but when I render an image/animation it looks weird. Not sure what im missing or if its a bug?\n\n**Blender project**\n[clothtest.blend](clothtest.blend)\n\n", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Topbar glitch when the Status Bar is hidden due to the process bar display\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: 2.81a, 2.82a, 2.83.0, 2.90, 2.93.3, 3.1.0\nWorked: not found\n\nIf the Status Bar is hidden, when you invoke a process that displays a progress bar, it causes a glitch.\n\nThis has something to do with the fact that the *arena* is divided into *regions*, so for example,\nthis works fine when `template_running_jobs()` is moved from `draw_right()` to `draw_left()`.\n\n\n- Hide the Status Bar\n- Press F12\n\n{[F8577145](topbar-glitch.png), size=full}\n\n[topbar-glitch.mov](topbar-glitch.mov)\n\n\n- Hide the Status Bar\n- Invoke the File Browser with File > Import or Add > Image > Background.\n\n{[F10340167](bug.mp4), layout=link}", "GPencil: Layer transform is duplicated when duplicating object\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't believe this has ever worked as expectated\n\n\nIf there is a transformation under the object data properties for a layer and the user duplicates the greasepencil object, the duplicated object will offset the greasepencil points by the vector specified in the layer transformation. It will retain the layer transformation from duplication, and will reapply the same transformation.\n\nIf I have a layer transformation of (0, 0.1, 0), the duplicated greasepencil object will have all points displaced by the (0, 0.1,0), but will still have an active layer offset of (0, 0.1, 0) which will cause a total of (0, 0.2, 0) displacement.\n\nThe only way to make the duplicated greasepencil object the same as the original, is to 0 out all the transforms on the duplicated object or go edit mode and correct the offset there. \n\nThis is more of an issue when overriding a library, since I can not 0 out the linked object layers without making them local to the file. The moment I override a linked greasepencil object/collection, the same issues as duplicating appear. \n\n\nIn the test file, duplicate the greasepencil object. Note how the 0.1 Transform Layer will translate 0.1 units on y after each duplication. This will occur if you make a library override of this object in another file.\n[Blender Bug with Layer Transform.blend](Blender_Bug_with_Layer_Transform.blend)\n", "GPencil: Buffer stroke is only visible in the area that originated the drawing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.1 26.20.15019.1003\n\nBroken: version: 2.90 (sub 0)\n\nWhen creating two viewport, you can't watch the lines drawn at the same time\n\nCreate two viewport and move a little on the screen. Then start drawing. You will notice that the lines are not visible at the right time\n[bandicam 2020-04-21 14-03-29-287.mp4](bandicam_2020-04-21_14-03-29-287.mp4)", "Stroke overlay when erasing\nOperating system: Win 10\nGraphics card: NVIDIA GeForce GTX 1070 Ti\n\nBroken: (example: 2.80, 66684bdff30f, master, 2019-07-05)\n\n\nThe new alpha overlap stops working, when you erase somethin of that stroke.\n\n \nOpen a new project create a blank stroke object draw something try to erase it", "Avoid graphical glitches during threaded preview generation\nWhen previews are generated using an OpenGL engine, there can be a number of glitches until the preview is done. That's because some data is accessed/modified that is not thread safe. E.g. `object_preview_render()` modifies `U.pixelsize`. I think other glitches are caused by overriding the active theme in `ED_view3d_draw_offscreen()` - although when I avoided this some time ago for similar work on threaded offscreen drawing for VR, this didn't solve the color flickering.\nThe active theme should probably use thread local storage.\n\nBesides that, the preview generation should be thread safe with OpenGL:\n* It uses the draw-manager's own context, which is mutex protected.\n* The non-thread-safe immediate mode API is not used inside the draw-manager.\n* The draw-manager already has workarounds for GPU driver issues with threaded drawing.\n\nA note: We could also speed up Eevee preview generation significantly by using viewport render quality, not final render quality. The `_imbuf` offscreen rendering functions don't expose the `is_image_render` option for that, which they probably should.", "Line art modifier clips with object on (MBP 16\")\nOperating system: macOS Big Sur\nGraphics card: 5500M \n\nBroken: 2.93.0 LTS\nWorked: -\n\nLine art modifier (grease pencil) seems to clip into / z-fighting the object. \n\n\nJust add a new line art modifier, possibly a mac problem?\n\nTest File:\n[line_sample.blend](line_sample.blend)", "GPencil: Hard to erase drawing when layer parented to animated object\nOperating system: MacOs 10.15.4\nGraphics card: AMD Radeon Pro 5500M 8 GB\n\nBroken: Version 2.90 (2.90 2020-05-20)\nWorked: ?\n\nSorry for the potentially misleading title. I think that when a Grease Pencil drawing is parented, and the parent animated, the erase tool (using control/Alt/Right Click or the Brush eraser) is somehow offset and it's near impossible to erase precisely. Going in Edit mode and Selecting/Deleting the vertices/strokes works though... \n[GP_EraseWhenParentedIssue.mp4](GP_EraseWhenParentedIssue.mp4)\nHere is the Blend file.\n[GP_EraseWhenParentedIssue.blend](GP_EraseWhenParentedIssue.blend)", "GPencil: Fill tool Ignore Transparent strokes setting broken\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Beta\n\nFill tool not ignoring transparent strokes when the settings is enabled. When you enable Show boundary lines, it shows that transparent strokes are not a boundary but the fill still uses them as boundaries.\n\n- Open attached file and try the fill tool. Under the Advanced menu 'Ignore Transparent' and 'Show Lines' are enabled.\n\n", "Grease Pencil Tint / Also Vertex Paint on Grease Pencil Objects very slow with Cintiq Pro 24\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.1\n\nWhen i use Grease Pencil Tint with the a Cintiq 24 Pro it's very very slow. I have to wait after each stroke to continue. Drawing with the mouse is no problem.\nSame with vertex paint on a grease pencil object.\n\nWindows Ink and Wintab made no difference\n\nJust tinting with the cintiq stylus in the attached scene on the current layer.\n\n", "GPencil: Object keyframes are not visible in grease pencil dopesheet mode\nOperating system: windows 10\nGraphics card: GTX 1650\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nIn grease pencil Object when I assign a key frame to its properties (like opacity or transformation ), I cant see the key frames in the action editor.\nAnd same thing when I do frame by frame animation.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n{[F10286546](GP_and_Action_Editor.blend)}" ]

[ "Fill messing up when clicking outside of it. ...*Anywhere* outside of it.\nOperating system: Windows 10\nGraphics card: 3071MB NVIDIA GeForce GTX 1060 3GB (HP)\n\nBroken: fbe81db29a28\nWhenever I click outside of the 3D view and, in particular, into text input boxes or even the menus on the right-hand side of the screen, any fill you give the object will...[mess up a little. ](yKW0CA8)\n\n1: Start up this build.\n2: Choose \"2D Animation.\"\n3: Enter Object Mode.\n4: Select the camera.\n5: Add a [picture to trace ](80qrR0k). No one ask for the full size of what picture I used or where from, long story.\n6: Under \"Background Images\", choose \"Fit\" instead of \"Stretch\".\n7: Add a new Blank Grease Pencil object.\n8 Enter draw mode.\n9: Proceed to trace, for example, the left eye, as depicted in the remainder of the album.\n10: Go to \"Materials\", add a new one and give it a Fill. No one cares what the color is.\n11: (Where the bug happens) Name the Material. Keep an eye on the eye. Click *out* of the text input. ~~Click *anywhere* but in the 3D view that is on the right-hand side of the screen. Try to edit some vulnerable text in there.~~ What happens: The fill messes up, it cuts of for whatever reason, as I had witnessed. This could all be just me, though.\n\nEdit 1: This most often (and possibly *only) happens when you click in and out of text input boxes...repeatedly.\nBased on the default startup.", "Flickering happening in the 3D Viewport.\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 8)\nWorked: 2.82 (sub 7)\n\nIn the latest master build there is some flickering in the viewport when you navigate, it happens only if you have the animation player running. \nIf you move the mesh you get also some ghosting effect.\n\n\n * Either with the default scene or with the example file.\n * Play Animation.\n * From the perspective or one of the side views try to rapidly click the navigation shortcuts like zooming but without going in and out, just like in this demo.\n * You can also just hover over the Viewport Navigation Widgets.\n.\n.gif](https://archive.blender.org/developer/F8403031/D2.gif)\n\n[exmp.blend](exmp.blend)\n\n\n\n\n", "Grease Pencil Stroke Depth Order Glitch\nSystem Information\nOperating system: OSX High Sierra\nGraphics card: AMD Radeon R9 M370X 2 GB / Intel Iris Pro 1536 MB\n\nBlender Version\n2.83 Alpha\nDate 2020-03-12 19:47\nHash: fa823f0af867\n\nShort description of error\nIf there are 2 GP objects in the scene and one is set so that the Stroke Depth Orientation is 2D Layers and the Other is 3D location, there are odd graphical glitches\n\nExact steps for others to reproduce the error{[F8402918](Screenshot_2020-03-12_at_23.11.24.png)}\n\n\n1. Start a General scene.\n2. delete cube\n3. Add GP Monkey\n4. Move Monkey slightly forward in Y space.\n5. Add a GP Blank\n6. Create a layer and material with a fill colour selected\n7. Go into draw mode\n8. Draw a large shape behind monkey.\n9. Go to Object mode\n10. Set the shape GP object to use £D Location as Stroke Depth Order\n11. Rotate camera around and you will see glitches. \n\nGlitches look like random shapes that mask the monkey and glitch in other ways.", "GPencil – Fills are Flickering\nOperating system: Linux-5.3.0-40-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 8)\nWorked: (optional)\n\nWhile scrolling or hovering over the *Viewport Gizmos* the Fills starting to flicker. In some cases these artifacts will also be rendered. See screencast (At second 24, I discovered that hovering over the Gizmo made it worse^^):\n\n[grease_pencil_fill_flickering_2.mp4](grease_pencil_fill_flickering_2.mp4) \n\n\n[gp_fills_flickering.blend](gp_fills_flickering.blend)\n\nOpen the attached blend file and hover over the *Viewport Gizmo*, or\n1. Open Blender with *2D Animation* workspace\n2. Draw a closed shape\n3. Fill the shape with a fill color\n4. Press `Tab` twice to change into *Object Mode* (this step is not necessary but in *Object Mode* it seems to be where the problem is most acute)\n5. Zoom in and out and hover over the Gizmo.\n\n\n––––––––––––––––––––––––––\n\nI don't have any silly jokes for you today.^^" ]

[ "Can not selection Armature in MacOS Backend Metal.\nOperating system: Macbook pro 14\nGraphics card: Apple M2\n\n3.6.2\n\n\n\nCan not selection wire Armature in MacOS Backend Metal.\n\nrecorded video\n\nview?usp=sharing\n\nWhen Macos' Backend is set to Metal and the Armature object Viewport Display is wire, objects cannot be selected in bone areas other than the root bone at the location of the origin point.\n\n- Open attached .blend file\n- Try to select any bone in wireframe mode", "Bevel when part of mesh is hidden results sometimes in wrong selection of vertices\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 3.2.0 Alpha\nalso broken in the latest official release of version 3.1.2, also broken in 2.93.\n\nBevel when part of the mesh is hidden and the selected points are not all connected results sometimes in the wrong selection of vertices and lines. I have noticed that the selection is wrong if the number of segments in the bevel attrributes is odd.\n\nOn the default startup file do the following:\n1. Edit the default cube, inset the top and bottom face \n2. Inset again, but only 0.001 \n3. Scale the selection in the Z by 0, \n4. Expand the selection (CTRL++)\n\n5. Shift+H to hide everything currently not selected\n6. Only select the top and bottom \n7. Try beveling, play a little with the segments and switch between vertex and line selection, you will see that not all the lines and not all the vertices that should be selected are selected. It seems to be wrong when you try odd number of segments\n\n\n\n\n\n\n\n", "Sculpt mode. Switching back to tool with brushes from tool without brushes rolls to next brush.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken 2.83.*, 2.91,\nBroken: version: 2.92.0 Alpha\n\nSculpt mode\nCreate 2 grab brushes 1 and 2, that can be switched with G\nSelect Grab 1\nSwitch to mesh filter.\nPress G.\nNow you switched to Grab2 instead Grab1, that was selected before.\nExpected: return to same brush, that was selected before.\n\nIssue appears with:\nLine project, [Box] mask, Box hide, [Box] faceset, [Box] trim, Mesh/Cloth/Color filters, Mask by color, Edit faceset, all transform tools, annotation.\nAffects all tools, who can have few brushes.\nTested with factory startup too.\n\n[2020-12-10_03-13-39.mp4](2020-12-10_03-13-39.mp4)\n[grabroll.blend](grabroll.blend)", "Offset Edge Tool Menu Rescaling Makes It Impossible To Use\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.3 26.20.13025.1004\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nName: Edit Mesh Tools (0, 3, 6)\nAuthor: Meta-Androcto\n\nThe tool menu ad the bottom left of the viewport pops between sizes making it impossible to use\n\nselect edges, use the offset edge with extrude option.\nopen the tool menu in bottom left of 3D viewport, then switch between Angle or Depth option a few times.\nNow hovering over either the Depth or Angle button will trigger it and rescale the menu. This moves the other button up making it impossible to select.[edit menu pops up and down.mp4](edit_menu_pops_up_and_down.mp4)\n\n\n", "'Dissolve' operator leaves inconsistent selection\nBroken: 2.82 (62d131e962d6e0a4f39db98d4f89243c16c55779) (down to, and including, 2.79)\nWorked: N/A\n\nAfter dissolution of edges in Edge selection mode, some vertices not connected with edges remain selected (which is indicated by a tool gizmo, Verts readout in the status bar, and verified by switching to Vertex selection mode).\n\n1. In a empty scene, add a mesh Grid.\n2. Switch to edit mode and Edge selection mode.\n3. Select one edge somewhere inside the grid (not on border).\n4. Dissolve it via the Delete -> Dissolve Edges or a default shortcut Ctrl+X.\n5. Verts readout in the status bar should show 2 selected vertices (despite you being in edge mode with no edges selected).\n6. Switch to Vertex selection mode: the two verts from that dissolved edge are still selected.\n7. Deselect all, switch to Edge selection mode and box-select one square at the corner of the Grid.\n8. Dissolve edges as in (4).\n9. Note that this time, Verts in status bar only shows one selected vertex: switching to Vertex mode would reveal it's the corner one.\n\nIt would seem that the vertices do remain \"selected\" for operators as well: after (4) or (8) you can transform those verts using a gizmo or shortcuts, extrude them (with strange results), connect them using Fill or Connect Vertex Path, and delete them (even though you're in Edge mode).\n\nUpdate: Video demo [here ](FAfhSU2AdbQ).", "Polishing Correct Face Attributes\n- [ ] Initialize operators options based on the \"correct face attribute\" value (e.g., edge slide).\n- [ ] Unify naming of the option and the operator options.\n\nThe way we do Proportional Editing seems to be a good example to follow. These issues have been raised on 4387aff", "Mesh Bevel Node\nNOTE: Design outdated. See #98674 for current design and progress. It is a development task though, so please don't add comments like \"when will this be finished?\"", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "Creating UV Maps from Face Sets\n# Issue\n\nThis is based on a popular request from users.\nOn very high density sculpts with messy topology it's very time consuming to create UV seams and unwrap the UVs.\n\nFor that case it can be a fast solution to use face sets from sculpt mode to create a new UV map.\nSome users already started creating geoemtry node operators and addons to acheive this:\n2017\n\n<video src=\"attachment\" title=\"face_set_to_uv.mp4\" controls></video>\n\n# 'Unwrap Face Sets' Operator\n\nTo get proper feedback on the new UV map it might be best to add an operator \"Unwrap Face Sets\" to the \"UV\" menu in the UV Editor.\nThen the easiest steps to create a UV map from Face Sets is to switch to the UV Editing workspace and do the needed operations there.\n", "Rip edge-move for curves\nCurrently with meshes you can press Alt+D to add a vertex at one side of the verts edges and drag it *(based on the mouse cursor location)*.\n\nThis same behavior could be added to curves.\n\n- the basic behavior with single vertices selected is simple\n- with multiple segments are selected this becomes more involved (see how this works for meshes).", "Wireframe modifier strange behaviour\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.2\n\nStrange behaviour from wireframe modifier\n\n\nTook a plane and subdivided, added a wireframe modifier, unsubdivided. Some corner vertices are pushed to the edge of scene.\n[Based on the default startup or an attached .blend file (as simple as possible)][Wireframe.BugReport.blend](Wireframe.BugReport.blend)\n\n", "Aliased wireframes + modifier edit mode display issue\nOperating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 3.4.1\n2.90\nWorked: 2.79, 2.81\n\nEdit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range.\n\n**Steps to reproduce**\n\n* Open file\n* Disable all anti-aliasing and smoothing in preferences > Viewport > Quality\n\nSelection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.", "Improve UX for interaction of modifier stack and node editor\nWhen a non-nodes modifier is selected as active modifier there is no indication or way to change that in the geometry nodes editor and it's very confusing for the user, especially when the properties editor is not displaying the modifiers panel.\n\nThis is related to #84927\nA potential solution has been proposed there as well (move towards interface similar to shader editor and material slots).", "Set normals from faces should respect sharp edges\nMac OS Sierra\nRadeon Pro 580\n\nBroken: 2.78.5 66383ea206 \n\nSet normals from face effects faces across edges set to sharp. It would make more sense and be more useful if it would respect those edges IMHO.\n\nCreate a cube\nBevel edges across one axis with one segment and mark the caps to sharp in the edge menu\nTurn on auto smooth and set the angle to 180.\nSelect the smooth large faces and \"Set normals to face\" to move the smoothness to the bevel.\n\nThe caps should confinue to be flat since all there edges are marked as sharp.\n\n\n\nI really like this functionallity and I only want it to improve :-D\n\n\n ", "Graph Editor: Link Visible and Selected states\nWorking with many curves in the GE currently requires animators to often toggle the visibility of curves and then select the newly visible curves.\nLinking 'visible' and 'selected' would make it faster to use the GE. However, having those two always linked would remove the feature of having certain curves visible \"in the background\", i.e. visible but unselected. We do not want to lose this feature.\n\n**Proposal**: Add a user preference to link 'visible' and 'selected'. When this mode is enabled:\n- The visibility icon can be removed from the graph editor UI.\n- Selection state determines visibility.\n\nWe think a user preference is best for this, as we suspect it's a personal preference and not so much something you want to manage per GE editor.\n" ]

[ "Unable to choose vertex after clicking snap transform (retopo)\nmacOS High Sierra 10.13.6\nMacBook Pro (Retina, 15-inch, Mid 2015)\n2.5 GHz Intel Core i7\n16 GB 1600 MHz DDR3\nAMD Radeon R9 M370X 2048 MB\nIntel Iris Pro 1536 M\n\nblender 2.80 alpha 2\nHash: ba36e901701\n\nWhen trying to snap vertex to a mesh and retopologize it.\nediting in wireframe mode.\n\nI am clicking the snap button (magnet), it works fine, BUT when changing it to a different mode FACE, EDGE AND VOLUME. clicking the vertices is very difficult. some of them i am unable to click at all and some of them are chosen when i offset the mouse position and then click. \n\nclicking out of edit mode and back in seems to fix the issue.\n\nalso, it looks like it happens only on the first time you are in edit mode, after exiting and entering again it won't give you any problems, so sorry that attaching a file is not possible.\n\n \n\n", "Selection becomes inaccurate in specific areas after (seemingly) random amount of time causing the need to switch from Edit mode, to Object, then back to Edit mode to get it to work again.\nOperating system: Windows 10\nGraphics card: GTX860m\n\nblender-2.80.0-git.4c31bed6b46-windows64\n\nBroken:\nWhile working with vertices and the box selection tool, eventually I can no longer select the vertices in the area in which I was working. If I try to select the ones near it, it will select the incorrect ones. If I go farther from the affected area the selection works just fine.\n\n[I am able to get it to work again by switching from Edit mode to Object mode then back to Edit mode as seen in this video link. ](watch?v=zOI9mnHZ0uE&feature=youtu.be)\n\nI was using transparency, box selection tool, and working with vertices. This keeps occurring after an unknown amount of time. Once switched to Object mode then back to Edit mode it will be fine again for some time. (about 5-10 minutes of working) and then it will happen again.", "Difficulty in selecting vertices, arrests and faces in \"smaller areas\"\nOperating system: Windows 10 Pro \nGraphics card: GTX 760 + AMD Ryzen 5 2600 six-core \n\nBroken: 2.80 (blender-2.80-925380050d0-win64.zip)\n\n\n**I am having problems with selecting vertices**\nI did not make any changes to Blender or I used addons.\nWhen entering and exiting Edit Mode, it causes the problem to disappear for a few minutes, after zooming in a few times the problem appears again.\n\nI'm attaching a video to demonstrate: PetF0zRCnlk\n", "Selection in XRAY mode is broken\nOperating system: Windows 10 Home x64\nGraphics card: GTX 1080 Ti\n\nblender 2.8, 2018-12-04 - 04:09\nHash: 925380050d0\nBranch: blender 2.8\n\n\nThe selection of vertices on wireframe or xray mode is broken. After moving a vertice on Wireframe mode you can only pick up the same vert again by clicking on its previous position, not on it's current position.\nDraging a selection box or using the selection brush around the vert doesn't do anything either. \n\nA workaround is to change from edit mode to object mode and back to edit again, this way you can select the vert by clicking on it and not on its previous location.\n\nThis bug is very frustrating, specially when modeling in ortho trying to match a background sketch/picture.\n\nThe bug is very easy to replicate:\n\n1. Open any file with any geometry in it;\n2. Turn on Wireframe mode;\n3. Move any vert/edge/face away from the geometry;\n4. Try picking the same vert/edge/face again;\n5. Try clicking on the previous location of the vert and see the same vert that is now far away being selected.\n\nI've tested this with the latest 5 or 6 builds of Blender 2.8 and the bug still exists.\n\n\nUPDATE:\n\nI've tested with several 2.80 builds and every single one of them have this bug.\n\nI did further testing and I can say that this bug also happens with faces and edges.\n\nThe problem seems to be XRAY. If I disable it I can select everything as it should, but this way I can't see through the object.\n\nThe problem still persists if I use XRAY with Matcap mode.\n\n\n\n", "Can't select vertex/face when \"Show whole scene transparent\" is enabled and you have moved a face\nOperating system: Windows 10\nGraphics card: Nvidia Geforce GTX 980 TI\n\nBroken: 2.80-be012c88c52-win64\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen you go into object edit mode and select a vertex/edge/face and then move it you can't select the element again until you exit/enter object edit mode again. As if the selection function is looking at old vertex/edge/face positions. If you click where the vertex *used* to be, you can select it.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Start new default Blender scene\n2. Press Tab and go to object edit mode\n3. Click \"Show whole scene transparent\" icon (so you see and can select back faces)\n4. Select a vertex and move it somewhere\n5. Select another vertex and move that one somewhere\n6. Try to select the vertex you moved in the first place (you can't)\n7. If you click where the vertex used to be, you can select it again\n\nThe problem doesn't occur when you don't have see through (\"Show whole scene transparent\"). If you exit/enter object edit mode again it has refreshed the location so selection works again.", "unable to select vertices in their actual location\nOperating system: Linux Mint 18.3 Cinnamon 64-bit\nGraphics card: Nvidia Geforce 760\n\nBroken: 7ec5a68091a\n\n\n\nonce moved, vertices cannot be selected in their actual location, but the former location.\n\n\nfrom factory settings\nselect the default cube\nenter edit mode\nactivate \"show whole scene transparent\" option\nselect the 4 bottom vertices\nmove them on the Z axis about 1 unit (or move it to the Z= 0 position)\ndeselect all\nthe four vertices you just moved cannot be selected using box, lasso or circle select in their actual location, but they can be selected in their former location\n", "Selection Space is not maintained in edit mode\nOperating system:\nGraphics card:\n\nBroken:blender2.8\nWorked: (optional)\n\nWhen working with edges or vertices after while of working in edit mode if you try to select certain vertices it wont select them properly unless you click at its previous position. you can reset it by exiting and re-entering edit mode\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Wrong vertices are selected in edit mode\n\nSystem info:\nOS: Ubuntu 16.04 64-bit\nProcessor: i7-6700HQ CPU @ 2.60GHz × 8 \nGPU: GeForce GTX 1060/PCIe/SSE2\nCycles Compute Device: CUDA/ GTX 1060\nAdditional info: tDDDA6J.png\n\n\n\nBlender hash: 0f5b53ba4dc\nDate: 2018-11-30 22:29\nBranch: blender2.8\n\n64-bit Linux build (1. Dec 00:09:31)\n\n\nThis is a bug affecting vertex selection in edit mode. It causes wrong vertices to be selected.\n\n\n1. Start Blender with the default startup file.\n2. Zoom in to the default cube (don't rotate the view*).\n3. Apply Subdivision (Catmull-Clark) level 3 to get some geometry.\n4. Switch to wireframe.\n5. Enter edit mode and deselect all.\n6. With circle select tool select part of the sphere and drag it outwards: https:*i.imgur.com/zu9Vj9T.png https:*i.imgur.com/ztrZqRb.png\n7. Now if you click with the circle select tool where the vertices used to be, those vertices will still get selected: DdndMKL.png\n\n* Rotating the view sometimes induces even more funky and unpredictable behaviour.", "Vertices visible in XRay/Edit Mode can't be reselected after initial select and transform operation\nMac OSX Sierra (10.12)\nnVidia GeForce GTX 780\n\nBroken: 2018-11-10 00:04\nHash: dc21ef7b86c\nBranch: blender2.8\n\nVertices visible in Xray/Edit Mode can't be reselected after initial select and transform operation\n\nTab into edit mode, Select a vertex in wireframe view mode (at the back of the mouth in the included .blend file), move it, select another vertex, move it also, attempt to select the first vertex again, and it will be un-selectable. This happens in more than just this file, and on multiple computers. I hope I'm submitting this correctly. This is my first time submitting a bug to the Blender Foundation. Thanks.\n\n\n[T-Rex.005.bugfix.blend](T-Rex.005.bugfix.blend)\n[system-info.txt](system-info.txt)\n", "Lasso and Box Select tools does not work properly after scale\nWindows 10\nGTX660TI-DC2\n\nBlender 2.8 2c2c996a1b2\n\nLasso and Box Select tools does not work properly after scale\n\n1: Create a cube, enter Edit mode, select all and scale\n\n2: Lasso or Box Select staying close to the vertices. \n\n3: Selection does non include all vertices inside the selection as supposed to do. If the selection is very large it works, but if you stay closer to vertices don't.\n\n\n\n\n" ]

[ "Sculpt Mode - Using Mask while Multiress active = Crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.2\n```\n Tried also with\n```\n 2.83LTS\n 2.92beta 77f73a928439\n 2.93.0 ae1e68f5146d\n\nWorked: None\n\nWas working in Sculpt mode, tried to hide the arms and the program crashed.\nI tried with another objects with multires and it doesn't happen\n\nHere the .Blend with the problem\n [Multires prueba.blend](Multires_prueba.blend)\n\nGo to Sculpt Mode -> Try to mask with mask brush, Mask Lasso or Mask Box", "Sculpt mode -> Curve Stroke causes Undo to behave differently\nOperating system: Windows 10 x64\nGraphics card: Nvidia 980 GTX\n\nBroken: v 2.82 Alpha, 10-12-2019\n\nIf Brush stroke is set to Curve and some sculpt detail is added (Ctrl + Left Click), (Ctrl + Z) or Undo does not work. Instead of Undo for the sculpt detail, the curve control points are removed.\n\n1. Start with default cube and add Multi-Res modifier, subdivide a couple of times.\n2. Go to sculpt mode and with the SculptDraw brush set the stroke to Curve.\n3. Draw a curve using (Ctrl + Right Click) to add some control points.\n4. Add sculpt details using Ctrl + Left Click. \n5. Press Ctrl + Z. Instead of removing the details the control points of the curve will be removed first. \n6. Press Ctrl + Z repeatedly. When the last control point remains then the sculpt detail will be removed.", "Erase Alpha in vertex paint not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\nWorked: latest 2.7 nightly build date 2019/06/27\n\nErase Alpha not showing in viewport.\n\ngo to vertex paint set mode to erase alpha and when painting nothing happens.\nalso found no ways to use the alpha data.\n\nVertex Alpha painting are needed for asset creation on some game engines like creation engine.\n", "Remesh Modifier in Voxel mode produces surface artifacts when Adaptivity enabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: \n - 2.83.9\n - 2.91.0 Beta\n - 2.92.0 \nWorked: never\n\nRemesh modifier produces artifacts on mesh which look like a result of bad triangulation.\n\n1. Open attached blender file\n2. Open modifier panel and select testMesh\n3. Change adaptivity value from 1 to 0 cm and back\n4. Observe black shading artifacts \n[remesh_bug.blend](remesh_bug.blend)\n", "Sculpt mode: Set Pivot to Mask Border doesn't work with the initial mask generated by the Box/Lasso mask tools\nWin 10\n\nBroken: blender-2.81-382e7ce9ecfb-windows64\nWorked: ?\n\nThe Set Pivot to Mask Border function doesn't work with the initial mask generated by the Box/Lasso mask tools.\n\nLaunch Blender\nOpen the Sculpting template (File ➞ New ➞ Sculpting)\nChoose the Box or Lasso mask tool\nMask a part of the mesh\nSelect one of the Transform tools (just to see the pivot)\nRun the Set Pivot to Mask Border (Sculpt menu ➞ Set Pivot ➞ Pivot to Mask Border)\n*And nothing happens* \n\n[2019-10-18_18-09-13.mp4](2019-10-18_18-09-13.mp4)\n\n**Note**, if I \"blur\" the mask **(Mask menu ➞ Smooth Mask)** then the \"Pivot to Mask Border\" will start working.\n\nAlso, masks generated with the regular mask brush don't have this problem...", "Stroke overlay when erasing\nOperating system: Win 10\nGraphics card: NVIDIA GeForce GTX 1070 Ti\n\nBroken: (example: 2.80, 66684bdff30f, master, 2019-07-05)\n\n\nThe new alpha overlap stops working, when you erase somethin of that stroke.\n\n \nOpen a new project create a blank stroke object draw something try to erase it", "Undo eliminates brush texture\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: version: 3.0.0 Alpha\n\nI think it shouldn`t be undoable as other brush settings now.\nIt is much easier to delete texture manually, than restore it and tune it again.\n\n[2021-05-26_14-00-22.mp4](2021-05-26_14-00-22.mp4)\n\n\n", "GPencil: Average tool in Vertex Paint mode not working as expected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.0 Beta\n\nThe tool paints colors that exist in points far from the brush's area of influence and sometimes paints unexisting colors.\n\n1. Draw simple strokes with the Solid Stroke material.\n2. In VP mode paint half of it orange and half blue.\n3. try the the Average tool in the half blue area then in the other half.\n4. Now do Paint > Reset Vertex Color.\n5. Try the Average tool again.\n\n<video src=\"attachment\" title=\"Vertex Paint Bug-1.mp4\" controls></video>\n\n", "AutoDepth ignores texture transparency\nOperating system: Win 10 64-bit\nGraphics card: 980 Ti\n\nBroken: 2.93.4 LTS, 3.0 alpha (including current latest build)\nWorked: 2.79\n\nWhen navigating using mouse with auto-depth enabled, the full-transparent parts of textures should be ignored when picking the depth.\nThis worked correctly in 2.79, but 2.93 and the latest 3.0 alpha seem to ignore this.\n\n\nEnable Auto-Depth, create an object, assign it a material with some full-transparent texture, then try to zoom / pan using mouse with the cursor on it.\n[autodepth-transparent-issue.blend](autodepth-transparent-issue.blend)", "Missing undo push for Paint Mask and Vertex Selection in weight paint\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.0.0 Alpha\n\nEnabling or disabling of the Paint Mask and Vertex Selection modes is missing an undo push\n\n\n\n[Weight.blend](Weight.blend)\nEnable Paint Mask\n\nPaint on the model\nUndo\nResult: Both the paint and the paint mask mode are undone", "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "ParticleEditSettings not updating when choosing tool from toolbar\nNot working Hash 1944bca49a\n\nBranch 2.8\n\nStep to reproduce:\n\n1. Open [hair_weight.blend](hair_weight.blend) you should see weights.\n2. Select another tool.\n3. You should not see weights but you still see them.\n\nThe display batch is reconstructed if ParticleEditSettings->brushtype changes but this only works if you change the brush type in the toolsettings panel.\n\nMust be a missing notifier/deg update.", "GPencil: Fill tool Ignore Transparent strokes setting broken\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Beta\n\nFill tool not ignoring transparent strokes when the settings is enabled. When you enable Show boundary lines, it shows that transparent strokes are not a boundary but the fill still uses them as boundaries.\n\n- Open attached file and try the fill tool. Under the Advanced menu 'Ignore Transparent' and 'Show Lines' are enabled.\n\n", "Sculpting - Cloth brush - Snake Hook deformation not working\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\n\nBroken: version: 3.5.0 Alpha\n\nThis is the image I got after kept dragging my cloth brush around the same spot for a few times:\n\n\nand this is the file I'm using:\n[20221206_sculpt_cloth_brush_snake_hook_donot_work_0001.blend](20221206_sculpt_cloth_brush_snake_hook_donot_work_0001.blend)\n\nI personally think the option is 'wired' to a wrong block of code.\n\n", "Sculpt: masks / face sets invisible in X-ray mode\nOperating system: Windows 10\n\nBroken: 2.91.0\n \nSculpt mask is invisible in X-ray view mode, but you can still paint the mask while in Xray.\nThis makes it hard to trace the background image when masking.\n\n \n\n" ]

[ "Grab brush used on Multires with Auto-Masking Topology enabled are breaking the mesh\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.83.2\n\nGrab brush used on Multires with Auto-Masking Topology enabled are breaking the mesh \n\n\n\nLooks like it's picking vertexes from some subdivision levels and ignoring others. Pose Brush acts how it is supposed to, though. \nOn flat geometry result is even worse: \n\n\nAlthough, there's some apparent correlation to the base level: \n\n\n\n1. Create a scene\n2. Switch to the Sculpt Mode\n3. Subdivide a few time\n4. Select Grab Brush and enable Auto-Masking by Topology\n5. Grab the model\n\n" ]

[ "3D Connexion Space Mouse Pro - Blender 2.82a on macOS\nmacOS Catalina 10.15.4 (19E287)\n3D Connexion 3dWare10 10.6.5\n\nBlender 2.82a\n\n\nThe mouse appears to almost match the 3D Connexion training app in terms of movement when in object/edit mode but it would appear that none of the buttons & especially the MENU do not work. \n\nI have installed the 3D Connexion drivers a second and third time with firewall and anti-virus off and the problem with these mice seem to persist. \n\n>> This has been edited by another but im wondering if there is some resource file missing where keys are mapped, either this is a 3D Connexion plug in or something to do with Blender?\n\n\nI've seen these tasks; It's still a problem for me. \n#67686 (NDOF mouse not working in code signed macOS builds)\n#67971 (3D Connexion Space Mouse Enterprise Custom Buttons 1-10 Not working in Blender 2.8 (macOS))", "Support Dragging Assets Into the Outliner\n- - [ ] Objects\n - - [ ] Drag into empty space in *View Layer* or *Scenes* display mode instantiates the object at the 3D cursor (TBD: Active collection or scene collection?). Linking places it at the location from the source file.\n - - [ ] Drag onto/into collection does the same, but assigns it to given collection. Rather not support modifier keys like {key Shift} to parent at first, better keep asset dragging simple and let users decide which collection the object should live in first. They can do the parenting then.\n - - [ ] Drag into the *Blender File* display mode only adds the object to the file, doesn't instantiate it? \n - - [ ] Dragging onto/into a collection there could still instantiate.\n- - [ ] Other Datablocks\n - - [ ] Other data-blocks only get added to the file by default\n - - [ ] Dragging materials or meshes onto objects could reassign. (Probably should consider where it's dragged to exactly, e.g. a material dropped onto another material could replace it, or add a new material slot if dropped in-between two existing ones.)\n\nMore type dependent behavior could be considered/investigated. E.g. maybe it's nice to have an image empty created when dragging an image to the Outliner.", "VSE's selection not centred to images\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.1.0 Alpha\nWorked: Never\n\nWhen zooming in enough to a selected image's corner, it can be seen that the selection box (white rectangle) reaches outside the image itself. It also happens with a scaled down \"color\" strip.\n\n- Open a \"Video Editing\" workspace and add a \"Color\" strip\n- Scale it down and zoom to a corner\n- To better notice the issue, play with the resolution of the Preview (in Properties)\n\n\nNotes & thoughts:\n- The selection box (white box) is unresponsive to \"aspect ratio\" changes (in Properties)\n- The drifting of the image is somewhat annoying, and sticking the selection box to the image wouldn't fix this.\nSince I don't know how pixel alignment works in the preview, I'm not sure about this, but it may work to instead drift the canvas, leaving the image put like the selection box currently does. So sticking the image TO the selection box.", "GN: Delete Geometry node hides edges in some cases\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.2.0 Alpha\n\nHard to describe this one more abstract..\n\nI start with a mesh line primitive (0,0,0) (0,1,0) and extrude it **n** times along **x** to get a grid.\nNow I try to delete all points with a distance from the **y** axis greater than **d** \nWhenever **d** lies between the first and the last extrusion, the edges of the starting primitive are not displayed.\nIt shows up in the spreadsheet however and reappears if I apply the modifier and tab into edit mode and back \n\n[2022-02-05 19-27-50.mp4](2022-02-05_19-27-50.mp4)\n[del_geo_node.blend](del_geo_node.blend)\n\n", "Texture Node Editor Using nodes causes weird issues in sculpt mode.\nOperating system: Linux-5.15.0-48-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.76\n\nBroken: version: 3.3.1\nWorked: perhaps never? (can redo in 2.83)\n\nAdding an image from the nodes of the texture editor for example, a sculpting brush, causes really weird issues. Disabling nodes and using the texture properties does not have this issue.\n\n- Check the blend file. Try sculpting, you will see weird noise being displaced with the texture.\n- Now disable the nodes and set the texture type from the texture properties to the same image. Sculpting again you see the issue is not happening.\n[bug.blend](bug.blend)\n\n\n\n", "Console warning \"ToolSettings\"/ \"snap_node_element\"\nOperating system: Windows 10\nGraphics card: Geforce GTX 970\n\nBroken:\n2.80, 8c8979067490, blender2.7, 2019-01-31\n\nI was importing a file from an older blender version and I noticed this error in the console:\n\nIt appears when you hover over the node editor and when toggling edit mode.\n\nThe reason I think it's not an issue which appears because of the different blender version is that I recently released an addon for managing nodes with layers and a few people noticed similar errors when editing a mesh with KitOps or similar addons and then trying to change the nodes.\nI also don't think it's an issue with my addon as I didn't change the file (included) with the addon and I tried it with a clean blender version as well.\n\n[warning_message.blend](warning_message.blend)\n- Open the file\n- Open blender console to see error messages\n- Hover over node editor with the cursor\n- > Warning message should appear", "The viewport may update at 0 FPS while navigating, until the mouse is released.\nOperating system: Windows 10\nGraphics card: RTX 3080 Ti\n\nBroken: 3.0.0\nWorked: 2.92.0\n\nWhen working in sculpt mode on a model with multires modifier, the viewport may update at 0 FPS while navigating, until the mouse is released.\n\nUsually when navigating in sculpt mode on a model with multires modifier, the model will switch to a low poly version while navigating. When this bug is happening, the viewport remains frozen and the high poly model remain on screen until mouse is released.\n\nThe bug will be temporarily fixed upon clicking on another application or resizing the blender window.\n\n1. Shift+A to create a plane\n2. Ctrl+E and subdivide it 4 times.\n3. Attach multires modifier onto the plane.\n4. Subdivide it 6 times with the multires modifier.\n5. Use sculpt mode and sculpt without moving the view for around 1~2 minutes (I used a wacom tablet. Using the sculptDraw brush, I added / subtracted (hold ctrl) from the mesh, also using smoothing brush (hold shift) to smooth certain parts, and undo (ctrl + z) multiple times to simulate a normal working environment.)\n6. Try to pan or rotate the view around.\n\n\n\n**I found another way to trigger this bug, and it's not strictly related to sculpt mode.**\n(Tested on blender 3.1.0 beta 03b57d3973)\n\n1. Click around with a Wacom tablet.\n2. Pan the camera around with a Wacom tablet.\n3. Pan the camera around with a mouse.\n\n\n[sculpt mode bug.blend](sculpt_mode_bug.blend)\n\n[2022-01-17 04-48-11_Trim.mp4](2022-01-17_04-48-11_Trim.mp4)", "Node Tools Overview\n## Background\nWith node group assets becoming more prevalent and geometry nodes becoming essential\nfor manipulating geometry in Blender, we want to add the ability to implement operators\nwith geometry node groups.\n\nRelevant node groups would need a geometry input and output, and could have other inputs (and possibly outputs), with similar mappings as the geometry nodes modifier.\n\nAdditionally, specific inputs could be marked as editable modally, for example, a \"Factor\" input could be controlled by moving the mouse cursor left or right.\n\nThe specific data design still needs to be settled on (i.e. is the node group an operator, or does an operator reference a node group?).\n\n## Design\n- The node group itself is the operator asset\n- Geometry nodes gets new input nodes\n\t- Selection\n\t- Mouse coordinates\n - View transform\n - 3D cursor location\n - etc.\n- Geometry node groups with these input nodes can only be used as operators\n\t- This design is similar to the shared node groups between shader and geometry nodes, for example.\n- The group outputs are used to adjust the output geometry\n\t- The geometry output will adjust the \"active\" geometry\n - We _might_ need to store a specific mapping for outputs, but relying on the name is a start\n- The project is \"completely finished\" when any existing edit mode operator could be implemented with nodes\n\n## Implementation\n\n_Organized by priority in each category_\n\n### 4.0 Targets\n\n_Changes needed to move the feature out of experimental and enable it in the release_\n\n- [x] Initial basic feature for curves sculpt mode e4cc91a6113f14418b5d8f2a0aace252dc3949d8\n- [x] Allow controlling which modes assets are available in fd9d22ba57d75b278a0350492c5eab2d39d39070\n- [x] Update 3D view menus dynamically (avoid need to restart Blender) cc83951951efc28411960d950435224e8d06606c\n- [ ] Make object info node geometry output work properly\n- [x] #111529 Show menus for unassigned node group assets d2d4de8c710c4e8e648a86f904e6436133664836\n- [x] Tool specific nodes\n - [x] Selection input e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] Set selection e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] 3D cursor e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] Sculpt face sets input e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n- [ ] Node group inputs displayed in the redo panel\n - [x] Initial input drawing bc393c403325c956ec4e83eeb072a9bdb2e7824d\n - [x] Display node group name in panel title f0467b4615b366f34f0daae81ef717c342e8f520 ee1ee584ded3b76fdd9b661244274af850b08fa9\n - [ ] Add attribute search\n - [x] Don't draw redo panel when there are no inputs c59d998ce524e37c2449694602fb6d57b6d292fa\n- [x] #111523 Improved default traits b4dc16f32d92a2fbc140abfe6eb438ff11b5d5e8\n- [ ] #111524 Finalize trait popover locations\n- [ ] Add support for evaluating output attributes\n- [x] Shortcut support 65591b2c8cc83b024bc0a283bae1bbeb7ee85132\n- [x] Quick favorite support 65591b2c8cc83b024bc0a283bae1bbeb7ee85132\n- [ ] #111526 Filter data-block selector based on tool/modifier option #112389\n- [ ] Publish the user manual\n\n### Polishing\n\n_Not necessarily required for a release in main_\n\n- [ ] Show visual difference for tool nodes in modifier context\n- [ ] Show visual difference for viewer and simulation nodes in tool context\n- [ ] Resolve flickering in asset browser when using redo panel\n- [ ] Warnings in node editor header\n - [ ] When node group is not an asset (with button to mark as asset) #110813\n - [ ] When the node group is not marked as a tool #110813\n - [ ] When asset is not in a catalog (and not in a menu) #110813\n\n### Milestone 2\n\n_The second phase of the project, after the fundamentals are working well_\n\n- [ ] Option to show settings in popup before operation starts\n- [ ] Tool specific nodes\n - [ ] Sculpt \"soft selection\" input and set\n - [ ] View transform\n - [ ] Mouse position\n - [ ] Deformed (\"cage\") positions\n- [ ] Modal operator support\n- [ ] \"Wait for cursor\" option\n- [ ] Store operator properties for the next execution\n\n\n## Use Cases and Ideas\n- [ ] Mesh sculpt \"face set extract\"\n- [ ] Mesh sculpt \"mask extract\"\n- [ ] Lasso selection operator", "Point Clouds only support one material\nOperating system: macOS-13.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken version: Current main.\nWorked: Never\n\nWhen using the `Join Geometry` node in Geometry nodes to join two points together, their material is reset to default. This only happens when joining two or more \"lone\" points.\n\n1. Recreate the geometry node setup found in the image below\n2. Change the render engine Cycles (necessary to see points with a material)\n3. Render the scene.\n4. Notice that the materials you assigned to the points are not applied.\n\nI have also included a .blend file with steps 1 and 2 done.\n[Missing Material - Join Geometry.blend](attachment)\n\n\n", "View zoom (scale mode in particular) doesn't work well when dragging horizontally, or crossing the middle of the screen\nBroken: 2.79, 2.80, 2.81 HEAD (8c9e6f123a2).\nWorked: ?\n\nNavigation Mode Scale Is Broken - it should never be calculated from the vector zero.\n\n- Set Blender Navigation to Scale\n- Try to press Alt + click and drag in viewport to make it zooming (or click and hold the \"zoom\" icon in the viewport).\n- Try to cross the mouse arrow in the vector zero (i.e., cross the mouse around the middle of the viewport).\n- As you can see the tool start to work weirdly inverting the zooming as soon you cross the scene vector zero.\n\nNote: The other zoom modes (e.g., dolly) also present a strange behaviour when zooming horizontally. But the zoom seems to reset when going over the origin regardless of the mouse direction.\n", "Selection to Active doesn't work when the selected object is a child of the active object\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.25\n\nBroken: version: 3.3.0 Beta\n\n\nSelection to Active operator doesn't work when the selected object is a child of the active object.\n\n\n1. Add 2 cube.\n2. Parent one of the cubes to the other.\n3. Select both cubes such that the parent is active. \n4. Use the Selection to Active operator.\n5. The operator has no effect.\n\n", "Alt modifier key to disable node auto-connection\nWe often get requests to make the behavior of auto-connection when placing nodes optional. This is because it can be tricky to place a node without connecting to overlapping links, among other reasons.\n\nA simple solution discussed in earlier [sub-module meetings ](22309) was is using the `alt` key to disable the auto connection.\n\n", "Generated texture coordinates missing when switching from solid to rendered mode\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.80.0-git.14884cda1ff5-windows64\nWorked: 2.79b f4dc9f9d68b\n\nThe \"Generated\" texture coordinates make textures \"stick\" to the surface, even if the object is being deformed.\nHowever, this does not work as expected in 2.80 with the Armature Modifier, neither in Eevee nor Cycles.\nIn 2.79 in works correctly.\n\nPossibly related: #59275.\nHowever, this bug affects both Cycles and Eevee, while that report only concerns Eevee (and Cycles works correctly).\nThe difference is that here an Armature is used, while that report uses Shape Keys.\n\n[generated.blend](generated.blend)\nThe scene contains a cube with an armature modifier.\n- Open in both 2.79 and 2.80.\n- Press F12 to render.\n- See how the texture mapping differs.", "Subtype for input value nodes\n\nThe user may be at a loss when entering a rotation radians value into some built-in node, copies it into the input value node, and now these are degrees.\nThe explicit way of specifying the sub type must be an option for all value input nodes that it can have.\nThe type list option should be available in the N-Panel so as not to clutter up the node space.\n\n", "Multi-Button Drag: not working properly for Object Dimensions\nWindows 7\n\nBroken: 2014-02-11\n\nMulti-Button Drag - D270 - doesn't work properly in N panel for Dimensions\n\nIf you drag over all 3, only X and Z change, Y remains unchanged. As mouse button is released, the first selected property will reset, only the last hovered is kept (and scale changed)" ]

[ "Node input output grabbing\nOperating system: Windows 10 Pro 64 bit\nGraphics card: GTX 1060 6GB\n\nBroken: 2.80 4c31bed6b46\n\nNot so much an error, but a work flow problem. When editing nodes, I find myself not selecting the circles outputs on the nodes to attach to other nodes inputs, but instead highlighting a small part of the screen. Did not have an issue with this in 2.79b, maybe you guys can increase the radius selection of the node inputs and outputs? It's just a minor thing compared to a lot of other issues you guys are probably working on, but it is annoying having to zoom in on nodes just to select an output circle to drag to an input circle\n\nJust try and use the nodes, the output selection box is smaller than 2.79b which makes it harder to grab and drag to another input", "Node inputs and output \"hit boxes\" are smaller when different select options are used.\n**System Information:**\nCPU: Ryzen 5 2600\nGPU: RX 570 4GB\nOS: Windows 10 Home\n\n**Blender Version:**\nBroken: Blender 2.8 Beta 26d5a3625ed\n\n**Short description of error:**\nIn the node editor (*I've only tested the shader editor*), the \"hit box\" of the input and ouput of nodes are harder to select while the \"Select Box\" or \"Select Lasso\" tools are active in comparison to the \"Select\" tool. Notable, the edges of the input output sockets." ]

[ "The walk mode is stuck when it is enabled while using a tablet pen\nOperating system: Windows 10\n\n\nBroken: 3.0.0\n\n\nThe walk navigation mode goes does not trigger right away when it is used with a Wacom tablet in Windows Ink mode. The Win ink is set both in Blender and the Wacom properties.\n\nHere I enable the walk mode, but it does not move at all until I lightly move the mouse. After that it works.\n[ClvNCLQx0H.mp4](ClvNCLQx0H.mp4)\n\nUse a Wacom pen \nEnable Windows Ink in Wacom panel and in Blender\nEnable Walk navigation", "Pie Menus initiated by tweak events will disable the mouse button used in the tweak event. Works fine for regular menus, operators.\nWindows 10\ngeForce GTXTitan\n\nBroken: blender-2.77.0-git.94e18c5-AMD64\nWorked: (optional)\n\nI've set up some UI shortcuts that use 'tweak' events (or directional gestures) for various pie menus, regular menus, and operators. This work fine for regular menus and operators. After calling a pie, however, the tweak button defined in the input editor (left, right, middle, action) becomes unusable. \n\n1) Open User Prefs, select the add-ons tab, and enable Official Pie menu addon\n2) Select the 'Input' tab in User Prefs, and in the keymap filter (set to name), type the the word 'pie' without quotes\n3) The first filtered pie is 'Frames'. change the hotkey as follows: \nClick the event mapping dropdown (its set to keyboard by default), and change to Tweak. two new options appear next to it: 'Left', and 'Any'.\nChange the type of event, or leave it as 'Left' \nChange 'Any' to a direction.\nSelect a modifier key such as Shift\n\n4) go to the 3d view and execute the new shortcut you set up. The playback options should appear in the pie menu but are not selectable. Hitting the escape key will get out of the pie, but the defined tweak button is not usable.\n\nNOTE: If you use the default right click select, you can still place the cursor, but can't trigger the shortcut again. If left click select is set, then normal tweak events like moving selected objects are also not possible.\n\nNOTE: Toggling Object/Edit mode will make the button usable again.", "Touchscreen 'Continuous Grab'\nOperating system: Linux-4.15.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Haswell Mobile Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.0.2\n(bug also tested on Windows 10)\n\n\nBroken: version: 2.80 (sub 74)\nWorked:\n\n\n* Activate a gizmo using the **touchscreen** on a computer. (The 3D navigation gizmo for example)\n* Drag your finger outside the original editor\n* The gizmo is manipulated incorrectly\nThis bug disappears if \"*continuous grab*\" is disabled in the User Preferences.\nI think it's a matter of auto-disabling *continuous grab* while receiving touch input, like how pen tablets are handled.", "Can't uninstall completely and clean\nwindows 7 SP1 64 bit\n\nBroken: 2.75a c27589e\n\nCan't uninstall completely when used \"Uninstall blender\" from Start menu, and need to manually delete\n\n\nthe old version (with .exe packed ) has an option that let's you select \"leave user setting\" or \"remove all things\" when you uninstall, but the new version (with .msi packed) no this option for uninstall, and will leave some files on your computer, by the way, it's have't choice for your install, e.g. create a desktop shortcut, use blender for .blend flies, and create start menu, all blender default at install, and I can't custom setting for this, although this no affect for our used, but i'm a little OCD :D\n\nsorry for my bad English :)\n", "Hair Dynamics: simulation doesn't work depending on smooth/flat shaded surfaces (and nvidia gpus?)\nOperating system: Windows 10\nGraphics card: RTX 2070 QMax\n\nBroken: v 2.80\nWorked: (optional)\n\nhair dynamics doesn't work, hair stuck in place, doesn't follow the mesh\n\n- build simplest possible model with hair dynamics\n- add simple animation\n- with hair dynamics disabled: hair follows mesh\n- with hair dynamics enabled: hair just stays behind and stretches to the mesh\n- changing settings, clearing cash ... all to no avail\n\n[190814_test_hair_dynamics.blend](190814_test_hair_dynamics.blend)\n\n", "Keymap changes are not reflected for the local view setting\nOperating system: Linux-5.18.10-arch1-1-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.57\n\nBroken: version: 3.3.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked:\n\nWhen I turn off frame selected in keymap -> local view and restore it to its default it keeps the old behavior until blender is restarted.\n\nI tested changing delete in object mode (x) key to disable confirm and when I restored it it worked as expected so I think it is related to local view specifically.\n\n- Open default scene\n- In Preferences > Keymap: search for local view and uncheck `Frame selected` checkbox\n- use the shortcut in viewport. Notice frame select operation is not performed (which is expected)\n- In keymap, restore changes\n- Again use shortcut to switch to local view (frame selected operation is expected to execute but it doesn't)\n\n\n", "Update Tweak Tool behaviour on Right Click Select\nThis has been a long running known issue for the Active Tools when using right click select.\n\n## Issue\nOn RCS, the Tweak Tool in the toolbar is placing the 3D Cursor instead of tweaking elements.\nThis duplicates the behaviour of the Cursor Tool (right next to it in the toolbar).\n\nThe reason for this seemed to be that right click & drag is already using the tweak action.\nIf the Tweak Tool would tweak with left & right click then there is no way of setting the 3D cursor anymore.\n\nBut the Tweak Tool doesn't require the 3D cursor. And this workaround is breaking the tweak tools purpose.\n\n## Solution\n\nThe Tweak Tool needs to tweak with left click & drag.\nThis can be it's own keymap item in the preferences under the Tweak Tool.\nRight click & drag can still use the default tweak action in the preferences.\n\nThe benefits are:\n- The Tweak Tool can be used without a drag threshold with left click & drag, if the option \"Alt Cursor Access\" enabled in the preferences\n- There is a functional distinction between the Tweak Tool and the Cursor Tool.", "Assign shortcuts: add support for enum menus\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nFor group menus, can't assign shortcuts by right click, and no python tooltips on this. maybe it's not bug, but really need it.\n\n\nscreenshots:\n\n\n\n\n\n\n", "can't use logitech mx master 3 mouse shortcut keys in blender 3.6 LTS\nOperating system: Win 11\nGraphics card: RTX 3070\n\nBroken: (3.6 LTS)\n\n**I can't use the logitech mx master 3 mouse shortcut keys in blender 3.6 LTS.**\n\n\n", "Insert keyframe wrong with cycle-aware keying after deleting end frame\nOperating system: Linux-6.4.6-arch1-1-x86_64-with-glibc2.37 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.86.05\n\nBroken: version: 3.6.0\n\nI have an action with manual frame range, 1 to 11, with cyclic animation checked. I have cycle-aware keying on.\n\nI'm not sure exactly when the bug starts, but eventually adding a frame at time 9 creates the keyframe at frame 4 again.\n\n\nI'm not sure exactly when the issue started, but roughly\n1. Cube\n2. Insert frame at time 1\n3. Turn overlay action into layer (stack?) action with the down icon button\n4. Set up manual frame range 1-11, cyclic\n5. Turn on cycle-aware keying\n6. Insert another frame at time 6, blender automagically adds a frame at time 11 to match the frame at time 1\n7. Delete the frame at time 11\n8. Move to time 9 and insert frame\n\n7 seems to be the key. Additionally, it's impossible to add a new frame at time 11. The issue persists after closing and re-opening. \n The issue disappears when cycle-aware keying is off, but comes back if I turn it back on.\n\nI didn't try a daily build, but I searched issues to see if anything similar was reported and found nothing.\n\n", "Modifying keymap won't tag prefs dirty\nWindows 7 Professional 64-bit service pack 1\nIntel Core i7-2600\n8GB RAM\nNVIDIA GTX 1060 6GB\n\nBroken: blender-2.80.0-git.aa003c73245f-windows64\n\n\"Save Preferences\" button, shown when \"Auto-Save Preferences\" is turned off, stays unavailable after modifying keymap.\n\n1. Make sure \"Auto-Save Preference\" is turned off. If it isn't, turn off this and press \"Save Preferences\" button.\n2. Modify keymap, editing the settings used to activate an operator (example: search for `Clear Rotation` operator, changing the `Clear Delta` option will not tag prefs dirty).", "Proportional Editing O key shortcuts bug/deceptive?\nOperating system and graphics card\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nI am using Blender GIT Rev b6df448 on a Fedora 20 Linux 64Bit Box with an Intel 3000HD gfx\ndebug build.\n\nI noticed that when in Edit Mode with a Mesh Object selected pressing the [o Key] while over\nthe 3D Viewport only enables or disabled Proportional Editing Mode. It never cycles through\nall the other available options (Connected & Project 2d) in the\n[3D View Editor Header > Mesh > Proportional Editing] sub-menu even though it has the shortcuts\nnext to their names. This is different from the Proportional Editing Falloff entries which use\n[SHIFT Key + o Key] they do have all their entries cycled through when using their shortcut (and\nkeyboard shortcuts next to they names).\n\nShould the short cut names against the entries that are not cycled through be removed?\n\n[3D_View_Editor_Header-Mesh-ProportionalEditing-OkeyBug.blend](3D_View_Editor_Header-Mesh-ProportionalEditing-OkeyBug.blend)\n\n[system-info.txt](system-info.txt)", "shift+key with option click\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7262\n\nBroken: version: 2.90.0 Alpha\n\n[problem with a key set to 'CLICK' and with shift=True]\n\nIf I do a shortcut with e.g: km.keymap_items.new('wm.call_panel', 'S', 'CLICK', shift=True)\nI need to press and hold Shift and then press and release S. \nI mean if you do a click on a key without shift or ctrl or alt, the option is respected. but adding a Shift for example the property is not working the same anymore.\napparently in the programing of this click option the presence or not of another key has not been considered.\nthe interest of a click as it is explained in the blender help is when you add another key with the same shortcut but with the option 'CLICK_DRAG'\n\n\n", "Dissolving edge doesn't work as expected\nOperating system: Windows 10\nGraphics card: RTX 2070 SUPER\n\nBroken: 3.2.1\nWorked: not sure\n\n\nDissolving edges doesn't work as expected.\n\n\n\n\n\n[untitled.blend](untitled.blend)", "No (selection) tool in Image editor mask mode (Left-click and drag selection doesn't work)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nLeft-click and drag selection doesn't work in Image editor -> Viewer Node -> Mask mode\n\nCreate a mask in the Image Editor and try to select it with left-click and drag selection\n\n\n" ]

[ "Execution of a predefined shortcut\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\n\nBroken: version: 2.80 (sub 59)\nWorked: 2.79.6\n\n\nExecution of a shortcut predefined to the exact state (90 degrees for example) doesn't finish the operation, change the exact number while moving mouse and wait to mouse click.\n\nRotate object by clicking the shortcut \"transform.rotate\" predefined to the 90 degrees. Belnder 2.79.6 will execute shortcut and finish operation.\n\nThe same task in Blender 2.80 continue to rotate object while you are moving mouse unitl click. Not posible to prepare fast shortcut \"transform.rotate\" as one click = 90 degrees, two clicks = 180 degrees, three clicks = 270 degrees rotation.\n\nThe problem is global in Blender 2.80. For example \"Edge Crease\" shortcut set to \"Factor = 1.0\" will set it to 1.0 but it will continue to change crease based on mouse move until click. All worked good in 2.79\n\n\n\n" ]

[ "Geometry Nodes modifier input: Show More descriptive names in the dopesheet\nRight now animated geometry nodes modifier properties get an infamous label such as \"Input_2\". It should instead show the name that is shown in the UI, just like the other (non-geometry nodes) modifier properties.\n\n{[F13048799](image.png), size=full}\n\n[modifier.blend](modifier.blend)\n\nA proposed solution by @HooglyBoogly + @JulianEisel is to introduce \"labels\" to the UI data of ID Custom Properties.\n\n*This doesn't touch the Python API.*", "Mulitres: Grab brush + 'Grab Active Vertex' option seems not intuitive or broken 3.2\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0\nWorked: (In 3.1 sort of?)\n\nI am not sure if its a bug but here we go:\nWhen you add a mulitres modifier to an object and try to sculpt on it with the grab brush it works.\nIf you enable Grab active vertex in the Brush settings it looks broken to me. Even in 3.1 the vertex are displaced from the original and impossible to grab. \n\n1. Start blender\n2. Add a sphere\n3. Add a multires on lvl 1 or 2\n4. Using the grab brush in sculpt mode works until you enable the grab active vertex option.\n\nThe blend file has the setup just try in sculpt mode the grab brush and the options.\n\n\nOn a side note the bug report said win 10 but i run win 11. It seems not to recognized my system.[GrabActiveVertexBUG.blend](GrabActiveVertexBUG.blend)", "Mesh Optimization Project Progress\n### Committed\n\n- 2b640622ff\n- aa6f0f3d1f\n- deb71cef38\n- 5f749a03ca\n- 44d2479dc3\n- c2fa36999f\n- 496045fc30\n- e4c6da29b2\n- d8b8b4d7e2\n- bcefce33f2\n- 8a1860bd9a\n- 6bef255904\n- 174ed69c1b\n- b3f0dc2907\n- 513f566b40\n- 2d60c496a2\n- 27da305a40\n- 51568030e9\n- b5542c1ea4\n- 2d4ec90497\n- 4f9ef65dac\n- 04313f1bb5\n- 0f201049b4\n- f9c9e000ca\n- 1b4d5c7a35\n- 25c2875e0f (depending on 8839b4c32a)\n- 178086d581\n- 4ba06ad0a8\n- 39b2a7bb7e\n- 399b6ec76c\n\n### Differentials\n\n*Remove once committed.*\n\n- [D11294: DrawManager: Use threading for ibo.fdots_nor/hq](D11294)\n- [D11969: Depsgraph: Implement 'ID_RECALC_GEOMETRY_DEFORM' - Second solution](D11969)\n", "UV Editor Snap Active to Vertex is Not Working\nOperating system: Linux-5.19.0-38-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.0\n\nI can not snap active to vertex, no matter what I try it acts like it is in median mode.\n\n\n\n\nIn the startup file snapping is enabled. In the uv editor try to move the selected vertex to snap to another vertex. Or try to snap a face instead, same issue. Sync mode on/off doesn't change the behavior.\n\n", "Incorrect combined texture baking with subsurface material\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nBaking result is different from what I have seen in render and has strange artifacts.\n\n\nOpen attached file and run combined baking with default settings.\n[test_bake_2_79.blend](test_bake_2_79.blend)", "Advancing Displace and Solidify modifiers to handle overlaps\nI briefly discussed this with C. Barton. I often I solidify and displace surfaces in the processes I work on -- recently for 3d printing custom assistance devices including molds for casting rubber, customized computer peripherals, etc. Whether or not they use clear-cut geometric forms, or are of organic nature, they often succumb to the issue of intersections with displace/solidify. I've wanted to work out some details on processes which would enhance these modifiers, but need some help. I'd attempt to implement it so it would be inactive normally, and use thresholds when enabled, so as not to slow down the normal modifier functionality, and a require a minimum processing when the features are used.\n\nThe main issue I'm having is that the modifiers do not presently have access to information on adjacent vertices, and my first approach to an algorithm would examine, with some function fn(vertex_normal, displacement_amount), if there would be a crossing (e.g. if faces would intersect). Then the simplest method would angle the normals away from each other. However, this does all require the ability to examine adjacency, and I'm relatively inexperienced in blender internals, having only contributed minor bits to sculpting tools and physics code. Your guidance would be appreciated.\n\n", "Blender crashes when I try to subdivide my model\nOperating system: Windows 11 Pro 64-bit, 12th Gen Intel(R) Core(TM) i9-12900KF (24 CPUs), ~3.2GHz\nGraphics card: NIVIDIA GeForce RTX 3070 Ti\n\nBroken: 3.6, latest version\n\n\n\n- Open Blender, Open File\n- Go to Preferences, Turns off GPU Subdivision\n- Change to CUDA and tick Graphics Card Box\n- Goes to Modifier, Click Subdivision Surface, Processing, Crashes\n\nTo give a bit more context, my current model only has 160000 vertices which I think is quite little? But still it cannot subdivide and crashes whenever I click the subdivide option in modifiers.\n\n", "Pinning Bones/Constraint Tabs in Properties Editor doesn't work\nBroken: 2.76 - master (1283c66)\nWorked: Unknown\n\nThe context pinning functionality in the Properties Editor doesn't work for Bones and Constraints. There may be a few others too that I haven't noticed yet, but these are the biggest ones.\n", "Stitch tool only works on separate islands\nHello,\n\nIn my opinion the biggest issue with UVs in blender right now is the stitch tool.\n\nIn its current state you are unable to stitch edges that belong to the same UV island. It will only function if you are stitching two different UV islands together. \n\nThe only way to sew edges together that belong to the same island is to either change your seams and unfold the UV island again or manually go through each UV point and merge them one by one.\n\nI propose that we have full control over the stitch tool and remove this limitation. If the selected edges have the capability to be stitched, the tool should function as expected regardless if the selected edges belong to the same UV island or not.\n\nThanks to the Devs for all your efforts.\n\n", "Drivers of sub-ID properties do not get removed along with the sub-ID\nBy \"Sub-ID\" I mean things like Modifiers, Constraints (bone & object), custom properties, shape keys, bones, VSE strips, etc. Not sure how to get a complete list of these types of things.\n\nWhen one of these things, such as a modifier, is removed, drivers on its driven properties are not removed. This makes it easy to leave behind broken drivers that now target nothing. These can be cleared up in the Driver Editor UI fairly easily, but the fact that we must do so is annoying. Experienced users end up learning that you can't just remove a modifier or constraint without removing its drivers first - Just to save you a trip to the Driver Editor.\n\nForgetfulness in this habit results in console warnings, which in a production environment trickle down from assets to shot files, and contribute to the users' sense of \"console warnings aren't important, I will ignore them\".\n\nI always thought this was a known issue but @Sergey told me it's fixable and that I should make a report. Here ya go! \n\nThis would be a really, really welcome improvement for the studio and probably the whole world.\n\n", "Transfer data - vertex position by sampling UV\nAs we discussed on blender.chat, Blender would benefit from being able to transfer vertex positions from one object to another by sampling the UV's. Both the operator and the modifier\n\nHere is a mockup that might clarify what I mean\n\n\n\n", "Paint Mode: Color Fill Tools\nNOTE: This design is still under discussion and is incomplete.\n\n# Issue\n\nCurrently there are different implementations of filling a solid color while in a mode:\n- Fill Tool (Texture Painting)\n- Fill operator (Vertex Paint Mode)\n- Color Filter (Sculpt Mode)\n\nThis needs to be reworked for consistency and to ensure more convenient and efficient workflows.\n\n# Requirements\n\nThere are certain broader features that will be required, no matter how the design of color filling looks like:\n- Fill everything that is not masked\n- Gradual Fill (Not full strength)\n- Fill via gestures (Box, Lasso, Line, Polyline)\n- Fill entire UV-islands, mesh-islands, face sets\n- Fill faces instead of pixels\n\nThere is also the common use of gradients and expand. This should be further notes down in #99770.\n\n# Goal\n\n### Key Problem\n\nThere are many different ways to give all of these tools to the user.\nWhat we should avoid is to have a large set of tools or tool settings scattered throughout the UI.\nThis is already an observable problem with the existing gesture and filter tools in sculpt mode:\n- None of the tools have shortcuts\n- Picking the tool, tool-type and adjusting the settings is time consuming\n- Each tool has their own disconnected settings\n\n### Conclusion\nWe should aim for a more systematic approach.\nAll of the requirements need to be easy to understand and access.\nThat is easier to accomplish if there are fewer tools that are not specifically just for a single purpose.\n\n# Proposal\n\nInstead of adding a lot of new tools/brushes and settings for filling in colors, we can rely on the current and planned masking features.\n\n### Mask -> Fill\n\nFilling should be as instant as possible. But first you need to define what to fill.\nBlender often has a strong design of \"Selecting -> Operation\". By strengthening the masking features via #97955 we could rely on this for color filling operations too.\n\n### Fill Operator\n\nThe most important part as a baseline is a simple operator that immediately fills in everything that is unmasked.\nCurrently this is implemented in Vertex Paint Mode with the shortcut `Shift + K`.\nThis could get a more convenient shortcut on the left of the keyboard.\n\nIt needs to be always clear what color will be used for the operator.\nThe easiest answer would be the primary color of the currently used tool/brush.\nIf the current brush/tool doesn’t have a primary color, then the primary color of the scene color should be used.\nIn that case it becomes very important that this color is somehow exposed. Otherwise there will be too much unnecessary switching between masking and painting tools.\n\n### Auto-Masking\n\nThis way of targeting specific areas is useful for any brush or tool. It already proved itself essential in Sculpt Mode.\nThe aim should be to use auto-masking for the fill operator as well.\n\nIt will be vital to add auto-masking support to the image editor for painting. Topology auto-masking in this case could mask UV islands instead.\n\nOpen question:\n- Is a “UV-island” auto-masking in the 3D Viewport needed or is it more convenient to initialise face sets from UV seams?\nThis could save us space in the auto-masking pie menu.\n\n### Masking Modes\n\nWe also need to allow filling by faces instead of pixels.\n\nWe are already aiming to implement three masking modes in Paint Mode (#97955) and an inverted masking approach (#97903) that could also cover this use case.\nWith this feature it would be as easy as pressing `2` on the keyboard and using any masking tool/operator to mask faces.\nThe fill operator can then fill all unmasked areas, or they can be painted in more detail with any painting tool.\n\n### Gradual Filling\n\nFor this the Color Filter, fill type should still be used. \nBut the fill operator could also get a strength input in the adjust last operation panel.\n", "Enhance ways of accessing active modifier for poll functions of operators\nCurrently, poll function of operators can only get the modifier they are supposed to work on from the context. This is often missing (when called from shortcuts e.g., also with drag-n-drop of modifier panels...).\n\nThis is a sever problem for liboverrides, as some modifiers should then be edited (the locally added ones), and others not.\n\nI can see two ways to solve that: \n \n- Add current 'active' modifier to context (not sure how, or even if, this is always possible).\n- Work around the issue by adding some kind of second 'polling' helper function to be used from invoke/exec functions (since when not found in context, those use event to get the modifier to work on, but events are not passed to poll functions).\n", "Regression: Boolean Modifier Distorts UVs\nBroken: Blender 3.2.2 Official\nBroken: 2.93\nWorked: 2.92\n\nBroke with a3f091d7ce\n\n\nBoolean modifier distorts UVs of cutter object. In the attached screenshot and blend file. There are two cutters objects of roughly the same shape, one of them works correctly and the other doesn't.\n\n\n\n[tmp_2.blend](tmp_2.blend)", "\"Cursor Extrude Vertex\" causes source vertex to snap\nOperating system: Tux-Based\nGraphics card: Intel\n\nBroken: 2.93\n\n\nThe [CTRL}+[RMB] extrude operator (`ops.mesh.dupli_extrude_cursor()`) causes the source vertex to be snapped, in addition to the newly created vertex:\n\n\n\n(GIF.)\n\nSelect a vertex, and do [CTRL}+[RMB] in a situation where there is a valid snap position for it. (I used Surface snap with a surface behind it.)\n\nTest File:\n[#89647.blend](T89647.blend)" ]

[ "Edge Loop Slide Correct UV random vertex Pin on the UV\n{[F251892](276slidebug.jpg)}System:\nWindows 8.1 on two computers, graphics cards: nvidia gt210 and nvidia gt660\n\nSearched everywhere for a similar bug, but didn't find anyone that refers to `UV vertex pinning` due to Correct UV's option.\n\nBlender:\n`Broken:` 2.76 x64 48f7dd6 (installed)\n`Broken:` 2.75 x64 (zip)\n**Worked**: 2.73 x64 (zip)\n\nDescription:\nSliding an edge loop and after that activating Correct UVs will randomly cause some of the selected loop's UV vertex to be pinned in the UV Image Editor (as if you had selected them and pressed 'P').\n\n`To reproduce ` (most of the times):\n- open blender\n- create a cube\n- mark seams and open the cube's UV map\n- Ctrl+'R' to create an edge loop on the cube, right click to confirm and cancel the auto slide\n- With the loop still selected, Double 'G' to slide the loop, left click to confirm the slide where it is (I managed to reproduce both moving and not moving the edge)\n- With the loop still selected, Click on Correct UV's\n- On the UV Image Editor, some random vertices of the selected loop will be pinned\n- Sometimes if no vertices were pinned after that, using edge slide a second time will make all the loop vertices be then pinned.\n\nIs this a feature (an inconsistent one) that I'm unaware of, or is it indeed a bug?\n\n" ]

[ "Remesh + symmetry model bug? : Blender 3.0.0\nOperating system: Windows 10 Home N\nGraphics card: GTX 1660 ti\n\nBroken: Blender 3.0.0 - Stable December 21, 02:21:47 - f1cca3055776 - zip - 234.03MB x64\n- also 3.0.0 from front page have same bug\n\nafter remesh, symmetry broken symmetry_bug_fix.jpg\n(contains ways i fixing the error currently like merge by distance)\n\n1.Remesh model, 2.symmetrise it (weird line appears) \n\n[blender_3.0_remesh.symmetry_wierd_line.blend](blender_3.0_remesh.symmetry_wierd_line.blend)", "unwanted uv-gap created by bevel modifier\nOperating system and graphics card\nwindows 7\nNVIDIA GeForce GTX 660\n\nBroken: 3d243eb\nWorked: same error on offical release 2.78\n\nbevel modifier (bevel by weight) creates an unwanted UV-gap at a vertex with 5 edges connected. 2 edges has bevel weight. Error visible if bevel modifier is applied of if subdiv modifier is active. The UV-gap disappears if 4 out of 5 edges has a 90 degree angle to one another.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nHard to explain how to model. Easiest for you is to open the .blend and test it. I put a shape key on the \"error mesh\". Turn the shapekey on/off to show the error.[bevel modifier error.blend](bevel_modifier_error.blend)", "The Tool Selector Window close one time every two times, when opened too closed to the bottom border of the screen\nOperating system: Windows 10\nGraphics card: GTX 1080\n\nBroken: 2.80\nWorked: (optional)\n\nThe Tool Window, open and close immediately, choosing the tool under the mouse cursor, if the tool window is opened too close from the bottom of the screen.\n\n1) In Edit > Preferences > Keymap, set the \"Space Bar action\" to \"Tools\"\n2) On the 3D viewport, place your mouse cursor in the top area of the viewport\n3) press the spacebar, the tool menu open without any problem, and you can choose a tool with a shortcut key (for example press B to choose the Box selection)\n4) You can repeat that several times in a row without any problems.\n5) Now move your mouse cursor much more closer to the bottom border of the screen, so that you know that the tool window will have to be shifted upward to be displayed correctly.\n6) Press the spacebar a first time. This is ok, you can select your tool\n7) Now press the spacebar a second time. This time, the tool window open and intermediately closed, and the tool selected is the one that is under your mouse cursor.\n8) Press the spacebar again: the tool window open normally\n9) Press the spacebar again: the bug reappear\n10) Now on, every one time over two, the bug appear.\n\n**Expected behavior**\nThe Tool Window should open and stay opened consistently, no matter where the mouse cursor is placed on the screen, when the spacebar is pressed.", "Workbench/Solid : Texture interpolation not displaying properly in viewport (shared across all users of an image)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.0\nWorked: --\n\nLow resolution textures are no longer being correctly displayed as a sharp graphic in the viewport when the texture interpolation is set to \"closest\" in the material shader.\n\nfeature works as intended in rendered view so long as Eevee or Cycles is selected. Workbench does not work as intended in rendered view.\n\nplace object into scene. Locate a low resolution asset such as pixel art and map the texture to the object. \n\ntextures have always appeared blurry at first in the viewport but common pixel art practice is to set the interpolation from \"linear\"(or whichever is set to default) to \"closest\"\n\nWe have 4 materials each having individual Image Texture nodes (but all using the same image).\n\nIf you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.\n\n", "Zoom to mousepos makes 2D Views pan after zoom limits are reached\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\n\nOnce the zoom limit is reached, the view starts to pan rather than stop.\n\nIt was reported #43554 and fixed for `zoomstep` in 6b107daf23c5 earlier, but not for `zoomdrag`.\nThe same fix can be applied to `zoomdrag` as well.\n\n- Enable \"Zoom to Mouse Position\" preference\n- In Node Editor, zoom with Ctrl + MMB-drag, or Ctrl + trackpad-pan\n- When the zoom limit is reached, the view will start panning\n\n", "Box select fails to select bones at certain zoom levels\nOperating system: Linux-5.19.0-43-generic-x86_64-with-glibc2.36 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 4.0.0 Alpha\nAlso 3.5 and 3.6\n\nBox select fails when zoomed out\n\n\n- Open [Select.blend](attachment)\n- Box select some of the bones in the provided file.\n- It doesn't work for me unless you zoom in first\n- If you display the bone as \"Wire\" or \"BBone\" then everything is selecting correctly, otherwise not.\n\nIt fails in both pose and edit modes, perspective or orthographic.\n\n", "Unable to zoom/scale graph editor with [ALT] middle mouse button after frame selected of lowest point\nOperating system: Linux-5.4.0-107-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.2.0 Alpha\nWorked: Likely never\n\nGraph editor goes into locked cycle when frame selecting certain points\n\n[Bug.blend](Bug.blend)\nOn attached file. Box select lowest point of y location on frame 25. Hit Num Pad . to frame the selected point\nAttempt to scale or move graph up and down with [Alt} middle mouse button\n\n", "Graph Editor Expand/Collapse Channels collapsing issue\nOperating system: Linux-5.8.4-200.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: never\n\nOnce Collapse/Expand Channels operator has been used with the All option turned OFF, then the All is turned ON again for Collapse, a following Expand Channels operation will not work anymore\n\n[#80753.blend](T80753.blend)\n- Open above .blend\n- `Collapse Channels`, in the `Redo Last Operation` panel turn OFF `All`\n- `Expand Channels`, in the `Redo Last Operation` panel turn OFF `All`\n- `Collapse Channels` again, in the `Redo Last Operation` panel turn ON `All` again\n- `Expand Channels` will not expand to selected channel anymore\n[T80753_bug.webm](T80753_bug.webm)\n\n", "Assertion Failure: Moving Keyframe in Graph Editor beyond enum range\nOperating system: Linux Mint Mate 19\nGraphics card: Nvidia GTX 850M\n\nBroken: master 2020-11-12 @ Merge branch 'blender-v2.91-release' only on debug builds 987732181f779ca792de933aa5f001168b1f6f26\nWorked: Anything that is not a debug build will not show any problems\n\nThis issue is split off from #44219 (Pose Breakdowner bug in Gooseberry rigs)\nMoving a keyframe of an enum in the graph editor allows it to go beyond the range of the enum. This causes an assert to fail\n\n\n\n* Open the file\n* Move the keyframe up\n* Blender crashed as soon as you exceed the enum range\n[enum_property_crash.blend](enum_property_crash.blend)", "Inconsistent tool selection and tool settings for different layouts\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Alpha\nBroken 2,83,9\n\nAs title said. Inside one layout all viewports have same settings and tool selection.\nExpected: global tool selection for SAME mode and editor. Different tool selection for different editors: 2D paint and 3d paint uses same brush inside one layout (and it is pain because zoom is different)\n\n[2021-02-09_04-19-36.mp4](2021-02-09_04-19-36.mp4)\n", "Camera to View and zoom do not work with orthographic cameras\nIf you switch to ortographic camera (point 1), and try to zoom in with the camera viewport active, the camera behaves as \"view lock>camera to view\" unchecked.\nThe correct behavior is that you can get near the object without changing the camera \"unlock view > camera view\" (point 3). Even though it's checked, it's not working as intended (check point 2 in the picture)\n\n\n- Open attached .blend file\n- Try zoom in, dolly in...\n[ortho_bug.blend](ortho_bug.blend)\n\n", "Bevel modifier - Clamp Overlap broken\nWindows 10\n\nBroken: 2.79.0-git.43a6cf1-windows64\nWorked: 2.79 RC2\n\n\n\nSee attached blend file.[clamp.blend](clamp.blend)", "Annotations (D) do not work with 3d cursor tool (keymap issue)\nMacBook Pro (Retina, 15-inch, Mid 2015)\n2.5 GHz Intel Core i7\n16 GB 1600 MHz DDR3\nAMD Radeon R9 M370X 2048 MB\nIntel Iris Pro 1536 MB\n\nBlender 2.80 Alpha 2\nHash: c94f806dc73\n\ndate: 2018-11-14 22:51\n\nAnnotation tool does not work when pressing D and LEFT MOUSE BUTTON.\n\nAnnotation tool will work when searching with CMD+F; but also within the search, if you click ENTER the annotation tool will pop up for a split second and disappear. \n\nAttaching a short video.\n[Annotation Bug.mov](Annotation_Bug.mov)\n", "Regression: Bevel issue when its percent/absolute mode is operated on edge loop along sharp angle\nBroken: 2.91~4.0\nWorked: 2.90.2\n\nCaused by 48c484a22e0d105ed21a4f18b0cb455af6aac661\n\nIf bevel's percent and absolute modes are operated on an edge loop along sharp angle, the sharp angle part does not get beveled.\n\nTest file: [bevel_sharp.blend](https://projects.blender.orgattachment) ~~[bevel_issue_2.blend](attachment)~~\n\n### Test mesh\nEdge loop at the center has bevel weight of 1.0 and runs along a sharp angle.\n\n\n\nI'm using bevel modifier here for convenience but this also happens with edit mode bevel operator.\n\n| | 2.83.20 | 2.93.16 | 4.0 alpha 2023-06-26 `82d9eb09dbbe` |\n|--|--|--|--|\n| Percent mode |  |  |  |\n| Absolute mode | - | - |  |\n\nEdit: Reproduce:\n\n- Open the updated [bevel_sharp.blend](https://projects.blender.orgattachment)\n- Bevel\n- Select to Absolute/Percent mode and adjust depth\n- observe two cubes behaves differently \n", "With ThinkPad keyboards Zoom does not work with the trackpoint and middle button\nOperating system: Linux ubuntu 22.04\nGraphics card: Intel HD4600 + NVidia GT730M\n\nBroken: 3.4.1\nWorked: Works correctly until Blender version 3.3.1\n\n\nIn previous versions of blender moving the trackpoint and pressing the center button of the trackpack on thinkpad keyboards blender zooms in and out. In version 3.4.1 it no longer does. In 3.4.1 rotates the wiev. Does not work with or without 3er button emulation. In previus versions it works correctly, does zoom in and out. \n\nBased on the default startup or an attached .blend file (as simple as possible).\nStart blender move the track point while cicking the middle button on the trackpad.\nUntil blender 3.5 it does zoom, in 3.4.1 rotates the view. (I think in some alpha 3.4 it works but not in 3.4.1)" ]

[ "Knife tool - 3 issues\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.17\n\n\nBroken: version: 2.80 (sub 71)\nWorked: (optional)\n\n\nKnife tool often creates double geometry in cut areas. Sometimes doesn't even finish the cut properly. When you zoom in during cutting and move cursor out of the model it moves the cut point to 0,0,0 location. \n\nI think everything is in the video.\nwatch?v=9U86POc_zxA\n[KnifeIssues.flv](KnifeIssues.flv)\n\n", "Knife tool makes unpredictable cuts in N-gon meshes\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen using Knife (k) on N-gon mesh, sometimes (in some particular places) right after first mouse click on edge or near edge, appears long cut from some other side of the mesh. \n\nOpen blend file, go to Edit mesh, activate Knife tool (k) and make first click in the circle or somewhere hear it near the outer edge of the mesh. Clicking on some outer edges can make this happen too, though it is some harder to catch.[bug.blend](bug.blend)", "knife snap bug\nOperating system: Linux-5.3.0-51-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 15)\nWorked: Never (2.8+)\n\nFor some reason its snapping to the origin of the object if go a few pixels over the edge.\n\n\n\n[knife bug.blend](knife_bug.blend)\nTry cutting using kife (k) from the marked vertex to the edge and move the mouse a little bit over the edge, (chek the gif in the description) \n", "Issue with the knife tool\nOperating system: Windows 10.0.19041\nGraphics card: GTX1650 (probably a mobile version)\n\nversion: 2.83.3, branch: master, commit date: 2020-07-22 06:01, hash: 353e5bd7493e, type: Release\nWorked: Can't say\n\nError part A)\nI'm modeling a plane and use the knife tool to make specific quads. But there seems to be an issue with the knife tool once you get very zoomed in : instead of behaving normally, helping you sticking a cut from an edge to the other, it systematically passes through the origin point / center of mass of your plane. \n\nIt seems to only happen with the mirror modifier\n\nMy point in [image ](xXmDhrJ).\n\nAnd it only happens when im [this ](xXmDhrJ) zoomed in.\n\n\nError part B) There's also an issue with the snapping of the knife in general with the mirror modifier. It fail to anchor cut points and will not cut upon clicking what seems to be a valid cut. Image [here ](1AJ2maM.png).\n\n\nPart B)\n1) Add plane, rotate 90 on x.\n2) Add mirror modifier \n3) Font view, Extrude right side\n4) Knife, try to cut the right square, will fail to clip on edges, no matter the zoom.\n\nPart A)\n5) Extrude the right side some more.\n6) Move the view until the center of mass / origin of the plane isn't visible.\n7) Zoom on an outer edge. \n8) Try to cut to an inner edge, will clip to the origin on mass then proceed to the point B.\n\nVery simple file that reproduces it attached below. [bug_reproduced_knife.blend](bug_reproduced_knife.blend)\n\n", "Knife Tool fail if camera is too close to the object and mouse away from object\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79\n\n\nIf the camera is too close to the object the knife tool fail to follow the direction of the pointer. (in both ortho and perspective)\n\n\nPlease open the attached file and try to cut some edges as I do in the video.\n\nThank you\n\n[knf.avi](knf.avi)\n[knife.blend](knife.blend)\n\n" ]

[ "Add Asset Browser to Animation Workspace?\nShould the Asset Browser, or at least the 3D View Sidebar with the pose library asset view be added to the default *Animation* workspace?", "Use new file-list design in the File Browser\nThis will be a rather complex task.\n\nFor this we'll need some kind of `uiModelView` for the File Browser, to handle filtering, sorting and lazy-cached previews. This may be the same (base?) view we use for the asset view as well.\n\nWe can either add C wrappers for the C++ functions, or compile the File Browser files in C++ (preferred).", "WIP: Blender Extensions Project\n\nThis is a design document proposing the Blender extensions platform.\n\n\nOnline Extensions\n=================\n\nThe online-extensions platform is a separate project,\nhowever it is expected that the Blender integration will be able to use online repositories to\nlist and install extensions.\n\nThis proposal works under the assumption that ``blender.org`` will maintain a list of add-ons,\nwhere the majority of add-ons currently included with Blender will be moved to.\n\nThese add-ons will be maintained by their respective authors, instead of having to maintain them centrally.\n\nCommunities are free to setup their own lists of add-ons although Blender will only enable the\nofficial ``blender.org`` repository by default.\n\nIncluding other repositories will be supported with minimal hassle with the understanding users\nare trusting the judgment of the people who setup such lists.\n\n\nInitial Proposal\n================\n\nRequirements\n------------\n\n- Support for multiple extension repositories (repos).\n\n Studios and individual users should be able to host their own extensions.\n\n- Support both online repos as well as local (file-system) based repositories,\n\n useful for developers, studios as well as running automated tests.\n\n- Support for multiple extension types (add-ons, apps, themes).\n\n- Building and updating extensions must be automated,\n where a change to an extension can be published without tedious web-UI's.\n\n- Support being disabled entirely.\n\n There is no requirement that external extensions must be used.\n It should be possible to opt-out of using extensions.\n\n *As long as automated updates are off by default, there is no need to use extensions unless users explicitly do so.*\n\n\nNon-Goals\n---------\n\n- Support for large multi-gigabyte extensions.\n\n Very large repositories (typically used for assets) are outside the scope of this project.\n\n Extensions may be re-downloading during an update for example.\n\n- Providing rich text and setting ratings etc from within Blender's UI.\n\n- Automatic updates (initially), while this can be supported the initial version will require manual updates.\n\n\nComponents\n----------\n\n- extension-builder\n\n A tool that validates metadata and packages the extension into an archive\n (perhaps an archive and generated metadata).\n\n Also used for generating a repository listing\n (which would be downloaded by the client to show candidates for installation).\n\n- extension-publish (not part of MVP)\n\n Handles uploading the extension, authentication.\n May also do sanity checks - such as versions never decreasing.\n\n- extension-validate\n\n Used by the builder and server to validate packages.\n \n Checks could include:\n \n - Versions always increase and follow ``semver`` spec.\n - Code checks (Python code byte-code compiles for e.g.).\n - Warn on inclusion of `__pycache__`, `*.blend1` files (for e.g.).\n - Warn on inclusion of modified files or files not under version control.\n\n- extension-client\n\n This utility would be responsible for adding/removing extensions,\n listing extensions from a repository.\n\n This is responsible for gracefully handling errors & cleaning up in the event of failure\n (network-error, disk-full ... etc).\n\n- blender-integration\n\n Blender would integrate with by communicating with the extension-client.\n\n This will be a new a new section in the user-preferences.\n\n - List repos (add/remove support).\n - List extensions (add/remove support).\n - Update extensions.\n\n\nDependencies\n------------\n\n- Packages must bundle any 3rd party modules they depend on as WHEEL's.\n- The package manager is responsible for installing the WHEEL's & uninstalling when they are no longer used (most likely the package meta-data includes bundled WHEEL's and their versions).\n- Multiple packages may include the same WHEEL, in this case only one of them will be used (as the same WHEEL at the same version should be compatible).\n- There is no complex dependency handling, in the event two packages use different version of the same WHEEL, there is a conflict - only one of the packages can be installed.\n\nNotes:\n\n- Prefer WHEEL's over PIP, since PIP is it's own package manager, it may compile code or do advanced operations that a Blender package manager can't reasonably manage - failures with PIP are likely to require command line access, OK for Python developers but not regular users.\n- We might consider allowing some minor difference in package versions, as a general rule though - supporting different versions and handling their possible incompatibilities is not a goal.\n- To avoid unnecessary version-mismatches, we may wish to have a rule of thumb for using the versions of packages available at Blender's release date for e.g.\n\n\n\nImplementation\n--------------\n\n- The extension-client will be managed by Blender as an external process.\n\n This avoids common problems integrating non-blocking logic into Blender interfering with Python's internal state\n and allows for (upgrading multiple extensions at once for e.g.).\n It also allows simplifies writing tests, allowing TDD.\n\n- The extension-client has no stored state (all configuration is passed to it on activation).\n\n Again, simplifies running multiple instances at once.\n\n- Local extension directories are to be entirely maintained by the extension manager.\n\n Meaning users should never manually copy files into this path.\n Removal of these files upon updating is not considered a bug.\n\n\nTo Be Decided\n=============\n\n- Details of meta-data formats, expected fields ... etc.\n\n An extension meta-data (likely a separate file)\n should contain enough information to display an entry in the interface\n (name, author(s), description, type, compatibility information).\n\n- Details of extension storage, archive format ... etc.\n\n- Details of compatibility (only compatible with certain Blender versions),\n support for multiple Blender versions at once.\n\n- It should be possible to install an extension from a URL,\n providing that URL references a repo currently in use.\n\n We might support drag & drop URL's into Blender's to install preferences, details TBD.\n\n- Support multiple versions of the same extension (development, stable... etc).\n\n- Handling of extensions which include compiled modules.\n\n- Support for listing extensions directly from GIT repositories.\n\n Note that this is more on the online infrastructure side of things.\n\n GIT repositories could be scanned and have their packages automatically built.\n This could be an experimental option - for users who also run daily builds.\n\n- Name-spacing\n\n - We may want to namespace extensions so each author has a top-level identifier.\n\n - How add-ons handle name spacing needs some investigation, e.g. ``bl_addons.{repo}.{add_on}``.\n\n- Storage\n\n - The local extension should not store configuration as we want to be able to uninstall/reinstall\n without loosing anything of value to the user.\n\n - We may want to support a generic API for extensions to have a storage location for their own persistent data.\n\n\nFurther Work\n============\n\n- Automatic updates (optional).\n\n This requires some investigation, even if updating can be automatic - the thing that's updated may be in-use.\n So user interaction may be required to explicitly disable the add-on, update and enable it.\n\n- Security (see below).\n\n- Installing/upgrading extensions from the command line,\n e.g. ``blender --extensions-upgrade-all``.\n\n\nSecurity\n--------\n\nFrom discussion with Brecht and Francesco,\nwe had some initial discussion around security, this is a summary of what we thought made sense.\n\n- Domain allow-listing\n\n - Blender will maintain a list of accepted domains and provide a Python API to access this list.\n\n - Add-ons are expected to check with this list before accessing online content\n (we may have a way to accept accessing a domain in the UI).\n\n - While we cannot enforce rules around accessing online content (such attempts are easy to by-pass).\n Intentionally bypassing these checks may result in the add-on being explicitly blocked.\n\n Note that we might have some limited enforcement of accepted URL's for common API's (requests for e.g.)\n that a developer would have to intentionally subvert - however this not a core requirement.\n\n- Malicious extension blocking\n\n As part of updating ``blender.org`` extensions, a list of known malicious extensions will be checked,\n where Blender reserves the right to disable an extension that is known to be malicious.\n\n Repositories can maintian their own malicious extension list as well.\n\n The user will be notified of this with a message for why the extension of what was disabled.\n\n Examples of malicious extensions include but are not limited to:\n\n - Extensions that install viruses/malware.\n\n - Extensions that bypass network access mechanisms (phone home without user consent).\n\n- Malicious repo blocking\n\n We may also want to support this.\n\n---\n\nProposed Layout:\n\n```\n ~/.config/blender/3.6/extensions\n /usr/share/blender/3.6/extensions\n\n Example Layout:\n\n ~/.config/blender/3.6/extensions/\n ├── shared-studio-addons.txt (supports multiple OSs)\n ├── fsiddi-local-addons.txt\n ├── localhost/\n │ ├── addons\n │ ├── keymaps\n │ ├── themes\n │ └── assets\n ├── blender.org/\n │ ├── addons/\n │ │ ├── light_utils\n │ │ ├── cycles_powerdrill\n │ │ └── animation_shelf\n │ ├── themes/\n │ │ ├── blue\n │ │ ├── nitro\n │ │ └── flatty-lite\n │ └── assets\n └── blendermarket.com/\n └── addons/\n └── retopo_flow\n```\n\n", "Clearing a CollectionProperty of ID pointers will dereference duplicate IDs below zero\n## Simplified Report\n\n- Execute the first script below in a new scene with a Cube.\n- The first script will add the cube 10 times to the collection property.\n- Save the file and reopen.\n- Execute the second script.\n- The second script will clear the collection.\n- The cube will get dereferenced to a user count below zero. With this assert:\n - `ERROR (bke.lib_id): source/blender/blenkernel/intern/lib_id.c:322 id_us_min: ID user decrement error: OBCube (from '[Main]'): 0 <= 0`\n- Saving the file again and reopening will remove the cube since it has no users. Even though it was linked to the scene.\n\n```lang=python\nimport bpy\n\nclass TestPropertyGroup(bpy.types.PropertyGroup):\n```\n object: bpy.props.PointerProperty(type=bpy.types.Object)\n```\n\nbpy.utils.register_class(TestPropertyGroup)\nbpy.types.ViewLayer.test_list = bpy.props.CollectionProperty(type = TestPropertyGroup)\n\nfor i in range(0):\n```\n item = bpy.context.window.view_layer.test_list.add()\n item.object = bpy.data.objects[\"Cube\"]\n```\n```\n\n```lang=python\nimport bpy\n\nclass TestPropertyGroup(bpy.types.PropertyGroup):\n```\n object: bpy.props.PointerProperty(type=bpy.types.Object)\n```\n\nbpy.utils.register_class(TestPropertyGroup)\nbpy.types.ViewLayer.test_list = bpy.props.CollectionProperty(type = TestPropertyGroup)\n\nbpy.context.view_layer.test_list.clear()\n```\n\n## Original Report\n\n\nOperating system: Linux-5.15.0-46-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.3.0\nWorked: version 3.1.2\n\n`ERROR (bke.lib_id): source/blender/blenkernel/intern/lib_id.c:322 id_us_min: ID user decrement error: OBCube (from '[Main]'): 0 <= 0` occurs when calling `.clear()` on a CollectionProperty attached to a ViewLayer. In the attached example, the CollectionProperty is a PropertyGroup containing a PointerProperty to bpy.types.Object.\n\n\n1. register properties and operators with provided script\n2. run `bpy.ops.view_layer.test_add_objects_operator()` to add selected objects to the view layer property\n3. save and close file\n4. open file and register properties and operators\n5. bpy.context.view_layer.test_attribute_list.clear() to get error\n\nstart with provided 'untitled.blend' to just run steps 4 and 5\n{F13493946}\n", "\"Make Default\" option not registering file explorer Thumbnails on Microsoft Store Blender\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.63\n\nBroken: version: 3.5.1\n\nWhen installing Blender 3.5 from the official Microsoft Store, attempting to \"Make Default\" installation to get Thumbnails to show on file explorer does not work, even after restarting the OS and refreshing file explorer.\n\n\n1. Download Blender 3.5 from the Microsoft Store\n2. Load Blender > Settings > System > \"Make Default\"\n3. Open any .blend with a camera and save it\n3. Open Windows File Explorer > go to the .blend path > Right Click > View > Large Icons\nOR press Ctrl + Shift + 1\n4. Click F5 to Refresh directory view\n\n", "Bug in particle system - missing particles representations\nOperating system: Linux-5.4.0-47-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.90.1\nWorked: potentially never, does also not work with 2.80\n\nWhen creating a particle system with `instance objects` and using more than ~15.000 particles, not all particles are represented with the instance object. The more particles the particle system contains, the more instance objects are missing. \nThe following images illustrate the problem.\n\nExample with 120 x 120 = 14.400 particles. All particles are represented with the instance object (in this case a cube) - except for the first particle at the top left corner. This particle is always missing - even for small particle systems. \n\n\n\nFor slightly bigger particle systems (e.g. 150 x 150 = 22500 particles), a few particles at random positions in the particle system do not contain an instance object (see the black dots)\n\n\n\nFor way bigger particle systems (e.g. 200 x 200 = 40000 particles) the last particles (i.e. the particles at the bottom right with the biggest indices are missing)\n\n\n\nThe presence of particles without instance objects also affects other particles when using specific nodes. For example, when using the `index` output of the `Particle Info Node` to compute a texture coordinate for each particle used to compute individual colors for the particles produced strange results.\n\nHere a working example for 120 x 120 particles (as reference)\n\n\n\nAnd here a non-working example for 200 x 200 particles (zoomed on the bottom-right corner)\n\n\n\nSide note: In all the examples, the particles are there, but the instance object representation is missing.\n\n\nExecute the following Python script within Blender's text editor. Or, when using Jacques Lucke's VSCode Plugin: execute the script (again) when Blender is already opened (since it does not work with a restricted context)\n\n[particle_sys.py](particle_sys.py)\n\nBlend file with the an incorrect particle system\n\n[particle_sys.blend](particle_sys.blend)\n", "Asset Browser doesn't show assets when drop-down set to \"All\"\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.6.0 Alpha\nAlso broken in 3.5 stable version!\nWorked: This feature is new as of 3.5 and I'm seeing the behavior in both. \n\nAssets from other files are not visible when asset browser preference is set to \"All\" (when assets are part of catalogs)\n\n- Extract uploaded file\n - Open general blend file\n- Set it as asset library path\n- Open asset browser and set preference to \"All' [notice every asset is visible (i.e. engine parts and sculpted sphere)\n- Now open `open-file.blend`\n- In asset browser, set preference to \"All\" (notice engine assets are missing)\nIf switched to \"user library\" then engine assets are visible\n", "Library Overrides: Making an override (for a linked object in the scene collection) creates a duplicate object\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\nLibrary Overrides: Making an override (for a linked object in the scene collection) creates a duplicate object\n\n- open `main.blend`\n- (there is a linked object in the scene collection)\n- `Object` > `Library Override` > `Make`\n- A separate (overridden) Cube object is created in the scene collection (along with the linked object still there)\n\nNOTE: doing the same from the Outliner (RMB > `Library Override` > `Make` > `Selected`) seems to work as expected\n\nas a comparison:\n- open `main_with collection.blend`\n- (there is a linked object in a collection [not the scene collection])\n- `Object` > `Library Override` > `Make`\n- The overriden Cube object is just there without the linked object Cube being present\n\n", "Collection linking + library override doesn't allow to transform object inside\nBroken: version: 3.6.0\n\n\nLinking this collection and then creating a Library Override on it doesn't allow to move the \"Gear\" object inside such collection.\n\n- Download [Test.blend](attachment)\n- Open Blender and link the collection \"Collection\" from Test.blend\n- In the Outliner right click on the imported collection and do Library Override > Make > Selected and Content\n\n", "Compositor in start up file does not show specific passes\nBroken: version: 3.1.0 Alpha\nWorked: Prior to 7e712b2d6a\n\nWhen loading the startup file, some passes will be missing from the compositor. For example the denoiser.\n\nHere is a video showing off the issue: [F12781327](Missing_Passes_in_Compositor.mp4)\n\nWatch the video above or follow the steps below:\n\n1. Start up Blender and change the render engine to Cycles.\n2. Go to the `Viewlayer Properties` tab and enable Denoising Data.\n3. Change one of the areas to the `Compositor` and tick the `Use Nodes` box.\n4. Take note of the passes that are available on the `Render layer` node.\n5. Select from the top of Blender `File -> Defaults -> Save Startup File`\n6. Close Blender\n7. Open a new instance of Blender 3.1 and notice that the `Render Layer` node is missing some of the inputs that should be there.\n\nHow it looks before you re-open Blender:\n{[F13081662](image.png), size=full}\n\nHow it looks afterwards:\n{[F13081667](image.png), size=full}\n\n\nExample of startup.blend:\n[startup.blend](startup.blend)", "File Browser: Can't Select/Delete Favorites Bookmark When File Path Is Missing\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nCan't select/delete an existing Favorites Bookmark in the Blender File Browser if the path no longer exists on your OS. You have to recreate the path to enable select/delete again.\n\n1. Create a Favorites Bookmark in the Blender File Browser that links to a folder on your OS.\n2. Close the Blender File Browser.\n3. Delete the folder in your OS the Bookmark links to.\n4. Open the Blender File Browser.\n5. The Bookmark is now gray and can't be selected/deleted. (Hovering over the link does show the original path.)\nTo reverse this:\n1. Close the Blender File Browser.\n2. Recreate the original path in your OS the bookmark originally linked to (see 5 above).\n3. Open the Blender File Browser.\n4. The Bookmark can now be selected/deleted.\n\nNOTE: A limited workaround was added some years ago (the 'Cleanup' option that will remove all invalid entries)", "Properly handle file links (as in symlinks)\nWhile it should be fairly straight forward, I didn't fully port the file linking support to the new file-list design yet. Most work should already be done however.", "VSE View menu - missing hotkeys for sidebar and toolbar in Preview mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09\n\nBroken: version: 3.0.0 Alpha\n\n\"Caused\" by 6aef124e7d\n\nThe VSE is missing the default hotkeys to open the sidebar and toolbar in Preview mode. T and N\n\nWhen you add them by yourself, then these hotkeys gets added in the Window section. Which can lead to override conflicts.\n\n\n- Open Blender\n- Switch to VSE\n- Watch the View menu in the upper Preview window\n\n\n\n\n\n\n\n\n", "Outliner selection not working correctly after undoing object deletion\nOperating system: Linux-5.17.15-1-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD VERDE (LLVM 13.0.1, DRM 2.50, 5.17.15-1-MANJARO) AMD 4.5 (Core Profile) Mesa 22.1.2\n\nBroken: 2.91.2, 3.2.0, version: 3.3.0 Alpha\nWorked: prior to b077de086e\n\nAn object that is linked in another collection can usually be removed from just that collection by using unlink, while using delete removes it from both collections. But if you delete the object and undo, unlink does delete the object in both collections. \nRenaming the cube or creating a new object \"breaks\" the cubes apart so they can be selected/unlinked individually again.\n\nIn the default scene,\n- create a new collection\n- in the outliner, ctrl-drag the default cube object to that collection to link it\n- delete the cube\n- undo\n- in the outliner, it is now impossible to select the cube in the new collection separately and using unlink will delete both cubes", "Missing Freestyle Lines\nOperating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon(TM) Vega 10 Graphics (RAVEN, DRM 3.35.0, 5.4.0-91-generic, LLVM 12.0.0) AMD 4.6 (Core Profile) Mesa 21.0.3\n\nBroken: 3.0.0, 3.2.0\nWorked: 2.83\n\nThere are missing Freestyle Lines when Rendering with Cycles. The results are better in eevee but the Problem is not gone. \nI use a similar file to create floorplans at work. \n\n- Open attached file or:\n - Create an orthographic camera,\n - create a huge amount of planes and text objects,\n - enable Freestyle, \n- render via Eevee or Cycles.\n[fs.blend](fs.blend)\n" ]

[ "File browser - Filter Blender IDs \nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Radeon Pro 580 ATI Technologies Inc. 4.5.13521 Core Profile Context 24.20.11016.9001\n\nBroken: version: 2.81 (sub 15)\nWorked: (optional)\n\nWhen linking a blend file and looking for Collections using File/Link... in the browser window that opens:\n\n1. by default collections, images and lights are deselected in the Filter Blender IDs list.\n2. If you turn off Filter Blender IDs you still can't see Collections for the blend file.\n\nSo to see collections you have to have Filter Blender IDs on and then expand the view and then Shift select Collections. \n\nI have assumed this is a bug, didn't see anything related to it in a search. \n\nReset to Factory settings.\nFile, link... \nBrowse to a blend file with collections\nSee the above description. \n\n\n", "Collections folder does not appear in file browser when linking or appending\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\nBroken: version: 2.81 (sub 15)\nWorked: 2.81 (sub 15), branch: master, commit date: 2019-10-11 19:43, hash: 60d02b336e\n\nWhen trying to link a collection, the folder inside the library .blend file that is usually called \"collections,\" is missing. \n\n1. Click **File > Link**\n2. Navigate to library .blend file that contains collections\n3. Select it so that the .blend file's contents are displayed\n4. The \"Collections,\" folder is missing. \n\n", "File browser: Filter Blender IDs default selection always has Collections, Images and Lights unselected\nOperating system: Linux-5.3.0-20-generic-x86_64-with-Ubuntu-19.10-eoan 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.33.0, 5.3.0-20-generic, LLVM 9.0.0) X.Org 4.5 (Core Profile) Mesa 19.2.1\n\nBroken: version: 2.81 (sub 16)\nWorked: -\n\nFilter Blender IDs default selection always has Collections, Images and Lights unselected\n\n\nWith vanilla blender\n - Open File> Link> (File browser will appear) Select a blend file with Collections\n - Notice there's no Collections folder until you explicitly click on the Collections Icon on the Filters menu despite it being selected already.\n```\n {F7865377}\n```\n\nMake file browser appear in full screen rather than a dialog\n - Repeat step 1\n - Notice Collections, Images and Lights unselected on the Filter area Select or Activate Collections to be able to see the Collections folder ( though, selection is not remembered between restarts and therefore you have to repeat the above steps to be able to see the Collections folder.)\n```\n {F7865391}\n```\n\n\n\n\n\n\n", "\"Collections\" and other blender IDs are filtered out on OSX when trying to link or append when the \"Filter Blender IDs\" is disabled\nOSX 10.14.6\n\nBroken on 2.81 onwards up until today's (26/10) version or 2.82 alpha\nWorked: 2.80 (Filter Blender IDs option not present\n\nWith the \"Filter Blender IDs\" option disabled, which is the default state, \"Collections\" and other ID types are filtered out from the Link/Append dialog box. In order to show the collections you need to enable \"Filter Blender IDs\" and switch it on\"\n\nOpen 2.82 alpha on mac, Link or Append, see that \"Filter Blender IDs\" is off, and therefore should show all datatypes contained within the file, open up a blendfile that you know has some collections in it, the collections will not be visible. Enable \"Filter Blender IDs\" and you can see you can enable Collections and see the collections within the blendfile.\n\n\n\n", "Collection Images and Lights disabled by default in Linking / Appending [commit is missing in release branch]\nOperating system: Linux-4.15.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.81 (sub 15)\nWorked: version: 2.81 (sub 15)\n\nCollection Images and Lights disabled by default in Linking file\n\n* Load Factory Settings.\n* File - link: \n\n\n", "Collections cannot be linked (do not appear in file browser)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Radeon (TM) Pro WX 4130 Graphics ATI Technologies Inc. 4.5.13547 Core Profile Context FireGL 25.20.15016.4002\n\nBroken: version: 2.81 (sub 15)\nWorked: version: 2.81, daily build oct15th\n\nWhen opening a blend file using the \"file->link\" option, collections do not appear anymore in the list of resources.\nThis is quite critical as it blocks most use cases for Library Override\n\n- open blender\n- choose file->link\n- select a blend file containing a collection (example file attached)\n- when browsing resources to be linked, collection folder does not appear\n\n\nExample file to link from:\n[libraryExample.blend](libraryExample.blend)\n\n" ]

[ "Blender crashing when rendering with eevee, not with cycles however.\nOperating system: Linux-5.15.82-1-lts-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.42, 5.15.82-1-lts) AMD 4.6 (Core Profile) Mesa 23.0.0-devel (git-e20564cfdb)\n\nBroken: version: 3.3.2\nWorked: None, I've tried 3.3-LTS, 3.4 (both the default version provided through steam and manually selecting 3.4 LTS) and the daily-alpha build (with the daily-alpha build I reset settings all to default as well) All of these versions are the ones provided through Steam.\n\nWhen rendering in eevee some of my meshes completely bug out as if only part of them are rendering (I've looked at my normals and they're all fine) and after that my entire PC crashes, forcing a power cycle. The viewport display, when in rendered mode, looks fine in eevee but after rendering and before my PC crashes the viewport also messes up with my meshes looking bizarre. This issue does not occur in cycles when using CPU or GPU compute and other blender files work fine in eevee / cycles both in the viewport and when rendering. I also tried applying all modifiers despite needing a displacement on my torches to animate them but no luck. My blend file also becomes corrupt sometimes after the crash.\n\nSimply just hitting the render button with my current .blend file when in eevee. Sometimes the render goes through with broken meshes (which then I can close the render window and switch to eevee in my viewport display but my meshes will be all messed up and then my PC will crash, sometimes it crashes before the render output. \n\n\n[Dungeon Course.blend](Dungeon_Course.blend)\n\n[Dungeon Course.blend1](Dungeon_Course.blend1)\n\n[3.4 config.7z](3.4_config.7z)", "crash when changing viewport shading to wireframe mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14760 Core Profile Context 21.2.3 27.20.14535.3005\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-04-23 20:25, hash: 17fca62fff9b, type: Release\nBroken: 2.81\nWorked: 2.80\n\n\nif you have a high poly mesh and try change the shading mode to wireframe. depending on the model it constantly crashes.\n\n\nI noticed this trying to make a retopo of a character. I tried to check what was causing de crash by deleting each object and testing the wireframe. \n\nI deleted everything but the main body mesh, without any uv map, vertex color or any other thing that could make it heavier, and also I tried reseting factory settings.\n\nI would send the file but its 200mb, the main mesh has about 4million vertices.\n\n\nthe crash doesn't happen when changing to eevee or solid view, it only happens when changing to wireframe.\n\nImportant note: if you DON'T move the camera after opening the file before changing to wireframe it doesn't crash even if you go to solid and wireframe back and forth as shown in the video bellow \n[2021-05-01 14-18-16.mp4](2021-05-01_14-18-16.mp4)\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[untitled.blend](untitled.blend)\n- open the file above\n- rotate it about 180degrees\n- activate wireframe", "Viewport Render crashes on macOS 12.3\nOperating system: macOS-12.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.1.0 Beta\n\n\nUpdated MacOS to 12.3 (Beta) and going to Viewport Render will cause a full Mac freeze then crash. A hard reboot is the only resolution.\n\nNot sure if this is caused from the latest version of MacOS (12.3 Beta) or if it's the latest version of Blender (3.1Beta). \nI haven't tried with the latest Blender 3.1 Beta build with Monterey 12.2 Beta as this would require me to wipe the computer and reload all apps and files in the OS downgrade process.\n\nOpen default scene and toggle the Viewport Render button.\n\n", "Paint Mode: Brush Radius VS Brush Size\nThis is a brief task design to explain **why Blender should switch brush radius to brush size** and how this change will benefit artists.\n\nI will start introducing the **issues that texture paint mode have currently by using brush radius:**\n\n**1. Makes impossible to paint single pixels.**\n\n- As minimum brush radius is 1px (integer values), **minimum brush size is 2px**, so it's **impossible** to use current brushes **to paint single pixels as for pixel art** styles.\n\n\n**2. Spectrum of brush size values cut by half.**\n\n- Current brush radius makes it **impossible** for artist **to paint with an odd number brush size**/diameter.\n- This likely **cut the values by half** as artists can't paint with a brush with sizes of 1, 3, 5, 7, 9, 11, and so on...\nThat's a silly limitation for artists when we have an easy solution of moving to brush size/diameter.\n\n\n**3. Contra-intuitive.**\n\n- **Brush size**/diameter **gives artists better feedback on the real size of the brush** over the texture space while they don't have to think in brush radius * 2.\n\n\nBrush size is a standard over brush radius but not because it is driven by big companies but because it is the most intuitive for artists while radius may be more intuitive for mathematicians and programmers, so I think we should invest into improving UX for the end-user, specially in texture paint mode that lacks a lot of it.", "simulation in new scene causes crash in original scene's simulation\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: (optional)\n\n**steps**\n- make cube an active rigid body. \n- play simulation\n- then click on new scene button and on full copy.\n- in the new scene, rewind playhead to frame 0\n- run the simulation.\nBlender should crash.\n\nThere are more ways to cause crash when full scene copy is done (see comments), but I guess these will stem from single issue.", "MacOS crash when opening a second rendered 3dview window --MacOS 13.0.1--\nOperating system: macOS-13.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.48\n\nBroken: version: 3.5.0 Alpha\n\n\nWhen in rendered 3dview and open a second window also in rendered 3d view, blender hangs for 20 sec. and then MacOS becomes unresponsive and finally crashes.\nNo way to 'force quit' or any other trick to stop blender. or the MacOS crash.\nThis happened now 5 times in a row, always when opening a second new window also in rendered 3dview.\n\nOpen blender 3.4 /3.5 in MacOS 13.01 & switch to rendered 3dview. Then after a minute open another rendered 3dview window.\n\n", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "Switching windows does not register as click\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0\n\nI use industry compatible keymaps.\nWhen switching between windows, no matter whether they are 2 Blender windows or Blender and any other, any camera adjustment is not registered and, depending on the keymap preset you use, you either rotate the camera or move the object instead(see attached capture).\n[switchingWindowsBug.mp4](switchingWindowsBug.mp4)\n\n1. Shift LMB Press on the corner where the viewport meets the outliner and drag to the left, this creates a new viewport window\n2. Create a cube and press on the move tool to show it's gizmo\n3. Pan the camera in one window\n4. Then without clicking into the second viewport try to pan the camera in the second viewport, depending on the keymap preset you use you either rotate the camera instead of panning or move the object\n\nBlender does not register when you have switched to the new window without first clicking with the LMB into the window.\nAs you can guess it makes it pretty nifty to switch between windows, either 2 Blender viewports, Blender and the tutorial you are watching or any window else.", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Texture Painting not updating cycles shader in viewport\nOperating system: Linux-5.8.0-44-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa Intel(R) Xe Graphics (TGL GT2) Intel 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.92.0\n\n\nLevel 1. When texture painting in the 3D viewport, the image is updated, but the visible shader on the object doesn't update in cycles until switching to viewport shading and back to cycles.\nIt still works when switching to Eevee shading. When reloading the image in the shader image texture node, it updates in cycles, but the problem persists when the image is updated (painted on) again.\n\nLevel 2. The above bug becomes worse as follows:\n\nIn cycles the image stops updating even when switching to viewport shading and back to cycles.\n(A)-When reloading the image in the shader image texture node, it updates in cycles, but any new paint on the texture in the viewport or image editor -> paint mode won't update until step A is repeated. \n\nI do not know exactly what triggers this 2nd level bug, but it doesn't take long to show up. \nI was able to repeat it just by painting and switching between Eevee and cycles using my test .blend file (attached)\n\n\n\n\n1. Assign a material with an image node to an unwrapped object\n2. Switch to viewport texture painting and start painting on the image in cycles shading. \n3. The image updates in viewport shading, but not the visible shader on the object in cycles. \n4. Switch to Eevee shading - now eveything works as expected.\n\n5. I do not know what triggers the level 2 bug.\n\n[Cycles not painting on Cube.blend](Cycles_not_painting_on_Cube.blend)\n\n\n\n\n\n", "Intermittent: Shift + MMB unresponsive or very sluggish\nOperating system: MacOS Ventura 13.4.1\nGraphics card: M1\n\nBroken: 3.5.1, Hash: e1ccd9d4a1d3, Branch: blender-v3.5-release\n\nShift+MMB to pan view in perspective mode becomes either completely unresponsive to keyboard input or extremely sluggish compared to the mouse pointer speed for the rest of the application. Agnostic to mouse pointer speed setting for the OS. \n\nAny model in perspective view. Attempt to pan view via SHIFT+MMB.\n\n", "Broken material assigment after changing mesh-linking to object-linking\nWindows 11\nNvidia RTX 2060 super\n\nBroken: blender-3.2.0-stable+daily.e05e1e369187\n\n\nOn objects with multiple material slots, the currently selected slot gets bugged when switching from object-linking to mesh-linking. It allows the user to select a different material for each link type, which seems to trigger the bug and has lingering effects. For example, in geometry-nodes setting the material becomes unpredicatable, with material names seemingly swapped.\n\nFrom the provided blend file or startup scene:\n1. create a new material slot\n2. pick a material for this slot\n3. swap the material link type between object-link and mesh-link\n4. select a different material for the same slot\nThe material or slot is now bugged. Geo nodes 'set material' will become unpredictable.\n\n[bug_slots.blend](bug_slots.blend)", "Greasepencil 3.0: Unable to switch to drawmode from sculptmode\nOperating system: Linux-5.15.0-73-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: 4.0.0 Alpha\n\nEnable GP 3.0\nOpen 2D session\nSwitch from the initial draw mode to sculpt mode via header button.\nTry to switch back to draw mode.\nAn error message appears:\n\n", "Zoom stops at certain level and won't go further\nOperating system: Windows 10\nGraphics card: GeForce GTX 1070\n\nBroken: 2.92, 3.0 alpha\n\nIn this simple model, I cannot zoom my view closer to mesh than I already did. I saved the closest achievable view position in the .blend.\nI can reach further close-ups using some more advanced navigation tools, like dolly zoom, but standard zoom won't let me.\nThe issue is linked to this particular model - if I copy the object (there's only one in the scene) to a new model, the issue is gone.\nThe model was originally saved in Blender 3.0 alpha, only then in stable 2.92. Could it be the cause of this bug?\n\nBased on the default startup or an attached .blend file:\n[zoom issue.blend](zoom_issue.blend)", "Trackpad stops working for a while\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M\n\nBroken: 3.6.2\nWorked: don't know\n\n\nSometimes, Blender stops responding to trackpad gestures such as two-finger scroll or pinch zoom. This is not just in the viewport but everywhere - I can't scroll menus or the node view, for example.\n\nThe UI is otherwise responsive when this happens - I can scroll menus by dragging the slider at the edge, just not with a two-finger scroll.\n\nIf I go and do something else in another app for a few minutes, it usually fixes itself.\n\nThis happens sporadically and I don't have a reliable way to reproduce it, but it seems to happen often after I render an image - after the image has rendered, I try to use pinch-zoom to look more closely and find I can't. I am not sure if it happens in other situations as well - if it does I will update this report.\n\n\nI'm afraid that I can't reproduce this reliably - it just happens every now and then, in any .blend file. I am happy to take any advice on how to look for a way to reproduce it.\n\n" ]

[ "Weight paint mode with close up mesh, auto depth active, \"show whole scene as transparent\" shut down blender 2.8\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\nBroken: version: 2.80 (sub 61), branch: master, commit date: 2019-05-11 18:20, hash: ebc44aae9897,\n\nWith weight paint mode, when active mesh is close up in 3d view, (large enough ), if use \"show whole scene as transparent\" shut down blender \n\n1. clear scene. load default cube and select cube.\n2. close up view, with mouse scroll, untill cube border edge is hidden by 3d view border.\n3. chage mode to weight paint.\n(or just load attached cube scene)\n[testweight.blend](testweight.blend)\n\n4 . from 3d view top menu>toggle \"whole scene transparent\"\n5. it shut down blender. if not, scroll more to close up with perspective view, then toggle \"whole scene transparent\"\n\nThere seems some conditions to avoid this issue, eg not close up , etc, but when close up with weight paint mode,\nand toggle \" whole scene transparent\" usually cause shut down. sometimes it happen immediately. \n\nBlender crash.txt (with debug build)\n# Blender 2.80 (sub 61), Commit date: 2019-05-11 18:20, Hash ebc44aae9897\nbpy.data.screens[\"Layout\"].shading.show_xray = True # Property\nbpy.ops.paint.weight_paint_toggle() # Operator\n\n# backtrace\n27: BLI_system_backtrace - 0x229D2210\n26: sig_handle_crash_backtrace - 0x225D9110\n25: sig_handle_crash - 0x225D9160\n24: windows_exception_handler - 0x225D93D0\n23: UnhandledExceptionFilter - 0xD241BC40\n22: memset - 0xD5A31580\n21: _C_specific_handler - 0xD5A1B550\n20: _chkstk - 0xD5A2F6C0\n19: RtlWalkFrameChain - 0xD599C460\n18: KiUserExceptionDispatcher - 0xD5A2E6E0\n17: workbench_taa_view_updated - 0x239D7150\n16: workbench_solid_view_update - 0x239927E0\n15: DRW_notify_view_update - 0x238DA130\n14: ED_render_scene_update - 0x25BC1E40\n13: DEG::deg_editors_scene_update - 0x22B291D0\n12: DEG_ids_check_recalc - 0x22B0A010\n11: BKE_scene_graph_update_tagged - 0x22665520\n10: wm_event_do_depsgraph - 0x2309E390\n9: wm_event_do_refresh_wm_and_depsgraph - 0x2309E5A0\n8: wm_event_do_notifiers - 0x2309E690\n7: WM_main - 0x230805D0\n6: main - 0x225D1D70\n5: invoke_main - 0x263C2670\n4: __scrt_common_main_seh - 0x263C2420\n3: __scrt_common_main - 0x263C2400\n2: mainCRTStartup - 0x263C2730\n1: BaseThreadInitThunk - 0xD31C4020\n0: RtlUserThreadStart - 0xD5A03670\n\nconsole\nSettings loaded\n18: BLI_system_backtrace - 0x229D2210\n17: GPU_viewport_engine_data_create - 0x26077310\n16: drw_viewport_engine_data_ensure - 0x238E0690\n15: DRW_notify_view_update - 0x238DA130\n14: ED_render_scene_update - 0x25BC1E40\n13: DEG::deg_editors_scene_update - 0x22B291D0\n12: DEG_ids_check_recalc - 0x22B0A010\n11: BKE_scene_graph_update_tagged - 0x22665520\n10: wm_event_do_depsgraph - 0x2309E390\n9: wm_event_do_refresh_wm_and_depsgraph - 0x2309E5A0\n8: wm_event_do_notifiers - 0x2309E690\n7: WM_main - 0x230805D0\n6: main - 0x225D1D70\n5: invoke_main - 0x263C2670\n4: __scrt_common_main_seh - 0x263C2420\n3: __scrt_common_main - 0x263C2400\n2: mainCRTStartup - 0x263C2730\n1: BaseThreadInitThunk - 0xD31C4020\n0: RtlUserThreadStart - 0xD5A03670\nBLI_assert failed: c:\\myprograms\\blender-git\\blender\\source\\blender\\gpu\\intern\\gpu_viewport.c:200, GPU_viewport_engine_data_create(), at '!\"Too many draw engines enabled at the same time\"'\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF6239D7173\nModule : C:\\myprograms\\blender-git\\build_windows_Release_x64_vc15_Debug\\bin\\Debug\\blender.exe\nWriting: I:\\myfile\\blender\\Temp\\blender.crash.txt\nPS C:\\myprograms\\blender-git\\build_windows_Release_x64_vc15_Debug\\bin\\Debug>" ]

[ "Cycle crash\n[System Information](https://projects.blender.orgattachment)\n\nBlender version: 3.4.1\n\nCrash when switching from Material Preview to Rendered in Viewport Shading and GPU Compute was set for Cycles. In CPU mode it's OK.\n\n\nOpen project.\nSelect CPU in Cycles settings.\nSwitch from Material preview to Rendered in Viewport shading.\nNow it works.\nChange to GPU Compute in Cycles settings.\nCrash...\n\n", "Rigify crash in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.3.2.230315\n\nBroken: version: 3.5.0\n\nWhen I orbit the view in edit mode, the program crashes after a few seconds. Especially around the hands and face.\nIn version 3.1.2 it does not happen to me, it does happen in 3.3.0 and 3.5.\nTried to clean and reinstall, update drivers, save file in 3.1.2 and open in new versions, but the bug persists.\n\nSorry for bothering you, I hope you have a good day.-\n\n\ncreate human metarig, go to edit mode, orbit the view. Orbiting around hands seems to crash faster.\n\n", "Regression: Repeating resizing image and undoing causes view in image editor strange state, and editing it causes crash.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 3.3.0 Alpha\nBroken: 3.2\nWorked: 3.1\n\nCaused/exposed by e06399c223\n\nIf resizeing image and undoing is repeated, view in image editor becomes strange state.\n(It looks like that the image size is incorrect state).\nIf the image is editted in this state, the blender would crash.\n\n\n\nAt the first undoing, it looks O.K.\nBut if I repeat resizing and undoing one more time, the image becomes strange.\n\n\nFollowings are what I did in the video above.\n1. Open image editor and make a new image. (1024x1024)\n2. Resize the image to 256x256 from menu.\n3. Undo it.\n4. Then, Resize the image to 256x256 one more time.\n5. Undo it.\n6. The image size in the editor becomes strange.\n7. If I edit the image, blender crashes.\n\nI tried above process in several conditions.\nI found that\nA. this does not happens in 3.1. It happens after 3.2\nB. If I checked Undo Legacy option, this does not happen. It happens in standard undo mode.\n", "Bevel Improvements\nBlender users have many desires for improvements to the Bevel tool and Modifier. This task is for exploring priorities for implementing those, as well as designs for doing so.\n\n**Some current TODOs and feature requests**\n\n* generalize to handle several manifold sheets touching at a point (see #34678).\n* improve clamping code (see #38871).\n* more options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n* treat more cases like \"pipe\" to avoid bulges (see #40258)\n* option to have bevel not create n-gons (see bf-funboard thread)\n* sometimes leaves degenerate geometry (#48174)\n* tapered bevel influence by vertex weight - see bevel-modifier-influenced-by-vertex-weight. Also #62739 where method isn't suggested -- could also let user set different widths at the two ends of a bevel.\n* merging of vertices that coincide after beveling (#61214)\n* better way of specifying vertices in modifier, and even better, a way of specifying edges (#62649) (edge group?)\n* bevel-after-booleans\n* option to make vertex group out of all vertices created in bevel\n* method to have bevel modifier affect curve objects\n* have angle limit method available in tool (as is already in modifier)\n* have clamp be local rather than global (or in addition to global?)\n* \"support loop\" option - extra loop of edges flat on adjacent faces\n* use bevel-like code to add new option to extrude (edge, vertex) that keeps geometry manifold (billrey idea in GSoC 2018 thread)\n* vertex mesh that has the effect of booleaning the edge profiles to have the effect of real-world material removal\n* profile superellipse arc should not use quarter-ellipse arc always, but rather rather the segment that hits adjacent faces tangentwise\n* beveling a face as an option in addition to beveling edges and vertices (starts to look like inset)\n* width method like Percent but where absolute distance along adjacent edges is equal to spec instead of percentage\n* option to round the terminal edge triangle\n* special case segments=2, profile=1 case to avoid diagonal edges on cube corners when smaller and large widths mixed\n\n\nFollowing comments will have some initial explorations of the problems and designs for solving each of these.\n\n", "Incorrect twist in bevel/extrusion using curve tangent mode\n\n\n\nOperating system:\nGraphics card:\n\nBroken: present in 2.83.3, 2.91.0, and 3.0.0 alpha\nWorked: ?\n\n\nBoth open and closed curves exhibit a \"sausage effect\" when a bevel is applied. This is not visible when the curve is closed and 'ResolutionU' is below 4. The issue is somehow attenuated by applying large amounts of smoothing (twist_smooth).\nBelow is a flat and symmetric curve showing this issue.\n\n\n[blender_sausage_bug.mp4](blender_sausage_bug.mp4)\n\n\nDelete default cube. Create a Bèzier Circle. Enter Edit Mode, select all vertices, subdivide once.\nIn Object Data Properties, select Shape->Twist Method-> Tangent, and Geometry->Bevel->Depth: 0.2.\nToggle the Active Spline->Cyclic->U, and change the Active Spline->Resolution U between 4-5.\nYour smooth symmetric curve will turn into sausages!\n\nThe effect is slightly different depending on the type of handles.\n[sausage_bug.blend](sausage_bug.blend)", "GN Boolean failure\nOperating system: Linux, Debian (Stable), KDE\nGraphics card: 3090\n\nBroken: 4.0.0 Alpha, branch: main (modified), commit date: 2023-06-29 23:21, hash: f47eed749eaf, type: Release\nbuild date: 2023-07-21, 00:45:10\nWorked: Not sure. 3.6 fails too.\n\nBoolean of a collection of meshes and text objects, in GN, with Realize Instances, fails.\nText objects have a text extrude size set. They all have remesh modifier as well (an attempt to get it to work).\n\n1. Load attached blend.\n2. Examine and see the text objects are not successfully boolean-differenced from the block.\n\n", "snap to face broken with mirror modifier\nOperating system: Linux-4.18.0-25-generic-x86_64-with-debian-buster-sid 64 Bits\n(same behavior on Windows 8.1)\n\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.81 (sub 11)\nAlso broken in 2.80 stable\n\n* open demonstration blend file with no config dir\n* note that snap-to-face (target:closest, affect:move) is already enabled\n* select small cuboidal in lower left\n* G, then X, to move along X, and attempt to snap to broad side of nearby horizontal cuboidal\n* see that the object flashes erratically, alternately assuming its original position, and alternately assuming an incorrectly snapped position\n* if instead the cuboidal we are trying to move is moved a bit first, without snapping, and then we again try to snap to the face, it doesn't flicker any more, but it still snaps incorrectly (and actually still does flicker on the overlapping face but doesn't jump around in position)\n* if the mirror modifier on the cuboidal we are trying to move is disabled, it snaps correctly\n\nStarting position: \n\nIncorrect snap result: \n\nCorrectly snapped result: \n\nDemo blend file: [snapbug.blend](snapbug.blend)", "Blender crashes after rendering a few frames of an animation\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nI've never had this kind of problem - Blender crashes randomly after rendering a few frames of the animation. The only \"new\" thing I'm doing is I started using geometry nodes in this scene. I have plenty of VRAM left, shouldn't be a GPU issue. Tried both in 3.4 and 3.5\n\n\n", "Bevel profile incorrect when using arc for inner miter\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.3.0 Alpha\n\nThe Bevel operation and modifier has an incorrect profile when the inner miter is set to arc and the profile value is either very high or low.\nthis happens in both edge bevel and vertex bevel mode.\n\n|Inner miter sharp (Ok):\n|---\n|\n\n|Inner miter arc:| \n|---|---\n||\n|Shape 0.93|Shape 0.5\nIn this case the Bevel kind of overshoots.\n\nProbably related to #95916 (Pinching effect when using bevel and bevel modifier).\n\n- Open attached .blend file\n[Test.blend](Test.blend)\n\nThank you and have a great day!\n\n---\nUPDATE:\nIn some cases it can also happen with Inner Miter Sharp (#105064)\n", "Mesh Optimization Project Progress\n### Committed\n\n- 2b640622ff\n- aa6f0f3d1f\n- deb71cef38\n- 5f749a03ca\n- 44d2479dc3\n- c2fa36999f\n- 496045fc30\n- e4c6da29b2\n- d8b8b4d7e2\n- bcefce33f2\n- 8a1860bd9a\n- 6bef255904\n- 174ed69c1b\n- b3f0dc2907\n- 513f566b40\n- 2d60c496a2\n- 27da305a40\n- 51568030e9\n- b5542c1ea4\n- 2d4ec90497\n- 4f9ef65dac\n- 04313f1bb5\n- 0f201049b4\n- f9c9e000ca\n- 1b4d5c7a35\n- 25c2875e0f (depending on 8839b4c32a)\n- 178086d581\n- 4ba06ad0a8\n- 39b2a7bb7e\n- 399b6ec76c\n\n### Differentials\n\n*Remove once committed.*\n\n- [D11294: DrawManager: Use threading for ibo.fdots_nor/hq](D11294)\n- [D11969: Depsgraph: Implement 'ID_RECALC_GEOMETRY_DEFORM' - Second solution](D11969)\n", "Crash when shading\nModel: HP Probook x360 435 G7 (independently upgraded SSD and RAM)\nOperating system: Windows 11 Pro 22H2 22621.1555\nGraphics card: AMD Radeon Graphics (Built-in graphics of AMD Ryzen 5 4500U with Radeon Graphics)\n\nBroken: 3.5.1 and 3.3.1 were tested, both had this issue.\nWorked: 3.1.2 – At the time of issue creation, there are no newer versions that have worked, including the latest build of 3.6.0 Alpha.\n\nBlender freezes for a second or so, and then crashes.\n\nI don't know if it *is* reproducable, but I have tested multiple conditions under which it crashes. These conditions are accompanied with the crash logs of that test. The problem does not seem to be (V)RAM usage, as the usage remains constant from before Blender is opened to long after.\n- Press F12 to Render Image: Crash [Log](itihmb)\n- Select Default Cube, Click on Shading workspace: Crash [Log](nxyeck)\n- Select Default Cube, Go to Materials tab: Crash [Log](ixgrhp)\n- Change Viewport Shading mode to Material Preview: Crash [Log](diwmma)\n- Change Viewport Shading mode to Render Preview: Crash [Log](ztajes)\n- DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: Crash [Log](gcaded)\n- Change Render Engine to Cycles, Press F12 to Render Image: **No** crash\n- Change Render Engine to Cycles, Click on Shading workspace: Crash [Log](chmkgj)\n- Change Render Engine to Cycles, Go to Materials tab: **No** crash\n- Change Render Engine to Cycles, Change Viewport Shading mode to Material Preview: Crash [Log](fhfyfo)\n- Change Render Engine to Cycles, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Cycles, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\n- Change Render Engine to Workbench, Press F12 to Render Image: **No** crash\n- Change Render Engine to Workbench, Click on Shading workspace: **No** crash\n- Change Render Engine to Workbench, Go to Materials tab: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Material Preview: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Workbench, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\nThank you for your help.\n\n", "Extra face dots in UV Layout editor (GPU subdivision OFF, On Cage OFF in Subdivision modifier make a difference)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4835\n\nBroken: version: 3.4.1\nBroken: version: 3.1\nWorked: not since GPU subdivision was introduced (so in a way, it was working in 3.0)\n\nExtra random faces appear in the UV Layout editor\n\n- I can mosty repro this if GPU Subdivision in Preferences > Viewport > Subdivision is OFF\n- It does not happen at all if I turn off `On Cage - Adjust edit cage to modifier result` on the SubSurf modifier.\n\nIn the attached file, toggle from face select mode to vertex select mode and back to face select mode. (Might have to repeat 5-6 times) Extra faces appear in the UV Layout editor. Also see here: [1457172]\n\n", "Quick Smoke crash guide February 3, 2023\nOperating system: macOS-13.2-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 3.5.0 Alpha\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\n[image.png](image.png)\n[image.png](image.png)\n[Blender-2023-02-03-113746.ips](Blender-2023-02-03-113746.ips)\nTest File: [3.5.zip](3.5.zip)\n```\nCall Stack: Main thread\n__psynch_cvwait\n_pthread_cond_wait\ntake_gil\nPyEval_RestoreThread\nPyGILState_Ensure\npy_timer_execute\nBLI_timer_execute\nwm_event_do_notifiers\nWM_main\nmain\nstart```", "Intersect (Boolean) in edit mode produces inconsistent selection\nBroken: 2.92 master\nWorked: N/D\n\n\nThis is how selection looks like after performing a Difference operation in edit mode using an enlarged copy of the same cube:\n\n\n\n4 verts and edges selected, yet 0 faces (should be 1). The operation was performed in vertex mode. If you do it in edge mode, again 4 verts and 4 edges, 0 faces (should be 1). In face mode though - nothing gets selected at all.\n\n\n1. Enter edit mode on the cube.\n2. Duplicate the geometry, move it to the side and scale it slightly.\n3. Invoke a Face -> Intersect (Boolean).", "Texture distortions near a seam WITH some Mean Bevel Weight applied\nOperating system: Windows 10 64-bit\nGraphics card: GTX 1080Ti\n\nBroken: 2.93.3\nWorked: \n\nOn a concave surface, texture distorts near a seam edge with a bit of Mean Bevel Weight applied.\n\n1) Create a curvy concave vessel/cup/pot with thickness. \n2) Add Bevel modifier 0.1m amount, segments 2, Weight method\n3) Make the mouth rim edges to be seams, and apply about 0.10 - 0.25 mean bevel weight\n4) you can do the same on the base outer edge \n5) UV unwrap, create image, better with 2048 and with UV Grid to see effect, apply to mesh\n\nNotice the texture distorts near the outer seam edge of the concave surface (the outer skin of the pot/cup)\nSetting the Mean Bevel Weight back to 0 removes this phenomenon but defeats the bevel purpose.\nI made 3 blender files and all exhibit same \"problem\".\n\n[bugreport2.blend](bugreport2.blend)\n" ]

[ "Regression: Blender crashes after using Inset Faces\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0 Alpha\n\nCaused by 6c774feba2\n\nBlender crashes after using Inset Faces (when a UV map is present)\n\n1 - create poly sphere\n2 - select several polygons\n3 - use Inset Faces (with the settings as in the screenshot)\nSometimes after this operation Blender crashes\n\nin a debug build with ASAN, this will reliably give\n\n`SUMMARY: AddressSanitizer: heap-buffer-overflow /blender/source/blender/bmesh/intern/bmesh_mesh_convert.cc:1030 in BM_mesh_bm_to_me`" ]

[ "Viewport display broken for fire- solid and rendered mode (Cycles & Eevee)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\n[Fire seems to get 'stuck' in the viewport (as in it does not disappear), it does however behave correctly when F12 rendered.\nThis happens in 2.83Alpha and 2.82Beta (both downloaded as of today, approx 16:00 Sydney time 15 Jan 2020)]\n\n[Bake the attached and observe.\nhere's what it looks like-\n[ViewportFire_2-82+2-83.mp4](ViewportFire_2-82_2-83.mp4)\n\nIt works Ok when F12 rendered as seen here-\n[Fire26Nov20190001-0050.mp4](Fire26Nov20190001-0050.mp4)\nI couldn't be bothered to render out the clip in Cycles but stills show the error is only in the viewport-\n\n\nHere's the .blend-\n[Fire2.83A.blend](Fire2.83A.blend)\n\nThis works properly in the 26November2019 build, here's what that looks like-\n{[F8279386](ViewportFireMantaflow_26-11-19Build.mp4)}]\n\n", "Blender has froze my Manajro Linux, which has corrupted my root Btrfs filesystem, rendering the machine unable to boot\nOperating system: Manjaro Linux\nGraphics card: Radeon RX 5500/5500M / Pro 5500M\n\nBroken: Blender 2.90.0, 2.90.1, 2.91.0 Alpha\nWorked: none yet\n\nWhen doing a very specific thing in Shader editor using Eevee rendered, my system froze. I've rebooted and tried again. It froze again, only this time when I rebooted it I was greeted by an emergency shell. My root Btrfs filesystem is unmountable. I'm currently performing disk imaging, and will attempt to fix the FS or restore the system from backup.\n\nHere's the screen that I saw after rebooting my laptop after the second lock-up:\n\n\n\nI have a specific .blend file that when loaded on Manjaro Linux will freeze the system. I've tried again booting a fresh Manjaro 20.1.1. However it's a confidential client project and I cannot share it publicly.\n\nI wasn't able to reproduce the problem on Windows 10 running on the same laptop.\n\nI suspect the problem could be in an AMD GPU driver - it's the only thing that I believe has enough system access to mess up a roo t filesystem that was involved. And it's clear the problem was triggered by a certain material in Blender, while rendering with Eevee.\n\nNote that the system won't freeze until I turn on Rendered view. Using Material Preview is fine.\nTwo first time when it happened it was immediately after I have added a mix node to add another texture to an existing image path in an Eevee material.\nI thought that maybe texture sizes could be the problem, as I've been using 3 8K textures, and maybe the laptop's GPU can't handle that, but filesystem corruption should never be the result of that.", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "Crashing and freezing when working on files with assets\nOperating system: macOS-12.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 580 1.2\n\nBroken: version: 3.5.0\n\nCrashing and freezing when working on files with assets\n\nif I open the demo file cube_diorama.blend the whole system freezes and either crashes or logs out needing to login again.\nevery blender crash a WindowsServer log is created.\n\n cube_diorama.blend never crashed in previous versions of blender for me.\n\n", "simply moving the render window is terribly slow\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13422 Core Profile Context 0\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nwith more complex scenes (such as for example blenderman file 57e5084f0fcf294119c5055c) once you render an image and you have eevee in render preview mode, moving the render window becomes very slow, probably because eevee returns to refreshing the previw render without needing it.\n\nsee the video\n\n[GRAbwindow.mp4](GRAbwindow.mp4)\n", "Objects in front of the selection stay in front in wireframe mode\nBroken: version 2.80+\nWorked: version 2.79\n\nIn blender 2.79, the wireframe of objects selected or in edit-mode was drawn in front of the wireframe of all other objects in the scene.\nIn blender 2.80 onwards, this doesn't happen anymore.\n\nHere's a model shown in 2.79b, with my usual theme:\n\n\nThe object in edit mode is behind the objects seen with gray wireframe. But because it is in edit mode, it is drawn in front of the others.\nThe same is true if the object is in object-mode but selected.\n\nNow compare the same model in 2.8x:\n\n\nHere the same object is seem in edit-mode. Now it is drawn behind everything else, which creates a noisy, low-contrast appearance, making it hard to see and sometimes hard to edit. \nSometimes it forces me to rotate the view to get other things out of the way (especially if the foreground objects have a lot of detail/geometry).\n\nIf you zoom in real close on an area where a foreground object overlaps the selection, snap a screenshot, and then scale or zoom the image, you can see how the foreground object is definitely being drawn in front of the active one:\n\n\nBottom line: In my opinion, in a normal view mode like Solid or Lookdev/Material, the selection of course should remain behind everything else (unless changed via its Object properties), but in Wireframe view mode the selected object should appear in front of other stuff.\nPerhaps an option is needed the Preferences to force the old 2.79b draw order.\n\n- Open attached file\n- Change the wire theme to something gray (or use the attached theme).\n[wireframe_in_2_79.blend](wireframe_in_2_79.blend)\n[classic-look.xml](classic-look.xml)\n\nThe original model is probably too big to upload here: Hypercube%20printer%20model%20(320x320%20bed,%20540x510x540%20frame).blend", "Eevee crashes when rendering some of the Blender Studio rigs\nOperating system: Windows 10 Home\nGraphics card: Intel(R) HD Graphics 4600\n\nAlso tested on Debian 11 on both GNOME and MATE. It didn't make much of a difference, the GNOME session crashes and takes me back to the login manager meanwhile on MATE the program gets killed after it freezes for too long. I'd say that this is just a difference in the behaviour of the two desktop environments, but I can't say for sure.\n\nAlso asked a friend of mine to test it on their MacBook Pro, they claim to have seen the same results as I have. Just keep in mind that they're busy and I don't have access to their hardware.\n\nTried opening it on multiple versions:\n3.0.1 (stable), 3.5.1 (stable) and 4.0.0 (alpha) with [66d20c8723e6](66d20c8723e6) being the latest commit.\n\n(Windows/Linux/Mac)\nWhen opening it from the list of recent files I see the Blender project being displayed on the screen, but apparently for only one frame then freezes. I can see the prompt that asks for script execution to be enabled, the model itself, the pose library, etc. It just freezes afterwards.\nSame thing happens for when opening it via File -> Open, but I only see the default cube project before the crash.\nGot it from .\n\n1. Run Blender\n2. Open `ellie_animation.blend`\n\nSomething else worth noting is that apparently a group of people on the Blender Artists forums are experiencing the same issue: 1342795\n\n`blender-stdout.txt` and `blender-stderr.txt` were generated like so:\n`C:\\Users\\Mustafa\\blender-4.0.0-alpha+main.66d20c8723e6-windows.amd64-release>blender --factory-startup --debug-all > blender-stdout.txt 2> blender-stderr.txt`\nI've even provided a file (`gdb-blender.txt`) containing the output of interactively debugging blender with the GNU Debuger, in case you'll need it.\nAll debug logs and related files were created on Windows.\n\nThanks in advance! It'd take a miracle to get such a huge open source project going and you're doing a great job, I appreciate your hard work on Blender.\n", "Panning with spacebar in clip editor stops after some movement\nOperating system: Windows-10-10.0.22581-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.14800 Core Profile Context 22.10.00.22 30.0.21000.22018\n\nBroken: version: 3.1.0\n\nWhen I set the spacebar to pan (disabling the play animation, tools, or search options for the same keymap), in all windows the shortcut works properly - when I press spacebar and move the mouse, the screen pans, but the clip editor window. It works for a second and then it stops working. It only works if right after pressing spacebar, I press ctrl, shift or alt, or any other key in fact. I think it causes a reset and it forgets to cancel the shortcut. Also, if I put the shortcut to be release sensitive (not press), it also works, but there's no point in making that, cause I'd have to press spacebar again in another window to apply the pan.\n\n- In default scene, switch to clip editor\n- From preferences tab, Set the spacebar as shortcut for panning in clip editor\n- Pan around by Holding `spacebar` key (stops after some movement)\n\n", "Scroll drag stuck after specific MMB click\nBlender 2.80rc1, 2.83 (sub 2)\n\nHere is the video\n[2019-02-26_06-35-31.mp4](2019-02-26_06-35-31.mp4)\n\n - Open Blender\n - In `Preferences -> Interface -> Menus` enable `Open on Mouse Over`\n - Close preference windows and go to any paint/sculpt mode\n - Display the sidebar and go to the Tool tab\n - Move mouse pointor over brush`s big icon and before it reacts with highlight (brush-search window appear) press and hold MMB\n - Then LMB to discard.\nNow scroll sticks. It releases after Esc or MMB. But at first I was forced to restart blender, because pointer stuck there.\n", "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\n\n", "Sculpting - Switching stroke method with a shortcut causes a freeze\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1\n\nWhen using E shortcut in sculpt mode to change stroke method of the brush, there is a ~5-10 second freeze every time.\nHowever, when you do the same thing from the brush UI, the switch is silky smooth. See the video for example\n\n1. Open attached file\n2. Switch to sculpt mode\n3. Do a few strokes, press E - blender will freeze for about 10 seconds\n4. Do a few strokes again, this time change stroke method from UI - no freezes here\n\nVideo:\n[blender_am0pkp0Cwy.mp4](blender_am0pkp0Cwy.mp4)\nExample File:\n[sculptbug.blend](sculptbug.blend)\n\n", "smoke effects flicker in domain when start frame is set to later than animation start frame\nOperating system: Windows 11\nGraphics card: nvidia geforce rtx 2060\n\nBroken: 3.5.0\nWorked: n/a; never worked since 2.9 at the earliest\n\nWhen smoke domain start frame is set to a value later than animation start frame, smoke effects will flicker inside that domain until the start frame is reached.\n\n`Object Mode` > `Add` > `Cube`, `Sphere`, or any other solid 3d object found in the `Tab` > `Quick Effects` > `Quick Smoke` > Under physics properties with smoke domain selected, set start frame to any value greater than the animation's Start frame > see error for self.\n\n", "One of four edited hair systems won't simulate unless edit is deleted\nOperating system: Win10\nGraphics card: GTC 1060\n\nBroken: **2.92.0 master 2021-02-24 16:25 02948a2cab44** and **2.93.0, master 2021-06-02 11:21 84da05a8b806**\nWorked: Didn't find a working version\n\n4 particle systems, one (\"Back\") won't sim unless the edit is deleted. It stays in place and stretches towards the animated head cap.\n\n**Attempted things to fix it:**\nDelete all bakes and resim - failed\nChecked the weight painting - doesn't seem to be the source of the issue\nAppend into new files and resim - failed\nDisabled dynamics - now everything moves with the haircap, but obviously no sim\nRemoved hair edit - now it works but I loose the edit\n\nOpen the file and press space to run the sim and animation. I would not know how to make a sim from scratch which won't work though so I'm sending the file.[hair_bug.blend](hair_bug.blend)", "Debug build BM_mesh_triangulate() will hang forever if mesh face count is high.\nOperating system: Xubuntu 20.04\nGraphics card: NVidia K5100M\n\n\n**Broken ONLY WITH `Debug` build**: Blender 3.0.0 Alpha (It should have been broken way earlier)\nWorked only with `Release` and 'RelWithDebInfo' build: Blender 3.0.0 Alpha\n\n\nThe call to `BM_mesh_triangulate(bm, quad_method, ngon_method, 4, false, NULL, NULL, NULL)` does not exit on some bigger meshes. Specifically, it seems to have been stuck inside `BM_face_kill(bm, faces_double->link);`.\n\n(if you call it with bmesh `op` and `slot_in/out` arguments it will run properly)\n\n\n1. Open 0_rougue_bucket.blend provided below.\n2. Add -> GPencil -> Scene Line Art **OR** go into sculpt mode and enable dynatopo (where it uses the same triangulation call).\n\nOn my machine the bucket runs fine with subdiv levels 1-2 and above 3 the bug shows. The subdiv value in that file is 3.\n\nNote that the bug is only reproducible in `Debug` build. Seems that function doesn't like meshes that has face count higher than a certain amount...\n\nMy guess would be there's a lot of checks in debug code path in the function, somewhere it reaches a case where the memory pool gets corrupted. It never quits, in the task manager, memory doesn't show any changes at all. (It's way below my 32G system memory so it can't be there being not enough memory).\n\nSince this triangulation call is related to sculpt as well so I'm gonna ask if this happens to @PabloDobarro in debug build...\n\n[0_rouge_bucket.blend](0_rouge_bucket.blend)\n\n", "Particles from multiple systems disappear when all Physics Type are None.\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.81a\n\nWhen selecting a Particle System, all particles of the object disappear.\nImages showing before and after:\n\n\n\n- In the default cube add two particle systems.\n- Set the `Frame End` of both to 1 for better observation.\n- In the `Physics` tab of both choose `Physics Type` `None`.\n- Select any of the particle systems, note that the particles disappear.\n\nAttached file contains an example of multiple particle system on one object:\n[LP_grass.blend](LP_grass.blend)\n\nThis has to be the first file you open with the application.\nIf you open blender and enable the eevee material preview for example with the default cube and open the example file afterwards it works." ]

[ "Particle system with collision modifier hangs on baking\nOperating system: Linux-5.8.0-55-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\nWorked: 2.81a\n\n[#88965.blend](T88965.blend)\n\n- Open file\n- Bake particles on LRG_Submarine_Propeller object\n\nIt fails. When you disable collision modifier on LRG_Submarine_Hull object or simplify it considerably, it works." ]

[ "Switching windows does not register as click\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0\n\nI use industry compatible keymaps.\nWhen switching between windows, no matter whether they are 2 Blender windows or Blender and any other, any camera adjustment is not registered and, depending on the keymap preset you use, you either rotate the camera or move the object instead(see attached capture).\n[switchingWindowsBug.mp4](switchingWindowsBug.mp4)\n\n1. Shift LMB Press on the corner where the viewport meets the outliner and drag to the left, this creates a new viewport window\n2. Create a cube and press on the move tool to show it's gizmo\n3. Pan the camera in one window\n4. Then without clicking into the second viewport try to pan the camera in the second viewport, depending on the keymap preset you use you either rotate the camera instead of panning or move the object\n\nBlender does not register when you have switched to the new window without first clicking with the LMB into the window.\nAs you can guess it makes it pretty nifty to switch between windows, either 2 Blender viewports, Blender and the tutorial you are watching or any window else.", "Zoom stops at certain level and won't go further\nOperating system: Windows 10\nGraphics card: GeForce GTX 1070\n\nBroken: 2.92, 3.0 alpha\n\nIn this simple model, I cannot zoom my view closer to mesh than I already did. I saved the closest achievable view position in the .blend.\nI can reach further close-ups using some more advanced navigation tools, like dolly zoom, but standard zoom won't let me.\nThe issue is linked to this particular model - if I copy the object (there's only one in the scene) to a new model, the issue is gone.\nThe model was originally saved in Blender 3.0 alpha, only then in stable 2.92. Could it be the cause of this bug?\n\nBased on the default startup or an attached .blend file:\n[zoom issue.blend](zoom_issue.blend)", "ShowNavigationGuide refresh Problem\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nno Updating the Viewport when setting the the Navigation Guide on/off\n\n \ninside Blender -Preferences -Input -Show Navigation Guide \nno refresh when checking the Show Navigation Guide on off .\norbit in the 3d-view will refresh and Update these changes.\n\n\n\n\n", "There can be infinite camera markers on one keyframe, active camera can't be uniquely determined.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\nCamera markers can be stacked up on top of each other infinitely, meaning the active camera gets randomised and has nothing to do with the displayed camera marker.\n\n\nSteps: just drag multiple camera markers on top of each other, one will get displayed at random, and then the active camera will be picked also at random, probably not being the one displayed by the top camera marker. \n\nExpected behaviour: They should behave like keyframes, if you drag one on top of another, it should replace it, not cumulate to infinity. The main issue is that when you want to synch them between scene, you \"duplicate to scene\" and then they stack up and the active camera is totally randomly displaying a random camera in the stack that's not the displayed camera marker. it's really confusing.\n\n", "Shading or Lighting Discrepancy issue\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.97\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nSo I’ve been having this problem since working in 2.8 and I don’t have a clue what could be causing this issue but I went and stripped down a project as simple as possible trying to isolate the root cause. It seems its a mesh that has an emissive material and when I disconnect the node or hide the mesh the problem disappears. Weird thing is that the brighter version is when hiding mesh number 2. I am attaching the file.\n\nYou will see how the tone changes. This never happened to me after so many years using Blender until now already in a few projects in 2.8. \n\n- Open attached file.\n- Render once using slot 1.\n- Hide mesh 2 or disconnect the emissive node.\n- Render again using slot 2.\n# Toggle with J\n\nNotice the different lighting between each result.\n\n[Shading Issue - Simplied.blend](Shading_Issue_-_Simplied.blend)", "Cycles GPU crash when switching to Rendered 3DViewport --MacOS 13.1--\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.5.0 Alpha (works fine)\n\nInstant crash of blender when switching to rendered 3DView.\n\nCompile latest 3.5 version as of 2022-12-18 20:06, hash: `50c7eb14f4`\nopen empty scene provided below and switch to rendered 3DView.\n[gpu.blend](gpu.blend)\n\n\nxcode 14.1\nlatest brew updates\n(cycles-cache & build-darwin folders deleted before compiling )\n\nPS: When switching to CPU there is no crash. Only GPU !", "Regression: Passepartout Flickers when using Solid Viewport Shading and Background > Viewport\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 2.93, 3.5\nWorked: 2.83\n\nThe Passepartout flickers with every Viewport interaction when using Solid Viewport Shading and the Background set to Viewport\n\n1. Create a 2D Animation workspace\n2. Zoom out to see the Passepartout\n3. Switch to Solid Viewport Shading and set the Background to Viewport\n\nIn this screencast, the Passepartout flickers with every Viewport interaction when using Solid Viewport Shading and the Background set to Viewport. In the video, it stops flickers when switching to World, however it is doing now. It does stop when using Material Preview Shading.\n\n[Passepartout.mp4](Passepartout.mp4)\n", "Sculpt mode: Pose/Cloth gizmos/cursors remain visible when switching to other tools \nOperating system: Win 10\n\nBroken: blender-2.92.0-165b4f85ec23-windows64\nWorked: 2.90\n\nThe gizmos/cursors of tools like Pose and Cloth remain visible when switching to other tools that shouldn't have cursor... which wasn't the case in 2.90...\n\n[2020-10-24_21-16-50.mp4](2020-10-24_21-16-50.mp4)", "Edit mode. Wire become non-selectable dependent on resolution (regression)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWithout multisampling wire just disappear and with multisampling it is still visible but not selectable.\n\n[2019-09-14_23-07-53.mp4](2019-09-14_23-07-53.mp4)\n[2019-09-14_23-09-58.mp4](2019-09-14_23-09-58.mp4)\n\n\n\nTry to select loop and zoom in-out with and without viewport multisampling. Here the file, but bug will appear even with UV-sphere.\n[b.blend](b.blend)\n\n", "Cycles: UV render pass corrupted in viewport\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.9664\n\nBroken: version: 3.1.0 Alpha\nWorked: 2.93 LTS\n\nWhen switching the render passfrom normal to UV the UVs are not displayed correctly.\n\n\nDownload bmw demo file.\nin viewport switch to render mode\nEnable the normal render pass. After that enable the uv render pass.\n\n{[F11785393](uv_render_pass.png) width=100%}\n\n`Film::update_passes` sets `shader->need_update_uvs`. The problem is that in 3.0 this is called as part of scene update after all syncing, instead of immediately after updating the render passes. That means this information is not available when we sync the geometry.\n\nNote: you can get the proper UVs back if you click on the UVMap in the Property Editor `UV Maps` panel", "EXCEPTION_ACCESS_VIOLATION error when trying to change object viewport color with the viewport compositing enabled in depsgraph_update_post\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.5.0\nWorked: 3.4\n\nThis error occurs only if the viewport compositor is enabled - rendered mode of the viewport and Compositor = Always.\nWhen trying to change the viewport color of the object by script on depsgraph update event, this error occurs.\n\nThe short script example:\n```\nimport bpy\n\ndef on_depsgraph_update_post(scene, depsgraph):\n if depsgraph.id_type_updated('SCENE'):\n for obj in depsgraph.updates:\n if isinstance(obj.id, bpy.types.Object):\n print('change object color')\n bpy.data.objects[obj.id.name].color = (1, 0, 0, 0)\n\nbpy.app.handlers.depsgraph_update_post.append(\n on_depsgraph_update_post\n)\n```\nAfter executing this script in the Text editor, switching to the \"Rendered\" mode of the 3D Viewport and enabling viewport compositing - when adding or copying the object - Blender throws an error.\n\nThis occurs only if the viewport compositing is enabled, if it is not used - code works as expected.\n\nError occurs on 3.5 and 3.6 alpha.\n\n1. I attached .blend file with the example\n2. Open .blend file\n3. Switch the viewport to the \"Rendered\" mode (z - Rendered)\n4. Execute script in the Text editor\n5. Try to copy cube (shift + d)\n6. Error throws\n\n", "Undo Makes Completed Renders Disappear From View Render Window Slots\nOperating system: Windows 10 Build 19043\nGraphics card: Nvidia RTX 3090\n\nBroken: 2.92\nWorked: Can't remember, but I don't recall this happening before\n\nUndo makes completed renders disappear from other slots in the View Render window. Some of them are preserved, but the more you undo, the more disappear from other slots.\n\n1. Load default scene (with the cube)\n2. Render scene\n3. Go to the cube's shader and change its base color\n4. Switch to next unoccupied slot in the View Render window\n5. Render scene\n6. (optional) Repeat steps 3-5 as many times as you like\n7. Go to View Render window and scroll through slots to verify all renders are there (with J key)\n8. Activate undo (ctrl+z)\n9. Go to View Render window and scroll through slots. Some will be missing.\n10. Activate undo again and more will be missing.\n\nThis doesn't seem like intended behavior, and I've replicated this issue on a different machine. Hope this helps!\n\nEdit: I've replicated this issue in 2.91, 2.90 and the latest LTS release. I assume intended behavior is for undo to change the shaders back, but for renders you've completed to remain in their slots.", "Camera background image is hidden by GPencil fill with alpha\nOperating system: Linux-4.14.78-gentoo-x86_64-AMD_FX-tm-8350_Eight-Core_Processor-with-gentoo-2.6 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 410.73\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nWhen I change the fill alpha while a background image is loaded, it behaves weirdly. i.e, when the alpha value is 0, the background image is visible, when alpha crosses 0.001, the image mysteriously disappears.\n\nIn Grease Pencil, I added a background image in the camera object data context menu,\nthen I drew a box and changed the alpha of fill, then the above said bug appears.\n\nI have included the blend file and a video to produce the bug.\n\n[blenderGreasePencilBugVid.mp4](blenderGreasePencilBugVid.mp4)\n\n[greasePencilBug.blend](greasePencilBug.blend)\n\n", "Cursor warping not supported on Remote Session\nOperating system: Linux-3.10.0-1160.59.1.el7.x86_64-x86_64-with-glibc2.17 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.2\nNever worked on previous Blender Version as far as I am aware\n\nMouse wrapping (seem in `Walk Navigation` for example) in Remote Sessions is unusable.\nAs Unreal had a similar issue that was fixed, I was wondering if that was something that could be fixed for Blender as well.\nIt happens both on Linux and Windows.\n\nInfo from the Remote tech used and possible issue:\nrelative_mouse_support/\nInfo on Unreal Problem and Solution:\n141157\n\n- Under a Remote session, go to View > Navigation > Walk Navigation to activate the tool.\n- panning and tilting around,\nthe camera will lag a lot and get out of control by over-panning/tilting\n\nThanks a lot :)\n\n", "Viewport render image not showing edge length and related info\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.81\n\nViewport render image function not showing edge length and related info that is normally visible in viewport\nthis is not working since 2.83 but was working in previous versions\n\n- take any mesh\n- enable displaying of edge length (or face area, angles etc)\n- enter edit mode and select few edges to see the info in viewport\n- go to view - > viewport render image\n\nin 2.81 you would get that edge info visible in viewport rendering, now since 2.83 it is not working\n\n" ]

[ "Negative scale camera causes BLI_assert\nWith the default scene:\n\n- Ctrl-Zero to enter camera view\n- Select the camera\n- Press N-Key\n- Drag the Y scale to negative zero.\n\n```\nBLI_assert failed: source/blender/draw/intern/draw_manager_data.c:1554, draw_view_matrix_state_update(), at 'is_negative_m4(viewmat) == !is_negative_m4(winmat)'\n```" ]

[ "Support Dragging Assets Into the Outliner\n- - [ ] Objects\n - - [ ] Drag into empty space in *View Layer* or *Scenes* display mode instantiates the object at the 3D cursor (TBD: Active collection or scene collection?). Linking places it at the location from the source file.\n - - [ ] Drag onto/into collection does the same, but assigns it to given collection. Rather not support modifier keys like {key Shift} to parent at first, better keep asset dragging simple and let users decide which collection the object should live in first. They can do the parenting then.\n - - [ ] Drag into the *Blender File* display mode only adds the object to the file, doesn't instantiate it? \n - - [ ] Dragging onto/into a collection there could still instantiate.\n- - [ ] Other Datablocks\n - - [ ] Other data-blocks only get added to the file by default\n - - [ ] Dragging materials or meshes onto objects could reassign. (Probably should consider where it's dragged to exactly, e.g. a material dropped onto another material could replace it, or add a new material slot if dropped in-between two existing ones.)\n\nMore type dependent behavior could be considered/investigated. E.g. maybe it's nice to have an image empty created when dragging an image to the Outliner.", "Eevee preview nodes with drivers performance drop Round 2\n[NodesPerformanceDropRound2.blend](NodesPerformanceDropRound2.blend) this is extend of previos task #71214\nSystem Information\nOperating system:Windows 10\nGraphics card: GeForce GTX 1060\n\nBlender Version\nBroken: Blender 2.81 Beta aff6446e064f and 2.82 Beta 092deb88b074\nWorked: 2.8\n\nShort description of error\nComplex shader with large amount of math nodes and with drivers slow down performance\nin 2.8 60 fps\nin 2.82 30 fps\n\nExact steps for others to reproduce the error\nCreate material with 30 node groups contains 30 math nodes, add driver to shader. Set viewport to material preview and watch performance droping", "Instancing Performance Improvements\nPerformance of instances in the viewport is much worse than is should be. This task is mean to keep track of possible improvements.\n- [ ] Use a vector or similar data structure instead of an linked list for storing an objects instances.\n- [ ] Don't recompute an object's instance list on every redraw.\n- [x] Store bounding box in geometry so that it is not recomputed for every geometry instance (#96968).\n- [ ] Remove the nested instance limit, avoiding the need to realize instances in some cases\n- [ ] Support passing many instances of the same to the render engine at once to reduce per-instance overhead. ", "Loading a brush alpha/texture via file browser on dense meshes takes very long.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: never i think\nLoading a brush alpha/texture on dense meshes takes very long. Especially when you do a brush before swapping out the brush texture again. If you don't do a brush stroke after loading a texture and directly load another one it will be done quicker.\n\nMy machine: AMD 5900x, 32gb ddr4 ram, RTX 3060 12gb\n\n[2022-09-20 14-13-15.mp4](2022-09-20_14-13-15.mp4)\n1. Add a standard uv sphere and apply 7 subdivisions. You will end up with over 8 million faces. \n2. Go to sculpt mode and add an image texture to the standard brush. -> rather quick\n3. Do a stroke and load another texture/alpha. -> long loading time (several seconds) and this will go higher and higher with more polygons\n4. Now don't do a brush stroke and load another texture/alpha. -> quick loading time\n\nHere are the textures i've used in the video to test. [Organic.7z](Organic.7z)\n\n\n", "Wrong number of datablocks indicated in the outliner\nOperating system: Linux 64\nGraphics card: GTX 1080\n\n2.93.5 & 3.0\n\nIn certain areas of the Outliner, icons show a little number indicating the total number of each datablock type contained in a collection, scene, etc. But the method for calculating this number is broken! If the same object shows up in multiple places, such as when it is linked in multiple collections, it will add to the total more than once. It's not hard to reveal the error- even the default file has this problem in the Blender File display mode:\n\nIt looks as though our default file has 4 mesh objects, 4 lights, and 4 cameras, but it doesn't. Those things just appear 4 times in different places.\n\n - Open the Outliner and go to Blender File display mode\n - Un-expand the Current File line to see the incorrect total\n # Link an object into multiple collections in one collection to see the same issue in the View Layer display mode\n\n\n", "Excessive Memory Usage and crash in Material Properties\nOperating system: Windows 10\nGraphics card: NVidia RTX 2060 Studio Drivers \n\nTested latest lts, latest stable, and latest daily, same result.\n\n**Description**\nI am using the UDIMS texture system for the model I am currently working on. During the rendering process, I have not encountered any issues, using approximately 20GBs of RAM. However when entering the \"Material Properties\" tab, Blender's memory usage increases. If I remove and readd a material, Blender recalculates all the materials in the scene, and the memory usage increases until my PC runs out of memory and Blender crashes. The memory usage grows this much since I have two UDIMS spaces assigned for the \"Base color,\" \"Roughness,\" and \"Normal Map\" textures, at a 4K resolution. I could understand that the size of my project or the textures are too big for my computer, but it renders without issues.\n\nThe only temporary solution I have found is to disable the image nodes in the \"Body\" material, which uses 8K images. I am unsure if this is due to an error on my part or if there is an option available to bypass this pre-calculation during work or while in the viewport.\n\n\nIf asked, I can upload a .blend file and all the necessary additional files, so you can observe the error, but it is too large to upload here.\n\nThank you very much for your attention.\n\n", "Performance iGPU with traffic-sim\nDuring testing of the traffic add-on on an 10th gen iGPU the frame rate dropped when agents were added to the scene.\n\nWill share detail soon", "Doubled Animation Render Output using only File Output Nodes\nWindows 7\n\nBroken: 2.79. 5bd8ac9,\nWorked: presumably never?\n\n**Short Explanation**\nWhen rendering an animation while using compositing output nodes, you get doubled output because of the \"write_still=True\", when the \".base_path\" of the output nodes and \"bpy.data.scenes[\"Scene\"].render.filepath\" differ.\n\nIn a new scene, go into the node editor, tick on \"use nodes\" and switch to the \"compositing nodes\" view.\nReplace the \"Composite\" node with a \"File Output\" node.\nChange its base path to \"[...]\\folder1\"\n\nGo into the \"properties\" area, into the render tab.\nUnder \"output\", change the folder to \"[...]\\folder2\"\n\nRender an animation, you will get an output in both folders.\n\nI would suggest turning off the properties panel output path when \"use nodes\" is True and output nodes are present?", "Working on a mesh that has a high multires subdivision causes blender to build Up memory even on lower levels.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\nRAM: 16GB\nCPU: AMD Ryzen 7 3800\n\nBroken: version: 3.6.0\n\nWhen editing a mesh that has been subdivided a few times will cause blender to increasingly start to consume more and more memory aggressively even if the modifier is turned off.\n\nSubdivide the mesh a few times using the multiresolution modifier, noted on 5-up levels on a mesh with originally 9 272 faces. then either switch the modifier Viewport Level to either 1 or disable It entirelly, start editing the mesh in edit mode the memory consumption stats will start to skyrocket with no signs of going back down until blender starts slowing down the computer and/or crashes entirely. (Got to about 32 GBs some times about where the computer would stop handling It anymore) I haven't tried doing it in workbench I think so I'd suggest trying to do It in Eevee mode too.\n", "Edge Sliding with subdivision surface is extremely laggy (caused by \"bad\" UVs and UV Smoothing in the modifier)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\n\nSo I've been modelling a raptor the last week and I noticed that viewport performance in edit mode was extremely laggy with subdivision surface modifier enabled. I checked the face count and it was just 150k faces which is not a lot at all. It's definitely a modifier problem because when I apply the subd modifier the lag goes away completely even when sliding twice the amount of edges around. I thought that was maybe a hardware issue so I opened task manager and while sliding edges with subd on I get like 4 fps with severe stuttering to top it off. All that while the cpu was at 10% usage and 5% gpu usage with memory barely touched (6gb used out of 64gb). I have nothing else running in the background like an ativirus or music app, I have the latest version of windows 10, latest gpu and chipset drivers, latest bios etc... I even have gpu subdivision enabled without autosmooth to make sure it actually works properly. I even run an sfc/scannow to check for other kinds of issues but nothing changed. Subd in edit mode however is not only slow when sliding edges and vertices but also in adding loop cuts or insetting faces. It is extremely frustrating so it would be great if you could fix this. I know edit mode was not made to handle massive polycounts but 150k is again not a whole lot and definitely comfortable to run on my PC. Here is the file to see for yourselves.\n\n- Open attached .blend\n- Execute Edge slide/loop cuts/inset faces\n[Broken Subd.blend](Broken_Subd.blend)\n\n", "Cycles Shadow Catcher Creating Multiple Shadows\nHi,\n\nThis .blend file will demonstrate two shadow catchers overlapping each other and creating double shadows. It would perhaps be interesting to add a termination value for the amount of shadows cast or just removed entirely.\n\n\nThanks!\nBeau\n\nSystem:\nWindows 10 64 bit\n\nBlender 2.79b f4dc9f9d68b\n\n\n\n\n\n[shadow_catcher_double_shadows.blend](shadow_catcher_double_shadows.blend)", "blender 3.4 and 3.5 hangs during compositing when rendering an animation\nOperating system: Linux-5.4.0-132-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.4.0 Beta\n\nwhen rendering a longer animation the beta and alpha versions tend to hang on the \"initializing execution\" part of the compositing. No compositing happens on the render in the render window, you see frame n while the playhead already is a frame n+1.\n\nWhen rendering the same animation it happens randomly after 5 frames or after 150 frames, but mostly with 200+ samples and at least HD resolution, smaller res and less samples went through mostly. I compared the same animation file with 3.3.1 and it just worked and the very same file with 3.4 got stuck.\n\n", "Grease pencil object in some cases look like low poly.\nOperating system: Linux-4.4.0-176-lowlatency-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 11)\nWorked: 2.82 (sub 7)\n\nIn some cases GP objects looks blocky, like a low poly objects.\n\nOpen attached file and render it.\nCompare render result with previous worked blender version.\n\n\n[2.83_bug.blend](2.83_bug.blend)\n", "UV space aware triangulation\nPlease see #102683 for details, since the issue is described and discussed there. The basic suggestion is:\n\n> Add an option to the \"Triangulate Faces\" operator. It currently has Quad/N-gon methods for Beauty, Fixed, Longest edge etc. It seems reasonable to add options for \"Prevent UV overlaps\" and specify the source UV map.\n\n", "VDB sequences are rendered blocky here and there ( issues with Volume Displacement Modifier )\nOperating system: Windows 10 \nGraphics card: RTX 2070 CUDA\n\nBroken: blender-3.0.0-alpha+master.ef5a362a5b24-windows.amd64-release.zip\n\n\nBlender renders these blocky frames here and there during the actual render. The VDBs seem to be fine, the same botched render frames look fine in the viewport render. These anomolies are happening only during the actual render. See the attached image (middle right image) for what is happening please.\n\nThe same sequence renders without any issues in Houdini.\n\n(Cycles)\n\n\n\n\nHere is an actual movie render (with Eevee) that shows how horrible this issue is.\n[borkedframes_0001-0200.mp4](borkedframes_0001-0200.mp4)\n\n\n[#88966.blend](T88966.blend)\n[steam.4.0001.vdb](steam.4.0001.vdb)\n\n- Open .blend file\n- Render sequence with CUDA\n\nIssue should appear within 30 frames\n" ]

[ "Switching to \"Textured solid\" and \"GLSL\" view will cause the FPS drop to 0 (was fine in 2.69)\nWin 7 64 bit\nGF GTX470 \n6GB RAM\nIntel Xeon w3520 @3ghz\n\nBroken: 2.70 official build Hash: 19e627c\nWorked: 2.69 official build\n\nSwitching to textured solid or GLSL with a 4k Texture will cause the framerate to drop massively to 0fps. \n\nI started working on this scene in 2.69 and i dont had any issues with the framerate. \n\nDownload the file. I packed the used textures in the Blend, so watch out for the downloadsize.\nIf you have to: unpack the Textures \nJust change in the \"n\" toolshelf the shading to \"textured solid\"\nYou will now see the textured ship, but in this situation i get around 0.2 FPS. \nMy graphiccard and cpu are around 25% usage when this happends, no intersting memoryspike or similiar to see. Maybe Blender is waiting for a thread to finish to draw the next frame? \nSadly this bug is pretty bad to work with, as i use atlastextures for my assets, so texturing without seeing the texture (because its to slow) doesnt work. \n\nIf you need more information on this issue, i will try to deliver as much as i can to solve this issue. \n\nTested on two Pcs (both intel cpus [i7 920/xeon w3520] and nvidia cards [gtx 470/ 460] latest drivers) happend on both of them.\n\nSave file (65mb!)\ntwitch_jet_01_bug.blend\n\n" ]

[ "Mesh Boolean and Bounding Box node joined together make lose the UVs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.5.0\n\nApparently, joining 2 branches of geometry node that contain a Mesh Boolean node and a Bounding Box node make the UV gone. On image attached, the cube on the left with the voronoid is the original cube and on the right it's the same cube with the Geometry node turned on. Maybe other node combination recreate this issue.\nWhen inspecting the branches independently the UV are still working but stop working when adding the Join Geometry.\n\n- Have an object with texture applied. \n- Have a geometry node modifier assigned.\n- The geometry node consists of a Mesh Boolean node joined with a Bounding box node. (I used a transformed node to move the bounding box away and see our object)\n\n", "Multiple Edge Loop Selection doesn't always work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0\nWorked: 3.3\n\nMultiple Edge Loop Selection (Shift+Alt+Select) will sometimes stop working until Shift is released and depressed again. Problem started in Blender 3.4 and did not exist in Blender 3.3 (tested).\n\n\n- Create a cylinder primitive.\n- Enter Edit Mode.\n- Attempt to Edge Loop Select multiple edges by holding Shift+Alt and clicking on them. Occasionally, this function will simply stop working after the first few selects -- no more edge loops can be selected -- until Shift is released and depressed again.\n\nThis problem does not occur for general multi selection (when only Shift is held).\n\n", "Merging vertices keeps vertex groups from one vertex, discards others\n[merge_vgroup_bug.webm](merge_vgroup_bug.webm)\nBroken: 2.80, d3870471edd7, 2019-02-12\n\nWhen merging vertices (either directly or using \"Remove Doubles\"), vertex groups are only inherited from one vertex and the others are discarded (effectively at random). Expected behavior is that all vertex groups assigned to the vertices to be merged will be inherited.\n\nDoing the same but with materials instead of vertex groups results in expected behavior (all materials assigned to the vertices to be merged are inherited), so I guess there's a case to be made for consistency.\n\n - Open the attached .blend file\n - Note that the vertex group \"top_group\" contains all top vertices and \"bottom_group\" contains all bottom vertices\n - Select all vertices\n - Remove Doubles\n # Note that the merged vertices only inherited vertex groups from either \"top_group\" or \"bottom_group\", instead of both\n[merge_vgroup_bug.blend](merge_vgroup_bug.blend)", "Solidify modifier flips faces not in vertex group\nOperating system: Linux-5.4.0-131-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.85.02\n\nBroken: version: 3.3.0\n\nSolidify modifier flips faces not in vertex group\n\n- create a cube\n- add detail faces to the cube for the solidify modifier and flip them so they solidify outwards, add this detail faces to a vertex group\n- add solidify modifier and use the vertex group\n\n- > the faces not in the vertex group are effected too\n\nWorkaround:\nSet a minimal value to vertex group factor\n\n\n\n[solidify_face_flip_bug.blend](solidify_face_flip_bug.blend)", "sharp_edge attribute doesn't work for GN-created geometry in 4.0\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\n\nBlender 4.0 is expected to finally expose normal smoothing capabilities to geometry nodes, and while the sharp_face attribute seems to somewhat work on the geometry generated inside GN, instead of inherited from the parent object, sharp_edge attribute just won't work on GN-created geometry no matter what.\n\n\n1. Open the attached file: [sharpbug.blend](attachment)\n2. Move the B value of Great Than node\nResult: sharp_edge attribute modifications don't have any effect on the mesh shading.\nExpected: sharp_edge attribute modifications affect the mesh shading.\n\n", "Support separate mesh/curve loose parts looses hooks\nWhen running separate on a mesh with hooks, the newly separated objects hooks are no longer working.\n\nIn this file: [sep_test.blend](sep_test.blend)\n\n- enter editmode\n- press P\n- choose loose parts.\n\nNotice hooks no longer work for 2 of the 3 cubes.\n\nTested with `b72a3146eb56dc021241594525848d41149044cf`", "UV Editor Snap Active to Vertex is Not Working\nOperating system: Linux-5.19.0-38-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.0\n\nI can not snap active to vertex, no matter what I try it acts like it is in median mode.\n\n\n\n\nIn the startup file snapping is enabled. In the uv editor try to move the selected vertex to snap to another vertex. Or try to snap a face instead, same issue. Sync mode on/off doesn't change the behavior.\n\n", "Edge Sliding With Snap in Edge/Vertex Mode is Inconsistent.\nOperating system: Linux-5.19.0-42-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.1\n\nEdge sliding in vertex or edge mode behaves like it is in edge perpendicular mode. This is very inconsistent because it snaps as expected in face project mode. Also in edge mode, depending on the edge being snapped to, the snapping mode will either be as expected or in edge perpendicular mode.\n\n\nFrom the blend file try to snap the selected edge to the pink edge in edge or vertex mode. Then try snapping to the annotated geometry as per the mode described in the text editor:\n\n\n", "Geometry Nodes: Mesh Boolean-Union node anamoly when boolean does not alter input mesh\nBroken: Current main.\nWorked: Never.\n\nI was trying to see if the simulation node group would get rid of internal geometry by incrementally using the **Mesh Boolean-Union** node in the **Simulation node group** but it **seems to delete some outer geometry instead.** \n\n## Without Simulation Nodes:\n| Operating as expected without Mesh Boolean Union node enabled (**creates internal geometry see red arrow**) | Operating as expected with Mesh Boolean Union node enabled (**no internal geometry**) |\n| -- | -- |\n|  |  |\n\n## With Simulation Nodes:\n\n| Description | Show |\n| -- | -- |\n| Operating as expected without Mesh Boolean Union node enabled (creates internal geometry see red arrow) |  |\n| Not Operating as expected with Mesh Boolean Union node enabled (no internal geometry but missing outer geometry) |  |\n| It should look something like this (no internal geometry but it should have \"external\" geometry also see red arrow |  |\n\nThe reason I'm trying to use the boolean mesh-union node within the simulation node group is because on some large meshes the boolean mesh-union node will fail or crash blender. \n105652#issuecomment-931240\n\nMy logic is if you have to finish an entire pie in one sitting (think of a pie eating contest) it's easier to cut them up into little pieces and eat them one at a time. **So I'm incrementally running the boolean mesh-union node on smaller pieces in the simulation node group to get rid of internal geometry therefore it's less likely to crash / fail like it does trying to do this all at once on larger meshes.**\n\nSee attached blend file: [cube repeat.blend](https://projects.blender.orgattachment)", "Some areas do not use modified (by geometry nodes) curve\nOperating system: Windows 10 - Probably irrelevant.\n\nBroken: 3.0.0 (not checked earlier versions).\nWorked: (none)\n\nThe Curve modifier on mesh objects does NOT use the modified version of a curve\n\nSee attached blend file for easy example: [bug - curve with modifier.blend](bug_-_curve_with_modifier.blend)\nExample screenshot of that blender: \nThe thin line is the curve, which has geometry nodes modifying it.\nThe thick (square) line is the mesh, which targets the curve but doesn't use the modified version.\n\n - Add BezierCurve, with a few points.\n - BezierCurve: Add geometry nodes (or any other modifier, like wave or whatever) that changes the curve.\n - BezierCurve: (for visibility) add geometry.\n - Add Cube .1m \n - Cube: Add Array modifier and Curve modifier, targeting the BezierCurve\n\n**Expected result**: Mesh follows modified curve.\n**Actual result**: Mesh follows original (unmodified) curve.\n\nThe blender file shows this very easily, the modified curve is round, the mesh is in the \"old location\" that the curve would have without the modifier on the curve.\n\n\nYes, this is a duplicate of: 93702/ - Where apparently there is confusion on what the issue is. I could not find a way to un-archive a ticket.\n\n\n**Areas Affected**\n- Curve modifier\n- Spline IK", "Edge masking artefacts on higher subdiv levels when removing the mask from lower subdivs\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.90 (sub 2)\n\nThis is a follow-up report on this bug report I made: T76386\n\nTo quickly summarise, there are still masking artefacts that aren't removed when you delete a mask at a lower subdiv level. It only deletes the mask that all subdiv levels share, but in the process the edges of the mask remain at the higer levels because said geometry doesn't exist on the lower levels. This causes problems like these to occur:\n[Desktop 2020.05.17 - 00.35.46.01.mp4](Desktop_2020.05.17_-_00.35.46.01.mp4)\n\n\n1) Take a cube and subdivide it.\n\n2) Go down to level 0 and try to mask the mesh, which will be completely invisible. Then pick any subdiv level above it and mask.\n\n3) Remove the mask at a lower subdiv above level 0 and then move up one level. The mask edges should still be there.\n\n4) Repeat 3) until you reach the highest subdiv level.", "VSE: Blade tool in Hard mode performs a Soft split (+ UI inconsistencies)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 4.0.0 Alpha\nWorked: (unknown)\n\nThe Tool Settings of the \"Blade\" tool let you choose between \"Soft\" and \"Hard\" splits, but both options perform a soft split.\n\nApart from this, there are some UI inconsistencies:\n* The tool is called \"Blade\", but the equivalent operation in the Strip menu is called \"Split\".\n* The tool's settings are called \"Soft\" and \"Hard\", but the equivalent operations in the Strip menu are called \"Split\" and \"Hold Split\".\n* The context menu has \"Split\" but is missing \"Hold Split\". (Maybe this one is intentional)\n* The context menu shows the \"K\" keyboard shortcut, but the Strip menu does not. (As a result of this point and the above, the \"Shift-K\" keyboard shortcut for performing a Hard/Hold Split is not discoverable in the UI.)\n\n* Open the VSE.\n* Add a movie strip.\n* Place the Playhead somewhere in the middle and click Strip -> Hold Split.\n* Delete the strip after the Playhead and drag the right handle of the remaining strip to the right. Notice that the newly revealed frames in the strip are dark blue; they're Hold frames as expected.\n* Delete the strip and re-add it.\n* Select the Blade tool, set the split type to \"Hard\" in the Tool Settings, and click somewhere in the strip.\n* Delete the strip after the Playhead and drag the right handle of the remaining strip to the right. Notice that the newly revealed frames in the strip are *not* dark blue; we got a Soft (non-Hold) split.\n\n", "Curves: Edit mode transform pivot on individual origins does not work\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.2.1.230210\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nAlso 3.5 beta.\n\nIn curves edit mode, transform pivot on individual origins does not work.\n\nPivot on active element also does not work, but it seems curves edit doesn't have the concept of active element at all, so not sure if this is a limitation right now.\n\n[CurvesEditTransformPivot.mp4](attachment)\n\n", "Transfer shape key is only working for meshes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: Never\n\nTransfering shape keys is option in panel menu, but it only works for meshes. This is not mentioned in documentation and only evident after running the operator.\n\n\nDuplicate object in provided file and try to transfer shape keys.\n", "Offset Edge Tool Menu Rescaling Makes It Impossible To Use\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.3 26.20.13025.1004\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nName: Edit Mesh Tools (0, 3, 6)\nAuthor: Meta-Androcto\n\nThe tool menu ad the bottom left of the viewport pops between sizes making it impossible to use\n\nselect edges, use the offset edge with extrude option.\nopen the tool menu in bottom left of 3D viewport, then switch between Angle or Depth option a few times.\nNow hovering over either the Depth or Angle button will trigger it and rescale the menu. This moves the other button up making it impossible to select.[edit menu pops up and down.mp4](edit_menu_pops_up_and_down.mp4)\n\n\n" ]

[ "Mesh to curve in 3.6.1 merges points\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.6.1\nWorked: (3.6.0)\n\nNot exactly an error.\nAfter updating to 3.6.1 from 3.6.0 I noticed my geometry nodetree wasn't working properlly, after some searching I find out the problem was the Mesh to curve node in 3.6.1, it merges points from an already splitted mesh into one spline instead of keeping each edge as a single spline. If merging points is the correct behaiviour there should at least be an option no to do so.\n\nOpen the attached blend file in both versions to see the difference in the number of splines outputed\n\n", "Regression: Split Edges node skips loose edges\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0 Beta\nWorked: 3.6.0 Alpha\n\nCaused by: 8a11f0f3a23ef9b3c11caa80f1f8646a1c19f479\n\nSplit Edge node do not split edge lines to individual edges. \n\n1. In Geometry Nodes:\n a. Add Mesh Line node.\n b. Add Split Edge node.\n c. Mesh Line -> Split Edge -> Group Output node.\n2. Apply modifier.\n3. Go to edit mode.\nNotice the loos vertices and the still connected edges.\n", "Geometry Nodes : Split Edges node don't split faceless edges\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.6.1\nWorked: 3.6.0\n\nVertices are not split when edges have no faces.\nI haven't found any mention of this change in the release notes, nor any new nodes to support split vertices. So I assume it's a bug.\n\n\n\nJust reproduce this node tree :\n\n\n\n\n**In Blender 3.5.1 :**\n\n\n\n\n**In Blender 3.6.0 it may work in specific cases :** \n\n\n\n" ]

[ "Regression: Crash on Start Up\nOperating system: Mac OS 12.6.9\nGraphics card: AMD FirePro D500 3 GB\n\nBroken: blender-3.6.3-stable+v36.d3e6b08276ba-darwin.x86_64-release.dmg\nWorked: blender-3.6.3-candidate+v36.71b55b491e9c-darwin.x86_64-release.dmg\n\nApp crashes at start up.\n\nClick on App icon, app attempt to start, crash. I restarted my computer with same results. Not opening app from a .blend file. Tried opening default app with same result.\n\n", "Blender crashes after rendering a few frames of an animation\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nI've never had this kind of problem - Blender crashes randomly after rendering a few frames of the animation. The only \"new\" thing I'm doing is I started using geometry nodes in this scene. I have plenty of VRAM left, shouldn't be a GPU issue. Tried both in 3.4 and 3.5\n\n\n", "Draw: Codegen crash MSVC 2019 debug build Mr elephant eevee\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0 Alpha\n\nFirst not working commit: d2728868c01d97540c9e5cd24adcf5f0ae6b232a (I did a bisect)\n\nBlender compiled in debug mode with MSVC 2019 is crashing in the joined scene when we switch to eevee\n\n- Compile blender master (2023/01/31) with Visual Studio 2019 in debug mode\n- Open blender with Visual studio 2019 debugger\n- Open the file joined here\n- Switch to eevee rendered mode\n\n- > it is causing a crash since the commit I mentionned\n\n\nMr elephant optimized .blend:\n\n[mr_elephantAnimed_fixed.blend](mr_elephantAnimed_fixed.blend)\n\ngif:\n\n\n\n", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "(Linux; AMD Radeon GPU) Rendering a complex scene with eevee crashes desktop environment / causes rendering and viewport artifacts\n```\nOperating system: EndeavourOS Linux / Fedora Linux (Same issue on both distros)\nGPU: AMD Radeon RX 6800 XT (16 GB VRAM)\nCPU: AMD Ryzen 5 3600\n```\n\n```\nrenderer:\t'AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64)'\nvendor:\t\t'AMD'\nversion:\t'4.6 (Core Profile) Mesa 22.3.7'\ndevice type:\t'AMD'\nbackend type:\t'OPENGL'\n```\n\nBroken: 3.4.1, 55485cb379f7, blender-v3.4-release; 3.5.0 Release Candidate, d5d8246441a5, blender-v3.5-release (both version exhibit the issue)\n\nWhen rendering complex scenes in Eevee (Scenes with many different objects), one of the following occurs:\n\n 1. On **X11**: Computer freezes for about 5 seconds before all monitors cut to black. After about 5 seconds on a black screen, the login screen appears and I can log in as normal, as if I logged out. All of the applications have closed.\n 2. On **Wayland**: Render finishes rendering, but many of the objects appear broken; they are semi transparent or appear as if they were using the holdout shader. Returning to the viewport causes all objects with transparency to flicker randomly and appear distorted. Occasionally, the desktop of the computer itself will become broken and artifacted, only logging out or restarting fixes it. This usually isn't possible, however, as after a short while everything all displays cut to a black screen. Unlike X11, however, the only way to recover from this is to restart the PC by holding down the power button.\n\nThis issue **only occurs on linux and does not occur on my Windows 10 partition**, even with the exact same settings and scene. It also only occurs when actually trying to render the scene. In the viewport everything works just fine, even on rendered view where everything looks the same as it should in the render.\n\nThis issue seems to occur regardless of the GPU Usage; even when I limit the GPU clock and power draw significantly it still happens.\n\nThe attached .blend file is an example of a simple scene which triggers the bug. It seems to occur no matter what the render settings are set to.\n\n", "Blender crashes instantly when trying to render with Cycles (HIP)\nOperating system: Windows 11\nGraphics card: AMD RX 6600 / Adrenalin 23.9.1\n\nBroken: Blender 3.4.x / 3.5.X / 3.6.2 / 4.0 Alpha\nWorked: 3.3.X\n\nBlender instantly crashes when trying to render with Cycles using HIP. Apparently only happens with files that have high number of polygons. New Project with cube doesn't crash. Using CPU doesn't crash.\nAlso, System preferences shows that I have 2 GPU units, but I have only one. It disables both when trying to disable a single one (idk if this is normal)\n\n", "Blender crashing when rendering with eevee, not with cycles however.\nOperating system: Linux-5.15.82-1-lts-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.42, 5.15.82-1-lts) AMD 4.6 (Core Profile) Mesa 23.0.0-devel (git-e20564cfdb)\n\nBroken: version: 3.3.2\nWorked: None, I've tried 3.3-LTS, 3.4 (both the default version provided through steam and manually selecting 3.4 LTS) and the daily-alpha build (with the daily-alpha build I reset settings all to default as well) All of these versions are the ones provided through Steam.\n\nWhen rendering in eevee some of my meshes completely bug out as if only part of them are rendering (I've looked at my normals and they're all fine) and after that my entire PC crashes, forcing a power cycle. The viewport display, when in rendered mode, looks fine in eevee but after rendering and before my PC crashes the viewport also messes up with my meshes looking bizarre. This issue does not occur in cycles when using CPU or GPU compute and other blender files work fine in eevee / cycles both in the viewport and when rendering. I also tried applying all modifiers despite needing a displacement on my torches to animate them but no luck. My blend file also becomes corrupt sometimes after the crash.\n\nSimply just hitting the render button with my current .blend file when in eevee. Sometimes the render goes through with broken meshes (which then I can close the render window and switch to eevee in my viewport display but my meshes will be all messed up and then my PC will crash, sometimes it crashes before the render output. \n\n\n[Dungeon Course.blend](Dungeon_Course.blend)\n\n[Dungeon Course.blend1](Dungeon_Course.blend1)\n\n[3.4 config.7z](3.4_config.7z)", "Crash when deleting ViewLayer while rendering\nOperating system: Linux-5.4.0-66-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.92.0\n\nA crash will happen when deleting a ViewLayer while rendering stills or animations, for any render_display_type\n\n- In the default scene, add a new ViewLayer\n- Set the renderer to Cycles so that you can see the render progress. In Eevee you could set up a little animation to get the same problem.\n- Start a normal render\n- While Blender is still rendering, delete the new ViewLayer that you just added and that was being in use when the render process was called\n- A crash happens with a Segfault, even after some time.\n\nThis problem looks to me as just an unhandled context change, because I noticed that if you delete the current scene or the current camera used while rendering animations, those context changes are appropriately handled and the render process is effectively stopped without a crash.\n", "Crash when rendering a specific 4k scene with Cycles Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M2 Pro Apple 4.1 Metal - 83.1\n\nBroken: version: 3.5.1\n\nWhen I render with Blender 3.5.1 on a MacBook 16\" with an M2 Pro chip at a 4K quality, Blender closes before finishing the rendering process.\"\n\n- Open attached .blend file\n- Make sure you have enabled Metal GPU+CPU in the Preferences\n- Render the scene\n\nIt should crash about halfway through the rendering process.\n\n\n", "Blender crashed in edit mode with material index creazy and strange normal\nOperating system: Linux pop-os 5.17.5-76051705-generic\nGraphics card: NVIDIA GeForce RTX 3060 Ti\n\nBroken: 3.1.0 / blender-3.2.0-stable+v32.e05e1e369187-linux.x86_64-release\n\nAn object imported from I don't know where, with crazy material_index : (-30086) in spreadsheet editor, and with strange normal, makes blender sik.\n\nIn edit mode, if I try to move the concerned geometry blender crashes systematically.\n\n[2022-06-16_bug-normal.crash.txt](2022-06-16_bug-normal.crash.txt)\n\n[2022-06-16_bug_system-info.txt](2022-06-16_bug_system-info.txt)\n\n[2022-06-16_bug-normal.blend](2022-06-16_bug-normal.blend)\n\nthank you,\n - Thomas", "Blender crashes when using bpy.ops.view3d.view_orbit with a custom context\nOperating system: Linux-5.15.11-arch2-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD RENOIR (DRM 3.42.0, 5.15.11-arch2-1, LLVM 13.0.0) AMD 4.6 (Core Profile) Mesa 21.3.2\n\nAlso tested on WIndows:\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14756 Core Profile Context 20.40.32 27.20.14032.8\n\nBroken (Linux): version: 3.0.0\nBroken (Windows): version: 3.0.0\nWorked: Never, the crash happens in 2.7 and 2.6 doesn't seem to support the override thing (I haven't tested subversions)\n\nBlender crashes when using `bpy.ops.view3d.view_orbit` with a custom context\n\nRun this in the Python console:\n```\narea = [n for n in bpy.context.screen.areas if n.type == \"VIEW_3D\"][0]\noverride = bpy.context.copy()\noverride['area'] = area\nbpy.ops.view3d.view_orbit(override, type='ORBITLEFT')\n```\n\n[blender.crash.txt](blender.crash.txt)", "Running a script that registers an operator from the same operator crashes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIf you execute an `bpy.ops.text.run_script()` through the operator through the panel in a Text editor, then blender crashes.\n\nP.s. maybe it's my fault and I did something wrong, but is blender supposed to crash?\n\nCopy the script or download the file:\n```Py\nimport bpy\n\nclass Op(bpy.types.Operator):\n bl_idname = 'op.op'\n bl_label = \"Op\"\n def modal(self, context, event):\n bpy.ops.text.run_script() # <------- here -------\n return {'FINISHED'}\n def invoke(self, context, event):\n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n self.layout.operator(Op.bl_idname, text='Click me')\n\n\nclasses = (Op, Panel)\n\ndef register():\n for c in classes:\n bpy.utils.register_class(c)\ndef unregister():\n for c in reversed(classes):\n bpy.utils.unregister_class(c)\n\nif __name__==\"__main__\": register()\n```\n\n", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n", "Crash when selecting line art\nOperating system: Linux mint 21. Blender installed using flatpak.\nGraphics card: See attached system_information.txt\n\nBroken: version: 3.5.1\n\nBlender Crashes.\n```\nbacktrace\n\nPython backtrace\nFile \"/app/blender/3.5/scripts/startup/bl_ui/space_view3d.py\", line 704 in draw\nFile \"/app/blender/3.5/scripts/modules/bpy_types.py\", line 903 in draw_ls\n```\n\n```Py\nbpy.ops.outliner.item_activate(deselect_all=True) # Operator\nbpy.ops.outliner.item_activate(deselect_all=True) # Operator\n```\nWith attached blend file, in the outliner, select cameras, line-art then try to change the color of the background.\n\n", "Crash Guide during render complete 2 December 9, 2022\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.4.0\n\nCrash Guide during render 2\n\nSame crash guide during render before and today.\nSee youtube: ZeCA2p5wISY\n\nHistory previous.\nT100691\n\n\n\n\n[Blender-2022-12-09-161546.ips](Blender-2022-12-09-161546.ips)\n\n[Horizontal Video.zip](Horizontal_Video.zip)" ]

[ "material & lamp properties crash\nSystem Information\nwindows10 nvdia GeForce GT 610/PCIe/SSE2'\n\nBlender Version\nBroken: blender2.8 alpha a6340a5068f\nWorked: blender2.8 alpha 53c63db\n\nShort description of error\nselect material & lamp properties crash\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF6F091D8E2\nModule : c:\\blender-git\\build_windows_Full_x64_vc14_Release\\bin\\Release\\blender.exe\n\nExact steps for others to reproduce the error for object material\n1.open blender\n2.in properties panel select material editor\n3.crash\n\nExact steps for others to reproduce the error for lamp\n1.open blender\n2.select lamp in viewport\n2.in properties panel select lamp editor\n3.crash\n" ]

[ "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "CPU + GPU render precision differences for small, far away area light\nOperating system: Linux-4.19.0-5-amd64-x86_64-with-debian-10.0 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74\n\nBroken: version: 2.81 (sub 8)\nWorked: (optional)\n\nThis was recently reported in this thread : \n2\n\n I can at least say, that when using small area lights below a size of 1 (e.g. meter), and it’s getting darker (the light source is far away from the object) you can clearly see this problem: CPU renders the tiles darker than the CUDA GPU.\n\n\n\nCreate a new scene with the cube, remove the default light, create an area light, resize it to lets say 10% (or 1%… the smaller the bigger the effect) and rotate it that it lights the default cube.\nHere is a .blend that reproduce the issue :\n[TileProblem.blend.blend](TileProblem.blend.blend)\n\n", "OptiX denoiser creates dark artifacts in viewport when used with 2 GPUs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.3.1\n\nThe OptiX denoiser creates several black sectors in the viewport. The smaller the area to be cleaned the more visible the error is.\nThis is only present when I have my 2 GPUs activated at the same time (3070 and 2060s). And it works normally when I enable only one of them.\n\n\n\n1. Activate both GPUs in preferences (OptiX or CUDA)\n2. Select Cycles render > GPU\n3. Activate viewport denoise and select OptiX.\n4. In viewport (Ctrl + B) set a small render region.\n[Based on the default startup]\n\n", "2.80 Pose Breakdowner doesn't work in Add NLA Strips\nOperating system: ubuntu 18.04\nGraphics card: gtx1080ti\n\nBroken: (2.80)\n\nPose Breakdowner doesnt work when editing NLA Tracks \n\n\nOpen attached file and use Pose Breakdowner\n[broken .blend](broken_.blend)", "Blender 3.1a sticks and doesn't render when rendering with Metal GPU on Mac\nOperating system: macOS-12.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.3\n\nBroken: version: 3.1.0 Alpha\nWorked: This project rendered on the same 3.1a build on the CPU, just not on the GPU.\n\nWhen I render this scene on the GPU, blender just sticks and doesn't render. (Blender 3.1a has always rendered other scenes perfectly on the GPU.)\n\n- Open .blend file\n- Render as Image (`F12`)\n The issue may be at the fault of either the fact that I have displacement on the plane, or that I have 2 render layers\n[try1.blend](try1.blend)\n\n", "just activating osl, without using it, makes any render 3 to 4 times slower\nWin7 x64\n\nBroken: 2.76b\n\nTake any prodution render with CPU, just activate osl in the render tab, it will render \" to 4 time slower, without using it in the scene. Compared to GPU render wich is already 5 times faster than a cpu render, it is = 15 to 20 times slower. OSL is unusable with this bug. Note that other renderer with OSL don't have this speed hit.\n\nWith CPU and 16x16 tiles, render this scene: pabellon_barcelona_v1.scene_.zip\nthen just activate osl, render again and compare times. although there isn't any use of OSL in the scene, the render times crawls down.\n(you can also lower the samples to 10 to make it faster for both render)", "Eyedropper: Sampling on another window does not work on Linux\nOperating system: Ubuntu 20.04 LTS (Linux-5.4.0-40-generic-x86_64-with-debian-bullseye-sid 64 Bits)\nGraphics card: AMD Radeon RX 5700 XT (NAVI10, DRM 3.37.0, 5.4.0-40-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8\nGraphics driver: amdgpu-pro-20.20-1089974-ubuntu-20.04\n\nBroken: version: 2.90.0 Alpha\nWorked: none\n\nAfter [D7910](D7910), sampling on other windows should have worked but it still doesn't on Linux.\n\nMake sure to have 2 separate windows of the same blender file (`Window` > `New Window`).\nUse eyedropper from one window to sample something on the next.\nEyedropper tool becomes a normal cursor once it leaves the window that initiated the tool.", "race_spaceship.blend demo file renders empty result (no renderlayer selected in Render Layers node dropdown)\nOperating system: Windows 11\nGraphics card: Radeon Graphic\n\nBroken: 3.6\n\nScene not display well as final render (demo file).\n\n1. Start Blender File.\n2. Check if Viewport working (all great).\n3. Render (seems going well).\n4. Final image (no image, trasparent background).\n\n", "interior rim edges not drawn for wireframe of subdiv + optimal-display\nOperating system: linux\nGraphics card: nvidia RTX 2060\n\nBroken: 3.3.1\nWorked: ?\n\ninterior rim edges not drawn for wireframe of subdiv + optimal-display\n\n(see attached .blend file)\n\nThis is not a bug, just maybe a short-coming.\n\nobject with topological hole (\"Box\")\nviewport_shading = wireframe\nviewport xray = off\nmodifier subdivision surface: - [x] optimal_display\n... inner-boundary of near \"hand-hole\" is not drawn.\n... inner-boundary of near-side rim is not drawn.\n\n[test045_subdivOptDisplay.blend](test045_subdivOptDisplay.blend)\n[system-info.txt](system-info.txt)\n", "Segfault after F12 render with multi-GPU Intel ARC A770 and experimental oneAPI packages on Debian\nOperating system: Linux-6.4.0-1-amd64-x86_64-with-glibc2.37 (Debian sid)\nGraphics card: two identical Intel ARC A770 Limited Edition 16GB\n\nBroken: 3.6.1, 4.0.0 Alpha, branch: main, commit date: 2023-07-25 19:23, hash: aebc743bf1c7\nWorked: 3.4, 3.4.1, 3.5.1\n\nSegfault when rendering Victor benchmark scene with F12 with second Intel ARC A770. This happens only when the second GPU is chosen as rendering device in Cycles. If both GPUs are selected first one seems to work correctly, but the second one causes a crash/error.\nEmbree on GPU does not seems to matter.\n\nBoth F12 and viewport renders with the second GPU give:\n`oneAPI kernel \"shader_eval_curve_shadow_transparency\" execution error: got runtime exception \"Native API failed. Native API returns: -50 (PI_ERROR_INVALID_ARG_VALUE) -50 (PI_ERROR_INVALID_ARG_VALUE)\"`\n\nRelevant info:\nI'm using following packages from experimental sources (I'm impatient I know :) ), so this crash might be very well caused by their incompatibility with Debian sid:\n`libigc1` - 1.0.13822.1-1\n`libigdfcl1` - 1.0.13822.1-1\n`intel-opencl-icd` - 23.13.26032.7-1\nRest of the packages, including all dependencies are from Debian sid.\n\nFull backtrace:\n\n```\n(gdb) backtrace full\n#0 0x0000000001cfee77 in ?? ()\nNo symbol table info available.\n#1 0x0000000001cffab9 in ?? ()\nNo symbol table info available.\n#2 0x0000000001b0fa9c in ?? ()\nNo symbol table info available.\n#3 0x0000000000f376a3 in ?? ()\nNo symbol table info available.\n#4 0x00007fffebaa63ec in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444\n ret = <optimized out>\n pd = <optimized out>\n out = <optimized out>\n unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737147199792, -8317621660586406251, -286296, 11, 140737488344416, 140734520795136, 8317937541230038677, 8317594907036290709}, mask_was_saved = 0}}, priv = {\n pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}\n not_first_call = <optimized out>\n#5 0x00007fffebb26a1c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81\nNo locals.\n(gdb)\n```\n\n1. On Debian sid install experimental packages mentioned above.\n2. Set second ARC GPU as a rendering device in Blender. \n3. Open Victor benchmark scene.\n4. Hit F12 and wait for the crash.", "Freestyle doesn't render hair\nOperating system: Win10 64bit\nGraphics card: gtx1050ti\n\nBroken: 2.8-155c62b070a9\nWorked: 2.79b\n\nRender file with Cycles in 2.79b and 2.8. In 2.8 only mesh is outlined.\n[free.blend](free.blend)", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Crash on Mac when starting with `--debug-gpu` flag\nOperating system: Mac OS Ventura 13.1\nGraphics card: Apple M1 Max\n[system-info.txt](system-info.txt)\n\nBroken: 3.4.1\nWorked: 3.3.2\n\nBlender won't start on a Mac when starting with `--debug-gpu` flag.\nThe terminal output is this:\n\n```\n/Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\nRead prefs: /Users/vollstock/Library/Application Support/Blender/3.4/config/userpref.blend\nWARN (gpu.debug): source/blender/gpu/opengl/gl_debug.cc:165 init_gl_callbacks: Failed to hook OpenGL debug callback. Use fallback debug layer.\nzsh: segmentation fault /Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\n```\n\n\nStart with the flag\n\n```\n/Applications/Blender.app/Contents/MacOS/Blender --debug-gpu\n```", "Clang on windows\nWhile we have supported building with clang on windows for a while, support has deteriorated a little due to it not getting regular exercise also not all features were supported this is a list of outstanding issues with clang on windows.\n\nOrder of importance:\n\n- {icon circle color=red} **Very Important** - *These we should handle before the next release.*\n- {icon circle color=yellow} **Somewhat Important** - *These issues would be nice to do as soon as possible*\n- {icon circle color=green} **Less Important** - *Extra polish, nice to have*\n- `?` **Incomplete** - *Tasks needing more details before implementing.*\n \n- {icon circle color=green} Better documentation on how to build, [the initial commit ](rB81060ff6b26c22331d2066bb83d492bbe61e936c) had instructions but some of those instructions are no longer applicable \n- {icon circle color=green} [D5962: Fix: Building quadraflow with clang on windows.](D5962)\n- {icon circle color=green} ~~Building with clang+ninja is broken~~ fixed:34bd23dbb7\n- {icon circle color=gray} VS2019 IDE support is broken due to the llvm integration addon, VS2017 IDE works, ninja work for both 2017/2019 \n- {icon circle color=green} [D5976: Add support for building with OpenMP support for clang on windows.](D5976)\n- {icon circle color=green} [D6012: Fix: BLI_expr_pylike_eval_test test failing with clang on windows](D6012)\n- {icon circle color=green} Cycles had a broken AVX2 kernel when running the benchmarks on EC2 \n- {icon circle color=green} Too many warnings a full build log is over 1GB \n- {icon circle color=green} cycles kernels get fed clang flags which it does not recognize `-fno-trapping-math`, `-fno-math-errno` , `-fno-signed-zeros`" ]

[ "Cycles Render Devices / No compatible GPUs found for path tracing\nOperating system: Windows 10\nGraphics card: GeForce GTX 1070 (driver version 462.59)\n\nBroken: 2.83.14\nWorked: 2.92.0\n\nAll the CUDA/OptiX/OpenCL tabs give same info on 2.83:\n**No compatible GPUs found for path tracing\nCycles will render on the CPU**\n[blender_system_info.txt](blender_system_info.txt) [blender_debug_output.txt](blender_debug_output.txt)\nOn 2.92 CUDA/OptiX I have those checkboxes for both GeForce and CPU so it's ok\n\nPreferences/System/Cycles Render Devices", "Graphics Card not discovered\nOperating system: Windows 10\nGraphics card: NVidia GTX 1070\n\nBroken: 2.83.14\nWorked: 2.83.8 in summer of 2019\n\nGraphics card doesn't show on the list of supported GPUs\n\nImages attached\n\n\n" ]

[ " Freestyle renders extra lines\n%%%--- Operating System, Graphics card ---\n1st PC: Win7 64bit & Quattro 2000\n2nd PC: Win7 64bit & Nvidia 560ti\n\n\n\n - Blender version with error, and version that worked ---\n2.68a\n\n - Short description of error ---\nFreestyle produces lines through objects as they are transparent\nI build a moving staircase and some lines of the glass roof appear \"randomly\" through the walls.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\n\n\nI just created objects + render. %%%", "Material glitches at joints when using Bevel modifier\nOperating system: Ubuntu 20.04.3 LTS\nGraphics card: GeForce RTX 2060\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\nWorked:\n\n\nI know people experience no end of unexpected Bevel behavior due to issues with their geometry. But I think this is a genuine bug - as do people who responded to my Blender SE question: 124535\n\nRobin Betts commented there that \"it looks like a bug. But at least a consistent, and therefore traceable bug. It seems to be in the 'Automatic' (-1) material offset setting, which should split the bevel down the middle at material boundaries. It's getting the boundary 1-off at the end of a patch/arc spread of faces.\"\n\nAt joints where two materials meet, the Bevel modifier seems to miscalculate which faces of the bevel should contain one material and which the other, as shown here:\n\n\n\nIf I apply the modifier, I can then correct the issue by hand.\n\nThe above picture is from Blender 3.1.2. The problem seems to have been there for a long time, things look different but are still incorrect in 2.93.7:\n\n\n\nThe complete mesh is fairly simple (I cut it out of a larger object for this bug report) and I've confirmed there are no overlapping vertices etc.:\n\n\n\nI actually started with a much simpler mesh but converted to triangles to ensure the issue wasn't somehow n-gon related (it isn't):\n\n\n\n\nCreate a simple shape like the one shown in the last image above and use two different materials for your object, e.g. above, I've applied one material to the darker colored faces and the other to the lighter colored faces.\n\nThen apply a *Bevel* modifier and then look at the object in a *Viewport Shading* mode that shows materials, e.g. *Material Preview* or *Rendered* (you can even see the issue with *Solid* viewport shading if you set the *Viewport Display* for one of the materials to be a different color to the default grey).\n\nHere are two small `.blend` files - the first created in Blender 3.1.2 and the second in Blender 2.93.7:\n\n[bevel-3.1.2.blend](bevel-3.1.2.blend)\n\n[bevel-2.93.7.blend](bevel-2.93.7.blend)\n\nYou can find a larger `.blend` file containing the original full mesh in my Blender SE question: 124535", "LineArt: \"Force intersection\" doesn't work like expected\nVersion: 3.3.2 Release Candidate, branch: master, commit date: 2022-10-17 14:20, hash: c98268d3f56d, type: release\nBuild date: 2022-10-18, 00:42:54\nPlatform: 'Windows-10-10.0.22621-SP0'\n\nRenderer:\t'NVIDIA GeForce RTX 3090/PCIe/SSE2'\nVendor:\t'NVIDIA Corporation'\nVersion:\t'4.5.0 NVIDIA 516.59'\n\nLine Art usage mode \"Force Intersection\" doesn't work like expected. See my screenshot and attached file for tests.\n\nObjects or collections that are set to \"Force Intersection\" should always produce intersections, even if other rules defines something else.\nLine Art usage set to \"Force Intersection\" should work like a global line art override.\n\n1. Try to set the Line Art usage of object \"Cube1\" to Force Intersection mode.\n2. Try to set the Line Art usage settings to \"Force Intersection\" to the Collection called \"Forced Intersections\".\n\n- >Both settings produce no results, means: Cube1 intersections with other objects aren't visible.\n\n**Screenshot:**\n\n\n**File:**\n[IntersectionBug.blend](IntersectionBug.blend)", "Cutter Tool Not Working When Lines are Drawn with the Draw Tool Using Guides\nOperating system: Windows 10\nGraphics card: Gigabyte GeForce RTX 3080\n\nBroken: 3.5.1\nWorked: Never tried it in older versions\n\nI use the Guides function to draw in perspective; however, the Cutter tool won't cut the lines correctly when the Guides function is used to draw the lines. Sometimes, it cuts them oddly. Most of the time, it doesn't cut them at all. When I use the Draw tool and manually draw in perspective (without using the Guides function), the Cutter tool works fine. \n\nStrokes drawn with \"guide\" options are not cleared in some cases with cutter tool\n\n- Use the Cutter tool on these to cut the lines from the intersections. I've named the layers appropriately.\n", "Some areas do not use modified (by geometry nodes) curve\nOperating system: Windows 10 - Probably irrelevant.\n\nBroken: 3.0.0 (not checked earlier versions).\nWorked: (none)\n\nThe Curve modifier on mesh objects does NOT use the modified version of a curve\n\nSee attached blend file for easy example: [bug - curve with modifier.blend](bug_-_curve_with_modifier.blend)\nExample screenshot of that blender: \nThe thin line is the curve, which has geometry nodes modifying it.\nThe thick (square) line is the mesh, which targets the curve but doesn't use the modified version.\n\n - Add BezierCurve, with a few points.\n - BezierCurve: Add geometry nodes (or any other modifier, like wave or whatever) that changes the curve.\n - BezierCurve: (for visibility) add geometry.\n - Add Cube .1m \n - Cube: Add Array modifier and Curve modifier, targeting the BezierCurve\n\n**Expected result**: Mesh follows modified curve.\n**Actual result**: Mesh follows original (unmodified) curve.\n\nThe blender file shows this very easily, the modified curve is round, the mesh is in the \"old location\" that the curve would have without the modifier on the curve.\n\n\nYes, this is a duplicate of: 93702/ - Where apparently there is confusion on what the issue is. I could not find a way to un-archive a ticket.\n\n\n**Areas Affected**\n- Curve modifier\n- Spline IK", "Grease Pencil shimmers in the viewport and renders\nOperating system: Windows 7 Ultimate\nGraphics card: Nvidia Quadro 2000\n\n2.92.0\n\nI have a video below, If you see carefully the lines are shimmering, Is there any way to avoid that? watch?v=aBIJbTTiLlU \nAttached a blender file as well.\nI tried \n- increasing samples of viewport \n- increasing anti-aliasing of grease pencil. \n- different render systems 'eevee' and 'cycles'. \n- Tried all possible file exports but the problem is in the viewport itself.\nShould I try denoising it? although that didn't work so well either.\nThe problem just isn't going way. Is it my system? Could you help?\n\n[room fix.blend](room_fix.blend)", "Curve Pen Error\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 4.0.0 Alpha\n\nNothing happened when I left click my mouse using Curve Pen in Edit Mode, but it is fine with blender on my windows laptop.\n\nI added a Bezier and I enter the edit mode, I deleted all the vertices and decided to draw a line using Curve Pen. However, it did not work.\n\n", "Grease Pencil Arrange Stroke operator does not function with Curve Editing\nOperating system: Linux 64-bit\nGraphics card: GTX 1080 ti\n\n2.93.5 and 3.0.0 alpha\n\nIn edit mode, \"Arrange Stroke\" operator does not work when use_curve_edit is enabled.\n\n[GP_arrange_bug.blend](GP_arrange_bug.blend)\n\n - Open attached file\n - Use any of the Arrange Stroke operators on the selected stroke\n # Disable Curve Editing and try again to see that it otherwise works as intended\n\n", "Strong emissive materials bleeding through grease pencil objects\nOperating system: Win10 Home 64\nGraphics card: rtx3070\n\nBlender Version\nBroken: 2.83, 2.90, 2.91, 2.92, 2.93, 3.0, 3.1\nWorked: N/A\n\nExact steps to reproduce the error:\n\nGive default cube an emissive material with strength ~50 or so and put any grease pencil object in front of it in Rendered view. This artifacting carries over into the actual renders. \n\n\n(I think it's an opacity issue, because creating a duplicate of the grease pencil on top of itself (Array modifier with 0,0,0 offset) covers the emission glitch up.)\n\n**Steps to Reproduce**\n- Open .blend file\n- Render in viewport\n\nTest File:\n[#94004.blend](T94004.blend)\n\n", "Proportional edit influence radius marker for Grease Pencil object is misplaced\nOperating system: macOS Catalina 10.15.7\nGraphics card: Radeon Pro 560 4 GB\n\nBroken: 2.92.0, 02948a2cab44, master, 2021-02-24 16:25\n\nAlso tried with 2.93.0 and the erroneous behavior is still there.\n\n[proportional-edit-bug.blend](proportional-edit-bug.blend)\n\nSteps to reproduce the error:\n1. Open the attached .blend file.\n1. Select the (only) GPencil object and go into edit mode.\n1. Enable proportional editing.\n1. Grab one point of the grease pencil curve and start moving it.\n1. Observe the influence radius marker being drawn at the object's origin point, instead of the current selection's median point.\n\n", "GPencil: Fill tool Ignore Transparent strokes setting broken\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Beta\n\nFill tool not ignoring transparent strokes when the settings is enabled. When you enable Show boundary lines, it shows that transparent strokes are not a boundary but the fill still uses them as boundaries.\n\n- Open attached file and try the fill tool. Under the Advanced menu 'Ignore Transparent' and 'Show Lines' are enabled.\n\n", "Cycles misses intersections when objects are too close\nBroken: 2.79b\n\nWhen two objects are too close, Cycles can miss intersections.\nIn the attached file, there are two intersecting semitransparent planes (at the center).\nIf the color is green or pink it indicates that the ray only intersected one plane.\n\n- Open the attached .blend file and render.\nNote how the line where the planes intersect has a coloured border.\n[transparent_planes.blend](transparent_planes.blend)", "The bridge tool fails in a situation with multiple rows of faces facing each other\nWin10 Pro 64 bit; AMD Ryzen 2700X; Nvidia GTX 1060 6GB; 32 gigs RAM\n\nBroken: hash d1be30f (buildbot build May 4).\nWorked: never\n\nIn a situation where you have multiple rows of faces that face each other across empty space (with other areas where they face away from each other). The bridge tool (even with*loop pairs* checked) is unable to give priority to the direction the normals are facing. The result of this is that instead of getting nice bridges among the multiple rows of cubes, the tool produces faces that overlap and have zero area. As hinted, the*loop pairs* checkbox in this case does not do anything and the result is the same.\n\nOpen the .blend, invoke the bridge operator (the result is the same whether or not \"loop pairs\" is selected.\n\n**blend**\n[IffyBridge.blend](IffyBridge.blend)\n\n[IffyBridge.blend](IffyBridge.blend) (updated blend)\n\nAn additional note; I submitted this issue years ago, but it was never fixed and I couldn't find my old report. If the bug is not going to be fixed, then just close this as a todo item or with a \"won't fix\" tag.\n", "Changing the Orientation of Modifiers\nCurrently, LineArt is created in 3D space, however, the Modifiers can be oriented incorrectly.\n\nIn this example, the Noise Modifier is moving the Grease Pencil points on the Normal but not up and down on Z. There is currently no way to change it.\n\n[Noise - Position.mp4](Noise_-_Position.mp4)\n\nThis is a request for a way to change the orientation of the Modifiers.", "Geonodes points have wrong generated texture coordinates\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.2.2\nWorked: ?\n\nGeometry nodes points use object coordinates in the \"Generated\" input of the Texture Coordinate node that doesn't match the look of generated coordinates for common spherical meshes, making materials look different between points and meshes\n\nOpen the attached file, go into rendered view\n[Coordinates.blend](Coordinates.blend)" ]

[ "LineArt wrong intersection detection on scene collections containing intersecting object\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.3.3\nWorked: N.A.\n\nLineArt always create intersection lines if in the scene there is a collection that includes intersecting objects.\n\nopen the attached lineart_intersection.blend. The file containss 2 collections:\n\n1. no_lineart - includes a suzanne and torus.\n2. lineart - includes just the default cube\n\nA LineArt is created from lineart collection, even if the other collection is not involed, its intersections are incorrectly drawn on in the LineArt.\n\n" ]

[ "Set Material Index node does not work on some GN-created geometry\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\nWorked: Never.\n\nThe scene contains 3 objects:\n1. Mesh object with GN which creates Mesh Cube primitive\n2. Curve object with GN which creates Mesh Cube primitive\n3. Curve object with GN which creates geometry using Curve to Mesh node\n\nAll 3 objects have their Material linked to Object, not Object Data\n\nThe Set Material Index node works on 1. and 2. but does not work on 3.\n\n1. Open the attached blender file: [curvematerialbug.blend](attachment)\n2. Check Geometry Nodes setups on all 3 objects\nResult: Set Material Index Node does not work on Geometry generated by Curve to Mesh node.\nExpected: Set material Index Node works on any geometry.\n\n", "Eevee Group Node ignores socket type conversion (eg. Vector to Float)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha, branch: main\nWorked: N/A\n\nIf the input of a group node is `Float`, but you connect a `Vector`, the group will read the input as a vector instead of a float.\n\n1. Download the Blender file below\n[test.blend](test.blend)\n2. Switch to Eevee, it looks like this:\n\n3. Switch to Cycles, it looks like this:\n\n\nIt seems to be node group evaluation. When ungrouped it looks identical.", "Particle systems cannot read curve modifiers and geometry nodes ..\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.1\n\nCan particle systems not use curves with modifiers added, or can particle systems only support fixed curves? This seems to lose a lot of creativity\n\n", "Geometry Node in World Shaderworkspace does not output the same coordinates in Eevee like in Cycles.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.0.0 Alpha\nWorked: None same in 2.83\n\nGeometry Node works differently for Cycles and Eevee in the World Shader Tab, The Coordinates are distorted with Eevee. Im not sure if this is as expected.\n\n1 Goto Shading Workspace\n2 Enable Viewport Shading and enable World Background\n3 Add Geometry Node.\n4 Connect either Position, Normal, True Normal or Incoming to Background Shader.\n5 Switch between Eevee and Cycles to see the difference.\n\nOn the other hand, the Normal output of the Texture Coordinate Node is exactly the same in both render engines.[Geometry Shader in World Bug.blend](Geometry_Shader_in_World_Bug.blend)", "Annonymous Attributes and Simulation Nodes - propagation issue\nBroken: version: 4.0.0 Alpha\nWorked: Never.\n\nSome annonymous attributes are not working with the output of the Simulation Nodes if the attribute is not propagate via the simulation.\n\n\n1. [simulation_attribute_bugs.blend](attachment).\n2. Toggle the \"Show Bug\" modifier property to see when the bug happens.\n\n", "Node Group Sliders Slow Performance using Packed Textures\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.83.6, also tested in the 2.91 daily build, and 2.90.1. Same performance.\n\nUsing custom nodes groups sliders with packed textures make them very slow using Cycles, on EEVEE it seems working fine. \nIf i unpack the textures the sliders acts normally.\nI also notice every time i use any slider in the top left corner shows \"Updating images\" and the freeze occurs. \nI also discover if i change the values of all the sliders that are using the packed textures it comes back to normality and the lag disapears.\nIm not a tech but it seems it has something to do with loading the textures.\nSize and image formts seems that are not the problem i tried changing them.\n{[F9090399](Packed_textures_performance.gif), size=full}\n\n- Append node group with textures unpacked.\n- Sliders working good and fast with textures unpacked.\n- Pack the textures.\n- Sliders and load times freezing.\n- Unpack the textures again.\n- Sliders come back to normality.\nor\n- Open attached .blend file\n- Play with the custom node sliders\n- Unpack the textures again.\n- Sliders come back to normality.\n\n[Packed _Performance_new.blend](Packed__Performance_new.blend)\n\n", "Particles Nodes\n**Status:** Project on hold. Active development in this area can be found in the [geometry nodes project ]().\n\n---\n\n**Team**\n**Commissioner:** @brecht\n**Project leader:** @JacquesLucke \n**Project members:** @sebbas @WilliamReynish\n\n**Description**\n**Big picture:** Implement a stable (reliable) flexible node based particle system.\n\n**Use cases**:\n* Motion-graph work that relies on time-based animations.\n* Set dressing of environment elements.\n* Generative weathering of surfaces.\n* Fireworks (particles that spawn new particles).\n* Dew drops on a leaf.\n\n**Design:**\n* Re-usable effects\n* High level nodes out of the box\n* ? (mental model for different types of nodes)\n\n**Engineer plan:**\n* C++ libraries in blenlib.\n* New builtin simulation node system.\n* The functions framework with a runtime type system for efficient evaluation of node trees.\n* The particles system that parses a particle node tree and performs the simulation.\n\n**Work plan**\n\n**Milestone 1**\n*Time estimate: 2-4 months*\n- [ ] Particle nodes\n - [x] Add Simulation node tree type\n - [x] Add placeholders for built-in simulation nodes\n - [x] Add placeholders for built-in function nodes\n - [x] Define list of built-in nodes\n - [ ] Define list of group nodes to ship with Blender\n - [x] Define categories and menu organization\n - [ ] Finalize naming of nodes and sockets\n - [x] Support for storing ID pointers in sockets for object/image sockets\n- [ ] Explore different ways to visualize sockets and links of different type ()\n- [ ] New `Simulation` data-block containing node tree and cache parameters\n - [x] Basic implementation of ID type\n - [x] Dependency graph and copy-on-write integration\n- [ ] Point cloud (basic) object type (@brecht)\n- [ ] Modifier for point cloud copies simulated particles from simulation\n- [ ] Simulation caching\n- [x] Functions nodes system\n- [ ] Particle solver capable of solving multiple particle simulations with emitters, events and forces (#77266)\n- [x] Find system to ship node groups with Blender (asset system or if not ready, something temporary) (in branch currently)\n- [ ] Implement all built-in nodes\n\n**Milestone 2 - Feature completion**\n- [ ] Use cases are supported (particle scattering, weathering, ...).\n\n**Unknown Milestone**\n- [ ] Good collision handling in solver\n- [ ] Access any particle attribute in material\n- [ ] Access particle data from Python\n\n---\n\n**Relevant links**:\n* #68636 (Initial Particle Nodes)\n* [Everything nodes project ](Nodes)\n* [Unified Simulation System Proposal ](UnifiedSimulationSystemProposal)", "Collada import/export: transparent textures don't work\nOperating system: Linux\n\nBroken: blender-3.3.0-alpha+master.dfb8c90324c0, probably all versions since 2.8\nWorked: 2.79\n\nCollada cannot import or export transparent (alpha) textures.\n\nImport this .dae\n\n[BlenderLogoDae.zip](BlenderLogoDae.zip)\n\nThe result (with 2.79 for comparison).\n\n\n\nManually hook up the alpha in the node graph and export. Open the .dae in a text editor and confirm there is no <transparent> element (which sets the alpha texture). You can confirm exporting works in 2.79 by exporting and reimporting.\n\n**Other**\nNote that OpenCollada's parsing of transparency is weird and buggy, see [D11259](D11259) and 651.", "Cycles - AO Shader node causes infinite \"loading render kernels\" and crashes on return to solid mode view\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.2.0\n\nAO Shader node causes infinite \"loading render kernels\" and crashes on return to solid mode view\n[AO BUG Test.blend](AO_BUG_Test.blend)\nAttaching Sample file.\nJust render the scene in viewport (doesnt render, just \"loading render kernel\" message)\nTry to go back to solid view - results in freeze/crash\n\nregards\n", "Physics: The default value for Format Volumes is nothing...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 2.93.4\n\nThe default value for Format Volumes is nothing...\nBlender will stop working if you try to let the Animation play. EDIT: Can no longer reproduce with Blender 3.0\n\nDo a Backspace (to reset to default) on \"Format Volume\"\n![2021-09-09 09_15_29-Blender_ [C__Users_raimund.klink_Downloads_adaptive bug2.blend].png](2021-09-09_09_15_29-Blender___C__Users_raimund.klink_Downloads_adaptive_bug2.blend_.png)\n[happy_little_bug.blend](happy_little_bug.blend)\n\n", "Data Transfer doesn't work in some situations (geometry nodes modifier preceeding the Data Transfer modifier)\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GT960\n\nBroken: 3.5.0 (2023/01/11)\n\nData Transfer does not work on geometry generated by Geometry Nodes\n\nError is set up in the attached file:\n\n[Color Transfer Test.blend](Color_Transfer_Test.blend)\n\nDoesnt work in `Material` or `Rendered` viewport mode either.\n\n[Color Transfer Test 2.blend](Color_Transfer_Test_2.blend)\n\nI don't know if it's related (it feels like it is) but even setting color inside a geometry node (on geo node created meshes) doesn't work in Material or Rendered viewport modes.\n\n[GeometryNodesColorBug.blend](GeometryNodesColorBug.blend)", "Node Tools Overview\n## Background\nWith node group assets becoming more prevalent and geometry nodes becoming essential\nfor manipulating geometry in Blender, we want to add the ability to implement operators\nwith geometry node groups.\n\nRelevant node groups would need a geometry input and output, and could have other inputs (and possibly outputs), with similar mappings as the geometry nodes modifier.\n\nAdditionally, specific inputs could be marked as editable modally, for example, a \"Factor\" input could be controlled by moving the mouse cursor left or right.\n\nThe specific data design still needs to be settled on (i.e. is the node group an operator, or does an operator reference a node group?).\n\n## Design\n- The node group itself is the operator asset\n- Geometry nodes gets new input nodes\n\t- Selection\n\t- Mouse coordinates\n - View transform\n - 3D cursor location\n - etc.\n- Geometry node groups with these input nodes can only be used as operators\n\t- This design is similar to the shared node groups between shader and geometry nodes, for example.\n- The group outputs are used to adjust the output geometry\n\t- The geometry output will adjust the \"active\" geometry\n - We _might_ need to store a specific mapping for outputs, but relying on the name is a start\n- The project is \"completely finished\" when any existing edit mode operator could be implemented with nodes\n\n## Implementation\n\n_Organized by priority in each category_\n\n### 4.0 Targets\n\n_Changes needed to move the feature out of experimental and enable it in the release_\n\n- [x] Initial basic feature for curves sculpt mode e4cc91a6113f14418b5d8f2a0aace252dc3949d8\n- [x] Allow controlling which modes assets are available in fd9d22ba57d75b278a0350492c5eab2d39d39070\n- [x] Update 3D view menus dynamically (avoid need to restart Blender) cc83951951efc28411960d950435224e8d06606c\n- [ ] Make object info node geometry output work properly\n- [x] #111529 Show menus for unassigned node group assets d2d4de8c710c4e8e648a86f904e6436133664836\n- [x] Tool specific nodes\n - [x] Selection input e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] Set selection e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] 3D cursor e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] Sculpt face sets input e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n- [ ] Node group inputs displayed in the redo panel\n - [x] Initial input drawing bc393c403325c956ec4e83eeb072a9bdb2e7824d\n - [x] Display node group name in panel title f0467b4615b366f34f0daae81ef717c342e8f520 ee1ee584ded3b76fdd9b661244274af850b08fa9\n - [ ] Add attribute search\n - [x] Don't draw redo panel when there are no inputs c59d998ce524e37c2449694602fb6d57b6d292fa\n- [x] #111523 Improved default traits b4dc16f32d92a2fbc140abfe6eb438ff11b5d5e8\n- [ ] #111524 Finalize trait popover locations\n- [ ] Add support for evaluating output attributes\n- [x] Shortcut support 65591b2c8cc83b024bc0a283bae1bbeb7ee85132\n- [x] Quick favorite support 65591b2c8cc83b024bc0a283bae1bbeb7ee85132\n- [ ] #111526 Filter data-block selector based on tool/modifier option #112389\n- [ ] Publish the user manual\n\n### Polishing\n\n_Not necessarily required for a release in main_\n\n- [ ] Show visual difference for tool nodes in modifier context\n- [ ] Show visual difference for viewer and simulation nodes in tool context\n- [ ] Resolve flickering in asset browser when using redo panel\n- [ ] Warnings in node editor header\n - [ ] When node group is not an asset (with button to mark as asset) #110813\n - [ ] When the node group is not marked as a tool #110813\n - [ ] When asset is not in a catalog (and not in a menu) #110813\n\n### Milestone 2\n\n_The second phase of the project, after the fundamentals are working well_\n\n- [ ] Option to show settings in popup before operation starts\n- [ ] Tool specific nodes\n - [ ] Sculpt \"soft selection\" input and set\n - [ ] View transform\n - [ ] Mouse position\n - [ ] Deformed (\"cage\") positions\n- [ ] Modal operator support\n- [ ] \"Wait for cursor\" option\n- [ ] Store operator properties for the next execution\n\n\n## Use Cases and Ideas\n- [ ] Mesh sculpt \"face set extract\"\n- [ ] Mesh sculpt \"mask extract\"\n- [ ] Lasso selection operator", "Cycles: Caustics don't work when volume boundary between casting and receiving surfaces\nOperating system: MacOS, Windows\nGraphics card: Apple Silicon, Nvidia RTX3090\n\nBroken: 3.5.1, 3.6 Alpha\nWorked: -\n\nWhen there is a volume boundary between a caustic casting and receiving surface, the caustics vanish. \n\nOpen the attached .blend file. There is a sun, an ocean surface, and a sea floor. There are 4 sections: \n- On the right, there is no volume and the caustics appear\n- the two middle sections contain volumes where either the top or bottom boundary of the volume is between ocean and floor, and no caustics appear\n- on the left the volume boundaries are above the ocean, and below the floor, and caustics are visible\n\n", "Two materials: volumetric being in second slot causes error in EEVEE\nOperating system: Windows 10 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.90.1\nWorked: IDK, but I've been using blender since 2.79 and have not encountered this problem when I have done this kind of thing.\n\nWhen I have a mesh object that has both solid and Volume Scatter materials on it (in different slots), in EEVEE, the volumetric material only works if it is not in the second slot. If it is in the second slot (top down), it causes the black \"shader missing\" to be applied. Moving the volume slot up to the top with the solid material in the slot at the bottom causes normal operation.\n\nGo into edit mode on the default cube.\nDuplicate the mesh, but leave it at 0 0 0. Scale the duplicate up a little.\nCreate a second material slot, and assign the duplicate larger cube to it. Leave edit mode.\nCreate a \"Volume Scatter\" material for the second slot. The outer cube will turn black.\nMove volumetric material up in list of materials. The outer cube will change to the proper fuzzy grey.\n\n[#83538.blend](T83538.blend)\n", "Material Library VX causes permanent freeze with EEVEE rendering\nOperating system: Windows 10, 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.81\n\nUsing materials from Material Library VX addon, particularly Floor Wood and Rusty Metal, causes EEVEE to freeze all of Blender. They work fine with Cycles, so it's not the addon. Not even the partial \"developer view\" render can take the materials.\n\nOpen default blend file.\nEnable Material Library VX addon.\nApply \"Floor Wood\" to the cube.\nSwitch to \"render view\" without changing the engine off of EEVEE. Blender 2.81 will freeze.\n\nNote: If you try to view the material preview and EEVEE is the render engine even *that* will freeze Blender 2.81." ]

[ "Eevee - no volume density textures when using Vega 64 external gpu on macOS Mojave\nOperating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26\n\n\nBroken: version: 2.80 (sub 74)\nWorked: Was working briefly with some builds in March 2019.\n\n\nMacOS Mojave external GPU fails to render volumetric on Eevee if there is a density texture. Internal GPU works fine.\n\nUsing external Vega 64:\nOn default cube, add principled volume shader to volume material output: volume looks correct.\nPlug noise texture node into density input of principled volume shader: volume disappears.\nUsing internal Radeon 560x:\nExact same steps gives properly textured volume.\n\n", "Eevee volumetric rendering on Mac Pro 2019\nOperating system: 10.15.4\nGraphics card: AMD Radeon Pro 580X 8 GB (or Radeon VII)\n\nBroken: 2.82a\n\nAny volumetric effect nearly completely shuts down the computer. The effect doesn't show properly; there's little detail and a lot of errors. Trying to render at 4K crashes the Mac Pro 2019 and the iMac 2017.\n\nAlso the 2 Radeon VII cards can't show any volumetric imagery.\n\n[Clouds.blend](Clouds.blend)", "volume shader shows \"nothing\" anymore if i plugin a colorramp + something in the colorramp\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha\n\n\n\n1) add a cube\n2) add material - principle volume\n3) add colorramp\n4) plug in a noise texture or any texture now in the colorramp - > the volume is \"gone\"\n\n\n\n[volume_shader_bug.blend](volume_shader_bug.blend)\n\n", "Volumetric Clouds in Eevee not working | MacOs\n2018 MacBook Pro 32 GB 2400 MHz DDR4\n2.6 GHz Intel Core i7\nOperating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 20 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26\n\n\nBroken: version: 2.80 (sub 74)\n\n\nVolumetric Clouds in Eevee not working | MacOs\n\nWorks in earlier versions of blender 2.8 Beta\n[Nebula_ObjectVolume.blend](Nebula_ObjectVolume.blend)\n\n", "Volume disappear in Eevee when plug a texture\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 2.92.0\n\nVolume disappear when a texture is plugged into density or emission in principled volume shader, only in Eevee, woks fine in Cycles. I tried with Blender 2.91 / 2.92 / 2.93 and 3.0, same problem with all this version.\nI have also tried with my 2013 macbook with High Sierra and works fine. \n\nOpen attached blend file, in render mode plug and unplug noise texture.\n\nThanks! Have a nice day!\n\n[volumetric fog bug test eevee.blend](volumetric_fog_bug_test_eevee.blend)\n\n\n\n\n\n" ]

[ "Transform Node Messes Up Alpha Channel Manipulation\nArch Linux\nNvidia 750ti\n\nBroken: 2.79 (Tried 2.8 as well and I have the same issue)\n\nAs referenced here:\n4\n\nWhen I take an image in the compositor and scale it up 2x or whatever and then separate the RGBA and dilate/erode the alpha and use that to set the alpha on the image, it only works within the size of the original image and not the scaled up image. Also even if I use the R, G, or B, it still only uses the size of the original image and not that of the scaled up one.\n\n\n\nCropped if I try to mess with the alpha after a transform.\n\n\nUncropped if I mute my changes to the alpha.\n\n\nAlso I believe that if you scale down\n\n[dilatecropissue.blend](dilatecropissue.blend)\n", "Hidden sockets in Compositor don't stay hidden when we duplicate any node or render starts\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nThis seems more like a cosmetic problem and is more a really small bug but it is nevertheless \nvery annoying - especially with big compositing setups.\n\n - > Hidden Sockets - hidden with CTRL-H are showing up and are not hidden anymore\n[6vWCy01EPQ.mp4](6vWCy01EPQ.mp4)\n\n\n\n - - Create Renderpasses with more then 3 Outputs\n - - open up CompositorEditor \n - - Press CTRL - H twice to hide all unconnected sockets\n - - hit Render or duplicate any node\n\n", "Doubled Animation Render Output using only File Output Nodes\nWindows 7\n\nBroken: 2.79. 5bd8ac9,\nWorked: presumably never?\n\n**Short Explanation**\nWhen rendering an animation while using compositing output nodes, you get doubled output because of the \"write_still=True\", when the \".base_path\" of the output nodes and \"bpy.data.scenes[\"Scene\"].render.filepath\" differ.\n\nIn a new scene, go into the node editor, tick on \"use nodes\" and switch to the \"compositing nodes\" view.\nReplace the \"Composite\" node with a \"File Output\" node.\nChange its base path to \"[...]\\folder1\"\n\nGo into the \"properties\" area, into the render tab.\nUnder \"output\", change the folder to \"[...]\\folder2\"\n\nRender an animation, you will get an output in both folders.\n\nI would suggest turning off the properties panel output path when \"use nodes\" is True and output nodes are present?", "Graph Editor - Multiple Windows Problem\nOperating system: Windows 10 - 64\nGraphics card: Radeon RX 5500 XT\n\nBroken: 2.93.0\n\nI split my single Blender window to two Graph Editor/Node Editor & 3D Viewport for my multiple screens. If my mouse hovering anything but node editor(Include Graph editor or 3D Viewport) and I press play that timeline cursor like starts twitching.\n\nCreate two different windows. Graph Editor and 3D Viewport. Than press play on 3D Viewport window selected.\n\nTest file:\n[Bugfile.blend](Bugfile.blend)\n\nVideo:\n[2021-06-10 15-35-41.mp4](2021-06-10_15-35-41.mp4)", "Sculpt Mode: Edit Voxel Size hotkey conflict\nOperating system: Win 10\n\nBroken: blender-2.90-51ac411ce80c-windows64\n\nThe \"Edit Voxel Size\" and the \"Repeat Last\" functions are using the same hotkey (Shift+R), and as a result, the \"Repeat Last\" command is not working in sculpt mode.\n", "Zoom to mousepos makes 2D Views pan after zoom limits are reached\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\n\nOnce the zoom limit is reached, the view starts to pan rather than stop.\n\nIt was reported #43554 and fixed for `zoomstep` in 6b107daf23c5 earlier, but not for `zoomdrag`.\nThe same fix can be applied to `zoomdrag` as well.\n\n- Enable \"Zoom to Mouse Position\" preference\n- In Node Editor, zoom with Ctrl + MMB-drag, or Ctrl + trackpad-pan\n- When the zoom limit is reached, the view will start panning\n\n", "Nishita sky node is noisy when using 0° sun size\nOperating system: Win10\nGraphics card: RTX 2080 Super\n\nBroken: 3.0\n\n\nTitle self explanatory\n\n\n I believe this has to do with world sampling settings but there's no way to fix the noise\n\n\nI made a small file where frame 1 is noise and frame 2 is not (due to the sun size changing)\n[Bug report.blend](Bug_report.blend)", "File Output node outputs incorrect dimensions in some cases\nOperating system: Linux 64-bit\n\n2.92\n\nWhen connected to certain composite node trees, the File Output node will output images with incorrect and unexpected dimensions. This appears to have something to do with the blur node, but I suspect the issue might occur with other nodes that alter the image buffer dimensions.\n\n[composite bug.blend](composite_bug.blend)\n\n - Open and inspect attached file\n - Adjust output file paths to whatever is convenient\n - Render a frame\n - Review the outputted image\n\n", "Geometry Nodes: 3D Viewport Overlay Statistics don't respect Viewer Node\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.4.0 Alpha\n\n\nThe geometry output by the preview node is not taken into account by the overlay scene statistics:\n[2022-09-30 11-35-43.mp4](2022-09-30_11-35-43.mp4)\n", "Grease Pencil: smaller objects have an export SVG-PDF Issues\nOperating system: Linux-4.15.0-144-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 5500 (BDW GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 3.0.0 Alpha\n\nI found an issue on the scale for smaller objects when they it is exported to SVG or PDF from new Grease pencil feature and LineArt. This was modeled in millimeters (0.001) and this is what happen when is exported. the bounding box is X84.6 Y35.3 Z78.2\n\n\nAnd this is the same object exported scaled up to 1000\n\n\n\n\n[tattoo-machine_Eevee.blend](tattoo-machine_Eevee.blend)\n", "Blender 3.5 Image editor does not fully refresh on some zoom levels while painting\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.1\nWorked: 3.3.2\n\nBlender 3.5 Image editor does not fully refresh on some zoom levels while painting\n\n\n- Open attached file\n- Scribble on the top left image editor\n- On 3.4.1, 3.5.0 and 3.5.1, the image editor being painted doesn't seem to update the view fully, both only below that uv seam line, and 3.5.0 had more portions that aren't updated compared to 3.5.1.\n- Zoom in/out, it refreshes back to normal.\n\nNote:\n\n- This only happens on some particular zoom levels, sometimes I can get a lower zoom level to produce this error too, by zooming in and out and draw, you could probably find some more zoom levels where the image update region isn't complete.\n- When you zoomed out to some level and it works, and then you could zoom to some other level it could fail again.\n\n| 3.3.2 (correct) | 3.4.1 | 3.5.0 | 3.5.1 |\n|--|--|--|--|\n|  |  |  |  |\n\n------\n\nOriginal description:\n\nWhen zoomed in at a particular level the real time properties of the image editor stop working, In the short video i sent I am painting a texture using the Image editor window, it updates the texture on the model and the UV editor below, but the image editor window doesnt update until I either zoom in or zoom out, At first I thought it was random but then I found it can be easily replicated by simply being zoomed in at the level that I was when the bug was happening.\n", "Moving reroute nodes with click-drag behaves unpredictably\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.1.0 Alpha\n\nThe recent builds of Blender 3.1 add an option to finally move reroute nodes with mouse only, like any other node types. Unfortunately, there is no pre-selection highlight to let the user know which action they are about to perform on click-drag action. According to the anti-features page, pre-selection highlight section, if such feature does not behave reliably and predictably, it should be reported as a bug: AntiFeatures \n\nThis is why I am reporting it as such.\n\n[2022-01-24 11-25-05.mp4](2022-01-24_11-25-05.mp4)\n\nCurrent implementation suffers from following issues:\n1. The circular area/radius where move operation occurs is not visible. It is not visible how far from the reroute node position the node can still be transformed.\n2. Click dragging slightly outside the reroute node circle will still result in node wire drag rather than transform, further adding to the confusing behavior.\n3. It is not obvious that the click-drag transforms works **only** when the reroute node is selected first, which is inconsistent with click-drag transform behavior of the other nodes.\n\n1. Add a reroute node to any node graph\n2. Select the reroute node\n3. Click-drag around near the reroute node in various distances\nResult: What happens when LMB click dragging near the reroute node is not reliably predictable\nExpected: Outcome of LMB click-drag input operation near a selected reroute node can be reliably predicted\n\nProposed solution:\nWhen the reroute node is selected, and therefore can be transformed, draw a simple transform gizmo representing the screen area, which results in the transform operation when click-dragged, but only for reroute node closest to the mouse cursor, and only when the mouse cursor is near it (the same the scrollbars are dynamically drawn only in the close proximity of the mouse cursor):\n", "UVEditor: Add developer option to show vertex, edge and poly indexes.\nSimilar to the 3d viewport we should add option to show the vertex, edge and poly indexes to the uv editor.\n\nWithout I have looked to close to the current code-base this should be possible by adding the option to the UVEditor overlay and some tweaks in the overlay engine. \n\nCurrent work-around is to use a split screen.\n\n", "Drawing size of particles not matching DPI\nOperating system: MacOS\nGraphics card: AMD Radeon Pro 450\n\nBroken: 2.83\nWorked: N/A\n\nWhen moving the blender window to the external monitor, the halo size of the particles changes, which can cause them to disappear.\nBest way to see what I mean is to watch this short clip of me moving the window, and also zooming in and out to show that not all colors are lost: Vu6MSHVxEUwYLvob8\n> In #82238#1283352, @jenkm wrote:\n> The problem here is with the `U.pixelsize` or something like that, as usual.\n> \n> When you move a window between Low and High DPI screens, the size of the spheres does not change correctly.\n> It seems that the size changes twice, like the UI scale plus the size of the spheres additionally.\n> \n> | Low DPI Screen | Moved to High DPI | Low DPI with Thick \"Line Width\" |\n> |  |  |  |\n> \n> And further, depending on the size, these spheres can be hidden by a mesh.\n> \n> | Thick | Default | Thin |\n> |  |  |  |\n> \n> The size of the spheres should not depend on `U.pixelsize`, first of all.\n> The visibility of these spheres also depends on the viewing angle, what is also not clear whether this is intentional or not.\n\n\n- Open attached file\n- Update the particles if needed\n- Move the window to another monitor with different DPI\n||\n| -- | -- |\n[particles.blend](particles.blend)\n\n---\n**Complex file:**\n[rain.blend](rain.blend)", "Redo panel overlaps part of the interface\nIn the image editor, the redo panel covers part of the pixel values. \nWould be nice if such panel could be dismissed, or if it would take into account the possible presence of the pixel value subheader.\n\n[open_image_overlay.mov](open_image_overlay.mov)" ]

[ "Zooming in the shader editor is 3 times slower than zooming out\nOperating system: Windows 10\nGraphics card: GTX 1070\n\nI am using Blender with a large Wacom tablet, and zooming in inside the shader node editor seems to be very painful. The zoom in and out speed is fine when one uses a mouse wheel. However dragging to zoomin seems to be an issue/\n\n\nBroken: 2.82 (sub 6), branch: master, commit date: 2020-02-11 14:45, hash: c939b4df18e9, type: Release\n\nWorked: (optional)\n\nZooming in inside the shader editor is 3x+ times slower than zooming out.\n\n\n**Exact steps for others to reproduce5 the error**\nPlease see the attached video\n\n[zoom.mp4](zoom.mp4)", "Can't zoom on 2D canvases by moving mouse left or right with ctrl+mmb\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\nBroken: version: 2.81 (sub 4)\nWorked: 2.80\n\nIn 2.80 you could zoom on 2d canvases like the UV editor or the node editor holding Ctrl+mmd and moving the mouse left or right, or up or down, from the starting point\n\nIn 2.81 you can only zoom moving it up or down, left or right doesn't work. This makes it harder with tablets\n\nOn top of that, in the node editors, zooming in is slower than before and slower than zooming out, so if you zoom back and forth by moving the cursor between the same two positions, it averages to less zoom instead of zero zoom, which also happens on 2.80 but at a much slower rate\n\nOpen a new file, go to the shader editor and try zooming with ctrl+mmb, moving the cursor either side to side and up or down. Compare with 2.80\n\n", "UI: Zooming out in any editor/area its a lot faster than zooming in (exept the 3D view)\nOperating system: Linux-5.3.0-29-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 2)\nWorked: never worked properly in 2.8x\n\nUsing Ctrl+MiddleMB we can zoom in and out in a lot of areas from editors to toolbars, however zooming out goes a lot faster than zooming in, for example the 3D view works fine but not the toolbars or properties shelf. \nSorry for the video but i don't have a better way to explain it \n \nWYdW96oN7z0\n\n\nTry to Zoom in any toolbar or the properties editor using Ctrl+mmb and look carefully how much do you move the mouse up and down. \n\n" ]

[ "Add modifier error message for attribute name clashes\nIf user has a UV and a vertex color groups with the same name things behave in non predictable ways.\n\nThe nodes modifier should check for this and add an error message when this happens.", "Translation disambiguation requests\nTranslators may provide their issues in comments below with a precise description (where/what [in the UI and PO messages], and what are the different meanings behind the same English word that are the problem).\n\nA solution will then be decided (or not :/) on a case by case basis (using an existing i18n context, adding new ones, or simply tweaking the original UI message).\n\n--------\n\n## Current Known Issues\n\n*Addressed issues will be erased after every release to clean things up.*\n\n\n### Non-translatable\n\n- [ ] **Render View**: slot 1-8 default render slots names\n\n- [ ] **Timeline Editor > Keying > Active Keying Set**: all built-in keying sets show in English in the dropdown\n\n- [ ] **Data-block types** in the file browser list and file path, when linking or appending data blocks [D15995](D15995)\n\n- [ ] Many **modal keymaps** (e. g. \"3D View > Mesh > 3D View Tool: Edit Mesh, Extrude Manifold\"): see #105548\n\n\n### Disambiguate\n\n- [x] **Path** !108213\n - a location (in a file system, blender datablock, etc.)\n - a trajectory (of an object, particles of a system, etc.)\n - in the context of particles appears in the Render > \"Render As\" dropdown option (and respective Options Panel Title).\n\n- [x] **Front/Back** meaning either: 'put something at the front/back' or 'the front/back face of something'. (perfect example of this is seen in the Empty Image options, you have Depth and Side, both using the same strings for their options, which shouldn't happen) !108213\n\n- [ ] **Smooth** meaning either: 'something is smooth' or 'to smooth something'.\n- [ ] **Add** meaning either: 'the Add blend mode / boolean-type operations' or 'to add a new object'.\n- [x] **Flat** Projection method / Mesh plane (material preview) / Blur type !111146\n- [ ] **Normal** Normal Direction / Usual, typical, default / Color blend mode\n- [ ] **Marker** (timeline, tracking)\n\n- [x] **Shear** meaning either: “to apply shear” or “property of being sheared”\n\n\n- [ ] **Value** can mean a constant value or a color lightness. However, the Separate and Combine nodes use labels and cannot be disambiguated for now. See #105113\n\n#### Issues to check\n\n- [ ] **Clip Start** / **Clip End** Camera view / Light distance\n\n- [ ] **[Power](43295#issuecomment-642674)**\n```\n#. :src: bpy.types.CopyScaleConstraint.power (strength)\n#. :src: bpy.types.CompositorNodeColorBalance.power (strength)\n#. :src: scripts/startup/bl_ui/properties_physics_common.py:343 (strength)\n#. :src: scripts/startup/bl_ui/properties_physics_field.py:242\n#. :src: scripts/startup/bl_ui/properties_physics_field.py:281\nmsgid \"Power\"\nmsgstr \"Cường Độ/Năng Lượng/Sức Mạnh/Lũy Thừa\"\n```\n\n- [ ] **[End](43295#issuecomment-642682)**\n\n\n- [ ] **Gender problems**: in several languages adjectives need to match the gender of the subject they describe, some of the more repetitive cases in the UI are seen regarding adjectives like:\n - Default, None and Fixed.\n- [ ] **Number problems**:\n - In several cases things like All and New should be plural (at least in Spanish), so being separated from other things 'singular' that use the same string would be good.", "Additional unwanted objects being created when asset browser asset is used\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA RTX A4500/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.5.0\n\nAdditional duplicate (unwanted) objects being created when using assets from the asset browser.\n\nI haven't managed to consistently reproduce how I get this issue to happen. However, I have attached files which are guaranteed to demonstrate it.\n\n1. The oxford-straps-demo.blend file contains the source meshes which are placed in a collection and marked as asset called \"Source Asset\"\n\n2. The test-asset.blend file contains the \"Source Asset\" dropped in as Linked then Library Overridden. That itself is then marked again as an asset called \"Test Asset\". (This is my workflow - I would do this, then add materials at this stage).\n\n3. Open a new blend file and drop in the \"Test Asset\" (with Append). You will see the appended asset plus two other unwanted objects which are duplicates of the objects contained within the sealed asset.\n\nI have to delete these every time the asset is used.\n\n", "Double click list renaming not working on heavy scenes\nVista64, 2.7a, gtx470\nWhen the scene is heavy, so that interface becomes slightly laggy, double click list rename stops working, especially for fast clicking.\n\n - Add subdivision modifiers to any mesh until interface becomes laggy.\n - Add a vertex group or UV map.\n - Double click to rename - renaming is not activated.\n", "Simplify duplication options in user preferences.\nCurrently we have one duplicate option for each and every object data type (in user preferences, 'Editing' section, 'Duplicate Data' panel).\n\nTopic of this task is whether we should keep things like that, or if we should rather simplify options by defining 'categories' instead.\n\nCategories could be:\n* Geometry *(meshes, curves, surfaces, fonts, mballs, lattices, armatures, gpencil)*\n* Physics *(hair, pointcloud, volume, particles)*\n* Lights *(lamp, lightprobe)*\n* Actions *(actions)*\n* Shading *(materials)*\n* Camera *(cameras)*\n* Speaker *(speakers)*\n\nThis could also include better handling of 'new' things, e.g. duplicating (deep copy) of geometry nodes when 'Geometry' is enabled, duplicating (deep copy) of shading nodes when 'shading' is enabled, and so on.\n\nNOTE: this was triggered by #90638 (Inconsistent object data behavior when link-duplicating collections.) and its fix 65dbeb1d81, which required adding three new options there to fully cover all current object types...", "Polishing Correct Face Attributes\n- [ ] Initialize operators options based on the \"correct face attribute\" value (e.g., edge slide).\n- [ ] Unify naming of the option and the operator options.\n\nThe way we do Proportional Editing seems to be a good example to follow. These issues have been raised on 4387aff", "Pixar USD export does not follow API spec for camera units of attributes like focalLength\nBroken: blender-2.93.5-candidate+v293.ae1a57a05eed-windows.amd64-release\n\nPixar USD export for camera units does not follow API specification\nclass_usd_geom_camera.html#a911505cf224b975546bc2ea5505a041e\n\nOpen blender\nFile->Export as Universal Scene Description \nSave as test.usda\nopen text.usda in text editor and view camera definition\n\nIn Camera prim, note that prim attributes focalLength, horizontalAperture, horizontalApertureOffset, verticalAperture, verticalAperture are written out in mm units. As per the API class_usd_geom_camera.html#a911505cf224b975546bc2ea5505a041e the units should 1/10 of the world unit therefore focalLength should be 0.50 (aka decimetre or 0.1m units) when metersPerUnit=1\n\n```\n def Camera \"Camera\"\n {\n float2 clippingRange = (0.1, 100)\n float focalLength = 50\n float horizontalAperture = 36\n float horizontalApertureOffset = 0\n token projection = \"perspective\"\n float verticalAperture = 20.25\n float verticalApertureOffset = 0\n }\n```\n\n\nHere is an example from Houdini's USD export for a 35mm focal length\n```\n def Camera \"camera1\"\n {\n float2 clippingRange = (1, 1000000)\n float focalLength = 0.35\n float focusDistance = 4.4\n float fStop = 2.4\n float horizontalAperture = 0.20955\n float horizontalApertureOffset = 0\n token projection = \"perspective\"\n double shutter:close = 0.25\n double shutter:open = -0.25\n float verticalAperture = 0.1571625\n float verticalApertureOffset = 0\n }", "BLI_path_util_test.cc TODO's\nThis is an area we have some tests setup, so its just a matter of adding remaining tests.\n*This is a relatively easy place to start and good for newer developers*\n\nNote, with these string functions typically the common cases are well tested, but the corner cases can trip us up, so be sure to include tests for empty strings, utf-8 with multi-byte characters, strings containing all path separators - the kinds of cases that may be overlooked.\n\nDone:\n\n- BLI_cleanup_path\n- BLI_path_frame\n- BLI_split_dirfile\n\n\nTODO:\n\n- BLI_split_name_num\n- BLI_make_file_string\n- BLI_path_suffix\n- BLI_path_frame\n- BLI_path_frame_range\n- BLI_stringdec, BLI_stringenc --- check they are compatible\n- BLI_path_abs\n- BLI_path_rel\n- BLI_join_dirfile\n\n- BLI_replace_extension\n- BLI_ensure_extension\n- BLI_ensure_filename\n\n*Note, its probably unreasonable to attempt to test all these functions as a single patch, so fine to submit tests for only a few*", "Make Local feature is undocumented\nBroken: version: 2.83.0\nWorked: Never\n\n**Description of error**\nMake Local feature is undocumented\n\nRight click on collection -> \"ID Data\" -> \"Make Local\" <---- no action (not intuitively obvious what the action would be)\n\n", "Multi-Object-Mode: EditMesh Tools\nNote, while these follow menus, duplicates have been removed.\n\n## Remaining\n\n- MESH_OT_select_similar_region ([D3672](D3672))\n- MESH_OT_knife_project (leave aside for now, too complex - see [D3637](D3637))\n- MESH_OT_knife_tool (leave aside for now, too complex - see [D3637](D3637))\n\n\n## Mesh Menu:\n\n- ~~MESH_OT_duplicate_move~~ 1ade071052\n- ~~MESH_OT_extrude_edges_indiv~~ d8f70a26fd\n- ~~MESH_OT_extrude_faces_indiv~~ 07774d4860\n- ~~MESH_OT_extrude_verts_indiv~~ 7c415e6fd7\n- ~~MESH_OT_extrude_edges_move~~ 1d7bdbd273\n- ~~MESH_OT_extrude_vertices_move~~ 1d7bdbd273\n- ~~MESH_OT_delete_loose~~ bfc9d426bb\n- ~~MESH_OT_decimate~~ 5b45d32f3a\n- ~~MESH_OT_dissolve_degenerate~~ (initial comsmit) bfc9d426bb\n- ~~MESH_OT_dissolve_limited~~ 09e14cb5bc\n- ~~MESH_OT_face_make_planar~~ 0e5a4f927a\n- ~~MESH_OT_vert_connect_nonplanar~~ b942106c73\n- ~~MESH_OT_vert_connect_concave~~4043e4b820\n- ~~MESH_OT_fill_holes~~ 69b95b45f4\n- ~~MESH_OT_symmetrize~~ 03a916e5b5\n- ~~MESH_OT_symmetry_snap~~ 7f9768cb80\n- ~~MESH_OT_bisect~~ f9eb2f29fe\n- ~~MESH_OT_sort_elements~~ ffb424c85f\n\n## Snap Menu:\n\n\n- ~~VIEW3D_OT_snap_selected_to_grid~~ 016ba0f38b\n- ~~VIEW3D_OT_snap_selected_to_cursor~~ ec3357e03a\n- ~~VIEW3D_OT_snap_selected_to_active~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_selected~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_center~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_grid~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_active~~ (no change required)\n\n\n## Vertex Menu:\n\n- ~~MESH_OT_merge~~ b73c7381cc\n- ~~MESH_OT_remove_doubles~~ 22b2bab702\n- ~~MESH_OT_rip~~ 9d0d7c375e\n- ~~MESH_OT_rip_edge~~ 6539c1fc41\n- ~~MESH_OT_split~~ fc8d903000\n- ~~MESH_OT_separate~~ 5e915baec4\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_vertices_smooth~~ d915aa57f8\n- ~~MESH_OT_vertices_smooth_laplacian~~ 1f30232aa7\n- ~~MESH_OT_blend_from_shape~~ 6ae09dfcad\n- ~~OBJECT_OT_vertex_group_smooth~~ 3dee8b4a12\n- ~~MESH_OT_shape_propagate_to_all~~ 3a43528274\n\n## Edge Menu:\n\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_subdivide~~ (initial patch)\n- ~~MESH_OT_subdivide_edgering~~ 853e55b043\n- ~~MESH_OT_unsubdivide~~ e245f7c09c\n- ~~TRANSFORM_OT_edge_crease~~ (initial patch)\n- ~~MESH_OT_mark_seam~~ 61f0608b4a\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_edge_rotate~~ 66ffbf9b7d\n- ~~MESH_OT_edge_split~~ 207b549d40\n- ~~MESH_OT_bridge_edge_loops~~ eb2226dde2\n- ~~TRANSFORM_OT_edge_slide~~ (wrapper to other operator, working)\n- ~~MESH_OT_loop_multi_select~~ df49155cfb\n- ~~MESH_OT_loop_to_region~~ 8b41999ea0\n- ~~MESH_OT_region_to_loop~~ 56d65719b3\n\n\n## Face Menu:\n\n- ~~MESH_OT_flip_normals~~ 4704f2687a\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_fill~~ b726ff4fc4\n- ~~MESH_OT_beautify_fill~~ e42b8c32ab\n- ~~MESH_OT_inset~~ 570455fb83\n- ~~MESH_OT_bevel~~ d9e04cb594\n- ~~MESH_OT_solidify~~ f309c34cfe\n- ~~MESH_OT_intersect~~ dffd37877d\n- ~~MESH_OT_intersect_boolean~~ 46aec45b2a\n- ~~MESH_OT_wireframe~~ a0a78f6da4\n- ~~MESH_OT_poke~~ 3a9669bfff\n- ~~MESH_OT_quads_convert_to_tris~~ (initial patch bfc9d426bb\n- ~~MESH_OT_tris_convert_to_quads~~ (initial patch bfc9d426bb\n- ~~MESH_OT_face_split_by_edges~~ b6a822d726\n- ~~MESH_OT_faces_shade_smooth~~ e4c4e8566f\n- ~~MESH_OT_faces_shade_flat~~ 9fc0c0c3de\n- ~~MESH_OT_uvs_reverse~~ 63951bc987\n- ~~MESH_OT_uvs_rotate~~ faaffc4011\n- ~~MESH_OT_colors_rotate~~ 42c5c20e54\n- ~~MESH_OT_colors_reverse~~ 753be0a2a5\n\n## Mesh Toolbar: (should be added to menu)\n\n- ~~MESH_OT_loopcut~~ e87dd9aa00\n- ~~MESH_OT_convex_hull~~ e1cee0ac71\n- ~~MESH_OT_delete~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_delete_edgeloop~~ 49be803ad6\n- ~~MESH_OT_dissolve_edges~~ 7f5c469716\n- ~~MESH_OT_dissolve_faces~~ 848d9cda0e\n- ~~MESH_OT_dissolve_mode~~ (wrapper of vert/edge/face dissolve)\n- ~~MESH_OT_dissolve_verts~~ 5f59a8bb11\n- ~~MESH_OT_drop_named_image~~ b4d23818c8\n- ~~MESH_OT_dupli_extrude_cursor~~ 68a719f1ea\n- ~~MESH_OT_duplicate~~ 1ade071052\n- ~~MESH_OT_edge_collapse~~ 2349b9777a\n- ~~MESH_OT_edgering_select~~ 7fa77cd31d\n- ~~MESH_OT_edges_select_sharp~~ dd93c80747\n- ~~MESH_OT_extrude_region~~ 1d7bdbd273\n- ~~MESH_OT_extrude_repeat~~ 9a125ca5fe\n- ~~MESH_OT_faces_select_linked_flat~~ 1bb9ccf887\n- ~~MESH_OT_fill_grid~~ 1cbe3b6e03\n- ~~MESH_OT_hide~~ 5d8937e8ba\n- ~~MESH_OT_loop_select~~ 7fa77cd31d\n- ~~MESH_OT_normals_make_consistent~~ 266638d783\n- ~~MESH_OT_offset_edge_loops~~ efd843b51c\n- ~~MESH_OT_reveal~~ f4c1685a16\n- ~~MESH_OT_screw~~ badd88ca02\n- ~~MESH_OT_select_all~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_axis~~ c899f21800\n- ~~MESH_OT_select_face_by_sides~~ 90c9458b2f\n- ~~MESH_OT_select_interior_faces~~ e161c51e7f\n- ~~MESH_OT_select_less~~ b6a7fa1880\n- ~~MESH_OT_select_linked~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_linked_pick~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_loose~~ eacb2eb423\n- ~~MESH_OT_select_mirror~~ 3ebe389605\n- ~~MESH_OT_select_mode~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_more~~ 2309131b4d\n- ~~MESH_OT_select_non_manifold~~ 4da2aec2bb\n- ~~MESH_OT_select_nth~~ 63c2397171\n- ~~MESH_OT_select_random~~ 847f028b71\n- ~~MESH_OT_select_similar~~ 75b2091d42\n- ~~MESH_OT_select_ungrouped~~ 1d8e6c5cd0\n- ~~MESH_OT_shortest_path_pick~~ c32cc3e43e\n- ~~MESH_OT_shortest_path_select~~ 5a431be629\n- ~~MESH_OT_spin~~ ab8dded330\n- ~~MESH_OT_vert_connect~~ 944054fbb6\n- ~~MESH_OT_vert_connect_path~~ fc7316fb54\n", "Cycles: add feature overrides\n[D4255: Cycles: Added feature overrides](D4255)", "Renaming an ID through RNA does not consistently increment OTHER or CURRENT ID in case of name collision\nRenaming an ID through RNA does not consistently increment either the current ID or the other ID in case of name collision. This depends on the existing order of the data-blocks before the rename happens.\n\nAs pointed out in the comment below by @ideasman42, fixing this in one way or the other is trivial. But we have to choose one of the two solutions:\n* Add incremented number suffix to renamed ID (this seems to be the soundest solution, as it will ensure we never silently rename a random other ID).\n* Add incremented number suffix to the other ID.\n\nNote that it should also be ensured that behavior is consistent with Outliner renaming code as well.\n\n------------\n\nOriginal Report\n-----------------\n\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nwhen we try to rename an object with an already used name,, it will rename the existing occurence, not the incoming one\n\nworks with the default scene (with Cube, Light, Camera) :\n- take the Cube, x2 clic on the name, rename it in \"Camera\". Enter\n- the original Camera (previously named \"Camera\") will be renamed in \"Camera.001\" and the Cube will be renamed in \"Camera\"\n\nI gess it should be the opposite : the incoming similar name is incremented, but the original name stays the same\n\n", "Wrong object naming when using context.copy\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.29\n\nBroken: version: 2.93, 3.6, 4.0\nWorked: none\n\nWhen duplicating an object with a parent and using context.copy() with the object.duplicate or any other operator that uses object.duplicate the child object to get a wrong name.\n\n\n1. set one object as a parent of another\n2. select both objects (parent and child)\n3. run this code in the Text Editor\n4. now take a look in the outline the duplicated parent is selected, but the origin child is also selected and the name of the origin child has changed\n\n```\nimport bpy\nbpy.ops.object.duplicate_move(bpy.context.copy())\n```\n- - -\n```\nimport bpy\n\nwith bpy.context.temp_override(**bpy.context.copy()):\n bpy.ops.object.duplicate_move()\n```\n\n\n\n| Before | After |\n| -------- | -------- |\n|  |  |", "Add option to re-use or duplicate data for the Current File asset library\nAgreed on this alternative to [D12752: Asset Browser: Hide Import Types menu for \"Current File\" asset library](D12752). Currently dragging in data from the *Current File* asset library always reuses the existing ID. The option to duplicate the data could be quite useful and make it explicit what dragging in the asset will do.", "File Browser: Can't Select/Delete Favorites Bookmark When File Path Is Missing\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nCan't select/delete an existing Favorites Bookmark in the Blender File Browser if the path no longer exists on your OS. You have to recreate the path to enable select/delete again.\n\n1. Create a Favorites Bookmark in the Blender File Browser that links to a folder on your OS.\n2. Close the Blender File Browser.\n3. Delete the folder in your OS the Bookmark links to.\n4. Open the Blender File Browser.\n5. The Bookmark is now gray and can't be selected/deleted. (Hovering over the link does show the original path.)\nTo reverse this:\n1. Close the Blender File Browser.\n2. Recreate the original path in your OS the bookmark originally linked to (see 5 above).\n3. Open the Blender File Browser.\n4. The Bookmark can now be selected/deleted.\n\nNOTE: A limited workaround was added some years ago (the 'Cleanup' option that will remove all invalid entries)" ]

[ "Import and Export options look identical in contexts besides the File menu, such as QuickFavorites. (Low priority)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nBroken: version: 2.93.0\n\n**Short description of error:**\nThe *import* and *export* buttons for the same file types are identical, and indistinguishable if these buttons are found in some other contexts, for example the QuickFavorites menu.\n... I understand that it's easier to see than to communicate. \n\n - Start from any template\n - Right-click the button for File > Import > STL, add to QuickFavorites\n - Do the same for Import\n - Open QuickFavorites now (Q)\n - Notice that you cannot tell which one is import and which is export without the tooltips.\n\n\n\n\n\n" ]

[ "In Face-select Mode, Hiding unselected doesn't hide loose edges\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 400 Intel 4.4.0 - Build 20.19.15.5070\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\nI don't really know if it is a bug or a limitation but Loose edges are not hidden when hiding unselected in face select mode.\n\nOpen the attached blend file and hit Shift+H with the selected face. It doesn't hide the loose edges.\n[Bug test.blend](Bug_test.blend)", "Edge Sliding With Snap in Edge/Vertex Mode is Inconsistent.\nOperating system: Linux-5.19.0-42-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.1\n\nEdge sliding in vertex or edge mode behaves like it is in edge perpendicular mode. This is very inconsistent because it snaps as expected in face project mode. Also in edge mode, depending on the edge being snapped to, the snapping mode will either be as expected or in edge perpendicular mode.\n\n\nFrom the blend file try to snap the selected edge to the pink edge in edge or vertex mode. Then try snapping to the annotated geometry as per the mode described in the text editor:\n\n\n", "Copying in edit-mode copies the entire object, not the selection\nthere is an issue occurs when a part of (mesh) is copyed in the edit mode \nwhat happens when copying one part of a (mesh) and pasting it\nyou suppose to get this part only pasted ,but instead you get the whole (mesh) pasted\n\nfor examble if you have a cube model with a single face selected in the edit mode \nif you copyed then pasted it the result is the whole cube modele is pasted rather than the single face \n \n \n\n", "'Dissolve' operator leaves inconsistent selection\nBroken: 2.82 (62d131e962d6e0a4f39db98d4f89243c16c55779) (down to, and including, 2.79)\nWorked: N/A\n\nAfter dissolution of edges in Edge selection mode, some vertices not connected with edges remain selected (which is indicated by a tool gizmo, Verts readout in the status bar, and verified by switching to Vertex selection mode).\n\n1. In a empty scene, add a mesh Grid.\n2. Switch to edit mode and Edge selection mode.\n3. Select one edge somewhere inside the grid (not on border).\n4. Dissolve it via the Delete -> Dissolve Edges or a default shortcut Ctrl+X.\n5. Verts readout in the status bar should show 2 selected vertices (despite you being in edge mode with no edges selected).\n6. Switch to Vertex selection mode: the two verts from that dissolved edge are still selected.\n7. Deselect all, switch to Edge selection mode and box-select one square at the corner of the Grid.\n8. Dissolve edges as in (4).\n9. Note that this time, Verts in status bar only shows one selected vertex: switching to Vertex mode would reveal it's the corner one.\n\nIt would seem that the vertices do remain \"selected\" for operators as well: after (4) or (8) you can transform those verts using a gizmo or shortcuts, extrude them (with strange results), connect them using Fill or Connect Vertex Path, and delete them (even though you're in Edge mode).\n\nUpdate: Video demo [here ](FAfhSU2AdbQ).", "Delete Geometry node face mode behaves unexpectedly when used after Join Geometry\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.2.1\nWorked: N/A (problem exists on 3.1.2)\n\n\nNot sure if this is by design, but I find that the following behaviour unexpected:\n\n- By itself, a Mesh Line output connected to Delete Geometry + Geometry Proximity node using Face mode won't delete anything.\n- However, when such a Mesh Line is joined with a Grid primitive, then Delete Geometry + Geometry Proximity in Face mode will cause all of Mesh Line to be deleted, regardless of distances.\n\n\n\n\n\n\n\n\n- Download the blend and observe Mesh Line is preserved.\n- Unmute Grid node link to Join Geometry, and observe Mesh Line is now gone.\n\n[line-deletion.blend](line-deletion.blend)\n", "Spin / Screw Adjust Last Operation: using the slider after having reset the axis will constantly pop up `Invalid/unset axis` [hard to escape]\nWindows 10\nNvidia mx 150\n\nBlender 2.9\n\nBlender starts to loose control in some functions when i press make some values to \"Zero\".\n\n1. Make a plane. goto edit mode and select face.\n2. Press \"Alt+E\" and select \"Spin\" option.\n3. Goto Last action menu, hover over the axis X value and press \"Backspace\" to make all values to zero. Error popup `Invalid/unset axis` comes up (which is correct)\n3. note here that Backspace seems broken [or intentionally disabled in recent builds], so it might be neccessary to set axis to zero \"by hand\"\n4. Now try to change the spin \"Steps\" using the slider (arrow keys are OK) and it will \"hang\" (as in: Error popup will follow the mouse) and you will have to hit ESC multiple times or force close blender.\n\n[#81042.webm](T81042.webm)", "Alpha channel of Textures can't be deactivated in UV Editor\nOperating system: Windows10\nGraphics card:Geforce GTX 970M\n\nBroken: 2.91.0\nWorked: 2.83.0\n\nWhen you load an Image/Texture with an alpha channel in the UV editor, you can't turn the alpha channel off anymore, the image will stay black.\nIt worked in older Versions from 2.80 up to 2.83, there you only have to click on **Color** in **Display Channel** options.\n\nOnly areas that aren't black in the Alphachannel will be visible, in my examples I work with textures that need an all black Alpha channel.\n\njust load any Texture with Alpha channel in UV editor viewport\n\n\n\nHere an Screenshot from Blender 2.83.0 where it worked\n\n\n\n\nand here an screenshot of Blender 2.91.0, the same Texture is used, I also tried different settings under Image, but nothing works\n\n\n", "UV: Add 3D Gizmos for UV projections, Cube, Cylinder and Sphere projection\nThe \"Unwrap > Projection\" operators are powerful, but would be even better with artist control over exact placement in 3D space.\n\nPropose to add gizmos in the 3D viewport to allow precise artistic control over the cube, sphere and cylinder.\n\nConsider adding Planar Projection as well.\n\nThanks @BlenderBob for the suggestion!\n\n", "Graph Editor Expand/Collapse Channels collapsing happens on all hierarchy levels at once [Outliner doesnt do this, expanding is also one step at a time]\nOperating system: Mac 10.15\nGraphics card: \n\nBroken: 2.90.0\nWorked: never\n\n(This might be considered a feature request, it would be consistent with the Outliner though)\nIn the Graph Editor when working on the left panel and use '+'/'-' keys on Numpad, the '+' is working well, it opens the collapse levels one each time, but the '-' is collapse all the level in one time. It is not convenient when having lots of things in this panel.\n\n[Screen Recording 2020-09-13 at 22.22.54.mov](Screen_Recording_2020-09-13_at_22.22.54.mov)", "UV: Mesh won't Unwrap at all\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nWhat is happening is that when i unwrap my mesh nothing happen, even if i isolated one face and tried to unwrap it wont work, also even faces you extruded from the faulty face won't unwrap, but adding a new plane from the add menu inside the same mesh unwraps normally, even if i connected the plane to the faulty face.\n\n1. Create a plane.\n2. Give one edge a Mean Bevel Weight from the side bar.\n3. Give the plane a Bevel Modifier and the Limit Method set to Weight (visually nothing will change since its just a plane but the error will still reproduce).\n4. Apply the Modifier and Unwrap the plane. (normally the plane comes unwrapped by default, try changing the UVs out of bounds or scale them down just so you can notice the change ).\n\nThanks you blender developers.", "straighten edges and unfold uv island\nStraighten selection and unwrap unselected vertices\n\n**Starting point**\n\nThe uv has pretty wonky topology. \n\n\n\n\n**Desired result**\n\nThe selection is straightened and the non selected uv’s of the UV island is unwrapped. Should work on multiple uv islands\n\nSuggested approach:\n- Store\n - Original pinning\n - Original seams\n- Run “seams from islands”\n- Remove all pins\n- Pin selection\n- Align auto on selection\n- Unwrap\n- Restore \n - Original pinning\n - Original seams\n\n\n", "Edge Slide: Vertices leave path when using with Mirror Modifier's Clipping Option\nOperating system: Linux-5.8.14-arch1-1-x86_64-with-arch 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.28\n\nBroken: version: 2.91.0 Beta\nSame in Stable Release. (And with Factory Settings.)\n\nWhen edge sliding, vertices diverge from their path as they hit the clipping point. (See the short video)\nI would expect the vertices to just stop at the intersection point. Otherwise it is not possible join the vertices while maintaining the angle of the edges. (Not without a lengthy workaround at least.) \n\n[Peek 2020-10-23 15-40.mp4](Peek_2020-10-23_15-40.mp4)\n\n1. Set up one or multiple edges which aren't parallel to the mirror Axis.\n2. Add a Mirror Modifier and enable Clipping.\n3. Edge Slide the edges into the clipping plane. ", "Scaling in edit mode with individual origins and snapping activated is broken\nWin7 x64\n\nBroken: 2.76\n\nFollowing #39161. Scaling in edit mode works well with \"median\" as pivot point but with \"individual origins\" it breaks.\n\n\nIn attached file:\nScale and choose a vertex with \"ctrl\" pressed, cube seems to disappear.\nTo compare, press \"G\" and choose a vertex for snap, the cube's center is moved as a cube (also individual origins could make all selected verts move to that position making a point instead of a cube?) to that vertex.\nScale with \"median\" as pivot, it works\n[bug scale individual origins.blend](bug_scale_individual_origins.blend)\n\nSo maybe to make it consistent, make \"individual origins behave like median.\n", "Extra face dots in UV Layout editor (GPU subdivision OFF, On Cage OFF in Subdivision modifier make a difference)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4835\n\nBroken: version: 3.4.1\nBroken: version: 3.1\nWorked: not since GPU subdivision was introduced (so in a way, it was working in 3.0)\n\nExtra random faces appear in the UV Layout editor\n\n- I can mosty repro this if GPU Subdivision in Preferences > Viewport > Subdivision is OFF\n- It does not happen at all if I turn off `On Cage - Adjust edit cage to modifier result` on the SubSurf modifier.\n\nIn the attached file, toggle from face select mode to vertex select mode and back to face select mode. (Might have to repeat 5-6 times) Extra faces appear in the UV Layout editor. Also see here: [1457172]\n\n", "Eevee 'Principled Normal' connected to 'Normal Map' node is disabling 'Displacement'\nOperating system: Win 10\nGraphics card: 2x1080Ti\n\nBroken: blender-2.91.2-windows64, blender-2.93.0-420f538fadfd-windows64\nNever worked as long as I remember\n\nBasically connecting normal map to principled shader is disabling any displacement map connected to the output. Just unplugging normal from principled turning it on. I don't know if its a bug or is it intentional \n\nNormal and displacement plugged in - displacement not working\n\nNormal unplugged - displacement working\n\n\n- Open attached file\n- Compare the result in Eevee with Cycles\n[bump_test2.blend](bump_test2.blend)" ]

[ "Vertex Slide and Loop Cut and Slide tools breaks the UVs and Vertex Colors after topology changes [new or deleted] (if CustomSplitNormals are present)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.91.0 Alpha\nWorked: Blender 2.83 LTS\nCaused by 93c8955a7\n\nVertex Slide and Loop Cut and Slide tools breaks the UVs and Vertex Colors on new vertices, please see the video or the attached .blend file.\n[Blender_2.91_VetexSlideProblem.mp4](Blender_2.91_VetexSlideProblem.mp4)\n\n1) Open the attached file\n2) Press J to cut polygons between selected vertices\n3) Select new vertex\n4) Slide it with G G hotkeys\n5) If you Undo the Vertex Slide, you can slide it again without this problem, but as soon you create a new geometry -- it happens again\n6) Same happens with Loop Cut and Slide tool (Ctrl + R)\n\nThank you for checking out this bug!\n[Blender_2.91_VetexSlideProblem.blend](Blender_2.91_VetexSlideProblem.blend)", "Vertex slide messes up UVs\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 2.90.1\nWorked: 2.83.6\n\nSliding vertex along an edge using double tap G causes the UVs to distort and they remain messed up.\n\nUsing a mesh that has been unwrapped double tap G to slide the vertex along an edge. Intermittently the UV will get stretched (it looks like to infinity) and be messed up. It isn't an issue with every vertex and seems to vary depending whether there are pinned UVs or not. To get the screenshots provided I had to try several vertices before I could replicate the issue.\n\nThis happens on factory settings with no addons enabled.[Screenshots.zip](Screenshots.zip)\n\n[Bug.blend.zip](Bug.blend.zip)\n\n" ]

[ "Fluid simulation result not visible after reloading file\nOperating system: MacOs\nGraphics card: Intel Iris Plus Graphics 640\n\nBroken: 2.91\nWorked: -\n\nHello. After I opened project, that I closed before, the fluid simulation didn't exist. It is very easy, to know the issue. Thanks for attention.\n- New file\n- Quick liquid effect on default cube\n- Save file\n- Close Blender\n- Open the same file again\n- The domain is just a smooth shaded cube until you play the file long enough for it to loop back to the first frame.", "GPencil: Blender crash when GP3 enabled & you open the default 2D animation file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6\n\nBlender crash when GP3 enabled & you open the default 2D animation file & use the Draw tool\n\n- enable GP3 under the experimental features\n- save preferences and restart Blender\n- do File > New > 2D Animation\n- try to draw something.\n\nSince my 2D animation file is customized, I included it below.\n\n", "Blender crash on combining textures (intel)\nOperating system: Windows 10\nGraphics card: Intel HD Graphics 4400\n\nBroken: 2.93.2\nWorked:\n\nWhen I tried to combine 2 textures like this blender is crashing.\n  \n\n[Test.blend](Test.blend)\n[Test.blend1](Test.blend1)\n[system-info.txt](system-info.txt)\n[Test.crash.txt](Test.crash.txt)\n[2021-11-12 09-11-32.mp4](2021-11-12_09-11-32.mp4)\n", "Realtime Compositor - Crash on Mac when using Map UV node\nOperating system: macOS Ventura 13.3.1\nGraphics card: AMD Radeon Pro 5700 XT 16GB\n\nBroken: 3.6 alpha cef128e68af5 (2023-04-13 16:06)\n\nConnecting a Map UV node in Compositing will crash on macOS\n\nIn Blender's startup scene, enable Compositing by checking \"Use Nodes\".\nConnect a Map UV node between the Render Layers node and the Composite node.\nIn a 3D view, turn on Rendered viewport and set Viewport Compositing to Always.\nThis will crash (100% reproducible).\n\nPlease contact summary if more information is required.\n\n", "Blender crashes right after loading up a blend file or when creasing a specific mesh on a slightly older version of said blend file\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\nCPU: Ryzen 7 3700X\nRAM: 16GB, roughly 7GB available when loading\n\nBroken: version: 3.2.0\n\nFollowing a sculpting course i'm currently trying to crease the claws of a model in the attched blend file.\nBlender keeps crashing without further notice when doing so. I managed to save in the specific state that causes the crash, but can also reproduce it by creasing the front-left hoof/claw-thing in the older state\n\nLoad up file, change to sculpt mode without hiding linked duplicates (feet/hooves)\n[dog!.blend](dog_.blend)\n\nOld:\nLoad up attached blend file -> Crash immediately after apparently successfully loading the scene\n[dog!.blend](dog_.blend)\nLoad up attached blend1 file, crease said claw region with Dyntopo active -> Crash soon after doing so\n[dog!.blend1](dog_.blend1)", "File Browser: Blender freezes for half a minute when opening File Browser\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: 3.5, 3.6, 4.0\n\nIn Blender when I access a file that has a shortcut to my private cloud storage, which contains an IP address (\\192.168..*), Blender freezes.\nThe cloud storage is not running most of the time, so it could be that Blender is trying to read the folder but fails, because the storage doesn't respond (because it's turned off).\nGeneric Windows File Explorer does the same thing when I open the folder (but doesn't freeze ofc, just trying to load it until timeout).\n\n<video src=\"attachment\" controls></video>\n\nYou will need a shortcut-file that points to some address on the network that takes a long time to load.\nOne way I found to create a shortcut like this is by:\n- On a local network, access a file from a computer on the network and create a shortcut to that file\n- Shut down the network or the computer being accessed.\n\nNow that we have this shortcut-file, in Blender, just do this:\n- Open File Browser in any way (loading file, or texture, or click on File > Import > Wavefront (.obj).)\n- Go to the directory with the shortcut-file\n\nAfter some time, the files may finally appear and the delay disappears when accessed again.\nTo replicate the delay again, close and reopen Blender.\n\n", "Make saving of `quit.blend` on exit optional\n### Description & Scope of Problem\n\nEvery time Blender quits, when it has something on the undo stack, it will write the current \"undo file\" to `${TEMPDIR}/quit.blend` ([manual](open_save.html#last-session)).\n\nSaving `quit.blend` can take a while when the file is large. While the file is being written, Blender's UI is gray and unresponsive.\n\nThe problem is not pressing, as usually it takes considerably longer to load the files in the first place. I've asked some artists at the Blender Studio and they didn't really consider the delay when quitting Blender a practical issue. Still, it gets somewhat in the way of quickly testing things with various production blend files, so it could be seen as an issue for developers more than for artists.\n\n### Possible Solutions & Impact\n\n**Simplest solution:**\n\nAs a solution we could introduce a user preference \"Save Recovery File\" that is enabled by default. Disabling this option would:\n- Avoid writing `quit.blend`.\n- Remove the \"File ‣ Recover ‣ Last Session\" menu item.\n- Remove the \"Recover Last Session\" button from the splash screen.\n\n**Alternative solution:**\n\nThe \"Recover Last Session\" operator does not poll the filesystem from its poll function. This means that the operator is available even when the file `${TEMPDIR}/quit.blend` does not exist. Changing this, such that the operator is disabled when `quit.blend` does not exists, means that the above solution would not have to remove the recovery operators when \"Save Recovery File\" is disabled. The operators would auto-detect whether a recovery file is available at all.\n\nThe upside of this solution is that it makes the \"Recover Last Session\" operator appear more reliable, as it refuses to work when it knows it cannot do its job. This would be an improvement regardless of the \"Save Recovery File\" status.\n\nThe downside is that an old `quit.blend` might be lingering around after \"Save Recovery File\" has been disabled. This means that it could appear as if you could still recover, but it would load an older file. This could be avoided by removing `quit.blend` when disabling \"Save Recovery File\", but I'm not a big fan of Blender explicitly removing files that are meant to recover from human error.\n\n### Discussion Topics\n\nThis task is meant to discuss the following:\n\n- Do we want to make it possible to quit without writing `quit.blend` at all?\n- If so, which of the solutions is preferred? Or is there another way to deal with this that's even better?\n- Do we want this as a general option, or something that's enabled only when \"Developer Extras\" are enabled?\n", "Regression: Image rendering fails while viewport rendering is in progress\nOperating system: OSX Ventura Version 13.3\nGraphics card:AMD Radeon Pro Vega II Duo 32 GB\n\nBroken: 3.5.0 Date 2023-03-29 02:56 Hash: 1be25cfff18b \nWorked: 3.4.1 Date 2022-12-19 17:00 Hash 55485cb379f7\nCommandBuffer Failed: cycles_metal_integrator_compact_shadow_states\n\n* Load file provided\n* Set ViewPortShading to MaterialPreview\n* Then select ViewPortShading to Rendered\n* While the viewport is rendering Select Render Image.\n\nThis will often cause the error. It may take an attempt or two but more likely to happen after at least one attempt.\n\nIn some case blender will throw the error in both the viewport and in the image window. In some cases...Blender will hang and require you to force quit. At other times it will crash the OS. \n\nThe larger the scene the more drastic the failure. In this simplified file it typically will recover.\n\n", "Blender crashes: OpenVDB math::Transform::read throws exception. \nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.2\n\nBlender keeps crashing.\n\nI have a project were I created an animation of modified arrays. Everytime I play it it crashes\n\nCrash report: P1536\n\ncrashed thread: \n```\n\tThread 35 Crashed:\n0 libsystem_kernel.dylib \t0x00007fff726c733a __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff72783e60 pthread_kill + 430\n2 libsystem_c.dylib \t0x00007fff7264e8a2 __abort + 139\n3 libsystem_c.dylib \t0x00007fff7264e817 abort + 135\n4 libc++abi.dylib \t0x00007fff6f8ae458 abort_message + 231\n5 libc++abi.dylib \t0x00007fff6f89f8bf demangling_terminate_handler() + 262\n6 libobjc.A.dylib \t0x00007fff713da5b1 _objc_terminate() + 104\n7 libc++abi.dylib \t0x00007fff6f8ad887 std::__terminate(void (*)()) + 8\n8 libc++abi.dylib \t0x00007fff6f8b01a2 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27\n9 libc++abi.dylib \t0x00007fff6f8b0169 __cxa_throw + 113\n10 org.blenderfoundation.blender \t0x0000000110291c61 openvdb::v7_0::math::Transform::read(std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 4801\n11 org.blenderfoundation.blender \t0x000000011026082b openvdb::v7_0::io::Archive::readGrid(std::__1::shared_ptr<openvdb::v7_0::GridBase>, openvdb::v7_0::io::GridDescriptor const&, std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 1787\n12 org.blenderfoundation.blender \t0x0000000110286589 openvdb::v7_0::io::File::Impl::unarchive(openvdb::v7_0::io::File const&, std::__1::shared_ptr<openvdb::v7_0::GridBase>&, openvdb::v7_0::io::GridDescriptor const&, openvdb::v7_0::io::File::Impl::NoBBox) + 57\n13 org.blenderfoundation.blender \t0x0000000110282c91 openvdb::v7_0::io::File::readGridByName(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, openvdb::v7_0::math::BBox<openvdb::v7_0::math::Vec3<double> > const&) + 465\n14 org.blenderfoundation.blender \t0x0000000110282ab6 openvdb::v7_0::io::File::readGrid(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 54\n15 org.blenderfoundation.blender \t0x00000001128a2cc9 MANTA::updateGridFromVDB(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 361\n16 org.blenderfoundation.blender \t0x0000000112890985 MANTA::updateGridFromFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 869\n17 org.blenderfoundation.blender \t0x0000000112890cee MANTA::updateNoiseStructures(FluidModifierData*, int) + 558\n18 org.blenderfoundation.blender \t0x000000011287e2b5 manta_update_noise_structures + 21\n19 org.blenderfoundation.blender \t0x000000010df34cd0 BKE_fluid_modifier_processDomain + 3168\n20 org.blenderfoundation.blender \t0x000000010df316ce BKE_fluid_modifier_do + 142\n21 org.blenderfoundation.blender \t0x000000010e3ad4f6 applyModifier + 54\n22 org.blenderfoundation.blender \t0x000000010dea5b0a mesh_calc_modifiers + 2778\n23 org.blenderfoundation.blender \t0x000000010dea4d6b mesh_build_data + 123\n24 org.blenderfoundation.blender \t0x000000010dea4035 makeDerivedMesh + 133\n25 org.blenderfoundation.blender \t0x000000010dfe1281 BKE_object_handle_data_update + 1089\n26 org.blenderfoundation.blender \t0x000000010dfe1704 BKE_object_eval_uber_data + 52\n27 org.blenderfoundation.blender \t0x000000010e9f36ba DEG::(anonymous namespace)::deg_task_run_func(TaskPool*, void*, int) + 138\n28 org.blenderfoundation.blender \t0x00000001142cadbc task_scheduler_thread_run(void*) + 364\n29 libsystem_pthread.dylib \t0x00007fff72784109 _pthread_start + 148\n30 libsystem_pthread.dylib \t0x00007fff7277fb8b thread_start + 15\n```\n", "Trackpad stops working for a while\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M\n\nBroken: 3.6.2\nWorked: don't know\n\n\nSometimes, Blender stops responding to trackpad gestures such as two-finger scroll or pinch zoom. This is not just in the viewport but everywhere - I can't scroll menus or the node view, for example.\n\nThe UI is otherwise responsive when this happens - I can scroll menus by dragging the slider at the edge, just not with a two-finger scroll.\n\nIf I go and do something else in another app for a few minutes, it usually fixes itself.\n\nThis happens sporadically and I don't have a reliable way to reproduce it, but it seems to happen often after I render an image - after the image has rendered, I try to use pinch-zoom to look more closely and find I can't. I am not sure if it happens in other situations as well - if it does I will update this report.\n\n\nI'm afraid that I can't reproduce this reliably - it just happens every now and then, in any .blend file. I am happy to take any advice on how to look for a way to reproduce it.\n\n", "Crash to login screen on macOS Ventura when enabling caustics and smooth shading.\nOperating system: macOS 13.1\nProcessor: 2.6GHz Intel Core i7\nGraphics card: AMD Radeon Pro 5500M 8 GB\nMemory: 16GB 2667MHz DDR4\n\nBroken: 3.4.1\n\nBlender/macOS crashes to login screen when enabling smooth shading on an object with \"Cast Shadow Caustics\" enabled.\n\nCreate a scene with:\n\n - A light with \"Shadow Caustics\" enabled\n - An object with \"Cast Shadow Caustics\" enabled and a transmissive material applied\n - An object with \"Receive Shadow Caustics\" enabled\n\nSet render engine to Cycles and device to GPU compute (crash does not occur with CPU compute).\nSwitch viewport mode to Rendered.\nSelect the cast shadow caustics object and enable smooth shading.\n\nmacOS will hang before crashing to a login screen.\n\nsystem.log reports:\n\nsessionlogoutd[4795]: DEAD_PROCESS: 3681 console\n\nConsole.app also lists a crash report for WindowServer (example crash report is attached).\n\n[Caustics-Crash-on-Shade-Smooth.blend](Caustics-Crash-on-Shade-Smooth.blend) [WindowServer-2023-01-19-171731.ips](WindowServer-2023-01-19-171731.ips)", "Viewport animation render crashes when collapsing the viewport.\nBroken: version: 2.91.0 Beta (and 2.83, 2.80, ...)\nWorked: never\n\nViewport animation render crashes when collapsing the viewport.\n\n[0001-0485.mp4](0001-0485.mp4)\n[Viewport render crash.blend](Viewport_render_crash.blend)\n\n", "Open Blender\nHello\n\nI can't open the app, i dowload all versión windows, windows store and portable.\n\nsxstrace.exe\n\nI have windows 10, but i can open the app,\n\nI hope you can help me\nThanks\n\n", "Blender Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at [email protected]\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file", "Crash when baking Dynamic Paint Image Sequence multiple times in loop\nBroken: 2.90.0 Alpha\nWorked: blender-2.80-windows64\n\nBlender crashes when baking dynamic paint image sequence in for loop. Depending on wait time crash will have differens stack traces.\n\n[#74052.blend](T74052.blend)\n\n- Open file\n- Run script" ]

[ "Blender crashing on Mac OS Catalina when changing scenes + crashing upon startup when opening certain .blend files\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M395 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.83.4\n\n[I'm working on a .Blend file that has 3 scenes. The file opens fine, but when I change to a specific scene in Blender, it crashes. Additionally, I have another .Blend file (that's basically identical to the attached file, minus an empty scene) that upon opening, Blender would instantly crash, almost as if the file is corrupt. This happened all day yesterday. Today however, I'm able to open the file again. But when switching to the shader tab, it crashed. I've had these issues using the same files on both my iMac and MacBook Pro... I'm not sure if this issue is directly related to my Macs, Mac OS Catalina, or Blender having a bug. I realize my graphics cards aren't supported for any GPU related tasks. But both Macs are far beyond the minimum requirements to run Blender. \n\nAdditionally, I tried restarting my Macs. Uninstalling and reinstalling Blender. And have even downgraded Blender versions all the way back to Blender 2.81\n\n**Mac OS:**Catalina 10.15.6 \n**iMac Specs:** iMac (Retina 5K, 27-inch, Late 2015), 3.3 GHz Quad-Core Intel Core i5,64 GB 1600 MHz DDR3,AMD Radeon R9 M395 2 GB.\n**MacBook Pro Specs** - (15-inch, 2016), 2.9 GHz Quad-Core Intel Core i7, 16 GB 2133 MHz LPDDR3, Radeon Pro 460 4 GB\nIntel HD Graphics 530 1536 MB.\n\n[Please describe the exact steps needed to reproduce the issue: Change the scene from \"Product Modeling\" to \"Lipstick in Environment V1\" and Blender should crash. (please note, you may have some missing texture files as I'm only uploading the blender file itself, not the displacement and color maps).[DATR-CGI-20-008 Body Ambitious Lip Stick.blend](DATR-CGI-20-008_Body_Ambitious_Lip_Stick.blend) ]\n\nAny help would be greatly appreciated! I'm new to Blender and have so far enjoyed learning it, with the exception of the instability I've been having recently.\n\n" ]

[ "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n", "Multiresolution - Crash when Linear Subdivision level is above 1\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.91.0\nWorked: Never? (2.90 and 2.92 dailies seem to crash on this one as well)\nWhen using multiresolution modifier on this part of my model and using linear subdivision level above 1, Blender crashes.\nThis does not happen with other subdivision methods, as shown in video.\nI've also tried to make this mesh manifold, but Blender crashed either way.\n\n\n1. Open attached Blend file\n2. Add multiresolution modifier to a mesh\n3. Press on \"linear\" button twice\n\n[Crash_SampleFile.blend](Crash_SampleFile.blend)\n\n[MultiresCrash0001-2375.mp4](MultiresCrash0001-2375.mp4)\n\n", "Double click list renaming not working on heavy scenes\nVista64, 2.7a, gtx470\nWhen the scene is heavy, so that interface becomes slightly laggy, double click list rename stops working, especially for fast clicking.\n\n - Add subdivision modifiers to any mesh until interface becomes laggy.\n - Add a vertex group or UV map.\n - Double click to rename - renaming is not activated.\n", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n", "Blender just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "Overlay: Edit-Mode: Anti-Alliasing not working with constructive modifiers\n```\nOperating system: Linux-4.15.0-50-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce 610M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n```\n\nthe bug is really intresting so... when you add mirror modifier to object.. and u enter edit mode and u select face or edges etc... the AA goes crazy it is so pixelised like even worse than tottaly without AA.\n\n\n\n\n\n\n\n", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n", "Crash when switching to Sculpt mode\nOperating system: \nLinux bu-dvl-2 5.13.0-51-generic #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux\n\nGraphics card:\n0:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)\n\nBroken: 3.2.0\n\ncrashed when switching to Sculpt mode\n\n- Open alien.blend (attached) \n- Switch to Sculpt mode\n\n[alien.blend](alien.blend)\n\ncrash.txt: \n[alien.crash.txt](alien.crash.txt)", "Crash (memory use after free) on freeing RigidBody world\nReproducible with current master, probably there since forever.\n\n# Steps\nWith an ASAN build:\n\n- Open `rigid.anim.blend`\n- Close Blender\n\n[rigid.anim.blend](rigid.anim.blend) \n\n(Case found while working on #86379 (When using \"Append\" rigid body objects + empty constraint, none of its constraints work.))\n", "Error de progama\nno me aparece el modo vèrtice\n\n", "Render Audio\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nIn the Video Editing mode, when using Render Audio, the program title bar shows: Not Responding.\nBut Blender actually completes the render audio process after a couple of minutes.\n\nOpen Blender, select Video Editing Mode and import video file with audio.\nClick display Wave form and set audio to mono.\nSelect Render - Render Audio and use mp3 container, Format: S16 and 128 as bitrate.\nEnter a file name and click \"Mixdown\"\n\nThe Blender title bar shows that the program is not responding, but after a couple of minutes the audio file finish rendering and works just fine.\n\nYou can find a screen capture of the event attached, showing the title bar \"Not Responding\" and also the RAM and CPU values at the time.\nAlso attached is the blender file. (I just removed the video parts.\n\nThank you all for the best 3D software in the world!\n\n\n\n", "Lag Adjusting Value Sliders & Navigating Nested Menus with a Wacom Tablet\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93.2\n\nTrying to change the value of shapekeys or shader sliders with my stylus doesn't get detected the first few seconds, then picks up, but in a non responsive way. Also while using my stylus, if I navigate to a nested menu like say \"Object > Transform\" There's a Lag when moving to another option in the \"Object\" Menu.\n\nThe steps above should apply. I did notice though, that if I change my Tablet API from 'Automatic' to 'wintab' in the the input preferences, it helps, but its still not as responsive as it is in 2.93\n\nAll these issues though, were non existent, if I tried using my laptop's trackpad. Also, my tablet is a Wacom Intuous Touch 5 with a stylus that supports up to 2048 levels if pressure sensitivity and has tilt support, just incase it could be any of these causing the issue. \n\nThanks.\n\n", "use-after-free crash after setting scene's render.engine inside custom render engine context\nOperating system: Ubuntu 20.04.2LTS\n\nBroken: 2.93.0 Beta, branch: master, commit date: 2021-05-19 10:14, hash: a294670bacb1, type: release\nAlso Broken: 0efb627bbd3ac3e53afb95591ae4e244bd1f8af4\n\nBlender crashes when setting some scene's render.engine property inside `__init__` or the `view_update` context of a custom render engine to a different one than the custom engine.\n\n[T88404_asan_report.txt](T88404_asan_report.txt)\n**Code to reproduce the error**\n```\nimport bpy\nimport bgl\n\nclass CustomRenderEngine(bpy.types.RenderEngine):\n bl_idname = \"CUSTOM\"\n bl_label = \"Custom\"\n bl_use_preview = True\n \n def __init__(self):\n return\n scene = bpy.data.scenes.new(\"foo\")\n scene.render.engine = \"CYCLES\"\n bpy.data.scenes.remove(scene)\n\n def __del__(self):\n pass\n\n def view_update(self, context, depsgraph):\n scene = bpy.data.scenes.new(\"foo\")\n scene.render.engine = \"CYCLES\"\n bpy.data.scenes.remove(scene)\n\n def view_draw(self, context, depsgraph):\n pass\n\ndef get_panels():\n exclude_panels = {\n 'VIEWLAYER_PT_filter',\n 'VIEWLAYER_PT_layer_passes',\n }\n\n panels = []\n for panel in bpy.types.Panel.__subclasses__():\n if hasattr(panel, 'COMPAT_ENGINES') and 'BLENDER_RENDER' in panel.COMPAT_ENGINES:\n if panel.__name__ not in exclude_panels:\n panels.append(panel)\n\n return panels\n\n\ndef register():\n bpy.utils.register_class(CustomRenderEngine)\n\n for panel in get_panels():\n panel.COMPAT_ENGINES.add('CUSTOM')\n\n\ndef unregister():\n bpy.utils.unregister_class(CustomRenderEngine)\n\n for panel in get_panels():\n if 'CUSTOM' in panel.COMPAT_ENGINES:\n panel.COMPAT_ENGINES.remove('CUSTOM')\n\nif __name__ == \"__main__\":\n register()\n```\n\n1) Copy code from above into a new script file inside of Blender\n2) Run the script\n3) Select \"Custom\" as Render Engine inside Render Properties\n4) Select \"Material Preview\" as display method in the viewport.\n\n[crash.blend](crash.blend)\n\nCrash log:\n```\n# Blender 2.93.0, Commit date: 2021-05-19 10:14, Hash a294670bacb1\nEngine 'CUSTOM' not available for scene 'Scene' (an add-on may need to be installed or enabled) # Error\nbpy.ops.text.run_script() # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xa63c950]\n./blender() [0xf6082a]\n/lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f7ce17be210]\n./blender(GPU_framebuffer_blit+0x2f) [0x8664faf]\n./blender() [0x1485fc3]\n./blender() [0x14597fe]\n./blender(DRW_draw_render_loop_ex+0x242) [0x1459a72]\n./blender(view3d_main_region_draw+0x8f) [0x1d3570f]\n./blender(ED_region_do_draw+0x851) [0x189c771]\n./blender(wm_draw_update+0x52e) [0x130cc9e]\n./blender(WM_main+0x30) [0x130aa20]\n./blender(main+0x319) [0xe881c9]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f7ce179f0b3]\n./blender() [0xf5d1bc]\n\n# Python backtrace\n```", "Multires: Artefacts from lower subdiv level changes\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.90 (sub 0)\n\nWhile I was testing MultiRes in 2.90, I found a bug when sculpting on lower subdiv levels which recently got activated. If you for instance smooth the sculpt at a lower subdiv level and save your sculpt while at any lower subdiv level that isn't the highest one, your sculpt will deform with artefacts. Here's a demonstration:\n\n[Desktop 2020.05.03 - 17.27.17.02.mp4](Desktop_2020.05.03_-_17.27.17.02.mp4)\n\n\nHere's the file I was working on.\n[Urbosa Sculpt.blend](Urbosa_Sculpt.blend)\n\nHere's what you need to do to reproduce:\n\n1) Smooth an area with a lot of sharpness to it at the current subdiv level (it can be any level except 5 which is the highest one).\n\n2) Save the project.\n\n3) Artefacts should appear now. Change to other subdiv levels, including level 5 and repeat the save just to compared the results. The highest subdiv level should always work. An alternative way to not reproduce the bug is to smooth at a lower subdiv level and then go to the highest level available and save. Then the artefacts don't appear either." ]

[ "2.8 - Subdivision Surf Modifier poor performance in this mesh\nOperating system: Linux-5.0.1-050001-generic-x86_64-with-Kubuntu-18.04-bionic 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.43\n\n\nBroken: version: 2.80 (sub 50)\n\nOpen this .blend file:\n[bad_perform_subsurf.blend](bad_perform_subsurf.blend)\nAdd subsurf modifier on the selected object by default. On my machine Blender hangs, one thread of the CPU working 100%\n\n" ]

[ "Clicking on a pie menu item doesn't work when holding the pie menu key.\nOperating system: Windows 10\n\nBroken: 2.79, 2.92\n\nClicking on a pie menu item doesn't work when holding the pie menu key. This is a problem because sometimes the pie menu key release isn't detected by blender and then the it locks the UI.\n\n1. On the 3D Viewport hold Z for the shading pie menu.\n2. While still holding Z try clicking on the pie menu items. Doesn't work.\n3. While still holding Z, left click on Windows's Taskbar then release z.\nAfter that, clicking on the pie menu items doesn't work even though the user isn't holding the pie menu key anymore, blender still considers that the key is held. Then Blender gets locked to the user unless he knows to press esc or right click. The solution is making the pie menu clickable even when the pie menu key is held.", "Known-issues with interaction handling inside pop-ups\n# Known-issues with interaction handling inside pop-ups\n\n*Pop-up in this case includes menus and popovers.*\n\nThere are quite some old and some new issues with pop-ups. Their increased usage after 2.80 means that users run into them more and more.\n\nIn this task all related known issues should be listed, to give a good view over the situation. Eventually it should help deciding how to move forward.\n\n* Resetting default value does not work in popovers or menus. (#69200)\n* Context Manual Help Operator does not work in context menus. (#67201)\n* Add Driver : Clicking the picker doesn't work. (#58341)\n* Popover: Color Sampling doesn't work. (#63890)\n* No color drag'n'drop in Viewport Shading popover. (#70654)\n* Eyedropper does nothing on \"New\" in Uv image editor (button is disabled as workaround). (#32396)\n* ~~Most ID selectors (like e.g. the 'target' ones in constraints and modifiers) do not show difference between local and linked IDs. Even worse, they do not allow to select linked ones when a local one exists with the same name. (#73156)~~ (d6cefef98f)\n* Double-click not working in UI_Lists in popovers (e.g., grease pencil layers renaming) (#66286)\n* #76833 (Eyedropper in object selection box doesn't work)\n* #76124 (Cannot use keyframes, File select, File picker (eyedropper), etc. in modal Operators/Panels called by WindowManager)\n\nMost of these issues probably have similar roots (e.g. code not checking if `CTX_wm_menu()` can be used over `CTX_wm_region()`, but often times the former returns `NULL` when it shouldn't).", "GPencil: W shortcut in Draw mode not working and displays error\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.4.1\n\nThe W shortcut used to display the Context menu, the same summoned with RMB, but it's not working & displaying this error message:\n```\nTool 'builtin.select_box' not found for space 'VIEW_3D'\n```\nOpen a new 2D Animation file and press W.\n\n", "NURBS: Repeat for Extrude doesn't repeat extrusion, selects all points\nBroken: 2.92\nWorked: ???\n\n\nAttempting to repeat (shift+r) extrusion in NURBS edit mode yields no result. Subsequent attempt results in all points being selected.\n\n\n1) Add a Surface -> NURBS curve\n2) In edit mode, select a point and extrude\n3) Attempt to repeat with shift+r (nothing happens)\n4) Attempt to repeat again (everything becomes selected)", "VSE: Select more/less functionality breaks on certain conditions\nOperating system: Linux Mint 20\nGraphics card: NVIDIA G92 [GeForce 9800 GT]\n\nBroken: 2.93.1 / 2.92.0\nWorked: Unsure\n\nThe functions sequencer.select_more and sequencer.select_less get stuck when the newly selected strip reaches an edge, or when number of selected strips becomes zero.\n\n[blender-bug__select-more-less.mp4](blender-bug__select-more-less.mp4)\n\nThe attached video shows the functions [select_more]/[select_less] will break when the following conditions are met:\n```\n a) Any strip chain selection reaches the edge of the row of strips with [select_more]\n i) either when it starts from an edge and reaches the other edge\n ii) or when it starts in the middle and expands from both sides, the side of whichever edge is met will get stuck\n b) Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more]\n```\n\n\n\nI think it's unlikely this is intended behaviour?\n\nSorry I didn't get visual keypresses set up for the video, but I'm just using CTL- [x] and CTL- [x] on num pad as per default. \n\nDavid", "Doubleclick not working in UI_Lists in popovers (e.g., grease pencil /annotations layers renaming)\nBlender 2.81, 2.82, ...\nWorked: ?\n\nUnable to rename grease pencil layer when tooltip says: 'Active layer index, Double click to rename.'\n\n\n- Go to either '2D Full Canvas' or ' 2D Animation', \n- Add a blank Grease Pencil, \n- Change mode to Draw\n- Drag the header bar to left to review 'Layer:'\n- Click the down arrow to show the layer's panel\n- Press + there to add a new layer\n- Select either old or new layer and while leaving mouse pointer hover over it, you should see a tooltip 'Active layer index, Double click to rename.' Try to double click on it and 'NOTHING HAPPENS'. \n- In 2D Animation layout you can access the 'Properties' panel on the left and rename there, in 2D Full canvas, you'll have to split window, creating a new one, change it to Properties before you can do the 'RENAME'.\n\nScreenshot for ' 2D Full canvas' layout, rename is IMPOSSIBLE:\n\n\nScreenshot for '2D Animation' layout, rename is IMPOSSIBLE:\n\n\nScreenshot for the same control in Properties panel, where RENAME is possible:\n", "Ctrl+Click for Nurbs Surfaces\nWith Meshes and Curves, you can select a point, press Ctrl+LMB, and the point is extruded to the mouse.\n\nThis however does not work for Nurbs, even though you can extrude a point, Ctrl+LMB does not work.\n\nTry:\n- Add -> surface -> nurbs curve\n- Enter editmode\n- Select an end-point\n- Ctrl+Click... *nothing happens*\n\nThe same works for a curve or a mesh.\n\nThis could be split into 2 tasks\n- Get Ctrl+Click working for single nurbs curves.\n- Get Ctrl+Click working for nurbs surfaces (using the extrude code), This should extrude and place the newly extruded vertices at the mouse position, as is done with mesh data.", "Implement Driver Workflow Changes\nFollowup task to #54653 to work on implementing the workflow changes proposed.\n(Note: This is currently a lower priority item than fixing bugs to get 2.8 into a usable state for Spring team. But, I'll be working on this when I get time). \n\nThere are the following sub-tasks:\n* ~~**Create operator for \"Open Drivers Editor\" functionality.**~~ c685c19df9\n * ~~Basic opening functionality~~\n * ~~Filtering support to get driven property under mouse at the time the \"active\" driver~~\n * Abstract out the \"Setup Drivers Editor\" and \"Show this channel\" functionality\n * Sub-editor mode for drivers in the mode selector\n\n* **Eyedropper support for clicking in 3D view and getting menu of common properties to drive, based on item under mouse.**\n * Basic object support\n * Investigate possibility of bone support too. (NOTE: Last time this was tried, it turned out being too complex to accomplish)\n * Restore cursor feedback when eyedropper is active (#55147)\n * Solve context/src button problems preventing eyedroppers from working in the popover\n\n* **Clean up drivers editor ui** - 57b47ebb28 (and followup commits)\n * ~~Add more space for expressions box~~\n * ~~Remove \"Show Debug Info\" checkbox - it's always needed~~\n * ~~Remove \"Update Dependencies\" button by making it redundant~~ - Should be ok now without out. It's still in the UI, but will be removed soon\n * Remove \"Use Self\"? Or rename?\n * Add optional display of useful hints about syntax for expressions and/or what can be used\n\n* **New persistent floating panel UI for editing driver settings**\n * ~~Basic layout~~ - 7e7680e33b - Use a modified version of the existing drivers editing panel, and make it a popover\n * ~~Floating panel~~ - 7a88a7742b - This makes the panel a popover. But, it doesn't stay open, or let you open the drivers editor\n * ~~Make floating panel stay open~~ - b11a1d5da2\n * ~~Get \"Open Drivers Editor\" button working in the popup (i.e probably missing button context info for source property)~~ - 1ff28c2650\n * ~~Get Copy/Paste dvar operator buttons working (currently always greyed out)~~ - 3e086af79c\n * ~~Fix issues where popover still goes away too easily sometimes~~ - Seems to be fixed with 17ee4836ab now. It may still happen, but it happens a whole lot less now.\n\n* **Reduce friction of adding new driver variables / setting up basic single-target drivers**\n * ~~Replace 'Add Drivers' Menu with Popover Panel ~~ - 4605e57b0f\n * Remove old (menu-based) operator\n * \"Mapping\" settings properties (see proposal)\n * ~~Make setting driver input-target easier~~ (i.e. no more need to change default expression first) - 9ab26bec27\n * Eyedropper for populating input variable settings (see above)", "Fly Navigation using the trackpad is broken\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: until 3064da1200a9\n\n\nThere is trackpad support for Fly Navigating, but it does not currently work due to key-map issues.\nDetails are here: D9641\n\n", "Driver Workflow Design\nFor Blender 2.8, we want to improve the workflow for adding drivers. Here's how:\n\n\n\n - When the user right-clicks on a property and adds a driver, we display a non-modal, persistent Add Driver floating popup. \n - While open, all of Blender remains responsive, and the user can select any object in the scene. \n # From the popup, users can select a property to use as as a driver. No other steps are needed.\n\n\n\n\nOptionally, users can then set a multiply and offset value, and add additional driver inputs. They can also click the Open Driver Editor button to open a Drivers window,\n\nUsers can also use the ID type picker to select from a list of Object and property ID's. They can also, using the eyedropper, directly select an object in the 3D View, or in the Outliner. When users select an object, they are presented with a basic list of commonly used properties, like so:\n\n\n\n\nIf the user has closed this window and wants to get it back, they can right-click on the property being driven and \nselect Edit Driver, like so:\n\n", "VSE UI: Change Path/Files is over exposed \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nChange Path/Files is exposed in four places. \n{[F10401818](image.png),size=full}\nAs this function is only working(afaik) on the active strip(why Files in plural?), it should only be exposed in the strip sidebar. See: #91306 If the function is basically the same as changing the path to the source file then the folder button next to the path should be enough. \nAlso, having it as a secret pop-up menu, shortcut key \"C\", is inconsistent with anything in Blender and this should be removed. \n\n\n", "Simple ball shooting animation not working as before\nOperating system: win7\nGraphics card: gtx970m\n\nBroken: 2.80, 2.81a, 2.82a, 2.83-1239cab11ff9\nWorked: 2.79b\n\nI've tried to create a simple shooting ball and while the effect was ok with blender 2.79b it won't work the same\nway on the specified \"broken\" versions. I'm not sure if the way to make these type of animations has changed of\nif this it's really an existing bug. \n\nDemo: [Blender 2.79b vs 2.82](2020-04-09_16-14-38.mp4)\n\n\nYou'll find the .blend file ready to display the issue below.\n\n[test1.blend](test1.blend)", "Allow changing Color Picker value with the trackpad\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: never\n\n\nWe can use the mouse wheel while hovering over the Color Picker to edit the value.\nBut this feature doesn't work when we use the trackpad scroll.\n\nThe required changes are quite simple: D8811\n\nInside the Color Picker popup box, scroll over the color wheel.\n\n", "Selection problem on new 'add modifier' menu\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\n\nin new 'add modifier menu' which introduced in Blender 4.0 if you hover your mouse over a main menu items like 'edit' to open edit's submenu then move your mouse diagonally from top right to bottom left on main menu, other main menu items not highlighting or selecting.\nI attach a video take look at it, in this video I move my mouse from edit(while it's open) to physics , non of menus open, not even physics which I stop mouse there no matter how much time my mouse stay there it will not open.\nalso I moved my mouse from edit to generate and also menu did not open.\n\n", "can't use logitech mx master 3 mouse shortcut keys in blender 3.6 LTS\nOperating system: Win 11\nGraphics card: RTX 3070\n\nBroken: (3.6 LTS)\n\n**I can't use the logitech mx master 3 mouse shortcut keys in blender 3.6 LTS.**\n\n\n" ]

[ "Eyedropper for driver's doesn't work\nOperating system: Win 10 64 bit\nGraphics card: Intel inside\n\nBroken: 2.80 rc1\n\nUsing the eyedropper to get a driver works around 8% of the time. Otherwise it's like clicking a dead button when I click the eyedropper: nothing happens.\n\nI admit I am using an older version of blender, but rcs 2 and 3 seem to be getting worse and worse for me (see other bug reports)." ]

[ "Workbench/Solid : Texture interpolation not displaying properly in viewport (shared across all users of an image)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.0\nWorked: --\n\nLow resolution textures are no longer being correctly displayed as a sharp graphic in the viewport when the texture interpolation is set to \"closest\" in the material shader.\n\nfeature works as intended in rendered view so long as Eevee or Cycles is selected. Workbench does not work as intended in rendered view.\n\nplace object into scene. Locate a low resolution asset such as pixel art and map the texture to the object. \n\ntextures have always appeared blurry at first in the viewport but common pixel art practice is to set the interpolation from \"linear\"(or whichever is set to default) to \"closest\"\n\nWe have 4 materials each having individual Image Texture nodes (but all using the same image).\n\nIf you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.\n\n", "Roundness fails for top corners of lighting subpanel\nWindows 11 OS\nBlender 3.0.1\n**Under 3DViewport Theme Settings, ''MenuBack\" Roundness slider only rounds the bottom part of matcap/studio light SubPanel)**\n\n", "Color Picker in texture mode sampling incorrect values (sample merged OFF, sampling from another object)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.92.0\nWorked: ?\n\nThe color picker in \"Texture Painting\" mode seems to only sample the correct color when the look is set to **None**under the **ColorManagement->Look->\"None\"** and if the Viewport **Shading->RenderPass** is set to **DiffuseColor**.\nOtherwise, the color values are simply wrong, they are either too bright or too dark.\n*In the provided scene the issue is quite clear, but in more complex scenes with more complex lighting and post-processing the sampling becomes **completely** broken giving values that aren't even close to what is shown on screen.*\n\n**Expected Behaviour**\nThe way I would expect the color picker to work is that it either samples the color as **I** as a user see it on my viewport.\nOr that it samples the source texture at the pixel I am sampling without any extra lighting applied to it. *( This should be easily toggleable behavior but that is more of a feature request )*[ColorPicker_WrongSampling.blend](ColorPicker_WrongSampling.blend)\nRight now it seems to do neither.\n\n\n - Open attached .blend file.\n - Select the black cube and enter Texture Paint Mode.\n # Sample the color from the other cube *( I recommend sampling the green since the meshes are close to each other making it easy to see the color difference )*.\n\n\n", "Improve visualisation and manipulation of lights in the viewport\nThe idea is to better control/visualize light parameters in the viewport. Currently we can only control the spot angle of spot lights, the size of area lights and the light direction. \nConcept drawings by @eyecandy for reference, not the final design.\n**Tasks**\n- [ ] visualize light color (translucent filled? opaque outline? center circle?)\n\n- [ ] register gizmo undo\n- [x] make scaling transform follow the cursor exactly\n\nAdd gizmos to\n- [ ] spot light\n - [x] radius\n \n - [x] make scalable even when radius is zero?\n - [x] blend \n - [ ] spot angle via new gizmo type instead of arrow \n- [ ] area light\n - [x] constraint scaling in X/Y directions \n - [ ] beam spread (only supported in Cycles) \n - [ ] clip end/custom distance (only in Eevee) \n- [ ] sun lamp\n - [ ] angular diameter \n- [x] point light\n - [x] size ", "EEVEE: User preference settings (anisotropy, texture size limit) affect rendering\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n[Viweport texture limit size affects eevee rendering.]\n\nWhen I change the \"texture limit size\" setting it also limits the size of the texture in the render.\nAs the setting is in the \"viewport\" tab I believe it should only affect the viewport, not the rendering.\n\n", "Boolean - Animation - Viewport works correctly render view doesnt\nUbuntu 18.04, Win 7 x64\n\nBroken: d53093953f8\n\nBooleans dont match between Viewport and Render\n\n1. Open attached blend file\n2. Preview render (shift z)\n3. Notice the green on top\n4. F12 Render\n5. Notice how the green is no longer there\n\n[booleansBug.blend](booleansBug.blend)", "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "2.93 texture coordinate display bug\nOperating system: win10\nGraphics card: 2070 super\n\nBroken: 2.93.0-321eef6a0c0f 4/2\n\n\n\ntexture coordinate display bug differently in viewport compared to render\n\ni used a generated coordinate. in the viewport it seems that blender applied the coordinate after the curve modifier (maybe)\n\nbut in render it will apply the coordinate before the curve modifier, so the gradient is able to follow the curve which is my desired look.\n\nsometimes it will display the coordinate correctly but I don't know how I achieved it\n[bug.blend](bug.blend)\n\n", "Cycles: negative BSDF mixtures weights\nOperating system: Ubuntu 21.10\nGraphics card: Nvidia 2060\n\nmaster branch\n\nWhen adding some sanity checks into the Cycles code I realized that the BSDF mixture weights can become negative.\nI am not sure if this is the desired behavior since it is not physically correct and has the potential to cause problems when there is the assumption\nthat BSDF evals always return positive values.\n\n\nNegative BSDF mixture weights occur in the Barbershop scene and can be matched by adding an assert \nto the `svm_node_closure_weight` function in `intern/cycles/kernel/svm/closures.h`:\n\n```\nccl_device void svm_node_closure_weight(ccl_private ShaderData *sd,\n ccl_private float *stack,\n uint weight_offset)\n{\n float3 weight = stack_load_float3(stack, weight_offset);\n assert(weight.x >= 0.f && weight.y >= 0.f && weight.z >= 0.f);\n svm_node_closure_store_weight(sd, weight);\n}'\n```", "Reflection plane significantly reduces intensity of normal maps on affected surfaces\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU\n\nBroken: Currenct main.\nWorked: Never.\n\nWhen a reflection plane capture is added to any scene in EEVEE, the resulting reflections on surfaces affected by said capture will be significantly less affected by shader-based normal maps.\n\nComparison:\n| Without a Reflection Plane | With a Reflection Plane |\n| -- | -- |\n|  |  |\n\nThis is unexpected behavior, and although I do not fully know the intricacies of how the reflection plane capture functions, it would ideally not affect surfaces in this way.\n\nOpen the included demo file and switch to rendered view.", "Incorrect combined texture baking with subsurface material\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nBaking result is different from what I have seen in render and has strange artifacts.\n\n\nOpen attached file and run combined baking with default settings.\n[test_bake_2_79.blend](test_bake_2_79.blend)", "Display as behaviour in rendered view inconsistent between Eevee and Cycles\nOperating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19\n\nBroken: version: 2.82 (sub 4)\n\nWhen objects are set to display as wire or bounds, in the rendered view in eevee they are shown as wire or bounds respectively, but in Cycles they are fully rendered. \n\nFor any object, under object properties -> viewport display, set display as to \"bounds\" or \"wire\". Subsequently when the viewport is set to rendered view, the object is shown as bounds or wire in Eevee, but in Cycles the object is fully rendered. The Cycles way would be the preferred way in my opinion.", "Cycles viewport rerender when changing any color management setting if a rigidbody is on any object\nOperating system: WIN 10\nGraphics card: GTX1660\n\nBroken: 3.0.0, 3.1 BETA, 3.2 ALPHA\nWorked: Never\n\nWhen changing any of the color management settings in blender, a viewport rerender will be triggered if you have a rigidbody on any object.\n\nOpen blender\nput renderer to cycles\nput a rigidbody on the default cube (or any object)\ngo into viewport rendered preview mode\nchange any setting in colormanagement (eg. exposure, gamma, false color, medium contrast to high contrast)\nwatch the viewport rerender\n\n[BugTest.blend](BugTest.blend)", "Object.display_type \"Solid\" behaves the same as \"Textured\"\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.8.1 26.20.13001.29010\n\nBroken: version: 2.81 (sub 12)\nWorked: 2.79b\n\nIn a viewport set to \"Textured\" mode (either on Cycles or Eevee), setting Object.display_type = \"SOLID\" still shows a textured object.\nOn Blender 2.79 this property was called \"Maximum Draw Type\" and was behaving as expected.\n\n1.-Set the viewport to Textured mode.\n2.-Select a textured object and set its property \"Display As\" to Solid.\nIt will stil be shown as Textured so theres no difference between the two modes (Solid, Textured)\n\nBlender 2.81\n\n\nBlender 2.79b\n\n\nExample blend.\nThe viewport is set to \"Textured\", the monkey set to \"Solid\" but is shown as Textured.\n[solid_object_display_type.blend](solid_object_display_type.blend)\n", "Image of the viewport can no longer be obtained via glReadPixels in Python. Gives strange results since 2.83\nOperating system: Arch Linux 5.8.5-arch1-1\nGraphics card: Intel i7-8665U\n\nBroken: since 2.83\nWorked: till 2.82\n\nIn Python, we get an image of the viewport from within an registered draw handler routine using:\n\nviewport = bgl.Buffer(bgl.GL_INT, 4)\nbgl.glGetIntegerv(bgl.GL_VIEWPORT, viewport)\nwidth = int(viewport[2])\nheight = int(viewport[3])\nimage = np.zeros([height, width, 4],dtype=np.uint8)\nbuffer = bgl.Buffer(bgl.GL_BYTE, image.shape, image)\nbgl.glReadPixels(0, 0, width, height, bgl.GL_RGBA, bgl.GL_UNSIGNED_BYTE, buffer)\n\nIt worked fine till 2.82, as shown here\n\n\nHowever, it gives blackish colors of the objects in the viewport since 2.83:\n" ]

[ "Layer weight gives incorrect result in GLSL Material mode\nNixOS Linux, kernel 3.18.26\nGeForce GTX 970, driver 352.63\n\nBroken: 2.77-rc1\nWorked: 2.76b\n\nCycles layer weight node shows an incorrect result in Material mode in the viewport.\n\nIn 2.76, the attached file shows as follows:\n\n\nWhile in 2.77-rc1 I get this:\n\n\nSee attached blend file in Material mode in the viewport.\n[bug.blend](bug.blend)\n\nA workaround is to connect the Normal input of the Layer weight node to the Normal output of a Geometry node. However, connecting to a image texture normal map gives wrong results.\n\nNote: reverting commit 72dd1ba3fe67206680ef3540b681d944e8bb4872 (\"Fix #47349: incorrect Cycles fresnel and layer weight with GLSL materials\") fixes the problem for me. However, that does break the workaround described above (i.e. where the Normal output of the Geometry node is used)." ]

[ "Pie menu assigned buttons freezes switching during mouse movement\nOperating system: Linux Mint\n\n\nBroken: 2.8 official\nWorked: 2.79\n\nZ, Tab and ` by default calls pie menu.\nEven if pie menu is disabled in keymap, they seems to wait for pie menu drag before switch their mode, so they sticks while mouse is moved.\n\nSteps to reproduce:\n\n1) Remove Shading checkbox assignment (VIEW3D_MT_shading_pie) from Z key\n2) Spam Z in 3D viewport\n\n3) If \"pie menu on drag\" checkbox is on\n\n 3a) When mouse is still, Z switches wireframe mode immediately\n\n 3b) When mouse is moving, Z stops switching.\n\n4) If \"pie menu on drag\" checkbox is off, Z key stops switch wireframe mode at all.\n\nGIF to compare 3a and 3b:\n\n\n\nGif to reproduce 4:\n\n\n\n", "Sculpt mode: brush strength jump, when brush switches between two parts of mesh\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: version: 3.0.0 Alpha\n\nWhen brush jumps from one mesh to another its strenght increases for a moment.\nHere is demo and file for tests:\n\n\n[2021-05-13_21-10-24.mp4](2021-05-13_21-10-24.mp4)\n\n[jump.blend](jump.blend)", "Gizmo shifting to different value after release with tablet input.\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.90.0\nWorked: 2.79 (haven't tested this extensively)\n\nWhen using a tablet to manipulate objects, the gizmo will often pop to a different location. A similar thing happens in the dopesheet when moving the playhead, it will pop to a different (usually very close) frame. I assume this is due to how the tablet input is being interpreted but after exploring and changing every setting I can find, the problem still persists to a certain degree. \n\nBasically, just select an object, choose the rotate tool (not the r shortcut) and use a tablet to rotate on an axis. I've attempted to record this issue in the attached video. [tablet issue.mp4](tablet_issue.mp4)\n\n", "Shader editor: nodes moved with G key added to frames based on cursor position\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.83.4 (also with the 2.90 beta from August 25th)\nWorked: I don't know. I remember this strange behaviour for a long time (2.80?) but could not pinpont the exact behaviour until now\n\nIn shader editor, when you have a frame and move nodes outside it with the shortcut G, the node is added to the frame based on the cursor position and not on the node position.\nAs expected, when pressing G key, a user does not align the cursor to the node to be moved but presses the G key regardless of the cursor position.\n\n- Default startup file\n- In shader editor, add and join some nodes into a frame (Ctrl J)\n- Grab another node outside the frame with G with the cursor position far from the node to be moved\n- Move the cursor so that the cursor is inside the frame but the node is not and click to confirm new position\n- The node is added to the frame based on the cursor position although it is far outside the frame\n", "Support Viewport roll - around the cursor position\nCurrently view orbit supports zoom-to-mouse-position as a way to rotate and zoom around the cursor position.\n\nView roll however always uses the view center.\n\nWhile low priority, this would be nice to support. See: #70761 (Roll View ignores Auto Depth)", "Value of Quad Corner Type changes automatically in the Subdivide operator.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.93.0 Alpha\n\nValue of `Quad Corner Type` changes automatically in the Subdivide operator.\n\n\n1) Open Default Scene.\n2) Go to Edit Mode, right click and select Subdivide.\n3) Uncheck the Create N-gons box.\nQuad Corner type is automatically set to `Inner Vert` from `Straight Cut`.\n\n(But we can still select `Straight Cut`, not like its disabled) so this doesn't look like consistent behavior?\n\n", "UI: Sequencer/Preview jumps to cover entire preview area\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\n\n- In the Sequencer Preview, select Sequencer/Preview.\n- Adjust regions so both Preview and Sequencer are visible.\n- Adjust the height of the area.\n- Notice that when the area height meets the region height, the Sequencer region jumps to fill the entire area.\nExpected behaviour: that the sequencer region doesn't jump to cover the entire area, but is scaled with the change of the area height. Or in other words that the sequencer region height is scaled to the area height, instead of being fixed. \n{[F10144522](sequencer-preview-jump.gif),size=full}\n\nAn additional annoyance is when changing the area height:\n{[F10144525](sequencer-preview-jump2.gif),size=full}\n", "Assign Shortcuts: creates shortcut in the \"wrong\" space\n**OS**: Linux 5.3.8-arch1-1 x86_64\n\n**Blender version**\nBroken: 2.8x (up to and including fc79d27951)\n\nWhen using the context menu to assign shortcut to a button or checkbox, the shortcut is created in a wrong space, which may lead to error popups when pressing that shortcut with mouse hovering over a different space.\n\n\n1. Load the default scene.\n2. In 3D viewport, expand the Overlays popover, right-click the Wireframes checkbox and assign a shortcut through the context menu.\n3. Note that shortcut works while the mouse is over the 3D viewport.\n4. Move the mouse over the Properties and try pressing the shortcut. You'll get an error popup.\n\nThis is due to the shortcut being created in the Window space, not 3D View space.", "Continuous Grab occasionally fails\nOperating system: Linux 5.9.10-arch1-1 (KDE Plasma desktop)\nGraphics card: NVIDIA GTX 980Ti (455.45.01)\n\nBroken: 2.80 - 2.92 master\nWorked: N/A\n\n\nMouse wrapping sometimes fails to transition screen edges, requiring at least a pixel of backpedaling with the mouse. This seems to affect all mouse-wrapping operators. Initially this report was written in terms of Shear, with which I've discovered this behavior.\n\nMesh edit mode Shear operator sometimes gets stuck on the toolbar side of window, showing the system mouse pointer (perhaps due to mouse passing over the toolbar?), needing at least one pixel of motion to the right to untangle it.\n\n[Video ](PeSL2fzKfT4).\n\nThis does not seem to occur if:\n- viewport is not touching window edge\n- window is made fullscreen\n\n\n- Make sure your window is not made fullscreen and that the 3D viewport is bordering window edges\n- Enter edit mode, select all and invoke Shear operator. Move the mouse continuously to the left, until it eventually gets stuck.", "Sculpt mode pivot ignores object transform when pivot mode is \"Active Element\"\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102\n\nBroken: version: 3.4.0\nWorked: unknown\n\nWhen the pivot mode is set to \"Active Element,\" the sculpt mode pivot location ignores the transform of the object.\n\n- move and/or rotate default cube\n- Set `Transform Pivot Point` to `Active Element`\n- To see the pivot position, enable `Move` Object Gizmos (in popover of `Viewport Gizmos`)\n- enter sculpt mode. (note that the pivot has moved back to origin)\n- Go to {nav Sculpt > Set Pivot} and run any of the `Set Pivot Operation` operators (such as `Pivot to Origin`, `Pivot to Unmasked`, `Pivot to Mask Border`, etc)\n\nThe pivot location will be relative to the world origin, not the transformed object (which is also active).\n\n---\nTo be honest, it's strange to me that operations such as \"Set Pivot -> Pivot to Mask Border\" generate a pivot that's different for different pivot selection modes in the first place --- it's very unintuitive for the pivot location to not appear at the actual (world space, post-transform) mask border when you run an operation that's supposed to set it to that location. I haven't thought through the nuances of sculpt pivot vs 3d cursor vs pivot mode interaction, though, so maybe there's a good reason for this --- in which case take this as UX feedback that I spent an hour trying to figure out why my pivots weren't working before finding this issue :)\n\nAt any rate, the Active Element behavior seems broken", "Inconsistent Grease Pencil auto-keying behavior\nOperating system: Linux 64-bit\nGraphics card: GTX 1080\n\n3.1 and prior\n\nWhen auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe. \n\nAlso, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.\n[GP_autokey_bug.blend](GP_autokey_bug.blend)\n - Open the attached file.\n - Grab (G) a stroke, then right-click to cancel moving it. The keyframe was inserted, even though no change was made.\n # Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!\n\n", "Multiple numerical values are not changing together in Motion tracking workspace\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GT 740M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 376.54\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI was trying some motion tracking stuff by adding a video file and I tried to change \"Pattern Area:\" value of \"Width and Height\" in \"N\" panel by clicking and dragging to select both tabs and then I changed values by typing different value and when I hit \"Enter\" it only changed in first tab. It should change in both tabs.\n```\n ~Attaching video Proof~\n```\n[2019-07-15 20-07-14.flv](2019-07-15_20-07-14.flv)\n\nOpen Motion tracking workspace\nadd a video clip\nadd a tracker\nin the \"N\" panel of the video\nclick and drag in \"Width and height\" values of \"pattern area\" to change them both together\ntype any different value\nThe change of value will be in only one value and not in both.\n\n\n", "pan gesture behaves randomly\nOperating system: macOS-12.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.4.1\n\nHi,\n\nOn external monitor, two fingered pan gesture on a Mac touchpad behaves randomly between orbit and zoom\n\nThis happens when you use the default Orbit & Pan navigation settings. Most of the time it works correctly: You make a two fingered pan gesture and the camera view orbits. But once a while a two fingered pan gesture will zoom the camera view (instead of obiting). As if you are making a pinch gesture (which you are not). I have disabled the pinch gesture on the system level to rule out the possibility that the pinch gesture interferes with the pan gesture. It is not a pinch gesture conflict.\n\nTo me it looks like following is happening. It seems like that although you have multi-touch gestures enabled, the two fingered pan gesture is sometimes handled as if multi-touch gestures is disabled. (When you go to Input > Touchpad preferences and disable Multi-touch Gestures then the camera view always zooms when you make a two fingered pan gesture.) \n\nThis happens about once every minute, and sometimes even a couple times a minute. It's random. When it happens and you don't end the gesture (you keep your fingers down on the touchpad) then you can continue to zoom in and out by moving two fingers left and right. So once the pan gesture handler chooses to zoom instead of to orbit then it is locked in this zoom behaviour until you end the pan gesture.\n\n\nWorkaround: 103973#issuecomment-79513\n\n", "Having a second window open makes top bar dissapear after switching workspaces\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nI created a new window with \"Window\" -> \"New Window\". Then I switched to a different workspace tab on the main window, which made the top bar with all its workspace tabs dissappear. after resizing the window the top bar is visible can be used again. After closing the new window, Blender behaves normally again.\n\n- Started Blender with new file\n- Open new window\n- Move new window to display with 125% scaling\n- Switch to next workspace\n- Switch to next workspace again\n\nworkspaces tab in main window dissapear\n\n\n\n\n\n\n", "NLA strip unexpectedly auto-switching from Hold to Hold Forward\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\n\n\nWhen creating a new action using the HOLD_FORWARD extrapolation, frames to the left of the keyframes will keep the value of the first keyframe, instead of ignore them like they did before and do with NOTHING extrapolation. They now behave like HOLD.\nThey work like normal in strips, just not as the *(orange)* action.\n\n[nla_hold_back.blend](nla_hold_back.blend)\n[2019-07-14 19-08-18.mp4](2019-07-14_19-08-18.mp4)" ]

[ "Mouse wrapping causes erratic movement\nOperating system: Windows 10, 20H2\nGraphics card: Nvidia GTX 1650\n\nBroken: 2.91 - 2.93\nWorked: 2.79 (That I know of)\n\nI first noted this issue on 228330\n\nSometimes, when the cursor wraps around the screen, whatever I am editing will jump drastically in location, scale, etc. I was best able to capture this phenomenon with scaling a cube, but it happens for literally everything; it's not even limited to the 3D Viewport. \n\n\n\n*Note how the cube jumps in scale when the cursor wraps around the edge. That's not a bug in the gif; that's what actually happening.*\n\nI have encountered this issue on multiple computers with multiple mice. I first encountered it in Blender 2.91, but it is possible it has existed longer than that.\n\nBased on the default startup.\n\n1. Select the default cube\n2. Hit `s` for scale\n3. Drag mouse past screen border so it wraps around. Drag it back and forth a couple times and the size should jump." ]

[ "particle system locations not as expected\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.5.14\n\nBroken: version: 3.0.0 Alpha\n\nif i parent an animated cube vertex to a vertex with a particle system and rotate that cube, it works fine. \nIf i copy that vertex with the particle system to another position - the locations get a bit weird.\n\n- tab -> edit mode\n- select vertex\n- Shift-D -> double vertex\n- Mesh -> Separate -> selection\n- rename that to vertex (not important, just for me)\n- add a default particle system to vertex\n- select vertex, ctrl select cube -> edit mode -> ctrl-p\n- select vertex -> origin to geometry -> run\n- works fine\n- select cube, insert keyframe scale/rot/loc\n- go to frame 100\n- location.z: 8 rotation.z: 360*8 -> keyframe both\n- run, works fine, all locations as expected\n\n- select the vertex\n\n- shift-d X -2\n\nrun -> weird location \"disorders\"\n\n\n[particle_bug.blend](particle_bug.blend)\n\n---\nor\n\n- open .blend file\n- select Vertex from outliner\n- {key Shift D} and place the duplicate Vertex anywhere\n- Play animation\n\n[#90494.blend](T90494.blend)\n\n---\nVideo:\n[particle_bug.mov](particle_bug.mov)", "Sculpting - Cloth brush - Snake Hook deformation not working\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\n\nBroken: version: 3.5.0 Alpha\n\nThis is the image I got after kept dragging my cloth brush around the same spot for a few times:\n\n\nand this is the file I'm using:\n[20221206_sculpt_cloth_brush_snake_hook_donot_work_0001.blend](20221206_sculpt_cloth_brush_snake_hook_donot_work_0001.blend)\n\nI personally think the option is 'wired' to a wrong block of code.\n\n", "UV map inconsistency after bevel modifier\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nMesh position in edit mode affects how bevel processes UV map\n\nIn attached file translate selected part of mesh along world Z axis -> UV is changing position\n[bevel_uv_issue.blend](bevel_uv_issue.blend)", "Rigid body doesn't work when collision is set to mesh, deform and deforming\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: Radeon RX Vega M GH Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.37.04 30.0.13037.4001\n\nBroken: version: 3.2.1\n\nThe rigid body simulation doesn't work with objects using collision with mesh, deform and deforming.\n\n* Make a plane, subdivided\n* Give it a wave modifier\n* Set up the rigid body type: dynamic, active, animated; collision: mesh, deform and deforming.\n* Use another object make it rigid body active\n* Run simulation\n* Sometimes works and when changing rigid body substeps per frame doesn't work at all (well sometimes works but when it does things jump out of control not like in Blender 2.79)\n\nIn Blender 2.79 works perfectly\n\n\n[Wave simulation 3.2.blend](Wave_simulation_3.2.blend)\n\n[Wave simulation 2.79.blend](Wave_simulation_2.79.blend)\n\nBlender 3.2\n\n\n\nBlender 2.79\n\n\n", "Metaball particles are handled inconsistently in Geometry Nodes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.7.1.220725\n\nBroken: version: 3.4.0 Alpha\nWorked: (n/a)\n\nMetaball rendered via particles are handled inconsistently in Geometry Nodes. It seems only mesh related nodes are generally working well with them.\n\nI wasn't sure about reporting this as a bug, because I assume that compatibility with the particle system is probably not intended use case. I guess ability to access metaball particles at all is an unintended bonus from eaa87101cd5a? I'd argue that if this can be easily \"fixed\" it will open up some interesting use cases before actual simulation/physics nodes arrive, but this is a borderline feature request and I guess developers will decide if this is worth to look at at this point.\n\n\n[MetaballParticles.blend](MetaballParticles.blend)\n[MetaballParticles.mp4](MetaballParticles.mp4)", "Bone's Transformation constraint numbers won't be symmetrized correctly.\nOperating system:Windows 10\nGraphics card:RTX 2070\n\nBroken: 3.3.1\n\n[Use this file](https://projects.blender.orgattachment)\n\nThis will break:\n\n- open the blend file\n- delete the selected Left bone\n- select Right bone and symmetrize it\n- check both Right and Left bones' Transformation constraint setting. Numbers on the Left one will be messed up.\n\nBut this works:\n\n- delete the selected Left bone\n- go to pose mode\n- select the Right bone\n- go to edit mode again and symmetrize it\n- Transformation numbers are both fine. \n\n------\n\nOriginal description:\n\nWhen Bones have Transformation constraint and are symmetrized in edit mode, its numbers are symmetrized correctly too.(Map from numbers like Location X min , Location X max and Map to numbers like Location min max etc) but if Transformation constraint's Target and Owner space are set as not Local those numbers are totally messed up and broken.\n\n", "Curve extrude offset default value is 1 (instead of 0)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 5500M ATI Technologies Inc. 4.5.13587 Core Profile Context 19.40.30.02 26.20.14030.2002\n\nBroken: version: 2.93.0\nWorked: -\n\nCurve > Object Data Properties > Geometry > Offset\nIf you reset the \"Offset\" value with right click+*Reset to Default value* or by pressing backspace the value is set to 1\n\n - Open blender\n - Create a curve\n - Extrude it\n - Reset the offset to the default value\n - Offset is set to 1 instead of 0\n\n**Expected behaviour**\nThe default value for this should be 0. If a curve is created the value is 0 without any changes\n\n[curve reset offset.blend](curve_reset_offset.blend)\n", "Geometry Nodes Mesh Boolean unexpected difference result\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 83\n\nBroken: version: 3.5.0 Alpha\nWorked: none\n\nGeometry Nodes Mesh Boolean Difference does not work as expected.\nNode setup:\n\n\nUnexpected boolean difference:\n\n\n- Open the attached .blend file\n- Press G to move the selected Cube.001 and the small cubes will flicker.\n# At certain positions of Cube.001 some of the small cubes will disappear when they should not.\nThanks!\n[test06.blend](test06.blend)\n", "Broken Twist on meshes deformed with Particle Instance Modifier with Along Path\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.90.1\n\nThe twist of a mesh deformed with the Particle Instance Modifier with the Along Path option seems broken, more noticeable with steep curvature in hairs. I compare it to the Curve Deform modifier as an example of proper deformation. Now, you may say it's an unfair comparison given that curves have an explicit twist that you can modify, unlike hairs. But even without controlling the initial twist of the hair, it's broken in a couple of ways.\n\nFirst, it deforms the mesh unevenly, with some vertices twisting more than others, even in a case where vertices are completely equidistant around the origin and both origins are aligned, like the cube in this image. The selected face and the edgeloop here should be squares but aren't, unlike in the curve deform modifier \nSecond, when changing the length with the Position Slider, the whole thing seems to change twist at once. Instead of having a consistent twist on each point of the path [Particle Instance Mod bug2.mp4](Particle_Instance_Mod_bug2.mp4)\nAs a side note, when using Along Path, finding how to orient your mesh to the hair is unintuitive, always using the global Y axis as the length axis in which I added subdivisions but then twisting weirdly when changing the Axis option in the modifier, I settled for Z in this example.\n\n\nAttached is the same file used in the video, you can open it and move the Position slider in the Particle Instance Modifier, the scale of the Curve Deform modifier example is driven by it so you can see both changing in real time.\n\n[ParticleInstanceTwistBug.blend](ParticleInstanceTwistBug.blend)\n\nWhy do I think this is happening? Well, if you select the object with the particle system, go to the particle properties, and change the length of the hair under the Render>Timing>End subpanel, you can see the problem is the same, basically the twist changes with length. Maybe the modifier should do something different and get the twist from the whole length particle and then scale the mesh instance before deforming or something like that, idk\n\n", "Armature > Symmetrize doesn't symmetrize Inverse Kinematics constraints correctly\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.93.0\nWorked: non\n\nWhen one Armature > Symmetrize a bone, the IK constraints aren't correctly symmetrized. For example, IK constraint Limit Z (Min -180°, Max 10°) is symmetrized as (Min -180°, Max 10°), while the proper symmetrized result should be (Min -10°, Max 180°). Note that this behavior is inconsistent with how Limit Rotation constraint works. When using Armature > Symmetrize, Limit Rotation Z (Min -180°, Max 10°) is symmetrized as (Min -10°, Max 180°), which in my opinion, is the correct result.\n\n\n1. Create an armature\n2. Create a bone at (1, 0, 0)\n3. Set Bone Properties > Inverse Kinematics > Limit Z (Min -180°, Max 10°)\n4. Enter Edit Mode\n5. Armature > Symmetrize\n\n", "Decimate modifier gives different result on every evaluation\nOperating system: Linux-5.4.0-122-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.129.06\n\nBroken: version: 3.2.2, 3.3 latest\nBroken: 3.1.2\nWorked: 3.1.0\nWorked: 2.93.8\n\nCaused by fb2cb0324a\n\nA mesh with decimate modifier gets topology rebuilt on each frame of Cycles render. Notice that a new cones object on the right is not broken.\nThere's something wrong with the left object. I checked every property I could think of.\n[0001-0250.mp4](0001-0250.mp4)\n[decimate_bug.blend](decimate_bug.blend)\n\nOpen the file. Render a sequence.\n\n", "Angle based UV-unwrap: distorted UV island with even angles on geometry\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 640/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\n\n\n\n\n[2020-06-21_18-02-13.mp4](2020-06-21_18-02-13.mp4)\n[untitled.blend](untitled.blend)\n", "Principled BSDF Anisotropy black faces\nWin10, 1080Ti\n\nBroken: 2.79\n\nIt seems that using anisotropy produces black odd artifacts under certain mesh circumstances. I don't think this happens often as it seems the actual mesh caused it, possibly by being a little bit too symmetrical? \n\nI suppose often it goes unnoticed so I thought it might be good for someone to investigate upon if there isn't some inconsistency.\n\nRotating the object by the tiniest bit helps (probably helps by something being non 0 ^__^).\n\nMoving random vertices randomly produces different results that are often completely correct or at least 50% correct. Good to try that in Rendered mode.\n\nScreenshot: \n\nBlend: [Anisotropy_Bug.blend](Anisotropy_Bug.blend)", "Nodes: Different mouse drag effect for float properties\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.5.0 Alpha\n\nDrag step inconsistent of float data type that between of geometry nodes in modifier and editor.\nAnd float of vector also.\nThis caused the mouse to drag far to reach the maximum value when going from 0-100.\n\n\n[drag_step.blend](drag_step.blend)\n\n", "Baked Particles are rendered incorrectly on frame 0 and below\nOperating system: Windows 10\nGraphics card: Geforce RTX 3070\n\nBroken: Blender 3.3.5, 3.3.8 ,3.3.7, 3.6\nWorked: Unknown\n\nWhen rendering baked particles systems that have a baked frame on Frame 0 (or below) particles are rendered incorrectly.\nParticles are rendered on the emitter instead of their correct position.\n\n\n- Open the attached blend file (Note: Particles are now displayed incorrectly even in Viewport on Frame 0)\n- Skip 2 Frames ahead in Timeline\n- Go back to Frame 0 (Note: Particles are now displayed as expected)\n- Render Frame 0, Note: Particles are rendered on the surface of the emitter, which is different from what can be observed in the viewport.\n\n" ]

[ "Rigid Bodies do not interact properly when animated\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 2070\n\nBroken: Tested on 2.93.6, broken on assumedly many more\nWorked: Unknown\n\nRigid bodies do not interact with each other properly when one of them is deformed via Armature Modifier.\n.\n- Add an Object as a Rigid Body (Passive, Animated), and rig it to an Armature.\n- Have the bone(s) controlling said Rigid Body be animated (e.g setting an axis of rotation to #frame/30)\n- Add another Object as a Rigid Body (Active) to interact with the first one\n- The Passive Object moves, but the Active Object will only interact with it as if the Passive Object is stuck on Frame 1.\n\nThis could be due to how the Rigid Body settings are not considered a Modifier like Collision, Cloth, Dynamic Paint, or Fluid (reinforced by how a Cloth Object interacts correctly with a Collision Object deformed by an Armature Modifier)[rigidbodyissue.blend](rigidbodyissue.blend)" ]

[ "GPU Subdivision not optimized in Weight Paint mode\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\nI'm not sure if it's unimplemented/unplanned or just overlooked, so I'm here to report in case.\nWhen you have a mesh using an Armature modifier and Subdivision modifier, the Subdivision will affect performance while posing the armature but enabling GPU Subdivision will noticeably improve performance during posing and animation. \n\nHowever, if you select the armature and the mesh and go into weight paint mode, allowing you to pose the rig, the GPU Subdivision will not boost performance with the Subdivision modifier. Weight Paint Pose is slower regardless as to the Subdivision modifier, just GPU Subdivision seems to be disabled here. \n\n- Open attached .blend file\n- Make sure `GPU Subdivision` is enabled in Preferences\n- in Weight Paint Mode, pose the rig (move any bone)\n- Go to object mode, select the rig and go to Pose mode\n- Compare performance when posing the rig\n\n[#101485.blend](T101485.blend)\n", "Bone IK constraint - add lockable axis properties for stretching\n*Adding task after e-mail conversation with Sybren 2020-12-17*\n\nThe bone IK constraint can activate stretching on the constrained bones if constrained bones has \n\n**Properties / Bone properties / Inverse Kinematics / IK Stretch > 0**\n\nexample:\n```\nbpy.context.object.pose.bones[\"Bone.005\"].ik_stretch = 0.01\n\n```\n\nThe problem is that the constrained bones stretch in all axes and not only in the +Y axis of the bone, which results in unwanted \"scaling\" of each bone. \n\n---\nHere is a video showing the issue:\n\n[ik stretch.mp4](ik_stretch.mp4)\n\n---\nMy suggestion is to fix this by adding properties to each bone that show the resulting IK stretching per axis on each bone. These properties should be readable (for drivers) but not possible for the user to change, since the stretching is generated. The property should be lockable by the user in order to fix any unwanted scaling on a specific axis.\n\nAnother solution is to add properties that is a factor (multiplier) to the scaling/stretching per axis. The upside is that the user can change the values, but the downside is that the user does not have a property to read the generated IK stretch values. \n\nI leave it up to you to decide what is the most \"blender way\" in regards to implementation.\n\n\n", "Bones displayed as stick don't have an active color\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.2\n\n\nBoth bones in the image above are selected, but which one is active?\n\n1. Set a rig to display their bones as stick.\n2. Select two bones.\n\nTest File:\n[#90923.blend](T90923.blend)", "Unable to add drivers to bone collections visibility\nOperating system: Windows 11\nGraphics card: RTX 4060ti\n\nBroken: 4.0.0 Alpha 2023-09-06\nWorked: Before bone collections were merged\n\nThis kinda leans into feature requests, but it is a regression nonetheless. Drivers also weren't acknowledged from what i could see.\nBefore bone collections were recently introduced, you could add a driver to each layer to influence it's visibility, and i know many people liked to use that in order to influence the visibility of a group of bones. Currently you cannot influence the visibility of a bone collection through drivers, the only option to do it now being controling the visibility of individual bones.\n\nN/A\n\n", "Improve upon the automatic weight paint assignment by using Bone Glow\nBlender currently uses the *Bone Heat*algorithm to automatically assign bone weights to a mesh.\n\nThe proposed *Bone Glow* algorithm improves over *Bone Heat* by fixing cases where it behaves poorly.\n\ndownload?doi=10.1.1.156.4787&rep=rep1&type=pdf\n\nThe provided example images should look very familiar to anyone that has used Blender's Bone Heat.\n\n", "Armature Symmetrize silently does nothing when no bones are selected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 27.20.100.8729\n\nBroken: version: 3.5.0 Alpha\nWorked: never AFAIK\n\nArmature Symmetrize does nothing when there are no bones selected.\n\n1. Open the attached blend file\n2. In the Armature menu, choose Symmetrize.\n3. See nothing happening. This is what this report is about.\n4. Press {key A} to select all bones.\n5. Run the Symmetrize operator again.\n6. See that the armature is now symmetrized. This is what I'd expect to happen when no bones are selected.\n\nExpected behaviour would be that when nothing is selected the armature gets symmetrized as if all bones are selected.\n\n[symmetrize-bugreport.blend](symmetrize-bugreport.blend)", "Add error message feedback on constraints, similar to what already exists for modifiers.\nCurrently de-activated constraints only show their status through a small red icon. It would be better for users to also show an error message explaining what is the issue, similar to what modifiers already do.\n\nSee e.g. the invalid settings for the IK constraint of the first bone in this file from #100128: [lib.blend](lib.blend)", "Hiding Armature in Outliner while in Pose Mode, leaves viewport without ability to select or exit the Pose Mode.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0\n\nWhen Armature is hidden via Outliner in Pose Mode, the selection, active object, and the Mode remains on that armature, not allowing to select anything anymore. Same happens with Meshes and Edit Mode, but one is still able to exit the Edit Mode. I assume it's likely that one either shouldn't be able to hide the object one is in Edit/Pose mode with, or the Mode probably should be exited upon hiding it's object. Or, at least, switching the Mode off shouldn't be disabled if the object is considered still active/selected.\n\n[armature.blend](armature.blend)\n - Select Bone,\n - Press Disable in Viewports for Armature object in Outliner,\n - > Can't select other objects in viewport now, or exit the pose mode.", "Bug: Extrude faces along normals + \"Individual origins\" pivot point\nOperating system: Windows 10 64-bit\nGraphics card: NVIDIA Geforce GTX 960M\n\nBroken: 2.80 957b4547aeeb 2019-01-28 22:11\nWorked: Set the piviot point option to anything else, such as bounding box center, 3D cursor, etc.\n\nWith pivot point set to **individual origins**, the tool **Extrude faces along normals** don't work properly. It just acts like the **extrude** tool.\n\nVery simple. open the startup file with a cube, set the pivot point to **individual origins** and use **extrude faces along normals**(Alt+E) inside the edit mode.", "Blender development todo list -- Tools (migrated from wiki)\nNOTE: this is a direct dump of Tools (without cherrypicking the valid items)\n\n\n# Scene\n\n**New scene - Full Copy**\nSeveral things are still not copied or reassigned when using this tool:\n- [ ] Particles - Not even the particle systems themselves, not to mention re-assigning 'objects' pointers to copied IDs too, see #40891.\n- [ ] Textures when they are only used by e.g. modifiers (i.e. not by a material, world or lamp).\n- [ ] Textures used by modifiers are not re-assigned to new copies when possible either (only objects are handled).\n\n# Library System\n- [x] Hard (or even impossible) to relocate libraries that have been moved (#44958). Addressed in id-remap branch, hopefully merged in 2.78.\n- [ ] 'Find Missing Files' does not work with .blend lib files (impossible with current master, easy to do once id-remap is merged, see #47774).\n\n# Transform\n- [ ] API and draw code for manipulator needs to be redone still. For this reason no manipulator drawing happens during transform.\n- [ ] Manipulator click behavior (left-click-release a manipulator axis to enable a transform on that axis -> perform transform and wait for another left-click to confirm. Expected behavior from 2.4x)\n- [ ] Operator parameters in toolbar don't have to be drawn all always, needs cleanup.\n- [x] Transform redo fails when you change mode during transform (use R S G keys).\n- [x] Mirror of rotated objects doesn't always work correct #37928\n- [ ] Numeric input for rotational transform resolves to modulo 360. Should it? #40167 - ''possible fix included''.\n- [ ] Transform along the axis does incorrect axis projection in certain circumstances #40893\n- [ ] Scaling from zero is not possible with 'S' shortcut (#44551).\n- [ ] Transform redo fails when mouse move is required (#50419).\n- [ ] Apply Scale: Option not to scale all object properties (curve radius, empty scale, text scale... etc). \"Scale Properties\" toggle.\n- [ ] Cursor input to calculate rotation can accumulate a small amount of error (impacts bend and rotate) #53590\n- [ ] Armature edit-mode transform proportional editing doesn't work (#53992).\n\n**Transform Snap**\n- [x] Snapping to vertex slide (Taking into account multiple selections)(#48927).\n- [x] Snapping to face local axis doesn't snap the vertex to the face surface (#38438).\n- [ ] Snapping to self doesn't work with proportional edit-mode (#44793).\n- [ ] Snapping doesn't work for Boolean modifier (#35023).\n- [x] Snapping in object mode rotates object around their origin, instead of rotating them around their snapped point (#42362).\n- [ ] Snapping doesn't behave as expected when having several parented objects (#41199).\n- [ ] Snapping between multiple objects can give some working-as-intended, but in practice quite undesirable behavior (using bounding box) (#47171).\n- [ ] Snapping falls back to using a grid, however this isn't clearly communicated<br>(advanced snapping on faces, vertices, etc. only works on move/rot/scale, see #42798).\n- [ ] Snap to cursor and snap to grid could be made to work more consistently: See (#34441)\n- [ ] snap_project individual element on surface of other objects - watch?v=XrEPpHGoKlk&feature=youtu.be&t=1m10s;\n- [ ] Snap does not work for NURB surfaces (#78434);\n\n# DupliObject\n- [ ] There is no good way to control the rotation of objects in DupliFaces option (rotation is computed from face normal (which is good) and first three vertices of the polygon (which is weak, epic fail with e.g. Mirror modifier). See #37365.\n- [ ] Duplifaces don't work well with the mirror modifier, see #37820.\n\n# Curves\n- [ ] Capping front / back -ends of beveled curve doesn't work, see #26136\n- [ ] Constructive modifier kills generated UV mapping on bevelled curves, see #27411\n- [ ] Surfaces Make Segment rotates U/V even when it's not actually needed, see #31480\n- [ ] Couldn't cycle through vertices with the same location using mouse selection, see #36760\n- [ ] Curve tessellation might work not as it's expected to, see #37386, #40171\n- [ ] Curve deform doesn't work if curve is zero-scaled #38907\n- [ ] Nurbs clamp order by total number of points, this should be clamped at runtime #40378\n- [ ] Handling of non-smooth control points with (Bézier/poly) curves in general, and their rotation in particular, could be improved when generating BevelList & Path, see #44393.\n- [ ] In some cases Bevel should prefer \"clip\" behavior over trying to keep constant shape across the path #50720.\n\n# Text objects\n\n- [ ] Font formatting interface should be improved (#49599)\n- [ ] Default Bfont doesn't support russian characters (or any other non-european charset) in text object, while UI does show Russian characters (#53744)\n\n# Metas\n\n- [ ] Some shapes (Cube) for eg. draw far outside the tessellation bounds making them hard to select. see #47455\n\n# Meshes\n\n**Mesh Editing**\n- [ ] Knife & loopcut\n - [ ] Knife/loop cut need to work properly with operator properties/redo\n - [ ] Restore Quad Corner Cut Methods (Innervert, Fan and Path) for Subdivisions and Knifecut\n - [ ] Knife cuts side-on, intersecting the entire face, could be detected and ignored #43816\n- [ ] Mirror edit mesh operator (Ctrl M) fails to flip normals leaving an incorrectly mirrored mesh (turns normals inside)\n- [ ] Add option to disable n-gons usage for tools (might be useful for some usages) (see #31268)\n- [ ] 'Checker deselect' could be modified to work in some cases where it currently fails, (see #34544)\n- [ ] Merge meshes: add option to join UVs (and other CD layers!) by names rather than index (see #36749).\n- [ ] toolbar mesh Extrude operator inconsistency (see #36977).\n- [ ] Shape keys: Enhance memory usage (not storing vcos for unchanged vertices? See blender/blender-addons#39287).\n\n- [ ] Bevel\n - [ ] Better handling of profile=1, profile=0.25, and implement profile=0 cases (see #39132 and #38458 and #40278).\n - [ ] Generalize to handle several manifold sheets touching at a point (see #34678).\n - [ ] Improve clamping code (see #38871).\n - [ ] More options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n - [ ] Treat more cases like \"pipe\" to avoid bulges (see #40258)\n - [ ] Option to have bevel not create n-gons (see bf-funboard thread)\n - [ ] Sometimes leaves degenerated geometry (#48174)\n\n- [ ] DataTransfer/Geometry Matching\n - [ ] Add 'matching' algorithms based on 'similar shape' rather than simple items proximity/raycasting (see #46762 for a usecase) - WARNING: most likely advanced, mathy project!\n - [ ] A review of islands handling could also be useful, current code is rather complex and not so efficient.\n\n- [ ] Discussion\n - [ ] Extrude behaviour on cancel, see (#23492).\n\n**Text Editing (3D)**\n- [ ] When converting beveled text into a mesh - there are many doubles.\n- [ ] Text object requires better integration with the system clipboard, #38556, #46330\n- [ ] Support font kerning (#47725).\n\n**UV Unwrapping**\n- [ ] Settings for pack margin in different operators behaves inconsistently, see detailed description: 039547.html\n- [ ] Remove doubles has an option to Merge with unselected verts, This would be very handy for welding also.\n- [ ] Detect convex mesh without seams on unwrap and print warning.\n- [ ] Unwrapping fails on a particular strange topology (#31145)\n- [ ] Unwrapping for concave polygons is badly supported #41810\n- [ ] Face/edge selection in UV Editor does not work same as in 3DView (#52276).\n\n; Not ported from 2.4x\n- [ ] Click Project from face\n- [ ] Consolidate into one image\n- [ ] Billboard render on active\n- [ ] Unwrapping could run out of stack size for tricky geometry #42524\n\n**Vertex Paint**\n\n- [ ] Undo in vertex (and weight paint) behave differently to sculpt/project-paint modes regarding undo steps #52993\n\n### Sculpt & Paint\n\n**Sculpting**\n- [ ] Check documentation and fix hotkeys which could be useful for artists (or remove redundant hotkeys and update documentation), see #26017\n- [ ] Grab + symmetry can make things shoot off more quickly than they should (strength of movement is being double counted), see #25370\n- [ ] Not all drawing modes supports PBVH drawing, see #32454, #38608, #38609\n- [ ] Not all shading modes are supported for dyntopo, see #34010\n- [ ] Hidden faces are treated as hidden by sculpt tools but when PBVH drawing isn't used, the hidden faces display (and cant be edited), see #33078\n- [ ] Multires modifiers: makes mesh invisible after leaving sculpting mode, see #36591\n- [ ] Multires sculpt: artifacts grabbing between different levels #40465\n- [ ] Dyntopo does not support restoration when aborting a stroke, see #46456.\n\n**Painting (3D)**\n- [ ] Solve projection paint issue when one vertex in a face in behind the view in perspective mode<br>index.php?func=detail&aid=26393&group_id=9&atid=498\n- [ ] Continue to unify paint modes\n - [ ] Consistent brush texture mapping across paint modes (sculpt/tex paint/proj paint).\n - [ ] Consistent brush options, eg. 'Rake' or 'Anchored' in texture paint.\n- [ ] Make paint of displacement texture apply real time on model (optional). (#24657)\n- [ ] Allow view center to work for selected/active face in WPaint mode.\n- [ ] Viewport navigation for painting modes can be improved #48113\n- [ ] Users can perform strokes which apply to a huge number of pixels (by accident) - this could be handled gracefully #52351\n\n**Painting (2D)**\n- [ ] Clone image painting should support the same translation/rotation/scale tools as stencil texture mapping.\n- [ ] Stepped lines in image editor painting, blending should use float coordinates and interpolate (#52610)\n\n\n**Grease Pencil**\n- [ ] Default attach point of GP data is confusing ((#21969))\n- [ ] GP ignores color management ((#50149))\n\n### Materials\n- [ ] Improve handling of linking of materials to Object/Data. Right assigning a material-less data to object the materials from object are gone too (blender/blender-addons#23805, #52484).\n- [ ] Fix EnvMap update, it can depends on many different things in the scene (#41900).\n\n### Modifiers\n- [ ] Make (at least some) generative modifiers to handle custom normals (like e.g. mirror one, see #44058).\n\n**Array Modifier**\n- [ ] Has been re-written to use bmesh, making 2.63 slower then 2.62, There are areas where speed could be improved, for full info see #30695\n- [ ] Textures from cap objects are completely ignored and no way to override them, see #33578\n\n**Boolean Modifier**\n- [ ] Boolean modifier does not preserve vertices/edges data, see #32203, #33548\n- [ ] Issues with degenerated faces, see #30447\n\n**Decimate Modifier**\n- [ ] Limit decimation along seams (UV vertex color, etc), see #32203\n\n**Explode Modifier**\n\n- [ ] Does not preserve UV maps when using Cut Edges option (#46514)\n\n**Multires Modifier**\n- [ ] Only solid draw mode uses optimized drawing\n- [ ] \"Applying Base\" gives spikes on lover levels sometimes, see #35560, #37997\n\n**Bevel Modifier**\n- [ ] Does not preserve edge custom data, see #35314.\n\n**Simple Deform Modifier**\n- [ ] The bend/taper/twist options use fixed axis, add XYZ options would be nice. #33712\n\n**Skin Modifier**\n- [ ] Skin modifier very slow in some cases, see #40770\n\n**Solidify Modifier**\n- [ ] Curves tesselation creates zero area faces which solidify doesn't handle well #52170\n\n**Remesh Modifier**\n- [ ] Mesh data at extreme distance from origin (2**24), crashes #47209<br>''Note, this is a real corner case - yet its a bug because it shouldn't crash.''\n\n### Physics\n- [ ] Allow using multiple baked caches on a single object (having different frame ranges), see #41896.\n- [ ] Bullet: High memory usage for objects that don't have scale applied (#35799)\n\n**Baking**\n\n- [ ] Generic issue: baking ignores making pointcaches when modifier preview has been disabled. Doesn't need fix - but let's keep track of this for future work.\n- [ ] Point caches do not work well with time remapping (example #35968)\n\n**Cloth**\n- [ ] Proper handling of rendered subframes without baked pointcache, for more info see (#21948)\n- [ ] Proper handling of different vertices placed at the same position with \"Soft Body Self Collision\" option turned on (see (#26956)).\n- [ ] Cloths doesn't allow preview during bake (see (#30490)).\n- [ ] Dupli-group cloth in NLA fails (#29838)\n- [ ] 'Emit from: verts' not working as expected when deforming #36237\n- [ ] Collision of hairs doesn't works properly #39219\n- [ ] Memory optimizations are possible for cloth #42577\n- [ ] Cloth pre-roll feature is totally weird and needs reconsideration #40103\n\n**Collisions**\n- [ ] Collision modifier updates it's data structure even if there are no physics that need it (can be slow), a check should be added to make sure the data is actually needed, see (#26965).\n- [ ] Force fields and collision objects are not included in DupliObjects. This is mostly a design decision (duplis being a purely visual feature), but would be nice to support at least in groups. #35264 #36300\n\n**Hair**\n- [ ] Better handling of collisions & force fields for dynamic hair\n- [ ] Wave kink direction is totally uncontrollable, probably there needs to be a way to define hair tangent direction in particle edit mode.\n- [ ] Adding hair in particle mode only uses the deformed mesh, see (#25689).\n\n**Particles**\n- [ ] Particle emission between frames is only accurate for object level emitter/parent animation, for parenting or constraints an interpolation method needs to be implemented, but before this can be done pointcache code has to get some changes too. See (#36516) for more details.\n*; Parent animation is now supported {{GitCommit|c24a23f. Similar issue still persists for non-animated parents (e.g. rigid bodies) though #39923\n- [ ] Reactor particles\n- [ ] Conversion from some old files could be better\n- [ ] Vector blur + particles being born/dying doesn't work properly, see (#23320).\n- [ ] Metaballs don't work with particles when the particle view setting isn't \"render\", see (#25794) for more info.\n- [ ] \"Constructive modifiers before particles\" is still an open issue, but some way to handle this gracefully would be really nice, see (#25838) for more info.\n- [ ] Density of particles can't be animated with animated textures, see (#28212).\n- [ ] Instanced objects do not show in particle edit mode, see (#28431).\n- [ ] Issue with ghosting particles if you don't bake first. (#28116)\n- [ ] Linked groups: Force fields and guides only work if you use \"Effector Group\" feature, set to its own group.\n- [ ] Particle Hair dynamics: stops working after using \"Add tool\". (#30557)\n- [ ] Instanced objects don't draw in Particle Edit Mode. (#31913)\n- [ ] Child particles Interpolated mode only works well for Hair, for other particles it doesn't take particle lifetime into account. (#33390)\n- [ ] Particle emission doesn't support NGons.\n- [ ] Particle Object duplication doesn't work with Mirror modifier (#34705)\n- [ ] Particle systems fail to duplicate for smoke simulation (#34705)\n- [ ] Random distribution of particles fails in specific setups (#35598)\n- [ ] Default point cache step of 10 frames fails in some cases, see #38563\n- [ ] Particles tangent rotation control by vertex group missing, see #35103\n- [ ] Texture doesn't affect grid particles #40404\n- [ ] The particle system needs to be set to 'Newtonian Physics' for texture to influence the size, and with global gravity turned off #28263\n- [ ] Multiple issues with particles rotation #32340, #44088\n- [ ] Particles hidden in viewport reappear during rendering #40463\n- [ ] Particle initial speed is not properly inherited from the parent #41305\n- [ ] Point density textures can not be used to control particles #44901\n- [ ] Particle duplication in general is rather poorly implemented (no relink of used datablocks, no duplication of psettings ID when duplicating objects, …) #45843.\n- [ ] Grid distribution only supports From Dupli Generated, but not UV. Potentially could use nearest face. #48928\n- [ ] Particles aren't spawned correctly, they are sometimes generated at the same location as other particles, or at the object's origin. See #50135 for one scenario.\n- [ ] Particle editmode could have its 'own' [X-mirror] option (and not reuse editmode option). See #53872\n\n**Rigid Body**\n- [ ] Velocities are not cached, which prevents a proper state update when cache has time gaps #50230.\n\n### Image & Video\n\n**Compositing**\n- [ ] DOF Defocus node: fStop close to 128 fails to give good results, stay away from that value! (#24534)\n- [ ] DOF node gives no realistic results as users expect, documentation needs upgrade for it.\n- [ ] Defocus node is very slow when large blur radius is needed, could be optimized somehow (mipmap, summed area table?) (#29481)\n- [ ] Defocus node does not work nicely without a camera controlling the blur radius. This makes external compositing workflows with defocus difficult. At the heart of this is a design conflict, because defocus is not a true postprocessing effect #36745\n- [ ] Fast Gauss (Gabor filter, Young/VanVliet) has bad results for edge cases. Needs image processing guru (#25543)\n- [ ] Check on DPX and ASC_CDL and (#27377)\n- [ ] Map UV makes mapped images blurry, see #31868\n- [ ] Some nodes does not preserve alpha channel replacing it with fully opaque, see #32580\n- [ ] With new compositor, on loading files a compositor doesn't start (for existing buffers), so viewers remain empty as well. #35417\n- [ ] Ghost Glare is of limited use, needs clarification and probably a more sophisticated generic lens flare alternative #30389 #36488\n- [ ] Some node inputs require a single constant value and don't work with image-based per-pixel values (#36585). This leads to confusion when nodes apparently don't work, because nothing prevents linking such variable values into constant inputs. Compositor nodes should keep track of constant values and limited inputs on the node level (also in node groups!).\n- [ ] Compositor gives unexpected results with specific curve mapping due to precision loss, see #36621\n- [ ] \"Full Sample\" merging does not work with the File Output node, sample merging happens only for render result outside compositor. Real-time editing might also be improved to deal with samples better (#36811, #39143)\n- [ ] Accumulation method in the Lens Distortion node causes artifacts on noisy input #37462\n- [ ] Compositor does not support render slots #43260\n- [ ] Scaling down produces artifacts due to lack of ellipse filtering of sampler #51070\n\n**Image formats**\n- [ ] Upgrade our DPX code to read newer or different versions, copy the ImageMagick code? (#24716)\n- [ ] No support yet to output images in user chosen color space. (#37650)", "How to integrate multi-frames icons/preview images in UI code\nSo, to support one preview per pose of a PoseLibrary (first use case, many more are possible later), multi-preview (or preview frames) is being added to Blender (see [the branch]() for details). \n\nThe main issue I’m facing here is how to use those 'frames' of preview images. I can think of two solutions, neither are really ideal to my taste (went with first one in current branch):\n- Introduce the concept of 'frames' of an icon. You basically have to pass an extra value to UI API functions, the frame of the icon you want to use. This is simple and rather powerful, drawback here is that you'll ultimately have to change the whole UI API, which will be awfully… verbose.\n- Generate one icon ID per frame of the preview image. This is simpler, but can lead to a huge amount of generated icon id’s (with matching Icon data), imho it’s really not worth the overhead.\n\nWouldn’t mind having your feelings here, or even better if you have other ideas, before I change whole UI api…", "Cycles: Viewport rendering is restarted when selecting bone in a rig with drivers\nOperating system: Linux-5.15.11-76051511-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.2.0 Alpha\nWorked: Unsure, possibly never\n\nWhen selecting bones or objects in very simple cases, the Cycles viewport rendering is not interrupted.\nHowever, if the armature has any drivers on it, selecting a bone will restart the viewport rendering.\n\n- File: [re_render_on_bone_select_with_drivers.blend](re_render_on_bone_select_with_drivers.blend)\n- Start viewport rendering.\n- Select one bone or another.\n- Viewport rendering is restarted on every selection.\n\n- Remove the driver from the bone's X location.\n- Issue is gone.", "Enhance ways of accessing active modifier for poll functions of operators\nCurrently, poll function of operators can only get the modifier they are supposed to work on from the context. This is often missing (when called from shortcuts e.g., also with drag-n-drop of modifier panels...).\n\nThis is a sever problem for liboverrides, as some modifiers should then be edited (the locally added ones), and others not.\n\nI can see two ways to solve that: \n \n- Add current 'active' modifier to context (not sure how, or even if, this is always possible).\n- Work around the issue by adding some kind of second 'polling' helper function to be used from invoke/exec functions (since when not found in context, those use event to get the modifier to work on, but events are not passed to poll functions).\n", "Drawing of pose markers does not take NLA time mapping into account\nOperating system: Linux-5.11.0-49-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.2.0 Alpha, branch: `master`, hash: `d6e7241237`\nWorked: don't think it ever workerd\n\nShifting an Action on the NLA, then going into tweak mode to edit it, shows the keyframes shifted in the animation editors. The action's pose markers are still in their absolute position.\n\n\n\nThe pose markers should align with the 2nd, 3rd, and 4th keyframe.\n\n- Open the attached file, look at the pose markers.\n- Drag the action in the NLA editor, and see the keys moving while the pose markers stay put.\n\n[[D14176](D14176)-select-markers.blend](https://archive.blender.org/developer/F13001132/D14176-select-markers.blend)\n\n**Context & Relevance**\n\nThese \"pose\" markers originated from the old, now obsolete, pose library. However, regardless of the status of that library, I've heard the desire to have Action-scoped markers (so independent of scene time), and the pose markers would fit that need quite well. The only thing that has to be done to make this a reality is a rename (from \"pose marker\" to \"action marker\") and some UI cleanup. Fixing this bug is a good start.\n\nMarked as low-prio because the new purpose for pose markers isn't that official yet.\n\n**Note:** Be sure to test the `marker.select_leftright` operator as well (f1ae6952a8) after addressing this issue.\n", "X RAY mode cannot be toggled while in pose mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R4 Graphics ATI Technologies Inc. 4.5.13547 Core Profile Context 25.20.15018.12\n\nBroken: version: 2.93.5\n\n while modifying animations i tried to turn on xray mode to see inside a mesh while moving bones around only to find it was not functioning\n\nstep 1: create mesh\nstep 2: go to pose mode\nstep 3: toggle xray and see it do nothing\n" ]

[ "Bones Selection\n**\nI can not select bones individually,\nonly when I click on the parent bone or in collections**\n\n[Blender 2019-07-16 02-00-02.mp4](Blender_2019-07-16_02-00-02.mp4)" ]

[ "Regression: Particle mirror broken for particular mirrored mesh.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.2. also version: 3.3.0 hash: `8d9d5da13706`\nWorked: 3.0.0, commit hash: `8b44b756d850db38ab4d83513682f2012d88a3f4` from branch 3.0.1 to be exact.\n\nCaused by 02ab4ad991\n\nParticle hair x-mirror results in hair going in all directions instead of being properly mirrored, see the following screenshot: \n\n1. Start from the attached blend file which has an emitter sourced from a base model and mirrored by applying a mirror modifier. I could not reproduce the issue from scratch with simpler geometry and I might have reconnected the hair at some point .\n2. Go into particle edit mode on the `Eyebrows_Particle` object.\n3. Enable x-mirror in the top-right `Options` menu.\n4. Observe that the particles change directions.\n\nHere is what it looks like when it's working in the same particle edit mode with x-mirror enabled. The exact commit that introduced the issue is: `77694b571f5bd297ea7228b30f591ebbd333e0ea`.\n\n\n\n[mirror_bug.blend](mirror_bug.blend)\n\n[repro.blend](repro.blend)\n- open file\n- `Particle` > `Mirror`\n- observe wrong mirroring", "Hair particle length vertex group effect is non linear\nOperating system: MacOS Big Sur 11.2.3\nGraphics card: AMD Radeon Pro 5500M 8 GB\n\nBroken: 3.0 alpha, 4b06420e6504, master, 2021-09-13\nWorked: Unknown\n\nHair particle length scales non linearly with its length vertex group. Put another way, hair length is usually not quite equal to vertex weight * max hair length, which I assume is unintended. This causes problems when exact hair length is needed.\n\nThe screenshot below demonstrates the issue. \n\nIn this example, planes are instanced along the X axis from 0 to 1, using Geometry Nodes. The X position of each face is assigned to the vertex group controlling hair length. A hair particle system is added and set to spawn 1 particle per face.\nAs seen in the screenshot, the actual height of the hair is slightly wavy and doesn't form a straight line.\n\nHere's a video showing the same issue, this time spawning particles on a single face with interpolated vertex weights:\n[Hair Length Vertex Group Non Linear Bug.mov](Hair_Length_Vertex_Group_Non_Linear_Bug.mov)\n\n1. Delete the default cube\n2. Add a plane\n3. Add a vertex group to the plane\n4. In edit mode, assign a weight of 0.1 to all vertices.\n4. Add a hair particle system\n5. Set the hair length to 1m\n6. Assign the vertex group to control hair length\n7. In side-on orthographic view, observe that the hair length is slightly less than 0.1m.\n\n[Hair Length Vertex Group Bug.blend](Hair_Length_Vertex_Group_Bug.blend)", "Eevee contact shadows appearing from objects with shadows disabled\nOperating system: Windows 10\nGraphics card: RTX 3080\n\nversion: 3.5.1\n\nIssue:\nObjects in Eevee with the material setting \"Shadow Mode\" set to \"None\" still casts contact shadows.\n\nreplication:\nWith the default scene add a plane and scale it up so a visible shadow is being casted on it from the default cube, go into material settings of the default cube and set shadow mode to none. Then go to the default point light and enable contact shadows on it. (or view the blend file)\n\n", "Metaballs particles with drag force disapearing\nOperating system: Linux-5.3.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.33.01\n\nBroken: version: 2.83.2\nWorked: Never (2.8+)\n\nHi Guys,\n\nas you could see in the atachment file, the metaballs instances particles disapears on certains frames ...\nThere is no problem when Drag Force is not applied\n\nThanks in advance for your help !\nYour Software is amazing !! We love it !\n\n[MetaballsParticlesBug.blend](MetaballsParticlesBug.blend)\n\n- Open file\n- Play animation", "Particle Edit mode for non hair particles - 2 Crashes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n\nParticle Edit: 2 Crashes\n\nParticle Edit: 2 Crashes\n\n- Open the blender file and click on the buttons \"Particle select and display point\"\n- Crash 1 (Screenshot)\n\n- Open the blender file and click on the tool \"Weight\" and click into the particles\n- Crash 2 (Screenshot)\n\n- Also had a crash with \"Puff\" \n- file not included\n\n- There are some tools that do nothing while others work\n- User gets no feedback / error message but give no feedback\n\n\n\n[2019-05-19-particle-edit-crash.blend](2019-05-19-particle-edit-crash.blend)\n\n", "Killed particle's position is reset to the initial position when rendered\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\nI am encountering a strange particle behavior.\nWhen a particle collides with a plane where collision is enabled and \"kill particles\" is checked, the particle position seems to be reset to its initial position. This can not be observed in the viewport. This unexpected position reset is observed only when rendering the images.\nAs shown in this video:\n[0001-0050.mp4](0001-0050.mp4)\n\n[debug.blend](debug.blend)\nBake particle simulation and render images. You will get the same video as shown above.\n", "Particle systems render wrong on frame 0\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.5 Release Candidate\n\nA particle system renders moving particles in the wrong place on frame 0, if particles are spawned (=Frame Start) before frame 0.\n\n1. Create a particle system\n2. Set Frame Start to something smaller than 0 (with bigger negative numbers the effect is more obvious, so f.e. Frame Start = -20) (the effect is even more obvious if \"End\" is set to 0 or close to 0)\n3. Set particle object to render (Render -> Render As -> Object; Select Instance Object)\n4. Setting timeline start to 0 and rendering the frames, the wrong particle placement in frame 0 is clearly observable in relation to the next few frames. \n\nMoving the whole project/particle system timing to later frames manually, fixes this location jump. This shows, the problem is only the frame being 0.\n\n[particle_system_bug.blend](particle_system_bug.blend)\n", "Cannot keyframe particle count property\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Quadro 2000M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 377.83\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\n clicking keyframe button next to particle count responds with *Failed to resolve path to property, try manually specifying this using a Keying Set instead*\nsee screenshot attached\n\nClick on animate property next to particle count\n", "Particle system texture added via API not working ['blend_type' when created using the interface is MULTIPLY, whereas when created through API, its value is MIX]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83 (sub 17)\n\nHi,\n\nI have been trying to write a script that automatically adds a clouds texture to control the density of hair particles/instances. I have been able to successfully add a texture to the active particle system of the selected object with the Density checkbox under Influence activated -- all done through API. However, there is no effect on the density of the particles.\n\nI am clueless of why this is happening. Is this a bug?\n\nI have attached a blend file (with an internal script) for reproducing the bug.\n\n - Open the attached blend file.\n - Allow execution of scripts (in case not allowed)\n - Select the plane (already has a particle system) and search for 'Particle Density Texture' and execute the script.\n\nThe texture will get added successfully to the particle system's texture slots with the density option on, but will have no effect on the particle distribution whatsoever. The script also has an UNDO panel. You could try changing values there or in the properties panel as well, but will have no effect.\n\nAm I doing something wrong? Or is this a bug or a known issue or any API limitation?\n[particle_density_texture.blend](particle_density_texture.blend)\n\n", "Keyed Particle Physics Incorrectly Rendered Under Eevee and Cycles, but Correctly Rendered in Viewport Render\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nCreate two objects. Attach a normal particle system to the first one. Attach a keyed particle system to the second one, with the two relations \"first object\" then \"second object\". Therefore, particles should move from the first object to the second object. If the starting velocities are non-trivial and the keyed particles are generated over three or more frames (e.g., start time 10, end time at least 12) then the particles of the keyed system are correctly rendered in the viewport (rendered mode) but appear in different positions when actually rendering (pressing F12).\n\nI first discovered this with a more complicated example, and the same behaviour occurred under both 2.90 and 2.83 (normal releases). Googling did not turn up anything relevant. (Motion blur is off.)\n\nI have been able to recreate it with a simple .blend file attached. Included are two screenshots at frame 20, one of the viewport, one of the rendered image. While the difference is just one particle here (a red particle is over the left square in the viewport but off the square in the rendered image), vastly different behaviour can be achieved by increasing the difference between start and end times. \n\nIn the more complicated example, not included here, a particle would appear at the top of the screen and move towards its final destination. When rendered though, it would appear in the correct place on that frame but then immediately jump to a very different location on the next frame.\n\nNote: This bug might depend on the first object's particles having a short lifetime - the original motivation is having one object explode then morph into another object. The rendered animation looked very different (and incorrect) from the viewport animation.\n\n[system-info.txt](system-info.txt)\n\n\n\n\n\n\n[Debug 2.blend](Debug_2.blend)\n1) Open it.\n2) Set viewport to Rendered mode.\n3) Move playhead to frame 20.\n4) Observe the locations of the 4 red particles near Plane.001. (They form a loose \"T\" shape and none are touching Plane.001.)\n5) Press F12.\n6) Observe the locations of the 4 red particles near Plane.001 are very different. (Two are touching Plane.001 and the other two are in line ready to arrive at Plane.001.)\n\n", "Particle Systems keep reacting to a Force Field even though the Force Field's already been deleted\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R5 M335 ATI Technologies Inc. 4.5.13497 Core Profile Context 23.20.768.12\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nParticle Systems keep reacting to a Force Field even though the Force Field's already been deleted. It's not that big a deal, but it may confuse or frustrate new users.\n\n - Select the default Cube. In the Particles tab, add a new particle system. Hit Play in the timeline to start the particle simulation.\n - While the simulation is still playing, add a Force Field, such as Wind. Rotate it 90 degrees around the y-axis. In the Physics tab, increase the Strength, perhaps to 20. The particles are now being blown away.\n # Delete the Force Field when the playhead is at about frame 40 or so. The particles keep being blown away from the start to that frame 40 or so, even though there's no longer a Force Field, even if you've tried replaying the simulation in the Timeline. The only way to return them back to before is to alter some settings, for example hiding the Cube in the Outliner then showing it again, or change the particle count, or baking the simulation, which are all awkward and confusing.\n[particleforcefield.blend](particleforcefield.blend)", "Hair Curves: Posed hair curves get stuck onto a wrong pose upon entering and exiting Sculpt, Vertex Paint or Weight Paint mode on the surface object\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2060 Super\n\nBroken: 3.6.1\nWorked: n/a\n\nOn posed hair when using the 'deform curves on surface' node, if you enter and exit Sculpt, Vertex Paint or Weight Paint mode on the surface object, the posed hair will get stuck on a wrong pose, see attached images for comparison. You don't have to edit anything for the bug to occur. \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Open the file and select the \"Surface\" object\n2. Enter and exit Sculpt, Vertex Paint or Weight Paint mode\n3. The hair curves object should now have deformed onto a wrong pose and can't be fixed until you reload the file\n\nThis bug still appears in the final render and can only be fixed by reloading the save file.\n\n", "Connected Only option of Proportional Editing in Particle Edit mode doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nConnected Only option of Proportional Editing in Particle Edit mode doesn't work\nWhen you try to edit a single hair curve, Proportional Editing affects the nearest curves as well, whether the Connected Only option is enabled or not.\n\n", "Particle Edit mode for non hair particles - Not working\nOperating system: Linux-5.6.0-050600-lowlatency-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 3)\nWorked: can not find one\n\n\nCan not edit a baked particle simulation's particle paths in Particle Edit mode\n\n\n- Delete all object from the original scene\n- Create a plane\n- Add a particle system. For the sake of testing with 20 particles,\n- Bake the simulation (not in disk)\n- Switch to Particle Edit mode\n- Select Point select mode\n\n- > There is no particle path in the view-port to be edited.[path not showing in particule edit .blend](path_not_showing_in_particule_edit_.blend)\n", "Hidden Particle paths draw solid [2.79 draws them half transparent]\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.81 (sub 15)\nWorked: (optional)\n\nComparison of particle hiding Blender 2.81 beta and 2.79. I wrote earlier that the particles are not hiding, and this is so fixed?\n\n" ]

[ "Hair Dynamics: collision doesn't work (exploding)\nOperating system:Ubuntu Studio 19.04\n\n\nBroken: current master @ 84c537e685\nWorked: 2.82 alpha @ 6bf0e9dbb1, 2.81a release\n\nOpen a 2.79 file with working hair dynamic in current master and the hair goes in all directions.\n\n\n- Open [slightly-simplified-279.blend](slightly-simplified-279.blend)\n- Play the animation.\n\nThe first 30 frames have been cached by Blender 2.79, so they show the correct dynamics. After that new dynamics are computed and are exploding.\n\nFrame 20 (cached 2.79 dynamics): \n\nFrame 47 (2.82 alpha dynamics): \n\n\nOriginal example: " ]

[ "Eevee volume render test memory leak in Mantaflow\nOperating system: Linux-4.15.0-76-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 4), `5b22713`\n\nRunning this command will hang, some problem with the Python GIL.\n```\nblender -b ../lib/tests/render/volume/smoke_color.blend -E BLENDER_EEVEE -P tests/python/eevee_render_tests.py -f 1\n```\n\nBacktrace:\n[P1260: (An Untitled Masterwork)](P1260.txt)\n```\nBlender 2.83 (sub 4)\nRead prefs: /home/brecht/.config/blender/2.83/config/userpref.blend\nfound bundled python: /home/brecht/dev/worktree_build/bin/2.83/python\nRead blend: /home/brecht/dev/lib/tests/render/volume/smoke_color.blend\nTraceback (most recent call last):\n File \"<string>\", line 55, in <module>\nNameError: name 'Vec3Grid' is not defined\nTraceback (most recent call last):\n File \"<string>\", line 3, in <module>\nNameError: name 'PcMGDynamic' is not defined\nMANTA::updateGridFromFile(): cannot read into uninitialized grid, grid is null\nMANTA::updateGridFromFile(): cannot read into uninitialized grid, grid is null\n^C\nThread 1 \"blender\" received signal SIGINT, Interrupt.\n0x00007ffff7231f85 in futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x7fffffffc340, expected=0, futex_word=0xbcd7678 <_PyRuntime+1336>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205\n205\t../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.\n(gdb) bt\n#0 0x00007ffff7231f85 in futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x7fffffffc340, expected=0, futex_word=0xbcd7678 <_PyRuntime+1336>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205\n#1 __pthread_cond_wait_common (abstime=0x7fffffffc340, mutex=0xbcd7680 <_PyRuntime+1344>, cond=0xbcd7650 <_PyRuntime+1296>) at pthread_cond_wait.c:539\n#2 __pthread_cond_timedwait (cond=0xbcd7650 <_PyRuntime+1296>, mutex=0xbcd7680 <_PyRuntime+1344>, abstime=0x7fffffffc340) at pthread_cond_wait.c:667\n#3 0x000000000560c7c9 in PyCOND_TIMEDWAIT (cond=<optimized out>, mut=<optimized out>, us=<optimized out>) at Python/condvar.h:90\n#4 take_gil (tstate=tstate@entry=0x7fffd2a18b80) at Python/ceval_gil.h:208\n#5 0x000000000560cd2f in PyEval_RestoreThread (tstate=tstate@entry=0x7fffd2a18b80) at Python/ceval.c:271\n#6 0x0000000005639fed in PyGILState_Ensure () at Python/pystate.c:1071\n#7 0x0000000005158e06 in MANTA::runPythonString (this=0xbcd7678 <_PyRuntime+1336>, commands=...) at /home/brecht/dev/worktree/intern/mantaflow/intern/MANTA_main.cpp:528\n#8 0x0000000005159140 in MANTA::~MANTA (this=0x7fff96443400) at /home/brecht/dev/worktree/intern/mantaflow/intern/MANTA_main.cpp:523\n#9 0x00000000051592b9 in MANTA::~MANTA (this=0x7fff96443400) at /home/brecht/dev/worktree/intern/mantaflow/intern/MANTA_main.cpp:508\n#10 0x000000000150bbaf in BKE_fluid_modifier_freeDomain (mmd=0x7fffbb59d3a8) at /home/brecht/dev/worktree/source/blender/blenkernel/intern/fluid.c:4192\n#11 0x000000000150ba85 in BKE_fluid_modifier_free (mmd=0x7fffbb59d3a8) at /home/brecht/dev/worktree/source/blender/blenkernel/intern/fluid.c:4315\n#12 0x00000000013f7a47 in modifier_free_ex (md=0x7fffbb59d3a8, flag=<optimized out>) at /home/brecht/dev/worktree/source/blender/blenkernel/intern/modifier.c:169\n#13 0x000000000140f6aa in BKE_object_free_modifiers (ob=0x7fffd299d208, flag=2) at /home/brecht/dev/worktree/source/blender/blenkernel/intern/object.c:190\n#14 0x0000000001410223 in BKE_object_free (ob=0x7fffd299d208) at /home/brecht/dev/worktree/source/blender/blenkernel/intern/object.c:516\n#15 0x0000000001d6c70e in DEG::deg_free_copy_on_write_datablock (id_cow=0x7fffd299d208) at /home/brecht/dev/worktree/source/blender/depsgraph/intern/eval/deg_eval_copy_on_write.cc:1066\n#16 0x0000000001d736f9 in DEG::IDNode::destroy (this=0x7fffd275fd08) at /home/brecht/dev/worktree/source/blender/depsgraph/intern/node/deg_node_id.cc:165\n#17 0x0000000001d4f1e3 in DEG::Depsgraph::clear_id_nodes_conditional(std::function<bool (ID_Type)> const&) (this=<optimized out>, filter=...) at /home/brecht/dev/worktree/source/blender/depsgraph/intern/depsgraph.cc:156\n#18 DEG::Depsgraph::clear_id_nodes (this=0x7fff88df7488) at /home/brecht/dev/worktree/source/blender/depsgraph/intern/depsgraph.cc:167\n#19 0x0000000001d4efec in DEG::Depsgraph::~Depsgraph (this=0x7fff88df7488) at /home/brecht/dev/worktree/source/blender/depsgraph/intern/depsgraph.cc:93\n#20 0x0000000001d4f689 in OBJECT_GUARDED_DESTRUCTOR<DEG::Depsgraph> (what=0x7fff88df7488) at /home/brecht/dev/worktree/intern/guardedalloc/MEM_guardedalloc.h:264\n#21 DEG_graph_free (graph=0x7fff88df7488) at /home/brecht/dev/worktree/source/blender/depsgraph/intern/depsgraph.cc:297\n#22 0x00000000016dd4fc in EEVEE_lightbake_job_data_free (custom_data=0x7fffd29ef288) at /home/brecht/dev/worktree/source/blender/draw/engines/eevee/eevee_lightcache.c:638\n#23 0x00000000028449c8 in light_cache_bake_exec (C=0x7ffff2efa288, op=0x7fffd294c608) at /home/brecht/dev/worktree/source/blender/editors/render/render_shading.c:928\n#24 0x000000000156be79 in wm_operator_invoke (C=0x7ffff2efa288, ot=0x7fffd284a468, event=0x0, properties=<optimized out>, reports=<optimized out>, poll_only=<optimized out>, use_last_properties=<optimized out>)\n at /home/brecht/dev/worktree/source/blender/windowmanager/intern/wm_event_system.c:1279\n#25 0x0000000001566ead in wm_operator_call_internal (C=0x7ffff2efa288, ot=0x7fffd284a468, properties=0x7fffffffc840, reports=0x7fffd2a15a18, context=6, poll_only=false, event=0x0) at /home/brecht/dev/worktree/source/blender/windowmanager/intern/wm_event_system.c:1514\n#26 0x00000000015674ed in WM_operator_call_py (C=0x7ffff2efa288, ot=0x7fffd284a468, context=6, properties=0x7fffffffc840, reports=0x7fffd2a15a18, is_undo=false) at /home/brecht/dev/worktree/source/blender/windowmanager/intern/wm_event_system.c:1614\n#27 0x000000000191629f in pyop_call (UNUSED_self=<optimized out>, args=<optimized out>) at /home/brecht/dev/worktree/source/blender/python/intern/bpy_operator.c:268\n#28 0x000000000555971b in _PyMethodDef_RawFastCallKeywords (method=0x98c5800 <bpy_ops_methods+32>, self=<optimized out>, args=<optimized out>, nargs=3, kwnames=0x0) at Objects/call.c:698\n#29 0x0000000005559945 in _PyCFunction_FastCallKeywords (func=0x7fff921393c0, args=<optimized out>, nargs=<optimized out>, kwnames=<optimized out>) at Objects/call.c:734\n#30 0x000000000137a132 in call_function (kwnames=0x0, oparg=3, pp_stack=<synthetic pointer>) at Python/ceval.c:4568\n#31 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:3124\n#32 0x000000000560dc5e in _PyEval_EvalCodeWithName (_co=_co@entry=0x7fff92165390, globals=globals@entry=0x7fff9214e780, locals=locals@entry=0x0, args=args@entry=0x7fffffffcbd0, argcount=1, kwnames=kwnames@entry=0x0, kwargs=0x0, kwcount=0, kwstep=2, defs=0x0, defcount=0, \n kwdefs=0x0, closure=0x0, name=0x7ffff7f7d1b0, qualname=0x7fff920e6030) at Python/ceval.c:3930\n#33 0x000000000555927f in _PyFunction_FastCallDict (func=0x7fff92165e60, args=0x7fffffffcbd0, nargs=<optimized out>, kwargs=0x0) at Objects/call.c:376\n#34 0x000000000555a42c in _PyObject_Call_Prepend (callable=callable@entry=0x7fff92165e60, obj=obj@entry=0x7fff8353fa90, args=args@entry=0x7ffff7f7d050, kwargs=kwargs@entry=0x0) at Objects/call.c:908\n#35 0x00000000055bb4d9 in slot_tp_call (self=0x7fff8353fa90, args=0x7ffff7f7d050, kwds=0x0) at Objects/typeobject.c:6402\n#36 0x0000000005559a23 in _PyObject_FastCallKeywords (callable=0x7fff8353fa90, stack=<optimized out>, nargs=<optimized out>, kwnames=0x0) at Objects/call.c:199\n#37 0x0000000001379aa8 in call_function (kwnames=0x0, oparg=<optimized out>, pp_stack=<synthetic pointer>) at Python/ceval.c:4619\n#38 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:3093\n#39 0x000000000137120f in function_code_fastcall (co=<optimized out>, args=<optimized out>, nargs=0, globals=<optimized out>) at Objects/call.c:283\n#40 0x00000000055594e6 in _PyFunction_FastCallKeywords (func=<optimized out>, stack=<optimized out>, nargs=<optimized out>, kwnames=<optimized out>) at Objects/call.c:415\n#41 0x0000000001378cef in call_function (kwnames=0x0, oparg=<optimized out>, pp_stack=<synthetic pointer>) at Python/ceval.c:4616\n#42 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:3124\n#43 0x000000000560dc5e in _PyEval_EvalCodeWithName (_co=_co@entry=0x7fff837ab6f0, globals=globals@entry=0x7fff901c88c0, locals=locals@entry=0x7fff901c88c0, args=args@entry=0x0, argcount=argcount@entry=0, kwnames=kwnames@entry=0x0, kwargs=0x0, kwcount=0, kwstep=2, defs=0x0, \n defcount=0, kwdefs=0x0, closure=0x0, name=0x0, qualname=0x0) at Python/ceval.c:3930\n#44 0x000000000560dd3e in PyEval_EvalCodeEx (_co=_co@entry=0x7fff837ab6f0, globals=globals@entry=0x7fff901c88c0, locals=locals@entry=0x7fff901c88c0, args=args@entry=0x0, argcount=argcount@entry=0, kws=kws@entry=0x0, kwcount=0, defs=0x0, defcount=0, kwdefs=0x0, closure=0x0)\n at Python/ceval.c:3959\n#45 0x000000000560dd6b in PyEval_EvalCode (co=co@entry=0x7fff837ab6f0, globals=globals@entry=0x7fff901c88c0, locals=locals@entry=0x7fff901c88c0) at Python/ceval.c:524\n#46 0x000000000564290a in run_mod (arena=0x7fff902cb2b0, flags=0x0, locals=0x7fff901c88c0, globals=0x7fff901c88c0, filename=0x7fff83792c00, mod=0x7fffbb57d210) at Python/pythonrun.c:1035\n#47 PyRun_FileExFlags (fp=<optimized out>, filename_str=<optimized out>, start=<optimized out>, globals=0x7fff901c88c0, locals=0x7fff901c88c0, closeit=0, flags=0x0) at Python/pythonrun.c:988\n#48 0x0000000001902146 in python_script_exec (C=0x7ffff2efa288, fn=0x7fffffffd4d0 \"/home/brecht/dev/worktree/tests/python/eevee_render_tests.py\", text=0x0, reports=0x0, do_jump=<optimized out>) at /home/brecht/dev/worktree/source/blender/python/intern/bpy_interface.c:532\n#49 0x000000000137e0df in arg_handle_python_file_run (argc=<optimized out>, argv=0x7fffffffdab0, data=0x7ffff2efa288) at /home/brecht/dev/worktree/source/creator/creator_args.c:1772\n#50 0x0000000006875131 in BLI_argsParse (ba=0x7ffff305f8c8, pass=4, default_cb=0x137e9d0 <arg_handle_load_file>, default_data=0x7ffff2efa288) at /home/brecht/dev/worktree/source/blender/blenlib/intern/BLI_args.c:302\n#51 0x000000000137b915 in main (argc=9, argv=0x7fffffffda88) at /home/brecht/dev/worktree/source/creator/creator.c:483\n\n```\n\n\n", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Cycles: Changing certain settings with `Persistent Data` enabled can lead to extremely long initialization times on re-render\nOperating system: Linux-5.15.0-1-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken version: 3.1.0 Alpha\nBroken version: 2.93.6\nWorked: Unsure\n\nWhen changing certain settings on some objects while having `Persistent Data` on in Cycles, can lead to extremely long initialization times on re-renders. For example I may have a particle count set to `10,000,000` and I render the scene for the first time. It takes roughly 2 minutes. Re-rendering the scene only takes 10 seconds because of the `Persistent Data` option. However, if I then **decrease** the particle count to `1,000,000`, the render takes a really long time to start (I waited 15 minutes before giving up)\n\n1. Change the render engine to Cycles.\n2. Change render settings such that the render is quick (lower sample count, turn off denoising, reduce the resolution).\n3. Enable `Persistent Data` in the `Render Properties -> Performance` section of the `Properties editor`\n4. Create a hair particle system with lots of objects. I did this by creating a plane, giving it a hair particle system set to count `10,000,000` and set it to \"render as\" a Suzanne object\n5. Render the scene. Take note of roughly how long it takes for the render to initialize. Roughly 2 minutes for me.\n6. Render the scene again. (I'm not sure why but this steps seems to be necessary)\n7. Reduce the particle count on the plane. I reduced it to `1,000,000`.\n8. Render the scene again. Notice how the render takes a really long time to start. (I gave up after waiting 15 minutes.)\n\nHere is a file that does step 1-4 for you:\n[Persistent Data Long Intialization Time.blend](Persistent_Data_Long_Intialization_Time.blend)\n\n**NOTE:** This is not an out of memory issue, at least from what I can tell. Blender gets nowhere close to using the entirety of my RAM (64GB) or VRAM (24GB) during tests using CPU or GPU for testing.", "Wrong editor type saved in workspace\nOperating system: Win11\nGraphics card: AMD Radeon (TM) Graphics (Included Graphics)\n\nBroken: 3.5.1\nWorked: N/A.\n\nMy properties editor is glitched and keeps resetting to nonlinear animation editor.\n(When saving file and reopening)\n\nIdk how to repreduce it, but here are steps for my blender file:\n1. Switch editor type to properties editor.\n2. Save file.\n3. Close blender .\n4. Open the saved file.\n5. Properties editor switched to nonlinear animation editor.\n6. (When repeating 1-4 with all objects deleted, then its working normally without the switch at restart).\n7. Viedeo: EDgFd6MIzjM.\n\n", "Extremely frequent crashing when using the compositor. Especially when using the glare node.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I believe it was far more stable before the realtime compositor implementation. (Blender 3.3-ish)\n\nBlender crashes extremely frequently when using the compositor on my system, especially when the glare node is being used at all. Does not seem related to vram or system specs, and looking through logs has not come up with any errors - it just closes.\n\nAdjust compositor glare node values with the viewer enabled. It seems to crash within a minute of doing so, usually sooner.\n\n", "Reliable GPU hang on common Intel cards (Linux)\nOperating system: Linux Fedora 32\nGraphics card: UHD Graphics 620 (rev 07) Intel\n\nBroken: 2.80.x, 2.90.0-x\n\n\n\nBlender crashes the computer, freezing, dmesg command shows a GPU Hang error.\n\n\nOnly with Intel GPU (Intel Corporation UHD Graphics 620 (rev 07) here)\n\nOpen the given blend file [F8892221](gpuhangtest.blend) (Thanks @HDMaster84 ) and activate lookdev or render view - the graphic server hangs.\n\nI followed the dmesg output that says to create an issue on freedesktop gitlab: 2422 (you can see my dmesg and gpu error) - anyway, thos problem only happens with Blender.\n\nThe problem started from 2.80 if I'm not wrong, not with others earlier versions.\n\n", "Segfault when encountering exception with props dialog open.\nOperating system: Linux\nGraphics card: Intel\n\n\nBroken: 2.92, 2.93.0\n\n\nWhen an `Exception` is raised in the `.invoke()` method of an operator while a props dialog is open, Blender does a segfault:\n\n`Unhandled exception thrown: read access violation. op->type was nullptr.`\n```\n>\tblender.exe!ui_layout_operator_properties_only_booleans(const bContext * C, wmWindowManager * wm, wmOperator * op, int layout_flags) Line 2517\tC\n\n \tblender.exe!uiTemplateOperatorPropertyButs(const bContext * C, uiLayout * layout, wmOperator * op, eButLabelAlign label_align, short flag) Line 2560\tC\n \tblender.exe!wm_block_dialog_create(bContext * C, ARegion * region, void * userData) Line 1391\tC\n \tblender.exe!ui_popup_block_refresh(bContext * C, uiPopupBlockHandle * handle, ARegion * butregion, uiBut * but) Line 586\tC\n \tblender.exe!ui_block_region_refresh(const bContext * C, ARegion * region) Line 399\tC\n \tblender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 754\tC\n \tblender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 867\tC\n \tblender.exe!wm_draw_update(bContext * C) Line 1066\tC\n \tblender.exe!WM_main(bContext * C) Line 654\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 523\tC\n```\n\n\n[#88929.blend](T88929.blend)\n\n- Open file\n- Run script", "3d viewport High memory usage--MacOS intel--\nOperating system: macOS-13.2-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 3.5.0 Alpha\n\nhigh memory usage of the factory settings startup file.\n\n- Open latest macos blender build 3.5 for MacOS 13.2 Intel\n- Perform selection operation (box select, click select, etc.)\n[Screen Recording 2023-02-07 at 2.27.06 amsmall.mp4](Screen_Recording_2023-02-07_at_2.27.06_amsmall.mp4)\n\n\n", "UI BUG: Icons in the property editor \"flicker\" when you hover them or click on them\nOperating system: Windows 10, 64 bits\nGraphics card: Geforce 1080 8gb, Geforce 1070 8gb\n\nBroken: blender-2.90.0-874af5301cdf-windows64\nWorked: 2.83.0 LTS\n\n\nIcons in the property editor annoyingly flicker, they change border thickness 1-2 pixels upon hovering over or clicking on them.\n\nThin:\n\n\nThen they get thicker:\n\n\nIt's very visible if you use Icon border settings in your theme and many monochrome themes dop use that setting, because not everyone wants to see distracting rainbow colors in their UI.\n\n\nGo to Blender Preference, Themes.\nOpen Icon colors tab and set icon border to 1.\nEssentially use any bright theme as it is very visible when your theme is bright and icons have borders.\n\n\nHover over icons in the property editor, see the flickering.\n\nHere's the video of the bug:\n\n[2020-06-22 01-18-44.mp4](2020-06-22_01-18-44.mp4)\n\n\n", "Material Library VX causes permanent freeze with EEVEE rendering\nOperating system: Windows 10, 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.81\n\nUsing materials from Material Library VX addon, particularly Floor Wood and Rusty Metal, causes EEVEE to freeze all of Blender. They work fine with Cycles, so it's not the addon. Not even the partial \"developer view\" render can take the materials.\n\nOpen default blend file.\nEnable Material Library VX addon.\nApply \"Floor Wood\" to the cube.\nSwitch to \"render view\" without changing the engine off of EEVEE. Blender 2.81 will freeze.\n\nNote: If you try to view the material preview and EEVEE is the render engine even *that* will freeze Blender 2.81.", "Blender is crashing instantly to the desktop randomly (solid viewport)\n\nOS: Windows 10 Pro 64bit (Version 21H2, OS Build 19044.2006)\nGPU: Nvidia GeForce RTX 2070 (Driver: Version 517.48 (released 27th September 2022))\nCPU: AMD Ryzen 7 2700\nRAM: 64GB\n\n\nBroken: version: 3.3 (and versions for the last couple of years)\nWorked: none since 2020 approx.\n\n\nBlender crashes seemingly randomly when performing modelling actions such as moving vertices, clicking sliders or buttons, switching to wireframe view, or moving the viewport camera in any way. There may be other actions that cause crashes. Crashes cause Blender to instantly close to desktop, leaving no crash dumps. Crashes occurring over multiple versions since 2020, multiple reinstallations of the OS, and clean reinstallations of graphics driver.\n\nUsing blender_debug_gpu.cmd, I was able to retrieve a log from a crash that has some differences to a normal log:\n\n\"*INFO (gpu.debug): Notification : Buffer usage warning: Analysis of buffer object 82 (bound to GL_SHADER_STORAGE_BUFFER (1)) usage indicates that the GPU is the primary producer and consumer of data for this buffer object. The usage hint supplied with this buffer object, GL_STATIC_DRAW, is inconsistent with this usage pattern. Try using GL_STREAM_COPY_ARB, GL_STATIC_COPY_ARB, or GL_DYNAMIC_COPY_ARB instead.*\"\n\nCurrently, have no way to reproduce the crashes at will, they just seem to happen during my normal work. Load tests using OCCT do not cause crashes.\n\n**Debug log from crash**:\n[blender_debug_output2.txt](blender_debug_output2.txt)\n\n**Normal debug log**:\n[blender_debug_output_normal.txt](blender_debug_output_normal.txt)", "Incorrect VRAM quantity in the Status Bar ( GNU/Linux AMDGPU )\nHello, first bug report :)\nA minor bug about the VRAM displayed in the status bar in my GNU/Linux AMDGPU system.\n\nOperating system: Linux-5.4.0-7642-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.35.0, 5.4.0-7642-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 2.90.1\nBroken: 2.91.0 alpha\nWorked: No\n\nDisplayed VRAM quantity in the status bar is wrong: 16 GB instead of 8 GB.\n\nIn a similar system enable the Video Monitor option to show the GPU usage in the status bar.\nUploaded an image and system info file:\n\n[system-info.txt](system-info.txt)", "Action Editor Name/Title field causing crashes, which further causes total loss of all stashed action data.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\nWorked: Never\n\nThis is happening in a very specific file (I have similar files with similar models, which this does NOT happen for) - I have 2 monitors: one has a window for the layout & timeline, and the other monitor has a single, docked window for the Action editor, the graph editor, and NLA editor. So in the ACTION editor, I try to set a name in the in the title field for a new action (to be \"stashed\" for later use) - and the moment I hit enter or click out of the field, Blender crashes immediately. I don't even have to change the default name for this to occur. This happened a dozen or so times, and somewhere in that series of crashes, all the actions I had made and \"stashed\" were deleted from the file entirely, and as far as I can tell, are completely lost. Upon closing the docked windows, and again separating windows from within the blender window on my MAIN monitor, opening up the action editor again and going through the same process, this problem does NOT persist. So the crashing can be addressed with work-arounds, but the total loss of the existing action data is a big concern, as I cannot predict when this issue will happen again. See videos linked in the google drive file below. (Honestly not sure if the google drive file will replicate this issue, but I redownloaded it from google drive, and it opened the graph/nla/action editor in a separate docked window, and the bug persists - so it SHOULD be repeatable on your end too). In any event, the dumping of stashed action data I believe is the biggest issue to address here, since the crash problem can be worked around, although the crashing in and of itself is obviously a concern, since it seems to have been the cause of the loss of action data.\n\nIn the below Gdrive folder there are: 2 videos, 2 images, and the original .blend file that this problem persists within.\n\n1Gi62lbXBRlkQxFB2m7E5t5pjkqeQQrPY?usp=share_link\n\n[#104293.blend](T104293.blend)\n- Open file\n- In window with action editor, rename the action\n\nBlender should crash.\nIt doesn't crash if asset browser window is activated or if file is saved to different location.\n", "Suspected asset library crash by `json_sax_dom_parser`\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nI dont completely know why but blender crashes very often for me.\nIts doing something no idea what it is doing.\nSorry for being vague, but it seems to mostly happen when i have the viewport set to cycles render and i am trying to modify materials, in the shader editor.\n\n", "Menus open on upward mouse movement\nOperating system: Linux (Debian bullseye)\nGraphics card: Nvidia GTX 1070\n\nBroken: current master 2.90.0 (fc672ce8e24e)\nWorked: Never\n\nWhen there are a lot of modifiers in the stack which make the evaluation slow there is a weird effect with the dropdown menu. It somehow glides when dragging to the next modifier.\n\n\n\nTo the default cube, add array modifiers until your memory usage is at roughly 300MiB. Then drag over the drop down arrows like shown in the gif." ]

[ "Windows crashes when draging properities panel to open it\nWindows 64bit, 4096 MB\nGeForce GTX 760/PCIe/SSE2, 4.5.0 NVIDIA 352.86\n\nBroken: 2.75 (sub 0), branch b'master', commit date b'2015-06-19' b'14:59', hash b'c85a58a', b''\n\nWindows crashes when draging properities panel to open it\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n- open .blend file\n- click on the properities panel edge and drag it to open it (see attached image)\n- the Windows OS crashes and I have to reboot \n- I can reproduce the crash on my system\n\n[windows-7-64bit-crash.blend](windows-7-64bit-crash.blend)\n\n" ]

[ "Touchscreen 'Continuous Grab'\nOperating system: Linux-4.15.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Haswell Mobile Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.0.2\n(bug also tested on Windows 10)\n\n\nBroken: version: 2.80 (sub 74)\nWorked:\n\n\n* Activate a gizmo using the **touchscreen** on a computer. (The 3D navigation gizmo for example)\n* Drag your finger outside the original editor\n* The gizmo is manipulated incorrectly\nThis bug disappears if \"*continuous grab*\" is disabled in the User Preferences.\nI think it's a matter of auto-disabling *continuous grab* while receiving touch input, like how pen tablets are handled.", "Issues with HDRIs and render result pixel values that exceed half float limits\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n(Also tested in latest 3.3 Alpha)\n\nSome lookdev HDRI's give the scene a colored tint, that also does not disappear after lowering the strength\n\nI imported this HDRI to preview lighting in my Eevee scene: lenong_2\n\nAt first, this looks okay in blender:\n\n\nBut after lowering the strength, you will notice that there is a yellow light that should not be there, as well as a white spot from where the sun used to be, even if strength=0\n\n\nI found a workaround by adjusting the exposure of the HDRi in advance by -1 in affinity photo. This makes the image only a tiny bit darker, but the end result is as you would expect it.\nNo yellow light, no sun.\n\n\nI tried this with another HDRi from HDRIhaven (from another creator, this one specifically ehingen_hillside) and the issue also existed there. \n\nHere is the blend file for testing:\n[HDRI_Test.blend](HDRI_Test.blend)\nAnd the HDRI fixed by me\n[lenong_2_1k_fixed.hdr](lenong_2_1k_fixed.hdr)", "Cycles XML, light node does not react to transform\nCycles XML, light node does not react to transform (it was ok before migration to graph/node* node parsing). Let me know if this is a bug or it is by design.\n\nSee attached sample XML.\n\n```\n<cycles>\n<transform translate=\"0 0 -4\"><camera type=\"perspective\" /></transform>\n<integrator max_volume_bounce=\"0\" method=\"branched_path\" sample_all_lights_direct=\"true\" sample_all_lights_indirect=\"true\"/>\n<background heterogeneous_volume=\"false\" volume_sampling_method=\"equiangular\" ><scatter_volume name=\"scatter\" color=\"0.8, 0.8, 0.8\" density=\"0.3\" /><connect from=\"scatter volume\" to=\"output volume\" /></background>\n<shader name=\"point_shader\"><emission name=\"emission\" color=\"0.8 0.1 0.1\" strength=\"100\" /><connect from=\"emission emission\" to=\"output surface\" /></shader>\n\n<state shader=\"point_shader\"><light type=\"point\" co=\"0 0 0\" size=\"0.01\" /></state>\n\n<!-- Light does not react to transform node -->\n<transform translate=\"0 0.5 0.0\">\n\t<state shader=\"point_shader\"><light type=\"point\" co=\"0 0 0\" size=\"0.01\" /></state>\n</transform>\n\n</cycles>\n```", "UV: Add 3D Gizmos for UV projections, Cube, Cylinder and Sphere projection\nThe \"Unwrap > Projection\" operators are powerful, but would be even better with artist control over exact placement in 3D space.\n\nPropose to add gizmos in the 3D viewport to allow precise artistic control over the cube, sphere and cylinder.\n\nConsider adding Planar Projection as well.\n\nThanks @BlenderBob for the suggestion!\n\n", "Tablet/Pen Usability Problems\nFor the most part any user who is using a Pen/Tablet can easily use Blender but there are still a few inconsistencies in the navigation and functions where in the worst case, you need to constantly switch to a mouse.\n\nFor one there is the inability to scroll through certain areas without using the mouse wheel.\nWhen opening a popup list for example when selecting a material, texture, brush, etc, you can only scroll through the window by using the mouse wheel or by typing in the result that you are looking for. But in all other menus that are not popup related, there is the option to scroll by holding the middle mouse button and moving the cursor up/down. \nAdding this option to these popups or at least adding a scrollbar to the side would make it possible for pen users to scroll through these windows without switching to the mouse temporarily.\n\n\nSome tools have a radius that can be adjusted by either using the mouse wheel or using the Numpad +/- keys. \nThis is the case for example in the Circle Selection and Proportional Editing.\nFor pen users the Numpad +/- keys work but are slow and awkward to use because because you have to cross your arms (depending on your layout & right/left handed) and you have to hit the keys in very quick succession for a while or hold it which created a delay of when the scale changes. \nAdding an extra key like using the F key to change the radius in the Paint/Sculpt Modes could be a solution but can be equally awkward and even more confusing to use. Maybe mapping the increase/decrease radius to the +/- keys as well for the non-numpad users and make holding the key more responsive and fast in resizing is a good improvement at least.\n", "Cycles, inconsistent power units between mesh light and rectangle area light\nOperating system: Windows 10 x64\n\nBroken: version: 2.82 (sub 6), branch: master, commit date: 2019-12-17 23:52, hash: e0cd5b980fc5, type: Release\n\nAs seen in #53517 comment :\n\n> Lamps are in Watts, [...]. Mesh lights are in Watts/m^2 [...]\n\n\nRendering the following two emissive items should give the same lighting :\n\n* rectangle area light, 1m x 1m, power 1W\n* plane mesh, 1m x 1m, Emission shader, strength = 1.0\n\nThis is not the case, area light power must be multiplied by 4 to get the same result.\n\n\nWith the attached blend file, [test-emissive-vs-arealight-1m².blend](test-emissive-vs-arealight-1m².blend)\n\n* enable 'Rendered' viewport shading\n* the 'Emissive plane' brings more light to the 'Ground' that the 'Area light'\n* change the 'Area light' power to 4W\n", "Adjust last operation: can't reset properties to default value\nBroken: 2.8x\n\nIn the Adjust Last Operation panel, the context menu for any property has the Reset to Default Value options disabled, although they are enabled in the operator panel.\n\n\n1. Load the default scene\n2. Enter edit mode on the cube\n3. Bevel an edge\n4. Expand the operator panel in the bottom left\n5. Right click any property, note that Reset to Default Value option is enabled and works\n6. Go Edit -> Adjust Last Operation\n7. Right click the same property in that panel, note that Reset to Default Value option is disabled", "Research: refactor dotted/dashed lines to support line width.\n Almost all line types in the UI are using shaders that add geometry, so they can be any width even on some Macs that don’t otherwise support line_width greater than 1. Except for one: dotted/dashed lines. We still use these in quite a few places, sometimes even using them as solid lines. Anyway this one shader always makes 1-pixel wide lines on these problematic Macs, and those users quite often have high-dpi displays, making them almost invisible. And then we have some people who need large UI scale and/or wide lines for accessibility reasons, like one fellow who is almost blind. So just hoping that a refactor of that one shader could be on your “to do” list. ", "Shadow caustics visible through colored glass has intensive, solid color for directional/sunlight and are probably too dark for spotlight/pointlight\nOperating system: Windows 11\nGraphics card: GTX 1070 Ti\n\nBroken: 3.22 master\nWorked: none\n\nThis happens when transparent object intersects with diffuse one and caustics are visible though volume. I know that MNEE doesn't work with volumes, but I think this might be a bug.\nFor directional light and sunsky system caustics are colored to pure red, green or blue or are just white. No other colors are possible. Spotlight and pointlight work, but color of intersected primitives differs substantially from not intersecting ones when looking thought them. This is especially visible on the left upper sphere that has only slight tint. Hope this is useful.\n\nmnee nishita sunsky:\n\n\nmnee directional light:\n\n\nmnee spotlight:\n\n\n\n1. Create an object casting caustics like sphere over default cube.\n2. Create transparent material for sphere that consists of two shaders, glass and volume, adjust volume color to something darker then white\n3. Turn on caustics for light and for objects, render in viewport.\n4. Move the sphere so it intersects with the cube, see the result.\n5. Switch light into directional mode and try to adjust volume absorption color.\n\n...or just open attached file and render. Lighting is set to nishita sky, but both spotlight and directional light are added and hidden.\n[mnee_test_master.blend](mnee_test_master.blend)", "EEVEE: Contact shadows problem on layered hashed materials\nOperating system: linux open source drivers\nGraphics card: rx 6800\n\nBroken: 2.93\nWorked: Never (2.83+)\n\ncontact shadows dont look correct on certain angles for layered alpha hashed materials(hair cards for example). iissue is more noticable in viewport then in final render, but it is noticable in both.\n\nmake a sphere make it alpha hashed and slightly transparent then duplicate and scale geometry with slight offset to make layers then rotate around object with contact shadows enabled on the lamp\n\n\n[contact shadows problem.blend](contact_shadows_problem.blend)", "Light show wireframe on alembic animation, and light pass throught some places of the mesh\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nCYCLES - I imported a alembic animation of a missile, when i try to add a point light on it, it show the wireframe. Also an other issue is if i add the light in the back of my missile, light pass throught my mesh at somes places. Very strange. Maybe a bug with .abc ?\n\nI attached a blend file, very simple scene. Just imported a .abc animation and parent a light to it .\n\n", "Add \"Island\" mode to UV-Sync-Selection\nIn the UV Editor, it would be nice to have UV-Island Selection mode still be available, even when UV-Sync-Selection is active.\n\n", "Cycles: ray & shader counters\n[D4204: Ray and Shader counters for Cycles](D4204)", "Regression: Themes: Highlight color in the text menus\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6.2\n\nThe highlight color is not longer adjustable by the Selected color in the User Interface / Menu Item panel. But changes with the Inner color. This breaks theming.\n\n\n- Enter Preferences. \n- Navigage to Themes tab, User Interface, Menu Item panel.\n- Play around with the Selected and Inner color\n\n", "Eevee Light Limitation failing to render at well under light limit\nOperating system: OS X 11.5.2\nGraphics card: AMD Radeon Pro 580\n\nAlso on Intel HD 6000, macOS 10.14.\n\nBroken:2.93.1 (2.93.1 2021-06-23), 2.93.5, 3.0 a217e043be\nWorked:\n\n\nUnder the impression that 128 lights is the limit. My system's render is failing at 11 area lights\nI have an image of what it is doing. It splits the viewport into four areas yellow, red, blue, green\n\n\n\n\n- On Default cube scene, add eleven area lights.\n- Set Shadow settings -> both of Cube size or Cascade Size to 4096.\n- Viewport render using Eevee.\n\n\n[Light ViewportRender ERror.blend](Light_ViewportRender_ERror.blend)" ]

[ "Cycles lamp - different results in 2.76b and current master - IES lights compatibility issues\nWin10 64bit, i7-5820K, 2xGTX970\n\nBroken: 2.76 e24323e, 2.76b official\nWorked: ----\n\nI use the [IES2Cycles addon ](ies2cycles.py) to generate node tree for lamps but this addon does not work correctly with the newest Blender build from buildbot. I tried to generate the nodes in the 2.76b Blender and than open it in the buildbot blender but there were some other problems - the intensity of the lamp changed to negative values (black spots in the scene).\n\n[Ies.blend](Ies.blend)\n1.) Open the file in the buildbot Blender and switch to rendered view - you can see a bright spot on the ceiling but the ceiling should be dark.\n2.) Open the file in the 276b official, switch to rendered view and the the lamp shines correctly.\n3.) Save the file in the 276b official and open it in the buildbot version. Switch to rendered view and you see a black spot on the ceiling. \n4.) Save the file in the buildbot version and open it in the 276b official. Switch to rendered and the whole scene is completely black. \n" ]

[ "Crash when modifing materials after using BMesh in Depsgraph-Pre event\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\n\nBroken: version: 3.0.0\nBroken: version: 3.0.1 Release Candidate\nBroken: version: 3.1.0 Alpha\n\nI wrote a script with a function that copies a mesh via BMesh to another object and then changes it's materials. When I want to export the scene as an alembic, Blender crashes when the function gets called via the Depsgraph_Pre event. Depsgraph_Post and Frame_changed_Pre & Post all work fine.\n\n\n- Open the attached Depsgraph_Pre_Crash.blend file in Blender\n- Run the script\n- (Optional) Scroll on the timeline between frames 1 & 2 to check that the script works\n- Set the active frame on the timeline to 1\n- Export as alembic with default settings\n- Blender crashes\n[Depsgraph_Pre_Crash.blend](Depsgraph_Pre_Crash.blend)\n\n[Depsgraph_Pre_Crash.crash.txt](Depsgraph_Pre_Crash.crash.txt)\n\nHere is the callback registered in `depsgraph_update_pre`:\n```lines=10,lang=python\ndef updateFrame(scene): \n```\n emptyObject = bpy.data.objects[\"EmptyObj\"]\n firstOBJ = bpy.data.objects[\"Frame1\"]\n secondOBJ = bpy.data.objects[\"Frame2\"]\n```\n\n```\n if(scene.frame_current == 1):\n bmNew = bmesh.new()\n bmNew.from_mesh(firstOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n```\n\n #Doing anything with the materials crashes blender on alembic export\n```\n emptyObject.data.materials.clear()\n```\n\n```\n if(scene.frame_current == 2):\n bmNew = bmesh.new()\n bmNew.from_mesh(secondOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n \n emptyObject.data.materials.clear()\n```\n", "Material Tab freeze still\n|**Operating system**:|Linux version 5.11.11-200.fc33.x86_64 ([email protected]) (gcc (GCC) 10.2.1 20201125 (Red Hat 10.2.1-9), GNU ld version 2.35-18.fc33)\n| -- | -- |\n|**Graphics card**:|OpenGL version string: 4.3 (Compatibility Profile) Mesa 20.3.5\n||NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1) (prog-if 00 [VGA controller])\n\nBroken: 2.83lts - 2.92.0 (Blender version has been downloaded from the Snap Store).\nThis same freeze also happens if using Blender from the Software store (2.91.2) or via the \"dnf\" command.\nWorked: N\\a\n\nIn Eevee, when opening the material tab, either blender crashes or my entire system freezes up and becoming completely unusable and requires a hard reset.\nwatch?v=te6IaP12Gbg&ab_channel=WhitequillRiclo\n\nPerhaps it is related to the compilation of shaders in the material icon.\n\n- Open the Material tab", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "Weird VSE crash\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) no clue\n\nBlender crashes on opening file. Was trying to make an alternative caption that gets around the Multiply color issue #112267 but came across a new bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nOpen the file I've attached\n\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "Rendering large scene causes viewport shading rendered to go out of memory\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Alpha\n\nwhen dealing with large files and scenes in Cuda or optix, rendering the scene then stopping and closing the render, causes the viewport shading rendered view to give out of memory when switch back to it, it renders normally before hitting F12, after hitting render and everything compile and render, when closing the rendered and switching back to viewport rendered view it gives out of memory and its stuck with it and I need to restart blender to make the viewport render work again.\n\nseems it keeps the memory full even after I close the render so there is no memory for viewport I have no idea (I'm not a programmer :D) \n\nWorks normally in 3.4.1\n\nThank you\n\n- Open large files (like view?usp=sharing)\n- set Cycles Render to Cuda or Optix\n- Press F12 to Render and ESC to cancel\n- Close render window\n- Set viewport shading to rendered\n\nSee \"out of memory\" issue\n\n", "Cycles GPU crash when switching to Rendered 3DViewport --MacOS 13.1--\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.5.0 Alpha (works fine)\n\nInstant crash of blender when switching to rendered 3DView.\n\nCompile latest 3.5 version as of 2022-12-18 20:06, hash: `50c7eb14f4`\nopen empty scene provided below and switch to rendered 3DView.\n[gpu.blend](gpu.blend)\n\n\nxcode 14.1\nlatest brew updates\n(cycles-cache & build-darwin folders deleted before compiling )\n\nPS: When switching to CPU there is no crash. Only GPU !", "Evee crashes when rendering \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.3\n\nRendering this file with evee causes a crash. Cycles is able to render the file.\nThe mesh was originally created in blender 2.6x with blender internal textures down loaded from blend swap 6618\nI was updating the textures for 2.9.3. \n\nRender the image.[crash.txt](crash.txt)\n\n[debug.blend](debug.blend)\n\n", "different generation of graphic card won't utilise together.\nOperating system: Windows 10\nGraphics card: Radeon R9 295X2 (secondary chip) + Radeon RX560 4GB\nAMD Ryzen 1700X\nMSI X370 Gaming Pro Carbon\n3 * 8GB DDR4-2400\n\nBroken: 2.82.7 to 2.83.3 <--- where x is from 0 to current stable version\nWorked: 2.8, 2.83.4 (partly worked, may end up sudden wattman reset)\n\nRadeon Version: 20.7.2\n\nafter the 3rd step, the render did not show anything, switching back to material viewport, the whole program was frozen. not sure if that is graphic card problem, but that way i could not even render anything. on 2.82.7, this also happened and the render kernels failed to work.\n\n\n1. open up a file of as shown\n2. set the preferences that would use OpenCL to render with R9 295X2 (and RX560)\n3. preview in Cycles\n4. unable to load the preview, switch back to material viewport.\n\n[zeta school 1.blend](zeta_school_1.blend)", "Blender development todo list -- Render\nNOTE: this is a direct dump of Render (without cherrypicking the valid items)\n\n### Render & UI\n\n- [ ] While rendering, manipulating images (like reload, resizing generated) can still crash Blender. Better image \"owner\" locking is required for 2.5 (#28477)\n- [ ] While rendering, several UI changes can cause crashes (#24758)\n- [ ] Rendering can't really use normal scene data if ui is interactive without causing all kinds of trouble, for examples and related issues see the item above this one.. and the reports (#26535)\n- [ ] Renaming scene leads to missing rendered result in image editor and compositor (see (#30222))\n- [ ] Rendering with File Output nodes could produce unwanted output images, see (#38605)\n- [ ] Shaded draw mode (using render code for vertex colors) is most certainly not coming back\n- [ ] Color Management can be communicated better, like when sampling colors in Image Window it confuses (could indicate such). Color Management also wasn't added backward compatible, disabling it gives dark results.\n- [ ] Compositor \"file out\" node doesn't work for FSA, and as color management troubles too.\n- [ ] FSA render uses temp files with names preventing other Blender instances to render too. (#28314)\n- [ ] Texture nodes have been implemented by recursively (backwards) calling parent nodes, this gives issues for viewers, previews and threads in general.We will try to keep it stable, but the functionality for this is going to replaced with a better shader system in 2.6. (compositor and material nodes call nodes forward, sorted on dependency. Each node is only called once this way).\n- [ ] Render display in Image window, for a window previously showing UV editor, doesn't restore correctly. (#26828). Code for this is too much spread around and fuzzy, needs full revision.\n- [ ] Object transform is not possible during rendering #37019\n- [ ] Don't render and warn when a driver or pre-render script can't be executed, a texture is missing, physics are not baked. Needed e.g. when renderfarms have scripts blocked.\n\n### Node Textures\n- [ ] Grouping texture nodes affects on data range #45696\n\n### Baking\n- [ ] add option to smooth vertex colors as a post process after baking #35066.\n- [ ] Baking to a low-res textures might miss pixels which lies on the UV island boundary #37681\n- [ ] Vertex baking might cause AO artifacts #44178\n- [ ] Support dupligroups #43553\n- [ ] Modifier produces non deterministic effects #42015\n- [ ] Update Blender side baking to support different topologies needed for adaptive subdivision #49405", "Particle Edit mode for non hair particles - particles viewport display option crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.79\n\nIn Particle Edit mode, you can enable Particles display in Tool Properties > Options > Viewport Display. Pressing this toggle crashes Blender.\n\nFor convenience use this Blend file:\n[particlespath.blend](particlespath.blend) \n\n - Press the toggle in Tool Properties > Options > Viewport Display called 'Particles'\n - Crash\n\n\n\n", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n", "Wireframe opacity doesn't work if object is \"in front\" and viewport shading is set to material preview or rendered.\nBroken: 3.0\nWorked: \n\nWireframe opacity slider doesn't work if the object is \"in front\" and \"texture space\" is checked and viewport shading is set to material preview or rendered.\n\nSelect Cube\nObject properties-> viewport display -> in front ON\nObject properties-> viewport display -> texture space ON\nIn the viewport overlay panel, drag the wireframe opacity to lower the value.\nchange the viewport shading to preview or rendered, wire will have full opacity.", "Crash when rendering animation\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.0\n\n\nI was rendering a simple camera animation overnight, Blender crashed about 2/3rd the way through. Here's the crash log.\n", "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n" ]

[ "3.2 Alpha : Eevee crashes when enabling Bloom\nOperating system: Linux-5.8.0-44-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14739 Core Profile Context 21.30\n\nBroken: version: 3.2.0 Alpha\nWorked: 3.1\n\nEevee crashes when enabling Bloom\n\n[Switch to Eevee in the Render Properties > Enable Viewport Shading Rendered > Enable Bloom\n\nEmpty Scene with the Default Cube\n\nERROR (gpu.shader): EEVEE_shaders_bloom_downsample_get FragShader: \n```\n | \n```\n 358 | vec3 safe_color(vec3 c)\n```\n | \n | Error: (#248) Function already has a body: safe_color\n```\n[blender.crash.txt](blender.crash.txt)\n", "[EEVEE] Enabling Bloom Crashes Blender\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.2.0 Alpha\nWorked: Not sure. Haven't used Eevee in the past few builds.\n\nEnabling Bloom in Eeevee and going in to Rendered mode crashes Blender.\n\n1. Setup a basic scene - add model / light / camera.\n2. Go to Rendered Mode.\n3. Enable Bloom in Eevee.\n4. Crash.\n\nHere's the crash error.\n\n> ERROR (gpu.shader): EEVEE_shaders_bloom_downsample_get FragShader:\n> |\n> 358 | vec3 safe_color(vec3 c)\n> |\n> | Error: C1013: function \"safe_color\" is already defined at 0(241)\n> \n\n\n\n", "latest 3.2 alpha quits right after start without a message\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.2.0 Alpha\n\nwhen starting blender it closes instantly again without an error message\n\nin the command prompt is the following:\nERROR (gpu.shader): EEVEE_shaders_bloom_downsample_get FragShader:\n```\n |\n```\n 358 | vec3 safe_color(vec3 c)\n```\n |\n | Error: C1013: function \"safe_color\" is already defined at 0(241)\n```\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7C3AD03E0\nModule : blender.exe\nThread : 00004ea8\nWriting: C:\\Users\\gerno\\AppData\\Local\\Temp\\blender.crash.txt\n\n[blender.crash.txt](blender.crash.txt)\n\n\n", "[EEVEE] Enabling Bloom Crashes Blender\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D500](D500) OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nEnabling Bloom in Eeevee and going in to Rendered mode crashes Blender.\n\n1. Open General template\n2. Go to Rendered Mode.\n3. Enable Bloom in Eevee.\n4. Crash.\n\n" ]

[ "Running multiple instances of Cycles HIP ends in segfault\nOperating system: Windows 10\nGraphics card: 2x Radeon W6800 32GB\n\nBroken: 3.0.0, 3788003cdaeb, master, 2021-11-30\nWorked: Never\n\nWhen I have 2 instances of Cycles rendering using HIP at the same time on a particular production scene, one instance will crash with the following error: \n\n\n```\n...\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.57 | Mem:1469.81M, Peak:1469.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Furniture_Roughness.png\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.70 | Mem:1533.81M, Peak:1533.81M | Scene, View Layer | Updating Images | Loading Metal02_nrm.jpg\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.73 | Mem:1569.81M, Peak:1569.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Objects_normal.png\nFra:441 Mem:9030.99M (Peak 9030.99M) | Time:00:21.73 | Mem:1570.69M, Peak:1570.69M | Scene, View Layer | Updating Images | Loading Tires_rough.png\nMalloc returns null: len=37748736 in Cycles Aligned Alloc, total 1149156740\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFED98C853D\nModule : amdhip64.dll\nThread : 00000734\n\n```\nI was unable to reproduce it in a simple scene or any commonly available demo scenes such as classroom or Barbarshop. And unfortunately I cannot share the particular scene that's causing the issue. But the scale of the scene that's crashing should easily fit onto the GPU vram three times.\n\nI've attached the crash report. If more info is needed I will try to create a dummy scene that show the same behavior.\n\n[Anim-A-Garage.crash.txt](Anim-A-Garage.crash.txt)", "GPU Subdivision Causes Artifacts in Mesh Analysis Overlay\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken:\nversion: 3.1.1 Release Candidate\nversion: 3.3.1\nversion: 3.5.1\nversion: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-25 13:50, hash: 6ee8aa4997ee, type: release\nversion: 3.6.0 Alpha\n\nWorked: could not find.\n\nWhen GPU subdivision is enabled, the Mesh Analysis overlay shows artifacts.\n\n\nPlease follow these steps to reproduce the issue:\n1. Start Blender.\n2. Select the default cube.\n3. Apply the Subdivision Modifier (press Ctrl+1).\n4. Enter edit mode.\n5. In the viewport overlay menu, enable Mesh Analysis.\n\n**Known Workarounds**\n1. Disable GPU Subdivision.\n2. Disable \"Show in Edit Mode\" for the Subdivision modifier.\n\n", "Blender sometimes crashes when loading a file with unregistered nodes\nOperating system: Windows 10 64 Bit\nGraphics card: Nvidia Geforce GTX 750 Ti\n\nBroken: 2.83.7 release\n\nSometimes when opening a file with unregistered custom nodes, Blender will crash with an `EXCEPTION_ACCESS_VIOLATION` error.\n\n**Stack trace from Visual Studio:**\n```\nblender.exe!node_free_node(bNodeTree * ntree, bNode * node) Zeile 2033\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\node.c (2033)\nblender.exe!ntree_free_data(ID * id) Zeile 227\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\node.c (227)\nblender.exe!BKE_libblock_free_datablock(ID * id, const int UNUSED_flag) Zeile 136\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\lib_id_delete.c (136)\nblender.exe!DEG::deg_free_copy_on_write_datablock(ID * id_cow) Zeile 1073\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (1073)\nblender.exe!DEG::deg_update_copy_on_write_datablock(const DEG::Depsgraph * depsgraph, const DEG::IDNode * id_node) Zeile 952\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (952)\nblender.exe!DEG::deg_evaluate_copy_on_write(Depsgraph * graph, const DEG::IDNode * id_node) Zeile 1088\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (1088)\nblender.exe!std::invoke<void (__cdecl*&)(Depsgraph *,DEG::IDNode const *),Depsgraph *,DEG::IDNode * &>(void(*)(Depsgraph *, const DEG::IDNode *) & _Obj, Depsgraph * && _Arg1, DEG::IDNode * & <_Args2_0>) Zeile 1626\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1626)\nblender.exe!std::_Invoker_ret<std::_Unforced,0>::_Call<void (__cdecl*&)(Depsgraph *,DEG::IDNode const *),Depsgraph *,DEG::IDNode * &>(void(*)(Depsgraph *, const DEG::IDNode *) & <_Vals_0>, Depsgraph * && <_Vals_1>, DEG::IDNode * & <_Vals_2>) Zeile 1658\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1658)\nblender.exe!std::_Call_binder<std::_Unforced,0,1,void (__cdecl*)(Depsgraph *,DEG::IDNode const *),std::tuple<std::_Ph<1>,DEG::IDNode *>,std::tuple<Depsgraph * &&>>(std::_Invoker_ret<std::_Unforced,0> __formal, std::integer_sequence<unsigned __int64,0,1> __formal, void(*)(Depsgraph *, const DEG::IDNode *) & _Obj, std::tuple<std::_Ph<1>,DEG::IDNode *> & _Tpl, std::tuple<Depsgraph * &&> && _Ut) Zeile 1388\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (1388)\nblender.exe!std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &>::operator()<Depsgraph *>(Depsgraph * && <_Unbargs_0>) Zeile 1427\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (1427)\nblender.exe!std::invoke<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> &,Depsgraph *>(std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> & _Obj, Depsgraph * && _Arg1) Zeile 1626\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1626)\nblender.exe!std::_Invoker_ret<void,1>::_Call<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> &,Depsgraph *>(std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> & <_Vals_0>, Depsgraph * && <_Vals_1>) Zeile 1641\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1641)\nblender.exe!std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &>,void,Depsgraph *>::_Do_call(Depsgraph * && <_Args_0>) Zeile 904\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (904)\nblender.exe!std::_Func_class<void,Depsgraph *>::operator()(Depsgraph * <_Args_0>) Zeile 952\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (952)\nblender.exe!DEG::`anonymous namespace'::evaluate_node(const DEG::`anonymous-namespace'::DepsgraphEvalState * state, DEG::OperationNode * operation_node) Zeile 117\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (117)\nblender.exe!DEG::`anonymous namespace'::deg_task_run_func(TaskPool * pool, void * taskdata, int thread_id) Zeile 129\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (129)\nblender.exe!BLI_task_pool_work_and_wait(TaskPool * pool) Zeile 939\n\tunter C:\\blender-git\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc (939)\nblender.exe!BLI_task_pool_work_wait_and_reset(TaskPool * pool) Zeile 970\n\tunter C:\\blender-git\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc (970)\nblender.exe!DEG::deg_evaluate_on_refresh(DEG::Depsgraph * graph) Zeile 403\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (403)\nblender.exe!DEG_evaluate_on_refresh(Main * bmain, Depsgraph * graph) Zeile 65\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\depsgraph_eval.cc (65)\nblender.exe!scene_graph_update_tagged(Depsgraph * depsgraph, Main * bmain, bool only_if_tagged) Zeile 1329\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\scene.c (1329)\nblender.exe!BKE_scene_graph_update_tagged(Depsgraph * depsgraph, Main * bmain) Zeile 1367\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\scene.c (1367)\nblender.exe!wm_event_do_depsgraph(bContext * C, bool is_after_open_file) Zeile 360\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (360)\nblender.exe!wm_event_do_refresh_wm_and_depsgraph(bContext * C) Zeile 387\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (387)\nblender.exe!wm_event_do_notifiers(bContext * C) Zeile 552\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (552)\nblender.exe!WM_main(bContext * C) Zeile 456\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm.c (456)\nblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Zeile 530\n\tunter C:\\blender-git\\blender\\source\\creator\\creator.c (530)\nblender.exe!invoke_main() Zeile 79\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (79)\nblender.exe!__scrt_common_main_seh() Zeile 288\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (288)\nblender.exe!__scrt_common_main() Zeile 331\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (331)\nblender.exe!mainCRTStartup() Zeile 17\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp (17)\nkernel32.dll!00007ffca1667bd4()\nntdll.dll!00007ffca1e0ce51()\n```\n\nThe exception in line 2033 of node.c says that there is an access violation when reading at position `0xFFFFFFFFFFFFFFFF`. `node->typeinfo` does exist (is not null), but `freefunc` (and actually most of the other attributes) point to `0xdddd...`. Because of that, I think that this bug might be caused by a similar issue as described in #72833.\n\nI'm not sure if a core dump helps you, it's quite large (1GB + another GB for the .pdb file) so if you need it I can look for a way to make it available to you. I'm not a C or C++ dev so I don't know what is helpful.\n\n**EDIT**: I think this crash is caused by opening files files with nodes that were registered while the file was originaly saved but not anymore.\n\nIt's a bit complicated because it doesn't happen all the time. The particular file(s) where I observed this issue use nodes from an addon (Armory3D) which supports per-project custom nodes which get registered via a `on_load_post()` handler (so there is a delay between opening the file and registering the nodes). I'm not entirely sure, but it seems like the crash occurs when the nodes are registered again. The crash even occurs when unregistering the nodes before saving the file.\n\nBecause of that complicated setup (addon required + project setup + custom node package) I will go without an example file. If you aren't able to find the cause without one, please tell me so that I can prepare a minimal project setup for you.\n\nThank you very much!\n\n*Original issue*: 1890", "Mesh to Volume modifier is recalculated even if the volume object is disabled/hidden\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nI'm disabling the volume object in the viewport to move the origin mesh, but the viewport is lagging until I turn off the \"Mesh to Volume\" modifier.\nMaybe it is better to not compute the \"Mesh to Volume\" modifier while the volume object is hidden/disabled?\n\n- Open attached file\n- hide the volume object\n- move the origin mesh\n[H.blend](H.blend)\n\n", "Crash when run the script code follow\nOperating system: Mac 11.4\nGraphics card: Intel Iris 1536 MB\n\nBroken: 3.0.1(2022-01-26)\n\nBlender crashed when running the script followed in \"Scripting Window\":\n\n```\nimport bpy\n\nfor obj in bpy.data.collections['Bg_objects'].all_objects:\n obj.is_holdout = True\n```\n\nAddressSanitizer error log:\n```lines=20\n==34714==ERROR: AddressSanitizer: heap-use-after-free on address 0x00015d792c38 at pc 0x00010523645c bp 0x00016fdfa1d0 sp 0x00016fdfa1c8\nREAD of size 8 at 0x00015d792c38 thread T0\n - 0 0x105236458 in rna_iterator_listbase_next rna_access.c:4677\n - 1 0x1053cc940 in Collection_all_objects_next rna_collection_gen.c:209\n - 2 0x105234920 in RNA_property_collection_next rna_access.c:3690\n - 3 0x105f6c330 in pyrna_prop_collection_iter_next bpy_rna.c:7107\n - 4 0x11366ad40 in _PyEval_EvalFrameDefault ceval.c:4001\n - 5 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 6 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 7 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 8 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 9 0x10a275444 in text_run_script text_ops.c:773\n - 10 0x10a275284 in text_run_script_exec text_ops.c:812\n - 11 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 12 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 13 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 14 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 15 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 16 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 17 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 18 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 19 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 20 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 21 0x1030043ec in WM_main wm.c:623\n - 22 0x10000ba94 in main creator.c:544\n - 23 0x1454710f0 in start+0x204 (dyld:arm64e+0x50f0)\n\n0x00015d792c38 is located 8 bytes inside of 80-byte region [0x00015d792c30,0x00015d792c80)\nfreed by thread T0 here:\n - 0 0x145a890f0 in wrap_free+0x98 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d0f0)\n - 1 0x1151b28e8 in MEM_lockfree_freeN mallocn_lockfree_impl.c:116\n - 2 0x114b67940 in BLI_freelistN listbase.c:463\n - 3 0x1003acbf8 in collection_object_cache_free collection.c:816\n - 4 0x1003aca74 in BKE_collection_object_cache_free collection.c:826\n - 5 0x100e4b080 in BKE_main_collection_sync_remap layer.c:1366\n - 6 0x1059bcf0c in rna_Object_hide_update rna_object.c:370\n - 7 0x105257fa8 in rna_property_update rna_access.c:2069\n - 8 0x105257bac in RNA_property_update rna_access.c:2138\n - 9 0x105f50268 in pyrna_py_to_prop bpy_rna.c:2083\n - 10 0x105f54308 in pyrna_struct_setattro bpy_rna.c:4453\n - 11 0x1135de558 in PyObject_SetAttr object.c\n - 12 0x113667dd0 in _PyEval_EvalFrameDefault ceval.c:2850\n - 13 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 14 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 15 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 16 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 17 0x10a275444 in text_run_script text_ops.c:773\n - 18 0x10a275284 in text_run_script_exec text_ops.c:812\n - 19 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 20 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 21 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 22 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 23 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 24 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 25 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 26 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 27 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 28 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 29 0x1030043ec in WM_main wm.c:623\n\npreviously allocated by thread T0 here:\n - 0 0x145a89380 in wrap_calloc+0x9c (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d380)\n - 1 0x1151b13b8 in MEM_lockfree_callocN mallocn_lockfree_impl.c:222\n - 2 0x1003b5754 in collection_object_cache_fill collection.c:754\n - 3 0x1003b5d20 in collection_object_cache_fill collection.c:775\n - 4 0x1003b53b0 in BKE_collection_object_cache_get collection.c:786\n - 5 0x1053cc5d8 in rna_Collection_all_objects_begin rna_collection.c:54\n - 6 0x1053cc2d0 in Collection_all_objects_begin rna_collection_gen.c:200\n - 7 0x105233a88 in RNA_property_collection_begin rna_access.c:3674\n - 8 0x105f6c158 in pyrna_prop_collection_iter_CreatePyObject bpy_rna.c:7076\n - 9 0x105f67ef0 in pyrna_prop_collection_iter bpy_rna.c:7083\n - 10 0x11357f400 in PyObject_GetIter abstract.c:2813\n - 11 0x11366ac34 in _PyEval_EvalFrameDefault ceval.c:3958\n - 12 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 13 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 14 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 15 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 16 0x10a275444 in text_run_script text_ops.c:773\n - 17 0x10a275284 in text_run_script_exec text_ops.c:812\n - 18 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 19 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 20 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 21 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 22 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 23 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 24 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 25 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 26 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 27 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 28 0x1030043ec in WM_main wm.c:623\n - 29 0x10000ba94 in main creator.c:544\n```\n\n- Open attached file\n- Go to Scripting workspace\n- Run the above script\n[bug.zip](bug.zip)", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n", "Output UVs from mesh primitive nodes with anonymous attributes\nInstead of creating a named `uv_map` attribute on the geometry, they should be anonymous attribute field outputs. This brings up a few complications.\n- Currently we have no 2D vector socket. We probably want to avoid adding this for 3.0, so a 3D vector can be used for now. Automatic conversions will make versioning simple when we add a 2D vector socket, hopefully for 3.1.\n- The BMesh mesh primitive icosphere creates an `MLoopUV` attribute, this should be converted into a 3D vector anonymous attribute.\n\nThe output should be called \"UV Map\"", "GPU: Workarounds and Device Features checks becoming obsolete\nBlender 4.0 bumped its OpenGL version from 3.3 Core profile to 4.3 Core profile. Some workarounds and optional device features were added to the GPU Backend in order to emulate features that were not available on all platforms.\n\nThis issue contains a list of features, workarounds that we should revisit.\n\n* `shader_draw_parameters` In Vulkan these seems to be supported even on low end devices (displayreport.php?id=23923#features_core_11) we might want to consider making this a requirement, although it is not required by vulkan.\n* `compute_shader_support` is required for workbench-next\n* `shader_storage_buffer_objects_support` is required (#112572)\n* `shader_image_load_store_support` is required. \n* `clear_viewport_workaround` should be solved by the editor, not by the gpu backend. IIRC the VSE has fixed this some months ago.\n* remove `--debug-gpu-disable-ssbo` as SSBO's are required. (#112571)\n\n", "Eevee: Volume Sampling for Purely Emissive Shader Behaves Strangely\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 3.5.0 Alpha\nWorked: perhaps never? (tested until 2.83)\nFor purely emissive shader, increasing sample count will disappear volume shader\n\n- Open attached file\n- Increase sample count in `volumetric` panel\n[eevee_volume_emission_sampling.blend](eevee_volume_emission_sampling.blend)\n[eevee_emissive_volume_sampling-2022-12-01_12.51.17.mp4](eevee_emissive_volume_sampling-2022-12-01_12.51.17.mp4)\n", "Eevee - no volume density textures when using Vega 64 external gpu on macOS Mojave\nOperating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26\n\n\nBroken: version: 2.80 (sub 74)\nWorked: Was working briefly with some builds in March 2019.\n\n\nMacOS Mojave external GPU fails to render volumetric on Eevee if there is a density texture. Internal GPU works fine.\n\nUsing external Vega 64:\nOn default cube, add principled volume shader to volume material output: volume looks correct.\nPlug noise texture node into density input of principled volume shader: volume disappears.\nUsing internal Radeon 560x:\nExact same steps gives properly textured volume.\n\n", "Lattice UVW input Glitch\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nClick dragging vertically through the UVW parameters of a Lattice will let you select all 3 parameters (as expected).\nBut, entering a new number will only change the 1st of the 3 selected parameters.\nWeirdly, click drag selecting all three parameters and entering nothing-at-all and then clicking away will somehow enter in the correct number that was entered one attempt back in time.\n\nStart a new General file and delete all objects.\nAdd a Lattice.\nGo to the Lattice Properties.\nClick and drag down through the U, V and W fields.\nEnter a new number.\nNotice that only 1 of the parameters changed (when all 3 should have changed).\nClick and drag down through the U, V and W fields again.\nClick away.\nNotice how the other 2 parameters \"catch up\" to the first 1.\n\n", "NaN pixels in Normal Pass\nOperating system: Linux-3.10.0-1127.10.1.el7.x86_64-x86_64-with-centos-7.8.2003-Core 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.83.0\nWorked: (Unknown)\n\nI produced a template based rendering solution and am experiencing occasion nan pixels in the normal pass output. Nan pixels are occurring in both CPU and GPU renders on a number of different hardware configurations.\n\nI've stripped down one of the files that exhibit the issue, see nan pixel at x162, y78 of normal pass.\nChanging visibility of the lights collection, specifically the 'LightArea', removes the pixel. Changing render resolution, sample seed, or adaptive sampling, can remove bad pixels.\nDisconnecting the normal map node on the geometry object's material removes the pixel. Providing input to that node, both textures and noise, has no effect on the pixel.\nChanging the transform on the rendered geometry removes the nan, regardless of whether the pixels occur on transparent background.\n\n[nan_pixel_isolated.blend](nan_pixel_isolated.blend)", "Extra face dots in UV Layout editor (GPU subdivision OFF, On Cage OFF in Subdivision modifier make a difference)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4835\n\nBroken: version: 3.4.1\nBroken: version: 3.1\nWorked: not since GPU subdivision was introduced (so in a way, it was working in 3.0)\n\nExtra random faces appear in the UV Layout editor\n\n- I can mosty repro this if GPU Subdivision in Preferences > Viewport > Subdivision is OFF\n- It does not happen at all if I turn off `On Cage - Adjust edit cage to modifier result` on the SubSurf modifier.\n\nIn the attached file, toggle from face select mode to vertex select mode and back to face select mode. (Might have to repeat 5-6 times) Extra faces appear in the UV Layout editor. Also see here: [1457172]\n\n", "Workbench: Cull before batch creation during viewport animation rendering\n\n## Current Situation\n\nWhen drawing an object (eg sending draw calls to the GPU) the object boundary sphere is tested against the active view). When the test fails the object isn't send to the GPU. Before this happens the GPUBatches were already generated.\n\nWhen doing animation playback this could lead to the situation that the GPU Batches are calculated, but not used.\n\n## Target Situation\n\nWhen using the Overlay engine/Workbench engine we could test the objects to the default view (e.g viewport). When this fails we could skip this object at all. This feature would be disabled when the shadows are turned on and only enabled when doing an image/animation render.\n\nA consistent framerate is more important to animators then having some frames faster.\n", "GPU subdivision: Wrong object's size when using subdivision surface modifier with GPU subdivision\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia Geforce GTX 660\n\nBroken: 3.1\nWorked: 3.0\n\nWhen GPU subdivision is activated, the object with subdivision surface doesn't show the correct size on the dimension section of the properties' sidebar.\n\nSelect the default cube.\nAdd Subdivision surface modifier\nOpen the properties' sidebar with N, the dimensions should be 1,68m (for X, Y and Z) but it shows 2,0m for all the axes. By deactivating the \"GPU subdivision\" the panel shows the correct dimensions.\n" ]

[ "Cycles crash hiding/unhiding volumes\nOperating system: Linux-4.15.0-156-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 5500 (BDW GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 3.0.0 Alpha\n\nHi I have a crash that occurs in view rendering mode when I switch from local view of an object to normal view always with the view-port with active rendering, I have attached the file, and I cannot find the debug of the crash anywhere too by running Blender with the --debug-all option\n\n1 start the rendering preview in the view

port\n2 select a sphere in local view mode with the /\n3 return to the full view by pressing /\n\nfile attached\n[Cycles-Volume-Bug.blend](Cycles-Volume-Bug.blend)\n\n\n" ]

[ "Mask Opacity keyframes not visible anywhere.\nUbuntu 14.04 64x\nnVidia GT620\n\nBroken: 2.78a\n\nKeyframes in LayerMask \"Opacity\" or \"Invert the mask B/W\" can be created. These keyframes exist in an existing Action (can be seen in Outliner - Actions and has datapath), but they don't appear in DopeSheet - DopeSheet nor DopeSheet - Mask. They can't be modified as the other keyframes. Nor changing its type (keyframe, interpolation, handle).\n\n- Open this file: [101-mask-keyframes.blend](101-mask-keyframes.blend)\n- Check the MaskLayer Opacity animation by going from 10 to 20 and back. Keyframes are visible only in the slider (as yellow slider).\n- The same with \"Invert the mask B/W\". Frame 30 and 40 have keyframes.\n\nEDIT: file uploaded.", "Can't undo the keyframe change in edit mode\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nWhile in edit mode, when you hit Undo in the graph editor after moving a keyframe, the graph doesn't change.\n\n- Animate anything using a couple of keyframes.\n- Change to edit mode in viewport\n- Switch timeline to the graph editor (not necessary, you can keep timeline as it is)\n- Select a keyframe and move it\n# Hit undo\n\nResult: The graph editor stays the same\n\nExpected: The move you just made in the graph editor should be the only thing being undone!\n\nTest file with first four steps included\n[#97700.blend](T97700.blend)", "Viewport gizmos in selection tools not updating.\nOperating system: Windows 10 64Bits\nGraphics card: GeForce GTX 1050 Ti latest driver\n\nBroken: version: 2.80.69 hash:4f6e25280558\n\nswitching between Active tools gizmos and viewport gizmos keeps the manipulators in it's previous position until a second selection...i assume because we have two different and unrelated gizmos!! \n\n\n- Activate transform gizmos in the gizmo popover.\n- Use Active tools manipulators and do transformation.\n- Switch to the selection tools.\n\nThe gizmo center is not updated.\n\n**Attachment**\n", "Sequencer doesn't reflect source range in strip display correctly\nWindows 7\n\nBroken: 2.78 Release\n\nWhen the length of a render source is modified, the display in the strip display doesn't show it. The info 'Original frame range' is correct though.\n\n1. From the default scene, create a 'link object data' copy (although i guess the type doesn't matter)\n2. Go back to scene 'Scene' and set the end frame to 100\n3. Go to scene 'Scene.001', open sequence editor and add scene 'Scene'. It will now show a strip of 100 frames length.\n4. Go back to scene 'Scene' and change the end frame to 50\n5. Go back to scene 'Scene.001' \nThe Sequence Editor will still show a green bar 100 frames long, although the info in the properties panel tells the correct info: Original frame range 1-50 (50).\nMore importantly, you can drag the right grabber of the strip to the right and it will still paint 100 frames green and the rest grey/transparent, although the 100 frames don't have any meaning no more - it was just the length it was created with. You can also unlink the strip from the original scene and relink it again, it will still paint 100 frames green/valid.\n\nMaybe this is a bug, an oversight, maybe even intentional, I don't know. \nI don't think a .blend file is necessary in this case, but I will upload one, if desired. \n", "Keyframed parameters are not preserved when frame_change_post handler is used\nOperating system: Win 10 Pro\nGraphics card: GTX 1080\n\nBroken: v2.81, master, 2018-11-26\nWorked: (optional)\n\n---\n\n\n**EDIT** by @EAW \n\n\n> In the .blend file setup, the 'mesh_cache' object would instance a cube over the vertices for display in rendering. An ocean modifier is added to the object with 'Geometry' set to Displace and the 'time' parameter is keyframed over a frame range. \n> \n> Playback in the viewport shows the ocean modifier evolving shape during the animation. If the animation is rendered, the ocean modifier does not evolve over time and the render result is static.\n> \n\n\n\n> Here is a script that generates a 2d grid of vertices in the frame_change_post handler:\n> \n> ```\n> import bpy\n> \n> def frame_change_post(scene, depsgraph):\n> # Generate a 2d grid of vertices. A cube object is set to be instanced over the vertices for rendering\n> vertices = []\n> for j in range(100):\n> for i in range(100):\n> vertices.append((i * 0.05, j * 0.05, 0.0))\n> \n> mesh_cache_object = bpy.data.objects.get(\"mesh_cache\")\n> mesh_cache_object.data.clear_geometry()\n> mesh_cache_object.data.from_pydata(vertices, [], [])\n> \n> depsgraph.update()\n> \n> \n> bpy.app.handlers.frame_change_post.append(frame_change_post)\n> ```\n> \n\n\n\n\n> Here is the .blend file including the script: [keyframed_modifier_bug.blend](keyframed_modifier_bug.blend)\n> \n> How to reproduce:\n> 1. Open .blend file\n> 2. Press 'Run Script'\n> 3. Blender > Render > Render Animation\n> \n> The result is a static animation.\n\n\n**End Edit**\n\n---\n\n\n\nI have created a FlipFluids simulation in Blender 2.81 ( 2019-11-25 21:45) and added an Ocean modifier in displacement mode to the fluid_surface. Then I have baked the complete sim from within FlipFluids.\nWhen I move from keyframe to keyframe in the default timeline everything is moving as desired in the default 3D window:\nOcean modifier waves, FlipFluids waves & wake, flags, radars...\n\nWhen I render the complete animation everything EXCEPT the ocean modifier waves are moving. The ocean modifier waves remain static but the FLIPFLUIDS waves move on that surface.\nALL modifiers and elements ARE enabled for renderings. D-NOISE: AI Denoiser is on (switching denoiser off did not help).\nComputer is a HP Z800 with dual Xeons, 72 GB of vRAM and a GTX 1060.\n\nIf I render & save the keyframes manually individually by hand the ocean surface moves! Which means I get the proper result.\n\nAs its working when rendering&saving each frame manually as image (Png) and its not giving the same result when saving out the same images (Png) when I hit render animation, I do suppose this might be a bug in 2.81.\nRunning indiviual frames via Renderpilot did not yield the proper result either. So I do suspect it might be that there is not enough time gap between saving the last frame and rendering the next. Or, something does not get purged properly.\n\nFor propriatary reasons I can not share the blend file.", "'Flipped' in Graph Editor Redo Panel for Paste Keyframes\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\nWorked: N/A\n\nWhen copying and pasting keyframes in the Graph Editor, the Redo panel has an option called 'Paste Flipped.' This is a highly-specific and confusing option.\n\n - Create an F-Curve with keyframes\n - Graph Editor Key Menu > Copy Keyframes\n - Graph Editor Key Menu > Paste Keyframes\n - Open Redo Panel\n # Enable and disable 'Flipped'\n\n**More Info**\nThe 'Flipped' option's description says that it pastes keyframes from mirrored bones if they exist. That is not at all my initial expectation of 'Flipped' in this context. I would expect the F-Curves to either be flipped on the X-axis or Y-axis in the Graph Editor. I would also expect 'Flipped' to work with all pasted keyframes: not just those of mirrored bones.\n\n\n\nFix: D14328", "Keyframing off Animated property of rigid body on second frame of rigid body simulation\nOS: Ubuntu 13.10\nLinux kernel: 3.11.0-18-generic\n\nBroken: 2.70-b64bdb2-linux-glibc211-x86_64\n\n\nNormally, keyframing off the Animated property of a rigid body will cause rigid body to maintain its velocity and rotation that it has at the last animated keyframe. However, if the Animated property is keyframed off on the second keyframe of the rigid body simulation, the object will continue the animation from a stand-still, i.e. it loses its initial velocity / rotation.\n\n\n\nCreate bug:\n\n - Open new Blender file\n - Keyframe location of the default cube\n - Go to frame 20, move cube along the y-axis by 20 units and keyframe location.\n - Enable Rigid Body for the cube\n - Go to frame 10, enable Animated (Physics context -> Rigid Body panel) and keyframe it\n - Go to frame 11, disable Animated and keyframe it\n - Go to Scene context -> Rigid Body Cache panel, and set Start to 10 (and say, End to 50)\n - Go to 3D View and hit ALT A to start animation. Notice that when the cube reaches frame 10, it loses its y-velocity and just falls straight down.\n\nResolution:\n\n - Set the start of Rigid Body Cache to 9. \n - Update cache by unlinking the RigidBodyWorld group from Rigid Body World panel, then choose it again.\n # Play animation again, and it's fine.\n\nAlthough, I have figured out how to get it working, I think this is unexpected behaviour (which took me a long time to figure out).\n\nSteps 1-7 have already been completed in this file: [rigidBody_bug.blend](rigidBody_bug.blend)\n", "Reference image opacity value doesn't work with Blender 2.83+ (Intel HD 630 with Mesa 20, regression from D6729)\nOperating system: Mageia 8 x86_64 (Linux)\nGraphics card: Intel HD Graphics 630, Mesa 20.1.0\n\nBroken: 2.83.0, 2.90.0-aed11c673efe\nWorked: 2.82a, 2.83-ce76e17584ee\n\nIn Blender 2.82a, when using a reference image with opacity between 0.0 and 1.0, the image is properly blended using the opacity value, provided that \"Use Alpha\" is enabled. (I.e. an image with opacity 0.20 will be less visible than an image with opacity 0.80, though both are transparent - like in most image editors.)\nA few weeks back I used 2.83-ce76e17584ee, and there the \"Use Alpha\" setting was renamed to \"Transparency\", but the behavior stayed the same.\n\nOpacity working in Blender 2.82a:\n\n\nAfter updating to 2.83.0 (stable) now, I see that opacity no longer works as intended, it behaves like an on/off switch without any blending.\nAn image will look the same with opacity 0.0001 or 1.0 (and will be invisible with opacity 0).\n\nOpacity not working in Blender 2.83.0 (same .blend):\n\n\nCurrent 2.90 alpha seems to suffer from the same issue.\n\n- Add > Image > Reference\n- Pick an image\n- In object properties, enable Transparency, and try different values of Opacity. Opacity doesn't impact the blending of the reference image in the viewport (unless it's 0, which makes it disappear).", "VSE: Blade tool in Hard mode performs a Soft split (+ UI inconsistencies)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 4.0.0 Alpha\nWorked: (unknown)\n\nThe Tool Settings of the \"Blade\" tool let you choose between \"Soft\" and \"Hard\" splits, but both options perform a soft split.\n\nApart from this, there are some UI inconsistencies:\n* The tool is called \"Blade\", but the equivalent operation in the Strip menu is called \"Split\".\n* The tool's settings are called \"Soft\" and \"Hard\", but the equivalent operations in the Strip menu are called \"Split\" and \"Hold Split\".\n* The context menu has \"Split\" but is missing \"Hold Split\". (Maybe this one is intentional)\n* The context menu shows the \"K\" keyboard shortcut, but the Strip menu does not. (As a result of this point and the above, the \"Shift-K\" keyboard shortcut for performing a Hard/Hold Split is not discoverable in the UI.)\n\n* Open the VSE.\n* Add a movie strip.\n* Place the Playhead somewhere in the middle and click Strip -> Hold Split.\n* Delete the strip after the Playhead and drag the right handle of the remaining strip to the right. Notice that the newly revealed frames in the strip are dark blue; they're Hold frames as expected.\n* Delete the strip and re-add it.\n* Select the Blade tool, set the split type to \"Hard\" in the Tool Settings, and click somewhere in the strip.\n* Delete the strip after the Playhead and drag the right handle of the remaining strip to the right. Notice that the newly revealed frames in the strip are *not* dark blue; we got a Soft (non-Hold) split.\n\n", "Design: More frame snapping options\n## Problem\nWhen dragging the frame cursor around you often want to hit keyframes.\nCurrently this is hard to do, especially when zoomed out. (also because you are not sure when you've hit the key)\n\nFrame snapping already exists, but it only snaps to seconds.\nThis is activated with `CTRL`\n\n## Design Question\n* Where in the UI should this functionality live\n* How can this feature be discoverable and understandable for users\n* What are the snapping options required and how do they work\n\n## Things to consider\n* there is different snapping behaviour in the VSE, so different time editors can have different snapping functions. This needs to be clear to the user\n* In the graph editor and the dope sheet there is already a snapping menu, but that is for snapping the keys while moving them. How do we differentiate the two\n\n## Proposed Solution\nThe idea is to add an option to the way the snapping is performed, e.g. either to seconds or to keys (or another snap type)\n[2021-10-02 19-50-20.mp4](2021-10-02_19-50-20.mp4)\n\nThe snap type would be chosen in a dropdown menu\n\n\nThe subframe setting would be moved to a scene setting\n", "Can't scrub timeline with alt + pan trackpad gesture\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.105\nMacOS 10.13.6 + Apple Magic Mouse\n\nBroken: version: 2.83 (sub 15)\nWorked: never ?\n\nWhen using a Magic Mouse it's not possible to navigate the timeline using the \"ALT+scroll\" default shortcut.\nCorrect behaviour is seen in **[this ](watch?v=o19U-yPGdyY&feature=youtu.be&t=84)** official Blender video.\n\nThis shortcut is in : User Preferences > Keymap > \"Frame Offset\".\nYou'll see it's actually **two instances** of the same shortcut :\n- one to scroll forward (ALT + Wheel Down) >> `screen.frame_offset = +1`\n- another to rewind (ALT + Wheel Up) >> `screen.frame_offset = -1`\n\nThis is a problem because the Magic Mouse is actually seen as a trackpad, therefore we have to use the \"Mouse/Trackpad Pan\" event.\nUnfortunately if you do that you are only able to scroll one way, because this shorcut entry doesn't \"see\" the scrool as bidirectional.\n\nProposed fix : add a new shortcut entry, like it's been done for \"Zoom View\" and \"Pan View\" for example.\n{[F8515046](MagicMouse_timeline_scroll.jpg), size=full}\n\nOn a Mac, using a Magic Mouse :\nopen Blender, in the viewport try to do ALT+scroll > it doesn't scroll the timeline.\n\n\n", "\"Clean Keyframes\" in Dope Sheet only works if channels are selected\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 2.93.0 Alpha\nWorked: unknown\n\nThe \"Clean Keyframes\" and \"Clean Channels\" operators in the Dope Sheet editor only work if the channels containing the selected keyframes are also selected. This is unlike the \"Delete Keyframes\" operator, which works even if the channels are not selected.\n\n- Load the default startup scene.\n- Enable Auto Keying in the Timeline editor.\n- Move the cube up a bit.\n- Seek the playhead to another frame and move the cube up a bit more.\n- Switch to the Animation workspace.\n- In the Dope Sheet editor, click in an empty space of the keyframe region to deselect all keyframes and channels.\n- Expand the \"Object Transforms\" channel group and, with the mouse cursor in the keyframe region, press A to select all keyframes (but not the channels).\n- Press X and select \"Delete Keyframes.\" All keyframes and channels are deleted as expected. Press Ctrl-Z to revert.\n- Press X again, but this time select \"Clean Keyframes.\" Nothing happens despite there being plenty of keyframes to clean.\n- Move the mouse cursor to the channel region and press A to select all channels.\n- Move the mouse cursor back to the keyframe region and run \"Clean Keyframes\" again. This time, the cleanup works as expected.\n\nThe \"Clean Channels\" operator behaves in the same way.\n\nThe reason this only happens in the Dope Sheet editor and not the Graph Editor is likely that the Graph Editor automatically selects the channels for the selected keyframes, but the Dope Sheet editor does not. (It's not limited to \"Select All\", either; if you box-select keyframes from multiple channels, the same difference is observed.)\n\nSo rather than making \"Clean Keyframes\" and \"Clean Channels\" independent of channel selection, the real fix might be to automatically select the relevant channels in the Dope Sheet editor too.\n\nApart from this, it might make sense to move the \"Clean Channels\" operator to the \"Channel\" menu (and the \"X\" button of the channel region) and make it depend on channel selection *only* - that is, clean all keyframes of the selected channels, even if there are no keyframes selected. That way, there'd be some nice symmetry between the \"Channel\" and \"Key\" menus, both having their own \"Delete\" and \"Clean\" operators.", "Force keyframe with “insert only needed” option on\nBroken: 2.80\n\nI suppose this was intended not a bug, but from an animator perspective it seems like a bug.\n\nWhy when \"insert only needed\" options is ON I can't insert keyframes manually? I only get \"Keying set failed to insert any keyframes\" info\n\nInserting manually only works if you do it outside the current range of animation, but then it removes the key frames next to it. I know there were flat, but it's frustrating when the software deletes keys from my animation. Is it possible to disable this option?\n\nI usually put keys on all available attributes so I don't accidentally change the pose, but on the in-betweens I like to have only keys on changed attributes\n\nIs there a possibility to forcefully insert a keyframe? or just set Autokey to insert only modified attributes? \n\nI somewhat got the functionality I wanted using KeyinSets with overriding the ION option but that worked only when Target ID-Block was set for a specific object. But creating & switching specific keyingsets for all animated object is way to troublesome while animating\n\nCheck the \"insert only needed\" in Preferences > Animation.\nManually add 2 keys for an object e.g. frame 0 & 10. Then try the same keyframe on frame 5. -> Keying set failed to insert any keyframes\" \nAlso later try setting keyframe on frame e.g 15 - > Keyframe on 10 disappears ", "VSE: Frame Overlay incorrectly applies Transform to reference frame, ignores keyframes\nOperating system: Ubuntu 20.04.2\nGraphics card: AMD® Verde\n\nBroken: 2.93.3\nWorked: don't know\n\nWhile Frame Overlay is active and set to \"Reference\" or \"Rectange\", the video sequencer applies transformations to the reference frame even when that frame has a different transformation keyframed. The expected behaviour is that the reference frame looks exactly as it does when that particular frame is active.\n\n - Open attached file [vseoverlaytransform.blend](vseoverlaytransform.blend)\n - Note that Frame Overlay is active and Overlay Type set to \"Reference\"\n - Alter the Rotation parametre of the text strip\n - Note that the displayed frame transforms as you change the value\n - Disable Frame Overlay and jump to the first frame\n - Note that the transformation parametre has a keyframe at 0 deg, but the displayed text is still rotated\n - Press Ctrl-R (Refresh All) and note that the text jumps back into its unrotated state\n\n", "Grease Pencil datablock property 'use_onion_skinning' doesn't work\nOperating system:\nGraphics card:\n\nBroken: 3.4\nWorked: \n\nThe datablock-level property \"use_onion_skinning\" on the Grease Pencil datablock doesn't seem to do anything. Toggling the property with Python doesn't affect the visibility of onion skinning.\nWorking as expected, this property will be useful when drawing among multiple Grease Pencil objects.\n\nOpen attached blend, toggle use_onion_skinning in the Python console: bpy.context.object.data.use_onion_skinning = False [onion_bug.blend](onion_bug.blend) " ]

[ "Sequencer cut loses animation data for the right strip\nOperating system: Ubuntu 18.04.1 LTS\n\nBroken: Latest master branch commit : 95736683a96d33a8a7220788502250fa9e109132\n\nWhen cutting a strip using the VSE (this affects all types of strips), the animation data is duplicated in the resulting right-hand strip, but is not copied to the left-hand strip.\n\nOpen the VSE, add a sound strip. Animate the \"volume\" property using two keyframes.\nOpen the Graph editor, visualize the \"Volume\" F-curve.\nSoft-cut the sound strip, and examine the F-curves for the two resulting strips :\n - The left strip has no animation data\n - The right strip has TWO identical \"Volume\" F-curves\n\nPossibly linked to the following code tag : \nblenkernel/intern/sequencer.c:5448 (95736683a96d33a8a7220788502250fa9e109132)\n\n\n```\nstatic Sequence *seq_dupli(const Scene *scene_src, Scene *scene_dst, Sequence *seq, int dupe_flag, const int flag)\n{\n Sequence *seqn = MEM_dupallocN(seq);\n\n seq->tmp = seqn;\n seqn->strip = MEM_dupallocN(seq->strip);\n\n seqn->stereo3d_format = MEM_dupallocN(seq->stereo3d_format);\n\n /* XXX: add F-Curve duplication stuff? */\n```\n" ]

[ "Scene Proxies in the Video Sequence Editor\nWindows 7 Ultimate, 64-bit, 32GB, 5960x, Nvidia Quadro FX 1800 (Primary) & GeForce 9800 GTX+ (Secondary)\n\nBroken: (2.79a) Official builds\nWorked: (2.79) Official builds\n\n\nTo cut a long story short @ideasman42 disabled Scene proxies in the Video Sequence Editor because:\n\n> In #54048#485268, @ideasman42 wrote:\n> Looked into this and for now **building proxies doesn't support anything besides movie, so disabling support for this.**\n> \n> 6535f668b4\n\n\n*This shocked me, have I been using Blender wrong?* Because I've been happily doing this for months.\n\nI don't quite understand the rationale behind the removal of is.\n\nThe main problem for me is that I have projects (made in 2.79 and earlier) that rely on scene proxies and when opening them up in 2.79a viewing or creating them doesn't work.\n\nNow there *are* issues with Scene Proxies most notably the aforementioned (#54048) one and it can be really bad:\n\n[0001-2565.mkv](0001-2565.mkv)\nand\n**Other proxy issues**\n - Skipping frames whilst rendering.\n - Properties side panel scrolls up after changing proxy location in the File Explorer.\n - Overwrite don't have the same behaviour as Overwrite does in the render setting (in the properties editor)\n - and [inconsistent functionality ](F2418236).\n\nBut I've always treated this as an incomplete feature, (same way I treat NetRender, it's somewhat stable but is inconsistent. e.g. blender/blender-addons#52502) throwing in a bug report due to just crashing (#53792) and have been fine.\n\nBut now with the update, the [Proxy/Timecode Panel ](proxy.html) is still there and does nothing. and as I said in my query to @ideasman42's decision to disable this:\n\n> In #54048#485618, @ChristopherAnderssarian wrote:\n> So, @ideasman42 does this invalidate my bug report? #53792\n> Also, is it a good idea to disable this considering the Proxy/Timecode Panel option still there (or are you still working on this)?\n> \n> With no information or feedback in the Blender Manual or when trying to create proxies (nothing happens), `you are going to get users confused on a essential feature that worked` (works fine in cycles for me (not the file names the crashing)) in 2.79 `and now doesn't with no apparent reason why. `\n\n___\n\n> In 6535f668b4, @ideasman42 wrote:\n>>...generating proxies currently only works for movies...\n\n*No... they don't. They worked for Scenes before. (and they work for images for that matter)*\n>>...cancel until other types of sequence strips are supported...\n\n*What do you mean by this? That it's officially 'supported', documented?* \n___\n\nNow that I've been trying to research around a bit, is this an incomplete feature or has it slowly gotten broken in time?\nThere's #43857 which uses a scene proxy. So there must be other uses who uses this right? Or was this just an example?\nI would love to use this with Eevee; having the proxies rendered in no time and my GPU not getting taxed.\n___\n\nWhat I think to be good next steps:\n\n - Having the functionality back as it was before.\n - An open task to deal with the *Other proxy issues.*\n___\n\nZipped folder with a working Blender file and proxy:\nTested in Ubuntu VM both 2.79 and 2.79a with reproducible behaviour.^\nTested on a separate laptop with both 2.79 and 2.79a with reproducible behaviour.^\n(Note: In my Ubuntu VM I had to toggle Textured Solid button in the Scene Preview/Render Panel to get the proxy showing in 2.79.)\n(^ Reproducible behaviour being: fully working in 2.79 and not working at all in 2.79a)\n[Blender_VSE_Testing_Scene_Proxy.zip](Blender_VSE_Testing_Scene_Proxy.zip)\n\n\nI'm sure this was just a misunderstanding.\nYours,\nA passionate Blender user", "Rendering in cycles causes objects with materials to go black and shiny when using the GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 7900 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\nWorked: N/a\n\nWhen my render engine is set to cycles and device is set to GPU Computer (with HIP and my 7900 XT selected), if I look at an object with a material applied in either viewport shading or as a rendered image the model will appear black and shiny or occasionally will just show as a flat blue colour. \n\nThis issue does not occur when using the CPU as the device instead and also did not begin to occur until a few days ago (prior to which it was working fine).\n\nI've checked the same blender file on a laptop with a 3060 GPU which worked correctly so I don't think the file itself is corrupted.\n\nI have also checked multiple blend files, some of which work fine, others do not, one file has some things working and other things broken (I will attach it to this bug report)\n\n\n1. Load the attached blend file \"ArkenV1R1_Interior.blend\".\n2. Go to edit > preferences > system > cycles render devices, set it to HIP with RX 7900 XT selected.\n3. Under scene settings, change the render engine to cycles and device to GPU compute.\n4. Switch to Viewport shading.\n5. Observe that the bullets and floor panel are shown as black and shiny while the table renders correctly (grey and blue).\n6. Press F12 and observe that the rendered image also shows the bullets and floor panel as black and shiny.\n\n\n**Additional**\nIncorrectRender.png was rendered using GPU\nCorrectRender.png was rendered using CPU\n\nI will be happy to provide anything else needed to figure this out, thanks!\n\n", "Cyclic Strip Time not work with non-zero Action Clip Start Frame\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.3\nWorked: ???\n\nCyclic Strip Time not work with Action Clip\n\nI attached .blend to show this bug.\nThe track called \"Ok\" works with the \"Cyclic Strip Time\" check mark correctly.\nThe track called \"Bug\" works with the \"Cyclic Strip Time\" check mark incorrectly.\n\nIn the track \"Ok\", there are two keys, at 0 and 10 frames.\nIn the track \"Bug\", the same two keys, but for 43 and 53 frames. In the Action Clip, I set the values Frame Start =43 and End = 53.\nI expect that the \"Bug\" track will perform the same actions as the \"Ok\" track, but this does not happen.\nI think this is a mistake.\n[BugCST.blend](BugCST.blend)\n", "Add sticky keys support for accessibility\nOperating system: Windows 10\nGraphics card: Geforce GTX-970m\n\nblender-2.80.0-git.1fa527bfa3a-windows64\n\n\nSticky keys not working properly.\nSfZ7Ua-ReuQ", "Self-referencing driver works in viewport, but not in render.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional) 2.79b\n\nRotation property of object is updated in viewport, but not in render.\nIf run same script in 2.79 - all works fine both in viewport and render.\n\n```\ndef rotator():\n var1=bpy.data.objects[\"Suzanne\"].rotation_euler.z\n var3=bpy.data.scenes[\"Scene\"].render.fps\n\n new_value=var1+math.radians(var3)\n\n return new_value\n```\n\n\n[Script_bug_2.8.2.blend](Script_bug_2.8.2.blend)\n\n- run the file Script_bug_2.8.2 ('Run script', 'Update Dependecies')\n- play in the viewport - the animation works correctly\n- render (Ctrl + F12) - the animation does not work;\n\nViewport:\n[bug_video_render0001-0050.mkv](bug_video_render0001-0050.mkv)\n\nRender:\n[bug_video_render_20001-0050.mkv](bug_video_render_20001-0050.mkv)\n\n2.79 file:\n[Script_work_2.79.blend](Script_work_2.79.blend)\n\n", "OPTIX_ERROR_INTERNAL_ERROR when rendering using Cycles with OptiX\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nAlso tested on:\n- 3.0.0 — got same error\n- 2.93.18 — same error but different line of code\n\nOPTIX_ERROR_INTERNAL_ERROR when rendering with OptiX.\n\nError on 3.6.2\n\n\nError on 2.93.18\n\n\nThe issue is **not** presented when I'm using _NVIDIA Studio Driver 472.84_. However I've tried several newer versions and got this error for all of them.\n\n\n1. Open blender (just the default cube)\n2. Edit -> Preferences -> System -> OptiX -> NVIDIA GeForce GTX 1060 6GB\n3. Render Engine: Cycles\n4. Device: GPU Compute\n5. Shading (Z) -> Rendered or Render Image (F12)\n\n", "Blender 2.91 alpha - Debug menu, instant crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90.1\n\nShader compilation is causing an error when the debug menu is invoked on a blank scene or working scene.\n\nOpen the .blend attached file, press F3>search: Debug. Type 22 (eevee GPU speed benchmarking verbose),\nBlender will crash immediately. The same is true on a blank new scene in the general application template.\n\nFile to test: \n44cb6eb461af31ad1209dedb738d76c0.blend\n\n", "Cycles: Bump node doesn't generate anything in certain conditions\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.3.0\nWorked: all versions from 2.79 to 3.4.0 alpha are affected, there is no working build\n\nI'm trying to generate a normal map using Bump node and color output of the env map as height map, it doesn't work on Cycles while it works on Eevee. Seems like the \"reflection\" output of Texture coordinate node is broken, but it works fine when I'm using another outputs though\n\nOpen the project, then click on viewport Rendered mode button - it'll start Cycles which for some reason can't generate bump map, then switch to Material preview mode - it'll start eevee which works as expected\n[bug_report.blend](bug_report.blend)\n\nEdit: typos and bad english grammar fixed, I believe", "Fake Dependency Cycle: 'Disable in Viewport' depends on 'Disable in Renders'\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.2.2\n\nDriving hide_render from hide_viewport causes a dependency cycle\nwhile the error occurs on all objects, the driver does seem to work on some objects, but not others. In the default scene for example, the driver works with the camera, but not the cube or the light\n\n- in the outliner, edit the filter to display the `Disable in Viewport` option.\n- Right click the `Disable in Viewports` icon on any given object\n- Copy as New Driver\n- Right click the `Disable in Render` icon of the same object\n- Paste Driver\n[render visibility driver issue.blend](render_visibility_driver_issue.blend)\n\n", "Blender 3.2.1 / 3.4 - Cycles - Persistant Data and Motion Blur artifacts on GPU\nOperating system: Windows 10, Ubuntu 21.04\nGraphics card: GTX 1080, RTX 3080\n\nBroken: 3.2.1, b5e92c3dfe\nWorked: 2.79\n\nPersistant data is bugs out during renders sometimes.\n\n1. Open attached blend file in Blender 3.2.1\n2. Press f12\n3. Press right on the keyboard (frame 771)\n4. Press f12\n5. Press right on the keyboard (frame 772)\n6. Press f12\n7. Notice how its not as expected.\n8. Press f12 without framing forward\n9. Notice how it is fine\n\ngood\n\nbad\n\n\nThis means when rendering animations, it can produce frames which bad, which then require more re-renders.\n\nWindows and Linux have both been tested and results are the same.\n\nTested CUDA, Optix and both have issues. CPU renders fine. \n\nDisabling Persistant Data renders fine.\n[bug.blend](bug.blend)\n\nNOTE: We had #95475, #96822 already for Persistent Data and Motion Blur issues (these should be fixed), I can repro this case though.\n\nEDIT:\nAs another task #100729 has been merged into this file, there is another test file [BUG.blend](BUG.blend)\n", "Shadow buffers\nIn order to reduce Shader register pressure during shading phase, we need to transfer the shadow sampling of opaque surfaces to a fullscreen pass.\nWe would store 1 or 2 bits per lights (limiting number of shadowed lights per pixels to 32 or 16) and use noise to dither the shadow shape.\nThe noise would disappear with accumulation.\nThis idea was explored in this presentation [link](view).\nThe issue is that this technique will not work for alpha-blended surfaces that will still need the standard shadow code.\nContact shadow and cascade shadows cost could be reduced. This could be the opportunity to remove support for contact shadows for alpha blend surfaces.\nThis also will permit to have raytraced shadows in the future.\n\nEstimate : 2 weeks\n", "Cycles XML, light node does not react to transform\nCycles XML, light node does not react to transform (it was ok before migration to graph/node* node parsing). Let me know if this is a bug or it is by design.\n\nSee attached sample XML.\n\n```\n<cycles>\n<transform translate=\"0 0 -4\"><camera type=\"perspective\" /></transform>\n<integrator max_volume_bounce=\"0\" method=\"branched_path\" sample_all_lights_direct=\"true\" sample_all_lights_indirect=\"true\"/>\n<background heterogeneous_volume=\"false\" volume_sampling_method=\"equiangular\" ><scatter_volume name=\"scatter\" color=\"0.8, 0.8, 0.8\" density=\"0.3\" /><connect from=\"scatter volume\" to=\"output volume\" /></background>\n<shader name=\"point_shader\"><emission name=\"emission\" color=\"0.8 0.1 0.1\" strength=\"100\" /><connect from=\"emission emission\" to=\"output surface\" /></shader>\n\n<state shader=\"point_shader\"><light type=\"point\" co=\"0 0 0\" size=\"0.01\" /></state>\n\n<!-- Light does not react to transform node -->\n<transform translate=\"0 0.5 0.0\">\n\t<state shader=\"point_shader\"><light type=\"point\" co=\"0 0 0\" size=\"0.01\" /></state>\n</transform>\n\n</cycles>\n```", "Cycles and Eevee Significant Difference in Texture Output\nOperating system: Ubuntu 20.04\nGraphics card: GTX 1060 3Gb\n\nBroken: 2.80 and on (3.0.0 is still affected)\nWorked: 2.79\n\nFrom Blender 2.80, Cycles produces incorrect output for some procedural textures, while Eevee produces correct ones.\n{[F12696991](Cycles.png)}\n\nTest file (I assume there might be other files affected too). [Carbon_90.blend](Carbon_90.blend)", "Image Editor Blank After Switching Slots, Even If There Is A Render In That Slot\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: (2.80, 79f67acccb36, blender2.7, 2019-03-24)\n\nSwitching the slots in the image editor for the render result (hotkey \"j\") can show a blank image, even if there is an image available in that slot.\nSelecting the render layer in the dropdown menu brings it back.\nThis is irritating, especially since the image is shown right after rendering.\nThis only happens if the compositor is disabled.\n\n- Load [bug.blend](bug.blend).\n- Press F12 to render. The image editor comes up.\n- Press \"j\" to switch to switch the slot.\n- Press F12 to render again.\n- Press \"j\" to switch back to the previous slot. It now appears blank.", "Rendering object in Cycles X preview hard crashes whole system\nOperating system: Windows 10 x64\nGraphics card: nVidia RTX 8000\n\nBroken: blender-3.5.0-alpha+universal-scene-description.1f9e90bb1cf3-windows.amd64-release\n\nRendering of scene in Cycles preview hard crashes whole system. System screen goes to black and the fans go to max.\n\nLoad blend file at link: brutes_set1C_trimmed.blend?dl=0\n\nSet screen to Render preview and navigate around.\n\n" ]

[ "Quick Effects: Smoke and Fluid simulation does not work \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nSmoke and fire simulation just does not work in my specific hardware as per introduction.html#bpy-ops-object-quick \n\n[Bug repport.mp4](Bug_repport.mp4)\n\nDefault Cube, In object menu, hit Q: quick effects, select either of fluid and smoke. The external cube is made, but no effect is seen in animation.\n\nFurther, add Smoke, add fur, add smoke: it throws this in console (which I guess is expected) as well in a banner in blender (which can be shown in a better way):\n```\nWarning: Only one modifier of this type is allowed\nTraceback (most recent call last):\n File \"/Users/me/blender-build/build/bin/Debug/Blender.app/Contents/Resources/2.83/scripts/startup/bl_operators/object_quick_effects.py\", line 480, in execute\n obj.modifiers[-1].fluid_type = 'FLOW'\nAttributeError: 'ParticleSystemModifier' object has no attribute 'fluid_type'\n\nlocation: <unknown location>:-1\n```\n", "EMERGENCY!! \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 25.20.100.6472\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\n[THE QUCIK SMOKE EFFECT IS NOT WORKING. I CAN ADD IT BUT EVERY TIME I HIT THE PLAY BUTTON THE SMOKE IS NOT SHOWING\nPLEASE HELP ME ASAP]\n\n\n", "The smoke effect doesn 't work on the new version\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13543 Core Profile Context 25.20.15002.58\n\nBroken: version: 2.82 (sub 7)\nWorked: (yes)\n\nOn version 2.82, smoke and fire effects do not work . Checked on the previous version 2.8 everything worked.\n\nWhen you try to create a quick effect and then play it back, nothing happens.\n[Smoke_.blend](Smoke_.blend)\n", "F3: Quick Smoke Not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro M1200/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.23\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\n\n\nI did a tutorial from the following link:-\n\nwatch?v=TPrnSACiTJ4\n\nat time 12:55 to 13:51 of the video. It was suppose to generate smoke on the object, but it didn't. I repeat with a box and use the quick smoke, and, again it did not happen.\n\nI used another computer with the same version of software, again the smoke did not appear. Can you assist to look into this?\n\nThank you so much for your help,\n\n\nGuan\n\n\n", "can't use smoke effect\nOperating system: windows 10 home \nGraphics card: AMD Radeon R5 M330\n\nBroken: 2.82a doesn't work properly\nWorked: 2.79a work properly\n\nI can't use quick smoke effect on my pc, I didn't understand why it happens.\nexact steps I attached in video.\nplease, can you solve this problem for me?\nIs it because of graphic card then give me proper solution.\n\nquick effect of smoke is not working as usual. (video attached)[FormatFactory Screen Record20200328_172605.mp4](FormatFactory_Screen_Record20200328_172605.mp4)", "Quick Effects doesnt show in viewport \nIntel Core i3-2100 CPU @3.10GHz, 3100Mhz ,2Core(s)\nRAM:4GB\n\nOperating system: Windows 7 Ultimate 64bit\nGraphics card: Nvidia GT710\n\nBlender 2.82a\n\n**Quick Effects Wont Work**\n1)Fire & Smoke not showing in Render or Viewport\n2)also Quick Liquid be not working if i applied effect it doesn't show anything", "quick smoke not working\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.39\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\n[quick smoke effect does not do anything]\n\n[reset to factory defaults, tried again, same thing - nothing. tried downloading a fresh portable copy of blender 5 minutes ago, same thing, no smoke]\n\n", "When running a quicksmoke animation in the Layout window nothing happens\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 19.20 26.20.14003.4003\n\nBroken: version: 2.82 (sub 7)\nWorked: version: 2.81a\n\nWhen running a quicksmoke animation in the Layout window nothing happens\n\nStart blender, add quicksmoke to cube, press space to start simulation\n\nI have been able to reproduce this on two systems including a laptop that uses CPU rendering, it does not seem to be a hardware or driver issue. I compared the exact same steps in 2.81a and 2.82a, see attached gifs. Both clean installations\n\n\n\n" ]