Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "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).", "Smooth shading usabilty\nWhen adding a mesh primitive in Blender, it is by default flat-shaded without subdivision surfaces. This means that after adding a new object with a smooth surface (like a sphere or monkey mesh), the user almost always has to change some settings.\n\nWe could change the default mesh settings to avoid that. However there are two distinct use cases which require different settings.\n\n* Meshes with autosmooth and/or custom normals. This could be either a low poly model for games, or a high poly model imported from CAD software.\n* Subdivision surfaces with creases to define sharp areas of the model. Custom normals are lost in the subdivision process, and autosmooth can't be combined with GPU acceleration.\n\nOnce subdivision surface settings become part of the mesh (#68891 (Subdivision surface settings part of the Mesh)), we could handle these as more distinct cases in the user interface and implementation.\n* If a mesh is a subdivision surface, no autosmooth or custom normals would be available.\n* Subdivision surface mesh primitives could be in a separate submenu of the Add menu, with all faces smooth shaded by default.\n* Mesh primitives could have smooth shaded faces and autosmooth enabled by default when it makes sense.\n\nEnabling autosmooth by default will negatively impact performance, particularly in edit mode. It's not obvious this is something we want to do. Further optimizations in this area are possible, but there will always be a cost.", "Edit Dyntopo Detail Size operator is not working with all methods.\nOperating system: Ubuntu 18.04\nGraphics card:\n\nBroken: master #e7dc3c91ad82\nWorked: 2.90\n\nEdit Dyntopo Detail Size operator was recently replaced to have a better gizmo.\nThat only works with Constant Detailing method.\n\nShift D is doing nothing when Relative or Brush detailing method are used.\nThat is a regression. It is pertinent to change the size for those methods, too.\n\nProbably, gizmo should work differently for a Brush Method. But, at least, shortcut should allow to change Detail Size like in 2.90. \n\n\n\nIssue in Master :\nEnter into Sculpt Mode.\nEnable Dyntopo mode.\nPress Shift D. Nothing happens.\nChange Detail Method from Relative to Constant. \nPress Shift D. New Gizmo is available.\nChange Detail Method from Constant to Brush.\nPress Shift D. Nothing happens. \n\nRepeat same steps In 2.90 :\nCircle gizmo is adapted to used method.\nRelative method is relative to screen. So, circle does not go above a certain limit.\nConstant/Manual method is relative to World Space. Size of Circle is not limited.\nBrush Method is relative brush size. Gizmo is showing a percentage.\n", "Bounding Box: compute during depsgraph evaluation\nCurrently `Object::runtime::bb` bounding boxes (BBs) are computed on demand. There are a few different code paths that trigger such computation, and not all of them have the same computation (resulting in #91102). This problem be solved by moving the computation of the bounding box to the depsgraph evaluation. This can then be done consistently and in parallel.\n\nThis improvement step should also be used to investigate which coordinate space is used for storing the bounding box, and actually documenting that in a comment in the source code.\n\n------------\n\nRelated note, **not part of this task** but could be fleshed out in a subtask:\n\nThe current code doesn't take instancing into account; the bounding box of each instance of an object is recomputed from scratch. From what I (@dr.sybren) understood, this is even done sequentially. This could likely be parallellized, and maybe some other smartness could use the BB of the duplicator to compute the BB of the dupli. Not sure how the latter could be done efficiently, though, as BBs are axis-aligned and simply applying a transformation matrix may make it too large/small.\n", "Motion Paths not updating when working on the graph editor\nOperating system: Windows 10\nGraphics card: 1050 TI\n\nBroken: 3.5\nWorked: Supposedly never worked due to the way the code is set up.\n\n\nMoving the F-curve for key-framed object will not update motion paths.\n\n\n- Do some location key frames on the default cube.\n- Calculate the cube's motion path in the object properties tab.\n- Move the f-curve key frames on the default cube, motion path does not update.\n - Move the object directly, only the motion path of the current frame is updated.\n\n", "GPU Subdivision Causes Artifacts in Mesh Analysis Overlay\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken:\nversion: 3.1.1 Release Candidate\nversion: 3.3.1\nversion: 3.5.1\nversion: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-25 13:50, hash: 6ee8aa4997ee, type: release\nversion: 3.6.0 Alpha\n\nWorked: could not find.\n\nWhen GPU subdivision is enabled, the Mesh Analysis overlay shows artifacts.\n\n\nPlease follow these steps to reproduce the issue:\n1. Start Blender.\n2. Select the default cube.\n3. Apply the Subdivision Modifier (press Ctrl+1).\n4. Enter edit mode.\n5. In the viewport overlay menu, enable Mesh Analysis.\n\n**Known Workarounds**\n1. Disable GPU Subdivision.\n2. Disable \"Show in Edit Mode\" for the Subdivision modifier.\n\n", "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", "Geometry Node: Sculpt mode doesn't cause update due to editing\n## SIMPLE REPORT:\n\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.5.0 Alpha\nWorked: Never\n\n\nObjects with geometry nodes do not update if dependent on the object that is currently being sculpted.\n\n[2023-01-14 13-13-37.mp4](2023-01-14_13-13-37.mp4)\n\n\n1. Duplicete default cube.\n2. Add Geometry Node tree on copy, add `Object Info`, choose other one cube, connect geometry to group output.\n3. Select other one cube, go to sculpt mode, do anything.\nCube with geometry node does not according to sculpted one\n\n## USER REPORT:\n\nOperating system: Windows 10 Pro\nGraphics card: Geforece RTX 2080\n\nBroken: 3.4.1 Stable\nWorked: not sure\n\n\nGeometry nodes network is not updating when in sculpt mode. It's updating fine when in edit mode.\n\nI have nodes basically adding differences in point positions from one mesh to another -\n\n\n\n\n[sculpt_mode_update.blend](sculpt_mode_update.blend)\n\n\n\n\n\n- Create an object(=A) and add a geometry nodes modifier\n\n- Duplicate the object(=B), and use it's object info in the first objects geometry node\n\n- Connect object B geometry, position and ID into a sample index node, sampling a vector on a point\n\n- Subtract the vector coming from the sample index from object A's position\n\n- Connect the result to the offset\n\n- Try moving verts on object B in edit mode and see object A updating\n\n- Try moving verts on object B in sculpt mode. Object A is only updating when switching from sculpt mode back to object mode.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Remeshing object with subdivision modifier hangs Blender\nOperating system: macOS 10.14.6\nGraphics card:\n\nBroken: All versions of Blender but tested on Version 2.93.0 (2.93.0 2021-02-25) & Version 2.92.0 (2.92.0 2021-02-25)\nWorked: ?\n\nRemeshing object with subdivision modifier hangs Blender\n1 Add a subdivision modifier to the default cube, set it to 2 or more.\n2 Jump into Sculpt mode and remesh with default voxel settings, it should work fine.\n3 Undo the last remesh and now change the voxel size to 0.002 m and remesh again, it hangs.\n\n\nDo step 1 again, this time apply subdivision modifier and then try to remesh with voxel size of 0.002 m, it should work\n\n\n\n", "Support for tools with interactive geometry preview\nSome of the current or planned tools (add object tool, insert mesh brushes...) and other functionality requested project members require adding new geometry to the scene. \n\nAs far as I know, these tools can't render new geometry without creating a new object or adding that geometry to an existing mesh. This makes the gizmo previews of the add object tool not ideal and some of the requested functionality for sculpt mode is not possible to implement. It would require to modify the mesh and rebuild the PBVH in real time each time geometry changes. \n\nThe only tool so far that requires this functionality in sculpt mode is a limited version of the insert mesh brush in [D9380](D9380). That tool joins the insert mesh to the active mesh using BMesh when the stroke starts and then rebuilds the PBVH so the new geometry can be rendered. This makes the tool lag each time a stroke starts in a high poly mesh, and it limits the functionality to only an insert operation per stroke. (The ideal behavior should be that the insert mesh brush should insert a new mesh per stroke step, so you can insert meshes with spacing over the mesh). \n\nThe main goal of this design of to have a fast way to create previews for tools that modify geometry which look like the mesh is actually being modified. This is just a implementation detail, so the user should not know if the mesh geometry is actually being modified or if it is just a preview, as both options should ideally look the same. \n\n## Proposed solution\n\nThe ideal solution would be to have a generic function(s) that can render arbitrary geometry using the current scene shaders and render mode (as it was a new mesh object). This function should be possible to use from any operator and mode. \n\nIn the case of the insert mesh brush, the tool can manage a list of triangles and indices created by combining the geometry of the insert mesh and use this function to render them in real time without modifying the PBVH or the active object geometry. Then after the stroke finishes, all the new geometry can be joined to the active mesh in a single operation.\n\n## Workarounds\nIf implemented that functionality is not possible, some workaround for sculpt mode could be:\n- When PBVH rendering is used, add a \"fake\" node to the PBVH and add the new geometry there. If this fake node exists, render it as a normal node. When the operation finishes, delete this node, join the meshes and rebuild the tree. This approach won't work when PBVH rendering is disabled, so these tools will still lag.\n- Exit sculpt mode when the operation starts and create a new temporally object to do the geometry preview there. After the operation finishes, join the geometry, delete the preview object and enter sculpt mode in the initial object. Not sure what potential problems this approach could have (like undo). \n", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "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)", "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.", "Apply modifiers on objects with shapekeys (with some exceptions)\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nCurrently it is not possible to apply modifiers to an object that has shapekeys, even though it would be technically possible for most modifiers. I suggest making it possible to apply modifiers to objects with shapekeys with some exceptions.\n\n\n\nFor example:\n\nThe subdivision and wire modifier does not modify the objects topology as the shape change. This modifier could be applied while still keeping the shape keys.\n\n---\n\nScreen capture example of how to apply modifiers and keep shapekeys.\n[apply modifiers with shape keys.mp4](apply_modifiers_with_shape_keys.mp4)\n\n---\n\nModifiers that can't be applied in a simple way when the object has shapekeys.\n\n- Boolean\n- Build\n- Decimate\n- Geometry nodes (in some cases. Easiest to just exclude this modifier)\n- Mirror (**IF USING BISECT**)\n- Remesh\n- Skin\n- Volume to mesh\n- Weld\n- Explode\n- Fluid\n- Ocean\n- Particle instance (Since source particle system density mapping can be applied in world space)\n- Particle system \n\n\n\nWhen the user tries to apply any of these modifiers when the object has shape keys, the error message should be:\n***Modifier that changes topology based on shape cannot be applied to a mesh with shape keys***\n\nNote:\nWhen applying a modifer of type \"Modify\" (for example \"Data transfer\"), the current shape should be used when applying the modifier (i.e. the resulting shape of all combination and values of the objects shape keys)\n\n\n", "Some areas do not use modified (by geometry nodes) curve\nOperating system: Windows 10 - Probably irrelevant.\n\nBroken: 3.0.0 (not checked earlier versions).\nWorked: (none)\n\nThe Curve modifier on mesh objects does NOT use the modified version of a curve\n\nSee attached blend file for easy example: [bug - curve with modifier.blend](bug_-_curve_with_modifier.blend)\nExample screenshot of that blender: \nThe thin line is the curve, which has geometry nodes modifying it.\nThe thick (square) line is the mesh, which targets the curve but doesn't use the modified version.\n\n - Add BezierCurve, with a few points.\n - BezierCurve: Add geometry nodes (or any other modifier, like wave or whatever) that changes the curve.\n - BezierCurve: (for visibility) add geometry.\n - Add Cube .1m \n - Cube: Add Array modifier and Curve modifier, targeting the BezierCurve\n\n**Expected result**: Mesh follows modified curve.\n**Actual result**: Mesh follows original (unmodified) curve.\n\nThe blender file shows this very easily, the modified curve is round, the mesh is in the \"old location\" that the curve would have without the modifier on the curve.\n\n\nYes, this is a duplicate of: 93702/ - Where apparently there is confusion on what the issue is. I could not find a way to un-archive a ticket.\n\n\n**Areas Affected**\n- Curve modifier\n- Spline IK" ]

[ "Toggling Autosmooth changes evaluated bbox `obj.bound_box` when SUBSURF mod (using GPU subd) is present\nOperating system: Linux-6.2.0-76060200-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\n\nBroken: version: 3.5.0\nWorked: -\n\nOn a mesh object with a SUBSURF mod active (using GPU Subdivision), the (evaluated) bounding box at `obj.bound_box` will only produce the correct coordinates when `obj.data.use_auto_smooth` is enabled. Otherwise it will be produce the coordinates of the original mesh bounding box, even though the evaluated mesh is clearly smaller, and so the bbox should be too.\n\nThat makes relying on `obj.bound_box` impossible, when working with the bounding box and assuming it represents the evaluated mesh object.\n\nInterestingly, boolean mods don't share this behavior, the bbox created using booleans, works properly with either auto smooth setting.\n\nSee watch?v=KKnWbRL5h7o for demonstration\n\n\n* open the attached blend file\n* toggle Autosmooth and see the bound box change, even though the evaluated mesh displayed does not change at all.\n\n" ]

[ "Support Scenes Overrides\nCurrently Scenes liboverrides are not really working, changes to its master collection will be lost, resync of scene itself is not possible when the override is the active scene, etc.\n\nSee e.g. #89963 (crash when library override is applied to an object)", "GPencil: Add option to jump to scene from Video Sequencer Strip\nNeed a way to jump from the strip to the scene edition directly.\n\nIt's necessary to define in some place what it's the layout to use.", "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. ", "Crash Python API - GPUOffScreen.draw_view3d() crashes blender with draw_type = POST_VIEW but works with draw_type = POST_PIXEL\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.1\n\nWhen using [GPUOffScreen.draw_view3d() ]] in a [[ https:*docs.blender.org/api/current/bpy.types.Space.html?highlight=post_view#bpy.types.Space.draw_handler_add | draw_handler ]], blender crashes when running the [[ gpu.shader.html?highlight=gpu+shader+from_builtin#built-in-shaders | 3D_IMAGE builtin shader ](https:*docs.blender.org/api/current/gpu.types.html?highlight=draw_view3d#gpu.types.GPUOffScreen.draw_view3d) if the draw_type was set to POST_VIEW but works if the draw_type was set to POST_PIXEL.\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script Crash3D and blender will crash\n\n\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script NoCrash2D, and it will draw the camera view in the viewport without crashing\n\nAttachments:\n\n[CrashScriptDrawView3D.blend](CrashScriptDrawView3D.blend)\n[blender.crash.txt](blender.crash.txt)\n\n\n\n\n\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```", "Blender 3.6.1 crashes when switching to Viewport Shading to Rendered on MacBook Pro M1\nOperating system: macOS-13.5-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\n\nEnabling objects in the scene causes blender to no longer render. It just says: Sample 0/32 (Using optimized kernels) and if i try and change the Viewport Shading back to something else it crashes. This issue seems to only happen on a specific file.\n\nOpen file, switch Viewport Shading to Rendered, try and switch it back to anything else.\n\n", "Crash when importing Collada .dae file\nOperating system: macOS 10.15.7 (19H114)\nGraphics card: AMD Radeon Pro 5500M 8 GB graphics\n\nBroken: 2.91.0 (2.91.0 2020-11-25)\nWorked: N/A\n\nI exported the attached .dae file from SceneKit on iOS. When I try to open it in Blender, it crashes. It's worth noting that [Apple's documentation ](1523577-write) for the SceneKit → .dae export says it should work only on macOS, but I was able to use it on the iOS simulator. It's possible that I'm using some sort of unsupported configuration, but Blender should at least report an error instead of crashing. And if there's something wrong with the .dae file, I'd like to report it to Apple.\n\n1. Open Blender.\n2. Choose **File** → **Import** → **Collada (Default) (.dae)**.\n4. Choose the attached Juggler.dae file.\n5. Try to import with default options: all checkboxes are Unchecked under Import Data Options, Armature Options, and Keep Bind Info.\n6. Crash.\n\n[juggler.dae](juggler.dae)\n\n[Blender_2020-12-29-143229_A9918.crash](Blender_2020-12-29-143229_A9918.crash)", "Avoid AssetHandle hacks in BPY\nThe asset handle is exposed directly as the file it wraps to BPY via `context.asset_file_handle`. This is bad design and should not go into the release if possible. Instead the limitations that don't allow us to return `AssetHandle`objects directly to BPY should be resolved. I think this can just be done by allocating the `AssetHandle` and letting the `FileDirEntry` own this. Then we can return the handle safely to BPY. There may be some pitfalls involved with that though.", "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", "Object properties In-front doesn't work in viewport shading\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nObject properties In-front doesn't work in viewport shading\nAll the other options works in Object properties/viewport display, except for In-front \n\n\n- Open attached file\n- Go to Viewport Shading\n[lookdev_in_front_bug.blend](lookdev_in_front_bug.blend)\n", "Importing a keymap with a default name makes a non deletable copy\nBroken: version: 3.2.1\n\nAfter importing a keymap configuration with the name \"Blender\" it created a copy of the default setting that is impossible to remove from the UI at least.\n\n\n\n\n\nImport a keymap setting with a default name\n\n\n**Fix**\nDelete keymap configuration from the user folder directly \n\n> \\AppData\\Roaming\\Blender Foundation\\Blender\\3.1\\scripts\\presets\\keyconfig\n\n\n", "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", "blender crash itself while importing a dae (collide) file\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nBroken: version: 2.82 and all versions in between then and now\nWorked: n/a\n\nHi, I'm using blender version 3.3 on a windows 10 downloaded on steam.\n\nwhen i try to import dae files, blender crashes itself and shuts down\n(this only happens with some dae files, not all and the ones who crash are not to big ).\n\nI tried to search with powershell to find the problem and I got this:\n\nError: EXCEPTION_ACCESS_VIOLATION\n[bgr_darryls_ship_ground.dae](bgr_darryls_ship_ground.dae)\n\n```\nThe gh->hashfp function pointer is NULL (hasn't been initialized yet)\n\nblender.exe!ghash_keyhash(const GHash * gh, const void * key) Line 133\tC\nblender.exe!ghash_lookup_entry(const GHash * gh, const void * key) Line 411\tC\nblender.exe!BLI_ghash_lookup(const GHash * gh, const void * key) Line 736\tC\nblender.exe!BKE_armature_find_bone_name(bArmature * arm, const unsigned char * name) Line 601\tC\nblender.exe!ArmatureImporter::create_armature_bones(Main * bmain, std::vector<Object *,std::allocator<Object *>> & arm_objs) Line 478\tC++\nblender.exe!ArmatureImporter::make_armatures(bContext * C, std::vector<Object *,std::allocator<Object *>> & objects_to_scale) Line 826\tC++\nblender.exe!DocumentImporter::finish() Line 228\tC++\n[External Code]\t\nblender.exe!DocumentImporter::import() Line 127\tC++\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", "Open Blender\nHello\n\nI can't open the app, i dowload all versión windows, windows store and portable.\n\nsxstrace.exe\n\nI have windows 10, but i can open the app,\n\nI hope you can help me\nThanks\n\n" ]

[ "Dont import OBJ format\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 73)\nWorked: (optional)\n\n\nTraceback (most recent call last):\n```\nFile \"D:\\Blender28\\Git-451c533e25dd-30-May-22-26\\2.80\\scripts\\addons\\io_scene_obj\\__init__.py\", line 145, in execute\n return import_obj.load(context, **keywords)\nFile \"D:\\Blender28\\Git-451c533e25dd-30-May-22-26\\2.80\\scripts\\addons\\io_scene_obj\\import_obj.py\", line 1241, in load\n dataname,\nFile \"D:\\Blender28\\Git-451c533e25dd-30-May-22-26\\2.80\\scripts\\addons\\io_scene_obj\\import_obj.py\", line 689, in create_mesh\n faces_ma_index = tuple(material_mapping[context_material] for (_, _, _, context_material, _, _, _) in faces)\nFile \"D:\\Blender28\\Git-451c533e25dd-30-May-22-26\\2.80\\scripts\\addons\\io_scene_obj\\import_obj.py\", line 689, in <genexpr>\n faces_ma_index = tuple(material_mapping[context_material] for (_, _, _, context_material, _, _, _) in faces)\n```\nKeyError: None\n\nlocation: <unknown location>:-1\n\n\nimport obj file (12Mb)\n\n\n", "OBJ import is broken\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.71\n\n\nBroken: version: 2.80 (sub 72)\nWorked: 2.79b\n\n\nOBJ import fails to import file. It works fine in 2.79b.\n\nImport the attached OBJ file in 2.79b. It will load fine.\nAttempt to import the same OBJ into 2.80 and it will not load.\n[jacketfixed.OBJ](jacketfixed.OBJ)\n\n", "Error import obj file\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nTraceback (most recent call last):\n```\nFile \"D:\\Soft\\blender_2.8\\30_05_2019_blender-2.80\\2.80\\scripts\\addons\\io_scene_obj\\__init__.py\", line 145, in execute\n return import_obj.load(context, **keywords)\nFile \"D:\\Soft\\blender_2.8\\30_05_2019_blender-2.80\\2.80\\scripts\\addons\\io_scene_obj\\import_obj.py\", line 1241, in load\n dataname,\nFile \"D:\\Soft\\blender_2.8\\30_05_2019_blender-2.80\\2.80\\scripts\\addons\\io_scene_obj\\import_obj.py\", line 689, in create_mesh\n faces_ma_index = tuple(material_mapping[context_material] for (_, _, _, context_material, _, _, _) in faces)\nFile \"D:\\Soft\\blender_2.8\\30_05_2019_blender-2.80\\2.80\\scripts\\addons\\io_scene_obj\\import_obj.py\", line 689, in <genexpr>\n faces_ma_index = tuple(material_mapping[context_material] for (_, _, _, context_material, _, _, _) in faces)\n```\nKeyError: None\n\n\n", "Error when importing OBJ\nOperating system: Windows-10-10.0.14393 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\n[Error when imp{[F7084054](OBJ_import_error.jpg)}orting an OBJ file, never had this problem in the past version]\n\n\nThank you!!!", "Problem with import obj\nOperating system: windows 10\nGraphics card: nvidia gefroce 1030\n\nBroken: (example: 2.80.74, 19dcb22a885d, master, 2019-06-02, branch blender 2.7)\nWorked: (optional)\n\nError when I import obj from instant meshes. But when I import obj from that Blender version, all is ok. Import-export vesrion 3.5.8.. In Blender version 2.80.71 i haven't this problem, import-export version 3.5.7.\nBased on the default startup or an attached .blend file (as simple as possible).\n- Create model in Blender 2.80.74\n- Export model in obj format\n- Doing lowpoly in Instant meshes\n- Export model from instant meshes in obj format\n- Trying to import obj in Blender 2.80.74\n" ]

[ "Texture Paint: Wrong active Texture Slot\nOperating system:win10\nGraphics card:GTX 740m\n\nBroken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, build date: 2021-02-25, 09:31:14, hash: 02948a2cab\n\nVpqy7BmMKaA\n\n- Open attached file or:\n - Go to \"texture painting mode\" (in default workspace)･\n - Create 2 base color textures\n - Open Shader Editor\n- In the Shader Editor, select non -active texture (\"Material Base Color 2\")\n- in the View 3D, paint texture\n- Nothing happen in visual.\n- The other texture slot is changed instead of current active texture.\n[tex_slot_problem.blend](tex_slot_problem.blend)\n\n", "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)", "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.", "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)", "2.80 Pose Breakdowner doesn't work in Add NLA Strips\nOperating system: ubuntu 18.04\nGraphics card: gtx1080ti\n\nBroken: (2.80)\n\nPose Breakdowner doesnt work when editing NLA Tracks \n\n\nOpen attached file and use Pose Breakdowner\n[broken .blend](broken_.blend)", "why some hairs are not moving with dynamic hair? in blender 2.90/2.91\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 670/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.1\n\nwhy some hairs are not moving with dynamic hair? in blender 2.90/2.91\nif I don't modifer the hair weight all the hairs will move,but when I brush some weight to the hair ,\nsome hairs are not moving in dynamic.\n\n[dynamic hair error.blend](dynamic_hair_error.blend)\n\n", "Weight paint mode can show influences of non selected vertexgroups (if weight is controlled by multiple dynamic paint brushes)\nOperating system: Linux-4.15.0-147-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.1\n\nWeight paint mode can show influences of non selected vertexgroups (if weight is controlled by multiple dynamic paint brushes)\n\n[PBdynamicPaint_check.blend](PBdynamicPaint_check.blend)\n\n- open .blend\n- go to weightpaint mode\n- play animation\n- in the mesh properties, change from one vertexgroup to the other back and forth\n- influence of one group is (partially) still visible when switching to the other\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}", "Box with beveled vert will damage, if use multires modifier in simple mode.\nOperating system: Fedora 32, 64bit\nGraphics card: GTX 650Ti\n\nBroken: version: 2.91.0 Alpha\nWorked: blender-2.82a-windows64\n\nAdd cube, bevel one vert (1 segments) add multires modifier, select simple mode, and subdivide 2 or 3 times. Mesh will damaged.\nIf beleled 2 or more verts subdivision works stability, but not always. Sometimes it will damaged, sometimes properly.", "Multi-Object (Weight) Painting\nMulti-object weight painting would be extremely useful when rigging characters with clothing pieces that are separate objects. If a character has a shirt and a jacket, they both have to be weight painted identically, but separately.\n\nThe objects could be combined, but that would mean they must share a modifier stack, which is not always an option. We could also paint one then transfer the weights, but that only works between very similar objects. So we are stuck with meticulously weight painting both clothing pieces, while making sure the weights match between them.\n\nWith multi-object weight paint, the same brush strokes could affect both meshes, so they would be a lot easier to keep in sync.\n\nThe bare minimum functionality that I would consider useful:\n- Be able to select an armature then several meshes that are rigged to it, and enter weight paint mode\n- Selecting a bone activates the relevant vertex group on all meshes\n- Brush strokes affect all meshes\n- Can switch to multi-object edit mode\n- Geometry masking features work\n\nIn my personal workflow, supporting multiple armatures is not important.\nIf anyone thinks this is important, please comment with a use case example.\n\nAdditional functionality that would be nice to have:\n- Indicating active object in the 3D View. So far this hasn't been necessary, since it was always just one object.\n- Changing the active object without leaving weight paint mode. Symmetry settings are stored on the mesh, so this would be needed to be able to access those.\n- All of the above for Vertex and Texture Paint :)\n\nI tried to keep wall of text to a minimum, I hope this is not too bad @ideasman42 :)", "new boolean difference meshing issue with surfaces\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 775M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: New Boolean code - version: 2.91.0\nWorked: Old Boolean code works\n\nnew boolean code does seem to have mesh intersection issues\nwhen dealing with a solid it works better\n\nintersect to surfaces \nadd a boolean difference modifier\n\nto make it work add a solidify modifier before the boolean modifier\n\n[Boolean Issue.blend.zip](Boolean_Issue.blend.zip)\n\n\n\n\n", "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", "Keymap: custom key modifiers work inconsistently\nOperating system: Arch Linux, no DE, i3wm\nGraphics card: GTX 960\n\nBroken: 2.80\nWorked: 2.79\n\nI'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79.\n\nLoad factory settings\nImport .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move)\nEnter sculpt mode\nAttempt to sculpt inverted by holding NumpadEnter+LMB\n\n[system-info.txt](system-info.txt)\n[custom_modifier_bug.py](custom_modifier_bug.py)\n\nSimilar bugs from ages ago:\nT44349\nT34822", "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", "Weight Paint Vertex Selection Display issue\nOperating system: Linux Mint\nGraphics card: RTX 3070\n\nBroken: latest master\nWorked: never really, more on that below\n\nWhen in weight paint mode with\n* vertex selection enabled\n* show wire enabled\n\nedges will not be drawn within the selection\n\n\n**The odd part**\nClicking in an empty space will get the wires to show again, but keep the vertices selected. \nThat's a behaviour that has changed from 3.1.2 to 3.2.2\nPreviously it deselected the vertices but didn't draw the edges\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n* Open the attached blender file\n* you can see that edges are not drawn between selected vertices\n* click in an empty space (important to click, not click drag)\n* vertices stay selected but wires are drawn\n\n" ]

[ "dynamic weight paint doesnt seem to be working on both animated objects and simulated objects. Also initial colour is assigning wrong values to vertices when using dynamic vertex paint instead of weight paint.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\nBroken: version: 2.81 (sub 5)\nWorked: (optional)\n\ndynamic paint doesnt work at all when in weight mode, vertex paint mode messes up the initial colour vertex values.\n\n\n\nScene here:\n\n[dynamic paint problem upload.blend](dynamic_paint_problem_upload.blend)\n\nexplanation left to right (image above)\n\n\nLeft:\n\ndynamic weight paint doesnt appear to be working at all. check the far left tyre and ground. I've set it up so that the tyres vertices will increase in weight the closer they get to the ground, and then set up a particle system which uses the vertex weights for the particle density. Nothing appears to happen. I cant find a good way to visualise the vertex weight, I tried going into edit mode and weight paint mode, but no reaction in either. Also the particles density doesnt change as the tyre hits the floor, which is another indicator nothing is happening.\n\n\nMiddle:\n\ndynamic paint type canvas, initial colour set to vertex color results in the existing paint being in the incorrect place. (see middle sphere and plane and check vertex paint mode to see original paint, then press play in object mode to see dynamic paint incorrect representation)\n\n\nRight:\n\nIn case the dynamic weight issue was related to the current high priority bug of the physics system being broken, I also set up an animated version on the far right set to dynamic weight paint. This also results in no weight data being created by the brush (sphere) onto the canvas object (plane).\n\n\nAny chance you could also add a vertex weight option to the overlays when not in edit mode? It would be good to be able to see what's happening to multiple object's weight values at the same time\t\t (not possible in weight paint mode).", "Problem with dynamic paint with a particle setting\nOperating system: Linux-4.15.0-20-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 18.0.5\n\nBroken: version: 2.81 (sub 3)\nWorked: (optional)\n\nFollowed the following example of dynamic paint with particles \n\nwatch?v=746GAAZbG_U\n\nand was\n\n- Unable to see the weight paint effects\n- Unable to see the particles\n\n\nPlease use the following test file:\n\n[20190831_particles_dynamic_paint_0001.blend](20190831_particles_dynamic_paint_0001.blend)\n\nand follow the video to see how all parameters are setup. I believe I've been following it to the letters. Unable to explain the differences in the results.\n\n\n", "Dynamic Paint : Paint Surface Type Not working\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.16\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nDynamics Paint: Paint not working\n\nwhen one object as a brush and another object as a canvas nothing happens. Then I tried the previous blender version and it worked. Is this a bug? Or is Blender 2.8 a bit different in method so that dynamic paint requires a node shader? I hope this report can make Blender 2.8 much better. Thank you.\n\n[Report bug.mp4](Report_bug.mp4)\n\n\n\n\n\n\n\n\n\n", "Dynamic Paint weight paint mode not working?\nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.4.10\n\n\nBroken: version: 2.80 (sub 48)\nWorked: (optional)\n\n\nI'm pretty sure that the Dynamic Paint's weight paint mode is not working, unless the UX has changed in some major way and I'm not understanding the new way it is supposed to work. I can confirm that the other modes (waves, texture paint) are working, albeit the texture paint mode has also proven to be somewhat finicky for the last few months, requiring some setting and resetting to get it stable.\n\nIt should be all set up in the attached file, there is a monkey [canvas] and a cube [bush], the vertex group dp_weight has been created and nothing seems to happen, regardless of what mode I'm in - weight is not getting affected in any way that I can tell.[DynamicPaintWeightBroken.blend](DynamicPaintWeightBroken.blend)\n\n", "Weight paint not showing in Dynamic Paint\nOperating system: macOS 10.14.6, Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nHi everyone. If what I'm describing is a design decision and not a bug, my apologies for wasting your time. :) \nUnlike the previous version of Blender 2.79b, weight paint will not show in the viewport when adding Dynamic Paint physics to a canvas object. \n1) make a plane\n2) go to the physics tab and enable Dynamic Paint, then Add Canvas\n3) under 'Surface', change the Surface Type from Paint to Weight. In the old version, the plane would turn blue, and interactions between the canvas object and a brush would show up. \n" ]

[ "Blender crashes when merging mesh.vertices with a python script\nOperating system: Pop_OS 20.04\nGraphics card: Intel 4th Generation Core Proc \n\n\nBroken: 2.82a\n\n\nLink to stackoverflow question:\n\nblender-crashes-when-merging-mesh-vertices-with-a-python-script\n\nI have reuploaded the question here because I think It could be an error with blender code rather than mine. The steps to reproduce the crash would be creating an icosphere mesh, setting the max_distance variable to 0.3 and just moving nodes nearby to other ones and clicking run_script then. At some point it will close and save an ico.crash.txt. I have attached mine.\n\n[ico.crash.txt](ico.crash.txt)\n\n[#88022.blend](T88022.blend)\n\n[#88022.webm](T88022.webm)", "Blender 3.5.1 + Mac + Metal + Crash\nOperating system: MONTEREY 12.6.3\nGraphics card: AMD Radeon Pro 5500 XT 8 GB\n\nBroken: Blender 3.5.1\nWorked: Blender 3.4.1\n\nBlender 3.4.1 will render a given scene with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" in 1 min 58 sec\n\nBlender 3.5 and 3.5.1 will crash on the same scene set on \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" - \nIt has to be run with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"CP\" and now takes 5 min 53 sec.\n\nI have lost computing power with the latest versions.\n\nJust run the file with GPU BACKEND turned on and \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\"\n\nI could not include the file as it is a project I am working on - if there is no other way to check up on this issue I will try to create another file that I can send\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 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", "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```", "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", "crash while setting vertices positions using foreach_set\nOperating system: macOS-12.6.6-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 6100 Intel Inc. 4.1 INTEL-18.8.6\n\nBroken: version: 3.6.0\n\ncrash while setting vertices positions using foreach_set\n\nstart blender, run script\n\n```python\nimport bpy\nimport numpy as np\n\nl = 2 ** 28\nme = bpy.data.meshes.new('mesh')\nme.vertices.add(l)\na = np.random.random((l, 3))\nme.vertices.foreach_set('co', a.ravel())\no = bpy.data.objects.new('mesh', me, )\nbpy.context.view_layer.active_layer_collection.collection.objects.link(o)\n```\n\noutput:\n```\nWriting: /tmp/blender.crash.txt\n[1] 13339 segmentation fault /Applications/Blender/blender-3.6.0.app/Contents/MacOS/Blender\n```\n\nin blender 3.4 while using 2**27 length output is this\n```\nError: Array length mismatch (expected -402653184, got 402653184)\nError: Python: Traceback (most recent call last):\n File \"/Text\", line 8, in <module>\nRuntimeError: internal error setting the array\n```\n\ncontents of `/tmp/blender.crash.txt` is just me running script, nothing interesting\n\ninteresting bit from crash report (i can provide in full)\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x10bbaef04 foreach_getset + 1124\n1 Blender \t 0x112f45046 cfunction_call + 134\n2 Blender \t 0x112f01015 _PyObject_MakeTpCall + 373\n3 Blender \t 0x112fdf95b call_function + 971\n4 Blender \t 0x112fdbc41 _PyEval_EvalFrameDefault + 24817\n5 Blender \t 0x112fd5a22 _PyEval_Vector + 146\n6 Blender \t 0x112fd5978 PyEval_EvalCode + 120\n7 Blender \t 0x10bb9cd2a python_script_exec + 506\n8 Blender \t 0x10c6754b0 text_run_script + 64\n9 Blender \t 0x10b600ce6 wm_operator_invoke(bContext*, wmOperatorType*, wmEvent const*, PointerRNA*, ReportList*, bool, bool) + 582\n10 Blender \t 0x10b600a03 wm_operator_call_internal(bContext*, wmOperatorType*, PointerRNA*, ReportList*, wmOperatorCallContext, bool, wmEvent const*) + 515\n11 Blender \t 0x10b602025 WM_operator_name_call_ptr_with_depends_on_cursor + 165\n12 Blender \t 0x10c36bffd ui_apply_but_funcs_after(bContext*) + 285\n13 Blender \t 0x10c366fc2 ui_handler_region_menu(bContext*, wmEvent const*, void*) + 434\n14 Blender \t 0x10b604a4f wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*) + 1007\n15 Blender \t 0x10b604020 wm_handlers_do(bContext*, wmEvent*, ListBase*) + 48\n16 Blender \t 0x10b6033ba wm_event_do_handlers + 2554\n17 Blender \t 0x10b5f91b0 WM_main + 32\n18 Blender \t 0x10adea41e main + 878\n19 dyld \t 0x12788152e start + 462\n```\n\n", "GPencil: Selecting textured brushes will crash Blender\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92.0\n\nWhen appending the textured brushes from the [Blender Cloud](5ccfe64353b85e279cf72acd) into a file, Blender will crash when trying to preview the brushes in the tool settings.\n\n\n - Open Blender 2.93 and select the \"2D Animation\" template.\n - Go to *File*>*Append* and browse to the `pepeland_GP_brush_pack_V1.blend` file. Go into the *Brush* folder and append the brushes `GBrush_001` through `GBrush_010`.\n # Click the brush icon in the tool settings. Blender crashes.\n\n\n\n", "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", "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", "Broken textures and shading\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nBroken textures when starting up blender and loading object textures and shading issues\n\n[Blender Texture Bug.mp4](Blender_Texture_Bug.mp4)\n\nPossible causes:\n * Not loading the parent asset blend file before the asset in another scene (opening it first seems to fix the issue in my testing) \n * 4k textures (i've heavily used 4k textures in the asset)\n * Viewport Texture size limit setting (Changed it to 2k)\n\n\n[untitled.blend](untitled.blend)\n", "Frequent render crashes in 3.5\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5500M 1.2\n\nBroken: version: 3.5.0\n\nI've been encountering a lot of crashes in 3.5 when rendering in the background. Meaning I start a rendering, and move over to something like a browser. At random time Blender 3.5 just crashes. I've included a crash log file.\n\n\n", "Crash with Boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.1.2 (appears to have been broken since 3.2.0)\n\nBlender crashes when performing an Intersection Boolean between a cube and a bunch of loose faces. (Granted, this is probably not something you should do in the first place, but at least it should be limited to producing a bad result, not a crash.)\n\nI didn't find a crash log, but it's easy to reproduce.\n\n* Load the attached .blend file.\n* Scrub the timeline to frame 209. Blender crashes.\n\n[crash.blend](crash.blend)\n", "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)", "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)" ]

[ "Regression: Recent MPoly refactor causes crash during FBX or 3DS import\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.6.0 Alpha\nWorked: versions before 7966cd16d6dc4e66d01f7bd68a090107c1a7978c\n\nCaused by 7966cd16d6dc4e66d01f7bd68a090107c1a7978c\n\nSome files, FBX or 3DS, that could be successfully imported before 7966cd16d6dc4e66d01f7bd68a090107c1a7978c will now cause the following crash:\n\n```\nStack trace:\n blender::bke::mesh::mesh_edges_sharp_tag C:\\Users\\jesse\\source\\blender-git\\blender2\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:746\n blender::bke::mesh::normals_calc_loop C:\\Users\\jesse\\source\\blender-git\\blender2\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:1490\n blender::bke::mesh::mesh_normals_loop_custom_set C:\\Users\\jesse\\source\\blender-git\\blender2\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:1572\n blender::bke::mesh::mesh_set_custom_normals C:\\Users\\jesse\\source\\blender-git\\blender2\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:1842\n rna_Mesh_normals_split_custom_set C:\\Users\\jesse\\source\\blender-git\\blender2\\source\\blender\\makesrna\\intern\\rna_mesh_api.c:140\n RNA_function_call C:\\Users\\jesse\\source\\blender-git\\blender2\\source\\blender\\makesrna\\intern\\rna_access.cc:6295\n pyrna_func_call C:\\Users\\jesse\\source\\blender-git\\blender2\\source\\blender\\python\\intern\\bpy_rna.c:6440\n\n# Python backtrace\n File \"C:\\Users\\jesse\\source\\blender-git\\build-lite2\\bin\\RelWithDebInfo\\3.6\\scripts\\addons\\io_scene_fbx\\import_fbx.py\", line 1568 in blen_read_geom\n File \"C:\\Users\\jesse\\source\\blender-git\\build-lite2\\bin\\RelWithDebInfo\\3.6\\scripts\\addons\\io_scene_fbx\\import_fbx.py\", line 2844 in _\n File \"C:\\Users\\jesse\\source\\blender-git\\build-lite2\\bin\\RelWithDebInfo\\3.6\\scripts\\addons\\io_scene_fbx\\import_fbx.py\", line 2845 in load\n File \"C:\\Users\\jesse\\source\\blender-git\\build-lite2\\bin\\RelWithDebInfo\\3.6\\scripts\\addons\\io_scene_fbx\\__init__.py\", line 207 in execute\n```\n\nThis is a complicated example and it's not clear if its Blender importers' fault, the FBX or the 3DS file's fault.\n\n- Import attached 3DS file or download the \"Zero-Day\" FBX from beeple-zero-day (`MEASURE_ONE.fbx`) with default settings\n\nShould crash after import\n\n\n\n----\nThere's complicating factors though. Looking into the FBX importer, it is calling `Mesh.validate` for every incoming mesh. This is fine, except that for this file, _every_ mesh is considered invalid and Blender is fixing things up behind the scenes:\n- Can the importer itself generate better meshes to begin with or is the file itself problematic?\n- Is this the root of the problem, an aggregating factor, or just a red-herring?\n - Ultimately the crash happens a few lines after validate when doing: `mesh.normals_split_custom_set(tuple(zip(*(iter(clnors.data),) * 3)))`\n\nIn any case, this is a prominent graphics research file that no longer loads. If it's broken we should notify nVidia. If it's not, then we'll have to fix our stuff.\nThe mesh called \"Mesh.1166\" is the first problematic one that causes the crash - I modified the FBX importer to provide tracing around the mesh in question:\n```\n...\n...\nMesh 'Mesh.1163' validate result is True!\nMesh 'Mesh.1164' validate result is True!\nMesh 'Mesh.1165' validate result is True!\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 0 has invalid edge reference (0, is_removed: 0), fixed using edge 4\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 0 has invalid edge reference (0, is_removed: 0), fixed using edge 6\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 0 has invalid edge reference (0, is_removed: 0), fixed using edge 1\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 1 has invalid edge reference (0, is_removed: 0), fixed using edge 6\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 1 has invalid edge reference (0, is_removed: 0), fixed using edge 2\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 2 has invalid edge reference (0, is_removed: 0), fixed using edge 5\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 2 has invalid edge reference (0, is_removed: 0), fixed using edge 3\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 2 has invalid edge reference (0, is_removed: 0), fixed using edge 2\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 3 has invalid edge reference (0, is_removed: 0), fixed using edge 7\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 3 has invalid edge reference (0, is_removed: 0), fixed using edge 1\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 4 has invalid edge reference (0, is_removed: 0), fixed using edge 2\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 4 has invalid edge reference (0, is_removed: 0), fixed using edge 4\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 4 has invalid edge reference (0, is_removed: 0), fixed using edge 7\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 5 has invalid edge reference (0, is_removed: 0), fixed using edge 2\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 5 has invalid edge reference (0, is_removed: 0), fixed using edge 3\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:659 BKE_mesh_validate_arrays: Poly 5 has invalid edge reference (0, is_removed: 0), fixed using edge 5\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:698 BKE_mesh_validate_arrays: Polys 5 and 2 use same vertices (1\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:700 BKE_mesh_validate_arrays: , 3\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:700 BKE_mesh_validate_arrays: , 4\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:702 BKE_mesh_validate_arrays: ), considering poly 2 as invalid.\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:743 BKE_mesh_validate_arrays: Loop 6 is unused.\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:743 BKE_mesh_validate_arrays: Loop 7 is unused.\nERROR (bke.mesh): <a long path>\\mesh_validate.cc:743 BKE_mesh_validate_arrays: Loop 8 is unused.\nMesh 'Mesh.1166' validate result is True!\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF698DF7E63\nModule : blender.exe\nThread : 00004b68\nWriting: C:\\Users\\jesse\\AppData\\Local\\Temp\\blender.crash.txt\n```\n\n" ]

[ "Very slow interaction with Armature, if GPU Subdiv is enabled\nOperating system: Ubuntu 20.04\nGraphics card: Gefore MX230\n\nBroken: 3.3, 3.2.2\n\nwith the enabled GPU Subdivision, interactions with the armature are much slower than with the disabled\n\n[2022-10-23 13-29-00.mp4](2022-10-23_13-29-00.mp4)\n\nmove the bones with GPU Subdivision on and off\n[kira_lite.blend](kira_lite.blend)", "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n", "Blender 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", "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", "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", "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)", "Depsgraph integration of physics\n- [ ] Rigid body\n- [ ] Fluids\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", "Crash when rendering (Apple M2)\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: version: 3.6.2\n\n[Rendering with GPU (metal) works fine without fire simulation, with fire simulation the render crashes, while rendering in the viewport is no problem.]\n\n\n", "Crash Guide during render complete 2 December 9, 2022\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.4.0\n\nCrash Guide during render 2\n\nSame crash guide during render before and today.\nSee youtube: ZeCA2p5wISY\n\nHistory previous.\nT100691\n\n\n\n\n[Blender-2022-12-09-161546.ips](Blender-2022-12-09-161546.ips)\n\n[Horizontal Video.zip](Horizontal_Video.zip)", "Intel (R) HD graphics 4600 also has the problem of cubemaps shows black\nIntel (R) HD graphics 4600 also has the problem of cubemaps shows black\n\nSystem Information\nOperating system: windows7 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 3.4.0 - Build 10.18.14.5117\n\nBlender Version\nBroken: since 2.83.3 branch: master\nCurrent broken: 2.93.7\nWorked: 2.82a\n\nShort description of error\nLike #75943 and #79158, HDRI cannot be displayed normally\n\nCan be resolved adding \"**HD Graphics 4600**\" to the blacklist\n\nComment from #79158: \"*I'm not sure whether Intel's graphics cards are like this. Can you put this repair method in preferences as an option?*\"\nOr perhaps adding command line flag like: **--disable_texture_cube_map_array**", "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", "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", "Constrained [on an axis] transform of an object far out of view can result in insanely high numbers\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.09\n\nBroken: version: 3.0.0\nWorked: never\n\nConstrained [on an axis] transform of an object far out of view can result in insanely high numbers\n\nThis file just contains a single cube 250m away from the origin:\n[#94105.blend](T94105.blend)\n- open file\n- hit {key G Y}\n- start moving the mouse\n- see values of 1000000000 m in the header\n\n**Original report**\n\nYour camera has to be close enough as in the attached video. Press G+Y and do a little move. The Cube starts to ignore modifiers and drastically increase Y-axis numeric value.\n[bug_10.mkv](bug_10.mkv)\n[bug_10.blend](bug_10.blend)", "MetalRT: Rendering being unresponsive with AO node\nOperating system: Ventura 13.4.1\nGraphics card: Apple M1 Max 32 Core\n\nBroken: Blender 3.6 LTS\nWorked: Blender 3.5.1\n\nAfter downloading the newest Version of Blender it seems that using the Ambient Occlusion Node need leads to Blender being unresponsive. Sample count stays on 0 and neither Viewport nor F12 Render is starting as expected. Trying to quit, Blender crashes completely.\n\n- Add new material\n- Add Ambient Occlusion Node\n- Select cycles and GPU\n- Enable MetalRT\n- Start Viewport Rendering.\n\n" ]

[ "Overheating -- GPU @ 74% (macOS + AMD Radeon)\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 48 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.90.0\n\n\nit happens every time something is selected in edit mode--even something small in number of edges like a detail in Edit Mode after hitting /.\nIt doesn't seem to be noticeable at first because it takes a minute to build the heat to get the fan getting louder. The thing is to watch the Activity Monitor and it immediately jumps to above 80% GPU usage with X-RAY and SOLID selected at the same time. I LOVE this mode combo and would like to use it (a thing of beauty) but my system flames out.\n" ]

[ "Cycles freeze on render and texture baking (with packed textures)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.83\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nBlender freezes on render\nBlender also freezes on texture bake and rendered viewport\nTried on 3 different PCs, all the same\n\nIf textures are unpacked, rendering is fine.\n\nSimply open attached .blend file and hit F12\n\n[render_test2b_delmesh3_simplified.blend](render_test2b_delmesh3_simplified.blend)", "Subdivided surface preserves mesh UVs and vertex colors when not needed\nThis code causes UVs and vertex colors to always be preserved through the modifier stack.\n\n```\n /* this wasn't in 2.63 and is disabled for 2.64 because it gives problems with\n * weight paint mode when there are modifiers applied, needs further investigation,\n * see replies to r50969, Campbell */\n#if 0\n CustomData_set_only_copy(&dm->loopData, mask->lmask);\n CustomData_set_only_copy(&dm->polyData, mask->pmask);\n#endif\n```\n\nFor simple solid shading these are not needed, and `ED_view3d_datamask` should take care of requesting them when needed, taking up memory and CPU time.\n\nHowever, there is currently an issue where switching shading modes does not reevaluate the dependency graph to add these data layers, so just re-enabling this code is not enough to fix this. See also #63595 (Generated texture coordinates missing when switching from solid to rendered mode).", "Unusable display with AMD driver errors.\nOperating system: Ubuntu 22.04.2 LTS/Kernel version 5.15.0.75/FOSS amdgpu driver(default)\nGraphics card:MSI Radeon RX580 8GB\n\nBroken: 3.5.1, 3.1.0\nWorked: 3.1.0(Did not experience this until recently)\n\nWhen editing UV GPU gets reset after errors, the compositor does not recover. Garbled image on the screen with displays unusable. Log data attached.\n\nThis happens when pressing .(dot) on the keypad, selecting or moving a UV.\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", "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", "High subsurface on principled bsdf causes glowing edges on polygons for walk\nBroken: Current main.\nWorked: Never.\n\nUsing high values for principled bsdf subsurface scatter causes glow effect on polygon edges. This happens with walk but not burley. \n\nAttached is a simple blender scene with a ball. Rendering you can see the squares polygons on the ball have glowing edges. I know that the walk radius calculations were changed around blender version 3.4. If you use burly the ball renders smooth. \n\nGraphics - set to optix, experimental, cycles.\nShape - make sure its set to smooth shading. You may have to recreate the stock sphere and set it to smooth shading.\n\n", "UV: Copy/Paste UVs sometimes merges vertices\nOperating system: Windows 10\nGraphics card:\n\nBroken: 3.5.1, 3.6.0 (2023-05-24), 4.0.0 (2023-05-24)\n\n\nCopy/Paste UVs sometimes merges vertices.\n\nTest file: [UV - Copy Paste.blend](attachment)\n\n\n\n", "straighten edges and unfold uv island\nStraighten selection and unwrap unselected vertices\n\n**Starting point**\n\nThe uv has pretty wonky topology. \n\n\n\n\n**Desired result**\n\nThe selection is straightened and the non selected uv’s of the UV island is unwrapped. Should work on multiple uv islands\n\nSuggested approach:\n- Store\n - Original pinning\n - Original seams\n- Run “seams from islands”\n- Remove all pins\n- Pin selection\n- Align auto on selection\n- Unwrap\n- Restore \n - Original pinning\n - Original seams\n\n\n", "Remesh modifier causes splitting wrongly\nWindows 7 Professional Service Pack 1 64-bit\nIntel Core i7-2600 3.40GHz\n8GB RAM\nNVIDIA GTX560\n\nBroken: 2.77 22a2853\n\nRemesh modifier causes splitting wrongly.\nIt happens when remesh modifier's scale value is 3/4, 1/2, 3/8, 1/4, 3/16 etc.\n\n[RemeshGlitch.blend](RemeshGlitch.blend)", "Remove DerivedMesh: subsurf-uv unwrap\nCurrently UV unwrap uses derived mesh, see: `construct_param_handle_subsurfed`", "percent bevel by weight doesn't work properly\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\npercent bevel by weight doesn't work properly \n\n\n\n", "Bevel assign vertex to another vertex group (BUG)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\n\nBevel assigns a new vertex to another vertex group.\nCreate mesh\nadd 3 vertex groups\nadd 3 bevels\nchange amount of 1st bevel when its be ~50% from length edge bevel add a new vertex to all groups\n\n\n[Bevel_Bug.blend](Bevel_Bug.blend)\n\n", "Vertex weight not carried through bevel modifier\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4080 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.4.1\n\nVertex weight not carried through bevel modifier in some cases\n\n\n[105012.blend](attachment)\n- open blend\n- apply visual geometry on the `good` object\n\n- apply visual geometry on the `bad` object\n\n\n\n\nOK, some more testing (which solves the issue at least on the example I posted [also if there is a second bevel modifier with custom profile on there] -- as well as to some degree for the original file as well [which is posted below]):\n\n- open the file\n- go into editmode on the `bad` object\n- select all **edges** (edge select mode)\n- `Mesh` > `Sort Elements` > e.g. `Cursor Distance`\n- voila!\n\n-----\n\n\n\n**Original report**\n\nWhen wishing to create a bevel with the modifier on a specific vertex group aftern another Bevel modifier, the vertex group does not carry over.\n\n\n* Create a geometry\n* Mark some edges to bevel with bevel weight set to 1\n* Add an edge loop in to a vertex group\n* Add a bevel modifier and use Weight\n* Add 2nd bevel modifier and use vertex group. The area where the first Bevel modifier has been executed does not become incorporated into the vertex group\n\n\n\n\n\n\n\n\n", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "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." ]

[ "Bevel modifier causing zero area faces\nOperating system: Windows 10 64-bit (Build 19043)\nGraphics card: Nvidia RTX 3070\n\nBroken: 3.0.1, 3.1.2\n\nWhen applying a bevel modifier it sometimes causes zero area faces:\n\nIt seems it places two vertices on the same location which then causes the triangle to become a flat line.\nThis happens with a default cube unwrap without any user defined seams so I'm not sure if it counts as the same bug as [this one ](T56625)\n\nThese zero area faces cause issues in unreal and makes the non-destructive approach with modifiers impossible since you need to apply the modifier and then unwrap the mesh afterwards to get workable UVs\n\n\n\n\n # Create a cube\n\n # Add bevel modifier\n\n # Apply bevel modifier\n\n # Look at the UVs, they should now appear as pictured above, broken\n\n", "UV Seam Issues with Bevel Miter Outer Arc setting On\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.0\n\nWhen Using the Bevel Modifier with \"Miter Outer\" on Arc, it creates an offset of the UV Seam and so an artefact of the Texture.\nWhen applying the modifier, we can see that the Seam has offset from one polygon.\n\n- Create on object with a stair like shape\n- Add a Bevel modifier to it\n- Change the \"Miter Outer\" setting in the \"Geometry\" tab from \"Sharp\" to \"Arc\"\n- UV Unwrap the Stair like shape (with seams, but it also works with Smart UV Project\n- Add a UV Grid to a texture and scale the UVs to have a better understanding of the issue\n\n\n\n[Bevel_Arc_Bug_Report.blend](Bevel_Arc_Bug_Report.blend)\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", "Blender 2.79b bevel messes up texture UV coordinates.\nBroken: 2.79b\n\nWhen bevelling something with texture coordinates, it usually looks really weird.\n\nSee attached.\n\nTop left: unbevelled\nTop right: 2-segment bevel modifier\nBottom left: 4-segment bevel modifier\nBottom right: What it should have looked like — 4-segment bevel modifier applied and then manually fixed up\n\nSometimes coordinates can be fixed by scaling them by a factor of 3 with the cursor set to the coordinates of another face.\n\nScreenshot:\n\n\nTest case:\n{[F6658142](bevel.blend)}\n" ]

[ "Color Attribute not affecting \"bump\" shader node\nOperating system: Windows 10\nGraphics card: RTX 3080\n\nBroken: 3.50 beta (03 March 23)\n\nUsing a mesh's color attribute as an input to the \"bump\" shader node does not result in the expected behavior. Using the color attribute for practically every other value (including the normal map node, roughness, metalness etc.) works as expected.\n\nCreate a mesh and paint a color attribute with, for example, a black-and-white pattern.\nGive the mesh a material and add the color attribute.\nPlug the color attribute into the \"height\" input of the bump node, and view the result. There is no difference compared to the \"height\" input being left disconnected.\n\nOther inputs (such as a noise texture) result in the expected behavior.\n\n", "Cycles GPU CUDA rendering high number of points seems broken in LTS (main is fine, request for backport)\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.3.3\nWorked: latest 3.5 alpha\n\nRendering point \"clouds\" with Cycles - CUDA seems to make some chunks of points disapear randomly\nThis looks like this has been fixed in 3.5, but i didn't find when. Can this be fix in LTS ?\n\nDelete the default cube and add a plane\nAdd a Geonode Modifier on that plane\nDistribute Points on Faces > Density : 250'000\nSet Point Radius > 0.0025 (for convenience)\n \nSwitch to Cycles, GPU\nSwitch the render device to CUDA\n\nResults with :\n\n|  CPU |  CUDA |  OPTIX\n| -- | -- | -- |\n\n\n\nBug is visible in both viewport shading and Render.\n\n", "crash when changing viewport shading to wireframe mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14760 Core Profile Context 21.2.3 27.20.14535.3005\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-04-23 20:25, hash: 17fca62fff9b, type: Release\nBroken: 2.81\nWorked: 2.80\n\n\nif you have a high poly mesh and try change the shading mode to wireframe. depending on the model it constantly crashes.\n\n\nI noticed this trying to make a retopo of a character. I tried to check what was causing de crash by deleting each object and testing the wireframe. \n\nI deleted everything but the main body mesh, without any uv map, vertex color or any other thing that could make it heavier, and also I tried reseting factory settings.\n\nI would send the file but its 200mb, the main mesh has about 4million vertices.\n\n\nthe crash doesn't happen when changing to eevee or solid view, it only happens when changing to wireframe.\n\nImportant note: if you DON'T move the camera after opening the file before changing to wireframe it doesn't crash even if you go to solid and wireframe back and forth as shown in the video bellow \n[2021-05-01 14-18-16.mp4](2021-05-01_14-18-16.mp4)\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[untitled.blend](untitled.blend)\n- open the file above\n- rotate it about 180degrees\n- activate wireframe", "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", "Aliased wireframes + modifier edit mode display issue\nOperating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 3.4.1\n2.90\nWorked: 2.79, 2.81\n\nEdit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range.\n\n**Steps to reproduce**\n\n* Open file\n* Disable all anti-aliasing and smoothing in preferences > Viewport > Quality\n\nSelection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.", "Debug build BM_mesh_triangulate() will hang forever if mesh face count is high.\nOperating system: Xubuntu 20.04\nGraphics card: NVidia K5100M\n\n\n**Broken ONLY WITH `Debug` build**: Blender 3.0.0 Alpha (It should have been broken way earlier)\nWorked only with `Release` and 'RelWithDebInfo' build: Blender 3.0.0 Alpha\n\n\nThe call to `BM_mesh_triangulate(bm, quad_method, ngon_method, 4, false, NULL, NULL, NULL)` does not exit on some bigger meshes. Specifically, it seems to have been stuck inside `BM_face_kill(bm, faces_double->link);`.\n\n(if you call it with bmesh `op` and `slot_in/out` arguments it will run properly)\n\n\n1. Open 0_rougue_bucket.blend provided below.\n2. Add -> GPencil -> Scene Line Art **OR** go into sculpt mode and enable dynatopo (where it uses the same triangulation call).\n\nOn my machine the bucket runs fine with subdiv levels 1-2 and above 3 the bug shows. The subdiv value in that file is 3.\n\nNote that the bug is only reproducible in `Debug` build. Seems that function doesn't like meshes that has face count higher than a certain amount...\n\nMy guess would be there's a lot of checks in debug code path in the function, somewhere it reaches a case where the memory pool gets corrupted. It never quits, in the task manager, memory doesn't show any changes at all. (It's way below my 32G system memory so it can't be there being not enough memory).\n\nSince this triangulation call is related to sculpt as well so I'm gonna ask if this happens to @PabloDobarro in debug build...\n\n[0_rouge_bucket.blend](0_rouge_bucket.blend)\n\n", "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", "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", "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)", "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).", "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)", "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.", "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)", "Design: Shading: Extend Clamp and Map Range nodes to work with Vectors\nI'd like to make these nodes work with vector inputs and outputs.\n\nIt's unclear to me as the the best way of doing this. \n\n\n\nSome options:\n\n - **Separate Nodes** : Create separate versions of these nodes with Vector sockets.\n\n - **Dynamic** : Use a dynamic socket. This is better from a UX perspective but how do we show this? For these two nodes, they are pretty pointless without a value input so the edit control could be hidden. The node then operates accordingly depending on the input link. \n\n\n\n- **Mode Switch** : Add vector input and output sockets and add a mode switch to hide the unwanted input socket. \n\n- **Double Sockets** : Add vector input and output sockets and depending what is connected. For vector only input, `Vector` > `Float & Vector`. For float only input, `Float` > `Float & Vector`. If both inputs are connected do `Float` > `Float` and `Vector` > `Vector`.\n\nFor the combined cases, the node would output and show both Value and Vector.\n\n\n\n\n\n\n\n", "Cycles rendered 3DViewport massive performance drop, using lights with node groups. --Intel MacOS--\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 4.0.0 Alpha\n\nSee screenrecording video! \nWhen switching to a light with nodegroups in Cycles rendered 3DView, performance drops a big time. (~50%).\n\n1. Open the performance.blend file with Intel MacOS blender 4.0, switch to cycles rendered 3DView, select the cube and rotate the view.\n2. Then switch to the caustic light and try to rotate the view again." ]

[ "Blender 2.78 can't render a plane with subdivision surface, displacement modifier & normal map on it\nOS: Windows 10\nGPU: GTX 1080\nCPU: intel i7 5820k\nRAM: 32gb\ndrivers: GeForce Game Ready Driver version 372.90\n[system-info.txt](system-info.txt)\n\nBroken: 2.78\nWorked: 2.78 release candidate v2\n\nBlender cycles won't render a subdivided plane with displacement modifier & normal map on it. The program goes unresponsive or gets stuck when using either GPU or CPU to render it & won't close unless closed from task manager. I rendered a scene that had the same plane in it with 2.78 release candidate v2 and it worked fine.\n\nOpen the .blend file, press render and it won't render the image. If you use the preview render in viewport, it will say Blender is not responding at the top left corner. You can't cancel the render either.\n[BUG.blend](BUG.blend)\n\nAdd a plane, scale it up > CTRL+A > appply scale. subdivide it 100 times in edit mode using w > subdivide. Add a subdivision surface with subdiv level 2 or 3. Then add a displacement modifier & a 4k displacement texture. It will still render it just fine. Then add a diffuse material. Add a normal map node & an image texture node with non-color data. Add a 4k normal map texture to the image texture node & connect it to the normal map's color input. Then connect the normal map node's output to the normal input of the diffuse shader. Try to render the scene > it gets stuck and won't render. If you change the viewport to rendered, blender stops responding & you have to close it from task manager.\n[reproduced_bug.blend](reproduced_bug.blend)" ]

[ "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)", "Crash when baking Dynamic Paint Image Sequence multiple times in loop\nBroken: 2.90.0 Alpha\nWorked: blender-2.80-windows64\n\nBlender crashes when baking dynamic paint image sequence in for loop. Depending on wait time crash will have differens stack traces.\n\n[#74052.blend](T74052.blend)\n\n- Open file\n- Run script", "Blender 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", "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```", "Blender crashes if simplify is turned on while baking multires\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: --\n\n\nBlender crashes if simplify is turned on while baking multires data\n\n\n- Grab any object and add multiresolution to if, subdivide at least once.\n- Activate simplify, and turn the max subdivisions on viewport to 0\n- Create a material and try to bake the multiresolution. Blender will crash instead of giving an error message or just baking normally \n\nTest File:\n[multires_crash.blend](multires_crash.blend) ", "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 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 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)", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "Blender crash 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.", "Blender hangs on Intel UHD 620 when switching to lookdev mode\nOperating system: 'Windows-10-10.0.19044-SP0'\nGraphics card: Intel UHD 620\n\nBroken: 3.5.1\n\n\nBlender hangs on when switching to lookdev/render mode on even simple shaders.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open crasherexample.blend on an Intel UHD 620 (Dell Inspiron 3581)\n2. This will be in solid preview mode in Shading view.\n3. Switch to lookdev mode. Blender hangs (Task Manager shows high CPU percent usage on the process, which goes down to zero percentage after a few seconds, after which Blender refuses any interaction).\n4. Use Task Manager to kill Blender. Now restart Blender and reopen crasherexample.blend which will be in solid preview mode in Shading view.\n5. Use Node Wrangler right-click drag to cut the Normal, Roughness, Displacement noodles. Leave just Base color noodle.\n6. Switch to Lookdev mode. It works! Now reconnect Normal noodle too. Switch to Lookdev. It works! Now reconnect Roughness noodle too. Switch to Lookdev. It works! Now reconnect Displacement noodle too. Switch to Lookdev. It works! Yet if you immediately switch to lookdev mode as did in step 3, it hangs. \n\nResult is opening/importing just about any file in Blender causes a hang. Not just crashexample.blend. Nearly any shader however simple causes this. But crashexample.blend file works fine on non-Intel UHD 620 PCs.\n\nWe've been plagued by this bug ever since Blender 2.8. Tried every version of the driver (Dell and Intel), but none ever fixed it. Result is we can't safely switch to lookdev/render mode on these PCs. Tried investigating and suspect perhaps a race condition related to shader compilation. Loading a typical Blender file begins with a message like eg '(some number) shaders to compile', and it hangs.\n\nThis only happens in EEVEE. Cycles is fine.", "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", "BMesh.free causes crash under curtain conditions\nOperating system: Linux-5.16.16-200.fc35.x86_64-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.0 Alpha\n```\nall 3.x versions are broken, 3.0.0 sometimes works\n```\nWorked: 2.93.8 LTS\nOn Fedora also some 2.91 versions have been affected, according to rebuild agains newer pythons.\nReported on redhat bugzilla: show_bug.cgi?id=1872980\n\n[blender.crash.txt](blender.crash.txt)\nUsing my python addon blender crashes on _PyEval_EvalFrameDefault or _Py_Dealloc.\n\nUnable to describe simple steps to reproduce. This happens using my python addon, but if a bug is in addon, still shouldn't crash blender but throw an python traceback.\nWhen I delete line describen in crash log's backtrace, then another row is marked as a problem, so unable to identify exactly what's happening.\nPlease, let me know, if you need more information.\n\n----\n\nEdit, run this script with the following command line arguments: [boxmaker_crash_single_script.py](boxmaker_crash_single_script.py)\n`blender -b --factory-startup --python boxmaker_crash_single_script.py`\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", "Texture Node editor --->creating image , then use created image as input node in texture node editor \nwin 10 \namd radeon \nintel i5\n\n Blender 2.8\n3d8cbb534f82\n\n\n First of all ,this is specifically about the \"texture node editor set to brush for creating an image , then using the created image as an image input in the (brush ) node editor , and again paiting in the SAME image ...\nIt totally makes sens that blender crashes because it is trying to create an image where the brush is that image itself , thus creating a feedback loop \n\n\nSteps to reproduce crash\n\n\n- Create plane \n- Go to the shader editor and create an image texture node \n- Create a new file , let's call this one ''crash'' and route it the shader's colour input \n- Go to the 'texture node editor and from the dropdown select 'brush''\n- Click the 'new tab' and enable úse nodes , by default we are presented with the checker pattern \n- go to the image editor and draw something , we are presented with a checker pattern \n- Now go back to the texture node editor'' and select ímage 'from the input nodes and route it to the tout\n- Select çrash 'as image \n- Now paint something in the image editor \n\nCrash \n\nIn the provided file , everything is already set up , al you have to do is paint in the image editor , and then route the module labeled çrash'to the output of the texture node editor [feedback crash .blend](feedback_crash_.blend)\n\n " ]

[ "VSE Editor crash when opening a different scene as a strip\nOperating system: Windows 10\nGraphics card: RTX 2080 Ti\n\nBroken: 2.9 Beta (8-19-20)\nWorked: 2.9 Beta (8-17-20)\nCaused by 47c6f41b89\n\nBlender crashes when opening a different scene as a strip in VSE editor. Also crashes if you try to open a blend file that uses a scene as a strip in the VSE editor.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Open a default startup Blender file.\n2. Open up the Video Editing workspace\n3. Create a new scene, can do new, copy settings, doesn't appear to matter.\n4. Shift+A in the sequencer\n5. Scene->Scene (Or whatever your default scene name is)\n6. Crash", "Blender becomes unresponsive (spinning beachball) when adding a scene to the VSE\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.91.0 Alpha\nWorked: version: 2.91.0 Alpha\n\nWhen adding a scene to the VSE blender becomes unresponsive.\n\n* Open attached .blend\n* In the VSE menus use Add>Scene>Scene1\n* Blender becomes unresponsive with spinning beachball.\n\n[VSEbug.blend](VSEbug.blend)\n\n" ]

[ "Cycle crash\n[System Information](https://projects.blender.orgattachment)\n\nBlender version: 3.4.1\n\nCrash when switching from Material Preview to Rendered in Viewport Shading and GPU Compute was set for Cycles. In CPU mode it's OK.\n\n\nOpen project.\nSelect CPU in Cycles settings.\nSwitch from Material preview to Rendered in Viewport shading.\nNow it works.\nChange to GPU Compute in Cycles settings.\nCrash...\n\n", "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", "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", "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 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.", "Blender 3.4 Random Crashing Since GPU Replacement\nOperating System: Windows-10-10.0.19044-SP0\nGPU: NVIDIA GeForce RTX 3060/PCIe/SSE2 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0, branch: blender-v3.4-release\n\n**Short Description**\nI have replaced my RX580 with an RTX3060 earlier and ever since that replacement, I have been having constant crashes whenever I attempt to use Blender, do note that I've been in edit/object mode during these crashes as I'm working on a subd model, I have tried a handful of fixes such as upping TDR values but it didn't seem to fix the issue.\n\nRyzen 5 2600, RTX3060, 16gb RAM, no temperature exceeds 60 degrees Celsius and nothing is active besides Blender 3.4 along with addons I have installed.\n\nHere are the logs I get when I run Blender via the gpu debug cmd: \n\nEdit: I did try disabling UV Packmaster as per the error logs, but that didn't stop the crashing.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[gunflipped.crash.txt](gunflipped.crash.txt)", "Crash when rendering animation in Workbench (with workbench shadows)\nOperating system: Windows 10 20H2\nGraphics card: Nvidia GTX1080\n\nBroken: 2.93.0\nWorked: 2.92.0\n\nWhen rendering the attached file as animation Blender ends without notice after the second rendered frame.[mirandaAnimNeu3.blend](mirandaAnimNeu3.blend)\n\nOpen the file mirandaAnimNeu3.blend. Click Render | Render Animation.\n\nThe animation is set to start at Frame 466 and to last until frame 4900. After rendering of frame 467 Blender crashes without notice. No crash file is created. Blender just ends.\n\nBoth rendered images are saved. It is interesting to note that the earlier images of this animation are rendered within seconds but the render times of the last images require minutes although no noticeable content becomes visible. Yesterday I have rendered all 4900 frames at 50% size without anti-aliasing, which worked fine. Each image rendered in a second or two.\nSorry that the blend-file is so big...", "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", "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)", "Blender 2.91 alpha - Debug menu, instant crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90.1\n\nShader compilation is causing an error when the debug menu is invoked on a blank scene or working scene.\n\nOpen the .blend attached file, press F3>search: Debug. Type 22 (eevee GPU speed benchmarking verbose),\nBlender will crash immediately. The same is true on a blank new scene in the general application template.\n\nFile to test: \n44cb6eb461af31ad1209dedb738d76c0.blend\n\n", "Cycles GPU Compute 5000 x 5000 pixels render F12 crashes\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 Alpha\n\nCycles GPU Compute 5000 x 5000 pixels render F12 crashes\n\nMacOS 13.5\nSee youtube about Blender crash guide during 5000 x 5000 pixels.\n\nNot matter both same crash Blender 3.6.3 and 4.0\n\n", "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", "Render Audio\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nIn the Video Editing mode, when using Render Audio, the program title bar shows: Not Responding.\nBut Blender actually completes the render audio process after a couple of minutes.\n\nOpen Blender, select Video Editing Mode and import video file with audio.\nClick display Wave form and set audio to mono.\nSelect Render - Render Audio and use mp3 container, Format: S16 and 128 as bitrate.\nEnter a file name and click \"Mixdown\"\n\nThe Blender title bar shows that the program is not responding, but after a couple of minutes the audio file finish rendering and works just fine.\n\nYou can find a screen capture of the event attached, showing the title bar \"Not Responding\" and also the RAM and CPU values at the time.\nAlso attached is the blender file. (I just removed the video parts.\n\nThank you all for the best 3D software in the world!\n\n\n\n", "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" ]

[ "Blender 2.91 crashes if I load a blend-File or try to map a UV-Texture on a face.\nOperating system: Windows 10\nGraphics card: RTX 2080 TI\n\nBroken: Blender 2.91.0\nWorked: Blender 2.80\n\nBlender crashes if I try load a Mesh (.blend file) The same Blend File is working on Blender 2.80\n\nOpen the .blend-File in Attachement I added to this report...[GGT-ATM1.blend](GGT-ATM1.blend)\n\nLog-Files: [blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)", "Crash when rendering with image texture in Eevee\nOperating system: Linux-5.4.0-7634-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.91.0 Alpha from 2020-07-24\n\nBlender crashes when going into Eevee rendered view / material preview / rendering with Eevee as long as any displayed shader uses an image texture.\n\nBased on startup scene:\nCreate an image texture in the shader of the default cube.\nSet the image texture as the material output.\nChange the viewport into material preview.\nCrash.\n\nBased on attached scene:\nChange the viewport into material preview.\nCrash.[eevee-crash.blend](eevee-crash.blend)\n\n\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", "Particle Instance from interpolated children works unexpected\nOperating system: win10 74bit\n\nBroken: 2.8, 2.79b\n\n\"Children\" option works good only with \"Along path\". Otherwise it just duplicates extra geometry where parent particles are located. \n\nOpen file and enable \"Children\" option, see how poly count is changed without visual appearance. Then check both \"Children\" and \"Along Path\" to see the difference.\n[Particle_instance_child.blend](Particle_instance_child.blend)", "Parenting breaks extract operations in sculpt mode\nOperating system: Linux-5.4.0-77-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 3.0.0 Alpha\n\nIf an object is parented to another it will not take the position of the parent into account when extracting geometry from sculpt mode.\nFor example I can parent the object to an empty and move the empty. As a result the empty will have translation values but the main object does not. \nIf I now mask off some of the surface and use \"Mask Extract\" or \"Mask Slice to New Object\" it will only use the relative position of the object in relation to its parent instead of the actual position in the Scene and position the extracted geometry in the wrong location.\nIn the case of mask extract this will completely break since it will try to shrinkwrap the extracted geoemtry back onto the original object but from the wrong location. \n\n[2021-07-02 15-44-32.mp4](2021-07-02_15-44-32.mp4)\n\n", "Ctrl+Click for Nurbs Surfaces\nWith Meshes and Curves, you can select a point, press Ctrl+LMB, and the point is extruded to the mouse.\n\nThis however does not work for Nurbs, even though you can extrude a point, Ctrl+LMB does not work.\n\nTry:\n- Add -> surface -> nurbs curve\n- Enter editmode\n- Select an end-point\n- Ctrl+Click... *nothing happens*\n\nThe same works for a curve or a mesh.\n\nThis could be split into 2 tasks\n- Get Ctrl+Click working for single nurbs curves.\n- Get Ctrl+Click working for nurbs surfaces (using the extrude code), This should extrude and place the newly extruded vertices at the mouse position, as is done with mesh data.", "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.", "Weird behavior with the set spline type node selection\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.1\n\nThe selection on the *set spline type* isn't working right for bezier and NURBS modes.\nAlso adding another node before the *set spline type* node will manipulate the weird behavior, even though the node doesn't do anything or is muted etc.\n\n- add a GN setup\n- add more that one curve\n- add a *set spline type* \n- try adding a selection that doesn't select all splines\n- see the weirdness.\n(it is more perceivable if the splines have more than two points, though the bug is still there)\n\nFile:\n\n[GN_set_spline_type_test.blend](attachment)\n\nVideo:\n\n<video src=\"attachment\" title=\"2023-07-31 21-15-45.mp4\" controls></video>\n\n", "Regression: Changes in curve normal behavior\nBroken: 3.0\nWorked: 2.92\n\nInstead of a simple arrow, the scene is something very remotely in the neighbourhood of that shape plus random extruded edges. \n\nOpen example file.\n\n", "Curve resample support for bezier curves\nCreating new bezier curve following the original curve with control points distributed equi-distantly along the original curve.\n\nThe curve resample is only generating poly splines at the moment. Another option (which could be the default) should create bezier curves.\n\n* Auto\n* Bezier\n* Poly Spline", "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", "When Object is not selectable it can still be switched to edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0\nWorked: dont know\n\nWhen a object is disabled for selection in the outliner and the object is then selected in the outliner its possible to enter any of the interaction modes. \nI would assume if a object is not selectable this should not be happening. \nNote: it only happens with single object selections. \nMaybe this is by design, it just felt like a strange thing and i thought i report it just in case.\n\n1. Create a object\n2. disable the object selection in the outliner \n\n3. Choose your interaction mode \n\n4. The mode changes to the one you selected \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.", "2d curve bevel ignores direction iff the curve is cyclic\nOperating system: Linux-5.4.0-89-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.74\n\nBroken: version: 2.93.5\nWorked: unknown\n\n\nWhen a 2D curve is NOT cyclic, reversing the direction of segments changes the orientation of the bevel. When the curve is cyclic, reversing it has no effect.\n\n\n\n1. Create two 2D curves: \"Profile\" and \"Shape\". In the Shape curve, set the bevel to use the Profile curve. Set the Shape curve to not be cyclic (in \"Active Spline\"). Give them some shape so you can tell them apart. Or download attached blend file.\n\n2. Enter edit mode on the Shape curve. Select all segments/control points, and click the menu: Segments -> Switch Direction. Notice that the Profile switches between inside and outside when you do this.\n\n3. Now turn on \"Cyclic U\" for the Shape curve, and try to switch the direction of the segments once more. It now has no visible effect. (However, it has still switched the direction of the curve, which can be seen by turning off Cyclic U after switching direction while it is on - it is just that the direction is ignored whenever Cyclic U is on.)\n\nBlend file with this situation set up:\n\n[2d-curve-bevel-bug.blend](2d-curve-bevel-bug.blend)", "Subdivision surface with circle curve issue. \nOperating system: Windows 11 Pro\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0\nWorked: (on 2.9 was working fine)\n\nCreating a mesh ring with curve circle and applying sub division serface, the modifier fails at two vertecies on the mesh. \n\nAdd curve -> circle -? edit mode -> select verticies -> E to extrude and S to apply size -> E to extrude on Z direction -> done\nObject Mode -> add modifier -> subdivision serface -> issue.\n[Issue with subdivision serface .blend](Issue_with_subdivision_serface_.blend)\n\n\n", "Setting curves to another spline type makes them shorter\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0\n\nI discussed this with Campbell during a meeting 2021-02-23. He suggested that I report it as a bug.\n\nWhen setting curve spline type **from nurbs to bezier**, the curve becomes shorter. It also becomes shorter when I convert it**from bezier to nurbs**. \n\nIt is worth to note that when converting from bezier to nurbs, the curve can get back the length by changing the following settings in \nobject data properties > active spline\n\n\n---\nScreen grab of issue\n\n[convert curve spline makes it shorter.mp4](convert_curve_spline_makes_it_shorter.mp4)\n\n\n- Add curve > path\n- Go into curve edit mode\n- Subdivide the curve 2 times in order to get enough vertices for changing spline type to bezier\n- Change spline type from Nurbs to Bezier - observe that the curve becomes shorter.\n# Change spline type from Bezier to Nurbs - observe that the curve becomes shorter\n\n\n\n\n\n\n", "Regression: Hiding all points of a spline in curve edit mode does not hide splines\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0\nWorked: version: 2.93.6\n\nCaused by b9febb54a4\n\nHiding all points of a spline in bezier edit mode does not hide the related curve spline\n\n1) Add a bezier object (like the squigle)\n2) Go into edit mode\n3) Select all the points\n4) Press H to hide\n5) Only the points are hidden but the curve (spline) remains visible\n\nExpected behavior:\n5) Both the points and the related curve spline are hidden (as they were in 2.93.6)\n\n[#93756.blend](T93756.blend)" ]

[ "Path animation and the new curves type\nEventually every use of `BKE_where_on_path` will have to be removed, since it isn't supported by the new curves type.\nThis task is just about the two constraints that use evaluated positions, tangents, and normals of the first curve at a specific factor.\n\nThe eventual idea is to use versioning to change all legacy curve objects to the new curves object type, so this will have to be addressed for that transition.\nBut the change can also make animation workflows more intuitive and consistent with other Blender design.\n\n### Path Animation Settings\n\n\n\nIn order to support the new curves object, the \"Path Animation\" settings from the legacy curve object will have to be moved to the contraints that support them, because the new curves data-block will not store those specific settings. Any animation on the curve's path animation settings should also be moved to the constraint.\n\nIt's not important to make the design for the constraint perfect, since the long term goal is to replace them with a node based system anyway. The path animation constraint will then need these new settings:\n- \"Frames\"\n- \"Evaluation Time\"\n- \"Clamp\"\n\nAfter the change, the \"Path Animation\" panel wouldn't exist anymore.\n\n### Parenting\n\n\n\nThe new curves object should **not** support the special parenting behavior for the legacy curve object that uses the path animation settings instead of regular parenting. This behavior will have to be removed with versioning, replaced with a proper follow path constraint, as described above.\n\n### Open Questions\n\n**What happens when there is no evaluated curve**\nPreviously the constraints used the original curve with some set of the deformation modifiers applied. That was often problematic because what looked like a curve visually in the viewport was actually a mesh, so the constraints wouldn't work. Now we have a more precise definition of the evaluated curves, which is different than before.\n\nThis is potentially problematic, because the changes suggested above could introduce regressions. I would suggest using the original curve *without any modifiers* applied in this case. This behavior is still slightly different, but it is simple and easy to predict, and doesn't involve keeping track of a \"pre-tesselation point\" in the middle of modifier/nodes evaluation, which is basically a non-starter for the new curves object.\n\n### Todo\n\n\n\n- [x] Implement updates to sample curve node (the constraints need to use that internally) (#95443)\n- [ ] Update constraints to use the new evaluated curves data\n - [ ] Follow path constraint\n - [ ] Clamp To constraint\n- [ ] Move path animation settings to constraints/curve deform modifier\n- [ ] Remove special parenting behavior by adding follow path constraints in versioning" ]

[ "EEVEE baking\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", "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.", "EEVEE & Viewport Module\nThis page is in the process of being fully replaced by #eevee_viewport.\n\n---\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- `(straightforward)` - *Task which is straightforward to implement, which don't rely on larger API changes or refactoring.* \n\n# Long Term Projects\n\nDevelopment may span multiple release cycles.\n\n- {icon circle color=yellow} #68989 ( Selection future-proof design)\n- {icon circle color=yellow} #68990 (Vulkan support)\n- {icon circle color=yellow} [D5442: LANPR line rendering (summer of code)](D5442)\n- {icon circle color=yellow} #68991 (Fisheye / panorama in EEVEE)\n- {icon circle color=yellow} #68993 (Stereo Panorama in EEVEE)\n- {icon circle color=yellow} #68994 (VR design / usability)\n- {icon circle color=yellow} #68995 (VR input integration and mapping)\n- {icon circle color=yellow} #68464 (Better Motion Blur)\n- {icon circle color=green} #68996 (OpenSubdiv GPU acceleration)\n- {icon circle color=green} #68997 (Panorama selection support in viewport)\n- {icon circle color=green} #68463 (Dynamic Indirect light cache)\n- `?` #68998 (Virtual Reality (XR/VR/AR/MR))\n\n\n# Medium Term Projects\n\nDevelopment should be possible in a single release cycle.\n- {icon circle color=red} #71347 (Virtual Reality - Milestone 1 - Scene Inspection)\n- {icon circle color=yellow} #68478 (World Light Extraction)\n- {icon circle color=yellow} #68453 (Anisotropic BSDF)\n- {icon circle color=yellow} #68456 (Shadow catchers)\n- {icon circle color=yellow} #68474 (Clustered Light Culing)\n- {icon circle color=green} #67579 (Improve NDOF navigation)\n- {icon circle color=green} #54638 (OpenGL headless rendering)\n- {icon circle color=green} #68479 (Pointiness support)\n- {icon circle color=green} #68460 (Multiscatter Glossy BSDF)\n- {icon circle color=green} #68459 (Hair BSDF)\n- {icon circle color=green} #68458 (Velvet BSDF)\n- {icon circle color=green} #68477 (Parallax Occlusion Mapping)\n- {icon circle color=green} #68468 (Depth of Field Refactor)\n- {icon circle color=green} #68472 (Light Nodetree support)\n- {icon circle color=green} #68470 (Shadow buffers)\n- {icon circle color=green} #60779 (3D Viewport clipping support)\n\n# Paper Cuts\n\nSmall improvements and polish.\n\n- {icon circle color=green} #64281 (Option to lasso-select using geometry instead of object centers.)\n- {icon circle color=green} #69282 (Ability to cancel viewport operations (rotate/pan/zoom))\n- {icon circle color=green} #68206 (Lag reading viewport depth buffer in LookDev mode)\n- {icon circle color=green} #70803 (Support Viewport roll - around the cursor position) `(straightforward)`\n- {icon circle color=green} #73214 (Armature Object's \"Display As\" does nothing)\n- {icon circle color=green} #73732 (Grid-lines vanish in perspective view, when viewed from the side)\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", "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!", "Blender 3.2.1 / 3.4 - Cycles - Persistant Data and Motion Blur artifacts on GPU\nOperating system: Windows 10, Ubuntu 21.04\nGraphics card: GTX 1080, RTX 3080\n\nBroken: 3.2.1, b5e92c3dfe\nWorked: 2.79\n\nPersistant data is bugs out during renders sometimes.\n\n1. Open attached blend file in Blender 3.2.1\n2. Press f12\n3. Press right on the keyboard (frame 771)\n4. Press f12\n5. Press right on the keyboard (frame 772)\n6. Press f12\n7. Notice how its not as expected.\n8. Press f12 without framing forward\n9. Notice how it is fine\n\ngood\n\nbad\n\n\nThis means when rendering animations, it can produce frames which bad, which then require more re-renders.\n\nWindows and Linux have both been tested and results are the same.\n\nTested CUDA, Optix and both have issues. CPU renders fine. \n\nDisabling Persistant Data renders fine.\n[bug.blend](bug.blend)\n\nNOTE: We had #95475, #96822 already for Persistent Data and Motion Blur issues (these should be fixed), I can repro this case though.\n\nEDIT:\nAs another task #100729 has been merged into this file, there is another test file [BUG.blend](BUG.blend)\n", "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", "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", "EEVEE - Screen space reflections artifacts\nOperating system: Linux-5.3.0-7625-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 2)\nWorked: ?\n\nSSR shows some strips when I have bad data for normals.\n\nOpen the file:\n[ssr_sripts.blend](ssr_sripts.blend)\n\nIf you click anywhere multiple times, viewport gets darker and darker.\n\nBefore:\n\n\nAfter clicking the glossy node header a few times:\n\n", "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", "Evee crashes when rendering \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.3\n\nRendering this file with evee causes a crash. Cycles is able to render the file.\nThe mesh was originally created in blender 2.6x with blender internal textures down loaded from blend swap 6618\nI was updating the textures for 2.9.3. \n\nRender the image.[crash.txt](crash.txt)\n\n[debug.blend](debug.blend)\n\n", "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.", "Batch Rendering Crashes if EEVEE set in scene\nOperating system: Windows 10\nGraphics card: Any or None\n\n2,83, 2,90, 2.92\n\nEEVEE is set as renderer in the scene file.\nThe scene is send to the render farm. \nOpenGL is not available as render farm is running as background service OR blades machines do not have any GPU at all.\nBlender in Commandline Crashes.\n\n(Side Note: Cycles works fine as CUDA is available within background service)\n\n\n**Expected Behavior**\nReport an error \"EEVEE requires OpenGL. Unable to find/initialize openGL32.dll\"\n\nTo reproduce the issue, you either need some helper service that starts Blender in commandline mode (I can provide one) OR you can use any machine that does not have a GPU installed.\nCreate a new scene with EEVEE as renderer.\nTry to commandline-render the scene.\n\nCommandline that we used:\n\"C:\\renderer_exe\\blender\\win_x64\\Blender_2.90\\blender.exe\" -b \"\\\\isilonai\\woodspeople\\Boar (With fur).blend\" -o \"\\\\isilonai\\woodspeople\\Boar (With fur)\\Brawler####\" -F PNG -x 1 -s 10 -e 10 -j 1 -t 24 -a -y\n\n\nCommandline output:\nR 6| >\"C:\\RR_localdata\\renderer_exe\\blender\\win_x64\\Blender_2.92\\blender.exe\" -b \"C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\" -o \"C:\\RR_localdata\\renderout\\A\\3D\\Blender\\render\\myOut####\" -F PNG -x 1 -s 2 -e 3 -j 1 -t 24 -a -y \nR 7| Blender 2.92.0 Alpha (hash 719bea0d6d06 built 2021-01-12 23:10:47)\nR 8| Read blend: C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\nR 9| Writing: C:\\RR_localdata\\temp\\A\\cube.crash.txt\nR 10| StdErr: Warning! Using result of ChoosePixelFormat.\nR 11| StdErr: Warning! Using result of ChoosePixelFormat.\nR 12| StdErr: Warning! Using result of ChoosePixelFormat.\nR 13| StdErr: Warning! Using result of ChoosePixelFormat.\nR 14| StdErr: Warning! Using result of ChoosePixelFormat.\nR 15| StdErr: Warning! Using result of ChoosePixelFormat.\nR 16| StdErr: Warning! Using result of ChoosePixelFormat.\nR 17| StdErr: Warning! Using result of ChoosePixelFormat.\nR 18| StdErr: Warning! Using result of ChoosePixelFormat.\nR 19| StdErr: Warning! Using result of ChoosePixelFormat.\nR 20| StdErr: Warning! Using result of ChoosePixelFormat.\nR 21| StdErr: Warning! Using result of ChoosePixelFormat.\nR 22| StdErr: Warning! Using result of ChoosePixelFormat.\nR 23| StdErr: Warning! Using result of ChoosePixelFormat.\nR 24| StdErr: Win32 Error# (127): The specified procedure could not be found.\nR 25| StdErr: Error : EXCEPTION_ACCESS_VIOLATION\nR 26| StdErr: Address : 0x00007FFF8DBA1C81\nR 27| StdErr: Module : VCRUNTIME140.dll\nR 28| StdErr: Thread : 00001c94\n[Boar.crash.txt](Boar.crash.txt)\n\n\n", "Blender 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." ]

[ "EEVEE White Dots/Speckles/Artifacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0 Alpha\n\nok so this is what I concluded, first the white dots will appear randomly in viewport in specific places, the dots place differ when rendered, this issue appears when a flat surface is tangent to camera/viewport view, with or without lighting, this is only solved when disconnecting the BSDF and leaving the Material Output with no input, it's not related to reflections or DOF, the DOF and Bloom exaggerate it but its not the cause{[F9920228](No_Bloom.png)}\n\n\n\n[Test.blend](Test.blend)\n\n\n\n\n\n\n\n\n- Try to make the camera tangent to a flat surface with a BSDF attached, activate the bloom and DOF to make it obvious \nThis is only in 2.93, 2.92 is ok\n\n", "Fireflies in EEVEE render\nOperating system: Linux-5.4.0-70-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha\n\nA scene with particles (grass) and a monkey head; motion blur enabled; the render has clear artifacts, similar to fireflies. When animation is rendered the fireflies are quiet distracting. The same scene rendered in 2.83 doesn't show the same artifacts.\n\nOpen the blend file attached and render frame 19. You'll see the artifacts clearly. When rendered in 2.83, it's not there. \n\nBlender 2.83 render\n\n\nBlender 2.93 render\n\n\nBlend file\n[artifcats.blend](artifcats.blend)", "white artifacts in EEVEE\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 670/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.92, 2.93.0 Alpha\nWorked: 2.91\n\nWhite NaN pixels appearing when using EEVEE. It's less apparent in the viewport than in renders as the number of artifacts depends on the number of samples. \n\n[spekles in eevee.blend](spekles_in__eevee.blend)\n\nOpen the attached file, switch to viewport rendering, hit F12. \n", "Bright white dots appear on the edges of the geometry in Eevee render\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0 Alpha\n\nBright white dots appear on the edges of the geometry\n\nrender in 2.92\n\nrender in 2.93\n\nrender in 2.93 with no lights in scene\n\n\nscene\n[pipeline_scene.blend](pipeline_scene.blend)\n\n", "Eevee DoF with \"Jitter Camera\" creates fireflies\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 465.89\n\nBroken: version: 2.93.0 Alpha\n\nSuper bright pixels are created by DoF\nThe problem seems to be present only when the *Jitter Camera* option is used\n\nZoomed in into a firefly pixel\n\n\nWhen the firefly occurs in a heavily out of focus part with bloom we get this (this is not even zoomed in)\n\n\nThe included file is highly simplified but this problem is plaguing pretty much all my scenes!\n\nPress F12 on the following simplified file\n[DOF FIREFLY.blend](DOF_FIREFLY.blend)\nLook around the center of the image at 100% resolution", "White Pixels in Render in Eevee\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\nWorked: (newest version of Blender that worked as expected) \n\nSince a version some days ago (i cannot tell which exact version) i am getting white pixels on some objects in some scenes in eevee.\nI haven't been able to narrow it down to a single parameter.\nIt seems to happen on flat angles/ borders.\n\nThere are things that sometimes make it worse:\nin material high glossiness, low roughness, normal map (but even happens without)\nreflection plane seems to make it worse\nin render settings: high sampling, half res trace, no high quality normals, max roughness\n\n\nI have attached a blend file which shows 1 pixel as white. in other scenes it's more obvious.\n[test.blend](test.blend)\n\n\n", "EEVEE fireflies along faces\n****Operating system: Windows 10 Home\nGraphics card: RTX 3070 Laptop\n\nBroken: 2.93.0 Alpha 9b806c49d08a master\nWorked: 2.92\n\nEEVEE creates white fireflies along faces that are parallel to the camera.\n\nEnter a scene with a cube or flat object, adjust the camera so it looks almost parallel or very low angle along the flat face and EEVEE will produce white fireflies along the face. Enabling depth of field and bloom makes the bug easier to see, but is not the cause of it. Test on GTX 1060 Desktop does not reproduce the bug.\n\n[Firefly Bug.blend](Firefly_Bug.blend)", "Eevee - white pixels on edges of surfaces\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.93.0 Beta\nWorked: 2.92 official release\n\nRendering in Eevee results in occasional fireflies/white pixels, mostly on the edges of a surface - even with the default material.\nOnly way to fix is to enable 'High Quality Normals' in the Performance tab under Render Properties, which makes it essential to use.\n\nOpen blend file and render F12.\nIf result is like attached image, pixel shows up at the center.\n\n\n\nEnabling 'High Quality Normals' (Render -> Performance) will make it disappear.\n\n[eevee_white_pixel.blend](eevee_white_pixel.blend)", "Eevee burnt white pixels\nOperating system: Win10 64, Ryzen 9 3900X\nGraphics card: GTX 3070\n\nBroken: (example: 2.92, 2.93)\nWorked: (2.91)\n\nIn Eevee random white burnt out pixels appear. Paired with DOF and / or Bloom they blow up to be super noticable.\nI assume it's got something to do with either my GPU or CPU, since with my old computer I never had this problem.\nI have the latest drivers installed.\n\n[system-info.txt](system-info.txt)\n\nOpen the attached blend file and switch to Eevee.", "Eevee trying to play God - Let there be light.\nOperating system: Linux Debian Stable\nNot sure if GPUs/drivers are the issue:\nFailing on Graphics card: GTX970, 2070's, both with Nvidia official (non-free debian) drivers\nWorking on: AMD RX580 (unconfirmed). (Blender 2.92)\n\nBroken: 2.93 git builds and daily download from Apr 4, 2021.\nWorked: 2.92 on AMD RX580, we think. Not 100% sure if 2.92 resolves it yet.\n\nShort description:\nScene with all lights/emitters hidden still produces light from various objects.\n\nReproduce:\nLoad attached blend, eevee rendered view, zoom in and out of camera view with ctrl-mousewheel.\n\nLong description:\nOne ultra-bright spot (pixel?) seems to be generated at object geometry. Even very clean objects will produce it. Depth of field spreads this. Screen space refractions spreads it around. Compositor nodes like glare/fog glow will over-react, but clamping the render layer output will prevent that, (so I presume this pixel is ultra bright)\n\nWith exposure set to 10 you can see the white light, with no actual light source, goes everywhere.\n\n\n\n\n\nThese frames were with emission objects on, but those aren't the issue. Frame 4 happens to be one that causes the bright pixel -> glare nodes to flood with light:\n\n\n[ix-nay.blend](ix-nay.blend)", "White artifacts in Blender EEVEE 2.93Alpha\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92\n\nI have packed the textures into the blend.\n[DOF_glitch2.93.blend](DOF_glitch2.93.blend)\n[Bug in 2.93Alpha.mp4](Bug_in_2.93Alpha.mp4)", "EEVEE Render Glitch\nOperating system: Linux-5.4.0-67-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha\nBroken: (oldest archive I have where it is broken) blender-2.93.0-f117ea262463-linux64 March 5\nWorked: blender-2.93.0-bfb2e87a9ea0-linux64 Feb 23\n\n\nGlitch when rendering with EEVEE\n\n- with new installation/configuration file and default startup file\n\n1. Rotate default cube on X axis -28.85 degrees\n2. From compositing tab, add a denoiser node\n3. Render \n \nAlso tested this on an Alienware laptop with same results (specs for that not uploaded as it doesn't seem to be hardware dependent).\n\nProblems seems to be related to the angle of the cube side in relation to camera - if you rotate cube intervals of 90 degrees on X axis in either direction problem and render glitch is still there. If you rotate cube just slightly on X axix (from -28.85), problem goes away.\n\nGlitch *mostly* goes away if you remove the tickmark on HDR box in Denoise node - but there are still a couple of white sparklies if you look very close.\n\nProblem does not appear when switching to Cycles.\n\n[#86795.blend](T86795.blend)\n", "Blender Dof Glitch in 2.93.0 Alpha\nOperating system: Windows 10 Pro\nGraphics card: 3070 Nvidia\n\nBroken: (2.93.0 Alpha)\nWorked: (2.92.0)\n\n**Short description of error** When rendered in 2.93.0 Alpha shows glitches over the horizon in my blend file. But its much faster than 2.92.0. While 2.92.0 Renders better results. (0 glitches in DOF )\n\nRender each on 2.93 and 2.92. you will see the dof issues as the jpegs i uploaded.\n\n < 2.92.0\n\n <2.93.0 Alpha\n[DOF_glitch2.93.blend](DOF_glitch2.93.blend)\n" ]

[ "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)", "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", "When turning VR mode on, the controllers show, even when there are no controllers in the system\n**System**\n* ConceptD 7 (laptop with holographic display using OpenXR backend on Windows)\n\nBroken: version: 4.0.0 Alpha\nWorked: - (technically in old Blenders before we had XR input support)\n\nWhen turning VR mode on, the controllers show, even when there are no controllers in the system.\n\n\nI don't know if the issue is unique to this system, but this is a laptop that uses OpenXR backend to handle head tracking and has an holographic display but no \"VR controllers\".\n\n* Turn on VR\n* You will see a big gizmo in the screen (black circle, with a XYZ gizmo on top of it).\n\nThe gizmo is following Blender's camera (making the experience unusable).\n\n**Workaround**\n\nI can work around that by disabling the visualization of VR controllers. However if the system has no controllers, they shouldn't be drawn in the first place:\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", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\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", "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", "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", "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)", "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.", "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", "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", "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.", "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", "Unable to create manual curve to mesh UV with spline parameter\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\n\nBelow file is creating uv's from the curve length and profile and then outputting as a custom_UV attribute. There seems to be squashing happening at the beginning and end.\n\n[spline parameter fac bug.blend](spline_parameter_fac_bug.blend)\n\n\n\n" ]

[ "The curves have disappeared in object mode\nOperating system: Linux, Windows\nGraphics card: Nvidia 1060\n\nBroken: 2.80, 36121a1bdcd8 2018-12-20\n\nCurves are not drawn in the viewport in object mode: only object dot is visible, only when selected.\nWhatever engine, whatever overlay, whatever object display options.\n\nIt may be related to: #59271 ?\n\n\nJust to add a curve.\n\nThank you,\nRiccardo", "curve\n**System Information \nOperating system: Windows 10\nGraphics card: Nivida GTX 1050 TI\n\nBlender Version 2.8\n\n\n\nIn the object mode, the curves are not visible", "Curves disappearance bug\nOperating system: win 10\nGraphics card: Nvidia GTX 780\n\n**Blender Version/2.8**\nI have downloaded the latest blender 3d beta build on date 12/19/2018.\n\nthe problem is that I experienced the curves doesn't show up, and I'm not sure why ill attach the image and the blend file.\n\n**simply just add a curve to the scene ^^**\nand thank you for the core team for their hard and consistent work.\n\n\n[cruve_problem_1_1 (1).blend](cruve_problem_1_1__1_.blend)\n", "Curves are not visible in Object Mode\nOperating system: macOS 10.14.2 (18C54)\nGraphics card: AMD Radeon R9 M395X 4096 MB\n\nBroken: Blender 2.80 Dec 20\n\nAll curve objects are not visible in object mode in 2.8.\n\n\n - Add a curve object\n - It's invisible\n\n\nObject Mode:\n\n\nEdit Mode\n", "unable to see curve ojects in Object mode\nOperating system: windows 10\nGraphics card: GeForce 940MX\n\nBroken: a91886e76ebd\nWorked: (optional)\n\ncurves are not seen when they are added in object mode, however you will see them when you go to edit mode", "Curves insivible in viewport, selected and unselected\nOperating system: WIN 10 Home\nGraphics card: NVIDIA GTX 1050\n\nBroken: 2.80, 9dde3e42a7c5, blender2.8, 2018-12-21, as found on the splash screen\n\nCurves are invisible / not displayed in viewport, selected or not selected. The only displayed element is the curve origin.\n\n- Open the default scene\n- Delete everything\n- Add a curve of your choice\n(I double checked that curve display is active in the \"Object type visibility\" drop down menu)", "curves are not showup on object mode\nOperating system:\nGraphics card:\n\nBroken:\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\nBased on the default startup or an attached .blend file (as simple as possible).", "Curve object with bevel width zero is not visible in the 'Object-Mode'\nOperating system: Ubuntu 16.04 LTS\nGraphics card: GeForce 920MX\n\nBroken: Blender 2.80\n\nCurve object with bevel width zero is not visible in the 'Object-Mode'\n\n1) ADD a Curve object\n2) Curve object is not visible in Object-Mode, however it is visible in Edit-Mode\nBlender File: [CurveObject.blend](CurveObject.blend)", "Curves invisible in object mode\nwin 10 64bit\nNvidia GeForce GTX 1060 6GB\n\nBroken:\nblender-2.80.0-git.fd42fe66161-windows64\nWorked: (optional)\n\n\nAll types of Curves are invisible in viewport object mode.\nOverlays options doesn't help\n\n[curves bug.blend](curves_bug.blend)\n\n1. Open attached blend file. \n2. See the empty viewport\n3. press Tab to see that Curves are there in the edit mode.\n\nor just Add any type of curve to a new blender file", "Potential bug: Bezier Curve not visible in object mode \nOperating system: Windows 10 \nGraphics card: NVIDIA Quadro M1000M \n\nBroken:2.80 Beta 21/12/2018 00:45 \n\n\nBased on the default startup:\nTop View\nAdd Bezier Circle -->> Nothing is visible\nHit Edit mode --> can see the object \n\nits as simple as that to reproduce \nAttn screen shots \n\nThanks Avi \n\n" ]

[ "Color management is broken in the Sequencer\nOperating system: Linux-5.0.21-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: Mesa DRI Intel(R) Sandybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 19.1.1\n\n\nBroken: version: 2.80 (sub 74)\nWorked: earlier build of 2.80 (hash: d62a749fcf48) and 2.79\n\nWeird things happens when changing the color management settings in the VSE:\n- wrong color display\n- make sound\n\nWith a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not.\nAlso, changing this setting does not apply the change directly, the VSE has to be refreshed.\n\nAnother issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise.\n", "Unusable display with AMD driver errors.\nOperating system: Ubuntu 22.04.2 LTS/Kernel version 5.15.0.75/FOSS amdgpu driver(default)\nGraphics card:MSI Radeon RX580 8GB\n\nBroken: 3.5.1, 3.1.0\nWorked: 3.1.0(Did not experience this until recently)\n\nWhen editing UV GPU gets reset after errors, the compositor does not recover. Garbled image on the screen with displays unusable. Log data attached.\n\nThis happens when pressing .(dot) on the keypad, selecting or moving a UV.\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)", "Objects in volumes have dirty noisy object pass AOV\nOperating system: Windows 11\nGraphics card: RTX 2070\n\nBroken: : 3.4, 2.93\n\n\n\nSee the image for the dirt Object index AOV\n\n\n- Load the attached .blend\n- Render it\n# Check the Comp tab for the result\n\n[_17082022_2227_24.zip](_17082022_2227_24.zip)", "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", "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", "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.", "Video Editing (outline on the border)\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\n\nSome images with an alpha channel have grey outline when scaled up and different bicubic or bilinear interpolation is used.\n\nIssue is visible immediately after opening .blend file\n[#86861.zip](T86861.zip)", "Diffuse Direct, Indirect Bake to Vertex Color Artefacts\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nWorked: This has never worked properly (At least in my experience)\n\nWhen baking Diffuse light to vertex color, black triangles and random dark spots appear in vertex color. This effect is more apparent with:\n- Area lights.\n- Emissive surfaces.\n- Lights with very high power.\n\n1. Create geometry and give each a byte_color vertex color channel.\n2. Place area lights in scene with high power.\n3. Bake diffuse direct and indirect to color attribute.\n\nSee .blend of my project attached. In the file i've already baked the emissive light to vertex color where you can see the artefacts. Switch to cycles live render view to see the correct output. I think the tiled texture may have something to do with it. I've added a tiled texture and packed it in the example.\n\n", "Black outlines around animated Objects when Scrubbing/Playback.\nOperating system: Windows 10 64 Bits\nGraphics card: GTX 1080 TI.\n\nBroken: version: 2.83.8 hash: 7c027f9480a9\nWorked: version: 2.83.4 hash: `abb7364912` (commit date: 2020-02-23 23:00)\n\nThere are some weird black outlines popping out during anim playback or scrubbing. \n\n***P**\n{[F8400153](spot.jpg) size = full}\n\n\n* open the file\n* If it is not already set, set viewport shading to material preview (that's where you can easily spot them)\n* playback the animation or quickly move the object\n\nThe black outlines will appear but the moment you stop they'll disappear, so you can screen capture the moment to check their existence ***P**.\n\n[Black.blend](Black.blend)\n", "Blender development todo list -- Render\nNOTE: this is a direct dump of Render (without cherrypicking the valid items)\n\n### Render & UI\n\n- [ ] While rendering, manipulating images (like reload, resizing generated) can still crash Blender. Better image \"owner\" locking is required for 2.5 (#28477)\n- [ ] While rendering, several UI changes can cause crashes (#24758)\n- [ ] Rendering can't really use normal scene data if ui is interactive without causing all kinds of trouble, for examples and related issues see the item above this one.. and the reports (#26535)\n- [ ] Renaming scene leads to missing rendered result in image editor and compositor (see (#30222))\n- [ ] Rendering with File Output nodes could produce unwanted output images, see (#38605)\n- [ ] Shaded draw mode (using render code for vertex colors) is most certainly not coming back\n- [ ] Color Management can be communicated better, like when sampling colors in Image Window it confuses (could indicate such). Color Management also wasn't added backward compatible, disabling it gives dark results.\n- [ ] Compositor \"file out\" node doesn't work for FSA, and as color management troubles too.\n- [ ] FSA render uses temp files with names preventing other Blender instances to render too. (#28314)\n- [ ] Texture nodes have been implemented by recursively (backwards) calling parent nodes, this gives issues for viewers, previews and threads in general.We will try to keep it stable, but the functionality for this is going to replaced with a better shader system in 2.6. (compositor and material nodes call nodes forward, sorted on dependency. Each node is only called once this way).\n- [ ] Render display in Image window, for a window previously showing UV editor, doesn't restore correctly. (#26828). Code for this is too much spread around and fuzzy, needs full revision.\n- [ ] Object transform is not possible during rendering #37019\n- [ ] Don't render and warn when a driver or pre-render script can't be executed, a texture is missing, physics are not baked. Needed e.g. when renderfarms have scripts blocked.\n\n### Node Textures\n- [ ] Grouping texture nodes affects on data range #45696\n\n### Baking\n- [ ] add option to smooth vertex colors as a post process after baking #35066.\n- [ ] Baking to a low-res textures might miss pixels which lies on the UV island boundary #37681\n- [ ] Vertex baking might cause AO artifacts #44178\n- [ ] Support dupligroups #43553\n- [ ] Modifier produces non deterministic effects #42015\n- [ ] Update Blender side baking to support different topologies needed for adaptive subdivision #49405", "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", "Vertex paint + x-ray + polygon selection mode = weird shading\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\n\nFor me it looks like this\n\n\n\n[vertex paint x-ray strange shading.blend](vertex_paint_x-ray_strange_shading.blend)", "Eevee: image sequence data bloc displays different offset attributes when set from different locations (texture editor, shader editor, image locator)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.5.0\n\nif I change the offset (or start frame) of the sequence in the shader editor, I would expect it to also change in the image editor or wherever I am using the same image sequence, otherwise it causes discrepancies and buggy viewport display (since we dont know which offset is displayed in the viewport). \n\nJust change the offset of 1 of the 3 displayed image sequence settings displayed... the other 2 won't follow.\n\nCycles does this fine btw.", "UI: Image/UV Editor\nThe UI of the Image and UV Editor can be improved.\n\n* Move smooth edges option to user pref\n* Move overlays to an overlay popover\n\n\n\n\n* Move display settings to a popover\n* Change the Pixel Coordinates toggle into an enum to choose between Pixels or Normalized\n\n\n* Slightly re-arrange the header:\n\n* Move th UV Vertex panel away from the Image Sidebar category and into Item, and include Coordinates option here too:\n\n" ]

[ "artifacts during the simultaneous operation of the X-ray and \"in front\"\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 20.1.3 26.20.15015.1007\n\nBroken: version: 2.92.0\n\nthe appearance of violent graphic artifacts \n\n\nCreate new scene.\nIt will take many objects to reproduce the error.\nfor one in the object property -> Viewport Display put a tick in front of the \"in front\".\n\nAfter that, in the Viewport Shading, put a tick in front of the X-ray.\n\n\nObserving artifacts. \n\n\nWhen you uncheck the \"in front\" checkbox in simple scenes, artifacts disappear, but in more complex scenes, others appear instead.\n\n" ]

[ "Small Custom Bone Shapes have some Wireframes Artifact.\nWindows 10 64 Bits.\nGraphics card GeForce GTX 1080 Ti \n\nBroken: version: 2.82.6, hash: a854840e76ae\nWorked: (optional)\n\nSmall custom bone shape has wireframe glitching, the Scale is based on real world but if you resize it in/out u can see it happen.\n\n{[F8257584](Shape.gif) size = full}\n\n\n\n[Bug.blend](Bug.blend)\n", "The arrows for expanding N/T panel are now drawn when using cycles and render border exists in the viewport\nOperating system: Linux-5.15.0-78-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro K5100M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 390.157\n\nBroken: version: 4.0.0 Alpha\nWorked: never...? 3.3.9~4.0 all broken like this\n\n\nThe arrows for expanding N/T panel are now drawn when using cycles and render border exists in the viewport.\n\nIt's only drawn once and then disappears. Moving the viewport will show it again for 1 redraw and then it disappears again.\n\nNot _that_ much of a problem, but if you are just using mouse/pen to find it during render preview it's kinda inconvenient.\n\n\n- Switch to cycles\n- Set a render border with `ctrl-b`\n- `Z -> Render Preview`, the arrow flickers for 1 redraw and then disappears.\n\n", "Light of 'Area' type lamp presents artifacts when placed at great distances\nOperating system: macOS-13.4.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: versions: 3.1 to 4.0a \n\nArtefact's appearing with bigger Arean Light distances and spread angle 0.1 to 20~ \n(Like for space scenes with bigger distance Area lights for better sun effects...)\n\nJust open one of the files or follow the image below to set up the light.\n\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", "Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)\nOperating system: Linux-5.15.0-52-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.4.0 Alpha\nBroken: 2.92.0\nWorked: 2.91.2\n\nBisecting gives 0f95f51361 as the culprit commit\n\nif the armature viewport mode is set to \"in front\" it doesn't properly update when the overlays are turned off and on\n[Peek 2022-11-01 05-35.mp4](Peek_2022-11-01_05-35.mp4)\n\n1-add an armature\n2-set the \"viewport display\" to in front\n3-turn off and on overlays\n4-if you can confirm the bug the armature should appear after changing anything in the 3d view to update as in the video, move rotate or zoom \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)", "VSE displaying png metadata/artifacts\nOperating system: Linux-5.11.2-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.11.2-1-MANJARO, LLVM 11.1.0) AMD 4.5 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.91, 2.92\n\nAfter loading a png created with inkscape, some hidden metadata of that png file (that I could not see using image viewers but only if I open the png in a text editor: line 4 \"tEXtSoftware www.inkscape.org\") www.inkscape.org is displayed below the image together with artifacts.\n\nexport something from inkscape to png\nin the VSE, load that png using Add Image/Sequence\ntext/artifacts appear below the image\n\npng:\n\n\nresult:\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)", "GPU Subdivision Causes Artifacts in Mesh Analysis Overlay\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken:\nversion: 3.1.1 Release Candidate\nversion: 3.3.1\nversion: 3.5.1\nversion: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-25 13:50, hash: 6ee8aa4997ee, type: release\nversion: 3.6.0 Alpha\n\nWorked: could not find.\n\nWhen GPU subdivision is enabled, the Mesh Analysis overlay shows artifacts.\n\n\nPlease follow these steps to reproduce the issue:\n1. Start Blender.\n2. Select the default cube.\n3. Apply the Subdivision Modifier (press Ctrl+1).\n4. Enter edit mode.\n5. In the viewport overlay menu, enable Mesh Analysis.\n\n**Known Workarounds**\n1. Disable GPU Subdivision.\n2. Disable \"Show in Edit Mode\" for the Subdivision modifier.\n\n", "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.", "VSE: Artifacts in histogram (NVIDIA)\nOperating system: Windows-10-10.0.19045-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\n\n\nmove the UI region/border and zoom into histogram/chroma vectoroscope/luma waveform and purple artifacts appear. tested on blender 3.5.1, 3.6.1, 4.0a\n\n", "sculpt mode artifacts if displace modifier is active\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.28\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIn sculpt mode if the displace modifier is active the brush behavior is unpredictable, especially with the smooth brush.\nIt looks like that the sculpting mode takes account of the mesh after being modified by the modifier and start the sculpt over it.\n'm reporting this because in other modes the modifier and the actual edit of the mesh are handled as separate thing.\n| [smooth_brush_prob.mp4](smooth_brush_prob.mp4) | [06_24_2022.mp4](06_24_2022.mp4)\n| -- | -- |\n\n- Open any of the attached files and try to smooth or grab as done in the video\n\nthanks!\nMax\n\n\n[smooth_bug.blend](smooth_bug.blend)\n[sculptbug_24062022_1422_44.blend](sculptbug_24062022_1422_44.blend)", "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!", "Cycles: overlapping VDBs cause rendering artifacts\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 511.79\n\nBroken: version: 3.1.2\nWorked: version: 3.0.1\n\nFirst reported here: #97062\nOverlapping VDBs cause black rendering artifacts.\nThis is likely a known issue or related to a known issue.\nFrom the release notes for 3.1: [Ray Tracing Precision](Cycles#Ray_Tracing_Precision)\n>Many artifacts from rendering small, large and far away objects have been eliminated. There will always be object scales where numerical precision becomes a problem, but it's further out now.\n>\n>There can still be artifacts with rendering overlapping geometry, in some cases more severe than before. Such overlapping geometry should be removed, or have a small distance added in between.\n\n\n|3.0.1|3.1.2 CPU|3.1.2 GPU|\n| -- | -- | -- |\n||||\n\n1) Import a VDB volume.\n2) Duplicate the volume without moving it.\n3) Render with Cycles.\n\nHere is the test file:\n[#97094.zip](T97094.zip)", "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" ]

[ "X-Ray resulting in a visual mess\nOperating system: Windows 10\nGraphics card: Radeon RX550/550 Series\n\nBroken: 2.92.0\n\nTurning on X-ray on will cause a model which is set to be rendered in front to be incorrectly rendered. It will be displayed using a lot of messed up pixels of various colours.\nSet a model to be rendered \"In front\"\nTurn on X-Ray (Alt+Z)\nDuplicate the model.\nTurn off In-Front rendering for the duplicate model.\nSee the result.[XRay bug.blend](XRay_bug.blend)\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", "Assigning pie menus to mouse clicks using the tweak function causes these menu shortcuts to stop working properly\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.39\n\n\nBroken: version: 2.80 (sub 71)\n\n\nBeen experimenting with creating keybinds and one of those experiments were to try and assign several menus to R click (using L click for select) by using the tweak function in the keymap settings. The idea was to have as many menus as possible on the same keybind to reduce the amount of keys needed, but using this method has proven difficult. \n\n\nWhile I can make standard menus work with tweaks, the pie menus don't work at all. If you manage to get the pie menu to show itself, it will eventually stop all the tweak commands from working unless you open up a menu on a keybind that is not using a tweak function. The second issue is that even when you do get the pie menus to show themselves, nothing can be selected on them, therefore making the keybind completely useless.\n\n\n1) Assign a standard menu and a pie menu to a mouse click (i.e. R click) using the tweak function, which can be set to north and south (just as an example).\n2) Use the new shortcuts to click and drag your mouse in the directions you assigned to to open up each menu (standard menu should be working correctly).\n3) Open the pie menu with this method and try to select any option on said menu, which should cause the pie menu to fail.\n4) Try opening the menus again, but this time none of the assigned menus will show up.\n5) To fix the previous error, open up a menu on a different shortcut (like something on your keyboard) to make the tweak shortcuts be able to appear again.\n6) Repeat the previous steps, which should cause the same error every time.", "Fly and walk navigation in AZERTY issues\nOperating system: windows 10\nGraphics card: rtx 3060\n\nBroken: Blender 3.6.1 (Steam)\n\n\nHello,\nIm on a AZERTY keyboard and the problem is that when i change my movements keybinds for fly (or walk) navigation it keeps repeating the action (even if i unpress the key) for the binds that i changed. For exemple i changed \"forward\" key by Z and when i press Z the camera will keep going forward forever.\n\n- Go in the View 3d fly (or walk) modal keymap settings\n- In \"Forward\" replace W by Z, \"Left\" Q by A, \"Down\" A by Q, \"Z axis correction\" Z by W\n- Go in fly (or walk) navigation mode\n- Try to move with ZQSD, A and E\n- Then when you press S,D or E it will work normaly but if you press Z, Q or A and release the key it will keep going in that direction exept if you press the opposit direction key (S for Z, D for Q, E for A)\n\nThanks for paying attention, lov u <3\n\n", "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\n\n", "Blender 3.0.0 breaks compatibility of rigs with the previous version\nOperating system: Windows 11 Pro 21H2\nGraphics card: Nvidia RTX 3070\n\nBroken: 3.0.0\nWorked: 2.93.6\nBlender 3.0.0 breaks compatibility of rigs with the previous version.\n\n1. Open Agent 327 shot 10_03_B-agent_dodges animation file (10_03_B.anim.blend)\n2. Observe that the rigs are completely broken\n\n\n", "Preset icon overlaps panel header text\nOperating system: Mac 10.9.5\nGraphics card: Macbookpro NVIDIA GeForce GT 750M 2048 MB\n\nBlender 2.8 downloaded today\n\nIn movie editor\nthe text tracking settings is somehow mixed up with a button.\nI can sent a pic if you want.\n\nI am a amateur and English is not my first language, so i'm very sorry if i've wasted your time.\n\nGreetz \nLes", "Hair particles: cannot delete hair particles in particle edit mode until you comb it\nOperating system: Linux-3.10.0-957.10.1.el7.x86_64-x86_64-with-centos-7.6.1810-Core 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.81 (sub 4)\nWorked: 2.79\n\nYou cannot delete all (hit a) hair particles until you comb them. Even more, if you select one hair or several and hit delete, they disappear, but if you then select all the rest and hit delete, all the particles deleted come back.\n\n\n- Open this blend file: [#69487-hair-delete-279.blend](T69487-hair-delete-279.blend)\n- Press {key X} and choose Particles\n\nIn current Blender (2.82 alpha @ 756b9acaf5) hairs get deselected but are not deleted. In 2.79b the hairs are deleted.\n\n**Original steps to reproduce:**\n\nCreate a new hair particle system\nGo into particle edit mode\nSelect all, hit X delete particles -> nothing happens\nDeselect all\nSelect a couple, hit X -> the selected hairs will disappear\nSelect all, hit X -> all the hairs come back visible again\n\nThere's a hair particle system newly created in the attached file.\n[hair_particles_delete_bug.blend](hair_particles_delete_bug.blend)", "Compositor refresh on every 3D view edit and blocks UI\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\nAdjust operator panel for selection operations is greyed out after every operation. When you move cursor out of the input field it's active again. It happens only when compositor is opened and \"Use Nodes\" is selected. See video:\n[Desktop 2019.06.19 - 12.22.31.02.avi](Desktop_2019.06.19_-_12.22.31.02.avi)\n\n - Open attached file: [select_compositor_bug.blend](select_compositor_bug.blend)\n - Use Select > Checker deselect\n # Go to adjust operator panel and change one value. Menu will be greyed out until you move cursor out of input field.\nIt's the same with other selection operations like \"Select Similar\" or \"Select Sharp Edges\".", "Undo/Redo shortcut still active in the Blender File View window\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Beta\n\nUndo/Redo shortcut still active in the Blender File View window\n\n* Open Blender with the default cube.\n* Move the cube a few times.\n* Open the “Preferences” window in the menu “Edit | Preferences...”\n* Then do Ctrl + Z to undo. The undo shortcut still works. It is the same for the redo shortcut.\n\nThe undo/redo is also active from any other windows of the “File” menu like “Open”, “Link”, “Save”, “Append”, etc. All links showing the “Blender File View”.\n\nIn the “Blender File View” window, I noticed that the buttons at the bottom disappear when doing the undo shortcut.\n\nI tried a few other shortcuts like Tab to go to edit mode and G to move the cube. They do not seem to be active when the focus is on the “Preferences” or “Blender File View” window.\n\nThe undo/redo is also active when the “Blender Render” has the focus.\n\nAs a consequence, someone accidentally hitting the undo shortcut will get his work being modified behind the window and probably will not notice.\n\n\n{[F9111517](BlenderFileView_Open.jpg) size=full}\n\n{[F9111519](BlenderFileView_AfterShortcut.jpg) size=full}", "Undo doesn't work with paint mask selection (texture paint vs. vertex/weightpaint)\nOperating system: Linux-5.2.10-arch1-1-ARCH-x86_64-with-arch 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.32.0, 5.2.10-arch1-1-ARCH, LLVM 8.0.1) X.Org 4.5 (Core Profile) Mesa 19.1.5\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nUndo does not work with paint mask selections. The expected behavior here is that undo should work as in other selection modes.\n\nClick on texture paint.\nSelect single image and create a texture.\nTurn on paint masking, and then select the \"select box\" tool.\nclick on a face on the cube to select it.\nPress ctrl-z.", "Keymap system refactor\nListing issues with the current key-map system.\n\nKey-Map System\n--------------\n\n\n- Timers should be removed from the key-map, since they are for internal operations.\n- Action-zones should be removed from key-maps.\n\n\n\nUser Interface\n--------------\n\n- The ability to re-order key-map items.\n\n```\nThis is important as key-map items are handled in the order listed, with some items passing on to key-map items defined afterwards. \n```\n\n- Ability to select from existing operators list instead of typing in a string (similar to selecting ID's bones... etc).\n\n- Other features:\n\n - Remove duplicate key-map items.\n - Show invalid key-map items (missing operators, reference to invalid menu items... etc).\n - Disallow assigning invalid/duplicate key-map items when using \"Assign Shortcut\".\n\n\nOpen Topics\n-----------\n\nThese are larger issues which need design work, which this proposal doesn't (yet) handle, and it's not clear exactly how these would be handled.\n\n- Exporting key-maps looses the ability to access key-map preferences.\n- Mapping keys from keyboards which have keys not found on a US/English keyboard.\n- Workflow for editing and maintaining custom key-maps could be looked into & improved.", "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", "Some bone animations break upon performing unrelated actions\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.2.0\nWorked: Unsure\n\nI have noticed that sometimes, doing random actions will break existing working animations in a blender project, but only for some bones. I'm not even sure what random actions will cause this - I've always had to resort to just loading from the last saved version. However, I do have a way to reproduce this issue almost 100% of the time really easily:\n\n*Open this blender file:\n*Select the armature (It's called \"Armature\")\n*Open the action \"Reload\" in the action editor\n*Play the animation, see that it is working\n*Now, turn on or off the fake user save toggle button (the shield icon)\n*Play the animation again, notice how the wrists no longer move, but everything else still moves.\n\n[template.blend](template.blend)\n\nThis can also be prevented by:\n- open file\n- select the armature (It's called \"Armature\")\n- go to posemode\n- select all bones\n- go back to objectmode \n- continue with the steps above (\"*Open the action \"Reload\" in the action editor\")\n- bug does not occur\n\nNote this does not have to be the the fake user save toggle button (the shield icon), e.g. toggling Manual Frame Range in the Action Editor triggers this, too\n\nworkaround (until this is fixed for good):\n\n- go to posemode\n- select all bones\n- change any setting that triggers re-evaluation of the action (this might be clicking the fake user save toggle button (the shield icon) again, or toggling Manual Frame Range in the Action Editor, or changing a keyframe or curve visibility in the Graph Editor\n- Action is working again\n", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "File browser buttons disappear on undo in another window\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\n- All versions since the new file browser was introduced are affected by this\nWorked: Never\n\nI've tried to save file with CTRL+S and by accident pressed my LMB on a viewport. Because of that mistake, I pasted object in my scene, instead of pasting file name in \"Blender File View\" window. So I tapped CTRL+Z (while still being active in a viewport) and whole panel with buttons \"Save file\", \"Cancel\" in \"Blender File View\" window disappeared. I've tested this on a completely new empty blender file. Pressing on a viewport didn't recreate that effect (probably, because nothing was there). But pressing on outliner or timeline have the same issue.\n\n- Open Blender\n- CTRL+S\n- Press LMB on an Outliner\n- CTRL+Z\n\n[UI bug.blend](UI_bug.blend)" ]

[ "action editor in dope sheet cant be deleted after created new one\nOperating system and graphics card\n\n2.75a hashc27589e\n\naction dope sheet cant be deleted after created new one\n\n1 open blender and add object in the scene\n2 change to dope sheet editor\n3 select action editor mode in dope sheet\n4 click new\n5 click \"+\" to create new one, must click multiple times\n6 delete the previous one or rest of them\nthis file>> [bug Action dope sheet.rar](bug_Action_dope_sheet.rar)" ]

[ "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", "Changing the Orientation of Modifiers\nCurrently, LineArt is created in 3D space, however, the Modifiers can be oriented incorrectly.\n\nIn this example, the Noise Modifier is moving the Grease Pencil points on the Normal but not up and down on Z. There is currently no way to change it.\n\n[Noise - Position.mp4](Noise_-_Position.mp4)\n\nThis is a request for a way to change the orientation of the Modifiers.", "Sculpt brush with texture breaks sculpt tiling\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n\nBroken: version: 2.93.0 Alpha\n\nIf the sculpt brush has a texture enabled with mapping set to *Area Plane*, then tiled strokes break up and do not match properly at the seams.\nIn this example the original stroke is on the right.\n\n\n1 Add texture to a brush\n2 Set mapping to area plane\n3 Enable tiling in the Symmetry drop-down menu\n4 Try sculpting at the seams\n\nOr use the file\n[tiling_bug.blend](tiling_bug.blend)\n\n", "View -> Lock Time to Other Windows does not maintain scale when CTRL+TAB between two animation editor modes.\nOperating system: Manjaro Linux\nGraphics card: nVidia\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nView -> Lock Time to Other Windows does not maintain scale when CTRL+TAB between two animation editor modes. \n\nExpand open the Timeline editor, now adjust the horizontal scale of the view (squeeze or expand), then Ctrl+TAB to swith to Graph Editor mode. Notice the scale does not stay in sych as it does when they are separate windows. ", "Mirror select doesn't select appropriate vertices where there are overlapping verts\nOperating system: Windows 10 Pro\nGraphics card: GTX 1070 + GT710 for extra outputs\n\nBroken: 2019-03-10 22:28\nHash 6fd11a21f5c5\n\n\nCtrl-Shift-M (or using the menu to select mirrored) doesn't select all mirrored verts where there are overlapping verts.\n\n\n[63Stingray.zip](63Stingray.zip)\n\nOpen blend file, hopefully it'll already be in edit mode with the appropriate vertices selected.\n\nShould look like this;\n\n\nFrom there select mirrored from either the select menu, or Ctrl-Shift-M, doesn't matter, and enable the following settings;\n\n\n\nObserve incomplete selection;\n\n\n\nThe area's of incomplete selection are here, where the overlapping underbody verts are in the same location as the verts for the body;\n\n\n\n", "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", "Workbench Shadow Improvement\n### Respect World Space Lighting option\nCurrently, the shadow is always in world space. Use view space orientation when matcaps is used or when studio lights use view space orientation.\n\n### Follow the brightest light\nCurrently, the shadow is not following any of the lights direction in the studio lighting config. Selecting the most bright light seems like a good default. Otherwise, we can add a flag in the studio-lights to tag which one the shadow should follow.\nA toggle option to force the use of the custom shadow direction should be added (disabled by default in new files, enabled in older files).\n\n\n### Follow the matcap\nWhen matcap brightest spot can be extracted, we should make the shadow follow this direction.\n\n", "Generic Rigid Body Constraint Bug\nOperating system: Windows 10\nGraphics card: Radeon RX 470\n\nBroken: 2.83.0\nWorked: Unknown if it ever worked\n\nAngle limit not only doesn't work but causes weird neverending twitching back and forth\nUPDATE:\nTwitching happens for both cases when both rigid bodies are active and when one of them is passive.\n[M0DJ38oWQo.mp4](M0DJ38oWQo.mp4)\n\n1. Add 2 rigid bodies, 1 active, 1 passive animated\n2. Position them active on top, passive on the bottom\n3. Add an empty in between them, add a rigid body constraint to it, select the 2 rigid bodies in its settings, uncheck disable collisions.\n4. Change the joint type to Generic, limit location to 0-0 on each axis.\n5. Play. Now it works, once you select the passive RB and move it it should behave normal.\n6. Undo. Check angle limit on Z and choose some angle range (I had it set to -30 to 30).\n7. Play. Move the passive RB and watch it breaking.\n", "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, ", "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", "Weight Painting intermittent issues with brush, not adding or subtracting weight, not influencing correct areas\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080ti + 3x GTX 1080Ti - Running 4 monitors and a pen tablet at three different resolutions using outputs from two GPUs (4k, 1440p, 1080p)\n\nBroken: 2.81 stable\nWorked: 2.80\n\n\nI have had numerous issues with weight painting in 2.81, however duplicating them has been problematic as this crops up intermittently. In this example, I saved this working file right at the moment I started having problems. Here I can neither add nor subtract weight with the brush in Weight paint mode from a certain distance from the model. \n\nIn other instances, I've had issues with the brush *not painting over the vertices it's over*. I use a hard falloff brush, so anything inside the circle gets painted, anything outside gets nothing. Essentially, it acts like the circle where the brush is being displayed, is not where the circle actually is, if that makes sense.\n\n\n*I tried exporting this to it's own file, but that seems to fix it. It has to be in the full working file I'll provide here. You should hopefully be able to open the file, already be in weight painting mode, with the brush set up, over some masked vertices ready to add or subtract. Try switching the brush to add, and zoomed in fairly close, add some weight, and nothing happens. However, zoom out and do the same thing, and watch weight be added.*\n\nYou can kind of jump around and try rigging other parts of the car, I've been having issues with it off and on for the past few days.\n\n[70sNewYorkers.blend](70sNewYorkers.blend)", "In the VSE Preview - Text \"X & Y\" alignments are not working correctly\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce 820M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 389.12\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIn the VSE Preview - Text \"X & Y\" alignments are not working correctly\n\n1. Opened blender's Video Editing Workspace\n2. I added a text layer in the timeline > the text is placing by default in the bottom the VSE Preview monitor\n3. In the \"effects strip\" panel, I changed the alignment of X & Y. But, it doesn't work properly.\n(e.g. when I selected \"Top\" from the align Y dropdown - The text is aligned to \"bottom\". the same issue in the align X) \n\nPlease check the blend file :\n[vse-text-alignment-issue.blend](vse-text-alignment-issue.blend)\n\n", "Setting the brush radius unit to \"scene\" does not automatically use correct stroke spacing distance\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nThe brush settings have an option to fix the radius to either the view or scene, called \"Radius Unit\".\nIf the Scene setting is used, it will not automatically use the correct spacing distances for the stroke.\nThis needs to be toggled manually with separate stroke setting called \"Spacing Distance\" from view to scene.\n\nIf the viewport orientation is very close to the world origin, rotated towards an object that is further away from the world origin, it will lead to a much higher spacing distance.\n\n[2022-05-13 10-24-15.mp4](2022-05-13_10-24-15.mp4)\n\n**Exact steps to reproduce**\n- Move the default cube 4 units away from the world origin\n- Add a multires modifier and subdivide 5 times\n- Enter sculpt mode\n- Use the draw brush\n- Switch the Radius Unit setting from View to Scene\n- Orient your viewport so that you are positioned very close to the world origin, looking at the cube\n- Sculpt on the cube (Notice the very high spacing distance)\n- Rotate your view around to the other side of the cube (Now the viewport is positioned further away from the world origin)\n- Sculpt on the cube from that angle (The stroke distance should be much smaller now)\n\n- To fix the issue switch the stroke setting \"Spacing Distance\" from View to Scene\n- Retry sculpting from the same angles", "Proportiona editing + X mirroring, has specific verts move on their own, despite not being touched\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0\n\nWhen moving something with proportional editing on (and connected only selected) Together with X-mirror turned on. A seperate mesh's verts will be moved back. Despite not being connected\n\nOpen attached blend file [proportional editing moves verts.blend](proportional_editing_moves_verts.blend)\nmake sure proportional editing is on,\nmake sure x-mirroring is on,\nselect a vert somewhere around the mouth.\nnotice how some verts on the teeth now move back all on their own, despite not being connected or touched.\n\nTurning either proportional editing, or x-mirror off fixes the issue, but it shouldn't be happening even if they're on.\n\n\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" ]

[ "Grease Pencil Ignores 'Stroke Placement: Stroke'\nOperating system: Windows 10 64-bit 2004\nGraphics card: NVIDIA Geforce 2070 Super\nCPU: AMD Ryzen 7 3700X (8-core)\n\nBroken: example: 2.90.1, master\nBroken: 2.83.0\nWorked: 2.82a\nCaused by 29f3af9527\n\nGrease Pencil Ignores **Stroke Placement: Stroke**\nIt Just behaves like **Stroke Placement: 3D Cursor** (When 3D cursor is closer to the viewpoint than the base stroke)\nor partially behaves like **Stoke Placement: 3D Cursor** (When 3D cursor is farther from the viewpoint than the base stroke).\n\nI tried my best to describe it clearly in the video.\nTo summarize, You only have to draw strokes in the 3D space and try **Stroke Placement: Stroke**.\n\nThis is from 2.80\n[GP Stroke Placement on 2.80.mp4](GP_Stroke_Placement_on_2.80.mp4)\n\nAnd This is from 2.90.1\n[GP Stroke Placement on 2.90.1.mp4](GP_Stroke_Placement_on_2.90.1.mp4)" ]

[ "Latest Blender 4.0 not opening\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: blender-4.0.0-alpha+main.b5c89822ac40-linux.x86_64-release\nWorked: 3.6.3 Release Candidate\n\nAfter double-clicking on the \"blender\" starter-folder, it shows what you can see on the picture, before canceling the session\n\nJust try to start 4.0. I guess it's my drivers and noone can confirm, right?\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 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)", "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", "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)", "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```", "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", "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.", "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", "crash when import fbx\nOperating system: Window 10 pro\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc\n\n\nCrash when I imported fbx file \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Particle Edit mode for non hair particles - particles viewport display option crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.79\n\nIn Particle Edit mode, you can enable Particles display in Tool Properties > Options > Viewport Display. Pressing this toggle crashes Blender.\n\nFor convenience use this Blend file:\n[particlespath.blend](particlespath.blend) \n\n - Press the toggle in Tool Properties > Options > Viewport Display called 'Particles'\n - Crash\n\n\n\n", "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", "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 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", "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" ]

[ "File Browser Crash while listing big image folders\nOperating system and graphics card\nWindows 10\nNvidia GeForce GTX 560 with latest drivers as of yesterday\nI am using CPU for Cycles renders.\n1.5 TB Hard Drive\n12 GB of RAM\n\n\nBroken: Blender 2.76 RC1 and RC2 e24ea81 2015-09-23 14:02\nWorked: (optional)\n\nI have a model that saves as a 17 MB blend file. It is mostly simple procedural materials (4 or fewer nodes each) with only three small image textures. If I try to use the Blender file browser to add an image texture and open my root image texture folder that has 212 individual images plus 58 subfolders with images), Blender crashes.\n\nIf I manually move the image textures I want to use from the root image texture folder to a new folder with only a few images (about 25) the textures will load OK.\n\nThe same thing happened with my root HDR folder that has a collection of 408 individual HDR, IBL, IES files except the first time I opened the HDR root folder, the Blender file browser locked up for about 30 minutes before crashing. On subsequent attempts, Blender crashes immediately after opening the root HDR folder.\n\nI've tried uninstalling Blender, deleting all residual folders and files and reinstalling Blender 2.76 RC2 and experience the same problem.\n\nIt appears that there is a limit to the number of images that the Blender file browser can handle. I did not experience this problem with Blender versions 2.75a and earlier.\n\n1. Open with Blender's default cube.\n2. Create a new Diffuse material\n3. Change to Edit Mode and UV unwarp the cube\n4. In the Node Editor, add a Texture Image Node and connect it to the Diffused Node\n5. Click the open button and the File Browser opens.\n6. Navigate to my root image texture folder ( 212 image files plus 58 subfolders with images in them) and open the folder.\n7. The folder opens for about 5 seconds and then Blender crashes.\n\nPerform the same steps with a folder with only 25 images, and it loads the image without any problem.\n\nRegards, \nBMF\n", "File Browser Crash while listing big folders in preview mode (fonts, images...).\nWindows 10\nNvidia GeForce GT 750M with latest drivers version 10.18.13.5362\nI am using CPU for Cycles renders.\n750 GB Hard Drive\n16 GB of RAM\n\nBroken: Blender 2.76 RC1 and RC2 e24ea81 2015-09-23 14:02\nWorked: Blender 2.75a c27589e 2015-07-07 14:56\n\nI am a chinese blender user, and I downloaded Blender 2.76 RC2 yesterday. When I try to modify the interface font in the User Preferences window, I open the file browser and navigate to the system fonts folder with the thumbnails option enabled. Then I scroll down to find the font, but suddenly Blender crashed.\n\nI tried to add a new text object, and modify the fonts with the file browser, the same issue(Blender crashed) happened again.\n\nMy system font folder has 745 font files with 623MB disk space.\nI tried to creat a font folder with161 font files and 368MB disk space, and then tested the file browser in preview mode, Blender did not crashed again.\n\nIt appears that there is a limit to the number of files that the Blender file browser can handle in preview mode. I did not experience this problem with Blender versions 2.75a and earlier.\n\n1. Open with Blender 2.76 RC1 or RC2;\n2. Creat a simple text object or enter the User Preferences window, and click the open button to modify the fonts.\n3. Navigate to system fonts folder(745 font files with 623MB disk space) and scroll down to find proper font.\n4. Blender crashes when I have not scrolled down to the end of the folder.\n\nPerform the same steps with a folder with161 font files and 368MB disk space, and it loads the file without any problem.\n" ]

[ "Grease pencil over geometry occlussion problems\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.5\nBroken: version: 3.0.0 Alpha\n\nGP lines get incorrect occlussion in the render while looking fine in the viewport\n\nThe problem displays differently in the following 2 scenarios:\n\nThis file has a grease pencil stroke close over (but not really touching at all) a piece of geometry\n[GP Aliasing.blend](GP_Aliasing.blend)\nViewport Rendering\n\nRender\n*The line looks jagged in the render*\n\n\nThis file has a grease pencil drawing far behind a piece of geometry\n[Occlussion.blend](Occlussion.blend)\nViewport\n\nRender\n*The drawing that should be occluded is completely visible*\n\n", "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", "C and V keys pressed while drawing a Grease Pencil stroke unchangeable in keymaps\nOperating system: Windows 10\nGraphics card: RTX 3070\n\nBroken: 3.0.0\nWorked: n/a\n\nWhile in the middle of drawing a stroke, pressing C and V keys toggle guides on and off. \n\nThe C and V keys can be bound to something else in preferences, but whatever you bind them to, pressing them while in the middle of drawing a stroke still turns the Guides on and off. I can find no listing for these shortcuts in the Keymaps section.", "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)", "Pivot point \"Active Element\" not functional for grease pencil strokes\nBroken: 2.83.10\n\nPivot point setting \"Active Element\" is not functional when used for grease pencil strokes.\nThis mode is nice for foreward kinematic rotations of say legs.\n\n- Open attached file\n- In edit mode, select pressing shift to have selected points and one active.\nEven with pivot point set to \"Active Element\", notice that the Transform Gizmo does not jump to the last selected point (the active one).\n[pivot bug.blend](pivot_bug.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-", "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)", "Sculpt: Grid overlay for Grab active point do not work.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nThis seems to be issue only with Nvidia GPUs on windows.\n\nBroken: version: 3.0.0 Alpha\n\n\nGrid overlay for Grab active point do not work.\n[2021-07-18_18-56-46.mp4](2021-07-18_18-56-46.mp4)\n\n\n**Steps to reproduce**\n[#89942.blend](T89942.blend)\n\n- Open file\n- Check if wireframe overlay is drawn under cursor\n\nWhat fixes this is to have any transform gizmo visible while using brush, then it works until Blender is restarted.\n\n\nFrom #92703:\n\n> This was proposed on the blenderartists thread, I have no idea if it works or if it could broke the preview on the AMD cards\n>  \n> If you know how to compile you can fix it by erasing ! from the line 1157 : if (!depth_test) {\n> to read like so: if (depth_test) {\n\n\n", "Grease Pencil Draw Tool Settings displayed in the wrong context\nversion: 2.80 (sub 74), branch: master, commit date: 2019-07-05 21:52, hash: a0f3...\nbuild date: 2019-07-06, 01:03:01\n\n\n\n**To reproduce:**\n\n - Create a Grease Pencil Object\n - Enter Draw Mode\n - Display tool settings, either in the header or the properties window\n - In the toolbar, click on the Erase or Fill tool\n - Now click on one of the Add tools (Line, Arc, Curve, etc.)\n - Look at your tool settings\n\nNote that when you switch from the Erase or Fill tool to an Add tool, the settings do not change to the correct ones! Instead, the settings or the Erase or Fill tools remain. You have to select the draw tool before selecting an add tool in order to refresh the settings. \n\nThis bug appears for the tool settings in both the properties window and the header.", "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", "Overlay-Next\nUpdate Overlay engine to leverage the new capabilities of the new draw manager.\n\nRequires #102177 (Draw: Selection Next)\n\n#### Complex:\n- [ ] Armature\n- [ ] Edit Mesh\n- [ ] Edit Curve\n- [ ] Edit Uv\n- [ ] Gpencil\n- [ ] Selection Outlines\n- [ ] Wireframe\n\n#### Medium:\n- [ ] Line Anti-Aliasing\n- [ ] Particles\n- [ ] Sculpt\n- [ ] Volume\n\n#### Easy:\n- [ ] Attribute Viewer\n- [x] Background\n- [ ] Bounds\n- [ ] Curves\n- [ ] Camera\n- [ ] Edit Text\n- [x] Empties\n- [ ] Facing\n- [ ] Force Fields\n- [x] Grid\n- [ ] Lattice\n- [ ] Lights\n- [ ] Light Probes\n- [ ] Relation Lines\n- [ ] Speaker", "Blender 3D shift+RMB \"set 3D cursor\" not sensing strokes made with the grease pencil nor strokes made with the annotation tool\nOperating system: Windows 10\nGraphics card: GTX 1060 6gb (Idk if this is very relevant lol)\n\nBroken: 2.82 BETA, 689a873029b9, master, 2020-01-15 21:07\nWorked: -\n\nBlender 3D shift+RMB \"set 3D cursor\" not sensing strokes made with the grease pencil nor strokes made with the annotation tool\n\nAdd a stroke, hover it with your mouse and press your \"Set 3D cursor\" hotkey combination (by default Shift RMB).\n\n**Expected result**\nWhen doing just this, but when hovering your cursor/mouse over a mesh object instead, the 3D cursor will be set on the surface of the mesh object right where the cursor/mouse is hovering over that mesh/object. As the grease pencil is rather new, Im guessing making this react with the grease pencil strokes were just something that was forgotten when implementing it.", "\"Use for Rendering\" tickbox in View Layer Properties only properly automating if View Layer is active\nOperating system: Win10 Home 64\nGraphics card: rtx3070\n\nBlender Version\nBroken: 2.93\nWorked: 2.80\n\n**Description**\n\n\nWhen you automate the \"Use for Rendering\" tickbox on a view layer, its change does not update during F12 renders unless you have that specific view layer open in your scene. \n\nVideo explanation:\nwatch?v=Prp5Vpeu5XE\n\n**Steps to reproduce**\n[#89235.blend](T89235.blend)\n\n- Open file\n- Render image - 3 cubes are visible\n- Change active view layer to \"RED LAYER\" and back to \"GREEN LAYER\"\n- Render image again - 2 cubes are visible\n\n", "Grease pencil eyedropper doesn't sample correct vertex color.\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.30\n\nBroken:\n```\nversion: 2.90.0\nversion: 2.92.0 Alpha\nversion: 2.83.9\n```\n\nWorked: (unknown maybe never)\n\nWhen using the grease pencil eye dropper with filmic color management selected; the sampled color is different than the original vertex stroke color. \nWorks as expected with standard color management selected\n(Note this is confusing to new users as they expect to color sample and return the previous color of their previous stroke.)\n\n\n - Start with a new file\n - Set color management to filmic.\n - Add grease pencil object\n - Enter Draw Mode\n - Paint in vertex color mode using a lighter color.\n - With a blank palette use the color eyedropper tool on the stroke you just made\n - now paint with the sampled color in the palette\n - result should be slightly darker than the first stroke.\n\nvideo reference:\n**with filmic enabled:**\n[Desktop 2020.11.25 - 02.35.06.03.mp4](Desktop_2020.11.25_-_02.35.06.03.mp4)\n\n**with filmic disabled:**\n[Desktop 2020.11.25 - 02.36.30.06.mp4](Desktop_2020.11.25_-_02.36.30.06.mp4)\n\n\n", "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" ]

[ "Grease Pencil populate draw manager method is not called when Cycles Render mode with Overlays OFF\nLast source compiled at 27/05/2019 \n\nI have tested with prints the populate method and when set Cycles render and disable overlays, the method never is called.\n\nI have tested with a simple Suzanne 2D\n\nTo reproduce.\n\n1) Open default scene\n2) Add Suzanne 2D\n3) Set to Cycles\n4) Set Render View mode\n5) Disable overlays" ]

[ "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", "Sculpt mode pivot ignores object transform when pivot mode is \"Active Element\"\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102\n\nBroken: version: 3.4.0\nWorked: unknown\n\nWhen the pivot mode is set to \"Active Element,\" the sculpt mode pivot location ignores the transform of the object.\n\n- move and/or rotate default cube\n- Set `Transform Pivot Point` to `Active Element`\n- To see the pivot position, enable `Move` Object Gizmos (in popover of `Viewport Gizmos`)\n- enter sculpt mode. (note that the pivot has moved back to origin)\n- Go to {nav Sculpt > Set Pivot} and run any of the `Set Pivot Operation` operators (such as `Pivot to Origin`, `Pivot to Unmasked`, `Pivot to Mask Border`, etc)\n\nThe pivot location will be relative to the world origin, not the transformed object (which is also active).\n\n---\nTo be honest, it's strange to me that operations such as \"Set Pivot -> Pivot to Mask Border\" generate a pivot that's different for different pivot selection modes in the first place --- it's very unintuitive for the pivot location to not appear at the actual (world space, post-transform) mask border when you run an operation that's supposed to set it to that location. I haven't thought through the nuances of sculpt pivot vs 3d cursor vs pivot mode interaction, though, so maybe there's a good reason for this --- in which case take this as UX feedback that I spent an hour trying to figure out why my pivots weren't working before finding this issue :)\n\nAt any rate, the Active Element behavior seems broken", "Needs two clicks with Ctrl or Shift key to deselect an item from a list of selected items\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0\n\nNeeds two clicks with Ctrl or Shift key to deselect an item from a list of selected items.\n\n\n* Open the project file “OutlinerSelectItemWithCtrl.blend” in attachment as a starting point.\n\nThe same problem happens in different views with different details.\n\nOutliner:\n* Select the entire collection of objects from the collection “Item List”. You can click the “Cone” object, hold the Shift key and then click the “Torus” object to select the entire list.\n* Then hold the Ctrl key and click the Cylinder object to deselect.\n* The item’s color get a lighter color, but it is still not excluded from the whole selection.\n* Clicking a second time on the object really deselects the object.\n* If clicking the first item of the selection (which is the Cone is this example), it is deselected properly.\n\n3D View:\nThe Shift key is used to select/deselect objects individually. It is pretty much the same issue. It requires two clicks on the same object to really deselect the object, whatever the order of the object in the selection. However, if one object has already been selected before deselecting everything, then the same object gets selected with an additional highlight from the new selection (dragging the mouse cursor in the viewport).\n\nShading view:\nPretty similar to the 3D view.\nIf I deselect all the nodes (Alt + A for example) and I drag the mouse cursor to select all nodes, the last selected node is highlighted in white. If I click the node highlighted in white while holding the Shift key, the node is deselected. However, if I do the same thing for the other nodes, it selects the node with a white highlight and I have to click a second time on the same node to really deselect it. The behavior of the last selected item is also present in the 3D View, but not for the Outliner.\n\nThe Compositing view has the same problem and I suspect that the Geometry Node view has the same too (I haven’t tested the last one).\n\nIn general, it requires two clicks to deselect an object with the normal behavior.\n\nThe first click behaves as an “add to selection” click unless the object already had a selection before completely creating a new selection.\n\nIn all cases, there is an issue with deselecting (or excluding) and single object from a selection of objects in different views. As a reference how it should behave correctly, the Windows Explorer in Windows is able to deselect a single item on the first time it is clicked.\n\n[OutlinerSelectItemWithCtrl.blend](OutlinerSelectItemWithCtrl.blend)\n\n[Deselect_Issue.mp4](Deselect_Issue.mp4)", "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", "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.", "Transform constraints not working with rigid body simulation\nOperating system: Ubuntu 16.04\nGraphics card: MSI 1080Ti\n\nBroken: 2.80, 337eb8c1de4c, master, 2019-03-27,\nWorked: 2.80, 8beab3e33922, master, 2019-01-21\n\nThe new blender release (as of hash: 936014ea8c74), seems to have disabled constraints from animations. \nIf you set a Minimum Z for a rigid body object, it will ignore that minimum.\n\n - Open the default room.\n - Place the cube at (0, 0, 5)\n - Add “Active” rigid body to the cube\n - Add “Limit Location” object constraint and check minimum Z = 0\n - Press play\n\nIn previous versions, the cube would drop and stop at z = 0, but now it falls to -infinity.", "Stronger binding of Active and Selected\n**Context**\n\nFor many things that can be *Selected*, there is also a state called *Active*. There can be 0..∞ *Selected* things, and 0..1 *Active* things. This applies to objects, bones, fcurves, fcurve keys, mesh elements, and more. These will just be referred to as *thing* in this task to avoid having to repeat that entire list.\n\nThe *Selected* and *Active* states are independent, so there are four states a thing can be in:\n\n| | Not Selected | Selected |\n| -- | -- | -- |\n| Not Active | x | x |\n| Active | x | x |\n\n**Problem**\n\nThere are two states possible that can cause issues:\n1. **There are *Selected* things, but none of them is *Active*:** a sidebar/numerical/properties panel will not show information, and generally be empty without explanation why.\n2. **There is an *Active* thing, but it is not *Selected*:** this is not shown in the UI, as there is no separate color for this situation; all *Active* things are shown the same way regardless of them being *Selected* or not. This causes confusion and unexpected behaviour, and also doesn't allow for an actual clear use of this possibility.\n\n**Related Reports**\n\nThese reports are examples of confusing situations where the disconnect between *Active* and *Selected*. The list is not exhaustive, and may be expanded later.\n\n- #14429 (selected bone is not active)\n- #65219 (Objects don't become active object if they are selected by a box)\n- #68647 (objects selected using box select cannot be moved to collection if there is no active object)\n- #81922 (The Graph Editor doesn't show any curve of the Armature (if in Pose mode, but armature unselected, with box/circle/lasso tools))\n\n**Proposal**\n\nThis design task proposes linking *Active* and *Selected* such that:\n1. If there are *Selected* things, there is always one of those that is the *Active* thing.\n2. If a thing is *Active*, it is also always *Selected*.\n\n**Hurdles to Overcome**\n\nRule 1. above requires that one of the selected things is marked active. There is not always a unique, obvious choice here, for example when box-selecting multiple things at the same time. In this case the choice should at least be consistent so that users know what to expect after a while. The thing closest to the mouse cursor (when using the mouse to select) could be a reasonable choice.\n\nRule 2. above can be dealt with in various ways:\n- Create a function that returns the *Active* thing, and make it return nil when that thing is not also *Selected*. This is what was implemented for the Active Keyframe (983ad4210b). This has the downside that now nothing is active, breaking rule 1 and forcing the selection-changing code to pick another thing to become *Active*.\n- Refuse deselection of the *Active* thing.\n- ... something more elegant.\n\n**Goal of this Design Task**\n\nThe goal of this design task is to answer the following questions:\n- Is there an agreement that the current situation causes issues, and that having a stronger correlation between *Active* and *Selected* is a good thing?\n- Is there an agreement that the proposed two rules are the way to go?\n- How do we implement these rules in a way that makes sense to artists?\n- Can we implement this in a way that can be reused by all the affected parts? Some unified selection/activation API that can be implemented for different data types?\n", "Objects in front of the selection stay in front in wireframe mode\nBroken: version 2.80+\nWorked: version 2.79\n\nIn blender 2.79, the wireframe of objects selected or in edit-mode was drawn in front of the wireframe of all other objects in the scene.\nIn blender 2.80 onwards, this doesn't happen anymore.\n\nHere's a model shown in 2.79b, with my usual theme:\n\n\nThe object in edit mode is behind the objects seen with gray wireframe. But because it is in edit mode, it is drawn in front of the others.\nThe same is true if the object is in object-mode but selected.\n\nNow compare the same model in 2.8x:\n\n\nHere the same object is seem in edit-mode. Now it is drawn behind everything else, which creates a noisy, low-contrast appearance, making it hard to see and sometimes hard to edit. \nSometimes it forces me to rotate the view to get other things out of the way (especially if the foreground objects have a lot of detail/geometry).\n\nIf you zoom in real close on an area where a foreground object overlaps the selection, snap a screenshot, and then scale or zoom the image, you can see how the foreground object is definitely being drawn in front of the active one:\n\n\nBottom line: In my opinion, in a normal view mode like Solid or Lookdev/Material, the selection of course should remain behind everything else (unless changed via its Object properties), but in Wireframe view mode the selected object should appear in front of other stuff.\nPerhaps an option is needed the Preferences to force the old 2.79b draw order.\n\n- Open attached file\n- Change the wire theme to something gray (or use the attached theme).\n[wireframe_in_2_79.blend](wireframe_in_2_79.blend)\n[classic-look.xml](classic-look.xml)\n\nThe original model is probably too big to upload here: Hypercube%20printer%20model%20(320x320%20bed,%20540x510x540%20frame).blend", "Rigid body Bounciness parameter not functioning\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: 2.92 and version: 3.0.0 Alpha\nWorked: 2.83.13\n\nIn recent Blender versions the bounciness parameter of rigid bodies does nothing.\n\nOpen attached file, press space to start animation.\nOlder versions: ball bounces\nRecent versions: ball falls and immediately comes to an halt when it hits the surface of the cube.\n\n[Bounciness bug.blend](Bounciness_bug.blend)", "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", "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.", "Asset drag & drop snapping: Limitations\nLimitations for the drag & drop snapping implemented in the `asset-browser-snap-dragging` branch.\n\n* - [x] The bounding box drawing uses bounding box based snapping, actually dropping the object uses the origin. (279f271a0a)\n* - [ ] No way to select an up-axis (e.g. for putting frames on a wall).\n* - [ ] No way to rotate the object while or after dragging.\n* - [ ] Rotation of the dragged object is not applied.\n* - [ ] Snapping uses rotation of the snapped to object.\n* - [ ] Snapping uses normals of the snapped to surface, which are often flipped. Should probably work in both positive and negative normal direction?\n* - [ ] Not implemented for collections yet.", "UV Editor face select mode fails to select ngons reliably\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.4.1\nWorked: never? (2.83 fails too)\n\nUV Editor face selection mode fails to select ngons reliably, because it uses face dot based selection, which can not be turned off. I was told to report scenarios where face dot based selection fails to work as bugs, so I am doing so here.\n\n1. Open the attached file\n2. Select the mesh object, enter the edit mode, and in the UV editor, switch selection mode to face\n3. Attempt to select some of the larger ngon UV face\nResult: The selection of larger ngon UV faces fails in many cases\nExpected The UV faces under the mouse cursor are selected when clicked on\n\n[UVSelectBug.blend](UVSelectBug.blend)\n[2023-02-06 12-20-58.mp4](2023-02-06_12-20-58.mp4)", "Outliner: Sync Selection off not working when clicking LMB on data object name\nBroken: version: 3.0.0\nBroken: version: 2.91.2 (works correctly on meshes for some reason till worked version)\nWorked: version: 2.82\n\nWhen `Sync Selection` is off it's still possible to sync selection by clicking on object data name (+ small margin). Additionaly clicking on object data name will sync it with relevant slot in Properties editor. This bugged area becomes slightly longer to the left when active, see video.\n\n1. Open default scene.\n2. Turn off `Sync Selection` on Outliner.\n3. Deselect onjects in your scene by clicking on empty space in 3D Viewport.\n4. Select objects or object data in outliner without clicking on their name - see that `Sync Selection` is off\n5. Select objects or object data in outliner by clicking in their name - see that now parent onject is selected in Outliner aswell as in 3D Viewport.\n[Outliner Sync Selection off bug 2021-12-15 20-45-35-213.mp4](Outliner_Sync_Selection_off_bug_2021-12-15_20-45-35-213.mp4)", "Outliner: Object selected/deselected when clicking with RMB on it's object data [`Sync Selection` option causes this]\nBroken: version: 3.0.0\nBroken: version: 2.91.2\nBroken (differently): 2.90.1, 2.83\nWorked: 2.82\n\nWhen clicking with RMB on *some* object data in outliner (can confirm for materials), parent object is selected/deselected (both in outliner and in 3D viewport). That can lead to undesired actions. For example, when click RMB on material object data from a cube and choosing `Delete` you'll get one of the following:\n- Delete only material object data if parent object is not selected\n- Delete cube object itself **and** material object data if parent object is selected\nMesh/ligh/camera object data also have this \"parent object selection/deselection\" behavior but for this object data it's not so apparent in terms of functionality since in both cases mesh/light/camera object data is deleted and object can't exist without those so it's deleted too.\nModifiers and constraints are handled consistent with context menu - deleting only modifier - although it's something to be discussed since it shows that parent object is selected.\nFor shortcut behavior there is already #94062.\n\nIn 2.90.1 core issue is same but behave slightly different - it'll not always change selection/deselection, can provide details if requested.\n\nFor materials:\n1. Open attached file. You'll see two objects with same mesh object data.\n2. Repeatedly click with RMB on material object mata in outliner to see parent object selected/deselected.\n3. Choose `Delete` from context menu when parent object is selected - one of the objects is deleted and one material that was clicked on (you can see it on other objest mesh object data since they share it).\n4. Undo\n5. Choose `Delete` from context menu when parent object is not selected - only one material is deleted.\n\nFor showcasing mesh/light/camera data behavior:\n1. Open attached file.\n2. RMB on `Sphere` mesh object data to a point where parent object is either selected or deselected.\n3. Choose `Delete` from context menu - in both cases all objects are deleted.\n[RMB outliner selection bug.blend](RMB_outliner_selection_bug.blend)" ]

[ "MacOS - left-click object selection is broken (object mode)\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha (local compile)\nWorked: 3.0.0 Alpha\n\nIn Object mode, left-click select does not select an object. CTRL-left-click does, but only when clicking near an object's origin.\nIn Edit mode, left-click selection seems to work fine for vertices, edges and faces.\n\n - Start Blender, the default scene appears.\n - Left-click the default cube, the default light or the default camera. Clicked objects are not selected.\n - CTRL-left-click the objects away from their origin, objects are not or not consistently selected.\n - CTRL-left-click the objects at or near their origin, objects are selected\n\n\n", "selecting in object mode works \"sometimes\"\nOperating system: macOS-12.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.3\n\nBroken: version: 3.0.0\n\nI have this problem only in Blender 3.0. Never on 3.1 or older versions.\n\nSo if i try to select the default cube just with a click it works only in 30% of all cases. But ONLY in object mode. If i change with tab in edit mode, i can perfectly select all vertices.\n\nEven box select doesn't work always.\n\nI have no idea what this can be...\n\ni downloaded the newest version of today.\n\nYes, i restarted blender several time. Restarting computer doesn't help either.\n\n[select_bug_in_3.0.mov](select_bug_in_3.0.mov)\n\n", "Selection of objects by clicking on them not working\nOperating system: macOS Monterey 12.1\nGraphics card: m1 max 10 core cpu and 32 core gpu\n\nBroken: (v3.0 for apple silicon, f1cca3055776, master, 2021-12-02, 18:35)\nWorked: (v3.0 for intel, f1cca3055776, master, 2021-12-02, 18:35)\n\nHi, Im new to blender on Mac and trying to adjust to this workflow. I noticed that in the 3.0 stable version selecting an object in viewport requires me to click slightly below the object to be selected. This distance keeps on changing for different objects (especially the scale of object). This problem only seems to be there in object mode in 3d viewport and I've tried multiple mice but with no success.(I currently used the mx master 3 from Logitech) \n\nJust start up blender and try selecting the default cube. The pointer needs to be at the center of the cube or below it. It won't get selected if the pointer is just above 3d cursor at world origin. This becomes especially difficult if the light or camera needs to be selected. I tried enabling and disabling OpenGL Depth Picking with no success. ", "Selection in the 3d view is broken in build from Xcode 13\nOperating system: macOS-11.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha\n\nUsing the default keymap, clicking to select items in the 3d view doesn't work\n\n - Compile Blender using Clang 13. See #91680#1225851\n - Open latest master using Factory settings, is Blender Default keymap set to left click select\n - Click on the default camera or light\n - Nothing happens\n\nBox select still works, but single clicking is broken. Bug also applies to the IC keymap. \n\n" ]

[ "VSE strip can't be seen with frame all\nOperating system:\t\tWindows 7\nGPU:\t\t\t\tRadeon Vega 64\nGPU Software Version:\t20.4.2 (2020.0515.1537.28108)\nCPU:\t\t\t\tIntel Core i7-5960X\n\n**Blender Version(s)**\n*(listed are versions tested)*\n\nWorking:\t\t\t\t`2.79 (sub 00), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68b, type: Release, build date: 2018-03-22, 09:59 AM`\nBroken:\t\t\t\t` blender-2.90.0-ba2d1c889819-windows64` (BF Build Bot)\n\n\nChannel 32 can't been seen with Frame All\n\n\n|  |  |\n| -- | -- |\n\n\nHave at least 2.00 Display Scaling\n\n[Channel_32.blend](Channel_32.blend)", "When changing the node type in material, sockets of different node types are reused\nOperating system: MacOS\nGraphics card: Apple M1\n\nBroken: main\nWorked: don't know\n\nShader nodes that have the same input sockets can have different default values.\nBut if you switch between shader nodes in the material interface, then the default values will first of all be copied from pre-existing socket of a node of a different type. Because of this, default values may not be used and may look strange.\n\nIn the default scene, assign Glass BSDF material to the default cube, and check the \"Roughness\" field. Now assign another material without \"Roughness\", such as Hair BSDF, then assign Glass BSDF material again and check the \"Roughness\" field.\n\n", "Segfault after F12 render with multi-GPU Intel ARC A770 and experimental oneAPI packages on Debian\nOperating system: Linux-6.4.0-1-amd64-x86_64-with-glibc2.37 (Debian sid)\nGraphics card: two identical Intel ARC A770 Limited Edition 16GB\n\nBroken: 3.6.1, 4.0.0 Alpha, branch: main, commit date: 2023-07-25 19:23, hash: aebc743bf1c7\nWorked: 3.4, 3.4.1, 3.5.1\n\nSegfault when rendering Victor benchmark scene with F12 with second Intel ARC A770. This happens only when the second GPU is chosen as rendering device in Cycles. If both GPUs are selected first one seems to work correctly, but the second one causes a crash/error.\nEmbree on GPU does not seems to matter.\n\nBoth F12 and viewport renders with the second GPU give:\n`oneAPI kernel \"shader_eval_curve_shadow_transparency\" execution error: got runtime exception \"Native API failed. Native API returns: -50 (PI_ERROR_INVALID_ARG_VALUE) -50 (PI_ERROR_INVALID_ARG_VALUE)\"`\n\nRelevant info:\nI'm using following packages from experimental sources (I'm impatient I know :) ), so this crash might be very well caused by their incompatibility with Debian sid:\n`libigc1` - 1.0.13822.1-1\n`libigdfcl1` - 1.0.13822.1-1\n`intel-opencl-icd` - 23.13.26032.7-1\nRest of the packages, including all dependencies are from Debian sid.\n\nFull backtrace:\n\n```\n(gdb) backtrace full\n#0 0x0000000001cfee77 in ?? ()\nNo symbol table info available.\n#1 0x0000000001cffab9 in ?? ()\nNo symbol table info available.\n#2 0x0000000001b0fa9c in ?? ()\nNo symbol table info available.\n#3 0x0000000000f376a3 in ?? ()\nNo symbol table info available.\n#4 0x00007fffebaa63ec in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444\n ret = <optimized out>\n pd = <optimized out>\n out = <optimized out>\n unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737147199792, -8317621660586406251, -286296, 11, 140737488344416, 140734520795136, 8317937541230038677, 8317594907036290709}, mask_was_saved = 0}}, priv = {\n pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}\n not_first_call = <optimized out>\n#5 0x00007fffebb26a1c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81\nNo locals.\n(gdb)\n```\n\n1. On Debian sid install experimental packages mentioned above.\n2. Set second ARC GPU as a rendering device in Blender. \n3. Open Victor benchmark scene.\n4. Hit F12 and wait for the crash.", "Shading or Lighting Discrepancy issue\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.97\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nSo I’ve been having this problem since working in 2.8 and I don’t have a clue what could be causing this issue but I went and stripped down a project as simple as possible trying to isolate the root cause. It seems its a mesh that has an emissive material and when I disconnect the node or hide the mesh the problem disappears. Weird thing is that the brighter version is when hiding mesh number 2. I am attaching the file.\n\nYou will see how the tone changes. This never happened to me after so many years using Blender until now already in a few projects in 2.8. \n\n- Open attached file.\n- Render once using slot 1.\n- Hide mesh 2 or disconnect the emissive node.\n- Render again using slot 2.\n# Toggle with J\n\nNotice the different lighting between each result.\n\n[Shading Issue - Simplied.blend](Shading_Issue_-_Simplied.blend)", "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", "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", "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", "Black artifacts on smooth surface in 2.79 64bit daily build\nOperating system: Windows 10\nGraphics card: RTX 2080Ti\n\nBroken: blender-2.79.0-git.d7cecc2ba3f6-windows64\nWorked: 2.79b\n\n\nThe software renders black artifacts on a smooth surface. This happens both in the rendered preview and in the final render. Artifacts disappear when smooth is not applied.\n\n\n\n\n\n\n\nJust go in rendered preview mode in the editor, or just F12 to see the artifacts in the render.\n\n[bug report.7z](bug_report.7z)", "Shadow caustics visible through colored glass has intensive, solid color for directional/sunlight and are probably too dark for spotlight/pointlight\nOperating system: Windows 11\nGraphics card: GTX 1070 Ti\n\nBroken: 3.22 master\nWorked: none\n\nThis happens when transparent object intersects with diffuse one and caustics are visible though volume. I know that MNEE doesn't work with volumes, but I think this might be a bug.\nFor directional light and sunsky system caustics are colored to pure red, green or blue or are just white. No other colors are possible. Spotlight and pointlight work, but color of intersected primitives differs substantially from not intersecting ones when looking thought them. This is especially visible on the left upper sphere that has only slight tint. Hope this is useful.\n\nmnee nishita sunsky:\n\n\nmnee directional light:\n\n\nmnee spotlight:\n\n\n\n1. Create an object casting caustics like sphere over default cube.\n2. Create transparent material for sphere that consists of two shaders, glass and volume, adjust volume color to something darker then white\n3. Turn on caustics for light and for objects, render in viewport.\n4. Move the sphere so it intersects with the cube, see the result.\n5. Switch light into directional mode and try to adjust volume absorption color.\n\n...or just open attached file and render. Lighting is set to nishita sky, but both spotlight and directional light are added and hidden.\n[mnee_test_master.blend](mnee_test_master.blend)", "\"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", "GPU texture baking with large tile size fails\nOperating system: Windows 10\nGraphics card: Vega56\n\nBroken: 2.90.1\nWorked: 2.83.8\nNot sure if this was a particular commit (or if libraries changed at that time) but this broke between 51ac411ce8 and 5c5a638b57\n\nI was trying to bake 8k emissive map but it doesnt work so i was searching for some error about hour a then try to make 4k emissive map and everything worked jsut fine with same settings, only thing i change was resolution of image from 8k to 4k. After this i try again bake 8k emissive but doesnt work image was empty so this must be some sort of bug.\nBased on the default startup or an attached .blend file (as simple as possible).\n[bug.blend](bug.blend)\n\nThis file has its tile size at 8192x8192.\nWith a tile size of 4096x4096 it works fine.", "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", "Working sliders are faded in the overlays panel\nBroken: 3.0\n\n**Short description of error** \nthe wireframe and wireframe opacity sliders are faded in the overlays panel even when they're working.\n\nFor better visibility, delete the cube, add a suzanne, press ctrl+3 to subdivide it, then apply the modifier.\nIn the Object Properties, under viewport display, turn on \"show edges\" OR set the object to \"Display As: Wire\".\nIn the viewport's Overlays panel, drag the wireframe threshold and wireframe opacity sliders. Make sure that you are in solid shading and the wireframe option is off in the overlays panel. \nThe sliders are faded even though they are working.", "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", "Blender freezes with Metal render device\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.5.0\nWorked: None\nAlso Tested: 3.5.1 RC (April 01, 01:59:41, `6fa464d18971`)\n\nBlender freezes after a few seconds when I enable the Metal Render Device in Preferences, switch to Cycles with GPU Compute and switch Viewport Shading to Rendered.\n\n1. **Do not** delete the default cube\n2. Switch to Metal (GPU) Cycles Render Device in Preferences > System\n3. Set GPU Backend to Metal\n4. Switch Render Engine to Cycles and device to GPU Compute\n5. Switch Viewport Shading to Rendered\n6. Wait for Cycles to compile shaders\n7. Look around for a few seconds\n8. Blender Freezes\n\n" ]

[ "Regression - OpenCL - some shaders don't render correctly\nWin 7, R9 280X with Radeon Software 16.1.1\n\nBroken: 2.77\nWorked: 2.76b\n\nSome shaders like water will not render correctly any more\n\nOpen Pabelon Barcelona scene from the cycles benchmark suite with 2.76b and 2.77, switch to \"GPU Benchmark\" scene, hit F12, you get this:\n\n2.76b, correct:\n\n\n2.77b not correct:\n\n\nNote that it's the exact same scene, the change in trees/flowers position is due to broken particle system (by the way, it would be good to remove any multithreading to make it more stable, because the new system is not coming in a foreseeable future?)\n", "Blender 2.77 Cycles Glass doesnt work\nWindows 8.1\nAMD FX 8350 Black\nSapphire r9 290 tri-x\n8gb ram\nasus m5a97 evo r2.0\n\nBroken:Blender 2.77, glass material in cycles renders glossy when i use my graphic card.\nWorked: with cpu usage\n\nThe glass material is rendered as a glossy material when i use my graphic card to render, it happens in the viewport and also when i press 'render'.\n(It worked when i use other Blenderversions, and i had never such problemes)\n" ]

[ "Alpha mode 'Straight' on Image Texture node behaves differently between Cycles and Eevee\nOperating system: Windows 10 Pro x64\nGraphics card: GTX 1080Ti for display, RTX 3090 for render\n\nBroken: 3.3.1\nWorked: I don't know\n\nWhen the `Alpha` property is set to `Straight`, the result is different between Eevee and Cycles.\n\n\n- Open the .blend file provided\n- Set one of the viewports to Material Preview and the other to Rendered\nNote that the results of the images are different\n[alpha_mode_eevee_vs_cycles.blend](alpha_mode_eevee_vs_cycles.blend)\n\nOriginal file\n[test leaking_ori.blend](test_leaking_ori.blend)\n", "Collada exporter's triangulation option messes up custom vertex normals\nBroken: v3.4.1, v3.2.0, v3.1.2\nWorked: Never, as far as I can tell.\n\nWhen using the Collada exporter to export a mesh with custom vertex normals (with the exporter's triangulation option on), for each quad, one vertex of a split-off triangle will have an incorrect vertex normal.\n\n Figure 1: A grassy slope mesh in Blender.\n\n Figure 2: The same mesh in Unity. Note how the lighting produces a visible seam between the two triangles of each grass quad. (Apologies for the low color contrast in the screenshot)\n\n- In Blender, create a quad mesh and rotate it so that it's standing instead of laying down\n- Use \"point to target\" to point the quad's normals straight up\n- Export the quad with the Collada exporter, with the triangulate option on\n- Import the mesh into some other program to check the exported vertex normals. You should see that one of the vertex normals is wrong.\n\n**Workarounds**\nTriangulating with Ctrl+T does not suffer from this bug.", "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", "Viewport is no color corrected correctly (ACES and others on background image from camera and ref images)\nOperating system: Windows 10 x64\nGraphics card: Geforce GTX 970 (primary / screen), 2x Geforce GTX 1070Ti (for Cycles)\n\nBroken: 3.4.1, 2022-12-19 17:00, 55485cb379f7, blender-v3.4-release\nWorked: None\n\nHi, \n\nSo my problem is that the viewport are not correctly color corrected when using OCIO ACES setup (ACES 1.2 for me, just stay on this one cause good for me and others studios). When I want a ref image or a background movie (from sequence images) to track or just to match some color on my lighting, my ref images are bad color corrected, so no clean reference for color picker, no possibility to try a fast pre comp to validate before advanced compositing in Davinci Resolve. The goal of ACES / OCIO is to have the same color pipeline and possibility to match all the footage just knowing the ACES profile used in the studio that send you data (raw exr sended and inform I used ACES cg and texture is in srgb / texture ACES mode and co).\n\nIt's really bad to have all working good in blender for ACES but not the viewport (displayed one, cycles render good aces color on bad colored viewport).\n\nI hope you will focus on this fast cause it's really boring, put in option to put the viewpot in raw linear workflow or fix the way to have the good color when I use my aces \"input sRGB\" on my png \"light\" srgb ref for tracking or when I use my full raw linear exr. I use ACES to be sure to send good color to others studios.\n\nHope it will be fixed in the next realease after the 3.4.1 ;)\nIn attachment my OCIO config + two pictures to show the problem.\n\nNothing to do, it's hard coded in Blender if I read well.\n\nThank you\n\n\n\n\n\n\n[config.ocio](config.ocio)", "bpy.ops.paint.image_paint with a texture requires initialization with manual paint stroke otherwise color not quite right\nWin 10 5820K GTX 970\n\n2.79b and latest daily build\n\nbpy.ops.paint.image_paint with slightly wrong colors when painting on object with texture on brush before a manual paint stroke applied\n\n1. Load attached file\n2. Run script\n3. With mouse over the cube - press space and type Simple Modal Operator to activate modal paint operator\n4. move mouse about to paint. \n5. left click to stop modal paint operator\n6. now paint on the cube normally by holding mouse button down\n7. you will see this is a slightly different color \n8. press space and type Simple Modal Operator to activate modal paint operator again\n9. move mouse around\n10. you should now see modal operator painting correctly\n\nThis seems to happen each time I change the texture on the brush to a new one (with obviously different colors on it)\n\nImage is attached showing this.\n\nPossibly something not being initialized properly?\n\nThanks you in advance for any work on this.\n\n[modal_paint.blend](modal_paint.blend)\n\n\n", "Cycles: sRGB texture compression happens after interpolation \nBroken: 2.81\n\nCycles does sRGB->linear texture conversion after texture interpolation instead of before. This leads to incorrect results.\n\nExample scene is attached. Two squares with a fine checkerboard texture, one with linear interpolation, the other with closest interpolation.\n\nExpected result: Both textures should render to an identical shade of gray. When switching the texture color space to \"linear\" instead of \"sRGB\", the result should not change as the texture contains only pure black and white pixels.\nActual result: The textures show different shades of gray. Switching the color space changes the result.\n[checkerboard.blend](checkerboard.blend)\n\n", "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "Average: Custom Normal's functions probably doesn't work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nMesh > Normals > Averame > Custom Normal functions (F9) probably doesn't work.\n\n1) Add any mesh. \n2) Switch mode to Edit Mode.\n3) Select all components.\n4) Call menu Mesh > Normals > Average > Custom Normals. At this point normals changed.\n5) Open bottom menu or press F9 and try change any sliders.\nChanges will not occur. I assumed that this was a mistake, because. these sliders are repeated in the modifier Weighted Normal, but there they work fine!\n", "percent bevel by weight doesn't work properly\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\npercent bevel by weight doesn't work properly \n\n\n\n", "Displacement distorts textures\nOperating system: Windows 10\nGraphics card: RTX 3060Ti \n\nBroken: 3.6.0\nWorked: Never\n\nAll textures are distorted where displacement texture is greater than 0.\n\nWhen you plugin displacement as 'bump only' the box projected textures glitch out and start to stretch.\nSee attached file.\n", "EEVEE renders black when no normal NODES connected to mix node --> normal input.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0 Release Candidate\n\n\nEEVEE renders black when no normal NODES connected to mix node --> normal input. Works fine with Cycles. \n\nOpen below file and click on each material output to see the issue. Switch to cycles and all fine.\n\n[empty normal bug.blend](empty_normal_bug.blend)\n\n\n\n\n", "Volume scatter shader affects data render passes.\nOperating system: Win 10\nGraphics card: GTX 980ti\n\nBroken: 2.80.74 2019-07-12 17:50 e3c586e262dd\nWorked: unknown (2.79 allegedly has the same issue)\n\nVolume scatter shader affects data render pass (AO, Depth, Normal).\n\n\nRender the scene below. The file has two view layers, one called FOG, and the other NO FOG. The former includes a volumetric object.\n\n[Problem.blend](Problem.blend)\n\n\n**Developer Note**\n\nI tweaked the file a bit (mainly added a texture to compare the changes in the AO pass and the normal and UV.\n[volume.blend](volume.blend)\n\nAnd a comparison between the AO and normal pass for each view layer:\n\n\n\n**Blob from original report**\n\nHello, I'm facing an annoying problem and it's blocking our tries to use Blender as a production tool here at Lightfarm. So, every time we try to use a volume scatter shader to create fog doesn't matter if I use the option inside the world tab or create a cube, invert its normals and apply a volume scatter shader to it. Blender applies noise or color coming from the volume scatter shader in Data render passes, AO, Depth, Mist, Vector, Normal and etc... what gives us a wrong output to be used in Post-Production. I shouldn't be happening. I tried different solutions in a way to get around this problem. Tried different values for alpha threshold, tried to apply a transparent shader in the BOX that has the volume scatter shader applied. Nothing seems to solve the problem. I'd love to hear from you a solution for this. \n\nAlso, using mist pass to comp fog in the post isn't an option here because it's not as realistic as we want or separate the fog in a different render layer because it'll increase our render times a lot.\n", "Move and share Eevee / Cycles render settings\nThe following settings should be unified for the 2.80 release:\n* - [x] Light intensity and color when not using nodes ([D4588](D4588))\n* - [x] Color management settings on image texture node and image datablock\n* - [x] Depth of field\n* - [x] Film transparency [D4874](D4874)\n\nFor later:\n* Material without nodes\n* Motion blur", "GPencil: Hardlight blend issue\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83.0\n\nThe semi-transparent textures of Grease Pencil material turn black when their layer is in HardLight blend mode.\n\n- open the provided blend file\n- see, wrong alpha blending\n- NB: change the blend mode and it works as expected\n\n[GP-hardlight-blend-issue.blend](GP-hardlight-blend-issue.blend)\n\n", "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)" ]

[ "16bit normal maps displayed wrong in eevee\nOperating system: Windows 10 64bit\nGraphics card: Geforce GTX 980 or Geforce GTX 970 (tested on both)\n\nBroken: 2.80, 69b2f5268114, blender2.8, 2019-02-10\n\nin eevee, 16bit normal Maps (png or tiff Format) are not displayed correctly and Output wrong normals. 8bit normal Maps and cycles is correct.\n\n\neevee, 16bit on the left, 8 bit on the right\n\n\n\ncycles, 16bit on the left, 8 bit on the right\n\n\n\nexample blend file + textures\n[textest.zip](textest.zip)" ]

[ "Weird artefacts from emission surface\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M (but this occurs also on CPU)\n\nBroken: 3.6.2\nWorked: don't know\n\n\nIn the attached .blend file I have set up an emission shader to emit light from one end of a long thin surface. The screenshot illustrates the problem: a bunch of weird artefacts appear.\n\nIf I change it to emit from the other end of the surface, by swapping the 'Map Range' node in the screenshot for the disconnected one, the problem goes away.\n\n\n\n\nLoad the attached .blend file and switch the view to rendered.\n\n", "Cycles: Bump node doesn't distort normals\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 10)\nWorked: Never\n\nHeight input have no effect on bump node output in cycles.\nThe main problem, that Generated texture cordinates give seams with bump. That is why I desided to try Normal input.\n\nEevee:\n\n\nCycles:\n\n\nHere the example file.\n[WhereNormals.blend](WhereNormals.blend)\n", "EEVEE baking\n", "EEVEE Cryptomatte Processing Performance\nCurrent implementation uses a single core. During implementation it was always kept in mind that we should do the processing in a threaded way. It should also be possible to render the next sample during the integration of the previous sample in the accumulation buffer.\n\nAnother solution would be to do the sorting on the GPU using compute shaders. [D10913: GPU: Compute Pipeline.](D10913)", "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", "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", "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", "EEVEE motion blur in cryptomatte\nI have tested this in 2.93.3 and even blender-3.0.0-beta+v30.bd734cc4419a to check if it got added there. \nThe issue is simple to explain: cryptomattes in eevee don't include motionblur. In Cycles they do include the motion blur. Is this a known thing, will it be addressed in the next updates?\nI suppose it could also be an undiscovered bug as the blender manual describes it as following \"[...] mattes will be anti-aliased and take into account effects like motion blur and transparency.\" cryptomatte.html - well in eevee it doesn't take motion blur into account", "Remove normalization from original coordinate attribute (CD_ORCO)\nFrom #95776:\n\n> The internal CD_ORCO attribute is normalized to 0..1 which is not really helpful, not even as default texture coordinates. It would be good to do some refactoring so these are stored unnormalized and then applying any additional texture space scaling for rendering only.", "EEVEE: User preference settings (anisotropy, texture size limit) affect rendering\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n[Viweport texture limit size affects eevee rendering.]\n\nWhen I change the \"texture limit size\" setting it also limits the size of the texture in the render.\nAs the setting is in the \"viewport\" tab I believe it should only affect the viewport, not the rendering.\n\n", "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.", "Post processing dithering can't be saved in 16bit format\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: never worked possibly\n\nDither applies to final image only if you save it in 8bit format.\n\nIn attached file:\n* Render scene (F12) and save PNG file twice: in 8bit and 16bit formats\n\n", "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", "The Viewport Display setting of Particles affect the Render result with Eevee \nOperating system: Linux-4.15.0-55-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe Viewport Display setting of Particles affect the Render result with Eevee \n\nWith Particles selected Change \"Display as\" to \"Path\" in Viewport Display setting and Render with Eevee . error : Pathes will be dislpayed in render result \n[partical_render.blend](partical_render.blend) press render\n\nFrom other reports what is also affected:\n- `Viewport Display` > `Strand Steps`\n- `Viewport Display` > `Amount`", "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" ]

[ "Normal map isn't working correctly (wrong Roughness and SSR, even light)\nOperating system: Windows 10 last update\nGraphics card: GTX 1070 ti\n\nBroken: 2.80, ba6cf3cdb649\n\nI don't know whats wrong with this shader but it is not working correctly for me, you can see how its working now (same HDR map in both program)\n1) off normal (correct SSR and light)\n\n2) normal strength is 1 (seems weird )\n\n3) Substance Designer \n \n\nDefault file with these textures\n[wrong_normal_map.blend](wrong_normal_map.blend)" ]

[ "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", "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", "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)", "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)", "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "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", "Crash handling collections in a timer\nOperating system: Mac OS Monterey version 12.0.1\nGraphics card: Radeon Pro 555X 4 GB\n\nBroken 3.0.1\nbroken blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg \n\nBuilding Nodes add-on causes Blender to crash consistently when editing nodes in Building Style Editor window. I've been in communication with the author off the add-on (user name Durman on GitHub), and he has provided the script and instructions to reproduce the crash below.\nCrash log [blender.crash.txt](blender.crash.txt)\nAsan report [F12872713](T95861_asan.txt)\n\n[#95861.blend](T95861.blend)\n\n1. Open the attached file\n4. Push execute button of the text editor\n5. Wait until the crush\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", "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.", "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", "Unable to execute Toggle Edit Mode - error changing modes\nOperating system: Linux-5.15.11-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.3.2\n\nBroken: version: 3.1.0 Alpha\n\n\nIt happens when I try to toggle to Edit Mode on second scene if first scene has edit mode a object\n\n\n\n1) Open file\n2) Select scene \"Scene.001\" and try to toggle to Edit Mode\n3) Get a error\n\nIt is issue or planned (user) error? Getting the error don't full inform an user. Why the error happens? A user may be confused :)\n\nP.S. For fix the error need in scene \"Scene.002\" to disable Edit Mode and than can be to switch to edit mode in \"Scene.001\"\n\n[edit-mode.blend](edit-mode.blend)\n", "Shadows stop working properly when changing render pass in viewport.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1404\n\nBroken: version: 3.5.1\n\nWhen doing a certain shading setup and changing render pass, the shadows break.\n\n- Create a new project, keeping the render engine to eevee\n- Make a new material and apply on default cube\n- Connect any image texture into the color input of principled bsdf\n- Connect any image texture into the normal input of principled bsdf while setting its color space to non-color\n- Switch viewport shading to rendered\n- Switch render pass to shadow and then back to combined\n- The lights will now not produce any light unless their shadow setting is turned off\n\nAny other nodes added before or in-between the image texture node do not seem to affect the result.\nThe shadows will stay like this until blender is closed and reopened again.\n\n", "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", "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)", "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>" ]

[ "Regression: Freeze when switching to material preview or render view\nOperating system: Linux-5.17.4-xanmod1-1-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.2.0 Alpha\nWorked: not sure\n\nNot bisected but appears to be caused by 9c82c00b32\n\n started blender and turned to eevee shading and it freezes. nothing can click anymore. \nfound out its because my saved startup file didnt have material on default cube what causes it. so i deleted startup.blend file in config folder and started and eevee shading works again.\ni think its bug because what if people dont want have material on default cube on startup file\n\n**Steps to Reproduce**\n- Open attached file\n- Switch to material preview or render view\n\n[startup.blend](startup.blend)" ]

[ "Disabled objects still get evaluated if there is a driver on their hide_viewport property.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.90 (sub 0)\nWorked: I think never\n\nCurrently, when an object is hide_viewport==True, that object as well as any dependencies it has that are also hidden, will have not hinder viewport performance. But that's not the case when there is a driver on the object's hide_viewport property, even if that driver evaluates to True.\n\nThe use case is as a rigger, I would give animators options to hide parts of a character to gain viewport performance.\n\n[remesh_performance_depdendency_test.blend](remesh_performance_depdendency_test.blend)\n- In the blend file, simply start playback and notice(unless your computer is a beast) you should get fairly low fps, even though the objects are disabled.\n- Remove the driver from the sphere's hide_viewport, and performance goes back to normal.", "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", "\"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.", "Cycles does not respect Object->Holdout option.\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 528.24\n\nBroken: version: 3.5.0\nWorked: Never (Goes as far back as 3.0 where the object->holdout option is added)\n\n\nCycles does not respect Object->Holdout option.\n\n\n- Open the provided file.\n- Press render.\n- The plane which is set as \"holdout\" doesn't mask the image.\n - Expected: the region of the plane should be zero alpha.\n", "Dyntopo: Performance hit when moving the viewport\nOperating system: Win10x64\nGraphics card: GTX 1080Ti\n\nBroken: 2.82 - 2.90 f96a689b3be2 (much worse in 2.9)\nWorked: Unknown\n\nWhen I turn dyntopo on with a high poly count model, the viewport becomes extremely slow, even if I'm not sculpting and just rotating around.\nAs soon as I switch dyntopo off or switch modes, it's butter smooth again. Where I'm looking also seems to have an effect on framerate.\nWhy should a feature related to actual sculpting affect performance when just looking around?\nDyntopo ON 2.90:\n![2020-04-26 02.13.26 Blender_ [C__Blender_Sculpt Owl_Owl.blend].png](2020-04-26_02.13.26_Blender___C__Blender_Sculpt_Owl_Owl.blend_.png)\nDyntopo ON 2.82:\n\nDyntopo OFF 2.90:\n\n\nOpen a high poly count model\nGo to sculpt mode\nNotice viewport framerate\nTurn on dyntopo, nothing else\nFramerate is now much lower\nTurn it off and it's back to smooth\n(No actual sculpting was done)", "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", "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", "Slow initialization in the rendered viewport after the default normal map added\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 512.15\n\nBroken: version: 3.1.0\n\n\n[slow initialization time in viewport rendering.mp4](slow_initialization_time_in_viewport_rendering.mp4)\nThe slow initialization in the rendered viewport occurs after the default normal map node was added in the Skin shader. (The Skin shader is very simple - it contains just a Principled BSDF and Material Output.) I have tried both CUDA and Optix, and the slow initialization exists in both cases after the default normal map node added. \n\n\n[Sample to test slow initialization in viewport rendering.blend](Sample_to_test_slow_initialization_in_viewport_rendering.blend)\n\nSteps to reproduce the bug:\n\n1, Download the sample file and open Blender; \n\n2, Select the mesh, and go to the Sculpting mode, and then under the \"Remesh\" tab change the Voxel Size from 0.4 m to 0.004 m, or even smaller value if your computer can handle. Click \"Remesh\".\n\n3, Then click the rendered preview. You will find that the higher the poly-count, the slower initialization speed. \n\n4, Go to the Shading mode, and remove the Normal Map, and click the rendered preview. Your initialization speed returns to normal, even if the poly-count is high. \n\n", "Cycles: modifying properties through the Python console does not trigger updates.\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Beta\n\n\nLoad a scene with a 16k hdri\nwith viewport rendering happening, try and rotate the hdri environment using a mapping node:\n\n\nnow change the world surface setting sampling method to manual, and the map resolution to 1024\n\nmessage will appear:\n\n\nnow rotate the hdri again. It'll be much more responsive.\n\nnow in the python console enter:\nbpy.data.scenes['Scene'].world.cycles.sample_map_resolution = 15360\n\nNotice the message 'updating lights' didn't appear in the viewport.\n\n rotate again, it's still responsive because cycles is still using the 1024 manually entered.\n\nNow restart the viewport render by clicking on solid viewport mode and back to rendered viewport mode\n\nRotate again. Still responsive. Even though the viewport has been restarted, cycles is still using the last manually entered value of 1024.\n\n-------\n\nNOTE: no updates seem to be triggered for the properties. The only update triggered seem to be for the console's current line which is modified after executing the entered line.\n", "Some GUI Pannel takes forever to load\nHello,\nOperating system: windows 10\nGraphics card: NVDIA RTX a2000 with latest driver\nIntel I7 with desactivated integrated gpu\n\nBroken: 3.5, 3.6\n\nBlender starting up is very slow\nmore importantly GUI is unresponding ( often around 25 sec ) when accessing to:\n>\"shading\" panel\n>Window explorer ( loading an image texture for example)\n>Material preview mode\n>Display render preview\n>Accessing preferences\n>Rendering window\n\nNo problem for modeling rendering etc. loading theses GUI parts seems to be the only lag itself.\n\nWhat i've tried:\n>Disable all addons\n>Factory user prefs\n>Deleted user pref app data folder\n>Updating driver to the latest version\n\ntried on 3.5. > Still the same\n\nThe lag is present even with the most basic file available\nIt has always been like so since i installed my pc.\n\nThanks\n\n", "VSE (Video Sequence Editor) scene strips have very slow playback in both Material preview and Rendered mode.\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 531.41\n\nBroken: version: 3.6.0 Alpha\n\nAdding the 3d scenes to the VSE and turning Material Preview or Rendered mode are making the playback very slow.\n\n1. With the default scene opened create a second scene.\n2. Switch to the Video sequencer.\n3. Add a first scene to the timeline.\n4. Switch \"Scene strip display\" to Material preview or Rendered.\n\nThank you.", "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.", "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", "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", "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 !" ]

[ "Many Geometry Node instances slow Cycles rendered viewport down (but only in camera view, perspective is fine)\nwindows 10\nrtx 2080 ti\n\nbroken in Blender 3.1 \nworks in ?\n\nIn scenes with many scattered objects, there is a huge difference in performance when in cycles rendered viewport, camera view vs perspective view. \nUsually, I think the best way to view such scene, with a lot of scattered objects, is through cycles, with the overlay and gizmos turned off (gpu) as it´s less lag compared to solid view . But, if I switch from perspective to camera view it gets as laggy as if with overlay on/solid shade. \n\nI´m not sure if this is a bug or a limitation but, Sins the perspective view and cam view is visually identical I report this as it would be a lot easier to be able to interactively work in camera view. \n\n\nOpen the attached file and set both perspective view and camera view to rendered se the difference in performance.\nnote: If you use a `Realize Instances` node just before outputting the geometry, the lag goes away\n\n[Bug_Slow_Camera_VS_Perspective.blend](Bug_Slow_Camera_VS_Perspective.blend)", "Enabling Camera View on heavily instanced scene causes massive slowness in changing view\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.2\nIt seems to be happening in 3.0.1 Stable and 3.2 Alpha from today's build too\n\nEnabling camera view in viewport causes changing view several times slower/laggy\n\nEDIT: Youtube clip showcasing issue - watch?v=hIR_hcWr2YY\nEDIT 2: Doesnt' seem to happen (or difference it too small to notice) in Solid and Material Preview view modes\n\n1. open attached .blend file\n2. move around in viewport\n3. enable Camera view (icon on right side of viewport) - notice that moving around is, much, much slower. \n\nI'm not sure why, but seems camera affects performance of instances? Despite practically the same viewport look (views, look, similar focal length etc.), the difference between non-Camera View viewport and Camera View enabled viewport is massive. I've also noticed that plugging Realize Instances node before geometry nodes output makes this difference much smaller, but difference in changing view is still there - roughly 20-30% instead of several times.\n\nAttached .blend file [instances_SlowCameraButFastViewport.blend](instances_SlowCameraButFastViewport.blend)\n\n", "Slow camera view navigation in Cycles rendered shading mode with many instances\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\n\nWhen looking through camera and navigating the viewport (with Lock Camera to View for example), the movement is much slower than a regular perspective view. This happens in rendered shading mode with Cycles, when many object instances are in the scene. Instances can be generated with Geometry Nodes or the old particle system. Also they don't even have to be visible on screen, you could be looking at a single cube somewhere to the side, and the camera navigation will still be slow.\n[camera navigation bug.blend](camera_navigation_bug.blend)\n\n\n - Use the provided file\n - Switch to rendered mode and disable overlays\n - Try looking around\n - Switch to camera view\n # Navigation should be much slower and unresponsive\n\n\n\n" ]

[ "Noise artefacts when lacunarity is near 1\nFor all noises that have fractal detail and lacunarity set close to 1 this outputs a zoom type effect.\n\n\n\nThis is caused by the noise origin occurring in the same place. \n\nIt is possible to mitigate this by offsetting the fractal layers but fixing this would be a breaking change.\n\n```Diff\n+#define FRACTAL_OFFSET 1259.0\n+\n /* The fractal_noise functions are all exactly the same except for the input type. */\n float fractal_noise(\n vec3 p, float octaves, float roughness, float lacunarity, bool normalize)\n@@ -78,7 +80,7 @@ float fractal_noise(\n octaves = clamp(octaves, 0.0, 15.0);\n int n = int(octaves);\n for (int i = 0; i <= n; i++) {\n- float t = snoise(fscale * p);\n+ float t = snoise(fscale * p + i * FRACTAL_OFFSET);\n sum += t * amp;\n maxamp += amp;\n@@ -87,7 +89,7 @@ float fractal_noise(\n }\n float rmd = octaves - floor(octaves);\n if (rmd != 0.0) {\n- float t = snoise(fscale * p);\n+ float t = snoise(fscale * p + (n + 1) * FRACTAL_OFFSET);\n float sum2 = sum + t * amp;\n return normalize ? mix(0.5 * sum / maxamp + 0.5, 0.5 * sum2 / (maxamp + amp) + 0.5, rmd) :\n\n```\n\n", "Snap to Grid in Perspective View performed only at ground level\nGenerally you are not sure which grid point the object is in the perspective view because you need to consider the current depth of the object on the screen.\nThis option would only limit movement at ground level under those conditions.", "Camera data node \"View Vector\" differs between Cycles and Eevee in the viewport when used as world output\nOperating system: Windows 10\nGraphics card: RX580\n\nBroken: 3.0.0\n\nThe camera data node's \"View Vector\" output does not work under Cycles in the viewport when used in World shaders.\nNote that it _does_ work as expected if there's an active camera (although it's not quite as bright as Eevee).\n\nEevee viewport rendering:\n\n\nCycles viewport rendering:\n\n\nCycles viewport (with active camera) rendering:\n\n\nConnect the camera data \"View Vector\" output directly to the \"Surface\" input of the \"World Output\" node.\nSwitch to rendered view.\nObserve that the view vector is incorrect when navigating the viewport in Cycles, but correct when in \"camera view\" (numpad 0) or in Eevee.", "Camera Field of View Modal Operator Error\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.5\n\nThe Modal Operator that changes the camera's Field of View displays the wrong value.\n\n1. Open Blender, select the Camera, and change Lens Unit to Field of View.\n2. Right click in 3D View and select Camera Lens Angle\n3. Move the mouse around, and notice that the value in the top left corner does not match the current field of view.\n", "USD import: investigate texture color space conversion issue\n\n@brurpo Reported the following issue:\n\n> When exporting USD from maya to blender none of the textures comes with the correct color space, they are all srgb.\n> Importing on maya again, on a clean scene, does not have this issue, all textures are loaded with the correct color space.\n> Is there a workaround for this, or is this planned?\n\n\nI'll be looking into this.\n\n\n", "modifier offset slider step value being driven by the mouse looses one order of magnitude worth of accuracy when units are metric vs none\nwin 10\n2080ti\n\nBroken: 2.80+\n\nSince blender 2.8 has switched to real world units the modifier slider step(when driven by the mouse) value has lost one order of magnitude worth of accuracy, 0.001 instead of 0.0001 \nIt is possible to switch the unit system back to none to get the higher accuracy. \nThey should be consistent and both work to the higher level of accuracy as this level is essential when working on real work scale small items e.g. a watch\n\n\n- with scene unit type set to \"metric\" add a bevel modifier the standard cube\n- press shift while clicking and dragging the bevel modifier offset slider and notice how the smallest amount possible to move is 0.001 m\n- switch scene unit type to \"none\"\n- press shift and click drag the modifier offset slider and notice the smallest amount possible to move is 0.0001 m\n", "Slow camera view navigation in Cycles rendered shading mode with many instances\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\n\nWhen looking through camera and navigating the viewport (with Lock Camera to View for example), the movement is much slower than a regular perspective view. This happens in rendered shading mode with Cycles, when many object instances are in the scene. Instances can be generated with Geometry Nodes or the old particle system. Also they don't even have to be visible on screen, you could be looking at a single cube somewhere to the side, and the camera navigation will still be slow.\n[camera navigation bug.blend](camera_navigation_bug.blend)\n\n\n - Use the provided file\n - Switch to rendered mode and disable overlays\n - Try looking around\n - Switch to camera view\n # Navigation should be much slower and unresponsive\n\n\n\n", "Camera Gizmo - Turning off Focus Distance has no effect\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.81 (sub 1)\nWorked: (optional)\n\n\nViewport Gizmos - Turning off Focus Distance has no effect\n\n[Based on the default startup or an attached .blend file (as simple as possible)\n\nSelect the camera. Turn on Limits in Viewport Display Panel of the camera. Focus Distance is dependant of this to be on. Now turn off Focus Distance. \n\nNothing changes. Shouldn't the yellow widget disappear? And why hide a widget that you explicitely have to turn on before?\n\n\n\n", "Grease pencil: unstable offset height (surface drawing)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\n\nWhen I use perspective camera, and try to drad on surface with GP, offset is unstable and depends on distance from camera.\n\nTest File:\n[#94735.blend](T94735.blend)\n[2022-01-08_10-23-37.mp4](2022-01-08_10-23-37.mp4)\n", "View zoom (scale mode in particular) doesn't work well when dragging horizontally, or crossing the middle of the screen\nBroken: 2.79, 2.80, 2.81 HEAD (8c9e6f123a2).\nWorked: ?\n\nNavigation Mode Scale Is Broken - it should never be calculated from the vector zero.\n\n- Set Blender Navigation to Scale\n- Try to press Alt + click and drag in viewport to make it zooming (or click and hold the \"zoom\" icon in the viewport).\n- Try to cross the mouse arrow in the vector zero (i.e., cross the mouse around the middle of the viewport).\n- As you can see the tool start to work weirdly inverting the zooming as soon you cross the scene vector zero.\n\nNote: The other zoom modes (e.g., dolly) also present a strange behaviour when zooming horizontally. But the zoom seems to reset when going over the origin regardless of the mouse direction.\n", "Non Uniform Scaling possible when Camera is parented\nOperating system: Win 10\nGraphics card: Geforce 2070\n\nBroken: 2.82-3.2\n\n\nIf you parent a Camera to an Object and scale the parent non uniformly, the Camera View gets scaled and distorted too.\n\n\nCreate an Empty, parent the Camera to an Empty, scale the Empty. The Camera View gets distorted.\n\n[blender_camera_scaling_bug.blend](blender_camera_scaling_bug.blend)", "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", "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", "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", "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 Aperture size does not properly translate to corresponding f-stop value\n(Model space set to unit length in centimeters and unit scale to 0.1)\n(Camera: 50mm, with focal point locked to the same object each time)\n\nFor the exact same scene at the exact same camera view with the exact same camera settings test two scenarios:\n\na) switch aperture type to \"radius\" and set to 2cm (this corresponds to an f-stop of 50mm/20mm=2.5)\n\n\nb) switch aperture type to \"f-stop\" and set it to 2.5 (as calculated above)\n\n\nObservation:\n(a) and (b) should render the same, but they do not.", "Blender GLSL viewport DoF doesn't respect world scale\nOS X 10.11.4 El Capitan and MacBook Pro with AMD Radeon R9 M370X\n\nBroken: 2.77 22a2853\n\nReal-time Depth of Field (DoF) in the viewport is incorrectly focused if <Scale> is not set to 1.0 under Properties->Scene->Units. If scale is set to 2.0, the camera's focus will be 1/2 the actual distance. This does not affect non-realtime rendering.\n\n\n\n\n- Create a cube and a camera, or use the default Blender scene\n- Create an Empty inside the cube to be used as the camera's focal object\n- In camera settings tab, set the focus object to be the Empty\n- In camera settings tab, set F-stop to 2.0\n- Enter camera view\n- In viewport properties (N-Key) under Shading, check <Depth Of Field>\n- **The cube should be in relative focus at this point**\n- To check, translate the empty along one of the axes (G-key + Y-key). It should go in and out of focus as the empty moves closer to and further from the cube.\n- Now, go to Properties->Scene tab->Units and check <Metric> to enable the Scale property\n- Set Scale to 2.0\n- **The cube should now appear out-of-focus**, even though the empty and cube are superpositioned\n- You will have to move the empty twice the distance of the cube from the camera in order to regain focus\n\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n[Scene Scale Viewport DoF Bug.blend](Scene_Scale_Viewport_DoF_Bug.blend)" ]

[ "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.", "Geometry Nodes Baking\nAs mentioned on the [blog]() the goal is to support the following features:\n* Editing procedurally generated geometry destructively in the viewport.\n* Prepare and manage simulations for the render farm which shouldn't need to run the simulation itself.\n* Explicitly cache parts of the node tree to avoid recomputing them after every change.\n* Re-time animated geometries, i.e. access geometry generated on one frame in another frame.\n\nAt a high level these goals are achieved by allowing the user to bake still or animated geometry at arbitrary positions in a geometry nodes tree using a new Bake node. The baked data can then be used without having to recompute the inputs of the Bake node. It can be edited destructively using Blender's existing edit modes. Furthermore, the baked data can be imported at specific frames.\n\nImplementing all of these features in one go would be too big of an undertaking, so below are smaller releasable milestones that can be worked on one after another.\n\n## Milestone 1: Bake Node\n\nAfter this milestone users will be able to bake still or animated geometries at arbitrary positions in the node tree. The main use cases are:\n* Prepare simulations (with optional post-processing) for a renderfarm.\n* Speedup working with very heavy node trees (e.g. static landscape generation) by explicitly caching the generated data.\n\nThere are a few requirements for this milestone:\n* New Bake node with a dynamic number of sockets for geometries and their attributes.\n* Baking works by pressing on a bake button in the node itself.\n * For baking the user has to choose between still or animated geometry and optionally a frame range.\n * A bake directory on disk has to be choosen.\n* Deleting the baked data should be possible from the node as well.\n* Potential settings and the baked data are stored per Bake node instance. A Bake node that is in a reused node group is counted as multiple Bake node instances. The actual data per Bake is stored in the geometry nodes modifier on the object.\n\nIt may be enough to keep UI changes local to the new Bake node.\n\n## Milestone 2: Manage Bakes\n\nIn production files, there are typically many simulations and other heavy effects that require baking. The goal of this milestone is to give the user tools to manage many bakes.\n\nThere are multiple parts to this which could potentially be split up into somewhat independent tasks, but I keep them together until further discussion happened:\n* Support naming Bake node instances.\n * While working with just Bake nodes in the node tree, this is less important, because the location of the Bake node in the tree \"identifies\" it to the use. When dealing with many Bake node instances at once, one can't rely on their location but needs to use names.\n * Just using node names does not work well for this, because a node only has one name but might be reused many times.\n* Support tagging Bake node instances.\n * As we've seen in the intro, not all baking happens for the same reasons. Therefore it is important that tools that work with multiple bakes can filter what bakes to work on.\n * Supporting custom tags can help the user organize baked data.\n* UI for dealing with all bakes in a scene or file.\n * There should be some kind of UI list that shows all the Bake node instances.\n * It should show which data is currently baked and which not.\n * Filtering can happen using tags and object selection.\n * Various new operators can work on multiple bakes at the same time: bake, delete bake, set bake directory.\n* Python API for dealing with baked data.\n * While the UI we provide for managing baked data should be good enough for most use cases, it seems unrealistic that we can provide all the tools that a larger production needs out of the box. Therefore, it is necessary to make it easy to manage bakes from addons as well.\n\n## Milestone 3: Import Bake\n\nThe Bake node does two things implicitly, it indicates where in the node group the baking happens and it also imports the baked data. Having both of these in the same node is desirable for most use cases, but sometimes it's benefitial to split both tasks. For example:\n* Baking an animated geometry and the loading it at different frames for re-timing.\n* Load multiple baked frames of the same Bake within the same frame.\n* Baking a geometry in one .blend file and then loading it as a cache in another.\n\nAll of these use-cases turn our baking format into a more general purpose interchange format like Alembic that is Blender specific. Baking into other formats will be possible eventually as well, but it not part of this project. Using a custom format allows us to optimize it for our needs and avoids the problem that Blenders data does not always map 1 to 1 to how data is stored in common formats. Also see [this](105251) task.\n\nThe import can be done with a new Import Bake node which takes a (file) path and a frame as input and outputs the geometry. There are some problems that need to be overcome:\n* The Import Bake node ideally has the same sockets as the corresponding Bake node, but this can't be guaranteed when they are in separate .blend files.\n* While not supported yet, it will be possible to pack baked data into the .blend file. Therefore, the path input is sometimes a path on disk and sometimes some internal identifier.\n* It should be possible to use the combination of a Bake node with one or more Import Bake nodes within a node group without having to hard code the file path for all of these nodes. Therefore, it seems reasonable that the Bake node also outputs where the baked data is stored. Also see [this](29266) older proposal.\n\n## Milestone 4: Editing Baked Data\n\nThe idea is that the user can just go into edit, sculpt or other modes on the baked data and edit it in place. For animated geometries, every frame can be destructively edited separately. The goal here is not to record all manual edits the user did. After baking again, the edits will generally be gone.\n\nWhile this might seem like a small feature, if done right, it can have huge impacts on the way people work with geometry in Blender in the long-term. That is because it could theoretically allow us to get rid of the idea of \"original geometry\" in Blender (e.g. the mesh referenced by `object->data`). To give a glimpse into what could become possible: Adding a cube object could just add an \"empty\" object with Cube node in geometry nodes. This allows the primitive mesh to remain procedural. Going into edit mode could implicitly (or explicitly) add a Bake node and bake the cube so that it can be edited destructively.\n\nAs for this milestone, the target use cases are more minor and mostly revolve around fixing up \"bad\" data in animated geometry. For example, in a particle simulation, a single particle got too close to the camera and blocks the entire view. It should be possible to just delete it manually. \n\n## Parallel Track 1: UI for Unused Nodes\n\nThere are various situations in which nodes in a node group are unused:\n* Nodes not connected to the output.\n* Nodes that would compute the unused input of a Switch node.\n* Nodes that were used to compute a simulation that is now cached.\n* Nodes that compute the inputs to the Bake node which is now baked.\n\nCurrently, there is no obvious way for the user to determine which nodes have been evaluated by the last evaluation. However, this information would be very useful because it allows seeing at a glance when data is cached/baked.\n\nLogging the set of nodes that has been evaluated is relatively [straight forward](107780). However, we still need the a good UI for these nodes. The obvious solution is to just gray out these nodes. While that can work, it's not ideal because the nodes can and should still be editable and graying out usually indicates that the user is not expected to edit them.\n\n## Parallel Track 2: Store Baked Data in .blend File\n\nWe already support packing external files into .blend files. That system just needs to be enhanced to also support baking entire folders full with baked data. Ideally, it is possible to load the baked data lazily when loading a .blend file, but that's probably quite a bit more challenging. It remains to be seen how much of a performance hit loading all frames at once has.\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", "Render Result not applying the compositor if the region is cropped\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\n\nWhen you render just a small region (to save time) and make the composite in full size (fullHD), it isn't taken into account in the final result. \nHaving the resulting file (in this case full size - fullHD) without the compositing taken into account, makes no sense.\n\nThis really limits the use of both *render region* and *Compositor*\n\nWorkaround is *File Output* node but that doesnt support video output.\n\n\nThanks and regards\n\n\n\n- Open attached file\n- render it and compare the compositor preview with the render result output\n\n[Test.blend](Test.blend)\n\n", "Cycles: tapering hair transparency fails in '3D Curves' mode [regression] (probably caused by embree)\nOperating system: Ubuntu 20 LTS and MacOS Mojave\nGraphics card: Quadro p2000\n\nBroken: 2.92 and latest 2.93.0 alpha 5f1f233dc97de34f6be0f51edd3cbf2d8247fbda\nWorked: 2.82a and 2.83.4\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nSetting a transparent BSDF shader to hair in 3D curves mode yields a visible error where parts of the hair are black.\nThis issue is visible in the viewport and at render time. It affects both CPU and GPU rendering.\n\nIn ribbons mode, transparency works almost as expected. I noticed that when hair strands overlap and they have transparency, they are not transparent but they take the background opaque color instead, so the hair strands below are \"covered\" with background color.\n\nembree\n\nbefore embree\n\n\n[#86500.blend](T86500.blend)\nOpen file and switch to rendered view\n\n---\n\nOriginal report:\n\nInitial setup in viewport: a cube with 20 hair strands:\n\n\nRender in version 2.83.4:\n\n\nRender in version 2.92+\n\n\n\nAttached is a .blend file example (so that you don't need to reproduce the steps below). [transparent_hair_curves_issue.blend](transparent_hair_curves_issue.blend)\nIf you run it on Blender 2.82a, rendering should show only a cube. Blender 2.92+ will show the issue.\n\nSteps:\n- Open a new default blender scene with a cube\n- Choose Cycles renderer\n- Under Render Properties > Hair, select 3D Curves\n- Add a hair particle system to it\n- Lower particle count to 10\n- Set segments to 5\n- Enable Hair Dynamics, play the timeline for a while until hair bends\n- Go to simulated frame 30 (just an example)\n- Scroll down in psys panel to Render, enable b-spline with steps 2\n- In Timing, set start to 0.361 (just for testing purpose)\n- In Hair Shape, set Diameter Root 0.5, Tip 1, Radius Scale 1.00\n- Render in viewport or to an image (same result)", "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).", "Regression: 3.0.0: The curve is not hidden in the Viewport if there is a Bevel value\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: 3.0.0 `d046a1f2fa `\nWorked: 3.0.0 `1275ce61b1`\n\nHiding the curve display in the viewport as an object does not work\n\nIf you add a curve to the scene and try to hide its display and the ability to select in View Object Types, then hiding works.\nIf you add a profile for a curve or Bevel, then hiding does not work. In this form, the curve is hidden only when it is done as a hide mesh.\nPerhaps this is the correct behavior.\n\n[2022-12-28 16-39-53.mp4](2022-12-28_16-39-53.mp4)\n", "Geometry Nodes/Curve to Mesh: BLI_ASSERT_UNIT_V3 failure for curve normals in `math_rotation.cc#rotate_direction_around_axis` when using Minimum Twist \nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 3.5.0 Alpha, branch: master, commit date: 2022-12-14, hash: `rBUnknown`\nWorked:?\n\nWhile debugging and testing changes in `curve_to_mesh_convert.cc`, I came across a `BLI_ASSERT_UNIT_V3` failure for curve normals in `math_rotation.cc#rotate_direction_around_axis`.\n\n```\nRead blend: /tmp/rotate_direction_around_axis_normalize_bug.blend\nBLI_assert failed: source/blender/blenlib/intern/math_rotation.cc:16, rotate_direction_around_axis(), at '!(fabsf(_test_unit - 1.0f) >= 0.0002f) || !(fabsf(_test_unit) >= 0.0002f)'\nAbort trap: 6\n```\n\n`rotate_direction_around_axis` is called from `CurvesGeometry::evaluated_normals()... curves::poly::calculate_normals_minimum()` when using `Minimum Twist` (no assert failure in `Z-up` mode). No apparent negative effect when tested with non debug release. It seems to be due to the fact that `curve_geometry.cc#rotate_direction_around_axis()` does not normalize its returned value. It happens on a fairly big curve with ~200k control points that I created to test curve_to_mesh performance. \n\nFull backtrace:\n[rotate_direction_around_axis_normal_assertion_failure.txt](rotate_direction_around_axis_normal_assertion_failure.txt)\n\n**How to reproduce:**\nStart Blender (compiled in debug mode) from command line to see standard output, open the test file and switch the Set Curve Normal to \"Minimum Twist\". `BLI_assert` message should appear on the standard output.\n\ntest file:\n[rotate_direction_around_axis_normalize_bug.blend](rotate_direction_around_axis_normalize_bug.blend)\n\n**Suggested change:**\n\nNormalize the result of `rotate_direction_around_axis`:\n\n```\nlang=diff\ndiff --git a/source/blender/blenlib/intern/math_rotation.cc b/source/blender/blenlib/intern/math_rotation.cc\nindex 454862c8d18..92eb7832eb8 100644\n--- a/source/blender/blenlib/intern/math_rotation.cc\n+++ b/source/blender/blenlib/intern/math_rotation.cc\n@@ -20,7 +20,7 @@ float3 rotate_direction_around_axis(const float3 &direction, const float3 &axis,\n const float3 diff = direction - axis_scaled;\n const float3 cross = math::cross(axis, diff);\n \n- return axis_scaled + diff * std::cos(angle) + cross * std::sin(angle);\n+ return math::normalize(axis_scaled + diff * std::cos(angle) + cross * std::sin(angle));\n }\n \n float3 rotate_around_axis(const float3 &vector,\n```\n", "Normals generated by Curve to Points node aren't always perpendicular to the curve\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\n\nFor curves with sharp corners, like poly splines or bezier splines with vector handles, the normals are not perpendicular to the straight curve segments, but bend around corners. This makes it impossible to properly align instances to the curve.\n\n\n\n\n\n - Create curve with sharp corners\n - Add Geometry nodes modifier and use Curve to Points node to generate points\n - Use either Normal or Rotation output to drive the rotation of instances, like in the example\n\n\n", "Curve extrude offset default value is 1 (instead of 0)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 5500M ATI Technologies Inc. 4.5.13587 Core Profile Context 19.40.30.02 26.20.14030.2002\n\nBroken: version: 2.93.0\nWorked: -\n\nCurve > Object Data Properties > Geometry > Offset\nIf you reset the \"Offset\" value with right click+*Reset to Default value* or by pressing backspace the value is set to 1\n\n - Open blender\n - Create a curve\n - Extrude it\n - Reset the offset to the default value\n - Offset is set to 1 instead of 0\n\n**Expected behaviour**\nThe default value for this should be 0. If a curve is created the value is 0 without any changes\n\n[curve reset offset.blend](curve_reset_offset.blend)\n", "Consider using more explicit names instead of the generic 'Size' value for Empties.\nWhen creating an Empty, the pop-up window specifies the `Radius` for the Empty, presumably because the shape chosen could be a sphere, arrows, or any number of different types.\n\nHowever, when viewed in the Object Data Properties, the radius is displayed as a more generic `Size` value.\n\n\n\nThis leads to confusion, especially when comparing an Empty to a Cube. In the example below, the visual scale of these two items is identical, yet looking at their `Size` tells a different story.\n\n\n\nFor context, this came up as a point of confusion for a use case where I'm using non-scaled empties as a 'holder' for position/rotation/scale while applying a set of custom properties to be exported as .glb and used in threejs.\n\nMy suggestion would be to continue the use of `Radius` as the label in the Object Data Properties, instead of `Size` since that's what is actually meant by the value.\n\n", "Edges generated by Bevel Modifier do not inherit correct crease values\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.02\n\nBroken: version: 2.81 (sub 14)\nWorked: (optional)\n\nThe Bevel Modifier ignores the crease values of connected edges, producing unexpected/undesired results.\n\nExample image of the bug in production asset (the rear of a flatbed car):\n\nPlease observe how the top is rounded toward the center of the car, despite the vertical corner crease and the horizontal beveling. This roundness goes against the artist's intention.\n\n\nOpen this file: [#70587-bevel-edges-bug.blend](T70587-bevel-edges-bug.blend)\n\nThat file was created by following these steps:\n\n1. Create a cube\n2. Set Edge Crease of vertical edges to 1.0\n3. Set Edge Bevel Weight of top horizontal edges to 1.0\n4. Add Bevel Modifier in Weight Mode\n5. Add Subdivision Modifier\n\nThis produces undesired result 1:\n\nPlease observe how the top of the cube becomes circular because the creasing on the vertical edges does not extend to the newly generated loop of faces.\n\nThis can be seen in image 2:\n\n\nOnly after manually adding the crease value to the new edges do we get the expected result, image 3:\n\n", "Compositor in start up file does not show specific passes\nBroken: version: 3.1.0 Alpha\nWorked: Prior to 7e712b2d6a\n\nWhen loading the startup file, some passes will be missing from the compositor. For example the denoiser.\n\nHere is a video showing off the issue: [F12781327](Missing_Passes_in_Compositor.mp4)\n\nWatch the video above or follow the steps below:\n\n1. Start up Blender and change the render engine to Cycles.\n2. Go to the `Viewlayer Properties` tab and enable Denoising Data.\n3. Change one of the areas to the `Compositor` and tick the `Use Nodes` box.\n4. Take note of the passes that are available on the `Render layer` node.\n5. Select from the top of Blender `File -> Defaults -> Save Startup File`\n6. Close Blender\n7. Open a new instance of Blender 3.1 and notice that the `Render Layer` node is missing some of the inputs that should be there.\n\nHow it looks before you re-open Blender:\n{[F13081662](image.png), size=full}\n\nHow it looks afterwards:\n{[F13081667](image.png), size=full}\n\n\nExample of startup.blend:\n[startup.blend](startup.blend)", "Cycles motion blur: The start and end of the motion blur range are not exposed like the rest of the range.\nOperating system: Fedora Linux\nGraphics card: AMD (rendered on AMD CPU)\n\nBroken: 3.5.1\n\nWhen rendering motion blur with Cycles (with the constant shutter curve preset) it seems like the shutter is not fully open at the start and end of the motion blur range.\n\nBased on the attached .blend file (as simple as possible).\n\nRender the first frame with Evee and Cycles and compare the motion blur.\n\n", "Split Draw curve tool in two distinct tools [properties of one mode dont make sense for other mode]\nOperating system: Win10 x64\nGraphics card: GTX 1080Ti\n\nBroken: 2.82 - 2.90\n\nDraw Curve F9 \"Error\" slider doesn't do anything if curve is set to Poly\nIn fact, none of the provided settings work\n\n\nMake a new curve\nEdit mode\nUse toolbar draw curve (Toolbar - 9)\nSwitch it's type to Poly in N - Tool - Active tool\nDraw any curve\nF9 to adjust the Error slider - no effect\nOther settings also have no effect\nSwitch mode to Bezier and the slider works" ]

[ "Regression: Trim curve make spline disapear.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon (TM) R9 390 Series ATI Technologies Inc. 4.5.14830 Core Profile Context 22.6.1 27.20.20912.1002\n\nBroken: version: 3.4.0 Alpha\nWorked: (13 Sep 22 before moving trim spline to another block)\n\nCaused by eaf416693d\n\n[Trim curve node make cyclic curve disappear when not trimmed]\n\n[Add circle node & trim spline node afterwords, this makes spline disappear. If you only trim to 0,999 instead of 1 (or from 0.0001 instead of 0.0) it comes back.\n[Trim spline bug.blend](Trim_spline_bug.blend)\n\n\n\n{[F13574735](image.png)}]\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", "Sculpting Has Unexpected behavior when Saving work\n**Broken**: 2.83.4, 2.90 beta 97dc370c50ed\n**Worked**: 2.82\n\n\nGlitches in the non-active mesh after sculpting the active mesh, saving, and updating the viewport.\n\n\n[Ogre.blend](Ogre.blend)\n\n* Sculpt\n* Save\n* Refresh viewport (e.g., continue sculpting)\n\nThe artifacts should be visible immediately.\n\n**Original message**\n\nWhen I am sculpting and I go to save my work, after a successful save I get weird artifacts in the mesh that I havent made edits on in sometime. And it seems to be the same mesh every time. This has happened over 5 times so i figure its just a visual bug.\n\nGet 2 seperate meshes ready to sculpt, then sculpt on one and save your work. This is all i did to see the bug arise.\n\n\n", "Missing overlays in the viewport when viewing through transparent shader\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6.1\n\nwhen viewing an LGT-shadow_caster.004 object, all overlays disappear from a certain side of it\n\n\nSee LGT-shadow_caster.004 in blender 3.6 splash screen\n\n", "Glitches on Video Sequence timeline\nOperating system: Linux 5.9.11\nGraphics card: Intel Haswell\n\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nShowing glitches on video sequence timeline when area of Video Sequencer resizing\n\nSteps shown on video\n\n[2020-12-02_15-19-26.mov](2020-12-02_15-19-26.mov)", "Orange tile boxes appear in the wrong place when using border render and viewing a different slot than the one being rendered in\n\nOperating system: Linux Mint 18.3 64-bit\nGraphics card: N/A; rendering on Intel i5-4460\n\n2.80 beta, 918941483f7e, blender2.7, 2019-02-27, 00:14\n\nWhen using border render (but not if rendering the full image), the orange tile boxes show up in the wrong place *when viewing another slot aside from the slot being rendered in*. They are a few hundred pixels too low.\n\n[F6720951](render-2019-02-26_21.28.51.mp4)\n\nOpen Blender.\nHit F12.\nAfter it renders, press CTRL+B, and select some portion of the render area.\nRender.\nPress J to switch to Slot 2 and render there too, so the canvas becomes visible.\nRender on either slot, and switch to the other.\nTake note of where the boxes are compared to where you set your render border at.\nCancel rendering/let it finish.\nSwitch back to Slot 1 to verify that the correct area was rendered and that the boxes were below it.\n\nI discovered this on 893fa5983193e from 3 days ago, but downloaded the latest version and did a quick test to make sure it still happens.\n\nI also noticed that after I rendered, set a render border, and started rendering again, it actually rendered the whole image - only the bordered area was visible, but it rendered everything else too. After that first time, it only rendered the bordered area, as it should.\n\n[F6721094](render-2019-02-26_22.08.33.mp4)\n\n(I set samples to 512 in order to slow rendering so I would have time to switch slots and show what happens before it finishes rendering.)\n", "Topbar gliches\nOperating system: Windows 10\nGraphics card: RTX 3060\n\nBroken: 3.3 Beta\n\nThis only happened on windows.\nWhen Status Bar is hidden and Resolution Scale is greater than 1, the Top Bar sometimes becomes unusable. (look at the end of video)\nMy guess it has something to do with notifications that are now displayed at Top Bar.\n[bug.mp4](bug.mp4)\n\nSame as in the video\n- On the `Windows` tab disable `Show Status Bar`\n- Go to {nav Edit > Preferences... > Interface} and change the `Resolution Scale` to 1.2\n- Save Preferences\n- Close the Temporary Window\n- Reopen the `Blender Preferences` window ({nav Edit > Preferences...})\n- Press `Save Preferences`\n\nInvoking save as temporary window also causes this issue\n\nTrying to resize Top Bar area or maximizing some other area fix the issue.", "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", "Display as behaviour in rendered view inconsistent between Eevee and Cycles\nOperating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19\n\nBroken: version: 2.82 (sub 4)\n\nWhen objects are set to display as wire or bounds, in the rendered view in eevee they are shown as wire or bounds respectively, but in Cycles they are fully rendered. \n\nFor any object, under object properties -> viewport display, set display as to \"bounds\" or \"wire\". Subsequently when the viewport is set to rendered view, the object is shown as bounds or wire in Eevee, but in Cycles the object is fully rendered. The Cycles way would be the preferred way in my opinion.", "Cycles 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!", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "EEVEE - Screen space reflections artifacts\nOperating system: Linux-5.3.0-7625-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 2)\nWorked: ?\n\nSSR shows some strips when I have bad data for normals.\n\nOpen the file:\n[ssr_sripts.blend](ssr_sripts.blend)\n\nIf you click anywhere multiple times, viewport gets darker and darker.\n\nBefore:\n\n\nAfter clicking the glossy node header a few times:\n\n", "EXCEPTION_ACCESS_VIOLATION error when trying to change object viewport color with the viewport compositing enabled in depsgraph_update_post\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.5.0\nWorked: 3.4\n\nThis error occurs only if the viewport compositor is enabled - rendered mode of the viewport and Compositor = Always.\nWhen trying to change the viewport color of the object by script on depsgraph update event, this error occurs.\n\nThe short script example:\n```\nimport bpy\n\ndef on_depsgraph_update_post(scene, depsgraph):\n if depsgraph.id_type_updated('SCENE'):\n for obj in depsgraph.updates:\n if isinstance(obj.id, bpy.types.Object):\n print('change object color')\n bpy.data.objects[obj.id.name].color = (1, 0, 0, 0)\n\nbpy.app.handlers.depsgraph_update_post.append(\n on_depsgraph_update_post\n)\n```\nAfter executing this script in the Text editor, switching to the \"Rendered\" mode of the 3D Viewport and enabling viewport compositing - when adding or copying the object - Blender throws an error.\n\nThis occurs only if the viewport compositing is enabled, if it is not used - code works as expected.\n\nError occurs on 3.5 and 3.6 alpha.\n\n1. I attached .blend file with the example\n2. Open .blend file\n3. Switch the viewport to the \"Rendered\" mode (z - Rendered)\n4. Execute script in the Text editor\n5. Try to copy cube (shift + d)\n6. Error throws\n\n", "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)", "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", "Avoid graphical glitches during threaded preview generation\nWhen previews are generated using an OpenGL engine, there can be a number of glitches until the preview is done. That's because some data is accessed/modified that is not thread safe. E.g. `object_preview_render()` modifies `U.pixelsize`. I think other glitches are caused by overriding the active theme in `ED_view3d_draw_offscreen()` - although when I avoided this some time ago for similar work on threaded offscreen drawing for VR, this didn't solve the color flickering.\nThe active theme should probably use thread local storage.\n\nBesides that, the preview generation should be thread safe with OpenGL:\n* It uses the draw-manager's own context, which is mutex protected.\n* The non-thread-safe immediate mode API is not used inside the draw-manager.\n* The draw-manager already has workarounds for GPU driver issues with threaded drawing.\n\nA note: We could also speed up Eevee preview generation significantly by using viewport render quality, not final render quality. The `_imbuf` offscreen rendering functions don't expose the `is_image_render` option for that, which they probably should." ]

[ "Issue with toggling fullscreen in camera view in cycles\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.81 (sub 15)\nWorked: version 2.79\n\nThe location of the object in camera view shifts when toggling fullscreen\n\nBased on the default startup\n1. Switch the render engine to cycles\n2. Numberpad 0 enter camera view and scroll to zoom in\n3. Switch to rendered view\n4. Open Window menu and toggle window full screen\n5. Ctrl Alt Space bar to full screen the area\nWatch the attached video for details.\n[Fullscreen Bug 3.mp4](Fullscreen_Bug_3.mp4)\n\n" ]

[ "GPencil: Tint modifier in Fill mode, don't get restricted by vertex group influence\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.4.1\n\nTint modifer in Fill mode, don't get restricted by vertex group as influence. in other hand, it works well on stroke mode,i really need this to be fixed really soon as possible please, see video\n\n", "Blender 2.90/ 2.91 Sculpt Vertex Paint - Stencil not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Beta, branch: master, commit date: blender-2.90.0-0e280b96ca82-windows64\nWorked: I think this last work in 2.83.2 or 2.83.1\n\nSculpt Vertex Paint - Stencil not working\n\n\n[BlenderBug.blend](BlenderBug.blend)\n\nAdded colored image to texture\nChange texture mapping to stencil\nImage is coming out as black and white on the screen and image is not being transferred on the object.\n\nI have tried changing Blender Mode and Color Space but it didn't work.\n\nAlso I am not sure if this suppose to happen but the image for stencil disappears when I tick Color Ramp under Color in Texture Panel.\n\n", "Bug when opening a file in sculpt mode, making N strokes, and undoing N times\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.90.1\nI know it says branch: master (modified), but the changes are just some print statements in build_files/utils/make_utils.py; nothing involving the actual Blender source code.\n\nAfter opening a blend file in sculpt mode, making one stroke and pressing undo causes an error. The same happens after N strokes and N undos(back to the original file state).\n\nThe following is a video showing what happens: [[ nRUn6EFqNlA ]], and I've also attached [sketch0.blend](sketch0.blend)\n\nsince I'm not able to reproduce it on a simple file. Note in the video that in addition to the obvious visual glitch, the \"dyntopo\" check mark in the top right gets cleared.\n\n1. Open the given file (it is saved in sculpt mode, with dyntopo and symmetry turned on).\n2. Make any stroke anywhere, and then press Ctrl-Z to undo.\n3. The same will happen if you make N strokes and undo N times.\n\n", "Grease Pencil drawing next to objects using 3D cursor and View mode previews \nOperating system: \nGraphics card:\n [system-info.txt](system-info.txt)\nBroken: Blender 2.92.0 Alpha - November 12, 10:10:02- bc090387ace9 - macOS 64 bit\nand blender-2.91.0-b99faa0f567f-macOS\nWorked: (blender-2.90.1-macOS)\n\nDrawing with the Grease pencil near objects sketches out and glitches through the object geometry and randomly offsets from the curser point when using a 3D cursor as the stroke placement and View as the drawing plane. The simple step by step video attached below best explains it. Note: this is not the case when starting the file in 2D Animation mode only when adding a grease pencil to a general 3D scene. Also, This problem did not exist with version 2.90.1\n\nSee the short video and blender files of the easiest set up to show the bug.\n\n[Grease Pencil Bug.mp4](Grease_Pencil_Bug.mp4)\n\n[Grease pencil Bug-latest build.blend](Grease_pencil_Bug-latest_build.blend)\n\n[Grease pencil Bug.blend](Grease_pencil_Bug.blend)\n", "Sculpt mode: hide masked do not work when modifier enabled, but hidden part works with modifier.\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\n\n\nAs title said. Hiding works with modifier but not work simultaneously as «hide masked»\nFor example, edit mode work well with mirror and hiding, hiding by faceset works well too...\n\n**Steps to Reproduce**\n- Open .blend file\n- Paint with mask brush\n- {nav Sculpt > Hide Masked} \n\nTest File:\n[#92372.blend](T92372.blend)\n[2021-10-20_18-49-00.mp4](2021-10-20_18-49-00.mp4)\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.", "Crosshair cursor is too small when sculpting on 4k resolution.\nOperating system: Linux-5.4.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\n\nOn 4k monitor, while sculpting, the cursor is barely visible.\nIf the mesh is grey/white, you cant see the cursor.\nSame on Vertex Paint and Weight Paint modes.\n\nwatch?v=fpADGvD47hE\n\n- On Edit Mode however the cursor is big and quite visible.\n", "Fix operators that affect hidden geometry\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar .\n\nThere are a number of operators in sculpt mode that affect hidden geometry. As a general rule this should be avoided.\n\n- [ ] `bpy.ops.sculpt.face_set_edit` to Grow/Shrink, Fair or Delete face sets needs to have the \"Modifiy Hidden\" property disabled by default and disabled in all menu and keymap entries.\n\nList of further operators:\n- [ ] `bpy.ops.sculpt.face_sets_init` \n- [ ] `bpy.ops.sculpt.face_sets_create(mode='SELECTION')`\n- [ ] `bpy.ops.mesh.paint_mask_extract()`\n- [ ] `bpy.ops.mesh.paint_mask_slice()`\n\n", "Sculpting: Vector Displacement option not enabled on appended brushes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.0\n\n\nWhen sculpting with imported brushes in 3.5 when applying an anchored brush (settings the same as in 3.3.5 LTS), the result looks lifted up from the surface.\n\n**Caused by** disabled \"Vector Displacement\" option when brushes from 3.3 were appended into 3.5, likely a versioning issue.\n\nThe option is added with #104481.\n\n\n\n\nSteps used in both releases:\n- Add Cube\n- Add Multisres modifier\n- Subdivide times 6\n- Apply modifier\n- Ctrl-A, origing to Geometry\n- Append brushes\n- Go to sculptmode\n- Choose a brush\n- Apply brush on object\n\nUsing 3.3.5 The brush is nicely put on the object, in 3.5 (with the same settings) you get a pimple. Lowering strength doesn't do the trick in 3.5.\n\n", "Cursor jumping to edge of screen when lifting pen from tablet area (wintab)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Beta\nWorked: 2.93\n\nTablet model: Huion h950p\nTablet api: Wintab\n\nWhen lifting the pen away from the tablet area, the cursor occasionally jumps to the edge of the screen, causing unexpected camera jumps or preventing hotkeys from being used in the 3d view.\n\nThe problem only happens with the Wintab api.\n\n\n - Set the tablet api to Wintab\n\n - Start creasing some edges and repeatedly lift and return the pen to the tablet area\n\n[cursorjump.mp4](cursorjump.mp4)\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", "The button \"Draw Curve\" for Stroke mode Curve probably doesn't work.\nOperating system: Windows 10\nGraphics card: AMD Ryzen 7, 2700, 8-core\n\nBlender Version: 3.0.1\n\nThe button \"Draw Curve\" from properties editor doesn't work.\n\nMy steps:\n1) Add any mesh object.\n2) Change Layout to Texture Paint (Default)\n3) Press + button below \"Mode: Material\". Add \"Base Color\". Press Ok.\n4) Scroll Down parameters to Stroke section. Expand Stroke section.\n4) Change Stroke Method to Curve.\n5) Press Ctrl+RMB button on mesh some times.\n6) Press \"Draw Curve\" button in properties editor - nothing happens!\nBut if I press Enter on my keyboard or Ctrl+LMB on mesh its drawing stroke.", "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", "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", "GPencil: Missing functionality in Vertex Paint mode Selection tool (left-click-select)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.0 Beta\n\nWhen Points select is enabled in Vertex Paint mode, the Selection tool doesn’t behave like in Edit mode:\n- it cannot select a single vertex,\n- a left click away from points doesn’t deselect them.\n\nAdditionally there is no color picker when this tool is selected, so if you select some points to use the Set Color Attribute operator on them, you can’t see the current color or choose a different color, unless you switch to a different tool.\n\nMake sure you use Left Click Select in Preferences > Keymap\nAs shown in video, open any stroke in Vertex Paint mode, enable Points select and select the Selection tool.\n- You can box select points but can’t left click on a point to select it and you can’t click away to deselect points.\n- There is no color picker.\n<video src=\"attachment\" title=\"Selection Bug-1.mp4\" controls></video>\n\n" ]

[ "Brushes don't draw under the property region, with region overlap\nBroken: 2.80 to 3.1 (and currently 3.2.0 alpha 4fa3eadce99a) (technically 2.79 as well, but back then region ovelap was drawn a bit diferently).\nWorked: Never\n\nTools brushes don't draw over the property panel, even though Region Overlap is on.\n\n* Ctrl + N → Sculpting\n* N (to open the Properties region).\n* Move the mouse to the right, beyond the alignment line of the properties editor panels.\n\n\n\nThe brush drawing doesn't follow the mouse cursor. The tool itself works though, and the brush is even drawn if you click in that part.", "Unusable screen space while opening the \"N-Panel\" in Sculpt Mode \nOperating system: Windows\nGraphics card: Gtx 1060 3Gb Gygabyte\n\nBroken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce1f, type: release\n\nThere is an unavailable part of the screen while using the \"N\"(shortcut) panel in sculpt mode\n\nUsing Blender **without any \"N-Panel\" addon**\nOpen the default startup > click on the cube > (shift + tab > Sculpt Mode) > press N > set the cursor just below the \"N-Panel\"\n[Example video, Same as attached file {F13485157}](watch?v=sdouMGus6ds)\n\nThanks a lot for your time and attention, wish you a fantastic day.", "Mouse stucks during sculpting when the panel is expanded \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon (TM) R5 M335 ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61\n\nBroken: version: 2.90.0\n\nDuring sculpting if the right side panel is expanded (contains Item, tool and view), the mouse gets stuck if moved from left to right just below the panel. The mouse will gets stuck from the as soon as it passes the boundary of the panel.\n\nGo to sculpt mode and expand the panel. Now move mouse from left to right just below the panel. The mouse will get stuck. \nIf you resize the panel, the mouse will stuck when the boundary is reached.\n\n[mouse_stuck.mp4](mouse_stuck.mp4)\n", "Brush cursor (sculpt, vertexpaint, weightpaint) stuck/doesn't draw under transparent part of N-panel\nBroken: 2.80 to 3.1 (and currently 3.2.0 alpha 4fa3eadce99a) (technically 2.79 as well, but back then region ovelap was drawn a bit diferently).\nWorked: Never\n\nTools brushes don't draw over the transparent property panel, even though Region Overlap is on.\n\n* Ctrl + N → Sculpting\n* N (to open the Properties region).\n* Move the mouse to the right, beyond the alignment line of the properties editor panels.\n\n\n\nThe brush drawing doesn't follow the mouse cursor. The tool itself works though, and the brush is even drawn if you click in that part.\n\n---\n\nVideo from the original report: [F8795403](2020-08-20_05-04-02.mp4)" ]

[ "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>", "Drivers don't refresh simulations.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77\n\nBroken: version: 2.90.0\nAs far as i can remember this bug exists at least from Blender 2.81\n\nAdding Drivers to any of the cloth simulation values will result in them not refreshing the bake when changing that value. When any of these values are changed by the Drivers, user needs to manually go back into the cloth simulation settings and either switch a random setting or Re-Bake the simulation for it to update to the current settings.\n\nAdd custom property to any object -> Copy that value as driver -> Paste it into any of the cloth simulation value settings -> Values will update but cloth simulation won't refresh, forcing you to go back into the cloth settings and refresh them manually. \n\n", "UV Stitch and Minimize Stretch do not support the trackpad\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: never\n\n\nWe can use the mouse wheel while executing \"UV Stitch\" and \"Minimize Stretch\" operators to adjust the Limit and Blend values. However, this feature is not available for trackpad users.\n\nA possible solution can be seen here:\nD8812\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", "Multi-object mode support (parent task)\nThis is a parent task to manage to todo's for multi object editing.\n\nThere are many small todo's.\n\n### Reference Patches:\n\nFor anyone interested in helping out, here are some example commits which can be used as a reference.\n\n- Edit Mesh Face Poke - 3a9669bfff *Committed without indentation, so you can see lines changed more easily.*\n- Edit Mesh Flip Normals - 4704f2687a\n- Pose Mode: Flip Quaternions - 7560aabf71\n\n\nOther commits may be useful too.\n\n### Object Loops\n\nThere is some duplicate code for looping over objects.\n\nWe'll keep the option of having a way of simplifying the looping open.\n\n----\n\nNote: to collect operator ID's.\n\n- this script helps copy them from menus: [P656](P656.txt)\n- this is a more efficient version that watches the x11 clipboard so you can hover over items and press Ctrl-C: [P657](P657.txt)", "Symmetry on sculpt mode won't work with auto masking topology enabled\nOperating system: Windows-11\nGraphics card:Quadro RTX 3000/PCIe/SSE2\n\nBroken: Blender 3.5.0\nWorked: N/A\n\nSymmetry on sculpt mode won't work with auto masking topology enabled.\n\n\n- Have a mesh that has two disconnected parts across a symmetry axis.\n- Enter sculpt mode, turn on \"Advanced -> Topology\" (topology auto masking).\n- Turn on X symmetry for sculpting brushes.\n- Sculpt on one part of the mesh, the opposite side doesn't change.\n", "Driven values do not change with units\nOperating system: Windows-10-10.0.20206-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\nWorked: No working versions (at least >= 2.79)\n\nWhen creating a driver from an unlabeled value, pasting it into a field that accepts units of measurement will always use meters rather than the Scene unit.\nThis means that for a scene using inches, a driver with a value of 1 will translate to approx. 39.\nWhile this prevents things from changing when units change, this is not ideal as exactly re-converting in an expression is impossible.\n(It is highly unlikely someone working specifically in inches will want to input their values in meters.)\n\n- Create a new project, and change the units. (in this case, to Inches)\n- Copy a new driver from an unlabeled value. (ex. array count)\n- Paste the driver into a field with a unit label. (ex. constant offset value)\n\n[#80649.blend](T80649.blend)", "snap to face broken with mirror modifier\nOperating system: Linux-4.18.0-25-generic-x86_64-with-debian-buster-sid 64 Bits\n(same behavior on Windows 8.1)\n\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.81 (sub 11)\nAlso broken in 2.80 stable\n\n* open demonstration blend file with no config dir\n* note that snap-to-face (target:closest, affect:move) is already enabled\n* select small cuboidal in lower left\n* G, then X, to move along X, and attempt to snap to broad side of nearby horizontal cuboidal\n* see that the object flashes erratically, alternately assuming its original position, and alternately assuming an incorrectly snapped position\n* if instead the cuboidal we are trying to move is moved a bit first, without snapping, and then we again try to snap to the face, it doesn't flicker any more, but it still snaps incorrectly (and actually still does flicker on the overlapping face but doesn't jump around in position)\n* if the mirror modifier on the cuboidal we are trying to move is disabled, it snaps correctly\n\nStarting position: \n\nIncorrect snap result: \n\nCorrectly snapped result: \n\nDemo blend file: [snapbug.blend](snapbug.blend)", "Reversing frames on video sequencer don't play them backwards\nOperating system: Windows 10\nGraphics card: Nividia GEFORCE 940MX\n\nBroken: ( 2.82a, 2020-3-12, as found on the splash screen)\n\n\nReversing frames do not play the frames backward as expected to when the strip is split.\n```\n\n```\n\nvideo sequencer -> Add an image strip -> cut the stip into 2 or three parts -> select the middle stip ->check the reverse frame checkbox.[Reverse.blend](Reverse.blend)\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)", "Partial UV selection working incorrectly with Metal backend\nOperating system: macOS-13.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.0 Beta\n\nUsing hide unselected in the UV editor seems to randomly 'explode' the UVs around the map.\n\nOpen [file](https://projects.blender.orgattachment), go to edit mode.\n\nUV is very messy, but when everything is selected, it's OK. Works fine with OpenGL backend\n", "Self-referencing driver works in viewport, but not in render.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional) 2.79b\n\nRotation property of object is updated in viewport, but not in render.\nIf run same script in 2.79 - all works fine both in viewport and render.\n\n```\ndef rotator():\n var1=bpy.data.objects[\"Suzanne\"].rotation_euler.z\n var3=bpy.data.scenes[\"Scene\"].render.fps\n\n new_value=var1+math.radians(var3)\n\n return new_value\n```\n\n\n[Script_bug_2.8.2.blend](Script_bug_2.8.2.blend)\n\n- run the file Script_bug_2.8.2 ('Run script', 'Update Dependecies')\n- play in the viewport - the animation works correctly\n- render (Ctrl + F12) - the animation does not work;\n\nViewport:\n[bug_video_render0001-0050.mkv](bug_video_render0001-0050.mkv)\n\nRender:\n[bug_video_render_20001-0050.mkv](bug_video_render_20001-0050.mkv)\n\n2.79 file:\n[Script_work_2.79.blend](Script_work_2.79.blend)\n\n", "Breaking change? Curve point tilt default orientation rotated by 90°\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\nWorked: 2.80\n\nThe default orientation (0°) of curve points has changed by 90°. If the curve is used for another object's curve modifier, the result between Blender 2.80 is different to newer versions (reproduced with 2.81...3.6). This is a change that I did not find listed in the release notes, so this is either a bug or by design. In any case, it's a breaking change.\n\n2.80 vs 3.6:\n\n\n\n1. Open the attached project in Blender 2.80 and in 3.6\n2. If you compare the two, you see that the normal orientation is different, consequently the result of the curve modifier affecting the mesh is different.\n\nAfter migrating a bigger project this causes several issues that would need to be fixed. Or Blender needs to be fixed.\nThis is an old issue, so I hope it's not a duplicate. Didn't find it.\nThank you.\n\n", "Unsubdivide and rebuild subdivisions from multires.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.1\n\nModel with multires applied doesnt works with unsubdivide option or rebuild subdivisions.\nI´ve applied the modifier, cleaned the data blocks but persist...\nThere is something strange in the mesh because it works with the default cube...\n\n- Open attached .blend file\n- In the Multires modifier, click in Subdivide\n- Apply modifier\n- Add multiresolution modifier again\n- Click in Unsubdivide\n\n> No valid subdivisions found to rebuild a lower level\n\n[UnsubdivideMultires.blend](attachment)\n\n", "Compositor: Viewport issues when Passepartout is off\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera `Passepartout` is off.\nNote that the Compositor is set to Camera.\n\n\n* Open this file: [zoomed_out.blend](attachment)\n* Notice that the passepartout is disabled in this camera, but the viewport compositor is set to Camera.\n\nCurrent buggy result:\n\n\nThe mask only matches when the camera has `Passepartout` on:\n\n\n\nRelated: #111344\n\n" ]

[ "Smart UV Project invert the resulting UVs\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\nWorked: 2.90.1\n\nCaused by 850234c1b1\n\nWhen using Smart UV Project, the resulting UVs are inverted in the X axis, compared to resulting UVs from Unwrap.\n\n1. Create a plane.\n2. Use Smart UV Project.\n3. If a material with a texture is added to the plane, the image will be inverted.\n\nThis doesn't happen using Unwrap.\n\nThanks!\n\n" ]

[ "Improve UX for interaction of modifier stack and node editor\nWhen a non-nodes modifier is selected as active modifier there is no indication or way to change that in the geometry nodes editor and it's very confusing for the user, especially when the properties editor is not displaying the modifiers panel.\n\nThis is related to #84927\nA potential solution has been proposed there as well (move towards interface similar to shader editor and material slots).", "Text Editor scrolling lag, macOS Metal backend\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: OpenGL\n\nThere is a lag when scrolling in Text Editor. (macOS, Metal backend)\n\n- In text editor, open a big text (like `gizmo_custom_geometry.py` from Templates)\n- Try using MMB-drag or try scrolling on the trackpad\n\nMMB-drag: you will see some page lag from the cursor, while with OpenGL the page moves with the cursor.\n\nTrackpad: if you scroll, stop and hold; the text will continue scrolling after you stop your fingers. When using the OpenGL backend it stopped immediately.\n\n", "Invert Masking behaviour for Sculpt/Paint Mode\nThis is a design related to the implementation of Paint Mode.\nIt outlines the possibility to invert the behavior & visualization of masks.\n**Current** = Masked vertices cannot be edited\n**Proposed** = Masks & Selections are the same -> They can be edited.\n\n# Current Issues\n\nThere are a few different issues that exist the with current way of how masks work.\n\n### An Inverted Workflow\n\nA typical workflow issue when using masks is that users mask a section of their mesh and then invert the mask.\nIn a lot of cases the areas you mask are the ones you DO want to edit.\nMasking is very much designed with this workflow in mind. But this leads to using `Invert` on the mask potentially hundreds of times per day.\n\n### Syncing Selections across Modes\n\nFor the implementation of Paint Mode it will be very beneficial to start syncing selections between various modes. \nSo if a selection is made in Edit Mode it will also appear as masked in Sculpt/Paint Mode (This would likely be a direct conversion every time you switch modes)\nThis will be less confusing and disconnected if both the selection in Edit Mode and the mask in Sculpt/Paint Mode are areas you CAN affect.\n\n### Masks vs Selections\n\nA current plan for the implementation of Paint Mode and the new Curves object type is to use \"Selections\". \nThe use case for sculpt mode masks and selections is essentially the same: \n**You define a temporary area that should be affected by your operations.**\n\nThe issue is that \"Masks\" also refer to the concept of for example creating an attribute (like a vertex group or color attribute)\n or a grayscale image texture and using it as a factor for shader/geometry nodes. The use case here is quite different:\n**You save an area for repeated use in materials and procedural networks.**\nFor example layering textures.\n\nReplacing the current concept of sculpt mode masks with selections would avoid confusion and make the use case of selections and masks very clear.\n\n# Proposal\n\n### Selection instead of Masking\n\nWe need to test the following behavior:\n- Rename \"Mask\" to \"Selection\" or \"Selection Mask\"\n- Unselected areas are darkened with an overlay\n- Selected areas are affected by brushes & other operations\n\nThere are use cases that are important to keep in mind with this change:\n- When entering sculpt mode, everything should already be selected.\n- Previous workflows (Mask brush) to create a deselected area and should still be accessible.\n\nOther areas of Blender will still refer to \"Masks\" like a Texture Mask in the brush settings, mask nodes, grease pencil layer masks and motion tracking masks.\n\n### Offer a preference to use the old behavior\n\nThere should be an option in the preferences to invert the selection behavior globally in sculpt/paint mode and get the old behavior back.\nTo what extend the inverted behavior would be done needs to be tested.", "just activating osl, without using it, makes any render 3 to 4 times slower\nWin7 x64\n\nBroken: 2.76b\n\nTake any prodution render with CPU, just activate osl in the render tab, it will render \" to 4 time slower, without using it in the scene. Compared to GPU render wich is already 5 times faster than a cpu render, it is = 15 to 20 times slower. OSL is unusable with this bug. Note that other renderer with OSL don't have this speed hit.\n\nWith CPU and 16x16 tiles, render this scene: pabellon_barcelona_v1.scene_.zip\nthen just activate osl, render again and compare times. although there isn't any use of OSL in the scene, the render times crawls down.\n(you can also lower the samples to 10 to make it faster for both render)", "UV Editor lacks Annotation 'Placement' option\nBroken: 2.80rc1\nWorked: 2.79b\n\nIn Blender 2.79, you had the 'View' and 'Cursor' Stroke Placement option in the left panel, under 'Grease Pencil'.\nIn 2.8 this is meant to be in the Top Bar or 'Active Tool and Workspace Settings', as it is for the 3d Viewport's Annotate tool, but this is missing for the UV Editor, meaning all annotation defaults to 'View'.\n\n - Open the blender and choose the `UV Editing` workspace\n - Compare the 3d View Annotate Tool with that of the UV Editor\n - Notice the lack of Placement options", "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", "Pixel Smearing in Compositor when using image node (image node lacks interpolation setting [in comparison to texture nodes])\nOperating system: Windows 10\nGraphics card: NVIDIA Quadro RTX 4000\n\nBroken: 2.79b , v2.83.8\nWorked: none known\n\nWhen an image is brought into the compositor and mixed with the scene, the result can be \"half pixel smeared\" depending on the even/odd pixel relationship between the image and the scene. It appears that some interpolation is happening on the image node's result in order to reconcile it with the center of the scene size, but this is undesirable as it breaks images that are intended to be pixel-perfect. \n\nAttached is a very simple, lightweight example .blend file (2.8) that contains 4 small example images (these images have dimensions 16x16 pixels, 15x16, 16x15, and 15x15).\nThese images exist as image nodes in the compositor.\nRender the scene, and then move the viewer node to the various outputs indicated to see how the resulting images have been smeared.[PixelError.blend](PixelError.blend)\nWhen these images are mixed with the scene, the resulting pixels from the small images will be smeared if there is a mismatch between the even-ness and odd-ness of the number of pixels in the image, and the number of pixels in the scene.", "Dead Keys failing (accented letters, double strokes)\nOperating system: Windows 10 X64 Enterprise\nGraphics card: Nvidia RTX 2070 MaxQ\n\nBroken: 2.73, 2.91.0\nWorked: Never\n\nIn a text editor window, using Unicode national characters (Greek in my case), there are accented vowels that register with two keys from the keyboard (eg: ά, έ, ό … etc).\nIf I type the 2 key sequence fast, the accent is missed, slower works. Is this a delay that can be set in Blender, or an interpreter lag that cannot be adjusted?\nActually I think it happens everywhere (not only text editor), but it’s especially nagging problem in a text window, where I may type whole paragraphs and almost each word has an accent.\n\n- In the text editor, press and hold the dead key\n- without releasing the dead key, press the key to be transformed. (this will fail)\n\nIf you release the dead key before pressing the key to be changed, it will work normally.", "Lag on moving mesh elements in edit mode with skin modifier\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: 3.4.0\nWorked: nothing\n\nIn edit mode if object has a skin modifier and visibility of modifier is set for edit mode, a performance drop is seen on moving mesh elements in edit mode\n\n- Open attached file\n- Switch to edit mode\n- Select all vertices and move them\n[untitled.blend](untitled.blend)", "Node Tools: popover menus for options\nWhen creating a new Node Tool the defaults are immediatelly set. But users can still change them from the menus\n\n* **Object Types**: Mesh, ...\n* **Modes**: Object, Edit, Sculpt\n\n\n\nNote: This is only for the Tool context. But once assets are also supported in the Modifiers Add Menu we will need the `Object Types` popover in the Modifier context as well.\n\n", "Remesh Resolution strange behaviour (Shift-R)\nOperating system: MacOS 10.14.6\nGraphics card: AMD Radeon R9\n\nBroken: Daily Build\nWorked: Don't know\n\n**Description**\nSetting the remesh resolution with Shift-R during sculpt when object is unproportional in size makes the grid fade (too quickly) and when zoomed in the numeric display of scale is upside down\n\nIn this small video clip, first part is correct behaviour.. second with disproportional object\n<video src=\"remesh_behaviour.mov\" controls></video>\n\n**Steps**\n- Use default cube\n- In edit mode scale the object 10x in Z only\n- Enter Sculpt mode\n- zoom in\n- Shift-R\n- observe grid fading and display upside down..\n\n[remesh_behaviour.mov](remesh_behaviour.mov)\n\n\n", "UI: Possible Change of Interface Font\nWith Blender 4.0 I am hoping that we can consider upgrading our interface font to something...\n* More modern\n* Easy to read\n* Supports variable design axes\n* Is actively maintained.\n\nOf these the first is quite subjective. But our current font, Deja Vu Sans Book came out in 2006, based on Bitstream Vera which was released in 2003. It has a look of its time and this look can cause our program to look similar dated.\n\nBeing \"easy to read\" can also be subjective. But I'm looking for good proportions, a good use of whitespace, etc. But also ideally avoid confusions like lowercase L and 1, \"clear / dear\", \"turn / tum\", etc\n\nSupport variable design axes is important to me because it allows the one font to support different weights, widths, tracking, slant, etc. Most will also tailor their feature sizes to output size. The majority of our fallback font stack consists of variable fonts, so this would complete that.\n\nMost fonts are designed and become static. I want a font that is actively maintained. Bugs fixed, glyphs added, and features improved by an active designer and community. The current version of our current font was [released in 2016]() and has had no changes for more [six years](dejavu-fonts). \n\nWith the above in mind I can only find two fonts that meet my requirements: Inter and Roboto Flex. I would love to hear of any other suggestions.\n\nFor testing the suitability of fonts I would prefer to do so with the following PR applied: [BLF: Subpixel Positioning, Anti-aliasing, Hinting #105441](105441). This PR enables typographically-correct sizing, placement, and rendering.\n\nOf these two fonts \"Inter\" is my favorite and has been the best-regarded interface font for a while now. However there is one way where it falls short for us.\n\nInter is kerned meticulously by its creator. Unfortunately the large amount of kerning corrections does not allow it to support the old style of kerning table that we use. It does not use the \"KERN\" table, but only the new style \"GPOS\" table. The former is supported by FreeType alone, while the latter requires a shaper like Harfbuzz (which also does complex languages, ligatures, etc). So in Blender, for now, Inter might show occasional kerning issues not shown in other applications or by Roboto. Whether anyone really cares though is up for debate - we have been using Deja Vu without kerning for years now.\n\n### Inter Variable V4.0 (Currently beta9h)\n\n\n\n\n\n\n### Roboto Flex 3.200\n\n\n\n\n\n", "Cycles renders SSS is noticeably slower in 3.4 than in 3.3 with multiple GPUs\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: 2x NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98 (SLI)\n\nBroken: version: 3.4.0\nWorked: 3.3\n\nCycles render images with SSS noticeably slower in 3.4 than in 3.3\n\nI noticed that some of my scenes render in 3.4 noticeably slower than in 3.3.\nAfter some analysis, I figured out that only images with SSS shaders are affected.\n\nI created a simplified test scene, this scene takes on my computer in Blender 3.3 **4:58** min and in Blender 3.4 it's **6:10** min.\n\nIf SSS is disabled, the test file renders equal fast in 3.3 and 3.4.\n\nProbably this change is unintended and might be a bug.\n\n[speed test.blend](speed_test.blend)\n\n\nTest render 3.4 (OptiX) 6:13 min:\n\n\nTest render 3.3 (OptiX) 5:12min:\n \n", "GPU Subdivision: Slow operations with Shape Keys\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.3, 3.2\n\nWith the GPU subdivision turned on, many operations with shape keys (locking, changing the active shape key) are quite slow, but the reason for the delay is the GPU subdivision itself, because when it is turned off, the speed of operation is several times higher\n\nselect the body itself, and perform various operations with the shape keys (for example, changing the active one). Compare the speed with the GPU subdivision turned off and on\n[kira_lite.blend](kira_lite.blend)\n[2022-10-09 22-50-29.mp4](2022-10-09_22-50-29.mp4)", "Viewport material is darker than the rendered version\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 10.18.14.5067\n\nBroken: version: 2.82 (sub 3)\nConfirmed in 2.81 release\n\n\nThe material consists \na transparent shade mixed with a translucent shade, mixed with an emission shade with\nfrenel node multiplied with a noise texture as the factor\n\nThe sample sizes are the same\n\nJust render\n\n\n[necro_core_reduced.blend](necro_core_reduced.blend)" ]

[ "Zooming in some interfaces becomes sluggish after opening the translation\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nWhen the translation function is turned on, some interface scaling becomes very sluggish, no matter which language is selected.\n\n\n1.Open Blender 2.80.\n2.Turn on the translation function.\n3.Scale some interfaces like timeline and shader editor with nodes\n[2019-08-15 20-31-39.mp4](2019-08-15_20-31-39.mp4)\n\n", "Mouse roller zoom lag in Node Editor with \"International Fonts\" turned on\nWindows 10 and GTX 970 (newest drivers)\n\nBroken: 2.76\n\nOn **some** computers (IRC #blender verified) it seems that turning on the**International Fonts** option in User Preferences -> System causes the middle mouse roller zooming in Node Editor to slow down considerably. \n`Ctrl MMB` or even `Shift B` zooming still works fast even with **IF** on. Altough in high zoom scenarios it slows down too when compared to **IF** off.\n\n`Ctrl Alt U`\nSystem -> check \"International Fonts\"\n\nOpen Node Editor\nUse mouse roller for zooming" ]

[ "'Solve Camera Motion' operator sometimes prevents Auto Save from running\nBroken: 3.5.1, 3.6\nWorked: maybe 3.4\n\nInvestigated in #107421 by @3di.\nIt's still unclear when this happens, but it could be replicated with the attached file.\nThe function `void wm_autosave_timer(Main *bmain, wmWindowManager *wm, wmTimer * /*wt*/)` in `wm_files.cc` skips AutoSave if any modal operators are running.\nIn this case, this can happen with the `\"CLIP_OT_solve_camera\"` operator even after the operation is theoretically completed.\n\n- Unzip attached .blend file\n- Go to \"Motion Tracking\" workspace\n- In the solve tab, press `Solve Camera Motion`\n\nAuto Save stops saving or saves very late.\n\nno%20autosave.zip?dl=0\n\n", "Text object dupli renders incorrectly due to missing depsgraph relations\nOperating system: Linux-5.10.96-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.0.1\nnote - the (modified) in there is because I commented out some annoying warning messages. The bug occurs in 3.01 un-modified. In fact, it occurs in 2.93, too!\nWorked: No idea. My guess is that it has not ever worked.\n\nBlender crashes when attempting to render Object Font text in Cycles if the font object is in an excluded view-layer (or is otherwise not visible in the render. It looks like simply clicking the camera to hide it in the render will also trigger the crash).\nFor now, it is easy to work around the issue by simply placing the font object somewhere in the scene where it won't be visible to the camera. \n\nEdit: it no longer crashes, but still renders with the wrong material and missing modifiers.\n\n- Open .blend file\n- Change render engine to Cycles\n- Switch to render preview\n[text_bug.blend](text_bug.blend)\n\n```lines=10\n# Blender 2.93.7, Commit date: 2021-12-07 14:43, Hash fb762eedbe85\nFile written by newer Blender binary (300.42), expect loss of data! # Error\nbpy.context.scene.exclude = False # Property\nbpy.data.objects[\"Cube-A\"].hide_render = True # Property\nbpy.ops.object.camera_add(enter_editmode=False, align='VIEW', location=(11.5822, 6.07443, 2.81362), rotation=(1.25533, 0.0140188, 0.598586), scale=(1, 1, 1)) # Operator\n\n# backtrace\nblender2.93(BLI_system_backtrace+0x33) [0xb0265b3]\nblender2.93() [0xf84231]\n/usr/lib/libc.so.6(+0x3cda0) [0x7fd276e87da0]\nblender2.93(_ZN3ccl6Shader8tag_usedEPNS_5SceneE+0) [0x31413c0]\nblender2.93(_ZN3ccl11BlenderSync17find_used_shadersERN2BL6ObjectE+0x211) [0x276a821]\nblender2.93(_ZN3ccl11BlenderSync13sync_geometryERN2BL9DepsgraphERNS1_6ObjectES5_bbPNS_8TaskPoolE+0xf7) [0x276aac7]\nblender2.93(_ZN3ccl11BlenderSync11sync_objectERN2BL9DepsgraphERNS1_9ViewLayerERNS1_23DepsgraphObjectInstanceEfbbRNS_20BlenderObjectCullingEPbPNS_8TaskPoolE+0x83e) [0x274367e]\nblender2.93(_ZN3ccl11BlenderSync12sync_objectsERN2BL9DepsgraphERNS1_11SpaceView3DEf+0x4c2) [0x27456c2]\nblender2.93(_ZN3ccl11BlenderSync9sync_dataERN2BL14RenderSettingsERNS1_9DepsgraphERNS1_11SpaceView3DERNS1_6ObjectEiiPPv+0x1a0) [0x2734520]\nblender2.93(_ZN3ccl14BlenderSession6renderERN2BL9DepsgraphE+0xc0e) [0x272984e]\nblender2.93() [0x132c995]\nblender2.93() [0x271eb69]\nblender2.93() [0x9096df4]\nblender2.93(_PyObject_MakeTpCall+0x90) [0x9058b10]\nblender2.93(_PyEval_EvalFrameDefault+0x8f40) [0xf80500]\nblender2.93() [0xf7665b]\nblender2.93(_PyEval_EvalFrameDefault+0x661d) [0xf7dbdd]\nblender2.93() [0xf7665b]\nblender2.93(PyVectorcall_Call+0x5f) [0x905856f]\nblender2.93() [0x190fb5d]\nblender2.93() [0x1869ab0]\nblender2.93() [0x8a5dbe0]\nblender2.93(RE_engine_render+0x214) [0x8a5e804]\nblender2.93() [0x8a62447]\nblender2.93() [0x8a65708]\nblender2.93(RE_RenderFrame+0xe3) [0x8a65e13]\nblender2.93() [0x2708994]\nblender2.93() [0x13472f2]\n/usr/lib/libpthread.so.0(+0x9259) [0x7fd277411259]\n/usr/lib/libc.so.6(clone+0x43) [0x7fd276f495e3]\n\n# Python backtrace\n File \"/all-users/blender-git/build_linux_2.93/bin/2.93/scripts/addons/cycles/engine.py\", line 177 in render\n File \"/all-users/blender-git/build_linux_2.93/bin/2.93/scripts/addons/cycles/__init__.py\", line 85 in render\n```\n\n", "Lots of animation-related operators do not check if the data is editable or not\nMany animation-related operators do not do any check whether the data-block they operate on is linked, liboverride or fully local data. This seems to affect in particular operations from the 3DView (like key insertions), and in the NLA (like adding new tracks, duplicating strips, etc.).\n\nE.g. one can insert keyframes on a linked object (ie create animdata for that linked object, a new local action, and assign that local action to the linked object!).\n\nRelated to issue reported in #98686 (Cant rename local NLA tracks within a local library override data-block.).", "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", "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", "Subdivided surface preserves mesh UVs and vertex colors when not needed\nThis code causes UVs and vertex colors to always be preserved through the modifier stack.\n\n```\n /* this wasn't in 2.63 and is disabled for 2.64 because it gives problems with\n * weight paint mode when there are modifiers applied, needs further investigation,\n * see replies to r50969, Campbell */\n#if 0\n CustomData_set_only_copy(&dm->loopData, mask->lmask);\n CustomData_set_only_copy(&dm->polyData, mask->pmask);\n#endif\n```\n\nFor simple solid shading these are not needed, and `ED_view3d_datamask` should take care of requesting them when needed, taking up memory and CPU time.\n\nHowever, there is currently an issue where switching shading modes does not reevaluate the dependency graph to add these data layers, so just re-enabling this code is not enough to fix this. See also #63595 (Generated texture coordinates missing when switching from solid to rendered mode).", "Image sequences used on brushes do not update while texture painting (despite auto refresh option)\nBroken: 2.8x and later\nWorked: 2.79 and probably older\n\n\npainting with image sequencer (sprite) no longer works when holding click, but it updates when clicking again and again while painting\n\n\nSteps to reproduce the error (you must be in 2.8 or later)\n1) go to Texture tab\n2) create a new texture and open\n3) select the images that contain the same name with order numbers\n4) enable Cyclic and Auto Refresh\n5) make sure you set it as Texture Mask and not Texture\n6) set it to View Plane so the texture image follows the brush\n7) play the timeline and begin to draw on the mesh\n\nNotice how the image texture does not change when dragging on the mesh, but if you try to click again and again, it changes.\n\nthis is how it should look when it works:\n\n\nThis must be brought back, it has soo much potential and possibilities!\nif this is something that is already considered and being worked on for the new upcoming blender version, then I'd be very happy\n\n[Desktop.zip](Desktop.zip)", "Particles cache ignores animated lifetime\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\nWorked: not sure if it worked after 2.80, maybe it worked in 2.79, but I'm not sure.\n\nIf you animate the lifetime and bake the particles everything in the same blender session everything works correctly, no matter if you bake them to disk or to memory.\nWhen you save the file, and open the file again the particle cache is broken and it's loading all the animation with the lifetime present in the first frame, no matter if it's a disk cache or a memory cache.\n\n\nBlende file: [test.blend](test.blend)\n\nSteps to reproduce:\n\nYou can watch the video I did or follow this steps:\n\nVideo:[particle_lifetime_an_bug.mp4](particle_lifetime_an_bug.mp4)\n\n1.- Open the attached blend file with Blender 2.90 release\n2.- Clean the cache if there is one, change some parameter like particle count (don't touch particle lifetime, it's animated)\n3.- Bake the animation, and you will see the correct result\n4.- create a new file\n5.- reload our test file\n6.- you will see how the cache is not behaving correctly and it's ignoring the animated lifetime\n\nIt's impossible to trustworthy bake particles without this working, because not even the disk cache is working\n\n\n", "Cycles does not respect Object->Holdout option.\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 528.24\n\nBroken: version: 3.5.0\nWorked: Never (Goes as far back as 3.0 where the object->holdout option is added)\n\n\nCycles does not respect Object->Holdout option.\n\n\n- Open the provided file.\n- Press render.\n- The plane which is set as \"holdout\" doesn't mask the image.\n - Expected: the region of the plane should be zero alpha.\n", "Statistic doesn't update if object deleted due to object data deletion with RMB\nBroken: version: 3.0.0\nBroken: version: 2.80 (sub 75)\nWorked: unsure (didn't find scene statistics in 2.79...)\n\nScene statistic (both in footer and 3D viewport) does not update correctly if object data is deleted with RMB\n\n1. Open default scene.\n2. Make sure you enable scene statistic either in 3D viewport or footer.\n3. In outliner unroll object to show it's object data, i.e. default cude.\n4. Click on object data, i.e. cube mesh, with RMB and delete it.\nObject will be deleted since it doesn't have mesh/camera/light object data. Notice that scene statistic is not updated (number of objects, vertices, selected status etc.). To update it you can select any object or click on outliner (doesn't matter on object or not).\n\nThat works correctly if object is not deleted, i.e. adding subdivision modifier (statistic will update) and then deleting it with RMB in outliner (statistic updated again).", "Missing progress indicator for 'Render Audio'\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 570 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.83.4\n\nWhen we use the 'Render Audio' option from Render menu, after the rendering starts, there is no indicator about the rendering progress, how much time is left.\n\nIn any scene with audio in the Sequence editor, try using Render>Render audio command. There is no progress indicator. It is very vital specially for long length tracks.\n", "Compositor: Viewport issues when zoomed in\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera is not fully in view.\n\n\n* Open this file: [zoomed_in.blend](attachment)\n* Notice that in the viewport the view is zoomed in inside the camera view.\n\nCurrent buggy result:\n\n\nThe mask only matches when the entire camera is in view:\n\n\n", "3D Texturing: When changing the texture resolution, the pixel data isn't recreated\n* Start painting\n* Change image resolution\n* Continue painting.\n\nWe have a safe guard for this, but it doesn't seem to work anymore.\n", "HDRI animation bug in eevee\nThe HDRI illumination shouldn't change on the cube, because every thing including the HDRI is rotating at the same speed. \nHowever, this went wrong in EEVEE... It seems that in Cycles everything went on so well.\n\nThis is a simplified bug presenting file of a complex scene which I found this bug, in which I have to rotate an object, a HDRI and camera together, and I'm struggling to get rid of this bug...\n\n[BugReport.blend](BugReport.blend)\n\n[0001-0096.mkv](0001-0096.mkv)\n\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.93.1\n\n\n\n", "Handler save_pre doesn't get called for session recovery save\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 389.12\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nThe Python handler `save_pre` does not get executed when Blender saves the session recovery file on exit. When add-on's are actively using this handler, they are very likely generating or finalizing data that will be saved along with the file. Skipping over this event while such add-ons are active is likely to cause data loss or strange bugs that will be difficult to track down.\n\nWrite a simple script that prints something to the console when `save_pre` is called, then exit Blender with it active. You can launch Blender from a console window to keep the window open after it exits.\n\n[#71506.blend](T71506.blend)" ]

[ "Persitent Data option does not update hair particles on animated objects\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.93.0 Beta\n\nWhen \"Persistent Data\" option is enabled, Cycles doesn't update moving hair particles on animated objects. Hair particles stay at the initial object position\n[0001-0025.avi](0001-0025.avi) \n\n1. Add a hair particle system to an object.\n2. Animate translation values of the object.\n3. Render a frame sequence via ctrl + F12.\n\n[persistent_data_does_not_update_hair_particles_001.blend](persistent_data_does_not_update_hair_particles_001.blend)\n\n\n" ]

[ "Cycles adaptive subdivision tasks\nAdaptive subdivision and displacement needs some work still to be considered stable and fully supported. This task is to keep track of what needs to be done.\n\nSubdivision:\n* #49159: Normal maps do not work, no tangents are computed.\n* #49585, also #86684: Adaptive subdivision setting linking issue (Make adaptive subdivision a proper modifier setting so it is copied correctly)\n* #49431: Missing smooth (face-varying) UV subdivision.\n* #73395: Pointiness not working with subdivision\n* #73403: Missing vertex colors\n* Motion blur not working ([test file ](open?id=12qOQg-5YSj4rTwwwFU3VFQJBE7-pPRNp), report #83639)\n* Support for instances, two strategies both worth trying:\n**Object space dicing option so users can manually set it for all instances** Bin instances according to distance from camera, so we have about log(N)\n* Grid primitive to reduce memory usage\n* Optimizations, reduce memory allocations, .. (#73564 (Adaptive subdivision modifier takes to much memory ))\n* In Blender 2.8, Blender subdivides the mesh itself which leads to too much memory usage.\n* #78055: panorama dicing works poorly compared to matching perspective camera\n* #92893 (\"Persistent Data\" stops \"Adaptive Subdivision Surface\" from working properly.)\n* #97364 (Adaptive subdivision breaks attributes passed from geometry nodes to shader editor)\n\nDisplacement:\n* Fast BVH refit updates when tweaking displacement shader\n* Better results for bump from vector displacement.\n* Vector displacement tangents compatible with other software.", "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", "No preview icon in the material list\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 536.40\n\nBroken: version: 3.6.1\nWorked: (unknown)\n\nI noticed that for this material in the list it is not previewed, but in the \"Preview\" panel the preview is correct.\nThis is a simple setup of mixing 2 shaders using the \"Alpha\" attribute as a factor.\nThis situation makes it difficult to work when only using the drop-down list of materials in various situations..\n\nThx.\n\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)", "Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)\nOperating system: Linux-5.15.0-52-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.4.0 Alpha\nBroken: 2.92.0\nWorked: 2.91.2\n\nBisecting gives 0f95f51361 as the culprit commit\n\nif the armature viewport mode is set to \"in front\" it doesn't properly update when the overlays are turned off and on\n[Peek 2022-11-01 05-35.mp4](Peek_2022-11-01_05-35.mp4)\n\n1-add an armature\n2-set the \"viewport display\" to in front\n3-turn off and on overlays\n4-if you can confirm the bug the armature should appear after changing anything in the 3d view to update as in the video, move rotate or zoom \n\n", "Viewport display broken for fire- solid and rendered mode (Cycles & Eevee)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\n[Fire seems to get 'stuck' in the viewport (as in it does not disappear), it does however behave correctly when F12 rendered.\nThis happens in 2.83Alpha and 2.82Beta (both downloaded as of today, approx 16:00 Sydney time 15 Jan 2020)]\n\n[Bake the attached and observe.\nhere's what it looks like-\n[ViewportFire_2-82+2-83.mp4](ViewportFire_2-82_2-83.mp4)\n\nIt works Ok when F12 rendered as seen here-\n[Fire26Nov20190001-0050.mp4](Fire26Nov20190001-0050.mp4)\nI couldn't be bothered to render out the clip in Cycles but stills show the error is only in the viewport-\n\n\nHere's the .blend-\n[Fire2.83A.blend](Fire2.83A.blend)\n\nThis works properly in the 26November2019 build, here's what that looks like-\n{[F8279386](ViewportFireMantaflow_26-11-19Build.mp4)}]\n\n", "Spreadsheet does not count changes by GPU Subdivision\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 (never worked as far as I can see)\n\nSpreadsheet does not count changes by GPU Subdivision.\n\nSee very similar issue with viewport stats: #98339\n\n\n- Add Subdivision Surface modifier. Make sure that GPU Subdivision is enabled\n- See spreadsheet does not count changes by the modifier\n\n[SpreadsheetGPUSubdiv.mp4](SpreadsheetGPUSubdiv.mp4)\n", "Grease Pencil keyframes not updating after GPencilFrames.copy()\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha\n\nCopied keyframes do not update with Grease Pencil Layer\n\n- Create a new document with the 2D Animation template\n- Draw a shape \n- (Note by @iss) It may be necessary to make new keyframe at later frame, see video\n- Run the below script in the Text Editor\n# Run the \"Grease Pencil Test Script\" command from the Draw Menu\n\nThe Grease Pencil data isn't updating in the Viewport unless the playhead is going backwards, a keyframe is deleted, or if the keyframes are added to a new `GPencil` object. I believe the issue is because the keyframes generated with `GPencilFrames.copy` are missing the layer update for some reason. If I use `GPencilFrames.new()` and copy every attribute manually, this issue does not happen. In the below code, I am updating all of the data I know to be possible.\n\n```\nimport bpy\n\ndef main(context):\n active_layer = context.active_gpencil_layer\n frames = active_layer.frames\n start_frame = frames[0]\n frame_numbers = [frame.frame_number for frame in frames]\n\n for frame in range(start_frame.frame_number, context.scene.frame_end+1):\n if frame in frame_numbers:\n continue\n new_frame = frames.copy(start_frame)\n for i,start_stroke in enumerate(start_frame.strokes):\n new_stroke = new_frame.strokes[i]\n for p,start_pt in enumerate(start_stroke.points):\n new_pt = new_stroke.points[p]\n new_pt.co[0] = start_pt.co[0]+(frame*0.5)\n new_frame.frame_number = frame\n\n gpencil = context.object\n gpencil.data.layers.update()\n for l in gpencil.data.layers:\n l.frames.update()\n for f in l.frames:\n f.strokes.update()\n for s in f.strokes:\n s.points.update()\n\n gpencil.data.update_tag()\n context.view_layer.depsgraph.update()\n context.view_layer.update()\n bpy.ops.gpencil.recalc_geometry()\n\nclass GPENCIL_OT_simple_operator(bpy.types.Operator):\n bl_idname = \"gpencil.simple_operator\"\n bl_label = \"Grease Pencil Test Script\"\n\n def execute(self, context):\n main(context)\n return {'FINISHED'}\n\ndef draw(self, context):\n self.layout.operator(GPENCIL_OT_simple_operator.bl_idname)\n\ndef register():\n bpy.utils.register_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.append(draw)\n\ndef unregister():\n bpy.utils.unregister_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.remove(draw)\n\nif __name__ == \"__main__\":\n register()\n```\n\nPlease disregard the step where I put the GP Object into Edit mode & create a new keyframe. This step is not necessary to seeing the `GPencilFrames.copy` bug.\n[duplicated_frame.mp4](duplicated_frame.mp4)\n\nNot sure if the bug will show consistently, but here is the scene file:\n[Grease_Pencil_Data_Bug.blend](Grease_Pencil_Data_Bug.blend)", "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)", "Sorted Collection info Instance - update problem\nAs showed in the gif, there's an update problem in the spreadsheet, somehow the name get updated when an user change the name in the outliner, but the order stay the same, sending another update signal (refresh the collection picker or edit mode toggle) is needed to refresh the order. \n\n\n\n\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: 3.0.0 Alpha\n\n", "Improve visualisation and manipulation of lights in the viewport\nThe idea is to better control/visualize light parameters in the viewport. Currently we can only control the spot angle of spot lights, the size of area lights and the light direction. \nConcept drawings by @eyecandy for reference, not the final design.\n**Tasks**\n- [ ] visualize light color (translucent filled? opaque outline? center circle?)\n\n- [ ] register gizmo undo\n- [x] make scaling transform follow the cursor exactly\n\nAdd gizmos to\n- [ ] spot light\n - [x] radius\n \n - [x] make scalable even when radius is zero?\n - [x] blend \n - [ ] spot angle via new gizmo type instead of arrow \n- [ ] area light\n - [x] constraint scaling in X/Y directions \n - [ ] beam spread (only supported in Cycles) \n - [ ] clip end/custom distance (only in Eevee) \n- [ ] sun lamp\n - [ ] angular diameter \n- [x] point light\n - [x] size ", "Animated properties of View Layers are not updated when View Layer is not Active\nOperating system: Windows 10, x64\nGraphics card: nVidia GTX 1660\n\nBroken: 3.1.0; 3.1.2; and 3.3.0-alpha (08a39d32)\nWorked: none\n\nI'm compositing separate View Layers of a single scene. To reduce render times, I want to not render View Layers which are currently completely hidden, so I'm animating the \"Use for Rendering\" property of some View Layers.\n\nWhen *rendering*, it always works as expected... but *in the editor*, it seems that View Layers which are not the active workspace view layer do not update their animated properties when I move around on the timeline.\n\n\n # Open attached `bugreport-useforrender.blend`\n ** [bugreport-useforrender.blend](bugreport-useforrender.blend)\n\n **There is one Scene, \"Scene\". There are two View Layers, \"View A\" and \"View B\".** Collection \"Common\" has a camera and light. Collection \"Layer A\" has a Cube. Collection \"Layer B\" has a Suzanne/monkey.\n\n * Set View Layer \"View A\" as active (it should be already in the example file).\n **Observe the active collections. \"View A\" includes only the \"Common\" and \"Layer A\" collections, thus including the cube, camera, and light.** Observe the Graph pane and Properties pane. View A is used for rendering from frames 1 to 60, and not used for rendering from frames 61 to 120.\n\n * Seek to a frame before 60. Render a frame with F12. Observe the monkey and the cube, as expected.\n * Seek to a frame after 60. Render a frame with F12. Observe only the monkey, as expected.\n\n * Set View Layer \"Layer B\" as active, while still on a frame after 60.\n ** Observe the active collections. \"View B\" includes only the \"Common\" and \"Layer B\" collections, thus including the monkey, camera, and light.\n\n * Seek to a frame after 60. Render a frame with F12. Observe only the monkey, as expected.\n * Seek to a frame before 60. Render a frame with F12. ***Observe only the monkey, but both a monkey and cube was expected.***\n\n * Set View Layer \"Layer A\" as active, without changing the current frame.\n * Render a frame with F12. ***Observe the monkey and the cube, as expected, but not as consistent with a moment ago.***\n\n * With either View Layer active, render the whole animation with Ctrl+F12. The resulting animation is always rendered as expected.\n", "Cycles viewport render border no longer shows scene behind with OpenGL\nOperating system: Ubuntu 18.04\nGraphics card: GTX 1080\n\nBroken: 2.80 Hash: 42dd888b98\nWorked: 2.79b.\n\nCycles Preview render removes all shading from the scene. This is very evident when using border renders to help isolate down sections to work on (which is key for working on large scale production scenes.\n\n1. Open attached blend file in blender 2.79\n2. hit shift z in the 3d viewport\n3. notice how you can see the building to the left\n4. close blender 2.79, and open the attahced blend file in blender 2.8\n5. hit shift z in the 3d viewport (blender 2.79 keymap)\n6. notice how you cannot see the building to the left anymore? \n\nThis means that reframing whilst border rendering is no longer possible, nor is it possible to change the border render without guessing to work on a different area of the frame without having to go back to solid mode and then back to rendered mode. Going in and out of solid mode can be 20-30 seconds on production scenes so limiting the amount of switching is important.\n\n[example.blend](example.blend)", "Panel order is not saved when preferences window closes\nWindows 10, GTX 1660\n\nversion: 2.83 (sub 7), branch: master (modified), commit date: 2020-03-10 07:58, hash: 1aa7c4c28a06, type: \nbuild date: 2020-03-10, 08:52:15\n\nWithin the Preferences Editor, you can change the ordering of various sections but the changes are not retained when you close the Preferences Editor.", "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" ]

[ "Sun changes don't update\nOperating system: Ubuntu 18.04.2\nGraphics card: AMD RX 580\n\nBroken: 2.80.66, e60890075b37, 2019-05-16\n\nChanging the sun strength and color via sun settings and node editor doesn't trigger any update in the viewport in Cycles rendered mode\n\n[Sun issue.blend](Sun_issue.blend)\nJust change any value of the sun while in rendered mode in Cycles" ]

[ "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", "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", "Regression: Ambient Occlusion causes shading artifacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.93.1\nWorked: 2.91, 2.92\n\n Under lookdev mode, when object has \"alpha blend\" turned on in the shader, \"ambient occlusion\" with \"bent normal\" option enabled will cause shading artifact that looks like the object is shading flat. \n\nSwitch the scene to lookdev mode. \nCreate a UV sphere\nShade it smooth\nTurn on Ambient Occlusion and make sure \"Bent Normals\" is checked. \nAssign a material to the sphere. \nUnder the material settings turn on \"Alpha Blend\". \nNow the object will look like it's shaded flat/without smoothing. \n\n[Eevee_bug_scene.blend](Eevee_bug_scene.blend)\n\n", "Holdout Fill not working as expected with Grease Pencil\nOperating system: Win 10\nGraphics card: Nvidia GTX 1060\n\nBroken: 2.93\nWorked: unknown\n\nI would expect holdout fills to render as 100% transparent. In Blender's image viewer, they don't - their opacity seems to change based on how bright they are, so white is 100% opaque, but grey is semi-transparent.\n\nSaving the same image to a PNG file, the holdouts are fully transparent, but with aliased artefacts around the edge of the surrounding black strokes, in the colour of the holdout fill. If there is another grease pencil object positioned behind the holdout fill, instead of vanishing, its strokes are tinted the colour of the holdout fill.\n\n\n(The artefacts are more noticeable against a dark or checkered background.)\n\nTry rendering the simple drawing in the attached .blend, exporting a PNG and examining it in an image editor. [holdouttest.blend](holdouttest.blend)", "Texture Paint - Clone tool not working when clone source area out of viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\n\nTexture Paint - Clone tool not working when clone source area out of viewport\n\nImport image as plane- select part of image to clone in bottom part of image. Scroll up to the top part of image so the bottom is not visible = clone tool doesnt draw anything.\n\n\n\n", "Eevee Depth of field creates white outline\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 466.11\n\nBroken: version: 2.93.2 Release Candidate\n\nwhite outlines appear on out of focus objects\n\n\n- open attached file and turn to rendered mode\n\n[dof bug recovered.blend](dof_bug_recovered.blend)\n", "API: Drawing artifact when drawing inside Gizmo and blend mode is enabled\nOperating system: Windows-10-10.0.19041-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 Release Candidate\n\nDrawing artifact when drawing inside Gizmo.draw and blend mode is enabled.\nLook at the line across each graphic/rectangle.\n\n\n[GizmoDrawingIssueBlendAlpha.blend](GizmoDrawingIssueBlendAlpha.blend)\n1. Open the provided .blend file.\n2. Run the script\n3. Look at the simple rectangle and the transparent line across the rectangle\n4. Now try again but remove both 'gpu.state.blend_set' lines\n5. Rectangle is ok\n\nNote: the same drawing code from a [draw callback ](bpy.types.Space.html?highlight=draw_handler#bpy.types.Space.draw_handler_add) works fine without artifact.\n", "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)", "Sculpt brush with texture breaks sculpt tiling\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n\nBroken: version: 2.93.0 Alpha\n\nIf the sculpt brush has a texture enabled with mapping set to *Area Plane*, then tiled strokes break up and do not match properly at the seams.\nIn this example the original stroke is on the right.\n\n\n1 Add texture to a brush\n2 Set mapping to area plane\n3 Enable tiling in the Symmetry drop-down menu\n4 Try sculpting at the seams\n\nOr use the file\n[tiling_bug.blend](tiling_bug.blend)\n\n", "GPU Subdivision Causes Artifacts in Mesh Analysis Overlay\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken:\nversion: 3.1.1 Release Candidate\nversion: 3.3.1\nversion: 3.5.1\nversion: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-25 13:50, hash: 6ee8aa4997ee, type: release\nversion: 3.6.0 Alpha\n\nWorked: could not find.\n\nWhen GPU subdivision is enabled, the Mesh Analysis overlay shows artifacts.\n\n\nPlease follow these steps to reproduce the issue:\n1. Start Blender.\n2. Select the default cube.\n3. Apply the Subdivision Modifier (press Ctrl+1).\n4. Enter edit mode.\n5. In the viewport overlay menu, enable Mesh Analysis.\n\n**Known Workarounds**\n1. Disable GPU Subdivision.\n2. Disable \"Show in Edit Mode\" for the Subdivision modifier.\n\n", "Grease Pencil: stroke placement \"Surface\" projects onto lamps and empties\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: AMD Radeon HD 5700 Series ATI Technologies Inc. 4.5.13417 Core Profile Context 15.301.1901.0\n\nBroken: version: 2.83 (sub 5)\n\nIf you draw with *Stroke Placement* set to *Surface*, Blender interprets objects such as lamps and empties as surfaces and projects the stroke onto them. \nThis might be a feature rather than a bug. Maybe just \"unexpected behaviour\"?\n\n\n\n\n1) Create a new \"2D animation\" Blender file.\n2) Create a mesh (A) to project your strokes onto, like a plane for example.\n3) Create a lamp object or an empty (B), and place it in front of A, closer to your viewpoint in space than A.\n4) Select the GP object and go into draw mode.\n5) Set \"Stroke Placement\" to \"Surface\". (You can add an offset of 0.1 for easier visibility.)\n6) Draw over A, crossing over B here and there.\n7) Rotate your viewpoint. The stroke you've drawn should be projected onto A, with a few points projected onto B where they crossed over it.\n\n", "Workbench: Random object color disables transparency in solid view\nOperating system: Windows 10 64bit\nGraphics card: Nvidia RTX 2080ti\n\nBroken: 2.83.1 official\n\n\n\n\nWhen setting the color of the material in the viewport to be semitransparent (Alpha value = 0.1) it works if the color of the viewport objects is set to \"Material\" it works, while if the color is set to \"Random\" the object is not semitransparent anymore.\n\nBlend file to test:\n[bug.blend](bug.blend)", "GPencil: Canvas Overlay becomes inconsistent when both Object and Layer are transformed\nOperating system: Windows\nGraphics card:\n\nBroken: 3.4.1\nWorked: never?\n\nModifying Grease Pencil Layer transforms affects the Canvas overlay, but when both the Object and Layer have transforms the overlay does not describe the drawing plane actually being used by tools.\n\n- Open attached .blend\n- Draw new strokes into the Lines layer\n- Rotate the viewport to view the stroke placement.\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", " LineArt: (Collection) Issue for Cameras in Orthographic View\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nChecked in Blender version 3.4.0 Apha, commit date: 2022-10-08 02:26 - same issue\n\nFor orthographic Camera without any shifts - Line art modifier (for a Collection) showing lines for objects behind other objects - which otherwise should not be visible. And some lines are not visible which should be.\nHappens with contours option in the Line Art modifier. Slight rotation on z axis solves the issue.\n\nNoticed issue with some specific frames on my complete blend file.\n\nOpen attached blend file and go to front orthographic view.\n\n[BugReport01.blend](BugReport01.blend)\n\n" ]

[ "Texture painting: Brush and fill miss some pixels.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.4 Release Candidate\n\nFinally I can reproduce this bug each time (and it annoys me every time I work with characters).\nTere is file with example: [fill testblend.blend](fill_testblend.blend)\nTry to fill selection \nOperation will leave randomly scattered pixels.\n\nYou can overpaint some of them, but another few pixels you can`t overpaint or you can only from specific camera angle.\n\nDemos:\n[2021-08-22_03-27-01.mp4](2021-08-22_03-27-01.mp4)\n[2021-08-22_03-22-39.mp4](2021-08-22_03-22-39.mp4)\n\nMake lowpoly.\nUnwrap to few islands.\nAdd Multiresolution (4-5 levels)\nAdd black texture (4k)\nSelect some islands in edit mode\nGo to texture paint mode, enable paint mask\nFill with white\nInspect result, you will find missed pixels\n\n\nFrom #95663: this is also true for orthographic view (if zoomed in far enough):\n- brushes wont paint pixels at all\n- fill tool will leave black pixels\n\n- Open .blend file\n- Use fill tool on object in 3DView (will leave black pixels) or\n- Use paint brush (wont paint pixels at all)\n\n\n\nTest File:\n[#95663.blend](T95663.blend)", "Texturing : Generates Diagonal Artefacts \nOperating system: Linux-5.15.4-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken: version: 2.93.6\n\n[Texture Paint: It generates diagonal lignes and dots artifacts on any meshes.]\n\n[\n - 1: Start by subdividing a cube with 4 iterations.\n - 2: Create a 16K texture. \n - 3: Painting on texture Paint mode (brush, fill or quick edit..).\nYou will see dots and diagonal lines on quads.\nMy bug report is also in blenderartists.org : 1340646\n\nThanks for you jobs friends. :)\n]\n\n\n" ]

[ "2.93 EEVEE viewport worse performance on iGPU\nOperating system: W10 20H2\nGraphics card: i5-8250U - IGPU UHD Graphics 620\n\nBroken: 2.93 release (windows store)\nWorked: 2.92 release (windows store)\n\n\nWith the new update i'm getting worse performance in EEVEE viewport, in the 2.92 version i had 18 fps, while in the new 2.93 i'm getting 8 fps\n\nScene has 1.200.000 tris\n\nScene has 40 mb \n\n[castle_of_maldrak.blend](castle_of_maldrak.blend)", "EEVEE: Add support for area light beam spread\nThis feature is already present in Cycles and should be fairly easy to implement as part of `light_attenuation` function.\n\nIt is still unknown if the cycles code can be reused or if we require a different approach.\n\n", "Region overlap crashes when interacting with action zones\nEnable region overlap user preference.\n\nIn the default 3D viewport, press NKey, then drag on the corner widget. -> Blender crashes.\n\nAttached asan output: [region_overlap_azone.txt](region_overlap_azone.txt), [region_overlap_azone_2020_01_28_update.txt](region_overlap_azone_2020_01_28_update.txt) (found while investigating #46764).\n\nUpdated asan output\n\n\n----\n\nNote: Blender internals aren't well suited of handling regions being manipulated like this while the rest of Blender is being used. We could either prevent interaction during the fade, or disable it since its not really needed.", "Correct link is shown as invalid\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIn the composer, after some actions, the link is displayed as incorrect, although there is no reason for this.\n\n**Exact steps for others to reproduce the error** \n\n0. Factory settings file (optional).\n1. Switch render engine to Cycles.\n2. Enable any `Scene > ViewLayer > Passes`. For example, this would be `... > Data > UV`.\n3. Enable the compositing nodes and connect the new socket to the \"Composite\" node.\n4. Switch render engine to Eevee.\n5. Make a Render.\n6. Switch render engine to Cycles.\n\n\n\n", "EEVEE: Crash if computation is too heavy for the system (TDR issue)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nAny time I try to render an image sequence in any format in Eevee, it constantly crashes the whole program on the first frame. I was able to render before until I changed some camera location animations and adding a focusing animation. As well as changing the camera sensor size. I am rendering in 4K I have attached the log file.\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[NebulaV2.blend](NebulaV2.blend)", "Avoid graphical glitches during threaded preview generation\nWhen previews are generated using an OpenGL engine, there can be a number of glitches until the preview is done. That's because some data is accessed/modified that is not thread safe. E.g. `object_preview_render()` modifies `U.pixelsize`. I think other glitches are caused by overriding the active theme in `ED_view3d_draw_offscreen()` - although when I avoided this some time ago for similar work on threaded offscreen drawing for VR, this didn't solve the color flickering.\nThe active theme should probably use thread local storage.\n\nBesides that, the preview generation should be thread safe with OpenGL:\n* It uses the draw-manager's own context, which is mutex protected.\n* The non-thread-safe immediate mode API is not used inside the draw-manager.\n* The draw-manager already has workarounds for GPU driver issues with threaded drawing.\n\nA note: We could also speed up Eevee preview generation significantly by using viewport render quality, not final render quality. The `_imbuf` offscreen rendering functions don't expose the `is_image_render` option for that, which they probably should.", "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.", "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).", "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", "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", "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", "Large soft shadows converge to an incorrect result in EEVEE viewport.\nOperating system: Linux-5.16.0-3-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.54\n\nBroken version: 3.2.0 Alpha\nBroken version: 3.1\nBroken version: 3.0\nBroken version: 2.93\nBroken version: 2.92\nBroken version: 2.91\nBroken version: 2.90\nBroken version: 2.83\nBroken version: 2.82\nBroken version: 2.81\nBroken version: 2.80\n\nWhen rendering large soft shadows in the EEVEE viewport, it converges to an incorrect result at high sample counts. Here are some examples:\n||||\n| -- | -- | -- |\n|EEVEE viewport - 512 samples (\"Mostly Normal\")|EEVEE viewport - 16,384 samples (\"Broken\")|EEVEE final render (`F12`) - 16,384 Samples (To be used for comparison)|\n\n1. Start with the default scene.\n2. Add a ground plane. ({nav Add > Plane} then scale it up and shift it below the cube)\n3. Select the default light and change it's radius to `2m`\n4. Render the scene in EEVEE to a high sample count in the viewport. This can be done by setting the `EEVEE viewport sample count` to something like 16,384 and letting it process. \n5. Render the same scene in EEVEE with a final render (`F12`) and the same sample count and compare it to the viewport result. Notice that it's very different.\n\nNote: Soft shadows is enabled by default in EEVEE in modern versions of Blender. But depending on your defaults, you might have to enable it. It's in {nav Render Properties Editor > Shadows > Soft Shadows}", "Volume scatter shader affects data render passes.\nOperating system: Win 10\nGraphics card: GTX 980ti\n\nBroken: 2.80.74 2019-07-12 17:50 e3c586e262dd\nWorked: unknown (2.79 allegedly has the same issue)\n\nVolume scatter shader affects data render pass (AO, Depth, Normal).\n\n\nRender the scene below. The file has two view layers, one called FOG, and the other NO FOG. The former includes a volumetric object.\n\n[Problem.blend](Problem.blend)\n\n\n**Developer Note**\n\nI tweaked the file a bit (mainly added a texture to compare the changes in the AO pass and the normal and UV.\n[volume.blend](volume.blend)\n\nAnd a comparison between the AO and normal pass for each view layer:\n\n\n\n**Blob from original report**\n\nHello, I'm facing an annoying problem and it's blocking our tries to use Blender as a production tool here at Lightfarm. So, every time we try to use a volume scatter shader to create fog doesn't matter if I use the option inside the world tab or create a cube, invert its normals and apply a volume scatter shader to it. Blender applies noise or color coming from the volume scatter shader in Data render passes, AO, Depth, Mist, Vector, Normal and etc... what gives us a wrong output to be used in Post-Production. I shouldn't be happening. I tried different solutions in a way to get around this problem. Tried different values for alpha threshold, tried to apply a transparent shader in the BOX that has the volume scatter shader applied. Nothing seems to solve the problem. I'd love to hear from you a solution for this. \n\nAlso, using mist pass to comp fog in the post isn't an option here because it's not as realistic as we want or separate the fog in a different render layer because it'll increase our render times a lot.\n", "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", "Volumetrics Doesn't Apply to other meshes created with the Array Modifier\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nIn evee, I have a cube with an array modifier and a volume scatter node in its material. The volume scatter only applies to the original object, not the objects created by the array modifier. However in cycles the volume scatter works as expected.\n\nCreate Cube with Fog material *see attached blend\nObserve where the volume scatter takes effect when switching between evee and cycles.\n\n\n\n[FogBug.blend](FogBug.blend)\n\n" ]

[ "Weird ghosting with Volumetrics on in Eevee\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\nBroken: version: 2.80 (sub 72)\n\n\nWith world volumetrics being used, once the scene gets a little bit more geometry than usual, it starts to create weird ghosting when you orbit. Disabling Viewport Denoise still gives some improper ghosting but without the smudging\n\nOpen the attached file, changed shading mode to eevee, and orbit around\n\n[bugsample.blend](bugsample.blend)\n\n[examplevideo.mp4](examplevideo.mp4)\n\n", "EEVEE viewport smudging / crash with volumes\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.17\n\n\nBroken: version: 2.80 (sub 71)\nWorked: version: 2.80 (sub 68)\n\n\nEEVEE viewport Smudge effect with Collection Instances + Volumetrics\n\nGo to camera view, EEVEE viewport, play scene\n[Smudged Render EEVEE.mkv](Smudged_Render_EEVEE.mkv)\n\n[Corridor Sam Miller.blend](Corridor_Sam_Miller.blend)\n\n", "Look Dev Viewport issues.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\n\nBroken: version: 2.80 (sub 71)\nWorked: The release from 5/13/2019 ~ 3:44pm.\n\n\n\nLatest release is giving me visual issues within the viewport while in LookDev mode. The screenshot is from a file I'm currently working on but is 182 MB. I can upload if necessary. The screenshot is of the file after rotating my view 3 times. The viewport would not update to show my actual view of the scene.\n\n\n\nPlease let me know what other information you might need to figure out if this is on my end or something else.\n\n\nI can only get it to reproduce in one file (but it is one of my more complex scenes.) and all I do is navigate within the viewport.\n", "EEVEE Viewport Becomes and Oil Painting\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.71\n\n\nBroken: version: 2.80 (sub 71)\nWorked: (optional)\n\n\nEEVEE's viewport goes from clear to a smeary oil painting when using Volumetric shader in the World settings.\n\nLoad the attached scene. \nThis is a simple ground plane with a bunch of trees instanced over it using a particle system.\nThe world uses an HDRI image combined with a Principled Volume shader to add environmental fog.\nSwitch to Rendered view.\nFrame 0 of the animation will look normal.\nPlay the animation.\nBy the end, the viewport will appear to melt and swirl into a blurry mess.\n[Smeary Render.blend](Smeary_Render.blend)\n\n\n\n\n" ]

[ "Huge memory usage when trying to paint on UVs far ouside the 0-1 range\nBroken: version: 2.82a (sub 7)\nWorked: Never\n\nBlender freezes when I attempt to use the paint options, after adding an image to Texture Paint. Memory will skyrocket from 150MB to 13GB and does not un-freeze.\nYoutube tutorial I'm following trying to learn to paint textures, bug happens after adding the image at 2:35, and I attempt to paint the model: watch?v=lmbAs9jE1vI\nI am very new to Blender, but pretty sure it shouldn't be doing that when attempting to use the Paint tools.\n\n\n\n- Open attached file\n- Try to paint the mesh\n\n[texture_paint_huge_memory_usage.blend](texture_paint_huge_memory_usage.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", "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", "Blender development todo list -- Render\nNOTE: this is a direct dump of Render (without cherrypicking the valid items)\n\n### Render & UI\n\n- [ ] While rendering, manipulating images (like reload, resizing generated) can still crash Blender. Better image \"owner\" locking is required for 2.5 (#28477)\n- [ ] While rendering, several UI changes can cause crashes (#24758)\n- [ ] Rendering can't really use normal scene data if ui is interactive without causing all kinds of trouble, for examples and related issues see the item above this one.. and the reports (#26535)\n- [ ] Renaming scene leads to missing rendered result in image editor and compositor (see (#30222))\n- [ ] Rendering with File Output nodes could produce unwanted output images, see (#38605)\n- [ ] Shaded draw mode (using render code for vertex colors) is most certainly not coming back\n- [ ] Color Management can be communicated better, like when sampling colors in Image Window it confuses (could indicate such). Color Management also wasn't added backward compatible, disabling it gives dark results.\n- [ ] Compositor \"file out\" node doesn't work for FSA, and as color management troubles too.\n- [ ] FSA render uses temp files with names preventing other Blender instances to render too. (#28314)\n- [ ] Texture nodes have been implemented by recursively (backwards) calling parent nodes, this gives issues for viewers, previews and threads in general.We will try to keep it stable, but the functionality for this is going to replaced with a better shader system in 2.6. (compositor and material nodes call nodes forward, sorted on dependency. Each node is only called once this way).\n- [ ] Render display in Image window, for a window previously showing UV editor, doesn't restore correctly. (#26828). Code for this is too much spread around and fuzzy, needs full revision.\n- [ ] Object transform is not possible during rendering #37019\n- [ ] Don't render and warn when a driver or pre-render script can't be executed, a texture is missing, physics are not baked. Needed e.g. when renderfarms have scripts blocked.\n\n### Node Textures\n- [ ] Grouping texture nodes affects on data range #45696\n\n### Baking\n- [ ] add option to smooth vertex colors as a post process after baking #35066.\n- [ ] Baking to a low-res textures might miss pixels which lies on the UV island boundary #37681\n- [ ] Vertex baking might cause AO artifacts #44178\n- [ ] Support dupligroups #43553\n- [ ] Modifier produces non deterministic effects #42015\n- [ ] Update Blender side baking to support different topologies needed for adaptive subdivision #49405", "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", "Blender freezes with Metal render device\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.5.0\nWorked: None\nAlso Tested: 3.5.1 RC (April 01, 01:59:41, `6fa464d18971`)\n\nBlender freezes after a few seconds when I enable the Metal Render Device in Preferences, switch to Cycles with GPU Compute and switch Viewport Shading to Rendered.\n\n1. **Do not** delete the default cube\n2. Switch to Metal (GPU) Cycles Render Device in Preferences > System\n3. Set GPU Backend to Metal\n4. Switch Render Engine to Cycles and device to GPU Compute\n5. Switch Viewport Shading to Rendered\n6. Wait for Cycles to compile shaders\n7. Look around for a few seconds\n8. Blender Freezes\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", "EEVEE NEXT: Memory leak when switching render type\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.5.0 Alpha\n\n```\nError: Not freed memory blocks: 1, total unfreed memory 0.000038 MB\n```\n\n1. Start render default cube in cycles\n2. Switch no eevee next (render turned to black)\n3. Closed blender", "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.", "OptiX Denoiser fails with large output resolution (final rendering completely black)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nDuring my final rendering, in 100% resolution, the final rendering is completely black. When calculating the image everything looks normal, I can see the tiles generating normally. Then the final render appears black. The other layers (shadow, OA, etc.) are well rendered. \n\nThis looks to be caused by OptiX failing to denoise a very large final image.\n\nThe example here will attempt to render a 6144x6144px image on an 8gb 1070 and fail during the Denoising step (leaving a completely black image too).\n\nThe original report attempted to render at >10240px (so adjust accordingly if it doesn't happen at first with your GPU).\n\n- Load attached `denoise.blend` file.\n- Attempt to F12 render\n\n```\nI0301 12:53:47.768775 15952 path_trace.cpp:971] Processing full frame buffer file T:\\Temp\\blender_a18956\\cycles-tile-buffer-15716-2377920588664-0-0.exr\nI0301 12:53:49.619309 15952 denoiser_gpu.cpp:51] Creating temporary buffer on denoiser device.\nI0301 12:53:50.388029 15952 device.cpp:669] Buffer allocate: RenderBuffers, 2,868,903,936 bytes. (2.67G) in device memory\nI0301 12:53:50.995292 15952 device_impl.cpp:80] using cuda device \"NVIDIA GeForce GTX 1070 with Max-Q Design\" (6.1), buffers: fp16, Winograd convolution, rt v11060\nI0301 12:53:52.356184 15952 device.cpp:669] Buffer allocate: __denoiser_state, 2,999,350,016 bytes. (2.79G) in host memory\nI0301 12:53:52.356184 15952 device_impl.cpp:80] layers created for resolution 4352 4352, inp 8, outp 3\nE0301 12:53:52.356184 15952 device_impl.cpp:74] copy of converted weights failed (CUDA error string: invalid argument, CUDA error code: 1)\nFailed to set up OptiX denoiser\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nE0301 12:53:52.356184 15952 denoiser_optix.cpp:577] OptiX denoiser configuration has failed.\n\n```\n\nVerbose 5 logs attached.\n\n", "Blender 3.1a sticks and doesn't render when rendering with Metal GPU on Mac\nOperating system: macOS-12.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.3\n\nBroken: version: 3.1.0 Alpha\nWorked: This project rendered on the same 3.1a build on the CPU, just not on the GPU.\n\nWhen I render this scene on the GPU, blender just sticks and doesn't render. (Blender 3.1a has always rendered other scenes perfectly on the GPU.)\n\n- Open .blend file\n- Render as Image (`F12`)\n The issue may be at the fault of either the fact that I have displacement on the plane, or that I have 2 render layers\n[try1.blend](try1.blend)\n\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "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)", "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", "Regression: Image rendering fails while viewport rendering is in progress\nOperating system: OSX Ventura Version 13.3\nGraphics card:AMD Radeon Pro Vega II Duo 32 GB\n\nBroken: 3.5.0 Date 2023-03-29 02:56 Hash: 1be25cfff18b \nWorked: 3.4.1 Date 2022-12-19 17:00 Hash 55485cb379f7\nCommandBuffer Failed: cycles_metal_integrator_compact_shadow_states\n\n* Load file provided\n* Set ViewPortShading to MaterialPreview\n* Then select ViewPortShading to Rendered\n* While the viewport is rendering Select Render Image.\n\nThis will often cause the error. It may take an attempt or two but more likely to happen after at least one attempt.\n\nIn some case blender will throw the error in both the viewport and in the image window. In some cases...Blender will hang and require you to force quit. At other times it will crash the OS. \n\nThe larger the scene the more drastic the failure. In this simplified file it typically will recover.\n\n" ]

[ "Optix not working (CPU and GPU) in Viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.93.2 Release Candidate and 3.0.0 Alpha\nWorked: Blender 2.92\n\nBlender cannot build kernel when denoise is enabled. Also freezes when switching modes.\n\nBlender 2.92\n\n\n\n\nBlender 2.93.2 \n\n\n\n\n\nBlender 3.0\n\n\n\n[test.blend](test.blend)\n\n\n\n\n", "Optix kernels not loading\nOperating system: Windows\nGraphics card: rtx 3090\n\nBroken: (2.93 LTS Master Hash 84da05a8b806 2021-06-02 11:21)\nWorked: (2.92 Master Hash 02948a2cab44 2021-02-24 16:25)\n*Experiencing this on May + June Studio drivers\n\n\n2.93 In any scene optix kernels will not load. Set to optix and GPU only in system. When rendering or viewport preview it sits indefinitely\nthrough troubleshooting I read to delete optix cache and let it rebuild. Still no fix. \n2.92 works no problem. \n\nDefault scene otherwise I just downloaded it, has not worked. Cuda works fine though \n\nTest File:\n[default7-5.blend](default7-5.blend)" ]

[ "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", "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", "Closing operator search menu with Escape also cancels bakes\nOperating system: Linux-4.15.0-45-generic-x86_64-with-LinuxMint-19.1-tessa 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.43\n\n\nBroken: version: 2.80 (sub 74)\n\n\nWhen baking something (tested with fluid and light cache), opening the operator search menu (F3 by default) and pressing Escape to close it will also cancel the bake.\nNot tested with other modal operations or popups.\n", "No slash in «Bright Contrast» menu item\nOperating system: Windows 7 SP1\nGraphics card: nVidia GTX 770\n\nBroken: 2.90 last beta\nWorked: 2.79\n\nI noticed that there is no slash in Bright/Contrast menu item in the Color category in the node editor. It is written there as \"Bright Contrast\" (without slash).\n\nOpen the node editor, select the add item, select the Color category and look at the \"Bright Contrast\" menu item.\n", "Support socket icons in the Group Sockets Input/Output type enum\n{[F10225900](image.png), size=full} (crude mockup)\n\nThe issue is that the socket colors are not icons, but maybe they should/could.", "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", "Keyframing Stretch property in IK won't work properly - iTaSC Solver\nDoesn't work in all versions 2.79b, 2.83, 3.00\n\nWhen using iTaSC solver for an armature, you can't keyframe or use a driver for the bone stretch property. If you do it will be buggy and won't work as expected.\n\nThe Stretch property I'm talking about\n\n\n1. Make a a small armature with iTaSC Solver\n2. Add IK Bone Constraint\n3. Animate the stretch property whether in the bone constraint or the bone property\n4. Keyframe your rig and see that it's not behaving properly\n\n**note: I know it may seem incomprehensible but if you click constantly \"Update Dependencies\" in the drivers panel you will see the expected result**\n\n[Bug report.blend](Bug_report.blend)", "Windows IME: Duplicated character when entering some symbols while in Chinese full width character mode.\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 471.41\n\nBroken: version: 3.2.0 Alpha\n\nDuplicated initial character when entering some symbols while in Chinese full width character mode.\nThe problem is the same as in #94868.\n\n\nIn Microsoft IME PinYin (Chinese Input) fullwidth mode, when entering some symbols at text edit, it duplicate characters.\n\nThe symbols are `-=~@#%*+{}|` in reference to the image below.\n\nAll symbols are shown below. Four rows represent four rows on the keyboard.\n\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 ", "The 3d cursor looks very dim on AMD cards with the Mesa driver.\nOperating system: Gentoo Linux\nGraphics card: AMD Vega64\n\nBroken: All current Blender versions (2.93 to 3.5)\n\nThe 3D cursor in the viewport seems to be drawn with transparency.\nHowever this is only an issue on AMD cards it seems.\nIt started happening 4-5 months ago, so this is most certainly a driver issue.\n\nOpen the default cube scene and observe that the 3D cursor looks very dim:\n", "Text editor slider now blocked\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.81 (sub 1)\nWorked: 2.80\n\nNow that the sidebar got moved to the right side, there's times when the slider gets blocked by the arrow and you can't select and move down. \n\n\n\n", "I have glitch when i turn on my Motion blur with a shape keys animate\nHello, \n\nOperating system: Darwin-19.4.0-x86_64-i38{[F8688055](Capture_d_e_cran_2020-07-12_a__01.21.11.png)}\n\n{[F8688058](Capture_d_e_cran_2020-07-12_a__01.21.11.png)}6-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.90.0 Alpha\n\nI tried with Eevee i don't have the problem only with cycles. \nIs only when i render animation or image. I can't see this glitch on viewport.\nI tried with blender version on mac and window and multiples different graphics card but the problem is still append.\nWith or without modifiers or movement of camera still in. \n\n\n\n\nOpen blender with love.\nMake a beautiful animation with shape keys.\nTurn on motion blur.\nProblem when i render :( \nClose blender but with love to help. :D \n\nThanks you \n\npacpac\n\n{[F8688074](Capture_d_e_cran_2020-07-12_a__13.46.43.png), size=full}\n\n\n\n\n\n", "Huion KD100 - incorrect programmable keys reading\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 27.20.100.8477\n\nBroken: version: 3.3.1\n\nHi, I got a Huion KD100 Mini Keydial and Blender seems to be the only software not regonizzing it's programmable keys correctly. I have set it up as Numpad keys, but Blender does not recognize the assigments, reading the keystroke values for Num Lock off. Affinity Designer, Photo, Google docs, everything else recognizes the defined keys, even with app profiles. Sadly Blender does not as the only one.\n\nThe only step here is really to hook up a configured KD100 and trying to change the view. Can also be easily verified in the Preferences section by testing the key bindings. \nI would be more than happy to test/debug further with my device if that's helpful.\n\n", "Weird Tab and redraw behavior in color popup\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA TITAN V/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.27\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93 has weird Tab behavior, but not redraw artifacts\n\nTab and redraw is not happening correct for RGBA color wheel popup. Almost as if sliders from different modes are drawn on top of the active ones.\n\n\n1. blender --factory-start\n2. World buttons\n3. Click on the Color to open color wheel popup\n4. Switch to RGB\n5. Click on the first slider (R)\n6. Start hitting Tab and see what happens with the values in the sliders (takes 4 times to tab from Blue channel to Alpha)\n\nIf you type values in the sliders things gets even more confusing.", "NLA: Animated Influence/Time Property Sliders Unresponsive\nTask: #76549 (NLA Strip influence slider doesn't respond to autokey correctly.)\n\n**Source of Problem**: (anim_sys.c) *nlastrip_evaluate_controls() -> animsys_evaluate_fcurves()*: I believe the issue is due to NLA evaluation, where the animated strip properties are evaluated and flushed at the same time the action strip channels are evaluated. Since autokeying doesn't insert a keyframe as the value changes, that's probably why the slider is unresponsive. \n\n**Solution**: Perhaps we should separate (despgraph-wise) NLA strip animated property evaluation from when we evaluate the NLA system for general animation? Animated strip properties would only be evaluated and flushed on frame change or when the whole frame needs refreshed. Then normal non-NLA animation evaluation will just read the strip properties as is. This would allow the slider be responsive. It also allows the user to change these properties and view their changes without having to keyframe, just like any other Blender animated property. \n\n**Potential Problems with Solution:** What do we do when strip influence is animated and the user changes it (without keying) then inserts keys on character bones. When we remap the keyframes, should we re-evaluate and use the strip's animated influence? Or should the new keys be remapped using the unkeyed strip time?" ]

[ "Arrow Keys cannot walk the search menu (F3)\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.82 (sub 5)\nWorked: (optional)\n\nWhen I type in the search menu (the popup menu), and press the arrow keys, it does not let me walk the menu but instead enter a weird non existent key icon.\nThis is only happening with the pop up search menu shown in the video.\n(ie F3 and Shift A in animation nodes)\n\nPress f3, then try to walk the menu with the down arrow.\n[menu_walk_error.mp4](menu_walk_error.mp4)\n\n", "Pressing the down arrow in the operator search field adds a  character instead of going down\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M395X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.82 (sub 5)\nWorked: (optional)\n\nPressing the down arrow in the operator search field adds a  character instead of going down\n\n - Open the operator search by pressing F3\n - press the down arrow to move to the next item\n - Rather than moving down by one, a  character is added to the search query:\n\n\n\nThe Terminal shows this message:\n\n\n\n" ]

[ "popup window call operator will crash blender\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.2.0 Beta\n\nThis script is use to check the active material, it can be run correct in the main window, but not popup window(change the pref window to node editor)\n```\nimport bpy\n\nbpy.ops.screen.userpref_show(\"INVOKE_AREA\")\narea = bpy.context.window_manager.windows[-1].screen.areas[0]\n\n\narea.type = 'NODE_EDITOR'\nflip_header = True\narea.ui_type = 'ShaderNodeTree'\narea.spaces[0].node_tree = bpy.data.materials['Material'].node_tree\n\nfor region in area.regions:\n if region.type == 'HEADER':\n with bpy.context.temp_override(area=area, region=region):\n if flip_header: bpy.ops.screen.region_flip('INVOKE_DEFAULT') # this line will not\n\n if region.type == 'WINDOW':\n with bpy.context.temp_override(area=area, region=region):\n bpy.ops.node.view_all(\"INVOKE_AREA\") # this line will report context error\n```\n\n- Open .blend file\n- Execute script\n[#98491.blend](T98491.blend)\n\n\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.", "Texture Node editor --->creating image , then use created image as input node in texture node editor \nwin 10 \namd radeon \nintel i5\n\n Blender 2.8\n3d8cbb534f82\n\n\n First of all ,this is specifically about the \"texture node editor set to brush for creating an image , then using the created image as an image input in the (brush ) node editor , and again paiting in the SAME image ...\nIt totally makes sens that blender crashes because it is trying to create an image where the brush is that image itself , thus creating a feedback loop \n\n\nSteps to reproduce crash\n\n\n- Create plane \n- Go to the shader editor and create an image texture node \n- Create a new file , let's call this one ''crash'' and route it the shader's colour input \n- Go to the 'texture node editor and from the dropdown select 'brush''\n- Click the 'new tab' and enable úse nodes , by default we are presented with the checker pattern \n- go to the image editor and draw something , we are presented with a checker pattern \n- Now go back to the texture node editor'' and select ímage 'from the input nodes and route it to the tout\n- Select çrash 'as image \n- Now paint something in the image editor \n\nCrash \n\nIn the provided file , everything is already set up , al you have to do is paint in the image editor , and then route the module labeled çrash'to the output of the texture node editor [feedback crash .blend](feedback_crash_.blend)\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", "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", "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", "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "Vertex/Edge Slide stuttering with modifier.\nOperating system: Windows 11\nGraphics card: RTX 3070\nCPU: Ryzen 5900x\n\nBroken: 2.83 and all other.\nWorked: 2.79b\n\nVertex/Edge Slide freezes a lot with subdiv modifier in a relatively simple object.\n\n| With `Use Limit Surface` | Without `Use Limit Surface` |\n| -- | -- |\n| https://projects.blender.orgattachment | https://projects.blender.orgattachment |\n\n1. Import attached fbx.\n2. Add subdivision modifier set to 1 subdivision.\n3. Select the loop in the middle.\n4. Edge slide.\n\n", "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 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", "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", "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.", "Error message and unable to edit a skeleton when using a library override armature\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.0\nWorked: No idea.\n\nBlender generates an error when you attempt to enter edit mode on a library overriden armature. There's no description of what the error is or if there is some extra step to make it work. Hopefully this isn't one of those, \"works as intended issues,\" because then there's no way to make multiple characters share an updateable base rig.\n\n\n- Add an armature, enter edit mode, extrude out a few bones.\n- Save the file and open a new scene.\n- Link in the armature you just created.\n- Make the armature a library override.\n- Try to enter edit mode. Should get an error.\n\n", "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`: ", "Crash on Changing Repeat value to -1 in Corrective Smooth modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 2.93.5\n\nNot Responding when I change the Repeat value to -1\n\n{[F11810617](image.png), size=full}\n\n" ]

[ "Crash when enter in Edit mode\nOperating system:Windows 10 64, [email protected],16 RAM\nGraphics card:1050ti 3Gb vRAM\n\nBroken: 2.80 Beta 16fc62e15f0\n\nToday morning I got crash during work, then I've opened the autobackup file. Mine texture was lost link because autobackup save in to temp folder.\nSo I've not update the path for texture (btw this no matter, seems we get crash will be even with path setted), instead turned on texture in Shading -> Color - Texture. And I tried to enter in edit mode. And got crash.\n\n1 - Open the file.\n2 - Turn on texture in Shading -> Color - Texture.\n3 - Press the Tab key.\n\n[lab_28_09.blend](lab_28_09.blend)\n\nI've digged more in file. Seems trouble exactly in this mesh \"lab_ceiling_3x3m.001\".\nI've attached this mesh to new created plane - and crashing gone.\nHope this help." ]

[ "EEVEE: Add support for extracting alpha channels from a color\nI mistakenly filed a bug report --> #72856 EEVEE transparency problem with mtpaint PNG\n\nI didn't fully understand the bug and attached a blender file that didn't show the bug properly.\nPacking the image file with blender command 'Pack' makes the image\nopaque so it is worthless to include a blender document. I will\ninclude a mtpaint PNG image instead and you can load it into\nblender 2.81 yourself and see how it renders in EEVEE versus cycles.\n\nI noticed that your forum converts the image to opaque if I try to attach to this post\nso I'll use a shareable link that preserves the transparency:\n\nopen?id=1TjfSjzabYEmVHXTODPFymGVNwuL02SnJ\n\nHere is how I created the mtpaint image to reproduce the problem...\n\n1) Launch GIMP -->new gimp document -no alpha channel - paint with brush\n2) save as PNG format with no alpha channel\n3) Launch mtpaint ---> open the PNG document\n4) 'Save as' to output the document - one color chosen to be transparent - PNG format\n5) Launch blender 2.81 (linux) - images > Images as planes\n\nEEVEE rendering doesn't respect the transparent region.\nCycles rendering does respect the transparent region.\n\n\nNot a high priorty.", "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", "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.", "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", "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", "EEVEE - Screen space reflections artifacts\nOperating system: Linux-5.3.0-7625-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 2)\nWorked: ?\n\nSSR shows some strips when I have bad data for normals.\n\nOpen the file:\n[ssr_sripts.blend](ssr_sripts.blend)\n\nIf you click anywhere multiple times, viewport gets darker and darker.\n\nBefore:\n\n\nAfter clicking the glossy node header a few times:\n\n", "Render Artifacts with SSS + Motion Blur + Use Spacial Splits\nWhen you have the \"perfect storm\" of Subsurface Scattering, Motion Blur, and \"Use Spacial Splits\" (Render>Performance) all applied to an animated mesh, the rendered image will exhibit some pretty severe artifacts and mesh cracking on certain frames of an animation.\n\nThe main issue appears to be related to \"Use Spacial Splits\"\n\nOpen the attached zip - watch the comparison video. Open the .blend file, hit F12 to render (frame 34 is a good example)[Spacial Splits +Motion Blur Artifact Bug.zip](Spacial_Splits__Motion_Blur_Artifact_Bug.zip)\n\n[Render Bug - Spacial Splits + Motion Blur + Sss-1.m4v](Render_Bug_-_Spacial_Splits___Motion_Blur___Sss-1.m4v)", "EEVEE viewport error when using volume and lights (with animation)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.25\n\n\nTested with the following two versions:\nBroken: version: 2.80 (sub 75)\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\n\nWhen enabling a Volume Scatter shader in the World Settings with anisotropy set to 1.0, a simple point light is emitting a streak of light when the camera is animated. This does not show when the animation is rendered.\n\n\n\n[eevee_volumetric.blend](eevee_volumetric.blend)\n\nWith the attached .blend file:\n - Open the attached .blend file\n - Switch to rendered view (renderer should be Eevee)\n # Play the animation\n\nTo reproduce from scratch (just for info on what I did)\n\n - Default scene, delete cube, renderer should be Eevee \n - set intensity of point light to high intensity (1000W or so should be enough to see the effect)\n - add Volume Scatter BSDF to Volume output of the world shader with low intensity (0.010) and Anisotropy set to 1.0\n - Place the light so that it can be seen in camera view somewhere on the right side and animate two keyframes for the camera so that the light moves from right to left. (Test file anmiates for 40 frames)\n # switch to Rendered view and play animation\n\n\n**Note 1**\nHas been reported as second issue in #58023 with the system info below, so reporting it separately here to be able to close #58023 as the primary issue there is solved.\n\nSystem Information\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\nBlender Version\nBroken: version: 2.81 (sub 11)\n\n**Note 2**\nI wasn't sure if #53588 could be same underlying cause, feel free to de-duplicate this report if it is.\n\n**Note 3**\nI checked that it also happens when using scene lights and world in 'Material Preview' (LookDev) mode\n\n\n\n", "(Linux; AMD Radeon GPU) Rendering a complex scene with eevee crashes desktop environment / causes rendering and viewport artifacts\n```\nOperating system: EndeavourOS Linux / Fedora Linux (Same issue on both distros)\nGPU: AMD Radeon RX 6800 XT (16 GB VRAM)\nCPU: AMD Ryzen 5 3600\n```\n\n```\nrenderer:\t'AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64)'\nvendor:\t\t'AMD'\nversion:\t'4.6 (Core Profile) Mesa 22.3.7'\ndevice type:\t'AMD'\nbackend type:\t'OPENGL'\n```\n\nBroken: 3.4.1, 55485cb379f7, blender-v3.4-release; 3.5.0 Release Candidate, d5d8246441a5, blender-v3.5-release (both version exhibit the issue)\n\nWhen rendering complex scenes in Eevee (Scenes with many different objects), one of the following occurs:\n\n 1. On **X11**: Computer freezes for about 5 seconds before all monitors cut to black. After about 5 seconds on a black screen, the login screen appears and I can log in as normal, as if I logged out. All of the applications have closed.\n 2. On **Wayland**: Render finishes rendering, but many of the objects appear broken; they are semi transparent or appear as if they were using the holdout shader. Returning to the viewport causes all objects with transparency to flicker randomly and appear distorted. Occasionally, the desktop of the computer itself will become broken and artifacted, only logging out or restarting fixes it. This usually isn't possible, however, as after a short while everything all displays cut to a black screen. Unlike X11, however, the only way to recover from this is to restart the PC by holding down the power button.\n\nThis issue **only occurs on linux and does not occur on my Windows 10 partition**, even with the exact same settings and scene. It also only occurs when actually trying to render the scene. In the viewport everything works just fine, even on rendered view where everything looks the same as it should in the render.\n\nThis issue seems to occur regardless of the GPU Usage; even when I limit the GPU clock and power draw significantly it still happens.\n\nThe attached .blend file is an example of a simple scene which triggers the bug. It seems to occur no matter what the render settings are set to.\n\n", "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)", "Regression: Ambient Occlusion causes shading artifacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.93.1\nWorked: 2.91, 2.92\n\n Under lookdev mode, when object has \"alpha blend\" turned on in the shader, \"ambient occlusion\" with \"bent normal\" option enabled will cause shading artifact that looks like the object is shading flat. \n\nSwitch the scene to lookdev mode. \nCreate a UV sphere\nShade it smooth\nTurn on Ambient Occlusion and make sure \"Bent Normals\" is checked. \nAssign a material to the sphere. \nUnder the material settings turn on \"Alpha Blend\". \nNow the object will look like it's shaded flat/without smoothing. \n\n[Eevee_bug_scene.blend](Eevee_bug_scene.blend)\n\n", "EEVEE Next - 'Alpha Blend' - distant objects - shadow buffer overflow\n### Reported as per @fclem [request](111809#issuecomment-1014998)\n\n--\n\nLinux Mint 21.2 Cinnamon kernel 6.2.0-32\n3400G\n\n- Broken\nblender-4.0.0-alpha+main.b5c89822ac40-linux.x86_64-release.tar.xz\n\n- Worked\nN/A (new feature).\n\n- Short description of error:\nWhen an object's shader uses Alpha, and (Material tab) 'Blend Mode' uses 'Alpha Blend', distant objects cause a shadow buffer overflow.\n\n- Exact steps\n1. Open following .blend file and zoom (far) out / back in.\n[EEVEE Next - 'Alpha Blend' shadow buffer overflow.blend](attachment)\n\n2. Appears no issue while using 'Alpha Clip' or 'Alpha Hashed'.\n\n'Alpha Blend' preferred for preventing Z fighting in Orthographic view.\n\nKind regards.\n\n**Screenshot**\n\n\n", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "Black Artifacts While Using Adaptive Subdivision\n{[F7718097](bug.png)}Operating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\n\nBroken: version: 2.80 (sub 75)\n\n\nBlack artifacts on edges of geometry while using adaptive subdivision. I was trying to duplicate my workflow from other 3d software. Extruding geometry from 2d curves creates extra edges on the model. And extra edges create weird shadows on displacement.\n\nImport curve from dxf file. Use extrude Object Data > Geometry. Fill mode: Both. Use subdivision and displacement.\n\n[1.blend](1.blend)\n", "Cycles: Motion blur Artifacts and high render time with Metaball\nOperating system: Ubuntu Linux 22.04 / Windows 10 64-bit\nGraphics card: Nvidia GeForce RTX 3080\n\nBroken: 3.60, 3.61, 3.62, 4.0.0-alpha+main.d0dcfb815964\nWorked: unknown\n\n**Short Description**\nActivating motion blur in Cycles results in artifacts and higher render time for 2% of frames\nReproducible across Ubuntu/Windows, CPU/CUDA/OptiX.\n\n\n- Open attached file \"phoenix12-reprocase.blend\"\n- Enable motion blur (should already be enabled)\n- Reduce transmission bounce\n- Render frame 189\n- Render frame 190 (takes significant time to render. Also notice Artifacts)\n\nIn the provided file, frames 74, 124, 179, 190 seem to have this problem. Turning off motion blur fixes the problem.\n\n|189 | 190 |\n|---|---|\n|  |  |" ]

[ "AO+DOF+OVERSCAN White Block Artifacts on EEVEE render\nOperating system: MS Win 10 Pro\nGraphics card: GTX 1070 ti\n\nblender-2.80.0-git.b0dee09a6d55-windows64\n\nWhite Block Artifacts appears in EEVEE render (not in viewport). On certain frames, usually on hair reflection. In this scene, they appears when all these setting are on in render setting, AO + DOF + Film Overscan. \n\n\n\n\n\n\n\n[AO DOF OVERSCAN White Artifacts Bug.blend](AO_DOF_OVERSCAN_White_Artifacts_Bug.blend)\n", "Horrible fireflies in Eevee making rendering impossible bug\nOperating system: Windows 7 SP1 64 bit\nGraphics card: GTX 1050 Ti\n\nBroken: 2.8 Beta, 319b9d6501f2 2019-02-17\nWorked: (optional): None.\n\nFlashing lights appear during render with high sample (appear at 64 and 32 samples at 1080p 25 fps, don't appear at 4 samples, at 60% of 1080p). If bloom is on, they will become huge, if bloom is clamped at like 500-1000, there will only be small squares and white dots during animation render. Clamping screen space reflections has no effect on it.\nIf you face the direction of the sun, there will be more, if you face opposite direction they will appear less frequently.\n\nI can't share the project file that I'm working on but I nerfed it down to have basically nothing except the settings and the camera and the sun lamp. Use a HDRI (I used a 8k one) for lighting.[Fireflies bug.blend](Fireflies_bug.blend)\n\nTest video (original animation had multiple of them not just 1-2).\n[Scene 01 mini test new 64 samp, screenspace clamp0000-0020.mp4](Scene_01_mini_test_new_64_samp__screenspace_clamp0000-0020.mp4)\n\nOn Blenderartists I saw a recent post with a similar problem so it's not just me and my file.\n", "Eevee rendering \"fireflies\"\nOperating system: Windows 10 64-bit\nGraphics card: Geforce GTX 970\n\nBlender 2.8\nDate: 2018-12-22 00:52\nHash: dafaa6f22881\nBranch: blender2.7\n\nI'm getting these white pixels/squares/rectangles in my Eevee renders. I've only ever seen it occur on top of particle hair and card-based hair with \"hashed\" transparency.\n\nDuring an animation it will only happen on certain frames, and assuming nothing is changed will always appear on that frame when rendered.\n\nThe artifacts always seem to be either 1x1 pixel, 1x2 pixels, 2x2 pixels, or 6x8 pixels, and can be affected by depth of field, bloom and other effects probably. One of the frames I've rendered has a blurry white blob about 140x140 pixels.\n\nThis is very frustrating because it's happening in a \"production\" file with many commercial assets so I can't upload the file. I also haven't been able to reproduce it in a simple file. I may be able to trim the file down if necessary.\n\n\n\n", "Weird black spots in render\nOperating system: Windows 10\nGraphics card: GTX 1050 ti\n\nBroken: 2.80, 38984b10ff7b, 2019-02-04 13:09\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nI keep getting weird black spots in the render. I'm rendering an animation and it seems to only happen on some frames, randomly. [SHot 4.blend](SHot_4.blend) \n\nCrtl F12" ]

[ "C and V keys pressed while drawing a Grease Pencil stroke unchangeable in keymaps\nOperating system: Windows 10\nGraphics card: RTX 3070\n\nBroken: 3.0.0\nWorked: n/a\n\nWhile in the middle of drawing a stroke, pressing C and V keys toggle guides on and off. \n\nThe C and V keys can be bound to something else in preferences, but whatever you bind them to, pressing them while in the middle of drawing a stroke still turns the Guides on and off. I can find no listing for these shortcuts in the Keymaps section.", "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", "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", "Pie menu design improvements\n\nNow that we are adding more pie menus, we could make some small but effective improvements to them.\n\n## Wedge Highlighting\nFirst, the wedge could be highlighted as you rollover it, to make it clearer how big the area is, like so:\n\n\n## Holding, Then Releasing Key Should Always Dismiss Pie\nThere's a slight quirk in the way we handle input: Normally, if you hold a key to invoke a pie menu and then let go, the pie menu is dismissed. This works if you move your cursor to an item, or to an empty area. But, if you don't move the cursor at all, this doesn't work. This makes the behaviour inconsistent, and makes the pies 'stick' in an annoying way if you regret opening one.\n\n## Letter Input While Pie is Active\nWhile number input works reasonably well, in Blender we also use letters to invoke options in menus. For pies, letters work better, because the order makes less direct sense. There's nothing intuitive that says left=1, right=2, and so on. We should enable letter input to activate pie options. This way, user can press Z, S to activate Solid Mode.\n\n----\n\nThese three changes should make pie menus more delightful to use.", "Lag Adjusting Value Sliders & Navigating Nested Menus with a Wacom Tablet\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93.2\n\nTrying to change the value of shapekeys or shader sliders with my stylus doesn't get detected the first few seconds, then picks up, but in a non responsive way. Also while using my stylus, if I navigate to a nested menu like say \"Object > Transform\" There's a Lag when moving to another option in the \"Object\" Menu.\n\nThe steps above should apply. I did notice though, that if I change my Tablet API from 'Automatic' to 'wintab' in the the input preferences, it helps, but its still not as responsive as it is in 2.93\n\nAll these issues though, were non existent, if I tried using my laptop's trackpad. Also, my tablet is a Wacom Intuous Touch 5 with a stylus that supports up to 2048 levels if pressure sensitivity and has tilt support, just incase it could be any of these causing the issue. \n\nThanks.\n\n", "Cursor jumping to edge of screen when lifting pen from tablet area (wintab)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Beta\nWorked: 2.93\n\nTablet model: Huion h950p\nTablet api: Wintab\n\nWhen lifting the pen away from the tablet area, the cursor occasionally jumps to the edge of the screen, causing unexpected camera jumps or preventing hotkeys from being used in the 3d view.\n\nThe problem only happens with the Wintab api.\n\n\n - Set the tablet api to Wintab\n\n - Start creasing some edges and repeatedly lift and return the pen to the tablet area\n\n[cursorjump.mp4](cursorjump.mp4)\n\n", "Problem with mouse walk navigation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.90\n\nBroken: version: 2.91.2\n\nWalk navigation breaks when key map is changed for Up and Down operation.\n\n- Load blender with factory settings\n- Open keymap from `Edit -> Preferences`\n- `3D View -> View 3D Walk Modal`\n- Change key value for Up and Down\n- In viewport `View -> Navigation -> Walk Navigation`\n- Use updated keys to move Up and down\n\n\n\nAs far as i could see, the problem happens when instead of the q down and e keys we put the midle mouse roll up or down. As you can see in the picture. I have tried with other keys and each time there is a problem with the middle mouse button. Simply the middle mouse button goes up, but when it turns so rool down it doesn't work?\nDoes it fix it or do you have an idea how to fix it?\n", "Multi-Button Drag: not working properly for Object Dimensions\nWindows 7\n\nBroken: 2014-02-11\n\nMulti-Button Drag - D270 - doesn't work properly in N panel for Dimensions\n\nIf you drag over all 3, only X and Z change, Y remains unchanged. As mouse button is released, the first selected property will reset, only the last hovered is kept (and scale changed)", "Click selecting a keyframe in the Dope Sheet deselects all channels\nOperating system: Linux Mint\nGraphics card: RTX 3070\n\nBroken: latest master\nWorked: checked until 2.93 and it still was broken\n\nWhen click selecting a keyframe on a summary channel in the Dopesheet (and the Timeline which is basically a Dopesheet),\nit deselects all channels.\nIf you drag select it, all channels of the keys are selected.\n\nClick selecting a keyframe that is not on a summary channel does select the channel as well.\n\nI would expect click and drag select to behave the same on summary channels.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n* open the provided blend file (channels are already selected)\n* click select a keyframe on a summary channel in either the Timeline or the Dope Sheet\n* note the channels are all deselected\n\n", "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)", "UI: Wrong text cut-off without \"…\"\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\nBroken: version: 2.80 (where `…` first appeared)\nWorked: never\n\nWhen text can't fit into designated area Blender will cut off last characters and adds `…` at the end. However in some cases it will not add it, instead plainly showing incomplete test.\nAdditionally with long text and limited space Blender will cut middle of a text like this: `start text … end text`. Issue also affecting this case and sometimes will make text to look like this: `start text … end tex`, without last letter.\nThat works for other areas like `Properties Editor`.\n\n1. Open preferences, go to `Keymap`.\n2. Resize window carefully and look how end of a text is behaving.\n[Wrong cut-off with ...2022-01-19 14-02-00.mp4](Wrong_cut-off_with_...2022-01-19_14-02-00.mp4)\n", "Operator macros [e.g. ARMATURE_OT_duplicate_move] have non-functional 'Proportional editing' option in Adjust Last Operation panel\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nDuplicating a bone in edit mode. In the Adjust Last Operation panel there is a proportional edit checkbox. Which can't be activated.\n\n\nOpen Blender\nCreate armature\nSwitch to Edit Mode\nDuplicate the bone\nIn Adjust Last Operation panel try to activate Proportional editing.\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).", "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 ", "Walk navigation stylus issues in 2.92 - no mouse input until alt tabbing (regression)\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0 Alpha\nWorked: version: version: 2.91.0 *\n\nWalk mode seems to be a bit broken in 2.92 alpha (with both mouse and wacom tablet)\n- The issue only happens if Walk mode is entered via keyboard shortcut\n- alt tabbing out and back into the blender seems to fix the mouse lock\n\n\n*Important note:\nI noticed that this issue is a bit less severe in an older 2.92 build !!2.92.0 Alpha!!, there was still an issue where wacom stylus had to be lifted from tablet surface and placed down again in order for blender to start registering mouse movement in walk mode. (The mouse worked fine, this is pen tablet only issue)\n\n**Here's a short video demonstrating issue**\n- Example 1: Blender 2.91 hash: `0f45cab862` - Works as intended\n- Example 2: Blender 2.92 hash: `c1740e9ad0` - Works BUT only if stylus is lifted from screen (note stylus diagnostic screen on right side)\n- Example 3: Blender 2.92 hash: `acbda123ad` - Only works if user alt tabs from the window itself\n[2021-01-13 00-09-24.mp4](2021-01-13_00-09-24.mp4)\n\n\n- Default document\n- 3D Viewport > View > Navigation > Walk Navigation - Assign a keyboard shortcut (eg: Shift + F)\n- Press the previously defined shortcut\n- Walk mode crosshair appears but mouse is locked\n- Alt tab out and back into blender\n- Now walk mode works " ]

[ "Blender File View - can't type space while holding shift key.\nOperating system: Windows 10\nGraphics card: RTX 2070SU\n\nBroken: 2.93.0 Alpha\nWorked: 2.91.2 \n\nWhen I type name of file holding at the same time shift (for capital letters) space symbol won't type.\nThat type of typing was working in 2.91.2.\n\n\n", "Space bar not working in Outliner if Shift key is pressed\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\nI was renaming all my items. Most of them are 3 capital letter, then a space then again a capital letter like \"MEA Wall\"\n\nGo to the outliner, and press F2 (or double click) on an item.\nSo I would press the following keys\n- Press Shift\n- Press MEA\n- Press space bar (nothing happens)\n- Press W\n- Release shift key\n- Press all\nResult is \"MEAWall\" with the missing space.\nI first thought my space bar was defective, but it works if you release the \"shift key\" at the moment when pressing the space bar.\n\n" ]

[ "When you clear measurements through View > Annotations, they don't vanish immediately\nOperating system: Windows\nGraphics card: GTX-2080\n\nBroken: 3.4.1\n\n\nDeleting measurement annotations appears to be broken because the UI is not refreshed until you change tool.\n\n\n1. Create some measurements\n2. Open View settings Tab\n3. Remove ruler Annotations\n\nExpected behavior: Measurements are removed and action can be undone.\n\nCurrent behavior: The Annotation is no longer visible in the annotation list, but still shown in edit view.\n\nHere is a screen recording: 185530\n\n", "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", "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)", "Mask invisible on object with modifiers when entering sculpt mode\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 3.0.0 Alpha\nWorked: unkown\n\nWhen selecting a previously unselected object with a modifier and a sculpt mask, the mask is invisible at first when entering sculpt mode.\nPainting the mask reveals it.\n\n- Create an object with a modifier (e.g. mirror or array) and paint a sculpt mask on it. Or use the file attached.\n- Outside the sculpt mode first make sure the object is unselected, then select it and enter sculpt mode.\n- The object appears with no mask visible, still you can not sculpt the masked parts.\n- Painting the mask reveals it.\n\n[mask.blend](mask.blend)\n\n[mask.mp4](mask.mp4)", "Cycles cryptomatte is noisy around materials with fully transparent shader\nOperating system: Windows 11, x64\nGraphics card: NVIDIA Quadro RTX 4000\n\nBroken: 3.5.0 Alpha\n\nWorked: None\n\nTwo problems can be observed in the compositor (cf. attached .blend file):\n1) the matte from the cryptomatte node (monkey + glasses) is slightly inferior to 1 around the lenses of the glasses (transparent material) even where the monkey is behind the lenses. This matte should be the same as the alpha channel from the \"foreground\" view layer.\n2) when setting the collection with all the objects (monkey + glasses) to holdout in the \"background\" view layer, the lenses (not the whole glasses) still appear on the matte from the cryptomatte node and connected to the same \"background\" view layer whereas it shouldn't (as the collection is holdout from the \"background\" view layer).\n\n- Open attached .blend file [SEGM_MASK_Blender_bug_v2.blend](SEGM_MASK_Blender_bug_v2.blend)\n- Open the compositing workspace\n\n\n- F12 to render (using Cycles)\n- See the differences between the alpha channel coming from the \"foreground\" view layer and the matte from the cryptomatte node and connected to the same \"foreground\" view layer.\n\n- See that (only) the lenses of the glasses still appear on the matte from the cryptomatte node and connected to the \"background\" view layer whereas it shouldn't as the whole collection of objects is holdout from the same \"background\" layer.\n", "Changing the 'Render Region' when rendering with Python with 'Persistent Images' checked results in glitched renders\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 1)\nWorked: -\n\n\nI have a (simplified) script that moves to a specific frame, sets the render region to a specific position and renders, before repeating the process for the next frame with a new render region position. When the 'Persistent Images' option in *Render> Performance> Final Render* is on, some of the resulting renders are glitched (they open but have artifacts) and the objects do not seem to be in the correct position. \n\nTurning off 'Persistent Images' results in renders with the objects in the expected location and without artifacts.\n\nFor some context, I do not specifically *want* to have 'Persistent Images' on; I have an add-on which repositions the render border on a per-frame basis and a user reported glitching renders.\n\n**Frame 8** - Persistent Images **off**- Correct location in render\n\n\n\n**Frame 8** - Persistent Images **on**- Incorrect location in render and artifacts\n\n\n\n**Frame 7** - Persistent Images **off**- Correct location in render\n\n\n\n**Frame 7** - Persistent Images **on**- Incorrect location in render\n\n\n\n\n[Render Region + Persistent Images bug.blend](Render_Region___Persistent_Images_bug.blend)\n\n 1. Open the attached blend file and set an output directory for the render.\n 2. Press 'Run Script' in the open text editor to render out the images.\n\nImages 3, 7, 8 and 9 will probably have artifacts and for the other frames the objects will be in the incorrect location (the border should be positioned perfectly around them).\n\n**Note**: I have set the script to render 10 frames because it seems to depend on what was rendered previously as to whether the glitches/incorrect positions will appear. Rendering the glitched frames on their own does not produce the errors consistently.\n\n", "Dopesheet Display Hidden doesn't work property combined with Only Selected.\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 75)\nWorked: Version 2.79b\n\n\nIn version 2.79 with the \"Selection Only\" option active in the dope sheet screen, after animating the appearance or disappearance of the object, you had the possibility to edit the keyframes, now it is possible only if the Only Selected option is deactivated, it is rather uncomfortable compared to the previous one because that option is useful to avoid having a max dopesheet window and to avoid errors in complex animations.\n\nFrame 1:\nTurn off the object then Animate Disable in viewport,\nFrame 2:\nTurn on the object and animate Disable in viewport.\nOpen dopesheet window, Click Selection only and Display Hidden option at frame 2, go to frame 1 the frames disappear.\n\n[Dopesheet_280.blend](Dopesheet_280.blend)\n[Dopesheet_279b.blend](Dopesheet_279b.blend)\n\n\n", "\"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.", "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", "Weird artefacts from emission surface\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M (but this occurs also on CPU)\n\nBroken: 3.6.2\nWorked: don't know\n\n\nIn the attached .blend file I have set up an emission shader to emit light from one end of a long thin surface. The screenshot illustrates the problem: a bunch of weird artefacts appear.\n\nIf I change it to emit from the other end of the surface, by swapping the 'Map Range' node in the screenshot for the disconnected one, the problem goes away.\n\n\n\n\nLoad the attached .blend file and switch the view to rendered.\n\n", "Presence of node socket in the context is unstable (layout context pointer lost on OK button of invoke_props_dialog)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 3.0.0 Beta\n\nIt looks like that if operator is called from a socket interface it has the socket in given context. But if the operator calls popup panel the socket is disappearing from the context if mouse cursors reaches some invisible boundary and after that execute method can't relay on socket to be in the context. It would be nice if the socket would be more persistent in different parts of operators' lives.)) P.S. the same problem with `context.node`\n\n[2021-11-04 22-07-56.mp4](2021-11-04_22-07-56.mp4)\n\n[untitled.blend](untitled.blend)\n1. Download the file\n2. Run the script\n3. Push first button on the socket\n4. Push second button on the socket\n5. Tracking the status of the socket in the panel interface move mouse closer to the OK button and beyond the panel borders\n6. Press OK\n7. Read console\n\n\n", "3D Paint Mode stencil disappears when panning viewport.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 2.93.4\n\nWhen panning viewport in 3D paint mode with stencil mask enabled, the stencil mask disappears when moving the viewport, however does not disappear when zooming it, which indicates it's not a technical limitation.\n\n1. Enter 3D paint mode\n2. Enable texture mask, select some texture and set mapping to stencil\n3. Navigate the viewport\nResult: The stencil disappears when moving the viewport, which makes it very difficult to line up stencil projection with the 3D geometry\nExpected: The stencil does not disappear when navigating the view\n\n", "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", "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", "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)" ]

[ "Local View broken\nOperating system: Windows 10\nGraphics card: Nvidia GeForce 980ti\n\nBroken: 2.8 beta, 2018 12-05 02:05\n\nMesh disappear in local view\n\nWhen you press \"/\" hotkey to go to local view in \"edit mode\" mesh disappear after I try do any extrude, bevel or another operation.\nIf I press \"/\" again, the mesh will appear with the last operation.\n\n[Local_view_bug.blend](Local_view_bug.blend)\n[name ](f3b224aea8de002e7344143a35c372d7)", "Blender 2.80 beta UV editing mesh disappearing\nOperating system: Windows 10\nGraphics card: Geforce 970m\n\nBroken:\n2.80, 4c31bed6b46, blender2.8, 2018-11-30, as found on the splash screen)\n\n\nRandom disapearances of the main mesh when editing it's UVs, in the Uv Editing tab\n\nIn Edit mode, move the UVs, and the mesh will disapear. Random clicks in the 3D viewport will bring it back, as well as double clickling the collection visibility.", "Blender 2.8 Beta - Geometry disappearing when extrude or grab while in \"user perspective (local)\"\nOperating system: Windows 10\nGraphics card: 1060\n\nBroken: 2.8\nHash: a205493426b\nDate: 2018-12-03 00:27\n\nWhile editing a simple extruded oval, I press / to enter \"User Perspective (Local)\". When I select a vertex and hit e or g, the geometry disappears. \n\nTo recreate: open blend file. Hit / to enter local mode. Click vertex. Hit g.\n\n", "Deleting edge loops makes disappear the object from local view\nOperating system: Win 10\nGraphics card: NVIDIA Geforce GTX 750\n\nBroken: 2.8 \nWorked: 2.79\n\n\nDeleting edge loops of an object makes it disappear from the local view. Some times it works correctly after some other operations. But it happens most of the time!\n\n Add a cube/ Or the default cube > enter into the edit mode > add some loops to the cube > Go to the local view using Numpad / > select some edge loops > press X and select edge loops from the menu. ", "Object disappears in local mode\nOperating system:\nGraphics card:\n\nBroken:\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n1. I go to local mode /\n2. go into edit mode\n3. Object disappears\n\nthat always happens. no matter with which file.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Mesh disappears when trying to move vertices while in isolation mode\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1080\n\nBlender 2.8 Beta \nHash: 1fa527bfa3a\n\nBroken: Select object > press key \"/\" to isolate, go to edit mode, vertices, select vertex, press key \"G\" to move, mesh disappears, until key \"/\" is pressed again to exit isolation mode.\n", "Object disappears when using / isolator and loop cut\nOperating system: Windows 10\nGraphics card: GTX 970M\n\nBroken: blender-2.80.0-git.4c31bed6b46-windows64\n\nWorked: (optional)\n\n\nI was working on a house model and when using the / isolate button. When I did a loop cut the model I was working disappears. It is not a big problem as all I had to do to fix the issue was press / off and on. It does it specifically while moving the loop cut on the model. \n\nNot a big problem but thought I'd let you know. \nTessa{[F5786388](house.blend)}", "[Blender2.8] Certain mesh operations causes the mesh to vanish in local view\nOperating system: Gentoo Linux\nGraphics card: AMD 290x\n\nBroken:\n1f5dd9c437cce27cf5a4498b1b7d31f4b9f9b8f2\nWorked: (optional)\n\nI'm reporting this issue for an other user. He was running windows so it seems like this is not GPU or platform related.\n\nCertain mesh operations causes the mesh to vanish from view until you exit local view\n\n[local_view.blend](local_view.blend)\n1. Open the attached .blend file\n2. Go into local view with the cube\n3. Press \"F\" to fill in the missing face on the cube\n4. The cube is now gone.", "Local view Bug\nOperating system: Linux Deepin 15.8\nGraphics card: NVIDIA Duke 1080ti\n\n```\n blender-2.80-7ec5a68091a-linux-glibc224-x86_64\n```\n\n\n\nOpen New file.\nSelect The Box.\nChange to Edit mode.\n\"/\" for local view.\nChange to Object mode\nBug \nThe box disappear and when click the Box appear\n" ]

[ "Multi-Object-Mode: EditMesh Tools\nNote, while these follow menus, duplicates have been removed.\n\n## Remaining\n\n- MESH_OT_select_similar_region ([D3672](D3672))\n- MESH_OT_knife_project (leave aside for now, too complex - see [D3637](D3637))\n- MESH_OT_knife_tool (leave aside for now, too complex - see [D3637](D3637))\n\n\n## Mesh Menu:\n\n- ~~MESH_OT_duplicate_move~~ 1ade071052\n- ~~MESH_OT_extrude_edges_indiv~~ d8f70a26fd\n- ~~MESH_OT_extrude_faces_indiv~~ 07774d4860\n- ~~MESH_OT_extrude_verts_indiv~~ 7c415e6fd7\n- ~~MESH_OT_extrude_edges_move~~ 1d7bdbd273\n- ~~MESH_OT_extrude_vertices_move~~ 1d7bdbd273\n- ~~MESH_OT_delete_loose~~ bfc9d426bb\n- ~~MESH_OT_decimate~~ 5b45d32f3a\n- ~~MESH_OT_dissolve_degenerate~~ (initial comsmit) bfc9d426bb\n- ~~MESH_OT_dissolve_limited~~ 09e14cb5bc\n- ~~MESH_OT_face_make_planar~~ 0e5a4f927a\n- ~~MESH_OT_vert_connect_nonplanar~~ b942106c73\n- ~~MESH_OT_vert_connect_concave~~4043e4b820\n- ~~MESH_OT_fill_holes~~ 69b95b45f4\n- ~~MESH_OT_symmetrize~~ 03a916e5b5\n- ~~MESH_OT_symmetry_snap~~ 7f9768cb80\n- ~~MESH_OT_bisect~~ f9eb2f29fe\n- ~~MESH_OT_sort_elements~~ ffb424c85f\n\n## Snap Menu:\n\n\n- ~~VIEW3D_OT_snap_selected_to_grid~~ 016ba0f38b\n- ~~VIEW3D_OT_snap_selected_to_cursor~~ ec3357e03a\n- ~~VIEW3D_OT_snap_selected_to_active~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_selected~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_center~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_grid~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_active~~ (no change required)\n\n\n## Vertex Menu:\n\n- ~~MESH_OT_merge~~ b73c7381cc\n- ~~MESH_OT_remove_doubles~~ 22b2bab702\n- ~~MESH_OT_rip~~ 9d0d7c375e\n- ~~MESH_OT_rip_edge~~ 6539c1fc41\n- ~~MESH_OT_split~~ fc8d903000\n- ~~MESH_OT_separate~~ 5e915baec4\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_vertices_smooth~~ d915aa57f8\n- ~~MESH_OT_vertices_smooth_laplacian~~ 1f30232aa7\n- ~~MESH_OT_blend_from_shape~~ 6ae09dfcad\n- ~~OBJECT_OT_vertex_group_smooth~~ 3dee8b4a12\n- ~~MESH_OT_shape_propagate_to_all~~ 3a43528274\n\n## Edge Menu:\n\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_subdivide~~ (initial patch)\n- ~~MESH_OT_subdivide_edgering~~ 853e55b043\n- ~~MESH_OT_unsubdivide~~ e245f7c09c\n- ~~TRANSFORM_OT_edge_crease~~ (initial patch)\n- ~~MESH_OT_mark_seam~~ 61f0608b4a\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_edge_rotate~~ 66ffbf9b7d\n- ~~MESH_OT_edge_split~~ 207b549d40\n- ~~MESH_OT_bridge_edge_loops~~ eb2226dde2\n- ~~TRANSFORM_OT_edge_slide~~ (wrapper to other operator, working)\n- ~~MESH_OT_loop_multi_select~~ df49155cfb\n- ~~MESH_OT_loop_to_region~~ 8b41999ea0\n- ~~MESH_OT_region_to_loop~~ 56d65719b3\n\n\n## Face Menu:\n\n- ~~MESH_OT_flip_normals~~ 4704f2687a\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_fill~~ b726ff4fc4\n- ~~MESH_OT_beautify_fill~~ e42b8c32ab\n- ~~MESH_OT_inset~~ 570455fb83\n- ~~MESH_OT_bevel~~ d9e04cb594\n- ~~MESH_OT_solidify~~ f309c34cfe\n- ~~MESH_OT_intersect~~ dffd37877d\n- ~~MESH_OT_intersect_boolean~~ 46aec45b2a\n- ~~MESH_OT_wireframe~~ a0a78f6da4\n- ~~MESH_OT_poke~~ 3a9669bfff\n- ~~MESH_OT_quads_convert_to_tris~~ (initial patch bfc9d426bb\n- ~~MESH_OT_tris_convert_to_quads~~ (initial patch bfc9d426bb\n- ~~MESH_OT_face_split_by_edges~~ b6a822d726\n- ~~MESH_OT_faces_shade_smooth~~ e4c4e8566f\n- ~~MESH_OT_faces_shade_flat~~ 9fc0c0c3de\n- ~~MESH_OT_uvs_reverse~~ 63951bc987\n- ~~MESH_OT_uvs_rotate~~ faaffc4011\n- ~~MESH_OT_colors_rotate~~ 42c5c20e54\n- ~~MESH_OT_colors_reverse~~ 753be0a2a5\n\n## Mesh Toolbar: (should be added to menu)\n\n- ~~MESH_OT_loopcut~~ e87dd9aa00\n- ~~MESH_OT_convex_hull~~ e1cee0ac71\n- ~~MESH_OT_delete~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_delete_edgeloop~~ 49be803ad6\n- ~~MESH_OT_dissolve_edges~~ 7f5c469716\n- ~~MESH_OT_dissolve_faces~~ 848d9cda0e\n- ~~MESH_OT_dissolve_mode~~ (wrapper of vert/edge/face dissolve)\n- ~~MESH_OT_dissolve_verts~~ 5f59a8bb11\n- ~~MESH_OT_drop_named_image~~ b4d23818c8\n- ~~MESH_OT_dupli_extrude_cursor~~ 68a719f1ea\n- ~~MESH_OT_duplicate~~ 1ade071052\n- ~~MESH_OT_edge_collapse~~ 2349b9777a\n- ~~MESH_OT_edgering_select~~ 7fa77cd31d\n- ~~MESH_OT_edges_select_sharp~~ dd93c80747\n- ~~MESH_OT_extrude_region~~ 1d7bdbd273\n- ~~MESH_OT_extrude_repeat~~ 9a125ca5fe\n- ~~MESH_OT_faces_select_linked_flat~~ 1bb9ccf887\n- ~~MESH_OT_fill_grid~~ 1cbe3b6e03\n- ~~MESH_OT_hide~~ 5d8937e8ba\n- ~~MESH_OT_loop_select~~ 7fa77cd31d\n- ~~MESH_OT_normals_make_consistent~~ 266638d783\n- ~~MESH_OT_offset_edge_loops~~ efd843b51c\n- ~~MESH_OT_reveal~~ f4c1685a16\n- ~~MESH_OT_screw~~ badd88ca02\n- ~~MESH_OT_select_all~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_axis~~ c899f21800\n- ~~MESH_OT_select_face_by_sides~~ 90c9458b2f\n- ~~MESH_OT_select_interior_faces~~ e161c51e7f\n- ~~MESH_OT_select_less~~ b6a7fa1880\n- ~~MESH_OT_select_linked~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_linked_pick~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_loose~~ eacb2eb423\n- ~~MESH_OT_select_mirror~~ 3ebe389605\n- ~~MESH_OT_select_mode~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_more~~ 2309131b4d\n- ~~MESH_OT_select_non_manifold~~ 4da2aec2bb\n- ~~MESH_OT_select_nth~~ 63c2397171\n- ~~MESH_OT_select_random~~ 847f028b71\n- ~~MESH_OT_select_similar~~ 75b2091d42\n- ~~MESH_OT_select_ungrouped~~ 1d8e6c5cd0\n- ~~MESH_OT_shortest_path_pick~~ c32cc3e43e\n- ~~MESH_OT_shortest_path_select~~ 5a431be629\n- ~~MESH_OT_spin~~ ab8dded330\n- ~~MESH_OT_vert_connect~~ 944054fbb6\n- ~~MESH_OT_vert_connect_path~~ fc7316fb54\n", "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", "\"Add [Object]\" menu not working correctly or lagging\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nI found out that the context menu that appears just after adding an object tends to lag or bug if you have split screen the viewport and the compositor with the checkbox \"use nodes\".\n\n1. Make a vertical split and and add the Compositor panel.\n2. Check \"use nodes\" in the compositor panel.\n3. Add any 3D Primitive object in the viewport, )E.G. Icosphere).\n4. Try changing the subdivisions in the \"add icosphere menu\" or just try to drag the logation paramenters whithin that menu.\n5. The result will be a choppy or lagging response, not expected.\n6. I've tracked this error even from the 3.4 version of blender, until now.\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", "Rendered object in displayed as a transparent png\nOperating system: Windows-10-10.0.19043\nGraphics card: Radeon AMD Radeon HD 8500M (4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001)\n\nWorked: (3.2.0)\n\nidk if it is even a bug but when i render my object, it shows the object as a transparent png. how do i fix it?\n\n[donut.blend](donut.blend)", "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.", "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)", "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", "Make Links > Objects to Scene: Does not changes origing point color. We have no visual indication!\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.2\n\n\n\n\nIn 2.79 it was visually distinguishable per scene linked objects by a bluish tinted origin point but this behavior is missing since 2.8 series has started (for no apparent reason).\n\nThis visual feedback is very important. It basically tells you:\nHey! If you touch me, you change me in all scenes I'm living at! Be aware!\n\nAnd the fact now I have remember what can I touch and what I can't, since my project is increasing in complexity, is overwhelming.\nYou might say: use library overrides then! But no, these are different features and both accomplish different purposes and they can keep coexisting. (unless we could now make a library override for a datablock in the same file, but that is not the case).\n\nAlso, the 2.93 manual states the expected behavior:\n\nBut this is not the case anymore for a while!\nI have been silently waiting for this to be fixed but its time to ask our dear developers to take a look onto this. Please, bring it back!\nOr maybe even enabling the ability to define a different outline color too. (honestly a tinted dot for me is enough)\n\nBest regards,\nJulio.\n\n", "Eevee RGB Curves node inaccurate compared to Cycles\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 3.0.0 Alpha\n\n[eevee_rgb_curve.mp4](eevee_rgb_curve.mp4)\nThe transformation that the RGB curves node applies to a color differs slightly between Eevee and Cycles, even if the curve is left as default.\nNot sure if this is a bug or just a known limitation, but it breaks compatibility between Eevee and Cycles in edge cases.\n\n[eevee_rgb_curve.blend](eevee_rgb_curve.blend)\n\n", "Broken material assigment after changing mesh-linking to object-linking\nWindows 11\nNvidia RTX 2060 super\n\nBroken: blender-3.2.0-stable+daily.e05e1e369187\n\n\nOn objects with multiple material slots, the currently selected slot gets bugged when switching from object-linking to mesh-linking. It allows the user to select a different material for each link type, which seems to trigger the bug and has lingering effects. For example, in geometry-nodes setting the material becomes unpredicatable, with material names seemingly swapped.\n\nFrom the provided blend file or startup scene:\n1. create a new material slot\n2. pick a material for this slot\n3. swap the material link type between object-link and mesh-link\n4. select a different material for the same slot\nThe material or slot is now bugged. Geo nodes 'set material' will become unpredictable.\n\n[bug_slots.blend](bug_slots.blend)", "Behavior for mathutils.Vector.rotation_difference when vectors are aligned\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001\n\nBroken: version: 2.93.0 Alpha\nWorked: Never? (tested on 2.79)\n\n```\nimport bpy\nfrom mathutils import Vector\n\nvector_a = Vector((0.0,-1.0,0.0))\nvector_b = Vector((0.0, 1.01,0.0))\nquat = vector_a.rotation_difference(vector_b)\n\nobj = bpy.context.object\nobj.rotation_quaternion = quat\n```\nIn the `rotation_difference` method shown in the script above, when the angle between two vectors is 180° or close, the resulting Quaternion, although pointing in the correct direction, also rotates on another axis.\n\n- Open attached file\n- Run script\nNote that the object did not rotate exactly 180° on one axis\n[rotation_difference_bug.blend](rotation_difference_bug.blend)\n\n", "Can't Animate Texture Mapping Offset For Particle Hair\nWindow 7 64bit 8gb\nnvidia 660\n\nBroken: 2.72 RC\nWorked: I thought this was possible all the way back into the 2.4 series.\n\nAdd a single keyframe to particle texture mapping coordinates.\nMove to another frame and type a new number in the *Offset* mapping field and it will jump back to the number of the first keyframe.\nIn this state there is no way to animate the*Offset*. Even if I insert the same value at the new time location and edit the value in the graph editor the system still refuses to use the *Offset*information for the particle system hair density.\n\nOpen the Attached BLEND file and type a new number in the *X Offset* field.\nThe system refuses to accept the input and resets to the keyframe value.\n\nNOTE: This seems to only be a problem in the *Offset* and *Size* properties for Mapping. You will also see in the BLEND file that I have successfully keyframed the R value of the RGB without experiencing the same problem.\n\n[27_sequin_star_curtain_1a.blend](27_sequin_star_curtain_1a.blend)\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", "Toggling Autosmooth changes evaluated bbox `obj.bound_box` when SUBSURF mod (using GPU subd) is present\nOperating system: Linux-6.2.0-76060200-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\n\nBroken: version: 3.5.0\nWorked: -\n\nOn a mesh object with a SUBSURF mod active (using GPU Subdivision), the (evaluated) bounding box at `obj.bound_box` will only produce the correct coordinates when `obj.data.use_auto_smooth` is enabled. Otherwise it will be produce the coordinates of the original mesh bounding box, even though the evaluated mesh is clearly smaller, and so the bbox should be too.\n\nThat makes relying on `obj.bound_box` impossible, when working with the bounding box and assuming it represents the evaluated mesh object.\n\nInterestingly, boolean mods don't share this behavior, the bbox created using booleans, works properly with either auto smooth setting.\n\nSee watch?v=KKnWbRL5h7o for demonstration\n\n\n* open the attached blend file\n* toggle Autosmooth and see the bound box change, even though the evaluated mesh displayed does not change at all.\n\n" ]

[ "Some kind of glitch\nOperating system: Windows 10\nGraphics card: nvidia\n\nBroken: Version 2.80 Beta\nWorked: Yes, besides this, it works pretty well, other than the occasional crash.\n\nI built a house in the picture, but when I switch from EEVEE to Cycles it's as if the house moved, when it didn't.\nYou can see here that the smaller section of the house seems to have shifted upwards somehow. Up and to the right side of the screen, intersecting with the other section. It tidn't happen with the other one, which isn't unwrapped properly.\n\nBased on the default startup or an attached .blend file. I shaped a few default cubes, including adding booleans where the windows are. Then I unwrapped them and added the brick image textures. After creating roogs, and tweaking with the shaders a bit, I started sculpting the sides of the house to add more realism. Then I unwrapped the smaller section of the house again, because I had added new geometry when I sculpted with dyntopo. so the brick textures were no longer there. I unrapped using the cube projection. Then I switched to rendered view, and changed to cycles to get a more realistic preview. And that's when the [picture happened. When I switch back to EEVEE, the house is where it belongs, and when I'm in solid view in Cycles, it's fine too. Only when I'm in Cycles AND rendered view, does this problem happen.\n\nI'm sure others have reported this bug and you may already be trying to fix it. I also understand that you have a lot of work to do and a lot of other bug reports incoming all the time, since 2.8 is still in Beta, so I don't expect a responce. I'm just doing my duty to the blender community, and I'm excited to see when 2.8 will be ready for official release." ]

[ "EEVEE: Nishita Sky change Sun Rotation causes shader recompilation\nBroken: version: 3.4.0 Alpha\n\nAdjusting Sun Rotation in Nishita Sky texture in EEVEE causes shader recompilation\nwhile adjusting sun elevation is not causing shader compilation and allow to realtime adjustments\n\nThis makes impossible to have animated sun position.\n**Steps to Reproduce**\n- Open .blend file -> switch to viewport rendering\n- Change rotation value with slider\n[#101197.blend](T101197.blend)\n[nitsha.mp4](nitsha.mp4)", "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.", "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", "EEVEE: Spotlight Parented To Scaled Object Behaves Incorrectly\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: Blender 2.82a, 2.90 alpha eaf7d36d66e5\n\nIn EEVEE, Spotlights parented to a scaled object cast an incorrect shape once they are rotated.\nThe viewport overlay, however, indicates the correct shape.\n(Note: This does not apply to Cycles, see #76823)\n\n[spotlight_ellipse_parented.blend](spotlight_ellipse_parented.blend)\n\nSet view to rendered.\n\nThe scene has a Spotlight (unscaled, not rotated) parented to an Empty (scaled).\nThis results in an elliptical spot.\n\nHowever, if the Spotlight is rotated around its Z-Axis, the spot's shape should stay identical. (As indicated by the overlay.)\nBut it does not.", "Video Editor Scene Strips and scene camera binds are out of sync (most of the time)\nBroken: blender-2.80.0-git.03bd024c077d-windows64\n\nThis is a re-do of another other bug report I filed earlier this month (#63304), now that I understand it a lot better I'm filing it again with a more accurate description and demo file.\n\nIn the video editor, if you one or many scene strips, on updating the frame the camera bind that the playhead falls under will most likely not be applied until the following frame.\nSo, when you place the playhead in a region that uses a different camera bind, it usually does not update unless you update once more in that same region.\nThis is also the case in rendering animations using the video editor.\n\nI've created a demo file that perfectly illustrates this problem below.\nThis bug urgently needs fixing.\n\n**Exact steps for others to reproduce the error**[sequence camera bind bug.blend](sequence_camera_bind_bug.blend)\nInstructions for demo:\n\nIf the playhead is in the BOX region, it should show a box, if it is in the SPHERE region, it should show a sphere. I estimate about 80-90% of the time it doesn't update correctly. Why there is an element of chance I cannot work out.\n\nTry moving the playhead around between markers (which indicate a camera bind in the strip's scene) and notice how the bind almost always fails to apply.\n\nNow try jumping from region to region and notice how the camera bind is almost always 1 step behind, so it is never applied, place the playhead within the current region and it updates without fail.", "Stereoscopic - right side has incorrect render (Eevee)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.93.4\nWorked: unknown\n\nStereoscopic creates an incorrect image for the rendered Right side (Eevee).\nThe right side seems to be a mix of the correct render and a render with low samples (1?). This is clear on the soft shadows and AO.\n \nIt can only be resolved by enabling Screen Space Reflections, which isn't always desirable obviously. \n\nOpen attached blend file and render. \nCompare left and right render.\n\n[stereoscopic_rightSide_difference.blend](stereoscopic_rightSide_difference.blend)\n", "Persistent Data causes the Image Editor to not update during rendering + pixel glitches in topper pixel lines\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.1.0 Beta\n\nVery often, when you render a sequence, it was on nearly every scene I was working on, there is not shown the render results, and you see the transparent background.\nUpdate in the image Editor is only shown once the whole render completes.\nSometimes it works randomly on some frames. And sometimes you have even a pixel glitch when the progress is not shown. As shown at the end of the video, you have sometimes that glitch on the top. When it is there, it is always the first\\second pixel line.\nThe Pictures are properly rendered and saved, but often the progress in the render results window is not shown and there are some glitches. But they will not appear in the final picture. ONLY in the render preview.\n\nWorks on my projects every time. Nothing particularly.\n\nWait a little bit. The second frame in the video has a glitch.\n[2022-02-01 19-39-28.mp4](2022-02-01_19-39-28.mp4)\n\nProblem is from on frame 3:\n[2022-02-04 08-09-30.mp4](2022-02-04_08-09-30.mp4)\n[Citty.blend](Citty.blend)", "Bump node results are affected by camera angle in Cycles\nOperating system: Linux-5.6.10-3-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GT 525M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.132\n\nBroken: version: 2.83 (sub 17)\nWorked: Never (2.80+)\n\nBump node result is affected by camera angle in Cycles, seems to work well in Eevee\n\nOpen Blender\nGo to Shader Editor\nCreate a Bump Node and connect its normal output to the normal input of Principled Shader(or any shader)\n[BumpBug.blend](BumpBug.blend)\n\n", "Sculpting laggy and weak from some directions.\nOperating system: Windows 10\nGraphics card: Nvidia GTX 970\n\nBroken: 3.6.1\nWorked:Never(2.80+)\n\nWhen i try to sculpt from from below, using radius unit: scene, sculptings get laggy and the stroke is weak.\n\nI'm trying to sculpt stones for a wall in place.\nThe sculpting works fine if i first move the stone i'm working on to the scene origin. This adds a lot of work as i want to for example put bevels on all objects first, then go on with cracks and other features!\n\nTo reproduce:\nOpen file, sculpt from top and bottom\n\nFile is default sculpt template with sphere moved up by 5 and using scene radius.\n\n", "Same pattern looks different for Cycles and Eevee\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.1\n\nThis is the difference\n\n\n\n\nsimplified file\n[pixels tiled1.blend](pixels_tiled1.blend)\n\n\nold file \n[pixels tiled.blend](pixels_tiled.blend)\n\nI suppose the difference in Color Ramp or Noise node.\n", "Alpha mode 'Straight' on Image Texture node behaves differently between Cycles and Eevee\nOperating system: Windows 10 Pro x64\nGraphics card: GTX 1080Ti for display, RTX 3090 for render\n\nBroken: 3.3.1\nWorked: I don't know\n\nWhen the `Alpha` property is set to `Straight`, the result is different between Eevee and Cycles.\n\n\n- Open the .blend file provided\n- Set one of the viewports to Material Preview and the other to Rendered\nNote that the results of the images are different\n[alpha_mode_eevee_vs_cycles.blend](alpha_mode_eevee_vs_cycles.blend)\n\nOriginal file\n[test leaking_ori.blend](test_leaking_ori.blend)\n", "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.", "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.", "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", "Different padding between eevee and cycle properties\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.0.0 Beta\nWorked: ???\n\ndifferent padding see image below:\n\n\n\ni dont know is this because new ui design or not.\n\n\n" ]

[ "bug in Cycles: rendering the scene, an object is not corresponding with the real mesh position\nOperating system: Windows 8.1\nGraphics card: 2x GTX770 (i7 with 32 GB RAM)\n\nBroken: 2.8\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nbug in Cycles: rendering the scene, an object is not corresponding with the real mesh position\n\nBased on the default startup or an attached .blend file (as simple as possible).\n[bug.mp4](bug.mp4)" ]

[ "Not possible to add keyframes to HSV values.\nOperating system: Linux-5.15.76-1-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: Mesa Intel(R) Graphics (ADL GT2) Intel 4.6 (Core Profile) Mesa 22.2.1 & NVIDIA GeForce RTX 3050Ti Laptop GPU 520.56.06\n\nBroken: version: 3.3.1\n\nIt is not possible to add keyframes to the HSV values of any color picker.\n\nOpen a new file. Go to the material tab of the default cube. Right-click in any of the HSV values of the Base Color picker tool.\n\n", "Material preview does not refresh when switching Workspaces\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.17\n\nBroken: version: 2.80 (sub 57)\nAs well as older 2.80, 2.79b etc. This is not a recently introduced issue.\n\nWhen you switch to a new Workspace that has the Material Preview visible, it will not refresh if the material has been changed while away from that Workspace.\n\nOpen default scene. In Properties, switch to Material tab and expand the Preview section.\nSwitch to Shading Workspace and do the same thing.\nChange the Base Color of the object.\nSwitch back to the Layout Workspace and note the preview does not update.\n\nAFAIK, it has always been like this but before Workspaces it wasn't as noticeable.\n\nIn other cases the preview refresh is extremely aggressive, for example it fires even if you just click on a node in the Shader Editor, start to drag a node, etc. Might improve general system performance if it only got triggered when something actually changes, but a simple solution to the not-refreshing problem would be to just always trigger the refresh when you switch to a workspace where at least one preview is visible.", "4090 has problem with texture in render preview\nOperating system: Windows 11\nGraphics card: Nvidia Geforce 4090\n\nBroken: (3.4 and 3.5.1)\nWorked: none.\n\n**Short description of error** \nThis only started recently, has been fine up till today. My preferences are set to use both the CPU (AMD Threadripper 32) and the GPU (geforce 4090) in OptiX (or CUDA, doesnt seem to matter). Once the file opens, material preview works fine. (refer to \"materialpreview.png\") but when i click render preview (refer to renderprevier.png) all i see is my rig. Anything with a texture is a similar dark grey as the default blender background. I can move the camera around fine, but no textures are visible. If i click material preview again to switch back, blender freezes and must \"end task\" in task manager. If i turn off the GPU assistance and only have the CPU enabled, everything works as it should. \n\nYesterday i updated to latest windows 11 update. I also updated my gameready drivers for my 4090. When the issue started, i thought it might have something to do with gameready drivers so switched to Studio drivers. This did not fix it. \nAssuming that these updates may have broken my file, i rolled back windows 11 drivers to most recent previous version, and did the same with the nvidia studio drivers (uninstalled 5.35.... installed 5.31). This fixed nothing.\n\nI would love to know why my GPU can't be used with Blender suddenly. Games work fine. Furmark 3d app works fine, no issues. Heat is fine. Very frustrating to have such expensive gear suddenly stop working.\n\n", "Grease Pencil datablock property 'use_onion_skinning' doesn't work\nOperating system:\nGraphics card:\n\nBroken: 3.4\nWorked: \n\nThe datablock-level property \"use_onion_skinning\" on the Grease Pencil datablock doesn't seem to do anything. Toggling the property with Python doesn't affect the visibility of onion skinning.\nWorking as expected, this property will be useful when drawing among multiple Grease Pencil objects.\n\nOpen attached blend, toggle use_onion_skinning in the Python console: bpy.context.object.data.use_onion_skinning = False [onion_bug.blend](onion_bug.blend) ", "Custom Properties Improved UI\nCurrent UI:\n\n\n\n- [ ] Allow reordering of custom properties in ways that make the most sense to an artist\n- [ ] Allow editing from the sidebar\n- [ ] Decrease the space between properties\n- [ ] Using an 'X' icon to delete\n- [ ] User and edit icon instead of \"Edit\"\n- [ ] Better location of icons\n- [ ] Group properties by the selected object/bone (see image)\n- [ ] Add a drop-down to select the data type\n- [ ] Allow the use of checkboxes to represent booleans\n\n", "Assign Shortcuts: creates shortcut in the \"wrong\" space\n**OS**: Linux 5.3.8-arch1-1 x86_64\n\n**Blender version**\nBroken: 2.8x (up to and including fc79d27951)\n\nWhen using the context menu to assign shortcut to a button or checkbox, the shortcut is created in a wrong space, which may lead to error popups when pressing that shortcut with mouse hovering over a different space.\n\n\n1. Load the default scene.\n2. In 3D viewport, expand the Overlays popover, right-click the Wireframes checkbox and assign a shortcut through the context menu.\n3. Note that shortcut works while the mouse is over the 3D viewport.\n4. Move the mouse over the Properties and try pressing the shortcut. You'll get an error popup.\n\nThis is due to the shortcut being created in the Window space, not 3D View space.", "Material slots undo is inconsistent in non-Object modes\nBroken: 3.0\nMaterial slots undo is inconsistent. Sometimes multiple slots are added/removed in one undo, and sometimes undo won't change back mode.\n\n\ntab to edit mode \nadd a material slot\nundo twice\nadd another material slot\nundo\nboth material slots will be undone. Also undo won't go back into edit mode.\nif you redo both material slots are redone at the same time.\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", "Menu Editor for Quick Favorites\nCurrently users can only manage menu items in the quick-favorites menu by adding/removing items.\n\nThis task proposes to: \n\n- Create a generic menu editor in the user preferences.\n\n - Add/remove menu items\n - Re-ordering menu items.\n - Operators options should be able to be changed or unset - as we have with the keymap editor.\n\n**Implementation**\n\n- This could share UI code with the keymap editor for adjusting operator settings, since internally they are very similar.\n- We may support multiple kinds of menus, besides \"Quick Favorites\", internally there is support for this. Even if this isn't exposed to users initially.\n\n```\nThis would be useful for declaring user defined toolbars for example.\n```\n\n**User Interface**\nHere's how the UI could be organized: \n\n{[F8282863](Screenshot_2020-01-17_at_11.08.58.png), size=full}", "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", "Remap user material selection uses enum menu instead of searchable list \nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\nAlso tried on 2.82 daily build 12/19\nWorked: (optional)\n\nI'm trying to remap some of my materials, but the menu that opens to allow me to choose the replacement material doesn't allow me to see all the materials available--there is no way to scroll down to see more of the list. I tried on the daily build for 12/19, and unlike the stable version, there are arrows, but they also don't open the full menu. \n\nGo to outliner>blender file>materials, right click on a material, choose remap, Outliner ID data remap opens, click on New ID to open that menu, and that's where I can't see all of the choices. I'm attaching a screenshot, because it only happens with a larger file with many materials. In the screenshot, the last material I can access is labelled M_Photo, and can't scroll to any beyond that. \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)", "\"Material preview\" shows always eevee mat branch / never cycles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.82 (sub 6)\nWorked: never, I think\n\n\"Material Preview\" shows always the material output assigned to eevee, but I want the cycles branch. Changing renderengine or the active material output node doesn't change anything.\n\nOpen the blendfile and try to preview the material with \"cycles\" image - without going to rendered viewport. The material preview seems to always use the node tree going to the Eevee material output node, even when the render enging is set to Cycles.\n[specific_material_output.blend](specific_material_output.blend)\n\n\n", "Undo doesn't work with paint mask selection (texture paint vs. vertex/weightpaint)\nOperating system: Linux-5.2.10-arch1-1-ARCH-x86_64-with-arch 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.32.0, 5.2.10-arch1-1-ARCH, LLVM 8.0.1) X.Org 4.5 (Core Profile) Mesa 19.1.5\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nUndo does not work with paint mask selections. The expected behavior here is that undo should work as in other selection modes.\n\nClick on texture paint.\nSelect single image and create a texture.\nTurn on paint masking, and then select the \"select box\" tool.\nclick on a face on the cube to select it.\nPress ctrl-z.", "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 (...)\"*" ]

[ "\"Select by active material slot\" can not be mapped to a shortcut\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.11\n\nBroken: version: 2.93.3\n\n\"select by active material slot\" can not be mapped to a shortcut\n\nbased on default startup:\n1. select \"Edit Mode\"\n2. select \"Material Properties\"\n3. Right click \"Select\" in the Material\n4. select \"Assign Shortcut\"\n\nExpected: \n- when I press a button combination that is not yet used, this combination is saved and can be used to toggle the \"Select\" functionality\n\nWhat happens:\n- the saved button combination is not saved as a shortcut for the \"Select\" functionality \n\n\n\n", "\"Assign Material Slot\"-Shortcut is created in the wrong place\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n\"Assign Material Slot\"-Shortcut is created in the wrong place, therefore does not work.\n\n\n[Material Shortcuts.blend](Material_Shortcuts.blend)\n\nBy rightclicking, the shortcut is created in the Input Preferences under `3D-View > Object Mode > Object Mode (Global)` which is wrong. It simply does nothing in Object mode. In order to work it has to be manually created under `3D-View > Mesh > Mesh (Global)` with the same entry name.\n\n\n\n" ]

[ "Mantaflow - force fields have very low influence compare to 2.90.1\nOperating system: Linux-5.4.0-52-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.80.02\n\nBroken: version: 2.92.0 Alpha\n```\n version: 2.91.0 Beta\n```\nWorked: 2.90.1\n\nForce fields appear to be approximately 50X less powerful in master and 2.91.0\n\nTo reproduce the error: go to frame 1, change the resolution to 34 for updating the parameters, and play/cache the simulation in both 2.90.1 and 2.91.0 or master.\n\n\n[Liquid_forcefield_test.blend](Liquid_forcefield_test.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", "new boolean difference meshing issue with surfaces\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 775M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: New Boolean code - version: 2.91.0\nWorked: Old Boolean code works\n\nnew boolean code does seem to have mesh intersection issues\nwhen dealing with a solid it works better\n\nintersect to surfaces \nadd a boolean difference modifier\n\nto make it work add a solidify modifier before the boolean modifier\n\n[Boolean Issue.blend.zip](Boolean_Issue.blend.zip)\n\n\n\n\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 Lighting - World light not influencing GP object correctly\nOperating system: Manjaro Linux (Kernel 5.4.18-1-MANJARO)\nGraphics card: Intel Haswell-ULT\n\nBroken: 2.83 (sub 2), c650ea9a13f9, greasepencil-refactor, 2020-02-11, 18:37\nWorked: unknown\n\nGrease Pencil Object (Strokes) unaffected by Background Light \n\nOpen either the General or the 2D Animation default file. Add a grease pencil monkey and a basic mesh, set some background color and change the strength settings once to 0 and once to 1.\nThe shading of the Suzanne object stays the same. When adding a spotlight and aiming it towards Suzanne it gets lit properly.\nThe [demo video ](GP_lighting.mp4) of the grease pencil lighting shows correct black objects where no scene light is hitting them.\n\n", "Very slow interaction with Armature, if GPU Subdiv is enabled\nOperating system: Ubuntu 20.04\nGraphics card: Gefore MX230\n\nBroken: 3.3, 3.2.2\n\nwith the enabled GPU Subdivision, interactions with the armature are much slower than with the disabled\n\n[2022-10-23 13-29-00.mp4](2022-10-23_13-29-00.mp4)\n\nmove the bones with GPU Subdivision on and off\n[kira_lite.blend](kira_lite.blend)", "Curve Pen Error\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 4.0.0 Alpha\n\nNothing happened when I left click my mouse using Curve Pen in Edit Mode, but it is fine with blender on my windows laptop.\n\nI added a Bezier and I enter the edit mode, I deleted all the vertices and decided to draw a line using Curve Pen. However, it did not work.\n\n", "Particles : Obstacles for particles no longer work from 50m from the origin of the world.\nOperating system: windoows 10 \nGraphics card: nvidia gtx 1070\n\nBroken: Blender 2.92 last release\nWorked: Don't know\n\nObstacles for particles no longer work from 50m from the origin of the world. The permeability of the obstacle does not work at all beyond 100 m. This is a big problem for landscapes. (see blend and play)\n\n- Open attached file\n- run simulation\n[particles_obstacle2.blend](particles_obstacle2.blend)\n\n---\nOther file to check: [particle_obstacle.blend](particle_obstacle.blend)", "Grease Pencil Sculpt/Vertex Paint Tool is exponentially slower when using tablet instead of mouse\nOperating system: Win10\nGraphics card: RTX 3070 FE\nTablet: Xp-Pen Deco 03 (Wireless)\n\nBroken: 3.1\nWorked: N/A\n\nWith high-geometry Grease Pencil strokes, the Sculpt Tool (and the Vertex Paint Tool) is exponentially slower when using tablet. \n\nVideo explanation:\nDavVZXsxBmI\n\nBlend File:\n[SculptToolExponentiallySlowerWithTabletThanMouse.blend](SculptToolExponentiallySlowerWithTabletThanMouse.blend)\n\n", "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)", "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.", "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", "closest_point_on_mesh() freezes Blender when called from a driver\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 580/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: 2.79\n\nCalling closest_point_on_mesh() from within a driver causes Blender to freeze.\n\n[test2.blend](test2.blend)\nOpen the file allowing scripts -> Freeze", "Outliner: Alt+disable is work for all selected, but Alt+Enable is not\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\n{key Alt LMB} generally enables a feature that repeats the operation on all selected items in the outliner.\nBut that seems to work only if the object is selected in 3d View.\n[2020-01-12_20-44-23.mp4](2020-01-12_20-44-23.mp4)\n\nOpen:\n[untitled4.blend](untitled4.blend)\n- select the three objects (either in 3d view or outliner).\n- {key Alt LMB} click on the icon that disables object in viewports.\n- {key Alt LMB} again to try to enable them all.\nOnly one object is enabled, because the others are not selected in 3dview.\n\n", "tablet mouse mousemove events are firing when should not\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\n\nBroken: version: 3.0.0 Alpha\nWorked: not tested\n\ntablet mouse mousemove events are firing when should not\n\ntablet mouse mousemove events are firing when should not, i.e. when pen is pressed down, not moving, at full force to max out pressure and holding with both hands to prevent tilting (and verifying by numbers that it is). to repeat have a wacom, run code, watch terminal, press pen on tablet and prevent it moving. with regular mouse mouse move events are not firing when mouse is not moved so i think tablet pen when is not moved, its pressure or tilt is not changed should behave the same..\n\n```\nimport bpy\nfrom mathutils import Vector\n\n\nclass ModalOperator(bpy.types.Operator):\n bl_idname = \"object.modal_operator\"\n bl_label = \"Simple Modal Operator\"\n \n def modal(self, context, event):\n if(event.type == 'MOUSEMOVE'):\n if(event.is_tablet):\n print(event.type, event.mouse_x, event.mouse_y, event.pressure, event.tilt.x, event.tilt.y, )\n if(self.mouse_x == event.mouse_x and self.mouse_y == event.mouse_y and event.tilt == self.tilt and event.pressure == self.pressure):\n #\n - should not fire mouse move event while everything is the same? like with regular mouse..\n #\n print(\"!\" * 100)\n else:\n print(\".\")\n \n self.tilt = event.tilt\n self.pressure = event.pressure\n self.mouse_x = event.mouse_x\n self.mouse_y = event.mouse_y\n \n elif(event.type in {'ESC', }):\n return {'CANCELLED'}\n \n return {'RUNNING_MODAL'}\n \n def invoke(self, context, event):\n self.mouse_x = 0.0\n self.mouse_y = 0.0\n self.pressure = 1.0\n self.tilt = Vector()\n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n\n\ndef register():\n bpy.utils.register_class(ModalOperator)\n\n\ndef unregister():\n bpy.utils.unregister_class(ModalOperator)\n\n\nif __name__ == \"__main__\":\n register()\n \n # test call\n bpy.ops.object.modal_operator('INVOKE_DEFAULT')\n\n```\n" ]

[ "Cintiq 22HD pressure don`t works but with Bamboo works (with Video-Bug Report :)\n%%%The Cintiq 22HD pressure don`t works In Blender but using a Bamboo works\nsee the video-Bug Report for more info: \n\n53713339\n\nCherrs!\n\nDaniel \n\n--------------------------------------------------------------------------------\nversion 2.64 (sub 9), revision b'52231'. b'Release'\nbuild date: b'2012-11-15', b'13:40:43'\nplatform: b'Linux:64bit'\n--------------------------------------------------------------------------------\n%%%" ]

[ "Clearing a CollectionProperty of ID pointers will dereference duplicate IDs below zero\n## Simplified Report\n\n- Execute the first script below in a new scene with a Cube.\n- The first script will add the cube 10 times to the collection property.\n- Save the file and reopen.\n- Execute the second script.\n- The second script will clear the collection.\n- The cube will get dereferenced to a user count below zero. With this assert:\n - `ERROR (bke.lib_id): source/blender/blenkernel/intern/lib_id.c:322 id_us_min: ID user decrement error: OBCube (from '[Main]'): 0 <= 0`\n- Saving the file again and reopening will remove the cube since it has no users. Even though it was linked to the scene.\n\n```lang=python\nimport bpy\n\nclass TestPropertyGroup(bpy.types.PropertyGroup):\n```\n object: bpy.props.PointerProperty(type=bpy.types.Object)\n```\n\nbpy.utils.register_class(TestPropertyGroup)\nbpy.types.ViewLayer.test_list = bpy.props.CollectionProperty(type = TestPropertyGroup)\n\nfor i in range(0):\n```\n item = bpy.context.window.view_layer.test_list.add()\n item.object = bpy.data.objects[\"Cube\"]\n```\n```\n\n```lang=python\nimport bpy\n\nclass TestPropertyGroup(bpy.types.PropertyGroup):\n```\n object: bpy.props.PointerProperty(type=bpy.types.Object)\n```\n\nbpy.utils.register_class(TestPropertyGroup)\nbpy.types.ViewLayer.test_list = bpy.props.CollectionProperty(type = TestPropertyGroup)\n\nbpy.context.view_layer.test_list.clear()\n```\n\n## Original Report\n\n\nOperating system: Linux-5.15.0-46-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.3.0\nWorked: version 3.1.2\n\n`ERROR (bke.lib_id): source/blender/blenkernel/intern/lib_id.c:322 id_us_min: ID user decrement error: OBCube (from '[Main]'): 0 <= 0` occurs when calling `.clear()` on a CollectionProperty attached to a ViewLayer. In the attached example, the CollectionProperty is a PropertyGroup containing a PointerProperty to bpy.types.Object.\n\n\n1. register properties and operators with provided script\n2. run `bpy.ops.view_layer.test_add_objects_operator()` to add selected objects to the view layer property\n3. save and close file\n4. open file and register properties and operators\n5. bpy.context.view_layer.test_attribute_list.clear() to get error\n\nstart with provided 'untitled.blend' to just run steps 4 and 5\n{F13493946}\n", "Splitting the \"Object Info\" node, access to object original geometry\nFor various use cases (like implementing the \"Deform Curves on Surface\" node as a group),\nwe need access to the original geometry of an object. One proposal was to break apart the\n\"Object Info\" node into separate nodes with more clear purposes:\n\n{[F13561065](image.png) size=full}\n\n{[F13561067](image.png) size=full}\n\nThe general \"Info\" nodes are generally not scalable, and their purpose is vague\nenough that they aren't as intuitive to use. This design means there are separate\nnodes for different use cases. \n\nThe \"Object Transform\" node could have a matrix output in the future.", "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", "Multi-object mode support (parent task)\nThis is a parent task to manage to todo's for multi object editing.\n\nThere are many small todo's.\n\n### Reference Patches:\n\nFor anyone interested in helping out, here are some example commits which can be used as a reference.\n\n- Edit Mesh Face Poke - 3a9669bfff *Committed without indentation, so you can see lines changed more easily.*\n- Edit Mesh Flip Normals - 4704f2687a\n- Pose Mode: Flip Quaternions - 7560aabf71\n\n\nOther commits may be useful too.\n\n### Object Loops\n\nThere is some duplicate code for looping over objects.\n\nWe'll keep the option of having a way of simplifying the looping open.\n\n----\n\nNote: to collect operator ID's.\n\n- this script helps copy them from menus: [P656](P656.txt)\n- this is a more efficient version that watches the x11 clipboard so you can hover over items and press Ctrl-C: [P657](P657.txt)", "New pointcloud object type\n**Status:** *Developers needed for point cloud editing features. Some features part of geometry nodes project*\n\n---\n\n**Team**\n**Commissioner:** `?`\n**Project leader:** `?` \n**Project members:** `-`\n\n**Description**\n**Use cases**:\n* Part of Particle Nodes, Datasets (for example from LIDAR scanning)\n* As part of photogrammetry / reconstruction itself (but is out of scope here)\n* Also might make sense to let the motion tracker output point clouds (\"3D Markers to Mesh\" -> \"3D Markers to point cloud\") (also out of scope here)\n\n**Design:**\n* New point cloud data-block (similar to mesh) with points.\n* Nodes to interact with points (distribute, deform, meshing, etc.)\n* Simple edit mode (mostly for simple operators and managing attributes?)\n\n**Work plan**\n\n**Milestone 1**\n*Basic integration of new data-block type*\n\n- [x] Point cloud data type\n - [x] Attribute support\n- [ ] Point cloud conversion / object operators\n - [ ] Data-set import\n - [ ] Simple operations\n - [x] Conversion to and from mesh [D7391](D7391)\n - [ ] Join point clouds operator\n - [x] Point cloud meshing (OpenVDB tools)\n - [x] Points distribution on meshes *Point distribute node*\n- [ ] Point cloud rendering\n - [ ] EEVEE\n - [x] Cycles\n - [x] Attribute node support\n- [x] Point cloud Python API\n - [x] Access to location/radius/index exists through \"Point\" type\n - [x] general creation/access to attributes\n- [x] Instancing\n- [ ] Transform snap system integration\n- [x] Remove `CD_LOCATION` and use `CD_PROP_FLOAT3` instead\n\n**Milestone 2**\n*More advanced features for editing point clouds*\n\n- [x] Point cloud Inspection\n - [x] Attribute overlay\n - [x] Spreadsheet editor\n - [x] Attribute list\n- [ ] Point cloud edit mode\n - [ ] Display selected points in viewport\n - [ ] Common selection tools\n - [x] Spreadsheet selection filter\n - [ ] Simple operators/nodes\n - [x] #101778 (Node group operators)\n - [ ] Delete points\n - [ ] Separate selected\n - [ ] Duplicate\n - [ ] Transform system integration\n - [ ] Filtering / cleanup (Datasets)\n - [ ] Stitching / aligning?\n - [ ] Filling holes?\n- [ ] Technical attribute paint mode\n\n---\n\n**Relevant links**:\n* `-`", "Outliner selection not working correctly after undoing object deletion\nOperating system: Linux-5.17.15-1-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD VERDE (LLVM 13.0.1, DRM 2.50, 5.17.15-1-MANJARO) AMD 4.5 (Core Profile) Mesa 22.1.2\n\nBroken: 2.91.2, 3.2.0, version: 3.3.0 Alpha\nWorked: prior to b077de086e\n\nAn object that is linked in another collection can usually be removed from just that collection by using unlink, while using delete removes it from both collections. But if you delete the object and undo, unlink does delete the object in both collections. \nRenaming the cube or creating a new object \"breaks\" the cubes apart so they can be selected/unlinked individually again.\n\nIn the default scene,\n- create a new collection\n- in the outliner, ctrl-drag the default cube object to that collection to link it\n- delete the cube\n- undo\n- in the outliner, it is now impossible to select the cube in the new collection separately and using unlink will delete both cubes", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n", "Node groups' new method doesn't throw errors at inputs and outputs collections\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.1.0 Alpha\n\n\nNode groups' new method doesn't throw errors at inputs and outputs collections\n\n1. Create a geometry nodes modifier, get node group:\n\n```\nnodes = C.object.modifiers[0].node_group\n```\n\n2. Add new input or output by command \n\n```\nnodes.outputs.new(\"RGBA\",'new')\n```\n3. Note that there are no errors, but a new socket hasn't been created. \n\n\n\n", "Consider using more explicit names instead of the generic 'Size' value for Empties.\nWhen creating an Empty, the pop-up window specifies the `Radius` for the Empty, presumably because the shape chosen could be a sphere, arrows, or any number of different types.\n\nHowever, when viewed in the Object Data Properties, the radius is displayed as a more generic `Size` value.\n\n\n\nThis leads to confusion, especially when comparing an Empty to a Cube. In the example below, the visual scale of these two items is identical, yet looking at their `Size` tells a different story.\n\n\n\nFor context, this came up as a point of confusion for a use case where I'm using non-scaled empties as a 'holder' for position/rotation/scale while applying a set of custom properties to be exported as .glb and used in threejs.\n\nMy suggestion would be to continue the use of `Radius` as the label in the Object Data Properties, instead of `Size` since that's what is actually meant by the value.\n\n", "Renaming Vertex Group Breaks Modifier's Vertex Group Reference\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 1070 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: Never (2.79+)\n\nChanging name of the vertex group breaks modifier's vertex group reference.\nSame issue has been reported 6 years ago: [#41876](T41876). If it's still a \"known limitation\" or \"to do\", it might be a good idea to tag it with new/proper labels.\n\n1- Launch default Blender.\n2- Create a vertex group to the cube and assign a face.\n3- Create a modifier with vertex group option (Mask modifier for example) and select the vertex group that we just created.\n4- Rename the vertex group and notice that breaks the modifier referencing to that vertex group.\n\n[#74726.blend](T74726.blend)\n", "Collections (parent task)\nPossible improvements for collections user interface:\n* G-key group operators in the 3D viewport and object properties should become more clear.\n* Creating a new collection in the outliner could put all the selected objects (and collections?) in it.\n* Shortcut keys to improve usability, as in #54707.", "Library Overrides: Making an override (for a linked object in the scene collection) creates a duplicate object\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\nLibrary Overrides: Making an override (for a linked object in the scene collection) creates a duplicate object\n\n- open `main.blend`\n- (there is a linked object in the scene collection)\n- `Object` > `Library Override` > `Make`\n- A separate (overridden) Cube object is created in the scene collection (along with the linked object still there)\n\nNOTE: doing the same from the Outliner (RMB > `Library Override` > `Make` > `Selected`) seems to work as expected\n\nas a comparison:\n- open `main_with collection.blend`\n- (there is a linked object in a collection [not the scene collection])\n- `Object` > `Library Override` > `Make`\n- The overriden Cube object is just there without the linked object Cube being present\n\n", "Joining Armatures\nJoining armatures is something that will become common in my workflow in the coming months and knowing this, I had to write an [operator](armature_merge.py) to facilitate this. But it feels like this should just work without an addon. I'd like to know if the rest of the animation module agrees, and this is something that could go into Blender's Join operator, or if any of these changes are controversial.\n\nThis is something I just might be able to implement myself, but I'd rather let a competent developer do it, if there are any volunteers. :)\n\nHere are the current problems when simply trying to join two armatures:\n\n**Bone Groups**\nBone Groups of the active armature are preserved, but bone groups of the source armature(s) are completely nuked, or worse, assigned seemingly at random.\nSometimes two armatures will have bone groups with the same name. In this case it would be best to \"merge\" these bone groups. It could happen that identically named bone groups have different colors, in which case this color data will be lost. In this case such bone groups could be suffixed with a .001 instead of being merged. But strictly only if the bone group colors do not match, otherwise just go ahead and merge them.\n\n**Parenting**\nCurrently, when joining Armature A into Armature B, all objects that were parented to A are now parented to B. This is good! However, if the armatures weren't in the same place, the parented objects will move because their transform matrix and parent inverse matrix is not set. (Currently in my script I set the transform matrix, but I guess changing the parent inverse matrix would be more correct.)\n\n**Modifier's References**\nSticking to the above A->B example, armature modifiers that were referencing A now reference nothing. I think these references should be redirected to Armature B.\nPerhaps this can be applied more generally, so that when any objects are joined into an object O, all references to the merged objects should be remapped to O? Are there any cases where this would be bad?\n(Note: I tried doing this with the current bpy.ops.outliner.remap_users() operator, but it segfaulted.)\n\n**Vertex Groups**\nBone names can clash, and then they need to be appended with a .001 in their name. That's fine, but in this case the objects that were rigged with the original bone names now have vertex group names that did not get renamed. Fixing this is very painful. So, these vertex groups should be renamed along with the bones.\n\n**Speed**\nJust a nitpick, but I find it odd that joining complex rigs can take up to 10 seconds! I've added some timers to my python operator to show how just the Join operation is taking super long. Maybe some low hanging fruit optimization is possible there?\n\nTest files:\n[simple_armatures_with_objects.blend](simple_armatures_with_objects.blend) (Just press Ctrl+J to see the usual result, and Alt+H to see the desired result)\n[complex_armatures.blend](complex_armatures.blend) (For testing the speed)\n\nCC @dr.sybren @jpbouza-4 @LucianoMunoz and any other people interested in rigging, for opinions :)", "\"Make Single User\" does not unlink object from other scenes when creating Scene using \"Linked Copy\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.6 Release Candidate\nWorked: 2.90.1 (according to [description by user DAG here ]], who lists his software version in a [[ https:*blender.stackexchange.com/questions/74460/how-to-unlink-remove-an-object-from-a-scene/227238#comment383264_74486 | comment higher in the same question, here ](https:*blender.stackexchange.com/questions/74460/how-to-unlink-remove-an-object-from-a-scene/227238#227238).\n\nScenes created using the \"Linked Copy\" option do not allow objects to be unlinked via \"Make Single User\".\nAdditionally, in my testing, I have not found any way to make single user objects in a scene created using the \"Linked Copy\" option or in the original scene (i.e. creating a new object in either scene always creates a **linked** object). Objects deleted from one scene are also deleted in the other. Because of this, I have not been able to find a way to change a Scene created via \"Linked Copy\" independently of the original scene, making the \"Linked Copy\" option functionally useless.\n\n\n - Open a new default file\n - Create a new scene using the \"Linked Copy\" option\n - Select the default cube in the new scene (will likely be already selected)\n - \"Option\" menu -> \"Relations\" -> \"Make Single User\"\n - Delete the cube in this Scene\n - Switch to the first Scene\n\nExpected Result: The default cube is still in the first Scene\nObserved Result: The default cube has been deleted from the first Scene\n\n\n\n", "Nodes for procedural hair\n# Nodes for procedural hair\n\nThis is a list of various nodes required for a procedural workflow when creating hair with the new hair object in blender. Some nodes will be possible to create as node groups in geometry nodes and some will have to be converted or created as \"proper\" nodes. \n\n---\n**Current approach**\nI (@DanielBystedt) will use my experience with grooming in other softwares and set up some node groups in geometry nodes as prototypes. @SimonThommes will iterate on those nodes and change any parts that he thinks can be improved (optimization, general usability etc)\n\nHair node designs that require a \"proper\" node instead of a node group will need help from C++ developers such as @JacquesLucke \n\n**Various issues**\n\nIMPORTANT:\nIt's not possible to resample hair curves in geometry nodes. This makes it hard to create high resolution dependent hair like curls for instance\n\nNOTE:\nThe self node (or similair) should be able to read a hair objects surface and UV Map to minimize extra inputs per hair nodes (object and uv map)\n\n---\n\n**Nodes list**\n\n\n**Distribute child splines on faces**\n**Prio (1-10): 10**\n\nDistribute child splines on a surface. Let it be possible to interpolate curve length and shape based on curve input. Patch [D16642](D16642) by Jacques Lucke in progress\n\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n\n\n---\n**Hair info per point**\n**Prio (1-10): 8**\n\nThis node will give the user spline related data that is outputted per point. Since similair type of data is reused in a lot of the hair node groups it makes sense to have a node like this.\n\n{[F14132928](image.png), height = 400}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n**Node name**\n**Prio (1-10): 8**\n\nClump curves based on another set of curves. Curves will interpolate to the same length as the clump curves\n\n{[F14132937](image.png), height =250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n**Frizz hair**\n**Prio (1-10): 7**\n\nThis node deforms the points of the curve based on a field (such as a noise texture). Each curve index should be usable as a \"seed\" for the noise to not get too uniform noise based only on point position. Uniform noise might also be desired. Perhaps implement a switch?\n\n{[F14132950](image.png), height =250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n**Curl hair**\n**Prio (1-10): 6**\n\nCurl hair along the tangent axis of another set of hair curves or a sparse set of the same hair curves. \n{[F14132957](image.png), height = 250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n**Smooth hair**\n**Prio (1-10): 6**\n\nSmooth/interpolate the position of the points per spline. Should have control for locking the tips of each hair/curve\n\n{[F14132967](image.png), height= 250}\n\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n**Braid hair**\n**Prio (1-10): 5**\n\nBraid curves along another set of curves or a sparse set of the same curves. It would be useful to both do \"normal braids\" but also \"cornrows\". Cornrows might need a separate node setup\n\n{[F14132963](image.png), height = 250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n\n**Redistribute hair points**\n**Prio (1-10): 5**\n\nRedistributes the points in each curve so that the distance between the points are equal\n\n{[F14132980](image.png), height = 250}\n*Points in the image are a temp debug tool for visualization*\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n\n**Rotate hair**\n**Prio (1-10): 4**\n\nRotate each curve by using the axis of the closest face surface normal or vector from curve root to tip. This is useful for creating some random overlap\n\n{[F14132986](image.png), height = 250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n\n**Shrinkwrap hair**\n**Prio (1-10): 4**\n\nShrinkwrap hair to the surface with an offset. This should be blended with a factor. When deforming hair it is very common that some points end up inside of the surface that the hair is growing from. This node has an option to push those points outside of the surface\n\n{[F14132990](image.png), height = 250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n\n**Bend hair**\n**Prio (1-10): 4**\n\nLong hair has a tendency to bend a bit at the tip of the hair strand. I guess we would use a point from a slight lower value on the curve factor (e.g. slightly closer to the root) as pivot. The axis to bend would be the cross product of the first curve point position, the surface normal and the curve tip position.\n\n- - [ ] Ready for implementation\n - - [x] Prototype wip\n - - [ ] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n\n**Displace hair**\n**Prio (1-10): 3**\n\nDisplace hair along surface normal or object/world vector displacement. Useful for displacing hair with displacement maps that are used in rendertime on the surface object. Also for creating cheap wind effects\n\n{[F14132998](image.png), height = 250}\n{[F14133000](image.png), height = 250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n\n**Straighten hair**\n**Prio (1-10): 1**\n\nStraightens the hair with a factor. The user should be able to\n- Keep length (by factor)\n- Keep length\n\n{[F14133005](image.png), height = 250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n\n**Interpolate hair shape**\n**Prio (1-10): 3**\n\nInterpolate shape of splines based on another set of splines. Splines interpolates based on distance to another spline so that the different curve sets can have different topology. This is useful when a hairstyle changes from one hairstyle to the next. For example: a person strokes the hair in front of their face to behind their ear.\n\n- - [ ] Ready for implementation\n - - [ ] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n**Hair noise attribute**\n**Prio (1-10): 3**\n\nDoes NOT deform hair. This is a utility node that outputs random values per spline or point. This node can be used in more complex setups to assign random blend or frequency to other hair nodes\n\n{[F14133016](image.png), height = 250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n**Set hair length**\n**Prio (1-10): 3**\n\nRedistributes the points along the current shape of each curve. If length > 1, each curve will extend along the vector of the last two points of the curve.\n\n{[F14133020](image.png), height =250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n**Scale hair**\n**Prio (1-10): 3**\n\nScales each curve uniformly from the root of each curve. The user can also set a target length. This is useful if a lot of hair deformations has resulted in a new length per curve\n\n{[F14133031](image.png), height = 250}\n\n- - [ ] Ready for implementation\n - - [x] Prototype exists\n - - [ ] Iterated by @SimonThommes \n\n---\n\nRelated Link: [Procedural Hair for Blender 3.5 Meeting Notes ](26700)\n" ]

[ "appending sometimes links\n%%%--- Operating System, Graphics card ---\nwin7, gef430\n\n\n - Blender version with error, and version that worked ---\n2.67.1\n\n\n - Short description of error ---\nwhen I append something, blender does linking\n\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\nsorry, very hard to reproduce, but some other guys has same problems here:\nshowthread.php?301451-blender-2-68-oddity\n\n%%%" ]

[ "Symmetry on sculpt mode won't work with auto masking topology enabled\nOperating system: Windows-11\nGraphics card:Quadro RTX 3000/PCIe/SSE2\n\nBroken: Blender 3.5.0\nWorked: N/A\n\nSymmetry on sculpt mode won't work with auto masking topology enabled.\n\n\n- Have a mesh that has two disconnected parts across a symmetry axis.\n- Enter sculpt mode, turn on \"Advanced -> Topology\" (topology auto masking).\n- Turn on X symmetry for sculpting brushes.\n- Sculpt on one part of the mesh, the opposite side doesn't change.\n", "Selection to Active doesn't work when the selected object is a child of the active object\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.25\n\nBroken: version: 3.3.0 Beta\n\n\nSelection to Active operator doesn't work when the selected object is a child of the active object.\n\n\n1. Add 2 cube.\n2. Parent one of the cubes to the other.\n3. Select both cubes such that the parent is active. \n4. Use the Selection to Active operator.\n5. The operator has no effect.\n\n", "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", "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", "Display as behaviour in rendered view inconsistent between Eevee and Cycles\nOperating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19\n\nBroken: version: 2.82 (sub 4)\n\nWhen objects are set to display as wire or bounds, in the rendered view in eevee they are shown as wire or bounds respectively, but in Cycles they are fully rendered. \n\nFor any object, under object properties -> viewport display, set display as to \"bounds\" or \"wire\". Subsequently when the viewport is set to rendered view, the object is shown as bounds or wire in Eevee, but in Cycles the object is fully rendered. The Cycles way would be the preferred way in my opinion.", "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", "Mantaflow - Bake not showing (when noise is used)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.7262\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.83\n\nEnabling Noise and then Baking Noise, the preview no longer shows. \n\nFrom Attached Blend\n\n\n - Bake Data\n - Play Animation (see preview)\n - Enable Noise\n - Bake Noise\n - Play Animation (No preview is shown)\n - Disable Noise \n - Play Animation (see preview)\n\n [smoke_noise.blend](smoke_noise.blend)\n", "Object Info node random output doesn't work properly\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13399 Core Profile Context 0\n\nBroken: version: 3.6.2\nWorked:\n\n**Short description of error and steps for others to reproduce the error**\nI have a scene with many collection instances of a collection containing a car and its wheels. The car has a material on it with its base color being controlled by an object info node's random output:\n[![enter image description here][1]][1]\n\nEverything looks good as long as I am in material preview with the overlays turned off:\n[![enter image description here][2]][2]\n\nBut with the overlays turned on(or sometimes the other way around) or if rendered using the EEVEE render engine, all the cars will have the same color.\n[![enter image description here][3]][3]\n\nHere is the .blend file:\n4whyzTYK#LYLMOGpAT3VvUi4j73Jg63W2p8sG_HRQ8L3E_A107z0\n\n [1]: Api9y.png\n [2]: XZ0Gz.png\n [3]: OeeZJ.jpg\n\n", "Geometry Nodes socket is not showing relevant value info for current modifier\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.3.0 beta\n\nUsing many modifiers with the same GN node tree (multiple users) has some issue with data updating.\nIf you bring cursor over socket to see its value, then it shows only data from first GN modifier, no matter what modifier is selected at the moment. Seems to be only interface problem, as internally processed data is correct.\n\nIn attached file bring cursor over orange socket (Object type) and it will show same object for both modifiers, when in fact they are different.\n[socket_info_issue.blend](socket_info_issue.blend)", "Wireframe modifier strange behaviour\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.2\n\nStrange behaviour from wireframe modifier\n\n\nTook a plane and subdivided, added a wireframe modifier, unsubdivided. Some corner vertices are pushed to the edge of scene.\n[Based on the default startup or an attached .blend file (as simple as possible)][Wireframe.BugReport.blend](Wireframe.BugReport.blend)\n\n", "Optix fails when geometry nodes instance has animated translation and scale 0 and motion blur is on\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.6.0 Alpha\nAlso broken in 3.4.1\n\nRendering will not start. It stops at \"Building OptiX acceleration structure\"\n\n\n\nThe culprit seems to be a combination of animated Translation and Scale 0 together with animated Rotation of the object and motion blur.\n\n\n\nDoesn't work in OptiX. Cuda and CPU both work.\n\nOpen the .blend file and render the frame.\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!", "Object properties In-front doesn't work in viewport shading\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nObject properties In-front doesn't work in viewport shading\nAll the other options works in Object properties/viewport display, except for In-front \n\n\n- Open attached file\n- Go to Viewport Shading\n[lookdev_in_front_bug.blend](lookdev_in_front_bug.blend)\n", "Asset Browser doesn't show assets when drop-down set to \"All\"\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.6.0 Alpha\nAlso broken in 3.5 stable version!\nWorked: This feature is new as of 3.5 and I'm seeing the behavior in both. \n\nAssets from other files are not visible when asset browser preference is set to \"All\" (when assets are part of catalogs)\n\n- Extract uploaded file\n - Open general blend file\n- Set it as asset library path\n- Open asset browser and set preference to \"All' [notice every asset is visible (i.e. engine parts and sculpted sphere)\n- Now open `open-file.blend`\n- In asset browser, set preference to \"All\" (notice engine assets are missing)\nIf switched to \"user library\" then engine assets are visible\n", "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: Wire frame display doesn't draw every edge in some cases\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 526.47\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.4\nCaused by 10131a6f62\n\nin some meshes the wireframe display doesn't show all edges. Most obvious in 2d meshes but also with meshes that have stretched or concave face areas. Happens in wireframe mode, wireframe overlay and object properties->VP display: wireframe\n\n\n\nthis is the same object in object and edit mode\n\n[wireframe_overlay_bug.blend](wireframe_overlay_bug.blend)\n\nselect object 3, enter edit mode, return to object mode - wire overlay is gone.\n\nsave and open in blender 3.4, select any, enter edit/sculpt mode - peekaboo, wireframe is back in objectz mode\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.", "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", "Blender freezes when moving the cube repeatedly on 3.6 and 3.5\nOperating system: Ubuntu 23.04\nGraphics card: Intel UHD 620\n\nBroken: 3.6.2 2023-08-16\nWorked: None\n\n\nWhen opening Blender(first or other times) and choosing general then moving the cube in multiple directions, Blender freezes\n\n\n- Open Blender\n- Choose general\n- Move the example cube with the move tool in multiple directions\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.", "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", "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", "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)", "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!", "(Linux; AMD Radeon GPU) Rendering a complex scene with eevee crashes desktop environment / causes rendering and viewport artifacts\n```\nOperating system: EndeavourOS Linux / Fedora Linux (Same issue on both distros)\nGPU: AMD Radeon RX 6800 XT (16 GB VRAM)\nCPU: AMD Ryzen 5 3600\n```\n\n```\nrenderer:\t'AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64)'\nvendor:\t\t'AMD'\nversion:\t'4.6 (Core Profile) Mesa 22.3.7'\ndevice type:\t'AMD'\nbackend type:\t'OPENGL'\n```\n\nBroken: 3.4.1, 55485cb379f7, blender-v3.4-release; 3.5.0 Release Candidate, d5d8246441a5, blender-v3.5-release (both version exhibit the issue)\n\nWhen rendering complex scenes in Eevee (Scenes with many different objects), one of the following occurs:\n\n 1. On **X11**: Computer freezes for about 5 seconds before all monitors cut to black. After about 5 seconds on a black screen, the login screen appears and I can log in as normal, as if I logged out. All of the applications have closed.\n 2. On **Wayland**: Render finishes rendering, but many of the objects appear broken; they are semi transparent or appear as if they were using the holdout shader. Returning to the viewport causes all objects with transparency to flicker randomly and appear distorted. Occasionally, the desktop of the computer itself will become broken and artifacted, only logging out or restarting fixes it. This usually isn't possible, however, as after a short while everything all displays cut to a black screen. Unlike X11, however, the only way to recover from this is to restart the PC by holding down the power button.\n\nThis issue **only occurs on linux and does not occur on my Windows 10 partition**, even with the exact same settings and scene. It also only occurs when actually trying to render the scene. In the viewport everything works just fine, even on rendered view where everything looks the same as it should in the render.\n\nThis issue seems to occur regardless of the GPU Usage; even when I limit the GPU clock and power draw significantly it still happens.\n\nThe attached .blend file is an example of a simple scene which triggers the bug. It seems to occur no matter what the render settings are set to.\n\n", "Scene Proxies in the Video Sequence Editor\nWindows 7 Ultimate, 64-bit, 32GB, 5960x, Nvidia Quadro FX 1800 (Primary) & GeForce 9800 GTX+ (Secondary)\n\nBroken: (2.79a) Official builds\nWorked: (2.79) Official builds\n\n\nTo cut a long story short @ideasman42 disabled Scene proxies in the Video Sequence Editor because:\n\n> In #54048#485268, @ideasman42 wrote:\n> Looked into this and for now **building proxies doesn't support anything besides movie, so disabling support for this.**\n> \n> 6535f668b4\n\n\n*This shocked me, have I been using Blender wrong?* Because I've been happily doing this for months.\n\nI don't quite understand the rationale behind the removal of is.\n\nThe main problem for me is that I have projects (made in 2.79 and earlier) that rely on scene proxies and when opening them up in 2.79a viewing or creating them doesn't work.\n\nNow there *are* issues with Scene Proxies most notably the aforementioned (#54048) one and it can be really bad:\n\n[0001-2565.mkv](0001-2565.mkv)\nand\n**Other proxy issues**\n - Skipping frames whilst rendering.\n - Properties side panel scrolls up after changing proxy location in the File Explorer.\n - Overwrite don't have the same behaviour as Overwrite does in the render setting (in the properties editor)\n - and [inconsistent functionality ](F2418236).\n\nBut I've always treated this as an incomplete feature, (same way I treat NetRender, it's somewhat stable but is inconsistent. e.g. blender/blender-addons#52502) throwing in a bug report due to just crashing (#53792) and have been fine.\n\nBut now with the update, the [Proxy/Timecode Panel ](proxy.html) is still there and does nothing. and as I said in my query to @ideasman42's decision to disable this:\n\n> In #54048#485618, @ChristopherAnderssarian wrote:\n> So, @ideasman42 does this invalidate my bug report? #53792\n> Also, is it a good idea to disable this considering the Proxy/Timecode Panel option still there (or are you still working on this)?\n> \n> With no information or feedback in the Blender Manual or when trying to create proxies (nothing happens), `you are going to get users confused on a essential feature that worked` (works fine in cycles for me (not the file names the crashing)) in 2.79 `and now doesn't with no apparent reason why. `\n\n___\n\n> In 6535f668b4, @ideasman42 wrote:\n>>...generating proxies currently only works for movies...\n\n*No... they don't. They worked for Scenes before. (and they work for images for that matter)*\n>>...cancel until other types of sequence strips are supported...\n\n*What do you mean by this? That it's officially 'supported', documented?* \n___\n\nNow that I've been trying to research around a bit, is this an incomplete feature or has it slowly gotten broken in time?\nThere's #43857 which uses a scene proxy. So there must be other uses who uses this right? Or was this just an example?\nI would love to use this with Eevee; having the proxies rendered in no time and my GPU not getting taxed.\n___\n\nWhat I think to be good next steps:\n\n - Having the functionality back as it was before.\n - An open task to deal with the *Other proxy issues.*\n___\n\nZipped folder with a working Blender file and proxy:\nTested in Ubuntu VM both 2.79 and 2.79a with reproducible behaviour.^\nTested on a separate laptop with both 2.79 and 2.79a with reproducible behaviour.^\n(Note: In my Ubuntu VM I had to toggle Textured Solid button in the Scene Preview/Render Panel to get the proxy showing in 2.79.)\n(^ Reproducible behaviour being: fully working in 2.79 and not working at all in 2.79a)\n[Blender_VSE_Testing_Scene_Proxy.zip](Blender_VSE_Testing_Scene_Proxy.zip)\n\n\nI'm sure this was just a misunderstanding.\nYours,\nA passionate Blender user", "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", "crash when changing viewport shading to wireframe mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14760 Core Profile Context 21.2.3 27.20.14535.3005\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-04-23 20:25, hash: 17fca62fff9b, type: Release\nBroken: 2.81\nWorked: 2.80\n\n\nif you have a high poly mesh and try change the shading mode to wireframe. depending on the model it constantly crashes.\n\n\nI noticed this trying to make a retopo of a character. I tried to check what was causing de crash by deleting each object and testing the wireframe. \n\nI deleted everything but the main body mesh, without any uv map, vertex color or any other thing that could make it heavier, and also I tried reseting factory settings.\n\nI would send the file but its 200mb, the main mesh has about 4million vertices.\n\n\nthe crash doesn't happen when changing to eevee or solid view, it only happens when changing to wireframe.\n\nImportant note: if you DON'T move the camera after opening the file before changing to wireframe it doesn't crash even if you go to solid and wireframe back and forth as shown in the video bellow \n[2021-05-01 14-18-16.mp4](2021-05-01_14-18-16.mp4)\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[untitled.blend](untitled.blend)\n- open the file above\n- rotate it about 180degrees\n- activate wireframe", "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)", "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", "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" ]

[ "Regression: 'Viewport Render Animation' stuck and crashes\nOperating system: `macOS Monterey 12.3`\nGraphics card: `Apple Silicon M1 Max`\n\nCaused by 0a32ac02e9\n\nTrying to render even the simplest animation (a cube moving up, 250 frames) through \"Render viewport animation\" gets stuck at about frame 25. The cursor changes to a weird box shape, and the whole process gets stuck, seemingly indefinitely.\n\n* Open Blender\n* Create a simple animation (cube moving up for example)\n* {nav View > Viewport Render Animation}" ]

[ "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", "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", "EEVEE and Workbench missing animatable properties\nOperating system:\tWindows 7\nGPU:\t\t\tRadeon Vega 64, Divider version: 19.12.2\nCPU:\t\t\tIntel Core i7-5960X\n\n\nWorking-ish*:\t\t`blender-2.79b-f4dc9f9d68b-windows64` (official release) \nBroken:\t\t\t`blender-2.80-f6cb5f54494e-windows64` (official release) and later\n\n\nEEVEE and Workbench's render properties (`Properties Editor --> Render Properties`) are, for the most part, not animatable.\nThis is in contrast to Cycles which, *for the most part*, has all settings set to be animatable.\nBack in 2.79b the OpenGL \"Workbench\" Render options were supported:\n\n\n\nSome of the panels like Film, Simplify and Colour Management (which exist in all render engines) work as expected from 2.7X to 2.8X.", "Hair particle system duplicates objects on some faces and don't fill the rest\nOperating system: Ubuntu 19.04\nGraphics card: AMD Radeon RX580\n\nBroken: (2.81 release compiled from source)\nWorked: (optional)\n\nEven with even distribution enabled, 1 particle per face and a low count of particles to spawn, the particle system put two particles on the same face but with different sizes.\n\n1) Create a cylinder with 32 vertices.\n2) Create a small (scale 0.05) cylinder to use as a reder for particle.\n3) Delete the top and bottom faces of the small cylinder so it becomes like an empty tube.\n4) Enable particle system hair on first cylinder and, choose 30 as number, 1 per face source and disable random order, select as render object the small cylinder, the scale 1.0 and choose to randomize the scale a few (0.5 is ok).\n5) Play with the number of particles and the seed and more than sometimes you will notice two or more small cylinders rendered on the same place overlaping (specially on the top and bottom faces).\n\nWhat I expect:\nIf you count the number of faces of the cylinder (added with default parameters) it will have near 30. If I choose \"even distribution\" of particles and \"1 for each face\" without random, what I expect is that all the faces of the cylinder have at least 1 particle, no more, no less.\nIf there are 30 faces and if I limit the number of particles to exactly 30, there must be exactly one particle for each face.\nWhat happens actualy is that there are 4 particles lying around on the top and bottom faces and I don't know why. And there are no particles on some other faces. And sometimes two spawns on the same place on the bottom or top face of the cylinder.\n\nWith complex meshes it makes a mess, specially if I need to paint the weight to affect density. In that case there are more particles on some places and there are no particles on places with a high value of weight. \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.", "EEVEE macOS: visual glitching when using Tangent shader input on hair\nOperating system: macOS Big Sur 11.2.3\nGraphics card: AMD Radeon Pro 5500M 8 GB, Intel UHD Graphics 630 1536 MB\n\nBroken: 3.0.0 Alpha, e81533b25e6b, master, 2021-09-28\nWorked: Unknown\n\nAttempting to use the \"Tangent\" shader input on hair with EEVEE results in visual glitching and smearing in the viewport:\n[EEVEE Hair Tangent Bug example.mov](EEVEE_Hair_Tangent_Bug_example.mov)\n\nFurthermore, if the tangent input is used in a node tree with any BSDF nodes, the hair will fail to render at all, appearing checkered as if it were using holdout instead:\n\n\n\nI've tested on both Windows and macOS; **only macOS is affected**.\n\nA similar bug occurs with the Parametric input, however it's slightly different so I will open another report for that one.\n\n\nPart one: \n1. Add a particle system to the default cube, or any mesh\n2. In the particle settings set the type to Hair\n3. To visualise the hair more clearly: under Hair Shape, increase diameter scale to 0.1. Also, under Render Properties -> Hair, set the Hair Shape Type to \"Strip\"\n4. Add a material to the mesh if it doesn't already have one\n5. In the shader editor add a Geometry node\n6. Connect the \"Tangent\" input to the Surface port on the material output node\n7. Enter EEVEE Material Preview or Rendered mode and orbit the 3dview to see smearing and glitching\nPart two:\n8. Add a diffuse BSDF (or any BSDF) node\n9. Connect the tangent input to any port on the BSDF node.\n10. Render with F12. In the rendered image any hair strips appear checkered as if they were masked with holdout\n\nExample blend file below. Note: if the hair doesn't show up, toggle \"Regrow\" or any other option in the particle settings.\n[EEVEE Hair Tangent Bug.blend](EEVEE_Hair_Tangent_Bug.blend)", "Hair Particles: Deflect Emitter option will affect all edited hairs\nOperating system: win 10 \nGraphics card: 2x vega 56\n\nBroken: 2.90 alpha\nWorked: 2.79\n\nWhen combing hair with deflect emitter on, **all** hair is affected (not just the hair in the brush radius).\n[for further explanation, see comments below incl. a potential fix]\n[#79042.webm](T79042.webm)\n\n**Original report (was also showing that deflect is affecting hair outside the brush radius -- collapsing itself is not considered a bug)**\nwhen combing hair with deflect emitter on, it causes chunks of hair to collapse into the mesh. deflector size has no effect\n\n\n\nmesh this is happening on \n[bugged hair.blend](bugged_hair.blend)", "sculpt mode artifacts if displace modifier is active\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.28\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIn sculpt mode if the displace modifier is active the brush behavior is unpredictable, especially with the smooth brush.\nIt looks like that the sculpting mode takes account of the mesh after being modified by the modifier and start the sculpt over it.\n'm reporting this because in other modes the modifier and the actual edit of the mesh are handled as separate thing.\n| [smooth_brush_prob.mp4](smooth_brush_prob.mp4) | [06_24_2022.mp4](06_24_2022.mp4)\n| -- | -- |\n\n- Open any of the attached files and try to smooth or grab as done in the video\n\nthanks!\nMax\n\n\n[smooth_bug.blend](smooth_bug.blend)\n[sculptbug_24062022_1422_44.blend](sculptbug_24062022_1422_44.blend)", "Image Texture shader node with Box projection outputs extreme values when mesh has unusual normals\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0\nWorked: can't test in other versions, since they can't open .blend files saved with Blender 3.0\n\nIf you open the attached file, you will see a mesh that's black everywhere except for some *very* bright pixels (the Bloom effect makes this glitch very pronounced).\nThe material is just an Image Texture node connected to BSDF's color, using Box projection and a completely black texture. Theoretically, it should only output interpolations between the colors of the source texture, but that's definitely not the case here.\nOn its own, the mesh doesn't exhibit the glitch, but some modifiers (such as Displace or Wave) make it manifest for certain combinations of parameters. I suspect that the mesh has some unusual normals or face orientations that the modifiers amplify into even weirder normals, which in turn cause trouble in Image Texture's Box projection.\n[shiny glitch blender3.blend](shiny_glitch_blender3.blend)\n\nOpen the attached file, wait for shaders to compile.", "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", "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", "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)", "Hair rotation/tilt do not work with path\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\nWhen i am trying to use rotation with paths/strands it just do not work at all.\nI know that new hair system is in development and probably this issue will not be fixed for current system.\nBut I hope, it will fixed at least for next one. Perhaps as «initial normal distortion» or something like that.\n\n[2020-11-08_22-11-50.mp4](2020-11-08_22-11-50.mp4)\n\n**to reproduce**\nOpen a file, switch rendering type to path.\n[hairRotation.blend](hairRotation.blend)", "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", "Cycles GPU/CPU render difference with more than 64 transparent bounces and coplanar faces\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\n\n\nWhen using particle plane with transparency ( to fake volume scatter ), we have a color mismatch between CPU and GPU rendering. \n\n\n see attach file\n\n\n\n[cpu_gpu_issue.blend](cpu_gpu_issue.blend)\n \n" ]

[ "hair doesn't render in workbench but does with openGL\nOperating system:\nGraphics card:\n\nBroken:\n2.80, 957b4547aeeb, blender2.8, 2019-01-28 22:11\n\n\nRendering hair in workbench doesn't work if using standard Render Animation -- bpy.ops.render.render()\n\nHowever when clicking the Display Render View in viewport and setting view>viewport animation -- bpy.ops.render.opengl() -- it works.\n\nI'm guessing these are different in that a separate operator is used? however the results are so similar i assume they are using the same engine?.\n\nUse the file attached.\n[test_hair_workbench_renders.blend](test_hair_workbench_renders.blend)\n\nOR\n1. Create new file and create a sphere then animate it.\n2. Add hair to it, turn dynamics on and cache\n3. Render Ctrl+F12 -> review result\n4. Render openGL -> review result and make comparison" ]

[ "Huion KD100 - incorrect programmable keys reading\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 27.20.100.8477\n\nBroken: version: 3.3.1\n\nHi, I got a Huion KD100 Mini Keydial and Blender seems to be the only software not regonizzing it's programmable keys correctly. I have set it up as Numpad keys, but Blender does not recognize the assigments, reading the keystroke values for Num Lock off. Affinity Designer, Photo, Google docs, everything else recognizes the defined keys, even with app profiles. Sadly Blender does not as the only one.\n\nThe only step here is really to hook up a configured KD100 and trying to change the view. Can also be easily verified in the Preferences section by testing the key bindings. \nI would be more than happy to test/debug further with my device if that's helpful.\n\n", "picker isn't working on cryptomatte matte id picker\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.3.0 Alpha\n\n\nadd a cryptomatte node (new or legacy), hover over matt id and press E . No picker will appear meaning user must click the + icon.\n\n\n", "Add modifier error message for attribute name clashes\nIf user has a UV and a vertex color groups with the same name things behave in non predictable ways.\n\nThe nodes modifier should check for this and add an error message when this happens.", "Keymap: custom key modifiers work inconsistently\nOperating system: Arch Linux, no DE, i3wm\nGraphics card: GTX 960\n\nBroken: 2.80\nWorked: 2.79\n\nI'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79.\n\nLoad factory settings\nImport .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move)\nEnter sculpt mode\nAttempt to sculpt inverted by holding NumpadEnter+LMB\n\n[system-info.txt](system-info.txt)\n[custom_modifier_bug.py](custom_modifier_bug.py)\n\nSimilar bugs from ages ago:\nT44349\nT34822", "Particle bug\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nHair particles in particle edit mode cannot add new particles if emit is set to vertices. When you try to change emit to faces - all previously created particles disappear.\n\n\n[test.blend](test.blend)\n", "Shader warnings with --debug-gpu\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon PRO W6800 ATI Technologies Inc. 4.5.14802 Core Profile/Debug Context FireGL 21.Q4 30.0.14002.136\n\nBroken: version: 3.0.0 Beta\n\nWhen launching Blender and the --debug-gpu option on the follow warnings are displayed\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_412 FragShader:\n```\n |\n```\n 6 | #extension GL_ARB_shader_draw_parameters : enable\n```\n | ^\n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n```\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_399 FragShader:\n```\n |\n```\n 6 | #extension GL_ARB_shader_draw_parameters : enable\n```\n | ^\n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n```\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_437 GeomShader:\n```\n |\n```\n 5 | #endif\n```\n | ^\n | (#310) Inputs that are integers should be qualified with the interpolation qualifier \"flat\"\n```\n\n\n1. Launch blender using blender --debug-gpu\n2. Warnings are displayed to the console.", "Invalid ColorRamp marker numbering with pasted driver \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.23.04 30.0.13023.4001\n\nBroken: version: 3.1.0\n\nit is possible to make not the second marker the second in color ramp \n\n\ngo to shader editor\nadd ColorRamp, add 2 additional markers on (4 total), set one of marker position to 0.5, another on 0.8\n\nadd value node, set value on it to 0.1\nright click on value -> copy as New driver\n\nin color ramp switch to second marker and paste the driver in position value window\n\nP.S. idk does it work correctly, but after this isn't possible to move first marker futher the second that equals 0.1 ¯\\_(ツ)_/¯\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", "Breaking shader node changes for 4.0\nThere are a number of proposed changes to shader nodes that break the Python API, mainly for add-ons that import and export shaders.\n\nWe need to make a decision to either:\n* Make these breaking changes in 3.2 or 3.3, and then do them all together with good communication so scripts only need to be updated once.\n* Postpone all breaking changes to 4.0, and see which parts of these patches can be non-breaking. For example we could have new general Mix/Combine/Separate nodes in addition to the existing ones.\n\nPatches:\n* [x] [D14034: Geometry/Compositor/Shader/Texture Nodes: Add general Combine/Separate Color nodes](D14034)\n* [ ] [D14257: Shader Nodes: Changes to node UI and default values to improve consistency](D14257)\n* [ ] [D14202: UI (Shader/Compositor): Rename \"RGB\" input to \"Color\" input](D14202)\n* [ ] [D13749: Node: Mix node](D13749)\n* [ ] [D13359: Rename \"fac\" to \"factor\" across all nodes](D13359)\n* [ ] Use proper \"Brightness\" word in names", "Lag Adjusting Value Sliders & Navigating Nested Menus with a Wacom Tablet\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93.2\n\nTrying to change the value of shapekeys or shader sliders with my stylus doesn't get detected the first few seconds, then picks up, but in a non responsive way. Also while using my stylus, if I navigate to a nested menu like say \"Object > Transform\" There's a Lag when moving to another option in the \"Object\" Menu.\n\nThe steps above should apply. I did notice though, that if I change my Tablet API from 'Automatic' to 'wintab' in the the input preferences, it helps, but its still not as responsive as it is in 2.93\n\nAll these issues though, were non existent, if I tried using my laptop's trackpad. Also, my tablet is a Wacom Intuous Touch 5 with a stylus that supports up to 2048 levels if pressure sensitivity and has tilt support, just incase it could be any of these causing the issue. \n\nThanks.\n\n", "Workbench: Shadow Bug\nOperating system: MacOS Catalina\nGraphics card: Intel Iris Pro 1536 MB\n\nBroken: 2.83\n\nWhen trying to add a shadow, all screen \"cracks\" into different-shadow pieces\n\n\n\nViewport Shading> \"checkbox\" Shadow ", "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", "Python API docs Error\n\nI'm not sure that it needs to be sent here\n\nThe Python API Docs contains an error - it says that blender as a python module need to be compiled independently. but this has not been the case for a long time\n\n\n\n", "Quick Favorites: add support for operator/prop enums (e.g. \"Set origin\")\nOperating system: Windows 10\nGraphics card: Nvidia GTX1080\n\nBroken: 2.80, 16fc62e15f0, blender2.8, 2018-12-12\nWorked: 3d92afca7eb\n\nThe Set origin menu is not possible to put into quic favourites.\n\n3dView -> Object menu -> Right click on \"Set origin...\" -> empty menu.", "Interface. Sculpt mode, checkbox title not react to click\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: since 2.83.9, checked with version: 2.93.0\n3.0 alpha broken too\n{[F10178598](изображение.png) size=full} — here\n\n\n[2021-06-18_00-08-00.mp4](2021-06-18_00-08-00.mp4)\n" ]

[ "Addon loading failed with exception instead of the proper error\nOperating system: MacOSX 11.0.1\n\nBroken: at least since 2.80\nWorked: none\n\nIf addon contains dots in the name - it will not be loaded and fail with unclear error:\n\n\nSo I think restriction of loading an addon with version in the addon dir name is a good thing, but there should be a clear error about that to allow the user to fix the issue.\n\nOriginal issue is here: 123\n\nName any addon with dots and try to load it" ]

[ "With ThinkPad keyboards Zoom does not work with the trackpoint and middle button\nOperating system: Linux ubuntu 22.04\nGraphics card: Intel HD4600 + NVidia GT730M\n\nBroken: 3.4.1\nWorked: Works correctly until Blender version 3.3.1\n\n\nIn previous versions of blender moving the trackpoint and pressing the center button of the trackpack on thinkpad keyboards blender zooms in and out. In version 3.4.1 it no longer does. In 3.4.1 rotates the wiev. Does not work with or without 3er button emulation. In previus versions it works correctly, does zoom in and out. \n\nBased on the default startup or an attached .blend file (as simple as possible).\nStart blender move the track point while cicking the middle button on the trackpad.\nUntil blender 3.5 it does zoom, in 3.4.1 rotates the view. (I think in some alpha 3.4 it works but not in 3.4.1)", "Assigning pie menus to mouse clicks using the tweak function causes these menu shortcuts to stop working properly\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.39\n\n\nBroken: version: 2.80 (sub 71)\n\n\nBeen experimenting with creating keybinds and one of those experiments were to try and assign several menus to R click (using L click for select) by using the tweak function in the keymap settings. The idea was to have as many menus as possible on the same keybind to reduce the amount of keys needed, but using this method has proven difficult. \n\n\nWhile I can make standard menus work with tweaks, the pie menus don't work at all. If you manage to get the pie menu to show itself, it will eventually stop all the tweak commands from working unless you open up a menu on a keybind that is not using a tweak function. The second issue is that even when you do get the pie menus to show themselves, nothing can be selected on them, therefore making the keybind completely useless.\n\n\n1) Assign a standard menu and a pie menu to a mouse click (i.e. R click) using the tweak function, which can be set to north and south (just as an example).\n2) Use the new shortcuts to click and drag your mouse in the directions you assigned to to open up each menu (standard menu should be working correctly).\n3) Open the pie menu with this method and try to select any option on said menu, which should cause the pie menu to fail.\n4) Try opening the menus again, but this time none of the assigned menus will show up.\n5) To fix the previous error, open up a menu on a different shortcut (like something on your keyboard) to make the tweak shortcuts be able to appear again.\n6) Repeat the previous steps, which should cause the same error every time.", "Dead Keys failing (accented letters, double strokes)\nOperating system: Windows 10 X64 Enterprise\nGraphics card: Nvidia RTX 2070 MaxQ\n\nBroken: 2.73, 2.91.0\nWorked: Never\n\nIn a text editor window, using Unicode national characters (Greek in my case), there are accented vowels that register with two keys from the keyboard (eg: ά, έ, ό … etc).\nIf I type the 2 key sequence fast, the accent is missed, slower works. Is this a delay that can be set in Blender, or an interpreter lag that cannot be adjusted?\nActually I think it happens everywhere (not only text editor), but it’s especially nagging problem in a text window, where I may type whole paragraphs and almost each word has an accent.\n\n- In the text editor, press and hold the dead key\n- without releasing the dead key, press the key to be transformed. (this will fail)\n\nIf you release the dead key before pressing the key to be changed, it will work normally.", "3D cursor not respecting orientation setting if other tools are active.\n**System Information:**\nNA\n\n**Blender Version:**\nBroken: Blender 2.8 Beta 0f5b53ba4dc\nRetested with Blender 2.90 c880e54a95dd (2020-05-14 22:52)\n\n**Short description of error:**\nThere are a few inconsistencies with the 3D cursor in the 3D viewport. Here are the steps to reproduce.\n1. Load up Blender. For this example I will use left click select. Right click select also experiences this issue.\n2. Select the 3D cursor from the tool bar and in the tool settings change the orientation to something other than \"View\" (I'll use \"Geometry\" in my example).\n3. Switch to any other tool on the toolbar and move the 3D cursor using `Shift-RMB`. The 3D cursor will move, but it will take on the orientation of the viewport, not the set 3D cursor orientation.\n\nHere's some interesting things to note:\n\nIf the tool you have selected is \"Tweak\" (found by cycling through the \"Box select\" tool until you get to tweak), the 3D cursor orientation will respect the orientation set in the 3D cursor settings.\n\nThis is interesting because as @lichtwerk has pointed out in the comments, there are settings in the keymap panel to control this. In the keymap there are options under the section \"3D View>3D View (Global)>Set 3D cursor\" and \"3D View>Object mode>3D View Tool (tweak)>Set 3D cursor\". Both of these options default to have the orientation as \"View\" (but gray out) which is technically the cause for the behavior I saw in the original copy of this report, but for some reason, the \"tweak\" tool doesn't follow the keymap. Or both keymaps are supposed to reference the orientation set by the user (signified by the grayed out buttons in the keymap) and \"3D View (Global)>Set 3D cursor\" isn't doing that.", "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", "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.", "3D cursor sometimes can't do absolute grid snap\nOperating system: windows 10 v2004\nGraphics card: GTX 970\n\nBroken: 2.83.5\nWorked: none\n\n3D cursor sometimes can't do absolute grid snap.\nHere is the link of the bug capture. \n[Bug capture on YouTube](QzOqgiRM97c)\n\n\n\nDon't know how to reproduce from scratch, but many of my blender files has the same problem.\n[base.blend](base.blend)", "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.", "Repeat Last does not work after undo\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0\nWorked: never?\n\nSomething I stumble upon every now and then is that 'Repeat Last' (default hotkey: Shift-R) does not work after an undo call.\nThis is especially annoying if you call undo after 'Repeat Last' - which in turn makes blender forget what the last operation was.\n\nI run into this regularily while doing UV's, so lets say I have called 'align auto' and then select some new uvs - then do 'Repeat Last' and keep doing this for a bit, but at some point I will make a wrong selection and hit shift-r and undo.. now I have to first understand why Shift-R is not working anymore and then search for whatever operation I was doing, this hurts the workflow fluidity quite a bit.\n\nI know the undo area is tricky corner in the blender codebase, so I suspect some technical difficulties will make this not so easy to pull off .. or is the reason why its not working in the first place.\n\nDid a quick search here on phab but could not find an open task for this - let's ignore some tasks from 2011 ;) - so I though I just do a small post about it here.\n\n\n- Open default scene\n- Move the cube\n- {nav Edit -> Repeat last} or `Shift + R` (Works)\n- Undo \n- Perform `Repeat last` again (nothing happens)\n\nAnyways thanks for your time :) \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", "Formalize Default Selection Behavior and Key-map\nSelection should behave as consistent as possible throughout Blender. There should be a formal description for that to help avoiding inconsistencies.\n\nNOTE: This task is WIP, all content is tentative.\n\nWe *may* have to draw distinctions between right-click vs. left-click and 2D vs. 3D editors. For the latter, there are rather different requirements.\n\n### 2D Editors\n\n| Key-map item | Action\n| ---------------- | --------\n| {key Click} | Select item (and activate) an item. Deselect others.\n| {key Shift Click} | Toggle selection (and activate):\n| | * Select (and activate) if item was *not* selected\n| | * (Activate it item was selected)\n| | * Deselect item (if already active, or) if selected.\n| ... | ...\n\n\n[TODO make table per-tool?]", "When IME is On, passing key inputs excluding caret operation to IME. (Windows)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 5100 Intel 4.3.0 - Build 20.19.15.4531\n\nBroken: version: 3.0.0 Alpha\n\nIn Translation set \"Japanese\", Interface is \"checked, with input box,\nWhen IME(Roma-ji) opend input puts a first letter to input box. (ex. 「あ」->「aあ」, 「か」->「kか」)\n\n\n\nI don't know how to post my modified branch's source yet.\nSo I paste the modifed hunks.\n----\n```GHOST_SystemWin32.cpp:1222\n```\n /* passing key inputs excluding caret operation (move, select) and deleting to IME */\n if ((!ctrl_pressed && !alt_pressed) &&\n (raw.data.keyboard.VKey != VK_BACK\n && raw.data.keyboard.VKey != VK_RETURN\n && raw.data.keyboard.VKey != VK_SHIFT\n && raw.data.keyboard.VKey != VK_CONTROL\n && raw.data.keyboard.VKey != VK_ESCAPE\n && raw.data.keyboard.VKey != VK_END\n && raw.data.keyboard.VKey != VK_HOME\n && raw.data.keyboard.VKey != VK_LEFT\n && raw.data.keyboard.VKey != VK_UP\n && raw.data.keyboard.VKey != VK_RIGHT\n && raw.data.keyboard.VKey != VK_DOWN\n && raw.data.keyboard.VKey != VK_DELETE)) {\n if (window->getImeInput()->GetOpenStatus(window->getHWND())) {\n return NULL;\n }\n }\n```\n```\n```\nGHOST_ImeWin32.h:271\n/* Retrieve the open status of IMM. */\nbool GetOpenStatus(HWND window_handle);\n```\n```\nGHOST_ImeWin32.cpp:385\nbool GHOST_ImeWin32::GetOpenStatus(HWND window_handle)\n{\n```\nbool result = false;\nHIMC imm_context = ::ImmGetContext(window_handle);\nif (imm_context) {\n result = ::ImmGetOpenStatus(imm_context);\n}\nreturn result;\n```\n}\n```\n----\n", "Select next active fails in some cases (default cylinder, cube)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro K2100M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 3.1.2\n\nWhen adding object: circle or cylinder, when selecting vertices, it does not select the next vertex at command: shif + ctrl + (+).\nif I select several vertices manually and give the command: shift + ctrl + (-) deselect, it works perfectly.\n\nany other option works, works well with other objects, sphere, monkey sesame, the circle object works if you select two consecutive vertices, if you select one vertex yes one no, it no longer works. .]\n\n- add cylinder object\n- Edit mode\n- Select 2 vertices then {key shift ctrl +}\n\n[2022-05-24 19-58-17.mp4](2022-05-24_19-58-17.mp4)", "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", "NLA: Animated Influence/Time Property Sliders Unresponsive\nTask: #76549 (NLA Strip influence slider doesn't respond to autokey correctly.)\n\n**Source of Problem**: (anim_sys.c) *nlastrip_evaluate_controls() -> animsys_evaluate_fcurves()*: I believe the issue is due to NLA evaluation, where the animated strip properties are evaluated and flushed at the same time the action strip channels are evaluated. Since autokeying doesn't insert a keyframe as the value changes, that's probably why the slider is unresponsive. \n\n**Solution**: Perhaps we should separate (despgraph-wise) NLA strip animated property evaluation from when we evaluate the NLA system for general animation? Animated strip properties would only be evaluated and flushed on frame change or when the whole frame needs refreshed. Then normal non-NLA animation evaluation will just read the strip properties as is. This would allow the slider be responsive. It also allows the user to change these properties and view their changes without having to keyframe, just like any other Blender animated property. \n\n**Potential Problems with Solution:** What do we do when strip influence is animated and the user changes it (without keying) then inserts keys on character bones. When we remap the keyframes, should we re-evaluate and use the strip's animated influence? Or should the new keys be remapped using the unkeyed strip time?" ]

[ "Pen Shortcuts(pan, rotate, grab...) doesn't work in 3D view \nOperating system: Windows 10 64bits\nGraphics card: GTX 1070 Ti\n\n**blender-2.83-85de07e64c96-windows64**\nBroken: (blender-2.83-85de07e64c96-windows64, master, 2020-04-11, on 3D viewport)\nWorked: around 5 or 6 versions ago\n\n\nPen Shortcuts(pan, rotate, grab...) doesn't work in 3D view since few updates ago in blender 2.83 alpha. If I change the tablet API method from automatic to windows Ink, It's come back to work, but, without pen pressure. On Blender 2.82a is working pretty well.\n\njust for your information, I'm using Huion GT 133 as display tablet.\n\nthanks for your attention", "Mouse clicks no longer work for a Huion Tablet\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.13\n\nBroken: version: 2.83 (sub 13) \n(also did not work in builds from 9th & 10th - have not tested builds inbetween 4th & 9th)\nWorked: 2.83 (sub 11) (and all prior versions)\n\nUsing a Huion Kamvas GT-156HD v2 tablet with Blender. In recent builds, Blender does not respond to stylus (mouse) clicks - either screen taps or stylus buttons. Can move the cursor, but cannot select, orbit etc because the click is not acknowledged. Build responds fine to the actual mouse. Tablet continues to work as expected in all builds tested from 04/04 back (including 2.82a).\n\nOpen Blender default scene - attempt to select cube with Huion stylus. Cursor moves but no clicks are acknowledged by Blender.\n\n", "Wacom tablet's side switches don't work\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.19\n\nBroken: version: 2.83 (sub 13)\nWorked: version: 2.83 (sub 11)\n\nSome side switches of the tablet don't work while a pen is hovering above the surface of the tablet.\nIf you stop hovering the pen over the tablet, the side switches become to work.\n\n**Tablet**\nWacom Driver Version 5.3.5-3\nModel: CTH-460\n\n1) Assign a side switch to the middle click.\n2) Hover the pen over the tablet.\n3) Press the side switch and try to rotate a viewport by moving the pen. This doesn't work.\n\n1) Keep the pen away from the tablet.\n2) Press the side switch.\n3) Move a cursor by using a mouse. In this case, I can rotate a viewport." ]

[ "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "NLA: Animated Influence/Time Property Sliders Unresponsive\nTask: #76549 (NLA Strip influence slider doesn't respond to autokey correctly.)\n\n**Source of Problem**: (anim_sys.c) *nlastrip_evaluate_controls() -> animsys_evaluate_fcurves()*: I believe the issue is due to NLA evaluation, where the animated strip properties are evaluated and flushed at the same time the action strip channels are evaluated. Since autokeying doesn't insert a keyframe as the value changes, that's probably why the slider is unresponsive. \n\n**Solution**: Perhaps we should separate (despgraph-wise) NLA strip animated property evaluation from when we evaluate the NLA system for general animation? Animated strip properties would only be evaluated and flushed on frame change or when the whole frame needs refreshed. Then normal non-NLA animation evaluation will just read the strip properties as is. This would allow the slider be responsive. It also allows the user to change these properties and view their changes without having to keyframe, just like any other Blender animated property. \n\n**Potential Problems with Solution:** What do we do when strip influence is animated and the user changes it (without keying) then inserts keys on character bones. When we remap the keyframes, should we re-evaluate and use the strip's animated influence? Or should the new keys be remapped using the unkeyed strip time?", "Region Overlap does not work on VSE editors\nOperating system:\t\tWindows 7\nGPU:\t\t\t\tRadeon Vega 64\nGPU Software Version:\t20.4.2 (2020.0515.1537.28108)\nCPU:\t\t\t\tIntel Core i7-5960X\n\n**Blender Version(s)**\n*(listed are versions tested)*\n\nWorking:\t\t\t\t`2.79 (sub 00), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68b, type: Release, build date: 2018-03-22, 09:59 AM`\nBroken:\t\t\t\t` 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: Release, build date: 2019-07-29, 09:44 AM`\nBroken:\t\t\t\t` 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: 26bd5ebd42e3, type: Release, build date: 2019-11-20, 16:33:00`\nBroken:\t\t\t\t` 2.82 (sub 07), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd76f, type: Release, build date: 2020-02-13, 01:56:46`\nBroken:\t\t\t\t` 2.83.3 LTS, branch: master, commit date: 2020-07-22 06:01, hash: 353e5bd7493e, type: Release, build date: 2020-07-22, 04:04:56`\nBroken:\t\t\t\t` blender-2.90.0-4f59e4bddcb0-windows64` (BF Build Bot)\nBroken:\t\t\t\t` blender-2.91.0-21fec9513969-windows64` (BF Build Bot)\n\n\n|  |  |\n| -- | -- |\n\n\n[No Overlap.blend](No_Overlap.blend)", "Proposal: improve functionality of Randomise Transform\nI personally find the way Randomise Transform works to be a bit confusing. The problem goes for all modes (location, rotation, scale) but it is most noticeable when randomising scale.\n\nIf I understand it correctly, setting the number to 1.15 would set the boundaries for the randomisation to 0.85 - 1.15, which is not very clear in this UI. It gets worse when I set it to a number below 1 - is it still the maximum? What's the minimum then?\n\nI would like to propose the following design for this: work with actual, defined boundaries - minimum and maximum values.\n\n\n*Though it's not really a huge issue in the location and rotation modes, I would extend it there for consistency.*\n\nWhile not exactly easier on the eyes than the current UI, I feel this offers more control and predictability than using one number that the user has to imagine going in both directions of the axis. And when scaling, no-idea-where.", "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`", "VSE: Animation operators missing cache invalidation\nOperating system: Linux Mint 19.1\nGraphics card: GTX 980\n\nBroken: blender-3.1.0-alpha+master.c34ea3323a3a-linux.x86_64\n\nRemove created action from NLA editor, this will still animate VSE elements\nSome weird VSE action cache?\n\n- Add any image to VSE strip\n- Set Rotation=0 at first frame and Rotation=220 for some another frame. It's rotating now, right?\n- Go to NLA tab -> push down Scene Action and remove it. Thus, we don't have any actions in our project but the image is still rotating. Why?\nAfter rebooting blender app the magick will gone. Is this a bug?\n\nThis has quite broad reach as all of these (if not more) dont invalidate the cache:\n- clearing keyframes\n- deleting actions\n- removing drivers\n- removing dopsheet channels\n- removing graph editor channels\n- removing nla tracks\n- removing nla strips\n- removing fcurve modifiers\n\n\n", "Operator macros [e.g. ARMATURE_OT_duplicate_move] have non-functional 'Proportional editing' option in Adjust Last Operation panel\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nDuplicating a bone in edit mode. In the Adjust Last Operation panel there is a proportional edit checkbox. Which can't be activated.\n\n\nOpen Blender\nCreate armature\nSwitch to Edit Mode\nDuplicate the bone\nIn Adjust Last Operation panel try to activate Proportional editing.\n\n\n\n", "Video Editor Scene Strips and scene camera binds are out of sync (most of the time)\nBroken: blender-2.80.0-git.03bd024c077d-windows64\n\nThis is a re-do of another other bug report I filed earlier this month (#63304), now that I understand it a lot better I'm filing it again with a more accurate description and demo file.\n\nIn the video editor, if you one or many scene strips, on updating the frame the camera bind that the playhead falls under will most likely not be applied until the following frame.\nSo, when you place the playhead in a region that uses a different camera bind, it usually does not update unless you update once more in that same region.\nThis is also the case in rendering animations using the video editor.\n\nI've created a demo file that perfectly illustrates this problem below.\nThis bug urgently needs fixing.\n\n**Exact steps for others to reproduce the error**[sequence camera bind bug.blend](sequence_camera_bind_bug.blend)\nInstructions for demo:\n\nIf the playhead is in the BOX region, it should show a box, if it is in the SPHERE region, it should show a sphere. I estimate about 80-90% of the time it doesn't update correctly. Why there is an element of chance I cannot work out.\n\nTry moving the playhead around between markers (which indicate a camera bind in the strip's scene) and notice how the bind almost always fails to apply.\n\nNow try jumping from region to region and notice how the camera bind is almost always 1 step behind, so it is never applied, place the playhead within the current region and it updates without fail.", "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", "Move To Line Begin and Reset View operators in the console editor conflict when pressing Home key\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\n\nIn the python console editor, both the Move To Line Begin and the Reset View operators have the same shortcut \"Home\", so it is not possible to invoke the Move To Line Begin operator.", "VSE: 'Reverse Frames' is reversing the source input and not the strip \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.90.1\n\n'Reverse Frames' is reversing the source input and not the strip.\n{[F9358967](Reverse_Frames.gif), size=full} \n\nDownload this file with a counter video included:\n[Reverse_Frames_bug.blend](Reverse_Frames_bug.blend)\nNotice that the video is counting up from zero to 4 sec. \nSplit the movie strip at 2 sec.\nSelect left side.\nCheck Reverse Frames for the left side strip.\nIt is now counting down from 4 sec to 2 sec.\nIt should count from 2 sec to zero sec. \n\nSo, currently this is not a Strip setting, but a Source setting. Question is if this should be moved into the Source panel or be properly implemented as a strip setting?\n\nBtw. the function `Strobe`, which is repeating frames, but keeping sync, has the wrong name: strobe \nWhen doing this process on celluloid-film-stock the this process is called \"Step Printing\": step_printing/\n\n", "Splitting strips will change image output\nOperating system: Windows 8\nGraphics card: 550Ti\n\nBlender Version\nBroken: 2.93.0 Beta\nWorked: Not sure\n\nSplitting strips with \"hard\" method will change image output.\n\nAdd movie or image sequence to VSE\nSplit strip by pressing Shift + K\n\nImage will change\n\n", "Multiple Frame Rates/ Playback/ VSE scene strips\nOperating system: windows 10\nGraphics card: rtx 2060\n\nBroken: 2.90.0\nWorked: Never\n\nI'm using the VSE and I have 2 scene strips from two different scenes inside the VSE.\nThe first scene strip references a scene that is set to 12 FPS.\nThe second scene strip references a scene that is set to 24 FPS.\nThe 3rd scene is where I'm using the VSE, and this scene is set to 12 FPS.\n\nThe problem is, all the scene strips are playing back at 12 FPS by default in the scene where I'm using the VSE. In other words, the scene that is 24 FPS is playing back at 12 FPS.\nIf I'm not mistaken, this wouldn't happen with real footage. Two recordings with two different FPS dropped into a project would play back at different speeds.\nWhat I'm trying to do is have a video at 12 fps, and the put a 24 fps scene strip in the VSE so that i can put it in slow motion and have it play back with the same quality. \n\n- Open attached file\n- Run VSE\nNote that the cube shown on each strip has the same speed in the animation.\nIt was expected that one was twice as fast than the other.\n[_VSE scene strips.blend](_VSE_scene_strips.blend)", "Wrong status bar keymap for release confirms and right click select\nOperating system: Manjaro x64\nGraphics card: HD5770\n\nBroken:\n2.80, 81ea815dcb6, blender2.8, 2018-12-12\nWorked: 2.79b\n\nWhen grabbing something(object, vertex, etc) by right clicking on it and then releasing/clicking on the same button the action is not performed, object doesn't return to its initial position. \nHowever if you use G or a Tool to grab instead of mice click Cancel by Right clicking option works.\n\nRight click on a Cube(in 2.79 thats enough to start moving an object but not here here you have to hold the button) AND HOLD the button\nDrag mice somewhere to move the Cube\nRight Click again to Cancel movement\nNothing happens.\n[blender_bug-2018-12-13_22.18.53.mkv](blender_bug-2018-12-13_22.18.53.mkv)\nI'm also attaching video file for it to be more clear.", "Motion Pasths: \"Clear Motion Paths\" default to \"only selected\"\nProblem: \nAs with \"calculating\" motion paths you expect the clear motion paths function to default to the one selected, In the same way you create Keyframe the selected objects. The default deletes all motion paths in scene and wanting to clear one motion path is more common than wanting to clear them all.\n\nSolution:\nChanging the default of clear motion paths to \"clear motion path\" and turn \"Only Selected\" to default." ]

[ "Video editor: Anim de-sync when pushing a strip onto another\nOperating system: Linux Mint 17.3\n\nBroken: 2.81 a\n\nVideo editor: Pushing a strip to another (in order to place together) for a while moves the animation keys of other linked ones\n\nCreate a strip A in the video editor\nThen another B, for example: B is an image\nCreate a \"Transform\" strip C for B, and animate it. The image moves, it works.\nThen move the B strip (C follows B) and push it to A: you want to locate it next to A, to the right. It becomes red as you do. You can be seeing the animation curve as doing. Look: as you push left, it goes farther more and more.\nNow strips B and C are at the desired place, both animation curve (C's) has been moving as you pushed, and it's out of time." ]

[ "Bevel Improvements\nBlender users have many desires for improvements to the Bevel tool and Modifier. This task is for exploring priorities for implementing those, as well as designs for doing so.\n\n**Some current TODOs and feature requests**\n\n* generalize to handle several manifold sheets touching at a point (see #34678).\n* improve clamping code (see #38871).\n* more options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n* treat more cases like \"pipe\" to avoid bulges (see #40258)\n* option to have bevel not create n-gons (see bf-funboard thread)\n* sometimes leaves degenerate geometry (#48174)\n* tapered bevel influence by vertex weight - see bevel-modifier-influenced-by-vertex-weight. Also #62739 where method isn't suggested -- could also let user set different widths at the two ends of a bevel.\n* merging of vertices that coincide after beveling (#61214)\n* better way of specifying vertices in modifier, and even better, a way of specifying edges (#62649) (edge group?)\n* bevel-after-booleans\n* option to make vertex group out of all vertices created in bevel\n* method to have bevel modifier affect curve objects\n* have angle limit method available in tool (as is already in modifier)\n* have clamp be local rather than global (or in addition to global?)\n* \"support loop\" option - extra loop of edges flat on adjacent faces\n* use bevel-like code to add new option to extrude (edge, vertex) that keeps geometry manifold (billrey idea in GSoC 2018 thread)\n* vertex mesh that has the effect of booleaning the edge profiles to have the effect of real-world material removal\n* profile superellipse arc should not use quarter-ellipse arc always, but rather rather the segment that hits adjacent faces tangentwise\n* beveling a face as an option in addition to beveling edges and vertices (starts to look like inset)\n* width method like Percent but where absolute distance along adjacent edges is equal to spec instead of percentage\n* option to round the terminal edge triangle\n* special case segments=2, profile=1 case to avoid diagonal edges on cube corners when smaller and large widths mixed\n\n\nFollowing comments will have some initial explorations of the problems and designs for solving each of these.\n\n", "Error \"NotImplementedError: bevel: keyword \"custom_profile\" type 4 not working yet!\" when attempting to use custom_profile keyword in bmesh.ops.bevel\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.1.2\nWorked: No previous working version known\n\nTried to call bmesh.ops.bevel with custom_profile keyword argument. Got \"NotImplementedError: bevel: keyword \"custom_profile\" type 4 not working yet!\" error.\n\n\nOpen the attached blend file.\nGo to the Scripting workspace\nCopy the text in the Text editor\nPaste it to the python console.\n[bmesh bevel bug.blend](bmesh_bevel_bug.blend)", "Adding new hook while in Edit mode breaks when trying to undo/redo the operator\nWin7 (32bit)\n\nBroken: 2.78a\n\n\n- Add Path from Curve menu, add new Armature\n- Assign Bone to control point as Hook\n- Blank Hook modifier appears along with real one\n\nScreencast: [screencast0001-0250.mp4](screencast0001-0250.mp4)\n", "Edges created by a bevel modifier are visible even for hidden items in edit mode (in wireframe display)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I did not follow it back to n previous versions.\nThe Problem is also reproducable in the latest nightly e362a2f0d41f\n\n\nIn mesh editting mode, if you hide an edge that is affected by a bevel modifier, the edges created by the bevel modifier are still visible. I expect them not to be visible because the edge is hidden.\n\n\n1. Open the attached file.\n2. There is one mesh in edit mode. One of the edges is affected by a bevel modifier.\n3. One face is already selected. Press Shift+H to hide all unselected items, including the aformentioned edge.\n4. You still see the result of the bevel modifier even if the edge is hidden. I expect it not to be visible. \n\nIn practice, this caused many confusing \"ghost\" lines of invisible items.\n\n", "Wrong SubSurf modifier results with inconsistent normals\nOperating system: Windows 10 Enterprise Version 1803\nGraphics card: 2 x GTX1080 ti\n\nBroken:\nblender2.8, 2018-12-05\n\nFrom latest builds subsurf modifier make a wrong subdivision of geometry as displayed in the attached files.\nBefore 18/20 November the behaviour of subsurf modifier was ok.\nI am sure because I did an animation on that date and the subdivided vase was ok.\n\nBest regards,\n\nUmberto\n\n\n\n\n\n[ceramic.blend](ceramic.blend)", "Missing UV Islands / Image Editor / Some generative modifiers (bevel, skin, triangulate, wireframe)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro M2200/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIf geometry has the Bevel Modifier applied and the Realtime Display is on, the UV islands do no display in the Image Editor.\nIf you turn off the Realtime display (Display in Viewport) and then adjust the view in the Image Editor, the UV Islands will appear.\nIf you turn On the Realtime display and then adjust the view in the Image Editor, the UV Islands will vanish.\nYou can still paint in the Texture paint on the geometry and it will appear in the Image Editor.\n\nCreate a Cube\nAssign a Bevel Modifier - turn Realtime display ON (for me it is on by default)\nSet interface to Texture Paint mode.\nThere will by no UV Islands displayed in the Image editor\n\n[UV_Island_Bevel.blend](UV_Island_Bevel.blend)\n\n\n\n", "unable to use 'grid fill' or 'fill' on screwed object\nOperating system: Window 10\nGraphics card: NVIDIA GeForce RTX 2060 SUPER\n\nBroken: Blender 2.83\nWorked: Blender 2.76 \n\n\nI am trying to create a solid spring using Screw modifier. After applied grid fill, I expected a full capped end of the screwed object, but it turns out to be like figure below. The complete file also attached in this post. Hope to get your response soon. \n\n[screw.blend](screw.blend)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Front Faces sometimes doesn't work with the Mask tool\nOperating system:\nGraphics card:\n\n3.5.0 beta 24/2/2023\n\n**lasso mask brush mask outside the border when symmetry enable**\n\nThe same as #103163 but in a more extreme case\n\n- Open attached .blend file\n- (optionally) Disable `X axis` mirror\n- Use Lasso or Box Mask tool in the region indicated\n\n[untitled.blend](https://projects.blender.orgattachment)\n", "Sporadic boolean issues\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.2.0\nWorked: 3.0\n\nMeshes using the boolean modifier sporadically break in Blender 3.2.0, while they still worked in 3.0.\nThis would result in meshes that lack faces or even crash Blender\n\n\nUnfortunately I wasn't able to isolate the cause of the issue, as it seems to occur sporadically and randomly. What I have noticed is that sometimes meshes that were fine suddenly break once you enter exit edit mode.\n\n", "Generative modifiers (solidify, mirror) draw face normals from original face (wrong direction)\n@Baszczer information\nOperating system: Ubuntu 20.04\nGraphics card: Radeon Pro WX 7100\n\n@Alaska information\nOperating system: Linux-5.4.0-7629-generic-x86_64-with-debian-bullseye\nGraphics card: GTX 1050Ti 440.82\n\nBroken: 2.83 (2020-05-26 22:42) `f772a4b8fa`, 2.90 (2020-05-26 20:02) `eb5422828a`\nWorked: 2.82a\n\n**Short description of error:**\nThe viewpoint overlay for displaying faces normals in edit mode for faces that are part of a solidify modifier will always point in the direction of the face normal being solidified with Blender 2.83 and 2.90.\n\n\n2.82a\n\n\n2.83/2.90\n\n**Exact steps for others to reproduce the error:**\n1. Open Blender.\n2. Add a plane.\n3. Give the plane a solidify modifier.\n4. In the modifier panel, enable the \"On cage\" option for the solidify modifier.\n5. Enter edit mode on the plane. \n6. In the viewport overlays enable the \"Display normals\" option for faces. \n\n[#77090 - Solidify Normals.blend](T77090_-_Solidify_Normals.blend)\n\nIn 2.82a, this will be have as expected. The normal lines will be perpendicular to the faces of the solidifies plane. In 2.83, all the normal lines align with the normal line of the face being solidified.\n\nVideo because I feel like I'm having a hard time explaining this in words:\n[2020-05-27 22-55-31.mp4](2020-05-27_22-55-31.mp4)", "Material glitches at joints when using Bevel modifier\nOperating system: Ubuntu 20.04.3 LTS\nGraphics card: GeForce RTX 2060\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\nWorked:\n\n\nI know people experience no end of unexpected Bevel behavior due to issues with their geometry. But I think this is a genuine bug - as do people who responded to my Blender SE question: 124535\n\nRobin Betts commented there that \"it looks like a bug. But at least a consistent, and therefore traceable bug. It seems to be in the 'Automatic' (-1) material offset setting, which should split the bevel down the middle at material boundaries. It's getting the boundary 1-off at the end of a patch/arc spread of faces.\"\n\nAt joints where two materials meet, the Bevel modifier seems to miscalculate which faces of the bevel should contain one material and which the other, as shown here:\n\n\n\nIf I apply the modifier, I can then correct the issue by hand.\n\nThe above picture is from Blender 3.1.2. The problem seems to have been there for a long time, things look different but are still incorrect in 2.93.7:\n\n\n\nThe complete mesh is fairly simple (I cut it out of a larger object for this bug report) and I've confirmed there are no overlapping vertices etc.:\n\n\n\nI actually started with a much simpler mesh but converted to triangles to ensure the issue wasn't somehow n-gon related (it isn't):\n\n\n\n\nCreate a simple shape like the one shown in the last image above and use two different materials for your object, e.g. above, I've applied one material to the darker colored faces and the other to the lighter colored faces.\n\nThen apply a *Bevel* modifier and then look at the object in a *Viewport Shading* mode that shows materials, e.g. *Material Preview* or *Rendered* (you can even see the issue with *Solid* viewport shading if you set the *Viewport Display* for one of the materials to be a different color to the default grey).\n\nHere are two small `.blend` files - the first created in Blender 3.1.2 and the second in Blender 2.93.7:\n\n[bevel-3.1.2.blend](bevel-3.1.2.blend)\n\n[bevel-2.93.7.blend](bevel-2.93.7.blend)\n\nYou can find a larger `.blend` file containing the original full mesh in my Blender SE question: 124535", "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 ", "Bevel profile incorrect when using arc for inner miter\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.3.0 Alpha\n\nThe Bevel operation and modifier has an incorrect profile when the inner miter is set to arc and the profile value is either very high or low.\nthis happens in both edge bevel and vertex bevel mode.\n\n|Inner miter sharp (Ok):\n|---\n|\n\n|Inner miter arc:| \n|---|---\n||\n|Shape 0.93|Shape 0.5\nIn this case the Bevel kind of overshoots.\n\nProbably related to #95916 (Pinching effect when using bevel and bevel modifier).\n\n- Open attached .blend file\n[Test.blend](Test.blend)\n\nThank you and have a great day!\n\n---\nUPDATE:\nIn some cases it can also happen with Inner Miter Sharp (#105064)\n", " EXCEPTION_ACCESS_VIOLATION when entering Edit Mode\nOperating system: Windows 10 1903 (18362.239)\nGraphics card: Intel HD Graphics 4000\n\n***Broken:***\nBlender 2.80 (sub 75) / 2019-07-29 09:44 AM Windows / Stable\nBlender 2.81 (sub 1), branch: master, commit date: 2019-08-13 11:31, hash: 6f9cbbc8ec4f\n***Worked:***\nBlender 2.79 (copied mesh over through copybuffer.blend)\n\n\nWhen entering edit mode of a specific object Blender crashes with EXCEPTION_ACCESS_VIOLATION. Logs and example .blend provided.\n\nThe issue shouldn't be in my GPU, since the same issue persists even with Software Rendering.\n\n1. Open up example file\n[window_broken.blend](window_broken.blend)\n\n2. Select `window_panes` and enter Edit Mode\n3. Get EXCEPTION_ACCESS_VIOLATION\n\n**Logs (2.80 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n\n**Logs (2.81 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "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)" ]

[ "Bevel modifier does not bevel: Edge Data - Mean Bevel Weight\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GT 750M\n\nBroken: 2.80 Beta, 2018-12-05 02:05, hash: 1fa527bfa3a (64 bit)\nWorked: (optional)\n\nBevel modifier doesn't bevel edge data mean bevel weight.\n\n- Scene included a mesh called: Knife HP, select that\n- go into edit mode and see the edges that contain Mean Bevel Weight: 1.0\n- check the modifier added to the mesh, which is the bevel modifier\n- Limit Method: Weight\n\nWith the bove settings it should show a bevel, but whatever I chance it won't bevel the Edge Data. When I set Limit Method to Angle, I can see the bevel work but all over my mesh. Looks like the bevel modifier doesn't take Mean Bevel Weight into account.\n\n[combat knife_001.blend](combat_knife_001.blend)" ]

[ "Color Attribute not affecting \"bump\" shader node\nOperating system: Windows 10\nGraphics card: RTX 3080\n\nBroken: 3.50 beta (03 March 23)\n\nUsing a mesh's color attribute as an input to the \"bump\" shader node does not result in the expected behavior. Using the color attribute for practically every other value (including the normal map node, roughness, metalness etc.) works as expected.\n\nCreate a mesh and paint a color attribute with, for example, a black-and-white pattern.\nGive the mesh a material and add the color attribute.\nPlug the color attribute into the \"height\" input of the bump node, and view the result. There is no difference compared to the \"height\" input being left disconnected.\n\nOther inputs (such as a noise texture) result in the expected behavior.\n\n", "Add modifier error message for attribute name clashes\nIf user has a UV and a vertex color groups with the same name things behave in non predictable ways.\n\nThe nodes modifier should check for this and add an error message when this happens.", "Wrong property changing `matrix_world` and destructive undo via RMB.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken:\nversion: 3.6.1\nversion: 4.0.0 Alpha\nWorked: never\n\nReturning to the original state during editing (or canceling) does not give the result that was when editing was started.\n<video src=\"attachment\" title=\"2023-08-16 21-40-53.mp4\" controls></video>\n\n1. Copy script and run\n```python\nimport bpy\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Test Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n col = self.layout.column()\n ob = context.object\n col.prop(ob,'name')\n col.prop(ob,'matrix_world')\n\nif __name__==\"__main__\":\n bpy.utils.register_class(Panel)\n```\n2. Quickly change the scale value for the object matrix.\n3. Press Right mouse button.\n\n", "Cycles: Persistent Data option corrupt geometry nodes instance meshes with changed normals\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.61\n\nBroken: version: 3.6.1\n\nThe instance mesh changes if render cycles use persistent data.\n\n1. Open attached file.\n2. Render few frame.\n\n", "Undo doesn't consider changes in nodetree when object is in edit and texture paint mode\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.79-3.4\n\nFor reference: this is due to this commit 4a08b974f4\nFrom the commit message:\n\"don't store undo steps for property changes in paint & edit modes.\"\n\nWhen in edit and texture paint mode, I can't undo changes, that I made in the shader editor. \n\n\n - Open .blend\n - Move some verts.\n - Change a shader node setting.\n - Press {key Ctrl Z}.\n # The verts move back, but the node setting remains.\n[#71895-undo-not-undoing-shader-nodes.blend](T71895-undo-not-undoing-shader-nodes.blend)", "Move function for creating id properties for node group inputs to blenkernel\nCurrently, we are doing a bad level call to `MOD_nodes_update_interface` in blenkernel. To remove this call @mont29 and me decided to add a new function in `node.c` that takes a node group and id property group as input, and creates id properties for the node group inputs.\n\nI intend to work on this after the id property refactor by @HooglyBoogly is done.", "EEVEE/Cycles discrepancy in how image texture node's alpha is managed.\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 511.79\n\nBroken: version: 3.2.0 Alpha\nWorked: ?\n\nWorkbench and EEVEE perform an unpremultipy calculation when premultiplied alpha mode is selected and the image texture node's alpha socket has a connection.\nWorkbench and EEVEE ignore the image alpha when straight alpha mode is selected and the image texture node's alpha socket has a connection.\nSee: [node_shader_tex_image cc](node_shader_tex_image.cc$125-153)\n\nIn Cycles, there is no apparent difference between the straight and premultiplied alpha modes and the alpha socket's connection status does not change how the alpha is managed.\nSee:\n[shader_nodes cpp](shader_nodes.cpp$200-250)\n[image cpp](image.cpp$471-566)\n[image_oiio cpp](image_oiio.cpp$154-204)\n\nExample:\n\nExample 2:\n\n\n**Test File**\n[Alpha_Image_Test_3.1.0.blend](Alpha_Image_Test_3.1.0.blend)\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", "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", "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", "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)", "Simulation Nodes: bake UI in simulation node\n_No response_\n\n", "Shader node connections in v3.0 file broken in v3.3\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.3.0\nWorked: 3.0\n\nRendering in 3.3 a file created in 3.0 (using both Cycles & Eevee) showed major differences from rendering made in 3.0. Investigation showed that critical node connections in multiple shader trees were broken when opening file in 3.3. Unable to determine if broken connections are consistent in terms of node type. Which nodes have broken connections seems consistent from file to file using the same shaders -- sample .blend was constructed with shaders used in file where bug was first observed. All shaders were originally created in versions prior to 3.0 but later than 2.80.\n\nAttached GIMP .xcf file has exemplary renderings and explanatory screenshots from file where bug was first identified. Sample .blend file was created in v3.0 using shaders from this file. Bug does occur in other files which render fine in 3.0 but have broken shaders in 3.3\n\n\n[REVISED sample file 300.blend](REVISED_sample_file_300.blend)\n\nOpen \"sample file 300.blend\" in v3.0 and inspect shader trees. Open in 3.3 and inspect shader trees, some nodes of which are now disconnected. \n\n\n", "Copypasting material is broken for `NodeCustomGroup` nodes\nOperating system: Linux-5.0.0-37-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nWhen copying+pasting material:\n\n - method `copy` is called twice, which produce undesireble results. \n```\n when copying for 'copy' operation it is called on unlinked nodetree inside buffer\n```\n - user counter of trees of containing nodes are messed up: source node get decremented counter\n\nAsan use after free [T72579_asan_use_after_free.txt](T72579_asan_use_after_free.txt)\n\n - load attached file and execute embedded script\n - it registers 2 custom nodes and adds them to first material\n```\n node trees created: 'foo' (1 user), 'bar' (1 user) \n```\n - select first slot in material list and call 'copy' from specials menu\n - select second slot and call `paste`\n\nThis expected to produce: \n - 'foo' (2 users, both materials)\n - 'bar' (1 user, material1) detached from pasted node in `copy` api call\n - 'bar.dup' (1 user, material2), created from inside `copy` api call\n\nInstead: \n - 'foo' (1 user, used in both materials), copypasting did not increment users (or incremented and then decremented)\n - 'bar' (0 users, used in material1), copypasting decremented source users\n - 'bar.dup' (0 users), created in first api `copy` call\n - 'bar.dup.001' (1 user, used in material2), created in second api `copy` call\n\n[test_mat_copypaste.blend](test_mat_copypaste.blend)\n\nThis case is covered by autotests submitted: D6420\nThe issue with api calls is fixed by D6450 \nBut the counter issue remains.", "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)" ]

[ "Node Editor - invisible and disappering connections\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n2.80\n\nIn Node Editor there is a problem with connection lines: they are not shown or disappear when reconnecting other nodes\n\n\nThis problem appears when Blender uses non-default user startup file, as I have investigated so far.\nCause even after Load defaults then Save config and reopen Blender ( it starts with my startup file ) does not solve this problem.\nI think that is something not right if user have to rebuild his workplace from scratch every time when software is updated.\nPlease investigate this case. Thank you.\n\n[MyStartup.blend](MyStartup.blend)\n\n[2019-09-26_12-41-23.mp4](2019-09-26_12-41-23.mp4)\n\n\n\n\n\n\n\n", "Communication (line) between nodes not displayed\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\ncommunication (line) between nodes not displayed\n\n\nalso sometimes the visibility of some links disappears in response to the update of others\nNOXpLlHXfmI\n\nJust connect the node to node on the editor shader\nno problem in the blender version \"Broken: version: 2.81 (sub 11)\"\n\n\nsorry for my english, i partially use google translator", "Node link is hidden when working in the shader editor\nOperating system: Linux-5.3.0-arch1-1-ARCH-x86_64-with-arch-Arch-Linux 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.81 (sub 12)\n\nThe error appears to start from commit ce34a6b0d727bbde6ae373afa8ec6c42bc8980ce\n\nA single link between nodes is not drawn when working with the nodes and a 3D editor visible. Selecting or deselecting the object in the 3D editor makes the line appear or disappear.\nFound that this only occurs when the 'floor' and world axes overlays are disabled in the 3D view (but not /all/ overlays disabled). Otherwise it works as normal.\n\nFrom the default scene, switch to the Shading workspace tab.\nIn the shader editor, the line connecting the principled node and the output should already be hidden.\nRe-selecting the default cube makes it reappear.\nSelecting the principled node makes it disappear.\nAdding new nodes and new links will show it is only one link being hidden.\n\"Reconnect\" the hidden link and one of the others will disappear.", "Disappearing connections in Node Editor\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nSince from 17.09.19 daily build, some connections in node editor begin to disappear. But still, nodes stay connected, connection just becomes invisible. Sometimes It randomly disappears when selecting different meshes, sometimes when trying to make new collections.\n\nVideo with an issue demonstration:\nyyND11xPaqFnvQ\n\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)", "Disabling Collections in the Outliner filters overlaps the Mode Column icons with the expansion arrows\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.4.0 Alpha\n\nIf you disable the \"Collections\" filter in the Outliner, the space of the Mode Column disappears even if the \"Show Mode Column\" filter is enabled, and the icons of the Edit Mode Column overlap with the object expansion arrows.\n\nAdd any mesh object, disable the Collections filter in the Outliner, enter edit mode.\n", "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)", "Add \"Link (Library Override)\" option when dragging assets into the scene\nAs a user, I want to be able to drag an object asset into a scene and have it have the following properties:\n\n1. The data block is not copied into the new scene, it should be linked.\n2. The underlying *data block* cannot be edited (i.e., you cannot go into edit mode on a mesh object)\n3. The new object should be able to be modified (i.e., translating, scaling, rotating etc.)\n\nThis is not possible with [the options provided](asset_browser.html#using-assets) at the moment.\n\nI propose that a new option be added, called **Link (Library Override)**.\n\nThis would essentially be the same as using \"Link\", followed by calling the \"Make Library Override\" operator on the linked object.", "Unable to fix broken linked IDs when renamed in libfile\nWindows 10\nWindows 7 x64\n\nWorked: 2.82\nBroken: 2.83.0\n\nCant rename linked collection. Error: Cannot edit external library data\n\nDefault Blender setup (first file lets call it assets.blend)\nCreate a collection and name it \"Test\" \nCreate a cube and move it to \"Test\" collection\nSave the file\n\nCreate another file (lets call it level.blend)\nLink the \"test\" collection from the assets.blend\nCheck all linking options before hiting link\nSave the file\n\nNow open assets.blend again and rename \"Test\" collection to \"Cube\"\nAnd save it again.\n\nOpen level.blend\nA message appears that link is broken\nGo to Outliner and change Display mode to Blender File\nNow go down to the linked collection\nDouble click broken collection to rename it\nError message appears \"Cannot edit external library data\"\n\nRenaming linked collections works fine in 2.82\n", "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", "Add Primitive Tool in Mask Editing\n# Improve the Add Circle/Square tool for masking\nCurrently a mask primitive will always be added at the current cursor position. \nBut with the new tool system it would make more sense to be able to use the current mouse position to add primitives.\nIt should work very similar to the Add Object tool in 3D view. \nHere's how it could work in Mask mode in both Clip and Image editor:\n- Switch to Add Circle/Square tool\n- Click and hold mouse button pressed to add a primitive and scale it to the desired size. Release mouse button to finish. \n- While dragging, hold Alt key to scale from the center, hold Shift to draw perfect square/circle instead of freeform rectangle/ellipse\nOptional:\nIn 3d view the primitives are mostly parallel to the grid. For masking it could be interesting to be able to hold Ctrl while adding the mask to be able to rotate it.", "Cannot to make single user in object properties (if object is used by multiple collections)\nOperating system:\nGraphics card:\n\nBroken:\n\n\nI made a linked copy of an object (not object data!) in another collection by dragging the object from one window of the outliner to another.\nNow in object properties showing amount users equals 2:\n\n\n\nif you click on button \"make a single copy\" then nothing will happen. I am not sure but seems this UI inconsistency\n\n\nOpen the file and try to make single user to click in object property window:\n\n[make-single-copy.blend](make-single-copy.blend)", "Delayed update of outliner ui on change of active collection\nBlender 3.6\n\nWhen you change active collection outliner UI updates only after you leave the outliner.\nAttached short demo gif.\n\nWay to reproduce the issue:\n1) Start default blender scene.\n2) Add new collection \"Example\"\n3) Run the script below in the text editor.\n4) Note that above the outliner you can see currently active collection, by default it's \"Collection\"\n5) Try to select \"Example\" instead of \"Collection\" - it won't update in the ui above.\n6) If you leave the outliner it will update the active collection.\n7) You can also try to choose some other collection and run operator to `.tag_redraw()` - F3 - Update Outliner. Note that info message that says that active collection didn't changed, it's just that outliner area wasn't updated.\n\nWhat expected - outliner ui to update as you change active collection.\n\n```python\nimport bpy\n\ndef get_outliner_area(context):\n screen = context.screen\n for area in screen.areas:\n if area.type == \"OUTLINER\":\n return area\n\nclass EXAMPLE_OT_custom_collection_new(bpy.types.Operator):\n bl_idname = \"example.redraw_outliner\"\n bl_label = \"Update outliner\"\n def execute(self, context):\n before = context.collection.name\n area = get_outliner_area(context)\n area.tag_redraw()\n self.report({\"INFO\"}, f\"{before} -> {context.collection.name}\")\n\n return {'FINISHED'}\n\ndef context_draw_outliner_foobar_buttons(self, context):\n layout = self.layout\n layout.label(text=context.collection.name)\n layout.label(text=context.view_layer.active_layer_collection.name)\n layout.operator(\"example.redraw_outliner\")\n\ndef register():\n bpy.utils.register_class(EXAMPLE_OT_custom_collection_new)\n bpy.types.OUTLINER_HT_header.append(context_draw_outliner_foobar_buttons)\n\ndef unregister():\n bpy.utils.unregister_class(EXAMPLE_OT_custom_collection_new)\n bpy.types.OUTLINER_HT_header.remove(context_draw_outliner_foobar_buttons)\n\nif __name__ == \"__main__\":\n register()\n```\n\n", "Linking/Moving collection to another scene messes with the object visibility.\nOperating system: Windows 11\nGraphics card:\n\n**Blender Version** \nBroken: 9719fd696488\n\n\n\nThere is no reason the object visibility should not be carried over when the collection is moved or linked to another scene.\n\n\n[blender_HRo7zHHvN3.mp4](blender_HRo7zHHvN3.mp4)\n\nload the attached .blend\n\nselect the TEST collection in scene.A\n\nleft click drag onto scene.B while holding ctrl to link the collection instead of moving it. Moving the collection has the same affect\n\nopen scene.B and check the visibility\n\n\n\n[tests_06122022_1933_13.zip](tests_06122022_1933_13.zip)\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.", "\"Add [Object]\" menu not working correctly or lagging\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nI found out that the context menu that appears just after adding an object tends to lag or bug if you have split screen the viewport and the compositor with the checkbox \"use nodes\".\n\n1. Make a vertical split and and add the Compositor panel.\n2. Check \"use nodes\" in the compositor panel.\n3. Add any 3D Primitive object in the viewport, )E.G. Icosphere).\n4. Try changing the subdivisions in the \"add icosphere menu\" or just try to drag the logation paramenters whithin that menu.\n5. The result will be a choppy or lagging response, not expected.\n6. I've tracked this error even from the 3.4 version of blender, until now.\n", "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", "Placement Tool for Objects and/or Collections\n### Motivation\n\nThe new drag & drop snapping helps easily & quickly placing objects in the scene. But it relies quite a bit on the asset and the scene it’s being dragged into (e.g. the size relative to the destination scene, the exact normal of the snapped to surface), etc. Users may want to adjust the rotation, the scale, the up-axis, use the origin for snapping rather than the bound-box (e.g. to place trees so they are partially covered by the ground plane), etc.\n\n### Basic Design Idea\n\nRather than setting these options before dragging (where you don’t get visual feedback) or while dragging (where it’s awkward to give input because you’re holding a mouse button), the Operate->Settings paradigm of Blender should be used: First the object/collection is dragged in and placed using basic snapping, then we provide a visual way to keep adjusting the transforms and parameters until the user is happy with the result.\n\nHowever, this placement method isn't just useful for dragging in assets. It is useful as a general transform tool and should be created as such. So this is a proposal for a general placement tool with bounding-box or origin based surface snapping, that gives access to most important transforms and properties for placing an object. In some way or another, it could be (temporarily and optionally?) activated after dragging an object or collection asset into the scene. If more advanced transforms are needed, the user can still access the proper transform tools & operators.\n\n### Temporary Activation\n\nHaving to activate a placement tool every time an asset is dragged in can be annoying. Blender could automatically activate it, at least in some temporary fashion. For example, the tool could temporarily override the active tool after dragging in an asset. Deselecting the dragged in object would bring back the real active tool. If the user wishes to go back to the placement tool, that can be explicitly enabled again in the toolbar.\n\n### Tool Design\n\nTODO", "Python Operators that add/remove ID data without an undo step crash Blender\nOperating system: Win 10\nGraphics card: GTX 1070\n\nBroken: 2.8.3, 2.9 aed11c673efe\nWorked: 2.8.0\n\nUndoing after object linking to the scene crashes blender. I used the latest daily build\n\n1. Load the crash blend file [crash_modal.blend](crash_modal.blend)\n2. Run the script attached\n3. Click in viewport to add a new object, and then press ESC\n4. Press Ctrl+Z to undo\n5. Crash..\n\n" ]

[ "Collections (parent task)\nPossible improvements for collections user interface:\n* G-key group operators in the 3D viewport and object properties should become more clear.\n* Creating a new collection in the outliner could put all the selected objects (and collections?) in it.\n* Shortcut keys to improve usability, as in #54707.", "Select Objects and Move to collection won't work in View Layers panel; works in viewport\nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.21 355.11.10.50.10.103\n\n\nBroken: version: 2.80 (sub 57)\nWorked: (optional)\n\n\nRight clicking on a Collection to Select Objects and Move to collection (via M shortcut) won't move the objects to a new collection BUT right clicking -> Select Objects and then in the viewport doing Move to collection (via M) works.\n\n\n1. (optional) Add array modifier to cube with 100 count; go into Edit mode and hit P to separate by loose\n2. Right click collection with objects\n3. Click Select Objects\n4. Over the View Layers panel, press M, create a new collection and enter\n\nObjects don't move (despite status message).\n\nWorking in viewport:\n1. (optional) Add array modifier to cube with 100 count; go into Edit mode and hit P to separate by loose\n2. Right click collection with objects\n3. Click Select Objects\n4. Over the viewport, press M, create a new collection and enter\n\nObjects are moved to the new collection.\n\n[blender.bug.move_objects_collection.mp4](blender.bug.move_objects_collection.mp4)\n\n\n" ]

[ "Optix fails when geometry nodes instance has animated translation and scale 0 and motion blur is on\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.6.0 Alpha\nAlso broken in 3.4.1\n\nRendering will not start. It stops at \"Building OptiX acceleration structure\"\n\n\n\nThe culprit seems to be a combination of animated Translation and Scale 0 together with animated Rotation of the object and motion blur.\n\n\n\nDoesn't work in OptiX. Cuda and CPU both work.\n\nOpen the .blend file and render the frame.\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.", "Workbench Shadow Improvement\n### Respect World Space Lighting option\nCurrently, the shadow is always in world space. Use view space orientation when matcaps is used or when studio lights use view space orientation.\n\n### Follow the brightest light\nCurrently, the shadow is not following any of the lights direction in the studio lighting config. Selecting the most bright light seems like a good default. Otherwise, we can add a flag in the studio-lights to tag which one the shadow should follow.\nA toggle option to force the use of the custom shadow direction should be added (disabled by default in new files, enabled in older files).\n\n\n### Follow the matcap\nWhen matcap brightest spot can be extracted, we should make the shadow follow this direction.\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.", "Motion blur artifacts on certain frames EEVEE\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked: not sure\n\nMotion blur on error appears on same certain frames.\n\nblend attached Error appears on frames : 49 , 60, 85, 95, 103, 119,130\n\n[blur test.blend](blur_test.blend)\nnormal frame \n\nerror frame \n\nvideo with error frames [0001-0300.mp4](0001-0300.mp4)\n\n", "EEVEE motion blur doesn't work on objects with loose geometry\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3080, 3090\n\nBroken: 2.93.6\nWorked: never\n\nEevee motion blur doesn't work on skinned to an armature objects with vertices or edges that not owned by any face.\n\n1. Create a cube and an armature\n2. Skin the cube to the armature by an Armature modifier and painting weight\n3. Animate bone\n4. Turn on motion blur en EEVEE.\n5. Duplicate a single vertex or extrude it\n6 Render.\n\nAll these steps was done in the attatched file, you can just render it. [motion_blur_bug.blend](motion_blur_bug.blend)", "Multiple Frame Rates/ Playback/ VSE scene strips\nOperating system: windows 10\nGraphics card: rtx 2060\n\nBroken: 2.90.0\nWorked: Never\n\nI'm using the VSE and I have 2 scene strips from two different scenes inside the VSE.\nThe first scene strip references a scene that is set to 12 FPS.\nThe second scene strip references a scene that is set to 24 FPS.\nThe 3rd scene is where I'm using the VSE, and this scene is set to 12 FPS.\n\nThe problem is, all the scene strips are playing back at 12 FPS by default in the scene where I'm using the VSE. In other words, the scene that is 24 FPS is playing back at 12 FPS.\nIf I'm not mistaken, this wouldn't happen with real footage. Two recordings with two different FPS dropped into a project would play back at different speeds.\nWhat I'm trying to do is have a video at 12 fps, and the put a 24 fps scene strip in the VSE so that i can put it in slow motion and have it play back with the same quality. \n\n- Open attached file\n- Run VSE\nNote that the cube shown on each strip has the same speed in the animation.\nIt was expected that one was twice as fast than the other.\n[_VSE scene strips.blend](_VSE_scene_strips.blend)", "Using python handlers introduces artifacts with EEVEE motion blur\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.87\n\nBroken: version: 2.90.0 Beta\n\n\nRendered image has \"wrong\" motion blur\n\n0. Open attached .blend file\n[motion_blur.blend](motion_blur.blend)\n1. It contains a script, which sets the cube position via a follow path constraint based on the current frame:\n\n2. Set motion blur steps to 1, render:\n\n3. Set motion blur steps to 8, render:\n\n", "Blender 2.91 alpha - Debug menu, instant crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90.1\n\nShader compilation is causing an error when the debug menu is invoked on a blank scene or working scene.\n\nOpen the .blend attached file, press F3>search: Debug. Type 22 (eevee GPU speed benchmarking verbose),\nBlender will crash immediately. The same is true on a blank new scene in the general application template.\n\nFile to test: \n44cb6eb461af31ad1209dedb738d76c0.blend\n\n", "Shading Problem in Eevee in Top Orthonographic View When the Scale is not Applie Yet\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0 Beta\nWorked: Never\n\nThere is a strange shading problem in Eevee that happens when the object is scaled and the scale is not applied yet. The light needs to be at certain angle to make it appear. The problem also has to do with the topology of the mesh, it is hard to notice with just one face (though still there as you can see it flickers when you scale it), but it becomes obvious when subdivided.\n\n\nBased on the attached .blend file \nOpen my .blend file, you can see there is a circle and a light in the scene. You can see the problem by turn on render view. The light is placed at certain angle to make the problem show. \nThe circle was created using the below steps:\n\n(0. delete or hide my circle)\n1. Shift A and add a circle\n2. Lower left corner menu, the fill type choose Ngon\n3. Scale it up a little, don't apply the scale, and you can see it flickers during the scaling process\n4. Edit mode, hit the a key to choose all, hit the i key to inset the circle, and then inset it again, and see it has to do with the topology\n5. Object mode, ctrl a apply the scale, the problem is gone, it has to do with the scaling.\n[Orthonographic Top View Shading Problem.blend](Orthonographic_Top_View_Shading_Problem.blend)\n\n", "FADE INNACTIVE GEOMETRY MODE doesn't work properly with COLLECTION INSTANCES\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.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\nBroken: version: 2.91.0 Alpha\n\nI really like this mode, but it feels likeit not completely done. It's not work with collection instances at all.\nHere is was my expectations and what it looks like currently: \n\nAnd even instances from other scenes ignore this mode too. Will be cool if it(instances) will work in stream ideology of this mode\n\n\nOpen this file [FADE INNACTIVE GEOMETRY DOESN'T WORK PROPERLY WITH INSTANCES.blend](FADE_INNACTIVE_GEOMETRY_DOESN_T_WORK_PROPERLY_WITH_INSTANCES.blend) and select (one by one) buttom figures (cone/torus/cube) and after selecting each one - press Tab.\nYou will see that instances ignores this mode\n\n", "EEVEE baking\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!", "blender3.4 alpha new eevee a rendering on the flashback\nOperating system:windows10 21h1\nGraphics card: amd 6800xt （22.7.1 driver opengl doubled the performance of a version)\n\nBroken: blender-3.4.0-alpha+master.ca172677b1a7-windows.amd64-release\nWorked: There is no version that can be tested\n\n\nScene any scene including cube, whether window rendering or f12, directly exit the software.", "Slow camera view navigation in Cycles rendered shading mode with many instances\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\n\nWhen looking through camera and navigating the viewport (with Lock Camera to View for example), the movement is much slower than a regular perspective view. This happens in rendered shading mode with Cycles, when many object instances are in the scene. Instances can be generated with Geometry Nodes or the old particle system. Also they don't even have to be visible on screen, you could be looking at a single cube somewhere to the side, and the camera navigation will still be slow.\n[camera navigation bug.blend](camera_navigation_bug.blend)\n\n\n - Use the provided file\n - Switch to rendered mode and disable overlays\n - Try looking around\n - Switch to camera view\n # Navigation should be much slower and unresponsive\n\n\n\n" ]

[ "Motion blur steps value incorrectly changes shutter duration and affects AA quality\nOperating system: SUSE Leap 15.1\nGraphics card: NVidia RTX 2070 Super (official drivers)\n\nBroken: 2.90, a93be410c974, x86_64 linux, 2020-08-07\nWorked: 2.90, c5b6b3d82f56, x86_64 linux, 2020-08-05\nIssue introduced by: {4f59e4bddcb0c06e441adf68a5f252a4e5b4b260}\n\nWhen the motion blur 'steps' value is set to any value greater than 1 it incorrectly changes the shutter duration and also affects the anti-aliasing quality. From this and the lack of blur on the animated texture strip, it looks like the sampled aspect isn't working.\n\nIncorrrect:\n\n\nCorrect:\n\n\n1. load the attached .blend\n2. choose an intermediate frame between 1 and 10\n3. set steps value to 1 and render - motion blur duration and AA appear correct\n4. set steps value to 4 and render - motion blur duration is reduced by a factor of 4 and AA samples is noticeably worse\n5. set steps value to 32 - motion blur is all but gone and AA is poor\n6. In earlier builds of 2.90 (eg c5b6b3d82f56) the animated texture line would be correctly blurred\n\n[motion_blur_steps_value_v0.2.blend](motion_blur_steps_value_v0.2.blend)\n\n" ]

[ "Compositor in start up file does not show specific passes\nBroken: version: 3.1.0 Alpha\nWorked: Prior to 7e712b2d6a\n\nWhen loading the startup file, some passes will be missing from the compositor. For example the denoiser.\n\nHere is a video showing off the issue: [F12781327](Missing_Passes_in_Compositor.mp4)\n\nWatch the video above or follow the steps below:\n\n1. Start up Blender and change the render engine to Cycles.\n2. Go to the `Viewlayer Properties` tab and enable Denoising Data.\n3. Change one of the areas to the `Compositor` and tick the `Use Nodes` box.\n4. Take note of the passes that are available on the `Render layer` node.\n5. Select from the top of Blender `File -> Defaults -> Save Startup File`\n6. Close Blender\n7. Open a new instance of Blender 3.1 and notice that the `Render Layer` node is missing some of the inputs that should be there.\n\nHow it looks before you re-open Blender:\n{[F13081662](image.png), size=full}\n\nHow it looks afterwards:\n{[F13081667](image.png), size=full}\n\n\nExample of startup.blend:\n[startup.blend](startup.blend)", "Texture Painting not updating cycles shader in viewport\nOperating system: Linux-5.8.0-44-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa Intel(R) Xe Graphics (TGL GT2) Intel 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.92.0\n\n\nLevel 1. When texture painting in the 3D viewport, the image is updated, but the visible shader on the object doesn't update in cycles until switching to viewport shading and back to cycles.\nIt still works when switching to Eevee shading. When reloading the image in the shader image texture node, it updates in cycles, but the problem persists when the image is updated (painted on) again.\n\nLevel 2. The above bug becomes worse as follows:\n\nIn cycles the image stops updating even when switching to viewport shading and back to cycles.\n(A)-When reloading the image in the shader image texture node, it updates in cycles, but any new paint on the texture in the viewport or image editor -> paint mode won't update until step A is repeated. \n\nI do not know exactly what triggers this 2nd level bug, but it doesn't take long to show up. \nI was able to repeat it just by painting and switching between Eevee and cycles using my test .blend file (attached)\n\n\n\n\n1. Assign a material with an image node to an unwrapped object\n2. Switch to viewport texture painting and start painting on the image in cycles shading. \n3. The image updates in viewport shading, but not the visible shader on the object in cycles. \n4. Switch to Eevee shading - now eveything works as expected.\n\n5. I do not know what triggers the level 2 bug.\n\n[Cycles not painting on Cube.blend](Cycles_not_painting_on_Cube.blend)\n\n\n\n\n\n", "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).", "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)", "Attribute Node Doesn't Function Under World Shader Context\nOperating system: Windows 10 19044.1826 64-bit, Linux 5.18.14.arch1-1\nGraphics card: NVIDIA GeForce GTX 1080 Ti\n\nBroken: 3.2.1\nWorked: never\n\nThe `Attribute` node (both in Cycles or Eevee) doesn't work under World materials.\nAlso the `Geometry` and `Instancer` types in the node are irrelevant in the Word context and should be hidden.\nMaybe the `Object` type should be renamed to 'World', but it currently doesn't seem to be able to pass world properties as uniforms.\nThis essentially means that:\n - There are redundant elements in the World shader node editor that currently serve no purpose\n - There is no way to pass custom uniform attributes to World shader nodes, although they should be available (similarly to how it is done for objects)\n\n\n\n- Open attached .blend file\n- Note that the \"test_color\" attribute of the World is not read by the material.\n[AttributeWorldShader.blend](AttributeWorldShader.blend)", "Blender has froze my Manajro Linux, which has corrupted my root Btrfs filesystem, rendering the machine unable to boot\nOperating system: Manjaro Linux\nGraphics card: Radeon RX 5500/5500M / Pro 5500M\n\nBroken: Blender 2.90.0, 2.90.1, 2.91.0 Alpha\nWorked: none yet\n\nWhen doing a very specific thing in Shader editor using Eevee rendered, my system froze. I've rebooted and tried again. It froze again, only this time when I rebooted it I was greeted by an emergency shell. My root Btrfs filesystem is unmountable. I'm currently performing disk imaging, and will attempt to fix the FS or restore the system from backup.\n\nHere's the screen that I saw after rebooting my laptop after the second lock-up:\n\n\n\nI have a specific .blend file that when loaded on Manjaro Linux will freeze the system. I've tried again booting a fresh Manjaro 20.1.1. However it's a confidential client project and I cannot share it publicly.\n\nI wasn't able to reproduce the problem on Windows 10 running on the same laptop.\n\nI suspect the problem could be in an AMD GPU driver - it's the only thing that I believe has enough system access to mess up a roo t filesystem that was involved. And it's clear the problem was triggered by a certain material in Blender, while rendering with Eevee.\n\nNote that the system won't freeze until I turn on Rendered view. Using Material Preview is fine.\nTwo first time when it happened it was immediately after I have added a mix node to add another texture to an existing image path in an Eevee material.\nI thought that maybe texture sizes could be the problem, as I've been using 3 8K textures, and maybe the laptop's GPU can't handle that, but filesystem corruption should never be the result of that.", "Realtime Compositor - Crash on Mac when using Map UV node\nOperating system: macOS Ventura 13.3.1\nGraphics card: AMD Radeon Pro 5700 XT 16GB\n\nBroken: 3.6 alpha cef128e68af5 (2023-04-13 16:06)\n\nConnecting a Map UV node in Compositing will crash on macOS\n\nIn Blender's startup scene, enable Compositing by checking \"Use Nodes\".\nConnect a Map UV node between the Render Layers node and the Composite node.\nIn a 3D view, turn on Rendered viewport and set Viewport Compositing to Always.\nThis will crash (100% reproducible).\n\nPlease contact summary if more information is required.\n\n", "Freestyle doesn't render hair\nOperating system: Win10 64bit\nGraphics card: gtx1050ti\n\nBroken: 2.8-155c62b070a9\nWorked: 2.79b\n\nRender file with Cycles in 2.79b and 2.8. In 2.8 only mesh is outlined.\n[free.blend](free.blend)", "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.", "Manipulators don't render properly\n## System Info\nOperating system: Debian 10.6 AMD64\nGraphics card: NVIDIA Corporation GF108 [GeForce GT 730] with proprietary drivers packaged from debian\n [system-info.txt](system-info.txt)\n## Blender versions\nBroken: 2.83 and upwards (latest build - Blender 2.92.0 Alpha November 22, 00:30:33- df8cc5662b9a - as well)\nWorked: 2.82 and older\n\n\n## Bug Description\nStarting a new (General) file, selecting the cube and pressing move or rotate, the manipulators render with some colored plane artifacts as in screenshots attached.\n\nThis is caused by the graphics card not being recognized and software rendering being used instead.\n\n## Demonstration\n\n### Video of bug\n\n[manipulators-bug.mp4](manipulators-bug.mp4)\n\n### Video of expected behavior\n\n[manipulators-normal.mp4](manipulators-normal.mp4)\n\n### Screenshots of bug\n\n\n", "Composited cycles render passes not matching combined output\nOperating system: Microsoft Windows [Version 10.0.19042.2251]\nGraphics card: Nvidia Quadro RTX 4000 (driver 512.36)\n\nBroken: 3.3.1 and 3.4.0\nWorked: Unknown\n\nCarrying out manual composition of the Cycles render passes as described in the Blender documentation is not resulting in the same result as the combined output.\n\nFig 1 shows the blender manual description of how passes are combined for the final output (edited by me with how I think the volume passes are included - the documentation doesn't explain this).\n\n\nFig 2 shows my compositor node tree that matches that description.\n\n\nFig 3 is the compositor output...\n\n...and Fig 4 is the combined noisy image output. If you click on Fig 3 or 4 to expan the image view then use the left/right arrows on your keyboard you can flick between these two images to clearly see the difference.\n\n\nNeither are denoised to eliminate that as a contributory factor (I used 4096 samples to keep noise low). Fig 5 highlights the regions where I'm seeing significant shading differences...\n\n\nFigs 6,7,8 are closer views of these regions.\n\n\n\n\nThe key issues (shown in Fig 5) are the missing shading around the sphere rim, and missing shading on the floor panels at the larger rib regions between the panels. The missing shading around the sphere rim is exacerbated when denoising is applied and those notches become more pronounced. All other regions appear to be the same to me.\n\nA potential clue: the issue might be originating with the DiffDir and/or the DiffInd passes, because the sphere rim highlight 'notches' and the darker regions on the floor panels are both visible when those two passes are multiplied in the compositor node tree (see Fig 9 showing viewer output from that multiply node).\n\n\nLoad the attached blend file and render in cycles (caution - its currently set to 4096 samples... you dont need to render it with as many samples to see the issue!). Compare the 'noisy image' output and the compositor output.\n[cycles_compositor_combine.blend](cycles_compositor_combine.blend)", "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", "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", "Cycles: Bump node doesn't generate anything in certain conditions\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.3.0\nWorked: all versions from 2.79 to 3.4.0 alpha are affected, there is no working build\n\nI'm trying to generate a normal map using Bump node and color output of the env map as height map, it doesn't work on Cycles while it works on Eevee. Seems like the \"reflection\" output of Texture coordinate node is broken, but it works fine when I'm using another outputs though\n\nOpen the project, then click on viewport Rendered mode button - it'll start Cycles which for some reason can't generate bump map, then switch to Material preview mode - it'll start eevee which works as expected\n[bug_report.blend](bug_report.blend)\n\nEdit: typos and bad english grammar fixed, I believe", "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" ]

[ "Cycles - Render Layer Node connection to File Output Node not possible\nWindows 10 Build 17134\nAMD Ryzen Threadripper 1950X 16-Core Processor\nGeforce GTX 1080 Ti\nGeforce GTX Titan X\n\nBroken: blender-2.80.0-git.41f4d210796\nWorked: (optional)\n\nThere is no connection between renderlayer node and output node possible if you switch to cycles.\n\nStart Blender\nSwitch to Compositing Workspace\nKlick on \"Use nodes\"\nSwitch to render engine Cycles\nAdd a file output node or in the View Layer Tab switch on Normal Pass in the passes section. - The render layers node looses its output connections.\nSwitching between the render engines (Eevee, OpenGl, Cycles) sometimes makes the connections appear again but arbitrary.\n" ]

[ "Knife Tool: incorrect interaction with Array modifier when the Merge \"First Last\" option is set\nOperating system: Win10\nGraphics card: nVidia 1070\n\nBroken: 2.80 (sub 44), branch: master, commit date: 2019-02-14 04:22, hash: caa8e7ff2894\nWorked: not sure\n\nWhen the Merge First Last option is set for an Array modifier, it seems like hidden, virtual geometry is picked up while using the knife tool to cut across the surface of the primary shape.\n\nThis results in an improper cut.\n\nBad in-progress cut:\n\n\nBad confirmed cut: \n\n\nGood cut -- with the First Last option turned off:\n\n\n[array-bug.blend](array-bug.blend)\n- Create a simple shape and array it in a radial fashion so that the first/last vertices of the shape are eligible for merge\n - Or just load the attached .blend\n\n- Attempt to make a cut across the main shape with the Merge First Last option set\n- Notice that the cut line is picking up some hidden edges somehow -- perhaps due to triangulation?\n- Confirm the cut and notice it's still incorrect and pretty weird", "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", "Sharp normals along base mesh wires in multires sculpting with smooth shading\nOperating system: Linux-5.4.0-47-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.91.0 Alpha\nWorked: As far as I know in 2.79 before the inclusion of OpenSubdiv\n\nThis has been a long standing issue in multires sculpting with shading artefacts in smooth shading.\nThese will only start appearing when sculpting on the surface and may flicker between different spots when sculpting directly over them.\n\n- Create a suzanne head\n- Add a multires modifier with 4 subdivisions\n- Change the object to smooth shading\n- Enter sculpt mode and smooth on the surface of the object\n\nOn these spots the sharp shading should consistently appear among others. A high contrast Matcap can help with spotting them.\nIn this example they are very subtle but they can be extremely noticeable on very curved surfaces.\n\n\n\n\n\n", "Color management is broken in the Sequencer\nOperating system: Linux-5.0.21-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: Mesa DRI Intel(R) Sandybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 19.1.1\n\n\nBroken: version: 2.80 (sub 74)\nWorked: earlier build of 2.80 (hash: d62a749fcf48) and 2.79\n\nWeird things happens when changing the color management settings in the VSE:\n- wrong color display\n- make sound\n\nWith a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not.\nAlso, changing this setting does not apply the change directly, the VSE has to be refreshed.\n\nAnother issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise.\n", "'Custom Split Normals' generated by the Boolean modifier does not match the normals of the object\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\nIf the object used as operand in the Boolean modifier has `Custom Split Normals` (either through the `WeightedNormal` modifier or manually added) the resulting object will have a \"broken\" `Custom Split Normal`.\nThis kind of works with objects which do not have any `Custom Split Normals` (so only shade flat and shade smooth, no weighted normals etc.) (although it also has it's problems. See #95913 (Strange shading behaviour when using boolean modifier))\nWhen `Custom Split Normals` are involved, the modifier uses the `Custom Split Normals` of the operand object on the target object to determine the shading on the affected areas.\n\n- Open attached file. (The left example has only shade smooth on the boolean object and on the right example the boolean object has a weighted normal modifier on the modifier stack).\nThe issue still persists even if you delete the weighted normals modifier on the target object in the right example.\n[Test_file2.blend](Test_file2.blend)\n\n---\nAnother example:\n[Test_file.blend](Test_file.blend)\n", "Wrong tangent space when using GPU subdivisions\nOperating system: Linux-5.18.0-1-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.08\n\nBroken: version: 3.3.0 Alpha\nWorked: N/A\n\n\nThe tangent space is calculated wrongly when using GPU subdivisions: it appears as if it is calculated for the base mesh instead of being calculated at the limit surface.\n\n\nOpen the attache file, and toggle \"GPU subdivisions\" in the preferences.\n\n|CPU subdivisions|GPU subdivisions|\n| -- | -- |\n||\n\n[gpu_subdiv_tangent.blend](gpu_subdiv_tangent.blend)\n", "Multi-object-Mode: EditMode transform properties\nEdit-mode buttons currently only show median values for the active edit-object.\n\nThe Mean Crease value of the N panel doesn't work for multiple objects:\nHere i have 2 objects selected\n\nIn Edit Mode changing the Mean Crease value does change its effect only on the selected object:\n", "Multilayer EXR UDIMs display incorrectly\nBroken: since introduction of UDIM in 2.82\n\nThis issue was encountered when investigating #100452 (USD Alab v2 import errors)\n\nThe attached zip archive contains two blend files, which are identical except that they reference EXR and PNG UDIMs, respectively. `alab_chair_exr_udim.blend`, referencing the EXRs, displays incorrectly in the viewport (first image). `alab_chair_png_udim.blend`, referencing PNGs, displays correctly (second image).\n\n\n\n\n[blender_exr_udim_bug.zip](blender_exr_udim_bug.zip)\n\nWhen the EXRs have multiple layers, even just 1, the problem occurs:\n| ok | not ok - uses a single layer called 'rgb' |\n| -- | -- |\n|  |  |\n\n----\nMultilayer EXRs have a custom loading sequence and storage location inside the `Image->rr (RenderResult)` field.\n\nThat code is quite intertwined with the RenderLayer/RenderPass system. It's unclear why this was chosen for multi-layer images. Maybe because it was the system that knew how to select layers/passes already? In any case, it is not UDIM aware and I'm not sure if the RenderLayer/RenderPass system should be aware of them.\n\nSince I don't have a full understanding of the history here a proper fix seems non trivial at first inspection.\n", "Eevee: math wrap and floor, AMD Driver precision issues\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 5500 XT ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.1 27.20.21003.1028\n\nBroken: version: 2.92.0\nBlender 2.83 LTS has same problem\n\nMath and Vector Wrap give different results for Eevee and Cycles, also doesn't swap min max, when max is less than min\n\n\n**More info**\nThis is important for an upcoming Shader Nodes patch that relies on wrap operation\nalso for shader setups that rely on this\n\nother people tested this, the problem seems to appear only on AMD Windows\n\n\nWhen Using -3 as Min for wrap, and 3 as max, some values give different results in Eevee than in Cycles\nFloor operation is probably the cause of this\nthis node setup \n\n\nCycles\n\n\nEevee\n\n\n[eevee_math_wrap_different_from_cycles.blend](eevee_math_wrap_different_from_cycles.blend)\n\n", "Decimate modifier gives different result on every evaluation\nOperating system: Linux-5.4.0-122-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.129.06\n\nBroken: version: 3.2.2, 3.3 latest\nBroken: 3.1.2\nWorked: 3.1.0\nWorked: 2.93.8\n\nCaused by fb2cb0324a\n\nA mesh with decimate modifier gets topology rebuilt on each frame of Cycles render. Notice that a new cones object on the right is not broken.\nThere's something wrong with the left object. I checked every property I could think of.\n[0001-0250.mp4](0001-0250.mp4)\n[decimate_bug.blend](decimate_bug.blend)\n\nOpen the file. Render a sequence.\n\n", "Bevel modifier profile direction depends on edge/face order\n[2021-04-18 01-18-54.mp4](2021-04-18_01-18-54.mp4)\n\n[01.blend](01.blend)\n\n\n\nIt is recommended that the Solidify modifier reorder the faces. \n\nThis is the problem I encountered when I was making a column. I thought it was bug. \n\nIt was later found that after the Solidify modifier, the Bevel direction is controlled by the face order, and the Bevel modifier has no option for the face order.", "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!", "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.", "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?", "Unify Interpolation In Vertex Paint And Sculpt Mode\nVertex paint squares colors when it interpolates, while the paint tools in sculpt mode do not. This should really be made consistent across both modes. \n\n\n" ]

[ "Subdivision modifier Apply works wrong\n{[F8419608](subdiv.blend)}{[F8415984](https://archive.blender.org/developer/F8415984/subd.jpg)}Operating 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 9)\n\nwhen I apply the deformer, I expect that the deformed geometry will look the same as before.\nIf I apply one level of subdivision deformer, then add subdivision deformer for another one level, geometry doesn't look like if I add just deformer with two levels of subdivisions.\n\nThis is awkward because the common pipeline looks like: make a base shape > subdivide > add mid-level detail >subdivide > add high-level detail. But before subdivision and after I get two different shapes.\n\n1 create two similar objects\n2 for the first object add subdivision modifier with subd level 2\n3 for the second object add subdivision modifier with subd level 1 and apply it\n4 for the second object add subdivision modifier with subd level 1 \n5 object 1 and 2 should look similar, but they don't" ]

[ "Regression: Crash when Sculpting on a mesh from a GP Lineart Modifier\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (W11)\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.2, 4.0.0 Alpha\nWorked: 3.1\n\n\nWhen trying to sculpt a mesh in an assigned collection that a grease pencil lineart modifier references and the layer it is drawing to contains Grease Pencil strokes - it will instantly crash Blender. \n\n\n1. Download and extract zip to get the test blend file\n2. Load attached file with Load UI off\n3. Select the bust, it is in a GP lineart modifier collection \n4. Go to sculpt mode\n5. Try sculpt\n6. Crash\n\nAlternative steps:\n1. Create new scene\n2. Create a sphere\n3. Create a Grease Pencil object\n4. Add sphere to a new collection\n5. Select the GP object and add a lineart modifier\n6. Reference the sphere collection in the modifier\n7. Assign layer and material to the modifier\n8. Draw in the same layer in Draw mode of the GP\n9. switch to sculpt mode\n10. Try sculpt over sphere surface\n11. Instant crash\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)", "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", "Regression: Multires Unsubdivide destroys the vertex groups\nOperating system: Windows 10\n\n\nBroken: 3.0 release, 3.0 (b42354672e)\nWorked: 2.93LTS, 3.0 (cec103d5a9) \n\n\nIt seems like unsubdividing using the Multires Modifier destroys the vertex groups, interesthingly enough other kind of mesh data stays intact (like the vertex colors) after the same operation.\n\nThe Decimate modifier's Unsubdivide does not destroy the data, but using the Decimate modifiers not option in these kinds of usage because the multires one is about getting the prior subd levels for sculpting purposes.\n\n[byUQjUlY19.mp4](byUQjUlY19.mp4)\n\n\nLoad the .blend file\nSelect the torus\nMultires->Unsibdivide\nMove your mouse to the 3d viewport to get the UI update properly\nThe Vgroups are gone\n\n[multires_09122021_1051_52.blend](multires_09122021_1051_52.blend)\n", "Crashes when working with pose mode (rigidbodies involved)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.0.1\nWorked: 2.8\n\nFrequent random crashes.\n\nJust animate bones. It may even crash at undo. One day it's okay, another it crashes 20 times a day.\n[debug_logs.zip](debug_logs.zip)\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", "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", "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", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "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", "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", "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", "Add modifier error message for attribute name clashes\nIf user has a UV and a vertex color groups with the same name things behave in non predictable ways.\n\nThe nodes modifier should check for this and add an error message when this happens.", "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\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)" ]

[ "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```" ]

[ "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", "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", "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.", "creating custom (combined ) texture brush is not visually updated in texture brush tab\nWin 10 \nIntel i5\namd radeon \n\nblender 2.8 \n8996e26116f0\n\nGo into the texture for the brush settings and enable ''úse nodes'' \nGive the new texture brush a name \nMix two textures together , the output result is not reflected in the text.brush tabe\nThis was not the case wiith blender 2.7 \n\n\n\n\nAlso , when rotating the brush (ctr-F) ,the alpha overlay of the brush texture is nor", "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", "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).", "Color Atributes: Inverted Smooth filter gives diferent artifacts in diferent Color Attributes\nOperating system: Linux-5.4.0-107-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 670MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\n\nInvert of the smooth color filter gives different results in different color Attributes, Some are good and some are realy bad.\n\n1 Create the for different color attributes for color paint in sculpt mode.\n2 Paint color with the paint brush.\n3 activate the smooth color filter from right to left a few times.\n\nHere it is a video showing the for results. As it can be seen independent of the domain, the color ones give worst result than the bytes colors. I have only use pure Red, Green, and Blue that are the colors that gives the less errors, but even so you can see that the results in color are changing.\n\nTest File:\n[#97340.blend](T97340.blend)\n[vokoscreen-2022-04-15_02-08-18.mp4](vokoscreen-2022-04-15_02-08-18.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.", "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)", "Splitting strips will change image output\nOperating system: Windows 8\nGraphics card: 550Ti\n\nBlender Version\nBroken: 2.93.0 Beta\nWorked: Not sure\n\nSplitting strips with \"hard\" method will change image output.\n\nAdd movie or image sequence to VSE\nSplit strip by pressing Shift + K\n\nImage will change\n\n", "Sound strips don't change length when sound file is changed\nOperating system: Windows 10\nGraphics card: Nvidia MX150\n\nBroken: 2.91 and 2.92 Alpha\n\n**Steps to reproduce**\nAdd sound, change file to another one with different length.\n\nStrip length is not updated.", "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", "VSE: Select more/less functionality breaks on certain conditions\nOperating system: Linux Mint 20\nGraphics card: NVIDIA G92 [GeForce 9800 GT]\n\nBroken: 2.93.1 / 2.92.0\nWorked: Unsure\n\nThe functions sequencer.select_more and sequencer.select_less get stuck when the newly selected strip reaches an edge, or when number of selected strips becomes zero.\n\n[blender-bug__select-more-less.mp4](blender-bug__select-more-less.mp4)\n\nThe attached video shows the functions [select_more]/[select_less] will break when the following conditions are met:\n```\n a) Any strip chain selection reaches the edge of the row of strips with [select_more]\n i) either when it starts from an edge and reaches the other edge\n ii) or when it starts in the middle and expands from both sides, the side of whichever edge is met will get stuck\n b) Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more]\n```\n\n\n\nI think it's unlikely this is intended behaviour?\n\nSorry I didn't get visual keypresses set up for the video, but I'm just using CTL- [x] and CTL- [x] on num pad as per default. \n\nDavid", "Mix Node Modes\nThe new mix node has different options according to data type.\n\nThe idea of this task is to look at adding the mix modes to float and vector data types.\n\nThe color blending modes could be used but a number of these modes assume that the\ndata is in the range of 0-1.\n\n[D16024: Node: Add mix type to Mix Node](D16024) \nThis a patch adds non-color mix types to float and vector data types.\n\nAdditionally, it would be good to look at how different interpolation modes could also be added. ", "Multiple Frame Rates/ Playback/ VSE scene strips\nOperating system: windows 10\nGraphics card: rtx 2060\n\nBroken: 2.90.0\nWorked: Never\n\nI'm using the VSE and I have 2 scene strips from two different scenes inside the VSE.\nThe first scene strip references a scene that is set to 12 FPS.\nThe second scene strip references a scene that is set to 24 FPS.\nThe 3rd scene is where I'm using the VSE, and this scene is set to 12 FPS.\n\nThe problem is, all the scene strips are playing back at 12 FPS by default in the scene where I'm using the VSE. In other words, the scene that is 24 FPS is playing back at 12 FPS.\nIf I'm not mistaken, this wouldn't happen with real footage. Two recordings with two different FPS dropped into a project would play back at different speeds.\nWhat I'm trying to do is have a video at 12 fps, and the put a 24 fps scene strip in the VSE so that i can put it in slow motion and have it play back with the same quality. \n\n- Open attached file\n- Run VSE\nNote that the cube shown on each strip has the same speed in the animation.\nIt was expected that one was twice as fast than the other.\n[_VSE scene strips.blend](_VSE_scene_strips.blend)" ]

[ "VSE Opacity Not Working With Certain Blend Types\nOperating system: Linux-5.4.0-28-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 15)\nBroken: 2.82\n\nThe Opacity slider under Adjust > Compositing on the Strip tab in the VSE Sequencer Sidebar doesn't work as expected with certain blend types.\n\nIt works as expected with Add, Cross, Multiply, Over Drop, Gamma Cross, Subtract, Alpha Under, and Alpha Over.\n\nHowever, it functions as a switch (0 = off, >0.000000001-1 = on) for Overlay, Soft Light, Hard Light, Vivid Light, Color Dodge, Screen, Lighten, Linear Burn, Color Burn, Darken, Value, Color, Saturation, Hue, Exclusion, Difference, Pin Light, and Linear Light.\n\n(This may very well be the expected behavior for some of these, I'm not an expert on blend types. Also, I am unsure what Replace is supposed to do, so I didn't include that above.)\n\nAlso, the Normal blend type (opaque) seems to be missing. Alpha Over seems to be the default for any new strips that are added.\n\nStart a new file by selecting Video Editing. Add two images or movies to the Sequencer window, and place these strips on top of each other. Under Adjust > Compositing on the Strip tab in the sidebar, change the blend type of the upper strip and play with the Opacity slider, going between 0 and non-zero values.\n\n[VSE_Opacity_Bug.blend](VSE_Opacity_Bug.blend)\n\n" ]

[ "EEVEE: Add support for extracting alpha channels from a color\nI mistakenly filed a bug report --> #72856 EEVEE transparency problem with mtpaint PNG\n\nI didn't fully understand the bug and attached a blender file that didn't show the bug properly.\nPacking the image file with blender command 'Pack' makes the image\nopaque so it is worthless to include a blender document. I will\ninclude a mtpaint PNG image instead and you can load it into\nblender 2.81 yourself and see how it renders in EEVEE versus cycles.\n\nI noticed that your forum converts the image to opaque if I try to attach to this post\nso I'll use a shareable link that preserves the transparency:\n\nopen?id=1TjfSjzabYEmVHXTODPFymGVNwuL02SnJ\n\nHere is how I created the mtpaint image to reproduce the problem...\n\n1) Launch GIMP -->new gimp document -no alpha channel - paint with brush\n2) save as PNG format with no alpha channel\n3) Launch mtpaint ---> open the PNG document\n4) 'Save as' to output the document - one color chosen to be transparent - PNG format\n5) Launch blender 2.81 (linux) - images > Images as planes\n\nEEVEE rendering doesn't respect the transparent region.\nCycles rendering does respect the transparent region.\n\n\nNot a high priorty.", "Adjusting spotlight blend using gizmo does not register undo\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\nThe gizmo control is introduced in 3c8c0f1094.\n\nAdjusting spotlight blend using gizmo does not register undo\n\n[SpotlightBlendGizmoBrokenUndo.mp4](SpotlightBlendGizmoBrokenUndo.mp4)\n", "VSE editor is 1 pixel off when aligning non-frame images\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0\n\nVSE editor is 1px off when compositing with non-full frame images\n\n1) open a VSE empty project\n2) set the scene dimension resolution to 1080x1080\n3) add a 1080x900 picture and check the left side pixels\n\n", "Sculpt: Grid overlay for Grab active point do not work.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nThis seems to be issue only with Nvidia GPUs on windows.\n\nBroken: version: 3.0.0 Alpha\n\n\nGrid overlay for Grab active point do not work.\n[2021-07-18_18-56-46.mp4](2021-07-18_18-56-46.mp4)\n\n\n**Steps to reproduce**\n[#89942.blend](T89942.blend)\n\n- Open file\n- Check if wireframe overlay is drawn under cursor\n\nWhat fixes this is to have any transform gizmo visible while using brush, then it works until Blender is restarted.\n\n\nFrom #92703:\n\n> This was proposed on the blenderartists thread, I have no idea if it works or if it could broke the preview on the AMD cards\n>  \n> If you know how to compile you can fix it by erasing ! from the line 1157 : if (!depth_test) {\n> to read like so: if (depth_test) {\n\n\n", "VSE: Some \"Select Grouped\" operators don't work as expected\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: version: 4.0.0 Alpha\nWorked: (unknown)\n\n\nSome of the operators in the VSE's \"Select -> Grouped\" menu have wrong/confusing names or don't behave as expected.\n\n---\n\n`Select -> Grouped -> Effect Type`\n\nDespite the name and the tooltip, this operator does not check the effect type. It only checks whether the strip is an effect or not. Maybe it could be renamed to \"Is Effect\"? Similarly, the vague \"Global Type\" could be renamed to \"Is Sound\".\n\n---\n\n`Select -> Grouped -> Data`\n\nWhen run on a file-based strip, it selects all strips pointing to the same folder rather than to the same file. This may be correct behavior for image sequences, but not for everything else (movies, sounds, single images).\n\nIn the screenshot below, the expectation is that it only adds the second strip to the selection, not the third.\n\n\n---\n\n`Select -> Grouped -> Effect`\n\nGoing by the tooltip (\"Shared effects\"), you'd expect that this operator selects content strips that share an effect strip with the active strip. Instead, it finds the effect *types* linked to the active strip, then selects any other content strips linked to that same effect type.\n\n(So really, this should have been the \"Effect Type\" operator above)\n\nIn the screenshot below, I'd expect that it only adds \"2.png\" to the selection. Instead, it adds all the strips that are affected by an \"Add\" effect.\n\n\n---\n\n`Select -> Grouped -> Effect/Linked`\n\nApart from the tooltip not being very clear, this operator doesn't work at all (simply deselects everything) unless \"Extend\" is enabled in the \"Adjust Last Operation\" panel.", "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", "False color look gives incorrect values\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.3.0 Alpha\n\nThe False color in Blender is indeed different from the Filmic master on GitHub:\n\n\nThe testing EXR I used (background is 0.18 middle grey):\n\n\n- Load image in Image editor\n- Enable View as Render in side panel\n- Set False Color as View Transform in Color Management settings", "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.", "VSE: No simultaneous strip snapping on left & right side [and right side favoured]\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108\n\nBroken: version: 3.0.0 Alpha\nWorked: Unsure\n\n{[F10300365](no-dual-strip-snapping.png),size=full}\nA strip in VSE cannot snap at left and right ends simultaneously. Annoying when the end that does not snap is the end that you're wanting to know the orientation of (especially when you're zoomed out and can't tell by eye). \n\nFurther to this, the right side snap will always prefer over the left. It seems it just searches the right side first, and if it snaps it just doesn't check the left side at all. I would find it very odd if dual snapping isn't intended, but if somehow there is no plan to add it in the near future, at least the behaviour should not prefer one side - like maybe prefer the side based on the direction the strip is dragged or something (snap first to the side of the direction the strip is heading?).\n\n[strips-do-not-snap-at-both-ends-simultaneously-and-right-side-is-preferred.blend](strips-do-not-snap-at-both-ends-simultaneously-and-right-side-is-preferred.blend)\n- Open the blend file, and drag colour strip along x-axis\n- Only the right end will snap, despite both ends clearly lining up with the metastrips\nNOTE: There is a reason I used a metastrip as the snap-to strips here, as there is another snapping bug I will be filing soon (and I didn't want that bug to mess up the behaviour in this one).\n", "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.", "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)", "overlay.show_paint_wire doesn't work in vertex paint modes depending on edit mode selection\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.80?\n\nThis overlay option seems to take into account edit-mode selection\n\n\nHere's what it's supposed to do:\n[viIeK7Tkv0.mp4](viIeK7Tkv0.mp4)\n\nBut on 2.93 and 3.0 it appears to do nothing in Weight/Vertex Paint mode if the geometry is selected in edit mode. This seems like a bug, unless it's some odd design choice?\n\n- Create a cube and select all its verts in edit mode.\n- Enter weight paint mode\n- Toggle the Show Wire setting under Viewport Overlays->Weight Paint (NOT \"Wireframe\" under Viewport Overlays->Geometry)\n- Nothing happens\n- Switch to edit mode\n- Deselect all with Alt+A\n- Go back to weight paint mode\n- Wireframe display now works as expected.\n\n\nNote: This now changed again in 44d2479dc3 (now it does not draw **at all** -- reported separately in #89880 (overlay.show_paint_wire doesn't work anymore))", "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.", "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", "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" ]

[ "Video Sequencer: The Blend Factor in Color Mix strips is broken.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 26.20.100.7262\n\nBroken: version: 2.82 (sub 7)\n\nThe Blend Factor in Color Mix strips has no effect.\n\n- Add two strips to the sequencer.\n- Select them both.\n- Add a Color Mix effect strip.\n- In the sidebar, change the Blend Factor.\n- Nothing happens.\nThis is a bug, as this function is supposed to set the amount of how much influence either input should have. \n\n(On the same note: ` Sidebar > Adjust > Composite > Blend Modes ` are completely missing the Blend Factor)\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", "particle system collisions stop working outside 255 blender units\nOperating system: windows 10\nGraphics card: gtx 1080\n\nBroken: 2.79b 2018-3-22, \nparticle systems do not interact with faces which are oriented in the axis where the face is more than 255 blender units away from the origin\n[name ]([particleproblem.blend](particleproblem.blend))", "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.", "Render Error using the HIP backend\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 7900 XTX ATI Technologies Inc. 4.5.0 Core Profile Context 22.40.51.06.230425\n\nBroken: version: 3.6.0 Beta\nWorked: Unknown\n\nMessed up renders in multiple of the common Blender Demo files. Classroom being the most obvious.\n\nStarting blender and running the render with the HIP or HIPRT backend using the 7900 XTX GPU causes the render errors in the attached \"broken\" images. Running and finishing a HIPRT render targeting the CPU results in a proper render, and fixes this for subsequent GPU renders with both HIP and HIPRT, see \"non-broken\" images.\n\n", "Cycles: ray & shader counters\n[D4204: Ray and Shader counters for Cycles](D4204)", "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```", "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)", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Wrong tangent space when using GPU subdivisions\nOperating system: Linux-5.18.0-1-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.08\n\nBroken: version: 3.3.0 Alpha\nWorked: N/A\n\n\nThe tangent space is calculated wrongly when using GPU subdivisions: it appears as if it is calculated for the base mesh instead of being calculated at the limit surface.\n\n\nOpen the attache file, and toggle \"GPU subdivisions\" in the preferences.\n\n|CPU subdivisions|GPU subdivisions|\n| -- | -- |\n||\n\n[gpu_subdiv_tangent.blend](gpu_subdiv_tangent.blend)\n", "Cycles: networking support\n[D2808: Cycles Networking support](D2808)", "Cycles HIP device\nTasks to keep track of HIP device development tasks.\n\n- [x] Windows support and stability\n - [x] Upgrade HIP SDK to 22.10\n - [x] RDNA2\n - [x] RDNA1\n - [x] Vega\n- [x] Linux support and stability\n - [x] Crash in `hipGetDeviceProperties`\n - [x] RDNA3 ([D16507](D16507))\n - [x] RDNA2\n - [x] RDNA1 (#97591)\n - [x] Vega\n- [ ] Hardware ray-tracing\n- [ ] Wiki build documentation for building with hipcc on Linux and Windows\n- [ ] Clip mode in Image Texture node not supported (#92975)\n- [ ] Image texture size is limited, could detect this and resize or show user better error (#94057, #93109)\n- [ ] Deduplicate CUDA and HIP host code\n- [ ] Graphics interop is broken in 21.Q4 driver, enable for next driver ([D13167](D13167))\n- [x] Compute capability checking (if needed)\n- [x] Integrator state size estimation depending on the GPU\n\nCompleted for 3.0 release:\n- [x] Buildbot setup of hipcc\n - [x] Install on CentOS workers\n - [x] Install on Windows workers\n - [x] Enable Windows binaries on the buildbot\n- [x] Determine range of supported cards on Linux and Windows for 3.0\n- [x] Detect supported cards in the code ([D12958](D12958))\n- [x] Bug: instancing rendering artifact in bmw27 scene\n- [x] Supported GPU hardware list for documentation\n- [x] #92972 (Cycles HIP graphics interop issue on AMD 5500 XT and Windows)\n- [x] Windows driver available\n- [x] #92984 (Cycles HIP crash with smoke volume)\n- [x] #93109 (Cycles HIP device missing driver version check)", "4090 has problem with texture in render preview\nOperating system: Windows 11\nGraphics card: Nvidia Geforce 4090\n\nBroken: (3.4 and 3.5.1)\nWorked: none.\n\n**Short description of error** \nThis only started recently, has been fine up till today. My preferences are set to use both the CPU (AMD Threadripper 32) and the GPU (geforce 4090) in OptiX (or CUDA, doesnt seem to matter). Once the file opens, material preview works fine. (refer to \"materialpreview.png\") but when i click render preview (refer to renderprevier.png) all i see is my rig. Anything with a texture is a similar dark grey as the default blender background. I can move the camera around fine, but no textures are visible. If i click material preview again to switch back, blender freezes and must \"end task\" in task manager. If i turn off the GPU assistance and only have the CPU enabled, everything works as it should. \n\nYesterday i updated to latest windows 11 update. I also updated my gameready drivers for my 4090. When the issue started, i thought it might have something to do with gameready drivers so switched to Studio drivers. This did not fix it. \nAssuming that these updates may have broken my file, i rolled back windows 11 drivers to most recent previous version, and did the same with the nvidia studio drivers (uninstalled 5.35.... installed 5.31). This fixed nothing.\n\nI would love to know why my GPU can't be used with Blender suddenly. Games work fine. Furmark 3d app works fine, no issues. Heat is fine. Very frustrating to have such expensive gear suddenly stop working.\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", "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", "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" ]

[ "Cycles HIP binaries disabled due to compiler bugs\n### Tasks\n\n- [x] Enable on Windows (#107098)\n- [x] Enable on Linux (#107662)\n- [ ] Enable Radeon VII (gfx906)\n\n### Background\n\nThere are known bugs in HIP compiler that are causing random build failures when making changes to the Cycles kernel. This is preventing developers from efficiently making improvements to Cycles.\n\nCycles AMD GPU rendering were disabled in Blender 3.6 alpha, so that ongoing work like Principled v2 is not blocked. Additionally light tree sampling is not available for HIP in Blender 3.5. We hope this can be resolved later on in the 3.6 release cycle.\n\nRelevant FIXME's in LLVM amdgpu backend (in fact I suspect we hit the same ones back when we were using OpenCL).\nSIRegisterInfo.cpp#L221\nSIRegisterInfo.cpp#L296\n\nMost recent issues:\n#104085 (#104720 )\n#104669\n#104097\nD16714", "Blender 3.6 Alpha - AMD GPU Problem\nOperating system: Windows 11 Home\nGraphics card: Ryzen 5 5500u with Radeon Graphic VII\n\nBroken: (example: 3.60, ef60b13c1f29, alpha, 2023-02-17, as found on the gpu section)\nWorked: (stable version of Blender 3.4.1 that worked as expected)\n\nWhen selecting GPU (AMD Radeon Graphic VII and also CPU+GPU) it appear an error \"HIP binary kernel for graphics card compute capability (\"9.0\") not found\".\n\nOpen Blender, go to preference, system, enable cpu+gpu or gpu only, then enable cycles, enable gpu and error appear as \"HIP binary kernel for graphics card compute capability (\"9.0\") not found\"\n\n" ]

[ "EEVEE motion blur in cryptomatte\nI have tested this in 2.93.3 and even blender-3.0.0-beta+v30.bd734cc4419a to check if it got added there. \nThe issue is simple to explain: cryptomattes in eevee don't include motionblur. In Cycles they do include the motion blur. Is this a known thing, will it be addressed in the next updates?\nI suppose it could also be an undiscovered bug as the blender manual describes it as following \"[...] mattes will be anti-aliased and take into account effects like motion blur and transparency.\" cryptomatte.html - well in eevee it doesn't take motion blur into account", "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", "X axis isn't showing in camera view like Z axis \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.2.1\n\nX axis isn't showing in camera view like Z axis when we activate it from viewport overlays:[2022-07-06 22-43-44.mp4](2022-07-06_22-43-44.mp4)\n\n", "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", "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", "\"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", "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", "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", "Setup Tracking Scene needs an upate\n\nThe Setup Tracking Scene operator needs an update. Since Blender has the option to make an object a shadow catcher, the current setup seems overly complex and elaborate. \nAlso, not always is a shadow catcher even needed. That's why I suggest to simplify the setup tracking scene operator and make it a bit more flexible. \n\n**Different Setup operators**\nInstead of the current two operators, I would break it up a bit more. \n\n- Set as Background (same as current operator)\n- Setup Camera: If no camera is available, add one. Setup the camera solver constraint. Set Background images.\n- Setup Tracking scene: see below\n- Setup Solved Object (not sure about the term): Add an Empty (drawtype Sphere maybe?) to the scene, setup the object solver constraint, set inverse.\n- optionally more operators can be added, maybe via addons, such as cleanplate setup etc. \n\n**Setup Tracking Scene**\nThe current setup operator is designed for a very specific usecase. But now with the shadow catcher and Eevee available I find it is not suitable anymore in most cases. So I suggest to use a simplified setup instead. Should the user need a more elaborate solution it is much easier to extend the simplified setup, than to cleanup the complicated one that we have at the moment. \nTo make it more convenient for the user I suggest to let the user choose which render engine he wants to use and if he even needs a shadow catcher.\nSo first the user can switch the render engine from the currently active one to a different engine with a dropdown menu. Though for now I would suggest to only use Eevee and Cycles. \nThen with a checkbox you can choose whether to use a shadow catcher or not.\nIf you then hit \"Setup Tracking scene\" the following happens:\n- Make Film transparent\n- Enable use_nodes in the compositor\n- Setup node_tree: Add Movieclip. Add scale node. Only if LensDistortion has been used for solving the Undistortion node will be added. Combine Viewlayer and the movieclip tree with an AlphaOver node.\n- If shadow catcher checkbox is enabled: Add a plane in a new collection named \"shadow catcher\". With Cycles as render engine, enable \"Shadow Catcher\" for the plane. With Eevee, add a shadow catcher material for the plane and set the Material to Alpha Blend, as suggested here: blender-2-8-eevee-tutorial-shadow-catcher\nIn both cases the shadow will appear in the alpha channel of the Viewlayer, so the node_tree from above won't have to be modified. \nI also would suggest not to change the World shader anymore, as it feels quite invasive, especially with Eevee. \n\n**Python**\nCurrently the setup tracking scene operator is made up of a bunch of functions all inside CLIP_OT_setup_tracking_scene. So I guess those functions can be pulled out of that class to make them more global, so that the new operators from above have access to them. \n\n\nFeedback and suggestions are very welcome!\n", "\"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", "Compositor: Viewport issues when Passepartout is off\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera `Passepartout` is off.\nNote that the Compositor is set to Camera.\n\n\n* Open this file: [zoomed_out.blend](attachment)\n* Notice that the passepartout is disabled in this camera, but the viewport compositor is set to Camera.\n\nCurrent buggy result:\n\n\nThe mask only matches when the camera has `Passepartout` on:\n\n\n\nRelated: #111344\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", "Asset Browser: Material preview with black background when Cycles is disabled\nBroken: version: 3.0.0, 3.4.0\nWorked: Never\n\nWhen a scene was saved with Cycles but I disable the Cycles add-on the material previews get a black background.\n\n* Disable Cycles add-on.\n* Click on any (e.g., the Yellow) material asset and update its preview.\n[black_preview.blend](black_preview.blend)\n", "Eevee \"Shutter\" setting in motion blur render settings not animatable\nOperating system: Win 10\nGraphics card: RTX 3090\n\nBroken: 2.91.0\nWorked: never worked (as far as i know)\n\n\nEevee \"Shutter\" in motion blur render settings not animatable\nIn Cycles it ***is***animatable.N/A", "2.83lts Regression: Viewport render image ignores colormanagement, and appears to be hardcoded to use sRGB.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBisect points to 190fd795a9\nBroken: version: 2.83.0\nWorked: 2.82a\n\n`Viewport Render Image` ignores color management. The image produced is clamped to 1.0 according to the color sampler. It appears to be hard coded to sRGB.\n\nCreate a Scene that has scene linear color values above 1.0. Render with Filmic. Then do `viewport render image` and see how it produces an image with blown out highlights.\n\n2.82a:\n\n\n2.83:\n\n\n\n[test.blend](test.blend)\n\n" ]

[ "When \"Motion Blur\" is turned on, materials look distorted in Viewport\nOperating system: Windows 10 x64\nGraphics card: Nvidia GTX 1060 (laptop)\n\nBroken: 2.80, 91a155833e59, blender 2.8, 2019-01-07\n\nBEHAVIOR\nWhen using Principled BSDF to make a metallic material and then enabling Motion Blur, seeing the rendered view in viewport shows heavy distortions in material appearance (renders out fine, though). Disabling or unchecking either \"Motion Blur\" or \"Screen Space Reflections\" in render settings fixes the issue and the distortions disappear.\n\nEXPECTED BEHAVIOR\nWhen in rendered mode in viewport, that material would appear without distortions regardless of whether motion blur is checked or not.\n\nSCREENSHOT EXAMPLES:\nHere is a screenshot example with motion blur enabled: scene%20with%20motion%20blur.jpg?dl=0\nAnd here is a screenshot example with motion blur disabled: scene%20without%20motion%20blur.jpg?dl=0\n\n1. Create new general blender project\n2. Go to default cube's Principled BSDF material settings and make metallic by turning up metallic parameter to 1.0\n4. Enable \"Motion Blur\" and \"Screen Space Reflections\" in render settings\n5. Press \"Z\" key and switch viewport mode to \"Rendered\", then press \"NUMPAD 0\" key to look through camera\n", "EEVEE camera motion blur renders only one viewport sample\nOperating system: Windows 10 Pro, 64 Bit\nGraphics card: GeForce GTX 1080 Ti\n\nBroken: Date 2018-12-03 00:27, Hash: a205493426b, Branch: blender2.8\n\n**Eevee mode:** When using rendered \"camera view\" in the viewport, it will always be rendered using 1 render sample only. The camera view ignores the global Viewport Samples settings.\n\nIf you exit the camera view and switch to the regular user perspektive view, then the global Viewport Samples are correct and the view renders as expected.\n\nWhy the camera view is ignoring the global viewport sample settings?\n\nSee my attached image,please.\n\nEDIT: The bug appear when \"Motion Blur\" is activated in Eevee render settings.\n\n\n\n[bug_prototyping01_eevee.blend](bug_prototyping01_eevee.blend)" ]

[ "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.", "Mesh to Volume intersection artifacts\nOperating system: Ubuntu18x64, Ubuntu20x64, Win8x64.\nGraphics card: Mesa DRI Intel(R) HD Graphics (BYT) Intel Open Source Technology Center 4.2 (Core Profile) Mesa 20.0.8\n\nBroken: version: 3.0, 3.1\n\nIntersecting Mesh to Volume produces artifacts (on CPU. GPU not tested).\n\n[volume-intersection.blend](volume-intersection.blend)\n - Open,\n - Run viewport Render Preview on the left side.", "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", "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", "Cycles: Volumes in the world shader behave strangle with some textures\n**System Information:**\nOperating system: Linux-5.14.0-1-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.63.01\n\nBroken: version: 3.0.0 Alpha, and every version between master at 2.81 (That is how far I tested).\nWorked: Unsure\n\n**Short description of error:**\nWhen using certain procedural textures in the volume output of the world shader in Cycles, you get unexpected results.\n\n**Exact steps for others to reproduce the error:**\n1. Create a scene in Cycles.\n2. Change to the rendered viewport.\n3. Open a shader editor and change to the `World` shader and delete the `Background` node.\n4. In the `World Shader`add a `Magic Texture` node and connect one of the outputs to the `Volume` socket on the `World Output` node.\n5. You will noticed that in the viewport you can see the `Magic Texture` is projecting light onto objects in the scene, but you can't see the `Magic Texture` directly.\n6. Place a `Color Ramp` node between the `Magic Texture` and the `World Output` nodes. Now you can see the `Magic Texture` in the viewport.\n\nAnother test:\n1. Create a scene in Cycles.\n2. Change to the rendered viewport.\n3. Open a shader editor and change to the `World` shader and delete the `Background` node.\n4. Add a `Noise Texture` node and connect an output to the `Volume` socket on the `World Output` node.\n5. Notice that you can see the impact the `Noise Texture` is having on the scene, but you can't see the `Noise Texture`\n6. Place a `Color Ramp` between the `Noise Texture` and the `World Output` nodes. You still can't see the `Nosie Texture` in the scene.\n7. Place a `Volume Scatter` node in the `World Shader`, connecting the output to the `Volume` socket on the `World Output` node and connect the output of the `Color Ramp` node to the `Density` input of the `Volume Scatter` node. You can now see the noise texture in the volume if you have a light in your scene.\n8. Select the left most handle (the handle that is black) in the `Color Ramp` node and drag it closer to the position `0.5`. You will see the results you expect until you reach the position `0.5` where the volume will seem to disappear from your scene. Yet when you look at objects in the scene, the light reaching them is still affected by a volume shader you can't see.\n\nHere's a video demonstrating this:\n[Volumetrics not visibile in viewport in certain sitautions.mp4](Volumetrics_not_visibile_in_viewport_in_certain_sitautions.mp4)", "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```", "Strange shadow when rendering with GPU device\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\n\nThere's a shadow in the scene that doesn't make sense.\n\nI've attached a Blender file that I've tried to strip down as much as possible. Here's what I get (notice the strange shadow bottom middle)...\n\nThe odd thing is that if I delete/hide random objects in the scene, the shadow disappears.\n\nExample... hide any of the following objects:\nMISTY_MOUNTAINS_39_2k_c.001\nPlane.001\nAny object in the atmos folder\nObject_4.001\nthe whole quixel folder\n\nI know the shadow shape is cast from the volumetric cloud container shape (a spherical shape) but it's behaving very oddly and, as I use volumetrics in every single scene I ever create, I'm familiar with them behaving oddly. This is just a new one.\n\n[shadow error.zip](shadow_error.zip)\n", "Cycles rendering world origin extremely slow when using hair particle system with density maps (no, really!)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.1\nTested in 2.93.1, 2.90 on CPU and Nvidia GPU.\n\nCycles is rendering the world origin extremely slowly, even if there is nothing at all in view.\nSeems to be caused by Hair particle system using a texture influencing density.\n\nWatch this video for me walking through the bug:\nwatch?v=3DdTrC-qN2M\n\n[particle_render_slow.blend](particle_render_slow.blend)\nRender image\n\n", "Mantaflow - Flickering Square pattern of the particles\nOperating system: Windows 10\nGraphics card: Quadro RTX 4000\nCPU: Ryzen Threadripper 2950x\nRAM: 64GB\n\nBroken: (2.90.0 // 2.83.5)\n\n\nI got the Problem both in the 2.83 LTS & 2.9 Version:\nIf i bake the fluid simulation in Mantaflow the particles of Bubble & Foam result in flickering squares: In one frame the particles are present and in the next frame they are abscent (in a square pattern). If I render an animation sequence out of this the video is flickering. I added the .blend-File for the used Settings and also two screenshots to demonstrate the square Pattern. Furthermore a rendered animation of another scene of mine shows the flickering result when rendered. \n\n\n[Mantaflow Flickering.avi](Mantaflow_Flickering.avi)\n\n[2020_09_19 - Fluid Test.blend](2020_09_19_-_Fluid_Test.blend)\n\n\n\n\n\nJust bake the attached .blend File (You need to change the saving location)", "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", "Mantaflow - Enabling \"Noise\" breaks fast-moving smoke\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 650 Ti\nProcessor: Intel® Core™ i7-3770\n\nBroken: 2.83.0\nWorked: Never\n\nEnabling noise on fast-moving smoke produces a \"grainy\" result that doesn't match original simulation.\n[C - High Speed Noise - Demo.mp4](C_-_High_Speed_Noise_-_Demo.mp4)\n\nAlso, this problem is less profound when the cache type is set to \"Final\", though still clearly visible.\n\n**Exact steps to reproduce the error**\n1. In any smoke simulation, dramatically increase the velocity of the smoke, either in the emitter settings, or with a force-field.\n2. Bake Data\n3. Bake Noise\n\n[Noise on High-Speed Smoke.blend](Noise_on_High-Speed_Smoke.blend)", "Cycles: GPU Performance\n**Memory usage**\n\n- [x] Auto detect good integrator state size depending on GPU (hardcoded to 1 million now)\n- [ ] Reduce size of IntegratorState\n - [x] Don't store float4 as float3\n - [x] Don't allocate memory for unused features (volumes, sss, denoising, light passes)\n - [x] Dynamic volume stack size depending on scene contents ([D12925](D12925))\n - [ ] Overlap SSS parameters with other memory\n - [ ] Compress some floats as half float\n - [ ] Reduce bits for integers where possible\n - [ ] Can diffuse/glossy/transmission bounces be limited to 255?\n\n- [ ] SoA\n - [ ] Individual arrays for XYZ components of float3?\n - [ ] Pack together 8bit/16bit values into 32bit?\n\n- [ ] Reduce size of ShaderData\n - [ ] Compute some differentials on the fly?\n - [ ] Read some data directly from ray/intersection?\n - [x] Don't copy matrix if motion blur is disabled\n\n- [ ] Reduce kernel local memory\n - [ ] Dynamically allocate closures based on used shaders\n - [ ] Dynamically allocate SVM stack based on used shaders\n - [ ] Check if SVM stack is allocated multiple times\n - [ ] Check on deduplicating ShaderData instances\n - [ ] Check for other unknown sources of memory usage\n - [x] Use either `shade_surface` or `shade_surface_raytrace` for reserving memory\n\n**Kernel Size**\n\n- [x] Replace megakernel used for last few samples? Only helps about 10% with viewport render, barely with batch render. But makes OptiX runtime compilation slow.\n- [x] Make `svm_eval_nodes` a templated function and specialize it for\n - [x] Background\n - [x] Lights\n - [x] Shadows\n - [x] Shader-raytracing\n - [x] Volumes\n- [x] Avoid shader ray-tracing for AO pass ([D12900](D12900))\n- [x] Verify if more specialization is possible in `svm_eval_nodes` (seems not)\n- [ ] Deduplicate shader evaluation call in `shade_background`\n\n**Scheduling**\n\n- [x] Make shadow paths fully independent so they do not block main path kernels ([D12889](D12889))\n- [x] Accurately count number of available paths for scheduling additional work tiles\n- [x] Compact shadow paths similar to main paths ([D12944](D12944))\n- [x] Consider adding scrambling distance in advanced options ([D12318](D12318))\n- [x] Compact path states for coherence\n- [ ] Tweak tile size for better coherence\n- [ ] Tweak work tiles or pixel order to improve coherence (many small tiles, Z-order, ..)\n- [ ] Try other shader sorting techniques (but will be more expensive than bucket sort)\n - [ ] Take into account object ID\n - [ ] Take into account random number for BSDF/BSSRDF selection?\n- [ ] Overlapped kernel execution\n - [ ] Use multiple independent GPU queueus? (so far was found to be 15% slower)\n - [ ] Use multiple GPU queues to schedule different kernels?\n- [ ] Optimize active index, sorting and prefix sum kernels\n - [ ] Parallelize prefix_sum\n - [ ] Build active/sorted index array for specific based on another array indicating active paths for all kernels, especially when number of paths is small\n- [ ] Try pushing (part of) integrator state in queues rather than persistent location, for more coherent memory access\n - [ ] Check potential performance benefit by coalescing state\n - [ ] Shadow paths\n - [ ] Main path\n- [ ] Cancelling renders and updates can be slow due to the occupancy heuristic that schedules more samples. Find a way to reduce this problem.\n- [ ] Shader sorting and locality balancing ([D15331](D15331))\n - [ ] Find better heuristics for scenes with many shaders\n - [x] Use for GPU devices other than Metal\n- [ ] Shader sorting by node graph similarity, to find coherence if e.g. the graph only has different image textures\n\n**Display**\n\n- [x] For final render, let Cycles draw the image instead of copying pixels to Blender\n - [x] Render pass support\n\n**Render Algorithms**\n\n- [x] Use native OptiX curve primitive for thick hair\n- [x] Transparent shadows: can we terminate OptiX rays earlier when enough hits are found? ([D12524](D12524))\n- [x] Transparent shadows: tune max hits for performance / memory usage\n- [ ] Detect constant transparent shadows for triangles and avoid recording intersection and evaluating shader entirely\n- [ ] Detect transparent shadows that are purely an image texture lookup and perform it in the hit kernel\n- [ ] For volume stack init, implement volume all intersection that writes directly into the stack\n\n**Tuning**\n\n- [ ] Automatically increase integrator state size depending on available memory\n- [ ] Tweak kernel compilation parameters (num threads per block, max registers)\n - [ ] Different parameters per kernel?", "Cache-folder name makes fluid simulation not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 20.1.3 26.20.15015.1007\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nCache-folder name makes fluid simulation not working. My blend file (with fluid cache data) was in a folder named badeværelse and the fluid sim didn't work. Changed the folders name to badevaerelse and it worked.\n\nMake folder called \"æ\" (possibly \"ø\" and \"å\" too)\nMake a blend file inside it and try to bake liquid sim and use the folder as cache directory for the fluid physics\nSee how no particles appear when you press bake\n\n", "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", "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" ]

[ "AMD Polaris Specific crashes.\nOperating system: Windows 10 Home, 64 Bit, fully updates\nGraphics card: AMD RX 580 8GB\n\nBroken: 2.85 and beyond\nWorked: 2.79(fully working), 2.82(sometimes crashes)\n\nAttempting to render a scene in cycles that uses smoke and/or fire utilizing the GPU will result in a crash or hang. If the processor is also selected as an OpenCL device, and GPU render is attempted, the entire operating system experience artifacting, across all screens, before the computer hangs and all screens go black. Enabling Open Shading Language before switching to GPU rendering seems to improve system responsiveness. If only the GPU is set as an OpenCL rendering device, the GPU will render one sample, before Blender freezes and eventually is labeled \"not responding\" by Windows.\n\nA fresh new file is created, and the quick smoke effect is applied to the default cube. The simulation type is switched to fire only, and baked. A random frame is selected(I usually use around 20 to 40), and it is switched to render view. The CPU renders it fine, but switching to GPU rendering causes the error. " ]

[ "Eevee contact shadows appearing from objects with shadows disabled\nOperating system: Windows 10\nGraphics card: RTX 3080\n\nversion: 3.5.1\n\nIssue:\nObjects in Eevee with the material setting \"Shadow Mode\" set to \"None\" still casts contact shadows.\n\nreplication:\nWith the default scene add a plane and scale it up so a visible shadow is being casted on it from the default cube, go into material settings of the default cube and set shadow mode to none. Then go to the default point light and enable contact shadows on it. (or view the blend file)\n\n", "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", "shadow catcher data missing from diffuse passes when transparency is disabled, and shadow catcher object is masking environment when transparency is enabled (can't recombine moving scene envronment)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\n\nshadow catcher data missing from diffuse passes when transparency is disabled, and shadow catcher object is masking environment when transparency is enabled (can't recombine moving scene envronment). This makes it impossible to rebuild the image unless the shadow catcher pass is used, which is not suitable when using vector motion blur.\n\nOpen below blend file (choose to load ui)\ngo to scene 'no transparency'\nin the compositor press f12 to render a frame\ncompare the combined image and the rebuilt image\n\ngo to the second scene 'transparency'\nin the compositor hit f12 to render again\nthis time the environment is masked out by the shadow catcher, making it impossible to use the rendered environment (which is necessary if the camera is animated)\n\nrequired behaviour - \n\nshadows appear in diffuse passes when transparency is disabled, so the rebuilt image matches the viewport.\n\nshadow catcher object doesn't mask out the environment pass when transparency is enabled (so the environment can be added back to the image when the camera is moving (backplate cant be used here))\n\n\n\nThe only possible solution currently is to always render with transparency enabled, and then render your scene a second time with only the environment visible, which causes issues when rendering via scripts.\n\n", "World Light Extraction\nEevee world probe is not suited for very high frequency details and even less for sunlight. For this we want to introduce a threshold. All light under the threshold would be pushed to the world diffuse/reflection probe. All light above the threshold would be moved to an importance sample map and used to position a (virtual) sun light that represent the missing energy from the probe.\n\nWe can position the sun in 2 ways: randomly per sample using the importance map, or fixed using a Spherical harmonic decomposition.\nThe first one offers more precise lighting (can work with multiple light source) when the second one offers more stable lighting (good for a sun).\n\nThe good thing is that this virtual sunlight can be shadowed! Thus making most of the light coming from the environment shadowed.\n\nThis should fix this sort discrepancy between cycles and eevee:\n\n\nEstimate : 2 weeks", "Simple ball shooting animation not working as before\nOperating system: win7\nGraphics card: gtx970m\n\nBroken: 2.80, 2.81a, 2.82a, 2.83-1239cab11ff9\nWorked: 2.79b\n\nI've tried to create a simple shooting ball and while the effect was ok with blender 2.79b it won't work the same\nway on the specified \"broken\" versions. I'm not sure if the way to make these type of animations has changed of\nif this it's really an existing bug. \n\nDemo: [Blender 2.79b vs 2.82](2020-04-09_16-14-38.mp4)\n\n\nYou'll find the .blend file ready to display the issue below.\n\n[test1.blend](test1.blend)", "EEVEE renders black when no normal NODES connected to mix node --> normal input.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0 Release Candidate\n\n\nEEVEE renders black when no normal NODES connected to mix node --> normal input. Works fine with Cycles. \n\nOpen below file and click on each material output to see the issue. Switch to cycles and all fine.\n\n[empty normal bug.blend](empty_normal_bug.blend)\n\n\n\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", "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.", "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", "Compositor: Viewport issues when zoomed in\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera is not fully in view.\n\n\n* Open this file: [zoomed_in.blend](attachment)\n* Notice that in the viewport the view is zoomed in inside the camera view.\n\nCurrent buggy result:\n\n\nThe mask only matches when the entire camera is in view:\n\n\n", "In eevee, shading disappears when SSS is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: -\n\nShading disappears in Eevee if one object is located on another object and both have Subsurface enabled\n\nWhen an object has no shading, it looks unrealistic and wrong.\nTo get around this bug, I render two images and connect them in the compositor.\n\nMaybe it is possible to somehow enable these shading without a second render?\nSSS is needed for both objects.\n\nBall Subsurface On (0.02)\n\nBall Subsurface Off (0.0)\n\n\n.Blend file\n[bugshafowsubsurface.blend](bugshafowsubsurface.blend)\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", "EEVEE Ambient Occlusion incorrect composition (affected by Bent Normals even at Factor of zero)\nOperating system: rx 6800\nGraphics card: windows 10\n\nBroken: blender-2.93.0-a9e7d503ddcd-windows64\n\nthe ambient occlusion does not appear to blend correctly both in viewport and in final renders\n\nno ambient occlusion\n\nao factor 1\n\nao factor 0\n\n[incorrect ao composition.blend](incorrect_ao_composition.blend)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Dissolving edge doesn't work as expected\nOperating system: Windows 10\nGraphics card: RTX 2070 SUPER\n\nBroken: 3.2.1\nWorked: not sure\n\n\nDissolving edges doesn't work as expected.\n\n\n\n\n\n[untitled.blend](untitled.blend)", "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" ]

[ ".IES Files do not Pack\nOperating system: win7\nGraphics card:\n\nBroken: blender-2.80-11f2c65128dc-win64\nWorked: (optional)\n\n\n2.8 cannot pack IES files, which is an issue since they are needed packed for the renderfarm\n\n\ngo \"automatically pack into .blend\" then search for IES file in blender file outliner, or try to upload anywhere\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n\n[IES TEST.blend](IES_TEST.blend)", "External IES is not packing in .blend file\nOperating system: Windows 10 Pro\nGraphics card: AMD Rx 580\n\nBroken: 155c62b070a9\n\n\n**External IES is not packing in .blend**\nI was using spot lamp with IES node with a External IES file, before to send my job to a render farm, I packed all externa data to .blend. When I recived the render result, all the IES propertys was missing and the lights was looking like a normal spot lamp. \nSo I did a new test and recorded in this video:\n\n[2019.07.06-14.21_01.mp4](2019.07.06-14.21_01.mp4)\n\n\nThanks for make possible this amazing software!\n\n" ]

[ "Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)\nOperating system: Linux-5.15.0-52-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.4.0 Alpha\nBroken: 2.92.0\nWorked: 2.91.2\n\nBisecting gives 0f95f51361 as the culprit commit\n\nif the armature viewport mode is set to \"in front\" it doesn't properly update when the overlays are turned off and on\n[Peek 2022-11-01 05-35.mp4](Peek_2022-11-01_05-35.mp4)\n\n1-add an armature\n2-set the \"viewport display\" to in front\n3-turn off and on overlays\n4-if you can confirm the bug the armature should appear after changing anything in the 3d view to update as in the video, move rotate or zoom \n\n", "Z-fighting in wireframe moded\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.90.1\nAlso tested with the latest 2.92 alpha build. Same results.\n\nI experience Z-fighting in wireframe mode when there are overlapping faces.\nWireframe mode should only render edges. Z-fighting indicates that faces are rendered too, but it only happens when they partially overlap.\n\nDuplicate the default cube and move it slightly in one axis, so that faces of the two cubes partially overlap. Switch to wireframe mode and you will see faces flickering where they overlap. You won't see it if the two cubes fully overlap by staying roughly in the same spot.\n\n[wireframe glitch.blend](wireframe_glitch.blend)\n", "Overlapping icons when modifier windows is squashed\nOperating system: Linux-5.15.0-37-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nIcons overlap each other in the modifier stack when the window is squashed\n\nDrag the viewport window over so that the modifier window is compressed\n\n", "Join Palettes\nActually is impossible to Join several Palettes and a operator to do that is needed.", "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)", "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", "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", "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", "Z-fight with invisible face in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nWorked: \n\nI have 2 cubes. Bigger one is set viewport display as wire. Both share the same XZ plane. In Object mode shading is fine, but if I enter in Edit mode with smaller cube artifacts are appear.\n\n[ladder_01.blend](ladder_01.blend) \n\n", "Boolean modifier - Intersect option - not working / artifacts while doing 3D Sectioning\nOperating system: Linux-5.4.0-72-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 20.2.6\n\nBroken: version: 2.93.0 Beta\nWorked: in Blender 2.92\n\nStrange artifacts using 3D sectioning using Boolean modifier - Intersect (see sectioning animation issues below)\n\nExpected behavior:\n3D slice working correctly in Blender 2.92 (to view internal section of object)\n```\n-Create Mesh Plane (larger than object)\n-Select Plane - Add Boolean Modifier \n\tOptions - Intersect\n\tObject - STL or Object\n\tSolver - Exact\n\n```\n\n\nActual behavior:\n3D slice issues using Blender 2.93 beta (to view internal section of object)\n1) Not showing object as a 3D section like in 2.92 (see animation above)\n2) Artifacts Showing up when moving cutting plane back and forth (see animation below) \n\n\n\n\nIn the blend file, move the `Plane_xy` along the z axis, or move the `Plane_xz` along the y axis.\n[section.blend](section.blend)\n\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", "VSE: In Multicam all strips gets white outline\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\nAll channels/strips get a white active strip outline when a multicam strip is selected. \n\nOpen this .blend file:\n[VSE_MultiCam.blend](VSE_MultiCam.blend)\n\nNotice that all previews have a white active strip outline, though it's only the multicam strip selected:\n{[F10961426](image.png),size=full}\n\n", "Fix preview flickering when using \"Adjust Last Operation\"\nTweaking properties in the \"Adjust Last Operation\" panel removes all previews for a moment, causing quite drastic and annoying flickering.", "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", "Spreadout enum in pie menu gives strange result\nWin7x64GTX660m\n\nBroken: 2.73\nWorked: (optional)\n\nIf \"select similar\" operator is launched from a pie, items are arranged in a weird fashion (happens only in vertex and edge mode), overlapping one another and showing index numbers such as 167.\n\nFrom file, just click run in text editor (replaced example operator in text editor's pie menu template with *pie.operator_enum(\"mesh.select_similar\", \"type\")*).\n\n[overlappingPies.blend](overlappingPies.blend)" ]

[ "Viewport borders flicker when splitting said viewport\n\nOperating system: Windows 7 SP1\nGraphics card: GeForce GTX 980 (Driver version 417.35)\n\n\nBroken: 2.80 ffa29194bbe7 win64 (March 13 2019)\n\n\nWhen you split the viewport, the viewport borders flicker.\n\nThis wasn't the case a few weeks ago.\n\n\nTry splitting a viewport as in the video below:\n\n[YOUTUBE Video ](q-AHximrnfY)\n" ]

[ "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?\"", "Geometry Node: Sculpt mode doesn't cause update due to editing\n## SIMPLE REPORT:\n\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.5.0 Alpha\nWorked: Never\n\n\nObjects with geometry nodes do not update if dependent on the object that is currently being sculpted.\n\n[2023-01-14 13-13-37.mp4](2023-01-14_13-13-37.mp4)\n\n\n1. Duplicete default cube.\n2. Add Geometry Node tree on copy, add `Object Info`, choose other one cube, connect geometry to group output.\n3. Select other one cube, go to sculpt mode, do anything.\nCube with geometry node does not according to sculpted one\n\n## USER REPORT:\n\nOperating system: Windows 10 Pro\nGraphics card: Geforece RTX 2080\n\nBroken: 3.4.1 Stable\nWorked: not sure\n\n\nGeometry nodes network is not updating when in sculpt mode. It's updating fine when in edit mode.\n\nI have nodes basically adding differences in point positions from one mesh to another -\n\n\n\n\n[sculpt_mode_update.blend](sculpt_mode_update.blend)\n\n\n\n\n\n- Create an object(=A) and add a geometry nodes modifier\n\n- Duplicate the object(=B), and use it's object info in the first objects geometry node\n\n- Connect object B geometry, position and ID into a sample index node, sampling a vector on a point\n\n- Subtract the vector coming from the sample index from object A's position\n\n- Connect the result to the offset\n\n- Try moving verts on object B in edit mode and see object A updating\n\n- Try moving verts on object B in sculpt mode. Object A is only updating when switching from sculpt mode back to object mode.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Hotkeys conflict between Shader Nodes, Compositing Nodes, GeoNodes and Texture Node Editor.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.6\n\nI have hotkeys on frequently used nodes in shader editor. When I switch to Compositing, first of all I have hotkeys already assigned to similar nodes (I did it in shader editor, but they are automatically assigned in compositing). Secondly, I get an error in Compositing - Not a shader or geometry node tree.\n\n1) Apply the \"I\" button to the \"Invert\" node in the shader editor\n2) Switch to Compositing or Texture Node Editor\n3) Call the invert node with the I button\n\nYou get the following error \n```\nPython: Traceback (most recent call last):\n\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 138, in invoke\n result = self.execute(context)\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 129, in execute\n self.create_node(context)\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 92, in create_node\n node = tree.nodes.new(type=node_type)\n\nRuntimeError: Error: Cannot add node of type ShaderNodeInvert to node tree 'Geometry Nodes'\n\nNot a shader node tree\n\nlocation: <unknown location>:-1\n```\nbandicam_2021-11-26_16-53-56-020.mp4\nNode_Conflict.blend\n\n", "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", "Geometry Node: Viewer output for instance domain ignore if value nearest to 0.01\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4, 3.5\n\nGeometry Node: Viewer output for instance domain ignore if value nearest to 0.01\n\nIf you explicitly specify the instance domain, then with a value nearest to 0.01, the viewer will ignore the value input\n\n[2022-11-11 23-41-29.mp4](2022-11-11_23-41-29.mp4)\n\n\n- Put some intance to Viewer\n- Connect Float Value to Viewer set to instance domain\n- Test various floats (0.01 and 0.3)\n\nOr in attached file switch between couple of Viewer nodes\n[gn_viewer_value.blend](gn_viewer_value.blend)", "Extremely Long time delay using geometry nodes with simple mesh boolean node 37706ms\nOperating system: Linux-5.13.0-41-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.2.0 Beta\n\nExtremely Long time delay using geometry nodes with simple mesh boolean node and difference (it takes **37706ms** for the mesh boolean node to do a cylinder difference)\n\n\nI've included the blend file which shows the times when you change the item to do a boolean difference 1 cylinder/count to 2 cylinder/count. \n\n**When I use the Boolean Modifier this time lag doesn't occur**. I've included this in the blend file for testing also.\n\n**PS: this time lag also occurs in Blender 3.1.2**\n\n\n\n[prego lid gn.blend.zip](prego_lid_gn.blend.zip)\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.*", "Cycles volumetrics mesh intersections visible when volume's shape does not match its mesh\nOperating system: tested on Windows 10 ; Linux Mint 20.2\nGraphics card: tested on GTX 1070 ; RTX 3090\n\nBroken : tested on 2.80 to 2.93 (official) and 3.0\nWorked : None\n\n**Description of error**\nCycles volumetrics mesh intersections are visible when the volume shape (density) is modified by nodes.\n\nIntersection example :\n \n\nOther example with .blend :\n\n[volumetric_bug.blend](volumetric_bug.blend)", "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", "Node Socket Name Change results in Cycles Material Rendering Black (name is also identifier, should be read-only?)\nWindows 10\nIntel Core i7-5820k 4.1GHz\n2x Nvidia GTX 970\n\nBroken: 2.79 5bd8ac9\n\nIf you change the name of a Node Socket (not the socket's identifier) of a Cycles Shader Node during execution of a python script, Cycles will render the Material black. \n\nDownload the blend file below:\n[socket_naming_bug.blend](socket_naming_bug.blend)\n\nRun the code in the text editor. \nSwitch to viewport preview.\n\nTo fix the problem, simply reset the two nodes, or add a new Material Output Node and a new Principled Node to the Node Tree. Connect the new nodes together and delete the old ones. \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)", "When changing the node type in material, sockets of different node types are reused\nOperating system: MacOS\nGraphics card: Apple M1\n\nBroken: main\nWorked: don't know\n\nShader nodes that have the same input sockets can have different default values.\nBut if you switch between shader nodes in the material interface, then the default values will first of all be copied from pre-existing socket of a node of a different type. Because of this, default values may not be used and may look strange.\n\nIn the default scene, assign Glass BSDF material to the default cube, and check the \"Roughness\" field. Now assign another material without \"Roughness\", such as Hair BSDF, then assign Glass BSDF material again and check the \"Roughness\" field.\n\n", "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)", "Index of Nearest geometry node outputs negative index values (-1).\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken:\nversion: 3.6.1\nversion: 3.6.0\nversion: 4.0.0 Alpha\n\nWorked: unknown.\n\nIndex of Nearest node outputs negative index values when its Group ID input is connected to the index output of another Index of Nearest node.\n\n\n\nIn a new Blender file, add a GN modifier to the default cube (almost any mesh works), add an Index of nearest node and connect its index output to the Group ID input of another Index of nearest node. Preview the output index of the second node using the viewer. In the spreadsheet editor, one or more -1 values will appear in the Viewer column.\n\nThe attached file has the described setup. Notice the bug happens with basically any mesh, and the amount and location of negative indices is random / unexpected.\n\nThis might be intended and useful behaviour, it's probable an index of -1 indicates no index has been found, but this doesn't seem to be documented in the manual.", "Geometry Nodes: Rendered glitch with Image Texture and Scene Time\nOperating system: Linux-5.15.0-76-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.0\nWorked: Never\n\n**Short description**\nGeometry nodes that use single images or image sequences are rendered inconsistently but usually look normal in the viewport.\nHigh-res images seem to be more unstable.\nHaving a connected/unconnected scene time node in the geo node group while using an image sequence with any number of frames also makes the rendered image/animation more unstable.\n\n|Expected render|Occasional render glitch|\n|--------------------------|--------------------------------------|\n|| |\n\n\n**Reproduction steps**\nThis is the most unstable setup:\n\n1. Create new project\n2. in the image editor window add a new image with resolution of around 1080x1080 pixels and set the source an image sequence \n3. add geometry nodes modifier to the default cube\n4. follow this node setup; in the image texture node use the created image sequence \n5. Render animation\n6. some of the rendered images will be glitched\n\nI've also tested this approach with face extrusion or instance selection instead of deleting faces. The resulting renders were also glitched. \n\nInside of this zip file is a blender project with a similar setup along with some sample images:\n[geo node groups that use images are rendered inconsistently.zip](attachment)\n\nThis reddit post seems to be describing a similar issue:\ngeometry_nodes_rendering_glitch_info_in_comments/\n\nThe workaround with disabling geo nodes modifier in the viewport mentioned there seems to be working in a simple setup. In the above project from the .zip file it is less effective.\n\n" ]

[ "Material not showing of geometry node Object\n\nBroken: 2.93 Daily 6.4.2021\n\nMaterial not showing in Object mode of geometry nodes Object, unless the geometry Input is joined at the top of the join node.\n\nWorking:\n\nNot working:\n\n\nCreate Object\nAdd Material\nAdd Geometry nodes\nAdd primitve node\nJoin Input Geometry with primitive Node" ]

[ "Node link drag search in shader editor doesn't filter by render engine compatibility\nOperating system: macOS-11.6.2-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-16.5.7\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't think ever. The feature was introduced in 3.1: 11be151d58\n\nOther than the default node search menu ( {nav Add > Search...} ) the link drag search doesn't filter out nodes that are not compatible with the current render engine.\n\n[node-link-drag-search-bug.mp4](node-link-drag-search-bug.mp4)\n\nAs shown in the video:\n- open the default blend scene with factory settings\n- switch to the shader editor\n- add a *Value* or *RGB* node\n- drag from the node's output and release the link on the canvas to activate the link drag search\n- look for the \"Toon BSDF\"\nResult: inputs from the node appear in the search despite the node not being supported by Eevee.\n\nHere's the simple setup from the video.\n[node-drag-link-search-bug.blend](node-drag-link-search-bug.blend)\n\n", "Fix bad behavior of Armature Join operator\nCurrently, armature 'Join' operator empties its source Armature IDs, while not deleting them. This is both fairly useless, and inconsistent with other 'Join' operations on e.g. Meshes, which do leave source obdata untouched.\n\nIt should instead probably operate on temporary out-of-main copies of the source armatures data, and also leave the original data unchanged.\n\nAlternative option would be to effectively delete the emptied source armature IDs, together with all the objects using them, but this is probably not the desired behavior either.\n\nIssue revealed while investigating #96452 (Armature corrupted after undo), see also [#96452.blend](T96452.blend) for a reproducible case.", "Compositor: Continously add/remove for cryptomatte.\nSource: 24223\n\nPROBLEM\n\nSometimes when using Cryptomatte the objects to isolate and divide into various passes can be a lot, and the process becomes tedious because you can only Add or Remove one object per time, then go back to the Cryptomatte node and click the + or - icon again, slowing a lot the process. Instead, it would be way more handy being able to select multiple specific objects.\n\nSOLUTION\n\nHave Add and Remove to work with multiple clicks, and then press Esc to go out of the selection mode when needed.\n\nNOTE: although categorized as good first issue, it might require more changes than expected as UI code is shared with color picker. Of course the color picker workflow should not change.", "Node groups' new method doesn't throw errors at inputs and outputs collections\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.1.0 Alpha\n\n\nNode groups' new method doesn't throw errors at inputs and outputs collections\n\n1. Create a geometry nodes modifier, get node group:\n\n```\nnodes = C.object.modifiers[0].node_group\n```\n\n2. Add new input or output by command \n\n```\nnodes.outputs.new(\"RGBA\",'new')\n```\n3. Note that there are no errors, but a new socket hasn't been created. \n\n\n\n", "Math with Nodes\nCurrently, there are two main math nodes: \"[Float] Math\" and \"Vector Math\". The current workflow for using these is that first the correct math node has to be inserted, and then the correct operation has to be selected. This approach has two problems:\n- It forces the user to do two steps for an operation that should only take a single step (e.g. \"insert multiply node\").\n- \"Math\" is a very generic term. When more operations are added, it becomes more and more unclear which should be added to the math node and which belong to another node. And the user has to remember that.\n\nA more scalable approach is to remove the \"Math\" node entirely and create individual nodes for different operations. For example, there will be an \"Add\", a \"Subtract\" and a \"Dot Product\" node. These new nodes can adapt to the data types that are connected to them.\n\nThis is not a change we have to do in the short term, but in the long run it is the better solution in my opinion. Especially as we get more types and operations.", "Broken/weird Continuous Grab behaviour\nOperating system: Linux-5.8.0-43-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: SVGA3D; build: RELEASE; LLVM; VMware, Inc. 3.3 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.93.0 Alpha\n\nbroken/weird behaviour under VMWare Player/Workstation 14.1.2+, Ubuntu 20.04.2 LTS\nEdit -> Preferences -> Input -> Continuous Grab\n|[2021-02-27 03-11-16.mp4](2021-02-27_03-11-16.mp4)|[cursorbug.mp4](https://archive.blender.org/developer/F13560997/cursorbug.mp4)\n| -- | -- |\n\n- activate grab mode (G-key) in the viewport or in any blender's area which support 'Continuous Grab'\n- drag mouse toward area top or bottom edge\n\nAlternatively:\n- Active walk navigation and quickly move the mouse outside of the Blender window. \n", "Regression: NODE_OT_add_search ignores NodeItems entries\nBroken: 3.4\nWorked: 3.3\nCaused by bdb5754147\n\nNodeItems entries are not taken into account when using the node `Shift+A` search functionality.\n\n- Load and register the `Python > Custom Nodes` script template.\n- Use the `Shift + A` search functionality.\n- In 3.4 `Node A` and `Node B` are missing.\n\n| 3.3 | 3.4 |\n| -- | -- |\n|  |  |\n\n**Reproduction File**\n[NodeItemsSearchRegression.blend](NodeItemsSearchRegression.blend)\n\n**More Context**\nIn Malt (https:*github.com/bnpr/Malt), we generate most nodes from a few node classes (https:*github.com/bnpr/Malt/tree/Development/BlenderMalt/MaltNodes/Nodes) and auto-generated GLSL reflection data. \nWe also use NodeItems to allow searching directly for node drop-down subcategories. (ie. you can search directly for `Dot Product`, instead of searching for `Vector` and then selecting the `Dot Product` option) \nBut none of this works in 3.4", "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", "mouse events from ui gets to running modal operator when should not\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\n\nBroken: version: 3.2.0\n\nrunning modal operator get left mouse press event when ui menu is double clicked on empty space. single click does not propagate, but double click (fast clicking or double click function on wacom pen) is reduced to single click and sent to operator while it should not be noticed. see video. i mix single clicking and double clicking on blank space in popup menu/panel so not always there is event to print out.\n\n[click.mp4](click.mp4)\n\nrun blender from terminal, load code in text editor, run code, search for operator, run operator, open some popup menu, try double or single clicking on empty space while watching event prints. works on grayed out regular menu items as well.\n\n```\nimport bpy\n\n\nclass ModalTestOperator(bpy.types.Operator):\n bl_idname = \"view3d.modal_test_operator\"\n bl_label = \"Modal Test Operator\"\n \n def __init__(self):\n print(\"start..\")\n \n def __del__(self):\n print(\"end.\")\n \n def modal(self, context, event):\n if(event.type in {'ESC', }):\n print(\"exiting..\")\n return {'CANCELLED'}\n \n print(event.type, event.value, )\n \n return {'PASS_THROUGH'}\n \n def invoke(self, context, event):\n print(\"invoke..\")\n \n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n\n\ndef register():\n bpy.utils.register_class(ModalTestOperator)\n\n\ndef unregister():\n bpy.utils.unregister_class(ModalTestOperator)\n\n\nif __name__ == \"__main__\":\n register()\n```", "Node Operators: Show node group inputs in redo panel\n_No response_\n\n", "Generated Texture Coordinate Node In Shader Creates Broken Pattern Upon Applying Subdivision After Armature Modifier \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.1\nWorked: Blender 3.2\n\nWhen I use the Generated value of a Texture Coordinate node, and have a modifier stack with an Armature above and a Subdivision below, it creates a really weird result [broke.blend](broke.blend)\n\n\n - Check the .blend file and simply activate the Subdivision modifier on the model\n\n\n\n\n", "Mismatch between nodetrees when creating a link does not throw error\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 531.41\n\nBroken: version: 3.6.0 Beta\nWorked: Tested as far back as 3.3.4 and no error was thrown\n\nWhen creating a node-link an error is not thrown if the node trees of `links`, `input socket`, and `output socket` are not all the same node tree or even the same type! It makes troubleshooting code sometimes difficult when no errors are thrown but with unexpected results.\n\nPaste the following into the text editor in Blender and Run it:\n\n```py\nimport bpy\n\nD = bpy.data\n\nnt1 = D.node_groups.new(\"NT1\", \"GeometryNodeTree\")\nnt2 = D.node_groups.new(\"NT2\", \"ShaderNodeTree\")\nnt3 = D.node_groups.new(\"NT3\", \"CompositorNodeTree\")\n\nnd1 = nt1.nodes.new(\"NodeReroute\")\nnd2 = nt2.nodes.new(\"NodeReroute\")\n\nnt3.links.new(nd1.outputs[0], nd2.inputs[0])\n```\n\n", "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.", "Make Thumbnail Dragging More Reliable\nOn some systems, the dragging is very glitchy and keeps invoking box selection instead.", "popup window call operator will crash blender\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.2.0 Beta\n\nThis script is use to check the active material, it can be run correct in the main window, but not popup window(change the pref window to node editor)\n```\nimport bpy\n\nbpy.ops.screen.userpref_show(\"INVOKE_AREA\")\narea = bpy.context.window_manager.windows[-1].screen.areas[0]\n\n\narea.type = 'NODE_EDITOR'\nflip_header = True\narea.ui_type = 'ShaderNodeTree'\narea.spaces[0].node_tree = bpy.data.materials['Material'].node_tree\n\nfor region in area.regions:\n if region.type == 'HEADER':\n with bpy.context.temp_override(area=area, region=region):\n if flip_header: bpy.ops.screen.region_flip('INVOKE_DEFAULT') # this line will not\n\n if region.type == 'WINDOW':\n with bpy.context.temp_override(area=area, region=region):\n bpy.ops.node.view_all(\"INVOKE_AREA\") # this line will report context error\n```\n\n- Open .blend file\n- Execute script\n[#98491.blend](T98491.blend)\n\n\n\n" ]

[ "Node Editor: Node Actions not started from the mouse are directly confirmed\nOperating system: Linux-4.15.0-52-generic-x86_64-with-Ubuntu-18.04-bionic 64 Bits\nGraphics card: AMD Radeon (TM) Pro WX 7100 Graphics ATI Technologies Inc. 4.5.13542 Core Profile Context FireGL 18.50.1.418\n\n\nBroken: version: 2.80 (sub 74), branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: (optional)\n\n\nWhen performing actions on mouse from a keyboard ('G' or 'Shift-D' for example), the actions are confirmed directly. I was able to reproduce this issue in any node editor. (Shader, Compositor etc)\n\n\n\n1. Open a node editor\n2. Select a node\n3. Perform an action starting from a key stroke (`Shift-D` for example)\n\nThe node is duplicated but depending on actual type of node the node might be placed exactly on top of the previous node. I would expect that the user could move the node around and confirm it by himself.\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 2.92.0 crashes when baking steam simulation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\nCPU: Intel Core i7-8700K\nMemory: 32 GB\n\nBroken: version: 2.92.0\nWorked: I have not tried any other version than 2.92.0 (sorry)\n\nI tried to make a simple steam simulation following the steps described here: watch?v=_K0XsHht6pg. It crashed while baking, and tried to simplify the setup with a minimal set of objects, and it still crashes after baking about 30-50% of the 300 frames.\n\nFollow the steps as described in the video watch?v=_K0XsHht6pg\n\nAttached is .blend file that I tried to make as simple as possible: [steam.blend](steam.blend)\n\n - Open the attached file\n - Press \"Bake Data\" for Physics Properties for the cube\n - Blender crashes after 30%-50% of baking\n\nI have not tried a newer experimental release or an older release.\n\nI was able to reproduce the issue with the default 32 Resolution Divisions (which is way faster to reproduce than the 160 in the included file). I then tried experimenting which exact setting caused the crash. I got it to crash with Adaptive Domain disabled, and Gas Heat 1.5 and Dissolve Time 30, but now I'm not able to reproduce anymore with any setting (at least with 32 Resolution Divisions).\n\nAfter some more experimenting, it seems it randomly crashes and sometimes works. It is definitely reproducible with 32 Resolution Divisions. I kept all settings as I had before, which had worked successfully, but then changed the Time Scale to 0.8, and then it crashed again when baking. However, it had previously crashed at least once with the exact same settings with which I had also successfully baked (and the Time Scale at the default 1.0), so it is not the Time Scale that is causing the issue.", "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", "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", "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?", "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", "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)", "EEVEE: Crash if computation is too heavy for the system (TDR issue)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nAny time I try to render an image sequence in any format in Eevee, it constantly crashes the whole program on the first frame. I was able to render before until I changed some camera location animations and adding a focusing animation. As well as changing the camera sensor size. I am rendering in 4K I have attached the log file.\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[NebulaV2.blend](NebulaV2.blend)", "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 - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "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 3.5.1 + Mac + Metal + Crash\nOperating system: MONTEREY 12.6.3\nGraphics card: AMD Radeon Pro 5500 XT 8 GB\n\nBroken: Blender 3.5.1\nWorked: Blender 3.4.1\n\nBlender 3.4.1 will render a given scene with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" in 1 min 58 sec\n\nBlender 3.5 and 3.5.1 will crash on the same scene set on \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" - \nIt has to be run with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"CP\" and now takes 5 min 53 sec.\n\nI have lost computing power with the latest versions.\n\nJust run the file with GPU BACKEND turned on and \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\"\n\nI could not include the file as it is a project I am working on - if there is no other way to check up on this issue I will try to create another file that I can send\n\n", "Segfault in CustomData_blend_read\nOperating system: Debian Linux, Stable\nGraphics card: GTX970\n\nBroken: 3.6.0 Alpha, branch: main (modified), commit date: 2023-04-05 18:55, hash: 92c9c1d4003e, type: Release\nWorked: Unsure. Old blend I loaded and worked on for a while. Errors on open now.\n\nSegfault on load.\n\n1. Load blend, or open blender and load blend\n\n(No idea what the gvfs error is.)\n```\nFailed to open dir (No such file or directory): /run/user/6001/gvfs/\n[New Thread 0x7fffe3ae9700 (LWP 2310937)]\n...\n[New Thread 0x7fffdb9fe700 (LWP 2310945)]\nRead blend: \"/tmp/segfault.blend\"\n\nThread 1 \"blender\" received signal SIGSEGV, Segmentation fault.\n0x0000000001009af9 in CustomData_blend_read (reader=0x7fffffffd498, data=0x7fffd9c471f0, \n count=5002)\n at /opt/src/blender-git/blender/source/blender/blenkernel/intern/customdata.cc:5194\n5194 if (layer->flag & CD_FLAG_EXTERNAL) {\n(gdb) l\n5189\n5190 int i = 0;\n5191 while (i < data->totlayer) {\n5192 CustomDataLayer *layer = &data->layers[i];\n5193\n5194 if (layer->flag & CD_FLAG_EXTERNAL) {\n5195 layer->flag &= ~CD_FLAG_IN_MEMORY;\n5196 }\n5197\n5198 layer->flag &= ~CD_FLAG_NOFREE;\n(gdb)\n```\n\n", "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.", "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" ]

[ "Cycles render crash Blender in some scene in versions >= f00f959 \nLinux mint 16 x64, 8GB \nBroken: (2.69.7 f00f959 and more new)\nWorked: (f86fbc4)\n\nwhen push Animation render button in scene (26264) it close lender; if Blender was started from terminal it contain a message about Segmentation fault; Type of Cycles render CPU/GPU has no mean..\n\nOpen .blend file 26264. press \"Animation\" button as for sequence render. :(\n" ]

[ "Gradient weight tool confusing (using previous tool brush)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nGradient Tool in its current state is not very user friendly:\n\n- generally this accesses previously selected tools brush as it doesnt have its own brush (so it looks like it has its own settings for strength/weight, but those are from an 'alien' brush) when `Unified Weight` is turned ON (default) the tool actually works with the `Unified Weight` (set on some other brush, e.g. the Draw Brush), but doesnt present you with that value in the UI (bug!)\n- when `Unified Weight` is turned OFF you are actually tweaking the weight setting of the previously selected tools brush (the 'alien' one) -- this causes confusion (it doesnt affect e.g. `Blur`, `Average` or `Smear` since these dont have weight capabilities)\n- this is even worse when tweaking the Strength, you are actually tweaking the weight setting of the previously selected tools brush (the 'alien' one), this affects `Blur`, `Average` or `Smear` (and Unified Strength is OFF by default!)\n\nSo not sure how to solve the issue with the \"tweaking setting of a seemingly unrelated brush\" issue, what I think we should do though is at least have the values in the UI respect Unified Weight / Unified Strength since this is what the tool will use internally...\n\nSo the main issue is fixed in f38c54d56e: Fix Vertex weight gradient tool show wrong weight/strength values in the UI.\n\n", "Armature modifier taking a performance impact, even when set to not be visible.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.2\n\nSome part of the Armature modifier is still calculating even when set to not be visible.\nCausing a performance impact, when an artist expects none. Other modifiers like Subdivision Surface do not have this issue.\n- unrelated, also kinda sucks that I get sub 24fps with 100k poly videogame ready models.\n\nHave a high poly model weighted and bound to an armature, with any simple animated movement. Take note of the viewport performance when viewing playback of the simple animation. Disable all visibility options on the Armature modifier on the model. Performance only increases slightly. Uncheck 'bind to vertex groups' on the modifier. See performance improve drastically, even though the modifier is set to not be visible in the first place.\n\nWith the attached blend file, a high poly model is already bound to an armature with a simple animation.\n[ArmatureModifierBug.blend](ArmatureModifierBug.blend)\n\n", "Vertex Selection Clipping Through Model\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.1\n\nWhen selecting vertices on an object, it will select the vertices on the face of the object and intermittently select all others behind as if in xray mode. \n\nGrab or scale icing vertices and pull.\n\n", "Bone Heat weighting: failed (due to none of the vertices in an island being visible to any bones)\n**Win 10 64. gtx 970**\n\n**Blender 2.75a Hash c27589e**\n\n**Bone Heat weighting: failed to find solution for one or more bones**\n\nI attach the blend file and two prints..\n\nAlso the same broblems apper when i try to \"assign automatic from bones\" by individual bones in Weight Paint. Like one by one. Please see print2.\n\n\n\n\n\n[cat.blend](cat.blend)\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`.", "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", "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)", "Texture paint: Bleedind around thin cuts do not fill texture\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\nWorked: never?\n\n\n1. Wider distance allow to overlap color\n2. closer distance between faces do not\n3. closer distance between islands allow to overflow to neighbour island…\n\n\n[bleeding test.blend](attachment)\nopen file, try to paint as seen in the [video 2023-03-24_05-09-32.mp4](attachment)\n\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", "Unable to select certain vertices (regression from 2.79)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nSome vertices are impossible to select.\n\nAt first I thought it was because the vertices formed a concave area (see first file) but then I hit a second concave case (see second file).\n\n\nWithout rotating or zooming the view try to select one of the marked vertices in both files.\n[Select1.blend](Select1.blend)\n[Select2.blend](Select2.blend)\n\n----\n\n2.79 worked in this case, open this file in 2.79 to test.\n\n[Select1(1)_279.blend](Select1_1__279.blend)", "Curve sculpting: occlusion by hidden parent makes the curves unresponsive to brushes.\nOperating system: Fedora Linux (Gnome Wayland)\nGraphics card: AMD\n\nBroken: 3.5.1\n\nSculpting the curves is not possible when hiding the parent and \"occluding\" the curves with the now invisible parent.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nAdd empty hair to the cube.\nAdd curves in sculpt mode.\nHide the cube.\nTry to sculpt the curves from the other side of the cube. \nDragging from inside the hidden cube and dragging from outside the hidden cube give different results, when it feels like it should not.\n\n", "Can't select bone while Weightpaint with Face PaintMask\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0\nWorked: Never (2.79+)\n\nBones can't be selected while in Weightpaint mode and Face Paintmaks option is activated.\n\nBased on the Select with Left Mouse button option and Default Blender Keymap:\n\n[PaintMaskAndWeightPaint.blend](PaintMaskAndWeightPaint.blend)\n\n1- Open the attached file called PaintMaskAndWeightPaint.blend\n2- You see the Cube rigged with 2 bones already in pose mode and cube in Weightpaint mode\n3- You can change Bone selection while weightpainting pressing the CTRL + LMB (Left Mouse Button), there is any problem for now\n4- Now, if you activate the Face Paint Mask button at the top-left and try to select another bone like before pressing CTRL+LMB on a bone, bone will not be selected, instead of that, you select a face mask. \n5- If you go to keymap options, and deactivate the option \"**Select**\" from \"**Weight paint**\" to avoid select faces with CTRL + LMB, now if you try to select another bone, it will not select another mask face, but it will not select the new bone and will exit the Weight Paint mode.\n", "Split up pose mode keymap to avoid weight-paint conflicts\nCurrently the \"Pose\" keymap us used in combination w/ weight paint.\n\nThis means we can't add key bindings for animation that conflict with weight painting for eg. F-Key. See: #63667 (Keymap: Weight Painting using the Pose Mode keymap)\n\n----\n\nProposal:\n\n- \"Pose Generic\" for basic selection operations.\n- \"Pose\" for more advanced animation actions.\n\n\"Pose Generic\" would co-exist with weight paint mode when weight painting is mixed with pose mode.", "Solidify cause wrong vertex selection in edit mode\nLinux-4.19.0-12-amd64-x86_64-with-debian-10.6 64 Bits\nMesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.3.6\n\nWindows 10-10.0.19041 SP0 64Bit\nGeForce 9600 GT PCIe SSE2 Nvidia Corporation\nRadeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.80 (sub 75)\nBroken: version: 2.83.2\nBroken: version: 2.90.1\nBroken: version: 2.91.0 Beta\nWorked: unknown\n\nIn 3d viewport, vertex selection, solid mode, X-Ray off, you cannot predict what you are selecting when using solidify:\nBlender is ignoring the X-Ray (\"Allow selecting through the items\") and is selecting, randomly, occluded items.\nHaving a very narrow clipping does not mitigate the issue.\n\nExplanation video [SelectLight.mp4](SelectLight.mp4)\n\n[#82182.blend](T82182.blend)\n\n- Open file\n- Click inside blue circle\nOccluded vertex will be selected\n", "Bone selection icon could be added next to Face and Vertex Selection in Weight Paint mode\nHello. I want to suggest to add a Bone Selection icon in weight paint mode by side the face and vertex selection modes. It intents to be a better feedback on what selection mode the artist is using. Now it is like having only face and edge selection icons for mesh editing but not vertex because it is the \"default\" tool. I know the bone selection is not a mask tool like the face and vertex selection, but, at the end, all 3 are just selection modes for the artist workflow.\n\nCheerios\n\n" ]

[ "Vertex paint: polygon selection in X-ray mode do not select back faces\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\n\n\nI suppose it is a bug, because , box selection + x-ray have differend behavior in edit mode.\nPlease check. Bug or flaw?\n[2020-01-23_08-12-52.mp4](2020-01-23_08-12-52.mp4)\n[vertex paint polygon selection.blend](vertex_paint_polygon_selection.blend)" ]

[ "Volumes look much much different in master compared to 2.79b\nWindows 10 pro x64\nGTX 970\nThread Ripper 1950x\n\n\n\nBasic volume shader with noise texture from build bot today doesnt look the same as 2.79b\n\n\n\n[untitled.blend](untitled.blend)\n", "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", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Blender 2.8 Splash Screen Design\nFor Blender 2.8, we want to make some improvements to the splash screen. \n\nOne of the main things we want to do here, is to provide an easy way to get started with various *types* of projects. You'll want a different setup if you are doing a 2D animation project, than if you are doing sculpting. That means, both some different objects in your scene, but also a different starting Workspace, and perhaps other things too.\n\nThe other thing we want to include, are links to tutorial videos about learning Blender, and also about new features for each release.\n\nLastly, Blender has many obscure features that even many seasones Blender users don't know about. We want to surface those by showing users various random tips.\n\n\n\n\n\nVisual Example:\n\n\n\n\n## First Launch Setup Screen\nThe splash screen could also help making the setup process smoother when first launching Blender. There are several options and settings that users will want to easily configure once, such as the keymap, the language and GPU rendering. We want to make these settings more discoverable and accessible.\n\nThis means we can remove these items from the normal splash screen, to make it cleaner and simpler.\n\nPressing the Done button would lead users into the regular splash screen.\n\n\nOutline:\n\n\nVisual example:\n\n\n\nWe could then lead new users to a screen with several links to start learning Blender:\n\n", "GPencil: Selecting textured brushes will crash Blender\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92.0\n\nWhen appending the textured brushes from the [Blender Cloud](5ccfe64353b85e279cf72acd) into a file, Blender will crash when trying to preview the brushes in the tool settings.\n\n\n - Open Blender 2.93 and select the \"2D Animation\" template.\n - Go to *File*>*Append* and browse to the `pepeland_GP_brush_pack_V1.blend` file. Go into the *Brush* folder and append the brushes `GBrush_001` through `GBrush_010`.\n # Click the brush icon in the tool settings. Blender crashes.\n\n\n\n", "Blender 2.92.0 crashes when baking steam simulation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\nCPU: Intel Core i7-8700K\nMemory: 32 GB\n\nBroken: version: 2.92.0\nWorked: I have not tried any other version than 2.92.0 (sorry)\n\nI tried to make a simple steam simulation following the steps described here: watch?v=_K0XsHht6pg. It crashed while baking, and tried to simplify the setup with a minimal set of objects, and it still crashes after baking about 30-50% of the 300 frames.\n\nFollow the steps as described in the video watch?v=_K0XsHht6pg\n\nAttached is .blend file that I tried to make as simple as possible: [steam.blend](steam.blend)\n\n - Open the attached file\n - Press \"Bake Data\" for Physics Properties for the cube\n - Blender crashes after 30%-50% of baking\n\nI have not tried a newer experimental release or an older release.\n\nI was able to reproduce the issue with the default 32 Resolution Divisions (which is way faster to reproduce than the 160 in the included file). I then tried experimenting which exact setting caused the crash. I got it to crash with Adaptive Domain disabled, and Gas Heat 1.5 and Dissolve Time 30, but now I'm not able to reproduce anymore with any setting (at least with 32 Resolution Divisions).\n\nAfter some more experimenting, it seems it randomly crashes and sometimes works. It is definitely reproducible with 32 Resolution Divisions. I kept all settings as I had before, which had worked successfully, but then changed the Time Scale to 0.8, and then it crashed again when baking. However, it had previously crashed at least once with the exact same settings with which I had also successfully baked (and the Time Scale at the default 1.0), so it is not the Time Scale that is causing the issue.", "Double clicking particle system name (to rename) deletes pre-calculated particle animation.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\nBroken: version: 2.80 (sub 55)\nWorked: 2.79b \n\n\nDouble clicking particle system name (to rename) deletes per-calculated particle animation.\n\nOpen new blend.\nAdd particle system.\nSimulate a few frames.\nPause animation.\nRename particle system.\nParticle animation / cache is deleted / reset.\n\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.", "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", "Make App templates more versatile\n**This is a report for a feature/design request, asked by Campbell**\n\nI'm facing an issue with the way blender manages its python scripts. I'm working in a studio and we deploy Blender with an environment builder (Rez). Blender and all the applications we need for our artists are installed on a dedicated drive.\nCurrently, we use the env var BLENDER_USER_SCRIPTS to install our app templates into it with the appropriate directory layout. But users don't have the permission to write on the server, which is normal. But, this leads to errors because Blender needs to write presets, like keymaps in the user scripts/presets directory, causing errors.\nI've tried to use the BLENDER_SYSTEM_SCRIPTS but it requires to move every blender's modules into each application built upon Blender we need to launch, this is very heavy and dirty.\n\nWith @ideasman42, we talked about that a long ago, and I will try to define my need correctly regarding app templates:\n- Either I'd like to be able to start blender with --app-template /path/to/app_template_dir\n- Or having a new env var BLENDER_PROD_SCRIPTS (or whatever the name which suits it) where Blender will look in to load app templates and addons but never ask to write in.\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", "Driver Workflow Design\nFor Blender 2.8, we want to improve the workflow for adding drivers. Here's how:\n\n\n\n - When the user right-clicks on a property and adds a driver, we display a non-modal, persistent Add Driver floating popup. \n - While open, all of Blender remains responsive, and the user can select any object in the scene. \n # From the popup, users can select a property to use as as a driver. No other steps are needed.\n\n\n\n\nOptionally, users can then set a multiply and offset value, and add additional driver inputs. They can also click the Open Driver Editor button to open a Drivers window,\n\nUsers can also use the ID type picker to select from a list of Object and property ID's. They can also, using the eyedropper, directly select an object in the 3D View, or in the Outliner. When users select an object, they are presented with a basic list of commonly used properties, like so:\n\n\n\n\nIf the user has closed this window and wants to get it back, they can right-click on the property being driven and \nselect Edit Driver, like so:\n\n", "Seemingly no way to remap \"use tool\" button?\nBroken: 2.80+\nWorked: 2.79\n\nSee 599\n\nThere doesn't seem to be a way to remap or disable the button which activates the tools selected by the buttons found in the T panel. Sometimes this button conflicts with the 2.7x keymap. For example, in the node editor, left tweak *always* applies the selected tool (box select by default), which prevents all the 2.7x Left Tweak shortcuts from working\n\n\n[27_28_keymap.blend](27_28_keymap.blend)\n\n1. Open the file with --factory-startup\n2. Go to the keymap section in the preferences\n3. Select the 27X preset\n4. Try to use the Shift+Left Tweak shortcut to add a reroute node\n5. Box select will be invoked instead", "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", "--addons does not enable the relative addon checkbox\nWindows 7\n\nBroken: 2.79\n\nBy using [--addons ](https:*docs.blender.org/manual/en/dev/advanced/command_line/arguments.html)*add-on*, the checkbox in the UI of*Blender User Preferences*\"Add-ons\" page is not enabled for*add-on//.\n\n - type `.\\blender.exe --addons mocap`\n - open *User Preferences*\n - click *Animation* under *Categories*\n - search for *Animation: Motion Capture Tools*\n - verify the checkbox is not enabled for this addon" ]

[ "Installing 2.80 DELETES 2.79 even if installed to a different folder\nMy 2.79 was installed to: C:\\Program Files\\Blender Foundation\\Blender\\\nSo I installed 2.80 to: C:\\Program Files\\Blender Foundation\\Blender2.80\\\n\nI don't know if I missed a prompt, but the 2.80 install deleted all the files in C:\\Program Files\\Blender Foundation\\Blender\\ The ...Blender\\2.79 folder was still there, but all the files in that tree were gone as well. As a result I could no longer open Blender 2.79 (which I need until all my addons are ready). \n\nFortunately I was able to copy C:\\Program Files\\Blender Foundation\\Blender\\ from a backup. \n\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nInstalling 2.80 Deletes the 2.79 installation\n\nSee Above\n\n" ]

[ "Sculpt: Artifact in Multires when mirror modifier is applied\nOperating system: Linux-4.19.97-x86_64-x86_64-AMD_Athlon-tm-_II_X4_620_Processor-with-gentoo-2.6 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 1)\n\nArtifact in Multires when apply mirror\n\n4xYyu0y.png\n\n1. add multires\n2. subdivide 4-5 times\n3. make sculpt\n4. add mirror\n5. apply mirror\nor \n1. Open attached file\n2. apply the mirror modifier\n[multires_mirror_bug.blend](multires_mirror_bug.blend)", "Mesh to Volume intersection artifacts\nOperating system: Ubuntu18x64, Ubuntu20x64, Win8x64.\nGraphics card: Mesa DRI Intel(R) HD Graphics (BYT) Intel Open Source Technology Center 4.2 (Core Profile) Mesa 20.0.8\n\nBroken: version: 3.0, 3.1\n\nIntersecting Mesh to Volume produces artifacts (on CPU. GPU not tested).\n\n[volume-intersection.blend](volume-intersection.blend)\n - Open,\n - Run viewport Render Preview on the left side.", "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)", "Realtime compositor: Texture node output textures with artifacts\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nTexture node support was introduced in 151a53110c\n\nIn realtime compositor, Texture node outputs textures with artifacts.\n\n\n\nIt happens with most procedural textures I tested. This does not happen when a custom image is used, or when Blend texture is connected from the Value output (instead of the Color output) of the node. (With other textures it happens with both outputs.)\n\nThis does not happen when running Blender with a single thread (`blender -t 1`)\n\nFile for quick test: [TextureNodeTest.blend](attachment)\n\n", "Composited cycles render passes not matching combined output\nOperating system: Microsoft Windows [Version 10.0.19042.2251]\nGraphics card: Nvidia Quadro RTX 4000 (driver 512.36)\n\nBroken: 3.3.1 and 3.4.0\nWorked: Unknown\n\nCarrying out manual composition of the Cycles render passes as described in the Blender documentation is not resulting in the same result as the combined output.\n\nFig 1 shows the blender manual description of how passes are combined for the final output (edited by me with how I think the volume passes are included - the documentation doesn't explain this).\n\n\nFig 2 shows my compositor node tree that matches that description.\n\n\nFig 3 is the compositor output...\n\n...and Fig 4 is the combined noisy image output. If you click on Fig 3 or 4 to expan the image view then use the left/right arrows on your keyboard you can flick between these two images to clearly see the difference.\n\n\nNeither are denoised to eliminate that as a contributory factor (I used 4096 samples to keep noise low). Fig 5 highlights the regions where I'm seeing significant shading differences...\n\n\nFigs 6,7,8 are closer views of these regions.\n\n\n\n\nThe key issues (shown in Fig 5) are the missing shading around the sphere rim, and missing shading on the floor panels at the larger rib regions between the panels. The missing shading around the sphere rim is exacerbated when denoising is applied and those notches become more pronounced. All other regions appear to be the same to me.\n\nA potential clue: the issue might be originating with the DiffDir and/or the DiffInd passes, because the sphere rim highlight 'notches' and the darker regions on the floor panels are both visible when those two passes are multiplied in the compositor node tree (see Fig 9 showing viewer output from that multiply node).\n\n\nLoad the attached blend file and render in cycles (caution - its currently set to 4096 samples... you dont need to render it with as many samples to see the issue!). Compare the 'noisy image' output and the compositor output.\n[cycles_compositor_combine.blend](cycles_compositor_combine.blend)", "Low Roughness Value on Glass Material Causes Artifacts with GPU+CPU Renders\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 1070 NVIDIA 419.67\nCPU: AMD Ryzen 7 1700X\n\nBroken: version: 2.80 (sub 57)\nWorked: 2.79.6\n\nLight inside an object that has glass material with low roughness causes blocky artifacts on GPU+CPU Cycles renders. It renders fine either in GPU or CPU renders.\n\n\n - Launch Blender, delete light.\n - Add 3-4 level subdivision surface modifier to the cube and enable smooth shading.\n - Add Glass material to that object and set low roughness value (below 0.2)\n - Add Light inside that object.\n # Bring camera closer and render.\n\n\n[glass_light_render_bug.blend](glass_light_render_bug.blend)\n", "render lagging behind tiles\nOperating system: win10\nGraphics card:rts 2070 super\n\n2.81\nwhen rendering, the picture doesnt appear for a while after the render tile already finished rendering that region, not sure if its a bug. didn't see anything like this online. here is a video\n\n\n[bug (2).blend](bug__2_.blend)\n\n- Open file and render\n\n[gnVknluHJZ.mp4](gnVknluHJZ.mp4)", "No error prompted when Cuda fails during GPU bake\nOperating system: Linux Debian 10 (buster) - kernel 4.19.0-19-amd64\nGraphics card: GeForce GTX 1060 Mobile\n\nBroken: 3.1.0\nWorked: -\n\nWhen you try to bake, having GPU set as compute device, and CUDA has an error, no error is shown.\nYou only notice the error when you try to render and get \"*Failed to create CUDA context (unknown error)*\"\n\nIt is useful to show an error, in the same way that, for example, \"Circular dependency for image...\" is shown during the bake.\n\nNote that this report is not about the error itself. It is about Blender not reporting any errors during baking, which causes user confusion.\n\nThank you,\nRiccardo", "Strange Cycles Area Light artifact when using Motion Blur in animation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nPer the attached screenshot, two astronauts are at the windows of a moving spacecraft. There are four Area Lights inside the spacecraft between the astronauts and windows acting as fill lights for the astronauts. The strange artifact appears when Motion Blur is enabled, causing the Area Lights to appear to be moving at a different velocity from the spacecraft. The result is that the Area Lights themselves become visible, especially the green light at the far left window; in reality it's behind the post between the windows.\n\nIs this a known issue? If yes, any way to fix it short of disabling Motion Blur? Thanks.\n\n\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", "\"Illegal address in CUDA queue\" error occurs when I use both Principled BSDF and Adaptive Subdivision\nOperating system: Windows 11 Pro 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\n\n-**\"Illegal address in CUDA queue\"** error occurs when I activate both Principled BSDF and Adaptive Subdivision at the same time.\n-It would work fine if I don't use both at the same time.\n-Here are the possibilities of the error occurring when I use different settings:\n1. Principled BSDF + Adaptive Subdivision = **error**\n2. Texture Coordinate surface + Adaptive Subdivision = **no error**\n3. Principled BSDF + NO Adaptive Subdivision = **no error**\n\n-I can use a high poly count without Adaptive Subdivision *(e.g. Level viewport = 7)*, works fine. But as soon as I turn it on *(even with low poly count, e.g. Dicing scale = 1)* combined with Principled BSDF, the error occurs.\n\nIn the file I sent, I've already activated Principled BSDF + Adaptive Subdivision, you need to turn on the \"Rendered Viewport Shading\" and then slide the Scale parameter of the Noise Texture very quickly and the error should occur.\n", "Line artifacts in Mantaflow smoke sim when using \"Noise\"\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.08\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nWhen Noise is activated in a Mantaflow smoke sim, hash line artifacts show up in the early frames of the sim. \nWith Noise active:\n\nWith Noise switched off:\n\n\nHere's the .blend file: [mantaflow_2.81_problems.blend](mantaflow_2.81_problems.blend)\n\nCreate mantaflow smoke sim, bake smoke, bake noise, notice artifacts. \n\n", "Artefacts with volume motion blur\nOperating system: Linux-5.15.0-25-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 Super/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.0 Alpha\n\nWhen rendering VDBs with motion blur, I get a lot of artefacts in the shadows (?), especially when rendering with the GPU.\nThese artefacts look the same on Windows and Linux with different nVidia cards (RTX 2070 and GTX 1080ti).\nHere's an example MP4 of how they look in an animation (watch the dark splotches on the floor plane):\n\n[VB_GPU_MB.mp4](VB_GPU_MB.mp4)\n\n- Unpack and open the attached blend file\n[Volume_MB_Bug_v01.zip](Volume_MB_Bug_v01.zip)\n- Press F12 to render, by default it should use GPU + motion blur:\n\n- Switch off motion blur:\n\n- Switch to CPU and turn motion blur back on:\n\n- And finally CPU without motion blur:\n\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)", "Z-fight with invisible face in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nWorked: \n\nI have 2 cubes. Bigger one is set viewport display as wire. Both share the same XZ plane. In Object mode shading is fine, but if I enter in Edit mode with smaller cube artifacts are appear.\n\n[ladder_01.blend](ladder_01.blend) \n\n" ]

[ "CUDA Devices GPU+CPU and Adaptive Sampling enabled leads to visual differences in tiles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.90.1\n\nWhenever I enable not only my GPU-Devices in the Preferences in the CUDA Tab, but also my CPU (TR 1950x in that case) and additionally enable Adaptive Sampling, Cycles Renders the some Tiles differently. \n\nEnable CUDA in Preferences\nEnable all available Devices CPU+GPU\nEnable Cycles GPU \nEnable Adaptive Sampling\nRender\n\nPlease see the images and a simple .blend file attached. Let me know if I can be of any help. \n\n\nBest, \nElmar \n\n[Cycles.blend](Cycles.blend)\n\n", "Tile Stealing + AS + Transparent BG produces alpha artifacts\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: 2.92.0 Alpha\nWorked: Any Version before the Tile-Stealing patch\n\nTile stealing with adaptive sampling + transparent background can mess up the alpha channel and the sample count.\n\n\n\n\n1. New Scene\n2. Load factory Settings\n3. In settings, enable Cuda with both CPU and GPU\n4. Set the render engine to Cycles and switch to the GPU Device\n5. Set the Render samples to something high like 2048\n6. Enable Adaptive Sampling with a low Threshold like 0.001\n7. Under \"Film\" enable Transparent\n8. Add a Sky Texture (Nishita) as an Environment Map (just to bump up the rendertime)\n9. Render (sometimes a couple of renders are needed to show the bug)\n10. If the GPU steals some Tiles, the Alpha channel can get corrupted and shows splotchy spots where the Alpha should just be solid. The \"debug Sample Count\" Pass also shows more samples for these Tiles.\n\nDisabling adaptive sampling seems to fix it.\n\n", "Missing render tile\nOperating system: Windows 10\nGraphics card: GTX 3090\n\nBroken: blender-2.92.0-c9efb5424079-windows64\n\n\nIt seems like there is a missing render tile in this scene. See the image for the issue.\n\n\n\n\nLoad the attached scene and render it.\n\n[asdsad_18122020_1057_45.blend](asdsad_18122020_1057_45.blend)\n", "Artifcats with adaptive sampling while using optix/cuda on both cpu and gpu | Daily build: 9c074548165a\nOperating system: Windows-10-10.0.20221-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09\nCPU: Ryzen 2700x\n\nBroken: version: 2.92.0 Alpha, Daily build: `9c074548165a`\nWorked: feature not in old versions\n\nWhen rendering out the junkyard scene at 2x resolution, 500 samples and the Open Image denoiser in the compositor and adaptive sampling on when the gpu takes over tiles unfinished by the cpu artifacts are generated when complete.\n\nArtifact with Denoiser on: 4NYFNG3.png\nArtifact without denoiser: B9pWZr8.png\nArtifact with no compositing: U4fA8wH.png\nArtifact mid render: 6KB22Yy.gif\nSame issue in cuda: DBMbeCb.png\n\n1. download junkyard scene\n2. set samples to 500\n3. untick the denoise option (Optional)\n4. enable Optix/Cuda on both cpu and gpu\n5. enable denoising information in the render layers (didnt test if optional)\n6. add the denoise node in compositing and connect it to the node group in place of colour (Optional)\n7. render out and look at cpu tiles taken over by gpu when complete", "Strange rendering results\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.92.0 Alpha\nWorked: 2.90.1\n\nIt's the second time that when I try the new 2.92 alpha, when I render a scene even fairly simple, a couple of buckets, that just finished to render a part of the image, go back there where they just finished and add some noise to it. This time it also happened that they erased part of the background. Unfortunately it happened only two times while other times the render went fine, so I'm unable to reproduce, I can only say that Optix denoiser is enabled.\n\n\nI don't know how to reproduce, I only think that it might be connected to the new \"GPU tiles stealing feature\" or to optix denoising.\n\n[Rendering bug.blend](Rendering_bug.blend)\n\n", "CUDA+CPU in cycles with Adaptative Sampling causes wrong tiles.\nOperating system: Linux-5.4.75-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.80.02\n\nBroken: version: 2.92.0 Alpha\n\nUsing CUDA+CPU in cycles with Adaptative Sampling leads to some weird tiles.\n\nJust enable the CUDA + CPU in the settings and Adaptative Sampling, even rendering the default cube will have this issue.\n\n\n I guess it's related to the tile stealing because it only happen with some of the last tiles on being redered. ", "OptiX GPU+CPU and CUDA GPU+CPU rendering problem - CPU tiles not correctly rendered\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: blender-2.92.0-caed4849d090-windows64 (CUDA GPU + CPU worked)\n\nWhen rendering with CUDA + CPU or the new feature OptiX GPU + CPU there are render artefacts. Seems like the CPU Tiles are not correctly rendered.\nCUDA GPU+CPU worked before but since the new feature Optix GPU + CPU was added, not anymore.\n\nOpen the attached blend file.\n[Optix_GPU+CPU_test.blend](Optix_GPU_CPU_test.blend)\nGo to Edit > Preferences > System > Cycles Render Devices - set to CUDA GPU +CPU\nRender > Render Animation\nSee that some tiles are not correctly rendered.\n\nGo to Edit > Preferences > System > Cycles Render Devices - set to OptiX GPU +CPU\nRender > Render Animation\nSee that some tiles are not correctly rendered.\n\n\n\n" ]

[ "Limit scale bone constraint: \"affect transform\" doesn't seem to work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: **2.83**LTS from steam, **2.92**release and **2.93.0**Alpha\nWorked: don't know\n\nContrary to the manual, the \"affect transform\" option does not limit the transform values (not visible).\nAlso when using limit scale as a bone constraint the minimum scale is not used, instead uses maximum as both being the min and max exactly the same number but in negative value.\n\n- Open attached file\n- Scale the bone beyond the limits\nNote that the scale values in the transform panel have not been clamped.\n[scale bone.blend](scale_bone.blend)\n", "Add support for 'editable but not saved' properties for liboverrides\n**Status:** WIP\n\n---\n\n**Team**\n**Commissioner:** @SimonThommes \n**Project leader:** @mont29 \n\n**Description**\n**Big picture:** A few properties of linked data are still editable by the user (though not saved on disk), using the `PROP_LIB_EXCEPTION` RNA flag. A similar behavior could be useful for overrides too.\n\n**Use cases**:\n* Deal with temporary not-really-working material overrides cases (it is currently possible to override the active material, however if assigned to obdata and said obdata is not overridden, this will break materials assignments.).\n* On a larger perspective, allow finer control over some properties when using override.\n\n**Design:**\n* `?` *Mental model, end user usability, paradigms, mockups.*\n\n**Engineer plan:**\n* `?` *Abstract code samples - linked here, UML, API guidelines, library changes.*\n\n**Work plan**\n\n**{icon check-circle color=green} Milestone 1 - optional name**\n*Optional description of milestone.*\nTime estimate: `?`\n\n*All existent tasks edited out (removed) since the milestone is fully done.*\n\n**Milestone 2 - optional name**\n*Optional description of milestone.*\nTime estimate: `?`\n\n* - [x]*Task or feature.*\n* - [ ]*Task or feature.*\n* . . .\n\n**Branch**: `-` *Existing patches or branches.*\n\n---\n\n**Relevant links**:\n* `-`", "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", "Library Override broken for Snow character rig\nOperating system: Linux-5.15.0-73-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: 3.0 to 4.0\nWorked: never?\n\nI tried to use the Snow character, following the guidelines. But every time I use the Libary Override, the character's eyebrows and neck get stretched and distorted. When the bug does not happen at the time, when saving and reopening the file it appears\n\n- Link the CH-snow collection\n- Object -> Relations -> Make Library Override\n- Save file then reopen it\n", "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", "Revisit Pose Library for Object animation\nThe pose library was made with character animation in mind. However, because any Action can be marked as asset, it's also possible to use it with Object (or other datablock types) animation. The pose library should be investigated, to determine what doesn't work well, and whether to fix it or to just make the operation available for armature objects only.\n\nExample: re-rendering preview image for object-level pose Action shows warning about not being able to apply the pose.\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", "Regression in 4.0, crash loading blend file without a scene collection\nBroken: `f6082a5042db7cfe6c4617387a04f216a1ba3f99`\nWorking: 3.6 LTS.\n\nThis test from `lib/` crashes on load:\n\n`blender ../lib/tests/depsgraph/deg_point_cache_transform.blend`\n\nThis crashes in release builds, asserts in debug builds:\n```\n./blender.bin() ./source/blender/blenlib/intern/system.c:86: BLI_system_backtrace (0x2fa9abe)\n./blender.bin() ./source/blender/blenlib/intern/BLI_assert.c:38: _BLI_assert_print_backtrace (0x29ca0f0)\n./blender.bin() ./source/blender/blenkernel/intern/collection.cc:2101 (discriminator 2): scene_collections_array(Scene*, Collection***, int*) (0x35b760e)\n./blender.bin() ./source/blender/blenkernel/intern/collection.cc:2124: BKE_scene_collections_iterator_begin (0x35b79ba)\n./blender.bin() ./source/blender/blenkernel/intern/collection.cc:2182: scene_objects_iterator_begin(BLI_Iterator*, Scene*, GSet*) (0x35b7f87)\n./blender.bin() ./source/blender/blenkernel/intern/collection.cc:2193: BKE_scene_objects_iterator_begin (0x35b8056)\n./blender.bin() ./source/blender/blenkernel/intern/lib_override_proxy_conversion.cc:126: BKE_lib_override_library_main_proxy_convert(Main*, BlendFileReadReport*) (0x3f08530)\n./blender.bin() ./source/blender/blenloader/intern/versioning_common.cc:522: do_versions_after_setup(Main*, BlendFileReadReport*) (0x4e43643)\n./blender.bin() ./source/blender/blenloader/intern/readblenentry.cc:512: BLO_read_do_version_after_setup (0x4d1c740)\n./blender.bin() ./source/blender/blenkernel/intern/blendfile.cc:880: setup_app_data(bContext*, BlendFileData*, BlendFileReadParams const*, BlendFileReadWMSetupData*, BlendFileReadReport*) (0x3520a67)\n./blender.bin() ./source/blender/blenkernel/intern/blendfile.cc:956: setup_app_blend_file_data(bContext*, BlendFileData*, BlendFileReadParams const*, BlendFileReadWMSetupData*, BlendFileReadReport*) (0x3521081)\n./blender.bin() ./source/blender/blenkernel/intern/blendfile.cc:994: BKE_blendfile_read_setup_readfile (0x35213c3)\n./blender.bin() ./source/blender/windowmanager/intern/wm_files.cc:1067: WM_file_read(bContext*, char const*, ReportList*) (0x3033a5f)\n./blender.bin() ./source/creator/creator_args.cc:2185 (discriminator 1): handle_load_file(bContext*, char const*, bool) (0x29c726d)\n./blender.bin() ./source/creator/creator_args.cc:2256 (discriminator 1): main_args_handle_load_file (0x29c76c5)\n./blender.bin() ./source/blender/blenlib/intern/BLI_args.c:322: BLI_args_parse (0x2fbfa62)\n./blender.bin() ./source/creator/creator.cc:564: main (0x29bcaa4)\n/usr/lib/libc.so.6(+0x27cd0) ??:0: ?? (0x7fdfca627cd0)\n/usr/lib/libc.so.6(__libc_start_main+0x8a) ??:0: ?? (0x7fdfca627d8a)\n./blender.bin() ??:?: _start (0x29bc125)\nBLI_assert failed: source/blender/blenkernel/intern/collection.cc:2101, scene_collections_array(), at 'collection != nullptr'\n```\n\n", "Custom data split normals are taking active object from the area even if the active object is overriden\nBlender 3.5\n\n\nOperators `customdata_custom_splitnormals_add` and `customdata_custom_splitnormals_clear` if called from properties panel seem to take active object from currently active area even if you `context.temp_override(object=obj)` or `context.view_layer.objects.active = obj` to change active object which is counterintuitive and contradicts with how other operators active object override work.\n\nFound a workaround - if you `context.temp_override(area=None, object=obj)` it will take active object into account.\n\n\n1. Open attached .blend file\n2. Run the script\n3. (Make sure all objects are selected)\n4. Go to Custom Split Normals section (in Object Data Properties after Geometry Data).\n5. Try \"Add CSN\" - it wouldn't work\n6. Try \"Add CSN override area\" - it doesk work.\n\n", "Override Linked armature with bone constraint inconsistent behaviour\nOperating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.105.17\n\nBroken: version: 3.3.6\nBroken: version: 3.5.1\n\nOverriding a linked armature with bone constraints makes bone constraints editable but saving and re-opening the file displays the constraint as not fully editable but overridden. This is confusing and source of mistakes.\n\n- Link `Armature` object from the given file: [rig.blend](attachment)\n- In outliner, right click on it and `Library Override > Make > Selected`\n- Have a look to the Properties panel, under `Bone Constraint`, the constraint appears editable: \n- Save your file, and click on `Revert`\n- The constraint appears now as not fully editable but overridable: \n\nNB: you can also rename the constraint by adding \"Test\": \nSaving and reverting will duplicate the constraint, which is a strange behaviour and not what the UI suggests will happen.\n\n\n\n", "Internal buffer overwrites during file import\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nDebugged this a little and the best I can see is some file paths are overwriting parts of an Object instance\n\n- open file in blender 3.4.1 or later.\n- Switch to the Scene Properties panel\n- Expand Rigid Body World\n- Expand Cache\n- Click Delete Bake, and then Bake\n[resaved279b.blend](resaved279b.blend)\n[#103590.blend](T103590.blend)\n\n```lines=10\n>\tblender.exe!BKE_ptcache_id_from_softbody(PTCacheID * pid, Object * ob, SoftBody * sb) Line 894\tC\n\n \tblender.exe!foreach_object_ptcache(Scene * scene, Object * object, int duplis, bool(*)(PTCacheID *, void *) callback, void * callback_user_data) Line 1195\tC\n \t[Inline Frame] blender.exe!BKE_ptcache_ids_from_object(ListBase *) Line 1250\tC\n \tblender.exe!BKE_ptcache_id_find(Object * ob, Scene * scene, PointCache * cache) Line 1094\tC\n \tblender.exe!ptcache_baker_create(bContext * C, wmOperator * op, bool all) Line 193\tC\n \tblender.exe!ptcache_bake_invoke(bContext * C, wmOperator * op, const wmEvent * UNUSED_event) Line 216\tC\n \tblender.exe!wm_operator_invoke(bContext * C, wmOperatorType * ot, const wmEvent * event, PointerRNA * properties, ReportList * reports, const bool poll_only, bool use_last_properties) Line 1477\tC++\n \tblender.exe!wm_operator_call_internal(bContext * C, wmOperatorType * ot, PointerRNA * properties, ReportList * reports, const wmOperatorCallContext context, const bool poll_only, const wmEvent * event) Line 1676\tC++\n \t[Inline Frame] blender.exe!WM_operator_name_call_ptr(bContext *) Line 1721\tC++\n \tblender.exe!WM_operator_name_call_ptr_with_depends_on_cursor(bContext * C, wmOperatorType * ot, wmOperatorCallContext opcontext, PointerRNA * properties, const wmEvent * event, const char * drawstr) Line 1915\tC++\n \tblender.exe!ui_apply_but_funcs_after(bContext * C) Line 1017\tC++\n \tblender.exe!ui_handler_region_menu(bContext * C, const wmEvent * event, void * __formal) Line 11418\tC++\n \t[Inline Frame] blender.exe!wm_handler_ui_call(bContext *) Line 791\tC++\n \tblender.exe!wm_handlers_do_intern(bContext * C, wmWindow * win, wmEvent * event, ListBase * handlers) Line 3244\tC++\n \tblender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3364\tC++\n \tblender.exe!wm_event_do_handlers(bContext * C) Line 3958\tC++\n \tblender.exe!WM_main(bContext * C) Line 643\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 590\tC\n```\n\nThe SoftBody pointer passed in is garbage. Looking at the memory for the Object instance, I see:\n\n```lines=10\n0x0000018450826048 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826058 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826068 00 00 00 00 00 00 00 00 53 43 53 63 65 6e 65 00 ........SCScene.\n0x0000018450826078 74 61 67 65 00 61 69 6e 00 00 00 00 00 00 00 00 tage.ain........\n0x0000018450826088 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826098 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x00000184508260A8 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 ................\n0x00000184508260B8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x00000184508260C8 00 00 00 00 50 07 00 00 48 99 28 50 84 01 00 00 ....P...H™(P....\n0x00000184508260D8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x00000184508260E8 40 db a3 42 84 01 00 00 00 00 00 00 00 00 00 00 @Û£B............\n0x00000184508260F8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826108 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826118 00 00 00 00 00 00 00 00 08 dd 4e 09 84 01 00 00 .........ÝN.....\n0x0000018450826128 08 16 97 73 84 01 00 00 00 00 00 00 00 00 00 00 ..—s............\n0x0000018450826138 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826148 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826158 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 3f ..............€?\n0x0000018450826168 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826178 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 3f ..............€?\n0x0000018450826188 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................\n0x0000018450826198 01 00 00 00 01 00 00 00 00 00 00 00 00 00 01 00 ................\n0x00000184508261A8 08 8f 23 50 84 01 00 00 00 00 00 00 00 00 00 00 ..#P............\n0x00000184508261B8 08 3c 23 50 84 01 00 00 00 00 00 00 00 00 00 00 .<#P............\n0x00000184508261C8 29 5c 0f 3d 29 5c 0f 3d cd cc cc 3d cd cc 4c 3d )\\.=)\\.=ÍÌÌ=ÍÌL=\n0x00000184508261D8 33 33 33 3e cd cc 4c 3d 9a 99 19 3e cd cc 4c 3d 333>ÍÌL=š™.>ÍÌL=\n0x00000184508261E8 11 02 18 00 5a 0f 02 00 00 00 00 00 00 00 00 00 ....Z...........\n0x00000184508261F8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826208 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826218 4e 6f 6e 65 00 00 00 00 00 00 00 00 00 00 00 00 None............\n0x0000018450826228 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826238 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826248 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826258 46 69 6c 6d 69 63 00 00 00 00 00 00 00 00 00 00 Filmic..........\n0x0000018450826268 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826278 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826288 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826298 00 00 00 00 00 00 80 3f 00 00 00 00 00 00 00 00 ......€?........\n0x00000184508262A8 00 00 00 00 00 00 00 00 73 52 47 42 00 00 00 00 ........sRGB....\n0x00000184508262B8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x00000184508262C8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x00000184508262D8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x00000184508262E8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x00000184508262F8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826308 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826318 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826328 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826338 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826348 c0 00 00 00 44 ac 00 00 02 00 00 00 00 00 80 3f À...D¬........€?\n0x0000018450826358 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ............ÿÿÿÿ\n0x0000018450826368 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826378 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826388 fe 00 00 00 01 00 00 00 58 02 00 00 00 00 00 00 þ.......X.......\n0x0000018450826398 00 00 00 00 00 00 00 00 64 00 00 00 64 00 00 00 ........d...d...\n0x00000184508263A8 00 00 01 00 00 00 80 3f 00 00 80 3f 01 00 00 00 ......€?..€?....\n0x00000184508263B8 01 00 00 00 96 00 00 00 58 07 00 00 20 03 00 00 ....–...X... ...\n0x00000184508263C8 20 00 00 00 20 00 00 00 18 00 11 00 00 00 5a 00 ... .........Z.\n0x00000184508263D8 00 00 00 00 10 00 00 00 01 42 40 00 18 00 00 00 .........B@.....\n0x00000184508263E8 00 00 00 00 00 00 80 3f 00 00 00 00 00 00 80 3f ......€?......€?\n0x00000184508263F8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n0x0000018450826408 00 00 00 00 00 00 80 3f 00 00 80 3f 00 00 80 3f ......€?..€?..€?\n0x0000018450826418 00 00 c0 3f 01 00 00 00 00 00 00 00 00 00 01 00 ..À?............\n0x0000018450826428 10 00 00 01 00 00 00 00 00 00 00 00 6f 12 83 3a ............o.ƒ:\n0x0000018450826438 00 00 00 00 2f 2f 2e 2e 5c 2e 2e 5c 4c 57 52 65 ....//..\\..\\LWRe\n0x0000018450826448 6e 64 65 72 5c 53 69 73 79 70 68 75 73 5c 00 72 nder\\Sisyphus\\.r\n0x0000018450826458 73 2f 53 74 65 70 68 65 6e 2f 44 65 73 6b 74 6f s/Stephen/Deskto\n0x0000018450826468 70 2f 42 61 6c 6c 73 52 65 6e 64 65 72 73 41 57 p/BallsRendersAW\n0x0000018450826478 53 2f 43 61 6d 65 72 61 30 38 2f 66 72 61 6d 65 S/Camera08/frame\n0x0000018450826488 5f 23 23 23 23 23 23 00 2f 43 61 6d 65 72 61 5f _######./Camera_\n0x0000018450826498 30 30 31 43 65 6e 74 72 65 54 69 6c 65 5f 23 23 001CentreTile_##\n0x00000184508264A8 23 00 64 65 62 75 67 5f 23 23 23 00 62 6c 65 5f #.debug_###.ble_\n0x00000184508264B8 23 23 23 00 00 00 00 00 00 00 00 00 00 00 00 00 ###.............\n0x00000184508264C8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n```\n\nNote that the 'soft' value in the Object instance has a value of \n`+\t\t&object->soft\t0x00000184508264b8 {0x0000000000232323 {totpoint=??? totspring=??? bpoint=??? ...}}\tSoftBody * *`\n\nwhich points right in the middle of that path text (`rs/Stephen/Desktop/BallsRender/AWS/Camera08/frame######./Camera_001CentreTile_###.debug_###.ble_###`)\n\nSomething has written a path into the wrong memory space and corrupted this Object instance.\n\n\n", "Library Overrides of the Same Linked Armature Cannot be Posed Simultaneously\nOperating system: Windows\nGraphics card: RTX 3070\n\nBroken: 3.3.1\nWorked: NA\n\n**Short Description**\nWhen linking a rig and making it into a library override twice in one scene, the rigs function properly as separate rigs but both linked from the same file. However, if you try to go into pose mode for both at the same time and pose the rigs, you cannot pose them separately. This is a pretty specific issue but if you had two identical rigs and wanted to animate them interacting in some way, it would become extremely bothersome.\n\n**Steps to Reproduce**\n- Open `example.blend`\n- Select both armatures\n- Switch to pose mode\n- Select any bone of any armature (this will also select same bone of another armature)\n[bug.zip](bug.zip)\n", "History filled with \"Double click to rename\" when user changed index of a UIList\n\n\nBroken: version: 3.2.0\nWorked: Never\n\n- open Blender\n- add particle systems\n- change particle systems index\n- see how your history got vanished by useless flags\n\nGifs: \n\n\nI believe in order to fix this bug,\na `SKIP_UNDO` flag need to be implemented at a property level \nexample: \n`my_uilist_idx : bpy.props.IntProperty(options={'SKIP_UNDO'},)`\n\nThis issue is not only linked with UILists indexes, but also with any properties used strictly GUI\n\nsee the blender dev thread where we talk about the general issue of using properties for interface\n4\n\n\n\n", "Visual glitches With adaptive domain enabled when object is duplicated or transformed\nOperating system: windows 10\nGraphics card: 3080ti\n\n**Blender Version** 3.3 lts\n\nVisual glitches With adaptive domain enabled when object is duplicated or transformed\n\n- Open default scene\n- Add quick smoke on cube\n- enable `adaptive domain`\n- play animation\n- move domain around or duplicate it (snaps back to original place)\n- play animation again (will move to transformed position)", "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" ]

[ "Can't assign parent to overridden linked libraries in 3.2+\nWindows 10\nRTX 3090\n\nBroken: 3.2.0, 2022-06-08 & 3.2.1 release candidate 7-2-2022\nWorked: 3.2.1\n\nAttempting to parent an overridden linked library fails silently. \n\n\nCreate a library blender file with a collection (link1) containing multiple objects and save.\n\nCreate a new file (test), like the library file collection (link1). Select the linked collection instance. Apply \"Make Library Override\". Select any object in the overridden instance. Parent to another object in the new file(test). \n\nIn 3.1.2 this will succeed, in 3.2+ this will fail." ]

[ "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", "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", "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", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n", "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", "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```", "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", "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)", "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)", "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", "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", "Crash when switching to Sculpt mode\nOperating system: \nLinux bu-dvl-2 5.13.0-51-generic #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux\n\nGraphics card:\n0:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)\n\nBroken: 3.2.0\n\ncrashed when switching to Sculpt mode\n\n- Open alien.blend (attached) \n- Switch to Sculpt mode\n\n[alien.blend](alien.blend)\n\ncrash.txt: \n[alien.crash.txt](alien.crash.txt)", "Animation Player crashes on MacOS\n\n```\nOperating system: macOS-11.6.1-x86_64-i386-64bit 64 Bits or OSX 12.2.1\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n```\n\n```\nmacOS 12.2.1 Intel HD Graphics 6000 1536 MB and Radeon Pro 5300M, macOS 11.4\n```\n\nBroken: version: 3.0.0 Beta\nBroken: blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg, \n\nI open a fresh Blender, Standard Cube scene.\nGo to View-> Viewport Render Animation\nIt freezes (Beachball of death) around frame 20 or 30 . Have to kill Blender, fan goes crazy.\nSame with the default cube scene. But the the crash doesn't come every time, but the image it way too dark.\n\n\nProblem 1 \n\nFreeze during \" Viewport Animation Render\"\n- Default scene, \"View\" menu -> \"Viewport Animation Render\".\n- after a couple dozen frames, Blender freezes, full CPU usage, and frames don't progress.\n\nProblem 2\nAssuming the above problem doesn't appear, \n- Default scene, \"View\" menu -> \"Viewport Animation Render\".\n- Render-> View Animation\n- Playback crashes at the end of caching.\n\n\nProblem 3\n- The image is much too dark compared to the Viewport.\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", "Clearing followed by setting a listbox created by UILayout.prop_search while keeping the mouse on the listbox crashes Blender\nOS: Ubuntu 16.04 x86_64\nGfx: Intel HD Graphics 530 (Skylake GT2) (driver: GL 4.5 (Core Profile) Mesa 17.3.0-devel)\n\nBroken:\n- 2.79-42a562496b5-linux-glibc219-x86_64 (latest build)\n- 2.79-5bd8ac9abfa-linux-glibc219-x86_64\n- 2.76b\n\nClearing followed by setting a listbox created by UILayout.prop_search while keeping the mouse on the listbox either crashes Blender or leads to unexpected behaviour.\n\nConsistently reproducible.\n1. Open the default startup blender file\n2. Open a textblock and paste and run the code provided in Appendix A\n3. In the 3D viewport, press SPACE and type \"Crashable\", then select \"Crashable Operator\" => at the right an operator panel will be drawn\n4. In the operator panel, click on the field next to \"Obj:\" and select e.g., \"Camera\" from the list\n5. Click the X sign right to \"Camera\" while keeping the mouse pointer pointed at the field\n6. Click again on the field\n\n**Expected behaviour of step 6.**\nStep 6 should be able to behave as step 4, i.e., one should be able to again select something from a non-empty list\n\n**Observed behaviour after step 6**\nOne of following, probably depending on how Blender's memory was allocated:\n - Crash\n - The list is empty\n\n**Appendix A**\n\n```\nimport bpy\n\n\nclass CrashableOperator(bpy.types.Operator):\n bl_idname = \"object.crashable_operator\"\n bl_label = \"Crashable Operator\"\n bl_options = {'REGISTER', 'UNDO'}\n\n obj = bpy.props.StringProperty(name=\"Obj\")\n\n def draw(self, context):\n self.layout.prop_search(self, \"obj\", context.scene, \"objects\")\n\n def execute(self, context):\n return {'FINISHED'}\n\n\ndef register():\n bpy.utils.register_class(CrashableOperator)\n\n\ndef unregister():\n bpy.utils.unregister_class(CrashableOperator)\n\n\nif __name__ == \"__main__\":\n register()\n```\n\n**Terminal output upon crash**\n\n```\n$ blender\nRead new prefs: /home/elias/.config/blender/2.76/config/userpref.blend\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n**Contents of \"blender.crash.txt\"**\n\n\n```\n# Blender 2.76 (sub 0), Commit date: 1970-01-01 00:00, Hash unknown\nbpy.context.area.type = 'TEXT_EDITOR' # Property\nbpy.ops.text.run_script() # Operator\nbpy.ops.object.crashable_operator() # Operator\nbpy.ops.object.crashable_operator(obj=\"Camera\") # Operator\nbpy.ops.object.crashable_operator(obj=\"\") # Operator\nbpy.ops.object.crashable_operator(obj=\"\") # Operator\n\n# backtrace\nblender(BLI_system_backtrace+0x30) [0x1361b10]\nblender() [0x97a98e]\n/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f242a7894b0]\nblender(rna_ID_refine+0x4) [0x11bac84]\nblender(rna_pointer_inherit_refine+0x66) [0x11a9af6]\nblender() [0x1273ae2]\nblender(RNA_property_collection_begin+0x15c) [0x11b161c]\nblender() [0xb654ae]\nblender(ui_searchbox_update+0x6a) [0xb7514a]\nblender() [0xb57089]\nblender() [0xb59f6d]\nblender() [0xb5a027]\nblender() [0xb5d7ad]\nblender() [0xb5ebe6]\nblender() [0xb5f433]\nblender() [0x985e81]\nblender() [0x986251]\nblender(wm_event_do_handlers+0x5f6) [0x9868e6]\nblender(WM_main+0x18) [0x97cfd8]\nblender(main+0xef4) [0x95ce04]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f242a774830]\nblender(_start+0x29) [0x97a2b9]\n```" ]

[ "blender 2.9 macOS 10.15.3 crash cycles rendering with viewport / into image\nmacPro 2010 2 x Xeon with a patched Catalina to install it and use a custom PC AMD GPU.\n\nOperating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits \nGraphics card: AMD Radeon RX 5600 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5\n\nmacPro 2012 2 x Xeon with High Sierra 10.13.6\nNVIDA Wedrivers 2 x GTX 1070Ti\n\nBroken: version: 2.90 Final\nWorked: 2.83 works\n\nBlender crashes with cycles when rendering in viewport or hitting render into image\n\nStart blender\nswitch to cycles\nhit viewport render\ncrash\n\n** EXTRA INFO\nI noticed that while I have CUDA installed on High Sierra 2.9 does not show it while 2.8x does\nIt seems with Blender 2.9 something in general changed a lot making it break on many macOS versions now\nno matter if NVIDA or AMD cards.\n\n\n\n\nMacOS High Sierra Crash Reports\n[macOS High Sierra 10.13.6 Cycles GPU.rtf](macOS_High_Sierra_10.13.6_Cycles_GPU.rtf)\n\n[macOS High Sierra 10.13.6 Cycles CPU.rtf](macOS_High_Sierra_10.13.6_Cycles_CPU.rtf)\n\n\n[P1623](P1623.txt)\n" ]

[ "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "Set normals from faces should respect sharp edges\nMac OS Sierra\nRadeon Pro 580\n\nBroken: 2.78.5 66383ea206 \n\nSet normals from face effects faces across edges set to sharp. It would make more sense and be more useful if it would respect those edges IMHO.\n\nCreate a cube\nBevel edges across one axis with one segment and mark the caps to sharp in the edge menu\nTurn on auto smooth and set the angle to 180.\nSelect the smooth large faces and \"Set normals to face\" to move the smoothness to the bevel.\n\nThe caps should confinue to be flat since all there edges are marked as sharp.\n\n\n\nI really like this functionallity and I only want it to improve :-D\n\n\n ", "Boolean merges CustomData inconsistently (UVs, VCols), breaks UV Map Node\nOperating system: Linux-5.0.0-25-generic-x86_64-with-Ubuntu-19.04-disco 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.34\n\nBroken: version: 2.81 (sub 2)\nWorked: (optional)\n\nThe UV Map of an object with Boolean Modifier doesn't work when the UV is assigned to the texture with the UV Map node. \n\nOpen this file:\n[boolean_uv_map.blend](boolean_uv_map.blend)\nThe UV layout of the bigger cube is not used. Once you unplug the custom UV Map node in the shader, the UV Map works again. It also works when you disable the Boolean Modifier. ", "GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\n\nSubdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost\n\n1. Open default scene.\n2. Add subdivision surface modifier to an object.\n3. Make sure GPU Subdivision option is enabled.\n4. ~~Uncheck Use Limit Surface~~\n5. ~~Disable GPU Subdivision to see correct result.~~\nLast two steps are not necessary for recreation of the bug since this change- 118a219e9d\n[Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4](Subdiv_GPU_Use_Limit_Surface_2022-01-15_22-13-33.mp4)\n\n------\n\nNOTE: This bug seems to only occur on AMD cards on Windows.\n\n**Reproducible on:**\n\n| Operating System | GPU | Driver |\n| ----------------|-------------|---------|\n| Windows 10 | AMD Radeon HD 7800 Series | 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 |\n| Windows 10 | AMD Radeon (TM) RX 480 | 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 |\n| Windows 10 | AMD Radeon(TM) 535 | 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013 |\n\n**Not reproducible on:**\n\n| Operating System | GPU | Driver Version |\n| -----------------|-------------|---------|\n| Linux Mint 20 | AMD Radeon RX550 | 4.5.14800 Core Profile Context 21.40 |\n| Linux Mint 20 | AMD Radeon RX550 | 4.6 (Core Profile) Mesa 21.3.0-devel |\n| Windows 10 | Intel(R) UHD Graphics 620 | |\n| Windows 10 | NVIDIA GeForce GTX 1050 | 472.39 |\n| Linux Mint 20 | NVIDIA RTX 2070 | 510.47.03 |\n| Linux | NVIDIA GeForce GTX 970M | 495.44\n|Windows-10-10.0.19043-SP0 64 Bits|Radeon (TM) RX 480 Graphics| 21.30.23.01, 22.2.3, 21.10.2 |\n", "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.", "Boolean Modifier not working \nOperating system: Windows \nGraphics card: Nvidia Geforce GTX 770\n\nBroken: 2.93.4\nWorked: 2.90\n\nIf one tries to apply the boolean modifier \"Difference\" it does nothing. In previous version it functions.\n\n1. Download the Blender File from above \n2. There a 3 objects in the collections. The objects are in the positive xy-quardant. (Sorry that they are not centered)\n3. If one tries to apply the modifier on the Frame object there is no error message but the frame object doesnt get modified.\n\nGreetings Philip \n\nTest File:\n[#71360.blend](T71360.blend)", "Blender solidify modifier bevel convex bug ?\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\n\nOn the solidify modifier, under Edge Data > Bevel Convex, the bevel weight seems to be added randomly instead on the inner and outer edges of the rim. Is it a bug or there's something I'm missing ? \n\nI recorded it : WB83jpVG3qo\nThe video is on the version 3.2.2 but it does the same in the latest 3.3 build.\n\n- Open attached file or\n - Add a solidify modifier onto a mesh,\n - then add bevel weight by putting the value of Bevel Convex to 1.\n - Then, add a bevel modifier with Limit Method set to Weight.\n[Solidify+Bevel_Bug.blend](Solidify_Bevel_Bug.blend)\n\n", "Applying mirror modifier doesn't work with mesh-deform data\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Beta\n\napply the mirror modifier while is used with the multiresolution produces artifacts.\n\nopen the attached file and apply the mirror modifier.\n\nThank you\n\n\n\n[multires_err.blend](multires_err.blend)\n\n", "Vector displacement on top of adaptive subdivision breaks normal\nOperating system: Windows 10 / Ubuntu 22.04\nGraphics card: NVidia A6000 / K5100M\n\nBroken: 4.0\nWorked: never\n\n\nVector displacement on top of adaptive subdivision breaks normal.\n\n\n- Open attached file, switch to render preview in viewport.\n- It's in adaptive subdivision, where the vector displacement is connected.\n - Wrong normal in the \"hanging over\" side (in black).\n- If unmute the Geometry \"True Normal\" node, the normal seems to be correct but it lacks smooth interpolation (observable upon close inspection.\n- Add a displacement modifier (thus disabling the adaptive subdivision), and remove the displacement output link in the material.\n- Set the displacement modifier to the displacement texture (use RGB to XYZ mode).\n - Vector displacement renders normal correctly.\n\n| VD on adaptive subdiv | VD on adaptive subdiv (with true normal) | VD modifier on regular subdiv (correct) |\n|---|---|---|\n|  |  |  |\n\n", "Skin modifier root on every vert\nOperating system: win10\n\nBroken: (2.79b, 2.82)\n\nSingle vert is screwed into spiral via Screw modifier. Skin modifier treats every vert as root, ending up with bad polygon flow.\nLeft is object with modifiers, right is applied version to see issue clearly:\n\n\n1. Use single vert with offset from origin to create spiral via Screw modifier\n2. Put Curve modifier on it\n3. Add Skin modifier\n4. Apply every modifier before Skin\n5. Enter edit mode and see many roots\n6. Click \"Mark Root\" in Skin settings -> polygons calculated correctly\n\nIn attached file:\n6. Click \"Mark Root\" in Skin settings -> polygons calculated correctly\n[screw_skin_root.blend](screw_skin_root.blend)\n", "Image Texture shader node with Box projection outputs extreme values when mesh has unusual normals\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0\nWorked: can't test in other versions, since they can't open .blend files saved with Blender 3.0\n\nIf you open the attached file, you will see a mesh that's black everywhere except for some *very* bright pixels (the Bloom effect makes this glitch very pronounced).\nThe material is just an Image Texture node connected to BSDF's color, using Box projection and a completely black texture. Theoretically, it should only output interpolations between the colors of the source texture, but that's definitely not the case here.\nOn its own, the mesh doesn't exhibit the glitch, but some modifiers (such as Displace or Wave) make it manifest for certain combinations of parameters. I suspect that the mesh has some unusual normals or face orientations that the modifiers amplify into even weirder normals, which in turn cause trouble in Image Texture's Box projection.\n[shiny glitch blender3.blend](shiny_glitch_blender3.blend)\n\nOpen the attached file, wait for shaders to compile.", "Sculpt, Mask extract with certain mesh produces broken mesh (hidden geometry)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nMesh made as «mask extract» from sculpt, then I fill and triangulated top.\nIt looks like mesh contains non-selectable geometry, that prevents to make proper operation Origin to geometry.\nTry to do it. Origin will stay at the same place.\n\nAfter exporting obj and importing back bug gone. After remesh too.\nIt is the second time, I`ve encountered such issue.\nMay be related to #82209 (Blender hanging with «separate selection» in particular model/file (svg imported).)\n\n[mesh.blend](mesh.blend)\n\n[2021-03-24_11-40-49.mp4](2021-03-24_11-40-49.mp4)\n\n\n\n", "Weighted normals modifier produces different results on objects of different scales\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.0\n\n\nWeighted normals modifier is not consistant on small objects \n\nOpen Blender\nCreate a cube 1mmx1mmx1mm, scale applied, \nadd bevel and weighted normals modifiers\nYou can notice the différence by doing the same process on a 1mx1mx1m cube\n\nI can do a work around by modifying the unit scale parameter but I think it should work on 1mm objects, like a lot of watch pieces. \n\n[weightednormals_defect.blend](weightednormals_defect.blend)\n", "Intersect Boolean does not work properly when mesh has a degenerate face\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001\n\nBroken: version: 2.91 - 3.0.0\nWorked: n/a\n\nThe `Intersect Boolean` Exact mode does not work correctly when the mesh has at least one degenerate face.\nIn this case, it was tested on a mesh with a triangle whose vertices are collinear\n\n- Open attached file - (The edited mesh has a degenerate triangle)\n- Go to `Face` -> `Intersect (Boolean)` - (The operation will not work because of that triangle)\n\n- Undo the operation\n- Move the triangle vertex a little so that the face is no longer degenerate.\n- Reselect that loose geometry ({key L})\n- Redo Boolean operation (now it works)\n[intersect_w_degenerated_tri.blend](intersect_w_degenerated_tri.blend)\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" ]

[ "Custom Normals: some operations that alter topology (bisect, loopcut, subdivide, knife, triangulate modifier) destroy them while other operations (e.g. Connect Vertex Path, triangulate operator) preserve them\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.2\nWorked: unknown\n\nMesh bisect generates incorrect normals when applied to a face generated using bevel with \"harden normals\" applied\n\n1. Start with the default cube\n2. In the cube properties, enable auto smooth normals (Object Data -> Normals -> Auto Smooth)\n3. Enter edit mode\n4. Select one edge and bevel it\n5. In the operator panel, ensure that \"harden normals\" is enabled\n6. Select the whole model\n7. Bisect the cube so the bevelled edge is split in half\n\nThe bad normals should now be visible. You can enable normal indicators in Overlays -> Normals -> Split face normals (the second option of the three icons). You can also go to object mode to remove the wireframe and make the bad shading more obvious.\n\n[bevel and bisect.mp4](bevel_and_bisect.mp4)\n\nNote that traditionally, topology altering operations were not expected to preserve custom normals, see for example \n- #69290 (Loop cut and knife tools makes wrong shading on the mesh)\n- #53763 (Operations that alter topology (e.g. Mirror modifier AND mirror operator, loopcut, subdivide, knife) destroy custom normals)\n\nThen there has been 93c8955a72 which was a nice improvement for some operators (but was missing others afaict).\n(check usages of `BM_custom_loop_normals_to_vector_layer`)\n\nSo this now leaves us in the situation which feels puzzling/inconsistent:\nOn the reported geometry for example `Connect Vertex Path` works as expected, whereas `Knife` doesnt:\n[#97698.webm](T97698.webm)" ]

[ "Hard crash while resizing packed multichannel EXR\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nWorked: unknown\n\nTrying to resize this particular image crashes blender instantly. There's 2 unusual things about the image, not sure if they're relevant\n\n\n - it's a packed multichannel EXR\n - it has some very large values (it's an SDF, so some values are like 9999) \n\n\n\n # Load the file\n[image_resize_crash_004.blend](image_resize_crash_004.blend)\n - Resize the image\n - Crash!\n```\n\n```\nSee video:\n\n[Blender image resize crash 2022-12-08 15-41-15.mp4](Blender_image_resize_crash_2022-12-08_15-41-15.mp4)\n\n\n", "Array/Skin-Modifier-Combo causes crash\nOperating system: Linux Mint 19\nGraphics card: GT630\n\nBroken:\n2.80 (sub 39), branch: blender2.8, commit date: 2018-12-20 23:46, hash: 7a26e930a8c0\n\n\nPlease try to toggle the \"visibility\" of the skin modifier in my simple file. It crashes instantly and repeatingly:\n[Procedural leaves feathered1.blend](Procedural_leaves_feathered1.blend)\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", "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", "Blender crashing when rendering with eevee, not with cycles however.\nOperating system: Linux-5.15.82-1-lts-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.42, 5.15.82-1-lts) AMD 4.6 (Core Profile) Mesa 23.0.0-devel (git-e20564cfdb)\n\nBroken: version: 3.3.2\nWorked: None, I've tried 3.3-LTS, 3.4 (both the default version provided through steam and manually selecting 3.4 LTS) and the daily-alpha build (with the daily-alpha build I reset settings all to default as well) All of these versions are the ones provided through Steam.\n\nWhen rendering in eevee some of my meshes completely bug out as if only part of them are rendering (I've looked at my normals and they're all fine) and after that my entire PC crashes, forcing a power cycle. The viewport display, when in rendered mode, looks fine in eevee but after rendering and before my PC crashes the viewport also messes up with my meshes looking bizarre. This issue does not occur in cycles when using CPU or GPU compute and other blender files work fine in eevee / cycles both in the viewport and when rendering. I also tried applying all modifiers despite needing a displacement on my torches to animate them but no luck. My blend file also becomes corrupt sometimes after the crash.\n\nSimply just hitting the render button with my current .blend file when in eevee. Sometimes the render goes through with broken meshes (which then I can close the render window and switch to eevee in my viewport display but my meshes will be all messed up and then my PC will crash, sometimes it crashes before the render output. \n\n\n[Dungeon Course.blend](Dungeon_Course.blend)\n\n[Dungeon Course.blend1](Dungeon_Course.blend1)\n\n[3.4 config.7z](3.4_config.7z)", "Blender 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 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)", "Different extrude operations use the scale of the object differently\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.4.0, 2.93\nWorked: - never?\n\nThe four different extrude operations (avaliable on the Alt+E menu) can take or not the scale of the object in consideration when applying the command.\nThe screenshot below, in which all objects were originally simple planes scaled by 2 (in object mode), shows the difference between the operations when trying to extrude it by 1 meter.\n\nAs shown, the \"Extrude Faces Along Normals\" and \"Extrude Individual Faces\" use the scale of the object, resulting in a 2 meter extrusion, which is not the intended value of 1 meter.\nGiven that most actions in edit mode don't take the scale of the object into consideration, I believe these two operations cited above are a bug.\n\n- Using a plane, scale it by 2 (or any number different than 1) and copy it 4 times.\n- In each plane, extrude it by the same amount (i.e. 1 meter), using a different extrude operation given by the Alt+E menu.\n- You should notice the \"Extrude Faces Along Normals\" and \"Extrude Individual Faces\" operations will interfere on the extrusion amount given.\n\nThe result should be the same as the screenshot above and can be checked in the file below:\n[Extrusion Bug Report.blend](Extrusion_Bug_Report.blend)", "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)", "Box with beveled vert will damage, if use multires modifier in simple mode.\nOperating system: Fedora 32, 64bit\nGraphics card: GTX 650Ti\n\nBroken: version: 2.91.0 Alpha\nWorked: blender-2.82a-windows64\n\nAdd cube, bevel one vert (1 segments) add multires modifier, select simple mode, and subdivide 2 or 3 times. Mesh will damaged.\nIf beleled 2 or more verts subdivision works stability, but not always. Sometimes it will damaged, sometimes properly.", "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", "Blender development todo list -- Import/Export\nNOTE: this is a direct dump of Import_Export (without cherrypicking the [still] valid items)\n\n## Blender files and Library linking\n\n- [ ] Mixing \"direct\" and \"indirect\" data not well supported #26706\n- [ ] Making local data which is still used in libraries, causes problems #44321\n\n## All Formats\n\nCurrently negative scales will flip faces for formats which don't store object transformations (obj, ply, stl ... etc). #35892\n\n## FBX\nSee [[Extensions:2.6/Py/Scripts/Import-Export/Autodesk_FBX]].\n\n## Alembic\n- [ ] While Alembic exports particles as points and supports ParticleInstance modifiers it could also support particle duplication (dupliobjects etc.), see #54703\n", "Draw Face Sets smoothing and Relax Face Sets don't respect locked axes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Actually Windows 11, but I'll leave the auto-generated specs here as well).\nGraphics card: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 4.0.0 Alpha\nWorked: Assumably never.\n\nThe Tool ➔ Symmetry ➔ Lock X/Y/Z options don't work when:\n● you use Shift in the Draw Face Sets brush to smooth Face Set borders;\n● you use Mesh Filter ➔ Relax Face Sets.\n\nThis is a handicap when you want to smooth borders and don't want the Face Set border vertices to move in a locked axis direction.\n\n1. Start Blender.\n2. Subdivide the default cube by pressing Control + 4.\n3. Press Control + A ➔ Visual Geometry To Mesh.\n4. Go to the Sculpting workspace, and activate the Draw Face Sets tool.\n5. Draw a Face Set area.\n6. Lock an axis in Tool ➔ Symmetry ➔ Lock X/Y/Z.\n7. Smooth the Face Set's border with Shift. The locked axis isn't respected.\n8. Press Undo.\n8. Activate Mesh Filter ➔ Relax Face Sets, then click and drag across the mesh. The locked axis is again not respected.\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", "Access violation in `vk_icdNegotiateLoaderICDInterfaceVersion` when putting computer to sleep.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.3 Release Candidate\nWorked: (3.6.2)\n\naccess violation when putting computer to sleep. crash log is created immediately after clicking sleep.\n\n\n1. launch blender.\n2. open a file\n3. save it\n4. put the computer to sleep\n\nEdited steps because it just happened when blender was launched normally. Wasn't saved this time, and was a different blend file." ]

[ "geometry extrude crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83 (sub 9)\n\nWhen extruding an edge on my 3d model blender crashes. I have a shrinkwrap modifier and amirror modifier.\n\nYou have to extrude some edges and blender will crash\n\nps: this is my first bug report sorry if it is not perfect.\n\n[furr_geo_bug_report.blend](furr_geo_bug_report.blend)\n\n[2020-03-18 12-45-15.mkv](2020-03-18_12-45-15.mkv)\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)", "Renaming Vertex Group Breaks Modifier's Vertex Group Reference\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 1070 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: Never (2.79+)\n\nChanging name of the vertex group breaks modifier's vertex group reference.\nSame issue has been reported 6 years ago: [#41876](T41876). If it's still a \"known limitation\" or \"to do\", it might be a good idea to tag it with new/proper labels.\n\n1- Launch default Blender.\n2- Create a vertex group to the cube and assign a face.\n3- Create a modifier with vertex group option (Mask modifier for example) and select the vertex group that we just created.\n4- Rename the vertex group and notice that breaks the modifier referencing to that vertex group.\n\n[#74726.blend](T74726.blend)\n", "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)", "Converting Modifiers to Nodes\n### Benefits\nGeometry nodes offer increase flexibility and improved usability compared with modifiers:\n* The ability to easily deal with different data types in the same space.\n* Different operations can happen in parallel to be merged into the final result.\n* The attribute system is a massive improvement in terms of flexibility and options compared to vertex groups.\n* A nodes modifier can output different data types at the same time, including instances.\n* An improved interface, separating operations into their more basic parts, and providing visibility to more operations at the same time.\n* Many more opportunities for sharing creations with node groups.\n\n### Conclusions\n* The behavior of existing modifiers will not change.\n* For the foreseeable future, every modifier will still be available in the \"Add Modifier\" menu, even if it is internally implemented with nodes.\n* Many modifiers are useful to have as nodes and can be implemented directly, others with more than one node.\n* Eventually there could be a \"Convert to nodes\" operator for to switch modifiers to use a node group re-implementation.\n\n### General Questions\n* When should modifiers with multiple modes like \"Remesh\" or \"Decimate\" be split into separate nodes?\n* #86907 (Selection / Tagging in Geometry Nodes)\n\n### Functionality Available\n| Name | Note |\n| ---- | ---- |\n| **Vertex Weight Proximity** | In the \"Attribute Proximity\" node\n| **Volume to Mesh** | In the \"Volume to Mesh\" node\n| **Vertex Weight Mix** | The attribute system provides so much more flexibility!\n| **Edge Split** | In the \"Edge Split\" node\n| **Wave** | Effects like this are already possible to build with more complex node groups\n| **Triangulate** | In the \"Triangulate\" node\n| **Displace** | Covered by Attribute sample texture and attribute vector math (and attribute processor in the future)\n| **Warp** | This type of affect is possible to implement with attribute nodes (and attribute processor in the future) \n| **Mask** | #86640 Can also be replaced by \"Delete Geometry\". Though the armature mode would need design work. \n| **Boolean** | [D10599](D10599) \n| **Vertex Weight Edit** | This allows changing a vertex group with a curve mapping widget.\n| **Build** | #86640 Should be replaced by \"Delete Geometry\" node (along with an eventual `index` expression / attribute.\n| **Cast** | Can be generalized with \"Attribute Transfer Node\" / \"Geometry Proximity\" and primitive nodes. \n| **Shrinkwrap** | The proximity node and raycast means that this node can basically be recreated with nodes.\n| **Mesh to Volume** | #86838 Can be a straight copy from the modifier\n\n### Functionality Mostly Available\n| Name | Note |\n| ---- | ---- |\n| **Subdivision Surface** | [D10417](D10417) Needs two recently exposed enum options. \n| **Particle Instance** | The \"Create Along Paths\" option is not possible yet, that use case will likely be handled differently in geometry nodes. \n| **Data Transfer** | #86843 This can be solved (and simplified) with an \"Attribute Transfer\" node \n| **Weld** | #86913 Should be named \"Merge by Distance\". It should also support more component types besides mesh. \"Connected\" mode still needs to be supported.\n\n### Ready to Implement\nThere are no open design questions, but there may be code architecture questions to answer before work starts. \nFor example, modifiers generally retrieve weights from vertex groups, but geometry nodes do not create vertex groups.\n\nWhenever a problem like this comes up, sometimes it's possible to share code, \nbut it often makes more sense to rewrite or \"duplicate\" code, with the eventual aim of replacing the modifier anyway.\n\n| Name | Note |\n| ---- | ---- |\n| **Remesh** | #89052 Do modes get different nodes?\n| **Curve** | #88702 Requires testing regarding differences with modifier.\n| **Bevel** | #86841 Attribute domains can affect bevel control, custom profile should use proper curve geometry. \n| **Smooth** | #86903 Quite simple, can be generalized to smooth any attribute, not just position.\n| **Solidify** | #89050 Only non-manifold mode supported in the node. Some functionality could be split into separate nodes.\n| **Mesh Sequence Cache** | Can become an alembic import node that outputs multiple data types, mesh, points, and curves.\n\n### Needs Design\nMore design work is required to figure out the best solution for these modifiers,\nor stakeholder artists who can provide a better view of the use cases these modifiers address,\nor input from other developers.\n| Name | Note |\n| ---- | ---- |\n| **Screw** | #86901 Initial version seems simple, but some controls like \"Stretch UVs\" should be generalized. Maybe the whole modifier is too specific too\n| **Wireframe** | Uses BMesh, which, like Bevel, raises the question of how to pass information.\n| **Mirror** | #86904 Some aspects of this are covered by a transform node with a negative scale, but having a specific node is nice, especially to deal with other attributes. The node could support an arbitrary mirror plane. \n| **Laplacian Smooth** | Looks relatively simple. \n| **Volume Displace** | Should be relatively simple, but should be discussed briefly to make sure it fits into geometry nodes design. For example, maybe supporting attribute grids is a first step. \n| **Decimate** | #89051 This looks relatively simple to convert. This might be an opportunity to make some design changes though. \n| **UV Project** | Should be relatively simple to convert this, but may need to be changed for attribute access. \n| **Weighted Normal** | Many of these ideas could use generalization. A first step is exposing custom normals in some form. \n| **UV Warp** | Can probably be accomplished with attribute system. Investigation needed.\n| **Lattice** | Lattice data could become a geometry component type. \n| **Mesh Cache** | What are the differences between this and the Mesh Sequence Cache modifier? \n| **Simple Deform** | Probably fine, but maybe this could be generalized somehow? \n| **Normal Edit** | #93551 Exposing a write-able normal attribute may be enough for this (and an improvement).\n\n### Requires \"Binding\"\nNodes will need a way to store data for use later-- currently they cannot.\nThat should be designed first as a general idea before these nodes are implemented.\n| Name | Note |\n| ---- | ---- |\n| **Laplacian Deform** | Requires binding (persistent storage over evaluations). \n| **Mesh Deform** | Also requires binding. \n| **Hook** | Needs bind operations in edit mode (persistent storage). \n| **Surface Deform** | Requires binding. \n| **Smooth Corrective** | Requires binding. \n| **Skin** | Requires binding, marking root, etc. \n| **Armature** | Might be a very large project, many object level operations. \n\n### Simulation\nThese are modifiers that should tie into a more generalized simulation system.\nMost of the code can be reused in many cases like Mantaflow, but a direct copy from the modifier\nto a node would not make sense, and needs design for how node-based simulation should work.\n| Name | Note |\n| ---- | ---- |\n| **Soft Body** | |\n| **Explode** | Requires current particle system. \n| **Fluid** | Canonical example for the generalized solver idea. Particles and meshing can be separate steps for liquid\n| **Ocean** | This works differently from the other simulations, since it is self contained. \n| **Cloth** | \n| **Collision** | This is just a static \"collider\" tag, and a storage for settings. \n\n### Not to be Replaced\nThese are modifiers with a design that does not fit into the goals for geometry nodes.\nFor example, the multi-resolution modifier must be the first, and is more of a specific tool\nfor sculpt mode than a modifier \"function.\"\n| Name | Note |\n| ---- | ---- |\n| **Array** | Should be mostly replaced by instancing of geometry directly in the node tree. \n| **Multiresolution** | Needs design / architecture work. Object data type? Does not fit into geometry nodes design. \n| **Particle System** | To be replaced by particle nodes. \n| **Dynamic Paint** | This idea should be more generalized. ", "Crash on Changing Repeat value to -1 in Corrective Smooth modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 2.93.5\n\nNot Responding when I change the Repeat value to -1\n\n{[F11810617](image.png), size=full}\n\n", "Objects referenced in the `UVProject` modifier property are not snapped\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.90 (sub 0)\n\nWhen i select an object as projector transform in the UVProject modifier it doesn't snap to the object I added the modifier to.\n\n- add cube\n- add an empty\n- add uvproject modifier to the cube\n- set the empty as projector transform\n- enable snaping to surface\nor\n- open attached file\nWhen moving the empty it does not snap to the cube\n[bug.blend](bug.blend)", "Node groups' new method doesn't throw errors at inputs and outputs collections\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.1.0 Alpha\n\n\nNode groups' new method doesn't throw errors at inputs and outputs collections\n\n1. Create a geometry nodes modifier, get node group:\n\n```\nnodes = C.object.modifiers[0].node_group\n```\n\n2. Add new input or output by command \n\n```\nnodes.outputs.new(\"RGBA\",'new')\n```\n3. Note that there are no errors, but a new socket hasn't been created. \n\n\n\n", "Crash on sculpt mask brush when Multiresolution modifier is copied from another object\nOperating system: Windows 11\nGraphics card: GTX 1060\n\nBroken: 3.3.0 / 3.2.0 / 2.93.10\nWorked: (First time trying multires hasn't worked on any of the versions I've tested on)\n\n\nCrash on sculpt mask brush when Multiresolution modifier is copied from another object.\n\n\nReplicate problem 1:\n\n - Add a Cube (#1)\n - Add Multiresolution modifier to Cube (#1)\n - Subdivide 4 times\n - Add a Cube (#2)\n - Copy Cube (#1)'s modifier onto Cube (#2) through the use of Link/Transfer Data > Copy Modifier\n - Select Cube (#2) and enter sculpt mode\n - Select Mask Brush\n - Use Mask Brush (Should crash blender)", "Blender 2.71 (rc2) crashes when a UV sphere is added\nMac OS X 10.10 (beta) / AMD Radeon HD 6750M 512 MB\n\nBroken: 2.71 (release candidate 2)\nWorked: -\n\nBlender 2.71 (rc2) crashes when a UV Sphere is added to a existent project in Edit Mode.\n\nUsing the attached file, select the figure (stickman), go to Edit Mode and add a UV Sphere. After executing these steps, Blender stops responding and it's necessary to force quit and reopen. \n\nIt seems that's something to do with the modifiers (in the attached file, I'm using Mirror, Skin and Sub-surf). One or more of them are causing the crash when the UV Sphere is added. If I create a new project with no modifiers, I'm able to add UV Sphere. \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", "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)", "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)", "Undoing the removal of a vertex group in edit mode changes other vertex groups and doesnt bring the removed vertex group back\nOperating system: Linux-5.4.13-201.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 2)\nWorked: (optional)\n\n\nUndoing a vertex group changes the rest. The video should show the issue. There's 3 vertex groups, A = A, B = B and C = C. If you delete A, B = B and C = C. If you delete A and then undo it, B = A and C = B.\n\nTy9U5rj_6Sw\n\n[#63434.blend](T63434.blend)\n- Open File\n- you should be in editmode\n- remove the `zero_weight` vertex group\n- Undo {key Ctrl Z}\n- `zero_weight` vertex group is not back\n- `half_weight` vertex group now has zero weights\n- `full_weight` vertex group now has half weights\n\n\n", "Crash. Script changing values of a prop attached to object by an operator popup crashes the app\nOperating system: Windows 10 Pro\nGraphics card: NVidia GTX 1070 Ti\n\nBroken:\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen used from a plugin, operator that uses wm.invoke_props_popup(self, event) to draw(and change) properties from a property group attached to an object (constantly) crashes the app.\nWhen same code is used from the blender scripting area, the app does not crash, but after initial change of the param, the property is grayed out(seems like a bug as well).\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7DDBEA080\nModule : c:\\Blender28\\program\\blender.exe\nThe terminal process terminated with exit code: 11\n\n1) Create a testing_grounds.py file\n2) Fill it with code provided below\n3) Install as an addon\n4) Select an object\n5) Launch the operator(through space, typing \"TEZZT\")\n6) Change the value of the property by clicking and dragging the value;\n7) Repeat step (6) a few times if the app hasn't crashed yet\n\n```\nbl_info = {\n \"name\" : \"TestingGrounds\",\n \"author\" : \"ChieVFX\",\n \"description\" : \"\",\n \"blender\" : (2, 80, 0),\n \"location\" : \"\",\n \"warning\" : \"\",\n \"category\" : \"Generic\"\n}\n\nimport bpy\n\nclass SomeParams(bpy.types.PropertyGroup):\n float_value : bpy.props.FloatProperty()\n\nclass TestOp(bpy.types.Operator):\n bl_idname=\"testing_ground.tezzt\"\n bl_label=\"TEZZT\"\n bl_options={'REGISTER', 'UNDO'}\n\n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_popup(self, event)\n \n def execute(self, context):\n print(\"Im fine\")\n return {'FINISHED'}\n \n def draw(self, context):\n layout : bpy.types.UILayout = self.layout\n obj = context.object\n some_params = obj.some_params\n layout.prop(some_params, \"float_value\", text=\"Prop popup test\")\n \nclasses = [\n SomeParams,\n TestOp\n]\n\ndef register():\n for cls in classes:\n bpy.utils.register_class(cls)\n \n bpy.types.Object.some_params = bpy.props.PointerProperty(type=SomeParams)\n\n\ndef unregister():\n for cls in classes:\n bpy.utils.unregister_class(cls)\n \nif __name__ == \"__main__\":\n register()\n bpy.ops.testing_ground.tezzt('INVOKE_DEFAULT')\n```\n", "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```" ]

[ "Crash when changing active keying set.\nWindows 10 64 Bits.\nGraphics card GeForce GTX 1080 Ti.\n\nBroken: 2.83.11 hash: 6b24f7d87cba\n\nIf you try to change a keying set Blender crashes.\nThe way it causes the crash is you have to remove it first then select a new one, it doesn't crash if you select from the dropdown list.\nI get this error in the console.\n\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF737AC6A49\n```\n\n * in the timeline-> Keying->Active Keying set.\n * Select a keying set.\n * Remove the set.\n * Select a new one.\n * Crash.\n\n\n" ]

[ "Crash When Adding Hair Subdivision upon Viewer node\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 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\n\n\nAdding hair subdivision will cause crash immediately when you are using viewer node to visualize field values in the viewport.\nNote no crash will occur if the viewer node is inactive.\n\n[Hair Crash.crash.txt](Hair_Crash.crash.txt)\n\n1. select default cube\n2. shift+A to add empty hair\n3. in the node tree add viewer node.\n4. Crash if adding subdivision\n[Hair Crash.blend](Hair_Crash.blend)", "Support previewing geometry in the viewport\n", "Can't resize node in visible bounds\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\n\nWhen trying to resize a node, the node cannot be resized if the mouse is precisely on the edge of the node\n\nAdd any node in shader o geometry node editor and try to resize the node with the cursor in the border line of the node\n<video src=\"attachment\" title=\"2023-07-11 14-28-46.mp4\" controls></video>\n\n", "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", "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)", "Applying geometry nodes modifier create an empty material slot for no reason\nOperating system: W10\n\n3.4.1\n\nApplying geometry nodes modifier create an extra empty material slot for no reason.\n\n| Geometry node tree | Applyed mesh |\n| -- | -- |\n|  |  |\n\n1. Create an object\n2. Add a GN modifier\n3. Create some geometry inside GN and assign a material to it (or don't)\n4. Apply the modifier, you'll get an empty material slot on the object.\n\n", "Frame Selected does not respect GN output if it has different type from input\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\nI think this is an old known issue but I can't find this documented here.\n\nFrame Selected does not respect the output geometry by Geometry Nodes if its type is different from the input type.\n\nFor example, if the input is mesh and the output is curve, Frame Selected works on the original input mesh. (The same if the output has multiple types of geometry including the original type.) If the output is mesh it respects the output geometry even if it has noting to do with the input and has a wildly different bounding box.\n\nOn the other hand, a curve object converted to a mesh by Solidify modifier is still respected as the final output mesh.\n\n(Maybe related? #104738)\n\n[FrameSelectedWithGN.mp4](attachment)\n\n[FrameSelectedWithGN.blend](attachment)\n\n", "Curves with curve modifiers are not translated to mesh correctly and can't be used as a target for constraints and modifiers predictably\nOperating system: W10\nGraphics card: GTX 1080TI\n\nBroken: 2.80-d966c2f0c2ad-win64\nWorked: 2.79 master build\n\nIf you ctrl+a and press \"visual geometry to mesh\" on a curve that has a curve modifier, the resulting mesh you're getting is as if you didn't have that curve modifier at all. This was not the behaviour in 2.79b. Also, if you assign any constraints or assign this curve as a modifier for objects, you'll have it deformed as if the deforming curve doesn't have the curve modifier.\n\nCtrl+a on the bezier curve in this sample file\n[sample.blend](sample.blend)", "Geometry Nodes: HSV color circle has incorrect position\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.5.0\n\n*Input > Constant > Color* shows incorrect position compared to numerical edit or shader editor.\n\nOpen file, compare node representation of a color with position, when you numerically edit input color\n\n", "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", "Support Alembic export/import of curve objects\nI created this issue as requested [here ](T51195#430327).\n\nWhile the export of animated mesh objects works quite well, exporting and importing curve objects does not work as expected at the moment.\n\nWhen exporting curves there are two main options:\n- Export as curve\n- Export as mesh\n\nBoth of these are very useful. Depending on the specific setup it might not be useful to export a curve as curve but rather as mesh. Being able to export as mesh should always be an option.\n\nI created a little test file that includes a curve object with multiple animated properties and modifiers: [curve_export_test.blend](curve_export_test.blend)\nSome modifiers implicitly convert the curve into a mesh, so when the user wants to export as a curve, it should (if possible) evaluate all modifiers until the curve is converted. If it is not possible to apply only some modifiers, it should still be possible to only export the curve before any modifier is applied (next to the option to export the whole thing as a mesh).\n\nAlso, keep in mind:\n- Curves can consist of multiple splines.\n- The amount of splines per curve object can change over time.\n- The amount of points in a spline can change over time.\n- Curves and spline points have quite properties have quite a few attributes that need to be considered when exporting as curve (bevel radius, ...).\n\nIf I had to choose what to develop first, mesh or curve export of curve objects, I'd vote for mesh, as it allows for more flexibility. Additionally I imagine it to be easier to develop.", "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", "Annonymous Attributes and Simulation Nodes - propagation issue\nBroken: version: 4.0.0 Alpha\nWorked: Never.\n\nSome annonymous attributes are not working with the output of the Simulation Nodes if the attribute is not propagate via the simulation.\n\n\n1. [simulation_attribute_bugs.blend](attachment).\n2. Toggle the \"Show Bug\" modifier property to see when the bug happens.\n\n", "Grease pencil over geometry occlussion problems\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.5\nBroken: version: 3.0.0 Alpha\n\nGP lines get incorrect occlussion in the render while looking fine in the viewport\n\nThe problem displays differently in the following 2 scenarios:\n\nThis file has a grease pencil stroke close over (but not really touching at all) a piece of geometry\n[GP Aliasing.blend](GP_Aliasing.blend)\nViewport Rendering\n\nRender\n*The line looks jagged in the render*\n\n\nThis file has a grease pencil drawing far behind a piece of geometry\n[Occlussion.blend](Occlussion.blend)\nViewport\n\nRender\n*The drawing that should be occluded is completely visible*\n\n", "Mesh Attributes Python API Is Buggy\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3070\n\nBroken: 2.93 & 3.3\nWorked: \n\nAccessing geometry attributes via python causes internal errors and mismatched pointers.\n\n\n```\n- Blender 3.3.0 bug\n- 1) Open new file w/ default cube\n- 2) Paste this script into the scripting tab\n- 3) Make sure the cube is selected and run this script\n\nimport bpy\n\nme = bpy.context.active_object.data\n\nfva = me.attributes.new('float_vector_attribute', 'FLOAT_VECTOR', 'CORNER')\n\nprint(f'fva : {fva}.data_type = {fva.data_type}')\n\nfca = me.attributes.new('float_color_attribute', 'FLOAT_COLOR', 'CORNER')\n\nprint(f'fva (again): {fva}.data_type = {fva.data_type}') # output will be wrong\nprint(f'fca : {fca}.data_type = {fca.data_type}')\n\nme.calc_normals_split() # causes next line to crash\n\nfva.data[0].vector = (1, 2, 3) # only crashes the first time the script is run\n\n```" ]

[ "Hair curves are not showing the segments in every strand \nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.3.1\n\nHair curves are not showing properly the segments in every strand \n\n- Grab a model and add empty hair \n\n- Add with density or either add brush some hair strands with default settings except the length is decreased (which is working)\n\n- Add more hair but with more segments for example 24, 50, and 100 were tested with same length as before (2 cm in my case)\n\n- Comb the hair to see if the hair looks smooth on the subdivided strands (Hair fails to look smooth after increasing the default 8 segments, for example 24,50 or 100 of value i tried but doesn't change anything after adding more hair instead stays at 8 points when i comb it)\n\n- Try converting the hair curves to hair particles to see if any change happens\n\n- then go to particle edit mode and i notice that the segments are indeed there but look like this: seems that again the default segment count seems to remain in the strand but i can see the dots of the segments that i supposedly added before there but without any strand, but they are still deforming as i comb the hair from there...\n", "Curve Hair Geometry nodes - Transfer Attributes + Set Curve Radius working only in cycles\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 512.96\n\nBroken: version: 3.4.0 Alpha\n(same in 3.3.1)\n\nThe Transfer Attribute / Set Curve Radius combo does not work in workbench and eevee (on a new curves hair system)\n[TransferAttribute-HairSystem-BUG.mp4](TransferAttribute-HairSystem-BUG.mp4)\n[bugReport_HairRadius.blend](bugReport_HairRadius.blend) \n\nSwitch renderer, see short video or the blend file\n\nNot even sure this qualifies as a bug, or if this method of achieving hair thinning is ok. All the other nodes i tested (curve trim, noise+set position) work in both render modes though. Thanks!\n\n", "Hair curves have incorrect deformation for NURBS type\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\nAny other type of curve is used as a evaluated poly curve. But it seems that for the nurbs curve this happens twice, which causes deformations.\n| Poly spline | NURBS |\n| -- | -- |\n|  |  |\n\n1. Create hait curve.\n2. Set spline type to NURBS.\n3. Resample it.\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", "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", "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", "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", "The program crashes when texturing \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nWhen try texture object in texture paint mode, and there are another map in shader tab. Program crashes. \n\n1. In default (or other) scene go to Texture paint window, create new texture for paint. \n2. Apply this texture to diffuse color object in shader editor. (or in object properties)\n3. Go back to texture window. We make sure that everything is painted correctly\n4. Go to shading window and drag&drop any other texture to node window. (NOT APPLY TO DIFFUSE COLOR (or APPLY))\n5. Go back to texture paint window. For some reason, the dragged texture itself was assigned to the duffuse color.\n6. Change linced texture in image editor (in left window)\n7. Try paint on RIGHT window (3D viewport)\n8. Click on left texture editor (try paint in 2D ) program crash. \n\nVideo steps: 0Ophy4Lmx0A\n\nDebug logs:\n[blender.crash.txt](blender.crash.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Blender_crash.webm](Blender_crash.webm)\n\n", "Blender 2.90.1 crashes after rendering the first few frames of animation.\n**System Information** \nOperating system: windows 10 64 bit\nGraphics card: Nvidia GeForce GTX 1650\n\nBroken: (2.90.1 3e85bb34d0d7; master)\nWorked(didn't): (only tried on 2.8.3 and did not work at all)\n\nWhen I try to render the animation, after about 50 or so frames(varies randomly), blender crashes with no alerts or anything that tells me what the error is, it simply closes.\nI've rendered another project, and that did indeed render, so I'm left confused why this short animation would cause a crash.\n\nEdit: I disabled motion blur, and it rendered fine. However, I would really like to know why blender won't render if motion blur is enabled. The renderer is Eevee and while my laptop isn't a super computer, it should be able to handle it. Thank you all in advance!\n\n- Open attached file\n- render the animation\n[cube-loop-tut-V1.0.blend](cube-loop-tut-V1.0.blend)", "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", "Crash when rendering animation in Workbench (with workbench shadows)\nOperating system: Windows 10 20H2\nGraphics card: Nvidia GTX1080\n\nBroken: 2.93.0\nWorked: 2.92.0\n\nWhen rendering the attached file as animation Blender ends without notice after the second rendered frame.[mirandaAnimNeu3.blend](mirandaAnimNeu3.blend)\n\nOpen the file mirandaAnimNeu3.blend. Click Render | Render Animation.\n\nThe animation is set to start at Frame 466 and to last until frame 4900. After rendering of frame 467 Blender crashes without notice. No crash file is created. Blender just ends.\n\nBoth rendered images are saved. It is interesting to note that the earlier images of this animation are rendered within seconds but the render times of the last images require minutes although no noticeable content becomes visible. Yesterday I have rendered all 4900 frames at 50% size without anti-aliasing, which worked fine. Each image rendered in a second or two.\nSorry that the blend-file is so big...", "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", "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", "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", "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 after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "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 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)" ]

[ "Regression: My blend file crashes when rendering in Blender 3.4 upwards, because of an unchecked NULL in the code. (stack trace provided)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 31.0.101.2111\n\nBroken: version: 3.4.0\nWorked: Any version prior to this\n\nWhen rendering a large blend file in any build from 3.4 upwards I get a crash before the render starts. I have reproduced this in a debug build and can show where the issue is. I don't know the code so I am not sure why my blend file causes blender to get in this state and unfortunately it is commercially sensitive so can't share it. \n\nI load up my blend file and hit render. It fairly quickly hits an access violation.\n\nThe call-stack is as follows:\n\n```\n>\tblender.exe!rna_Object_indirect_only_get(Object * ob, bContext * C, PointerRNA * view_layer_ptr) Line 208\tC\n\n \tblender.exe!Object_indirect_only_get_func(Object * _self, bContext * C, PointerRNA * view_layer) Line 3365\tC\n \tblender.exe!BL::Object::indirect_only_get(BL::Context C, BL::ViewLayer & view_layer) Line 65142\tC++\n \tblender.exe!ccl::BlenderSync::sync_object(BL::Depsgraph & b_depsgraph, BL::ViewLayer & b_view_layer, BL::DepsgraphObjectInstance & b_instance, float motion_time, bool use_particle_hair, bool show_lights, ccl::BlenderObjectCulling & culling, bool * use_portal, ccl::TaskPool * geom_task_pool) Line 227\tC++\n \tblender.exe!ccl::BlenderSync::sync_objects(BL::Depsgraph & b_depsgraph, BL::SpaceView3D & b_v3d, float motion_time) Line 613\tC++\n \tblender.exe!ccl::BlenderSync::sync_data(BL::RenderSettings & b_render, BL::Depsgraph & b_depsgraph, BL::SpaceView3D & b_v3d, BL::Object & b_override, int width, int height, void * * python_thread_state) Line 285\tC++\n \tblender.exe!ccl::BlenderSession::render(BL::Depsgraph & b_depsgraph_) Line 401\tC++\n \tblender.exe!ccl::render_func(_object * __formal, _object * args) Line 243\tC++\n\n```\nThe function where we access a null pointer is:\n\n\n```\nstatic bool rna_Object_indirect_only_get(Object *ob, bContext *C, PointerRNA *view_layer_ptr)\n{\n Base *base = find_view_layer_base_with_synced_ensure(ob, C, view_layer_ptr, NULL, NULL);\n return ((base->flag & BASE_INDIRECT_ONLY) != 0);\n}\n```\n\nLooking through the code a little, it can be expected that the fine function may return NULL, this isn't checked before looking at the flag. I have no idea the conditions in my file which would cause it to return NULL though as I don't know the code, but there is a code-path through it where it would return NULL if you look up the stack a little. \n\nHope this helps in resolving the issue, it still works fine in version of Blender Prior to 3.4\n\n" ]

[ "Crash with mantaflow\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nBaking simulation causes crash\n\n[splash.blend](splash.blend)\n\nOpen file and bake liquid\n", "Crash when switching to Sculpt mode\nOperating system: \nLinux bu-dvl-2 5.13.0-51-generic #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux\n\nGraphics card:\n0:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)\n\nBroken: 3.2.0\n\ncrashed when switching to Sculpt mode\n\n- Open alien.blend (attached) \n- Switch to Sculpt mode\n\n[alien.blend](alien.blend)\n\ncrash.txt: \n[alien.crash.txt](alien.crash.txt)", "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", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "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", "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 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. -----------------------------------------------------------", "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\".", "Mantaflow: charge force field crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nWhen I try to add the charge force field and play the simulation the blender 3.0.0 Alpha crashes\n\nMake a simple water simulation and add the charge force field\n**Crash seems to happen only in release builds**\n\n[#92110.blend](T92110.blend)", "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", "Rendering animation using \"Generate\" type modifiers after animated displacement texture crashes Blender\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.83.10\n\nIf 2 high poly (~100k faces per obj) objects in modifiers properties have after Displacement modifier (with animated texture) \"Generate\" type modifiers (I've tried Boolean and Decimate), Blender cant run Animation render (but still can run Image render). \nCrash happens on 2.9 and higher. I've tested this on 2.83.10 LTS (from steam) and everything worked fine there.\nCrashes with Decimate a little bit hard to recreate. So I will go with steps for \"Boolean crash\"\n\n- create Cude, Empty and Icosphere\n- Add Subdivision mod. to Cube: set it to \"Simple\" and 7 levels\n- Add Displacement mod. to Cube and set texture (Clouds) coordinates to object - Empty\n- Add Boolean mod. (difference) and select object Icosphere\n- Select Cude with Icosphere and duplicate them\n- Save and press Render Animation\n[bug.blend](bug.blend)\n[bug.crash.txt](bug.crash.txt)\n\n```lines\n## 3883==ERROR: AddressSanitizer: heap-use-after-free on address 0x61500034ec08 at pc 0x000016fc795d bp 0x7fffc19dd6c0 sp 0x7fffc19dd6b0\nREAD of size 8 at 0x61500034ec08 thread #15\n - 0 0x16fc795c in blender::gpu::GLBatch::verts_(int) const /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112\n - 1 0x17013501 in blender::gpu::GLVertArray::update_bindings(unsigned int, GPUBatch const*, blender::gpu::ShaderInterface const*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_array.cc:124\n - 2 0x16fa900b in blender::gpu::GLVaoCache::vao_get(GPUBatch*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:273\n - 3 0x16fa84d8 in blender::gpu::GLVaoCache::base_instance_vao_get(GPUBatch*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:234\n - 4 0x16fa9d3e in blender::gpu::GLBatch::bind(int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:317\n - 5 0x16fa9f3f in blender::gpu::GLBatch::draw(int, int, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:328\n - 6 0x16eca2be in GPU_batch_draw_advanced /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_batch.cc:282\n - 7 0x16fc1207 in blender::gpu::GLDrawList::append(GPUBatch*, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_drawlist.cc:122\n - 8 0x16efa9f5 in GPU_draw_list_append /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_drawlist.cc:52\n - 9 0x5978acc in draw_indirect_call /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:598\n - 10 0x5978acc in draw_call_batching_flush /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:795\n - 11 0x597c5f0 in draw_call_batching_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:891\n - 12 0x597eae7 in draw_shgroup /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1056\n - 13 0x597f89f in drw_draw_pass_ex /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1113\n - 14 0x597fe50 in DRW_draw_pass /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1153\n - 15 0x5c51bc0 in EEVEE_velocity_resolve /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:466\n - 16 0x5c5202b in EEVEE_draw_effects /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:486\n - 17 0x5a21f42 in EEVEE_render_draw /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_render.c:671\n - 18 0x59b1dbc in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:559\n - 19 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 20 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 21 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 22 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 23 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 24 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 25 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 26 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 27 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 28 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 29 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 30 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n - 31 0x7ffff6f46292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)\n\n0x61500034ec08 is located 8 bytes inside of 512-byte region [0x61500034ec00,0x61500034ee00)\nfreed by thread #15 here:\n - 0 0x7ffff76927cf in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)\n - 1 0x18e0eab0 in MEM_lockfree_freeN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:129\n - 2 0x16ef56c6 in blender::gpu::GLVertBuf::operator delete(void*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x17018021 in blender::gpu::GLVertBuf::~GLVertBuf() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:35\n - 4 0x16f8bb19 in blender::gpu::VertBuf::reference_remove() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer_private.hh:94\n - 5 0x16f877f5 in GPU_vertbuf_discard /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:161\n - 6 0x5a0eab8 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:449\n - 7 0x59b1bef in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:542\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\npreviously allocated by thread #15 here:\n - 0 0x7ffff7692bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)\n - 1 0x18e0f510 in MEM_lockfree_mallocN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:276\n - 2 0x16ef5676 in blender::gpu::GLVertBuf::operator new(unsigned long) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x16ef70a2 in blender::gpu::GLBackend::vertbuf_alloc() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_backend.hh:121\n - 4 0x16f85d10 in blender::gpu::VertBuf::duplicate() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:77\n - 5 0x16f8750d in GPU_vertbuf_duplicate /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:149\n - 6 0x5a0ee06 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:467\n - 7 0x59b1953 in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:507\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\nThread #15 created by T0 here:\n - 0 0x7ffff75bf805 in pthread_create (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)\n - 1 0x18de42b9 in BLI_threadpool_insert /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:245\n - 2 0x4fee516 in WM_jobs_start /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:484\n - 3 0xd7b88bd in screen_render_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:1041\n - 4 0x4f8f3ba in wm_operator_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1293\n - 5 0x4f912f2 in wm_operator_call_internal /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1500\n - 6 0x4f91551 in WM_operator_name_call_ptr /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1548\n - 7 0x90f1c95 in ui_apply_but_funcs_after /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:932\n - 8 0x917b8d0 in ui_handler_region_menu /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:10809\n - 9 0x4f88a9b in wm_handler_ui_call /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:636\n - 10 0x4f9ec36 in wm_handlers_do_intern /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2757\n - 11 0x4f9fc78 in wm_handlers_do /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2865\n - 12 0x4fa537f in wm_event_do_handlers /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3288\n - 13 0x4f732cf in WM_main /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm.c:635\n - 14 0x34f58fa in main /home/dev/01-data/01-git/blender-git/blender/source/creator/creator.c:522\n - 15 0x7ffff6e4b0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112 in blender::gpu::GLBatch::verts_(int) const\nShadow bytes around the buggy address:\n 0x0c2a80061d30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa\n 0x0c2a80061d70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n# >0x0c2a80061d80: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d90: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061da0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061db0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c2a80061dd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n```\nAddressable: 00\nPartially addressable: 01 02 03 04 05 06 07 \nHeap left redzone: fa\nFreed heap region: fd\nStack left redzone: f1\nStack mid redzone: f2\nStack right redzone: f3\nStack after return: f5\nStack use after scope: f8\nGlobal redzone: f9\nGlobal init order: f6\nPoisoned by user: f7\nContainer overflow: fc\nArray cookie: ac\nIntra object redzone: bb\nASan internal: fe\nLeft alloca redzone: ca\nRight alloca redzone: cb\nShadow gap: cc\n```\n", "Regression: Crash on deleting NLA strip in tweak mode\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.0, 3.6.0\nWorked: 2.93\n\nWhen using the 'Previous Layer' function of the Action Editor to tweak NLA strips, trying to delete a (green) strip in tweak mode crashes Blender.\n\n\n- Open `109430.blend`\n- In the NLA area, press X to delete the green strip.\n- Blender crashes\n\nOriginal/from fresh file:\n\n- In the default startup file, open 2 areas; a Dope Sheet set to Action Editor, and a Nonlinear Animation.\n- Keyframe any property of the default cube.\n- In the Action Editor, click Push Down on the newly created action.\n- Also in the Action Editor, click the 'Previous Layer' button (the small down arrow). This activates tweaking for the NLA strip.\n- In the NLA area, click the green strip so it's highlighted.\n- Press X to delete it. Blender crashes.\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", "lineart bake w/ object keyframes + camera binds = crash\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.4.1\n\nA crash (instant program exit) happens when trying to bake line art with *both* keyframes on object visibility *and* cameras bound to a frame in the timeline.\n\n1. Open the attached blend file. Select the Line Art modifier, and click \"Bake Line Art\". The baking starts, gets to frame 7 (the one after the TriAllFree bound camera) and crashes.\n2. Open the attached blend file. Delete the camera binding marker on frame 6. Select the Line Art modifier, and click \"Bake Line Art\". The baking starts, gets to frame 7 (the one after where the TriAllFree bound camera was) and crashes.\n3. Open the attached blend file. Delete the camera binding marker on frame 6. Save the file to a new filename. **Exit blender**. Open the blend file with the new filename. Select the Line Art modifier, and click \"Bake Line Art\". The baking completes with no issue.\n4. Open the original attached blend file (not the new one without the camera bind). Delete the timeline channel on the Suzanne model that changes the render visibility. Select the Line Art modifier, and click \"Bake Line Art\". The baking completes with no issue.\n\nTested with daily builds of 3.4.1, 3.5.0 beta, and 3.6.0 alpha. Issue still present in all cases.\n\n", "Impossible to run Modal operator with simultaneously open props dialog (Blender crashes)\nOperating system: Linux-5.15.4-x86_64-AMD_Ryzen_3_PRO_4350G_with_Radeon_Graphics-with-glibc2.33 64 Bits\nGraphics card: AMD RENOIR (DRM 3.42.0, 5.15.4, LLVM 13.0.0) AMD 4.6 (Core Profile) Mesa 21.2.6\n\nBroken: version: 2.93.0\n2.93.6, 2.93.7, 3.0.0 and 3.1.0 all are broken.\nWorked: (don't know)\n\nBlender crashes while trying to display operator properties dialog (invoke_props_dialog) and add\nthe same operator as the modal handler (modal_handler_add(self))\nI think it's the same problem as in the (closed) task blender/blender-addons#48196\n\nTry to invoke corresponding operator and then to return {'FINISHED'} or {'CANCELLED'} from the modal() handler.\nThen blender crashes after pressing ESC or closing dialog.\n\nSample code:\n\n```\nimport bpy\n\nclass TEST(bpy.types.Operator):\n bl_idname = \"test.modal\"\n bl_label = \"test invoke props + modal\"\n\n test: bpy.props.StringProperty(\n name=\"test\",\n description=\"test\",\n default=''\n )\n \n def draw(self, context):\n col = self.layout.column(align=True)\n col.prop(self, \"test\")\n\n def invoke(self, context, event):\n context.window_manager.invoke_props_dialog(self)\n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n \n def execute(self, context):\n return {'FINISHED'}\n\n def modal(self, context, event):\n if event.type in {'ESC'}:\n return {'CANCELLED'}\n return {'PASS_THROUGH'}\n\ndef register():\n bpy.utils.register_class(TEST)\n\n\ndef unregister():\n bpy.utils.unregister_class(TEST)\n\nif __name__ == \"__main__\":\n register()\n```\n\nI think that impossibility of creating modal operators which can simultaneously have open properties\ndialog for on-the-fly corrections lead to endless tries to create custom bgl-rendered UIs which is just\nan unneeded overhead.\n\nPlease, review the mentioned bug, AFAIK it was already fixed but somehow reappeared upstream...\n" ]

[ "Crash when current frame is used as driver\nOperating system: Linux-4.15.0-142-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 3000 (SNB GT2) Intel Open Source Technology Center 3.3 (Core Profile) Mesa 20.0.8\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93 [FrameDriverBug.blend](FrameDriverBug.blend)\n\nCaused by eb06ccc324\n\nBlender crashes when `#frame` is used as driver in Geometry Nodes.\n\n- Add a Geometry Node modifier to an object\n- Switch to the Geometry Node editor and add a *Value* node\n- Type `#frame` into the input field\n- Play the animation or change the current frame\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)", "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)", "Crash when loading a geometry nodes asset into itself\nOperating system: Win 11\nGraphics card: 2070\n\nBroken: 3.4, 4.0\nWorked: none\n\nWhen working on an geometry nodes asset in an asset library - if you search for the name and adding it to the graph it causes a crash. \n\nDrag n drop from the asset browser behaves correctly here - so I think its just the node search code which is missing the check for self referencing.\n\n1. Download the blend file.\n2. Put into a folder.\n3. Add folder as asset library in prefs -> file paths -> asset libraries.\n4. Open the blend file from that folder.\n5. Go to the geometry node graph (should be open already).\n6. `Shift` + `A` to add new nodes.\n6. Search \"noop\" and press enter.\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", "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", "Crash when switching from solid to rendered view\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\n\nI have a scene about 1.7GB in size with 4K textures but renders in 2K using simplify, blender crashes when I open the file > hit F12 and render the scene then close the render windows and switch to render view > it starts compiling then blender closes, in the past it would show out of memory this report: \n\n105522#issuecomment-904934 \n\nThis issue happens only when persistent Data is active\n\nunfortunately I can't share the file at the moment. \n\n\n\n\n", "Lasso Select Broken if Select key is changed from Default Left to Right\nOperating system: Windows 10 (Home)\nGraphics card: Nvidia 1070 \n\n**Blender Version** \nBroken: 2.90.0 (Steam)\nWorked: Not sure, Has been like this since before 2.79b\n\nWhen the default select mode is changed from Left to Right Mouse button Lasso Select no longer works with Tweak + RMB Any. \n\nSplash Screen Change on initial set up or Select button or Edit - Preferences - KeyMap - Select With Mouse Button\n\nAffected: any View Mode that has the Lasso option. (Edit mode, Object Mode, Grease Pencil, etc)\n\n\nSee attached MP4.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nStart Blender and use Start up Cube. [BlendBug_2.mp4](BlendBug_2.mp4)\n\nTemporary fix if the Select key is changed from Left to Right Mouse Button is to walk through the KeyBindings and set anything that uses Lasso to Tweak Right and anything that was using Tweak Left to Tweak Right where Lasso is was changed. ", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "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```", "Adjusting spotlight blend using gizmo does not register undo\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\nThe gizmo control is introduced in 3c8c0f1094.\n\nAdjusting spotlight blend using gizmo does not register undo\n\n[SpotlightBlendGizmoBrokenUndo.mp4](SpotlightBlendGizmoBrokenUndo.mp4)\n", "Rolling the viewport causes unpredictable behavior when orbiting using turntable method.\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\nWorked: Never\n\nWhen using the turntable there is a fixed axis around which the viewport always orbits (the Z axis when the viewport hasn't been rolled).\nWhat happens is that Blender rolls this fixed axis with the viewport, so that when you orbit up/ down it does that using the new rolled fixed axis.\nHowever it does not roll the left/right orbiting directions (whatever you call them) with the viewport, meaning that, in my example, it creates an issue akin to gimbal lock where orbiting up/down will cause the same rotation of the viewport effectively making it lose one degree of freedom.\n\nI don't know the reason why Blender seems to behave in an unpredictable manner when orbiting with the mouse, but when orbiting with the numpad keys it confirms that we do indeed lose one degree of freedom as both Numpad {key 4} and {key 8} both cause an upward rotation of the viewport and both Numpad {key 2} and {key 6} cause a downward rotation of the viewport.\n\nSo to fix the issue all that needs to be done is to roll the left/right orbiting directions with the viewport and fixed axis.\n\n**Edit:**\nIt seems my original report focuses to much on the special case where the viewport has been rotated by exactly 90 degrees, causing it to lose one degree of freedom.\nHowever this is just a special case, the main issue is that whenever the viewport is rolled only the fixed axis is rolled, while the left/right orbiting axis(whatever you call them) is not.\nWhat you normally would expect when orbiting left/right that it orbits perpendicular to when you orbit up/down.\nBut since the left/right orbiting axis is not rolled, it meets the fixed axis at an angle other than 90 degrees, causing very unintuitive viewport behavior.\nOf course unless the viewport is rolled by exactly 90 degrees it is still technically possible to axis any viewing direction, however trying to do so will pose quite a challenge to the user.\n\n\n**For loss of one degree of freedom:**\n\n- Open new Blender file (Make sure to use turntable orbit method).\n- Roll the viewport by e.g. 90 degrees using {key shift 4} or {key shift 6}\n- Try orbiting the viewport with the mouse or the Numpad {key 2} {key 4} {key 6} {key 8} keys.\n\n**To see the unintuitive behavior:**\n\n- Open new Blender file (Make sure to use turntable orbit method).\n- Roll the viewport by any number of degrees using {key shift 4} or {key shift 6}\n- Try orbiting the viewport with the mouse or the Numpad {key 2} {key 4} {key 6} {key 8} keys.\n", "Suspected asset library crash by `json_sax_dom_parser`\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nI dont completely know why but blender crashes very often for me.\nIts doing something no idea what it is doing.\nSorry for being vague, but it seems to mostly happen when i have the viewport set to cycles render and i am trying to modify materials, in the shader editor.\n\n", "Support Undo for tweaking Gizmos\nSupport Undo for tweak gizmos, such as the Spin gizmo. Currently, the user may have performed many adjustments using adjustment gizmos, but if the user performs one undo, everything is lost.\n", "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)", "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" ]

[ "Crash when using gizmos in specific order\nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M395X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.4.10\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (Blender 2.8 2019-05-21)\n\n\nUsing gizmos in certain orders causes a Segmentation fault: 11 crash\n\nUsing the factory defaults,:\n\n - Activate the rotate tool\n - Drag inside the gizmo to spin the object aroung\n - Go to the viewpoint gizmo in the right of the viewport and drag it to orbit the view\n - Crash\n\n\n" ]

[ "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", "Transform constraints not working with rigid body simulation\nOperating system: Ubuntu 16.04\nGraphics card: MSI 1080Ti\n\nBroken: 2.80, 337eb8c1de4c, master, 2019-03-27,\nWorked: 2.80, 8beab3e33922, master, 2019-01-21\n\nThe new blender release (as of hash: 936014ea8c74), seems to have disabled constraints from animations. \nIf you set a Minimum Z for a rigid body object, it will ignore that minimum.\n\n - Open the default room.\n - Place the cube at (0, 0, 5)\n - Add “Active” rigid body to the cube\n - Add “Limit Location” object constraint and check minimum Z = 0\n - Press play\n\nIn previous versions, the cube would drop and stop at z = 0, but now it falls to -infinity.", "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", "Regression: Set curve radius. Operator/window do not react to Enter immediately\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.5, 3.1.0 Alpha\nWorked: 2.79b\n\nIn 2.79 i can call Set curve radius and press {key Enter} right after that. And it will set existing radius.\nIn 2.93—3.1 this window ignores {key Enter} (but reacts to {key Esc})\n\n[2021-12-02_18-59-11.mp4](2021-12-02_18-59-11.mp4)\nOpen the file\n[untitled.blend](untitled.blend)\nCall operator search\nFind «Set curve radius» and call it\nYou see small window with field and default 1.0 radius\nPress {key Enter}\nRadius of curve node remains the same.\nCompare to 2.79 version.\n\n", "Rigid body Bounciness parameter not functioning\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: 2.92 and version: 3.0.0 Alpha\nWorked: 2.83.13\n\nIn recent Blender versions the bounciness parameter of rigid bodies does nothing.\n\nOpen attached file, press space to start animation.\nOlder versions: ball bounces\nRecent versions: ball falls and immediately comes to an halt when it hits the surface of the cube.\n\n[Bounciness bug.blend](Bounciness_bug.blend)", "Object transforms affecting Sculpt Mode Brush behaviour\nThis is a design proposal to change some underlying behaviour of the brush system in Sculpt Mode.\n\n**The issue:**\nWhen scaling or rotating an object and then proceeding to sculpt on it in Sculpt Mode, the brush behaviour is generally affected by the transforms of the object.\nSo if the scaling is 1 on X & Y but 3 on Z, the brush radius will be 3 times as high. \nIf the object is scaled down in general, the brush strength will be lower in total.\nIf the object is also rotated, the brush radius will be as well and rake effects like for the Snake Hook brush will be badly affected since the object rotation is added to the rotation of the brush.\n\nIn recent versions the brush radius is at least reflecting the object transforms, which helps spotting these negative influences and reminding the user to apply the object transforms before sculpting.\nBut there is not benefit to having the Sculpt Mode being affected by the object transforms, so this is just a limitation of the current system.\nIt's also good to add that on the other hand Edit Mode is not negatively affected by the transforms of the object.\n\n[2020-03-02 11-42-04.mp4](2020-03-02_11-42-04.mp4)\n\n**The proposal:**\n\nTo make the sculpting workflow easier on the user it would be ideal if the brushes are not affected by the local transforms of the object but are instead based on the world scale & orientation.\nOnly symmetry options should be directly influenced bu the local transforms.", "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", "Support Scenes Overrides\nCurrently Scenes liboverrides are not really working, changes to its master collection will be lost, resync of scene itself is not possible when the override is the active scene, etc.\n\nSee e.g. #89963 (crash when library override is applied to an object)", "Statistic doesn't update if object deleted due to object data deletion with RMB\nBroken: version: 3.0.0\nBroken: version: 2.80 (sub 75)\nWorked: unsure (didn't find scene statistics in 2.79...)\n\nScene statistic (both in footer and 3D viewport) does not update correctly if object data is deleted with RMB\n\n1. Open default scene.\n2. Make sure you enable scene statistic either in 3D viewport or footer.\n3. In outliner unroll object to show it's object data, i.e. default cude.\n4. Click on object data, i.e. cube mesh, with RMB and delete it.\nObject will be deleted since it doesn't have mesh/camera/light object data. Notice that scene statistic is not updated (number of objects, vertices, selected status etc.). To update it you can select any object or click on outliner (doesn't matter on object or not).\n\nThat works correctly if object is not deleted, i.e. adding subdivision modifier (statistic will update) and then deleting it with RMB in outliner (statistic updated again).", "Regression: Extrude Tool XYZ Handles overlap on orthographic view and small world scale\nOperating system: Linux-5.15.0-43-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.85.02\n\nBroken: version: 3.4.0, 3.3 , 3.2\nWorked: 3.1\nCaused by 5045968f24\n\nThis bug might be related to #99670.\nWhen using the Extrude Tool, the handle type can be changed to show XYZ axes. When the object is way smaller than 1 Blender Unit, it becomes impossible to grab the Y and X handles in orthographic view.\n\n- Scale down the cube to 0.01 percent\n- Enter edit mode\n- Make the Extrude Tool active and switch the tool settings to XYZ\n- Try dragging the Z or Y handles\n\nFirst 3 steps are included in file\n[#100321.blend](T100321.blend)", "Blender Crashes when trying to create a Pivot Constraint for armature\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU\n\nBroken: 3.33, 3.34, 3.35 Beta\nWorked: 2.79\n\nWhen trying to set a bone in the Pivot Constraint for the Armature, it crashes.\n\n1. Create an armature.\n2. Create a Pivot constraint from \"Object Constraint Properties > Add Object Constraint > Relationship > Pivot\".\n3. Select the armature in the Target field.\n4. Then select the Bone in the Bone field. (Blender crashes)\n\n", "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", "Limit scale bone constraint: \"affect transform\" doesn't seem to work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: **2.83**LTS from steam, **2.92**release and **2.93.0**Alpha\nWorked: don't know\n\nContrary to the manual, the \"affect transform\" option does not limit the transform values (not visible).\nAlso when using limit scale as a bone constraint the minimum scale is not used, instead uses maximum as both being the min and max exactly the same number but in negative value.\n\n- Open attached file\n- Scale the bone beyond the limits\nNote that the scale values in the transform panel have not been clamped.\n[scale bone.blend](scale_bone.blend)\n", "Broken textures and shading\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nBroken textures when starting up blender and loading object textures and shading issues\n\n[Blender Texture Bug.mp4](Blender_Texture_Bug.mp4)\n\nPossible causes:\n * Not loading the parent asset blend file before the asset in another scene (opening it first seems to fix the issue in my testing) \n * 4k textures (i've heavily used 4k textures in the asset)\n * Viewport Texture size limit setting (Changed it to 2k)\n\n\n[untitled.blend](untitled.blend)\n", "Unpredictable 3D cursor positioning with vertex snapping and active target\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.63\n\nBroken: version: 3.2.0\n\nUnpredictable 3D cursor positioning when using active + vertex as snapping option\n\nUse snap with vertex and snap set to active.\nPosition 3D cursor by either having it as the active tool or with right + shift (and ctrl if snapping is not currently activated)\nSometimes it goes under the position under the mouse, sometimes it goes somewhere apart and depending on the direction you hover over it gets a different direction offset.\nThis is very annoying as I have to change snapping to closest everytime I want to accurately position the cursor, I use active most of the time and the cursor should allways go there, at least when only vertex is the snapping option that is used.\nAlso when I don't have any object selected it works as intended.\n\n[20220620-160415.mp4](20220620-160415.mp4)" ]

[ "The Include Non-Edited snapping option affects object mode\nOperating system: Linux-5.18.7-1-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 22.1.2\n\nBroken: version: 3.3.0 Alpha\nWorked:\n\n\nIf the **Include Non-Edited** snapping option is disabled in edit mode, it also affects object mode and snapping doesn't work. \n\n\n1) Open any project\n2) Select any object and go to Edit Mode, then switch all target selections to disable in snapping menu and return to Object Mode\n3) In Object Mode try any objects snapping to other edges, vertexes, etc. Nothing happens." ]

[ "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", "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)", "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.", "Solidify (Complex, Constraints) - very rare glitch\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.5.1\nWorked: 3.1.2\n\nbehavior changed in c2e8e68b6517b91eb14270707d7182c1727861c4\n\nSolidify modifier creates a weird glitch at a specific vertex.\n\nI have a model with about 40000 verticies that I wanted to solidify. Everything works fine, except the surroundings of a single vertex. The topology does not seem any particular there. The model is made out of triangles, but the glitch also appears if I convert it to quads. I copied the vertex and the surrounding faces to a sperarate blender file and recorded how the glitch appears depending on moving one of the verticies:\n\n(the glitch looks exactly the same when the vertex is part of the larger object)\n\nSolidify Modifier Settings:\nMode: Complex\nThickness Mode: Constraints\n(other settings does not affect the glitch)\n\n", "Console warning \"ToolSettings\"/ \"snap_node_element\"\nOperating system: Windows 10\nGraphics card: Geforce GTX 970\n\nBroken:\n2.80, 8c8979067490, blender2.7, 2019-01-31\n\nI was importing a file from an older blender version and I noticed this error in the console:\n\nIt appears when you hover over the node editor and when toggling edit mode.\n\nThe reason I think it's not an issue which appears because of the different blender version is that I recently released an addon for managing nodes with layers and a few people noticed similar errors when editing a mesh with KitOps or similar addons and then trying to change the nodes.\nI also don't think it's an issue with my addon as I didn't change the file (included) with the addon and I tried it with a clean blender version as well.\n\n[warning_message.blend](warning_message.blend)\n- Open the file\n- Open blender console to see error messages\n- Hover over node editor with the cursor\n- > Warning message should appear", "Multires modifier data (CD_MDISPS) can remain on a (once shared) mesh, bloats filesize, adding a new multires modifer will already have its levels then\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 2.93.0 Beta\n\nWhen adding multires and press subdivide, a single press adds 3 levels at once and gives the result in the picture\n\nThe left part is obtained after applying the mirror modifier\n\nAdd multiresolution and press subdivide [bug.blend](bug.blend)\nIf the modifier is removed and re-added, the bug disappears\n\nFound a way to reproduce this:\n\n- - [x] add Multires to the Default Cube object, subdivide twice\n- - [x] add a Monkey\n- - [x] change the mesh of the Monkey to the Cube mesh under `Object Data Properties`\n- - [x] (you can delete the default cube object now if you like)\n- - [x] add Multires modifier to the Monkey object\n - > it already has 2 multires levels (without subdividing even once), if you now subdivide, it will jump right to level 3\n - > saving the file at step - [x] will bloat the filesize (even though there is no multires modifier anymore :/)\n\nnote: this behavior does not occur if one removes the Multires modifier from the Default Cube object prior to deletion in step 4\n\nSo opposed to any other modifier (afaict), Multires seems to store info in mesh that is kept around.\nIt does get removed from the mesh when the modifier gets removed, but it does not get removed from the (possibly shared) mesh when the object gets deleted.\n\nUpon further inspection, these are stored in a `CD_MDISPS` custom data layer on the mesh.\nNow when `ob->data` is changed (step - [x]), or when a new modifer is added, the levels of the modifer will be made matching (see `BKE_mesh_assign_object` & `BKE_modifiers_test_object` & `multiresModifier_set_levels_from_disps`)\nThis can also be observed when for example a second multires modifier is added on top of an existing mutires modifier (levels will also be made matching).\n\nNow I assume that in the end this has its reasons (and it might very well turn out to not be a bug), but will leave up to module devs to decide.\n(I think it would be reasonable to remove CD_MDISPS initially when adding a **new** multires modifier?)", "GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\n\nSubdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost\n\n1. Open default scene.\n2. Add subdivision surface modifier to an object.\n3. Make sure GPU Subdivision option is enabled.\n4. ~~Uncheck Use Limit Surface~~\n5. ~~Disable GPU Subdivision to see correct result.~~\nLast two steps are not necessary for recreation of the bug since this change- 118a219e9d\n[Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4](Subdiv_GPU_Use_Limit_Surface_2022-01-15_22-13-33.mp4)\n\n------\n\nNOTE: This bug seems to only occur on AMD cards on Windows.\n\n**Reproducible on:**\n\n| Operating System | GPU | Driver |\n| ----------------|-------------|---------|\n| Windows 10 | AMD Radeon HD 7800 Series | 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 |\n| Windows 10 | AMD Radeon (TM) RX 480 | 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 |\n| Windows 10 | AMD Radeon(TM) 535 | 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013 |\n\n**Not reproducible on:**\n\n| Operating System | GPU | Driver Version |\n| -----------------|-------------|---------|\n| Linux Mint 20 | AMD Radeon RX550 | 4.5.14800 Core Profile Context 21.40 |\n| Linux Mint 20 | AMD Radeon RX550 | 4.6 (Core Profile) Mesa 21.3.0-devel |\n| Windows 10 | Intel(R) UHD Graphics 620 | |\n| Windows 10 | NVIDIA GeForce GTX 1050 | 472.39 |\n| Linux Mint 20 | NVIDIA RTX 2070 | 510.47.03 |\n| Linux | NVIDIA GeForce GTX 970M | 495.44\n|Windows-10-10.0.19043-SP0 64 Bits|Radeon (TM) RX 480 Graphics| 21.30.23.01, 22.2.3, 21.10.2 |\n", "Crash/Assert with two modifiers that require normals data [e.g. DataTransfer]\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.90.0\n\nCrash/Assert with two modifiers that require custom normals data [e.g. DataTransfer]\n\nIn a Debug build:\n\n[#84664.blend](T84664.blend)\n- Open File\n- add another modifier that requires normal data (e.g. Displace), or just duplicate the existing modifier\n\n[un2.blend](un2.blend)\n- Try to go to edit mode of \"Vert.011\"\n- Blender will crash.\n\n", "Array/Skin-Modifier-Combo causes crash\nOperating system: Linux Mint 19\nGraphics card: GT630\n\nBroken:\n2.80 (sub 39), branch: blender2.8, commit date: 2018-12-20 23:46, hash: 7a26e930a8c0\n\n\nPlease try to toggle the \"visibility\" of the skin modifier in my simple file. It crashes instantly and repeatingly:\n[Procedural leaves feathered1.blend](Procedural_leaves_feathered1.blend)\n", "Region overlap crashes when interacting with action zones\nEnable region overlap user preference.\n\nIn the default 3D viewport, press NKey, then drag on the corner widget. -> Blender crashes.\n\nAttached asan output: [region_overlap_azone.txt](region_overlap_azone.txt), [region_overlap_azone_2020_01_28_update.txt](region_overlap_azone_2020_01_28_update.txt) (found while investigating #46764).\n\nUpdated asan output\n\n\n----\n\nNote: Blender internals aren't well suited of handling regions being manipulated like this while the rest of Blender is being used. We could either prevent interaction during the fade, or disable it since its not really needed.", "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", "Geometry Node: Changing modifier input values with python no cause update\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0 Alpha\n\n\nChanging modifier input values with python no cause update.\nBy code:\n\n```\nbpy.data.objects[\"Cube\"].modifiers[\"GeometryNodes\"][\"Input_1\"][0] = 13.8\n```\n\nValue in modifier property was changed. User interface no updated before modifiers panel are not redrawn. Result of modifier didn't updated.\n\n\n\n- Open attached file\n- Run the code `bpy.data.objects[\"Cube\"].modifiers[\"GeometryNodes\"][\"Input_7\"] = 1.0` in the python console\nThe modifier UI may change, but the Viewport does not.\n[geom_node_py_bug.blend](geom_node_py_bug.blend)\n\n", "Geometry Nodes: Only re-evaluated log do update available attributes in drop-down menu\nBroken: version: 4.0.0 Alpha\n\nThis is a fairly insignificant UI bug. If the GeoNodes modifier is disabled, the list of available attributes to select in one of the inputs is not updated. For example, when a vertex group is renamed, that won't be reflected in the list, until the modifier is enabled again. Can result in a bit of confusion.\n\n1. Open attached file.\n2. Notice the GeoNode modifier is disabled.\n3. Rename the vertex group.\n4. Try assigning the renamed vertex group as the modifier's Factor input; You can't, because it won't appear in the list.\n5. Enabling the modifier updates the list again, and then all is well.\n\n", "Old files with subsurf modifier requite long time to load\nOperating system: Windows 10 x64 and Linux Regata OS\nGraphics card: Intel HD Graphics 620 Kaby Lake\nScreen resolution: 1366x768\nCPU: Intel Core i3 7100U quad-core 2.4GHz\nRAM: 4gb DDR4\n\nBroken: 2.81\nWorked: 2.79\n\n**Description**\nOld files with subsurf modifier requite long time to load.\nWhen subsurf modifier is disabled in Blender 2.79 ans file is saved, it loads quickly.\n\n3D Model working on Blender 2.79:\n\n\n**Steps to reproduce**\n[militar.blend](militar.blend)\n\nOpen the file", "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." ]

[ "Segfault/crash with two subdivision surface modifiers, latter one with viewport level 0\nOperating system: Linux-5.13.0-40-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (NAVI10, DRM 3.41.0, 5.13.0-40-generic, LLVM 12.0.0) AMD 4.6 (Core Profile) Mesa 21.2.6\n\n(OS is Ubuntu 20.04)\n\nBroken: version: 3.1.2\n\n(Blender was installed from Snap)\n\nBlender crashes with segmentation fault when adding two subdivision surface modifiers to an object and setting the viewport level of the last applied one (bottom one in the view) to 0.\n\n- Create new default scene\n- Select the default cube\n- Go in the Modifiers tab\n- Add two Subdivision Surface modifiers\n- Set the \"Levels Viewport\" of the *second* modifier (bottom one) to 0\n- Blender will crash immediately\n\n**Note:** I've seen other bugs like #97371, #97330, #97282 and #97160 - but unlike their cases, in my case it only crashes with *two* subsurf modifiers and the *latter* one having a viewport level of 0.\n\n**Note 2:** In Preferences -> Viewport, disabling GPU Subdivision **does** fix the issue. I assume that means the problem is about compatibility with my graphics card; I'm reporting the bug anyways, in case something can be done about it.\n\nCrash logs:\n[blender.crash.txt](blender.crash.txt)\n\n", "GPU subdivision: Last subsurf modifier is always used for GPU subdivision, even when disabled.\nOperating system: Arch Linux (last updated Mar 10, 2022)\nGraphics card: NVIDIA GeForce GTX 1070\nSystem Info: [system-info.txt](system-info.txt)\n\nBroken: 3.1.0, c77597cd0e15\nWorked: 3.0.1\n\nThis bug only takes hold when GPU Subdivision is enabled.\nWhen multiple SubSurf modifiers are added to an object, the last one in the stack determines the subdivision levels **even when it is disabled**.\nThis screenshots showcases the setup and issue: \n\nThis affects not only the viewport, **but also renders**: \n\nAdditionally, setting the subdivision count to 0 causes a crash (image attached is a GIF): \n\nBased on the default startup file:\n- Enable GPU Subdivision in Viewport -> Subdivision -> GPU Subdivision.\n- Add two SubSurf modifiers to the default cube.\n- Disable the second SubSurf modifier both in Viewport and Renders.\n- Change the subdivision levels on the second modifier.\n\nI've attached an example file showcasing the issue here: [gpu_subdiv_bug.blend](gpu_subdiv_bug.blend)\n\nI understand stacking SubSurf modifiers is a little unusual. I use this often in conjunction with drivers to switch between a high-fidelity and low-fidelity SubSurf that are stacked on top of each other." ]

[ "(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", "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)", "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.", "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", "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)", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n", "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", "Multi-Object Properties Editing\nIn Blender, we want to make it easier to set values for multiple objects, bones, strips, keys and other items at once. \n\nCurrently you can do this in limited circumstances, but you have to right-click on a value after you've changed it and pick Copy to Selected from the menu or hold Alt while editing values. This not only slow, but also very hidden, and the Alt-key conflicts with Emulate 3 Button Mouse. Lastly, it isn't clear at all to users which values work for multi-editing, and which values don't.\n\nHere's how we would like to solve it:\n\n\n## Selection vs Active\n\nThe concept of ***active*** in Blender means that we only show properties and only affect the active object or item. However, if we want to better support multi-item editing, we must start by making it so the Properties reflects the ***selection*** rather than the ***active*** item, of which there can only be one. Going forward, by default the Properties will be set to reflect the selection instead. This could be controlled in the Properties like so:\n\n{[F8363009](Screenshot_2020-02-22_at_17.34.54.png), size=full}\n*(The search box is added here to reflect how the Properties will be updated when that item is also added, but is a separate feature)*\n\nIf set to ***Active***, the Properties will continue to function as it does today, only showing properties for the active item.\n\n## When there are multiple selected items\n\nWhen the user has selected multiple items, a few things change:\n\nInstead of showing the name of the object at the top, Blender tells the user how many items are selected:\n\n\nIn the list of tabs, only properties sections are shown that are common among the selected items. For example, if you select a text and a mesh object, we don't show Modifier, Mesh or Curve Properties, since these properties only exist on a subset of the selected objects:\n\n\nThis rule also goes for individual panels. Here, both a Sun and Spot light are selected, and we only see properties that are shared between them. A note at the bottom clarifies that you are only seeing the shared subset:\n\n{[F8364914](Screenshot_2020-02-23_at_18.49.33.png), size=full}\n\n## When values differ\nWhen multiple items are selected, Blender will compare values to check if they are the same, or if they are different. If they differ, we change the way properties are displayed, like so:\n\n{[F8363037](Screenshot_2020-02-22_at_17.52.51.png), size=full}\n\n\n\n## Manipulating values across multiple items\n\n\n\nFor simply setting a value to be the same. you would simply type a new value, hit Return, and that value is then propagated to the selection.\n\nFor manipulating numbers and sliders relatively, you can just drag on them (like Alt-dragging today), or type the character '=', so the user can type '= -3' to subtract 3 from the value on all selected items.", "Render artifacts in Cycles with multi material with sss combined with glass or transparent \nOperating system:\nGraphics card: rtx 2080 TI\n[Bug_joined_object_sss_and_transparency_01.blend](Bug_joined_object_sss_and_transparency_01.blend)\n\nBlender version 3.0 stable\nRender artifacts in Cycles when rendering a multi material mesh with sss combined with glass or transparent shader. the transparent shader is shadowing the sss part of the model. this is not the case when the shaders are also separated in to two different objects. \n\nCreate two boxes assign a sss shader to one and transparent shader to the other. render in viewport. It works as supposed to. Now join the two objects in to one mesh. Render and see the \"shadow\" artifacts. or see attached file", "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", "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", "Multi-Object (Weight) Painting\nMulti-object weight painting would be extremely useful when rigging characters with clothing pieces that are separate objects. If a character has a shirt and a jacket, they both have to be weight painted identically, but separately.\n\nThe objects could be combined, but that would mean they must share a modifier stack, which is not always an option. We could also paint one then transfer the weights, but that only works between very similar objects. So we are stuck with meticulously weight painting both clothing pieces, while making sure the weights match between them.\n\nWith multi-object weight paint, the same brush strokes could affect both meshes, so they would be a lot easier to keep in sync.\n\nThe bare minimum functionality that I would consider useful:\n- Be able to select an armature then several meshes that are rigged to it, and enter weight paint mode\n- Selecting a bone activates the relevant vertex group on all meshes\n- Brush strokes affect all meshes\n- Can switch to multi-object edit mode\n- Geometry masking features work\n\nIn my personal workflow, supporting multiple armatures is not important.\nIf anyone thinks this is important, please comment with a use case example.\n\nAdditional functionality that would be nice to have:\n- Indicating active object in the 3D View. So far this hasn't been necessary, since it was always just one object.\n- Changing the active object without leaving weight paint mode. Symmetry settings are stored on the mesh, so this would be needed to be able to access those.\n- All of the above for Vertex and Texture Paint :)\n\nI tried to keep wall of text to a minimum, I hope this is not too bad @ideasman42 :)", "Applying negative scale inverts multires displacement\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.82a, 2.90 Alpha (542ff416e274)\nWorked: 2.79b\n\nWhen multires-sculpting an object, then mirroring it on any axis and then applying the scale, the multires displacement inverts - turning inside out. Flipping normals (either before or after applying scale) doesn't help.\nIn 2.79b, multires data is retained correctly after applying scale, although normals need to be flipped afterwards.\n\n1. Pick the default cube, add a multires modifier to it.\n2. Subdivide a bit for good measure, sculpt something.\n3. In object mode, mirror the object on any axis.\n4. Apply scale.\n5. Observe the sculpt turning inside out.", "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", "Cycle Shader Displacement does not distinguish Instances by Geometry Nodes\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.0.0 Beta\n\nThe color of shader is different on each instance, but the shader displacement has all the same result for each one.\n\n\n[DISPLACEM.blend](DISPLACEM.blend)" ]

[ "Baking in multi-Tiles textures (Udim) from MultiRes only use the height of the last tile as reference\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.5.1\n3.1 was OK on the first tile [but it didnt support baking UDIMs at all -- that came with 6787cc13d4ef], 3.2 already had this strongish contrast\n\nBaking in multi-Tiles textures (Udim) from MultiRes only use the height of the last tile as reference\n\n1. Make an object.\n2. Unwrap the UV on several Udim Tiles.\n3. Add a MultiRes modifier.\n4. Sculpt it, but make sure to not sculpt any faces unwrapped on your last tile: you'll have no value on your texture, only a 50% grey image.\n5. Now, sculpt the faces unwrapped on the last tile, but VERY slightly: you'll get a displace texture with too much contrast on the previous tiles (see the jpg image on attached files).\n6. Bake your displace on a new Udim image with all the necessary number of tiles.\n7. Here, you can see on the previous tiles that the displace has too much contrast and can't be used to get a correct result.\n\nPS: It has been tested on the .blend file in attached files with 2 tiles AND on another file (a dragon with only its wings membrane unwrapped in the last tile) with 4 tiles." ]

[ "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\n\n", "Blender crashes as soon as an image texture is plugged in the material BSDF node\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 1080 Ti\nSee attached log for more detail\n\nBroken: 3.5.1, but also 4.0.0 Alpha, did not try intermediate versions\nWorked: ??? The earliest available build, 2.93.18, also causes the same crash\n\nThe second any kind of image texture is plugged in a material, Blender crashes without any warning. Occurs when creating a new image texture, when plugging an existing file, or even when trying to plug a UV grid for unwraping purposes\n\n**Similar tickets**\n#76193\n#76377\n\n1. Start Blender.\n2. Create new default file.\n3. Select the default cube.\n4. Switch to Shading workspace.\n5. Add Image Texture node.\n6. Create new image or select an existing one.\n7. Plug Color output to the Base Color input of the Principled BSDF node.\n8. Watch Blender shut down.", "Blender File Browser Freezes if folder includes an not reachable Alias | MacOS\nOperating system: 13.5.2 (22G91)\nMachine: Apple Macbook Pro M2 Max\n\n3.6.2 - This has been happening before, I'm just reporting it now.\n\nWe have been using an Alias of our flamenco root folder called \"_flamenco\" on our Desktops for a while now. This error is NOT connected to flamenco issues, but I figured I add this for completeness.\n\nAlias is at:\n`/Users/USERACCOUNT/Desktop/\n`\nAlias points to:\n`/Volumes/Files/_flamenco\n`\n\nThis Files server is only reachable in local – physical – network, so if no cable is attached to the machine the connection can not be established.\n\nEvery time I select the Blender File Browser and open the Desktop folder, Blender will hang, freeze or crash. We had quite the trouble figuring out what is happening as we thought it would be connected to the actual contents of the other elements in the folder.\n\nI wonder if it is necessary to evaluate the source of the alias at that stage, or if this can be postponed until I click on the Alias.\n\n\nNo special blend file is needed to recreate this bug.\n\n1. Create Alias to an imaginary/not connected resource to the Desktop\n2. Open default Blender install\n3. File -> Open.. -> \n4. The Blender File Browser will open\n4. The Blender File Browser will still look responsive (hovering over buttons still works) but the next interaction will trigger a freeze\n4. User clicks on anything\n5. The file Browser and Blender will freeze, either for a very long time >3minutes or crash completly\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", "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)", "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", "Flickering macOS Blender 2.83\nOperating system: macOS 10.15.4\nGraphics card: XFX Radeon RX 580 8 GB\n\nBroken: 2.83\nWorked: 2.82\n\nFlickering occurs sometimes, as seen on this capture:\n[Screen Recording 2020-06-16 at 09.11.21.mov](Screen_Recording_2020-06-16_at_09.11.21.mov)\n\nI don't know exactly. I think it happens when I use Blender, then I switch to other applications and then return to Blender.\nIf I go to full screen mode, it's back to normal.\n\nThanks.", "Pivot point \"Active Element\" not functional for grease pencil strokes\nBroken: 2.83.10\n\nPivot point setting \"Active Element\" is not functional when used for grease pencil strokes.\nThis mode is nice for foreward kinematic rotations of say legs.\n\n- Open attached file\n- In edit mode, select pressing shift to have selected points and one active.\nEven with pivot point set to \"Active Element\", notice that the Transform Gizmo does not jump to the last selected point (the active one).\n[pivot bug.blend](pivot_bug.blend)", "Regression: Crash with boolean modifier\nOperating system: Fedora Linux 36 (Workstation Edition)\nGraphics card: Nvidia Geforce RTX 3080\n\nBroken: 3.2.1, 3.3 alpha\nWorked: 3.1\n\nCrash with boolean modifier\n\n- Open .blend file\n- In boolean modifier tab -> select `dot cutter` for boolean operation\n[yin_yang-v1.blend](yin_yang-v1.blend)\noriginal file: [F13292564](yin_yang.blend)", "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 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)", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "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", "Add sticky keys support for accessibility\nOperating system: Windows 10\nGraphics card: Geforce GTX-970m\n\nblender-2.80.0-git.1fa527bfa3a-windows64\n\n\nSticky keys not working properly.\nSfZ7Ua-ReuQ", "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" ]

[ "Grease Pencil: python generated strokes flicker and crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 11)\n\nWhen generating grease pencil strokes with python the results in the 2.83 master build refactor are unstable. They visually glitch and often lead to crashes.\n\n[Test GP Generate.blend](Test_GP_Generate.blend)\nThe attached blend file has 2 scripts. 1 that generates random strokes and 1 that copies the existing stable grease pencil object and all of it's strokes/settings. These scripts worked fine before the refactor.\n\nBoth result in a grease pencil object that when animated, sculpted, or edited have crazy spiky flickering. The thickness flickers all over the place and the triangles flash in and out.\n\nEventually if enough sculpting is done it will end up crashing.\n\nThe only way to fix it I have found is to join it with another GP object that was created and manually drawn. Then you have to delete the drawn stroke and re-add any modifiers that you setup.\n\n[2020-03-27 14-46-10.mp4](2020-03-27_14-46-10.mp4)" ]

[ "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\n\n", "Hide by face set and switch between objects not working in SCULPT Mode INDUSTRY COMPATIBLE\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.4.0\n\nHide by face set and switch between objects not working in SCULPT Mode INDUSTRY COMPATIBLE\n\nOpen blender, switch to industry compatible keymaps, and then if you try to hide faces by face sets, you don t have that option. The same goes for switching objects in sculpt mode. Further more, mask pie doesn't exist in sculpt mode in industry compatible version.\n\n", "Adjust last operation: can't reset properties to default value\nBroken: 2.8x\n\nIn the Adjust Last Operation panel, the context menu for any property has the Reset to Default Value options disabled, although they are enabled in the operator panel.\n\n\n1. Load the default scene\n2. Enter edit mode on the cube\n3. Bevel an edge\n4. Expand the operator panel in the bottom left\n5. Right click any property, note that Reset to Default Value option is enabled and works\n6. Go Edit -> Adjust Last Operation\n7. Right click the same property in that panel, note that Reset to Default Value option is disabled", "Python segfault or incorrect select_set()\nOperating system: MacOS 12.01\nGraphics card: Intel MacBook Pro\n\nBroken: 2.83.9, 3.0.0 and 3.1.0 Alpha\n\nSegmentation Fault happens or select_set is applied to the wrong object.\n\n\n- Based on the default startup file\n- Run the code provided below (two Font objects will be created)\n- Select all objects\n- Run this code again\n\n```\nlines=12, lang=py\nimport bpy\n\nfor n in bpy.data.objects:\n try:\n l = n['clearable']\n except:\n print(\"no clear\")\n else:\n print(\"deleting\", n.name)\n n.select_set(True)\n bpy.ops.object.delete() \n\n# add text\nfont_curve = bpy.data.curves.new(type=\"FONT\", name=\"Font Curve\")\nfont_curve.body = '2.44%'\nfont_obj = bpy.data.objects.new(name=\"Font Object\", object_data=font_curve)\nfont_obj.rotation_euler = [1.55,0,0]\nfont_obj.location = [10,0,2]\nfont_obj.scale = [.7,.7,.7]\nfont_obj['clearable'] = True\n# move the object to the collection, called link but taught as \"viewed as part of\" first via UI\nbpy.data.collections['Collection'].objects.link(font_obj)\nprint(font_obj.scale, font_obj.location)\n\nfont_curve = bpy.data.curves.new(type=\"FONT\", name=\"Font Curve\")\nfont_curve.body = '2.44%'\nfont_obj = bpy.data.objects.new(name=\"Font Object\", object_data=font_curve)\nfont_obj.rotation_euler = [1.55,0,0]\nfont_obj.location = [10,0,2]\nfont_obj.scale = [.7,.7,.7]\n# move the object to the collection, called link but taught as \"viewed as part of\" first via UI\nbpy.data.collections['Collection'].objects.link(font_obj)\nprint(font_obj.scale, font_obj.location)\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", "Shift+Spacebar shortcut for Tool Menu doesn't work correctly in sculpt mode\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0\n\nPressing and holding Shift+Spacebar and selecting a tool works okay. But just pressing that shortcut quickly shows the menu and hide it.\n\nOpen sculpt layout or go to sculpt mode. Press and hold shortcut Shift+Spacebar. While holding you can move the cursor on some tool and release the buttons. Tool under cursor is selected. All is okay, it works like a Pie menu.\nBut there are also hotkeys in that menu and if I just press Shift+Spacebar (without holding), menu opens and closes quickly. And selected is tool that was under cursor at that moment. If you press (without holding) Shift+Spacebar again, the menu doesn't close now, because the selected tool has already selected. But again, if I move my cursor, just press the shortcut, the menu shows and closes. It's impossible to use the hotkeys on the right of the tools in that menu.\n\n", "Baking dynamic paint to image sequence is cancelled without user interaction\nOperating system: Window 10, 64 Bit, 128GB RAM\nGraphics card: RTX 3090 with the newest studio driver.\n\nBroken: 2.93.5\nWorked: ./.\n\nI am following the cggeek tutorial on creating rain effects (watch?v=35bbyAJodEQ). Like said in 06:30 of the tutorial I wanted to bake the image sequence.\nIt happened some times that the Blender status line said that the bake had started, it sopped announcing that the bake had been cancelled without user interaction.\nI installed 2.93.5 and isolated the 3 concerned objects: The emitter plane, the plane I want to create the baking for and the drop. I started Blender via the debugging command file, clicked on bake and Blender crashed. \nThese are the produced files:\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\nPreviously I have tried to find out if the modifier sequence has an effect, but it does not have one. The position of the Dynamic Paint modifier can be arbitrary, and it is not essential if the plan includes particle systems or not.\n\nAfter more trials I could not reproduce the crash, only the indication of cancelling appeared - furthermore withour interacton:\n\n\n\nThanks\n\n- Open attached file (This is a minimum .blend file, which crashed on the first try after installing 2.93.5 and led to the production of the debug files above)\n- With the object \"aBodenFriedhof.002\" selected, go to {nav Physics Properties > Dynamic Paint > Output} and press `Bake Image Sequence`\nAfter a short time, the process will be canceled without an explanation.\n\n[dpSplit.blend](dpSplit.blend)\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", "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", "Geometry Nodes: simulation crashes when \"Cache\" option is disabled\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14802 Core Profile Context 21.40.64.06 30.0.14064.6002\n\nBroken: version: 4.0.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `Unknown`\n\nDisabled \"Cache\" option causes a crash when jumping back to start frame.\n\nAdd a simulation zone, output the geometry result.\n\nGo to the Physics tab and disable the __Cache__ option in the Simulation Nodes\n\nSimulation a few frames, then jump back to the start frame.\n\n", "Sculpt undo bug, mixing sculpt brush and multi-res modifier changes.\nWith current master (also 2.83).\n\nThe following steps show and error when redoing sculpt mode undo, when mixing multi-res subdivisions.\n\n- Startup file\n- Add multi-res modifier.\n- Enter sculpt mode.\n- *Repeat this 3-5 times.*\n - Multi-res subdivide.\n - Brush Stroke.\n\n- Now undo until the very beginning.\n- Now redo until the very end.\n\nWhen redoing, there are glitches where the multi-res has tearing/artifacts.\n\nSee video: [sculpt_undo_bug.mp4](sculpt_undo_bug.mp4)", "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", "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).", "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)", "Tool Menu does not wait in Sculpt mode unless the cursor is hovering on the previously selected tool.\nOperating system: Windows 10\nGraphics card:\n\nBroken: 2.90.3 alpha Date: 2020-05-25 19:50 Hash : 5254ffa17bf0 Branch: master\n\nTools menu does not wait even for a second Shift + Spacebar in Sculpt mode. Tricky thing is : unless the mouse cursor is on the previously selected tool in the menu.\n\n- Go to Sculpt Mode\n- Press Shift + Spacebar.\n\nOnly when you PRESS TWICE the \"Shift Spacebar\" key combination TOOL MENU STAYS. i.e., Only if cursor hovering on the previously selected tool menu stays otherwise it disappears. " ]

[ "Pressing R click when using Face Set Expand crashes Blender\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 6)\nWorked: (optional)\n\nPressing R click crashes Blender while using Face Set Expand.\n\nSee video. Just press R click when using Face Set Expand.\n\n[Desktop 2020.03.06 - 18.33.35.06.mp4](Desktop_2020.03.06_-_18.33.35.06.mp4)\n\n", "crash sculpt face sets\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.4642\n\nBroken: version: 2.83 (sub 6)\nWorked: (optional)\n\n\nIn sculpt mode face sets, while using Shift+W to expand the face set right click crashes blender. Left click confirms the face set expansion thats good, right click crashes. \n\n\n\nSculpt mode\nFace sets\nPress Shift+W expand face set, while expanding Press right click - Crashes\n\n\n\n", "Crash on expand face sets and cancel\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 2.83 master\n\n1. Go to sculpt mode\n2. Press Shift and W to expand a face set, \n3. expand, dont apply, press Escape to cancel \n\n\nCrash is in this function in sculpt.c, ss->filter_cache->prev_mask is nullptr.\n\n\n```\nstatic void sculpt_mask_expand_cancel(bContext *C, wmOperator *op)\n{\n Object *ob = CTX_data_active_object(C);\n SculptSession *ss = ob->sculpt;\n\n MEM_freeN(op->customdata);\n\n for (int n = 0; n < ss->filter_cache->totnode; n++) {\n PBVHNode *node = ss->filter_cache->nodes[n];\n PBVHVertexIter vd;\n BKE_pbvh_vertex_iter_begin(ss->pbvh, node, vd, PBVH_ITER_UNIQUE)\n {\n *vd.mask = ss->filter_cache->prev_mask[vd.index];\n }\n```", "crash when using expand Face Sets \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 6)\nWorked: (optional)\n\nwhen i use expand face sets shift+w in sculpt mode then cancel it using esc/rmb blender crash\n\ndefault cube> remesh it using ctrl+r> setting face sets to 1.0 in overlays >ctrl+w to face set expand >esc/rmb to cancel \n\n\n" ]

[ "Running a script that registers an operator from the same operator crashes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIf you execute an `bpy.ops.text.run_script()` through the operator through the panel in a Text editor, then blender crashes.\n\nP.s. maybe it's my fault and I did something wrong, but is blender supposed to crash?\n\nCopy the script or download the file:\n```Py\nimport bpy\n\nclass Op(bpy.types.Operator):\n bl_idname = 'op.op'\n bl_label = \"Op\"\n def modal(self, context, event):\n bpy.ops.text.run_script() # <------- here -------\n return {'FINISHED'}\n def invoke(self, context, event):\n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n self.layout.operator(Op.bl_idname, text='Click me')\n\n\nclasses = (Op, Panel)\n\ndef register():\n for c in classes:\n bpy.utils.register_class(c)\ndef unregister():\n for c in reversed(classes):\n bpy.utils.unregister_class(c)\n\nif __name__==\"__main__\": register()\n```\n\n", "simulation in new scene causes crash in original scene's simulation\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: (optional)\n\n**steps**\n- make cube an active rigid body. \n- play simulation\n- then click on new scene button and on full copy.\n- in the new scene, rewind playhead to frame 0\n- run the simulation.\nBlender should crash.\n\nThere are more ways to cause crash when full scene copy is done (see comments), but I guess these will stem from single issue.", "Blender 2.8. In edit mode when you have hard scene (slow down processing) all your actions will applyes not at right moment (not at click but at moment when blender finn. caclucations)\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\n\nBroken: version: 2.80 (sub 53)\nWorked: (optional)\n\n\nI have scene where I put a lot boolean(and not only) modificators on one objects and when I enter into edit mode all processing erally slow (each action: movement, extrusion, etc..) And problem here in next: when you doing any action (and it took time to process it) and then press mouse button to apply action affect, but! it will not memorize position of the mouse when you pressed, and still continue doing (move to the cursor) And this really anoing because you need repeat all twice or more time. Or just seating and waiting with no mouse movement at all, when it will apply action effect. \nSo core problem is that: in edit mode any affect will applyes not at moment when you decide but by moment when CPU will finished calculetion of movement/action and will change your action to position where is going be mouse positioned at the moment of the end calculation... something like that. \n\nCreate some worcload/heavy scene. For example by a lot subdivisions and booleans at object. When each your action will be like \"under water gravity\" slowed down. And then try to change(extrude/move vertext / anything) boolean part that will be used as cut area in the edit mode. \n\n[2019-04-01 17-39-35.mov](2019-04-01_17-39-35.mov)", "Transform cursor (patch included)\nRecently LMB-Drag was made to move the cursor *(edit, this has since been reverted)*.\n\nHowever this just moves the cursor under the mouse,\n\nit _could_ be useful to use transform here, it allows.\n\n- Drag, XKey to lock to an axis\n- ... Shift+Y to constrain to a plane.\n- ... Hold Ctrl to snap (snap to verts for example is handy)\n- ... Shift for more precise placement...\n... most other transform keys.\n\n\nOne reservation I have about this, is that you probably would often want to be able to snap to vertices and edges, and not have to depend on the current snap options in the 3d view header.\n\nSo we could override the snap options that transform uses.... but this seems a bit crappy too, since you may want to snap to faces in some cases, or even snap to grid.\n\nAs an alternative, we could just not bother attempting to integrate this with transform, and add snapping to the current modal operator (similar to how we have with the Ruler operator, which shares low level code with transform snapping)\nBut in that case we miss the axis constraints which seem like they would be nice to support.\n\n\nHere is a test patch to show how it works: [P87](P87.txt)\nNote, it crashes if you try to scale and its hard coded to LMB for cursor place, so its mostly a proof of concept.", "Menus open on upward mouse movement\nOperating system: Linux (Debian bullseye)\nGraphics card: Nvidia GTX 1070\n\nBroken: current master 2.90.0 (fc672ce8e24e)\nWorked: Never\n\nWhen there are a lot of modifiers in the stack which make the evaluation slow there is a weird effect with the dropdown menu. It somehow glides when dragging to the next modifier.\n\n\n\nTo the default cube, add array modifiers until your memory usage is at roughly 300MiB. Then drag over the drop down arrows like shown in the gif.", "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", "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.", "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", "Duplicate Shortcut, Smooth Brush and Stabilize Stroke (Sculpt Mode)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Alpha\n\nSmooth Brush and Stabilize Stroke use the same \"Shift + S\" shortcut. And only the smooth brush shortcut works.\n\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", "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", "Trackpad scrolling is too sensitive in Text Editor\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.6.1\nWorked: never\n\n\nIf you scroll very slowly, nothing happens, deltas that give an offset of less than one line/character are simply discarded and not accumulated. The minimum possible scrolling is too fast, this jumps several lines at once and it's impossible to stop at the desired one.\n\nOne of the possible solutions can be seen here: D9552. This makes the scroll speed match the speed in other Blender editors, and other macOS applications as well.\n\nAnother solution could be to use a smooth scroll like with the MMB.\n\n", "Modifier re-evaluation makes editing dimensions unreliable\nCurrently editing dimensions uses the bounding box that's recalculated while dragging.\n\nThis can cause a feed-back loop as the objects scale is used by some modifiers which calculate a new bounding based on the scale which is then used in dimensions.\n\nIn the case of armature modifier - any zero scaled axis makes causes the mesh to scale into a single point, making any further changes to the dimensions not have any effect.\n\n----\n\nOriginal report:\n\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 74)\nWorked: Blender 2.79\n\n\nIf object is rigged scrolling its dimension value toward zero causes object to disappear, even if right mouse button has been clicked in order to cancel a scaling. So blender accepts a scale of zero even if left mouse button hasn't been released yet, Is it an expected behavior in Blender 2.8?\n\n\n\n\n - Select the cube.\n - Scroll any of its dimensions value toward zero without releasing the left mouse button\n - Cancel scrolling by right mouse button click.\n\n\n\n[Bug_report.blend](Bug_report.blend)\n\n", "Scroll drag stuck after specific MMB click\nBlender 2.80rc1, 2.83 (sub 2)\n\nHere is the video\n[2019-02-26_06-35-31.mp4](2019-02-26_06-35-31.mp4)\n\n - Open Blender\n - In `Preferences -> Interface -> Menus` enable `Open on Mouse Over`\n - Close preference windows and go to any paint/sculpt mode\n - Display the sidebar and go to the Tool tab\n - Move mouse pointor over brush`s big icon and before it reacts with highlight (brush-search window appear) press and hold MMB\n - Then LMB to discard.\nNow scroll sticks. It releases after Esc or MMB. But at first I was forced to restart blender, because pointer stuck there.\n", "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." ]

[ "Zoom Border -> Crash (OSX)\nOS X 10.9 and NVIDIA GeForce 9600M GT 512 MB\n\nBroken: Blender 2.69 (and current Git build)\nWorked: Blender 2.68\n\nUsing the Zoom Border feature crashes Blender\n\n\n - Open default factory scene\n - Go to View -> Zoom Border...\n - Drag the box around the camera, cube and lamp\n - Crash" ]

[ "Use proximity for edit mesh mirror and mirror selection operator\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nIt is hard to select the corresponding vertex on the flipped axis side when the topology is non symmetrical and the corresponding vertices on the flipped axis side is slightly offsetted.\n\nIn order to fix this, it would be great with a \"proximity slider\" that selects vertices on the axis flip side that is within the range of the corresponding coordinate of your current selection.\n\n---\nUI mockup for viewport options\n\n\nUI mockup for operator \"Select mirror\"\n\n---\n\nUse cases below:\n---\n\nCurrent behavior works great when **Topology mirror == True** and the mesh on both side of the axis is connected (and the topology was \"built symmetrical\"). Even if vertices on the axis flip side is slightly offseted.\n\n[topology mirror.mp4](topology_mirror.mp4)\n\n---\n\nCurrent behavior does not work when the topology is built symmetrical, but the topology on both side of the axis is not connected (like the eyes in this case). And the mesh is slightly offsetted on the axis flip side.\n\n[symmetry does not work.mp4](symmetry_does_not_work.mp4)\n\n---\n\nCurrent behavior does not work when the topology is not completely symmetrical and the vertices on the axis flip side is slightly offsetted.\n\n[slightly non symmetrical topology.mp4](slightly_non_symmetrical_topology.mp4)\n\n\n\n\n", "Modifier are still evaluated even when not required.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.0.0\nWorked: never\n\nModifiers are evaluated, even when blank, for example a lattice modifier without any lattice, would still make depth graph calculation or something like that, that make each action (select, move, rotate, etc.) verry slower.\n\nCreate/ import a large object (60M poly mesh for example).\nAdd lattice modifier, let all option blank. \nDisable viewport visibility of this modifier.\nTry to move/rotate/scale the object in the viewport, the performance is really low.\n\nIn order to transform your mesh, you need to remove all modifiers, and add then back once transform is convenient.\n", "Only Render visibility for 3D viewport\nIt should be possible to show only objects that will be in the final render in the 3D viewport.\n\nCurrently disabling the overlay only does half of what the old Only Render option did, which is to hide non-geometry objects. The visibility part is important too, though more complicated now since the regular viewport depsgraph will not evaluate objects that are not visible in the viewport.", "Visibility differences when hiding from layer and object level properties\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.1.0 Alpha\n\nHiding collection/object from outliner with layer level property (eye icon) and object level property (screen icon) in nested releation\ngives inconsistent results\n\n**Steps to Reproduce**\n- Open attached file\n- Hide `Collection A2` with eye icon\n- Now hide `Collection A2` with screen icon\n\nRefer video: r6yA5iDHdn\n[collections_bugs.blend](https://projects.blender.orgattachment)\n\n<details>\n<summary> Original Report </summary>\n\n**Short Description**\nThere are 2 cases where:\n1. Watching viewport in rendering mode give different view in view-port and final render image or video\n\n a ) it's happening due some **not refreshed states from outliner on hide/show object and disable/enabled in render on `vieport`**\n\n b) it's especially observed problem around:\n\n - collections\n\n - moved collection to other\n\n - parent object from other collections\n\n\n2. Watching viewport and animation\n a) user operating object and all looks ok, then ruining animation and blender doing broken whole objects, relations and movements\n\n\n I can't save file that showing this, coz is unpredictable case for me when:\n1. Refresh states not working automatically from outliner in some cases, save/open file again solving problem.\n - also suggestion is to hide all child objects in parent when parent status is changed to hide to not child one per one, or give to hide just this object (eg. contex menu by RMB)\n - this management can solve problems around operation as in point 1,b) issye\n\n2. When refresh states not working on timeline and when just animation refreshing coordination **not when objects are moved,**etc. (just play changing eg. x,y,z on this same frame in case operations as move, scale, rotate not doing this - so backing to main frame when was operation, update etc. not giving effect, just play)\n - for both solution is suggestion to **give option for viewport rendering** as this same like final render, regarding the states and depth levels of parents/child/collections \n\n\nMaybe is know issue, maybe some on meet this and can explain better than me, or some part of code can be checked to see relations for this type issues.\n\n</details>", "Workbench: shadow/face still visible at clipped side of view\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\n\nClipping view do not clip shade effect\n\n\n\n[untitled.blend](untitled.blend)\n", "Mirror Pose: Custom center of symmetry\nAs it is now, the Mirror Pose operator works through a rig/root bone center, which is of limited use when the character has moved away from that center while animating. The center of Mirror Pose should be selected on a per armature basis and should be available in linked/proxied armatures for the animators to change never at rigging stage, so i would potentially display it only in pose mode in the tool bar or under the pose options..\n\n- In the armature, you could have a bone selector box, where you can pick the mirror bone and axis.\n- If nothing is selected then it defaults back to the current behaviour.\n\nNote that this design task is for poses only, and not other places, like sculpting, where mirroring is used.\n", "Affects only origins does not work for Point Cloud, Curves, Text objects\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: n/a\n\nAffects only origins does not work for Point Cloud, (new hair) Curves and Text objects.\n\n- Add Point Cloud (experimental), Curves or Text object\n- Set Affect Only: Origins\n- Try to move\n\n[AffectOnlyOrigin.mp4](AffectOnlyOrigin.mp4)", "Cycles box mapping not working with rotated texture coordinates\nubuntu 14.04, 630GT, 4930k\n\nBroken: 2.74\n\n\nbox mapping doesn't work with object mapping (object) if the object is rotated (only 1 side is properly projected)\n\n\n1. open the blend file\n2. copy \"Cube\" and rotate it (90 degress)\n3. render\n\n\n\n\n\n\n\n\n", "VSE's selection not centred to images\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.1.0 Alpha\nWorked: Never\n\nWhen zooming in enough to a selected image's corner, it can be seen that the selection box (white rectangle) reaches outside the image itself. It also happens with a scaled down \"color\" strip.\n\n- Open a \"Video Editing\" workspace and add a \"Color\" strip\n- Scale it down and zoom to a corner\n- To better notice the issue, play with the resolution of the Preview (in Properties)\n\n\nNotes & thoughts:\n- The selection box (white box) is unresponsive to \"aspect ratio\" changes (in Properties)\n- The drifting of the image is somewhat annoying, and sticking the selection box to the image wouldn't fix this.\nSince I don't know how pixel alignment works in the preview, I'm not sure about this, but it may work to instead drift the canvas, leaving the image put like the selection box currently does. So sticking the image TO the selection box.", "Randomize Transform + Affect Only Origins, not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\n\nRandomize Transform not working as expected with Affect Only = origin. Whole object is transformed rather than just origin.\n\nin the 3d view port go Options > Affect Only and tick Origins\nselect default cube\nTransform the cube using Object>Transform>Randomize Transform\n\nCube moves/rotates/scales when I'd expect only the origin to be affected\n\n", "SpaceView3D.draw_handler_add with PRE_VIEW draw type does not result in visible draws\nOperating system: MacOS 11.6.3, Ubuntu 18.04 LTS (issue exists in both)\nGraphics card: Intel UHD 630, Nvidia Quadro RTX 400 (issue exists in both)\n\nBroken: 2.93 LTS, latest master (b626edd751d64b269da12ef8e774ced2836c3c9e)\nBroken: 2.83.0\nWorked: 2.82\n\nBroke between good 189e96ba68 and bad d95e9c7cf8\n\n1. Startup Blender\n2. Go to scripting tab and create a new script\n3. Copy \"Triangle with custom shader\" code from: gpu.html\n4. Change draw_type param in draw_handler_add from\n```\n'POST_VIEW'\n```\nto\n\n```\n'PRE_VIEW'\n```\n5. Run script.\n\nExpected behavior:\nThe drawn triangle is visible.\n\nActual behavior:\nThe drawn triangle is not visible.\n", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "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", "PBVH Pixels should check on center uv coordinate.\nCurrently it checks on bottom left corner, but the painting is half a pixel shifted. By adding an offset of half a pixel this should reduce some artifacts.", "Generic way for modifiers to check user-edited flags\nThe simulation modifiers need to take care of invalidating cache when user edits are performed on the modifier itself, or its dependencies.\n\nFor the point cache (rigid body simulation, for example) this is done as a dedicated dependency graph node, which is hooked to the rest of the graph via a relation which has `RELATION_FLAG_FLUSH_USER_EDIT_ONLY` flag. The benefit of such approach is that a generic callback function can be used (without capturing any internal state of the graph). The downside is the more complex routing of relations.\n\nThe simulation nodes took a bit different approach: the nodes modifier has a special lambda callback which checks the node and dependency graph state:\n```Cpp\nmodifier_node->evaluate = [](...) {\n if (modifier_node->flag & DEPSOP_FLAG_USER_MODIFIED) {\n ...\n }\n}\n```\n\nSuch approach allows to access the modification state without extra nodes and relations, but it is not very generic: ideally the modifier-specific logic will be left to the modifier's \"apply\" callback.\n\nFortunately, there is a simple modification to the current nodes modifier callback we can do!\n\nGeneral idea: have a generic modifier node callback (for all node types) which will copy the user-modified flag from the modifier dependency graph node to the modifier data. The modifier's \"apply\" callback then can make decision based on this flag.\n\nPseudo-code of this proposal goes as following:\n```Cpp\nmodifier_node->evaluate = [modifier_index = ...](::Depsgraph * /*depsgraph*/, ...) {\n ModifierData *md_eval = object_eval->modifiers[modifier_index];\n if (modifier_node->flag & DEPSOP_FLAG_USER_MODIFIED) {\n md_eval-> flag |= MODIFIER_USER_MODIFIED;\n } else {\n md_eval-> flag &= ~MODIFIER_USER_MODIFIED;\n }\n}\n```\n\nUse the modifier index since it can be captured at the graph construction time, and will stay available even if the original objects are destroyed (the long-term goal is to allow the depsgraph be fully independent from the original scene after its Copy-On-Write was run). It is a bit annoying to do an index-based lookup in the list, but it is unlikely to show up in a profiler.\n\nThe geometry node modifier can immediately use this new flag. In a longer term the rigid body will do the same or be migrated to the new simulation framework :)\n\n" ]

[ "T97783 closed but not finished\nRefer to T97783\n\nRefer to T97783\n\nRefer to T97783\n\nRefer T97783\n\n\nHi Robert.\n\nI still didn't get an answer to my question which possibly could resolve the problem if answered.\n\nThe question stands:\nIs there a specific reason of showing the image frame in isometric view and hiding it in perspective?\n\nYou wrote:\n\"The wireframe is displayed in both cases:\nShow In > Perspective and Only Axis Aligned are enabled, but the current view is not aligned with an axis\nShow In > Orthographic and Only Axis Aligned are enabled, but the current view is not aligned with an axis\"\n\nI think don't understand the nature of the issue.\nAs a helper I'm sending a video.\nFor the explanation please follow this ticket: T97783\nI you still need my assistance let me know.\n\nKind regards,\nWitold.\n[OnlyAxisAligned.mov](OnlyAxisAligned.mov)\n\n\n\n\n\n" ]

[ "Masks overlay not visible with Mirror Modifier\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.5.0 Alpha\nWorked: Unclear. Tested all the way back until 3.1\n\nThe mask overlay is regularly disappearing when using modifiers. The most reliable to reproduce this issue is the Mirror modifier.\n\n- Add an object with a mirror modifier\n- Duplicate the object\n- Enter sculpt mode on one of the objects and create a mask\n- Exit sculpt mode, select the other object, then the primary object again and enter sculpt mode (The mask is no longer visible)\n- Use the shortcut `Alt Q` to switch to another object and switch back (The mask should now be visible)\n- Or disable the modifier and the mask should appear.", "Multres disabled in Sculpt Mode when under another modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.92.0 Alpha\n\nWhen stacking another modifer like Solidify or Mirror over (listed below in the modifier stack) the multires modifier it will disable you from sculpting on the subdivision levels when entering sculpt mode.\nInstead it will show the base resolution. If any modifier visibility is toggled or sculpt level is switched it will be fixed.\nSometimes when sculpting on an object with this bug it also crashes but I couldn't reliably reproduce this.\n\nI assume the intended effect would be that the modfiers other than the multire get disabled, but not the multires itself.\n\n- Add a multires modifier on the default cube\n- Subdivide 2 times\n- Add solidifiy modifier \n- Enter sculpt mode\nNow instead of showing subdivision 2 it will show the base mesh\n- Toggle any modifier visibility, subdivision level or the sculpt mode option \"Use Deform only\"\nNow it will be fixed. Toggle out and into sculpt mode again and it will show the bug again.\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", "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.", "Face Sets Hide/Show don't work with Industry Compatible keymap\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.83.0\nWorked: N/A\n\nWhen using the industry compatible keymap, the Face Sets tool doesn't work properly. The shortcut commands for hide/show are listed in the keymap settings but they don't function.\n[Keymap Settings ](9b6f1d6608.png)\n[Video of the Hide/Show not working ](80c4d51da2.mp4)\nThe shortcut works fine in the normal keymap settings however.\n\nIn the default sculpting workspace (*while using the Industry Compatible keymap settings*)\n\nFirst select the face sets tool and draw a few face sets, then attempt to use the ctrl/shift/alt + H shortcuts to isolate the particular face sets.\n\n\n\n", "Blender locks into Pose Mode if rig-object or the rig's collection is hidden\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.0.0\nWorked: 2.9 \n\nBlender locks into Pose Mode if rig-object or the rig's collection is hidden\n\nOpen Blender, add a rig.\nGo to pose mode, hide the rig object (toggle its viewport render or deactivate the collection the rig is in).\nBlender now stays in Pose-Mode unable to leave it without restoring rig visibility.\n\nIn 2.9 Blender automatically exits Pose mode in this scenario. (Desired behavior)\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).", "Hidden Face Set Boundaries unmasked after inverting the mask on Multires Modifier\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\nHidden face sets are not affected by changes in the mesh, colors or mask. So when inverting a mask, the hidden face sets will keep their state of masking intact.\nOn a mesh without a multires modifier it will keep the mask sharp between the face sets but when using a multires modifier it will smooth past what is hidden and what is shown.\nThe mask should remain sharp and accurate.\n\nIn this example I am hiding a face set (Shift + H) and inverting the mask (A) to compare the result on the left (no multires) to the right (with multires).\n[2020-07-27 13-54-29.mp4](2020-07-27_13-54-29.mp4)\n\n[bug.blend](bug.blend)\n\n- Open file\n- Hide center face set (green)\n- Draw mask somewhere on mesh that is visible\n- Invert mask\n# Show all face sets\nRepeat steps 2-4 for another object and compare results.", "Add In Front/Visible option to lasso and box mask tools\nCurrently Box Mask and Lasso Mask create the mask through the object, which is not useful in some cases. There should be an in front option to change this behavior. \n\nImplementing this by checking the vertex normal and view direction is trivial, but it won't work as expected on models with occluded vertices facing toward the view. We should evaluate if it is possible to implement vertex occlusion test in sculpt mode. If it is not, then we can use the vertex normal implementation. ", "UI Lists Filtering can have non-visible items active (e.g. after deletion) which lets you act on non-visible items\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.83 (sub 17)\n\nWhen using any UI list filtering, if you press the \"-\" several times, at some point you'll jump out of the list and start deleting things from the list without seeing them:\n\na short video to show more in detail\n[2020-05-15 08-44-35.mov](2020-05-15_08-44-35.mov)\n\nUse any list, that has more than a few elements,\nfilter it, \nstart deleting, \nthe active highlighting disappears at some point, \nkeep deleting\nfind out that you deleted things outside of the list that was filtered.\n\nOR\n[#76853.blend](T76853.blend)\n- Open File\n- Cube has 2 vertex groups [\"apples\" and \"oranges\"]\n- \"oranges\" is selected/active\n- \"oranges\" is not visible though because a filter for \"app\" is applied on the list\n- \"thus only \"apples\" is visible\n- hit the {key -} button\n- \"oranges\" will be deleted [without user knowing]\n", "Curve sculpting: occlusion by hidden parent makes the curves unresponsive to brushes.\nOperating system: Fedora Linux (Gnome Wayland)\nGraphics card: AMD\n\nBroken: 3.5.1\n\nSculpting the curves is not possible when hiding the parent and \"occluding\" the curves with the now invisible parent.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nAdd empty hair to the cube.\nAdd curves in sculpt mode.\nHide the cube.\nTry to sculpt the curves from the other side of the cube. \nDragging from inside the hidden cube and dragging from outside the hidden cube give different results, when it feels like it should not.\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", "Creating a new image texture in shader editor does not appear among the texture slots\nWindows 10 Pro 64bit, AMD Ryzen 5 2600, 16Gb RAM\nNVidia GTX 1060 6Gb\n\nWindows 10 Pro 64bit, AMD Ryzen 5 1600, 8Gb RAM\nNVidia GTX 1050Ti 4 Gb\n\nBlender 2.8 Beta 91a155833e59\n\nIf you are texture painting in one window and you modify the shader by adding/removing an image texture to it in another, it won't appear/disappear from the texture slot list until you change to edit mode (or anything else) and back. Another issue is that this way you can paint onto an image texture that is no more connected to the shader and it doesn't disappear even if you do the \"edit mode and back\" (TAB x2) trick.\n\nSteps: Add an image texture to the shader in the attached file, connect to the roughness for example, create a new texture for. It won't be in the texture slots list. Now TAB x2 in the 3D view, slot appears. Paint on it, delete the node from the shader. It is still in the list. TAB x2. It is no more in the list, but the 3D view still shows the texture.\n\n[test1.zip](test1.zip)", "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", "Meshes with the remesh modifier disappear when they are edited at the same time\n**System Information** :\nOperating system :Windows10, CPU:3950X\nDisplayCard: RTX4000\n\n **Blender version**: \nBlender:2.92\n\nWhen editing multiple objects in edit mode, if you edit more than one at the same time, some modifiers (such as remesh) cause the meshes to disappear.\n[2021-04-13 07-02-23.mp4](2021-04-13_07-02-23.mp4)\n\n- Open attached file\n- In edit mode select the face of an object\n- Scale (modifier updates correctly)\n- Deselect all and select the face of the other object\n- Scale (modifier updates correctly)\n- Select both faces\n- Scale (Meshes disappear)\n\n[UNTD_SIMPLIFIED.blend](UNTD_SIMPLIFIED.blend)\n\n---\n**Original description:**\n\nI added a lot of modifiers to these two objects.\n\nSelect one. Edit mode scale is fine. \n\nSelect two edit modes scale will disappear\n\nTest file : \n[UNTD.blend](UNTD.blend)" ]

[ "Sculpt Box Hide Undo+Redo cause artifacts when using smooth shading\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nAfter using box hide tool and doing Undo + Redo, it creates visible artifacts...\n\n\n1. Open the attached blend file and in sculpt mode, use the box hide tool to hide a part of the mesh.\n2. Then Undo the last step and then Redo it.\n\n[Box Hide Undo Redo Bug.mp4](Box_Hide_Undo_Redo_Bug.mp4)\n\nI get that issue in both of my machines. And I also checked by exporting and importing as an OBJ but always get the same case.\nHere's the exact file.\n[Box Hide Undo Redo Bug.blend](Box_Hide_Undo_Redo_Bug.blend)" ]

[ "Lagging out when using pose brush\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0\nWorked: (also had issue on 3.4)\n\nlags out when trying to use the pose brush, particularly after unchecking \"connected only\" getting rid of the multires modifier seems to fix the issue but I'd like to be able to use the pose brush while preserving my resolution.\n\n\"connected only\" is already unchecked in the attached file, so to see the error just try to move the mouse/use the pose brush and you will see the lag. This is a majorly cut down version of the file so it is much worse in the full version to the point where the file is completely unusable.\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", "“Surface Deform”-modifier is overwriting the whole modifier stack\nOperating system and graphics card\nFedora 27 / GeForce GT 740\n(OS-independent issue)\n\n2.79a - offical release - 8928d99270f\n\nUnlike the “Mesh Deform”-modifier, which is applying the changes in a relative fashion, the “Surface Deform”-modifier just overwrites the previous modifier/s with the absolute values of the transform.\n\n[bug_report_surface_deform_modifier.blend](bug_report_surface_deform_modifier.blend)\n\nPlease look into the attached blend-file to follow the examples:\n\nExample1: adding two times the same “Surface Deform”-modifier on top of each other yields the same result as just one or in fact any number of copies of this modifier, thus rendering the nature of the modifier-stack here somewhat useless. In contrast e.g. the “Mesh Deform”-modifier would apply each copy of itself as a relative transform, thus building upon the previous modifiers in stack and changing the output-mesh with every copy of itself.\n\nExample2: Using the “Multi Modifier”-option of the “Armature”-modifier usually takes the same data as the previous modifier as input. The results of the previous modifier and the “Armature”-modifiers are then mixed together, using the weights of the Vertex Group as “mixing guides”. But in the case of the “Surface Deform”-modifier being the previous modifier this seems not to apply and the “Multi Modifier”-option takes no effect at all.\n\nExample3: Adding the “Surface Deform”-modifier on top of “Armature”-modifier overwrites the effect of the “Armature”-modifier (and all other modifiers prior to the “Surface Deform”-modifier.\n\n( An additional oddity seems to me that there is no option to control the overall influence of the “Surface Deform”-modifier with a vertex group, as is usually the case with all other deform modifiers. This though is not part of the bug report and rather a small feature request – but if someone is already looking into the above issue, I figured it wouldn't hurt to mention it here as it is probably just a matter of copy and paste from any modifier that already has this implemented - I might be wrong here though of course - please forgive my ignorance.)\n\nThank you for taking your time to look into that issue.\n\n\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", "Copying in edit-mode copies the entire object, not the selection\nthere is an issue occurs when a part of (mesh) is copyed in the edit mode \nwhat happens when copying one part of a (mesh) and pasting it\nyou suppose to get this part only pasted ,but instead you get the whole (mesh) pasted\n\nfor examble if you have a cube model with a single face selected in the edit mode \nif you copyed then pasted it the result is the whole cube modele is pasted rather than the single face \n \n \n\n", "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", "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)", "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", "Particle Edit Breaks After Selecting a Mesh with Cloth Physics\nOperating system: macOS 10.13.6\nGraphics card: NVIDIA GeForce GT 650M 1024 MB\n\nBroken: at least 2.82 up to 2.92 experimental (I suspect it never worked since 2.80)\nWorked: 2.79\n\nParticle edit behaves like object edit mode, but the UI shows \"Particle Edit\" being active.\n- There is no circle typical for the comb tool around the mouse cursor.\n- No additional key points to select or black hair strands are rendered.\n- Instead of e.g. combing you will move the object around once you drag with the mouse.\nBasically everything except for the UI stays in \"Object Mode\".\n\nEffect On (broken):\n\n\nEffect Off (works as expected):\n\n\nBased on the default startup:\n1. Go to \"Particle Properties\"\n2. Add a particle system\n3. Set its type to \"Hair\"\n4. Add a second particle system\n5. Set its type to \"Hair\" too\n6. Add a new mesh e.g. \"Plane\"\n7. Go to \"Physics Properties\"\n8. Add \"Cloth\" physics\n9. Select the original \"Cube\" again\n10. Switch mode to \"Particle Edit\"\n\nWays to reverse the effect (make \"Particle Edit\" work properly again):\n- Either: Make a new file and append both objects of the old file\n- Or: Delete one of the particle systems on the \"Cube\" and undo the operation\n\nEven after reversing it you can restore the effect by selecting the \"Plane\" once.\nAt least two particle systems are required for the effect.\n\nThe effect can even be saved and stays the same after loading from the file again.\nThus I was able to create two files one with the effect and one without.\nThe file without the effect is a little bigger in size.\n\n[EffectOn.blend](EffectOn.blend)\n\n[EffectOff.blend](EffectOff.blend)\n\nIt took me a whole day to find the cause and boil it down so far.\nHope it helps and that it can be fixed with the provided info.", "Continuous Grab occasionally fails\nOperating system: Linux 5.9.10-arch1-1 (KDE Plasma desktop)\nGraphics card: NVIDIA GTX 980Ti (455.45.01)\n\nBroken: 2.80 - 2.92 master\nWorked: N/A\n\n\nMouse wrapping sometimes fails to transition screen edges, requiring at least a pixel of backpedaling with the mouse. This seems to affect all mouse-wrapping operators. Initially this report was written in terms of Shear, with which I've discovered this behavior.\n\nMesh edit mode Shear operator sometimes gets stuck on the toolbar side of window, showing the system mouse pointer (perhaps due to mouse passing over the toolbar?), needing at least one pixel of motion to the right to untangle it.\n\n[Video ](PeSL2fzKfT4).\n\nThis does not seem to occur if:\n- viewport is not touching window edge\n- window is made fullscreen\n\n\n- Make sure your window is not made fullscreen and that the 3D viewport is bordering window edges\n- Enter edit mode, select all and invoke Shear operator. Move the mouse continuously to the left, until it eventually gets stuck.", "Vertex Paint bug with Falloff Angle\nBroken: 2.79.x, Win32 & Mac\n\nSee video below.\n\nTo reproduce, set Falloff Angle to 45, and paint (one continuous stroke)\nwith the brush radius approximately equal to the object.\n\nAll by default (2D Falloff and Accumulate is OFF).\n\n[vertex-paint-falloff-angle-bug.blend](vertex-paint-falloff-angle-bug.blend)\n\n---\n\nSmall brush size is ok:\n\n\nIncreased size produces artifacts:\n\n\n---\n\n[vertex-paint-falloff-angle-bug.mp4](vertex-paint-falloff-angle-bug.mp4)", "Rotate sculpting brush may have an incorrect pen pressure behavior\nOperating system: Linux-5.9.12-1-default-x86_64-with-glibc2.17 64 Bits\nGraphics card: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.39.0, 5.9.12-1-default, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.4\n\nBroken: version: 2.92.0 Alpha\n\nThe sensitivity to pressure of the Rotate Brush in Sculpting mode appears to be too low: no matter how hard the pen is pressed on the pen tablet, disabling pressure sensitivity produces much more controllable/faster results. Potentially other brushes in sculpting mode could be affected as well in various ways (only a general impression; unclear as of yet).\n\nWith Grease Pencil, pen pressure sensitivity appears to be correct and similar to that observed with a typical drawing program (Krita). So, this does not seem to be a general problem with Blender or my own pen tablet.\n\nMy pen tablet is a Wacom Intuos 5 Large. In Tablet settings inside Blender Preferences > Input, Max Threshold = 1.0 (max), Softness = 0.0\n\n- Open the attached .blend file\n- Use the Rotate sculpting brush to attempt rotating the bumps on the provided plane object\n- Enable Pressure sensitivity for \"Strength\" in the brush and attempt it again applying maximum pressure on the pen tablet. Compare the difference in response\n\n[rotatebrush-veryhard.blend](rotatebrush-veryhard.blend)\n", "Live unwrap interaction changes unwrapping and ignores pinned vertices\nBroken: 2.79 - 2.83 (sub 10), commit date: 2020-03-19 13:43, hash: `42012493a8`\nWorked: Never\n\nGrabbing and moving one of the pinned vertices seems to kind of reset the unwrap, even ignoring the pinned vertices.\nShort video demonstration:\neesv3\n\n- Unwrapped parts of an object.\n- Pinned some vertices in UV editor\n- enabled live unwrapping.\n\nor\n\n- Open this file: [LiveUnwrapPinFail.blend](LiveUnwrapPinFail.blend)\n- Go to edit mode\n- Move pinned vertices.\n\n\nIn some cases it also just doesn't do anything at all:\nignig\nHere is a file showing this other problem:\n[LiveUnwrapCube.blend](LiveUnwrapCube.blend)", "Sculpt mode transform tools. Weirdness with 3d cursor.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.2 26.20.13003.1007\n\nBroken: version: 2.81 (sub 11)\n\n1. In sculpt mode transform tools strange behavior with 3d cursor. Trying rotate part of the mesh, first rotation might be ok and second sometimes ok, but then rotation is going crazy. Exit to object mode then again enter sculpt mode, rotation is ok, but only for 1-2 times then again it acts weird (watch the video 1).\n\n2. Scaling in sculpt mode with 3d cursor not like in edit mode, it is very strange (watch the video 2).\n\n1. Open attached *.blend file, rotate several times, (do not cancel rotation with rmb!).\n\n2. Open attached *.blend file, select scale tool, try to scale, go to edit mode try to scale, see the difference?[video_1.mp4](video_1.mp4)\n\n[video_2.mp4](video_2.mp4)\n\n[bug_rot_scale.blend](bug_rot_scale.blend)", "Bug when opening a file in sculpt mode, making N strokes, and undoing N times\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.90.1\nI know it says branch: master (modified), but the changes are just some print statements in build_files/utils/make_utils.py; nothing involving the actual Blender source code.\n\nAfter opening a blend file in sculpt mode, making one stroke and pressing undo causes an error. The same happens after N strokes and N undos(back to the original file state).\n\nThe following is a video showing what happens: [[ nRUn6EFqNlA ]], and I've also attached [sketch0.blend](sketch0.blend)\n\nsince I'm not able to reproduce it on a simple file. Note in the video that in addition to the obvious visual glitch, the \"dyntopo\" check mark in the top right gets cleared.\n\n1. Open the given file (it is saved in sculpt mode, with dyntopo and symmetry turned on).\n2. Make any stroke anywhere, and then press Ctrl-Z to undo.\n3. The same will happen if you make N strokes and undo N times.\n\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" ]

[ "Sphere is does not showing color in solid mode from material\nOperating system: Windows 11\nGraphics card:\n\n3.5\n\nWe have created a plugin to add multiple spheres, the plugin is attached below.\nafter adding active material to all spheres when we are adding color the sphere is at the 4096th location is does not show color\nPFA:\n\n\nThe black sphere is also having color in its material but it is not showing as the sphere is at the 4096th location\nPFA for material data\n\n\nAlso, the color is also visible in another mode currently it is solid panel mode. for our internal uses, we are using the solid mode \nCan we have any workaround for this fix or please fix this bug? What I presume is while displaying material in the solid mode we are not managed properly in our code as this bug continues for every sphere count of multiples of 4096(2 power 12).\n\n", "Stereoscopic render - Convergence Plane doesn't show in the cameraview while in viewport\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.0\nWorked: version: 3.4.1\n\nConvergence Plane doesn't show in the cameraview while in viewport. It work when the mode is in Toe-in but not in off-Axis.\nI made the exact same steps in 3.4 and it works.\n\n- Render engine : Cycles\n- Output properties : stereoscopy\n- Objecte data properties : \n - Lens type : panoramic \n - Panorama type : Equirectangular\n -Stereoscopy \n - Mode : Off-Axis\n -Convergence Plane : doesn't change in the cameraview but we can see the plane in the viewport\n\n\n[Based on the default startup .blend file (as simple as possible)]\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)", "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)", "Some particles do not appear in the render when the 'Vector' pass is enabled\nOperating system: Linux-5.19.17-2-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: 3.2.2 - 3.3.1\nWorked: 2.79\n\nParticles in Render don't match particles in viewport. Some particles do not appear. When they move very fast the issue is more visible.\nIt happens when we enable the pass `Vector`\n\n- Open attached file or:\n - In the default scene (with the Cube), add a Plane\n - Add a ParticleSettings toe the plane\n - In {nav Particle Properties > Render} set `Render As` to `Object`\n - For the `Instance Object` choose the Cube\n - In {nav Particle Properties > Field Weights} set `Gravity` to `0.0`\n - Optionally bake for cache\n - Set `Render Engine` to `Cycles`\n - In {nav View Layer Properties > Passes > Data} enable `Vector`\n - Move Cube out of camera view\n- Choose a frame in the middle and render\nNote that the particles closest to the plane disappear\n\n[particles displaced.blend](particles_displaced.blend)\n\n", "Xray doesn't work in wireframe shading for objects set to display as wire.\nBroken: 3.0\nWorked: \n\nXray doens't work in wireframe shading mode for objects set to display as wire.\n\n- Open .blend file\n- Change the viewport shading to wireframe.\n- Set one of the cubes to \"Display As : Wire\" in object properties->viewport display.\n- change X-ray value from `Viewport Shading` popover\n- compare the two, only one has xray effect.\n\nTest File:\n[#94802.blend](T94802.blend)", "No preview icon in the material list\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 536.40\n\nBroken: version: 3.6.1\nWorked: (unknown)\n\nI noticed that for this material in the list it is not previewed, but in the \"Preview\" panel the preview is correct.\nThis is a simple setup of mixing 2 shaders using the \"Alpha\" attribute as a factor.\nThis situation makes it difficult to work when only using the drop-down list of materials in various situations..\n\nThx.\n\n", "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)", "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", "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)", "No visible mesh on Viewport Screenshot in sculpt mode with Multires\nOperating system: Linux-6.2.11-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.36 64 Bits, X11 UI\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Alpha\n\nWhat the title says.\n\n- Add a cube\n- Enter sculpt mode\n- Add a multiresolution modifier and subdivide\n- Use the operator: Header -> View -> \"Viewport Render Image\"\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).", "Blender viewport rendering incredibly slow when certain objects are visible when switching from Solid to Rendered\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.3.1\n(Every version from 3.0.0 to 3.3.1 has this issue)\nWorked: 2.93.9\n\nWhen rendering scene or viewing scene from Rendered view, rendering is orders of magnitude slower than normal. If large objects are hidden and then un-hidden while in Rendered view, rendering runs at normal speed.\n\nOpen the included .blend file\nGo from \"Solid\" view to \"Rendered\" view\n(Render speed should now be severely hindered)\nWhile still in Rendered view, hide the object named \"Fog\" and then un-hide it\n(Render speed is now significantly faster.)\n\n[away.blend](away.blend)", "USD Export don´t export Vertex Colors ( Color Attributes )\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40\n\nBroken: version: 3.2.0\nWorked: Not known\n\nUSD Exporter don´t export Vertex Colors ( Color Attributes )\n\nJust paint some VC on the default cube with Vextex Paint Mode, then try to export the cube. \nExporter don´t have the \"Color Attributes\" checkbox ( Importer has it )\nYou can then try to reimport the USD file and check that your VC aren´t there.[CUBE.blend](CUBE.blend)\n\n\n", "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" ]

[ "Window doesn't update in Windows under high contrast mode\nWindows 8.0 Intel Graphics 4600\n\nBroken: 2.72b\nWorked: (optional)\n\nUsing this high contrast theme will cause blender to not open correctly and will not take commands for the mouse or keyboard\n\n1. Use the attached theme for windows\n2. Open Blender \n", "Window does not update when under Windows 10's high contrast mode\nThinkpad S440 running Windows 10\nUsing the Haswell-generation Intel integrated GPU that came with the i5.\nAdditionally have an AMD 8670M, but not using it with Blender.\n\nBroken: 2.75a\nWorked: (optional)\n\nThe UI only updates when you resize the window, not when input (clicking, keypresses) is received unless you disable High Contrast mode.\n\nMake sure you save your Windows 10 theme first so you don't lose it.\nSearch for \"high contrast\" in Windows 10.\nSelect \"High Contrast #1\" from the theme picker and click apply.\nLaunch Blender.\nThe window remains grey.\nResize it.\nThe contents are now shown.\nTry clicking in the viewport around the splash screen.\nNothing happens.\nResize the window.\nThe splash screen is now gone; it had accepted your input, but not updated the display.\nSimilar input like clicking on the menu bar or dragging in the viewport exhibits the same symptoms.\nThe only workaround is to disable high contrast mode." ]

[ "AlembicObjectPath has a fixed-size char[]\nAlembicObjectPath (see `DNA_cachefile_types.h`) has a fixed-size char- [ ] buffer. \n\n> In 3128600a8a#142412, @LazyDodo wrote:\n> if the object path can be arbitrarily large it's gonna be a matter of time before someone comes with a file with 4097 byte object path, why not just allocate the ram you need? \n\n\nI think that's a good idea, and that's what this task is for.\n", "Lots of animation-related operators do not check if the data is editable or not\nMany animation-related operators do not do any check whether the data-block they operate on is linked, liboverride or fully local data. This seems to affect in particular operations from the 3DView (like key insertions), and in the NLA (like adding new tracks, duplicating strips, etc.).\n\nE.g. one can insert keyframes on a linked object (ie create animdata for that linked object, a new local action, and assign that local action to the linked object!).\n\nRelated to issue reported in #98686 (Cant rename local NLA tracks within a local library override data-block.).", "Python Operators that add/remove ID data without an undo step crash Blender\nOperating system: Win 10\nGraphics card: GTX 1070\n\nBroken: 2.8.3, 2.9 aed11c673efe\nWorked: 2.8.0\n\nUndoing after object linking to the scene crashes blender. I used the latest daily build\n\n1. Load the crash blend file [crash_modal.blend](crash_modal.blend)\n2. Run the script attached\n3. Click in viewport to add a new object, and then press ESC\n4. Press Ctrl+Z to undo\n5. Crash..\n\n", "Error message and unable to edit a skeleton when using a library override armature\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.0\nWorked: No idea.\n\nBlender generates an error when you attempt to enter edit mode on a library overriden armature. There's no description of what the error is or if there is some extra step to make it work. Hopefully this isn't one of those, \"works as intended issues,\" because then there's no way to make multiple characters share an updateable base rig.\n\n\n- Add an armature, enter edit mode, extrude out a few bones.\n- Save the file and open a new scene.\n- Link in the armature you just created.\n- Make the armature a library override.\n- Try to enter edit mode. Should get an error.\n\n", "Failing assert when choosing custom icon for brush\nOperating system: Linux-5.9.16-100.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.92.0 Alpha, latest master\nWorked: Master on September 15th still had this issue, I don't plan on bisecting further\n\n\nClicking on the \"Custom Icon\" button to the right of the preview causes an assert to fail in debug builds\n\n- New file\n- Sculpt mode\n- Active tool settings in property editor\n- Click twice the picture icon to the right of the ID template\n", "Quick Favorites: add support for operator/prop enums (e.g. \"Set origin\")\nOperating system: Windows 10\nGraphics card: Nvidia GTX1080\n\nBroken: 2.80, 16fc62e15f0, blender2.8, 2018-12-12\nWorked: 3d92afca7eb\n\nThe Set origin menu is not possible to put into quic favourites.\n\n3dView -> Object menu -> Right click on \"Set origin...\" -> empty menu.", "File selector dialog: long file extension filtering does not work\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 615 Intel 4.5.0 - Build 27.20.100.8854\n\nBroken: \nversion: 3.0.0 Beta\nversion: 2.93.5\nWorked: probably never\n\nIf you try to filter files inside the file selector with filter_glob, this only works for extensions with a max. length of 15 chars including `*.`\n\nBecause today some file extensions are much longer, I would suggest to increase the maximum allowed file extension length.\n\nCreate a file with the extension `.12345678901234567890`\nLoad the attached script and navigfate to the folder where you created the file.\nIt will not displayed in the file selector.\n\n[operator_file_import_test.py](operator_file_import_test.py)\n\n**Solution**\nIn [path_util.c ](path_util.c) in the function `BLI_path_extension_check_glob` the search pattern is limited to 16 chars.\nI would suggest to increase this value to 33 chars.\n", "Text object Tab glyphs need special handling\nWhile we have special handling for the horizontal displacement of tabs, it seems most system fonts actually do not have a tab glyph itself, and they are doing something different than bfont with regards to the reference to .notdef -- leading blender to place the missing-tab glyph in their place. I've evaluated numerous fonts, and searched my entire system font folder for those with tab glyphs, and almost none actually have them. This leads me to believe that, I believe, we need some additional handling, at least for the tab character, to handle the missing glyph(s) in Text Objects.\n\nAttached is a blend with FreeSerif.ttf, FreeSans, Liberation something, and FreeSans.otf:\n(Linux, Debian, different versions. 2.90, 2.91 alpha... Standard system fonts from /usr/share/fonts/truetype/ and /usr/share/fonts/opentype/\n[tab.blend](tab.blend)\n\nThe attached shot is blender with FreeSerif (same with most others).\n\n\nBfont works fine. It is missing the glyph, but 9 refers to U+fffd / .notdef:\n\n\nBfont's 9 (with the .notdef ref):\n\n\nFreeSerif, at U+fffd (I don't see it specifying .notdef, but it is set as a replacement char):\n\n\nFreeSerif's tab (9)\n\n\nDejaVuSans.ttf (9)\n\nDejaVuSans.ttf (U+fffd)\n\nDejaVuSans in Blender with tabs\n", "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).", "(Unneccessarily) restricted execution in scripted expression drivers (using e.g. \"self\", \"bpy.data\")\nOperating system: Linux-5.15.0-69-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 22.2.5\n\nBroken: version: 3.5.0\n\nself causes error in scripted expression drivers\n\nIn scripted expression drivers using expression \"self.location.x\" from Blenders manual and \"self.location[0]\" from online examples both fail with \"ERROR: Invalid Pythpn expression\".\nI have enabled \"Use Self\" in driver and \"Auto Run Python Scripts\" in preferences\n\n", "Allow menus to be added referenced to another menu \n## Motivation\nAddon developers cannot add menus on specified place. \nThey are always added at the end (append), or at begin (prepend)\n\n## Analysis\nAfter a look at current code, i think a good approach should be allow to define a reference label on append function.\n\nWhen drawing the menu layout, a new RNA call should be done on a new function class, that should then execute the referenced drawing calls on py scope.\n\nIssue with this development is that for any but menu drawn two python calls are performed to allow addons draw before and after itself. Maybe this could be solved checking in C scope if it has post/pre functions added.\n\n## Development steps\n* {icon check-square-o color=green} Draw after label\n* {icon check-square-o color=green} Draw before label\n* {icon check-square-o color=green} Give warning if not used (label not found)\n\n## Know Issues\n* Issues with enums, if shown as submenu it's not working. Is shown on self menu, the label is the operator name, and considered a block\n\nFeedback is welcome!\n\n\n\n\n", "Cannot to make single user in object properties (if object is used by multiple collections)\nOperating system:\nGraphics card:\n\nBroken:\n\n\nI made a linked copy of an object (not object data!) in another collection by dragging the object from one window of the outliner to another.\nNow in object properties showing amount users equals 2:\n\n\n\nif you click on button \"make a single copy\" then nothing will happen. I am not sure but seems this UI inconsistency\n\n\nOpen the file and try to make single user to click in object property window:\n\n[make-single-copy.blend](make-single-copy.blend)", "[winerror 233] .glb, .gltf\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.42\n\nBroken: version: 3.6.2\n\n\n\ncant import .glb or .gltf files\n\n", "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", "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" ]

[ "Copy Previous Settings Not Working, with accented Username\nWindows 8.1\n\nBroken: 2.70 19f7f9a\n\nWhen I click on Copy Previous Settings, the fallowing error message pops up.\n\nI suspect, that it is caused by the accent in my (Auto generated thanks to Windows 8) account name. Also I cant set any path which consist my account name as simulation target. When I does, it sticks at 0 and loads forever,\n\n**Error message:**\n*\"A hozzáférés megtagadva\" - Access Denied*\n\nTraceback (most recent call last):\n```\nFile \"C:\\Users\\Iván\\Desktop\\Blender Source\\blender-2.70-RC1-windows64\\2.70\\scripts\\startup\\bl_operators\\wm.py\", line 1315, in execute\n shutil.copytree(path_src, path_dst, symlinks=True)\nFile \"C:\\Users\\Iván\\Desktop\\Blender Source\\blender-2.70-RC1-windows64\\2.70\\python\\lib\\shutil.py\", line 295, in copytree\n os.makedirs(dst)\nFile \"C:\\Users\\Iván\\Desktop\\Blender Source\\blender-2.70-RC1-windows64\\2.70\\python\\lib\\os.py\", line 266, in makedirs\n mkdir(name, mode)PermissionError: [WinError 5] A hozzáférés megtagadva: 'C:\\\\Users\\\\Iván\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.70'location: <unknown location>:-1", "Username with special chars in Windows 7\n%%%With Windows 7 pro 64bit and blender 2.63a i get an error if my username contains special chars, like \"сидорович\" (russian). Output follows:\n\n>>>\n\nfound bundled python: C:\\games\\blender-2.63a-release-windows64\\2.63\\python\nTraceback (most recent call last):\n```\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\scripts\\modules\\bpy\\utils.\n```\npy\", line 484, in user_resource\n```\n _os.makedirs(target_path)\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\python\\lib\\os.py\", line 14\n```\n4, in makedirs\n```\n makedirs(head, mode, exist_ok)\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\python\\lib\\os.py\", line 14\n```\n4, in makedirs\n```\n makedirs(head, mode, exist_ok)\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\python\\lib\\os.py\", line 14\n```\n4, in makedirs\n```\n makedirs(head, mode, exist_ok)\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\python\\lib\\os.py\", line 14\n```\n4, in makedirs\n```\n makedirs(head, mode, exist_ok)\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\python\\lib\\os.py\", line 14\n```\n4, in makedirs\n```\n makedirs(head, mode, exist_ok)\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\python\\lib\\os.py\", line 14\n```\n4, in makedirs\n```\n makedirs(head, mode, exist_ok)\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\python\\lib\\os.py\", line 14\n```\n4, in makedirs\n```\n makedirs(head, mode, exist_ok)\nFile \"C:\\games\\blender-2.63a-release-windows64\\2.63\\python\\lib\\os.py\", line 15\n```\n2, in makedirs\n```\n mkdir(name, mode)\n```\nWindowsError: [Error 5] Access is denied: 'C:\\\\Users\\\\С\\u201eРёС\\u201aР°С\\u040fС\n\\u2021'\n<<<\n\nI get this error when installing some plugin (in fact just pressing ctrl+alt+u>addons>install addon>ok button). If i try to save or load my work i see an empty:\n\nC:\\Documents and Settings\\\n\nEven if i have users written only with normal symbols like \"james\" or \"brown\" and my testuser \"сидорович\" in the same folder.%%%" ]

[ "Smoke and Fire simulation bug\nOperating system: Mac osx 10.15.6\nGraphics card: AMD Radeon Pro 5500M 8 GB\nIntel UHD Graphics 630 1536 MB\n\nBroken: 2.90.0 (202-08-31)\n\n\nBlender crashes while trying to bake a fire + smoke simulation in 128 resolution divisions... Sometimes it works. Mostly it doesn't.\n\nAttaching the file.\n\n[Blender Bug copy.rtf](Blender_Bug_copy.rtf)\n\n[fire.blend](fire.blend)", "Error \"NotImplementedError: bevel: keyword \"custom_profile\" type 4 not working yet!\" when attempting to use custom_profile keyword in bmesh.ops.bevel\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.1.2\nWorked: No previous working version known\n\nTried to call bmesh.ops.bevel with custom_profile keyword argument. Got \"NotImplementedError: bevel: keyword \"custom_profile\" type 4 not working yet!\" error.\n\n\nOpen the attached blend file.\nGo to the Scripting workspace\nCopy the text in the Text editor\nPaste it to the python console.\n[bmesh bevel bug.blend](bmesh_bevel_bug.blend)", "Optix not available after Manjaro Update\nOperating system: Linux-5.17.1-3-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.1.2\nWorked: both 3.1.0 as well as 3.1.2 was working before the Manjaro update. Version 3.0.0 is still working, regardless of the OS update.\n\nSince the last Manjaro Update I get an error message when I try to switch to rendered view in Blender 3.1.2 :\n```\nFailed to load Optix Kernel from: '/_DATA_WK/Blender/blender-3.1.2-linux-x64/3.1/scripts/addons/cycles/lib/kernel_optix.ptx' (OPTIX_ERROR_INVALID_FUNCTION_USE)\n```\n\nI tested it with Blender installed from the Manjaro Repository as well with Blender from Blender.org (extracted to the above location).\nBoth of them gives the same error message (with different kernel_optix.ptx location of course.)\nThey were working perfectly before the OS update. Blender 3.0.0 still works fine. \n\n- Start Blender. (No need to load any file or content).\n- switch to Rendered Viewport Shading. \n\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", "Incorrect full data path copying viewport shading parameters ('Screen' object has no attribute 'shading')\nBlender 3.6.2\n\nWay to reproduce:\n1) Any blender project\n2) RMC on any of \"Viewport Shading\" icons and choose \"Copy Full Data Path\".\n3) Paste it in python console, it will result in the error `AttributeError: 'Screen' object has no attribute 'shading'`\n4) Same goes for the other parameters from the viewport shading menu.\n\nGuess it should be returning something like \"bpy.data.screens[\"Layout\"].areas[3].spaces[0].shading.type\" in this case.\n\nDemo attached.\n", "File->Data Preview->Batch Generate Preview failed\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\n\n\nThis Menu give a error and no work\nFile->Data Preview->Batch Generate Preview \n\nLog : Previews generation process failed for file 'D:\\Cours et Note\\Blender Cours\\Cours avec Mykol en Francais Blender 3.0\\fichier du cours\\xam Collection.blend'!\n\n", "FPS problem (movie import)\nOperating system: Windows 10\nGraphics card: rtx 2070\n\nBroken: \nWorked: Blender 3.5.1 \n\nWhen I import a 30 fps video in blender (in \"movie clip editor\"), this video will be interpreted as 120 fps per blender, making motion tracking impossible.\n\nimporting a 30fps video in movie clip editor\n\n", "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.", "Add Existing Import/Export Functionality to Collection Properties\n**Problem Statement**\nCurrently importing and exporting files like glTF, FBX, Alembic or USD is done through operators. This is fine for a one time export, but when re-importing or re-exporting the same asset many times it becomes cumbersome. We need to store relations to such files and settings permanently, so re-import and re-export is quick, and may even be done automatically on changes.\n\n**Collection Settings**\nThe basic idea is that Collection datablock would get settings for import and export.\n\nFor export, a collection could have one or more associated exporters. Blender would natively support USD and Alembic exporters. However this could be an API that Python add-ons can plug into, to also support file formats like FBX and glTF. The settings would be defined by the exporter, and could be exactly the same as existing export operator properties. Once export settings are set up, re-exporting one (or all) collections would be a single click, much like rendering.\n\nFor import, the simplest case would be similar to export. A collection would have one associated importer and settings. Re-importing would be done with a single click as well. This would delete the objects in the collection and add new objects, however any changes to these objects would be lost.\n\n---\n\n\n**Goal**\nThe first step will be to wrap the existing import and export logic using Collection Properties.\n\n\n**Requirements**\n- A user should be able to select the file for import/export\n- A user should be able to set the required import/export parameters\n\n- A user should be able to import all data from a supported file type as children of the selected Collection.\n- A user should be able to re-import all data from the selected file. This would delete the objects in the collection and add new objects, however any changes to these objects would be lost.\n - This would probably require a pop up to ask the user if they are sure the want to re-import and overwrite the collection children\n\n- A user should be able to export all objects that are a child of the Collection back to the selected file.\n- A collection could have one or more associated exporters. \n - This was mentioned in the main design task, is it a realistic/requested use case?\n\n**Design Goals**\n- It should be generic enough to be usable for any importer/exporter\n- Start thinking about how the Collection data block should be updated to support the longer term goals of using the collection properties import/export as a sort of live library to the file contents.\n\n\nAn initial thought for a UI design could be something like below (all the relevant import/export parameters have not been added to the list). Ideally we should be able to re-use the existing operator an UI logic as much as possible.\n\n\n**Implementation Notes**\n- Import for USD already has an option to import all objects to the active collection. Not much needs to be changed there.\n- I believe export for USD only currently supports options for All, All Selected, All Visible. Would have to be updated to support exporting all children of the active collection.\n- (I am unfamiliar with the other import/exporters)\n\n**Questions**\n- If there is work that needs to be done for each individual file type to support this workflow, who is responsible for that implementation? Does it fall to the owner of the importer, or should they all be tackled together before moving on to the next phase of this work?\n\n**Technical Design**\n\nTo support import, the Collection data-block would need to be updated to store the import filepath and the import parameters. If we want to keep this as generic as possible, what would be the best way to store these parameters? Obviously each format will have a different set of parameters, and we want to keep it generic enough to be easy to add other formats in the future. Currently the import parameters are contained entirely in their respective modules (`USDImportParams` used only in `../io/usd` and `.../io/editors/usd`), how should the parameters be exposed at a lower level?\n\nTo support a single file export, the same technical requirements and questions apply regarding best way to make generic. To support multiple file export, Collection will need to store a list of export parameter blocks.", "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", "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*", "Pixels and resolution not for multilayer EXR and Render Result\nCentOS - GTX 1070\n\n2.79\n\nPixels and resolution are not available with multilayer EXR or Render Result images.\n\nimport bpy\ndata = bpy.data\nimage = data.images['Render result or multilayer EXR']\nprint(image.pixels) # length is 0\nprint(image.resolution) # return always Vector((0.0, 0.0))\n\nIt is working with regular EXR file.\n", "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "Regression: bpy.utils.register_class() \"can't run in readonly state\" error when run from Text Editor\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked: 4.0.0 Alpha, branch: main, commit date: 2023-09-01 21:43, hash `de09bdb510a0`\n\nRunning `bpy.utils.register_class()` from the Text Editor raises `RuntimeError: register_class(...): can't run in readonly state 'TestOp'`.\n\nRunning from the Python Console instead has no issues.\n\nRun in the Text Editor (or use and run one of the many Python Templates in the Text Editor that also use `bpy.utils.register_class()`):\n```py\nimport bpy\n\nclass TestOp(bpy.types.Operator):\n bl_label = \"Test Op\"\n bl_idname = \"test.op\"\n\n def execute(self, context):\n return {'CANCELLED'}\n\nbpy.utils.register_class(TestOp)\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?" ]

[ "Ошибка экспорта файла в FBX\nPython: Traceback (most recent call last):\n```\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\__init__.py\", line 644, in execute\n return export_fbx_bin.save(self, context, **keywords)\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 3198, in save\n ret = save_single(operator, context.scene, depsgraph, filepath, **kwargs_mod)\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 3094, in save_single\n fbx_objects_elements(root, scene_data)\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 2894, in fbx_objects_elements\n fbx_data_mesh_elements(objects, me_obj, scene_data, done_meshes)\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 1174, in fbx_data_mesh_elements\n elem_data_single_int32_array(lay_uv, b\"UVIndex\", (uv2idx[uv_id] for uv_id in _uvtuples_gen(t_luv, t_lvidx)))\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\fbx_utils.py\", line 504, in elem_data_single_int32_array\n return _elem_data_single(elem, name, value, \"add_int32_array\")\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\fbx_utils.py\", line 451, in _elem_data_single\n getattr(sub_elem, func_name)(value)\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\encode_bin.py\", line 161, in add_int32_array\n data = array.array(data_types.ARRAY_INT32, data)\nFile \"C:\\Program Files\\Blender Foundation\\Blender 2.93\\2.93\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 1174, in <genexpr>\n elem_data_single_int32_array(lay_uv, b\"UVIndex\", (uv2idx[uv_id] for uv_id in _uvtuples_gen(t_luv, t_lvidx)))\n```\nKeyError: ((nan, nan), 7206)\n\nlocation: <unknown location>:-1\n\n", "FBX export error because of invalid NaN UV values.\nOperating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 3.3.1\nWorked: never\n\nExport of an element from attached file in FBX format cause error until UV is not removed.\nTested on 3.2, 3.3.1, 2.79\n\n[3.2 fbx error.blend](3.2_fbx_error.blend)\n```lines=10\nPython: Traceback (most recent call last):\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\__init__.py\", line 655, in execute\n return export_fbx_bin.save(self, context, **keywords)\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 3243, in save\n ret = save_single(operator, context.scene, depsgraph, filepath, **kwargs_mod)\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 3134, in save_single\n fbx_objects_elements(root, scene_data)\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 2932, in fbx_objects_elements\n fbx_data_mesh_elements(objects, me_obj, scene_data, done_meshes)\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 1179, in fbx_data_mesh_elements\n elem_data_single_int32_array(lay_uv, b\"UVIndex\", (uv2idx[uv_id] for uv_id in _uvtuples_gen(t_luv, t_lvidx)))\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\fbx_utils.py\", line 494, in elem_data_single_int32_array\n return _elem_data_single(elem, name, value, \"add_int32_array\")\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\fbx_utils.py\", line 441, in _elem_data_single\n getattr(sub_elem, func_name)(value)\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\encode_bin.py\", line 143, in add_int32_array\n data = array.array(data_types.ARRAY_INT32, data)\n File \"C:\\Users\\prati\\OneDrive\\Desktop\\BlenderOSP\\2022_lite_ninja\\bin\\3.5\\scripts\\addons\\io_scene_fbx\\export_fbx_bin.py\", line 1179, in <genexpr>\n elem_data_single_int32_array(lay_uv, b\"UVIndex\", (uv2idx[uv_id] for uv_id in _uvtuples_gen(t_luv, t_lvidx)))\nKeyError: ((nan, nan), 34)\n```" ]

[ "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "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", "\"Input Pending\" for Loop Cut and Slide when called from menu.\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 1660Ti\n\nBroken: 3.3.2\nWorked: 2.93\n\n**Caused by:** da2ba402689d7ed752b0b37ad49dce1a5851cc77\n\n**Reproducing the error:**\n\n- Ctrl+R on default cube edit mode, regardless of selection mode, loop cut slide works as usual.\n- Use search menu or header->edge menu and select loop cut slide, header bar only shows \"Input Pending\", if pressed left mouse, then operator runs correctly. If pressed right mouse, then operator is cancelled.\n\n\n\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", "UI: Discussion Topics & Possible To-Do's for 3.0\n3.0 is the next chance to do breaking changes which should not go into normal releases. That may be: higher level design changes, muscle memory breaking, documentation breaking (e.g. changed operator names) or non-trivial visual changes. There should still be no .blend file compatibility breaking changes.\n\nIn this task we can collect such changes for consideration. This is not a \"wish a feature\" list. These are things we discussed already but couldn't do earlier because they would be too disruptive.\n\n* Active vs. selected (#82359 (Stronger binding of Active and Selected))\n* Keymap polish\n\n - Consistent selection with modifier keys #78253 (Formalize Default Selection Behavior and Key-map)\n - {key 1}/{key 2}/{key 3} for changing into vertex/edge/face edit mode #88071 (Keymap: use number keys for mode switching (2nd Iteration))\n - {key D} for view-navigation sub-menu #88092 (Keymap: use D-key for view navigation pie-menu (2nd iteration)).\n - {key Alt} usage #83689 (Default Keymap Update: Improve tool access using Alt-LMB)\n\n* Toolsystem wrap-up (change toolsystem defaults if needed)\n* Theme polish (#74358)\n* General defaults (Preferences, startup configuration, bundled workspaces, etc)\n - [ ] Set default subdivision modifier levels to be 1 for viewport and render.\n* More dynamic file selection (e.g. show import/export settings based on file selection)\n* Reevaluate closing popups on mouse moves.\n* Improve naming:\n**Avoid \"link\" for anything unrelated to link/append (e.g. *Link Materials* -> *Share Materials*).** Correct usages of \"copy\" (e.g. *Copy Modifiers* -> *Replace Modifiers*).\n* 3D cursor default orientation method to \"Surface\"\n* #89266 (Investigate renaming the \"Video Sequencer\" editor)\n* #83612 (UI: Tracking: Migrate to active tools based toolbar)", "UV: Copy/Paste UVs sometimes merges vertices\nOperating system: Windows 10\nGraphics card:\n\nBroken: 3.5.1, 3.6.0 (2023-05-24), 4.0.0 (2023-05-24)\n\n\nCopy/Paste UVs sometimes merges vertices.\n\nTest file: [UV - Copy Paste.blend](attachment)\n\n\n\n", "Color picker samples merged (display output) colors on a certain object regardless of \"Sample Merged\" setting\nOperating system: Windows 10 v1909\nGraphics card: NVIDIA GeForce GTX 1660 super\n\nThe bug occured on the latest Steam release of Blender (2.90.1). I also tried to open the project file with the said bug in 2.83 LTS steam beta branch but it happened there too.\n\nWhen trying to texture paint a certain project it ignores the \"Sample Merged\" setting and always picks the display output color, while other objects don't share this problem. \nIt happens regardless of the material or texture I'm editing, it seems to be tied to a single object. For example, If I create a cube and assign the material which the bugged object uses color picking works fine with it, and if I assign any other material to the bugged object it still samples display output color regardless of the settings.\n\nI'm sadly not sure how to reproduce it. Though I appended the bugged object to a fresh file: [color_picker_thing.blend](color_picker_thing.blend)\nIt's system info:\n[system-info.txt](system-info.txt)\nI separated it so you wouldn't have to dig through the mess that is my main project file :D. It retained it's weird inabillity to pick colors though.\n\nI couldn't find a solution to this when I tried to google for it, so my only assumption left here is it being a bug. I'm sorry in advance if something I said isn't clear. If needed, I can provide a whole project or try and provide more specific information if what I wrote here isn't enough as soon as possible.\nCheers!", "Transfer data - vertex position by sampling UV\nAs we discussed on blender.chat, Blender would benefit from being able to transfer vertex positions from one object to another by sampling the UV's. Both the operator and the modifier\n\nHere is a mockup that might clarify what I mean\n\n\n\n", "Undo of operations on modifiers is inconsistent when object is in edit mode\nBroken: version: 2.79, 2.82 (sub 1), branch: master, commit date: 2019-11-22 18:14, hash: 373e936e3e\n\n\nwhen a modifier that has been **added in edit mode** to a object and is **deleted in edit mode,** it is not restored when using undo. \nThe operation shows up in the undo history but does nothing.\n\n\n1. go into edit mode\n2. add a modifier\n3. delete the modifier\n4. use undo, notice modifier is not restored.\n\ncreating the modifier in object mode or deleting it in object mode will restore it when using undo. this is a very confusion inconsistency that i noticed with the new undo method.\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)", "VSE: Transform settings doesn't get copied across scenes\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\nTransform settings doesn't get copied across scenes\n\nCopy a strip, which doesn't match the render resolution, across scenes:\n{[F10121941](copy_missing_transform.gif),size=full}\n\n", "Text strip duplication with madeup driver\nOperating system: Linux neo 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux\nGraphics card: nvidia GTX 970\n\nBroken:\n```\n3.0.0-alpha+master.a3027fb09416-linux.x86_64\n```\nWorked: (?)\n\nI duplicated a Text strip via <shift><D>. Then the clone had a driver on 'Location X' set, that the original has not. If You delete that driver, blender crasches (see #91912)\n\n\n- Load attached file\n- Duplicate the Text strip with <Shift><D>\nThe new Text strip now has a driver on Location X\n\n[driver_duplicate_bug.blend](driver_duplicate_bug.blend)", "UI: Linux & Mac Support for Clipboard Copy/Paste Images\nAs of the merge of #105833 Windows users can copy and paste images between Blender and other applications. That PR should have made it fairly easy to add similar support for other platforms.\n\nNot shown in #105833 (added later) is that each platform has a \"Capabilities\" flag that indicates that some optional features are supported. For Mac, for example, you can open up intern/ghost/intern/GHOST_SystemCocoa.mm. There is a getCapabilities() function and you can just remove `GHOST_kCapabilityClipboardImages` from that list of things not supported.\n\nThen you are going to declare a few functions in `GHOST_WindowCocoa.hh` and define them in `GHOST_WindowCocoa.mm`, using #105833 as a guide. `GHOST_hasClipboardImage` is meant to return true if the system clipboard contains a format that you are able to read and use. In the unlikely event that your platform does not provide this information you could just return true as that is only used to enable/disable the menu item.\n\n`putClipboardImage` gives you an array of bytes in RGBA order, and a width and height of the image buffer. The data will be without padding, so 4 X width X height of bytes (0-255 per channel). You just need to massage it into whatever format your platform wants and put it on the system clipboard. Returning true if you are able to do so.\n\nWith `getClipboardImage` you need to confirm that there is indeed an image available, get that image from the system clipboard. Set *r_width and *r_height to the dimensions of the image. Then return a pointer to the image data as an array of RGBA bytes without padding. Use 255 for Alpha if your image does not support it. The memory that you malloc for the buffer will be managed by the caller of the function.\n\nNote that the Windows implementation in `GHOST_SystemWin32.cc` is probably much more complicated that you will probably have to write. Windows has a long and strange history with clipboard formats and support for alpha. Implementations on other platforms could be extremely trivial in comparison.\n\n", "Save Copy - Does not maintain state of packed + edited images\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.93.4\nWorked: Never?\n\nWhen using the 'Save Copy' function (from File menu or via op: wm.save_as_mainfile(copy=True)), packed images that have not been individually saved since their last change do not have those changes maintained in the saved copy.\n\nCreate an image, set it to 'Packed', edit it in some way. Now use the 'Save Copy' function to create a copy of the blend file. Open the new copy and your edits to the packed file will be missing.\nWorkaround is to save all images before using the Save Copy function. However the current behavior is not intuitive and makes it easy to lose changes when creating backup copies of your working file.\nThere is also the case where you may want to have your current edits ONLY in the saved copy and not save them in the current mainfile, which currently is impossible to have happen. \n\n", "Tasks after BI removal\n* Code cleanup\n * Preview render code could be simplified, not used old preview.blend** Customdata mask handling still assumes old draw types\n * Move camera matrix code out of Render and into Freestyle, the only user\n * ~~Remove BLENDER_RENDER compat engine, find better system~~\n * Simplify GLSL shader coordinates, originally designed for camera space shading\n\n* Bigger tasks\n * #54696 (Blender Internal displacement baking move to Cycles)\n * [x] #54697 (Vertex color baking for Cycles)\n * #54656 (Cycles/Eevee texture nodes for modifiers, painting and more)" ]

[ "Impossible to copy/paste data between different Blender instances that are using different temp directories\n|Operating system:|Linux-5.8.16-2-MANJARO-x86_64-with-glibc2.2.5 64 Bits\n| -- | -- |\n||Windows 10\nGraphics card: AMD VERDE (DRM 2.50.0, 5.8.16-2-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.1.8\n\nBroken: version: 2.92.0 Alpha\nWorked: Never\n\nIt is not possible to copy/paste data between two Blender instances that use a different `Temporary Files` path.\n\n- Open two instances of Blender (regardless of whether they are the same version or different versions)\n- In the destination instance, delete all objects and set a custom path for Temporary Files (in Blender Preferences - File Paths)\n- In the other instance, Ctrl-C to copy default cube, \n- In the destination instance, Ctrl-V to paste,\nIt is not pasted, message \"no objects to paste\"\n\n" ]

[ "Geometry Nodes: Only re-evaluated log do update available attributes in drop-down menu\nBroken: version: 4.0.0 Alpha\n\nThis is a fairly insignificant UI bug. If the GeoNodes modifier is disabled, the list of available attributes to select in one of the inputs is not updated. For example, when a vertex group is renamed, that won't be reflected in the list, until the modifier is enabled again. Can result in a bit of confusion.\n\n1. Open attached file.\n2. Notice the GeoNode modifier is disabled.\n3. Rename the vertex group.\n4. Try assigning the renamed vertex group as the modifier's Factor input; You can't, because it won't appear in the list.\n5. Enabling the modifier updates the list again, and then all is well.\n\n", "Changing dimension on multiple objects no-longer works\nOperating system: Windows\n**working version:**\n2.79b\n**Last known *working* version:**\nblender-2.80.0 Beta (dec 2018)\nHash: e4dbfe0a98c1\nBransh blender2.7\n2.80.39\n**Earliest known *broken* version**\nblender-2.80.0 Beta (april 2019)\nHash: 480a09a92f7f\nBransh blender2.7\n2.80.60→2.83.2→2.90.0 Alpha\nManipulating the values in ‘`3d view`→`n-panel`→`dimensions:`' with ‘alt-key’ held down and dragging the mouse cursor will no-longer affect all the selected objects, only the parent.\n(feature still present for '`Location`', '`Rotation`', '`Scale`'.)\n\n1. Duplicate the default cube and move it so both cubes are visible.\n2. select both cubes and go to ‘`3d view`→`n-panel`→`Dimensions:`'\n3. With both cubes selected, hold down the alt-key and start manipulate the value by dragging your cursor in one of the three fields for 'Dimensions'\n\n**PS.** feature did not have the same affect as just scaling the objects, (see animated gif bellow)\n\n[dimbug.blend](dimbug.blend)\n", "Wrong status bar keymap for release confirms and right click select\nOperating system: Manjaro x64\nGraphics card: HD5770\n\nBroken:\n2.80, 81ea815dcb6, blender2.8, 2018-12-12\nWorked: 2.79b\n\nWhen grabbing something(object, vertex, etc) by right clicking on it and then releasing/clicking on the same button the action is not performed, object doesn't return to its initial position. \nHowever if you use G or a Tool to grab instead of mice click Cancel by Right clicking option works.\n\nRight click on a Cube(in 2.79 thats enough to start moving an object but not here here you have to hold the button) AND HOLD the button\nDrag mice somewhere to move the Cube\nRight Click again to Cancel movement\nNothing happens.\n[blender_bug-2018-12-13_22.18.53.mkv](blender_bug-2018-12-13_22.18.53.mkv)\nI'm also attaching video file for it to be more clear.", "NLA Strip influence slider doesn't respond to autokey correctly.\nOperating system: Win 10\nGraphics card: GeForce GTX 1070\n\n\nBroken: 2.82 Release\n\n\nThe Influence property of the NLA's strip, has some strange behavior and something that might be a bug.\nThis was reported before in #63865, which was supposedly resolved, but the problem still exists\n\nWhen changing the value of the influence slider with the autokey turned on, it jumps back to its previous value and does not update to the new one. After repeating it 2 or 3 times it applies the value. When applying the value numerically it works fine, it seems to be a problem with the update of the slider.\nMoreover, when turning influence on it always adds a keyframe to the first frame of the action (where the action is on the timeline ). It sets a keyframe with the value 0, instead of the current value.\n\n- Open attached file\n- Select one of the Action strips.\n- In the Sidebar, go to {nav Strip > Active Strip} and turn on `Animated Influence`. (Note that a keyframe is added to the first frame of the action).\n- Go to a new frame with the Autokey turned on, change the value of the influence slider.\n- Go to a new frame - the value should jump back to the previous one\n\nI've made a short video which describes the errors\nwatch?v=Sh5MwYCH9T4\n\nSample file:\n\n[Influence_bugreport.blend](Influence_bugreport.blend)", "\"Clean Keyframes\" in Dope Sheet only works if channels are selected\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 2.93.0 Alpha\nWorked: unknown\n\nThe \"Clean Keyframes\" and \"Clean Channels\" operators in the Dope Sheet editor only work if the channels containing the selected keyframes are also selected. This is unlike the \"Delete Keyframes\" operator, which works even if the channels are not selected.\n\n- Load the default startup scene.\n- Enable Auto Keying in the Timeline editor.\n- Move the cube up a bit.\n- Seek the playhead to another frame and move the cube up a bit more.\n- Switch to the Animation workspace.\n- In the Dope Sheet editor, click in an empty space of the keyframe region to deselect all keyframes and channels.\n- Expand the \"Object Transforms\" channel group and, with the mouse cursor in the keyframe region, press A to select all keyframes (but not the channels).\n- Press X and select \"Delete Keyframes.\" All keyframes and channels are deleted as expected. Press Ctrl-Z to revert.\n- Press X again, but this time select \"Clean Keyframes.\" Nothing happens despite there being plenty of keyframes to clean.\n- Move the mouse cursor to the channel region and press A to select all channels.\n- Move the mouse cursor back to the keyframe region and run \"Clean Keyframes\" again. This time, the cleanup works as expected.\n\nThe \"Clean Channels\" operator behaves in the same way.\n\nThe reason this only happens in the Dope Sheet editor and not the Graph Editor is likely that the Graph Editor automatically selects the channels for the selected keyframes, but the Dope Sheet editor does not. (It's not limited to \"Select All\", either; if you box-select keyframes from multiple channels, the same difference is observed.)\n\nSo rather than making \"Clean Keyframes\" and \"Clean Channels\" independent of channel selection, the real fix might be to automatically select the relevant channels in the Dope Sheet editor too.\n\nApart from this, it might make sense to move the \"Clean Channels\" operator to the \"Channel\" menu (and the \"X\" button of the channel region) and make it depend on channel selection *only* - that is, clean all keyframes of the selected channels, even if there are no keyframes selected. That way, there'd be some nice symmetry between the \"Channel\" and \"Key\" menus, both having their own \"Delete\" and \"Clean\" operators.", "Dragging the cursor (shift-right-click-drag) locks it's rotation\nOperating system: ~~Windows-10-10.0.22621-SP0 64 Bits~~ Windows 11 22H2\n> ***Meta Bug: this doesn't seem to recognize I'm on Windows 11.***Graphics card: NVIDIA RTX A2000 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\nBroken: version: 3.4.1\nWorked: /\n\nWhen setting the 3D cursor to project to surface and align its rotation to the geometry, it doesn't update when dragging. It only sets the aligned rotation on first click.\n\n1. Change Keybinding setting for shift right-click\n\n2. Add UV sphere\n3. Shift right-click-drag the 3D cursor over different face of the sphere\n4. Notice it only sets the rotation once initially\n\n", "VSE: Select more/less functionality breaks on certain conditions\nOperating system: Linux Mint 20\nGraphics card: NVIDIA G92 [GeForce 9800 GT]\n\nBroken: 2.93.1 / 2.92.0\nWorked: Unsure\n\nThe functions sequencer.select_more and sequencer.select_less get stuck when the newly selected strip reaches an edge, or when number of selected strips becomes zero.\n\n[blender-bug__select-more-less.mp4](blender-bug__select-more-less.mp4)\n\nThe attached video shows the functions [select_more]/[select_less] will break when the following conditions are met:\n```\n a) Any strip chain selection reaches the edge of the row of strips with [select_more]\n i) either when it starts from an edge and reaches the other edge\n ii) or when it starts in the middle and expands from both sides, the side of whichever edge is met will get stuck\n b) Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more]\n```\n\n\n\nI think it's unlikely this is intended behaviour?\n\nSorry I didn't get visual keypresses set up for the video, but I'm just using CTL- [x] and CTL- [x] on num pad as per default. \n\nDavid", "Select Interior Faces is not working\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA RTX A4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 4.0.0 Alpha\nWorked: \n\nthe operator \"select > select all by trait > interior faces\" is not working at all. Honestly I've never used this operator, so I'm not sure of how it should behave, but it doesn't do anything even with the simplest geometry. I tested it in 3.5 and 4.0 Alpha; I can't test it on other releases at the moment because of company installation restriction\n\nthe file attached is just a cube inside another cube in the same object\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", "3DConnexion Mouse not working in new Blender instance\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon VII OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.81 (sub 5)\nWorked: (optional)\n\n3dconnexion mouse works only in one instance of Blender\n\nIf I open 2nd instance of Blender 3d mouse does not work in it, only in the original file. This behaviour is same in official 2.8. I have tested this in Rhino for Mac. There Mouse works in both instances, which ever is active of course.\n", "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", "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", "Modifier re-evaluation makes editing dimensions unreliable\nCurrently editing dimensions uses the bounding box that's recalculated while dragging.\n\nThis can cause a feed-back loop as the objects scale is used by some modifiers which calculate a new bounding based on the scale which is then used in dimensions.\n\nIn the case of armature modifier - any zero scaled axis makes causes the mesh to scale into a single point, making any further changes to the dimensions not have any effect.\n\n----\n\nOriginal report:\n\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 74)\nWorked: Blender 2.79\n\n\nIf object is rigged scrolling its dimension value toward zero causes object to disappear, even if right mouse button has been clicked in order to cancel a scaling. So blender accepts a scale of zero even if left mouse button hasn't been released yet, Is it an expected behavior in Blender 2.8?\n\n\n\n\n - Select the cube.\n - Scroll any of its dimensions value toward zero without releasing the left mouse button\n - Cancel scrolling by right mouse button click.\n\n\n\n[Bug_report.blend](Bug_report.blend)\n\n", "Gesture selection does not deselect on nothing if collection is hidden\nOperating system: Linux-6.4.8-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.8-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-57b0db63e1)\n\nBroken: version: 4.0.0 Alpha\nWorked:\n\nThis is an inconsistency in the selection behavior.\nIf you select on nothing, it will deselect all objects in the viewport and the outliner. This is the case for click selection and selection tools/operators.\n\nBut if selected objects are hidden, they are not affected by this with selection tools (gesture selections such as box & lasso). Selected objects and collections stay selected in the outliner.\nThe expected behavior is that gesture selection and single click selection have the same effect on hidden objects and collections.\n\n1. Create two collections each with an object in it\n2. Select a collection and its object in the outlliner\n3. Select on empty space (Notice how the object and collection are deselected)\n4. Repeat 1 & 2\n5. Do a lasso/box selection on empty space (Notice how the outliner selection isn't cleared)\n\n", "Box Select Keyframes doesnt set an active keyframe\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Alpha\n\nWhen no keys are selected in the graph editor and you create a selection y box selecting no keyframe is set as active creating the dreaded issue of blender's having selection without active element to perform actions.\n\nopen the graph editor\ncreate several keyframe\ndeselect them all with a.\nselect with box select, none is active.\n\n**Expected solution**\n- When box selecting the keyframe that is closest to the mouse cursor (not the 2d cursor) should become the active one when box selecting, unless there is already an active keyframe in which case the active keyframe should remain.\n\n**Test builds for potential fix**\n\nThese builds not only fix the box/circle/lasso select by ensuring a keyframe is active, but also update the active FCurve so that the selection also contains the active FCurve.\n\n- [Windows](temp-#81874-box-select-active-keyframe-blender-2.91.0-87d654535c71-windows64.zip).\n- [Linux](temp-#81874-box-select-active-keyframe-blender-2.91.0-87d654535c71-linux64.tar.xz)\n" ]

[ "Circle Select Tool improvements\n## Issue\n\nThe current problem with the Circle Select Tool is that it is very inconvenient to change the brush size. In the modal operator equivalent (Shortcut C) it's just about pressing + and - or using the scrollwheel but this is not an option for the Tool. Generally there are no shortcuts for Tools before they are initiated. If the settings need to be changed then this needs to happen in the Tool Settings in the header or sidebar.\nBut changing the radius via that slider in the settings is awkward and appears visually glitchy since it's intersecting with the UI itself.\n\n\n\n## Proposals\n\nSo how can this be fixed. Ideally the solution should be as straight forward as possible without reshuffling the keymap. But it is very important that this is a general solution that can also be used for other brush-like Tools in the future (like proposed retopology tools that also rely on a brush radius)\n\n**1. More integrated modal shortcuts**\n\nOnce a Tool is initiated (usually by click & dragging) it uses the modal operator. This means that when using the Circle Select Tool and click & dragging, the radius can be changed with the mouse wheel & the + and - keys. \nThe current issue with this is that the Gizmo drawing is conflicting with the Tool Radius and that any changes to the radius are not updated in the tool settings.\nKeeping these 2 more in sync would be one solution or at least a great added feature.\n\n\n\nIt should be updated to the way the annotate eraser tool works but with more accessible shortcuts for radius changes if the mouse wheel is not an option (pen users)\n\n**2. Include Brush Tools in more modes**\n\nAnother solution is to redesign the Circle Select Tool (and any tools, present or future, that work similarly) as a brush like in sculpt mode or the painting modes.\nThis means that when the Tool is active it does have a set of shortcuts that can change the tool settings before the tool is initiated.\n\n**Conflicts**\n\nAlmost all are already taken like the typical F for brush size changes. It's not clear what shortcut can be used. \nAlso any shortcut that would be available must then be exclusively used for those brush tools to avoid any conflicts. \n\n**Solutions**\n\n1. Find or make an available shortcut for brush tools radius. But this shortcut then needs to be left exclusive of those tools.\n2. Override needed shortcuts when brush tool is used (In this case F for the radius). This does introduce difficulties and extra tool switching in edit mode though. \n3. Reuse the shortcut C that is used for the Circle Select Tool to change the radius once the tool is active. This will be awkward and incompatible with future tools that will work similar though.\n\n## Open Topics\n\n- Can it be achieved to use both solutions to improve brush like tools?\n- Are there possibly other ways of solving the conflicts in proposal 2?\n- For proposal 1, what shortcuts could be better for adjusting the brush size? + & - are on the numpad and the brackets are too far to the right and on for example German keyboard layouts not very accessible." ]

[ "GPencil: Canvas Overlay becomes inconsistent when both Object and Layer are transformed\nOperating system: Windows\nGraphics card:\n\nBroken: 3.4.1\nWorked: never?\n\nModifying Grease Pencil Layer transforms affects the Canvas overlay, but when both the Object and Layer have transforms the overlay does not describe the drawing plane actually being used by tools.\n\n- Open attached .blend\n- Draw new strokes into the Lines layer\n- Rotate the viewport to view the stroke placement.\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", "Display Workbench Textures On Curve Objects\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D500](D500) OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.24\n\nBroken: version: 2.82 (sub 6)\nSame on Windows version with same hash as well as in older versions of the 2.8x series.\n\nWorked: (optional)\nWorked in 2.7x Blender viewport ('Texture' mode)\n\nTextures don't display on curve extrusions in 'Solid' viewport shading mode even when UVs are assigned and 'Texture' is chosen as the object color. Instead, Curve extrusions simply stay gray.\nThese same textures show up fine on regular mesh objects in the same viewport. Also the curves display as intended in Material Preview and Rendered modes.\n\n\nIdeally open attached blend file to see the issue right away.\n\nAlternatively :\n1. Create a curve object and give it depth and UVs and apply a material\n2. Import a bitmap texture, attach to the curve's material and select it\n3. Switch to Solid shading mode and activate Texture as object color\n4. Compare look in Solid and Material Preview\n5. Repeat the above steps for a mesh object with UVs\n\n\n[textures_on_curves.blend.zip](textures_on_curves.blend.zip)", "Cannot set the Color attribute to display an object through Geometry Nodes\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 535.98\n\nBroken: version: 3.5.1\nWorked: version: 3.4.1\n\nbehavior changed in 6514bb05ea\n\nUsing the \"Store Named Attribute\" node setting the Attribute \"Col\" in geometry nodes, no longer sets the Vertexcolor of an object procedurally. When the Curve is converted to mesh and then the created \"Col\" Vertexcolor attribute is clicked, the colors show up.\n\nIn 3.4 and below this would override the vertexcolor attribute in \"realtime\" without converting the curve to mesh.\n\nOn a Curve Object, add a geometry node\n- create \"Store Named Attribute\"\n- set the \"Name\" to \"Col\"\n- change the color\n- Set the Viewport shading to color \"Attribute\" (seeattached Images) to view the result\n\nAttached file with example setup that used to overwrite the vertexcolor in 3.4.1, but no longer does in 3.5.1\n\n", "NaN pixels in Normal Pass\nOperating system: Linux-3.10.0-1127.10.1.el7.x86_64-x86_64-with-centos-7.8.2003-Core 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.83.0\nWorked: (Unknown)\n\nI produced a template based rendering solution and am experiencing occasion nan pixels in the normal pass output. Nan pixels are occurring in both CPU and GPU renders on a number of different hardware configurations.\n\nI've stripped down one of the files that exhibit the issue, see nan pixel at x162, y78 of normal pass.\nChanging visibility of the lights collection, specifically the 'LightArea', removes the pixel. Changing render resolution, sample seed, or adaptive sampling, can remove bad pixels.\nDisconnecting the normal map node on the geometry object's material removes the pixel. Providing input to that node, both textures and noise, has no effect on the pixel.\nChanging the transform on the rendered geometry removes the nan, regardless of whether the pixels occur on transparent background.\n\n[nan_pixel_isolated.blend](nan_pixel_isolated.blend)", "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)", "Architecture Texture Coordinates in Cycles\nHello dear Cycles team and developers :)\n\nI've been working in an archiviz project and stumbled upon a short come of Cycles: we don't have a straightforward way of setting world-based-dimensioned textures . This is a must for architecture, and I can give a few real-world use cases if requested.\n\nAs a Blender user I came up with a node system that can handle this. You can check my approach here: ?p=1198. Basically what this does it to take the Object texture coordinate and transform it based on the face normal (so we have an unstretched mapping for X, Y and Z).\n\nAs a Blender/Cycles developer I think we can do even better, and have this feature into master once we agree on the design and approach for the implementation.\n\nI wonder why this never came up before as an issue. As a side note, if you read the Expose 3D Blender migration post on BlenderNation () you will find that they consider the \"Lack of architectural UV mapping\" as the number one \"flaw\" of Cycles rendering.\n\nMy initial suggestion would be to have a Node where you could control (via socket input) the offset, scale and rotation of the texture. At first I would like to keep it simple and have offset to be a Vector(2), Scale to be a Vector(2), and Rotation to be a Float. In other words, I wouldn't bother with having per-axis nitty-gritty control. Also, the object size should NOT affect the texture size (unlike my original approach, or even the one from the \"Sure UVW mapping” addon used by the Expose 3D team). I'm not sure if this last bit is possible though.\n\nAny thoughts?", "The colors of the vertices do not correspond to the values in which I paint them with vertex paint.\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.92.0\n\nthe vertex color values that I get from the vertices in the shader editor node called \"vertex_color\" do not correspond to the values that I write there using vertex painting.\n\n\nSet the viewport mode to render or material preview. And change the inputs from the manual value to the value taken from vertex color. As you can see, the values themselves should not differ, but the color change.\n\n[vertex_color_error.blend](vertex_color_error.blend)\n\nPerhaps this is due to this issue D10956, but I want to say that we then need the ability to convert from one color space to another.\nBecause I use a blender to create game models and would like to use vertex colors to mix materials. But I can't, because it doesn't correspond to the colors and values that I enter. And it will not match what I will see in the game.\nIn addition, I enter specific values using the color wheel and sliders. And I expect to get them unchanged. That would be logical.\n", "Some circular shapes are rotated 90 degrees by default \nOperating system: windows 10\nGraphics card: GeForce RTX 2080ti\n\nBroken: 2.93.0 alpha\n\nAdding a mesh torus and geometry node circle primitive are rotated on z axis 90 degrees by default compared to other circular mesh and geometry node primitives. \ncreate a shape with 3 sides from torus, compare to shape with 3 sides made from cylinder, circle, UV sphere, cone. notice torus doesn't line up until rotated z 90 degrees.\ngeometry node, add primitive circle. join geometry with primitive cone, primitive cylinder, and primitive UV sphere. use the same value input for each primitive, increase the value from 3 to 12 and notice all primitives except the circle are uniformly changing. \n\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", "USDZ - Normal and Roughness maps imported as 'sRGB' instead 'Non Color'\nSystem Information\nOperating system: Windows 11\nGraphics card: RTX 3090\n\nBlender Version\nBroken: (3.60, 6daa3f6b8a)\nWorked: NA\n\nShort description of error\n\nWhen importing a sample USDZ file it imports correctly but has no Occlusion applied on the shader. When exporting back out to USDZ the Occlusion map is not included inside the USDZ anymore.\n\nWhen checking the original file (extract the usdz via a 7zip) it does have the AO texture inside the directory.\n\nExact steps for others to reproduce the error\n\n1) Download sample USDZ file from Apple: Rock.usdz\n2) Import USDZ into Blender\n3) Go to Shading Tab\n4) See the Normal Map Shader Color Space set to sRGB\n\n", "OBJ/MTL export: problems with map_d imfchan, d\nOperating system: Linux\nGraphics card:\n\nBroken: 3.2.0-alpha+master.bf80dc2bd4ac\n\nWhen exporting an alpha texture to OBJ/MTL, a wrong imfchan is written. Also a wrong d value may be written\n\nI'm using \"Wavefront OBJ (experimental)\" (but the old exporter is the same). Recall that MTL calls alpha \"dissolve\" and specifies it with a factor (d) and a texture (map_d) that are multiplied together. The MTL spec is .\n\n**Problem 1: wrong imfchan**\nUse a texture's Color for Base Color and its Alpha for Alpha.\n\n\n\n\n```\nExpected Actual\n-------- ------\nmap_d -imfchan m Tex.png d 1.000000\n map_d Tex.png\n```\n\nThe -imfchan option specifies \"the channel used to create a scalar or bump texture\", ie. it tells you how to make a scalar texture from a color texture. For example -imfchan r means to make a scalar by taking the red component. The expected MTL uses -imfchan m to take the alpha component (m=matte). The actual MTL omits imfchan and therefore uses the default which \"for bump and scalar textures is 'l' (luminance)\". This is what I'd expect from plugging the image's Color socket into the Alpha.\n\n**Problem 2: socket value being written when unused**\nIn the graph above, unplug the Alpha socket, change its default_value to 0.5, then change your mind and plug it back in. The graph is identical.\n\n```\nExpected Actual\n-------- ------\n(same as above) d 0.500000\n map_d Tex.png\n```\nIt seems the default_value is written as d. The actual MTL file incorrectly says the dissolve from the texture should be halved before being used.", "Very high or low values in the exponent parameter of the minkowski voronoi texture causes parts to become completely black\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 using the minkowski voronoi texture completely black spots appear when the input values are outside of a ~0.3,~40 range.\n\nTest file:\n[Test.blend](Test.blend)\n\nPlease open the shader editor to see all nodes.\n\nThank you and have a great day!\n\n", "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", "Incorrect twist in bevel/extrusion using curve tangent mode\n\n\n\nOperating system:\nGraphics card:\n\nBroken: present in 2.83.3, 2.91.0, and 3.0.0 alpha\nWorked: ?\n\n\nBoth open and closed curves exhibit a \"sausage effect\" when a bevel is applied. This is not visible when the curve is closed and 'ResolutionU' is below 4. The issue is somehow attenuated by applying large amounts of smoothing (twist_smooth).\nBelow is a flat and symmetric curve showing this issue.\n\n\n[blender_sausage_bug.mp4](blender_sausage_bug.mp4)\n\n\nDelete default cube. Create a Bèzier Circle. Enter Edit Mode, select all vertices, subdivide once.\nIn Object Data Properties, select Shape->Twist Method-> Tangent, and Geometry->Bevel->Depth: 0.2.\nToggle the Active Spline->Cyclic->U, and change the Active Spline->Resolution U between 4-5.\nYour smooth symmetric curve will turn into sausages!\n\nThe effect is slightly different depending on the type of handles.\n[sausage_bug.blend](sausage_bug.blend)" ]

[ "Baking normal errors when auto smooth enabled\nOperating system: Windows 10\nGraphics card: GTX 970\n\nBroken: 2.80.45, 6bab905c9d40, blender2.8, 2019-02-24,\n\n\nWhen I try bake normal for my simple object i have this weird edge issue. UV islands are separated and low poly has sharp edges marked. Also i notice that baked normal map is too intense. I think that in this case baking with auto smooth and flat shading should produce the same result, but somehow don't. Also when I change strength of the broken normal map in the material normal map node to 0.5 everything looks ok.\n\n\n\n\n\n[Box_Bake.blend](Box_Bake.blend)" ]

[ "File Browser unable to rename with Upper/Lower case\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.5\nversion 2.90.0 as well.\n\nWhen renaming a file/folder case changes are not taken into account.\n\nOn default startup : \nFile -> Save As -> New Folder -> Type \"TEst\" as name, click to release focus.\nRight Click -> Rename (or F2); Type \"Test\", click to release focus.\nThe name changes back to \"TEst\".\nWorkaround : \nRename to \"Test 2\", then back to \"Test\".\n\n\n\n", "Pressing Tab while renaming in UI List doesn't scroll past the end\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: v2.79b (`b5c3f26cba`) to v2.93.0 (`09c7c63890`)\n\nWhen navigating by TAB in a list (it's values/names inputs), the expected behaviour is go to next item, next ... until the last one\nBut on blender, if the list box don't fit'em all, so there's a scroll bar, when TABing out of the \"last visible\", instead of scroll to the list item, is gets out of list, as if that was the last item at all.\n\nIlustrative image:\n\nwvsIUlf.gif\n\nIt does the same on any list with scroll bars, but here's an example:\n\n- Open attached file or\n - Open Blender\n - go to compositor\n - place a *Output -> File Output* node\n - In the node properties, click on *\"+ add input\"* 5+ times, so a scroll bar show up in the list\n- Double click the first list item, to start renaming it\n- Try reach the last item, by pressing TAB on your keyboard 5+ times again\n**The Bug:** When in the item Image_004, pressing tab gets you to \"File Subpath\" input (out of the list), instead of Image_005\n[tab_item_navigat_bug.blend](tab_item_navigat_bug.blend)", "crash when alt+LMB to change custom properties of different bones\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Plus Graphics 655 Intel Inc. 4.1 INTEL-12.10.25\n\nBroken: version: 3.0.0 Alpha\nBroken version: 2.92\n\nWorked: 2.83.17 (`fb67495c7f`)\n\nI have two bones A and B, A has a custom property name 'a', B has none, in pose mode, select B and shift select A, press alt+LMB click and slide to change the custom property 'a', crash happens every time. If B has a custom property but with a different name, crash happens as well\n\nI know this operation doesn't make sense, you can't change a property that doesn't exist on some of the selected objects, but sometimes irrelevant bones are selected unintentionally, and crashes are annoying, if properties don't exist just do nothing\n\n- Open .blend file\n- Select Bone `A` and add a custom property\n- Select bone B then {key Shift LMB} to select bone A\n- Edit custom property value with {key Alt LMB drag}\n[#90732.blend](T90732.blend)", "Custom Properties Improved UI\nCurrent UI:\n\n\n\n- [ ] Allow reordering of custom properties in ways that make the most sense to an artist\n- [ ] Allow editing from the sidebar\n- [ ] Decrease the space between properties\n- [ ] Using an 'X' icon to delete\n- [ ] User and edit icon instead of \"Edit\"\n- [ ] Better location of icons\n- [ ] Group properties by the selected object/bone (see image)\n- [ ] Add a drop-down to select the data type\n- [ ] Allow the use of checkboxes to represent booleans\n\n", "Shader Image Mapping Issue\nOperating system: Mac OSX High Sierra\nGraphics card: NVIDiA GeForce\n\nBroken: (example: 2.92 Master 02948a2cab44\nWorked: N/A\n\nIt seems the mapped image is not applying to an object that's linked by Object Data\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n[repro2.blend](repro2.blend)\n\nIn this file, just going in and out of editmode causes the the (rendered) UVs to not be consistent (they appear fine in the UV Editor):\n\n\n\n\n\n\n---\nOriginal report:\n[modular.blend](modular.blend)\n\nLook at the image reference in the shader for the second to last vehicle. All other vehicles with similar bodies are linked and are following the map except the second to last object. After linking the body of that vehicle, the object appears to follow the map until you render the image. ", "Macro operators [e.g. Loop cut and slide]: \"adjust last operation\" fails completely [when called from the menu -- F9 is fine]\nBroken: 2.8x\nWorked: 2.79b\n\nThis might fall into the same boat as anything related to #45964, although it does seem to be \"new\" in 2.8x.\nAfter performing a loop cut and slide operator, you can adjust the properties in the operator panel (albeit with caveats from #45964). However, if you instead open the Adjust Last Operation panel, it will list a different operator name (Loop Cut, not Loop Cut and Slide), and while you can change properties there, those changes have no effect, even though they are reflected by the operator panel.\nThis didn't use to happen in 2.79b, though IIUC the \"Adjust...\" panel is different in 2.8x from the \"Redo Last\" of the 2.7x era.\n\n1. Load the default scene.\n2. Go into edit mode on the cube.\n3. Add a loop cut, e.g. via the shortcut or using the active tool\n4. Expand the operator panel in the bottom left and adjust properties. Note how those adjustments do have an effect on the result.\n5. Go Edit -> Adjust Last Operation\n6. Note the different operator name in that newly opened panel (Loop Cut vs. Loop Cut and Slide).\n6. Try adjusting any properties in the newly opened panel. Note how the operator panel in the bottom left picks up these changes, but at the same time they have no effect on the operation.\n\n[Demo video ](eAlL08M8AZA)", "Motion Paths not updating when working on the graph editor\nOperating system: Windows 10\nGraphics card: 1050 TI\n\nBroken: 3.5\nWorked: Supposedly never worked due to the way the code is set up.\n\n\nMoving the F-curve for key-framed object will not update motion paths.\n\n\n- Do some location key frames on the default cube.\n- Calculate the cube's motion path in the object properties tab.\n- Move the f-curve key frames on the default cube, motion path does not update.\n - Move the object directly, only the motion path of the current frame is updated.\n\n", "Image Sequence data disappears after certain properties are set\nOperating system:\nGraphics card:\n\nBroken: 2.83.6 (and all previous 2.8x versions)\n\n\nCannot access image sequence pixel data from 'Image Sequence' editor after certain properties are set.\n\nBased on the following startup file and bundled image sequence:\n\n\n1. Open the 'image_sequence_issue.blend' file from the following zip folder:\n[image_sequence_issue.zip](image_sequence_issue.zip)\n2. Run the active script in the text editor area\n3. Notice that an error is thrown - the image sequence has no data.\n4. Now comment out lines 8 & 9 (or line 12), and re-run the script. Notice that no error is thrown and the image has data.\n\nFor reference; the script bundled in the above file is copied below:\n\n```\nimport bpy\n\n# get the image editor space in the current screen\nviewer_area = next(area for area in bpy.context.screen.areas if area.type == \"IMAGE_EDITOR\")\nviewer_space = next(space for space in viewer_area.spaces if space.type == \"IMAGE_EDITOR\")\n\n# set properties on the image user\nviewer_space.image_user.frame_offset = 1\nviewer_space.image_user.use_cyclic = True\n\n# set the display channels to 'color'\nviewer_space.display_channels = \"COLOR\"\n\n# viewer_space.image.reload() # this line does not fix the issue\nprint(\"Before update:\", viewer_space.image.has_data)\nviewer_space.image.update()\nprint(\"After update: \", viewer_space.image.has_data)\n```", "Perstistant data causes point cloud objects to move\nOperating system: WIndows 10\nGraphics card: RTX 3070Ti\n\nBroken: Latest 3.4 Alpha of time of writing\nWorked: Tested back to 3.0 where the domain size node doesn't exist.\nCorrect location, no persistent data: \nRandom location, using persistent data \nA combination of animating the point cloud count and Persistent data causes the point cloud to move from its set location. \nBased on the default startup or an attached .blend file (as simple as possible).\nRender with and without persistant data.\n[Bug_test.blend](Bug_test.blend)", "Multi-User Action keeps moving object after deleting all keyframes until reloading file\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nDeleting keys from action with several users doesn't update correctly.\nActions without any keyframes keep changing the object until you revert the file.\n\n1. Add two keyframes to the default cube. (Scale it up and move it to the side)\n2. ALT+D to create a linked copy.\n3. On the linked copy, go to the dopesheet (e.g. action editor)\n4. Delete the keys. Because the action has two users, the keys should be deleted for all users.\n5. Play the animation. You'll see the original copy still moves according to the original keys.\n\n[#88208.blend](T88208.blend)\n\nThank you for taking a look at this! :)\nSeems like a bug to me.\n", "Treat object & object data the same for preview generation\nIt shouldn't matter if an object, or an object's data is marked as asset, the same preview should be generated. If the object data ID is passed, a wrapping object can be created if needed, so it's treated as object.", "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", "Snapping icon don't change when activating snap while moving object, vertex, edge, etc\nOperating system: Windows 10\nGraphics card: Geforce GTX 1080Ti\n\nBroken: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen\nBlender 2.91.0 Alpha b522e834ec30\nBlender 2.90.0 Beta bb5cc3bccf49\nWorked: Don't know!\n\nIf a move action is performed, and toggling snapping with Shift+Tab, no change on the snapping icon is present, confusing if the actual snapping is activated or not.\n\nNot a big thing, but has always botherd me. Don't seem to work on the alpha or beta builds either. Maybe just and overlooked or small enough thing? ", "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)", "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." ]

[ "NLA Editor RNA Path Bug\nWindows 7 64bit, Geforce 690 GTX \n\n2.69.0 r60995\n\nIn certain situations, RNA path names in f-curves\nare not updated when the animated RNA path was changed.\n\n - Open [NLA_Editor_Track_renaming_Bug.blend](NLA_Editor_Track_renaming_Bug.blend).\n - Change Name of Strip \"Animation\" to something else.\n # RNA Path of the \"Time\" strip is now broken.\nThe same thing happens when the strips are moved to\nanother track or the track-name is changed." ]

[ "Fix preview flickering when using \"Adjust Last Operation\"\nTweaking properties in the \"Adjust Last Operation\" panel removes all previews for a moment, causing quite drastic and annoying flickering.", "Modifiers added in edit mode are undone out of order if you go back to object mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 13)\nWorked: Never (2.8+)\n\nModifiers added in edit mode are undone out of order if you go back to object mode and then start undoing.\n\nAffects both old and new undo system. There's often mentions of edit<->object transitions being problematic but just in passing; I think this is a long standing issue. Just wanted to note it down as I test out the undo systems.\n\nHoping the new undo system can account for this now.\n\n- Default scene\n- Go to edit mode on the default cube\n- Add any modifier (bevel, subdivision, etc.)\n- Add any loop cut 1\n- Add another loop cut 2\n\n- Go to object mode\n- Undo --> Modifier is removed first (out of order)\n- Undo --> Loop cut 2 is removed\n- Undo --> Loop cut 1 is removed\n\n\n", "When \"Pie Menu on Drag\" is enabled in user prefs, Ctrl + Z has a tendency to open the shading menu by accident\nversion: 2.80 (sub 74), branch: master, commit date: 2019-07-05 21:52\nbuild date: 2019-07-06, 01:03:01\nplatform: Linux\n\nThis may be more of a design issue than a bug, but it's happened to me about 100 times now and it's quite irritating.\n\n**To reproduce:**\n\n - enable User Preferences > Keymap > Preferences > Pie Menu on Drag.\n - open a complex scene (one where the undo operator will have a significant lag) \n - fill the undo history with events, as though you've been working for a while\n - Press Ctrl + Z a couple times while moving the mouse a bit, rolling your hand so that Ctrl is released just before Z (in the manner of a busy artist)\n\nIf the user happens to release Ctrl earlier than Z while moving the mouse, this can bring up the shading menu, interrupting the user's workflow. This may sound like an edge case, but when working quickly, it's actually really frequent and annoying! It seems to especially effect large scenes where there is a lag in the effect of the undo operator.\n\nIdeally, the \"Pie On Drag\" feature should not listen for key presses if those key presses were part of a different combination that has yet to be completely released. What do you think?", "Multiple CNTRL Z replaces properties in driver\nWin7 64bit\n\nBroken: 2.79\n\nI was copying drivers from one object to another and hiding (H) those with already pasted driver. At some point I wanted to unhide previous object, so used undo instead of ALT H to bring back only one object. After object was revealed, I do not re-copy driver just paste what was already in memory. I make three undo's (just the step before copying driver), so I didn't expect this will corrupt driver's data. Would be better to make \"paste\" not happen, rather than changing it.\n\n*Original driver*\n\n*Pasted driver after some undo's*\n\n\n1. Copy driver from texture slot of left cube\n2. Hide left cube in viewport\n3. Paste driver in texture slot of right cube\n4. Pres CTRL Z three times until left cube will appear back\n5. Then repeat pasting driver from stage 3 -> driver's properties have been replaced by another\n[Paste_driver.blend](Paste_driver.blend)\n", "Disabled Selectability: it is still possible to enter other modes (The new Switch Objects operator, py API, ...) - should this be prevented?\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\n\nAfter trying the new Switch Objects operator in Sculpt Mode and Edit Mode, I noticed that the operator completely ignores if an object has Disable Selection active or not in the Outliner.\n[Desktop 2020.09.19 - 22.58.16.01.mp4](Desktop_2020.09.19_-_22.58.16.01.mp4)\n\n1. Have two separate objects in your scene. Go into Sculpt Mode or Edit Mode with one object.\n2. Use Disable Selection in the Outliner on the object you are not selecting in Sculpt Mode/Edit Mode.\n3. Click on the object that uses Disable Selection. You will be able to select it regardless.", "Outliner: Sync Selection off not working when clicking LMB on data object name\nBroken: version: 3.0.0\nBroken: version: 2.91.2 (works correctly on meshes for some reason till worked version)\nWorked: version: 2.82\n\nWhen `Sync Selection` is off it's still possible to sync selection by clicking on object data name (+ small margin). Additionaly clicking on object data name will sync it with relevant slot in Properties editor. This bugged area becomes slightly longer to the left when active, see video.\n\n1. Open default scene.\n2. Turn off `Sync Selection` on Outliner.\n3. Deselect onjects in your scene by clicking on empty space in 3D Viewport.\n4. Select objects or object data in outliner without clicking on their name - see that `Sync Selection` is off\n5. Select objects or object data in outliner by clicking in their name - see that now parent onject is selected in Outliner aswell as in 3D Viewport.\n[Outliner Sync Selection off bug 2021-12-15 20-45-35-213.mp4](Outliner_Sync_Selection_off_bug_2021-12-15_20-45-35-213.mp4)", "Double click list renaming not working on heavy scenes\nVista64, 2.7a, gtx470\nWhen the scene is heavy, so that interface becomes slightly laggy, double click list rename stops working, especially for fast clicking.\n\n - Add subdivision modifiers to any mesh until interface becomes laggy.\n - Add a vertex group or UV map.\n - Double click to rename - renaming is not activated.\n", "Avoid creating doubles in UV-Sphere primitive\nCurrently some new mesh operators are creating meshes with duplicate geometry, then removing it. This can cause problems - see: [D6001: Fix #70560: Large cones are created with double vertices (even though the radius is zero)](D6001).\n\n\nIt would be more elegant not to create duplicate geometry to begin with.\n\n- Committed fix for cone 5c8ccad652, while it still creates doubles, they are removed without relying on removing doubles.", "Edit mode has two different knife tools\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 516.59\n\nBroken: version: 3.2.0\n\nThe knife tool accessed through the button on the left side panel is different from the one accessed through the shortcut K, as the latter is not affected by settings.\n[1506-2326.mp4](1506-2326.mp4)\n\nChange the settings of the knife tool and notice they don't reflect when it's accessed through the shortcut.\n", "Non-keyboard shortcuts allowed to be set via context menu, but cannot be unset without going to user-preferences\nBroken: 2.79 or latest 2.80 (fa59346c13).\n\nAlthough I can easily (and often accidentally) assign non-keyboard shortcuts to menu items, I cannot easily undo it.\n\nFrom the viewport: View > Frame All [RMB] > Change Shortcut.\n\nAlthough the UI says \"Press a Key\", if you mouse click it (e.g., LBM) will register as the new shortcut.\nNow if you try to change the shortcut again it says it is a Non-Keyboard shortcut and cannot be changed.\n\nTooltip: *\"Only keyboard shortcuts can be changed that way (...)\"*", "Menus & Context Menus: What to do if operators aren't valid\nThis is a design doc to clarify how we should handle cases where operators aren't applicable. \n\nCurrently, we deal with this poorly:\n\n - In the context menus, we often show properties that won't work (such as when nothing is selected)\n - In regular menus, sometimes operators don't work in certain criteria, but it isn't communicated\n\nHere's how I think we should solve it:\n\n## Context menus\nRule: Only ever show operators here that actually work in the current context.\nThis means that, if nothing is selected, we should not show operators to act on the selection, since this will fail.\nIn general the context menus are always meant to show the user relevant items for the current situation, so this fits with that concept.\n\n**When nothing is selected**\nFor the case where nothing is selected, there often won't be very many applicable operators. In that case, we should add operators to add new items (objects, meshes, strips etc).\n\n## Regular menus\nThese we should keep constant, and not hide or show items, since it breaks muscle memory. Instead, we should use greying out. Preferably we should improve operator polling so that operators get greyed out when not applicable. When nothing is selected, or the wrong kind of item is selected, operatoers that don't do anything then should become greyed out.", "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", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "Multi-object-Mode: EditMode transform properties\nEdit-mode buttons currently only show median values for the active edit-object.\n\nThe Mean Crease value of the N panel doesn't work for multiple objects:\nHere i have 2 objects selected\n\nIn Edit Mode changing the Mean Crease value does change its effect only on the selected object:\n", "Move To Line Begin and Reset View operators in the console editor conflict when pressing Home key\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\n\nIn the python console editor, both the Move To Line Begin and the Reset View operators have the same shortcut \"Home\", so it is not possible to invoke the Move To Line Begin operator." ]

[ "Loop Cut preview not showing\nBroken: 2.80 \nWorked: all prior releases\n\nThe cut preview only shows the centre line of the cut, if the number of cuts has been increased then the preview used to show all the cuts.\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", "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", "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.", "Regression: Crash with boolean modifier\nOperating system: Fedora Linux 36 (Workstation Edition)\nGraphics card: Nvidia Geforce RTX 3080\n\nBroken: 3.2.1, 3.3 alpha\nWorked: 3.1\n\nCrash with boolean modifier\n\n- Open .blend file\n- In boolean modifier tab -> select `dot cutter` for boolean operation\n[yin_yang-v1.blend](yin_yang-v1.blend)\noriginal file: [F13292564](yin_yang.blend)", "Frequent render crashes in 3.5\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5500M 1.2\n\nBroken: version: 3.5.0\n\nI've been encountering a lot of crashes in 3.5 when rendering in the background. Meaning I start a rendering, and move over to something like a browser. At random time Blender 3.5 just crashes. I've included a crash log file.\n\n\n", "Debug information not generated upon crash.\nOperating system: Arch Linux 6.4.12-arch1-1\nGraphics card: AMD ATI Radeon 680M\n\nBroken: 3.6.2\nWorked: Could not determine (tried up to 3.5.1, which does not work without a full system downgrade)\n\nBlender crashes immediately upon launch.\n\nLaunching from the command line, I get this:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\nThe contents of /tmp/blender.crash.txt are this:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nPassing the --debug-all flag, I get no errors. I attached the output of this command as a text file.\n\nWhile Blender crashing on startup is not in and of itself an issue worthy of reporting, the lack of any debug information immediately makes the problem impossible to tackle independently. I have no idea what my next steps should be here.\n\nLaunch blender.\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", "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```", "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", "Blender is crashing instantly to the desktop randomly (solid viewport)\n\nOS: Windows 10 Pro 64bit (Version 21H2, OS Build 19044.2006)\nGPU: Nvidia GeForce RTX 2070 (Driver: Version 517.48 (released 27th September 2022))\nCPU: AMD Ryzen 7 2700\nRAM: 64GB\n\n\nBroken: version: 3.3 (and versions for the last couple of years)\nWorked: none since 2020 approx.\n\n\nBlender crashes seemingly randomly when performing modelling actions such as moving vertices, clicking sliders or buttons, switching to wireframe view, or moving the viewport camera in any way. There may be other actions that cause crashes. Crashes cause Blender to instantly close to desktop, leaving no crash dumps. Crashes occurring over multiple versions since 2020, multiple reinstallations of the OS, and clean reinstallations of graphics driver.\n\nUsing blender_debug_gpu.cmd, I was able to retrieve a log from a crash that has some differences to a normal log:\n\n\"*INFO (gpu.debug): Notification : Buffer usage warning: Analysis of buffer object 82 (bound to GL_SHADER_STORAGE_BUFFER (1)) usage indicates that the GPU is the primary producer and consumer of data for this buffer object. The usage hint supplied with this buffer object, GL_STATIC_DRAW, is inconsistent with this usage pattern. Try using GL_STREAM_COPY_ARB, GL_STATIC_COPY_ARB, or GL_DYNAMIC_COPY_ARB instead.*\"\n\nCurrently, have no way to reproduce the crashes at will, they just seem to happen during my normal work. Load tests using OCCT do not cause crashes.\n\n**Debug log from crash**:\n[blender_debug_output2.txt](blender_debug_output2.txt)\n\n**Normal debug log**:\n[blender_debug_output_normal.txt](blender_debug_output_normal.txt)", "Assertion Failure: Moving Keyframe in Graph Editor beyond enum range\nOperating system: Linux Mint Mate 19\nGraphics card: Nvidia GTX 850M\n\nBroken: master 2020-11-12 @ Merge branch 'blender-v2.91-release' only on debug builds 987732181f779ca792de933aa5f001168b1f6f26\nWorked: Anything that is not a debug build will not show any problems\n\nThis issue is split off from #44219 (Pose Breakdowner bug in Gooseberry rigs)\nMoving a keyframe of an enum in the graph editor allows it to go beyond the range of the enum. This causes an assert to fail\n\n\n\n* Open the file\n* Move the keyframe up\n* Blender crashed as soon as you exceed the enum range\n[enum_property_crash.blend](enum_property_crash.blend)", "Crash guide during render complete August 29, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.44\n\nBroken: version: 3.3.0 Beta\n\nBlender 3.3 Beta crash guide during render August 29, 2022\n\n\nNot matter all version 3.0 to 3.4 keep me crash. Do not use Windows. Only for Macintosh.\n\n\n\n[Blender-2022-08-29-092340.ips](Blender-2022-08-29-092340.ips)\n\n[Armor wear 1.0.0.blend](Armor_wear_1.0.0.blend)\n\n\n\nT100328\n@Nurb2Kea\nRender 600 (complete render cause crash guide)\n", "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", "Eevee crashes when rendering some of the Blender Studio rigs\nOperating system: Windows 10 Home\nGraphics card: Intel(R) HD Graphics 4600\n\nAlso tested on Debian 11 on both GNOME and MATE. It didn't make much of a difference, the GNOME session crashes and takes me back to the login manager meanwhile on MATE the program gets killed after it freezes for too long. I'd say that this is just a difference in the behaviour of the two desktop environments, but I can't say for sure.\n\nAlso asked a friend of mine to test it on their MacBook Pro, they claim to have seen the same results as I have. Just keep in mind that they're busy and I don't have access to their hardware.\n\nTried opening it on multiple versions:\n3.0.1 (stable), 3.5.1 (stable) and 4.0.0 (alpha) with [66d20c8723e6](66d20c8723e6) being the latest commit.\n\n(Windows/Linux/Mac)\nWhen opening it from the list of recent files I see the Blender project being displayed on the screen, but apparently for only one frame then freezes. I can see the prompt that asks for script execution to be enabled, the model itself, the pose library, etc. It just freezes afterwards.\nSame thing happens for when opening it via File -> Open, but I only see the default cube project before the crash.\nGot it from .\n\n1. Run Blender\n2. Open `ellie_animation.blend`\n\nSomething else worth noting is that apparently a group of people on the Blender Artists forums are experiencing the same issue: 1342795\n\n`blender-stdout.txt` and `blender-stderr.txt` were generated like so:\n`C:\\Users\\Mustafa\\blender-4.0.0-alpha+main.66d20c8723e6-windows.amd64-release>blender --factory-startup --debug-all > blender-stdout.txt 2> blender-stderr.txt`\nI've even provided a file (`gdb-blender.txt`) containing the output of interactively debugging blender with the GNU Debuger, in case you'll need it.\nAll debug logs and related files were created on Windows.\n\nThanks in advance! It'd take a miracle to get such a huge open source project going and you're doing a great job, I appreciate your hard work on Blender.\n", "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 2.8 Beta quits to desktop after full screen selection in Windows menu bar\nOperating system: OSX 10.14.3 Mojave\nGraphics card: Intel HD Graphics 4000 1536 MB\n\nBroken:\n2.80 Beta release (2.80 2019-03-01)\n\nquits to desktop after full screen selection in Windows menu bar without error\n\nStartup in default.\nSelecting full screen in Windows menu, Blender quits to Desktop without any error reporting\n\nBlender 2.80 OSX error report complete\n\nProcess: blender [1420]\nPath: /Volumes/VOLUME/*/blender.app/Contents/MacOS/blender\nIdentifier: org.blenderfoundation.blender\nVersion: 2.80 (2.80 2019-03-01, Blender Foundation)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: blender [1420]\nUser ID: 501\n\nDate/Time: 2019-03-02 11:02:28.058 +0100\nOS Version: Mac OS X 10.14.3 (18D109)\nReport Version: 12\nAnonymous UUID: C44F4FCB-29B1-4056-42AF-090ED13E299C\n\nSleep/Wake UUID: 8532D266-BF30-4B32-8393-787659FF71B7\n\nTime Awake Since Boot: 9900 seconds\nTime Since Wake: 1800 seconds\n\nSystem Integrity Protection: enabled\n\nNotes: Translocated Process\n\nCrashed Thread: 1\n\nException Type: EXC_CRASH (SIGSEGV)\nException Codes: 0x0000000000000000, 0x0000000000000000\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: blender [1420]\n\nThread 0:: Dispatch queue: com.apple.main-thread\n0 org.blenderfoundation.blender \t0x000000010f924c10 sig_handle_crash + 496\n1 libsystem_platform.dylib \t0x00007fff5acd2b3d _sigtramp + 29\n2 org.blenderfoundation.blender \t0x0000000110620a96 MEM_lockfree_callocN + 38\n3 org.blenderfoundation.blender \t0x000000010f92ba38 wm_event_do_handlers + 2728\n4 org.blenderfoundation.blender \t0x000000010f925600 WM_main + 32\n5 org.blenderfoundation.blender \t0x000000010f9213ef main + 927\n6 libdyld.dylib \t0x00007fff5aae7ed9 start + 1\n\nThread 1 Crashed:\n0 libsystem_kernel.dylib \t0x00007fff5ac247de __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff5acde593 _pthread_cond_wait + 724\n2 libc++.1.dylib \t0x00007fff581c4bda std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 org.blenderfoundation.blender \t0x00000001127ccca3 IlmThread_2_3::Semaphore::wait() + 147\n4 org.blenderfoundation.blender \t0x00000001127ca202 IlmThread_2_3::(anonymous namespace)::DefaultWorkerThread::run() + 66\n5 org.blenderfoundation.blender \t0x00000001127cc6f7 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_3::Thread::*)(), IlmThread_2_3::Thread*> >(void*) + 663\n6 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n7 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n8 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff5ac247de __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff5acde593 _pthread_cond_wait + 724\n2 libc++.1.dylib \t0x00007fff581c4bda std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 org.blenderfoundation.blender \t0x00000001127ccca3 IlmThread_2_3::Semaphore::wait() + 147\n4 org.blenderfoundation.blender \t0x00000001127ca202 IlmThread_2_3::(anonymous namespace)::DefaultWorkerThread::run() + 66\n5 org.blenderfoundation.blender \t0x00000001127cc6f7 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_3::Thread::*)(), IlmThread_2_3::Thread*> >(void*) + 663\n6 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n7 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n8 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff5ac247de __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff5acde593 _pthread_cond_wait + 724\n2 libc++.1.dylib \t0x00007fff581c4bda std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 org.blenderfoundation.blender \t0x00000001127ccca3 IlmThread_2_3::Semaphore::wait() + 147\n4 org.blenderfoundation.blender \t0x00000001127ca202 IlmThread_2_3::(anonymous namespace)::DefaultWorkerThread::run() + 66\n5 org.blenderfoundation.blender \t0x00000001127cc6f7 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_3::Thread::*)(), IlmThread_2_3::Thread*> >(void*) + 663\n6 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n7 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n8 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff5ac247de __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff5acde593 _pthread_cond_wait + 724\n2 libc++.1.dylib \t0x00007fff581c4bda std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 org.blenderfoundation.blender \t0x00000001127ccca3 IlmThread_2_3::Semaphore::wait() + 147\n4 org.blenderfoundation.blender \t0x00000001127ca202 IlmThread_2_3::(anonymous namespace)::DefaultWorkerThread::run() + 66\n5 org.blenderfoundation.blender \t0x00000001127cc6f7 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_3::Thread::*)(), IlmThread_2_3::Thread*> >(void*) + 663\n6 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n7 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n8 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 5:\n0 libsystem_kernel.dylib \t0x00007fff5ac247de __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff5acde593 _pthread_cond_wait + 724\n2 org.blenderfoundation.blender \t0x00000001104b06fc task_scheduler_thread_run + 124\n3 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n4 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n5 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff5ac247de __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff5acde593 _pthread_cond_wait + 724\n2 org.blenderfoundation.blender \t0x00000001104b06fc task_scheduler_thread_run + 124\n3 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n4 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n5 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 7:\n0 libsystem_kernel.dylib \t0x00007fff5ac247de __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff5acde593 _pthread_cond_wait + 724\n2 org.blenderfoundation.blender \t0x00000001104b06fc task_scheduler_thread_run + 124\n3 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n4 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n5 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 8:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff5ac2117a mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff5ac216d0 mach_msg + 60\n2 com.apple.CoreFoundation \t0x00007fff2d7fe158 __CFRunLoopServiceMachPort + 336\n3 com.apple.CoreFoundation \t0x00007fff2d7fd6a6 __CFRunLoopRun + 1661\n4 com.apple.CoreFoundation \t0x00007fff2d7fcdd6 CFRunLoopRunSpecific + 467\n5 com.apple.AppKit \t0x00007fff2ad49f89 _NSEventThread + 160\n6 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n7 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n8 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 9:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff5ac2117a mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff5ac216d0 mach_msg + 60\n2 com.apple.audio.CoreAudio \t0x00007fff2d24089a HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned int, unsigned int, mach_msg_header_t*, bool, unsigned int) + 124\n3 com.apple.audio.CoreAudio \t0x00007fff2d24080d HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 45\n4 com.apple.audio.CoreAudio \t0x00007fff2d23cb84 HALC_ProxyIOContext::IOWorkLoop() + 988\n5 com.apple.audio.CoreAudio \t0x00007fff2d23c5ee HALC_ProxyIOContext::IOThreadEntry(void*) + 128\n6 com.apple.audio.CoreAudio \t0x00007fff2d23c0d6 HALB_IOThread::Entry(void*) + 72\n7 libsystem_pthread.dylib \t0x00007fff5acdb305 _pthread_body + 126\n8 libsystem_pthread.dylib \t0x00007fff5acde26f _pthread_start + 70\n9 libsystem_pthread.dylib \t0x00007fff5acda415 thread_start + 13\n\nThread 10:: Dispatch queue: NSCGSDisableUpdates\n0 libsystem_kernel.dylib \t0x00007fff5ac2117a mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff5ac216d0 mach_msg + 60\n2 com.apple.SkyLight \t0x00007fff5398ebc5 CGSUpdateManager::enable_updates_common() + 577\n3 com.apple.SkyLight \t0x00007fff53931e3b CGSUpdateManager::enable_update(unsigned long long) + 317\n4 libdispatch.dylib \t0x00007fff5aa98d53 _dispatch_call_block_and_release + 12\n5 libdispatch.dylib \t0x00007fff5aa99dcf _dispatch_client_callout + 8\n6 libdispatch.dylib \t0x00007fff5aaa0124 _dispatch_lane_serial_drain + 618\n7 libdispatch.dylib \t0x00007fff5aaa0bdc _dispatch_lane_invoke + 388\n8 libdispatch.dylib \t0x00007fff5aaa9090 _dispatch_workloop_worker_thread + 603\n9 libsystem_pthread.dylib \t0x00007fff5acda60b _pthread_wqthread + 409\n10 libsystem_pthread.dylib \t0x00007fff5acda405 start_wqthread + 13\n\nThread 11:\n0 libsystem_pthread.dylib \t0x00007fff5acda3f8 start_wqthread + 0\n1 ??? \t0x0000000054485244 0 + 1414025796\n\nThread 12:\n0 libsystem_pthread.dylib \t0x00007fff5acda3f8 start_wqthread + 0\n1 ??? \t0x0000000054485244 0 + 1414025796\n\nThread 1 crashed with X86 Thread State (64-bit):\n```\nrax: 0x0000000000000004 rbx: 0x0000000000000002 rcx: 0x0000700007cab988 rdx: 0x0000000000000000\nrdi: 0x00007fc42ee01720 rsi: 0x0000000100000100 rbp: 0x0000700007caba10 rsp: 0x0000700007cab988\n r8: 0x0000000000000000 r9: 0x00000000000000a0 r10: 0x0000000000000000 r11: 0x0000000000000202\nr12: 0x00007fc42ee01720 r13: 0x0000000000000016 r14: 0x0000000100000100 r15: 0x0000700007cac000\nrip: 0x00007fff5ac247de rfl: 0x0000000000000203 cr2: 0x0000700007cabf78\n\n```\nLogical CPU: 0\nError Code: 0x02000131\nTrap Number: 133\n\n\nBinary Images:\n 0x10f7d7000 - 0x116893faf +org.blenderfoundation.blender (2.80 - 2.80 2019-03-01, Blender Foundation) <60B4E652-B820-3BC4-8080-71582EC31DF8> /var/folders/*/blender.app/Contents/MacOS/blender\n 0x119e5b000 - 0x119ebcff7 +libomp.dylib (0) <C32CE1B6-6F34-34E2-B9A3-7B8AD010CE68> /var/folders/*/blender.app/Contents/Resources/lib/libomp.dylib\n 0x11ac05000 - 0x11adaaff7 com.apple.audio.units.Components (1.14 - 1.14) <A7E7DE74-B219-308E-8177-7F1AC561DB93> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x11ae4d000 - 0x11ae51fff com.apple.audio.AppleHDAHALPlugIn (282.10 - 282.10) <8C1742CF-F0B3-3321-9918-F5237B84CF5A> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x11b439000 - 0x11b4b7a87 dyld (655.1) <3EBA447F-A546-366B-B302-8DC3B21A3E30> /usr/lib/dyld\n 0x11ec9d000 - 0x11eca0047 libobjc-trampolines.dylib (750.1) <1F602C29-B6EE-34B1-BB43-93A592C1F0BC> /usr/lib/libobjc-trampolines.dylib\n 0x11fa5e000 - 0x11fa5fff7 +_heapq.cpython-37m-darwin.so (0) <4E38D5FE-D41E-3D73-A691-D8EB68705BA1> /var/folders/*/blender.app/Contents/Resources/2.80/python/lib/python3.7/lib-dynload/_heapq.cpython-37m-darwin.so\n 0x121d41000 - 0x121d46ff7 +math.cpython-37m-darwin.so (0) <8E3040CF-1D6C-31F6-877B-1A1834678F7E> /var/folders/*/blender.app/Contents/Resources/2.80/python/lib/python3.7/lib-dynload/math.cpython-37m-darwin.so\n 0x7fff23461000 - 0x7fff237dafff com.apple.RawCamera.bundle (8.13.0 - 1031.3.2) <C1DB8AE5-1683-3AE8-ACDD-C5EBB3682EE8> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff25264000 - 0x7fff25785fff com.apple.driver.AppleIntelHD4000GraphicsGLDriver (12.4.7.2 - 12.0.4) <F7A9FEF4-9BAD-35AC-B4EC-8A4E3EE45FE5> /System/Library/Extensions/AppleIntelHD4000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD4000GraphicsGLDriver\n 0x7fff25786000 - 0x7fff25800fff com.apple.driver.AppleIntelHD4000GraphicsMTLDriver (12.4.7.2 - 12.0.4) <CA8D48F7-69DF-3186-BAED-AEF57D95B2BB> /System/Library/Extensions/AppleIntelHD4000GraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelHD4000GraphicsMTLDriver\n 0x7fff298f8000 - 0x7fff298f8fff com.apple.Accelerate (1.11 - Accelerate 1.11) <FC9BE0AB-2371-3ACB-9FD8-A1D439CC4C49> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff298f9000 - 0x7fff2990fff7 libCGInterfaces.dylib (506.19.1) <9E0F6B86-9E59-3EA9-A586-3A3BA7F2F08A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff29910000 - 0x7fff2a204fcf com.apple.vImage (8.1 - ???) <D6FBBB13-4760-3811-AF3E-F2B6626B70F6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff2a205000 - 0x7fff2a3b0fcf libBLAS.dylib (1243.200.4) <432DB967-86BB-3645-8838-CE91CBF51CFA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff2a3b1000 - 0x7fff2a3f6fff libBNNS.dylib (38.200.5) <FE0872E1-B992-369F-BD01-2EABBDD318F1> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff2a3f7000 - 0x7fff2a7b0fff libLAPACK.dylib (1243.200.4) <670B40E4-AE2F-3311-8ACC-E355F9A36769> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff2a7b1000 - 0x7fff2a7c6ffb libLinearAlgebra.dylib (1243.200.4) <4F53BB84-19EB-3B37-ADD7-553077851007> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff2a7c7000 - 0x7fff2a7ccff3 libQuadrature.dylib (3.200.2) <4FBCAC0A-81A4-3C53-8458-27F3569C809D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff2a7cd000 - 0x7fff2a84affb libSparse.dylib (79.200.5) <2D650C50-E87E-3F24-9BFA-C8EB6DE1A6E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff2a84b000 - 0x7fff2a85dffb libSparseBLAS.dylib (1243.200.4) <16E0C963-955E-3197-9EE0-256A61DB9D57> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff2a85e000 - 0x7fff2a9fcfdb libvDSP.dylib (671.220.1) <95AA3236-5D63-35AF-9305-FDC361365110> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff2a9fd000 - 0x7fff2ab74ff3 libvMisc.dylib (671.220.1) <6F0164E4-3812-3F1D-AEBC-AF3AFF207FB6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff2ab75000 - 0x7fff2ab75fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <0AB4E69A-8159-3BA5-984D-002B5ACB175C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff2ad26000 - 0x7fff2bb47ffb com.apple.AppKit (6.9 - 1671.20.108) <D460682F-1B60-372E-A8E5-58D7F3A1CB3A> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff2bb99000 - 0x7fff2bb99fff com.apple.ApplicationServices (50.1 - 50.1) <86D6F10E-21F8-3CDC-9838-EB07A1C54BA9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff2bb9a000 - 0x7fff2bc05ff7 com.apple.ApplicationServices.ATS (377 - 453.11) <4080F8BE-F2A2-3707-8754-436FBDB1DAF1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff2bc9e000 - 0x7fff2bdbdfff libFontParser.dylib (228.6) <BBCBEE2C-5B55-3278-B81D-22D72466753E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib\n 0x7fff2bdbe000 - 0x7fff2be09ff7 libFontRegistry.dylib (228.12.1.1) <B515718C-81BC-3705-A207-7215486C6D28> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff2be68000 - 0x7fff2be9bff7 libTrueTypeScaler.dylib (228.6) <760BF895-3D7A-36E2-B97C-6775C3615A1D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib\n 0x7fff2bf05000 - 0x7fff2bf09ff3 com.apple.ColorSyncLegacy (4.13.0 - 1) <4B1238CC-9B77-3AA5-8329-EE3C736F07EA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff2bfa6000 - 0x7fff2bff8ff3 com.apple.HIServices (1.22 - 627.14.2) <1F851BF9-AD29-3558-9EA5-AAD9BAAAC823> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff2bff9000 - 0x7fff2c007ff3 com.apple.LangAnalysis (1.7.0 - 1.7.0) <5654723A-7B3B-391F-B9F7-0DE4D5940185> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff2c008000 - 0x7fff2c054fff com.apple.print.framework.PrintCore (14.2 - 503.8) <F1246C9A-2216-3390-8DF1-89304F47CE5D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff2c055000 - 0x7fff2c090ff7 com.apple.QD (3.12 - 407.2) <F6B648DA-DA39-3EB4-B593-1B7E316661CD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff2c091000 - 0x7fff2c09dff7 com.apple.speech.synthesis.framework (8.1.0 - 8.1.0) <CF19C8B6-AAD5-3DCF-ABD0-3BABB44D119C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff2c09e000 - 0x7fff2c33bfff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <5D484151-F269-3D98-B507-0544A6B950AC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff2c33d000 - 0x7fff2c33dfff com.apple.audio.units.AudioUnit (1.14 - 1.14) <91100E0A-C14D-3E6C-B095-0C4109AC6694> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff2c6a1000 - 0x7fff2ca62fff com.apple.CFNetwork (976 - 976) <A434842F-305B-301D-8F88-373CA7BF7196> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff2ca77000 - 0x7fff2ca77fff com.apple.Carbon (158 - 158) <82E18DC5-6557-3A66-89A9-9FAD7B4E56DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff2ca78000 - 0x7fff2ca7bffb com.apple.CommonPanels (1.2.6 - 98) <775C94BE-EC00-315F-96E0-F0C1CD6EE3F4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff2ca7c000 - 0x7fff2cd83ff7 com.apple.HIToolbox (2.1.1 - 917.3) <8FEBBC30-9C36-3AD4-BC4C-AE3537E8943D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff2cd84000 - 0x7fff2cd87ffb com.apple.help (1.3.8 - 66) <0C6CC127-A860-30D2-8434-6CC3CAFFB030> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff2cd88000 - 0x7fff2cd8dff7 com.apple.ImageCapture (9.0 - 1530.1) <72ABBF32-531B-3B04-926D-E14B8D9003A8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff2cd8e000 - 0x7fff2ce22ff3 com.apple.ink.framework (10.9 - 225) <344AACCC-E997-3498-8B1D-2EFD3A889205> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff2ce23000 - 0x7fff2ce3dfff com.apple.openscripting (1.7 - 179) <A57FC4DB-4C51-3ABB-842F-9578991043E3> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff2ce5e000 - 0x7fff2ce5ffff com.apple.print.framework.Print (14.2 - 267.4) <618D290C-2EA0-3959-A2A8-FB7B61DA92DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff2ce60000 - 0x7fff2ce62ff7 com.apple.securityhi (9.0 - 55006) <2FE1EB07-F717-3E89-9662-8BA7C17C6AEC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff2ce63000 - 0x7fff2ce69ff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <F7E95C56-19E8-30A1-9594-84D4DD89F6D4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff2cf92000 - 0x7fff2cf92fff com.apple.Cocoa (6.11 - 23) <3F281295-3B16-359C-AE0C-5B4181DE1579> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff2cfa0000 - 0x7fff2d06cfff com.apple.ColorSync (4.13.0 - 3340) <2F45EB01-0C51-3D25-9836-18F99222E1C7> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff2d207000 - 0x7fff2d297fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <1E7EF105-B843-370D-884E-0A43E1A5800B> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff2d2fd000 - 0x7fff2d328ff7 com.apple.CoreBluetooth (1.0 - 1) <F041753E-7709-3FA4-ADA3-6B37296D92FB> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff2d329000 - 0x7fff2d6d7fff com.apple.CoreData (120 - 866.1) <FD7900C2-5A00-3560-9F37-6EED4DDFE873> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff2d6d8000 - 0x7fff2d7c1ff7 com.apple.CoreDisplay (101.3 - 106.2) <EE0D334B-8B71-3A70-9F90-677171D6762F> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff2d7c2000 - 0x7fff2dc10ff7 com.apple.CoreFoundation (6.9 - 1562) <DA75643F-6CF0-3FB1-B047-C142152E63B6> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff2dc12000 - 0x7fff2e2bcff7 com.apple.CoreGraphics (2.0 - 1249.2) <9F212010-3F68-33E7-AC96-716BD2BC90E4> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff2e2be000 - 0x7fff2e5e7fff com.apple.CoreImage (14.2.0 - 720.0.130) <B356BA95-EDD3-35D8-9E4B-250AF6C6DDF9> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff2e938000 - 0x7fff2ea39ff7 com.apple.CoreMedia (1.0 - 2285.4.4) <AC7E25F4-77B4-351E-974D-760F4F96FEDE> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff2ea9d000 - 0x7fff2ea9dfff com.apple.CoreServices (941 - 941) <6DBA4791-26DB-39FB-A6A3-5910A0F2EDD2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff2ea9e000 - 0x7fff2eb1cffb com.apple.AE (771 - 771) <4B009524-699E-3891-98DD-E3B6BB433C8F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff2eb1d000 - 0x7fff2edf5ff7 com.apple.CoreServices.CarbonCore (1178.16 - 1178.16) <17FC2B9E-EB6C-3768-A2D0-6E086F2563D9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff2edf6000 - 0x7fff2ee40ff7 com.apple.DictionaryServices (1.2 - 284.16.3) <1DAC9153-FB5A-3798-8797-CBFEFF227F71> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff2ee41000 - 0x7fff2ee49ffb com.apple.CoreServices.FSEvents (1239.200.12 - 1239.200.12) <8E1507EA-F0A8-3845-B32D-4FBC1381E89C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff2ee4a000 - 0x7fff2f015fff com.apple.LaunchServices (941 - 941) <A8E42760-995C-35E2-BF4A-C96FD0633B29> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff2f016000 - 0x7fff2f0b8fff com.apple.Metadata (10.7.0 - 1191.53) <48609998-8A34-3CAF-8A42-52C180809656> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff2f0b9000 - 0x7fff2f104ff7 com.apple.CoreServices.OSServices (941 - 941) <1B9EA259-09DF-332B-807A-BD50F3184CAC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff2f105000 - 0x7fff2f173ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <CEC29BB5-D28E-3424-84FE-70756E521F3B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff2f174000 - 0x7fff2f198ffb com.apple.coreservices.SharedFileList (71.27 - 71.27) <6389B59D-DDAC-3C97-A982-137B9B1FB734> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff2f4e0000 - 0x7fff2f645ffb com.apple.CoreText (352.0 - 584.26) <5F61037C-825D-37A4-9091-0047413CC213> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff2f646000 - 0x7fff2f683fff com.apple.CoreVideo (1.8 - 0.0) <34EC73F1-F0ED-32F5-B96E-7683B1F9A7A2> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff2f684000 - 0x7fff2f71affb com.apple.framework.CoreWLAN (13.0 - 1370.8) <32426190-3455-3049-8C09-0EC04D9C1279> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff2f997000 - 0x7fff2f99cfff com.apple.DiskArbitration (2.7 - 2.7) <97707A79-30E7-3D99-AA20-B992B0900BC4> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff2fb62000 - 0x7fff2fb64ff7 com.apple.ForceFeedback (1.0.6 - 1.0.6) <42A74696-FDA2-3F33-872A-A452D246B80C> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff2fb65000 - 0x7fff2ff33fff com.apple.Foundation (6.9 - 1562) <83D4A12B-EA5A-3C62-8D93-95E64F0A256B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff2ffa4000 - 0x7fff2ffd4ff3 com.apple.GSS (4.0 - 2.0) <86D07291-5DFC-30C2-9A18-5FCEDB0BE621> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff300ee000 - 0x7fff301f8ff3 com.apple.Bluetooth (6.0.10 - 6.0.10f1) <B3E7A841-1D1B-3043-A2C9-398928CB31AB> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff3025a000 - 0x7fff302edfff com.apple.framework.IOKit (2.0.2 - 1483.240.1) <241690BB-8AFA-3B6A-A210-67874197CB59> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff302ef000 - 0x7fff302f9ff7 com.apple.IOSurface (255.1 - 255.1) <58826B1A-38E8-3C76-8FFC-76C9282DA893> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff30350000 - 0x7fff304f1ff7 com.apple.ImageIO.framework (3.3.0 - 1822.1) <1451559D-4224-3F53-A976-16CF186DDE80> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff304f2000 - 0x7fff304f6ffb libGIF.dylib (1822.1) <9084A1A9-0AB3-314E-B76F-6642EAFD367A> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff304f7000 - 0x7fff305dcff7 libJP2.dylib (1822.1) <8138A169-983C-3ACF-B05C-81317D8A3792> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff305dd000 - 0x7fff30602ffb libJPEG.dylib (1822.1) <54E1BA95-B7C7-3078-921D-909B8EB33A84> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff308d6000 - 0x7fff308fcff3 libPng.dylib (1822.1) <5AFB0813-562F-3DB9-A4AD-A6FCABA63A2D> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff308fd000 - 0x7fff308ffff7 libRadiance.dylib (1822.1) <8CAA370A-A46C-3EA1-8338-F42AD183C19C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff30900000 - 0x7fff3094dffb libTIFF.dylib (1822.1) <4748924B-8F25-30A9-95BF-0A106E908B36> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff319f7000 - 0x7fff31a10fff com.apple.Kerberos (3.0 - 1) <5D1B0593-3C0E-32D5-AAE5-ABC22A98B639> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff31cce000 - 0x7fff31cd8fff com.apple.MediaAccessibility (1.0 - 114.4) <C0584BAA-27BC-30F4-8B0C-5043559995AA> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff31d92000 - 0x7fff32430fff com.apple.MediaToolbox (1.0 - 2285.4.4) <BAA7289A-FD04-30AD-B46E-89310BF67C02> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff32432000 - 0x7fff324c5fff com.apple.Metal (158.5 - 158.5) <72BF7187-81FE-389B-882F-7B2587FEB455> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff324e2000 - 0x7fff32502ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <18281B14-0C6A-38F8-AB80-2D4BB0743C88> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff32503000 - 0x7fff32581ff7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <BEAF764B-362B-3C45-86F5-2AFBA5FA0F47> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff32582000 - 0x7fff325aafff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <116D6C1A-2FD7-3743-95A0-CDDA3D459529> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff325ab000 - 0x7fff326ddff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <88E80BEE-3D2B-328B-80D4-F4717BDB2E9F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff326de000 - 0x7fff326f9ff7 com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <E0E652B0-1624-3435-AD60-83A9C4B59852> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff326fa000 - 0x7fff326faff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <1BBA8BC8-49C6-3C9B-B985-7CE4373E3553> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff338f8000 - 0x7fff33904ffb com.apple.NetFS (6.0 - 4.0) <918DF6CD-2DB0-36A8-B869-5EF637A06C0D> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff33c83000 - 0x7fff33ca8ff7 com.apple.audio.OpenAL (1.8 - 1.8) <A43E8D93-FBEE-3A59-A4E3-43B1FFC7BAC8> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff363bb000 - 0x7fff363c3fe7 libcldcpuengine.dylib (2.10.3) <D7BF3AFE-3E48-35FF-B674-6CA33B982D63> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff363c4000 - 0x7fff3641cfff com.apple.opencl (2.15.1 - 2.15.1) <CC9439C3-FF30-38D2-BF2F-EA0EF1B5775E> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff3641d000 - 0x7fff36439ff7 com.apple.CFOpenDirectory (10.14 - 207.200.4) <2CB1F122-2FA0-347C-8454-9CE0FA150832> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff3643a000 - 0x7fff36446ffb com.apple.OpenDirectory (10.14 - 207.200.4) <A3FB0F0C-57F4-3F89-A4B1-63DA1F7C9E8E> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff36da9000 - 0x7fff36dabfff libCVMSPluginSupport.dylib (17.3.1) <B2310175-04D6-378B-A220-A8AD7F0DA68E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff36dac000 - 0x7fff36db1ff3 libCoreFSCache.dylib (163.20) <566DB80E-F1D6-3AEC-AF06-08955507AFEE> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff36db2000 - 0x7fff36db6fff libCoreVMClient.dylib (163.20) <B9A89373-BDCD-3003-9A82-6D73B930A122> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff36db7000 - 0x7fff36dbfffb libGFXShared.dylib (17.3.1) <9FFA679A-8CC9-3932-8A41-AA80C386AD3A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff36dc0000 - 0x7fff36dcbfff libGL.dylib (17.3.1) <CFAB6AE4-E646-3E8A-B872-EF091CAF949E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff36dcc000 - 0x7fff36e06fef libGLImage.dylib (17.3.1) <1AEC8E56-[D851](D851)-3516-96FE-2829883A8302> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff36e07000 - 0x7fff36f79ff3 libGLProgrammability.dylib (17.3.1) <3B701B8D-FF2C-383E-8F94-77B052ECC075> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff36f7a000 - 0x7fff36fb7fff libGLU.dylib (17.3.1) <90279918-D4B2-31E0-9709-8E06628D9486> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff37967000 - 0x7fff37976ff3 com.apple.opengl (17.3.1 - 17.3.1) <2F59064F-D6EF-35CD-9747-20A91DB3D5DF> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff37977000 - 0x7fff37b0dff7 GLEngine (17.3.1) <2320D7E8-11EF-3667-8FC9-7EA5ABD6B8AD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff37b0e000 - 0x7fff37b36ff7 GLRendererFloat (17.3.1) <444BAB14-2648-3CD9-863F-695EA9206059> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff387d2000 - 0x7fff38a2bfff com.apple.QuartzCore (1.11 - 696.3) <01A2F065-8759-311D-AC2E-FD49F52A87FA> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff3927f000 - 0x7fff395a7ff7 com.apple.security (7.0 - 58286.240.4) <91A03FF2-2EE9-36A7-AC4F-169E11FE7846> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff395a8000 - 0x7fff39637fff com.apple.securityfoundation (6.0 - 55185.200.14) <F6A0EC77-51DB-3312-991C-3E1F920DE8F1> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff39669000 - 0x7fff3966dff3 com.apple.xpc.ServiceManagement (1.0 - 1) <26BA237C-DBA0-3322-B9BF-8B8E739E3A20> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff39a2a000 - 0x7fff39a9aff3 com.apple.SystemConfiguration (1.17 - 1.17) <A8FD596E-C858-397F-836C-978038B97AC0> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff39cfb000 - 0x7fff3a05dfff com.apple.VideoToolbox (1.0 - 2285.4.4) <76B3A88C-9042-329D-8DD7-56AEE23D1790> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff3cd08000 - 0x7fff3cdadfe7 com.apple.APFS (1.0 - 1) <BCB42C90-DEE0-3CD2-9B28-55CD8EFD9487> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff3d7f9000 - 0x7fff3d7faff3 com.apple.AggregateDictionary (1.0 - 1) <EBA6443E-6CF0-34F6-B77A-3FCEC57F8F80> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff3ddf7000 - 0x7fff3de23ff7 com.apple.framework.Apple80211 (13.0 - 1376.2) <A71EADCB-7582-3D1B-9122-356F03E11594> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff3e0ff000 - 0x7fff3e10efcf com.apple.AppleFSCompression (96.200.3 - 1.0) <78D538DD-1D24-34FC-AFB3-10411494870D> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff3e20c000 - 0x7fff3e217fff com.apple.AppleIDAuthSupport (1.0 - 1) <E41452B2-3AFB-3493-BB82-0CE6D04DF424> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff3e258000 - 0x7fff3e2a1ff3 com.apple.AppleJPEG (1.0 - 1) <EC4C49F1-C060-3C0F-910F-3620985D4F12> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff3e4f4000 - 0x7fff3e51cff7 com.apple.applesauce (1.0 - ???) <58654BC0-9243-39D1-BC43-B7F2E37A3A44> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff3e5e7000 - 0x7fff3e637fff com.apple.AppleVAFramework (5.0.44 - 5.0.44) <618AB3FC-6A41-3A84-A305-CEA19434EB1C> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff3e682000 - 0x7fff3e698ffb com.apple.AssertionServices (1.0 - 1) <3F767D20-FE14-35CF-A089-E0445375ECFB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff3e9d4000 - 0x7fff3ec77ff7 com.apple.AuthKit (1.0 - 1) <4FF8DA76-2250-39B9-B6A9-0E584C8B988F> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff3ee48000 - 0x7fff3ee51ff3 com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <05CF66F0-9650-3F75-9857-F8D186043866> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff3ee52000 - 0x7fff3eef4fff com.apple.backup.framework (1.10.3 - ???) <0B4C2292-AEA9-39B5-A65F-8F381166C5C2> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff3eef5000 - 0x7fff3ef66ffb com.apple.BaseBoard (360.24 - 360.24) <04AF4372-C5D3-3F0A-A688-68D888D6D138> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff40b1b000 - 0x7fff40b24fff com.apple.CommonAuth (4.0 - 2.0) <090893E5-BB65-39DA-A174-EAB2C7191EFE> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff40fe2000 - 0x7fff413b9fef com.apple.CoreAUC (273.0.0 - 273.0.0) <FE2B4D86-2C83-3FE2-A427-54DA2170E980> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff413ba000 - 0x7fff413ebfff com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <B15A24E4-2A92-3FD7-8F20-C372E4115FA7> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff41835000 - 0x7fff41849fff com.apple.CoreEmoji (1.0 - 69.19.8) <26BC0F82-08C1-3EBD-9299-D3CC5091C467> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff41e1f000 - 0x7fff41e91ff7 com.apple.CoreNLP (1.0 - 130.15.22) <D0A3E880-CDEA-360A-9838-220D76BAECC6> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff4215c000 - 0x7fff42164ffb com.apple.CorePhoneNumbers (1.0 - 1) <2D9AF545-ED3C-3EC1-887F-86922652EC57> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff422f3000 - 0x7fff42324fff com.apple.CoreServicesInternal (357 - 357) <789E57F4-5A14-3220-93DF-1D4FEE315431> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff426f9000 - 0x7fff42787ff7 com.apple.CoreSymbolication (10.1 - 64460.6) <177AC44B-32E4-3F80-A36B-5B9999B388A8> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff42817000 - 0x7fff42943fff com.apple.coreui (2.1 - 498.46) <5EFE2CDC-897C-3A6B-A60B-4E0FB1D1ECA9> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff42944000 - 0x7fff42ac9fff com.apple.CoreUtils (5.7.4 - 574.17) <DEF9C8A6-DDF1-37F4-A7F0-7DFAA95E8451> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff42b20000 - 0x7fff42b83ffb com.apple.framework.CoreWiFi (13.0 - 1370.8) <818F8915-BA51-3145-9C40-C9B8D7BE2DBD> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff42b84000 - 0x7fff42b95ffb com.apple.CrashReporterSupport (10.13 - 938.23) <D8D105F5-B6FB-3E91-A116-7CD92171E5C5> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff42c18000 - 0x7fff42c27ff3 com.apple.framework.DFRFoundation (1.0 - 211) <B72944ED-E4E8-3479-B832-8D50C4E30386> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff42c28000 - 0x7fff42c2cff7 com.apple.DSExternalDisplay (3.1 - 380) <76449D22-BA27-3FB1-AD25-A290936E6DEA> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff42caf000 - 0x7fff42d26ffb com.apple.datadetectorscore (7.0 - 590.24) <3A49EC90-2081-3031-8CAE-3A6D5F7BFA1E> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff42d74000 - 0x7fff42db5fff com.apple.DebugSymbols (185 - 185) <64F5F9D6-401D-388B-82AD-A48B56413556> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff42db6000 - 0x7fff42f0fff7 com.apple.desktopservices (1.13.1 - ???) <AD61A660-0218-327E-8963-A1A170EC2C20> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff43f51000 - 0x7fff44379fff com.apple.vision.FaceCore (3.3.4 - 3.3.4) <41218EB7-19C9-3813-A793-B0623387CADF> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff47c9b000 - 0x7fff47c9cfff libmetal_timestamp.dylib (902.2.2) <55E0B1F2-94F0-3A77-9DB3-152F44848DA5> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib\n 0x7fff4933a000 - 0x7fff49345ff7 libGPUSupportMercury.dylib (17.3.1) <CBF68814-AF66-3B8D-AF60-69469EA92E61> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff49346000 - 0x7fff4934bff7 com.apple.GPUWrangler (3.28.4 - 3.28.4) <7E06C75D-5502-3F1D-987C-4F103917CD85> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff4a1b6000 - 0x7fff4a1c5fff com.apple.GraphVisualizer (1.0 - 5) <CAFE626E-9738-3C14-88AA-B6A9182F2C39> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff4a316000 - 0x7fff4a38bfff com.apple.Heimdal (4.0 - 2.0) <D99FF31F-6310-3D80-8AE3-64934385AC11> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff4b77b000 - 0x7fff4b782ffb com.apple.IOAccelerator (404.2.2 - 404.2.2) <2F099589-DBE9-3442-AC93-F4AB363482A0> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff4b786000 - 0x7fff4b79ffff com.apple.IOPresentment (1.0 - 42.6) <F7E91CC9-E4BB-3904-8647-0473E3BCAF70> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff4bbb4000 - 0x7fff4bbe3ff7 com.apple.IconServices (379 - 379) <694E17A6-471B-3C57-92D6-ECC4295FB859> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff4be83000 - 0x7fff4be96fff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <DC6F5E18-3411-32AF-B395-AFC110C74A63> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff4beb2000 - 0x7fff4bfa9fff com.apple.LanguageModeling (1.0 - 159.15.15) <34609F31-4DA1-3881-8947-85BEA7AFC938> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff4bfaa000 - 0x7fff4bfebff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <07E008F3-E823-333B-8B41-A46024AB0561> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff4bff2000 - 0x7fff4bff8ff7 com.apple.LinguisticData (1.0 - 238.23.4) <F6AA7095-3975-3C76-9833-BBE955EFEBD7> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff4c857000 - 0x7fff4c85afff com.apple.Mangrove (1.0 - 25) <8DF73279-BCEB-38CE-AE83-571C1B3FF45B> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff4cd55000 - 0x7fff4cd7dffb com.apple.spotlight.metadata.utilities (1.0 - 1191.53) <2CFFD786-87A5-3629-B5E1-8E4DEF51ADA8> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff4cd7e000 - 0x7fff4ce10fff com.apple.gpusw.MetalTools (1.0 - 1) <C0489BBD-C25C-33E5-84CD-8A50205080A0> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff4ce25000 - 0x7fff4ce3efff com.apple.MobileAssets (1.0 - 437.230.2) <D962A68E-00AC-3C2F-BC09-0C16E77FE85E> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff4cfbb000 - 0x7fff4cfd6ff3 com.apple.MobileKeyBag (2.0 - 1.0) <663E513E-CE91-3474-9108-77DF844F17BA> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff4d064000 - 0x7fff4d08eff7 com.apple.MultitouchSupport.framework (2410.5 - 2410.5) <3A712911-F672-3BB3-B62B-A2A7BADF3578> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff4d301000 - 0x7fff4d30cfff com.apple.NetAuth (6.2 - 6.2) <A6474ABC-FD4B-3A8F-AB33-7AACEEED7F0E> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff4dbd9000 - 0x7fff4dc2ffff com.apple.OTSVG (1.0 - ???) <F020144A-[D840](D840)-390D-A87F-29E8095C78AF> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff4ed9a000 - 0x7fff4eda9ff3 com.apple.PerformanceAnalysis (1.217 - 217) <AA34989F-7E01-303E-8134-5BB37CE82DDF> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff50d68000 - 0x7fff50d86ff7 com.apple.ProtocolBuffer (1 - 263.1) <D70A1E3D-D2F7-3765-861C-173F5BBC848B> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff50f35000 - 0x7fff50f8df0f com.apple.ROCKit (24 - 24) <FA6B086A-1841-3A5E-800B-CE7A52C3DAF1> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit\n 0x7fff510b1000 - 0x7fff510d4ffb com.apple.RemoteViewServices (2.0 - 128) <55D89BC9-0613-3910-B63E-9A146D35D91A> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff52a4a000 - 0x7fff52b68fff com.apple.Sharing (1214.19 - 1214.19) <27C2CFC8-1C1B-3F98-B0BC-7AB6B1847B1B> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff53922000 - 0x7fff53bd4ff3 com.apple.SkyLight (1.600.0 - 337.5) <B18B2F6F-F44B-3B5B-8DA1-3B8977E59240> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff543a5000 - 0x7fff543b2fff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <FABB97BC-9555-33FE-B6C5-606CC403CE16> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff54a97000 - 0x7fff54ad6ff3 com.apple.StreamingZip (1.0 - 1) <251128E7-C343-3799-A31B-8B10CEC69F19> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff55213000 - 0x7fff552a0ff7 com.apple.Symbolication (10.1 - 64460.8) <7DDC5C90-947F-34FF-864D-5ED3C2B746A9> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff557a9000 - 0x7fff557b6ffb com.apple.TCC (1.0 - 1) <81F88B91-49C1-36E7-8A39-C4BD654EE942> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff55a29000 - 0x7fff55af0ff7 com.apple.TextureIO (3.8.4 - 3.8.1) <83CDF659-E5B3-381F-BDA1-FF0BFA17B5EE> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff55baa000 - 0x7fff55babfff com.apple.TrustEvaluationAgent (2.0 - 31.200.1) <5C3E1B2D-40A8-3237-A8D9-4E7B15EEA678> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff55bb1000 - 0x7fff55d6bfff com.apple.UIFoundation (1.0 - 551) <65A80450-7A24-3366-B521-4D02C4DB5094> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff56a5a000 - 0x7fff56b43ff7 com.apple.ViewBridge (401.1 - 401.1) <E76BC854-5B08-3FFF-AA2C-9679754FCAF0> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff57369000 - 0x7fff5736cfff com.apple.dt.XCTTargetBootstrap (1.0 - 1) <5F779D77-4AB1-3CCD-9AAF-101EC7E4905B> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff5779d000 - 0x7fff5779fff3 com.apple.loginsupport (1.0 - 1) <67BC49D6-320F-33ED-912E-16E5A342F385> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff577a0000 - 0x7fff577b5fff com.apple.login (3.0 - 3.0) <D6486C5A-E644-3F43-AD27-5E14685CD8D6> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff57a5a000 - 0x7fff57a92fff libCRFSuite.dylib (41.15.4) <92752A96-D1CF-3CA1-837A-1E075AE4C642> /usr/lib/libCRFSuite.dylib\n 0x7fff57a95000 - 0x7fff57aa0ff7 libChineseTokenizer.dylib (28.15.3) <55572692-4918-3C54-AD35-726E03EC47D5> /usr/lib/libChineseTokenizer.dylib\n 0x7fff57b31000 - 0x7fff57b32ff7 libDiagnosticMessagesClient.dylib (107) <15210AC0-61F9-3F9D-A159-A009F62EB537> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff57b69000 - 0x7fff57d2cff7 libFosl_dynamic.dylib (18.3.2) <D67B74E9-EB95-38BC-995C-5F4CC044C3F7> /usr/lib/libFosl_dynamic.dylib\n 0x7fff57d82000 - 0x7fff57da1ff7 libMobileGestalt.dylib (645.220.9) <C2C55511-993B-34D2-9040-902BFDA38141> /usr/lib/libMobileGestalt.dylib\n 0x7fff57da2000 - 0x7fff57da2fff libOpenScriptingUtil.dylib (179) <441A2E60-5D5C-3567-9B00-AA22E6EE5358> /usr/lib/libOpenScriptingUtil.dylib\n 0x7fff57ee3000 - 0x7fff57ee4ffb libSystem.B.dylib (1252.200.5) <C6201660-5E17-397D-BA21-C503420CD706> /usr/lib/libSystem.B.dylib\n 0x7fff57f6e000 - 0x7fff57f6ffff libThaiTokenizer.dylib (2.15.1) <F09EB0BB-1E8A-3391-BEF5-7D91F0715A62> /usr/lib/libThaiTokenizer.dylib\n 0x7fff57f82000 - 0x7fff57f98ffb libapple_nghttp2.dylib (1.24.1) <71C126C5-[D869](D869)-3E67-9778-058FA7F3CA74> /usr/lib/libapple_nghttp2.dylib\n 0x7fff57f99000 - 0x7fff57fc2ffb libarchive.2.dylib (54.200.3) <32B8634D-E465-3F6D-B254-A20D44504508> /usr/lib/libarchive.2.dylib\n 0x7fff57fc3000 - 0x7fff580c2ff7 libate.dylib (1.13.8) <6FF4C626-689E-3464-B2C5-C01F3C084219> /usr/lib/libate.dylib\n 0x7fff580c6000 - 0x7fff580c6ff3 libauto.dylib (187) <003DEF68-0C59-3AFB-A7B7-A1B5ED301AF2> /usr/lib/libauto.dylib\n 0x7fff5819d000 - 0x7fff581adff3 libbsm.0.dylib (39.200.18) <58A9ACEC-BF46-3A4E-86F5-3DD9AD7095B4> /usr/lib/libbsm.0.dylib\n 0x7fff581ae000 - 0x7fff581bcfff libbz2.1.0.dylib (38.200.3) <4DEC3797-087F-3C8D-815B-48E895813251> /usr/lib/libbz2.1.0.dylib\n 0x7fff581bd000 - 0x7fff58214ff7 libc++.1.dylib (400.9.4) <B260AC33-EB9A-30C6-8746-D011B3B02B08> /usr/lib/libc++.1.dylib\n 0x7fff58215000 - 0x7fff5822afff libc++abi.dylib (400.17) <446F4748-8A89-3D2E-AE1C-27EEBE93A8AB> /usr/lib/libc++abi.dylib\n 0x7fff5822b000 - 0x7fff5822bff3 libcharset.1.dylib (51.200.6) <43F7E100-F5D1-36AB-A26E-CF94196A19C0> /usr/lib/libcharset.1.dylib\n 0x7fff5822c000 - 0x7fff5823cffb libcmph.dylib (6.15.1) <CEDA6538-C071-3B5A-948E-DF61E2878983> /usr/lib/libcmph.dylib\n 0x7fff5823d000 - 0x7fff58255fdb libcompression.dylib (52.200.13) <6298529A-0120-3360-891C-84436972EA8D> /usr/lib/libcompression.dylib\n 0x7fff58500000 - 0x7fff58516fff libcoretls.dylib (155.220.1) <1229F9EA-C070-3D03-9DC6-F548C59F9FD5> /usr/lib/libcoretls.dylib\n 0x7fff58517000 - 0x7fff58518ff3 libcoretls_cfhelpers.dylib (155.220.1) <33661841-3C3B-3608-86AC-C88D1CD6FE98> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff586b7000 - 0x7fff58847ffb libcrypto.35.dylib (22.240.1) <603427B4-6A5E-367B-B164-744606A2AA27> /usr/lib/libcrypto.35.dylib\n 0x7fff58b8f000 - 0x7fff58be6ffb libcups.2.dylib (462.10) <29B6D106-A5F2-321D-8916-90F595545D88> /usr/lib/libcups.2.dylib\n 0x7fff58d1e000 - 0x7fff58d1efff libenergytrace.dylib (17.200.1) <F5BA8134-16F9-31CD-90E1-D1EBEBADA4AE> /usr/lib/libenergytrace.dylib\n 0x7fff58d50000 - 0x7fff58d55ff7 libgermantok.dylib (17.15.2) <9381B152-5CFD-3D23-A5A7-4D64EE55B85E> /usr/lib/libgermantok.dylib\n 0x7fff58d56000 - 0x7fff58d5bff7 libheimdal-asn1.dylib (520.220.2) <D851A47D-E162-35F8-B8D4-6ABEA7FFDAD7> /usr/lib/libheimdal-asn1.dylib\n 0x7fff58d87000 - 0x7fff58e78ff7 libiconv.2.dylib (51.200.6) <9FB95807-7C62-32B7-A19F-946D7FB7CCA6> /usr/lib/libiconv.2.dylib\n 0x7fff58e79000 - 0x7fff590dcffb libicucore.A.dylib (62109.0.1) <FEB89BD3-79C4-3208-A754-7E6BC4D38548> /usr/lib/libicucore.A.dylib\n 0x7fff59129000 - 0x7fff5912afff liblangid.dylib (128.15.1) <663D0A24-7260-31D1-9BFE-74D67B6F72F6> /usr/lib/liblangid.dylib\n 0x7fff5912b000 - 0x7fff59143fff liblzma.5.dylib (10.200.3) <9A52A949-0CB1-39B6-9244-D079FB609559> /usr/lib/liblzma.5.dylib\n 0x7fff5915b000 - 0x7fff5920bfff libmecab.1.0.0.dylib (779.24.1) <590BC39C-2A3E-368B-9499-C808B84C4955> /usr/lib/libmecab.1.0.0.dylib\n 0x7fff5920c000 - 0x7fff59449ff7 libmecabra.dylib (779.24.1) <22BFD5A8-EA42-3DC3-8910-F27DCFB1B631> /usr/lib/libmecabra.dylib\n 0x7fff59621000 - 0x7fff59979ffb libnetwork.dylib (1229.240.1) <F99593DA-3089-3008-BE5B-5AC096EBF3A3> /usr/lib/libnetwork.dylib\n 0x7fff59a0b000 - 0x7fff5a194fd7 libobjc.A.dylib (750.1) <4D6C889C-60F4-3028-9B13-DD3DFE6A2A44> /usr/lib/libobjc.A.dylib\n 0x7fff5a1a7000 - 0x7fff5a1abffb libpam.2.dylib (22.200.1) <85253002-89F2-3872-9C8A-1801303A2EBB> /usr/lib/libpam.2.dylib\n 0x7fff5a1ae000 - 0x7fff5a1e4ff7 libpcap.A.dylib (79.200.4) <6D25197A-2F7C-3147-A45A-F6F13E55909F> /usr/lib/libpcap.A.dylib\n 0x7fff5a2fe000 - 0x7fff5a316ffb libresolv.9.dylib (65.200.2) <A1A77B4E-1AF0-3039-9945-D05440494E00> /usr/lib/libresolv.9.dylib\n 0x7fff5a368000 - 0x7fff5a369ff7 libspindump.dylib (267.1) <9DEA015B-410E-3D6E-A3EE-54E046092EA9> /usr/lib/libspindump.dylib\n 0x7fff5a36a000 - 0x7fff5a536ff7 libsqlite3.dylib (274.22) <B33F9DBF-5947-31B4-A61C-EBB5326C6CD3> /usr/lib/libsqlite3.dylib\n 0x7fff5a7c3000 - 0x7fff5a7c6ffb libutil.dylib (51.200.4) <10C5E165-0939-363A-9D13-7076F3B513EC> /usr/lib/libutil.dylib\n 0x7fff5a7c7000 - 0x7fff5a7d4fff libxar.1.dylib (404) <16E875B3-CF89-3059-87BB-36D301B32E7B> /usr/lib/libxar.1.dylib\n 0x7fff5a7d9000 - 0x7fff5a8bcfff libxml2.2.dylib (32.8) <3E7875AC-3195-3800-AC48-8AA3B7BE51E4> /usr/lib/libxml2.2.dylib\n 0x7fff5a8bd000 - 0x7fff5a8e5ff3 libxslt.1.dylib (16.1) <D6EBFEBB-F88E-398F-B1B5-66F413C2CD32> /usr/lib/libxslt.1.dylib\n 0x7fff5a8e6000 - 0x7fff5a8f8ffb libz.1.dylib (70.200.4) <15F7B40A-424C-33BB-BF2C-7E8195128B78> /usr/lib/libz.1.dylib\n 0x7fff5a969000 - 0x7fff5a96dff3 libcache.dylib (81) <704331AC-E43D-343A-8C24-39201142AF27> /usr/lib/system/libcache.dylib\n 0x7fff5a96e000 - 0x7fff5a978ff3 libcommonCrypto.dylib (60118.220.1) <9C865644-EE9A-3662-AB77-7C8A5E561784> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff5a979000 - 0x7fff5a980fff libcompiler_rt.dylib (63.4) <817772E3-E836-3FFD-A39B-BDCD1C357221> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff5a981000 - 0x7fff5a98aff3 libcopyfile.dylib (146.200.3) <5C5C4F35-DAB7-3CF1-940F-F47192AB8289> /usr/lib/system/libcopyfile.dylib\n 0x7fff5a98b000 - 0x7fff5aa0ffdf libcorecrypto.dylib (602.230.1) <C78D1A87-5543-3561-BEB4-3B480BA94ECB> /usr/lib/system/libcorecrypto.dylib\n 0x7fff5aa96000 - 0x7fff5aad0ff7 libdispatch.dylib (1008.220.2) <2FDB1401-5119-3DF0-91F5-F4E105F00CD7> /usr/lib/system/libdispatch.dylib\n 0x7fff5aad1000 - 0x7fff5ab00ff3 libdyld.dylib (655.1) <90C801E7-5D05-37A8-810C-B58E8C53953A> /usr/lib/system/libdyld.dylib\n 0x7fff5ab01000 - 0x7fff5ab01ffb libkeymgr.dylib (30) <A4EFD9A4-2EF3-3E18-B325-F527E3821939> /usr/lib/system/libkeymgr.dylib\n 0x7fff5ab02000 - 0x7fff5ab0eff7 libkxld.dylib (4903.241.1) <D039B38D-E8E6-3011-94F5-A21CD3D59526> /usr/lib/system/libkxld.dylib\n 0x7fff5ab0f000 - 0x7fff5ab0fff7 liblaunch.dylib (1336.240.2) <D5F0014D-CF46-3B04-9DE0-A1466DA14A2C> /usr/lib/system/liblaunch.dylib\n 0x7fff5ab10000 - 0x7fff5ab15fff libmacho.dylib (921) <6ADB99F3-[D142](D142)-3A0A-B3CE-031354766ACC> /usr/lib/system/libmacho.dylib\n 0x7fff5ab16000 - 0x7fff5ab18ffb libquarantine.dylib (86.220.1) <58524FD7-63C5-38E0-9D90-845A79551C14> /usr/lib/system/libquarantine.dylib\n 0x7fff5ab19000 - 0x7fff5ab1aff3 libremovefile.dylib (45.200.2) <BA53CA8A-9974-3A43-9265-B110B1AE470F> /usr/lib/system/libremovefile.dylib\n 0x7fff5ab1b000 - 0x7fff5ab32ff3 libsystem_asl.dylib (356.200.4) <33C62769-1242-3BC1-9459-13CBCDECC7FE> /usr/lib/system/libsystem_asl.dylib\n 0x7fff5ab33000 - 0x7fff5ab33fff libsystem_blocks.dylib (73) <152EDADF-7D94-35F2-89B7-E66DCD945BBA> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff5ab34000 - 0x7fff5abbcfff libsystem_c.dylib (1272.200.26) <D6C701A2-9F17-308D-B6AC-9E17EF31B7DF> /usr/lib/system/libsystem_c.dylib\n 0x7fff5abbd000 - 0x7fff5abc0ff7 libsystem_configuration.dylib (963.200.27) <94898525-ECC8-3CC9-B312-CBEAAC305E32> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff5abc1000 - 0x7fff5abc4ff7 libsystem_coreservices.dylib (66) <10818C17-70E1-328E-A3E3-C3EB81AEC590> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff5abc5000 - 0x7fff5abcbffb libsystem_darwin.dylib (1272.200.26) <07468CF7-982F-37C4-83D0-D5E602A683AA> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff5abcc000 - 0x7fff5abd2ff7 libsystem_dnssd.dylib (878.240.1) <5FEA5E1E-E80F-3616-AD33-8E936D61F31A> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff5abd3000 - 0x7fff5ac1fff3 libsystem_info.dylib (517.200.9) <54B65F21-2E93-3579-9B72-6637A03245D9> /usr/lib/system/libsystem_info.dylib\n 0x7fff5ac20000 - 0x7fff5ac48ff7 libsystem_kernel.dylib (4903.241.1) <CA10BC3A-5B09-32CE-B74F-BAD01755AA37> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff5ac49000 - 0x7fff5ac94ff7 libsystem_m.dylib (3158.200.7) <AF25F8E8-194C-314F-A2D3-A424853EE796> /usr/lib/system/libsystem_m.dylib\n 0x7fff5ac95000 - 0x7fff5acb9ff7 libsystem_malloc.dylib (166.220.1) <4777DC06-F9C6-356E-82AB-86A1C6D62F3A> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff5acba000 - 0x7fff5acc5ff3 libsystem_networkextension.dylib (767.240.1) <4DB0D4A2-83E7-3638-AAA0-39CECD5C25F8> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff5acc6000 - 0x7fff5accdfff libsystem_notify.dylib (172.200.21) <65B3061D-41D7-3485-B217-A861E05AD50B> /usr/lib/system/libsystem_notify.dylib\n 0x7fff5acce000 - 0x7fff5acd7fef libsystem_platform.dylib (177.200.16) <83DED753-51EC-3B8C-A98D-883A5184086B> /usr/lib/system/libsystem_platform.dylib\n 0x7fff5acd8000 - 0x7fff5ace2fff libsystem_pthread.dylib (330.230.1) <80CC5992-823E-327E-BB6E-9D4568B84161> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff5ace3000 - 0x7fff5ace6ff7 libsystem_sandbox.dylib (851.230.3) <D6469A17-C13C-3538-A300-D6517BB7F249> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff5ace7000 - 0x7fff5ace9ff3 libsystem_secinit.dylib (30.220.1) <5964B6D2-19D4-3CF9-BDBC-4EB1D42348F1> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff5acea000 - 0x7fff5acf1ff7 libsystem_symptoms.dylib (820.237.2) <487E1794-4C6E-3B1B-9C55-95B1A5FF9B90> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff5acf2000 - 0x7fff5ad07ff7 libsystem_trace.dylib (906.220.1) <4D4BA88A-FA32-379D-8860-33838723B35F> /usr/lib/system/libsystem_trace.dylib\n 0x7fff5ad09000 - 0x7fff5ad0effb libunwind.dylib (35.4) <EF1A77FD-A86B-39F5-ABEA-6100AB23583A> /usr/lib/system/libunwind.dylib\n 0x7fff5ad0f000 - 0x7fff5ad3ffff libxpc.dylib (1336.240.2) <EE0CDA53-6FF9-3B4E-A571-335A5FF6B6F4> /usr/lib/system/libxpc.dylib\n\nExternal Modification Summary:\n```\nCalls made by other processes targeting this process:\n task_for_pid: 2\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: 5040\n thread_create: 0\n thread_set_state: 0\n```\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=541.0M resident=0K(0%) swapped_out_or_unallocated=541.0M(100%)\nWritable regions: Total=690.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=690.8M(100%)\n \n```\n VIRTUAL REGION \n```\nREGION TYPE SIZE COUNT (non-coalesced) \n**=======**\nAccelerate framework 256K 2 \nActivity Tracing 256K 2 \nCG backing stores 224K 3 \nCG image 56K 8 \nCoreAnimation 64K 10 \nCoreGraphics 8K 2 \nCoreImage 8K 3 \nCoreUI image data 288K 8 \nCoreUI image file 404K 4 \nFoundation 4K 2 \nKernel Alloc Once 8K 2 \nMALLOC 266.8M 95 \nMALLOC guard page 32K 9 \nMALLOC_LARGE (reserved) 384K 3 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 2 reserved VM address space (unallocated)\nMemory Tag 242 12K 2 \nMemory Tag 249 156K 2 \nOpenGL GLSL 256K 4 \nSTACK GUARD 56.0M 14 \nStack 14.1M 15 \nVM_ALLOCATE 23.8M 83 \nVM_ALLOCATE (reserved) 36K 2 reserved VM address space (unallocated)\n__DATA 53.4M 263 \n__FONT_DATA 4K 2 \n__GLSLBUILTINS 5176K 2 \n__LINKEDIT 244.1M 10 \n__TEXT 296.9M 266 \n__UNICODE 564K 2 \nmapped file 51.2M 14 \nshared memory 672K 11 \n**=======**\nTOTAL 1.4G 817 \nTOTAL, minus reserved VM space 1.0G 817 \n\nModel: MacBookPro9,2, BootROM 222.0.0.0.0, 2 processors, Intel Core i7, 2,9 GHz, 8 GB, SMC 2.2f44\nGraphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In\nMemory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020\nMemory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.21.190.32 AirPortDriverBrcm4360-1315.1)\nBluetooth: Version 6.0.10f1, 3 services, 27 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en1\nSerial ATA Device: ST500LM030-2E717D, 500,11 GB\nSerial ATA Device: MATSHITADVD-R UJ-8A8\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 Bus\nUSB Device: Hub\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: USB 3.0 Bus\nUSB Device: USB Optical Mouse\nThunderbolt Bus: MacBook Pro, Apple Inc., 25.1\n\n\n", "Maximise Window crashes 2.80\n\n\nMacBook Pro (part of Apple crash report follows: )\n\nProcess: blender [9210]\nPath: /Applications/blender.app/Contents/MacOS/blender\nIdentifier: blender\nVersion: 2.80 (2.80 2019-02-24, Blender Foundation)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: blender [9210]\nUser ID: 501\n\nDate/Time: 2019-03-02 20:55:36.914 +0000\nOS Version: Mac OS X 10.13.6 (17G5019)\nReport Version: 12\nAnonymous UUID: 017A1F48-DA38-CF81-4606-96CFE86854DE\n\nSleep/Wake UUID: A87BDB54-656A-4A22-943D-F2C9479CC722\n\nTime Awake Since Boot: 74000 seconds\nTime Since Wake: 4700 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 1\n\nException Type: EXC_CRASH (SIGSEGV)\nException Codes: 0x0000000000000000, 0x0000000000000000\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: blender [9210]\n\nThread 0:: Dispatch queue: com.apple.main-thread\n0 org.blenderfoundation.blender \t0x0000000101cd4643 MEM_lockfree_freeN + 19\n1 org.blenderfoundation.blender \t0x0000000100fe438d wm_event_do_handlers + 2781\n2 org.blenderfoundation.blender \t0x0000000100fddf20 WM_main + 32\n3 org.blenderfoundation.blender \t0x0000000100fd9d0f main + 927\n4 libdyld.dylib \t0x00007fff66955015 start + 1\n\nThread 1 Crashed:\n0 libsystem_kernel.dylib \t0x00007fff66aa5a16 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff66c6e589 _pthread_cond_wait + 732\n2 libc++.1.dylib \t0x00007fff648accb0 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 org.blenderfoundation.blender \t0x0000000103e81db3 IlmThread_2_3::Semaphore::wait() + 147\n4 org.blenderfoundation.blender \t0x0000000103e7f312 IlmThread_2_3::(anonymous namespace)::DefaultWorkerThread::run() + 66\n5 org.blenderfoundation.blender \t0x0000000103e81807 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_3::Thread::*)(), IlmThread_2_3::Thread*> >(void*) + 663\n6 libsystem_pthread.dylib \t0x00007fff66c6d661 _pthread_body + 340\n7 libsystem_pthread.dylib \t0x00007fff66c6d50d _pthread_start + 377\n8 libsystem_pthread.dylib \t0x00007fff66c6cbf9 thread_start + 13\n<snip>\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=485.7M resident=0K(0%) swapped_out_or_unallocated=485.7M(100%)\nWritable regions: Total=528.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=528.9M(100%)\n \n```\n VIRTUAL REGION \n```\nREGION TYPE SIZE COUNT (non-coalesced) \n**=======**\nAccelerate framework 128K 2 \nActivity Tracing 256K 2 \nCG backing stores 4112K 4 \nCG image 52K 10 \nCoreAnimation 52K 10 \nCoreGraphics 8K 2 \nCoreImage 8K 3 \nCoreUI image data 836K 11 \nCoreUI image file 180K 3 \nFoundation 4K 2 \nKernel Alloc Once 8K 2 \nMALLOC 426.8M 144 \nMALLOC guard page 48K 12 \nMemory Tag 242 12K 2 \nMemory Tag 249 156K 2 \nOpenGL GLSL 512K 7 \nSTACK GUARD 56.0M 14 \nStack 14.1M 18 \nVM_ALLOCATE 71.7M 101 \nVM_ALLOCATE (reserved) 36K 2 reserved VM address space (unallocated)\n__DATA 48.6M 244 \n__FONT_DATA 4K 2 \n__GLSLBUILTINS 2588K 2 \n__LINKEDIT 222.7M 10 \n__TEXT 263.0M 245 \n__UNICODE 560K 2 \nmapped file 45.4M 15 \nshared memory 828K 15 \n**=======**\nTOTAL 1.1G 860 \nTOTAL, minus reserved VM space 1.1G 860 \n\nModel: MacBookPro8,1, BootROM 82.0.0.0.0, 2 processors, Intel Core i5, 2.3 GHz, 4 GB, SMC 1.68f99\nGraphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In\nMemory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020\nMemory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.102.30)\nBluetooth: Version 6.0.7f12, 3 services, 27 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en1\nSerial ATA Device: Hitachi HTS545032B9A302, 320.07 GB\nSerial ATA Device: MATSHITADVD-R UJ-8A8\nUSB Device: USB 2.0 Bus\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: Hub\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: BRCM2070 Hub\nUSB Device: Bluetooth USB Host Controller\nUSB Device: USB 2.0 Bus\nUSB Device: Hub\nUSB Device: Trust Wireless Mouse\nUSB Device: IR Receiver\nThunderbolt Bus: MacBook Pro, Apple Inc., 22.1\n\n2.80 \n2.80 (2.80 2019-02-24, Blender Foundation)\n\nProgram crash and exit\nOccurred In default startup state, immediately on clicking top ‘WINDOW’ menu option ’Toggle Maximise Current Window’.\nRepeatable. \n\n", "on OSX \"Toggle Window Fullscreen\" crashes the Blender 2.8b\nOperating system: OSX High Sierra\nGraphics card: Radeon Pro 560 4096 MB / Intel HD Graphics 630 1536 MB\n\nBroken: Version 2.80 2019-02-05\nWorked: (optional)\n\nWhen using Window -> \"Toggle Window Fullscreen\", Blender crashes\n\n\nOn OSX High Sierra, with any scene, go to Window -> \"Toggle Window Fullscreen\" - this should crash the Blender." ]

[ "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)", "Cycles GPU render white pixel when rendering monster image\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon PRO W6800 ATI Technologies Inc. 4.5.14802 Core Profile Context FireGL 21.Q4 30.0.14002.136\n\nBroken: version: 3.0.0 Beta\n\nWhen using the AMD HIP as the Cycles render device a pixel appears on the bed sheet just below the boy. When using Optix this white dot is fainter, with CUDA a white dot appears in a different location and the original white dot is fainter but noticeable. With CPU rendering the white dots are not noticeable.\n\nRepo Steps\n-------------\n1. load \"Monster Under the Bed\" scene by Metin Seven.\n2. Set the render samples in the render properties tab to 1024 samples.\n3. Hit F12 to render the scene.\n4. white pixel appears\n\n\n| CPU | CUDA | Optix | HIP |\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", "Pointness gives a white spots on a small objects \nWin10, gtx 1070\nBroken: 2.79,2.79a,2.79b\n\nPointness gives a white spots on a small objects (a few cm objects)\nIn the image below, you can see how the `Pointless` output is affected by the local size:\n\n\nThe leftmost object shows the smallest one, the middle one is of intermediate size and the one on the right has not been scaled.\n\n\n - Open: [pointess_scale_bug.blend](pointess_scale_bug.blend)\n", "Occasional render glitches when using simulation zones on an object without a material.\nThis bug has an easy workaround, mostly posting this so anyone running into the same issue knows the solution.\n\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.30.02\n\nBroken: version: 3.6.2\nWorked: N/A, 3.6 is the first version with simulation nodes.\n\nIn Eevee, rendering an object with a simple simulation zone applied in geometry nodes and no material assigned to the object results in some rendered frames being blank or displaying odd glitches.\n\nThe workaround is to simply assign a material to the object.\n\nCheck out the attached .blend file for reproduction.\n\n", "Denoiser creating artefacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\nWorked: ー\n\nStrange artefacts are being created by the denoiser, firefly like bright and dark pixels where there were no such artefacts in the 'Noisy Image'. Looking into the 'Denoising Depth' pass reveals negated depth values around the artefacts. In the supplied .blend it seems to be caused by some weird interaction between the sun lamp and the water material with a black diffuse.\n\nDenoised Image: \nNoisy Image: \nDenoising Depth: \n(White values are ~90 black are ~-90)\n\nRender frames from supplied .blend\n[DenoiseBug.blend](DenoiseBug.blend)\n", "Evee Shading artifacts on metallic surfaces with mid roughness\nOperating system: Windows 64bit\nGraphics card: GTX 950\n\nBroken: (example: 2.81 Alpha, ad21a6c22461, 2019-09-08\n\nWhen renderign with Eevee I get ring shaped bright spots around GGX highlights.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nStart with a new file, delete the vertex at position 1, -1, 1\nAdd a metarial to this cube.\nset metallic to 1\nset roughness to a value between 0.2 and 0.4\n\nset the power of the pointlight to 100W\nset the radius to 0\nmove it to (0.5, -0.5, 0.5)\n\nset the background color to black\n\nview it from the top in perspective mode\nyou should see a grey ring at a corner.\n\nIn my personal experience this might be caused by an unnormalized vector in the ggx calculation.\n\n\nThe .blend file and a screenshot:\nIndirect Lighting settings dont help since there is no indirect lighting going on. As far as I can see it's a problem with the microfacet shading.\n[bug.blend](bug.blend)\n\n", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "Panoramic Render in Cycles. Bump bug.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.1\n\nWhen using a material with fine bump and a panoramic camera the bump appears inncorrectly in rendered view.\n\n- Give an object a material with a fine bump (e.g. noise texture 15 detail, .8 roughness. Bump strength 1, distance 1)\n- Bring camera in really close.\n- Set to cycles.\n- Switch camera between panoramic and perspective mode.\n\nPlease let me know if there are any work-arounds, this bug is causing me problems.\nThank you.\n\n", "Flickering macOS Blender 2.83\nOperating system: macOS 10.15.4\nGraphics card: XFX Radeon RX 580 8 GB\n\nBroken: 2.83\nWorked: 2.82\n\nFlickering occurs sometimes, as seen on this capture:\n[Screen Recording 2020-06-16 at 09.11.21.mov](Screen_Recording_2020-06-16_at_09.11.21.mov)\n\nI don't know exactly. I think it happens when I use Blender, then I switch to other applications and then return to Blender.\nIf I go to full screen mode, it's back to normal.\n\nThanks.", "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)", "Light show wireframe on alembic animation, and light pass throught some places of the mesh\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nCYCLES - I imported a alembic animation of a missile, when i try to add a point light on it, it show the wireframe. Also an other issue is if i add the light in the back of my missile, light pass throught my mesh at somes places. Very strange. Maybe a bug with .abc ?\n\nI attached a blend file, very simple scene. Just imported a .abc animation and parent a light to it .\n\n", "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.", "Strange shadow when rendering with GPU device\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\n\nThere's a shadow in the scene that doesn't make sense.\n\nI've attached a Blender file that I've tried to strip down as much as possible. Here's what I get (notice the strange shadow bottom middle)...\n\nThe odd thing is that if I delete/hide random objects in the scene, the shadow disappears.\n\nExample... hide any of the following objects:\nMISTY_MOUNTAINS_39_2k_c.001\nPlane.001\nAny object in the atmos folder\nObject_4.001\nthe whole quixel folder\n\nI know the shadow shape is cast from the volumetric cloud container shape (a spherical shape) but it's behaving very oddly and, as I use volumetrics in every single scene I ever create, I'm familiar with them behaving oddly. This is just a new one.\n\n[shadow error.zip](shadow_error.zip)\n", "Shadow caustics visible through colored glass has intensive, solid color for directional/sunlight and are probably too dark for spotlight/pointlight\nOperating system: Windows 11\nGraphics card: GTX 1070 Ti\n\nBroken: 3.22 master\nWorked: none\n\nThis happens when transparent object intersects with diffuse one and caustics are visible though volume. I know that MNEE doesn't work with volumes, but I think this might be a bug.\nFor directional light and sunsky system caustics are colored to pure red, green or blue or are just white. No other colors are possible. Spotlight and pointlight work, but color of intersected primitives differs substantially from not intersecting ones when looking thought them. This is especially visible on the left upper sphere that has only slight tint. Hope this is useful.\n\nmnee nishita sunsky:\n\n\nmnee directional light:\n\n\nmnee spotlight:\n\n\n\n1. Create an object casting caustics like sphere over default cube.\n2. Create transparent material for sphere that consists of two shaders, glass and volume, adjust volume color to something darker then white\n3. Turn on caustics for light and for objects, render in viewport.\n4. Move the sphere so it intersects with the cube, see the result.\n5. Switch light into directional mode and try to adjust volume absorption color.\n\n...or just open attached file and render. Lighting is set to nishita sky, but both spotlight and directional light are added and hidden.\n[mnee_test_master.blend](mnee_test_master.blend)" ]

[ "Random fireflies with Eevee\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\nWorked: NEVER\n\nSo I tried to find the cause of this problem for 2 weeks straight. And I didn't succeed. Trying different versions of Blender; disabling objects/materials/modifiers; recreating scene from scratch (+ with loading factory settings (+ on different versions)) - NOTHING helped to find the root of this problem. Originally, I found this bug after rendering animation. But countless experiments showed me that this happens with \"Render Image\" as well. These fireflies just randomly appear on my renders. I can render one frame first time and everything will be okay, and on second render of this same frame - fireflies will appear. \nIm burned out with frustrating bug and giving up on my searching. So I hope someone here will be luckier than me. \n\np.s.: fireflies can also appear in a viewport, but they are hard to catch\n[Car_291_3.blend](Car_291_3.blend)\n\n1) try to render attached file like 20 times using \"Render Image\"; \n2) try to render 100 frames from the attached file using \"Render Animation\";", "Eevee Light Artifacts World Volume - Video\nOperating system: Windows 10\nGraphics card: 2070 Super Lastest drivers as of 21.09.2020\n\nBroken: I have experianced this in 2.83, 2.90 and the latest build 2.91.0 Alpha, branch: master, commit date: 2020-09-20 18:23, hash: e14894aad2b8\nWorked: Has Never Wroked\n\n\nI seem to be getting light artifacting with Eevee video renders, I seem to have narrowed it down to world volume shader causing the problem, but not sure what else it is interacting with it, as it does not seem to be issue for many others. It also seems to be random, as I can render an indivdual frame from a video and not have an issue. Or re-render the video and artifacts are different again.\n\n\n\nAttached is an example frame from the attached blend file and also a video I have been working on experiancing the issue.\n\nHere is an example of anther use experiancing the issue as well [name ](1254312)\n\nCreate new scene with standard cube and a plane for the ground, one light source and camera.\napply a material to ground and cube.\nset world background colour to black\napply a mixed volume shader to world volume\nset all eevee render settings to high\napply a camera movement for video\nRender out video\n\n\n[test speaker yesh boi_0000505-0810.mkv](test_speaker_yesh_boi_0000505-0810.mkv)\n[Eevee Light Flares.blend](Eevee_Light_Flares.blend)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Eevee random flickering lights when rendering\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09\n\nBroken: version: 2.91.0\n\nThere's one light object in the scene and when rendering, it caused a pixelated fog. So I tweaked the tile size to 2 px and though it fixed those pixels, now I get weird flashing in random places. [Video ](bIB2FJvLVik).\n\n\nSet Tile Size in Volumetrics to 2 px, anything other than 16 px will cause the flickering.\n\n\n[misha4.blend](misha4.blend)\n", "Weird spots of light when rendering with EEVEE\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.90.1\n\nI'm getting these random flashes of light when rendering with EEVEE. I only have 2 static lights, area and spot, and a world HDRI. And also a sphere with Principled Volume in the scene for mist.\n\nMy GPU or CPU are not overclocked and I have the latest NVidia Studio driver.\n\n\n[break dancer.mov](break_dancer.mov)\n\n[Break dancer.blend](Break_dancer.blend)", "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**", "Random flashing coloured lights\nDuring an EEVEE render if bloom is enabled lights will randomly pop in some frames of random position and colour, re rendering the frames that had the lights will fix the issue, but doing this is not a very feasible solution if there are alot of frames that need fixing.\n\nPlease find attached an example of a frame which has this phenomenon as well as a copy of the blend file. The scene in which the Blend file is creating there are supposed to be alot of floating lights (Blue) but there are certain frames in which similar looking lights of varying colour (as well as only appearing for 1 frame) appear, those are obviously not intended.\n\nThese flashing lights appear in any sort of EEVEE render even if the lighting is bright and there is no intention of any sort of floating fairy lights.[Fantasy scene.blend](Fantasy_scene.blend)\n\n\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 2.90.0\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", "2.83lts Regression: Viewport render image ignores colormanagement, and appears to be hardcoded to use sRGB.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBisect points to 190fd795a9\nBroken: version: 2.83.0\nWorked: 2.82a\n\n`Viewport Render Image` ignores color management. The image produced is clamped to 1.0 according to the color sampler. It appears to be hard coded to sRGB.\n\nCreate a Scene that has scene linear color values above 1.0. Render with Filmic. Then do `viewport render image` and see how it produces an image with blown out highlights.\n\n2.82a:\n\n\n2.83:\n\n\n\n[test.blend](test.blend)\n\n", "Camera background movieclips are not visible if \"Viewport Shading\" is set to \"Rendered\" \nOperating system: Linux-5.4.0-65-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.92.0 Beta\nWorked: 2.90.1\nCaused by 3ffa0452af\n\nWhile static background images of cameras are correctly visualized when \"Viewport Shading\" is set to \"Rendered\", background image sequences defined with the clip editor are only visible when \"Viewport Shading\" is set to \"Material Preview\", \"Solid\" or \"Wireframe\" \n\nIn the following python script adjust the path such that it points to some valid input image.\n\n[background_image_test.py](background_image_test.py)\n\nExcecuting the script creates two cameras. \n\nThe first camera contains a static background image (see the code snippet below)\n```\nstatic_background_image = static_camera_data.background_images.new()\nstatic_background_image.image = bpy.data.images.load(image_fp)\n```\nand is visible for all \"Viewport Shading\" types.\n\n\nThe second camera contains a background image defined by a video clip (see the code snippet below),\n```\ndynamic_background_image = dynamic_camera_data.background_images.new()\ndynamic_background_image.source = \"MOVIE_CLIP\"\ndynamic_background_image.clip = bpy.data.movieclips[first_fn]\n```\nwhich is not visible when \"Viewport Shading\" is set to rendered.", "ShowNavigationGuide refresh Problem\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nno Updating the Viewport when setting the the Navigation Guide on/off\n\n \ninside Blender -Preferences -Input -Show Navigation Guide \nno refresh when checking the Show Navigation Guide on off .\norbit in the 3d-view will refresh and Update these changes.\n\n\n\n\n", "Regression: Visual bug when using the object gizmos\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\nCaused by 917a972b56\n\nDifferently from using the transform tools in the toolbar, when activating the object gizmos that stay visible also with the select tools, a strange bug occurs that the e.g. moving the object on an axis keeps a grey axis where it was before, the gizmo is always present (differently again from using the transform tools), and if you switch from this to the transform tools to the selection with gizmo again, it messes the origin of the object.\n[2021-09-20 14-59-52.mp4](2021-09-20_14-59-52.mp4)\n\n\nI'm pretty sure that this is caused by the recent change of keeping the viewport gizmo visible when doing these operations.\n\nUse the select tool in the toolbar, activate on or more object gizmos that stay always visible, do a transform operation.\n[Based on the default startup]\n\n", "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", "Transparent Object intersecting shows artefacts in Render, but not in VP preview render\nOperating system: Win10\nGraphics card: GeForce980\n\n\nBroken: 2.93, 2.93, only in Cycles\nNote this was always visible, but there seems to be a change between 0f61b27e93 (where this was a lot less noticable) and then e14894aad2 (which already shows the current behavior).\n\n2 Objects imported from a CAD via .PLY, they intersect slightly. Gave one of them a fully transparent material, it shows up in render in the form of shadows (or dark reflections?) on the other one. Solving the intersection, disabling ray visibility for camera both solves this, but it still feels like a bug.\n\n\nOpen .blend, press render. Move up solid2_solid2, disable its ray visibility or use vp preview render for comparison.\nNormal Render (object is fully transparent)\n\nobject hidden for camera (still some artefacts)\n\nobject excluded from render - no artefacts\n\n\n[OverlapBug.blend](OverlapBug.blend)", "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)", "EEVEE: Add support for extracting alpha channels from a color\nI mistakenly filed a bug report --> #72856 EEVEE transparency problem with mtpaint PNG\n\nI didn't fully understand the bug and attached a blender file that didn't show the bug properly.\nPacking the image file with blender command 'Pack' makes the image\nopaque so it is worthless to include a blender document. I will\ninclude a mtpaint PNG image instead and you can load it into\nblender 2.81 yourself and see how it renders in EEVEE versus cycles.\n\nI noticed that your forum converts the image to opaque if I try to attach to this post\nso I'll use a shareable link that preserves the transparency:\n\nopen?id=1TjfSjzabYEmVHXTODPFymGVNwuL02SnJ\n\nHere is how I created the mtpaint image to reproduce the problem...\n\n1) Launch GIMP -->new gimp document -no alpha channel - paint with brush\n2) save as PNG format with no alpha channel\n3) Launch mtpaint ---> open the PNG document\n4) 'Save as' to output the document - one color chosen to be transparent - PNG format\n5) Launch blender 2.81 (linux) - images > Images as planes\n\nEEVEE rendering doesn't respect the transparent region.\nCycles rendering does respect the transparent region.\n\n\nNot a high priorty.", "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)", "Wireframe opacity slider does not work.\nOperating system: Windows 10\nGraphics card: gtx1060\n\nBroken: 3.1\nWorked: \n\nWireframe opacity slider does not work if smooth wires is turned off.\n\nopen preferences>viewport\ndisable smooth wire overlay\nsave preference\nset viewport to wireframe shading\nin the overlay panel in viewport drag the wireframe opacity slider, the wire color will fade to black, the opacity won't change.", "shadow catcher data missing from diffuse passes when transparency is disabled, and shadow catcher object is masking environment when transparency is enabled (can't recombine moving scene envronment)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\n\nshadow catcher data missing from diffuse passes when transparency is disabled, and shadow catcher object is masking environment when transparency is enabled (can't recombine moving scene envronment). This makes it impossible to rebuild the image unless the shadow catcher pass is used, which is not suitable when using vector motion blur.\n\nOpen below blend file (choose to load ui)\ngo to scene 'no transparency'\nin the compositor press f12 to render a frame\ncompare the combined image and the rebuilt image\n\ngo to the second scene 'transparency'\nin the compositor hit f12 to render again\nthis time the environment is masked out by the shadow catcher, making it impossible to use the rendered environment (which is necessary if the camera is animated)\n\nrequired behaviour - \n\nshadows appear in diffuse passes when transparency is disabled, so the rebuilt image matches the viewport.\n\nshadow catcher object doesn't mask out the environment pass when transparency is enabled (so the environment can be added back to the image when the camera is moving (backplate cant be used here))\n\n\n\nThe only possible solution currently is to always render with transparency enabled, and then render your scene a second time with only the environment visible, which causes issues when rendering via scripts.\n\n", "Support previewing geometry in the viewport\n", "Asset Browser: Material preview with black background when Cycles is disabled\nBroken: version: 3.0.0, 3.4.0\nWorked: Never\n\nWhen a scene was saved with Cycles but I disable the Cycles add-on the material previews get a black background.\n\n* Disable Cycles add-on.\n* Click on any (e.g., the Yellow) material asset and update its preview.\n[black_preview.blend](black_preview.blend)\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." ]

[ "Seamless 3D view issue\nOperating system: Linux-5.19.0-26-generic-x86_64-with-glibc2.36 64 Bits\nGraphics card: NV167 nouveau 4.3 (Core Profile) Mesa 22.2.1\n\nBroken: version: 3.4.0\n\n\n\n\nHello I would like to report a problem of transparency of 3D and timeline views.\n\n[Capture vidéo du 2022-12-07 21-06-25.webm](Capture_vidéo_du_2022-12-07_21-06-25.webm)" ]