Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "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", " Annotations are blended incorrectly (looks like added?) on viewport backgrounds in viewport renders\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER\n\nBroken: version: 3.0.0\n\nBlender renders colorful annotations as white while using the viewport render function, when the viewport background is set to be completely white.\n\n- Draw an annotation (e.g. blue)\n- Set the viewport background (via Viewport Shading) to \"Viewport\" and set it to be red (could be world as well if you like).\n- 3D Viewport > View > Viewport Render Image.\n- notice the blue annotation being added to red background (resulting in pink)\n- if you do this with a white background, you will think the annotations are gone (all strokes add to white... giving.... white :)\n\n[#93748.blend](T93748.blend)\n\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", "Theme: Inconsistent solid color for the background in the 3D viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.90 (sub 0)\nWorked: 2.79b\n\nThe color of the 3D viewport background set to theme seems to not match with the color set in the theme setting.\n\nCheck the examples below with the color #36393F\n\n2.79b: color is exactly like in the theme setting.\n\n\n2.80 to 2.82: color looks good but seems grainy.\n\n\n2.83 to 2.90: color is slightly changed, when sampled not the expected theme color.\n\n\n- Open blender\n- In the initial layout change the Outliner editor to Preferences\n- Go to background color option\n- Use the colorpicker to get a sample of the background color\nThe color shouldn't change, but it does", "Inconsistencies between 3D Viewport and Viewport Render Image using the GPU Shader Module\nOperating system: Ubuntu 18.04, Windows 10\nGraphics card: GeForce GTX Titan X, GeForce GTX 1080 Ti\n\nBroken: \n2.83.0\n2.90.0 Alpha\nWorked: Never\n\nRendering the `3D Viewport` with `3D Viewport/View/View Render Image` (i.e. OpenGL rendering) does not render elements drawn with the [GPU Shader module ](gpu.html).\n\nThe problem is illustrated in the following example, which shows the `3D Viewport` (left) and the rendered result of `View/View Render Image` (right).\nThe points drawn with the GPU shader module are neglected during OpenGL rendering.\n\n\nExcecute the [3D Lines with Single Color ]] example of the [[ https:*docs.blender.org/api/current/gpu.html | GPU shader module documentation ](https:*docs.blender.org/api/current/gpu.html#d-lines-with-single-color).\nThen, render the results with`View/View Render Image` as shown in the image below.\n\n\nThe lines visible in the 3D Viewport (left) are missing in the rendered result (right).\n ", "Viewer Node does not initialize from within Compositor node group\nOperating system: Windows 10 x64\nGraphics card: RTX 8000\n\nBroken: 10/26/2022 build\n\n\nViewer node does not work if used for the very first time inside a compositor node group. Once the user goes back to the top level composite and connects a Viewer Node, it works, and then updates normally when going back into node groups.\n\n**Reproduce from a file**\n\n[viewerNodeNotWorkingInNodeGroup.blend](viewerNodeNotWorkingInNodeGroup.blend)\n\n- Add a viewer node for the Image node output.\n- Notice how the backdrop and the Viewer image doesn't get initialize with the viewer content.\n- Go back to the top level node tree and add a viewer node.\n- Notice how the viewer is initialized.\n- Go back inside the node group.\n- Notice how it updates correctly, so it is only for the first time.\n\n**Reproduce from scratch**\n - New General file\n - Hit 0 and F12 to render one frame of the default cube\n - Change to Composite tab\n - Change top view to Image Editor\n - Pick dropdown and select Viewer Node\n - In compositor panel Shift-A to add a greenscreen image\n - Shift-A to add a Keyer node\n - PIck a green color to key it\n - Add Scale node, set to Fit and Render Size\n - Connect Keyer Image output to Scale node\n - Add Alpha Over node. Connect Render Layers to Alpha Over Background input and Scale node to Foreground input\n - Select Image, Keying, Scale, and Alpha Over nodes. \n - Ctrl-G to Group\n - Make sure Node Wrangler is enabled.\n - Inside the group. select the Image node.\n - Ctrl-Shift-LMB to add a Viewer and connect it\n - Note that Viewer Node display in Image Editor does not update.\n - Press Tab to go up one level.\n - Highlight Render Layers and press Ctrl-Shift-LMB. Now render layer is shown in Viewer Node.\n - Highlight Node Group and press Tab to go in.\n - Now image viewer is working and active.\n\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 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)", "Cycles fully transparent shader is brighter when a Clear Coat shader is behind it\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.3.0 Alpha\nWorked: Never Worked\n\nWhen doing Decals, we often use alpha channel to define transparent area. However, I found when the Object's base color is above hsl(h,s,0.01), who's under the Decal, then the decal's transparent area will affect the underneath object's shading.\nMy test configuration is that 2048 viewport samples alongwith light bounces param all been set to 64.\nThe BUG is easier to notice when the background object is light grey, and the light is quite dimmed(or just turn down the exposure in colormangement to observe.)\n\n\n\n\n\nPlease open the attached Blend file to test.\n[Transparent shading BUG.blend](Transparent_shading_BUG.blend)\n\n", "Cycles shaders show up in EEVEE list (Properties > Material tab > Surface panel)\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.80 (sub 75)\nAlso confirmed broken in 2.80 release candidates 2 and 3\nWorked: ----\n\nSome shaders not yet available in EEVEE, such as the Toon shader, are included in the list of shaders in the materials tab of the properties window even when EEVEE is selected as the render engine. When such shaders are selected, adjusting most of their parameters has no effect on the viewport/render. Currently, the only way to know which shaders are supported is either by trial and error or by using the node editor.\n\n1. With a fresh blender scene, check that EEVEE is the selected render engine, and go to materials tab in the properties window\n2. You should already have a material if it's the default cube scene. In the surface panel, click on the shader selector (set to principled BSDF by default)\n3. The menu that shows up includes Toon shader among other unsupported ones.\n\n[Based on the default startup]\n\n**Screenshot**\n\n\n", "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", "The alpha channel set in Viewport Display settings for an object's material appears as if it's set to 0 when a background image is behind it\nOperating system: Linux x64 (Debian-based)\nGraphics card: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a)\nNvidia drivers, version: 440.31\nKernel: 4.19.0-6-amd64\n\nBroken: v2.81a and v2.80, downloaded from blender.org as a tar.gz\n\nWhen you change the Viewport Display color for an object to have an alpha channel < 1.0 but > 0.0, then manipulate the scene so that there's a reference or background image behind that geometry, the overlapping area will appear completely transparent (alpha 0.0).\n\n\n1. New scene\n2. Add a cube: Shift a -> Mesh -> Cube\n3. Add an image: Shift a -> Image -> Reference (or background)\n4. Select an image\n5. Position the image behind the cube in the viewport. Select the cube.\n6. In the properties panel, select Material Properties\n7. In the Material Properties panel, select Viewport Display\n8. Change the Color to have an alpha between 0.0 and 1.0, exclusive\n\n**Observed behavior**\nLike the screenshots, the overlapping area allows the background image to completely shine through.\n\nQQxLCpv\n\n**Expected behavior**\nThe object will become uniformly translucent and allow the background/reference image to be partially visible, not make the image fully transparent in the overlap.\n\n", "Data Transfer modifier works only for Byte Color & Face Corner color attributes\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 472.12\n\nBroken: version: 3.2.0\n\nIf a target color attribute Domain is *Vertex* or it's Data Type is *Color*, the data are not transferred.\n\n[data-transfer-color-attr-bug.blend](data-transfer-color-attr-bug.blend)\nYou can see in the attached .blend that the Data Transfer modifier is set correctly, but the Col attribute isn't updated.\nAfter doing Convert Attribute -> Domain: *Face Corner*, Data Type: *Byte Color*, it starts to work correctly.\n\n\n", "Driver using Depsgraph to retrieve current View Layer name fails when rendering in EEVEE\nBroken: version: 3.0.1\n\nI tried to make a driver reference the current View Layer as [Animation: Passing Dependency Graph to Drivers](rB686ab4c9401a90b22fb17e46c992eb513fe4f693) seems to enable. However, it only seems to work if I click the render button on the Render Layers node in the compositor. Rendering with F12 results in the expression depsgraph.view_layer.name evaluating to whatever the first View Layer is named.\n\n**Video Demonstration**\n[Viewlayer Depsgraph Problem.mp4](Viewlayer_Depsgraph_Problem.mp4)\n\nAfter you allow execution of scripts, you can test rendering with F12 versus using the buttons render buttons on the Compositor Render Layers nodes.\n[DG_VL_Render.blend](DG_VL_Render.blend)\n", "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" ]

[ "Regression: Shader To RGB not displaying textures\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.0 Beta\nWorked: 3.1.2\n\nCaused by 80859a6cb2\n\nShader to RGB seems to be broken because it's not passing through the texture information. \n\nCreate a texture, add an image node plugin into a Diffuse BSDF and then to a Shader to RGB and then, the color output to the surface Material Output. \n\nFind attached a blender file and screenshot of whats on version 3.1.2 working and not on 3.2\n\n\n\n\n[Shader_to_Rgb_BUG_01.blend](Shader_to_Rgb_BUG_01.blend)" ]

[ "gpu.states.line_width_set doesn't work (on Mac Air)\nOperating system:\nGraphics card:\n(just copy pasted specs here)\n Model Name:\tMacBook Air\n Model Identifier:\tMacBookAir7,2\n Processor Name:\tDual-Core Intel Core i5\n Processor Speed:\t1,8 GHz\n Number of Processors:\t1\n Total Number of Cores:\t2\n L2 Cache (per Core):\t256 KB\n L3 Cache:\t3 MB\n Hyper-Threading Technology:\tEnabled\n Memory:\t8 GB\nIntel HD Graphics 6000:\n\n Chipset Model:\tIntel HD Graphics 6000\n Type:\tGPU\n Bus:\tBuilt-In\n VRAM (Dynamic, Max):\t1536 MB\n Vendor:\tIntel\n Device ID:\t0x1626\n Revision ID:\t0x0009\n Metal Family:\tSupported, Metal GPUFamily macOS 1\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nBlender 3.6\n??\nOn this specific Macbook, gpu.states.line_width_set simply does nothing - Just tested also on WIndows and there it works.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nJust try the 'Operator Modal Draw' Template in Python templates in Blender text editor - the function is used there so it's very fast to check.\n\nAnd yes, I know this is probably outdated hardware, but didn't want to not report bug if I already found one ;)\n\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)", "OptiX Denoiser crashes OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\nCPU: AMD Ryzen 7 1700\nRAM: 32 GB\n\nBroken: version: 2.90.0 Alpha\nWorked: unknown\n\nWhen the Viewport OptiX Denoiser is activated it crashes with the following error *\"OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources(denoiser, rect_size.x, rect_size.y, &sizes) (device_optix.cpp:850)\"*\n\nBased in the Startup File, (Reseted to Factory Settings and userpref.blend deleted):\n1. In Preference->System set Cycles Render Devices to \"CUDA\"\n2. Set render engine to \"Cycles\"\n3. Set device to \"GPU Compute\"\n4. Set Viewport Denoiser to \"Fastest (Optix)\" or \"OptiX\"\n5. Set Viewport Shading to \"Rendered\"\nERROR *(View screenshot)*\n\nOnce the error has ocurred I can't render with CUDA, even on a new file. To be able to render with CUDA I must close Blender and open it again. *View System Console Output*\n\n**Additional Info**\n\n- The error doesn't happen if the Cycles Render Devices is set to \"OptiX\"\n- This error doesn't happen in my laptop (i7 7700HQ, GTX 1050, 16GB RAM)\n- In a more complex scene blender tries to load the render kernels for a long time before throwing the error\n\n\n[system console Output.txt](system_console_Output.txt)\n[system-info.txt](system-info.txt)\n\n\n\n", "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?", "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", "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.", "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 !", "CUDA problem Error: Invalid value in cuMemcpy2DUnaligned_v2(&param)\ndoes anybody know what this error mean (blender 3.5, 3.6, 4.0 win 11):\n\n*Error:Report:\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\n\n\nWe tried two rtx 4070ti video cards and this error came up when we were about to render. If I disable one of the two, the render runs fine, but if I enable both, the render freezes. I see that it starts using both, but it still gives an error.\n\nThanks\n\n", "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", "Blender segfault if Bake Line Art\nOperating system: Debian Linux Stable 11\nGraphics card: Intel internal UHD Graphics 630 (driver: i915)\n\nBroken: 3.2.2 - 3.6.1 official releases\n\nBlender segfault if Bake Line Art.\n\nConsole:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault\n```\n\nFile /tmp/blender.crash.txt:\n```\n# Blender 3.2.2, Commit date: 2022-08-02 18:15, Hash bcfdb14560e7\nbpy.ops.object.delete(use_global=False, confirm=False) # Operator\nDeleted 1 object(s) # Info\nbpy.ops.object.gpencil_add(align='WORLD', location=(0, 0, 0), scale=(1, 1, 1), type='MONKEY') # Operator\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.gpencil_modifier_add(type='GP_LINEART') # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xc1619d0]\n./blender() [0x11da18d]\n/lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f97f7664d60]\n./blender(MEM_lockfree_allocN_len+0x7) [0xc16e1e7]\n./blender(MEM_lockfree_dupallocN+0x14) [0xc16e624]\n./blender(BKE_gpencil_stroke_duplicate+0x1a) [0x11f926a]\n./blender(BKE_gpencil_frame_copy_strokes+0x42) [0x11f94c2]\n./blender() [0x1207d97]\n./blender(BKE_gpencil_prepare_eval_data+0x1b7) [0x1208b07]\n./blender(BKE_object_handle_data_update+0x2fe) [0x12af9ae]\n./blender(BKE_object_eval_uber_data+0x2f) [0x12afc7f]\n./blender() [0x1913f22]\n./blender() [0x19140f2]\n./blender() [0xc16574d]\n./blender() [0x1796a35]\n./blender() [0x1796ceb]\n./blender() [0x1783d27]\n./blender() [0x1790720]\n./blender() [0x179275c]\n./blender() [0x1792959]\n/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f97f807aea7]\n/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f97f7727a2f]\n\n# Python backtrace\n```\n\n1. Open Blender\n2. Click to default box and delete it (press del)\n3. Press Shift+A\n4. Select \"Grease Pencil\" - \"Monkey\"\n5. At right area select \"Modifier Properties\"\n6. Click \"Add Modifier\"\n7. Select \"Line Art\"\n8. At bottom of this area click \"Bake\" - \"Bake Line Art\"\n9. Segfault here\n\n", "Error de progama\nno me aparece el modo vèrtice\n\n", "LightGroups & big render resolution results in Hardware failure & macOS crash incl. reboot\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.15\n\n**Blender VersionS**\nBroken: version: 3.2.0 Alpha\nBroken: version: 3.2.0 Alpha\n\n\n(GPU only)\nI usually render with a resolution of 5120x2048 on 50% as check resolution. \nWhen I scale it up with the slider to 100% and render I get a stripe pattern as we seen in other bugreports related to M1 Mac's.\nThen when I try double the resolution on 50% I get the same.\n\nThe crash of macOS with a hardware failure and reboot happened when I tried my final resolution 10240x2048 on 100%. (blender calculated a sec. and when the render via GPU only started it hanged for two sec. and then completely crashed)\nTo be honest, a crash like this I never had with 3 imac's the last 6 years. Only with a hackintosh not related to blender...\n\nDespite the fact of the total crash, I decided not to try to reproduce the total crash,\nBUT...\nthe stripes I could with the resolution I used. \n- Open attached file\n- Render once in 50% from 5120x2048,\n- and then render on 100%, or try the higher resolution.\n\n(The scene was: just a plane, monkey and 3 lights, to check the lightgroups and compositing options (worked all fine, exept the render...))\n(see attached blendfile)\n\nSo just 3 pointlights, each into a one of the 3 lightgroups a plane, monkey...(something to get lit),\nresolution 5120x2048 on 50% and render. Then render on 100% and you should get stripes.\n\n`***When there, just delete the lightgroups under Scene -> View Layer Tab and the stripes are gone.***`\nOperating system: (INTEL) macOS-12.3.1-x86_64-i386-64bit 64 Bits \nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.15\n[untitled.blend](untitled.blend)\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", "Crash on purging orphans\nOperating system: Windows 8.1, Windows 10\nGraphics card: GTX 770, RTX 2060\n\nBroken: 3.3 LTS, 3.5\nWorked: unsure\n\nWhen browsing through material search list fast enough (with textures loaded or not [purple as shown in video]) and then deleting the object + purging orphans, blender crashes.\n\n- Open uploaded file\n- Scroll through materials from dropdown\n- Switch to object mode and delete object\n- In outliner, execute Purge operation from `Orphan Data` display mode\n[#103820.blend](T103820.blend)\n[sample.blend](sample.blend)\n[3.3.lts.mp4](3.3.lts.mp4)", "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" ]

[ "NVIDIA Quadro P4000 graphic card no longer accepted for CUDA rendering\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro P4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.93.0 Beta\n\nDESCRIPTION\nThe NVIDIA Quadro P4000 graphic card (with updated driver and even with the previous version) is no longer recognized in the system tab of the preferences window to render with CUDA enabled, whereas the 2.92 version of Blender works fine.\nSame problem for Blender 3.0\n\n\n", "the GPU is not showing up in my prefferences\nOperating system: window 10\nGraphics card: RTX 2080Ti\n\nBroken: 2.93.0 Beta 2021-05-18 09:58 Hash: aa06be9148a3 Branch:master\nWorked: 2.92.0 2021-02-24 16:25 Hash: 02948a2ca44 Branch:master\n\n2.93.0 beta in prefferences/ system / cycles render device: my Nvidia Geforce RTX 2080Ti and AMD Ryzen 9 3900X 12-core Processor does not show up. \nbut does in the stable version of 2.92.0\n\n", "Blender 2.93 and 3.0 both say they \" No Compatible GPU's found\" - 2.92 does show I have a GPU\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 466.47\n\nBroken: version: 2.93.0 Beta\n\nBlender does not see my GPU in 2.93 and 3.0 and 3.0 Cycles X build.\nWhen I check 2.92, it does show my GPU. Here is a screenshot of 2.93 and 2.92 preferences open to show the difference in GPU.\n\n\n\n" ]

[ "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "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)", "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", "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)", "Geometry Nodes: Simulation nodes cache assert\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\n\nSee attached stack trace file.\n\nDebug build.\n1. Geometry nodes:\n a. Add Simulation nodes.\n2. Quickly and randomly move time cursor on timeline by hands.\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)", "Linked group breaks Object Mapping in Texture Coordinates\nWindows 10\n\nBroken: 2.79b official release\n\nLinked group breaks Object Mapping in Texture Coordinates, when:\n- a texture (on a plane) uses another object (empty) as texture coordinates\n- all objects are in the same group\n\nFurther explanation in the blend file.\n\n1) Link the group \"object_mapping\" from the blend file\n2) move the group in any direction\nDespite the gradient texture on the plane using the empty's coordinates, this is completely ignored once linked as a group\n[object_mapping.blend](object_mapping.blend)", "Delete geometry node performance regression writing to multiple vertex groups in 3.1\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.1.0\nWorked: 3.0.1 and older\n\nCaused by f5e5a0987a\n\nUsing a combination of Delete Geometry node along side the Armature modifier makes the node run slower and slower the more vertex groups armature is using. The difference is an immense drop from 144fps back to 8fps using the same .blend file in 3.0.1 and 3.1\n\n[Delete Geometry + Armature 3.0.1.blend](Delete_Geometry___Armature_3.0.1.blend)\n\n[Delete Geometry + Armature 3.1.blend](Delete_Geometry___Armature_3.1.blend)\n\n**.blend file overview**\n\n\nI would argue that this bug is a high priority issue and makes a lot of the character animation workflows impossible to use in 3.1 .\nDelete Geometry Node has been a replacement for the Mask Modifier ever since Geometry Nodes was introduced, it is a crucial part of a lot workflows. \n\n\n\n**More information if needed :**\n\n- Order of the modifiers does not matter\n- Vertex groups on the mesh have to be used by the armature for it to take an affect, however the vertex group used to delete the geometry is not being used by the Armature\n- The issue seems to be that the Node is now checking every single vertex group instead of the single attribute given to it\n- The more vertex groups used by the armature the worse the performance\n\n\n\n", "Support warnings for field input nodes\nField input nodes evaluate in a context, but currently they give no warning if they do not support\na particular context. The initial goal is to add a warning like \"Input node does not support geometry type: Mesh\" on the spline parameter node in the following situation:\n\n{[F12738459](image.png) size=full}\n\n### Implementation\nA potential implementation isn't clear.\nIt seems there needs to be a way to keep track of which node (`bNode`, `NodeRef`, `DNode`, etc.) the field input node came from.\nThen the field evaluation system should have a way to collect errors and return them to the caller. Or maybe the caller can pass a\n\"logger\" class to the field evaluation system. That generalization could allow more specific breakdowns of node timing in the future.", "Geometry Nodes: Support materials in simulation state.\nCurrently, the simulation state in geometry nodes cannot contain materials. The main reason is that those separate IDs which are not serialized as part of simulation baking. Ideally, baking materials would just work, at least in the most common circumstances.\n\nWhile this task is about materials, the same thoughts also apply to other referenced IDs like object/collection instances.\n\nThere are two main possible solutions:\n1. Serialize materials as part of the simulation state.\n2. Only store a reference to the material in the simulation state.\n\n### 1. Serializing Materials\n\nSerializing materials has the benefit that it could just work. We'd have to store all the materials for every geometry in the simulation state in cached frame. Though, it's possible to deduplicate this to some degree of course. Serializing materials would also involve serializing the node graph and potentially even more referenced data like images. At some point we most likely want things to stay referenced, so the problem is just moved to a different place. Another problem is that the materials are essentially recreated on every frame. Blender does not really have the ability to work with materials that are not in `Main` currently.\n\n### 2. Storing References\n\nStoring a reference to the material mainly means storing a material name and an optional library name in the simulation state. Then, when loading the simulation state, the materials available in the .blend file are mapped to the loaded geometry. Conceptually, this is also very straight forward. Materials can still be edited like they always have been. A potential problem is that if materials are renamed or removed, they can not be linked correctly anymore. However, that is somewhat expected with linking already. While this approach is easy design wise, there are some technical difficulties: The main problem is that we only know which materials are used by the baked data, once the data is loaded. And, to make matters more difficult, we might only know which baked data to load once depsgraph evaluation has started. That can happen when e.g. the file path to the data on disk is dynamically build/choosen during evaluation (this is not supported right now, but likely will be at some point).\n\nThe problem with knowing which materials will be used by the geometry is that materials are part of the dependency graph. As such, all materials we wish to use for rendering have to be added to the dependency graph *before* evaluation starts. As of right now, it's not possible to lazily add materials to the depsgraph once it becomes known that it is required.\n\nThere are a couple different possible solutions with different trade-offs:\n* A. Always add all materials to the depsgraph. This would be a simple solution, but it's obviously not scalable. Even less so if we wish to use the same solution for other kinds of referenced data like objects.\n* B. Only support linking baked data with materials that are referenced by material slots on the object or original geometry. This means that if the simulation state happens to contain materials used by e.g. other imported objects, those will not be linked correctly.\n* C. Detect all materials \"reachable\" from an object and always add those to the depsgraph. This might have noticeable overhead when potentially large parts of `Main` have to by scanned by many objects. It also wouldn't work in all cases. For example, if the simulation has been baked, and then the .blend file changes in ways that the material is not reachable from the object anymore. Then the material would not be linked correctly.\n* D. Store a name-to-material mapping on the modifier. This mapping could be created/updated automatically when baking or at other points in time. Only materials in this mapping can be linked when loading simulation state. If the simulation state contains a material name that is not in the list, we could show a warning and automatically add it to the list with the press of a button in many cases. With this approach, the user also has the ability to replace a material after baking easily. The mapping could also have per simulation zone overrides for more control.\n\n-----\n\nCurrently, my preferred solution is referencing the materials by name in the simulation state and use option D to do the linking at evaluation time.\n\n", "Point Instance node doesn't instance meta objects.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\nBroken: version: 2.93.0 Alpha\n\nFor Geo Nodes, Point Instance node doesn't work (doesn't copy) meta objects (like metaball). \n\nI used a very basic setup. The original input and output nodes plus one point instance node. I selected the object to be a meatball. Nothing happens! I selected any other object (non-meta). The object is instanced. Geo nodes were added to the default cube. \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.*", "Geometry node - setting lacunarity to 0 crashes Blender (musgrave texture)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.2.2\n\nIn a fairly simple geonode tree, trying to set lacunarity to 0 will crash Blender instantly.\n\n- Use attached Blend.file\n- In the 'set position' branch, try to set 'musgrave texture' lacunarity to 0\n- Crashes everytime for me\n\n[Geonode attribute.blend](Geonode_attribute.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.", "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)" ]

[ "Alpha Channel from Mesh is not rendered when used in Geometry Nodes 3.6 (from 3.5)\nOperating system: Windows 11 Pro & macOS Ventura 13.4.1\nGraphics card: AMD Radeon Pro VII & Apple M2 Max (96 GB)\n\nBroken: 3.6.0, c7fc78b81ecb, branch: blender-v3.6 release, 2023-06-27 08:08 \nWorked: 3.5.0, 1be25cfff18b, branch: blender-v3.5-release, 2023-03-29 02:56\n\nFile build on 3.5 does not work the same in 3.6. Please see image attached. The mesh on the right displays correctly on both versions (holes using alpha channel), however, when using a geometry node with \"object info\" node and picking that mesh, the alpha channel does not display correctly on version 3.6.\n\nMaking a simple geometry node using \"Object info\" with group output on 3.6 works fine, but not with the complex geometry network from the original file. No errors or warnings on any node from the file in 3.5. Impossible to make any sense of what it can be wrong. \n\nOpen file, choose Viewport shading -> Material Preview\n\n" ]

[ "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", "Extreme motion blur not rendering correctly in Cycles\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: x2 GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.17\n\n\nBroken: version: 2.80 (sub 51)\nWorked: (optional)\n\n\nI'm trying to recreate the zig-zag motion blur of bullet tracers seen in WWII aircraft combat footage.\nThis is a test showing the effect I'm aiming for rendered with Redshift\n \n\nIn Blender the blur seems to be angular as if it does not obey the sub frame sampling.\n\n\nParticles must be baked otherwise they do not render properly\nAlso Blender crashes several times while rendering this scene. (CPU & GPU)\n\nPlease see attached simple Blend file.\n[BlurTest.blend](BlurTest.blend)\n\n\n\n", "Save camera transformation matrix out to OpenEXR files\nCurrently cycles exports the normal pass in world coordinates. However there are good and valid use-cases for wanting camera space normals when compositing. This would consist of 2 parts.\n\n - Saving\n - support for saving metadata / attributes to OpenEXR\n - Utilizing this support to save camera data \n\n - Loading\n - support for loading these attributes from OpenEXR\n - some node / way in the compositor to transform the normals channel\n\nAs having a cross software pipeline for compositing and rendering is the norm rather then the exception this is what some other packages seem to also do in order to be able to use and recreate the camera. Particularity nuke (loading) and vray (saving) seem to also do this.\n\nData as saved by vray 3.0\n\n```\ncameraAperture, float\ncameraFNumber, float\ncameraFarClip, float\ncameraFarRange, float\ncameraFocalLength, float\ncameraFov, float\ncameraNearClip, float\ncameraNearRange, float\ncameraProjection, int\ncameraTargetDistance, float\ncameraTransform, m44f ( float matrix 4x4 )\n```\n\nThe current metadata support in imbuf ( the blender image buffer) seems to be modeled after that png provides. This currently only provides string/string key/value parts. I think we should modify the metadata support to include at least int, float, float3/4 and matrix support as attributes. \n\n```\ntypedef struct ImMetaData {\n\tstruct ImMetaData *next, *prev;\n\tchar *key;\n\tchar *value;\n\tint len;\n} ImMetaData;\n```\n\n**I think we should consider in order:**\n\n- For saving \n - Extend \"ImMetaData\" so that value can be *anything* but at least the attributes we need for this\n\n- For saving \n 1) Extend the render api so that an engine can set all these ( currently engines using this api do not write any metadata )\n 2) Support writing this data from cycles\n 3) Fix writing the other metadata ( from stamp )\n 4) Figure out how and if the user should be able to control this. ( I would like to propose having this always on at least for OpenEXR as the data overhead is negligible)\n\n- For loading\n 1) Figure out how this should work in the compositor \n 2) Implement this", "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", "Extended Controls for Camera Gizmo\nCurrently, when switching to the camera view, it’s not immediately clear to users how to manipulate it. The camera must be selected, and it requires some difficult multi-step actions to be able to rotate or move the camera. \n\nAdditionally, from a camera operation perspective, users usually need a more optimized and precise way to only affect the pitch, yaw, panning, tracking and zooming, separately. \n\nWe can make this a lot easier by surfacing optimized camera manipulation gizmos right in the viewport when viewing the scene through the camera view:\n\n\n", "Local Camera doesn't allow animation of camera from excluded collection\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\n Local Camera in N-panel not playing camera action, if this camera is in excluded collection. For comparison Cube is parented to rotating Empty from the same excluded collection and it is working fine.\n\n\nIn default scene:\n - Give Camera an animation and put it in a new excluded collection\n - Select this Camera as Local Camera in N-panel\n - Remove Active Camera (or replace with another camera) from Scene Properties tab and play animation -> not working\n - Include collection back and play again -> working ok\n\nIn attached file:\n - Play animation with excluded/included New Collection\n\n[camera_problem.blend](camera_problem.blend)\n", "Object cryptomatte is not respecting the camera Dof\nOperating system: Windows 11\n \n\nBroken: 3.0, 3.6\nWorked: never?\n\n\n\nCycles object cryptomatte is not respecting the camera depth of field while the material one respects it properly. See the image for comparison\n\n\n\n\nload the attached .blend (it already has the object and the material cryptomattes enabled)\n\nrender\n\ncompare the current cryptomatte types in the compositor\n\n", "Insufficient transform precision?\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.1\n\nIn rigs, and to a lesser degree in geometry itself, there is percievable jiggle in moving objects that are further from world origin.\n\nWe are working on an animation feature film, which has lots of open nature scenes. That assumes moderately large object dimensions and distances (1-10 kilometers) in relation to life sized character close-ups. In shots that are not located in the center of the coordinate system there is a visible jiggle in bone locations and resulting geometry. Same jiggle can be seen in plain geometry objects that are further from origin, however in characters it becomes a problem already at a 100m from the world origin, probably due to many layers of transform/parent/constraint relationships multiplying the error.\n\nInsufficient floathing point precision? #90125 might be of same nature but in rotation.\nEdit: just to be clear this is about precision of transforms and calculated final world coordinates. Never encountered problems with precision of the stored geometry data.\n\n[var.blend](var.blend)\nPress play. Vertex motion gets quantized.\n", "Wrong teleport behaviour if scene scale is greater than 1.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.3.1\n\nCalling teleport using a scene scale greater than 1 will place the camera in a wrong position whose height is greater than expected\n\n\nPreferences>Navigation>View height = 1.7m (default value)\nSceneProperties>Units>Units Scale = 10 (10x default value)\nAdd a plane, it will act as a ground, scale it to 50x\nAdd a cube (default 2m)\nusing Walk navigation, enable gravity with tab, the camera will stay more or less on the same height as the cube. (1.7m ~ 2.0m), everything works as expected.\nbut, if you teleport to any location on the plane, the new camera position will be the cursor position + 17m on the Z axis instead of 1.7m on the Z axis.\nThe blend file contains a scene with a plane and a cube, all done using scene scale 10.\n\n[Scale10Problem.blend](Scale10Problem.blend)\n\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", "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", "Object drop snapping should be disabled for cameras, lamps, etc\nE.g. when dragging a camera from the Outliner into the 3D View, it gets an all-0 rotation, which isn't useful. And it will always snap to an underlying surface, which is annoying because you wouldn't want a camera to snap to geometry or the grid. Think we should just bring back the old dropping behavior, even if it's a bit hard to predict which distance along the view it will use to place the object.\n\nIt wasn't intentional to have this. In review I asked to address this which I thought it was. Probably a misunderstanding.\n\nShould it be disabled for empties as well? It may be useful to have snapping for these.", "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)", "Text moving in status bar\nOperating system: Linux-5.15.4-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.44\n\nBroken: version: 3.0.0 Release Candidate\n\n\nText moving in status bar when moving camera in viewport. \n\nEnable Scene Statistic in Status Bar Preferences. Move camera in Viewport.\n\n[2021-11-30 11-21-38.mp4](2021-11-30_11-21-38.mp4)\n", "Auto perspective sometimes fails\n**System Information** \nOperating system: Windows 10\nGraphics card: 3070\n\nBroken: 3.2.0 and 3.2.1\nWorked: 3.1\n\nAuto perspective setting doesn't work in this case: if you are in camera view or any side view and then you are switching to another side view you have this smooth transition animation between views. If during this animation you press middle mouse button (rotation) to go from side view it doesn't change to perspective. Moreover it \"shifts\" viewport like it was aligned to a bad quad. \n\n1. Turn on auto perspective.\n2. Go to top view.\n3. Change top view to any other side view.\n4. During smooth transition between view press middle mouse button and rotate the viewport.\n5. Now viewport is shifted and stays in orthographic instead perspective." ]

[ "Shake at extreme distances.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\nCPU: Intel Core i5-4460\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nAt an extreme distance, the view becomes extremely shaky and inconsistent. As well as inconsistency in the grid square.\n\nIt can be seen on a clean blender file.\nLock view to 3d cursor\nMove 3d cursor >1,000m away. In any axis but only clearly visible on x or y.\nPanning around cursor shows shake.\nAt >100,000m extreme shake as well as inconsistency in the grid squares.\n\n", "If the camera is animated away from the origin, the background image will shake\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.90.1\nWorked: 2.79\n\nThe background image will shake when the camera is animated more than about 1000 away from the origin.\n\nIf the camera is animated to move or rotate away from the origin more than 1000 (camera tracking data constraint), the background image will be shaken during viewport playback and viewport rendering.\nThe greater the distance from the point of origin, the greater the shaking.\n\nSample files and videos are keyed to the start end as shown in the attached image.\nThe background image is a single static checker image.\n\n[test.mp4](test.mp4)\n\n\n[test.blend](test.blend)\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```", "Particle hair with density influenced by texture is (partially) invisible with cycles CUDA backend\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.0.0 up to latest (version: 3.3.0 Alpha)\nWorked: 2.9.3 (from memory since these blend files can no longer be opened)\n\nThe particle hair in the given example file does not show up properly when switching to rendered preview using GPU compute and CUDA specifically. Switching to Optix, or CPU render makes the hair appear shaded. With not showing up properly I mean that the grid lines behind the hair does get obscured (only very faintly visible in the screenshots), but they are clearly not shaded. Disabling texture density influence also makes the hair appear in the GPU compute and CUDA combination.\n\nI understand that the particle system is deprecated, but figured I might as well report this issue so it does hopefully not occur in the replacement.\n\n 1. Open the attached blend file. \n\n [hair_invisible.blend](hair_invisible.blend)\n 2. Make sure that CUDA is used as the GPU compute backend, and that the device is set to GPU compute.\n 3. Switch to rendered view.\n 4. Observe that the hair is only obscuring the grid lines, but not shaded. Next there are several possibilities.\n\n 5. Switch to CPU backend for cycles and observe that the hair appears.\n 7. Or, disable texture density influence and observe that the hair appears.\n\n 8. Reduce the children to 23 and observe that some part of the hair appears within some bounding box. Further reducing the children makes it appear and disappear occasionally until everything appears (as above) at 9 children.\n\n", "Hair dynamics stopped working after editing and combing in \"Particle Edit\"\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.76\n[system-info.txt](system-info.txt)\n\nBroken: version: 3.1.0 Alpha\n\nHair dynamics stopped working after editing and combing in \"Particle Edit\"\nPossible duplicates: #91258, #56818\n\n[#93344.blend](T93344.blend)\n\n- Open file\n- Cut hair with Cut brush\n# Comb hair with Comb brush with disabled Preserve Strand Lengths option\n\nSimulation no longer works", "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\".", "Eevee slower than cycles when using a lot of particles or collection instances\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 17)\n\nWhen using a lot of collection instances with particles in them, or with a lot of objects, Eevee seems to be very slow in evaluating the scene. \neevee: 2min and 2sek \ncycles (gpu): 9sek\n\nopen the file switch to cycles - hit render\nswitch to eevee hit render\n", "Hair particles won't follow instaced position under 2 level nested collections.\nOperating system: Linux-5.11.0-7620-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 2.93.3\n\nHappens when you have an object with hair as instanced collection (A) inside another collection (B). Then, when you instance (B) the hair particle from (A) will not follow the relative position correctly.\n\n\n- Open .blend file\n- Select \"Cube\"\n- Object -> Quick Effects -> Quick Fur\n- {key Shift A} -> Collection Instance -> Collection\n- Move the instanced collection little away\n- {key M} -> New Collection -> Ok\n- {key Shift A} -> Collection Instance -> Collection 2\n- Move the instanced Collection 2 little away\n- You will notice the hair particle with a wrong position in relation to the original emitter Cube.\n\n1 min video here:\n[bugOrFeature.mp4](bugOrFeature.mp4)\n\nblend 2.93 here:\n[#91008.blend](T91008.blend)\n\n---\n\nNote that the concept works under 2.7 using Instaced Groups:\n\nblend 2.7 here:\n[ConceptWorks_b27.blend](ConceptWorks_b27.blend)\n", "Bake All Dynamics doesn't include all when Lifetime of particle system gets animated\nOperating system: Windows 10\nGraphics card: Quattro\n\nBroken: 2.91.0\nWorked: \n\nWhen the lifetime setting of a particle system gets changed during an animation of the emitter and the animation gets baked, the number of frames are not aligned to the changed lifetime. \n\nInitial lifetime of 100 will be changed during the animation to 500. Number of frames after bake is the frame end setting of the particle system plus the initial life time setting - in this case 100.\n\n- Open attached file or (Based on the default startup):\n - Set number of frames to 1.000\n - Create a sphere - size .1\n - Enter keyframe on frame 0 for location x,y,z\n - Move sphere on x-axis to +10\n - Enter keyframe on frame 250 for location x,y,z\n - Add particle system to the sphere, 1.000 pieces, start frame 1, end frame 250, lifetime 100\n - Add keyframe for lifetime on frame 1 and frame 49 with lifetime value 100\n - Add keyframe for lifetime on frame 50 with a lifetime value of 500\n\n- Bake all Dynamics\nYou will see 351 frames in memory and not 751 as expected\nAlthough the error is the same, rendering of animation does still work in Blender 2.83.5 but not in Blender 2.91.0 anymore\n **WORKAROUND:** Set keyframe for lifetime on frame 0 with lifetime value 500 \n[LiveTimeTest_002.blend](LiveTimeTest_002.blend)\n\n\n\n", "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", "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", "Viscoelastic springs (particle system fluid emitter) crashes blender 2.90.1 (and probably in all versions)\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1060 6gb\nCPU: Ryzen 7 3700x\n\nBroken: 2.90.1, 2.91, 2.92\nWorked: 2.83.x\n\nEnabling viscoelastic springs and try playing the simulation, or baking, it will crash at about frame 5. However when you put springs settings to 0 and turn on it doesn't happen, but doesn't have any effect either.\nThe project files I provide is for 2.90.1. the setup is default cube with particle system, below it another cube with collision with default settings.\n\n[BrokenViscoelastics.blend](BrokenViscoelastics.blend)\n\n- Open the attached file\n- Enabled Vicoelastic Springs\n- Bake", "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", "Keyed Particle Duration Crash\nOperating system: Windows 7 64\nGraphics card: nVidia GeForce GTX 970\n\nv.2.80.60\nDate: 2019-05-10 22:21\nHash: de9d846353bd\n\nBlender will sometimes crash when a keyed physics type particle system references more than one particle system. This usually occurs when attempting to change the duration setting of the second particle system.\n\nIn the provided file, change the duration setting in the particle system settings. Blender will crash.\n\n[Keyed Particle Duration Crash.blend](Keyed_Particle_Duration_Crash.blend)", "Smoke simulation silently fails in Sync to Audio or Frame Dropping playback\nSmoke simulation silently fails in Sync to Audio or Frame Dropping playback\n\n---\n\n**Original Report:**\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.30\n\nBroken: version: 3.1.2\nWorked: Never (tried 2.93, 2.83)\n\nThe smoke simulation does not simulate beyond the first frame in this particular file. Any smoke simulation added or appended from other files stops working as well.\n\nHowever, everything works fine in new files on the same system & hardware.\n\n[smoke simulation issue.blend](smoke_simulation_issue.blend). \n\nOpen the blend file, move the smoke domain to clear the old cache.\nHit play and the smoke is not moving. Other physics (rigid body, particles) are working fine.\n\nDelete everything, add a cube, add the quick smoke effect, and the same happens.\n\n", "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", "Bake of the second particle system after duplication and making it unique makes mess.\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 74)\nWorked: version: 2.79 (sub 7), branch: blender2.7, commit date: 2019-05-23 08:19, hash: 054dbb833e15, type: Release\nbuild date: 24/06/2019, 17:18\n\nIf you duplicate particle settings, make them unique, and tune, bake of dynamica will broken.\n[2019-07-16_10-03-29.mp4](2019-07-16_10-03-29.mp4)\n\nFinally I found how to reproduce it.\n\nCreate plane, \nCreate particle system that emits cubes (color A) from -50 to 50 frame with short lifetime (20).\nDuplicate particle settings, make settings unique, rename it.\nChange instance to another cube (color B), change working period to 50 — 100 frames.\nCheck work in the viewport. Bake all dynamics, Revert file.\n\nMessed:\n[duplicated particle settins.blend](duplicated_particle_settins.blend)\n\nBug is not appere only if you create separate fully independent settings in the fresh file.\nWith independently created particles systems\n[fresh separate created.blend](fresh_separate_created.blend)\n\n\nPerhaps it can be connected with #61963\nLooks like some data just stucks\n\n\n" ]

[ "Particals stop rendering on the last frame\nOperating system: Windows 10 Home\nGraphics card: 1050 Ti\n\n3.0 & 3.0.1\n\nAfter baking particles, then rendering in either Cycles or Eevee, the last frame in the animation will not render the particles.\n\nAdd a new mesh, like a cube or sphere or a Suzanne, any mesh with a face will do.\n[Optional] Move said object out of camera view for a cleaner render.\nAdd a particle system to the Default Cube, and change the render as under the 'Render' tab for particles to object and set the instance object to the mesh created prior.\n[Optional] Change the end frame to something like 30 so the bake is shorter, \nBake the particles, jump to the last frame and render the frame, note the absence of particles, now go back one frame so it's the second to last frame, note the presence of particles\n\n\n[partical test.blend](partical_test.blend)\n", "Baked particles dont render in final frame\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79b\n\n\nBaked particles in final frame shows up in viewport but not in render.\n\nLoad attached blend file. [bug particle 280.blend](bug_particle_280.blend)\nPlay animation, move to last frame. Render and you can see the particles fine.\nBake the particles, move to last frame. Render and now particles missing.\n\n\n\nOriginally attached file:\n[Bug test particles.blend](Bug_test_particles.blend)\n", "Bake all dynamics does not bake last frame of frame range [Even though it appears at first so!]\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 3.0 & 3.2\nWorked: None found\n\nWhen baking particle systems for a specific frame range the last frame of the frame range will not be baked.\nThis results in rendered sequences having an no particles in their last frame.\n\nSeems to be an issue with render frame range being inclusive and bake using it exclusive.\n\n[bug.blend](bug.blend)\n\n\n # Delete all baked dynamics\n\n # Bake all dynamics\n\n # It appears as if frame 50 actually has particles\n\n # Save .blend file\n\n # Close blender\n\n # Open the file again\n\n # Frame 50 does NOT have particles!\n\n # Render the sequence\n\n # Last frame will NOT have particles (even though it should)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n" ]

[ "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", "Child Object jumps away with changing the parent bone\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.91.0 Alpha\n\nWhen i parent an object to a bone, and change the parent in the object properties in the relations panel, then the child object jumps around. And switching back to the original object does not reposition the child object at the original position.\n\n\nCreate a armature with at least two bones. Parent the default cube to the armature with method bones.\nIn the relations panel switch the parent bone to the second bone. The cube will jump away.\nSwitch back to the original bone. The cube will jump even further away. And will not go back to the original position. \n\nBlend file is attached.\n\n[bonejumping.blend](bonejumping.blend)\n\n[bonejumping.mp4](bonejumping.mp4)\n\n", "Auto-Merging keyframes in the Driver Editor has unappropriate threshold (merges keyframes that shouldnt)\nOperating system: windows 10 & Linux ubuntu\nGraphics card: GTX 1070\n\nBroken: 3.6.2\nWorked: unknown\n\nSee att. blendfile and pictures; moving the base of the armature in the Y direction drives the shapekey of the torus.\nIf you edit a driver keyframe by just slightly moving it to the right, the keyframe next to it is removed\n\nTry editing keyframes in the driver f-curve editor\n\n\n**Note**\nDrivers editor has the driver value as the x-axis (this can be arbitrary low, e.g. in the report, this was the x location [in meters] so handling quite small values where \"keyframes\" where ~0.01 apart\n\n`BKE_fcurve_merge_duplicate_keys` acts with a threshold of `BEZT_BINARYSEARCH_THRESH 0.01f`", "shrink/flatten not working right way?\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\nBroken: version: 2.91.0 Alpha\n\ni think shrink/flatten not working the right way. only top works fine goes up down.\nbut bottom and sides are backwards and a bit counterintuitive.\n\ni dont know if its bug but wanted to report anyway.\n\n\ncheck video\n\nthanks\n\n\n[2020-09-27 04-57-36.mp4](2020-09-27_04-57-36.mp4)\n\n[blender.blend](blender.blend)", "When double clicking to selecting text the first characters aren't selected\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.23\n\nBroken: version: 3.6.2\n\nWhen you double click on any text field with the intention to select all of the text when you start dragging to select the other words the first characters dont stay selected\n\ndouble click on a word and then drag your mouse to select the next or previous words. Some of the characters will always become unselected when you drag the mouse as seen in the attached video\n\n\n\nusually when double clicking a word the entire word stays selected regardless of where the initial mouse location was when double clicked but in blender the characters before or after the mouse location when double clicked don't remain selected when you drag to select more words", "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", "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", "Exact Boolean with Incorrect Result - multiprecision/float round trips not exact\nOperating system: Windows 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.91.0 Beta dca36a8ec922\n\nAnother case, where the exact boolean does not work as expected. (Sorry @howardt, I had to break it. I have to admit, that I have not run into this problem in a real scene.)\nAgain, this manifests after applying the same difference operation several times.\n\n[boolean_rotated_box3.blend](boolean_rotated_box3.blend)\nLook at the scene.\nThe first run of the modifier works as expected, the second creates overlapping faces, the third removes most of the mesh.\nThis \"bug\" is very erratic, and if the transform of the objects is slightly changed, it does not occur.\n\nThis is what I see:\n\n\nThe expected behavior is that the second and third modifier do nothing.", "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", "Workspace tabs click-dragging only works when starting from current tab.\nSystem Information\nOperating system: Windows 10\nGraphics card: Geforce GTX 1070\n\nBlender Version\nBroken: 2.80 2019-02-20 20:10\n\nShort description of error\nClick-dragging on tabs works fine in the Preference's tabs now, but fails to work on the Workspace tabs *unless*you start from the current one (so to rephrase, for clarity: if you start on one that's not the currently selected one, it will simply not go through the tabs)\n\n- Create workspace (either duplicate or append) so there's more than one\n- Click on one of the workspaces that isn't currently displayed\n- Drag left and right, you'll notice nothing happens.\n- Click on the currently selected workspace's tab\n- drag left and right: this should switch between workspaces as you pass over their tabs", "Regression: Attempt to move object with Copy Location (with Offset) crashes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nA consistent crash when trying to move an object with COPY LOC w/ Offset enabled.\n\n\n1. Open the attached blend file\n\n2. Move the pre-selected object in any direction, you may have to do this two or three times\n\n3. program will crash with EXCEPTION_ACCESS_VIOLATION\n\nThis is happening every time.\n\n```\nStack trace:\nblender.exe :0x00007FF73E03C510 blender::bounds::min_max<blender::VecBase<float,3> >\nblender.exe :0x00007FF73E03BD30 blender::FunctionRef<void __cdecl(blender::Bounds<blender::VecBase<float,3> > &)>::callback_fn<<lam\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF7425212F0 blender::CacheMutex::ensure\nblender.exe :0x00007FF73E042390 BKE_mesh_minmax\nblender.exe :0x00007FF73E0409F0 BKE_mesh_boundbox_get\nblender.exe :0x00007FF73E02E940 BKE_object_boundbox_get\nblender.exe :0x00007FF73E02F410 BKE_object_dimensions_get\nblender.exe :0x00007FF73E613520 RNA_property_float_get_index\nblender.exe :0x00007FF73E235050 dtar_get_prop_val\nblender.exe :0x00007FF73E235410 evaluate_driver\nblender.exe :0x00007FF73E168590 calculate_fcurve\nblender.exe :0x00007FF73E156270 BKE_animsys_eval_driver\nblender.exe :0x00007FF73E4464F0 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF73E446320 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7425175C0 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FF9998CA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FF9A5D192C0 recalloc\nKERNEL32.DLL :0x00007FF9A6F72690 BaseThreadInitThunk\nntdll.dll :0x00007FF9A882AA40 RtlUserThreadStart\n```\n\n", "Indices order is inconsistent with duplicate operation\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.2.0\n\nIndices on copied geometry (in edit mode) are sometimes reversed (verts) or misplaced (edges). Not sure when it happens exactly, but it can happen, if you duplicate and delete new geo couple times.\n\n\n\n\n - Enable *indices* overlay to see results\n - Create clockwise mesh loop (for example draw it in *Edit mode* from single vert via *ctrl + mouse click*)\n - Select mesh and press *shift + D* and *Enter*\n - Check verts indices order, it should match initial clockwise direction\n # Delete copied geometry and repeat steps 3 & 4 -> indices should be reversed. (Interesting thing that if you change *Mode* option in operation's menu from 1 to 0 it preserves original order)\n\nOr in attached file perform steps from 3 to 5\n\n[indices_order.blend](indices_order.blend)\n\n", "Modifying keymap produces unreliable results when duplicate entries exists\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken: 2.83-3.0\n\nModifying keymap produces unreliable results when duplicate entries exists.\n\n**Steps to reproduce**\n1. To create duplicate keymaps apply patch \n[P2817: (An Untitled Masterwork)](P2817.txt)\n```\ndiff --git a/release/scripts/presets/keyconfig/keymap_data/blender_default.py b/release/scripts/presets/keyconfig/keymap_data/blender_default.py\nindex 5fb0f052154..ad335883afa 100644\n--- a/release/scripts/presets/keyconfig/keymap_data/blender_default.py\n+++ b/release/scripts/presets/keyconfig/keymap_data/blender_default.py\n@@ -2758,20 +2758,28 @@ def km_sequencercommon(params):\n def km_sequencer(params):\n items = []\n keymap = (\n \"Sequencer\",\n {\"space_type\": 'SEQUENCE_EDITOR', \"region_type\": 'WINDOW'},\n {\"items\": items},\n )\n\n items.extend([\n *_template_items_select_actions(params, \"sequencer.select_all\"),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n+ {\"properties\": [(\"type\", 'SOFT')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n+ {\"properties\": [(\"type\", 'HARD')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n+ {\"properties\": [(\"type\", 'SOFT')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n+ {\"properties\": [(\"type\", 'HARD')]}),\n (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n {\"properties\": [(\"type\", 'SOFT')]}),\n (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n {\"properties\": [(\"type\", 'HARD')]}),\n (\"sequencer.mute\", {\"type\": 'H', \"value\": 'PRESS'},\n {\"properties\": [(\"unselected\", False)]}),\n (\"sequencer.mute\", {\"type\": 'H', \"value\": 'PRESS', \"shift\": True},\n {\"properties\": [(\"unselected\", True)]}),\n (\"sequencer.unmute\", {\"type\": 'H', \"value\": 'PRESS', \"alt\": True},\n {\"properties\": [(\"unselected\", False)]}),\n\n```\n \n\n2. Remove shift modifier key from all `sequencer.split` keymap entries\n - First time this works, after that entries will be removed\n3. Try to set Shift modifier key for last `sequencer.split` keymap entry.\n - This sets Shift modifier key on first `sequencer.split` keymap entry.\n4. Try to set Shift modifier key for second `sequencer.split` keymap entry. (Type is Hard)\n - This entry will jump to bottom and it is last entry now.\n", "After duplicating a collection with rigidbody objects, the simulation doesn't apply to the new rigidbody objects\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU\n\n\nBroken: `master` branch\nWorked: Don't know if it ever worked\n\nAfter duplicating a collection with rigidbody objects, the simulation doesn't apply to the new rigidbody objects\n\n**Steps to Reproduce**\n\nIn a new blender project, add a new collection. Add a cube to the collection. Add a rigidbody to the cube. Verify that playing the simulation causes the object to fall under gravity.\n\nCopy and paste the cube to create a new cube inside the collection. Move the new cube so both are visible. Verify that playing the simulation causes both cubes to fall under gravity.\n\nIn the outliner right-click on the collection and select \"Duplicate Collection\". Move the two new cubes so all four cubes are visible. Run the simulation.\n- The two cubes in the original collection will fall under gravity.\n- The two cubes in the duplicate collection do not move and are not affected by the simulation.\n\n \n\nIt appears the two cubes in the duplicated collection are not added to the RigidBodyWorld collection.\n\n", "Objects with clampto constraint change their position after the target object from copy rotation constraint is rotated and then pressed ctrl+z\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.3\nWorked: 2.82a\n\n\nOn the video clampto constrain is used on the ammo. When I rotate it and press ctrl+z ammo change their position and move chaotically\n\n[20210901_054810.mp4](20210901_054810.mp4)\n\n[#91102.blend](T91102.blend)\n\nRotate the empty and press ctrl+z, object array in \"ammo\" collection will change shape.\n" ]

[ "Duplicate macro faulty after rotation\nBroken: 2.79 and above\nWorked: 2.78c\n\n**Short description**\nThe \"duplicate and move\" macro fails to remember translation for redo after it's been switched to rotation at least once.\n\n**Exact steps to reproduce**\n\n1. Load the default scene\n2. Select the cube\n3. Duplicate it with shift+d, immediately switch to rotation with r, move the mouse and click to confirm.\n4. Note that the redo panel correctly reflects the rotation angle.\n5. Press shift+r a few times and note that the cube is duplicated and rotated correctly.\n6. Press shift+d, and this time simply move the cube and confirm.\n7. Note that this time translation in redo panel is 0 (or incorrectly set) for all three axes.\n8. Press shift+r a few times and note that the cube is duplicated but **not** moved.\n\n[Demo video ](wDJHa03DmWw)" ]

[ "Moving cursor quickly jumps it out of the window when translating objects\nArchlinux\nNvidia GTX 460\n\nBroken: 2.7 RC1\n\nIt's possible to escape the window by moving the mouse quickly while translating an object. This does not seem to be possible while moving the view.\n\n1. Open blender in windowed mode with some space at the top of the screen\n2. Open default startup file (load factory settings)\n3. Select the default cube and press G+Z, then move the mouse sharply upwards as fast as possible (I don't actually need to move it that quickly, it's happened several times by mistake. But just to be sure.). The cursor will escape the window (will not wrap).\n4. Try the same with rotating the view (press and hold MMB, move mouse upwards quickly). The cursor will not escape, even when going at least as fast as when translating objects (sometimes the cursor will appear outside the window, but it still wraps).\n", "Crash after undo \"Mask slice to new object\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\nWorked: This problem happens to me with 2.92, the pc that I use now I formatted it, unfortunately before I used version 2.82\n\nMy problem is that when I use the option \"mask slice to new object\" and then I use ctrl + Z the blender closes !! I formatted the PC a few weeks ago, unfortunately I didn't use version 2.92 before. What I realized is that when I use the \"mask slice to new object\" option and then go to edit mode, I can use control + Z without any problem, that is, it does not close.]\n\nThis happens to me in any file:\n\n1. Sculpture mode.\n2.Use the \"mask\" or \"box mask\" brushes\n3. I paint the mask.\n4.I go to the \"MASK\" menu.\n5. I click on \"mask slice to new object\".\n6. Press CTRL + Z.\n7. Blender closes.\n", "Fluid inside Effector / Fluid Inside Closed Object not Working\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.96\n\nBroken: version: 3.2.0\nWorked: 2.83 (#104938)\n\nFluid simulation stops flowing while inside effector whether the effector its one mesh or separate mesh.\nThis also works, when I created a holes in the mesh, but I really need to close it completely for my actual project.\n\n\n[Fluid Inside Effector.mp4](Fluid_Inside_Effector.mp4)\n\n\n\n[Fluid Inside Effector.blend](Fluid_Inside_Effector.blend)\n", "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.", "Text Object Edit Cursor nearly invisible in 2D Animation or Light Background\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics 640 Intel 4.5.0 - Build 26.20.100.7986\n\nBroken: version: 2.92.0 Beta\n\nMost of my workflow takes place with a light background, as is the case with the 2D-animation startup file. As you can see from the attached image, the Text Object Edit cursor is easily visible with a darker world, but in the 2D-animation with a light world, it is nearly invisible and unusable when there is a lot of text, making editing within Blender untenable.\n\n\nOpen Blender, select 2-D animation. Go back to object mode. Press Shift-A, Add a Text object. Turn the object towards the camera or rotate the camera to see the text. Change the text object's material to black or another color so it is easily visible from the background white. Tab to edit mode. Paste or type in a paragraph's worth of text, then try and go in and edit it. The text cursor is basically invisible, making editing the text extremely difficult. \n\nThis is NOT the mouse pointer, this is the text-edit cursor. I also checked on this thread T78498 but confirmed in the screenshot that the overlays are turned on. I also checked through all Edit > Preferences > Themes, but could not find a setting that affects the color of the text cursor/highlight. \n\nThe quick fix would be to give access in the preferences to the cursor color for text object edit (then we could just change it to Magenta or something visible with common backgrounds). The fancier fix would be to adjust the cursor color based on the background or have it be half white/black so it is always visible.", "Particles disappear, motion blur not showing properly\nOperating system: Windows 10 Pro, version 21H2, OS version 19044.2486, 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB, version 31.0.15.1694\n\nBroken: version: 3.2.1\n\nParticles disappear in animation, most notable at the beginning.\n\nDuring the dissolve effect, motion blur isn't showing. At the moment the effect ends, motion blur shows up.\n\n1. Render e.g. frame 16; particles are not showing, no motion blur.\n2. Render e.g. frame 31; all particles seem to be showing, motion blur.\n\n", "Blander crash without ray shadows Nvidia GTX 950M CUDA\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 16)\nWorked: (optional)\n\nWhen turn off ray shadow visiblity render becomes slow and the blender crashes.\n[2019-10-28_03-53-23.mp4](2019-10-28_03-53-23.mp4)\n\n------------\nI tested again on GTX 750 Ti and 2.92.0 Alpha. If I turn shadows off first, then switch to rendered view, it gives bad render:\n\nIt disappears when you do something. Typical when there's something wrong in Cycles. I need to restart Blender to be able to render again.\nWhen I turn rendered view first, then turn shadows off, it sometimes crashes.\nThis is all Cuda. Optix renders nothing at all. I presume Optix doesn't do volumes yet.\nAlso noticed that deleting sun lamp and leaving only area lamps fixed the issue.\n\n**Steps to reproduce**\n[облака в стекле.blend](облака_в_стекле.blend)\n- Open file\n- Disable shadow ray invisibility on object\n- Switch to rendered shading\n", "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", "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.", "Performance issues when moving bones of an armature when the Outliner is set to Blender file\nBroken: 2.93\n\nThis happens on heavy scenes and with many linked files, if you have an Outliner opened and set to \"Blender file\".\nThe fps drops dramatically only when trying to move a bone of an armature. It doesn't matter the complexity of said armature.\nThe problem stops happening after closing the Blender file Outliner.\nCould it be related to this other fix? T87842", "Material Properties Button\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 6700 XT ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.18.220726\n\nBroken: version: 3.5.0\n\nevery time i click on the materials properties button on the right, blender shut down.\n\nit happens when you start or anytime what you are doing. Just start program, click materials properties button.\n\n", "Objects do not retain View State when turning Collections Off then back On\nOperating system: Linux-5.8.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.92.0\n\nIf an object has been hidden within a collection, after turning the collection off and then back on the object becomes visible again. It's \"hidden\" state is not retained.\n\n\n- Drag the cube into a new collection\n- Disable `Hide in viewport (eye button)` option for cube\n- Disable `Exclude from view layer option (checkbox)` for collection.\n- Enable checkbox, now cube is visible (it should not)\n\nResult = the cube is visible, it should remain hidden.\n\nN.B. This does not affect whether the cube is hidden from renders - the render view state is retained.\n\n", "Blender 2.80 Canceling of visibility actions during opened panel with object default parameters.\nwin 10 - 64 bit\nNVIDIA GeForce GTX 560\n\n2.80 beta, 1df6a98b176f, blender2.8, 2019-03-05\n\n**Error description**\nLooks like a small flaw. Panel with default parameters(radius, etc..) of standard objects if objects just created - will be canceling your actions with outliner panel (visibility actions) if you dont close it and continue changing parametrs after that\nDemo: 0876b975cd74ce4d9400b6556e5cbe14.mp4\n\n**Steps to reproduce**\n\n- Open new general template\n- Add mesh - circle\n- Hide cube in outliner\n- In Adjust Last Operation panel change radius\n\nCube is no longer hidden", "Mode locked and crash if objects become disabled in viewport while not in object mode\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 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: didn't crash but showed an error message in 2.91.2\n\nObjects that are in a mode which is not Edit Mode nor Object Mode, will lock the mode setting (so the mode options are greyed out and unusable) if they get disabled in the viewport. Hiding will not cause the this bug, it needs to be disabled in viewport using that display icon in the outliner, not the eye.\n\nThe solution for this is probably to make the disable in viewport action switch the mode to object mode if the active objects gets removed (much like delete from outliner). Another solution would be to still allow the mode switch.\n\nMuch worse though! Blender crashes sometimes when it gets into this state. I can reliably crash blender as described below.\n\nGo into weightpaint mode of the default cube and disable it in the viewport using the outliner (you need to enable the option first). Now you are stuck and have to enable it in the viewport first to be able to edit anything.\n\nNow restart blender etc. and try this:\n1. Go into Vertex Paint Mode of the default cube\n2. Hit Tab to go into Edit Mode\n3. Disable the cube in the viewport using the outliner as above\n4. Hit Tab to switch out of Edit Mode -> Crash", "Holding Ctrl disables Object Lock Modes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.2.1\n\n\nObject Lock Mode have no effect when Ctrl is held, for instance, while using Shortest Path Selection as shown in the following video:\n\n[bug-object-lock-mode.mp4](bug-object-lock-mode.mp4)\n\nThis also happens in other cases like selecting Reference and Background images:\n\n[lockobject.mp4](lockobject.mp4)\n\n" ]

[ "Transforming a hidden object (hidden via Outliner>Eye-Icon) crashes Blender application\nOperating system: Linux Ubuntu 18.04.1LTS\nGraphics card: nvidia 1060 mobile\nNote: see attached \"system-info.txt\" for further details\n\nBroken:\nBlender 2.80 Beta *Date:2019-01-03 17:12* Hash: a30bdcc142f1 (as from Splashscreen)\n\n\nTransforming/Moving/Scaling/Rotating an object, which has been hidden via the corresponding \"eye\" icon in the Outliner window, crashes Blender.\n\n\nBug is easy to consistently reproduce starting from the default scene:\n1) Start from the default scene that Blender presents you with when opened;\n2) Right-click mouse on the default cube object to select it;\n3) In the Outliner window click on the \"eye\" icon relative to the viewport-visibility of the default cube object, in such a way to have the cube hidden/invisible in the Viewport but still selected as from step 2.;\n4) With the default cube object hidden but still selected press \"G\" key to grab/translate the hidden object and drag the mouse to move the cube object to a new position;\n5) When you left-click mouse in order to confirm translation of the cube object to the new position Blender will crash/exit.\n\nNotes: The same behavior happens both when you try to translate \"G\" or scale \"S\" the hidden object: Blender crashes on confirmation of the attempted transformation; if you try and rotate \"R\" the hidden object, then Blender crashes as soon as you drag the mouse to rotate, even before left or right mouse-clicking for confirmation/cancel of the operation.\n\nsystem-info.txt\n[system-info.txt](system-info.txt)" ]

[ "EEVEE: GPU Subdivision causes noticeable shading differences\n**System Information: System 1**\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.4369\n\n**System Information: System 2**\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.79\n\nThis object does not appear shinier/with brighter highlights when rendered on Eevee and GPU subdivision is turned OFF.\n\nI noticed this when using both PCs to render an animation faster, this particular material flickered at random and it was because one PC was outputting slightly different results than the other.\n\n- Open .blend file\n- select EEVEE engine and start viewport render\n- toggle GPU subdivision to notice the difference\n", "Bisect Tool Todo\n## Bisect\n * - [ ] {icon circle color=yellow} We should add an updated Gizmo here \n\n *Comment: should this gizmo's plane be an outline (design looks opaque), also, it's quite different to the previous design, see: #54661 ~ ideasman42*\n\n *Answer: This design is more similar to what we have now, but makes it easier to rotate and move the bisect plane along specific axes. The blue plane here should be transparent, not opaque. ~ billreynish*\n\n * - [x] {icon circle color=yellow} We should add these options to the tool settings: Fill, Clear Outer, Clear Inner. Otherwise, users have to keep setting these settings for every bisect operation.\n * - [ ] {icon circle color=yellow} We should add an option called 'Only Selected' just like the Knife tool. Currently it always only applies to selected elements, but that makes many successive bisects annoying because you constantly have to select all. \n", "Bump map texture painting in 3d viewport applies gamma correction to 32-bit float noncolor image data. \nOperating system: **NA** (Windows-10-10.0.18362-SP0 64 Bits, Darwin)\nGraphics card: **NA** (GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35, AMD Radeon HD 6970M 4.1 ATI-1.68.25)\n\nBroken: version: 2.90.1, 2.92.0 Alpha\n\nWhen texture painting a float non color image, the `3D viewport` uses a different `mix` algorithm than the one used on byte images in the 3D viewport, and floats and bytes in the `Image Editor`.\n\n\n\n| **Mix additive ?** | Byte | Float |\n| -- | -- | -- |\n| Image Editor | Yes | Yes |\n| 3d Viewport | Yes | No |\n\n\n\n\n\n\n\nProblem with texture painting bump maps. The image above shows two drawn curves. The left curve was drawn in the image editor, the right curve was drawn in the 3D viewport. Brush color is set to (r,g,b)=(0.6,0.6,0.6). The image texture used for the bump map was generated by the brush tool which creates a noncolor image set to 0.5. The problem occurs when specifying a 32-bit float for that image. \n\nYou can open the 2 following .blend files, and try painting a stroke in both the 3D viewport and the Image editor.\n\n\n\n[T82818_texturepaint_mix_byte.blend](T82818_texturepaint_mix_byte.blend)\n\n\n\n\n\n[T82818_texturepaint_mix_float.blend](T82818_texturepaint_mix_float.blend)\n\n---\n[system-info.txt](system-info.txt)", "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", "Denoise + Pixel Size + Render Region = Artifacts in Viewport\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: \nNVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84, \nNVIDIA GTX 1080.\nOptix is used.\n\nBroken: version: 3.2.0 Alpha\nWorked: Don't know.\n\nWhen the pixel size for render preview is increased, (2X, or 4X), Render region is set, and viewport denoiser is turned on, the viewport render gives weird artifacts.\n\n\nTurn on render preview, and zoom in this file:\n[Pixl Size Denoise Render region.blend](Pixl_Size_Denoise_Render_region.blend)\n\n", "Eevee clamping color values when viewport rendering and using viewport HDRI\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n[system-info.txt](system-info.txt)\n\nBroken: version: 3.0.0 Alpha\nWorked: (never)\n\nWhen doing a viewport render, color values are being clamped. In 2.92 a workaround for this was introduced - if you disable overlays, color is being processed as it should.\nHowever, if you use a viewport HDRI, even with the overlays turned off, values are still clamped.\nAs these two are often used together to get some quick snaps, it is a little inconvenient\n\n\n\n[#88288.blend](T88288.blend)\n\n- Open file\n- Switch to rendered view\n# Viewport render image\n\nColors are clamped even though overlays are disabled\n", "The Denoise Node Turns the Rendered Image into Pure Black at the Resolution of 1920 *1920 \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\nCPU: Intel Core i7-8550U\n\nBroken: version: 2.90 (sub 1)\nWorked: Never\n\nThe denoise node fails to work when the render resolution is set to 1920*1920\n\nBased on the default startup, you can also check out the attached .blend file as well if you want.\n1. Switch the render engine to Cycles\n2. Under Output Properties tab, set the resolution to 1920*1920, make sure the percentage is 100%\n3. Under View Layer Properties tab, check Denoising Data\n4. Go to the Compositor, add a denoise node, connect all three sockets accordingly\n5. Hit F12 to render\nThen you will see, after the render is done, the image becomes pure black.\n\n[Denoise Node Resolution Bug.blend](Denoise_Node_Resolution_Bug.blend)\n\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", "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", "Unexplained reflection logic (artifacts) on water shader with bump mapping\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.59\n\nBroken: version: 3.2.0\nWorked: Probably never\n\nUnexplained reflection logic (artifacts) on water shader with bump mapping.\n\n* Open the sample project in attachment.\n* Test the rendering in Cycles in the viewport.\n* Test the different shaders (Shading tab) with the tests cases in the object “Water_Large” in the “Water” collection.\n* Try to vary the height of the camera from 0 meter to many meters to see how it affects the artifacts.\n* You can also enable the “Test - Torus” collection for extra testing.\n\nThe object “Water_Large_SimpleReflection” shows the result without any bump mapping. The reflection is accurate. The object “Water_Large” shows the result with bump mapping applied. Naturally, the reflection is distorted because of the angle of the waves created on the reflection. That is normal, but the reflection of a portion of the rectangles is offset with wrong placement.\n\n**The problem:**\nFor a reason that I really cannot explain, the rectangles of 45 degrees are reflected vertically on the water surface from a precise horizontal position. Without expecting perfection, the reflection should have been displayed with an average of 45 degrees on the water. It is like a threshold where the reflection logic changes See the screenshot and check where the red arrow is for an indication.\n\n* On the screenshot “Camera 1 - 2 meters high”, we can see the reflection making a steep angle at a precise horizontal position on the water.\n* On the screenshot “Camera 2 - 20 meters high”, we can see the problem not being as present as on camera 1. There are still some artifacts.\n\n**Observations:**\n* The problem tends to disappear as we increase the camera distance from the water surface.\n* Furthermore, the problem is less apparent when the noise scale of the texture node used to create the height factor of the bump mapping is lower. You can play with the parameters of the “Water\" shader.\n* The objects closer to the camera are lower in the image height and also show are a more natural reflection (the rectangle at the right for example).\n\nAs you can see on the screenshots, a part of the far objects is being reflected correctly on the water surface, but the majority of the color is not aligned with the angle of the object. Strangely, the objects are being reflected at 45 degrees from the far horizon line and suddenly, from a virtual horizontal line, they start reflecting vertically as if the objects were totally vertical. And that happens at a precise vertical height on the water surface. This is exactly where the problem happens.\n\nFor years, I have never seen any issues with reflections. If you have a scene with a city skyline in the horizon, you are less likely to see that kind of artifacts. In the present case, we have the equivalent of skyscrapers, but at 45 degrees.\n\nI also tried with Blender version 2.93 and the problem is the same.\n\nBefore reporting this bug, I looked at the scene setup. To validate the nature of the problem, I decided to take into account the following factors. \n* The bump height and the distance are relatively low. Nothing exaggerated here to mess up the results.\n* The height of the camera is at 2 meters from the water surface, which is about the height of a human. Nothing exaggerated once again.\n\nI was not sure if that was a bug in Cycles or a limitation. I relied on the definition that has been given to me, “if it works as expected”, and clearly it is not working as expected. Therefore, I decided to report it.\n\n[ReflectionBug.blend](ReflectionBug.blend)\n\n\n\n\n\n", "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", "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]().", "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", "Eevee refraction regression in orthographic view\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.93.0 Alpha\nWorked: 2.91\nWorked: 2.92\n\nIn orthographic view, with the view or camera camera perpendicular to a refractive surface, screen space refractions appears blurry, as if it had roughness, even with refraction shaders with 0 roughness\n\n2.91: \n\n2.93: \n\nEdit: In perspective it's also noticeable in the center. It looks like a small ball or dot that distorts the image slightly\n\n\nOpen file in different versions\n[bugRefractionEevee.blend](bugRefractionEevee.blend)\n\n\n", "Random Per Island working incorrectly with sharp edges and volumes\nOperating system: Linux-5.0.0-36-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.50\n\nBroken: version: 2.82 (sub 4)\nWorked: (optional)\n\nRandom Per Island not working correctly with sharp edges or volumes.\n\n\nSharp Edges:\n\n- Create Cube\n- Add Bevel Modifier with Harden Normals\n- Set Smooth Shading\n- Set Auto Smooth\n- Random Per Island is affected incorrectly by sharp edges, even after applying Bevel modifier\n\nVolumes:\n\n- Create cube (or array of objects)\n- Create volume shader\n- Assign Random Per Island to volume shader\n- No random colors\n\n[random_per_island.blend](random_per_island.blend)" ]

[ "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)" ]

[ "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", "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)", "Particle system behaves inconsistently in viewport and render when instance object visibility is disabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro [P2200](SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.91.0 Beta\nWorked: The behavior was different in 2.80\n\nWhen the instance object of a particle system is disabled in the viewport the particles are also disabled in the viewport. However when the instance object is disabled in render they still appear in the render.\n\n1. Open the default scene.\n2. Create another object (B).\n3. Create a particle system modifier on the default cube (A).\n4. Set Particle Settings to Hair (A).\n5. Set Render -> Render As to \"Object\" (A)\n6. Set the Instance Object to the other object (B).\n7. Disable the object (B) in viewport and render\n8. Render the scene, observe that the object has particles rendered\n[particle_visibility_bug.blend](particle_visibility_bug.blend)\n", "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.", "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)", "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", "The viewport grid is visible over the curves hair \nOperating system: Linux-5.15.14-1-lts-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46\n\nBroken: version: 3.3.0 Beta\n\nThe viewport grid is visible over the curves hair with cycles render engine.\n\nWith cycles > Press render preview on the viewport.\n[grid_cycles_and_hair_bug.blend](grid_cycles_and_hair_bug.blend)\n\n{[F13429852](image.png) size=full}", "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", "UDIM tiled images with generated contents dont render in Cycles\nOperating system: Windows 10 pro 64 bit, AMD Ryzen 5 3400 G with radeon vega graphics, 16 gb ram\nGraphics card: nvidia GTX 1650 super\n\nBroken: 2.91.0, 0f45cab862b8, master, 2020-11-25 \n\n\n\nworking on the new udim mode I was proving my uvs with a uv grid and when i went to try to get a render i note that when you change to cycles in the render engine the texture is lost and dont appears in the render but in eevee it works fine. the error only happen when you try to use cycles.\n\n*Open the file\n*Go to render preview mode\n*Change to cycles in the render engine section", "Zero area meshes lacking an outline (even if selected)\nOperating system: Linux-5.10.12-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.79\n\nZero area meshes lacking an outline (even if selected)\n\nThis came up in a special case in #85461 (Mesh. Skin modifier shows nothing in viewport, when mesh do not have root.), reporting the general case here\n[zero_area_mesh_missing_outline_when_selected.blend](zero_area_mesh_missing_outline_when_selected.blend)\n\n- Open file\n- Cube (scaled to zero in two axis) is selected but has no representation in the viewport (outline)\n- open the same file in 2.79 and observe the outline\n\nThis might very well be a Known Limitation, just bringing this up here so we have a task we can refrence if this comes up again.\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", "Can't control image transparency\nSystem:\n```\nKernel: 5.4.64-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 \nDesktop: GNOME 3.36.6 Distro: Manjaro Linux\n```\nCPU:\n```\nTopology: Dual Core model: Intel Core M-5Y10c bits: 64 type: MT MCP \narch: Broadwell rev: 4 L2 cache: 4096 KiB \nflags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx \nbogomips: 7981 \nSpeed: 798 MHz min/max: 500/2000 MHz Core speeds (MHz): 1: 798 2: 798 \n```\n 3: 798 4: 798 \nGraphics:\n```\nDevice-1: Intel HD Graphics 5300 vendor: Hewlett-Packard driver: i915 \nv: kernel bus ID: 00:02.0 \nDisplay: x11 server: X.org 1.20.8 driver: intel unloaded: modesetting \nresolution: <xdpyinfo missing> \nOpenGL: renderer: Mesa Intel HD Graphics 5300 (BDW GT2) v: 4.6 Mesa 20.1.7 \ndirect render: Yes \n```\n\nBroken: Blender 2.90.0\n\tbuild date: 2020-09-04\n\tbuild time: 21:14:50\n\tbuild commit date: 2020-08-31\n\tbuild commit time: 11:26\n\tbuild hash: 0330d1af29c0\n\tbuild platform: Linux\n\tbuild type: Release\n\nI've also tested on 2.83 from the site, and some appimages i found on github of 2.9 and 2.83 it did not work on any of those.\n\nCan't control transparency of images on this machine, the image keeps the same transparency with every value except 0.0 where it completely disappears.\nI've used blender on a different system (with different hardware and linux distro) and this error does not occur there, just to check I was pressing the right buttons.\nI can control the transparency of the basic cube through Materials>Viewport Display>Color, so it's not problem with transparency in general\n\nSince this only happened on this system I can't give many details I just added a image (background or reference) and tried to control it's transparency\n\nThanks for your time, have a nice day.", "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 fully transparent shader is brighter when a Clear Coat shader is behind it\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.3.0 Alpha\nWorked: Never Worked\n\nWhen doing Decals, we often use alpha channel to define transparent area. However, I found when the Object's base color is above hsl(h,s,0.01), who's under the Decal, then the decal's transparent area will affect the underneath object's shading.\nMy test configuration is that 2048 viewport samples alongwith light bounces param all been set to 64.\nThe BUG is easier to notice when the background object is light grey, and the light is quite dimmed(or just turn down the exposure in colormangement to observe.)\n\n\n\n\n\nPlease open the attached Blend file to test.\n[Transparent shading BUG.blend](Transparent_shading_BUG.blend)\n\n", "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" ]

[ "Mesh becoming weirdly invisible.\nOperating system: Windows 10\nGraphics card: RTX 2060 Mobile\n\n**Blender Version** 2.90.1 \n\n\n\n.blend file car mesh opened in edit mode lookdev, once switched to shaded render mode in viewport and move to object mode the mesh becomes invisible and only the shape can be seen and few parts. After moving back to lookdev and back again to render shanded mode the mesh becomes visible correctly.\n\nAll in Cycles, no transparency shading node applied, just a normal image texture conected to roughness.", "Cycles: mesh becomes weirdly transparent after some samples CPU only\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.90.1\nWorked: 2.83.7\n\n[mesh Car becomes invisible when switch from lookdev to rendered mode in cycles, looks like the issue doesnt happen in GPU compute.\n\n1. Edit mode ,material preview\n2.Edit mode go to render preview\n3.Go to object mode from edit mode and the mesh becomes weirdly/progressively transparent (starting at ~sample 20)\n\n\n\n[Car.blend](Car.blend)\n\n" ]

[ "Active selection not updated when selecting from outline\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.4.0 Alpha[Very Long File Name For No reason.blend](Very_Long_File_Name_For_No_reason.blend)\n\nThe current latest active selection is not updated when selecting from outliner.\nSelecting mesh then bones from viewport \nSelecting mesh then bones from outliner \n\n - Open the attached .blend file\n - From the 3D viewport : Click the mesh, then shift click the bones. Press CTRL+P, you can link the bones to the mesh.\n - From the outliner : Click the mesh, then shift click the bones. Press CTRL+P, you cannot link the bones to the mesh.\n[2022-08-07 16-35-46.mp4](2022-08-07_16-35-46.mp4)\n[Very Long File Name For No reason.blend](Very_Long_File_Name_For_No_reason.blend)\n\n", "Blend file thumbnail shows the file browser\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: 3.0.0 Alpha\n\nWhen using the full screen file browser preference and saving a blend file, the thumbnail shows the file browser\n\n\n\nSet file browser to Maximized Area\n\nSave a file\nCheck the thumbnail\n\n", "Improve MemFile Undo (for general use)\n**Motivation:**\n\n- Resolve bugs where changes to data outside a 'mode' are ignored by the undo system.\n- Unify logic and reduce code duplication.\n\n**Description:**\n\nCurrently we have a blend file based undo system (internally called 'MemFile').\n\nWe could use this almost everywhere (edit-modes for example), it would be sub-optimal at the moment.\n\nThis project would involve optimizing the case when only a limited set of data-blocks change - so we can skip writing all other data-blocks into the memfile.\n\nIt may also involve using better binary diffing for `MemFile` undo (as edit-modes currently use).\n\nThis would most likely not cover image painting and sculpting.\n\n**Estimated Time:** possibly 2-4 weeks *(hard to know)*.", "Drag and drop non-blend files\nBeyond the initial feedback on [D12098](D12098), I haven't heard anything for a while; so hoping this might be the expected avenue for further discussion?\n\nI propose to extend python operators to enable them to register themselves for drag-and-drop of files from the host OS.\n\nFollowing the general Operator pattern, the registering is done through a new bl_options flag, 'DRAGDROP', and the Operator's poll and invoke functions are called as usual, but in the context of a drag-and-drop operation.\n\nThe operator's poll is called to determine if the dropped file is supported by this operator, usually by examining the filename of the dragged file, which is stored in context.window_manager.dropfile.\nIf poll returns true, the operator's invoke function is called, with property 'filepath' set to the dropped filename.\n\nThere is an existing Operator in wm.py called WM_OT_drop_blend_file which works in this way, but which has had its poll and dropbox registering hardcoded into a C file (blender/editors/screen/screen_ops.c). This proposal would remove the need to do that, and open up the ability to drag and drop other file types into blender.\n\n------------------------------------\n\nAddressing some concerns I know about:\n\n1. Could be done with planned general WM drop box support / Doesn't allow for dropping files into different views\n\nThe Operator poll/invoke mechanism seems like a good way to express dragging and dropping in any case, and registering the dropboxes for different views could be done through the Operator's bl_regiontype.\n\n2. Could be done via a planned file-type registration system\n\nI'm not sure how much file-type registration already exists in blender, but my unsolicited opinion:\nAt its simplest a filetype might be a mapping of a filename extension to read/write routines, but probably also includes what sorts of things it might contain (images, sounds, 3d meshes), some sort of import/export UI, etc., etc.\nBut why register such a thing when you can just register an Operator that can be asked if it can read a file, and can automatically load the data into the right structures in memory? A similar argument exists for saving/exporting.\nMy point is that a filetype is an ephemeral thing that exists only at the boundary of a filename and loaded data, and it's sort-of a good thing that blender doesn't have some sort of list of them.\n\n3. Multiple file support\n\nWhen you drag multiple files they can be of different types. Making a per-file determination of what Operator will be called leaves the Operators to only have to consider a single file.\nI had thought that this was already supported in blender, but in fact multiple-file dragging had been explicitly disabled. I remove that restriction with [D12159](D12159)\n\n4. Specifying import UI / choosing to merge in or load file contents\n\nAs in WM_OT_drop_blend_file, all those things can be easily done in the Operator's invoke function. This is in contrast with a filetype registration system, where these variations in behaviour would have to be somehow accounted for.\nin the case of dragging multiple files I think it would be reasonable to put up a menu or import panel on the first file and then have an option in the UI to use the same options for all subsequent files in this drag; but that would be totally authorable.\n\n\n------------------------------------\n\nI know it looks like I'm mostly just arguing for my patch as-is, and being overly pushy; but I thought it would be best to give you all these thoughts up-front, especially since we're in very different time zones.", "Filesystem accidental creations of directories\nOperating system: Windows 10 Pro (64-bit), version 1809, OS build 17763.615\nOperating system: Ubuntu 18.04.2 LTS 64-bit\nGraphics card: Nvidia GTX 650\n\nWindows Build version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: \nWindows Build version: 2.81 (sub 1), branch: master, commit date: 2019-08-05 13:33, hash: 8f1a55831c89, type: Release\nUbuntu Build version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: Release\n\nThe window pop-up asking for confirmation of a filesystem change, e.g creating a directory, seeks cursor and a click gets immediately accepted as a confirm.\n\nFile -> Open\nClick the \"file path\" area (\"C:\\Users\\%USERNAME%\\\" or similar)\nType \"C:\\Users\\%USERNAME%\\something_random\" and click in the file browser.\nResult: Created a directory called something_random.\n\nBased on the default startup nothing other than Blender needed.", "ID Management: Sanitize and clarify our ID creation/copy tags\nSome of our ID creation/copying code and flags are currently still fuzzy and not really correct, especially when changes proposed in #88555 (ID Management: Sanitize and clarify our ID tags) become real. This concerns 'out of `G_MAIN`' IDs mostly.\n\nIMPORTANT: This task is a sister of #88555 (ID Management: Sanitize and clarify our ID tags), both will be worked on together.\n\n## `LIB_ID_CREATE_LOCALIZE`\nThis ID creation flag is only used in two places, and its name is extremely confusing since it actually sets `NO_MAIN` flag, not `LOCALIZED` one. It should simply be removed.\n\n## `LIB_ID_COPY_LOCALIZE`\nShould be updated to set `LOCALIZED` flag instead of `NO_MAIN` one: `LIB_ID_CREATE_LOCAL | LIB_ID_CREATE_NO_USER_REFCOUNT | LIB_ID_CREATE_NO_DEG_TAG | LIB_ID_COPY_NO_PREVIEW | LIB_ID_COPY_NO_LIB_OVERRIDE`\n\nA new `LIB_ID_COPY_NO_MAIN` set of flags should be added with default behavior to create a `NO_MAIN` ID, probably `LIB_ID_CREATE_NO_MAIN | LIB_ID_CREATE_NO_DEG_TAG | LIB_ID_COPY_NO_PREVIEW | LIB_ID_COPY_CACHES | LIB_ID_COPY_NO_LIB_OVERRIDE` (would leave `NO_REF_COUNT` out of the default set of flags).\n\n## `ntreeLocalize`\nThis special function needs to be removed, this specific behavior should be strictly handled through calls to generic `BKE_id_copy_ex` and dedicated code in `ntree_copy_data` IDType callback.\n\nNot sure where the recursive copying of sub-trees should be handled though, either in `BKE_id_copy_ex` or `BKE_libblock_copy_ex`, in a similar way to how we deal with animation data currently, or from `ntree_copy_data`, as done e.g. for shapekeys for meshes and other obdata?\n*Would rather keep this 'localize' behavior in the `ntree_copy_data` i think, at least for now. We need a full rethink of how we handle recursive 'deep' copying of IDs anyway, current code is dodgy at best here, and often fully broken (ref. #72659 (Making 'singleuser' for a group with too smart NodeCustomGroup breaks user counters of both source and target nodes) and similar).*", "Unified object and geometry I/O handling\n## Motivation\n\nCurrently I/O for objects and geometry is primarily handled through import and exporter operators. But there are plans to extend this to:\n* Drag & drop\n* #68933 (Collections for Import/Export)\n* Geometry nodes\n* Asset system\n\nFor this we need a unified system to handle I/O for various file formats, to provide consistent functionality across these areas and avoid code duplication.\n\nIt will also make a better user interface for the import operator possible, with a single `File > Import` menu entry where you can then pick a file and see the appropriate options, without having to determine the file format first. Drag & drop similarly should be able to recognize the file type automatically.\n\n## Design Proposal\n\nAdd new `IOHandler` type that can be subclassed, similar to operators or render engines (maybe a better name can be found).\n\nIt would include:\n* List of file extensions (or method to determine if a filepath matches)\n* Method to create import / export settings\n* Method to make UI layout of import / export settings\n* Method to import a file\n* Method to export to a file\n* Method to provide metadata about file\n\nThe precise functionality needs to be determined by looking at the various use cases. But a few general points:\n* Settings:\n**Can be stored as ID properties.** Potentially the defined properties may depend on the use case, for example an import operator may have additional properties relating to how it affects the scene, compared to collection I/O which may be more local.\n* Import:\n** This could work similar to library linking .blend files. That is, importing would populate its own main database with datablocks. The operator, geometry node, assets system would then receive this main database and use, copy or link the datablocks as appropriate for each. This gives each use case more control over the ownership, and by not affecting the main .blend database there should be no side effects from running the import method.\n* Export:\n**Exporters typically export depsgraph evaluated scene data. They also have options for exporting only selections or the entire scene. There is some potential here for an abstraction that provides the relevant subset of evaluated scene data to the exporter, but the right API for this is not obvious.** On the other hand for syncing with Omniverse or other collaborative tools, the data you import and export needs to match, so then you might be exporting original scene data? This might be something we do for USD only and after the basic I/O handler is in place, it's unclear if this would be part of the same system and how it would fit in.\n* Assets:\n**Currently assets must always be datablocks from .blend files, but ideally any importable file would be indexable by the asset browsers as well. For this it's important to be able to quickly read metadata, maybe read or generate a preview image.** Being able to get the file as a set of datablocks in a database could allow reusing existing code more. Even image files could be read as an image datablock for example. However the asset system might already have plans for its own abstractions here, we need to check how it fits.", "Blender crashes on startup if a large USD file is attached to the scene\nOperating system: Windows 10, Windows 11\nGraphics card: GeForce RTX 1660 (Win 10), GeForce RTX 3060 (Win 11)\n\nBroken: 3.3.1; 3.3.4; 3.4.1; 3.5 beta\nWorked: not found\n\nThere are several Blender files created at different times. The files are scenes into which a file of the usd format is connected through the \"MeshSequenceCache\" modifier. If the usd file size exceeds a certain size, then with a high degree of probability, almost always, Blender will crash on startup.\nAt the moment, this situation occurs in the scene, to which the usd file is connected, about 1 GB in size.\nThe following method is used as a temporary solution. First, a file is launched that is either smaller or does not have a usd file attached. Then from the running program through the file-open the desired file is launched\n\nAttach a ~1 GB USB file to the scene using a modifier \"MeshSequenceCache\"\n\n", "Use aliased names for file versioning checks\nOperating system: Linux-5.0.13-arch1-1-ARCH-x86_64-with-arch 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n\nThe new angle setting of the Sun light type is not saved with the blend file. It always defaults back to 11.4°.\n\n\n- Add Sun lamp\n- change the angle\n- save the file and reopen it.\n\n\n\n", "Fast Blend File Compression\n**Motivation:**\n\nReduce size of saved files, without the slow file writing of zlib.\n\nAllowing compression to be enabled by default.\n\n**Description:**\n\nRecently there have been multiple fast compression algorithms, while some more investigation can be done (especially regarding multi-threaded compression), it looks like [LZ4 ]() would be a good candidate for our purposes.\n\n**Estimated Time:** 2..4 days *(maybe a day if there are no complications)*", "multiview: overwrite and file naming \n\n\"not overwrite\" option doesn't work with multiview when some views already exist on disk, could be a minor problem but rendering one single view with views option activated create a 0 byte \"myfile_L.jpg\" file but save only myfile.jpg\n\n\n\n\n\n", "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", "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.", "Data Transfer modifier works only for Byte Color & Face Corner color attributes\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 472.12\n\nBroken: version: 3.2.0\n\nIf a target color attribute Domain is *Vertex* or it's Data Type is *Color*, the data are not transferred.\n\n[data-transfer-color-attr-bug.blend](data-transfer-color-attr-bug.blend)\nYou can see in the attached .blend that the Data Transfer modifier is set correctly, but the Col attribute isn't updated.\nAfter doing Convert Attribute -> Domain: *Face Corner*, Data Type: *Byte Color*, it starts to work correctly.\n\n\n", "Mac (Intel) + Eeeve/Metal : Possible \"ignoring\" of the 2nd UVmap on faces\nOperating system: Macbook Pro Intel (the latest before M1)\nGraphics card: Intel Iris Plus Graphics 1536 Mo\n\nBroken: 3.6.0 (latest)\nWorked: n/a\n\n**Short Description**\nOn a Mac Intel, when using Eevee + Metal backend ; (does *NOT* happened with OpenGL backend) ;\nOn a mesh plane (mostly rectangular, representing a terrain evolution, 174 k vertices, 348 k triangles).\n\nI have 2 textures, with each its own UVmap ;\nI checked the content of the UVmap, they are correct, and I was careful to assign the correct UVmap to the correct texture.\n\nThe 2nd UVmap :\n- Eevee + Metal : seems to be \"ignored\" (and the 1st UVmap is used instead)\n- Eevee + OpenGL : works okay\n- Cycles : works okay (Cycles is not configured to use \"Metal\" since it's not a M1/M2)\n\nI think that for UVmaps, \"second\" means nothing, since there should be no particular order and/or the \"order\" is hidden from the user when using only shading \"nodes\" (except in the case of a bug being triggered...)\nEspecially since I explicitly specify the \"UVmap node\" for each \"image texture\" node.\n\nYet, the order in which I created/imported them seems to have an impact here.\n\nBy \"second\" UVmap, I mean the second material and/or second UVmap in the list of Object Data's properties UV maps.\n(Selecting another UV map in the Object Data's properties has no effect, since I explicitly specify the UV map to use in the \"nodes\").\n\n\n**Steps to Reproduce**\n- Open attached file\n- Switch to EEVEE render in viewport\n\n[bug.blend](https://projects.blender.orgattachment)\n\n| bug | no bug |\n| -- | -- |\n|  |  |\n\n<details>\n<summary> Original Report </summary>\n\nThe scene is the most simple : a mesh, and 2 materials + 2 UV maps.\nI then created an empty 3rd material, being careful to apply all faces to this 3rd material.\n\nThe shading \"nodes\" of this material is the most simple, in reverse order :\n- default \"material output\" node\n- default \"Principled BSDF\" node\n- a single \"Image Texture\" node\n- a single \"UV map\" node (of course linked UV<->Vector, and \"from Instancer\" disabled)\n\nThe 2 terrain textures which I have do not cover the same mesh area (partial overlap) :\n- One of the textures cover the whole mesh (no more, no less) : a satellite picture (an orthophoto)\n- One of the textures cover a small part of the mesh : an architect plan\nThe UV maps correctly reflects that ;\n\nWhatever Texture/UVmap I import first and then second, the second one seems to always be drawn with the UV map of the first, despite the fact that I explicitly select the second UV map.\n\nHint : If I link the UVmap \"UV\" output directly to the \"material output\" node, it seems to correctly draws the 2nd UV map colors (some square-y green + yellow + red texture, optionally some black if the texture does not cover the whole mesh).\n\nThe catch is that the problem only occurs with Eevee + Metal. It does not happened with Eevee + OpenGL nor Cycles.\n\nI would guess maybe some bug in the Metal implementation and/or Metal shaders?\n\n\nWell, I used blenderGIS to import a DEM (digital elevation map : a point cloud) + some trinagulation which yield a mesh.\nThen I used blenderGIS to import 2 terrain textures (one covering 1:1 the mesh, one way smaller).\n\nWhichever of the 2 textures I import 1st, it will always be the 2nd that has its UVmap seemingly ignored.\nNote : I checked the UV map content in the UVmap editor.\nNote 2 : I use QGIS since 2019, I made sure that the CRS (projection) are the same for all 3 datas (DEM + geotiff textures).\n\n***Based on the default startup or an attached .blend file (as simple as possible).***\n\n***My best guess***\n\nA bug in the Blender's Mac implementation of Eeveee Metal (and or /shaders) ?\n\nPlease note that my 2 textures have different coverage of the mesh, and so the UV map reflects that. Possibly the bug only occurs when it's the case.\n\n</details>" ]

[ "Auto-fill name for exported file doesn't change when opening a different file.\nWindows 7 Ultimate 64-bit\nnVidia GeForce 230m\n\nBroken: Blender 2.69.0 r60995\n\nThe filename suggested by the Blender export dialog does not change to reflect the currently opened file.\n\n* Open a .blend file and click File > Export > Wavefront (.obj)\n* Notice the filename that is suggested by Blender (same as the name of the currently open file with a different extension)\n* Click File > Open recent... > [another .blend file]\n* Click File > Export > Wavefront (.obj)\n* Notice the filename that is suggested. It will be the name of the previous file, not the currently opened file.\n" ]

[ "Insert key dropdown on keymap doesn't show keying sets anymore\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.2 Release Candidate\nWorked: 2.92\n\nwhen trying to assign a default keying set to the insert key menu, it doesnt show the list anymore just a dropdown that says default\n\n2.92\n\n\n\n2.93+\n\n\nopen blender, go to settings > keymap\nsearch for \"insert keyframe\"\nexpand the \"insert keyframe menu\" under pose mode\nclick the keyingset dropdown... all you get is default.\n", "Can't bind shortcut Alt+Numbers 0-9\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\nKeyboard: UK ISO (tenlesskey) w/ UK Layout\n\nBroken: version: 2.93.4\nBroken: version: 3.0.0 Alpha\nWorked: None (tried 1.8, 2.28, 2.34, 2.58, 2.66, 2.79, 2.80, 2.82)\n\nUnable to use Alt modifier with Numbers 0-9\n\nTry to rebind something (e.g Hide Collections to Alt+Number key).\nThe binds will fail to execute.\n\n{[F10604609](210926_blender_10b48.png), size=full}\n\nBroken:\n• Alt+Numbers 0-9\n• Alt+Numpad Numbers 0-9\n• Using 'Left Alt' as a custom modifier key in the keymap plus Numbers 0-9\n\nWorks:\nAlt+F Keys 1-24 work (unfortunately Alt+F4 is hardcoded to exit blender.exe)\nAlt+Qwerty/Punctuation keys work.. just seems like its Alt+Numbers that fail\n\nThank you for your time and consideration :3", "Toolbar hotkeys can change unintentionally\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0\n\n**Description**\nToolbar hotkeys can change unintentionally. This happens when you select tool that is not last in hotkey list and it uses character instead of number as hotkey.\n\n- New General template\n- Switch to UV editing workspace\n- Observe shortcuts for Grab - 7, Relax - 8 and Pinch tools - 9\n- Activate Annotate tool\n- Observe shortcuts for Grab - 8, Relax - 9 and Pinch tools - 0\n- Activate Select Box tool\n- Observe shortcuts for Grab - 7, Relax - 8 and Pinch tools - 9\n", "2.90 Not opening on Linux\nOperating system: Linux Mint 18.1\nGraphics card: Intel HD 620\n\nBroken: \nBlender 2.90 won't open up fully, it appears to open up and immediately closes\nWorked: \n\nTried a few different ways to open, won't open.\n\nOne of the methods I tried opening with was through the Terminal and this was the message I had returned back:\n\nRead prefs: /home/john/.config/blender/2.90/config/userpref.blend\nfound bundled python: /home/john/Desktop/3D Related/1BlenderVersions/blender-2.90.0-linux64/2.90/python\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nWriting: /tmp/blender.crash.txt\nSegmentation fault", "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 ", "Shortcuts for Tools (design task)\nOne of the major issues with the tool system, is that switching tools isn't easy enough using the keyboard with the default keymap. \n\nWe would like to introduce a way to make the keyboard shortcuts switch tools, without having to click on the toolbar, or opening menus. Here's how we think we can solve it:\n\nWe want to leverage muscle memory for shortcuts users already know, such as G, R, S for the transform tools, as well as K for Knife, Alt-S for Move Along Normals, and so on. \n\n## Leader Keys\nTo do this, we use the concept of *leader keys* (also known as *chained keys*). This makes it so that tapping (but not holding) a modifier will change the following shortcut. In this case we think we will use Alt to switch tools. \n\nIn practice, this means users will tap Alt, then G to switch to the Move tool, and so forth.\n\n## Visual Feedback\nWe want to make it obvious that a leader key has been entered, so that users know that the following key stroke will differ from normal. We do this in a few ways:\n\n**Status Bar**\nHere we can see the leader key, plus the shortcuts:\n{[F7753731](Screenshot_2019-09-15_at_21.50.34.png), size=full}\n\n**Toolbar**\nAfter the leader key is pressed, we can also display the hotkeys inside the toolbar buttons. This gives a more direct association with the tools in the toolbar and their corresponding shortcut. \n{[F7753735](Screenshot_2019-09-15_at_21.43.58.png), size=full}\n\n## Implementation\n\n- Pressing Alt and releasing (without pressing another key) would prompt for input.\n - Pressing any of the mapped keys would activate the tool immediately. \n - Pressing any key not mapped - such as painting or using mouse buttons to pan the view - would cancel the prompt and perform the action (preventing unintended leader key press from Blocking other actions). Pressing escape would also cancel.\n\n## Precedents\n\n- Firefox supports accessing menu this way (Tapping Alt, then F opens the file menu).\n- Typing in accent characters on macOS uses [leader-key like functionality. ]()\n- Spacemacs relies heavily on a [leader key ](QUICK_START.html#the-leader-keys).\n\n", "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: ", "Impossible to move with G key an object scale to 0 and parent to an empty\nOperating system: Windows 7\nGraphics card: GTX 780\n\nBroken: 3.5.1\nWorked: \n\nWhen an object is parented to an empty, and this object is scale to 0, you cannot move it anymore with the G key. But you can move it in the transform menu location.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open blend.\n2. Try to move object with G key.\n3. It is possible with Transfom menu.\n\nThanks a lot !\ndono", "Regression: Blender text editor lost support for dead keys\nOperating system: Linux-4.19.0-11-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 2.93.0\nWorked: 2.92\n\nCaused by cafd6b519c\n\n\nOn any text input field, on the Python Console, on the text editors, I cannot type any of the characters that need dead keys (I use English International with dead-keys to type English, Spanish, and German).\nI cannot, for example even type quotes, which makes Python expressions hard - let alone accents, etc. \n\nThis used to work on previous versions of Blender. The latest I found it working on is on a 2.92 release candidate I had somewhere on my hard drive.\n\n\n1. On a computer configured with dead-keys input, open the default scene\n2. Switch the main display to be a Text Editor.\n3. Press \"New\" to create a new file.\n4. Try to type \"é\" (by pressing 'e) or \"'' by typing (' space).\n\nExpected behaviour: Blender accepts the typed-in characters.\nActual behaviour: Blender ignores the typed-in characters.\n\nSomething like this gets printed to the console:\n\n```\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7f80237f2980 0x7f804905d0c0\n```", "GPencil: Hotkeys of Tools is not consistent when Draw Tool is active\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.76\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nI'm not sure whether this is intended or not.\nHotkeys (1 to 9) shift downward one by one depending on whether you are in a draw tool or not.\n\n1. Go to Draw Mode\n2. Select a draw tool by pressing Shift Spacebar, O (Not 1)\n3. Select a fill tool by pressing Shift Spacebar, 1\n4. Select a draw tool by pressing Shift Spacebar, 1 (Not O)\n\n", "Cannot use Chinese input or Japanese input\nOperating system: Linux-5.4.0-70-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.93.0 Beta\nWorked: 2.92 ([#issuecomment-224988](87578#issuecomment-224988), [#issuecomment-225000](87578#issuecomment-225000))\n\nCannot use Chinese input or Japanese input\n\nWhen I use Chinese or Japanese input, I get a warning like this on the console \n\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7fca129c0900 0x7fca36c513c0\n\n", "Modal key map item don't appear when searched in the keymap\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.36\n\nBroken: version: 2.83.0\n\n\nSome items don't appear in the keymap when searched by Name even thought they appear when scrolled in the hierarchy tree.\nI think it's only modal keymap that are not directly tie to an operator ex: View3D Walk modal, Knife Tool Modal Map\n\n\n* Default blender cube\n* Go to preferences->keymap\n* Search for \"Walk\"\n* \"View3D Walk Modal\" don't appear even thought you can find it when expand 3DView->View3D Walk Modal\n\n\n", "Different results when keyframing visual transforms and applying transforms manually on IK constraint\nBroken: v2.82a and blender-2.90-f9d0f59bed4d-windows64\nWorking: never, tested with 2.75a and that even shows this issue.\n\nThere is a difference between using the insert keyframe menu to insert Visual LocRot compared to if you Apply Visual Transform to Pose and then use normal keyframe LocRot.\n\n\n[keyframe-visual-root.blend](keyframe-visual-root.blend)\n- Open the attached blend file.\n- Set a VisualLocRot keyframe on the root bone.\n- See in the graph editor that the orientation is keyed with quaternion (1, 0, 0, 0), even though the bone was visually influenced by the IK constraint.\n- Disable the IK constraint, and see that the root bone moves.\n\n\n---------------------------------\n\nUsing Keyframe Menu (broken):\n\n[2020-05-15 11-24-58.mkv](2020-05-15_11-24-58.mkv)\n\nIterating Keyframe Insertion (Semi-working):\n[2020-05-15 12-02-32.mkv](2020-05-15_12-02-32.mkv)\n\nManually applying transforms to Pose (working):\n\n[2020-05-15 11-29-47.mkv](2020-05-15_11-29-47.mkv)\n", "Autokey keys disabled driver values\nOperating system: Darwin-17.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.27.6 378.10.10.10.20.109\n\nBroken: version: 2.83 (sub 2)\nWorked: (optional)\n\nWhen you have autokeying turned on for LocRotScale, then disable a driver (for say a shape key) and then manually tweak the value. Blender will key this change in the driver editor.\n\n- turn on autokey (keying set LocRotScale will do)\n- create a property on the default cube\n- copy as new driver\n- create a shape key\n- paste this driver to this shape key\n- then disable the curve for this driver in the driver editor (check box)\n- manually tweak the driver value and this will be keyed in the driver editor.\n\n[autokey_disabled_drivers.blend](autokey_disabled_drivers.blend)\n\n[auto_keying_disabled_drivers.mp4](auto_keying_disabled_drivers.mp4)\n\n", "Blender's search in data-blocks is case-sansitive in cyrilic letters\nUbuntu 14.04\n\nBroken: 2.73\n\nSupporting of Utf-8 characters chars in names of objects and data-blocks are not completely done. While searching, uppercase and lowercase letters in the Cyrillic alphabet are considered as different letters. \n\nHere is the test file [casetest.blend](casetest.blend)\n\n\n\n\n" ]

[ "shortcuts stop working when switching to non-latin keyboard on mac\nOperating system and graphics card\nMac os sierra 10.12.4, mac mini 2012, Intel HD Graphics 4000 1536 MB\n\nBroken: 2.78c e92f235\nWorked: (optional)\n\nshortcuts stop working when switching to non-latin keyboard\n\nI have two keyboards Latin and Russian and I am switching between them frequently, so it was a big surprise for me that shortcuts in blender stop working when I switch to Russian keyboard. It is very confusing and it doesnt work this way in other programs, so I think it is a bug.\nThis problem might be related to these problems:\nrB12c71508c2d7b719cc5cd0bf5ed79123aa38e52d\nT47228\n" ]

[ "Cycles Rendering of project causes crash of program.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Windows 11)\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\nNot sure if you need textures, can provide if needed.", "Pack UV's crashes blender\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\n\nwith all uv's selected, using \"pack uv's\" crashes blender\n\nopen provided file. Go in edit mode. Select all\nin uv editor go UV > Pack UV\n\nBlender crashes\n\n", "Render procedural crashes Blender when trying to render\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 3.2.0 Alpha\n\nRender procedural crashes Blender when trying to render\n\nLoad the attached alembic in the file, go Cycles experimental, turn on Use Render Engine Procedural and render.\n\n[Particles_BlastV_v01.abc.zip](Particles_BlastV_v01.abc.zip)\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", "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", "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n", "Script node with shader output crashes Eevee\nOperating system: OSX Monterey (12.6)\nGraphics card: Radeon Pro Vega 20\n\nBroken: git versions: blender-v3.2-release, blender-v3.3-release, master\nWorked: 3.2 release\n\nI'm testing the MaterialX standard surface shader. It seems to work when in Release versions, but in a debug build, it crashes when you connect the output of the shader to 'surface' in the terminal node.\n\nUsing the default scene, switch from Eevee to Cycles + Open Shading Language. Select the Cube, switch to Shading tab. Create a new material, and add a new Script node. Load the attached .oso file (to compile the attached .osl, you need to have MaterialX installed. I'm using 1.38.5). Attach the output of the script node to the 'Surface' input of the terminal. Boom! Where the crash occurs depends on whether your in Eevee preview, or Cycles preview.\n\n[out.osl](out.osl)\n\n[out1.oso](out1.oso)", "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```", "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks", "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", "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", "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", "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)", "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", "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```" ]

[ "Blender Crash after stopping screencast recording.\nOperating System : Ubuntu 14.04.2 LTS\n\n- Display-\nResolution\t\t: 1280x800 pixels\nOpenGL Renderer\t\t: Mesa DRI Intel(R) 915GM x86/MMX/SSE2\nX11 Vendor\t\t: The X.Org Foundation\n\nversion 2.75 (sub 1), branch b'master', commit date b'2015-06-18' b'16:56', hash b'a1e01fd', b'Release'\nbuild date: b'2015-06-19', b'11:17:04'\nWorked: version 2.74\n\n\nAfter stopping screencast recording go in crash.\n\n**below the last row of console**\n\nAppended frame 6\nClosing ffmpeg...\nFlushing delayed frames...\n[matroska @ 0xaff00500] end duration = 600\nzero video stream 0xaff00b80\n***Error in `./blender': double free or corruption (out): 0xaff00488***\nAnnullato (core dump creato)\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "3.4.1 Not Displaying GTX 1660 TI\nOperating system: Windows 10 Home 22H2\nGraphics card: GTX 1660 TI\n\nBroken: These versions do not display my GPU under CUDA/OptiX: 3.4.1, 3.4.1, 3.3.4, 3.3.3 and 3.3.2 (I was also getting Python errors when trying to install addons. (This is true whether they are installed or run from the unzipped .rar downloads.\n\nWorked: blender-2.93.15 candidate+v293.400f35914421-windows.amd64-release is the most recent version that works - everything works as it should!\n\n\nI tried uninstalling/installing the latest Nvidia game ready drivers, the studio drivers, the CUDA Toolkit (which asked for me to install Visual Studio, C++, etc... 🤦‍♂️ ), tweaking the registry settings etc... none of these things worked. \n\nOnly using the older version would detect my GPU. A user on the Discord forum asked me to run the GPU debugger in the latest version 3.4.1 and when I open the program that way, my GPU was finally showing! I sent him the error reports (I can post them below) and he said that Blender IS SEEING my GPU, it's just not displaying it for use.\n\n", "Blender Crash MacOS Arm M1 - Wireframe - Memory issue\nOperating system: macOS-12.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Pro Apple 4.1 Metal - 76.3\n\nBroken: version: 3.2.0 Alpha\nBroken: version: 3.1.2\nWorked: Any version using linux/windows\nWorked: version: 3.1.2 on Intel base Mac\n\nBlender crashes with a viewport in wireframe mode or tries to allocate ~100 GB memory when .\n\nBase: default blend file.\n\n1. Go to \"Geometry Node\" tab\n2. Create new node setup\n3. Add Mesh line node\n4. Set count to something big like 256^3 (this was my test case)\n5. Switch the viewport to wireframe\n6. Crash\n\nNote: Slower increase can lead to huge memory consumption by blender:\n\n\nExample node setup:\n\n\nSwitch to wireframe:\n\n\n", "Regression: Massive drops in Animation playback (fps) in the viewport\n```\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-fedora-36-Rawhide 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n```\n| version | VSYNC | fps solid | fps material | fps rendered |\n| -- | -- | -- | -- | -- |\n| 2.92 | off | 230 | 80 | 61 |\n| 2.93.9 (regression caused by 7f7e683099) | off | 230 | 76 | 55 |\n| 2.93.9 (regression caused by 64d96f68d6) | off | 230 | 69 | 46 |\n| 2.93.9 (regression caused by 267a9e14f5) | off | 230 | 57 | 41 |\n| 3.0.1 (regression caused by 03013d19d1)| off | 200 | 57 | 41 |\n| 3.1.2 (regression caused by d09b1d2759) | off | 110 | 57 | 41 |\n| 3.2beta (regression caused by 80859a6cb2) | off | 107 | 54 | 37 |\n\n```\nWin 10\nGTX 1070 - Studio Driver 462.59\n```\n| version | VSYNC | fps solid | fps material | fps rendered |\n| -- | -- | -- | -- | -- |\n| 2.92 | off | 223 | 143 | 85 |\n| 3.0 and Cycles-X | off | 79 | 66 | 50 |\n\n\nMassive drops in Animation playback\n\n\nI have this test scene here from the forum (unfortunately I forgot the direct link).\n[fps-performance.blend](fps-performance.blend)", "OptiX Denoiser crashes OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\nCPU: AMD Ryzen 7 1700\nRAM: 32 GB\n\nBroken: version: 2.90.0 Alpha\nWorked: unknown\n\nWhen the Viewport OptiX Denoiser is activated it crashes with the following error *\"OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources(denoiser, rect_size.x, rect_size.y, &sizes) (device_optix.cpp:850)\"*\n\nBased in the Startup File, (Reseted to Factory Settings and userpref.blend deleted):\n1. In Preference->System set Cycles Render Devices to \"CUDA\"\n2. Set render engine to \"Cycles\"\n3. Set device to \"GPU Compute\"\n4. Set Viewport Denoiser to \"Fastest (Optix)\" or \"OptiX\"\n5. Set Viewport Shading to \"Rendered\"\nERROR *(View screenshot)*\n\nOnce the error has ocurred I can't render with CUDA, even on a new file. To be able to render with CUDA I must close Blender and open it again. *View System Console Output*\n\n**Additional Info**\n\n- The error doesn't happen if the Cycles Render Devices is set to \"OptiX\"\n- This error doesn't happen in my laptop (i7 7700HQ, GTX 1050, 16GB RAM)\n- In a more complex scene blender tries to load the render kernels for a long time before throwing the error\n\n\n[system console Output.txt](system_console_Output.txt)\n[system-info.txt](system-info.txt)\n\n\n\n", "Cycles noise texture with high distortion differences between CPU and CUDA\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Quadro M4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.82 (sub 3)\nWorked: (optional)\n\nCycles appear to produce different random values for CUDA tiles and CPU tiles.\n\nOpen [TileBug_CUDA+CPU.blend](TileBug_CUDA_CPU.blend) and compare rendered view with rendered output.\nImages of the bug in isolation.\nCPU Only - Fine:\n\nCUDA Only - Fine:\n\nCPU + CUDA - Bugs out:\n\n\nIn addition, I had some even more strange artefacts in a real render.\nThe random effect is more subtle here, but it's there. But the other ones I can't really reproduce, not sure what is going on with that:\n\n\nI can't update drivers, due to other software requiring certain certified drivers. Windows 10 is up to date.", "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)", "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", "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", "GPencil: Massive slowdown when stroke number scales\nOperating system: Win10\nGraphics card: NV GTX960 / NV RTX 2080\n\nBroken: e03d78417a77\nWorked: never \n\n\nOur artist want to make \"gris\" quality characters with a lot of inner shades, and created a huge character with lot of strokes and did not break it down in sub objects.\nAlas when using \"Edit mode\" to animate the keys blender gets extremely choppy.\nIf we remove strokes situation gets better which leads us to believe that stroke/key storage is too linear or computed during motion\n\ndownload : view\ngo to \"strokes\" \ngo to edit mode\nselect hairs\nmove hairs around\nobserve any movement or undo is very choppy and slow \n\nnote :\nAs a dodge, we will try to split the character strokes in sub objects but we thought it would be important for this use case to be fixed because going back and forth in sub objects can be a time consuming and be counter intuitive for less technical artists.\nThank you so much for reading and creating GPencil.", "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", "CYCLES abnormally high graphic memory usage on RTX 4090\nOperating system: WINDOWS 11 Professional\nGraphics card: RTX 4090\n\n[blender_system_info.txt](blender_system_info.txt)\n\n3.3.1\n\nCYCLES used too much graphic memory (19GB) for a simple scene that only included 6 characters made by Character Creator 4. And \nstop rendering due to \"System out of graphic memory\" when the viewport uses cycles at the same time\n\n\n\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n- Download .blend file bellow\n- Render (key {key F12})\n- Compare VRAM of RTX 4090 vs RTX 3080\nview?usp=sharing", "Excessive RAM usage with instances that have emission material\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.3\n\nInstances with a material that contains emission use a massive amount of memory compared with those without emission.\n\nRender a scene with a number of instances (geometry nodes) that have an Emission BSDF on them and the memory usage will be significantly more than with a Diffuse BSDF.\n\nExample scene with 10000 instances of a 250k tri mesh:\n[EmissionMemory.blend](EmissionMemory.blend)\n\nDiffuse material:\n0:25, Mem: 44.7M\n\nEmission material:\n3:52, Mem: 41376.8M\n\n\n", "Blender freezes when using Texture paint or Weight Paint\nOperating system: Windows 10 Insider build19592\nGraphics card: GTX 1660Ti Max Q 6GB\nProcessor: i7-9750H\nRAM: 32GB DDR4-2666Mhz\n\nBroken: version: 2.83 (sub 11)\nWorked: Never (2.79, 2.8+)\n\nBlender freezes or stops responding when using Texture Paint or Weight Paint. Tried game ready and Studio drivers, still the same issue.\nMoreover, RAM consumption spikes up to more than 20GB. This happens when the brush size is increased and starts painting. \n\nAssigned GPU in Preferences>System>CUDA, but the GPU is been barely used.\n\n[Blender.rar](Blender.rar)", "Cycles oneAPI device\n**Tasks**\n\nFor release in Blender 3.3:\n\n- [x] oneAPI host and kernel code\n - [x] NanoVDB support\n- [x] Windows\n - [x] JIT compilation\n - [x] AoT compilation (disabled due to build times in CI)\n- [x] Linux\n - [x] JIT compilation\n - [x] AoT compilation (disabled due to build times in CI)\n- [x] User manual update\n- [x] Benchmark graph for release notes\n- [x] Wiki instructions for building\n\nFor later:\n\n- [x] Hardware ray tracing usage\n- [x] Host memory as fallback when out of VRAM\n- [ ] Hardware texture sampler usage\n- [ ] Memory sharing between devices\n- [ ] Simplify build process:\n - [ ] Ability to use SDK provided by Intel instead of building own compiler? to be reconsidered once moving to new C++11 ABI.\n - [x] Remove need to use shared library? dynamic libraries still needed but integration improved with rB7eeeaec6da33971ab7805c9a4bfd5f4e186273d1\n - [x] Faster AoT build times - partially adressed by rBdf29211eeb59f54079123e2bc82578a561431290\n\n**Compiler Build Instructions**\n\nAdditional build steps:\nFor Windows:\n1) Compile intel/llvm project (currently recommended version=sycl-nightly/20221019, later version are also supported):\n\n```\ngit clone llvm -b sycl-nightly/20221019\npython .\\llvm\\buildbot\\configure.py\npython .\\llvm\\buildbot\\compile.py\n```\nOr download prebuilded binaries from [the release page ](sycl-nightly%2F20221019)\n2) Download latest dGPU “Intel® Graphics Offline Compiler for OpenCL™ Code” from [standalone components webpage: ](oneapi-standalone-components.html) and extract it to the path of your choice.\n3) Perform Blender configuration “make …” as usual\n4) edit these CMake options (with SYCL_COMPILER_DIR=.\\llvm\\build\\install from step 1) and rebuild\n\n```\nWITH_CYCLES_DEVICE_ONEAPI=1\nWITH_CYCLES_ONEAPI_BINARIES=1\nCYCLES_ONEAPI_SPIR64_GEN_DEVICES=dg2 # available targets can be listed from ocloc compile --help\nSYCL_COMPILER=%SYCL_COMPILER_DIR%\\bin\\clang++.exe \nSYCL_INCLUDE_DIR=%SYCL_COMPILER_DIR%\\include\\sycl \nSYCL_LIBRARY=%SYCL_COMPILER_DIR%\\lib\\sycl.lib\nOCLOC_INSTALL_DIR=path of your choice\n```\n5) sycl.dll and pi_level_zero.dll from .\\llvm\\build\\install are needed at runtime and will be installed next to blender executable\n\nstep 1 is optional now it's available from win64_vc15/\n\n\nFor Linux: \n1) Compile intel/llvm project (currently recommended version=sycl-nightly/20221019, later version are also supported):\n```\ngit clone llvm -b sycl-nightly/20221019\npython ./llvm/buildbot/configure.py\npython ./llvm/buildbot/compile.py\n```\n2) Follow these steps to build the latest release of the Graphics Compiler: build_ubuntu.md and install it to ./llvm/build/install/lib/igc.\n3) adjust runpath of libsycl.so and libpi_level_zero.so: patchelf --set-rpath '$ORIGIN' *.so\n4) Follow these steps to build the latest release of ocloc: BUILD.md and install it to ./llvm/build/install/lib/ocloc\n5) Perform Blender configuration “make …” as usual\n6) edit these CMake options (with SYCL_COMPILER_DIR=./llvm/build/install from step 1) and rebuild\n\n```\nWITH_CYCLES_DEVICE_ONEAPI=1\nWITH_CYCLES_ONEAPI_BINARIES=1\nCYCLES_ONEAPI_SPIR64_GEN_DEVICES=dg2 # available targets can be listed from ocloc compile --help\nSYCL_COMPILER=${SYCL_COMPILER_DIR}/bin/clang++ \nSYCL_INCLUDE_DIR=${SYCL_COMPILER_DIR}/include/sycl \nSYCL_LIBRARY=${SYCL_COMPILER_DIR}/lib/libsycl.so\nOCLOC_INSTALL_DIR=path of your choice if it's different than ${SYCL_COMPILER_DIR}/lib/ocloc\n```\n7) libsycl.so and libpi_level_zero.so from ./llvm/build/install are needed at runtime and will be installed to ./lib. \n\n1/2/3/4 are optional since these now are available from linux_centos7_x86_64/\n", "PyGPU: Deprecate shader creation through direct GLSL code input\nWith new backends implemented (Metal, Vulkan), an alternative for creating shaders that is compatible with them was required.\n\nFor this we have [gpu.shader.create_from_info](gpu.shader.html#gpu.shader.create_from_info) and [gpu.types.GPUShaderCreateInfo](gpu.types.html#gpu.types.GPUShaderCreateInfo).\n\nBut we need to make this clear to users. So it's important:\n- [ ] a deprecate message\n- [ ] a better documentation\n\nRefs:\ngpu.html#examples\n#106304\n#107332\n\n" ]

[ "GPU memory explode since version 2.73\nWindows 7 x64\nI7 860 16gb ram\n2x Geforce GTX 670 4 gb vram\nDriver 344.11\nNO SLI ENABLE\n\nBroken: Blender 2.73 Hash : b4d8fb5\nWorked: (optional)\n\nSince the 2.73 RC and for the current, the gpu memory grows up really fast. For 142368 faces, with a diffuse material with a grey color in world, the memory grows to 1.225 Gb vram. The same scene in Octane render blender version 2.72, last version only take 120 mb of vram. I know that Octane have a good geometry compression process but here it's 10.2 time bigger than Octane. Before just be 1.25, 1.65 ratio between the two render engine. Also, scenes builded with previous version seems to be not affected by this problem, don't know why.\n\nComputing a scene in gpu mode under 2.73" ]

[ "Support previewing geometry in the viewport\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)", "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).", "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", "Viewport Shading 'Attribute' Option Broken for Instanced Geometry\nOperating system: Windows 10\nGraphics card: Nvidia GTX 2080\n\nBroken: 3.5\nWorked: 3.4, 3.4.1\n\nWhen instancing a mesh to another meshes vertices, the Solid Viewport Color Option 'Attribute' is no longer displaying the vertex color data.\n\nCreate A Sphere, and using \"Vertex Paint Mode\" Paint a color onto the sphere.\nUsing geometry nodes set up the following, Group Input (Geometry) -> Mesh to points - > Instance on points -> Realize Instances -> Output (Geometry)\nSet a simple sphere as the object to be instanced.\nSet Shading mode to 'Solid'.\nToggle 'Attribute'\n\n", "Use toolbar for Clip Editor\nAs discussed with @Sergey, here's how we would like the Clip Editor to work:\n\n{[F6943021](Screenshot_2019-04-14_at_10.06.22.png), size=full}\n\nThis makes it compliant with the other editors in Blender 2.8.\n\n\n - - [x] {icon circle color=yellow} Add toolbar to the Clip Editor\n - - [x] {icon circle color=yellow} Add Marker tool to the toolbar\n - The Marker tool lets you add markers whenever you click. The tool settings for the next marker should then be added to the tool settings\n - - [x] {icon circle color=yellow} Add Selection tools to the toolbar\n - - [ ] {icon circle color=yellow} Add Cursor tool to the toolbar\n - - [ ] {icon circle color=yellow} Add transform tools (Move, Rotate, Scale, Transform) to the toolbar\n - - [x] {icon circle color=yellow} In Mask mode, add the masking tools to the toolbar", "GPencil: Stroke not working with Holdout\nOperating system: Windows 10\nGraphics card: GeForce GTX 970\n\nBroken: 2.82a, as found on the splash screen\nWorked: Never\n\nSetting a collection as holdout in view layer options in cycles works as expected on grease pencil objects in the viewport render preview, but does not work on grease pencil objects when rendering. The entire grease pencil object is visible in the renders, whereas in the viewport render preview the parts of the grease pencil obscured by foreground objects set to holdout is alpha. \n\nCreate a grease pencil empty behind the startup cube. \nDraw some stuff. \nPut the startup cube in a collection and set the engine to cycles. \nFrom the view layers options for the new collection containing the startup cube, set it to holdout. \nTurn on render preview from the viewport shading options. Notice that the cube is invisible, along with the parts of the grease pencil that had been obscured by the cube.\nPress F12\nNotice in the rendered image that all of the grease pencil is visible, even the parts we had expected to be alpha masked from the startup cube holdout.\n\nSee the attached blend file.\n[HoldoutTrouble.blend](HoldoutTrouble.blend)\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", "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", "Highlight active item in pop-up menu (eg: Editor Type)\nCurrently the only way for newcomers to learn what is the currently chosen Editor in an Area is to compare the icon in the Editor Type combo-box with the list of icons when the combo box is open (it's not something that long time users think about).", "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", "custom brushes icon won't show up is some cases\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\n\nIn some cases the custom icon of the brushes won't load properly. Even by reassigning it it doesn't work.\n\nOpen the attached file and try to assign the accatech custom icon to the active brush (but anykind of image won't load)\n\nThankyou\n\n\n\n[icon.blend](icon.blend)", "viewport problem\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\n\nwhen I move inside the viewport, some objects become hidden.\n\n", "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", "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" ]

[ "Can't \"Copy Data Path\" of the viewport visibility\nBroken: blender 2.8\nWorked: blender 2.79\n\nIn the outliner, right clicking on the eye doesnt give the same options as right clicking on the camera or the arrow. im trying to get to \"Copy Data Path\" for the viewport.\n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "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", "Crushed Velvet Eevee render problems in Cycles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: \n- 2.93.0 Alpha\n- 2.82 (sub 7)\nWorked: ?\n\n\nThe *Crushed Velvet* material from the *Material Library* does not render properly with Cycles when setting the device to *GPU*.\n\n- Load the simplified material attached below\n- Set the render device to *CPU* and render. The output should be all black\n# Set the render device to *GPU* and render.. Depending whether you have only GPU(s) activated in the preferences or also CPU(s) you should see one of the following. When only GPU(s) are enabled you should get a proper render. When CPU(s) are also enabled you should get dark render tiles that are rendered on the CPUs.\n\n[VelvetTestSimplified2.blend](VelvetTestSimplified2.blend)\n\n---\n\nOriginal description:\nI'm attaching the .blend file I used to test this issue. I'm not even sure this is a bug or simply me not being overly familiar with materials yet, but it feels like a bug. An dit may be a Blender bug and nothing to do with this add-on. Obviously, this material renders fine in Eevee, but it also renders fine in Cycles when using CPU to render, but has major artifacts when using GPU to render. I've attached a render to show what I'm getting in case you don't experience it.\n\nThe steps I took to get here are, \n\nBasically, I have a default scene I use to do my modeling or as a start point. It's very basic. I was experiencing this issue in another project I was working on and noticed it went away when I changed the material on one object. \n\n- I loaded up my basic start file\n- selected the sphere\n- Scrolled down to the Material Library VX panel in the Material Properties tab\n- Loaded the Sample Library\n- Chose the Crushed Velvet Eevee material and clicked Apply to Selected\n\nThat's it. I had initially thought it was simply a problem rendering in Cycles but for my first render, I forgot to switch from CPU to GPU and noticed it rendered fine. So I did a few more tests and it renders fine with CPU every time, but not with GPU.\n\n[VelvertTest.blend](VelvertTest.blend)\n\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", "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 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", "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?", "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)", "Mirror painting error\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", "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", "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)", "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", "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", "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", "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", "Segmentation fault (core dumped) when opening render folder during rendering\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.105.17\n\nBroken: version: 3.6.0\n\nSegmentation fault during rendering. It happens after some frames. Sometimes 5 sometimes 100. Heavy use of OSL shaders.\nIt might get triggered when using nautilus filebrowser and open the folder which contains the rendered frames during rendering. Just opening the folder seems to trigger the segmentation fault. Crash.txt file is empty.\n\nIt happens when rending animation. I tried without GUI in comannd line and got the same error.\n\n" ]

[ " Radeon RX5xx: Computer freezes/crashes when user performs actions in Viewport during rendering in Blender 2.90\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61\n\nBroken: version: 2.90.0\nWorked: 2.8x (did not have this issue wit versions < 2.9)\n\nWhen rendering with Cycles and doing actions in parallel like changing Viewport Shading from \"Material Preview\" to \"Rendered\" (while using Cycles), or even only moving around the rendering window, Blender either freezes completely (but stoppable via Taskmanager) or crashes the whole machine. Symptoms are different. Sometimes screen flips between full black and full white. Sometimes it is possible to still access the Taskmanager, but in some cases also mouse freezes and only pressing the power button can bring the system up again.\n\n- Set Viewport Shading to \"Material preview\"\n- Press F12 to start rendering\n- Set Viewport Shading to \"Rendered\"\n- Move around the render window with the mouse\n\nNormally the issue is reproducible a after a view seconds. Sometimes its even enough just to press F12 and move the window. It looks like the issue does not happen that offen when I remove some of the textures (also attach in the zip), but it doesn't look like a specific texture causes the issue.\n\nEven when I'm able to stop the hanging/crashed Blender process it looks like something with the display driver is broken permanently after restarting Blender the issue is back immediately. When I then reboot the machine, it takes a little bit longer until I can reproduce it.\n\nI also saw the attached image of the menu (with a lot of green little dots). Minimizing/maximizing the Blender Window did not help in this case to restore the menus.\n\nMy machine 0,5 years old thus a very new system with a Radeon RX570. I can't reproduce the issue with a simple cube (incl. a material). It also doesn't matter when changing the number of threads in use to a fixed number (lower than 12, which is the maximum of my CPU). In case I set it to a very low number e.g. 1-3 it even seems to get worse. The issue than appears nearly immediately.\n\nIf you need additional information, let me know. I really love version 2.9 and the new features. Would be really great if you could find and fix this annoying issue or even let me know if there is a good workaround.\n\nThanks & Regards,\nBernd\n\n[Crash Example.zip](Crash_Example.zip)\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n[2020-09-08 10-34-46.mkv](2020-09-08_10-34-46.mkv)" ]

[ "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", "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", "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", "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", "AMD: Rendering Instances On Points using a Collection crashes Blender on Linux\nBroken\nOperating system: Linux-6.2.0-060200-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 580 Series (polaris10, LLVM 15.0.7, DRM 3.49, 6.2.0-060200-generic) AMD 4.6 (Core Profile) Mesa 23.1.0\nversion: 3.5.1\n\nBroken\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\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\nversion: 3.5.1\n\nFine (same system as above, but using nvidia)\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\nversion: 3.5.1\n\n\nOn Linux, using Geometry Nodes to have a Collection Info node feed instances of like items to an Instance on Points node going to Group Output will work properly, but will crash Blender when Rendering.\n\nDoing the obligatory Donut Tutorial. When creating the sprinkles using the Collection Info node to feed Instance on Points will create a nice set of sprinkles. The sprinkles share a Linked Material to randomize colors. Using Render Preview in the Layout (or Shading) tab correctly displays randomly colored sprinkles. However, actually rendering crashes Blender. Using the Realize Instances geometry node before the Output node will allow it to render, but then every sprinkle has a single, random color.\n\nReproduce (using Linux): \n1. Using the attached file, render using the Realize Instances node on the Icing's Geometry Nodes (file's current setup). Blender will not crash, but all sprinkles have same color. \n2. Remove the Realize Instances geometry node, and the sprinkle colors will be properly randomized. Render, and blender will crash.\n\nWarning: This is a hard system freeze, not a simple Blender crash. Typically requires a system reset to recover.\nUpdate: AMD graphic cards only. Eevee rendering only.", "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)", "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", "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", "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", "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 when duplicating and \"Use Clump Curve\" is turned on for hair particles\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 497.09\n\nBroken: version: 3.1.0 Beta\n\nA crash occurs when a curve guide force field is applied and \"Use Clump Curve\" is turned on. Doing this then duplicating the object crashes Blender.\n[blender_puASiznJH9.mp4](blender_puASiznJH9.mp4)\n\nFrom Default Start up\n1. Create Hair particle on cube\n2. Create curve, and add \"Curve Guide\" force field\n3. In Hair particle settings, turn on \"Children: Simple\" and \"Use Clump Curve\"\n4. Attempt to duplicate cube. It should crash here\n\nFrom attached:\nJust turn on \"Use Clump curve\" then duplicate. \n[haircrash.blend](haircrash.blend) \n\n\n\n\n\n", "Blender 2.8 and 2.81 (ab519b91b2c4) has high chance of crashing when using Python to create a new node-tree link.\nOperating system: Windows 10 (x64) v1903 Build 18362.356\nGraphics card: Nvidia GeForce GTX 1060 6GB\nCPU: Intel Core i5 7600K\n\nBroken: 2.81-ab519b91b2c4 **AND** 2.80 release\n\nCreating a new node-tree link via Python sometimes causes Blender to crash with the error \"EXCEPTION_ACCESS_VIOLATION\".\nI have attached a .blend file that will cause the crash, just by clicking \"Run Script\" once or twice. \nWhen I found the bug, I spent some time making the script as small as possible while still causing the crash, so the script is less than 30 lines.\n\nI also installed Blender 2.81-ab519b91b2c4 on a Windows 10 laptop that had never seen Blender before, and the bug was present on there too, so I'm confident the issue isn't specifically due to my hardware.\nI've also included blender_debug_output.txt and blender_system_info.txt, generated by the blender_debug_log.cmd file included in the Blender 2.81 download.\n\n1) Open the attached .blend file.\n2) Click \"Run Script\" in the bottom right of the text editor pane.\n3) Repeat 2 until crash (should only take 1 or 2 tries)\n\n[Crashy crash.blend](Crashy_crash.blend)\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "Dropbox saving errors with compressed files\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 3.1.0 Alpha\n\nSaving compressed blend files on a Dropbox folder gives sporadical saving errors\n\n\nSave a compressed blend file on a Dropbox folder\nIf it doesn't give you an error keep pressing Ctrl+S\n\n*Notes:*\n*Tested on Windows with the official Dropbox app*\n*Save versioning is completely disabled*", "Crash when multiple materials are assigned to a mesh\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.1 Release Candidate\nWorked: unknown (I haven't opened the .blend file in versions older than 3.2. It is broken in 3.2)\n\nWhen two materials are assigned to the mesh, random faces disappear and reappear when switching between Object and Edit modes. After switching back and forth several times, Blender crashes. In some instances it took significantly more switches from Edit mode to Object mode and back before Blender crashed. In some of these instances, Blender appeared to create new faces with one or more vertices at the object's origin.\n\nWhen transforming any vertex, edge, or face, Blender quickly generates new faces with at least one vertex at the object origin and crashed shortly thereafter.\n\nI posted a 30-second video of the issue (including two crashes) here: strange_face_artifacts_causing_crashes/\n\nThankfully, I have not reproduced this issue in any other .blend file.\n\n1) Open the attached file, \"Crash - random faces.blend\" and you will see the mesh has a number of holes in it.\n2) Press tab and the missing faces will reappear but other faces will disappear. Pressing tab additional times eventually results in Blender crashing.\n3) Select any vertex, edge, or face and transform the selected element using G, S, or R and new faces will appear. Blender will quickly crash.\n4) Reducing the number of material slots to one appears to fix the problem (all faces are visible as normal) but it reappears as soon as a material is assigned to the second slot.\n\nThank you very much for your time.\n\n[Crash - random face orientation.blend](Crash_-_random_face_orientation.blend)\n", "OpenImageDenoise crash / computer restart\nOperating system: Windows 10 (x64)\nGraphics card: GTX970\n\nVersion 3.0.0\n\n\n**Finish rendering when Denoise processing should take place, the computer restarts. This happens with the Cycles rendering on the GPU, when the \"Use nodes\" checkbox is checked in the \"Composting\", and the \"Denoising Data\" checkbox is unchecked on the right panel. Regardless of the scene, be it a simple cube or a complex scene like 512 or 1024 samples, the PC always reboots at the end.**\n\n\nПод конец рендера когда должно происходить обработка Denoise, происходит перезагрузка компьютера. Происходит это с рендером Cycles на GPU, когда в \"Composting\" включена галочка \"Use nodes\", а на панели с права отключить галочку \"Denoising Data\". Независимо от сцены, будь то простой куб или сложная сцена, например 512 или 1024 семпла, всегда в конце происходит перезагрузка ПК. \n\n\n\n**I attach a screenshot of the settings and the scene file itself.**\n\n\nПрикрепляю скриншот настроек и сам файл сцены.\n\n[Bug.blend](Bug.blend)\n\n" ]

[ "Blender closes/crashes unexpectedly \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 511.79\n\nBroken: version: 3.4.0\n\n\n\nThere are no exact steps that the bug happens, since 3.3 included, I have had blender just unexpectedly close. It is not that it freezes and becomes not responding, but as I am working and it suddenly closes. I have settings to save my progress but for some reason when this happens it just rolls back way before, disregarding the automatic saving. I don't know if maybe therte is something wrong with my setup or it is a bug, but it's so annoying and frustrating. Let me know what I can do to help discover the issue and fix it. I thought it would be better with 3.4 but the same things happen. \n\n", "Blender Crash all the time\nOperating system: Windows 11\nGraphics card: 3070Ti\nCPU: R 9 5900X\nRam: 32 GB\n\nBroken: 3.3.0\n\nWorked: Never worked in this new pc\nI m just working and it just closes no erro msg or anything, this can happen when I do simple task like rename a object or changing viewport for exemple...\n\nCan literally happen whenever it feels like it so I can select vertice, change viewport or more complex work like physics or rendering\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)", "blender randomly closing after upgrade to 3.4\nOperating system: windows 11 pro 22h2 \nGraphics card: NVIDIA geforce rtx 3080 noctua edition\n\nBroken: 3.4.1\nWorked: 3.3\n\nso when I' m working on something my render randomly closes\n\nI just work in this file [spider ding.blend](spider_ding.blend) and it just randomly closes without me doing anyhing", "Crashing when using snapping with Ctrl\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.2.2\n\nLots of times I use ctrl (and drag the vertice to the location) Blender either freezes momentarily and then starts snapping normally or crashes. When it doesn't crash it stops freezing as I do more snapping after.\n\nHappens randomly and usually on more complex meshes. The video shows it crashing on a simple mesh (the video ends when it crashes. At that point I basically started moving a vertice and pressed Ctrl to activate snapping).\n\n[Blender [C__Users_NPC Tech_Google Drive_Think Tank Classes_200 3D MODELING_BLENDER_Youre_Alive_v65-blend] 2022-08-23 16-16-53.mp4](Blender__C__Users_NPC_Tech_Google_Drive_Think_Tank_Classes_200_3D_MODELING_BLENDER_Youre_Alive_v65-blend__2022-08-23_16-16-53.mp4)\n\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", "Crash so often when modeling\n\nOperating system: Window 10 pro\nGraphics card: NVIDIA GeForce RTX 3060\n\n\nBlender Version\nBroken version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: 55485cb379f7\nWorked: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc\n\n\nWhen modeling, often crash like every 10-15minutes. \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n" ]

[ "Texture paint in viewport is not using the color space of the image.\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\nIf you paint a noncolor texture like a normal map, painting it directly in the 2D image correcly uses the non-color space, but painting in the viewport doesn't.\n\n\n- With any non-color texture, try to paint both in viewport and in the 2D image\n[2022-02-15 10-34-07.mp4](2022-02-15_10-34-07.mp4)\n\nAditional note: This seems to happens when you sample from the 2D image. By contrast, if you sample the color from the 3D view, you can correctly paint on it, BUT in the 2D viewer the color becomes brighter.", "In orthogonal view, XYZ axis overlay toggle doesn't work with axis aligned views\nBroken: 2.8x\n\nIn orthogonal view, XYZ axis overlay toggle doesn't work\n\n- press numpad 1/3/7\n- toggle xyz axis from overlays panel, they won't hide.\n\nVideo: [F8571714](2020-06-02_20-18-29.mp4)", "Tangent node used as a vector on Texture Nodes yields nothing through a Bump Node\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nIf you plug a tangent node into any procedural noise texture as the vector, it will work, however once you plug the result into a vector bump node it will draw as an empty bump map. \n\n1. In the shading workspace, grab a noise texture\n2. Grab the tangent node and plug it into the noise textures vector input. Any tangent mode will do fine (x,y,z)\n3. Grab a vector bump node and plug the noise texture into height. \n4. View the resulting bump, nothing will be yielded (however if plugged into the normal input it will)\n[Example.blend](Example.blend)\n", "Using another Mesh for Texture Indices (Texture Space / Generated Texture Coordinates)\nOperating system: Windows 10\nGraphics card: Geforce GTX1060\n\nBroken: 2.80.74 and 2.91.0 Beta\nWorked: Blender 2.79b Date: 2018-03-22 14:10 Hash: `f4dc9f9d68b`\n\n\nThe option \"Texture Mesh\" in the \"Texture Space Panel\" of the \"Object Data Properties Tab\" has no effect if the mesh does not have a deform type modifier.\n\n|\n| -- |\n|File is [here ](GeneratedTextureCoordinates4.blend?dl=0).\n\n\n- Open attached file - (Note that the geometry of one mesh affects the texture coordinates of the other)\n- Go to the modifiers tab and disable or delete the modifier\nTexture Mesh has no effect.\n[texspace_texture_mesh_bug.blend](texspace_texture_mesh_bug.blend)", "Support modal axis & user/local space switching for the shear tool\nCurrently the shear tool doesn't support setting the axis XYZ, Local/Global etc. As translate or scale do.\n\nInternally this is supported (the gizmo can do this), however there is no way to access this functionality using keyboard shortcuts.\n\nNote that some design is needed for this task since shear has a secondary axis - unlike most other transform modes.\n\nThere will need to be a key assigned to cycle between the secondary axis too.\n\nSee: blender/blender-addons#73879 (custom property values not setting correctly via code)", "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", "UI Themes: Grid color affecting axis color\n2.81a, 2.82 Beta.\n\n**Description**\nIn 3D View, the grid color overlays the XYZ axis colors, so it's impossible to set the colors I want to the XYZ axis. \nThis even happens if the grid color is set to transparent.\n\n[0020-1556.mp4](0020-1556.mp4)\n\n- Go to preferences -> Themes -> User Interface -> Axis & Gizmo Colors\n- Change X and Y axis color to black RGB(0, 0, 0)\n- Go to preferences -> Themes -> 3d View\n- change Grid color/alpha.\n\nX and Y axis color will be affected", "alt brush doesn't work in image editor -> paint\ni think this should be fairly easy to reproduce so i wont bother sharing system info. i was able to reproduce this on 3.3.0 and 3.3.1.\n\nalt brush doesn't work in image editor -> paint\n\ni have a different colour on my brush but when i press ctrl and try to paint the primary colour is painted onto the canvas", "ops.paint.image_paint() crashes blender with brush texture\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.1\nWorked: unknown\n\n\nWhen using bpy.ops.paint.image_paint() in a addon and use a brush texture, blender crashes on the first stroke with a EXCEPTION_ACCESS_VIOLATION\n\n\n\n1. load the paintstroke addon \n```\n {F10253953}\n```\n\n2. load the blend file\n[paint_crash.blend](paint_crash.blend) \n3. go into texture paint mode\n3. make sure the brush texture is assigned\n\n4. paint on the object with (LEFTMOUSE)\n5. crash\n\n\n**addon code:**\n\n```\nbl_info = {\n 'name': 'paintstroke',\n 'description': 'Paint Material image channels at once',\n 'author': 'Daniel Grauer',\n 'version': (2, 0, 0),\n 'blender': (2, 92, 0),\n 'location': \"View3D > Sidebar > Edit Tab\",\n 'category': 'Image Paint',\n 'wiki_url': 'blender_Material_Brush',\n}\n\nimport bpy\nfrom bpy.utils import register_class, unregister_class\nfrom bpy.types import Operator, Brush\n\n \nclass PaintStroke(Operator):\n '''paintstroke'''\n bl_idname = \"paint.paintstroke\"\n bl_label = \"paintstroke\"\n bl_options = {'REGISTER', 'UNDO'}\n \n \n @classmethod\n def poll(cls, context):\n return bpy.ops.paint.image_paint.poll()\n \n def modal(self, context, event): \n #print(\"MB keybinding test modal\")\n if event.type in {'MOUSEMOVE'}: \n brushstroke = {\n \"name\": \"defaultStroke\",\n \"pen_flip\": False,\n \"is_start\": False,\n \"location\": (0,0,0),\n \"mouse\": (event.mouse_region_x, event.mouse_region_y),\n \"pressure\": 1,\n \"size\": bpy.context.tool_settings.unified_paint_settings.size,\n \"time\": 0,\n \"mouse_event\": (0.0, 0.0),\n \"x_tilt\": 0,\n \"y_tilt\": 0,\n }\n stroke = [brushstroke] \n bpy.ops.paint.image_paint(stroke=stroke, mode='NORMAL') \n\n elif event.value in {'RELEASE'} or event.type in {'ESC'}:\n return {'FINISHED'} \n return {'PASS_THROUGH'}\n \n\n def invoke(self, context, event):\n if event.type in {'LEFTMOUSE'}: \n #self.paint(event) \n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n \n\nclasses = (\n PaintStroke, \n )\n\n\naddon_keymaps = []\n\ndef register(): \n [register_class(c) for c in classes]\n \n # Keymapping\n kc = bpy.context.window_manager.keyconfigs.addon\n km = kc.keymaps.new(name=\"Image Paint\", space_type='EMPTY', modal=False)\n kmi = km.keymap_items.new(\"paint.paintstroke\", type='LEFTMOUSE', value='PRESS', shift=False, ctrl=False , alt=False)\n kmi.active = True\n addon_keymaps.append((km, kmi))\n \n\ndef unregister(): \n # remove keymaps\n for km, kmi in addon_keymaps:\n km.keymap_items.remove(kmi)\n addon_keymaps.clear() \n \n [unregister_class(c) for c in classes]\n \n\nif __name__ == \"__main__\":\n register() \n```\n", "Missing viewport update after creating texture with canvas menu (sculpt mode, paint tool)\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nMissing viewport update after creating texture with canvas menu (sculpt mode, paint tool)\n\n- set viewport shading to `Material Preview`\n- Select cube\n- go to sculpt mode\n- select paint tool\n- open canvas menu\n\n- create new material slot texture with a certain color\n- result: \"Compiling Shaders 1\" in the viewport statistics top left, but this never finishes, update (incl. seeing the actual texture on the cube) only takes place after interaction with the viewport (rotating, zooming, doing an actual paint stroke)\n\n", "Impossible to use any other mouse button than MMB to navigate in Knife tool mode\nOperating system: Windows 10\nGraphics card: GTX1080Ti\n\nBroken: 2.8 latest master\nWorked: Probably never\n\nThe way Knife tool mode is executed makes it impossible to navigate 3D viewport in the Knife tool mode as long as navigation buttons are mapped to any other key than middle mouse button (MMB). This does not interfere with default Blender kemap, where Orbit (Rotate), Pan and Zoom viewport navigation actions are mapped to MMB, but doesn't allow viewport navigation in the other custom keymaps, including the proposed industry compatible one: T54963 \n\nThere is no combination of settings in Knife Tool Modal Map section which would allow to solve this issue and make non-MMB based viewport navigation function in Knife tool mode.\n\n\n1, In factory default setup Blender, got to edit mode of the default cube, activate Knife tool using K key, and notice MMB to orbit, Shift+MMB to pan and Ctrl+MMB works.\n2, Go to User Preferences, Keymap section, and in 3D View>3D View (Global) \n3, Change Rotate View from Middle mouse to Alt+Left Mouse and change the action type from \"Press\" to \"Click-Drag\" (To distinguish from Alt+LMB click, which selects edge loops)\n4, Change Zoom view from Ctrl+Middle Mouse to Alt+Right Mouse\n5, In 3D viewport, notice that Alt+LMB and Alt+RMB work correctly to activate Viewport Rotate and Viewport Zoom respectively\n6, Enter Knife tool mode, and notice that Alt+LMB and Alt+RMB do not work to Rotate or Zoom the viewport.\n7, In Keymap editor, under 3D View>Knife Tool Modal Map, notice there is no possible setup to make these new navigation hotkeys work.\n\nResult: There is no way to configure Knife Tool Modal Map so that viewport navigation in Knife Tool Mode works with any other mouse buttons than MMB.\n\nExpected: It is possible to configure Knife Tool Modal Map so that it works with non-MMB based viewport havigation configuration.", "Undo in Sculpt Mode\n\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.90.1\n\nWhen I apply undo in sculpt mode it applies to my previous settings as well (symmetry activation, some of brush settings and any settings in sculpt mode). \nThis is so annoying moment please help with it?\n\n", "Wireframe not visible with X-ray in weight paint mode.\nOperating system: Win10\nGraphics card: GTX 1070\n\nBroken: 3.0.0\nWorked: 2.93.6\n\nWireframe on other side of mesh can't be seen through faces when x-ray is enabled.\n\n[#94704.blend](T94704.blend)", "Weight paint issue with brush Accumulate option\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 use weight paint with option Accumulate, turn on symmetry, artifacts appear on the axis of symmetry\n[test.blend](test.blend)\n\n\n[EnrLS0nY4n.mp4](EnrLS0nY4n.mp4)\n", "Selection not transfering to paint mask (vertexpaint, weightpaint, texturepaint) when a triangulate modifier is present\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.81\n\nBroken: version: 2.92.0\nWorked: -\n\nIf you face select on edit mode, it will carry your selection to weight paint face select or texture paint face select or etc.\nBut if you have triangulate modifier on it will not carry it over.\n\nI did not know this and there was not error message about this anywhere on blender.\n\nLoad this file: [faceselect001.blend](faceselect001.blend)\nyou see some faces selected with triangulate modifier on.\ngo to weight paint or texture paint and you see none.\n\nI know this might not be a bug but how software works BUT for a common artist, at least adding a message that it will not carry over selection would have been nice, or disabling triangulate on view automatically when you go to those modes.\n\n" ]

[ "3D View orbit navigation widget doesn't work in paint modes\nOperating system: Win 10\nGraphics card: Geforce 1070\n\nBroken: Blender 2.80, hash: fee600f47980\n\n\nSculpt navigation widget don't work\n\n1KLrl5k.gifv", "Compass/ Gimbal not working with a pen in sculpting mode \nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Intel(R) HD Graphics 615 Intel 4.5.0 - Build 23.20.16.4974\nDevice: Microsoft Surface Go tablet \n\nBroken: version: 2.80 (sub 74)\nWorked: unknown \n\n\nwhen in sculpting mode you can't use a pen (surface pen) to rotate the camera (using the gimbal) l note this as a bug because you can rotate the camera in this way when in object and edit mode\n\nenter sculpt mode and try using a surface pen to rotate around using the compass/ Gimbal\n\n" ]

[ "Laucnh error since version 3.4\nOperating system: High Sierra 10.13.6\nGraphics card: ATI 6970M 2 GB RAM\n\nBroken: (example: 3.4 and 3.4.1 2022-12-20, master)\nWorked: (Blender 3.3.1)\n\nWhen I launch blender a get this error that I have found others on the web reporting also on similar setups:\nError opening window.\nFailed to create metal device for offscreen GHOST Context.\n \n\nPrevious versions worked a charm and I really hope 3.3.1 wont be the last version for my humble setup.\n\nThanks and as always appreciate your amazing work!", "Crash on render on some of the frames\nOperating system: Linux-4.4.0-154-generic-x86_64-with-debian-stretch-sid 64 Bits\n8x Tesla V100 SXM2 NVLINK Accelerator Cards\nDual XEON Scalable 4208 CPUs\n192 GB RAM\n\nBroken: version: 2.82 (sub 7)\nI also tested recent 2.83 build\n\nBlender crash when it renders scene frames from 346-639, the rest of the frames are fine.\nIt crashes for CPU anf GPU as well.\n\nIn order to render above frames I workaround the assert:\n\n```\n--- a/intern/cycles/kernel/kernel_compat_cpu.h\n+++ b/intern/cycles/kernel/kernel_compat_cpu.h\n@@ -74,8 +74,10 @@ CCL_NAMESPACE_BEGIN\n template<typename T> struct texture {\n ccl_always_inline const T &fetch(int index)\n {\n- kernel_assert(index >= 0 && index < width);\n- return data[index];\n+ //kernel_assert(index >= 0 && index < width);\n+ if (index < 0) return data[0];\n+ else if (index >= width) return data[width];{F8410049}\n+ else return data[index];\n }\n #if defined(__KERNEL_AVX__) || defined(__KERNEL_AVX2__)\n /* Reads 256 bytes but indexes in blocks of 128 bytes to maintain\n```\n\nThe scene is complex and I couldn't make it very simply and narrow the problem.\nPlease find the scene attached.\n\n[animation_002_02_part01.blend](animation_002_02_part01.blend)\n\n1. Open Blender 2.82\n2. Open attached scene\n3. Set frame 346, start render (F12)\n4. After one minute or so it will crash\n\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)", "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.", "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>", "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", "Fix big LIghtCache restriction\nAs reported in #78529 saving big lightcache is impossible due to blocksize restriction.\n\nFor now we restrict the lightcache size that can be written to disk but it would be better to slice the huge textures to avoid such limitation.\n\nHowever this needs some refactors in GPUTextures namely the need of a properly exposed `glTexSubImage2D` and `glTexSubImage3D`.", "Blender crashes after GPU spike (Specially when we have a character with Rigify)\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: 3.4.1\nWorked: 3.3\n\nEvery time I'm working in Blender, after 2 minutes if I start to move around on a rig made based on Rigify, or work on geometry nodes, Blender Crashes. It happens even faster if I'm working in eeve.\n\n- Open a blender file\n- Import a character using rigfy with Linked Library\n- Library override\n- Turn Eeve on\n- Start working\n- Eventually, blender will crash.\n\nI noticed that if I don't import a character with rigfy, it doesn't have the GPU spike\n[Christmas.crash.txt](Christmas.crash.txt)\n[KalyAndAkrasiel 3.5.crash.txt](KalyAndAkrasiel_3.5.crash.txt)", "Viewport rendering bug : unable to make the render progress (infinite calculation)\nOperating system: Windows 11\nGraphics card: RTX 3090\n\n**3.0.1**\n\nI installed the latest studio drivers for the graphic card (28 january 2022 version), and then :\n\nI encounter a really strange bug when using the viewport rendering (with or without denoising) on some projects. This bug only happens on this new computer, not on my iMac.\n\nDescription : it's like the viewport rendering \"never stops\" and fails to progress. I see the object, but in the \"worst\" rendered version only. It doesn't progress at all and I can hear the graphic card working infinitely, trying to calculate it.\n\nThe bug is present both using CUDA and Optix. Notice that normal rendering works really fine.\n\nUPDATE : The bug is also present with an old version of the studio drivers.\n\nBlend file : [realistic-atom-1.blend](realistic-atom-1.blend)\n\n", "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", "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`", "Problems due to leftover Nvidia drivers\nOperating system: Windows 11 Home\nGraphics card: Intel Arc a770 16gb Limited Edition (latest drivers)\n\nBroken: (Blender 3.3, 3.5 and 4.0) Trying to work out if it is just my GPU that is the issues\n\n\nBlender 3.5.1 will not allow me to access editor preferences, and won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 3.3 allows me to access editor preferences, but still won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 4.0 allows for editor preferences, same issue with Cycles. Eevee works fine.\n\nBy not allowing me to access editor preferences or Cycles I mean it crashes.\n\nI have tried to converse with Intel engineers with a video of the crashes but they seem incompetent with knowing how to enable GPU rendering in their own tests.\n\n", "Custom render engine is unable to create gpu context\nOperating system: Linux-5.19.17-2-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon Graphics (renoir, LLVM 14.0.6, DRM 3.47, 5.19.17-2-MANJARO) AMD 4.6 (Core Profile) Mesa 22.3.1\n\nBroken: version: 3.5.0 Alpha\nWorked: Blender 3.4\n\nUnable to perform background rendering using `gpu` module in custom render engine.\n\nRun the script in background mode: `blender -b -P background-gpu.py`. Blender throws: `SystemError: GPU API is not available in background mode`, despite the line `bl_use_gpu_context = True` in custom render engine. Worked perfectly fine in blender 3.3 and 3.4. Not in 3.5 though.\n[background-gpu.py](background-gpu.py)\n\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\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" ]

[ "Rendering with Volume Absorption aborts with CUDA Error\nXPS 15 9560\n\n**Operating system and graphics card**\nWin 10 / GTX 1050\n\nOfficial 2.79 Release and 2.79.0-cacba95\nBroken: both\nWorked: negative\n\nHere on the XPS and a Ryzen Threadripper with GTX 1080Ti the render of the attached scene will be stopped with a CUDA error:\nLaunch failed in cuCTXSynchronize(), line 1762\n\nDisconnecting the Volume Absorption node will fix this. Conclusion: Volume Absorption is broken. \n\nLoad the attached scene and press F12 for render.\n\n\n\n\n\n[Trans_Fluor_NoVol_v01.zip](Trans_Fluor_NoVol_v01.zip)\n\n[RB0112_6981_Arial_Intruder_v03.zip](RB0112_6981_Arial_Intruder_v03.zip)" ]

[ "Crash creating \"position\" attribute with the wrong type while in Edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: 3.5.0 and 3.6.0 Alpha\nWorked:\n\nWhile in Edit mode, attempting to create an attribute called `\"position\"` that has type not set to `\"FLOAT_VECTOR\"` will crash Blender.\n\nI couldn't get any other attributes to crash when added while in Edit mode.\nCreating the `\"position\"` attribute with the correct type, but incorrect domain does not cause a crash either.\n\nI can't imagine a use case for users wanting to do this, but it came up while I was determining the extent of 107228 and isn't really the same issue.\n\n1. Select a mesh object\n1. Enter Edit Mode\n1. Either:\n 1. Run `bpy.context.object.data.attributes.new(\"position\", \"FLOAT\", \"POINT\")` from the Python Console\n 1. Create a new attribute called \"position\" using the `bpy.ops.geometry.attribute_add` operator and set the `Data Type` to anything other than `Vector`: ", "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", "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", "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", "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>", "EEVEE: Blender Crashes when rendering specific File\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.93.0\nWorked: (N/A)\n\nBlender crashes when rendering specific file. It only seems to happen with this file - when I render other (even larger) files with the same inputs it works fine, but with this one it crashes every time. The error message is EXCEPTION_ACCESS_VIOLATION, but I received the data from an open source website and it is placed in a folder on my computer that I have full access to. Debug report: [blender_debug_output.txt](blender_debug_output.txt)\n\nSave NZ_Compressed40pc.jpg to desktop \nOpen Dev.blend\nIn the shader editor for the plane, ensure the image texture has NZ_Compressed40pc.jpg linked as input.\nRender>render image\n\nTest File:\n[Dev.blend](Dev.blend)\n", "internal error: modal gizmo-map handler has invalid area\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 rendering to the Image Editor and toggling \"maximize area\" while rendering, an error is displayed in the console\n\n\n\n**Step to Reproduce**\n- open `test.blend`\n- make sure `Preferences` > `Interface` > `Editors` > `Temporary Editors` > `Render In` is set to `Image Editor`\n- render {key Ctrl F12}\n- Hit {key Ctrl + Space} when rendering\n\n```\ninternal error: modal gizmo-map handler has invalid area\n```\n\n[test.blend](test.blend)\n[userpref.blend](userpref.blend)", "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", "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", "Crash when sculpting with a texture, deleting the image of the texture and exiting sculpt mode\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: version: 3.4, 3.5, 3.6\nBroken: version: 3.3.3\nBroken: 3.1.0\nWorked: 3.0.1\nWorked: 2.93 LTS\n\nCaused by 9111ea78ac\n\nBlender crashes when a texture image is deleted and you exit sculpt mode.\n\nYou can test it inside the attached blend file. I basically just attached an image to a sculpting brush.\n\n1. Open the blend file below\n2. draw on the surface of the sphere\n3. delete the image inside the outliner\n4. exit sculpt mode\n\nCrash occurs because `item->image->runtime.cache_mutex` is null inside `BKE_image_pool_free`\n```\nStack trace:\nblender.exe :0x00007FF713D04C10 pthread_mutex_lock\nblender.exe :0x00007FF70E6EE880 BKE_image_pool_free\nblender.exe :0x00007FF70E6B5CF0 BKE_sculptsession_free\nblender.exe :0x00007FF70F1B67A0 ED_object_sculptmode_exit_ex\nblender.exe :0x00007FF70F1B85F0 sculpt_mode_toggle_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\nblender.exe :0x00007FF70E9528D0 wm_operator_call_internal\nblender.exe :0x00007FF70E955880 WM_operator_name_call_ptr\nblender.exe :0x00007FF70F171800 ED_object_mode_set_ex\nblender.exe :0x00007FF70F148710 object_mode_set_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\n```", "inset and bevel edits crashing blender 3.x\nThreadripper 1950x 128 gb ram 2tb SSD (home)\nNVIDA 3080 updated to latest drivers\n\nIntel i7 64 gb ram 2 tb SSD (work)\nAMD 6900xt updated to latest drivers\n\n\nHappens on all 3.x versions of blender.\n\nIssue happens on both my home PC (the thread ripper) and my work PC.\n\nStart editing default cube add bevels, insets place some cuts... crashes within a couple of minutes. Happens in all display modes.. mesh, solid, renders. Happens with a smooth display mesh and hard edges. Super frustrating need to save just before doing any of these procedures on any modeling task. Always update video drivers which probably cant be the issue because two different families of video cards in two different machines have the same issue. Been doing this ever since I updated to Blender 3. I assume it's a plugin I installed because I can't imagine why this would happen on two completely different computers. Is there a dump file or something I can send? Here is a video of a typical crash. No dialog box... just blender vanishes in the the middle of editing.\n\n", "Keyed Particle Duration Crash\nOperating system: Windows 7 64\nGraphics card: nVidia GeForce GTX 970\n\nv.2.80.60\nDate: 2019-05-10 22:21\nHash: de9d846353bd\n\nBlender will sometimes crash when a keyed physics type particle system references more than one particle system. This usually occurs when attempting to change the duration setting of the second particle system.\n\nIn the provided file, change the duration setting in the particle system settings. Blender will crash.\n\n[Keyed Particle Duration Crash.blend](Keyed_Particle_Duration_Crash.blend)", "Blender 3.5 crash on render with Intel 4600 integrated GPU\nOperating system: WIndows 10 x64\nGraphics card: Intel 4600\n\nBroken: 3.5 \nWorked: 3.4.1\n\n\nBlender crashes when attempting to render in Evee. Cycles seems to work.\n\n", "MeshDeformModifier Crashing\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.6.0 Alpha\nWorked: -\n\nAfter binding, with the Dynamic attribute driver value set to 1 in driver editor, it crashed.\n\n1. Add a driver to use_dynamic_bind.\n2. Click Bind\n3. Set the driver value to 1\n\n\n\n\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" ]

[ "Blender's VDM brush addon causes crashes during Undo (missing \"UNDO\" in bl_options)\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.5.0\n\nBlender 3.5 comes with an optionally downloadable VDM Brush addon: #sculpting\n\nUnfortunately, the 2 Operators inside the addon do not contain the appropriate settings to enable Undo to work properly.\n\n- Download, install, and enable the VDM Brush addon: #sculpting\n- Delete the default Cube\n- From the N-Panel's Tool menu click \"Create Sculpting Plane\"\n- Ctrl-Z\n - Notice that the cube has incorrectly come back (bug 1)\n- Delete the Cube again and create another Sculpting plane\n- Make a stroke across the surface of the plane\n- Ctrl-Z\n - Crash (bug 2)\n\nBoth bugs can be solved by adding \"UNDO\" to the `bl_options` of the 2 Operators inside the addon.\n\nThe crash\n```\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF716C53F18\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x00000000000003F0\n\n\nStack trace:\nblender.exe BKE_scene_object_base_flag_sync_from_base C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\scene.cc:2987\nblender.exe BKE_scene_set_background C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\scene.cc:2169\nblender.exe setup_app_data C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\blendfile.cc:485\nblender.exe setup_app_blend_file_data C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\blendfile.cc:532\nblender.exe BKE_blendfile_read_setup_ex C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\blendfile.cc:569\nblender.exe BKE_blendfile_read_setup C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\blendfile.cc:577\nblender.exe BKE_memfile_undo_decode C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\blender_undo.cc:85\nblender.exe memfile_undosys_step_decode C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\editors\\undo\\memfile_undo.cc:212\nblender.exe undosys_step_decode C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\undo_system.cc:206\nblender.exe BKE_undosys_step_load_data_ex C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\undo_system.cc:788\nblender.exe BKE_undosys_step_undo_with_data_ex C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\undo_system.cc:832\nblender.exe ed_undo_step_direction C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\editors\\undo\\ed_undo.cc:284\nblender.exe ed_undo_exec C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\editors\\undo\\ed_undo.cc:504\nblender.exe wm_operator_invoke C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:1539\nblender.exe wm_handler_operator_call C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:2561\nblender.exe wm_handlers_do_keymap_with_keymap_handler C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:2960\nblender.exe wm_handlers_do_intern C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3284\nblender.exe wm_handlers_do C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3425\nblender.exe wm_event_do_handlers C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:4131\nblender.exe WM_main C:\\Users\\jesse\\source\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm.c:649\nblender.exe main C:\\Users\\jesse\\source\\blender-git\\blender\\source\\creator\\creator.c:597\n\n\n```\n\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", "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", "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", "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", "Menu items slow to open, laggy, in video editing mode on Mac M2\n```\n====================================\n= Blender 3.6.2 System Information =\n====================================\n\n\nBlender:\n====================================\n\nversion: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a, type: release\nbuild date: 2023-08-16, 23:43:53\nplatform: 'macOS-13.2-arm64-arm-64bit'\nbinary path: '/Applications/Blender.app/Contents/MacOS/Blender'\nbuild cflags: -Wall -Werror=implicit-function-declaration -Werror=return-type -Wno-tautological-compare -Wno-unknown-pragmas -Wno-char-subscripts -Wstrict-prototypes -Wmissing-prototypes -Wunused-parameter -Werror=unguarded-availability-new -mmacosx-version-min=11.00 -Xclang -fopenmp -I'/Users/blender/git/blender-v360/blender.git/../lib/darwin_arm64/openmp/include' -std=gnu11 -pipe -funsigned-char -fno-strict-aliasing -ffp-contract=off \nbuild cxxflags: -Wall -Wc++20-designator -Wno-tautological-compare -Wno-unknown-pragmas -Wno-char-subscripts -Wno-overloaded-virtual -Wno-sign-compare -Wno-invalid-offsetof -Wno-suggest-override -Werror=unguarded-availability-new -mmacosx-version-min=11.00 -ftemplate-depth=1024 -stdlib=libc++ -Xclang -fopenmp -I'/Users/blender/git/blender-v360/blender.git/../lib/darwin_arm64/openmp/include' -pipe -funsigned-char -fno-strict-aliasing -ffp-contract=off \nbuild linkflags: -fexceptions -framework CoreServices -framework Foundation -framework IOKit -framework AppKit -framework Cocoa -framework Carbon -framework AudioUnit -framework AudioToolbox -framework CoreAudio -framework Metal -framework QuartzCore -framework Accelerate -framework ForceFeedback -framework GameController -framework CoreHaptics -liconv -Wl,-unexported_symbols_list,'/Users/blender/git/blender-v360/blender.git/source/creator/symbols_apple.map' -stdlib=libc++\nbuild system: CMake\n\nPython:\n====================================\n\nversion: 3.10.12 (main, Jun 20 2023, 20:10:37) [Clang 14.0.3 (clang-1403.0.22.14.1)]\nfile system encoding: utf-8:surrogateescape\npaths:\n\t'/Applications/Blender.app/Contents/Resources/3.6/scripts/startup'\n\t'/Applications/Blender.app/Contents/Resources/3.6/scripts/modules'\n\t'/Applications/Blender.app/Contents/Resources/3.6/python/lib/python310.zip'\n\t'/Applications/Blender.app/Contents/Resources/3.6/python/lib/python3.10'\n\t'/Applications/Blender.app/Contents/Resources/3.6/python/lib/python3.10/lib-dynload'\n\t'/Applications/Blender.app/Contents/Resources/3.6/python/lib/python3.10/site-packages'\n\t'/Applications/Blender.app/Contents/Resources/3.6/scripts/freestyle/modules'\n\t'/Applications/Blender.app/Contents/Resources/3.6/scripts/addons/modules'\n\t'/Users/local/Library/Application Support/Blender/3.6/scripts/addons/modules'\n\t'/Applications/Blender.app/Contents/Resources/3.6/scripts/addons'\n\t'/Applications/Blender.app/Contents/Resources/3.6/scripts/addons_contrib'\n\nPython (External Binary):\n====================================\n\nbinary path: '/Applications/Blender.app/Contents/Resources/3.6/python/bin/python3.10'\nversion: Python 3.10.12\n\nDirectories:\n====================================\n\nscripts:\n\t'/Applications/Blender.app/Contents/Resources/3.6/scripts'\nuser scripts: '/Users/local/Library/Application Support/Blender/3.6/scripts'\npref scripts:\ndatafiles: '/Users/local/Library/Application Support/Blender/3.6/datafiles'\nconfig: '/Users/local/Library/Application Support/Blender/3.6/config'\nscripts: '/Users/local/Library/Application Support/Blender/3.6/scripts'\nautosave: '/Users/local/Library/Application Support/Blender/3.6/autosave'\ntempdir: '/var/folders/7v/szffw42146z3d53bhf53scw80000gn/T/blender_AEVBnW/'\n\nFFmpeg:\n====================================\n\navcodec: '60, 3, 100'\navdevice: '60, 1, 100'\navformat: '60, 3, 100'\navutil: '58, 2, 100'\nswscale: ' 7, 1, 100'\n\nSDL:\n====================================\n\nVersion: 2.0.20\nLoading method: linked (WITH_SDL_DYNLOAD=OFF)\n\nOther Libraries:\n====================================\n\nOpenColorIO: 2, 2, 0\nOpenImageIO: 2, 4, 11\nOpenShadingLanguage: 1, 13, 0\nOpenSubdiv: 3, 5, 0\nOpenVDB: 10, 0, 0\nAlembic: 1, 8, 3\nUSD: 0, 23, 5\n\nGPU:\n====================================\n\nrenderer:\t'Metal API'\nvendor:\t\t'Apple M2 Pro'\nversion:\t'1.2'\ndevice type:\t'APPLE'\nbackend type:\t'METAL'\nextensions:\n\nImplementation Dependent GPU Limits:\n====================================\n\nMaximum Batch Vertices:\t-2147483648\nMaximum Batch Indices:\t-2147483648\n\nGLSL:\nMaximum Varying Floats:\t60\nMaximum Vertex Attributes:\t31\nMaximum Vertex Uniform Components:\t1024\nMaximum Fragment Uniform Components:\t1024\nMaximum Vertex Image Units:\t128\nMaximum Fragment Image Units:\t128\nMaximum Pipeline Image Units:\t128\n\nFeatures:\nCompute Shader Support: \t1\nShader Storage Buffer Objects Support:\t1\nImage Load/Store Support: \t1\n\nCycles:\n====================================\n\n\nCPU device capabilities: \n\nMetal device capabilities:\nNumber of devices: 1\n\t\tDevice: Apple M2 Pro (GPU - 16 cores)\n\nEnabled add-ons:\n====================================\n\nio_anim_bvh (version: (1, 0, 1), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_anim_bvh/__init__.py)\nio_curve_svg (version: UNKNOWN, path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_curve_svg/__init__.py)\nio_mesh_ply (version: (2, 2, 0), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_mesh_ply/__init__.py)\nio_mesh_stl (version: (1, 1, 3), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_mesh_stl/__init__.py)\nio_mesh_uv_layout (version: (1, 1, 6), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_mesh_uv_layout/__init__.py)\nio_scene_fbx (version: (5, 4, 0), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_scene_fbx/__init__.py)\nio_scene_gltf2 (version: (3, 6, 27), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_scene_gltf2/__init__.py)\nio_scene_obj (version: (3, 9, 0), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_scene_obj/__init__.py)\nio_scene_x3d (version: (2, 3, 1), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/io_scene_x3d/__init__.py)\ncycles (version: UNKNOWN, path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/cycles/__init__.py)\npose_library (version: (2, 0), path: /Applications/Blender.app/Contents/Resources/3.6/scripts/addons/pose_library/__init__.py)\n```", "VSE: BLI_assert fails while rendering strip with changed font\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.90 (sub 0)\nWorked: unknown\n\nOn Windows VSE fails the `BLI_assert(BLI_thread_is_main())` assert at `BKE_sequencer_text_font_load` when trying to render a sequence with a text strip that has it's font changed. Debug build will crash, release build will ignore the assert and continue without any issues. Not sure if this is a bug or `BLI_assert`s are somehow optional.\n\n1. Open VSE\n2. Add text strip\n3. Change strip font\n4. Render (image will do)\nResult: Debug build will crash, release build will ignore the assert and work fine.\n\n**Stack Trace** (ucrtbased.dll thread)\n\n```\nucrtbased.dll!00007ffccd9a7135() (Unknown Source:0)\nucrtbased.dll!00007ffccd9a72d3() (Unknown Source:0)\nucrtbased.dll!00007ffccd9bbf3d() (Unknown Source:0)\nblender.exe!BKE_sequencer_text_font_load(TextVars * data, const bool do_id_user) Line 3799 (%BLENDER_SOURCE%\\blender\\source\\blender\\blenkernel\\intern\\seqeffects.c:3799)\nblender.exe!copy_text_effect(Sequence * dst, Sequence * src, const int flag) Line 3830 (%BLENDER_SOURCE%\\blender\\source\\blender\\blenkernel\\intern\\seqeffects.c:3830)\nblender.exe!seq_dupli(const Scene * scene_src, Scene * scene_dst, ListBase * new_seq_list, Sequence * seq, int dupe_flag, const int flag) Line 5718 (%BLENDER_SOURCE%\\blender\\source\\blender\\blenkernel\\intern\\sequencer.c:5718)\nblender.exe!BKE_sequence_base_dupli_recursive(const Scene * scene_src, Scene * scene_dst, ListBase * nseqbase, const ListBase * seqbase, int dupe_flag, const int flag) Line 5824 (%BLENDER_SOURCE%\\blender\\source\\blender\\blenkernel\\intern\\sequencer.c:5824)\nblender.exe!scene_copy_data(Main * bmain, ID * id_dst, const ID * id_src, const int flag) Line 321 (%BLENDER_SOURCE%\\blender\\source\\blender\\blenkernel\\intern\\scene.c:321)\nblender.exe!BKE_id_copy_ex(Main * bmain, const ID * id, ID * * r_newid, const int flag) Line 589 (%BLENDER_SOURCE%\\blender\\source\\blender\\blenkernel\\intern\\lib_id.c:589)\nblender.exe!DEG::`anonymous namespace'::scene_copy_inplace_no_main(const Scene * scene, Scene * new_scene) Line 314 (%BLENDER_SOURCE%\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc:314)\nblender.exe!DEG::deg_expand_copy_on_write_datablock(const DEG::Depsgraph * depsgraph, const DEG::IDNode * id_node, DEG::DepsgraphNodeBuilder * node_builder, bool create_placeholders) Line 881 (%BLENDER_SOURCE%\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc:881)\nblender.exe!DEG::deg_update_copy_on_write_datablock(const DEG::Depsgraph * depsgraph, const DEG::IDNode * id_node) Line 953 (%BLENDER_SOURCE%\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc:953)\nblender.exe!DEG::`anonymous namespace'::depsgraph_ensure_view_layer(DEG::Depsgraph * graph) Line 353 (%BLENDER_SOURCE%\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:353)\nblender.exe!DEG::deg_evaluate_on_refresh(DEG::Depsgraph * graph) Line 377 (%BLENDER_SOURCE%\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:377)\nblender.exe!DEG_evaluate_on_framechange(Main * bmain, Depsgraph * graph, float ctime) Line 84 (%BLENDER_SOURCE%\\blender\\source\\blender\\depsgraph\\intern\\depsgraph_eval.cc:84)\nblender.exe!render_update_depsgraph(Render * re) Line 1991 (%BLENDER_SOURCE%\\blender\\source\\blender\\render\\intern\\source\\pipeline.c:1991)\nblender.exe!render_init_depsgraph(Render * re) Line 2008 (%BLENDER_SOURCE%\\blender\\source\\blender\\render\\intern\\source\\pipeline.c:2008)\nblender.exe!RE_RenderFrame(Render * re, Main * bmain, Scene * scene, ViewLayer * single_layer, Object * camera_override, int frame, const bool write_still) Line 2037 (%BLENDER_SOURCE%\\blender\\source\\blender\\render\\intern\\source\\pipeline.c:2037)\nblender.exe!render_startjob(void * rjv, short * stop, short * do_update, float * progress) Line 679 (%BLENDER_SOURCE%\\blender\\source\\blender\\editors\\render\\render_internal.c:679)\nblender.exe!do_job_thread(void * job_v) Line 397 (%BLENDER_SOURCE%\\blender\\source\\blender\\windowmanager\\intern\\wm_jobs.c:397)\n\n```", "Python 4.0 delayed annotation evaluation (from __future__ import annotations )\n\n\nAdding\n`from __future__ import annotations`\nat the top of a python file makes the properties annotations of operators non-existent.\n\nThis will be enabled by default in Python 4.0, see: pep-0563\n\nCreate and enable this simple demo addon:\n\n```\nfrom __future__ import annotations # this line makes the line 30 throw an error, because the property some_prop of BUGANNOTATIONS_OT_some_op will no longer exist\n\nbl_info = {\n\t'name': 'Bug annotations with __future__',\n\t'author': 'Arnold, Arnaud Couturier, piiichan ([email protected])',\n\t'version': (1, 0, 0),\n\t'blender': (2, 80, 0),\n\t'location': 'scene options',\n\t'category': 'Scene',\n}\n\nimport bpy\n\n\nclass BUGANNOTATIONS_OT_some_op(bpy.types.Operator):\n\tbl_idname = 'scene.hey'\n\tbl_label = 'An operator'\n\tsome_prop: bpy.props.StringProperty(name='Hello', default='Default value')\n\n\nclass BUGANNOTATIONS_PT_some_panel(bpy.types.Panel):\n\tbl_region_type = 'WINDOW'\n\tbl_space_type = 'PROPERTIES'\n\tbl_context = 'scene'\n\tbl_options = {'DEFAULT_CLOSED'}\n\tbl_label = 'Bug annotations'\n\n\tdef draw(self, context):\n\t\top = self.layout.operator(BUGANNOTATIONS_OT_some_op.bl_idname)\n\t\tprint(op.some_prop)\n\n\ndef register():\n\tbpy.utils.register_class(BUGANNOTATIONS_OT_some_op)\n\tbpy.utils.register_class(BUGANNOTATIONS_PT_some_panel)\n\n\ndef unregister():\n\tbpy.utils.unregister_class(BUGANNOTATIONS_PT_some_panel)\n\tbpy.utils.unregister_class(BUGANNOTATIONS_OT_some_op)\n```\n\nthen go in the scene settings, a new panel appears. Show the button inside, and look into the console, you'll see that some_prop from the operator doesn't exist if __future__ is imported.\n\n", "Blender development todo list -- Scripting\n| Notes: |\n| -- |\n| - This is a direct dump of Scripting (without cherrypicking the [still] valid items)\n| - Changed the broken python documentation links |\n\n\n**Unstable or poorly tested**\n- [ ] BMesh operators currently use int's for enums that have undocumented values. blender/blender-addons#34914\n\nFixes that still need doing.\n**Internal API Problems**\n- [ ] Class registration needs to be reworked. as well as some internal bugs fixed.\n- [ ] RNA api has a bug where 'raw_type' defaults to INT but is not set for MFace verts in makesrna.\n- [ ] ID data returned from functions is not included unless the type is an ID itself.Returning a mesh will work but not a meshes face for eg. See bpy_rna.c - /- [ ] XXX this is missing the ID part! []/\n- [ ] Dynamic enums currently refer to invalid memory when accessed from python, we need a way for python to hold the memory until its done with the dynamic enum.\n\n**Low Priority Py API**\n- [ ] Re-Registering classes leaks memory, would be good to resolve this. (see comments in bpy_rna.c)\n- [ ] 'Safe Mode' - where writes to invalid memory are detected.\n- [ ] Implement import hooks rather than replacing import/reload pep-0302/\n\n### Python/RNA API Design TODO\n- [ ] Add a way to cancel running scripts from the user interface, with no console this becomes very problematic (Esc --> KeyboardInterrupt for example).\n- [ ] Currently there is no way to write packed images from blend files, support for this should be added to exporters. eg: image.pack_write(\"somepath.png\")\n- [ ] Addressing operators/panels/menus, should we translate all names fromSOME_MT_menu --> some.menu, ONE_PT_panel --> one.panel ? would mean the UI code could reference them by this more pythonic syntax.\n- [ ] need to decide how 2.4x api's will fit in with new apis. PyNodes, PyConstraints.\n- [ ] convenience function to get selected verts/edges/faces to prevent expensive iteration over meshes. Something like: me.verts.selected\n- [ ] Design a method to allow custom UIs to filter properties/options. Useful for Blender GE too (example: which constraints are supported (#26804). Complex matter for which rna needs to be extended?\n- [ ] Zero bytes are not supported in RNA byte string types, see blender/blender-addons#32581\n- [ ] Better python API and undo stack integration, see #38386\n\n**Inconsistencies**\n- [ ] bpy.ops.mode_set(...) has different mode-names than bpy.context.mode. E.g. TEXTURE_PAINT vs PAINT_TEXTURE''CoDEmanX:'' Getting mode from bpy.context.mode for mode_set() is inappropriate, use '''bpy.context.object.mode''' instead!\n- [ ] bpy.ops.object.move_to_layer() takes a boolean array of 20 elements (like in Blender GUI), but most functions require 32 elements. bpy.ops.object.add() for example.\n- [ ] bone.matrix returns a matrix, but requires a list when assigning to it. This also goes for some of the other matrix attributes of bone, editbone and posebone. [appears to be resolved as of 2.67?]\n- [ ] the term 'size' is used incorrectly in some cases, where it should be 'scale' instead. Review and correct: search.html?q=size&check_keywords=yes&area=default\n- [ ] keyframe_insert(), options for insert or replacing existing keyframes, threshold for detecting doubles see: bpy.types.bpy_struct.html#bpy.types.bpy_struct.keyframe_insert\n- [ ] The ID data block path returned by RNA_path_full_ID_py (rna_access.c) for node trees only works for node groups, which are stored as true ID data blocks in bpy.data.node_groups. For material/compo/texture nodes which are part of Material/Scene/Texture respectively the function can not determine the correct path. Best solution would be to get rid of nested ID data blocks altogether blender/blender-addons#35720\n\n### Python RNA access\n- [ ] Remove mesh vertices / edges / polygons (without bmesh module)\n- [ ] Shorthand for active vertex / active edge (bmesh module)\n- [ ] Active vertex / edge index for meshes (like Mesh.polygons.active)\n- [ ] Remove Shape Key\n- [ ] Remove Curve Points\n- [ ] Particle edit mode\n- [ ] Start/stop the physics sim\n- [ ] Sculpt mask custom data\n- [ ] Add / remove rigid body + constraints + world\n- [ ] Add / remove transform orientation\n- [ ] Add / remove Text curve object Textboxes\n- [ ] Add / remove Particle Systems\n- [ ] Sequencer, ability to load and images blender/blender-addons#40663\n- [ ] Pixels and resolution are not available with multilayer EXR or Render Result images #53768\n\n### Python Console\n- [ ] Append to (and remove from?) SpaceConsole .history and .scrollback\n- [ ] input() is not supported #40592\n\n### General todo items\n- [ ] Operator redo (toolbar) could also change the last InfoWindow print of the python operator equivalent.\n- [ ] mathutil.geometry.intersect_point_quad_2d works inpredictable for non-concave or quads with singularity edges #30831\n- [ ] modules/rna_xml.py: BoolVectorProperty and CollectionProperty issue blender/blender-addons#32882\n- [ ] Drivers should be able to access '''self''' for bones and objects.\n- [ ] Add the ability to report() without an operator, internally use CTX_wm_reports(C), See: operator-report-outside-operators\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", "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", "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", "\"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.", "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.", "Test bf_imbuf_save fails with an assert in debug builds (DPX 8-bit save)\nOperating system: Linux-6.2.0-10007-tuxedo-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Beta\n\n\n\n- Compile a debug version of v3.6-release\n- run `ctest -R imbuf_save` \n\nIt fails with the assert:\n```\nBLI_assert failed: source/blender/imbuf/intern/colormanagement.cc:2530, IMB_colormanagement_imbuf_for_write(), at '!(byte_output && linear_\nfloat_output)'\n```\n\n", "BMain locking during the 'after liblink' doversion\nin 6a850f3cc8, `Main.is_locked_for_linking` was added, and is currently only used in versioning code (both before and after liblink), to prevent adding or deleting IDs from Main.\n\nHowever, exceptions have already been added to allow creation of workspaces and collections in that context. And {[D12722](D12722)#inline-108272} adds nodetrees to the exceptions.\n\nProblem\n----------\n\nWhile preventing before-liblink doversion to add or remove any ID makes total sense, I do not understand why after-liblink doversion should have this constraint.\n\nTo me the bug fixed by the commit is a bug in the (removed) doversion code, not something inherently forbidden at this stage?\n\nProposed Solution\n---------------------\n\nRemove that lock check altogether in after-liblink doversion.\n\nI think however that we could use that lock on all other Mains besides the one being processed (to ensure doversion code does not create/delete things outside its own scope). And do-version code there should be smart enough to check when it runs on the local main, or a lib main, and adapt its code accordingly.\n\n~~Another thing to fix is in `BKE_libblock_alloc`, which should assign `main->curlib` to the newly created ID's `id->lib` (and tag it as indirectly linked). That way if doversion needs to create an ID in a library context, that new ID is properly created as a 'virtual' indirectly linked data, and does not break Main consistency (even if doing stupid things like generating default brushes for a lib main).~~ Done in 7681326acd" ]

[ "Failed assert when generating scene preview\nOperating system: Linux-5.11.0-7612-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Radeon Vega Frontier Edition (VEGA10, DRM 3.40.0, 5.11.0-7612-generic, LLVM 11.0.0) AMD 4.6 (Core Profile) Mesa 21.0.0\n\nBroken: version: 3.0.0 Alpha, 33d9a0c951\n\nLikely caused by 50782df4258.\n\n```\nBLI_assert failed: source/blender/render/intern/engine.c:151, engine_depsgraph_free(), at '!BLI_thread_is_main()'\n```\nThe scene preview runs on the main thread, so it makes sense that the assert fails.\n\n* Factory startup in a debug build\n* Right click the scene selector in the top-bar\n* Press `Mark Asset`\n\nOr:\n* Factory startup in a debug build\n* {nav File > Data Previews > Refresh Data-block Previews}" ]

[ "Grease Pencil Sculpt mode - clone brush and select\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\n\nThe clone brush requires you to copy a brush before you can use it. In Blender 2.80 you have a select menu in all submodes. In Blender 2.82 you miss the select menu without masking submode.\n\nNow for the bug: without masking you can call the select tools by hotkey, but you can't use it. And this means that the clone tool requires to be in a selection mask mode so that you can select, copy and clone the brush.\n\n\nOpen Blender, create a grease pencil object. Switch to Sculpt mode. Activate the Clone brush. Press C to select what you want to clone. You can't.\n\n\n\n\n\n\n\n\n\n\n", "Texture painting does blend modes like overlay incorrectly when using 16/32bit images\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.4.0 Alpha\nWorked: unknown\n\n[texture_paint_overlay_16F_bug-2022-09-28_15.37.38.mp4](texture_paint_overlay_16F_bug-2022-09-28_15.37.38.mp4)\nHere you can see that even though the paint color is white, the overlay blend mode results in darkening of the gray base color, when painting with a low strength/at the edge of the brush falloff. This happens only for 16/32bit images and independently of the color space of the texture. It seems like brush falloff and strength are applied before the blend mode.\n\n- create 32bit/16bit image texture\n- draw with white, set to Overlay on shade of gray\n[16F_texture_paint_overlay_bug.blend](16F_texture_paint_overlay_bug.blend)\n\n", "Proposal: Improving Brush Workflow in Blender\nThis is an ongoing design-topic about improving the way we handle brushes in Blender. This applies to Grease Pencil Draw Mode, Texture Paint Mode, Vertex Paint Mode, Sculpt Mode and so on. \n\n## Terminology\n\n\n**Tool**\nA tool a something that can perform a type of operation. Extrude, paint, erase, line etc are tools.\n\n**Brush**\nA brush is essentially a preset for tools. As an example, the draw tool has a bunch of options for stroke width, textures, curves, spacing and so on. A brush acts as a preset to set these various settings which can be combined to create infinite combinations of settings. Brushes act as a way to save and reuse these tool presets.\n\n\n## Problems\nThe way we handle brushes in Blender is has some issues:\n\nIn the toolbar, we directly select brushes, rather than the tools they belong to. This means we mix up brush icons and tool icons in confusing ways. In fact, the brush icons currently can’t update to reflect changes in brush settings, making the icons go out of sync if you make changes to the brushes. It also makes it so the list of tools in the toolbar becomes very long, because we mix both tools and brushes, and there’s a toolbar entry for every brush variation. So if you use Sculpt Mode, and want to make three brushes for the Smooth tool, the Smooth tool now has three copies in the toolbar, all with the same Smooth icon. That is not great.\n\nEven worse, sometimes we don't even put tools inside the toolbar, because of this clash. Case in point: In the Grease Pencil Draw Mode, the Line, Oval & Rectangle tools are placed in the header, not the toolbar, which has the brushes instead. The distinction between tools and brushes is unclear and often swapped around in inscrutable ways. \n\n## Proposal\nWe can make this much more straight forward to use, and much more powerful, like so:\n\n*In the toolbar, we only show the tools.*\n\nThe brushes then become a property of the tool, and can be selected in the tool settings/top bar. This means we can make nice generic icons that represent the tool, and then dynamic brush icons in the brush popover that updates to reflect the changes in settings, like this:\n\n\n\n*Here you can see the list of tools on the left, and the brushes popover in the top bar.*\n\nHere's a more visually complete version:\n\n\n\n\nThis is using Grease Pencil Draw mode as an example. With this change, we can now properly put the Line, Oval and Rectangle tools inside the toolbar and make the brushes separate, so they can apply to any of the tools used. \n\nIn the Tool Settings, we can display an expanded version of the Brushes popover to quickly switch between brushes:\n\n\n\nThe brush icons update dynamically to reflect the changed settings, making brushes much more useful. Users can still name brushes and share them, just as before.\n\nHere are specific examples of how the tools and brushes in the various paint modes in Blender:\n\n### Grease Pencil Draw Mode\nHere we should add the Line, Rectangle & Circle tools to the toolbar, and then expose the brushes for the corresponding tools.\n\n\n\n### Texture Paint Mode\n\n\n\n### Vertex Paint Mode\nBlending Modes should become brush settings, not separate entries in the toolbar\n\n\n### Weight Paint Mode\nBlending Modes should become brush settings, not separate entries in the toolbar\n\n\n\n### Sculpt Mode\n\n\n\n\n## Quick Access\nWith this proposal, users can change the active brush using the top bar. To make switching faster, they can also directly select the active brush in the Tool Settings tab in Properties. However, when the Properties isn't visible, we could still have other quick ways to access brushes.\n\nOne idea, is to use a shortcut to bring up the same brush panel with previews, and users can select brushes from here. We could even enable shortcut keys here, so that typing any number on the keyboard would enable a given brush.\n\nThe exact shortcut can be defined as part of the keymap, and can be decided separately. \n\n\n### Switching Brushes\nIn order to make switching brushes in Blender fast and fluid, we should provide an expanded list UI, so that users can directly click on any desired brush directly, without having to open up a popup to do so every time. The *dynamically generated* **brush previews** help the user to know what the brush will look like.\n\n\n\nNow that all the tools in our paint modes are expanded and directly available in the toolbar, we can add an affordance so that users can hold down on the tool to get a fly-out popover to set the brush, like so:\n\n\n\nHere's an example of the same thing in Sculpt Mode:\n\n\n\n\nBy default, we only show brushes that are relevant to the active tool. When switching brushes, you don't expect the tool to change, only the brush, and this approach makes it easier to categorise brushes. \n\nHowever, there are some situations where it can be useful to quickly jump between specific brushes across several tools. We can support this by having a toggle to enable viewing all the brushes in the current mode:\n\n\n\nWith this enabled, we can still display the tool that the brush will activate when you enable it, using the tool icon here:\n\n\n\nSomething we can do to aid in switching and organising brushes, is the ability to group them by category. If a user has, say 200 brushes, keeping them all in one list is not tenable. Therefore, we can support a way to give each brush a category tag name. At the top of the brush selector, users can then switch between these categories:\n\n\n\nAnother thing we can do here, is add a way that users can favourite certain brushes they may use a lot, even if they are in different categories. By clicking the heart symbol, the brush is added to the favourite brushes category:\n\n\n", "Grease Pencil ignores collection Line Art usage settings\nversion: 3.3.0 Beta, branch: master, commit date: 2022-07-28 22:39, hash: 6ca602dd9fa1, type: release\nbuild date: 2022-07-29, 00:21:12\nplatform: 'Windows-10-10.0.22000-SP0'\n\nrenderer:\t'NVIDIA GeForce RTX 3090/PCIe/SSE2'\nvendor:\t'NVIDIA Corporation'\nversion:\t'4.5.0 NVIDIA 516.59'\n\nGrese Pencil ingnores Collections Line Art usage settings. See my attachment and screenshot.\n\nOpen the attached file and check the line art settings in the torus collection.\n\n\n\n[gpencil_outlines-test-3_3.blend](gpencil_outlines-test-3_3.blend)", "Grease pencil scale issue\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.65\n\nBroken: version: 3.2.0\n\n\nGrease pencil seems to deteriorate as the scale of a camera increases\n\nIn the attached file I created a door object with a central thinner panel. I then created an orthographic camera at ortho scale 1 in plan view and set the near clipping plan to about the middle of the door in the Z axis. I added a Grease pencil scene Lineart object an placed it in it's own collection to aid turning it on and off and set the style thickness to 1 in the modifier tab. The resulting lineart works fine. I then duplicated the camera and changed its orthographic scale to 2 which also works fine. I repeated this at orthographic scale 3 and again at 4 where the resulting lineart starts to break down. at orthographic scale 20 the issue is very apparent. If I am working on a large scale scene I obviously need to have my orthographic scale high. Please advise if there is a way of increasing the orthographic scale without losing the line art quality.\nThanks\n[Greasepencil_scale_bug01.blend](Greasepencil_scale_bug01.blend)\n\n\n\n\n", "Grease Pencil Onion Skin visible when disabled\nOperating system: Linux 64-bit\nGraphics card: GTX 1080 ti\n\nbroken 2.93.5 - 3.1\n\nGrease Pencil Onion Skins should not be visible in the Viewport when disabled in Viewport Overlay settings, or when Viewport Overlays are turned off. Nevertheless, they still appear in Wireframe View.\n[GP_onion_skin_bug.blend](GP_onion_skin_bug.blend)\n - Create a GP animation with Onion Skinning (example attached)\n - Disable Onion Skins in Viewport Overlay settings\n # Change Viewport Shading Method to Wireframe. The onion skins show up again!\n\n\n", "Geometry Nodes: Color mix nodes don't effect the alpha\nOperating system:\nGraphics card:\n\nBroken: 3.4.1\n\nwhenever I try doing any math with colors, the alpha isn't affected when I use the color mix node in any blend mode. \n\n1. Open blender geometry nodes.\n2. Add 2 combine color, color or whatever node with different different values for the alpha's.\n3. Use a mix color node with any operation like add, subtract etc.\n4. See that the alpha didn't change (use the spreadsheet or the hover over).", "3D Viewport clipping support\nThis task is to keep track of which features support view-port clipping (Alt-B). [See docs ](hide_mask.html#the-clipping-border)\n\nEdit Modes:\n\n- - [x] edit armature.\n- - [x] edit curve/surface. 3e6ebdd2a6\n- - [x] edit grease pencil.\n- - [x] edit lattice. 04d18b117c\n- - [x] edit metaballs. e8292466bc\n- - [x] edit particle.\n- - [x] edit mesh.\n\nPaint Modes:\n\n- - [x] texture paint 42cd07c28c\n- - [x] sculpt mode.\n- - [x] vertex paint.\n- - [x] vertex paint.\n\nObject Data:\n- - [x] armatures.\n - - [x] bone vertices. 6fd0d810b4\n - - [x] bone axis. 37af7ce779\n - - [x] octahedral bones. 7325035e60\n - - [x] stick bones. 813800f143\n - - [x] wire bones. 813800f143\n - - [x] box bones. 7325035e60\n - - [x] envelope bones. c55fb58e8a\n - - [x] relationship lines. 6aebb5a4d5\n\n- - [x] wireframes/points 04d18b117c\n- - [x] cameras 6d8394d38b\n- - [x] empties 77b66a9666\n- - [x] lights 851d58b34f\n- - [x] light probes 671827549a\n- - [x] speakers 9bc43223c1\n- - [ ] grease pencil\n\nShading:\n\n- - [x] workbench - objects.\n- - [ ] workbench - smoke. *(clipping was supported in pre 2.76b versions)*.\n- - [ ] lookdev *(think this would be nice to support)*.\n- *eevee/cycles support is not planned.*\n\n----\n\nOther todo's\n\n\n- - [x] draw clipped background color (to see the clipped region). 48eed058b1\n- - [x] draw clipped background color (non-wire X-Ray mode still needs to be supported).\n- - [x] Object selection. 11428e0b7f\n- - [x] Object center dots. 9bc43223c1\n- - [x] Bone selection.\n", "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)", "Crash after using Grease Pencil object as object font\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nWhen I use a grease pencil object for the object font of a text, blender crashes. I have had the same issue on a different computer with the version 3.1.0.[Test.blend](Test.blend)\n\n1. Add a text object\n2. Add a grease pencil object, for example a stroke, and put it into a seperate collection\n3. Put the instancing of the text to vertices (first image) and change the object font to \"Strok\", so it references the grease pencil object (second image)\n4. Repeatedly click the \"exclude from view layer\" symbol of the collection the grease pencil object is in\n\nThank you for your effort, I hope I filled everything out correctly\n{[F14114132](1.PNG), size=full}\n{[F14114131](2.PNG), size=full}\n\n\n", "NLA: Fix Dragging Strips\nNOTE: test the patches for Solution1 temp-[D10103](https://archive.blender.org/developer/D10103)-nla_support_strip_overlap_during_transform/temp-[D10103](D10103)-nla_support_strip_overlap_during_transform-blender-2.92.0-5065c0e6d5bc-windows64.zip\n\nThis is no longer true, we would rather remove them and improve the interaction with HOLD type ****Update design since transition strips should be kept.****\nTodo: Add concrete examples where transitions are useful in the ideal case (where strips animate through the transition).\n___\nReport: #82195 (NLA tracks won't pass through actions or locked tracks)\n\n**Summary:** The ideal solution is to get rid of transition strip types. They're useless. Let strips overlap. When they do, they get blended in order like an upper strip. Then we don't have to restrict movement.\n\n___\n\nBehavior can be found in: (transform_convert_nla.c) *recalcData_nla()*\n**Problem**: The core intent of the function is to prevent moved strips from overlapping other strips. The restriction is reasonable since NLA evaluation is undefined in this case. However, the implementation prevents the ability to move a strip to its destination even if it wouldn't result in overlap. \n\nWhen moving strips:\n* You cannot move a strip through a locked track, even if not the intended final destination.\n\n* You cannot move a strip past another in the same track, even if the intended final destination would not result in overlap.\n\n* You cannot move a strip into through or into a track if doing so results in overlap. \n\n* Vertically moving strips, when there are no more nla tracks, leads to strips being vertically compressed. This breaks the animation when strip extrapolation is important.\n\n___\n**Solution1:** (Simpler solution) We only apply the restriction on the final strip location. If the strip cannot be placed without overlap, then we either cancel the move operation (not ideal) or notify the user (show the strip as red?) without cancelling.\n\n[D10101: Cleanup: Nla: Refactor nla.c functions](D10101) (independent patch) Does a little bit of refactoring which [D10103](D10103) relies on.\n[D10102: NLA: Strip Post-transform Horizontal Shuffle](D10102) (independent patch) Adds support for horizontal shuffling so users can horizontally drag strips past eachother.\n[D10103: NLA: Strip Post-transform Vertical Shuffle and Auto-Grow Track List](D10103) (depends on prior patches) Adds support for vertical shuffling so users can vertically drag strips into a new track even if it results in overlap or the user moves the strip into a locked track.\n\nPatches have been made for this solution since it's simpler and faster to implement. Overlap support can still be worked on but is a lower priority and still has design problems to figure out.\n___\n**Solution2:** (Ideal solution, but would take longer to implement) We change NLA evaluation to work properly when strips overlap. Then we can completely remove the restriction and let the animator freely move strips. \n \n**Patch1: Completely remove transition types**\nWe can simplify NLA evaluation here a bit. NLA transitions are problematic and ineffective. *Transition strip types should be completely removed.* They do a lerp between the previous strip's last pose and next strip's first pose. Generally in animation, lerping 2 poses is a problem you fix, not something you ever want. Support-wise, transitions are a bit broken anyways (see [D9711](D9711) and [D9713](D9713))\n\n**Patch2: Implement new behavior when strips overlap**\nInstead of an explicit transition strip type, we'll let action and meta strips support a new transition behavior. When two strips overlap, we simply blend the next strip as if it was an upper strip. That's the core idea. \"Transitioning\" strips of the same track would used for convenience and organization. This would simplify the keyframe remapping math. In [D8296](D8296), I couldn't figure out the math to properly invert through transitions between a Quaternion Combine strip and a Quaternion Replace (or any non-Combine) strip. With the new behavior, keyframing through transitions is simplified to inverting through any other strip. \n\n**Patch3: Re-add support for holding poses through the transition**\nThough, as is, both strips are always animated through the transition. We don't have the ability to hold one strip's boundary pose while the other animates through the transition. I propose a few new strip properties: `hold_left_duration` (unit: scene frame), `hold_right_duration`. The influence over these regions can be automatically calculated when strips overlap. Or they can be keyed into shape using the existing influence fcurve. As an example of these new properties, we'll have two strips that only overlap over this held duration. \n*Note. I'm having second thoughts on the properties. Yes, there should be support for holding poses through the transition. But the problem is how these properties are anchored relative to the strip bounds and what's most convenient. I want to avoid problems like the ones we already have with nla strip frame_start/end being tightly related to the action clips frame_start/end, scale and repeat values. This leads to unintuitive strip frame_start/end changes.*\n\n**Patch4: Finally loosen strip dragging logic (only relies on patch2)**\nWe can completely remove the dragging restriction and let the animator freely move and overlap strips.\n \n___\n\n(Pretend the two strips are in the same row/track. I did not draw them that way because I'm not sure how the UI should look. This also isn't a suggestion for how the UI should render)\n\nThis results in *nearly*the same result as old Transition clips. Only *nearly*, because the old implementation would first blend the prev strip with the lower NLA stack, then blend the next strip with the lower NLA stack, then lerp the two. The new behavior holds the previous strip's last pose over the light green area. The next strip's first pose is held over the pink area. The influence of the next strip increases linearly. \n___\n\nThis holds the previous strip's last pose. The next strip animates as it's blended.\n___\n\n\nAnother possibility.\n___\n\n**Problematic UI case**: I'm not sure what the proper UI should look like when one strip completely overlaps. The animator can always just move the strip out above as a work around. Logically, it would evaluate fine. It would just be a UI issue. What if N strips overlap? It still all works out. We blend the strips in the order of their start frame. What if all strips are on the same start frame? That case won't be properly supported and considered undefined (as in we won't fix it). The animator can and should fix it themselves. \n__\n\n**Alternative WorkAround:** Add operators that can be used as workarounds.\n* ([RCS]())Send strip to the end of the active strip or track, with options to handle overlap properly. \n\n___\nPatches:\n\n**(Abandoned)Patch set 1: Removal of transitions** \n*Note: I'm not sure how file versioning should be handled? I haven't removed the strip type NLASTRIP_TYPE_TRANSITION yet. I'm not sure if the enum should remain so it can be used for file versioning to either delete transitions or convert them to the new behavior (after Patch set 3).*\n[D9702: Nla Transitions Obselete: remove ui icon](D9702)\n[D9703: Nla Transitions Obselete: Nla Stack no longer evaluates Transitions](D9703)\n[D9704: Nla Transitions Obselete: Remove Operator Add Transition](D9704) \n[D9705: Nla Transitions Obselete: Remove themed drawing](D9705) \n[D9706: Nla Transitions Obselete: Remove default naming case](D9706) \n[D9707: Nla Transitions Obselete: Special case for adjacent strip deletion](D9707) \n[D9708: Nla Transitions Obselete: Adjacent strip overlap resolution](D9708) \n[D9709: Nla Transitions Obselete: nlastrip_get_frame()](D9709) \n[D9710: Nla Transitions Obselete: RNA strip frame_start/end set functions](D9710) \n[D9711: Nla Transitions Obselete: Transform, redundant check](D9711) \n[D9712: Nla Transitions Obselete: Transform, Cancelling](D9712) \n[D9713: Nla Transitions Obselete: Transform, broken strip exceed resolution](D9713) \n[D9714: Nla Transitions Obselete: Loose comments](D9714)\n**Abandon Reason:** I misunderstood why transitions were limited. Yes, their current implementation only supports single pose transitions. But they would be more useful if the strips animated through the transition. Alexander Gavrilov suggested we keep transitions for their branched evaluation behavior.\n", "Grease Pencil Fill Tool Breaks After Scroll-Wheel Zooming Window\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0 Beta\nAlso tested in 2.83.9 & 2.92 Alpha on Windows, and 2.91 Beta on Mac with same results.\n\nIf an 'unclosed' area made with grease pencil lines on its own layer overlaps and is 'closed' with grease pencil lines on a second layer, zooming the 2d workspace in and out will cause the fill tool to 'break' and fill the whole screen; even when the fill tool is set to: Advanced-Layers-Visible. \n\nCreate closed shape on one layer. Create 'open' shape on second layer that overlaps and is closed by grease pencil lines from the first layer. Zoom in and out in workspace while using the fill tool in a separate 'fill' layer. \nPlease see attached .blend file and screen capture: \n\n[FillTest.blend](FillTest.blend)\n\n[FillTest.mp4](FillTest.mp4)\n\n\nI really hope this isn't just user error. Thank you for taking a look!\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 cutter tool doesn't reliably terminate lines where they intersect\nOperating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5\n\nBroken: version: 2.90.0 Alpha\n\nGrease pencil cutter tool doesn't reliably terminate lines where they intersect\n\nLoad the attached blend file.\n\nUse the cutter to drag around the green area of the top line. A new point is added, but the line's terminated too early. Leaving a lump on the 'cutter side' of the intersection.\n\nUndo. And drag the cutter tool around the red area of the bottom line. A new point is added, but the line's terminated too late. Leaving a small gap on the other side of the intersection.\n\n\nExpected behaviour: The cutter tool adds a new point exactly on the intersection with the second line and deletes points up to that new point.\n\n[cutterproblem.blend](cutterproblem.blend)\n", "Grease Pencil: Visual glitches in viewport when using guides \nOperating system: Linux-5.8.0-7630-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.82a\n\n\nWhen using one of the guides that enable the drawing of straight lines, visual glitches in the viewport appear.\n\n\n - Open Blender with the 2D Animation template\n - Enable Guides\n - Use \"Parallel\" guides\n - Start drawing a horizontal line -> move the cursor perpendicular to the tip of the stroke (up or down; not too fast)\n\n\n\n\n\n" ]

[ "Grease Pencil Blend Modes Generate a thin line with BG color\n{[F6942412](1.png)}Operating system: Linux-4.15.0-47-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Ivybridge Mobile Intel Open Source Technology Center 4.2 (Core Profile) Mesa 18.2.8\n\n\nBroken: version: 2.80 (sub 55)\n\n\n\nWhen using blend modes in the layers of a Grease Pencil Object a line with the bg color appears right in the lines of the objects.\n\nAdd a grease pencil object. Draw something in a layer. Add another layer and draw again. In the second layer change the blend mode to other than Regular.\n" ]

[ "Grease pencil scale issue\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.65\n\nBroken: version: 3.2.0\n\n\nGrease pencil seems to deteriorate as the scale of a camera increases\n\nIn the attached file I created a door object with a central thinner panel. I then created an orthographic camera at ortho scale 1 in plan view and set the near clipping plan to about the middle of the door in the Z axis. I added a Grease pencil scene Lineart object an placed it in it's own collection to aid turning it on and off and set the style thickness to 1 in the modifier tab. The resulting lineart works fine. I then duplicated the camera and changed its orthographic scale to 2 which also works fine. I repeated this at orthographic scale 3 and again at 4 where the resulting lineart starts to break down. at orthographic scale 20 the issue is very apparent. If I am working on a large scale scene I obviously need to have my orthographic scale high. Please advise if there is a way of increasing the orthographic scale without losing the line art quality.\nThanks\n[Greasepencil_scale_bug01.blend](Greasepencil_scale_bug01.blend)\n\n\n\n\n", "GP transparent layer doesn't blend with background object \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\nI have a foreground grease pencil object, and a background grease pencil object (yellow blob).\nThe foreground object contains a layer set to 0 opacity.\nWhere this layer overlaps the background object in the viewport, the background object is invisible.\nExpected behaviour: the visibility of the background grease pencil object isn't affected by transparent layers in a foreground object.\n\n\n\n\n\n[#89286.blend](T89286.blend)\n\nForeground object \"makes hole\" in background, doesn't blend. Rotate viewport camera, suddenly it blends correctly.\nWhen foreground location is set to 0,0,0 it blends correctly too.", "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", "Grease pencil eraser settings not loaded on startup when using ctrl+LMB with the Draw tool\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 26.20.100.7925\n\nBroken: version: 2.90.0\n\nWhen first opening a blend file, your eraser settings are set to default when using ctrl+LMB with the draw tool, and only update after switching to the eraser tool and using it.\n\n\n- Open attached file (the Stroke object is selected and the Draw tool activated in Draw mode).\n- Draw a line\n- Erase part of the line using the same tool but with Ctrl selected. Notice how it behaves as if the `\"Eraser Soft\"` brush is used. \n- Switch to the Eraser tool, erase part of the line. Notice how it behaves according to the specified Brush: `\"Eraser Point\"`. \n- Switch back to Draw tool, and hold down ctrl to erase another part of the line, it should now start behaving like the `\"Eraser Point\"` brush.\n\n[eraser bug.blend](eraser_bug.blend)\n\n", "Grease pencil set origin fails then object has transforms\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\nGrease pencil set origin fails then object has transforms\n\nCheck blend file:\n\n[GP test.blend](attachment)\n\n1 case: select left object, press W -> Set Origin -> Origin to Geometry.\n\nOrigin will move aside like if rotation is cleared.\n\n\n\n2 case: select central object, press W -> Set Origin -> Origin to Geometry.\n\nOrigin will move to object like if scale is cleared.\n\n\n\n3 case: Select all 3 objects, press W -> Set Origin -> Origin to Geometry.\n\nOrigin will move to object as intended, but geometry data moves itself.\n\n\n\n", "Smoke darkening/miscoloration with multiple inflow objects\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nHaving 2 or more inflow objects in a smoke simulation, each with its own smoke color, causes darkening and other hue color glitches, even when the two smokes don't mix. At first I thought this was maybe an intended effect, like burning smoke, but with just one flow object the smoke comes out with a proper uniform color.\n\nOpen this file, select the domain and bake the smoke sim to see the darkening, you can see it better in Cycles. You can move the object \"model2\" out of the Flows collection and rebake again with just one Flow object, and see the color to compare\n\nThe attached images use a saturation node on the shader to exagerate the color so you guys can see it more clearly\n\n[BUGREPORT_smoke.blend](BUGREPORT_smoke.blend)\n\n\n\n", "Grease Pencil Alpha/Opacity bug\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 3.1.0\n\nGrease pencil objects containing strokes with stroke materials can not be seen through separate grease pencil objects with either a stroke with fill material with an alpha value >0 or <1, a layer with opacity value >0 or <1. \nWhen the grease pencil object with the alpha material (or layer opacity) has its location moved forward in object mode, the other grease pencil object's stroke can be seen beneath it as expected.\n\n\n\n\n\n\n\n\n\n - Create grease pencil object\n - Create stroke with material with alpha value >0 or <1\n - Set Stroke depth Order to 3D location\n - Move layer location Y forward (-0.05m)\n - Create other grease pencil object\n - Create stroke with stroke material\n\n[grease_pencil_alpha_error.blend](grease_pencil_alpha_error.blend)\n\nThank you :D\n\n", "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", "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", " 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", "Incorrect occlusion between grease pencil objects\nOperating system: macOS-12.2.1-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Plus Graphics 655 Intel Inc. 4.1 INTEL-18.4.6\n\nBroken: version: 3.3.0\n\nIncorrect occlusion occurs with this setup\n\nThe two Suzannes are clearly behind the strip, but one of them appears to be in front of the strip in camera\nIf I rotate the camera a little, both of them are in front\n\nI've tried switching the stroke depth order to 3D Location, it doesn't fix it either\n\nSee the attached file\n[gp_wrong_depth.blend](gp_wrong_depth.blend)\n\n", "Grease Pencil Sculpt mode - clone brush and select\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\n\nThe clone brush requires you to copy a brush before you can use it. In Blender 2.80 you have a select menu in all submodes. In Blender 2.82 you miss the select menu without masking submode.\n\nNow for the bug: without masking you can call the select tools by hotkey, but you can't use it. And this means that the clone tool requires to be in a selection mask mode so that you can select, copy and clone the brush.\n\n\nOpen Blender, create a grease pencil object. Switch to Sculpt mode. Activate the Clone brush. Press C to select what you want to clone. You can't.\n\n\n\n\n\n\n\n\n\n\n", "GP kills bloom\nOperating system: Linux-5.15.0-83-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: 3.6.3 Release Candidate\nWorked: \n\nWhen you have mesh objects emitting in front of grease pencil objects, bloom doesn't work there.\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 Relationship Parenting problem\nScreen \n- Huion (on a $100 computer arm )\n- Viano TV\n\nOperating System \n- 64 bit Windows 10 Pro\n- Version 4\n- Pen Touch Support\n\nProcessor \n- Intel Core i7-8700k CPU @3.70GHz 3.70GHz\n\nRam \n- 32 GB\n\nGraphics card \n- NVIDIA GeForce GTX 1070\n- NVIDIA GeForce GTX 960\n\n[system-info.txt](system-info.txt)\n\nBroken: version: 3.0.0\nWorked: I am not sure if this has ever worked\n\n[Realationship Transformation Bug.m4v](Realationship_Transformation_Bug.m4v)\n\nAttached you will find the blend file\n[Relationship.blend](Relationship.blend)\nIf you need more information let me know\n\n" ]

[ "Grease Pencil layer clamp mode alpha error\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.22\n\n\nBroken: version: 2.80 (sub 48)\n\n\nHi everyone, I've been working with the new Grease pencil tool and came across a bug. When you activate \"clamp\" on one layer, the layers beneath get a thin white outline (alpha error). A workaround is to add another layer just below your clamp layer and set it to any blending mode except \"regular\", such as \"overlay\" or \"subtract\". This can be seen in the images below. The extra layer with the nose \"highlight\" set to \"overlay\" removes the alpha error. Blend file attached. Toggle the \"Correction Layer\" on/off to see the edge appear.\n\nThanks for looking into this. :-)\n\n- Adam Janz\n\n \n\n\n\n[alpha error.blend](alpha_error.blend)\n\n" ]

[ "Outliner: Unexpected behavior when duplicating object hierarchies\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.4.1\n\n**may not be a bug** - duplicate a parent object (i.e. an object that has child objects). The duplication automatically selects the new object in the 3D viewport but this selection differs from that shown in the outliner. This means dragging to, say, a new collection does not work as expected (only the parent object is moved leaving the child behind).\n\nThe set up (this is the attached blend file):-\n1. Create two cubes (or any meshes) and parent one to the other to form a hierarchy.\n2. Add the object(s) to a collection.\n3. Create another top level collection which is empty.\n\nThe aim:-\nTo duplicate the object(s) (not the collection) and copy the duplicate to the second (currently empty) collection.\n\nThe steps:-\n1. Right click the parent object in the outliner and choose \"Select Hierarchy\". Note that the outliner shows the selected objects with a blue background bar (as expected).\n\n2. In the 3D viewport, use Shift or Alt D (doesn't matter which) to create new duplicate objects. Note that the 3D viewport shows the duplicate parent and child selected. The outliner shows a new object selected (with blue bar) but the tree is collapsed so we can't see the child.\n\n3. In the outliner, click and drag the selected parent object to the empty collection. Note that only the parent moves, the child is left behind. This child has then to be dragged separately.\n\nAfter step 2, every visual cue leads the user to believe that the duplicate hierarchy is selected. And this is the intuitive behaviour expected. But expanding the outliner tree shows the child object is not, in fact, selected (no blue bar). So an additional step of having to reselect the hierarchy is required before step 3.\n\nThe main issue is that with lots of objects and detailed hierarchies, just forgetting that additional \"select hierarchy\" step before dragging means that child objects can be scattered all over the place away from their parent and the user is left picking through the large list trying to sort it out.\n\nThis may not be a bug, it may be working as designed. But I cannot think of a use case where the current functionality would be useful so I'm assuming it's a small selection bug.\n\n", "Assert duplicating a collection in a linked scene\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.31\n\nBroken: version: 3.1.0 Alpha\n\nAssert duplicating a collection in a linked scene\n\nfrom the default startup:\n- 1) `Scene` > `Linked Copy`\n- 2) select the collection `Collection` in the Outliner\n- 3) context menu > `Duplicate Collection` or `Duplicate Linked` (does not matter which)\n\n```\nBLI_assert failed: source/blender/blenkernel/intern/collection.c:184, collection_owner_get(), at '(id->tag & LIB_TAG_NO_MAIN) == 0'\n```\n\nIf the file is saved (and reloaded) before step 3), the above assert does not happen", "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", "Using Viewport Navigation Gizmos can execute tool gizmos or sculpting\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.91.0 Alpha\nWorked: never worke in 2.8+\n\nLeft Mouse dragging on those two buttons can lead to unexpected/undesired behavior. \n\nThe dragging executes whatever tool is currently active:\n- if the selection tool is active, a selection is drawn\n- if the move tool is active and an object selected, the object is moved\netc.\n\nWhy this is a problem:\nIf one of these two buttons get accidentally dragged a little, it can apply a tiny yet destructive change to your scene which isn't noticed at first (as this behavior is unexpected).\n\n\n\nThis example is for the move tool:\n1. Open a new scene\n2. Activate the move tool\n3. Select the cube\n\n4. Drag the camera or perspective button to the side\n5. See how the cube is moved\n\n\n\nThis example is for sculpting:\n1. Open new sculpting scene\n\n2. Drag the camera or perspective button to the side\n3. See how the mesh gets distorted\n\n\nThanks\n", "Inset operator modal handling misses option to toggle \"Offset Even\" via shortcut\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 527.56\n\nBroken: version: 3.4.1\n\nNoticed problems when using Inset Faces tool in Edit Mode. If I'm using the select tool and I press **I** to activate the tool Inset Faces tool its menu doesn't display anywhere so I can't choose Even for example. If I click on the tool icon then it works, even if I then use **I** to activate the tool. This makes it so I can't use shortcut keys anymore. I suspect this is happening with other tools as well. Another thing worth noting is that the status bar says the Call Menu is triggered by the right mouse button but it actually just closes the tool.\n\n\n\n\n\n\nGo into edit mode with the default cube. Select a face. Hit I to activate the inset faces tool. Notice that the options for the tool aren't available.\n\n", "The Shortcut keys of Play Aniamtion not work in Spreatsheet Editor\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Beta\n\nThe Shortcut keys of Play Aniamtion({key Space}) not work in Spreatsheet Editor\n\n[play animation bug.mp4](play_animation_bug.mp4)\n\n", "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", "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", "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", "Bug when working with the Child Of constraint and the Selection to Cursor command\nBroken: version: 3.0.0 Alpha\nWorked: Never\n\nWhen working with the Child Of constraint the `Select To Cursor` command does not work correctly.\n\n- Open attached file\n- In the 3d View press {key Shift S} and `Select To Cursor`\n[Bug_ChildOf_Selection2Cursor.blend](Bug_ChildOf_Selection2Cursor.blend)\n\n---\n**Original Report:**\nWhen working with the Child Of constraint, it is impossible to use it several times by enabling and disabling the influence of the constraint. \nHe second time the offset is different and the child object jumps away from the desired position. \nIt's hard to put it in the right place. I tried to use a 3D cursor for this, but the Select To Cursor command does not work correctly when working with this the Child Of constraints.", "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)", "'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", "Copy/Paste Behavior in Viewport\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M390 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15\n\nBroken: version: 2.91.0 Alpha\nWorked: Never worked in 2.8+\n\nWhen pasting an object, the gizmo is not positioned at the newly created object, where you would expect it to be. Instead, there are two cases - both seem to be not intended.\nThe pasted object also is not active for direct manipulation despite the visual indication with the gizmo.\n\nIf there is a selection somewhere else before pasting, the gizmo ends up in the wrong position. Example:\n\n\nIf there is no selection before pasting, there is no gizmo appearing at all. Example:\n\n\nA directly interconnected problem is that pasted objects are not made active despite having an attached Gizmo. Example:\n\n\n**Potential fix**\n1. The gizmo could always appear and show where the object is pasted (belonging to the new object).\n2. The pasted object could become active. When multiple objects are pasted, the selection and active states of the copied objects could be transferred to the newly pasted ones. Also, all previous selections could be deselected after pasting.\n\nThank you :)\n", "Animation. Keyframes. Copy - move to the current frame.\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.77\n\nBroken: version: 2.93.0\n\n[Animation. Keyframes. Copy - move to the current frame for replacing the previous one. If you copy keyframes and move them to the current frame it won't work properly. All will seem good but the last frame will play an animation relay on the previous parameters. ]\n\n\n[bug.blend](bug.blend)\n\n\n\n", "The SHIFT key, mapped on my graphic tablet is not working in Blender 2.80\nOperating system: Windows 10\nGraphics card: NVidia GeForce GTX 1070\n\nBroken: 2.80 25-12-2018\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\nI own a Huion NEW 1060 PLUS 8192 graphics tablet. One of my keys is mapped as SHIFT, but Blender doesn't recognize it at all. As one of the pen keys is mapped as the Middle Mouse Button.\nAnother key on the tablet is mapped as CTRL, another as ALT etc. and they all work with the MMB on the pen, but the SHIFT key is not recognizable to Blender. I can zoom, I can rotate, I can change views but i cannot pan nor select multiple objects. Basically, everything that is connected to the SHIFT key is dead.\nBlender recognizes the keyboard SHIFT key, as well as a mapped SHIFT shortcut on the mouse, but not on the tablet.\nAll around the OS and in Rhino, Photoshop, Illustrator, the Shift key from my tablet is working perfectly, but inside Blender no.\n\nOh, and this is the first time I'm trying 2.8. \nEverything works fine in 2.79.\n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "weird side-effects of ctrl-z\nOperating system: Linux-4.18.0-2-amd64-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.87\n\n\nBroken: version: 2.80 (sub 58)\nWorked: 2.79\n\n\nUndo button has unexpected effects\n\nchange something/multiple things in the scene, press undo (ctrl-z).\nEffects:\n - unexpectedly switches to a different object and into edit mode\n - seemingly reloads start-up file\n - possibly other effects\nany file" ]

[ "Switching to a mode that has a tool set which is not available for that object causes error [e.g Select Box tool is available if paint mask is enabled, if it is disabled it causes error]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0\n\n[when i try open vertex paint or weight paint , brush and color bar not coming to viewport]\n\n[after basic modeling something i apply all modifer and try to create uv but i cant do properly. So after unsuccessful attempt i tried to paint weight paint but color and other bar not coming to screen. But if i create new blend file and append it. Also work and i can create but after some paint also broke vertex paint file and mine locak vertex paint parts gone. btw i also cant open in new file as link...\n\n[try_007_gun.blend](try_007_gun.blend)\n\n\n", "Crash on Python API bpy.ops.mesh.rip_move()\nOperating system: Windows 10\nGraphics card: RTX3080\n\nBroken: 3.3.2, 3.4.0, 3.5.0-alpha\n\nCrash on calling `bpy.ops.mesh.rip_move()` from Python API.\n\n - Open new Blender file\n - Switch to Scripting workspace\n - Create file with\n```\nimport bpy\nbpy.context.area.ui_type = 'VIEW_3D'\nbpy.ops.mesh.rip_move()\nbpy.context.area.ui_type = \"TEXT_EDITOR\"\n```\n - Delete all objects\n - `Shift-A` to add cylinder\n - Tab` to edit mode\n - Click edge or vertex selection mode\n - Select an edge or vertex\n - Run script\n - Crash\n\nManually doing a `V` rip move and then using the \"reports\" list to copy over the exact command to line #3, also results in a crash\n[blender.crash.txt](blender.crash.txt)", "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```", "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", "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", "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", "Mesh related crash in add-on\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 780 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.0.0 Alpha\n\nUsing an the operation connect spread in an addon is causing an EXCEPTION_ACCESS_VIOLATION. \n\n[blender.crash.txt](blender.crash.txt)\n\n```\nStack trace:\nblender.exe :0x00007FF7A109EC60 blender::deg::deg_graph_flush_updates\nblender.exe :0x00007FF7A1084AA0 DEG_evaluate_on_refresh\nblender.exe :0x00007FF79C983790 scene_graph_update_tagged\nblender.exe :0x00007FF79CB61510 wm_event_do_notifiers\nblender.exe :0x00007FF79CB4B550 WM_main\nblender.exe :0x00007FF79C7E2ED0 main\nblender.exe :0x00007FF7A16421A8 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFEEB937020 BaseThreadInitThunk\nntdll.dll :0x00007FFEECA62630 RtlUserThreadStart\n```\n\nDownload [Forgotten Tools ](forgotten_tools_0_5_0.zip) use Connect spread on 2+ edges go to operation popup menu increase the cuts.\n\n[2021-06-20_00-26-23.mp4](2021-06-20_00-26-23.mp4)\n\n", "Geometry Nodes related memory leak and exception access violation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: \n\nBlender freezes, memory usage spikes and eventually you get exception access violation crash.\n\nOpen attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.\n\n[gnodes bug1.blend](attachment)\n\nTo stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the \"fir_twig\" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.\n\n", "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", "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", "Breaking Mesh API changes for 4.0\nThis will allow cleaning up code and unifying with the generic attribute system.\n\n- [ ] Normals changes from #108014\n- [x] Remove legacy format writing for #95965\n- [ ] Remove `mesh.vertex_colors`, replaced by `mesh.color_attributes`\n- [x] Remove `mesh.sculpt_vertex_colors`, also replaced by `mesh.color_attributes` and never used in a release\n- [ ] Use a single collection property for `Mesh.edge_creases`\n- [ ] Remove no-op `Mesh.free_loop_normals()` function\n- [ ] Remove `Mesh.calc_normals()`, replaced by lazy calculation\n- [ ] Remove `Mesh.calc_loop_triangles()`, replaced by lazy calculation\n- [ ] Avoid clearing lazily calculated caches in `ED_mesh_update`\n- [x] Remove old custom data API (`polygon_layers_int`, etc.)\n\n**Needs agreement**\n- [ ] Remove `.index` properties, which are much less efficient than writing a loop properly\n- [ ] Remove accessors to properties on mesh element classes, which are accessed much less efficiently than looping through arrays of basic types separately\n\t- [ ] Replace `MeshVertex.bevel_weight` and `MeshEdge.bevel_weight` with attribute API and float attribute type\n - [ ] Replace `MeshEdge.crease` with `Mesh.edge_creases`\n - [ ] Remove hide status from vertices, edges, faces\n - [ ] Remove selection status from vertices, edges, faces\n - [ ] etc (needs further discussion)\n- [ ] Remove some of the redundant ways to assign active layers", "Cycles vertex baking seams\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 560 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.1.0\n\nThere are seams between the vertices when I try to bake lighting into vertex colors using Cycles, even when the vertices are merged.\n\nHere's my .blend file:\n[baking test.blend](baking_test.blend)", "Vertex Painting with data type \"Color\": Painting pure Red or Green creating non Zero in Blue Channel\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.63\n\nBroken: version: 3.5.0 Alpha\n\n**Short description of error** \nIn Geometry Nodes, I've tried scattering objects with vertex painting (data type \"Color\") using pure red (1,0,0), green (0,1,0) and blue (0,0,1). With a math node set to \"Greater than\", the different color channels are tested whether their values are bigger than 0. However, I discovered that I needed actually a \"Threshold\" value slightly bigger than 0 (I used 0.0001, just below the \"Spreadsheet's\" precision) because my objects for the blue painted areas got also displayed in red and green areas with a \"Threshold\" value of exactly 0 for testing the blue color channel. The red and green channels could be tested with a threshold of exactly 0. \n\nWith vertex painting using the data type \"Byte\", I could also set the blue channel's testing threshold to exactly 0.\n\n**Steps to Reproduce**\n- Open attached file\n- Set Threshold value exact to 0 for blue color channel\n[Geometry-Nodes_Instancing_with_Vertex-Colors_1Jan2023_7.blend](Geometry-Nodes_Instancing_with_Vertex-Colors_1Jan2023_7.blend)\n\n", "Vertex Paint ➔ Paint menu ➔ Smooth Vertex Colors could be improved\nOperating system: Windows 10 Pro 64-bit\nGraphics card: NVIDIA GeForce RTX 2080 Ti\n\nTested: Blender 2.81 Alpha, September 18, 14:29:45 - b962aca8003d\nWorked: never\n\nVertex Paint ➔ Paint menu ➔ Smooth Vertex Colors tool does not smooth other than direct loop neighbors.\n\n1. Divide the default cube a few times (apply if subdivision is done with modifier).\n2. Enter Vertex Paint mode.\n3. Paint an area with black.\n4. Apply Paint menu ➔ Smooth Vertex Colors.\n5. The vertex paint is not smoothed other than direct loop neighbors.\n\n\nHere is some clarification as the descriptions above are not very clear (I work with vertex colors very regularly and still came out confused by reading this post).\n\n- The Smooth Vertex Colors command will have visible results *if* it is run on vertex colors that have been applied per-face (by first selecting the desired faces in Edit mode, and then filling them with colors in Vertex color mode with the face filter enabled). Think of these as \"harsh\" vertex colors. When such vcols exist, then the smooth operation will indeed smooth out the vcol data so that the harsh separation between painted faces will be smoothed out, blending it with the surrounding faces.\n- But if the command is run on vcol data that has been painted on using the paint brush or on vcol generated by the \"dirty vertex colors\" command then nothing will happen as the vcols will already be point-based.\n\nTherefore there is no bug here, just some very confusing naming of the command and a lack of clarity when the command is run but nothing happens. For any user working with painted-on vertex colors, it will indeed seem like nothing is happening at all since one would expect some sort of global smoothing to be applied.\n\nPart of the confusion is also coming from the fact that this command sits just below \"Dirty Vertex Colors\" in the menu, which generates smooth, per-vertex vcol data. Meaning that for a user exploring vcol mode by trying one feature after the next, \"smooth vertex colors\" will almost always feel like it is doing nothing at all (unless the user first applied some vcol using face masking, which is extremely unlikely).\n\nIf anything the tooltip and/or the menu entry could be changed for clarity :\n\n- The menu item name could be renamed from \"Smooth vertex colors\" to \"Smooth harsh per-face vertex colors\"\n- The tooltip could be changed from \"Smooth colors across vertices\" to \"Smooth colors across vertices. Only operates on harsh, per-face vertex colors\".\n\nAnd then of course it would be great to have a new feature altogether to blur vcols globally, similarly to what the blur brush does.", "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. -----------------------------------------------------------" ]

[ "Python API: Mesh editing: Editing uvs after normals with a previously assigned variable doesn't work\nBroken: 3.5.1\nWorked: 3.4.1\n\nCaused by 6c774feba2\n\nHolding on a variable referencing the uv layer data for later uv editing, doesn't work when normals are edited in between\n\nRun the attached python script in Blender 3.5.1\nThis creates three objects, all should have all their loop uvs as 0,0:\n\n- no_set_normals (should have default normals, sideways)\n- with_set_normals_and_reaccess_uv (should have upwards +z normals)\n- with_set_normals_but_no_reaccess_uv (should have upwards +z normals)\n\nGo in edit mode on each generated object, look at the normals and uvs\nThe results are only correct for no_set_normals and with_set_normals_and_reaccess_uv\nFor with_set_normals_but_no_reaccess_uv, neither the uvs nor normals are correct. Both appear to be defaults\n\nIn Blender 3.4.1 this works as expected, i.e. with_set_normals_and_reaccess_uv and with_set_normals_but_no_reaccess_uv are identical\n\nAttached are also screenshots in 3.5.1 of the normals and uvs of each object\nAnd a screenshot in 3.4.1 showing the expected results\n\n**Guess at what's happening**\nOn more complicated cases (actual meshes with hundreds of triangles), the normals are messed up (seemingly random instead of defaults) and Blender is prone to crashing. This leads me to believe holding on the uv layer data after normal editing accesses freed memory or something like that?\n\n" ]

[ "Current frame indicator has misaligned and inconsistent pixel positioning\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3060 TI\n\nBroken: 3.1.2\nWorked: Probably never\n\nThe current frame indicator is aligned inconsistently against the keyframes depending on where the current frame indicator is within the 2D viewport.\n\n[framewiggle.mp4](framewiggle.mp4)\n\nThere is an additional issue that is probably contributing to this as well. The frame indicator is 4 pixels wide (shadow included). Note that this is an *even* number. Because the background grids, keyframes etc. all have *odd* widths, it is mathematically impossible for the frame indicator to ever be properly centred over any of them. The current frame indicator should be made to be 3 pixels wide, or perhaps 5 pixels wide so that it can actually be centred with other elements in the UI.\n\n\n\n1. Make a bunch of keyframes on an action.\n2. Position the current frame at a frame that has keyframes.\n3. Pan the 2D viewport of the action editor.", "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", "UI: Merge Text Style \"Widget Label\" into \"Widget\", Add \"Tooltip\"\nWhen controlling how big interface elements are displayed, users can not only change the Resolution Scale and Region Zoom but can change the size and styles of some elements separate from others. This document proposes changes to our Text Styles.\n\nIf you go to Preferences / Themes / Text Style you will see that you can change the size of different UI elements independent of the overall UI scale. You can make it so that regardless of scale you always have Header text twice as large as regular text, for example.\n\nBut the design is not fleshed out well. We have just \"Panel Title\", \"Widget\", and \"Widget Label\". There are many areas where one type of UIBut uses one when it should use another. There are assumptions, like in #102687, that \"Widget\" and \"Widget Label\" are the same size. The function mentioned in that bug report - `ui_text_icon_width_ex()` - is trying to estimate an element's width but does not have the information needed to know what style to use, so just uses UI_FSTYLE_WIDGET, which is hardcoded for the \"widget\" style.\n\nIt seems like a nice idea that we can have labels displaying differently to the inputs beside it. And I have personally proposed adding to these options to include width, weight, slant, spacing and other text features.\n\nHowever, our interface is laid out programmatically using quite rough rules. We necessarily have a very tabular layout. For example we don't have (and might not be able to supply) a \"line height\": the vertical spacing between interface rows. This value is calculated from UI element width, considering scale and line width. So can't for example, leave the resolution scale the same but change the line-height to better accommodate languages that use fonts that are very tall (Arabic) or squat (Chinese).\n\nThis all means that we have little chance to make Label and Widget have varying sizes. The line-height can't vary with the largest of them, and we have to keep all interface rows the same height anyway.\n\nI propose that we merge \"Widget Label\" into \"Widget\" text styles, leaving us with only two styles \"Header\" and \"Widget\". And then add a third back for \"Tool Tips\" because that text size is currently set as a hardcoded fraction of the widget size - and I can imagine some users with vision impairment wanting those proportionally larger.\n\nThe only real downside is this would remove the ability for \"Widget\" and \"Widget Label\" to have differences unrelated to the size. There could be some users who have the same size but have them differ in shadow. Right now the only non-size changes possible are shadow-related but, as mentioned, we could add other options. For example we could allow one to be bold and the other italicized. But I don't personally think this is important. I don't like our text shadowing and use of weight and slant differences should be more selective than this, having sematic meaning. I would rather embolden important words, italicize special sections, etc.\n\n", "Pose Library: Collection pop-up when creating new poses in Action Editor\nWhen creating poses from the Action Editor it should be explicit to which catalog the new asset should be added.\n\nBy default the Unassigned option should be highlighted, so users can post-pone this decision for later, similar to when marking data-blocks as assets.\n\nThis is part of #103265.\n\n---\n\nSome initial code snippets for anyone interested on tackling this: [P3408](P3408.txt)", "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, ", "Cycles dupli object baking issues\nnvidia g880m\n\nBroken: blender-2.73-d56c9fb-win64\nWorked: (optional) probably never\n\nwhen assigning object as duplis to some mesh, and then trying to bake these duplis to another mesh, duplis appear black. But in normals mode, it works, so they are there, just without material or something.\nAlso, you can see that the duplis are there actually twice, one offset quite strongly. In some other file, I got them also four times...\n\n\n[bakebug.blend](bakebug.blend)\nopen the file, hit bake. \nthe group of objects in the ceter bakes to the cube.\n\nalso, you can see another group of objects, where duplis have been made \"real\" and it works well, it's group of objects called \"fine\", baking to the cube works well with seemingly same meshes.\n", "Asset Browser refreshes unnecessarily and halts Blender when doing so\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.94\n\nBroken: version: 3.4.0 Alpha\n\nThe Asset Browser refreshes its thumbnails often, without need for it, and stalls Blender when doing so.\n\nThe video demonstrates that only some actions cause this and that this only happens when the Asset Browser is visible + it shows that the UI can be completely unresponsive for seconds.\n\nThis happens any time the asset browser is open and certain actions such as deleting any object is being performed.\nLarger Asset libraries and slower hard drives compound the issue.\n[2022-08-30_17-22-14.mp4](2022-08-30_17-22-14.mp4)", "Looks like an eevee limitations with UV maps and attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\n\nWhen working with multiple UVs and attributes, eevee disables some normal/bump maps.\nThere is an error in the console:\n```\nGPU_material_compile: Attribute \"nor\" overlap one or more index from another attribute. Note that mat4 takes up 4 indices. While merging eevee_legacy_material_surface_frag_opaque\n```\nIn 3.4, the shader cannot compile at all (pink texture).\n\nThis is not documented anywhere and it is not clear to me how it works, because until I connect nodes with attributes in Base Color, all normals are displayed.\n\n1. Open .blend file.\n2. Turn on the eevee render.\n3. Look, all normals are displayed.\n4. Connect nodes with attributes to Base Color.\n5. One normal map is missing. An error appeared in the console.\n\n", "Don't show catalog path when dragging assets over root level catalogs\nWe show the name, and the full path of a catalog in parentheses, when dragging assets over it. For root level items this will just result in showing the catalog name twice. This is confusing and should be avoided.\n\n", "Font rendered incorrectly with text object\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nThe font is displayed incorrectly when added to 3d text object\n\nFont and blend file in attachment\n[untitled.blend](untitled.blend)\n\n[roadrage.ttf](roadrage.ttf)\n\n", "Asset Browser - Current File doesn't place objects in active collection\nOperating system: Windows 11\nGraphics card: RTX 4070ti\n\nBroken: 3.5.0\nWorked: Supposedly never (tested 3.0-3.6)\n\nWhen adding an object into the scene from the Current File category in the Asset Browser, objects are placed into the same collection as the assets they originate from instead of the collection you are currently working in.\n\n- Move default cube into a new collection\n- Mark as asset\n- Ensure the scene collection is active, not the cube collection\n- Drag cube asset from Asset Browser Current File category into the scene\n- It will appear in the same collection as the asset reference object\n", "Asset System & UI: Improve memory management for assets and previews\nLoading asset libraries can lead to significant memory use, since all contained assets need to be represented in memory. This may be thousands of assets. Further, the UI may request previews for assets, where each preview has a notable memory footprint (around 70kB for each preview at the default 256x256 image size).\n\nAs it stands, Blender is not mindful about this at all. For example simply calling the \"Add\" menu in geometry nodes editors loads all asset libraries into memory (!), including all previews (!) and keeps all this data in memory until another .blend is read (!). This is bad and wasteful design that users have to pay for.\n\n## Status Quo\n\nMemory and asset lifetime is managed rather differently in the asset browser and the rest of the UI (asset shelves, add menus, etc.).\n\n**Current Asset Browser Memory Management:**\n\nThe situation for the asset browser is not too bad (because it's simpler).\n\n- **Good**: Only the currently shown asset library is loaded into memory.\n- **Good**: Previews are lazy loaded into a cache based on the assets in view.\n- **Good**: Previews are removed if the cache is filled with a resonably small amount of previews.\n- **Bad**: Storage is per asset browser instance, so when multiple are open and showing the same asset libraries, storage is duplicated (especially wasteful for the \"All\" asset library).\n- **Bad**: The preview cache is cleared and reloaded often, causing flickering on common interactions (e.g. undo/redo).\n- **Bad**: The preview cache fails miserably with large asset libraries and causes continuous freezes, making the asset browser unusable with large asset libraries.\n\n**Rest of the UI:**\n\n(Asset views, the node add menu, the node search menu, asset-view template, etc.)\n\n- Challenge: Usually use the \"All\" asset library, meaning all assets are loaded when showing such UIs.\n- **Good**: Memory is shared between these UIs (static storage), so libraries are only loaded and stored once. (Asset browser storage is still separate).\n- **Bad**: No lazy loading of previews, all previews are loaded into memory\n- **Bad**: Only freed when closing the file.\n- **Bad**: Previews are also loaded when none are displayed (e.g. node \"Add\" menu)\n\n---\n\n## How to solve it?\n\n### Good solution characteristics\n\nA good solution should give us the following:\n- Only hold asset previews in storaged that are in view of the user\n- Don't keep asset libraries in storage that the user isn't interacting with (at least not regularly, see next point)\n- Provide fast repetetive access to asset libraries (e.g. assets shouldn't be reloaded every time the \"Add\" menu is called in the geometry nodes editor)\n- Support shared storage. All UIs giving access to assets should be able to access the same static asset library and preview image storage.\n\n(Further improvements are possible still, see below)\n\n### Lazy Loading Previews\n\nPreviews should always be lazy loaded based on which assets the user sees, and only if the previews are actually displayed (e.g. not for the node \"Add\" menu). #109234 does most of the necessary work for this.\n\n### Garbage Collector?\n\nA garbage collector could be implemented to remove unused asset libraries and asset previews from storage. Some kind of user-counting will be needed to detect the unused state, even when multiple parts of the UI display the same asset library (and thus may share storage). By being time based rather than user-count based only, the garbage collector still gives enough time for repetitive access to asset libraries. For example the asset library may still be in storage for multiple calls to the node \"Add\" menu, but be freed from storage if it hasn't been called for at least 5 minutes.\n\nNote that this doesn't need to be asset system specific. There are other UI previews that we load from disk that could make use of this. So this could be a more general UI garbage collector.\n\n---\n\n## Possible Further Improvements\n\n## Partial asset library loading?\n\nUsers rarely ever look at all assets of a library. They typically look at assets of a certain type (e.g. in the node \"Add\" menu), a specific catalog, or the view simply only has space for a subset of the available assets. So this is another case where we can avoid keeping data in storage, e.g. by lazy loading assets or deleting them once they are recognized as irrelevant.\n\nKeeping track of which assets are loaded and which have to be made available can be finicky. Plus we may run into issues when asset library contents were updated in-between partial reads.\n\n## Lazy load extended metadata\n\nIn most cases, all the user sees from an asset is the name, and potentially the preview. Keeping all the asset metadata in storage is a bit of a waste. We could lazy load this as well, although this can become finicky too, since some metadata needs to be accessed faster or more frequently (e.g. basic type information, tags for search, etc.) than other.\n\n## Compressed preview buffers\n\nPreview buffers could be compressed to reduce the memory footprint of each, potentially leading to faster load times too.\n\n", "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks", "Graph Editor: Automatic Colours can be confusing\nProblem: when there are many curves, the mapping from X/Y/Z/W to colour is inconsistent. For example, the same hue can be used for X in one bone and Y in another.\n\n**Proposal**: No concrete proposal yet, apart from the desire to have consistent X/Y/Z/W colours. The colour generator code could be altered to always produce the same hue for the same RNA `array_index`, for example, or use `array_index/array_length`.\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" ]

[ "Interface glitches in Mark Asset on a multiple selection.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon R7 200 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.10.1 27.20.12033.1007\n\nBroken: version: 2.92.0 Alpha\nWorked: N/A (new feature)\n\nAll the interface of blender starts glitching when you mark as Assets a multiple object selection in the outliner.\n\n - Open the attached file with blender 2.92 [FIME_BASIC.blend](FIME_BASIC.blend)\n - Change the outliner to blender file\n - Open material section -> Select all the materials -> right clic ->Mark Asset (nothing happens)\n - Open objects section -> Select some objects (*like from the first one to the first camera in the list*) -> right click ->id data ->Mark Asset\n - The interface glitches\n\nVideo showing the Bug [2020-12-22 15-49-37.mp4](2020-12-22_15-49-37.mp4)\n\n", "UI Problems after Create Asset after Undo\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\nWhen creating several assets and then undoing it, the UI has some frames that are resized correctly and the whole header disappears.\n\n1. Create a cube\n2. Duplicate it 3 times\n3. Mark every single one as an asset\n4. Undo every **Mark as Asset**\n5. The text size of most of the UI will resize on every undo for a short time\n[UIProblemAssetUndo.mp4](UIProblemAssetUndo.mp4)", "Menu/Outliner text funkyness\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1\n\nWhen marking objects as assets, sometimes the text in the outliner and/or the main menu flickers, gets bigger and goes back to normal. In other cases, it just disappears.\n\n1. open default scene\n2. select default cube\n3. mark default cube as asset\n4. repeat 3 until it happens\n\n[2022-02-23 16-48-38.mp4](2022-02-23_16-48-38.mp4)\n\n", "Asset operation refresh UI with large font, and refresh normally\nOperating system: Ubuntu 20.04\nGraphics card: RTX 2070\n\nBroken: latest Blender 2.93 master\n\nWhen doing some asset operations (listed so), the all ui or just some areas are refreshed.\n- Marking an asset\n- generating the preview in the sidebar of the asset browser area\n [Kazam_screencast_00000.webm](Kazam_screencast_00000.webm)\nHere is a screenshot of the screencast when the issue happens.\n\n\n\nI do not know if it is related to the asset system, but I never saw that with other tools or operators.\n\n- Open blender defaults\n- Mark cube as Asset ( right click in outliner, IDData, mark asset ) **-> Issue here**\n- Open asset browser tab\n- Open the side panel\n- Regenerate the preview** -> Issue here**" ]

[ "Regression: Importing of collada model with instances became a LOT slower since 2.80 (practically freezing)\nOperating system: windows 10\nGraphics card: geforce gtx 1070\n\nBroken: blender 3.4.1\nWorked: 2.80\n\nImporting of collada model makes Blender not respond anymore with high CPU usage in windows task manager (and never finishes no matter how long you wait)\n\n- import attached collada file\n- Blender not respond anymore with high CPU usage in windows task manager (and never finishes no matter how long you wait)\n\nLink to model file:\n\nCruisn-Exotica-arcade-game-Dual\n\n[doubleexotica.zip](doubleexotica.zip)", "Bug while moving vertices with mirror & subdivision modifier\nOperating system: Windows 10 64-bit\nGraphics card: ATI Radeon HD 5670\n\nBroken: 2.82\nWorked: at least 2.8\n\nWhen I try to move a vertice it seems like the mirror modifier gets applied in an odd way. The result even changes when moving the camera or hide one of the images I use for reference. In fact it becomes distorted when hiding the images.\nThe following link is a recording of my screen:\nview?usp=sharing\nI encountered this bug only recently. The file itself is older and I do not remember which version I used (since I use it via Steam I did not pay attention to the automatic patches).\n\n1. Open this file [Bugged Project.blend](Bugged_Project.blend)\n2. Disable visibility of Subdivision modifier for Edit Mode (which should already cause the bug)\n3. Move a vertice\n\n[system-info.txt](system-info.txt)", "Cycles: CUDA takes ages to render what takes seconds on CPU and OPTIX (it also needs way more RAM)\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1, 2.93, 2.92\nWorked: I think it was always the case\n\nThe dino demo file (Splash Blender 2.92 60337d495677e942564cce76) takes with CUDA (BVH2) way longer to build the scene than CPU (Embree).\nIt also needs a lot more RAM. \nCa. 100GB of RAM\n\n\n```\nCUDA (BVH2)\nFra:1 Mem:1175.90M (Peak 51547.35M) | Time:21:52.48 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0001.png'\n Time: 21:53.12 (Saving: 00:00.63)\nOptix (Embree)\nFra:2 Mem:1176.06M (Peak 14002.25M) | Time:00:36.55 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0002.png'\n Time: 00:37.16 (Saving: 00:00.60)\nCPU (Embree)\nFra:1 Mem:1175.90M (Peak 14007.17M) | Time:01:08.57 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0001.png'\n Time: 01:09.21 (Saving: 00:00.63)\n```\n1. Open the scene\n2. Set it to one sample (disable denoising)\n3. Render with CPU, CUDA and OPTIX to compare.\n", "Subdivision Surface Performance Degrades Markedly With Non-Quad Meshes\nOperating system: Windows 7 Pro X64\nGraphics card: Nvidia Geforce GTX 980 Ti\n\n\nBroken: Date: 2019-01-21\n```\n Hash: dd3f5186260e\n Branch: Blender 2.7 (although it's supposed to be a 2.80 Beta)\n```\n\n[OpenSubDiv_PerformanceBug.zip](OpenSubDiv_PerformanceBug.zip)\n\nSubdivision surfaces are fast and responsive in Edit mode *with all-quad meshes*, but very slow (~ 10x slower) with meshes comprised of triangles and quads.\n\n\nOpen the attached blend file and select **Cube.001**\n\nGo into Edit mode. Turn on Proportional Editing. Grab a point and move it - observe how responsive the viewport is with the all-quad mesh.\n\nGo back to Object Mode. Select **Cube**. Go back into Edit Mode. Grab a point and move it (with proportional editing still turned on) Observe how slow it is.\n\n", "Sculpt Mode Performance\n**Status:** Prototype implemented in [D8983](D8983) with all optimizations included for Meshes, but only for some tools and features. Needs to be split into multiple patches and implement all remaining features.\n\n---\n\n**Team**\n**Commissioner:** @DanielBystedt \n**Project leader:** @PabloDobarro\n**Project members:** `-` \n\n**Description**\n**Big picture:** Improve the performance of Sculpt Mode brushes and tools.\n\n[Sculpt performance demo.mov](Sculpt_performance_demo.mov)\n\n**Use cases**:\n* Edit geometry surface detail in high poly meshes without performance issues\n\n**Design:**\nRemove all unnecessary calculations and updates from the PBVH when an editing operation is active, making all the Sculpt Mode code work only with the relevant vertices per brush step. The PBVH should only be used to get the affected area by the stroke as fast as possible.\n\n**Engineer plan:**\n* Get the PBVH code ready to have much smaller leaf node sizes\n* Store draw buffers in intermediate nodes to reduce the size of the leaf nodes of the PBVH.\n* Make proxies, bounding box and normal updates optional per tool and per symmetry options.\n* Do fast bounding box recalculations by updating the bounding boxes when deforming and propagating them from children to parents nodes to the root of the tree.\n* Implement optional fast normal updates (single loop) for brushes that require them.\n* Replace per node undo with a per vertex undo, which will also be used to get the original data during the stroke.\n\n* Remove BMesh based dyntopo (to be replaced with a better implementation).\n* Remove all loops over nodes from the code that runs when a stroke is active. \n* Configure the optimal settings of the scheduler per tool.\n* Make special tools (Pose, Boundary, Elastic Deform) not use the PBVH for getting the affected area. Cache the affected area of these tools once their data is initialized.\n\n**Work plan**\n\n**Milestone 1 - optional name**\n*Optimize PBVH queries and drawing*\nTime estimate: `2 - 3 weeks`\n\n**Milestone 2 - optional name**\n*Rewrite task scheduling and per vertex updates.*\nTime estimate: `3 - 4 weeks`\n\n---\n\n**Relevant links**:\n* #68873\n* #73934", "Blur brush(Weight Paint): Take edge distance into consideration when blurring weights\nThe current Blur brush is difficult to use in cases where the mesh topology is not very uniform. More vertex-dense areas will get affected by the weight blurring \"less\".\n\nI discussed this briefly with @ZedDB over chat, also with a quick look at [D10068](D10068) which seems like it could be useful for improving the Blur brush.\n\nHere is a simple example:\n[weight_paint_blur-2021-04-06_12.47.00.mp4](weight_paint_blur-2021-04-06_12.47.00.mp4)\n[weight_paint_blur_test.blend](weight_paint_blur_test.blend)\n\nAs you can see, when the cylinder has fairly uniform density, the result I get from blurring is what I expect(even if it looks ugly in this example), but when I add extra edge loops, the result is totally different. This is not necessarily unexpected, and in some cases it might even be desired. So here's a more realistic example, on an actual character with details modeled in:\n[weight_paint_rex_blur-2021-04-06_15.37.04.mp4](weight_paint_rex_blur-2021-04-06_15.37.04.mp4)\nNotice especially the banding of the colors. I was blurring it as much as I could, but there'd still be clearly visible bands where the topology is more dense.\nIf I remove some edge loops to try to get more evenly distributed faces, I can make a clean gradient again, with no bands:\n[weight_paint_rex_edges_removed-2021-04-06_15.38.18.mp4](weight_paint_rex_edges_removed-2021-04-06_15.38.18.mp4)\n\nThe goal would be to be able to create a clean gradient like this, even with uneven topology. This could allow rigging more complex meshes \"directly\" rather than using indirect methods like Mesh Deform/Surface Deform, which come with their own sets of inherent limitations.", "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", "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", "Crash when baking a normal map from procedural materials\nOperating system:\nManjaro w/ KDE\nGraphics card:\nNvidia GTX 1060 6GB\n\nBroken: 2.80 Beta, 5e626e766459, branch: blender2.7, 2019-06-13\n\n\nI've sculpted a high poly model from the lowpoly one - baking normals from that works fine.\nWhen I created procedural materials using Geometry Pointiness, Noise, a painted texture and other sources to create additional normal information - the baking crashes.\n\nHere's the project file. It's huge (781 MB), but compresses very well (turns out the painted texture was wasting a lot of space), without it the file is only 12 MB).\n\n[Barrel_02 08.zip](Barrel_02_08.zip)\n\nNormal map baked from Highpoly model to Lowpoly model:\n\nIf you disconnect the two materials on the highpoly model and just use a default Principled shader, it bakes fine.\n\n\nThe baking process crashes at various stages. First bake crashed after an hour or so, next attempts crashed much quicker.\n\nCrash logs:\n\n[Barrel_02 08.crash.txt](Barrel_02_08.crash.txt)\n\n[Barrel_02 07.crash.txt](Barrel_02_07.crash.txt)\n\n[Barrel_02 06.crash.txt](Barrel_02_06.crash.txt)", "GPU Subdivision: Wrong objects statistics information\nWindows 10\ni7-4790\n16 GB RAM\nRTX 2070\n\nBlender v3.4.1 (Steam)\n\nWrong objects statistics information in object mode when GPU Subdivision is enabled\n\n- Open `Rat.blend` file\n- Enable GPU subdivision\n- Rotate/move the bone\n- Switch to object mode (notice the viewport statistics)\n\n\n\n", "Apply base results in oversized mesh using Catmull-Clark.\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.83 (sub 13)\nWorked: Never\n\n\n\n[#75463.blend](T75463.blend)\n\n- Open file\n- Examine how subdivided object `original` looks like\n- Change number of subdivisions in Preview to 0\n- Click on Apply Base\n# Compare to form of subdivided mesh\n\nModified base mesh is slightly oversized.", "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", "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", "Remove DerivedMesh: subsurf-uv unwrap\nCurrently UV unwrap uses derived mesh, see: `construct_param_handle_subsurfed`", "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" ]

[ "vertex paint face selction display bug gpu subdivision\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0\n\nFace selection mode overlays in vertex paint mode produce drawing glitches when gpu subdivision is enabled.\n\n- Make sure {nav Preferences -> Viewport -> Subdivision -> GPU Subdivision} is enabled\n- Create Suzanne\n- Add Subdiv Modifier\n- Go to Vertex Paint Mode\n- Enable Face Selection Mode\n- Select Some Faces\n- If nothing weird happens zoom in and switch back and forth between vertex and face selection mode\n\nthis is how the error looks for every tested setup\nrandomly chaning when switching on and off face selection mode\n\n\nOnly happens if GPU subdivision is enabled\nAlso tested on following gpus all on Windows 10:\nGTX 980, GTX 1070, GTX 1080, RTX2070 Super, RTX 2080\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", "Crash on startup with 2.82 and Intel HD + Windows\nOperating system: Windows 10 Pro (1909)\nGraphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951\n\nBroken: 2.81, 2.82, downloaded from blender.org\nWorked: 2.80 worked.\n\nBlender crashes on start:\n\n```\nC:\\Program Files\\Blender Foundation\\Blender 2.81>blender.exe\nGPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.34 MiB.\nGPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB\n```\n\nThis appears to be similar to #69594.\n\n\n\n1. Download 2.81.\n2. Launch 'blender.exe'\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "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", "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\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", "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 on calling bpy.ops.mesh.loopcut in python script\nOperation system: macOS BigSur 11.6 (20G165) \nApple M1\n\nVersion 3.4.1 (3.4.1 2022-12-20)\n\nBlender crashes in background mode when you are calling bpy.ops.mesh.loopcut with overridden context\n\nRun Blender from cli with args:\n/path/to/bin --background --python bug.py\n[bug.py](bug.py)\n\n", "Render cause crash guide many time August 10, 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.39\n\nBroken: version: 3.2.2\n\nRender crash too many\n\nFor Mac only. Do not use Windows please.\n\n\n\n\n\nSee blender 3.2.2 on Cycle-x picture\n\n\nCommand + F12 then render for a while few minutes cause crash many times.\n\n[Blender report a ticket August 10 2022.zip](Blender_report_a_ticket_August_10_2022.zip)", "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", "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", "Crash on render on some of the frames\nOperating system: Linux-4.4.0-154-generic-x86_64-with-debian-stretch-sid 64 Bits\n8x Tesla V100 SXM2 NVLINK Accelerator Cards\nDual XEON Scalable 4208 CPUs\n192 GB RAM\n\nBroken: version: 2.82 (sub 7)\nI also tested recent 2.83 build\n\nBlender crash when it renders scene frames from 346-639, the rest of the frames are fine.\nIt crashes for CPU anf GPU as well.\n\nIn order to render above frames I workaround the assert:\n\n```\n--- a/intern/cycles/kernel/kernel_compat_cpu.h\n+++ b/intern/cycles/kernel/kernel_compat_cpu.h\n@@ -74,8 +74,10 @@ CCL_NAMESPACE_BEGIN\n template<typename T> struct texture {\n ccl_always_inline const T &fetch(int index)\n {\n- kernel_assert(index >= 0 && index < width);\n- return data[index];\n+ //kernel_assert(index >= 0 && index < width);\n+ if (index < 0) return data[0];\n+ else if (index >= width) return data[width];{F8410049}\n+ else return data[index];\n }\n #if defined(__KERNEL_AVX__) || defined(__KERNEL_AVX2__)\n /* Reads 256 bytes but indexes in blocks of 128 bytes to maintain\n```\n\nThe scene is complex and I couldn't make it very simply and narrow the problem.\nPlease find the scene attached.\n\n[animation_002_02_part01.blend](animation_002_02_part01.blend)\n\n1. Open Blender 2.82\n2. Open attached scene\n3. Set frame 346, start render (F12)\n4. After one minute or so it will crash\n\n\n", "Pack UV's crashes blender\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\n\nwith all uv's selected, using \"pack uv's\" crashes blender\n\nopen provided file. Go in edit mode. Select all\nin uv editor go UV > Pack UV\n\nBlender crashes\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", "Crash when using OCIO v2\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.0.0 Release Candidate\n\nWhen I used OCIO v2 config file and used Cycles for rendering with Optix, it worked for viewport rendering. But if I pressed F12 for final render, Blender 3.0 crashed when the render was finsihing.\nI tried with a few scenes even if the Blender default scene still crashed. Then I tried rendering with CPU, it still crashed.\nI also tried in Blender 2.93.5. It crashed again even if the render didn't start.\nI downloaded the OCIO v2 config file from ocio_v2_demo.html.\n\nWhen I used OCIO v1.2 config file, Blender worked perfectly.\n\n[test-ocio2.txt](test-ocio2.txt)\n- Set the OCIO environment variable to the location of the test-ocio2.txt config file.\n- Start blender and set Cycles as the render engine\n- F12\n\n-----\nOCIO v2 Config\n{[F12676993](image.png) size=full}\n\nBlender 3.0 crash video\n[Crash.mp4](Crash.mp4)\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" ]

[ "Blender Crashes When Saving\nMac OSX 10.6\nIntel Graphics Card\n\nBroken: 2.73.9 3d5df50\n\nAfter downloading the Blender 2.74 test release, I tried to save some of my files after editing and Blender crashed multiple times. Also I tried to save and export a Blender Game with the same result.\n\nThis - [bow-and-arrow.blend](bow-and-arrow.blend) is my Game engine file\n\n1. Open the file\n2. Make any change\nBlender Crashes\n3. Open file again\n4. Try to save as runtime\nBlender Crashes\n", "Blender crashes in saving any file\nOS: lubuntu 14.10\nCPU: Intel(R) Pentium(R) M processor 1.73GHz\nGraphic card :Mobile 915GM/GMS/910GML Express Graphics Controller\n\nBroken: Blender 2.73 (sub 9), Commit date: 2015-03-06 16:53, Hash cf1227d\nWorked: (optional)\n\nHi, I have already reported this error here (T43892) but I do not think the same thing, in that they talk about the game engine. I hope not to be redundant.\nI have tried to save in several mode the blender file and it don't save any Blender file.\nWith the previous version works very well. (2.73a)\n\nThis is the error that tells me the crash report.\n# Blender 2.73 (sub 9), Commit date: 2015-03-06 16:53, Hash cf1227d\n\n# backtrace\n./blender(BLI_system_backtrace+0x30) [0x95892c0]\n./blender() [0x8b5a91f]\n./blender() [0x8b5ab08]\n[0xb76f6c58]\n\nNo special operations, does not save even the default cube." ]

[ "Unnecessary Proportional editing in Sculpt Mode.\nOperating system: Windows-10-10.0.1709 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 and 2.82 (sub 1)\nWorked: (optional)\n\nthis is probably not a bug but more of a design since Sculpt mode now has regular transform tools.\n\nI accidentally found out that if you enable Proportional editing then going to Sculpt mode the Transform tools will show Proportional editing & it's hotkeys in the Status bar.\n\n * Enable Proportional editing in Object mode.\n * Enter Sculpt mode.\n * Use any tool of the Transform tools.\n", "Mask paint is invisible in Sculpt Mode.\nOperating system:Mac OS 12.3.1\nGraphics card: 24-core GPU (?)\n\n**Blender Version** 3.2.1\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nThe mask in sculpt mode is invisible. I have the overlay turned on and I don't have any unapplied modifiers. I also don't have any physics or particle systems turned on. \n\nThank you for your help.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Paint Mode: Masking Modes\nThis is an important task related to the implementation of Paint Mode and #96225.\n\n# Painting Modes & Selections\n\nIn the current painting modes there are various ways of masking. Including all of these in their current form in a single Paint Mode would lead to a muddled and confusing design.\nBut still, these ways of masking should be supported:\n\n- Masking per vertex (Like Sculpt Mode masking)\n- Masking per face (To achieve sharp edges on face corner color attributes and image textures)\n- Masking based on selection (Synched with edit mode)\n- Masking based on a texture (Stencil Mask)\n\n# Issue\n\nThese ways of masking are very different and currently implemented as completely separate features.\nMoving all of these with their current design to a new Paint Mode would lead to multiple masks and selections having to be enabled and managed at the same time, each with their own overlay.\nThis issue can already be observed in the current Texture Paint Mode when enabling any of the selection masking modes and stencil masking at the same time.\n\nThe ideal way moving forward in Paint Mode has to be by combining these masking methods into a single cohesive design without regression in functionality.\n\n# Proposal\n\n### Masking Modes\n\nThe proposal is to add three easily accessible “Masking modes” to choose which data is being used for the masking operations in Paint Mode.\nThese should be easy to switch between via the number keys. \nThis directly parallels the selection modes in edit mode, grease pencil and the UV editor. And just like in these other modes they should be interchangeably usable for intuitive and fast masking.\n\n\n\nThe 3 modes would let you:\n\n- **Mask Vertices** (Vertex float)\nSame behaviour as sculpt mode.\n\n- **Mask Faces** (Face bool)\nWill restrict the masking to only fill in entire faces as completely masked or unmasked. This is far more useful than trying to paint face float values, which will almost always result in a stepping effect.\n\n- **Mask Pixels** (Greyscale image texture))\nThis feature should replace the current “Stencil Mask”.\n\n### Converting Masks\n\nThese masking features are meant for loose and temporary masks, similar to selections in other modes. \nFor more permanent masking for material and texture mixing it would still be preferred to paint image textures and use them as masks in the material.\n\nWith that use case in mind, it would be easiest to implement to convert the mask to another domain and data type every time the masking mode is changed (Similar to selection modes in Edit Mode).\n\nAlternatively we could test a way of abstracting/propagating the selection between those modes but that could just end up as far more complicated, less predictable and for questionable advantages.\n\n### Edit Mode Syncing\n\nAn important task that is tied to this is to convert the mask of Paint Mode to the Edit Mode selection (and vise versa).\nThis way masks can be much more precisely created in Edit Mode.\nWhile switching between Edit Mode should not be required - masking in Paint Mode should be intuitive enough for most cases - some workflows rely on this for painting precise attributes and technical textures.\n\nSo keeping this functionality will be a priority!\n\n(There are even other potential advantages from considering a Paint Mode mask an Edit Mode selection, like assigning materials directly in Paint Mode. \nThe design of #97903 could help in making this more clear.\n\n# Sculpt Mode\n\nIf these masking modes should be included in Sculpt Mode as well is questionable. \nMasking faces and based on an image texture is no use if you are only able to affect vertices with all tools available.\nThe only advantage would be to avoid mask conversion on mode switching (Which shouldn't be a problem) and to allow painting face corner color attributes with the Sculpt Mode painting toolset (Which is not what Sculpt Mode is for. For sharper edges you should increase the amount of geometry or use the bigger Toolset of Paint Mode).", "Sculpting: Draw Sharp brush has sharp point at the beginning of the line\n**Broken:** \nBlender version: 2.93.7, 3.0, 3.1 (27.12.2021)\n\n**Short Description**\nDraw Sharp brush line is uneven at the beginning of the line there is a sharp point. It can be seen with large radius of the brush.\n\n**Steps to reproduce:**\n1. Default scene\n2. Remesh cube, Voxel Size 0.01.\n3. Brush \"Draw Sharp\", Radius 200-500 px.\n\n\nTest File:\n[#94463.blend](T94463.blend)", "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", "Initial stroke delay - clay strips\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.1\n\nWhen you start a stroke in sculpt mode with the clay strips brush, it takes some movement for it to start registering. Previous versions of Blender didn't have this problem. See video to understand better (sorry for the low audio volume, if you can, wear headphones or raise the volume).\n\nJust start a stroke with clay strips, it will take a drag to appear. It can be reproduced in default room.\n\n", "Sculpt Mode Border Hide Tool Todo\n## Sculpt Mode Border Hide Tool Todo\n * - [x] {icon circle color=red} When this tool is selected, it currently shows the wrong tool settings which affect the brushes, not this tool. These should not be visible when this tool is active.\n * - [ ] {icon circle color=yellow} We should add a tool setting to add/remove the mask as you drag. Currently, the only way to remove from border hide, is very hidden: You drag with RMB. This could become more consistent and more discoverable if we added the same Add/Remove buttons as with other Sculpt tools", "GN +motion blur =bi-direction\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 522.30\n\nBroken: version: 3.5.0 Alpha\n\n\n\n[Мошкара.blend](Мошкара.blend)\n\n", "3D Cursor & Origin overlays should be grayed out if hidden by current mode/tool\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\nThe 3D Cursor and Origins are not displayed in painting modes as well as sculpt mode. \nThe overlay popover does not give feedback on this though.\n\n\nThe overlays should be grayed out in the modes and tools where it is hidden. \nIdeally there should be exceptions to this rule, like while the 3D Cursor is transformed (already implemented) and when the current Tool is using it (Annotation Tools).", "Mask from Cavity blurring artefacts\n## The Issue\n\nThis is a limitation of how this new feature was implemented, but I'm still adding this to the bug tracker so we are aware that this is meant to be fixed at some point.\nWhen adding blurring steps to the cavity masks in sculpt mode, either with the \"Mask From Cavity\" menu operator or via the auto-masking options, it will not lead to an ideal result.\nThe blurring very strictly follows the triangulation of the mesh causing streaks along the surface, and poles grow into star patterns.\n\n\n\n| Smooth Mask Filter | Cavity Blur | \n| -------- | -------- | \n|  |  | \n\n\n\n\n\nThis needs a deeper look into alternatives to blur the mask in the operator.", "Sculpt Mode Stroke Perfomance\nThis task intention is to plan how to tackle the stroke performance issue that sculpt mode has. This is the issue we are trying to solve:\n\n[2020-08-08 13-07-14.mp4](2020-08-08_13-07-14.mp4)\n\nThe plan is to avoid the slowdown that freeze the UI during the stroke. In any case, if the computer hardware is not enough to keep up with the mesh deformation, the stroke should lag consistently instead of freezing for several seconds.\n\nThis should not focus on:\n - Dyntopo performance (should be handled in a separate task as it has some specific performance issues).\n - Making large brush strokes and mesh filters faster.\n\nThese are the attempt the were made. There were some successful experiments, but none of them can provide the expected performance sculpt mode should have in a high end computer: \n\n### Control paint operator events rate\n\n- Dynamic Stroke Spacing [D8508](D8508): This is the solution with the most noticeable effect so far. In order to make this work, high frequency pen tablet events should be available in all platforms. This patch can be beneficial to merge also for not performance reasons as it will also allow to reduce the spacing of some brushes that need it. \n- Paint stroke step queue [D5676](D5676): This is not related to improve performance (it may even make performance worse), but to improve UX avoiding locking the UI. The idea was to use it for 2D painting were it works fine, but it 3D projection painting and Sculpt Mode it still has some issues.\n- Ignore INVETWEEN_MOUSE_EVENTS in grab brushes (in master since 2.81) [D5429](D5429): This also had a noticeable effect in the performance of these brushes.\n\n\n### Modify PBVH scheduler settings\n\n- Change Multires to limit the PBVH leaf size using vertices [D8454](D8454): This reduces the leaf limit for Multires. It improved performance in high end computers (Julien workstation). Before this patch, Multires was lagging with 80k vertices with 3 subdivisions levels.\n- Change PBVH leaf limit size [D8442](D8442): This has a noticeable effect in performance. Stroke performance usually improves when making the limit size lower, but this makes tools that modify all nodes slower (like elastic deform or the mesh filters). When increasing the limit size, stroke performance is worse, but tools that modify the whole mesh are faster.\n- PBVH Scheduler performance design task: #72943\n\n\n### Other info\n\nI tested sculpt mode in the following computers, all of them running Ubuntu:\n\n- Mini-PC media center: i3, 8GB integrated graphics.\n- Gaming Laptop: i7 9750H, GTX 1650, 16GB\n- Workstation: Threadripper 3990X, Radeon Pro VII, 128GB\n\nThis is my experience so far\n\n- Performance does not scale: The workstation and the mini-pc have the same stroke performance and lag problem. In the case of the mini-pc, performance is clearly limited by the GPU as the viewport lags with high poly meshes without doing any strokes.\n- Removing the normal recalculation completely before drawing the PBVH does not have any noticeable effect. If we can find a fix that only works for flat shading (so we can move these updates to somewhere else), it should be acceptable, \n- I did a refactor during the 2.82 development to unify all the loops for the Clay Strips brush as suggested in #68873. It didn't have any noticeable performance effect.\n- In 2.81 the scheduler was changed to TBB. Before that change, Sculpt Mode was noticeable faster disabling multithreaded sculpting. This option is no longer available.\n- This bug fix removed a heavy computation per vertex in clay strips. Even after the fix, the stroke lag is still there\n- Stroke lag is generally higher in Multires than in meshes, when we should expect Multires to be faster than meshes (less cache misses).\n- In the gaming laptop with the EEVEE PBVH drawing enabled, stroke performance is almost the same (if not better) in EEVEE than in workbench. I did't test this with the workstation because I can't guarantee that the new GPU is working correctly. This makes me think that this problem is not related to a viewport drawing issue.\n- The default Sculpt Vertex Colors paint brush does not need normal updates, sampling the area normal or updating the nodes bounding boxes, but it is also affected by the stroke lag issue. \n- The Brush cursor is using a PBVH raycast and a multithreaded task to sample the area normal, but it is not affected by the lag, no matter how fast you move the cursor over the mesh. \n\n### Performance reference benchmark\n\nEven this is not an easy to define thing, we should have a fixed performance reference benchmark for sculpting for supported devices. This should allow people to report performance issues with different setups instead of just assuming that performance is bad because Blender is not a especialized software, so we can have more data to debug this issue (the same way if we notice that moving elements in edit mode on a 20 vertices mesh lags, we know it is a bug).\n\nAs and initial proposal, I would expect that with a 500k - 750k vertices mesh, Sculpt Mode should never lag regardless of the stroke size or stroke speed, in any computer that meets the minimum requirements to run Blender.\n\n\n\n\n\n\n\n", "Backface culling setting applies in Material Preview shading and affects selectability\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 (sub 3)\nBroken: version: 2.83 (sub 17)\nWorked only if face orientation on in 2.82a release\n\nBackface culling setting applies in Material Preview shading and affects selectability.\nExpected: if it is visible and selectable, I should be able to select it.\n[2020-05-26_00-02-02.mp4](2020-05-26_00-02-02.mp4)\n\n**Steps to reproduce**\n[nonselectable.blend](nonselectable.blend)\n\n- Open file\n- Try to select octagon", "Proportional Editing in Mask mode only works with \"G\", not with slide_marker\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.93.0 Alpha\nWorked: never\n\nCould be that this is more a design issue, but it feels very inconsitent to me and I cannot find a good reason for it.\nWhen proportional editing is enabled in Mask mode, it only works when you use \"g\" or the move tool to actually grab the mask control point and move it, but when you use the left mouse button (= \"slide_marker\") it only moves the current CV, without proportional editing. I am not sure there should be a difference between \"grab and move\" and \"slide_marker\" when it comes to proportional editing.\nWith keymap set to right click select this is maybe less of an issue because you can right click and drag to tweak the curve (and thereby using proportional editing), but with the default of left click select there is only slide_marker available as a tweaking option, and that does not use proportional editing. \nI suggest to have proportional editing during slide_marker as well. \n@SeanKennedy what do you think about this?\n\nOpen this file:\n[mask_drawing.blend](mask_drawing.blend)\nUse use left mouse button to slide any of the mask points. No falloff is in use.\nNow try the same with \"g\". Proportional editing is in use.", "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", "Clay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop) \nOperating system:\n\nDevice name\tDESKTOP-V97J8T0\nProcessor\t12th Gen Intel(R) Core(TM) i7-12700F 2.10 GHz\nInstalled RAM\t32.0 GB (31.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\nPen and touch\tPen support\n\nGraphics card:\n\n3070 RTX\n\nBroken: 3.3.1\nWorked: 3.2.2 \n\n\nClay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop). it works fine in blender when i push Wacom Intous tablet on max with pen\n\nVideo Link: 1J_NZ0-1Qqg" ]

[ "Stereoscopic Display Mode (Side-by-Side, Top-Bottom): Mouse Cursor stays monoscopic\nWorked: Never\n\nWhen in Side-by-Side Stereoscopic Display Mode, the mouse cursor is just shown on the left side of the stereoscopic UI.\n\nEnable Side-by-Side Stereoscopic Display Mode:\n - “Properties Editor” → “Output Properties” → “Stereoscopy”: Checkmark\n - Title Bar → “Window” → “Set Stereo 3d”: “Side-by-Side”\n - Title Bar → “Window” → “Toggle Window Fullscreen”\n\n\n\n" ]

[ "bpy.ops.constraint.apply crashes when owner='BONE' and in object mode\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 516.94\n\nBroken: version: 3.4.1\nWorked: unknown\n\nThe bpy.ops.constraint.apply operator crashes blender when targeting a bone constraint while in object mode. The attached blender file reliably causes the crash. It also seems to crash in pose mode at times, but I've so far been unable to recreate this in a small example file. See also [#97640](T97640) where a crash relating to the operator being used on objects has seemingly been fixed between 3.1.2 and 3.2\n\nto recreate simply open the blender file and run the script.\n[apply_bone_constraint_crash.blend](apply_bone_constraint_crash.blend)\n[apply_bone_constraint_crash.crash.txt](apply_bone_constraint_crash.crash.txt)\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", "Keep Alt Key not work in the F-Curve properties\nwin10 64bit, gtx1060\n\nBroken: 2.79a 8928d99270f\nWorked: (optional)\n\nKeep alt key for multiple objects not work in F-curve property ( N panel )\n\nOpen my .blend file, when I select multiple curves and keep alt key to twice the Interpolation or Easing option, it's just worked in one cure,not for all selected, if this is bug, please fix, it very useful for lots curves, else I must one by one to change those, thanks.\n\n\n\n[bug.blend](bug.blend)", "Use after free: Baking Rigid Body physics causes instant crash\nOperating system: macOS 10.15.7\nGraphics card: AMD Radeon Pro 5500M 4 GB / Intel UHD Graphics 630 1536 MB\n\nBroken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, 2.93.0 Beta, branch: master, commit date: 2021-04-28 22:25, \nbroken: f7b22fc3d27113715e8726c69ab3264e1d487439\nWorked: \n\nBaking the Rigid Body world physics causes Blender to crash either instantly, or after baking less than 100 frames (it varies). Interestingly, a friend with the PC version of 2.92 says the project works fine, no crashes whatsoever.\n\nOpen the project. Make sure Allow Negative Frames is on under Preferences/Animation. Go to the Rigid Body World and hit bake.\n\n[physics test b.blend](physics_test_b.blend)\nAsan report: [T88113_asan_report.txt](T88113_asan_report.txt)", "Old blend file corrupts to crash blender, I guess\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.14761 Core Profile Context 20.11.2 27.20.14540.4003\n\nBroken: version: 3.0.0\n\nCrashes here and there. RN I witness crush form select/deselect. help plz ;c\n\nI do, tho, have installed two PROBABLY outdated addons BUT in new file crash doesn't seem to happen.\n\nThe problem is - Idk exact steps, but overall it takes to select/deselect all/smth at all few times\n\nSteps\n- Open the provided .blend below\n- Enter edit mode on the main SN4K3Mesh\n- Select-All, De-Select-All (Repeat)\n\n[#94213-asan.txt](T94213-asan.txt)\n\n```\n# Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF715993808\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n```\n```\n# Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF71599380C\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n```\n\n[SN4K3.blend](SN4K3.blend)\n\n[SN4K3.crash.txt](SN4K3.crash.txt)", "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", "Material Preview (EEVEE) can cause access violations when switching to edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.3\nWorked: N/A\n\nSwitching to edit mode with material preview (EEVEE) enabled results in a crash \n(Log from my machine produced with the joined blender file also joined to this report)\n\nusing the file joined in this report:\n- Open the scene\n- Select \"Circle.039\"\n- Switch to material preview\n- Attempt to enter edit mode on \"Circle.039\"\n\n", "Crash clicking on Material Preview\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nSometime, clicking on Material Preview button (Eevee) Blender 2.92 crashes without a reason.\nSee file and log attached\nThank you\n[Rocks_Pack.crash.txt](Rocks_Pack.crash.txt)\n\n-\n\n[Rocks_Pack.blend](Rocks_Pack.blend)", "Specific Rig Crashes blender when going into pose mode\nOperating system: Linux-5.10.7-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.92.0 Alpha\nWorked: not sure but pre 2.80\n\nThis specific file, containing only one armature, crashes when selecting the armature and attempting to enter pose mode.\n\nFirst load the included file, then:\n- select the rig if it isn't already selected,\n- press ctrl tab or otherwise enter pose mode\nat this point blender crashes.[bug_posemode.blend](bug_posemode.blend)\n\n", "Cycles Rendering of project causes crash of program.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Windows 11)\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\nNot sure if you need textures, can provide if needed.", "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", "Crash probability opening .blend with imported USDs\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 512.15\n\nBroken: version: 3.3.0\n\nOpening files with imported USDs (animated high poly) causes a crash, on some files, with probability of crash, depending on file 25-80%, on some - 100%.\nWhat possibly leads to increased chances of crash is replacing materials or multiple USDs.\nIdentical geometry via Alembic works fine.\n\n - Opening the file should lead to a crash\n[usd_crash.zip](usd_crash.zip)\n\n\n", "PyAPI: Crash when trying to draw a PointerProperty in the UI.\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.56\n\nBroken: version: 3.1.0 Alpha\n\nMy addon registers a PropertyGroup with a PointerProperty within, which wants to point at Objects.\nThis PropertyGroup is added to bpy.types.PoseBone.\nSometimes, when trying to draw this PointerProperty, Blender crashes.\n\nThe stack trace seems to be an infinite loop between these two asserts:\n```\nBLI_assert failed: source/blender/blenkernel/intern/idprop.c:741, IDP_GetPropertyFromGroup(), at 'prop->type == IDP_GROUP'\nBLI_assert failed: source/blender/blenkernel/intern/idprop.c:687, IDP_AddToGroup(), at 'group->type == IDP_GROUP'\n```\nand with some other stuff in between.\n\n- Zip of a .blend file and the addon (stripped down to just a few lines of code):\n[property_draw_crash.zip](property_draw_crash.zip)\n- Note that although the addon was originally about bone gizmos, all the widget drawing related code is completely gone. It's now just a PropertyGroup, a PointerProperty, and a Panel, and nothing else.\n- Install the addon.\n- Open the Blend file. The Properties Editor should already be set to the Bone tab, with the Viewport Display panel opened, which is where the addon will attempt to draw the property.\n- Enable the addon. It should crash with the above stack trace.\n\n[props_draw_crash-2021-11-12_13.14.46.mp4](props_draw_crash-2021-11-12_13.14.46.mp4)", "API's new context.property causing immediate Blender access violation crash.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked: N/A\n\ncertain properties cause immediate access violation when using the new context.property which was introduced recently. See: 6ba0346797f43cd73eb1003ce65a62b8409203fb and 107280\n\n\n\n1. open attached blend file makins sure 'load ui' is ticked in the file open options.\n2. click the play button on the script editor to register the shortcut key\n3. hover the mouse over the font size in the text editor's font size property\n \n4. press tab\n5. immediate access violation is triggered in the poll function on line 28.\n\n", "Crash undoing in certain scenario (disabling Global Undo)\nOperating system: Linux-5.10.12-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.82a\n\nCrash undoing in certain scenario (disabling Global Undo)\n\nFrom the default startup file (order of operations is important here):\n- move the cube (could be any objectmode operator) {key G Z 3}\n- disable `Global Undo` in Preferences {key F4} > `Preferences` > `System` > uncheck `Global Undo`\n- add an armature {key Shift A} > `Armature`\n- go to pose mode\n- select bone\n- move bone\n- Undo {key Ctrl Z}\n - > crash\n\n```\n1 BKE_scene_object_base_flag_sync_from_base scene.c 2914 0x35b41a9 \n2 BKE_scene_set_background scene.c 2125 0x35b2957 \n3 setup_app_data blendfile.c 386 0x4b63950 \n4 setup_app_blend_file_data blendfile.c 416 0x4b639e4 \n5 BKE_blendfile_read_from_memfile blendfile.c 524 0x4b63e38 \n6 BKE_memfile_undo_decode blender_undo.c 88 0x4b62cc0 \n7 memfile_undosys_step_decode memfile_undo.c 193 0x486eb47 \n8 undosys_step_decode undo_system.c 214 0x4bb97ec \n9 BKE_undosys_step_load_data_ex undo_system.c 809 0x4bbb2df \n10 BKE_undosys_step_undo_with_data_ex undo_system.c 870 0x4bbb4a4 \n11 BKE_undosys_step_undo_with_data undo_system.c 880 0x4bbb4d3 \n12 BKE_undosys_step_undo undo_system.c 889 0x4bbb511 \n13 ed_undo_step_direction ed_undo.c 278 0x486c907 \n14 ed_undo_exec ed_undo.c 489 0x486d214 \n15 wm_operator_invoke wm_event_system.c 1332 0x3a17b06 \n16 wm_handler_operator_call wm_event_system.c 2161 0x3a198e3 \n17 wm_handlers_do_keymap_with_keymap_handler wm_event_system.c 2486 0x3a1a617 \n18 wm_handlers_do_intern wm_event_system.c 2782 0x3a1b591 \n19 wm_handlers_do wm_event_system.c 2914 0x3a1bafc \n20 wm_event_do_handlers wm_event_system.c 3445 0x3a1d2a3 \n```\n```\n \n```\n\n\n" ]

[ "Crash with keyframing\nWindows 10 64 bit\nIntel Core i7-6700K\n32 GB RAM\nGTX 1080\n\nBroken: 2.8 2d720f51cd7 compiled in debug mode\nWorked: it works when compiled in release mode\n\nCrash when keyframing a property, deleting the keyframe and inserting the keyframe again.\n\n\n- Start blender in debug mode.\n- Select default cube if it not selected.\n- From the property panel, set the keyframe for the location (or any animatable property).\n- Delete the keyframe.\n# Keyframe the property again.\n\nI've also made a small video showing the issue: watch?v=AZUsa6vTnYY", " animate property crash\nOperating system: Operating system: windows10\nGraphics card: Nvdia GeForce GT 610/PCIe/SSE2\n\nBroken: Blender2.8 2018-12-04 hash: e7641b683427 \n\n animate property crash\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7497096A0\nModule : c:\\blender-git\\build_windows_Full_x64_vc14_Release\\bin\\Release\\blender.exe\n\n1. open blender\n2. open material panel\n3. click Screen Space Refraction animate property 3 time\n4. crash\n\n\n" ]

[ "Blender segfault if Bake Line Art\nOperating system: Debian Linux Stable 11\nGraphics card: Intel internal UHD Graphics 630 (driver: i915)\n\nBroken: 3.2.2 - 3.6.1 official releases\n\nBlender segfault if Bake Line Art.\n\nConsole:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault\n```\n\nFile /tmp/blender.crash.txt:\n```\n# Blender 3.2.2, Commit date: 2022-08-02 18:15, Hash bcfdb14560e7\nbpy.ops.object.delete(use_global=False, confirm=False) # Operator\nDeleted 1 object(s) # Info\nbpy.ops.object.gpencil_add(align='WORLD', location=(0, 0, 0), scale=(1, 1, 1), type='MONKEY') # Operator\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.gpencil_modifier_add(type='GP_LINEART') # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xc1619d0]\n./blender() [0x11da18d]\n/lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f97f7664d60]\n./blender(MEM_lockfree_allocN_len+0x7) [0xc16e1e7]\n./blender(MEM_lockfree_dupallocN+0x14) [0xc16e624]\n./blender(BKE_gpencil_stroke_duplicate+0x1a) [0x11f926a]\n./blender(BKE_gpencil_frame_copy_strokes+0x42) [0x11f94c2]\n./blender() [0x1207d97]\n./blender(BKE_gpencil_prepare_eval_data+0x1b7) [0x1208b07]\n./blender(BKE_object_handle_data_update+0x2fe) [0x12af9ae]\n./blender(BKE_object_eval_uber_data+0x2f) [0x12afc7f]\n./blender() [0x1913f22]\n./blender() [0x19140f2]\n./blender() [0xc16574d]\n./blender() [0x1796a35]\n./blender() [0x1796ceb]\n./blender() [0x1783d27]\n./blender() [0x1790720]\n./blender() [0x179275c]\n./blender() [0x1792959]\n/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f97f807aea7]\n/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f97f7727a2f]\n\n# Python backtrace\n```\n\n1. Open Blender\n2. Click to default box and delete it (press del)\n3. Press Shift+A\n4. Select \"Grease Pencil\" - \"Monkey\"\n5. At right area select \"Modifier Properties\"\n6. Click \"Add Modifier\"\n7. Select \"Line Art\"\n8. At bottom of this area click \"Bake\" - \"Bake Line Art\"\n9. Segfault here\n\n", "Crash playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "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 crashes with certain geometries (e.g. tweaked Jiggly Pudding simulation demo file)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 4.0.0 Alpha\nWorked: Unsure\n\nWith certain geometries, Blender will freeze then crash. I have included a demonstration in the video attached below:\n<video src=\"attachment\" title=\"Jiggly Pudding Crash.mp4\" controls></video>\n\n1. Download the Jiggly Pudding demo from demo-files/\n2. Follow the steps outlined in the video attached above. The steps in the video are as follows:\n a. Open the Jiggly Pudding file.\n b. Select the Pudding and open a geometry node editor.\n c. Inside the Simulation zone there is a node with the title \"Scale\". Change the Scale from 0.85 to 10 or something higher.\n d. Open a 3D viewport (if you haven't already) and press play in the time line.\n e. Blender will freeze and crash.\n\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", "Changing Resolution Preset doesn't allow to Undo\nBroken: 3.6.0\n\nChanging Resolution Preset and then trying to undo doesn't work, like if the action is not registered.\n\n\n- Open Blender\n- Click on the Format panel on the right icon to change preset\n- Select a preset\n- Undo\n\n", "Edge Slide via the GG shortcut can show incorrect selected checkboxes\n%%%--- Operating System, Graphics card ---\nWindows 8 x64, GTX560SE\n\n - Blender version with error, and version that worked ---\n2.67 r56888\n\n - Short description of error ---\nEdge Slide via the G-G shortcut can show incorrect selected checkboxes in Tools Shelf: eNwW8Kj.gif\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\nOpen attached .blend file. With an edge selected, use \"Edge Slide\" button in Tool Shelf. Click on checkbox \"Correct UVs\". Select another edge and now use Edge Slide via the G-G shortcut - tool behaves as if \"Correct UVs\" selected, but it's showing unchecked in Tools Shelf.%%%", "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\".", "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)", "Crash when playing animation in rendered view (cycles)\nOperating system: macOS-12.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0, 3.5\nWorked: unknown\n\nPlaying animations in cycles rendered view frequently crash blender. With the attached file I consistently get a crash within 1-2 minutes of starting the animation.\n\nThe crashes do not occur when running the intel version through rosetta. They occur much faster/more often when using the CPU than when using the GPU.\n\nOpen attached file\nSwitch to rendered view (Crashes with and without Metal preference)\nPress spacebar to play\n\n[Boat boating.blend](Boat_boating.blend)\n[Animation crash.txt](Animation_crash.txt)\n```\nThread 17 Crashed:\n0 Blender \t 0x10319354c tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 340\n1 Blender \t 0x103193644 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 588\n2 Blender \t 0x103192c60 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 184\n3 Blender \t 0x103183300 tbb::internal::arena::process(tbb::internal::generic_scheduler&) + 252\n4 Blender \t 0x10318c3b8 tbb::internal::market::process(rml::job&) + 40\n5 Blender \t 0x10318d6b0 tbb::internal::rml::private_worker::run() + 288\n6 Blender \t 0x10318d584 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n7 libsystem_pthread.dylib \t 0x1b39cd4ec _pthread_start + 148\n8 libsystem_pthread.dylib \t 0x1b39c82d0 thread_start + 8```", "In blender 3.5, Edge Crease in 3D view isn't overlaid.\nOperating system: macOS-13.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 580 1.2\n\nBroken: version: 3.5.1\n\nIn blender 3.5, Edge Crease in 3D view isn't overlaid.\nIs it replaced with Vertex Crease?\n\n1. Select an object and toggle it into Mesh Edit Mode.\n2. Make sure ‘Creases' is selected in Mesh Edit Mode of Viewport Overlays.\n3. Select an edge and press shift+E to set Factor to 1.\n\n\n\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.", "Regression: Attempt to move object with Copy Location (with Offset) crashes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nA consistent crash when trying to move an object with COPY LOC w/ Offset enabled.\n\n\n1. Open the attached blend file\n\n2. Move the pre-selected object in any direction, you may have to do this two or three times\n\n3. program will crash with EXCEPTION_ACCESS_VIOLATION\n\nThis is happening every time.\n\n```\nStack trace:\nblender.exe :0x00007FF73E03C510 blender::bounds::min_max<blender::VecBase<float,3> >\nblender.exe :0x00007FF73E03BD30 blender::FunctionRef<void __cdecl(blender::Bounds<blender::VecBase<float,3> > &)>::callback_fn<<lam\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF7425212F0 blender::CacheMutex::ensure\nblender.exe :0x00007FF73E042390 BKE_mesh_minmax\nblender.exe :0x00007FF73E0409F0 BKE_mesh_boundbox_get\nblender.exe :0x00007FF73E02E940 BKE_object_boundbox_get\nblender.exe :0x00007FF73E02F410 BKE_object_dimensions_get\nblender.exe :0x00007FF73E613520 RNA_property_float_get_index\nblender.exe :0x00007FF73E235050 dtar_get_prop_val\nblender.exe :0x00007FF73E235410 evaluate_driver\nblender.exe :0x00007FF73E168590 calculate_fcurve\nblender.exe :0x00007FF73E156270 BKE_animsys_eval_driver\nblender.exe :0x00007FF73E4464F0 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF73E446320 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7425175C0 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FF9998CA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FF9A5D192C0 recalloc\nKERNEL32.DLL :0x00007FF9A6F72690 BaseThreadInitThunk\nntdll.dll :0x00007FF9A882AA40 RtlUserThreadStart\n```\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.", "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" ]

[ "Crash Blender 3.0 Edge Becel Weight\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 3.0.0 Alpha\n\nWhen click on Edge Bevel Weight from edge menú, blender 3.0 crashes.\n\nGo into edit edges mode, select any edge, then go to edge menu and click Edge Bevel Weight, then blender crashes.\n\nSorry if my english is not so good, I am from Colombia.\n\nThanks. Have a nice day.\n\n\n[Blender 3 crash Edge weigth.blend](Blender_3_crash_Edge_weigth.blend)\n\n", "Crash when setting Edge Weight/Crease\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\n\nCrash occurs 'every time' when trying to apply a Crease setting to a row of Edges.\n\n\n\nWith default cube:\n- Select at least 2 edges \n- Press Shift-E for Edge Crease \nBlender crashes.\n\n" ]

[ "Normal map bug in Blender 2.9 / 3.0\nOperating system: Windows 10\nGraphics card: NVIDIA Geforce GTX 1050 Ti\n\nBroken: Blender 2.93 / 3.0 (stable version)\nWorked: Blender 2.83 (stable version)\n\nWhen applied a precedural texture (noise, Voronoi etc.) as a normal map in Node editor, the boundaries of the polygons stand out and it will look like a block. \nThere was no such problem in 2.83.\n\nCreate a mesh. Add a procedural texture on the Shading tab and apply it as a normal map.\n[#94139.blend](T94139.blend)\n\n\n\n", "Strange background grid pattern appears on the compositor panel\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.9079\n\nBroken: version: 2.93.5\nWorked: 2.91.2\n\nStrange grid pattern appears on the compositor background when zooming in (when backdrop is on).\n\nThis is what it should looks like:\n\n\nThis is what it actually looks like:\n\n\nAnd this only happens when I zoom in. At a very far-away view the background gradually becomes normal:\n\n\n\n\nThis does not happen on my other devices, so I think it might be a hardware compatibility problem. Also, I had the latest graphic driver installed and the graphic card supports OpenGL 4.6:\n\n\n- Open blender\n- Switch to the compositor workspace,\n- Enable backdrop\n- zoom in.\n\n", "Viewport Z-Bias & retopology overlay related issues\nSince this is being reported frequently and retopology overly has caused some weird issue with mask display as well previously, it's best we keep track of them in a central place so we could check if any particular fix is working for all situations:\n\n------\n\nProblem still presents:\n\n- Retopology overlay affecting other parts of the drawing/picking operation: #109115 #107768 ~~#109277~~ ~~#107411~~\n- (Potentially related) Selecting when X-Ray turned on is not visually effective and then switching to face mode crashes: #110136\n\n------\n\nFixed:\n\n- ~~Wireframe visible in close distances: #110048 #109040 #109514 #109499 #109685~~\n- ~~Retopology overlay 0 z offset problem: #109662~~\n\n-------\n\nProbable cause:\n\nAs suggested in 107768#issuecomment-937545 , I believe the problem here is that\n\n1. `DRW_object_is_in_edit_mode` does not exclusively check if object is in edit mode, but it combines other logics that affects drawing and stuff.\n2. `XRAY_ENABLED` marco is not always accompanied with `RETOPOLOGY_ENABLED`, this leads to inconsistencies in the user interaction and the display.", "Material setting \"show_transparent_back\" (Show Backface) gives weird results\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nMy materials are messed up by having blend mode set to \"Alpha Blend\" and \"Show Backface\" set true.\n(The checkbox for \"Show Backface\" pops up if a materials blend mode is set to Alpha Blend\")\n\nIs this normal behaviour?\nThe intend here was to see every side of the cube with a bit of transparency.\n\n[ShowTransparentBackBug.blend](ShowTransparentBackBug.blend)\n1. Add a Cube (subdivide a few times) and give it a material\n2. Go to material settings and set the materials...\n- Blend mode to \"Alpha Blend\"\n- Backface Culling to False\n- Show Backface to True", "Bug while moving vertices with mirror & subdivision modifier\nOperating system: Windows 10 64-bit\nGraphics card: ATI Radeon HD 5670\n\nBroken: 2.82\nWorked: at least 2.8\n\nWhen I try to move a vertice it seems like the mirror modifier gets applied in an odd way. The result even changes when moving the camera or hide one of the images I use for reference. In fact it becomes distorted when hiding the images.\nThe following link is a recording of my screen:\nview?usp=sharing\nI encountered this bug only recently. The file itself is older and I do not remember which version I used (since I use it via Steam I did not pay attention to the automatic patches).\n\n1. Open this file [Bugged Project.blend](Bugged_Project.blend)\n2. Disable visibility of Subdivision modifier for Edit Mode (which should already cause the bug)\n3. Move a vertice\n\n[system-info.txt](system-info.txt)", "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", "Can't see wireframe (vertex, selected components) through semi-transparent object\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 10)\nWorked: c26f470cfeea is last I have by hand\n\nIn the viewport, you can't see wireframe (vertex, selected components) through a semi-transparent object\n\n[75106.blend](75106.blend)\n1 - Create 2 objects one behind the other \n2 - Make front object semi-transparent (via Object properties > Viewport Display > Color > Alpha\n3 - Select the second object in Edit mode\n\n", "Workbench: Strange anti-shadow when clipping cuts landscape\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.1.2\n\n\nAs title says. This shadow looks like this:\n\n\nDemo:\n[2022-05-06_01-02-27.mp4](2022-05-06_01-02-27.mp4)\n\nYou can test it by your own with my file\n[WB shadowbug.blend](WB_shadowbug.blend)\n\n", "Camera Background image is appearing greyish in 3D Viewport \nOperating system: Windows 10\nGraphics card: Nvidia GTX 1080Ti\n\n**Blender Version** 3.2.1\nBroken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac9e\nWorked: \n\nCamera Background image is appearing greyish in deep black area in 3D Viewport but showing completely normal in Image editor section and renders. \nEven after turning on \"View as Render\", problem is still there.\n \nOpen the attached blend file.[Blender BG Bug Report.blend](Blender_BG_Bug_Report.blend)", "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)", "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks", "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)", "Bevel Bug\nblender-2.80-07765499abee-win64 \n\n**cylinder :**\non the cylinder with a lot of segments, bevel doesn't merge in one point. Create nice see n-gon(normal we must see the only verts in one point)\n\n\n**Cube :**\nThe middle loop has deformed when we bevel sharp corner for small mesh. On the large mesh, we cant see this deform .\n\n\n[Cylinder_Bevel_Bug.blend](Cylinder_Bevel_Bug.blend)\n\n[Cube_Bevel_Symmetry_Bug.blend](Cube_Bevel_Symmetry_Bug.blend)\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", "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" ]

[ "Wireframe is not displayed correctly with reference images on empties\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GT 650M (2GB GDDR5) \nDELL 7720 Inspiron\n\nBroken:\n(2.80 , 6a5e8096973 , Branch: blender2.8, 2018-12-07 18:28)\nI didn't see that working in any 2.8 Alfa versions of Blender I used. I think it may be an old bug.\n\n\nWhen using reference images (Empties) and modeling in wireframe mode the wireframe is not visible (reference images are covering wireframe)\nThere is X-Ray slider under shading but it doesn't help. \n\n\n1 Setup Reference images using Empties/Images.\n2 Create simple mesh by boxmodeling\n3 add SubdivisionSurface modifier\n4 Separate parts of the mesh\n5 Enter Wireframe display mode or Solid display mode with Shading>Options>X-ray to 0\n6 Turn on 'Show whole screen transparent' next to wireframe button\n7 Pan/Orbit 3D view to see that wireframe is covered by reference images.\n\nOnly when nothing is behind the wireframe it is correctly displayed.\n\nexample file:[2.8-ref-images-02.blend](2.8-ref-images-02.blend)\n\nLink to animated GIF showing how it is visible on my PC (You will need to download it... dropbox does not play animaged gifs...:)\nWireframeOnRefImagesC.gif?dl=0\n\n\nIf there are any alternatives to see the wireframe of the mesh in front of reference images please write in the response to the ticket. As far as I know background images are removed from 2.8 so users can only use Empty-based reference images.\n\nThanks for your great work on Blender 2.8 by the way!", "2.8 The display of wireframes in front of background images seems to be working incorrectly\nits my first bug report so sorry in advance\n\n**System Information** \nOperating system: win 10\nGraphics card: GTX 1080\n\n**Blender Version** blender 2.80.0 16fc62e15f0 windows 64 date: 2018-12-12 01:18\n\n\n**Short description of error** \n\nIn wireframe wiev with x-ray enabled background images seem to be covering the wireframes of objects in front of them. Seems to be working fine when you place the image in the front and reduce its transparency\n\n\nImport a background image and place some geometry in front of it, whether its in perspective or in ortho does not seem to matter. switch to wireframe wiev and enable x-ray.\n\n\n" ]

[ "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)", "blender crash if boolean + very very big scale\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2.1, 3.2\n\n[2022-07-21 19-15-24.mp4](2022-07-21_19-15-24.mp4)\n\n1. add boolean modifier\n2. scale any object on very very big value", "Crash after executing the script\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.1 Release Candidate\n\nApplication crashes when clicking on the script run button\n\n1/ launch Blender\n2/ click on \"Scripting\" tab; click \"New\"\n3/ paste the following chatgpt generated script and run it: \n```\nimport bpy\nfrom math import sqrt, sin, cos\n\n# Define the vertices of the tetrahedrons\nvertices1 = [\n (1, 1, 1),\n (-1, -1, 1),\n (-1, 1, -1),\n (1, -1, -1)\n]\n\nvertices2 = [\n (1, -1, -1),\n (-1, 1, -1),\n (-1, -1, 1),\n (1, 1, 1)\n]\n\n# Define the faces of the tetrahedrons\nfaces1 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\nfaces2 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\n# Create new meshes and objects\nmesh1 = bpy.data.meshes.new(\"Tetrahedron1\")\nobj1 = bpy.data.objects.new(\"Tetrahedron1\", mesh1)\n\nmesh2 = bpy.data.meshes.new(\"Tetrahedron2\")\nobj2 = bpy.data.objects.new(\"Tetrahedron2\", mesh2)\n\n# Set the object locations and scene context\nobj1.location = (-2, 0, 0)\nbpy.context.scene.collection.objects.link(obj1)\n\nobj2.location = (2, 0, 0)\nbpy.context.scene.collection.objects.link(obj2)\n\n# Create the vertices and faces of the meshes\nmesh1.from_pydata(vertices1, [], faces1)\nmesh1.update(calc_edges=True)\n\nmesh2.from_pydata(vertices2, [], faces2)\nmesh2.update(calc_edges=True)\n\n# Hinge the tetrahedrons together by one edge\nedge1 = mesh1.edges[0]\nedge2 = mesh2.edges[2]\n\nbpy.ops.object.select_all(action='DESELECT')\nobj1.select_set(True)\nobj2.select_set(True)\n\nbpy.context.view_layer.objects.active = obj2\nbpy.ops.object.mode_set(mode='EDIT')\nbpy.ops.mesh.select_all(action='DESELECT')\nedge2.select = True\nbpy.ops.mesh.edge_face_add()\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Add an armature to the tetrahedrons\nbpy.ops.object.armature_add()\narmature = bpy.context.object\narmature.name = \"HingeArmature\"\narmature.location = (0, 0, 0)\n\n# Add bones to the armature\nbpy.ops.object.mode_set(mode='EDIT')\nbone1 = armature.data.edit_bones.new('Bone1')\nbone1.head = (0, 0, 0)\nbone1.tail = (-2, 0, 0)\nbone1.use_deform = False\n\nbone2 = armature.data.edit_bones.new('Bone2')\nbone2.head = (0, 0, 0)\nbone2.tail = (2, 0, 0)\nbone2.use_deform = False\n\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Parent the tetrahedrons to the armature\nobj1.parent = armature\nobj1.parent_type = 'BONE'\nobj1.parent_bone = 'Bone1'\n\nobj2.parent = armature\nobj2.parent_type = 'BONE'\nobj2.parent_bone = 'Bone2'\n\n# Animate the hinge\nframes = 30\n\nfor frame in range(frames):\n bpy.context.scene.frame_set(frame)\n\n angle = frame / frames * 2 * 3.14159265\n\n bone1.tail = (-2 * cos(angle), 0, -2 * sin(angle))\n bone2.tail = (2 * cos(angle), 0, 2 * sin(angle))\n\n bone1.keyframe_insert(data_path='tail')\n bone2.keyframe_insert(data_path='tail')\n```", "Blender crashes with certain geometries (e.g. tweaked Jiggly Pudding simulation demo file)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 4.0.0 Alpha\nWorked: Unsure\n\nWith certain geometries, Blender will freeze then crash. I have included a demonstration in the video attached below:\n<video src=\"attachment\" title=\"Jiggly Pudding Crash.mp4\" controls></video>\n\n1. Download the Jiggly Pudding demo from demo-files/\n2. Follow the steps outlined in the video attached above. The steps in the video are as follows:\n a. Open the Jiggly Pudding file.\n b. Select the Pudding and open a geometry node editor.\n c. Inside the Simulation zone there is a node with the title \"Scale\". Change the Scale from 0.85 to 10 or something higher.\n d. Open a 3D viewport (if you haven't already) and press play in the time line.\n e. Blender will freeze and crash.\n\n", "Python API: \"NodeLink\" object in 'insert_link' callback of bpy.types.Node causes crash when reading some properties.\nOperating system: Linux-5.15.65-1-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.0\n\nTrying to dereference the properties of the sockets in the link crashes Blender.\n```\nException thrown: read access violation.\nntree was nullptr.\n```\n```\n>\tblender.exe!nodeFindNode(bNodeTree * ntree, bNodeSocket * sock, bNode * * r_node, int * r_sockindex) Line 2038\tC++\n\n \tblender.exe!rna_NodeSocket_node_get(PointerRNA * ptr) Line 2803\tC\n \tblender.exe!NodeSocket_node_get(PointerRNA * ptr) Line 46896\tC\n \tblender.exe!RNA_property_pointer_get(PointerRNA * ptr, PropertyRNA * prop) Line 3516\tC\n \tblender.exe!pyrna_prop_to_py(PointerRNA * ptr, PropertyRNA * prop) Line 1429\tC\n \tblender.exe!pyrna_struct_getattro(BPy_StructRNA * self, _object * pyname) Line 4287\tC\n \tpython310_d.dll!PyObject_GetAttr(_object * v, _object * name) Line 922\tC\n \tpython310_d.dll!_PyEval_EvalFrameDefault(_ts * tstate, _frame * f, int throwflag) Line 3593\tC\n \t[Inline Frame] python310_d.dll!_PyEval_EvalFrame(_ts *) Line 46\tC\n \tpython310_d.dll!_PyEval_Vector(_ts * tstate, PyFrameConstructor * con, _object * locals, _object * const * args, unsigned __int64 argcount, _object * kwnames) Line 5072\tC\n \tpython310_d.dll!_PyFunction_Vectorcall(_object * func, _object * const * stack, unsigned __int64 nargsf, _object * kwnames) Line 342\tC\n \tpython310_d.dll!PyVectorcall_Call(_object * callable, _object * tuple, _object * kwargs) Line 255\tC\n \tpython310_d.dll!_PyObject_Call(_ts * tstate, _object * callable, _object * args, _object * kwargs) Line 290\tC\n \tpython310_d.dll!PyObject_Call(_object * callable, _object * args, _object * kwargs) Line 318\tC\n \tblender.exe!bpy_class_call(bContext * C, PointerRNA * ptr, FunctionRNA * func, ParameterList * parms) Line 8690\tC\n \tblender.exe!rna_Node_insert_link(bNodeTree * ntree, bNode * node, bNodeLink * link) Line 1751\tC\n \tblender.exe!blender::ed::space_node::node_link_exit(bContext & C, wmOperator & op, const bool apply_links) Line 899\tC++\n \tblender.exe!blender::ed::space_node::node_link_modal(bContext * C, wmOperator * op, const wmEvent * event) Line 1055\tC++\n \tblender.exe!wm_handler_operator_call(bContext * C, ListBase * handlers, wmEventHandler * handler_base, wmEvent * event, PointerRNA * properties, const char * kmi_idname) Line 2380\tC++\n \tblender.exe!wm_handlers_do_intern(bContext * C, wmWindow * win, wmEvent * event, ListBase * handlers) Line 3283\tC++\n \tblender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3333\tC++\n \tblender.exe!wm_event_do_handlers(bContext * C) Line 3924\tC++\n \tblender.exe!WM_main(bContext * C) Line 643\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 579\tC\n \t[External Code]\t\n\n```\n\n- Open attached .blend file\n- run the script,\n- Create `New` Node Tree\n- add two nodes\n- connect them.\nBlender will crash to desktop.\n[custom_nodes_simple_bug_finder.blend](custom_nodes_simple_bug_finder.blend)\n\n", "Crash when rending animation w/simple physics sim\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0\nWorked: Spinning beach ball in 3.1 Alpha\n\nWhen selecting \"Render Animation\", the Rendering window starts to draw, and then the app crashes.\n\n\nFile attached. Just load and Select Render Animation.[simple-physics-crash.blend](simple-physics-crash.blend)\n\n", "Crash when selecting object on Mac\nOperating system: macOS-12.5.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.3.0\n\nSystem crash trying to open einar_hair.blend file\n\nDownload einar_hair.blend fle from ?asset=6072\nSelect any object.\n\nBlender will crash. Also hair is not visible. It's possible, that OS will crash as well. ", "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)", "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", "Geometry Nodes: viewer node and output geometries are shown together in Cycles render preview\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14800 Core Profile Context 22.5.1 30.0.15021.11005\n\nBroken: version: 3.4.0 Alpha\nWorked: n/a\n\n\n\nThe output geometry should not be shown when viewport preview in Geometry Nodes is active. But it's shown in Cycles render preview.\n\n[ViewportPrivewCycles.blend](ViewportPrivewCycles.blend)\n", "Crash using blender_debug_log.cmd and \"Reload Scripts\" in Cycles preview render\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nLoading Blender with blender_debug_log.cmd, it crash immediately when I try to reload the scripts if Cycles is running. This is not happening when launching blender.exe \n\nLaunch blender 2.8 using blender_debug_log.cmd.\nIn the view 3d, choose Cycles as render preview.\nIn the search bar, look for \"Reload Scripts\" and click on it.\nBlender Crash.\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n", "Normal map support in Cycles standalone\nWindows 8.1 64-bit\n\n**Cycles Version**\nd553b8de7180\n\n\nIn the latest version available in the Cycles standalone repository, commit d553b8de7180, using a normal map node in a shader graph will cause Cycles to crash. This behavior was not present in release 1.7.0 but has been added since then.\n\nThis looks to be caused by an improperly initialized member variable in the ccl::NormalMapNode type. Upon creating an object of type NormalMapNode, the ustring named 'attribute' is initialized such that attribute.c_str() will return a nullptr.\n\nCycles crashes when the nullptr used to construct a std::string in NormalMapNode::attributes in this bit:\n\n```\t\n\t\telse {\n\t\t\tattributes->add(ustring((string(attribute.c_str()) + \".tangent\").c_str()));\n\t\t\tattributes->add(ustring((string(attribute.c_str()) + \".tangent_sign\").c_str()));\n\t\t}\n```\n\n\nI have attached a simple cycles standalone scene that triggers this error here: [sample_scene.xml](sample_scene.xml)", "Assert in debug for dyntopo sculpt\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: Today main.\n\nSee attached stack trace file.\n\nIn debug:\n1. Sculp mode.\n2. Enable Dyntopo option.\n3. Do something.\nSee the crash.\n\n", "Blender crashes when calling ArgumentParser.parse_args() if sys.argv is anything other than [\"path/to/blender.exe\"]\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.1\n\nBlender crashes when calling `ArgumentParser.parse_args()` if `sys.argv` is anything other than `[\"path/to/blender.exe\"]`\nI discovered this bug while trying to run a script using the `exec()` function. Any script that uses argparse makes blender crash.\n\nYou can run this code\n```Py\nimport argparse\nimport sys\nimport bpy\n\nsys.argv = [bpy.app.binary_path]\nsys.argv.append(\"--some_arg\") # Comment this line and everything works fine\n\nparser = argparse.ArgumentParser()\nargs = parser.parse_args()\n```\n\n", "Blender crashes when click on shading tab \nOperating system: Windows 10, 64-bit\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 4.5.0 NVIDIA 445.87\n\nBroken: \n - version: 2.81 (sub 16), branch: v2.81_octane2019 (modified), commit date: 2020-02-11 11:57, hash: 81ff79b8cdb7, type: build date: 2020-02-11, 12:22:28\n - version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503, type: Release\n\nBlender crashes when clicking on the shading tab. It closes and goes back to the desktop.\n\nSee short description.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)" ]

[ "Crash When Adding Volume Object While in Workbench\nOperating system: macOS-12.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon `R9 M370X` OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.103\n\nBroken: version: 3.2.0 Alpha\nWorked: version: 3.2.0 Alpha\nCaused by f75449b5f2\n\nBlender crashes immediately after adding a volume object while in Workbench. That's... that's it really!\n\n- While in Workbench, Shift+A > Volume > Empty or Import OpenVDB...\n- Immediate crash or crash after confirming file dialogue\n\n[Blender-2022-02-05-171837.ips](Blender-2022-02-05-171837.ips)\n[blender.crash.txt](blender.crash.txt)" ]

[ "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). ", "Invisible object in preview mode\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: AMD Radeon HD 8600/8700M ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0\n\nWhen I enable Material Preview mode in Blender, the object becomes invisible regardless of the Render Engine. Also the object is invisible with Rendered mode enabled when I use the Render Engine - Eevee. \n\nI don't know how it happened but I can't repair Blender. I reset all settings to factory, reinstalled the application, but it did not help. Can you help me, please?\n\n\n\n\n\n\n\n\n\n", "Cycles viewport render doesn't resize if an animation is playing.\nOperating system: macOS-13.0-arm64-arm-64bit 64 Bits\nGraphics card: Apple `M1` Pro Apple 4.1 Metal - 83\n\nBroken version: 3.5.0 Alpha\nBroken version: 3.3.1\n\nIf a .blend file contains a animation, and the animation is playing, and you're in the Cycles rendered viewport mode, then the viewport resolution/size will not update as you adjust it's size.\n\n1. Create a scene that has a colour that differs from the standard background colour of the 3D viewport.\n2. Animate something in the scene (E.G. Animate the movement of an object)\n3. Change the render engine to Cycles (This issue only appears in Cycles for me.)\n4. Enter the rendered viewport mode so you're now seeing a Cycles viewport.\n5. Start playing the animation.\n6. While the animation is playing, start adjusting the size of the 3D viewport editor and notice how the Cycles rendered view isn't updating with the change in size. This is the issue. Once you stop playing the animation, it will update.\n\nHere is a video demonstrating the issue:\n\n[Cycles preview doesn't resize.mp4](Cycles_preview_doesn_t_resize.mp4)\n", "Improve volume render passes\nCycles volumes mostly do not write to render passes currently. Given the transparency it's not always useful or meaning to do this, but we can do better.\n\nA few known issues:\n- [ ] Cryptomatte is not written for volumes. We could accumulate cryptomatte contributions of objects while ray-marching.\n- [ ] Mist is not written, which causes the background value to be used when the volume is opaque. More useful would be to either write it based on the volume position weight by transparency, or to write mist for the object behind. (#91280)\n- [ ] There is no Volume Color pass currently, equivalent to the Diffuse/Glossy/Transmission Color passes. We do now write albedo for denoising, a similar thing could be added for volumes but it's unclear if this is useful for compositing in practice, especially with overlapping volumes.\n", "UV: (investigate) Render UVs of selected object in UV Editor while in Object Mode\nCurrently, the UV Editor only works while in \"Edit\" mode.\n\nHow firm is that restriction?\n\nIt would be nice if we could view UVs in the UV editor, even in \"Object\" mode.\n\nIf would be even nicer if we could use the basic edit tools, such as move, scale and rotate on those UVS, again, even in Object mode.\n\nUVs can be generated and adjusted procedurally, but there's no good way to see them. It would be nice to allow displaying (not editing) evaluated UVs. Combined with features like visualizing overlapping faces, this could save a lot of time.\n\nThis is an *investigate* task, to see if such a thing is even possible. If we discover it's possible, we'll then need to decide if it's desirable.\n\nThanks @BlenderBob for the inspiration!\n\n", "Cycles X: Camera-visible lamps are not affected by holdout\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0 Alpha\n\nBlender 3.0 adds a feature where camera ray visibility can be enabled on lamps, making them directly visible. However, if this option is enabled simultaneously with the holdout option, the lamp will remain visible. Holdout should override camera visibility, as holdout can be changed per-view layer. With the current behavior, a directly-visible lamp will appear again on holdout layers, copying it's direct brightness for every layer it appears as a holdout in.\n\nSee attached .blend file, which contains a point lamp with holdout and camera visibility both enabled. Note that the lamp remains visible. In fact, the holdout option seems to have no affect at all.\n\n[holdout_lamp_bug.blend](holdout_lamp_bug.blend)\n\n", "texture in solid mode not updated\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2, 2.93\nWorked: probably never\n\nif the shader editor is located in another workspace, in which there is no viewport in solid mode, then the texture on the object will not be updated\n\n- Open .blend file\n- In both layout an shading workspace: make sure skin texture is selected\n- switch to shading workspace and select blue texture\n- Now switch back to layout workspace (notice `blue` texture is selected in node space but viewport is not updated)\n\n[#99598.blend](T99598.blend)\n\n---\noriginal file and video provided by the reporter\n[jupiter.blend](jupiter.blend)\nVideo [F13283900](2022-07-11_00-19-08.mp4)", "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", "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", "Custom render engine is unable to create gpu context\nOperating system: Linux-5.19.17-2-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon Graphics (renoir, LLVM 14.0.6, DRM 3.47, 5.19.17-2-MANJARO) AMD 4.6 (Core Profile) Mesa 22.3.1\n\nBroken: version: 3.5.0 Alpha\nWorked: Blender 3.4\n\nUnable to perform background rendering using `gpu` module in custom render engine.\n\nRun the script in background mode: `blender -b -P background-gpu.py`. Blender throws: `SystemError: GPU API is not available in background mode`, despite the line `bl_use_gpu_context = True` in custom render engine. Worked perfectly fine in blender 3.3 and 3.4. Not in 3.5 though.\n[background-gpu.py](background-gpu.py)\n\n", "Problems due to leftover Nvidia drivers\nOperating system: Windows 11 Home\nGraphics card: Intel Arc a770 16gb Limited Edition (latest drivers)\n\nBroken: (Blender 3.3, 3.5 and 4.0) Trying to work out if it is just my GPU that is the issues\n\n\nBlender 3.5.1 will not allow me to access editor preferences, and won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 3.3 allows me to access editor preferences, but still won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 4.0 allows for editor preferences, same issue with Cycles. Eevee works fine.\n\nBy not allowing me to access editor preferences or Cycles I mean it crashes.\n\nI have tried to converse with Intel engineers with a video of the crashes but they seem incompetent with knowing how to enable GPU rendering in their own tests.\n\n", "EEVEE: Reduce viewport render time by only render needed draw passes.\nCurrently all material + effect passes are rendered even when eventually they aren't needed. This can happen when viewing a render pass in the viewport. For example:\n* Mist\n* AO\n* Shadow\n* AOV (after [D7010](D7010) has been comitted)\n* etc\n\nWe should see how we can optimize the rendering pipeline so that only the passes that are needed are drawn. This would lead to a more responsive viewport in these cases.", "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", "Rendering: Engine specific passes show up in other render engines render result\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: Blender 2.83.18, Blender 2.93.6, Blender 3.2.1, Blender 3.4\n\nPasses that were enabled for Cycles show up for eevee/workbench even if they should not.\n\n1. Fresh start-up\n2. Switch to Cycles\n3. Enable all render passes\n4. Switch to Eevee/Workbench\n5. Disable all render passes except `Combined`\n6. Render the image\n7. Notice `Vector`, `Position`, `UV`, etc. in the Pass dropdown\n\nAlternative:\n1. Fresh start-up\n2. Enable all render passes\n3. Switch to Workbench\n4. Render the image\n5. Notice `Vector`, `Position`, `UV`, etc. in the Pass dropdown\n\n[T100319_eevee.blend](T100319_eevee.blend)\n\n[T100319_workbench.blend](T100319_workbench.blend)\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." ]

[ "UV pass preview in viewport messing up UVs temporarily\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.2.2\nWorked: 2.93LTS\n\nWhile using a subdivision surface modifier, using the UV pass preview in the viewport will mess with UVs until you hard-refresh the renderer by changin the display type (Ex: Material preview)\n\n- Open .blend file\n- Change render engine to cycles and start render preview\n- Switch from combined -> UV pass (notice corrupted shader output)\n- switch UV -> combined pass\ntest File:\n[#100235.blend](T100235.blend)\n[2022-08-05 22-23-56.mp4](2022-08-05_22-23-56.mp4)\n", "Odd texture mapping in Cycles viewport after viewing UV pass\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.4.0\nWorked: 2.93 Release\nSeems to occur after 3.0.0 release\n\nUV maps reshuffle after viewing \"UV Map\" render pass in 3D viewport\n- Seems to only affect meshes with multiple UV islands\n- Behavior reverts when cycles updates images\n- Occurs on CPU and GPU using CUDA or Optix\n\n 1. Switch to Cycles viewport render view\n 2. Change render pass to \"UV\"\n 3. Change back to \"Combined\"\n\n**Example file:**\n[UV Bug.blend](UV_Bug.blend)\n\n**Quick Demo:**\n[UV Bug Demo 0022-0630.mp4](UV_Bug_Demo_0022-0630.mp4)\n\nLet me know if I missed anything\nThanks", "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", "Cycles Renderpasses cycling causes Image Texture Errors\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.2\nWorked: I am not able to reproduce this in earlier Versions\n\nI was curious about the Renderpasses and noticed that I could switch through them quickly by holding control and using the mouse wheel to scroll through the passes.\nOnce I got through the UV Render pass and switched back to combined the Texture Images were distorted a lot\nAlso checked if this was a one-time error in Blender and restarted Blender and my whole machine, but it keeps happening\n\nClick on the Viewport shading tab and Crtl + mouse wheel on the Renderpasses, after the UV Renderpass the Image Texture should be distorted.\n\n\nShown Blend in the Video is attached\n\n" ]

[ "Objects with volume material is included in render even when it's inside HOLDOUT collection\nOperating system: Windows 10\nGraphics card: NVIDIA RTX 2070 Super\n\nBroken: 2.91\nWorked: (Nothing since collection system was presented)\n\nObjects with volume material is included in render even when it's inside HOLDOUT collection.\n\nApart from the question whether volume material should mask the other collections, it should not be rendered like it normally would. It should at least be excluded from the render.\n(Volume material object inside INDIRECT ONLY collection works fine)\n\nIt's very simple. Based on the default new file...\n\n1. Make a new collection and enable holdout.\n2. Make a new icosphere object inside the new collection.\n3. Give the icoshpere a volume material(Simple principled volume is fine).\n4. Move the icosphere in front of the camera, making the default cube go behind the icosphere inside the camera view.\n5. Render the image. You'll see that the holdout is not working properly for volume material objects.\n\n[volume_holdout.blend](volume_holdout.blend)", "Viewport display: in front should be listed under visibility as it also affects final render\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\nWorked: unknown\n\nUnder object properties, viewport display: in front affects both the visibility in the viewport and in the final render, and as such should probably be listed under visibility rather than viewport display.\n\n-", "Fly/Walk in viewport, Workbench/Eevee do not stop rendering at sample limit\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken since at least 2.80 and still broken in 2.91.0 Alpha\n\nWhen using Walk or Fly navigation modes using any built-in renderer except Cycles, the viewport will render the specified number of samples, then start again from sample 1 and repeat indefinitely, *even if the navigation is motionless.* This can be seen visibly. If set to 1 sample, it still re-renders it indefinitely. This can be confirmed via GPU usage.\n\nEnter walk or fly mode in any scene, using any viewport mode, and any renderer except Cycles. If you have a hard time seeing it, you can use Eevee and any volume shader to more easily see each sample as it's rendered.\n\n**Misc notes**\nI'm aware Workbench's render settings are anti-aliasing samples instead of sample count, but it still re-renders those anti-aliasing samples.\n\nIt's not a pressing problem, but it does waste GPU resources and can introduce visible flickering. It should either stop rendering when it reaches the set number of samples (like orbit), or stop rendering after 1 sample regardless of sample limit. The latter would actually be more useful in my use case, even for regular orbiting. My proposal: It could pause for about 500-1000ms (configurable?) before rendering sample 2 and onward. This would improve viewport responsiveness, but still retain the benefits of rendering the full quality version during navigation.", "Asset Browser - Append (Reuse Data) without instancing collections doesn't add more objects\nOperating system: Windows 10 Home 64bit (10.0, Build 19044)\nGraphics card: Nvidia RTX 3080\n\n\nBroken: 3.2.0\n\nWhen dragging a collection item from the Asset Browser with \"Append (Reuse Data)\" and \"Instance Off\" it doesn't add the collection again, it moves one object and leaves the rest where they were.\n[Asset Browser Reuse data issue.mp4](Asset_Browser_Reuse_data_issue.mp4)\n\n1. Create a collection asset with at least two items inside\n2. Save that collection to your library (save file inside the correct folder)\n3. Open a new scene\n4. Drag your new collection asset into your scene with Append (Reuse Data) active\n5. In the tool window (not sure about its name) lower left turn off \"Instance\"\n6. Drag out another of the same collection asset\n7. It should now have moved one of the two items", "Remove BKE_layer_collection_resync_forbid and BKE_layer_collection_resync_allow\nThese can be removed after each area has been checked and optimized to use the new structure (synced_ensure)\n\nRecently ceb0e7fcea was done and added a use for resync_forbid. This makes this ticket perhaps irrelevant?", "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. ", "Decide how to handle collection instancing or linked data\nCurrently, dropping collections always creates a collection instance. This should be optional somehow, there are valid usages for both cases. Should it just be an option of the drop operator? So users could change it after dropping. (May be annoying when dropping heavy collections from external libraries, which can take a moment.)\n\nSimilarly, some users seem to expect that object data is linked by default. This is already an option of the drop operator (disabled by default). However it seems like they actually expect that data is a new \"instance\", rather than a full copy. This could mean either de-duplicating already existing data (so that dropping the same material asset onto 10 objects doesn't create 10 local materials), or linking data rather than appending.", "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)", "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", "Viewport animation renders take progressively longer if there is a split in the scene!\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Ultra 1.2\n\nBroken: version: 3.6.2\nWorked: Never\n\nWhen animating a render from the viewport, if a spline is present in the scene each frame takes progressively longer and longer to render until it takes a painfully long time per frame. Once the spline is deleted from the scene, each frame takes the same amount of time to render!\n\nMake an animation of approx 1000 frames\nInclude a spline in the scene - you don't have to render it, it just needs to be in the scene!\nViewport Render Animation\nYou should quickly notice that each frame is taking longer and longer to render\nBy the time you get to frame 800 (if you care to wait that long) you will be pulling your hair out!\n...now delete the spline\nViewport Render Animation\nEach Frame now takes the same time to render and you can smile once more.\n\n....I'm already guessing that whoever is gracious enough to try this will magically not have the problem - if so, please reply and I will supply files... I just would rather not at this time as I am interested to see if it is indeed reproducible? I can confidently say that I have experienced this issue for at least 5 years, but it's only now that it has come to bite me again and I have finally proven (to myself, at least) that the issue is spline related - my scene had one single 'Annotation' spline that I wasn't even aware of hanging around in it and deleting it sped up render times by an order of magnitude!\n\nThanks\nWayne\n\n", "Blender editing performance with many datablocks\n**Status:** 1st milestone almost complete, need final optimizations.\n\n---\n**Team**\n**Commissioner:** @brecht \n**Project leader:** @mont29\n**Project members:** @ZedDB \n**Big picture:** In heavy scenes, new features in Blender 2.8x are making the inherently linear (`O(N)`), when not quadratic (`O(N²)`), complexity of most operations over data-blocks more problematic than in 2.7x era. The general goal is to bring those operations back to a constant (`O(1)`) or logarithmic (`O(log(N))`) complexity.\n\n**Description**\n**Use cases:**\n*Need specific test cases.*\n* Undo changes in object mode in a heavy scene.\n* Undo changes in pose mode in a heavy scene.\n* Duplicating objects in a heavy scene.\n* Adding many objects in a scene.\n\n*Note:* There are two types of “heavyness” in scenes (that can be combined of course):\n * Scenes that have many objects and/or collections.\n * Scenes that have very heavy geometry, either in the geometry data itself, or generated from modifiers like subdivision surface.\n\n**Design:**\n # Dependency graph should not have to re-evaluate objects that did not change.\n ** This is mainly a problem currently during global undo, as all data-blocks are replaced by new ones on each undo step.\n # Handling naming of data-blocks should be `O(log(N))` (it is currently close to `O(N²)`, or `O(N log(N))` in best cases).\n **This will require caching currently used names.*** We will probably also have to handle smartly the numbering in that cache, if we really want to be efficient in typical “worst case” scenarii (addition of thousands of objects with same base name e.g.).\n - Caches/runtime data helpers should be always either:\n - Lazily-built/updated on-demand (code affecting related data should only ensure that the 'dirty' flag is set then).\n *** This approach can usually be easily managed in a mostly lock-less way in a threaded context (proper locking is only needed when actually rebuilding a dirty cache).\n ## Kept valid/in sync all the time (code affecting related data should take care of updating it itself, code using the cache can always assume it is valid and up-to-date).\n ***Such cache should be easy to incrementally update (it should almost never have to be rebuilt from scratch).****This implies that the cache is highly local (changes on a data-block only ever affect that data-block and a well-defined, easy to reach small number of “neighbors”).*** In general keeping this kind of cache valid will always be harder and more error-prone than approach #A.\n *** This approach often needs proper complete locking (mutexes & co) in a threaded context.\n \n *Note: The ViewLayer's collections/objects cache e.g. currently uses the worst mix of #A and #B - it is always assumed valid, but updating it requires a complete rebuild from scratch almost all the time.*\n\n *Note: Approach #B is usually interesting only if a complete rebuild of the cache is **very** costly, and/or if the cache is invalidated very often while being used.*\n\n**Engineer plan:** `-`\n\n**Work plan**\n\n**Milestone 1 - Optimized per-datablock global undo**\nTime estimate: `6 months`\n\n* Re-use as much as possible existing data, and try to swap newly read (modified) data to the original memory, during 'memfile' undo step. Updating the depsgraph should then be much less work.\n** #60695 (Optimized per-datablock global undo)\n** [D6580: WIP/Demonstration patch about undo speedup project.](D6580)\n\n**Milestone 2 - Lazy collection synchronizations**\nTime estimate: `1 month`\n* Fix view layer collection syncing (to not require looping over all objects, or to be ran much less often...).\n** #73411 (Fix ViewLayers cache building)\n\n**Milestone 3 - Data-blocks management performances with many of them**\nTime estimate: `5 months`\n\n# Investigate how to best handle naming conflicts issues.\n**Most obvious idea would be store all used base-names in a GHash (one per ID type), along with used indices. Needs further design though.** #73412 (Improve name conflict handling in ID management)\n# Investigate the best way to cache bi-directional relationships info between data-blocks.\n**We already have a start of this with `BKE_main_relations_create()` & co, but it is heavily under-used and needs better design to be usable more widely.** #73413 (Cache data-block relationships info )\n# Fix/Improve handling of the Bone pointers (which are sub-data of `Armature` ID) stored in poses (which are sub-data of `Object` ID).\n**Ideally such horrible pointers should not exist ever. They are a very solid recurrent source of bugs in Blender.** Not sure how to best deal with them, at the very least we could add some generic ID API to ensure those kind of caches are up-to-date?\n\n\nSee also #68938 (Blender editing performance with many datablocks).\n\n**Later**\n\n* Dependency graph rebuild to be `O(1)` or `O(log(N))` (it is also `O(N)` at the moment). *???? would assume linear would already be nice performance for such a code?*\n\n**Notes:** -\n\n---\n", "Collection Assets: To Instance or Not to Instance\nWhen using collections as assets, it needs to be defined when dropping a collection should use instancing and when not. Instancing collections basically means a non-editable version of the collection is added to the scene, with an empty acting as the pivot point. So the collection can be transformed by transforming the empty, but the contents of the collection aren't editable without further steps.\n\ncollection.html\n\n## Proposal: Operator Option\n\nWhile we could just add another option for instancing to the Asset Browser, next to the *Import Type* option, it adds clutter and also requires setting up things before dragging: If you dragged in an asset and used the wrong setting or change your mind afterwards, you'd have to undo and perform the operation again, or manually replace the collection.\nSo it violates the [Operate -> Settings design paradigm ](Paradigms#Operate_-.3E_Settings) of Blender. Instead the proposal is to have this controlled via an operator option, whereby the option will remember what it was set to last. Another setting could still be added, but the operator setting should be useful either way.\n\n***Current File* Asset Library**\n\nIn the *Current File* asset library we often reuse data, but not as often as with the *Append (Reuse Data)* option. E.g. materials are shared, but objects are duplicated including their mesh. [D12879](D12879) tries to make things more unified & explicit, but it's on hold.\n\nNo strong opinion on how this should be handled, I'd say let's avoid confusing users by sharing meshes. So:\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, all objects will be duplicated.\n\n**Other Asset Libraries**\n\n**Link:**\n- Use drop operator option to determine if instancing should be used (*Instance* option)\n\n**Append:**\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, all objects will be duplicated.\n\n**Append (Reuse Data):**\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, a new collection is created but the object's meshes are shared.\n\n**Determining the Drop Location & Rotation**\n\nIdea is to make the drop location and rotation be defined visually. So when dropping a collection, it is transformed to land under the mouse cursor (and later use bounding-box snapping), regardless of where the instance empty is, or regardeless of the collection instance offset. They are reverse applied.\n\nNotes:\n- The drop transform will have to be applied to all added objects, including objects used by the objects inside the collection, which are not in the collection itself. E.g. if an object has a parent or a boolean modifier, the parent or boolean-object is imported along, and the relative transform needs to be preserved. We already do this for dropping object assets, code can be shared.\n- When linking without instancing, the dropped collection will use the drop location of the source file.\n\n**What Should be the Default**\n\nThere seems to be some agreement that in production environments, instancing should be the default. However for beginners (or anybody unfamiliar with collection instancing) this may be a bit confusing. Needs some feedback, for now instancing can be the default behavior.\n\n", "depsgraph.object_instances does not respect collection visibility\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 860M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.83 (sub 5)\nWorked: 2.80 release\n\nCollection visibility (Hide in Viewport) does not affect object appearance in `depsgraph.object_instances`.\nWhile hiding objects individually or excluding collection from view layer or Disable in Viewports does hide them from `depsgraph.object_instances`.\n\nIn 2.80 release collection visibility did affect `depsgraph.object_instances`.\n\n\n - Open attached blend file: [dep_visibility.blend](dep_visibility.blend)\n - Run the script > console output lists all three objects.\n - Use collection `Hide in Viewport` visibility options and run script > console output has the same objects regardless of collection visibility state.\n - Use `Hide in Viewport` on an individual object > console output remose this individual object\n", "Copying scene unhides hidden collections\nWindows-10-10.0.16299 64 Bits\nGeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBlender 2.80 (sub 53)\n\n[hidden_collections_copy_scene_bug.blend](hidden_collections_copy_scene_bug.blend)\n\nOpen attached file. There are two hidden collections.\nMake a copy of the scene using either \"Link Object Data\" or \"Full Copy\".\nCollections in the newly created scene will be set to visible.", " 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)" ]

[ "DepsGraph: Disabled objects referenced by other disabled object still get evaluated\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.56\n\nBroken: version: 3.0.0 Alpha\n\nIn the below setup, although all mesh objects are disabled, the viewport is still extremely slow because the objects (which have expensive modifiers like Remesh and Boolean) are still evaluated.\n\nThey stop being evaluated only when their grandparent collection (\"coll Root\") is also hidden from the viewport(or deleted).\n\nNote that there are no drivers involved.\n\nFile: [disabled_objects.blend](disabled_objects.blend)\n- Try moving the cube, should see bad performance even though all meshes are disabled. If your PC is too powerful to notice, put a subsurf modifier on the object named \"expensive mesh\", that should make it a lot more expensive.\n- Disable or remove the \"coll Root\" collection, and performance goes back to normal.\n\n[depsgraph_bug-2021-07-02_13.10.41.mp4](depsgraph_bug-2021-07-02_13.10.41.mp4)" ]

[ "Graph Editor: Curve drawing improvements\nProblem: keyframe dots can be somewhat hard to see, especially behind the current frame marker line.\n\n\n\n**Proposal**:\n- Change the default theme to draw the keyframe dots larger. The current theme draws at 6px, for modern displays this should probably be increased to 7-9px. It's probably better to defer a concrete choice for this until #68982 (Graph Editor: UI Scale effect on Curves drawing) is done.\n- Draw keyframe dots of selected keyframes on top of current frame line. Keep drawing unselected keyframe dots behind the line.\n", "Scrollbars Design\nWe think we can make a few improvements to how scrollbars look and work.\n\n**Larger size**\nIn Blender 2.8, we made it so scrollbars don't make the content jump around as they appear and disappear. However, to do this, scrollbars had to be made very thin.\n\nWe would like to make the scrollbars just a tad wider: \n\nBefore/after:\n\n\nThis requires creating a little bit of extra space always, so scrollbars have enough space to appear & disappear inside this gutter area.\n\n**Unified scrollbars**\nWe can also use this opportunity to unify scrollbars. Currently, list view scrollbars are huge, while the regular 2D view scrollbars are very thin. Here, both are unified:\n\nBefore/after\n\n\n**Thickness fading**\nIt's also desirable to keep the scrollbars always visible, rather than making the fade away. This makes them more practical for use with devices with no hover state (some tablets), and also for users to see at a glance where in a list they are.\n\nWe can keep these at a very small width. When the cursor is close, we can then make them much more prominent: \n\n", "Weight paint: front face falloff checkbox looks inactive (dimmed)\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\nBroken in 2.93.7 too\n\nFront face falloff checkbox Looks dimmed, but it is active\n\n\nAlso in the n-panel there is correct variant. And another one incorrect.\n\n\n[2021-12-19_04-11-58.mp4](2021-12-19_04-11-58.mp4)\n", "Sidebar changes\nCurrently, the Sidebar has several UI-related issues, especially in the 3D View.\n\n\n\n - Use of vertical text\n - Finite space for tabs\n - The tab bar works poorly with Region Overlap, pushing the panels further into the viewport, and overlapping\n\nYou can see an example of using lots of tabs here. This is an extreme example: \n\n\nWe also have a visual clash with the Properties tabs often:\n\n\nTabs also often appear outside the panel region, which looks glitchy:\n\n\n\n----------\n\nWe can address these issues by making a number of changes:\n\n\n\n\n - No vertical text\n - No bar which extends all the way down the viewport\n - Not bound by the viewport height \n - Floating design mirrors the toolbar\n\n\nThe menu at the top could be expanded into a list, which would allow users to re-order sections. If users mainly use a couple of sections, they could move those to the top for easy access. \n\nWe could also add the ability to view several sections at once, something which would be hard to support with tabs:\n\n\n\nNote: This would require changes to UI lists in Blender to support this, but would also benefit other areas.\n\nThese changes could also be adopted by other sidebars in Blender. ", "Blender 2.82: Fails to immediately report information to XServer on Linux\nOperating system: Manjaro Linux 5.6\nGraphics card: GTX 1070 ti\n\nBroken: 2.82, found as soon as app is open.\nWorked: 2.81\n\nIn Linux, if an app doesn't report anything to the Xserver, but still specifies window dimensions, it leads to a sort of awful stuttery broken effect while said app is loading. This is visible in 2.82, where, upon opening and loading, it fails to report to Xserver, and looks like this:\n\nIt looks like this while the app is loading (that is, only a title bar) and produces an odd effect if the window is dragged around during loading, and I can confirm that it lasts longer if Blender is put on a mechanical hard drive VS an SSD. This doesn't occur launching any other apps, nor even a binary of 2.81, which instead displays a gray screen while loading. This is obviously just an aesthetic problem, but it can (rarely) cause issues. \n\n\nOpen Blender. ", "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: 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", "Sequencer: Can't toggle Channels sidebar when VSE view type is \"Sequencer & Preview\"\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon (TM) R9 380 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nversion: 3.2.0\n\nAll in the title.\n\n1) Be in Video Sequencer editor\n2) Switch view type to Sequencer & Preview\n3) Try to toggle Channels sidebar : either with the little arrow (that doesn't show up), or by going to View > Channels (it doesn't toggle the sidebar, its checkbox doesn't get checked)\n\n", "Cycles: principled BSDF thin surface support\n[D2354: Thin surface approximation for Cycles Disney BSDF](D2354)\n\nRebase and benchmark performance impact.", "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", "Brushes Assets Viewport User Interface\n{[F13331829](image.png), size=full}\n\nAdditional Notes:\n\n{[F13331831](image.png), size=full}", "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~~", "Outliner: Search box doesn't search in non-expanded sections in Data-API mode \nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nthe outliner's search box doesn't search in non-expanded sections of the outliner in the data-api mode]\n\n- Load default blender;\n- In the outliner display mode choose `Data API`;\n- Type \"Cube\" in to the search box - No results are returned;\n- Expand the object section;\n- Type \"Cube\" in to the search box again;\n- This time it finds it.\n\n", "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", "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" ]

[ "Scroll bar in maximized view invisible\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\nBroken: version: 2.81 (sub 4)\n\nOK, noticed the scroll bar in preferences seems to be invisible. Seems to work everywhere else. I loaded factory settings as a test and it still does it.\n\nOpen preferences and go to addons.\n\n\n\n\nOpen preferences in separate window for it to start showing.\n\n\n\n" ]

[ "Grease Pencil sculpt tool affecting strokes behind camera\nOperating system: Windows 11 Home\nGraphics card: Nvidia GeForce MX350\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\nWorked: ?\n\nIf the 3D view camera has strokes in front of it (visible on screen) as well as behind it (not visible on screen), in Grease Pencil's Sculpt Mode, using the grab tool will affect not only the strokes that you can see, but also the ones behind the camera that you do not see.\n\n1. Move the Camera object to the origin\n2. Create an empty Grease Pencil object\n3. Place the 3D cursor a little bit in front of the Camera object, set the Stroke Placement to 3D Cursor and the Drawing Plane to View. Align the 3D view to the active camera object.\n4. Draw some strokes, make sure to cover a good portion of the screen. The strokes will be visible.\n5. Rotate the active camera object around the Z-axis 180 degrees. Move the 3D cursor to again be a bit in front of the camera and make sure the 3D view is aligned to the active camera object again.\n6. Draw some more strokes. They will be visible, while the strokes from before are now no longer visible since they are behind the camera.\n7. Go to Sculpt Mode and select the grab tool.\n8. Grab and manipulate some strokes that you can see.\n\nExpected outcome: only the strokes from step 6 are manipulated, and the ones from step 4 are not.\nActual outcome: both the strokes from step 6 and step 4 are manipulated.", "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", "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.", "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.", "Regression: Multi sockets on muted nodes display wrong internal noodle\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 531.29\n\nBroken: version: 3.5.0 Release Candidate\nAlso broken in 3.4\nWorked: 3.3.1\n\nWhen a node with a multi socket (e.g. Join Geometry or Mesh Boolean) is muted, the visual internal noodle goes from the last (bottom) input instead of the first (top) input, even though it is the top input that is actually passed through.\n| 3.3 | 3.5 |\n| -- | -- |\n|  |  |\n\n- Open attached .blend file or\n - Create a geometry node group\n - Connect two or more different inputs into a Join Geometry node\n- Mute the Join node\n\nObserve the discrepancy between the visualized noodle and the actual result in the viewport\n\n", "GPencil: lines on surface quality difference between F12 and viewport render\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\nBroken: version: 2.83.0\nWorked: I don't think it ever worked\n\nThere's a difference in GPencil line quality between viewport render and F12. The GPencil lines are drawn on top of a 3d surface. The difference in quality seems to be the level of intersecting.\n\nBlend file has GPencil lines drawn over a 3d surface.\n1) render viewport in rendered viewport shading\n2) render with F12 and compare both renders\n[GP_on_3D_ViewportVsF12.blend](GP_on_3D_ViewportVsF12.blend)\n\n", "HDRI Preview Spheres appear in surface reflections\n\n\nBroken: version: 2.82 (sub 7)\nMaster\n\nWhen using material shading and overlays in the viewport, the gizmo at the bottom-left corner (sphere displaying the environment map used for preview) is reflected by shiny surfaces in the 3D world, despite technically being a part of the UI. Using the icon to show / hide overlays affects this, the reflection also disappears when overlays are hidden.\n\nShould work in any setup, if there are issues replicating this let me know and I'll extract the relevant part from my project's blend file. Just add a plane, lower its material roughness so it's shiny, move the view upward so the overlays appear under it, and you should see the strange reflection.\n\n\n\n[HDRI_reflected_in_viewport.blend](HDRI_reflected_in_viewport.blend)", "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", "GPencil: Strokes with texture & round caps have distorted extremities\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\n\nStrokes with a material of line type 'Line', a texture & round caps have distorted extremities.\n\n\n- Open file and see how the start & end of the drawn strokes are distorted.\n[round caps bug.blend](round_caps_bug.blend)\n\n", "Grease Pencil: Better render Anti-Aliasing\n## Motivations:\nThin lines are correctly rendered using grease pencil with the currently implemented post process Anti-Aliasing. This is done by making sure the line width is not less than 1.3 and by modulating its opacity.\nHowever, there is cases where this is not enough. For instance really dense drawings with small lines with little to no curvature still tends to flicker a lot.\nAnother case is when the gpencil strokes intersects the scene geometry. This makes the line less thick to the post process which makes it too small.\n\n## Proposed solution:\nWe propose to implement a Temporal AntiAliasing solution. It is robust and will match Cycles & EEVEE's film filtering if using the same filtering function. This only adds one temporary buffer (low VRAM usage compared to rendering at higher resolution) and is completely self contained (works with transparency and don't interfere with other features).\n\nI propose to only implement this for final rendering since it might introduce flickering that might be annoying while drawing.\n\nHowever this wouldn't solve the issue of gpencil strokes intersecting geometry.\nFor this I propose to erode or reproject the render's depth to match the render sample of the new AA scheme. This should fix the second problem completely.\n\n## Technical details:\n- Implementation just need to be ported from Workbench which has a lighter form of TAA than EEVEE. Also [D10414](D10414) can be of great help to reduce render/convergence time.\n- Depth buffer modification can be implemented after new AA is in.", "Render issues when two VBD overlap if rendered with motion blur\nBroken: 3.2, 3.6\nWorked: 3.1\n\nRender issues when two VBD overlap if rendered with motion blur\n\nRender the attached file with and without motion blur. If you render them separatly they both render OK. Only when together it doesn't work.\n\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", "Sculpting/Painting on invisible objects\nOperating system: Linux-6.5.2-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 16.0.6, DRM 3.54, 6.5.2-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-b492f73f87)\n\nBroken: version: 4.0.0 Alpha\nWorked: ---\n\nThis is an inconsistency that I noticed when toggling between collections of objects while working on an asset. It's most likely not a regression.\n\nIn edit mode it's impossible to operate on the selection if the object is currently hidden. This is very helpful to prevent mistakes and as feedback that you might be editing the wrong object atm.\n\nWhile in sculpt mode or any of the painting modes this is not the case. If the object is currently hidden while in sculpt or weight paint mode, it is possible to use the brushes on the geometry.\n\nIdeally any operation should be prevented if the object is hidden.\n\n1. Enter edit mode.\n2. Select everything.\n3. Hide the object or collection in the outliner.\n4. Try to move or otherwise edit the selected geometry.\n5. Show the object again (No edits should have happened).\n6. Enter sculpt mode and hid the object/collection again.\n7. Use a brush on the hidden object.\n8. Show the object/collection (See the edits that have been done).\n\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)", "Freestyle wireframe-only rendering is broken with Ztrans faces (lines disappear when Ztrans alpha and Ztrans spec are set to zero / lines behind transparent faces are not rendered / marked edges are not sometimes rendered when faces overlap)\nOSX 10.11.2 / Macbook Pro Retina 15\" Mid 2014 / GeForce GT 750M\n\nBroken: 2.76b (also broken in 2.76)\n\nRendering wireframes with controllable wire thickness requires using Freestyle but Freestyle requires filled faces even when rendering only edges. To only render edges and make the faces invisible one must set Ztrans alpha to zero.\n- When other line objects are behind line-only objects their lines are culled (however ordinary objects are rendered properly)\n- When both Ztrans alpha and spec are set to zero no lines are rendered\n- When faces overlap only some marked edges are rendered (even when faces are set to be transparent)\n\nObserve and render the attached .blend file.\n[freestyle-lineclipping.blend](freestyle-lineclipping.blend)" ]

[ "Grease Pencil strokes transparent when covering the surface of a 3d object\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nGrease Pencil strokes artifacting when covering the surface of a 3d object. It's like the strokes are going transparent.\n\n\nSurface draw with grease pencil at 0.0001 offset on 3d sphere\nU29ieUO.png (the right side is suppose to show grease pencil strokes)\n\n" ]

[ "Mantaflow foam particles as objects break motion blur\nOperating system: Linux-5.3.0-40-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 5)\nWorked: (optional)\n\nIf you use an object in foam particles and enable motion blur it renders incorrectly and very slow compared to the liquid alone. But I suspect this is due to huge vectors from those particles.\n[0001-0100.mp4](0001-0100.mp4)\n\nOpen the attached file\nBake caches\nAssign the cube for the foam particles instance object\nRender a couple of frames\n\n[mantaflow_particles_mblur.blend](mantaflow_particles_mblur.blend)", "Entire system freezing while using NLA in Blender 2.91 and newer (Mesa only?)\nOperating system: Fedora 33\nGraphics card: Intel HD Graphics 520 (Mesa 20.2.4)\n\nBroken: 2.91\nWorked: 2.90.1\n\nBlender randomly freeze entire graphics system. After freezing, last 2 frames is flickering if you move mouse. I can even save my work with CTRL+S, but after that i need to restart my computer. Setting INTEL_DEBUG=reemit environment variable fixes the issue.\n\nMethod 1\nAdd a few keyframes.\nScroll up and down in the NLA editor.\n[blender-freeze-2.mp4](blender-freeze-2.mp4)\n\nMethod 2\n\nJust do something, even in Solid view, even in Video Sequence editor. I don't know how to reproduce, it happens after 10 minutes of work. Also i notice some glitches in VSE with image strips. Also bug with Depth of Field was fixed in this version, probably this fix relate to this bug.\n\nBug with depth of view that was fixed:\nT77828\n\nIssue with VSE\n[blender-vse-artifacts-1.webm](blender-vse-artifacts-1.webm)", "Checking the Vector Blur pass checkbox causes the most recently emitted particles to not be rendered.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.80, 2.83.8, 2.92.0 Alpha c271600101, \nWorked: 2.79b\n[T82260_2.79_Sample.blend](T82260_2.79_Sample.blend)\n\nChecking the Vector Blur pass checkbox causes the most recently emitted particles to not be rendered. This issue is visible when using a fast moving emitter.\nRendering on the GPU or CPU doesn't seem to make a difference, the issue still occurs.\n\n - Open the attached .blend\n\n[T82260_2.92.0_Alpha_Sample.blend](T82260_2.92.0_Alpha_Sample.blend)\n - F12 to render.\n - Click on the Vector Blur pass checkbox.\n - F12 to render.\n - Compare the 2 render results.\nVector Pass unchecked\n\n\nVector Pass checked.\n\n\n[Desktop 2020.10.30 - 21.14.11.01.mp4](Desktop_2020.10.30_-_21.14.11.01.mp4)\n\n\n\n\n", "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\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", "Lifetime-Keyframes for particle system are ignored when rendering a baked particle simulation\nOperating system:Windows 10\nGraphics card:GTX1070\n\nBroken: Blender 3.5\nWorking:\n\n\nKeyframing the Lifetime of particles inside of a particle-system and baking the system (Both bake/bake all dynamics) leads to only the first keyframe being utilized when rendering an animation. For both the viewport and single-frame renders it works as expected.\n\n1. Create a simple particle system.\n2. Keyframe the Lifetime value at **1** on frame 30, and value **50** on frame 31.\n3. Bake all particle dynamics.\n4. Observe how the particles disappear after 1 frame up until frame 31, where they then last for 50 frames.\n5. Render an animation of the particle system.\n6. The particle system will only utilize the first keyframe for the duration of the animation, in this case 1. So even after frame 31 the particles will despawn after 1 frame.\n\nThe blendfile has a particle system setup, you merely need to look at the behavior in the viewport vs rendering an animation.\n\nThank you.\n\n", "Clipping Region in blender v3.2 and up is causing a werid artifact\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon RX 6600M ATI Technologies Inc. 4.5.0 Core Profile Context 22.10.1.221003\n\nBroken: version: 3.3.1\n\nweird colorful noise when using Clipping region ALT+B\n\nit happens by simply using the clipping region, it happens in both object mode and edit mode\n\n**Diagnosis that I tried** (USEFUL NOTES{[F13703419](Untitled.png)} FOR FIXING THE PROBLEM)\nwhat is causing it?: \n- I noticed that the bug is only on the Viewport Overlays it seems like it's smth related to the graphical smoothing done by \"viewport overlay smooth wires\" from blender preferences -> viewport -> Quality -> Smooth Wires. I can turn of that for Overlay and for Edit mode, but it's just hiding the problem not fixing it, also the selected objects highlight (active element and not active element) are both still showing the same artifact and I don't know how to turn off smoothing for this part.\n\nis it gpu driver problem?\n- it most likely is a conflict between blender and my gpu, I don't think it's a driver problem tho because I tried the latest two gpu drivers available from amd, and both of them are showing the same problem. I tried running blender using my integrated gpu and tried my RX6600M gpu and in both cases it happend, I don't know if the smoothing is done on the gpu level or cpu level tho so it could be not related to which gpu I use\n\nWhat versions of blender does it happen in?\n- I mainly use blender from steam with auto updates, I noticed the problem when I was using v3.3.1 then I tried few older versions by manually installing them from the offical blender website, the bug doesn't show up in v3.1.2 and v2.79b however it's in showing up in v3.2.0 and v3.3.0 and v3.3.1 -not steam version- I didn't test more versions tho\n\nP.S. my device -Legion 5- has a mux switch, when I did the bug report the mux switch is turned off which means the integrated GPU is disconnected thus it's not showing up in the bug report, however when I tried to check the bug \n\n\n\n\n\n\n\n[untitled.blend](untitled.blend)", "Particle system baking messes particle dietime (that in turn messes up particle textures)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.5.0\n\nIf texture with color ramp is used for animating particle size through lifetime, in ~10 last frames of simulation all particles PERMANENTLY getting smaller until totally disappear lol, and it occurs only if using BAKE.\nthis is not animation, this is 100% bug, looks like particle size animation is applied to WHOLE particle system respectively/relatively to all scene timeline, and is overriding every single particle age at the end of timeline.\n\nFile uploaded.\nParticle systems in blender are SOOOO broken, the way how it works is so facepalmable, particularly \"bake\" and \"textures\".\nlooks like in my case they met lol\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", "Cycles smoke is not exported to render without baking\nOperating system: win 10\nGraphics card: geforce 1080 ti\n\nBroken: blender-2.80-4488056f3d9-win64\\\nWorked: (optional)\n\nSmoke is visible in viewport but not in render.\n\n\n- Select default cube.\n- Run quicksmoke\n- Select the domain and in the simulation cache settings choose `Replay`(step added to be reproducible in mantaflow)\n- Run play so you get some smoke.\n- Press f12 (or switch to cycles and press f12).\n- Renders cube but no smoke.\n\nManually setting it up gives the same result.", "Motion blur artifacts on complex object animation (reproducable)\nOperating system: win10\nGraphics card: 2070super\n\nBroken: (example: 2.83.4, 2.92.0alpha)\n\n\n**motion blur gives strange artifacts in some frames.**\n\n[bug_motion_blur.blend](bug_motion_blur.blend)\n\n\nIn the attached file, this happens on frames 9 and 20. Bug reproducable", "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)", "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", "Parent with child containing particle emitter can't be moved on frame 1 keyframe\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0 Alpha\n\nEmpty in provided .blend file cannot be moved on frame 1 when it has a keyframe on frame 1. It can be moved on any other frame with or without a keyframe on that frame, or on frame 1 if it doesn't have a keyframe.\n\nSelect the Empty in the provided .blend file, and attempt to move it with `g`, transform sliders, etc. It will not move.\n\n[move_bug.blend](move_bug.blend)\n\nI'm not sure how I got my .blend file in this state, as my best effort at making a seemingly identical set of objects does not reproduce it. I'm guessing someone will have to inspect the internal state of these objects to find something amiss.\n", "Particle system behaves inconsistently in viewport and render when instance object visibility is disabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro [P2200](SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.91.0 Beta\nWorked: The behavior was different in 2.80\n\nWhen the instance object of a particle system is disabled in the viewport the particles are also disabled in the viewport. However when the instance object is disabled in render they still appear in the render.\n\n1. Open the default scene.\n2. Create another object (B).\n3. Create a particle system modifier on the default cube (A).\n4. Set Particle Settings to Hair (A).\n5. Set Render -> Render As to \"Object\" (A)\n6. Set the Instance Object to the other object (B).\n7. Disable the object (B) in viewport and render\n8. Render the scene, observe that the object has particles rendered\n[particle_visibility_bug.blend](particle_visibility_bug.blend)\n" ]

[ "When rendering, camera randomly jumps to a different (Z-axis) location.\nOperating system: Windows 10 Home - 10.0.18362\n\nNVIDIA GeForce GTX 1080 Ti\nIntel(R) Core(TM) i7-7800X CPU @ 3.50GHz\n32GB RAM\n\nBroken: 2.83\nWorked: newest version of Blender that worked as expected\n\nTrying to render out a particle + physics explosion (fully baked)\nRender samples: 192 *(also happens on lower samples)*\n\nSome frames are *skipped completely* which is already being discussed in #77922\nBut now I'm also getting random frames where the camera is way lower, than on other frames.\nAnd it's not just the location of the smoke on the screen, it's physically looking at the bottom of the explosion.\nAs if the camera is on a different Z axis position.\n\n*Note: The camera is not even animated. So shouldn't be moving at all.*\n\n[Explosion1.blend](Explosion1.blend)" ]

[ "Cycles : Massive OSL performance deficit compared to SVM using AcesCG studio profile\nOperating system: Ubuntu 23.04\nGraphics card: 6900XT (not used here)\nCPU: Threadripper 3990X\nRAM: 256GB\n\nCycles Standalone 3.5.0 (under Gaffer though)\nOSL version 1.14.6 (vs Blender 3.5.1's `1a7670600c8b08c2443a78d03c8c27e9a1149140` - specific commit I believe for OptiX support?)\nOIIO version 2.4.11.0 (vs Blender 3.5.1's 2.4.9.0)\nOCIO version 2.2.1 (vs Blender 3.5.1's 2.2.0)\n\nMassive 10x OSL vs SVM performance deficit, using a photo-realistic human asset with a lot of hair + SSS random-walk + normal map, moderate texture usage using mip-mapped/tiled tx.\n\nSwitch between OSL and SVM and compare the performance, as well as htop to see green bars and 99+% CPU utilisation under SVM vs OSL which is mostly red and 20-25% green CPU utilisation (all up 99+% CPU usage?). Also check render-times, SVM takes 7-8 mins/frame vs OSL taking 1hr 10 mins so roughly 10x the time.\n\nAll textures are maketx'd tiled+mip-mapped .tx files.\n\nApologies I cannot share the render due to NDA. I am re-creating something in Blender which just has a sphere with random walk + SSS + normal map, and I get similar results but not as severe. Roughly 7-8 mins for SVM but 15-20 mins for OSL so 2x which I assume is something to be expected? Htop has all the bars as green. Further investigation I believe it might be something to do with OIIO's texture cache getting thrashed, although I am pretty sure I am not hitting its built-in limit here:\n\nosl.cpp#L257\n\nRam usage in both OSL/SVM is about 3.5GB.\n\nWill keep digging...\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)", "Cycles/Compositor: The denoiser returns a black image if not all requirements are fulfilled\nOperating system: Default KVM (Proxmox, Linux)\nGraphics card: None\n\nBroken: Blender 3.0\nWorked: Before Blender 3.0 the frame was just not denoised\n\nIf you enable OIDN/Optix denoising without having the needed CPU flags you will get a black frame back.\nThe desired outcome would be an aborted render with a helpful error.\n\n\n1. Set up a default KVM \n2. Enable denoising \n3. Render over the CLI one Frame\n4. It will be black\n\n**Further information**\nThe config of a default KVM:\n```\nArchitecture: x86_64\nCPU op-mode(s): 32-bit, 64-bit\nByte Order: Little Endian\nAddress sizes: 40 bits physical, 48 bits virtual\nCPU(s): 6\nOn-line CPU(s) list: 0-5\nThread(s) per core: 1\nCore(s) per socket: 6\nSocket(s): 1\nNUMA node(s): 1\nVendor ID: AuthenticAMD\nCPU family: 15\nModel: 6\nModel name: Common KVM processor\nStepping: 1\nCPU MHz: 3399.998\nBogoMIPS: 6799.99\nHypervisor vendor: KVM\nVirtualization type: full\nL1d cache: 384 KiB\nL1i cache: 384 KiB\nL2 cache: 3 MiB\nL3 cache: 16 MiB\nNUMA node0 CPU(s): 0-5\nVulnerability Itlb multihit: Not affected\nVulnerability L1tf: Not affected\nVulnerability Mds: Not affected\nVulnerability Meltdown: Not affected\nVulnerability Spec store bypass: Not affected\nVulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization\nVulnerability Spectre v2: Mitigation; Full AMD retpoline, STIBP disabled, RSB filling\nVulnerability Srbds: Not affected\nVulnerability Tsx async abort: Not affected\nFlags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm rep_good nopl cpuid extd_apicid tsc_known_freq pni cx16 x2apic hypervisor cmp_legacy 3dnowprefetch vmmcal\n l\n```\nThe command that I used to render one frame: \n```\n./blender -b --debug --debug-cycles --python-expr 'import _cycles;print(_cycles.with_openimagedenoise);print(_cycles.with_embree);print(_cycles.with_osl)' \"your path to the .blend\" -f 1 \n```\n\n[oidn_disabled.blend](oidn_disabled.blend)\n[oidn_disabled.txt](oidn_disabled.txt)\n\n[oidn_enabled.blend](oidn_enabled.blend)\n[oidn_enabled.txt](oidn_enabled.txt)\n\n[optix_enabled.blend](optix_enabled.blend)\n[optix_enabled.txt](optix_enabled.txt)\n\n\nIf I set up the KVM to use HOST at least OIDN works\nHOST config:\n```\nVirtualization: AMD-V\nHypervisor vendor: KVM\nVirtualization type: full\nL1d cache: 384 KiB\nL1i cache: 384 KiB\nL2 cache: 3 MiB\nL3 cache: 16 MiB\nNUMA node0 CPU(s): 0-5\nVulnerability Itlb multihit: Not affected\nVulnerability L1tf: Not affected\nVulnerability Mds: Not affected\nVulnerability Meltdown: Not affected\nVulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp\nVulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization\nVulnerability Spectre v2: Mitigation; Full AMD retpoline, IBPB conditional, STIBP disabled, RSB filling\nVulnerability Srbds: Not affected\nVulnerability Tsx async abort: Not affected\nFlags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 fma cx1\n 6 sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw perfctr_core ssbd ibpb vmmcall fsgsbase tsc_adjust bm\n i1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr virt_ssbd arat npt nrip_save arch_capabilities\n```\n**Why it would be nice to have the bug fixed:**\nWe have a renderfarm that consist out of random machines and it is always a problem if random frames are black/not denoised/strange colored/broken/out of order. ", "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", "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", "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", "[ Linux/ Wayland ] Cannot use evee with nvidia\nOperating System: Arch Linux \nKDE Plasma Version: 5.27.7\nKDE Frameworks Version: 5.108.0\nQt Version: 5.15.10\nKernel Version: 6.4.10-arch1-1 (64-bit)\nGraphics Platform: Wayland\nProcessors: 8 × Intel® Core™ i5-9300H CPU @ 2.40GHz\nMemory: 15.3 GiB of RAM\nGraphics Processor: Mesa Intel® UHD Graphics 630 + Nvidia GTX 1660 ti \n\n\nBroken: Blender 3.6 (in wayland session) \nWorked: Works in X11 session with nvidia prime.\n\nIn x11 i can use blender evee with nvidia-prime but in wayland i cannot use blender evee with nvidia prime. The blender window \ndoesn't open at all. \n\nI have two graphics card, one integrated intel & another discrete graphics card nvidia. \nCycles works fine with nvidia in wayland session but when i try to use evee it uses integrated graphics instead of \nnvidia card. \n\n\n1. Login to wayland session.\n2. Open blender with nvidia-prime to run the program with nvidia. ( $ prime-run blender )\n3. Try to render using evee\n\n", "Inconsistency between CPU and OptiX GPU when using OSL hash function \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken version: 3.5.0 Alpha\nWorked: NA\n\nWhen using the Open Shading Language \"hash\" noise function there is an inconsistency between the CPU and OptiX GPU implementation. The most noticeable is that the OptiX output is grey scale while the CPU implementation has colour.\n\n|CPU|OptiX|\n| -- | -- |\n|||\n\n1. In user preferences change your Cycles rendering backend to OptiX (requires a OptiX compatible GPU)\n2. Download the attached blend file and open it.\n3. Enter the rendered viewport and compare the results with CPU rendering and OptiX GPU rendering.\n\n[OptiX CPU OSL Hash Inconsistency.blend](OptiX_CPU_OSL_Hash_Inconsistency.blend)", "Fix big LIghtCache restriction\nAs reported in #78529 saving big lightcache is impossible due to blocksize restriction.\n\nFor now we restrict the lightcache size that can be written to disk but it would be better to slice the huge textures to avoid such limitation.\n\nHowever this needs some refactors in GPUTextures namely the need of a properly exposed `glTexSubImage2D` and `glTexSubImage3D`.", "Disable Constraint Drivers Not Visible When Opening Older Files in 3.0\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\nWorked: (before 3.0)\n\nCaused by d6891d9bee\n\nDrivers put on the \"Disable Constraint\" switch are no longer accessible in the viewport.\n\n**`2.93`**\n\n\n[Constraint Driver Bug 2.93.5.blend](Constraint_Driver_Bug_2.93.5.blend)\n\n**`3.0`**\n\n\n[Constraint Driver Bug 3.0.blend](Constraint_Driver_Bug_3.0.blend)\n\nDriver does still work and is visible in the Driver Editor window, however it appears invisible on the constraint, Right Clicking the icon where the Driver is supposed to be does not come up with options to delete or edit that driver, button itself cannot be manually turned On or Off either.\n\nIn any Blender before 3.0 Add a driver to the \"Disable Constraint\" button on any of the constraints. Save the file and open it in 3.0.\n\n", "Cycles: Persistent Data stops \"Animated Seed\" from working\nOperating system: Linux-5.15.0-2-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 the Persistent Data option is enabled the `Animated Seed` option doesn't appear to operate work.\n\n1. Create a scene in Cycles with noticeable noise.\n2. In the `Advanced` tab of the `Sampling` settings, enable `Animated Seed` (click on the clock icon beside the `Seed` value)\n3. In the `Performance` tab of the `Render Properties` enable `Persistent Data`\n4. Render an animation.\n5. Notice that the seed pattern doesn't change between frames. Disabling `Persistent Data` resolves this.\n\nHere is a file that does steps 1-3 for you:\n\n[#93534 - Persistent Data - Animated Seed.blend](T93534_-_Persistent_Data_-_Animated_Seed.blend)\n\nNote: The first time I rendered this, frame 1 has a different seed than all the other frames. Subsequent re-renders sees the seed used on frame 1 matching all other frames.", "Cycles brightness difference between CPU, GPU and CPU+GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.1\n\nSeems a noticeable difference on how cycles render depending if you use GPU, CPU and XPU and you use transparent materials.\n\nGPU\n \n\nCPU:\n\n\nCPU+GPU:\n\n\nAs you can see, there's a visible line at the top of the render-\nTrying to encapsulate the bug i get this result. \n\nCreate a interior scene, add a glass material and try to render with both CPU and GPU.\n**i guess the problem is related to the material.\n\n\nHere is the scene.. \n[GlobalIllumination2.blend](GlobalIllumination2.blend)\n\nThanks.\n\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)", "Cycles regression testing for GPU devices\n**Background**\n\nThe Cycles automated regression tests so far only ran on the CPU.\n\nWith some environment flags it was possible to execute a script that runs them on other devices, but this is cumbersome. The goal of this task is to add a CMake option to enable running the regression tests on GPU devices in addition to CPU devices.\n\nThe reference images are currently only valid for CPU rendering. Keeping differeing reference images updated will have to wait until we have CI infrastructure for testing GPU rendering. For now we can do a few things:\n* Do nothing and manually check when tests fail\n* Increase difference thresholds for tests that only differ a little\n* Disable failing tests for GPU testing\n\n**Status**\n\n- [x] CYCLES_TEST_DEVICES option to specify devices to test\n- [x] Blacklist failing CUDA tests\n- [x] Blacklist failing OPTIX tests\n- [ ] Verify HIP tests are working\n- [ ] Enable GPU testing on the buildbot", "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" ]

[ "Cycles HIP issues on Debian\nOperating system: Linux-6.0.0-1-rt-amd64-x86_64-with-glibc2.35\nDevuan GNU/Linux 5 (daedalus/ceres) x86_64 (aside from init system differences this distribution can be treated as Debian sid)\nGraphics card: Vega 20 [Radeon VII]\n[system-info.txt](system-info.txt)\n[dmesg](dmesg)\n[lshw](lshw)\n\nBroken: 3.4.0 Alpha, branch: master, commit date: 2022-10-21 11:11, hash: 26f181c6b7b2\n\nAs of recently Debian is packaging ROCm drivers for AMD GPUs and version 5.2.3-1 just landed in unstable (sid). This version as per official AMD ROCm release notes is an equivalent of 22.20.1.\nOne of the differences between official AMD's version and Debian's is ROCm installation path `/opt/rocm/` versus `/usr/lib/x86_64-linux-gnu/` respectively:\n\n```\nsudo find / -iname \"libhsa*\"\n\n/usr/share/doc/libhsakmt1\n/usr/share/doc/libhsa-runtime-dev\n/usr/share/doc/libhsa-runtime64-1\n/usr/lib/x86_64-linux-gnu/libhsa-runtime64.so\n/usr/lib/x86_64-linux-gnu/libhsa-runtime64.so.1.5.0\n/usr/lib/x86_64-linux-gnu/libhsa-runtime64.so.1\n/usr/lib/x86_64-linux-gnu/libhsakmt.so.1\n/usr/lib/x86_64-linux-gnu/libhsakmt.so.1.0.6\n\nsudo find / -iname \"libamdhip64*\"\n\n/usr/share/doc/libamdhip64-dev\n/usr/share/doc/libamdhip64-5\n/usr/lib/x86_64-linux-gnu/libamdhip64.so.5\n/usr/lib/x86_64-linux-gnu/libamdhip64.so\n/usr/lib/x86_64-linux-gnu/libamdhip64.so.5.2.21153-\n```\n\nWhen ROCm is installed from Debian's repositories Blender does not detect AMD GPU even thou the ROCm platform is validated with AMD's tools. \nHow_To_Install_ROCm.html#_Installation_Methods\n\nrocminfo and hipconfig outputs with both GPUs detected:\n[rocminfo](rocminfo)\n[hipconfig](hipconfig)\nAnd how it looks in package manager and Blender:\n\n\n\nI suspect this is caused by ROCm paths being different between Blender libraries and HIP installed from Debian's packages, but I could be very much wrong. \nPlease consider this report as void if this is a mistake on my side. I'm reporting this here only because this installation differs from the official one and ROCm is a very new package in Debian.\n\nOn Debian unstable (sid) Linux distribution:\n- install rocm packages from apt\n- validate install with `rocminfo` and `hipconfig`\n- open Blender and check if there are any devices detected in `Preferences` -> `System` -> `HIP`\n\nAdditional info:\nROCm packaging is done by Debian AI team:\n10/\nteam-project" ]

[ "Subsurface Scattering Radius issue with low values or zero in RGB channels\nOperating system: Darwin-15.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-10.14.74\n\nBroken: version: 2.81 (sub 9)\nWorked: (optional)\n\nWhen using Scattering Radius, we can adjust the scattering effect per RGB channel. The problem is when one of these values is very low, near to zero. We see a reflection on the surface of that channel.\n\n01 object with principle shader and set Scatter Radius to R=.6, G=.35, B=0, basic gray color diffuse, soft roughness\n02 Add HDR with strong lighting from 1 side and add perhaps sunlight (power 1, angle 5deg)\n03 You see a blueish highlight apear on this material\n\nSee attached scene and example shots\nleft bl 2.79 - right bl2.81 > alterered material darker for better highlight\n\n\nleft bl 2.81 - right bl2.79\n\n\nleft bl 2.81 with Scatter Radius Blue 0.02 - right bl2.80 with Scatter Radius Blue 0.00\n\n\nHere's another example, simplified material to show the scatter effect. Left is bl280 right is bl279\n\n\nIs it perhaps due to the number 0 that blue light shows at the surface of a model? This cause weird reflections. I bumped into this from a scene from Rico Cilliers. I believe it was made in an Beta bl 2.80 in december 2018\n\nAfter some talk with him, he noted that there an issue with Scatter Radius in the beginning. Number of zero or near zero would cause this weird haze/reflection.", "Visual geometry to Mesh does not duplicate a linked object\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.2.0 Alpha\n\nWhen applied to a linked object, Visual geometry to Mesh does it on the shared mesh.\n\nApply the subdiv modifier to the original cube. Link copy it. Use Visual geometry to Mesh on the linked object. Now select the original object and go into edit mode. You should see that the the subdiv modifier has been applied.\n\nThere is also a side issue to this. If you put a Decimate modifier (something visible like planar 20 degrees) on the original object, selected the linked one and go into edit mode, you'll see that in the viewport the modifiers on the original object don't show their effect.", "Performance test and notes regarding multires\nDaniel Bystedt and Dalai Felinto had a catch up meeting 11:th of May. During that meeting we talked a bit about sculpting. Dalai asked me to create this task and to add a test file and some more info which is detailed below.\n\n**Computer and Blender specs**\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nversion: 2.92.0\n\n\n**Blend file**\n[orc_head_5_subd_v001.blend](orc_head_5_subd_v001.blend)\n\n**Switching symmetry on/off**\nSwitching symmetry on/off is something a user does quite often in order to not make human faces (for example) look totally mirrored when sculpting. It’s a bit surprising that it is so slow when the vertex count is high. \n\n@PabloDobarro explained via chat: *The lag from turning on/off symmetry is because of a BVH rebuild. Symmetry is a property of meshes, so each time a property of the mesh changes, it considers it as a change in geometry and rebuilds the BVH again. It should be possible to do a more proper tagging of these changes to avoid this, which will fix this multires and any other future system we can make.*\n\n|Vertex count| Time to switch symmetry on/off\n| -- | -- |\n|10 million| 3 s 7ms|\n\n**Subdivide performance**\nSubdividing when vertex count will be above 1-3 million is usually rather slow. The user only have to subdivide the model once when sculpting a model so it’s not a frequent thing that you do. If it could be made faster it would be a nice improvement though\n\n|Vertex count| Time subdivide with multires|\n| -- | -- |\n|subdiv 2.6 million > 10 million| 16 s 5 ms|\n\n**Switching sculpt levels performance**\nSwitching sculpt subdivision levels is something the user does quite often, so if it is fast it would be great. The performance is not terrible though.\n\n|Vertex count| Time subdivide with multires|\n| -- | -- |\n|2.6 million > 10 million| 1 s 8 ms|\n\n\n**Performance investigation starting point**\n- Run a profiler to see if we do not have obvious bottlenecks and see that all threads are occupied\n- Measure exact memory footprint of OpenSubdiv topology. If it is not terribly big, can cache those on different levels while being in the sculpt mode\n- Look into sparse patch tables. This seems to be a solution to a specific of OpenSubdiv which is related on a single-threaded nature of topology construction\n- Run quick and dirty check whether using GPU evaluation brings 10x speedup (quick and dirty is because doing proper integration is not trivial and you don't want to do it if the speedup is not that great)\n- Check whether all tools are properly multi-threaded\n- Make ID_RECALC_PARAMETERS to work for non-geometry properties of meshes (to mitigate the symmetry lag)", "Linked data-block has \"pointer\" property still active\nBroken: version: 3.4.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: Probably never\n\n\n\n[torus.zip](torus.zip)\n\nOpen torus.blend. It has a linked collection containing the selected object `Torus`.\n\nAs you can see in the image, the \"Object\" rna properties (parent, and the array modifier one) are both active:\n\n{[F13627034](image.png), size=full}\n\nIn fact you can even click on the property to change it (the popup show up, but clicking on it at least doesn't change it):\n\n{[F13627039](image.png), size=full}", "Expand face sets freeze blender when cursor is on mesh boundaries\nOperating system: Linux (Mint 21) \nGraphics card: RTX 3070 Ti\n\nBroken: 4.0.0 alpha, 12f51bd1c77b, master, 2023-09-21, as found on the splash screen)\nWorked: 3.6\n\nTry to create new face sets from first or last face loops on a cylinder.\nBut expand Face Set from boundaries is frozen in 4.0 alpha.\n\n\n- Open the blend file\n\n- Switch to Sculpt mode\n\n- Move your cursor outside boundaries and press Expand Face Set (Shift +W). (See on pictures)\n\nAt this point, Blender freeze, not crash. No more info in console.\n\nBug :\n\n\nExpected (3.6 version): \n\n\nThanks for your help.\n\n", "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", "'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).", "Editing redo panel properties of torus in edit mode reverts some steps\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.24 355.11.10.50.10.103\n\nBroken: version: 3.4.1\nWorked: (never worked as expected)\n\nAdding and then adjusting a Torus or any Add Mesh add-on in edit mode reverts edits made to nodes, video sequencer, and more, since entering edit mode on the mesh object.\n\n1. Go to the Geometry Nodes workspace\n2. Select the default cube\n3. Click the New button to add the Geometry Nodes modifier and create and assign a new node group\n4. In the 3D Viewport switch to Edit mode\n5. In the Node Editor, pour your heart and soul into crafting an elaborate node tree (lol, jk 👀💔)\n6. In the 3D Viewport add a Torus\n7. Tweak any setting in the Adjust Last Operation panel\n8. Observe Geometry Nodes edits reverted (all edits since entering edit mode in the 3D Viewport)\n\nNo other built-in mesh primitives (nor even primatives!) have this effect, but the Add Mesh add-ons all do.\n\nI have checked some of the editors to see what data is reverted and what is preserved. This is not yet an exhaustive review.\nThe following data is reverted:\n- Video Sequencer\n- Properties\n- every Node editor\n- Timeline\n\nThe following data is preserved:\n- Preferences\n- Text Editor\n- Python Console\n- Movie Clip Editor\n- UV Editor\n\nThe Outliner has mixed results:\n- Hierarchy expansion reverts in Blender File, Data API, and Orphan Data but not in Scenes nor View Layer.\n\nSome editors have special behavior:\n- Image editor\n - Paint mode\n - {Add torus, paint image, tweak torus} reverts the paint\n - {Paint, add, tweak} kicks out of Edit mode into Object mode\n - Switching Image Editor modes does not close the ALO panel. The following sequence of steps produces a Python error:\n - Add torus\n - Switch Image Editor modes\n - Adjust torus\n (If this merits its own tracker issue, tell me and I will write one up. This all seems so tied to one root culprit that it is not my initial inclination to do so)\n\n", "Move the transform info away from the header, into the viewport.\nCurrently, when you transform any item in Blender, we take over the header while the transform is happening:\n\n\n\nThis makes for a vey flashing/blinking UI, where both the header and the viewport gizmo disappears and re-appears in a jarring way. \n\nInstead, the header and viewport gizmos should stay untouched, and the transform info can be moved to the viewport along the bottom.", "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", "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)", "Wrong undo/redo sequence with direct transform change (via Item/transform panel or addon)\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: 2.93.1\n\n\nUndo operation is not working properly with `Copy attributes addon`.\n[refer the video to understand the situation better]\n\n\n**Exact steps to Reproduce the error**\n\n[2021-07-28_13-59-32.mp4](2021-07-28_13-59-32.mp4)\n\n**To reproduce**\n- 0. Make sphere, go to sculpt mode.\n- 1. Draw «1» on sphere\n- 2. Change location via item panel\n- 3. Draw «3» on the sphere\n- 4. Undo actions with {key Ctrl+Z}: undo order is broken\n\n---\n\n**Exact steps to Reproduce the error (Addon Case)**\n\n- Open .blend file\n- Enable Copy attributes addon\n- Select both mesh objects\n- Do {key Ctrl C} -> `Copy Locations`\n- Switch to edit mode\n- Perform some changes to the mesh\n- Switch to object mode\n- Perform undo operation.\n\n[Notice that the undo operation ignores all the steps from edit mode and directly switches the mesh to the initial position]\n\n\n[2021-07-27_13-33-38.mp4](2021-07-27_13-33-38.mp4)\n\nTest File:\n[#90234.blend](T90234.blend)", "Statistics Viewport Overlay Showing Incorrect Value\nOperating system: Windows 11\nGraphics card: Nvidia GeForce RTX 1650\n\nBroken: 3.6\nWorked: Every other version I've used so far\n\nWhile working in the viewport, the \"Viewport Overlay: statistics (edges count)\" glitches out and shows the wrong number. Sometimes being absurdly high. The image shows the main objects in my scene with the most geometry, mostly being 2k to 10k faces each. It gets a bit annoying when I can't see the right count. I'm not sure how to reproduce the error on command, but I'll keep looking!\n\nBased on the default startup or an attached .blend file (as simple as possible).\nIt happens mostly while I swap in and out of pose mode but then again, I'm not too sure. However, this is usually the last action I take before I notice. I'm sorry for the insufficient information, but I hope you find the problem.\n\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.", "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" ]

[ "Object with OpenSubdiv has 0Verts 0Edges 0Poly\n\nWindows 10. GTX 760\n\nBlender 2.76 from Blender.org\nDate 2015-09-17\n Hash:c586e30\n\nBlender doesn't show polycount of model with OpenSubdiv,\nAlso shows wrong dimensions.\n\n[buggg.blend](buggg.blend)\n\n" ]

[ "Slow and laggy transforms using the tool pop-up box after clicking the transform gizmo\nOperating system: Windows 10 \nGraphics card: Geforce GTX 1650 Super\n\n3.5.0 (also same issue in 3.4.1)\n\nWhen I move/rotate the gizmo in the viewport with the mouse it is nice and responsive. However, when I use the rotate and move transform value sliders in the transform pop-up box the values are very slow to update and the viewport object being transformed lags quite drastically. Not only when using the mouse to slide value but using the increment arrows too. This seems to only be when using the TRANSFORM_OT_translate.value / TRANSFORM_OT_rotate.value / TRANSFORM_OT_resize.value \nAs a note the viewport side panel Item-Transform (Object.location, Object.rotation_euler, Object.scale) doesn't seem to have this problem and updates as it should, allowing nice responsive viewport updates as the value slider is dragged.\n\n- Unzip attached file\n- Open .blend file\n- Select any object\n- Rotate it with the help of viewport gizmo\n- Now change values from redo panel (notice slowdown).", "The Object Mode drop down menu in the 3D viewports is not reactive to larger font point settings.\nOperating system: Windows 10 1803\nGraphics card: nVidia RTX 2070\n\nBroken: v 2.80 as found on the splash screen\n\nThe Object Mode drop down menu in the 3D viewports does not properly resize itself if the user picks a larger font point size in the Themes section of the preferences. Instead of resizing the control truncates the overrunning text with a square character.\n\nStart Blender\nIn Preferences \\Themes \\ Text Style change the Widget Points setting from the default of 11 to a larger value. I used 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", "inset and bevel edits crashing blender 3.x\nThreadripper 1950x 128 gb ram 2tb SSD (home)\nNVIDA 3080 updated to latest drivers\n\nIntel i7 64 gb ram 2 tb SSD (work)\nAMD 6900xt updated to latest drivers\n\n\nHappens on all 3.x versions of blender.\n\nIssue happens on both my home PC (the thread ripper) and my work PC.\n\nStart editing default cube add bevels, insets place some cuts... crashes within a couple of minutes. Happens in all display modes.. mesh, solid, renders. Happens with a smooth display mesh and hard edges. Super frustrating need to save just before doing any of these procedures on any modeling task. Always update video drivers which probably cant be the issue because two different families of video cards in two different machines have the same issue. Been doing this ever since I updated to Blender 3. I assume it's a plugin I installed because I can't imagine why this would happen on two completely different computers. Is there a dump file or something I can send? Here is a video of a typical crash. No dialog box... just blender vanishes in the the middle of editing.\n\n", "Regression: object.local_view_get and object.visible_in_viewport_get() always returns False\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 3.0.0\nBroken: 2.81\nWorked: 2.80\n\nCaused by 1954723635\n\nobject.local_view_get() and object.visible_in_viewport_get() always returns False\n\n1. Set Viewport in Local View.\n2. Get 3D view space, that's in the local view, (in my case C.workspace.screens- [x].areas- [x].spaces[0])\n3. Get local view state by command C.object.local_view_get. Observe that the result is False, but the object is in local view.\n4. Remove object from local View by command C.object.local_view_set. Observe that the object is hidden now.\n5. Get local view state by command C.object.local_view_get. Observe that the result is False, as expected.\n\n{[F12823064](image.png), size=full}\n\nobject.visible_in_viewport_get() have same behavior.", "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. ", "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 modeling performance regressions\nList of performance issues that we would like to fix or investigate for 2.80:\n\n* Transforming vertices in edit mode on high poly meshes is slow, due to overhead of depsgraph, mesh updates and and batch creation. Verify if there is anything unexpected happening here.\n* BMesh to mesh conversion was happening all the time at some point, is this still the case? See check_rendered_viewport_visible, it now always happens when a 3D viewport is visible, and could be quite problematic for edit mode performance.\n* Verify if custom data is only being preserved through modifier stack when needed (vertex colors, vertex groups, UVs)\n* Manipulate modal callback performance may be problematic: #55458\n", "Cannot paginate shape key list\nSteps to reproduce:\n* add any mesh (e.g. a cube)\n* in Object Data Properties > Shape Keys click '+' twenty times\n* clicking above or below the scroll bar does not paginate the list\n\nBroken: 3.5 alpha, 50c7eb14f455, master, 2022-12-19\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", "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). ", "Performance issues when moving bones of an armature when the Outliner is set to Blender file\nBroken: 2.93\n\nThis happens on heavy scenes and with many linked files, if you have an Outliner opened and set to \"Blender file\".\nThe fps drops dramatically only when trying to move a bone of an armature. It doesn't matter the complexity of said armature.\nThe problem stops happening after closing the Blender file Outliner.\nCould it be related to this other fix? T87842", "Very strong aliasing in 3.2\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2\nWorked: 3.0\n\nin 3.2, there is a very strong aliasing in edit mode. In 3.0 it is not so strong\n3.2:\n\n\n3.0:\n\n\nboth versions have the same settings. There are 16 samples everywhere and smoothing in edit mode\n[jupiter.fbx](jupiter.fbx)", "EEVEE viewport rendering loop bug when using walk or fly navigation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\nWorked: As far as I know, this bug was always in Blender\n\nEEVEE viewport rendering loop bug when using walk or fly navigation:\nwhile using fly or walk navigation and staying still, the sampling always just jumps back to 0 when finished sampling and just starts sampling over and over again thus creating an irritating loop of constant resampling\n\n1. Use EEVEE\n2. For the purpose of this example, change the scene filter size to 50px so that the effect is easily noticeable \n3. Press shift + ` to go to walk navigation (fly navigation has this bug too)\n4. Stay still so that the viewport could start sampling to the specified amount\n\nNotice when the sample amount reaches the specified viewport samples amount, rendering starts again as in if you have moved\n\n[EEVEE viewport navigation loop bug.blend](EEVEE_viewport_navigation_loop_bug.blend)\n\n\n\n\n\n", "Rigid body bugs\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.21\n\nBroken: version: 2.93.1\n\nSimulation somehow broken for small (less than 1 cm) or light (less then 100 grams) objects. In first example below object stay still between bouncing and small shivering. And that is just one example. Another examples are – reaching speed of light instantly (one frame), partial simulation when one object (or some objects) acts like it suppose to, but others act completely inadequate, two or three similar parts in one simulation (example 2). I tried different options but nothing helped. \"Substeps per frame\" and \"Solver iterations\" seems not working because there are no actual changes with different values or simulation just goes nuts.\n\n[r_body-bug.blend](r_body-bug.blend)\n[r_body-bug2.blend](r_body-bug2.blend)\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)" ]

[ "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", "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", "Edit Source operator missing the \"see XXX.py in the text editor\" info in the status bar\nOperating system: Linux-6.4.13-200.fc38.x86_64-x86_64-with-glibc2.37 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 16.0.6, DRM 3.52, 6.4.13-200.fc38.x86_64) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6 LTS\n\nCaused by 1251b7c4001b3f7de158c089256b04c887d6c5bb\n\nEdit Source operator missing the \"see XXX.py in the text editor\" info in the status bar\n\n- use the context menu on a button in the UI and call Edit Source\n- this is missing the following info in the status bar:\n\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", "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", "Geometry Nodes: Viewer overlay disappears when enabling In Front\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\nWhen enabling \"In Front\" in the Viewport Display options of an object, which currently has a geometry nodes viewer overlay, that overlay disappears.\n\n| Viewer object: `In Front`: OFF | Viewer object: `In Front`: ON |\n| -- | -- |\n|  |  |\n\n1. Open the attached file in 3.4 or newer versions.\n2. Make sure the viewer node is enabled in the geometry nodes of `Plane.001`.\n3. Under Viewport Display, toggle `In Front` for `Plane.001`.\n\n[bug_report.blend](bug_report.blend)\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)", "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", "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", "When search is active in keymap section of preferences, top level text truncated for no reason.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.99\n\nBroken: version: 4.0.0 Alpha\n\nWhen search is active in keymap section of preferences, top level text truncated for no reason.\n\n\nGo to Edit > Preferences > keymap.\nIn the search box type \"eye\".\nSee the useless truncated text, and all the unused space.\n\n", "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", "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", "UILayout.emboss missing UI_EMBOSS_NONE_OR_STATUS\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 860M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93 release and earlier revisions of 3.0\n\n`UI_EMBOSS_NONE_OR_STATUS` missing from `UILayout.emboss`. There is new `NONE_OR_STATUS`, but it does not work the same.\n\nHere is the difference:\n * `UI_EMBOSS_NONE_OR_STATUS` in Blender 2.93 makes emboss look `None`, but keeping UI active.\n * `NONE_OR_STATUS` in Blender 3.0 makes emboss `None` and UI not active.\n\n[emboss.mp4](emboss.mp4)\n\n - Run script from attached blend file in 3.0 and 2.93 versions.\n - Try to interact with popover elements.\n\n[emboss.blend](emboss.blend)", "Python API bindings for volume render pass broken\nOperating system: macOS-11.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 555X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\n\nPython API calls for Volume render pass settings are missing.\n\nEnabling the render pass show in the info window `bpy.data.scenes[\"Scene\"].(null) = True`.\nSetting it with python fails too:\n```\n>>> C.scene.view_layers['View Layer'].use_pass_volume_direct = True\n\nTraceback (most recent call last):\n File \"<blender_console>\", line 1, in <module>\nAttributeError: 'ViewLayer' object has no attribute 'use_pass_volume_direct'\n```\n\n", "No way to distinguish enum buttons that support shift-click to select multiple\nBlender has some buttons that allow shift-click to select multiple, but no way to show the difference. eg:\n\nTransform Tool, Gizmo's (Move / Rotate / Scale)" ]

[ "blender 4.0 Alpha . Search feature of Geometry Nodes does not work anymore.\nOperating system: Linux-6.2.0-26-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 580 Series (polaris10, LLVM 15.0.7, DRM 3.49, 6.2.0-26-generic) AMD 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6 and earlier \n \nSearch feature for Geometry Nodes does not work anymore.\n\nCreate a new Geometry Nodes tree > Right Click and select Find or press Ctrl F to bring up Search. No Nodes can be found.\n\n", "No \"Search\" option in the shortcut menu in the compositor\nSystem Information\nOperating system: Win 10 64bit\nGraphics card: Nvidia GTX 1660 Ti\n\nBroken: blender-4.0.0-alpha+main.8f21353b5dc8-windows.amd64-release\nWorked: blender-4.0.0-alpha+main.30de3d7c1a79-windows.amd64-release\n\n\nThere is no \"search\" option in the menu in the compositor tab, when the menu is invoked with the command SHIFT+A\n\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", "Annotation tool: wrong undo order and different in different modes\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: 2.93.2\nBroken: 3.0.0 Alpha, `c1f5ac7cfe`, 2021-07-25 18:36\nBroken: 2.83.17\nWorked: never\n\n\n| Object mode | works correct, as expected. Each undo action undoes 1 stroke |\n| -- | -- |\n| Weight paint | works properly |\n| Vertex paint | works properly most of the time, sometimes as Texture paint |\n| Texture paint | do not undoes each stroke but after number of {key Ctrl+Z} (n=strokes) undoes all strokes simultaneously or disables em at n=strokes+1 and undo previous action (mode switch in my case) |\n| Edit mode | same as Texture paint |\n| Sculpt mode | Undoes strokes one by one, but on the last stroke it do not react to {key Ctrl+Z} once, and then on the secon disables stroke and previous action (mode change) |\n\n**Steps to Reproduce**\n- Open default scene\n- Switch to Edit or texture paint mode\n- Draw 4 strokes with annotation tool\n- Undo 4 times (nothing happens to any stroke)\n- Undo again: Clears all strokes\n[2021-08-15_15-46-27.mp4](2021-08-15_15-46-27.mp4)\n\n", "Redo Panel changes the state of the last active Vertex Group\nOperating system: macOS-12.4-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.4.0 Alpha\n\nActivating a certain Vertex Group before calling the Smooth Vertex Weights (or another weight paint operator) won't necessarly respect the choices even when the Subset Active Group is enabled. As soon as you interact with the pop-up operator's parameters seems Blender will pick up another Vertex Group instead of the current activated one.\n\nVideo:\n[WightPaint-SmoothOperator-Bug.mp4](WightPaint-SmoothOperator-Bug.mp4)\n\nSample file:\n[Smooth-Operator_Bug.blend](Smooth-Operator_Bug.blend)\n\n\n1. Paint some vertex groups on your mesh.\n2. Click on one of your groups to set it active.\n3. Call the Operator from Weight Paint > Weights > Smooth\n4. Set operator's Submenu to Active Group\n\n*Note that is might switches to another Vertex Group as soon as you interact with the pop-up's operator parameters.\n_ \nWorkaround: after setting the desired Vertex Group active, you must perform another action like clicking with you brush on an empty area of the 3D view. This way it will respect the active Vertex Group selected.\nIt seems some kind of residue living in the memory of undo buffer. I don't know... could you please investigate?\n\nThanks you!\n\n", "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", "Bevel modifier creates zero area faces with unexpected normals when clamping to an unbeveled edge.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0\nWorked: I cannot find a working version, I've checked 2.83 and 2.81. (I tried to use 2.79, but I've forgotten how to use it.)\n\n\n\n\nEdit (Baardaap): When the bevel modifier is clamped to an unbeveled edge, it creates a zero area face. This in itself it to be expected and not really a problem though it might be nice to prevent. When you bevel with the bevel operator the same happens. The problem is that the bevel modifier causes a recalculation of all normals, which generates random normals for the zero area faces. These random normals lead to strong shading artifacts when the shading is set to shade smooth.\n\noriginal report follows:\n----------------------------------------\n\n\n\n\n\n\nInconsistent normal behaviour when using a bevel modifier with\n(a) amount exactly matching the face dimension (or is clamped), and\n(b) auto smooth off\nWhen compared with auto smooth on, or just bevelling an edge directly.\n\nIn the sample file attached, I've created an L shape by creating a plane, then extruding 3 additional edges.\nI've added a reflective material to see how the normal affects the reflections.\nFor each L shape, I've then added a bevel modifier, only changing amount/segments. Or alternatively I've done bevel edge, and only set amount/segments.\nThen I've either set to smooth or flat shading, and/or turned-on auto-smooth.\n\nIn the attached file, I've prepared the different test scenarios.\nFrom bottom to top:\n - Modifier/Flat,\n - Modifier/Smooth, // This is the row where I see inconsistencies (highlighted in red)\n - Modifier/Smooth/AutoSmooth,\n - BevelEdge/Flat,\n - BevelEdge/Smooth,\n - BevelEdge/Smooth/AutoSmooth,\n\nFrom left to right:\n - Amount=2, Segments=10, // obvious difference for the flat plane above the bevel, plus weird anomaly for top segment of bevel\n - Amount=2, Segments=3, // obvious difference for the flat plane above the bevel\n # Amount=1, Segments=3, // this row has no apparent differences\n\n\n\nWhen viewing the file, I find it best to use material preview mode, then orbit up/down, and compare the reflections of the different rows.\n\n\nMy analysis.\nWhen performing a bevel, the faces being bevelled shrink to make space for the bevel, but retain their original normal.\n \n\nWhen the bevel amount matches the face size, then those faces still exist, however they have zero size - represented by the red lines.\n\n\nUsing the spreadsheet in 2.93, I can see inconsistencies with the normal vector for these faces.\n\nHere I've set the bevel modifier segments=1, and amount=2.\n\n\nAnd the corresponding spreadsheet (annotated).\n\n\nYou'll note that the two empty faces do have valid unit normals, though both a pointing at Z=1.\nYou would expect the vertical face - [x] to have a normal with X=1.\n\nHowever if you compare with the reference scenarios like having auto-smooth=on, or applying a bevel edge directly, this is what you see.\n\n\nIn this case, rows 0 and 4 actually have the normal vector set to 0, 0, 0. (I.e. technically an invalid unit vector.)\n\n\nSo, what I believe is happening is that when there is an invalid normal vector, then blender refuses to perform smoothing across from one face to another. The smoothing ends at the bevel edge and the adjacent face in this case is shaded flat.\n\nGetting back to the bevel modifier when auto-smooth is off, while this has valid unit vectors, one of those vectors has the wrong orientation.\nThis is why there is a reflection anomaly on the vertical face, but not on the horizontal face.\n", "Nodes: Group input subtype \"Angle\" max values are in radians, but the default implies degrees.\nOperating system: Linux-5.4.0-148-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: 3.6.0 Alpha\n\nThe subtype \"angle\" in the socket editor provides a default value in °, and a min and a max value, which seem related to the default setting in degrees, so the user assumes the slider in the modifier frontend UI to stop at the set values. Which it doesn't. Set max to say 1, and the slider will stop at 57,3° (180/pi), not at 1°.\n\n\n", "The Tool Settings UI should update when holding modifier keys\nIn Sculpt Mode, users can hold Ctrl to invert the effect of the current tool. However, both the tool settings + and - buttons, as well as the color of the brush cursor, don't update to reflect that you've inverted the effect. \n\nBoth of these should update their state when the user holds Ctrl.\n\n\n\nThe same is true for the selection tools and their modes.\n\n{[F5686801](Screenshot_2018-11-23_at_00.36.36.png), full=true}\n\nWhen holding Shift or Ctrl to add or remove, the state of these buttons should update to reflect that. ", "Quad view toggle changes \"main view\" orientation with lock rotation is unchecked\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon HD 6700 Series ATI Technologies Inc. 4.5.13417 Core Profile Context 15.301.1901.0\n\nBroken: version: 2.82 (sub 7)\nWorked: Never (2.79+)\n\nQuad view toggle changes main view orientation with lock rotation is unchecked\n[Project 121.mpg](Project_121.mpg)\n\n- Open general template\n- ctrl + alt + q to toggle quad view\n- In side panel > Quad View uncheck Lock\n- Move mouse to any dedicated ortho views\n# Hit ctrl + alt + q twice\n\nTop right view - \"main\" view has orientation of view where mouse cursor was.\n", "Curve to Mesh node creates wrong face orientation with cyclic profile curve\nOperating system: Linux-6.1.26-x86_64-with-glibc2.37 64 Bits\nGraphics card: AMD Radeon RX 6800 XT (navi21, LLVM 15.0.7, DRM 3.49, 6.1.26) AMD 4.6 (Core Profile) Mesa 23.0.3\n\nBroken: version: 3.5.1, branch: Unknown, commit date: Unknown Unknown, hash: `Unknown`\nWorked:\n\nThe `Curve to Mesh` geometry node creates incorrect face orientation when using a cyclic `Profile Curve`. This bug only happens with cyclic profile curves, non-cyclic profile curves work correctly.\n\nInside of the attached `.blend` file there are two identical curves. The left curve uses the curve `Bevel` option. The right curve uses the `Curve to Mesh` geometry node.\n\nThey should produce the same results, but they don't.\n\nThe `Profile` curve is just a standard `Add` -> `Curve` -> `Circle`.\n\n1. Open the attached `.blend` file.\n2. Notice that the curve on the left has the correct face orientation.\n3. Notice that the curve on the right has the wrong face orientation.\n\n", "Expose symmetry options for operators that use them in weight paint\nCurrently there are quite a few weight paint operators that use the symmetry/mirror setting under the hood.\n\nThis is great, but we should expose this in the operator settings so that is might be easier for the user to realize that the mirror/symmetry options also influence operators if they are on.\n\nThe new exposed operator settings should use the current symmetry options from the mesh/object.\nBut the user can then see and set the symmetry value manually in the operator if they wish.\nThis can be used to create custom shortcuts/key binds that always has symmetry on or off.\n\nThe operators use `ME_SYMMETRY_X` or `ME_EDIT_VERTEX_GROUPS_X_SYMMETRY` and are in `source/blender/editors/object/object_vgroup.c` and `blender/editors/sculpt_paint/paint_vertex_weight_ops.c`.", "Digital Pen will lose pressure sensor after Ctrl + R\nOperating system: Windows 11\nGraphics card: RTX2060\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n3.5\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nmy digital pen is Gaomon M6, and the issue is reproduceable 100%.\n\nin sculpt mode, before Ctrl + R, blender will accept pressure percent, resulting in small or narrow sculpt effect. after it will be 100% always.\n\n", "Constraint with custom space not limiting transformation\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: Blender 3.6.2\nWorked: Never\n\nAffect transform conflict with custom space\n\nAccording to documentation, Affect Transform option will limit manual rotation, but it doesn't with custom space. It works with local space.\n\n**Steps To Reproduce**\n\nOpen [file](https://projects.blender.orgattachment) and rotate contrained bone. Check bone transformaton - it is not limited.\n", "Make easing equations to follow the curve start point normal\nThe easing equations are great, but they can't be editable. What is the best thing about them: the user doesn't need to worry about the animation if some point change its location.\n\nBut there is an aspect of easing equations that still can be improved. They don't follow the normal of the curve. In an animation, this mean that they can break any previous movement of a object, instead of starting from it.\n\nCurrently, this is what happen if we change the bezier control point of the start point of an easing equation Cubic In:\n{[F86114](blender-cubic.gif) size=full}\n\nFor Bounce In:\n{[F86115](blender-bounce.gif) size=full}\n\nYou can see how the animation break when the easing start, because the first internal point of the easing curve doesn't follow the previous curve normal.\n\n**The proposed solution**\nTo solve it, the first internal control point of an easing equation should be placed above the curve normal. This is what would be expected for Cubic:\n{[F86120](proposed-cubic.gif) size=full}\n\nFor Bounce:\n{[F86118](proposed-bounce.gif) size=full}\n\nAn example of how this issue can break an animation is if we nest 2 easing equations, for instance a Back In followed by a Bounce Out. [easing-back-in-bounce-out.blend](easing-back-in-bounce-out.blend)\n\nI'm not sure it's applicable to all easing modes. But it should be the default behaviour for those that it's applicable. I believe an option to disable it would be useless, since its easy to control the control point handler to get the the horizontal normal. And these options are actually new, so I would not be worried about breaking backward compatibility for the previous easing curves that will change now with follow normal by default.\n\nThe most important thing about the easing equation is that they allow easy, smooth and automatic animations. So I think the change proposed here is looking to allow it in a more complete way.", "Curve draw tool: taper setting can lead to wrong handles / random tilt behavior\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.0\nWorked: never\n\nCurve draw tool: taper setting can lead to wrong handles / random tilt behavior.\n\n[#103879.blend](T103879.blend)\n- open .blend\n- draw quick roundish strokes (all should be good at this point)\n- change Taper Start to something non-zero (I set it to 0.05)\n- draw quick roundish strokes again\n- notice \"wrong\" handles\n\nIf I draw a curve like this\n{[F14175937](image.png) size=full}\n\nthen looking at to neighbors (and their handles)\n{[F14175942](image.png) size=full}\n{[F14175944](image.png) size=full}\n\nMakes me think that while the placement of the points are OK, their computed handles are wrong.\n\nTesting more, it seems this is caused by the `Taper Start` being non-zero:\n[#103879.webm](T103879.webm)\n\n**Original report**\n\nCurve Tilt seems to be broken when using tilt. It could be the configuration of the Tool that's being used and the object settings.\nThese may be changes that were added/ done to 3.2 to 3.4.1. Honestly, I have no idea, that's why i am here.\n\n- What I expected to happen? *Draw with the draw tool and the stroke face the viewport so I can see the thickness of the strokes*\n- What happens instead? *Stroke draws randomly miss-aligned to the view randomly giving the appearance of not drawing the stroke*\n- Why's that bad? *Because the user is forced to correct Blenders miscalculation.* \n\nThe objective is to have the 3D curve face front view without any tilt of the points when drawing using the \"Draw Tool\" in edit mode\". Zup method works best for this in the object settings in 3.2.\n\n1. Create is 3D curve \n**Curve Settings:**\n\n\n2. Edit curve delete point.\n\n3. Front view.\n\n4. Select the drawing tool.\n**Drawing Tool Settings:**\n\n\n5. Draw freely in any direction \n6. 3.2 should be no twisting happening with the tilt of the curve. 3.3 twist method is happening twisting is an issue on every setting when using the draw tool. The twisting happens when using the drawing capability. sometimes giving the impression the stroke is not drawing at all\n\nThings to pay attention to working between the tool and the object.\n1. Pen pressure setting on and off.\n2. The twist method seems more consistent in 3.2 working with the current tool settings. Changing this setting of corrected tilt issues that was thought previously to be 3.2 of the Twist (Curve Tilt) method of the object.\n3. in the Tool settings.\n4. The scale of the stroke when drawing.\n5. When there is a floating window the stroke misbehaves in really extreme ways.\n6. Having the stroke in a poly setting mode help the stroke behavior become more consistent\n7. Setting the stroke to bezier can be really unpredictable\n\nFinally, I am going to share this file around with a few communities to see if someone knows why this problem keeps coming up\n\n**Blend File:**\n[Curve Title Broken.blend](Curve_Title_Broken.blend)\n\n**Demo:****Audio is available** in this file. At around **2 minutes 40 seconds**, you can see the random tilt happen. It looks like i draw a stroke and nothing happens. I then rotate the camera and switch mode to **Z Up to show that it doesn't fix the twist**. This behavior seems to happen from any view. Top, bottom, left, right it doesn't matter.\n[Tilt Issue.m4v](Tilt_Issue.m4v)\n\n", "Zero sized normals if the object scale to zero in one axis. \nOperating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 555X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5\n\nBroken: version: 2.82 (sub 7)\n\nA 3D object with a reflective texture turns black when flattened by scaling x0 along an axis\n\n~\n\nI was rendering a transform of a reflective hemisphere from concave to convex, seeing how the reflection changes over time.\n\n- With Cycles, this works as expected. Concave is warped one way, flat is a flat mirror, convex is warped the other way.\n- With Eevee, the concave and convex reflections are fine, but for one frame where the hemisphere has become a 2D circle, it shows up black.\n\nExample file attached, saved at the half-way point in the animation where this bug occurs: [spoon.blend](spoon.blend)\n\nVideos attached to show the effect just in case this is hardware-specific and only happens on my laptop.\n\nEevee, with one black frame right in the middle:\n[spoon-eevee0001-0120.webm](spoon-eevee0001-0120.webm)\n\nCycles, everything is fine:\n[spoon-cycles0001-0120.webm](spoon-cycles0001-0120.webm)" ]

[ "Clear Transform in pose mode resets bendy bones settings\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\n\nBroken: version: 2.80 (sub 75)\n\n\nThe clear all transform option in pose mode resets all bendy bone settings of the selected bones. Upon some testing, I've noticed that only \"Clear Scale\" causes this, clearing rotation and location does not change any bendy bone settings. This behavior doesn't seem intended, so I decided to report it as a bug.\n\n\n***These steps work on factory settings Blender 2.80***\n\n- Add an armature with more than one bone connected to each other\n- Under \"Obejct Data\" > \"Viewport Display\", change \"Display as\" to B-Bone (this makes the bendy bone options visible on the armature itself, for convenience sake)\n- Enter pose mode and activate \"Bendy Bones\" by adding extra segments\n- Change any value under the Bendy Bones settings\n- On the viewport header, click Pose > Clear Transform > All \n\n\nThis should reset all settings of bendy bones back to their defaults, except for the inherit roll checkbox and the number of segments itself. I did a quick test on a 2.81 development version and it is still works\n", "In Pose Mode, clearing a bones Scale Transform also clears that bone's Bendy Bone Ease in/out values and also Scale in/out values\nOperating system: Win10 Pro\nGraphics card: Nvidia 1080 GTX Ti\nRAM: 16Gb\n\nblender2.7, commit date: 2019-05-04 13:12, hash: d83a72ec104c\n\nIn Pose Mode, when clearing any bones' Scale Transform, via shortcut Alt-S that bones' Bendy Bones' properties of Scale and Easing are reset to 1.0 and 0.0 respectively.\nThis makes it hard to reset the whole armature easily, as each individual Bendy Bones' scale values X Y and Z have to be set to scale of 1 individually.\n\nThe bone doesn't even have to have more than 1 segment.\nIn any bone's Bendy Bones property set Scale In/Out values to anything other than the default 1.\nSet Easing In/Out values to anything other than the default 0.0.\nIn 3D view press Alt-S.\nThe values will revert to default after a short delay.\n" ]

[ "Clicking \"Bake All Dynamics\" causing various crashes.\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 536.99\n\nBroken: version: 3.6.2\n\nUsing \"Bake All Dynamics\" is beyond finicky and crashes Blender in many different use cases. Many little \"tricks\" are needed to make it work. I am using Disk Cache for all below situations, but I believe the crashes happen with or without this.\n\nSituations where it crashes:\nClicking \"Bake All Dynamics\" within the Cloth cache settings. It seems it's required to click \"Bake All Dynamics\" button within the context of the Rigid Body system, or else it crashes instantly.\n\nClicking \"Bake All Dynamics\" in the context of hair dynamics seems to do nothing. Same goes for \"Update All to Frame\"\n\nIf a rigid body simulation has been baked, clicking \"Delete All Bakes\", then clicking \"Bake All Dynamics\" immediately will also crash blender. The only workaround for this is to \"move\" an object even if using a zero value, before clicking \"Bake All Dynamics\" again. This prevents the crash. \n\n\nCreate a Rigid Body Sim, create a Cloth Sim. Check \"Disk Cache\" as an option. Try the various methods listed above.\n\n", "crash freeze with ellie_animation.blend file\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.23\n\nBroken: version: 3.2.0\nv3.0.1 also broken for this file\n\nwhen opening the demo file ellie_animation.blend the Blender crash freezes with spinning beachball.\n\nopen the demo file ellie_animation.blend \nBlender has spinning beachball\nmacOS Activity Monitor built-in utility shows Blender (Not responding). \nI have to force quit blender.\n\nother blender files I have work ok. other blender demo files work ok.", "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", "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", "blender's UI repeatedly freezes when editing a material while the material settings are open.\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.11\n\nBroken: version: 2.93.2 Release Candidate\n\nWhen I load any .blend file containing at least 1 material that has image texture maps assigned to it, and I open the material settings, blender's UI will freeze for a while when I change any value or property related to said material, either in the shader editor or the material settings. \n\nThe whole process will repeat whenever you change any value/property in the materials settings or shader editor. The time it freezes depends on what formats and resolutions the textures are. In the below example with 16k textures, it should freeze for about 10 seconds on a fast computer, but if you replace the textures with 8 or 16k PNGs (which are available from the same site where the blend is hosted), the freeze time increases significantly: 120 seconds or more. \n\nThe only way to get it to stop repeatedly freezing is to close the material settings. \nIt will keep happening in render preview or in solid mode, it also happens regardless of whether the material preview in the material properties is enabled or disabled. \n\nThis also happens with 8k and 4k textures, but it's less noticeable.\n\n\n1. download and open clay_floor_001.blend\n2. select the sphere.\n3. open the material settings.\n4. change any property or value in the material properties or in the shader editor\n5. wait for a moment and blender's UI should freeze completely for 10-25 seconds. \n6. after it unfreezes, change any value/property in the materials properties or shader editor again, and the process should repeat.\n\ndownload the blend hosted here: clay_floor_001\nNote: you can also download png versions of the textures for this blend by clicking the little menu button to the top right of the site.\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 procedural crashes Blender when trying to render\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 3.2.0 Alpha\n\nRender procedural crashes Blender when trying to render\n\nLoad the attached alembic in the file, go Cycles experimental, turn on Use Render Engine Procedural and render.\n\n[Particles_BlastV_v01.abc.zip](Particles_BlastV_v01.abc.zip)\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)", "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.", "bpy.ops.constraint.apply crashes when owner='BONE' and in object mode\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 516.94\n\nBroken: version: 3.4.1\nWorked: unknown\n\nThe bpy.ops.constraint.apply operator crashes blender when targeting a bone constraint while in object mode. The attached blender file reliably causes the crash. It also seems to crash in pose mode at times, but I've so far been unable to recreate this in a small example file. See also [#97640](T97640) where a crash relating to the operator being used on objects has seemingly been fixed between 3.1.2 and 3.2\n\nto recreate simply open the blender file and run the script.\n[apply_bone_constraint_crash.blend](apply_bone_constraint_crash.blend)\n[apply_bone_constraint_crash.crash.txt](apply_bone_constraint_crash.crash.txt)\n\n", "Blender Crashing When Painting Stroke into a \"Moving Animated Character\" (heap-use-after-free)\nBroken: 4.0 alpha\nBroken: version: 2.79 - 2.82 (sub 7)\nWorked: Never\n\nI have this experiment of making LIVE talking head, via OSC. And I noticed that if I tried painting a stroke on a talking moving animated head, it will crash. Even with timeline not running.\n\nI got a video (Might need iPhone X with MOM addon to test this....) :\njhHdG6ZXFDU\n\n- Open attached file\n- Run animation\n- Paint over the animated object\n[paint_animated_shapekey_bug.blend](paint_animated_shapekey_bug.blend)\n\n\n", "Regression: Mesh render artifacts\nOperating system: Windows 10\nGraphics card: GTX 1070 TI\n\nBroken: 3.1, 3.6\nWorked: (3.0.1)\n\nNormals on hair mesh is corrupted in newer versions of blender while being perfect in older ones.\nMesh name is LOD0_1_front_hair_omote597.\n\n- Open the attached .blend file\n- View the model/mesh in normals/ambient occlusion render pass (cycles)\n\n", "Blender randomly crash without reason in 'glDrawElementsInstancedBaseVertex' (in 'OVERLAY_wireframe_draw' or 'workbench_draw_sample')\n|Operating system:|macOS-10.14.6-x86_64-i386-64bit 64 Bits|@MaciejSobolewski\n| -- | -- | -- |\n||macOS Big Sur 11.1 2.4 GHz 8-Core Intel Core i9 64 GB 2667 MHz DDR4|@RonMartin\n||Darwin-18.7.0-x86_64-i386-64bit 64 Bits|@aayerbe\n||Darwin-20.3.0-x86_64-i386-64bit 64 Bits|@Chyiik\n||Mac OS X 10.14.6 (18G7016)|@sahrul\n||macOS 11.2.3 (20D91)|@fahr\n||macOS-10.14.6-x86_64-i386-64bit 64 Bits|@didi404\n---\n|Graphics card:|AMD Radeon Pro 460 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.23|@MaciejSobolewski\n| -- | -- | -- |\n||Intel UHD Graphics 630 1536 MB|@RonMartin\n||Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-12.10.25|@aayerbe\n||AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15|@Chyiik\n||Intel Iris Plus Graphics 640|@sahrul\n||AMD FirePro [D700](D700)|@fahr\n||AMD Radeon Pro 570X|@didi404\n\nBroken: 2.91, 2.92, 2.93.0 Alpha, commit date: 2021-04-01 21:49\nWorked: 2.81, 2.90\n\nBlender crashes randomly on Mac OS\nIt can crash randomly after startup even if we do nothing like this example.\n\nIt has also been reported that it happens often when try to save the file after several minutes of work (#86565).\n\nCrash Log 1:\n```lines=25\nProcess: Blender [6485]\nPath: /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\nIdentifier: Blender\nVersion: 2.93.0 (2.93.0 2021-04-01)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [6485]\nUser ID: 501\n\nDate/Time: 2021-04-03 13:43:19.501 +0200\nOS Version: Mac OS X 10.14.6 (18G8022)\nReport Version: 12\nBridge OS Version: 3.0 (14Y906)\nAnonymous UUID: 5527B0F5-C330-CDA4-B73E-9CB133041D4E\n\nSleep/Wake UUID: DBADD923-7C0B-4D5E-AEFC-935ECD0B12BA\n\nTime Awake Since Boot: 850000 seconds\nTime Since Wake: 1600 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000e2c\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [6485]\n\nVM Regions Near 0xe2c:\n--> \n __TEXT 000000010cad1000-0000000118885000 [189.7M] r-x/r-x SM=COW /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff3cfe28b5 gleRunVertexSubmitImmediate + 6085\n1 GLEngine \t0x00007fff3cf4c29c glDrawElementsInstancedBaseVertex_GL3Exec + 681\n2 libGL.dylib \t0x00007fff3c2fcd02 glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x000000010d27bf05 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010d27b68c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x000000010d27afdf DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x000000010d2d2819 OVERLAY_wireframe_draw + 41\n7 org.blenderfoundation.blender \t0x000000010d2c2499 OVERLAY_draw_scene + 393\n8 org.blenderfoundation.blender \t0x000000010d2724fa drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x000000010d274643 drw_draw_depth_loop_impl + 1299\n10 org.blenderfoundation.blender \t0x000000010db9670f ED_view3d_depth_override + 239\n11 org.blenderfoundation.blender \t0x000000010dbbe460 ED_view3d_autodist + 48\n12 org.blenderfoundation.blender \t0x000000010db9dc9a ED_view3d_cursor3d_position + 234\n13 org.blenderfoundation.blender \t0x000000010db9dd80 ED_view3d_cursor3d_position_rotation + 144\n14 org.blenderfoundation.blender \t0x000000010db9e417 ED_view3d_cursor3d_update + 279\n15 org.blenderfoundation.blender \t0x000000010db9e7f1 view3d_cursor3d_invoke + 145\n16 org.blenderfoundation.blender \t0x000000010d152629 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x000000010d153bd8 wm_handler_operator_call + 648\n18 org.blenderfoundation.blender \t0x000000010d1531c4 wm_handlers_do_intern + 1588\n19 org.blenderfoundation.blender \t0x000000010d14ec16 wm_handlers_do + 774\n20 org.blenderfoundation.blender \t0x000000010d14e2de wm_event_do_handlers + 2862\n21 org.blenderfoundation.blender \t0x000000010d146b80 WM_main + 32\n22 org.blenderfoundation.blender \t0x000000010cc3691b main + 907\n23 libdyld.dylib \t0x00007fff5f1f93d5 start + 1\n\n(...)\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000e2c rbx: 0x0000000000000011 rcx: 0x00007fff3cfe28b5 rdx: 0x00007fff3cfe3ec8\n rdi: 0x0000000000000004 rsi: 0x0000000000c00000 rbp: 0x00007ffee312d230 rsp: 0x00007ffee312d090\n r8: 0x0000000000000211 r9: 0x00006000055d9f50 r10: 0x000000000000108c r11: 0x0000000000000001\n r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000108c00049800\n rip: 0x00007fff3cfe28b5 rfl: 0x0000000000010213 cr2: 0x0000000000000e2c\n \nLogical CPU: 4\nError Code: 0x00000004\nTrap Number: 14\n\n\nBinary Images:\n 0x10cad1000 - 0x118884fdf +org.blenderfoundation.blender (2.93.0 - 2.93.0 2021-04-01) <76DA024A-23A9-360A-9B4D-17E1FFF3C70F> /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n 0x11f240000 - 0x11f2acffb +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender 2.93/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x11f81a000 - 0x11f9affff com.apple.audio.units.Components (1.14 - 1.14) <D7C7C00C-202E-3F6B-A395-129A1A69A233> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x121431000 - 0x121435ffb com.apple.audio.AppleHDAHALPlugIn (282.54 - 282.54) <207D25F0-B094-3569-AA6D-09B4EDD72861> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x123231000 - 0x123234ff7 +_opcode.cpython-39-darwin.so (0) <B301C79A-62B7-387B-8FF2-1AA125557218> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_opcode.cpython-39-darwin.so\n 0x123241000 - 0x12325eff3 +libRprSupport64.dylib (0) <E10A8DBC-2DAE-3C5D-A670-E95122180BDF> /Users/USER/Library/Application Support/Blender/*/libRprSupport64.dylib\n 0x123a67000 - 0x123a6affb +_lsprof.cpython-39-darwin.so (0) <390A27D2-FE66-3D62-9D0D-EC24BDD4185E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lsprof.cpython-39-darwin.so\n 0x123c6f000 - 0x123c72047 libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib\n 0x124d05000 - 0x124dceff7 com.apple.AMDRadeonX4000GLDriver (2.11.23 - 2.1.1) <C9BBA305-1222-3D05-A096-DF3485CAA6D1> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver\n 0x12a338000 - 0x12a4eaffb +libRadeonProRender64.dylib (0) <7857C60D-5962-34B2-9946-AA62FB25A0FC> /Users/USER/Library/Application Support/Blender/*/libRadeonProRender64.dylib\n 0x12b156000 - 0x12b159fff +_heapq.cpython-39-darwin.so (0) <39FBF3FE-B287-3DE1-9C22-E65F7DE3FBD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_heapq.cpython-39-darwin.so\n 0x12b32f000 - 0x12b33aff3 +math.cpython-39-darwin.so (0) <B182812A-68AA-35BD-A8E8-D26E6BDB8C3F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/math.cpython-39-darwin.so\n 0x12b4cf000 - 0x12b53970f dyld (655.1.1) <EA5BF483-08FB-31C9-B31E-C0D0FD94FE89> /usr/lib/dyld\n 0x12c854000 - 0x12cb0b80f +_ssl.cpython-39-darwin.so (0) <9E0B733D-CC78-37AF-9E27-8D058929365F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ssl.cpython-39-darwin.so\n 0x12cbdc000 - 0x12cbebff7 +_socket.cpython-39-darwin.so (0) <B1F1427E-EC5E-35BF-8595-3AB7F81B8BFA> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_socket.cpython-39-darwin.so\n 0x12cc3c000 - 0x12cc43fff +select.cpython-39-darwin.so (0) <9F931F33-6B72-314B-9365-C443F0E411CE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/select.cpython-39-darwin.so\n 0x12cc50000 - 0x12cc57fff +array.cpython-39-darwin.so (0) <C6EAB41B-E104-3EF6-923E-5279F64BB2AE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/array.cpython-39-darwin.so\n 0x12cc68000 - 0x12cc6fff7 +_struct.cpython-39-darwin.so (0) <80252227-C14A-3C4F-974E-3F540EDA92B5> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_struct.cpython-39-darwin.so\n 0x12cc80000 - 0x12cc87ff7 +binascii.cpython-39-darwin.so (0) <804000F0-C103-3525-88BB-176B163AC5A4> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so\n 0x12cd14000 - 0x12cd17fff +_bisect.cpython-39-darwin.so (0) <C55FDD46-701F-3112-80AC-1514BA077D76> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bisect.cpython-39-darwin.so\n 0x12cd24000 - 0x12cd27ff3 +_random.cpython-39-darwin.so (0) <17F6835A-5316-353E-89E2-28FA2C7310B6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_random.cpython-39-darwin.so\n 0x12cd34000 - 0x12cd3bff3 +_sha512.cpython-39-darwin.so (0) <FE9A114B-3EB9-331D-9CB2-3F71DA53B2FB> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_sha512.cpython-39-darwin.so\n 0x12cd88000 - 0x12cd97ff7 +_datetime.cpython-39-darwin.so (0) <DD77ED03-5D10-32E9-A860-DEBFE5951394> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_datetime.cpython-39-darwin.so\n 0x12ce6c000 - 0x12d08b0f7 +_hashlib.cpython-39-darwin.so (0) <4EADD130-4A3F-3A9C-BFD5-5226CC3B80BC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_hashlib.cpython-39-darwin.so\n 0x12d12c000 - 0x12d133ff3 +_blake2.cpython-39-darwin.so (0) <47823C31-458F-31C3-939B-3E51CAFB21E9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_blake2.cpython-39-darwin.so\n 0x12d140000 - 0x12d143fff +_queue.cpython-39-darwin.so (0) <B6BD974A-932F-3126-8B07-332D5C1005B1> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_queue.cpython-39-darwin.so\n 0x12d150000 - 0x12d167ff3 +zlib.cpython-39-darwin.so (0) <1357BDA0-EBFF-328F-8CF8-2BAAF0777C3E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/zlib.cpython-39-darwin.so\n 0x12d2d6000 - 0x12d2edff3 +_bz2.cpython-39-darwin.so (0) <F5BE8D18-E1D6-3C23-B906-AB09DBF0FFBF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bz2.cpython-39-darwin.so\n 0x12d2fa000 - 0x12d329ff3 +_lzma.cpython-39-darwin.so (0) <6D9DCFA1-0480-302F-8AD2-8B32FD3377EE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lzma.cpython-39-darwin.so\n 0x12d33a000 - 0x12d33dff7 +grp.cpython-39-darwin.so (0) <DCF6B520-1F6E-3ADF-B061-CE405DC2CB4B> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/grp.cpython-39-darwin.so\n 0x12d3d9000 - 0x12d3e0fff +_json.cpython-39-darwin.so (0) <ACB3C18C-E080-3C95-8420-DAE93E2D5E99> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_json.cpython-39-darwin.so\n 0x12d43f000 - 0x12d442ffb +_scproxy.cpython-39-darwin.so (0) <50CE8674-D618-32A2-9E79-A89350AE9BA9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_scproxy.cpython-39-darwin.so\n 0x12d48f000 - 0x12d59aff7 +unicodedata.cpython-39-darwin.so (0) <B1C10C25-AADB-3554-8EA4-2D8EDBA913C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/unicodedata.cpython-39-darwin.so\n 0x12d6cd000 - 0x12d710ff7 +_decimal.cpython-39-darwin.so (0) <DB2C2DBC-0CAC-396C-9DC6-F473D0ED9DD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_decimal.cpython-39-darwin.so\n 0x12d731000 - 0x12d734ffb +_statistics.cpython-39-darwin.so (0) <1FC5B98C-DFF6-34A6-B0BB-817D49440624> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_statistics.cpython-39-darwin.so\n 0x12d881000 - 0x12d884ff3 +_posixsubprocess.cpython-39-darwin.so (0) <A047F4C3-E223-3AAB-9298-1E5E46906ADD> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_posixsubprocess.cpython-39-darwin.so\n 0x12db66000 - 0x12dedbfe7 +_multiarray_umath.cpython-39-darwin.so (0) <495E23F2-DD86-34BE-85F2-D8B8FA1CFDFE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so\n 0x12e003000 - 0x131baab4f +libopenblas.0.dylib (0) <03CB01A7-1E7B-3A87-B36F-CD619D546D98> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libopenblas.0.dylib\n 0x131e47000 - 0x131f5eff7 +libgfortran.3.dylib (0) <9ABE5EDE-AD43-391A-9E54-866711FAC32A> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgfortran.3.dylib\n 0x131fcd000 - 0x132003fff +libquadmath.0.dylib (0) <7FFA409F-FB04-3B64-BE9A-3E3A494C975E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libquadmath.0.dylib\n 0x132017000 - 0x13202cff7 +libgcc_s.1.dylib (0) <7C6D7CB7-82DB-3290-8181-07646FEA1F80> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgcc_s.1.dylib\n 0x14a03c000 - 0x14a053ffb +_pickle.cpython-39-darwin.so (0) <3559C80E-CFDA-3F33-B6ED-B469333FB0C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_pickle.cpython-39-darwin.so\n 0x14a0b2000 - 0x14a0bfff7 +_multiarray_tests.cpython-39-darwin.so (0) <AE0DCAB5-64AB-3F7D-B12A-60B9B9E919FF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_tests.cpython-39-darwin.so\n 0x14a116000 - 0x14a131f4f +_ctypes.cpython-39-darwin.so (0) <61595129-0907-3B76-BAD5-E83E12232E92> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ctypes.cpython-39-darwin.so\n 0x14a1ce000 - 0x14a1cfffb +lapack_lite.cpython-39-darwin.so (0) <ED8E8882-7728-3AFC-B16E-AD65D26C95CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/lapack_lite.cpython-39-darwin.so\n 0x14a1d7000 - 0x14a1f0ffb +_umath_linalg.cpython-39-darwin.so (0) <C031BBC1-676E-3561-971A-817DB290B4CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/_umath_linalg.cpython-39-darwin.so\n 0x14a2c4000 - 0x14a2d5fff +_pocketfft_internal.cpython-39-darwin.so (0) <F874775F-892F-3E6D-AB44-13585A46F440> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/fft/_pocketfft_internal.cpython-39-darwin.so\n 0x14a31e000 - 0x14a38ffff +mtrand.cpython-39-darwin.so (0) <26C3326C-CD5C-3EB6-ADC1-1501DEFF4824> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/mtrand.cpython-39-darwin.so\n 0x14a3ea000 - 0x14a408ffb +bit_generator.cpython-39-darwin.so (0) <0AA58188-F7BE-3259-B73D-F73A44D18892> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/bit_generator.cpython-39-darwin.so\n 0x14a429000 - 0x14a45eff3 +_common.cpython-39-darwin.so (0) <A5274DC2-1EDF-3596-810F-949AFC3280AF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_common.cpython-39-darwin.so\n 0x14a47b000 - 0x14a4d1ffb +_bounded_integers.cpython-39-darwin.so (0) <C5EA861D-2A70-3753-B812-574045E67644> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_bounded_integers.cpython-39-darwin.so\n 0x14a4f8000 - 0x14a506ffb +_mt19937.cpython-39-darwin.so (0) <317BAC67-09BA-3FCD-951A-1F8665EB2AB2> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_mt19937.cpython-39-darwin.so\n 0x14a517000 - 0x14a523ff3 +_philox.cpython-39-darwin.so (0) <E0D66351-2EA3-3CAC-92B8-9BDD75A35465> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_philox.cpython-39-darwin.so\n 0x14a533000 - 0x14a53dff7 +_pcg64.cpython-39-darwin.so (0) <97A10DFD-6916-3251-84B1-FCCF8D908E08> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_pcg64.cpython-39-darwin.so\n 0x14a54c000 - 0x14a553fff +_sfc64.cpython-39-darwin.so (0) <4A390EEB-7105-3235-85B2-4C8D98B3587C> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_sfc64.cpython-39-darwin.so\n 0x14a560000 - 0x14a5e6ffb +_generator.cpython-39-darwin.so (0) <D25A4A84-E711-357E-9925-2B76BD03BAB0> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_generator.cpython-39-darwin.so\n 0x152b16000 - 0x152b9aff7 +core.so (0) <90E3783C-EA48-3E8D-98E7-E2465548F8C7> /Users/USER/*/core.so\n 0x152e28000 - 0x152e2fff7 +_csv.cpython-39-darwin.so (0) <A88064E5-CC97-3CD9-9422-3148889BB740> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_csv.cpython-39-darwin.so\n 0x7fff27936000 - 0x7fff27c8ffff com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <AB6E8A8F-0BFE-37EE-A135-44ABA4FCB559> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff27c92000 - 0x7fff27d9efff com.apple.AMDMTLBronzeDriver (2.11.23 - 2.1.1) <69902D3A-0267-3D14-9820-D65016305FCC> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver\n 0x7fff27d9f000 - 0x7fff28744ff3 ATIRadeonX4000SCLib.dylib (2.11.23) <CC649A6F-573C-30F6-AC1B-8F0850D85B87> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib\n 0x7fff2caac000 - 0x7fff2d880ff7 com.apple.driver.AppleIntelSKLGraphicsGLDriver (12.10.25 - 12.1.0) <9AE3588C-F533-3A5D-9E4B-602ACEA5493C> /System/Library/Extensions/AppleIntelSKLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsGLDriver\n 0x7fff2d881000 - 0x7fff2dbb2ff7 com.apple.driver.AppleIntelSKLGraphicsMTLDriver (12.10.25 - 12.1.0) <8889F99C-A463-3299-8DE8-ED06FF6A6735> /System/Library/Extensions/AppleIntelSKLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsMTLDriver\n 0x7fff2f5b8000 - 0x7fff2f5b8fff com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff2f5b9000 - 0x7fff2f5cfff7 libCGInterfaces.dylib (506.22) <1B6C92D9-F4B8-37BA-9635-94C4A56098CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff2f5d0000 - 0x7fff2fc69fef com.apple.vImage (8.1 - ???) <53FA3611-894E-3158-A654-FBD2F70998FE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff2fc6a000 - 0x7fff2fee3ff3 libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff2fee4000 - 0x7fff2ff56ffb libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff2ff57000 - 0x7fff30300ff3 libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff30301000 - 0x7fff30316feb libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff30317000 - 0x7fff3031cff3 libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff3031d000 - 0x7fff30399ff3 libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff3039a000 - 0x7fff303adfe3 libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff303ae000 - 0x7fff30595ff7 libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff30596000 - 0x7fff30649ff7 libvMisc.dylib (671.250.4) <D5BA4812-BFFC-3CD0-B382-905CD8555DA6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff3064a000 - 0x7fff3064afff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff307ec000 - 0x7fff315a1ffb com.apple.AppKit (6.9 - 1671.60.109) <F3BB6BCD-F2DF-36E7-8F20-FEC419671841> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff315f3000 - 0x7fff315f3fff com.apple.ApplicationServices (50.1 - 50.1) <7BDB78C7-9021-3B29-823A-1FFDB9F79602> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff315f4000 - 0x7fff3165ffff com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff316f8000 - 0x7fff3180fff7 libFontParser.dylib (228.6.2.10) <B0B7AF1F-2342-3A95-A7E6-629FC032D4B1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib\n 0x7fff31810000 - 0x7fff31852fff libFontRegistry.dylib (228.12.2.4) <6DDE44EC-FF6B-3893-9209-45E0955ABDD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff318ac000 - 0x7fff318defff libTrueTypeScaler.dylib (228.6.2.10) <5FE48A9A-8329-3B0D-9A99-DEAC708F8334> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib\n 0x7fff31943000 - 0x7fff31947ff3 com.apple.ColorSyncLegacy (4.13.0 - 1) <E8E9342C-47EB-359D-A373-554AC19B174A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff319e2000 - 0x7fff31a34ff7 com.apple.HIServices (1.22 - 628) <2BE461FF-80B9-30D3-A574-AED5724B1C1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff31a35000 - 0x7fff31a44fff com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff31a45000 - 0x7fff31a8eff7 com.apple.print.framework.PrintCore (14.7 - 503.8) <E1D0FCBC-155E-372E-A90F-4A20B94FC114> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff31a8f000 - 0x7fff31ac8ff7 com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff31ac9000 - 0x7fff31ad5fff com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <5E7B9BD4-122B-3012-A044-3259C97E7509> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff31ad6000 - 0x7fff31d4dfff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <32487CB2-246B-3B80-8F60-D65DFC367DDC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff31d4f000 - 0x7fff31d4ffff com.apple.audio.units.AudioUnit (1.14 - 1.14) <B489CFDA-DEF3-38F5-A815-23EC30B8DA03> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff320a8000 - 0x7fff3244afff com.apple.CFNetwork (978.5 - 978.5) <06BB192E-0302-3AE9-B229-A9B15AD4CBF4> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff3245f000 - 0x7fff3245ffff com.apple.Carbon (158 - 158) <B955D7C0-ACA6-33EB-9527-1598288532A6> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff32460000 - 0x7fff32463ffb com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff32464000 - 0x7fff3275bfff com.apple.HIToolbox (2.1.1 - 918.7) <88D7F19C-8C9D-384B-BAB5-8205CA282F2C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff3275c000 - 0x7fff3275fff3 com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32760000 - 0x7fff32765ff7 com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff32766000 - 0x7fff327fbff3 com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff327fc000 - 0x7fff32814ff7 com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff32834000 - 0x7fff32835ff7 com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff32836000 - 0x7fff32838ff7 com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff32839000 - 0x7fff3283fff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff32961000 - 0x7fff32961fff com.apple.Cocoa (6.11 - 23) <987A526D-6FD8-345E-9265-4D8067B337D1> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff3296f000 - 0x7fff32abeff7 com.apple.ColorSync (4.13.0 - 3345.6) <356BA478-76DE-3087-86BE-5E884276AB83> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff32c4a000 - 0x7fff32cd0fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <E6E4A58D-9BAE-30B1-856E-E1332B98E9ED> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff32d34000 - 0x7fff32d5effb com.apple.CoreBluetooth (1.0 - 1) <4F2DDEF0-1F92-384B-8CDA-4958725D0A8E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff32d5f000 - 0x7fff330e4fef com.apple.CoreData (120 - 866.6) <132CB39B-8D58-30FA-B8AD-49BFFF34B293> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff330e5000 - 0x7fff331d5ff7 com.apple.CoreDisplay (101.3 - 110.18) <6DD41271-E145-3E99-9D49-7CC8AC1C65B6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff331d6000 - 0x7fff3361bfff com.apple.CoreFoundation (6.9 - 1575.401) <4D6EA727-F7B9-398A-9B0B-4A30802E49BD> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff3361d000 - 0x7fff33cadfe7 com.apple.CoreGraphics (2.0 - 1265.11) <71E7056D-6AA5-324A-A5B8-9CD35772D87B> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff33caf000 - 0x7fff33fcffff com.apple.CoreImage (14.4.0 - 750.0.140) <11026E39-D2FF-3CF6-8ACE-7BA293F9853E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff342cc000 - 0x7fff343d0fff com.apple.CoreMedia (1.0 - 2290.14) <2C7A5348-7F19-3E28-97E4-6065A64B1DC9> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff3442d000 - 0x7fff3442dfff com.apple.CoreServices (946 - 946) <8423F2AB-74CB-3BBD-A66E-ED93DE2363C2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3442e000 - 0x7fff344aaff7 com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff344ab000 - 0x7fff34782fff com.apple.CoreServices.CarbonCore (1178.33 - 1178.33) <CB87F0C7-2CD6-3983-8E32-B6A2EC925352> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff34783000 - 0x7fff347cbff7 com.apple.DictionaryServices (1.2 - 284.16.4) <746EB200-DC51-30AE-9CBC-608A7B4CC8DA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff347cc000 - 0x7fff347d4ffb com.apple.CoreServices.FSEvents (1239.200.13 - 1239.200.13) <5913F08D-4AA2-3200-B998-012E6A19A66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff347d5000 - 0x7fff34986ff7 com.apple.LaunchServices (946 - 946) <A0C91634-9410-38E8-BC11-7A5A369E6BA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff34987000 - 0x7fff34a25ff7 com.apple.Metadata (10.7.0 - 1191.58) <89DA10B4-5695-3FD9-A920-C34C33957868> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff34a26000 - 0x7fff34a70ff7 com.apple.CoreServices.OSServices (946 - 946) <20C4EEF8-D5AC-39A0-9B4A-78F88E3EFBCC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff34a71000 - 0x7fff34ad8ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff34ad9000 - 0x7fff34afaff3 com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff34e05000 - 0x7fff34f67ff7 com.apple.CoreText (352.0 - 584.26.3.6) <47B18B6F-C53C-357A-8EBA-A2CD340018E6> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff34f68000 - 0x7fff34fa8ff3 com.apple.CoreVideo (1.8 - 281.4) <10CF8E52-07E3-382B-8091-2CEEEFFA69B4> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff34fa9000 - 0x7fff35038fff com.apple.framework.CoreWLAN (13.0 - 1375.2) <A476486C-B863-3941-BAE6-A78BDFED4A3B> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff3528f000 - 0x7fff35294ffb com.apple.DiskArbitration (2.7 - 2.7) <A31C207C-8255-3E93-9DD7-D80C4B179050> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff35458000 - 0x7fff3545aff3 com.apple.ForceFeedback (1.0.6 - 1.0.6) <205B0C3E-4E8D-3347-A993-469F06ABBFF9> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff3545b000 - 0x7fff35808ffb com.apple.Foundation (6.9 - 1575.401) <546CCD67-0069-369A-8E6A-37FB5DD64AA1> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff35877000 - 0x7fff358a6ffb com.apple.GSS (4.0 - 2.0) <E2B90D08-3857-3155-9FCC-07D778988EC9> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff359a6000 - 0x7fff35ab0fff com.apple.Bluetooth (6.0.14 - 6.0.14d12) <0904E4FC-DE05-3B78-BD49-832A5AC2967D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff35b13000 - 0x7fff35ba2fff com.apple.framework.IOKit (2.0.2 - 1483.260.5) <6D560570-9AEB-3046-96B7-12AC1D145C3D> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff35ba4000 - 0x7fff35bb3ffb com.apple.IOSurface (255.6.1 - 255.6.1) <85F85EBB-EA59-3A8B-B3EB-7C20F3CC77AE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff35c07000 - 0x7fff35d94fe7 com.apple.ImageIO.framework (3.3.0 - 1850.2.11) <5F5F7C36-2A20-3CFE-ACAC-53633B0F2F0A> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff35d95000 - 0x7fff35d99ffb libGIF.dylib (1850.2.12) <060E927C-DFA7-33A7-98E3-F9699D734A8E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff35d9a000 - 0x7fff35e76ff7 libJP2.dylib (1850.2.12) <CEC4FF68-7522-3430-B03D-37648FEB450E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff35e77000 - 0x7fff35e9cfeb libJPEG.dylib (1850.2.12) <F7A6A6EC-24B6-3C45-813F-B2FFA3980B49> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff36172000 - 0x7fff36198feb libPng.dylib (1850.2.12) <B816B90B-2454-31D8-AD34-1489B6350C70> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff36199000 - 0x7fff3619bffb libRadiance.dylib (1850.2.12) <1A67ED5D-00BC-301D-8515-CEDFFE994F2B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff3619c000 - 0x7fff361e9ff3 libTIFF.dylib (1850.2.12) <3FB9D8DC-1D7B-324C-ADE6-DDC794FD2B43> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff3735c000 - 0x7fff37375fff com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff3762f000 - 0x7fff37639fff com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff376e9000 - 0x7fff37d8ffff com.apple.MediaToolbox (1.0 - 2290.14) <927F9E24-32DB-33F9-9866-4DD8092A51F4> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff37d91000 - 0x7fff37e39ff7 com.apple.Metal (162.2 - 162.2) <B65C71BF-D40E-3BB3-940C-117DDD203551> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff37e55000 - 0x7fff37e74ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <44CE8362-E972-3697-AD6F-15BC863BAEB8> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff37e75000 - 0x7fff37ef1fe7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <EE8440DA-66DF-3923-ABBC-E0543211C069> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff37ef2000 - 0x7fff37f19fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E64450DF-2B96-331E-B7F4-666E00571C70> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff37f1a000 - 0x7fff38045ff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <F2CF26B6-73F1-3644-8FE9-CDB9B2C4501F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff38046000 - 0x7fff38060fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B33A35C3-0393-366B-ACFB-F4BB6A5F7B4A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff38061000 - 0x7fff38062ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <69F14BCF-C5C5-3BF8-9C31-8F87D2D6130A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff38e66000 - 0x7fff38e72ff7 com.apple.NetFS (6.0 - 4.0) <1C8237D6-731D-3E32-8BD5-B92A33D08A30> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff391d5000 - 0x7fff391f8ff7 com.apple.audio.OpenAL (1.8 - 1.8) <2EE5236C-775B-36B1-97A8-DEE5FB80F5B5> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff3b907000 - 0x7fff3b90ffe3 libcldcpuengine.dylib (2.11) <AAE49359-EB53-3FD4-ADBF-C60498BD0B34> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff3b910000 - 0x7fff3b967ff7 com.apple.opencl (2.15.3 - 2.15.3) <2F6B796C-901C-33AF-8B12-F3522DA05218> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff3b968000 - 0x7fff3b983ff7 com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff3b984000 - 0x7fff3b98fffb com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff3c2df000 - 0x7fff3c2e1fff libCVMSPluginSupport.dylib (17.7.3) <700B3323-3404-3848-91D2-99EFC7E2634A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff3c2e2000 - 0x7fff3c2e7ff3 libCoreFSCache.dylib (166.5) <5BC99EE7-7FFD-3F30-9AEE-EEDC25067AC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff3c2e8000 - 0x7fff3c2ecfff libCoreVMClient.dylib (166.5) <B8FA5858-8185-3992-AD3B-A81AF08C3CDD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff3c2ed000 - 0x7fff3c2f5ff7 libGFXShared.dylib (17.7.3) <26BA051E-1113-3022-A46A-1F69E7CFA787> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff3c2f6000 - 0x7fff3c301fff libGL.dylib (17.7.3) <16C56C55-327F-395F-810C-C360F7DE9063> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff3c302000 - 0x7fff3c33cfef libGLImage.dylib (17.7.3) <F68F1268-5AD1-3D2E-A255-0BD442A24F4D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff3c33d000 - 0x7fff3c4afff7 libGLProgrammability.dylib (17.7.3) <92DDEDA1-5E95-36A9-9D2E-A725541B2F93> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff3c4b0000 - 0x7fff3c4eefff libGLU.dylib (17.7.3) <D83871DF-B7DD-3DFD-8D5C-0BA359AC1BF2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff3ce8b000 - 0x7fff3ce9affb com.apple.opengl (17.7.3 - 17.7.3) <62E4CB29-51CA-387E-90BF-F58213D56D62> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff3ce9b000 - 0x7fff3d032ff7 GLEngine (17.7.3) <8C9F33DD-7C81-3D45-80F7-A7D6A877993A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff3d033000 - 0x7fff3d05cff3 GLRendererFloat (17.7.3) <2B5F700E-9E9B-3543-BC35-949279CB24FF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff3dca4000 - 0x7fff3defbff7 com.apple.QuartzCore (1.11 - 701.14) <B37B1291-4977-34D2-B3F0-509FB3DB5090> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff3e733000 - 0x7fff3ea33ff7 com.apple.security (7.0 - 58286.270.10) <990FF42E-0726-318F-94ED-A8FDF7F41402> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff3ea34000 - 0x7fff3eac0fff com.apple.securityfoundation (6.0 - 55185.260.1) <964F1F81-D8F1-3952-8137-EF21CDD3A7A6> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff3eaf2000 - 0x7fff3eaf6fff com.apple.xpc.ServiceManagement (1.0 - 1) <5055F807-1DD4-3F97-A2A6-4537F51A5736> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff3ee8f000 - 0x7fff3eefcfff com.apple.SystemConfiguration (1.17 - 1.17) <30C8327F-3EFF-3520-9C50-016F8B6B954F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff3f15b000 - 0x7fff3f4bcfff com.apple.VideoToolbox (1.0 - 2290.14) <30C690CF-8935-39E8-B343-ADB009C84FC5> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff42138000 - 0x7fff421ddfff com.apple.APFS (1.0 - 1) <06284DE8-5883-39F8-B04D-0D5EA74D12ED> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff42bf2000 - 0x7fff42bf3ff7 com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff431f6000 - 0x7fff43222ff7 com.apple.framework.Apple80211 (13.0 - 1380.2) <E4D12303-8B12-303C-91E2-3B40F60832BA> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff4334a000 - 0x7fff43359fc7 com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff43455000 - 0x7fff43460fff com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff434a1000 - 0x7fff434eaff3 com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff4373e000 - 0x7fff43760fff com.apple.applesauce (1.0 - ???) <F49107C7-3C51-3024-8EF1-C57643BE4F3B> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff43824000 - 0x7fff43874ff7 com.apple.AppleVAFramework (5.1.4 - 5.1.4) <FB127E63-853B-3F00-BE2A-12B4BF6FED33> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff438bf000 - 0x7fff438d3ffb com.apple.AssertionServices (1.0 - 1) <456E507A-4561-3628-9FBE-173ACE7429D8> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff43ca2000 - 0x7fff43d8eff7 com.apple.AuthKit (1.0 - 1) <2765ABE9-54F2-3E45-8A93-1261E251B90D> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff43f50000 - 0x7fff43f58fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <2A396FC0-7B79-3088-9A82-FB93C1181A57> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff43f59000 - 0x7fff43feefff com.apple.backup.framework (1.10.7 - ???) <5243C2BC-0159-3DBB-9FAB-22EA01E58052> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff43fef000 - 0x7fff4405cff3 com.apple.BaseBoard (360.28 - 360.28) <68FA8044-F3CD-3BC6-9DAB-27DACF52BFC0> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff44ebc000 - 0x7fff44f0bff7 com.apple.ChunkingLibrary (201 - 201) <DFE16C42-24E6-386F-AC50-0058F61980A2> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff45cc9000 - 0x7fff45cd2ffb com.apple.CommonAuth (4.0 - 2.0) <93335CB6-ABEB-3EC7-A040-8A667F40D5F3> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff4616b000 - 0x7fff4654efef com.apple.CoreAUC (274.0.0 - 274.0.0) <C71F1581-E73B-3DA0-958B-E912C3FB3F23> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff4654f000 - 0x7fff4657dff7 com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <A04A99B8-DAC5-36FC-BAC7-7431600C1F89> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff469ab000 - 0x7fff469bcff7 com.apple.CoreEmoji (1.0 - 69.19.9) <228457B3-E191-356E-9A5B-3C0438D05FBA> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff46f66000 - 0x7fff46fccff7 com.apple.CoreNLP (1.0 - 130.15.22) <27877820-17D0-3B02-8557-4014E876CCC7> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff47279000 - 0x7fff47281ff7 com.apple.CorePhoneNumbers (1.0 - 1) <11F97C7E-C183-305F-8E6C-9B374F50E26B> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff473fd000 - 0x7fff4742eff3 com.apple.CoreServicesInternal (358 - 358) <DD6EF60D-048F-3186-83DA-EB191EDF48AE> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff477f5000 - 0x7fff47879fff com.apple.CoreSymbolication (10.2 - 64490.25.1) <28B2FF2D-3FDE-3A20-B343-341E5BD4E22F> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff47909000 - 0x7fff47a34ff7 com.apple.coreui (2.1 - 499.10) <A80F4B09-F940-346F-A9DF-4EFADD9220A8> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff47a35000 - 0x7fff47bd5fff com.apple.CoreUtils (5.9 - 590.16) <BF9A990D-24C0-3633-A753-F19F4DFCA663> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff47c29000 - 0x7fff47c8cff7 com.apple.framework.CoreWiFi (13.0 - 1375.2) <7E9CC352-BB06-3C97-A51F-6A35F09EBA16> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff47c8d000 - 0x7fff47c9eff3 com.apple.CrashReporterSupport (10.13 - 938.29) <8A66F5D5-87D1-31C9-BEAE-86E0735F4E92> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff47d2e000 - 0x7fff47d3dfff com.apple.framework.DFRFoundation (1.0 - 211.1) <E3F02F2A-2059-39CC-85DA-969676EB88EB> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff47d3e000 - 0x7fff47d42ff7 com.apple.DSExternalDisplay (3.1 - 380) <787B9748-B120-3453-B8FE-61D9E363A9E0> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff47dc3000 - 0x7fff47e38ffb com.apple.datadetectorscore (7.0 - 590.27) <06FB1A07-7AE6-3ADD-8E7E-41955FAB38E8> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff47e84000 - 0x7fff47ec1ff7 com.apple.DebugSymbols (190 - 190) <6F4FAACA-E06B-38AD-A0C2-14EA5408A231> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff47ec2000 - 0x7fff47ffdff7 com.apple.desktopservices (1.13.6 - ???) <7536F3F3-90F1-3D1C-9249-91B809FE5328> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff48f44000 - 0x7fff4935ffff com.apple.vision.FaceCore (3.3.4 - 3.3.4) <A576E2DA-BF6F-3B18-8FEB-324E5C5FA9BD> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff4cc13000 - 0x7fff4cc14fff libmetal_timestamp.dylib (902.3.2) <05389463-AF2E-33E2-A14F-1416E4A30835> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib\n 0x7fff4e2a8000 - 0x7fff4e2b3ff7 libGPUSupportMercury.dylib (17.7.3) <121E8765-3C03-32AB-903E-6B1DD9A4FD4A> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff4e2b4000 - 0x7fff4e2b9fff com.apple.GPUWrangler (3.50.16 - 3.50.16) <1156CF8C-729B-3173-B3CC-00BB17156BCC> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff4e647000 - 0x7fff4e66bff3 com.apple.GenerationalStorage (2.0 - 285.101) <84C2E52C-F2C6-3FF8-87E5-3C88A40D3881> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff4f0c5000 - 0x7fff4f0d4fff com.apple.GraphVisualizer (1.0 - 5) <48D020B7-5938-3FAE-B468-E291AEE2C06F> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff4f23a000 - 0x7fff4f2aeffb com.apple.Heimdal (4.0 - 2.0) <D97FCF19-EAD6-3E2F-BE88-F817E45CAE96> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff505af000 - 0x7fff505b8fff com.apple.IOAccelMemoryInfo (1.0 - 1) <32F6778F-3EB5-36A3-8AF8-55B37A44AC0C> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff505b9000 - 0x7fff505c0ffb com.apple.IOAccelerator (404.15 - 404.15) <06D2C96E-1CF5-3199-A234-9033934D78BF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff505c4000 - 0x7fff505dcfff com.apple.IOPresentment (1.0 - 42.6) <D2BA3A78-21C6-37B8-9F8F-9EC0F30F953F> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff50984000 - 0x7fff509b1ff7 com.apple.IconServices (379 - 379) <7BAD562D-4FA3-3E11-863C-1EEBE2406D2C> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff50c44000 - 0x7fff50c56ff3 com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <D5DDE47A-E922-3166-BD7F-E7C3DF360DD9> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff50c71000 - 0x7fff50d4cff7 com.apple.LanguageModeling (1.0 - 159.15.15) <3DE3CE61-542B-37B7-883E-4B9717CAC65F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff50d4d000 - 0x7fff50d89ff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <4B5E843E-2809-3E70-9560-9254E2656419> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff50d90000 - 0x7fff50d95fff com.apple.LinguisticData (1.0 - 238.25) <F529B961-098C-3E4C-A3E9-9DA9BFA1B3F0> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff515b4000 - 0x7fff515b7fff com.apple.Mangrove (1.0 - 25) <537A5B2E-4C30-3CFD-8BDC-79F9A04AC327> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff51a8b000 - 0x7fff51ab3ff7 com.apple.spotlight.metadata.utilities (1.0 - 1191.58) <23E8580B-19C0-3E4F-A9FE-368DA80EAA6F> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff51ab4000 - 0x7fff51b41ff7 com.apple.gpusw.MetalTools (1.0 - 1) <9B542958-6363-3041-A265-EC7AC7BD7A43> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff51b58000 - 0x7fff51b71ffb com.apple.MobileAssets (1.0 - 437.250.3) <8BE5B3A0-8F3A-3FAE-9AFF-32836300183C> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff51d3d000 - 0x7fff51d58ffb com.apple.MobileKeyBag (2.0 - 1.0) <39337CBB-1D39-3DDC-A998-591194C76523> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff51de1000 - 0x7fff51e0bffb com.apple.MultitouchSupport.framework (2450.1 - 2450.1) <42A23EC9-64A7-31C7-BF33-DF4412ED8A3F> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff52047000 - 0x7fff52051fff com.apple.NetAuth (6.2 - 6.2) <0D01BBE5-0269-310D-B148-D19DAE143DEB> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff528b3000 - 0x7fff52904ff3 com.apple.OTSVG (1.0 - ???) <CB2F1DBE-0313-30CB-A95F-2FE75E0A089E> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff53a9d000 - 0x7fff53aacff7 com.apple.PerformanceAnalysis (1.218.2 - 218.2) <65F3DB3E-6D4E-33A0-B510-EF768D323DAB> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff5593e000 - 0x7fff5595cff7 com.apple.ProtocolBuffer (1 - 263.2) <907D6C95-D050-31DE-99CA-16A5135BC6F9> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff55af4000 - 0x7fff55b44fff com.apple.ROCKit (27.6 - 27.6) <756C2253-E8B1-3C48-9945-DE8D6AD24DE2> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit\n 0x7fff55ca2000 - 0x7fff55cc4fff com.apple.RemoteViewServices (2.0 - 128) <8FB0E4EB-DCBB-32E6-94C6-AA9BA9EE4CAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff574ce000 - 0x7fff575ecfff com.apple.Sharing (1288.62.5 - 1288.62.5) <BB647030-839A-3271-B205-D4325346DD3B> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff58401000 - 0x7fff586b0fff com.apple.SkyLight (1.600.0 - 340.55) <1F737945-E242-3F03-A7D6-1A5955AB1298> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff58e54000 - 0x7fff58e60fff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <7A6A67DB-C813-328E-AAFB-D267A5B50B3D> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff594ff000 - 0x7fff5953bff3 com.apple.StreamingZip (1.0 - 1) <046FAD5C-E0C5-3013-B1FE-24C018A0DDCF> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff595b1000 - 0x7fff5963cfc7 com.apple.Symbolication (10.2 - 64490.38.1) <9FDCC98D-5B32-35AD-A9BF-94DF2B78507F> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff59b22000 - 0x7fff59b2effb com.apple.TCC (1.0 - 1) <E3691073-7284-35E4-94F3-16587A7F380F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff59d94000 - 0x7fff59e5cff3 com.apple.TextureIO (3.8.4 - 3.8.1) <7CEAC05A-D283-3D5A-B1E3-C849285FA0BF> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff59f12000 - 0x7fff59f13fff com.apple.TrustEvaluationAgent (2.0 - 31.200.1) <15DF9C73-54E4-3C41-BCF4-378338C55FB4> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff59f19000 - 0x7fff5a0d1ffb com.apple.UIFoundation (1.0 - 551.5) <A0FDC3A4-45C6-3C87-B77F-7DC394374C08> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff5ad4d000 - 0x7fff5ae26fff com.apple.ViewBridge (406 - 406) <3CC6AE31-2CD7-30CA-982C-47EF242EFA30> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff5b5fe000 - 0x7fff5b601fff com.apple.dt.XCTTargetBootstrap (1.0 - 14490.66) <7AE3457F-AF40-3508-93FB-1D9E31EB1C9D> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff5ba02000 - 0x7fff5ba04ffb com.apple.loginsupport (1.0 - 1) <3F8D6334-BCD6-36C1-BA20-CC8503A84375> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff5ba05000 - 0x7fff5ba1afff com.apple.login (3.0 - 3.0) <E168F05D-A5DF-3848-8686-DF5015EA4BA4> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff5bcce000 - 0x7fff5bd02fff libCRFSuite.dylib (41.15.4) <406DAC06-0C77-3F90-878B-4D38F11F0256> /usr/lib/libCRFSuite.dylib\n 0x7fff5bd05000 - 0x7fff5bd0fff7 libChineseTokenizer.dylib (28.15.3) <9B7F6109-3A5D-3641-9A7E-31D2239D73EE> /usr/lib/libChineseTokenizer.dylib\n 0x7fff5bd9d000 - 0x7fff5bd9effb libDiagnosticMessagesClient.dylib (107) <A14D0819-0970-34CD-8680-80E4D7FE8C2C> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff5bdd5000 - 0x7fff5c02cff3 libFosl_dynamic.dylib (18.3.4) <1B5DD4E2-8AE0-315E-829E-D5BFCD264EA8> /usr/lib/libFosl_dynamic.dylib\n 0x7fff5c07d000 - 0x7fff5c09cfff libMobileGestalt.dylib (645.270.1) <99A06C8A-97D6-383D-862C-F453BABB48A4> /usr/lib/libMobileGestalt.dylib\n 0x7fff5c09d000 - 0x7fff5c09dfff libOpenScriptingUtil.dylib (179.1) <4D603146-EDA5-3A74-9FF8-4F75D8BB9BC6> /usr/lib/libOpenScriptingUtil.dylib\n 0x7fff5c1dd000 - 0x7fff5c1deffb libSystem.B.dylib (1252.250.1) <C7A55258-8EB2-3202-82B5-AA56E53EE2DA> /usr/lib/libSystem.B.dylib\n 0x7fff5c25a000 - 0x7fff5c25bfff libThaiTokenizer.dylib (2.15.1) <ADB37DC3-7D9B-3E73-A72A-BCC3433C937A> /usr/lib/libThaiTokenizer.dylib\n 0x7fff5c26d000 - 0x7fff5c283ffb libapple_nghttp2.dylib (1.24.1) <6F04250A-6686-3FDC-9A8D-290C64B06502> /usr/lib/libapple_nghttp2.dylib\n 0x7fff5c284000 - 0x7fff5c2adffb libarchive.2.dylib (54.250.1) <47289946-8504-3966-9127-6CE39993DC2C> /usr/lib/libarchive.2.dylib\n 0x7fff5c2ae000 - 0x7fff5c32dfff libate.dylib (1.13.8) <92B44EDB-369D-3EE8-AEC5-61F8B9313DBF> /usr/lib/libate.dylib\n 0x7fff5c331000 - 0x7fff5c331ff3 libauto.dylib (187) <3E3780E1-96F3-3A22-91C5-92F9A5805518> /usr/lib/libauto.dylib\n 0x7fff5c403000 - 0x7fff5c413ffb libbsm.0.dylib (39.200.18) <CF381E0B-025B-364F-A83D-2527E03F1AA3> /usr/lib/libbsm.0.dylib\n 0x7fff5c414000 - 0x7fff5c421fff libbz2.1.0.dylib (38.200.3) <272953A1-8D36-329B-BDDB-E887B347710F> /usr/lib/libbz2.1.0.dylib\n 0x7fff5c422000 - 0x7fff5c475ff7 libc++.1.dylib (400.9.4) <9A60A190-6C34-339F-BB3D-AACE942009A4> /usr/lib/libc++.1.dylib\n 0x7fff5c476000 - 0x7fff5c48bff7 libc++abi.dylib (400.17) <38C09CED-9090-3719-90F3-04A2749F5428> /usr/lib/libc++abi.dylib\n 0x7fff5c48c000 - 0x7fff5c48cff3 libcharset.1.dylib (51.200.6) <2A27E064-314C-359C-93FC-8A9B06206174> /usr/lib/libcharset.1.dylib\n 0x7fff5c48d000 - 0x7fff5c49dffb libcmph.dylib (6.15.1) <9C52B2FE-179F-32AC-B87E-2AFC49ABF817> /usr/lib/libcmph.dylib\n 0x7fff5c49e000 - 0x7fff5c4b6ffb libcompression.dylib (52.250.2) <7F4BB18C-1FB4-3825-8D8B-6E6B168774C6> /usr/lib/libcompression.dylib\n 0x7fff5c72b000 - 0x7fff5c741fff libcoretls.dylib (155.220.1) <4C64BE3E-41E3-3020-8BB7-07E90C0C861C> /usr/lib/libcoretls.dylib\n 0x7fff5c742000 - 0x7fff5c743ff3 libcoretls_cfhelpers.dylib (155.220.1) <0959B3E9-6643-3589-8BB3-21D52CDF0EF1> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff5c8e1000 - 0x7fff5c9d9ff7 libcrypto.35.dylib (22.260.1) <91C3D71A-4D1D-331D-89CC-67863DF10574> /usr/lib/libcrypto.35.dylib\n 0x7fff5cbef000 - 0x7fff5cc45ff3 libcups.2.dylib (462.16) <E82021D0-36AD-3FB7-AE47-A03A6947C7D0> /usr/lib/libcups.2.dylib\n 0x7fff5cd79000 - 0x7fff5cd79fff libenergytrace.dylib (17.200.1) <80BB567A-FD18-3497-BF97-353F57D98CDD> /usr/lib/libenergytrace.dylib\n 0x7fff5cdab000 - 0x7fff5cdb0ff7 libgermantok.dylib (17.15.2) <E5F0F794-FF27-3D64-AE52-C78C6A84DD67> /usr/lib/libgermantok.dylib\n 0x7fff5cdb1000 - 0x7fff5cdb6ff7 libheimdal-asn1.dylib (520.270.1) <73F60D6F-76F8-35EF-9C86-9A81225EE4BE> /usr/lib/libheimdal-asn1.dylib\n 0x7fff5cde1000 - 0x7fff5ced1fff libiconv.2.dylib (51.200.6) <2047C9B7-3F74-3A95-810D-2ED8F0475A99> /usr/lib/libiconv.2.dylib\n 0x7fff5ced2000 - 0x7fff5d133ffb libicucore.A.dylib (62141.0.1) <A0D63918-76E9-3C1B-B255-46F4C1DA7FE8> /usr/lib/libicucore.A.dylib\n 0x7fff5d180000 - 0x7fff5d181fff liblangid.dylib (128.15.1) <22D05C4F-769B-3075-ABCF-44A0EBACE028> /usr/lib/liblangid.dylib\n 0x7fff5d182000 - 0x7fff5d19aff3 liblzma.5.dylib (10.200.3) <E1F4FD60-1CE4-37B9-AD95-29D348AF1AC0> /usr/lib/liblzma.5.dylib\n 0x7fff5d1b2000 - 0x7fff5d256ff7 libmecab.1.0.0.dylib (779.24.1) <A8D0379B-85FA-3B3D-89ED-5CF2C3826AB2> /usr/lib/libmecab.1.0.0.dylib\n 0x7fff5d257000 - 0x7fff5d45bfff libmecabra.dylib (779.24.1) <D71F71E0-30E2-3DB3-B636-7DE13D51FB4B> /usr/lib/libmecabra.dylib\n 0x7fff5d633000 - 0x7fff5d984ff7 libnetwork.dylib (1229.250.15) <72C7E9E3-B2BE-3300-BE1B-64606222022C> /usr/lib/libnetwork.dylib\n 0x7fff5da16000 - 0x7fff5e19bfdf libobjc.A.dylib (756.2) <7C312627-43CB-3234-9324-4DEA92D59F50> /usr/lib/libobjc.A.dylib\n 0x7fff5e1ad000 - 0x7fff5e1b1ffb libpam.2.dylib (22.200.1) <586CF87F-349C-393D-AEEB-FB75F94A5EB7> /usr/lib/libpam.2.dylib\n 0x7fff5e1b4000 - 0x7fff5e1e9fff libpcap.A.dylib (79.250.3) <97B8CE1B-3EF6-3443-95EF-5659733139C9> /usr/lib/libpcap.A.dylib\n 0x7fff5e302000 - 0x7fff5e31affb libresolv.9.dylib (65.200.3) <1FB0982D-84D9-36E0-B3D8-C808891EFF50> /usr/lib/libresolv.9.dylib\n 0x7fff5e36b000 - 0x7fff5e36cff7 libspindump.dylib (267.3) <A584E403-8C95-3841-9C16-E22664A5A63F> /usr/lib/libspindump.dylib\n 0x7fff5e36d000 - 0x7fff5e54afff libsqlite3.dylib (274.26) <6404BA3B-BCA4-301F-B2FE-8776105A2AA3> /usr/lib/libsqlite3.dylib\n 0x7fff5e763000 - 0x7fff5e766ff7 libutil.dylib (51.200.4) <CE9B18C9-66ED-32D4-9D29-01F8FCB467B0> /usr/lib/libutil.dylib\n 0x7fff5e767000 - 0x7fff5e774fff libxar.1.dylib (417.1) <39CCF46B-C81A-34B1-92A1-58C4E5DA846E> /usr/lib/libxar.1.dylib\n 0x7fff5e779000 - 0x7fff5e85cfff libxml2.2.dylib (32.19) <E07AB10E-E2E6-33F2-8550-C24A0EB8FEAC> /usr/lib/libxml2.2.dylib\n 0x7fff5e85d000 - 0x7fff5e885ff3 libxslt.1.dylib (16.7.1) <4A5CB7D5-50F8-36BF-8A80-D526C57EB5D9> /usr/lib/libxslt.1.dylib\n 0x7fff5e886000 - 0x7fff5e898ff7 libz.1.dylib (70.200.4) <B048FC1F-058F-3A08-A1FE-81D5308CB3E6> /usr/lib/libz.1.dylib\n 0x7fff5f07c000 - 0x7fff5f080ff3 libcache.dylib (81) <1987D1E1-DB11-3291-B12A-EBD55848E02D> /usr/lib/system/libcache.dylib\n 0x7fff5f081000 - 0x7fff5f08bff3 libcommonCrypto.dylib (60118.250.2) <1765BB6E-6784-3653-B16B-CB839721DC9A> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff5f08c000 - 0x7fff5f093ff7 libcompiler_rt.dylib (63.4) <5212BA7B-B7EA-37B4-AF6E-AC4F507EDFB8> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff5f094000 - 0x7fff5f09dff7 libcopyfile.dylib (146.250.1) <98CD00CD-9B91-3B5C-A9DB-842638050FA8> /usr/lib/system/libcopyfile.dylib\n 0x7fff5f09e000 - 0x7fff5f122fc3 libcorecrypto.dylib (602.260.2) <01464D24-570C-3B83-9D18-467769E0FCDD> /usr/lib/system/libcorecrypto.dylib\n 0x7fff5f1a9000 - 0x7fff5f1e2ff7 libdispatch.dylib (1008.270.1) <97273678-E94C-3C8C-89F6-2E2020F4B43B> /usr/lib/system/libdispatch.dylib\n 0x7fff5f1e3000 - 0x7fff5f20fff7 libdyld.dylib (655.1.1) <002418CC-AD11-3D10-865B-015591D24E6C> /usr/lib/system/libdyld.dylib\n 0x7fff5f210000 - 0x7fff5f210ffb libkeymgr.dylib (30) <0D0F9CA2-8D5A-3273-8723-59987B5827F2> /usr/lib/system/libkeymgr.dylib\n 0x7fff5f211000 - 0x7fff5f21dff3 libkxld.dylib (4903.278.56) <A3FF22FA-4AD4-3FF3-9891-B34482DC8572> /usr/lib/system/libkxld.dylib\n 0x7fff5f21e000 - 0x7fff5f21eff7 liblaunch.dylib (1336.261.6) <1F0EEC6F-4D08-38E6-ACF9-6E44D328931F> /usr/lib/system/liblaunch.dylib\n 0x7fff5f21f000 - 0x7fff5f224fff libmacho.dylib (927.0.3) <A377D608-77AB-3F6E-90F0-B4F251A5C12F> /usr/lib/system/libmacho.dylib\n 0x7fff5f225000 - 0x7fff5f227ff7 libquarantine.dylib (86.270.1) <3F36A3D6-9606-3D90-B520-809BAEF981C3> /usr/lib/system/libquarantine.dylib\n 0x7fff5f228000 - 0x7fff5f229ff7 libremovefile.dylib (45.200.2) <9FBEB2FF-EEBE-31BC-BCFC-C71F8D0E99B6> /usr/lib/system/libremovefile.dylib\n 0x7fff5f22a000 - 0x7fff5f241ff3 libsystem_asl.dylib (356.200.4) <A62A7249-38B8-33FA-9875-F1852590796C> /usr/lib/system/libsystem_asl.dylib\n 0x7fff5f242000 - 0x7fff5f242ff7 libsystem_blocks.dylib (73) <A453E8EE-860D-3CED-B5DC-BE54E9DB4348> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff5f243000 - 0x7fff5f2cafff libsystem_c.dylib (1272.250.1) <7EDACF78-2FA3-35B8-B051-D70475A35117> /usr/lib/system/libsystem_c.dylib\n 0x7fff5f2cb000 - 0x7fff5f2ceffb libsystem_configuration.dylib (963.270.3) <2B4A836D-68A4-33E6-8D48-CD4486B03387> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff5f2cf000 - 0x7fff5f2d2ff7 libsystem_coreservices.dylib (66) <719F75A4-74C5-3BA6-A09E-0C5A3E5889D7> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff5f2d3000 - 0x7fff5f2d9fff libsystem_darwin.dylib (1272.250.1) <EC9B39A5-9592-3577-8997-7DC721D20D8C> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff5f2da000 - 0x7fff5f2e0ffb libsystem_dnssd.dylib (878.270.3) <D5352ABD-0311-3327-8E64-93F29EB19BF1> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff5f2e1000 - 0x7fff5f32cffb libsystem_info.dylib (517.200.9) <D09D5AE0-2FDC-3A6D-93EC-729F931B1457> /usr/lib/system/libsystem_info.dylib\n 0x7fff5f32d000 - 0x7fff5f355ff7 libsystem_kernel.dylib (4903.278.56) <5B0F1BF0-E2F4-3753-87B6-6F91C594F59E> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff5f356000 - 0x7fff5f3a1ff7 libsystem_m.dylib (3158.200.7) <F19B6DB7-014F-3820-831F-389CCDA06EF6> /usr/lib/system/libsystem_m.dylib\n 0x7fff5f3a2000 - 0x7fff5f3ccfff libsystem_malloc.dylib (166.270.1) <011F3AD0-8E6A-3A89-AE64-6E5F6840F30A> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff5f3cd000 - 0x7fff5f3d7ff7 libsystem_networkextension.dylib (767.250.2) <FF06F13A-AEFE-3A27-A073-910EF78AEA36> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff5f3d8000 - 0x7fff5f3dffff libsystem_notify.dylib (172.200.21) <145B5CFC-CF73-33CE-BD3D-E8DDE268FFDE> /usr/lib/system/libsystem_notify.dylib\n 0x7fff5f3e0000 - 0x7fff5f3e9fef libsystem_platform.dylib (177.270.1) <9D1FE5E4-EB7D-3B3F-A8D1-A96D9CF1348C> /usr/lib/system/libsystem_platform.dylib\n 0x7fff5f3ea000 - 0x7fff5f3f4ff7 libsystem_pthread.dylib (330.250.2) <2D5C08FF-484F-3D59-9132-CE1DCB3F76D7> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff5f3f5000 - 0x7fff5f3f8ff7 libsystem_sandbox.dylib (851.270.5) <20D11F30-783F-3A56-9BD2-6CF38C049332> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff5f3f9000 - 0x7fff5f3fbff3 libsystem_secinit.dylib (30.260.2) <EF1EA47B-7B22-35E8-BD9B-F7003DCB96AE> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff5f3fc000 - 0x7fff5f403ff3 libsystem_symptoms.dylib (820.267.2) <0DA60956-0403-3456-9D6A-11F2DB9E3819> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff5f404000 - 0x7fff5f419ff7 libsystem_trace.dylib (906.260.3) <5B6FAE61-EF5C-381F-B71B-9B6F6428FEE2> /usr/lib/system/libsystem_trace.dylib\n 0x7fff5f41b000 - 0x7fff5f420ffb libunwind.dylib (35.4) <24A97A67-F017-3CFC-B0D0-6BD0224B1336> /usr/lib/system/libunwind.dylib\n 0x7fff5f421000 - 0x7fff5f450fff libxpc.dylib (1336.261.6) <522FA3AF-D3B1-3283-8EF4-8B17CB237B65> /usr/lib/system/libxpc.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 1047\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 76643460\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=750.3M resident=0K(0%) swapped_out_or_unallocated=750.3M(100%)\nWritable regions: Total=1.9G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.9G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 3 \nActivity Tracing 256K 1 \nCG backing stores 1320K 2 \nCG image 380K 11 \nCoreAnimation 328K 10 \nCoreGraphics 8K 1 \nCoreImage 32K 4 \nCoreUI image data 704K 8 \nCoreUI image file 540K 5 \nFoundation 4K 1 \nImage IO 256K 1 \nKernel Alloc Once 8K 1 \nMALLOC 868.0M 567 \nMALLOC guard page 32K 7 \nMALLOC_LARGE (reserved) 128K 1 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nMemory Tag 242 12K 1 \nMemory Tag 249 192K 2 \nOpenGL GLSL 256K 3 \nSTACK GUARD 92K 23 \nStack 36.7M 23 \nVM_ALLOCATE 524.9M 572 \nVM_ALLOCATE (reserved) 128.0M 2 reserved VM address space (unallocated)\n__DATA 120.0M 333 \n__DATA_CONST 20K 1 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 283.5M 85 \n__TEXT 467.0M 320 \n__UNICODE 564K 1 \nmapped file 79.5M 26 \nshared memory 4276K 12 \n=========== ======= ======= \nTOTAL 2.8G 2030 \nTOTAL, minus reserved VM space 2.3G 2030 \n\nModel: MacBookPro13,3, BootROM 429.80.1.0.0, 4 processors, Intel Core i7, 2,9 GHz, 16 GB, SMC 2.38f7\nGraphics: kHW_AMDRadeonPro460Item, AMD Radeon Pro 460, spdisplays_pcie_device, 4 GB\nGraphics: kHW_IntelHDGraphics530Item, Intel HD Graphics 530, spdisplays_builtin\nMemory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nMemory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.11)\nBluetooth: Version 6.0.14d12, 3 services, 27 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.0 Bus\nUSB Device: Wacom Wireless Receiver\nUSB Device: iBridge\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\n```\n\nCrash Log 2:\n```lines=25\nProcess: Blender [4923]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 2.92.0 (2.92.0 2021-02-25)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [4923]\nUser ID: 501\n\nDate/Time: 2021-03-14 13:37:52.807 +0100\nOS Version: macOS 11.2.3 (20D91)\nReport Version: 12\nBridge OS Version: 5.2 (18P4347)\nAnonymous UUID: B5FE06B1-F2A1-95FF-0593-1738C46F37D4\n\nSleep/Wake UUID: CBAA4D96-6C0A-4683-B5C6-D788FF799225\n\nTime Awake Since Boot: 65000 seconds\nTime Since Wake: 5700 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000024\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [4923]\n\nVM Regions Near 0x24:\n--> \n __TEXT 10016f000-10ab5b000 [169.9M] r-x/r-x SM=COW /Applications/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff6cc64690 gleRunVertexSubmitImmediate + 5632\n1 GLEngine \t0x00007fff6cbeb197 glDrawElementsInstancedBaseVertex_GL3Exec + 807\n2 libGL.dylib \t0x00007fff6cb323cf glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x0000000100808ec5 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010080864c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x0000000100807f9f DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x0000000100832048 workbench_draw_sample + 344\n7 org.blenderfoundation.blender \t0x000000010083229c workbench_draw_scene + 76\n8 org.blenderfoundation.blender \t0x00000001007ff33a drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x00000001007fde5d DRW_draw_render_loop_ex + 1565\n10 org.blenderfoundation.blender \t0x00000001007ff5db DRW_draw_render_loop_offscreen + 155\n11 org.blenderfoundation.blender \t0x000000010111d058 ED_view3d_draw_offscreen + 808\n12 org.blenderfoundation.blender \t0x000000010111d834 ED_view3d_draw_offscreen_imbuf + 692\n13 org.blenderfoundation.blender \t0x000000010111db64 ED_view3d_draw_offscreen_imbuf_simple + 628\n14 org.blenderfoundation.blender \t0x00000001006e6876 wm_save_as_mainfile_exec + 1974\n15 org.blenderfoundation.blender \t0x00000001006e6cb1 wm_save_mainfile_invoke + 289\n16 org.blenderfoundation.blender \t0x00000001006e0bd9 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x00000001006e216c wm_handler_operator_call + 636\n18 org.blenderfoundation.blender \t0x00000001006e1836 wm_handlers_do_intern + 1782\n19 org.blenderfoundation.blender \t0x00000001006dcdbf wm_handlers_do + 31\n20 org.blenderfoundation.blender \t0x00000001006dca1d wm_event_do_handlers + 3373\n21 org.blenderfoundation.blender \t0x00000001006d5360 WM_main + 32\n22 org.blenderfoundation.blender \t0x00000001002b3b8b main + 907\n23 libdyld.dylib \t0x00007fff203ca621 start + 1\n\nThread 1:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 13:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e 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_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 17:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 com.apple.audio.caulk \t0x00007fff284ad92a caulk::mach::semaphore::wait_or_error() + 16\n2 com.apple.audio.caulk \t0x00007fff2849a6e6 caulk::semaphore::timed_wait(double) + 110\n3 com.apple.audio.caulk \t0x00007fff2849a634 caulk::concurrent::details::worker_thread::run() + 30\n4 com.apple.audio.caulk \t0x00007fff2849a3c0 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*) + 45\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 18:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.audio.CoreAudio \t0x00007fff21e9edd5 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 com.apple.audio.CoreAudio \t0x00007fff21d3a467 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 3435\n4 com.apple.audio.CoreAudio \t0x00007fff21eddf2a HALB_IOThread::Entry(void*) + 72\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 31:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 34:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.CoreFoundation \t0x00007fff204a7bf7 __CFRunLoopServiceMachPort + 316\n3 com.apple.CoreFoundation \t0x00007fff204a62ca __CFRunLoopRun + 1315\n4 com.apple.CoreFoundation \t0x00007fff204a56ce CFRunLoopRunSpecific + 563\n5 com.apple.AppKit \t0x00007fff22e4b7c6 _NSEventThread + 124\n6 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n7 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 35:: Dispatch queue: com.apple.opengl.cvmDoWork\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 libdispatch.dylib \t0x00007fff2021a776 _dispatch_mach_send_and_wait_for_reply + 518\n3 libdispatch.dylib \t0x00007fff2021ab6e dispatch_mach_send_with_result_and_wait_for_reply + 50\n4 libxpc.dylib \t0x00007fff200f11ac xpc_connection_send_message_with_reply_sync + 238\n5 libCoreVMClient.dylib \t0x00007fff6c90670a cvms_element_build_and_get_internal + 229\n6 libCoreVMClient.dylib \t0x00007fff6c90660e cvms_element_build_from_source + 169\n7 libCVMSPluginSupport.dylib \t0x00007fff6c91bf14 cvm_deferred_build_modular(void*) + 422\n8 libdispatch.dylib \t0x00007fff202047c7 _dispatch_client_callout + 8\n9 libdispatch.dylib \t0x00007fff2020a5fe _dispatch_lane_serial_drain + 606\n10 libdispatch.dylib \t0x00007fff2020b0cb _dispatch_lane_invoke + 375\n11 libdispatch.dylib \t0x00007fff20214c5d _dispatch_workloop_worker_thread + 819\n12 libsystem_pthread.dylib \t0x00007fff203ac499 _pthread_wqthread + 314\n13 libsystem_pthread.dylib \t0x00007fff203ab467 start_wqthread + 15\n\nThread 36:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 37:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 38:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 39:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 40:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000024 rbx: 0x00000c3300041000 rcx: 0x00007fff6cc64690 rdx: 0x00007fff6cc65ae8\n rdi: 0x0000000000000006 rsi: 0x0000000000000000 rbp: 0x00007ffeefa8dce0 rsp: 0x00007ffeefa8db50\n r8: 0x0000000000000001 r9: 0x0000600003844bf0 r10: 0x0000000000000001 r11: 0x0000000186600082\n r12: 0x0000000000000000 r13: 0x0000000000000003 r14: 0x0000000000000000 r15: 0x00000c3300041000\n rip: 0x00007fff6cc64690 rfl: 0x0000000000010217 cr2: 0x0000000000000024\n \nLogical CPU: 0\nError Code: 0x00000004 (no mapping for user data read)\nTrap Number: 14\n\nThread 0 instruction stream:\n ff 48 8b 8d 28 ff ff ff-48 8b 44 01 08 e9 b6 f7 .H..(...H.D.....\n ff ff 85 d2 0f 84 84 00-00 00 49 89 fd be 00 00 ..........I.....\n 80 38 66 2e 0f 1f 84 00-00 00 00 00 0f 1f 40 00 .8f...........@.\n 89 d7 8d 14 3f 81 c6 00-00 80 ff f7 c7 00 02 00 ....?...........\n 00 74 ed 81 e2 fe 03 00-00 4c 89 ef 4c 8b ad 08 .t.......L..L...\n ff ff ff eb 4d c1 e6 0d-81 c6 00 00 00 38 eb 42 ....M........8.B\n [8b]08 89 8d 30 ff ff ff-8b 48 04 89 8d 34 ff ff ....0....H...4..\t<==\n ff e9 bc f9 ff ff 8b 08-89 8d 30 ff ff ff 8b 48 ..........0....H\n 04 89 8d 34 ff ff ff 8b-48 08 89 8d 38 ff ff ff ...4....H...8...\n 8b 40 0c 89 85 3c ff ff-ff e9 42 05 00 00 31 f6 .@...<....B...1.\n 31 d2 c1 e2 0d 09 f2 09-ca 89 95 30 ff ff ff 41 1..........0...A\n 83 fd 02 0f 82 e0 03 00-00 0f b7 70 02 89 f1 c1 ...........p....\n \nThread 0 last branch register state not available.\n\n\nBinary Images:\n 0x10016f000 - 0x10ab5afff +org.blenderfoundation.blender (2.92.0 - 2.92.0 2021-02-25) <F92572D3-A6D1-3A9C-9F23-72D19FC8242A> /Applications/Blender.app/Contents/MacOS/Blender\n 0x11191c000 - 0x111988fff +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x1186b5000 - 0x118818fff com.apple.audio.units.Components (1.14 - 1.14) <8C3B07AD-A96B-383A-94DC-902CCE4CD511> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x11886d000 - 0x11887cfff libobjc-trampolines.dylib (818.2) <29187EF9-2BD6-3ABF-8088-DE708721B612> /usr/lib/libobjc-trampolines.dylib\n 0x118c6b000 - 0x118d06fff dyld (832.7.3) <0D4EA85F-7E30-338B-9215-314A5A5539B6> /usr/lib/dyld\n 0x118d83000 - 0x119332fff com.apple.audio.AudioDSPComponents (1.0 - 1) <1A7FCA3F-190C-32F0-A48D-1524A11B0910> /System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP\n 0x119963000 - 0x119ce2fff com.apple.AMDRadeonX6000MTLDriver (4.2.15 - 4.0.2) <56DBFC8D-9ABB-34AE-873F-CAF3E6A184D5> /System/Library/Extensions/AMDRadeonX6000MTLDriver.bundle/Contents/MacOS/AMDRadeonX6000MTLDriver\n 0x11a0ab000 - 0x11a1fefff com.apple.AMDRadeonX6000GLDriver (4.2.15 - 4.0.2) <6A663F3B-05F2-35F1-9832-C0E3645C7E08> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/AMDRadeonX6000GLDriver\n 0x127eb0000 - 0x127eb1fff +_heapq.cpython-37m-darwin.so (0) <20086BF0-0130-3463-B824-F98C6D51BE39> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/_heapq.cpython-37m-darwin.so\n 0x1280ba000 - 0x1280bffff +math.cpython-37m-darwin.so (0) <F76ADA60-2AAA-34A7-BB31-26405F501673> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/math.cpython-37m-darwin.so\n 0x128fe4000 - 0x128fe7fff com.apple.CloudDocsFileProvider (1.0 - 726.1) <AB47EF12-834C-3720-BEE5-22E11638BFB7> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/CloudDocsFileProvider.bundle/Contents/MacOS/CloudDocsFileProvider\n 0x128ff8000 - 0x128ffbfff com.apple.FileProviderOverride (326.3 - 326.3) <54B6F621-7F46-3223-A227-C0757EB3F900> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FileProviderOverride.bundle/Contents/MacOS/FileProviderOverride\n 0x12900c000 - 0x129027fff com.apple.findersync.fileprovideroverride.FinderSyncCollaborationFileProviderOverride (1.0 - 1350.2.10) <EDD7E1EC-AB15-3496-9A57-237C9D3A2CEB> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride\n 0x7fff200e4000 - 0x7fff200e5fff libsystem_blocks.dylib (78) <E644CAA0-65B7-36E4-8041-520F3301F3DB> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff200e6000 - 0x7fff2011bfff libxpc.dylib (2038.80.3) <70F26262-01AA-3CEC-9FAD-2701D24096F0> /usr/lib/system/libxpc.dylib\n 0x7fff2011c000 - 0x7fff20133fff libsystem_trace.dylib (1277.80.2) <87FEF600-48D9-31C9-B8FC-D5249B2AE95D> /usr/lib/system/libsystem_trace.dylib\n 0x7fff20134000 - 0x7fff201d3fff libcorecrypto.dylib (1000.80.5) <1EB11CFB-ABD7-36DD-97C7-C112A6601416> /usr/lib/system/libcorecrypto.dylib\n 0x7fff201d4000 - 0x7fff20200fff libsystem_malloc.dylib (317.40.8) <A498D1EF-E43D-310C-84E8-9C0AADA0C475> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff20201000 - 0x7fff20245fff libdispatch.dylib (1271.40.12) <AD988EEA-1A2F-3404-9A6E-390FC2504223> /usr/lib/system/libdispatch.dylib\n 0x7fff20246000 - 0x7fff2027efff libobjc.A.dylib (818.2) <EB6B543F-D42C-3FB2-A2EC-43407C5F80D3> /usr/lib/libobjc.A.dylib\n 0x7fff2027f000 - 0x7fff20281fff libsystem_featureflags.dylib (28.60.1) <9CECB43A-094E-3CA9-B730-24DEA1A6DE05> /usr/lib/system/libsystem_featureflags.dylib\n 0x7fff20282000 - 0x7fff2030afff libsystem_c.dylib (1439.40.11) <4AF71812-4099-3E96-B271-1F259491A2B2> /usr/lib/system/libsystem_c.dylib\n 0x7fff2030b000 - 0x7fff20360fff libc++.1.dylib (904.4) <B217D905-4F9C-3DE0-8844-88FAA3C2C851> /usr/lib/libc++.1.dylib\n 0x7fff20361000 - 0x7fff20379fff libc++abi.dylib (904.4) <3C9FE530-3CD2-3A64-8A36-70816AEBDF0D> /usr/lib/libc++abi.dylib\n 0x7fff2037a000 - 0x7fff203a8fff libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff203a9000 - 0x7fff203b4fff libsystem_pthread.dylib (454.80.2) <B989DF6C-ADFE-3AF9-9C91-07D2521F9E47> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff203b5000 - 0x7fff203effff libdyld.dylib (832.7.3) <4641E48F-75B5-3CC7-8263-47BF79F15394> /usr/lib/system/libdyld.dylib\n 0x7fff203f0000 - 0x7fff203f9fff libsystem_platform.dylib (254.80.2) <1C3E1A0A-92A8-3CDE-B622-8940B43A5DF2> /usr/lib/system/libsystem_platform.dylib\n 0x7fff203fa000 - 0x7fff20425fff libsystem_info.dylib (542.40.3) <0C96CFE8-71F5-3335-8423-581BC3DE5846> /usr/lib/system/libsystem_info.dylib\n 0x7fff20426000 - 0x7fff208c1fff com.apple.CoreFoundation (6.9 - 1774.101) <2A0E160E-9EE6-3B23-8832-6979A16EC250> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff208c2000 - 0x7fff20af1fff com.apple.LaunchServices (1122.11 - 1122.11) <9ACD5692-3B92-3E6E-8B24-56ADCC911556> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff20af2000 - 0x7fff20bc5fff com.apple.gpusw.MetalTools (1.0 - 1) <B1FDD261-7707-3E20-A6C2-99D9AF46356B> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff20bc6000 - 0x7fff20e29fff libBLAS.dylib (1336.40.1) <92702864-A5C6-3E22-86F6-DB329532674A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff20e2a000 - 0x7fff20e77fff com.apple.Lexicon-framework (1.0 - 86.1) <2F429EBD-1BD2-3057-B760-8A81546DBD6F> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff20e78000 - 0x7fff20ee6fff libSparse.dylib (106) <B889DE4E-7356-3CC8-A13E-68D15E2024DF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff20ee7000 - 0x7fff20f64fff com.apple.SystemConfiguration (1.20 - 1.20) <3518EA0E-C32D-32CC-81B9-0F3C83B6430C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff20f65000 - 0x7fff20f9afff libCRFSuite.dylib (50) <970D1F7B-5DBD-355F-80D8-C820AA1626D2> /usr/lib/libCRFSuite.dylib\n 0x7fff20f9b000 - 0x7fff211d2fff libmecabra.dylib (929.1.1) <102A0AD8-D119-340B-B652-B75F0AAB1C7E> /usr/lib/libmecabra.dylib\n 0x7fff211d3000 - 0x7fff21536fff com.apple.Foundation (6.9 - 1774.101) <8D9081B3-3F6A-31A0-9B20-1AE5CD8DD747> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff21537000 - 0x7fff21623fff com.apple.LanguageModeling (1.0 - 247.1) <1A05BCD7-232F-3950-936D-EC0F95BA3FB0> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff21624000 - 0x7fff2175afff com.apple.CoreDisplay (231.3 - 231.3) <6DD6A260-800F-3284-842C-8E4CB9EA47FF> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff2175b000 - 0x7fff219d1fff com.apple.audio.AudioToolboxCore (1.0 - 1180.25) <DEE2C5BA-BFD1-349F-A10A-B10717BA8F7C> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore\n 0x7fff219d2000 - 0x7fff21bbafff com.apple.CoreText (677.3.0.4 - 677.3.0.4) <9A8DC9A0-1A80-3A26-ACA0-A245D3FFF921> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff21bbb000 - 0x7fff2225ffff com.apple.audio.CoreAudio (5.0 - 5.0) <801E2D1E-7EA5-37DA-8F44-B6D7DD3CE5B9> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff22260000 - 0x7fff225b1fff com.apple.security (7.0 - 59754.80.3) <B377D7C7-EDB6-3737-B492-E9872F4C6469> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff225b2000 - 0x7fff22813fff libicucore.A.dylib (66109) <8F8D8A8B-4EE0-3C09-9F45-725A1FBDD38C> /usr/lib/libicucore.A.dylib\n 0x7fff22814000 - 0x7fff2281dfff libsystem_darwin.dylib (1439.40.11) <E016D8F7-C87F-36F8-B8A0-6A61B8E4BACB> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff2281e000 - 0x7fff22b05fff com.apple.CoreServices.CarbonCore (1307 - 1307) <B857EADF-D517-34E8-8053-34C0E6695250> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff22b06000 - 0x7fff22b44fff com.apple.CoreServicesInternal (476 - 476) <0DA95074-B315-3B84-B8A3-BAEDC4471A2C> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff22b45000 - 0x7fff22b7ffff com.apple.CSStore (1122.11 - 1122.11) <89992991-8538-380B-B2B8-4EA997CBFDBE> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore\n 0x7fff22b80000 - 0x7fff22c2efff com.apple.framework.IOKit (2.0.2 - 1845.81.1) <49AC0177-35A3-3C96-AD9D-3E59923C4761> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff22c2f000 - 0x7fff22c3afff libsystem_notify.dylib (279.40.4) <B2BF20C7-448A-3FBD-A2F5-AB7618D173F6> /usr/lib/system/libsystem_notify.dylib\n 0x7fff22c3b000 - 0x7fff22c86fff libsandbox.1.dylib (1441.60.4) <591F41F3-1FE9-354F-A1F9-BC0CC73333DA> /usr/lib/libsandbox.1.dylib\n 0x7fff22c87000 - 0x7fff239e9fff com.apple.AppKit (6.9 - 2022.30.122) <EA4B3536-A5AF-3E5D-A8E3-A3F795F34F05> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff239ea000 - 0x7fff23c3efff com.apple.UIFoundation (1.0 - 727.3) <5A905085-B5EB-3F71-A663-200428E7A5F4> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff23c3f000 - 0x7fff23c51fff com.apple.UniformTypeIdentifiers (633.0.2 - 633.0.2) <2AAE247F-1BA0-3E42-A07B-CBE413747B30> /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers\n 0x7fff23c52000 - 0x7fff23ddcfff com.apple.desktopservices (1.18 - 1346.3.1) <2144B85E-A433-3F9E-A25D-E8F9D7B6D175> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff23ddd000 - 0x7fff23deffff com.apple.metadata.SpotlightLinguistics (1.0 - 1) <7FC34645-4185-3382-8813-9780C822BB15> /System/Library/PrivateFrameworks/SpotlightLinguistics.framework/Versions/A/SpotlightLinguistics\n 0x7fff240a9000 - 0x7fff246ecfff libnetwork.dylib (2288.80.2) <A3F1E999-6D61-32D7-B3F7-67832CEA53CD> /usr/lib/libnetwork.dylib\n 0x7fff246ed000 - 0x7fff24b8afff com.apple.CFNetwork (1220.1 - 1220.1) <04A917FB-DBFB-3432-BA4C-5B860990A420> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff24b8b000 - 0x7fff24b99fff libsystem_networkextension.dylib (1295.80.3) <5213D866-7D0E-3FD9-8E1A-03C0E39CEC44> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff24b9a000 - 0x7fff24b9afff libenergytrace.dylib (22) <33A9FBF3-A2D3-3ECE-9370-B0ADDE3896DE> /usr/lib/libenergytrace.dylib\n 0x7fff24b9b000 - 0x7fff24bf6fff libMobileGestalt.dylib (978.80.1) <C4C7A5DC-C3AD-374D-902A-B6DED14FBB67> /usr/lib/libMobileGestalt.dylib\n 0x7fff24bf7000 - 0x7fff24c0dfff libsystem_asl.dylib (385) <5B48071E-85EB-33B0-AE9B-127AEB398AEC> /usr/lib/system/libsystem_asl.dylib\n 0x7fff24c0e000 - 0x7fff24c25fff com.apple.TCC (1.0 - 1) <2F48471B-68F3-3017-8B18-BEDD4ED5853F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff24c26000 - 0x7fff24f8cfff com.apple.SkyLight (1.600.0 - 570.7) <8034EAA7-787C-3A3E-A301-FF90376F247D> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff24f8d000 - 0x7fff25620fff com.apple.CoreGraphics (2.0 - 1463.3.2) <29845645-F6F2-34E0-AC0D-C659773C78ED> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff25621000 - 0x7fff25717fff com.apple.ColorSync (4.13.0 - 3473.3.1) <A67D9B0A-E9FB-325A-873B-032DAF45C112> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff25718000 - 0x7fff25773fff com.apple.HIServices (1.22 - 714) <780B2B09-80A6-32C8-B9E5-024988196E00> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff25b1f000 - 0x7fff25f3dfff com.apple.CoreData (120 - 1044.3) <7BE9684B-4439-3008-A2A7-4093BBCA180A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff25f3e000 - 0x7fff25f54fff com.apple.ProtocolBuffer (1 - 285.23.11.29.1) <58CD91DC-64A9-3A97-AE41-6EA30308D617> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff25f55000 - 0x7fff26114fff libsqlite3.dylib (321.1) <ACCC6A4C-3257-38A4-8AFB-BA73D906205B> /usr/lib/libsqlite3.dylib\n 0x7fff26115000 - 0x7fff26191fff com.apple.Accounts (113 - 113) <BCB8494A-A340-30A1-928C-9B53E953328D> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts\n 0x7fff26192000 - 0x7fff261aafff com.apple.commonutilities (8.0 - 900) <8C96D016-2B40-39C0-A51C-9CF687AE7218> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities\n 0x7fff261ab000 - 0x7fff2622cfff com.apple.BaseBoard (526 - 526) <3A964BB6-7AB8-3B5D-BAF6-40F56D2BA393> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff2622d000 - 0x7fff26278fff com.apple.RunningBoardServices (1.0 - 505.80.1) <4B9FFFB3-310F-350A-BEBB-AB779BD3F405> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices\n 0x7fff26279000 - 0x7fff262eefff com.apple.AE (918.0.1 - 918.0.1) <9B6B42DB-8768-343B-B10E-A9A5710280CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff262ef000 - 0x7fff262f5fff libdns_services.dylib (1310.80.1) <97EB5DFD-BB41-3834-BF09-1F597D84F324> /usr/lib/libdns_services.dylib\n 0x7fff262f6000 - 0x7fff262fdfff libsystem_symptoms.dylib (1431.40.36) <BC85B46C-02EE-31FF-861D-F0DE01E8F6CF> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff262fe000 - 0x7fff26482fff com.apple.Network (1.0 - 1) <75C2713C-F0D8-32BA-A839-17A2AE49A061> /System/Library/Frameworks/Network.framework/Versions/A/Network\n 0x7fff26483000 - 0x7fff264a7fff com.apple.analyticsd (1.0 - 1) <4FFF906A-FE79-38F9-B777-AE878A0C99F1> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics\n 0x7fff264a8000 - 0x7fff264aafff libDiagnosticMessagesClient.dylib (112) <20EDB261-69C7-3E4A-8C00-878814186A62> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff264ab000 - 0x7fff264f7fff com.apple.spotlight.metadata.utilities (1.0 - 2150.7.5) <FB7BF527-2D95-3E82-AAD8-D42B33DAC0F0> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff264f8000 - 0x7fff26592fff com.apple.Metadata (10.7.0 - 2150.7.5) <49187239-597B-31A1-8895-8AA265C818C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff26593000 - 0x7fff26599fff com.apple.DiskArbitration (2.7 - 2.7) <ACFCD23E-05DF-3F96-BCFA-E294AAAFD2CE> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff2659a000 - 0x7fff26c40fff com.apple.vImage (8.1 - 544.2) <3EBF95E1-30EB-3162-A9D4-B97BE581B69F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff26c41000 - 0x7fff26f0bfff com.apple.QuartzCore (1.11 - 926.8) <04D8759B-1119-3E37-B922-32BDECB7C5D2> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff26f0c000 - 0x7fff26f4dfff libFontRegistry.dylib (309) <9E9329F6-7384-3C7F-83E7-D52CD7FFBC09> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff26f4e000 - 0x7fff2708ffff com.apple.coreui (2.1 - 690) <6DB427BB-44CA-3002-A3FF-77F0FEFC2A51> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff27090000 - 0x7fff2717bfff com.apple.ViewBridge (551.3 - 551.3) <9F31CEDB-5B8A-3BAE-A638-E9F352EF4E87> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff2717c000 - 0x7fff27187fff com.apple.PerformanceAnalysis (1.275 - 275) <2E5E666D-EE93-3949-8C76-692FA748D129> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff27188000 - 0x7fff27197fff com.apple.OpenDirectory (11.2 - 230.40.1) <333A7F2E-0F3E-37F1-9E1B-69996F5084D2> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff27198000 - 0x7fff271b7fff com.apple.CFOpenDirectory (11.2 - 230.40.1) <25F138F8-9E55-3749-8271-0FDB275C3E2C> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff271b8000 - 0x7fff271c0fff com.apple.CoreServices.FSEvents (1290.40.2 - 1290.40.2) <6B70B98B-BCC5-3FBE-A6B5-CD0696AA055A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff271c1000 - 0x7fff271e5fff com.apple.coreservices.SharedFileList (144 - 144) <C861FAD6-D3A5-302C-88AE-B2813F7201A7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff271e6000 - 0x7fff271e8fff libapp_launch_measurement.dylib (14.1) <2BBB708C-4D91-364E-ABD0-39BF198688A6> /usr/lib/libapp_launch_measurement.dylib\n 0x7fff271e9000 - 0x7fff27231fff com.apple.CoreAutoLayout (1.0 - 21.10.1) <7A2E42E6-3AF2-3ECB-8A16-5C4AC41206EE> /System/Library/PrivateFrameworks/CoreAutoLayout.framework/Versions/A/CoreAutoLayout\n 0x7fff27232000 - 0x7fff27314fff libxml2.2.dylib (34.9) <E0BF29C7-869B-3DD5-82AE-F36E6398091A> /usr/lib/libxml2.2.dylib\n 0x7fff27315000 - 0x7fff27361fff com.apple.CoreVideo (1.8 - 408.4) <50857F8D-C7CC-3609-B0DB-FC3C7382243B> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff27362000 - 0x7fff27364fff com.apple.loginsupport (1.0 - 1) <B149BCAF-854C-3820-809D-15C6077FFB8B> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff27365000 - 0x7fff2738dfff com.apple.aps.framework (4.0 - 4.0) <D86ED827-F22D-3A52-B055-251478B29AE1> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService\n 0x7fff2738e000 - 0x7fff273abfff com.apple.UserManagement (1.0 - 1) <B6B35079-3860-384F-B7A2-584192BAAE70> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement\n 0x7fff273ac000 - 0x7fff2754bfff com.apple.cloudkit.CloudKit (970 - 970) <58BD254C-AAF1-3CC5-AAB7-2EF0A70BA033> /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit\n 0x7fff2754c000 - 0x7fff275cefff com.apple.CloudDocs (1.0 - 726.1) <EDBE33B4-1629-3323-902F-F6DABE66D552> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs\n 0x7fff282c8000 - 0x7fff28345fff com.apple.corelocation (2420.12.16 - 2420.12.16) <8BD49018-78D4-3A81-88AD-47DE1A8E3BFE> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation\n 0x7fff28346000 - 0x7fff28356fff libsystem_containermanager.dylib (318.80.2) <6F08275F-B912-3D8E-9D74-4845158AE4F3> /usr/lib/system/libsystem_containermanager.dylib\n 0x7fff28357000 - 0x7fff28368fff com.apple.IOSurface (289.3 - 289.3) <029C5E16-2E04-3E98-BE25-CC8BAE5E3D19> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff28369000 - 0x7fff28371fff com.apple.IOAccelerator (439.52 - 439.52) <41EDF102-E1B5-3FBA-A74A-6C583CAA5D24> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff28372000 - 0x7fff28497fff com.apple.Metal (244.32.7 - 244.32.7) <829B9C4D-2DB6-38C9-9FE8-E6544FB3BDCC> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff28498000 - 0x7fff284b4fff com.apple.audio.caulk (1.0 - 70) <3FFEB564-C7CC-3F3E-B193-3F4E7B7C6764> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7fff284b5000 - 0x7fff2859efff com.apple.CoreMedia (1.0 - 2765.6.4.2) <8E50C806-C6A2-3B96-B3D2-DA1FFC73D2A8> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff2859f000 - 0x7fff286fbfff libFontParser.dylib (305.3.0.1) <2CD3B3C9-7022-34DD-BF53-D48D79DEF726> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib\n 0x7fff286fc000 - 0x7fff289fbfff com.apple.HIToolbox (2.1.1 - 1061.2) <82B316E1-E47F-334D-8C33-DB1B7E8A4F71> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff289fc000 - 0x7fff28a0ffff com.apple.framework.DFRFoundation (1.0 - 265) <4B26DB42-BFDD-3B0D-8966-3D0926A3A5B7> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff28a10000 - 0x7fff28a13fff com.apple.dt.XCTTargetBootstrap (1.0 - 17500) <D279B67B-7108-3A16-93E5-5A429B898DAA> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff28a14000 - 0x7fff28a3dfff com.apple.CoreSVG (1.0 - 149) <D88B5A7D-F9F7-36C2-A346-87D7163605A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG\n 0x7fff28a3e000 - 0x7fff28c78fff com.apple.ImageIO (3.3.0 - 2130.3.5) <3558ABA9-6522-36A8-A49D-8641A9D7FCE1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff28c79000 - 0x7fff28ff6fff com.apple.CoreImage (16.2.0 - 1130.1) <29BE82F7-93BE-336A-AF66-9DD3F48B8565> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff28ff7000 - 0x7fff29052fff com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <287C79B5-4E13-3DF6-BDC4-439EC621E010> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff29053000 - 0x7fff29056fff libsystem_configuration.dylib (1109.60.2) <4917D824-4DE8-32CC-9ED2-1FBF371FEB9F> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff29057000 - 0x7fff2905bfff libsystem_sandbox.dylib (1441.60.4) <5F7F3DD1-4B38-310C-AA8F-19FF1B0F5276> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff2905c000 - 0x7fff2905dfff com.apple.AggregateDictionary (1.0 - 1) <E6C1A91D-4ADE-33CB-AA47-2F573811BFD9> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff2905e000 - 0x7fff29061fff com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <4F8A1D06-3EFF-3174-BE9C-C4B70A3EA290> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo\n 0x7fff29062000 - 0x7fff29063fff liblangid.dylib (136) <E8044658-AE79-3930-A902-07A38BB22382> /usr/lib/liblangid.dylib\n 0x7fff29064000 - 0x7fff29104fff com.apple.CoreNLP (1.0 - 245.1) <6C49B26B-CB39-3504-AD5E-9C3333FFE086> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff29105000 - 0x7fff2910bfff com.apple.LinguisticData (1.0 - 399) <B059FF7F-731A-38F1-884A-588C6C8CA7F2> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff2910c000 - 0x7fff297c9fff libBNNS.dylib (288.80.1) <C5CD30D8-114B-3104-9020-E5C05E68CEE8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff297ca000 - 0x7fff2999dfff libvDSP.dylib (760.40.6) <4CCEE561-A72B-33BC-B9F9-77A6CF2E7AF0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff2999e000 - 0x7fff299b0fff com.apple.CoreEmoji (1.0 - 128) <D43F3FFA-6692-3D56-ACBA-DDA40C566DDE> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff299b1000 - 0x7fff299bbfff com.apple.IOMobileFramebuffer (343.0.0 - 343.0.0) <B15E9DA1-1C81-3ECF-94C7-FD137AD6C5E2> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/Versions/A/IOMobileFramebuffer\n 0x7fff299bc000 - 0x7fff29a8efff com.apple.framework.CoreWLAN (16.0 - 1657) <35927D28-3324-3CAB-9255-276A7022EADC> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff29a8f000 - 0x7fff29c8efff com.apple.CoreUtils (6.5 - 650.6) <184C48A4-7F66-395B-81DB-DAA1641383CF> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff29c8f000 - 0x7fff29cb1fff com.apple.MobileKeyBag (2.0 - 1.0) <0F83FED4-709A-37A0-9E04-EFFD71CB1272> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff29cb2000 - 0x7fff29cc2fff com.apple.AssertionServices (1.0 - 505.80.1) <A00B802D-7BB8-3F6B-A79D-E9697F7D0ABB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff29cc3000 - 0x7fff29d4ffff com.apple.securityfoundation (6.0 - 55240.40.4) <72AC63B1-0B72-394F-97E8-BA9B114DD0A9> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff29d50000 - 0x7fff29d59fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <EC15118E-62BD-3C24-A880-3B9B74318B0B> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff29d5a000 - 0x7fff29d5efff com.apple.xpc.ServiceManagement (1.0 - 1) <FD031028-B702-3909-B2AF-3916404DD4A8> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff29d5f000 - 0x7fff29d61fff libquarantine.dylib (119.40.2) <40D35D75-524B-3DA6-8159-E7E0FA66F5BC> /usr/lib/system/libquarantine.dylib\n 0x7fff29d62000 - 0x7fff29d6dfff libCheckFix.dylib (31) <74E17BB2-1A3C-3574-92DD-63ABE39E3FF9> /usr/lib/libCheckFix.dylib\n 0x7fff29d6e000 - 0x7fff29d85fff libcoretls.dylib (169) <B33BEF87-3275-356D-9815-D0E94122D2EB> /usr/lib/libcoretls.dylib\n 0x7fff29d86000 - 0x7fff29d96fff libbsm.0.dylib (68.40.1) <D71EF121-D4B0-306E-9843-9FAFD558E3A4> /usr/lib/libbsm.0.dylib\n 0x7fff29d97000 - 0x7fff29de0fff libmecab.dylib (929.1.1) <1F424683-4213-3594-9BF5-EFCCCDAA83A5> /usr/lib/libmecab.dylib\n 0x7fff29de1000 - 0x7fff29de6fff libgermantok.dylib (24) <E40EFA11-E95C-36D1-A8BE-8CA5B1DD179D> /usr/lib/libgermantok.dylib\n 0x7fff29de7000 - 0x7fff29dfcfff libLinearAlgebra.dylib (1336.40.1) <0D017F3F-6FD6-38DB-AA14-A64523A4D093> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff29dfd000 - 0x7fff2a024fff com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <8FA469B3-48BE-315B-B3A0-C868CD541608> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff2a025000 - 0x7fff2a074fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <613BB6F1-3588-3E25-B523-059022FBE56E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff2a075000 - 0x7fff2a1bcfff com.apple.MLCompute (1.0 - 1) <01B968D9-A464-3667-8B8E-C99AEBA1FF79> /System/Library/Frameworks/MLCompute.framework/Versions/A/MLCompute\n 0x7fff2a1bd000 - 0x7fff2a1f3fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <B988D5F6-4E54-335D-A654-12C74FD668EA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff2a1f4000 - 0x7fff2a231fff com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <51ECDE6B-39F8-3BAB-ADC1-84C958F40A3F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray\n 0x7fff2a232000 - 0x7fff2a2c2fff com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <D009508B-DCDF-3421-B1CB-40FDF4A68E93> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff2a2c3000 - 0x7fff2a2d2fff com.apple.AppleFSCompression (125 - 1.0) <879A04AA-F9A1-3640-A9EF-F5D0813C852A> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff2a2d3000 - 0x7fff2a2e0fff libbz2.1.0.dylib (44) <E163D5F9-E202-3A53-817B-8BC40B9293C0> /usr/lib/libbz2.1.0.dylib\n 0x7fff2a2e1000 - 0x7fff2a2e5fff libsystem_coreservices.dylib (127) <529A0663-A936-309C-9318-1B04B7F70658> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff2a2e6000 - 0x7fff2a313fff com.apple.CoreServices.OSServices (1122.11 - 1122.11) <8D30829B-426E-361E-B2A9-5850F1E5513D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff2a314000 - 0x7fff2a445fff com.apple.AuthKit (1.0 - 1) <4A9B2D94-7AB0-3417-8D4E-A9C6C31C31D4> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff2a4e9000 - 0x7fff2a4fbfff libz.1.dylib (76) <6E2BD7A3-DC55-3183-BBF7-3AC367BC1834> /usr/lib/libz.1.dylib\n 0x7fff2a4fc000 - 0x7fff2a543fff libsystem_m.dylib (3186.40.2) <DD26CC5C-AFF6-305F-A567-14909DD57163> /usr/lib/system/libsystem_m.dylib\n 0x7fff2a544000 - 0x7fff2a544fff libcharset.1.dylib (59) <D14F9D24-693A-37F0-8F92-D260248EB282> /usr/lib/libcharset.1.dylib\n 0x7fff2a545000 - 0x7fff2a54afff libmacho.dylib (973.4) <C2584BC4-497B-3170-ADDF-21B8E10B4DFD> /usr/lib/system/libmacho.dylib\n 0x7fff2a54b000 - 0x7fff2a566fff libkxld.dylib (7195.81.3) <DE05C188-D9FE-30DC-8299-DF3DC9F837A5> /usr/lib/system/libkxld.dylib\n 0x7fff2a567000 - 0x7fff2a572fff libcommonCrypto.dylib (60178.40.2) <822A29CE-BF54-35AD-BB15-8FAECB800C7D> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff2a573000 - 0x7fff2a57dfff libunwind.dylib (200.10) <1D0A4B4A-4370-3548-8DC1-42A7B4BD45D3> /usr/lib/system/libunwind.dylib\n 0x7fff2a57e000 - 0x7fff2a585fff liboah.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/liboah.dylib\n 0x7fff2a586000 - 0x7fff2a590fff libcopyfile.dylib (173.40.2) <39DBE613-135B-3AFE-A6AF-7898A37F70C2> /usr/lib/system/libcopyfile.dylib\n 0x7fff2a591000 - 0x7fff2a598fff libcompiler_rt.dylib (102.2) <62EE1D14-5ED7-3CEC-81C0-9C93833641F1> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff2a599000 - 0x7fff2a59bfff libsystem_collections.dylib (1439.40.11) <C53D5E0C-0C4F-3B35-A24B-E0D7101A3F95> /usr/lib/system/libsystem_collections.dylib\n 0x7fff2a59c000 - 0x7fff2a59efff libsystem_secinit.dylib (87.60.1) <E05E35BC-1BAB-365B-8BEE-D774189EFD3B> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff2a59f000 - 0x7fff2a5a1fff libremovefile.dylib (49.40.3) <5CC12A16-82CB-32F0-9040-72CFC88A48DF> /usr/lib/system/libremovefile.dylib\n 0x7fff2a5a2000 - 0x7fff2a5a2fff libkeymgr.dylib (31) <803F6AED-99D5-3CCF-B0FA-361BCF14C8C0> /usr/lib/system/libkeymgr.dylib\n 0x7fff2a5a3000 - 0x7fff2a5aafff libsystem_dnssd.dylib (1310.80.1) <E0A0CAB3-6779-3C83-AC67-046CFE69F9C2> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff2a5ab000 - 0x7fff2a5b0fff libcache.dylib (83) <1A98B064-8FED-39CF-BB2E-5BDA1EF5B65A> /usr/lib/system/libcache.dylib\n 0x7fff2a5b1000 - 0x7fff2a5b2fff libSystem.B.dylib (1292.60.1) <83503CE0-32B1-36DB-A4F0-3CC6B7BCF50A> /usr/lib/libSystem.B.dylib\n 0x7fff2a5b3000 - 0x7fff2a5b6fff libfakelink.dylib (3) <D939A124-9FD5-37A2-B03B-72E98CBC98FE> /usr/lib/libfakelink.dylib\n 0x7fff2a5b7000 - 0x7fff2a5b7fff com.apple.SoftLinking (1.0 - 1) <EF2AC5FF-B98D-3252-ABA8-2FC721CBA942> /System/Library/PrivateFrameworks/SoftLinking.framework/Versions/A/SoftLinking\n 0x7fff2a5b8000 - 0x7fff2a5effff libpcap.A.dylib (98.40.1) <DE5787F8-D011-3E71-8323-936B35976D9E> /usr/lib/libpcap.A.dylib\n 0x7fff2a5f0000 - 0x7fff2a6e0fff libiconv.2.dylib (59) <AD10ECF4-E137-3152-9612-7EC548D919E8> /usr/lib/libiconv.2.dylib\n 0x7fff2a6e1000 - 0x7fff2a6f2fff libcmph.dylib (8) <A5D1EBB3-70A1-3ECA-A3C7-E97FBAD36ECF> /usr/lib/libcmph.dylib\n 0x7fff2a6f3000 - 0x7fff2a764fff libarchive.2.dylib (83.40.4) <9061C767-43FD-3483-9C48-73973AF82DC1> /usr/lib/libarchive.2.dylib\n 0x7fff2a765000 - 0x7fff2a7ccfff com.apple.SearchKit (1.4.1 - 1.4.1) <6243D4C0-3572-30A6-889A-B8690A5EAC24> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff2a7cd000 - 0x7fff2a7cefff libThaiTokenizer.dylib (3) <47CDE3EE-60AB-38CE-9494-5CC047CACA7F> /usr/lib/libThaiTokenizer.dylib\n 0x7fff2a7cf000 - 0x7fff2a7f6fff com.apple.applesauce (1.0 - 16.26) <4A637FE0-A740-32F0-AE70-4593F6DF1573> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff2a7f7000 - 0x7fff2a80efff libapple_nghttp2.dylib (1.41) <A2F6DE8D-2B38-3669-A16E-E1BD54108F24> /usr/lib/libapple_nghttp2.dylib\n 0x7fff2a80f000 - 0x7fff2a821fff libSparseBLAS.dylib (1336.40.1) <FC45F7FD-6B10-3F8D-A553-F57C757F6717> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff2a822000 - 0x7fff2a823fff com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <F37DBCE9-20CD-33D4-806B-93B326E08422> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff2a824000 - 0x7fff2a828fff libpam.2.dylib (28.40.1) <FA3308D0-E7B4-3A2C-AE39-0E085F6CDEE0> /usr/lib/libpam.2.dylib\n 0x7fff2a829000 - 0x7fff2a841fff libcompression.dylib (96.40.6) <9C42DB2C-0A6D-38CE-BB8D-899A9B34B695> /usr/lib/libcompression.dylib\n 0x7fff2a842000 - 0x7fff2a847fff libQuadrature.dylib (7) <55EE1866-623B-3C10-91FB-C8B06EB83995> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff2a848000 - 0x7fff2abe4fff libLAPACK.dylib (1336.40.1) <2F92E8CD-396D-3665-88EB-41A4E1A9CB31> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff2abe5000 - 0x7fff2ac33fff com.apple.DictionaryServices (1.2 - 341) <5D0B1BB2-995B-32EB-AE75-F5F27127ACAF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff2ac34000 - 0x7fff2ac4cfff liblzma.5.dylib (16) <168D84A7-8E54-361E-9161-B661D96C0C9A> /usr/lib/liblzma.5.dylib\n 0x7fff2ac4d000 - 0x7fff2ac4efff libcoretls_cfhelpers.dylib (169) <80AF345B-1989-3C88-AEF4-8FF18A366A9C> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff2ac4f000 - 0x7fff2ad49fff com.apple.APFS (1677.81.1 - 1677.81.1) <E48CCAAC-34B5-377E-8E5D-06CDBD411C2F> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff2ad4a000 - 0x7fff2ad57fff libxar.1.dylib (452) <FAA7B36E-21EC-3ADF-AA6A-E3742737CA3A> /usr/lib/libxar.1.dylib\n 0x7fff2ad58000 - 0x7fff2ad5bfff libutil.dylib (58.40.2) <0A268749-08E7-3551-8969-442210651CCA> /usr/lib/libutil.dylib\n 0x7fff2ad5c000 - 0x7fff2ad84fff libxslt.1.dylib (17.3) <1C5219FB-B504-3658-B23B-2C45A3BA28F1> /usr/lib/libxslt.1.dylib\n 0x7fff2ad85000 - 0x7fff2ad8ffff libChineseTokenizer.dylib (37) <718400BF-9911-3CB6-8CCE-4C2D7C35D80A> /usr/lib/libChineseTokenizer.dylib\n 0x7fff2ad90000 - 0x7fff2ae4efff libvMisc.dylib (760.40.6) <9D11FCFC-6C30-32B6-864B-9CC3ED7D1143> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff2ae4f000 - 0x7fff2aee7fff libate.dylib (3.0.4) <42707DFB-86A4-3F56-A5AF-E6DAA7E49DC7> /usr/lib/libate.dylib\n 0x7fff2aee8000 - 0x7fff2aeeffff libIOReport.dylib (64) <8DEEA01D-B715-340A-900E-B448AB22720E> /usr/lib/libIOReport.dylib\n 0x7fff2aef0000 - 0x7fff2af1efff com.apple.CrashReporterSupport (10.13 - 15047.1) <EA306EDB-2A02-3FB6-8812-F5EAA337AEE6> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff2b00b000 - 0x7fff2b012fff libMatch.1.dylib (38) <DE8B7844-BFB2-3E3E-9FD0-1C9AD1DC1736> /usr/lib/libMatch.1.dylib\n 0x7fff2b013000 - 0x7fff2b09efff libCoreStorage.dylib (554) <044E6815-6340-31D5-BEE9-760C354E92A3> /usr/lib/libCoreStorage.dylib\n 0x7fff2b09f000 - 0x7fff2b0f2fff com.apple.AppleVAFramework (6.1.3 - 6.1.3) <E3BE877B-1C78-3ABF-8C41-66FE9B6971C7> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff2b0f3000 - 0x7fff2b10cfff libexpat.1.dylib (26) <1D978F91-674E-3A44-8A93-773C7E3E513C> /usr/lib/libexpat.1.dylib\n 0x7fff2b10d000 - 0x7fff2b116fff libheimdal-asn1.dylib (597.80.1) <8F6CD867-FB45-375D-82C1-E0AE79558C8C> /usr/lib/libheimdal-asn1.dylib\n 0x7fff2b117000 - 0x7fff2b12bfff com.apple.IconFoundation (479.3 - 479.3) <3563C4B4-ABF6-3DE0-8381-D3667DFE2B80> /System/Library/PrivateFrameworks/IconFoundation.framework/Versions/A/IconFoundation\n 0x7fff2b12c000 - 0x7fff2b199fff com.apple.IconServices (479.3 - 479.3) <B6859735-701D-307E-8061-298BA2296E47> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff2b19a000 - 0x7fff2b237fff com.apple.MediaExperience (1.0 - 1) <14E84D66-28B8-390E-A499-9F24B7628EC7> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience\n 0x7fff2b238000 - 0x7fff2b261fff com.apple.persistentconnection (1.0 - 1.0) <B3FE85C5-8034-38D5-8566-5317B49ECF61> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection\n 0x7fff2b262000 - 0x7fff2b270fff com.apple.GraphVisualizer (1.0 - 100.1) <A7393BC4-4441-31B5-BB15-5A5A70738BEC> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff2b271000 - 0x7fff2b68cfff com.apple.vision.FaceCore (4.3.2 - 4.3.2) <23CD0C8A-E300-3E28-BD5B-DDCDA4521C54> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff2b68d000 - 0x7fff2b6d7fff com.apple.OTSVG (1.0 - 677.3.0.4) <827396F3-F3A7-3A4F-BE7F-171077501137> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff2b6d8000 - 0x7fff2b6defff com.apple.xpc.AppServerSupport (1.0 - 2038.80.3) <C78E9D22-5110-349B-AF8E-6BA893A20214> /System/Library/PrivateFrameworks/AppServerSupport.framework/Versions/A/AppServerSupport\n 0x7fff2b6df000 - 0x7fff2b6f0fff libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <F0974976-30C0-35EB-92F1-B4CF1E974F11> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib\n 0x7fff2b6f1000 - 0x7fff2b6f3fff libspindump.dylib (295.1) <3B4701CB-8F66-3E50-A38A-BEEC992AAC31> /usr/lib/libspindump.dylib\n 0x7fff2b6f4000 - 0x7fff2b7b4fff com.apple.Heimdal (4.0 - 2.0) <69768234-4F4F-3AB6-B116-4AE249E6417A> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff2b7b5000 - 0x7fff2b7cffff com.apple.login (3.0 - 3.0) <B9BEC3A1-688C-3999-B705-2D50B8756E62> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff2b94f000 - 0x7fff2b952fff libodfde.dylib (26) <47160F56-2A36-3147-B721-279BE2F8B4A6> /usr/lib/libodfde.dylib\n 0x7fff2b953000 - 0x7fff2b9bdfff com.apple.bom (14.0 - 233) <F4B7C353-8A65-3B54-9E01-2C93CB3F55A3> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom\n 0x7fff2b9be000 - 0x7fff2ba08fff com.apple.AppleJPEG (1.0 - 1) <7F3819DE-BCE7-32B7-BB33-10C1DB2BA512> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff2ba09000 - 0x7fff2bae7fff libJP2.dylib (2130.3.5) <2DFE6642-4309-30BD-A402-F93E28F1F065> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff2bae8000 - 0x7fff2baebfff com.apple.WatchdogClient.framework (1.0 - 98.80.2) <C257C950-F430-3762-BC72-15D314D99556> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient\n 0x7fff2baec000 - 0x7fff2bb1ffff com.apple.MultitouchSupport.framework (4400.28 - 4400.28) <4243F7DC-7EB9-3750-BE36-527B0BADF36C> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff2bb20000 - 0x7fff2bc72fff com.apple.VideoToolbox (1.0 - 2765.6.4.2) <425BDD2D-6C26-3D09-AD9F-942EA387B2A4> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff2bc73000 - 0x7fff2bca5fff libAudioToolboxUtility.dylib (1180.25) <83DBFA98-F85B-3B63-B58F-C9989BAC9611> /usr/lib/libAudioToolboxUtility.dylib\n 0x7fff2bca6000 - 0x7fff2bcccfff libPng.dylib (2130.3.5) <9046A7B7-6C31-32C5-B610-6AEA6F6B2D48> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff2bccd000 - 0x7fff2bd2cfff libTIFF.dylib (2130.3.5) <CAAF5746-3171-38B1-9722-8CB9B650C627> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff2bd2d000 - 0x7fff2bd49fff com.apple.IOPresentment (54 - 37) <5AD7B6E0-1744-3C8D-8A95-FE425DEA005C> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff2bd4a000 - 0x7fff2bd50fff com.apple.GPUWrangler (6.2.2 - 6.2.2) <60363868-111B-36CF-9CDF-2643DF82002D> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff2bd51000 - 0x7fff2bd54fff libRadiance.dylib (2130.3.5) <71EBA416-A317-380A-984A-F6B0A0695A65> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff2bd55000 - 0x7fff2bd5afff com.apple.DSExternalDisplay (3.1 - 380) <010F8260-BC46-361E-BE59-540F765EFE74> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff2bd5b000 - 0x7fff2bd7ffff libJPEG.dylib (2130.3.5) <4BFCC012-7CDD-320D-845D-E475243D3ECE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff2bd80000 - 0x7fff2bdaffff com.apple.ATSUI (1.0 - 1) <6C45783D-CF90-3F11-BA86-92D31A9B68CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI\n 0x7fff2bdb0000 - 0x7fff2bdb4fff libGIF.dylib (2130.3.5) <0C91C2A9-5D71-3042-A0D2-AA8F1F09012E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff2bdb5000 - 0x7fff2bdbefff com.apple.CMCaptureCore (1.0 - 80.20.5) <2B7E468B-D901-3EA9-85CF-82FD753785BD> /System/Library/PrivateFrameworks/CMCaptureCore.framework/Versions/A/CMCaptureCore\n 0x7fff2bdbf000 - 0x7fff2be06fff com.apple.print.framework.PrintCore (16 - 531) <DB939B2B-D47D-3035-8C02-01006D21C5A7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff2be07000 - 0x7fff2bed3fff com.apple.TextureIO (3.10.9 - 3.10.9) <50BA07A4-02E8-38EE-B0B9-B12C277B563B> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff2bed4000 - 0x7fff2bedcfff com.apple.InternationalSupport (1.0 - 60) <DE997943-6AD5-32DA-B48E-78170C1EAA7B> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport\n 0x7fff2bedd000 - 0x7fff2bf58fff com.apple.datadetectorscore (8.0 - 674) <A4EBFF22-F861-321A-AF28-1DB8ECB9A4FF> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff2bf59000 - 0x7fff2bfb7fff com.apple.UserActivity (435 - 435) <12250395-D660-3CC1-81DB-565340F2651B> /System/Library/PrivateFrameworks/UserActivity.framework/Versions/A/UserActivity\n 0x7fff2bfb8000 - 0x7fff2c723fff com.apple.MediaToolbox (1.0 - 2765.6.4.2) <C8645EA0-643D-38CF-AA88-3253339192B1> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff2cbdd000 - 0x7fff2cc05fff com.apple.locationsupport (2420.12.16 - 2420.12.16) <63AB1284-8E33-3E9D-A857-9370F492B343> /System/Library/PrivateFrameworks/LocationSupport.framework/Versions/A/LocationSupport\n 0x7fff2cc06000 - 0x7fff2cc37fff libSessionUtility.dylib (76.7) <6AAD02A0-9590-3CED-9568-36E05C59AA2B> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib\n 0x7fff2cc38000 - 0x7fff2cd68fff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <8E53C25F-9FE2-372E-8374-6A598D72C4C1> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff2cd69000 - 0x7fff2cdd0fff com.apple.audio.AudioSession (1.0 - 76.7) <F696F4EC-9344-3C85-941E-6E5EF5CEF585> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession\n 0x7fff2cdd1000 - 0x7fff2cde3fff libAudioStatistics.dylib (25.4) <303533DD-D001-3CE8-A5A4-EC29F464FC3A> /usr/lib/libAudioStatistics.dylib\n 0x7fff2cde4000 - 0x7fff2cdf3fff com.apple.speech.synthesis.framework (9.0.51.2 - 9.0.51.2) <14F3382B-2B8E-31E5-8C73-73F0B8DD05F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff2cdf4000 - 0x7fff2ce5ffff com.apple.ApplicationServices.ATS (377 - 516) <3DD60168-A0F3-3388-8DDE-69F81280AE91> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff2ce60000 - 0x7fff2ce78fff libresolv.9.dylib (68) <7B043B4A-71CE-3F6E-91F0-CBBED47A9EA9> /usr/lib/libresolv.9.dylib\n 0x7fff2ce79000 - 0x7fff2ce8cfff libsasl2.2.dylib (214) <7EE1EE13-9D86-3612-A6BC-3E6B5D578267> /usr/lib/libsasl2.2.dylib\n 0x7fff2cfab000 - 0x7fff2d08afff libSMC.dylib (20) <B207FDFF-8D80-3800-B968-03C718FFBF3F> /usr/lib/libSMC.dylib\n 0x7fff2d08b000 - 0x7fff2d0eafff libcups.2.dylib (494.1) <CDF6F483-017E-3DED-B107-C50FC3CADD65> /usr/lib/libcups.2.dylib\n 0x7fff2d0eb000 - 0x7fff2d0fafff com.apple.LangAnalysis (1.7.0 - 254) <14703020-3124-3C62-A9DB-6DD28024CD42> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff2d0fb000 - 0x7fff2d105fff com.apple.NetAuth (6.2 - 6.2) <D40BF56F-DF5F-3ECB-AAC2-FE6F13E9D120> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff2d106000 - 0x7fff2d10dfff com.apple.ColorSyncLegacy (4.13.0 - 1) <F3AEB77A-456F-3F9F-98CC-3E29ABAF5D0C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff2d10e000 - 0x7fff2d119fff com.apple.QD (4.0 - 416) <F65D0944-C775-33FB-A345-C046789667B7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff2d11a000 - 0x7fff2d788fff com.apple.audio.AudioResourceArbitration (1.0 - 1) <6A293E4C-1E2D-36DA-B416-FBED7286CD6E> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration\n 0x7fff2d789000 - 0x7fff2d795fff com.apple.perfdata (1.0 - 67.40.1) <A9D2E8CD-9D74-304E-BD99-A7704F3CD38B> /System/Library/PrivateFrameworks/perfdata.framework/Versions/A/perfdata\n 0x7fff2d796000 - 0x7fff2d7a4fff libperfcheck.dylib (41) <5AFDC5C6-EBB6-33E4-9215-1AACE6C6F6EE> /usr/lib/libperfcheck.dylib\n 0x7fff2d7a5000 - 0x7fff2d7b4fff com.apple.Kerberos (3.0 - 1) <02FFA3CA-F8AF-3211-9159-36BC29612650> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff2d7b5000 - 0x7fff2d804fff com.apple.GSS (4.0 - 2.0) <5D06022E-C963-390A-9487-90BD1B61BC20> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff2d805000 - 0x7fff2d815fff com.apple.CommonAuth (4.0 - 2.0) <C4418557-FA52-3B80-804F-2BC7AF760FD6> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff2d816000 - 0x7fff2d83cfff com.apple.MobileAssets (1.0 - 659.60.1) <62F25002-C547-3C6C-87D1-0824DD058C82> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff2d86a000 - 0x7fff2d88cfff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <6F4B051F-BC33-3880-81B2-5C62DABFF02D> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff2d88d000 - 0x7fff2d895fff com.apple.CorePhoneNumbers (1.0 - 1) <AA493452-21D3-3EC6-953C-42DBF75F4EB9> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff2d9ea000 - 0x7fff2d9eafff liblaunch.dylib (2038.80.3) <C7C51322-8491-3B78-9CFA-2B4753662BCF> /usr/lib/system/liblaunch.dylib\n 0x7fff2e1e5000 - 0x7fff2e32cfff com.apple.Sharing (1579 - 1579) <4925CAB3-09C0-373C-A5D3-9BB5FF025A4F> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff2e32d000 - 0x7fff2e44dfff com.apple.Bluetooth (8.0.3 - 8.0.3d9) <C6FFFDA7-CD91-339A-8529-7D094338949D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff2e44e000 - 0x7fff2e462fff com.apple.AppContainer (4.0 - 509.60.2) <F294CD92-94FA-3D7D-9E59-AA5544504264> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer\n 0x7fff2e463000 - 0x7fff2e466fff com.apple.SecCodeWrapper (4.0 - 509.60.2) <1BEC89D6-6AC8-36C2-89AE-41662D14DC50> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper\n 0x7fff2e467000 - 0x7fff2e4c0fff com.apple.ProtectedCloudStorage (1.0 - 1) <88EF8B12-617E-316C-9036-18357E27BC0A> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage\n 0x7fff2e714000 - 0x7fff2fc0afff com.apple.GeoServices (1.0 - 1757.23.11.29.3) <72B73209-98B3-3E90-8D5D-B69C81784E5D> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices\n 0x7fff2fc0b000 - 0x7fff2fc16fff com.apple.DirectoryService.Framework (11.2 - 230.40.1) <4DB85BA3-9323-304B-BDC3-6E13B9AAA1C2> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService\n 0x7fff2fc17000 - 0x7fff2fc42fff com.apple.RemoteViewServices (2.0 - 163) <661A448B-2901-33CD-B13C-362D61AFD998> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff2fc43000 - 0x7fff2fc52fff com.apple.SpeechRecognitionCore (6.1.12 - 6.1.12) <B24969AE-43BA-36C2-80F9-2CBBC3F63CC8> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff2fc53000 - 0x7fff2fc5afff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <8C33ECFF-2FBF-30FF-87EA-32A508860543> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff2fe9e000 - 0x7fff2fe9efff libsystem_product_info_filter.dylib (8.40.1) <20310EE6-2C3F-361A-9ECA-4223AFC03B65> /usr/lib/system/libsystem_product_info_filter.dylib\n 0x7fff2ff79000 - 0x7fff2ff79fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <8CD6F55A-8E4F-3653-A367-427D0ED3DD16> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff2ffa0000 - 0x7fff2ffa0fff com.apple.CoreServices (1122.11 - 1122.11) <E59859C6-7221-3324-BB58-F910B2199959> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3026e000 - 0x7fff3026efff com.apple.Accelerate (1.11 - Accelerate 1.11) <2423F0F6-A3A4-37AB-971E-FCFC7645D282> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff302af000 - 0x7fff302bafff com.apple.MediaAccessibility (1.0 - 130) <264B30DF-646A-30EC-98B6-20429E9718CB> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff302bb000 - 0x7fff302dafff com.apple.networking.AlgosScoreFramework (1.0 - 1) <8713D2A4-ECB6-3B96-BE39-F47851EEF900> /System/Library/PrivateFrameworks/AlgosScoreFramework.framework/Versions/A/AlgosScoreFramework\n 0x7fff302db000 - 0x7fff302dffff com.apple.AppleSRP (5.0 - 1) <3BF95CAF-2EC5-393A-95B7-429C0C5F8F13> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP\n 0x7fff302e0000 - 0x7fff302ebfff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <D73E7719-09C8-30E6-B92D-AFC1BB356D92> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon\n 0x7fff302ec000 - 0x7fff30323fff com.apple.framework.SystemAdministration (1.0 - 1.0) <9275DC16-B898-326A-B6AD-6CDF34F0CF77> /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration\n 0x7fff30ae5000 - 0x7fff30b47fff com.apple.CoreBluetooth (1.0 - 1) <B88DEE8B-6268-36BA-BF6C-088F3BD8C652> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff30b48000 - 0x7fff30b51fff com.apple.SymptomDiagnosticReporter (1.0 - 79.40.12) <83B5E330-D786-34D2-AEE6-6F7B34D6FE9C> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter\n 0x7fff30b52000 - 0x7fff30b65fff com.apple.PowerLog (1.0 - 1) <3A076F54-AE8C-3550-8262-5655B5026489> /System/Library/PrivateFrameworks/PowerLog.framework/Versions/A/PowerLog\n 0x7fff30b66000 - 0x7fff30b72fff com.apple.AppleIDAuthSupport (1.0 - 1) <964BA0DB-E86E-3F81-BB82-CC27184B6D20> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff30b73000 - 0x7fff30c1bfff com.apple.DiscRecording (9.0.3 - 9030.4.5) <2B9AA549-63FD-36BB-AE05-ABD5DAC41279> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording\n 0x7fff30c1c000 - 0x7fff30c4ffff com.apple.MediaKit (16 - 927.40.2) <D1056292-E38F-313F-B202-EFD871195729> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit\n 0x7fff30c50000 - 0x7fff30d3bfff com.apple.DiskManagement (14.0 - 1733.80.1) <9281E3F8-EAFE-3367-B7D5-23687AA6EB70> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement\n 0x7fff30d3c000 - 0x7fff310f6fff com.apple.CoreAUC (322.2.0 - 322.2.0) <DAE981E0-5FED-39FD-8443-BD91D6957901> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff310f7000 - 0x7fff310fafff com.apple.Mangrove (1.0 - 25) <61919815-50C9-3358-836F-B81ED66CCD84> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff310fb000 - 0x7fff31128fff com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B123866C-3945-37E7-92EF-BE36AEDD620D> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff31129000 - 0x7fff31249fff com.apple.FileProvider (326.3 - 326.3) <C5007E6E-897B-308F-B173-4F5C6BF3968D> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider\n 0x7fff3124a000 - 0x7fff3126dfff com.apple.GenerationalStorage (2.0 - 322) <974A1465-7AA4-347E-8606-CF35160FFA92> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff31ac0000 - 0x7fff31afffff com.apple.AppleVPAFramework (3.21.1 - 3.21.1) <4E96F781-3689-3086-9DF3-60F20487FB9E> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA\n 0x7fff31bd0000 - 0x7fff31c0cfff com.apple.DebugSymbols (195.1 - 195.1) <12A5A6E2-6C84-3FCA-9927-8B9E241C607F> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff31c0d000 - 0x7fff31ccafff com.apple.CoreSymbolication (12.2 - 64541.4) <F1A41B4E-671A-335E-8AE0-B99688F255C8> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff31ccb000 - 0x7fff31cd4fff com.apple.CoreTime (284) <D80E792D-33D1-3D07-B39F-F0A1A7F74E24> /System/Library/PrivateFrameworks/CoreTime.framework/Versions/A/CoreTime\n 0x7fff32b61000 - 0x7fff32bc4fff com.apple.framework.Apple80211 (17.0 - 1728) <A62689A7-7C22-33B3-90FA-730E4AAEE5B5> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff32bc5000 - 0x7fff32d17fff com.apple.CoreWiFi (3.0 - 341) <F3D8F158-611A-3A5E-9F1D-E5FC273A4C74> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff32d31000 - 0x7fff32d68fff com.apple.LDAPFramework (2.4.28 - 194.5) <246874E6-4FD1-35A5-A039-4141999D8CD6> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP\n 0x7fff32d69000 - 0x7fff32d6afff com.apple.TrustEvaluationAgent (2.0 - 35) <6FEF60A0-F80F-34E3-8845-FEEC92840920> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff32d6b000 - 0x7fff32e6efff libcrypto.44.dylib (56.60.2) <7D8D4B1B-625D-3D00-A626-C21AFEE0462E> /usr/lib/libcrypto.44.dylib\n 0x7fff32e6f000 - 0x7fff32e9cfff libssl.46.dylib (56.60.2) <E02ED3C9-4956-39C4-AF0A-B541EEDD3F1B> /usr/lib/libssl.46.dylib\n 0x7fff32e9d000 - 0x7fff32f4cfff com.apple.DiskImagesFramework (595.40.1 - 595.40.1) <3139EC22-A8F2-3F26-8953-7961C97E7CEF> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages\n 0x7fff32f84000 - 0x7fff32f93fff com.apple.xpc.RemoteServiceDiscovery (1.0 - 2038.80.3) <78AF1606-37D8-3424-92AE-071A9F43AA0F> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/RemoteServiceDiscovery\n 0x7fff32f94000 - 0x7fff32fabfff com.apple.xpc.RemoteXPC (1.0 - 2038.80.3) <C4BFF5FC-FC9C-3161-9612-7070EDAE9989> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC\n 0x7fff32ff3000 - 0x7fff32ff6fff com.apple.help (1.3.8 - 71) <6074D81C-4507-35A6-88D7-D82309F81587> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32ff7000 - 0x7fff32ffefff com.apple.EFILogin (2.0 - 2) <B06CCD1C-A4D1-34D2-89C5-0DB69FE65234> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin\n 0x7fff32fff000 - 0x7fff3300afff libcsfde.dylib (554) <9CDB9580-DD1C-347E-91C5-6D92D96F52F5> /usr/lib/libcsfde.dylib\n 0x7fff3300b000 - 0x7fff33070fff libcurl.4.dylib (121.40.2) <77010EA9-4AD1-3F4A-B3EF-2FFE739FB349> /usr/lib/libcurl.4.dylib\n 0x7fff33071000 - 0x7fff33078fff com.apple.LoginUICore (4.0 - 4.0) <7225326A-7704-362D-B64E-4ABF4A221F88> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore\n 0x7fff33238000 - 0x7fff33238fff com.apple.ApplicationServices (48 - 50) <42B48E32-1918-3178-8DE0-E8126B9EC088> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff33539000 - 0x7fff33539fff libHeimdalProxy.dylib (79) <85526E13-1E48-377A-A700-EE3F5648A6E3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib\n 0x7fff335ec000 - 0x7fff335ecfff com.apple.audio.units.AudioUnit (1.14 - 1.14) <8CF768B8-836B-3DA8-9F0A-8CF840348202> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff33611000 - 0x7fff33653fff com.apple.StreamingZip (1.0 - 1) <157C7AC0-9F73-3FF5-A276-54EC3CAE958A> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff33696000 - 0x7fff3369bfff com.apple.PushKit (1.0 - 1) <4D0A6539-611C-3B9C-A67D-D45CDEEC8CDC> /System/Library/Frameworks/PushKit.framework/Versions/A/PushKit\n 0x7fff3369c000 - 0x7fff336d2fff com.apple.C2 (1.3 - 569) <817D8F9D-1801-3E6D-846A-7002174B59CB> /System/Library/PrivateFrameworks/C2.framework/Versions/A/C2\n 0x7fff33705000 - 0x7fff33f12fff com.apple.vision.EspressoFramework (1.0 - 256.2.2) <70E23334-A179-3671-A930-A7AB9EC77BDD> /System/Library/PrivateFrameworks/Espresso.framework/Versions/A/Espresso\n 0x7fff33f13000 - 0x7fff33f2afff com.apple.ANEServices (4.52 - 4.52) <50EF6199-93EF-3227-B64A-313BC1DF41AE> /System/Library/PrivateFrameworks/ANEServices.framework/Versions/A/ANEServices\n 0x7fff342c7000 - 0x7fff3458afff com.apple.spotlight.index (10.7.0 - 2150.7.5) <0056D8F9-D6CF-3586-974C-80902DF8952A> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex\n 0x7fff345a3000 - 0x7fff345f3fff com.apple.ChunkingLibrary (334 - 334) <CBEBDC8A-CCE4-3A21-915C-D2F3FB20B900> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff34ebf000 - 0x7fff34ed5fff com.apple.CoreML.AppleNeuralEngine (1.0 - 1) <A2E78405-4382-3A23-8638-56E1A5D14543> /System/Library/PrivateFrameworks/AppleNeuralEngine.framework/Versions/A/AppleNeuralEngine\n 0x7fff3503b000 - 0x7fff3503efff com.apple.Cocoa (6.11 - 23) <B0F6AF8E-B85C-3C5C-9812-9CD8BC07ADB2> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff36482000 - 0x7fff3649dfff com.apple.openscripting (1.7 - 190) <E3815884-A406-3CF6-82C1-BEDC772A9081> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff3649e000 - 0x7fff364a1fff com.apple.securityhi (9.0 - 55008) <F7E1C957-65AF-39E5-8BBA-9D7C7C9D30B6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff364a2000 - 0x7fff364a5fff com.apple.ink.framework (10.15 - 227) <E3D118A5-7A62-3893-ADAC-E0A9F45314C9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff364a6000 - 0x7fff364a9fff com.apple.CommonPanels (1.2.6 - 101) <F46676FA-60F3-30CC-BF48-F5BB6E66E576> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff364aa000 - 0x7fff364b1fff com.apple.ImageCapture (1708.1 - 1708.1) <AC709D2F-7C16-3645-BB20-19DD1414E210> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff3949f000 - 0x7fff394a2fff com.apple.OSAServicesClient (1.0 - 1) <201350F5-56C4-3342-AD10-4BE20772C52B> /System/Library/PrivateFrameworks/OSAServicesClient.framework/Versions/A/OSAServicesClient\n 0x7fff3c090000 - 0x7fff3c24bfff libFosl_dynamic.dylib (200) <83EE0261-E5F6-3607-8897-B03B2B954B15> /usr/lib/libFosl_dynamic.dylib\n 0x7fff3d1a8000 - 0x7fff3d1abfff com.apple.print.framework.Print (15 - 271) <F3F40AFD-1743-34E6-8BD3-6A577E3BD590> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff3d1ac000 - 0x7fff3d1affff com.apple.Carbon (160 - 164) <7395C7E9-AE3B-3547-8773-4F3A70B241AA> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff3d434000 - 0x7fff3d453fff com.apple.private.SystemPolicy (1.0 - 1) <29F5E3FE-CF12-3242-9FD3-4950DA38E4D0> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy\n 0x7fff3d600000 - 0x7fff3d61dfff com.apple.sidecar-core (1.0 - 228) <78195DB7-D409-3B46-B8C8-3B70538D3CDC> /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore\n 0x7fff3dd7d000 - 0x7fff3dd88fff com.apple.MallocStackLogging (1.0 - 1) <507894FA-6738-372B-9A10-C38AFC9DA079> /System/Library/PrivateFrameworks/MallocStackLogging.framework/Versions/A/MallocStackLogging\n 0x7fff3dd9e000 - 0x7fff3ddb0fff libmis.dylib (274.60.2) <6C720DC2-E50E-3A8D-8494-F8C007DF8DF4> /usr/lib/libmis.dylib\n 0x7fff3ddb1000 - 0x7fff3ddb4fff com.apple.gpusw.GPURawCounter (17.3 - 12.0) <070CF9B7-EE89-39F3-B0F6-26D4974AD3A8> /System/Library/PrivateFrameworks/GPURawCounter.framework/Versions/A/GPURawCounter\n 0x7fff3e2c0000 - 0x7fff3e2d1fff com.apple.sidecar-ui (1.0 - 228) <E0B4A84C-7E8D-338B-8269-DAA5AE1ED094> /System/Library/PrivateFrameworks/SidecarUI.framework/Versions/A/SidecarUI\n 0x7fff4153a000 - 0x7fff41569fff libncurses.5.4.dylib (57) <CAD79205-84C0-3731-AED8-EDEF51ACC872> /usr/lib/libncurses.5.4.dylib\n 0x7fff4156a000 - 0x7fff41573fff com.apple.IOAccelMemoryInfo (1.0 - 1) <544B95BE-810E-3D94-AEB1-D5C117D946D7> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff419aa000 - 0x7fff419c8fff libCGInterfaces.dylib (544.2) <2BC461CE-B7FA-33F3-A36B-64F54FB371B5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff43fb8000 - 0x7fff44231fff com.apple.RawCamera.bundle (9.10.0 - 1430) <3E7403EB-156C-36C7-93AD-1356447D5310> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff46cb9000 - 0x7fff46cc4fff libGPUSupportMercury.dylib (18.1.1) <1321060E-8F56-3917-8F4D-510A4DB45798> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff48327000 - 0x7fff48376fff com.apple.osanalytics.OSAnalytics (1.0 - 1) <CADD88A2-87A8-3879-8759-D3C112A6844F> /System/Library/PrivateFrameworks/OSAnalytics.framework/Versions/A/OSAnalytics\n 0x7fff4c3d2000 - 0x7fff4c3d5fff com.apple.FinderSyncPriv (1.3 - 1350.2.10) <121C1E64-B0BE-389F-A35D-DD44D84129E8> /System/Library/PrivateFrameworks/FinderSyncPriv.framework/Versions/A/FinderSyncPriv\n 0x7fff522ff000 - 0x7fff52391fff com.apple.Symbolication (12.2 - 64541.7.1) <FA39B702-6E08-3F11-953F-5EC1EFB993BB> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff564d5000 - 0x7fff564d8fff com.apple.ForceFeedback (1.0.6 - 1.0.6) <8782199E-5556-3FB6-87E8-03472B480BAA> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff5eada000 - 0x7fff5ef6afff com.apple.driver.AppleIntelKBLGraphicsMTLDriver (16.1.12 - 16.0.1) <2B7EEE40-F4BD-32CD-B5A3-51F67B57AA69> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver\n 0x7fff5ef6b000 - 0x7fff5f97efff libSC.dylib (4.2.15) <86667FD2-E9BB-39FE-82E9-7B1F0230A922> /System/Library/Extensions/AMDShared.bundle/Contents/PlugIns/libSC.dylib\n 0x7fff5fcc7000 - 0x7fff60caafff com.apple.driver.AppleIntelKBLGraphicsGLDriver (16.1.12 - 16.0.1) <7E0C9E81-E41B-3D24-AB0B-84295B61FADF> /System/Library/Extensions/AppleIntelKBLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsGLDriver\n 0x7fff6a490000 - 0x7fff6a494fff libmetal_timestamp.dylib (31001.161) <DF0A6F36-E486-3656-A6F2-9BA9A0CF2159> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libmetal_timestamp.dylib\n 0x7fff6c8fe000 - 0x7fff6c904fff libCoreFSCache.dylib (177.22) <44489BD1-3963-35DF-86F1-DE95778AC0DB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff6c905000 - 0x7fff6c909fff libCoreVMClient.dylib (177.22) <989F6CBF-CCEF-340D-9CB5-EC4133707040> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff6c90a000 - 0x7fff6c919fff com.apple.opengl (18.1.1 - 18.1.1) <F70AF1B3-D17A-3A0E-A8AC-9D45C5B52BA9> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff6c91a000 - 0x7fff6c91cfff libCVMSPluginSupport.dylib (18.1.1) <AF77D964-9A4C-3690-AF62-4E05825DC9BF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff6c91d000 - 0x7fff6c925fff libGFXShared.dylib (18.1.1) <45A1FFDC-03B7-3D64-AFAF-16D321B53D28> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff6c926000 - 0x7fff6c959fff libGLImage.dylib (18.1.1) <16D10CE1-C2A1-3E24-A617-766CB6E9133C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff6c95a000 - 0x7fff6c996fff libGLU.dylib (18.1.1) <F0DD35B5-3692-3BE5-AD3D-4F6B237EF6AD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff6c997000 - 0x7fff6cb2bfff libGLProgrammability.dylib (18.1.1) <F8A8DACC-1932-3DEF-A269-396E4981B4D0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff6cb2c000 - 0x7fff6cb36fff libGL.dylib (18.1.1) <68ABAADE-2DB4-3412-9F36-CA1AEAC8E9F6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff6cb37000 - 0x7fff6ccb2fff GLEngine (18.1.1) <2C9F1F38-F0CA-3416-9A6E-C0E3F40C3AAC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff6ccb3000 - 0x7fff6ccdcfff GLRendererFloat (18.1.1) <A66AB383-EE4C-325C-8115-78F2B3FFECC7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff6df6d000 - 0x7fff6dfc5fff com.apple.opencl (4.5 - 4.5) <40B70A3B-D981-3E4A-9BEC-F22EF84118F5> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff6eee8000 - 0x7fff6ef37fff ATIRadeonX6000SCLib.dylib (4.2.15) <E3B416D3-3876-3218-A68F-A745B103F160> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/ATIRadeonX6000SCLib.dylib\n 0x7fff6f857000 - 0x7fff6f879fff com.apple.audio.OpenAL (1.8 - 1.8) <43D5D99A-39C3-30F3-BB9E-5B83EEA9DAFD> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff78132000 - 0x7fff78139fff libRosetta.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/libRosetta.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 4\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 55959\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)\nWritable regions: Total=8.8G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8.8G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 4 \nActivity Tracing 256K 1 \nCG backing stores 3456K 6 \nCG image 1180K 10 \nCoreAnimation 84K 9 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreServices 36K 1 \nCoreUI image data 904K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 6.8G 341 \nMALLOC guard page 48K 10 \nMALLOC_MEDIUM (reserved) 1.5G 16 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 164K 41 \nStack 73.8M 42 \nVM_ALLOCATE 92.1M 777 \n__CTF 759 1 \n__DATA 89.4M 371 \n__DATA_CONST 17.6M 215 \n__DATA_DIRTY 918K 116 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 545.7M 25 \n__OBJC_RO 60.5M 1 \n__OBJC_RW 2449K 2 \n__TEXT 461.6M 370 \n__UNICODE 588K 1 \nmapped file 260.7M 39 \nshared memory 40K 4 \n=========== ======= ======= \nTOTAL 10.2G 2421 \nTOTAL, minus reserved VM space 8.3G 2421 \n\nModel: MacBookPro16,1, BootROM 1554.80.3.0.0 (iBridge: 18.16.14347.0.0,0), 8 processors, 8-Core Intel Core i9, 2,3 GHz, 32 GB, SMC \nGraphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin\nGraphics: kHW_AMDRadeonPro5500MItem, AMD Radeon Pro 5500M, spdisplays_pcie_device, 8 GB\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Sep 11 2020 17:01:15 version 9.30.440.2.32.5.61 FWID 01-1d69e4b4\nBluetooth: Version 8.0.3d9, 3 services, 25 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.1 Bus\nUSB Device: USB Receiver\nUSB Device: Apple T2 Bus\nUSB Device: Composite Device\nUSB Device: Touch Bar Backlight\nUSB Device: Touch Bar Display\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: Headset\nUSB Device: Ambient Light Sensor\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: Apple T2 Controller\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\n```\n\n- Random\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", "Use after free: Baking Rigid Body physics causes instant crash\nOperating system: macOS 10.15.7\nGraphics card: AMD Radeon Pro 5500M 4 GB / Intel UHD Graphics 630 1536 MB\n\nBroken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, 2.93.0 Beta, branch: master, commit date: 2021-04-28 22:25, \nbroken: f7b22fc3d27113715e8726c69ab3264e1d487439\nWorked: \n\nBaking the Rigid Body world physics causes Blender to crash either instantly, or after baking less than 100 frames (it varies). Interestingly, a friend with the PC version of 2.92 says the project works fine, no crashes whatsoever.\n\nOpen the project. Make sure Allow Negative Frames is on under Preferences/Animation. Go to the Rigid Body World and hit bake.\n\n[physics test b.blend](physics_test_b.blend)\nAsan report: [T88113_asan_report.txt](T88113_asan_report.txt)" ]

[ "Rigid Body Simulations Crash to Desktop During Real-Time Playback\nOperating system: Windows-10-10.0.22000-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\nWorked: Hasn't worked in any 3.X releases, still crashes in 3.2 alpha. \n\nBlender crashes to desktop when Rigid Body simulations are played back in real-time (no baking). Crashes are hard to reproduce as they typically seem to happen at random, but below method seems to work reliably. I am experiencing these crashes on 3 different workstations, all with different hardware configs (all using Nvidia 3080 cards). Possibly related to using UNDO during real-time simulation playback?\n\n[rigid body crash.blend](rigid_body_crash.blend)\nIn attached Blend File:\n1) Drag playhead to Frame 0 and begin playback of simulation by pressing Spacebar. Let simulation play on a constant loop.\n2) While playback is running, Go to Scene Properties, and under \"Rigid Body World\" change simulation speed to \"10\". \n3) Hit CTRL-Z to undo, and then click frame 0 on the timeline to jump playhead to frame 0 (don't stop playback-- keep it looping during process). \n4) Repeat steps 2-3 until crash (usually only takes a few iterations before crash)", "Rigidbody crash undoing while animation plays (which was started at frame 1 or below)\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[animation_john2.blend](animation_john2.blend)\n\nOperating system: Windows 10\nGraphics card: Nvidia 2070 Super\n\nWorked: -\n\nBlender crashes when object is rotated to a steep vertical angle and animation player is run.\n\nFor animation_john2.blend\n- Play Animation\n- Select a bone (could be any other operator as well I think)\n- Undo (this will also jump back to frame 0 -- where we started -- which is the important part, starting animation at frame 2 or higher does not result in the crash)\n- Redo\n\nRepeat until crash. Occurs between 2-5 repeats.\n\nAlso occurs at other similar high angles." ]

[ "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).", "Surface Deform Modifier invokes \"Invalid surface UVs\" error when applied to Hair\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 770 Intel 4.5.0 - Build 31.0.101.3959\n\nBroken: version: 3.5.1\n\nWhen adding Fur to the mesh in the example file, the Surface Deform modifier produces the error message \"Invalid surface UVs on x curves\". This also appears related the rippling visibility of the hair an animation (see also [#109285](109285#issuecomment-965921))\n\n\n1. Load the attached file and press play\n2. Note the \"Invalid surface UVs on x curves\" error in the Surface Deform modifier\n3. Stop the playback, and note that the figure in the error corresponds with the appearance of hairs on the surface\n4. Select the Body object and Add > Curve > Fur\n5. Observe the same error in the newly added Surface Deform modifier\n\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", "Constrain axis always draws on top [covers mesh in unfavorable ways]\nThe mesh outline is not visible when extruding or moving along the axes. The axes overlap the faces of the mesh themselves, and because of this, it is not convenient to precisely position the extruded faces.\nIt exists on all versions of the 2.8x blender.\n\nTo repeat the problem, you can select an edge in the editing mode and simply drag along the y axis. In this case, the contour will not be visible by how much it is moved from its actual position.\n\n\n\nWith the same action in 2.79, I see black the contours of the mesh as far as it changes when moving.\nBring it back as it was in 2.79", "Multi-Object-Mode: Operators that need refactor on their logic\nSome operators are working for multiple-object editing however are still not fully benefiting from it.\nThe most common case is that the operator works but only if all the objects have the same transformation matrix.\n\n* **~~MESH_OT_select_similar~~** (SIMEDGE_FACE_ANGLE, SIMFACE_AREA, SIMFACE_PERIMETER). 0c1934f3c2\n\n* **MESH_OT_knife_project** and **MESH_OT_knife_tool**.\nNeed to convert the code from screen space to world space. More details on [D3637](D3637).\n\n* **UV_OT_weld** (UV_STRAIGHTEN, UV_STRAIGHTEN_X, UV_STRAIGHTEN_Y).\nThe current logic to determine the first and last selected vertex is not very compatible with multi-object. We should be able to select vertices from different objects, and use their position to determine the line extremes.\n\n* **LATTICE_OT_flip**\nThe axis need to be in world space, not local space.\n\n* **~~CURVE_OT_select_similar~~** (SIMCURHAND_DIRECTION). ab77f5b5fe\nNeed to calculate direction taking scale into consideration.", "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", "UV: Modified Edges UV overlay don't show on generated Mesh from Geometry Nodes\nBroken: version: 3.6.0\n\n\"Modified Edges\" UV Option does not work when there is Join Node or primitives is used to generate geometry.\n\nIn setup like this, where we generate UVs in GN, and have \"Modified Edges\" overlay work correctly.\n\n\n\nWhen we generate geometry eg. by using Join Node, or Primitives. Overlay no longer works (even in UV sync mode where all UVs should be shown)\n\n\n\n\nI'm not sure if its desired behavior because eg. some setup do work when we modify and not generate new geometry.\n\n\n--\n\n(that's the overlay if someone is not aware of its existence :p)\n\n\n- Open attached .blend file. (Note that the UV for \"Modified Edges\" is showing as expected)\n- Unmute `Join Geometry` node. (UV for \"Modified Edges\" no longer appears)", "Transform: Tilt values in curves are not transformed\n2.8, 2.81\n\nWhen mirroring curves, tilt values are not mirrored.\n\nIn edit mode, MIRROR(or SCALE -1) dose not change tilt values.\nSo I can not get mirrored result (bebel geometry).\n\n(In object mode, I can get mirrored 2 curves by MIRROR(or SCALE -1),\nBut JOIN the two curves results not mirrored tilt effect.)\n\nOpen:\n[mirrored_curve.blend](mirrored_curve.blend)\n* The file contains 2 splines. One is a scaled duplicate of the other.\n* Note that the tilt of the corresponding point remains the same on both splines.", "Regression: Curve wire line not displayed in edit mode when it has evaluated mesh/point/volume\nBroken: 3.0, 3.1, 3.2\nCaused by b9febb54a4\n\nThe original line for edit mode curves is not displayed in edit mode .\n\nThis change only applies when the curve is changed during evaluation, for example, when it is replaced by an evaluated \"tube\" mesh, or points, or a volume, etc.\n\n| Before | After |\n| -- | -- |\n|  |  |\n(Ignore the change in lightness there, it's just a different UI scale)", "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", "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.", "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", "different Skin Modifier outputs for same mesh\nWindows 10\nNvidia Quadro 600\n\nBroken: 1422f0d\n\nThe skin modifier produces different meshes on the default cube.\n\n\nTrigger the skin modifier to update by doing the same thing I do in the .gif\n\n[skin_modifier_bug.blend](skin_modifier_bug.blend)\n\nNote: this only seems to happen when the edges are orthogonal. When I move one point, the problem doesn't appear on this and connected points.\n\n(Originially reported here: 576)\n", "Layer Switching Shortcut Inconsistency\nThere is some improvement concept for collections shortcuts.\nCurrently, 1234 buttons shows a collection, but sending objects requires name in menu (M - \"Collection 1\" - \"Collection 3\" for example)\nThat would be nice if moving to collection will also support their number.\n\nFor example, \"5\" button shows collection called \"Lighting Collection\", so pressing \"M5\" will send selected objects to it.\n\n----\n\n*See: #55162#619317 - originally from @1D_Inc*", "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" ]

[ "UV Dismemberment after Mirror the Mesh Blender 2.90\nOperating system: Windows\nGraphics card: GTX 1080 Ti\n\n**Blende Version**\nBlender 2.9\n\nby mirroring the Mesh the UV will be dismembered\n\nAdd a Mesh > Mesh (UV Sphere) > Edit Mode>Mirror (Ctrl M) x axis>Add a New Material> look at the uv in UV Editor\n" ]

[ "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", "Python API : OBJECT_OT_convert can't be fully abstracted from context with override\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 2.93.5\nIt didn't work in latest Beta build either.\nWorked: I don't think it ever worked otherwise ?\n\nOverriding the context of an operator with a dictionary enables us to call them from pretty much anywhere in the code without having to make sure the context is correct (selected objects, active object, called from a particular editor, etc.)\n\nHowever the `OBJECT_OT_convert` called with `bpy.ops.object.convert` operator still requires an active object to be selected to function with an override, which defeats the purpose of using an override.\n\nIt is explained quite thoroughly in this BSE Q&A 86891\n\nScript to reproduce in an empty file :\n\n```\nimport bpy\n\nbpy.ops.curve.primitive_bezier_curve_add()\n\n# Commenting these 2 lines removes the RuntimeError (context incorrect) on last line\nbpy.context.active_object.select_set(False)\nbpy.context.view_layer.objects.active = None\n\nbpy.ops.object.convert({\"selected_objects\": bpy.data.objects}, target=\"MESH\")\n```\n\n", "Library Overrides: Making an override for \"Selected & Content\" does not create overrides for content\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 \"Selected & Content\" does not create overrides for content\n\n- open `main.blend`\n- with the linked Cube selected, do Outliner context menu > `Library Override` > `Make` > `Selected & Content`\n- override for object is created, however override for mesh is not\n\nNOTE: if you do it a second time, it works as expected.\n\nfor a comparsion:\n- open `main.blend`\n- with the linked Cube selected, do Outliner context menu > `Library Override` > `Make` > `Content`\n- override for mesh is properly created (so Outliner should know what \"Content\" is here)\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.", "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\">", "Collapsed pull down menus have no name in Quick Favourites \nOperating system:\tWindows 7\nGPU:\t\t\tASUS Strix Radeon Vega 64, Divider version: 19.4.1\nCPU:\t\t\tIntel Core i7-5960X\n\nBroken: 2.80, (since Quick Favourites were added)\n\n**Exact steps for others to reproduce the error from scratch**\n\n - Factory Startup\n - Find pulldown menus\n - Right-click context menu --> Untick `Show Menus`\n - Add the three line menu toggle to Quick Favourites\n\n", "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", "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", "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", "Loop deselect doesn't work in 3 button emulation mode\nOperating system: Windows 7\nGraphics card: irrelevant\n\nBroken: 2.80, 9a8b6d51c12, 2018-12-11 01:35, Branch: blender2.8\n\nWith three button emulation and left click select on in user preferences, no methods for deselecting edge loops work.\n", "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", "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", "macOS todo list\nNOTE: this is a direct dump of Install-OS\n\n- [ ] Users have to manually change macOS defaults:\n * Map middle mouse to regular \"Mouse button 2\"\n * Make the Function keys use modifiers (so Blender sees these)\n * Change the Shift+NumPad options to not use Shift (change spaces)\n * The latter two could become part of a new standard macOS compliant map in the future?\n- [ ] ~~Finder aliases or~~(1f223b9a1f afb1a64ccb) hidden files are not being recognized by Blender\n- [ ] macOS swallows some key events, like e.g. emulated numpad - on Norvegian keyboard (see #38273).\n- [ ] Blender prevents macOS from sleep #38702", "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", "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" ]

[ "Resetting default value does not work in popovers or menus\nOperating system: Windows 10, 64 bits, \nGraphics card: Nvidia GTX 1080 8 gb, Nvidia GTX1070 8 gb\n\nBroken:\nblender-2.81.0-git.ce2368cf69f5-windows64\n\nWorked: (optional)\n\nResetting options in the context menu (right click) of things like brush stroke strength, Autosmooth, plane offset and other parameters does not work at all, but does work through active Tool side panes and top bar. Probably it should work everywhere? If I'm working full screen I would want to be able to reset it in the context menu with my stylus as I sculpt.\n\n\n\n1 Create any mesh\n2 Enable Sculpt mode\n3 Select any brush\n4 Right click to invoke context menu\n5 Try resetting any of the parameter to default values\n", "F1 button Help function is not fully working \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.90.0 Alpha\n\n\nWhen trying to use the F1 button help for the online manual in different options of Blender, some don't seem to work. \n\nIn any blender scene, when I go to an option and try to use the F1 button shortcut to get to the online manual, it doesn't work, for example, in the viewport if you go to \"Add>Mesh>Plane\" and try to use F1 nothing happens, but if you right clic the option is there and completely functional, but the F1 is not working, the same happens using the shortcut menu of SHIFT+A. This also happens with the other menus in the viewport, like the Object menu, etc, the left menu in the viewport seems to work, for example the \"select box\" icon works fine, and all the other tools there, also the options in the other menus like in the material section, they all work, it seems to be only some things of the viewport menu.\n\nThank you :) [Blender 2020-07-07 20-47-42-1.mp4](Blender_2020-07-07_20-47-42-1.mp4)\n\n\n- Open general template\n- In viewport, navigate in menu Object -> Transform -> Move\n# Press F1\n\nNothing happens, but manual will be opened by right clicking and selecting Online Manual.\n" ]

[ "Blender 3.5 crash on render with Intel 4600 integrated GPU\nOperating system: WIndows 10 x64\nGraphics card: Intel 4600\n\nBroken: 3.5 \nWorked: 3.4.1\n\n\nBlender crashes when attempting to render in Evee. Cycles seems to work.\n\n", "Sculpt Mode Painting\nThis task outlines the remaining To Do's for fundamental sculpt mode painting.\n\n### Color Swapping\n\n- `X` for switching primary and secondary color\n- The current shortcut for `X` for the draw brush will be removed.\n\nIn one of the upcoming releases all brush shortcuts in sculpt mode will be removed anyway, for maximum user customization.\n\n### Canvas Picker & Viewport Color\n\nSince painting is something optional in sculpt mode we need to make sure that:\n- Color Attribute shading isn't enforced\n- Color attributes will be displayed when using painting tools\n- A fast way of choosing color attributes in the UI\n- An optional & discoverable way of switching the viewport shading for all objects (optimal painting scenario)\n\nThe proposal for this is:\n- Use [D16241](D16241) canvas picker UI in sculpt mode. Always visible but grayed out if viewport shading color is not `Attribute`\n- Whenever a painting tool is active, the canvas picker is no longer grayed out and the color attribute viewport shading is enforced in workbench shading on the active object only\n- In the canvas picker popover, add a message or button to switch the viewport color to Attribute if this is not yet the case, so that colors stay visible between brushes/tools. \n- Remove the current behavior of automatically switching the viewport color when a painting tool is used\n\nTo make sure the sculpting experience is already taking color attributes into account, the default sculpting template and workspace should use color attributes for viewport shading.", "Multires Level switching undo bug\nOperating system: Linux-5.4.0-42-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.90.0 Beta\n\nWhen sculpting in multires, the switching between different levels of subdivision is not included in the undo stack.\nBecause of this, when sculpting changes in the model, then switching between levels and sculpting more and afterwards using undo, it will not reliably undo the strokes.\nIn some cases it won't undo at all unless it exits sculpt mode or reaches some point in the undo stack where the level gets changes another time.\n\n\n[2020-08-03 15-38-50.mp4](2020-08-03_15-38-50.mp4)\n\n- Add an object with a multiresolution modifier and subdivide it a few times\n- Sculpt changes on the highest level, then on a lower level and then again on a higher level\n- Undo all those strokes until the mesh breaks or you exit sculpt mode and all is reverted at the same time", "Script node with shader output crashes Eevee\nOperating system: OSX Monterey (12.6)\nGraphics card: Radeon Pro Vega 20\n\nBroken: git versions: blender-v3.2-release, blender-v3.3-release, master\nWorked: 3.2 release\n\nI'm testing the MaterialX standard surface shader. It seems to work when in Release versions, but in a debug build, it crashes when you connect the output of the shader to 'surface' in the terminal node.\n\nUsing the default scene, switch from Eevee to Cycles + Open Shading Language. Select the Cube, switch to Shading tab. Create a new material, and add a new Script node. Load the attached .oso file (to compile the attached .osl, you need to have MaterialX installed. I'm using 1.38.5). Attach the output of the script node to the 'Surface' input of the terminal. Boom! Where the crash occurs depends on whether your in Eevee preview, or Cycles preview.\n\n[out.osl](out.osl)\n\n[out1.oso](out1.oso)", "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", "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)", "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", "Particle instance modifier can crash when create from Children is checked and Normal is not\nOSX 10.11.6, xeon w3680 6core 12thread \n[system-info.txt](system-info.txt)\n2.69.7 5bd8ac9\nalso Nightly 2.79 34fe3f9c069\n\n\nUsing a particle instance modifier with Children checked and Normal not checked and then attempting to change certain parameters of the particle system such as in the velocity or children tabs causes a crash. Enabling Normal in the particle instance modifier prevents this from happening.\nCreate a Plane with a hair type particle system.\nCreate a cube with a particle instance modifier and set the object to the Plane with the particle system.\nCheck the box for Children and uncheck the box for Normal.\nGo to the particle system on the Plane and check Advanced. \nDrag any of the values in Velocity or Children and soon it will crash.\n[Crash_ParticleInstance.zip](Crash_ParticleInstance.zip)", "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", "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```", "Grease Pencil: Line Art › Light Contour causes crash\nOperating system: macOS-11.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M295X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.21\n\nBroken: version: 3.6.0 Alpha\nAlso reproduced with 3.5 and 3.4.1\n\nWhile using the Grease Pencil Line Art modifier, enabling the Light Contour feature causes a crash. The problem does not appear with a very simple scene, so a certain amount of geometry may be needed, hence the 6mb sample file. While trying to reproduce with smaller scenes, I sometimes had to toggle the Light Contour checkbox on and off a few times to trigger the crash, and the number of toggles actually varied from one launch to the next.\n\n1. Open provided file, GP crash.blend\n2. Select Grease Pencil object and expand its Line Art modifier\n3. Click Light Contour checkbox to enable it\n\nThis reliably causes a crash on my Intel Mac\n\n", "Crash while switching to edit mode with EEVEE + Geometry Nodes\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 3.0.0\n\nWhen switching to edit mode in while the viewport's set to render it crashes (see attached video)\n[blender crash 2021-12-17 21-54-00.mp4](blender_crash_2021-12-17_21-54-00.mp4)\n\n1 load the attached file\n2 switch to rendered view in the viewport\n3 switch to edit vertex mode\n4 that's a crash!\n\n[transitions_001_blender3.blend](transitions_001_blender3.blend)", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\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", "Geometry instances cannot mix with other instancing\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 Alpha\nWorked: 3.0 alpha\n\n\n\n[cant scatter.blend](cant_scatter.blend)\n[2021-11-02 19-08-07.mp4](2021-11-02_19-08-07.mp4)\n\n" ]

[ "Regression: Sculpting on a linked copy of an objects crashes Blender\nOperating system: Windows-10-10.0.19044-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\nWorked: 3.2 alpha and mabye betas\n\nThis apparently started with eae36be372 \n\nSculpting on a linked copy of an objects crashes Blender\n\n- Open Blender \n- Create duplicate linked of default cube: {key Alt D}\n- In sculpt mode draw with brush on linked copy OR\n- switch to wireframe viewport shading mode and just enter sculptmode\n\n(No crash when i sculpt on the original Object though.)\n\n[NVIDIA_Share_nm7AkRc7Ad.mp4](NVIDIA_Share_nm7AkRc7Ad.mp4)" ]

[ "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", "Allow View Navigation within Modal Operators\nExcept when there's a good reason to block navigation (such as modal transforms) all modal operators should allow user to navigate the viewport. This includes panning, rotating, zooming, and changing to direct view (top, front, side, etc).\n\nFor example, neither Box Select or Circle Select allow viewport navigation. This severely limits the tools use, often requiring the user to activate the operator multiple times from different angles. \n\n**Operators that need navigation events passed through**:\n - Circle Select\n - Box Select\n - Mesh Bisect\n - Mesh Loopcut and Slide\n", "Drivers not updating correctly when multiple drivers are relying on single property value change (viewport issue only)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\nBroken: version: 2.81 (sub 10)\nAlso tested on 2.80 release version. Happened for me there for the first time so I've downloaded newest build to check if issue still occurs.\n\nWhen multiple drivers are linked into the same property, changing value of that property is not always propagated to all drivers. It looks like some sort of race condition, although I don't think it's caused by switching property back and forth and threads overlapping in that scenario, because even when doing this slowly, issue occurs. Issue also occurs when clicking arrows on a property instead of dragging left/right. \n\nSeems to be related to viewport displaying only. As presented at the end of linked video, rendering scene in such broken state is working correctly.\n\n1. Open provided blend file\n2. Select small cube at the bottom of the screen\n3. Cube has a property on it. Switch its value back and forth.\n4. When property is set to 0, only vertical bars should be visible. When property is set to 1, only horizontal bars should be visible.\n5. Not every time, but occasionally bar is visible when it shouldn't or the other way around.\n\nVideo of bug occurrence:\n\nwatch?v=5wrGXl3KnrQ&feature=youtu.be\n\n[bug-drivers.blend](bug-drivers.blend)", "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). ", "Impossible to use any other mouse button than MMB to navigate in Knife tool mode\nOperating system: Windows 10\nGraphics card: GTX1080Ti\n\nBroken: 2.8 latest master\nWorked: Probably never\n\nThe way Knife tool mode is executed makes it impossible to navigate 3D viewport in the Knife tool mode as long as navigation buttons are mapped to any other key than middle mouse button (MMB). This does not interfere with default Blender kemap, where Orbit (Rotate), Pan and Zoom viewport navigation actions are mapped to MMB, but doesn't allow viewport navigation in the other custom keymaps, including the proposed industry compatible one: T54963 \n\nThere is no combination of settings in Knife Tool Modal Map section which would allow to solve this issue and make non-MMB based viewport navigation function in Knife tool mode.\n\n\n1, In factory default setup Blender, got to edit mode of the default cube, activate Knife tool using K key, and notice MMB to orbit, Shift+MMB to pan and Ctrl+MMB works.\n2, Go to User Preferences, Keymap section, and in 3D View>3D View (Global) \n3, Change Rotate View from Middle mouse to Alt+Left Mouse and change the action type from \"Press\" to \"Click-Drag\" (To distinguish from Alt+LMB click, which selects edge loops)\n4, Change Zoom view from Ctrl+Middle Mouse to Alt+Right Mouse\n5, In 3D viewport, notice that Alt+LMB and Alt+RMB work correctly to activate Viewport Rotate and Viewport Zoom respectively\n6, Enter Knife tool mode, and notice that Alt+LMB and Alt+RMB do not work to Rotate or Zoom the viewport.\n7, In Keymap editor, under 3D View>Knife Tool Modal Map, notice there is no possible setup to make these new navigation hotkeys work.\n\nResult: There is no way to configure Knife Tool Modal Map so that viewport navigation in Knife Tool Mode works with any other mouse buttons than MMB.\n\nExpected: It is possible to configure Knife Tool Modal Map so that it works with non-MMB based viewport havigation configuration.", "Knife cursor goes away when dragging status bar to see options\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 531.41\n\nBroken: version: 3.5.0\n\nWhile using the Knife tool, and using middle mouse click and drag to see all options within the status bar, the knife cursor changes to the edit cross cursor. This doesn't happen when using the mouse wheel to scroll through the status bar. It also doesn't happen using the Knife Active Tool, only when pressing K to launch the tool.\n\n1. Press K in Edit Mode to launch the knife tool\n2. Move the cursor over to the status bar, where the options for the tool are shown.\n3. Middle Mouse click and drag left and right to scroll through the status bar.\n\n[Knife cursor dissappears.mp4](attachment)\n\n", "Inconsistency of some tools/operators (e.g. Subdivide) in regards to hidden geometry\nBroken: all or none\n\nI'm not really sure this is even an issue, though it feels like it. As far as I understand it, mesh editing tools are not supposed to affect hidden geometry. But the Subdivide tool does. Consider this mesh:\n\n\nIf you hide the middle face...\n\n\n...and then Subdivide the two remaining faces...\n\n\n...Subdivide will create new edges cutting through the hidden face, also creating inconsistent selection (i.e. selected edges in face select mode). Shouldn't the operator check that that face is hidden and not create edges through it?", "Can't scale area light in normal direction\nOperating system: Windows-10-10.0.15063-SP0 64 Bits\nGraphics card: Quadro K2200/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.78\n\nBroken: version: 2.82 (sub 5)\nWorked: blender-2.82-77c744054062-windows64\n\nDefault area lights need too much space in viewport, so I usually scale them down in normal direction to get smaller object. In this build I can't make it any more. One more thing, that also Spot lights need to much space in normal direction and I can't change it. I remember, that I 2.5 - 2.7x was function named clip start and clip end for this issue.\n\n1. Add area light.\n2. Hit S to scale and type 0,05 in Z direction.\n3. Notice, that doesn't happened.\n\n\n", "Blender 2.80 Canceling of visibility actions during opened panel with object default parameters.\nwin 10 - 64 bit\nNVIDIA GeForce GTX 560\n\n2.80 beta, 1df6a98b176f, blender2.8, 2019-03-05\n\n**Error description**\nLooks like a small flaw. Panel with default parameters(radius, etc..) of standard objects if objects just created - will be canceling your actions with outliner panel (visibility actions) if you dont close it and continue changing parametrs after that\nDemo: 0876b975cd74ce4d9400b6556e5cbe14.mp4\n\n**Steps to reproduce**\n\n- Open new general template\n- Add mesh - circle\n- Hide cube in outliner\n- In Adjust Last Operation panel change radius\n\nCube is no longer hidden", "Circle Select and Border Select malfunction when their shortcuts are set to Mouse4 or Mouse5\nOperating system: Windows 10\nGraphics card: RTX 2080 Ti\n\nBroken: 3.0.0\nWorked: 2.93.5\n\n**Bug Description**\nWhen called using a shortcut set to \"Button4 Mouse\" or \"Button5 Mouse\", Circle Select and Border Select in the 3D Viewport will act as if the left mouse button is being held down continuously (The circle is continously selecting / a selection box will be drawn). \n\nPressing the Middle mouse button does not deselect, pressing the left, middle or right mouse button will instead end the Circle/Border Select. \n\nIf the shortcut is set to a keyboard button or the tool is activated through left-clicking a menu, the tools work as intended.\n\nOn a fresh install of Blender 3.0 with default settings, \nset the shortcut for Circle Select or Border Select to \"Button4 Mouse\" or \"Button5 Mouse\", \nthen press the assigned button", "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", "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", "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)", "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", "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" ]

[ "Navigation problem with Background/Reference Images\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Intel(R) HD Graphics 520 Intel 4.4.0 - Build 21.20.16.4599\n\n\nBroken: version: 2.80 (sub 51)\nWorked: (optional)\n\n\nNavigation problem (random viewport teleportation) when zooming into background/reference images.\n\n- startup basic blend file;\n- import reference or background image;\n- navigate (pan, orbit or zoom) while hovering mouse over image;\n- viewport moves to random point, fixable by hitting shift+C.\n" ]

[ "Crazy-space support for meshes in geometry nodes\nIn [D15407](D15407) crazy-space support for curves is added to geometry nodes. Currently, meshes use a different system for crazy-space that is not really compatible with nodes as is.\n\nIt should be possible to use the approach implemented for curves for meshes as well, but that needs to be investigated further.", "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).", "Cannot render GeoNodes instanced collection without having original collection also rendered\nA collection is created and two planes shaped as diamonds are added. A separate plane is created and geometry nodes is used as a modifier instancing multiple copies of the diamond collection. When rendering only the geometry node instances are to be rendered but the original collection also renders. If the camera icon in the outliner is changed to black for the original collection or the diamonds then the whole scene is rendered black. The geonode plane with a white (on) camera icon should render all items generated by that modifier and the original diamonds with the camera black (off) should not be rendering.\n[B30beta renders too much.blend](B30beta_renders_too_much.blend)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Beta\n\n\n\n", "Texture nodes CPU evaluation design\nFor #54656, we need CPU evaluation of a subset of shader nodes that form the texture nodes.\n\nPrototype under development in [D15160](D15160).\n\n**Overview**\n\nThe plan is to make this a subset of geometry nodes that can be evaluated using the same mechanisms. Texture nodes can be though of as a geometry nodes field, and when evaluated in the context of geometry nodes they are.\n\nHowever they can also be evaluated outside of a geometry node tree. In particular, they can be evaluated on:\n* Geometry domains vertex, edge, face, corner, for geometry nodes and baking of textures to attributes. Possibly also sculpting and vertex color painting.\n* Geometry surface, for image texture baking and painting.\n* 2D or 3D space not attached to any geometry. For brushes, 2D image painting, physics effectors.\n\nTo support the last two cases in the geometry nodes infrastructure (but not the geometry node evaluation itself), a new field context named `TextureFieldContext` is added. This represents a continuous texture space, that may be mapped to a geometry surface or not. It has one domain, `ATTR_DOMAIN_TEXTURE`.\n\n**Compilation and Execution**\n\nThe texture nodes compilaton and evaluation mechanism uses much of the same infrastructure as geometry nodes, but is separate to be usable in different contexts. It's meant to be possible to execute texture nodes efficiently many times, for example paint brushes are multi-threaded and each thread may execute the nodes multiple times. This is unlike geometry nodes where multiple threads may cooperate to execute nodes once.\n\nThe current compilation mechanism is as follows:\n* Multi-function nodes are compiled into a `MFProcedure`, which bundles multiple multi-functions into one for execution. Geometry nodes do not currently use this mechanism, but it is designed for this type of evaluation. This is rather inefficient currently for individual points, but should get more efficient when evaluated in big batches.\n* Remaining nodes are input nodes, and execute `geometry_node_execute` as part of compilation, which then outputs fields and values. The execution context for these nodes is limited, unlike geometry nodes there is no geometry, object or depsgraph.\n* For evaluation, fields are converted into `GVArray` using the provided geometry.\n\nWe could consider making geometry available and to the compilation and caching the compilation per geometry, though it's not clear there will be nodes that need this. Alternatively we may cache just the `GVArray` per geometry.\n\n**Fields**\n\nInput nodes return fields, which are then turned into `GVArray` for evaluation. For the texture domain, this is a virtual array that interpolates attributes. There may be some possibility here to share code with data transfer field nodes, or nodes that distribute points and curves on surfaces and inherit attributes.\n\nShader nodes need additional fields that are not currently in geometry nodes:\n* Generated / Rest Position / Orco\n* Normal, taking into account face smooth flag and custom normals\n* UV maps (planned to become available as float2 attributes)\n* Active render UV map and color layer\n* Tangent\n* Pointiness (Cavity)\n* Random Per Island\n\nIt's unclear to me what the best way to specify these as fields is, if we should add additional builtin atttribute names or `GeometryFieldInput`. Some of these like Pointiness would also make sense to cache as attributes, and make available to external renderers.\n\nOne constraint is that it must be efficient to evaluate only a small subset of the domain. For many field inputs and operations this works, but there are some that will compute a data array for the entire domain. This can be enforced by just not making such nodes available as texture nodes, or caching the data array on the geometry.\n\nFor sculpt and paint modes, there is a question if and how we can make all these attributes available. The challenge is that it has different mesh data structures (bmesh and multires grids), which are not supported by geometry nodes. Additionally, recomputing for example tangents and pointiness as the geometry changes during a brush stroke would be inefficient, especially if it's for the entire mesh and not just the edited subset.\n\n**Batched Processing**\n\nFields and multi-functions are not optimized for evaluating one point at a time, there is too much overhead. That means we want to process texture evaluations in batches, and all (non-legacy) code that uses textures should be refactored.\n\nFor geometry nodes, modifiers and 2D brushes this is most likely straightforward. However for 3D brushes, particles and effectors it will be more complicated.\n\nThere is currently a mechanism to single evaluations possible while code is being converted. However this is rather inefficient, with quite a bit of overhead in `MFProcedure` execution. It may be possible to do some optimizations there for legacy code that we may not be able to easily convert to batches.\n\n**Node Graph Transforms**\n\nTo support sockets like Image datablocks, and to automatically insert Texture Coordinate or UV Map nodes for textures coordinate sockets, we need to transform the node graph. The texture node layering will also need to do significant node graph transformations. In order to share code with Cycles and other external engines, it may be best to do this as part of node tree localization.\n\n**Relation to Other Node Systems**\n\nThere are many node evaluation systems in Blender, and the question is if we can somehow share this implementation with anything else. I don't think the CPU evaluation can be directly shared, but will make the old texture nodes evaluation obsolete at least. The GPU implementation can probably be largely shared with shader nodes, and that implementation could be refactored to use DerivedNodeTree for consistency and to simplify that code.", "Geometry Nodes Inputs `is_animatable` Property Incorrectly Returns False\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.59\n\nBroken: version: 3.3.0 Alpha\n\nGeometry Nodes inputs' context menus ([WM_MT_button_context ](bpy.types.Menu.html#extending-the-button-context-menu)) incorrectly show the inputs' `is_animatable` property as `False` when the property does accept keyframes (see screenshot, attached).\n\n\n - Open the attached .blend file (attached, below)\n - Run the script in the Text Editor\n - Right-click the Input property of the Cube's Geometry Nodes Modifier\n - Open the System Console to see the `is_animatable` property of `context.button_prop` is `False`\n[is_animatable.blend](is_animatable.blend)", "Cycles does not render geo with Multires modifier while in Sculpt mode\nOperating system: Windows 10, Linux\nGraphics card: Nvidia GTX 960\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nAdding a Multires modifier with the Sculpt parameter > 0 (to further develop the model I'm working on) makes the geo disappear when using Cycles in the viewport, while in Sculpt Mode. As a first time Blender user, I'm not sure if this is the expected behaviour for this. I have checked with other users and they can reproduce the error. \n\nIt would be useful to render in viewport without leaving Sculpt Mode.\n\nCreate a geometry. Add a Multires modifier. Set Sculpt to a value greater than 0. Enter Sculpt Mode. Change the viewport render from Eevee to Cycles. The geometry disappears on rendering. I have a sample of the problem in this tweet I published several hours ago: 1150657198374080512\n\nThanks!", "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", "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", "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", "Modifiers which deform spline points propagate across all users of the same data unexpectedly\nVersion: 2.81 build Oct 23 (Linux 64)\n\nWhen a Curve Object Modifier uses the \"Apply On Spline\" setting, it seems to affect the curve data directly. This means that if a curve data block is used by multiple objects, a modifier on one of those objects will affect all the others.\n\n[curve_modifier_bug.blend](curve_modifier_bug.blend)\n\nTo reproduce, open and inspect the attached file. Notice that the objects on the left both have deformation modifiers, while their clones on the right do not. However, the curve object still appears to be modified because it uses the same data as the modified curve object. This is not how modifiers are supposed to behave. \n\nThe expected behavior is demonstrated by the two mesh objects. Like the curve objects, they also share the same data, but the effect of the modifier is limited to the owner of the modifier.", "Translation is not displayed in the node attribute interface\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 496.49\n\nBroken: version: 3.5.0 Alpha\n\nTranslation is not displayed in the node attribute interface.\n![4IN6Y]W3O[TB6@}K9$PW~4L.png](4IN6Y_W3O_TB6__K9_PW_4L.png)\nShaders can translate languages, but there is no translation language in the property panel of geometric nodes.\n![X@@KXLBM9W@5OK%{[email protected]](X__KXLBM9W_5OK__BNZRN_R.png)", "Geometry nodes crash involving point translation and points to volume\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.\nCannot open reference file in stable (crashes immediately). \nMy oldest 3.0 from 2021-08-01 (`836aeebf7077`) also has the issue.\n\nBlender crashes in certain setups involving point translation and points to volume.\n\n- Open .blend file\n- Connect \"Crash\" node with Reroute\n\nUpon some more testing I found that there are more specific values or ranges that cause the problem, when using the power node one is around 2 to the power of 24.003.\nKnowing values that crash, the attribute fill node can be used:\n\n\n[attribute-fill.blend](attribute-fill.blend)\n[attribute-power.crash.txt](attribute-power.crash.txt)", "Cannot sculpt under masked geometry 2.92\nOperating system: windows 10\nGraphics card: nvidia 1050ti\n\nBroken: 2.92.0, also 5ec6c8d267\n\nWorked: (optional)\n2.83.12lts\n\nLast report on the same issue #80980 (Cannot sculpt behind Hidden geometry)\nCannot sculpt under maked geometry. I reported this bug in a previous version and it was fixed. the bug is now back.\n\n| ||\n| -- | -- |\n\n- Add a UV sphere.\n- Assign some vertices to a vertex group, \"del\".\n- Add mask modifier, mode = vertex group, select \"del\", check \"invert\"\n- Go to sculpt mode, notice the vertices highlighted under the brush or the geometry modified while sculpting. In 2.83.12, they're on the back side of the hole. In 3.0, they're part of the \"del\" group.\n\n\n\n\n", "Cannot Apply Multi Objects\nOperating system: Linux-5.8.0-53-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14735 Core Profile Context 21.10\n\nBroken: version: 2.92.0\n\nWhen I try to apply scaling, rotation or location to a linked object (Alt+D) I get this error message:\n\"Cannot apply to a multi user: Object \"Cube.001\", Mesh \"Cube\", aborting\"\n \n- Scale the cube \n- Link it with Alt+D,\n- Apply scaling, location or rotation to one of the two cubes.\n\n[Blender 2021-05-30 00-10-18.mp4](Blender_2021-05-30_00-10-18.mp4)", "Geometry nodes. Viewer node data late update (delete node and undo)\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**Short Description**\nSpread Sheet editor is not updating when I undo the action of viewer node deletion\n\n**Steps to Reproduce**\n- Open .blend file\n- Delete viewer node\n- undo (You will not see any data in the spreadsheet until click on the viewer node or hovering mouse over spreadsheet)\n\n[#94641.blend](T94641.blend)\n[2022-01-04_20-09-05.mp4](2022-01-04_20-09-05.mp4)\n" ]

[ "Support piping legacy modifiers with the geometry nodes modifiers\nThe proposed solution is to output only volume and mesh data. Point cloud data will be converted to vertices.\n\nThis allows to integrate other modifiers with the geometry nodes modifier (e.g., an array modifier after the geometry nodes).\n\nTo support instancing \"made real\" is a different task. ", "Object Info node breaks \"active selection\" and excludes Geometry Nodes object from modifiers\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: 2.93.0 Alpha\nWorked: On 2.8.2021 2.93 Alpha version.\n\nA little difficult to explain to be honest. Take a look at the image. When using an Object Info Node with Geometry Nodes, the input mesh appears to not be an active selection under the Node Tree, resulting on an exclusion of this object from another modifiers. Notice how the cylinders received the wireframe modifier but the sphere hasn't. \n\n\n\n\n\n1. Create a node tree using a cylinder. \n2. Add a sphere on the scene. \n3. Add the above sphere on the node tree using the Object Info node. \n4. Join them using the Join Geometry node. \n5. Add a modifier after the Geometry Nodes modifier. \n6. See how the object info mesh is not affected by the modifier. \n\n" ]

[ "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", "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)", "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)", "Minor image editor left click values bug\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\nWhen inspecting an Openexr image file with sRGB color space it gives incorrect raw values.\n\n\nOpen any external Openexr image in the image editor\nLeft click to inspect values\nSwitch to sRGB color space\nLeft click to inspect values\nThe image editor will now display incorrect values for RGB (not color managed) next to XY\n\nDon't ask me why I inspect an Openexr with sRGB color space, but here is just to let you know this bug exists.\n\nThank you and have a great day!\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", "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", "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", "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)", "When updating render percentage, the Box Mask node in compositor is also affected\nI ran into a confusing issue the other day that made me log bug #50113, thinking there was an issue related to masks and render size, but it turns out the issue is in the viewer node not updating correctly when adjusting render size.\n\nIn the attached fine, when I change the render percentage and update a value in the compositor, the result in the viewer changes so the mask is not consistent.\n\nIf I re-render the scene, the mask would appear relative.\n\nUnfortunately, since the viewer updates and displays the incorrect information, this can be confusing to the user and cause them (me) to freak out and try and adjust things that don't need to be adjusted. For example, I ended up changing my mask values over and over again, never achieving the correct result. \n\n - Open: [maskIssue.blend](maskIssue.blend)\n - Render an image\n - adjust the render resolution percentage to 100% (so far it's ok)\n - click on the `width` property of the `Box Mask` node and drag to a lower value\n\nNotice that the mask changes in the preview. Render again, and the mask looks correct.\nRendering resolution should not influence the result of the composite.\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", "Edit mode: Fill region operator wrong behavior.\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: since 2.79 till now. \nTested with 2.79b, 2.83.9, 2.92, 2.93 3ea1779365b5\n\n\nFill region operator fails with this geometry. Test my file.\n{[F9906012](9540941.png) size = full}\n[untitled.blend](untitled.blend)\n[2021-03-23_23-38-13.mp4](2021-03-23_23-38-13.mp4)\n", "Subdivision modifier artifacts in Blender 2.80\nOperating system: Windows 10\nGraphics card: 1080ti\n\nBroken: \n2.80 downloaded on the 3rd of Feb, 2019 as found on the download beta section\nWorked: (optional)\n\n\nSome artifacts around the out circle in the blend file, this is not present in Blender 2.79\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nload attached file, doesn't matter if it is Cycles or Blender the artifact is present.\n\n[ukelele.blend](ukelele.blend)", "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)", "Shader node float precision issue cause different results on CPU and GPU\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\nCPU: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz\n\nBroken: version: 2.80rc2 (2.80 (sub 74))\n\nWhen rendering a mandelbulb volumetric thing on cycles using CPU and GPU, the two have very different ideas on how the scene should look like, making the individual tiles clearly visible. \n\n**Render**\n \n(most tiles are GPU-rendered, note the stray red CPU-rendered tile to the left)\n\n**Blend**\n[mandelbrot.blend](mandelbrot.blend)\n\n**Potentially useful information**\n* #50193 may be the same bug; I opened a new one because that bug doesn't report differences within a single frame, and is from 2016.\n* Since most of this object is endless math nodes, it may be some sort of floating-point thing that works differently on CPUs and GPUs. \n* I was following this tutorial: watch?v=WSQFt1Nruns\n* I noticed that some operations for which I expected single inputs (namely the sines) had two inputs. In the tutorial, the dude said the second input doesn't do anything, but then, that's from the alpha. Maybe taking a 0.5th sine of a value does something strange?", "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" ]

[ "Subdivision Creasing Unresponsive on 0.55-0.99 range\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\nBroken: version: 2.81 (sub 1)\n(Also broken in 2.8 release version)\nWorked: 2.79b\n\nWhen using Edge Creasing and Subdivision Surface modifier the result is inconsistent for .55-.99 values. For 0-.55 the mesh updates gradually as one would expect. However, after that inserting .6 .7 .8 .9 no visual change can be observed. At value of 1 the mesh snaps to the final creasing. (which is considerably sharper than the .55)\n\n- Select the default cube. \n- Add a subdivision surface modifier \n- Go to edit mode and select single edge (or all edges) \n- Press N to open tab and go to edge data to scrub Crease value\n- Observe how 0-.55 change is linear but after that nothing really happens before 1.0\n\n[EdgeCreasingProblems.blend](EdgeCreasingProblems.blend)\n" ]

[ "Blender 2.7x keymap: Add reroute shortcut (shift right mouse) doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.91\n\nCaused by 58e554a55c\n\nShortcut for add reroute doesn't work in node editor.\n\nTry add reroute between two connected nodes using shortcut (shift + RMB during cross line).\n\n", "Application templates crashes if the startup.blend of the application template contains scene named \"Asset\"\nOperating system: Windows-10-10.0.22621-SP0'\nGraphics card: NVIDIA GeForce RTX 2070 Super with Max-Q Design/PCIe/SSE2\n\nBroken: 3.5.1 2023-04-24 18:00 e1ccd9d4a1d3\nWorked: Never\n\nApplication templates that contain certain pattern in startup.blend lead to Blender to crash.\nApparently occurs when the scene is created with the name \"Asset\" and used as a application template.\n\n- Download attached [MCE.zip](attachment) file\n- Install the attached application template file (`Blender` menu > `Install Application Template...`).\n- Load it (choose the new \"MCE\" option in `File` > `New`).\n\nBlender crashes.\n\nAttached also the `blender.crash.txt` and another template.\n\n[MCE.zip](attachment)", "Cycles destroys an existing texture image while baking to a new image\nOperating system: Windows 11\nGraphics card: rtx 2070\n\nBroken: 51bc44420b89\n\n\nBlender seems to destroy or empty an existing texture in a multi material setup while baking to a new image.\n\n\n\n\nload the attached file\n\nselect the BAKE material\n\nselect the BAKE image node\n\nRender Props -> Bake ( it is already setup)\n\nPay attention to the viewport to see that one of the textures turn black, and the BAKE texture is still black\n\nYou can try variations as in putting the BAKE node in other materials however the result seems to be the same failed bake.\n\n", "Crash when renaming a world in a timer and dragging a world in the asset browser\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.23\n\nBroken: version: 3.4.0 Alpha\nWorked: Don't know, tested back to 3.1, and still got the crash\n\nWhen a python timer renames a world, and the user is dragging a world *from another file* in the asset browser, blender will crash. (doesn't happen if the world is from the current file)\n\nI also tested this on materials, and it didn't cause a crash, so I assume that it's limited to just worlds.\n\n[world renaming crash.blend](world_renaming_crash.blend)\n* Open the attached blend file, and run the script in the text editor.\n* That will start a timer that will run once a second for ten seconds, and will rename a world data-block each time.\n* During those ten seconds, in the asset browser window, start dragging a world asset that originates from another file.\n* Blender should crash.\n\n[2022-10-23 15-49-18.mp4](2022-10-23_15-49-18.mp4)\n\nThanks a lot!", "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", "Crash on render\n**System Information** MSI BRAVO 15\nOperating system: WINDOW 11\nGraphics card: RX 6600\n\n**Blender Version**3.6\n\nWhen attempting to render a scene in Blender, the software consistently crashes, causing frustration and hindrance to the rendering process. This issue is hindering users from efficiently creating their projects and requires immediate attention to maintain a stable and reliable rendering environment.\n\n[debug-log](https://projects.blender.orgattachment)\n[system info](https://projects.blender.orgattachment)", "Cycles doesn't refresh after changing color space of the image texture node in 3.0 beta.\nOperating system: Win10 20h2\nGraphics card: RTX 3090\n\nBroken: 3.0 beta Nov.22th daily\n\n[Color Space.mp4](Color_Space.mp4)\n\nUse image texture node to import a image. Changing the color space, cycles refreshes. \nLoad another image, it still works. \nBut after using the drop down menu to load back the previous image, it doesn't work any more.", "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", "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)", "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.", "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", "Adding NodeGroupInput node with NodeSocketImage input to CompositorNodeTree causes Bad Access crash\nOperating system: macOS 12.3.1 (21E258)\nGraphics card: `Apple M1`\n\nBroken: 2.93.10, 3.1.0, 3.1.2, 3.2.1\n\n\nAdding both a `NodeGroupInput` node and a `NodeSocketImage` socket to a `CompositorNodeTree`'s input causes a crash upon entering the group view of the node.\n\n\nOpen a fresh Blender instance\n\nRun the following python commands:\n\n```\ngroup = bpy.data.node_groups.new(\"test\", \"CompositorNodeTree\")\ngroup.inputs.new(\"NodeSocketImage\", \"image\")\ngroup.nodes.new(\"NodeGroupInput\")\n```\n\nOrder of the last two commands does not matter.\n\nOpen up your compositing node graph and enable \"Use Nodes\" if you haven't already.\n\nGo to Add->Group->test\n\nThe application crashes immediately with the following error summary\n\n```-------------------------------------\nTranslated Report (Full Report Below)\n-------------------------------------\n\nProcess: Blender [83447]\nPath: /Applications/Blender3.1.2.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.1.2 (3.1.2 2022-04-01)\nCode Type: ARM-64 (Native)\nParent Process: launchd [1]\nUser ID: 501\n\nDate/Time: 2022-05-14 23:55:57.0678 -0700\nOS Version: macOS 12.3.1 (21E258)\nReport Version: 12\nAnonymous UUID: FFD4E34D-780E-1ED3-65BE-8567CF743554\n\nSleep/Wake UUID: DF7F69BF-5C10-4E9C-8649-79686FC1C136\n\nTime Awake Since Boot: 140000 seconds\nTime Since Wake: 5503 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 27\n\nException Type: EXC_BAD_ACCESS (SIGABRT)\nException Codes: KERN_PROTECTION_FAILURE at 0x0000000101784ddc\nException Codes: 0x0000000000000002, 0x0000000101784ddc\nException Note: EXC_CORPSE_NOTIFY\n\nVM Region Info: 0x101784ddc is in 0x100e48000-0x10a7dc000; bytes after start: 9686492 bytes before end: 151351843\n```\n REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n```\n - > __TEXT 100e48000-10a7dc000 [153.6M] r-x/r-x SM=COW ...MacOS/Blender\n```\n __DATA_CONST 10a7dc000-10ada8000 [ 5936K] r--/rw- SM=COW ...MacOS/Blender\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", "MeshDeformModifier Crashing\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.6.0 Alpha\nWorked: -\n\nAfter binding, with the Dynamic attribute driver value set to 1 in driver editor, it crashed.\n\n1. Add a driver to use_dynamic_bind.\n2. Click Bind\n3. Set the driver value to 1\n\n\n\n\n", "Laucnh error since version 3.4\nOperating system: High Sierra 10.13.6\nGraphics card: ATI 6970M 2 GB RAM\n\nBroken: (example: 3.4 and 3.4.1 2022-12-20, master)\nWorked: (Blender 3.3.1)\n\nWhen I launch blender a get this error that I have found others on the web reporting also on similar setups:\nError opening window.\nFailed to create metal device for offscreen GHOST Context.\n \n\nPrevious versions worked a charm and I really hope 3.3.1 wont be the last version for my humble setup.\n\nThanks and as always appreciate your amazing work!" ]

[ "Regression: Crash when opening a file from a directory that is part of the asset library\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.4 beta\nCaused by cf98518055\n\nif the file is saved in a directory that is part of the asset library, and if the file uses assets from the same library, then a crash occurs\n\n- Extract attached file\n- Open default scene\n- Assign the library folder \"geonodes\" from the archive\n- Switch to GN workspace\n- In node editor, invoke search menu \n[asset_crash.zip](asset_crash.zip)\n- - -\nsteps from bug reporter :\n1. Unpack the archive somewhere, and assign the library folder \"geonodes\" from the archive\n2. Create a file, then a group of geometry nodes, then use any asset from the library in it, save the file in the \"geonodes\" folder\n3. Close the file and open it again. Wait until the Add menu in the geometry node editor finishes loading the asset library (usually it is enough to open the menu, close it immediately, wait a few seconds, and open it again). after opening the menu, there will be a crash" ]

[ "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", "Snapping issue while rotating and 'Align Rotation to Target' is ON - can't set correct origon rotation for simple object \nOperating system: Windows 10\n\n\nBroken 2.81 new feature of origon \n\nsnaping rotation origon bug - can't set correct origon rotation for simple object \n\nrotation snaping of origon is tha same important as moveing origon to spec place\n \nI need to specyfy Z direction also x and y direction. To working with this propably I need to have 2 directions snaping z and x or z and y to work with this.\nso for example Z with snaping and then hold shift seting Y snaping... \n\nThis will help with orientation objects in space by orientation of another objects like aligment rotation object to another object ect. \n\nThanks for great work.\n\n\n[origon snaping rotation video.mp4](origon_snaping_rotation_video.mp4)", "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)", "Gizmos do not appear when editing normals via the rotate or point to target functions\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 24.20.100.6292\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nWhen editing normals using the \"rotate\" or \"point to target\" options in the Alt-N normal menu, no gizmo appears to control these functions using the mouse. This behavior isn't consistent with the behavior [shown in this video ](Rqsgrg_SVME?t=123).\n\n\n # Open new \"General\" file\n\n # (Optional: Enable normal visualization gizmos)\n\n # Select cube and go into edit mode\n\n # Select a face and open the Alt-N normal editing menu\n\n # Choose the \"rotate\" or \"look at target\" options\n\n - Gizmo for mouse does not appear\n", "All lights gets turned off when start dragging if the image render window is open on another monitor.\nOperating system: EndeavourOS (Arch Linux variant), Gnome, Wayland\nGraphics card: Intel A770\n\nBroken: 3.6.2.\nWorked: Don't remember.\n\nIn a multi-monitor setup with different scaling values, when the render result window is open on another monitor, if I drag the viewport in the rendered mode, every time the dragging starts, all lights get turned off. Please see the attached screen recording.\n\nBased on the attached .blend file.\n\n1. Find a computer that is running Arch Linux, Gnome, Wayland, and has two monitors with different scaling values like 100% and 150%.\n2. Start Blender.\n3. Switch to Rendered view mode.\n4. Add a cube.\n5. Render the image\n6. Don't close the rendered window but move the window to the secondary monitor\n7. Start dragging the viewport of Blender.\n\n", "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.", "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", "Geometry Nodes: Disabled from viewport object is not visible as instance\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: Current main.\nWorked: Never.\n\nDisabled from viewport object is not visible as instance.\n\nOpen attached file and check/uncheck `As Instance` option of _Object Info_ node.\n\n", "Extrude Gizmo doesn't match extrusion direction\nOperating system: Linux-5.15.0-27-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.3.0 Alpha\n\nThis seems to be a bigger issue without an obvious solution.\nEssentially, when using the Extrude Tool it shows a handle that is oriented towards the normal Z axis. it is supposed to indicate the direction in which the extrusion will happen.\nWhen click & dragging it, it will instead use the normal Z axis of the newly created geometry.\n\nTo be clear, this is the intended and preferred behaviour! Before Blender 2.93 it used to take the original normal Z axis and it lead to a less intuitive experience.\n\nWhat this bug points out is that there is still a mismatch between the previewed direction and the direction that will be used.\n\n\nIn this picture you can see how the extrusion handle and the direction arrow mismatch. This is after already extruding once, but it highlights the disconnect.\n\n- Go into edit mode on the default cube\n- Select the top face and move it to the side (To create a sheared cube shape)\n- Delete the selected top face\n- Select the open edges\n- Make the Extrude Tool active and use the yellow plus handle\n\n", "Gizmo position is wrong for meshes with modifiers\nWin10, Win7, Mac OS Sierra\nGTX970, GTX750\n\nBroken: 2.78a e8299c8 , 2.66.0 r54697\n\n\nWhen a joint (for example, an arm) is bent, paint weight is not enough to express deformation around the joint. So it's a common practice to add a shape key for the bent shape and edit it.\nBut when you enter edit mode and select polygons to edit it, the manipulator is on wrong position. \n\nJust select faces. Manipulator is supposed to sit on the selected faces but it's not.\n\n[manipulator bug.blend](manipulator_bug.blend)", "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)", "Objects with negative and small scale cant be selected using Select Box without zooming. But Select Circle and Select Lasso work fine\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.2\n\nObjects in the sample scene have a very low negative scale. Something like -0.03. They are clearly visible but Select Box doesn't select them. But they can be selected with Lasso and Circle without problem. Please see an attached GIF.\n\n1. Open attached scene.\n2. Try to select all the objects with Select Box. Without zooming try to select them with Lasso Select\n3. Zoom a bit closer and try Select Box once again. You'll be able to select a few more objects\n4. Zoom really close, now all objects can be selected. \n\n\n[small_objects.blend](small_objects.blend)\n", "Holding Ctrl disables Object Lock Modes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.2.1\n\n\nObject Lock Mode have no effect when Ctrl is held, for instance, while using Shortest Path Selection as shown in the following video:\n\n[bug-object-lock-mode.mp4](bug-object-lock-mode.mp4)\n\nThis also happens in other cases like selecting Reference and Background images:\n\n[lockobject.mp4](lockobject.mp4)\n\n", "Set parent (keep transform without inverse) has no effect on scale\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.0 Alpha\n\n\nSet parent (keep transform without inverse) has no effect on scale. End result is different if use Set parent (without inverse)\n\n[parent_scale.mp4](parent_scale.mp4)\n", "UI: Drag Tool option is misaligned and should not use colon\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\nDrag Tool option is misaligned and should not use colon:\n{[F11087908](image.png), size=full}\n\nBtw. `Gizmos:` shouldn't use colon either\n\n" ]

[ "Inconsistent display of 3D Viewport axes and Floor grid display\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.59\n\nBroken: version: 3.2.2\n\nIn the Viewport Overlays options there's a section that enables/disables the axes display (X/Y/Z). It doesn't always work in orthographic side, front and top views. Additionally sometimes it is also dependent of Grid and Floor display being turned ON. It should not be dependent of neither Grid nor Floor display AND it should display the axes reliably on orthographic side, front and top views. Of course the one being \"looked along at\" should not be visible, however the other two aren't always displayed or hidden reliably either.\n\n- Set Blender to factory default settings.\n- Switch to orthographic SIDE view (numpad 3).\n- Check Viewport Overlay display options: you will find the Z axis disabled, and yet it is being displayed. Toggling it on and off doesn't do a thing.\n- Disabling the other two axes doesn't hide them neither. They only vanish when the Grid is disabled.\n- Switch to Top view (numpad 7).\n- Enable Grid. Disable Floor. Nothing happens! The floor grid remains.\n- Toggle the axes. Again, nothing happens. The axes remain visible even if turned off.\n\nSomehow the subsequent display settings of Floor and all 3 Axes are dependent of the 'Grid' setting being enabled or disabled while they should actually be all independent from each other.\n\nThank you", "In orthogonal view, XYZ axis overlay toggle doesn't work with axis aligned views\nBroken: 2.8x\n\nIn orthogonal view, XYZ axis overlay toggle doesn't work\n\n- press numpad 1/3/7\n- toggle xyz axis from overlays panel, they won't hide.\n\nVideo: [F8571714](2020-06-02_20-18-29.mp4)" ]

[ "Artifacts when composing render passes with SSS, EEVEE and SSR\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0 Beta\nWorked: I'm not sure this behavior is new. Blender 3.2 displays the same behavior.\n\nWhen compositing render passes that have been generated using EEVEE, and an object has Subsurface Scattering enabled, and Screen Space Reflections are enabled, and Half Res Trace is disabled, artifacts are generated. The combined pass, however, correctly renders.\n\n\n*What I get (demo file included below)*\n\n\n*What I should get*\n\nNote: if Half Res Trace is enabled, the problem disappears.\nAlso, if Cycles is used to render the same scene, the passes do not display these artifacts.\n\n\n\n\n- Create a file that uses EEVEE as renderer.\n- Enable Screen Space Reflections. Disable Half Res Trace.\n- Create an object with Subsurface Scattering\n- Enable the following necessary render passes: Diffuse Light, Diffuse Color, Specular Light, Specular Color\n# In compositing, mix as follows the passes: multiply Diffuse Light and Diffuse Color; multiply Specular Light and Specular Color; add them.\n\nChanging the roughness can make the effect more extreme. Having a very contrasty roughness map exacerbates the problem:\n\n\n*a contrasty roughness map*\n\n\n*the render showing the problem more extremely*\n\n\n*how it should be*\n\nThe final result should be akin to the one posted above. You can compare the composited result with the one that is already combined: the combined one does not display the issue. Using Cycles for the same setup also works without problems.\n\nThe inconsistency of results mentioned above makes me believe this is a bug, and hence my report.\n\nDemo file: [sstest.blend](sstest.blend)", "Blander crash without ray shadows Nvidia GTX 950M CUDA\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 16)\nWorked: (optional)\n\nWhen turn off ray shadow visiblity render becomes slow and the blender crashes.\n[2019-10-28_03-53-23.mp4](2019-10-28_03-53-23.mp4)\n\n------------\nI tested again on GTX 750 Ti and 2.92.0 Alpha. If I turn shadows off first, then switch to rendered view, it gives bad render:\n\nIt disappears when you do something. Typical when there's something wrong in Cycles. I need to restart Blender to be able to render again.\nWhen I turn rendered view first, then turn shadows off, it sometimes crashes.\nThis is all Cuda. Optix renders nothing at all. I presume Optix doesn't do volumes yet.\nAlso noticed that deleting sun lamp and leaving only area lamps fixed the issue.\n\n**Steps to reproduce**\n[облака в стекле.blend](облака_в_стекле.blend)\n- Open file\n- Disable shadow ray invisibility on object\n- Switch to rendered shading\n", "Some Cycles nodes are active when muted (RGB To BW, Math, vector Math, Separate RGB)\nWin10 64bit\n\nBroken: 2.79\n\nRGB To BW node is active when muted\n\nOpen file and render\n[RGB_BW.blend](RGB_BW.blend)\n\n", "Volume render bug in view layer indirect only.\nOperating system: windows 10\nGraphics card: RTX 2080 supper\nCPU: AMD ryzen7 2700\n\nBroken: 2.92.0\nWorked: no\n\nOutliner \"Indirect Only\" option does not work well with volumes, as inner shadows are ignored.\n\n\nSurface material with indirect only can work.\n\n- Open attached file\n- Display Render Preview in any of the viewports\n(Make sure the \"Indirect Only\" option in the outliner is enabled).\n[renderlayer bug.blend](renderlayer_bug.blend)", "Holdout doesn't work with Mix Shader correctly in Eevee\nOperating system: Darwin-20.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.13\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.91.0\n- 2.90.1\nWorked: 2.83.x\n\nHoldout doesn't work with Mix Shader correctly in Eevee. \n\nWhat I expect when mixing with 100% Holdout:\n\n\n\nWhat I get instead:\n\n\n\n\n\n - Open the simple blend below\n - Move the timeline from 0-100, which moves the Mix Shader Fac from 0-1.\n - When at frame 1, it should be a 100% Holdout, but notice that this isn't the case\n - Switch to Cycles and verify that it indeed handles this case correctly\n\n[holdout_eevee_bug.blend](holdout_eevee_bug.blend)\n\n", "EEVEE Holdout missing screen space reflections\nOperating system: windows 10\nGraphics card: rtx 2070 super\n\nBroken: 2.8.5\n\nscreen space reflections are not applied to an object from environment that has been held out using holdout button on collection. since the stuff is still there when holdout is applied to background, screen space should still be applied to objects that are not held out.\n\nhere is an example:\n\n\n\n[holdout ssr.blend](holdout_ssr.blend)", "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", "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", "Regression: unhide now is global even in local 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 471.41\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.79b\n\nAlt+H in local view unhides objects all over the scene instead only local context, as it work in 2.79\nPlease fix. It is very handy feature and we have lost it.\n\n**Step to Reproduce**\n- Open .blend file\n- Select a sphere and Hide: {key H}\n- Select all three cubes and enter in Local view: {key /}\n- Hide cubes\n- Now unhide cubes in Local view: {key Alt H}\n- sphere is also visible (Either check outliner or Switch back from Local view)\n\nTest File:\n[#92527.blend](T92527.blend)\n[2021-10-27_12-23-23.mp4](2021-10-27_12-23-23.mp4)", "Volume voxels visible in compositing (Cycles)\nOperating system: Windows 10\nGraphics card: GeForce GTX 950 OC\n\nBlender 2.80 cc73d59ad580\n\nFirst of all :\nNot sure if this is a bug or if Im just not getting it.\n\nEverything is done in Cycles\n\nIm subtacting the DiffInd passes in compositing and I get the volxel shape of my smoke sim.\n\nHere a screenshot of my Nodesetup (note the backdrop)\n\n\nI do this to extract the Indirect lighting of for example fire or something else while excluding the sun and stuff.\n\n\nThis is the image (the white cuby thing to the right of the smoke)\n\n\n\n\nAdd a basic smoke simm with high resolution and a ground and wall.\nAdd a sun light\nAdd a new view layer\nExclude the smoke domain from the 2nd layer\nEnable the DiffInd pass for both layeres\n\nIn compositing :\nSubtract the DiffInd passes from each other.\n\n\nThis is an example scene:\n[debug.blend](debug.blend)\n\nIt seems like there is a problem how \"null\" surfaces get handeled.\nIf I set a layer to indirect only the indirect light only appear outside the voxels (where they are intersecting the geometry).\n", "Instancing a collection with an object that has been Disabled in Viewport fails to correctly link in disabled objects breaking \"Make Instances Real\" operator\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0\n\nInstancing a collection into a scene fails to properly link in objects that have been disabled in viewport (henceforth disabled object) using either the \"Disable in Viewport\" icon in the outliner or by setting obj.disable_viewport = True in a script or console. This bug doesn't appear when you hide an object using the H key or obj.hide_set(True)\n\nThis means that if you instance a collection and then \"Make Instances Real\" that the disabled objects will not be transformed with the parent object even if they have been parented to it in the original file and Keep Hierarchy is checked. \n\nThis is a problem because if you have used the disabled object as the operand in e.g. a boolean modifier then as soon as you make a collection real your collection breaks. This is doubly a problem since the default behaviour in the new asset browser is to instance collections into the scene rather than appending them. This bug also affects instancing a collection in the same scene as well as instancing in a collection from an external file. \n\nStart from default file. \nAdd a second cube.\nTransform second cube and place on corner of default cube.\nMake second cube a child of default cube.\nAdd a boolean difference modifier to default cube.\nSet second cube as Object in boolean modifier\nDisable second cube in viewport in the outliner\nInstance collection into scene by dragging and dropping collection from outliner somewhere which isn't the origin.\nEverything appears as it should.\nSelect instanced collection\nSelect Object > Apply > Make Instances Real\nWhile the none disabled cube has been made real the second cube hasn't and if we look in the modifier you can see that the boolean object is still set to the original second cube.\n\nIf instead of disabling the second cube we instead hide it and then instance the collection into the scene the second cube is linked in (although it's also unhidden which is annoying). If we the make this collection real everything works as it should (i.e. the second cube used as a boolean is also made real)\n[link bug.blend](link_bug.blend)", " Render Face Sets and Mask as contour lines\nFace Sets were added to control the visibility of all paint modes and currently, they are rendered as colors (which is the easiest way to debug them and work with them from sculpt mode). This won't work for vertex paint and texture paint (and any other mode that works with color), so a different rendering needs to be implemented that does not affect the color of the surface as an option these painting modes. \n\nIf possible, this should be implemented for the current sculpt mask (add an option to render it as a contour line, similar to the lasso selection) as the same mask implementation and rendering will also be used for vertex paint.", "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", "Cycles X: Camera-visible lamps are not affected by holdout\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0 Alpha\n\nBlender 3.0 adds a feature where camera ray visibility can be enabled on lamps, making them directly visible. However, if this option is enabled simultaneously with the holdout option, the lamp will remain visible. Holdout should override camera visibility, as holdout can be changed per-view layer. With the current behavior, a directly-visible lamp will appear again on holdout layers, copying it's direct brightness for every layer it appears as a holdout in.\n\nSee attached .blend file, which contains a point lamp with holdout and camera visibility both enabled. Note that the lamp remains visible. In fact, the holdout option seems to have no affect at all.\n\n[holdout_lamp_bug.blend](holdout_lamp_bug.blend)\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" ]

[ "Does not work when collection 'holdout' is set to 'indirect only'\nOperating system: MacOS10.14.5\nGraphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nPreviously reported, but the latest version has not been fixed\nReport again with the video file, as the previous report does not recognize the problem\n[Hold out.mp4](Hold_out.mp4)\nDoes not work when collection 'holdout' is set to 'indirect only'\n\n1. Register an object in the collection\n2. Set the holdout for that collection\n3. Render (holdout works)\n4. Set \"indirect only\" of the collection in that state\n5. Render (holdout does not work, only \"indirect\" works)" ]

[ "CUDA problem Error: Invalid value in cuMemcpy2DUnaligned_v2(&param)\ndoes anybody know what this error mean (blender 3.5, 3.6, 4.0 win 11):\n\n*Error:Report:\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\n\n\nWe tried two rtx 4070ti video cards and this error came up when we were about to render. If I disable one of the two, the render runs fine, but if I enable both, the render freezes. I see that it starts using both, but it still gives an error.\n\nThanks\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", "Laucnh error since version 3.4\nOperating system: High Sierra 10.13.6\nGraphics card: ATI 6970M 2 GB RAM\n\nBroken: (example: 3.4 and 3.4.1 2022-12-20, master)\nWorked: (Blender 3.3.1)\n\nWhen I launch blender a get this error that I have found others on the web reporting also on similar setups:\nError opening window.\nFailed to create metal device for offscreen GHOST Context.\n \n\nPrevious versions worked a charm and I really hope 3.3.1 wont be the last version for my humble setup.\n\nThanks and as always appreciate your amazing work!", "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", "Fix big LIghtCache restriction\nAs reported in #78529 saving big lightcache is impossible due to blocksize restriction.\n\nFor now we restrict the lightcache size that can be written to disk but it would be better to slice the huge textures to avoid such limitation.\n\nHowever this needs some refactors in GPUTextures namely the need of a properly exposed `glTexSubImage2D` and `glTexSubImage3D`.", "broken contact shadows on glossy/metalic materials\nOperating system: win 10\nGraphics card: 2070 s\n\nBroken: 2.91\n\nbroken contact shadows on glossy/metalic materials. works fine otherwise\n\n\n\n- Open attached file\n- Go to rendered preview\n[broken contact shadows.blend](broken_contact_shadows.blend)", "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", "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", "The display will be damaged when the node editor in Fullscreen Area mode (ctrl alt spacebar)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R7 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.11.1 27.20.12033.2007\n\nBroken: 2.93 as well as version: 3.0.0 Beta\nWorked: Haven't tested before 2.93.\n\nThe display will be damaged when the node editor in Fullscreen Area mode (ctrl alt spacebar).\n\n* Switch workspace to Geometry Nodes\n* Add a new Geometry Nodes modifier/datablock\n* Ctrl+Alt+Space to go fullscreen (not Ctrl + Space)\n* Select or move a node\n\nFile:\n[bug.blend](bug.blend)\n\nGIF：\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", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Vega GPU crash during render\nOperating system: Debian 11 bullseye x86_64 Linux 5.10.0-17-amd64\nGraphics card: gfx900 AMD/ATI Vega 10 XTX [Radeon Vega Frontier Edition]\n\nHip info: \n```\n➜ blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release hipconfig\nHIP version : 5.2.21152-4b155a06\n\n== hipconfig\nHIP_PATH : /opt/rocm-5.2.1\nROCM_PATH : /opt/rocm-5.2.1\nHIP_COMPILER : clang\nHIP_PLATFORM : amd\nHIP_RUNTIME : rocclr\nCPP_CONFIG : -D__HIP_PLATFORM_HCC__= -D__HIP_PLATFORM_AMD__= -I/opt/rocm-5.2.1/include -I/opt/rocm-5.2.1/llvm/bin/../lib/clang/14.0.0 -I/opt/rocm-5.2.1/hsa/include\n\n== hip-clang\nHSA_PATH : /opt/rocm-5.2.1/hsa\nHIP_CLANG_PATH : /opt/rocm-5.2.1/llvm/bin\nAMD clang version 14.0.0 (llvm-project roc-5.2.1 22204 50d6d5d5b608d2abd6af44314abc6ad20036af3b)\nTarget: x86_64-unknown-linux-gnu\nThread model: posix\nInstalledDir: /opt/rocm-5.2.1/llvm/bin\nAMD LLVM version 14.0.0git\n Optimized build.\n Default target: x86_64-unknown-linux-gnu\n Host CPU: znver2\n\n Registered Targets:\n amdgcn - AMD GCN GPUs\n r600 - AMD GPUs HD2XXX-HD6XXX\n x86 - 32-bit X86: Pentium-Pro and above\n x86-64 - 64-bit X86: EM64T and AMD64\nhip-clang-cxxflags : -std=c++11 -isystem \"/opt/rocm-5.2.1/llvm/lib/clang/14.0.0/include/..\" -isystem /opt/rocm-5.2.1/hsa/include -isystem \"/opt/rocm-5.2.1/include\" -O3\nhip-clang-ldflags : -L\"/opt/rocm-5.2.1/lib\" -O3 -lgcc_s -lgcc -lpthread -lm -lrt\n\n=== Environment Variables\nPATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/home/ian/.local/bin\n\n== Linux Kernel\nHostname : *****Linux***** 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64 GNU/Linux\nNo LSB modules are available.\nDistributor ID:\tDebian\nDescription:\tDebian GNU/Linux 11 (bullseye)\nRelease:\t11\nCodename:\tbullseye\n```\n\nBroken: blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release\nWorked: N/A\n\nBlender crashes when attempting to render more complex scenes on Vega GPU.\n\n[lone monk demo](lone-monk_cycles_and_exposure-node_demo.blend)\n./blender ../lone-monk_cycles_and_exposure-node_demo.blend\nrender on gpu\n\n```\n➜ blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release ./blender ../lone-monk_cycles_and_exposure-node_demo.blend | tee log.txt\nRead prefs: /home/ian/.config/blender/3.3/config/userpref.blend\nRead blend: /home/ian/Downloads/lone-monk_cycles_and_exposure-node_demo.blend\nWARNING: Shader warning [node_vertex_color]: Invalid attribute.\nMemory access fault by GPU node-1 (Agent handle: 0x7f2683fa6400) on address 0x7f2400000000. Reason: Unknown.\n[1] 25965 abort ./blender ../lone-monk_cycles_and_exposure-node_demo.blend | \n 25966 done tee log.txt\n```\n\n```\n:0:rocdevice.cpp :2652: 2702732952 us: 249488: [tid:0x7f1dd0b76640] Device::callbackQueue aborting with error : HSA_STATUS_ERROR_MEMORY_APERTURE_VIOLATION: The agent attempted to access memory beyond the largest legal address. code: 0x29\n[1] 249488 abort ./blender --factory-startup --debug-all\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", "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", "Entire system freezing while using NLA in Blender 2.91 and newer (Mesa only?)\nOperating system: Fedora 33\nGraphics card: Intel HD Graphics 520 (Mesa 20.2.4)\n\nBroken: 2.91\nWorked: 2.90.1\n\nBlender randomly freeze entire graphics system. After freezing, last 2 frames is flickering if you move mouse. I can even save my work with CTRL+S, but after that i need to restart my computer. Setting INTEL_DEBUG=reemit environment variable fixes the issue.\n\nMethod 1\nAdd a few keyframes.\nScroll up and down in the NLA editor.\n[blender-freeze-2.mp4](blender-freeze-2.mp4)\n\nMethod 2\n\nJust do something, even in Solid view, even in Video Sequence editor. I don't know how to reproduce, it happens after 10 minutes of work. Also i notice some glitches in VSE with image strips. Also bug with Depth of Field was fixed in this version, probably this fix relate to this bug.\n\nBug with depth of view that was fixed:\nT77828\n\nIssue with VSE\n[blender-vse-artifacts-1.webm](blender-vse-artifacts-1.webm)" ]

[ "The red part turned into shocking pink\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 555 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.83.0\n\n\n\n" ]

[ "Black Artefacts in EEVEE on Transparent BSDF when using Alpha Hashed for Blend mode and Camera Depth Of Field\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0\n\nBlack Artefacts in EEVEE on Transparent BSDF when using Alpha Hashed for Blend mode and Camera Depth Of Field, if Shader Color is not pure white (similar problem with Layer Weight)\n\n**Exact steps for others to reproduce the error**\n- Open attached file (Just a simple box (can be a plane) with Transparent BSDF. Camera' distance or depth of focus influences the result. Attached pictures in Image Editor from a real case).\n- Press F12 to render\n[transprarent_shader_artifacts_with_camera_DOF1.blend](transprarent_shader_artifacts_with_camera_DOF1.blend)\n\n\n", "Cycles Principled shader Fresnel glitches\nConsistent across 3 diffrent devices and operating systems.\n\nBroken: v2.8 stable\nstill Broken: v2.83 Alpha, 9d90cad3ed39, 2020-01-17 00:13\n\nSpecific combinations of roughness and specular cause weird visual artefacts in cylces, that also look diffrent in contrast to eevee. It is possible for the edges of an object to look brighter or darker, than it's surroundings in a uniformly lit environment or an object appearing darker overall despite only roughness being changed.\n\nUsing all white background to better visiualize artefacts.\nCycles:\n\nEevee:\n\n\nDelete cube+light, set environment to be white color, add spheres, assign principled shader, try out diffrent spec+rough+metal values.\n(Happens on both smooth and flat shaded objects...)\n\nHere's a 2.80 file to try it out:\n[bug_report_principled.blend](bug_report_principled.blend)", "Path Guiding: Cycles in viewport produce inconsistent results\nOperating system: Windows 11\nGraphics card: Geforce 1660S\n\nBroken: 3.5\n\nJust moving the camera around the viewport gives inconsistent cycles renders. I am not sure if it's directly related to path guiding as the issue is only visible in the mirror caustics.\n\n\n\n\n", "Rendering: Engine specific passes show up in other render engines render result\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: Blender 2.83.18, Blender 2.93.6, Blender 3.2.1, Blender 3.4\n\nPasses that were enabled for Cycles show up for eevee/workbench even if they should not.\n\n1. Fresh start-up\n2. Switch to Cycles\n3. Enable all render passes\n4. Switch to Eevee/Workbench\n5. Disable all render passes except `Combined`\n6. Render the image\n7. Notice `Vector`, `Position`, `UV`, etc. in the Pass dropdown\n\nAlternative:\n1. Fresh start-up\n2. Enable all render passes\n3. Switch to Workbench\n4. Render the image\n5. Notice `Vector`, `Position`, `UV`, etc. in the Pass dropdown\n\n[T100319_eevee.blend](T100319_eevee.blend)\n\n[T100319_workbench.blend](T100319_workbench.blend)\n", "Ambiant Occlusion cycle node gives artecacts when the mesh has Custom Split normals\nOperating system: win 10 \nGraphics card: Geforce RTX 2070\n\n**Blender Version** \nBroken: 2.90.0 alpha\nWorked: N/a\n\nOn my mesh , with custom normals, (i applied a withged normal modifier) \nI had to clear the custom split normal date to get rid of artefacts given with the Ambiant Occlusion node in Cycles\n\n\nAlso seen with smooth shader:\n\n\nAnother way to have this bug (without Custom Split normals): \n- Create a suzanne.\n- Smooth the normals \n- Use Cycles render. \n- Add an Ambient occlusion node and plug it on an Emit shader\n[cycles_ao_smooth_normals_bug.blend](cycles_ao_smooth_normals_bug.blend)", "GPencil: Layers used as mask and with viewlayer filter applied are rendered in all passes. \nOperating system: Linux-5.4.43-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.90.0 Alpha\n\n\nLayers, used by other layers as masks, are always rendered when they have a viewlayer filter applied in all render passes.\nI feel a layer used as a mask for other layers and with viewlayer filtering it should work as a mask even when it is not rendered in a pass.\nI don't know if this is intentional, a time limitation, or a complex implementation.\nAssess whether this squares as a bug or feature recuest. Thank you very much for your wonderful work.\n\n- Download the blend file.\n- Note that the layer called \"masc\" is used as a mask for the other two and all layers are filtered in viewlayer filter.\n- Render and note that the mask appears in both passes.\n[GP bugreport viewlayerfilter and layers mask.blend](GP_bugreport_viewlayerfilter_and_layers_mask.blend)\n", "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", "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).", "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)", "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)", "Triangle Mesh Transmission Rendering\nOperating system: Linux-5.10.0-12-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.1.0\nWorked: n/a\n\nDear Blender Devs,\n\nthank you very much for this awesome software. I encountered the following problem while working with some imported triangle meshes.\n\nI tried loading a triangle mesh, removing one side using Geometry Nodes and subsequently using the Solidify modifier to give it depth for the transmission rendering. When looking at the rendered view in the viewport, it looked \"fine\". Since I was dealing with a triangle mesh with some weird connectivity I expected there to be some artifacts. See below.\n\nHowever, when I rendered with F12 (optix), the result was completely different to what I saw in the viewport (also optix). See below.\n\nNote the weird artifact at the back of the object in the F12 rendered version. Normally I would attribute this problem to the \"bad\" triangle mesh and just move on with my life. However, because the F12 rendered version produces different results to the viewport rendered version, I assume that there might be a bug somewhere.\n\n\n- Difficult to explain, see the `.blend` file for an example as it seems to be an issue with this specific triangle mesh.\n\n[viewport_f12_problem.blend](viewport_f12_problem.blend)\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.", "The alpha channel set in Viewport Display settings for an object's material appears as if it's set to 0 when a background image is behind it\nOperating system: Linux x64 (Debian-based)\nGraphics card: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a)\nNvidia drivers, version: 440.31\nKernel: 4.19.0-6-amd64\n\nBroken: v2.81a and v2.80, downloaded from blender.org as a tar.gz\n\nWhen you change the Viewport Display color for an object to have an alpha channel < 1.0 but > 0.0, then manipulate the scene so that there's a reference or background image behind that geometry, the overlapping area will appear completely transparent (alpha 0.0).\n\n\n1. New scene\n2. Add a cube: Shift a -> Mesh -> Cube\n3. Add an image: Shift a -> Image -> Reference (or background)\n4. Select an image\n5. Position the image behind the cube in the viewport. Select the cube.\n6. In the properties panel, select Material Properties\n7. In the Material Properties panel, select Viewport Display\n8. Change the Color to have an alpha between 0.0 and 1.0, exclusive\n\n**Observed behavior**\nLike the screenshots, the overlapping area allows the background image to completely shine through.\n\nQQxLCpv\n\n**Expected behavior**\nThe object will become uniformly translucent and allow the background/reference image to be partially visible, not make the image fully transparent in the overlap.\n\n", "Keyed Particles don't render as expected\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5069\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n[KeyedParticlesJL.blend](KeyedParticlesJL.blend)\n\n- Open file\n- Go to frame 105\n- Render\n- Compare render to viewport\n\nRender is different to viewport\n\nThat's what I expected:\n[ViewportRender.mp4](ViewportRender.mp4)\n\nThat's what I get when rendering with Eevee:\n[EeveeRender.mp4](EeveeRender.mp4)\n\nThat's what I get when renderng with Cycles:\n[CyclesRender.mp4](CyclesRender.mp4)\n", "Default Value for Viewport Display Color's Alpha Wrong.\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 457.09\n\nBroken: version: 2.92.0 Alpha\nAlso tested on 2.83.8 and same problem.\nWorked: It do not think this has ever worked\n\nWhen reverting to the Default Value for Viewport Display Color the alpha gets down to 0.8 making the object semi transparent.\n\nOpen up a new scene.\nSelect the cube.\nGo to the materials tab.\nScroll down to \"Viewport Display\"\nRight Click on \"Color\"\n\"Reset to Default Value\"\nResult: RGB values go back to the default, but Alpha goes to 0.8\n\n\nThank you so much !" ]

[ "Cycles semi transparent materials produce very noisy mist pass\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\n\n\nWhen mix the transparent shader with any other shader using a factor higher than 0 but lower than 1, the mist pass becomes extremely noisy\n\nOpen this file and hit F12 to render a noisy mist pass, even when increase the samples to 1024, the mist pass is still noisy.\n[mist test.blend](mist_test.blend)\n\n\n" ]

[ "Crash after linked object is edited then switched to another scene (object origin scene)\nOperating system: Window10\nGraphics card:\n\n\nBroken: 2.90.1 ( hash: 3e85bb34d0d7 )\nWorked: unknown\n\n\nBlender simply crash and close the window directly after editing the \"linked\" object from 2nd screen and switched back to 1st screen.\n\n\n\nThis error can be reproduced with 2 scenes setup.\n\n- First scene contains a simple mesh object. Let's say a \"Cube\" object\n- Create a second scene.\n- In the first scene, select the \"Cube\" object then \"Make Links\" {key Ctrl L} to 2nd scene.\n- Now, we switch to 2nd scene. The 2nd scene now should contains the same \"linked\" Cube object from 1st scene.\n- Okay, this is important step. In this 2nd scene, we select this \"linked\" Cube object and set the Relations to: *Object > Relations > Make Single User > Object*\n- After that, we go to \"Edit Mode\" for this \"linked\" Cube object.\n- In \"Edit mode\", make a simple change to this \"linked\" Cube object.\n- Once simple change is done, don't do anything else. You just directly switch back to \"First scene\". CRASH here.\n\n", "Evaluate \"Add to Collection\" in Object > Collections panel\nIn the Properies {nav Object tab > Collections}, the '+' icon invokes the *Add to Collection* operator (the button next to it shows the same name, but actually invokes *Link to Collection* - this task is about the '+' button next to it!). \n\n\n\nWhen clicking it a new collection is created (which the name doesn't suggest) and the object moved to it. Problem is, the collection is not linked into the current scene. The user thinks nothing happened. You have to check the Data API or Blender File Outliner display mode to see that a collection was added. There actually is a way to link it to the scene, but it's pretty much hidden (can you find it? :) )\nA fake user is set, so this seems to be deliberate behavior. I assume it was more intended to be used for collection instances, where you might not want to link a collection, only an instance. And it's probably a left over from the old group system.\n\nCould we avoid this confusion?\nWe could just link the collection into the scene. Users can still unlink it. And the operator name could be *Add to New Collection*.", "Action Editor: Animations no longer work after renaming bones.\n**Information & Blender version**\nWindows 10, 64 bit, CPU integrated/no graphics card [doubt it's relevant but: AMD A8-7600 Radeon R7]\nBroken Blender Version: 3.3.0, master, 2022-09-06, hash: 0759f671ce1f\nNo idea if it worked in a previous Blender version.\n\n**Description**\nThis happens while using Action Editor and creating several actions to store different animations.\nIf at some point you rename bones, the action that is currently active will automatically update it's paths and continue to work, but any previous actions will not update their path and the animation will no longer play. \n\nFixing it requires either:\n1) manually changing the name of each affected path through the graph editor.\n2) Select the bone, select the affected channel under the action summary, temporarily change the name back to what it used to be, then change it again to the new name. This way the path gets updated.\n\n\n**Reproduce Error & File**\nYou'll need to create at least 1 bone first.\nCreate an action [dope sheet/action editor] and make an animation.\nCreate a new action, make a new animation, and change the name of the bone. The action that is currently active continues to work, but any previous actions now have a broken path and no longer work.\n\nIn this file I made 2 actions with different animations, I had \"Action 1\" active while I renamed the bone form \"Box\" to \"Bone\". Now \"Action 1\" continues to work, while \"Action 2\" no longer plays.\n\nFor this test I changed the name of the bone while in pose mode through Bone Properties.\n\n**Important note: This seems to not happen all the time, I'm not sure why.**\nWhile making this file to recreate the issue, I first created both actions actions and animations, and I had \"Action 2\" active when I changed the bone's name from \"Bone\" to \"Box\". This seemed to create the error for a moment, but when I changed from \"Action 2\" to \"Action 1\" and back to \"Action 2\" it resolved itself and I was able to see both animations.\nI then had \"Action 1\" active while I changed the name of the bone from \"Box\" to \"Bone\", and now the error persisted. [even after closing and reopening the file]\n\nI made the test again with a new file [not attached] and the error persisted, I saved the file, closed it, and after re-opening the file the error was gone.\nSo it seems sometimes the paths get updated automatically and other times they don't.\n\n[BrokenActionTest.blend](BrokenActionTest.blend)", "Pose Library: Collection pop-up when creating new poses in Action Editor\nWhen creating poses from the Action Editor it should be explicit to which catalog the new asset should be added.\n\nBy default the Unassigned option should be highlighted, so users can post-pone this decision for later, similar to when marking data-blocks as assets.\n\nThis is part of #103265.\n\n---\n\nSome initial code snippets for anyone interested on tackling this: [P3408](P3408.txt)", "File Output nodes output gets overwritten by \"standard\" output (if the same filename is used)\nI have a scene with simple animation. \nI'm rendering muilti-layer open exr with an composite output node with the passes as in them. \nThe standard file 5 year old output bug is still here, where your file saves twice, once from the main file output tab and again on your composite output, normally I don't care whatever, it will just overwrite and I'll end up with one file. \n\nAfter setting up my render output with all the layers I want, normally I just let the overwrite button on regular output be set and it's fine. However all my passes in the exr file were changed to VeiwLayer.(pass), and I'm missing passes like image and alpha or others I might composite into the composite output node. \n\nMy work around is to make the file name something different than my composite output vs the normal file output name. \nBut now I'm saving twice and having to deal with deleting 100s of gigs of junk EXR files from the main file output tab. \n\nIf you render one frame from the file I uploaded, then drop it into a compositor like nuke, fusion or cough cough AE, you'll see the passes are different. \nP.S. You can kill the textures, sorry I didn't pack them for size sake\n\nThank you\n\nblender 3.6 \nFile SYS - (although it seems to be the case on multiple machines, so I thinks it's just an overlook bug): \nryzen 9 5950x\n128 gigs ddr4\nrtx 4090\n\nAnd \nM1max 64 gig integrated\n\n", "ID Deduplication on Append - UX \nThis task is about which behavior should be default when linking/appending IDs, and assets, and how much/how users should be able to customize those behaviors.\n\nNOTE: Currently this is mostly listing topics to be discussed. This is also a first pass, there are likely many more use cases/topics to be discussed.\n\n# Problem\nCurrently, when appending a data-block, Blender appends (i.e. link and make local) the ID and all of its dependencies.\n\nThis means that if a single object in appended ten times, you will get ten copies of the object, but also of its meshes, materials, animations, etc.\n\nThis behavior may be fine in some cases, but not in others.\n\n# Default Behaviors\n## Generic Considerations\nTo avoid having many copies of the same ID, the first appended copy needs to be re-used for the subsequent appends.\n# Do we always re-use that ID, even if it has already been modified by the user locally?\n *Think first appended ID should always be re-used, reliably detecting modified IDs compared to linked one is possible, but tricky and not very efficient (RNA diffing)... There could be a mechanism though to break that reference such that next append creates a new copy of it.* **No diffing.** User has ways to make an existing local ID not re-usable anymore, and to force not re-using an ID when appending again. \n# ~~Could we use the UserPreferences settings for data copying, to decide which ID types we systematically create new copies for, and which ID types we try to re-use previously appended ID?~~\n\n## Specific Cases\nHere is a list of different use cases, possible behaviors being:\n* Link.\n* Append (Link + Make Local, aka new copy).\n* Re-use of previously appended local ID.\n\n### Append Material\n| Data type | DEFAULT | Alternative Behavior 1 |\n| --- | --- | --- |\n| Material itself: | re-use | *duplicate* |\n| Image: | NA | re-use |\n| Node groups: | NA | *duplicate* |\n| Actions: | NA | *duplicate* |\n\n### Append Object\n| Data type | DEFAULT | Alternative Behavior 1 |\n| --- | --- | --- |\n| Object itself: | *duplicate* | *duplicate* |\n| Obdata: | re-use | *duplicate* |\n| Actions: | re-use | *duplicate* |\n| Materials: | re-use | Apply Materials Rules ? |\n\n### Append Collection\n**Collection itself:*** In case of Empty-based instantiation:\n***In case of ViewLayer-based instantiation:** Object: *same as above for Object case?*\n\n# User Customization\n## Change behavior in UserSettings\nShould user be able to change default behavior in user settings, or only on a case-by-case basis when actually linking/appending IDs or assets?\n\n## Change Behavior in Asset/File browsers\nShould user be able to toggle options like \"Link everything\", or \"Never deduplicate\" ? etc.\n", "Add UUID to Blender data-blocks\nHaving UUIDs to reference data-blocks of Blender would help in some cases with interaction with third party tools, especially when relations between different types of data storage is needed, and handling renaming of data-blocks across those is not possible.\n\nThis design task is here to define what would be expected from such feature, and how various issues should be addressed.\n\nSee also this [ML discussion](https:*lists.blender.org/pipermail/bf-committers/2020-November/050751.html).*Disclaimer: this is a **draft** design proposal currently.// \n\nCore Ideas\n----------\n\n* UUIDs should be 'real' ones, 128bits long.\n* UUIDs should be generated on demand, not systematically. *This process is not free, and internal handling of data-blocks by Blender itself should not use them at all.*\n** Think we should still store them as a systematic fixed chunk of data in the ID block in the .blend file though (being zeroed for non-generated ones), to ease their retrieval from third-party code 'parsing' .blend files?\n\nIssues to Investigate\n-------\n\n# Collision and Uniqueness\n**UUIDs should be absolutely unique withing a .blend file. *This would be easy to ensure.**Linked**data-block would not be concerned by this, since they belong to another .blend file.*** UUIDs should be reasonably unique across .blend files.\n***Creating new IDs from existing ones (internal copy, appending from a library, creating proxies or overrides from linked data) should nullify the UUID of the new data-block.*** 'Save file' operations explicitly creating a duplicate file (Save as, Save copy) should maybe enforce re-generating UUIDs?\n*** .blend file duplication would be the main source of collision. Not sure how to deal with that case, besides offering the possibility of a manual re-generation of UUIDs by user?\n*** If the 'file copy' case is solved, collision between different .blend files remains possible, though extremely unlikely.\n# Runtime IDs\n**Some system may generate a random number of data-blocks in a procedural way (e.g. from future geometry nodes evaluation.*** Persistence of UUID in such IDs is probably not possible? We should then accept that it would need to be re-generated when nodetree re-create data-blocks?\n*** This only concerns IDs that would be generated in Main database (and hence saved on disk), not runtime IDs.\n\nImplementation Hints\n---------\n\n* Search for existing implementations of UUIDs (e.g. in python).\n* Using OS-provided tools should be preferred solution as much as possible.\n* How should RNA (Py API) expose those 128bits UUIDs, as an array of 4 integers? An hexadecimal-encoded string?", "Compositor: canvas and transforms\n## Motivation\n\nThe tiled, full-frame and realtime compositors currently behave differently regarding transforms. See [A Comparative Look At Compositor Systems In Blender](attachment) created by @OmarEmaraDev. `COM_domain.hh` in the realtime compositor also has good information on the current workings of that system.\n\nWe need consistent behavior across CPU and GPU compositing, and decide on the right behavior. Ideally we would like support all of the following:\n\n* 3D viewport and final render should give consistent results relative to the camera frame.\n* Automatic resolution independence for previewing or outputting and different resolutions.\n* Overscan, where pixels exist beyond the frame for flexibility in compositing and avoiding border artifacts.\n* Border render, where a render is only a subset of the full frame.\n* Combining multiple images with different transforms on a shared canvas.\n* Avoid clipping and losing image resolution where possible.\n* OpenEXR data and display windows.\n* Execute node graph in easy to understand way, without unexpected behavior.\n\n## Proposal\n\n### Data and Display Windows\n\nEvery image used in compositing is placed on an infinite canvas, and has the following properties:\n* Data window: bounding box for the part of the canvas that contains pixel data.\n* Display window: bounding box for the part of the image that will be displayed or output.\n\nThe data window may be bigger (for overscan) or smaller (for border render) than the display window. See the [OpenEXR docs](TechnicalIntroduction.html#overview-of-the-openexr-file-format) for illustrations.\n\nBy making this distinction, transform nodes can translate, rotate and scale images without clipping data that falls outside the display window. Such transforms would change the data window but not the display window.\n\n### Combining Images\n\nAll images that go into the compositor are placed on the same infinite canvas. Nodes like mix and alpha over by default output a data window that is the union of the two bounding boxes. However there can also be an option to use the intersection, or use the data window from either image.\n\nThe display window would be taken from the primary image input.\n\n### Realizing Transforms\n\nThe realtime compositor has a mechanism where affine transforms and wrapping are not immediately applied after every node. Rather they are stored as part of the image, and realized when an operation is performed that needs it.\n\nThis mechanism can remain, but clipping can be avoided by writing to a data window that may be partially or fully outside the display window.\n\nOne thing that we found confusing in its current behavior is that the transform is not realized before filter nodes like blur. That means rotating an image 90° and then applying a horizontal blur, the image is blurred vertically in global space. We suggest realizing such transforms before filter nodes. If users want the existing behavior, they can place the blur node before the rotation.\n\n### Performance and User Control\n\nWhile the data window avoids losing data, it can also lead to high memory usage as users may (accidentally) make node setups that occupy many pixels outside the display window.\n\nThere are no ideal solutions for this, but we can think of ways to mitigate this:\n* Nodes that work on a single image could have settings to keep the data window unchanged.\n* Nodes that work on multiple images could have a setting to use the data window from just one of them.\n* A default limit on data windows, set to some % beyond the display window?\n\n### Resolution Independence\n\nNodes should generally not use pixel coordinates, but rather coordinates relative to the image size or output size. The reason being that while changing the render resolution percentage could scale the size in pixel coordinates, this would not work when the user changes the render resolution.\n\nCompositing nodes should be evaluated at a known resolution factor, either taken from the render resolution percentage, or computed automatically from the 3D viewport size. Images coming into the compositor should then be scaled and translated appropriately to match.\n\n### Viewing and Editing Windows\n\nWhen using the viewer nodes, there should be a visual indication of what the data and display windows are in the resulting image.\n\nThere should also be nodes to modify the display window, and to clip the data window to the display window or non-empty pixels.\n\n### Open Questions\n\n* Data windows and display windows may be difficult to understand for users. Are there ways to make this easier to understand, or defaults that mean users don't have to think about them much in simple cases?\n* Can we find better terminology? The current terms come mainly from OpenEXR, and are also used in e.g. OpenImageIO. Another compositing application calls data window \"bounding box\" and display window \"format\". Image editors have some similar concepts where a layer may only take up part of the canvas, but I could not find a clear enough correspondence between concept to share terminology.\n* This design assumes the display window is coming from the input render data or camera footage, and the compositor output will just follow this. But render output may expect a particular resolution, and some things may be simplified if the whole compositing nodes would use the display window from the render output. Still some other compositors seem to offer flexibility where the display window does not have to be the same throughout. What is the best solution here? Would it make sense to adapt any input images to the render output display window by default, and then make it an option to not do that for advanced users?\n* Should nodes like blur also extend the data window automatically? This could be helpful for example if you want to blur an element you want to composite over another image, without having to manually increase its size first. On the other hand if you apply depth of field or motion blur to a complete render and not just an individual element, that's not what you want.", "Outliner: Linking object hierachies to a collection is buggy\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX Vega ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 2.93.2 Release Candidate\nWorked: Unknown\nLinking objects with parent child relationship has inconsistent display behaviour in outliner\n\nThis bugreport is about linking an object in the outliner to an additional collection. \n\nA linked object can have children. Normally they are displayed in a greyed out state until they are also linked to the same collection as the parent. But there is a bug or at least an inconsistent behaviour if these childs are displayed in a greyed out state or not at all.\n\n\nThe following script adds 3 cubes ,creates a collection and links the cubes to it. \nI deleted everything from the Scene Collection and did run the script. \n\nThis will work: \n\nBut just one more child-level in the tree and it starts to behave inconsistent as can be seen in the outliner shown in the screenshot of some reruns of the same script on a totally empty scene. \n\n\n\n\n\n\n\n\n\n```\n\nimport bpy\n\n# create some cubes\nbpy.ops.mesh.primitive_cube_add(location=(0,0,0))\ncube0= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(5,0,0))\ncube1= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(10,0,0))\ncube2= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(10,0,0))\ncube3= bpy.context.active_object\n\n#create a new coll\ncollection = bpy.data.collections.new(\"Test\")\nbpy.context.scene.collection.children.link(collection)\n\n# establish parent child relationships\n\ncube1.parent = cube0\ncube2.parent = cube1\ncube3.parent = cube2\n\n# link root cube to new coll\ncollection.objects.link(cube0)\n\n\n```\n\n\n", "Usability issues with old group operators\nBroken: 2.79, 2.8x\n\n\nWhen using linked objects, all the Group commands [Remove From Group / Remove From All Groups / Add Selected To Active Group / Remove Selected From Active Group] except [Create New Group (Ctrl G)], do nothing\n\n\nIn my particular usage, I link a scene from one file into my main scene, afterwards I create a [New scene with Link Objects] from the Linked scene. \n\n [GroupsFail.blend](GroupsFail.blend)\n [GroupsFail-MainScene.blend](GroupsFail-MainScene.blend)\n\nI can Create Groups by selected objects, and I can remove the group from the object in the Object Properties tab but the only way to remove multiple groups is through python script or deleting the group itself.\n\nSince this report is used to more generally handle issues with the old group operators and other reports have already been merged here, will also list these:\n- Ctrl G is placing new collections inside \"Orphan Data\"", "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", "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)", "NLA: Action Track Hold Forward Inconsistency\nBug Report: #66946 (NLA strip unexpectedly auto-switching from Hold to Hold Forward)\n\n**Problem:** For the Action Track (non pushed action), extrapolation `None` and `Hold` is respected but `Hold_Forward` is not. It's a source of confusion. \n\n**Solution:** [Originally proposed by angavrilov]]. We treat extrapolation `Hold_Forward` as bounded on the left and infinite on the right.*FModifiers note:*It's important to note that the Action Track does not evaluate the same as normal strips which is [[https:*developer.blender.org/T66946#723602 |intentional](https:*developer.blender.org/T66946#724251). FModifiers will affect the track's boundaries so keyframes don't necessarily define the Action Track's evaluation bounds. So adding a default cyclic modifier to channels effectively makes the Action Track's evaluation bounds infinite. Even extrapolation `None` in this case appears to not work properly. This behavior is still intentional even though it appears broken. The user-side solution is to restrict the modifier's frame range. ", "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)", "Keyed particles work on viewport but not in render, also they are not affected by force fields\nOperating system: Linux-4.15.0-20-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Haswell Desktop Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.2.8\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nWhen making a particle system with keyed physics, it works in viewport but the particles do not show properly in the final render. They reappear from the world center when all the previous particles die. Also the particles of the keyed particle system are not affected by force fields.\n\nSee the link for screen recording and the sample file.\n\nThe problem shows in blender 2.80 and 2.81 but not in 2.79.\n\nI think this might be a bug in blender 2.8 but I hope you can help me to solve it.\n\nscreencast\n\nview?usp=sharing\n\n**Steps to reproduce:**\n[#69238.blend](T69238.blend)\n\n- Open file\n- Render animation\n- Compare output to viewport\n\n\n\n\n\n" ]

[ "Difficult to play an animation with a proxy\n**Category**: Animation\n\n\n%%%I have a rigged character in one file. I link it as a group to another, add a proxy for the armature, and animate it. How should I get the action to play in the bge?\n\nMy first attempt was to add an action actuator to the proxy object, but it doesn't do anything. That's what this bug report is about: should it do something?\n\nIn the end, I have decided to go with dfelinto's method: have the action actuator on the original armature object in the library, and set which action to play with a message. Both techniques are illustrated in the attached files:\n\n - character.blend is the library file, containing the mesh and armature. There are two groups: G_ok and G_bug; G_bug has no logic attached to it, while G_ok uses a message sensor and a short script to play the action.\n - game.blend uses the library file, pulling in G_ok and G_bug as groups. A proxy armature is made for each group; these share an action, \"proxyAction\". Both objects animate in the 3D view, but only G_ok works in the game engine.\n\nActually, I think using the set-up in G_ok is the only way that makes sense: having logic bricks on the proxy object would be weird, because it's not clear what role it plays in the scene. Is it even converted? However, maybe there should be an easier way to do this that doesn't involve any Python.\n\nTested in Blender 2.63.2, r46163.%%%" ]

[ "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.", "Mesh related crash in add-on\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 780 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.0.0 Alpha\n\nUsing an the operation connect spread in an addon is causing an EXCEPTION_ACCESS_VIOLATION. \n\n[blender.crash.txt](blender.crash.txt)\n\n```\nStack trace:\nblender.exe :0x00007FF7A109EC60 blender::deg::deg_graph_flush_updates\nblender.exe :0x00007FF7A1084AA0 DEG_evaluate_on_refresh\nblender.exe :0x00007FF79C983790 scene_graph_update_tagged\nblender.exe :0x00007FF79CB61510 wm_event_do_notifiers\nblender.exe :0x00007FF79CB4B550 WM_main\nblender.exe :0x00007FF79C7E2ED0 main\nblender.exe :0x00007FF7A16421A8 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFEEB937020 BaseThreadInitThunk\nntdll.dll :0x00007FFEECA62630 RtlUserThreadStart\n```\n\nDownload [Forgotten Tools ](forgotten_tools_0_5_0.zip) use Connect spread on 2+ edges go to operation popup menu increase the cuts.\n\n[2021-06-20_00-26-23.mp4](2021-06-20_00-26-23.mp4)\n\n", "Error: Illegal address in CUDA queue copy_from_device\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\n\nWhen rendering in GPU mode, Render crashes.\n\nAttached Blend File\nAny frame after 1150 crashes on render with the title error for us.\nTry rendering frame 1160 - This one crashes for me all the time.\n\n", "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", "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", "Error \"Gizmos hidden in this view\" when trying to delete with measure tool and gizmos disabled\nOperating system: Windows 10 64 bit\n\nBroken: 2.83 release, 2.90 ec776f18ff70\nWorked: blender-2.82a-windows64\n\nIf the \"Measure\" tool is selected AND gizmos are turned off (\"Show Gizmo\", in the top right next to \"Overlays\"), trying to delete with the X Shortcut will result in the error \"Gizmos hidden in this view\".\nIf either\n* another tool is selected, or\n* gizmos are enabled\ndeleting works as expected.\n\n[delete_without_gizmo.blend](delete_without_gizmo.blend)\nOpen the file.\nHit the X key.\n\n", "Line Art errors when rendering small details\nOperating system: Linux-5.15.5-76051505-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.0.1\nBroken: version: 3.1.0 Beta\nBroken: version: 3.2.0 Alpha\n\nWorked: version: 2.93.8\n\nLine art when rendering fine edge mark details now produces errors that were not present in 2.93.\n\n**Example of Error**\n{[F12864446](3.0_World_Space.png)}\n\n**Expected Results**\n{[F12864444](2.93_Screen_Space.png)}\n\n\nEXAMPLE BEND FILE: [Line Art Fine Detail Error.zip](Line_Art_Fine_Detail_Error.zip)\n1. Open Example File \n2. Ensure Line Art is enabled\n3. Render Image\n\n", "No space mouse support in --debug mode\nOperating system: macOS 12.6.7\nGraphics card: Apple M1 Max GPU\n\nBroken: 3.6.1\n\nConnexion Space Mouse does not work if Blender is launched with --debug.\nNormal launch works.\nIs this related to #93170 ?\n\nLaunch Blender with --debug\nTry to use Space Mouse\n\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.", "Application templates crashes if the startup.blend of the application template contains scene named \"Asset\"\nOperating system: Windows-10-10.0.22621-SP0'\nGraphics card: NVIDIA GeForce RTX 2070 Super with Max-Q Design/PCIe/SSE2\n\nBroken: 3.5.1 2023-04-24 18:00 e1ccd9d4a1d3\nWorked: Never\n\nApplication templates that contain certain pattern in startup.blend lead to Blender to crash.\nApparently occurs when the scene is created with the name \"Asset\" and used as a application template.\n\n- Download attached [MCE.zip](attachment) file\n- Install the attached application template file (`Blender` menu > `Install Application Template...`).\n- Load it (choose the new \"MCE\" option in `File` > `New`).\n\nBlender crashes.\n\nAttached also the `blender.crash.txt` and another template.\n\n[MCE.zip](attachment)", "Blender 2.8 and 2.81 (ab519b91b2c4) has high chance of crashing when using Python to create a new node-tree link.\nOperating system: Windows 10 (x64) v1903 Build 18362.356\nGraphics card: Nvidia GeForce GTX 1060 6GB\nCPU: Intel Core i5 7600K\n\nBroken: 2.81-ab519b91b2c4 **AND** 2.80 release\n\nCreating a new node-tree link via Python sometimes causes Blender to crash with the error \"EXCEPTION_ACCESS_VIOLATION\".\nI have attached a .blend file that will cause the crash, just by clicking \"Run Script\" once or twice. \nWhen I found the bug, I spent some time making the script as small as possible while still causing the crash, so the script is less than 30 lines.\n\nI also installed Blender 2.81-ab519b91b2c4 on a Windows 10 laptop that had never seen Blender before, and the bug was present on there too, so I'm confident the issue isn't specifically due to my hardware.\nI've also included blender_debug_output.txt and blender_system_info.txt, generated by the blender_debug_log.cmd file included in the Blender 2.81 download.\n\n1) Open the attached .blend file.\n2) Click \"Run Script\" in the bottom right of the text editor pane.\n3) Repeat 2 until crash (should only take 1 or 2 tries)\n\n[Crashy crash.blend](Crashy_crash.blend)\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "PyAPI: template_modifiers doesn't work in the viewport\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\nThis was working outside the context of the Properties Editor prior to 9b099c8612 -- when it was still template_modifier(md).\n\nDisplaying the dafault modifier layout doesn't work in the viewport (in the sidebar or in a popup). template_modifiers() gives errors:\nPanel type 'MOD_PT_Array' not found.\nPanel type 'MOD_PT_Bevel' not found.\nPanel type 'MOD_PT_SimpleDeform' not found.\n... \n(interface_panel.c, line 292)\n\nBased on the attached file:\n1. Run the script in the text editor to create a panel in the sidebar called \"Modifiers\"\n2. Verify that the modifiers don't show up and there are errors in the console\n3. Click the \"Modifier Popup\" button\n4. Same thing should happen with the popup\n\n[template_modifiers_bug.blend](template_modifiers_bug.blend)\n", "Laucnh error since version 3.4\nOperating system: High Sierra 10.13.6\nGraphics card: ATI 6970M 2 GB RAM\n\nBroken: (example: 3.4 and 3.4.1 2022-12-20, master)\nWorked: (Blender 3.3.1)\n\nWhen I launch blender a get this error that I have found others on the web reporting also on similar setups:\nError opening window.\nFailed to create metal device for offscreen GHOST Context.\n \n\nPrevious versions worked a charm and I really hope 3.3.1 wont be the last version for my humble setup.\n\nThanks and as always appreciate your amazing work!", "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", "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" ]

[ "Error\nOperating system: Windows 10 Pro\nGraphics card: GeForce 1070 Ti\n\n**2.80**\n\n\n**Traceback (most recent call last):\n```\nFile \"C:\\Program Files\\Blender Foundation\\Blender\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 524, in execute\n value = context_path_validate(context, data_path)\nFile \"C:\\Program Files\\Blender Foundation\\Blender\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 83, in context_path_validate\n value = eval(\"context.%s\" % data_path) if data_path else Ellipsis\nFile \"<string>\", line 1\n context.(null).down_cat\n ^\n```\nSyntaxError: invalid syntax\n\nlocation: <unknown location>:-1\n\nlocation: <unknown location>:-1**\n", "selection error\nOperating system: Windows 10\nGraphics card:![Blender_ [E__Warriors-the game_untitled.blend] 05.08.2019 10_57_52.png](Blender___E__Warriors-the_game_untitled.blend__05.08.2019_10_57_52.png)\n\nBroken: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen\nWorked:\n\nWhen I click on the object, makes an error\n", "How can i fix this but we i open it i cant select thing and gives me a error message\nTraceback (most recent call last):\n```\nFile \"D:\\Blenderapp\\2.82\\scripts\\startup\\bl_operators\\wm.py\", line 525, in execute\n value = context_path_validate(context, data_path)\nFile \"D:\\Blenderapp\\2.82\\scripts\\startup\\bl_operators\\wm.py\", line 84, in context_path_validate\n value = eval(\"context.%s\" % data_path) if data_path else Ellipsis\nFile \"<string>\", line 1, in <module>\n```\nAttributeError: 'SpaceInfo' object has no attribute 'context'\n\nlocation: <unknown location>:-1\n\n", "Error in every click\nOperating system: Windows 10\nGraphics card: Radeon (TM) 530\n\nBroken: 2.80.75\nShows no error in 2.79 and down\n\nWhenever I click anything on the screen, this error shows up. I also uninstall and reinstall the blender, but nothing works. this only happens in general, VFX and video editing.\n\n1. Click anything on the screen.\n\nHere's the screenshot of the error: ovtgtj", "Error after assigning operation to a shortcut\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.94\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nAfter assigning a shortcut \"SHIFT+Z\" to Viewport Shading: Rendered in Preferences>Keymap (I generally use new shortcuts, but I didn't like not having this one) and pressing SHIFT+Z, an error appears. The error does not appear when changing to Rendered Shading Mode without using the shortcut.\n\n1. Go to Edit>Preferences>Keymap\n2. Type \"Shading\" into the filter, delete Shading keymap and change Toggle Shading Type keymap from SHIFT+Z to Z. Close Preferences window.\n3. In 3D Viewport, find Viewport Shading: Rendered icon (the rightmost sphere icon), right-click it and change its shortcut to SHIFT+Z.\n4. Press SHIFT+Z.\n[Based on the default startup setup]\n\n", "Bug line 524, line 83\nOperating system: Windows 10\nGraphics card: AMD A8-3500M APU with Radeon(tm) HD Graphics 1.50 Ghz\n\nBroken: 2.80\n\n\n\nHello! Help solve the problem. The problem starts because if I start to actively use third-party add-ons, although after the program is completely reset to the initial settings, the problem disappears only for a while. Later, an error appears when trying to select an object in the scene.\n\nI enclose the error text:\n\nTraceback (most recent call last):\n```\nFile \"D:\\╨Я╤А╨╛╨│╤А╨░╨╝╨╝╤Л\\╨С╨╗╨╡╨╜╨┤╨╡╤А\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 524, in execute\n value = context_path_validate(context, data_path)\nFile \"D:\\╨Я╤А╨╛╨│╤А╨░╨╝╨╝╤Л\\╨С╨╗╨╡╨╜╨┤╨╡╤А\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 83, in context_path_validate\n value = eval(\"context.%s\" % data_path) if data_path else Ellipsis\nFile \"<string>\", line 1\n context.(null).shading.type\n ^\n```\nSyntaxError: invalid syntax\n\nlocation: <unknown location>:-1\n\nlocation: <unknown location>:-1\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Traceback\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\n", "Context error \nIf you assign a key here for example the end and click it in another window, you get an error.\n\n \n\n\n\nthe same thing here if assigned and cause a 3D view for example there will be an error.\n\nIt can be correct if it should not be called where it is not available, it simply does nothing when a button is pressed?", "Traceback and now I cant use blender\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Quadro P5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.02\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nI left click anywhere and the error pops up. I am new to blender and i don't know what i did to get here. The last thing i can remember is pressing Control-Z and this showing up. from then on i cant use blender. The error take priority. Then if i click a few more times Blender Freezes and says not responding.\n\n**This is the Error i get and i cant do anything. no matter where I click in the view port it pops up. Even if i close blender and restart it**\n\nTraceback (most recent call last):\n```\nFile \"C:\\Program Files\\Blender Foundation\\Blender\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 524, in execute\n value = context_path_validate(context, data_path)\nFile \"C:\\Program Files\\Blender Foundation\\Blender\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 83, in context_path_validate\n value = eval(\"context.%s\" % data_path) if data_path else Ellipsis\nFile \"<string>\", line 1\n context.(null).type\n ^\n```\nSyntaxError: invalid syntax\n\nlocation: <unknown location>:-1\n\nlocation: <unknown location>:-1\n", "Runtime syntax error when attempting to select object\nOperating system: Windows 10\nGraphics card: GTX 1050 Ti\n\nversion: 2.80 (sub 74), branch: master, commit date: 2019-06-29 20:58, hash: be060c3990ad, type: Release\nbuild date: 29/06/2019, 17:58\n\n\n\n```\nTraceback (most recent call last):\n File \"C:\\Users\\Xavier\\Desktop\\blender-2.80.0-git.dd3f5186260e-windows64\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 524, in execute\n value = context_path_validate(context, data_path)\n File \"C:\\Users\\Xavier\\Desktop\\blender-2.80.0-git.dd3f5186260e-windows64\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 83, in context_path_validate\n value = eval(\"context.%s\" % data_path) if data_path else Ellipsis\n File \"<string>\", line 1\n context.(null).shading.type\n ^\nSyntaxError: invalid syntax\n\nlocation: <unknown location>:-1\n\nlocation: <unknown location>:-1\n```\n\n\n**Edit:**\n\n\n - Default startup file, load factory settings\n - Right click one of the show X-Ray `shading.show_xray` / Shading option toggle buttons at the top right and click `assign shortcut` and left click (Or right click depending on your select key map) _inside_ the `Press a key` button ( Image: 2jee3et.png )\n - Left/right click in the viewport, dope sheet, UV editor, shader graph and the error should occur\n - Notice now as well that we are unable to re-assign the shortcut for this particular action through the context menu: ( Image: 2jywAjH.png )\n\nAfter exporting the keymap, this can be found:\n```\n (\"wm.context_menu_enum\",\n {\"type\": 'RIGHTMOUSE', \"value\": 'PRESS'},\n {\"properties\":\n [(\"data_path\", '(null).shading.type'),\n ],\n },\n ),\n```", "Crash:Traceback most recent call last\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 20.2.2 26.20.15019.19000\n\nBroken: version: 2.82 (sub 7)\nWorked: (\n\nWhen I put a model, then I will press it and I get a tracking error (the last recent call) and many files, after that it does not let me do anything, every time I press something I get the error.\n\n\n\n\n\n", "wm.py bug\n[wm.py](wm.py)\n\n{[F7795415](Blender_Bug.JPG)}Operating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nWhen I click wherever on the interface it spawns the message I attached.\n\nI do not know. It happened out of the blue with no reason. Sorry\n\n", "Left click issue\nOperating system: macOS Mojave v10.14\nGraphics card: Intel HD Graphics 5000 1536 MB\n\nBroken: 2.80\nWorked: (optional)\n\n**Using the trackpad on a MacBook, a left click almost anywhere in the program will produce the following error message: {[F7657686](Screen_Shot_2019-08-09_at_11.08.15_PM.png)}**\n\n**The above error message appears when left-clicking anywhere in the 3D viewport, or on a file in the file browser, or an object in the Outliner, or nodes in the Shader Editor. When object select is set to left-click, the error message appears and blocks me from selecting objects. I am using the trackpad on an Apple MacBook, 13-inch, early 2014.**", "Assigning shortcut to editor properties gives errors\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: AMD Radeon R5 M230 Series ATI Technologies Inc. 4.5.13464 Core Profile Context 21.19.407.0\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nEverytime I open blender and click anything in the object mode, the program reports to me an error and it's very annoying.\nI'll write the entire report:\n\n```\n File \"D:\\Blender\\blender-2.80.0-git.cc600de6695a-windows64\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 332, in execute if context_path_validate(context, data_path) is Ellipsis:\n File \"D:\\Blender\\blender-2.80.0-git.cc600de6695a-windows64\\2.80\\scripts\\startup\\bl_operators\\wm.py\", line 75, in context_path_validate value = eval(\"context.%s\" data_path) if data_path else Ellipsis\n File \"<string>\", line 1\n context.(null).shading.show_xray\n ^\n SintaxError: invalid syntax\n```\n\n```\n location: <unkown location>:-1\n```\n\nRight click on \"Show whole scene transparent\" -> \"Assign Shortcut\" -> I clicked \"Dash\" key \n\n[help.blend](help.blend)\n\n" ]

[ "Color attributes difference between vertexpaint and sculpt modes\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 512.15\n\nBroken: version: 3.2.0 Beta\n\nColor attributes difference between vertexpaint and sculpt modes\n\n[vertex_paint_geo_nodes.blend](vertex_paint_geo_nodes.blend)\n\n- open the included blend file and try to remove the instance objects from the geo nodes (The objects are linked to a color attribute. Using white color to add the objects and black to remove them)\n- when using vertexpaint mode, several pure black strokes are required\n- when using sculptmode paint tool, trees vanish on the first black stroke stroke- when i open blender 3.1 it works fine. \n\n\n\n", "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", "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", "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\"", "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", "Material Node Groups bug connections with shortcut \"F\"\n**System Information - Intel Core i5-4590 CPU 3.3GHz 16 RAM**\nOperating system: Windows 8.1 64, and graphics card: NVIDIA GeForce GTX 760\n\n\nBroken: 2.76b f337fea\n\n\nMaterial Node Groups bug connections with shortcut \"F\"\n\n\n1. Make Group Node\n2. Select Node Output with Shift\n3. Select Group Output Node with Shift\n4. Press \"F\" - first pair connected\n5. Repeat step 2 and 3 for next nodes\n6. Nodes not connected and can not even connect manualy\n[bug_nodes.blend](bug_nodes.blend)\n", "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.", "Cycles: point cloud geometry improvements\n[D9887: Cycles: pointcloud geometry type](D9887)\n\nImprovements:\n- [x] Point Info node with radius, position, random\n- [ ] Backfaces are ignored (like curves), which means e.g. volumes inside points don't work.\n- [ ] Render as normal or ray oriented disc (see [D9887](D9887)#289012, [P2125](P2125.txt))\n- [ ] Baked shadow transparency support like hair? But must be optional since texturing alpha across the sphere/disc is useful.", "Geometry Node: Filter out based on subtype (modifier/tool)\nWe need to filter out the nodegroups based on subtype (tool/modifier):\n\n* Template in the Geometry Nodes editor header\n* Template in the Geometry Nodes modifier\n\nNote that the Node Group node template can still take both type of node groups.\n\n", "Ghost / False Node inputs\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40\n\nBroken: version: 3.1, 3.2, 3.3\n\nWhen the output type of a node changes:\n\nVector Math multiply (vector output) ----> Vector Math distance (float output)\n\nIt causes the node that has the changing type as it's input to be in a bugged state.\n\n* Open .blend file\n[ghost_inputs.blend](ghost_inputs.blend)\n* Change the multiply to distance (easiest one I could think of)\n* The other math node will be in a messed up state\n\n* You can even drag from the ghost input and you will be able to see that Blender thinks it is still connected.\nThanks!", "UV: Modified Edges UV overlay don't show on generated Mesh from Geometry Nodes\nBroken: version: 3.6.0\n\n\"Modified Edges\" UV Option does not work when there is Join Node or primitives is used to generate geometry.\n\nIn setup like this, where we generate UVs in GN, and have \"Modified Edges\" overlay work correctly.\n\n\n\nWhen we generate geometry eg. by using Join Node, or Primitives. Overlay no longer works (even in UV sync mode where all UVs should be shown)\n\n\n\n\nI'm not sure if its desired behavior because eg. some setup do work when we modify and not generate new geometry.\n\n\n--\n\n(that's the overlay if someone is not aware of its existence :p)\n\n\n- Open attached .blend file. (Note that the UV for \"Modified Edges\" is showing as expected)\n- Unmute `Join Geometry` node. (UV for \"Modified Edges\" no longer appears)", "Drag-to-toggle visible/selectable/renderable in the Group view.\nWindows 64\n\nBroken: 2.70a\n\nThe drag-to-toggle visible/selectable/renderable in the Outliner does not work in the Groups view.\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", "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", "Serious problems with visibility when linking a character\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.3\n\n\nwhen linking a collection containing a character model, rig, etc., oddities occur with the visibility of the armature: when the overlays are turned off/ on, the armature is not displayed until some event occurs (this bug applies to the file where the model is located). undo ignores hiding bones (scene with linked and override character) for clarity, two animation files will be attached. in both, sometimes both of these bugs occur, while it is absolutely unpredictable\n[2022-09-16 02-20-35.mp4](2022-09-16_02-20-35.mp4)\n\n[broken_7.zip](broken_7.zip)\n\nfile with character in broken_7/stalker/\nfiles with animation in broken_7/3d_projects/tests/animation/\n" ]

[ "Linked data-block has \"pointer\" property still active\nBroken: version: 3.4.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: Probably never\n\n\n\n[torus.zip](torus.zip)\n\nOpen torus.blend. It has a linked collection containing the selected object `Torus`.\n\nAs you can see in the image, the \"Object\" rna properties (parent, and the array modifier one) are both active:\n\n{[F13627034](image.png), size=full}\n\nIn fact you can even click on the property to change it (the popup show up, but clicking on it at least doesn't change it):\n\n{[F13627039](image.png), size=full}" ]

[ "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)", "Can't pan more on the viewport when set to camera view with a wide resolution.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.81 (sub 16)\n\nI can't pan to the side more than this with the camera on the viewport. I wanted to have the cube in the center of the viewport but blender just doesn't pan anymore.\n\nHOWEVER! if I change the ratio of the 3D editor, it works (up to a limit), it is a workaround, but a weird one!\nLike this:\n\n\nOpen the file and try to pan to have the cube on the center of the viewport without exiting camera view:\n[Camera_pan.blend](Camera_pan.blend)\nThis happens with this kind of resolution settings and the camera > sensor fit > set to Vertical (that I need in my project).\n", "Regression: Unable to move camera/area light with gizmo (intel GPU)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 30.0.101.1122\n\nBroken: version: 3.2.0, 3.3\nWorked: 3.1\nCaused by 5045968f24\n\ni cant move my camera using move tool or tranform tool on left side bar\n\n- select camera\n- Choose move or transform tool\n- Move camera with gizmo (won't be able to move)\n\n[bug camera.blend](bug_camera.blend)\n[blender 3.2.mkv](blender_3.2.mkv)", "Cycles motion blur does not interpolate correctly\nOperating system: Fedora Linux (Wayland)\nGraphics card: AMD GPU (but Cycles renders on AMD CPU)\n\nBroken: 3.5.0\nWorked: never? (same results till 2.83)\n\nCycles motion blur interpolation is strange.\nIt's very noticeable when an object or the camera is bound to a constraint and the motion blur shutter is set very high (like 60 frames). Cycles motion blur will interpolate it wrong. I will include pictures and .blend files\n\n- Open attached .blend file\n- Render the first frame with EEVEE and Cycles and compare the motion blur.\n\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", "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.", "Cycles volume rendering issues when domain overlaps a plane\nOperating system: Windows 10\nGraphics card: gtx 760 and 1070\n\nBroken: 2.79b(master, release) and 2.80\n\n\n\nShadows on intersecting geometry from Objects with volume shader yield unusable result when using object ray visibility settings.\nWith 2.80 using collections to set objects not visible in camera also fails to achieve this with volumes.\n\nDesired result with volume objects would yield in a same result as done with node group(picture 2)\n\nDoing camera visibility in the shader with nodes works .correctly \n\n\n\n\n[smoke_incorrect shadow.blend1](smoke_incorrect_shadow.blend1)\nAttached blend file(2.80)\n- run smoke simulation for a couple of frames and switch to rendered view\n- toggle object camera ray visibility", "Cascaded shadows produced with EEVEE with orthographic camera loose resolution.\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 457.30\n\nBroken: version: 2.92.0 Alpha\nWorked: no idea?\n\nAs you can see in the image below, to the left side we have an orthographic camera, to the right we have a normal perspective view and the shadows are broken through the orthographic one, \n\n\nCreate a new scene\nPut a plane to cast shadows from the light source\nselect the camera and switch it to orthographic.\nturn the light to sun light\ntada!\n\nIt doesn't seem to happen with the lights in either point, spot or area.\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", "Eevee: Procedural material very slow\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.85\n\nBroken: version: 2.83.3 / 2.90.0 Beta\nWorked: -\n\nFor some reason in eevee my procedural asphalt material works pretty slow.\nI don't see any problems with Cycle and the same scene works as fine on a Radeon RX 480, so it seens to be a bug.\n\n- Open attached file\n- go to material view \n- move around the plane (it's getting worse if you get closer)\n\n[Eevee_RTX_material_bug.blend](Eevee_RTX_material_bug.blend)\n", "Cycles smoke is not exported to render without baking\nOperating system: win 10\nGraphics card: geforce 1080 ti\n\nBroken: blender-2.80-4488056f3d9-win64\\\nWorked: (optional)\n\nSmoke is visible in viewport but not in render.\n\n\n- Select default cube.\n- Run quicksmoke\n- Select the domain and in the simulation cache settings choose `Replay`(step added to be reproducible in mantaflow)\n- Run play so you get some smoke.\n- Press f12 (or switch to cycles and press f12).\n- Renders cube but no smoke.\n\nManually setting it up gives the same result.", "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", "Smoke artefacts when baking smoke simulation based on particles\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.2\nWorked: none\n\nI have a baked particle simulation that is propelled by a wind force field. Next, I have a smoke simulation whose flow source is set to particle system.\nWhen I run the simulation it takes much longer than usual and ends up creating lines of smoke in random directions.\n\nI add that all the sliders in the field weights tab of the domain object are at 0 (gravity, all...) so no force field can be the cause of this scattering\n\nHere are some pictures of the problem :\n\n\n\nWith higher resolution :\n\n\n- Open the blend file\n- Bake Particles\n- Bake Smoke\n\n[SceneProblem2.blend](SceneProblem2.blend)\n\n", "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)", "EEVEE: Shader error for incorrect type connected to a AOV Output\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\n\n\n\n\n```Cpp\nShader Nodetree Error: Invalid implicit socket conversion\nERROR (gpu.shader): GPU_material_compile FragShader:\n |\n 8604 | node_output_aov(vec4_from_Closure(tmp34), node_tree.u36, cons37, tmp38);\n |\n | Error: C1503: undefined variable \"vec4_from_Closure\"\n |\n 8622 | node_output_aov(vec4_from_Closure(tmp72), node_tree.u74, cons75, tmp76);\n |\n | Error: C1503: undefined variable \"vec4_from_Closure\"\n```\n\n1. Material node tree:\n a. Add `AOV Output`.\n b. Connect `Principled BSDF` to a `AOV Output`.\nSee terminal.\n\n" ]

[ "Volumetrics doesn't work on the Orthographic Camera\nHey Guys! I found this bug recently.\n\nMicrosoft Windows 10 Home\nNVIDIA Geforce GTX 1060 3GB\n\nBlender 2.8 Alpha 2 ae87adc73a2\n\nWhen I try to render volumetrics doesn't work on the Orthographic Camera, but in the viewport and perspective camera works perfectly.\n\n- Set principal volume shader in the cube\n- Enables Screen Space Reflections and Volumetrics\n- Add a Ortographic Camera and spotlight.\n- Render" ]

[ "Set Active UV - new node\n\n\n---\n\nSee also: #98851 (Active UV - new node)", "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)", "Group Index input for the fill curve node\nAdd a \"Group Index\" integer input to the node, evaluated on the curve domain.\nThis will allow limiting intersections between separate curves, which can be helpful\nas a performance optimization and for a simpler result.\n\nThe default value should be a single value of zero, and the number button should be hidden on the node.\nTo fill each curve separately, the \"Index\" node can be connected the group index.\n\n**Implementation**\n- The filling function `do_cdt` can have a new `IndexMask` argument\n- This is similar to the sample curve node which uses a `MultiValueMap` to find groups of related indices\n- When the group index is a single value, creating the full `IndexMask` and map can be skipped\n- The total size of the mesh should be calculated based on all of the intersection results, then the results can be converted directly into subsets of the output mesh", "Pinning data (mesh, curve, grease pencil, lattice, particle system) makes certain tabs/options disappear (vertex groups, shapekeys facemaps)\nOperating system: Microsoft 10\nGraphics card:GeForce GTX 10606GB\n\nBroken: 2.93\nWorked: don't know\n\n**in the properties editor, in object data properties, the pin toggle hides vertex groups and shapekeys**\n\n- select default cube\n- go to properties editor\n- press object data properties tab\n- press the pin button\n", "Group nodes starting with \".\" is no longer hidden from search\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 3.4.0\nWorked: 3.3.0\n\nGroup nodes starting with \".\" is no longer hidden from search.\nNot sure if this is a change made or an actual regression bug.\nSometimes we don't want some group nodes to be shown, such as some group nodes inside a group nodes.\n\n\n[Search.blend](Search.blend)", "Node Panels Polishing\n- [ ] Support A to expand/collapse panels.\n- [ ] Support Ctrl+click to isolate panel.\n- [ ] Support dragging all panels to collapse/expand them.\n- [ ] Use the horizontal padding vertically:\n\nBefore:\n\n\n\nAfter:\n\n\n\n---\n\n- [ ] Don't space out socketes when hiding the node\n\n\n- [ ] Bug, hide panel when all its sockets are hidden with Ctrl+H\n\n", "Joining meshes or realizing instances in geometry nodes removes custom normals data\nOperating system: macOS Big Sur 11.5.2\nGraphics card: Apple M1\n\nBroken: 2.93 and 3.0 Alpha\n\n\nUsing the collection info node in geometry nodes destroys custom normals data when the geometry node modifier is applied (or when the project is exported).\n\n\nApply the geometry node modifier on the \"Dummy\" object in the attached blender project. I've also included a video that shows the issue.[collection_info_test.blend](collection_info_test.blend)\n\n[collection_info_bug.mov](collection_info_bug.mov)", "Fields UI: Differentiate between dynamic attribute fields and anonymous attributes\nThere should be way to clearly tell the relation of a field to geometry in the nodetree.\n\n**Definitions**\n\n**Dynamic Attributes**\nThere input fields of attributes/derived data that can be evaluated on any geometry and change dynamically to changes that are made on that geometry. (E.g. Position, Normal, Index, etc.)\nThis type of field gets especially confusing when it is generated with an operation that includes a secondary geometry, which it relies on implicitly. (E.g. Raycast, Attribute Transfer)\n\n**Anonymous Attributes**\nOn the other hand there are attribute fields that depend on/are associated with a certain geometry and don't *change* throughout the node-tree, but are only propagated/interpolated. (E.g. Captured Attributes, Group Inputs)\nTheir evaluation only makes sense in the context of that associated geometry that they exist on.\n\n**The Issue**\nTheir difference in behaviour as to when in the node-tree the values are reevaluated can be crucial to understand what a node-tree is doing and can very easily cause problems and confusion.\nThis is why it should be easy to read in the UI what geometry a fields is associated with when making any fields connection, or when investigating the node-tree.\n\nThere are 3 different categories of fields that can result from this:\n- Fully dynamic: All referenced attributes are dynamic/derived data. They are not simply propagated through the node-tree but rather calculated whenever the field is evaluated in a geometry operation. This means that they change depending on the context of when they are evaluated.\n- Fully anonymous: All referenced attributes are anonymous. They are clearly associated with a geometry that they were created on and only make sense in the context of that geometry and any geometry that inherits this data.\n- Mixed: Some referenced attributes are dynamic and some are anonymous. The restricting factor for socket connection here is given by what geometry the anonymous fields are associated with. On the other hand the dynamic aspect of changing data is also something to keep track of.\n\n**Initial Proposal**\nThere are multiple possible ways to go about visualizing this. My idea is to create the least additional visual concepts necessary and show the information as it is needed.\n\n**Geometry Association**\nI think the most straight-forward to visualize the dependency of anonymous attributes with their associated geometry is to highlight compatible geometry while drawing a connection from an output socket carrying a field that depends on.\nThat can be done by highlighting all geometry connections starting from the first geometry socket that includes the anonymous attribute that was created last and branching off downstream. (E.g. thickening the noodle and adding glow)\nOn top of that input sockets could also be highlighted/greyed out depending on their compatibility.\n\nSocket selection would also help here, so that this wouldn't only happen as a connection is drawn but also for a selected socket.\n\n**Dynamic Reference**\nBy default, this would also already mark fully dynamic fields by not having any geometry highlighted visual. I do still think though that there should be an additional hint whenever a field carries a dynamic reference. For both fully dynamic and mixed fields. \nI think this could be done by altering the socket of all fields with dynamic references to have an additional outline with an offset.\n\n**Remarks**\n\n- When no input geometry is connected on a node, also don't grey out inputs\n- Node groups pose an issue in that what field is associated with what geometry needs to be marked. This could be derived implicitly/set by the user/following a convention.\n\n--- \nThere are many other ways this could be done, but as I am working with geometry nodes I am noticing more and more the need for this, so I wanted to make an initial push.\nFurther discussion and feedback, especially also from the UI team are welcome and requested.", "Support warnings for field input nodes\nField input nodes evaluate in a context, but currently they give no warning if they do not support\na particular context. The initial goal is to add a warning like \"Input node does not support geometry type: Mesh\" on the spline parameter node in the following situation:\n\n{[F12738459](image.png) size=full}\n\n### Implementation\nA potential implementation isn't clear.\nIt seems there needs to be a way to keep track of which node (`bNode`, `NodeRef`, `DNode`, etc.) the field input node came from.\nThen the field evaluation system should have a way to collect errors and return them to the caller. Or maybe the caller can pass a\n\"logger\" class to the field evaluation system. That generalization could allow more specific breakdowns of node timing in the future.", "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", "Search of nodes from multiple strings\nFor the math nodes it would be good to have a way to search \"dot\" and add the attribute vector math in the \"dot\" mode.", "Custom RenderEngine: Shader Editor issues\nOperating system: Arch Linux\nGraphics card: GTX Titan\n\nBroken: git version, 2.81.8 (f2400c1bb5e2)\n\n\nBehaviour with respect to keeping Cycles/Evee shader nodes around seems to be inconsistent with the documentation, as the shader editor is either not available or shows an incomplete list of shader nodes.\n\n\nOn bpy.types.RenderEngine.html the property `bl_use_shading_nodes_custom` is described as\n\n> Don't expose Cycles and Eevee shading nodes in the node editor user interface, so own nodes can be used instead\n\n\nUsing the attached RenderEngine test class, which is based on the code in the above doc page:\n\n1. Start `blender -P blender_render_engine.test.py`\n2. Switch to `Custom` renderer\n\nI see the following depending on `bl_use_shading_nodes_custom`:\n\n- When `bl_use_shading_nodes_custom` is `False` (i.e. keep Cycles/Eevee nodes\n```\naround) the Shader editor's add node menu (`Shift+A`) under `Shader` only \nhas a `Principled Volume` entry, other Cycles nodes are gone. But when creating a new material in\nthe editor the initial graph is `Principled BSDF -> Material Output`, i.e.\nusing the principled BSDF node that cannot be created from the menu.\n```\n\n- When `bl_use_shading_nodes_custom` is `True` the Shader editor is \n```\nno longer available. Is this new behaviour, where a custom RE\nneeds to provide its own editor page, instead of adding to the existing shader editor?\n\n```\nThere's also a corner case when having the Shader editor visible (for example when Cycles is active) and then switching to a render engine that has `bl_use_shading_nodes_custom=True`: the icon for the editor will become blank, but the Shader editor remains visible. In the console I warnings in this case:\n\n`WARN (bpy.rna): ../source/blender/python/intern/bpy_rna.c:1451 pyrna_enum_to_py: current value '3' matches no enum in 'SpaceNodeEditor', '(null)', 'tree_type'`\n\n [blender_render_engine.test.py](blender_render_engine.test.py)\n", "Geometry Node: New Sample Curve\nAdding support for a random attribute to the sampling node exposed the problem of attribute evaluation ignoring the calculated curve. This design variant is intended to treat the sampling of values from calculated curves as a new attribute-based сontext.\n| [2022-08-01 14-00-56 (video-converter.com).mp4](2022-08-01_14-00-56__video-converter.com_.mp4) |    |\n| -- | -- |\nThe crux of the problem is that a random attribute, when sampled, must be able to have a position behavior. Other behaviors are not covered yet, but may be added later.\nSampling attributes do not belong to the curve and have their own size. Their interpolation may not be linear, but based on the type of curve, which increases the speed for large objects.\n\nExample: sampling a random vector from curve points. You want the vector to keep its length. But even the original implementation of normals kept the length just because of the normalization. Nonlinear interpolation in spline space for a vector has the ability to rotate it without loss of length and incorrect deformations.\n\nOr you want to sample a color. You can set the color for the breakpoints and... Whoa, those are just linear transitions! Handles cannot be used. They are not a domain and this design does not violate that. Simply by sampling an attribute, you can sample it not only from breakpoints, but from handles!\n\nAlso, in addition to entering an attribute as the domain of the sampled curve, a segment data node is offered. This low-level node is for primary access to cache data. The sampled attribute input node uses this as its signature. But it can also be useful for the user to be able to use this data, for example, to visualize the operation of a bezier curve.\n\nWhen sampling, 3 types of values must be present in the scope of the context:\n - Curve data obtained from the visible version of the curve\n - Curve data sampled from its points and handles\n - Sampling destination data. To keep things simple, if multiple post-sampling values are going to be used with geometry definitions, it's best to do this before the sampling node to keep the output of the node to a minimum.\n\nAlso sampling features:\n1. The option of sampling a vector in normal/target space + sample position can be used as a variant of the curve mesh deformation\n2. Sampling at an arbitrary point creates freedom to obtain information about the curvature of the surface.\n\n---\nCurve Input:\n - Spline type (Select current type curves / index of type)\n - Select Spline By Type (By type index)\n\n---\nChanged Nodes:\n - Sample Curve\n - Input:\n - Curve\n - Factor / Length\n - Curve (Index)\n - Attribute (Random type) (use SampleCurveContext)\n - Output:\n - Value (Random type)\n```\n\n```\n - Position:\n - In SampleCurveContext return evaluated_positions\n - Normal:\n - Same Position\n - Curve Tangent:\n - Move TangentFieldInput to Fields Input and add it in SampleCurveContext same position\n - Index:\n - Same position. Index in sampling input index of current curve\n - ID:\n - Same Index. ID is index of current sample. Sampling no has order ad id make sence only for random and same things\n - Spline Length, Parameter, Resolution, Cyclic:\n - Data of spline same changed. Data of point internolated by sampling\n\n- Context Add:\n - Sample Signature Input:\n - Curve Index\n - Curve Type\n - First Point\n - First Factor\n\n---\nAdd Nodes (Valid only in SampleCurveContext):\n - Sample Attribute on Curve:\n - Input:\n - Attribute (Random type)\n - Hadles type ? left/right position : Weight\n - Output:\n - Value (Random type)\n - Sampling Attribute:'\n - Input:\n - Attribute (Random type)\n - Output:\n - Value (Random type)\n - Sample Segment:\n - Output:\n - Previous Point of original curve\n - Factor for interpolatin in current segment\n\nFirst test version: P3114", "Sculpt Mode TODO tasks\nThis task keeps a list of approved tasks related to Sculpt Mode that can be considered as TODOs or missing functionality in the current design.\n\n**Gesture tools**\n\n - Make Hide Box tool use the new sculpt API and gesture operator\n - Face Set Line Gesture\n - Color Fill Gestures\n - Line Trim Gesture\n - Normal Orientation for trimming tools\n - Poly line gestures\n - Mask Gradient Gesture tools\n - Lasso, Line and Poly line hide tools\n\n\n\n**Sculpt Vertex Colors**\n\n - Sculpt vertex colors gradient Tool\n - Combined Color Coords Undo step\n - Pick Sculpt Vertex Color from other object with the sample color operator\n\n\n**Transform tool**\n\n - Transform Tools TODO: #80392\n\n\n\n**Brush tools**\n\n - Expose minimum size and size pressure smoothness for all brushes\n - Implement area normal/center stabilizer \n - Make Grab active vertex grab from original coordinates instead of PBVH deformed coordinates\n - Pinch perpendicular mode for crease\n\n\n\n**Viewport**\n\n - Update matcaps to include a separate specular pass\n - Render Face Sets as contour lines\n\n\n\n**Elastic Deform**\n\n - Pinch elastic deform mode\n - Multi scale twist-scale-pinch for elastic deform\n\n\n\n**Filter tools**\n\n - Support textures in mesh filter\n - Unify filter strength with brush strength \n\n\n\n**Cloth Sculpting**\n\n - Expose solver properties as Sculpt properties (iterations, delta...)\n - Make use collisions options global\n - Implement SDF collisions\n - Implement collisions plasticity\n - Elastic Deform cloth brush\n - Support cloth deformation target with dynamic area in all brushes\n - Support cloth deformation target for the transform tool\n\n\n\n**Boundary brush**\n\n - Split the internal and boundary falloff into two different falloff\n - Let boundary falloff offset be smaller than 1\n\n\n\n**Sculpt Mode options**\n\n - Store radial and tiling symmetry in meshes\n - Enable \"Delay Viewport Updates\" by default\n - Add a separate property to meshes to store if they should use flat/smooth shading in sculpt mode, without modifying their normals\n\n\n\n**Multires**\n\n - Multires Delete Lower\n - Multires refit/rebase\n - Key map changes to support switching up/down subdivisions\n - Hide remeshers and Dyntopo when multires is active\n - Preview the current/total number of subdivisions in the viewport\n - Optimize Unsubdivide dissolve operation when creating the base mesh\n\n\n", "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" ]

[ "User interface improvements for attribute search\nDesign task: #85280\n\nThis depends on #85658.\n\n---\n\n{[F9750374](image.png), size=full}\n\n---\n\nThe idea is to go beyond the basic search list and indeed show:\n* Data Type\n* Category\n* Attribute\n* Domain." ]

[ "GUI: The curser is heavily lagging if GSync is set to windowed and full screen mode\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: Blender 2.79b up to Blender 3.0.0\n\nEverything is as expected if the mode is set to \"Fullscreen only\" (the default)\nBut as soon as you set to it to \"Window- and Fullscreen mode\" the mouse curser will lag heavily.\n\n\n1. Enable GSync\n2. Set it to \"Enable for windowed and full screen mode\"\n3. Save\n4. Open Blender and move the curser\n\n**Workaround** \nJust set it back to full screen mode only.\nOR\nIf you go to nVidia Control Panel > Manage 3d Settings > Program Settings.\n\nAdd Blender under Select Program To Customize. Changing to the following settings can fix it:\n\nMonitor Technology: Fixed Refresh\nPreferred Refresh Rate: Application-controlled\n\n**Desired behavior** \nA fluid curser on the screen even with \"windowed and full screen mode\" enabled", "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", "Buggy floor grid when using a micrometer unit scale\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.83.5\n\nWhen working with micrometer unit, setting up unit scale up to 0.0001 works ok. But, from 0.00001 micrometer value and grid scale changes to weird condition.\n\n\n- In Scene Settings set unitscale to 0.00001 or less (metric r imperial)\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", "unable to use the workspace tabs or menus if rendering onto a second monitor\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.90 (sub 0)\n\nunable to use the workspace tabs or menus if rendering onto a second monitor\n\nSee video below. I reported it previously but it got merged with T71334 which was recently closed. @brecht fixed it the other day, but this bug still remains so just raising a new bug with better info. \n\n[2020-05-02 22-21-54.mp4](2020-05-02_22-21-54.mp4)\n\n\nSet resolutions:\n- Primary monitor 4K, 150% scaling\n- Secondary monitor 1920 x 1080 100% scaling\n\n- Have Blender main window on primary monitor and render on secondary monitor.\n- Render image\nTry to switch workspace - it doesn't work\n\n", "Bone Override Transform affects bone local axis display.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.0\n\nWhen a bone gets assigned a display transform override, it's viewport display axis gets transformed, which probably shouldn't happen as its purpose is to display the Bone's not it's Shape's local axes.\n\n[override-transform.blend](override-transform.blend)\n - Remove Override Transform from Bone's Viewport Display's Custom Shape -> Displayed Bone's axes change location.", "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.", "Render animation cycles-x bug March 11, 2022\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nRender count from 1 to 1200 frames\n\n\nBlender 3.2.0 Alpha within Cycles-x\nPush the 'Command + F12\" and render animation cause bug between start to end (855 - 1200 frames)\n\nBlender and video file: [Blender 3-2-0 by Kent Davis March 11 2022.zip](Blender_3-2-0_by_Kent_Davis_March_11_2022.zip)\n\n\n\n\n\n\n\nRadeon Pro 575:\n\n```\nChipset Model:\tRadeon Pro 575\nType:\tGPU\nBus:\tPCIe\nPCIe Lane Width:\tx16\nVRAM (Total):\t4 GB\nVendor:\tAMD (0x1002)\nDevice ID:\t0x67df\nRevision ID:\t0x00c4\nROM Revision:\t113-D000AA-931\nVBIOS Version:\t113-D0001A1P-025\nEFI Driver Version:\t01.00.931\nMetal Family:\tSupported, Metal GPUFamily macOS 2\nDisplays:\n```\niMac:\n```\nDisplay Type:\tBuilt-In Retina LCD\nResolution:\tRetina 5K (5120 x 2880)\nFramebuffer Depth:\t30-Bit Color (ARGB2101010)\nMain Display:\tYes\nMirror:\tOff\nOnline:\tYes\nAutomatically Adjust Brightness:\tNo\nConnection Type:\tInternal\n```\n\n", "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", "UI: File Browser Incorrect uiFontStyles\nOperating system: All\nGraphics card: All\n\nBroken: 3.1\nWorked: 2.79\n\nFile Browser uses an odd mixture of uiFontStyles to draw interface\n\nEdit / Preferences / Themes / Text Style\nChanging \"Widget\" points changes the font size of \"Bookmarks\", \"Recent\", the browsed directory, and the line height of the entries:\n\n{[F11861179](FBWidget.gif),width=100%}\n\nChanging \"Widget Label\" changes Volumes, System, and the text size (but not line height) of entries:\n\n{[F11861234](FBLabel.gif),width=100%}\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", "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}", "Line Art Thickness doesn't consider Render Resolution Percentage\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.1122\n\nBroken: version: 3.2.2\nBroken: version: 3.4.0 Alpha\nBroken\n\nWhen using Line Art Modifier, on a Grease Pencil Object in Screen Space Mode, Line Thickness doesn't scale with resolution as expected. \n\n1. Open new General Startup File\n2. Create New Object>Grease Pencil>Scene Line Art\n3. Under Object Data Properties>Strokes>Stroke Thickness and set to World Space\n4. Set Render Resolution % to a factor. line thickness will be different than expected\n\n\n\n\n\n", "object monitor and menu bar flickers when i move move my cursor\nOperating system: Windows-11-22H2\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.92\n\nBroken: version: 3.6.2\n\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" ]

[ " temporary visual UI glitch when Having two monitors with different windows scaling\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14758 Core Profile Context 21.1.1 27.20.14527.2002\n\nBroken: version: 2.92.0 Beta\n\nif you have two monitors and one has 100% scaling while the other have 125% for example, when changing the workspace some ui parts will have the wrong size until you hover your mouse on the panel\n\n\n- Have the monitors with different scaling, in my setup the main one is 125% and the secondary is 100%\n- Have two blender windows, one in each monitor\n- Change the workspace from any to animation(for example)\n- Check the timeline UI and hover your mouse on it right after\n\n[video_2021-02-16_12-39-12.mp4](video_2021-02-16_12-39-12.mp4)", "Glitching UI\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\n\nUI scaling gets distorted and important menu toolbars are lost \n\n4k display as main (125% Scaling) 2 side Monitors @ 1080p (225% scaling) - \nWhen creating a floating window (holding shift clicking) and dragging onto a 1080p side monitor, the entire blender program redraws the UI every workplace switch Modelling > Sculpting > Sculpting to Modelling etc\nrendering the whole process useless!\n" ]

[ "Crash when moving to Shading workspace\nOperating system: Darwin-16.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.17.5 355.10.05.45f01\n\n|Broken:|version: 2.83.0, commit date: 2020-06-03,|hash: `211b6c29f7`\n| -- | -- | -- |\n||version: 2.90, commit date: June 08,|hash: `9f7d84b656`\n|Worked:|version: 2.82|-\n\nWhen I open Blender, without changing anything in the default scene, if I move to the 'Shading' workspace my system freezes for a few seconds and crashes (it closes).\n\n- Default startup scene\n- click on 'Shading' workspace from the top bar\n", "Crash clicking on Material Preview\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nSometime, clicking on Material Preview button (Eevee) Blender 2.92 crashes without a reason.\nSee file and log attached\nThank you\n[Rocks_Pack.crash.txt](Rocks_Pack.crash.txt)\n\n-\n\n[Rocks_Pack.blend](Rocks_Pack.blend)", "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", "Crash/Bugs with material's Surface dropdown + undo\nOperating system: Linux-4.15.0-45-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 4)\nAlso confirmed to crash in 2.80.\nWorked: 2.79b does not crash (works as expected)\n\nWhen changing the surface/volume in material properties (the list view of the shader nodetree) and undo, opening the dropdown directly afterwards again can crash Blender.\n\n- Download repro blend file (it's just a Cube with a Principled BSDF) [shaderlistRepro.blend](shaderlistRepro.blend)\n- In Properties Editor, click on Surface (Principled BSDF) and select any option in the dropdown\n- Move your mouse over the Surface dropdown and keep it there!\n- Press CTRL+Z to undo\n- Click on the Surface (Principled BSDF) dropdown again (your mouse may not leave the dropdown box)\n- Blender crashes\n\nThe same happens when done with the Volume dropdown instead.\n\n[2020-02-24 15-09-16.mp4](2020-02-24_15-09-16.mp4)\n\n**Possibly related issue**\nIn another file, doing the exact same steps as above has some other effects:\n- Either it spawns this popup (clicking any of these options crashes Blender) \n- Or it spawns a blank popup \nThis is the reproduction file which caused this: [shaderlistRepro2.blend](shaderlistRepro2.blend)\n\nWhich effect happens is really inconsistent and I am not sure how to reproduce one or the other.", "Use after free: Baking Rigid Body physics causes instant crash\nOperating system: macOS 10.15.7\nGraphics card: AMD Radeon Pro 5500M 4 GB / Intel UHD Graphics 630 1536 MB\n\nBroken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, 2.93.0 Beta, branch: master, commit date: 2021-04-28 22:25, \nbroken: f7b22fc3d27113715e8726c69ab3264e1d487439\nWorked: \n\nBaking the Rigid Body world physics causes Blender to crash either instantly, or after baking less than 100 frames (it varies). Interestingly, a friend with the PC version of 2.92 says the project works fine, no crashes whatsoever.\n\nOpen the project. Make sure Allow Negative Frames is on under Preferences/Animation. Go to the Rigid Body World and hit bake.\n\n[physics test b.blend](physics_test_b.blend)\nAsan report: [T88113_asan_report.txt](T88113_asan_report.txt)", "Blender crashes with Noise Texture Node + Hair Particle System + Eevee\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 480 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: 8dc95f61f3\nBroken: version: 2.92.0\nBroken: version: 2.91.2\nWorked: version: 2.83.12\n\nBlender 2.92 with AMD crashes with **Noise Texture Node**and **Hair Particle System** with render engine Eevee.\nWith Blender 2.91.2 with AMD it doesn't crash but colors are incorrect.\n\nWith 8dc95f61f3 with Intel GPU, there's no crash but colors are incorrect in the same way as in AMD - 2.91.2.\n\n1. Open attached .blend file\n2. Viewport shading to: Render \n3. Play animation by tapping space bar\n\n[particle_loop.blend](particle_loop.blend)\n[blender_2_92_crash.txt](blender_2_92_crash.txt)\n\n**Blender 2.92**\n[blender_2_92.mp4](blender_2_92.mp4)\n\n**Blender 2.91**\n[blender_2_91_2.mp4](blender_2_91_2.mp4)\n\n**Blender 2.83.12**\n[blender_2_83_12.mp4](blender_2_83_12.mp4)", "Rendering instability from Blender 3.5 to 36+\nOperating system: macOS 13.4.1\nGraphics card: Apple/AMD W6800X Duo\n\nBroken: 3.6 to 4.0\nWorked: 3.5.1\n\nI get substantial instability when rendering animation sequences in Blender 3.6 and above, compared to 3.5. For example, I've built a large scene with lots of assets and displaced ground material. Today I left Blender 3.5 rendering and have outputted all 250 frames without a single issue using the GPU.\n\nBut previously in 3.6 I get a variety of frames – sometimes 30 or 40, sometime just a single frame – before I have to reboot Blender and start the rendering process again. I've tried all sorts of tricks, like using tiling to render and even switching to CPU-only, but in all cases, the animation process will eventually crash Blender. I thought it might be a VRAM issue, but my dual card has 32GB! My Mac Pro is a standard system with 64GB RAM and no strange or non-Apple additions – it should be rock solid.\n\nI don't have one specific scene to give you, but I've experienced all manner of instability since 3.6 came out – there is obviously a core difference in the app from 3.5 to 3.6+. However, I am really keen to help find the culprit. If you let me know what you need, I can provide crash reports or debug information, just point me in the right direction. Thanks!\n\n", "Momentary interface freezes while EEVEE rendering causes progress bar malfunction\nOperating system: Windows 10, 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.80, 2.81\n\n**Rendering in EEVEE has been causing momentary complete interface freezes for each frame**, which caused the progress bar on the frame render to malfunction and jump very quickly from one value to another, thus giving momentarily true but useless information (note that the progress bar never moved to an incorrect position, it just froze). One thing that assures me this is a bug is **minimizing all Blender windows causes the progress bar visible on the minimized icon to work properly** (but unfortunately one cannot see what frame it's on).\n\nOpen the default blend file.\nRender the animation. The interface on 2.81 has frozen for each frame.", "Blender segfault if Bake Line Art\nOperating system: Debian Linux Stable 11\nGraphics card: Intel internal UHD Graphics 630 (driver: i915)\n\nBroken: 3.2.2 - 3.6.1 official releases\n\nBlender segfault if Bake Line Art.\n\nConsole:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault\n```\n\nFile /tmp/blender.crash.txt:\n```\n# Blender 3.2.2, Commit date: 2022-08-02 18:15, Hash bcfdb14560e7\nbpy.ops.object.delete(use_global=False, confirm=False) # Operator\nDeleted 1 object(s) # Info\nbpy.ops.object.gpencil_add(align='WORLD', location=(0, 0, 0), scale=(1, 1, 1), type='MONKEY') # Operator\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.gpencil_modifier_add(type='GP_LINEART') # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xc1619d0]\n./blender() [0x11da18d]\n/lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f97f7664d60]\n./blender(MEM_lockfree_allocN_len+0x7) [0xc16e1e7]\n./blender(MEM_lockfree_dupallocN+0x14) [0xc16e624]\n./blender(BKE_gpencil_stroke_duplicate+0x1a) [0x11f926a]\n./blender(BKE_gpencil_frame_copy_strokes+0x42) [0x11f94c2]\n./blender() [0x1207d97]\n./blender(BKE_gpencil_prepare_eval_data+0x1b7) [0x1208b07]\n./blender(BKE_object_handle_data_update+0x2fe) [0x12af9ae]\n./blender(BKE_object_eval_uber_data+0x2f) [0x12afc7f]\n./blender() [0x1913f22]\n./blender() [0x19140f2]\n./blender() [0xc16574d]\n./blender() [0x1796a35]\n./blender() [0x1796ceb]\n./blender() [0x1783d27]\n./blender() [0x1790720]\n./blender() [0x179275c]\n./blender() [0x1792959]\n/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f97f807aea7]\n/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f97f7727a2f]\n\n# Python backtrace\n```\n\n1. Open Blender\n2. Click to default box and delete it (press del)\n3. Press Shift+A\n4. Select \"Grease Pencil\" - \"Monkey\"\n5. At right area select \"Modifier Properties\"\n6. Click \"Add Modifier\"\n7. Select \"Line Art\"\n8. At bottom of this area click \"Bake\" - \"Bake Line Art\"\n9. Segfault here\n\n", "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", "Blender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\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 535.98\n\nBroken: version: 3.6.0\nWorked: I dunno\n\nBlender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\n\n<video src=\"attachment\" title=\"Crash when particle edit.mp4\" controls></video>\n\n1, Open the attached Blender file\n2, Rekey it to have a higher keypoints\n3, Increase the Strand Steps in the Viewport Display on the Particle tab\n\n", "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 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)", "Blender keeps crashing relocating linked library [3.5.1]\nOperating system: Windows-10-10.0.25357-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\nRelocating linked library file results in instant crash when different file is chosen. I need this because i work on both OSX and Windows. While testing file version, i had issue with indirectly linked files. These are nested files so to say. They are linked blend files inside another linked blend file. \n\n- Download and Unzip attached `RML-test file-bl350.zip` file\n- open file \"RML-test file-bl350.blend\"\n- go to `Outliner` > `Blender File` and select the linked lib file with exclamation mark \"linked object\"\n- Right click and select \"Relocate\"\n- Point to the file \"linked object-bl293\"\n\nBlender file browser closes and crashes short after.\n\nSide note\nThe linked lib blend file is name \"linked object\", if i rename the \"linked object-bl293\" to \"linked object\" it works. But because i work on both OSX and Windows and sometimes also with different version. I need to rename linked files so i dont break anything.\n\nHowever, i jsut tested these 2 files in an issue folder i created and then it links just fine. When these files are linked in the original folder, blender crashes right after i pick that file \"linked object-bl293.blend\". See attached screengrab.\n\n\n", "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" ]

[ "Blender crashes on refocus\nOperating system: Windows 10 x64\nGraphics card: Nvidia GTX 1060\nProcessor: Intel Core i5 3570\n\nBroken: 2.79-git.4e3562f45ad, 2.79-git.968bf0df148, 2.76 to 2.80 from blender download page. All same behavior.\nWorked: none\n\nBlender crashes when switching back into focus with ERROR_ACCESS_VIOLATION\n\nI open blender. I switch to another window and back into blender via alt-tab, by clicking, or just double-tapping the win-key, and blender crashes instantly.\n\n - No Error log generated. Running in CMD just gives me this: EXCEPTION_ACCESS_VIOLATION\n - I tried running blender from console with --factory-startup, no change\n - I tried both .zip and .msi versions, none worked\n - I tried running versions from 2.76 up to 2.80, always same behavior\n - I tried opencl.dll from other solutions, did not work\n - I updated to newest drivers (from 385.xx to 417.35), nothing changed\n - I tried turning off my anti-vir (windows defender), did not work\n - I am slowly going mad\n\nIs there any way I can get a better error msg?\nAny help or stabs to this would be highly appreciated. Screenshot of cuda-z and cpu-z.\n\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", "Blender Crashing When Painting Stroke into a \"Moving Animated Character\" (heap-use-after-free)\nBroken: 4.0 alpha\nBroken: version: 2.79 - 2.82 (sub 7)\nWorked: Never\n\nI have this experiment of making LIVE talking head, via OSC. And I noticed that if I tried painting a stroke on a talking moving animated head, it will crash. Even with timeline not running.\n\nI got a video (Might need iPhone X with MOM addon to test this....) :\njhHdG6ZXFDU\n\n- Open attached file\n- Run animation\n- Paint over the animated object\n[paint_animated_shapekey_bug.blend](paint_animated_shapekey_bug.blend)\n\n\n", "Mesh related crash in add-on\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 780 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.0.0 Alpha\n\nUsing an the operation connect spread in an addon is causing an EXCEPTION_ACCESS_VIOLATION. \n\n[blender.crash.txt](blender.crash.txt)\n\n```\nStack trace:\nblender.exe :0x00007FF7A109EC60 blender::deg::deg_graph_flush_updates\nblender.exe :0x00007FF7A1084AA0 DEG_evaluate_on_refresh\nblender.exe :0x00007FF79C983790 scene_graph_update_tagged\nblender.exe :0x00007FF79CB61510 wm_event_do_notifiers\nblender.exe :0x00007FF79CB4B550 WM_main\nblender.exe :0x00007FF79C7E2ED0 main\nblender.exe :0x00007FF7A16421A8 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFEEB937020 BaseThreadInitThunk\nntdll.dll :0x00007FFEECA62630 RtlUserThreadStart\n```\n\nDownload [Forgotten Tools ](forgotten_tools_0_5_0.zip) use Connect spread on 2+ edges go to operation popup menu increase the cuts.\n\n[2021-06-20_00-26-23.mp4](2021-06-20_00-26-23.mp4)\n\n", "Modal operator causes a crash when using the REDO operation\nOperating system: Win10\nGraphics card: nVidia 1070\n\nBroken: 2.80 (sub 45), branch: master, commit date: 2019-02-19 23:18, hash: 855b3e68ef27, type: Release\nWorked: n/a\n\nA custom modal operator seems to cause an AccessViolation when you shift+r (REDO) the operator\n\n[modal_redo_bug.blend](modal_redo_bug.blend)\n - Open the provided blend and execute the script that is sitting in the script editor\n - Select the \"Cube\" object\n - Invoke the custom \"DC Modal Redo Bug\" operator from the Space/F3 search menu\n - Left click to confirm. Things are fine\n - Select \"Cube\" again\n - Shift-R to REDO\n - Left click to confirm\n - Crash\n\n```\nException thrown: read access violation.\nop->type was 0xFFFFFFFFFFFFFF3F.\n\n\nblender.exe!wm_operator_register(bContext * C, wmOperator * op) Line 164\tC\nblender.exe!wm_operator_finished(bContext * C, wmOperator * op, const bool repeat, const bool store) Line 923\tC\nblender.exe!wm_handler_operator_call(bContext * C, ListBase * handlers, wmEventHandler * handler_base, wmEvent * event, PointerRNA * properties) Line 2028\tC\nblender.exe!wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2616\tC\nblender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 2660\tC\nblender.exe!wm_event_do_handlers(bContext * C) Line 3011\tC\nblender.exe!WM_main(bContext * C) Line 421\tC\nblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 507\tC\n```", "Regression: Attempt to move object with Copy Location (with Offset) crashes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nA consistent crash when trying to move an object with COPY LOC w/ Offset enabled.\n\n\n1. Open the attached blend file\n\n2. Move the pre-selected object in any direction, you may have to do this two or three times\n\n3. program will crash with EXCEPTION_ACCESS_VIOLATION\n\nThis is happening every time.\n\n```\nStack trace:\nblender.exe :0x00007FF73E03C510 blender::bounds::min_max<blender::VecBase<float,3> >\nblender.exe :0x00007FF73E03BD30 blender::FunctionRef<void __cdecl(blender::Bounds<blender::VecBase<float,3> > &)>::callback_fn<<lam\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF7425212F0 blender::CacheMutex::ensure\nblender.exe :0x00007FF73E042390 BKE_mesh_minmax\nblender.exe :0x00007FF73E0409F0 BKE_mesh_boundbox_get\nblender.exe :0x00007FF73E02E940 BKE_object_boundbox_get\nblender.exe :0x00007FF73E02F410 BKE_object_dimensions_get\nblender.exe :0x00007FF73E613520 RNA_property_float_get_index\nblender.exe :0x00007FF73E235050 dtar_get_prop_val\nblender.exe :0x00007FF73E235410 evaluate_driver\nblender.exe :0x00007FF73E168590 calculate_fcurve\nblender.exe :0x00007FF73E156270 BKE_animsys_eval_driver\nblender.exe :0x00007FF73E4464F0 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF73E446320 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7425175C0 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FF9998CA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FF9A5D192C0 recalloc\nKERNEL32.DLL :0x00007FF9A6F72690 BaseThreadInitThunk\nntdll.dll :0x00007FF9A882AA40 RtlUserThreadStart\n```\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 playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "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 on deleting 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```\n)\nWorked: (?)\n\nI duplicated a Text strip via <shift><D>. I don't know where that driver on Location X came from. The original didn't have one. I then wanted to delete that driver. After deleting it and moving the current frame blender crashed.\n\n- Load attached file\n- Delete driver of 'Location X'\n- Press Cursor keys Left/Right a few times till crash.\n[crash.blend](crash.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)", "Blender 2.93 crashes randomly\nHardware: MacBook Pro 13\", 8 GB 2016, as well MacMini 8GB 2020\nOperating system: MacOS\nGraphics card:\n\nBroken: version: 2.93.1\nWorked: ?\n\nI work with files exported from CAD-software packages imported into Blender showing technical installations: vacuum chambers and related technical infrastructure. I process the objects in the files by sorting them into collections representing subsystems (vacuum chambers, electrodes, magnets, ...) joining parts of larger systems, assigning materials from a material library file. I use hierarchies of files containing standard parts occurring at various places, materials and larger structures. In total, the files have a size of about 1 GB of data.\n\nWhen working with the files, Blender repeatedly and randomly crashes without obvious relation to specific actions.\n\nCannot provide this kind of information: random crashes.\n\nI am willing to give access to a git repo containing the 1 GB files\n\nSystem_info.txt:\n\n```lines\n> =====================================\n> = Blender 2.93.1 System Information =\n> =====================================\n> \n> \n> Blender:\n> =====================================\n> \n> version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: 1b8d33b18c2f, type: release\n> build date: 2021-06-22, 23:47:10\n> platform: Darwin\n> binary path: '/Applications/Blender.app/Contents/MacOS/Blender'\n> build cflags: -Wall -Werror=implicit-function-declaration -Werror=return-type -Wno-tautological-compare -Wno-unknown-pragmas -Wno-char-subscripts -Wstrict-prototypes -Wmissing-prototypes -Wunused-parameter -mmacosx-version-min=10.13 -Xclang -fopenmp -I'/Users/blender/git/blender-v293/blender.git/../lib/darwin/openmp/include' -std=gnu11 -msse -pipe -funsigned-char -fno-strict-aliasing -msse2 \n> build cxxflags: -Wall -Wno-tautological-compare -Wno-unknown-pragmas -Wno-char-subscripts -Wno-overloaded-virtual -Wno-sign-compare -Wno-invalid-offsetof -mmacosx-version-min=10.13 -ftemplate-depth=1024 -stdlib=libc++ -Xclang -fopenmp -I'/Users/blender/git/blender-v293/blender.git/../lib/darwin/openmp/include' -std=c++17 -msse -pipe -funsigned-char -fno-strict-aliasing -msse2 \n> build linkflags: -fexceptions -framework CoreServices -framework Foundation -framework IOKit -framework AppKit -framework Cocoa -framework Carbon -framework AudioUnit -framework AudioToolbox -framework CoreAudio -framework Metal -framework QuartzCore -framework ForceFeedback -liconv -Wl,-stack_size,0x100000 -Wl,-unexported_symbols_list,'/Users/blender/git/blender-v293/blender.git/source/creator/osx_locals.map' -stdlib=libc++\n> build system: CMake\n> \n> Python:\n> =====================================\n> \n> version: 3.9.2 (default, Mar 16 2021, 14:53:03) [Clang 10.0.0 (clang-1000.11.45.5)]\n> file system encoding: utf-8:surrogateescape\n> paths:\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/startup'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/modules'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/python/lib/python39.zip'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/freestyle/modules'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/addons/modules'\n> \t'/Users/wgeithner/Library/Application Support/Blender/2.93/scripts/addons/modules'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/addons'\n> \t'/Users/wgeithner/Library/Application Support/Blender/2.93/scripts/addons'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/addons_contrib'\n> \t'/Users/wgeithner/.local/lib/python3.9/site-packages'\n> \n> Python (External Binary):\n> =====================================\n> \n> binary path: '/Applications/Blender.app/Contents/Resources/2.93/python/bin/python3.9'\n> version: Python 3.9.2\n> \n> Directories:\n> =====================================\n> \n> scripts:\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/modules'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts'\n> \t'/Users/wgeithner/Library/Application Support/Blender/2.93/scripts'\n> user scripts: '/Users/wgeithner/Library/Application Support/Blender/2.93/scripts'\n> pref scripts: None\n> datafiles: '/Users/wgeithner/Library/Application Support/Blender/2.93/datafiles'\n> config: '/Users/wgeithner/Library/Application Support/Blender/2.93/config'\n> scripts : '/Users/wgeithner/Library/Application Support/Blender/2.93/scripts'\n> autosave: '/Users/wgeithner/Library/Application Support/Blender/2.93/autosave'\n> tempdir: '/var/folders/qc/ph84tvmx4h19sn6wl8nnn8hw0000gn/T/blender_iWUimt/'\n> \n> FFmpeg:\n> =====================================\n> \n> avcodec: '58, 54, 100'\n> avdevice: '58, 8, 100'\n> avformat: '58, 29, 100'\n> avutil: '56, 31, 100'\n> swscale: ' 5, 5, 100'\n> \n> SDL:\n> =====================================\n> \n> Version: 2.0.12\n> Loading method: linked (WITH_SDL_DYNLOAD=OFF)\n> \n> Other Libraries:\n> =====================================\n> \n> OpenColorIO: 2, 0, 0\n> OpenImageIO: 2, 1, 15\n> OpenShadingLanguage: 1, 11, 10\n> OpenSubdiv: 0, 0, 0\n> OpenVDB: 8, 0, 0\n> Alembic: 1, 7, 16\n> USD: 0, 21, 2\n> \n> OpenGL:\n> =====================================\n> \n> renderer:\t'Intel(R) Iris(TM) Plus Graphics 640'\n> vendor:\t\t'Intel Inc.'\n> version:\t'4.1 INTEL-16.5.2'\n> extensions:\n> \tGL_APPLE_client_storage\n> \tGL_APPLE_container_object_shareable\n> \tGL_APPLE_flush_render\n> \tGL_APPLE_object_purgeable\n> \tGL_APPLE_rgb_422\n> \tGL_APPLE_row_bytes\n> \tGL_APPLE_texture_range\n> \tGL_ARB_ES2_compatibility\n> \tGL_ARB_blend_func_extended\n> \tGL_ARB_draw_buffers_blend\n> \tGL_ARB_draw_indirect\n> \tGL_ARB_explicit_attrib_location\n> \tGL_ARB_gpu_shader5\n> \tGL_ARB_gpu_shader_fp64\n> \tGL_ARB_instanced_arrays\n> \tGL_ARB_internalformat_query\n> \tGL_ARB_occlusion_query2\n> \tGL_ARB_sample_shading\n> \tGL_ARB_sampler_objects\n> \tGL_ARB_separate_shader_objects\n> \tGL_ARB_shader_bit_encoding\n> \tGL_ARB_shader_subroutine\n> \tGL_ARB_shading_language_include\n> \tGL_ARB_tessellation_shader\n> \tGL_ARB_texture_buffer_object_rgb32\n> \tGL_ARB_texture_cube_map_array\n> \tGL_ARB_texture_gather\n> \tGL_ARB_texture_query_lod\n> \tGL_ARB_texture_rgb10_a2ui\n> \tGL_ARB_texture_storage\n> \tGL_ARB_texture_swizzle\n> \tGL_ARB_timer_query\n> \tGL_ARB_transform_feedback2\n> \tGL_ARB_transform_feedback3\n> \tGL_ARB_vertex_attrib_64bit\n> \tGL_ARB_vertex_type_2_10_10_10_rev\n> \tGL_ARB_viewport_array\n> \tGL_ATI_texture_mirror_once\n> \tGL_EXT_debug_label\n> \tGL_EXT_debug_marker\n> \tGL_EXT_framebuffer_multisample_blit_scaled\n> \tGL_EXT_texture_compression_s3tc\n> \tGL_EXT_texture_filter_anisotropic\n> \tGL_EXT_texture_sRGB_decode\n> \tGL_NV_texture_barrier\n> \n> Implementation Dependent OpenGL Limits:\n> =====================================\n> \n> Maximum DrawElements Vertices:\t1048575\n> Maximum DrawElements Indices:\t150000\n> \n> GLSL:\n> Maximum Varying Floats:\t150000\n> Maximum Vertex Attributes:\t16\n> Maximum Vertex Uniform Components:\t4096\n> Maximum Fragment Uniform Components:\t4096\n> Maximum Vertex Image Units:\t16\n> Maximum Fragment Image Units:\t16\n> Maximum Pipeline Image Units:\t80\n> \n> Cycles:\n> =====================================\n> \n> \n> CPU device capabilities: SSE2 SSE3 SSE41 AVX AVX2\n> \n> Enabled add-ons:\n> =====================================\n> \n> io_anim_bvh (version: (1, 0, 0), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_anim_bvh/__init__.py)\n> io_curve_svg (version: UNKNOWN, path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_curve_svg/__init__.py)\n> io_mesh_ply (version: UNKNOWN, path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_mesh_ply/__init__.py)\n> io_mesh_stl (version: (1, 1, 3), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_mesh_stl/__init__.py)\n> io_mesh_uv_layout (version: (1, 1, 1), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_mesh_uv_layout/__init__.py)\n> io_scene_fbx (version: (4, 22, 0), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_scene_fbx/__init__.py)\n> io_scene_gltf2 (version: (1, 6, 16), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_scene_gltf2/__init__.py)\n> io_scene_obj (version: (3, 8, 1), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_scene_obj/__init__.py)\n> io_scene_x3d (version: (2, 2, 5), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_scene_x3d/__init__.py)\n> cycles (version: UNKNOWN, path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/cycles/__init__.py)\n> GTry (version: (1, 3, 7), path: /Users/wgeithner/Library/Application Support/Blender/2.93/scripts/addons/GTry/__init__.py)\n> add_curve_sapling (version: (0, 3, 4), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/add_curve_sapling/__init__.py)\n> materials_utils (version: (2, 2, 0), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/materials_utils/__init__.py)\n> materials_library_vx (version: (0, 6, 0), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/materials_library_vx/__init__.py)\n> render_auto_tile_size (version: (3, 1, 3), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/render_auto_tile_size.py)\n> ```\n\n\n[BlenderCrash_20210730-01](BlenderCrash_20210730-01)\n[BlenderCrash_20210801-01](BlenderCrash_20210801-01)", "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", "Mouse movement causes crash during particle bake\nOperating system: Win10\nGraphics card: GTX2060\n\nBroken: 2.90, 0330d1af29c0, master, 2020-08-31\n\nReproducible crash when baking particle animation and moving mouse\n\nSadly, I was not able to reproduce the crash in a simpler file, so I assume it has to be related to the current boid setup with lots of drivers.\n\n1. Load the attached blend file\n2. Make sure Workspace is set to layout\n3. Select one of the two particle-emitters\n4. Click bake\n5. During bake move the mouse over Render or Graph views\n- > Crash\n\nAlso see this video capture: VIUy6r9S-Hk (It ends in the moment of the crash)\n\n[swarm-test1.crash.txt](swarm-test1.crash.txt)\n\n[swarm-test2-crash.blend](swarm-test2-crash.blend)", "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", "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." ]

[ "Audio playback doesn't work when a VSE sound strip is copy/pasted to a new scene\nOperating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5\n\nBroken: version: 2.90.0 Alpha\n\nAudio playback doesn't work when a VSE sound strip is copy/pasted to a new scene\n\n\n* File > new > Video Editing\n* Add > Sound. Choose a .wav file. In the sequencer, confirm it's playing correctly by clicking play on the transport.\n* Select and copy the sound strip to the clipboard\n* Create a new scene.\n* Paste the strip into the VSE in the new scene.\n* Play the new scene. There's no audio.\n" ]

[ "Expand face sets freeze blender when cursor is on mesh boundaries\nOperating system: Linux (Mint 21) \nGraphics card: RTX 3070 Ti\n\nBroken: 4.0.0 alpha, 12f51bd1c77b, master, 2023-09-21, as found on the splash screen)\nWorked: 3.6\n\nTry to create new face sets from first or last face loops on a cylinder.\nBut expand Face Set from boundaries is frozen in 4.0 alpha.\n\n\n- Open the blend file\n\n- Switch to Sculpt mode\n\n- Move your cursor outside boundaries and press Expand Face Set (Shift +W). (See on pictures)\n\nAt this point, Blender freeze, not crash. No more info in console.\n\nBug :\n\n\nExpected (3.6 version): \n\n\nThanks for your help.\n\n", "Select loop only works if the hidden face is a ngon\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3070\n\nBroken: 3.3, 2.79b\nWorked: 2.49b, 2.59\n\nCan't select the boundary loop of a hidden face, unless the face is an ngon.\nThe expected selection behavior is the same as if the face was deleted instead of hidden.\nIn ancient Blender versions it works.\n\n- Open attached file\n- Alt click to select the open loop. It will only select an edge (selects loop for n > 4)\n[bug.blend](bug.blend)", "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", " Render Face Sets and Mask as contour lines\nFace Sets were added to control the visibility of all paint modes and currently, they are rendered as colors (which is the easiest way to debug them and work with them from sculpt mode). This won't work for vertex paint and texture paint (and any other mode that works with color), so a different rendering needs to be implemented that does not affect the color of the surface as an option these painting modes. \n\nIf possible, this should be implemented for the current sculpt mask (add an option to render it as a contour line, similar to the lasso selection) as the same mask implementation and rendering will also be used for vertex paint.", "Sculpt Mode Border Mask Tool Todo\n## Sculpt Mode Border Mask Tool Todo\n * - [x] {icon circle color=red} When this tool is selected, it currently shows the wrong tool settings which affect the brushes, not this tool. These should not be visible when this tool is active.\n * - [ ] {icon circle color=yellow} We should add a tool setting to add/remove the mask as you drag. Currently, the only way to remove from mask, is very hidden: You drag with RMB. This could become more consistent and more discoverable if we added the same Add/Remove buttons as with other Sculpt tools", "Instancing a collection with an object that has been Disabled in Viewport fails to correctly link in disabled objects breaking \"Make Instances Real\" operator\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0\n\nInstancing a collection into a scene fails to properly link in objects that have been disabled in viewport (henceforth disabled object) using either the \"Disable in Viewport\" icon in the outliner or by setting obj.disable_viewport = True in a script or console. This bug doesn't appear when you hide an object using the H key or obj.hide_set(True)\n\nThis means that if you instance a collection and then \"Make Instances Real\" that the disabled objects will not be transformed with the parent object even if they have been parented to it in the original file and Keep Hierarchy is checked. \n\nThis is a problem because if you have used the disabled object as the operand in e.g. a boolean modifier then as soon as you make a collection real your collection breaks. This is doubly a problem since the default behaviour in the new asset browser is to instance collections into the scene rather than appending them. This bug also affects instancing a collection in the same scene as well as instancing in a collection from an external file. \n\nStart from default file. \nAdd a second cube.\nTransform second cube and place on corner of default cube.\nMake second cube a child of default cube.\nAdd a boolean difference modifier to default cube.\nSet second cube as Object in boolean modifier\nDisable second cube in viewport in the outliner\nInstance collection into scene by dragging and dropping collection from outliner somewhere which isn't the origin.\nEverything appears as it should.\nSelect instanced collection\nSelect Object > Apply > Make Instances Real\nWhile the none disabled cube has been made real the second cube hasn't and if we look in the modifier you can see that the boolean object is still set to the original second cube.\n\nIf instead of disabling the second cube we instead hide it and then instance the collection into the scene the second cube is linked in (although it's also unhidden which is annoying). If we the make this collection real everything works as it should (i.e. the second cube used as a boolean is also made real)\n[link bug.blend](link_bug.blend)", "Viewport Z-Bias & retopology overlay related issues\nSince this is being reported frequently and retopology overly has caused some weird issue with mask display as well previously, it's best we keep track of them in a central place so we could check if any particular fix is working for all situations:\n\n------\n\nProblem still presents:\n\n- Retopology overlay affecting other parts of the drawing/picking operation: #109115 #107768 ~~#109277~~ ~~#107411~~\n- (Potentially related) Selecting when X-Ray turned on is not visually effective and then switching to face mode crashes: #110136\n\n------\n\nFixed:\n\n- ~~Wireframe visible in close distances: #110048 #109040 #109514 #109499 #109685~~\n- ~~Retopology overlay 0 z offset problem: #109662~~\n\n-------\n\nProbable cause:\n\nAs suggested in 107768#issuecomment-937545 , I believe the problem here is that\n\n1. `DRW_object_is_in_edit_mode` does not exclusively check if object is in edit mode, but it combines other logics that affects drawing and stuff.\n2. `XRAY_ENABLED` marco is not always accompanied with `RETOPOLOGY_ENABLED`, this leads to inconsistencies in the user interaction and the display.", "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", "`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", "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", "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.", "2.91 - Undo in Sculpt Mode switches tool to inflate brush (specific to attached file)\nOperating system: Win 10 64-bit\nGraphics card: Nvidia GFX 1060 6GB\n\nBroken: \n - 2.90.1\n - 2.91.0, from steam, seems *file specific*\n - 2.92.0\nWorked: 2.91.0, same version, fresh file\n\nWith attached file: In sculpt mode calling undo changes the tool to \"Inflate\" besides undoing.\n\nAdditionally, when undo is called via menu, the undo operation happens only when undoing so far back sculpt mode was entered. On reentering Sculpt Mode, tool is set to \"Inflate\". \n\nThis issues seems to be tied to this specific file, as it's not reproducible in a fresh file. The file was created with blender 2.91.0. I sculpted multiple objects using both Dynamesh and Remesh in Sculpt Mode. I deleted the sculpts to keep the file size small and since the same behavior persisted with newly created geometry (in this case a cube). I don't know how to debug this any further, any hints appreciated. As a workaround I will try to reimport the geometry into a new file.\n\nBased on the attached .blend file [SculptModeBug.blend](SculptModeBug.blend)\n\nUndoing with shortcut:\n - Select object \n - enter sculpt mode\n - select any other tool than \"Inflate\"\n - modify mesh with tool\n - hit ctrl + z\n - tool switched to \"Inflate\"\n\nUndoing via menu:\n - Select object \n - enter sculpt mode\n - select any other tool than \"Inflate\"\n - modify mesh with tool\n - modify mesh with tool\n - call \"undo\" from menu \"edit/undo\" - this has no effect\n - call \"undo\" from menu \"edit/undo\" until the point object goes back to Object Mode - changes get undone\n - On entering Sculpt Mode again, the active tool has switched to \"Inflate\"\n", "(Shrinkwrap) Modifiers and constraints targeting a mesh wont update during that meshes sculpting session (unless an additional mirror modifier is in play)\n2.8x - 3.0 (may exist in older versions)\n\nAppearently I cannot modify the shape of the target mesh in sculpt mode since the shrinkwrap on the main mesh does not update unless I click somewhere else and not use the sculpt tools. It does update in edit mode tho.\nI remember someone saying its supposed to happen in order to keep performance running smooth or something like that, but I hardly believe it.\n\nThe only way to be able to update shrinkwrap is to add a mirror modifier to the target mesh and then you can now use sculpt mode with no issues. I've done this a few times now and I barely noticed any performance impact.\n\n1) Add a mesh, any mesh\n2) Give it a shrinkwrap modifier\n3) Add another mesh that will be used as the target\n4) Go to sculpt mode and shape up the target mesh\n\nNo update on shrinkwrap unless I click something else around the UI\n\nTo fix this:\nif the model has one mesh and I wanna edit it symmetrically, I cut it in half and add a mirror modifier to it\nShrinkwrap now updates all the time when I sculpt the target mesh without needing to click somewhere\n\nFrom there on I can do whatever I want with the target mesh in sculpt mode", "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", "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" ]

[ "Parts of the mesh disappear in Sculpt and in Edit mode but not in objec\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 9)\nWorked: 2.83 `c26f470cfeea` is last I can check\n\nFor some reason parts of the mesh will disappear in sculpt mode and sometimes in edit mode.\n[2020-03-15 22-23-42.mkv](2020-03-15_22-23-42.mkv)\n\nI'm not sure how the bug is produced. I created a mesh from a circle to make a body shape and at a certain point the mesh disappears when I enter sculpt mode.\n\n\n[Mesh Hidden Error.blend](Mesh_Hidden_Error.blend)\n" ]

[ "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", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "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", "Hair (Particles): Cannot animate the property hair_lenght\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14739 Core Profile Context 21.6.1 27.20.22001.14011\n\nBroken: version: 2.93.5\n\nI can't animate the hair_lenght property in hair (particles)\n\n1. Select an object (mesh) and add hair (particles) to it.\n2. Add an animation key in the Hair Lenght property (4m by default).\n3. Change to another frame, modify the Hair Lenght property (put 0m for example) and add a new animation key.\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", "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", "Texture paint undo sometimes changes texture slot\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 2.80 (sub 48), 2019-03-12 13:53, hash: 936014ea8c74\n\nWhen texture painting on a particular texture slot, then undoing that painting, sometimes the selected paint slot will change.\n\nI couldn't reproduce from the default startup file, so I've stripped down the file that's having problems as much as I can.\n\n1. Open attached file\n2. Select paint slot \"Skin mask\" from either topbar or properties panel.\n3. Paint some strokes on the model or image editor\n4. Press Ctrl-Z\n5. Notice the paint slot is no longer set to \"Skin mask\"\n\n- - -\n\n- Change to the Skin Mask slot.\n- Paint a single stroke in the image editor.\n- Undo two times.\n- Paint another single stroke in the image editor.\n- Undo one time.\n- Notice that the slot changed.\n[texturepaintbug.blend](texturepaintbug.blend)", "Meshes that are generated with the screw modifier cant use the box projection type\nOperating system:\nGraphics card:\n\nBroken: 83f9218801d4\n\nThe meshes that are modified or extended by the screw modifier can't use the box projection of an image map. All the objects in the screenshot use the same material and the texture projection. As you can see the box and the plane has no problem with the projection type.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nLoad the attached .blend\n\nEnable the material preview and check the object named \"Screw\"\n\nCtrl-A -> \"visual geometry to mesh\" to see that the texture would normally work on the mesh, except ehwn the modifier is enabled.\n\n[_23012023_1655_00.zip](_23012023_1655_00.zip)", "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) ", "Grease Pencil Fill Tool Breaks After Scroll-Wheel Zooming Window\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0 Beta\nAlso tested in 2.83.9 & 2.92 Alpha on Windows, and 2.91 Beta on Mac with same results.\n\nIf an 'unclosed' area made with grease pencil lines on its own layer overlaps and is 'closed' with grease pencil lines on a second layer, zooming the 2d workspace in and out will cause the fill tool to 'break' and fill the whole screen; even when the fill tool is set to: Advanced-Layers-Visible. \n\nCreate closed shape on one layer. Create 'open' shape on second layer that overlaps and is closed by grease pencil lines from the first layer. Zoom in and out in workspace while using the fill tool in a separate 'fill' layer. \nPlease see attached .blend file and screen capture: \n\n[FillTest.blend](FillTest.blend)\n\n[FillTest.mp4](FillTest.mp4)\n\n\nI really hope this isn't just user error. Thank you for taking a look!\n", "Bug with environment texture\nOperating system: Windows 10\nGraphics card: Nvidia GeForce RTX 3050 Laptop GPU\n\n3.6.2\n\nAfter I checked and unchecked \"Open Shading Language\" checkbox Blender crashed, after that I opened my project and turned rendered viewport the environment texture become a one solid color, and as I was rotating my camera it was changing the color.\n\nBased on an attached .blend file you can go to the Render viewport and take a look at this error.\n\n", "Hair particles: Entering sculpt mode [dyntopo] changes hair particle distribution without warning\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: Don't know\n\nEntering Sculpt Mode can mess up particle settings without warning. See the attached gif. \n\n\nIn the attached blend file, notice hair in the \"x\" pattern on the cube. Switch to Sculpt Mode, then back to the Particle Edit mode. Notice the hair pattern has changed. \n\n[sculpt_hair_test.blend](sculpt_hair_test.blend)\n\nTo reproduce the issue from scratch, follow these steps: \n- Modify a mesh using sculpting tools with Dyntopo enabled. \n- Make sure the mesh has no vertex data that would cause Dyntopo to turn off when you switch away from and back to sculpting mode.\n- Make sure Dyntopo is on and switch away from sculpting mode.\n- Add a hair particle system to the mesh. Use the particle editor to add a recognizable shape to the hair.\n- Switch to sculpting mode.\n- Switch back to the particle editor and see the shape of the hair.", "Material slots menu: copy material and copy to selected work different\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\n\nCopy and paste material actually work as copy of all data from one material to another.\nCopy to selected do not work as copy, it acts like material linking/referencing\n\n**Steps to Reproduce**\n- Open attached file\n- Switch to material preview\n- In material properties tab open `material specials` popup\n- Click Copy materials to Selected\n[#85419.blend](T85419.blend)\n[2021-02-06_07-55-48.mp4](2021-02-06_07-55-48.mp4)", "Grease Pencil Vibrating Contours\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.83.4\n\nHi, i i have bug on Grease Pencil contours. When i move camera in animation contours vibrate, changing size. This is not problem with my PC, because i tried it on another and problem is the same. I tried Anit-Aliasing, change render engine (Cyles and Evee), the same bug is in viewport and in render animation. I'm attach the video of this bug. This bug occurs just with camera or object move. \n\n1. Create Grease Pencil object.\n2. Move camera to \"zoom\" it.\n\n[vibrating contours.mp4](vibrating_contours.mp4)\n\n[vibrating contours.blend](vibrating_contours.blend)\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 attributes added to regular material\nOperating system: linux Mint\nGraphics card: Nvidia 1070\n\nBroken: 2.8 4439e5d0ba3f\nWorked: (optional)\n\nGrease pecil attributes on regular materials on file load.\n\nGetting grease pencil attributes added on some regular materials on file load.\nAllready have such error reported ~10 days ago.\n\n[gp_material_mess.blend](gp_material_mess.blend)" ]

[ "Removing Effectors (from a Collection, or deleting corresponding object) does not refresh physics, hair properly\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.83.8\n\n**Desription**\nHairs do not react to force deleting.\n\n**To reproduce**\nOpen file, delete force field object.\nHair system will keep it`s deformed shape, despite force do not exist anymore.\n\n[2020-11-08_22-34-26.mp4](2020-11-08_22-34-26.mp4)\n[late responce.blend](late_responce.blend)\n\n- in `build_effector_relations` the relation is properly **not** built anymore, but there is no way to detect if this actually changed compared to the previous state. \nAnd since nothing else changed in participating objects (e.g. it doesnt even refresh if you have two forcefields and remove one of them), no \"proper\" update happens.", "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", "Modifiers don't work on particle instances of a hidden object\nOperating system: Linux Mint 20.3 Cinnamon kernel 5.13.0-35\nGraphics card: 3400G\n\nBroken: 2.83\nWorking: apparently never\n\nRelated to #96367 (Crash when trying to snap to instances on an object)\nTo replicate bug, the instantiated Object (the one with a `Modifier`) has to meet the following conditions:\n* Must have a modifier (obviously)\n* Must be instantiated through a particle system. (instantiated through Geom Nodes is OK and through Dupli Verts/Faces hides the `Object` as well)\n* Must be hidden inside a collection with the `Excluded from View Layer` option enabled\n\nAnd the instantiating Object (the one with `Particle System`) has to meet the following conditions:\n* Must be referenced by a `Camera` in the \"`Focus on Object`\" field\n* In the outliner, the `Camera` object must be placed in a `Collection` before the instantiating Object\n\n|||\n| -- | -- |\n|Camera placed before |Camera placed after\n\n # Open the attached file\nUnhide collection or switch `Camera` and `Plane with particle system` collections order (via Drag and Drop) get around the problem.\n[Camera 'Focus on Object' - particle system issue.blend](Camera__Focus_on_Object__-_particle_system_issue.blend)", "Particle system bug with texture influence\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: N/A.\n\nParticle system caching issue. \n\n1. Make a particle system with collider that kills particle. Add a cloud texture to influence it's density.\n2. Now bake.\n3. Now later when you increase or decrease size of the particle. the cache breaks. \n4. Some particle is starting to stay on collide serve instead of killing . And some particle floats around.", "Hair Particles: Deflect Emitter distance will affect all edited hairs on entering particle particle editmode\nWindows 10 Home \nIntel Pentium G4560 \n16 GB\nIntegrated GPU \n\n**Blender 2.79**\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n**Short description of the error**\n\nI have a hair particle system on a mesh emitter and I want to comb hairs with diferent angles. For this I set the Deflect emitter to 0.1 so it stands pretty straight up and comb it . Then I do the same on another part of the mesh but this time setting deflect emitter to 3 and automatically all the combed hairs ( including the 0.1 ones ) are set to 3.\n\n1)Create a cube \n2)aply a subsurface modifier with 4 subdivisions\n3)aply a particle system with hair type\n4)switch to particle edit mode\n5)in tools tab choose comb and set deflect emitter to 0.1 and comb one side of the cube\n6)set deflect emitter to 3 and comb another side of the cube\n7)switch back to object mode ( everything looks ok)\n8)switch to particle edit mode again ( and now the side combed with the deflect emitter set to 0.1 \n is changed to match the side with deflect emitter set to 3 )\n\nAttached file [cube with hairs.blend](cube_with_hairs.blend)\nNote: If we invert step 5 and 6 order the error is not reproduce.", "Particle system behaves inconsistently in viewport and render when instance object visibility is disabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro [P2200](SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.91.0 Beta\nWorked: The behavior was different in 2.80\n\nWhen the instance object of a particle system is disabled in the viewport the particles are also disabled in the viewport. However when the instance object is disabled in render they still appear in the render.\n\n1. Open the default scene.\n2. Create another object (B).\n3. Create a particle system modifier on the default cube (A).\n4. Set Particle Settings to Hair (A).\n5. Set Render -> Render As to \"Object\" (A)\n6. Set the Instance Object to the other object (B).\n7. Disable the object (B) in viewport and render\n8. Render the scene, observe that the object has particles rendered\n[particle_visibility_bug.blend](particle_visibility_bug.blend)\n", "Datablocks can't be duplicated everywhere, because trick with fake user no longer works\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4454\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional) 2.79b\n\n\nThe MCE or tracker, should allow you to duplicate the clip asset so that you can attach other tracker bundles. In 2.8 it does not allow you to create more instances.\n\nHowever I was able to make a duplicate of a Movie Clip which is reflected in its datablock. I opened a legacy tracking project from 2.79b. It had some duplicated clips already. Once this function (multiple instances) is activated I am able to duplicate them more by using the counter buton next to the Clip name in the MCE.\n\n[Please describe the exact steps needed to reproduce the issue] Make a project in 2.79 with multiple instances of a Movie Clip then open it in 2.8. The number indicator appears. Otherwise opening a movie clip in 2.8 it does not.\n[Based on the default startup or an attached .blend file (as simple as possible)] Find the .blend of a project with extra Movie Clip instances attached{[F7091277](broken_MCE_clip_users.blend)}\n\n", "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)", "Duplicating hair particles from one file to another is not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.25\n\nBroken: version: 3.3.0\nWorked: I don't know. And at least, v3.2.1 is also affected.\n\nFor Eevee rendering, duplicating the hair particles within the same file is working as expected, because the duplication and the original hair look exactly the same. \nHowever, duplicating the hair particles from one file to another is not working for Eevee rendering, because they do not look identical. \nMoreover, under the Eevee rendering, the duplicated hair can no longer be controlled by the particle system. (In comparison, Cycles rendering is not affected by this problem.)\n\nThe video to reproduce the error:\n[Duplicate hair under Eevee.mkv](Duplicate_hair_under_Eevee.mkv)\n\n**Steps to reproduce**\n[eevee hair test3.blend](eevee_hair_test3.blend)\n\n- Open file\n- Copy objects `LLonglash` and `LLonglash.001`\n- Open new file\n- Paste objects\n# Inspect hair shape\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)", "Creating Lattice object with script with {\"REGISTER\", \"UNDO\"} if parameters was changed in Undo window and mesh was in Edit mode - undo last changes to the mesh or last action\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.1\n\n{\"REGISTER\", \"UNDO\"} also undo last action if parameters was changed in \"Adjust last action\" pannel and mesh was in Edit mode.\n\n[Register_Undo_Issue.mp4](Register_Undo_Issue.mp4)\n\n[REGISTER_UNDO_in_EDIT_Mode.blend](REGISTER_UNDO_in_EDIT_Mode.blend)\n\n", "Show Emitter toggle still hides object after Particle System has been deleted.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.92.0 Alpha\nWorked: version: \n- 2.92.0 Alpha\n- 2.91.0 Release\n\nWhen you delete a particle system with show emitter unchecked under Viewport Display the object stays hidden. You have to re-add the particle system and check Show Emitter.\n\n- Add Particle System to default cube.\n- Uncheck Show Emitter under Viewport Display\n- Delete Particle System. \n\n", "Hair (Particles): Cannot animate the property hair_lenght\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14739 Core Profile Context 21.6.1 27.20.22001.14011\n\nBroken: version: 2.93.5\n\nI can't animate the hair_lenght property in hair (particles)\n\n1. Select an object (mesh) and add hair (particles) to it.\n2. Add an animation key in the Hair Lenght property (4m by default).\n3. Change to another frame, modify the Hair Lenght property (put 0m for example) and add a new animation key.\n\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", "Crash when renaming a world in a timer and dragging a world in the asset browser\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.23\n\nBroken: version: 3.4.0 Alpha\nWorked: Don't know, tested back to 3.1, and still got the crash\n\nWhen a python timer renames a world, and the user is dragging a world *from another file* in the asset browser, blender will crash. (doesn't happen if the world is from the current file)\n\nI also tested this on materials, and it didn't cause a crash, so I assume that it's limited to just worlds.\n\n[world renaming crash.blend](world_renaming_crash.blend)\n* Open the attached blend file, and run the script in the text editor.\n* That will start a timer that will run once a second for ten seconds, and will rename a world data-block each time.\n* During those ten seconds, in the asset browser window, start dragging a world asset that originates from another file.\n* Blender should crash.\n\n[2022-10-23 15-49-18.mp4](2022-10-23_15-49-18.mp4)\n\nThanks a lot!" ]

[ "Renaming of Vertex Groups not possible in complex projects\nBroken: blender 2.80rc1\nWorked: 2.79b\n\nRenaming of Vertex Groups not possible in complex projects\n\n - Open [Bug_vertexGroupsRenaming.blend](Bug_vertexGroupsRenaming.blend)\n - Double click to try to rename the Vertex Group\nor\n - Start New File\n - add a vertex group (renaming is still possible)\n - add an emitter (in this case: hair)\n - increase the number: If the number is set to 100000\n - renaming of the vertex group is not possible\n" ]

[ "Crash upon renaming collection or clicking on Blenderkit after creating said collection (without renaming)\nOperating system: Win 10\nGraphics card: Nvidia Quadro M5000 \n\nBroken: 3.4.1\nWorked: 3.4.1\n\nCrash upon renaming collection or clicking on Blenderkit after creating said collection (without renaming). \n\n- Download file through the link from Google Drive attached (I leave the file as it is since I don't know what caused the problem)\n- Click in the collection \"Möblierung\",\n- create some new collection in it,\n- rename the new collection (with double click)\n- hit enter - crash\n\nOr create the collection, don't rename it and then click something in the interface (Blenderkit \"eye\" symbol in my case).\n\nReload didn't do anything, just kept crashing.\n\nLoaded a recent autosave, seems to work. Already hat to kill startup file and all settings yesterday, got permanent exception access violation crashes upon file load, after enabling some addon (TrueAssets) it worked.\n\nLink to the blend: view?usp=sharing\n\n", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\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", "Its possible to create Built-in attributes with wrong metadata\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\n\nSee attached stack trace file.\n\n```\nCode marked as unreachable has been executed. Please report this as a bug.\nError found at C:\\Users\\blender\\git\\blender-vdev\\blender.git\\source\\blender\\blenkernel\\intern\\attribute.cc:486 in BKE_id_attribute_remove.\nSaved session recovery to \"C:\\Users\\rfnei\\AppData\\Local\\Temp\\quit.blend\"\n```\n\n1. Create any attribute on mesh.\n2. Rename it to `material_index`.\n3. In debug: try to delite this.\n\n", "Crash when renaming a world in a timer and dragging a world in the asset browser\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.23\n\nBroken: version: 3.4.0 Alpha\nWorked: Don't know, tested back to 3.1, and still got the crash\n\nWhen a python timer renames a world, and the user is dragging a world *from another file* in the asset browser, blender will crash. (doesn't happen if the world is from the current file)\n\nI also tested this on materials, and it didn't cause a crash, so I assume that it's limited to just worlds.\n\n[world renaming crash.blend](world_renaming_crash.blend)\n* Open the attached blend file, and run the script in the text editor.\n* That will start a timer that will run once a second for ten seconds, and will rename a world data-block each time.\n* During those ten seconds, in the asset browser window, start dragging a world asset that originates from another file.\n* Blender should crash.\n\n[2022-10-23 15-49-18.mp4](2022-10-23_15-49-18.mp4)\n\nThanks a lot!", "Cycles vertex color bump map banding \nOperating system: Win10\nGraphics card: GTX 1070\n\n2.79b release\n\nUsing vertex colors in cycles material as a mask for bump/normal texture causes banding/hard edges in render.\n\nBanding of vertex color is also visible when using it as a color for shader. \n\nIt might have something to do with the fact that vertex colors are represented in 8-bit sRGB values but on the other hand it renders as expected when using it as a mask for example for mix shader node. But the bump doesn't look correct in that case.\n\n\n[vertex_color_mask_problem.blend](vertex_color_mask_problem.blend)", "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", "Fast highpoly mesh editing\n**Status:** Need work plan \"approval\", all tasks listed already. Could use a design / engineer plan and ideally a commissioner (though if the scope here is super technical just having some artists testing may be enough.\n\n---\n\n**Team**\n**Commissioner:** `?`\n**Project leader:** @ideasman42 \n**Project members:** @fclem\n\n**Description**\n**Big picture:** 2.7x level of performance for mesh editing.\n\n**Use cases**:\n* Editing high poly objects with good performance without modifiers.\n* Sample file with 3M avaiable on request, file is ~300MB.\n\n**Design:** #74186 (Proposal for fast high poly mesh editing)\n\n**Engineer plan:** `?`\n\n**Work plan**\n\n**Milestone 1**\nTime estimate: `?`\n\n- [ ] Skip EditMesh to Mesh Conversion [D7169](D7169) (committed)\n\n - [x] Create API function to lazily initialize an edit-mesh objects evaluation mesh #64262\n - [x] Lazily initialize by disabling edit-mesh to mesh conversion in the modifier stack, calling lazy initialization where needed.\n - [ ] Replace lazy initialization with code that uses the edit-mesh, where practical. *(partially done)*\n - [ ] Evaluate production scenes *(yet to be defined)* to ensure that conversion isn't required for common editing operations.\n - [x] Draw manager support deformed edit-meshes, so an edit-mesh conversion isn't required when drawing an edit-meshes deformed cage *(similar to 2.7x support).*\n\n- [ ] Minimize GPU Transfer Overhead\n\n - [ ] Create API functions for tagging edit-mesh changes.\n - [ ] Limit updates to: selection data, active element.\n - [ ] Edge Flags Sharpness Seam\n - [ ] Limit updates to: deformations.\n\n - [ ] Coordinates, Face centers & normals.\n - [ ] Custom normals.\n - [ ] UV-tangents.\n\n - [ ] Limit updates to: custom-data layers.\n\n - [ ] UV coordinates.\n - [ ] UV selection.\n - [ ] Vertex color.\n - [ ] Vertex group color.\n - [ ] Custom normals.\n\n - [ ] Limit updates to: mesh properties.\n\n - [ ] Edge crease.\n - [ ] Edge flags (sharp, seam).\n - [ ] Face flags (freestyle).\n\n\n- [ ] Multi-Thread bmesh to mesh conversion.\n\n - [ ] For evaluation mesh *(uses simplified logic)*. [D6947](D6947)\n - [ ] For the full bmesh to mesh coversion *(uses more complex logic).*\n\n- [ ] Optimize edit-mesh GPU updating code\n\n *Benchmark production files, and investigate if the current code has room for improvement, making necessary optimizations.*\n\n**Milestone 2**\nTime estimate: `?`\n\n- [ ] Partial Geometry Updates\n\n - [ ] Support updating only modified geometry when transforming vertex coordinates.\n\n - [x] Coordinates.\n - [x] Normals.\n - [ ] Custom Normals *(note: need to investigate feasibility)*.\n - [ ] UV-tangents *(note: need to investigate feasibility)*.\n\n - [ ] Support partial updates for custom data layers.\n\n - [ ] UV mapping.\n\n - [ ] Mesh UV coordinates.\n - [ ] Mesh UV-tangents.\n - [ ] UV editor coordinate display.\n\n *note: we may run into diminishing returns with UV layer partial updates for custom-data layers, since only updating a single layer will already give us significant benefits. I'd suggest only to support this if it doesn't add a lot of code-complexity.*\n\n- [ ] Multi-object edit-mode\n\n - [ ] Undo optimization: skip mesh conversion for meshes which aren't modified.\n\n- [ ] BMesh support for the modifier stack.\n\n**Milestone 3 - opensubdiv**\n*Fast mesh OpenSubdiv viewport implementation.*\nTime estimate: `?`\n\n**Unknown Milestone**\n\n- [ ] Multi-thread edit-mesh to GPU data uploading.\n- [ ] Improve geometry buffer configuration (data layout used by the draw manager). \n\n\n**Notes:** Optimizing modifiers is out of the scope.\n\n---\n\n**Relevant links**:\n* #57936 (Mesh modeling performance regressions)", "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)", "Error during connection custom sockets to group input / output nodes\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\n\n\nMy guess is that this is relevant to connecting custom (Sverchok) sockets because connecting standard color socket does not caus the error in a console.\n\n```Code 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\nCan't help but report with such the invitation))\n\n1. Download sverchok add-on\n2. Add a node group\n3. Connect any node to group input / output nodes\n\n[2021-06-03 16-45-28.mp4](2021-06-03_16-45-28.mp4)\n", "Transfer vertex index\nAs we discussed on blender.chat, Blender would benefit from having an operator that can transfer the vertex index (order) from one object to another. If the vertex count between the source object and target object is mismatching, I think the transfer should go ahead and transfer what is possible instead of returning an error.\n\nOperator UI mockup\n\n\n---\n\nHere is an image to clarify. Only 6 vertices numbered in the image for readability. \n\n\n---\n\nEdge selection as sample type\nThis can be a good idea if the target object no longer resembles the source object because of sculpting or rotating the object (i.e. the position of vertices does no longer match between the objects). By selecting corresponding edges on the objects, it can be possible to \"crawl\" over the topology and thereby transfer vertices. \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)", "Support all attributes in the non-point cloud attribute list\nSee #87827.\n\n* position\n* UVMaps\n* Vertex groups\n(...)\n\nTechnical design discussion: #88460", "Memory leak with a combination of vertex groups and particle systems\nOperating system: Windows-10-10.0.19043-SP0 64 Bits, **This seems to happen only on Windows.**\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.1\nWorked: no one worked\n\n[system-info.txt](system-info.txt)\n\nThis is not an error but a memory leak bug. The ram is filled more and more at each render. I simplified the file as max as possible. When you remove the 20 copied particule systems, no bug anymore or when you remove all the vertex group, the bug also disappear. But when there is this combinaison of particule system and vertex group there is the memory leak. Note => I duplicated the particule system to see faster ram growth\n\n[Memory leak the animal.blend](Memory_leak_the_animal.blend)\nOpen the file \nrender image repeatedly.\nBlender will use all available memory.\nDoes not happen when rendering animation.", "Node Group Inputs\nNode groups serve the purpose of combining multiple nodes into reusable components. To make them more useful, node groups can have a set of inputs that the \"caller\" has to provide. Currently, node groups have one Group Input and one Group Output node. This works well for many cases. However, I'd argue that there is a better way to do it (both approaches are used in multiple other pieces of software).\n\nSome motivation for implementing a new approach:\n- When a node group needs more inputs, there is usually a large node on the left side of a node tree that has links to many other nodes. I'd argue that these links add more confusion than they actually provide information to the user. At some point it becomes quite hard to follow these links through the entire node tree.\n- In the current implementation, there is no mechanism that supports grouping of inputs. \n- Important information like the min/max/default values is hidden in a panel in the sidebar.\n\nPersonally, I think it would be good to allow multiple Input Parameter nodes in a node group. Something like this:\n\n\nSome notes on this approach:\n- For different data types, a different set of settings can be shown. Of course the node can also be collapsed when not all information is necessary.\n- The node can be placed exactly where the value is needed, providing better information when actually working on the node tree.\n- All the settings can still be shown in a side bar to have all information accessible in a single place.\n- We could also allow multiple inputs per Function Parameter node for better grouping of related settings.\n\nImplementation wise, this approach might actually be simpler than the old solution.\nAt the same it scales better when node trees get larger and when we want groups to become more powerful." ]

[ "Double Click Rename Fails if Too Many Particles\nOperating system: Ubuntu 18.04\nGraphics card: GTX 1080 Ti\n\nBroken: 2.80 (for at least 2 months)\n\nIf there are too many particles in the scene (100,000-1,000,000), then double clicking to rename a particle system/material does not work anymore.\n\n1. Add a particle system to the default cube\n2. Double click on the name of the default cube's particle system to see the baseline renaming method\n3. Change to hair particle system and set the amount of hair to 1,000,000 or enough the lag the computer in Particle Edit mode when a comb operation is applied\n4. Double click on the name of the particle system, or a material, vertex group, etc. and observe that the rename tool doesn't appear" ]

[ "Grease Pencil ripped line when rendering in EVEE\nOperating system: Windows 10\nGraphics card: GeForce 1050 ti\n\n3.62\n\nGrease pencil object is displayed normally in the viewport, but when rendering the line becomes jagged, not like in the viewport. In Cycles all is good.\n\n\n\n", "Sculpting: Draw Sharp brush has sharp point at the beginning of the line\n**Broken:** \nBlender version: 2.93.7, 3.0, 3.1 (27.12.2021)\n\n**Short Description**\nDraw Sharp brush line is uneven at the beginning of the line there is a sharp point. It can be seen with large radius of the brush.\n\n**Steps to reproduce:**\n1. Default scene\n2. Remesh cube, Voxel Size 0.01.\n3. Brush \"Draw Sharp\", Radius 200-500 px.\n\n\nTest File:\n[#94463.blend](T94463.blend)", "Grease Pencil Vibrating Contours\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.83.4\n\nHi, i i have bug on Grease Pencil contours. When i move camera in animation contours vibrate, changing size. This is not problem with my PC, because i tried it on another and problem is the same. I tried Anit-Aliasing, change render engine (Cyles and Evee), the same bug is in viewport and in render animation. I'm attach the video of this bug. This bug occurs just with camera or object move. \n\n1. Create Grease Pencil object.\n2. Move camera to \"zoom\" it.\n\n[vibrating contours.mp4](vibrating_contours.mp4)\n\n[vibrating contours.blend](vibrating_contours.blend)\n", "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.", "Grease pencil eraser settings not loaded on startup when using ctrl+LMB with the Draw tool\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 26.20.100.7925\n\nBroken: version: 2.90.0\n\nWhen first opening a blend file, your eraser settings are set to default when using ctrl+LMB with the draw tool, and only update after switching to the eraser tool and using it.\n\n\n- Open attached file (the Stroke object is selected and the Draw tool activated in Draw mode).\n- Draw a line\n- Erase part of the line using the same tool but with Ctrl selected. Notice how it behaves as if the `\"Eraser Soft\"` brush is used. \n- Switch to the Eraser tool, erase part of the line. Notice how it behaves according to the specified Brush: `\"Eraser Point\"`. \n- Switch back to Draw tool, and hold down ctrl to erase another part of the line, it should now start behaving like the `\"Eraser Point\"` brush.\n\n[eraser bug.blend](eraser_bug.blend)\n\n", "Line Art Thickness doesn't consider Render Resolution Percentage\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.1122\n\nBroken: version: 3.2.2\nBroken: version: 3.4.0 Alpha\nBroken\n\nWhen using Line Art Modifier, on a Grease Pencil Object in Screen Space Mode, Line Thickness doesn't scale with resolution as expected. \n\n1. Open new General Startup File\n2. Create New Object>Grease Pencil>Scene Line Art\n3. Under Object Data Properties>Strokes>Stroke Thickness and set to World Space\n4. Set Render Resolution % to a factor. line thickness will be different than expected\n\n\n\n\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", "Exchanging a color in Grease pencil from a color attribute is bugged\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 3.4.1\n\n**Short Description**\nExchanging a color in Grease pencil from a color attribute is bugged\n\n- Go into 2D animation\n- Draw a shape with a fill color using a color attribute\n- Change color attribute and draw another fill stroke\n- In materials tab create a new fill color\n- Assign that color in edit-mode to the shape to replace color attribute. \nIt doesn't look like it got applied. Go into viewport shading with material view and the assigned color is there. Pressing F12 shows the color that is supposed to be overwritten.[Color error.blend](Color_error.blend)", "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)", "GPencil: Low hardness values always draws yellow\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.91.0 Alpha\n\nGrease Pencil creates yellow transparency with lower hardness values on brush.\n\n - Open in 2D Animation mode\n - Set to a \"Dots\" brush (eg. Dots Brush) its most noticeably shown there. It happens for the other ones too but this one is most noticeable\n - Set the Radius to something largish so we can see whats happening (eg 2000px), or zoom in \n - Draw a circle and you'll be able to see it\n\nIt looks like there's a faint yellow tinge transparency which builds up when putting the grease pencil strokes on top of each other.\nWhat it looks like:\n\n\nExample blend\n[yellowtransparency.blend](yellowtransparency.blend)\n\nBasic repro gif\n\n\nMe shading a ball\n\n\n\n\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: Strokes with texture & round caps have distorted extremities\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\n\nStrokes with a material of line type 'Line', a texture & round caps have distorted extremities.\n\n\n- Open file and see how the start & end of the drawn strokes are distorted.\n[round caps bug.blend](round_caps_bug.blend)\n\n", "GPencil: Square type strokes do not react to Rotation option with Solid Shading\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBroken: version: 3.0.0 Alpha\nWorked: ?\n\nThe stroke type Squares draw little squares at the points of the stroke. The rotation is controlled by the alignment option and the rotation slider, which in this case does nothing if solid shading mode is selected. Note that textures are not displayed in solid shading mode and even if used the squares don't rotate as long as I am in solid shading mode.\n\n1. Add default Stroke Grease Pencil Object\n2. Navigate to the Material and change Line Type to Squares\n3. Make sure you are in Solid Shading Mode with \"Color\" not set to \"Texture\"\n4. Change the Rotation slider from the same panel, which says in the tooltip it should rotate the squares\n5. observe how the squares do nothing at all.\n\n", "GPencil: Hotkeys of Tools is not consistent when Draw Tool is active\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.76\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nI'm not sure whether this is intended or not.\nHotkeys (1 to 9) shift downward one by one depending on whether you are in a draw tool or not.\n\n1. Go to Draw Mode\n2. Select a draw tool by pressing Shift Spacebar, O (Not 1)\n3. Select a fill tool by pressing Shift Spacebar, 1\n4. Select a draw tool by pressing Shift Spacebar, 1 (Not O)\n\n", "Holes converted to grease pencil are not holes after conversiton.\nOperating system: Linux mint\n\nBroken: 3.4.1\n\nUsing `bpy.ops.object.convert(target='GPENCIL')` to convert meshes to grease results in holes being filled. typical examples are text. Here is a text before conversion:\n\n\n\n\nafter conversion:\n\n\n\nGet the file:\n87623d\n\nTransform this to GPENCIL via python or object--> Conert --> Grease\n\n" ]

[ "Stylus pressure splike on first dab\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0 Release Candidate\nWorked: 2.91.2\n\nWhen using stylus(me wacom CTL-690),the first dab of a stroke has a too high pressure amount regardless of the actual pressure input.\nThe left stroke of each pair in the following pictures is drawn within Blender 2.92.0 and the right one is 2.91.2:\n  As what I have tested,sculpting,texture paint,weight paint and grease pencil all get influenced.\n\n{icon fa-plus} OS Conditon: **WIN 10** |Blender: **2.92.0 Candidate**|Tablet: **Wacom CTL-690**\n- Using stylus to draw a stroke in __sculpt mode__ , __texture paint mode__ , __weight paint mode__ or __grease pencil draw mode__ .Try having the pressure initially low,then the first dab drawn should get a high pressure amount which is false.\n{icon rocket} In case,this is the blend file which is used to capture the pictures above:[BugReport.blend](BugReport.blend)\n", "Grease Pencil default pencil in 2.92RC look and feel like ink unlike in 2.91.2\nOperating system: Windows 10\nGraphics card: NVidia GeForce RTX 2080\n\nBroken: 2.92 RC (only the RC versions tested everyday up to today, now)\nWorked: 2.91.2 and 2.92 alpha/beta\n\nThe default pencil of the grease pencil module look different then in the previous version! Here is a GIF on twitter to show what I mean! Someone mentioned it was like that on Mac for over a year, but I always used windows and I ain't sure what changed, but I cannot get the pencil to feel and look the same!\n\n1363609811900891143\n\nSimply open up 2.91.2 and 2.92 RC side by side and open a new 2D animation project for both and try the default pencil in both! Very different looking!!", "Brush Radius Pressure Sensitivity In Texture Paint Not Working\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25\n\nBroken: version: 2.92.0 Release Candidate\n\n[When texture painting with the pressure sensitivity enabled, the pressure sensitivity is not working at the start of the stroke resulting in a dot the size of the brush at the start of each stroke.]\n\n[Start a new default file. Go into Texture Paint mode on the default cube. Create a Paint slot and base color material for the cube. Enable pressure sensitivity for the brush size. Disable pressure sensitivity for the brush strength (this step for visibility only). Draw test strokes on the cube and observe the start of the strokes. A small 1 minute video is attached illustrating this behavior on my computer.{[F9828160](2021-02-22_11-06-21.mp4)}]\n\n\n", "Pressure sensitive brushes have an initial hard mark in the beginning\nOperating system: Windows 10 \nGraphics card: RTX 2070\nWacom Intuous Pro\n\nBroken: 2.92.RC0\nWorked: 2.91\n\n\nStarting of a brush always has a strong mark just in the beginning of the brush stroke in Sculpt mode or the image paint mode.\n\nI also tested the exact same setup in Blender 2.91 and that one has no such issue. It seems like this has been inctroduced in recent 2.92 builds. This rules out that this is not an hardware issue.\n\nI also get click stuck when changing between object mode panes like object properties and modifiers pane etc. I thought that w as a glitch but now it makes sense to me. There seems to be an issue with initial Wacom left click putting down on the surface whether hard press or a soft press. \n\n\n**Exact steps for others to reproduce the error**\nPlease see the attached videos for the issues. You can see the first hard markings in both modes. No matter how lightly I press down with the pen on the surface I am left with those marks..\n\n[236TXMQ0X6.mp4](236TXMQ0X6.mp4)\n\n[vXZqpLBEdX.mp4](vXZqpLBEdX.mp4)" ]

[ "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", "Curve to Mesh node causes other objects to edge split when not shaded smooth\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Beta\n\nWhen using a Curve to Mesh node, it causes other objects joined to it to be read with each face as a separate mesh island by Cycles (using the Random per Island socket of the Geometry node in shaders). This only happens while using Flat shading AND the Curve to Mesh is plugging into the first position of the Join Geometry node. In any other order it will not happen.\nAlso happens with more mesh objects as long as the Curve to Mesh object is the first on in the Join node.\n\nThe edges aren't actually split, it just seems to be Cycles that thinks they're individual mesh islands.\n\nAdd a grid node and join it to a curve going through a Curve to Mesh node.\nEnsure the Curve to Mesh is the first connection into the Join Geo node.\nAssign a material to the grid and in the shader, view the Random Per Island output of the Geometry node.\n\n[2021-11-06 18-08-29.mp4](2021-11-06_18-08-29.mp4)\n\n[Mesh Island Bug.blend](Mesh_Island_Bug.blend)", "Dependency Graph: Assert for DEG_get_evaluated_scene\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 527.56\n\nBroken: version: 4.0.0 Alpha\n\nSee attached stack trace.\n\nDebug build:\n1. Default cube.\n2. Add Geometry Nodes modifier. In node tree:\n a. Add Cube primitive node.\n b. Add Scene Time node.\n c. Putt Cube geometry to Group Output node.\n d. Set some large values in Vertices inputs of Cube node. (~0.5s to compute)\n3. Start playing of animation.\n4. Click on some place of time line\n5. Press undo/redo few times.\n\n", "crash when i try to make instances real for nodes\nhi , in attached files all info about the crash , its when i try to make instances real for nodes modifier addon scifi pro + flex\nso can i fix it ?\n\n", "Segmentation Fault Crashing Blender when Rendering\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.1\n\nDuring rendering, Blender will often crash with segmentation fault \"Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header\" message.\n\nNeed guidance to help provide a blend file to reproduce the issue.\n\nThe issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports. \n\nMy workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame.\n\nI believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model.\n\nGPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash.\n\nI have tested on 2 other Windows computers with the same results, so it is not Ubuntu related.\n\nOther frames render perfectly.\n\nThere is no issue with viewport render mode. Often I get \"out of memory\", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around.\n\nI have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file.\n\nN.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well.\n\nIs there any advice I can get as to how to narrow down this problem?\n\n", "GPU subdivision improvements\nThis is a list of TODOs and ideas for improving GPU subdivision support ([D12406](D12406)).\n\n**TODOs**\n\n- Investigate if read and write operations can be made more coherent.\n- Investigate if compute dispatch size can be improved, to avoid too many calls.\n- Remove some useless OpenGL initialization from OpenSubDiv\n - We use our own patch evaluation shader, however we are still forced to compile the one from OpenSubDiv. This will require to implement our own GLComputeEvaluator.\n - `GLVertexBuffer` also initializes the OpenGL library. We can avoid this by using our own vertex buffer wrapper.\n- Compressed data structures for reducing memory usage\n - Using compute shaders forces us to only deal with ints and floats. However, this is using more memory than necessary (e.g. for normals).\n - This requires to do manual bit packing in the shaders, we need to pay good attention to alignements and data types (int vs. uint).\n- Use multithreading for CPU tasks when applicable\n - We still process some data on the CPU (e.g. polygons to materials map, edit mode flags). Although they are based on the coarse mesh, we could use multithreading to speed things up if needed.\n\n**Ideas**\n\n- Heuristic to disable GPU subdivision for small meshes, if they are hindering performance\n- The mesh wrapper used for on the CPU might not need all of the data to be subdivided (e.g. we do not need vertex colors for snapping), we could potentially speed up CPU subdivision by only subdividing what we need.\n- Potentially evaluate points on the GPU and copy back to the CPU side, this would require threads to have their own GL context.\n- See if OpenSubDiv data structures can be shared between the CPU and GPU code (e.g. the stencils buffers) so that we do not have to create duplicate versions when the CPU side mesh is requested.\n\n**Vulkan**\n\n- OpenSubDiv does not yet officially support Vulkan. The Pixar team seem to already have something working internally (1153). It is not clear when this will be released.", "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", "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", "EXCEPTION_ACCESS_VIOLATION when baking between linked objects\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen experimenting with the idea of having linked duplicate objects and bake materials between them I found a reproducible crash.\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF63BB28F6E\nModule : C:\\Program Files\\Blender Foundation\\Blender 2.82\\blender.exe\n```\n\n- Oppen attached file\n- Try to bake the textures (blender crashes)\nSometimes it doesn't crash the first time but always atleast on the second or third attempt.\n\n[mushroom.blend](mushroom.blend)\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", "Crash when rendering animation\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.4.1\n\nBlender crash when rendering an animation\n\nIn an attempt to simplify my rendering of multiple scenes, I added an additional scene to a blend file with no objects itself. Its purpose is to be a place to put multiple *Render Layer* nodes in its compositor for all the other scenes in the file. In other words I hit \"Render\" when on that special scene and all other scenes are rendered in one go. Running this render as a single image works fine. Running render animation crashes after one frame.\n\nMy actual file has 7 scenes to be rendered. But to help demonstrate and reproduce this, I have simplified the file to just two scenes:-\n\"*Scene 1*\" is a simple scene containing a cube and a camera. Rendering this scene directly, works fine as still image or animation.\n\"*Render all*\" is a second scene that has no objects of its own (just a camera because my render farm seems to insist upon that). This scene is set to not be rendered (\"*Use for Rendering*\" unticked). However it's compositor has a *Render Layers* object which looks at *Scene 1* and which is connected to a *File output* node.\n\n\n[crash-test3.blend](crash-test3.blend)\n\nOpen file and render animation.", "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", "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", "Crash while baking the Line Art modifier\nOperating system: Windows 11\nGraphics card: RTX 2070\n\nBroken: 7c2dc5183d03\n\n\n\nI get regular crashes when baking Line Art modifier in relatively complicated geometries. \n\nI can't provide my project file. I am hoping that the crash log will give insight into this bug.\n\n", "Crashing while viewing animation in Cycles\nOperating system: macOS-13.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.4.0\n\nWill crash seconds after playing animation in viewport when Cycles is selected and in render view. Both CPU and GPU crash. Does not crash when removing the Subdivision Surface Modifier so polycount may be a factor? This is a brand new Apple M1 Max computer from BestBuy with nothing else installed. Also tried initializing a render to video file and crashed as well. (Note: This is an error strictly with Apple M1 computers as I have tested it on an Apple intel MacBook Pro and it works just fine.) Thank you and happy holidays!\n\n1. Load file. It is a mesh plane with default cloth and subdivision modifiers acting on a wind force.\n2. Make sure Cycles is selected as Render Engine.\n3. Select Viewport Shading to Rendered (to view cycles render)\n4. Push play. Will crash or freeze seconds after play.\n\n[Cloth_Cycles_Crash.blend](Cloth_Cycles_Crash.blend)\n\n[Blender 3.4 Crash Report 12.13.22.rtf](Blender_3.4_Crash_Report_12.13.22.rtf)\n[Blender 3.5 Crash Report 12.14.22.rtf](Blender_3.5_Crash_Report_12.14.22.rtf)" ]

[ "Join geometry with groups crashes (geometrynodes)\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\nCrash happens when a value is changed in a nodegroup which is connected to a join geometry node.\n\nEdit a value in a group when it is connected to a join geometry node. \n[Join Geometry Crash.blend](Join_Geometry_Crash.blend)\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", "High Resolution Render support\nSome fields needs to be able to output really high resolution renders out of EEVEE.\n\nFor now, we just try to allocate the asked buffer size and live with the consequence.\n\nMost GPU have a limit of 16K² texture resolution and some really high renders could not fit GPU memory in some cases.\n\nTo workaround this issue, we need to implement a multipass rendering.\n\nThe issue with this approach is that Screen Space effects (GTAO, SSR, SSRefract, SSSubSurfaceScattering) cannot take the whole picture into account.\n\nWe can split the rendering into tiles, scanlines, checkerboard pattern but the artifacts of SS effects will likely to be different for each", "\"No Render\" volume of space with motion blur and GPU render\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.27\n\nBroken: version: 3.4.1\nWorked: N/A\n\nThere appears to be a volume of virtual space where objects do not render.\n\nLoad attached file. Set render frame to 110 and render the scene. Note the progress it makes as the large cube slowly vanishes with each render pass, while the smaller thin cube only partially renders. Set the frame to 50 and it renders fine. The problem starts with frame 106 and gets progressively worse for the large cube, while it seems to somewhat recover for the thin cube in later frames.\n\nThe problem does not repro with CPU rendering, and did not repro with my older graphics card way back when I first made this scene (GeForce 1080Ti). It repros with GPU rendering on both 3.4.1 and 3.1.0. It does not repro with motion blur disabled (hence the viewport render is also fine).\n[GPU Motion Blur Bug.blend](GPU_Motion_Blur_Bug.blend)\n", "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", "Checking the Vector Blur pass checkbox causes the most recently emitted particles to not be rendered.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.80, 2.83.8, 2.92.0 Alpha c271600101, \nWorked: 2.79b\n[T82260_2.79_Sample.blend](T82260_2.79_Sample.blend)\n\nChecking the Vector Blur pass checkbox causes the most recently emitted particles to not be rendered. This issue is visible when using a fast moving emitter.\nRendering on the GPU or CPU doesn't seem to make a difference, the issue still occurs.\n\n - Open the attached .blend\n\n[T82260_2.92.0_Alpha_Sample.blend](T82260_2.92.0_Alpha_Sample.blend)\n - F12 to render.\n - Click on the Vector Blur pass checkbox.\n - F12 to render.\n - Compare the 2 render results.\nVector Pass unchecked\n\n\nVector Pass checked.\n\n\n[Desktop 2020.10.30 - 21.14.11.01.mp4](Desktop_2020.10.30_-_21.14.11.01.mp4)\n\n\n\n\n", "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", "Motion Blur missing in the Render Preview of viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\n\nIn 2.83 we had the access to realtime motion blur with Eevee (which was limited to camera deformation).\nIn 2.90 and above this was replaced with a new motion blur system that is render only. \nEevee is amazing for having realtime screen space reflections, ambient occlusion, depth of field and motion blur, which made it perfect for screen capture or viewport rendering an animation without excessive time consumption.\nI was wondering wether this is a decision or a bug, since having the camera deformation motion blur back in the viewport would allow for the same realtime rendering results as in 2.83\n\n- Go to camera view\n- move the camera around\nIin 2.90 and above and youll see any motion blur previously existent in 2.83 is gone. \n", "Motion blur doesn't work with curve with subdivision\nOperating system: Windows 10\nGraphics card: GTX 780\n\nBroken: blender 3.3.1\nWorked:\n\nMotion blur doesn't work with curve with subdivision\n\n- render F12 : the motion blur works with simple curve\n- subdivise curve\n- render F12 : the motion blur doesn't work anymore\n\n\n\n\n\n[motion_blur_curve.blend](motion_blur_curve.blend)\n\nThanks a lot!", "Blocky artifacts in various render passes when rendering Mantaflow volumes in Cycles\n## Simplified Report\n\n- Open the attached file and set the VDB path to the attached VDB volume.\n- The VDB volume file is the result of a Mantaflow simulation generated in Blender using Quick smoke.\n- Render the scene and look at the shadow pass.\n- The shadow pass contains blocky artifacts as shown in the attached image.\n\n[blockyVolumeShadowPass.blend](blockyVolumeShadowPass.blend)\n\n[fluid_noise_0060.vdb](fluid_noise_0060.vdb)\n\n\n\n## Original Report\n\n[system-info.txt](system-info.txt)\n\nBroken: 3.1, 3.4.0 Alpha, branch: master, commit date: 2022-09-27 23:42, hash: 5beaecb33e74\nWorked: most likely never\n\nRendering imported vdb generated with Mantaflow in Cycles gives blocky artifacts in various passes. \nMost visible artifacts are in shadow pass and denoising albedo. Less visible can be seen in volume direct and indirect.\n\nThis bug is particularly nasty as the artifacts are mostly invisible in beauty pass. \nHowever when volume have high density and is illuminated with intense light the artifacts starts to appear in combine pass.\nArtifacts in denoising albedo pass can ruin seemingly good volume render.\n\nI wasn't able to replicate the artifacts in EEVEE.\n\nHere is how the bug looks with Quick smoke on default cube (scene in attached blend file):\n\nshadow pass\n\n\ndenoise albedo pass\n\n\nAnd here is an example how this bug might affect production scene:\n\nshadow pass\n\n\n\ndenoise albedo pass\n\n\n\nvolume direct\n\n\n\nvolume indirect\n\n\n\nbeauty (cropped)\n\n\n\n\nReproduce render artifacts:\n- open first attached blend file\n- hit `F12`\n- observe shadow pass\n- change `Render Layer` output in `Compositor` if needed\n\nRecreate vdb (optional):\n- open second attached blend file\n- (optional) in `Properties` -> `Physics Properties` -> `Fluid` -> `Cache` set path for cache\n- in the same panel hit `Bake All` and wait until bake is completed\n- navigate to cache directory and open `noise` folder, pick one file (better to pick one from the end where the smoke have more complicated shape)\n- import vdb to the first file and place it so the camera can see it\n\n[volume_bug_render.blend](volume_bug_render.blend)\n[volume_bug_sim.blend](volume_bug_sim.blend)", "Render issues when two VBD overlap if rendered with motion blur\nBroken: 3.2, 3.6\nWorked: 3.1\n\nRender issues when two VBD overlap if rendered with motion blur\n\nRender the attached file with and without motion blur. If you render them separatly they both render OK. Only when together it doesn't work.\n\n", "Rigidbody doesn't work when you change motion blur steps in eevee\nOperating system:debian buster\nGraphics card:nvidia gtx 1070\n\nBroken: (example: 2.90, 0330d1df29c0, master, 2020-08-31, as found on the splash screen)\nWorked: Never\n\nRendering unbaked rigidbody simulation in eevee with motion blur with 2 or more steps will cause simulation to stop working.\n\n[#80388.blend](T80388.blend)\n- Open file\n- Check if rigidbody simulation works\n- Render image\n- Check if rigidbody simulation works\nIt doesn't work anymore.", "Glare Node set to \"Fog Glow\" in Real-Time Compositor vastly different from actual render results\nOperating system: Windows 10\nGraphics card: RTX3070 FE\n\nBroken: 3.6 A\nWorked: N/A\n\nWhen using the Glare Node in Real-Time compositor, the results in the viewport are turned up way higher than the actual render and Backdrop preview.\n\n\n\n1. Open attached .blend file\n2. Set to Rendered view, enable Real Time Compositor\n3. Compare the Glare effect in an F12 render to the effect previewed in the viewport\n\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", "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)", "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" ]

[ "Motion blur all out of whack \nOperating system:\nDistributor ID:\tUbuntu\nDescription:\tUbuntu 21.10\nRelease:\t21.10\nCodename:\timpish\n\nGraphics card:\n04:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1)\n\nBroken: version: 3.1.0 Alpha, branch: master, commit date: 2022-03-09, hash: `c77597cd0e`\nWorked: I have not tested this scene in any other blender version. \n\nSimple ball animated with (also broken) physics that produce unexpected motion blur.\n\n\n\n- Open attached file\n- Press F12 to render\n(I guess any HDRI works as light source) .\n\n[broken_physics_3.1.blend](broken_physics_3.1.blend)", "Regression: Motion blur resulting from rigid body simulation vectors is amplified / wrong / too strong\nOperating system: Windows 10\nGraphics card: RTX 3060 TI\n\nBroken: 3.1.0 beta to 3.2.0 alpha\nWorked: 3.0.0\n\nCaused by e1ae95f6b2.\n\nMotion blur resulting from rigid body simulation vectors is rendered wrong / too strong since Blender 3.1.0 alpha (at least) and up to latest Blender 3.2.0 alpha+master.28656293c624-windows.amd64-release, while motion blur resulting from manually keyframed vectors behaves as expected. Rendering via CPU, CUDA or Optix makes no difference. \n\n Motion blur rigid body simulation Blender 3.0.0 (expected output)\n\n Motion blur rigid body simulation Blender 3.2.0 (questionable output)\n\n Motion blur manual keyframed Blender 3.0.0 (expected output)\n\n Motion blur manual keyframed Blender 3.2.0 (expected output)\n\nSteps to reproduce:\nOpen mblur_rigid.blend in either Blender version and hit F12. Compare renders.\n[mblur_rigid.blend](mblur_rigid.blend)\n\nFor comparison purposes, I attach a manually keyed file, where the render output is constant across all tested versions.\n[mblur.blend](mblur.blend)" ]

[ "stack_overflow exception while rendering with viewport render on\nOperating system: win10\nGraphics card: 2070super\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: 2.83.4, 2.91 6fe609d4c3\n\n\nwhen pressing f12 in render mode, blender crashes,\nwhen pressing render in solid mode, blender doesnt crash\n\n[blender_debug_output.txt](blender_debug_output.txt)\n```\nError : EXCEPTION_STACK_OVERFLOW\nAddress : 0x00007FFF42963FDB\nModule : C:\\Windows\\system32\\DriverStore\\FileRepository\\nv_dispsi.inf_amd64_6af46268c19e4980\\nvcuda64.dll\n```\n[2.blend](2.blend) \n1. switch to render mode\n2. press f12 & watch task manager.\n3. blender will close", "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", "Cycles: Baking to an externally loaded image fails to update the image buffer results in Cycle's Rendered Viewport Shading\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 512.59\n\nBroken: version: 3.3.0, 2.93\nWorked: probably never\n\nBaking to an externally loaded image will not changed the baked image as displayed in the Viewport Shading's Rendered Mode.\nThe newly baked image buffer is shown correctly in the image editor and (EEVEE's) Material Preview, but wrong in Cycles's render view.\n\n- Open the attached .blend file.\n- Open the attached baked image in the image texture node.\n- Use it to bake any type of pass to the loaded image.\n- Observe that the image looks unchanged in the Rendered View by connecting the image texture node to the material output.\n[#98063.blend](T98063.blend)\n\n[2022-05-12 09-12-20.mp4](2022-05-12_09-12-20.mp4)", "Blender Crash MacOS Arm M1 - Wireframe - Memory issue\nOperating system: macOS-12.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Pro Apple 4.1 Metal - 76.3\n\nBroken: version: 3.2.0 Alpha\nBroken: version: 3.1.2\nWorked: Any version using linux/windows\nWorked: version: 3.1.2 on Intel base Mac\n\nBlender crashes with a viewport in wireframe mode or tries to allocate ~100 GB memory when .\n\nBase: default blend file.\n\n1. Go to \"Geometry Node\" tab\n2. Create new node setup\n3. Add Mesh line node\n4. Set count to something big like 256^3 (this was my test case)\n5. Switch the viewport to wireframe\n6. Crash\n\nNote: Slower increase can lead to huge memory consumption by blender:\n\n\nExample node setup:\n\n\nSwitch to wireframe:\n\n\n", "Render crashes – metal related\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.2\n\nI get some of these intermittently: `Context leak detected, msgtracer returned -1`\nrender ultimately fails (always at around frame 400) with this:\n\n```\nCommandBuffer Failed: cycles_metal_integrator_reset\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nCommandBuffer Failed: cycles_metal_integrator_init_from_camera\n``` \n\n- download and extract the files attached to this issue\n- run `render.sh` + wait until blender crashes\n\n~~using the opengl backend, it works just fine~~\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", "Texture paint in viewport is not using the color space of the image.\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\nIf you paint a noncolor texture like a normal map, painting it directly in the 2D image correcly uses the non-color space, but painting in the viewport doesn't.\n\n\n- With any non-color texture, try to paint both in viewport and in the 2D image\n[2022-02-15 10-34-07.mp4](2022-02-15_10-34-07.mp4)\n\nAditional note: This seems to happens when you sample from the 2D image. By contrast, if you sample the color from the 3D view, you can correctly paint on it, BUT in the 2D viewer the color becomes brighter.", "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", "Laucnh error since version 3.4\nOperating system: High Sierra 10.13.6\nGraphics card: ATI 6970M 2 GB RAM\n\nBroken: (example: 3.4 and 3.4.1 2022-12-20, master)\nWorked: (Blender 3.3.1)\n\nWhen I launch blender a get this error that I have found others on the web reporting also on similar setups:\nError opening window.\nFailed to create metal device for offscreen GHOST Context.\n \n\nPrevious versions worked a charm and I really hope 3.3.1 wont be the last version for my humble setup.\n\nThanks and as always appreciate your amazing work!", "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", "Blender 3.5 and 3.5.1 are crashing while using Metal as backend\nOperating system: macOS 12.6.3\nGraphics card: Radeon Pro 580 8GB\n\nBroken: 3.50, 3.51 (Metall Backend)\nWorked: 3.50, 3.51 (OpenGL Backend)\n\nBlender simply hang. I use eevee, if you switch to rendered viewport shading it crashed complete system. I use Metall as backend, if I choose OpenGL it works fine. \n\n \nI attached an .blend file for example.\n\n", "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", "Cycles GPU rendering is broken on Apple M1/macOS Ventura\nOperating system: macOS-13.0-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.3.0 Release Candidate\nWorked: 3.2.2\n\nCycles GPU rendering is broken, CPU rendering works as expected.\n\nCycles - CPU:\n\n\nCycles - GPU Compute:\n\n\n1. Create any scene\n2. Switch Cycles to GPU Compute\n[simple_test.blend](simple_test.blend)\n", "Viewport animation renders take progressively longer if there is a split in the scene!\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Ultra 1.2\n\nBroken: version: 3.6.2\nWorked: Never\n\nWhen animating a render from the viewport, if a spline is present in the scene each frame takes progressively longer and longer to render until it takes a painfully long time per frame. Once the spline is deleted from the scene, each frame takes the same amount of time to render!\n\nMake an animation of approx 1000 frames\nInclude a spline in the scene - you don't have to render it, it just needs to be in the scene!\nViewport Render Animation\nYou should quickly notice that each frame is taking longer and longer to render\nBy the time you get to frame 800 (if you care to wait that long) you will be pulling your hair out!\n...now delete the spline\nViewport Render Animation\nEach Frame now takes the same time to render and you can smile once more.\n\n....I'm already guessing that whoever is gracious enough to try this will magically not have the problem - if so, please reply and I will supply files... I just would rather not at this time as I am interested to see if it is indeed reproducible? I can confidently say that I have experienced this issue for at least 5 years, but it's only now that it has come to bite me again and I have finally proven (to myself, at least) that the issue is spline related - my scene had one single 'Annotation' spline that I wasn't even aware of hanging around in it and deleting it sped up render times by an order of magnitude!\n\nThanks\nWayne\n\n", "Render crash\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon RX 560X ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.1.220810\n+ AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx\n\nBroken: version: 3.3.0 Beta\nWorked: 3.2.2\n\nBlender every time crash when switch to render mode in viewport.\nRender set to Cycles with GPU Compute.\nVega 8 selected as device in preferences.\nIf I select RX 560X in preferences, GPU Compute is greyed in Render preferences (also interesting why).\n\nAny project with simple cube crashed.[test11.crash.txt](test11.crash.txt)\n" ]

[ "Viewport rendering whilst previewing rendered does not show any result.\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:\t\t\t`blender-2.79b-f4dc9f9d68b-windows64` (official release)\nBroken:\t\t\t`blender-2.80-f6cb5f54494e-windows64` (official release)\nBroken:\t\t\t`blender-2.81-26bd5ebd42-windows64` (official release)\nBroken:\t\t\t`blender-2.82-fa5e28ab08c7-windows64` (build bot)\n\n\n - Open bmw27_cpu.blend\n\n - Remove overlays\n\n - Switch to rendered viewport shading\n\n - Viewport Render Image\n\n| 2.79 | 2.8x |\n| -- | -- |\n|  |  |", "Cycles Viewport Render Image shows a gray picture\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nRendering straight from the viewport with Cycles will result in a gray picture with object outlines and other overlay elements but not the picture proper. (2.80 and upwards, I tested with 3 different versions, one of which was the official 2.80, one beta of 2.81 and a 2.82 alpha.)\n\n\nDefault scene.\nSet viewport shading to Cycles\nPress F12. You will see a predictable result. Like this:\n\nThen instead render the scene by using the \"Viewport Render Image\" option.\n \nThe result will be just a grayish image.\n\n\nI wanted to render a viewport render because of the new option where you can set the Cycles to render the LookDev HDR backgrounds instead of the actual world background. Then these bugs were found :(\n\n" ]

[ "alpha does not contribute to adaptive sampling noise treshold\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\nWorked: i dont think it ever worked\n\nwhen rendering with adaptive sampling enabled, the noise treshold does not seem to be affected by a noisy alpha channel.\n\nthis is most visible on shadow catchers: since their rgb is always black, they are always rendered with \"Min Samples\", as soon as adaptive sampling is enabled.\neven though the alpha channel is still very noisy, it stops rendering additional samples.\n\n[shadowCatcherNoise.blend](shadowCatcherNoise.blend)\n- open file\n- render samples at 64-512 samples\n- when adaptive sampling is enabled, the shadow will remain very noisy. when adaptive sampling is disabled, the shadow will be smooth\n\n", "Cycles: Motion blur artifacts\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.88\n\nBroken: version: 3.2.2\n\n\n**description of error**\nWhen rendering an animated rigged model on cycle **with motion blur** ; if the model has **auto smooth enable AND a subdivision modifier**, then it is possible that strange artefact will appear during the render. (doesn't happen in the viewport) \n- This bug do not happen if auto smooth is disable or doesn't have a subdivision modifier. \n- The bug also only appear during some specfic poses. So this is mainly noticiable when rendering an animation.\n- Those artefact often appear near sharp edge.\n- Only happen on Cycle, Eevee render seem fine.\n- [Edit] changing the shutter values of the blur will sometime remove the bug on some frames OR make the bug appear on frame that was fine before.\n\nHere 2 Render exemple with and without autosmooth , both has motion blur enabled :\n \nAnd here an animation where you can notice the bug.\n[Animated0035-0318.mp4](Animated0035-0318.mp4)\n\n\n[MotionBlurCycleArtefact.blend](MotionBlurCycleArtefact.blend)\nIn this blender file, rendering the frame 302 will make the bug happen. \n- If you disable auto smooth on the model (the main body and not the cloth) then the render will be fine.\n- If you disable the subdivision modifier on the model then the render will be fine.\n- If you disable the subdivision modifier AND the auto smooth on the model then the render will be fine.\n\nThank\n", "Artifacts when composing render passes with SSS, EEVEE and SSR\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0 Beta\nWorked: I'm not sure this behavior is new. Blender 3.2 displays the same behavior.\n\nWhen compositing render passes that have been generated using EEVEE, and an object has Subsurface Scattering enabled, and Screen Space Reflections are enabled, and Half Res Trace is disabled, artifacts are generated. The combined pass, however, correctly renders.\n\n\n*What I get (demo file included below)*\n\n\n*What I should get*\n\nNote: if Half Res Trace is enabled, the problem disappears.\nAlso, if Cycles is used to render the same scene, the passes do not display these artifacts.\n\n\n\n\n- Create a file that uses EEVEE as renderer.\n- Enable Screen Space Reflections. Disable Half Res Trace.\n- Create an object with Subsurface Scattering\n- Enable the following necessary render passes: Diffuse Light, Diffuse Color, Specular Light, Specular Color\n# In compositing, mix as follows the passes: multiply Diffuse Light and Diffuse Color; multiply Specular Light and Specular Color; add them.\n\nChanging the roughness can make the effect more extreme. Having a very contrasty roughness map exacerbates the problem:\n\n\n*a contrasty roughness map*\n\n\n*the render showing the problem more extremely*\n\n\n*how it should be*\n\nThe final result should be akin to the one posted above. You can compare the composited result with the one that is already combined: the combined one does not display the issue. Using Cycles for the same setup also works without problems.\n\nThe inconsistency of results mentioned above makes me believe this is a bug, and hence my report.\n\nDemo file: [sstest.blend](sstest.blend)", "Viewport \"Focal Length\" doesn't match Camera's focal length\nI've noticed that camera's focal length and viewport's focal lengths don't match. I agree with the Alessandro Padovani (padone) who created the parent task.\n\nBasically, when you have a scene and want to do a quick test render of what you see in the viewport you need to set the camera's position/rotation to viewport's view. To do that you first view the scene using the viewport then set the camera's position/rotation using Ctrl+Alt+0 (numpad) and hit F12. The problem with this is viewport's focal length and camera's focal length don't match even though they are both set to 50mm. \nWhen you hit Ctrl+Alt+0, camera's position/rotation is set but what camera sees is actually zoomed in which seems like 100mm. So, if you want the camera to see what the viewport sees then you need to change viewport focal length to twice of what camera is.\n\nI don't know what the parent task was closed.\n\nI'm using Blender 2.90 \nBuild date: 2020-06-23\n\n", "Incorrect Areas affected by Timeline Playback settings\nVersion: 2.80 rc2 (Linux 64)\n\n[Timeline_bug.blend](Timeline_bug.blend)\n\nTo reproduce:\n\n - Open the example file (enable \"Load UI\" too)\n - With the mouse cursor in the 3d view, play the animation using Shift + Space (or Alt + A, whatever your keymap is)\n - Ignore the 3d view. Notice which animation editors show a moving playhead.\n - Inspect the playback settings in the timeline editor.\n - Disable \"All 3d Viewports\" and repeat step 2.\n - Now Enable \"Active Editor Only\" and repeat step 2.\n\nWith certain settings, the Dope Sheet and Timeline show playback even when the Graph Editor and NLA do not. It's as if these windows think they are 3d viewports!", "Python/BMesh: Add/removing textures between renders causes memory leak/ram crash\nOperating system and graphics card\nUbuntu 18.04, Nvidia GTX 960M\n\nBroken: blender-2.80-17bc0567268-linux-glibc219-x86_64\n\n**Working Blender Version**\nBlender 2.79b stable (ubuntu repository) with cycles\n\nIf you run the attached code and target it a directory with a large number of images, it will repeatedly:\n\n1. Load an image from file\n2. Set the image to be the content of a \"Image Texture\" node\n3. Delete/remove the image that use to be the image texture node\n4. Render \n\nAs it processes images, blender takes more and more memory. Eventually it will crash. If you leave out step 4, then it will not.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n\nImport python code, run \n\nLoadAndRemoveTextures(\"/folderWithManyImages\", 2000)\n\nin the console window.\n\n[imageMemoryProblem-WorksWithStableCycles.blend](imageMemoryProblem-WorksWithStableCycles.blend)\n[imageMemoryProblem2pt80.blend](imageMemoryProblem2pt80.blend)\n\nCode:\n\n\n```\nimport datetime\nimport sys\n\nimport bpy\nimport bmesh\nfrom mathutils import Vector\nfrom mathutils import Euler\nfrom bpy_extras.object_utils import world_to_camera_view\nimport random\nimport math\nimport json\n\nimport time\nimport os\nimport gc\n\ndef RemoveImageFromMemory (passedName):\n # Extra test because this can crash Blender.\n img = bpy.data.images[passedName]\n try:\n img.user_clear()\n can_continue = True\n except:\n can_continue = False\n \n if can_continue == True:\n try:\n bpy.data.images.remove(img, True)\n result = True\n except:\n result = False\n else:\n result = False\n return result\n\ndef CollectBackgroundImagePaths(sourceDirectoryPath, imageExtension):\n file_paths = []\n\n for root, dirs, files in os.walk(sourceDirectoryPath):\n for file_name in files:\n if file_name.endswith(imageExtension):\n file_paths.append(root + \"/\" + file_name)\n return file_paths\n\ndef SetBackgroundImage(backgroundImagePath):\n #Store reference to old image so it can be removed\n old_image_name = bpy.data.materials[0].node_tree.nodes.get(\"Image Texture\").image.name\n\n #Load new image to be used\n new_image = bpy.data.images.load(filepath = backgroundImagePath)\n\n #Set the new image to be used\n bpy.data.materials[0].node_tree.nodes.get(\"Image Texture\").image = new_image\n\n #Delete the old one from the file\n remove_succeeded = RemoveImageFromMemory(old_image_name)\n gc.collect()\n\n if not remove_succeeded:\n print(\"Error removing \" + old_image_name)\n else:\n print(\"Removing \" + old_image_name + \" worked\")\n\ndef LoadAndRemoveTextures(texturesFolderPath, numberToLoad):\n background_image_paths = CollectBackgroundImagePaths(texturesFolderPath, \".png\")\n\n for example_index in range(0, numberToLoad):\n SetBackgroundImage(random.choice(background_image_paths))\n\n #If you alternate adding/removing images and rendering, it will eat all the ram on your system and crash\n bpy.ops.render.render( write_still=True )\n```", "Render error not shown in VSE\nOperating system: Windows 10\n\nBroken: 2.90 8956e9e5f6c0\nWorked: Unknown\n\n**Reproduction**\n1. In a scene's Compositing workspace, enable Use Nodes and delete all the nodes.\n2. In another scene's VSE, add the above scene as a strip.\n3. Render\n\n**Description**\n\nF12 on the outputless scene throws an error.\n\nThe VSE shows the checkerboard pattern even if there's another strip (e.g. solid black) below the outputless scene strip and does not throw any error. The outputless scene strip should either not interfere with the layers below it or show an error indicating it doesn't have an output.", "Audio Scrubbing bug\nOperating system: Windows 10 64-bit\nGraphics card: RTX 2070 Super\n\nBroken: (2.90, 2.91, 2.92 Alpha, 3.0)\n\nEnabling \"Audio Scrubbing\" with \"AV-sync, Frame Dropping, and No Sync\" causes an issue with animations in the 3D Viewport and Timeline \n(AV-sync issue)\n1. Open a default Blender file.\n2. Create basic animation with any mesh, just something to show keyframe movement. Frames 1 - 250 should be enough for this procedure.\n3. In the timeline window, click \"Playback\" and switch \"Audio\" to \"AV-sync\" and enable \"Scrubbing\". A sound file is **not** needed for this step.\n4. Hit spacebar. The timeline cursor and animation should move as intended.\n5. Hit spacebar again to stop the timeline cursor and animation.\n6. Now the tricky part! Move the timeline cursor in any direction on the timeline, then **instantly** hit spacebar again. It may take a few tries but when it does work, the animation and the timeline cursor will not move. Yet, the \"FPS counter\" in the top left corner and the \"Anim Player\" icon will stay visible as if the animation is playing.\n7. Press spacebar to stop the \"ghost\" animation.\n\n(Frame Dropping and No Sync issue)\n1. Using the same file from above, add a sound clip in the \"Video Sequence\" editor.\n2. In the timeline window, click \"Playback\" and switch \"Audio\" to either \"Frame Dropping\" or \"No Sync\" and enable \"Scrubbing\". A sound file **is** needed for this step.\n3. Hit spacebar. The timeline cursor, animation, and sound should play as intended.\n4. Hit spacebar again to stop the timeline cursor and animation.\n5. Same as before, move the timeline cursor in any direction on the timeline, then **instantly** hit spacebar again. It may take a few tries but when it does work, the animation and timeline cursor will move but the sound will not play.\n6. Hit spacebar to stop the animation.\n\nWith both examples above, issues only popped up when \"Scrubbing\" was enabled. Disabling it did not produce the same results.\n\n\n", "Dither affects 'File Output' image even when \"save as render\" is disabled \nThe dither option in the Post Processing tab affects images saved through the file output node in the compositioner even when \"save as render\" is disabled, when disabled it should not touch the output image, when \"save as render\" is enabled it makes sense to dither.\n\n\nnoise in output file\n\n\n- Open attached file\n- Optionally change the Dither in {nav Output Properties > Post Processing}\n- hit render\nIt will generate an image in the directory pointed to by the node `File Output`.\nNote that Dither also affects this image.\nMaybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data.\n\n[gradient.blend](gradient.blend)", "Asset spawns at Camera origin when in camera view\nOperating system: Microsoft Windows 10 Home\nGraphics card: GeForce RTX 2060\n\nBroken: (3.0.0, f1cca3055776, master, 2021-12-02 18:35 )\nWorked: N/A\n\n----------------------------------------------------\n\nCreate and mark asset. \nAdd camera move camera along Y axis away from world center. \nOpen asset browser and find your marked asset. \nGo into camera view, drag asset to viewport. \nAsset will lock to camera origin. \n\n--------------------------------------------------\n\nGo to front view, drag asset in, works as expected.\n\n----------------------------------------------------\n\n2D artist will want to work from the camera view for standardize production. In this example I used a grease pencil object but it can be replicated with 3D objects also. Thanks for looking at this. \n\n[2022-01-17 11-40-38.mp4](2022-01-17_11-40-38.mp4)\n", "Grease Pencil Outline Modifier not showing with duplicated camera in outliner\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 522.33\n\nBroken: version: 3.4.0 Alpha\n\nThe outline modifier of a grease pencil is not showing with a camera that gots duplicated in the outliner\n\n\n- Remove the default cube\n- In the outliner copy and paste the default camera\n- Remove the first camera\n- Add a grease pencil stroke\n- Add a Outline modifier to it\n\nThe outline will not show.\n\nThis bug is related to this report. I am just not sure if it is two different causes and cases, or the same. T102373\n\n\n\n[2022-11-09 10-30-57.mp4](2022-11-09_10-30-57.mp4)\n\n\n\n", "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", "Object cryptomatte is not respecting the camera Dof\nOperating system: Windows 11\n \n\nBroken: 3.0, 3.6\nWorked: never?\n\n\n\nCycles object cryptomatte is not respecting the camera depth of field while the material one respects it properly. See the image for comparison\n\n\n\n\nload the attached .blend (it already has the object and the material cryptomattes enabled)\n\nrender\n\ncompare the current cryptomatte types in the compositor\n\n", "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)", "Switching a speakers sound data-blocks fails\nSwitching the sound data-block of a speaker doesn't update audio playback.\n\nRedo with this file:\n\n[sound_switch_bug.blend](sound_switch_bug.blend)\n\n- Spacebar to play animation (white noise will play).\n- In the \"Sound\" panel, switch the sound datablock from \"W\" to \"B\".\n- Notice nothing plays (pause / play, it still doesn't work).\n\nTo hear playback from the updated data-block you can:\n\n- Open and close the preference window (on closing, the new sound will begin to play). This also works with any file-selector window (not windows created from \"New Window\" / \"New Main Window\" though).\n- Save and reload the file. Play animation. \n\nTested with 3.0 and `1705587e21bc62f67a0aa297769853e1903d2a44`." ]

[ "Sequencer Scene Strips' Input(3D/Sequencer) and volume and has no effect on audio.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 24.20.100.6137\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nThe volume floatproperty of Scene strips(in the Sidebar) has no effect and selecting Input: 3D or Sequencer has no effect on what sound are heard. Both will always be heard. \n\n\n- Add a speaker to the 3d view.\n- Add a sound file to the speaker from first frame.\n- In the sequencer add a sound file from first frame.\n- Boths sound should be heard when playing.\n\n- Add a new(!) scene.\n- In the sequencer add a scene strip.\n- In the Sidebar in the Scene strip sub panel changing the input will not change what sound is heard.\n- In the Sidebar in the Scene strip sub panel changing the volume will not have any effect.\n\nA blend file, where the above has been done - so to experience the bug change input and change volume:\n[Scene_Strip_Volume_No_Effect.blend](Scene_Strip_Volume_No_Effect.blend)\n\nAnd two audio files if the packing didn't work\n[433725__disagree__running-on-ground.flac](433725__disagree__running-on-ground.flac)\n[204341__bunting__birds-in-aviary.wav](204341__bunting__birds-in-aviary.wav) \n \n\n", "VSE Linked external scene with audio with input Sequencer only works if the scene is NOT also linked with input Camera\nOperating system: Linux-4.9.0-9-amd64-x86_64-with-debian-9.9 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 13.0.6\n\nBroken: version: 2.81 (sub 3)\nWorked: Haven't yet tried other versions.\n\nVSE: Linking external scene with audio with input Sequencer only works if the scene is NOT also linked with input Camera.\n\n1. Create file A with Scene-A and add audio to it on the VSE.\n2. Create file B\n3. From the VSE in file B, link the Scene-A from file A. Set it's input to \"Sequencer\". On file B, playing the strip will correctly play the sound from Scene-A.\n3. Duplicate (or re-instance) Scene-A on the VSE sequencer. If the Input is still \"Sequencer\", both clips will play the audio, as expected.\n4. Switch one of the Scene-A instances to use the Camera as input. \n\nExpected behaviour: \n\nWe should be able to both see the Camera strip and hear the Sequence strip for Scene-A\n\nActual behaviour:\n\nFor all the strips of Scene-A that are set to Input \"Sequencer\", the audio will stop playing.\n\nNote: I've determined that it is not that the audio crashes: other clips with sound on the sequencer keep playing normally.\n\nNote: If I delete the strip with Input Camera and leave only the input Sequencer strips, the problem will not go away, unless I save the file like this and \"revert\" to it.\n\nI cannot find a suitable work-around. In the video that I'm producing I need to edit local sound effects on the shot sequence, and incorporate it on the larger edit.\nI cannot, therefore, both see and hear my sequence on the host sequencer.\n\n\nIf a workaround is possible (that is not reconstruct and re-import the sounds on the original scene) I'd be a happy man :-)\nThanks!\n\n\n" ]

[ "UI of Dropdown Menus : long list of EnumProperty Items (ColorSpace, Language, RemapUser ID) is partially hidden\nHi all !\nHere is a UI glitch in Dropdown Menus happening with long list of items.\n\nOriginally, this report was about the Language select list in the Preferences window but it actually occurs with every long Dropdown Menu lists.\nThis problem appears every time the Dropdown Menu is bigger than the window it is displayed inside.\n\n\nOperating system: Linux-5.3.0-2-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.4\nDisplay resolution : Full HD 1920x1080px\n\nBroken: version: 2.82 (sub 3)\n\nOpening the Preferences window (or any small sized Blender window) with Factory Settings defaults and changing the translation language (or choosing any other option in a long Dropdown Menu) displays a \"bigger than expected\" dialog that is partially hidden by the side of the window in a 1920x1080 pixels screen. The user has then to resize the Preferences window to fit, not a big problem per se but would be better if defaults were better.\nThat is because the list of supported languages is becoming quite big, specially the \"starting\" ones.\nBlender already has a few big list dialogs (e.g. the Editor Type or the Add Modifier) but those are generally dispayed correctly within the Blender window (almost full-screen).\nThat is not the case of the Preferences window.\n\nThree possibilities to solve this:\n- reordering the list so it stays into the Preferences window (e.g. \"In Progress\" below \"Complete\")\n- allowing the list to go beyond the borders of the Preferences window (do not know if technically feasible)\n- resize a bit the whole Preferences window to fit\n- redesign how Dropdown Menus behave, allowing for easy scrolling and search\n \n see illustrations below\n Thanks a lot ! =D\n\n\n\n\n\n", "Mem leak when rendering on GPU\nOperating system: Windows 10 20H2 Build 19042.985\nGraphics card: Gigabyte RTX 30870\n\nBroken: 2.92 - 3.0\n\n\nRender 2.92 splash screen on GPU 60337d495677e942564cce76\n\nOn CPU, memory usage was 18GB, on GPU it went to 60GB and I had to terminate the process.", "Cloth simulation randomly breaks down when scrubbing timeline\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2.1\n\nWhen scrubbing the timeline , the cloth simulation may cause the mesh to become distorted even with the existence of cache. The video below will show a quick way to break the simulation, however, I first stumbled upon the problem when I set the keys for the bones.\n\n[2022-07-22 15-48-43.mp4](2022-07-22_15-48-43.mp4)\n\n1. Create cloth simulation.\n2. Scrub the timeline. After some time, a situation will arise where the mesh will be distorted.", "Rewrite file-list code for asset system (and File Browser)\nFor details see #88184 (Asset System: Data Storage, Reading & UI Access).\n\nThis is in progress in the `asset-system-filelist` branch.", "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*", "Grease Pencil: Eraser Brush ends on maximum radius\nOperating system: Linux-5.4.0-89-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.1.0 Alpha\nWorked: never\n\nWhen using the eraser brush in draw mode of grease pencil objects you can notice that when you stop your stroke, the brush radius will end on the maximum radius.\nThis has the effect of users erasing something carefully when using pressure sensitivity for the radius, but then erasing everything within the max radius anyway once they end the stroke.\n\nThis effect is most noticeable if you use the \"Eraser Point\" brush in the eraser tool with \"Use Pressure\" enabled.\n\n", "Python: Large memory leak if an operator modifies certain properties during the \"load_post\" handler\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.3.3\nBroken: version: 3.4.x through 3.6 as well\nWorked: n/a\n\nThere's a large memory leak if an Operator modifies certain properties during the `load_post` handler\n\n\n- Install the provided `leak.py` addon\n- Enable it and save preferences\n- Quit Blender\n- From the command line execute `blender --debug-memory`\n- Once loaded, quit blender again\n- Notice the large amount of leaks\n\n`Error: Not freed memory blocks: 543, total unfreed memory 0.040207 MB`\n\nThe property being modified -- see the 2 \"NOTE\" comments in provided addon for clues:\n```python\n def execute(self, context):\n \n # NOTE: This statement causes a large leak\n context.space_data.show_region_tool_header = False\n```\n\nThe leaks looks like:\n```\nError: Not freed memory blocks: 552, total unfreed memory 0.040894 MB\nWM_event_add_keymap_handler len: 80 000002128B026558\nWM_event_add_dropbox_handler len: 40 00000212EF01CE58\nWM_event_add_ui_handler len: 80 000002128B0264B8\nWM_event_add_keymap_handler len: 80 000002128B026418\nWM_event_add_keymap_handler len: 80 000002128B026378\nWM_event_add_keymap_handler len: 80 000002128B0262D8\nWM_event_add_keymap_handler len: 80 000002128B026238\nWM_gizmomap_add_handlers len: 40 00000212EF01CDE8\nWM_event_add_keymap_handler_dynamic len: 80 000002128B025AB8\n...\n...\n```\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", "Improve auto offset when inserting new node\nIn the example below the Noise Texture node should be moved automatically as well, not just the Set Position node.\n\n[screen_recording-2021-12-13_17.34.37.mp4](screen_recording-2021-12-13_17.34.37.mp4)\n\nThe exact behavior in more complex trees still has to be designed.", "Mouse leaves window during walk navigation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.3.0\n\nmouse goes out in walking navigation\n\n\n- Simply open any file\n- Activate walking navigation and turn the mouse from top left to bottom right quickly several times (between 3 and 5 times)\n\n", "Can't stop audio playback when using multiple windows\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.29\n\nBroken: version: 3.3.1\n\nAfter creating New Main Window, the Video Editing cannot be played normally\n\n1、Create a new scene \"Scene001\" in the Video Editing interface Sequencer window of “scene” \n2、Create a New Main Window to open another scene\"scene001\" and enter 2D Anmation,and draw\n3、At this time, the picture of the \"scene\" cannot be played normally, but the sound will continue\n\n[ceshi.blend](ceshi.blend)\n", "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).", "Using a File Picker element in a popup window causes the popup to go away\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 471.96\n\nBroken: version: 2.93.4\nWorked: Not sure if it has, at least not for a while.\n\nIf I put a string property with a subtype of \"DIR_PATH\" or \"FILE_PATH\" to have the folder/file picker show up for a user to easily select a folder/file in an operator's props and then call it with a window manager invoke_props_dialog (or any of the other popup panel ops), after the user has selected a folder/file the file window goes away but so does the panel without executing the operator.\n\n1. Open included blend file\n2. Run 'Popup File Picker Test' script in text editor\n3. In the Object section of the Properties area, under \"Popup File Picker Test Panel\" click 'Test Popup'\n4. In the popup window use the folder picker button to select a folder and hit \"Accept\"\n5. If it worked, the popup should still be there for you to continue to change other props. If it ran execute instead there should be a statement in the info area and in the console window saying \"Ran execute\". Otherwise it most likely made the popup to disappear without running the operator\n\n[popup_file_pick_test.blend](popup_file_pick_test.blend)\n\n", "Design issue: Icon next to overridden property does not perform the function it strongly suggests\n3.0.0\n\nWhen a propertry is overridden, the \"animate property\" button next to it is replaced by this \"reset\" icon:\n\nThese really seem to suggest that clicking them will remove the override. Instead it just adds a keyframe as usual. This seems misleading.\n\n - Override a property of some library override asset\n - Click the button to the right of that property\n\n", "Misuse of 'U.pixelsize' in code\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: -\n\n\nThe `U.pixelsize` is the user preference for line width in the UI. Go to \"Preference\" > \"Interfece\" > \"Line Width\".\nChanging the \"Line Width\" has an undesirable effect in some cases.\n\n- [ ] Zooming value with MMB-drag in Clip and Image editors\n- [ ] Dynamic-topology Detail Size\n- [ ] Width of tooltips block\n\nThere's an old list of places that need to be re-checked:\nD9604\n\n" ]

[ "New autoscrolling after renaming in the File Browser works weird\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.33.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.31\n\nBroken: version: 3.0.0 Alpha\nWas introduced in 6b0869039a like this\n\nNew autoscrolling after renamin in the File Browser works weird (does not scroll to the item created/renamed)\n\nin the FileBrowser:\n- go to a directory with many files/folders\n- create a new folder or rename an existing folder\n- watch it scroll somewhere else\n\n[filebrowser_autoscroll_somewhere_else.webm](filebrowser_autoscroll_somewhere_else.webm)\n" ]

[ "Texture paint in viewport is not using the color space of the image.\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\nIf you paint a noncolor texture like a normal map, painting it directly in the 2D image correcly uses the non-color space, but painting in the viewport doesn't.\n\n\n- With any non-color texture, try to paint both in viewport and in the 2D image\n[2022-02-15 10-34-07.mp4](2022-02-15_10-34-07.mp4)\n\nAditional note: This seems to happens when you sample from the 2D image. By contrast, if you sample the color from the 3D view, you can correctly paint on it, BUT in the 2D viewer the color becomes brighter.", "Most sculpt tools do not work while model is animated\nLinux 64-bit\n2.93.2\nMost sculpt tools do not work as expected when the object is spinning like it's on a pottery wheel. Some tools like the clay tool work okay, but other tools like smooth and scrape do not. I think it has to do with the stroke method; the stroke accounts for screen space but not the local transform of the object if it's moving during a stroke. Video of my attempt here:\n[pottery.mp4](pottery.mp4)\nI made this as a joke and it looks like garbage, but unfortunately it went viral and everybody thinks it's a great idea so now more people are gonna try it and complain that it doesn't work. It's a valid workflow that you have to account for now apparently. I'm really sorry.\n - Open the attached file\n - Play the animation\n # Try to sculpt the thing while it spins\n[bowl.blend](bowl.blend)\n", "Viewport redraws unnecessarily after each selection when using Eevee in look-dev or rendered modes\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 11)\nBroken: version: 2.83 (sub 10)\nWorked: n/a\n\nThe viewport will unnecessarily redraw each time a selection change occurs when using Eevee's rendered mode or look-dev mode. This does not occur with the Cycles Rendered viewport.\n\nLoad the attached .blend\n[badredraws.blend](badredraws.blend)\n\n- Contains a default cube, a ground plane, and 1 large radius light (to make it obvious that things are redrawing)\n- Go into look-dev or rendered modes with Eevee as the render engine\n- Select each object in the scene and notice that the viewport redraws each time a new selection is made (obvious due to the flickering of the shadows)\n- If switched to cycles rendered mode, selection changes do not cause re-rendering\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", "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)", "Texture Mapping issues on large brush radius\nOperating system: Linux-6.4.6-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.6-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-50c29e1ffa)\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\n\nWhen a large brush radius for textured brushes in sculpt mode, the outer-most affected geometry doesn't apply the texture fully. This is especially noticeble on the Clay Strips and Paint brushes when the stroke method is set to anchored.\n\n\n\n\n\nBlend file = [bug.blend](attachment)\n\n- Open the File\n- Use the provided paint brush and clay strips brush on a subdivided cube or suzanne head like shown\n- Notice how the outer edges of the falloff is not updating the geoemtry fully\n\n", "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)", "Sculpt: RCS keymap conflicts (Context menu blocked by Face Sets pie menu, angle control, smooth/lazy mouse, smooth brush)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nI found 3 keys which are simply blocked by others:\n[2021-01-25 14-35-28.mp4](2021-01-25_14-35-28.mp4)\n`Shift+S`: `Context Toggle` (toggle smooth/lazy mouse) >> `Brush Select` (Smooth Brush)\n`R`: `Angle Control` (VIEW3D_MT_angle_control) >> `Rotate` (from 3D View)\n`W`: `Context menu` >> `Face Sets pie menu`\n\nIn Sculpt mode, W uses a Pie Menu (`VIEW3D_MT_sculpt_face_sets_edit_pie`), which in addition to doing nothing in Dyntopo (#84973), does not provide alternative access to this menu.\n\n# {key R}: `Angle Control` (VIEW3D_MT_angle_control) vs `Rotate`\n - Go to sculpt mode\n - Press {key R} to call the \"Angle Control\" menu - Rotate will be performed\n - In the Sidebar, go to `Tool -> Brush Settings -> Texture` and change the `Mapping` to \"View Plane\"\n - Press {key R} - \"Angle Control\" menu is now called\n# {key Shift S}: `Context Toggle` (toggle smooth/lazy mouse) vs `Brush Select` (Smooth Brush)\n - Go to Sculpt mode\n - Press {key Shift S} to enable the \"Stabilize Stroke\" (`Tool -> Brush Settings -> Stroke`) - The Smooth brush will be selected instead.\n - Disable the \"Brush Select\" keyitem from the keymap\n - Press {key Shift S} in the 3D View again\n# {key W}: `Context menu` vs `Face Sets pie menu`\n - Go to Sculpt mode\n - Press {key W} - Pie menu will be called\n - Disable the \"Face Sets Edit\" keyitem from the keymap\n - Press {key W} in the 3D View again - Context menu will be called", "Image Editor \"Erase Alpha\" brush erases all channels of float images\nLinux 64-bit\n\nBroken: 2.92\nNote: In versions 2.83 and earlier, Alpha was not premultiplied (this started in 4212b6528a, unsure if this should be the case if we are only looking at the Color without Alpha?).\n\nErasing the alpha on float images erase the RGB channels as well.\n[erase_alpha_bug.mp4](erase_alpha_bug.mp4)\n\n - Open the attached file. (Left image is a Non-float while right image is Float, both have Alpha channel. We are seeing only the RGB channels).\n - Use the brush \"Erase Alpha\" to erase part of the non-floating-point image (on the left).\n - Use shift-click to sample the pixel-values of this image. The RGB channels have **NOT** actually been affected and the image only appears to have been premultiplied.\n - Use the brush \"Erase Alpha\" on the floating-point image (on the right).\n # Use shift-click to sample the pixel-values of this image. **ALL** channels were erased!\n\nIt may look like the same bug as #86866 but it isn't! The brush works as expected; it's the RGB display that's wrong.\n[image editor bug.blend](image_editor_bug.blend)\n\n", "Missing viewport update after creating texture with canvas menu (sculpt mode, paint tool)\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nMissing viewport update after creating texture with canvas menu (sculpt mode, paint tool)\n\n- set viewport shading to `Material Preview`\n- Select cube\n- go to sculpt mode\n- select paint tool\n- open canvas menu\n\n- create new material slot texture with a certain color\n- result: \"Compiling Shaders 1\" in the viewport statistics top left, but this never finishes, update (incl. seeing the actual texture on the cube) only takes place after interaction with the viewport (rotating, zooming, doing an actual paint stroke)\n\n", "Mask paint is invisible in Sculpt Mode.\nOperating system:Mac OS 12.3.1\nGraphics card: 24-core GPU (?)\n\n**Blender Version** 3.2.1\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nThe mask in sculpt mode is invisible. I have the overlay turned on and I don't have any unapplied modifiers. I also don't have any physics or particle systems turned on. \n\nThank you for your help.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Backface culling is not working for mask in edit mode\n2.80 (sub 45), 893fa598319e, 2019-02-24 22:02\n\nAnd wireframe too heavy.\n\n\n\nIdk if it is bug or intended, but it will be nice, if it will work like on the 2nd or 3rd picture: much more readable.\nAnd when x-ray is on, wireframe on the background will be faded too, accordingly slider-setting.\n\n\n\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)", "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", "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)" ]

[ "Sculpting with smooth shading doesn't update normals\nOperating system: Linux-5.3.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0 Alpha\n\nWhen sculpting on an object with shading set to smooth, the normals are not being updated when the smooth brush (Laplacian) is used.\n\n- Add an object with high resolution\n- Switch the shading for the object to smooth instead of flat\n- Sculpt some strokes with the draw brush\n- Smooth out the surface\n\n" ]

[ "Issues with Fluid sim INSIDE objects\nOperating system: Win 10\nGraphics card: Twin GTX 1070\n\nBroken: 2.92\nWorked: 2.91\n\n**Fluid sim inside properly meshed objects does not work at all**\n- Create a tube with a curb or a Cylinder,\n- add a solidify modifier and apply it,\n- put a icosphere and downscale it to fit inside the tube,\n- keep icosphere selected and go to Object -> Quick Effects -> Quick Liquid.\n- scale the domain to fit everything inside.\n- Use tube as effector (planar or not does not work either way)\n- Try to bake a sim.\nAll settings that used to work in 2.93 and 2.91 do not work AT ALL in 2.92. Looks like it considers the mesh as a closed object.\n\nThanks in advance", "Particle hair simulation not working\nOperating system: Windows 10\nGraphics card: GTX 1070ti\n\nBroken: 2.93.4\nWorked: unknown\n\nI modeled particle-hair and try to make it dynamic, for whatever reason I cannot make it to work and sometimes Blender crashes.\n\n[Test.blend](Test.blend)\n\n[Test.crash.txt](Test.crash.txt) \n\nIf I try another simple particle-hair system on the-same object it does work. \n\nTry to get the hair in attached file to simulate.", "Timeline drawing with multiple simulation bakes\nCurrently, all simulation zones in an object are cached/baked together. However, that will change with #112179. It allows baking of individual simulations and simulations might also have independent frames ranges that they are active on.\n\nThis is a challenge for the timeline, because now it has to show information from potentially a large number of simulations which can have different cache states.\n\nCurrent timeline drawing:\n\n\nI can think of three main ways to address this:\n* Don't draw cache status in the timeline at all (this is what e.g. fluids seem to be doing). This would be simple, but we'd loose valuable information that's not really available anywhere else.\n* Draw a status bar in the timeline for every simulation. This shows the most information, but can get very confusing when there are many simulations (which will likely become more common over time). Also it's difficult to map between the timeline editor and the corresponding simulation nodes.\n \n* Draw information about all simulations in a single line, reducing information from all simulations.\n * If all simulations have the same frame range and cache state, the drawing could be the same we have now.\n * If two simulations are different in some aspect, the line needs to be drawn differently depending on the combination of simulation states. The issue here is that there may be many different combinations, so we probably have to reduce it down to the most useful set of states.\n * We could have a checkbox per simulation, that allows drawing a separate line in the timeline just for that simulation.\n * We could draw a separate line in the timeline for the \"active simulation(s)\", i.e. the one selected in the node editor or outliner.\n\n\nRelated task: #108196.", "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", "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", "bpy.ops.fluid.free_all() can cause a crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.0\n\npython script to free and re-bake smoke can cause a crash in 2.9x\n\nThe description of this bug is clearly documented along with the example blend file in [this blender stackexchange question ](python-script-to-bake-two-fluid-domains-aborting-cmd-line).\nIf I comment out the lines that contain:\n\n```\nbpy.ops.fluid.free_all()\n```\n\nin the following script, and instead manually free the bakes, all is fine. Otherwise the application crashes with console messages like:\n\n```\nUnable to remove directory\nor\nUnable to delete file\n```\neven if run from cmd line as Administrator\n\n\n```\nimport bpy\n\ndomain = bpy.data.objects['Smoke Domain Purple']\ndomain.select_set(True)\nprint(\"free Purple\")\nbpy.ops.fluid.free_all()\nprint(\"bake Purple\")\nbpy.ops.fluid.bake_data()\ndomain.select_set(False)\ndomain = bpy.data.objects['Smoke Domain Blue']\ndomain.select_set(True)\nprint(\"free Blue\")\nbpy.ops.fluid.free_all()\nprint(\"bake Blue\")\nbpy.ops.fluid.bake_data()\ndomain.select_set(False)\n```\n\n[dual smoke.blend](dual_smoke.blend)\n", "The flame of the Mantaflow Domains disappears when you make an append of the baked object.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nWhen simulating fire with Mantaflow, although the fire is baked and is correctly represented in the scene in which it was created, it disappears when an append of the domain is performed in a new scene.\n\nOpen the default scene.\nSelect the cube.\nWith Object / Quick Effects, create smoke.\nSelect the Flow Cube and in Flow Type activate Fire + Smoke.\nIn the Domain Cache activate Data File Format = OpenVDB.\nSimulate and bake the animation.\nSave the file\nOpen a new file.\nMake an append of the Domain.\nThe problem persists in the different render engines.\n[2020-02-12 21-06-54.mp4](2020-02-12_21-06-54.mp4)\n", "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", "Blender full crash during smoke+noise baking \"EXCEPTION_ACCESS_VIOLATION\"\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\nCPU: Ryzen 5900X\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nEvery single time I try to bake a high res particle system, in this case, fire at 256 + default noise settings, it never gets to complete the render and the blender crashes completely (including the console running in the background) at around frame 60 / 150.\nPausing and resuming baking sometimes works but most of the time it instantly crashes on the resume.\n\nEdit:\nI currently have 32 GB RAM and they are not really under much use during the bake.\nI tried with an RTX 3070 and Ryzen 5800x and the same issue.\n\nCrash file:\n\n\n```lines=30\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF76E01AD1A\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x000001C8281373F8\n\n\nStack trace:\nblender.exe :0x00007FF76E01A850 adaptive_domain_adjust\nblender.exe :0x00007FF76E021580 update_flowsfluids\nblender.exe :0x00007FF76E01F380 manta_step\nblender.exe :0x00007FF76E018CD0 BKE_fluid_modifier_processDomain\nblender.exe :0x00007FF76E018530 BKE_fluid_modifier_do\nblender.exe :0x00007FF76E2CC220 modifyMesh\nblender.exe :0x00007FF76E0C4DF0 mesh_calc_modifiers\nblender.exe :0x00007FF76E0C4AF0 mesh_build_data\nblender.exe :0x00007FF76E0C7170 makeDerivedMesh\nblender.exe :0x00007FF76E0A65F0 BKE_object_handle_data_update\nblender.exe :0x00007FF76E0A6320 BKE_object_eval_uber_data\nblender.exe :0x00007FF771D6AFA0 std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph * __ptr64,Main * __p\nblender.exe :0x00007FF771D69380 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF771D69330 blender::deg::`anonymous namespace'::deg_task_run_func\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF771DEE500 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFDEAAFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThreads:\nThread : 00002380\nntdll.dll :0x00007FFDEFFED280 NtDelayExecution\nKERNELBASE.dll :0x00007FFDEDB18FE0 SleepEx\nblender.exe :0x00007FF76E122380 wm_window_process_events\nblender.exe :0x00007FF76E1184D0 WM_main\nblender.exe :0x00007FF76DE09C70 main\nblender.exe :0x00007FF772313468 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000024a0\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000549c\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006094\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003a78\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000722c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000058fc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004090\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005f20\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000029a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000047b8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005718\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ba0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002ae4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006820\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001738\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c44\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004984\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c48\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000389c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002d68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002f90\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00007248\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005010\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002668\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000571c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000017f0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000060a4\nntdll.dll :0x00007FFDEFFF05F0 ZwWaitForAlertByThreadId\nntdll.dll :0x00007FFDEFFB3EF0 RtlSleepConditionVariableSRW\nKERNELBASE.dll :0x00007FFDEDB3C8A0 SleepConditionVariableSRW\nMSVCP140.dll :0x00007FFDD2CEBA70 _crtSetThreadpoolWait\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c64\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001d08\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ea4\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003cb8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000dd8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071bc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nnvoglv64.dll :0x00007FFD2046D50D Symbols not available\n\n\nThread : 000058f8\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFDEDB1C460 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20B35890 vk_icdNegotiateLoaderICDInterfaceVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000037dc\nwin32u.dll :0x00007FFDEDDDA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFDEF8A06F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002bcc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000031b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001778\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c94\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003e70\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000059b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000070a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003fd4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005b68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005508\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002c88\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000587c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000065ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000055ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006998\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001c30\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004bd0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000ee0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000049c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000041a8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000721c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000077f0\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\nblender.exe :0x00007FF76E319F80 tbb::internal::task_group_base::wait\nblender.exe :0x00007FF771D68EC0 blender::deg::deg_evaluate_on_refresh\nblender.exe :0x00007FF76DF8E3C0 BKE_scene_graph_update_for_newframe\nblender.exe :0x00007FF76E7B6A90 fluid_bake_startjob\nblender.exe :0x00007FF76E13D7D0 do_job_thread\nblender.exe :0x00007FF77234F320 _ptw32_threadStart\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF76DCE0000 2.9.2.0 blender.exe C:\\Program Files (x86)\\Steam\\steamapps\\common\\Blender\\blender.pdb \n0x00007FFDEFF50000 10.0.19041.844 ntdll.dll \n0x00007FFDEE790000 10.0.19041.804 KERNEL32.DLL \n0x00007FFDEDAD0000 10.0.19041.906 KERNELBASE.dll \n0x00007FFDEF880000 10.0.19041.906 USER32.dll \n0x00007FFDEDDD0000 10.0.19041.906 win32u.dll \n0x00007FFDEF500000 10.0.19041.746 GDI32.dll \n0x00007FFDED770000 10.0.19041.746 gdi32full.dll \n0x00007FFDED880000 10.0.19041.789 msvcp_win.dll \n0x00007FFDEAAF0000 2019.9.0.0 tbb.dll \n0x00007FFDEDE00000 10.0.19041.789 ucrtbase.dll \n0x00007FFDEEDB0000 10.0.19041.906 SHELL32.dll \n0x00007FFDED920000 10.0.19041.546 CFGMGR32.dll \n0x00007FFDEEA40000 10.0.19041.546 WS2_32.dll \n0x00007FFDEE5E0000 10.0.19041.746 RPCRT4.dll \n0x00007FFDCFCF0000 7.0.0.0 openvdb.dll \n0x00007FFDCF740000 10.0.19041.844 OPENGL32.dll \n0x00007FFDEEC60000 10.0.19041.610 ADVAPI32.dll \n0x00007FFDEED10000 7.0.19041.546 msvcrt.dll \n0x00007FFDEEAB0000 10.0.19041.906 sechost.dll \n0x00007FFDEDFF0000 10.0.19041.906 combase.dll \n0x00007FFDEE850000 10.0.19041.746 ole32.dll \n0x00007FFDEEA30000 10.0.19041.546 PSAPI.DLL \n0x00007FFDEEB50000 10.0.19041.746 SHLWAPI.dll \n0x00007FFDCF870000 3.7.7150.1013 python37.dll \n0x00007FFDEDFB0000 10.0.19041.546 IMM32.dll \n0x00007FFD22410000 58.54.100.0 avcodec-58.dll \n0x00007FFDCD5C0000 58.29.100.0 avformat-58.dll \n0x00007FFDEAB40000 58.8.100.0 avdevice-58.dll \n0x00007FFDEE510000 10.0.19041.804 OLEAUT32.dll \n0x00007FFDD40F0000 5.5.100.0 swscale-5.dll \n0x00007FFDCF610000 56.31.100.0 avutil-56.dll \n0x00007FFDEDDA0000 10.0.19041.662 bcrypt.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFDC8FD0000 1.20.1.0 OpenAL32.dll \n0x00007FFDCE1D0000 2.0.12.0 SDL2.dll \n0x00007FFDEAAE0000 2019.9.0.0 tbbmalloc_proxy.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFDEFAA0000 10.0.19041.844 SETUPAPI.dll \n0x00007FFDD2CB0000 14.26.28720.3 MSVCP140.dll \n0x00007FFDEAAC0000 14.26.28720.3 VCRUNTIME140.dll \n0x00007FFDEAAB0000 14.26.28720.3 VCRUNTIME140_1.dll \n0x00007FFDE1F70000 6.10.19041.844 COMCTL32.dll \n0x00007FFDE7F50000 10.0.19041.1 AVIFIL32.dll \n0x00007FFDE6B50000 10.0.19041.546 VERSION.dll \n0x00007FFDD8550000 10.0.19041.844 GLU32.dll \n0x00007FFDEBD30000 10.0.19041.867 dbghelp.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFDD30A0000 3.5.100.0 swresample-3.dll \n0x00007FFDCDB10000 10.0.19041.546 Secur32.dll \n0x00007FFDD82B0000 10.0.19041.1 AVICAP32.dll \n0x00007FFDE28A0000 10.0.19041.546 WINMM.dll \n0x00007FFDD2C70000 2019.9.0.0 tbbmalloc.dll \n0x00007FFD5AD10000 10.0.19041.1 MSACM32.dll \n0x00007FFDD3070000 10.0.19041.1 MSVFW32.dll \n0x00007FFDDECB0000 10.0.19041.1 winmmbase.dll \n0x00007FFDED580000 10.0.19041.906 SSPICLI.DLL \n0x00007FFDEE980000 10.0.19041.746 shcore.dll \n0x00007FFDEBF80000 10.0.19041.546 kernel.appcore.dll \n0x00007FFDEB590000 10.0.19041.906 windows.storage.dll \n0x00007FFDED100000 10.0.19041.662 Wldp.dll \n0x00007FFDEADF0000 10.0.19041.746 uxtheme.dll \n0x00007FFDED6F0000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFDED5D0000 10.0.19041.844 profapi.dll \n0x00007FFDEEBB0000 2001.12.10941.16384 clbcatq.dll \n0x00007FFDE6250000 10.0.19041.789 MMDevApi.dll \n0x00007FFDED440000 10.0.19041.546 DEVOBJ.dll \n0x00007FFDE6400000 10.0.19041.906 AUDIOSES.DLL \n0x00007FFDECC30000 10.0.19041.546 powrprof.dll \n0x00007FFDECAF0000 UMPDC.dll \n0x00007FFDEAF10000 10.0.19041.546 resourcepolicyclient.dll \n0x00007FFDEF6D0000 10.0.19041.906 MSCTF.dll \n0x00007FFDC2F40000 10.0.19041.746 dataexchange.dll \n0x00007FFDE8030000 10.0.19041.746 d3d11.dll \n0x00007FFDE8EB0000 10.0.19041.906 dcomp.dll \n0x00007FFDEBFD0000 10.0.19041.746 dxgi.dll \n0x00007FFDE6B60000 10.0.19041.746 twinapi.appcore.dll \n0x00007FFDE7A20000 10.0.19041.906 AppXDeploymentClient.dll \n0x00007FFD1FA70000 27.21.14.6192 nvoglv64.dll \n0x00007FFDEA2D0000 10.0.19041.546 WTSAPI32.dll \n0x00007FFDED280000 10.0.19041.546 msasn1.dll \n0x00007FFDE6AA0000 10.0.19041.906 cryptnet.dll \n0x00007FFDED970000 10.0.19041.844 CRYPT32.dll \n0x00007FFDED040000 10.0.19041.546 cryptbase.dll \n0x00007FFDED690000 10.0.19041.804 WINTRUST.dll \n0x00007FFDEC4F0000 10.0.19041.546 ntmarta.dll \n0x00007FFDE5470000 10.0.19041.546 dxcore.dll \n0x00007FFDEB000000 10.0.19041.746 dwmapi.dll \n0x00007FFDEC490000 10.0.19041.546 WINSTA.dll \n0x00007FFDCB3B0000 10.0.19041.906 textinputframework.dll \n0x00007FFDE9960000 10.0.19041.746 CoreMessaging.dll \n0x00007FFDE9420000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFDE9CA0000 10.0.19041.906 wintypes.dll \n0x00007FFDC2C70000 10.0.19041.844 explorerframe.dll \n0x00007FFDEA590000 7.0.19041.867 propsys.dll \n0x00007FFDED050000 10.0.19041.546 CRYPTSP.dll \n0x00007FFDEC7A0000 10.0.19041.546 rsaenh.dll \n0x00007FFDE53A0000 3.7.7150.1013 python3.dll \n0x00007FFDD40D0000 3.7.7150.1013 _bz2.pyd \n0x00007FFDD04E0000 3.7.7150.1013 _lzma.pyd \n0x00007FFDD04C0000 3.7.7150.1013 _socket.pyd \n0x00007FFDDFD70000 3.7.7150.1013 select.pyd \n \n# Python backtrace\n\n```\nSimply bake the file attached, I can't do it and I tried with multiple brand new .blend simple mantaflow setups.\n[Cinematic Fire Simulation.blend](Cinematic_Fire_Simulation.blend)", "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", "Particle instance modifier can crash when create from Children is checked and Normal is not\nOSX 10.11.6, xeon w3680 6core 12thread \n[system-info.txt](system-info.txt)\n2.69.7 5bd8ac9\nalso Nightly 2.79 34fe3f9c069\n\n\nUsing a particle instance modifier with Children checked and Normal not checked and then attempting to change certain parameters of the particle system such as in the velocity or children tabs causes a crash. Enabling Normal in the particle instance modifier prevents this from happening.\nCreate a Plane with a hair type particle system.\nCreate a cube with a particle instance modifier and set the object to the Plane with the particle system.\nCheck the box for Children and uncheck the box for Normal.\nGo to the particle system on the Plane and check Advanced. \nDrag any of the values in Velocity or Children and soon it will crash.\n[Crash_ParticleInstance.zip](Crash_ParticleInstance.zip)", "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)", "Mantaflow simulation stops and crashes at the end of the bake (or when closing blender): The CG solver diverged, residual norm > 1e30, stopping.\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nCrash baking fluid simulation.\n\n\nOpen the file and bake all its frames (or only frame 181 to 183).\n\n[beach.blend](beach.blend)\n\n```\nTraceback (most recent call last):\n File \"<string>\", line 1, in <module>\n File \"<string>\", line 169, in bake_fluid_data_5\n File \"<string>\", line 164, in bake_fluid_process_data_5\n File \"<string>\", line 136, in liquid_adaptive_step_5\n File \"<string>\", line 221, in liquid_step_5\nRuntimeError: GridCg::iterate: The CG solver diverged, residual norm > 1e30, stopping.\nError raised in extern/mantaflow/preprocessed/conjugategrad.cpp:562\n(...)\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in extern/mantaflow/preprocessed/fluidsolver.cpp:33\nAborted (core dumped)\n```\n\nComplete output: [P2568](P2568.txt)", "Simulation zone pauses randomly during render\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, Cycles, and Workbench, rendering an object with a simple simulation zone applied in geometry nodes results in some rendered frames being duplicates of each other, effectively making the simulation pause at random in the final render.\n\nThe workaround is to bake the simulation zone result before rendering (see screenshot.)\n\nCheck out the attached .blend file for reproduction.\n\n", "Smoke not rendering randomly, video and blend attached\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\n\n\nSmoke renders haphazardly in the viewport. see:\n[Blender Smoke Render Bug.mp4](Blender_Smoke_Render_Bug.mp4)\nSometimes it's fixed by toggling Adaptive Domain on/off and changing its Add Reosultion value up, e.g. 0, 16, 512, 32, 64, etc.\nThis is random and not guaranteed to fix it.\n\n- Open the attached .blend file,\n- Play (hit Space).\nSmoke sometimes renders correctly in the viewport, sometimes it doesn't.\n[SmokeDEBUG.blend](SmokeDEBUG.blend)" ]

[ "Quick smoke vorticity is broken.\nOperating system: Windows 10.\nGraphics card: NVIDIA GeForce RTX 2080 Super\n\nBroken: (version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29c0, type: Release \nThe same is on experimental 2.91\n[system-info.txt](system-info.txt)\n\nI'm not sure, but in video tutorial of Blender 2.7 is working correctly. Link to vid: watch?v=BhjK-6t9Gqs&t=2m10s\n\nWhen you add vorticity to smoke sim it does something crazy,video with 0 vorticity:\n[smoke_novorticity.wmv](smoke_novorticity.wmv)\n\n\nWith vorticity value of 3 here is what happens:\n[smoke_vorticity.wmv](smoke_vorticity.wmv)\nIt happens a bit differently on different strength but once you add any vorticity it goes wrongly.\n\nThe file is simple - adding icosphere, make couple keyframes to animate it. Add quick smoke, adjust domain. For emitter make temp.diff -1, enable initial velocity. For smoke domain set vorticity to 3.\n[smoke_voticity.blend](smoke_voticity.blend)" ]

[ "Compiling shaders for Eevee locks up the viewport until the process is complete (MacOS)\nOperating system: macOS-11.2.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 71.0.7\n\nBroken: version: 2.93.0 Beta\nWorked: I don't believe this has ever been good on the Mac platform\n\nWhen working in a heavy scene (the spring or barbershop demo, for example), the UI will \"beach ball\" or lock up while blender calculates Eevee shaders. On a pc, these calculations don't appear to lock up the interface the way it does on Mac. The expected behavior would be that the UI remains responsive at all times.\n\nOpen the Spring or Barbershop demos. Switch the viewport to full Eevee interactive rendering. The UI will lock up while Blender calculates the shaders. Once this process is complete, the viewport will return to normal behavior.\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)", "Image sequence render just stops on Cycles on MacOS Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Ultra 1.2\n\nBroken: version: 3.5.0\nWorked: none, tried 2.93, 3.3\n\nafter about 100 or so frames render just stops, Blender is still responsive, its not frozen or crashed, render bar just sits at %0. I'm doing motion tracking to get some kitbashed 3d elements into the scene. Plays fine in Eevee in the viewport. This is the error I get: CommandBuffer Failed: cycles_metal_shader_eval_displace. Attached ram usage for last 24 hours, I still have plenty of ram!\n\nI've closed the file and retried, several times, never got a render all the way through.\n", "Grease Pencil: Line Art › Light Contour causes crash\nOperating system: macOS-11.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M295X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.21\n\nBroken: version: 3.6.0 Alpha\nAlso reproduced with 3.5 and 3.4.1\n\nWhile using the Grease Pencil Line Art modifier, enabling the Light Contour feature causes a crash. The problem does not appear with a very simple scene, so a certain amount of geometry may be needed, hence the 6mb sample file. While trying to reproduce with smaller scenes, I sometimes had to toggle the Light Contour checkbox on and off a few times to trigger the crash, and the number of toggles actually varied from one launch to the next.\n\n1. Open provided file, GP crash.blend\n2. Select Grease Pencil object and expand its Line Art modifier\n3. Click Light Contour checkbox to enable it\n\nThis reliably causes a crash on my Intel Mac\n\n", "Decals crash Eevee on AMD graphics card\nOperating system: Linux 6.2.7 Manjaro \nGraphics card: AMD 7900XT\n\nBroken: 3.3LTS, 3.4.1\n\nUsing decals will crash blender in Eevee. cycles works\n\nas an example file please see the .blend that was linked here by the decalmachine creator: 66438\n\nThe issue there is unrelated but the file can serve to show the issue I am having. The moment I switch to rendered view or materials preview blender will crash. I see no error message in console. The log files states just: \n\n```\nbpy.context.space_data.shading.type = 'RENDERED' # Property\nbpy.context.space_data.context = 'RENDER' # Property\nbpy.context.scene.render.engine = 'BLENDER_EEVEE' # Property\n \n```\n\n", "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", "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", "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", "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.", "ops.paint.image_paint() crashes blender with brush texture\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.1\nWorked: unknown\n\n\nWhen using bpy.ops.paint.image_paint() in a addon and use a brush texture, blender crashes on the first stroke with a EXCEPTION_ACCESS_VIOLATION\n\n\n\n1. load the paintstroke addon \n```\n {F10253953}\n```\n\n2. load the blend file\n[paint_crash.blend](paint_crash.blend) \n3. go into texture paint mode\n3. make sure the brush texture is assigned\n\n4. paint on the object with (LEFTMOUSE)\n5. crash\n\n\n**addon code:**\n\n```\nbl_info = {\n 'name': 'paintstroke',\n 'description': 'Paint Material image channels at once',\n 'author': 'Daniel Grauer',\n 'version': (2, 0, 0),\n 'blender': (2, 92, 0),\n 'location': \"View3D > Sidebar > Edit Tab\",\n 'category': 'Image Paint',\n 'wiki_url': 'blender_Material_Brush',\n}\n\nimport bpy\nfrom bpy.utils import register_class, unregister_class\nfrom bpy.types import Operator, Brush\n\n \nclass PaintStroke(Operator):\n '''paintstroke'''\n bl_idname = \"paint.paintstroke\"\n bl_label = \"paintstroke\"\n bl_options = {'REGISTER', 'UNDO'}\n \n \n @classmethod\n def poll(cls, context):\n return bpy.ops.paint.image_paint.poll()\n \n def modal(self, context, event): \n #print(\"MB keybinding test modal\")\n if event.type in {'MOUSEMOVE'}: \n brushstroke = {\n \"name\": \"defaultStroke\",\n \"pen_flip\": False,\n \"is_start\": False,\n \"location\": (0,0,0),\n \"mouse\": (event.mouse_region_x, event.mouse_region_y),\n \"pressure\": 1,\n \"size\": bpy.context.tool_settings.unified_paint_settings.size,\n \"time\": 0,\n \"mouse_event\": (0.0, 0.0),\n \"x_tilt\": 0,\n \"y_tilt\": 0,\n }\n stroke = [brushstroke] \n bpy.ops.paint.image_paint(stroke=stroke, mode='NORMAL') \n\n elif event.value in {'RELEASE'} or event.type in {'ESC'}:\n return {'FINISHED'} \n return {'PASS_THROUGH'}\n \n\n def invoke(self, context, event):\n if event.type in {'LEFTMOUSE'}: \n #self.paint(event) \n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n \n\nclasses = (\n PaintStroke, \n )\n\n\naddon_keymaps = []\n\ndef register(): \n [register_class(c) for c in classes]\n \n # Keymapping\n kc = bpy.context.window_manager.keyconfigs.addon\n km = kc.keymaps.new(name=\"Image Paint\", space_type='EMPTY', modal=False)\n kmi = km.keymap_items.new(\"paint.paintstroke\", type='LEFTMOUSE', value='PRESS', shift=False, ctrl=False , alt=False)\n kmi.active = True\n addon_keymaps.append((km, kmi))\n \n\ndef unregister(): \n # remove keymaps\n for km, kmi in addon_keymaps:\n km.keymap_items.remove(kmi)\n addon_keymaps.clear() \n \n [unregister_class(c) for c in classes]\n \n\nif __name__ == \"__main__\":\n register() \n```\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\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", "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)", "`Materials` tab not opened at the first time running the script\nOperating system: macOS 10.14.2 (18C54)\nGraphics card: Intel Iris Plus Graphics 640 1536 MB\n\nBroken: (example: 2.80, 89207DF7222A, master, 2019-05-27, as found on the splash screen)\n\n`Materials` tab not open at the first time running the script in attached .blend file\n\n\n* Open the attached .blend file\n* Click `Run Script` the first time\n* It just opens the `Object` tab\n* Click `Run Script` the second time\n* It then opens the `Materials` tab\n\nIt should open Materials tab at the first time clicking `Run Script`\n\n[bug_001.blend](bug_001.blend)", "The version over 3.5 (3.6 and 3.6.2) crashes for me after using control of view.\nOperating system: Linux-6.2.0-32-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics 650 (Kaby Lake GT3e) (KBL GT3) Intel 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1\n\nBroken: 3.6 and 3.6.2\nWorked: version: 3.5.0\n\n\nI have quite simple scene: 1 table, 1 chair. I change selection from chair to table f.x., then deselection or I make zoom out, the screen freezes, Blender proposes me to closing because not responding\n\n" ]

[ "Crash when adding a reference image\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: Intel HD Graphics 4000 OpenGL Engine Intel Inc. 4.1 INTEL-14.7.20\n\nBroken: version: 2.93.5\nWorked: 2.93.5\n\nWhen adding a reference image to the viewport, either drag and drop or shift-A then adding a reference image, Blender crashes. I've reset Blender to its defaults but that did not help. I also trying using 2.93.4 to test, but the same crash happened.\n\nDrag and drop an image or shift-A{[F11669426](crash.blend)}\n\n", "Blender crashes whenever I tries to open either the texture properties menu or open a file with textures\nOperating system: macOS Catalina Version 10.15.7\nGraphics card and hardware: Intel HD Graphics 4000 with 8GB memory and 1536 MB VRAM, meets the requirement\n\nBroken: 2.93.5\nWorked: 2.80 (This is the version I used, it does not work anymore. And I forgot to update blender for two years)\n\n\nThree days ago I could I not open one of the files I was working on, blender crashes when I open it. Sent to my friend and asked him to open it, it worked. I messed around and tried to find the problem and eventually finds that whenever I open the texture properties menu or open a file with textures blender crashes around two seconds after. This happened **BEFORE** I updated blender and still happens after I installed the newer version.\n\n\nNo idea.\n\n**Crash Log**\n\n[Blender.txt](Blender.txt)", "Bug in Catalina 15.10.7\nMacBook Pro (13-inch, Mid 2012)\nOperating system: macOS Catalina 15.10.7\nGraphics card: Intel HD Graphics 4000 1536 MB\n\nBroken: all versions\n\n\nI use Blender on my mac for a few years, it was now version 2.80 and after my mac updated to macOS Catalina version 15.10.7 the blender opens and closes then i tried all the old blender versions and the same happens . If you can help. Thanks", "Switching to Material Preview and Eevee Crash :(\nI updated from 2.83 Bleter to 2.93 and this happened .\nevery time i click on Material Preview or when i render with eevee it crashes and i dont know why.\n\n\n\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel HD Graphics 4000 OpenGL Engine Intel Inc. 4.1 INTEL-14.7.20\n\nBroken: version: 2.83.10\n\n\n\n", "Blender Crash\nProcess: Blender [1945]\nPath: /Applications/Blender 3.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.0.0 (3.0.0 2021-11-12)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [1945]\nUser ID: 501\n\nDate/Time: 2021-12-03 21:25:45.525 +0100\nOS Version: Mac OS X 10.15.7 (19H1519)\nReport Version: 12\nAnonymous UUID: 72501B55-FE19-C6AF-1E96-1480A488346B\n\n\nTime Awake Since Boot: 780 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_CRASH (SIGABRT)\nException Codes: 0x0000000000000000, 0x0000000000000000\nException Note: EXC_CORPSE_NOTIFY\n\nApplication Specific Information:\nabort() called\n\nApplication Specific Signatures:\nGraphics kernel error: 0xfffffffb\n\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff691bb33a __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff6927be60 pthread_kill + 430\n2 libsystem_c.dylib \t0x00007fff691428a2 __abort + 139\n3 libsystem_c.dylib \t0x00007fff69142817 abort + 135\n4 libGPUSupportMercury.dylib \t0x00007fff503ad0a5 gpusGenerateCrashLog.cold.1 + 95\n5 libGPUSupportMercury.dylib \t0x00007fff503a418f gpusGenerateCrashLog + 89\n6 com.apple.driver.AppleIntelHD4000GraphicsGLDriver\t0x00007fff24c5add0 gpusKillClientExt + 9\n7 libGPUSupportMercury.dylib \t0x00007fff503a555b gpusSubmitDataBuffers + 164\n8 com.apple.driver.AppleIntelHD4000GraphicsGLDriver\t0x00007fff24830c78 IntelCommandBuffer::getNew(GLDContextRec*) + 48\n9 com.apple.driver.AppleIntelHD4000GraphicsGLDriver\t0x00007fff24830aa6 intelSubmitCommands + 187\n10 com.apple.driver.AppleIntelHD4000GraphicsGLDriver\t0x00007fff24835ba8 glrWriteBufferData + 554\n11 GLEngine \t0x00007fff39a91d6c glBufferSubData_Exec + 608\n12 org.blenderfoundation.blender \t0x0000000116bd6b9d blender::gpu::GLUniformBuf::update(void const*) + 141\n13 org.blenderfoundation.blender \t0x000000010eb8d98c drw_draw_pass_ex + 156\n14 org.blenderfoundation.blender \t0x000000010eb8d8df DRW_draw_pass + 31\n15 org.blenderfoundation.blender \t0x000000010ebd7314 OVERLAY_draw_scene + 324\n16 org.blenderfoundation.blender \t0x000000010eb84cd9 drw_engines_draw_scene + 185\n17 org.blenderfoundation.blender \t0x000000010eb83a61 DRW_draw_render_loop_ex + 1489\n18 org.blenderfoundation.blender \t0x000000010f686f28 view3d_main_region_draw + 136\n19 org.blenderfoundation.blender \t0x000000010f1620c1 ED_region_do_draw + 337\n20 org.blenderfoundation.blender \t0x000000010ea0dc4d wm_draw_update + 1757\n21 org.blenderfoundation.blender \t0x000000010ea0ac10 WM_main + 48\n22 org.blenderfoundation.blender \t0x000000010e47a12b main + 907\n23 libdyld.dylib \t0x00007fff69073cc9 start + 1\n\nThread 1:\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff6901aaed _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff6901afbf _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x000000011663d36f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 org.blenderfoundation.blender \t0x000000011663bdfe 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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n6 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff6901aaed _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff6901afbf _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x000000011663d36f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 org.blenderfoundation.blender \t0x000000011663bdfe 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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n6 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff6901aaed _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff6901afbf _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x000000011663d36f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 org.blenderfoundation.blender \t0x000000011663bdfe 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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n6 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff6901aaed _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff6901afbf _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x000000011663d36f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 org.blenderfoundation.blender \t0x000000011663bdfe 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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n6 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 5:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 com.apple.audio.caulk \t0x00007fff62bb7b16 caulk::mach::semaphore::wait() + 16\n2 com.apple.audio.caulk \t0x00007fff62bb79b2 caulk::semaphore::timed_wait(double) + 106\n3 com.apple.audio.caulk \t0x00007fff62bb77c4 caulk::concurrent::details::worker_thread::run() + 30\n4 com.apple.audio.caulk \t0x00007fff62bb71e4 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*) + 45\n5 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n6 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 com.apple.audio.caulk \t0x00007fff62bb7b16 caulk::mach::semaphore::wait() + 16\n2 com.apple.audio.caulk \t0x00007fff62bb79b2 caulk::semaphore::timed_wait(double) + 106\n3 com.apple.audio.caulk \t0x00007fff62bb77c4 caulk::concurrent::details::worker_thread::run() + 30\n4 com.apple.audio.caulk \t0x00007fff62bb71e4 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*) + 45\n5 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n6 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 7:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff691b4dfa mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff691b5170 mach_msg + 60\n2 com.apple.audio.CoreAudio \t0x00007fff2e5c6bf1 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 com.apple.audio.CoreAudio \t0x00007fff2e4c2d88 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 2677\n4 com.apple.audio.CoreAudio \t0x00007fff2e5f6b9e HALB_IOThread::Entry(void*) + 72\n5 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n6 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t0x00007fff691bb3d6 poll + 10\n1 select.cpython-39-darwin.so \t0x0000000131c42753 select_poll_poll + 291\n2 org.blenderfoundation.blender \t0x0000000116c9fa3c method_vectorcall_FASTCALL + 140\n3 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n4 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n5 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n6 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n7 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n8 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n9 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n10 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d847ea _PyEval_EvalFrameDefault + 27114\n13 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n14 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d846a0 _PyEval_EvalFrameDefault + 26784\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c99506 method_vectorcall + 486\n19 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n20 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n21 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n22 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n23 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n24 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n25 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n26 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n27 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n28 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n29 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n30 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n31 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 13:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116cb4277 calliter_iternext + 71\n7 org.blenderfoundation.blender \t0x0000000116d83f3a _PyEval_EvalFrameDefault + 24890\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 17:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 18:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t0x00007fff691bb3d6 poll + 10\n1 select.cpython-39-darwin.so \t0x0000000131c42753 select_poll_poll + 291\n2 org.blenderfoundation.blender \t0x0000000116c9fa3c method_vectorcall_FASTCALL + 140\n3 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n4 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n5 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n6 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n7 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n8 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n9 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n10 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d847ea _PyEval_EvalFrameDefault + 27114\n13 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n14 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d846a0 _PyEval_EvalFrameDefault + 26784\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c99506 method_vectorcall + 486\n19 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n20 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n21 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n22 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n23 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n24 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n25 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n26 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n27 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n28 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n29 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n30 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n31 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116cb4277 calliter_iternext + 71\n7 org.blenderfoundation.blender \t0x0000000116d83f3a _PyEval_EvalFrameDefault + 24890\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t0x00007fff691bb3d6 poll + 10\n1 select.cpython-39-darwin.so \t0x0000000131c42753 select_poll_poll + 291\n2 org.blenderfoundation.blender \t0x0000000116c9fa3c method_vectorcall_FASTCALL + 140\n3 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n4 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n5 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n6 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n7 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n8 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n9 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n10 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d847ea _PyEval_EvalFrameDefault + 27114\n13 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n14 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d846a0 _PyEval_EvalFrameDefault + 26784\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c99506 method_vectorcall + 486\n19 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n20 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n21 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n22 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n23 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n24 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n25 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n26 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n27 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n28 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n29 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n30 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n31 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116cb4277 calliter_iternext + 71\n7 org.blenderfoundation.blender \t0x0000000116d83f3a _PyEval_EvalFrameDefault + 24890\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 31:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t0x00007fff691bb3d6 poll + 10\n1 select.cpython-39-darwin.so \t0x0000000131c42753 select_poll_poll + 291\n2 org.blenderfoundation.blender \t0x0000000116c9fa3c method_vectorcall_FASTCALL + 140\n3 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n4 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n5 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n6 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n7 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n8 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n9 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n10 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d847ea _PyEval_EvalFrameDefault + 27114\n13 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n14 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d846a0 _PyEval_EvalFrameDefault + 26784\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c99506 method_vectorcall + 486\n19 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n20 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n21 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n22 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n23 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n24 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n25 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n26 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n27 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n28 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n29 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n30 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n31 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 34:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116cb4277 calliter_iternext + 71\n7 org.blenderfoundation.blender \t0x0000000116d83f3a _PyEval_EvalFrameDefault + 24890\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 35:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 36:\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x000000010ea019a8 tbb::internal::rml::private_worker::run() + 344\n2 org.blenderfoundation.blender \t0x000000010ea01849 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n4 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 37:\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x000000010ea019a8 tbb::internal::rml::private_worker::run() + 344\n2 org.blenderfoundation.blender \t0x000000010ea01849 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n4 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 38:\n0 libsystem_kernel.dylib \t0x00007fff691b4e36 semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x000000010ea019a8 tbb::internal::rml::private_worker::run() + 344\n2 org.blenderfoundation.blender \t0x000000010ea01849 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n4 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 39:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff691b4dfa mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff691b5170 mach_msg + 60\n2 com.apple.CoreFoundation \t0x00007fff2eef62b7 __CFRunLoopServiceMachPort + 247\n3 com.apple.CoreFoundation \t0x00007fff2eef4d71 __CFRunLoopRun + 1329\n4 com.apple.CoreFoundation \t0x00007fff2eef41e3 CFRunLoopRunSpecific + 466\n5 com.apple.AppKit \t0x00007fff2c2f9ea4 _NSEventThread + 132\n6 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n7 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 40:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 41:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 42:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 43:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 44:\n0 libsystem_kernel.dylib \t0x00007fff691bb3d6 poll + 10\n1 select.cpython-39-darwin.so \t0x0000000131c42753 select_poll_poll + 291\n2 org.blenderfoundation.blender \t0x0000000116c9fa3c method_vectorcall_FASTCALL + 140\n3 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n4 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n5 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n6 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n7 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n8 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n9 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n10 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d847ea _PyEval_EvalFrameDefault + 27114\n13 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n14 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d846a0 _PyEval_EvalFrameDefault + 26784\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c99506 method_vectorcall + 486\n19 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n20 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n21 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n22 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n23 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n24 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n25 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n26 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n27 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n28 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n29 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n30 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n31 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 45:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116cb4277 calliter_iternext + 71\n7 org.blenderfoundation.blender \t0x0000000116d83f3a _PyEval_EvalFrameDefault + 24890\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 46:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 47:\n0 libsystem_pthread.dylib \t0x00007fff69277b68 start_wqthread + 0\n\nThread 48:\n0 libsystem_pthread.dylib \t0x00007fff69277b68 start_wqthread + 0\n\nThread 49:\n0 libsystem_pthread.dylib \t0x00007fff69277b68 start_wqthread + 0\n\nThread 50:\n0 libsystem_pthread.dylib \t0x00007fff69277b68 start_wqthread + 0\n\nThread 51:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 52:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 53:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 54:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n9 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n10 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n11 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n12 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n13 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n14 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n19 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n20 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n21 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n22 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 55:\n0 libsystem_kernel.dylib \t0x00007fff691bb3d6 poll + 10\n1 select.cpython-39-darwin.so \t0x0000000131c42753 select_poll_poll + 291\n2 org.blenderfoundation.blender \t0x0000000116c9fa3c method_vectorcall_FASTCALL + 140\n3 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n4 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n5 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n6 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n7 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n8 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n9 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n10 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d847ea _PyEval_EvalFrameDefault + 27114\n13 org.blenderfoundation.blender \t0x0000000116d88e7d _PyEval_EvalCode + 3245\n14 org.blenderfoundation.blender \t0x0000000116c96dd1 _PyFunction_Vectorcall + 257\n15 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n16 org.blenderfoundation.blender \t0x0000000116d846a0 _PyEval_EvalFrameDefault + 26784\n17 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n18 org.blenderfoundation.blender \t0x0000000116c99506 method_vectorcall + 486\n19 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n20 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n21 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n22 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n23 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n24 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n25 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n26 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n27 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n28 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n29 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n30 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n31 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 56:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116cb4277 calliter_iternext + 71\n7 org.blenderfoundation.blender \t0x0000000116d83f3a _PyEval_EvalFrameDefault + 24890\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 57:\n0 libsystem_kernel.dylib \t0x00007fff691b7882 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff6927c425 _pthread_cond_wait + 698\n2 org.blenderfoundation.blender \t0x0000000116ddc96d PyThread_acquire_lock_timed + 557\n3 _queue.cpython-39-darwin.so \t0x0000000134623561 _queue_SimpleQueue_get_impl + 369\n4 _queue.cpython-39-darwin.so \t0x000000013462317f _queue_SimpleQueue_get + 191\n5 org.blenderfoundation.blender \t0x0000000116cd9d74 cfunction_vectorcall_FASTCALL_KEYWORDS + 132\n6 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n7 org.blenderfoundation.blender \t0x0000000116d84742 _PyEval_EvalFrameDefault + 26946\n8 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n9 org.blenderfoundation.blender \t0x0000000116d84d5b _PyEval_EvalFrameDefault + 28507\n10 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n11 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n12 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n13 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n14 org.blenderfoundation.blender \t0x0000000116d87d7b call_function + 411\n15 org.blenderfoundation.blender \t0x0000000116d84676 _PyEval_EvalFrameDefault + 26742\n16 org.blenderfoundation.blender \t0x0000000116c96ec5 function_code_fastcall + 229\n17 org.blenderfoundation.blender \t0x0000000116c9948f method_vectorcall + 367\n18 org.blenderfoundation.blender \t0x0000000116e2d796 t_bootstrap + 70\n19 org.blenderfoundation.blender \t0x0000000116ddc549 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t0x00007fff6927c109 _pthread_start + 148\n21 libsystem_pthread.dylib \t0x00007fff69277b8b thread_start + 15\n\nThread 58:\n0 libsystem_pthread.dylib \t0x00007fff69277b68 start_wqthread + 0\n\nThread 0 crashed with X86 Thread State (64-bit):\n```\nrax: 0x0000000000000000 rbx: 0x0000000125ffbdc0 rcx: 0x00007ffee1900df8 rdx: 0x0000000000000000\nrdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007ffee1900e20 rsp: 0x00007ffee1900df8\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000125ffbdc0 r11: 0x0000000000000246\nr12: 0x0000000000000307 r13: 0x00007fe157bef2b0 r14: 0x0000000000000006 r15: 0x0000000000000016\nrip: 0x00007fff691bb33a rfl: 0x0000000000000246 cr2: 0x000000013c1e4000\n\n```\nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n\n\nBinary Images:\n 0x10e2fe000 - 0x11a901f1f +org.blenderfoundation.blender (3.0.0 - 3.0.0 2021-11-12) <C79B6069-E0E0-3BE1-9728-7A61F3E887DF> /Applications/Blender 3.app/Contents/MacOS/Blender\n 0x12253a000 - 0x1225a5ff3 +libomp.dylib (0) <0AE3ADB3-C01E-334A-B0BA-E9A374587E3D> /Applications/Blender 3.app/Contents/Resources/3.0/lib/libomp.dylib\n 0x124243000 - 0x124247fff com.apple.audio.AppleHDAHALPlugIn (283.15 - 283.15) <AB88E450-7A43-3F72-9A07-FA761BA1B389> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x125d87000 - 0x125ee0ff7 com.apple.audio.units.Components (1.14 - 1.14) <1AE0EF8D-BBC9-3A50-B4A6-31735A41BB76> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x125f1c000 - 0x125f1f047 libobjc-trampolines.dylib (787.1) <571C6A14-9E0E-3139-B82D-A1A3D46F2C9C> /usr/lib/libobjc-trampolines.dylib\n 0x125f30000 - 0x125fc2267 dyld (750.7) <FAE66DB5-B10B-393E-98E6-FC052DA267B0> /usr/lib/dyld\n 0x1272a9000 - 0x1272abfff +_heapq.cpython-39-darwin.so (0) <4435868A-0B70-306D-9523-88454FB26DF9> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_heapq.cpython-39-darwin.so\n 0x1272b3000 - 0x1272b4fff +_bisect.cpython-39-darwin.so (0) <6523CCB9-FBAD-3264-B0AC-45D5A2155047> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_bisect.cpython-39-darwin.so\n 0x12a651000 - 0x12a65aff3 +math.cpython-39-darwin.so (0) <BD93E619-C5F7-3EC6-8195-BCE1185D5B4D> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/math.cpython-39-darwin.so\n 0x12ada6000 - 0x12ada7ff3 +_random.cpython-39-darwin.so (0) <D94C41F0-ED03-37DD-B7E0-B7943094FB9D> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_random.cpython-39-darwin.so\n 0x12adb0000 - 0x12adb4ff7 +_sha512.cpython-39-darwin.so (0) <65FE8D47-D7D1-35B5-A3D7-715055CBB7EB> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_sha512.cpython-39-darwin.so\n 0x12ae3c000 - 0x12ae3cff7 +_opcode.cpython-39-darwin.so (0) <7CEBFD8B-0C12-3BE6-9744-BB873A46F7A5> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_opcode.cpython-39-darwin.so\n 0x12ae84000 - 0x12ae8afff +_json.cpython-39-darwin.so (0) <B917D818-8243-3764-B8FC-BA71B09E6085> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_json.cpython-39-darwin.so\n 0x12af14000 - 0x12af1cff7 +binascii.cpython-39-darwin.so (0) <DD7010C4-AB00-38F7-A377-D2EC898465A1> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so\n 0x12af25000 - 0x12af39ff3 +zlib.cpython-39-darwin.so (0) <AE10DFD1-609A-3F74-97B9-C59D625D0563> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/zlib.cpython-39-darwin.so\n 0x12af44000 - 0x12af5aff3 +_bz2.cpython-39-darwin.so (0) <85EB8565-95DF-37DD-85C4-7146ED337C90> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_bz2.cpython-39-darwin.so\n 0x12af65000 - 0x12af94ff3 +_lzma.cpython-39-darwin.so (0) <9F0561F7-E61B-3B36-9570-E7970A66CA37> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_lzma.cpython-39-darwin.so\n 0x12afa2000 - 0x12afa3ff7 +grp.cpython-39-darwin.so (0) <EC51AC03-0C6D-312D-A90F-1F179F6A4088> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/grp.cpython-39-darwin.so\n 0x12afab000 - 0x12afb0ff7 +_struct.cpython-39-darwin.so (0) <DB5D4B1F-164B-3787-A5E7-EC6440E62583> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_struct.cpython-39-darwin.so\n 0x12b27d000 - 0x12b283ff3 +cmath.cpython-39-darwin.so (0) <F7858BA7-CD34-39A1-B1CD-95799F8536DF> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/cmath.cpython-39-darwin.so\n 0x12b48e000 - 0x12b849fd7 +_multiarray_umath.cpython-39-darwin.so (0) <6D5306A5-0ADF-30E5-B7DF-EAE3157E59C4> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so\n 0x12b982000 - 0x12f5346ef +libopenblas.0.dylib (0) <9112000D-375C-34F0-9A66-9D68F91A12CD> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/.dylibs/libopenblas.0.dylib\n 0x12f7d2000 - 0x12f8e9ff7 +libgfortran.3.dylib (0) <9ABE5EDE-AD43-391A-9E54-866711FAC32A> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/.dylibs/libgfortran.3.dylib\n 0x12f958000 - 0x12f98efff +libquadmath.0.dylib (0) <7FFA409F-FB04-3B64-BE9A-3E3A494C975E> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/.dylibs/libquadmath.0.dylib\n 0x12f9a2000 - 0x12f9b7ff7 +libgcc_s.1.dylib (0) <7C6D7CB7-82DB-3290-8181-07646FEA1F80> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/.dylibs/libgcc_s.1.dylib\n 0x131a07000 - 0x131a16fff +_datetime.cpython-39-darwin.so (0) <F6DCFCF7-7674-3E18-B988-E8FB0EA15B2D> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_datetime.cpython-39-darwin.so\n 0x131aa7000 - 0x131abdff7 +_pickle.cpython-39-darwin.so (0) <4C3BED93-F0CB-3A06-996B-FF702CF491BB> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_pickle.cpython-39-darwin.so\n 0x131bcd000 - 0x131bdcff3 +_multiarray_tests.cpython-39-darwin.so (0) <8DD0C91A-F5D2-34E6-AE55-ABDF68F90FD4> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/core/_multiarray_tests.cpython-39-darwin.so\n 0x131c35000 - 0x131c37ff3 +_posixsubprocess.cpython-39-darwin.so (0) <B83E0566-BBF0-35A7-A854-9BE8113AA79E> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_posixsubprocess.cpython-39-darwin.so\n 0x131c40000 - 0x131c44fff +select.cpython-39-darwin.so (0) <087F3AFE-A4C9-3236-88B5-FC3AF2040C43> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/select.cpython-39-darwin.so\n 0x131c4e000 - 0x131c6af7f +_ctypes.cpython-39-darwin.so (0) <750F9FDF-33D4-3C82-85E6-6A4E654386D1> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_ctypes.cpython-39-darwin.so\n 0x131d03000 - 0x131d06ffb +lapack_lite.cpython-39-darwin.so (0) <B12E9544-44FF-3554-B75E-CDCA20B534FF> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/linalg/lapack_lite.cpython-39-darwin.so\n 0x131d13000 - 0x131d2eff3 +_umath_linalg.cpython-39-darwin.so (0) <DF05EA91-A61D-3DE1-A95D-A03CAF423492> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/linalg/_umath_linalg.cpython-39-darwin.so\n 0x131dc7000 - 0x131ddafff +_pocketfft_internal.cpython-39-darwin.so (0) <3E71DDF0-A465-3093-9257-E1CFD7FA2403> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/fft/_pocketfft_internal.cpython-39-darwin.so\n 0x131e67000 - 0x131edaffb +mtrand.cpython-39-darwin.so (0) <C6F1D297-403C-34C4-8345-C36FFB3DBD48> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/mtrand.cpython-39-darwin.so\n 0x131f3f000 - 0x131f5efff +bit_generator.cpython-39-darwin.so (0) <3DB8FF1E-5AE6-3D7F-8EBE-C9E331B438E8> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/bit_generator.cpython-39-darwin.so\n 0x131f87000 - 0x131fbafff +_common.cpython-39-darwin.so (0) <E898A3FF-F5F3-3851-9929-E99EF69F3C88> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/_common.cpython-39-darwin.so\n 0x131fdb000 - 0x1321f7b0f +_hashlib.cpython-39-darwin.so (0) <DB86902F-762A-3624-AE03-798BE3327B90> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_hashlib.cpython-39-darwin.so\n 0x132292000 - 0x132298ff7 +_blake2.cpython-39-darwin.so (0) <6BBEE8BC-36A1-3E76-A425-3C77EBD35E24> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_blake2.cpython-39-darwin.so\n 0x1322a2000 - 0x1322f5fff +_bounded_integers.cpython-39-darwin.so (0) <0A44E7B9-54D0-3216-ADC2-37FB6DE623D8> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/_bounded_integers.cpython-39-darwin.so\n 0x132326000 - 0x132335ff3 +_mt19937.cpython-39-darwin.so (0) <0E7CB1A0-3AAA-3313-B6D2-E64647A616F4> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/_mt19937.cpython-39-darwin.so\n 0x13234a000 - 0x132359ff7 +_philox.cpython-39-darwin.so (0) <DCDA722A-3169-318C-983E-F94217389617> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/_philox.cpython-39-darwin.so\n 0x13236e000 - 0x13237dffb +_pcg64.cpython-39-darwin.so (0) <C406953F-0F32-3CDB-9FFD-EF8EAA9810FF> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/_pcg64.cpython-39-darwin.so\n 0x132392000 - 0x132399ff7 +_sfc64.cpython-39-darwin.so (0) <EDFA6F98-89F3-308A-9F4E-46F776F32296> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/_sfc64.cpython-39-darwin.so\n 0x1323aa000 - 0x132435fff +_generator.cpython-39-darwin.so (0) <94886D96-4DA7-31B5-BFCC-C14DF330E68A> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/site-packages/numpy/random/_generator.cpython-39-darwin.so\n 0x134622000 - 0x134623fff +_queue.cpython-39-darwin.so (0) <2C3D2B9E-C671-36CC-92B4-2A4E076C8E19> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_queue.cpython-39-darwin.so\n 0x134652000 - 0x13465fffb +_socket.cpython-39-darwin.so (0) <60AFEE8B-EA4A-33F3-A4BB-D8BCDDC32E58> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_socket.cpython-39-darwin.so\n 0x134a12000 - 0x134a40fff +pyexpat.cpython-39-darwin.so (0) <6BA347F0-9D4B-3213-AECE-E1A599CB104D> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/pyexpat.cpython-39-darwin.so\n 0x134d58000 - 0x134d5ffff +array.cpython-39-darwin.so (0) <19C8E8ED-23A1-302C-BED4-637AD3B0067C> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/array.cpython-39-darwin.so\n 0x134d6c000 - 0x134d6dff3 +_multiprocessing.cpython-39-darwin.so (0) <F418338E-4F96-3C9A-B81D-9E4D2EE84D8B> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_multiprocessing.cpython-39-darwin.so\n 0x134db6000 - 0x13506d29f +_ssl.cpython-39-darwin.so (0) <8468CDDE-67CB-3F23-ABCB-5B3A3B18FB86> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_ssl.cpython-39-darwin.so\n 0x1352fa000 - 0x135405ff7 +unicodedata.cpython-39-darwin.so (0) <A2FE0369-173C-3CE4-AA8C-0BFEA18C893A> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/unicodedata.cpython-39-darwin.so\n 0x135411000 - 0x135415ffb +_multibytecodec.cpython-39-darwin.so (0) <02FFF8BF-C63B-38E2-9B12-E024F16426CD> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_multibytecodec.cpython-39-darwin.so\n 0x1354a2000 - 0x1354a2ffb +_scproxy.cpython-39-darwin.so (0) <13352C8E-C878-3573-B2FE-4A564CD34F1F> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_scproxy.cpython-39-darwin.so\n 0x13562a000 - 0x13562affb +_uuid.cpython-39-darwin.so (0) <3DAB9203-3DB0-3BB0-977A-CA94538549EB> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_uuid.cpython-39-darwin.so\n 0x1356f2000 - 0x135735ff7 +_decimal.cpython-39-darwin.so (0) <4D497ADD-96D2-3A0E-98D7-B5E2DD8C0E32> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_decimal.cpython-39-darwin.so\n 0x135754000 - 0x135754ffb +_statistics.cpython-39-darwin.so (0) <A5958A2F-84FA-374F-8792-610059DDD56C> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_statistics.cpython-39-darwin.so\n 0x135bdc000 - 0x135be6ffb +_elementtree.cpython-39-darwin.so (0) <5866FAB7-811A-3FA4-8A7B-4876ADE3728D> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_elementtree.cpython-39-darwin.so\n 0x135c35000 - 0x135c94ffb +_imaging.cpython-39-darwin.so (0) <8EFF35BF-5AB0-3532-953A-C5DF8B6FB3E6> /Users/USER/*/_imaging.cpython-39-darwin.so\n 0x135cc1000 - 0x135cf8ff3 +libjpeg.9.dylib (0) <A64FF089-2549-3F0D-88B5-6659DDF22B5D> /Users/USER/*/libjpeg.9.dylib\n 0x135d0d000 - 0x135d90ff7 +libopenjp2.2.4.0.dylib (0) <1CCFE535-1A7F-3C88-A8DF-F9C23CC0251A> /Users/USER/*/libopenjp2.2.4.0.dylib\n 0x135da1000 - 0x135dbcff7 +libz.1.2.11.dylib (0) <167A44E4-48C7-3096-B8B0-D995E03899F2> /Users/USER/*/libz.1.2.11.dylib\n 0x135dc5000 - 0x135e5cff3 +libtiff.5.dylib (0) <01D059E4-376C-39EF-B882-F3F19D76368B> /Users/USER/*/libtiff.5.dylib\n 0x135e71000 - 0x135e98ff3 +libxcb.1.1.0.dylib (0) <67125A03-DD5F-316E-B8A1-8D429AA8C847> /Users/USER/*/libxcb.1.1.0.dylib\n 0x135ead000 - 0x135ee0ff7 +liblzma.5.dylib (0) <16BF2FCB-16FA-30E7-ABE8-FD5025393AF2> /Users/USER/*/liblzma.5.dylib\n 0x135eed000 - 0x135ef0ff7 +libXau.6.dylib (0) <BEA2533A-4E98-3333-A29C-0B9622570F4B> /Users/USER/*/libXau.6.dylib\n 0x136079000 - 0x136079ff7 +_posixshmem.cpython-39-darwin.so (0) <7457ECA0-6A72-3A7D-8E96-5C7279889360> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_posixshmem.cpython-39-darwin.so\n 0x136cc1000 - 0x136cc4fff +test_compile.cpython-39-darwin.so (0) <4A7BF42B-304B-39F9-B3B5-7A585BDE053C> /Users/USER/Library/Application Support/Blender/*/test_compile.cpython-39-darwin.so\n 0x136ccd000 - 0x136cd0ffb +murmurhash3.cpython-39-darwin.so (0) <6AB2AFD2-E5C6-3768-8A74-F4B40E155D2B> /Users/USER/Library/Application Support/Blender/*/murmurhash3.cpython-39-darwin.so\n 0x136cd9000 - 0x136cdcff7 +utils.cpython-39-darwin.so (0) <846E925B-CCE7-31B4-841D-DE0B2110FC75> /Users/USER/Library/Application Support/Blender/*/utils.cpython-39-darwin.so\n 0x136ce5000 - 0x136cfcfff +implementations.cpython-39-darwin.so (0) <BC83F6A3-D19D-36F1-8EFE-55978352B771> /Users/USER/Library/Application Support/Blender/*/implementations.cpython-39-darwin.so\n 0x136d59000 - 0x136d64fff +clist.cpython-39-darwin.so (0) <29D09CB7-F801-3663-89E2-6DCA1ED1D1D3> /Users/USER/Library/Application Support/Blender/*/clist.cpython-39-darwin.so\n 0x136d71000 - 0x136f00ff7 +base_lists.cpython-39-darwin.so (0) <DCAA0AA9-B32E-3E34-B4DC-9C3216D8F629> /Users/USER/Library/Application Support/Blender/*/base_lists.cpython-39-darwin.so\n 0x136f89000 - 0x136f8cfff +geometry.cpython-39-darwin.so (0) <DDE9EBC9-7D87-3B33-BB59-102F8E52CF09> /Users/USER/Library/Application Support/Blender/*/geometry.cpython-39-darwin.so\n 0x136f95000 - 0x136f98ff7 +vector.cpython-39-darwin.so (0) <BE2B1817-56D6-3C60-8336-C8DACAFC5DE2> /Users/USER/Library/Application Support/Blender/*/vector.cpython-39-darwin.so\n 0x136fa1000 - 0x136facffb +conversion.cpython-39-darwin.so (0) <F05E5F6B-C187-3A79-8FB3-FE58F01F5328> /Users/USER/Library/Application Support/Blender/*/conversion.cpython-39-darwin.so\n 0x136fb5000 - 0x136fbcff3 +list_operations.cpython-39-darwin.so (0) <06A89563-1CDB-3B72-B414-5304C30BEB5C> /Users/USER/Library/Application Support/Blender/*/list_operations.cpython-39-darwin.so\n 0x136fc5000 - 0x136fccff7 +matrix.cpython-39-darwin.so (0) <A149B24E-2322-3B92-8014-78AC57910F9D> /Users/USER/Library/Application Support/Blender/*/matrix.cpython-39-darwin.so\n 0x137015000 - 0x13701cfff +rotation_conversion.cpython-39-darwin.so (0) <33820D59-5008-3897-BC56-49D060BF7F44> /Users/USER/Library/Application Support/Blender/*/rotation_conversion.cpython-39-darwin.so\n 0x137025000 - 0x137028ff7 +quaternion.cpython-39-darwin.so (0) <FA232D35-F08D-37ED-BE2B-A1EB66717085> /Users/USER/Library/Application Support/Blender/*/quaternion.cpython-39-darwin.so\n 0x137031000 - 0x137034ff3 +number.cpython-39-darwin.so (0) <C8F5A7F9-C1E6-3A7A-8315-4184450D948D> /Users/USER/Library/Application Support/Blender/*/number.cpython-39-darwin.so\n 0x13703d000 - 0x137044ff3 +utils.cpython-39-darwin.so (0) <8A843175-E7CC-379E-AAD2-298749E37FC9> /Users/USER/Library/Application Support/Blender/*/utils.cpython-39-darwin.so\n 0x13704d000 - 0x137064ff7 +polygon_indices_list.cpython-39-darwin.so (0) <17085318-1859-38EA-8E67-5A9FC4910FB0> /Users/USER/Library/Application Support/Blender/*/polygon_indices_list.cpython-39-darwin.so\n 0x137075000 - 0x13708cff7 +virtual_list.cpython-39-darwin.so (0) <C0D536AF-BC93-3DCB-8E43-4FF6CF80EBD9> /Users/USER/Library/Application Support/Blender/*/virtual_list.cpython-39-darwin.so\n 0x13709d000 - 0x1370d8fff +virtual_clists.cpython-39-darwin.so (0) <C63BB4C9-5962-3F0B-BD64-09E45697F145> /Users/USER/Library/Application Support/Blender/*/virtual_clists.cpython-39-darwin.so\n 0x1370fd000 - 0x137104ff3 +default_list.cpython-39-darwin.so (0) <F74F8F33-55DC-333A-84B8-E7FE0112B7B5> /Users/USER/Library/Application Support/Blender/*/default_list.cpython-39-darwin.so\n 0x13710d000 - 0x137114ffb +c_default_list.cpython-39-darwin.so (0) <F1897E38-777D-374F-9B2F-B64C00869E2D> /Users/USER/Library/Application Support/Blender/*/c_default_list.cpython-39-darwin.so\n 0x13711d000 - 0x137130fff +attribute.cpython-39-darwin.so (0) <8791A890-0725-3177-9092-C5E86FAFDCBF> /Users/USER/Library/Application Support/Blender/*/attribute.cpython-39-darwin.so\n 0x137141000 - 0x13716cff3 +mesh_data.cpython-39-darwin.so (0) <9C49D881-6186-39D7-A31D-92DC56882046> /Users/USER/Library/Application Support/Blender/*/mesh_data.cpython-39-darwin.so\n 0x137181000 - 0x137198fff +validate.cpython-39-darwin.so (0) <ED6E22B0-0681-3370-AC10-47A56E8465FA> /Users/USER/Library/Application Support/Blender/*/validate.cpython-39-darwin.so\n 0x1371a5000 - 0x1371acff7 +triangulate_mesh.cpython-39-darwin.so (0) <17EB5B6E-226F-36AB-8CD4-EF114C8FCB5B> /Users/USER/Library/Application Support/Blender/*/triangulate_mesh.cpython-39-darwin.so\n 0x1371b9000 - 0x1371c8ff3 +poly_spline.cpython-39-darwin.so (0) <0A636DAC-38BC-3247-8DC9-0CAC12A46EA8> /Users/USER/Library/Application Support/Blender/*/poly_spline.cpython-39-darwin.so\n 0x1371d5000 - 0x1371f0ff7 +base_spline.cpython-39-darwin.so (0) <88794D0B-ADCE-3BA5-98C0-C086F00ADEE5> /Users/USER/Library/Application Support/Blender/*/base_spline.cpython-39-darwin.so\n 0x137201000 - 0x137204ff3 +lists.cpython-39-darwin.so (0) <E77D5E8D-8E78-3A1F-9E46-8517A10E9C95> /Users/USER/Library/Application Support/Blender/*/lists.cpython-39-darwin.so\n 0x13720d000 - 0x137224ff7 +bezier_spline.cpython-39-darwin.so (0) <5BC510F7-B5B1-37B4-896C-F984BFB1A0E0> /Users/USER/Library/Application Support/Blender/*/bezier_spline.cpython-39-darwin.so\n 0x137235000 - 0x137244ffb +evaluation.cpython-39-darwin.so (0) <11EF0342-62BC-31AD-B5D5-F142D285783A> /Users/USER/Library/Application Support/Blender/*/evaluation.cpython-39-darwin.so\n 0x137251000 - 0x13725cff7 +falloff_base.cpython-39-darwin.so (0) <B2B0E82E-AB1D-3853-B738-25E244867DEE> /Users/USER/Library/Application Support/Blender/*/falloff_base.cpython-39-darwin.so\n 0x137269000 - 0x137270ff3 +types.cpython-39-darwin.so (0) <15BC7268-C248-3ED8-8C7C-9BA59C6DDD2C> /Users/USER/Library/Application Support/Blender/*/types.cpython-39-darwin.so\n 0x137279000 - 0x13727cff3 +pointers.cpython-39-darwin.so (0) <81D56538-531C-3354-AB33-64E16AA76A4E> /Users/USER/Library/Application Support/Blender/*/pointers.cpython-39-darwin.so\n 0x137285000 - 0x13728cffb +interpolation.cpython-39-darwin.so (0) <C0719841-7560-317F-A208-718717384FCA> /Users/USER/Library/Application Support/Blender/*/interpolation.cpython-39-darwin.so\n 0x137299000 - 0x1372acff7 +action_base.cpython-39-darwin.so (0) <731E6D43-5D55-33EC-9C36-C80F60A5D022> /Users/USER/Library/Application Support/Blender/*/action_base.cpython-39-darwin.so\n 0x1372bd000 - 0x1372c8fff +action_channels.cpython-39-darwin.so (0) <06EDE994-295B-3E5D-A3EF-305E798EEA5A> /Users/USER/Library/Application Support/Blender/*/action_channels.cpython-39-darwin.so\n 0x1372d5000 - 0x137304ff7 +action_types.cpython-39-darwin.so (0) <04EF5D15-C96A-32D9-86A8-6DF688A6BFAC> /Users/USER/Library/Application Support/Blender/*/action_types.cpython-39-darwin.so\n 0x1373e1000 - 0x1373e4fff +clamp.cpython-39-darwin.so (0) <4CCDC056-3EA8-3704-AFAE-14AD03B28CE1> /Users/USER/Library/Application Support/Blender/*/clamp.cpython-39-darwin.so\n 0x1373ed000 - 0x1373f0fff +limits.cpython-39-darwin.so (0) <1DA3E83A-370D-3728-8897-5E84B362B951> /Users/USER/Library/Application Support/Blender/*/limits.cpython-39-darwin.so\n 0x1373f9000 - 0x137404ff7 +presets.cpython-39-darwin.so (0) <C8BDBF43-615A-3915-9CC2-5A8B319C57DD> /Users/USER/Library/Application Support/Blender/*/presets.cpython-39-darwin.so\n 0x137411000 - 0x13741cff7 +shuffle.cpython-39-darwin.so (0) <9E99EB2A-F6D0-3DCD-A192-D4C83545ECAB> /Users/USER/Library/Application Support/Blender/*/shuffle.cpython-39-darwin.so\n 0x137429000 - 0x137430fff +reverse.cpython-39-darwin.so (0) <0EA55FD0-B8D2-325E-A6A2-138F8EEEC352> /Users/USER/Library/Application Support/Blender/*/reverse.cpython-39-darwin.so\n 0x13743d000 - 0x137448ff7 +repeat.cpython-39-darwin.so (0) <BB1B64EA-2E8D-3658-9308-5CA4BAC08E95> /Users/USER/Library/Application Support/Blender/*/repeat.cpython-39-darwin.so\n 0x137455000 - 0x137460fff +sample.cpython-39-darwin.so (0) <2E0C4CD1-70A8-3954-B250-3756776A2F44> /Users/USER/Library/Application Support/Blender/*/sample.cpython-39-darwin.so\n 0x13746d000 - 0x137470ff3 +splitmix64.cpython-39-darwin.so (0) <2EC93C0F-50D7-3C84-84B4-4FB307DD4CE6> /Users/USER/Library/Application Support/Blender/*/splitmix64.cpython-39-darwin.so\n 0x137479000 - 0x13747cff7 +xoshiro256starstar.cpython-39-darwin.so (0) <3ABDCC75-C43B-3FC7-99C4-DCDC34F94C4F> /Users/USER/Library/Application Support/Blender/*/xoshiro256starstar.cpython-39-darwin.so\n 0x137485000 - 0x137488ffb +xoshiro256plus.cpython-39-darwin.so (0) <023BAB16-4CFB-397B-859A-9B6F68BD84E9> /Users/USER/Library/Application Support/Blender/*/xoshiro256plus.cpython-39-darwin.so\n 0x137491000 - 0x1374a0ff3 +fill.cpython-39-darwin.so (0) <5EEC089D-2216-3396-9C63-1C276B280A27> /Users/USER/Library/Application Support/Blender/*/fill.cpython-39-darwin.so\n 0x1374ad000 - 0x1374b8ff7 +mask.cpython-39-darwin.so (0) <4ECF94A3-5297-35B9-B724-BA534CF2C812> /Users/USER/Library/Application Support/Blender/*/mask.cpython-39-darwin.so\n 0x1374c5000 - 0x1374d0ff7 +repeat_elements.cpython-39-darwin.so (0) <921A8F54-7C38-30A9-B01D-5CAB3209CF7C> /Users/USER/Library/Application Support/Blender/*/repeat_elements.cpython-39-darwin.so\n 0x1374dd000 - 0x1374e4ff3 +random.cpython-39-darwin.so (0) <F74901CE-DD24-36E4-8077-B719C970E4AB> /Users/USER/Library/Application Support/Blender/*/random.cpython-39-darwin.so\n 0x1374f1000 - 0x1374f8ffb +py_interface.cpython-39-darwin.so (0) <E4EC03CC-1BC1-39B5-8C80-2C3A3F2FA252> /Users/USER/Library/Application Support/Blender/*/py_interface.cpython-39-darwin.so\n 0x137501000 - 0x13750cff7 +symbol_string.cpython-39-darwin.so (0) <49057E1D-9E02-3C33-A831-62F5BCC3CD16> /Users/USER/Library/Application Support/Blender/*/symbol_string.cpython-39-darwin.so\n 0x137519000 - 0x137524ffb +apply_rules.cpython-39-darwin.so (0) <3BE61731-4F80-3B5D-9D9F-E8996491A02C> /Users/USER/Library/Application Support/Blender/*/apply_rules.cpython-39-darwin.so\n 0x137531000 - 0x13753cffb +geometry.cpython-39-darwin.so (0) <C76D121A-B84D-39F7-B6B8-F994277A9B08> /Users/USER/Library/Application Support/Blender/*/geometry.cpython-39-darwin.so\n 0x137549000 - 0x13755cff3 +parsing.cpython-39-darwin.so (0) <2DDA5AF6-F0F7-3914-911E-7678BE0D909D> /Users/USER/Library/Application Support/Blender/*/parsing.cpython-39-darwin.so\n 0x137565000 - 0x13756cffb +translation.cpython-39-darwin.so (0) <0BDDFA82-B616-3F79-84FE-E5F3544582C8> /Users/USER/Library/Application Support/Blender/*/translation.cpython-39-darwin.so\n 0x137579000 - 0x137580ffb +rotation.cpython-39-darwin.so (0) <10FF7C83-73BD-3403-B505-810385068CAA> /Users/USER/Library/Application Support/Blender/*/rotation.cpython-39-darwin.so\n 0x13758d000 - 0x137594ffb +scale.cpython-39-darwin.so (0) <2B619973-92BE-3BE9-9F89-86A42BE6031A> /Users/USER/Library/Application Support/Blender/*/scale.cpython-39-darwin.so\n 0x1375a1000 - 0x1375acff3 +points_scatter.cpython-39-darwin.so (0) <4CA00C82-EE20-31FA-AD4E-9BA8CE80FAAC> /Users/USER/Library/Application Support/Blender/*/points_scatter.cpython-39-darwin.so\n 0x1375b9000 - 0x1375c4fff +circle.cpython-39-darwin.so (0) <A91A5CBA-6578-382C-901B-14430BFE628D> /Users/USER/Library/Application Support/Blender/*/circle.cpython-39-darwin.so\n 0x1375d1000 - 0x1375dcff3 +cylinder.cpython-39-darwin.so (0) <82E62A4C-[D69](D69)-32B0-B3C9-676C7ADC013D> /Users/USER/Library/Application Support/Blender/*/cylinder.cpython-39-darwin.so\n 0x1375e9000 - 0x1375f4fff +find_shortest_path.cpython-39-darwin.so (0) <4443450D-B019-3EE5-8303-4B8344FDB5A6> /Users/USER/Library/Application Support/Blender/*/find_shortest_path.cpython-39-darwin.so\n 0x137601000 - 0x13760cff7 +line.cpython-39-darwin.so (0) <08684502-E4AC-3E0E-842F-C500F09B12B7> /Users/USER/Library/Application Support/Blender/*/line.cpython-39-darwin.so\n 0x137619000 - 0x13762cff3 +grid.cpython-39-darwin.so (0) <73234D3F-696A-3B0E-8E5E-D3688A6EB8FB> /Users/USER/Library/Application Support/Blender/*/grid.cpython-39-darwin.so\n 0x13763d000 - 0x137654ffb +loft.cpython-39-darwin.so (0) <0B436912-1053-3204-83A3-9D5E84D2AE85> /Users/USER/Library/Application Support/Blender/*/loft.cpython-39-darwin.so\n 0x1376a5000 - 0x1376b0ffb +revolve.cpython-39-darwin.so (0) <C3EAE6F5-[D96](D96)-389D-8453-0CC9D0547C0A> /Users/USER/Library/Application Support/Blender/*/revolve.cpython-39-darwin.so\n 0x1376bd000 - 0x1376c8ffb +perlin_noise.cpython-39-darwin.so (0) <BFFF2C51-9C1F-3568-82C6-6AE86FD0B2F5> /Users/USER/Library/Application Support/Blender/*/perlin_noise.cpython-39-darwin.so\n 0x1376d5000 - 0x1376e0ff3 +random.cpython-39-darwin.so (0) <C841D12E-8238-395B-978B-422F4A885959> /Users/USER/Library/Application Support/Blender/*/random.cpython-39-darwin.so\n 0x1376ed000 - 0x1376f8ff3 +rotation_and_direction.cpython-39-darwin.so (0) <8B34DA4E-E2A7-3CFB-A9A6-0FB00F9E2A15> /Users/USER/Library/Application Support/Blender/*/rotation_and_direction.cpython-39-darwin.so\n 0x137705000 - 0x137710ff7 +bevel_poly_spline.cpython-39-darwin.so (0) <3D398CE4-72F2-3DE7-AB6C-F552E836DE83> /Users/USER/Library/Application Support/Blender/*/bevel_poly_spline.cpython-39-darwin.so\n 0x13775d000 - 0x1377b0ff7 +convert.cpython-39-darwin.so (0) <73467100-63D2-32EC-9064-238395AAEB85> /Users/USER/Library/Application Support/Blender/*/convert.cpython-39-darwin.so\n 0x137845000 - 0x137850ff7 +to_blender.cpython-39-darwin.so (0) <9B6F5BE6-0E63-3920-883E-54883C7813FE> /Users/USER/Library/Application Support/Blender/*/to_blender.cpython-39-darwin.so\n 0x137859000 - 0x137860ff7 +c_utils.cpython-39-darwin.so (0) <2B65E84B-FB21-3BFE-8962-4E9F1097DDCF> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x13786d000 - 0x137878ff3 +mesh_indices.cpython-39-darwin.so (0) <59960025-7C2E-3BF4-A4ED-5A8C89F206FF> /Users/USER/Library/Application Support/Blender/*/mesh_indices.cpython-39-darwin.so\n 0x1378c5000 - 0x1379e0ff7 +wrapper.cpython-39-darwin.so (0) <25A09BF8-6218-3996-A2C3-E7579FCB936A> /Users/USER/Library/Application Support/Blender/*/wrapper.cpython-39-darwin.so\n 0x1379f9000 - 0x1379fbfff +mmap.cpython-39-darwin.so (0) <754A12FC-F23E-3C53-96AB-BF5A9364B238> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/mmap.cpython-39-darwin.so\n 0x137a44000 - 0x137a47ff3 +color.cpython-39-darwin.so (0) <39BC6F3E-DAE9-35CF-804F-8CAD3B68F4A6> /Users/USER/Library/Application Support/Blender/*/color.cpython-39-darwin.so\n 0x137a50000 - 0x137a53ffb +euler.cpython-39-darwin.so (0) <87B639A3-BD1E-35F1-8339-772522B8D0E8> /Users/USER/Library/Application Support/Blender/*/euler.cpython-39-darwin.so\n 0x137a5c000 - 0x137a6fffb +action_from_object.cpython-39-darwin.so (0) <D4FC0AD8-EC06-366B-B9A1-5561EF4F19C8> /Users/USER/Library/Application Support/Blender/*/action_from_object.cpython-39-darwin.so\n 0x137a80000 - 0x137a93ff3 +chain_actions.cpython-39-darwin.so (0) <42A76829-BDB8-3933-BF64-F835B74538E5> /Users/USER/Library/Application Support/Blender/*/chain_actions.cpython-39-darwin.so\n 0x137aa4000 - 0x137aabffb +delay_action.cpython-39-darwin.so (0) <49A865E7-8C09-3812-9246-0505F38F78B1> /Users/USER/Library/Application Support/Blender/*/delay_action.cpython-39-darwin.so\n 0x137ab4000 - 0x137abffff +follow_spline_action.cpython-39-darwin.so (0) <AD563B97-0D2B-34EF-A234-0018E9982E8C> /Users/USER/Library/Application Support/Blender/*/follow_spline_action.cpython-39-darwin.so\n 0x137acc000 - 0x137ae3ff7 +object_action_output.cpython-39-darwin.so (0) <AFEB5585-4FB9-32EC-A89D-A68BD66F69D3> /Users/USER/Library/Application Support/Blender/*/object_action_output.cpython-39-darwin.so\n 0x137af4000 - 0x137b07ffb +overlay_action.cpython-39-darwin.so (0) <BB7FB811-ACC2-367F-8D1D-E4C66EB58A78> /Users/USER/Library/Application Support/Blender/*/overlay_action.cpython-39-darwin.so\n 0x137b18000 - 0x137b2ffff +wiggle_action.cpython-39-darwin.so (0) <67F48367-7DB5-307F-BD70-C9C8E3C4A787> /Users/USER/Library/Application Support/Blender/*/wiggle_action.cpython-39-darwin.so\n 0x137b40000 - 0x137b47ffb +c_utils.cpython-39-darwin.so (0) <B68D4BEF-E966-3F84-8F1E-4552C425868B> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x137b54000 - 0x137b5bff3 +c_utils.cpython-39-darwin.so (0) <00EE1D82-8942-3D87-BE4B-8DB273FB7B75> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x137b68000 - 0x137b77fff +c_utils.cpython-39-darwin.so (0) <DBFBF131-8399-3844-9629-72C34CC1CD7F> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x137bc4000 - 0x137bcffff +constant_falloff.cpython-39-darwin.so (0) <7442913E-9B88-3D8B-BCDF-1F4D15B36755> /Users/USER/Library/Application Support/Blender/*/constant_falloff.cpython-39-darwin.so\n 0x137bdc000 - 0x137be7ff7 +custom_falloff.cpython-39-darwin.so (0) <DAD43877-5EE1-378E-8B4D-16D8E9939A1B> /Users/USER/Library/Application Support/Blender/*/custom_falloff.cpython-39-darwin.so\n 0x137bf4000 - 0x137bffff3 +delay_falloff.cpython-39-darwin.so (0) <DD9D3431-B287-3DDB-9497-C159C1C749B0> /Users/USER/Library/Application Support/Blender/*/delay_falloff.cpython-39-darwin.so\n 0x137c0c000 - 0x137c17ff3 +interpolate_falloff.cpython-39-darwin.so (0) <5B6FEC58-1D13-3D9C-B9DA-BF5A2D165437> /Users/USER/Library/Application Support/Blender/*/interpolate_falloff.cpython-39-darwin.so\n 0x137c24000 - 0x137c33ffb +directional_falloff.cpython-39-darwin.so (0) <301D638C-E1CA-3D49-83AB-32EA8A327F95> /Users/USER/Library/Application Support/Blender/*/directional_falloff.cpython-39-darwin.so\n 0x137c44000 - 0x137c57ff3 +evaluate_falloff.cpython-39-darwin.so (0) <56FE3225-2C2D-3FD0-A550-5D817F89586F> /Users/USER/Library/Application Support/Blender/*/evaluate_falloff.cpython-39-darwin.so\n 0x137c68000 - 0x137c77ff7 +fade_falloff.cpython-39-darwin.so (0) <02114EDE-6DF2-3305-8334-8FD2FA9A7112> /Users/USER/Library/Application Support/Blender/*/fade_falloff.cpython-39-darwin.so\n 0x137c88000 - 0x137c97ff3 +index_mask_falloff.cpython-39-darwin.so (0) <227374E7-21D9-37A6-9A73-543D335E281E> /Users/USER/Library/Application Support/Blender/*/index_mask_falloff.cpython-39-darwin.so\n 0x137ca8000 - 0x137cb3fff +interpolate_list_falloff.cpython-39-darwin.so (0) <6F2270C3-E689-3FDA-AADF-8620D6EA15BF> /Users/USER/Library/Application Support/Blender/*/interpolate_list_falloff.cpython-39-darwin.so\n 0x137cc0000 - 0x137ccfff7 +remap_falloff.cpython-39-darwin.so (0) <AECC6D7C-FD3A-309A-B2F6-97E232ED894B> /Users/USER/Library/Application Support/Blender/*/remap_falloff.cpython-39-darwin.so\n 0x137cdc000 - 0x137cebffb +mesh_falloff.cpython-39-darwin.so (0) <4AE52DE6-A185-3861-93EA-7A94E0AE7C9F> /Users/USER/Library/Application Support/Blender/*/mesh_falloff.cpython-39-darwin.so\n 0x137cf8000 - 0x137d13ffb +mix_falloffs.cpython-39-darwin.so (0) <3C7F845D-40EF-3FA9-BEBA-56AD683A29CA> /Users/USER/Library/Application Support/Blender/*/mix_falloffs.cpython-39-darwin.so\n 0x137d2c000 - 0x137d37ff7 +noise_falloff.cpython-39-darwin.so (0) <696A4AEB-B94D-3EF1-8976-4EBC00D2C911> /Users/USER/Library/Application Support/Blender/*/noise_falloff.cpython-39-darwin.so\n 0x137d48000 - 0x137d63ff3 +object_controller_falloff.cpython-39-darwin.so (0) <C235F6EB-D7FC-3D8E-82DA-B5081885BEE5> /Users/USER/Library/Application Support/Blender/*/object_controller_falloff.cpython-39-darwin.so\n 0x137d74000 - 0x137d7fffb +radial_falloff.cpython-39-darwin.so (0) <94E16451-E008-3E5B-A527-89DB50CB82F2> /Users/USER/Library/Application Support/Blender/*/radial_falloff.cpython-39-darwin.so\n 0x137d8c000 - 0x137d97ffb +point_distance_falloff.cpython-39-darwin.so (0) <C157B90F-AE52-3B0F-ABB3-EBD49E0FE470> /Users/USER/Library/Application Support/Blender/*/point_distance_falloff.cpython-39-darwin.so\n 0x137da4000 - 0x137dafffb +random_falloff.cpython-39-darwin.so (0) <8D7ABC48-FEB5-3CE6-AA7D-543D23F49EDF> /Users/USER/Library/Application Support/Blender/*/random_falloff.cpython-39-darwin.so\n 0x137dbc000 - 0x137ddbfff +sound_falloff.cpython-39-darwin.so (0) <31829F9E-C7D4-3054-BCCA-CBE14F585C3C> /Users/USER/Library/Application Support/Blender/*/sound_falloff.cpython-39-darwin.so\n 0x137df4000 - 0x137e0ffff +spline_falloff.cpython-39-darwin.so (0) <F8706164-3DC0-3445-A063-C25F4ABF1187> /Users/USER/Library/Application Support/Blender/*/spline_falloff.cpython-39-darwin.so\n 0x137e20000 - 0x137e2bff7 +wiggle_falloff.cpython-39-darwin.so (0) <54578CB3-9AB8-3C39-A901-BC4C7FFA7AA2> /Users/USER/Library/Application Support/Blender/*/wiggle_falloff.cpython-39-darwin.so\n 0x137e78000 - 0x137e83ffb +c_utils.cpython-39-darwin.so (0) <8BDD914A-5C20-35AA-AF1C-2B5DED2DE20E> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x137e90000 - 0x137ea3ff7 +c_utils.cpython-39-darwin.so (0) <291A3A79-FDD5-32DB-940D-2CD66F72872B> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x137ef4000 - 0x137f03fff +c_utils.cpython-39-darwin.so (0) <F834A636-E819-3D16-B686-E90EC0CE7C33> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x137f10000 - 0x137f1bff7 +c_utils.cpython-39-darwin.so (0) <1BD53042-8EDB-3100-91F2-9EBB0E0C65AE> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x137fa8000 - 0x137fbfff3 +c_utils.cpython-39-darwin.so (0) <3F6709F2-79BA-3A05-8770-B8B82244FCD4> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x137fd0000 - 0x137ffbffb +distribute_matrices.cpython-39-darwin.so (0) <BB894326-61FD-373D-B3A8-22F05F8FDE1C> /Users/USER/Library/Application Support/Blender/*/distribute_matrices.cpython-39-darwin.so\n 0x138018000 - 0x138043ff3 +c_utils.cpython-39-darwin.so (0) <152B1697-7E46-334F-85D5-8E6031B0BFE5> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x1380d8000 - 0x1380ebff7 +offset_vector.cpython-39-darwin.so (0) <A9D620AD-4076-3C08-8C31-4ABDD364CE13> /Users/USER/Library/Application Support/Blender/*/offset_vector.cpython-39-darwin.so\n 0x1380fc000 - 0x13811ffff +float_math.cpython-39-darwin.so (0) <11479342-6C19-33D4-A8CD-1B9C51F80724> /Users/USER/Library/Application Support/Blender/*/float_math.cpython-39-darwin.so\n 0x13817c000 - 0x138197ffb +vector_math.cpython-39-darwin.so (0) <79E17C3E-B0EB-3752-942C-9502E6060CDD> /Users/USER/Library/Application Support/Blender/*/vector_math.cpython-39-darwin.so\n 0x1381ac000 - 0x1381bfff7 +object_matrix_output.cpython-39-darwin.so (0) <984F048D-91D7-3632-BB8E-1D1D82A3CEEE> /Users/USER/Library/Application Support/Blender/*/object_matrix_output.cpython-39-darwin.so\n 0x138210000 - 0x138217fff +c_utils.cpython-39-darwin.so (0) <D5EFC540-37E0-31FB-97D6-DFF8E96C2975> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x138224000 - 0x138233ff7 +c_utils.cpython-39-darwin.so (0) <99DD5F9A-59F5-3D4F-951D-1FCDD888C3B1> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x138280000 - 0x13828bff3 +c_utils.cpython-39-darwin.so (0) <20CBB9AA-7EB1-37C3-AB47-C40BA9500A8F> /Users/USER/Library/Application Support/Blender/*/c_utils.cpython-39-darwin.so\n 0x138298000 - 0x1382a3ff7 +splines_from_edges_utils.cpython-39-darwin.so (0) <6D182999-D30E-3769-8EE4-692BE446A8A8> /Users/USER/Library/Application Support/Blender/*/splines_from_edges_utils.cpython-39-darwin.so\n 0x138370000 - 0x138372ffb +_lsprof.cpython-39-darwin.so (0) <17BF94D9-6D3F-3063-A8E4-F99CAAEE64A0> /Applications/Blender 3.app/Contents/Resources/3.0/python/lib/python3.9/lib-dynload/_lsprof.cpython-39-darwin.so\n 0x138ee4000 - 0x138ee6ff3 com.apple.CloudDocsFileProvider (1.0 - 698.20) <E43BCFE0-F68C-3434-9A56-4F61BEE00ED2> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/CloudDocsFileProvider.bundle/Contents/MacOS/CloudDocsFileProvider\n 0x138eef000 - 0x138ef2fff com.apple.FileProviderOverride (304.141.1 - 304.141.1) <58E74E38-FA6A-3D1E-8EC7-F7B052FE3DDC> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FileProviderOverride.bundle/Contents/MacOS/FileProviderOverride\n 0x138f91000 - 0x138fa8ffb com.apple.findersync.fileprovideroverride.FinderSyncCollaborationFileProviderOverride (1.0 - 1298.7.1) <1911451B-5BA5-3A08-AB9F-2729A55BDE38> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride\n 0x7fff21ef1000 - 0x7fff2213eff8 com.apple.RawCamera.bundle (9.02.0 - 1350.30) <5337D338-FB27-3B70-91C8-096357BEFAC2> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff24822000 - 0x7fff24d1fff7 com.apple.driver.AppleIntelHD4000GraphicsGLDriver (14.7.20 - 14.0.7) <7C755611-B8FD-37AE-8B39-5B01F7F8673E> /System/Library/Extensions/AppleIntelHD4000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD4000GraphicsGLDriver\n 0x7fff24d20000 - 0x7fff24d9fff6 com.apple.driver.AppleIntelHD4000GraphicsMTLDriver (14.7.20 - 14.0.7) <CA4CF416-1AF8-3619-959B-5A3B4EDD551F> /System/Library/Extensions/AppleIntelHD4000GraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelHD4000GraphicsMTLDriver\n 0x7fff2aa86000 - 0x7fff2aa86fff com.apple.Accelerate (1.11 - Accelerate 1.11) <C1FB2338-2D52-3884-BED3-071A82B1FD77> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff2aa87000 - 0x7fff2aa9eff7 libCGInterfaces.dylib (524.2.1) <69118118-1CEC-3019-A36E-3EC2FF1CAD8F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff2aa9f000 - 0x7fff2b33afcf com.apple.vImage (8.1 - 524.2.1) <4B6AB2C1-7CF5-3FDA-AC1C-04E531AB9BCE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff2b33b000 - 0x7fff2b4d0fef libBLAS.dylib (1303.60.1) <C157903D-417A-322B-916E-DDCFE2AF97EE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff2b4d1000 - 0x7fff2b812fff libBNNS.dylib (144.100.2) <69FA0C4F-B59D-374A-9DCF-E9FA79F332FD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff2b813000 - 0x7fff2bbbafff libLAPACK.dylib (1303.60.1) <6FEC8434-0C35-3528-A3DE-E3C78A748B6C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff2bbbb000 - 0x7fff2bbd0ffc libLinearAlgebra.dylib (1303.60.1) <AAC1A8DA-0B44-3D52-A03F-1DFED19D33BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff2bbd1000 - 0x7fff2bbd6ff3 libQuadrature.dylib (7) <371F36A7-B12F-363E-8955-F24F7C2048F6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff2bbd7000 - 0x7fff2bc47fff libSparse.dylib (103) <B8A10D0C-4577-343D-B310-A3E81265D107> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff2bc48000 - 0x7fff2bc5aff7 libSparseBLAS.dylib (1303.60.1) <CFFEAA75-99FB-369E-80A1-4BC73ADEBEA9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff2bc5b000 - 0x7fff2bdedfe3 libvDSP.dylib (735.140.1) <1586D162-55FD-3EC0-AFC7-975EAE2D0DD6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff2bdee000 - 0x7fff2bf6cfe7 libvMisc.dylib (735.140.1) <61CF1106-41C2-3971-9187-BD1D53C00343> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff2bf6d000 - 0x7fff2bf6dfff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <4686AE53-FD05-302C-AC20-C014EFC2305F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff2bf6e000 - 0x7fff2bfcdff0 com.apple.Accounts (113 - 113) <E2438070-30AB-3B89-AE63-1E485B92D108> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts\n 0x7fff2c117000 - 0x7fff2ced5ff4 com.apple.AppKit (6.9 - 1894.60.107) <D955876A-483C-3E04-94B2-4A2A574D64E0> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff2cf25000 - 0x7fff2cf25fff com.apple.ApplicationServices (48 - 50) <5DCBE58B-F7AD-39FF-BAB8-1B300C6DE8F5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff2cf26000 - 0x7fff2cf91fff com.apple.ApplicationServices.ATS (377 - 493.0.4.1) <87EA5DE1-506A-39FD-88BE-D8A3416C9012> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff2d02a000 - 0x7fff2d068ff0 libFontRegistry.dylib (274.0.5.1) <F3461C05-0370-359B-9F03-5C1C1F7763EC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff2d0c3000 - 0x7fff2d0f2fff com.apple.ATSUI (1.0 - 1) <5F513967-DDD7-3F22-AD14-8A38ABD9F2D0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI\n 0x7fff2d0f3000 - 0x7fff2d0f7ffb com.apple.ColorSyncLegacy (4.13.0 - 1) <1616B44A-FCBC-3B11-A6CB-8B40D4DE27AE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff2d191000 - 0x7fff2d1e8ffa com.apple.HIServices (1.22 - 676) <14DF4D42-E24D-3EBD-9A9D-93124D8D6AA1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff2d1e9000 - 0x7fff2d1f7fff com.apple.LangAnalysis (1.7.0 - 1.7.0) <01B8B6B3-E2C3-3607-B34A-8283A7E0E924> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff2d1f8000 - 0x7fff2d23dffa com.apple.print.framework.PrintCore (15.4 - 516.2) <437BCF12-48D2-3770-8BC9-567718FB1BCA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff2d23e000 - 0x7fff2d248ff7 com.apple.QD (4.0 - 413) <27A36D07-B5E9-32E6-87B6-3127F260F48D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff2d249000 - 0x7fff2d256ffc com.apple.speech.synthesis.framework (9.0.24 - 9.0.24) <75344F8F-32CA-3558-B4E6-F56D498250E4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff2d257000 - 0x7fff2d338ff2 com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <302BD446-B8AF-3D96-8A4E-9E636608AF75> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff2d33a000 - 0x7fff2d33afff com.apple.audio.units.AudioUnit (1.14 - 1.14) <BAD748CE-87DA-3DF8-AA04-8C3A2B6DF6A6> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff2d6d1000 - 0x7fff2da5fffa com.apple.CFNetwork (1128.1 - 1128.1) <04F37E21-8AC6-35BF-8D2C-8ED954B09026> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff2dadb000 - 0x7fff2dadbfff com.apple.Carbon (160 - 162) <057B03E9-2B72-3F1F-A6FE-30E371063A85> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff2dadc000 - 0x7fff2dadfff3 com.apple.CommonPanels (1.2.6 - 101) <9F6E13D9-374B-386F-8E15-FDD6CE967859> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff2dae0000 - 0x7fff2ddd4ff3 com.apple.HIToolbox (2.1.1 - 994.7) <000A63E3-7A5B-3EFC-ACC8-2F8B825C4748> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff2ddd5000 - 0x7fff2ddd8ff3 com.apple.help (1.3.8 - 71) <36483951-6F3E-3F7E-8A5B-191C2357EF17> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff2ddd9000 - 0x7fff2dddeff7 com.apple.ImageCapture (9.0 - 1600.65.1) <19E8B178-4C4D-3779-8815-E905310F20EF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff2dddf000 - 0x7fff2dddffff com.apple.ink.framework (10.15 - 227) <284507AE-EF47-3ABC-86A4-669243DB1D33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff2dde0000 - 0x7fff2ddfaffa com.apple.openscripting (1.7 - 185.1) <B6E28747-5FC7-3461-8A71-864A969ED022> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff2de1b000 - 0x7fff2de1bfff com.apple.print.framework.Print (15 - 271) <0D9FB08F-EA87-3BE7-821B-C61BA5601050> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff2de1c000 - 0x7fff2de1eff7 com.apple.securityhi (9.0 - 55008) <390C6FAA-99BF-3924-9180-9EAE41D9C6BE> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff2de1f000 - 0x7fff2de25fff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <9614A01E-8303-3422-A3BA-6CE27540E09A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff2dfbf000 - 0x7fff2dfbffff com.apple.Cocoa (6.11 - 23) <791A1DB8-2D84-325C-9409-985C02C510ED> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff2dfcd000 - 0x7fff2e0c3fff com.apple.ColorSync (4.13.0 - 3394.11) <B0DE6D9E-3C1D-3121-A1B9-769443238BEF> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff2e3ae000 - 0x7fff2e8b7ffb com.apple.audio.CoreAudio (5.0 - 5.0) <47923B12-3D14-328A-9C86-27A3A2A73068> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff2e90a000 - 0x7fff2e942fff com.apple.CoreBluetooth (1.0 - 1) <23DBB313-A082-3C08-8E1F-2D31EE4247EF> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff2e943000 - 0x7fff2ed3eff8 com.apple.CoreData (120 - 977.3) <CEAA4BC1-62AB-3702-B790-82A55EA10302> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff2ed3f000 - 0x7fff2ee71ff6 com.apple.CoreDisplay (1.0 - 186.6.15) <213D7011-8180-3CF4-9BE7-FB8F75DCDB95> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff2ee72000 - 0x7fff2f2f3ff6 com.apple.CoreFoundation (6.9 - 1678.101) <41A8276A-02BD-3369-AF6D-A3277D586182> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff2f2f5000 - 0x7fff2f98dff0 com.apple.CoreGraphics (2.0 - 1355.24) <9B167C47-1FDB-3D44-93D0-64CC7B30AB2A> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff2f99b000 - 0x7fff2fcf6ff0 com.apple.CoreImage (15.0.0 - 940.9) <69361069-01AB-342E-862B-73A74271A765> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff300b7000 - 0x7fff30192ffc com.apple.CoreMedia (1.0 - 2625.9.4.1) <09A2E0F7-4448-35A4-87B6-C250F4EA415E> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff3027f000 - 0x7fff3027ffff com.apple.CoreServices (1069.28 - 1069.28) <72D55A31-EFDB-3E6B-8B12-E91E059A4540> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff30280000 - 0x7fff30305fff com.apple.AE (838.1 - 838.1) <2E5FD5AE-8A7F-353F-9BD1-0241F3586181> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff30306000 - 0x7fff305e7ff7 com.apple.CoreServices.CarbonCore (1217 - 1217) <BE379206-99FA-30CD-8391-2708473A633F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff305e8000 - 0x7fff30635ffd com.apple.DictionaryServices (1.2 - 323.6) <26B70C82-25BC-353A-858F-945B14C803A2> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff30636000 - 0x7fff3063eff7 com.apple.CoreServices.FSEvents (1268.100.1 - 1268.100.1) <FC84DB48-A3CE-30F7-A918-B3587731ACC7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff3063f000 - 0x7fff3087afff com.apple.LaunchServices (1069.28 - 1069.28) <C8A1268A-ADA9-31E9-A5FE-63C15A4B5D3B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff3087b000 - 0x7fff30913ff9 com.apple.Metadata (10.7.0 - 2076.7.1) <3FBA1665-4F76-3403-9C87-E120D53D40FB> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff30914000 - 0x7fff30941fff com.apple.CoreServices.OSServices (1069.28 - 1069.28) <1F3E8B56-E660-332C-9D01-E517729EA970> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff30942000 - 0x7fff309a9fff com.apple.SearchKit (1.4.1 - 1.4.1) <2C5E1D85-E8B1-3DC5-91B9-E3EDB48E9369> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff309aa000 - 0x7fff309ceff5 com.apple.coreservices.SharedFileList (131.4 - 131.4) <02DE0D56-E371-3EF5-9BC1-FA435451B412> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff30cf3000 - 0x7fff30eaaffc com.apple.CoreText (643.1.5.7 - 643.1.5.7) <34D12C1B-541D-3796-BDD8-D40EE509CD5F> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff30eab000 - 0x7fff30eefffb com.apple.CoreVideo (1.8 - 344.3) <5314E70D-325F-3E98-99FC-00FDF520747E> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff30ef0000 - 0x7fff30f7dffc com.apple.framework.CoreWLAN (13.0 - 1601.2) <6223BFD5-[D451](D451)-3DE9-90F6-F609AC0B0027> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff31139000 - 0x7fff31144ff7 com.apple.DirectoryService.Framework (10.15 - 220.40.1) <6EACB7D0-A013-3D2B-93D2-5113F7C2559D> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService\n 0x7fff31145000 - 0x7fff311efff0 com.apple.DiscRecording (9.0.3 - 9030.4.5) <BCF3AFB0-6E1A-3F28-A575-1FD2D74E7C19> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording\n 0x7fff31214000 - 0x7fff3121afff com.apple.DiskArbitration (2.7 - 2.7) <3C4C5E39-0F17-394F-AD6F-07E60728B7A4> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff3140f000 - 0x7fff3153eff6 com.apple.FileProvider (304.141.1 - 304.141.1) <4D593263-0D4D-3D60-9E7D-023185B1756B> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider\n 0x7fff31553000 - 0x7fff31555ff3 com.apple.ForceFeedback (1.0.6 - 1.0.6) <9B324178-4FAA-3686-9E01-634607F38493> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff31556000 - 0x7fff3191bff7 com.apple.Foundation (6.9 - 1678.101) <3C4F5EDA-E6D2-398D-A0FF-8B16200BC0CC> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff31988000 - 0x7fff319d8ff7 com.apple.GSS (4.0 - 2.0) <95568BAB-7F1A-3E1C-BD5A-78A8B4338EDA> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff31b15000 - 0x7fff31c29ff3 com.apple.Bluetooth (7.0.6 - 7.0.6f8) <EF3F4D14-258C-3241-BB9F-BCEFF622D6D0> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff31c8f000 - 0x7fff31d33ff3 com.apple.framework.IOKit (2.0.2 - 1726.148.1) <0A9D244C-AECC-3D29-86DE-4F3B04F8DD25> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff31d35000 - 0x7fff31d46ffb com.apple.IOSurface (269.11 - 269.11) <BCD744D4-E17E-3C2E-B69C-F69C789892E9> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff31dc5000 - 0x7fff31f25ff6 com.apple.ImageIO.framework (3.3.0 - 1976.12.1) <A35EF001-9F5E-3C0C-AB42-FB9642CB5D5E> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff31f26000 - 0x7fff31f29fff libGIF.dylib (1976.12.1) <D9A68370-AB11-3BF0-9402-0F81CA8302AC> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff31f2a000 - 0x7fff31fe3ff7 libJP2.dylib (1976.12.1) <F5505138-7C8F-3D2A-ACEE-2E537CF9AC52> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff31fe4000 - 0x7fff32008ff7 libJPEG.dylib (1976.12.1) <9FBF5E3F-5F33-3A3B-ADC5-8A94C3E9F22D> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff32286000 - 0x7fff322a0ff7 libPng.dylib (1976.12.1) <3DE5DE3C-6A8F-3C8A-A173-66D04FEAAC70> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff322a1000 - 0x7fff322a2fff libRadiance.dylib (1976.12.1) <E6AB86A1-AD17-3737-96BC-E821DBC2A929> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff322a3000 - 0x7fff322e9ff7 libTIFF.dylib (1976.12.1) <F2696C77-AFA5-3FBE-A420-69EBD2236834> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff3384b000 - 0x7fff3385dff3 com.apple.Kerberos (3.0 - 1) <03BB492B-016E-37BF-B020-39C2CF7487FE> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff3385e000 - 0x7fff3385efff libHeimdalProxy.dylib (77) <0A2905EE-9533-3345-AF9B-AAC71513BDFD> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib\n 0x7fff3385f000 - 0x7fff33895ff7 com.apple.LDAPFramework (2.4.28 - 194.5) <45AD36CB-[D311](D311)-32A2-843C-ED6350A59B5A> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP\n 0x7fff33bf0000 - 0x7fff33bfaffb com.apple.MediaAccessibility (1.0 - 125.1) <98065EA1-3484-3A5A-B05C-D2FABED8CEA4> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff33cc6000 - 0x7fff34413ff2 com.apple.MediaToolbox (1.0 - 2625.9.4.1) <C894387C-[D72](D72)-3BD1-A6FE-A13CAF0BB874> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff34415000 - 0x7fff344dffff com.apple.Metal (212.8 - 212.8) <98C944D6-62C8-355E-90F8-C1CA2429EF24> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff344fc000 - 0x7fff34539ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <7EBAC15D-7837-395D-B405-1E29F7DA68FA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff3453a000 - 0x7fff345c4fe2 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <B424FE0C-6E90-3BFA-A6E7-DD86C735AE90> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff345c5000 - 0x7fff345eaff4 com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <02006D92-E2AB-3892-A96B-37F6520C19BA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff345eb000 - 0x7fff34600ffb com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <CAA5A368-DB71-34F6-AEF9-27A8BC298F53> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray\n 0x7fff34601000 - 0x7fff3475fffc com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <05612E06-50CB-318F-9F8E-EF4D49FAB3B0> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff34760000 - 0x7fff347afff4 com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B0B591F8-6875-351E-867F-8EB3CD38CD52> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff347b0000 - 0x7fff347b1ff5 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <F2921F9A-3041-3495-878D-64134267B847> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff3585e000 - 0x7fff3586affe com.apple.NetFS (6.0 - 4.0) <57CABC68-0585-3989-9161-157DBB544B82> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff3586b000 - 0x7fff359c2ff3 com.apple.Network (1.0 - 1) <4A0F3B93-4D23-3E74-9A3D-AD19E9C0E59E> /System/Library/Frameworks/Network.framework/Versions/A/Network\n 0x7fff35cae000 - 0x7fff35cd0fff com.apple.audio.OpenAL (1.8 - 1.8) <6D66C5D7-8410-35B7-B06E-3BE56E0A708E> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff383eb000 - 0x7fff383f3ff7 libcldcpuengine.dylib (2.14) <D20EF7DF-8508-3707-A9B3-B7D8190971F5> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff383f4000 - 0x7fff3844cfff com.apple.opencl (3.5 - 3.5) <BEE2BF96-BB35-3444-9BCE-46CBAD05EC2E> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff3844d000 - 0x7fff38469fff com.apple.CFOpenDirectory (10.15 - 220.40.1) <7E6C88EB-3DD9-32B0-81FC-179552834FA9> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff3846a000 - 0x7fff38475ffd com.apple.OpenDirectory (10.15 - 220.40.1) <4A92D8D8-A9E5-3A9C-942F-28576F6BCDF5> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff38ddb000 - 0x7fff38dddfff libCVMSPluginSupport.dylib (17.10.22) <2A3CAB2E-CF43-36BF-BDB1-343D7E92D71B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff38dde000 - 0x7fff38de3fff libCoreFSCache.dylib (176.20) <A9877F89-92E9-3139-BEF4-C45B2A5F3B76> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff38de4000 - 0x7fff38de8fff libCoreVMClient.dylib (176.20) <9741DE63-28A6-3B0C-858D-9D653355F1AB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff38de9000 - 0x7fff38df1ff7 libGFXShared.dylib (17.10.22) <C8ABDE91-E05F-341A-BBB0-0C583F6AA91F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff38df2000 - 0x7fff38dfcfff libGL.dylib (17.10.22) <F9B81B8B-659F-3182-89A3-DC1F06D5BF86> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff38dfd000 - 0x7fff38e31ff7 libGLImage.dylib (17.10.22) <999AA7FA-C130-37AA-843B-4662A4F68DD2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff38e32000 - 0x7fff38fc6ff7 libGLProgrammability.dylib (17.10.22) <E94C9337-AE83-3FA8-BEDA-DDFBC1CE03DF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff38fc7000 - 0x7fff39003fff libGLU.dylib (17.10.22) <0E15537A-03FB-32DF-B850-5D3E25DA4627> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff39a3f000 - 0x7fff39a4eff7 com.apple.opengl (17.10.22 - 17.10.22) <251345CF-9DE1-342A-8710-2543AEA59B18> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff39a4f000 - 0x7fff39bc8fff GLEngine (17.10.22) <F17DB254-EE87-3163-9EFE-4B65502B9A83> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff39bc9000 - 0x7fff39bf1fff GLRendererFloat (17.10.22) <5E086183-D7E6-36A9-ABB4-D868CCF09F3B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff3aa0c000 - 0x7fff3ac8fffb com.apple.QuartzCore (1.11 - 841.6) <3EB993C4-261C-36C6-9C86-64A9B73EA2D4> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff3b813000 - 0x7fff3bb5eff9 com.apple.security (7.0 - 59306.140.11) <3B46FC31-708A-3526-B888-BB7C1A9FBD98> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff3bb5f000 - 0x7fff3bbe7ffb com.apple.securityfoundation (6.0 - 55236.60.1) <954B6238-07CB-3357-BC4F-AE827DD3F9E3> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff3bc16000 - 0x7fff3bc1aff8 com.apple.xpc.ServiceManagement (1.0 - 1) <055976F5-69DF-3846-B7CC-D72FA09D1A98> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff3c8c6000 - 0x7fff3c940ff7 com.apple.SystemConfiguration (1.19 - 1.19) <D3494EFE-F392-379E-B21C-0F1B094ECE77> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff3cbc0000 - 0x7fff3cf43ff4 com.apple.VideoToolbox (1.0 - 2625.9.4.1) <FC56B4CA-7FCA-3E62-AA0A-A667B259C4A2> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff408b0000 - 0x7fff40975fe7 com.apple.APFS (1412.141.2 - 1412.141.2) <100E8447-2563-3E1C-8B65-5A3910CD55AD> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff41a8a000 - 0x7fff41a8bff1 com.apple.AggregateDictionary (1.0 - 1) <95A291F5-B69F-3C37-9483-C3B2EBF52AC1> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff42025000 - 0x7fff42042ff4 com.apple.AppContainer (4.0 - 448.100.6) <87CEE13C-8585-3EFB-92CD-0852DFF0921B> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer\n 0x7fff42097000 - 0x7fff420a5ff7 com.apple.AppSandbox (4.0 - 448.100.6) <0F49AA04-3400-349A-9096-6D4D7ED61027> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox\n 0x7fff42521000 - 0x7fff42545ffb com.apple.framework.Apple80211 (13.0 - 1610.1) <D94E03E8-4C38-3B2F-8DF4-473ACC5A7D71> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff42803000 - 0x7fff42812fd7 com.apple.AppleFSCompression (119.100.1 - 1.0) <466ABD77-2E52-36D1-8E39-77AE2CC61611> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff42911000 - 0x7fff4291cff7 com.apple.AppleIDAuthSupport (1.0 - 1) <74F6CD9C-27A7-39C7-A7EB-47E60D2517EB> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff4295e000 - 0x7fff429a6ff7 com.apple.AppleJPEG (1.0 - 1) <6DE30A07-C627-319B-A0DE-EB7A832BEB88> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff42d90000 - 0x7fff42d94ff7 com.apple.AppleSRP (5.0 - 1) <70C25EA9-F7A7-366C-97C6-EEE7845FFCC3> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP\n 0x7fff42d95000 - 0x7fff42db7fff com.apple.applesauce (1.0 - 16.25) <68E0364C-AEA7-3654-A030-136BF3CD92F3> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff42e77000 - 0x7fff42e7afff com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <67255151-F989-39F0-BC87-0C0BDAE70730> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo\n 0x7fff42e7b000 - 0x7fff42ecbff7 com.apple.AppleVAFramework (6.1.2 - 6.1.2) <6FFF024C-E5E8-3A98-A3F6-67116DA6A7CF> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff42f14000 - 0x7fff42f23ff9 com.apple.AssertionServices (1.0 - 223.140.2) <48AD21CA-B81D-380E-A04F-90C48FDA5203> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff43466000 - 0x7fff43861ff8 com.apple.audio.AudioResourceArbitration (1.0 - 1) <2BD68521-C19C-3D67-B5EB-DE3E9A4DAF0A> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration\n 0x7fff439a0000 - 0x7fff439f1ff9 com.apple.audio.AudioSession (1.0 - 17) <AB93CA04-083D-3D80-9C33-28B30BA7A525> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession\n 0x7fff439f2000 - 0x7fff43a1fff7 libSessionUtility.dylib (17) <54A1C204-FCBA-3106-A896-28F22ECF144E> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib\n 0x7fff43ab7000 - 0x7fff43cf8ff8 com.apple.audio.AudioToolboxCore (1.0 - 1104.101) <DFAF67B3-AE61-34BC-AFC5-9C7B2DFC77AE> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore\n 0x7fff43cfc000 - 0x7fff43e18fff com.apple.AuthKit (1.0 - 1) <DC1A27C5-0172-3C72-9B24-06996D0B6207> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff43fd5000 - 0x7fff43fdeff7 com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <A6877DAD-8F47-363C-983A-DC8DDE83B7B5> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff43fdf000 - 0x7fff44080ff5 com.apple.backup.framework (1.11.7 - 1298.7.1) <C9DC35FA-E69F-3C64-9519-494126096337> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff44081000 - 0x7fff4410dff6 com.apple.BaseBoard (466.3 - 466.3) <10D0F3BB-E8F3-365E-8528-6AC996A9B0E7> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff4420f000 - 0x7fff4424bff7 com.apple.bom (14.0 - 219.2) <79CBE5E7-054F-377B-9566-A86A9F120CF1> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom\n 0x7fff44dcb000 - 0x7fff44e1afff com.apple.ChunkingLibrary (307 - 307) <5B09C30D-FD2B-3E98-8B64-C5EF470FC13C> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff44f75000 - 0x7fff45000ff8 com.apple.CloudDocs (1.0 - 698.20) <F28635C0-9935-31FF-8EE1-ADD6972F8848> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs\n 0x7fff45cc7000 - 0x7fff45cd7ffb com.apple.CommonAuth (4.0 - 2.0) <24F1A864-0FA1-39CE-8A26-52E8C078FD33> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff45ceb000 - 0x7fff45d02fff com.apple.commonutilities (8.0 - 900) <F4C97244-E5D8-3F7D-8D94-4B6841C5A4EC> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities\n 0x7fff46409000 - 0x7fff467defc8 com.apple.CoreAUC (283.0.0 - 283.0.0) <4341271C-[D270](D270)-3F9F-8464-31A20D15158D> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff467df000 - 0x7fff4680cff7 com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <C3CFDC68-C7D9-3C44-9E7C-801D45575C10> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff4682f000 - 0x7fff46850ff4 com.apple.analyticsd (1.0 - 1) <15784654-86D7-3E6F-8AA9-BEC7852DC638> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics\n 0x7fff46b5b000 - 0x7fff46b66ff7 com.apple.frameworks.CoreDaemon (1.3 - 1.3) <BB7D67B1-2102-3D71-9BB6-AEB8C6A6EBB2> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon\n 0x7fff46de7000 - 0x7fff46df7ff3 com.apple.CoreEmoji (1.0 - 107.1) <7C2B3259-083B-31B8-BCDB-1BA360529936> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff47438000 - 0x7fff474a2ff0 com.apple.CoreNLP (1.0 - 213) <E70E2505-8078-324E-BAE1-01A2DA980E2C> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff478d0000 - 0x7fff478d8ff8 com.apple.CorePhoneNumbers (1.0 - 1) <E4DAD514-0B3B-3E0B-8AEA-39B320FAAF03> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff482c5000 - 0x7fff482e8fff com.apple.CoreSVG (1.0 - 129.3) <F38189F9-C8F9-3D62-9D5F-3F520FB81724> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG\n 0x7fff482e9000 - 0x7fff4831cfff com.apple.CoreServicesInternal (446.7 - 446.7) <65F53A22-6B61-382C-AAC2-B2C53F8FFB44> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff4831d000 - 0x7fff4834bffd com.apple.CSStore (1069.28 - 1069.28) <533A2D3E-B20F-3711-811D-4AD078437898> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore\n 0x7fff48870000 - 0x7fff48906ff7 com.apple.CoreSymbolication (11.4 - 64535.33.2) <955BD339-F593-3A70-8C08-71989480CC93> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff4899e000 - 0x7fff48acaff6 com.apple.coreui (2.1 - 609.4) <D8DA588B-CC17-339D-8D96-03B15100AE4C> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff48acb000 - 0x7fff48c84ffa com.apple.CoreUtils (6.2.4 - 624.7) <A74A1C65-6695-3F57-B703-0DEDE13E66C1> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff48dbe000 - 0x7fff48dd1ff1 com.apple.CrashReporterSupport (10.13 - 15016.1) <D584FFA6-32C5-328B-BE77-2C256B2B116C> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff48e8a000 - 0x7fff48e9cff8 com.apple.framework.DFRFoundation (1.0 - 252.50.1) <8162057E-E856-3451-9160-04AEDDECFFA4> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff48e9d000 - 0x7fff48ea2fff com.apple.DSExternalDisplay (3.1 - 380) <31ECB5FD-7660-33DB-BC5B-2B2A2AA7C686> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff48f2c000 - 0x7fff48fa6ff0 com.apple.datadetectorscore (8.0 - 659) <B1534796-1000-3520-A641-A97A4AC5D39B> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff48ff2000 - 0x7fff4902fff8 com.apple.DebugSymbols (194 - 194) <040AE30B-CF2C-3798-A289-0929B8CAB10D> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff49030000 - 0x7fff491b8ff6 com.apple.desktopservices (1.14.6 - 1281.6.1) <C2355E6B-C5F7-3E39-B778-B117BD4652C6> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff49467000 - 0x7fff4952fffe com.apple.DiskImagesFramework (559.100.2 - 559.100.2) <71022C31-42C2-399C-9337-BBB3F40F77D8> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages\n 0x7fff49530000 - 0x7fff49603ff1 com.apple.DiskManagement (13.0 - 1648.140.2) <640DBACE-B6EC-3C72-9F73-F484E891534E> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement\n 0x7fff496e6000 - 0x7fff496eaff9 com.apple.EFILogin (2.0 - 2) <3BFE697B-469F-38F4-B380-4A4F4A37C836> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin\n 0x7fff4ab79000 - 0x7fff4af94ff1 com.apple.vision.FaceCore (4.3.0 - 4.3.0) <5D32F65D-2CD7-3204-975C-F4C9256E505F> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff4b5ec000 - 0x7fff4b5ecfff com.apple.FinderSyncPriv (1.0.7 - 1298.7.1) <5E08FCCF-B5AA-367F-BD08-DEFD32AB073F> /System/Library/PrivateFrameworks/FinderSyncPriv.framework/Versions/A/FinderSyncPriv\n 0x7fff4b633000 - 0x7fff4b769ffc libFontParser.dylib (277.2.6.8) <CEF2BBCB-E520-3B2E-85F7-4B2565ED4B18> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib\n 0x7fff4b76a000 - 0x7fff4b79efff libTrueTypeScaler.dylib (277.2.6.8) <4D7463BE-7831-3A60-8010-223293D3B232> /System/Library/PrivateFrameworks/FontServices.framework/libTrueTypeScaler.dylib\n 0x7fff4b802000 - 0x7fff4b812ff6 libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <69BBF689-9AC2-3B8E-8EDD-6B083BF583F4> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib\n 0x7fff4ecf3000 - 0x7fff4ecf4fff libmetal_timestamp.dylib (902.14.11) <C29C7125-A894-3718-8E1D-249C53BCC0B8> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib\n 0x7fff503a2000 - 0x7fff503adff7 libGPUSupportMercury.dylib (17.10.22) <10F6DA68-90C5-3EF3-A437-EFF8B51320E3> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff503ae000 - 0x7fff503b4fff com.apple.GPUWrangler (5.2.7 - 5.2.7) <FA34760B-4E5C-3A18-A6C3-DBA68F9D1220> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff506d3000 - 0x7fff506f9ff1 com.apple.GenerationalStorage (2.0 - 314) <54483E50-20BB-3AF8-900F-992320C109B0> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff51827000 - 0x7fff51835ffb com.apple.GraphVisualizer (1.0 - 100.1) <507D5812-9CB4-3C94-938C-59ED2B370818> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff519d4000 - 0x7fff51a92ff4 com.apple.Heimdal (4.0 - 2.0) <D621CBD1-DC73-32BC-A9C0-A9C289832005> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff53c1e000 - 0x7fff53c26ff5 com.apple.IOAccelerator (438.7.4 - 438.7.4) <3C973800-3AE0-3908-9922-EFBC57C3F5B2> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff53c33000 - 0x7fff53c4afff com.apple.IOPresentment (47.10 - 37) <C97340B5-C71D-32CC-A519-30A5D7184BD3> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff53fd2000 - 0x7fff5401dff1 com.apple.IconServices (438.3 - 438.3) <0DADB4C3-46FF-3FDB-8A86-51E2067FC7F4> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff541db000 - 0x7fff541e2ff9 com.apple.InternationalSupport (1.0 - 45.4) <8D8D4A7D-FD35-36B8-A456-7C93030EDAB3> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport\n 0x7fff5446f000 - 0x7fff5448effd com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <42DEA6AF-7D35-37CC-A943-8CAEF0C482FF> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff545c3000 - 0x7fff54691ffd com.apple.LanguageModeling (1.0 - 215.1) <C456087D-5B3A-390E-A665-862FA284C59C> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff54692000 - 0x7fff546dafff com.apple.Lexicon-framework (1.0 - 72) <41F208B9-8255-3EC7-9673-FE0925D071D3> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff546e1000 - 0x7fff546e6ff3 com.apple.LinguisticData (1.0 - 353.18) <3B92F249-4602-325F-984B-D2DE61EEE4E1> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff5478a000 - 0x7fff5478fff7 com.apple.LoginUICore (4.0 - 4.0) <25CA17AF-8A74-3CE3-84D8-67B4A2B76FEA> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore\n 0x7fff54f7f000 - 0x7fff54f82fff com.apple.Mangrove (1.0 - 25) <482F300F-9B70-351F-A4DF-B440EEF7368D> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff551eb000 - 0x7fff55275ff8 com.apple.MediaExperience (1.0 - 1) <A419A023-7F58-3C06-857A-5FA7C329979E> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience\n 0x7fff55276000 - 0x7fff552a9fff com.apple.MediaKit (16 - 923) <09FEE738-41E4-3A9C-AF1E-1DD00C56339D> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit\n 0x7fff55a4f000 - 0x7fff55a9bfff com.apple.spotlight.metadata.utilities (1.0 - 2076.7.1) <4B5178DD-3F75-3508-BDE9-BF5BCA0FD66F> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff55a9c000 - 0x7fff55b6dffa com.apple.gpusw.MetalTools (1.0 - 1) <99876E08-37D7-3828-8796-56D90C9AFBDB> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff55bcb000 - 0x7fff55be4ff4 com.apple.MobileAssets (1.0 - 619.120.1) <07E116E6-7EBC-39F2-B5B4-31BAB6BAF852> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff55da1000 - 0x7fff55dbffff com.apple.MobileKeyBag (2.0 - 1.0) <D5FA7041-297F-3ADC-8C7A-6EAAAB82EB68> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff56022000 - 0x7fff56052ff7 com.apple.MultitouchSupport.framework (3440.1 - 3440.1) <6794E1C8-9627-33DF-84F4-FDD02C97F383> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff56552000 - 0x7fff5655cfff com.apple.NetAuth (6.2 - 6.2) <B0C03C41-87A3-352B-B130-96E1A6F94B47> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff56f73000 - 0x7fff56fbeffb com.apple.OTSVG (1.0 - 643.1.5.7) <2F7D0C6A-6D8C-351C-8305-31D83D71893A> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff581dc000 - 0x7fff581e7ff2 com.apple.PerformanceAnalysis (1.243.3 - 243.3) <7B2C4193-68D7-3B95-ACA3-0FDD33A74D45> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff581e8000 - 0x7fff58210ffb com.apple.persistentconnection (1.0 - 1.0) <5B2D87A8-2641-3F6D-ACEA-96B00F85AAB5> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection\n 0x7fff59c8b000 - 0x7fff59cbbff7 com.apple.pluginkit.framework (1.0 - 1) <EFBD7FE7-02CC-3E30-999D-B036F252F805> /System/Library/PrivateFrameworks/PlugInKit.framework/Versions/A/PlugInKit\n 0x7fff59ce6000 - 0x7fff59cf9ffc com.apple.PowerLog (1.0 - 1) <76D14DBC-1D4C-3D15-B076-9DE487BADC41> /System/Library/PrivateFrameworks/PowerLog.framework/Versions/A/PowerLog\n 0x7fff5ab75000 - 0x7fff5abcfff6 com.apple.ProtectedCloudStorage (1.0 - 1) <6F271388-3817-336D-9B96-08C7AAC4BA39> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage\n 0x7fff5abd0000 - 0x7fff5abe9ffb com.apple.ProtocolBuffer (1 - 274.24.9.16.3) <5A020941-C43C-303E-8DE8-230FC6A84DBC> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff5b049000 - 0x7fff5b072ff1 com.apple.RemoteViewServices (2.0 - 148) <D3AAC2BE-3423-3F18-9654-E35F1DD8DDB3> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff5b1d7000 - 0x7fff5b212ff0 com.apple.RunningBoardServices (1.0 - 223.140.2) <96BB04BD-D6E0-3D70-8F36-89B46DA1DA30> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices\n 0x7fff5caf3000 - 0x7fff5caf6ff5 com.apple.SecCodeWrapper (4.0 - 448.100.6) <C4BF691D-A09E-37E8-A6CC-1145B79B8722> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper\n 0x7fff5cc69000 - 0x7fff5cd90fff com.apple.Sharing (1526.37 - 1526.37) <CBDA0ADD-F1E7-3B06-9118-C5E183F0D3D6> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff5e1a5000 - 0x7fff5e49bfff com.apple.SkyLight (1.600.0 - 451.6) <489A2996-E719-346E-BACE-DCCDB5E00553> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff5ece8000 - 0x7fff5ecf6ffb com.apple.SpeechRecognitionCore (6.0.91.2 - 6.0.91.2) <4D6CAC2A-151B-3BBE-BDB7-E2BE72128691> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff5edb8000 - 0x7fff5f044ffe com.apple.spotlight.index (10.7.0 - 2076.7.1) <99A0E014-3FAC-3A60-8CE0-2D4F13033250> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex\n 0x7fff5f3d2000 - 0x7fff5f413ff9 com.apple.StreamingZip (1.0 - 1) <063525B7-8F1D-334B-88E4-BBEAE42B61F2> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff5f52a000 - 0x7fff5f533ff7 com.apple.SymptomDiagnosticReporter (1.0 - 1238.120.2) <C3D66901-7E31-3FDB-BD7A-441EB0520D1D> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter\n 0x7fff5f5a4000 - 0x7fff5f5ceffe com.apple.framework.SystemAdministration (1.0 - 1.0) <F33CF335-5E41-3D50-926A-5AA8B5D2A1B4> /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration\n 0x7fff5f7ea000 - 0x7fff5f7faff3 com.apple.TCC (1.0 - 1) <520B2095-42EF-3837-99D3-393CA377ADBA> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff5fd1f000 - 0x7fff5fde5ff0 com.apple.TextureIO (3.10.9 - 3.10.9) <EEDAB753-329A-396A-8119-5BEDF7DB5A56> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff5ff7c000 - 0x7fff5ff7dfff com.apple.TrustEvaluationAgent (2.0 - 33) <10E56F70-E234-31E0-9286-96D93A8ED17E> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff5ffb5000 - 0x7fff6020dff0 com.apple.UIFoundation (1.0 - 662) <EC55B9E5-7E62-380A-9AB1-FC7BEF663653> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff60eaa000 - 0x7fff60ecaffc com.apple.UserManagement (1.0 - 1) <9F00880E-6EA6-3684-B208-455E14EC07C8> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement\n 0x7fff61c76000 - 0x7fff61d61ff2 com.apple.ViewBridge (468 - 468) <E35C7CF5-DE95-3B39-ACB8-A3C72C785E8F> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff61f07000 - 0x7fff61f08fff com.apple.WatchdogClient.framework (1.0 - 67.120.2) <FFA17DA1-F6DD-34D3-A708-1F73C8BA7EA7> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient\n 0x7fff62b38000 - 0x7fff62b3bffa com.apple.dt.XCTTargetBootstrap (1.0 - 16091) <00FA6272-2017-3199-9E0F-F6DEF5E868D5> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff62bb5000 - 0x7fff62bc3ff5 com.apple.audio.caulk (1.0 - 32.3) <06D695EA-E2BC-31E4-9816-9C12542BA744> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7fff62f05000 - 0x7fff62f07ff3 com.apple.loginsupport (1.0 - 1) <540BB904-0A51-3B37-A436-969D24CD28AC> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff62f08000 - 0x7fff62f1bffd com.apple.login (3.0 - 3.0) <4483035E-7BEB-3CEB-AC1B-A765FBC12678> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff659eb000 - 0x7fff65a1effa libAudioToolboxUtility.dylib (1104.101) <EE629877-CE82-3286-B40B-ACEABFCC494A> /usr/lib/libAudioToolboxUtility.dylib\n 0x7fff65a25000 - 0x7fff65a59fff libCRFSuite.dylib (48) <5E5DE3CB-30DD-34DC-AEF8-FE8536A85E96> /usr/lib/libCRFSuite.dylib\n 0x7fff65a5c000 - 0x7fff65a66fff libChineseTokenizer.dylib (34) <7F0DA183-1796-315A-B44A-2C234C7C50BE> /usr/lib/libChineseTokenizer.dylib\n 0x7fff65a67000 - 0x7fff65aeffff libCoreStorage.dylib (551.0.1) <D2F45D31-91C3-31A0-85BF-56FFDC4EB793> /usr/lib/libCoreStorage.dylib\n 0x7fff65af2000 - 0x7fff65af4ff7 libDiagnosticMessagesClient.dylib (112) <C94F3B7B-1854-38EB-9778-834501C53B3F> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff65b3a000 - 0x7fff65cf1ffb libFosl_dynamic.dylib (100.4) <737573B2-190A-3BA1-8220-807AD0A2CE5E> /usr/lib/libFosl_dynamic.dylib\n 0x7fff65d18000 - 0x7fff65d1eff3 libIOReport.dylib (54) <75D177C4-BAD7-3285-B8E1-3019F49B3178> /usr/lib/libIOReport.dylib\n 0x7fff65e00000 - 0x7fff65e07fff libMatch.1.dylib (36) <5C6F3971-9D9E-3630-BDB6-60BFC5A665E0> /usr/lib/libMatch.1.dylib\n 0x7fff65e36000 - 0x7fff65e56ff7 libMobileGestalt.dylib (826.140.5) <2BE94E6A-FA61-312F-84A1-F764D71B7E39> /usr/lib/libMobileGestalt.dylib\n 0x7fff65fc8000 - 0x7fff65fc9fff libSystem.B.dylib (1281.100.1) <0DE4111E-9962-33E7-9F68-347DD9FE720F> /usr/lib/libSystem.B.dylib\n 0x7fff66056000 - 0x7fff66057fff libThaiTokenizer.dylib (3) <4F4ADE99-0D09-3223-B7C0-C407AB6DE8DC> /usr/lib/libThaiTokenizer.dylib\n 0x7fff6606f000 - 0x7fff66085fff libapple_nghttp2.dylib (1.39.2) <07FEC48A-87CF-32A3-8194-FA70B361713A> /usr/lib/libapple_nghttp2.dylib\n 0x7fff660ba000 - 0x7fff6612cff7 libarchive.2.dylib (72.140.2) <F9EA2883-5D5C-3FA6-B3F8-C5031BF88ABD> /usr/lib/libarchive.2.dylib\n 0x7fff6612d000 - 0x7fff6625cfed libate.dylib (3.0.1) <DE609B9D-AD02-34FE-A91B-464ECDECC73A> /usr/lib/libate.dylib\n 0x7fff66260000 - 0x7fff66260ff3 libauto.dylib (187) <B6124448-7690-34AE-8939-ED84AAC630CE> /usr/lib/libauto.dylib\n 0x7fff66326000 - 0x7fff66336ffb libbsm.0.dylib (60.100.1) <00BFFB9A-2FFE-3C24-896A-251BC61917FD> /usr/lib/libbsm.0.dylib\n 0x7fff66337000 - 0x7fff66343fff libbz2.1.0.dylib (44) <14CC4988-B6D4-3879-AFC2-9A0DDC6388DE> /usr/lib/libbz2.1.0.dylib\n 0x7fff66344000 - 0x7fff66396fff libc++.1.dylib (902.1) <59A8239F-C28A-3B59-B8FA-11340DC85EDC> /usr/lib/libc++.1.dylib\n 0x7fff66397000 - 0x7fff663acffb libc++abi.dylib (902) <E692F14F-C65E-303B-9921-BB7E97D77855> /usr/lib/libc++abi.dylib\n 0x7fff663ad000 - 0x7fff663adfff libcharset.1.dylib (59) <72447768-9244-39AB-8E79-2FA14EC0AD33> /usr/lib/libcharset.1.dylib\n 0x7fff663ae000 - 0x7fff663bffff libcmph.dylib (8) <E72A20DB-2E86-378D-A237-EB9A1370F989> /usr/lib/libcmph.dylib\n 0x7fff663c0000 - 0x7fff663d8fd7 libcompression.dylib (87.1) <F3C7F9B4-71CF-3398-AAD3-456C9FEECD08> /usr/lib/libcompression.dylib\n 0x7fff666b2000 - 0x7fff666c8ff7 libcoretls.dylib (167) <770A5B96-936E-34E3-B006-B1CEC299B5A5> /usr/lib/libcoretls.dylib\n 0x7fff666c9000 - 0x7fff666cafff libcoretls_cfhelpers.dylib (167) <940BF370-FD0C-30A8-AA05-FF48DA44FA4C> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff66b6d000 - 0x7fff66c71fef libcrypto.44.dylib (47.140.1) <CB6B188A-1ADC-3C5D-AFFC-2ACD86E235EE> /usr/lib/libcrypto.44.dylib\n 0x7fff66c74000 - 0x7fff66c7ffff libcsfde.dylib (551.0.1) <FDD996E0-B876-3B82-8B12-D311324E8331> /usr/lib/libcsfde.dylib\n 0x7fff66c87000 - 0x7fff66ce6ff7 libcups.2.dylib (483.8) <A5424908-1508-35AF-B218-7A976BEABCBA> /usr/lib/libcups.2.dylib\n 0x7fff66ce8000 - 0x7fff66d4dff7 libcurl.4.dylib (118.120.6) <5ECFDF8F-E82B-3194-984C-181897781A64> /usr/lib/libcurl.4.dylib\n 0x7fff66df0000 - 0x7fff66df0fff libenergytrace.dylib (21) <162DFCC0-8F48-3DD0-914F-FA8653E27B26> /usr/lib/libenergytrace.dylib\n 0x7fff66df1000 - 0x7fff66e0bff7 libexpat.1.dylib (19.60.3) <4FD5D517-B4C8-365B-A2C0-D998A624D5A0> /usr/lib/libexpat.1.dylib\n 0x7fff66e19000 - 0x7fff66e1bfff libfakelink.dylib (149.1) <36146CB2-E6A5-37BB-9EE8-1B4034D8F3AD> /usr/lib/libfakelink.dylib\n 0x7fff66e2a000 - 0x7fff66e2ffff libgermantok.dylib (24) <D2AE5AC0-EDCE-3216-B8C9-CF59292A545F> /usr/lib/libgermantok.dylib\n 0x7fff66e30000 - 0x7fff66e39ff7 libheimdal-asn1.dylib (564.140.7) <45E5B8EE-93E9-31FC-9A4D-E96AF618BABA> /usr/lib/libheimdal-asn1.dylib\n 0x7fff66e3a000 - 0x7fff66f2afff libiconv.2.dylib (59) <18311A67-E4EF-3CC7-95B3-C0EDEE3A282F> /usr/lib/libiconv.2.dylib\n 0x7fff66f2b000 - 0x7fff67182fff libicucore.A.dylib (64260.0.1) <8AC2CB07-E7E0-340D-A849-186FA1F27251> /usr/lib/libicucore.A.dylib\n 0x7fff6719c000 - 0x7fff6719dfff liblangid.dylib (133) <30CFC08C-EF36-3CF5-8AEA-C1CB070306B7> /usr/lib/liblangid.dylib\n 0x7fff6719e000 - 0x7fff671b6ff3 liblzma.5.dylib (16) <C131EF18-2CDD-3271-8A30-A8760D4FE166> /usr/lib/liblzma.5.dylib\n 0x7fff671ce000 - 0x7fff67275ff7 libmecab.dylib (883.11) <0D5BFD01-D4A7-3C8D-AA69-C329C1A69792> /usr/lib/libmecab.dylib\n 0x7fff67276000 - 0x7fff674d8ff1 libmecabra.dylib (883.11) <E31DE74D-1B88-377F-ACD3-D789D29C3AE7> /usr/lib/libmecabra.dylib\n 0x7fff67845000 - 0x7fff67874fff libncurses.5.4.dylib (57) <995DFEEA-40F3-377F-B73D-D02AC59D591F> /usr/lib/libncurses.5.4.dylib\n 0x7fff679a4000 - 0x7fff67e20ff5 libnetwork.dylib (1880.120.4) <BA294A54-F309-398D-B308-F97032AFF555> /usr/lib/libnetwork.dylib\n 0x7fff67ec1000 - 0x7fff67ef3fde libobjc.A.dylib (787.1) <265783CE-6D74-36C9-B6D2-95D3910199EC> /usr/lib/libobjc.A.dylib\n 0x7fff67ef4000 - 0x7fff67ef5ff7 libodfde.dylib (26) <33F49412-5106-35B8-AA60-5A497C3967E6> /usr/lib/libodfde.dylib\n 0x7fff67f06000 - 0x7fff67f0afff libpam.2.dylib (25.100.1) <0502F395-8EE6-3D2A-9239-06FD5622E19E> /usr/lib/libpam.2.dylib\n 0x7fff67f0d000 - 0x7fff67f43fff libpcap.A.dylib (89.120.2) <86DAA475-805A-3E01-86C5-6CAE4D1D9BC6> /usr/lib/libpcap.A.dylib\n 0x7fff67fc7000 - 0x7fff67fdffff libresolv.9.dylib (67.40.1) <C57EDFEF-D36A-310B-8D14-8C68A625B1E8> /usr/lib/libresolv.9.dylib\n 0x7fff67fe1000 - 0x7fff68025ff7 libsandbox.1.dylib (1217.141.6) <1B5B5733-BAD1-3FB6-BA75-2AC4FDCCE7CE> /usr/lib/libsandbox.1.dylib\n 0x7fff68026000 - 0x7fff68038ff7 libsasl2.2.dylib (213.120.1) <E7573AC1-83FD-305A-8FB8-03145BDA286B> /usr/lib/libsasl2.2.dylib\n 0x7fff68039000 - 0x7fff6803aff7 libspindump.dylib (281.3) <AE8C1AE9-5CBC-332F-BBE8-370A2A19FED6> /usr/lib/libspindump.dylib\n 0x7fff6803b000 - 0x7fff6821dff7 libsqlite3.dylib (308.6) <3E17BEE7-19F3-329D-BBF9-1DD5D54913AD> /usr/lib/libsqlite3.dylib\n 0x7fff68311000 - 0x7fff6833effb libssl.46.dylib (47.140.1) <06932872-13DA-33E3-8C28-7B49FC582039> /usr/lib/libssl.46.dylib\n 0x7fff68413000 - 0x7fff6846dff8 libusrtcp.dylib (1880.120.4) <05346A91-737C-33D0-B21B-F040950DFB28> /usr/lib/libusrtcp.dylib\n 0x7fff6846e000 - 0x7fff68471ffb libutil.dylib (57) <F01467F6-23A7-37EE-A170-33CE1577B41D> /usr/lib/libutil.dylib\n 0x7fff68472000 - 0x7fff6847fff7 libxar.1.dylib (425.5) <89F150D9-C1CC-3FD5-A132-0860BF919795> /usr/lib/libxar.1.dylib\n 0x7fff68485000 - 0x7fff68567fff libxml2.2.dylib (33.9) <B72D22CE-3429-3217-A8DD-5C9D2077C980> /usr/lib/libxml2.2.dylib\n 0x7fff6856b000 - 0x7fff68593fff libxslt.1.dylib (16.12) <42938E5F-5FE9-3265-8D10-1D1115BC5402> /usr/lib/libxslt.1.dylib\n 0x7fff68594000 - 0x7fff685a6ff3 libz.1.dylib (76) <793D9643-CD83-3AAC-8B96-88D548FAB620> /usr/lib/libz.1.dylib\n 0x7fff68e55000 - 0x7fff68e5aff3 libcache.dylib (83) <AF488D13-9E89-35E0-B078-BE37CC5B8586> /usr/lib/system/libcache.dylib\n 0x7fff68e5b000 - 0x7fff68e66fff libcommonCrypto.dylib (60165.120.1) <C7912BE5-993E-3581-B2A0-6AABDC8C5562> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff68e67000 - 0x7fff68e6efff libcompiler_rt.dylib (101.2) <49B8F644-5705-3F16-BBE0-6FFF9B17C36E> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff68e6f000 - 0x7fff68e78ff7 libcopyfile.dylib (166.40.1) <3C481225-21E7-370A-A30E-0CCFDD64A92C> /usr/lib/system/libcopyfile.dylib\n 0x7fff68e79000 - 0x7fff68f0bfdb libcorecrypto.dylib (866.140.2) <E9AAA2A6-D0D4-328A-BEA2-4DC5E513BA30> /usr/lib/system/libcorecrypto.dylib\n 0x7fff69018000 - 0x7fff69058ff0 libdispatch.dylib (1173.100.2) <CD9C059C-91D9-30E8-8926-5B9CD0D5D4F5> /usr/lib/system/libdispatch.dylib\n 0x7fff69059000 - 0x7fff6908ffff libdyld.dylib (750.7) <AB99C9EE-7127-3451-89AB-339F8F2CEE61> /usr/lib/system/libdyld.dylib\n 0x7fff69090000 - 0x7fff69090ffb libkeymgr.dylib (30) <DB3337BE-01CA-3425-BD0C-87774FC0CDC0> /usr/lib/system/libkeymgr.dylib\n 0x7fff69091000 - 0x7fff6909dff3 libkxld.dylib (6153.141.43) <DE02C6DC-98DA-30EB-A528-57AA625F3A90> /usr/lib/system/libkxld.dylib\n 0x7fff6909e000 - 0x7fff6909eff7 liblaunch.dylib (1738.140.3) <E2CFD17D-F36C-3734-8F37-16798799EF9E> /usr/lib/system/liblaunch.dylib\n 0x7fff6909f000 - 0x7fff690a4ff7 libmacho.dylib (959.0.1) <AA613A9C-961A-3B67-B696-4622FA59FC4E> /usr/lib/system/libmacho.dylib\n 0x7fff690a5000 - 0x7fff690a7ff3 libquarantine.dylib (110.40.3) <F234E51D-FD0B-3EE4-B679-AE3EE9C536C3> /usr/lib/system/libquarantine.dylib\n 0x7fff690a8000 - 0x7fff690a9ff7 libremovefile.dylib (48) <7C7EFC79-BD24-33EF-B073-06AED234593E> /usr/lib/system/libremovefile.dylib\n 0x7fff690aa000 - 0x7fff690c1ff3 libsystem_asl.dylib (377.60.2) <1563EE02-0657-3B78-99BE-A947C24122EF> /usr/lib/system/libsystem_asl.dylib\n 0x7fff690c2000 - 0x7fff690c2ff7 libsystem_blocks.dylib (74) <0D53847E-AF5F-3ACF-B51F-A15DEA4DEC58> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff690c3000 - 0x7fff6914afff libsystem_c.dylib (1353.100.4) <BCD3F031-4A3F-32CF-AB9A-D6EE7A7499D4> /usr/lib/system/libsystem_c.dylib\n 0x7fff6914b000 - 0x7fff6914effb libsystem_configuration.dylib (1061.141.2) <393137B7-3631-3450-B6F4-95EECD3ADDFF> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff6914f000 - 0x7fff69152fff libsystem_coreservices.dylib (114.1) <72857ADA-AA97-398B-B089-F50B2E89064B> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff69153000 - 0x7fff6915bfff libsystem_darwin.dylib (1353.100.4) <19242BF1-BAF6-3DF0-AAD3-93E3E0870DBE> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff6915c000 - 0x7fff69163fff libsystem_dnssd.dylib (1096.100.3) <EBB4C2C2-E031-3094-B40A-E67BF261D295> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff69164000 - 0x7fff69165ffb libsystem_featureflags.dylib (17) <29FD922A-EC2C-3F25-BCCC-B58D716E60EC> /usr/lib/system/libsystem_featureflags.dylib\n 0x7fff69166000 - 0x7fff691b3ff7 libsystem_info.dylib (538) <8A321605-5480-330B-AF9E-64E65DE61747> /usr/lib/system/libsystem_info.dylib\n 0x7fff691b4000 - 0x7fff691e0ff7 libsystem_kernel.dylib (6153.141.43) <07D18CB3-15B9-3490-A6B5-D8C0964D0FEC> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff691e1000 - 0x7fff6922cfef libsystem_m.dylib (3178) <D1CF3A92-2424-3420-B375-DEED7AA68C53> /usr/lib/system/libsystem_m.dylib\n 0x7fff6922d000 - 0x7fff69254fff libsystem_malloc.dylib (283.100.6) <8549294E-4C53-36EB-99F3-584A7393D8D5> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff69255000 - 0x7fff69262ffb libsystem_networkextension.dylib (1095.140.2) <F06C65C5-2CBE-313C-96E1-A09240F9FE57> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff69263000 - 0x7fff6926cff7 libsystem_notify.dylib (241.100.2) <FA22F928-D91B-3AA5-96BB-3186AC0FB264> /usr/lib/system/libsystem_notify.dylib\n 0x7fff6926d000 - 0x7fff69275fef libsystem_platform.dylib (220.100.1) <009A7C1F-313A-318E-B9F2-30F4C06FEA5C> /usr/lib/system/libsystem_platform.dylib\n 0x7fff69276000 - 0x7fff69280fff libsystem_pthread.dylib (416.100.3) <62CB1A98-0B8F-31E7-A02B-A1139927F61D> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff69281000 - 0x7fff69285ff3 libsystem_sandbox.dylib (1217.141.6) <ACACC5C9-CE29-394C-87AD-3AF5FDDA942E> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff69286000 - 0x7fff69288fff libsystem_secinit.dylib (62.100.2) <F80872AA-E1FD-3D7E-8729-467656EC6561> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff69289000 - 0x7fff69290ffb libsystem_symptoms.dylib (1238.120.2) <702D0910-5C34-3D43-9631-8BD215DE4FE1> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff69291000 - 0x7fff692a7ff2 libsystem_trace.dylib (1147.120.1) <BC141783-66D9-3137-A783-211B38E49ADB> /usr/lib/system/libsystem_trace.dylib\n 0x7fff692a9000 - 0x7fff692aeff7 libunwind.dylib (35.4) <42B7B509-BAFE-365B-893A-72414C92F5BF> /usr/lib/system/libunwind.dylib\n 0x7fff692af000 - 0x7fff692e4ffe libxpc.dylib (1738.140.3) <8DA7D88F-AE2F-3BCF-8426-8D041E57A9AA> /usr/lib/system/libxpc.dylib\n\nExternal Modification Summary:\n```\nCalls made by other processes targeting this process:\n task_for_pid: 4\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: 530\n thread_create: 0\n thread_set_state: 0\n```\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=947.2M resident=0K(0%) swapped_out_or_unallocated=947.2M(100%)\nWritable regions: Total=1.6G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.6G(100%)\n \n```\n VIRTUAL REGION \n```\nREGION TYPE SIZE COUNT (non-coalesced) \n**=======**\nAccelerate framework 128K 1 \nActivity Tracing 256K 1 \nCG backing stores 224K 2 \nCG image 48K 6 \nCoreAnimation 84K 15 \nCoreGraphics 8K 1 \nCoreImage 8K 2 \nCoreUI image data 332K 6 \nFoundation 4K 1 \nKernel Alloc Once 8K 1 \nMALLOC 382.5M 361 \nMALLOC guard page 32K 7 \nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 236K 59 \nStack 692.0M 59 \nVM_ALLOCATE 157.2M 442 \nVM_ALLOCATE (reserved) 36K 1 reserved VM address space (unallocated)\n__DATA 97.9M 520 \n__DATA_CONST 124K 6 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 458.7M 313 \n__OBJC_RO 32.3M 1 \n__OBJC_RW 1908K 2 \n__TEXT 489.4M 511 \n__UNICODE 564K 1 \nmapped file 73.0M 22 \nshared memory 640K 15 \n**=======**\nTOTAL 2.7G 2362 \nTOTAL, minus reserved VM space 2.3G 2362 \n\nModel: MacBookPro9,2, BootROM 424.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2,5 GHz, 16 GB, SMC 2.2f44\nGraphics: kHW_IntelHD4000Item, Intel HD Graphics 4000, spdisplays_builtin\nMemory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5358384758334D314131363030433130\nMemory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5358384758334D314131363030433130\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.21.190.33 AirPortDriverBrcm4360-1601.1)\nBluetooth: Version 7.0.6f8, 3 services, 18 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en1\nSerial ATA Device: Samsung SSD 750 EVO 250GB, 250,06 GB\nSerial ATA Device: HL-DT-ST DVDRW GS41N\nUSB Device: USB 2.0 Bus\nUSB Device: Hub\nUSB Device: Hub\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: IR Receiver\nUSB Device: BRCM20702 Hub\nUSB Device: Bluetooth USB Host Controller\nUSB Device: USB 2.0 Hub\nUSB Device: USB Keyboard\nUSB Device: USB Gaming Mouse\nUSB Device: Ultra\nUSB Device: USB 2.0 Bus\nUSB Device: Hub\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: USB 3.0 Bus\nUSB Device: Elements 25A2\nThunderbolt Bus: MacBook Pro, Apple Inc., 25.1", "macOS Catalina 10.15.7: Eevee crash with Intel HD 4000\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n|Graphics card: | AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.22\n| -- | -- |\n||Intel HD Graphics 4000\nBroken: version: 2.93.5\nWorked: Same version before macOS update\n\nHT212825\nHT212871\n\nOpen & Close Blender without any other actions: Blender crash report comes up on Mac.\nCrash report attached in text file.\n\nOpen Blender. Press CMD+Q to Quit or File>>Quit\n\n[Blender_Crash_Report.rtf](Blender_Crash_Report.rtf)\n[Blender_Crash_Log.rtf](Blender_Crash_Log.rtf)\n" ]

[ "Most sculpt tools do not work while model is animated\nLinux 64-bit\n2.93.2\nMost sculpt tools do not work as expected when the object is spinning like it's on a pottery wheel. Some tools like the clay tool work okay, but other tools like smooth and scrape do not. I think it has to do with the stroke method; the stroke accounts for screen space but not the local transform of the object if it's moving during a stroke. Video of my attempt here:\n[pottery.mp4](pottery.mp4)\nI made this as a joke and it looks like garbage, but unfortunately it went viral and everybody thinks it's a great idea so now more people are gonna try it and complain that it doesn't work. It's a valid workflow that you have to account for now apparently. I'm really sorry.\n - Open the attached file\n - Play the animation\n # Try to sculpt the thing while it spins\n[bowl.blend](bowl.blend)\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", "Crash on applying boolean modifier\nOperating system: Linux Fedora V35\nGraphics card: Nvidia 3070TI\n\nBlender 3.1.2 and Blender 3.2.0 both crash\n\nI created a mesh object, then used boolean modifier to create a hollow center. I applied the modifier. When I go into edit to clean it up, it crashes.\n\napply the boolean modifier to the mesh \"Bottom\" with object \"Plug\" in the included blend file using all defaults. Enter edit mode and see the mesh is badly corrupted.\n\n[part7.blend](part7.blend)\n[printReady1.blend](printReady1.blend)", "Trim tools doesn't work with Dyntopo enabled\nBroken: blender-2.92.0-ef5d6e9c457a-windows64\n\nEnable the experimental \"tools with missing icons\"\nFile ´/ New / Sculpting\nEnable Dyntopo\nChoose the box or trim lasso tool and try to trim the mesh\nDoesn't work", "Allow changing the active modifier on linked objects\nUnzip the files from [active-modifier-linked.zip](active-modifier-linked.zip)\n\nOpen `linked.blend` and try to change the active modifer. You can't because it is linked.\n\nIn order to allow users to inspect their nodetrees (and eventually see the evaluated result of the modifier) I suggest we treat this as UI data and allow users to change that even for linked objects.\n\nWe do something similar already for the modifier \"Realtime - Display in viewport\" option.\n", "The Object Mode drop down menu in the 3D viewports is not reactive to larger font point settings.\nOperating system: Windows 10 1803\nGraphics card: nVidia RTX 2070\n\nBroken: v 2.80 as found on the splash screen\n\nThe Object Mode drop down menu in the 3D viewports does not properly resize itself if the user picks a larger font point size in the Themes section of the preferences. Instead of resizing the control truncates the overrunning text with a square character.\n\nStart Blender\nIn Preferences \\Themes \\ Text Style change the Widget Points setting from the default of 11 to a larger value. I used 15.\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.", "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", "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!", "Mesh box stl sizing issue when exporting\nOperating system: Windows 11\nGraphics card: Intel UHD Graphics 630\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen): 2.9.1 and 3.5.1\nWorked: (newest version of Blender that worked as expected). Unknown\n\nI started a brand new design/project from design. Nothing imported at all and this was a simple design, nothing hard. I've have done others, but those involved mesh cylinder's. For this, i was starting with a mesh cube. I've started from scratch at least 10 times. Before starting I have units set to Metric with measurements set to millimeters. For this issue, if I click on Add -> Mesh -> Cube. Then size it to what I need, in this case between 170-200mm ( aprox 7 inches). Once I size it, I export to an stl file and import into superslicer the cube shows up as a spec of dirt that you can't even see. Even if I import it using imperial units, it's slightly bigger, but only around 2 or 3mm in length.\nWhat is odd is, I do NOT have this problem if I'm dealing with a mesh cone or a Mesh cylinder. I have found a partial work around. When I start a new design from scratch, and my first object is a cylinder, i size that, then add a mesh cube... the sizing works perfectly. Now, once I do that though, if I add a second cube, then it's 100% totally messed up. Size is totally off and not even close. I do not have this behavior with cone or cylinder.\nI also get the same result if I take the original cube that is correctly sized, and I do a Shift+D to create a duplicate cube. \n\nBased on the default startup or an attached .blend file (as simple as possible).\nYou can start with the existing Cube when it starts up, or you can choose File -> New -> General\nsize the cube so it's... 200mm x 200mm or anything like that. Then choose File -> Export - > Stl\nNow, for this project i'm printing on a Rat Rig printer so I'm using Superslicer for that. This is when it shows up like a spec of dust.\nNow, the work around, if you start new, delete the initial existing cube, then click on File -> Add -> Mesh -> Cylinder so that is the first and ONLY object on the screen. Size the cylinder to 300mm\nNow, if you click on File -> Add -> Mesh -> Cube and size that for example 200mmx200mm\nthen export as Stl, and import into SuperSlicer... it shows up EXACTLY the correct size you specify in Blender.\nSo far that is the only work around, but again, i haven't found a way to add a second cube and not mess up the sizing.\nThanks\n\nJim\n\n", "Can't edit new driver on an overriden property on a linked object with no animation data\n## Simplified Report\n\n- The following file contains an object with no animation data.\n- Link the object to a new file and make a library override from it.\n- Add a new driver on one of its location channels.\n- Notice that driver options are grayed out and can't be edited.\n- One expects to be able to edit the driver since the object has no animation data. \n\n[libraryFileWithNoAnimationData.blend](libraryFileWithNoAnimationData.blend)\n\n## Original Report\n\n\nOperating system: Linux-5.15.60-1-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.0\nWorked: ??? I could have sworn this worked in 3.2 but it seems to have the same behavior. Same in 2.93.\n\nUsing drivers with overridden properties is not really usable. I can add a driver, but then I cannot edit it.\n\nLink a collection into a file and make a library override. Right-click on a property and choose \"Add Driver\".\nRight click on the property (which should turn purple) and then choose \"Edit Driver\" Notice that the\ndriver's controls are all blurred out! You can't edit them in the UI.\nIt gets worse!\nOpen a driver-editor window so you can watch what happens in the next step, and select the driver you\njust created- open the \"Drivers\" tab in the window. Look at the expression.\nIn the main window (not the driver window), click on the driven property and type ~~\"#1\" - when you\nprepend a hash symbol, that tells Blender to edit the expression of a driver (it's a handy way to make\nnew drivers with simple expressions. Try it at home!)~~ **edit: it looks like you don't need the hash when it is already driven.**\nNow, notice the expression change in the driver window that you aren't normally able to edit!\nI have also confirmed that you can edit some properties with the Python API that you cannot edit in\nthe user interface.\n\n**My Thoughts** (If you're interested)\nI do not know if the design for overrides is intended to support using drivers like this. It feels a little squishy\nbecause I don't know if Blender will keep the driver around when I resync the override. On the other hand, it's\nreally handy when doing animation that is easier to do programmatically, such as causing a bone to oscillate\nwith sine-waves (e.g. a plant waving with the wind). Sometimes I use a driver to bake keyframes - so I set up the\ndriver and then bake its motion to an action, and get rid of the driver. It is my opinion that driver support is\nnecessary for overrides, because it's something I expect to be able to use, as an animator. I don't know if the\nold Proxy system supported drivers, though.\nAt any rate, if it is blocked from editing in one place, it should be blocked from editing through the API, too.\n\nI apologize if this is a known issue. I don't see any similar bug reports but it appears things have been like this\nfor a while.", "Gizmo position is wrong for meshes with modifiers\nWin10, Win7, Mac OS Sierra\nGTX970, GTX750\n\nBroken: 2.78a e8299c8 , 2.66.0 r54697\n\n\nWhen a joint (for example, an arm) is bent, paint weight is not enough to express deformation around the joint. So it's a common practice to add a shape key for the bent shape and edit it.\nBut when you enter edit mode and select polygons to edit it, the manipulator is on wrong position. \n\nJust select faces. Manipulator is supposed to sit on the selected faces but it's not.\n\n[manipulator bug.blend](manipulator_bug.blend)", "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", "Library Override Bug\nOperating system: Windows 10\nGraphics card: MSI 3060 Nvidea RTX\n\n2.6.1 LTS\n\nLibrary Override is bugged in this versión, rigs, mesh and some times materials too, i make library override in this version and the \"Alt+D\" objects or rigs was working well while the file is open but at the momment when i save and close the file and re-open the file most of the objects are broken or was deleted\n\n", "Creating Lattice object with script with {\"REGISTER\", \"UNDO\"} if parameters was changed in Undo window and mesh was in Edit mode - undo last changes to the mesh or last action\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.1\n\n{\"REGISTER\", \"UNDO\"} also undo last action if parameters was changed in \"Adjust last action\" pannel and mesh was in Edit mode.\n\n[Register_Undo_Issue.mp4](Register_Undo_Issue.mp4)\n\n[REGISTER_UNDO_in_EDIT_Mode.blend](REGISTER_UNDO_in_EDIT_Mode.blend)\n\n" ]

[ "BGE- No material when replace mesh used. :O\nWindows 7, GTX 650 \n\nBroken: All 2.70 versions...\nWorked: 2.60 versions it seems\n\nObjects replaced from one mesh to another only replace mesh data and not material data. :(\n\nCreate a \"Monkey\" (or whatever you like) and create a new material for that model. Now, make a new model and give it a new material of a different color. Now program one model to be replaced by the other. You'll see that the model changes but, the material does not. (In some cases the mesh will have no color data at all.) I've created a simple example file for you to test it out for yourself. :)\n\n**Test File**\n[Replace-Bug-Tester.blend](Replace-Bug-Tester.blend)", "2.70 RC1 Actuator editObject.replaseMesh replaced only mesh, and not replaced material.\nUbuntu 12.04, NVIDIA GTS-250\n\nBroken: (2.70 RC1)\nWorked: (2.69)\n\n2.70 RC1 Actuator editObject.replaseMesh replaced only mesh, and not replaced material." ]

[ "\"No Render\" volume of space with motion blur and GPU render\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.27\n\nBroken: version: 3.4.1\nWorked: N/A\n\nThere appears to be a volume of virtual space where objects do not render.\n\nLoad attached file. Set render frame to 110 and render the scene. Note the progress it makes as the large cube slowly vanishes with each render pass, while the smaller thin cube only partially renders. Set the frame to 50 and it renders fine. The problem starts with frame 106 and gets progressively worse for the large cube, while it seems to somewhat recover for the thin cube in later frames.\n\nThe problem does not repro with CPU rendering, and did not repro with my older graphics card way back when I first made this scene (GeForce 1080Ti). It repros with GPU rendering on both 3.4.1 and 3.1.0. It does not repro with motion blur disabled (hence the viewport render is also fine).\n[GPU Motion Blur Bug.blend](GPU_Motion_Blur_Bug.blend)\n", "Rendering with F12 does not consider the different resolutions in each scene\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: ATI Radeon HD 5750 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.25\n\nBroken: version: 3.4.0 Alpha\nWorked: I don't know, but even it never worked, it doesn't mean it is correct :)\n\nRender (F12) does not respect **Render Layer** node dimension\n\nI have two scenes with different dimension\n- Scene 1080 px - for rendering scene\n- Scene 2160 px - for compositing scene 1080 px\n\nScene 1080 rendered by pressing render icon at **Render Layer** node result correct with expected mix in compositor of Scene 2160 ...\n\n\n\n... but rendering by pressing **F12** in Scene 2160 renders Scene 1080 also in 2160 px (so compositor fails in result).\n\n\n\nFor more info or sample file see 2214\n\nI hope it is would be something small to fix. \nThank you for your time.\n\n- Open attached file\n- Compare rendering with F12 (which should render the two scenes at different sizes) with rendering using the render button on node\n[bse275864_OneScene.blend](bse275864_OneScene.blend)", "Cycles GPU rendering is broken on Apple M1/macOS Ventura\nOperating system: macOS-13.0-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.3.0 Release Candidate\nWorked: 3.2.2\n\nCycles GPU rendering is broken, CPU rendering works as expected.\n\nCycles - CPU:\n\n\nCycles - GPU Compute:\n\n\n1. Create any scene\n2. Switch Cycles to GPU Compute\n[simple_test.blend](simple_test.blend)\n", "Eevee Volume Artifacting\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.3.1\n\nI'm rendering some nebulae in Eevee and despite having 256 render samples, 256 volumetric samples and 128 volumetric shadow samples with 0.9 distribution and 2px tile size with proper start and end clipping distance both in camera and volume settings I'm getting really ugly flickering where the whole volume just artifacts which is really irritating. I'd love it if you could fix this issue in the upcoming blender release because even though I have a good computer it still takes 30 minutes to render the exact same scene in Cycles (where the issue is absent). watch?v=8ImqpM4zOEU\n\n[#101826.blend](T101826.blend)\n\n- Open file \n- Render animation\n\nIssue is visible after rendering ~10 frames when animation is inspected.\n\n", "gpu.states.line_width_set doesn't work (on Mac Air)\nOperating system:\nGraphics card:\n(just copy pasted specs here)\n Model Name:\tMacBook Air\n Model Identifier:\tMacBookAir7,2\n Processor Name:\tDual-Core Intel Core i5\n Processor Speed:\t1,8 GHz\n Number of Processors:\t1\n Total Number of Cores:\t2\n L2 Cache (per Core):\t256 KB\n L3 Cache:\t3 MB\n Hyper-Threading Technology:\tEnabled\n Memory:\t8 GB\nIntel HD Graphics 6000:\n\n Chipset Model:\tIntel HD Graphics 6000\n Type:\tGPU\n Bus:\tBuilt-In\n VRAM (Dynamic, Max):\t1536 MB\n Vendor:\tIntel\n Device ID:\t0x1626\n Revision ID:\t0x0009\n Metal Family:\tSupported, Metal GPUFamily macOS 1\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nBlender 3.6\n??\nOn this specific Macbook, gpu.states.line_width_set simply does nothing - Just tested also on WIndows and there it works.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nJust try the 'Operator Modal Draw' Template in Python templates in Blender text editor - the function is used there so it's very fast to check.\n\nAnd yes, I know this is probably outdated hardware, but didn't want to not report bug if I already found one ;)\n\n", "AMD GPU Denoising via \"Radeon Image Filters\" library.\n**Overview**\nThis task is to enable GPU denoising on AMD GPUs. We have a denoising library (RadeonImageFilter) publically available which operates similarly to OIDN, Optix, etc. We would like to use this to enable faster GPU denoising for users on AMD hardware. It should be noted, this library actually works on other GPUs and CPU (the latter via OIDN) but on Nvidia GPUs, the Optix denoiser will most likely be more optimal.\n\n**GPL compliance**\nWe offer the library free under a permissive Apache2 license at the link above. However, it is not open source. A shortly upcoming version of the AMD driver on windows will include this RIF library. Thus we propose to use it similarly as Optix, as a closed source \"system device\" library exception to the GPL.\n\n**Code design** \nWe added a new denoiser type, AMD Radeon Image Filter, with similar options to Optix Denoising to enable usage.\n\nPatch coming soon.", "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).", "Render difference with big quad light and ray visibility\nall vendors\n\nBroken: 1ebc14064b\nWorked: 2.79a\n\nsome parts of principled shader render very glossy in latest master\n\nOpen attached file [bug principled v2.blend](bug_principled_v2.blend), render. \nIn 2.79a you get this (correct):\n\nand in latest master this:\n\nNote that I replaced wood tex by voronoi in file, but differences are also obvious.", "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)", "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.", "Regression: mantaflow Domain \"Guides\" (velocity source) not working \nOperating system: Windows 11 Pro\nProcessor 12th Gen Intel(R) Core(TM) i9-12900K \nGraphics card: asus dual geforce rtx 3060 12gb gddr6\nRAM:32.0 GB \n\nnot worked: (3.1.2)\nWorked: (2.82.7)\n\nTo simulate the spraying of water fluid, I use the Guide Domain tool so that the water particles react with the smoke coming out of the flow and the spraying mode was simulated, but this simulation does not work in version 3.1.2, but in version 2. 82.7 works properly\nIs this a bug?\nPlease watch the videos\n[3.1.2 not work.mp4](3.1.2_not_work.mp4)\n[2.82 work.mp4](2.82_work.mp4)\n\nfile:[3.1.blend](3.1.blend)", "Blender 3.1 CPU/GPU rendering denoise is broken on M1 Mac / Monterey\nOperating system: MacOS Monterey (M1 Max)\nGraphics card: Integrated GPU\n\n**Blender Version** 3.1.0 release for M1 Macs\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (newest version of Blender that worked as expected) 2.93.3\n\nOn all my projects, when rendering via the CPU or GPU, the render works as expected, but on completion the entire screen blacks out to a solid color and the render is LOST! I suspected it must be a post render step, and I have confirmed that it is the DENOISER that is broken in this version of blender. When I go into the scene and remove the denoiser, the render completes, and I can save the image!\n\nBased on the default startup or an attached .blend file (as simple as possible).\nYou need a project that uses denoising as a final compositing step. Attached is a simple matt object set to denoise at the end. Render it, and at the end you get a gray screen. Go into compositing and remove the denoise node, and you get the render.[TestRenderWithDenoise.blend](TestRenderWithDenoise.blend)\n", "Flicker Volume Artifacts in EEVEE on RTX Cards by increasing samples\nOperating system: Windows-10-10.0.18362-SP0 64 Bits + Linux\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\nIt seems to be only on RTX Cards\n\nBroken: version: 2.83 - 3.1 (Seems to be worse since 3.0)\n\nWierd colorful artifacts every frame in volume in rendered footage from EEVEE (Not in viewport)\nBloom makes out of this artifacts a big glowing colorfull mess. \nWithout bloom you can see little white artifacts random generated around in Volume (like in old Films)\nif you have less Objects in your Scene. less Artifacts are their (Video 2).\nWhen you increase the sample rate more artifacts show up. You can use a sample rate like 1000 and you have Disco.\n\nIt is in every big volume scene (this isnt the only scene where these artifacts are. All of my scenes ,that have volume in it, have these artifacts (with bloom on, you can realy see the lightflashes)\n\nBug Report from Nvidia:\n3233904\n\nBlend file:[Scene Volume Moinster.blend](Scene_Volume_Moinster.blend)\n\n**Video much Stones (100 samples) :** [Bug wierd flikkering40000-0150.mp4](Bug_wierd_flikkering40000-0150.mp4)\n\n\n**Video less Stones (100 samples) :** [Bug wierd flikkering50000-0150.mp4](Bug_wierd_flikkering50000-0150.mp4)\n\n**Video less Stones (1000 samples) :** [Bug wierd flikkering6 1000samples0000-0150.mp4](Bug_wierd_flikkering6_1000samples0000-0150.mp4)\n \n**Other Examples:** [S1 new Exp0800-0950.mp4](S1_new_Exp0800-0950.mp4)\nI hope you can find the Problem\nThank you for your Time to make Blender better.\n**Thank you very much**", "Cycles regression testing for GPU devices\n**Background**\n\nThe Cycles automated regression tests so far only ran on the CPU.\n\nWith some environment flags it was possible to execute a script that runs them on other devices, but this is cumbersome. The goal of this task is to add a CMake option to enable running the regression tests on GPU devices in addition to CPU devices.\n\nThe reference images are currently only valid for CPU rendering. Keeping differeing reference images updated will have to wait until we have CI infrastructure for testing GPU rendering. For now we can do a few things:\n* Do nothing and manually check when tests fail\n* Increase difference thresholds for tests that only differ a little\n* Disable failing tests for GPU testing\n\n**Status**\n\n- [x] CYCLES_TEST_DEVICES option to specify devices to test\n- [x] Blacklist failing CUDA tests\n- [x] Blacklist failing OPTIX tests\n- [ ] Verify HIP tests are working\n- [ ] Enable GPU testing on the buildbot", "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" ]

[ "Volume objects not rendered on Cycles with GPU and AMD OpenCL\nOperating system: Linux-5.3.18-lp152.66-preempt-x86_64-with-glibc2.26 64 Bits\nGraphics card: Radeon RX 570 Series (POLARIS10, DRM 3.33.0, 5.3.18-lp152.66-preempt, LLVM 9.0.1) X.Org 4.5 (Core Profile) Mesa 19.3.4\nAMD OpenCL version: 20.50\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.91\n\nA volume object is not being rendered on linux using Cycles with GPU and AMD OpenCL, but is being rendered using Cycles with CPU.\n\n\n - add empty volume object and use the \"mesh to volume\" modifier to create the volume\n - hide the mesh object\n - set the render preferences to OpenCL and select the GPU\n - set the render settings to Cycles and GPU\n - render scene\n - no volume will be visible\n\nDemo file:\n[Volume.blend](Volume.blend)\n\nGPU render result:\n\n\nCPU render result:\n\n\nThis is a new bug report based on the resolved task #86610 and 91c44fe885 about Blender crashing due to nanoVDB when trying to render with Cycles with GPU and AMD OpenCL. The crash is fixed but the Cycles GPU render still doesn't show volume objects.\n\n\n\n", "Windows platform under version 2.93 amd rdna2 can not render volume ,No matter 2.93.5 or 2.93.0 there is this bug, delete opencl compile cache as no effect, 2.92 does not have this problem\nOperating system: windows10\nGraphics card ： 6800xt\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (newest version of Blender that worked as expected) 2.93.0 - 2.93.5\n\n**Short description of error** \n\n![N5J00RVL5KHUXK~1SI]PBG0.png](N5J00RVL5KHUXK_1SI_PBG0.png)\n\n\n\n\n\n{[F11579918](3_3Z6AX9___A4_5NNC4J_Q3.png)}Windows platform under version 2.93 amd rdna2 can not render volume \n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "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)", "Eyedropper values are slightly off from target color\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nEyedropper values are slightly off from target color, unless in hex mode press enter.\n\nIn attached file using eyedropper replace green color of selected strip with grey from above strip -> result is a bit darker color\nGo to hex color mode, place cursor at value and hit enter -> color is ok\n[color_picker.blend](color_picker.blend)", "White Noise Glitch using Value Attribute of Particle Instances\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\nWorked: (?)\n\nThe White Noise Texture (in 1D) does not display as expected using the Value Attribute of Particle Instances in both EEVEE and Cycles. Instead of showing a single random value or color on the surface of an instance there's a fuzzy mess of different values similar to the look of overlapping faces:\n\nThe issue also appears on non flat geometry not only on planes. The using the Index attribute shows the same result. It's the same on the current stable release (that being 2.91.2) and previous releases. I tried the same setup with a Noise Texture and it seems to work just fine:\n\n- Choose any object as the emitter of a particle hair system.\n- Adjust the settings of the particle system to display the desired quantity of hairs\n- Add another object and add a Particle Instance Modifier to it\n - under 'Object' set the emitter object\n - check 'Create Along Paths'\n - in the object data properties under vertex color create a new vertex color\n - choose the same vertex color as the 'Value' data of the particle instance modifier under 'Layers'\n- use the created data as the name in the Attribute Node\n- connect any output of the Attribute Node to a White Noise Node set to '1D'\n- display the results\n(same last 5 steps for Index Attribute)\n[ParticleInstanc_ValueAttributeBug.blend](ParticleInstanc_ValueAttributeBug.blend)\n\nThank you so much for looking into it! And keep up the great work.", "The Hair Particles interprets the color from the newer vertex domain and float color types wrong\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 512.15\n\nBroken: version: 3.3.0\n\nI am trying to modify hair color using color attribute (called as vertex color in previous versions). But hair particles simply ignores the color attribute. I just plugged in a musgrave texture and that works as expected but color attribute does not. I have attached a screenshot for a better understanding.\n\n\n\n\n", "Geometry Nodes: Color mix nodes don't effect the alpha\nOperating system:\nGraphics card:\n\nBroken: 3.4.1\n\nwhenever I try doing any math with colors, the alpha isn't affected when I use the color mix node in any blend mode. \n\n1. Open blender geometry nodes.\n2. Add 2 combine color, color or whatever node with different different values for the alpha's.\n3. Use a mix color node with any operation like add, subtract etc.\n4. See that the alpha didn't change (use the spreadsheet or the hover over).", "Geometry Attributes panel in Edit Mode (design pending)\nThis task is going to adding a unified panel for editing attributes of the selected element by value in edit mode. It makes users able to pass arbitrary per-element data to geometry nodes, opening up more possibilities for procedural modeling.\n\nAll data types (int, color etc.) should be supported. \nDomain supports should match selection modes in edit mode (eg. no face corner support for meshes). \n\n## Basic\nAttributes on the active element is listed in the side panel. \nItems are grouped by domain.\n\n\n## Multiple Selection\nfor float types (float, vector, 2d vector): \n* Show a mean value computed from all selected elements. \n* Button offsets values of all selected elements.\nfor other types: \n* If an active element with a matching domain exists, show the value of it.\n* Button only affects the value of the active element.\nFill operators are provided for batch editing. It fills current button value into all selected elements.\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(", "Stucci noise texture ignores all color settings\nOperating system: Windows 10 Pro N (unlicensed so far :( )\nGraphics card: AMD 6800 XT\n\nBroken: 3.0.0\nWorked:\n\nWhen using Stucci noise as texture for density of particles, the colors properties of the texture do not apply. F.x. setting contrast to 0.1 or 1.0 makes no difference.\n\n\n\n\n\nMake a plane. Add particles. Add texture to particles. Use Stucci noise. Set as density for particles. Try to change contrast.\n[GrassyMeadow.blend](GrassyMeadow.blend)", "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)", "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.", "Sculpt Mode Border Mask Tool Todo\n## Sculpt Mode Border Mask Tool Todo\n * - [x] {icon circle color=red} When this tool is selected, it currently shows the wrong tool settings which affect the brushes, not this tool. These should not be visible when this tool is active.\n * - [ ] {icon circle color=yellow} We should add a tool setting to add/remove the mask as you drag. Currently, the only way to remove from mask, is very hidden: You drag with RMB. This could become more consistent and more discoverable if we added the same Add/Remove buttons as with other Sculpt tools", "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", "Polishing the Painting Experience\nThere are a few tasks that would enhance the texture painting pipeline that could be prioritized before advanced features like layered textures is even considered.\n\n## Existing Painting System\n\n### Small Tasks (e.g., bug fixing)\n- [ ] Graphics Tablet Lag when in Texture Paint mode in Blender 3.0 #93796\n- [ ] Undo bugs\n - [ ] Undo eliminates brush texture #88592\n - [ ] Texture paint undo can changes texture slot #62520\n - [ ] Texture Paint mode tools swap when exiting maximized area #98014\n- [ ] Color space support for texture painting #95797\n- [ ] Sync Image Sequence options (Frames, Start Frame, Offset, Cyclic, Auto Refresh) #109769\n- [ ] Texture paint: Bleedind around thin cuts do not fill texture #106066\n- [ ] Add support for \"Channels\" to the Images & Color Attributes #108404\n- [ ] 8/16 bit textures have different strength behavior (premultiplied problems) #101436\n- [ ] UDIM bugs [need report]\n- [ ] 3D mirroring in Image Editor\n- [ ] Other bugs (by Daniel Bystedt) [need report]\n\n### Bigger Tasks (e.g., re-designs) - need design\n- [ ] Image syncing between Editors via active image canvas #103636\n- [ ] Multi-object painting\n- [ ] Multi-object uv editing\n- [ ] Support \"viewport\" face sets in Image Editor\n- [ ] Square brush\n\n## 3D Brush\n\nRelated to #96225\n\n### 3D brush vital\n- [ ] Color sampling\n- [ ] Erase blend mode\n- [ ] Affect only visible (Show/Hide)\n- [ ] Affect Alpha option\n- [ ] Masking\n- [ ] (2D) Fill operation\n\n### 3D brush additional\n- [ ] Feature parity\n - [ ] Blur & Smear brushes\n - [ ] Clone brush\n - [ ] Sync masks and edit mode selection\n - [ ] Paint modified geometry instead of base mesh\n - [ ] Missing brush settings\n - [ ] Stencil masking\n- [ ] Image editor syncing\n- [ ] Dedicated paint mode\n- [ ] Performance\n\n", "Support Face color attributes for painting\nFace color attributes should be supported for sculpt painting and vertex paint mode.\n\nThey should also be listed under the Color Attributes UI List.\n\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" ]

[ "Texture Paint Color Picker Interpreted as Gamma Corrected\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 465.89\n\nBroken: 3.0.0 alpha\n\n**Description of Issue**\n\nI'm not sure if there is a bug, if there is a doc issue or neither so I'm asking in multiple places.\n\nThe Blender Documentation states: \n\n> In Blender, the RGB and HSV/HSL values are in Scene Linear color space, and are therefore not Gamma corrected. On the contrary, Hex are automatically Gamma corrected for the sRGB Color Space. For more information, see Color Management.\n\n\n> Note that Vertex Paint works in sRGB space, and the RGB representation of the same colors will be different between the paint tools and the materials that are in linear space.\n\n\nBut when painting to a linear texture target in texture paint mode, RGB colors appear to be interpreted as gamma corrected srgb for display. Then converted to linear before painting.\n\nThis is evident from the color values when using the color sampling tool in image view mode:\n\n\n\n\nThis also seems to be supported by the fact that in code, `brush.color` is converted to linear using `IMB_colormanagement_display_to_scene_linear_v3` in image editor texture paint mode.\n\nIn paint_image.c L404, the color_correction condition is true when the texture is linear, so the display to scene conversion is applied.\n\n```\nif (color_correction) {\n IMB_colormanagement_display_to_scene_linear_v3(color, display);\n}\n```\n\nIf the color picker is gamma corrected whilst in this mode, it's confusing to for the user because the documentation states otherwise.\n\nTo add to the confusion, brush.color has a `PropertySubType` of `PROP_COLOR_GAMMA` but is converted to linear before use.\n\nThe code states that `PROP_COLOR_GAMMA` \"is used for colors that would be color managed before display\". Therefore I'm interpreting that colors with the type `PROP_COLOR_GAMMA` are Linear - they will be gamma corrected before display.\n\nAm I interpreting this incorrectly!?\n\n*Sorry for the long description.*\n\n**Steps to see discrepancy**\n\n - From start-up create an image in texture paint mode, with a floating point buffer. This should be linear.\n - Go into image paint mode\n - Select the rgb(0,5, 0.5, 0.5) from the color picker\n - Paint a stroke so that you can sample it\n - Go back to image view mode and use the sample tool to check the color values before and after color management\n - You will see that the unmanaged color values are 0.214 and the color managed values are 0.5\n - Now turn off color management in the render properties tab\n - Paint another stroke with the same color\n - Sample the colors again and you will see that both the unmanaged color and the managed color have values of 0.5.\n - This is evidence that the color is converted to linear. Is this a bug or a design decision?\n", "Texture painting uses wrong values from picker\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83.0\n\nColour picking while painting in the Image Editor commits the *linear* RGB values as *colour managed* - which causes their linear counterparts to differ from what we chose.\nWhile this is desirable for colour channels like Base Color, SSS, and Emission, it's the polar opposite of what we need for data channels like Roughness, where we know exactly what linear values we want, and no conversion should ever happen.\nIt's as simple as placing a dropdown in the colour picker, offering us the choice between linear and display space.\n\n\n\n1. Create a 32-bit float image data block in the Image Editor, set its mode to Paint.\n1. Since we're painting a 1D data channel, pick a grayscale 'colour' of 0.5\n1. Paint on the canvas. The Image Editor now assumes we want to store what we see.\n1. Switch the Image Editor mode from Paint to View and hold RMB over the gray pixels.\n1. Their colour managed values are 0.5, but their linear values are now 0.214" ]

[ "Particle hair with density influenced by texture is (partially) invisible with cycles CUDA backend\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.0.0 up to latest (version: 3.3.0 Alpha)\nWorked: 2.9.3 (from memory since these blend files can no longer be opened)\n\nThe particle hair in the given example file does not show up properly when switching to rendered preview using GPU compute and CUDA specifically. Switching to Optix, or CPU render makes the hair appear shaded. With not showing up properly I mean that the grid lines behind the hair does get obscured (only very faintly visible in the screenshots), but they are clearly not shaded. Disabling texture density influence also makes the hair appear in the GPU compute and CUDA combination.\n\nI understand that the particle system is deprecated, but figured I might as well report this issue so it does hopefully not occur in the replacement.\n\n 1. Open the attached blend file. \n\n [hair_invisible.blend](hair_invisible.blend)\n 2. Make sure that CUDA is used as the GPU compute backend, and that the device is set to GPU compute.\n 3. Switch to rendered view.\n 4. Observe that the hair is only obscuring the grid lines, but not shaded. Next there are several possibilities.\n\n 5. Switch to CPU backend for cycles and observe that the hair appears.\n 7. Or, disable texture density influence and observe that the hair appears.\n\n 8. Reduce the children to 23 and observe that some part of the hair appears within some bounding box. Further reducing the children makes it appear and disappear occasionally until everything appears (as above) at 9 children.\n\n", "Undo, Sculpt mode options reverts back with wrong order and simultaneously\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: 2.93.1\n\n\n\nTo reproduce:\nWith sphere\n1. Go to sculpt mode\n2. Make a stroke\n3. Change an option (remesh/options)\n4. Make another stroke\n5. Press Undo or {key Ctrl+Z} twice \n\nExpected: one stroke and one option change will be rolled back.\nActually: option wasn`t reverted, but both strokes do.\n\n6. change few options\n7. Press Undo: you will go back to object mode and all options from the Remesh panel will be reverted.\n\n[2021-07-29_11-11-37.mp4](2021-07-29_11-11-37.mp4)\n\n\n", "2.91 - Undo in Sculpt Mode switches tool to inflate brush (specific to attached file)\nOperating system: Win 10 64-bit\nGraphics card: Nvidia GFX 1060 6GB\n\nBroken: \n - 2.90.1\n - 2.91.0, from steam, seems *file specific*\n - 2.92.0\nWorked: 2.91.0, same version, fresh file\n\nWith attached file: In sculpt mode calling undo changes the tool to \"Inflate\" besides undoing.\n\nAdditionally, when undo is called via menu, the undo operation happens only when undoing so far back sculpt mode was entered. On reentering Sculpt Mode, tool is set to \"Inflate\". \n\nThis issues seems to be tied to this specific file, as it's not reproducible in a fresh file. The file was created with blender 2.91.0. I sculpted multiple objects using both Dynamesh and Remesh in Sculpt Mode. I deleted the sculpts to keep the file size small and since the same behavior persisted with newly created geometry (in this case a cube). I don't know how to debug this any further, any hints appreciated. As a workaround I will try to reimport the geometry into a new file.\n\nBased on the attached .blend file [SculptModeBug.blend](SculptModeBug.blend)\n\nUndoing with shortcut:\n - Select object \n - enter sculpt mode\n - select any other tool than \"Inflate\"\n - modify mesh with tool\n - hit ctrl + z\n - tool switched to \"Inflate\"\n\nUndoing via menu:\n - Select object \n - enter sculpt mode\n - select any other tool than \"Inflate\"\n - modify mesh with tool\n - modify mesh with tool\n - call \"undo\" from menu \"edit/undo\" - this has no effect\n - call \"undo\" from menu \"edit/undo\" until the point object goes back to Object Mode - changes get undone\n - On entering Sculpt Mode again, the active tool has switched to \"Inflate\"\n", "Unable to get object to stay hidden while new mesh tool is active.\nWindows 10, 1060\n\nBroken: 2.80 master (also reproduced in a month-old daily build, so not new behavior).\n\nIf you have an active tool like Add Cylinder going, and you hide another object using the eye icon in the outliner, then as soon as you touch the cylinder parameters, the hidden object becomes unhidden.\n\n1) From the default scene, Add a Cylinder to the scene and expand the tool properties in the lower left of the 3dview.\n2) Because the cylinder is hidden inside the cube, we can't easily see the effect of changing the tool parameters, so go to the outliner and click the eyeball icon associated with the cube to hide it in the viewport.\n3) Change any parameter in the cylinder tool properties pop-up in the 3dview. The cube reappears and the eyeball indicates it is no longer hidden.\n\nBasically any changes made to the Outliner visibility icons gets reverted as soon as you change any active tool property, (at least for the Cylinder tool). This at least unexpected behavior.", "Grease pencil stroke partially invisible until mouse-up\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\nWhile drawing in the attached scene the stroke is only partially visible. The full line becomes visible only on mouse-up\n\n* open the attached .blend\n* draw over the area with the 3d geometry behind it, only part of the line will show until you end the stroke (see video below)\n\nScreen recording of the problem: Jehz9YAXmE0\n\nBlend file: [gpdrawbug.blend](gpdrawbug.blend)\n\n", "Generated images with disabled alpha can have alpha but are saved with no alpha, losing user's work\n## Simplified Report\n\n- Create a new image with Alpha disabled.\n- Set the generated color to fully transparent.\n- Set up this image for 3D texture painting on a simple plane and paint some opaque strokes.\n- Execute the Same All Images operator in the textures slots panel.\n- The image is saved as RGB and alpha is lost, losing some of the user's work without warning.\n\nThis can be even less clear, because some operators like the Lightmap Pack operator can create images with no alpha implicitly, and the user doesn't know this until the alpha data is lost.\n\n## Original Report\n\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.3.1\n\nwhen you create a new image texture through the Lightmap Pack feature and paint on it can display as RGBA but the alpha channel gets discarded on save and reopening the file. Images created through other means (like the image shader node or the image panel) do save with alpha channel.\n\n1. go into edit mode on the default cube.\n2. UV > Lightmap pack. choose new image.\n3. in the image panel, select the image, go to the Image tab on the right, set Source to Generated and Color to Transparent.\n4. make a material using the texture. Set the alpha mode to hashed/clip/blend doesn't matter.\n5. apply it to the cube.\n6. draw something on it in texture paint mode.\n7. under Texture Slots click 'save all images'.\n8. close blender and reopen the file.\n9. the texture lost it's alpha.\n\nThe reason seems to be that lightmap pack generates an RGB file, but it can still appear as RGBA throughout blender until you hit refresh in the image panel or re-open the file. Ideally for my own workflow the lightmap pack feature would allow for creating RGBA files (perhaps an alpha checkbox if it's important for other workflows to not have an alpha channel)\n\nattached file: white cube was made through image shader node, blue cube through image panel generate option, green cube through lightmap pack.\n\n[bug.blend](bug.blend)", "Hair particles: 'Use modifier Stack' option with simple children leads to texture disappearing in cycles [interpolated children are fine]\nOperating system: Mint Tara\nGraphics card: GTX 1080ti\n\nBroken: 2.79 latest, 2.80 latest\n\nThe render engine can't read a texture while using the \"use modifier stack\" checkbox with simple children. Works fine with Interpolated or None.\n \nOpen the attached blend file.\nSet the viewport to render.\nActivate the \"use modifier stack\" checkbox.\nTexture disappears.\n\n[hair_use_modifier_stack_texture_bug.blend](hair_use_modifier_stack_texture_bug.blend)", "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", "Dynamic paint sub-steps don't work when the brush position is set in geometry nodes\n\nI believe this **may** be the same issue as T40597\n\nIn order to have a brush follow a potentially very large collection of curves in sequence, I'm using geometry nodes to set the position, which avoids the pain of having to join the curve paths or painstakingly tweak the offsets and influence keyframes for each and every one.\n\nThis works, but with sub-steps enabled it seems that the nodes are still only being updated once/frame. Or, if they are being updated, then the `seconds` input from the `Scene Time` node is being derived from the `frames` value which is clamped to an integer.\n\n\n[text_path_test.blend](text_path_test.blend)\n", "NaN in object matrix of instanced objects\nRyzen 7 3800x\n31.9 GB Ram\nOperating system: Windows 10\nGraphics card: Nvidia 2060 6GB Ram\n\nI tested the same scene out on my other box and the problem happened. Both machines are running RTX 2060s. One is a Intel box and the other AMD.\n\n**Blender Version** 2.81 and 2.82a\nWorked: Nothing has worked\n\n**Error**\nYouTube link to render glitches: e1ScHjBANLk\n\nWhenever I start a render, around frame 58 the sun shadows just disappear.\nIf I close the scene and open it back up and render the frame where the shadows disappear, it will render fine. But after about 50 or so frames the shadows disappear again. \nIt works fine in viewport. \n\n**note**\nI deleted the volume light box with just a 1000 floating sprite boxes for the dust inside the garage. After that, the issue went away all together. I then added the volume box back and the problem happened again. It must have something to do with volume lighting. The grass outside is over 12k clones using a particle hair so it has something to do with volume lighting and particles inside a object. \n\n**Files**\n[Blender_Bug.zip](Blender_Bug.zip)\nIt was 12 GB, removed extra elements and brought it down to this.\nAround frame 60 if you render the animation 1-300 the shadow will disappear. Escape the render… The viewport will continue to display the shadow. But after the shadow disappears during the render, and without closing and reopening Blender, whenever you render that frame, the shadow “sun light” is absent. \n\n\n\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).", "Switching to a mode that has a tool set which is not available for that object causes error [e.g Select Box tool is available if paint mask is enabled, if it is disabled it causes error]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0\n\n[when i try open vertex paint or weight paint , brush and color bar not coming to viewport]\n\n[after basic modeling something i apply all modifer and try to create uv but i cant do properly. So after unsuccessful attempt i tried to paint weight paint but color and other bar not coming to screen. But if i create new blend file and append it. Also work and i can create but after some paint also broke vertex paint file and mine locak vertex paint parts gone. btw i also cant open in new file as link...\n\n[try_007_gun.blend](try_007_gun.blend)\n\n\n", "vertex group re-appears, after it was previously removed via the API\nOperating system: Linux-4.15.0-175-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.3.1\n\nI have an object with 2 bevel modifiers. Each one uses it's own vertex group to control the beveling.\nI have a script that applies the first mod in the stack, and then removes its vertex group as well.\nIf you run this script 2 times, both mods, and both vertex groups should be removed. \nCuriously, while the modifiers are both removed successfully, the first vgroup will reappear after the second run of the script, so after the 2nd mod and vgroup have been removed.\n\nTo workaround this, you can toggle into edit mode and back into object mode at the beginning of the script.\n\nPossibly related to the commits mentioned here: T93896 ? \n\n[video demo ](BNwfPiyczdg)\n[bevel_vgroups.blend](bevel_vgroups.blend)\n\n* open the attached blend file\n* verify how each bevel mod is related to a vertex group sharing its name\n* run the script two times, and notice how the first vgroup reappears at the end\n\n", "Tool 'builtin_brush.Draw' not found for space 'VIEW_3D' warning\nOperating system: Win 10\n\nBroken: (3.2)\nWorked: (3.1)\n\n\nHi I am getting warning similar to the following when I open the following file in 3.2 but not other version.\n\n```\nTool 'builtin_brush.circle' not found for space 'VIEW_3D'\nTool 'builtin_brush.Draw' not found for space 'VIEW_3D'\n...\n```\n\n[EmptyScene Error.blend](EmptyScene_Error.blend)\n\n\n\n- Open the first file.\n- Press T or N to open the sidebar and tool menus.\n- The warning appears.\n", "Proposal: Improving Brush Workflow in Blender\nThis is an ongoing design-topic about improving the way we handle brushes in Blender. This applies to Grease Pencil Draw Mode, Texture Paint Mode, Vertex Paint Mode, Sculpt Mode and so on. \n\n## Terminology\n\n\n**Tool**\nA tool a something that can perform a type of operation. Extrude, paint, erase, line etc are tools.\n\n**Brush**\nA brush is essentially a preset for tools. As an example, the draw tool has a bunch of options for stroke width, textures, curves, spacing and so on. A brush acts as a preset to set these various settings which can be combined to create infinite combinations of settings. Brushes act as a way to save and reuse these tool presets.\n\n\n## Problems\nThe way we handle brushes in Blender is has some issues:\n\nIn the toolbar, we directly select brushes, rather than the tools they belong to. This means we mix up brush icons and tool icons in confusing ways. In fact, the brush icons currently can’t update to reflect changes in brush settings, making the icons go out of sync if you make changes to the brushes. It also makes it so the list of tools in the toolbar becomes very long, because we mix both tools and brushes, and there’s a toolbar entry for every brush variation. So if you use Sculpt Mode, and want to make three brushes for the Smooth tool, the Smooth tool now has three copies in the toolbar, all with the same Smooth icon. That is not great.\n\nEven worse, sometimes we don't even put tools inside the toolbar, because of this clash. Case in point: In the Grease Pencil Draw Mode, the Line, Oval & Rectangle tools are placed in the header, not the toolbar, which has the brushes instead. The distinction between tools and brushes is unclear and often swapped around in inscrutable ways. \n\n## Proposal\nWe can make this much more straight forward to use, and much more powerful, like so:\n\n*In the toolbar, we only show the tools.*\n\nThe brushes then become a property of the tool, and can be selected in the tool settings/top bar. This means we can make nice generic icons that represent the tool, and then dynamic brush icons in the brush popover that updates to reflect the changes in settings, like this:\n\n\n\n*Here you can see the list of tools on the left, and the brushes popover in the top bar.*\n\nHere's a more visually complete version:\n\n\n\n\nThis is using Grease Pencil Draw mode as an example. With this change, we can now properly put the Line, Oval and Rectangle tools inside the toolbar and make the brushes separate, so they can apply to any of the tools used. \n\nIn the Tool Settings, we can display an expanded version of the Brushes popover to quickly switch between brushes:\n\n\n\nThe brush icons update dynamically to reflect the changed settings, making brushes much more useful. Users can still name brushes and share them, just as before.\n\nHere are specific examples of how the tools and brushes in the various paint modes in Blender:\n\n### Grease Pencil Draw Mode\nHere we should add the Line, Rectangle & Circle tools to the toolbar, and then expose the brushes for the corresponding tools.\n\n\n\n### Texture Paint Mode\n\n\n\n### Vertex Paint Mode\nBlending Modes should become brush settings, not separate entries in the toolbar\n\n\n### Weight Paint Mode\nBlending Modes should become brush settings, not separate entries in the toolbar\n\n\n\n### Sculpt Mode\n\n\n\n\n## Quick Access\nWith this proposal, users can change the active brush using the top bar. To make switching faster, they can also directly select the active brush in the Tool Settings tab in Properties. However, when the Properties isn't visible, we could still have other quick ways to access brushes.\n\nOne idea, is to use a shortcut to bring up the same brush panel with previews, and users can select brushes from here. We could even enable shortcut keys here, so that typing any number on the keyboard would enable a given brush.\n\nThe exact shortcut can be defined as part of the keymap, and can be decided separately. \n\n\n### Switching Brushes\nIn order to make switching brushes in Blender fast and fluid, we should provide an expanded list UI, so that users can directly click on any desired brush directly, without having to open up a popup to do so every time. The *dynamically generated* **brush previews** help the user to know what the brush will look like.\n\n\n\nNow that all the tools in our paint modes are expanded and directly available in the toolbar, we can add an affordance so that users can hold down on the tool to get a fly-out popover to set the brush, like so:\n\n\n\nHere's an example of the same thing in Sculpt Mode:\n\n\n\n\nBy default, we only show brushes that are relevant to the active tool. When switching brushes, you don't expect the tool to change, only the brush, and this approach makes it easier to categorise brushes. \n\nHowever, there are some situations where it can be useful to quickly jump between specific brushes across several tools. We can support this by having a toggle to enable viewing all the brushes in the current mode:\n\n\n\nWith this enabled, we can still display the tool that the brush will activate when you enable it, using the tool icon here:\n\n\n\nSomething we can do to aid in switching and organising brushes, is the ability to group them by category. If a user has, say 200 brushes, keeping them all in one list is not tenable. Therefore, we can support a way to give each brush a category tag name. At the top of the brush selector, users can then switch between these categories:\n\n\n\nAnother thing we can do here, is add a way that users can favourite certain brushes they may use a lot, even if they are in different categories. By clicking the heart symbol, the brush is added to the favourite brushes category:\n\n\n" ]

[ "2.80 Sculpting tool size indicator circle missing \nOperating system: Windows 10\nGraphics card: NVIDIA GTX 980\n\nBroken: 2.80\n\nThe sculpting tool size indicator circle is not being rendered after opening a file, that has been saved in the sculpting workspace.\n\nOpen Blender\nSelect Default Cube\nGo into Sculpting Workspace\nSave file\nOpen file\nNow the tool size indicator circle is not being rendered\nSwitching the Workspace and than back to the Sculpting workspace fixes the problem." ]

[ "Image Editor in Mask mode: Toolbar broken \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\nImage Editor in Mask mode: Toolbar broken \n\n- Open the Image Editor\n- Change the UI mode to Mask.\n- Add a new mask.\n- Toggle Toolbar(T).\nNotice that the Adjust Last Operation pop up i moving but no Toolbar becomes visible.\n{[F11089235](mask.gif),size=full}\n\n\n", "Regression: Texture slots thumbnails in Texture painting mode are missing\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.59\n\nBroken: version: 3.3.0 Alpha\nCaused by 8b7cd1ed2a\n\nTexture slots thumbnails in Texture painting mode are missing\n\nIn Texture Paint mode, create texture, begin to paint, save texture and blender file. In the active tools panel>Texture Slots, the texture appears as a generic icon and its name, in 2.90 there was a thumbnail of the created texture instead of a generic icon.\n\n\nimages for reference:\n\n\n", "Deformation checkbox should be visible but isn't\nI discovered this in 2.76, I upgraded to the official 2.78c release and it's still there.\n\nFor Rigid bodies of Shape `Mesh` there is a `deform` option that is only visible for Source of type `Deform`.\nHowever, this option can affect other Source types.\n\n\n**Steps to reproduce**\n - Open blender\n - Make the starting cube a rigid body\n - Check the \"animated\" box (so it doesn't fall away).\n - Set the shape to `\"Mesh\"` inside \"Rigid body collisions\"\n\nnote that a `\"deforming\"` checkbox has appeared just below.\nThat checkbox disappear with `\"Final\"` and `\"Deform\"`, but still has an impact on the simulation.\n\n---\n\n**Edit: Developer note:**\n\n> In #51233#457199, @sreich wrote:\n> This is intentional behaviour. \"Final\" includes generative modifiers which don't just deform the mesh but generate a new one.\n> Now we could do shenanigans like rebuilding the collision shapes every frame, but that would be extremely slow and unstable.\n> \n> As for convex hulls, they don't support deformations so everything is fine there too. Again, we could rebuild the shapes during simulation, but as already said, it's a bad idea.\n> \n> Making the checkbox greyed out is possible, but I'm not sure if it's a good idea, maybe a question for the UI team?", "Proposed Size Preference for Color Picker\nI had fixed a bug that allows the [eyedropper to work in popups](105387). That led to other fixes, like [problems with positioning](106122) and that it can't currently work [outside Blender windows](105324).\n\nBut this work prompted some users on BlenderArtists to mention that it is [too small](589).\n\nWhile playing with the idea of making it user configurable, I came to agree that it is easier to use at a larger size that we have it now. This becomes especially important when users have very large monitors that are then used at a relatively small scale. This can give you a very large working area but a very small color picker.\n\nThe following capture was taken at 1.0 scale and shows it at the current size, a size that I liked much better, and then even larger:\n\n\n\nThere is a PR that can allow testing this: 106135\n\n", "Paint Mode: Pixel Brush Tool\nThis task design is about adding a pixel brush tool as a potential solution to the current limitation in texture paint mode to not being able to paint textures in a pixel art style not even able to paint single pixels.\n\n\nBefore looking into this solution let's check anothe non-pixel-brush-tool alternative and see the pros and cons of each one so we reach a conclusion.\nFeedback and new ideas are welcome!\n\n\n**SOLUTION 1 - REFACTOR and EXTRA ADDITIONS:**\n- Replacing current brush radius (which is strange IMHO) to brush size. This will make possible to have brushes with 1px size (diameter) to paint single pixels.\n- Add alternative squared paint cursor display over cursor settings to have a better feedback.\n- Add AA toggle as a unified paint setting to make possible paint in pixel art with any brush and size.\n- Add pixel grid overlay in the overlays panel.\n\n**CONS:**\n- Cursor isn't aligned with pixel grid.\n- So much options user have to configure before doing pixel art. (cursor, AA, pixel grid...)\n\n**SOLUTION 2 - PIXEL BRUSH TOOL:**\n- To have a dedicated pixel brush tool independent from current paint brush. This tool will behave differently.\n- To paint single pixels and blocks/chunks of 2x2, 4x4, ... pixels.\n- To paint pixel art patterns and gradients.\n- Dedicated pixel grid overlay which will be automatically enabled depending on zoom or pixel size in screen space.\n- Align brush automatically to the pixel grid.\n- No need to pre-configure anything.\n\n**CONS:**\n- Align cursor to pixels in 3d viewport may be a lot of fun BUT extremely useful.\n\n--------------------------------\n\n**CONCLUSION:**\nIn conclusion, having a separated tool will be most suitable as a pixel brush needs specific behaviours, as a squared cursor, aligned cursor, pixel grid overlay and no AA brushes.\n\n--------------------------------\n\n\n### Let's talk about the PIXEL BRUSH TOOL solution!\n\nI've made a few prototypes in Python so I can give you all an idea of how it could behave:\n\n**• Pixel Grid Overlay**\n\n A grid per pixel.\n\n A grid per chunks of 4x4 pixels (or whatever configured by user).\n\n**• Align Brush Automatically to the Pixel Grid**\n[ezgif.com-gif-maker (15).mp4](ezgif.com-gif-maker__15_.mp4)\n\n**• Pixel Brush Tool overview**\n[ezgif.com-gif-maker (5).mp4](ezgif.com-gif-maker__5_.mp4)\n", "Imported SVG dimensions are incorrect after scaling and undo\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 2070\n\nBroken: 2.93.1\nWorked: 2.80 also has this issue, the older versions are not working on my computer.\n\nImported SVG dimensions are incorrect after scaling and undo. After toggling edit mode this issue can't be reproduced anymore.\n\nSeems to be caused by `BKE_nurb_minmax` because `use_radius` is true\n\n\n\n- Import svg file (as curve, not GP)\n- Open side panel > Item tab, note initial dimensions\n- Scale imported object\n- Undo scale\nDimensions are incorrect.", "Switching to a mode that has a tool set which is not available for that object causes error [e.g Select Box tool is available if paint mask is enabled, if it is disabled it causes error]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0\n\n[when i try open vertex paint or weight paint , brush and color bar not coming to viewport]\n\n[after basic modeling something i apply all modifer and try to create uv but i cant do properly. So after unsuccessful attempt i tried to paint weight paint but color and other bar not coming to screen. But if i create new blend file and append it. Also work and i can create but after some paint also broke vertex paint file and mine locak vertex paint parts gone. btw i also cant open in new file as link...\n\n[try_007_gun.blend](try_007_gun.blend)\n\n\n", "Cursor size for \"Use Cursor for Depth\" in Sculpt doesn't reset properly on undo\nOperating system: MacOS 11.6\nGraphics card: Radeon RX 580 8 GB\n\nBroken: 2.93.4 (2.93.4 2021-09-01)\nBroken: 2.93.5 (2.93.5 2021-10-05)\nBroken: 3.0.0 (3.0.0 2021-10-05)\nWorked: don't know\n\n\nCursor size for \"Use Cursor for Depth\" (Sculpt -> Box/Lasso Trim -> Trim Mode: Join) doesn't reset properly on undo.\n\nBased on the default startup\n\n- File -> New -> Sculpting\n- Select Box Trim (or Lasso Trim)\n- In tool options, select Trim Mode: Join \n- In tool options, select Use Cursor for Depth\n\n- Use tool on the outside of the object (Note that the geometry created has a volume)\n- Undo (if you used the tool more times, repeat the undo each time).\n- Use the tool again. \n\nExpected result:\nTool works normally after all undo.\n\nActual result:\nAfter undoing all tool uses, the tool disregards the cursor size and the next shape created is flat/collapsed. \n\nAdditional notes:\nIt only happens when the file starts in Sculpt mode (hence the New -> Sculpting). If started in Object mode, and then switched to Sculpt, it is not occurring. \nAfter switching tools (even without actually using another tool), it seems to work correctly. \nAlso if switched from Sculpt to Object mode and back, it's working properly. Unless you undo from before switching to the Object mode, and undo all the tool uses, it happens again.", "Unnecessary Proportional editing in Sculpt Mode.\nOperating system: Windows-10-10.0.1709 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 and 2.82 (sub 1)\nWorked: (optional)\n\nthis is probably not a bug but more of a design since Sculpt mode now has regular transform tools.\n\nI accidentally found out that if you enable Proportional editing then going to Sculpt mode the Transform tools will show Proportional editing & it's hotkeys in the Status bar.\n\n * Enable Proportional editing in Object mode.\n * Enter Sculpt mode.\n * Use any tool of the Transform tools.\n", "Cylinder mesh (outline) will not display in ortho when viewed end on with no end caps.\nOperating system: Windows 10 64-bit\nGraphics card: Not applicable\n\nBroken: 2.80 64-bit installer 9/2/2019\nWorked: Cylinder displays correctly in version 2.79b\n\nUpon further investigation problem seems to be confined to Object mode only. Cylinder seems to display normally in Edit mode, front orthographic.\n\n**Update (9/27)**: If I add a curved path and go to Object mode to scale it to length it disappears from view in both Orthographic and Perspective views. It appears in Edit mode but the scaling works differently in Edit mode for some reason. In Object mode one end of path remains anchored when scaling on Y axis, for example, but in Edit mode scaling occurs in the positive and negative directions simultaneously.? Not a show stopper but puzzling.\nAgain, the translation and scaling icons are still visible but not the object. Other objects remain visible selected or not. Perhaps it has something to do with the selection order; just a thought.\n\nThis may not be the correct place for a suggestion about Blender version information but it could be helpful, particularly for bug reports and such to put version information in the main menu under 'About' as in other Windows apps.\n\n**Original Complaint**\nCreate cylinder mesh, 64 facets, no end faces, rotate 90d around X axis, scaled on X,Y,Z by 3 to 4. If you switch to orthographic view and try to view the cylinder end on its outline is not visible. You can see the object pivot or center of mass and any manipulation icons but not the object itself. Zooming has no effect. I could discern a couple of pixels sometimes when zooming to try to find the object but it is unknown whether they were part of the cylinder although they did display in the typical orange selection color.\n\nSimply create as described above and the results should be the same. No apparent issues result when same cylinder is created in version 2.79b.\n", "Update \"Input Samples\" settings as brush data\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\nCurrently the brush setting \"Input Samples\" (`tool_settings.sculpt.input_samples`) is stored in `bpy.data.scenes[\"Scene\"]`.\n\nTo follow useful conventions with other brush settings, this should be updated to be stored in `bpy.data.brushes[\"Brush\"] instead. For the use case of having the input samples unified between all brushes, an additional scene property `bpy.data.scenes[\"Scene\"].tool_settings.unified_paint_settings.use_unified_input_samples` should be added, including a a button to toggle it in the UI.\n\nA mockup:\n\n\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)", "GPU: Design topic for displaying outline for instances\nSee 2 for discussion on devtalk\nWe might have technical reasons, but we don't need to distract users with drawing an outline around each instance.\n\nDesign topic could be should we group the outlines per original object (when using multiple objects to instance) or should we outline the object that creates the instances (eg contains the node group).\n\nPersonally I think we should have a single outline for an object. Not taking into account that it draws instances or not.\n", "Edit Dyntopo Detail Size: Add resolution value for visual feedback\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\n## Issue\n\nWhen using the `sculpt.dyntopo_detail_size_edit` on `R` while Dyntopo is set to 'Constant' or 'Manual' Detailing in the dyntopo settings, \nit can easily happen that the overlay doesn't show the wires that indicate the resolution.\nThis happens when the value is much higher than the current brush size, like when working on a very small object.\n\n\n\n## Suggestion\n\nIt would be give better feedback to the user that this is happening by displaying the 'Resolution' value\n- in the header\n- in the viewport itself, like with `object.voxel_size_edit` on the same shortcut.\n\nThe first solution would be the easiest and most consistent with other operators.\nThe second solution is also very welcome but would need the text to be placed outside of the brush cursor (Perhaps even dynamically placed depending on the availible viewport space).\n\n\n\n", "Empty object property \"Size\" should be \"Radius\"\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.0\n\n- Mesh Cube is 1 meters wide when set its \"Size\" to 1 meters when creating\n- Empty Cube is 2 meters wide when set its \"Radius\" to 1 meter when creating.\n- However the property tab for the empty cube shows \"Size\" as 1 when it really supposed to mean \"Radius\".\n\n- Add a Mesh Cube with size 1 meter\n- Add an Empty Cube with size 1 meter\n- Compare the size. The size of Empty Cube is 2 Meters when set to 1 meter\n\n" ]

[ "Sculpt brush circle disappears after saving in Sculpt workspace\nOperating system:\nGraphics card:\n\nBroken:\n2.8 Beta 12-12-2018\nHash: 16fc62e15f0\n\n\n\nWhen a .blend file is saved while in the Sculpt workspace, reloading the file will cause the sculpt brush cursor to disappear. Checking the menu shows that the brush should be visible. The only fix is to go back to object mode and then enter sculpt mode again. At this point, the sculpt brush cursor will reappear.\n\nLoad in the attached file. This is the Default cube that has had a SubD modifier applied to it. The Sculpt workspace was selected, a few brush strokes were applied, and the file was saved. \n\nWhen you load the file, you will be in sculpt mode, but you will not see a sculpt cursor. Go back to object mode and then re-enter sculpt mode. The cursor will reappear.\n\n[sculpt.blend](sculpt.blend)", "Brush radius doesn't show when opening a file that's been saved in Sculpt Mode\nOperating system: Windows 10 version 1809\nGraphics card: Geforce 980ti\n\nBroken: December 29, 01:07:02 - 7c438e5366b2\nWorked: Switching to Object Mode and then back to Sculpt Mode will make the brush radius reappear.\n\nThe sculpting brush disappears (the round circle that shows the brush radius size. See image below). This happens when you save a file while in Sculpt Mode, and then open that same file again. \n\n1. Either create a new scene, or open any file.\n2. Go in to Sculpt Mode.\n3. Go to File > Save to save the file while you are in Sculpt Mode.\n4. Reopen that same file, and the brush radius will have disappeared." ]

[ "Editing redo panel properties of torus in edit mode reverts some steps\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.24 355.11.10.50.10.103\n\nBroken: version: 3.4.1\nWorked: (never worked as expected)\n\nAdding and then adjusting a Torus or any Add Mesh add-on in edit mode reverts edits made to nodes, video sequencer, and more, since entering edit mode on the mesh object.\n\n1. Go to the Geometry Nodes workspace\n2. Select the default cube\n3. Click the New button to add the Geometry Nodes modifier and create and assign a new node group\n4. In the 3D Viewport switch to Edit mode\n5. In the Node Editor, pour your heart and soul into crafting an elaborate node tree (lol, jk 👀💔)\n6. In the 3D Viewport add a Torus\n7. Tweak any setting in the Adjust Last Operation panel\n8. Observe Geometry Nodes edits reverted (all edits since entering edit mode in the 3D Viewport)\n\nNo other built-in mesh primitives (nor even primatives!) have this effect, but the Add Mesh add-ons all do.\n\nI have checked some of the editors to see what data is reverted and what is preserved. This is not yet an exhaustive review.\nThe following data is reverted:\n- Video Sequencer\n- Properties\n- every Node editor\n- Timeline\n\nThe following data is preserved:\n- Preferences\n- Text Editor\n- Python Console\n- Movie Clip Editor\n- UV Editor\n\nThe Outliner has mixed results:\n- Hierarchy expansion reverts in Blender File, Data API, and Orphan Data but not in Scenes nor View Layer.\n\nSome editors have special behavior:\n- Image editor\n - Paint mode\n - {Add torus, paint image, tweak torus} reverts the paint\n - {Paint, add, tweak} kicks out of Edit mode into Object mode\n - Switching Image Editor modes does not close the ALO panel. The following sequence of steps produces a Python error:\n - Add torus\n - Switch Image Editor modes\n - Adjust torus\n (If this merits its own tracker issue, tell me and I will write one up. This all seems so tied to one root culprit that it is not my initial inclination to do so)\n\n", "No snapping for objects referenced in modifiers (even if disabled)\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 451.67\n\nBroken: version: 2.91.0 Alpha\nWorked: probably never; hopefully it's just an oversight. Even 2.79b is broken\n\nI've experienced this a handful of times but finally sat down to investigate from the user perspective here today (sorry, haven't looked at the code). But apparently the object you use as Simple Deform's \"origin\" will not be snap-able to the object that has Simple Deform on it. It doesn't matter if the modifier is enabled or disabled or if the settings actually produces no deformation, it always breaks snapping for the origin object.\n\n[snap-issue.blend](snap-issue.blend)\n\n- Open the attached .blend file OR follow next instructions to setup\n - Start with default scene and add an Empty to the scene\n - Add a Simple Deform modifier to the Cube\n - Set the Simple Deform's \"origin\" object to the Empty, the mode to \"Bend\" and the \"Angle\" to 0deg (to prevent any deformation)\n - Set the scene snapping mode to vertex\n\n- Grab the Empty and attempt to snap it to verts of the Cube -- it cannot snap (bug)\n\n- Disable the modifier and repeat the snap attempt -- it still cannot snap to the Cube (bug)\n\n- Create a new object and attempt to snap the empty to that new object -- it succeeds (the Sphere in the attached .blend file)\n\n- Delete the modifier and repeat the snap -- finally, it is able to snap to the Cube\n\n", "Sequencer Preview : area_join() doesn't join well\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI join two Sequencer preview areas with a script and both stay, but one is like broken. If I resize the view, it goes back as expected : the residual broken view disappears.\n\n- Open the provided blend file\n- There are two Sequencer preview views\n- Run the script in the text editor\n- The display of one view changes a bit and you cannot resize it.\n- Resize the main view, the residual view disappears.\n- NB: You can run the script again to split views and re-run it to join them again. The bug remains the same.\n\n[BugSplitView.blend](BugSplitView.blend)", "After `save as` operation with non-default options of Image, simple `save` operation does not use previous settings, but default settings again.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\n**Description**\n\nWhen re-saving a modified imaged (from Texture Painting for example), the newly saved file appears to lose all settings used during the original \"Save As\" operation. For file types such as OpenEXR that were saved as 16-bit using Zip compression, this can result in a file that was roughly 800KB becoming *64MB* in size. This wastes quite a large amount of disk space and bandwidth when using version control.\n\nImage files should remember the settings applied when loaded or from Save As. There does not appear to be a way to set global file-type defaults to reduce some of this behavior.\n\n\n* Switch to the Texture Paint workspace.\n* Click \"New\" to create a new texture. Set Width/Height: 2048x2048, 32-Bit Float: Checked\n* Switch to the \"Paint\" mode if needed and draw a circle.\n* Click Image / Save As. File Format: OpenEXR, Color: RGB, Color Depth: Float (Half), Codec: ZIP (lossless)\n* Open a File Explorer window and note the saved file size is roughly 300KB.\n* Click Image/ \"Save\" (not Save As) to re-save the file. Note the image file is now roughly 1MB. (It appears Blender has now forgot the file should be Float (Half)\n* Close Blender and Save the scene.\n* Open Blender and the saved scene.\n* Click Image/ \"Save\" to re-save the file again. Note that the image file is now roughly **50MB** as Blender appears to have lost the Codec setting and the Float (Half) setting.\n\nThis bug occurs on other file types as well such as PNG where the compression settings are lost.", "\"View\" settings not refreshing when going out of camera view\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.80 (sub 74)\n\nNot a big bug, but I'm reporting anyway.\n - Open file:\n[viewport_camera_settings_bug.blend](viewport_camera_settings_bug.blend)\n - Use middle mouse button to go out of camera view. Simple click should be enough.\n - Some of the settings in \"View\" will be greyed out until hovered over with mouse cursor:\n\n\n", "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.", "Blender crash in bmesh.to_mesh() while using it to modify weights\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\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nCrash in bmesh.to_mesh() if using it to modify weights in weightpainting while playing animation\n\n*Remove any lights or cameras, keep just one cube in the scene (for the simple script to work).\n*Subdivide it 5 times and apply the modifier.\n*Add the script below to the script editor and run it\n*Go to weight paint mode for the cube\n*Run the animation and try to paint. If you just click the left mouse button it will paint a dot and the script will work, but if you hold and drag, Blender crashes.\n\n\n```\nimport bpy, bmesh\n\n\ndef add_handler():\n # remove existing handlers\n old_handlers = []\n for h in bpy.app.handlers.frame_change_post:\n if \"paint_test\" in str(h):\n old_handlers.append(h)\n for h in old_handlers: bpy.app.handlers.frame_change_post.remove(h)\n # add new handler\n bpy.app.handlers.frame_change_post.append(paint_test)\n\ndef paint_test(scene):\n for ob in scene.objects:\n me = ob.data\n \n print(str(scene.frame_current) + \": Creating Bmesh\")\n bm = bmesh.new()\n bm.from_mesh(me)\n \n group_index = ob.vertex_groups.active_index\n dvert_lay = bm.verts.layers.deform.active\n \n for vert in bm.verts:\n dvert = vert[dvert_lay]\n try: dvert[group_index] -= 0.1\n except: pass \n \n print(str(scene.frame_current) + \": Writing Bmesh\")\n bm.to_mesh(me)\n bm.free()\n \nadd_handler()\n```", "My Blender won't open anymore\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: Every version\n\nWhen I try to open Blender the terminal appears then disappears and nothing else happens.\nBlender worked until today in all its versions, but now it no longer opens.\n\nI tried opening it as administrator, on different versions. I restarted my PC. I updated my drivers. There no bug/crash report or anything.\n\nI don't know what to do.\n\n", "When loading factory defaults, Render Dimensions preset dropdown menu is not reset\nOSX\n\n2.73a\n\nWhen loading factory defaults, Render Dimensions preset dropdown menu is not reset\n\n\n- Change Scene Dimensions to a preset\n- Maybe change a couple of settings like x resolution to see changes later on\n- Reset to factory default\n- Observe change of X, Y Scale etc of Scene Dimensions Resolution to default\n- Observe Preset dropdown choice still on previous setting before factory default..\n\n\nJust a little teenie weenie thingie.. I know, but thanks for looking into it!\nCheers and thanks again for developing worlds' greatest application!\n\nRoel\n", "2.8 Cycles viewport Ray Visibility is not updated in viewport when changed by Python\nOperating system: Mac OSX, 10.13.6 (a MacBook Air)\nGraphics card: Intel HD Graphics 5000 1536 MB\n\nAlso tried on a linux virtual machine (Ubuntu), same issue\n\nBroken:\nMac build: 2.80.43, build 2019-02-01 22:37\nLinux build: 2.80., 2019-02-15 7:29\nWorked: 2.79, unsure if there was a working version of 2.8\n\n\nWhen updating an object's CyclesRay visibility (e.g. camera visibility) via python from a script or console, there is no impact in the viewport; while the UI as well as render will reflect the changed state of the setting (checking or unchecking the box), the visibility will not have changed in the viewport. Note: this is only an issue for the viewport, when rendering it will reflect the setting update properly. The issue persists even between leaving and re-entering rendered mode in the viewport, until the user manually clicks to toggle the UI setting directly which resolves the problem.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1) Open default scene\n2) Open console window/scripting workflow,\n3) Enable cycles and enter a viewport into rendered mode\n4) With Default cube selected, type: C.object.cycles_visibility.camera = false\n5) Notice how viewport scene does not update; but if you move the mouse over the property panel:Objects/Cycles settings, you'll see the draw refresh will show the camera visibility turns off\n6) Exit and re-enter rendered mode in the viewport, to find the issue persists (cube is visible to camera)\n7) Press render to notice that the setting however is reflect in render (cube will not be visible to camera)\n8) Manually toggle the camera visibility setting in by clicking the tick box twice, to verify the setting works when done by hand; and see that now the cube does not appear in the viewport (as expected).\n9) Repeat for reverse; ie turning setting to True when initial camera visibility is false.\n\nNote I also tested this and found the same issue with the Glossy visibility using a similar process (adding a mirror-like object next to the cube), so I expect this is true for all of the cycles object visibility settings. \n\nVideo demonstration, happens in any scene including the default\nview?usp=sharing\n\nWhile I agree this is less of an issue since ultimately the correct results appear in render, this is an issue for addons that control this setting and confuse the user as prior to render, there then appears to be a discrepancy between the viewport visibility and the panel settings. ", "Uncheck Save Copy freezes on next render - Mutex is still locked\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\n2.90.1 and 2.83.5 have the same behavior\n\nWith default scene :\nWhenever I try to save a render, I uncheck both save as render and save copy, the next time I hit render, blender will freeze.\n- Unticking save as render only does not seem to create the freezes, however the option is not saved, I have to manually uncheck it every time.\n\nNew file : \n- Save file\n- Hit render\n- Save as\n- Uncheck Save as Render and Save Copy\n- Save.\n- Hit Render again = freeze\n\n\n", "Image scale is reset after rendering in background mode\nOperating system: Windows 10\n\nBroken: 2.91.2\n\n\nI am starting Blender from command line in background mode (-b) and execute a Python script which does the following:\n* Load an image\n* Scale the image\n* Render with Cycles\n\nAfter the rendering is done, *it is as if the image scaling never happened.* The image is back to its original size, and if I save it, it is identical to the original unscaled image.\nSo it looks like somewhere during bpy.ops.render.render(), the changes to the image are undone.\n\n*This only happens when Blender is started in background mode.* If started without -b argument, the problem does not occur.\n\n\nDownload this test image: \n\nRun Blender from command line with the following command. Replace path to Blender executable and path to the test.jpg image with the correct paths for your machine, i.e. replace the following strings:\n* `\"C:\\Program Files\\Blender Foundation\\Blender 2.91\\blender.exe\"`\n* `C:\\Users\\Simon\\Downloads\\test.jpg`\n\n```\n\"C:\\Program Files\\Blender Foundation\\Blender 2.91\\blender.exe\" --factory-startup --addons \"io_import_images_as_planes\" -b --engine CYCLES --python-expr \"import bpy; import bpy_extras; image = bpy_extras.image_utils.load_image(r'C:\\Users\\Simon\\Downloads\\test.jpg', check_existing=True, force_reload=False); print('original size:', image.size[:]); image.scale(99, 99); print('before render:', image.size[:]); bpy.ops.render.render(); print('after render:', image.size[:]);\"\n```\n\n**With -b flag**\n\nBlender will print a log like this:\n\n```\n\"C:\\Program Files\\Blender Foundation\\Blender 2.91\\blender.exe\" --factory-startup --addons \"io_import_images_as_planes\" -b --engine CYCLES --python-expr \"import bpy; import bpy_extras; image = bpy_extras.image_utils.load_image(r'C:\\Users\\Simon\\Downloads\\test.jpg', check_existing=True, force_reload=False); print('original size:', image.size[:]); image.scale(99, 99); print('before render:', image.size[:]); bpy.ops.render.render(); print('after render:', image.size[:]);\"\nBlender 2.91.2 (hash 5be9ef417703 built 2021-01-19 16:25:50)\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.91\\2.91\\python\noriginal size: (712, 400)\nbefore render: (99, 99)\nFra:1 Mem:47.08M (Peak 47.15M) | Time:00:00.00 | Mem:0.00M, Peak:0.00M | Scene, View Layer | Synchronizing object | Cube\nFra:1 Mem:47.09M (Peak 47.15M) | Time:00:00.00 | Mem:0.00M, Peak:0.00M | Scene, View Layer | Initializing\nFra:1 Mem:46.97M (Peak 47.15M) | Time:00:00.00 | Mem:0.00M, Peak:0.00M | Scene, View Layer | Waiting for render to start\nFra:1 Mem:47.00M (Peak 47.15M) | Time:00:00.00 | Mem:0.00M, Peak:0.00M | Scene, View Layer | Loading render kernels (may take a few minutes the first time)\n\n[... cut out unimportant output ...]\n\nFra:1 Mem:49.34M (Peak 50.97M) | Time:00:09.92 | Remaining:00:00.01 | Mem:2.09M, Peak:3.57M | Scene, View Layer | Rendered 505/510 Tiles\nFra:1 Mem:49.23M (Peak 50.97M) | Time:00:09.92 | Remaining:00:00.01 | Mem:1.98M, Peak:3.57M | Scene, View Layer | Rendered 506/510 Tiles\nFra:1 Mem:49.12M (Peak 50.97M) | Time:00:09.93 | Remaining:00:00.00 | Mem:1.87M, Peak:3.57M | Scene, View Layer | Rendered 507/510 Tiles\nFra:1 Mem:49.01M (Peak 50.97M) | Time:00:09.94 | Remaining:00:00.00 | Mem:1.76M, Peak:3.57M | Scene, View Layer | Rendered 508/510 Tiles\nFra:1 Mem:48.90M (Peak 50.97M) | Time:00:09.95 | Remaining:00:00.00 | Mem:1.65M, Peak:3.57M | Scene, View Layer | Rendered 509/510 Tiles, Sample 128/128\nFra:1 Mem:48.78M (Peak 50.97M) | Time:00:09.96 | Mem:1.53M, Peak:3.57M | Scene, View Layer | Rendered 510/510 Tiles\nFra:1 Mem:48.78M (Peak 50.97M) | Time:00:09.96 | Mem:1.53M, Peak:3.57M | Scene, View Layer | Finished\nFra:1 Mem:47.17M (Peak 50.97M) | Time:00:09.96 | Sce: Scene Ve:0 Fa:0 La:0\nafter render: (712, 400)\n\nBlender quit\n```\n\nYou can see that the image is loaded, the original size (712, 400) is printed, then after scaling and before rendering, the correct new size (99, 99) is printed, and then again after rendering, the old and now incorrect size (712, 400) is printed.\n\n**Without -b flag**\n\nWhen run without -b flag, we get the following output where Blender behaves correctly:\n\n```\nC:\\Users\\Simon>\"C:\\Program Files\\Blender Foundation\\Blender 2.91\\blender.exe\" --factory-startup --addons \"io_import_images_as_planes\" --engine CYCLES --python-expr \"import bpy; import bpy_extras; image = bpy_extras.image_utils.load_image(r'C:\\Users\\Simon\\Downloads\\test.jpg', check_existing=True, force_reload=False); print('original size:', image.size[:]); image.scale(99, 99); print('before render:', image.size[:]); bpy.ops.render.render(); print('after render:', image.size[:]);\"\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.91\\2.91\\python\noriginal size: (712, 400)\nbefore render: (99, 99)\nafter render: (99, 99)\n```\n\n**The script in more legible form**\n\nHere's the script that is passed to --python-expr, expanded to be more legible:\n\n```\nimport bpy\nimport bpy_extras\n\nimage = bpy_extras.image_utils.load_image(r'C:\\Users\\Simon\\Downloads\\test.jpg', check_existing=True, force_reload=False)\nprint('original size:', image.size[:])\n\nimage.scale(99, 99)\n\nprint('before render:', image.size[:])\nbpy.ops.render.render()\nprint('after render:', image.size[:])\n```", "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", "Blender card only showing a default cube when open even the file size is 100 mb\nI am working on a blender file on my pc . The file size is almost 100mb . I saved the file. But when i opened it again the file is just showing a single default cube. No layers no anything. Just default interface. My file was just having the room interface . It consists of some free models also which i downloaded from the internet. Like free 3d website like sketchfab. \nThis thing happened with me 1 week ago. But then i made the file again and get my pc hard disk and windows changed. And now it happened with me again. I dont know what to do. Please tell me what to do to recover my file and to prevent this issue next time.\n\ni was able to recover it through .blender1 format but still i know this will happen again. please guide me on this, i have not added anything in my addons also \n\nblender 3.6 version \ngraphic card 750 Ti \nWindows 10 \nnew hardrive of 250 gb\n\n", "blender 4.0 shutdown immediately after launching\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nblender 4.0 latest build shutdown immediately after launching . and i think its cant overwrite the file showing in the image .when i deleted that file and try to launch blender its work just fine . after doing some stuff blender got crashed 🙃 and the same thing happen again (can`t launch) and so i have to do the same method to get it to work again 🙂👌\n\n----\n\n" ]

[ "fresh install of blender 2.83.0 not able to save user startup file \nOperating system: Windows 10 ver 1909 and 2004, Archlinux with KDE\nGraphics card: GeForce GTX 1060\n\nBroken: \n```\n Windows: 2.83.0 211b6c29f771, from both official website download, installer and zip version both tested. Also tested with blender-2.90.0-e079bf6996fc-windows64, still can reproduce the issue.\n Archlinux: 2.83.0 211b6c29f771, package version17:2.83-1 from Archlinux official repo\n```\n```\n Windows: 2.82a 375c7dc4caf4.\n```\n(all build hash are get from `blender --version` output).\n\nFresh install of blender 2.83.0 not able to save user startup file.\n\n\n - Make sure your computer never run blender 2.83 before, or by remove all the files under '%APPDATA%\\Blender Foundation\\Blender\\2.83\\config\\' for Windows (or '~/.config/blender/2.83/config/' for linux)\n - Open blender 2.83 by double clicking the blender.exe executable.\n - Just delete the default cube.\n - Click File>Defaults>Startup File, click Save Startup File.\n - Close the program and re-open it.\n - Check the result (the default cube is still there).\n\nI notice that in the user config folder, there are no userpref.blend file get generated, so I checked my old blender user config folder and put the old userpref.blend file into the 2.83 user config folder, then I found that fixed this issue, the Save Startup File menu also works after that.\n\n - Do the above steps to reproduce the issue first.\n - Copy the working 'userpref.blend' file form my 2.82a folder '%APPDATA%\\Blender Foundation\\Blender\\2.82\\config\\' (or '~/.config/blender/2.82/config/' for linux) to '%APPDATA%\\Blender Foundation\\Blender\\2.83\\config\\' (or '~/.config/blender/2.83/config/').\n - Open blender 2.83, and we can see the default cube is deleted which means it's working.\n\nAlso, here is the userpref.blend file I used for the above workaround.\n\n[userpref.blend](userpref.blend)\n\nbtw I guess it's the same issue as T77813 . @mano-wii" ]

[ "GPU Subdivision slows down in Sculpt mode, Weight paint mode.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.1\n\nGPU Subdivision slows down the work in Sculpt mode and Weight paint mode\n\n1. Turn on the GPU Subdivision.\n2. Enable the subdivision surface modifier on the model.\n3. Try to do something in Sculpt mode, Weight paint mode.\n4. Turn off the GPU Subdivision and follow step 3.\n\nWith GPU Subdivision enabled, the Sculpt mode and Weight paint mode tabs work much slower.\nIf it can't be fixed, then it would be logical for GPU Subdivision not to be enabled on these tabs.\n\nAt the same time, the GPU Subdivision works correctly in Object mode.\n", "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", "alt brush doesn't work in image editor -> paint\ni think this should be fairly easy to reproduce so i wont bother sharing system info. i was able to reproduce this on 3.3.0 and 3.3.1.\n\nalt brush doesn't work in image editor -> paint\n\ni have a different colour on my brush but when i press ctrl and try to paint the primary colour is painted onto the canvas", "Sculpting: Ctrl+S reverts recent progress. \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0,\nBroken too: b67423f806\n\nWhen saving with ctrl+S the last changes applied to sculpt with \"grab\" brush gets reverted. This should be observed by reopening the file. \n\n- Have a sculpt with dynamic topology. Disable dynamic topology for the next step.\n- Move a part of the mesh with the grab brush.\n- Save your last progress. \n- Reopen the file using file browser. All changes done with the grab brush will be undone.\n\n\n\n[face sculpt broken.blend](face_sculpt_broken.blend)\n\nThanks, have a great day and stay healthy!", "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)", "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", "Weight gradient tool auto normalizes over locked groups\nOperating system: Linux-5.19.0-41-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: 3.6.0 Alpha\n\nWhen gradient painting over a group, the auto normalization affects other groups that are locked.\n\n[Weight Gradient Normalize.blend](attachment)\n1. Notice the weighing of the **Bone 1** vertex group.\n\n2. Select the **Bone 2** vertex group.\n3. Drag over the model to gradient paint.\n\n4. Select **Bone 1** again.\n**Bone 1** has been auto normalized even when it's locked\n", "Grease Pencil - A corrupt Sculpt > Push brush is created when undoing a mode change\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 2.90.0 Alpha\n\nA corrupt Push brush is created when I undo a Draw -> Sculpt mode change.\n\n* File > New > 2D animation\n* Change from draw to sculpt mode\n\n* Edit > Undo (the mode changes back to draw mode)\n* Change again to sculpt mode as before\n* A new corrupt Push brush has appeared called F Push (instead of F Push Stroke), and is selected. It has no thumbnail. It is missing the usual UI elements of the Push brush, like strength. See screenshot.\n \n\n", "GPencil: Inconsistent brush profile using Line/Shape tool\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.0\n\n- When certain brushes with unique characteristics like \"Ink Pen\" or \"Marker Chisel\" brush is selected, and *Draw tool* is used, the brush characteristics (thickness, frequency of effect) are appealing (image: green). \n- But when those brushes are selected, and any *Line/Curve/Shape* tool is used, the brush characteristics have undesired effect (image: red). The peaks are extreme, and the frequency of the extremes along the stroke is high (not as smooth as drawing).\n- (A) The Thickness Profile can reduce the maximum peaks, but not even-out the minimum valleys. (B) The frequency of the brush effect can't be distributed evenly across the stroke. It seems the only way to edit it is through manual sculpting. \n- The number of points (few/many) also doesn't smooth out the effect. \n\n*Also just an additional suggestion, when using line/shape tool in its edit mode (before confirmed with Enter) it would be helpful to be able to adjust its settings (Subdivision, Radius, Strength, Thickness Profile) in real-time to preview the changes - without having to confirm the stroke, undo, change settings, and apply stroke again. Only mouse-wheel scrolling, that controls subdivisions, allows preview of settings changes in real-time.\n\n\n\n", "Imported SVG dimensions are incorrect after scaling and undo\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 2070\n\nBroken: 2.93.1\nWorked: 2.80 also has this issue, the older versions are not working on my computer.\n\nImported SVG dimensions are incorrect after scaling and undo. After toggling edit mode this issue can't be reproduced anymore.\n\nSeems to be caused by `BKE_nurb_minmax` because `use_radius` is true\n\n\n\n- Import svg file (as curve, not GP)\n- Open side panel > Item tab, note initial dimensions\n- Scale imported object\n- Undo scale\nDimensions are incorrect.", "XYZ symmetry options: unclear release notes\nThe 2.91 release notes for 5502517c3c are lacking, both in clarity of the description and the discoverability of that change for the people it impacts.\n\n- The change is described in the Sculpting section, under \"[Sculpting Workflow with multiple objects](Sculpt#Sculpting_Workflow_with_multiple_objects)\". However, it is much broader than just that. Since this change also impacts weight painting, it is relevant to riggers as well. It should be described in a place such that riggers can find it.\n- The only description is \"XYZ symmetry is now a per mesh settings which is shared between all painting and editing modes\". This doesn't convey what this change means practically, it doesn't show the changes in the UI, and doesn't tell riggers how they have to change their workflow to account for this change.\n\nAs a side-note, the #animation_rigging module should have been involved in design task #79785 and the review of [D8587](D8587), since this change impacts workflow of riggers. Instead, it went completely under the radar.\n", "Impossible to weight paint certain vertices\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.47\n\nBroken: version: 3.0.0 Alpha\nBroken a7ac8a22f8\nWorked c8df6f2cf9 (huh!)\nBroken 9a85592dde\nBroken 382e7ce9ec\nBroken 2.81 release\nBroken 2.80 release\n\nToo often when weight painting it's impossible to paint over certain vertices.\n\n[Weight Paint Bug.blend](Weight_Paint_Bug.blend)\nTry to paint over the middle vertex (0 weight)\n\n\n", "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", "Expose symmetry options for operators that use them in weight paint\nCurrently there are quite a few weight paint operators that use the symmetry/mirror setting under the hood.\n\nThis is great, but we should expose this in the operator settings so that is might be easier for the user to realize that the mirror/symmetry options also influence operators if they are on.\n\nThe new exposed operator settings should use the current symmetry options from the mesh/object.\nBut the user can then see and set the symmetry value manually in the operator if they wish.\nThis can be used to create custom shortcuts/key binds that always has symmetry on or off.\n\nThe operators use `ME_SYMMETRY_X` or `ME_EDIT_VERTEX_GROUPS_X_SYMMETRY` and are in `source/blender/editors/object/object_vgroup.c` and `blender/editors/sculpt_paint/paint_vertex_weight_ops.c`.", "Switching to a mode that has a tool set which is not available for that object causes error [e.g Select Box tool is available if paint mask is enabled, if it is disabled it causes error]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0\n\n[when i try open vertex paint or weight paint , brush and color bar not coming to viewport]\n\n[after basic modeling something i apply all modifer and try to create uv but i cant do properly. So after unsuccessful attempt i tried to paint weight paint but color and other bar not coming to screen. But if i create new blend file and append it. Also work and i can create but after some paint also broke vertex paint file and mine locak vertex paint parts gone. btw i also cant open in new file as link...\n\n[try_007_gun.blend](try_007_gun.blend)\n\n\n" ]

[ "Paint mask selection buttons lack undo push\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 3.1.0 Alpha\n\nThe buttons for face or vertex masking on weight paint and vertex paint modes alck an undo push\n\nThis file is on Weight Paint mode\n[Weight.blend](Weight.blend)\nPaint on a vertex\nClick on any of those two buttons (face and vertex masks)\n\nCtrl+Z\nNot only the button press is reverted but also the vertex weight\n\nThe exact same problem exists in Vertex Paint mode\n\n\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", "Memory Leak in Blender 3.1.2 Metal CPU + GPU\nOperating system: macOS 64 Bits (12.3.1?)\nGraphics card: AMD RX 6900 XT x 2\nCPU: i9 10859K\nRam: 64Gigs (2x32)\n\nBroken: version: 3.1.2\nWorked: -\n\nI've been encountering a consistent Memory Leak using the new 3.1.2 Version, rendering in Cycles \"Metal\", on both GPUs and the CPU.\nAll rendering settings are default - the output Render samples are set to 1200 cycles.\nAll export settings are default - Resolution is set to 1920x1080 at 100%\n\nThere is no difference when Cycles Render Rate or Resolution Output is changed - I always end up with a memory leak in that I can render around 440 Frames before the memory has become full enough to suddenly increase render time. The system eventually reaches about 60.64Gigs of usage and stays there:\n|||\n| -- | -- | -- |\n\n**Workaround:** Render only 400 frames. Close Blender, restart and start the next render at Frame 401, etc.\n\n- \n\n---\nStill new to Version 3.1.2, quite different from 2.7 But I begin to really like the new layout and system - big shout out to all developers!\nJens", "Clay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop) \nOperating system:\n\nDevice name\tDESKTOP-V97J8T0\nProcessor\t12th Gen Intel(R) Core(TM) i7-12700F 2.10 GHz\nInstalled RAM\t32.0 GB (31.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\nPen and touch\tPen support\n\nGraphics card:\n\n3070 RTX\n\nBroken: 3.3.1\nWorked: 3.2.2 \n\n\nClay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop). it works fine in blender when i push Wacom Intous tablet on max with pen\n\nVideo Link: 1J_NZ0-1Qqg", "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.", "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", "GPU Subdivision slows down in Sculpt mode, Weight paint mode.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.1\n\nGPU Subdivision slows down the work in Sculpt mode and Weight paint mode\n\n1. Turn on the GPU Subdivision.\n2. Enable the subdivision surface modifier on the model.\n3. Try to do something in Sculpt mode, Weight paint mode.\n4. Turn off the GPU Subdivision and follow step 3.\n\nWith GPU Subdivision enabled, the Sculpt mode and Weight paint mode tabs work much slower.\nIf it can't be fixed, then it would be logical for GPU Subdivision not to be enabled on these tabs.\n\nAt the same time, the GPU Subdivision works correctly in Object mode.\n", "Do Not Allow The Image Resolution To Go Below 1 (or .8 at lowest)\nOperating system:\nGraphics card:\n\n2.8.3\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nI have very poor vision. Before I realized the font text box also had little arrow sizers or something, I thought you had to type in the value only.\n\nWhen trying to type 1.4, I accidentally typed .1 somehow (I couldn't see the screen with 1.0 Resolution Scale).\n\nI almost uninstalled the software, but with 15 minutes and WIndows Magnifier I got lucky and found Edit Preferences again, and another 5 or 10 minutes to find the Resolution Scale textbox.\n\nA minimum resolution scale would easily solve this, to where it cannot go below 1 in my opinion, but maybe an 18 year old with eagle eyes and a 99 inch monitor might want smaller, like .8.\n\n\nEdit - Preferences - Type .1 in Resolution Scale and hit ok.\n\nLet me know if you can solve it from there without uninstalling. Its like a pinatta game, but should never happen in the best menu font system I have ever used (I made a video giving you an A++ today, until I found this bug, I crossed off an A.\n\nThe file attached is from a Resolution Scale of .6, which I can't risk setting it any lower or I can't get it back.\n\nHere is a video link of the problem if you care to watch:\nrstH-msnuuw\n\nPlease tell me you agree Resolution Scale has no business ever being so low the software is unreadable.\n\nNew users, especially those with visual impairments worse than mine may not be aware of the little slider arrows. I noticed them on my 5th attempt at learning Blender, and uninstalled / installed each time before I found the font setting today, \n\nFive minutes later I found the font bug.\n\n\nThank you,\n\nCorby / Data Juggler", "Dynamic Paint evaluated even when disabled\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.04\n\nBroken: version: 3.3.1\nWorked: (Unknown)\n\nAfter disabling the Viewport Display and Render options for both the Canvas and the Brush in the Dynamic Paint settings, the system continues to be evaluated during timeline playback, resulting in a very low frame rate. The only way to fix this is to completely delete the **Dynamic Paint modifier** from **both** the Canvas **AND** the Brush. This is not ideal, as settings need to be tweaked in between testing an animation, so the system **should be properly bypassed** when the Viewport Display and Render options are disabled.\n\nThanks very much for looking into this!\n\n**[exact steps needed to reproduce the issue]**\n\nPlease see example .blend file. The landscape mesh is used as a proximity brush to paint \"shoreline\" interaction onto an animated canvas. The project exhibits the same low frame rate even when the Dynamic Paint modifiers have their Visibility and Render settings disabled. Only by completely deleting the modifiers, does the the frame rate return to normal.\n\n\n\n[DYNAMIC PAINT TEST FILE.blend](DYNAMIC_PAINT_TEST_FILE.blend)\n\n", "Timeline/Frame ranges inconsistencies in UI\n#39484 raised that timeline frame range representation actually show (real_length - 1) interval… So e.g. a scene having same start and end frame is shown as zero length. This is also inconsistent with how caches are drawn in same window (they start at -0.5 frame and end at +0.5 frame), which allows to represent the real length, assuming 'frame' itself as a sort of “center” value.\n\nTo fix #39484 I simply made same thing for frame range, but this was to quick in fact, we need a design decision here and make it consistent in all time-related windows (timeline, VSE, MCE, animations, etc.).\n\n@sebastian_k proposed to rather draw a [start, end+1] interval, adding a small green square of one frame width to the cursor:\n\n", "Freeze on performing any operation when compositor tab is open\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 516.40\n\nBroken: version: 3.3.1\n\nFreeze on performing any operation when compositor tab is open.\nSubsurf modifier seems important for redoing the issue \n\nThis is the continuation of #99695 \n\nThe Bug in #99695 was fixed, but there seems to be more conditions which make the Compositor slow.\n\nDorian from Scatter5 was so nice and made again a simplified version of a secene with the bug.\n\nThe slowdown caused by an unkown combination of geometry nodes, which makes the Compositor unusable slow.\n\n1. Open the attached file\n2. Go to the Compositor\n3. Enjoy the freeze\n4. Try to disconnect a node in the Compositor\n5. Again, enjoy the freeze\n\n[COMPOSITOR SLOW.blend](COMPOSITOR_SLOW.blend)\n", "compositor performance issue when larger empty area surrounding the image\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: much faster in 2.93\n\ncompositor performance is severely degraded if there is a larger empty area surrounding the pixels. Also becomes more and more sluggish the longer it plays back, despite it only updating a single image block. Task manager doesn't show any increase in memory usage as it becomes slower.\n\n<video src=\"attachment\" controls></video>\n\nGet an image sequence to playback in the compositor's backdrop, either with a image sequence node, or by updating a single image via python and calling render.render to force the playhead to wait for the compositor to finish calculating. Try playing back with the compositor contracted and expanded. See video for demonstration.\n\nIssue affects the tiled, full frame, and gpu compositor modes. Also happens when experimental compositor is disabled completely in the preferences.\n\nExample video attached.\n\n", "Blender 3.0 Denoising on Transparency Creates Artifacting (Blend included)\nOperating system: Win 10 (latest update)\nGraphics card: RTX 3090\n\nBroken: (3.0.0 and 3.0.1 dc2d18018171 Branch: Master)\nWorked: (2.9.0)\n\nWhen enabling transparency under \"Film\" settings, artifacts occurs in the transparency channel\n\nOpen attached .blend in 2.9.0 and 3.0.0 and hit render to see. I've set-up a compositor node setup to highlight and visualize the artificating found in 3.0.0. Try rendering with both Denoising methods to see variations in artifacts.\n\n**Other notes**\nI've played with as many render settings as possible and found that the denoiser is responsible. OptiX is worst, OpenImage is not as bad in artifacting.\n\n[alpha-transparency-denoising-issue-sample.blend](alpha-transparency-denoising-issue-sample.blend)\n\nNotice the clean colors in the greys (background composited in Compositor to help see issue)\n\n\nNotice the vertical and horizontal line noise\n\n\n[system-info.txt](system-info.txt)", "Subdiv hangs blender\n**System Information** DESKTOP-HR30UII\nOperating system:Windows 11 Home Single Language\nGraphics card:2GB NVIDIA GRAPHICS DRIVER\n\n\nBroken: Blender Version 3.5\nWorked: ?\n\nBLENDER 3.5 KEEPS NOT RESPONDING WHILE I USE MODIFIERS \n\nON BLENDER ADD MESH AND ADD MODIFIERS TO SUBDIVISION SURFACE THEN CHANGING THE VALUE OF LEVELS VIEWPORT VALUE ABOVE 4 .THEN ONWARDS BLENDER COMPLETELY STOPS WORKING AND I NEED TO RESTART IT AGAIN\n\n", "GPencil: Materials' preview thumbnails cause heavy lag when updating\nOperating system: Windows 10\nGraphics card: RTX 3070 FE\n\nBroken: 3.2.1 RC\nWorked: n/a\n\n\n\nAny action that requires the refreshing of your Grease Pencil materials' thumbnails (isolate/hide materials, etc.) causes major lag until the thumbnails are finished refreshing. The more materials your GP object has, the longer the lag. Sometimes the lag is so bad, that it makes the sound buffer skip while the thumbnails refresh.\n\n\n**Video Explanation**\nwatch?v=5KAWsJkIeRY\n\n\n**Steps to Reproduce**\nCreate a GP object and add 10-20 unique materials\nClick one of the \"Isolate Material\" buttons, and start drawing/moving strokes. You will notice extreme lag until all of the little circle thumbnails are finished updating. \n\nTest File:\n[#99361.blend](T99361.blend)", "GPencil: Massive slowdown when stroke number scales\nOperating system: Win10\nGraphics card: NV GTX960 / NV RTX 2080\n\nBroken: e03d78417a77\nWorked: never \n\n\nOur artist want to make \"gris\" quality characters with a lot of inner shades, and created a huge character with lot of strokes and did not break it down in sub objects.\nAlas when using \"Edit mode\" to animate the keys blender gets extremely choppy.\nIf we remove strokes situation gets better which leads us to believe that stroke/key storage is too linear or computed during motion\n\ndownload : view\ngo to \"strokes\" \ngo to edit mode\nselect hairs\nmove hairs around\nobserve any movement or undo is very choppy and slow \n\nnote :\nAs a dodge, we will try to split the character strokes in sub objects but we thought it would be important for this use case to be fixed because going back and forth in sub objects can be a time consuming and be counter intuitive for less technical artists.\nThank you so much for reading and creating GPencil." ]

[ "Blender 3.1 poor UV editor performance regression\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\n\nIn Blender 3.1, the UV editor performs significantly worse than it did in 3.0, when displaying 4k texture. The poor performance is most noticeable in terms of framerate, and also in terms of time it takes to toggle the fullscreen display of the editor using Ctrl+Spacebar shortcut.\n\nHere's the video of the issue:\nwatch?v=HfOYQko6TAw\n\n1. Open the attached .blend file: [SlowTextureBug.blend](SlowTextureBug.blend)\n2. Maximize the UV editor using the Ctrl+Spacebar shortcut and pan around using middle mouse button\n3. Very quickly, repeatedly keep pressing Ctrl+Spacebar with the mouse cursor over the UV editor to rapidly maximize and restore it\nResult: Both display framerate as well as maximize/restore operation of the UV editor are significantly worse than in Blender 3.0\nExpected: The performance is comparable or better than Blender 3.0\n\nNote: The nVidia GPU drivers are on the latest version.\n", "Regression: 3.1 & 3.2 Image/UV Editor poor performance (Byte textures, window dragging, maximizing area)\nOperating system: Win 10\nGraphics card: 980 Ti, recent drivers\n\nBroken: 3.1 beta v31.f420118335e4 and 3.2 alpha master.95005bbe02cf\nWorked: 3.0.x\n\n**Short Description**\nTest 1: \nWhen interacting with UV / Image editor my fps drops from 144 to ~20 - depending on how large is the Image Editor window.\nThe actual image size or format doesn't affect the performance at all, but Image Editor without any image loaded (just with grid) is completely smooth when moving it around.\n\nTest 2: \nThe performance is also significantly lower when dragging any window border\nWas completely smooth in 3.0.x\nCould be specific for this GPU / architecture, since my coworker with AMD can't reproduce the issue.\nnote this also has its own report, see #97272 (Regression: Blender 3.1 UI editor resize /border dragging performance), so maybe this could be removed from this report...\n\n**Steps to Reproduce**\nTest 1:\n\nopen UV / Image Editor\nload any image\npan the view around, move UVs etc\nshould be noticeably slower than in 3.0.x\n[2022-02-02 11-03-10.mp4](2022-02-02_11-03-10.mp4)\n\nTest 2:\nopen the default scene\ndrag any window border\nshould be noticeably slower than in 3.0.x\n[2022-02-02 11-00-05.mp4](2022-02-02_11-00-05.mp4)\n", "Image editor/uv editir issue\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.0\n\n**Image editor/uv editir issue**\n\nHello Blender Team!\n\nI've found a bug with image editor in blender 3.1. When I move the area between image editor/uv editor and any other editor I experience a great slow down. Comparing to the previous version of blender 3.0 it worked much faster.\nAttaching 2 short videos with blender 3.0 and 3.1 comparison and blend file just in case [image editor_issue.blend](image_editor_issue.blend) [IE_fast_blender_3.0.mp4](IE_fast_blender_3.0.mp4)\n\n[IE_slow_blender_3.1.mp4](IE_slow_blender_3.1.mp4)\n\n\n", "Severe lag in UV Editor/Image Editor when dragging the workspace around or Texture Painting\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0 Beta\nWorked: Previous versions of 3.1.0, sorry don't know exact version \n\nWhen I attempt to drag around the workspace in UV Editor there is considerable lag. Also occurs when in image editor attempting to texture paint. \n\nWith an empty scene if I create a cube, add a material, then in shader editor create a new image texture with size of 4096x4096 if I bring that file up in the UV editor or Image editor the translate or texture paint operations are severely lagged.\n" ]

[ "Cycles is not working in 3.5.1 on a MacBook M1 Max—causes the program to immediately freeze!\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.1\nWorked: (This started happening two days ago, and I only updated to 3.5.1 today. But in the days/weeks prior it was 3.4)\n\nOn my MacBook M1 Max (with all upgrades possible), I have had to force quit Blender countless times in the last 48 hours after turning on viewport Cycles view. Upgrading to 3.5.1 has seemingly made it a constant problem. Even now opening a brand new project, then turning on Cycles render, it starts saying it’s loading kernels (very slowly), and never renders, freezing the viewport, forcing me to force quit. So it seems I no longer can turn on Cycles in 3.5.1.\n\nThere is no further steps really, this is happening on a new project for me. Hopefully you all can see this and figure out something! I’m happy to provide further details if you need anything. I use Blender for my day-to-day at work so fingers crossed this isn’t the new normal for the foreseeable future. Also, love you all!\n\n", "Blender 3.5 and 3.5.1 are crashing while using Metal as backend\nOperating system: macOS 12.6.3\nGraphics card: Radeon Pro 580 8GB\n\nBroken: 3.50, 3.51 (Metall Backend)\nWorked: 3.50, 3.51 (OpenGL Backend)\n\nBlender simply hang. I use eevee, if you switch to rendered viewport shading it crashed complete system. I use Metall as backend, if I choose OpenGL it works fine. \n\n \nI attached an .blend file for example.\n\n", "Materials don't support more than 8 Attributes\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.2\n\nMaterials in Blender currently seem to not support more than 8 Attributes in the final material output node. Not quite sure where the problem lies but i stumbled upon it today wanting to expose 12 Node Group sliders in the Custom Property tab.\n\n\n\nHere is a .Blend file i set up to demonstrate the issue. There is 12 circles which colors are controlled by the custom properties on the object. Only last 8 attributes are registered while the newly added ones past 8 are returned with a value of zero. When previewed individually they do give a correct value however once connected into a chain of nodes it appears they are limited to 8 inputs. Example uses Color output however i did test it on the Fac output and it gave the same results. File was set up on the Factory Settings\n\n[Shader Attributes Limitation.blend](Shader_Attributes_Limitation.blend)\n\n\n\n\n\n", "Blender Crash when deleting images too fast\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.44 30.0.13044.0\n\nBroken: version: 3.2.0\n\nBlender crashes when deleting images in the Layer blend file libery\n(3.3 alpha is crashing also and i didnt found any report about this issue)\n\n\n* go to outliner -> select blend file\n* make sure to be in the material preview mode\n* delete the first image by right click and then click on delete image\n* (now u only need to rightclick and leftclick to delete next images, because u dont need to aim for the delete anymore)\n* delete images while blender tries to preview the last change after deleting one of the images\n blender crashes\nwhen deleting images too fast, my blender just crashes (happens on my bad pc often, because i download models and rework them)\nIf you wait for the new material preview of the model after deleting nothing happens, but if you dont blender crashes when continuing to delete images\n\nVideo: CvO9nw4qilc\n\n[pharaoh x suite.blend](pharaoh_x_suite.blend)\n", "Calling operator from handler that saves bmesh freezes blender forever\nBlender version: 3.5.1\n\nI setup some shader to run on top of blender viewport and connected it’s update to `SpaceView3D.draw_handler_add`. The idea was that shader will only work in EDIT mode and if user exists it then it will automatically trigger some operator.\nLine that freezes Blender is `bm.to_mesh(context.object.data)` although it doens’t freeze right away.\n\nWhat I’ve found that if I call operator that edits mesh from bmesh then it freezes Blender entirely.\nCurrently as a workaround I moved operator’s code to some function and call it instead of because `bm.to_mesh(context.object.data)` doesn’t seem to freeze Blender when it’s called from handler without operator.\n\n\nEasy way to reproduce (create default scene, make sure cube is selected, run the script):\n\n```python\nimport bpy\nfrom bpy.types import SpaceView3D\nimport bmesh\n\nclass TestHandler:\n installed = None\n\n @classmethod\n def install(cls, context):\n handler = cls()\n cls.installed = SpaceView3D.draw_handler_add(\n handler, (context, ), \"WINDOW\", \"POST_VIEW\"\n )\n\n @classmethod\n def uninstall(cls):\n try:\n SpaceView3D.draw_handler_remove(cls.installed, \"WINDOW\")\n except ValueError:\n pass\n cls.installed = None\n\n def __call__(self, context):\n obj = context.object\n if obj.mode != \"EDIT\":\n TestHandler.uninstall()\n bpy.ops.test.test()\n print('HANDLER CALL FINISHED') # never printed\n return\n \n print('HANDLER FINISHED')\n\nclass TestOperator(bpy.types.Operator):\n bl_idname = \"test.test\"\n bl_label = \"test\"\n\n def execute(self, context):\n print('TEST OPERATOR CALLED')\n bm = bmesh.new()\n\n # WITHOUT THIS LINE IT DOESN'T FREEZE\n bm.to_mesh(context.object.data)\n\n # still printed\n print('TEST OPERATOR FINISHED')\n return {\"FINISHED\"}\n \nclass TestSetupOperator(bpy.types.Operator):\n bl_idname = \"test.test_setup\"\n bl_label = \"test\"\n\n def execute(self, context):\n print('TEST SETUP OPERATOR CALLED')\n TestHandler.install(context)\n return {\"FINISHED\"}\n\n\nbpy.utils.register_class(TestOperator)\nbpy.utils.register_class(TestSetupOperator)\nbpy.ops.object.mode_set(mode=\"EDIT\")\nbpy.ops.test.test_setup()\n# freezes on the next step\nbpy.ops.object.mode_set(mode=\"OBJECT\")\n```\n\n", "Geometry node don't expose materials to the solidify modifier\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2060\n\nBroken: blender-3.1.0-beta+v31.93cc89247010\nWorked: 3.0.1\n\n\nWhen using a geometry node to generate a mesh, and then applying a solidify modifier to it, the materials are not properly exposed and not or wrongly assigned to the final mesh\n\n- create a plane\n- go in edit mode and delete all the mesh data\n- back in object mode, add geometry node modifier\n- add a Cylinder mesh primitive, and set its fill type to None\n- add a Join Geometry node and plug the Group Input Geometry socket and the Cylinder node Mesh socket into the Join node\n- plug the join node into the output\n- add 3 materials to the object and set different colors\n- add a solidify modifier and set material for offset and rim to indices 1 and 2\n\nThe resulting tube doesn't show any of the materials.\n\n- go in edit mode and add at least one vertex to the mesh\n\nNow the resulting tube displays the last material of the list on some parts, but this is still not it.\n\n- Instead of creating a cylinder in the geometry node tree, plug a Mesh circle primitive\nThen add a screw modifier to extrude it, after the geometry node modifier and before the solidify modifier\nSet its angle to 0° and Screw value to 1\n\nNow the resulting tube is only displaying the first material\n\n- Go in edit mode and add at least one vertex to the mesh\n\nNow the resulting tube displays all the materials properly.\n\nNote : it is not obvious, but it is mandatory to join the original geometry into the end result to get the materials correctly propagated to the output.\nMaybe this could be more clearly explained or simplified somehow.\n\nSample file here reproducing all cases mentionned above :\n[solidify_material_bug.zip](solidify_material_bug.zip)", "Crash when multiple materials are assigned to a mesh\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.1 Release Candidate\nWorked: unknown (I haven't opened the .blend file in versions older than 3.2. It is broken in 3.2)\n\nWhen two materials are assigned to the mesh, random faces disappear and reappear when switching between Object and Edit modes. After switching back and forth several times, Blender crashes. In some instances it took significantly more switches from Edit mode to Object mode and back before Blender crashed. In some of these instances, Blender appeared to create new faces with one or more vertices at the object's origin.\n\nWhen transforming any vertex, edge, or face, Blender quickly generates new faces with at least one vertex at the object origin and crashed shortly thereafter.\n\nI posted a 30-second video of the issue (including two crashes) here: strange_face_artifacts_causing_crashes/\n\nThankfully, I have not reproduced this issue in any other .blend file.\n\n1) Open the attached file, \"Crash - random faces.blend\" and you will see the mesh has a number of holes in it.\n2) Press tab and the missing faces will reappear but other faces will disappear. Pressing tab additional times eventually results in Blender crashing.\n3) Select any vertex, edge, or face and transform the selected element using G, S, or R and new faces will appear. Blender will quickly crash.\n4) Reducing the number of material slots to one appears to fix the problem (all faces are visible as normal) but it reappears as soon as a material is assigned to the second slot.\n\nThank you very much for your time.\n\n[Crash - random face orientation.blend](Crash_-_random_face_orientation.blend)\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", "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.", "Node Group Texture slot problem\nOperating system: Windows 10\nGraphics card: gtx1060\n\nBroken: 2.9\nWorked: N/A\n\nIn the Texture Paint mode, when all textures are inside a node group, if you change brush radius it jumps to the top texture slot every time.\n\n- Open attached file\n- In the property editor, select `test` texure slot\n- Change brush radius.\nThe top texture slot (`test`) was selected automatically\n[Node Group Texture Slot Problem.blend](Node_Group_Texture_Slot_Problem.blend)", "Cycles X material preview using 100% of cpu\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\nUsing cycles X, opening the material preview causes my computer to lag and drop in FPS\n\nCreate a new material and open the material preview with cycles x\n\nFor a new scene with default cube and default material, preview render completes in about 5 seconds.\nWith Beckmann glass it's ~10 seconds.\nWith Multiscatter GGX Glass, ~35 seconds.\n\n(Size of preview render: 134x150px)\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", "Memory leak cause my computer to freeze when rendering anumation\nOperating system: macOS-12.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5300M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.2.2 Release Candidate\nWorked: worked on blender ~3.0 but it broke on 3.1+.\n\nwhen rendering full animations the memory of Blender is raised to 20GB, although the animation is a very simple content. after 300 frames of rendering in the low quality, we are still stuck and the rendering output is blank frames. \nThe entire compute get stuck and Swap Files rose to 10GB. I have 32 GB of memory.\n\nI will attach the file I render to this ticket.\n\n**Update August 19, 2022**\nThe memory issue was fixed in the current 3.2.2 version and in 3.3 version.\nbut there is an issue with black images rendered from frame 700 in the animation ( in the same file attached).\nin the previous versions the black frames occurred from the frame 300 because of memory leak issue.", "Crash when sculpting with a texture, deleting the image of the texture and exiting sculpt mode\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: version: 3.4, 3.5, 3.6\nBroken: version: 3.3.3\nBroken: 3.1.0\nWorked: 3.0.1\nWorked: 2.93 LTS\n\nCaused by 9111ea78ac\n\nBlender crashes when a texture image is deleted and you exit sculpt mode.\n\nYou can test it inside the attached blend file. I basically just attached an image to a sculpting brush.\n\n1. Open the blend file below\n2. draw on the surface of the sphere\n3. delete the image inside the outliner\n4. exit sculpt mode\n\nCrash occurs because `item->image->runtime.cache_mutex` is null inside `BKE_image_pool_free`\n```\nStack trace:\nblender.exe :0x00007FF713D04C10 pthread_mutex_lock\nblender.exe :0x00007FF70E6EE880 BKE_image_pool_free\nblender.exe :0x00007FF70E6B5CF0 BKE_sculptsession_free\nblender.exe :0x00007FF70F1B67A0 ED_object_sculptmode_exit_ex\nblender.exe :0x00007FF70F1B85F0 sculpt_mode_toggle_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\nblender.exe :0x00007FF70E9528D0 wm_operator_call_internal\nblender.exe :0x00007FF70E955880 WM_operator_name_call_ptr\nblender.exe :0x00007FF70F171800 ED_object_mode_set_ex\nblender.exe :0x00007FF70F148710 object_mode_set_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\n```", "Freeze on performing any operation when compositor tab is open\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 516.40\n\nBroken: version: 3.3.1\n\nFreeze on performing any operation when compositor tab is open.\nSubsurf modifier seems important for redoing the issue \n\nThis is the continuation of #99695 \n\nThe Bug in #99695 was fixed, but there seems to be more conditions which make the Compositor slow.\n\nDorian from Scatter5 was so nice and made again a simplified version of a secene with the bug.\n\nThe slowdown caused by an unkown combination of geometry nodes, which makes the Compositor unusable slow.\n\n1. Open the attached file\n2. Go to the Compositor\n3. Enjoy the freeze\n4. Try to disconnect a node in the Compositor\n5. Again, enjoy the freeze\n\n[COMPOSITOR SLOW.blend](COMPOSITOR_SLOW.blend)\n" ]

[ "Material properties thumbnail update causes short UI freeze 2 seconds after material parameter change\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nAny update of material parameters in material properties editor causes short input blocking UI freeze roughly 2 seconds after parameter change. This is very annoying when user changes a material value, proceeds to interact with viewport which hitches a moment later. There is no logical reason 16px wide material thumbnail generation should cause entire UI and input to freeze. Especially with powerful hardware, such as GTX1080Ti.\n[2019-07-09 12-20-52.mov](2019-07-09_12-20-52.mov)\n\n\n\n1. In a new .blend file, open material tab of properties panel and create a new material\n2. Change any material property which has impact on material appearance and quickly proceed to orbit the viewport.\n3. Notice the viewport hitches and freezes for a short moment roughly 2 seconds after every material update\n\nResult: Viewport and UI freezes for a short moment roughly 2 seconds after any material update. \n\nExpected: No freezes ever occur during viewport navigation even if material properties are edited. \n\nProposed solution: Do not delay material thumbnail updates, but update material parameters only on mouse button up/num input enter. Not during the interaction with the UI elements but right after mouse button is released / numerical value is confirmed with enter key." ]

[ "shrink/flatten not working right way?\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\nBroken: version: 2.91.0 Alpha\n\ni think shrink/flatten not working the right way. only top works fine goes up down.\nbut bottom and sides are backwards and a bit counterintuitive.\n\ni dont know if its bug but wanted to report anyway.\n\n\ncheck video\n\nthanks\n\n\n[2020-09-27 04-57-36.mp4](2020-09-27_04-57-36.mp4)\n\n[blender.blend](blender.blend)", "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", "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", "Viewport x-ray shading slider flipped\nOperating system: Linux-4.15.0-66201911071317-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nViewport x-ray shading slider flipped\n\nI think this is ment to work the other way round, isn't it?\n", "Regression: Blender text editor lost support for dead keys\nOperating system: Linux-4.19.0-11-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 2.93.0\nWorked: 2.92\n\nCaused by cafd6b519c\n\n\nOn any text input field, on the Python Console, on the text editors, I cannot type any of the characters that need dead keys (I use English International with dead-keys to type English, Spanish, and German).\nI cannot, for example even type quotes, which makes Python expressions hard - let alone accents, etc. \n\nThis used to work on previous versions of Blender. The latest I found it working on is on a 2.92 release candidate I had somewhere on my hard drive.\n\n\n1. On a computer configured with dead-keys input, open the default scene\n2. Switch the main display to be a Text Editor.\n3. Press \"New\" to create a new file.\n4. Try to type \"é\" (by pressing 'e) or \"'' by typing (' space).\n\nExpected behaviour: Blender accepts the typed-in characters.\nActual behaviour: Blender ignores the typed-in characters.\n\nSomething like this gets printed to the console:\n\n```\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7f80237f2980 0x7f804905d0c0\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", "Geometry nodes/Text Object: negative space character width\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.5.0 Alpha \n3.3.1\n2.79b at least with Text Objects.\n\nWhen I have zero word space and character space, the size of space-character is negative.\n{[F13938068](изображение.png) size=full}\n[2022-11-17_23-59-38.mp4](2022-11-17_23-59-38.mp4)", "With FPS change, VSE does not change clip start frame\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 516.94\n\nBroken: version: 3.4.1\nAlso problem in 2.92, 3.3.2, 3.5 alpha\n\nWith a FPS change, VSE changes the duration of an audio clip but not the start frame and the clips become misaligned.\n\nBest seen with two clips starting at different frames. See images. In my example the audio clips are mono at 11025 Hz. (Seems video clips act the same way.)\n\n{[F14133157](24.png),size=full}\n{[F14133163](6.png),size=full}\n\nI know there are several somewhat related reports re: VSE and FPS. Hope not a duplicate.\n\nThanks!!! (for all the great work!)\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", "Zooming in and out of the node viewport, text keeps changing its size\nOperating system: Arch Linux\nGraphics card: NVIDIA GTX 980\n\nBroken: Blender 2.90.0 Stable Release\nWorked: I'm not sure if this has ever worked correctly but it looks ugly.\n\n\nWhen zooming in and out of the node viewport, the text keeps changing its size making it look like it's jumping all around. I think the view should only zoom in and out without ever changing the text's size.\n\n\nAdd a principled BSDF node and then zoom in and out.\n\n[nodetitle.webm](nodetitle.webm)\n\n", "The Chinese input method does not work properly when searching\nOperating system: windows11 home\nGraphics card: RTX2060\n\nBroken: 4.0.0-alpha+main.24fe81e602a8\nWorked: 3.6.2\n\nThis is related to a previous problem:(93421)\nLet me describe the process:\n1. Make sure that the IME is off, otherwise the shortcut key is not available\n2.Shift A\n3. I tried to search for Chinese, but because there is a certain probability that IME cannot be automatically opened at this time, I can only enter letters directly\n4. I had to delete the letters that had already been entered (and enable IME manually if IME was not automatically turned on) before I could enter Chinese normally\n\nIf this problem can't be solved in a short time, perhaps offering an option, in the 4.0 version you can still use the old search button, as in version 3.6?\n\n", "Using LineArt modifier , line behind object will appear unexpectedly.\nSystem Information\nOperating system: Windows-10 64bit ver.20H2 os build 19042.1052{[F10208498](2021-07-02__3_.png)}\n\nGraphics card: NVIDIA Quadro [P2000](P2000.txt) driver ver.R470 U1 (471.11) WHQL\n\nBlender Version\nBroken: version: 3.0.0 Alpha\n\n**Short description of error:**\nUsing LineArt modifier , line behind object will appear unexpectedly.\n\n[2021-07-09 10-22-31.mp4](2021-07-09_10-22-31.mp4)\n\n**Exact steps for others to reproduce the error:**\n[lineartTest.blend](lineartTest.blend)\n\n- Open file \n- Tweak camera shift X property from min to max\n\nLines won't be drawn for some objects. \nBug looks a bit different in `7489427e4d` than what's shown in video\n\nAny way ,I’m excited new features.Thank you all to a great work.\nHave a nice days.", "GN +motion blur =bi-direction\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 522.30\n\nBroken: version: 3.5.0 Alpha\n\n\n\n[Мошкара.blend](Мошкара.blend)\n\n", "Graph Editor menu item Key -> Clean Channels and Key -> Clean Keyframes have the same descriptive text\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha\nWorked: none\n\nThe graph editor menu item Key -> Clean Channels and Key -> Clean Keyframes have the same descriptive text when they do two different things.\nKey -> Clean Channels help text should be changed to Clears keyframes on channels that have default values.\n\nCreate some animation on the default cube\nopen the graph editor\nselect the curves\nChoose the Key menu\nHover over the Clean Channels and Clean Keyframes menu items to see the text.\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)" ]

[ "The Arabic language appears reversed\nBroken: 2.79, 2.80, 2.81, ...\n\nThe Arabic language appears reversed\n\n\nExample text: القرآن", "The problem of displaying the Arabic language incorrectly\nHello all .\nI would like to highlight a problem that has existed since the beginning of the Blender program\nIt does not support the Arabic language at all and causes a lot of problems for users who write in the Arabic alphabet\nI would like to correct this problem, which has persisted for a long time, as the Blender program shows writing an error in the user interface and file browser, or when writing 3D text, it requires me another program to correct the way the writing is displayed\n\nblender \nﻲﺒﻳﺮﺠﺗ ﺺﻧ ﺍﺬﻫ\n\ncorrect writing\nهذا نص تجريبي" ]

[ "Cycles X: Camera-visible lamps are not affected by holdout\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0 Alpha\n\nBlender 3.0 adds a feature where camera ray visibility can be enabled on lamps, making them directly visible. However, if this option is enabled simultaneously with the holdout option, the lamp will remain visible. Holdout should override camera visibility, as holdout can be changed per-view layer. With the current behavior, a directly-visible lamp will appear again on holdout layers, copying it's direct brightness for every layer it appears as a holdout in.\n\nSee attached .blend file, which contains a point lamp with holdout and camera visibility both enabled. Note that the lamp remains visible. In fact, the holdout option seems to have no affect at all.\n\n[holdout_lamp_bug.blend](holdout_lamp_bug.blend)\n\n", "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 Vibrating Contours\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.83.4\n\nHi, i i have bug on Grease Pencil contours. When i move camera in animation contours vibrate, changing size. This is not problem with my PC, because i tried it on another and problem is the same. I tried Anit-Aliasing, change render engine (Cyles and Evee), the same bug is in viewport and in render animation. I'm attach the video of this bug. This bug occurs just with camera or object move. \n\n1. Create Grease Pencil object.\n2. Move camera to \"zoom\" it.\n\n[vibrating contours.mp4](vibrating_contours.mp4)\n\n[vibrating contours.blend](vibrating_contours.blend)\n", "\"Disable in Viewport\" option results in UI for \"Disable in Render\" not updating properly when it is keyframed\nOperating system: Linux-5.10.0-8-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: NA\n\nBroken versions: 2.82-3.4\nWorked: Unsure\n\n**Short description of error:**\n\"Disable in Viewport\" option results in UI for \"Disable in Render\" not updating properly when it is keyframed.\n\n**Exact steps for others to reproduce the error:**\nFollow the steps shown in the video above or follow the steps below:\n1. Start with a new file.\n2. Select an object.\n3. In the `Object Properties` tab of the `Properties Editor`, expand the `Visibility` panel.\n4. Inside the `Visibility panel`, animate the the `Show in -> Renders` property. You can do this by inserting a keyframe for it being enabled on frame 1, then go to frame 2 and disable it and keyframe it again.\n5. Once the `Show in -> Renders` property is animated, disable `Show in -> Viewports`. Now if you scrub through your time line, you will notice that the UI for `Show in -> Renders` does not update the `Tick` as you go back to a frame you had keyframes to be enabled. This can also be observed in the `Outliner` as the `Camera` icon does not change from disabled to enabled or vice-versa.\n6. If you enable `Show in -> Viewports`, you will notice the `Tick` and `Camera` icon start updating again as you scrub through the time line.\nHere is a video demonstrating the issue:\n[Disable in viewport breaking disabled in render.mp4](Disable_in_viewport_breaking_disabled_in_render.mp4)", "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", "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", "GPencil: Strokes with texture & round caps have distorted extremities\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\n\nStrokes with a material of line type 'Line', a texture & round caps have distorted extremities.\n\n\n- Open file and see how the start & end of the drawn strokes are distorted.\n[round caps bug.blend](round_caps_bug.blend)\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", "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", "Grease Pencil mask error\nOperating system:windows10\nGraphics card:GTX1060ti\n\nBroken: 2.83&2.9\nWorked:greasepencil-Mask error\n1.When 2.83 or later, creates two objects, the masks collide, causing a strange phenomenon, and in 2.82 there are no errors.\n2.And creating two masks under the same object can cause problems too。\niJlqkf556sA\n[GP剪贴测试.blend](GP剪贴测试.blend)", "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", "GP transparent layer doesn't blend with background object \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\nI have a foreground grease pencil object, and a background grease pencil object (yellow blob).\nThe foreground object contains a layer set to 0 opacity.\nWhere this layer overlaps the background object in the viewport, the background object is invisible.\nExpected behaviour: the visibility of the background grease pencil object isn't affected by transparent layers in a foreground object.\n\n\n\n\n\n[#89286.blend](T89286.blend)\n\nForeground object \"makes hole\" in background, doesn't blend. Rotate viewport camera, suddenly it blends correctly.\nWhen foreground location is set to 0,0,0 it blends correctly too.", "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", "(Camera) Motion blur renders wrong (does not cancel out) when a mix of parenting and (baked) object animation is used\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nwhen I parant a camera (looking for a simple cube) and the cube (who is the camera looking for it) to any other object, if the parent object is rotating, it will rendered fine but if I baked the action of the camera, and renderd the same frame it will be very in coorect motion blur, to fix the issue I have to bake the camera and all the objcects that appear on it, \n\n\n[motion blur bug.blend](motion_blur_bug.blend)\nopen the attached blend file, you will find a very simple scene with a camera, cube and a light are parented to a rotating empty object, just press render at frame 2 (which at the meddle of rotation) and it will render the motion blur very good (you will not see any motion blur which is logic because the camera and the cube are parended to the same object), but after that just bake only the camera (with selected object, visual keying and clear parent enabled) and render the same frame, it will give very unlogic motion blur, after that bake also the cube and the light and redner the same frame, it will render very good, this issue is only on rotating parent object bun in location it works very good, also I tested it on blender 2.7 and the same issue are there\n\n\n\n", "Some sculpting brushes work incorrectly on the Grease Pencil object with Armature.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 590 Series ATI Technologies Inc. 4.5.14742 Core Profile Context 21.8.2 27.20.22025.1006\n\nBroken: version: 3.0.0 Beta\n\nAfter applying the Armature modifier to the Grease Pencil object and after animating the bones, some brushes in Sculpt Mode do not work correctly. In this case Grab brush. Smooth, Thickness, Strength and Randomize brushes work correctly.\n\n\nOpen attached .blend file. Go to the 20th frame. \nSelect Grease Pencil object.\nSwitch to the Sculpt Mode select the Grab brush and test it. Push, Twist and Pinch brushes also work incorrectly.\n[SculptTools_problem.blend](SculptTools_problem.blend)\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" ]

[ "Non-themeable property in nonlinear animation\nOperating system: Windows 10\nGraphics card: 1080ti\n\nBroken: 2.93\nWorked: ???\n\nThere is a property that is always blue in all of the shipped Blender themes, and which cannot be changed. I don't know the name, since I don't think it appears in the UI...\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", "Channel Group Color in the Action Editor is difficult to change\nversion 2.71 (sub 0), branch b'master', commit date b'2014-06-25' b'18:36', hash b'9337574', b'Release'\nbuild date: b'2014-07-08', b'20:27:39'\nplatform: b'Darwin:64bit'\n\n[system-info.txt](system-info.txt)\n\nIn the action editor, I have a set of related influence channels. So I put them in a group with ctrl-g, and gave the group a name. I wanted to change it's color to make it stand out from my bone channels, but I couldn't find a way to do it. Eventually, I looked in the datablock outliner, and found it can be changed via \"Blendflile Data/Actions/<Action Name>/Groups/<Group Name>/Color Set\".\n\nIt would be nice if this were in the UI somewhere. Best place I can think of would be in the N sidebar of the F-Curve editor, in a \"Group\" panel, or something. Name could also be edited there, perhaps. It would also fit well in the N sidebar of the DopeSheet or Action Editor, if they had an N sidebar", "keyboard shortcut to switch between vertex / edge / face not present in tooltip\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nI rely on the tooltips to learn keyboard shortcuts.\nWhen hovering above the vertex / edge / face select button, the shortcut to enable this button is not mentioned.\nexpected: \nVertex Select: 1\nEdge Select: 2\nFace select: 3\n", "select interior faces doesn't support some kinds of interior geometry\nwin 7 pro\n\nBroken: (example: 2.76.1 bfdb420)\nWorked: (optional)\n\nwhen you try to check if there are some interior faces, from menu you select interior faces in face mode. but it does not show them. you only can do this by select non manifold in egde mode and then find the wrong ones. \nwhen you open file, there is black frame where interior faces are. change to face mode, then select interior faces from menu. nothing happens. change to egde mode and select non manifold, and there are 2 interior faces which were not selected earlier.\n[interior faces_bug.blend](interior_faces_bug.blend)\n", "Tweak tool deselects previously selected items.\nOperating system: Windows\nGraphics card: 1060\n\nBroken: All 2.8 versions\n\nTweak tool deselects previously selected items.\n\n\n", "Generic Input in a Group Node displays as Grayscale, when it is in fact neutral.\nSolution: \n\n\n\nIn the example above, the only change would be that the socket next to the Input would be empty instead of gray. This would fix the wrong impression that it's a Grayscale input - it's not, it's neutral as Sergey stated.", "PyAPI: Unregistering DATA_PT_modifiers causes wrong panels (such as contraints) to appear in modifier UI\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.1.0 Alpha\nWorked: 2.83\n\nUnregistering DATA_PT_modifiers causes wrong panels to appear in the modifier UI. \n\nProblem 1: Constraints appear in the modifier UI.\nProblem 2: Grease pencil modifiers appear on other object types. To be more specific, only the main panels appear, not subpanels. \n\nThese problems didn't occur with the old modifier stack. I use this in my Modifier List addon.\n\nRelated: T77541\n\n1. Open the attached file\n2. Run the simple script to unregister DATA_PT_modifiers\n3. Select the grease pencil object\n4. Select the mesh object\n5. Grease pencil modifiers should appear on the mesh\n6. Add some constraints to the mesh\n7. Switch to modifiers tab\n8. The modifiers should appear there (however, now the grease pencil modifiers should no longer be there)\n\n[unregister DATA_PT_modifiers grease pencil bug.blend](unregister_DATA_PT_modifiers_grease_pencil_bug.blend)", "Bisect Tool Todo\n## Bisect\n * - [ ] {icon circle color=yellow} We should add an updated Gizmo here \n\n *Comment: should this gizmo's plane be an outline (design looks opaque), also, it's quite different to the previous design, see: #54661 ~ ideasman42*\n\n *Answer: This design is more similar to what we have now, but makes it easier to rotate and move the bisect plane along specific axes. The blue plane here should be transparent, not opaque. ~ billreynish*\n\n * - [x] {icon circle color=yellow} We should add these options to the tool settings: Fill, Clear Outer, Clear Inner. Otherwise, users have to keep setting these settings for every bisect operation.\n * - [ ] {icon circle color=yellow} We should add an option called 'Only Selected' just like the Knife tool. Currently it always only applies to selected elements, but that makes many successive bisects annoying because you constantly have to select all. \n", "Show small preview image even in non-Thumbnail Display Modes\nAs mentioned in #89729 (Add toggle for Vertical and Horizontal Display Mode) we should support the Vertical and Horizontal List Display Modes as well. But rather than showing the data-block type icon there (which is rather useless), show the preview, which is much more important typically.\n\nThis may actually be nice for the regular File Browsing as well, but there it may be more important to have an icon to quickly differentiate the different file types.", "Context menus for Grease Pencil layer visibility/lock icons are inconsistent between editors\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.93.0 Beta\nWorked: (unknown)\n\nWhen selecting a Grease Pencil object, the \"Object Data\" tab of the Properties editor shows the object's layers, where each layer has (among others) an eye icon for visibility and a padlock icon for locking. These icons can not only be left-clicked to toggle their state, but also right-clicked to open a context menu for animating them (through keyframes or drivers).\n\nThe Grease Pencil mode of the Dope Sheet editor also lists the layers and also has these icons, but while left-clicking them does the same as in the Properties editor, right-clicking does not: it opens the context menu for the channel instead.\n\nFor the other Dope Sheet icons (\"Use Mask\" and \"Onion Skinning\"), the context menu works as expected.", "Lookdev HDRIs are interpreted incorrectly when using different colour spaces\nOperating system: Any\nGraphics card: Any\n\nBroken: 2.82 (sub 1), type: Release\n\nHDRIs installed into Blender for use in Lookdev Mode don't offer an option to set their colour space.\n- Blender probably assumes they are encoded in Rec.709, but this doesn't hold up if they're not.\n- Alternatively, when using a different OCIO config, the Rec.709 colour space is almost never listed as just 'Linear', so Blender picks a different space from the config.\nBoth scenarios cause undesired hue shifts. This is most probably also true for MatCaps, but to be fair I haven't looked yet into how they work.\n\n\n- Install a differently encoded HDRI into Blender, for example one of the EXRs from the imageworks/OpenColorIO-Configs repo on GitHub.\n- Switch the viewport to lookdev mode and activate the newly installed HDRI. The colours will have shifted.\n\nor:\n\n- Start Blender using an alternate OCIO config, such as one from said imageworks/OpenColorIO-Configs repo.\n- Switch the viewport to lookdev mode and try the HDRIs that ship with Blender by default. Those colours will also have shifted.", "Color of header-bar of Graph and Drivers Editors is darker than that of the other editors.\nOperating system: Linux-4.19.69-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40\n\n\nBroken: version: 2.80 (sub 75)\n\n\nColor of header-bar of Graph and Drivers Editors is darker than that of the other editors. This looks a bit inconsistent.\nI feel that the color should be lighter as in Timeline and other editors.\nI'm using the default Blender Dark theme, and haven't changed any of the theme settings.\n\n\n[Based on the default startup .blend file]\n\n{[F7723159](Graph_Editor_header_color_darker.png), size=full}\n\nThanks!", "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", "Dope Sheet: Keyframe Type Colors and Shape Improvements\nAfter the spring production the animation team at the blender institute had a meeting, to come up with the issues we had during the production and sharing them with the developers.\n\nOne of the issues we had, was that the \"Set Keyframe Type\", which changes the color of the keyframes, was really hard to see due to non saturated colors + size changes. When keyframes are dense, the keyframe type becomes almost impossible to see. We agreed that this feature was really useful for organizing the keyframes of a shot, but it needed improvements.\n\n### Current behaviour:\n\n{[F7785806](Set_Keyframe_Type_Visibility_UnSelected_Original_Comparison__copy_1_.png), height=55}\n\n - The size of the keyframe changes, 3 of the 5 options make the icons smaller, making them harder to find\n - The colors are not bright enough.\n - Colors of Selected/Unselected are too similar.\n\n{[F7785842](Set_Keyframe_type.mov), loop, autoplay, layout=left, float}\n\n\n- Keyframe colors become almost impossible to see when there are more keyframes nearby.\n\n---------------------------\n\nSo we came up with a proposal with three main points in mind:\n\n- The user is the one deciding the color/shape\n- Clear colors\n- Clear Shapes (so they are easy to see even for color blind people, as some of them might not be able to differentiate the colors)\n\n### Animation team proposal:\n\n{[F7785822](Set_Keyframe_Type_Visibility_UnSelected_Mock_Up_Comparison2__copy_1_.png), height=50}\n\nThis visualizing way could also propagate to the graph editor, which connects with [D5621](D5621) :\n\n{[F7785827](Graph_Editor_Key_Visibility_Blue_Selected__copy_1_.png), height=250}\n\n\n ---------------------------\n\nBut this proposal fundamentally conflicts with the new way of visualizing the handle type in the dopesheet, as that one changes the keyframe shape as well.\n\n## Current handle type icons\n\n{[F7785830](handletype-current.png), height=50}\n\nFor the animators at the studio showing the handle type in the dope sheet is not really useful, so we keep the option off, but we understand that there are other users that will find these really useful.\n\nI think it's important to understand how we use the dopesheet: \n\n- Since generally every bone has 9 different channels, and we are dealing with a lot of bones in a rig, we keep the channels collapsed in the dope sheet, using the summary or the top channel to make changes, if we want more precise control we'll jump into the Graph Editor.\n\nThe main issues we have with the handle type visualization and the interpolation type visualization are:\n\n### Spring shot file example\n\n{[F7785832](springshotexample.png), height=80}\n\n- When you have a lot of keyframes together the shape difference is so small it becomes really hard to see, becoming more confusing than helpful.\n \n### Open - Collapsed example:\n\n{[F7785835](coolapse-open.png), height=250}\n\n\nWhen the channels are collapsed, the information shown is not reliable. In the example used above, each one of the channels have different handle types and different interpolations. When collapsed there is no single type to be shown, creating misinformation. \n\n---------------------------\n\n## Conclusion:\n\nKeyframe colors are important. We propose an improvement by:\n\n - Clarifying keyframe-type colors and shapes in the dopesheet\n - Suggesting this would be useful in the graph editor too ([D5621](D5621))\n - Offer a switch between handle-type shape and keyframe-type shape (instead of the on/off switch for handle-type shape).\n```\n\n```\n*I’m not not a designer, so this is not final or beautiful design just a proposal to visualize my points. \n" ]

[ "Icons not loading\n\nIntel i3 core and Intel Graphics Media Accelerator (GMA) HD Graphics\n\n\nBroken: 2.69. r60995\nWorked: First vision downloaded.\n\nI downloaded the software for the first time, and when it opened the icons appeared to be transitions or matalic looking. You can not see the icons at all and it appears they did not load or were replaced by the blur of colors in their place. \n\nI downloaded the US 64 Bit version with the installer in it. Ran the installer and it opened the program at the end of the installing. The icons were never comprehensible. \n", "Tool icons look erased.\nOS: Windows 7 64 bit\nGraphics: Intel Graphics\n\nBroken: 2.71\nWorked: (optional)\n\nI just upgraded to blender 2.71.\n\nAll tool icons in the menus appear erased. See image. \n\nI was using Blender 2.66 before i upgraded, and the icons worked fine.\nI'm not sure if this is the right way to report this, please help.\n\nJust launching Blender 2.71", "Intel OpenGL on ms-windows driver displays blurry icons\nGood Day\nwhen i use the program i got color boxes instade of buttons as shown (i hope) in the pic\n\nthank you in advance\n(i am using a HP Elitebook 6930p, and i think the GPU is too old)\n\n\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\n", "All of the Interface icons are blurry - Intel onboard graphics MipMap failure\n%%%--- Operating System, Graphics card ---\nWin7 64bit; integrated graphics with an intel core 2 duo\n\n - Blender version with error, and version that worked ---\n2.66--32 and 64bit both have this problem\nI have never had this problem before.\n\n - Short description of error ---\nAs seen in the picture, all of the icons (in the outliner, splash screen, properties window, etc.) are blurry.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\n\n\n%%%", "Most if not all interface icons fail to load.\n%%%most if not all interface icons fail to load, displaying a white box where there should be an icon in the interface. this problem does not ocour on all computers, but does effect mine. I use windows 7 with a celeron processor and an integrated graphics card.(yes i am well aware my hardware is low end) the previous stable release of blender(2.49) never experienced this problem. if there is anything that can be done to fix this please let me know. blender is just about unusable in this state. I do have ubuntu linux installed on another partition and will post an update next time i boot into it.%%%" ]

[ "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", "Disappearing buttons in pie menu, depending on button text length and use of align=True\nOperating system: Linux-4.15.0-144-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\nWorked: - \n\nI have a pie menu, with a section like this:\n\n\n```\n box = pie.split()\n column = box.column(align=False)\n \n row = column.row(align=True)\n row.operator(\"transform.translate\", text=\"(B) Get Backup\")\n row.operator(\"transform.translate\", text=\"(V) Match\")\n\n row = column.row(align=True)\n row.operator(\"transform.translate\", text=\"(D) Project\")\n row.operator(\"transform.translate\", text=\"Unwrap\")\n```\n\nChanging the column's align argument to True, leads to the Unwrap button disappearing.\nIt can be brought back by changing the text length of any of the buttons. For instance, you can shorten or lengthen the Unwrap button's text. Same for the other buttons, changing the text length will usually bring the Unwrap button back. \n\nSee [video demo ](watch?v=v3VkH44p7xk): \n\n[disappearing_button.blend](disappearing_button.blend).\n\nI've checked back until 2.77 and it's present in all versions since, likely before that too.\n\n* open the blend, run the script in the text editor\n* the pie pops up and all 4 buttons are present\n* set the column's align arg to True\n* the Unwrap button disappears\n* change the text length of any of the 4 buttons to make the button re-appear\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)", "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", "Pen input UI/UX issues\nThis task keeps track of the UI/UX related design issues in all Blender mode that don't work as intended or can greatly improved with pen input devices. \nIf we consider that most pen input devices have at least one button in the pen, this will mostly include feature that rely on mouse wheel events. \n\n\n## Edit mode\n\n- ##Number of Cuts## of loop cut and slide can't be controlled during modal operation, needs to be adjusted with the redo panel.\n- Proportional editing size can only be adjusted incrementally with keyboard shortcuts instead of with pen gestures (like brushes in all modes)", "Scene pre/post handlers are called for each main loop iteration\nTitle says it pretty much everything. just execute this in py console:\n\n```\ndef cb(sce): print(\"foo\")\n\nbpy.app.handlers.scene_update_post.append(cb)\n```\n\n…and you'll get endless 'foo' lines in your console, even when Blender is hidden and all.\n\nIssue is, main loop calls (through `wm_event_do_notifiers()`) `BKE_scene_update_tagged()`, which unconditionally fires those pre/post scene update handlers.\n\nNot quite sure what's to be done here really, not familiar at all with this area of the code.", "Addon custom categories/tabs are broken (are gone after a session)\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 511.79\n\nBroken: version: 3.1.0\nBroken: 2.80\nWorked: 2.79\n\nChanging the category (in add-on preferences) on add-ons that allow you to change the category does not retain placement after restart.\n\nTested using \"Align Tools\" add-on as example.\nRelevant reference:\nT48459\n\n- Open default scene\n- Go to \"Align Tools\" (Prefs > add-ons)\n- Enable add-on and change `Tab category` string to something else (say \"AB\")\n- Save preferences\n- restart blender.\n- Now the label of tab remains same (AB) in preferences but it does not reflect in UI (sidebar)", "Improve keyboard usage for menu search popup\nNA\n\nBroken: example: 2.78\nWorked: >new feature request<\n\nwhen spacebar search menu popups and user start writing the required command, only down-arrow keyboard shortcut are allowed to select the required command, starting from first item on top.\nIt will be very useful and faster if also up-arrow can be usable to select the last item in the list (so starting from bottom).\nSee image as reference: green arrow show the required feature, red one is the only one actually working.\n\n\nnot an error, only UI usage improvement :)\n", "Regression: Curve wire line not displayed in edit mode when it has evaluated mesh/point/volume\nBroken: 3.0, 3.1, 3.2\nCaused by b9febb54a4\n\nThe original line for edit mode curves is not displayed in edit mode .\n\nThis change only applies when the curve is changed during evaluation, for example, when it is replaced by an evaluated \"tube\" mesh, or points, or a volume, etc.\n\n| Before | After |\n| -- | -- |\n|  |  |\n(Ignore the change in lightness there, it's just a different UI scale)", "VSE UI: Overlay Source text displays nothing & default Overlay text design considerations\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\n{[F10310240](image.png), size=full}\n\nWhen I implemented the Overlay dropdown, the main intention was to clean up all of the text on strips which clutter the VSE UI, however the patch was changed and my defaults never made it into the commit. The idea was the only Source should be displayed as default setting, unless Name differed from source. Source was implemented to show the strip type names or the content of the strip ex. for Movie files it would show the path and for text strips the content text. \n\nFor some unknown reason ex. effect strips do no display any type when Source is selected, and it should. They were properly removed to avoid both Name and Source saying the same, but if Source is only displayed when it differs from Name, then that problem wouldn't occur. \n\nSo the fix is:\n- Display strip type as Source, if no content to display(ex. Movie path or Text).\n- Display only Source if it differs from Name(and both overlay options are selected).\n- Remove Duration as default. \n\nOr the fix could be, if the content of the Text strip(currently only displayed with Source on) was written in the content area(ex. where the color of the color strip is displayed), then Name could be on as the only Overlay text setting. Like this:\n{[F10310203](image.png), size=full}\n\nOr Source could be split up into: Strip Type and Content(displaying url, text etc.).\n\nBasically, I think the default setting should display only the file name, or the strip type if no filename, and then have the content text in the content area of the strip.\n\n\n", "macOS todo list\nNOTE: this is a direct dump of Install-OS\n\n- [ ] Users have to manually change macOS defaults:\n * Map middle mouse to regular \"Mouse button 2\"\n * Make the Function keys use modifiers (so Blender sees these)\n * Change the Shift+NumPad options to not use Shift (change spaces)\n * The latter two could become part of a new standard macOS compliant map in the future?\n- [ ] ~~Finder aliases or~~(1f223b9a1f afb1a64ccb) hidden files are not being recognized by Blender\n- [ ] macOS swallows some key events, like e.g. emulated numpad - on Norvegian keyboard (see #38273).\n- [ ] Blender prevents macOS from sleep #38702", "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.", "Font rendered incorrectly with text object\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nThe font is displayed incorrectly when added to 3d text object\n\nFont and blend file in attachment\n[untitled.blend](untitled.blend)\n\n[roadrage.ttf](roadrage.ttf)\n\n", "Windows/msi installer: Blender casing in the installer is lower case\nOperating system: Windows\nGraphics card: Irrelevant \n\nBroken: 3.4/3.5\nWorked: No idea\n\n\nThe Blender .msi installer on windows has a lower case 'blender' in the title bar\n\n\n\n\nUse the installer.\n\nEverything on the blender repository side is configured to have a capital B, when I build an installer locally it indeed has the right capitalization. @brecht showed me part of the build bot scripts when this last came up that forced that specific variable to lower case so this needs to be fixed on the bots to either by it having the right capitalization or to stop it from overriding this specific value.\n\n", "Text object automatic bold/italic creation when font's aren't present\nCurrently the user needs to set bold/italic fonts, which may not always exist.\n\nThis task proposes to automatically calculate bold and italic fonts.\n\n- Italic: adjust slant with slider for how much to slant the text.\n- Bold: thicken the font by expanding the curve before tessellation.\n\nNote, automatic bold-creation is very likely to cause self intersection, we may need to improve filling before this is practical, or - filling may need to be performed on un-expanded charactersl" ]

[ "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\" " ]

[ "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", "Baking vertex colors does not respect alpha with \"Diffuse\" selected but respects alpha with \"Direct + Indirect\" also selected\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\nI believe this is a bug: when baking vertex colors, the alpha channel is included ONLY if \"Direct + Indirect + Color\" are all enabled, but then lighting gets baked in as well which is often not intended.\nThis leads to the situation that It doesn't look like there's a way right now to bake just color + alpha to a Color Attribute with alpha channel.\n\n- open the attached blend file: [BugDiffuseAlphaVertexBake.blend](BugDiffuseAlphaVertexBake.blend)\n- select the Cube\n- switch viewport to Eevee\n- make sure Render Engine is set to Cycles so things can be baked\n- in the Bake tab, click \"Bake\" with Bake Type=Diffuse and Contributions=[Color]\n- note the result doesn't have an alpha channel in vertex colors, it's just black\n\n- now, enable \"Direct\" + \"Indirect\" and Bake again\n- note the result has aloha channel BUT now looks incorrect as only diffuse was intended to be baked...\n\n\n- also note that neither \"Color + Direct\" nor \"Color + Indirect\" result in an alpha channel\n- both \"Direct\" only and \"Indirect\" only result in alpha channels but then the color can't be baked.", "Cycles fully transparent shader is brighter when a Clear Coat shader is behind it\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.3.0 Alpha\nWorked: Never Worked\n\nWhen doing Decals, we often use alpha channel to define transparent area. However, I found when the Object's base color is above hsl(h,s,0.01), who's under the Decal, then the decal's transparent area will affect the underneath object's shading.\nMy test configuration is that 2048 viewport samples alongwith light bounces param all been set to 64.\nThe BUG is easier to notice when the background object is light grey, and the light is quite dimmed(or just turn down the exposure in colormangement to observe.)\n\n\n\n\n\nPlease open the attached Blend file to test.\n[Transparent shading BUG.blend](Transparent_shading_BUG.blend)\n\n", "Color > Multiply doesn't multiply alpha channels\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) 3.6.2\n\nThe Color > Multiply section in a video sequencer strip no longer multiplies the alpha channel when that feature is pretty important for creating outlines using the glow effect. Perhaps adding an option whether to multiply alpha or not would be beneficial?\n\nStart up blender 4.0.0\nSwitch to Video Editing workspace\nAdd a white color strip with 0.1 opacity\nAdjust the Color > Multiply value and notice how it doesn't affect alpha anymore\n\n", "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", "Motion Blur missing in the Render Preview of viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\n\nIn 2.83 we had the access to realtime motion blur with Eevee (which was limited to camera deformation).\nIn 2.90 and above this was replaced with a new motion blur system that is render only. \nEevee is amazing for having realtime screen space reflections, ambient occlusion, depth of field and motion blur, which made it perfect for screen capture or viewport rendering an animation without excessive time consumption.\nI was wondering wether this is a decision or a bug, since having the camera deformation motion blur back in the viewport would allow for the same realtime rendering results as in 2.83\n\n- Go to camera view\n- move the camera around\nIin 2.90 and above and youll see any motion blur previously existent in 2.83 is gone. \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", "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.", "Cycles: Keyframing motion blur shutter value fails to apply it properly when generating animation\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\n\nBroken: 3.6, 4.0\n\n\nIf we keyframe shutter property of motion blur, the updated shutter value is not considered during the final render.\nSuppose shutter value is 0 at the start of render, it will remain 0 thorught the animation even if we've keyframed the value.\n\n- Open attached file\n- select cycles render Engine\n- Start animation render (Ctrl-F12)\n", "HDRI background shows lighting artefacts at zero strength\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nDont know if this is a Blender issue, but I encountered a few HDRI files that still show light sources despite having zero strength in the viewport shading studiolight setting:\n\nThe HDRI file is:\n[blue_lagoon_night_2k.hdr](blue_lagoon_night_2k.hdr)\n\nThe lighting comes from remaining artefacts at the spot of the lamp. Its more noticable with a bit of blur, but you can still see it without.\nSince this is only an issue for some HDRI Backgrounds I assume it has to do with those files, I dont know. Regardless, it would be nice if Blender could take care of these cases to guarantee a dark background.\n\n\n[HDRIBackgroundStrengthBug.blend](HDRIBackgroundStrengthBug.blend)\n1. Install the attached HDRI File and set it as background.\n2. Change the strength setting for the Viewport Shading to zero.\nProblem:\nThe background lightens the scene at zero strength with the remaining artefacts.\n\n", "Default Value for Viewport Display Color's Alpha Wrong.\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 457.09\n\nBroken: version: 2.92.0 Alpha\nAlso tested on 2.83.8 and same problem.\nWorked: It do not think this has ever worked\n\nWhen reverting to the Default Value for Viewport Display Color the alpha gets down to 0.8 making the object semi transparent.\n\nOpen up a new scene.\nSelect the cube.\nGo to the materials tab.\nScroll down to \"Viewport Display\"\nRight Click on \"Color\"\n\"Reset to Default Value\"\nResult: RGB values go back to the default, but Alpha goes to 0.8\n\n\nThank you so much !", "compositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image.\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: (4.0 alpha from a few weeks ago not sure of version as deleted now)\n\nCompositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image.\n\n1. Open a new blend file.\n2. Go to the compositor.\n3. Drag in the image file attached below.\n4. Connect the resulting image node's 0_Image output to a viewer node and turn on the backdrop.\n5. Image will be shown.\n6. Now place a blur node between the image node and the viewer node.\n7. Set the x and y values of the blur node to 1 and the size to 1.\n8. Image will blur.\n9. Now change the blur mode to fast gaussian.\n10. Image will go completely black.\n\n[test-image](https://projects.blender.orgattachment)", "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", "Optix Viewport Denoiser Makes Objects Glow When Using High Exposure Even When There is no Light in the Scene\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nThe latest build added the feature to let non-RTX GPUs use the denoiser, so I tested it on my scene right away. However, the objects in the scene start glowing when the denoiser starts working. The scene was lit using the Physical Lights feature that the Photographer 3 addon has provided, which offers units like Lumen and Candela, etc. And since physically correct light values can sometimes be very dim (like a candle = 1 candela), sometimes be very bright (like the Sun at noon 111,000 lux), Photographer offers real life camera's settings for modifying the exposure in the color management in the render settings to adjust the overall brightness. And in my scene, I used a candle, which is very dim. Therefore the exposure has been set very high. It has been fine until the denoiser came. \n\nBased on the default startup\n1. Delete the default point light\n2. Turn the World Background Strength to 0\n3. Turn the Exposure in the Render Settings under Color Management to 10\n4. Change the render engine to Cycles\n5. Turn on render view, you should see nothing but complete darkness\n6. Turn on the Optix Viewport denoiser\n7. Wait for a while and see the default cube glowing\n\nI don't know if this is a bug or not, if it is not, please at least get some work around. Like making the denoiser refresh when the exposure changes or something?\n\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." ]

[ "Eevee does not render alpha when DOF is turned on \nubuntu 16.4\n\nblender 2.8 9596dfc26af\n\nEevee does not render alpha when DOF is turned on \n\ncheck the attached blend file , turn on DOF in rendersettings and press f12 , render will not have alpha \nnow turn off DOF in rendersettings and press f12 , render image will have alpha \n\n[test dof.blend](test_dof.blend)\n" ]

[ "Unable to get object to stay hidden while new mesh tool is active.\nWindows 10, 1060\n\nBroken: 2.80 master (also reproduced in a month-old daily build, so not new behavior).\n\nIf you have an active tool like Add Cylinder going, and you hide another object using the eye icon in the outliner, then as soon as you touch the cylinder parameters, the hidden object becomes unhidden.\n\n1) From the default scene, Add a Cylinder to the scene and expand the tool properties in the lower left of the 3dview.\n2) Because the cylinder is hidden inside the cube, we can't easily see the effect of changing the tool parameters, so go to the outliner and click the eyeball icon associated with the cube to hide it in the viewport.\n3) Change any parameter in the cylinder tool properties pop-up in the 3dview. The cube reappears and the eyeball indicates it is no longer hidden.\n\nBasically any changes made to the Outliner visibility icons gets reverted as soon as you change any active tool property, (at least for the Cylinder tool). This at least unexpected behavior.", "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).", "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)", "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", "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", "keyboard shortcut to switch between vertex / edge / face not present in tooltip\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nI rely on the tooltips to learn keyboard shortcuts.\nWhen hovering above the vertex / edge / face select button, the shortcut to enable this button is not mentioned.\nexpected: \nVertex Select: 1\nEdge Select: 2\nFace select: 3\n", "Knife cursor goes away when dragging status bar to see options\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 531.41\n\nBroken: version: 3.5.0\n\nWhile using the Knife tool, and using middle mouse click and drag to see all options within the status bar, the knife cursor changes to the edit cross cursor. This doesn't happen when using the mouse wheel to scroll through the status bar. It also doesn't happen using the Knife Active Tool, only when pressing K to launch the tool.\n\n1. Press K in Edit Mode to launch the knife tool\n2. Move the cursor over to the status bar, where the options for the tool are shown.\n3. Middle Mouse click and drag left and right to scroll through the status bar.\n\n[Knife cursor dissappears.mp4](attachment)\n\n", "Sample color add to palette, works for mouse click but not key press only\nOperating system: Windows 10 64-bit\nGraphics card: NVIDIA GeForce GTX 960M\n\nBroken: 2.80 2019-02-05 23:34\nWorked: (optional)\n\nUsing the **sample color** tool, **add to palette** option does not work properly.\n\n1. Press S+LMB with cursor on any color. The option **add to palette** is checked automatically(at the tool properties panel at the bottom left) and the color is actually added to the palette(tool properties bar at the top > brush).\n2. Press S with cursor on any other color(do not click). The option **add to palette** is still checked(because it remembers the last operation). new color is extracted and is now the foreground color. However it does not add the new color to the palette. Strange.\n3. Press S with cursor on any other colors(do not click). It behaves the same. **Add to palette** is checked but is not working.\n\n**Extra bug**\n1. Press S with cursor on any color(do not click). The option **add to palette** is not checked automatically.\n2. Try to enable the checkbox **add to palette**.\n3. Blender crashes.\n\nMaybe the solution is just to get rid of the checkbox **add to palette**.\nS is sampling color to foreground color, S+LMB is sampling color to palette. Why would we need the checkbox?\nIt is also possible to add the color to palette after sampling(to foreground color). This option doesn't seem necessary to me...\n\n[bug-samplecolortool-addtopalette.blend](bug-samplecolortool-addtopalette.blend)", "Sculpt Mode Border Hide Tool Todo\n## Sculpt Mode Border Hide Tool Todo\n * - [x] {icon circle color=red} When this tool is selected, it currently shows the wrong tool settings which affect the brushes, not this tool. These should not be visible when this tool is active.\n * - [ ] {icon circle color=yellow} We should add a tool setting to add/remove the mask as you drag. Currently, the only way to remove from border hide, is very hidden: You drag with RMB. This could become more consistent and more discoverable if we added the same Add/Remove buttons as with other Sculpt tools", "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", "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", "custom brushes icon won't show up is some cases\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\n\nIn some cases the custom icon of the brushes won't load properly. Even by reassigning it it doesn't work.\n\nOpen the attached file and try to assign the accatech custom icon to the active brush (but anykind of image won't load)\n\nThankyou\n\n\n\n[icon.blend](icon.blend)", "Grease pencil eraser settings not loaded on startup when using ctrl+LMB with the Draw tool\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 26.20.100.7925\n\nBroken: version: 2.90.0\n\nWhen first opening a blend file, your eraser settings are set to default when using ctrl+LMB with the draw tool, and only update after switching to the eraser tool and using it.\n\n\n- Open attached file (the Stroke object is selected and the Draw tool activated in Draw mode).\n- Draw a line\n- Erase part of the line using the same tool but with Ctrl selected. Notice how it behaves as if the `\"Eraser Soft\"` brush is used. \n- Switch to the Eraser tool, erase part of the line. Notice how it behaves according to the specified Brush: `\"Eraser Point\"`. \n- Switch back to Draw tool, and hold down ctrl to erase another part of the line, it should now start behaving like the `\"Eraser Point\"` brush.\n\n[eraser bug.blend](eraser_bug.blend)\n\n", "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", "Improved Rake functionality\nFor now it would be best to focus this implementation on Sculpt Mode, since this will be the basis of the upcoming Paint Mode.\n\n## Issue\n\nWhen using an image texture in a brush you can enable the option \"Rake\" so that the texture rotation is following the direction of the stroke.\nThis has a huge issue that it stamps the entire texture repeatedly which makes it impossible to create a smooth curved texture that accurately follows the stroke.\n\n\n\n\n\n## Proposal\n\nEssentially we need to implement a way to split up the brush texture into many thin slices and apply them to the stroke incrementally.\nThis way it will have the visible effect of putting the texture on a paint roller and rolling it over a surface.\nThis would also make it possible to assign a very wide texture to a brush and paint it in a curved way on the surface.\n\n[roll brush mockup.mp4](roll_brush_mockup.mp4)\n\nAdjusting the texture size should help to redefine how stretched the used texture is:\n\nSize = 1\n\n\nSize = 0.25\n\n\nSize = 2 \n\n\n### Open Questions\n\nIt still needs to be discussed how this setting will be exposed and how it relates to the mapping, stroke and rake setting." ]

[ "Tools selected from Quick Favorites menu don't update cursor icon properly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.83 (sub 4)\nNot working in 2.82 either\n\nSelecting tools from Quick Favorites doesn't update the cursor icon straight away. Specifically, they seem to retain the previous tool's cursor icon. This is supported by the fact that selecting a tool twice from the Quick Favorites menu updates the icon \"correctly\" (though it's simply reading from the tool's first selection).\n\nIt does not appear to affect extra cursor features like Brush Falloff/Eraser Ring (those update correctly).\n\n[2020-02-18_19-55-07.mp4](2020-02-18_19-55-07.mp4)\n\nHere's another example in a 2D Workspace (shows problem more clearly):\n[2020-02-18_20-06-28.mp4](2020-02-18_20-06-28.mp4)\n", "Mouse pointer/cursor doesn't update when changing tools via shortcut or pop up menu\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nMouse pointer doesn't change to the tool you have selected if you use shortcut or pop up menu. \nFor example, if are using Knife tool, the pointer looks like a... Knife. But if then change to Select or any other tool via shortcut or using the pop up menu, it will keep the little white knife as the pointer even though you are now using another tool.\n\n(Using LEFT-CLICK mode).\n- Default startup file\n- Enter EDIT MODE on Cube\n- Change tool to KNIFE (clicking on toolbar on left)\n- Now change to SELECT BOX via shortcut (W default) or using pop up menu via Shift Spacebar\n\nYou will see that the mouse pointer keeps a Knife icon, even though you can normally use the function of the tool you've selected.\n\nThe opposite is also true. If you are on SELECT BOX and change to KNIFE via pop up meno (shift spacebar) the pointer doesn't update.\n\n", "Grease Pencil icon wont change.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Radeon 500 Series ATI Technologies Inc. 4.5.13571 Core Profile Context 19.10.1 26.20.13025.10004\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nGrease Pencil Icon won't change after changing the tool in the tools panel.\n\n1. Press the Grease Pencil / Annotation icon and draw something with it.\n2. Press W to return to the select tool.\n\nNow as you can see the Icon does not change but the functionality changes to select mode.\n\n\n\n[2020-02-12 20-14-50.mkv](2020-02-12_20-14-50.mkv)\nIn the video, I first draw something by holding the D button.\nThen I draw by using the Grease Pencil button.\nAfterwards, I change the tool to select mode Via the hotkey \"W\".\nAnd the icon does not change but the functionality changes.\n", "A little Glitch with knife tool icon\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nHi, Blender team. I have encountered a little glitch with knife tool viewport icon icon. The icon doesn't change on the crosshair, when i change knife tool on box selection tool and vice versa.\n\nOne can try to recreate it in startup file.\n1) enter in Edit mode\n2) Select knife tool (from tool bar of tool box (menu which is activated with Space button), doesn't matter)\n3) Change knife tool to box select tool with tool box (menu which is activated with Space button) Important: do not leftclick on box selection tool, just hover cursor over it and left up Space button\n4) You have activated box select tool and watching knife tool icon instead of crosshair icon.\nIt work properly if once leftclicks on the box menu tool instead just hovering cursor on it and release Space button \nThe glitch happens both ways changing from knife tool to bot selection and from box selection to knife tool\nThanks in advance, And have a nice day, guys.\n\n", "Wrong change of tool icon in 2D animation\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen using Shift + Space and selecting a new tool, the previous tool icon falls on the new tool\nDraw a shape. Using Shift + Space select the Cutter tool and cut out a part of the shape and then click Shift + Space again and select Draw tool, then you will see a problem with the icons{[F8353284](Bandicam_2020-02-20_15-38-58-700-1.m4v)}" ]

[ "Blender full crash during smoke+noise baking \"EXCEPTION_ACCESS_VIOLATION\"\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\nCPU: Ryzen 5900X\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nEvery single time I try to bake a high res particle system, in this case, fire at 256 + default noise settings, it never gets to complete the render and the blender crashes completely (including the console running in the background) at around frame 60 / 150.\nPausing and resuming baking sometimes works but most of the time it instantly crashes on the resume.\n\nEdit:\nI currently have 32 GB RAM and they are not really under much use during the bake.\nI tried with an RTX 3070 and Ryzen 5800x and the same issue.\n\nCrash file:\n\n\n```lines=30\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF76E01AD1A\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x000001C8281373F8\n\n\nStack trace:\nblender.exe :0x00007FF76E01A850 adaptive_domain_adjust\nblender.exe :0x00007FF76E021580 update_flowsfluids\nblender.exe :0x00007FF76E01F380 manta_step\nblender.exe :0x00007FF76E018CD0 BKE_fluid_modifier_processDomain\nblender.exe :0x00007FF76E018530 BKE_fluid_modifier_do\nblender.exe :0x00007FF76E2CC220 modifyMesh\nblender.exe :0x00007FF76E0C4DF0 mesh_calc_modifiers\nblender.exe :0x00007FF76E0C4AF0 mesh_build_data\nblender.exe :0x00007FF76E0C7170 makeDerivedMesh\nblender.exe :0x00007FF76E0A65F0 BKE_object_handle_data_update\nblender.exe :0x00007FF76E0A6320 BKE_object_eval_uber_data\nblender.exe :0x00007FF771D6AFA0 std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph * __ptr64,Main * __p\nblender.exe :0x00007FF771D69380 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF771D69330 blender::deg::`anonymous namespace'::deg_task_run_func\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF771DEE500 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFDEAAFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThreads:\nThread : 00002380\nntdll.dll :0x00007FFDEFFED280 NtDelayExecution\nKERNELBASE.dll :0x00007FFDEDB18FE0 SleepEx\nblender.exe :0x00007FF76E122380 wm_window_process_events\nblender.exe :0x00007FF76E1184D0 WM_main\nblender.exe :0x00007FF76DE09C70 main\nblender.exe :0x00007FF772313468 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000024a0\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000549c\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006094\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003a78\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000722c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000058fc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004090\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005f20\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000029a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000047b8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005718\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ba0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002ae4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006820\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001738\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c44\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004984\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c48\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000389c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002d68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002f90\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00007248\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005010\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002668\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000571c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000017f0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000060a4\nntdll.dll :0x00007FFDEFFF05F0 ZwWaitForAlertByThreadId\nntdll.dll :0x00007FFDEFFB3EF0 RtlSleepConditionVariableSRW\nKERNELBASE.dll :0x00007FFDEDB3C8A0 SleepConditionVariableSRW\nMSVCP140.dll :0x00007FFDD2CEBA70 _crtSetThreadpoolWait\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c64\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001d08\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ea4\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003cb8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000dd8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071bc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nnvoglv64.dll :0x00007FFD2046D50D Symbols not available\n\n\nThread : 000058f8\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFDEDB1C460 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20B35890 vk_icdNegotiateLoaderICDInterfaceVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000037dc\nwin32u.dll :0x00007FFDEDDDA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFDEF8A06F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002bcc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000031b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001778\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c94\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003e70\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000059b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000070a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003fd4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005b68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005508\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002c88\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000587c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000065ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000055ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006998\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001c30\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004bd0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000ee0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000049c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000041a8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000721c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000077f0\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\nblender.exe :0x00007FF76E319F80 tbb::internal::task_group_base::wait\nblender.exe :0x00007FF771D68EC0 blender::deg::deg_evaluate_on_refresh\nblender.exe :0x00007FF76DF8E3C0 BKE_scene_graph_update_for_newframe\nblender.exe :0x00007FF76E7B6A90 fluid_bake_startjob\nblender.exe :0x00007FF76E13D7D0 do_job_thread\nblender.exe :0x00007FF77234F320 _ptw32_threadStart\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF76DCE0000 2.9.2.0 blender.exe C:\\Program Files (x86)\\Steam\\steamapps\\common\\Blender\\blender.pdb \n0x00007FFDEFF50000 10.0.19041.844 ntdll.dll \n0x00007FFDEE790000 10.0.19041.804 KERNEL32.DLL \n0x00007FFDEDAD0000 10.0.19041.906 KERNELBASE.dll \n0x00007FFDEF880000 10.0.19041.906 USER32.dll \n0x00007FFDEDDD0000 10.0.19041.906 win32u.dll \n0x00007FFDEF500000 10.0.19041.746 GDI32.dll \n0x00007FFDED770000 10.0.19041.746 gdi32full.dll \n0x00007FFDED880000 10.0.19041.789 msvcp_win.dll \n0x00007FFDEAAF0000 2019.9.0.0 tbb.dll \n0x00007FFDEDE00000 10.0.19041.789 ucrtbase.dll \n0x00007FFDEEDB0000 10.0.19041.906 SHELL32.dll \n0x00007FFDED920000 10.0.19041.546 CFGMGR32.dll \n0x00007FFDEEA40000 10.0.19041.546 WS2_32.dll \n0x00007FFDEE5E0000 10.0.19041.746 RPCRT4.dll \n0x00007FFDCFCF0000 7.0.0.0 openvdb.dll \n0x00007FFDCF740000 10.0.19041.844 OPENGL32.dll \n0x00007FFDEEC60000 10.0.19041.610 ADVAPI32.dll \n0x00007FFDEED10000 7.0.19041.546 msvcrt.dll \n0x00007FFDEEAB0000 10.0.19041.906 sechost.dll \n0x00007FFDEDFF0000 10.0.19041.906 combase.dll \n0x00007FFDEE850000 10.0.19041.746 ole32.dll \n0x00007FFDEEA30000 10.0.19041.546 PSAPI.DLL \n0x00007FFDEEB50000 10.0.19041.746 SHLWAPI.dll \n0x00007FFDCF870000 3.7.7150.1013 python37.dll \n0x00007FFDEDFB0000 10.0.19041.546 IMM32.dll \n0x00007FFD22410000 58.54.100.0 avcodec-58.dll \n0x00007FFDCD5C0000 58.29.100.0 avformat-58.dll \n0x00007FFDEAB40000 58.8.100.0 avdevice-58.dll \n0x00007FFDEE510000 10.0.19041.804 OLEAUT32.dll \n0x00007FFDD40F0000 5.5.100.0 swscale-5.dll \n0x00007FFDCF610000 56.31.100.0 avutil-56.dll \n0x00007FFDEDDA0000 10.0.19041.662 bcrypt.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFDC8FD0000 1.20.1.0 OpenAL32.dll \n0x00007FFDCE1D0000 2.0.12.0 SDL2.dll \n0x00007FFDEAAE0000 2019.9.0.0 tbbmalloc_proxy.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFDEFAA0000 10.0.19041.844 SETUPAPI.dll \n0x00007FFDD2CB0000 14.26.28720.3 MSVCP140.dll \n0x00007FFDEAAC0000 14.26.28720.3 VCRUNTIME140.dll \n0x00007FFDEAAB0000 14.26.28720.3 VCRUNTIME140_1.dll \n0x00007FFDE1F70000 6.10.19041.844 COMCTL32.dll \n0x00007FFDE7F50000 10.0.19041.1 AVIFIL32.dll \n0x00007FFDE6B50000 10.0.19041.546 VERSION.dll \n0x00007FFDD8550000 10.0.19041.844 GLU32.dll \n0x00007FFDEBD30000 10.0.19041.867 dbghelp.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFDD30A0000 3.5.100.0 swresample-3.dll \n0x00007FFDCDB10000 10.0.19041.546 Secur32.dll \n0x00007FFDD82B0000 10.0.19041.1 AVICAP32.dll \n0x00007FFDE28A0000 10.0.19041.546 WINMM.dll \n0x00007FFDD2C70000 2019.9.0.0 tbbmalloc.dll \n0x00007FFD5AD10000 10.0.19041.1 MSACM32.dll \n0x00007FFDD3070000 10.0.19041.1 MSVFW32.dll \n0x00007FFDDECB0000 10.0.19041.1 winmmbase.dll \n0x00007FFDED580000 10.0.19041.906 SSPICLI.DLL \n0x00007FFDEE980000 10.0.19041.746 shcore.dll \n0x00007FFDEBF80000 10.0.19041.546 kernel.appcore.dll \n0x00007FFDEB590000 10.0.19041.906 windows.storage.dll \n0x00007FFDED100000 10.0.19041.662 Wldp.dll \n0x00007FFDEADF0000 10.0.19041.746 uxtheme.dll \n0x00007FFDED6F0000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFDED5D0000 10.0.19041.844 profapi.dll \n0x00007FFDEEBB0000 2001.12.10941.16384 clbcatq.dll \n0x00007FFDE6250000 10.0.19041.789 MMDevApi.dll \n0x00007FFDED440000 10.0.19041.546 DEVOBJ.dll \n0x00007FFDE6400000 10.0.19041.906 AUDIOSES.DLL \n0x00007FFDECC30000 10.0.19041.546 powrprof.dll \n0x00007FFDECAF0000 UMPDC.dll \n0x00007FFDEAF10000 10.0.19041.546 resourcepolicyclient.dll \n0x00007FFDEF6D0000 10.0.19041.906 MSCTF.dll \n0x00007FFDC2F40000 10.0.19041.746 dataexchange.dll \n0x00007FFDE8030000 10.0.19041.746 d3d11.dll \n0x00007FFDE8EB0000 10.0.19041.906 dcomp.dll \n0x00007FFDEBFD0000 10.0.19041.746 dxgi.dll \n0x00007FFDE6B60000 10.0.19041.746 twinapi.appcore.dll \n0x00007FFDE7A20000 10.0.19041.906 AppXDeploymentClient.dll \n0x00007FFD1FA70000 27.21.14.6192 nvoglv64.dll \n0x00007FFDEA2D0000 10.0.19041.546 WTSAPI32.dll \n0x00007FFDED280000 10.0.19041.546 msasn1.dll \n0x00007FFDE6AA0000 10.0.19041.906 cryptnet.dll \n0x00007FFDED970000 10.0.19041.844 CRYPT32.dll \n0x00007FFDED040000 10.0.19041.546 cryptbase.dll \n0x00007FFDED690000 10.0.19041.804 WINTRUST.dll \n0x00007FFDEC4F0000 10.0.19041.546 ntmarta.dll \n0x00007FFDE5470000 10.0.19041.546 dxcore.dll \n0x00007FFDEB000000 10.0.19041.746 dwmapi.dll \n0x00007FFDEC490000 10.0.19041.546 WINSTA.dll \n0x00007FFDCB3B0000 10.0.19041.906 textinputframework.dll \n0x00007FFDE9960000 10.0.19041.746 CoreMessaging.dll \n0x00007FFDE9420000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFDE9CA0000 10.0.19041.906 wintypes.dll \n0x00007FFDC2C70000 10.0.19041.844 explorerframe.dll \n0x00007FFDEA590000 7.0.19041.867 propsys.dll \n0x00007FFDED050000 10.0.19041.546 CRYPTSP.dll \n0x00007FFDEC7A0000 10.0.19041.546 rsaenh.dll \n0x00007FFDE53A0000 3.7.7150.1013 python3.dll \n0x00007FFDD40D0000 3.7.7150.1013 _bz2.pyd \n0x00007FFDD04E0000 3.7.7150.1013 _lzma.pyd \n0x00007FFDD04C0000 3.7.7150.1013 _socket.pyd \n0x00007FFDDFD70000 3.7.7150.1013 select.pyd \n \n# Python backtrace\n\n```\nSimply bake the file attached, I can't do it and I tried with multiple brand new .blend simple mantaflow setups.\n[Cinematic Fire Simulation.blend](Cinematic_Fire_Simulation.blend)", "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", "OptiX Denoiser crashes OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\nCPU: AMD Ryzen 7 1700\nRAM: 32 GB\n\nBroken: version: 2.90.0 Alpha\nWorked: unknown\n\nWhen the Viewport OptiX Denoiser is activated it crashes with the following error *\"OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources(denoiser, rect_size.x, rect_size.y, &sizes) (device_optix.cpp:850)\"*\n\nBased in the Startup File, (Reseted to Factory Settings and userpref.blend deleted):\n1. In Preference->System set Cycles Render Devices to \"CUDA\"\n2. Set render engine to \"Cycles\"\n3. Set device to \"GPU Compute\"\n4. Set Viewport Denoiser to \"Fastest (Optix)\" or \"OptiX\"\n5. Set Viewport Shading to \"Rendered\"\nERROR *(View screenshot)*\n\nOnce the error has ocurred I can't render with CUDA, even on a new file. To be able to render with CUDA I must close Blender and open it again. *View System Console Output*\n\n**Additional Info**\n\n- The error doesn't happen if the Cycles Render Devices is set to \"OptiX\"\n- This error doesn't happen in my laptop (i7 7700HQ, GTX 1050, 16GB RAM)\n- In a more complex scene blender tries to load the render kernels for a long time before throwing the error\n\n\n[system console Output.txt](system_console_Output.txt)\n[system-info.txt](system-info.txt)\n\n\n\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)", "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", "Blender stops updating display after GPU spike\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 2.92.0 Beta\nWorked: I have not found a version that works as expected on this computer. I have tried 2.79, 2.8, 2.91\n\nI was premature in saying the problem is gone for [#85061 ](T85061).\n>After a few minutes of using Blender, the window freezes. Windows does not detect that it is not responding, but Blender does not respond to any input, including clicking on the close button. All elements that are drawn by Blender remain as they were at the moment of the crash except if I resize the window smaller.\n\nIf I watch the performance tab on Windows Task Manager, the freeze coincides with a 100% spike on the GPU.\nAs long as that spike doesn't happen, there is no problem, but once it does, Blender stops responding to any input, but it does not crash.\nI have updated my graphics drivers.\n[blender_debug_output.txt](blender_debug_output.txt)\n\nI have not determined exact steps. It has occurred on multiple files doing multiple different tasks. As far as I can tell, there is no correlation between what I am working on or what task I am performing, and the error occurring.\n", "Crash when baking a normal map from procedural materials\nOperating system:\nManjaro w/ KDE\nGraphics card:\nNvidia GTX 1060 6GB\n\nBroken: 2.80 Beta, 5e626e766459, branch: blender2.7, 2019-06-13\n\n\nI've sculpted a high poly model from the lowpoly one - baking normals from that works fine.\nWhen I created procedural materials using Geometry Pointiness, Noise, a painted texture and other sources to create additional normal information - the baking crashes.\n\nHere's the project file. It's huge (781 MB), but compresses very well (turns out the painted texture was wasting a lot of space), without it the file is only 12 MB).\n\n[Barrel_02 08.zip](Barrel_02_08.zip)\n\nNormal map baked from Highpoly model to Lowpoly model:\n\nIf you disconnect the two materials on the highpoly model and just use a default Principled shader, it bakes fine.\n\n\nThe baking process crashes at various stages. First bake crashed after an hour or so, next attempts crashed much quicker.\n\nCrash logs:\n\n[Barrel_02 08.crash.txt](Barrel_02_08.crash.txt)\n\n[Barrel_02 07.crash.txt](Barrel_02_07.crash.txt)\n\n[Barrel_02 06.crash.txt](Barrel_02_06.crash.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", "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", "CUDA problem Error: Invalid value in cuMemcpy2DUnaligned_v2(&param)\ndoes anybody know what this error mean (blender 3.5, 3.6, 4.0 win 11):\n\n*Error:Report:\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\n\n\nWe tried two rtx 4070ti video cards and this error came up when we were about to render. If I disable one of the two, the render runs fine, but if I enable both, the render freezes. I see that it starts using both, but it still gives an error.\n\nThanks\n\n", "Blender will not use new GPU for rendering or recognize it for OpenCL or\nOperating system: Windows 10, all up to date\nGraphics card: msi 4070ti (brand new)\n\nBroken: 2.93.18 as well as the most recent 3.5 on the splash screen, tried most of the in-between builds on clean reinstalls but same issue on all of them.\nWorked: no version\n\n**Error**\nAfter getting a new 4070ti, blender started crashing every 5-10mins or so while moving around a simple scene in the viewport set to material shaders mode, not render mode. The scene consisted of a couple of primitives with very simplistic wood, glass, and metal shaders. When I tried rendering as is it also crashes immediately upon rendering no matter what I use. GPU wasn't greyed out in render settings initially (though it now is), but only showed in preferences under CUDA, and wasn't recognized in OptiX or OpenCL (in newer blender models it also wasn't recognized by anything but CUDA). \n\n1. tried to render a simple scene with render settings set to new gpu\n2. render crashes immediately\n3. move around in viewport on material mode, barely move and blender crashes\n4. check Blender preferences <system <cycles rendering devices: gpu is visible in CUDA but not in any other options (originally was working on 2.93 where I wanted to use OpenCL, I know this isn't in the newer versions with OptiX/all non-CUDA options). Try unchecking CPU hoping to force blender to actually use the GPU and have tax manager up to see if gpu is even being used\n5. blender crashes without rendering, no sign of gpu being used on task manager but CPU usage spikes to 100%\n\n**What I've tried so far that might be helpful**\n\n- tried clean reinstalling different versions of blender, both newer/experimental and older/more stable builds\n- made sure I reset BIOS in case this is a new component/migration error\n- made sure the settings for blender in NVIDIA control panel were all compatible or high performance \n- made sure NVIDIA drivers are all studio version and up to date\n- made sure blender cache folder didn't have any kernel errors\n- installed any updates to windows, this did make the gpu visible in OptiX but unfortuantely the same issue persists even with OptiX on any version where blender just won't use it and uses only cpu (despite being unchecked)\n- double checking how much memory I have on my new gpu vs the old one - yup it does\n- benchmarked my gpu using port royal and making sure I could render a project in Premiere. GPU did fine on the benchmark test and was able to render a 20min video fine. Only blender seems to be the problem\n- noticed today in stackexchange there are a lot more reports with others having the same issue, even with equivalent AMD gpus, and all comments said this seems to be a bug\n\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", "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", "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", "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)" ]

[ "Crash when rendering on CPU with OptiX denoising enabled.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.90.1\nWorked: 2.83\nBlender crash when rendering on CPU with OptiX denoising enabled.\n\n- Start Blender\n- Go to Preferences\n- Go to General Tab, Enable CUDA as \"Cycles Compute Device\", tick boxes for \"GeForce GTX 970 (Display)\" and \"Intel Core i5-6700 CPU @ 3.40Ghz\"\n- Save Preferences\n- Go to Properties Panel, Render Tab, select Render Engine \"Cycles\", Denoising render select OptiX\n- Select Device \"CPU Compute\" (Feature Set remains on \"Supported\")\n- Hit F12\n- Render Window opens for 0.5 seconds, then Blender closes completely\n\n[cube.blend](cube.blend)\n\n", "Blender 2.90.1 crashing when OptiX viewport denoising is enabled\nOperating system: Win 10 Pro Version\t10.0.19041 Build 19041\nGraphics card: NVIDIA GeForce GTX 1070\nCPU: AMD Ryzen 5 2600\nRAM: 16 GB\n\nBroken: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: 3e85bb34d0d7, type: Release\nWorked: unknown\n\nWhen I choose Cycles, GPU Compute and the Viewport OptiX Denoiser is activated it crashes when i switch viewport to render. Blender window just abruptly closed. No error window from windows.\n\n1. Set render engine to \"Cycles\"\n2. Set device to \"GPU Compute\"\n3. Set Viewport Denoiser to Automatic\" or \"OptiX\"\n4. Set Viewport Shading to \"Rendered\"\n\n\n\n[room.crash.txt](room.crash.txt)\n[system-info.txt](system-info.txt)", "Viewport rendering with cycles, CPU device, and viewport denoising crashes blender.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.90.1\n\nWhen rendering with cycles with CPU device selected, any kind of viewport denoising Auto/OptiX, etc. crashes blender.\n\n1.Create a new blender file with default cube.\n2. Select cycles as renderer, with default device as CPU selected.\n3. Enable viewport denoising, with any denoising option (Auto/OptiX, etc.) selected.\n4. Click on display render preview for viewport rendering. Blender starts to render, and crashes within seconds.\n\n** Sample blend file attached.\n\n", "Blender 2.90.1 Optix Crash if CPU Device Enabled.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.90.1\nWorked: 2.90\n\nUsing Optix will crash Blender if device is set to CPU.\n\nOpen Blender, Enable Optix, Set to Cycles mode, set device has CPU will crash.\n\n2.90\n\n\n2.90.1\n[sA2Fbga1zW.mp4](sA2Fbga1zW.mp4)", "Blender 2.90.1 OptiX viewport crashs when denoising is enabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\nCPU: Intel i7-7700\nRAM: 16GB DDR4\n\nBroken: version: 2.90.1\nWorked: I didn't try on other versions\nWen I choose cycles GPU and denoising Optix on the viewport it crashes\n\n1.Select cycles GPU render \n2.Select Optix viewport render or automatic\n3.Crash\n\n", "crash while rendering\nPLEASE REPLY AS SOON AS POSSIBLE AND PLEASE HELP ME RESOLVE MY ERROR\n\nOperating system: Windows 10 home\nGraphics card: Nvidia GeForce RTX 2060, Version: 3.20.5.70, Driver Version: 460.89\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen): 2.90.1\nWorked: (newest version of Blender that worked as expected)Did not try any other\n\nWhen i finished my modeling then switched to render mode to better work with the materials but as i went on with my materials' assigning blender crashed without any error message. But then i tried to resume my work again but happened the same. Then tried to hit render image without even finishing with my materials IT CRASHED AGAIN :(\nthis is the file creating errors\n[lecture3.blend](lecture3.blend)\n\nHere are the files i got after running debug.cmd tool\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[lecture3.crash.txt](lecture3.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Switched to render mode to better work with materials \n2. While working on materials blender crashed without any error message\n3. If not crashed while being in render mode then crashes as I hit the render image mode\n", "Enabling Optix denoiser crashes Blender\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.90.1\nI'm not using any addon, this a fresh Blender Install with no customization whatsoever except for one keyboard remap because \"~\" is not easily accessible on a french keyboard.\n\nWorked: N/A (2.90.1 is the 1st version of Blender where I tried the feature)\n\nWhen I enable Optix denoiser, Blender crashes when rendering a simple scene (Cycles renderer using GPU compute)\nThis happens even with a default scene and (only a cube).\nNote : Blender also crashes instantly when enabling Optix for viewport.\n\n- Enable Optix denoiser for rendering\n- Press F12 to do a render", "Crash when turning on Viewport denoising\nOperating system: Kubuntu\nGraphics card: Nvidia gtx 1070\n\nBroken:20.90.1\n\nWhen trying to turn on viewport denoising in cycles Blender crashes.\nBased on the default startup or an attached .blend file (as simple as possible).\nOpening or creating a scene.\nswitched render engine to cycles, gpu\nturned on deonising-viewport", "crashes in viewport rendering\nOperating system:Windows 10\nGraphics card: GTX 1080ti\n\n**Blender Version** 2.90.1\n\n\nBlender crashes when trying to render in viewport\n\nif the render device is set to CPU and one tries to render in viewport using Cycles with denoising enabled, blender crashes, a warning would be nice to have to troubleshoot the problem without too much hassle.\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "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", "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", "Mantaflow: Normal Inflow documentation discrepancy with real behaviour\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.2 26.20.15019.19000\n\nBroken: version: 2.91.0 Alpha\n\nAccording to the official [documentation ](flow.html#bpy-types-fluidflowsettings-velocity-normal), the Normal option \"controls how much velocity fluid is given along a face Normal.\" but it's clearly emitting from the vertex normal.\n[0001-0010.mp4](0001-0010.mp4)\n\nDefault cube, create a mantaflow smoke simulation. Try to add to the cub the inflow velocity and add normal to a certain value. The smoke is emitted from the vertex.\n[Bug.blend](Bug.blend)\n\n", "Bevel modifier disconnects vertices in the UV map\n{[F8713789](2KmuzHs.png)}Operating system: Windows 10 x64\nGraphics card: GTX 970\n\nBroken: 2.83.1, 47b6c332587ca45eddc98e75b3f563e2f17a0d47, probably all 2.8+ versions\n[SM_UVTest.blend](SM_UVTest.blend)\n\nWhen using an angle or weight limit on the Bevel modifier, vertices connecting beveled and unbeveled edges are split in the UV map, producing distorsions.\n\nAdded a blend file. To reproduce the issue, apply the Bevel modifier, and select all faces to see the problematic vertex in the UV editor. \n\nSome context is here : 1241831", " 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. %%%", "Normal map bug in Blender 2.9 / 3.0\nOperating system: Windows 10\nGraphics card: NVIDIA Geforce GTX 1050 Ti\n\nBroken: Blender 2.93 / 3.0 (stable version)\nWorked: Blender 2.83 (stable version)\n\nWhen applied a precedural texture (noise, Voronoi etc.) as a normal map in Node editor, the boundaries of the polygons stand out and it will look like a block. \nThere was no such problem in 2.83.\n\nCreate a mesh. Add a procedural texture on the Shading tab and apply it as a normal map.\n[#94139.blend](T94139.blend)\n\n\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", "Wireframe overlay opacity does not work correctly with viewer node\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.3.1.230305\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nAlso confirmed in 3.4 (which introduced the Viewer Node).\n\nWireframe overlay opacity does not work correctly if Geometry Nodes viewer node is activated and it's showing attribute.\n\nIt looks as if there's extra wireframe overlay under the usual overlay. Remaining wireframe does not respect smooth wires option from the preferences.\n\n- From the startup file, add Geometry Nodes to the cube\n- From Geometry Nodes editor, add a node that outputs attribute (Random Value node for example)\n- Connect Group Input and the attribute node to Viewer node\n- From viewport overlay option, enable wireframe. Try opacity slider\n\nVideo:\n<video src=\"attachment\" controls></video>\n\nFile for quick test:\n[ViewerNodeWireframe.blend](attachment)\n\n", "Mirror modifier produces odd normals along the seam for Custom Normals.\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.1.2\n\nDespite the normals of the seam being pre-aligned in mirror plane, so that they shouldn't change, the resulting normals after mirror seam merge aren't the average of the input, but produce some odd angles.\n\n[normals.blend](normals.blend)\nTurn Mirror modifier or it's Merge on/off -> the seam is clearly visible. Resulting normals don't point in the direction of the original vertex pairs.\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 ", "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).", "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", "Subdivide smooth is not symmetric\nWindows 8\nGeforce GTX 665 M\n\nBroken: Blender 2.96.0 r60995\n\n\nOn a 3 vertex line with the center vertex with greater y like that :\n\n\nIf I use subdividee smooth the result is not symmetric, I haven't set any random property.\n \n\n1./ Use subdivide smooth on the attached blend file, I have put the result that I get and the original\n[subdivide_smooth_bug.blend](subdivide_smooth_bug.blend)", "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.", "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)" ]

[ "Loop normals display not working if have custom split normals\nMacOS 10.14. Intel HD Graphics 530 1536 MB\n\nBroken: 2.8 hash 642fe9e0f2a95 Nov 4\n\nIf one sets up custom normals on a mesh and then modifies them, and enables loop normals in the overlay options, then the displayed normals stay at whatever the loop normals would be just for the face that the loop is for.\n\nThis blend\n[cubecustomnorm.blend](cubecustomnorm.blend)\nwas made by setting autosmooth on the cube, making the top edges sharp, setting the object to smooth shading, then using alt-L to enter normal editing mode, then using m (point at mouse) and moving the mouse a bit, and then left clicking. The matcap shows that normals are affected when doing this.\n\nThe commit 478899dee771 appears to have added loop normal display support so I'll assign to fclem but maybe the problem is due to a number of TODOs in draw_cache_impl_mesh.c about \"real loop normals\"." ]

[ "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", "Auto Render doesnt work with scene animations\n{[F8575831](autorender.gif)}Operating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0 Beta\n\nIt should render when the scene animation updates. In general auto render also seems a bit unreliable. eg. Sometimes I turn it off and it keeps rendering, and it doesn't render even if some changes are made to the scene. Anyway in this case it doesn't update when there're scene animations.\n\nFrom startup:\n1. Set \"Use nodes\" in compositor\n2. Turn on \"Auto render\"\n3. Animate default cube (I used rotate here)\n4. Scrub timeline\nIt doesn't auto render with new changes.\n\nWith attached blend:\n- Scrub timeline\n\n[autorender_animation.blend](autorender_animation.blend)\n\n\n", "Blender crashes on startup if a large USD file is attached to the scene\nOperating system: Windows 10, Windows 11\nGraphics card: GeForce RTX 1660 (Win 10), GeForce RTX 3060 (Win 11)\n\nBroken: 3.3.1; 3.3.4; 3.4.1; 3.5 beta\nWorked: not found\n\nThere are several Blender files created at different times. The files are scenes into which a file of the usd format is connected through the \"MeshSequenceCache\" modifier. If the usd file size exceeds a certain size, then with a high degree of probability, almost always, Blender will crash on startup.\nAt the moment, this situation occurs in the scene, to which the usd file is connected, about 1 GB in size.\nThe following method is used as a temporary solution. First, a file is launched that is either smaller or does not have a usd file attached. Then from the running program through the file-open the desired file is launched\n\nAttach a ~1 GB USB file to the scene using a modifier \"MeshSequenceCache\"\n\n", "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", "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n", "Texturing with anchored type stroke\nOperating system: Linux-5.4.0-47-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.51.06\n\nBroken: version: 2.91.0 Alpha\n\nTexture paint with stroke set to anchored while using texture significantly slows down blender up to non responsive state and crash while paint texture is larger than 2k.\n\n[Texture pain stroke ty[e anchored.blend](Texture_pain_stroke_ty_e_anchored.blend)\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", "Geometry Nodes related memory leak and exception access violation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: \n\nBlender freezes, memory usage spikes and eventually you get exception access violation crash.\n\nOpen attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.\n\n[gnodes bug1.blend](attachment)\n\nTo stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the \"fir_twig\" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.\n\n", "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 full crash during smoke+noise baking \"EXCEPTION_ACCESS_VIOLATION\"\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\nCPU: Ryzen 5900X\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nEvery single time I try to bake a high res particle system, in this case, fire at 256 + default noise settings, it never gets to complete the render and the blender crashes completely (including the console running in the background) at around frame 60 / 150.\nPausing and resuming baking sometimes works but most of the time it instantly crashes on the resume.\n\nEdit:\nI currently have 32 GB RAM and they are not really under much use during the bake.\nI tried with an RTX 3070 and Ryzen 5800x and the same issue.\n\nCrash file:\n\n\n```lines=30\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF76E01AD1A\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x000001C8281373F8\n\n\nStack trace:\nblender.exe :0x00007FF76E01A850 adaptive_domain_adjust\nblender.exe :0x00007FF76E021580 update_flowsfluids\nblender.exe :0x00007FF76E01F380 manta_step\nblender.exe :0x00007FF76E018CD0 BKE_fluid_modifier_processDomain\nblender.exe :0x00007FF76E018530 BKE_fluid_modifier_do\nblender.exe :0x00007FF76E2CC220 modifyMesh\nblender.exe :0x00007FF76E0C4DF0 mesh_calc_modifiers\nblender.exe :0x00007FF76E0C4AF0 mesh_build_data\nblender.exe :0x00007FF76E0C7170 makeDerivedMesh\nblender.exe :0x00007FF76E0A65F0 BKE_object_handle_data_update\nblender.exe :0x00007FF76E0A6320 BKE_object_eval_uber_data\nblender.exe :0x00007FF771D6AFA0 std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph * __ptr64,Main * __p\nblender.exe :0x00007FF771D69380 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF771D69330 blender::deg::`anonymous namespace'::deg_task_run_func\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF771DEE500 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFDEAAFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThreads:\nThread : 00002380\nntdll.dll :0x00007FFDEFFED280 NtDelayExecution\nKERNELBASE.dll :0x00007FFDEDB18FE0 SleepEx\nblender.exe :0x00007FF76E122380 wm_window_process_events\nblender.exe :0x00007FF76E1184D0 WM_main\nblender.exe :0x00007FF76DE09C70 main\nblender.exe :0x00007FF772313468 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000024a0\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000549c\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006094\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003a78\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000722c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000058fc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004090\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005f20\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000029a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000047b8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005718\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ba0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002ae4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006820\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001738\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c44\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004984\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c48\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000389c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002d68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002f90\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00007248\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005010\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002668\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000571c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000017f0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000060a4\nntdll.dll :0x00007FFDEFFF05F0 ZwWaitForAlertByThreadId\nntdll.dll :0x00007FFDEFFB3EF0 RtlSleepConditionVariableSRW\nKERNELBASE.dll :0x00007FFDEDB3C8A0 SleepConditionVariableSRW\nMSVCP140.dll :0x00007FFDD2CEBA70 _crtSetThreadpoolWait\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c64\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001d08\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ea4\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003cb8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000dd8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071bc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nnvoglv64.dll :0x00007FFD2046D50D Symbols not available\n\n\nThread : 000058f8\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFDEDB1C460 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20B35890 vk_icdNegotiateLoaderICDInterfaceVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000037dc\nwin32u.dll :0x00007FFDEDDDA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFDEF8A06F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002bcc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000031b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001778\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c94\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003e70\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000059b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000070a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003fd4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005b68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005508\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002c88\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000587c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000065ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000055ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006998\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001c30\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004bd0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000ee0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000049c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000041a8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000721c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000077f0\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\nblender.exe :0x00007FF76E319F80 tbb::internal::task_group_base::wait\nblender.exe :0x00007FF771D68EC0 blender::deg::deg_evaluate_on_refresh\nblender.exe :0x00007FF76DF8E3C0 BKE_scene_graph_update_for_newframe\nblender.exe :0x00007FF76E7B6A90 fluid_bake_startjob\nblender.exe :0x00007FF76E13D7D0 do_job_thread\nblender.exe :0x00007FF77234F320 _ptw32_threadStart\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF76DCE0000 2.9.2.0 blender.exe C:\\Program Files (x86)\\Steam\\steamapps\\common\\Blender\\blender.pdb \n0x00007FFDEFF50000 10.0.19041.844 ntdll.dll \n0x00007FFDEE790000 10.0.19041.804 KERNEL32.DLL \n0x00007FFDEDAD0000 10.0.19041.906 KERNELBASE.dll \n0x00007FFDEF880000 10.0.19041.906 USER32.dll \n0x00007FFDEDDD0000 10.0.19041.906 win32u.dll \n0x00007FFDEF500000 10.0.19041.746 GDI32.dll \n0x00007FFDED770000 10.0.19041.746 gdi32full.dll \n0x00007FFDED880000 10.0.19041.789 msvcp_win.dll \n0x00007FFDEAAF0000 2019.9.0.0 tbb.dll \n0x00007FFDEDE00000 10.0.19041.789 ucrtbase.dll \n0x00007FFDEEDB0000 10.0.19041.906 SHELL32.dll \n0x00007FFDED920000 10.0.19041.546 CFGMGR32.dll \n0x00007FFDEEA40000 10.0.19041.546 WS2_32.dll \n0x00007FFDEE5E0000 10.0.19041.746 RPCRT4.dll \n0x00007FFDCFCF0000 7.0.0.0 openvdb.dll \n0x00007FFDCF740000 10.0.19041.844 OPENGL32.dll \n0x00007FFDEEC60000 10.0.19041.610 ADVAPI32.dll \n0x00007FFDEED10000 7.0.19041.546 msvcrt.dll \n0x00007FFDEEAB0000 10.0.19041.906 sechost.dll \n0x00007FFDEDFF0000 10.0.19041.906 combase.dll \n0x00007FFDEE850000 10.0.19041.746 ole32.dll \n0x00007FFDEEA30000 10.0.19041.546 PSAPI.DLL \n0x00007FFDEEB50000 10.0.19041.746 SHLWAPI.dll \n0x00007FFDCF870000 3.7.7150.1013 python37.dll \n0x00007FFDEDFB0000 10.0.19041.546 IMM32.dll \n0x00007FFD22410000 58.54.100.0 avcodec-58.dll \n0x00007FFDCD5C0000 58.29.100.0 avformat-58.dll \n0x00007FFDEAB40000 58.8.100.0 avdevice-58.dll \n0x00007FFDEE510000 10.0.19041.804 OLEAUT32.dll \n0x00007FFDD40F0000 5.5.100.0 swscale-5.dll \n0x00007FFDCF610000 56.31.100.0 avutil-56.dll \n0x00007FFDEDDA0000 10.0.19041.662 bcrypt.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFDC8FD0000 1.20.1.0 OpenAL32.dll \n0x00007FFDCE1D0000 2.0.12.0 SDL2.dll \n0x00007FFDEAAE0000 2019.9.0.0 tbbmalloc_proxy.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFDEFAA0000 10.0.19041.844 SETUPAPI.dll \n0x00007FFDD2CB0000 14.26.28720.3 MSVCP140.dll \n0x00007FFDEAAC0000 14.26.28720.3 VCRUNTIME140.dll \n0x00007FFDEAAB0000 14.26.28720.3 VCRUNTIME140_1.dll \n0x00007FFDE1F70000 6.10.19041.844 COMCTL32.dll \n0x00007FFDE7F50000 10.0.19041.1 AVIFIL32.dll \n0x00007FFDE6B50000 10.0.19041.546 VERSION.dll \n0x00007FFDD8550000 10.0.19041.844 GLU32.dll \n0x00007FFDEBD30000 10.0.19041.867 dbghelp.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFDD30A0000 3.5.100.0 swresample-3.dll \n0x00007FFDCDB10000 10.0.19041.546 Secur32.dll \n0x00007FFDD82B0000 10.0.19041.1 AVICAP32.dll \n0x00007FFDE28A0000 10.0.19041.546 WINMM.dll \n0x00007FFDD2C70000 2019.9.0.0 tbbmalloc.dll \n0x00007FFD5AD10000 10.0.19041.1 MSACM32.dll \n0x00007FFDD3070000 10.0.19041.1 MSVFW32.dll \n0x00007FFDDECB0000 10.0.19041.1 winmmbase.dll \n0x00007FFDED580000 10.0.19041.906 SSPICLI.DLL \n0x00007FFDEE980000 10.0.19041.746 shcore.dll \n0x00007FFDEBF80000 10.0.19041.546 kernel.appcore.dll \n0x00007FFDEB590000 10.0.19041.906 windows.storage.dll \n0x00007FFDED100000 10.0.19041.662 Wldp.dll \n0x00007FFDEADF0000 10.0.19041.746 uxtheme.dll \n0x00007FFDED6F0000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFDED5D0000 10.0.19041.844 profapi.dll \n0x00007FFDEEBB0000 2001.12.10941.16384 clbcatq.dll \n0x00007FFDE6250000 10.0.19041.789 MMDevApi.dll \n0x00007FFDED440000 10.0.19041.546 DEVOBJ.dll \n0x00007FFDE6400000 10.0.19041.906 AUDIOSES.DLL \n0x00007FFDECC30000 10.0.19041.546 powrprof.dll \n0x00007FFDECAF0000 UMPDC.dll \n0x00007FFDEAF10000 10.0.19041.546 resourcepolicyclient.dll \n0x00007FFDEF6D0000 10.0.19041.906 MSCTF.dll \n0x00007FFDC2F40000 10.0.19041.746 dataexchange.dll \n0x00007FFDE8030000 10.0.19041.746 d3d11.dll \n0x00007FFDE8EB0000 10.0.19041.906 dcomp.dll \n0x00007FFDEBFD0000 10.0.19041.746 dxgi.dll \n0x00007FFDE6B60000 10.0.19041.746 twinapi.appcore.dll \n0x00007FFDE7A20000 10.0.19041.906 AppXDeploymentClient.dll \n0x00007FFD1FA70000 27.21.14.6192 nvoglv64.dll \n0x00007FFDEA2D0000 10.0.19041.546 WTSAPI32.dll \n0x00007FFDED280000 10.0.19041.546 msasn1.dll \n0x00007FFDE6AA0000 10.0.19041.906 cryptnet.dll \n0x00007FFDED970000 10.0.19041.844 CRYPT32.dll \n0x00007FFDED040000 10.0.19041.546 cryptbase.dll \n0x00007FFDED690000 10.0.19041.804 WINTRUST.dll \n0x00007FFDEC4F0000 10.0.19041.546 ntmarta.dll \n0x00007FFDE5470000 10.0.19041.546 dxcore.dll \n0x00007FFDEB000000 10.0.19041.746 dwmapi.dll \n0x00007FFDEC490000 10.0.19041.546 WINSTA.dll \n0x00007FFDCB3B0000 10.0.19041.906 textinputframework.dll \n0x00007FFDE9960000 10.0.19041.746 CoreMessaging.dll \n0x00007FFDE9420000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFDE9CA0000 10.0.19041.906 wintypes.dll \n0x00007FFDC2C70000 10.0.19041.844 explorerframe.dll \n0x00007FFDEA590000 7.0.19041.867 propsys.dll \n0x00007FFDED050000 10.0.19041.546 CRYPTSP.dll \n0x00007FFDEC7A0000 10.0.19041.546 rsaenh.dll \n0x00007FFDE53A0000 3.7.7150.1013 python3.dll \n0x00007FFDD40D0000 3.7.7150.1013 _bz2.pyd \n0x00007FFDD04E0000 3.7.7150.1013 _lzma.pyd \n0x00007FFDD04C0000 3.7.7150.1013 _socket.pyd \n0x00007FFDDFD70000 3.7.7150.1013 select.pyd \n \n# Python backtrace\n\n```\nSimply bake the file attached, I can't do it and I tried with multiple brand new .blend simple mantaflow setups.\n[Cinematic Fire Simulation.blend](Cinematic_Fire_Simulation.blend)", "Re-saving 16bit PNG image with straight alpha multiple times corrupts the image\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.2.1\nWorked: ?\n\n\nRe-saving 16bit PNG image with straight alpha multiple times corrupts the image.\nAs far as I can tell it's broken only for 16/32bit images and works for 8bit\n\n[Texture.zip](Texture.zip)\n1) Open the file, paint something half-transparent (optionally)\n2) Press \"Save image\"\n3) Press \"Reload image\"\n4) Image should look different than before saving", "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\n", "Crash when sculpting with a texture, deleting the image of the texture and exiting sculpt mode\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: version: 3.4, 3.5, 3.6\nBroken: version: 3.3.3\nBroken: 3.1.0\nWorked: 3.0.1\nWorked: 2.93 LTS\n\nCaused by 9111ea78ac\n\nBlender crashes when a texture image is deleted and you exit sculpt mode.\n\nYou can test it inside the attached blend file. I basically just attached an image to a sculpting brush.\n\n1. Open the blend file below\n2. draw on the surface of the sphere\n3. delete the image inside the outliner\n4. exit sculpt mode\n\nCrash occurs because `item->image->runtime.cache_mutex` is null inside `BKE_image_pool_free`\n```\nStack trace:\nblender.exe :0x00007FF713D04C10 pthread_mutex_lock\nblender.exe :0x00007FF70E6EE880 BKE_image_pool_free\nblender.exe :0x00007FF70E6B5CF0 BKE_sculptsession_free\nblender.exe :0x00007FF70F1B67A0 ED_object_sculptmode_exit_ex\nblender.exe :0x00007FF70F1B85F0 sculpt_mode_toggle_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\nblender.exe :0x00007FF70E9528D0 wm_operator_call_internal\nblender.exe :0x00007FF70E955880 WM_operator_name_call_ptr\nblender.exe :0x00007FF70F171800 ED_object_mode_set_ex\nblender.exe :0x00007FF70F148710 object_mode_set_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\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)", "Blender 3.2 crash when extracting mesh draw cache\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.96\n\nBroken: version: 3.2.0\nWorked: 3.1\n\nBlender 3.2 constantly crash on heavy load.\n\nI have loaded my scene that has a lot of particles. tried to playback the timeline. after maximum 3 frames, Blender just closes without any error messages.\n[HourglassBuildUp-JUNE30.blend](HourglassBuildUp-JUNE30.blend)\n\n" ]

[ "Hard to reproduce crash while rendering animation\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.90.0 Alpha current master, 2.83.0\nWorked: unknown\n\nBoth `2.83` and `2.90` sometimes crash at random frame during animation render. The bug is hard to catch reliably, but it seems to happen more often wtih some render settings. In particular I couldn't reproduce it without \"presistent images\" checked. Also it seems to be sensitive to frame count, render sample count, output resolution and tile size. Tested only with Cycles. Happens both with GPU and CPU render, with CPU much less frequently. Tested only on one Windows machine. The crash only happens on release builds (`2.83` - official installer, `2.90` - self built with more or less standard settings). The issue is particularly hard to catch as it dissappears as soon as any code is altered or a breakpoint/logpoint is placed in the suspicious code. Changing build optimizations also breaks reproducibility.\n\nThe crash happens at `external_engine.h:560`:\n```\n GHashIterator pa_iter;\n GHASH_ITER (pa_iter, re->parts) {\n RenderPart *pa = BLI_ghashIterator_getValue(&pa_iter); *HERE* pa_iter.curEntry is 0xFFFFFFFFFFFFFFEF\n```\n\nStack trace:\n```\nblender.exe!RE_engine_get_current_tiles(Render * re, int * r_total_tiles, bool * r_needs_free) Line 560 (.\\blender\\source\\blender\\render\\intern\\source\\external_engine.c:560)\nblender.exe!draw_render_info(const bContext * C, Scene * scene, Image * ima, ARegion * region, float zoomx, float zoomy) Line 104 (.\\blender\\source\\blender\\editors\\space_image\\image_draw.c:104)\nblender.exe!draw_image_main(const bContext * C, ARegion * region) Line 1037 (.\\blender\\source\\blender\\editors\\space_image\\image_draw.c:1037)\nblender.exe!image_main_region_draw(const bContext * C, ARegion * region) Line 677 (.\\blender\\source\\blender\\editors\\space_image\\space_image.c:677)\nblender.exe!ED_region_do_draw(bContext * C, ARegion * region) Line 543 (.\\blender\\source\\blender\\editors\\screen\\area.c:543)\nblender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 689 (.\\blender\\source\\blender\\windowmanager\\intern\\wm_draw.c:689)\nblender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 812 (.\\blender\\source\\blender\\windowmanager\\intern\\wm_draw.c:812)\nblender.exe!wm_draw_update(bContext * C) Line 1013 (.\\blender\\source\\blender\\windowmanager\\intern\\wm_draw.c:1013)\nblender.exe!WM_main(bContext * C) Line 482 (.\\blender\\source\\blender\\windowmanager\\intern\\wm.c:482)\nblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 530 (.\\blender\\source\\creator\\creator.c:530)\n[Inline Frame] blender.exe!invoke_main() Line 78 (d:\\agent\\_work\\2\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:78)\nblender.exe!__scrt_common_main_seh() Line 288 (d:\\agent\\_work\\2\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288)\nkernel32.dll!00007fff3eb684d4() (Unknown Source:0)\nntdll.dll!00007fff3f9ae871() (Unknown Source:0)\n```\n\n1. Open blender 2.83 or 2.90 (default blend file)\n2. Check \"presistent images\"\n3. Minimize sample count, output resolution and tile size for faster render, but make the resolution at least 4xtile_size.\n4. Render animation\n5. If id doesn't crah alter the settings from step 3 and repeat. Changing frame count may also help.\n\nOr use one of the attached files:\n[crash-fast-unreliable.blend](crash-fast-unreliable.blend)\n[crash-unsimplified-more-reliable.blend](crash-unsimplified-more-reliable.blend)\n\n[hat_2.83_debug_logs.zip](hat_2.83_debug_logs.zip)\n\n" ]

[ "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", "Can't bake to external textures (Python)\nHello, when trying to bake an object to an external texture, Blender seems to ignore the \"save_mode\" and bakes the texture to an internal buffer. I've tried two ways:\n\n```\nimport bpy\n\n# Bake selected objects\nfor obj in filter(lambda x: x.type == 'MESH', bpy.data.objects):\n\t\n\tprint('Selected: ' + obj.name)\n\t\n\t# Select current object\n\tbpy.ops.object.select_all(action='DESELECT')\n\tobj.select = True\n\tbpy.context.scene.objects.active = obj\n\t\n\t# Bake\n\tbpy.ops.object.bake(type='COMBINED', save_mode='EXTERNAL', filepath='E:\\\\baked.png', use_automatic_name=True, width=512, height=512)\n\t\n\t- Other version, doesn't work either\n\t- bpy.ops.object.bake(filepath=\"//baked.png\", save_mode='EXTERNAL')\n```\n\nAnd also setting the parameters in a different way:\n```\nbpy.context.scene.render.bake.filepath = 'E:\\\\baked.png'\nbpy.context.scene.render.bake.save_mode = 'EXTERNAL'\nbpy.context.scene.render.bake.use_split_materials = False\n```\n\nAlways, the execution of the previous code returns the following and does not create an image file:\n```\nSelected: Cube\nInfo: Baking map saved to internal image, save it externally or pack it\nSelected: Floor\nInfo: Baking map saved to internal image, save it externally or pack it\n```\n\nTried with different paths and parameters for the bake funcion, also creating image nodes and selecting / deselecting them in the node editor for the material.\n\nAlso, I found someone who had the same problem as me, and found no solution:\n676562\n\n\nFind attached a blend file: [Bake.blend](Bake.blend)\nIt's a simple cycles scene with a cube and a floor, Cycles renderer. It bakes correctly to textures (internal buffer).\n\n - Open the blend file or create your own scene\n - Run the code written above\n - Blender won't create a bake file, in the console you'll see \"Baking map saved to internal image, save it externally or pack it\"\n\n\nWindows 10, nVidia Quadro K5100M\n\nBroken: 2.79b f4dc9f9d68b, 2.77a abf6f08\n\nThank you", "\"Updating Objects Flags\" Stalling Blender\n{[F10130762](22_Nautilus_through_City_-_Cycles___Eevee.zip)}Operating system: Linux-5.8.0-53-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBroken: version: 2.92.0\nWorked: Not working down to 2.83 LTS\n\nThis file will not render the Scene named \"Cycles\" with the Cycles render engine. \n\n\n1. Open attached blend file. Note everything except camera and lights are turned off.\n\n2. Using command line, attempt to render a single frame (say 130).\n\n3. Result = Everything initialises but the render stalls on \"Updating Objects Flags\".\n\n4. Open the file in UI\n\n5. Render image renders a blank image (expected).\n\n6. Turn on Buildings and Landscape, 9 collections from the top, and Nautilus and Submarine Search Lights at the bottom. \n\n7. Render a single frame, or the cycles render layer in the compositor.\n\n8. Result = A single image may render in cycles (followed by the second scene in Eevee that composites).\n\n9. Render animation\n\n10. Result = Blender hangs on \"updating objects flags\" and it does not render, and it is not possible to cancel the render.\n\nIt may be possible to get back rendering by saving the file as a new file. But as soon as rendering an animation as attempted, \"updating objects flags\" hangs Blender either in command line or in UI mode.\n\nNotes: \n\n1. I have tried the same file on multiple machines and multiple Operating Systems with the same result.\n\n2. Quite a number of files have similar kinds of problems. Most commonly, the files will not render in UI mode. Usually though, rendering in command line works. In this case it does not.\n\n3. I have tried every permutation of trouble-shooting I can think of. I have added meshes back in one by one, re-baking ocean modifer, particles, everything. Trying recently, I had to re-bake the particles after which rendering stopped working in any configuration. The particle systems have been baked to a disk cache.\n\n4. Reconstructing from a new blend file is pointless - new blend files are fine and I do not know what is happening to bring about the bug.\n\n5. It may be necessary to re-send the file in its state when it cannot render. Please let me know if anymore information is required.", "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.", "Textfield disables input permanently if hidden while editing\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 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: <2.80\n\nIf a textbox that is currently being used is hidden, then all input gets permanently disabled, staying in typing mode of a non existing textbox. There is also a memory leak of a few bytes reported in the console when I close blender in this state.\nThis bug can lead to data loss since there is no way to recover, so it's basically like a crash.\n\n1. Make the blender window maximized.\n2. Open the right panel in the viewport and drag it open until it covers as much of the window as possible.\n3. go into text editing of the x location of the default cube\n4. use Meta+Right Arrow or some similar shortcut which resizes the window.\n5. now if the window is small enough the panel with the textbox is hidden, but the mouse is still a textcursor and all input is blocked.", "Object Info node not update if delete object from viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nIf you delete an object selected in the Object Info node, the object remains selected in the node\n\n\n\nDelete object from viewport selected in the Object Info node. Object Info node not update socket\n\n[Proximity_displaces2.blend](Proximity_displaces2.blend)\n\nNote that if you delete it from the outliner things work. The issue is when the object is deleted from the viewport.\n\n**Original file**\nThis file doesn't help because the object was already deleted from it:\n[Proximity_displaces.blend](Proximity_displaces.blend)\n\n\n\n\n", "Can't edit new driver on an overriden property on a linked object with no animation data\n## Simplified Report\n\n- The following file contains an object with no animation data.\n- Link the object to a new file and make a library override from it.\n- Add a new driver on one of its location channels.\n- Notice that driver options are grayed out and can't be edited.\n- One expects to be able to edit the driver since the object has no animation data. \n\n[libraryFileWithNoAnimationData.blend](libraryFileWithNoAnimationData.blend)\n\n## Original Report\n\n\nOperating system: Linux-5.15.60-1-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.0\nWorked: ??? I could have sworn this worked in 3.2 but it seems to have the same behavior. Same in 2.93.\n\nUsing drivers with overridden properties is not really usable. I can add a driver, but then I cannot edit it.\n\nLink a collection into a file and make a library override. Right-click on a property and choose \"Add Driver\".\nRight click on the property (which should turn purple) and then choose \"Edit Driver\" Notice that the\ndriver's controls are all blurred out! You can't edit them in the UI.\nIt gets worse!\nOpen a driver-editor window so you can watch what happens in the next step, and select the driver you\njust created- open the \"Drivers\" tab in the window. Look at the expression.\nIn the main window (not the driver window), click on the driven property and type ~~\"#1\" - when you\nprepend a hash symbol, that tells Blender to edit the expression of a driver (it's a handy way to make\nnew drivers with simple expressions. Try it at home!)~~ **edit: it looks like you don't need the hash when it is already driven.**\nNow, notice the expression change in the driver window that you aren't normally able to edit!\nI have also confirmed that you can edit some properties with the Python API that you cannot edit in\nthe user interface.\n\n**My Thoughts** (If you're interested)\nI do not know if the design for overrides is intended to support using drivers like this. It feels a little squishy\nbecause I don't know if Blender will keep the driver around when I resync the override. On the other hand, it's\nreally handy when doing animation that is easier to do programmatically, such as causing a bone to oscillate\nwith sine-waves (e.g. a plant waving with the wind). Sometimes I use a driver to bake keyframes - so I set up the\ndriver and then bake its motion to an action, and get rid of the driver. It is my opinion that driver support is\nnecessary for overrides, because it's something I expect to be able to use, as an animator. I don't know if the\nold Proxy system supported drivers, though.\nAt any rate, if it is blocked from editing in one place, it should be blocked from editing through the API, too.\n\nI apologize if this is a known issue. I don't see any similar bug reports but it appears things have been like this\nfor a while.", "Linked Text Object Data Bug\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.42\n\nBroken: version: 2.93, 3.0.0\nWorked: -\n\nText objects with linked object data behave strangely. Some letters change their shape, which may vary from instance to instance. (see uploaded image)\nMaybe i´ve got the bug is because i use the Small Caps format.\n\n\n1. Create several same text Objects (you maybe should use Small Caps format in them)\n2. Link their Object Data\n3. Try to switch several times between Object and Edit mode and you will see the bug. It occurs everytime on different letter. And every instance of the text looks often different then the others.\nI am attaching the Blend file\n[bug.blend](bug.blend)\n", "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.", "Inaccuracy in 'Info' editor\nThis bug is difficult to describe specifically, since I have no idea of *all* of the affected properties. All I noticed is that *some* are reported inaccurately (i.e. the reported rna path does not exist or does not point to the changed property).\n\nA few I found are on the View Layer tab in the Properties editor:\n`bpy.context.scene.view_layers- [x].cycles.denoising_store_passes` is reported as `bpy.context.scene.denoising_store_passes`\n`bpy.context.scene.view_layers- [x].cycles.pass_debug_render_time` is reported as `bpy.context.scene.pass_debug_render_time`\n`bpy.context.scene.view_layers- [x].cycles.use_pass_volume_direct` is reported as `bpy.context.scene.use_pass_volume_direct`\n`bpy.context.scene.view_layers- [x].cycles.use_pass_volume_indirect` is reported as `bpy.context.scene.use_pass_volume_indirect`\nPlus all of the Cryptomatte and Denoising properties.\n\nI have no idea how the Info editor receives this information, but it looks as if the message is partially hard-coded and not up to date?", "NLA is editable even when the animation data is linked\nBroken: 2.80 to current main branch (`96abaae9ac57e3833f862bc0b562d2fe7a95f702`)\nWorked: probably never\n\nThe NLA is editable, even when the animation data is linked and thus should be read-only.\n\n\n- Extract the attached ZIP\n- Open `nla-link-test.blend`\n- Move the strip in the NLA\n- Save and reload the file\n- See that the strip edit has not been saved to disk.\n\nObserved behaviour: the NLA strip can be moved.\n\nExpected behaviour: the NLA data of the linked object should be read-only. Just like the cube itself (you cannot move it).\n\n", "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", "Dither affects 'File Output' image even when \"save as render\" is disabled \nThe dither option in the Post Processing tab affects images saved through the file output node in the compositioner even when \"save as render\" is disabled, when disabled it should not touch the output image, when \"save as render\" is enabled it makes sense to dither.\n\n\nnoise in output file\n\n\n- Open attached file\n- Optionally change the Dither in {nav Output Properties > Post Processing}\n- hit render\nIt will generate an image in the directory pointed to by the node `File Output`.\nNote that Dither also affects this image.\nMaybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data.\n\n[gradient.blend](gradient.blend)", "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 |", "Motion Blur break position pass\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.79\n\nBroken: version: 3.6.0\n\nHi ! I just discover that the motion blur break de position pass.\n\n1. Choose Cycles render.\n2. Choose CPU Render.\n3. Active Motion Blur in the render properties.\n4. Enable Position pass rendering.\n5. Create a sphere then anim it.\n6. Hit render button.\n7. Constat the bug :)\n\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.", "API, Changing part of evaluated object.original resets all attributes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 780 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nChanging a part of evaluated object.original during animation resets all object attributes to those of the last visible frame before rendering of animation started.\n\n\nleomoon-textcounter.py#L353\nI enountered a problem (and possible bug) with API in this add-on. This script alters Font object text (body) on every frame. \nThis is achived by handler:\n\n\n```\n@persistent \ndef textcounter_text_update_frame(scene, depsgraph=None):\n for object_inst in depsgraph.object_instances:\n text = object_inst.object\n if text.type == 'FONT' and text.data.text_counter_props.ifAnimated:\n textcounter_update_val(text, scene.evaluated_get(depsgraph))\n```\n\nDepsgraph is used to get evaluated object for each animation frame. Simply taking object from bpy.context.scene.objects will not work either in viewport or during rendering animation (don't remember which one). To be specific, PropertyGroup text_counter_props, that is part of Font object, will not refresh during animation until it is taken from evaluated object.\n\nThen, new body (text) is assigned to the Font object:\n\n```\ntext.original.data.body = out\n```\nAt this moment all other properties of this object (like location, rotation, scale etc.) will reset to those of the last visible frame before rendering of animation started.\n\nI think it is a bug because, in my understanding, only body attribute should be changed by this code.\n\nTo reproduce:\n1. Open file\n2. Run script\n3. Start animation in viewport - all works fine (timer counts and moves right to left)\n4. Start rendering animation - timer counts but sits still\n\nEdit. I messed up file attachments. [textcouer-test.blend](textcouer-test.blend)\n", "Changing properties of an object from a frame_change_post handler blocks animation\nOperating system: Linux-4.15.0-91-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.81, 2.83 (sub 13)\nWorked: 2.80\n\nWriting to `ob.color` of all objects in the view layer breaks keyframe animation.\n\n\n[bug.blend](bug.blend)\n\n- Open Blender with `blender --factory-startup --enable-autoexec bug.blend`\n- Press {key Space} to see the animation (three spheres rising)\n- Press {key Ctrl F12} to render the animation\n- See that one sphere remains in the position it had before pressing {key Ctrl F12}, instead of being animated. This is the ball that had its `color` set in the frame change handler.\n\nBisecting showed that this was caused by commit f7fce00297.\n\nThe blend file contains the following code:\n\n```\nimport bpy\n\[email protected]\ndef _update(_, context=None):\n ob = context.view_layer.objects['GEO-drone_001']\n ob.color = (1, 1, 1, 1)\n\ndef register():\n print(\"Bug-causing code registering!\")\n bpy.app.handlers.frame_change_post.append(_update)\n\n\nif __name__ == '__main__':\n register()\n```\n\nNote that this behaviour isn't specific to the `color` property; I changed the code to set `ob.pass_index = 3` and it has the same result.\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)", "Rigidbody Physics Refactor\n**Goal**\nThe goal is to simplify the rigidbody physics code.\n\nThis ticket is being raised after discussions with @ZedDB about this issue T91369 and the related tickets regarding rigidbody physics crashes. I attempted to resolve those crashes on their own, but really struggled to find a sensible way to resolve some of the memory management issues that were occuring. @ZedDB mentioned that this was an area of the code in need of a redesign for some time, and with comments like below predicting this could be an issue, we decided it could be a good time to start tackling it.\n\n\n\n**Approach**\nI want to start with some smaller low hanging fruit, that wouldn't change any logic but will improve the readability of the code. \n\n- [ ] There is some dead code that can be removed\n- `BKE_rigidbody_calc_center_of_mass` - probably worth keeping the logic but hiding with a `#if 0`\n- `BKE_rigidbody_world_groups_relink` is only used by `BKE_scene_groups_relink` which doesn't seem to be used anywhere else.\n\n- [ ] It would make things much easier to follow by separating the simulation logic from the rididbody creation/deletion logic, into a separate `rigidbody_simulation.c` file.\n\n- [ ] There is a lot of general tidy-up that would make the code more readable and easier to understand.\n\nOnce these tasks are completed we can start thinking about any larger design issues that need to be addressed - like with the memory management of the constraints. With more readable code, and a better understanding of the logic from the refactoring process, it should be a more solvable problem.\n\n", "cloth sim pin stiffness ignored\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 3.0.0 Alpha\n\nPin stiffness is not working at all.\n\nOpen file, press play. left plane has pin stiffness animated from 1 to 0, right plane has pin stiffness set to 0 (non animated). Both act as though pin stiffness is set to 1. Right plane included to indicate this is not the same bug as cloth simulations only taking into consideration the mesh state at first frame.\n\nExpected behaviour is for the cloth to become unpinned when set to 0.\n\n[pin stiffness ignored.blend](pin_stiffness_ignored.blend)\n\n", "Library overrides does not work well with Materials.\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 Release Candidate\nWorked: No\n\nAfter saving and reloading, the object's material changes unexpectedly.\nThis bug only appears on objects that have library overrides.\n\n\n**Exact steps for others to reproduce the error**[bug check.zip](bug_check.zip)\n\n1. Download bug check.zip\n2. Open the t2.blend file. You can see that the cube contains red and green.\n3. Then select mat2a in the material list and save it as t4.blend.\n4. Reload t4.blend, and the cube is only red.\n\nMy current bypassing method:\nBefore saving, choose the same material slot as t1.blend. Only in this way can the object's material do not turn into another.\n\nt1.blend is the original data.\nt2.blend is a link of t1.blend, and then replace the data material to the object material.\nt3.blend is wrong, just like the t4.blend you get.\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.", "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", "Improve Interior Face Selection Method #2\nOperating system: Win 10 Pro\nGraphics card: nVidia GeForce GTX 1070ti\n\nBroken: tested in 2.80 stable and 2.81-dcad1eb03ccc\n\n\nIn Edit Mode Select -> Select all by Trait -> Interior Faces does not select all expected Faces.\n\n\nIn the attached blend file try to select the interior faces by trait and nothing happens. The object was created by moving a default cyclinder and UV sphere into each other and merging the vertices at the spheres equator by distance. After the merge the top face of the cylinder is selected by trait as expected while the lower faces of the sphere are not.\n\n[interior_faces_bug.blend](interior_faces_bug.blend)", "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", "Live unwrap is non responsive if mesh has no boundaries and no seams.\nSubtask of #75007 see `LiveUnwrapCube.blend` and discussion.\n\nIf a mesh has no boundaries in 3D space (e.g. cube, sphere) and also no seams, then `UV Editor > UV > Live Unwrap` will fail and the unpinned UVs will not follow the movement of the pinned UVs.\n[Pin_two_no_seam.blend](Pin_two_no_seam.blend)\n\n\n\nOTOH if a mesh **does** have a boundary or seams, after the LSCM solver has found a solution, then the single-pin and two-pin interactions (translation, scale+rotation) are both well defined and unpinned UVs will follow pinned UVs in a familiar way:\n[Pin_two_all_seam.blend](Pin_two_all_seam.blend)\n\n\n\nThere are two possible fixes here.\n\nOne possible fix is to upgrade the LSCM algorithm to handle the case where there are no boundaries or seams, either by automatically adding seams if they are missing, or (equivalently) by adding additional constraints to the Least-Squares solver directly.\n\nA second possible fix is to detect the condition, leave the UVs unchanged on return from the LSCM solver, yet still provide the same user interaction for the one-pin and two-pin cases:\n\n\nAt this point, we need design input to determine which (or both?) of these fixes to implement.\n", "Edit mode: Fill region operator wrong behavior.\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: since 2.79 till now. \nTested with 2.79b, 2.83.9, 2.92, 2.93 3ea1779365b5\n\n\nFill region operator fails with this geometry. Test my file.\n{[F9906012](9540941.png) size = full}\n[untitled.blend](untitled.blend)\n[2021-03-23_23-38-13.mp4](2021-03-23_23-38-13.mp4)\n", "blender::Set exhibits poor behavior if growth occurs after a round of removals\nI noticed `blender::Set` behaving poorly when an `add` operation requiring container growth comes after various `remove` operations. The net effect being that the container actually shrinks.\n\nI'm guessing that what I'm seeing below is not expected.\n\nThe sequence went something like the following:\n\n```\nmy_set.reserve(64);\n\n// a series of adds and removes\n\nmy_set.add(...); *start of poor behavior* Current state of the container\n* removed_slots_\t54\n* occupied_and_removed_slots_\t64\n* usable_slots_\t64\n\n*The value 11 is passed into \"realloc_and_reinsert\" indicating we need space for at least 11 items (i.e. size + 1)* The following values are calculated\n* total_slots\t32\n* usable_slots\t16\n\nshrinkage :(\n\n// At the end of \"realloc_and_reinsert\" the state of the container is\n* removed_slots_\t0\n* occupied_and_removed_slots_\t10\n* usable_slots_\t16\n\n\n\n```", "Multires: Missing updates are not communicated in the UI\nIntel Core i7, 16 Gb RAM, NVidia GeForce 2070 RTX\nWindows 10 x64\n\nBroken: 2.8x up to 6fff73e3f001 from 2020-01-23\nWorked: 2.79b\n\nCurrently it’s not possible to use Shrinkwrap (modifier and constraint) and Walk Navigation with Gravity (toggling Gravity causes you to fall through the floor, teleporting doesn't work) with object that has subdivided Multires and is in Sculpt Mode. In 2.79 Shrinkwraps are not updating during sculpting but it's still possible to see where objects are being shrinkwrapped. Not being able to see shrinkwraps becomes problematic in a very similar way as not being able to see textures while sculpting.\n\n\n1.\tOpen provided file in 2.79 and observe that Road and House objects are shrinkwrapped to the Landscape object while subdivided Multires is in Sculpt mode. You can use Walk Navigation with Gravity to walk or teleport over the surface.\n2.\tOpen provided file in 2.8, both Shrinkwraps will be disabled and you will not be able to teleport or walk across the surface in Walk Navigation mode.\n[No_Shrinkwrap_and_Walk_Gravity.blend](No_Shrinkwrap_and_Walk_Gravity.blend)", "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)", "High poly meshes perform poorly with planer decimate\nOperating system: Windows 10\nGraphics card: AMD Asus Vega RX64\n\nBroken: blender-2.81-92736a7b7592-windows64 (plus previous few builds - atleast)\nWorked: 2.8\n\nMy PC is decent, and I have had no problem decimating millions of vertices (albeit some few seconds of lag) usually. Right now, I'm trying to decimate a simple model with about 45k vertices only. The decimate modifier is working fine on default settings i.e., on 'Collapse' setting .. but as soon as I switch to 'Planer' .. Blender becomes unresponsive for several minutes at least (and also indefinitely in some cases). \n\nI noticed that in my task manager, the Blender is only using 29% of CPU.. and regarding RAM .. on one side it shows 61% usage, while the actual usage is only 289MB in the value column (see screenshot). Could this be a memory related overflow/underflow? This definitely does look like a bug to me. \n\n\n\n\n\n", "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" ]

[ "broken softbody.\nwindows 7 professional 64-bit laptop integrated graphics (dell inspiron n5010)\n\nBroken: 2.71 full\n\nthe stiffness and shapematch of softbody objects is nonexistent.\n\n\n\n\nenter game engine\ncreate softbody object uv sphere (for better detail)\ncreate collision object\npress p\nwatch the sphere land flat\n" ]

[ "Blender segfault if Bake Line Art\nOperating system: Debian Linux Stable 11\nGraphics card: Intel internal UHD Graphics 630 (driver: i915)\n\nBroken: 3.2.2 - 3.6.1 official releases\n\nBlender segfault if Bake Line Art.\n\nConsole:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault\n```\n\nFile /tmp/blender.crash.txt:\n```\n# Blender 3.2.2, Commit date: 2022-08-02 18:15, Hash bcfdb14560e7\nbpy.ops.object.delete(use_global=False, confirm=False) # Operator\nDeleted 1 object(s) # Info\nbpy.ops.object.gpencil_add(align='WORLD', location=(0, 0, 0), scale=(1, 1, 1), type='MONKEY') # Operator\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.gpencil_modifier_add(type='GP_LINEART') # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xc1619d0]\n./blender() [0x11da18d]\n/lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f97f7664d60]\n./blender(MEM_lockfree_allocN_len+0x7) [0xc16e1e7]\n./blender(MEM_lockfree_dupallocN+0x14) [0xc16e624]\n./blender(BKE_gpencil_stroke_duplicate+0x1a) [0x11f926a]\n./blender(BKE_gpencil_frame_copy_strokes+0x42) [0x11f94c2]\n./blender() [0x1207d97]\n./blender(BKE_gpencil_prepare_eval_data+0x1b7) [0x1208b07]\n./blender(BKE_object_handle_data_update+0x2fe) [0x12af9ae]\n./blender(BKE_object_eval_uber_data+0x2f) [0x12afc7f]\n./blender() [0x1913f22]\n./blender() [0x19140f2]\n./blender() [0xc16574d]\n./blender() [0x1796a35]\n./blender() [0x1796ceb]\n./blender() [0x1783d27]\n./blender() [0x1790720]\n./blender() [0x179275c]\n./blender() [0x1792959]\n/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f97f807aea7]\n/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f97f7727a2f]\n\n# Python backtrace\n```\n\n1. Open Blender\n2. Click to default box and delete it (press del)\n3. Press Shift+A\n4. Select \"Grease Pencil\" - \"Monkey\"\n5. At right area select \"Modifier Properties\"\n6. Click \"Add Modifier\"\n7. Select \"Line Art\"\n8. At bottom of this area click \"Bake\" - \"Bake Line Art\"\n9. Segfault here\n\n", "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", "WARN (bpy.rna) current value '3' matches no enum in 'SpaceProperties', '(null)', 'context'\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 512.96\n\nBroken: version: 3.3.0 Alpha\n\n```\nWARN (bpy.rna): C:\\Users\\blender\\git\\blender-vdev\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1339 pyrna_enum_to_py: current value '3' matches no enum in 'SpaceProperties', '(null)', 'context'\n```\nwhen first time run the script below, it will get error`item.attr = val: enum \"MATERIAL\" not found in ()`\nbut when the property panel is exist (run the second time), it works. \nIt is an updata bug for the panel? How can I solve this problem or skip it?\n\n\n```\nimport bpy\n\narea_props = bpy.context.window_manager.windows[-1].screen.areas[-1]\narea_props.type = 'PROPERTIES'\nprint(area_props.spaces[0].context)\narea_props.spaces[0].context = \"MATERIAL\"\n```", "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", "The tools panel suddenly disappears in engraving mode.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro K620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\n\nBroken: version: 2.93.0\n\n\n\n\nIn the engraving mode, use the blank key to call the tools panel may suddenly disappear.\n\nMy native language text↓↓↓↓\n\n在雕刻模式，使用空白鍵呼叫　tools 面板會有突然消失的可能。\n\n\n\n\n\n1. Set KeyMap>Spacebar Action>Tools\n2. Select any object and enter sculpt mode.\n3. Press the blank key to call the tools panel. At this time, the panel will suddenly disappear. (Error generation)\n4. Move the mouse arbitrarily\n5. Press the space button again to call the tools panel. At this time, the panel will suddenly disappear. (Error occurs again)\n\nOther additional tests:\n\n1. The panel disappears (when an error occurs), do not move the mouse, press the blank key again, and it will appear normally\n\n2. When it appears normally, as long as you move the mouse and press the blank key, an error will occur, but there is one exception, which is simply moving the mouse horizontally so that the panel appears in the second position, the selected brush and slide The overlapping position of the mouse is exactly the same as the last time, the error will not occur (image)\n\n3. In the object mode, everything is normal, I think it should be operated like the object mode.\n\nMy native language text↓↓↓↓\n\n1.設定 KeyMap >Spacebar Action>Tools\n2.選擇任意物體，進入sculpt模式。\n3.按空白鍵呼叫tools面板。這時候面板會突然消失。(錯誤產生)\n4.任意移動滑鼠\n5.再次按空白鍵呼叫tools面板。這時候面板會突然消失。(再次錯誤產生)\n\n其他額外測試 :\n\n1.面板消失(錯誤產生時)，滑鼠不要動，再按一次空白鍵，就可以正常出現\n\n2.當正常出現後，只要有移動滑鼠，再按空白鍵就會發生錯誤，但有一個時候例外，就是單純水平移動滑鼠，讓第二個位置出現面板時，選取的筆刷與滑鼠重疊的位置和上一次一模一樣，錯誤就不會發生 (圖片)\n\n3.在物體模式，一切正常，我認為應該操作起來要像物體模式這樣。\n\n\n\n", "Keyframing Corner pinning in compositing is inconsistent\nOperating system: windows 10\nGraphics card: Nvidia geforce GTX 1050 Ti\n\nBroken: 3.3.0\n\n\nWhen using the background X symbols to drag and drop corners with corner pinning, only the topmost value of each vector is keyframed\nExample image(wanted to edit a meme):\n\n\n- Open attached file\n- Single Render to Update Compositor\n- Move the Corner Pins\nor\n- Arrange nodes as seen.\n```\n{F13601679}\n```\n- Select the corner pin node\n- Try to keyframe the location of the second image/video, using auto keyframes and the background viewport manipulators.\nOnly the topmost (X) value gets keyframed\n\n[Corner pin.blend](Corner_pin.blend)\n", "Memory Leak: Opening some file in lite debug build\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 527.56\n\nBroken: version: 3.6.0 Alpha\n\nOpening some file (not all) can cause memory leak.\nThis happens only in my lite debug build.\n\n> Error: Not freed memory blocks: 1, total unfreed memory 0.000092 MB\n\n1. Open blender\n2. File -> Open\n3. In file browser:\n a. Filter Settings: Blend file only.\n b. Select example file.\n c. Open this.\n4. Close blender.\n\n", "GPUOffScreen example give strange \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 512.96\n\nBroken: version: 3.1.2\n\n\n\n1. copy the code from here gpu.html#rendering-the-3d-view-into-a-texture\n2. run it \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)", "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", "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)", "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", "Reference/background images hide additional information in the Properties Editor\nOperating system: Linux-6.4.13-200.fc38.x86_64-x86_64-with-glibc2.37 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 16.0.6, DRM 3.52, 6.4.13-200.fc38.x86_64) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 4.0.0 Alpha\n\nReference/background images hide additional information in the Properties Editor\n\n- Add > Image > Reference / Background\n- observe the Image panel in the Properties Editor\n\n- compare with the Image panel in the Image Editor\n\n\n", "The version over 3.5 (3.6 and 3.6.2) crashes for me after using control of view.\nOperating system: Linux-6.2.0-32-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics 650 (Kaby Lake GT3e) (KBL GT3) Intel 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1\n\nBroken: 3.6 and 3.6.2\nWorked: version: 3.5.0\n\n\nI have quite simple scene: 1 table, 1 chair. I change selection from chair to table f.x., then deselection or I make zoom out, the screen freezes, Blender proposes me to closing because not responding\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```" ]

[ "Additional \"Falloff\" tab in Brushes UI\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 3.1.0 Alpha\n\nSince recently there has been an additional Falloff setting tab in the sidebar & properties editor outside of the brush settings tab.\nThis is the case in all painting modes and sculpt mode. The setting doesn't even correlate to the actively used brush.\n\n\n\n", "Spare falloff panel\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.0.0\nWorked: 2.93.7 and other modes in 3.0+\nCaused by f8a0e102cf\n\nthis how it looks\n{[F12762629](40171841.png) size=full}\n\n[2021-12-19_07-45-52.mp4](2021-12-19_07-45-52.mp4)\n\n" ]

[ "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", "GPencil: envelope, Multiplestrokes, Array modifiers missing with the orders of strokes.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Beta\n\ni can't use build modifier with array, envelope,multiplestrokes efficiently because the generated stokes and originals don't get well indexing( orders) to be used by build modifier. i observed the following: \n** Multiplestrokes** modifier be the last in order then the generated lines. \n**Array** modifier and **Envelope** modifier don't have any predictable indexing (order) of strokes and all the time makes the original strokes the last in order. see the video\n\n", "Hitting 'Escape' while editing a shortcut enters that key on Windows, while on linux it cancels edition\nWindows 7 64bits, nvidia gt540m CUDA 2GB, Intel i7 2GHz, 8GB ram\n\nBroken: 2.75 c6b042b\n\n\nWhen i do a search of a shortcut, and then if i want to assign a new value and then cancel, the tab disappear.\n\nBlender User Preferences > Input > Search by key-binding \"Ctrl Tab\" > Show key map and property of any tab > Clic on \"type of event\" to change the value > Press Esc to cancel > the tab disappear.\n", "UI: Drag Tool option is misaligned and should not use colon\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\nDrag Tool option is misaligned and should not use colon:\n{[F11087908](image.png), size=full}\n\nBtw. `Gizmos:` shouldn't use colon either\n\n", "Blender's search in data-blocks is case-sansitive in cyrilic letters\nUbuntu 14.04\n\nBroken: 2.73\n\nSupporting of Utf-8 characters chars in names of objects and data-blocks are not completely done. While searching, uppercase and lowercase letters in the Cyrillic alphabet are considered as different letters. \n\nHere is the test file [casetest.blend](casetest.blend)\n\n\n\n\n", "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 ", "Problem with Panel class in layout and with translation texts\n**Targeting Project**\nGUI Development\n\nOperating system: \nLinux, Kernel: 4.15.0-20-generic x86_64 bits: 64 compiler: gcc v: 7.3.0 Desktop: Cinnamon 4.0.8 \nDistro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic \n\nGraphics card:\nDevice-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel \nDevice-2: NVIDIA GK208M [GeForce GT 740M] vendor: Hewlett-Packard driver: nouveau v: kernel bus ID: 01:00.0 \nDisplay: x11 server: X.Org 1.19.6 driver: modesetting,nouveau unloaded: fbdev,vesa \nresolution: 1920x1080~60Hz, 1920x1080~60Hz \nOpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.0.5 direct render: Yes \n\nBlender 2.80 (sub 75)\n\tbuild date: 2019-07-29\n\tbuild time: 17:17:04\n\tbuild commit date: 2019-07-29\n\tbuild commit time: 14:47\n\tbuild hash: f6cb5f54494e\n\tbuild platform: Linux\n\tbuild type: Release\n\nOn the 3D Viewport, the main screen of 'Layout', you see the drop down list of 'Object Types Visibility' where English texts are all visible and well spaced.\n\n\n\nWhen switched to the Vietnamese translation language, it looks like this:\n\n\n\nWhere 'heading' and item texts are BOTH obscured to the right, trailing with two dots ('..')\n\nThe code for this module is at:\n\n\n\nand the piece of text translation is this:\n\n\n\nPlease take this 'blender.mo' file of Vietnamese I translated and compiled locally: \n\n[blender.mo](blender.mo)\n\nand drop in to the location:\n\n2.80/datafiles/locale/vi/LC_MESSAGES\n\nof your binary before switching to Vietnamese, select to turn on translation only for 'Interface' and 'Tooltips' while testing (because I only turning on these options on my pc).\n\n**Questions**\n\nCan 'Panel's be able to calculate their size and extendable at run time to cater for the size of the 'Longest' string of text (based on the dpi of font chosen and configuration scale) and aligning themself away from the edge of the parent windows (so do not overlapped the underneath) as in this situation:\n\n\n\n- Run Blender\n- Drop the translation 'blender.mo' file into the directory mentioned\n- Edit (Biên Soạn) ->Preferences (Cấu Hình) -> Interface (Giao Diện) and click on Translation (Phiên Dịch). In the language combo box, select 'Vietnamese' (Tiếng Việt). Then click to turn on 'Tooltips' (Chú Thích Công Cụ) and 'Interface' (Giao Diện).\n- Click on drop down panels as shown in the images and notice their contents and layout.", "Assigning shortcuts: Lots of keyboard keys unknown to Blender (international keyboard layout)\nOperating system: Ubuntu 18.04\nGraphics card: GeForce GTX 1060\n\nBroken: 2.81a, 2.79, 2.81\nWorked: (optional)\n\n\nI want to use '<' key (grless in windows) as shortcut, like I have in Windows but it doesn't work with \"unsupported key: unknown\" message. The same behavior append with '^', '$', ':', '!' keys (maybe some more, didn't test) . All these keys work in all other apps.\nI have a french azerty keyboard and tried multiple keyboard configurations without success.\n\nInstall Ubuntu 18.04, install Blender 2.81a, plug a french azerty keyboard, try to change a shortcut with the mentioned keys.\n\nAdding some more info, the keys works in Blender console and text editor, it's only the shortcut assignation that doesn't work.\n\n\nI'm open to make some more testing if needed.", "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)", "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 (...)\"*", "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.", "\"Whole Character\" keying set not working properly with autokey enabled\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 2.93.4\n\nUsing the keying set \"Whole character\" with autokey enabled creates a keyframe only for the selected bone and not for all bones and properties.\n\n- Open attached file or create a new armature with more than one bone, add a few bone properties to each bone.\n- Enable autokey and set \"Whole Character\" as the keying set.\n- Move one bone and you can see that only the transform values are keyed.\n- If you enable \"Only active keying set\" in the autokey options and move the bone, a keyframe for the custom properties of the selected bones, at least, will be created, but other bones and properties will be unaffected.\n[bugreport.blend](bugreport.blend)\n", "Keying sets other than Whole Character (or keyframing in general) do not respect channel locks\nOperating system: macOS Monterey 12.3.1\nGraphics card: MacBook Air (M1, 2020)\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\n\nKeying sets (other than Whole Character) do not respect channel locking. Whole Character is the only keying set that respects channel locking, which is surprising, unexpected, and undocumented behavior. This is actually a big pain point when it comes to animating complex rigs.\n\nblender/blender-addons#70447 is related, but @lichtwerk mentioned in T70447#806580 that it would be good to file a separate report about this problem.\n\n1. Create a new Blender file with the General template.\n2. Make the default Cube object the active object.\n3. In Object Properties, lock the Cube object’s rotation channels.\n4. Create a new keyframe using the Location, Rotation & Scale keying set.\n5. Note that the rotation channels have been keyed, despite being locked.\n\nNOTE: the tooltip for locking says \"lock editing **when transforming**\" (so if we decide to respect locking in general keframing, this would need to be adjusted) ", "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", "When double clicking to selecting text the first characters aren't selected\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.23\n\nBroken: version: 3.6.2\n\nWhen you double click on any text field with the intention to select all of the text when you start dragging to select the other words the first characters dont stay selected\n\ndouble click on a word and then drag your mouse to select the next or previous words. Some of the characters will always become unselected when you drag the mouse as seen in the attached video\n\n\n\nusually when double clicking a word the entire word stays selected regardless of where the initial mouse location was when double clicked but in blender the characters before or after the mouse location when double clicked don't remain selected when you drag to select more words" ]

[ "Blender inputs do not accept nonlatin character typing (like item names or subtitles etc.)\n{[F8210181](nonlatin-error.jpg)}Operating system: Elementary OS 5.1 Hera\nGraphics card: Nvidia 540M\nplatform: Linux\nLANG=tr_TR.UTF-8\nKeyboard: Logitech K400r\n\n**Blender Version**(flatpak)\nversion: 2.81 (sub 16), branch: unknown, commit date: 1970-01-01 00:00, hash: unknown, type: RelWithDebInfo\nbuild date: 2019-12-02, 08:10:22\n\n I couln't be able to write non-latin characters in object names or subtitles etc. input area doesn't allow me to write characters like \"ş\" \"ç\" \"ü\" \"ğ\" even though my font is latin extended and on other softwares (krita, chrome, visual studio code etc. ) there is no problem.\n\nopen belender > doubleclick and change default cube name and try to **type** a non latin caharter like \"ş\" \"ç\" \"ü\" \"ğ\". but do not paste. it accepts pasting but does not accept typing.", "Text fields don't allow to enter language specific text like Umlauts \"öäü\" on X11\nOperating system: Linux-4.18.0-15-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.77\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\n\n\nVSE\nSHIFT-A->Text \nTry to enter special characters -> Nothing\nOnly Linux (see above)!\n\nHowever: Copy&Paste works!\n\n" ]

[ "Subsurface modifier new \"OpenSubdiv\" method Issue\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\n\nBroken: version: 2.80 (sub 53), \nbranch: blender2.7, \ncommit date: 2019-03-31 21:52, \nhash: `b936d7b16c`\nWorked: (optional)\n\n\nIssues with the new \"OpenSubdiv\" modifier method.\n\n- Add a simple plane mesh in Blender 2.8\n- UV unwrap it\n- Import a texture and apply it to your plane\n- Add a Subsurf modifier \n\nHere is the issue in details.\nI was doing some texture work on High-poly models, and when I applied the textures to my model, they were deformed in places.\n\n\n\n\nI later learned that the method used in Subsurface modifiers was changed :\n\n\nWould there be any way to bring back the old method ?\nbecause this is going to break a LOT of my models.\n\n", "Make \"offset edge loop\" slide evenly\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)\n\n\n\n[2019-09-17_15-04-45.mp4](2019-09-17_15-04-45.mp4)\n\nJust repeat the video example\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", "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", "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)", "Skin modifier can produce undesirable geometry\nBroken: blender-2.74-65328fa-win32\nWorked: never as the skin modifier always had problems like that\n\nThe skin modifier sometime fail and generate very bad geometry\n\n[skinbug.blend](skinbug.blend)\nload the attached blend, and see the problem as shown in the screenshot {[F177512](screenshotbug01.jpg)}(the underlying vertices are all symmetrical, as that base was done with the mirror modifier) \nTest with the various x/y/z options in the skin modifier and see how that buggy geometry can move in other place of the generated mesh\n\nOnly way to fix is to try to either move around the vertices or to rescale them (CTRL+A with the skin modifier) , not real solutions if you need all the branches to be +/- the same diameter and at exact locations.", "Inconsistency of some tools/operators (e.g. Subdivide) in regards to hidden geometry\nBroken: all or none\n\nI'm not really sure this is even an issue, though it feels like it. As far as I understand it, mesh editing tools are not supposed to affect hidden geometry. But the Subdivide tool does. Consider this mesh:\n\n\nIf you hide the middle face...\n\n\n...and then Subdivide the two remaining faces...\n\n\n...Subdivide will create new edges cutting through the hidden face, also creating inconsistent selection (i.e. selected edges in face select mode). Shouldn't the operator check that that face is hidden and not create edges through it?", "Wrong reflection in Reflection Plane when Ambient Occlusion is also turned on\nIntel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB\nWindows 7 x64\n\nBroken: 2.8, 2.9\nWorked: n\\a\n\nReflection Plane object produces wrong reflections when Reflection Plane is nearly perpendicular to camera and Ambient Occlusion is turned on.\n\n1. Open provided Blender file, switch to Rendered view and observe how Reflection Plane reflects the opposite wall as almost black.\n2. Disable Ambient Occlusion and reflection will become normal.\n3. I have also noticed that if you change Ambient Occlusion value to something like 40 mm, reflection will be turned into a gradient.\n4. Moving Reflection Plane away from the wall does absolutely nothing, if you switch to the second camera that faces Reflection Plane straight on, back wall will look normal but side walls will become dark.\n[WrongReflection.blend](WrongReflection.blend)\n\n", "\"Regression\" : Using normal or bump maps in cycles produces flat washed-out shading (caused by terminator softening)\nOperating system: Windows 10 x64\nGraphics card: GeForce GTX 1660 Dual OC\n\nBroken: 2.81, 2.82, 2.83 from 2020-03-06 22:46\nWorked: 2.80\n\nCaused by c3be14e151\n\nUsing normal or bump maps in cycles produces flat washed-out results comparing to EEVEE.\nThe bug also appears in the latest 2.83 build, it affects both Diffuse and Principled Shader but not Glossy.\nNormal Map and Bump nodes seem to produce identical results with the 2.80 version, so the problem lies with the Shader node itself.\n\n\n[bug_report.blend](bug_report.blend)\n1. Open file\n2. Switch to Rendered viewport shading", "GPU Subdivision: Geometry Nodes: Realize Instances node does not use the GPU version of the curve object\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: Current master.\nWorked: Never.\n\nCollection Info node does not use the GPU version of the curve-objects from collection.\n\n1. Create curve.\n2. Make curve extruded.\n3. Added subdivision modifier.\n4. Create another collection.\n5. New object in another collection.\n6. Added geometry nodes:\n a. `Collection Info` -> `Realize Instances` -> `Group Output`.\n b. Set first group in `Collection Info` node.", "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", "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", "Transform: Tilt values in curves are not transformed\n2.8, 2.81\n\nWhen mirroring curves, tilt values are not mirrored.\n\nIn edit mode, MIRROR(or SCALE -1) dose not change tilt values.\nSo I can not get mirrored result (bebel geometry).\n\n(In object mode, I can get mirrored 2 curves by MIRROR(or SCALE -1),\nBut JOIN the two curves results not mirrored tilt effect.)\n\nOpen:\n[mirrored_curve.blend](mirrored_curve.blend)\n* The file contains 2 splines. One is a scaled duplicate of the other.\n* Note that the tilt of the corresponding point remains the same on both splines.", "Hair from 2.79 messed up in 2.8 (modifiers prior to PSys and partially broken without 'Use Modifer Stack')\nOperating system:\nGraphics card:\n\nBroken: blender-2.80.0-git.dd3f5186260e-windows64\nWorked: 2.79b release\n\nHair particles made in blender 2.79 get messed up, when opend in 2.8. The hairs are pulled in direction of objects origin:\n\n\n[hairbug.blend](hairbug.blend)\n\nopen attached file in 2.80 (and in 2.79, to compare)\n\n---\nIt is maybe is related to T59587 .. i am not sure.", "Switching Curve Shapekeys in Edit Mode go haywire if relative to one another\nOperating system:\nLinux\n\nBroken in 2.79 onwards\nWorked in 2.78\n\nPossibly caused by\n6f1493f68f\n5e1d4714fe\n\nShapekeys on curves do not reset properly when switching between them in edit mode, and one shapekey is relative to another.\n\nSelect the circle and enter edit mode. Repeatedly switch between shapekeys 'Key 1' and 'Key 2' while staying in edit mode. 'Key 2' will change over time from just this.\n[bug_report_shapekeys_curve.blend](bug_report_shapekeys_curve.blend)\n\n**How to reproduce the scene**\nCreate a Curve object. Add Basis, Key 1, Key 2 shapekeys. Set 'Key 2' relative to 'Key 1'. Select 'Key 1' and translate/scale it. " ]

[ "Round corner in edge crease of subdivided surfaces\nOperating system: Linux Ubuntu 18.04\nGraphics card: Intel HD 5500\n\nBroken:\n(version: 2.80 (sub 35), branch: blender2.8, commit date: 2018-12-02 23:40, hash: 63ac7c799c8, type: Release\nbuild date: 2018-12-03, 00:02:45)\nWorked: (2.79b)\n\n\nThe new rounded corner on th creased face is a bug or the new pixar subdiv?? In the Old Blender there is a difference with the surfaces creases, look below the difference on the corner of surface near to the cube\n\n**screenshot**\n\nRounded corner\n\n\nNormal croner (for me :)\n" ]

[ "Apply Base (Multiresolution Modifier) on mesh with shape keys distorts the mesh\nBroken: version: 2.83 (sub 8)\nWorked: Doesn't Work even in Blender 2.79b official release. I haven't tested versions earlier than that.\n\nPressing Apply base using the multires modifier on a mesh with a stored Basis shape key causes artifacting and mesh corruption. Undo still works though.\n\n1. Delete Default Cube\n2. Add Plane mesh (Shift+A > Mesh > Plane)\n3. Add Basis Shape Key.\n4. Add Multiresolution modifier\n5. Subdivide multiple times. (Either Catmull-Clark or Simple type)\n6. (optional) Apply brush strokes in Sculpting mode. \n7. Press Apply Base in Modifier Properties.\n\nor\n\n1. Open attached file\n2. Press Apply Base in the Modifier Properties.\n\n[Shape key Multires Bug.blend](Shape_key_Multires_Bug.blend)\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}", "Broken edge lines with boolean and freestyle\nOperating system: Linux-5.0.7-200.fc29.x86_64-x86_64-with-fedora-29-Twenty_Nine 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\n\nBroken: version: 2.80 (sub 58)\nWorked: (optional)\n\n\nI'm seeing two different issues:\n(1) There is a broken line in the edge (see attached render). Rotating the object for a different angle, changing the boolean by moving one of the cylinders, etc. still causes broken lines, sometimes on multiple edges. Also, using the simple surface (without the toon shading setup of Shader-to-RGB and gradient) still causes the broken line. \n(2) The second possible issue is that while Eeevee renders correctly otherwise, Cycles also has the broken line and in addition seems to be rendering incorrectly for the toon shade effect - i.e., all solid color vs. multiple colors expected, see attached render. \n\nCreate a cube and two cylinders. Add two boolean modifiers to the cube to subtract the two cylinders. Add a toon shading setup (shader to RGB and gradient) and free style to render lines for edges. Render with Eevee and Cycles (see above). File attached. [sekhar-04-20.blend](sekhar-04-20.blend)\n\n", "Geometry Node: Mesh Boolean & Attributes domain\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.40\n\nBroken: version: 3.4.0 Alpha\n\n\nIncorrect save behavior of attributes during Mesh Boolean node if they have different domain or points.\nVideo example based on the example file:\n|  |  |\n| -- | -- |\n[2022-10-10 13-54-06.mp4](2022-10-10_13-54-06.mp4)\n\n\n1. Create 2 meshes and attach a named color attribute of a different color to them.\n2. Perform a cut operation between them using the Mesh Boolean node.\n3. Display the color of the attribute in the preview or otherwise.\n\n[test boolean.blend](test_boolean.blend)", "Mesh modeling performance regressions\nList of performance issues that we would like to fix or investigate for 2.80:\n\n* Transforming vertices in edit mode on high poly meshes is slow, due to overhead of depsgraph, mesh updates and and batch creation. Verify if there is anything unexpected happening here.\n* BMesh to mesh conversion was happening all the time at some point, is this still the case? See check_rendered_viewport_visible, it now always happens when a 3D viewport is visible, and could be quite problematic for edit mode performance.\n* Verify if custom data is only being preserved through modifier stack when needed (vertex colors, vertex groups, UVs)\n* Manipulate modal callback performance may be problematic: #55458\n", "Gizmo position is wrong for meshes with modifiers\nWin10, Win7, Mac OS Sierra\nGTX970, GTX750\n\nBroken: 2.78a e8299c8 , 2.66.0 r54697\n\n\nWhen a joint (for example, an arm) is bent, paint weight is not enough to express deformation around the joint. So it's a common practice to add a shape key for the bent shape and edit it.\nBut when you enter edit mode and select polygons to edit it, the manipulator is on wrong position. \n\nJust select faces. Manipulator is supposed to sit on the selected faces but it's not.\n\n[manipulator bug.blend](manipulator_bug.blend)", "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", "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", "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.", "Intersect (Knife/Boolean) - Exact: triangulate faces and merges double vertices\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0\n\nIntersect (Knife) with Exact method triangulates some faces (not flat faces - idn how their call exactly)\n\n* delete default Cube\n* create Suzanne\n* enter edit mode\n* create plane\n* with the plane selected, run {nav Face > Intersect (Knife or Boolean)} - Exact method (by default)\n* look at the faces near Suzanne nose, they turns to triangles\n* \n* add a Subdivision modifier\n* look at the vertex near Suzanne eyes, because vertices on eye and on cheek are at the same coordinates, they became merged together\n* ", "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", "Joining meshes or realizing instances in geometry nodes removes custom normals data\nOperating system: macOS Big Sur 11.5.2\nGraphics card: Apple M1\n\nBroken: 2.93 and 3.0 Alpha\n\n\nUsing the collection info node in geometry nodes destroys custom normals data when the geometry node modifier is applied (or when the project is exported).\n\n\nApply the geometry node modifier on the \"Dummy\" object in the attached blender project. I've also included a video that shows the issue.[collection_info_test.blend](collection_info_test.blend)\n\n[collection_info_bug.mov](collection_info_bug.mov)", "Inconsistent Limitations of Instances in Geometry Nodes\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nIt's not clear what operations can or can't be done to an instance, eg. Extrude and Scale Element, Dual Mesh, Triangulate etc all work fine but Set Position doesn't. \n\nSorry for the complex file but I wanted to leave in all the nodes I'd been through before realising that I was working an Instance still.\nThe Set Position node was the first one in that line that gave me any indication that I was still on an instance.\n\n[12 Marching Squares.blend](12_Marching_Squares.blend)\n", "Dynamic Paint doesn't update to original values on start frame\nOperating system: win10 64\n\nBroken: 2.81\n\nAdd *Dynamic Paint (Canvas)* to any mesh and try to set 0 as a start frame of simulation.\n\n1. Open file and see how Displace modifer doesn't affect mesh\n2. Run animation -> bake current cache\n3. First problem: see how weight is empty at the mesh origin (Displace modifier works except begining of animation)\n4. Second problem: return to frame 0 -> weight doesn't updated to original values (Displace modifier still active on vertex group)\n\n[dyn_paint.blend](dyn_paint.blend)", "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 in Boolean Difference when placing object with snap to vertex tool\nOperating system:Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 \n```\nDesktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26 2019 \nbase: Debian GNU/Linux 9 (stretch) \n```\n\nGraphics card: \nDevice-1: Intel Haswell-ULT Integrated Graphics vendor: Lenovo \n```\ndriver: i915 v: kernel bus ID: 00:02.0 \nDisplay: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa \nresolution: 1366x768~60Hz \nOpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.2.6 \ndirect render: Yes \n```\n\n\nBroken: blender-2.81- 14 oct \nWorked: (optional)\n\n\nBoolean Difference not working when using snap to vertex before using the modifier\n\nAdd Cube, Add another Cube. Place the second Cube intersecting the previous one using the snap to vertex tool (probably restricting axis is needed to achieve that) \n\nThen add a modifier on the first cube and use the 2nd as difference boolean operation. ERROR:There wont be any visible subtraction on the first cube as expected, only It will cut the mesh leaving all the other vertex edges and faces in the object (view in edit mode)\n\nAdd:\n(The error Only hapens using standard coordenates 0,0,0 or 1,1,1 .\nWhen the object is placed free not in the matrix, it works ok, but when the objects are beeing placed in the space matrix the error happens)\n\nThe error is also in previous blender 2.79", "Boolean modifier not working well if there is overlapping of faces\nOperating system: Linux-5.3.0-46-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.0\n\n[Boolean modifier not working well if there is overlapping of faces.\nwe can solve this problem by scaling any on of objects that involved in boolean operation, but this destroy the idea of precision modeling. especially when working in Non-Destructive Modeling work flow.\n\nnote: if this problem fixed this will make 2D Boolean operation possible.\n\nthank for your hard work]\n\n[1- duplicate existing cube and move the copy slightly in X and Y direction(not in Z direction) , while keeping it intersecting with original cube.\n2- add boolean modifier to original cube and use coped cube as target object, you can add cylinder with the same steps and will get the same result]\n[\n[Boolean_modifier_problems.blend](Boolean_modifier_problems.blend)\n\n{[F8596063](2020-06-08_07-24-24.png) size=full}\n]\n\n", "BMesh boolean fails when edge is co-planar to face (under some circumstances)\nUbuntu 17.10, Intel HD Graphics\n\n\n2.79\n\n\nBoolean operations using BMesh may not work properly when I use cubes in combination with cylinders\n\n\nwatch?v=LQyUePorgpA This video shows exactly what I did.\n\nTEXT GUIDE:\nMake a cylinder with the depth 6 and the radius 1\nMake a second cylinder with the radius 0.8 and the depth 7\nMake a Boolean operation (BMesh) to subtract the smaller cylinder from the bigger one\nYou now have a pipe.\nPlace a cube covering half of the pipe but bigger than the pipe\nDo a Boolean operation (BMesh) on the pipe: difference with the cube.\n\nThe results should be that the pipe disappears or stays a whole pipe without getting anything cut of of it. The results seem to vary when you restart Blender and different rotations may also make a difference.\n[broken_bool.blend](broken_bool.blend)" ]

[ "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", "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)", "Subdivision surface modifier creates self-overlapping geometry on coplanar non-triangulated face\nOperating system: Linux-5.15.5-76051505-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2) Intel 4.6 (Core Profile) Mesa 21.2.2\n\nBroken: version: 2.93.4 -- confirmed in 3.1a 12/20/2021\nWorked: Unknown\n\nWhen set to simple, the subdivision surface modifier creates self-overlapping geometry with certain concave polygons on non-triangulated coplanar face:\n\nCan be related to #61145. See steps for more details.\n\nThis affects the `Subdivide` node in Geometry Nodes as well. \n\nAttached file have needed objects to reproduce.\nIn image is different examples of issue, from left to right then top to bottom:\n1. Plane with `Simple` subdivision surface modifier, works as expected.\n2. Plane with top-left vertex moved so that it's edges have angle >180 degrees. When moving either right, down or towards bottom right vertex issue will show itself. In this working state sum of this vertex angle and it's neighbors is strangely close to 270 degrees (with remaining bottom-right vertex having 90 degrees).\n3. Vertex moved close to opposite one. In `Top` view it shows that this unnecessary face have back normal but if you move viewport aroung you'll see it's gliching, overlapping with another face that have forward normal.\n4. Case where top edge of a plane is subdivided and created vertex moved to center to the point of glitching. See that on the right it shows back face normal but on the left it shows different color which I don't really know what it means.\n5. Showcasing slightly different glitch. When troubled vertex moved top/right face with back normal will disappear. That might be filed as separate report.\n6. Same as - [x] but bottom-right vertex also moved close to top-left one. Notice that while top-left vertex not moved from it's \"glitchless\" position in - [x] there is still bug.\n\nIssue is gone if face is non-coplanar. That can be seen if in attached file second collection made visible:\n\nThat is same meshes as before but with troubled vertices moved down Z axis. If view is rotate the cause for self-overlapping geometry can be seen. That's example [3]:\n\nWith that topology it's clear that if you move vertex so that face becomes coplanar you'll get self-overlapping geometry. \n\n`Simple` mode of subdivision surface definitely doesn't befave like `Subdivide` in Edit mode. You can see that in non-coplanar example [1]:\n\nWhen entering Edit mode transparent initial mesh without modifier is shown. If it behaved like `Subdivide` then it would not be shows because of full match with modified geometry.\n[examples subdivision coplanar non-triangulated.blend](examples_subdivision_coplanar_non-triangulated.blend)", "Overlapping objects of different sizes with volumetric materials render incorrectly\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.75\n\nBroken: version: 2.83.4\nWorked: 2.82a\n\n\nTwo cubes, both principled volume, one large one small, smaller cube inside larger cube. \n\nThe area inside the smaller cube from the view perspective renders differently than outside with a hard edge where the mesh ends, the effect is much easier to see with a texture controlling the volume density of the large cube. Looks to me like an issue with blender using different step sizes for different objects. Definitely not an issue with not enough transparency/volume light bounces, already tried that.\n\nOnly happens with cycles\n\nOpen blend file\nSwitch to rendered view\nToggle visibility of big volume and/or small volume in outliner to see difference\nExtra notes in shader nodes for big volume and small volume's materials\n\n[overlapping volumes hard edge bug.blend](overlapping_volumes_hard_edge_bug.blend)", "Carve vs. Bmesh booleans\n__ Copy for archival purposes from: 049334.html __\n\nAfter the removal of Carve for booleans, which is an important part of the \nFracture Modifier, I did some tests with Bmesh booleans to find out the \ndifferences and what we need to change in order to make FM work with that \nsystem. I'd like to share some of my observations and maybe discuss possible \nimprovements for consistency with you. \n \nOverview: \nBlend file: [booleans-bmesh-vs-carve.blend](booleans-bmesh-vs-carve.blend)\n(Note that you need an older Blender build with Carve) \n \nOur premise always was to make the Fracture Modifier a robust tool that should \nnot be nitpicky about the given input mesh. It should basically work for the \nartist at all times. This means the FM should also accept and work with \nnon-manifold, self-intersecting and complex meshes which are typical use cases \nin production and provide solutions for that. We have used Carve for this in \nthe past and analyzed and utilized its behavior to make that possible, thus my \ntests include all those possible variants. \n \nResults:\n\nMy first impression was that Bmesh is doing quite well now. It produces more \npredictable results for non-manifold targets and even for some manifold ones. \nHere are my observations: \n \n1 - Bmesh is leaving free edges in non-manifold results (well visible in orange \nin the lower right), those should be removed after operation. \n \n2 - Bmesh is not face normals aware. I'm not sure if this is good or bad thing \nin a higher sense, but I know that this is limiting factor for some users (see \ninverted normals variants which would flip results in Carve). \n\n3 - As a result of 2. Bmesh can produce meshes with inconsistent normals as it \nkeeps the original normals of the operator object but ignores them for the \nactual boolean operation (row 3 and 6). \n\nThis is what I could see, maybe there are more differences. I think that Bmesh \ncould be more consistent with Carve in general but it should at least output \nclean results. We have no \"make normals consistent\" modifier in Blender for \ninstance to fix normals within a modifier stack. \n \nI'm aware that these are not necessarily considered being bugs, so I'm just \nputting it here for discussion and making you aware of that.\n", "Using Viewport Navigation Gizmos can execute tool gizmos or sculpting\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.91.0 Alpha\nWorked: never worke in 2.8+\n\nLeft Mouse dragging on those two buttons can lead to unexpected/undesired behavior. \n\nThe dragging executes whatever tool is currently active:\n- if the selection tool is active, a selection is drawn\n- if the move tool is active and an object selected, the object is moved\netc.\n\nWhy this is a problem:\nIf one of these two buttons get accidentally dragged a little, it can apply a tiny yet destructive change to your scene which isn't noticed at first (as this behavior is unexpected).\n\n\n\nThis example is for the move tool:\n1. Open a new scene\n2. Activate the move tool\n3. Select the cube\n\n4. Drag the camera or perspective button to the side\n5. See how the cube is moved\n\n\n\nThis example is for sculpting:\n1. Open new sculpting scene\n\n2. Drag the camera or perspective button to the side\n3. See how the mesh gets distorted\n\n\nThanks\n", "Geometry Node: Mesh Boolean & Attributes domain\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.40\n\nBroken: version: 3.4.0 Alpha\n\n\nIncorrect save behavior of attributes during Mesh Boolean node if they have different domain or points.\nVideo example based on the example file:\n|  |  |\n| -- | -- |\n[2022-10-10 13-54-06.mp4](2022-10-10_13-54-06.mp4)\n\n\n1. Create 2 meshes and attach a named color attribute of a different color to them.\n2. Perform a cut operation between them using the Mesh Boolean node.\n3. Display the color of the attribute in the preview or otherwise.\n\n[test boolean.blend](test_boolean.blend)", "data transfer breaks if more than one remesh is above it in the stack.\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\nSometimes the `DataTransfer` modifier doesn't work for no apparent reason.\nIn the attached file, putting a `Boolean` modifier after the `Remesh` makes `DataTransfer` work again.\nThis isn't anything to do with differing topology between the hidden and unhidden monkey, otherwise it wouldn't work with only one remesh modifier in the stack.\n\n- Open the file bellow\n- with the monkey selected, turn off the boolean modifier in the stack. \nThe uvs which are being transferred from the hidden monkey will disappear (making the monkey all black).\n[simplified data transfer.blend](simplified_data_transfer.blend)\n\n---\nOriginal file:\n\nOne remesh modifier works fine:\n\n\n\ntwo remesh modifiers break the data transfer:\n\n\n[terminator.blend](terminator.blend)\n", "Incorrect order in undo stack when switching between Object Mode and Edit Mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83 (sub 10)\nWorked: I don't know, I am a new user\n\n**Expected Behavior**\nWhen you undo, you expect to undo the last thing you did (FIFO).\n\nCurrently, if I am in Edit Mode and I change the scale of an object in the \"Transform\" panel on the right, and then undo immediately, it will undo all changes I did in Edit Mode and only then, undo the scale change even though I just did the scale change.\nIn other words, for some reason the undo stack in blender prioritizes things you didn't do in the transform panel when you are in Edit Mode even if these other changes aren't the most recent ones.\n\nFile > New > General\nA cube should appear in the center\nUse Tab to go into edit mode\n(1) Do some changes like moving vertices\n(2) Now change the scale of the object in the transform panel on the right\nNow hit Ctrl+Z to undo the last change\n\nIt will likely undo (1) the \"Edit Mode\" change instead of (2) the \"Transform Panel\" change.\nIf you keep doing Ctrl + Z it will eventually undo the transform panel change after undoing all the \"Edit Mode\" changes.", "Most sculpt tools do not work while model is animated\nLinux 64-bit\n2.93.2\nMost sculpt tools do not work as expected when the object is spinning like it's on a pottery wheel. Some tools like the clay tool work okay, but other tools like smooth and scrape do not. I think it has to do with the stroke method; the stroke accounts for screen space but not the local transform of the object if it's moving during a stroke. Video of my attempt here:\n[pottery.mp4](pottery.mp4)\nI made this as a joke and it looks like garbage, but unfortunately it went viral and everybody thinks it's a great idea so now more people are gonna try it and complain that it doesn't work. It's a valid workflow that you have to account for now apparently. I'm really sorry.\n - Open the attached file\n - Play the animation\n # Try to sculpt the thing while it spins\n[bowl.blend](bowl.blend)\n", "Mesh cache Modifier cant unselect Flip axis once selected \nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nin Mesh cache Modifier i cant unselect X,Y,Z Flip axis once selected ..it can only be interchanged\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)", "Dyntopo detail size drawing with Shift + D seems broken\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: At least a few alpha versions ago\n\nDyntopo size control with Shift + D seems broken.\nThe first time I tried, the gizmo simply froze and the Resolution value didn't change after mouse movement.\nAfter installing the latest GeForce Studio Driver — version 457.30 — I tried again. The gizmo casts infinite lines, but I noticed that the Resolution value does change after mouse movement.\n\n1. Enter Sculpt Mode.\n2. Activate Dyntopo.\n3. Switch to Constant Detail mode.\n4. Press Shift + D.", "Mesh flickers in edit mode if shapekey added\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.0.0 and later\nWorked: 2.93\n\nThat mesh I put in .blend file is from my old project (started in 2.79). For some reason normals on that mesh go crazy if I try to edit it in Face selection mode. I found that this particular mesh can't have shapekeys and auto smooth enabled at the same time.\n\n1. Add Basis shapekey to the mesh\n2. Enter Edit Mode\n3. Select Face Selection Mode\n4. Move any face\n\n[bugFlicker.blend](bugFlicker.blend)\n[bandicam 2022-12-03 01-21-18-089.mp4](bandicam_2022-12-03_01-21-18-089.mp4)", "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" ]

[ "Sculpt glitches when using Eevee\nBroken: 97e2b0c594a0\nWorked: Not sure if it ever did.\n\nArtifacts (light variation, ghosting) when sculpting with Eevee.\n\n\nOpen the following file and continue sculpting:\n[dyn28.blend](dyn28.blend)\n\nYou will soon get artifacts like:\n\n\nTo reproduce from scratch you can start with a sphere, subdivide a few times. I had to turn dyntopo and sculpt a bit before turning off. But I'm not sure if it's related, or just that dyntopo gives me a particularly messy mesh." ]