Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "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 ", "Blender Crashing When Painting Stroke into a \"Moving Animated Character\" (heap-use-after-free)\nBroken: 4.0 alpha\nBroken: version: 2.79 - 2.82 (sub 7)\nWorked: Never\n\nI have this experiment of making LIVE talking head, via OSC. And I noticed that if I tried painting a stroke on a talking moving animated head, it will crash. Even with timeline not running.\n\nI got a video (Might need iPhone X with MOM addon to test this....) :\njhHdG6ZXFDU\n\n- Open attached file\n- Run animation\n- Paint over the animated object\n[paint_animated_shapekey_bug.blend](paint_animated_shapekey_bug.blend)\n\n\n", "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```", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Blender 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)", "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)", "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", "Segmentation fault when selecting context.area.type before applying operator (scripting)\nOS: Ubuntu 16.04.4 LTS\nHW: Dell XPS 9550 notebook, using Intel HD GPU (nvidia deactivted)\n\nBroken: 2.83\n\nExecuting the operator `bpy.ops.transform.translate` causes a crash if `bpy.context.area.type` is set manually before.\nCrash in `setTransformViewMatrices` because `t->ar->regiondata` is `NULL`\n\nRunning the following script causes the crash:\n```\nimport bpy\nimport bmesh\n\n# Create object\nbpy.ops.mesh.primitive_plane_add(size=1, enter_editmode=False, location=(0, 0, 0))\n\n# Enter edit mode\nbpy.context.area.type = 'VIEW_3D' # If this is not set, crash does not occur\nbpy.ops.object.mode_set(mode='EDIT', toggle=False)\n\n# Modify vertices\nmesh = bmesh.from_edit_mesh(bpy.context.active_object.data)\nmesh.verts.ensure_lookup_table()\nmesh.verts[0].select = True\n\n# Next call causes crash:\nbpy.ops.transform.translate(value=(0, 0, 1), constraint_axis=(False, False, True),\n mirror=False, use_proportional_edit=True,\n proportional_edit_falloff='SHARP')\n```\n", "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 - 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", "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", "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>", "Mouse movement causes crash during particle bake\nOperating system: Win10\nGraphics card: GTX2060\n\nBroken: 2.90, 0330d1af29c0, master, 2020-08-31\n\nReproducible crash when baking particle animation and moving mouse\n\nSadly, I was not able to reproduce the crash in a simpler file, so I assume it has to be related to the current boid setup with lots of drivers.\n\n1. Load the attached blend file\n2. Make sure Workspace is set to layout\n3. Select one of the two particle-emitters\n4. Click bake\n5. During bake move the mouse over Render or Graph views\n- > Crash\n\nAlso see this video capture: VIUy6r9S-Hk (It ends in the moment of the crash)\n\n[swarm-test1.crash.txt](swarm-test1.crash.txt)\n\n[swarm-test2-crash.blend](swarm-test2-crash.blend)", "Blender crashes after rendering a few frames of an animation\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nI've never had this kind of problem - Blender crashes randomly after rendering a few frames of the animation. The only \"new\" thing I'm doing is I started using geometry nodes in this scene. I have plenty of VRAM left, shouldn't be a GPU issue. Tried both in 3.4 and 3.5\n\n\n", "Blender 3.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 when the Home button is pressed in the VSE\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 5500M ATI Technologies Inc. 4.5.14761 Core Profile Context 21.10.2 30.0.13025.5005\n\nBroken: version: 3.0.0\nWorked: 2.93.7 (tested on Ubuntu 21.10)\n\nI was cutting a video and wanted to get the timeline in focus (Home button). Blender immediately crashed.\n\n* Open the attached blend file\n* Hover over the Sequencer Timeline\n* Press the Home button\n\n[bug.blend](bug.blend)\n\n**Additional info**\nThis once was a larger video project. I removed everything up to the point where the blend file seems pretty much as empty as it can be empty.\nThe scene itself never had anything in the VSE, but only in the 3D view. The 3D view only had some very simple geometry in it.\nThis never happend before and I have no idea why it crashes. The crash is reproducable though.\n\n**Linux**\nI tested the issue on Ubuntu 21.10. I got the same result.\nI tested blender 3.0 and 2.93.7. Version 3.0 crashes, 2.93.7 does not crash. See also attached system info files.\n\n[system-info 2.93.txt](system-info_2.93.txt) [system-info 3.0.txt](system-info_3.0.txt)\n" ]

[ "Subdivision Surface modifier performance issues\nOperating system: Xubuntu 18.04\nGraphics card: Nvidia Titan X (Pascal)\n\nBroken: 2.80 26d5a3625ed\nWorked: Before the new \"Quality\" setting was introduced in the Subdivision Surface modifier\n\nThe Subdivision surface modifier has slowed down significantly, especially noticable with multiple Subdivision Surface modifiers on the same object.\nCreating the same setup in the builds before the new setting is as fast as 2.79.\n\n- Create Monkey object\n- Add Subdivision Surface modifier\n- Add Wireframe Modifier\n- Add second Subdivision Surface modifer\n[slow-subsurf.blend](slow-subsurf.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", "soft body issue\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nWith some soft body basic setting sometine the object go crazy and disappear, with almost same setting sometime it work fine. \n\nMake a Suzane and a subsurf by 3 applied, make a plane for the floor and make it collision.\nMake Suzane softbody and uncheck the goal button. Make pull and push a hight value (9.5 for exemple) and a hight Bending value (like 9). Bake it and see what append, if it work just tweak a little bit the setting and sometime the scene go crazy (Suzane disappear at frame 2 or 3).\nIf I reduce the poly count (suzane with subsurf at 2) it append less but sometime the same thing append.\n\n\n", "Fluid modifier affects particle hair (even when set to None)\n(blendfile attached : view?usp=sharing ) \nUsed Blender 2.91.\nDon't really know how to reproduce the because when I try reproducing the bug by adding a fluid modifier to a scalp before (in the modifier hierarchy his edited particle system, the hair edit changes in the edit particle, as well as it changes in object mode. However, with my original file, the hair edit don't change in edit particle mode, whether I hide the fluid modifier or not, it just changes in the other mode, e.g. object mode.\n\nHello,\nMy hair is very buggy and, I really, really need help on this.\nI have a hairstyle composed of two layers, two particle system, one for the main hairs, and one for the frizzy hairs. The scalp where the hair is, has modifiers set up like this :\n\n\n\nAnd here is a picture of the hair how I want em, and how I stylized em in the particle editor :\n\n\n\nBut this is how it looks when I disable the fluid modifier that the scalp has\n\n\n\nAnd this is how it looks when I uncheck the “Dynamic Hair” box\n\n\n\nI want to simulate my hair, but when I bake it, it comes out weird and deformed, plus, the main hair are static, there is only the frizz going crazy.\nWhat am I doing wrong, please I really need help, at the end I want to be able to simulate my hair correctly, them looking exactly like the first picture, but without the fluid modifier, wich I think is causing problem in the sim.\n\nIf you can provide help, please do, It’s urgent, and I absolutely need this to get fixed, and If you can’t provide me help, like or upvote my post so that other users that can help, see my post.\n\n(blendfile attached : view?usp=sharing )\n\nEdit : If you wanna see the particles in edit particle mode, make sure this option is set to particles :\n", "Armature modifier slows down any transforms on an object\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 2.92.0\n\nHaving the armature modifer on an object with a slightly high polycount slows down any transformations (move, scale, rotation) done to it in the viewport.\nEven with the modifier disabled in view still slows down its movement.\nThis slowdown is very impactful to the smooth playback framerate of projects.\n\nHere's a video of the steps (I started out in the default scene and deleted all the starting objects)\n0Bgx_1JEouc\n\n- Make a high poly mesh (Eg. Suzanne subdivided 5 times)\n- Add Modifier: Armature\n- Transform the high poly object (Mode, rotate ...) and note the delay in fps", "Modifiers header misalignment on change Resolution Scale [pixel perfect thing]\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5161\n\nBroken: version: 2.92.0; blender-2.90.0-d7c4e9649320\nWorked: don't know\n\nModifiers/Constraints header buttons misalignment on different (especially smaller) Resolution Scale value\n\nSimple as that. Tried set Resolution Scale down on a notebook, and saw the modifier name input \"jump\" out of the modifier box.\nSo checked that any value bellow 1, varnishes the \"top margin\" of it. The same on constraints, bones included.\nThan i suppose it has something to do with the dragging feature.\n\nOpen Blender.\nAdd any modifier/constraint an object.\nGo to Preferences -> Interface -> Display -> Resolution scale, and click the input's left arrow.\nSe the bug on the modifier header\n\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", "\"Disable in Viewport\" option results in UI for \"Disable in Render\" not updating properly when it is keyframed\nOperating system: Linux-5.10.0-8-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: NA\n\nBroken versions: 2.82-3.4\nWorked: Unsure\n\n**Short description of error:**\n\"Disable in Viewport\" option results in UI for \"Disable in Render\" not updating properly when it is keyframed.\n\n**Exact steps for others to reproduce the error:**\nFollow the steps shown in the video above or follow the steps below:\n1. Start with a new file.\n2. Select an object.\n3. In the `Object Properties` tab of the `Properties Editor`, expand the `Visibility` panel.\n4. Inside the `Visibility panel`, animate the the `Show in -> Renders` property. You can do this by inserting a keyframe for it being enabled on frame 1, then go to frame 2 and disable it and keyframe it again.\n5. Once the `Show in -> Renders` property is animated, disable `Show in -> Viewports`. Now if you scrub through your time line, you will notice that the UI for `Show in -> Renders` does not update the `Tick` as you go back to a frame you had keyframes to be enabled. This can also be observed in the `Outliner` as the `Camera` icon does not change from disabled to enabled or vice-versa.\n6. If you enable `Show in -> Viewports`, you will notice the `Tick` and `Camera` icon start updating again as you scrub through the time line.\nHere is a video demonstrating the issue:\n[Disable in viewport breaking disabled in render.mp4](Disable_in_viewport_breaking_disabled_in_render.mp4)", "Crash with animated displacement modifier in Texture paint mode while playing\nAMD Ryzen 5 2600, 16GB ram\nWindows 7 64bit\nNvidia GTX 1060 6gb (driver version 416.34)\n\n2.79b\n\nI intend to paint a heightmap interactively. So i keyframed a displacement modifier (2 frames) on a subdivided plane and assigned a texture.\nPlaying the timeline should now refresh the modifier every frame. \nPainting in the UV-editor this way works fine, but switching to texture paint mode and painting on the mesh directly crashes blender after about 0.5seconds.\n[HeightmapPaint.blend](HeightmapPaint.blend)\nI attached an example file.\nHit play and in the uv editor paint on the noise texture. This works okay.\nNow switch to Texture painting in the 3d viewport. The moment a stroke is applied to the mesh it should crash (it does consistently for me). ", "object display as wire , invisible when overlay is turned off \nwin 10\nintel i5\namd radeon \n\nblender 2.8 \n6b39dc7672eb\n\n\nNot sure if it's abug or intended behaviour \n\nWhen an object is set to wireframe ( object properties , viewport display ) , when overlays is turned off , the object is not shown ", "Booleans are completely breaking on my object\nOperating system: macOS Monterey (ARM64)\nGraphics card: Apple Silicon `M1`\n\nBroken: 3.2.0 Alpha & others\nWorked: *2.83.X*? (reported in comment)\n\nBooleans can often be very touchy and may require positioning them just right for them to do operations properly. It seems that it really depends on where the vertices line up. I've been cutting window slots out of ridged galvanized steel plates using boolean cubes and it's worked for every other object. However, this one particular piece in my scene has been causing endless trouble for me despite being the exact same procedure. Seems as though I need to put my boolean objects in the EXACT RIGHT place for them to work right. I found that adding a ludicrous number of subdivisions w/ the subsurface modifier can somewhat help, but it greatly depends on whether or not I position my cubes in the right spot. It is preventing me from placing my windows where they need to go on my scale accurate historic building recreation. I don't know why this object is being so temperamental but it is blocking me from making any progress on this side of the building and I'm afraid I'll keep running into the problem later on.\n\nI may post additional demo files that showcase more boolean issues as I frequently run into problems of faces not being filled properly, crappy vertex extrusions, objects being weirdly combined instead of differenced, and many more annoyances. I hope booleans can get a lot more love from the developers so that they work as intended.\n\n\n\nI'm not entirely sure how to reproduce an issue like this. It mostly plagues more detailed models but can happen anywhere and depends on object positions, alignment, topology, and so on. Attached is a problematic file.\n\n**Attached file information**\n[F12870489](brokenBooleans.blend.zip) There are several issues present. For one thing, the boolean modifier is struggling to cut a simple rectangle out of a plane. It is adding geometry to certain parts, cutting out geometry that shouldn't be cut out, and is not accurate at all. I've noticed that using the \"fast\" option usually yields better results than using the \"exact\" option. However, in the case of this object, it actually breaks it EVEN MORE! Try selecting the \"cutoutGalvanizedSteel\" (planar object) and setting the booleans to \"fast\" to see a new problem emerge. Adding a solidify modifier to the very top of the stack will fix the issue. However, booleans should work on planes, too.\n\n[F12871474](BorkedBooleans.blend.zip) Many different problems. Boolean objects are displayed as wireframes. If you see a boolean as having geometry, it's because it is being added by the Boolean modifier. The boolean modifier likes to add the boolean's geometry to the source mesh sometimes, even when it is set to difference or intersection. In issue 2, there is a mesh problem in the boolean. If you enter edit mode, you can see that the problematic vertices are selected. They crash the boolean operation altogether. Merging these vertices will solve the issue, but for more complex boolean objects, this may not always be an option.\n\n[brokenBooleans.blend.zip](brokenBooleans.blend.zip)\n[BorkedBooleans.blend.zip](BorkedBooleans.blend.zip)", "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.", "Edges, generated with Triangulate modifier looks differend and do not disappear with hiding.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 640/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\n2.83 release\n\n\n[2020-06-18_15-14-00.mp4](2020-06-18_15-14-00.mp4)\n[untitled.blend](untitled.blend)\n\nDefault cube with Triangulate modifier, wireframe mode, edit mode.\nSelect all, hide. You will have this.\n\n\nThere is no way to part of mesh with generated edges and hide another part.\nAlso weird shading for polygons.\n\n\n", "Mesh is not being deformated correctly via Mesh Deform Modifier (quads, tris behave better)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.4\n\nI have an Object 1 that I use as a Mesh Deformer target to on Object 2. Both are meshes, of course. Object 1 is parented to an Armature with just 1 Bone.\nWhen I rotate the bone, the Object 2 is deformed incorrectly. It looks like \"waves\" are going through it.\n\nBind Object 2 to and Object 1 with Mesh Deform Modifier. I use Precision of 6 which I think must be enough for such a simple construction. Then Rotate the Main Bone.\nI also added the Camera parented to the Bone, so that you could use view from camera to see changes, relative to the rotation movement itself.\n\nNote: triangulating the cage mesh with a modifier during bind seems to eliminate most of the wiggeling.\n\n[Mesh_Deform_Bug.blend](Mesh_Deform_Bug.blend)\n\n[Mesh_Deform_Bug.mp4](Mesh_Deform_Bug.mp4)", "Animation Editors: Modifier keys cancel out dragging handles \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.4.0 Alpha\n\nIn recent releases db4313610cab was implemented and the animation editors are still not adapted to this behaviour. This fix allows the use to press any keyboard key, like `Shift` or `X`, etc, before the drag threshold of the current action is reached, and it will cause the operator to execute.\n\nFor example: Click and hold on a move gizmo in object mode. Either drag 3 pixels to start the operation and then press `X` and hold `Shift` to slowly move along the x axis.\nOR immediately press `X` and hold `Shift` without reaching the drag threshold of 3 pixels to already start the operator.\n\nBefore this fix, any pressed keys would cancel the click & drag and prevent the operator from running.\nThis is still the case with the graph and dopesheet editors.\n\n- Create a simple animation to the default cube\n- click and drag on the keyframes or handles in the animation editors\n- Now click and hold them, hold `Shift`, and then continue to drag. Nothing happens." ]

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

[ "Greasepencil 3.0: Unable to switch to drawmode from sculptmode\nOperating system: Linux-5.15.0-73-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: 4.0.0 Alpha\n\nEnable GP 3.0\nOpen 2D session\nSwitch from the initial draw mode to sculpt mode via header button.\nTry to switch back to draw mode.\nAn error message appears:\n\n", "Sculpt mode. Layer brush. Persistent base breaks with local mode.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Alpha\n\n\nIf I set persistent base in default mode and go Local, i loose persistent base. Same for Local→Main\nI can't rememeber if persistent base or sililar thing used in another area. But I assume, it may be broken too.\n\n[2020-12-16_17-15-04.mp4](2020-12-16_17-15-04.mp4)\n\nsummon @PabloDobarro ", "Tooltip for the Drag tool setting\n## Issue\nRecently for Blender 3.0 the \"Drag\" option in the header tool settings was included for most active tools. This allows right click select users to make use of this feature by using the option \"Right Mouse Selection Action = Selection Tool\" in the keymap preferences.\nThe issue is that these options still have no tooltip so it can be hard to understand how or why to use this feature.\n\n\n\n### Proposal\nWe need a simple tooltip with the following information:\n\n- General information\n- Sub Tooltip (From what it is currently set to)\n- Shortcut of the Pie Menu for quick access\n- Context sensitive information based on keymap settings (right or left click select)\n\nSo this would be:\n\n> Action when dragging anywhere in the editor with left click: Select Box\n> Select items using box select.\n> *Shortcut: Alt + W*\n\n\nOr when right click is used in the keymap preferences:\n\n> Action when dragging anywhere in the editor with right click: Select Box\n> Select items using box select.\n> *Shortcut: Alt + W*.\n\n\n## Related issues\n\nThe tooltip for the setting \"Active Tool\" needs to be changed. \nIt currently says:\n> Action when dragging in the viewport: Active Tool\n\n\nIdeally this would be changed to something that fits the other options.\n\nAnother thing to keep in mind is that the tooltip Tweak for tweak on right click select is still \"Set the location of the 3D Cursor\".\nThis is since recently wrong and needs to be updated. \n\nAlso there are never shortcuts for pie menus mentioned in tooltips so far, even though they are heavily used.\nPie menu shortcuts that also aren't mentioned are for example: `Tab` for modes, `Z` for shading, `.` for Pivot Point and `,` for Orientation.\nThis can be handled as a separate task: #92478", "Vertex paint mode breaks permanently under certain conditions (Global undo involved)\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: 3.6.0 Alpha\n\nCaused by 575ade22d4de (vertex paint now does `SCULPT_undo_push_begin_ex` in wpaint_invoke [which leads to `BKE_undosys_step_push` using sculpt undo])\n\nVertex paint mode breaks permanently under certain conditions\n\n- turn OFF Global undo in Preferences\n- enter vertex paint mode\n- make two strokes\n- Undo (prior to 575ade22d4de nothing was undone, now stroke is actually undone)\n- Undo again (this now takes you out of vertexpaint mode into object mode prior to 575ade22d4de you would never leave vertexpaint mode)\n- enter vertex paint mode\n- painting is not possible anymore (strokes have no effect)\n- this is also true for other objects\n\n", "Sculpt performance warnings in the UI\nMultiple options in Blender can cause performance drops in sculpt mode (using modifiers, shape keys, EEVEE, dyntopo). Most of these options are handled in the code in ##BKE_sculptsession_use_pbvh_draw##\n\nUsers often report poor performance in sculpt mode because there is currently no information in the UI when the object is not using the sculpt mode optimizations. We have the ##use_deform_only## option to partially fix these problems, but new users are not aware of it and it only covers the modifier stack, but not EEVEE or dyntopo. \n\n**To be decided**\n - How and where to show these warnings\n - Should we include an operator to disable all settings (modifiers, viewport, shape keys...) that are causing the performance problems?", "Paint Mode: Pixel Brush Tool\nThis task design is about adding a pixel brush tool as a potential solution to the current limitation in texture paint mode to not being able to paint textures in a pixel art style not even able to paint single pixels.\n\n\nBefore looking into this solution let's check anothe non-pixel-brush-tool alternative and see the pros and cons of each one so we reach a conclusion.\nFeedback and new ideas are welcome!\n\n\n**SOLUTION 1 - REFACTOR and EXTRA ADDITIONS:**\n- Replacing current brush radius (which is strange IMHO) to brush size. This will make possible to have brushes with 1px size (diameter) to paint single pixels.\n- Add alternative squared paint cursor display over cursor settings to have a better feedback.\n- Add AA toggle as a unified paint setting to make possible paint in pixel art with any brush and size.\n- Add pixel grid overlay in the overlays panel.\n\n**CONS:**\n- Cursor isn't aligned with pixel grid.\n- So much options user have to configure before doing pixel art. (cursor, AA, pixel grid...)\n\n**SOLUTION 2 - PIXEL BRUSH TOOL:**\n- To have a dedicated pixel brush tool independent from current paint brush. This tool will behave differently.\n- To paint single pixels and blocks/chunks of 2x2, 4x4, ... pixels.\n- To paint pixel art patterns and gradients.\n- Dedicated pixel grid overlay which will be automatically enabled depending on zoom or pixel size in screen space.\n- Align brush automatically to the pixel grid.\n- No need to pre-configure anything.\n\n**CONS:**\n- Align cursor to pixels in 3d viewport may be a lot of fun BUT extremely useful.\n\n--------------------------------\n\n**CONCLUSION:**\nIn conclusion, having a separated tool will be most suitable as a pixel brush needs specific behaviours, as a squared cursor, aligned cursor, pixel grid overlay and no AA brushes.\n\n--------------------------------\n\n\n### Let's talk about the PIXEL BRUSH TOOL solution!\n\nI've made a few prototypes in Python so I can give you all an idea of how it could behave:\n\n**• Pixel Grid Overlay**\n\n A grid per pixel.\n\n A grid per chunks of 4x4 pixels (or whatever configured by user).\n\n**• Align Brush Automatically to the Pixel Grid**\n[ezgif.com-gif-maker (15).mp4](ezgif.com-gif-maker__15_.mp4)\n\n**• Pixel Brush Tool overview**\n[ezgif.com-gif-maker (5).mp4](ezgif.com-gif-maker__5_.mp4)\n", "Sculpt mode -> Curve Stroke causes Undo to behave differently\nOperating system: Windows 10 x64\nGraphics card: Nvidia 980 GTX\n\nBroken: v 2.82 Alpha, 10-12-2019\n\nIf Brush stroke is set to Curve and some sculpt detail is added (Ctrl + Left Click), (Ctrl + Z) or Undo does not work. Instead of Undo for the sculpt detail, the curve control points are removed.\n\n1. Start with default cube and add Multi-Res modifier, subdivide a couple of times.\n2. Go to sculpt mode and with the SculptDraw brush set the stroke to Curve.\n3. Draw a curve using (Ctrl + Right Click) to add some control points.\n4. Add sculpt details using Ctrl + Left Click. \n5. Press Ctrl + Z. Instead of removing the details the control points of the curve will be removed first. \n6. Press Ctrl + Z repeatedly. When the last control point remains then the sculpt detail will be removed.", "Circle Select Tool Todo\n## Circle Select Tool Todo\n * - [x] {icon circle color=red} Add Radius control to the tool settings, to set the radius of the select brush\n * - [x] {icon circle color=red} There should be a brush circle size preview cursor always visible, just like a paint tool. Currently the radius is only visible while painting your selection.\n * - [ ] {icon circle color=yellow} Currently, Circle Select only selects object origins. Add enum option to select normally too.\n * - [ ] {icon circle color=yellow} Add options to create new selections, add to selections or subtract from selections.\n\n * - [x] 3D view.\n * - [x] UV editor.\n * - [ ] Action editor.\n * - [ ] Annotations.\n * - [ ] Tracking.\n * - [ ] Node.\n * - [ ] Graph.\n\n\n\n\n", "Symmetry in sculpt mode weird behavior with mask and face set\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.90.0 Alpha\nWorked: --\n\nWhen sculpting a non-symetric object with symmetry on, using shift+a or shift+w creates a weird behavior\n\n\n\n[bug.blend](bug.blend)\n- Open the file above.\n- use shift+a in the second finger like this:\n\n- Turn symmetry off and try it again:\n\n\nThe origin is far off those two fingers and also all the transformations are applied, so I don't think its an expected behavior,\n\n\nBesides, it doesn't happen when you try using brushes on the mesh. \n\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.", "Sculpt Mode: Improve Expand performance\nWith [D16434: Sculpt Mode: Invert Expand behavior for masking consistency](D16434) it will be a stronger focus to highlight the Expand operators as a core feature in sculpt mode to create masks & face sets.\n\nThe issue is that the operator tends to be too slow to initialize on high res meshes.\nThis is especially the case for the geodesic expanding method.\n\nWe need to address these performance issues.\nOne usggestion was to incrementally calculate the distances while the operator is running.", "Grease Pencil problem (especially soft pencil) \nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\n\nSince couple version of Blender I cannot use a soft pencil (mainly) brush in Grease Pencil 2D animation mode. The issue depends on how much You zoom. When You zoom in and use same size it's not visible. When You zoom out and draw with same size dots are visible. \nIt's behavior is very strange now and produces bad results (visible dotted lines or other which are visible on attached file. Some of these issues occur when the brush is small (line type set as dots). This is much more more visible when stroke stabilization is on. The bug was not there about 2 years ago and I was able to use the soft pencil without such problems. When line type is set to line the pencil stroke has strange contour around and when self overlap is off it produces artifacts on edges. \n\n\n\nJust choose a soft pencil and make it small. Check it with stroke stabilization as well. Then change the line type to line with self overlap on and off. \n\n", "Text Object: D key is used for the Annotate Tool\nOperating system: Linux-5.4.0-104-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.0 Alpha\n\nIn the keymap preferences there is an option to use the Active Tools for shortcuts instead of the modal operation.\nIt's called \"Tool Keys -> Immediate / Active Tools\".\n\nIf this preference is used and you go into edit mode of a text object, you are unable to type in the letter `D`.\nIt will always make the Annotate Tool active instead.\n\n- Enable the \"Active Tool\" keymap preference\n- Add a text obejct\n- Enter Edit Mode\n- Type in a word with the letter `D` in it like \"Addon\" ", "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", "UV Editor Tools Todo\n\n\n# UV Editor\nCurrently, the UV editor has a bunch of confusingly overlapping tool-modes. This should all be simplified via the new active tools system.\n\n * - [x] {icon circle color=red} Add Radius, Strength and the other relevant UV Sculpt settings to the tool settings & top bar\n * - [x] {icon circle color=red} Add Move tool to the toolbar\n * - [x] {icon circle color=red} Add Rotate tool to the toolbar\n * - [x] {icon circle color=red} Add Scale tool to the toolbar\n * - [ ] {icon circle color=red} Add Scale Cage tool to the toolbar\n * - [x] {icon circle color=yellow} Add Pan & Zoom gizmos in top right corner, same as 3d view.\n * - [x] {icon circle color=green} Add the Placement option to the Annotate tool settings (Current default is to only draw in the view, which is not so useful)\n * - [ ] {icon circle color=green} Add Shear tool to the toolbar\n * - [x] Split UV Editor from Image Editor\n * - [x] Remove old tools panels \n * - [x] Add 2D Cursor tool to toolbar\n * - [x] Add Transform tool to the toolbar\n * - [x] Make the Transform Scale Cage Gizmo only appear when Scale Cage transform tool is used\n * - [x] Fix Annotate tool in the toolbar, so that it actually works\n * - [x] Add UV Sculpt tools to the toolbar \n\n\n\nWhen in the Image Editor Paint Mode, we should follow the design of the Paint modes in the 3D View, meaning;\n\n * - [x] {icon circle color=red} Tool Settings should be in top bar\n * - [x] {icon circle color=red} Toolbar should work the same as in 3D View\n\n" ]

[ "Regression: Sculpt mode Annotation tool cursor conflict\nOperating system: Win 10\n\nBroken: 2.91, 3.4\nWorked: 2.90\nCaused by b9e4696641\n\nThe Annotation tool in sculpt mode is not using it's proper cursor. It's using the regular sculpting cursor instead.\nWhen you start drawing, the original cursor shows up on top of the regular sculpting cursor. \nThe end result is two cursors displaying at the same time and the original one flickering sometimes...\n\nTry to use the Annotation tool in sculpt mode....\n\nHere 2.90 (working fine)\n\n\nHere 2.91 (broken)\n\n" ]

[ "alpha does not contribute to adaptive sampling noise treshold\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\nWorked: i dont think it ever worked\n\nwhen rendering with adaptive sampling enabled, the noise treshold does not seem to be affected by a noisy alpha channel.\n\nthis is most visible on shadow catchers: since their rgb is always black, they are always rendered with \"Min Samples\", as soon as adaptive sampling is enabled.\neven though the alpha channel is still very noisy, it stops rendering additional samples.\n\n[shadowCatcherNoise.blend](shadowCatcherNoise.blend)\n- open file\n- render samples at 64-512 samples\n- when adaptive sampling is enabled, the shadow will remain very noisy. when adaptive sampling is disabled, the shadow will be smooth\n\n", "Particle edit mode - Hide hairs doesn't work\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\n\nBroken: version: 2.80 (sub 50)\nWorked:\nThe \"hidden\" hairs can't be selected or edited\n\n\nThe hidden hairs are still visible.\n\nAdd a hair system to the default cube \nSwitch to particle edit mode and then switch to point display/select mode\nSelect any number of particles, press H to hide\n- >The hairs are only locked, not hidden\n\n\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", "Flickering in unrelated hair strands when deleting hair\nOperating system: Linux-5.13.0-48-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.3.0 Alpha\nWorked: n/a\n\nWhen I delete the hair, the rest of the hair flickers. This doesn't happen when adding hair, changing their length, combing, ...\n\nNote it also happens when deleting hair with the density brush.\n\n* Open this file and delete some hair.\n\n[hair_flicker.blend](hair_flicker.blend)\n\nVideo:\n\n[flicker-2022-06-21_14.38.51.mp4](flicker-2022-06-21_14.38.51.mp4)", "Empty object property \"Size\" should be \"Radius\"\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.0\n\n- Mesh Cube is 1 meters wide when set its \"Size\" to 1 meters when creating\n- Empty Cube is 2 meters wide when set its \"Radius\" to 1 meter when creating.\n- However the property tab for the empty cube shows \"Size\" as 1 when it really supposed to mean \"Radius\".\n\n- Add a Mesh Cube with size 1 meter\n- Add an Empty Cube with size 1 meter\n- Compare the size. The size of Empty Cube is 2 Meters when set to 1 meter\n\n", "Hairs & custom normals\nOperating system: Linux 5.10.0-5-amd64 #1 SMP Debian 5.10.26-1\nGraphics card: Radeon RX 560 Series\n\nBroken: 2.92 (from snap)\nWorked: not known\n\n\nHairs does not consider edited ‘custom normals’ and still use ‘face normals’.\n\nLook at attached screenshot.\n\n[test_normals.blend](test_normals.blend)\n", "Sculpting Brush size becomes too big or too small outside the object when the radius unit is in scene\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\n\nSculpting Brush size becomes too big or too small outside the object when the radius unit is in the scene This is not file-specific it is happening in all files and for all objects. its sometimes hard to adjust the side at all when that happens. Attaching a video for reference\n\n- Create a new object and scale up or down a lot\n- Switch to sculpt mode\n- Change the Radius Unit to Scene\n- Examine the brush cursor size changes along the surface and in empty space from different angles & zoom", "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, ", "Particle Texture influence broken when using two particle system on the same object\nOperating system: Ubuntu 18.04\nGraphics card: GeForce 970GTX\n\nBroken: 2.90.1\nWorked: Never (2.8+)\n\n\nWhen using two particles system on the same object with an influencing texture, one particle system has a wrong influence (e.g. Particle System shrink to quickly)\n\nBlend File: [particle_texture_bug.blend](particle_texture_bug.blend)\n\n0. Set the animation start and end to 100 - 200\n1. Create an Emitter and a Particle Object\n2. Add a Particle System to the Emitter and use the Particle Object for rendering\n3. Set the Start and End to 100 - 200\n4. Give the Particle System a Blend Texture that influences the size with \"Strand/Particle\" as Coordinates\n5. Add another System and Duplicate the previous one to get the exact same setting\n6. Change the Start and End of the new System to 0 - 100\n7. Bake all Dynamics\n8. Render Frame 199 and compare to rendering of 101. The particles in 199 are tiny in comparison (or invisible). They should look near identical\n\nOptional: \n9. Remove the 0-100 Particle and Redo Baking\n10. Frame 199 now has normal sized particles\n", "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", "Hair particle length vertex group effect is non linear\nOperating system: MacOS Big Sur 11.2.3\nGraphics card: AMD Radeon Pro 5500M 8 GB\n\nBroken: 3.0 alpha, 4b06420e6504, master, 2021-09-13\nWorked: Unknown\n\nHair particle length scales non linearly with its length vertex group. Put another way, hair length is usually not quite equal to vertex weight * max hair length, which I assume is unintended. This causes problems when exact hair length is needed.\n\nThe screenshot below demonstrates the issue. \n\nIn this example, planes are instanced along the X axis from 0 to 1, using Geometry Nodes. The X position of each face is assigned to the vertex group controlling hair length. A hair particle system is added and set to spawn 1 particle per face.\nAs seen in the screenshot, the actual height of the hair is slightly wavy and doesn't form a straight line.\n\nHere's a video showing the same issue, this time spawning particles on a single face with interpolated vertex weights:\n[Hair Length Vertex Group Non Linear Bug.mov](Hair_Length_Vertex_Group_Non_Linear_Bug.mov)\n\n1. Delete the default cube\n2. Add a plane\n3. Add a vertex group to the plane\n4. In edit mode, assign a weight of 0.1 to all vertices.\n4. Add a hair particle system\n5. Set the hair length to 1m\n6. Assign the vertex group to control hair length\n7. In side-on orthographic view, observe that the hair length is slightly less than 0.1m.\n\n[Hair Length Vertex Group Bug.blend](Hair_Length_Vertex_Group_Bug.blend)", "GPU Hair Rendering Bug - \"Glitter\" with particular Root to Tip sizes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIn a perfect storm of GPU rendering + Hair with Radius Root size smaller or equal to the Tip size, bright white \"cards\" appear at the tips of some hair strands. \n*Switching to CPU rendering, the anomalies go away.*\n\nAlso, making the Root size Large and the Tip size small reduces the cards, but they are still there.\n\n\n\n\n[Hair Render Bug.zip](Hair_Render_Bug.zip)\n\n\n\nOpen the attached file in Blender 2.80\nSwitch to the Camera view if not already there\nRender (should be set to *Cycles using GPU*)\nSwitch to *Cycles using CPU* rendering\nRender\n\nOptionally:\n\nSelect the hair object (eyebrows)\nGo to the particle tab\nUnder Hair Shape, change the Radius Root to, say, 0.45 and the Tip to 0.1\nRender using GPU - cards are still there but are much smaller.\n\n", "Drawing size of particles not matching DPI\nOperating system: MacOS\nGraphics card: AMD Radeon Pro 450\n\nBroken: 2.83\nWorked: N/A\n\nWhen moving the blender window to the external monitor, the halo size of the particles changes, which can cause them to disappear.\nBest way to see what I mean is to watch this short clip of me moving the window, and also zooming in and out to show that not all colors are lost: Vu6MSHVxEUwYLvob8\n> In #82238#1283352, @jenkm wrote:\n> The problem here is with the `U.pixelsize` or something like that, as usual.\n> \n> When you move a window between Low and High DPI screens, the size of the spheres does not change correctly.\n> It seems that the size changes twice, like the UI scale plus the size of the spheres additionally.\n> \n> | Low DPI Screen | Moved to High DPI | Low DPI with Thick \"Line Width\" |\n> |  |  |  |\n> \n> And further, depending on the size, these spheres can be hidden by a mesh.\n> \n> | Thick | Default | Thin |\n> |  |  |  |\n> \n> The size of the spheres should not depend on `U.pixelsize`, first of all.\n> The visibility of these spheres also depends on the viewing angle, what is also not clear whether this is intentional or not.\n\n\n- Open attached file\n- Update the particles if needed\n- Move the window to another monitor with different DPI\n||\n| -- | -- |\n[particles.blend](particles.blend)\n\n---\n**Complex file:**\n[rain.blend](rain.blend)", "Area light resize gizmo (amongst other gizmos) missing undo step?\nOperating system: Arch Linux\nGraphics card: GTX Titan\n\nBroken: 2.81.3 (232049dd9408)\n\n\nSeems an area light resize in the 3D view is not registered with the undo system. \n\n\n1. Add an area light to the scene\n2. Grab and move somewhere else\n3. Change size with widget\n4. Ctrl-Z\n5. The light is now back at the origin with the default size\n\nNote that when changing the size using the properties panel an undo *will* work correctly, i.e. only change back the size.\n\nThis seems true for a couple of Gizmos [not adding an undo step -- or at least not working correctly / as expected]\nThese are the ones I quickly checked:\n- Camera Focal Length\n- Area Light size\n- Spot Size\n- Wind Force Field Strength\n- Reference Image size\n- Compositor Backdrop\n- Reference image size and move\n", "Blender development todo list -- Tools (migrated from wiki)\nNOTE: this is a direct dump of Tools (without cherrypicking the valid items)\n\n\n# Scene\n\n**New scene - Full Copy**\nSeveral things are still not copied or reassigned when using this tool:\n- [ ] Particles - Not even the particle systems themselves, not to mention re-assigning 'objects' pointers to copied IDs too, see #40891.\n- [ ] Textures when they are only used by e.g. modifiers (i.e. not by a material, world or lamp).\n- [ ] Textures used by modifiers are not re-assigned to new copies when possible either (only objects are handled).\n\n# Library System\n- [x] Hard (or even impossible) to relocate libraries that have been moved (#44958). Addressed in id-remap branch, hopefully merged in 2.78.\n- [ ] 'Find Missing Files' does not work with .blend lib files (impossible with current master, easy to do once id-remap is merged, see #47774).\n\n# Transform\n- [ ] API and draw code for manipulator needs to be redone still. For this reason no manipulator drawing happens during transform.\n- [ ] Manipulator click behavior (left-click-release a manipulator axis to enable a transform on that axis -> perform transform and wait for another left-click to confirm. Expected behavior from 2.4x)\n- [ ] Operator parameters in toolbar don't have to be drawn all always, needs cleanup.\n- [x] Transform redo fails when you change mode during transform (use R S G keys).\n- [x] Mirror of rotated objects doesn't always work correct #37928\n- [ ] Numeric input for rotational transform resolves to modulo 360. Should it? #40167 - ''possible fix included''.\n- [ ] Transform along the axis does incorrect axis projection in certain circumstances #40893\n- [ ] Scaling from zero is not possible with 'S' shortcut (#44551).\n- [ ] Transform redo fails when mouse move is required (#50419).\n- [ ] Apply Scale: Option not to scale all object properties (curve radius, empty scale, text scale... etc). \"Scale Properties\" toggle.\n- [ ] Cursor input to calculate rotation can accumulate a small amount of error (impacts bend and rotate) #53590\n- [ ] Armature edit-mode transform proportional editing doesn't work (#53992).\n\n**Transform Snap**\n- [x] Snapping to vertex slide (Taking into account multiple selections)(#48927).\n- [x] Snapping to face local axis doesn't snap the vertex to the face surface (#38438).\n- [ ] Snapping to self doesn't work with proportional edit-mode (#44793).\n- [ ] Snapping doesn't work for Boolean modifier (#35023).\n- [x] Snapping in object mode rotates object around their origin, instead of rotating them around their snapped point (#42362).\n- [ ] Snapping doesn't behave as expected when having several parented objects (#41199).\n- [ ] Snapping between multiple objects can give some working-as-intended, but in practice quite undesirable behavior (using bounding box) (#47171).\n- [ ] Snapping falls back to using a grid, however this isn't clearly communicated<br>(advanced snapping on faces, vertices, etc. only works on move/rot/scale, see #42798).\n- [ ] Snap to cursor and snap to grid could be made to work more consistently: See (#34441)\n- [ ] snap_project individual element on surface of other objects - watch?v=XrEPpHGoKlk&feature=youtu.be&t=1m10s;\n- [ ] Snap does not work for NURB surfaces (#78434);\n\n# DupliObject\n- [ ] There is no good way to control the rotation of objects in DupliFaces option (rotation is computed from face normal (which is good) and first three vertices of the polygon (which is weak, epic fail with e.g. Mirror modifier). See #37365.\n- [ ] Duplifaces don't work well with the mirror modifier, see #37820.\n\n# Curves\n- [ ] Capping front / back -ends of beveled curve doesn't work, see #26136\n- [ ] Constructive modifier kills generated UV mapping on bevelled curves, see #27411\n- [ ] Surfaces Make Segment rotates U/V even when it's not actually needed, see #31480\n- [ ] Couldn't cycle through vertices with the same location using mouse selection, see #36760\n- [ ] Curve tessellation might work not as it's expected to, see #37386, #40171\n- [ ] Curve deform doesn't work if curve is zero-scaled #38907\n- [ ] Nurbs clamp order by total number of points, this should be clamped at runtime #40378\n- [ ] Handling of non-smooth control points with (Bézier/poly) curves in general, and their rotation in particular, could be improved when generating BevelList & Path, see #44393.\n- [ ] In some cases Bevel should prefer \"clip\" behavior over trying to keep constant shape across the path #50720.\n\n# Text objects\n\n- [ ] Font formatting interface should be improved (#49599)\n- [ ] Default Bfont doesn't support russian characters (or any other non-european charset) in text object, while UI does show Russian characters (#53744)\n\n# Metas\n\n- [ ] Some shapes (Cube) for eg. draw far outside the tessellation bounds making them hard to select. see #47455\n\n# Meshes\n\n**Mesh Editing**\n- [ ] Knife & loopcut\n - [ ] Knife/loop cut need to work properly with operator properties/redo\n - [ ] Restore Quad Corner Cut Methods (Innervert, Fan and Path) for Subdivisions and Knifecut\n - [ ] Knife cuts side-on, intersecting the entire face, could be detected and ignored #43816\n- [ ] Mirror edit mesh operator (Ctrl M) fails to flip normals leaving an incorrectly mirrored mesh (turns normals inside)\n- [ ] Add option to disable n-gons usage for tools (might be useful for some usages) (see #31268)\n- [ ] 'Checker deselect' could be modified to work in some cases where it currently fails, (see #34544)\n- [ ] Merge meshes: add option to join UVs (and other CD layers!) by names rather than index (see #36749).\n- [ ] toolbar mesh Extrude operator inconsistency (see #36977).\n- [ ] Shape keys: Enhance memory usage (not storing vcos for unchanged vertices? See blender/blender-addons#39287).\n\n- [ ] Bevel\n - [ ] Better handling of profile=1, profile=0.25, and implement profile=0 cases (see #39132 and #38458 and #40278).\n - [ ] Generalize to handle several manifold sheets touching at a point (see #34678).\n - [ ] Improve clamping code (see #38871).\n - [ ] More options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n - [ ] Treat more cases like \"pipe\" to avoid bulges (see #40258)\n - [ ] Option to have bevel not create n-gons (see bf-funboard thread)\n - [ ] Sometimes leaves degenerated geometry (#48174)\n\n- [ ] DataTransfer/Geometry Matching\n - [ ] Add 'matching' algorithms based on 'similar shape' rather than simple items proximity/raycasting (see #46762 for a usecase) - WARNING: most likely advanced, mathy project!\n - [ ] A review of islands handling could also be useful, current code is rather complex and not so efficient.\n\n- [ ] Discussion\n - [ ] Extrude behaviour on cancel, see (#23492).\n\n**Text Editing (3D)**\n- [ ] When converting beveled text into a mesh - there are many doubles.\n- [ ] Text object requires better integration with the system clipboard, #38556, #46330\n- [ ] Support font kerning (#47725).\n\n**UV Unwrapping**\n- [ ] Settings for pack margin in different operators behaves inconsistently, see detailed description: 039547.html\n- [ ] Remove doubles has an option to Merge with unselected verts, This would be very handy for welding also.\n- [ ] Detect convex mesh without seams on unwrap and print warning.\n- [ ] Unwrapping fails on a particular strange topology (#31145)\n- [ ] Unwrapping for concave polygons is badly supported #41810\n- [ ] Face/edge selection in UV Editor does not work same as in 3DView (#52276).\n\n; Not ported from 2.4x\n- [ ] Click Project from face\n- [ ] Consolidate into one image\n- [ ] Billboard render on active\n- [ ] Unwrapping could run out of stack size for tricky geometry #42524\n\n**Vertex Paint**\n\n- [ ] Undo in vertex (and weight paint) behave differently to sculpt/project-paint modes regarding undo steps #52993\n\n### Sculpt & Paint\n\n**Sculpting**\n- [ ] Check documentation and fix hotkeys which could be useful for artists (or remove redundant hotkeys and update documentation), see #26017\n- [ ] Grab + symmetry can make things shoot off more quickly than they should (strength of movement is being double counted), see #25370\n- [ ] Not all drawing modes supports PBVH drawing, see #32454, #38608, #38609\n- [ ] Not all shading modes are supported for dyntopo, see #34010\n- [ ] Hidden faces are treated as hidden by sculpt tools but when PBVH drawing isn't used, the hidden faces display (and cant be edited), see #33078\n- [ ] Multires modifiers: makes mesh invisible after leaving sculpting mode, see #36591\n- [ ] Multires sculpt: artifacts grabbing between different levels #40465\n- [ ] Dyntopo does not support restoration when aborting a stroke, see #46456.\n\n**Painting (3D)**\n- [ ] Solve projection paint issue when one vertex in a face in behind the view in perspective mode<br>index.php?func=detail&aid=26393&group_id=9&atid=498\n- [ ] Continue to unify paint modes\n - [ ] Consistent brush texture mapping across paint modes (sculpt/tex paint/proj paint).\n - [ ] Consistent brush options, eg. 'Rake' or 'Anchored' in texture paint.\n- [ ] Make paint of displacement texture apply real time on model (optional). (#24657)\n- [ ] Allow view center to work for selected/active face in WPaint mode.\n- [ ] Viewport navigation for painting modes can be improved #48113\n- [ ] Users can perform strokes which apply to a huge number of pixels (by accident) - this could be handled gracefully #52351\n\n**Painting (2D)**\n- [ ] Clone image painting should support the same translation/rotation/scale tools as stencil texture mapping.\n- [ ] Stepped lines in image editor painting, blending should use float coordinates and interpolate (#52610)\n\n\n**Grease Pencil**\n- [ ] Default attach point of GP data is confusing ((#21969))\n- [ ] GP ignores color management ((#50149))\n\n### Materials\n- [ ] Improve handling of linking of materials to Object/Data. Right assigning a material-less data to object the materials from object are gone too (blender/blender-addons#23805, #52484).\n- [ ] Fix EnvMap update, it can depends on many different things in the scene (#41900).\n\n### Modifiers\n- [ ] Make (at least some) generative modifiers to handle custom normals (like e.g. mirror one, see #44058).\n\n**Array Modifier**\n- [ ] Has been re-written to use bmesh, making 2.63 slower then 2.62, There are areas where speed could be improved, for full info see #30695\n- [ ] Textures from cap objects are completely ignored and no way to override them, see #33578\n\n**Boolean Modifier**\n- [ ] Boolean modifier does not preserve vertices/edges data, see #32203, #33548\n- [ ] Issues with degenerated faces, see #30447\n\n**Decimate Modifier**\n- [ ] Limit decimation along seams (UV vertex color, etc), see #32203\n\n**Explode Modifier**\n\n- [ ] Does not preserve UV maps when using Cut Edges option (#46514)\n\n**Multires Modifier**\n- [ ] Only solid draw mode uses optimized drawing\n- [ ] \"Applying Base\" gives spikes on lover levels sometimes, see #35560, #37997\n\n**Bevel Modifier**\n- [ ] Does not preserve edge custom data, see #35314.\n\n**Simple Deform Modifier**\n- [ ] The bend/taper/twist options use fixed axis, add XYZ options would be nice. #33712\n\n**Skin Modifier**\n- [ ] Skin modifier very slow in some cases, see #40770\n\n**Solidify Modifier**\n- [ ] Curves tesselation creates zero area faces which solidify doesn't handle well #52170\n\n**Remesh Modifier**\n- [ ] Mesh data at extreme distance from origin (2**24), crashes #47209<br>''Note, this is a real corner case - yet its a bug because it shouldn't crash.''\n\n### Physics\n- [ ] Allow using multiple baked caches on a single object (having different frame ranges), see #41896.\n- [ ] Bullet: High memory usage for objects that don't have scale applied (#35799)\n\n**Baking**\n\n- [ ] Generic issue: baking ignores making pointcaches when modifier preview has been disabled. Doesn't need fix - but let's keep track of this for future work.\n- [ ] Point caches do not work well with time remapping (example #35968)\n\n**Cloth**\n- [ ] Proper handling of rendered subframes without baked pointcache, for more info see (#21948)\n- [ ] Proper handling of different vertices placed at the same position with \"Soft Body Self Collision\" option turned on (see (#26956)).\n- [ ] Cloths doesn't allow preview during bake (see (#30490)).\n- [ ] Dupli-group cloth in NLA fails (#29838)\n- [ ] 'Emit from: verts' not working as expected when deforming #36237\n- [ ] Collision of hairs doesn't works properly #39219\n- [ ] Memory optimizations are possible for cloth #42577\n- [ ] Cloth pre-roll feature is totally weird and needs reconsideration #40103\n\n**Collisions**\n- [ ] Collision modifier updates it's data structure even if there are no physics that need it (can be slow), a check should be added to make sure the data is actually needed, see (#26965).\n- [ ] Force fields and collision objects are not included in DupliObjects. This is mostly a design decision (duplis being a purely visual feature), but would be nice to support at least in groups. #35264 #36300\n\n**Hair**\n- [ ] Better handling of collisions & force fields for dynamic hair\n- [ ] Wave kink direction is totally uncontrollable, probably there needs to be a way to define hair tangent direction in particle edit mode.\n- [ ] Adding hair in particle mode only uses the deformed mesh, see (#25689).\n\n**Particles**\n- [ ] Particle emission between frames is only accurate for object level emitter/parent animation, for parenting or constraints an interpolation method needs to be implemented, but before this can be done pointcache code has to get some changes too. See (#36516) for more details.\n*; Parent animation is now supported {{GitCommit|c24a23f. Similar issue still persists for non-animated parents (e.g. rigid bodies) though #39923\n- [ ] Reactor particles\n- [ ] Conversion from some old files could be better\n- [ ] Vector blur + particles being born/dying doesn't work properly, see (#23320).\n- [ ] Metaballs don't work with particles when the particle view setting isn't \"render\", see (#25794) for more info.\n- [ ] \"Constructive modifiers before particles\" is still an open issue, but some way to handle this gracefully would be really nice, see (#25838) for more info.\n- [ ] Density of particles can't be animated with animated textures, see (#28212).\n- [ ] Instanced objects do not show in particle edit mode, see (#28431).\n- [ ] Issue with ghosting particles if you don't bake first. (#28116)\n- [ ] Linked groups: Force fields and guides only work if you use \"Effector Group\" feature, set to its own group.\n- [ ] Particle Hair dynamics: stops working after using \"Add tool\". (#30557)\n- [ ] Instanced objects don't draw in Particle Edit Mode. (#31913)\n- [ ] Child particles Interpolated mode only works well for Hair, for other particles it doesn't take particle lifetime into account. (#33390)\n- [ ] Particle emission doesn't support NGons.\n- [ ] Particle Object duplication doesn't work with Mirror modifier (#34705)\n- [ ] Particle systems fail to duplicate for smoke simulation (#34705)\n- [ ] Random distribution of particles fails in specific setups (#35598)\n- [ ] Default point cache step of 10 frames fails in some cases, see #38563\n- [ ] Particles tangent rotation control by vertex group missing, see #35103\n- [ ] Texture doesn't affect grid particles #40404\n- [ ] The particle system needs to be set to 'Newtonian Physics' for texture to influence the size, and with global gravity turned off #28263\n- [ ] Multiple issues with particles rotation #32340, #44088\n- [ ] Particles hidden in viewport reappear during rendering #40463\n- [ ] Particle initial speed is not properly inherited from the parent #41305\n- [ ] Point density textures can not be used to control particles #44901\n- [ ] Particle duplication in general is rather poorly implemented (no relink of used datablocks, no duplication of psettings ID when duplicating objects, …) #45843.\n- [ ] Grid distribution only supports From Dupli Generated, but not UV. Potentially could use nearest face. #48928\n- [ ] Particles aren't spawned correctly, they are sometimes generated at the same location as other particles, or at the object's origin. See #50135 for one scenario.\n- [ ] Particle editmode could have its 'own' [X-mirror] option (and not reuse editmode option). See #53872\n\n**Rigid Body**\n- [ ] Velocities are not cached, which prevents a proper state update when cache has time gaps #50230.\n\n### Image & Video\n\n**Compositing**\n- [ ] DOF Defocus node: fStop close to 128 fails to give good results, stay away from that value! (#24534)\n- [ ] DOF node gives no realistic results as users expect, documentation needs upgrade for it.\n- [ ] Defocus node is very slow when large blur radius is needed, could be optimized somehow (mipmap, summed area table?) (#29481)\n- [ ] Defocus node does not work nicely without a camera controlling the blur radius. This makes external compositing workflows with defocus difficult. At the heart of this is a design conflict, because defocus is not a true postprocessing effect #36745\n- [ ] Fast Gauss (Gabor filter, Young/VanVliet) has bad results for edge cases. Needs image processing guru (#25543)\n- [ ] Check on DPX and ASC_CDL and (#27377)\n- [ ] Map UV makes mapped images blurry, see #31868\n- [ ] Some nodes does not preserve alpha channel replacing it with fully opaque, see #32580\n- [ ] With new compositor, on loading files a compositor doesn't start (for existing buffers), so viewers remain empty as well. #35417\n- [ ] Ghost Glare is of limited use, needs clarification and probably a more sophisticated generic lens flare alternative #30389 #36488\n- [ ] Some node inputs require a single constant value and don't work with image-based per-pixel values (#36585). This leads to confusion when nodes apparently don't work, because nothing prevents linking such variable values into constant inputs. Compositor nodes should keep track of constant values and limited inputs on the node level (also in node groups!).\n- [ ] Compositor gives unexpected results with specific curve mapping due to precision loss, see #36621\n- [ ] \"Full Sample\" merging does not work with the File Output node, sample merging happens only for render result outside compositor. Real-time editing might also be improved to deal with samples better (#36811, #39143)\n- [ ] Accumulation method in the Lens Distortion node causes artifacts on noisy input #37462\n- [ ] Compositor does not support render slots #43260\n- [ ] Scaling down produces artifacts due to lack of ellipse filtering of sampler #51070\n\n**Image formats**\n- [ ] Upgrade our DPX code to read newer or different versions, copy the ImageMagick code? (#24716)\n- [ ] No support yet to output images in user chosen color space. (#37650)" ]

[ "2.79a Particle System: Random Size and Rotation not available at same time\nOptions to randomly (1) rotate and (2) scale particles should be available at the same under Hair particles. This is not the case, starting with 2.79a.\n\nI believe this is a showstopper for those that use the Particle System to do such things as randomly scatter objects such as plants/grass/rocks over an area.\n\n\n\n\n\nSystem: Windows 10/64bit" ]

[ "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.", "Force field can't expand smoke evenly.\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 650 Ti\nProcessor: Intel® Core™ i7-3770\n\nBroken: (2.83 Beta, 8956e9e5f6c0, 2020-05-11 19:18 )\nWorked: (never)\n\nBlender smoke can't expand in all directions evenly.\nThe video below shows two situations: one where particles are emitted in an omnidirectional fashion, and one where the \"Force\" force field is used to push the smoke outwards.\n[ExpansionDemoC.mp4](ExpansionDemoC.mp4)\n\n**Exact steps to reproduce the error**\n[Spherical Expansion (Force).blend](Spherical_Expansion__Force_.blend)\n\n1. Add a sphere.\n2. Press F3 and select Quick Smoke.\n3. Add a \"Force\" force field in the center of the sphere.\n4. (optional) Set Buoyancy Density and Heat to zero, to ensure that the only movement the smoke has is the push from the force field.\n", "Displacement textures rendering incorrectly when viewed through/near volumetric shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\nGraphics card secondary: NVIDIA GeForce GTX 1070\n\n\nBroken: version: 3.2.0 Alpha\nI originally ran into this issue on 3.0 a few weeks ago. I tried it on the public release of 3.1 and encountered the same issue. Today I have reproduced it on 3.2.0. I do not believe this has ever worked.\n\nWhen rendering a view of a smoke simulation (or any volumetric shader) where the material on the far side of that simulation/volumetric uses displacement, there seems to be an effect surrounding and inside the volumetric which causes the displacement texture to jitter, its reflections rapidly altering between frames causing an appearance almost like the texture/object or light source is vibrating/moving. The effect, when viewed on small smoke simulations, appears almost like heat distortion and may be useful for achieving that effect in other desired scenarios. When viewed through large volumetric shaders (such as fog) it creates an effect over the entirety of the object using displacement and is very distracting.\n\nFrom a default Blend, create an object. On this object create a texture that uses displacement and has displacement & bump truly enabled. Then, run a smoke simulation either via a quick smoke or particle simulation or, create a large object that then uses a displacement texture. Then render the scene such that the object with the displacement texture is on the far side of the smoke simulation/volumetric object. A well-lit environment, dense smoke, and a complex texture (high scale noise for small fine displacement/bump details) that makes use of glossy areas will make the effect easier to see. Disabling/removing displacement from the texture (and disconnecting the socket) will correct the issue at the cost of loss of displacement.\n\n\nThings I have tried to get around this problem:\nI have drastically increased, decreased, enabled, or disabled, the following settings to no avail.\nWith regards to the domain:\n- Adaptive domain\n- Noise\n- Empty space: higher values (up to 1.0) did seem to have an influence on the size of the distortion area but could never eliminate it. \n- resolution divisions\n- time scale minimum\n- precision volumes\nWith regards to the smoke texture:\n- Sampling\n- interpolation\n- homogenous\n- step rate\nWith regards to rendering:\nOptix denoising and openimage denoise - I will attach an example of each.\nvery high samples\nI also made sure/tested a domain and/or smoke which does not pass through the surface or near the actual surface of the displacement texture. \n\n - attaching several GIF examples at lower framerate playback.\nI believe the jittering in the full foggy stadium in the reflection of the moon and distance areas when displacement is off is simply due to the lower samples I used for that test render.\n[Bug.blend](Bug.blend)\n\n\n\n\n\n\n\n\n\n[31 displacement issues.mp4](31_displacement_issues.mp4)", "Adaptive Domain creates lines in smoke\nOperating system: Win 10\nGraphics card: Dual RTX Titans\n\nBroken: Blender 2.82\n\nWith adaptive domain enabled, noticeable horizontal (and sometimes vertical) lines appear in the smoke\n[weird lines.mp4](weird_lines.mp4)\n\nSimple blend file: \n\n - Create a large box and set it as a gas domain.\n - Create a small object as the Flow (both 'smoke' and 'fire' reproduce it)\n - Put the flow object near the bottom of the domain\n - Enable Adaptive Domain\n - Bake\n - You should see lines like this: \n # Turn off adaptive. Not only will the smoke move faster creating a totally different looking simulation (which is problem in itself) but the lines will be gone: \n\nIt's most noticeable when the domain is large, and the adaptive box is only a small portion of it.\n\nIncreasing the adaptive margin to 24 helps somewhat, but it's still there. Any higher and it defeats the purpose of adaptive - baking takes as long as just turning it off.\n\nSample blend:\n[adaptive bug2.blend](adaptive_bug2.blend)", "Blender Mantaflow gas fire and smoke simulation - Adaptive Domain problem!\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nTHE SAME BEHAVIOUR FOR Blender versions 3.3.1 and 3.4.1.\n\nAdaptive Domain from time to time shrinks as intended, but those shrinks are sometimes visible.\n\n\n- Open [file](https://projects.blender.orgattachment)\n- Bake 180 frames\n- Check frames 173 - 178\n\nDomain shrinks while space is occupied by smoke with substantial density", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Eevee viewport soft shadows are broken on higher sample count\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: ---\n\nEevee soft shadows in viewport have color spills. But it works fine on final render (F12)\n\n\n\n- Open .blend file\n\n[bug_soft_shadows.blend](bug_soft_shadows.blend)\n\n- Switch to Rendered Mode of Viewport Shading\n- Wait half a min and see the problem(", "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.", "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", "Crashing while viewing animation in Cycles\nOperating system: macOS-13.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.4.0\n\nWill crash seconds after playing animation in viewport when Cycles is selected and in render view. Both CPU and GPU crash. Does not crash when removing the Subdivision Surface Modifier so polycount may be a factor? This is a brand new Apple M1 Max computer from BestBuy with nothing else installed. Also tried initializing a render to video file and crashed as well. (Note: This is an error strictly with Apple M1 computers as I have tested it on an Apple intel MacBook Pro and it works just fine.) Thank you and happy holidays!\n\n1. Load file. It is a mesh plane with default cloth and subdivision modifiers acting on a wind force.\n2. Make sure Cycles is selected as Render Engine.\n3. Select Viewport Shading to Rendered (to view cycles render)\n4. Push play. Will crash or freeze seconds after play.\n\n[Cloth_Cycles_Crash.blend](Cloth_Cycles_Crash.blend)\n\n[Blender 3.4 Crash Report 12.13.22.rtf](Blender_3.4_Crash_Report_12.13.22.rtf)\n[Blender 3.5 Crash Report 12.14.22.rtf](Blender_3.5_Crash_Report_12.14.22.rtf)", "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.", "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", "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 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", "Mantaflow: Minimum timesteps affects dissolve rate\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.2 26.20.15019.19000\n\nBroken: version: 2.91.0 Alpha\n\nI was testing the dissolve feature described [here ](settings.html#dissolve). Time: \"Speed of smoke’s dissipation in frames.\" but it seems wrong. Let me show this short video (don't look at my test about flow consistency in domain settings):\n[0000-0150.mp4](0000-0150.mp4)\nAs you can see, changing the Maximum Timesteps does not change the Dissolve velocity, even changing the substeps of the inflow object doesn't change the dissolve behaviour.\nBut changing the Minimum Timesteps (forcing mantaflow to iterate more on each frame) it clearly messes up the behaviour. It seems to act faster than desired! It seems the Dissolve Time parameter works on steps and not frame.\n\n[MineExplosion.blend](MineExplosion.blend)\n\nBake simulations and play animation.\n" ]

[ "Smoke Simulation crashes on eevee and is not persistent on Cycles\nOperating system: Windows 10 64bit\nGraphics card: gtx 950\n\nBlender 2.82a (00:40 Uhr 03.19.2020)\nA smokesimulation wont stay after the last simulation frame ends.\n\n- Open the attached file, bake data.\n- render frame 1-3 -> smoke\n- render frame 4-5 -> no more smoke\nIf you render in Eevee it crashes\n[#74901.blend](T74901.blend)\nIm not entirely sure if this is considered a bug, but if I remember correctly this wasn't the case in older blender versions.\nIf this is ment to e this way you would help me with a workaround." ]

[ "Eevee: Soft shadows causing flickering in animation and temporal AA in scenes\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.80\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nEevee soft shadows in objects with thin reflections causes flickering in animation and temporal AA in still images. This type reflections common in interior Arch Viz.\n\nScene 1 example of flickering of soft shadows in animation. I have remove all light probes and effects to focus only light and shadows. Open attach file \"Scene1_AA_eevee.blend\".\nRender the animation with Soft Shadows ON. Then Render animation with Soft Shadows OFF.\n[Scene1_AA_eevee.blend](Scene1_AA_eevee.blend)\n\nAnimation with Soft Shadows ON. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_eevee.mp4](Scene1_AA_eevee.mp4)\n\nAnimation with Soft Shadows OFF. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_No_SShadow_eevee.mp4](Scene1_AA_No_SShadow_eevee.mp4)\n\nAnimation in Cycles for comparison. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_cycles.mp4](Scene1_AA_cycles.mp4)\n\n******************************************************************************************************\nScene 2 example of temporal anti-aliasing cause by soft shadows. I have simplify the scene 2 to focus only light and shadows. Open attach file \"Scene2_AA_eevee.blend\".\nRender Image with Soft Shadows ON. Then Render Image with Soft Shadows OFF.\n[Scene2_AA_eevee.blend](Scene2_AA_eevee.blend)\n\nRender image with Soft Shadows ON. Make sure to view at full size. Notice the temporal AA on the edges on horizontal counter, vertical counter, oven handle and oven racks.\n\n\nRender image with Soft Shadows OFF. Make sure to view at full size. Notice the temporal AA is gone.\n\n\nRender image with Cycles for comparison. Make sure to view at full size.\n\n\n", "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", "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", "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", "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.", "GPencil: Airbrush draw tool with solid stroke has transparency artifacts\nOperating system: Win 11, GTX 3080, Wacom Tablet\n\n\n\nBroken: 2cd7e70c18a8\nWorked: ~~3.3.0~~\n\nThe airbrush tool has artifacts around the stroke during drawing. Also what is drawn during stroke has nothing to do with the final result visually. Please see the video for the issue.\n\n\n\n- New scene -> 2d Animation\n- Select Airbrush tool from the tool pane\n- Switch to `solid stroke` material from header\n- Draw\n\n[image](attachment)\n[blender_lOlSgoorkK.mp4](attachment)\n", "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.", "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)", "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", "Vertex slide (GG) acts weird with zoom (steppy, jumping, not slowing down with shift)\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.19\n\nBroken: version: 2.82 (sub 7)\n\n\n[2020-02-22_06-30-18.mp4](2020-02-22_06-30-18.mp4)\n\n[gg.blend](gg.blend)\n\n", "Light Linking Misaligned Mouse Cursor Position\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.98\n\nBroken: version: 4.0.0 Alpha\nWorked: Don't know\n\nWhen toggling on/off light linking items, the mouse cursor position seems to be misaligned, so you end up toggling the item on top of the one you are hovering over.\n<video src=\"attachment\" title=\"2023-07-21 22-38-23.mkv\" controls></video>\n\n- Create new project\n- Create few objects\n- Add a light\n- Select the light and go to light linking settings\n- Select collection from the drop-down menu to get all the objects in the linking menu\n- Try to click the “lightbulb” icons to turn off light linking objects.\n\nYou should notice that clicks are detected 1 item higher than you are pointing.\n\n", "Curves don't have 'All Edges' option for wireframe\nBroken: 2.80\n\nMesh objects have the toggle for its viewport display wireframe to render all edges, but curve objects don't.\n\n\nOpen the attached file and look for the 'All Edges' option.\n[Wiref.blend](Wiref.blend)\n", "Grease Pencil: Better render Anti-Aliasing\n## Motivations:\nThin lines are correctly rendered using grease pencil with the currently implemented post process Anti-Aliasing. This is done by making sure the line width is not less than 1.3 and by modulating its opacity.\nHowever, there is cases where this is not enough. For instance really dense drawings with small lines with little to no curvature still tends to flicker a lot.\nAnother case is when the gpencil strokes intersects the scene geometry. This makes the line less thick to the post process which makes it too small.\n\n## Proposed solution:\nWe propose to implement a Temporal AntiAliasing solution. It is robust and will match Cycles & EEVEE's film filtering if using the same filtering function. This only adds one temporary buffer (low VRAM usage compared to rendering at higher resolution) and is completely self contained (works with transparency and don't interfere with other features).\n\nI propose to only implement this for final rendering since it might introduce flickering that might be annoying while drawing.\n\nHowever this wouldn't solve the issue of gpencil strokes intersecting geometry.\nFor this I propose to erode or reproject the render's depth to match the render sample of the new AA scheme. This should fix the second problem completely.\n\n## Technical details:\n- Implementation just need to be ported from Workbench which has a lighter form of TAA than EEVEE. Also [D10414](D10414) can be of great help to reduce render/convergence time.\n- Depth buffer modification can be implemented after new AA is in.", "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)", "The viewport may update at 0 FPS while navigating, until the mouse is released.\nOperating system: Windows 10\nGraphics card: RTX 3080 Ti\n\nBroken: 3.0.0\nWorked: 2.92.0\n\nWhen working in sculpt mode on a model with multires modifier, the viewport may update at 0 FPS while navigating, until the mouse is released.\n\nUsually when navigating in sculpt mode on a model with multires modifier, the model will switch to a low poly version while navigating. When this bug is happening, the viewport remains frozen and the high poly model remain on screen until mouse is released.\n\nThe bug will be temporarily fixed upon clicking on another application or resizing the blender window.\n\n1. Shift+A to create a plane\n2. Ctrl+E and subdivide it 4 times.\n3. Attach multires modifier onto the plane.\n4. Subdivide it 6 times with the multires modifier.\n5. Use sculpt mode and sculpt without moving the view for around 1~2 minutes (I used a wacom tablet. Using the sculptDraw brush, I added / subtracted (hold ctrl) from the mesh, also using smoothing brush (hold shift) to smooth certain parts, and undo (ctrl + z) multiple times to simulate a normal working environment.)\n6. Try to pan or rotate the view around.\n\n\n\n**I found another way to trigger this bug, and it's not strictly related to sculpt mode.**\n(Tested on blender 3.1.0 beta 03b57d3973)\n\n1. Click around with a Wacom tablet.\n2. Pan the camera around with a Wacom tablet.\n3. Pan the camera around with a mouse.\n\n\n[sculpt mode bug.blend](sculpt_mode_bug.blend)\n\n[2022-01-17 04-48-11_Trim.mp4](2022-01-17_04-48-11_Trim.mp4)" ]

[ "Wireframes & 3d Cursor Bug.\nOperating system: Windows-10-10.0.1709 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.34\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nWhen wireframes on and dragging the 3d cursor you get this flickering and sometimes wireframes disappear completely.\n\n- Enable Wireframes on top.\n- Select 3d cursor and click & drag, happens for both Selected and Unselected meshes.\n\n**Demo**\n{[F7746040](wire.gif) size = full}\n\n" ]

[ "Grease Pencil - Straight line at beginning of stroke\nOperating system: Mac OS Mojave\nGraphics card: Intel UHD Graphics\n\nTablet: Wacom Cintiq\n\nBroken: 2.83.0\n\nWhen making fast strokes, there is delay that causes a straight line. Most noticeable when drawing quick circles. It seems to be there's a delay between starting the cursor pressing down and starting the stroke.\n\n\nBased on the default startup, adjusting setting doesn't change the behaviour. The straight line is present with all brushes.", "Text fields don't allow to enter language specific text like Umlauts \"öäü\" on X11\nOperating system: Linux-4.18.0-15-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.77\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\n\n\nVSE\nSHIFT-A->Text \nTry to enter special characters -> Nothing\nOnly Linux (see above)!\n\nHowever: Copy&Paste works!\n\n", "Subdiv hangs blender\n**System Information** DESKTOP-HR30UII\nOperating system:Windows 11 Home Single Language\nGraphics card:2GB NVIDIA GRAPHICS DRIVER\n\n\nBroken: Blender Version 3.5\nWorked: ?\n\nBLENDER 3.5 KEEPS NOT RESPONDING WHILE I USE MODIFIERS \n\nON BLENDER ADD MESH AND ADD MODIFIERS TO SUBDIVISION SURFACE THEN CHANGING THE VALUE OF LEVELS VIEWPORT VALUE ABOVE 4 .THEN ONWARDS BLENDER COMPLETELY STOPS WORKING AND I NEED TO RESTART IT AGAIN\n\n", "Blender freezes after scrubbing timeline or changing keyframe value\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.0\n\n\nAfter playing the timeline, or moving the play head, the system seems to pause for about ten seconds and won't register selections in the viewport, data boxes, or selecting a keyframe in the graph editor. If you did try to click some things and move them, suddenly they will register as selected and all the mouse movements you made get piled on all at once.\n\n\n- On \"Sc6\" or \"Sc2-5\", scrub the timeline then try to select anything, especially key frames in the graph editor\n\n", "Moving cursor quickly jumps it out of the window when translating objects\nArchlinux\nNvidia GTX 460\n\nBroken: 2.7 RC1\n\nIt's possible to escape the window by moving the mouse quickly while translating an object. This does not seem to be possible while moving the view.\n\n1. Open blender in windowed mode with some space at the top of the screen\n2. Open default startup file (load factory settings)\n3. Select the default cube and press G+Z, then move the mouse sharply upwards as fast as possible (I don't actually need to move it that quickly, it's happened several times by mistake. But just to be sure.). The cursor will escape the window (will not wrap).\n4. Try the same with rotating the view (press and hold MMB, move mouse upwards quickly). The cursor will not escape, even when going at least as fast as when translating objects (sometimes the cursor will appear outside the window, but it still wraps).\n", "Keep Alt Key not work in the F-Curve properties\nwin10 64bit, gtx1060\n\nBroken: 2.79a 8928d99270f\nWorked: (optional)\n\nKeep alt key for multiple objects not work in F-curve property ( N panel )\n\nOpen my .blend file, when I select multiple curves and keep alt key to twice the Interpolation or Easing option, it's just worked in one cure,not for all selected, if this is bug, please fix, it very useful for lots curves, else I must one by one to change those, thanks.\n\n\n\n[bug.blend](bug.blend)", "Blender ignores xinput mouse sensitivity (as a result, mouse cursor randomly jumps when I attempt to navigate, move objects, etc.)\nLinux, Debian Sid, GTX 680\n\nThis is what happens: if mouse sensitivity is default, everything works fine. If mouse sensitivity is, for example, 0.9 instead of 1, and I try to rotate view by holding middle mouse button, when I release it, mouse cursor jumps to position it would reach with default sensitivity. Automatic cursor wrapping in Blender also ignores xinput sensitivity, so if it happens, mouse cursor will jump unexpectedly even before I release mouse button. The same thing happens when I try to rotate or move objects. When sensitivity is set to low value, for example, 0.3, mouse cursor jumps to edge of the screen almost every time I release mouse button or move/rotate some object with mouse. And because of this, mouse does not wrap around from one edge of the screen to another seemlessly, it just starts behaving crazy, like rotating view at extreme speed.\n\nI have very sensitive mouse, and I cannot change its hardware sensitivity. So I have to adjust it with xinput, otherwise cursor will be \"flying\" too fast. This used to work with Blender in older distros where it was possible to adjust \"Device Accel Constant Deceleration\" to change mouse sensitivity. However, this seems to be not possible for a while now because this xinput property was removed. Instead, to change mouse sensitivity I have to adjust Coordinate Transformation Matrix. This works everywhere except in Blender. In case somebody does not know this, in Linux I have to use xinput to adjust sensitivity, because as far as I know there is no other way to do it (for example, in KDE systemsettings I can adjust only acceleration, and even if I set it below 1x, even to minimum 0.1x, it does not do much, and this is expected, since acceleration and sensitivity are completely different settings).\n\nSet mouse sensitivity to anything but 1. For example:\n\nid=\"pointer:Mouseemu virtual mouse\"; speed=0.3; xinput set-prop $id \"Coordinate Transformation Matrix\" $speed, 0, 0, 0, $speed, 0, 0, 0, 1\n\nOf course, you need to replace pointer name (text after \"pointer:\" prefix) with your own (if you do not know it, see output from \"xinput list\"). Then try to rotate view with middle button. You will see cursor to jump unexpectedly when you release mouse button or if you hit edge of the screen.\n\nAs far as I can tell, it feels like Blender always assumes default \"Coordinate Transformation Matrix\", and ignores real one. And as a result, Blender does not calculate mouse position correctly. This pretty much makes Blender practically unusable with mouse which needs xinput sensitivity adjustment. So far I was not able to found any workaround, and it is very hard to work with default sensitivity in my case. If you need more information, please let me know.", "Distribution: Jittered And Random ignore flag \"Use Modifier Stack\" PS\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\nWorked: never\n\njitter and random ignores modifier stack\n\n\n- Open default scene\n- In particle system change distribution to grid (modifiers stack appears to be included)\n- Change type to jitter/Random\n[GNParticle.blend](GNParticle.blend)\n", "Array modifier: Count value doesn't increase over 1000 when using arrow icons.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: \n3.5.1,\n3.4.1\nWorked: N/A\n\nThis is a minor bug but hopefully easy to fix:\nWhen changing the \"Count\" value in Array modifier using arrow icons it is impossible to pass a value higher than 1000, it simply doesn't change. However, any value can be set using keyboard and then the arrow icons work as intended (eg. setting the value using keyboard to 1001 enables the arrow icons to set values 1002, 1003...).\nThis seems to be happening when trying to pass over values eg. 1000, 2000, 5000. When trying to pass over values eg. 3000, 4000, 6000, 7000 the icons work as intended.\n\n1. Open blender\n2. Select default cube (or any newly created object)\n3. Go to Modifier Properties\n4. Add Array modifier\n5. Manually change Count to 998\n6. Press the right arrow icon until the Count value reaches 1000 and keep pressing to see if the value increases\n7. Manually change Count to 1001 and check if the right arrow icons changes the value\n\n", "GPencil: envelope, Multiplestrokes, Array modifiers missing with the orders of strokes.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Beta\n\ni can't use build modifier with array, envelope,multiplestrokes efficiently because the generated stokes and originals don't get well indexing( orders) to be used by build modifier. i observed the following: \n** Multiplestrokes** modifier be the last in order then the generated lines. \n**Array** modifier and **Envelope** modifier don't have any predictable indexing (order) of strokes and all the time makes the original strokes the last in order. see the video\n\n", "Multiple Edge Loop Selection doesn't always work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0\nWorked: 3.3\n\nMultiple Edge Loop Selection (Shift+Alt+Select) will sometimes stop working until Shift is released and depressed again. Problem started in Blender 3.4 and did not exist in Blender 3.3 (tested).\n\n\n- Create a cylinder primitive.\n- Enter Edit Mode.\n- Attempt to Edge Loop Select multiple edges by holding Shift+Alt and clicking on them. Occasionally, this function will simply stop working after the first few selects -- no more edge loops can be selected -- until Shift is released and depressed again.\n\nThis problem does not occur for general multi selection (when only Shift is held).\n\n", "Dynamic Paint evaluated even when disabled\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.04\n\nBroken: version: 3.3.1\nWorked: (Unknown)\n\nAfter disabling the Viewport Display and Render options for both the Canvas and the Brush in the Dynamic Paint settings, the system continues to be evaluated during timeline playback, resulting in a very low frame rate. The only way to fix this is to completely delete the **Dynamic Paint modifier** from **both** the Canvas **AND** the Brush. This is not ideal, as settings need to be tweaked in between testing an animation, so the system **should be properly bypassed** when the Viewport Display and Render options are disabled.\n\nThanks very much for looking into this!\n\n**[exact steps needed to reproduce the issue]**\n\nPlease see example .blend file. The landscape mesh is used as a proximity brush to paint \"shoreline\" interaction onto an animated canvas. The project exhibits the same low frame rate even when the Dynamic Paint modifiers have their Visibility and Render settings disabled. Only by completely deleting the modifiers, does the the frame rate return to normal.\n\n\n\n[DYNAMIC PAINT TEST FILE.blend](DYNAMIC_PAINT_TEST_FILE.blend)\n\n", "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", "Autokey function hinders execution of drivers\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.0.1\nWorked: Never (2.80+)\n\n- Open General template\n- Enable auto-keyframing in preferences for new scenes\n- Create new scene\n- Add cube\n- To Location X type `#frame`\n- Scrub timeline\n\nDriver won't update\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" ]

[ "Last character typed on keyboard is not taken into account when typing fast three characters with the third character being the same as the first one\nOperating system: Windows 10\nGraphics card: 4090 RTX\n\nBroken: 3.2\nWorked: never?\n\n**Description**\nIf I go in any text field and quickly press 121, aza, or whatever with the same third character as the first one, it is not taken into account in the field. The result in the text field is 12, az...\n\nThe issue is everywhere in the software, every text field behaves like this. This is quite problematic when you want to scale something to 1.1 for example and use the numpad.\n\nNote: Tried with 4 different keyboards (two with Logitech unifying, one with bluetooth, one USB wired). All of them have the issue in Blender but work fine anywhere else.\nNo .blend file provided as it wouldn't show the issue.\n\n**Steps to reproduce**\n1. Open Blender 3.2\n2. Click on any text field\n3. Quickly type a 3 characters sequence with the third character being the same as the first one (1.1, 121, 323, aza...)\n4. Observe that the third character is not taken into account", "Regression: Touch typing in text fields results in dropped key presses\nOperating system: Ubuntu 20.04 (Gnome / Xorg)\nGraphics card: Radeon RX 5700 XT\n\nBroken: 3.3 , 3.2 release\nWorked: 3.1\nCaused by 102644cb8c\n\n\nWhen touch-typing rapidly, entering certain words will often result in dropped key presses. I discovered this issue while using the Python console; entering \"data\" would more often than not result in \"dat\" appearing in the console.\n\n\n - Select a text field in the interface, such that typing will produce text. Text fields tested include the Python Console, the Text Editor, and renaming an object in the Outliner after double-clicking it.\n - Rapidly perform the following exact sequence of key events. In testing, the bug occurs every time if I complete the sequence in less than about half a second (easy to do using one hand for A and the other for T):\n - Press down the A key\n - Press down the T key\n - Release the A key (T is still pressed)\n - Press down the A key again (T is still pressed)\n\nExpected result: \"ata\" appears in the text field.\n\nActual result: \"at\" appears in the text field. Again, this is 100% consistent when performed rapidly.\n\n**Other notes**\n\nAny choice of two keys produces the issue, e.g., \"ege.\"\n\nI know this may sound like a niche issue, but in testing, if I type \"data\" the way I naturally do into the Python Console, the bug is triggered much more than half of the time. No other software I use rejects the second press of \"A\" in this way." ]

[ "Collada export crashes (when relative \"//\" is in `Preferences` > `File Paths` > `Temporary Files`)\nOperating system: macOS 12.1\nGraphics card: M1 MBP\n\nBroken: 3.0 with the attached userpref.blend\nBroken: 2.93.8\nBroken: 2.83.19\n\n\n\nfrom factory-startup:\n\n- - [x] type `//` in `Preferences` > `File Paths` > `Temporary Files`\n- - [x] `Export` > `Collada`\n- crash\n\nnote: in a debug build, the following assert is hit after step [1]\n```\n./bin/blender(BLI_system_backtrace+0x26) [0xf4a5f1b]\n./bin/blender(_BLI_assert_print_backtrace+0x16) [0xf344596]\n./bin/blender(BLI_exists+0x2a) [0xf497c6c]\n./bin/blender(BLI_is_dir+0x18) [0xf497d21]\n./bin/blender() [0x3c2a38d]\n./bin/blender(BKE_tempdir_init+0x27) [0x3c2a5e2]\n./bin/blender() [0x4c1ec17]\n./bin/blender() [0x4a2e592]\n./bin/blender(RNA_property_update+0x50) [0x4a2e7ca]\n./bin/blender() [0x55d728b]\n./bin/blender() [0x55f3b4a]\n./bin/blender() [0x435810e]\n./bin/blender() [0x435e018]\n./bin/blender() [0x435e5cc]\n./bin/blender(wm_event_do_handlers+0x7a0) [0x435fd81]\n./bin/blender(WM_main+0x30) [0x4351d2e]\n./bin/blender() [0x3c236af]\n/lib64/libc.so.6(+0x2d590) [0x7fb0c4842590]\n/lib64/libc.so.6(__libc_start_main+0x89) [0x7fb0c4842649]\n./bin/blender(_start+0x25) [0x3c23095]\nBLI_assert failed: source/blender/blenlib/intern/storage.c:348, BLI_exists(), at '!BLI_path_is_rel(path)'\n```", "Show error messages in the info editor\nFollowup task to #83237", "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", "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.", "Python 4.0 delayed annotation evaluation (from __future__ import annotations )\n\n\nAdding\n`from __future__ import annotations`\nat the top of a python file makes the properties annotations of operators non-existent.\n\nThis will be enabled by default in Python 4.0, see: pep-0563\n\nCreate and enable this simple demo addon:\n\n```\nfrom __future__ import annotations # this line makes the line 30 throw an error, because the property some_prop of BUGANNOTATIONS_OT_some_op will no longer exist\n\nbl_info = {\n\t'name': 'Bug annotations with __future__',\n\t'author': 'Arnold, Arnaud Couturier, piiichan ([email protected])',\n\t'version': (1, 0, 0),\n\t'blender': (2, 80, 0),\n\t'location': 'scene options',\n\t'category': 'Scene',\n}\n\nimport bpy\n\n\nclass BUGANNOTATIONS_OT_some_op(bpy.types.Operator):\n\tbl_idname = 'scene.hey'\n\tbl_label = 'An operator'\n\tsome_prop: bpy.props.StringProperty(name='Hello', default='Default value')\n\n\nclass BUGANNOTATIONS_PT_some_panel(bpy.types.Panel):\n\tbl_region_type = 'WINDOW'\n\tbl_space_type = 'PROPERTIES'\n\tbl_context = 'scene'\n\tbl_options = {'DEFAULT_CLOSED'}\n\tbl_label = 'Bug annotations'\n\n\tdef draw(self, context):\n\t\top = self.layout.operator(BUGANNOTATIONS_OT_some_op.bl_idname)\n\t\tprint(op.some_prop)\n\n\ndef register():\n\tbpy.utils.register_class(BUGANNOTATIONS_OT_some_op)\n\tbpy.utils.register_class(BUGANNOTATIONS_PT_some_panel)\n\n\ndef unregister():\n\tbpy.utils.unregister_class(BUGANNOTATIONS_PT_some_panel)\n\tbpy.utils.unregister_class(BUGANNOTATIONS_OT_some_op)\n```\n\nthen go in the scene settings, a new panel appears. Show the button inside, and look into the console, you'll see that some_prop from the operator doesn't exist if __future__ is imported.\n\n", "Viewport: Texture limit size generates artifacts during painting\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nWhen limit size is lesser than the actual image size, this will result in artifacts at paint region.\n\n- Open attached file\n- Change Texture limit size to 2k or less (`Edit > Preferences > Viewport > Textures > Limit size`\n- Paint the plane.\n", "UI: Annotate Tool - Missing Layer and Color Parameters\nOperating system: Windows 10\n\nBroken: 3.5.0, 3.6.0 (2023-04-06)\n\nIn some places, layer and color parameters are missing:\n\n\n", "lost 90% of my progress\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\ni was 90% through my build and had forgetten to save although i havent made saving every five minutes my priority anyways i was almost done when it freezes then crashes and all of mt work is now gone this has already happened once but i didnt lose anything so i therefore didnt report it\n\n", "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)", "Error when denoising (Optix) large image\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090, 3060 Driver 522.30\n\nBroken: version: 3.3.1\nWorked: Never (3.0 failed, 2.90 did not start rendering)\n\nDenoising large image will fail and may result in crash.\n\nShortened log:\n```\nIllegal address in CUDA queue synchronize (film_convert_float3 filter_guiding_preprocess)\nE1122 18:16:01.843204 7088 denoiser_optix.cpp:470] Error converting denoising passes to RGB buffer.\nIllegal address in CUDA queue copy_from_device ()\n```\n\n[#102515.blend](T102515.blend)\n\nOpen file and render image.", "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", "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.", "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", "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", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n" ]

[ "FBX export brings up an error\nOperating system: macOS 10.14.1\nGraphics card: AMD Radeon R9 M295X\n\nBroken:\nversion: 2.80 (sub 35), branch: blender2.8, commit date: 2018-12-03 23:39, hash: 1b6a394d862, type: Release\nbuild date: 2018-12-04, 01:09:28\nWorked: (optional)\n\nWhen exporting a simple mesh as FBX using the 'Tangent Space' option an error occurs and no FBX file is created.\n\n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Cycles: Keyframing motion blur shutter value fails to apply it properly when generating animation\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\n\nBroken: 3.6, 4.0\n\n\nIf we keyframe shutter property of motion blur, the updated shutter value is not considered during the final render.\nSuppose shutter value is 0 at the start of render, it will remain 0 thorught the animation even if we've keyframed the value.\n\n- Open attached file\n- select cycles render Engine\n- Start animation render (Ctrl-F12)\n", "Low unit scale values show wrong Values and Units in sliders\nOperating system: Linux-5.8.0-2-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: not in 2.80 or 2.83\n\nWhen the unit scale is too low (< 0.0001 e.g. 0.00009), the values in all sliders will jump up to the value they would have with a unitscale of 1.0. This causes problems with the clipping planes of the viewport camera (didn't do this in 2.80). This seems to be independend of the unit system (metric/imperial).\n\nIf this is a known limitation then the shown precision of the unit scale slider should reflect that. Also a fix for the clipping plane issue is needed as that did work in 2.80.\n\nBased on default startup.\n1. In Scene Settings: enable seperate units\n2. set unitscale of 0.00009 or less (metric r imperial)\n3. observe what the dimensions sliders tell you about the dimension of the default cube.\n4. observe the buggy floor grid in the viewport probably due to the same bug in the clipping sliders (wasn't there in 2.80)\n", "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", "\"Radius of the brush\" field missing in box trim and lasso trim sculpt tools.\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\nWorked: Never (tool was introduced in 2.91.0)\n\n\"Radius of the brush\" field missing in box trim and lasso trim sculpt tools after checking use cursor location and radius for trimming shape. The tool uses the brush radius for the depth but the field is not visible.\n\nUse Trim Lasso and Box Trim tools in sculpt mode.\n\n", "Asset Browser refreshes unnecessarily and halts Blender when doing so\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nThe Asset Browser refreshes its thumbnails often, without need for it, and stalls Blender when doing so.\n\nThe video demonstrates that only some actions cause this and that this only happens when the Asset Browser is visible + it shows that the UI can be completely unresponsive for seconds.\n\nThis happens any time the asset browser is open and certain actions such as deleting any object is being performed.\nLarger Asset libraries and slower hard drives compound the issue.\n[2022-08-30_17-22-14.mp4](2022-08-30_17-22-14.mp4)", "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)", "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", "GPencil: Materials' preview thumbnails cause heavy lag when updating\nOperating system: Windows 10\nGraphics card: RTX 3070 FE\n\nBroken: 3.2.1 RC\nWorked: n/a\n\n\n\nAny action that requires the refreshing of your Grease Pencil materials' thumbnails (isolate/hide materials, etc.) causes major lag until the thumbnails are finished refreshing. The more materials your GP object has, the longer the lag. Sometimes the lag is so bad, that it makes the sound buffer skip while the thumbnails refresh.\n\n\n**Video Explanation**\nwatch?v=5KAWsJkIeRY\n\n\n**Steps to Reproduce**\nCreate a GP object and add 10-20 unique materials\nClick one of the \"Isolate Material\" buttons, and start drawing/moving strokes. You will notice extreme lag until all of the little circle thumbnails are finished updating. \n\nTest File:\n[#99361.blend](T99361.blend)", "Color Management / Use curves : Setting clipping option to Min = Max causes CRGB curves to go blank.\nWindows 10, GTX 1660\n\nBroken: Blender 2.82 release.\nBroken: Blender 2.83 daily update\n\nThis will recreate the black CRGB Curve display to go blank.\n\n1. In the Properties Panel, Select Color Management.\n2. Enable 'Use Curves'\n3. Select the 'Clipping Options'\n4. Set 'Max Y' to 0.00\n5. Now select anywhere in the CRGB curve display. It goes blank.\n", "Scrollbar of Clip Editor's Graph and Dopesheet View does not update\nOperating system: elementaryOS 0.4.1\nGraphics card: GTX 1080\n\nBroken: 2.80, 58bfe93db614\n\nWorked: apparently never...\n\nIf you change the endframe of your scene, the scrollbar in the Clip Editor's Graph and Dopesheet view does not reflect the changes.\n\nOpen startup .blend\nGo to Motion Tracking Layout.\nSet Endframe to 1000.\nNotice how the scrollbar down in the Graph View of the Clip Editor does not change its length.\nNow try the same with any other Animation Editor, for example in Animation workspace\nIf you set the endframe to anything that makes the scene longer, the scrollbar will update accordingly and become shorter, indicating that you do not see the full range of your scene.", "Linked data-block has \"pointer\" property still active\nBroken: version: 3.4.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: Probably never\n\n\n\n[torus.zip](torus.zip)\n\nOpen torus.blend. It has a linked collection containing the selected object `Torus`.\n\nAs you can see in the image, the \"Object\" rna properties (parent, and the array modifier one) are both active:\n\n{[F13627034](image.png), size=full}\n\nIn fact you can even click on the property to change it (the popup show up, but clicking on it at least doesn't change it):\n\n{[F13627039](image.png), size=full}", "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)", "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)", "Undo doesn't work with image type empty\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\n\nUndo doesn't work with image type empty (reference image) when you use the bracket or the centre cross to scale or move the empty image, that is very annoying when you accidentally modify your reference image image. A working undo or an option to disable the direct moving/scaling possibility (yellow gizmo) for such empty will be welcome. The undo is active when we use the normal scaling or moving gizmos or panels. \n \n\n- Create an image reference (drag and drop an image in the viewport) \n- Change size and position using the yellow gizmo on the object itself \n- Undo. \n\n", "Faster Animation Playback\n**Status:** Discussing Designs\n\n---\n**Team**\n**Commissioner:** @Mets @Hjalti\n**Project leader:** @Jeroen-Bakker\n**Project members:** @Sergey\n\n**Description**\n**Big picture:** Animators should be able to work in an interactive environment.\n\n**Non functional requirements:**\n\n* Animation playback in the viewport should play at constant framerate at 24fps.\n* `?` Motion curves should be update-able in realtime\n* Playblast shouldn't take much more than regular viewport playback.\n\n**Work plan**\n\n\n**Milestone - Animation Playback/Render Performance**\n\n**Status:** Execution\n**Time estimate:**: \n**Design:** #73429 (Approach Faster Animation Playback)\n**Engineer plan:** Will be created per improvement.\n**Related Tasks**\n* {icon circle color=red} #75134 (TaskScheduler Improvements)\n* {icon circle color=red} #75120 (DrawManager: Improved Task Scheduler)\n* {icon circle color=red} #75208 (Dependency Graph Evaluation Optimizations)\n* {icon circle color=yellow} F-Curve Evaluation Optimizations\n* {icon circle color=yellow} Profile and optimize modifiers (some suggestions are archived in #75207)\n* {icon circle color=yellow} Motion Path Performance\n* {icon circle color=yellow} Optimize VSE Playback for Animators\n* {icon circle color=green} #75124 (ActionEditor: Keyframes Drawing)\n* {icon circle color=green} #75127 (ActionEditor: Add callback function to ANIM_animdata_filter)\n\nThese tasks are ordered in priority. The changes to the task scheduler has most technical impact so we should execute that task with highest priority so we have more time to fix any related issue. The Draw Manager changes rely on features that will be realized by the task scheduler. (@Jeroen-Bakker will do the developments)\n\nChanges to the dependency graph can start from the beginning. Most likely they will be executed by @dr.sybren or @sergey.\n\nThe rest (modifiers, action editor) can be executed afterwards. This is also the time to look at improving motion curves (if this is still needed). (@Jeroen-Bakker will do the developments)\n\n**Milestone - GPU Subdivision**\n\n**Status:** Initial\n**Time estimate:**: \n**Design:** To be completed\n**Engineer plan:** To be completed\n**Related Tasks**\n\n* #68996 (OpenSubdiv GPU acceleration)\n\nThe final design for subdivision (part of the modifiers optimization) needs more collaboration between the GPU/Viewport team and @Sergey to come with an realistic approach.\n\n\n**Milestone - Animation Cache**\n\n**Status:** Needs Design and engineering plan to proceed\n**Time estimate:**: To be determined after Design/EngineeringPlan\n**Design:** #73481 (Design: Animation Caching)\n**Engineer plan:** Not started\n\nAnimation Caching Mechanism: RAM/Disk cache mechanism that can cache the output of an animation. During the animation the cache is invalidated.\nThis cache can also be used for viewport playback and viewport animation rendering.\n" ]

[ "Small size of thumbnails in the shading popover\nOperating system: Win 10\n\nBroken: blender-3.0.0-alpha+master.4a00faca1a5e-windows.amd64-release\nWorked: Previous versions\nCaused by 5183653951\n\nThe size of the thumbnails of the studio lighting/matcaps are displaying smaller than usual....\nNot sure if it was an intentional change or not..\n\nPlease see the image:\nLeft is a previous 3.0 alpha version, right is the current master (4a00faca1a5e):\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```", "Disabling/enabling in viewport a sub collection doesn't make the instances of the collection disabled/enabled unless you save and re-open the file\nOperating system: Windows 10 Pro 64-bit (10.0, Build 18363)\nGraphics card: NVIDIA GeForce 920M (Laptop)\n\nBroken: v2.83.13 Beta, 2020-04-21\n\nIf you disable/enable in viewport a sub collection of Collection then the instances of the parent collection \"Collection\" is not disabled/enabled in viewport unless you save and re-open the file.\n\n**Wanted result**\nThe wanted result is exactly like when you save and re-open the file, because for example if you enable/disable the cube which is child of child of Collection, then the instance of cube is enable/disabled. And just like that, SubCollection is child of Collection and if it's enable/disabled then the instance should be enabled/disabled too.\n\n\n[SubCollection_ViewportEnableDisable_refresh_bug.blend](SubCollection_ViewportEnableDisable_refresh_bug.blend)\n1. Open the provided file.\n2. Disable in viewport the collection named \"**SubCollection**\" to unreveal it in viewport. Now the two collection instances \"Instance of '**Collection**' (1) & (2)\" are not hidden.\n3. Save the file.\n4. Press Ctrl+N and click General.\n5. Reopen the same file. Now the two collection instances before are hidden, but before they were not hidden, it's a bug about refreshing.\n6. Enable in viewport the collection named \"**SubCollection**\" to reveal it in viewport. Now the two collection instances \"Instance of '**Collection**' (1) & (2)\" are not shown.\n7. Save the file.\n8. Press Ctrl+N and click General.\n9. Reopen the same file. Now the two collection instances before are shown, but before they were not shown, it's a bug about refreshing.\n\n**Steps for others to explain the logic of the viewport visibility of Collection and Collection Instance, this is not a bug, it's a useful feature that you should keep**\n- Don't forget to enable the \"SubCollection\" if you didn't do it yet, you've already save and re-open the file.\n- Disable in viewport the collection named \"**Collection**\" to unreveal it (not SubCollection). Now the two collection instances \"Instance of '**SubCollection**' (1) & (2)\" are not hidden. Now Enable back the \"Collection\", the enablement of the 2 collection instances \"Instance of 'SubCollection' (1) & (2)\" don't depend on the viewport enablement of the collection named \"Collection\".\n\n**Description of the last steps**\nIt's very useful when you build a model in a .blend file at the origin (0, 0, 0), and its collection name is \"_MODEL_\", and you want to place a collection instance of it at other location (not origin), and you want to disable the model at the origin by disabling the parent collection of the collection named \"_MODEL_\", and you want to keep enabled (visible) the collection instances.\n\n\n**People will adapt the non-logic bug but they will see weird things**\nThis is a big problem because if people don't know the bug then they think that it's the logic of viewport enablement of collection instances, and all their projects depend on that, but once they save and close and then re-open the file, they will see weird things.", "`Materials` tab not opened at the first time running the script\nOperating system: macOS 10.14.2 (18C54)\nGraphics card: Intel Iris Plus Graphics 640 1536 MB\n\nBroken: (example: 2.80, 89207DF7222A, master, 2019-05-27, as found on the splash screen)\n\n`Materials` tab not open at the first time running the script in attached .blend file\n\n\n* Open the attached .blend file\n* Click `Run Script` the first time\n* It just opens the `Object` tab\n* Click `Run Script` the second time\n* It then opens the `Materials` tab\n\nIt should open Materials tab at the first time clicking `Run Script`\n\n[bug_001.blend](bug_001.blend)", "Contents of \"Viewer Node\" image block do not get updated \nThis might not necessarily be a bug, but may be a feature request. I apologize in advance for being very unprofessional here. I don't think my problem is necessarily relevant to the way I build Blender of the system hardware I use. I've seen the same problem over and over on different systems. Anyways, I compile Blender from source as follow on a freshly-installed Ubuntu:\n\nHere's how I set up Ubuntu after installing it:\n\n```\napt-get -y update && apt-get -y install locales \\\n make \\\n\t\t\t\t\t dpkg \\\n wget \\\n bzip2 \\\n libglib2.0-0 \\\n libxext6 \\\n libsm6 \\\n libxrender1 \\\n g++ \\\n gcc \\\n xvfb \\\n libyaml-cpp-dev \\\n\t\t\t\t\t git \\\n cmake \\\n\t\t\t\t\t vim \\\n\t\t\t\t\t curl \\\n\t\t\t\t\t ca-certificates \\\n software-properties-common \\\n\t\t\t\t\t python3 \\\n python3-pip\n```\n\n\n```\ngit clone blender.git\ncd blender\ngit checkout 8ef39d5c882896bd75e0d4d17fb3e3d4710fc768 # Blender 2.79\ngit submodule update --init --recursive\ngit submodule foreach git checkout master\ngit submodule foreach git pull --rebase origin master\n\nblender/build_files/build_environment/install_deps.sh --source=/blender-git/\n\nPPATH=\"$(which python3)\"\ncmake blender \\\n -DCMAKE_INSTALL_PREFIX=/usr/lib/python3/dist-packages \\\n -DWITH_INSTALL_PORTABLE=OFF \\\n -DWITH_PYTHON_INSTALL=OFF \\\n -DWITH_PYTHON_MODULE=ON \\\n -DPYTHON_SITE_PACKAGES=/usr/lib/python3/dist-packages \\\n -DPYTHON_VERSION=3.5 \\\n -DWITH_OPENAL=ON \\\n -DWITH_CODEC_AVI=ON \\\n -DWITH_MOD_OCEANSIM=ON \\\n -DWITH_CODEC_FFMPEG=ON \\\n -DWITH_SYSTEM_GLEW=ON \\\n -DWITH_FFTW3=ON \\\n -DWITH_OPENCOLORIO=ON \\\n -DWITH_GAMEENGINE=OFF \\\n -DWITH_PLAYER=OFF\nmake -j 7\nmake install\n```\n\nI want to do a very simple thing but it seems that it's becoming very complicated to do it. I have described what my problem is [here ]]. I do not necessarily want to simulate clicking but it turns out that I cannot update the contents of 'Viewer Node' image block. Finally, I thought the best way would be to automatically have backdrop enabled. So I followed the instructions given [[ https:*blender.stackexchange.com/questions/72742/depth-data-works-but-not-in-background-mode | here ](https:*blender.stackexchange.com/questions/102790/how-to-trigger-lmb-click-events-to-activate-a-specific-view-node-and-update-cont) by *Sebastian Koch* thinking that I should be able to dynamically add/remove view nodes and update the contents of the image block automatically. Although I could access to the pixels, but But this does not happen!\nI wrote the right code to do exactly what I show in [this video ]] but the pixels in \"Viewer Node\" image block do not get updated, as they do in the video. Not only that, I tried activating newly-added Viewer nodes manually (as described [[ https:*blender.stackexchange.com/questions/102790/how-to-trigger-lmb-click-events-to-activate-a-specific-view-node-and-update-cont | here ](https:*youtu.be/YCv5qdKLkZo)) but I am still unsuccessful in updating the pixels in the image block. I also tried removing the image block in Python and then continue adding new Viewer nodes. But from the time I remove the image block its contents will always be zero even if I redo the rendering.\n\nThe only way I could successfully update the contents of the image block was after, first, I followed *Sebastian Koch*'s solution and then wrote some code to remove/add all nodes and their links to get either depth map or surface Normals and did the rendering again. But the whole point of me trying to store pixels into Numpy arrays was to avoid doing re-rendering to get around the IO overhead. I could have instead stored two files (for both depth map and Normal maps) throught two Output nodes with rendering only once.\n\nFirst, if this behavior does not look like a bug, I would appreciate the community provide me an easy solution to do what I want. Second, It would be great if you can improve Blender's Python API and add ways of easily accessing rendering results in memory so that people like me who want to do millions of rendering do not need to deal with the delays cause by IO to transfer rendering results from memory to hard drive and can easily store the results into Numpy arrays and store them on disk in chunks. \n\n", "UI bug in preset window after repeated remove\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0\n\nWhen you remove a preset the textfield with the +/- moves one entry up\n[2022-07-15 09-17-07.mp4](2022-07-15_09-17-07.mp4)\n\n1. Go to the scene tab\n2. Create several new presets\n3. Remove all the new created presets in one go without moving the mouse away.\nI think the textfield with the +/- moves should just stay at the bottom and the window should shrink from the top.", "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", "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", "Missing note in the documentation about contexts in application handlers\nOperating system: Linux-5.15.0-41-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 580 Series (polaris10, LLVM 14.0.6, DRM 3.42, 5.15.0-41-generic) AMD 4.6 (Core Profile) Mesa 22.1.4 - kisak-mesa PPA\n\nBroken: version: 3.2.0\nWorked: Could not find one\n\nWhen running `bpy.ops.render.render` with 'INVOKE_DEFAULT' as a result of a render_complete handler throws an exception, stating that `Missing 'window' in context`\n\n1. Create new file\n2. Add script to run render on render finish\n```\nimport bpy\n\ndef render_complete(a, b):\n bpy.ops.render.render('INVOKE_DEFAULT', write_still=True, use_viewport=False)\n\n\nbpy.app.handlers.render_complete.append(render_complete)\n\n```\n3. Run script and start render\n4. Exception gets thrown in Terminal:\n```\nTraceback (most recent call last):\n File \"/Text\", line 6, in render_complete\n File \"/home/richards/Documents/BlenderDev/blender-3.2.0-linux-x64/3.2/scripts/modules/bpy/ops.py\", line 113, in __call__\n ret = _op_call(self.idname_py(), C_dict, kw, C_exec, C_undo)\nRuntimeError: Operator bpy.ops.render.render.poll() Missing 'window' in context\n```\n\nI am unsure if this is intended behavior, as invoking a render in other circumstances reopens the render view. If it is intentional, it would be a useful thing to mention in the handler documentation, that inside the handler, the context does not contain 'window'", "The Tool Selector Window close one time every two times, when opened too closed to the bottom border of the screen\nOperating system: Windows 10\nGraphics card: GTX 1080\n\nBroken: 2.80\nWorked: (optional)\n\nThe Tool Window, open and close immediately, choosing the tool under the mouse cursor, if the tool window is opened too close from the bottom of the screen.\n\n1) In Edit > Preferences > Keymap, set the \"Space Bar action\" to \"Tools\"\n2) On the 3D viewport, place your mouse cursor in the top area of the viewport\n3) press the spacebar, the tool menu open without any problem, and you can choose a tool with a shortcut key (for example press B to choose the Box selection)\n4) You can repeat that several times in a row without any problems.\n5) Now move your mouse cursor much more closer to the bottom border of the screen, so that you know that the tool window will have to be shifted upward to be displayed correctly.\n6) Press the spacebar a first time. This is ok, you can select your tool\n7) Now press the spacebar a second time. This time, the tool window open and intermediately closed, and the tool selected is the one that is under your mouse cursor.\n8) Press the spacebar again: the tool window open normally\n9) Press the spacebar again: the bug reappear\n10) Now on, every one time over two, the bug appear.\n\n**Expected behavior**\nThe Tool Window should open and stay opened consistently, no matter where the mouse cursor is placed on the screen, when the spacebar is pressed.", "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", "Context in Timers\nCalling operators in [timers ]] is difficult currently, because very few attributes of `bpy.context` are initialized (which is expected and not a bug). The issue is, even when you [[ https:*docs.blender.org/api/blender2.8/bpy.ops.html#overriding-context | override the context ](https:*docs.blender.org/api/blender2.8/bpy.app.timers.html), problems remain. This task exists to keep track of these problems and to discuss solutions.\n\nProblem 1: Incomplete operator `poll` functions\n****\n\nMany operators have `poll` functions that are supposed to check if the operator can run in a given context. The issue is that many poll functions are incorrect, because they assume that `CTX_wm_window(C)` and `CTX_wm_screen(C)` don't return `NULL` (maybe some more like `CTX_wm_workspace(C)` are missing here). Those context variables are almost always initialized, but not in timers. This is the main source of crashes when dealing with operators in timers.\n\nTo reproduce the issue, run this script:\n```lang=python\nimport bpy\n\ndef add_object():\n```\n bpy.ops.mesh.primitive_uv_sphere_add()\n```\n\nbpy.app.timers.register(add_object, first_interval=1)\n```\n\nThis results in a crash, but it should throw an exception due to incorrect context. The issue is that this operator internally calls `ED_object_editmode_exit` in `make_prim_finish`, which calls `CTX_data_edit_object` which returns `NULL`, because `CTX_data_screen(C)` is `NULL`.\n\nThe script can be fixed as follows:\n\n```lang=python\nimport bpy\n\ndef get_base_context():\n '''Create a minimum context override that is necessary to avoid crashes.'''\n wm = bpy.data.window_managers[0]\n window = wm.windows[0]\n context = bpy.context.copy()\n context[\"window\"] = window\n context[\"screen\"] = window.screen\n context[\"workspace\"] = window.workspace\n return context\n\ndef add_object():\n context = get_base_context()\n bpy.ops.mesh.primitive_uv_sphere_add(context)\n\nbpy.app.timers.register(add_object, first_interval=1)\n```\n\nSolution 1\n---------\n\nTry to find all the incorrect `poll` functions and fix them individually. This will definitely solve the issue, but might require a lot of effort (maybe it's also easy, I haven't tried yet).\n\nSolution 2\n----------\n\nDefine some \"minimal context\" that is required to run operators. For example, we could say that in order to run an operator the context must have a window and a screen, otherwise the `poll` function of the operatoris not even checked. It's fairly easy to implement such a check in `WM_operator_poll`. The downside is that there might be some operators that can run without any context. To mitigate this downside, we could add a flag that can be added to operators that don't require any context.\n\nProblem 2: Context Override\n****\n\nWe do support context overrides when calling operators from Python already. However, there is one severe limitation when calling a operator that is defined in Python that itself calls other operators. The issues is that the context override only applies to the immediately called operator, but not to the indirectly called operators. \n\nTo see this issue in action, run the following script and check the terminal output:\n\n```lang=python\nimport bpy\n\ndef get_base_context():\n```\n '''Create a minimum context override that is necessary to avoid crashes.'''\n wm = bpy.data.window_managers[0]\n window = wm.windows[0]\n context = bpy.context.copy()\n context[\"window\"] = window\n context[\"screen\"] = window.screen\n context[\"workspace\"] = window.workspace\n return context\n \n```\ndef custom_operator():\n```\n context = get_base_context()\n bpy.ops.object.my_operator1(context)\n \n```\nclass MyOperator1(bpy.types.Operator):\n```\n bl_idname = \"object.my_operator1\"\n bl_label = \"My Operator 1\"\n \n def execute(self, context):\n print(1, context.screen)\n bpy.ops.object.my_operator2()\n return {\"FINISHED\"}\n \n```\nclass MyOperator2(bpy.types.Operator):\n```\n bl_idname = \"object.my_operator2\"\n bl_label = \"My Operator 2\"\n \n def execute(self, context):\n print(2, context.screen)\n return {\"FINISHED\"}\n \n```\nbpy.utils.register_class(MyOperator1)\nbpy.utils.register_class(MyOperator2)\n```\n \n```\nbpy.app.timers.register(custom_operator, first_interval=1)\n```\n\nIn my case it prints:\n```\n1 <bpy_struct, Screen(\"Scripting\")>\n2 None\n```\n\nSolution 1\n---------\n\nApply this patch:\n```\ndiff --git a/source/blender/python/intern/bpy_operator.c b/source/blender/python/intern/bpy_operator.c\nindex 4b2b5f129a7..b599242219c 100644\n - a/source/blender/python/intern/bpy_operator.c\n+++ b/source/blender/python/intern/bpy_operator.c\n@@ -227,7 +227,9 @@ static PyObject *pyop_call(PyObject *UNUSED(self), PyObject *args)\n \n```\n context_dict_back = CTX_py_dict_get(C);\n```\n \n- CTX_py_dict_set(C, (void *)context_dict);\n+ if (context_dict != NULL) {\n+ CTX_py_dict_set(C, (void *)context_dict);\n+ }\n```\n Py_XINCREF(context_dict); /* so we done loose it */\n```\n \n```\n if (WM_operator_poll_context((bContext *)C, ot, context) == false) {\n```\n```\n\nWith this change the python context override is not reset when an operator is called without an explicit context override. This fixes the example above, and might even work in general. One issue is when someone overwrites the context without calling `context.copy()` first, because then the underlying context might suddenly change in unexpected ways.\n\nSolution 2\n------------\n\nRefactor `bContext` to properly support \"context override stacking\". The pattern that parts of the context are temporarily overridden is quite common in Blender. We could change `bContext` so that it supports multiple layers of overrides natively. The API could look like so:\n```lang=c\nCTX_override_push(\"area\", area);\n/* ... */\nCTX_override_pop();\n```\n\nAn \"override\" could be a single overridden property, or a python dictionary or something else, that we do not know yet.\n\nWhile this refactor is a larger project, it seems doable to me, because `bContext` is fairly well encapsulated.\n\nWith this system, we could also support doing context overrides with a [[ context_managers.html | context manager ]] in python, instead of copying the entire context and passing it to the operator call.\n", "Crash using blender_debug_log.cmd and \"Reload Scripts\" in Cycles preview render\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nLoading Blender with blender_debug_log.cmd, it crash immediately when I try to reload the scripts if Cycles is running. This is not happening when launching blender.exe \n\nLaunch blender 2.8 using blender_debug_log.cmd.\nIn the view 3d, choose Cycles as render preview.\nIn the search bar, look for \"Reload Scripts\" and click on it.\nBlender Crash.\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n", "Crash at the end of preview generation for a deleted datablock\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 536.99\n\nBroken: version: 3.6.2\nWorked: -\n\nBlender crashes if you trigger the generation of a preview for a data block and then delete the data block itself. Obviously, the preview data is generated, but since the datablock itself no longer exists, I get an `EXCEPTION_ACCESS_VIOLATION` and a crash.\n\n\nRun simple script in attached *.blend file.\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)", "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..." ]

[ "Setting Workbench as Render Engine blocks loading of icon previews\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 860M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.81 (sub 2)\n\nSetting Workbench as Render Engine blocks loading of icon previews, while setting it to EEVEE or Cycles does not.\n\n - Open attached blend file: [workbench_x_icons.zip](workbench_x_icons.zip)\n - Use Run Script and check TEST tab in Sidebar (icon loads).\n # Change Render Engine to Workbench and use Run Script again (icon does not load).\n\n[workbench_x_icons.mp4](workbench_x_icons.mp4)", "Workbench makes Addons icons disappear! \nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82, also tested on 2.90 (13abd3784ad0)\nWorked: (optional)\n\nStartup file with Workbench selected causes all extra icons for active Addons to disappear. This does not happen with Eevee or Cycles. Please see the pictures and the startup file attached \n\n{[F8498299](image.png), size=full}\n\n{[F8498304](image.png), size=full}\n\n\n1) Have some plugin that has custom icons activated (e.g: TexTools)\n2) Set Workbench as the workspace render engine\n3) Save Startup File\n4) Open Blender Again and you will see the icons are missing!\n\n**How to get the icons back:**\n\n1) Disable the plugin/plugins\n2) Set Eevee as the workspace render engine\n3) Save Startup File\n4) Open Blender again\n5) Activate the plugins you need and Icons will be fine\n\n[startup.blend](startup.blend)\n\n\n♥♥♥ **Thank you very much for making this program so great. The community loves you guys** ♥♥♥ " ]

[ "4.0A producing specular reflections of area lights on diffuse surfaces, 3.6.1 doesn't behave this way.\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.1 & 4.0 Alpha\n\nArea lights in 4.0 Alpha producing specular reflections on diffuse only (specular = 0) surfaces in 4.0.\n\nI tried to report this discrepancy to the developer forum but can't seem to post it there, so I figured maybe whoever monitors this could help. \n\nIn 3.6.1, if a material has no specular component, area lights only produce diffuse illumination. But in the 4.0 alpha (build downloaded 8/14), the area light produces a specular reflection. I don't know if this is a new intentional development thing, or if it's somehow related to the light linking feature.\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)", "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)", "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.", "Faces culled with \"backface culling\" still receive shadows in the viewport\nSorry if this is a repeat report. I was unable to find another report for this.\n\nOperating system: NA\nGraphics card: NA\n\nBroken: All versions of Blender 2.8X and 2.90 that I am able to test.\nWorked: Never\n\n**Short description of error:**\nWhile the \"Backface culling\" option is enabled in the viewport, the culled backface will still receive a shadow when the \"shadow\" option is also enabled.\n\n\n\nFor example, here's a box with all it's normals facing inwards. With backface culling, we are able to see inside the box. But with shadows also enabled (as seen in the picture), shadows are cast onto the \"culled\" faces.\n\n\n\n**Exact steps for others to reproduce the error:**\n1. Create scene with an object that has it's normal facing away from the camera (you're seeing the backface).\n2. Enable \"Backface culling\" in the viewport shading options.\n3. Enabled \"Shadows\" and adjust the position of the \"light\" such that the \"back face is in shadow.\n4. The backface should now have a shadow placed on it.\n5. If you reproduce the steps above for the workbench render engine, the same issue applies.\n\n[Backface Shadowing.blend](Backface_Shadowing.blend)", "Cycles: Tex Coord node plugged directly in a world shader does not affect diffuse rays\nI tested and it's not supported in 2.79 so this maybe a corner case that has long been standing.\n\nThis happens also in final render.\n\n[cycles_diffuse_ray_issue.blend](cycles_diffuse_ray_issue.blend) \n- Open given file and switch to rendered view.\n- Connect the 2nd checker color socket to another of the dysfunctional texco socket.\n- Only glossy rays can now see the texco of the environment.\n\nThe issue seems to happen if the coordinate is plugged straight to the background or emission node. If the output is mixed it does work (default state of the file).\n\nMixed, working:\n\n\nNot mixed, broken:\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", "Grease pencil strokes are incorrectly blended with geometry in draw mode (depending on 'Fade Inactive Geometry' setting)\nOperating system: Win 10\nGraphics card: ATI Radeon 5700\n\nBroken: (example: 2.92b, 213f8*, master, 2021-01-28, as found on the splash screen)\n\n\nnote: this is due to `Fade Inactive Geometry` being ON\n\nWhen drawing grease pencil strokes with a black material the rendering style changes when...\n\n - ...switching between draw-mode and edit mode, or\n - ... toggling the overlay button in draw mode (even will all overlay options disabled).\n\n\nThis leads to noticeable rendering artifacts while drawing. Please consider the following screenshots:\n\noverlays on:\n\n\noverlay off:\n\n\nSome assumptions:\n- I assume that the blend modes are not correctly set and thus interfere with the MSAA.\n- The white artifacts are especially pronounced for thin strokes of all opacities. Increasing the thickness factor slightly decreases the problem.\n\nLoad the following blender file\n[stroke-test.blend](stroke-test.blend)\n\nStep by step:\n1. Start blender\n2. Create Cube\n3. Create Grease Pencil\n4. Add new material for grease pencil and change to black\n5. Draw strokes (with different opacities)\n6. Switch between Draw and Object mode or toggle Overlay-Toggle\n", "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)", "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", "Mirror painting error\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "UV-space triangulation wrong\nOperating system: Arch Linux\nGraphics card: NVidia 1080 Ti\n\nBroken: 3.3.1\nWorked: none?\n\nTriangulation of (concave) N-gons is wrong in UV-space.\n\nJust check the UV-space of Suzanne: on the right side of the main island, where the hole of the ear is, see the screenshots.\n\n\n\n", "OpenColorIO-Config-ACES 0.2.0 breaks in sRGB view transform\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nI tested the newest OCIO v2 config from Github (v0.2.0)\nin Blender 3.2 Alpha. It was first time I tried that.\nI had to change the OCIO 2.1 version to 2.0 to make it actually work in Blender. I was assured that this shouldn't be a problem.\n\nI rendered a test scene and saw some strange shading errors with the default sRGB view transform.\nSelecting a different view transform like Rec.709 fixes the issue.\n\nI posted about the issue on my blog ?page_id=5517 and on ACESCentral.com \n4354\n\nThe rendered EXR file is fine of course. The problem only occurs in the render view or when I try to export the rendered image.\nJPG works fine, PNG breaks in a different way and creates a strangely bright image.\n\n[Blender_32alpha_OCIOv2_sRGB_bug.blend](Blender_32alpha_OCIOv2_sRGB_bug.blend)\n\n\n\n\n\n\nI also tested the same .blend file on a new M1Max MBP. There I cannot replicate the error.", "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)", "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" ]

[ "EVEE: No shadows at orthographic camera\nOperating system: Windows 10\nGraphics card: GTX 760\n\nblender-2.80.0-git.009dbc2bc9fb-windows64\n \n\nI dunno know if it's a bug.... But there are no shadows in EVEE at Orthographic camera. But In 3d Viewport I see shadows.\n\nFile:\n[tmp1.blend](tmp1.blend)\n\nOrthographic Camera:\n\n\n3D Viewport with Perspective:\n\n\n\n- Open the blend file\n- Press \"0\" to get into my Ortho Camera" ]

[ "unwanted uv-gap created by bevel modifier\nOperating system and graphics card\nwindows 7\nNVIDIA GeForce GTX 660\n\nBroken: 3d243eb\nWorked: same error on offical release 2.78\n\nbevel modifier (bevel by weight) creates an unwanted UV-gap at a vertex with 5 edges connected. 2 edges has bevel weight. Error visible if bevel modifier is applied of if subdiv modifier is active. The UV-gap disappears if 4 out of 5 edges has a 90 degree angle to one another.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nHard to explain how to model. Easiest for you is to open the .blend and test it. I put a shape key on the \"error mesh\". Turn the shapekey on/off to show the error.[bevel modifier error.blend](bevel_modifier_error.blend)", "QuadriFlow with the new symmetry option creates holes at the center\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)\n\n\nQuadriFlow creates hole artifacts like these when remeshing. Usually occurs after using Voxel Remesher and/or Dyntopo which can break symmetry at the center very often.\n\n\n1) Sculpt something in Sculpt Mode and use Voxel Remesher/Dyntopo.\n2) Start QuadriFlow. It doesn't always produce these holes in the mesh, but keep repeating part one and two and you will eventually get these holes where each side hasn't been properly merged together.", "Sculpt Mode Gesture Tools\nThis task keeps track of the missing gesture tools in Sculpt Mode\n\n| | Box | Lasso | Line | PolyLine |\n|------------|-----------|-----------|-------|----------|\n| Mask | In master | In master | In master | |\n| Hide | In master | | | |\n| Face Set | In master | In master | | |\n| Color Fill | | | | |\n| Trim | In master | In master | | |\n| Project | | | In master | |\n\n**Gesture Tools**\n**Mask**: Performs a masking operation in the area affected by the gesture. It can mask, unmask or invert the mask.\n**Hide**: Hides the vertices affected by the gesture without modifying the face sets.\n**Face Set**: Creates a new Face Set that contains all vertices affected by the gesture\n**Color fill**: Fills the area affected by the gesture with color, using a blend mode and a strength.\n**Trim**: Cuts the area affected by the gesture using a boolean operation. This modifies the mesh topology and needs to use the boolean solver. It creates a new Face Set for the new created faces after the boolean cut.\n**Project**: Projects the vertices outside/inside the area of the gesture towards the area of the gesture. This allows to simulate cuts in the mesh without modifying the topology, so it should be much faster in cases were a remesh operation will follow the cut operation. Unlike trimming, this operation won't be able to make hole though the mesh. \n\n**Polyline**\nPolyline is not implemented yet as a gesture in ##wm##. It will use the same data as the lasso gesture, but it will add a point on each mouse click and it will confirm the gesture with enter. This won't require any modification to the code of any gesture tool (sharing they same code with the lasso gesture will work). \n\n**Additional tasks**\n- Option to snap the line/polyline gesture angle\n- Improve the line gesture preview, displaying which side of the line/plane is going to be affected", "Knife tool fails on a non-planar n-gon\nBroken: 2.74 up to and including 2.92 master\nWorked: 2.73 (yes, I bisected that far back ;) )\n\n\nKnife tool fails to cut between verts in n-gons of certain configuration.\n\n\nLoad the attached .blend and try to make a knife cut between the two selected verts (i.e. try to create an edge connecting them).\n\n[knife_fail.blend](knife_fail.blend)\n\n(If you want to test in 2.73 yourself, copy the object from a running instance of 2.9x into 2.73 using ctrl+c/ctrl+v, then replace the mesh in another existing mesh object).", "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", "Mesh flickers in edit mode if shapekey added\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.0.0 and later\nWorked: 2.93\n\nThat mesh I put in .blend file is from my old project (started in 2.79). For some reason normals on that mesh go crazy if I try to edit it in Face selection mode. I found that this particular mesh can't have shapekeys and auto smooth enabled at the same time.\n\n1. Add Basis shapekey to the mesh\n2. Enter Edit Mode\n3. Select Face Selection Mode\n4. Move any face\n\n[bugFlicker.blend](bugFlicker.blend)\n[bandicam 2022-12-03 01-21-18-089.mp4](bandicam_2022-12-03_01-21-18-089.mp4)", "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", "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", "Remesh with small voxel size sometimes generates mesh with many holes\nOperating system: macOS-14.0-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: 3.1 - 4.0\n\nRemeshing breaks objects\n<video src=\"attachment\" controls></video>\n\nIn a new scene add a monkey model and jump into sculpting, change the voxel size to 0.0024 m and remesh...the object breaks\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", "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", "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", "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", "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.", "Orbit Around Selection in Curves Sculpt Mode\nIn mesh sculpt mode, the new orbit pivot is set based on the last brush stroke. The same should happen in curves sculpt mode." ]

[ "Clay Thumb brush rips edges\nOperating system: Linux-5.3.0-29-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.48.02\n\nBroken: version: 2.83 (sub 2)\n\nSimilar to #70387, the Clay Thumb brush seems to rip edges while sculpting with the Strength close to 1\n\n- With Factory Settings, open the Sculpting Template\n- Pick the Clay Thumb Tool and reset the brush to the default settings\n- Increase the Strength to 1\n- Sculpt a long spiralling stroke along the surface of the default sphere\n\nThe result should looks somewhat like this:\n\n\nOnce the Tool or the Mode is switched, the ripped holes are connected again but the stepping in the surface is still clearly visible.\n\n" ]

[ "Camera projection mapping for brush texture\n**Status:** Task design and engineer plan review\n\n---\n\n**Team**\n**Code Review:** @Jeroen-Bakker @ideasman42\n**Project leader:** @ivpe \n**Project members:** @ssh4 \n\n\n**Preamble**\n\nGoal of this project are add code support and tools for Camera Projection Painting to Blender.\nSuch workflows used in 3D CG from early days for matte painting, 3D and video integration, etc.\nIn all workflows most logical UX is projection preview as it seen from camera and projection preview overlay on 3D model or scene that visible from any point.\n\nWhen matte painting is one of oldest workflows. Last years we can see huge progress in 3D scanning/Photogrammetry methods, that now one of main parts of 3D assets or scenes creation process. And in same time a lot of artists use photo modeling workflows with photo or video data as a source for textures.\nAnd again, most logical and fast way to work with textures for that models is using 3D paint feature directly in 3D app, instead of use external 3D painters or 2D editors to work with UVed textures.\n\n-----------------\n\n**Who can use it**\n\nThis project improvements in used UX from 3D assets creators, Photogrammetrists (3D scanners) and VFX/Matte painters point of view.\nFor that we made a list of current limitations and propose improvements for wide type of 3D CG users.\n\n* 3D assets creators:\n\nProbably one of biggest group. Standard photo modeling workflow use photo or images as a backgrounds. Final model UVed in human readable form and textures are making with standard for 2D editors or texture painter's workflows with using layers, masks, etc.\n\nPaint tool that can allow project image or photo from specific camera view can speedup time for mock-ups iterations in works with clients and art/creative directors. Due to real-time preview of results in 3D. In same moment using real photo, especially in architectural models limiting possible source of images. Due to lens distortions in all photo, required additional attention to used only high-quality professional photo equipment. Or applying undistortion to all sources before using them for texturing. And when using video in that moment required lot of additional disk space to store that temporary data.\n\nIf 3D assets are low-polygon than this also required creation of “proxy” objects with higher polygons count, because current Blender UV Projection give visible distortions on textures if used low-poly mesh or mesh with n-gons.\n\n* 3D sculptors:\n\nAnother and also big group of 3D content creators. And if in early CG days that was mostly artists that working with organic shapes or characters. In current time a lot of artists doing hard-surface modeling in 3D sculpting editors.\nThat group of artists also need the way to project photo data to textures and using paint editor in same app, speedup sketching or work in progress iterations.\n\nAll models made in that workflows in time of work can have complicated and non-optimized UVs. And using external 2D editors or texture painters not usable until model are retopologized and UVed in human readable form.\nCurrent Blender UV projection have less issues with such meshes. But polygons count already have a big impact on CPU time required for work. Computing new UV Projection from new camera/view for 5-10 million poly meshes already far from real-time.\n\nThis user group also have demand on works with photo or video sources, and lens distortion in source data required to use of undistorted images.\n\n* Photogrammetry and 3D scanning:\n\nLast years one of most growing groups of 3D content creators. That group work with a huge poly count meshes. And it more narrows to 3D sculpting by used workflows in post-processing scan data. With one but important difference, 3D scans are often monolith or split to chunks 3D meshes. And in the middle of process this meshes have completely non optimized UV's with thousands UV islands made by UV parametrization algorithms optimized for speed and works with thousands or even hundreds of millions polygons meshes.\n\nPhotogrammetry with all its power have a limitations in used algorithms due to a huge amount of data used in time of creation of 3D meshes and their texturing. And photogrammetry user not always have way to easily control process of choosing best source for texture in specific part of model. And result texture can use source data from image (camera) with worse depth of field or changed environment lights.\n\nLot of clients of 3D scan studios prefer to work with raw meshes and original textures to be sure that all possible details from 3D scan was used in most efficient way for their project.\nBut photogrammetrist still need fast way to quickly fix raw mesh and raw texture from specific image (specific camera) with better details, or correct light, etc.\n\nAs with 3D sculptors, mesh polygon count is more than enough to avoid UV projection deformations on textures. But used polygon count around 10-20 million of polygons in raw mesh is not a rare use case for high-quality high-resolution 3D scan.\n\nOne of biggest differences for other groups, is an image (camera count) used for 3D model and texture creation. 50-60 images/cameras are average small photogrammetry scan.\nBig or precise scans can easily have 1000 or even 10000 images with 8K or bigger resolution.\nGood point that using all these images/cameras for final texture is not a mandatory. But workflow that allow quickly switching between images/cameras are big time saver.\n\nAnd as soon as source for 3D model and texture are real photo, that always have lens distortions. But if other groups probably can work with some small distortions. Photogrammetry due to it high precision required using mathematically correct lens distortion models. That allow precise copy of source texture from scanned objects with sub millimeter resolution.\n\nUsed image count and size of this images required a lot of disc space for any additional temporary files like undistorted images.\nSo support for using lens undistortion in projection painting “must have” feature.\n\n* Matte painting/VFX:\nThat group can combine workflows and issues from all groups mentioned above. But in addition, this group often work with video sources. That mean this can be hundreds or thousands of frames that also can have real lens distortions or even rolling shutter issue (visible as a skew image deformation).\n3D models can be a combination of low-polygon models or blocks or n-gons for quickly build different distance planes on scene.\nAnd all of this in production or sketching time required quick integration with projection mapping painting.\n\n----------------\n\n**Current Blender workflow limitations and issues**\n\nSummarizing the above limitations of Blender:\n\nBlender currently has a way to do camera projection painting, with \"Clone\" brush and \"UV Project\" modifier. This method is enough labor intensive on the part of the user experience, requires to choose a lot of options even just to change camera from which projection act, which negatively affects the speed of the workflow. The main disadvantage of this method is the requirement for the density of the geometry. Low poly models (for example, after retopology) will have unnecessary distortions when drawing. Also, an extra step in this process is the export undistorted images/movie clips, because datasets can be large enough to create a lot of unnecessary files. It is also desirable to have control over brightness/contrast, ect, this method do not allow this.\n\n-----------------\n\n**User workflow expectations**\n\nThe ultimate goal of this project is to build a workflow that eliminates these shortcomings:\n\n**Scene setup**\nAssumed that the user has a scene with mesh objects, created by himself or imported from third-party software. There are also a number of cameras and original images/movie clips.\n- Automatically attach images/movie clips to specific cameras, they have similar names in any software. It should also be possible to do this manually.\n- Distortion parameters can be obtained through Movie Tracking Solver, but it should be possible to set parameters separately.\n\n**Canvas texture correction/painting process**\nAssumed that user is in Texture Paint Mode.\n- Select a camera. It is assumed that when you select a camera, the corresponding image/movie clip will also be selected for painting.\n- Paint. It is assumed that texture projection will occur from the camera with distortion correction according to the distortion parameters.\n\nMore globally, a major refactoring of the Texture Paint module is needed (like this one [#73935 ](T73935)), all users expect smooth workflow with high-polygon objects and high-resolution images/movie clips.\nAlso, an important part is to give the user a visual representation in the viewport of exactly how the texture will project on the object and from which camera the projection is act (the most obvious is to project from the active camera of the scene).\n\n------------------\n\n**Suggestions**\n\nHere described only a suggestions, each of them can be an open question.\n\n- For both \"Movie Tracking\" and \"Texture Paint\" modules image/movie clip as well as distortion parameters should be part of a particular camera (That should be coordinated with Movie Tracking module). About the Brush Management project. The described workflows have a tight relationship with a specific scene and objects in it, hence from the point the user's view of the photogrammetrist or VFX artist, it is expected that the work done by him at the scene setup stage will be saved specifically for this scene and objects in it. Therefore, it is important to understand that the camera with which the projection is act, its distortion parameters should not have relations with a specific brush. Since the dataset of images/movie clips can be large and also associated with specific cameras of a specific scene, it is also cannot relate to the brush.\n- Automate the process of attaching images/movie clips to specific cameras. This is most often possible by the name matching of the camera and the image/movie clip file.\n- Add \"Camera\" brush texture projection mode. It should use data (image/movie clip) from the active scene camera for the brush texture and also to determine the current parameters of the distortion.\n- Refactoring the brush preview. At the moment it is not informative and has limited presentation of the end result (for example, for \"3D\" texture map mode it's not presented for many years). In the context of this project the preview should be an overlay that takes into account the geometry of the object and gives an actual representation at any view.\n\n**All this but more visually**\nPreviously, we (@ssh4, @ivpe) did it as an addon, it was more photogrammetry-oriented so UI/UX should be different in some cases. In this short video described basic principles of workflow with large dataset of raw (distorted) images, viewport preview. Non-commercial scene is used.\n[Camera Projection Mapping.mov](Camera_Projection_Mapping.mov)\n\n-------------------\n**Work plan**\n> This section will proceed only after final design is ready:\n\n- ...\n\n**Open questions**\nOpen questions according to the suggestions below. Everyone can have their own opinion, so we need a general solution to be approved by everyone. Therefore, I leave a link to the original post, as well as its summary. After design document update some suggestions are included into it and some are still questionable:\n\n- [Original post by]] @brecht [[ https:*developer.blender.org/T81662#1038426 | Original post by](https:*developer.blender.org/T81662#1037146) @Sergey Where to store the distortion parameters of images/movie clips as well as the relationship between a specific camera with a specific image as given the current Movie Tracking design and in the case of its modification to more unified?\n- [Original post by](T81662#1037214) @brecht In case if camera store image or movie clip as background image. Should we have option for automation switch brush texture image / movie enabled by default? Or it should be the only way? \n- [Original post by](T81662#1046815) @sebastian_k Camera background image is enough for visual preview or it should be shader based?\n- [Original post by](T81662#1046815) @sebastian_k VFX scenes has already set background movie clips on cameras. It can be used for any workflow as well, I think. In terms of current project - to store image or movie clip relative to specific camera. But if we have more than one background image on single camera? In this case background images/movies are blended. The oldest principle: \"You get what you see\" should work here too. So how can we handle this? In my opinion the simple way - remove list of background images and leave only one. As I remember in older releases (< 2.8x) we had this as a list to use from different view angles (from left, right, top, camera). So, I think it is more Blender's design questionable too.\n- [Original post by](T81662#1047507) @ssh4 should be camera intrinsics animated for support videos that captured using zoom lenses as well as using optical or sensor stabilization?\n\n- Refactoring of the Texture Paint mode. Is it planned and is it worth counting on help in its implementation?\n- ...\n\n**Relevant links**:\nA small research on YouTube about current limitations:\n[CGMatter: Blender 2.8 Panorama stitching projection painting (part 2)](s_x62z1T9tk?t=467)\n[CGMatter: 2D To 3D](nWCWtojeM14)\n[CGMatter: Realistic 3D? EASY](uWkKV0HxwFQ?t=919)\n[IanHubert: Wild Tricks for Greenscreen in Blender](RxD6H3ri8RI?t=131)\n\nPrevious implementation using UV-projection method in separate boost-module:\n[Camera projection painter addon](watch?v=lasdJIIAv70&t=13s)\nIndustry-compatible lens distortion models:\n[Brown-Conrady]], [[ https:*developer.blender.org/D7484 | Nuke ](https:*developer.blender.org/D9037)", "No \"affect alpha\" in brush settings in the Image Editor\nOperating system: Linux-5.3.0-40-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 7)\n(as well as the latest alpha: version: 2.83 (sub 5))\nWorked: 2.80 (Checkbox existed in Image Editor brush settings, but had NO effect on brush behavior)\n\nIn the 3D Viewport as well as the Properties Editor while in Texture Paint mode, all brushes offer the \"affect alpha\" option in the \"Advanced\" section of the Brush Settings. In the Image Editor that option is missing from the \"Advanced\" section for no apparent reason.\n\n\nOpen Blender with factory settings. Switch to \"Texture Paint\" tab. Compare the \"Advanced\" section of the active brush's tool settings in the Image Editor to that in the 3D Viewport or Properties Editor.\n\nSurely this has to be a well-known issue and exists only due to technical limitations of some kind.\nWhat should I tell my students why this inconvenience exists and when it will be addressed?", "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", "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)", "Object.display_type \"Solid\" behaves the same as \"Textured\"\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.8.1 26.20.13001.29010\n\nBroken: version: 2.81 (sub 12)\nWorked: 2.79b\n\nIn a viewport set to \"Textured\" mode (either on Cycles or Eevee), setting Object.display_type = \"SOLID\" still shows a textured object.\nOn Blender 2.79 this property was called \"Maximum Draw Type\" and was behaving as expected.\n\n1.-Set the viewport to Textured mode.\n2.-Select a textured object and set its property \"Display As\" to Solid.\nIt will stil be shown as Textured so theres no difference between the two modes (Solid, Textured)\n\nBlender 2.81\n\n\nBlender 2.79b\n\n\nExample blend.\nThe viewport is set to \"Textured\", the monkey set to \"Solid\" but is shown as Textured.\n[solid_object_display_type.blend](solid_object_display_type.blend)\n", "Outline of plane in Object mode does not Render after applying transforms\nBroken: Current main.\nWorked: N/A.\n\nOutline of plane in Object mode does not Render after applying transforms and looking Down the plane in top down view or any view.\n\n1. Delete the default cube.\n2. Add a Plane.\n3. Numpad 7 for top down view.\n4. selct the plane and rotate on x axis 90 degrees\n5. Apply all transforms.\n\nFrom Blend File Just Select the plane and press numpad 7 to go to Topdown view and Out line should stop rendering.", "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.", "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", "3D texturing: Fix seam bleeding\n# Version 1 (abandoned)\n\nThe concept of this approach is create a list of source pixels that should be copied to other areas of the texture. By doing this the seams will be fixed. During copying the pixels can be blended with near pixels to improve quality.\n\n* Scan over all uv edges that make the bounds of an UV island.\n* Scan over pixels that are 'intersect' with the found uv edges.\n* Pixels that are already part of the PBVH Pixels should be ignored.\n* Pixels that are not part of a PBVH Pixels should be 'fixed'\n* Find a corresponding pixels that could be used as a source to fix the pixel.\n* Add the source pixel to be copied to the pixel to be fixed. This should be added to the PBVHNode of the sourcing pixel. If the pixel was changed it should be copied to the target.\n\nDuring test we decided that this solution doesn't get to the quality we want.\n\n# Version 2 (new approach)\n\n- for now the unconnected uv edges will be the same as version 1, we can in the future change this by extending the edges. I left this out of scope for now.\n- split the mesh into uv island. \n- extract the pixels of the 'original' mesh.\n- per UDIM tile create uv island map (2d array with ints)\n- dilate the uv islands until they reach each other undecisive pixels should not be solved.\n- This map is used as a mask where uv island can extended.\n- per uv island find the sharpest corner.\n- go over the 3d mesh fan of the corner and see how this fan can be extended. For now I see 3 scenarios\n - the corner is a cut (both edges are connected in 3d space). for example see uvmap of cube. In this case we should duplicate the original faces and \n - the corner connects to another edge on the same uv island. might be similar to the first case, \n - the corner connects to one or multiple uv island. In this case the geometry that isn't connected in uv space, but is in 3d space should be added in between.\n- this generates new primitices that could be extracted using the pixel extractor.\n- the newly primitives should be stored in the PBVH as the uv coords must be stored somewhere.\n- the new primitives should still be mappable to the original primitives. ", "Generated texture coordinates missing when switching from solid to rendered mode\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.80.0-git.14884cda1ff5-windows64\nWorked: 2.79b f4dc9f9d68b\n\nThe \"Generated\" texture coordinates make textures \"stick\" to the surface, even if the object is being deformed.\nHowever, this does not work as expected in 2.80 with the Armature Modifier, neither in Eevee nor Cycles.\nIn 2.79 in works correctly.\n\nPossibly related: #59275.\nHowever, this bug affects both Cycles and Eevee, while that report only concerns Eevee (and Cycles works correctly).\nThe difference is that here an Armature is used, while that report uses Shape Keys.\n\n[generated.blend](generated.blend)\nThe scene contains a cube with an armature modifier.\n- Open in both 2.79 and 2.80.\n- Press F12 to render.\n- See how the texture mapping differs.", "Render will not load anything but a cube silhouette in a new untouched file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R4 Graphics ATI Technologies Inc. 4.5.14830 Core Profile Context 21.09.04 27.20.20904.1\n\nBroken: version: 3.6.2\n\nSo, when I open in a new file, new to blender and following a tutorial, I go to render the cube immediately, but instead of a gray cube with shading, it is a transparent silhouette. I have touched nothing, just installed from steam, and opened. Then that, IDK what's going on with it.\n\nIDK what to put here, since I didn't do anything.\n\n\n", "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", "Erase Alpha in vertex paint not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\nWorked: latest 2.7 nightly build date 2019/06/27\n\nErase Alpha not showing in viewport.\n\ngo to vertex paint set mode to erase alpha and when painting nothing happens.\nalso found no ways to use the alpha data.\n\nVertex Alpha painting are needed for asset creation on some game engines like creation engine.\n", "Collada import/export: transparent textures don't work\nOperating system: Linux\n\nBroken: blender-3.3.0-alpha+master.dfb8c90324c0, probably all versions since 2.8\nWorked: 2.79\n\nCollada cannot import or export transparent (alpha) textures.\n\nImport this .dae\n\n[BlenderLogoDae.zip](BlenderLogoDae.zip)\n\nThe result (with 2.79 for comparison).\n\n\n\nManually hook up the alpha in the node graph and export. Open the .dae in a text editor and confirm there is no <transparent> element (which sets the alpha texture). You can confirm exporting works in 2.79 by exporting and reimporting.\n\n**Other**\nNote that OpenCollada's parsing of transparency is weird and buggy, see [D11259](D11259) and 651.", "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)" ]

[ "Cube mapping is broken, texture shows up as pink or black.\nOperating system: Linux-4.15.0-70-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Radeon RX Vega (VEGA10, DRM 3.23.0, 4.15.0-70-generic, LLVM 8.0.0) X.Org 4.5 (Core Profile) Mesa 19.0.8\n\nBroken: version: 2.82 (sub 5)\nWorked: (optional) Worked previously today. Don't have version (a couple of days old?), but it had Geometry/Random Per Island (absolutely love this!!!) but not AOVs.\n\nTexture shows up as pink (sometimes black in real projects) when set to box mapping projection. If set to flat, tube, or sphere, texture (same texture object) will show up as expected. Tried object and generated coordinates. Doesn't matter if texture is packed (done here) or not.\n\nIn attached file, go to camera view and show rendered view. For me, the right (box mapped) side renders pink, while the left (flat) renders as expected.\n[BoxMappingBug.blend](BoxMappingBug.blend)", "Box mapping is broken in Cycles\nOperating system: Linux-5.3.0-22-generic-x86_64-with-Ubuntu-19.10-eoan 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.31\n\nBroken: version: 2.82 (sub 5)\nWorked: 2.82, before UDIM was committed\n\nBox mapping in Cycles is broken. \n\nOpen this file and go to rendered viewport. \n[box_mapping.blend](box_mapping.blend)\nIt is rendering as pink here. All other mapping methods such as Flat, Tube and Sphere work fine.\nIn Eevee it works fine as well.\n" ]

[ "Delete Geometry node face mode behaves unexpectedly when used after Join Geometry\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.2.1\nWorked: N/A (problem exists on 3.1.2)\n\n\nNot sure if this is by design, but I find that the following behaviour unexpected:\n\n- By itself, a Mesh Line output connected to Delete Geometry + Geometry Proximity node using Face mode won't delete anything.\n- However, when such a Mesh Line is joined with a Grid primitive, then Delete Geometry + Geometry Proximity in Face mode will cause all of Mesh Line to be deleted, regardless of distances.\n\n\n\n\n\n\n\n\n- Download the blend and observe Mesh Line is preserved.\n- Unmute Grid node link to Join Geometry, and observe Mesh Line is now gone.\n\n[line-deletion.blend](line-deletion.blend)\n", "OBJECT_OT_shape_key_clear ignores slider_min and slider_max\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: version: 2.79, 3.5.1, 4.0.0 Alpha\nWorked:\n\nThe OBJECT_OT_shape_key_clear operator clears the `.value` of each Shape Key, setting it back to zero, but Shape Keys have `.slider_min` and `.slider_max` attributes which specify the minimum and maximum values for `.value`. OBJECT_OT_shape_key_clear does not respect the `.slider_min/max` values when it clears the `.value` of each Shape Key, setting `.value` to an otherwise impossible value when either `.slider_min` is greater than zero or `.slider_max` is less than zero.\n\nAttached is a .blend (authored in 4.0.0a) with steps 1-4 already set up.\n1) Create two non-'Basis' shape keys on a default cube\n1) On the first shape key, set its `.slider_min` to 0.5\n1) On the second shape key, set its `.slider_min` to -1.0\n1) On the second shape key, set its `.slider_max` to -0.5\n1) Click the button in the UI to Clear Shape Keys, or run `bpy.ops.object.shape_key_clear()`\n\n1) Observe that the `.value` of each shape key is now set to 0.0\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", "Geometry nodes. Objects with negative scale have positive scale as instances\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.3.3\n3.4.1 and 3.5 are broken too\n\nWhen I instance from collection, objects with negative scale passes only positive scale to instances.\nCheck file and video.\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", "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", "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "Geometry nodes: Profiled curve have inverted shading with matcaps\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\nBroken: 3.0 release\n\nAs title said. Profiled curve looks properly (left) and profiled with GN looks inverted.\nNormals are okay, studiolight and other shading too (as I see).\nOpen file and compare cylinders, with matcaps (workbench)\n[cprofile.blend](cprofile.blend)\n\n\n[2022-01-11_05-11-45.mp4](2022-01-11_05-11-45.mp4)", "Outliner Floating window Drag & Drop to Geometry Nodes editor not working\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: I don't know if it ever worked\n\nDragging and dropping objects from the outliner to the geometry node editor is not working\n\nFloat outliner to be its own window\ndrag and drop an object from the node editor to the geometry nodes\ndoesn't work.\n\n", "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", "Weird Motion Blur with Simulation Nodes\nBroken: 3.6.2\n\nMotion Blur doesn't work properly with Geometry Nodes instances.\nAs shown in the rendered video, the motion blur seems to give weird results, the motion trails of the instanced particles from the Geometry Nodes (and Simulation Nodes) setup don't seem to follow their direction properly.\n\n<video src=\"attachment\" title=\"animation.mp4\" controls></video>\n\n[Test.blend](attachment)\n- Open file\n- Hit play to bake simulation until let's say frame 45\n- Render frame 45\n\n", "Realize Instances lost Z rotation of Curve Line in certain situations\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 527.56\n\nBroken: version: 3.5.0 Beta\nWorked: N/A, 3.4.1 is also affected\n\n\nDiscovered in Blender.chat, Realize Instances doesn't appear to passthrough some type of curve rotation, for example Z rotation on a (0,0,0) to (0,0,1) curve line is lost during the process.\n\n\n- Download the attached blend file\n- Observe the curve line have random rotation per instances, but didn't result in rotated meshes\n- Disable Realize Instances and observe the instanced meshes are rotated as expected.\n- Enable Realize Instances, instead put an additional (0.001) rotation to X axis with the Combine XYZ node, observe this rotation are kept after Realize Instances.\n- I believe this behaviour should be consistent across all possible rotations.\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", "Line Art doesn't exclude object's instanced by geo node\nOperating system: Linux-6.0.6-76060006-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.3.1\nBroken: version: 3.5.0 Alpha\n\nCollection Line Art includes instances that are distribute my geometry nodes, even if that object is not within the Line Art target collection.\n\n\n[Line_art_Geo_Nodes_instance_bug.blend](Line_art_Geo_Nodes_instance_bug.blend)\n**Exact steps for others to reproduce with example file**\n1. Open Attached File \n2. Observe Line Art is on objects outside target collection\n\n**Exact steps for others to reproduce the error from Startup**\n1. Distribute Objects from a collection with Geo-Nodes\n2. Create a second collection with a Line Art Target Object only\n3. Add Collection Line Art and target collection from step 2\n4. Line Art will be drawn on Geo-Nodes instanced objects\n\n\n\n", "Alpha doesn't work as a mask \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 511.79\n\nBroken: version: 3.0.0\n\nI use an alpha channel as a mask for mix node. If I put an alpha channel from the same node where I take a color channel I get a strange result but if I grab a mask from an alpha channel a copy of the same texture node I get the proper result. \n\n\n\n\n[bug_11.blend](bug_11.blend)\n\n" ]

[ "Regression: Geometry Node: Radius input don't propageted on input curve for Set Curve Radius node\nOperating system: Windows 10\nGraphics card: RTX 3090\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.5.0 Alpha\n\nCaused by 2ffd08e952\n\n## Simplified short description of error\nThe node does not propagate the radius input attribute.\n\nFile example. If you open it, you will see that the attribute captured for the point does not propagate to curves.\n\n[Set Curve Radius missing field_on_all.blend](Set_Curve_Radius_missing_field_on_all.blend)\n\n**Possible fix**\n```lang=Diff\ndiff --git a/source/blender/nodes/geometry/nodes/node_geo_set_curve_radius.cc b/source/blender/nodes/geometry/nodes/node_geo_set_curve_radius.cc\nindex f03f5aa0413..1224ef5dfb6 100644\n - a/source/blender/nodes/geometry/nodes/node_geo_set_curve_radius.cc\n+++ b/source/blender/nodes/geometry/nodes/node_geo_set_curve_radius.cc\n@@ -13,7 +13,7 @@ static void node_declare(NodeDeclarationBuilder &b)\n```\n b.add_input<decl::Float>(N_(\"Radius\"))\n .min(0.0f)\n .default_value(0.005f)\n```\n- .supports_field()\n+ .field_on_all()\n```\n .subtype(PROP_DISTANCE);\n b.add_output<decl::Geometry>(N_(\"Curve\")).propagate_all();\n```\n }\n\n```\n\n##Original short description of error\n\nThe attached file presents a trunk-and-branches Geometry Nodes example where the radii of the points that are used for instancing are used to affect the properties of the (realized) instances. Expected behavior / behavior consistent with old files is shown in the first image:\n{F14210541}\nAnd the new behavior is shown in the second image. The value from the \"capture attribute\" on the points used for instancing is read by all the realized geometry as zero.\n{F14210543}\nThis can be fixed with a \"capture attribute\" node put after the instancing/realization and before the \"set radius\" node.\n{F14210553}\nThis problem does not apply to using the uncaptured value for \"scale instances\" on unrealized instances, nor does it apply to using the uncaptured value for an offset for \"set position;\" it appears isolated to \"set radius\" from what I can tell.\n\nSee attached file.\n{F14210536}\n" ]

[ "Different results when keyframing visual transforms and applying transforms manually on IK constraint\nBroken: v2.82a and blender-2.90-f9d0f59bed4d-windows64\nWorking: never, tested with 2.75a and that even shows this issue.\n\nThere is a difference between using the insert keyframe menu to insert Visual LocRot compared to if you Apply Visual Transform to Pose and then use normal keyframe LocRot.\n\n\n[keyframe-visual-root.blend](keyframe-visual-root.blend)\n- Open the attached blend file.\n- Set a VisualLocRot keyframe on the root bone.\n- See in the graph editor that the orientation is keyed with quaternion (1, 0, 0, 0), even though the bone was visually influenced by the IK constraint.\n- Disable the IK constraint, and see that the root bone moves.\n\n\n---------------------------------\n\nUsing Keyframe Menu (broken):\n\n[2020-05-15 11-24-58.mkv](2020-05-15_11-24-58.mkv)\n\nIterating Keyframe Insertion (Semi-working):\n[2020-05-15 12-02-32.mkv](2020-05-15_12-02-32.mkv)\n\nManually applying transforms to Pose (working):\n\n[2020-05-15 11-29-47.mkv](2020-05-15_11-29-47.mkv)\n", "Timeline > Playback > Follow Current Frame Does not work if you drag the frame number widget.\nOperating system: Win 10\nGraphics card: AMD R7 200\n\nBroken: Blender 3.61 release.\nWorked: never, checked back till 2.83.20\n\nFollow Current Frame only works with keyboard arrow keys and ALT+Middle mouse button dragging in the timeline editor area\nDoes not work with the click and drag area of the Timeline header current frame box, or its arrow buttons\n\nAs show in attached video\n1. Open Default General file\n2. In the Timeline, Click on Playback > Follow Current Frame\n3. Drag the frame number widget, the frame indicator will go outside the region, while if use play or keyboard arrow keys, region follows the frame indicator.\n4. Expectation is that it should follow the frame, regardless of where the current frame is being changed from.\n\n", "Pen input UI/UX issues\nThis task keeps track of the UI/UX related design issues in all Blender mode that don't work as intended or can greatly improved with pen input devices. \nIf we consider that most pen input devices have at least one button in the pen, this will mostly include feature that rely on mouse wheel events. \n\n\n## Edit mode\n\n- ##Number of Cuts## of loop cut and slide can't be controlled during modal operation, needs to be adjusted with the redo panel.\n- Proportional editing size can only be adjusted incrementally with keyboard shortcuts instead of with pen gestures (like brushes in all modes)", "GPencil: Square type strokes do not react to Rotation option with Solid Shading\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBroken: version: 3.0.0 Alpha\nWorked: ?\n\nThe stroke type Squares draw little squares at the points of the stroke. The rotation is controlled by the alignment option and the rotation slider, which in this case does nothing if solid shading mode is selected. Note that textures are not displayed in solid shading mode and even if used the squares don't rotate as long as I am in solid shading mode.\n\n1. Add default Stroke Grease Pencil Object\n2. Navigate to the Material and change Line Type to Squares\n3. Make sure you are in Solid Shading Mode with \"Color\" not set to \"Texture\"\n4. Change the Rotation slider from the same panel, which says in the tooltip it should rotate the squares\n5. observe how the squares do nothing at all.\n\n", "Metaballs with drivers hangs Blender\nOperating system: Ubuntu 21, Windows 10\nGraphics card: Nvidia GeForce GTX 1060\n\nBroken: 3.1\n\n1. Add metaballs to scene.\n2. Add drivers changing the scale of the balls by moving an empty.\n3. Move the empty. Blender hangs or crashes.\n\nLoad the attached .blend file. Move the empty along the X axis.\n\n[Fade_1.blend](Fade_1.blend)", "Force fields don't work on a fire simulation with Flame Smoke 0\nOperating system: Windows 7 (64 bits)\nGraphics card: Radeon R7 200\n\nBroken: 2.83, 2.92.0\nWorked: -\n\nSetting the Flame Smoke to 0 makes the fire simulation to ignore all forces except gravity.\n\n* create a Quick Smoke simulation\n* set the Flow object to Fire, behaviour to Inflow\n* set Domain object Flame Smoke to 0 in the domain object of a fire simulation\n\nI've also added a particle system to visualize the force, while the fire remains unaffected:\n\n\nHere's a test file:[fire-test.blend](fire-test.blend)", "GeoNodes: Getting animated/driven Curve Radius doesn't work if curve has shape key\nOperating system: Linux-6.2.2-gentoo-x86_64-Intel-R-_Core-TM-_i9-9900K_CPU_@_3.60GHz-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\n\nBroken: version: 3.6.0 Alpha\nWorked: Likely never\n\nThis is a pretty specific set-up on the old Curves, so I'm not sure if it's something that needs to be fixed or if this datablock is getting replaced anyways, but I thought it would at least be good to be aware of.\n\nIf a curve has a shape key, the GeoNodes \"Radius\" node seems to fail to return the correct radius value.\n\nI don't know for sure if this is really a GeoNodes issue, though, because from my testing, the way the Radius value works with shape keys just seems pretty weird. It makes a fair amount of sense until the Radius value gets a driver. At that point, the shape key seems to take on whatever value the Radius had when leaving edit mode.\n\n- File: [radius_driver_not_working.blend](attachment)\n- Scale the bone; The curve point's radius is hooked up to be driven by the bone's scale, and the sphere is created by GeoNodes based on that curve point's radius. So, when you scale the bone, the sphere gets bigger.\n- Add 2 shape keys to the curve\n- Scale the bone again; Sphere doesn't scale any more.\n\nFor my use case, I don't actually need shape keys on my curve, so this won't be an issue for me at all, I just ran into it because I happened to have a temporary shape key on there and I thought I would report it.\n\n", "Keyframed parameters are not preserved when frame_change_post handler is used\nOperating system: Win 10 Pro\nGraphics card: GTX 1080\n\nBroken: v2.81, master, 2018-11-26\nWorked: (optional)\n\n---\n\n\n**EDIT** by @EAW \n\n\n> In the .blend file setup, the 'mesh_cache' object would instance a cube over the vertices for display in rendering. An ocean modifier is added to the object with 'Geometry' set to Displace and the 'time' parameter is keyframed over a frame range. \n> \n> Playback in the viewport shows the ocean modifier evolving shape during the animation. If the animation is rendered, the ocean modifier does not evolve over time and the render result is static.\n> \n\n\n\n> Here is a script that generates a 2d grid of vertices in the frame_change_post handler:\n> \n> ```\n> import bpy\n> \n> def frame_change_post(scene, depsgraph):\n> # Generate a 2d grid of vertices. A cube object is set to be instanced over the vertices for rendering\n> vertices = []\n> for j in range(100):\n> for i in range(100):\n> vertices.append((i * 0.05, j * 0.05, 0.0))\n> \n> mesh_cache_object = bpy.data.objects.get(\"mesh_cache\")\n> mesh_cache_object.data.clear_geometry()\n> mesh_cache_object.data.from_pydata(vertices, [], [])\n> \n> depsgraph.update()\n> \n> \n> bpy.app.handlers.frame_change_post.append(frame_change_post)\n> ```\n> \n\n\n\n\n> Here is the .blend file including the script: [keyframed_modifier_bug.blend](keyframed_modifier_bug.blend)\n> \n> How to reproduce:\n> 1. Open .blend file\n> 2. Press 'Run Script'\n> 3. Blender > Render > Render Animation\n> \n> The result is a static animation.\n\n\n**End Edit**\n\n---\n\n\n\nI have created a FlipFluids simulation in Blender 2.81 ( 2019-11-25 21:45) and added an Ocean modifier in displacement mode to the fluid_surface. Then I have baked the complete sim from within FlipFluids.\nWhen I move from keyframe to keyframe in the default timeline everything is moving as desired in the default 3D window:\nOcean modifier waves, FlipFluids waves & wake, flags, radars...\n\nWhen I render the complete animation everything EXCEPT the ocean modifier waves are moving. The ocean modifier waves remain static but the FLIPFLUIDS waves move on that surface.\nALL modifiers and elements ARE enabled for renderings. D-NOISE: AI Denoiser is on (switching denoiser off did not help).\nComputer is a HP Z800 with dual Xeons, 72 GB of vRAM and a GTX 1060.\n\nIf I render & save the keyframes manually individually by hand the ocean surface moves! Which means I get the proper result.\n\nAs its working when rendering&saving each frame manually as image (Png) and its not giving the same result when saving out the same images (Png) when I hit render animation, I do suppose this might be a bug in 2.81.\nRunning indiviual frames via Renderpilot did not yield the proper result either. So I do suspect it might be that there is not enough time gap between saving the last frame and rendering the next. Or, something does not get purged properly.\n\nFor propriatary reasons I can not share the blend file.", "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 hangs due to deadlock caused by two registered draw handlers\nOperating system: Only happens on Linux (Ubuntu 22.04)\n\nBroken: 3.2.2\nWorked: unknown\n\n\nWhen my addon is used together with the addon [\"node minimap\" ](1366781), Blender hangs/freezes completely under certain conditions (details below).\nTo close Blender in this state, not even Ctrl+C is enough, it is necessary to close the parent terminal from which Blender was started.\n\n\n[addons.zip](addons.zip)\n\n[test.blend](test.blend)\n\n- Install the two addons \"node minimap\" and \"test addon\" from the attached zip file.\n- Enable both addons (search for \"node\" in the addon list to find both).\n- Open the blend file.\n- Convert the editor on the lower left to a Shader Editor.\n# Blender will immediately hang.\n\n\n", "Rigid body : the animation of the angle constraint parameters does not work with an animated object\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: 2.92\nWorked: don't know \n\n\nRigid body : A rigid body \"animated\" object + a another rigid body object connected with hinge rigid constraint. The animation of the angle constraint parameters does not work with an animated object. I have bugs sometimes also with other parameters like breakable . (see the blend)\n\n[rigidconstraint.blend](rigidconstraint.blend)\n\n", "Node editor: zoom is affected by DPI\nOperating system: macOS-12.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 460 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.2.2\nSame on 3.3.0 beta and 3.4.0 alpha\n\nGeometry nodes panel does not re-scale when Blender window is moved to a display with a different DPI (e.g. retina to non-retina display, in Apple's parlance). Everything else in the GUI gets re-scaled correctly.\n\nSee attached screen-shots.\n\nHave 2 displays - one with a higher DPI.\nOpen Geometry Nodes panel.\nMove Blender window from one display to another.\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", "Annotations do not scale in the Shader Editor with the Resolution Scale or Windows Display Scaling\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.3\nWorked: Couldn't find one. Tried 2.90 beta too.\n\nAnnotations made in the Shader Editor do not scale with the interface, either with the Preferences resolution scaling or with Windows Display scaling. This is problematic when reviewing annotations made on a computer using a different screen scale as notes do not line up.\n\nGo to Shader Editor - Add default material/nodes for scale reference.\nT - for left toolbar. Select Annotation tool.\nAdd annotation to the screen, e.g. draw around a node.\nOn the Menu > Edit > Preferences > Interface \nChange the resolution scale.\nNodes will scale. The annotation marks will not.\n\nSame behaviour is observed by changing the Windows Scaling % in the Windows Display 'Scale & Layout' menu.\n\n\n\n", "Wayland: Cursor hover effect flickers when scaling a Blender window\nOperating system: Fedora Linux (Wayland, Gnome Shell 44.1)\nGraphics card: AMD\n\nBroken: 3.5.1\n\nWhen scaling a Blender window the buttons get highlighted under the position the cursor was at when starting to scale the window.\n\nI'm not sure if the flickering shown in the video is related or belongs in it's own bug report.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nGrab the Preferences window next to a button to scale it bigger.\nThe button and sometimes one other button will flicker once a button reaches the position the cursor started to scale at.\n\nThe \"original cursor position\" is only updated when hovering the cursor over the window again, not when sliding along the edge of it.\n\n" ]

[ "F-Curve Handles cannot be scaled along x-axis in Graph editor\nOperating system and graphics card\n\nWindows 7, Intel Integrated\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\nBlender 2.70\n(I'm nearly certain this worked fine in 2.69)\n\nThe handles on Keyframes in the Graph Editor along the x-axis cannot be Scaled (stretched) along the x-axis. In the past, you could go to an individual frame, highlight, for instance, the LocRotScale frames, and then go S > X, and those bezier handles would all stretch out. Now, they do not budge.\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n(1) Select the default cube\n(2) On frame 1, Keyframe the LocRotScale\n(3) On frame 20, move the default cube and again Keyframe the LocRotScale\n(4) Go to the Graph Editor and highlight the Keyframes on frame #20. To try and make the animation slower, go S > X to stretch the handles out. They will not budge.\n\n(As a note: This has a MAJOR impact on my personal Keyframing - and so I would guess on that of many other users, too. Very often, when I'd want to just make the animation a bit slower, I'd stretch them out. Or, if I wanted a jarring start or end to an animation, I'd just go S > X > 0. Now, none of that is possible, and every single Keyframe has to be moved manually. This is VERY time-consuming and also imprecise.)" ]

[ "Particle edit mode - Hide hairs doesn't work\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\n\nBroken: version: 2.80 (sub 50)\nWorked:\nThe \"hidden\" hairs can't be selected or edited\n\n\nThe hidden hairs are still visible.\n\nAdd a hair system to the default cube \nSwitch to particle edit mode and then switch to point display/select mode\nSelect any number of particles, press H to hide\n- >The hairs are only locked, not hidden\n\n\n", "Modifiers added in edit mode are undone out of order if you go back to object mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 13)\nWorked: Never (2.8+)\n\nModifiers added in edit mode are undone out of order if you go back to object mode and then start undoing.\n\nAffects both old and new undo system. There's often mentions of edit<->object transitions being problematic but just in passing; I think this is a long standing issue. Just wanted to note it down as I test out the undo systems.\n\nHoping the new undo system can account for this now.\n\n- Default scene\n- Go to edit mode on the default cube\n- Add any modifier (bevel, subdivision, etc.)\n- Add any loop cut 1\n- Add another loop cut 2\n\n- Go to object mode\n- Undo --> Modifier is removed first (out of order)\n- Undo --> Loop cut 2 is removed\n- Undo --> Loop cut 1 is removed\n\n\n", "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)", "Wrong interaction by extrude region with 2 cube's faces\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.22\n\nBroken: version: 3.1.0\n\nWhen extrude the \"z\" and \"-x\" faces of cube they extrude up \n\n* Create a cube\n* Choose edit mode\n* Select \"z\" face(top of cube) and \"-x\" face\n* Use Extrude Region or press E\n\n{[F12930516](image.png), size=full}\n\nThanks!", "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)", "Inset faces and Bevel Edge command has bugged interaction with Undo command and shape keys\nOperating system: Windows-7,10\n\nBroken: version: 2.83 (sub 2)\nBroken: version: 2.82 (sub 6)\n\n\nIn edit mode, while selecting a shape key, the Inset operation (I) followed by any other operation (Translating vertices or extruding or whatever), followed by an Undo (Ctrl-Z) command causes the shape key selector to hop to the \"basis\" shape key. This also occurs when using the `Bevel` command.\n\nFrom Default Startup:\n1. Create two shape keys: \"Basis\" and \"Key 1\"on Default Cube. Selection will be on \"Key 1\"\n2. Go into edit mode\n3. Inset a face on any of the existing faces with \"I\"\n5. Do ANY other operation or operations, such as moving a vertex or extruding. The bug occurs with any number of operations done after the Inset command.\n6. Undo (Ctrl-Z)\n7. Observe Shape key information as the undo command causes the selection to switch from \"Key 1\" to \"Basis\".\n8. Keep `Undoing` until you `Undo` the `Inset` operation.\n9. Notice that the shape key selection jumps back to \"Key 1\" as you `Undo` the `Inset`. \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.", "overlays extras option being ignored\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Beta\nWorked: (unsure, definitely 2.8 possibly 3.0)\n\nbounding box representation of particle instanced geometry (hair) where the object being instanced is set to bounding box is not being hidden from the viewport when the 'extras' option is checked. \n\n\n", "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", "Tracking: Selecting camera maker in 3D-View with other active camera\nWhen fixing #72162 (Crash when selecting camera maker in 3D-View when different camera is active) we came into uncharted territory. This task is for the expedition to this territory.\n\nIn the setup where you have a track connected to a camera, but have activated another camera, the selection logic is not working.\nIt is expected that when selecting a marker in this case, it would select the camera where the marker belongs to and select the marker that is under the mouse button.\n", "Mirror Modifier On Cage Selection Papercut \nBroken: 2.93.4\nWorked: Maybe never.\n\nWhen in edit mode, using the \"On Cage\" option for the mirror modifier results in some unintuitive behavior when selecting vertices created by the bisect feature. The vertices created by the by the bisection are mapped to the original mesh data in a way that appears to be based on blenders internal representation of the mesh and not based on something observable to the user.\nThe behavior when selecting should feel consistent to the user. To fix this, I suggest that the vertices created by the bisection should always map to the vertices on the original mesh that are on the removed side of the bisection plane. This way users would be able to tweak the centerline of the mirrored mesh in while using \"On Cage.\" As it is currently implemented, there are vertices that affect the mesh that cannot be accessed through normal click selection unless \"On Cage\" is off.\n\n**Example**\n\n\nSelect the +X or -X face of the default cube and scale it by 0.5.\nAdd the mirror modifier and select bisect for the X axis so that the object is mirrored and bisected about the X axis.\nTurn on \"On cage\" for the mirror modifier then enter edit mode for the object.\nWhen selecting the vertices on plane X=0, you should notice that two of the vertices correspond to visible mirrored vertices and two correspond to vertices removed by the modifier. \n\nSimple scene showing the behavior. \n[MirrorSelectOnCagePapercut.blend](MirrorSelectOnCagePapercut.blend)\n", "Option to lasso-select using geometry instead of object centers.\nCurrently lasso-select in object mode uses object centers,\n\nThis can have the option to select using the geometry (like box select does already).\n\nSee #64251", "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.", "Cycles: transparent object has black line where it intersect with other objects\nOperating system: Windows-10-10.0.18363 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 461.40\n\nBroken: 2.91.2\n\n\nWhen rendering transparent objects that intersect with other objects, black lines will appear on the intersecting area.\n\n1. Open a default scene.\n2. Add a plane to the scene.\n3. Rotate the plane a little.\n4. Move the plane up to make it intersect with the top face of the default cube.\n5. Make sure the view or camera view is very close to the intersecting area and lower the Clip Start value to 0.00001\n6. Set the renderer to Cycles and render the view.\n\n\n\n[Cycles_Black_Line_Transparency.blend](Cycles_Black_Line_Transparency.blend)", "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)" ]

[ "Multi-Object-Mode: EditMesh GL selection objects don't occlude eachother\nCurrent GL selection for edit-mesh is performed once per mesh, so objects don't occlude eachother.\n\nThis should be modified so all meshes are drawn in the same pass (assigning indices to ranges).", "Multi-object editing, wrong selection priority\nOperating system: Windows 10, Intel Core i7\nGraphics card: Nvidia GeFroce GTX1060\n\nBroken: 2.80, 61a816e8ff0, blender2.8, 2018-12-18\n\nWhen multiple objects are in edit mode, it is hard to select a component of the object in the front, this doesn't happen when the object are joined.\n\n- Select two objects\n- Tab into edit mode, edge mode for example\n- Make it so one object is in front of the other one\n- Try to select an edge by clicking on a face\n\nThis should have the same effect than when one object is in edit mode, selecting one of the edges around the face. But it often select an edge of the other object." ]

[ "Some transform modes don't apply absolute grid snaping \nOperating system: Windows 10 \nGraphics card: GTX 1080 ti \n\nBroken:\nBlender 2.8 January 31, 01:48:40 - 8c8979067490 Beta\nBlender 2.79 (It worked)\nBlender 2.77 (It worked)\n\nAbsolut grid snaping dont work with \"Face Inset\" and neither with loop cuts. \n\nTurn on the snaping (increment) -> turn on absolut grid snaping -> spawn a plane -> try to snap while loop cutting or inseting faces.", "Sculpt Mode: Edit Voxel Size hotkey conflict\nOperating system: Win 10\n\nBroken: blender-2.90-51ac411ce80c-windows64\n\nThe \"Edit Voxel Size\" and the \"Repeat Last\" functions are using the same hotkey (Shift+R), and as a result, the \"Repeat Last\" command is not working in sculpt mode.\n", "Shortcuts for Tools (design task)\nOne of the major issues with the tool system, is that switching tools isn't easy enough using the keyboard with the default keymap. \n\nWe would like to introduce a way to make the keyboard shortcuts switch tools, without having to click on the toolbar, or opening menus. Here's how we think we can solve it:\n\nWe want to leverage muscle memory for shortcuts users already know, such as G, R, S for the transform tools, as well as K for Knife, Alt-S for Move Along Normals, and so on. \n\n## Leader Keys\nTo do this, we use the concept of *leader keys* (also known as *chained keys*). This makes it so that tapping (but not holding) a modifier will change the following shortcut. In this case we think we will use Alt to switch tools. \n\nIn practice, this means users will tap Alt, then G to switch to the Move tool, and so forth.\n\n## Visual Feedback\nWe want to make it obvious that a leader key has been entered, so that users know that the following key stroke will differ from normal. We do this in a few ways:\n\n**Status Bar**\nHere we can see the leader key, plus the shortcuts:\n{[F7753731](Screenshot_2019-09-15_at_21.50.34.png), size=full}\n\n**Toolbar**\nAfter the leader key is pressed, we can also display the hotkeys inside the toolbar buttons. This gives a more direct association with the tools in the toolbar and their corresponding shortcut. \n{[F7753735](Screenshot_2019-09-15_at_21.43.58.png), size=full}\n\n## Implementation\n\n- Pressing Alt and releasing (without pressing another key) would prompt for input.\n - Pressing any of the mapped keys would activate the tool immediately. \n - Pressing any key not mapped - such as painting or using mouse buttons to pan the view - would cancel the prompt and perform the action (preventing unintended leader key press from Blocking other actions). Pressing escape would also cancel.\n\n## Precedents\n\n- Firefox supports accessing menu this way (Tapping Alt, then F opens the file menu).\n- Typing in accent characters on macOS uses [leader-key like functionality. ]()\n- Spacemacs relies heavily on a [leader key ](QUICK_START.html#the-leader-keys).\n\n", "Using Viewport Navigation Gizmos can execute tool gizmos or sculpting\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.91.0 Alpha\nWorked: never worke in 2.8+\n\nLeft Mouse dragging on those two buttons can lead to unexpected/undesired behavior. \n\nThe dragging executes whatever tool is currently active:\n- if the selection tool is active, a selection is drawn\n- if the move tool is active and an object selected, the object is moved\netc.\n\nWhy this is a problem:\nIf one of these two buttons get accidentally dragged a little, it can apply a tiny yet destructive change to your scene which isn't noticed at first (as this behavior is unexpected).\n\n\n\nThis example is for the move tool:\n1. Open a new scene\n2. Activate the move tool\n3. Select the cube\n\n4. Drag the camera or perspective button to the side\n5. See how the cube is moved\n\n\n\nThis example is for sculpting:\n1. Open new sculpting scene\n\n2. Drag the camera or perspective button to the side\n3. See how the mesh gets distorted\n\n\nThanks\n", "Snapping: Make 'Absolute Grid Snapping' a new Snap Mode\nHaving `Absolute Grid Snapping` as an option for `Increment` does not seem ideal.\n\nIncremental Snapping means to snap to values that increment the current position.\n\nGrid Snapping means snap to grid.\n\nHaving `Grid Snapping` as an option also limits its use because `Increment` does not use a pivot or base point for transformation.", "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", "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.", "Edges are selected in face mode when deselecting vertices from vertex group Panel\nBlender Version\nBroken: Current main.\nWorked: N/A.\n\nShort description of error\nDeselect Button in Vertex Groups Panel will deselect vertices that are not assigned to any groups. Edges become selected while in Face Mode as well. Also the Select Button will Select Faces that are not assigned too but those Edges that are active in face mode must be Selected for the Bug to work. Pay attention to the Edge around the triangle Fan at the top of the uv Sphere While in face mode.\n\nBlend File Incuded for simplicity\nJust Press the Deselect and notice the Faces that Get removed. and the Edges are actively Selected.\n\n", "Handle Type selector in the Graph Editor's sidebar sets different types than selected\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 517.40\n\nBroken: version: 3.3.0\nWorked: Don't know if it ever worked before or when.\n\nWhen choosing the type of handle for a keyframe in the Graph Editor's sidebar, the options don't work as expected. Selecting \"Vector\" sets the handle to \"Free\", and selecting \"Automatic\" or \"Auto Clamped\" sets it to \"Aligned\".\n\nNot sure if this is expected behavior, but choosing an option to get a different one be set felt weird. Most of all, I couldn't set it as Vector from there, so I had to press V in the Graph Editor and do it from there. Interestingly, then it appears as \"Vector\" in the sidebar as well.\n\nI'm attaching a screenshot of the menu I refer to, and a .blend prepared to reproduce the issue (any file with an animation would do).\n\n\n\n1. Create an animation (already present in the attached .blend file)\n2. Open a Graph Editor\n3. Select a keyframe\n4. Open the Graph Editor's sidebar\n5. Try to change the handle type options in the F-Curve tab of the sidebar\n\n[Handles Issue.blend](Handles_Issue.blend)\n\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)", "GPencil: Hotkeys of Tools is not consistent when Draw Tool is active\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.76\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nI'm not sure whether this is intended or not.\nHotkeys (1 to 9) shift downward one by one depending on whether you are in a draw tool or not.\n\n1. Go to Draw Mode\n2. Select a draw tool by pressing Shift Spacebar, O (Not 1)\n3. Select a fill tool by pressing Shift Spacebar, 1\n4. Select a draw tool by pressing Shift Spacebar, 1 (Not O)\n\n", "Connected Proportional Editing cuts of in special case\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.2.0 Alpha\nWorked: ?\n\nWhile creating the ladder as attached, connected proportional editing seems to be stopped at certain points. It deforms the points near it, but as soon as it gets around one hole it does not propagate any further. This issue only appear with this indice order of the mesh.\n\n\n\n[connecteddeformbug.blend](connecteddeformbug.blend)\nTo prove that it is not a corrupted mesh, here is how to create it: (follow the steps exactly, otherwise it might not work)\n1. Create a plane object and tab into editmode\n2. Scale the plane 0.3 along the X-axis\n3. Add 3 loop cuts simultaneously to make almost squares (so there are 3 new edges pointing along the x axis)\n4. select everything and inset individual faces by 0.1.\n5. delete the interior faces (all at once) to get a ladder-like geometry\n6. try moving the long internal edges on the -Y side of the mesh.", "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).", "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", "bpy.ops.object.vertex_weight_copy() fails in multi edit mode\nOperating system: windows 10 amd ryzen 9 5950x 2 x 3090 (not in nvlink)\nGraphics card:\n\nBroken: 3.12\nWorked: don't think it ever has\n\nin multi edit copy vertex to selected fails and does not create new groups or copy the weights, you have to join the mesh first then do copy to selected then separate the mesh again which is problematic in more complex rigging scenarios with shape keys etc. \n\nincluded example blend file with both meshes selected tab into edit mode highlight 1 vertex on the cylinder and then select all the verts on the ico sphere and select copy, the copy fails. If you join the ico sphere to the cylinder mesh and do the same it works as expected.\n\ngoing to write a script as a workaround but I think it's really a bug ? (all be it a small one :-) )\n\n\n[copyfail.blend](copyfail.blend)" ]

[ "Poly Build: created vertices not snapping on high poly surface\nOperating system: Linux-4.15.0-66201911071317-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nOne would expect the poly-build-tool to create new vertices on the surface of the high poly mesh that one is going to retopo. That's not the case with snapping enabled.\n\n- Open attached .blend file.\n- With the Poly Build tool try to use the ctrl-click-thing to extrude a new vertex on the monkey's surface (snap should work).\n- Enable the toggle `Snap`.\n- Try the ctrl-click-thing again and note that snapping doesn't work.\n[tmp_T72913.blend](tmp_T72913.blend)\n\n\n" ]

[ "Solidify modifier rotates custom normals incorrectly\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.93\n\nBroken: version: 3.4.1\nWorked: not as far as I know.\n\nWhen solidifying an object with custom normals, the newly created geometry rotates (destroys) these normals on the newly created geometry. So a smooth surface gets a non-smooth (faceted-looking) surface on the other side. \nHowever, activating the Normals --> Flip option in the modifier actually produces the correct (smooth) normals on the new geometry, but destroys the custom normals of the original surface. The newly created surface then has flipped normals, but these can be flipped again inside edit mode after applying the modifier. They are then facing the right way and still smooth. So the modifier actually has the code to correctly calculate the new split normals.\n\n\n- Take a mesh surface with custom normals, make two copies.\n- Object 1: Add a solidify modifier with a relatively small thickness. Look at the newly created surface: it's not smooth but faceted. \n- Object 1:Apply modifier, turn on display of custom normals, zoom in on new geometry: the normals on the new vertices are divergent.\n- Object 2: Add a solidify modifier activate with Normals --> Flip. Look at newly created surface: it's smooth as the original one. Great. But the original surface is now broken up and not smooth.\n- Object 2: Apply modifier, turn on display of custom normals, zoom in on new geometry: the normals on the new vertices are identical, do not diverge, they are simply facing the wrong way. Apply \"Normals (ALT-N) --> Flip\", now they are correct.\n\nSo basically there is a work-intensive workaround (which also means losing the flexibility of having a modifier): make two copies of the object, add modifer with flipped normals, apply, flip normals again in edit mode, manually select and delete original geometry, join with the original object (original geometry). This is what the modifier itself should be doing.\n\n- See the attached Blend file. Four objects: original, two solidify copies, and one created with the workaround.\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", "Scaling in edit mode with individual origins and snapping activated is broken\nWin7 x64\n\nBroken: 2.76\n\nFollowing #39161. Scaling in edit mode works well with \"median\" as pivot point but with \"individual origins\" it breaks.\n\n\nIn attached file:\nScale and choose a vertex with \"ctrl\" pressed, cube seems to disappear.\nTo compare, press \"G\" and choose a vertex for snap, the cube's center is moved as a cube (also individual origins could make all selected verts move to that position making a point instead of a cube?) to that vertex.\nScale with \"median\" as pivot, it works\n[bug scale individual origins.blend](bug_scale_individual_origins.blend)\n\nSo maybe to make it consistent, make \"individual origins behave like median.\n", "Knife Tool. No preview dot of where the cut will start.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nWhen activating a knife tool, the preview dot of where the cut will begin does not show up. So i do not know if the cut will begin on a face, or on an edge, and i can't see if it snaps to a vertex, etc. I can see all of this only when i actually begin a cut. \nA desirable behavior is when i activate a knife operation with \"k\" key. \n\nCreate a cube. Enter edit mode. Select a knife tool. Point it on a mesh. There is no green dot projected on mesh, indicating where the cut will start.\nOn the other hand, when in edit mode, press \"k\" and you immediately see where the cut will start, and if ctrl is pressed - to which place it snaps.[Knife_Tool_cube.blend](Knife_Tool_cube.blend)\n\n", "Subdivision surface modifier creates self-overlapping geometry on coplanar non-triangulated face\nOperating system: Linux-5.15.5-76051505-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2) Intel 4.6 (Core Profile) Mesa 21.2.2\n\nBroken: version: 2.93.4 -- confirmed in 3.1a 12/20/2021\nWorked: Unknown\n\nWhen set to simple, the subdivision surface modifier creates self-overlapping geometry with certain concave polygons on non-triangulated coplanar face:\n\nCan be related to #61145. See steps for more details.\n\nThis affects the `Subdivide` node in Geometry Nodes as well. \n\nAttached file have needed objects to reproduce.\nIn image is different examples of issue, from left to right then top to bottom:\n1. Plane with `Simple` subdivision surface modifier, works as expected.\n2. Plane with top-left vertex moved so that it's edges have angle >180 degrees. When moving either right, down or towards bottom right vertex issue will show itself. In this working state sum of this vertex angle and it's neighbors is strangely close to 270 degrees (with remaining bottom-right vertex having 90 degrees).\n3. Vertex moved close to opposite one. In `Top` view it shows that this unnecessary face have back normal but if you move viewport aroung you'll see it's gliching, overlapping with another face that have forward normal.\n4. Case where top edge of a plane is subdivided and created vertex moved to center to the point of glitching. See that on the right it shows back face normal but on the left it shows different color which I don't really know what it means.\n5. Showcasing slightly different glitch. When troubled vertex moved top/right face with back normal will disappear. That might be filed as separate report.\n6. Same as - [x] but bottom-right vertex also moved close to top-left one. Notice that while top-left vertex not moved from it's \"glitchless\" position in - [x] there is still bug.\n\nIssue is gone if face is non-coplanar. That can be seen if in attached file second collection made visible:\n\nThat is same meshes as before but with troubled vertices moved down Z axis. If view is rotate the cause for self-overlapping geometry can be seen. That's example [3]:\n\nWith that topology it's clear that if you move vertex so that face becomes coplanar you'll get self-overlapping geometry. \n\n`Simple` mode of subdivision surface definitely doesn't befave like `Subdivide` in Edit mode. You can see that in non-coplanar example [1]:\n\nWhen entering Edit mode transparent initial mesh without modifier is shown. If it behaved like `Subdivide` then it would not be shows because of full match with modified geometry.\n[examples subdivision coplanar non-triangulated.blend](examples_subdivision_coplanar_non-triangulated.blend)", "Creating UV Maps from Face Sets\n# Issue\n\nThis is based on a popular request from users.\nOn very high density sculpts with messy topology it's very time consuming to create UV seams and unwrap the UVs.\n\nFor that case it can be a fast solution to use face sets from sculpt mode to create a new UV map.\nSome users already started creating geoemtry node operators and addons to acheive this:\n2017\n\n<video src=\"attachment\" title=\"face_set_to_uv.mp4\" controls></video>\n\n# 'Unwrap Face Sets' Operator\n\nTo get proper feedback on the new UV map it might be best to add an operator \"Unwrap Face Sets\" to the \"UV\" menu in the UV Editor.\nThen the easiest steps to create a UV map from Face Sets is to switch to the UV Editing workspace and do the needed operations there.\n", "Wrong interaction by extrude region with 2 cube's faces\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.22\n\nBroken: version: 3.1.0\n\nWhen extrude the \"z\" and \"-x\" faces of cube they extrude up \n\n* Create a cube\n* Choose edit mode\n* Select \"z\" face(top of cube) and \"-x\" face\n* Use Extrude Region or press E\n\n{[F12930516](image.png), size=full}\n\nThanks!", "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.", "Crash when baking a normal map from procedural materials\nOperating system:\nManjaro w/ KDE\nGraphics card:\nNvidia GTX 1060 6GB\n\nBroken: 2.80 Beta, 5e626e766459, branch: blender2.7, 2019-06-13\n\n\nI've sculpted a high poly model from the lowpoly one - baking normals from that works fine.\nWhen I created procedural materials using Geometry Pointiness, Noise, a painted texture and other sources to create additional normal information - the baking crashes.\n\nHere's the project file. It's huge (781 MB), but compresses very well (turns out the painted texture was wasting a lot of space), without it the file is only 12 MB).\n\n[Barrel_02 08.zip](Barrel_02_08.zip)\n\nNormal map baked from Highpoly model to Lowpoly model:\n\nIf you disconnect the two materials on the highpoly model and just use a default Principled shader, it bakes fine.\n\n\nThe baking process crashes at various stages. First bake crashed after an hour or so, next attempts crashed much quicker.\n\nCrash logs:\n\n[Barrel_02 08.crash.txt](Barrel_02_08.crash.txt)\n\n[Barrel_02 07.crash.txt](Barrel_02_07.crash.txt)\n\n[Barrel_02 06.crash.txt](Barrel_02_06.crash.txt)", "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", "Some particle hairs that emitted from the vertices do not rotate with the armature.\nOperating system:MacOS\nGraphics card:Radeon Pro\n\nBroken: 2.93.2\n\n\nSome particle hairs that emitted from the vertices do not rotate with the armature.\n\n\n\n\n\n\n\n\n\n[Hair Rotation bug.blend](Hair_Rotation_bug.blend)\n\nSimple example wit a cube:\n[#89749.blend](T89749.blend)\n\nIssue only happens when emitting from Vertices (emitting from faces is fine)", "Unselected nurbs vertices occlude selected ones\nBroken: 2.80 , 2.92\nWorked: 2.79\n\nCan't select Nurbs Sphere's top points with simple left click. It's only selectable with box selection.\n\n\nAdd nurbs sphere\nEdit mode\ntry to left click select the central top points.", " Improve PBVH building performance or PBVH_FACES\nIn high poly meshes, PBVH building for meshes could take several seconds, which affects performance when switching objects and when using tools that modify mesh topology (remeshers, mirroring trimming...).\nAs mentioned in #68873 it can be improved by multithreading it. \n\n", "UV: Mesh won't Unwrap at all\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nWhat is happening is that when i unwrap my mesh nothing happen, even if i isolated one face and tried to unwrap it wont work, also even faces you extruded from the faulty face won't unwrap, but adding a new plane from the add menu inside the same mesh unwraps normally, even if i connected the plane to the faulty face.\n\n1. Create a plane.\n2. Give one edge a Mean Bevel Weight from the side bar.\n3. Give the plane a Bevel Modifier and the Limit Method set to Weight (visually nothing will change since its just a plane but the error will still reproduce).\n4. Apply the Modifier and Unwrap the plane. (normally the plane comes unwrapped by default, try changing the UVs out of bounds or scale them down just so you can notice the change ).\n\nThanks you blender developers.", "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." ]

[ "Poly Build Tool CTRL Hotkey Possible Design Flaw / Oversight Conflict With Snapping To Grid\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nWhen using the Poly Build Tool, if I drag out a new polygon from an existing edge while holding CTRL ( this allows me to create a new triangle without adding a new edge, or more accurately, instead of creating a new polygon from the two points of the respective highlighted edge in addition to a new point inbetween, where you clicked, it adds a new vertex to the existing polygon to which that edge is connected, therefore extending the number of sides to the existing polygon, which, if it was previously a triangle, as is typical, is a necessity to sustain good topology ), and what I have just found is that CTRL is used generally to enable snapping throughout the application as a whole, i.e. if at the object level I select and then move an object while holding CTRL, while it remains pressed snapping to grid will be enabled. Therefore, the problem is more or less at face value a flaw or oversight in the design of this tool. Consequently this makes learning to use the tool less intuitive, and, when I resorted to an online tutorial in order to learn how to use this new tool, because they did not point out that generally speaking if you hold down CTRL snapping to grid is enabled, I just concluded the tool was buggy, and I did not like using it until I understood what was happening. Basically, this means every time I perform this functionality I have to go through the awkward process of immediately lifting the CTRL key after I have clicked along the highlighted edge and begun to drag and position the new vertex that is added to the existing polygon, and not knowing about the snapping to grid hotkey functionality, the functionality appears inconsistent and naturally becomes confusing and unintuitive to learn, and forgetting to lift the CTRL key afterwards, which may happen, meaning snapping to grid will remain enabled, makes positioning the new vertex frustrating if you desire to do so in a regular unrestrained manner. I believe swapping the ALT and CTRL hotkey functionality used by this tool would be a potential solution, SHIFT, which may appear to be an appealing alternative, has its own functionality in this context similarly to CTRL, and therefore is an illegitimate alternative. I understand that it is likely a design philosophy or otherwise a general or naturally inherent principle that the more preferable or essential tool is always without question mapped to CTRL and the lesser, if there is one, to ALT, but in this case, there is definitely good justification to swap the two. I have also checked every other tool on the same toolbar to see if they have any of the same problems, and they do not. Obviously, this problem only exists in specific contexts whereby duplicate hotkey functionality coexist or is in conflict, and specifically, in this case, duplicate hotkey functionality that involves moving, rotating, or scaling, or generally speaking, any transformation related functionality that would incur snapping to grid etc, whatever the functionality may be.\n\n1. Based on the default startup, select the existing cube\n2. Hit tab to enter into edit mode\n3. Select the Poly Build Tool from the icon-based tools menu to the left\n4. Create a triangle using the Poly Build Tool i.e. click three times in empty space to create three new vertices, and from there, select, holding CTRL or SHIFT, each vertex in clockwise order noting that the last vertex you created will already be selected and press F to create a new face\n5. Hover over an edge, and, while holding CTRL, click and drag\n\n\n" ]

[ "Collection don't change text color\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\nActive object's text is not visible if the selected object is collection (in the outliner).\n \n\n**Steps to Reproduce**\n- Open the directory where blender.exe is\n- Place the `test.xml` file inside `\\blender_version\\scripts\\presets\\interface_theme\\`\n- Run Blender\n- Change the theme to `test` from preferences tab\n- Select the collection in outliner (Collection name is not clearly visible because of changed `active Highlight` color)\n\n[test.xml](test.xml)", "LibOverrides - Refactor how diffing of RNA collections is handled, and extend diffing possibilities.\n**Status:** \n\nMilestone 1 has been implemented in Blender 3.0.\n\nIt implies forward compatibility breakage (i.e. files saved in Blender 3.0 won't open in a fully correct state regarding inserted local override modifiers/constraints, in older versions). Some fix will be added to Blender 2.93 LTS to at least prevent crashes.\n\nMilestone 2 is not yet scheduled.\n\n---\n\n**Description**\n**Big picture:** \n\nThe insertion of new items in existing RNA collections of override data-blocks (e.g. object constraints or modifiers) was 'hacked' in in early stage of the project and unfortunately never properly reworked before it got into production.\n\nIt currently has a weird implementation and design flows that make it close to impossible to extend in practice (to support e.g. re-ordering, deletions, etc.)\n\n**Goals**:\n* Make current code match expected design of data model used to store overrides.\n* Support more complex operations over collection items (re-ordering, deletion?).\n\n**List Operations Design:**\nUltimately this would include `Insertion`, possibly `re-ordering` of existing (from linked data) items. Supporting `deletion` operation remains an open topic, as it has fairly complicated implications, and is not strictly needed since items can usually be muted/de-activated anyway.\n\n*Implementation comments are in italic below.*\n\n* Current Design:\n**Order of operations defined in the override property is crucial, since if you insert a new item `A`, and then another item `B` after `A`, you will need to use `A` as anchor for `B` insertion.** Insertion:\n***Insertion operations are applied in a separate, second pass after all other override operations have been applied.**** *This is a mistake, insertion and ordering should be applied **before** any other override operation, such that order of items in destination data fully matches the one it had when operations were generated by diffing code). This is especially important for index-based operations or index-only lists.*\n***If items in the collection can be referenced by unique names (e.g. modifiers, constraints), new items can be inserted anywhere, using any other existing item as anchor (insertion before/after that anchor item).*** If items in the collection can only be referenced by index (NLA tracks), new items can only be inserted after existing ones (i.e. after items coming from the linked reference datablock).\n***If name reference is defined, it takes precedence over index reference.*** If no valid reference is found, insertion point is assumed to be first (for insert after) or last (for insert before) position in the list.\n*** ***Current implementation main flaw:** it uses a single reference information, `subitem_local_name`/`subitem_local_index`. This is used to find the anchor item after which the new one (matching current override operation) is inserted, **in local override data**. The one to be inserted is then always considered to be the next item in the list of the local (source, stored-in-blend) override data. This makes `insert after` operation the only possible one currently.*\n*** *Items inserted in local override data have a specific flag, different for each type (e.g. `eModifierFlag_OverrideLibrary_Local` for modifiers, `CONSTRAINT_OVERRIDE_LIBRARY_LOCAL` for constraints, etc.).*\n**Re-ordering:*** Not supported.\n\n* Target Design:\n**Insertion:*** Fix current main issue by adding a third set of subitem data, called e.g. `subitem_storage_name`/`subitem_storage_index`, to be used by insertion operations to find the source item from the local override data used as storage, when re-applying overrides over linked localized data.\n**** *Versioning code could then simply detect that an insert operation has a define `subitem_local_xxx` info, but no `subitem_storage_xxx` one, and re-generate that one from the next item in the list of the local stored override data.*\n***The rest of the current design for insertions should then be fine.** Re-ordering:\n***This should only be supported for lists that can reference items by their names (Index-based ones would be too prone to produce invalid data if linked reference data changes).**Engineer plan:**\n* Research the best way to `do_version` to use existing data model in the expected way for current, already implemented code/supported feature. This might imply a breaking of forward compatibility.\n* Research more advanced algorithms able to detect deletion or re-ordering of existing items.\n\n**Work plan**\n\n- [x] **Milestone 1 - Refactor Existing Code/Feature** 33c5e7bcd5, ec71054a9b\n - [x] Change existing diffing code to generate expected override info (relatively easy).\n - [x] Versioning for old .blend files (backward compatibility, relatively easy).\n - [x] ~~Try to find a way to ensure forward compatibility (not sure this is possible without unreasonable changes to the override data structures).~~ *Not practical to implement.*\n - [x] Backport simple fix to 2.93 (and possibly 2.83) to avoid crashes on opening new 3.0 files. 95c82513ca 1d8d6c2f62\n\n- [ ] **Milestone 2 - Advanced Diffing**\n - [ ] Implement a diffing algorithm that would support re-ordering and deletion of existing items.\n\n**Branch**: ...\n\n---\n\n**Relevant links**:\n* ...", " Verts/Faces instantiation recursion: child items reappear if they are collection instances\nOperating system: kubuntu\nGraphics card: nvidia\n\nBroken: 2.82a - 2.90.1\nWorked: I don't think it did in the 2.8 series\n\n\nThe lower plane is the face-instancer of a blue sphere, and a collection instance that consists only of the peg (the one to the right). When the plane gets instantiated, the sphere is hidden (as expected) but the collection instance of the peg appears.\n\n\n\n\n\n[instantiating-a-collection-vs-object.blend](instantiating-a-collection-vs-object.blend)", "Rigid Body Physics forces no longer restricted to specific layers/collections\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 26.20.100.7641\n\nBroken: version: 2.93.0 Alpha\n\nPrior to Blender version 2.8, forces would only affect rigid body objects within the same layers. With later versions the scene is managed via Collections but despite forces being able to be placed in any number of collections, all forces seem to affect rigid bodies in all collections.\n\nNote that saving a file with mulitple forces in different layers in Blender version 2.79b and loading into 2.93 Alpha does seem to retain the layer structure by creating an additional collection for the objects in different layers but the forces no longer work the same.\n\nAdd Rigid Body Physics to the default cube and duplicate it to a second cube. Move the second cube into a different collection. Switch off Scene Gravity. Create two forces that would affect the two cubes in different ways (eg, place one above one cube and the other below the other cube) and move the forces to the respective collection relating to its associated cube. This should result in each force affecting only one of the cubes (since they are in different collections). However, running the simulation results in both cubes being affected by both forces - rather than just the force in its own collection. \n\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", "Disabling/enabling in viewport a sub collection doesn't make the instances of the collection disabled/enabled unless you save and re-open the file\nOperating system: Windows 10 Pro 64-bit (10.0, Build 18363)\nGraphics card: NVIDIA GeForce 920M (Laptop)\n\nBroken: v2.83.13 Beta, 2020-04-21\n\nIf you disable/enable in viewport a sub collection of Collection then the instances of the parent collection \"Collection\" is not disabled/enabled in viewport unless you save and re-open the file.\n\n**Wanted result**\nThe wanted result is exactly like when you save and re-open the file, because for example if you enable/disable the cube which is child of child of Collection, then the instance of cube is enable/disabled. And just like that, SubCollection is child of Collection and if it's enable/disabled then the instance should be enabled/disabled too.\n\n\n[SubCollection_ViewportEnableDisable_refresh_bug.blend](SubCollection_ViewportEnableDisable_refresh_bug.blend)\n1. Open the provided file.\n2. Disable in viewport the collection named \"**SubCollection**\" to unreveal it in viewport. Now the two collection instances \"Instance of '**Collection**' (1) & (2)\" are not hidden.\n3. Save the file.\n4. Press Ctrl+N and click General.\n5. Reopen the same file. Now the two collection instances before are hidden, but before they were not hidden, it's a bug about refreshing.\n6. Enable in viewport the collection named \"**SubCollection**\" to reveal it in viewport. Now the two collection instances \"Instance of '**Collection**' (1) & (2)\" are not shown.\n7. Save the file.\n8. Press Ctrl+N and click General.\n9. Reopen the same file. Now the two collection instances before are shown, but before they were not shown, it's a bug about refreshing.\n\n**Steps for others to explain the logic of the viewport visibility of Collection and Collection Instance, this is not a bug, it's a useful feature that you should keep**\n- Don't forget to enable the \"SubCollection\" if you didn't do it yet, you've already save and re-open the file.\n- Disable in viewport the collection named \"**Collection**\" to unreveal it (not SubCollection). Now the two collection instances \"Instance of '**SubCollection**' (1) & (2)\" are not hidden. Now Enable back the \"Collection\", the enablement of the 2 collection instances \"Instance of 'SubCollection' (1) & (2)\" don't depend on the viewport enablement of the collection named \"Collection\".\n\n**Description of the last steps**\nIt's very useful when you build a model in a .blend file at the origin (0, 0, 0), and its collection name is \"_MODEL_\", and you want to place a collection instance of it at other location (not origin), and you want to disable the model at the origin by disabling the parent collection of the collection named \"_MODEL_\", and you want to keep enabled (visible) the collection instances.\n\n\n**People will adapt the non-logic bug but they will see weird things**\nThis is a big problem because if people don't know the bug then they think that it's the logic of viewport enablement of collection instances, and all their projects depend on that, but once they save and close and then re-open the file, they will see weird things.", "Bug on Rigid Body Simulation when an object is parented to another\nOperating system: Windows 10\nGraphics card: GTX 1060 6G\n\n2.80\n\nBug on Rigid Body Simulation when an object is parented to another\n\nPlease check the video......\n[BL280BUG.mp4](BL280BUG.mp4)\n\nMore, I have some questions on Rigid Body. I want to ask something, coding and algorithm, to the developers who work on it...\nHow can I reach them?\n\nThanks.", "Error \"Gizmos hidden in this view\" when trying to delete with measure tool and gizmos disabled\nOperating system: Windows 10 64 bit\n\nBroken: 2.83 release, 2.90 ec776f18ff70\nWorked: blender-2.82a-windows64\n\nIf the \"Measure\" tool is selected AND gizmos are turned off (\"Show Gizmo\", in the top right next to \"Overlays\"), trying to delete with the X Shortcut will result in the error \"Gizmos hidden in this view\".\nIf either\n* another tool is selected, or\n* gizmos are enabled\ndeleting works as expected.\n\n[delete_without_gizmo.blend](delete_without_gizmo.blend)\nOpen the file.\nHit the X key.\n\n", "Alpha Blend material has inconsistent behavior with Geometry nodes\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nAlpha Blend material renders differently on the object, which is referenced inside Geometry Nodes tree of another object, despite this another object is already hidden and has muted GN modifier.\n\nIn attached file:\n* Remove/Select *Shell* object inside GN tree of object *Mesh*\n* Activate/Deactivate *Viewport Disable* for *Collection* or object *Mesh*\nIn both cases material becomes transparent or not\n\n", "Can't move collections and objects to another collection at the same time\nOperating system: Linux-5.13.0-7614-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.63.01\n\nBroken: version: 3.0.0 Alpha\n\ncant move collections and objects to another collection in the same time\n\nNew file\nCreate a cube\nIn the Outliner \nCreate tow collections\nSelect the Cube and one Collection and move them to the other Collection by dragging \nJust the last selected before dragging will be moved\n", "creating a new collection in linked scene (same blend file) causes objects placed in it to dissapear from the outliner in the first scene.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\nWorked: unknown\n\nCreating a new collection in linked scene (same blend file) causes objects placed in it to disappear from the outliner in the first scene.\n\n1. Open default blender scene.\n2. Click the new scene button and choose linked copy.\n3. In the new scene, create a new collection and drag the cube into it.\n4. Go back to the first scene.\n5. The cube is gone and the new conllection not listed in the outliner.\n\n", "Breaking UI API changes for 4.0\n- [ ] Remove grid display for UI lists - Never worked well and is badly maintained. May have been added for an oudated asset UI design even?\n- [ ] Remove asset-view UI template - Should be replaced by the [asset shelf](102879).\n- [ ] Replace/deprecate UI lists? - Probably too much work, would require UI views to be exposed to Python. But can at least be converted to use UI views internally and benefit from its features.\n\n", "Crash upon renaming collection or clicking on Blenderkit after creating said collection (without renaming)\nOperating system: Win 10\nGraphics card: Nvidia Quadro M5000 \n\nBroken: 3.4.1\nWorked: 3.4.1\n\nCrash upon renaming collection or clicking on Blenderkit after creating said collection (without renaming). \n\n- Download file through the link from Google Drive attached (I leave the file as it is since I don't know what caused the problem)\n- Click in the collection \"Möblierung\",\n- create some new collection in it,\n- rename the new collection (with double click)\n- hit enter - crash\n\nOr create the collection, don't rename it and then click something in the interface (Blenderkit \"eye\" symbol in my case).\n\nReload didn't do anything, just kept crashing.\n\nLoaded a recent autosave, seems to work. Already hat to kill startup file and all settings yesterday, got permanent exception access violation crashes upon file load, after enabling some addon (TrueAssets) it worked.\n\nLink to the blend: view?usp=sharing\n\n", "Isolate restriction toggles on collection also affects nested collections\nOperating system: Linux-6.5.3-gentoo-r1-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 16.0.6, DRM 3.54, 6.5.3-gentoo-r1) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-b5a79000eb)\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\nUnclear if it's a bug but should see some developer attention if it's intended behavior.\n\nIn a nutshell:\nCollections in the outliner have various restriction toggles (selectable, hide, disable, etc).\nThese can be toggled in different ways:\n1. `LMB` to toggle single collection\n2. `Shift LMB` toggle collection and all collections inside\n3. `Ctrl LMB` isolate the collection\n\nThe issue is with the third one. For example when using it on the eye icon.\nIt doesn't just toggle the visibility of the collection that is clicked on and all other top level collections around it. It toggles visibility recursively downwards in each hierarchy.\nSo all collections inside the isolated collection are now shown and **every** other collection in the outliner is hidden.\n\nThe negative effect of this behavior is that just toggling a collections with `LMB` is not doing anything anymore. It's a necessity to use `Shift LMB` every time to make sure the contents are also toggled, since they are otherwise all toggled off. \n\nThe more desired behavior is to toggle only the top most collections so that the nested collections inherit that state. This preserves the current setup.\n\n- Create a simple collection tree of multiple collections, each with multiple collections inside\n- Hide one of the nested collections\n- Use `Ctrl LMB` on the eye icon on the top most collection from that same collection hierarchy\n\nSee how the nested collection was toggled on again. Also all other collections that aren't part of this one hierarchy are now hidden.\n\n", "Collection instancing does not include metaballs.\nOperating system: Win 10 x64\nGraphics card: Gtx 1070\n\nBroken: blender-2.83-50ef801a79b5-windows64\n\n\nAdd some objects to a collection. Then add a metaball to the collection. Once done instance the collection. The metaball is not included in the new instanced collection.\n\n\nPlease see the attached image and the scene for a quick look at.\n\n\n\n[NoMetaball.blend](NoMetaball.blend)" ]

[ "Blender 3.0.1 Collection Bug (have video for better understanding)\nOperating system: Windows 10 64Bit, Ryzen 5900X 64GB Ram\nGraphics card: RX6900XT (latest stable driver)\n\nBroken: 3.0.1\nWorked: \n\n\nWhen you Exclude (Disable) a collection with lower sub collections\nand when you un-exclude (Enable) the same collection with lower sub collections\nall lower sub collections remain Excluded (Disabled)\n\nI don't think this is intended, but I've experienced this{[F13004372](collection_bug.blend)} even with previous versions of blender\nWhen this happens I had to un-exclude (Enable) them one by one and it's consuming lot of time\nespecially when you have a larger scene\n\n\nI was not sure if I could reproduce this error but I somehow I could do it\n\n1.Make a Superior Collection A \n2.Make a Lower Collection B and put inside of Collection A\n3.Make a Lowest Collection C, D and E and put all of them inside of Collection B\n4.In summary you have Collection C,D and E inside of A\\B\\\n5.now exclude B (C,D,E are excluded)\n6.exclude A (C,D,E are excluded)\n7.unexclude A or B (doesn't matter which one you pick C,D,E will not comeback and will remain excluded)\n\nI've made a short video about this issue for the better understanding\n\nwatch?v=aWfKEtAMVqs&ab_channel=JayPatrick\n\nI've been using blender for years but even now I do think myself a noob, I need to more learning\nIf it is not a bug and if it is intended please let me know and also teach me how to bring back all excluded (disabled) collection \nat once so I don't need to un-exclude them one by one. \n\n", "Outliner: when excluding collections from view over more than one nesting level state gets lost (plus fix)\nOperating system: Kubuntu 20.10\nGraphics card: nvidia TU106 GeForce RTX 2060 SUPER\n\nBroken: 2.82a - 2.91.0\n\n[collection-demo.webm](collection-demo.webm)\nSee [D9849: fix preserving user selected exclude-state of nested collections.](D9849)\nI understand there is a rewrite of some outliner parts under way?\nNTL, fully local fix and allows using the checkboxes for mid-term workspace focus. In contrast to hiding for ad-hoc focus. I have been working with it since without problems.\n\n- Open attached file\n- turn off `widget1` collection\n- toggle `theme` off and on again\n- turn on `widget1`\nNotice that the collection exclude-state is gone.\n\n[collection-on-off-setting-nested-lost.blend](collection-on-off-setting-nested-lost.blend)\n" ]

[ "Glare Node set to \"Fog Glow\" in Real-Time Compositor vastly different from actual render results\nOperating system: Windows 10\nGraphics card: RTX3070 FE\n\nBroken: 3.6 A\nWorked: N/A\n\nWhen using the Glare Node in Real-Time compositor, the results in the viewport are turned up way higher than the actual render and Backdrop preview.\n\n\n\n1. Open attached .blend file\n2. Set to Rendered view, enable Real Time Compositor\n3. Compare the Glare effect in an F12 render to the effect previewed in the viewport\n\n", "Cycles 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.", "dual monitor will sometimes cause blender to freeze\nOperating system:win10\nGraphics card:2080s\n\nBroken: 3.4.1\nWorked: \n\ni have two monitors (4k and 2k) scrolling timeline or doing anything on one monitor and displaying cycles render viewport on the other monitor will sometimes cause blender to freeze forever\n\nit is not specific to this scene it will freeze on all kinds of scenes, might be related to the muti-monitor bug i have been reporting T96248\nhere is a screenshot of what it looks like when freezing \n\nmake some animation\nhave 2 monitors and use cycles rendered view on one monitor and scrolling timeline on the other monitor", "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|  |  |", "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", "Cycles viewport rerender when changing any color management setting if a rigidbody is on any object\nOperating system: WIN 10\nGraphics card: GTX1660\n\nBroken: 3.0.0, 3.1 BETA, 3.2 ALPHA\nWorked: Never\n\nWhen changing any of the color management settings in blender, a viewport rerender will be triggered if you have a rigidbody on any object.\n\nOpen blender\nput renderer to cycles\nput a rigidbody on the default cube (or any object)\ngo into viewport rendered preview mode\nchange any setting in colormanagement (eg. exposure, gamma, false color, medium contrast to high contrast)\nwatch the viewport rerender\n\n[BugTest.blend](BugTest.blend)", "Regression: Blender 3.1 UI editor resize /border dragging performance\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\nWorked: 3.0.1\n\nCaused by {6738ecb64e8b6d0c1f5a79f1e63f468b4138de19}\n\nResizing UI editor panels in Blender 3.1 is significantly slower (framerate) and laggier than it was in 3.0. This is not related to the UV Editor performance regression as it happens even when there's no UV editor displayed in the given workspace. \n\nHere's a video of the issue, recorded at 60FPS and slowed down to 50% so the issue is more apparent: watch?v=a0wzLgkf6mk\n\n1. Open blender with a new empty file \n2. Drag the top of the Timeline Editor UI area around\nResult: The UI redraw framerate and input response (lag) are worse than in Blender 3.0\nExpected: The UI redraw framerate and input response (lag) are same or better than in Blender 3.0\n\n", "Triangle Mesh Transmission Rendering\nOperating system: Linux-5.10.0-12-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.1.0\nWorked: n/a\n\nDear Blender Devs,\n\nthank you very much for this awesome software. I encountered the following problem while working with some imported triangle meshes.\n\nI tried loading a triangle mesh, removing one side using Geometry Nodes and subsequently using the Solidify modifier to give it depth for the transmission rendering. When looking at the rendered view in the viewport, it looked \"fine\". Since I was dealing with a triangle mesh with some weird connectivity I expected there to be some artifacts. See below.\n\nHowever, when I rendered with F12 (optix), the result was completely different to what I saw in the viewport (also optix). See below.\n\nNote the weird artifact at the back of the object in the F12 rendered version. Normally I would attribute this problem to the \"bad\" triangle mesh and just move on with my life. However, because the F12 rendered version produces different results to the viewport rendered version, I assume that there might be a bug somewhere.\n\n\n- Difficult to explain, see the `.blend` file for an example as it seems to be an issue with this specific triangle mesh.\n\n[viewport_f12_problem.blend](viewport_f12_problem.blend)\n", "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)", "Solid Viewport Transparency Artifacts/Dots\nOperating system: Windows 10 Home Build 19044\nGraphics card: iGPU on Intel Core i7 1185G7 (Iris Xe Graphics)\n\nBroken: 3.1.2\n\nI downloaded a 3D model from TurboSquid of an Aston Martin Vantage (the model is free, [find it here ](3d-aston-martin-s-1685480)) and the viewport has strange dots at object edges when looked at through the partially transparent glass. I tracked the issue down to the alpha of the Glass material in `Properties > Material Properties > Viewport Display`, the dots only appear when the alpha value is not 0.0 or 1.0.\n\n - Open `TransparencyBug.blend` or `astonAston MArtinV12 Vantage S 2016 .blend` (files at the bottom)\n - Set Viewport Shading to Solid\n - Set transparency of Transparent or Glass material (Properties>Material Properties>Viewport Display, select Transparent or Glass material) to some decimal value other than 0.0 and 1.0\n - Dots appear at edges of materials looked at through transparent objects\n\n\n**Images**\n\nastonAston MArtinV12 Vantage S 2016 .blend:\nAlpha 1.0: \nAlpha 0.201: \nAlpha 0.0: \n\nTransparencyBug.blend:\nAlpha 1.0:\nAlpha 0.5: \nAlpha 0.0: \n\n**Affected Files**\n[TransparencyBug.blend](TransparencyBug.blend)\n[astonAston MArtinV12 Vantage S 2016 .blend](astonAston_MArtinV12_Vantage_S_2016_.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.", "Viewport 3d is not updated with VSE driver\nBroken: 2.82 (unknown which revision, custom build without buildinfo)\nWorked: (unknown)\n\n[system-info.txt](system-info.txt)\n\nViewport is not updated for a material that is driven by a VSE driver.\n\n[ejemplo.zip](ejemplo.zip)\n\nChanging the VSE strip opacity doesn't update the viewport.\n\n**More info from user**\n\nI am creating an addon to transform eevee into a VSE. I encountered several problems, and one is that by changing the values ​​\"chanel\", \"opacity\" or moving the strip (it should disappear). the changes are not visible until the 3d view is moved. Just there it is updated. This makes it uncomfortable to work with the addon. The only change that works well is when changing the resolution X of the render, when playing the video or scrolling through the timeline, everything looks correctly.\nEverything is being controlled by drivers.", "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", "Intermittent: Shift + MMB unresponsive or very sluggish\nOperating system: MacOS Ventura 13.4.1\nGraphics card: M1\n\nBroken: 3.5.1, Hash: e1ccd9d4a1d3, Branch: blender-v3.5-release\n\nShift+MMB to pan view in perspective mode becomes either completely unresponsive to keyboard input or extremely sluggish compared to the mouse pointer speed for the rest of the application. Agnostic to mouse pointer speed setting for the OS. \n\nAny model in perspective view. Attempt to pan view via SHIFT+MMB.\n\n", "Cycles: CUDA takes ages to render what takes seconds on CPU and OPTIX (it also needs way more RAM)\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1, 2.93, 2.92\nWorked: I think it was always the case\n\nThe dino demo file (Splash Blender 2.92 60337d495677e942564cce76) takes with CUDA (BVH2) way longer to build the scene than CPU (Embree).\nIt also needs a lot more RAM. \nCa. 100GB of RAM\n\n\n```\nCUDA (BVH2)\nFra:1 Mem:1175.90M (Peak 51547.35M) | Time:21:52.48 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0001.png'\n Time: 21:53.12 (Saving: 00:00.63)\nOptix (Embree)\nFra:2 Mem:1176.06M (Peak 14002.25M) | Time:00:36.55 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0002.png'\n Time: 00:37.16 (Saving: 00:00.60)\nCPU (Embree)\nFra:1 Mem:1175.90M (Peak 14007.17M) | Time:01:08.57 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0001.png'\n Time: 01:09.21 (Saving: 00:00.63)\n```\n1. Open the scene\n2. Set it to one sample (disable denoising)\n3. Render with CPU, CUDA and OPTIX to compare.\n" ]

[ "General performance issues on Surface pro 7\n\nMicrosoft Surface pro 7 - i7, 16gb ram \nOperating system: Windows\nGraphics card: intel Iris integrated\n\n2.8\n\nFrom the get go, Blender does work, but is significantly slower than the other \n3d modelling software that I have installed. I'm currently running Zbrush, silo, Maya and Max with\nNo issues.\n\nSlow performance from startup to closing.\n\nIt's worth noting I do have the latest drivers for the Surface\n" ]

[ "Context override of bpy.ops.object.mode_set does not work\nOperating system: Ubuntu 18.04.5 LTS\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 440.100\n\nBroken: version: 2.93.0 Beta, branch: master, commit date: 2021-05-04 23:07, hash: 96abe5ebbc55\n\nSetting the object whose edit mode you want to enter via context overrides does not work.\n\nAlthough the active object is changed via the context override, the following line still switches into edit mode of the object selected in the UI:\n\n\n\n```\nbpy.ops.object.mode_set({\"active_object\": bpy.context.scene.objects[\"Cube\"]}, mode='EDIT')\n```\n\nI also tested:\n```\nbpy.ops.object.mode_set({\n\"active_object\": bpy.context.scene.objects[\"Cube\"]\n\"object\": bpy.context.scene.objects[\"Cube\"]\n\"selected_objects\": [bpy.context.scene.objects[\"Cube\"]]\n\"selected_editable_objects\": [bpy.context.scene.objects[\"Cube\"]]\n}, mode='EDIT')\n```\n\nAnd \n\n\n```\ncontext = bpy.context.copy()\ncontext[\"active_object\"] = bpy.context.scene.objects[\"Cube\"]\ncontext[\"object\"] = bpy.context.scene.objects[\"Cube\"]\ncontext[\"selected_objects\"] = [bpy.context.scene.objects[\"Cube\"]]\ncontext[\"selected_editable_objects\"] = [bpy.context.scene.objects[\"Cube\"]]\nbpy.ops.object.mode_set(context, mode='EDIT')\n```\n\nBoth do not work.\n\nThe only thing that works is:\n\n\n```\nbpy.ops.object.select_all(action='DESELECT')\nbpy.context.view_layer.objects.active = bpy.context.scene.objects[\"Cube\"]\nbpy.context.scene.objects[\"Cube\"].select_set(True)\nbpy.ops.object.mode_set(mode='EDIT')\n```\n\nBut it would be great to be able to do that simply via context overrides, as it also can be done for other operators.\n\n- Open Startup Scene\n- Duplicate Cube\n- Select Cube.001\n- Enter \"bpy.ops.object.mode_set({\"active_object\": bpy.context.scene.objects[\"Cube\"]}, mode='EDIT')\" in console\n- > The edit mode of Cube.001 is activated, however it should be the one of Cube", "blender crash if boolean + very very big scale\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2.1, 3.2\n\n[2022-07-21 19-15-24.mp4](2022-07-21_19-15-24.mp4)\n\n1. add boolean modifier\n2. scale any object on very very big value", "UV unwrap: pinning faces in an island causes other islands to have the wrong scale and fill the whole map\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.97\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWhen unwrapping, if you pin some faces in an island, then the other islands will not be in the same scale anymore, they will fill the whole map instead of remaining in the same scale.\n\n- before unwrapping any object, add some seams around a few faces so that this area will have its own small island in the UV map\n- unwrap the object. You should now have a main island, and a small island in the UV map\n- pin a few faces of the main island in the UV map\n- unwrap the object again. Now the small island will fill the whole map or be way too large, instead of remaining in the correct scale.\n\nI tried in Blender 2.81, and the problem is still there.\n\n**Steps to reproduce**\n\n* Open file\n* In UV editor, pin selected vertex\n* select all vertices and unwrap\n\nIsland will fill the whole map", "UV: (investigate) Render UVs of selected object in UV Editor while in Object Mode\nCurrently, the UV Editor only works while in \"Edit\" mode.\n\nHow firm is that restriction?\n\nIt would be nice if we could view UVs in the UV editor, even in \"Object\" mode.\n\nIf would be even nicer if we could use the basic edit tools, such as move, scale and rotate on those UVS, again, even in Object mode.\n\nUVs can be generated and adjusted procedurally, but there's no good way to see them. It would be nice to allow displaying (not editing) evaluated UVs. Combined with features like visualizing overlapping faces, this could save a lot of time.\n\nThis is an *investigate* task, to see if such a thing is even possible. If we discover it's possible, we'll then need to decide if it's desirable.\n\nThanks @BlenderBob for the inspiration!\n\n", "Mirror Uv\nThere already exists an operator called Copy Mirrored UV Coords. This could be extended to support the features described below\n\n\n- From +X to -X for example (source can be positive or negative X, Y or Z) \n- Options:\n - By object space\n - By world space\n - By topology \n\n\n\n**Starting point**\n\n\n**Desired result**\n\n", "Batch Rename: Preset support\nThe batch rename operator supports chaining operations, allowing for setup actions which users may want to re-use.\n\nThis is a convenience feature.\n\nExample use cases (which may be possible in the future):\n\n- *Bones*\n - Add a prefix.\n - Number the object/bone based on it's level in the hierarchy.\n - Add a L/R suffix based on it's side.\n- *Objects*\n - Rename them to match their object data.\n - Number them, ordering based on their Z locaiton.\n", "Layer Switching Shortcut Inconsistency\nThere is some improvement concept for collections shortcuts.\nCurrently, 1234 buttons shows a collection, but sending objects requires name in menu (M - \"Collection 1\" - \"Collection 3\" for example)\nThat would be nice if moving to collection will also support their number.\n\nFor example, \"5\" button shows collection called \"Lighting Collection\", so pressing \"M5\" will send selected objects to it.\n\n----\n\n*See: #55162#619317 - originally from @1D_Inc*", "Cycles Image Texture Alpha conversion inconsistency with EEVEE and Image Editor\nOperating system: Windows 10 Pro 64-bit (10.0, Build 18363)\nGraphics card: NVIDIA GeForce 920M (Laptop)\n\nBroken: v2.83.13 Beta, 2020-04-21\n\nIf an image is packed, it will get displayed differently in Cycles and EEVEE. It changes in EEVEE when\nAlpha Mode is changed from Straight to Premultiplied to match Cycles, but it does not change in Cycles\nby changing that option. If the image is unpacked Cycles will look like EEVEE with Straight Alpha Mode\nand again it will not be changed by the Alpha Mode option like EEVEE is.\n\n1. Open the provided file.\n2. Select the Image Texture Node\n3. Go into the right panel in the Shader Editor (N-panel) into the Item tab and Properties subsection\n4. Render Image\n5. try changing Alpha Mode and rerendering.\n6. try unpacking the image and rerendering.\n7. try changing the Alpha Mode on unpacked image and rerender.\n[packed_image_cycles_display_inconsistency.blend](packed_image_cycles_display_inconsistency.blend)\n", "Interlaced 3D Viewport swaps eyes when creating new window\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro [P1000](SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.56\n\nBroken: version: 2.91.0\n\nI am using a Zalman Trimon passive 3D monitor which uses Blender's interlaced 3D mode to display stereoscopic 3D. Everything works well in the 3D Viewport until I either create a new window or resize a nearby window. The original 3D Viewport pane suddenly swaps the left and right eyes and never goes back to the original configuration. It appears that dragging an adjacent window triggers the 3D Viewport to be vertically offset by one line, which causes the left eye image to become the right eye image and vice versa.\n\nSee this video for a demonstration (use the password \"blender\" without quotes): x7yf3cg\n\n- Open the default Blender file.\n- In the Properties editor, go to the Output Properties tab, check Stereoscopy and make sure Stereo 3D is picked as the option.\n- Go to Window -> Set Stereo 3D.\n- Set Display Mode to Interlace. Leave Interlace Type set to Row Interleaved. Leave Swap Left/Right unchecked.\n- Look at any object in the 3D Viewport through a 3D monitor that can interpret interlaced rows. Take note if the object is in positive parallax (the object is deep within the screen) or if the object is in negative parallax (the object is sticking out of the screen).\n- Create a new 3D Viewport pane by dragging the lower right hand corner of the current 3D Viewport up.\n- Note that the original 3D Viewport pane has swapped the left and right eyes (i.e. if the object was in positive parallax, it's now in negative parallax and vice versa), but the 3D Viewport pane you just created has the expected views for the left and right eyes.\n\n[swapped_eyes.blend](swapped_eyes.blend)\n", "Sequencer: transforming strips with overwrite enabled sometimes shuffles\nThe overwrite option sometimes shuffles the strips.\n\nWith `838b6ec48af6fb767089784193d8525c5f5faf13` (current master), and the attached file, the following error can be observed.\n\n- `G` key.\n- Type in `654`.\n- Press Enter to confirm.\n\n... if this doesn't shuffle the strips (so one strip is placed above the others), press Ctrl-Z and repeat the steps above.\n\n[sequencer_overwrite_sometimes_shuffles.blend](sequencer_overwrite_sometimes_shuffles.blend)\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", "After swapping the basis shape key to another one, the former basis key still affects the new one\n2.91.0\n\nWhat I try to do: I would like to make a later created shape key the basis one. \nI can do it with moving it to the top, and setting the former basis key's \"Relative To\" setting to this new basis one.\nIt works as expected until I'd like to make further changes in the old basis key (now just a regular shape key)\nIt affects the current basis, where - by definition - there's no \"relative to\" setting, so it shouldn't be affected by anything.\n\nI noticed that it does work as expected if I'm using the \"shape key in edit mode\" option - BUT it only behaves well until I come back to object mode. Then the new basis key instantaneously gets all the modifications I just made on the old basis.\n\nThe steps are below on an image with descriptions, but I attached the blend file too. Just change the shape key called \"starting basis\" and check what happens with the real basis one.\n\n\n[shapekey_error.blend](shapekey_error.blend)\n\nNote: there was one time when I created a shape key pair where this whole thing worked as intended. But out of (literally) 6 tries, only one worked and I couldn't pinpoint what I did differently in that case.", "Stitch by matching target edge length\nAdditional option to existing operator **stitch** that scales one uv island to match the other uv island by matching the edge lengths of the target uv island\n\n**Starting point**\n\nA couple of edges selected before running “stitch operator”\n\n\n\n\n**Undesired result**\n\n\n\nThe uv island that is being stitched to the bigger uv island is still very small\n\n\n\n**Desired result**\n\nThe loose UV island has the same texel density as the UV island that it stitches to \n\nSuggested approach:\n- Store\n - Original pinning\n - Original seams\n- Run “seams from islands”\n- Clear seams on selected edges\n- Pin all but the UV island that will stitched to bigger uv islande\n- Unwrap\n- Restore \n - Original pinning\n - Original seams\n\n", "Crash undoing in certain scenario (disabling Global Undo)\nOperating system: Linux-5.10.12-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.82a\n\nCrash undoing in certain scenario (disabling Global Undo)\n\nFrom the default startup file (order of operations is important here):\n- move the cube (could be any objectmode operator) {key G Z 3}\n- disable `Global Undo` in Preferences {key F4} > `Preferences` > `System` > uncheck `Global Undo`\n- add an armature {key Shift A} > `Armature`\n- go to pose mode\n- select bone\n- move bone\n- Undo {key Ctrl Z}\n - > crash\n\n```\n1 BKE_scene_object_base_flag_sync_from_base scene.c 2914 0x35b41a9 \n2 BKE_scene_set_background scene.c 2125 0x35b2957 \n3 setup_app_data blendfile.c 386 0x4b63950 \n4 setup_app_blend_file_data blendfile.c 416 0x4b639e4 \n5 BKE_blendfile_read_from_memfile blendfile.c 524 0x4b63e38 \n6 BKE_memfile_undo_decode blender_undo.c 88 0x4b62cc0 \n7 memfile_undosys_step_decode memfile_undo.c 193 0x486eb47 \n8 undosys_step_decode undo_system.c 214 0x4bb97ec \n9 BKE_undosys_step_load_data_ex undo_system.c 809 0x4bbb2df \n10 BKE_undosys_step_undo_with_data_ex undo_system.c 870 0x4bbb4a4 \n11 BKE_undosys_step_undo_with_data undo_system.c 880 0x4bbb4d3 \n12 BKE_undosys_step_undo undo_system.c 889 0x4bbb511 \n13 ed_undo_step_direction ed_undo.c 278 0x486c907 \n14 ed_undo_exec ed_undo.c 489 0x486d214 \n15 wm_operator_invoke wm_event_system.c 1332 0x3a17b06 \n16 wm_handler_operator_call wm_event_system.c 2161 0x3a198e3 \n17 wm_handlers_do_keymap_with_keymap_handler wm_event_system.c 2486 0x3a1a617 \n18 wm_handlers_do_intern wm_event_system.c 2782 0x3a1b591 \n19 wm_handlers_do wm_event_system.c 2914 0x3a1bafc \n20 wm_event_do_handlers wm_event_system.c 3445 0x3a1d2a3 \n```\n```\n \n```\n\n\n", "Inconsistency: Vector math node flips large list of options/operations.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.04\n\nBroken: version: 3.1.2\n\nWhen direction of opening changes, direction/order of list changes too.\n\n[2022-04-12_09-48-55.mp4](2022-04-12_09-48-55.mp4)\nIt is fun, it was the same in 2.79. But there was very short list with 1 column And it wasn`t so annoying. \nNow, with 2 columns the order should be fixed same way as in Math node.\nBecause user remember the relative position of option too. Not just «how far from start»\nAlso the same flipping exists for other lists, like Transfer Attributes node. But as I said, for one short column it is not the issue at all\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. " ]

[ "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", "Touch on Gizmos can return invalid cursor coordinates\nversion: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-23 21:42, hash: e5e885d0ecb9, type: Release\nbuild date: 23/12/2018, 17:14\nplatform: Windows\n\n\nWhen using a pen, as in a Microsoft Surface or similar device, using the camera Gizmos and moving the pen outside the 3D viewport seems to return null/invalid coordinates, and it breaks. They can ONLY be used inside the 3D viewport. It's an absolute deal breaker for touch screen users (Surface, Wacom, etc)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nAny default .blender. On a touch device using a stylus pen, click on a Gizmo (axis, zoom, or drag) and move the pen outside the 3D viewport.\n\n\nWhen using a regular mouse the cursor gets hidden and it works as intended.", "UI: sidebar tabs look for region overlap editors\nFor 3.0 we now have panels thinner than the area in which they are drawn. \nWhile this looks nice in most situations it's not the case for the category tabs in editors where region overlap is active, where they look arguably worse than before since there is now a visible gap between them and the panels.\n\nThis is he current look in 3.0 *(left is 3D viewport which has region overlap on, right is node editor which doesn't)*:\n\n\n---\nThese are some short-term possible solutions that I've tried, but there might be others:\n\n1. Draw all the tabs fully rounded and change the theme accordingly:\n * Possible theme change A\n```\n {F11800641}\n```\n * Possible theme change B\n```\n {F11800643}\n```\n\n\n2. Force no background and fully rounded tabs for overlap regions, keep the current look for the other ones *(this doesn't require theme changes)* [P2595](P2595.txt):\n \n\n\n3. Mix between 1 and 2, fully rounded tabs for all the editors and completely remove `tab_background` from the theme options *(would probably require updates to the themes)*\n\n\n4. Restore 2.93 look with full width panels for overlap region, keep the current look for the other ones [D12971](D12971):\n \n\n---\nWhile all the options proposed have their disadvantages, I'd personally go for option 2, until a better solution is found for the future.\nIMHO it looks fairly nice, it's not intrusive code-wise, and it doesn't require changes to any of the default or community themes, so it could be applied to 3.0 without further complications.", "Smoke Shadow glitches in Cycles (workaround only with Fluid \"Empty Space\" option)\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D700](D700) OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.21\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79\n\n\nWeird artifacts and boxes appear in the shadows of smoke simulations\n\n\nI've seen this happening in different simulations with different results. Sometimes it is a big square in the shadows like in the image attached. Sometimes it's just little squares.\n\nGenerally speaking the workflow I'm following when I see these errors is the following:\n\nSet the scene to cycles\nCreate ground plane\nCreate Sun Light\nCreate smoke domain\nCreate smoke emitter with particles\nSet smoke flow to emit fire and smoke from particles\nCaches simulation\nRender with Cycles\nGlitches appear in the shadows of the smoke\n\nAttached is a blend file and the render result with glitches\n\n[VolumetricsTest.blend](VolumetricsTest.blend)\n\n", "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", "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", "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", "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", "Cycles doesn't render smoke properly with adjusted clipping distances\nWindows 10 / AMD Radeon 6800 Series \nBroken: 2.79.1 1802d14\n\nI need to render a cross section of a smoke simulation. I set up the simulation and adjust the start/end clipping distances of the active camera to the desired values and in OpenGL viewport it works fine, renders exactly the cross section I want.  \nHowever, when I go into cycles and render it out, I get nothing: [*The second camera next to the active one is just for the convenience sake, mimicking the clipping values. Cycles behaves the same without it.*] \nI know that the materials are working fine because I can render it outside the camera's view: \nIf it helps, here's something else that I've found. When the end clipping distance goes beyond the Flow mesh (emitter) I get this weird result: \nAnd when it (end clipping distance) goes even outside the adaptive domain box, then it renders the smoke: \n[smoke.blend](smoke.blend)", "Wireframe visible when going relatively far from the 0,0,0 (20 meters)\nOperating system: Linux-5.16.15-76051615-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.54\n\nBroken: version: 3.1.2\nWorked: not sure\n\nYou can see the geometry of the object in cycles render in far away parts of it if the object its relatively far from the origin, 20 meters it's not so far, but you can see it.\n\n\n\n\n1.- Open the provided .blend\n2.- Don't touch anything, just enable viewport render\n3.- You should see the wireframe being visible\n4.- If you don't see the wireframe, you might need to change your render device/backend. E.G. Change between CPU, CUDA, OptiX, HIP, Metal, etc. At the moment, @Alaska can only reproduce this issue in CUDA with Blender 3.2 while @derekbarker can only reproduce the issue with OptiX.\n\n[train_bug_report.blend](train_bug_report.blend)\n", "UI: Linux & Mac Support for Eyedropper Outside Blender\nAs of the merge of #105324 Windows users can now use the Color Picker Eyedropper to select colors from outside of the Blender window, e.g. from other applications or the desktop:\n\n\n\nThis is currently only for the Windows platform, but it should be quite trivial to add this functionality to other platforms. If you examine #105324 you will see many changed files, but almost all of them can be ignored as they were just adding general support for this feature. You can add this feature to other platforms by changing two files, mostly by adding a single small function.\n\nFor Mac, for example, you can open up `intern/ghost/intern/GHOST_SystemCocoa.mm`. There is a `getCapabilities()` function that is setting flags for what a platform is capable of. You can just remove GHOST_kCapabilityDesktopSample from that list of things not supported. Then add a new function to the file, `getPixelAtCursor` that matches the others. Just ask the operating system where the mouse cursor is now, find the color at that point, and then return that as three floats (0-1) in sRGB color space. Don't forget to add a function declaration to `GHOST_SystemCocoa.hh`.\n\nLooking at detect-color-under-macos-mouse-cursor and get-the-color-a-pixel-on-the-screen-in-objective-c-cocoa-app this appears to need just a handful of lines.\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", "Smoke Domain glitching outside of its cache range 2.91.2, 2.9 Beta\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0 Beta\n\nIf you have a smoke/fire simulation and the playhead is outside of the cache range of the smoke domain. The 3D viewport and the render shows glitches in the domain.\nAlso the same glitch happens in 2.9.2\n\n[Mantaflow bug Test.blend](Mantaflow_bug__Test.blend)\n\n[2021-02-14 03-26-24.mp4](2021-02-14_03-26-24.mp4)\n[2021-02-14 03-34-25.mp4](2021-02-14_03-34-25.mp4)\n", "particle system collisions stop working outside 255 blender units\nOperating system: windows 10\nGraphics card: gtx 1080\n\nBroken: 2.79b 2018-3-22, \nparticle systems do not interact with faces which are oriented in the axis where the face is more than 255 blender units away from the origin\n[name ]([particleproblem.blend](particleproblem.blend))", "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" ]

[ "Regression: cycles render region in viewport hides all shading around region\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: 2.93+, tested with 3.1.0 Alpha\nWorked: 2.79b\n\nI am ready to swear, i did such bug report, but can`t find it now. Perhaps due to bad title?\nIt is easy to compare. In 2.79 Blender saves solid shading out of render region \n\n\nBut 2.8+ versions just do not keep it.\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)" ]

[ "NaN in object matrix of instanced objects\nRyzen 7 3800x\n31.9 GB Ram\nOperating system: Windows 10\nGraphics card: Nvidia 2060 6GB Ram\n\nI tested the same scene out on my other box and the problem happened. Both machines are running RTX 2060s. One is a Intel box and the other AMD.\n\n**Blender Version** 2.81 and 2.82a\nWorked: Nothing has worked\n\n**Error**\nYouTube link to render glitches: e1ScHjBANLk\n\nWhenever I start a render, around frame 58 the sun shadows just disappear.\nIf I close the scene and open it back up and render the frame where the shadows disappear, it will render fine. But after about 50 or so frames the shadows disappear again. \nIt works fine in viewport. \n\n**note**\nI deleted the volume light box with just a 1000 floating sprite boxes for the dust inside the garage. After that, the issue went away all together. I then added the volume box back and the problem happened again. It must have something to do with volume lighting. The grass outside is over 12k clones using a particle hair so it has something to do with volume lighting and particles inside a object. \n\n**Files**\n[Blender_Bug.zip](Blender_Bug.zip)\nIt was 12 GB, removed extra elements and brought it down to this.\nAround frame 60 if you render the animation 1-300 the shadow will disappear. Escape the render… The viewport will continue to display the shadow. But after the shadow disappears during the render, and without closing and reopening Blender, whenever you render that frame, the shadow “sun light” is absent. \n\n\n\n\n", "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.", "Invisible object in preview mode\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: AMD Radeon HD 8600/8700M ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0\n\nWhen I enable Material Preview mode in Blender, the object becomes invisible regardless of the Render Engine. Also the object is invisible with Rendered mode enabled when I use the Render Engine - Eevee. \n\nI don't know how it happened but I can't repair Blender. I reset all settings to factory, reinstalled the application, but it did not help. Can you help me, please?\n\n\n\n\n\n\n\n\n\n", "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 viewport soft shadows are broken on higher sample count\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: ---\n\nEevee soft shadows in viewport have color spills. But it works fine on final render (F12)\n\n\n\n- Open .blend file\n\n[bug_soft_shadows.blend](bug_soft_shadows.blend)\n\n- Switch to Rendered Mode of Viewport Shading\n- Wait half a min and see the problem(", "Particles from multiple systems disappear when all Physics Type are None.\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.81a\n\nWhen selecting a Particle System, all particles of the object disappear.\nImages showing before and after:\n\n\n\n- In the default cube add two particle systems.\n- Set the `Frame End` of both to 1 for better observation.\n- In the `Physics` tab of both choose `Physics Type` `None`.\n- Select any of the particle systems, note that the particles disappear.\n\nAttached file contains an example of multiple particle system on one object:\n[LP_grass.blend](LP_grass.blend)\n\nThis has to be the first file you open with the application.\nIf you open blender and enable the eevee material preview for example with the default cube and open the example file afterwards it works.", "Eevee clamping color values when viewport rendering and using viewport HDRI\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n[system-info.txt](system-info.txt)\n\nBroken: version: 3.0.0 Alpha\nWorked: (never)\n\nWhen doing a viewport render, color values are being clamped. In 2.92 a workaround for this was introduced - if you disable overlays, color is being processed as it should.\nHowever, if you use a viewport HDRI, even with the overlays turned off, values are still clamped.\nAs these two are often used together to get some quick snaps, it is a little inconvenient\n\n\n\n[#88288.blend](T88288.blend)\n\n- Open file\n- Switch to rendered view\n# Viewport render image\n\nColors are clamped even though overlays are disabled\n", "Eevee camera clipping inconsistent when using child of constraint on an armature.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.83.15\nversion: 2.83.17\nversion: 2.83.18 Release Candidate\nversion: 2.93.2\nversion: 2.93.3 Release Candidate\nversion: 3.0.0 Alpha\n\nViewport's material preview and viewport's render has different camera cull than F12's render image, despite same clipping settings\n[2021-08-15_12-16-50.mp4](2021-08-15_12-16-50.mp4)\n\n[CullBugSimplified.blend](CullBugSimplified.blend)\nVerify viewport is in ACamera's view\nSwitch to viewport rendered and material preview to verify cubes on foreground are visible\nRender to verify cubes in foreground have disappeared\nSwitch to ACamera.001 and render to verify cubes in foreground are consistent with viewport\n\n", "Sculpting Has Unexpected behavior when Saving work\n**Broken**: 2.83.4, 2.90 beta 97dc370c50ed\n**Worked**: 2.82\n\n\nGlitches in the non-active mesh after sculpting the active mesh, saving, and updating the viewport.\n\n\n[Ogre.blend](Ogre.blend)\n\n* Sculpt\n* Save\n* Refresh viewport (e.g., continue sculpting)\n\nThe artifacts should be visible immediately.\n\n**Original message**\n\nWhen I am sculpting and I go to save my work, after a successful save I get weird artifacts in the mesh that I havent made edits on in sometime. And it seems to be the same mesh every time. This has happened over 5 times so i figure its just a visual bug.\n\nGet 2 seperate meshes ready to sculpt, then sculpt on one and save your work. This is all i did to see the bug arise.\n\n\n", "GPU Hair Rendering Bug - \"Glitter\" with particular Root to Tip sizes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIn a perfect storm of GPU rendering + Hair with Radius Root size smaller or equal to the Tip size, bright white \"cards\" appear at the tips of some hair strands. \n*Switching to CPU rendering, the anomalies go away.*\n\nAlso, making the Root size Large and the Tip size small reduces the cards, but they are still there.\n\n\n\n\n[Hair Render Bug.zip](Hair_Render_Bug.zip)\n\n\n\nOpen the attached file in Blender 2.80\nSwitch to the Camera view if not already there\nRender (should be set to *Cycles using GPU*)\nSwitch to *Cycles using CPU* rendering\nRender\n\nOptionally:\n\nSelect the hair object (eyebrows)\nGo to the particle tab\nUnder Hair Shape, change the Radius Root to, say, 0.45 and the Tip to 0.1\nRender using GPU - cards are still there but are much smaller.\n\n", "Two materials: volumetric being in second slot causes error in EEVEE\nOperating system: Windows 10 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.90.1\nWorked: IDK, but I've been using blender since 2.79 and have not encountered this problem when I have done this kind of thing.\n\nWhen I have a mesh object that has both solid and Volume Scatter materials on it (in different slots), in EEVEE, the volumetric material only works if it is not in the second slot. If it is in the second slot (top down), it causes the black \"shader missing\" to be applied. Moving the volume slot up to the top with the solid material in the slot at the bottom causes normal operation.\n\nGo into edit mode on the default cube.\nDuplicate the mesh, but leave it at 0 0 0. Scale the duplicate up a little.\nCreate a second material slot, and assign the duplicate larger cube to it. Leave edit mode.\nCreate a \"Volume Scatter\" material for the second slot. The outer cube will turn black.\nMove volumetric material up in list of materials. The outer cube will change to the proper fuzzy grey.\n\n[#83538.blend](T83538.blend)\n", "High Resolution Render support\nSome fields needs to be able to output really high resolution renders out of EEVEE.\n\nFor now, we just try to allocate the asked buffer size and live with the consequence.\n\nMost GPU have a limit of 16K² texture resolution and some really high renders could not fit GPU memory in some cases.\n\nTo workaround this issue, we need to implement a multipass rendering.\n\nThe issue with this approach is that Screen Space effects (GTAO, SSR, SSRefract, SSSubSurfaceScattering) cannot take the whole picture into account.\n\nWe can split the rendering into tiles, scanlines, checkerboard pattern but the artifacts of SS effects will likely to be different for each", "Library overrides does not work well with Materials.\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.3.1 Release Candidate\nWorked: No\n\nAfter saving and reloading, the object's material changes unexpectedly.\nThis bug only appears on objects that have library overrides.\n\n\n**Exact steps for others to reproduce the error**[bug check.zip](bug_check.zip)\n\n1. Download bug check.zip\n2. Open the t2.blend file. You can see that the cube contains red and green.\n3. Then select mat2a in the material list and save it as t4.blend.\n4. Reload t4.blend, and the cube is only red.\n\nMy current bypassing method:\nBefore saving, choose the same material slot as t1.blend. Only in this way can the object's material do not turn into another.\n\nt1.blend is the original data.\nt2.blend is a link of t1.blend, and then replace the data material to the object material.\nt3.blend is wrong, just like the t4.blend you get.\n\n", "EEVEE: Contact shadows problem on layered hashed materials\nOperating system: linux open source drivers\nGraphics card: rx 6800\n\nBroken: 2.93\nWorked: Never (2.83+)\n\ncontact shadows dont look correct on certain angles for layered alpha hashed materials(hair cards for example). iissue is more noticable in viewport then in final render, but it is noticable in both.\n\nmake a sphere make it alpha hashed and slightly transparent then duplicate and scale geometry with slight offset to make layers then rotate around object with contact shadows enabled on the lamp\n\n\n[contact shadows problem.blend](contact_shadows_problem.blend)", " Verts/Faces instantiation recursion: child items reappear if they are collection instances\nOperating system: kubuntu\nGraphics card: nvidia\n\nBroken: 2.82a - 2.90.1\nWorked: I don't think it did in the 2.8 series\n\n\nThe lower plane is the face-instancer of a blue sphere, and a collection instance that consists only of the peg (the one to the right). When the plane gets instantiated, the sphere is hidden (as expected) but the collection instance of the peg appears.\n\n\n\n\n\n[instantiating-a-collection-vs-object.blend](instantiating-a-collection-vs-object.blend)" ]

[ "Material view and Eevee Rendered View displaying as pure white when scene contains hair particle systems\nOperating system: OpenSUSE Leap 15.1\nGraphics card: NVIDIA Geforce RTX 2070\n\nBroken: (example: 2.81 stable)\n\nIn scenes containing particle hair, viewport will render as nearly solid-white or solid-black in Material Preview mode or Eevee rendered view\n\nThis is the smallest scene with which I've been able to recreate this. MaterialLightingBug.zip\n\nOpen this scene, ensure Eevee is the renderer. Switch viewport to Material Preview or Rendered view. Also occurs if render engine set to Cycles, and Material Preview mode is selected. But does NOT occur when set to Cycles and Rendered view.\n\nWhen issue is occurring, no longer occurs when performing either of these options. And won't reoccur until Blender is closed and reopened.\na) selecting an object\nb) opening a new default scene, displaying eevee rendered, then reopening the above scene." ]

[ "Dead particles are unexpectedly rendered\n## Simplified Report\n\n- The following file contains a simple particle system and a collider that kills some of the particles.\n- Bake the particle system simulation.\n- Go to the end frame and render.\n- Notice that killed particles still appear in the render.\n\n[killedParticles.blend](killedParticles.blend)\n\n## Original Report\n\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 3.3.1\n\n\nI use particle system and mesh that kills particle. In preview dead partcles aren't rendered \nWhen I press f12 I see this . Cycles and eevee doesnt consider these as dead. It's very old bug, also information about death isn;'t saved in cache\n[report.blend](report.blend)\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)", "Baked Particles are rendered incorrectly on frame 0 and below\nOperating system: Windows 10\nGraphics card: Geforce RTX 3070\n\nBroken: Blender 3.3.5, 3.3.8 ,3.3.7, 3.6\nWorked: Unknown\n\nWhen rendering baked particles systems that have a baked frame on Frame 0 (or below) particles are rendered incorrectly.\nParticles are rendered on the emitter instead of their correct position.\n\n\n- Open the attached blend file (Note: Particles are now displayed incorrectly even in Viewport on Frame 0)\n- Skip 2 Frames ahead in Timeline\n- Go back to Frame 0 (Note: Particles are now displayed as expected)\n- Render Frame 0, Note: Particles are rendered on the surface of the emitter, which is different from what can be observed in the viewport.\n\n", "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", "Subdivision Surface Modifier slow when animation started with EEVEE\nOperating system: Linux (Debian bullseye)\nGraphics card: Nvidia Geforce GTX 1070\n\nBroken: 2.80 up to current master (d3cda49d143)\nWorked: Never\n\nThe performance wildly varies when Workbench shading is used and EEVEE shading is used when the animation starts.\nBasically if EEVEE is used and the timeline is reset and played it will have half the framerate than when Workbench is\nused when the timeline was reset. I first though this was a problem with EEVEE but as it turns out, when the animation\nruns with Workbench and it is switched to EEVEE while it is running it will have the same good performance with EEVEE.\nFor more testing I included instructions in the blend file to show the problem. Similar to solid viewport shading, undo also\nincreases performance (see instructions in the blend file).\n\nI file this as a bug even if its about performance because it seems like the limit is not my computing power here.\n\n[slow_subdiv.blend](slow_subdiv.blend)\n\n- Open file\n- Start playback with Solid Shading and remember the framerate\n- Go into Material Preview Shading\n- Reset the timeline with Shift+Left Arrow\n# Start playback\nframerate is only half of the framerate we started with\n- Go back into Solid Shading\n- Reset the timeline with Shift+Left Arrow\n# Start playback and while running select Material Preview Shading\nframerate stays roughly the same, but as soon as it gets to the end frame and loops it will go down again\n- Stay in Material Preview Shading\n- Deselect the object\n- Reset the timeline with Shift+Left Arrow\n- Start playback and press Ctrl+Z to undo the selection, note that before pressing Ctrl+Z\nframerate is what we started with.", "Particle System missing on right eye when renderd via terminal\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\nBroken: version: 2.81 (sub 12)\nI tested also 2.8 and it's also broken.\n\nIf you render a stereo image via terminal and use particle system emitter/hair the particle are only visible on one eye (left).\n\n- Add a second cube and make it smaller\n- Add a Particle System to the first cube, as hair, set \"render as\" to object and choose second cube.\n- In output properties enable stereoscopy. Set Outputfilename.\n- Save blendfile and start rendering via terminal, like this on windows:\nC:\\Users\\simeo\\Desktop\\blender2.8_nightly\\blender.exe -b C:\\Users\\simeo\\Desktop\\bugreports\\stereo_terminal_bug.blend -f 1\nHere's my blendfile:\n[stereo_terminal_bug.blend](stereo_terminal_bug.blend)\n\nHere's a comparison between rendered with and without terminal:\n\n\n", "Slow EEVEE timeline scrubbing when using Scene World material\nOperating system: Arch Linux\nGraphics card: Intel UHD 620 (`iris` with `INTEL_DEBUG=reemit`)\n\nBroken: `0781c22ceedc`, `2.90`\nWorked: \n\n\nScrubbing through the timeline on an empty scene is slow when viewing through EEVEE and Scene World enabled, even though the node graph for it is a simple Background Shader node.\n\nThis also happens when *nothing* is connected to World's material output.\n\n[slow_scrub.mp4](slow_scrub.mp4)\n\nYou can see in the first part of the video, when using LookDev and have Scene World disabled, the scrubbing is relatively fluid and very close to the cursor. After enabling Scene World you can see that the scrubbing is lagging behind the cursor.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Create a new scene\n2. Delete everything (not really necessary)\n3. Try scrubbing the timeline without Scene World in LookDev\n4. Try scrubbing the timeline *with* Scene World in LookDev\n5. Notice that the latter is less responsive\n\n**Note**\n\nI have only experienced this on this GPU (probably due to its low-performance), however I still feel this is a weird bug.", "Wireframe opacity doesn't work if object is \"in front\" and viewport shading is set to material preview or rendered.\nBroken: 3.0\nWorked: \n\nWireframe opacity slider doesn't work if the object is \"in front\" and \"texture space\" is checked and viewport shading is set to material preview or rendered.\n\nSelect Cube\nObject properties-> viewport display -> in front ON\nObject properties-> viewport display -> texture space ON\nIn the viewport overlay panel, drag the wireframe opacity to lower the value.\nchange the viewport shading to preview or rendered, wire will have full opacity.", "Theme: Inconsistent solid color for the background in the 3D viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.90 (sub 0)\nWorked: 2.79b\n\nThe color of the 3D viewport background set to theme seems to not match with the color set in the theme setting.\n\nCheck the examples below with the color #36393F\n\n2.79b: color is exactly like in the theme setting.\n\n\n2.80 to 2.82: color looks good but seems grainy.\n\n\n2.83 to 2.90: color is slightly changed, when sampled not the expected theme color.\n\n\n- Open blender\n- In the initial layout change the Outliner editor to Preferences\n- Go to background color option\n- Use the colorpicker to get a sample of the background color\nThe color shouldn't change, but it does", "Regression: Some particles have darker faces\nOperating system: Windows 10 1909\nGraphics card: GTX 1070 512.15\n\nBroken: 3.1 (also 3.1.1 RC)\nWorked: 3.0.1\n\nSome object instances, in a hair particle system, have darker faces\n\n3.0.1\n\n\n3.1 and 3.1.1 RC\n\n\nPress F12 in this test file:\n[Dark Particles.blend](Dark_Particles.blend)", "Cycles can not render parent particle hair, while Eevee can.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.0\nWorked: I duno\n\n\nIn Eevee, parent particles are successfully rendered both in viewport and final render.\n\n\nHowever, Cycles fail to render the parent particles both in viewport and final render.\n\nA sample Blender file has been attached below.\n\n", "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", "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)", "Texture properties not working with OSL enabled and unpacked textures\nOperating system: Linux-5.11.7-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 520 (SKL GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.92.0\nBroken: version: 2.93.0 Alpha\n\nI have a texture with RGB channels set to 1 and alpha set to 0. When trying to use this texture with OSL, the alpha property (at least) of the image texture node does not work when the texture is unpacked. I set it to channel packed, expecting the color data to be always white. The problem is that when the texture is unpacked, the color data is black.\n\n1. Open the attached file.\n2. Set viewport shading to rendered.\n3. The plane shows as white (as it should).\n4. Unpack the texture.tga file.\n5. Toggle between preview and rendered viewport shading to refresh.\n6. The plane now shows as black.\n7. Pack the texture again.\n8. The plane shows as white again.\n\n[bug.blend](bug.blend)", "Particles disappear, motion blur not showing properly\nOperating system: Windows 10 Pro, version 21H2, OS version 19044.2486, 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB, version 31.0.15.1694\n\nBroken: version: 3.2.1\n\nParticles disappear in animation, most notable at the beginning.\n\nDuring the dissolve effect, motion blur isn't showing. At the moment the effect ends, motion blur shows up.\n\n1. Render e.g. frame 16; particles are not showing, no motion blur.\n2. Render e.g. frame 31; all particles seem to be showing, motion blur.\n\n" ]

[ "Material view and Eevee Rendered View display glitch when scene contains hair particle systems with high amount of instances\nOperating system: Ubuntu 18.04.3\nGraphics card: AMD RX 580\n\nBroken: 2.81 125257758007\nWorked: 2.80.75\n\n\n[American Beech.blend](American_Beech.blend)\nThis glitched viewport happens if you append the tree object in a new project in 2.81.\n\nThe glitch happens only if you never go in material or rendered modes before appending the object.\nSo, open Blender 2.81, let everything as it is by default, click on File > Append and append the \"American Beech\" and \"Leaves American Beech\" objects.\nSwitch to material preview or rendered.... the tree is glitchy.\nBut, if before appending the object, you switch to material preview or rendered mode and then append the two objects then you will see it textured correctly." ]

[ "VSE: adding scene stripe resets animation of colour stripe with mask\nOperating system: Linux-5.13.0-41-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD RENOIR (DRM 3.41.0, 5.13.0-41-generic, LLVM 12.0.1) AMD 4.6 (Core Profile) Mesa 21.3.8 (git-813ee839be)\n\nBroken: version: 3.1.2\nWorked: none tested\n\nI have added a colour channel and applied a mask to it. I have created and animated a clock as UI element.\nWhen I add the clock as scene stripe to the scene with the masked colour stripe, the mask of the colour strip is not applied correctly.\n\nI have no idea what really causes the issue or how I could reproduce it. See the attached blend file and video files.\n\n**Notes**\n- When the clock strip is muted in the VSE overview, the problem does no longer exist. So I guess it's some weird interaction between the mask and the scene strip\n- The bug can be solved when you create a new scene and add the colour strip as scene strip and on top of that the clock strip. It works, but performance is incredibly bad.\n\n**Files**\n - The actual output: [bug 01.mp4](bug_01.mp4)\n - How it should look like: [bug 02.mp4](bug_02.mp4)\n - blend file: [bug.blend](bug.blend)", "Force fields don't work on a fire simulation with Flame Smoke 0\nOperating system: Windows 7 (64 bits)\nGraphics card: Radeon R7 200\n\nBroken: 2.83, 2.92.0\nWorked: -\n\nSetting the Flame Smoke to 0 makes the fire simulation to ignore all forces except gravity.\n\n* create a Quick Smoke simulation\n* set the Flow object to Fire, behaviour to Inflow\n* set Domain object Flame Smoke to 0 in the domain object of a fire simulation\n\nI've also added a particle system to visualize the force, while the fire remains unaffected:\n\n\nHere's a test file:[fire-test.blend](fire-test.blend)", "flow simulation element viewport size indicator strange after applying resize\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)\nWorked: not known\n\nElement size preview in viewport behaves unexpected.\n\n1) Open Blender\n2) Apply Quick Smoke to cube\n3) scale up Smoke Domain by 20 in x and y direction while keep z scale unchanged (S+Shift Z+20). Notice that preview of element size in corner of Smoke Domain gets resized and becomes more flat. Maybe that is bug because I would have expected that fluid elements are always cubic. But maybe that is intended?\n4) Apply All transforms to Smoke Domain\n5) I would now expect that viewport showed a resized preview of element size for Smoke Domain that was cubic. Instead size preview completely disappears from Smoke Domain. Instead a preview element is shown in the Cube. See . \n\nWhy does a flow object, that is not a domain object, need a element size preview? I think this is a bug.\nAlso, why doesn't the Smoke Domain get a updated cubic element preview when the Smoke Domain object changes size? I think this is also a bug.\n\n\n\n", "Boolean modifier - Intersect option - spike type artifacts while using Hole Tolerant option\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\n\n\nStrange spike artifacts at top while using the Boolean modifier - exact solver - Intersect - Hole Tolerant option\n\nSee video and attached blend file\n[issue.blend](issue.blend)\n\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)", "Blender Mantaflow gas fire and smoke simulation - Adaptive Domain problem!\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nTHE SAME BEHAVIOUR FOR Blender versions 3.3.1 and 3.4.1.\n\nAdaptive Domain from time to time shrinks as intended, but those shrinks are sometimes visible.\n\n\n- Open [file](https://projects.blender.orgattachment)\n- Bake 180 frames\n- Check frames 173 - 178\n\nDomain shrinks while space is occupied by smoke with substantial density", "Cycles doesn't render smoke properly with adjusted clipping distances\nWindows 10 / AMD Radeon 6800 Series \nBroken: 2.79.1 1802d14\n\nI need to render a cross section of a smoke simulation. I set up the simulation and adjust the start/end clipping distances of the active camera to the desired values and in OpenGL viewport it works fine, renders exactly the cross section I want.  \nHowever, when I go into cycles and render it out, I get nothing: [*The second camera next to the active one is just for the convenience sake, mimicking the clipping values. Cycles behaves the same without it.*] \nI know that the materials are working fine because I can render it outside the camera's view: \nIf it helps, here's something else that I've found. When the end clipping distance goes beyond the Flow mesh (emitter) I get this weird result: \nAnd when it (end clipping distance) goes even outside the adaptive domain box, then it renders the smoke: \n[smoke.blend](smoke.blend)", "Mantaflow Noise Smear (OpenVDB cache)\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 472.12\n\nBroken: version: 3.0.0 Alpha\n\nWhen you add the noise effect to any gas simulation (that uses the OpenVDB cache type) it creates a smearing effect. It only adds to the simulation and it never deletes itself.\n\n**Video explanation** base simulation | with noise enabled | overlayed\n\n[Noise_Smear.mp4](Noise_Smear.mp4)\n\n[Noise_Smear_2.mp4](Noise_Smear_2.mp4)\n\n\n - Create any kind of Mantaflow gas simulation (if the emitter moves it is the most noticeable)\n - Leave the cache type to OpenVDB (With UniCache it works properly)\n - Enable [Noise ](noise.html#bpy-types-fluiddomainsettings-use-noise)\n - Bake the simulation\n\n\nTest File:\n[Noise_smear_bug.blend](Noise_smear_bug.blend)\n", "Regression: Child hair particles set to \"Interpolated\" causes jittering when the based vertex changes position\nOperating system:win10\nGraphics card:RTX3060ti\n\nBroken: c8c6f62cf3a3,fca8df9415\nBroken: 3.5\nWorked: 3.4\n\nCaused by d20f9923224d2637374dd4390ae84c5041e3f9d3\n\nChild hair particles set to \"Interpolated\" causes jittering when the based vertex changes position\nThis problem seems to have been solved before,in #63534 and #56408\n\nOpen the file and render animation\n\n", "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", "The light and smoke is not rendering in 3.4\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.3 with motion blur off.\n\nThe light and smoke is not rendering in 3.4\n\n\n\n\n**Steps to reproduce**\n[other other.blend](other_other.blend)\n\n- Open file\n- Bake smoke domain\n# Render image\n\n\n\n\n\n\n", "Smoke artefacts when baking smoke simulation based on particles\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.2\nWorked: none\n\nI have a baked particle simulation that is propelled by a wind force field. Next, I have a smoke simulation whose flow source is set to particle system.\nWhen I run the simulation it takes much longer than usual and ends up creating lines of smoke in random directions.\n\nI add that all the sliders in the field weights tab of the domain object are at 0 (gravity, all...) so no force field can be the cause of this scattering\n\nHere are some pictures of the problem :\n\n\n\nWith higher resolution :\n\n\n- Open the blend file\n- Bake Particles\n- Bake Smoke\n\n[SceneProblem2.blend](SceneProblem2.blend)\n\n", "Smoke not rendering randomly, video and blend attached\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\n\n\nSmoke renders haphazardly in the viewport. see:\n[Blender Smoke Render Bug.mp4](Blender_Smoke_Render_Bug.mp4)\nSometimes it's fixed by toggling Adaptive Domain on/off and changing its Add Reosultion value up, e.g. 0, 16, 512, 32, 64, etc.\nThis is random and not guaranteed to fix it.\n\n- Open the attached .blend file,\n- Play (hit Space).\nSmoke sometimes renders correctly in the viewport, sometimes it doesn't.\n[SmokeDEBUG.blend](SmokeDEBUG.blend)", "adding outflow object removes smoke from viewport\nOperating system: Windows 10\nGraphics card: Geforce RTX 2060\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nversion: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: 3e85bb34d0d7\nversion: 2.91.0 Alpha, branch: master, commit date: 2020-10-02 22:11, hash: 743eca0f316d, \n\nWorked: (newest version of Blender that worked as expected): \nunknown\n\nA simple smoke simulation with a plane inflow works fine. When a torus shaped outflow mesh is added the smoke is not calculated.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Start Blender\n2. Add Fluid Domain to default cube\n3. Add 0.5m plane mesh\n4. Add Flow->Inflow to plane\n5. Cube-Fluid->cache->type->Modular\n6. Cube-Fluid->cache->Frame end->50\n7. Bake data\n8. Verify smoke is seen rising in view port\n9. Free data\n10. Add torus mesh object, major radius 0.8, minor radius 0.1\n11. Add Flow->Outflow to torus\n12. Free data\n13. Bake data\n14. Verify that smoke is not seen in view port (this is assumed a bug)\n\n[#81423.blend](T81423.blend)", "Mantaflow liquid collisions not working properly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.90.1\n\nUnless a liquid collision effector's Surface Thickness is set to at least 0.5 or set to \"Is Planar\" it is not used.\n\nI reference two examples for liquid and smoke+fire [examples ]] and there are several issues logged in [[ https:*blender.stackexchange.com/search?q=liquid+collision | Blender stackexchange ]], along with my [[ 111042 | investigation ](http:*optionpeer.com/jimtpersonal/collisions.zip).\n\nA collision effector is ignored unless Surface Thickness is set to at least 0.5 or set to \"Is Planar\". However as [docs ](effector.html) state Surface Thickness is \"Additional area around the effector\".\n\nIn my first example \"liquid collision.blend\" the results (show in \"liquid collision.png\") shows how the extra Surface Thickness effects the liquid that becomes more confined in the container, whereas setting it to less than 0.5 will cause the liquid to fall through the container.\n\nThe same is true in the \"muzzle*.blend\" file where the flash & smoke comes through the collision object unless Surface Thickness is set (incorrectly) to at least 0.5\n\n[liquid collision.blend](liquid_collision.blend)\n[muzzle flash no projectile.blend](muzzle_flash_no_projectile.blend)\n" ]

[ "Mantaflow: changing render resolution % in Cycles messes up everything\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.3.1 26.20.15029.15007\n\nBroken: version: 2.90.0 Alpha\n\nWhile i was doing some tests with mantaflow i found that if you render (my scene, i've tried to reproduce the problem with a fresh project but i wasn't able) the scene changing the resolution of the render in %, Cycles has some problem with the smoke.\n\nExpectation:\n\n\nReality:\n45%\n\n\n50%\n\n\n35%\n\n\n25%\n\n\n10% (Here the smoke isn't even in the scene ahah)\n\n\nThey are honestly really cool effects but, they are definitely not an explosion!\n\nOpen the scene, bake some frames, and try to render to different % of resolution\n[Explosion.blend](Explosion.blend)\n\n", "Blender 2.83 Buggy and Glitchy Mantaflow fire animation in Cycles\nPC 1\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nCPU Ryzen 1700X\nGraphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013\n8GB RAM\n\nPC 2\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nCPU Ryzen 2700X\nGraphics card: nVidia 1660 TI, latest driver\n32GB RAM\n\n\nBroken: version: 2.83.0\nWorked: v2.83 beta (from sometime in May)\n\nWhen rendering a mantaflow fire or fire + smoke animation in **Cycles**the result is a glitchy and buggy mess of a file/files.\n\nSo I've tried this on 2 different computers and 2 different versions of Blender 2.83 LTS and 2.9 alpha I've been doing this for a week. The results are the same.\nAnd none of the PC's run out of memory or anything. This is a simple mataflow fire animation but there are some really serious show-stopping bugs. I've had Blender crash on me several times. No matter if the output are pictures or a single .mp4 file.\n\nWhen I render a single frame in Cycles the render is correct most of the time, but not always.\nWhen I render the animation in Cyles, 50% or more of the frames are glitched out.\nWhen I render in EEVEE everything is fine, no problems.\nI have also cleared the baked cache many times. And tried different locations.\n\nI have only a single node, Principled Volume attached to the Volume input in Material Output in the Shader editor.\nI have tested with many new files not just a single one .blend file.\n\nThis is how it Renders in EEVEE, which is correct.\n\n\nThis is the same file rendered in Cycles, that glitches out. This was with jpg output. Have tried with many mantaflow samples settings. Many different output settings. The results are always buggy in Cycles but not EEVEE.\n\n\nHere's another Cycles render example with another file.\n\n\nThis is the file from the first example. But I have many more with the same problems.\n[mantaflow fire.blend](mantaflow_fire.blend)", "Glitched fire simulation when rendering (Cycles)\nMacOS Catalina 10.15.5\nGraphics card: Radeon Pro 560X 4 GB, Intel UHD Graphics 630 1536 MB\n\nBroken: v2.83.0 official release\nWorked: v2.83 beta (from sometime in May)\n\n**Mantaflow smoke simulation is incredibly broken when rendering in Cycles. If it shows up at all, each time attempting a renders yields vastly different results, none of which resemble what it should be. Attempting to render will also frequently result in a crash.**\n\nCurrently have not figured out which factors specifically cause the issue. It happened with a simulation originally baked in a previous version. I have re-baked it since updating to 2.83.0, but the issue remains.\n\nThe following images are the results of rendering the same frame of the same scene, except with strange and buggy results.\n\n\n\n\n" ]

[ "Wireframe opacity doesn't work if object is \"in front\" and viewport shading is set to material preview or rendered.\nBroken: 3.0\nWorked: \n\nWireframe opacity slider doesn't work if the object is \"in front\" and \"texture space\" is checked and viewport shading is set to material preview or rendered.\n\nSelect Cube\nObject properties-> viewport display -> in front ON\nObject properties-> viewport display -> texture space ON\nIn the viewport overlay panel, drag the wireframe opacity to lower the value.\nchange the viewport shading to preview or rendered, wire will have full opacity.", "Cycles dupli object baking issues\nnvidia g880m\n\nBroken: blender-2.73-d56c9fb-win64\nWorked: (optional) probably never\n\nwhen assigning object as duplis to some mesh, and then trying to bake these duplis to another mesh, duplis appear black. But in normals mode, it works, so they are there, just without material or something.\nAlso, you can see that the duplis are there actually twice, one offset quite strongly. In some other file, I got them also four times...\n\n\n[bakebug.blend](bakebug.blend)\nopen the file, hit bake. \nthe group of objects in the ceter bakes to the cube.\n\nalso, you can see another group of objects, where duplis have been made \"real\" and it works well, it's group of objects called \"fine\", baking to the cube works well with seemingly same meshes.\n", "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", "EEVEE-Next: Refactor renderpass storage\nCurrently render-passes are allocated in multiple texture buffers.\nThey take a lot of binding points and currently prevent the deferred pipeline to output diffuse color correctly.\n\nThe plan is to combine all render-passes into the same array texture and use an associated UBO containing offset to the layer of each pass type.\n\nThis would very similar to the AOV support.\n\nAnother direct benefit of this would be that the GBuffer encoding could be simplified.\n\n", "Subsurface scatering does not indirectly affect diffuse.\nHello,\nI've noticed an oddity: materials with SSS are considered totally opaque, but only for the diffuse aspect, but remain visible for glossy surfaces ;\n\n\n\n\nIt looks like a limitation, but it doesn't seem to be listed anywhere :\n\n-0df9b2c715\n-sss.html\n\nMaterials, such as ivory, jade, marble, rubber or skin, will produce variable results.\n\nIf this is a limitation, it's strange that it's only on the diffuse component and not the glossy one.\n\nSo it looks like a bug.\n\nThanks for reading, and sorry about my bad English.\n\n\nOperating system: Windows 11\nGraphics card: nvidia 2080ti\n\nBroken: 3.6\nWorked: none ?\n\n\nLoad SssPasstrought.blend , render\n\n", "Regression: Wrong colors editing list items in dark theme\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\nWorked: (3.6)\n\n\n It's same problem that I mentioned here:\n\n111942\n\nbut in dark theme. highlighting(selecting) text to rename it in dark theme is wrong color. I upload an image and compare it to 3.6 take a look at it.\nthe problem is that highlighting text is just same as selecting item and you will not notice that you are renaming it.\n\n", "3D Texturing: Limit Eevee samples to 1 during paint stroke.\nGhosting effects appear when painting. We should limit the number of samples to improve the performance and reduce the ghosting effect.", "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", "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)", "The result of Dynamic paint Image sequence is brighter than intended when using initial color.\nOperating system:Windows 10 64bit\nGraphics card: GTX 1060\n\nBroken: 2.79b, 2.80\nWorked: \n\nthe result of baked Image is birghter than it displays on properties panel. \nNot sure but seems like it is gamma correcting the color but the input color is already in sRGB space, not in linear space!\n\n\nset any color that is not too bright or dark to \nDynamic paint - Canvas - Image Sequence - Initial Color : color.\nthen press \"Bake Image sequence\".\nThe color of baked Image will be brighter than the color you set.\n[dynamic paint color.blend](dynamic_paint_color.blend)", "Bake actions operator converting F-curves to linear\nOperating system: windows 10\nGraphics card: Nvidia RTX 3080\n\nBroken: ( 3.5.1 , e1ccd9d4a1d3 , master, 2023-04-24\n\nWorked: (3.3.8, 6a4c537c211e, master, 2023-06-19 )\n\nbaking actions (object or pose mode) converts F-curves to linear interpolation in blender 3.5 and 3.6 but the accuracy of keyframe placement is higher opposed to 3.4 and 3.3 where the interpolation of the curves remains unchanged but for complex custom interpolation the keyframe placement after bake is unaccurate \n\nuse the default cube to key a 30 frame loopable action (increasing the Z transform on frame 15 will do), \ngo to the graph editor, \nturn the handle type to free and make custom interpolations like the attached files\nbake action\nimage2: orginal unbaked\nimage1: baked in 3.6/3.5\nimage3: baked in 3.3/3.4\n\n", "Artifacts when composing render passes with SSS, EEVEE and SSR\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0 Beta\nWorked: I'm not sure this behavior is new. Blender 3.2 displays the same behavior.\n\nWhen compositing render passes that have been generated using EEVEE, and an object has Subsurface Scattering enabled, and Screen Space Reflections are enabled, and Half Res Trace is disabled, artifacts are generated. The combined pass, however, correctly renders.\n\n\n*What I get (demo file included below)*\n\n\n*What I should get*\n\nNote: if Half Res Trace is enabled, the problem disappears.\nAlso, if Cycles is used to render the same scene, the passes do not display these artifacts.\n\n\n\n\n- Create a file that uses EEVEE as renderer.\n- Enable Screen Space Reflections. Disable Half Res Trace.\n- Create an object with Subsurface Scattering\n- Enable the following necessary render passes: Diffuse Light, Diffuse Color, Specular Light, Specular Color\n# In compositing, mix as follows the passes: multiply Diffuse Light and Diffuse Color; multiply Specular Light and Specular Color; add them.\n\nChanging the roughness can make the effect more extreme. Having a very contrasty roughness map exacerbates the problem:\n\n\n*a contrasty roughness map*\n\n\n*the render showing the problem more extremely*\n\n\n*how it should be*\n\nThe final result should be akin to the one posted above. You can compare the composited result with the one that is already combined: the combined one does not display the issue. Using Cycles for the same setup also works without problems.\n\nThe inconsistency of results mentioned above makes me believe this is a bug, and hence my report.\n\nDemo file: [sstest.blend](sstest.blend)", "Error baking particles in OSX\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX TITAN X OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.135\n\nBroken: version: 2.83.1\n\nI have two particle emisor and when I try to bake it crash.\nI try it in Linux and work perfectly!\n[TEST_ERROR.crash.txt](TEST_ERROR.crash.txt)\n\n[TEST_ERROR1.blend](TEST_ERROR1.blend)\n\n- Open file\n- Bake particles\n\n", "Smart Bake option for \"Bake Action\"\nProblem: \nCurrently we only support baking every Nth frame. Which sometimes results in more keys than desired, but \"cleaning curves\" doesn't do the job since most of the time you'd want your original key frames to be returned as a result not a \"cleaned up version\" of the curves.\n\nSolution: \nAdd an option to \"bake action\" named \"Smart Bake\", which will bake and only return key frames where the user has key framed already.\nIf the object baked has a constraint target to an other object. The constrain result should be considered in the same fashion it is done now, but only the keyframes that the user inputs in the object baked should be gotten as output.\n\n\nThis will retain the user's original poses or keys in place but depending how sparse the keyframes he originally has are, it will possibly break the interpolation between keys which is expected but should be stated in the tooltip.\n", "Displacement baking with Cycles\n" ]

[ "Baking diffuse lighting on 100% metallic surface produces black\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.0.1\nWorked: NONE\n\nWhen attempting to use the Bake function to render Diffuse on Metallic surfaces, setting the surface to be 100% Metallic causes the render bake to turn out completely black on those surfaces. \nIt makes some degree of sense that a metallic surface would not absorb any diffuse light, however, this is internally inconsistent as **setting the Metallic value to ANYTHING below 1.0 produces diffuse lighting information in the bake**.\nMetallic surfaces of varying degrees in real life show lighting and shadows on them. Blender appears to work the same way--except for this 1.0 metallic case, which ends up seeming like a bug. \n**99.99% metallic bakes diffuse lighting but 100.0% bakes NO diffuse lighting**. How was that threshold decided? There must be a more scientific, physically-based approach that might make more sense.\n\nNOTE: I understand, from this [other bug report ]], that you cannot bake the Metallic factor into a Diffuse channel, for example. However, this is just diffuse lighting and shadow information, not metallic.*I also tried on the latest daily alpha build (3.2.0 Alpha), but baking was somewhat broken in general.*[[ https:*github.com/mrdoob/three.js/issues/22692 | This issue thread in the Threejs github repo ](https:*developer.blender.org/T69826) is what sparked this whole exploration, for context.\n\n- Start with the provided .blend file\n- Select the cube object and make sure the image texture is selected in the Shader Editor\n- Try light baking with the \"Diffuse\" setting enabled (dropdown). Set to both Direct and Indirect lighting (no color)\n- Try again with the Metallic slider all the way up to 1.0\n- Compare the rendered lightmap-- when at 1.0, the cube doesn't get any baked lighting at all.\n\n[LightBakeMetal.blend](LightBakeMetal.blend)\n" ]

[ "Crash when importing / working with big or multiple VDB's in Shaded or Rendered 3dView (GPU & CPU)\nOperating system: macOS-13.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 3.6.0 Alpha\n\n\nBlender crashes when using big VDB files or scattered VDB's.(clouds)\nIn the viewport, when scattering VDB files, it is only possible in wireframe view mode.\n- When switching to only GPU shaded or rendered mode blender crashes.\n- When switching to only CPU you are able to use wirframe and rendered 3dview as well as rendering the image.\nBut not shaded view!\n\nMacOS 13.3.1 CPU --> 64GB \nAMD Radeon Pro 5700XT GPU --> 16GB\n\nSingle VDB files up to 450MB are OK. \nBigger cloud VDB used = 2.8GB crashes right after or while importing.\nThe scattered clouds are smaller in filesize, but more of them used.\n\nWhen opening the files, it's then only possible in wireframe mode.\n\n3DViewport used without realtime compositor !\n\nSince this is to big to upload here, the VDB file is here for free to test: clouds/\n\nOpen latest MacOS Blender version, switch to wireframe mode and CPU.\nImport the VDB from the link above.\nNow try shaded & rendered 3dview with CPU and then GPU. \n\n\nCRASHLOG:\n```\nRead prefs: \"/Users/NURB/Library/Application Support/Blender/3.6/config/userpref.blend\"\nDevice with name AMD Radeon Pro 5700 XT supports metal minimum requirements\nMETAL API - DETECTED GPU: AMD Radeon Pro 5700 XT\nregister\n\nWARN (bpy.rna): source/blender/python/intern/bpy_rna.c:1342 pyrna_enum_to_py: current value '17' matches no enum in 'View3DShading', '(null)', 'studio_light'\nWARN (bpy.rna): source/blender/python/intern/bpy_rna.c:1342 pyrna_enum_to_py: current value '17' matches no enum in 'View3DShading', '(null)', 'studio_light'\n\n[MTLTextureDescriptorInternal validateWithDevice:]:1344: failed assertion `Texture Descriptor Validation\nMTLTextureDescriptor has depth (2088) greater than the maximum allowed size of 2048.'\n\n[1] 42841 abort /Users/NURB/blender-git/build_darwin/bin/Blender.app/Contents/MacOS/Blender\n```\n", "Particle Edit mode for non hair particles - point select mode crash\nOperating system: Linux-5.6.0-050600-lowlatency-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 3)\n\nBlender crashes when entering into the Particule Edit mode\n\n- Delete all objects from the default scene\n- Create a plane\n- Add a particle system\n- Set end frame to 50\n- Bake the particle system\n- Switch to the Particle Edit mode\n- Select Point select mode\n\n- > Crash\n\n[blender.crash.txt](blender.crash.txt)\n\n\n", "VSE UI: Overlay Source text displays nothing & default Overlay text design considerations\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\n{[F10310240](image.png), size=full}\n\nWhen I implemented the Overlay dropdown, the main intention was to clean up all of the text on strips which clutter the VSE UI, however the patch was changed and my defaults never made it into the commit. The idea was the only Source should be displayed as default setting, unless Name differed from source. Source was implemented to show the strip type names or the content of the strip ex. for Movie files it would show the path and for text strips the content text. \n\nFor some unknown reason ex. effect strips do no display any type when Source is selected, and it should. They were properly removed to avoid both Name and Source saying the same, but if Source is only displayed when it differs from Name, then that problem wouldn't occur. \n\nSo the fix is:\n- Display strip type as Source, if no content to display(ex. Movie path or Text).\n- Display only Source if it differs from Name(and both overlay options are selected).\n- Remove Duration as default. \n\nOr the fix could be, if the content of the Text strip(currently only displayed with Source on) was written in the content area(ex. where the color of the color strip is displayed), then Name could be on as the only Overlay text setting. Like this:\n{[F10310203](image.png), size=full}\n\nOr Source could be split up into: Strip Type and Content(displaying url, text etc.).\n\nBasically, I think the default setting should display only the file name, or the strip type if no filename, and then have the content text in the content area of the strip.\n\n\n", "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)", "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", "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", "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.", "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", "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 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", "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", "Compositor doesn't render if VSE contains strips\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 3.0.0 Alpha\n\nCompositor doesn't render if VSE contains strips.\nIn some cases user may want to have for example sound strip to play sound while compositing. This can cause only VSE to be used for rendering.\n\nAdd color strip to VSE, in compositor check Use Nodes and render.", "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", "Video Editing: \"Set Render Size\" does not respect Crop settings of selected video strip\nOperating system: Windows 8.1\nGraphics card: Nvidia GTX 970\n\nBroken: 3.6.2\n\n\nIn the Video Editing workspace, video strips can be cropped through the sidebar.\nBut even when a clip's size is adjusted through this crop, the command \"Set Render Size\" (Strip>Movie Strip>Set Render Size / sequencer.rendersize) will set the render size to the strip's ORIGINAL dimensions prior to cropping, rather than the adjusted ones.\n\n\n1. Open a new file based on the default \"Video Editing\" setup.\n2. Import a video strip into any of the channels on the Sequencer.\n3. In the sidebar on the right (the one toggled with the N key), expand the \"Crop\" menu entry on the right (the third from the top after Compositing and Transform).\n4. Adjust the Left, Right, Top and Bottom values to crop the video\n5. In the menu at the top of the Sequencer, click Strip->Movie Strip->Set Render Size (or use the F3 command search and execute the \"Set Render Size\" command from there)\n6. The render size will have adjusted to the video strip's original dimensions, ignoring your crop settings.\n\n\n\n", "VSE Regression: Changing dimensions are cropping instead of scaling\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\n\nImport a video and change ex. resolution. \nThe video will be cropped instead of scaled. It used to do that, so it's a regression.\n\nThis basically means that if you import you footage and edit it, and then realize the the project resolution is wrong or if you need to render in a different resolution, you''re in trouble. \n\n{[F9869337](dimentions.gif),size=full}\n\n" ]

[ "Regression: Crash on changing view type with adjustment layer strips\nOperating system: Windows 8.1\nGraphics card: NVIDIA GeForce GT 750M (5+years old)\n\nBroken: 3.2.0 Alpha, master branch from git\nWorked: 3.2.0 Alpha from 2 weeks ago (so a recent regression). 3.1.0 release and older.\nCaused by 277fa2f441\n\n\nSimple operations in VSE like adding a strip and then changing the View Type will cause a crash. Reported to be an access violation. This has been happening on the Alpha build for the past couple of weeks.\n\n**Exact steps for others to reproduce the error** \n - Default startup\n - Change Editor Type to 'Video Sequencer'\n - Change View Type to 'Sequencer'\n - Add adjustment layer\n - Add second adjustment layer\n - Change View Type to Preview\n - Crash" ]

[ "Blender baking's margin overlap if multiple meshes are selected\nBasically just a duplicate of T51134 that Aaron Carlisle asked me to send as a new report.\n\n\nOperating system: Linux-5.4.0-58-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: AMD RAVEN (DRM 3.35.0, 5.4.0-58-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 2.90.1\nWorked: never with Cycles as far as I know.\n\nCycles overlap the region margin on other islands in the final result.\n\nCycles will bake an object/island, apply the margin, then proceed to do the same to the next one on top of the previous and they will overlap if the margin is bigger than the distance of the UVs, instead of applying to the finished bake and having the margins having an equal distance between islands, as Blender Internal used to do.\n\nJust press bake on the file. Or any multiple objects with a margin bigger than the UV islands.\n\nAs far as I know this has always been a problem with the Cycles baking implementation, besides some other issues of performance and usability. For instance if baked with multiple objects selected it is much, much slower than if I collapse them and merge, as I mentioned in the previous bug report.\n\nI understand it should be slower if they are separated, but I don't imagine it should be that much slower.\n\n\n\n", "Boolean modifier produces unexpected result\nOperating system: Debian bookworm / sid\nGraphics card: Intel WhiskeyLake-U GT2, but most likely doesn't matter\n\nBroken: 3.3.1 (from Debian), 3.4.1RC (Daily Build from blender.org, b87bcd3f8fe1), 2.93.12 RC (Daily Build, 1f30e…)\nWorked: unknown\n\n\nIteratively generating the difference between a mesh (in this case a plain torus) and a rotated version of its copy seems to work fine initially but results in broken meshes after a few steps. Artefacts include non-manifold bits and pieces of the original mesh, or a DIFFERENCE step that ends up adding the mesh that it just subtracted to the result.\n\nAlso discussed at 1427102 (page contains images showing said broken results).\n\n[problem.blend](problem.blend)\n\nInspect file above.", "Keyframed parameters are not preserved when frame_change_post handler is used\nOperating system: Win 10 Pro\nGraphics card: GTX 1080\n\nBroken: v2.81, master, 2018-11-26\nWorked: (optional)\n\n---\n\n\n**EDIT** by @EAW \n\n\n> In the .blend file setup, the 'mesh_cache' object would instance a cube over the vertices for display in rendering. An ocean modifier is added to the object with 'Geometry' set to Displace and the 'time' parameter is keyframed over a frame range. \n> \n> Playback in the viewport shows the ocean modifier evolving shape during the animation. If the animation is rendered, the ocean modifier does not evolve over time and the render result is static.\n> \n\n\n\n> Here is a script that generates a 2d grid of vertices in the frame_change_post handler:\n> \n> ```\n> import bpy\n> \n> def frame_change_post(scene, depsgraph):\n> # Generate a 2d grid of vertices. A cube object is set to be instanced over the vertices for rendering\n> vertices = []\n> for j in range(100):\n> for i in range(100):\n> vertices.append((i * 0.05, j * 0.05, 0.0))\n> \n> mesh_cache_object = bpy.data.objects.get(\"mesh_cache\")\n> mesh_cache_object.data.clear_geometry()\n> mesh_cache_object.data.from_pydata(vertices, [], [])\n> \n> depsgraph.update()\n> \n> \n> bpy.app.handlers.frame_change_post.append(frame_change_post)\n> ```\n> \n\n\n\n\n> Here is the .blend file including the script: [keyframed_modifier_bug.blend](keyframed_modifier_bug.blend)\n> \n> How to reproduce:\n> 1. Open .blend file\n> 2. Press 'Run Script'\n> 3. Blender > Render > Render Animation\n> \n> The result is a static animation.\n\n\n**End Edit**\n\n---\n\n\n\nI have created a FlipFluids simulation in Blender 2.81 ( 2019-11-25 21:45) and added an Ocean modifier in displacement mode to the fluid_surface. Then I have baked the complete sim from within FlipFluids.\nWhen I move from keyframe to keyframe in the default timeline everything is moving as desired in the default 3D window:\nOcean modifier waves, FlipFluids waves & wake, flags, radars...\n\nWhen I render the complete animation everything EXCEPT the ocean modifier waves are moving. The ocean modifier waves remain static but the FLIPFLUIDS waves move on that surface.\nALL modifiers and elements ARE enabled for renderings. D-NOISE: AI Denoiser is on (switching denoiser off did not help).\nComputer is a HP Z800 with dual Xeons, 72 GB of vRAM and a GTX 1060.\n\nIf I render & save the keyframes manually individually by hand the ocean surface moves! Which means I get the proper result.\n\nAs its working when rendering&saving each frame manually as image (Png) and its not giving the same result when saving out the same images (Png) when I hit render animation, I do suppose this might be a bug in 2.81.\nRunning indiviual frames via Renderpilot did not yield the proper result either. So I do suspect it might be that there is not enough time gap between saving the last frame and rendering the next. Or, something does not get purged properly.\n\nFor propriatary reasons I can not share the blend file.", "Unsubdivide support for non-grid topology\nOperating system:mac os mojave 10.14.5\nGraphics card:intel iris 550\n\nBroken: d62a749fcf48\nWorked: never\n\nUnsubdive either from the edge menu or under the decimate modifier not giving expected result with many production models. This never worked well so I figured I put in a report since I haven't seen an active one.\n\nAttached blend file, unsibdivide fails more often than not, producing triangles with unsubividealbe geometry. Works in other packages though, so it's not a problem with the geo.\n\n\n[unsubdivide.blend](unsubdivide.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", "Cannot render GeoNodes instanced collection without having original collection also rendered\nA collection is created and two planes shaped as diamonds are added. A separate plane is created and geometry nodes is used as a modifier instancing multiple copies of the diamond collection. When rendering only the geometry node instances are to be rendered but the original collection also renders. If the camera icon in the outliner is changed to black for the original collection or the diamonds then the whole scene is rendered black. The geonode plane with a white (on) camera icon should render all items generated by that modifier and the original diamonds with the camera black (off) should not be rendering.\n[B30beta renders too much.blend](B30beta_renders_too_much.blend)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Beta\n\n\n\n", "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", "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)", "Linked Instances Across Scenes have unreliable updates when editing their common mesh data.\n\nBroken: 2.93.4 LTS;\nBroken: master\n\nWith two different objects in two different scenes sharing a same obdata Mesh, editing the mesh in one of the scene can fail to properly update object in the other scene.\n\n- Open attached file.\n- Go to scene 2.\n- Switch to Edit mode.\n- Assign the red material (first slot) to the cube in edit mode.\n- Switch back to Object mode.\n- Go to Scene 1, the Cube in Scene one still uses the second slot material (green).\n# Switch to edit mode and back, now the cube is shown with expected first material slot (red) as well.\n\nNOTE: If you replace step 4 by a mesh geometry editing (e.g. rotate the mesh in Edit mode), in current master there is the same missing update issue in Scene 1, but in 2.93LTS it is properly updated... Regression introduced by 51568030e9.\n\n[Example.blend](Example.blend)\n\n------------------------\n\n# Original report\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.0\n\nIf you link an instanced object to another scene, having it's material link to object, it can have a different material from the non-instance. However upon saving and re-opening the scene, the instance's material will revert to that of the non-instance. \n\n- Open attached file or\n - Take the default cube and assign a material to it. In the viewport display settings assign a color for the material, this will give feedback in the viewport to highlight the issue. \n - Create another material on the same cube and once again assign a color in the viewport display settings.\n - Set both materials to Object Link in the material properties. \n - Name the current scene \"Scene 1\" and proceed to create another scene named \"Scene 2\".\n - Return to Scene 1, and using Alt+D instance the cube.\n - Using Ctrl+ L, link the instance to Scene 2. Delete the newly created instance in Scene 1.\n- In Scene 2, assign the instance a different material than Scene 1 in edit mode. You now have 2 scenes, with 2 cubes that share mesh data, but that are using 2 different materials. This is the desired goal in practice.\n- Save the file and re-open it. Blender will have automatically assigned both cubes to 1 material.\n[Example.blend](Example.blend)\n", "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", "Asset browser: Collection position offset on toggling instance option\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon(TM) 535 ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013\n\nBroken: version: 3.3.0, 3.2\n\nAssets imported with link option offsets position when `Instance` option is toggled\n\n- Create collection asset and save it in user library\n- Open default scene\n- Change timeline to asset browser (and in asset browser select library where asset collection is present)\n- Change import type to link\n- Drag collection to viewport\n- toggle `Instance` option (notice collection instance moves from its original position)\n\n[Blender 2022-06-16 10-26-03.mp4](Blender_2022-06-16_10-26-03.mp4)\n", "Annotations shouldn't be shared among different Geometry Nodes\nOperating system: ubuntu 20.04\nGraphics card: cpu\n\nBroken: 2.93.0\n\nWhen you ad an annotation to a geometry node, by default the same annotations can be seen in all the other geometry nodes layout.\nThis is unexpected, since each geometry node layout should have its own annotations.\n\nAdd a geometry node modifier.\nWrite something with the annotate tool.\nDuplicate that geometry node modifier, erase the old nodes, the annotations, and you'll find out that you erased the annotation also from the first geometry node layout.\n", "Driving object scale also scales its particle instances.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nWhen scaling the object that the particles are on, everything works correctly, the particles stay at the same size they are supposed to. \n\n\nBut when driving the exact same scale variable with a driver, for some reason the particles get scaled.\nThe property has to be on another object than the particle system, when it's on the object with particle system, then everything works as expected. \n\n\n\n\n- Open attached file\n- Change the 'prop' value (particle instances also get scaled)\n- Now select the object with the particles\n- Disable the driver\n- Scale in x direction (particles stay at the same size they are supposed to)\n\nPressing \"Update Dependencies\" fixes the scale, but in my real project that is unfeasible thing to do, I have many parameters that are driven that need to be animated and clicking them all through each time I make a tiny change is not possible. Also, rendering does not always fix the scales either. \n\n[DriverPartBug.blend](DriverPartBug.blend)", "Colection instances can't render if duplicated while instanced on a mesh with array\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.1\n\ncol instances disapear from render view if duplicated when instanced on an array\n\nmake a plane, add aray modifier. \nput anythng in a collection, instance it \nput the instance as child of the aray, toggle face instances on.\nduplicate the col instance: the previous one(s) will disapear from render.\n\nin this blend file, just turn render view and you'll see only the lastest col instance renders.\n\n", "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." ]

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

[ "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", "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", "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", "Script node with shader output crashes Eevee\nOperating system: OSX Monterey (12.6)\nGraphics card: Radeon Pro Vega 20\n\nBroken: git versions: blender-v3.2-release, blender-v3.3-release, master\nWorked: 3.2 release\n\nI'm testing the MaterialX standard surface shader. It seems to work when in Release versions, but in a debug build, it crashes when you connect the output of the shader to 'surface' in the terminal node.\n\nUsing the default scene, switch from Eevee to Cycles + Open Shading Language. Select the Cube, switch to Shading tab. Create a new material, and add a new Script node. Load the attached .oso file (to compile the attached .osl, you need to have MaterialX installed. I'm using 1.38.5). Attach the output of the script node to the 'Surface' input of the terminal. Boom! Where the crash occurs depends on whether your in Eevee preview, or Cycles preview.\n\n[out.osl](out.osl)\n\n[out1.oso](out1.oso)", "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", "Rigify crash in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.3.2.230315\n\nBroken: version: 3.5.0\n\nWhen I orbit the view in edit mode, the program crashes after a few seconds. Especially around the hands and face.\nIn version 3.1.2 it does not happen to me, it does happen in 3.3.0 and 3.5.\nTried to clean and reinstall, update drivers, save file in 3.1.2 and open in new versions, but the bug persists.\n\nSorry for bothering you, I hope you have a good day.-\n\n\ncreate human metarig, go to edit mode, orbit the view. Orbiting around hands seems to crash faster.\n\n", "Blender-3.1 (git) boolean in Geomenty Nodes issue\nOperating system:\nGraphics card:\n\nBroken: All\n\nBulean issue like T91889\nbut now in GN\n[2021-11-25_22-29-42.mp4](2021-11-25_22-29-42.mp4)\nTest Scene\n[parktronic1-Blender-3.blend](parktronic1-Blender-3.blend)", "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", "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "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", "Mesh Boolean and Bounding Box node joined together make lose the UVs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.5.0\n\nApparently, joining 2 branches of geometry node that contain a Mesh Boolean node and a Bounding Box node make the UV gone. On image attached, the cube on the left with the voronoid is the original cube and on the right it's the same cube with the Geometry node turned on. Maybe other node combination recreate this issue.\nWhen inspecting the branches independently the UV are still working but stop working when adding the Join Geometry.\n\n- Have an object with texture applied. \n- Have a geometry node modifier assigned.\n- The geometry node consists of a Mesh Boolean node joined with a Bounding box node. (I used a transformed node to move the bounding box away and see our object)\n\n", "Tweaking redo values in extend vertices operator causes extended vertex to dissolve\nBroken in 2.80 (1d908bffddb4 from 2019-01-24) as well as 2.79b release\n\nTweaking redo values in extend vertices operator causes extended vertex (the one from which the operator is executed) to dissolve", "Remove and re-add the rigid body world causes Blender to crash.\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.3.1\nWorked: I dont know.\n\nWhen the physical world is removed and added again, playback will cause the program to crash.\n\n\n1. Download the 2.blend and open it.\n2. Play 5 frame.\n3. Click the Remove Rigid Body World button.\n4. Click the Add Rigid Body World button.\n5. Click the rigid body world setting Collection. Then select RigidBodyWorld .\n6. Click the rigid body world setting Constraints. Then select RigidBodyConstraints .\n7. Move to 1 frame.\n8. Play 5 frame. Blender will crash immediately.\n\n[2.blend](2.blend)", "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", "Blender becomes unstable/crashes after using \"Reload Scripts\" if using any \"ShaderNodeCustomGroup\" nodes.\nOperating system: Windows 10\nGraphics card: NVIDIA\n\nBroken: 2.81\n\nIf you manipulate a \"ShaderNodeCustomGroup\" node after having used the \"Reload Scripts\" operator (F8) Blender will become unstable.\n\nAttached is a small addon that implements a minimal custom node group.\n1. Enable the addon and switch to the shader editor.\n2. Create the custom node (Add->Test Category->TestNodeCustomGroup)\n3. Trigger 'Reload Scripts' (F8 key).\n4. Adjust the color input of the custom node.\n5. Repeat steps 3/4 until you crash (usually crashes on first or second try for me)\n[node_custom_test.py](node_custom_test.py)" ]

[ "Blender hangs when making unintentional loops in geometry nodes\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14761 Core Profile Context 21.10.2 30.0.13025.5005\n\nBroken: version: 3.0.0 Alpha\n\n[geo-loop.blend](geo-loop.blend)\n- Load above .blend file\n- Attach the re-route node back into the Set Position Geometry input\n- Observe blender hanging (it's busy spinning)\n\n[Examples]\n- If for some reason you connect geometry nodes in a loop while they are being computed blender simply hangs instead of just not letting you make a loop.\n\n\n\n- it does not happen if its connected outside the nodes that are being computed\n\n\n\n- in shader nodes, if some loop occurs it simply is not computed \n\n" ]

[ "Sculpting - Switching stroke method with a shortcut causes a freeze\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1\n\nWhen using E shortcut in sculpt mode to change stroke method of the brush, there is a ~5-10 second freeze every time.\nHowever, when you do the same thing from the brush UI, the switch is silky smooth. See the video for example\n\n1. Open attached file\n2. Switch to sculpt mode\n3. Do a few strokes, press E - blender will freeze for about 10 seconds\n4. Do a few strokes again, this time change stroke method from UI - no freezes here\n\nVideo:\n[blender_am0pkp0Cwy.mp4](blender_am0pkp0Cwy.mp4)\nExample File:\n[sculptbug.blend](sculptbug.blend)\n\n", "Blender crash on combining textures (intel)\nOperating system: Windows 10\nGraphics card: Intel HD Graphics 4400\n\nBroken: 2.93.2\nWorked:\n\nWhen I tried to combine 2 textures like this blender is crashing.\n  \n\n[Test.blend](Test.blend)\n[Test.blend1](Test.blend1)\n[system-info.txt](system-info.txt)\n[Test.crash.txt](Test.crash.txt)\n[2021-11-12 09-11-32.mp4](2021-11-12_09-11-32.mp4)\n", "Installation fails when desktop permission to write is denied\nOperating system: Windows 10\nGraphics card: N/A\n\nBroken: 3.6 lts\nWorked: Unknown\n\n**Short Description**\n\nBlender setup error : An error occurred while attempting to create the directory DESKTOP_PATH\nOptions are Retry or Cancel.\nSelecting cancel give a confirmation prompt and then rolls back the installation.\n\n- - -\nI do not want every program I install to create icons on my desktop so have remove permissions to prevent this which is why this error occurs. Even so setup should not fail simply because a desktop Icon can not be created.\n\n", "Sculpt mode - program crash: brush smooth + graphics tablet\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 531.30\n\nBroken: version: 3.6.0\n\nUnless explicitly specified in \"preferences > input > tablet > tablet API > wintab or windows ink\", it crashes when using smooth brush. If I use the \"automatically\" setting.\nFor the bug to recur, the brush must take a force or size parameter from the pressure force on the graphics tablet. If I use the mouse, the error does not occur.\nThis error is repeated in any scene and with any object. I created a cube, remesh it and used a smooth brush in sculpt mode. Blender crashes to completion.\n\ngraphics tablet: xp-pen star 06\n\n", "Using another Mesh for Texture Indices (Texture Space / Generated Texture Coordinates)\nOperating system: Windows 10\nGraphics card: Geforce GTX1060\n\nBroken: 2.80.74 and 2.91.0 Beta\nWorked: Blender 2.79b Date: 2018-03-22 14:10 Hash: `f4dc9f9d68b`\n\n\nThe option \"Texture Mesh\" in the \"Texture Space Panel\" of the \"Object Data Properties Tab\" has no effect if the mesh does not have a deform type modifier.\n\n|\n| -- |\n|File is [here ](GeneratedTextureCoordinates4.blend?dl=0).\n\n\n- Open attached file - (Note that the geometry of one mesh affects the texture coordinates of the other)\n- Go to the modifiers tab and disable or delete the modifier\nTexture Mesh has no effect.\n[texspace_texture_mesh_bug.blend](texspace_texture_mesh_bug.blend)", "Dynamic Paint sub-steps doesn't work with particles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.0 Alpha\n\nWhen using a particle system as a dynamic paint brush, the sub-steps setting of the canvas doesn't work. The sub-steps appear to work as intended with all other brush types. Whether the painting is done with vertex or texture maps doesn't seem to have an impact on the bug.\n\n* Open attached .blend\n* Bake the dynamic paint cache with a sub-steps value > 0\n* The result shows no sub-steps\n[Bug2.blend](Bug2.blend)\n", "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)", "Blender hangs due to deadlock caused by two registered draw handlers\nOperating system: Only happens on Linux (Ubuntu 22.04)\n\nBroken: 3.2.2\nWorked: unknown\n\n\nWhen my addon is used together with the addon [\"node minimap\" ](1366781), Blender hangs/freezes completely under certain conditions (details below).\nTo close Blender in this state, not even Ctrl+C is enough, it is necessary to close the parent terminal from which Blender was started.\n\n\n[addons.zip](addons.zip)\n\n[test.blend](test.blend)\n\n- Install the two addons \"node minimap\" and \"test addon\" from the attached zip file.\n- Enable both addons (search for \"node\" in the addon list to find both).\n- Open the blend file.\n- Convert the editor on the lower left to a Shader Editor.\n# Blender will immediately hang.\n\n\n", "adding drivers in the compositor always results in a dependency cycle which often causes blender to hang when reopening the saved .blend file.\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.0 Alpha\n\nadding drivers in the compositor always results in a dependency cycle which causes blender to hang when reopening the saved .blend file.\n\n\nJust to clarify, the append issue I mention in the video only happens if you copy and paste 3d objects from a file with the dependancy cycle problem into a new file, save the new file, and then try and append that new file into another new file, in this instance it also results in a missing data block if trying to re-open the file you copied into.\n\n[compositor dependancy cycle on all drivers.blend](compositor_dependancy_cycle_on_all_drivers.blend)\n\n[2020-06-02 17-50-21.mp4](2020-06-02_17-50-21.mp4)\n\n", "Segmentation fault when selecting context.area.type before applying operator (scripting)\nOS: Ubuntu 16.04.4 LTS\nHW: Dell XPS 9550 notebook, using Intel HD GPU (nvidia deactivted)\n\nBroken: 2.83\n\nExecuting the operator `bpy.ops.transform.translate` causes a crash if `bpy.context.area.type` is set manually before.\nCrash in `setTransformViewMatrices` because `t->ar->regiondata` is `NULL`\n\nRunning the following script causes the crash:\n```\nimport bpy\nimport bmesh\n\n# Create object\nbpy.ops.mesh.primitive_plane_add(size=1, enter_editmode=False, location=(0, 0, 0))\n\n# Enter edit mode\nbpy.context.area.type = 'VIEW_3D' # If this is not set, crash does not occur\nbpy.ops.object.mode_set(mode='EDIT', toggle=False)\n\n# Modify vertices\nmesh = bmesh.from_edit_mesh(bpy.context.active_object.data)\nmesh.verts.ensure_lookup_table()\nmesh.verts[0].select = True\n\n# Next call causes crash:\nbpy.ops.transform.translate(value=(0, 0, 1), constraint_axis=(False, False, True),\n mirror=False, use_proportional_edit=True,\n proportional_edit_falloff='SHARP')\n```\n", "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", "\"Z\" changed to \"depth\" breaks consistency in compositing and in Render layers\n\nwin7 gtx 550ti\nOperating system and graphics card\n\nBroken by: 4cf7fc3b3a\n\n\"Z\" changed to \"depth\" breaks consistency in compositing and in Render layers\n\n\n- Make sure that the **z**-pass is checked in the Render Layers tab\n- Open node editor, notice that the**z**-pass is now **depth**-pass\n- Notice as well that everywhere else it is still consider as**z**-pass even in the manual z_combine.html\n\n\n\nAlthough **depth** is more meaningful name, it is breaking consistency. Suggestion: we bring back the old behavior or we change everywhere to z-depth or depth.\n", "Adding Clearcoat freezes Blender with error \"Execution of the command buffer was aborted due to an error during execution\"\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 5700 XT 1.2\n\nBroken: version: 3.5.0\nWorked: Unknown\n\nAdding Clearcoat to a Surface freezes Blender, with Console logs showing only an \"Execution of the command buffer was aborted due to an error during execution. <private>\" error.\n\nOnly appears to happen when using Metal, using Blender in OpenGL mode doesn't have this issue. The issue is also present on brand-new projects with just the default cube.\n\n1. Create new file (Eevee renderer)\n2. Change the Clearcoat amount of the default cube from the Materials tab.\n3. Blender crashes usually within seconds, with the default cube I've found it freezes more easily if you use the sliding mechanism to change the Clearcoatness.\n\n", "Improve Palette management in Paint Modes (Meshes and Grease Pencil)\nThis is not a task only related to Grease Pencil, but also to any Paint mode.\n\nAs part of the Vertex Paint development in Grease Pencil, we have detected some missing features in Palettes and we have decided to fix it, because Palettes look a little outdate and without improvements for several versions.\n\nMissing features/ WishList:\n\n* There is no default palette.\n* Swatches cannot be re-arranged\n* Colors cannot be sorted\n* Colors can't be named\n* Palettes cannot be merged\n* templatePalette control UI is outdated\n* No ability to import palettes from other software\n* No ability to export palettes to other software\n* Missing easy way to create palettes from images\n\nAbout default palette, in grease pencil we have implemented a default palette similar to Krita/GImp palette. This palette is required by GPencil, but it would be good idea to set this default palette in Texture Paint and Vertex Paint for meshes too.\n\n\nCurrently, I have solved the Sorting, Moving, Join and some Import modules in Grease Pencil branch, but the list above is the initial ideas.", "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" ]

[ "Blender crashes when switching to texture paint mode\n[system-info.txt](system-info.txt)\n\nversion: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-22 09:56, hash: 4c5e76025d83, type: Release\n\nCrash when switching to texture paint.\n\nStart blender with default config.\nClick \"texture paint\"\n\n**Logs output**\n[blender.stderr.txt](blender.stderr.txt)\n\n[blender.log](blender.log)\n\n[blender.crash.txt](blender.crash.txt)", "Crash when unwrapping UV on object imported from .stl and entering texture paint mode.\n**Broken:**\nBroken on hash 064cbe9f3fe0, windows. AMD 280X graphics card.\n\n**Description**\nWhen I import a .stl file, go inter texture painting mode, and select \"Add Simple UVs\", blender crashes. I have tried this on multiple .stl files from thingiverse to the same end. It only crashes while in or upon entering texture paint mode.\n\n**Reproduction steps:**\n- Open the attached .blend\n- Click \"Add Simple UVs\" while in texture paint mode *OR*\n- In edit mode, go to UV->UV Unwrap, then return to texture paint mode.\n\n**Sample .blend:** [simple UV crash.blend](simple_UV_crash.blend)\n\n**Sample STL:**\n [EM_Cone_single_3A.STL](EM_Cone_single_3A.STL)\n\n**Sysinfo:**\n[system-info.txt](system-info.txt)\n\n**Stacktrace:**\n\n```\nblender.exe!DRW_shgroup_call_add(DRWShadingGroup * shgroup, GPUBatch * geom, float[4] * obmat) Line 383\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\draw\\intern\\draw_manager_data.c(383)\nblender.exe!PAINT_TEXTURE_cache_populate(void * vedata, Object * ob) Line 286\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\draw\\modes\\paint_texture_mode.c(286)\nblender.exe!drw_engines_cache_populate(Object * ob) Line 1019\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\draw\\intern\\draw_manager.c(1019)\nblender.exe!DRW_draw_render_loop_ex(Depsgraph * depsgraph, RenderEngineType * engine_type, ARegion * ar, View3D * v3d, GPUViewport * viewport, const bContext * evil_C) Line 1483\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\draw\\intern\\draw_manager.c(1483)\nblender.exe!DRW_draw_view(const bContext * C) Line 1410\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\draw\\intern\\draw_manager.c(1410)\nblender.exe!view3d_draw_view(const bContext * C, ARegion * ar) Line 1334\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\editors\\space_view3d\\view3d_draw.c(1334)\nblender.exe!view3d_main_region_draw(const bContext * C, ARegion * ar) Line 1356\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\editors\\space_view3d\\view3d_draw.c(1356)\nblender.exe!ED_region_do_draw(bContext * C, ARegion * ar) Line 571\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\editors\\screen\\area.c(571)\nblender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 581\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\windowmanager\\intern\\wm_draw.c(581)\nblender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 715\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\windowmanager\\intern\\wm_draw.c(715)\nblender.exe!wm_draw_update(bContext * C) Line 868\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\windowmanager\\intern\\wm_draw.c(868)\nblender.exe!WM_main(bContext * C) Line 434\n\tat c:\\blender-git-2.80\\blender\\source\\blender\\windowmanager\\intern\\wm.c(434)\nblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 523\n\tat c:\\blender-git-2.80\\blender\\source\\creator\\creator.c(523)\n[External Code]\n```", "Blender - Texture Paint crashes\nOperating system: Windows 10 1709\nGraphics card: NVIDIA GeForce GTX 1050\n\nBroken:\nBranch:2.7\nHash: 6d89337257b6\nDate: 2018-12-24 14:03\n\n\nBlender crashes and closes when trying to bring up Texture Paint.\nAdd an object (default cube or other). Mark seams and unwrap. Select UV Editing and apply texture. Click on Texture Paint. Program closes. ", "Error in blender 2.8 beta (meshes and texture paint)\nOperating system: win10 Home\nGraphics card: Intel(R) Core(TM) i3-4030U\n\nBroken:2.80 b, 4c5e76025d83, 2018-12-22\n\n\nWhen I add any mesh object and I go to the texture paint tab, blender closes immediately. this only happens with the meshes. but if I eliminate the meshes before going to texture paint blender it does not close. the error occurs whenever I go to texture paint mode in any way.\n\n\n1. I open a new session in blender.\n2. I add any mesh.\n3. I enter texture paint mode.\n4. Blender closes.\n", "Crashing while trying to use Blender Beta 2.80's texturing.\nBroken: 2.80 (BETA) \nWorking: Yes but crashes.\n\nBlender BETA 2.80, Crashes for me while using Texture paint to make a \"skin\" for my models.\n\n1: Having my \"object\" selected.\n2: Clicking on \"Texture Paint\".\n3: Closes down without auto-saving.\n\nA bug reported by Ms.Foxy Winters (Gothic Drag Queen.)", "Texture Paint w/out Material Causes Crash\nOperating system: Windows 10\nGraphics card: GeForce GTX 1070\n\nBroken: 2.80 (c9df453ce70b)\n\nIf Texture Paint mode is accessed on an object without a material assigned to it, a crash occurs.\n\nStarting with default setup.\nDelete the default cube (press x and click or the delete key).\nPress the shift key + a and select a mesh object (every mesh except the circle mesh should work).\nWith the new object selected, go into texture paint mode.", "Blender closes on trying to use Texture Paint\nOperating system: wind10 64bits\nGraphics card: geforce gtx 1050ti\n\nBroken: version: 2.80 (sub 39), branch: master, commit date: 2018-12-22 09:56, hash: 4c5e76025d83, type: Release\nbuild date: 22/12/2018, 17:02\n\nWhen I select \"Texture Painting\" on an object with no material, the Blender closes.\n\nCreate any Object with no material and try to enter in Texture Painting Mode. The program will close all by itself.", "Crashed in texture painting in old file\nOperating system: Linux ubuntu 18.04\nGraphics card: Nvidia gt 610 (no vulkan support)\n\nBroken: 2.80 (sub 39) 2018-12-25 16:36, hash: 60b930af3e73 \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\nobject mode -> texture paint -> crashed [Artefacts.crash.txt](Artefacts.crash.txt)\n\nBased on the default startup or an attached .blend file (as simple as possible). [Artefacts.blend](Artefacts.blend)", "Texture paint mode crash\nWindows 10 64bits GTX 1050 TI latest driver\n\nBroken:\n2.80.39 hash:6b13f10d40e5 2018-12-23.\n\ncrash with adding new mesh to the scene then switching to texture painting.\n\n1 - either add new mesh like plane,cube..etc or delete everything then add new mesh.\n2 - switch to texture paint workspace." ]

[ "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", "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```", "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 when rendering animation\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.0\n\n\nI was rendering a simple camera animation overnight, Blender crashed about 2/3rd the way through. Here's the crash log.\n", "Blender 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 on pose library N-panel\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nEvery time I click on invert button (which invert filtering) inside pose library N-panel blender crashes under this condition that your active asset library set to all.\n\n1. First be sure animation pose library add-on is enable.\n2. Create new scene.\n3. Create an armature.\n4. Go to pose mode.\n5. Click on Animation tab on side bar(N-panel).\n6. Change active pose library from \"Current File\" to \"All\".\n7. Click on double arrow icon which indicate invert filtering one or two times.\n8. Blender will crash.\n\nI also tested on blender 3.6 Beta , It still exist but in v 3.6 beta you should click on view port shading options after step 6 to perform crash.\n\nAnyway I upload crash log.\nThanks a lot.", "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", "Crash when modifing materials after using BMesh in Depsgraph-Pre event\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\n\nBroken: version: 3.0.0\nBroken: version: 3.0.1 Release Candidate\nBroken: version: 3.1.0 Alpha\n\nI wrote a script with a function that copies a mesh via BMesh to another object and then changes it's materials. When I want to export the scene as an alembic, Blender crashes when the function gets called via the Depsgraph_Pre event. Depsgraph_Post and Frame_changed_Pre & Post all work fine.\n\n\n- Open the attached Depsgraph_Pre_Crash.blend file in Blender\n- Run the script\n- (Optional) Scroll on the timeline between frames 1 & 2 to check that the script works\n- Set the active frame on the timeline to 1\n- Export as alembic with default settings\n- Blender crashes\n[Depsgraph_Pre_Crash.blend](Depsgraph_Pre_Crash.blend)\n\n[Depsgraph_Pre_Crash.crash.txt](Depsgraph_Pre_Crash.crash.txt)\n\nHere is the callback registered in `depsgraph_update_pre`:\n```lines=10,lang=python\ndef updateFrame(scene): \n```\n emptyObject = bpy.data.objects[\"EmptyObj\"]\n firstOBJ = bpy.data.objects[\"Frame1\"]\n secondOBJ = bpy.data.objects[\"Frame2\"]\n```\n\n```\n if(scene.frame_current == 1):\n bmNew = bmesh.new()\n bmNew.from_mesh(firstOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n```\n\n #Doing anything with the materials crashes blender on alembic export\n```\n emptyObject.data.materials.clear()\n```\n\n```\n if(scene.frame_current == 2):\n bmNew = bmesh.new()\n bmNew.from_mesh(secondOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n \n emptyObject.data.materials.clear()\n```\n", "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)", "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 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.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", "Shader Nodetree Error: Invalid implicit socket conversion: Shader -> Color\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.33\n\nBroken: version: 3.3.1\nWorked: I don't know but the problem is also present in the version 3.0.0\n\n\n```lang=glsl\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.3\\config\\userpref.blend\nShader Nodetree Error: Invalid implicit socket conversion\nERROR (gpu.shader): GPU_material_compile FragShader:\n |\n\n 7164 | invert(float_from_Closure(tmp34), node_tree.u36, tmp37);\n |\n | Error: C1503: undefined variable \"float_from_Closure\"\n\n\nShader Nodetree Error: Invalid implicit socket conversion\nERROR (gpu.shader): GPU_material_compile FragShader:\n |\n\n 7164 | invert(node_tree.u35, vec4_from_Closure(tmp34), tmp37);\n |\n | Error: C1503: undefined variable \"vec4_from_Closure\"\n\nShader Nodetree Error: Invalid implicit socket conversion\nShader Nodetree Error: Invalid implicit socket conversion\n```\n\n\n1. EEVEE render\n2. Shader editor: put some shader socket to color socket\n3. Check the console", "2.83 3D viewport performance\nOperating system: Ubuntu 20.04 LTS\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2), version: 4.5 (Core Profile) Mesa 20.0.4\n[system-info.txt](system-info.txt)\n\nBroken: 2.83\nWorking: 2.82\n\nProblem seen in Workbench, Wireframe and Eevee.\nViewport performance it's really bad, I'm moving around just the initial cube scene at 15-20 Fps, older Blender versions movement is perfectly smooth.\nNo matter the scene/blend file, 2.83 offers worse viewport movement performance compared to older versions,\nIt's important to mention that only the viewport movement is being affected by this performance drop, everything else including rendering works smooth as butter just like older versions or even better. Splitting up the scene in windows kinda fixes this problem.", "(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" ]

[ "2.82 Crashing When Going To Material Preview\nOperating system: macOS Catalina, Vers. 10.15.3\nGraphics card: Radeon Pro 570 4 GB\n\nBroken: v 2.82\nWorked: ??\n\n\nProject is in Camera View. Select Material Preview icon in upper right of screen; then, click on down arrow to select different hdri for lighting changes. The drop-down window, with the selected hdri icon opens, and when I click on the hdri icon to cause the other hdri options to appear, Blender crashes, i.e. totally closes. This happens every time.\n\nI've reset Preferences to default; I've deleted and re-downloaded Vers. 2.82 - still happens.", "Crash when clicking on viewport shading properties\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.08\n\nBroken: version: 2.83 (sub 5)\nWorked: (optional)\n\nCrash when clicking on viewport shading properties\n\n1.open blender\n2.change shading to render \n3.click the properties drop-down \n\n[bug.blend](bug.blend)\n\n", "Crash when trying to access the viewport shading popover(Eevee).\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.83 (sub 5)\nWorked: 2.82 (sub 7)\n\nWhen enabling Ambient Occlusion then trying to access the viewport shading options Blender crashes, you have to be either in Material Preview or Rendered mode.\n \n\n 1- Enabled Ambient Occlusion (Eevee).\n 2- Switch to Material Preview or Rendered.\n 3- Click the Viewport Shading Popover.\n\n\nJust with the Default Scene.\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)", "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)", "Multi-layered image support\nWe already partially support OpenEXR multi-layer for the image editor and compositor.\nHowever we do not support other multi-layer formats (e.g., Krita, Photoshop), nor have it working well for materials (say, a single multi-layered file with albedo, roughness, ... layers).", "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", "GPencil: Airbrush draw tool with solid stroke has transparency artifacts\nOperating system: Win 11, GTX 3080, Wacom Tablet\n\n\n\nBroken: 2cd7e70c18a8\nWorked: ~~3.3.0~~\n\nThe airbrush tool has artifacts around the stroke during drawing. Also what is drawn during stroke has nothing to do with the final result visually. Please see the video for the issue.\n\n\n\n- New scene -> 2d Animation\n- Select Airbrush tool from the tool pane\n- Switch to `solid stroke` material from header\n- Draw\n\n[image](attachment)\n[blender_lOlSgoorkK.mp4](attachment)\n", "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)", "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!", "branches connected to inactive composite nodes are still being calculated.\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\nin the compositor, you can have multiple composite nodes, and only the selected one will generate an image. Currently the branches of inactive composite nodes are being calculated. I've never had this issue before, but I can't say for certain when it began, or if perhaps I've just never had branches complex enough to highlight the issue.\n\nin this example, my post rendering compositor calculation time rises from 20 seconds to 40 seconds with only two composite nodes.\n\n\n\n\n\n", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?", "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)", "Artefacts on render passes Shadow and Diffuse Direct when rendering image texture with zero value in a channel\nWindows 7 Ultimate, 64-bit SP1\nGeForce GTX 750 Ti\n\nversion: 2.79 (sub 1), branch: master, commit date: 2017-10-10 07:26, hash: 8d73ba5, type: Release\nbuild date: Tue 10/10/2017, 10:00 AM\n\nArtefacts on render passes Shadow and Diffuse Direct when rendering image texture with zero value in a channel. The scene is lighted with 3 spots each absolute red, green and blue.\n\n- Create a texture image file with absolute 0 spots in one channel. Or use this one: \n- Create a scene with 3 spots lights, each colored with an absolute red, green and blue color.\n- Add a random object with uvs\n- Assign the texture image file to the object (Tested with Principled BSDF, Diffuse BSDF, Toon BSDF).\n- Add Diffuse Direct and Shadow pass.\n- Render, get this: \n\n**Additionnal infos**\n- Other channels render correctly\n- Scene is lighted only with direct lights, bounces are set to 0.\n- Clamping lowest values to 1 in the texture map resolves the artefact partially.\n- Also shortly tested on unix system.\n- Blender file: \n[bug_cycles.blend](bug_cycles.blend)", "Strange background grid pattern appears on the compositor panel\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.9079\n\nBroken: version: 2.93.5\nWorked: 2.91.2\n\nStrange grid pattern appears on the compositor background when zooming in (when backdrop is on).\n\nThis is what it should looks like:\n\n\nThis is what it actually looks like:\n\n\nAnd this only happens when I zoom in. At a very far-away view the background gradually becomes normal:\n\n\n\n\nThis does not happen on my other devices, so I think it might be a hardware compatibility problem. Also, I had the latest graphic driver installed and the graphic card supports OpenGL 4.6:\n\n\n- Open blender\n- Switch to the compositor workspace,\n- Enable backdrop\n- zoom in.\n\n", "Unbaked Dynamic Paint Not Displayed in Rendered Output but Shows in Viewport\nOperating system: Manjaro 18.0.1 Illyria / x86_64 Linux 4.14.90-1-MANJARO\nGraphics card: Nvidia 1080 Ti\n\nBroken: 2.80 (sub 39), Commit date: 2018-12-29 18:10, Hash 266b1e2cdbc1\nWorked: 2.79 (sub 6), Commit date: 2018-10-22 16:17, Hash 86dbbd156fa\n\nUnless baked, dynamic paint does not affect the final rendered image but is properly displayed in viewport.\nThe default and expected behavior is to be able to render the effect regardless if baked or not. This is how 2.7x operated in the past.\nMoreover this problem, which I assume has something to do with vertex colors [has caused other issues ]] with different [[ https:*github.com/hsab/tensionmap | addons ](https:*github.com/JacquesLucke/animation_nodes/issues/989) that depend on similar workflows of modifying the vertex color using the python API (eg. proximity, stress mapping etc.) \nNot sure if #51214 is related since it's from April 2017. If so please close as a duplicate.\n\nTwo blend files attached, one for 2.8 and one for 2.79.\n2.79 file works as expected.\n2.8 file is broken unless baked.\n\n2.79.6 Render:\n\n\n2.80.0 render:\n\n\n[dynamicpaint2.8.blend](dynamicpaint2.8.blend)\n[dynamicpaint2.79.blend](dynamicpaint2.79.blend)", "Eevee in VSE as Scene strips - erratic behaviour\nOperating system: Win 10\nGraphics card: Radeon RX580\n\nBroken: 2.80 version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-16 23:08, hash: 12da679fa094, type: Release\nbuild date: 16/06/2019, 17:07\n\nWhen using Eevee Scene Strips in VSE , the VSE viewport shows the wrong items on screen in OpenGL preview, and then the Render also does not show correct layering or camera moves\n\nOpen Blend file\nSee 3 scenes. \n- 2x animated (linked) scenes that render several layers in Eevee properly, then composite as expected\n- 1x Edit scene that has those linked scenes as Scene Strips in the VSE.\n\na) Observe in VSe that the viewport doesn't not reflect each Eevee scene in preview.\nb) Press render in VSE scene, and observe the render layers are broken and don't match the orig scene.\n\n[20190626.blend](20190626.blend)", "Inconsistencies between 3D Viewport and Viewport Render Image using the GPU Shader Module\nOperating system: Ubuntu 18.04, Windows 10\nGraphics card: GeForce GTX Titan X, GeForce GTX 1080 Ti\n\nBroken: \n2.83.0\n2.90.0 Alpha\nWorked: Never\n\nRendering the `3D Viewport` with `3D Viewport/View/View Render Image` (i.e. OpenGL rendering) does not render elements drawn with the [GPU Shader module ](gpu.html).\n\nThe problem is illustrated in the following example, which shows the `3D Viewport` (left) and the rendered result of `View/View Render Image` (right).\nThe points drawn with the GPU shader module are neglected during OpenGL rendering.\n\n\nExcecute the [3D Lines with Single Color ]] example of the [[ https:*docs.blender.org/api/current/gpu.html | GPU shader module documentation ](https:*docs.blender.org/api/current/gpu.html#d-lines-with-single-color).\nThen, render the results with`View/View Render Image` as shown in the image below.\n\n\nThe lines visible in the 3D Viewport (left) are missing in the rendered result (right).\n " ]

[ "Compositor sometimes fails to composite (Image Editor involved)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\nand\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90\n\nIn this .blend file\n[compositing_291_bug.blend](compositing_291_bug.blend)\nthere are 3 scenes, each with a different object, that are overlayed in compositor.\n\n - Open the file and render (F12).\n - If you're seeing 3 objects that means compositor worked.\n\n - Try render (F12) again. It may take couple of attempts but eventually you should see that there is now only monkey object from scene 3 rendered.\n\n - If you still can't reproduce, you can also try to 'maximize' the image view window. I noticed that it may trigger the bug, but could be a red herring.\n\n - Now change \"Layer\" from \"Composite\" to \"View Layer\"\n\n - And then back to \"Composite\".\n\n - All three object are now rendered." ]

[ "Using subdiv modifier affects normal baking performace of all objects in scene\nOperating system: Windows 10\nGraphics card: GTX 1080Ti\n\nBroken: version: 2.83 (sub 10)\nWorked: Never (2.8+)\n\n[#60428.blend](T60428.blend)\n- Open file\n- Press bake, watch memory usage\n# Remove subsurf modifier on `door_frame_low.001` object and repeat step 2\n\nBaking is much quicker and doesn't require too much RAM\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)", "Blender crashes after GPU spike (Specially when we have a character with Rigify)\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: 3.4.1\nWorked: 3.3\n\nEvery time I'm working in Blender, after 2 minutes if I start to move around on a rig made based on Rigify, or work on geometry nodes, Blender Crashes. It happens even faster if I'm working in eeve.\n\n- Open a blender file\n- Import a character using rigfy with Linked Library\n- Library override\n- Turn Eeve on\n- Start working\n- Eventually, blender will crash.\n\nI noticed that if I don't import a character with rigfy, it doesn't have the GPU spike\n[Christmas.crash.txt](Christmas.crash.txt)\n[KalyAndAkrasiel 3.5.crash.txt](KalyAndAkrasiel_3.5.crash.txt)", "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", "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```", "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", "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", "Crash while using several rigid bodies and some force fields.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe scene is pretty simple, a house with some elements used as rigid bodies and some force field, vortex and wind force are applied.\n\nWhen I play the animation, it starts and around frame 140-200 it crashes.\n\nAttached blend file. The only thing to do is to play the animation and wait for the crash.\nAttached crash report.[Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash](Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash)\n\n[casaFalla.blend](casaFalla.blend)\n\n", "Viewport Render crashes on macOS 12.3\nOperating system: macOS-12.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.1.0 Beta\n\n\nUpdated MacOS to 12.3 (Beta) and going to Viewport Render will cause a full Mac freeze then crash. A hard reboot is the only resolution.\n\nNot sure if this is caused from the latest version of MacOS (12.3 Beta) or if it's the latest version of Blender (3.1Beta). \nI haven't tried with the latest Blender 3.1 Beta build with Monterey 12.2 Beta as this would require me to wipe the computer and reload all apps and files in the OS downgrade process.\n\nOpen default scene and toggle the Viewport Render button.\n\n", "Blender 3.5 crash on render with Intel 4600 integrated GPU\nOperating system: WIndows 10 x64\nGraphics card: Intel 4600\n\nBroken: 3.5 \nWorked: 3.4.1\n\n\nBlender crashes when attempting to render in Evee. Cycles seems to work.\n\n", "CPU render will look different to GPU render and fails randomly\nWin 10, GTX 880M, GTX 1080TI Founders Edition\n\nBroken: blender-2.79.0-git.2ca1f29-windows64\nWorked: na\n\nAttached you'll finde a scene what has issues with GPU rendering. The scene is using the old shaders with a bevel shader (OSL).\n\nThe preview will not start or maybe it takes a very long time. Here nothing happened.\nIn GPU mode the preview starts as expected.\n\nWhen I try to render with F12 in CPU mode it doesn't start or maybe it will start after a long time. Here nothing happened after 10 minutes.\nWhen I render a small region with CPU it takes a long time till it starts to render.\nWhen I start rendering in GPU mode it starts fast as expected ignoring OSL of course.\n\nIn the ZIP and attached you'll see a picture with a split screen. Left side is GPU. Right CPU. The results are different. Transparent parts with DOF will have extreme noise.\n\nLoad the scene and press F12. Here CPU render will not start as expected.\nSwitch to GPU and press F12. Rendering will start.\nDefine a small region where the transparent parts are. Press F12. It will take really long but start. Result has noise at the transparent parts.\nThis might be a bug in the Cycles render engine or an issue with the shader tree.\n\n[170902_Blender_279_Cycles_CPU_Issue.zip](170902_Blender_279_Cycles_CPU_Issue.zip)\n\n\n\n", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "OpenEXR can't be used to save results during the render process\nOperating system: XUbuntu 20.04\nGraphics card: Not applicable\n\nBroken: Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nWorked: Blender 2.93.7\n\nSeems OpenEXR now can't be used to save intermediate results during rendering using Cycles. The other formats (like PNG) seems works just fine. Blender starting v3 just crashing if you trying to save as single or multi-layer EXR. When the render is completed the `save_render` function is working correctly.\n\nThis bug doesn't allow to prepare the proper distributed preview for user outside of Blender UI (EXR needed to merge multiple preview samples from the remote workers).\n\nThe default cube blender scene is just enough to reproduce. Please switch to script console and paste the next code:\n```\nbpy.context.scene.render.engine = 'CYCLES'\nbpy.context.scene.render.image_settings.file_format = 'OPEN_EXR' # OPEN_EXR_MULTILAYER here will fail too, but PNG for example will work just fine.\nbpy.context.scene.cycles.use_adaptive_sampling = False\nbpy.context.scene.cycles.samples = 512\n\nbpy.ops.render.render('INVOKE_DEFAULT', use_viewport=True)\n\nimport time\ntime.sleep(2)\nbpy.data.images['Render Result'].save_render('_preview.exr')\n\n### Crash will be right here ###\n\nimport os\nprint(\"Preview file exists:\", os.path.exists('_preview.exr'))\n```\n\nCrash report: [blender.crash.txt](blender.crash.txt)\n", "Blender just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "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" ]

[ "Volume Absorption hangs RenderPreview w Cycles in Viewport when GPU Compute AMD\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.5.1 27.20.1017.1011\n\nBroken: version: 2.83.1\n\nAdding Material Propperties->Volume->Volume Absorption breaks Viewport render preview when rendering with Cycles engine with GPU. \n\n1. Set render engine to Cycles\n2. Set render device to \"GPU Compute\" (in settings set to OpenCL)\n3. In material properties set Volume->Volume Absorption\n4. Switch viewport to \"Render preview\"\n5. \"Path Tracing Sample\" will indefinitely get stuck at 1/32\n6. Switch Render Properties->Device->CPU compute and the preview render works without problems. (CPU AMD FX-8350)\nNote: For the actual render (F12) it is possible to render with GPU (and GPU+CPU) without problems\nNote 2: As soon as the Volume Absorption is removed the Render Preview in Viewport works fine also with \"GPU Compute\"\n[Bug_VolumeAbsorption.zip](Bug_VolumeAbsorption.zip)\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", "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", "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", "Camera Background image is appearing greyish in 3D Viewport \nOperating system: Windows 10\nGraphics card: Nvidia GTX 1080Ti\n\n**Blender Version** 3.2.1\nBroken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac9e\nWorked: \n\nCamera Background image is appearing greyish in deep black area in 3D Viewport but showing completely normal in Image editor section and renders. \nEven after turning on \"View as Render\", problem is still there.\n \nOpen the attached blend file.[Blender BG Bug Report.blend](Blender_BG_Bug_Report.blend)", "Polishing the Painting Experience\nThere are a few tasks that would enhance the texture painting pipeline that could be prioritized before advanced features like layered textures is even considered.\n\n## Existing Painting System\n\n### Small Tasks (e.g., bug fixing)\n- [ ] Graphics Tablet Lag when in Texture Paint mode in Blender 3.0 #93796\n- [ ] Undo bugs\n - [ ] Undo eliminates brush texture #88592\n - [ ] Texture paint undo can changes texture slot #62520\n - [ ] Texture Paint mode tools swap when exiting maximized area #98014\n- [ ] Color space support for texture painting #95797\n- [ ] Sync Image Sequence options (Frames, Start Frame, Offset, Cyclic, Auto Refresh) #109769\n- [ ] Texture paint: Bleedind around thin cuts do not fill texture #106066\n- [ ] Add support for \"Channels\" to the Images & Color Attributes #108404\n- [ ] 8/16 bit textures have different strength behavior (premultiplied problems) #101436\n- [ ] UDIM bugs [need report]\n- [ ] 3D mirroring in Image Editor\n- [ ] Other bugs (by Daniel Bystedt) [need report]\n\n### Bigger Tasks (e.g., re-designs) - need design\n- [ ] Image syncing between Editors via active image canvas #103636\n- [ ] Multi-object painting\n- [ ] Multi-object uv editing\n- [ ] Support \"viewport\" face sets in Image Editor\n- [ ] Square brush\n\n## 3D Brush\n\nRelated to #96225\n\n### 3D brush vital\n- [ ] Color sampling\n- [ ] Erase blend mode\n- [ ] Affect only visible (Show/Hide)\n- [ ] Affect Alpha option\n- [ ] Masking\n- [ ] (2D) Fill operation\n\n### 3D brush additional\n- [ ] Feature parity\n - [ ] Blur & Smear brushes\n - [ ] Clone brush\n - [ ] Sync masks and edit mode selection\n - [ ] Paint modified geometry instead of base mesh\n - [ ] Missing brush settings\n - [ ] Stencil masking\n- [ ] Image editor syncing\n- [ ] Dedicated paint mode\n- [ ] Performance\n\n", "Grease Pencil phasing through objects even when 3d location is selected \nOperating system: Windows 10\nGraphics card: NVIDIA RTX 2060 SUPER\n\n3.1.2\n\nGrease Pencil strokes that should be under the floor/behind objects are phasing through with a weird grainy texture. Looks perfectly fine in viewport rendering but when I render an image/animation it looks weird. Not sure what im missing or if its a bug?\n\n**Blender project**\n[clothtest.blend](clothtest.blend)\n\n", "Some Overlays are not rendered in Viewport Render (Text Info incl object name, Statistics, 3D Cursor)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.1\nAlso 3.1.0 Alpha\n\nUsing viewport render (or workbench) I'm unable to view object or empty names \n```\n(bpy.data.objects[\"NAME\"].show_name)\n```\n\nEnable show name on a visible object, and make a viewport render (bpy-ops-render-opengl)\nThe text isn't rendered in the image like it is in the viewport.\n\n", "Grid lines showing up when origin is far from mesh\nOperating system: Win 10 Home\nGraphics card: GTX 1070\n\nBroken: (example: 3.2.1, a2d59b2dac9e, master, 2022-07-05, as found on the splash screen)\n\n\nGrid lines showing up when origin is far from mesh but only when bumping out the normals in the shader editor, more testing required. (only happens in cycles regardless of optix/cuda or cpu rendering)\n\nopen the attached blend file and go to camera view, then switch to viewport shading or render an image. you will notice a grid on the surface of the plane in certain areas. And the grid goes away when origin is set to centre of mesh. Or you disable the bump node in the shader editor. Seems to be a rendering bug.", "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.", "Dynamic Paint sub-steps doesn't work with particles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.0 Alpha\n\nWhen using a particle system as a dynamic paint brush, the sub-steps setting of the canvas doesn't work. The sub-steps appear to work as intended with all other brush types. Whether the painting is done with vertex or texture maps doesn't seem to have an impact on the bug.\n\n* Open attached .blend\n* Bake the dynamic paint cache with a sub-steps value > 0\n* The result shows no sub-steps\n[Bug2.blend](Bug2.blend)\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", "Grease Pencil drawing only show up when pen is lifted from tablet\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800S ATI Technologies Inc. 4.5.14802 Core Profile Context 21.40.64.30 30.0.14064.30001\n\nBroken: version: 3.6.1\n\n\nGrease Pencil is not the same as before. When I press down to draw something with the pen, it won't show up- until after I lift my pen up from the tablet and then it shows what I drew. This is bad because I can't draw if I can't see what mark I made. It only shows up after and ruins the workflow.\n\n\nI open up Blender, the updated version: 3.6.1. I click: 2d animation to start. Then I click pen as my grease pencil drawing tool. I draw something on the canvas. I press down to draw a shape. Nothing shows up as I press down on the canvas. I lift my pen off the tablet and then I see what I 'drew'. A horrible squiggle line because I cannot see what I'm drawing as I'm drawing. I did not have this problem with the past version of blender that I had: Blender 3.3.1. \n\n~Karina\n\n", "Greasepencil z fighting alpha issue\nHi,\nnot too sure if this is known issue or any fix but I am getting this alpha issue from certain angle when I have 2 different grease object. \n\n", "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", "Line Art Thickness doesn't consider Render Resolution Percentage\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1122\n\nBroken: version: 3.2.2\nBroken: version: 3.4.0 Alpha\nBroken\n\nWhen using Line Art Modifier, on a Grease Pencil Object in Screen Space Mode, Line Thickness doesn't scale with resolution as expected. \n\n1. Open new General Startup File\n2. Create New Object>Grease Pencil>Scene Line Art\n3. Under Object Data Properties>Strokes>Stroke Thickness and set to World Space\n4. Set Render Resolution % to a factor. line thickness will be different than expected\n\n\n\n\n\n" ]

[ "Texture painting: \"normal\" option not working correctly.\nWindows 7 64bit\n\nBroken: official 2.72 release and also 2.72 4d4d2a31\n\n\nIn texture painting mode, on 3d viewport, the \"normal\" option is working weirdly: brush strokes are sometimes not \"showing up/ working\" even when supposed to be working, especially when painting close up to the mesh.\n\nAdd a cube or other mesh, uv unwrap it, assign a texture and go to texture paint mode.\nStart painting/brushing with the default brush and move, rotate, zoom in the object being painted.\nWhen view is close to the object paint strokes stops to work even if the angle towards the view is below the \"normal option\" treshold; they sometimes resume to work if the view is modified.\nWhen disabling that option brush strokes are working correctly.\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", "Irradiance volume Distance should not be affected by scale\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.34\n\nBroken: version: 2.80 (sub 51)\nWorked: N/A\n\nWhen you scale the Irradiance Volume to the size of a room (e.g. 6m x 4m x 2.4m), then the Distance is scaled too, and hence scaled non proportionally.\n\nFurthermore I expected the Distance to represent an actual Distance, in particular because it expressed as one (e.g. 1 metre).\n\n\n1. Create a Cube which will be sized to be a room. Set Dimensions to X=6m, Y=4m, Z=2.4m. (This is just to compare against the irradiance volume.)\n2. Create an Irradiance Volume. Scale to X=2, Y=1.2, Z=1. Set Irradiance Distance to 1m\n3. Observe that the Irradiance volume now overlaps the Cube, and that due to the non-proportional scaling there is more irradiance influence in the X direction compared to Z.\n\nWhy does this matter? I would think that for architectural scenes you probably want to carefully control the irradiance volume influence distance so that indirect lighting does not extend through the wall into an adjoining room. Furthermore you do want to ensure the irradiance volume does correctly overlap the walls, and in some cases it might be important to position the irradiance probes close to the wall. Using the current non-proportional scaling, and the Distance that is actually a factor it is hard to achieve this.\n\n\nNote if I import a file from 2.79 where the units were set to centimetres then unit scale is set to 0.01. This means that the Irradiance Volume requires massive scaling to get it to the correct size (e.g. 200, 120, 100) - hence the Distance must be set to a very small number - specifically 0.01m.\nI note that if I create a file in 2.80 then when setting the Length to Centimetres it does not change the Unit Scale. So perhaps this is now handled better.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nI can't see where to do this - however the blend file is not particularly important.", "Mantaflow APIC creates wrong droplet behaviour\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Alpha\n\nIf you create a big ball of water with the APIC solver, it breaks apart when falling. FLIP keeps the ball spherical until it touches the collision and APIC deforms it incorrectly immediately.\n\n**FLIP** (left) vs **APIC** (right) \ntimesteps were set to MIN 4 and MAX 8\n[Drop_FLIP_vs_APIC.mp4](Drop_FLIP_vs_APIC.mp4)\n\n\n\n\n - Create any primitive (I used an Icosphere in my case)\n - Perform a Liquid quick effect on that primitive\n - Change the simulation from FLIP (where it works) to APIC (where it doesn't work)\n - Simulate and observe\n\n\nBased on the default startup or an attached .blend file [Droplet.blend](Droplet.blend)\n\n", "Smoke Domain glitching outside of its cache range 2.91.2, 2.9 Beta\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0 Beta\n\nIf you have a smoke/fire simulation and the playhead is outside of the cache range of the smoke domain. The 3D viewport and the render shows glitches in the domain.\nAlso the same glitch happens in 2.9.2\n\n[Mantaflow bug Test.blend](Mantaflow_bug__Test.blend)\n\n[2021-02-14 03-26-24.mp4](2021-02-14_03-26-24.mp4)\n[2021-02-14 03-34-25.mp4](2021-02-14_03-34-25.mp4)\n", "Fluid/Smoke modifier has an \"Apply\" button, which is misleading/dangerous (only meaningful for mesh-baked liquid domains)\n(All systems)\n\n- 2.81a and earlier (pre-mantaflow)\n- and 2.82 Alpha (2020-01-05) 5c66739b782e (mantaflow)\n\n**Short description of the error**\nAll objects involved in a fluid (gas or liquid) simulation, including domains, effectors, etc, have a modifier in the modifier stack.\n\nHowever, in all cases except one, the \"Apply\" button in this modifier is (as far as I can tell) just a synonym for \"remove the modifier and the physics settings (destructively!)\". It only actually \"applies\" something when we're dealing with mesh-baked liquid domains.\n\nSuch \"Apply\" button may be misleading and dangerous if a user were to, for instance, try to \"freeze\" a frame of a smoke simulation, which will just result in them losing all cache.", "Particle system with collision modifier hangs on baking\nOperating system: Linux-5.8.0-55-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\nWorked: 2.81a\n\n[#88965.blend](T88965.blend)\n\n- Open file\n- Bake particles on LRG_Submarine_Propeller object\n\nIt fails. When you disable collision modifier on LRG_Submarine_Hull object or simplify it considerably, it works.", "Surface tension is not working\nOperating system:Windows-10-10.0.19041-SP0 64Bits\nGraphics card:NVIDIA GeForce RTX 2080/PCIe/SSE2\n\nBroken:3.1.0 Alpha, branch: K-Cycles, commit date: 2022-01-16 15:45, hash: 164a13275cf8\nWorked: \n\nIn mantaflow fluid simulation, change the value of 'surface tension' does not work at all, My cpu is Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz, i tried different version of blender, it didn't work either\n[surface1.blend](surface1.blend)", "Particle collisions aren't simulated before frame zero for negative frame simulations\nBroken: 2.79, 2.81\nWorked: (optional)\n\nMaking particles simulation start from negative frames don't allow for those particles to have collisions with meshes. Unless I set the initial frame to be negative.\n\n\nOpen the file and look at the already baked simulation. The first particles went through while the later ones collide perfectly. You can also rebake the cache and see the same result\n\n[ParticleBug.blend](ParticleBug.blend)\n\n**Known workaround**\nChange initial frame to match the first simulated frame before baking the simulation.\n\n", "Flashing vertices on screen updates\nWindows 10 Home, version 1909, 64-bit\n| Graphics card: | Author:\n| -- | -- |\n| GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 | @Code_Craft_Plugin\n| GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89 | @MontagueMGM\n\nBroken: 2.83.0 - 2.83.10 (still broken as of latest 2.92.0 alpha experimental build acbda123ad08)\nWorked: 2.82.7\n\nVertices flash when the screen is updating. Only on my desktop using a GTX 780, not my laptop using an i7-1065G7 (Intel Iris Plus)\n\nCreate an Ico Sphere with subdivisions set to 6. It happens at levels 5 and 7 as well, but not nearly as noticeable. It seems related to a specific vertex count, rather than proportional to the number of vertices.\n\n[Blender 2021-01-12 02-13-49.mp4](Blender_2021-01-12_02-13-49.mp4)", "Support warnings for field input nodes\nField input nodes evaluate in a context, but currently they give no warning if they do not support\na particular context. The initial goal is to add a warning like \"Input node does not support geometry type: Mesh\" on the spline parameter node in the following situation:\n\n{[F12738459](image.png) size=full}\n\n### Implementation\nA potential implementation isn't clear.\nIt seems there needs to be a way to keep track of which node (`bNode`, `NodeRef`, `DNode`, etc.) the field input node came from.\nThen the field evaluation system should have a way to collect errors and return them to the caller. Or maybe the caller can pass a\n\"logger\" class to the field evaluation system. That generalization could allow more specific breakdowns of node timing in the future.", "Improve Interior Face Selection Method #2\nOperating system: Win 10 Pro\nGraphics card: nVidia GeForce GTX 1070ti\n\nBroken: tested in 2.80 stable and 2.81-dcad1eb03ccc\n\n\nIn Edit Mode Select -> Select all by Trait -> Interior Faces does not select all expected Faces.\n\n\nIn the attached blend file try to select the interior faces by trait and nothing happens. The object was created by moving a default cyclinder and UV sphere into each other and merging the vertices at the spheres equator by distance. After the merge the top face of the cylinder is selected by trait as expected while the lower faces of the sphere are not.\n\n[interior_faces_bug.blend](interior_faces_bug.blend)", "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", "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)", "Scaled Rigid Body causes issue (moving origin or mesh breaks collision, double transforms on negative scale)\nOperating system: Ubuntu 18.04 LTS\nGraphics card: Intel HD 4000\n\nBroken: 3.0\nBroken: 2.90.1\nWorked: I don't know if this works with any other version, I created the file using 2.90.1.\n\n\nSee the attached .blend file. This file contains two errors with Rigid body simulation. I'm filing both errors in one bug because these may be related (both happen in one example simulation).\n\nError 1: object origin distance from another object changes interaction between objects\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that \"Ball\" is attached to the chain.\n3. Stop the animation and jump to first frame.\n4. Select object \"Ball\" and from menu Object - set Origin - Origin to Center of Mass (Volume)\n5. Play the animation to verify that \"Ball\" is no longer attached to the chain.\n\nError 2: Rigid body type \"Active\" changes orientation of the object\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that chain is attached to the object \"Cube\".\n3. Stop the animation and jump to first frame.\n4. Change \"Cube\" Physics properties - Rigid body - Type: Active and Settings: Dynamic\n5. Play the animation and notice that Cube is now rotated 180 degress around the X axis. Obviously this results in chain no longer connected to the cube as expected and chain and Ball drop directly down during the animation.\n\nExample .blend file (cannot simplify more because Blender seems to be unstable with this file):\n[physics-test.blend](physics-test.blend)\n\n**Additional information**\nIt seems that I can work around Error 1 by selecting all items and applying \"Rotation & Scale\". I think this should not be required to get two objects to interact during simulation so I'm reporting the problematic file as-is. I cannot figure out the reason nor workaround for Error 2.\n\n$ apt policy blender\nblender:\n```\nInstalled: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nCandidate: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nVersion table:\n```\n *** 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0 500\n 500 ubuntu bionic/main amd64 Packages\n", "free style does not work if there are nested collections\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.91.2\n\nI'm not sure it can be called \"bug\", but if I apply freestyle to a collection (which I call \"Lines\") that contains others, it doesn't work\n\nI create objects to which I want to apply freestyle, I put them inside each of its collections. If I apply the freestyle option to the \"Lines\" collection it doesn't work. It only works if the objects are directly inside the \"Lines\" collection. It is a problem when I work on very complex scenes where it is useful to organize objects within many collections and I want to apply freestyle only to some of these collections by inserting them into a larger one (Lines) and leaving the others in another call \" no lines \"[freestyle.blend](freestyle.blend)\n\n\n\n" ]

[ "Water Simulation\nOperating system and graphics card\nWindows 8.1, Graphics Card is unknown.\nBroken: (example: 2.69.7 4b206af, see splash screen) 2.69.0 r60995\nWorked: (optional)\n\n**Short description{[F68301](Final.blend)} of error**\nI've reported this problem before and someone gave me advice that worked only once. Both times I started with the loaded factory settings.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nOpen the attached .blend file (I hope it attached properly) and inside you will find a large cube (the Domain) and inside that you will find a plane that I extruded out to be a closed mesh with a hole in it. In the hole I have placed a cube with the inflow property. The other mesh is an obstacle. When I bake the simulation it doesn't work. the domain doesn't even disappear. But if I stop it and move the inflow cube out of the hole it works fine. " ]

[ "Geometry nodes preview, clipping Region in the viewport its not working\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\nTo be compleatly honest i don't remember if this was a limitation of the preview node or not and i was unable to find the answer. \nSo as the title says viewport clip in viewport doesn't work in the geonodes overlay preveiw\n\n\n- Try to preview any data from geometry nodes. \n- alt+b to do a viewport clip\nshould look like in the left side of the image above, but it seems that a second geometry with the info from geo nodes in alpha blend mode its not being clipped \n\n", "Bend Tool Todo\n## Bend Tool Todo\n * - [ ] {icon circle color=green} We should add the Bend tool to the toolbar\n * - [ ] {icon circle color=green} Should work with drag-release paradigm, similar to other tools in the toolbar\n * - [ ] {icon circle color=green} We should introduce an interactive Gizmo for this tool, such as this:\n * - [ ] {icon circle color=yellow} Just like the transform gizmos, the manipulator should be visible immediately, not only *after* the initial bend operation.\n\n", "Render Region widgets do not appear when active object is not a camera\nOperating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.1\nAlso broken: version: 3.6.0 Alpha\n\nWhen there is any active object in scene the render region widgets are invisible.\n\nDefault scene.\nCtrl+B to set render region\nNo widgets are visible\n\nDelete all objects\nThe render region widgets are visible and accessible.\n\n\n", "Back side of rotate gizmo appears when approaching small object\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.41\n\nBroken: version: 3.6.1\nWorked: 3.4.1\n\nWhen approaching a small size object, the back side of the Rotate gizmo is displayed.\nThis happens not only in Perspective view, but also in Orthographic view and Camera view.\nThis did not occur in Blender 3.4.1.\n\n\n1. Add a Cube of Size 0.02m\n2. Press \"Numpad .\" to approach Cube\n3. Show Rotate Gizmo\n\n", "context override for bpy.ops.view3d.view_selected doesn't work\nBlender 3.6\n\nTried to override currently selected items and run `bpy.ops.view3d.view_selected` (default blender operator binded on \"Numpad .\" by default) and it doesn't work. If I select objects manually with `obj.select_set(True)` it works.\n\nI've compared context's dict produced by `bpy.context.copy()` - the only difference between the context after `.select_set` were `selected_objects`, `selected_ids`, `selected_editable_objects` and I've overidden them.\n\nWay to reprodiuce:\n1) Open default blender scene.\n2) Make sure nothing is selected and move camera away.\n3) Run the code below - nothing happens\n4) Uncomment first two lines of code - operator works.\n\n```python\nimport bpy\n\n#for obj in bpy.data.objects:\n# obj.select_set(True)\n \nfor area in bpy.context.screen.areas:\n if area.type == 'VIEW_3D':\n for region in area.regions:\n if region.type == 'WINDOW':\n override = {\n 'area': area, \n 'region': region\n }\n override['selected_objects'] = bpy.context.view_layer.objects[:]\n override['selected_ids'] = bpy.context.view_layer.objects[:]\n override['selected_editable_objects'] = bpy.context.view_layer.objects[:]\n with bpy.context.temp_override(**override):\n bpy.ops.view3d.view_selected()\n # print(bpy.context.copy())\n```\n\n", "Node Tools Overview\n## Background\nWith node group assets becoming more prevalent and geometry nodes becoming essential\nfor manipulating geometry in Blender, we want to add the ability to implement operators\nwith geometry node groups.\n\nRelevant node groups would need a geometry input and output, and could have other inputs (and possibly outputs), with similar mappings as the geometry nodes modifier.\n\nAdditionally, specific inputs could be marked as editable modally, for example, a \"Factor\" input could be controlled by moving the mouse cursor left or right.\n\nThe specific data design still needs to be settled on (i.e. is the node group an operator, or does an operator reference a node group?).\n\n## Design\n- The node group itself is the operator asset\n- Geometry nodes gets new input nodes\n\t- Selection\n\t- Mouse coordinates\n - View transform\n - 3D cursor location\n - etc.\n- Geometry node groups with these input nodes can only be used as operators\n\t- This design is similar to the shared node groups between shader and geometry nodes, for example.\n- The group outputs are used to adjust the output geometry\n\t- The geometry output will adjust the \"active\" geometry\n - We _might_ need to store a specific mapping for outputs, but relying on the name is a start\n- The project is \"completely finished\" when any existing edit mode operator could be implemented with nodes\n\n## Implementation\n\n_Organized by priority in each category_\n\n### 4.0 Targets\n\n_Changes needed to move the feature out of experimental and enable it in the release_\n\n- [x] Initial basic feature for curves sculpt mode e4cc91a6113f14418b5d8f2a0aace252dc3949d8\n- [x] Allow controlling which modes assets are available in fd9d22ba57d75b278a0350492c5eab2d39d39070\n- [x] Update 3D view menus dynamically (avoid need to restart Blender) cc83951951efc28411960d950435224e8d06606c\n- [ ] Make object info node geometry output work properly\n- [x] #111529 Show menus for unassigned node group assets d2d4de8c710c4e8e648a86f904e6436133664836\n- [x] Tool specific nodes\n - [x] Selection input e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] Set selection e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] 3D cursor e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] Sculpt face sets input e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n- [ ] Node group inputs displayed in the redo panel\n - [x] Initial input drawing bc393c403325c956ec4e83eeb072a9bdb2e7824d\n - [x] Display node group name in panel title f0467b4615b366f34f0daae81ef717c342e8f520 ee1ee584ded3b76fdd9b661244274af850b08fa9\n - [ ] Add attribute search\n - [x] Don't draw redo panel when there are no inputs c59d998ce524e37c2449694602fb6d57b6d292fa\n- [x] #111523 Improved default traits b4dc16f32d92a2fbc140abfe6eb438ff11b5d5e8\n- [ ] #111524 Finalize trait popover locations\n- [ ] Add support for evaluating output attributes\n- [x] Shortcut support 65591b2c8cc83b024bc0a283bae1bbeb7ee85132\n- [x] Quick favorite support 65591b2c8cc83b024bc0a283bae1bbeb7ee85132\n- [ ] #111526 Filter data-block selector based on tool/modifier option #112389\n- [ ] Publish the user manual\n\n### Polishing\n\n_Not necessarily required for a release in main_\n\n- [ ] Show visual difference for tool nodes in modifier context\n- [ ] Show visual difference for viewer and simulation nodes in tool context\n- [ ] Resolve flickering in asset browser when using redo panel\n- [ ] Warnings in node editor header\n - [ ] When node group is not an asset (with button to mark as asset) #110813\n - [ ] When the node group is not marked as a tool #110813\n - [ ] When asset is not in a catalog (and not in a menu) #110813\n\n### Milestone 2\n\n_The second phase of the project, after the fundamentals are working well_\n\n- [ ] Option to show settings in popup before operation starts\n- [ ] Tool specific nodes\n - [ ] Sculpt \"soft selection\" input and set\n - [ ] View transform\n - [ ] Mouse position\n - [ ] Deformed (\"cage\") positions\n- [ ] Modal operator support\n- [ ] \"Wait for cursor\" option\n- [ ] Store operator properties for the next execution\n\n\n## Use Cases and Ideas\n- [ ] Mesh sculpt \"face set extract\"\n- [ ] Mesh sculpt \"mask extract\"\n- [ ] Lasso selection operator", "Texture on active object is not visible in solid view with sculpt mode activated\nOperating system: Windows 10, Ubuntu 16.04\nGraphics card: GeForce GTX 760\n\nBroken: 2.80\n\nTexture is not visible in solid view with sculpt mode activated\n\nCreate a texture, apply it to an object, like start cube, make sure you're in solid view mode with textured color active, you'll see the texture in object mode. After switching to sculpt mode, object becomes gray.\nIf you change view mode to LookDev or Material, everything is fine.\n\n**Extra info**\nIf you go back to Solid view and add a Shape Key, texture is visible again, but mask brush doesn't work. The problem with mask brush and shape keys is already mentioned #67303\nI made a video about those problems Mk2w41C87AI", "Error \"Gizmos hidden in this view\" when trying to delete with measure tool and gizmos disabled\nOperating system: Windows 10 64 bit\n\nBroken: 2.83 release, 2.90 ec776f18ff70\nWorked: blender-2.82a-windows64\n\nIf the \"Measure\" tool is selected AND gizmos are turned off (\"Show Gizmo\", in the top right next to \"Overlays\"), trying to delete with the X Shortcut will result in the error \"Gizmos hidden in this view\".\nIf either\n* another tool is selected, or\n* gizmos are enabled\ndeleting works as expected.\n\n[delete_without_gizmo.blend](delete_without_gizmo.blend)\nOpen the file.\nHit the X key.\n\n", "Volumetrics: Add Light Grid support\nVolumetrics are currently not affected by lightgrids. FIX THAT.", "Trim tools doesn't work with Dyntopo enabled\nBroken: blender-2.92.0-ef5d6e9c457a-windows64\n\nEnable the experimental \"tools with missing icons\"\nFile ´/ New / Sculpting\nEnable Dyntopo\nChoose the box or trim lasso tool and try to trim the mesh\nDoesn't work", "Custom Nodes customizable Header for the Node Editor\nHi\n\nThis is a follow up from my closed design task:\n 104066\n\nAs @brecht suggested the best way will be to create a dedicated function that every addon can use to customize the header. \n\nI'm going to investigate if it can be donein `release/scripts/modules/bpy_types.py`.\n\nI hope I can get it done this time. \n\nCheers, \nDavid\n\n", "gpu.types.GPUOffscreen renders nothing when samples > 0\nOperating system: Linux-5.3.0-55-lowlatency-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83.0\nWorked: None known 2.90 alpha has same issue\n\nOffscreen rendering from Python fails if GPUOffscreen buffer is created with any number of of samples > 0. If samples > 0, nothing is drawn (nor is there any error)\n\nRun the small script in the attached .blend (it is the sample script for offscreen rendering from the documentation but with samples>0)\nThe generated image is empty.\n\n(full system info also in .blend in text buffer system-info.txt)\n[MSAA bug.blend](MSAA_bug.blend)\n", "Draw-Manager: Allow independent gizmo redraws\n# Draw-Manager: Allow independent gizmo redraws\n\n## Motivation\n\nCurrently, to redraw a gizmo, we have to redraw the entire viewport. So whenever a gizmo changes highlight state, visiblity state or any other visual state, the entire viewport is redrawn. This may be a very expensive operation that we should definitely try to avoid.\n\nFor the first XR milestone (#71347), we further want to introduce gizmos to viewports that give feedback on the VR session. For example gizmos indicating the position and rotation of the VR camera and the controllers. They would have to be constantly redrawn at a rather high rate to be useful. Redrawing the entire viewport for this takes many resources needed for the VR view rendering.\nThis is such a gizmo, it currently requires redrawing the entire viewport for every frame:\n\n[06_vr_view_gizmo_update.m4v](06_vr_view_gizmo_update.m4v)\n\n## Basic Proposal\n\nIt would be nice if we could just render gizmos into a separate framebuffer and overlay that on top of the viewport, so that both can be updated independently. Integrating the gizmo drawing with the draw-manager passes and compositing would be quite difficult, and brings its own overhead (re-running draw loop, managing passes, compositing, ...).\n\n@Jeroen-Bakker suggested to instead blit the default framebuffer into a separate one before gizmos are drawn. That one can then be kept around and re-used to redraw the gizmos on top, whenever they changed visual state.\nWe'll also need to redraw 2D annotations and region info (cursor, render border, view-axis, FPS text, etc) then, since they draw in-between 3D and 2D gizmos. Doing so isn't that expensive though.\n\nWe may want to have an option to use the old full-redraw behavior over the more performant one, as the latter is heavier on GPU memory.", "Custom Manipulators: General Design & Functionality\nThere are a number of features that should be supported but further design work is needed before they can be implemented properly. Everyone is welcome to join the discussion by proposing more ideas or solutions, by creating mockups or by just giving some own input.\n\n----\n\n# Scope of Widgets\n\n### Description\n\nWhen should a tool use a widget?\n\nExamples:\n\n* Edit Mesh Spin Tool\n* Edit Mesh Smooth tool (number of steps, smooth factor)\n* Edit Mesh Bevel/Inset\n* Edit Mesh UV Rotate\n* Edit Mesh Subdivide\n\nSpin tool is an example where widgets make a lot of sense (you rotate around an axis, so direct manipulation is useful).\n\nThe issue with Smooth & UV-Rotate is that using a 3D manipulator for these is using manipulator simply as a way to access buttons in the view-port.\n\nAn issue with bevel/inset depends on the kind of manipulator used. Having a single manipulator in the view doesn't directly relate to the edge, and again - its more a replacement for accessing buttons in the tool-bar.\n\n### Proposed Solutions\n\nSuggest not to use manipulators if they are simply an alternate access to buttons.\n\nAs for bevel/inset: we could make the bevel edges themselves into manipulators, so you could click on beveled edge and drag it.\n\n----\n\n# Toggling Visibility of Widgets\n\n### Description\n\nCurrently, only the widgets of the active object are drawn. While this works for most cases, being able to precisely control which widgets are visible and which not can be useful.\nFor example, in future, a camera could have widgets for the focal length, sensor size, depth of field distance, ... If all are visible all the time it's easy to accidentally manipulate them.\n\n### Proposed Solutions\n\n* Draw a panel for the active object in which its widgets can be enabled/disabled individually (similar to \"Display\" for cameras).\n* Add a toggle button next to every button represented by a widget (similar to how it's done in the transform panel in the properties region, where you can press the 'lock' icon to disable the widget for this axis)\n\n### Open Topics\n\n* Where would the manipulator toggles be stored? (Object / Viewport / Tool-Settings)\n* How to expose settings that aren't related directly to objects? (Group Center, View-Port Clipping Bounds)\n\n----\n\n# Numerical Input\n\n### Description\n\nIt should be possible for users to input precise values to manipulate a widget (and thus the value it represents). This way they can keep their locus of attention in the viewport, avoiding having to search for a button in the UI.\n\n### Proposed Solutions\n\n* Enabling number input by holding a modifier key while clicking on widget (as in - Ctrl+LMB on widget activates modal mode to input value)\n\n---\n\n# Snap System\n\nUsers may want to snap manipulators to other elements in the scene, eg:\n\n* Snapping the spin center-point to a vertex on a mesh.\n* Snapping bisect angle to a vertex\n* Snapping the camera's DOF to the surface of an object.\n\nNote that currently holding Ctrl sets `WM_MANIPULATOR_TWEAK_SNAP` but each manipulator needs to implement this.\n\n### Proposed Solutions\n\n* Each manipulator has a snap flag for 'TRANSLATE | ROTATE | SCALE', when set, holding Ctrl will snap to any of the elements set.\n* Snapping can also respect scene settings (in the 3D) view-port, so users can snap as with mesh edit-mode.\n\n----\n\n# Key Framing\n\nWhen the cursor is over a manipulator, do we want to support I-Key to keyframe that setting (DOF, lense for eg).\n\n----\n\n# Theme Colors\n\nManipulators now use theme colors, there are basic preset colors to use: (HIGHLIGHT, PRIMARY, SECONDARY, A, B).\n\nWhere A/B are for other controls.\n\n*Currently they're hard coded in manipulators but they can be set however we like.*", "Geometry based lights do not generate shadow on a shadow catcher surface\nOperating system: Windows 10\nGraphics card: RTX 3060\n\nBroken: 3.0.0 and further versions\nWorked: (2.93.10 LTS)\n\nGeometry based lights do not generate shadow on a shadow catcher surface.\n\n- Open attached file\n- Switched to viewport rendering\n[#103795-3.blend](T103795-3.blend)\n\nBlender 2.93 LTS:\n\n\nBlender 3.x:\n" ]

[ "Custom gizmo created with new_custom_shape are difficul to select.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nIt is very difficult to select a gizmo created with new_custom_shape \n\nUsing default scene and the factory setting,\nChange the power of the light to 0, to see the gizmo\nopen and execute the template **gizmo_custom_geometry.py**\nTry to select the gizmo to change the power of the light. Sometimes, it is impossible to select.\n\n\n\n\n", "Inaccurate highlighting of custom gizmos (can't select them properly)\nOperating system: Linux-4.15.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26\n\nBroken: version: 2.80 (sub 74)\n\n**Description of issue**\nThere is a python template called “gizmo_custom_geometry.py” which adds a gizmo with some custom geometry for the energy of lamps. When run, it appers properly along the Z axis of the lamp, and you can select it and move it.\n\nThe problem is that the gizmo is not accurately highlighted when the cursor is over the drawn custom geometry, instead it becomes highlighted when the cursor is over some unclear area in the middle. This makes it hard to select.\nIf I add the “SCALE” option in the GizmoGroup class to disable the viewport scaling, I can zoom into the geometry, making this fact more evident.\n\n\nThis doesn’t happen with other built-in gizmos like “GIZMO_GT_arrow_3d” for any of the available draw types. The geometry always highlights, following the 3D geometry when the cursor is near, even when pointing to an edge.\n\n\nWithout this working properly is almost useless to write custom gizmos with a different drawing, because those can't be selected.\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", "Crash when using OCIO v2\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.0.0 Release Candidate\n\nWhen I used OCIO v2 config file and used Cycles for rendering with Optix, it worked for viewport rendering. But if I pressed F12 for final render, Blender 3.0 crashed when the render was finsihing.\nI tried with a few scenes even if the Blender default scene still crashed. Then I tried rendering with CPU, it still crashed.\nI also tried in Blender 2.93.5. It crashed again even if the render didn't start.\nI downloaded the OCIO v2 config file from ocio_v2_demo.html.\n\nWhen I used OCIO v1.2 config file, Blender worked perfectly.\n\n[test-ocio2.txt](test-ocio2.txt)\n- Set the OCIO environment variable to the location of the test-ocio2.txt config file.\n- Start blender and set Cycles as the render engine\n- F12\n\n-----\nOCIO v2 Config\n{[F12676993](image.png) size=full}\n\nBlender 3.0 crash video\n[Crash.mp4](Crash.mp4)\n", "Cleanup: remove `Scene *` from dupli-list\n`SnapObjectContext` needs a `Scene *` to pass it to the dupli-list, which only needs to pass it to the particle system, which only needs it to obtain the gravity vector.\n\nThe gravity vector should only be read from the evaluated scene, but there are cases where the original scene is passed instead. Since the depsgraph is also passed to the dupli-list (`object_duplilist()`) & simulation code (`ParticleSimulationData`), that can be used to obtain the evaluated scene instead.\n\n- rainyDay\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)", "Crash when scrubbing the timeline when using the line art modifier\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.0\nWorked: 3.4.1\n\nWhen scrubbing the timeline, blender will crash. This happens frequently when I have a project of sufficient complexity that uses the line art modifier. The provided blend file has been simplified as much as possible while still reproducing the crashing behavior.\n\n1. Open line_art_crash.blend\n2. Scrub the timeline. Jumping between frames makes it less likely to crash, but holding onto the playhead and slowly moving should have it crash in a few seconds.\n\n", "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", "Particle Edit mode for non hair particles - 2 Crashes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n\nParticle Edit: 2 Crashes\n\nParticle Edit: 2 Crashes\n\n- Open the blender file and click on the buttons \"Particle select and display point\"\n- Crash 1 (Screenshot)\n\n- Open the blender file and click on the tool \"Weight\" and click into the particles\n- Crash 2 (Screenshot)\n\n- Also had a crash with \"Puff\" \n- file not included\n\n- There are some tools that do nothing while others work\n- User gets no feedback / error message but give no feedback\n\n\n\n[2019-05-19-particle-edit-crash.blend](2019-05-19-particle-edit-crash.blend)\n\n", "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.", "Video Sequence Editor cache not updating for scene strips\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.11\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79\n\n\nNot sure if I'm doing something wrong here, but the Video Sequence Editor is not updating scene strips when changes are made to the scene (like object/camera manipulation).\nWhatever is cached before the change stays in memory. The only way to force the update I've found so far is to change the \"Preview Shading\".\n\nThe expected behavior is that any visual change made to the scene in the scene strip would be updated real-time without changing the Preview Shading every time.\n\nThis isn't the case in 2.79. For the most part, I found scene strips updating when I made changes to the scene. If it won't update for some reason, I'd toggle something that won't affect my scene (like \"Show Grease Pencil\" when I have no GP elements).\nWhile even this wasn't ideal, at least I wasn't forced to change the strip visually to force the update, and it didn't need to be done every time.\n\nIf this isn't a bug but it's a settings issue, maybe the defaults need to be changed to make it work as expected.\n\n1. Add a scene strip to the VSE.\n2. Playback the timeline in VSE.\n3. Do something to change the scene. (e.g. Add a new Cube, move the camera, etc.)\n4. Scrub the timeline in VSE, and you should find that wherever there is cache, the scene doesn't update.\n\n[T66891_VSE_cache_scene.blend](T66891_VSE_cache_scene.blend)", "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", "Select Loop Inner-Region issue\nWin8 64bit | GTX680\n\nBroken: 2.77 509270e\n\nWhen working with face loop, this tool doesn't always work as expected.\n\n\n\n\nNot sure if this can be a bug. Please check.", "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", "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.", "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", "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" ]

[ "scene_to can be NULL and cause segfault\nUbuntu Linux 16.04\n\nBroken: 9da7dfa15\nWorked: 580741b317ae60eb3\n\nDuplicating a sequencer strip causes a segfault\n\n1. Add an adjustment layer effect strip (or a color strip, text strip, whatever strip)\n2. Hit Shift+D\n3. Segfault\n\nThe problem lies in `sequencer.c:5541`. The line used to call `BKE_sequencer_active_set(scene, seqn);`, but since 9da7dfa15 it calls `BKE_sequencer_active_set(scene_to, seqn);`. This is a problem, since `scene_to` can be `NULL` (for example, see the call in `sequencer_add_duplicate_exec(...)`, but there are other places).\n\nSince `scene` is const, and `BKE_sequencer_active_set()` expects a non-const pointer, it's not trivially possible to just pass `scene` instead of `scene_to`. Maybe calling `BKE_sequence_base_dupli_recursive(scene, scene, ...` instead of `(scene, NULL, ...` is enough?\n" ]

[ "Drivers round to 0 when working in um range\nOperating system: Windows 11\nGraphics card: RTX 3090\n\nBroken: 3.0\n\nWhen a driver/scripted expression returns a value in the micrometer range (0.05/1000 for example), it rounds to 0.\nThis is fatal because I need to store a \"clearance\" value and want to control that with drivers, which is simply not possible now. Please enable an even lower range of floats before rounding down to zero.\n\nMake a new project\nSwitch to metric units\nAdd a solidify modifier to a small object\nAdd a driver that calculates or just returns a um value\n- > It rounds down to zero", "Cycles X material preview using 100% of cpu\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\nUsing cycles X, opening the material preview causes my computer to lag and drop in FPS\n\nCreate a new material and open the material preview with cycles x\n\nFor a new scene with default cube and default material, preview render completes in about 5 seconds.\nWith Beckmann glass it's ~10 seconds.\nWith Multiscatter GGX Glass, ~35 seconds.\n\n(Size of preview render: 134x150px)\n", " Elastic deform brush won't work with lower scene unit scale.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.81 (sub 14)\n\n Elastic deform brush won't work with lower scene unit scale.\n\n*Set scene units to Metric, scale to 0.01m\n*Scale the cube by 100 to compensate, apply all transforms\n*Enter sculpt mode\n*Use the elastic transform brush with the options **Grab, Twist or Scale**, the others appear to work", "compositor performance issue when larger empty area surrounding the image\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\nWorked: much faster in 2.93\n\ncompositor performance is severely degraded if there is a larger empty area surrounding the pixels. Also becomes more and more sluggish the longer it plays back, despite it only updating a single image block. Task manager doesn't show any increase in memory usage as it becomes slower.\n\n<video src=\"attachment\" controls></video>\n\nGet an image sequence to playback in the compositor's backdrop, either with a image sequence node, or by updating a single image via python and calling render.render to force the playhead to wait for the compositor to finish calculating. Try playing back with the compositor contracted and expanded. See video for demonstration.\n\nIssue affects the tiled, full frame, and gpu compositor modes. Also happens when experimental compositor is disabled completely in the preferences.\n\nExample video attached.\n\n", "Dimensions reported by Add Primitive Tools do not match actual dimensions.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro P4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.16\n\nBroken: version: 3.0.0 Alpha\nWorked: Never Known to Work\n\nNo matter what physical size the primitive is when created, the redo panel reports that it is 1m or 2m for any dimension. In the example attached  the radius and depth are reported as 39.4\" (1m) and 61.7\" (2m) respectively. While the actual dimensions reported in the N-Panel are 0.221\" x 0.255\" x 0.127\".\n\nCuboids (Cube) are especially erroneous because they can have a different actual value for width, length, and height, but the single dimension \"Size\" is reported as 2m in the redo panel.\n\nIn the base startup file, create a primitive using the tool in the tool panel. Open the redo panel and observe the dimensions reported and compare them to the dimensions reported in the Item Panel.", "Render will not load anything but a cube silhouette in a new untouched file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R4 Graphics ATI Technologies Inc. 4.5.14830 Core Profile Context 21.09.04 27.20.20904.1\n\nBroken: version: 3.6.2\n\nSo, when I open in a new file, new to blender and following a tutorial, I go to render the cube immediately, but instead of a gray cube with shading, it is a transparent silhouette. I have touched nothing, just installed from steam, and opened. Then that, IDK what's going on with it.\n\nIDK what to put here, since I didn't do anything.\n\n\n", "File Browser and Preference Windows open at unusable position/scale.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.8\n\nOn a multi-monitor set up the File Browser and Preferences windows open up on the \"wrong\" monitor and insanely small. They require being resized *every single time* they are opened - does not remember last position or scaling.\n\nScreenshot of both monitors. The main monitor is a 4k and the secondary, on which I regularly run Blender, is a Cintiq 22HD (1080).\n\n\n\n\n\nOn a multi-monitor display, especially one with a 4k as main, open the File Browser and/or Preferences windows.\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.", "problem Blender 4.0 in a mac mini\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 4.0.0 Alpha\n\nI'm trying to get Blender 4.0 (Alpha) running on a Mac Mini running OS Ventura 13.14.1(c). When the cube appears (by default) it is not surrounded by the yellow paint and cannot be selected with the left mouse button or the pointer of the digital tablet either. It can only be selected in the outliner\n\n\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.", "Viewport: Texture limit size generates artifacts during painting\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nWhen limit size is lesser than the actual image size, this will result in artifacts at paint region.\n\n- Open attached file\n- Change Texture limit size to 2k or less (`Edit > Preferences > Viewport > Textures > Limit size`\n- Paint the plane.\n", "Drag data-block into \"Current File\" asset library to create local asset\nIt's not obvious to users how they can create assets. One thing many seem to expect is that they can drag a data-block into the Asset Browser. We can easily support this for the *Current File* repository. For others, we'd have to error out for now.", "Affect origins indicator gizmo is not affected by unit scale\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.2\nWorked: never\n\nThe gizmo used to indicate affect origin feature of transform tool is enabled does not change with different unit scale. This makes the gizmo invisibly tiny when using unit scale of 0.01, which is mandatory for Unreal Engine export capability, as described here: scene_scale.mp4\n\n1. In a new .blend file, set unit scale to 0.01\n2. Create a new cube. Newly created cube should be sized appropriately for new unit scale.\n3. Select new cube, Activate move tool, and activate \"Origins\" Affect Only option.\nResult: The gizmo to indicate Affect Only Origins feature is enabled is invisibly tiny and requires extreme zoom in:\n\nExpected: The Affect Only Origins indicator gizmo scale changes appropriately with different unit scales.\n", "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", "Bone's Custom Properties are invisible in the Bone Properties Editor if bone in hidden layer\nOperating system: Linux 64-bit\nGraphics card: GTX 1080 ti\n\n3.0.0\n\nWhen a bone is selected in the Outliner, but is not on a visible bone layer, its Bone Properties are accessible, but it will not appear to have any Custom Properties.\n\n[BoneBug.blend](BoneBug.blend)\n\n - Open attached file. \n - Select \"Bone B\" in the Outliner.\n - View the properties of Bone B in the Properties Editor. The Custom Properties panel is empty!\n - Go to Armature Properties and enable the hidden layer.\n # Bone B's Custom Property has magically re-emerged.\n\nThis is very misleading!\n" ]

[ "Asset Browser - Thumbnails are not working with big / large Objects\nBroken: version: 3.2.0 Alpha\nWorked: -\n\nHi here ! So with big scale object, the thumbnail of asset browser is not rendered:\n\n\n- Open Blender\n- Create a Cube with size 10000\n- Mark it a Asset \n- look at the thumbnail in Librairy\n\nAs far as i know the thumbnail start to show something with cube of 400 and work perfectly with 300 Cube.\n\n[Tumbnail_Bug.blend](Tumbnail_Bug.blend)\n\n \n\n\n\n" ]

[ "Max brush radius is too small for 4k screens\nThe maximum brush radius (500 pixels) is too small when working on 4K monitors. Possible solutions:\n\n - Increase maximum to 1000. Not a generic solution and could make the radius slider less usable (Krita's radius slider suffers from this).\n - Scale brush radius by DPI. Need to investigate if the existing DPI can be used or if we need a separate one for the 3D viewport.\n", "Wayland: Huge cursor when using a graphics tablet in KDE\nOperating system: Linux-6.0.11-300.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon Pro WX 5100 Graphics (polaris10, LLVM 15.0.0, DRM 3.48, 6.0.11-300.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.2.3\n\nBroken: version: 3.4.0\nWorked: version: 3.3.1 (XWayland)\n\nI'm using KDE Plasma 5.26.4 Wayland on a 4k monitor which is scaled to 200%. Blender 3.4 automatically detected my windowing environment and launched in Wayland mode. Everything appears to be working fine using a mouse, but when I use my Wacom tablet, the mouse cursor doubles in size and looks abnormal.\n\n1. Open Blender in a Wayland session.\n2. Use a graphics pen tablet in any workspace.\n3. The cursor will double in size.\n\n", "Intermittent: Shift + MMB unresponsive or very sluggish\nOperating system: MacOS Ventura 13.4.1\nGraphics card: M1\n\nBroken: 3.5.1, Hash: e1ccd9d4a1d3, Branch: blender-v3.5-release\n\nShift+MMB to pan view in perspective mode becomes either completely unresponsive to keyboard input or extremely sluggish compared to the mouse pointer speed for the rest of the application. Agnostic to mouse pointer speed setting for the OS. \n\nAny model in perspective view. Attempt to pan view via SHIFT+MMB.\n\n", "Multi-touch gesture: Zooming is reverse in shader editor comparing to viewport\nOperating system: macOS-11.4-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 71.6.4\n\nBroken: version: 2.93.1\n\nZooming is reverse in shader editor (other 2d editors are fine)\n\n- Hold ctrl and drag downwards\n- This will zoon in the viewport but zoom out in shader editor\n\n- - -\nsteps from original report:\nOn MacOS, by holding CMD and scrolling on the magic mouse you can zoom on the object. the correct behavior is that dragging down should zoom-in. but it's reverse in the shader editor.\nand if I set the \"Invert zoom direction\" in the settings, it will do both of those oppositly\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", "Inconsistency in the behavior of 'Jump to next/previous keyframe' operator\nOperating system: Linux-5.4.0-124-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.3.0 Beta, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: as far as I know, none.\n\nWhen calling the 'Jump to next/previous keyframe' operator, there are inconsistency of behavior depending whether the active object is a Grease Pencil one or not.\nFor standard keyframes, it jumps to next keyframe if the object is active, regardless of if the object or any of its channels are selected.\nFor grease pencil layers keyframes, it jumps to next keyframe only if the layer channel is selected.\n\nReproduce the bug :\n - Open a new blender file,\n - Add one grease pencil object with two keyframes,\n - Add one 3D mesh (for example) with two keyframes (at different frames than the grease pencil ones),\n - Try to jump to next or previous keyframes, standard shortcut : up/down arrow in the viewport.\n\n[issue_jump_to_next_keyframe.mp4](issue_jump_to_next_keyframe.mp4)\n\n", "GUI: The curser is heavily lagging if GSync is set to windowed and full screen mode\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: Blender 2.79b up to Blender 3.0.0\n\nEverything is as expected if the mode is set to \"Fullscreen only\" (the default)\nBut as soon as you set to it to \"Window- and Fullscreen mode\" the mouse curser will lag heavily.\n\n\n1. Enable GSync\n2. Set it to \"Enable for windowed and full screen mode\"\n3. Save\n4. Open Blender and move the curser\n\n**Workaround** \nJust set it back to full screen mode only.\nOR\nIf you go to nVidia Control Panel > Manage 3d Settings > Program Settings.\n\nAdd Blender under Select Program To Customize. Changing to the following settings can fix it:\n\nMonitor Technology: Fixed Refresh\nPreferred Refresh Rate: Application-controlled\n\n**Desired behavior** \nA fluid curser on the screen even with \"windowed and full screen mode\" enabled", "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)", "Sculpt mode. Switching back to tool with brushes from tool without brushes rolls to next brush.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken 2.83.*, 2.91,\nBroken: version: 2.92.0 Alpha\n\nSculpt mode\nCreate 2 grab brushes 1 and 2, that can be switched with G\nSelect Grab 1\nSwitch to mesh filter.\nPress G.\nNow you switched to Grab2 instead Grab1, that was selected before.\nExpected: return to same brush, that was selected before.\n\nIssue appears with:\nLine project, [Box] mask, Box hide, [Box] faceset, [Box] trim, Mesh/Cloth/Color filters, Mask by color, Edit faceset, all transform tools, annotation.\nAffects all tools, who can have few brushes.\nTested with factory startup too.\n\n[2020-12-10_03-13-39.mp4](2020-12-10_03-13-39.mp4)\n[grabroll.blend](grabroll.blend)", "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", "Grease Pencil vertices selection is offset when Layers/Transform Location as set to a driver\nOperating system: Win10\nGraphics card: RTX3070\n\nBroken: 3.1.0 A\nWorked: N/A\n\n**Short Description of issue**\nMoving a Grease Pencil object's layer via Layers->Transform, by using a Driver, offsets where you have to click to select vertices from that layer.\n\nNOTE: Switching to Draw Mode and drawing a stroke fixes it temporarily, but once you move the controller of the driver again, the problem returns.\n\n**Steps to Reproduce**\n- Open .blend file\n- Select Suzanne and switch to edit mode\n- Try selecting vertices (Does not work)\n- Now attempt to select in circled area\n\n\n\n[#95902.blend](T95902.blend)\nVideo example: iZ_A2wOnAJQ", "GPencil: Define the active scene when using the Video Editing Workspace\nThis is required to have a fast switching method for Storyboarding.", "Vector transform node with constant input difference in Cycles and Eevee\nOperating system: win\nGraphics card: nvidia gtx 790\n\nBroken: 2.80, 009dbc2bc9fb\n\n\nEvee and Cycles have different background rendering. It looks like Cycles has 180 rotation for the backgraund.\n[2_8_setup_1.blend](2_8_setup_1.blend)\n\n[temp1.mp4](temp1.mp4)\n\n\n\n\n- Open a file\n- rotate in the viewport\n- switch to Evee, Cycles, Evee, Cycles.", "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", "Changing \"Disable in Viewports\" of a viewlayer-disabled collection would affect animation playback speed\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.6.1\n\nDisabled objects are affecting animation playback when the armature is placed in a collection.\n\n\n- Download and open \"Buggy_easier.blend\"\n- Play animation, it goes smoothly.\n- Click the \"Disable in Viewports\" button (the little screen button) for \"Collection\" which is disabled in view layer.\n - Animation plays much slower due to evaluation happening in that collection.\n - If instead, you click the little screen button for \"Collection For Extra Cubes (DISABLED)\" (which is also disabled in view layer), playback proceeds normally.\n\n------------\n\nOriginal description:\n\nI have attached two blend files. \n\nNot_Buggy_Blend\nThe objects are parented to the armature. The armature is placed directly in view layer (without any collections).\nAll Cubes use \"auto smooth\" and contain 20k+ polygons.\nThe first Cube is enabled.\nThe other cubes are disabled. These cubes are also shrinked wrapped to the first cube. \nMy animation playback is 60 fps.\n\nBuggy_Blend\nSame setup as in Not_Buggy_Blend. The only difference is that the armature is now placed in a collection, and the disabled cubes are also placed in a collection.\nPlayback is poor.\nMy animation playback is 15 fps.\n\n" ]

[ "Moving objects (G key) has broken behavior on linux/wayland\nFedora 27, GNOME wayland\n\nAny\n\n**Description of error (can't be short, sorry)**\nBlender relies on pointer warping to implement infinite motion on certain features (eg. Moving an object, keyboard shorcut: G). This shows broken behavior on Linux systems running Wayland sessions (with Blender running through Xwayland). The pointer warp request won't be honored under the circumstances Blender does them, as a result the pointer moves outside the viewport and every motion event is interpreted as a full turn around, making the moved object go away really really fast. \n\nXwayland is meant to make X11 clients work seamlessly, this is however a 1% case that may require some compromise.\n\nDue to stricter security principles in Wayland, Xwayland can only \"honor\" X(I)WarpPointer requests whenever the pointer cursor is hidden (like it seems blender already does in other modes like shift-F, which work with Xserver >= 1.19.4), hiding the cursor would likewise make these cases work. Another plausible option is confining the cursor (confineTo argument to XGrabPointer) and obtaining relative pointer motion.\n\nBackground:\nshow_bug.cgi?id=100740\n\nOn a wayland session, move an object past the viewport edge." ]

[ "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", "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", "Unable to flip side with \"Bridge Edge Loops\" operator\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 535.98\n\nBroken: version: 3.6.0 Beta\n\nwhen bridging 2 opposite faces that face away from each other, the bridge inversely connects or chooses the shortest path and there is no way to adjust the smoothness profile to invert the connection to the positive side, the image below shows the difference between blenders bridge tool on the left and Quick Bridge Addon connection on the right, I think this is an important problem as there are no easy way around this to achieve the same result, I hope you can fix it , maybe allow a negative input in smoothness or something, Thank you\n\n\n", "Fillet Curve Node: Merge points with limit radius mode\nWhen \"Limit Radius\" is turned on, the new points often meet in the middle and end up in the same location. This creates curves that are harder to work with in later nodes.\nAs a new option, these points could be merged by the node.\n\nThe point merges should be calculated before `calculate_result_offsets` so the new curves only need to be created/resized once.", "Poor performance for \"Remove duplicate vertices\" for some models\n**System Information** \nOperating system: Windows 10 (but happens on Linux too)\nGraphics card: NVIDIA GeForce GTX 970 (but happens w/ no gfx card too)\n\nBroken: 2.91.0 Beta of 2020-10-26 17:29, hash edf4378c442a (master)\nWorked: unknown\n\n\"Merge vertices\" becomes very slow if glTF object is imported with vertices already merged\n\n\n* Start blender, remove all default objects\n* Import the attached glTF with:\n * Merge Vertices: Turned on\n * Shading: `Smooth Shading`\n* Select Model Group > Mesh Group > Mesh_0\n* Enter Edit mode\n* right-click Merge Vertices > By Distance\n* repeat the above process, but leave Merge Vertices turned off during import\nor\n- Open attached .blend file\n- Go to edit mode on the object named `Mesh_0_slow`\n- right-click Merge Vertices > By Distance\n- Try the same with the object named `Mesh_0_fast`\n\nNote the first time taken: for me it's around 30 sec, which is quite slow\nNote the second time taken for `Merge Vertices > By Distance` is only a second or so\n\nI speculate that this could be because this particular glTF object is reusing some buffers (the 60 meshes are just transformed copies of Mesh_0), so the merge may be doing more work than necessary, but I haven't dug into it.\n\nIn my application, I'm looping over all meshes in the scene and removing duplicate verts, so in my case I'm spending the 30 sec per mesh 60 times for a total of 30 min of processing time! Of course I shouldn't need to do that with Merge Vertices turned on, but I have other imported objects and it's all scripted so it's hard to know which ones to merge vs. not.\n\n[merge_by_distance_bug.blend](merge_by_distance_bug.blend)\n[test-molecule-1.glb](test-molecule-1.glb)\n\n", "UV Loop Select with Double Click and Shift+Double Click to Extend. Need to triple click to Extend + Border Extend problem\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nBroken: 2.93.1\nWorked: probably none of the versions\n\nInconsistent behavior for selecting multiple edge/face loop.\n\nChange keymap values:\nUV Loop Select: `dbl-Left Mouse`\nUV Loop Select (Extend): `Shift dbl-Left Mouse`\nWith custom key for UV Loop Select, selecting with extend become a problem\n\n\n- Load factory settings.\n- Change keymap as suggested\n- Click on UV Edge or Face selection\n- dbl-click selects loop\n- Shift + dbl-click - does not select the loop, need to click 3 or more times\n[UV_Loop_Selecting_Issue.mp4](UV_Loop_Selecting_Issue.mp4)\n\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.", "Weight paint vertex select difficult to see (depends on surface color)\nThis is an issue since 3.2x\n\n**Short description of the issue**\nVertex selection is difficult to see in some cases, depending on the surface color.\n\nChanging the view-port shading \"Color\" can make the unselected vertex color match the selected vertices color.\n\n<video src=\"attachment\" title=\"screenshot.webm\"></video>\n\n**Exact steps for others to reproduce the issue**\n- Open attached .blend file.\n", "Limited dissolve ruins UV\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\nI made 3 or 4 times cycles of \"Limited dissolve - triangulate\" and get ruined UV after 3-rd or 4-th iteration. \nthe goal is to rid of exceeding geometry like on a screen.\n\n\n", "\"Cursor Extrude Vertex\" causes source vertex to snap\nOperating system: Tux-Based\nGraphics card: Intel\n\nBroken: 2.93\n\n\nThe [CTRL}+[RMB] extrude operator (`ops.mesh.dupli_extrude_cursor()`) causes the source vertex to be snapped, in addition to the newly created vertex:\n\n\n\n(GIF.)\n\nSelect a vertex, and do [CTRL}+[RMB] in a situation where there is a valid snap position for it. (I used Surface snap with a surface behind it.)\n\nTest File:\n[#89647.blend](T89647.blend)", "Intersect Selection in edit mode\nOperating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.3.0 Alpha\n\nIntersect existing Selection apply just to what in the viewport frame \nI can t reproduce it with an exact steps\nopen the linked file and select some vertexes with Select Box and with Intersect Mode\nthe intersection apply just to the vertexes shown in the viewport frame \nsame problem in 2.83 - 3.1 - 3.2\n[bug.blend](bug.blend)", "Mirror Modifier On Cage Selection Papercut \nBroken: 2.93.4\nWorked: Maybe never.\n\nWhen in edit mode, using the \"On Cage\" option for the mirror modifier results in some unintuitive behavior when selecting vertices created by the bisect feature. The vertices created by the by the bisection are mapped to the original mesh data in a way that appears to be based on blenders internal representation of the mesh and not based on something observable to the user.\nThe behavior when selecting should feel consistent to the user. To fix this, I suggest that the vertices created by the bisection should always map to the vertices on the original mesh that are on the removed side of the bisection plane. This way users would be able to tweak the centerline of the mirrored mesh in while using \"On Cage.\" As it is currently implemented, there are vertices that affect the mesh that cannot be accessed through normal click selection unless \"On Cage\" is off.\n\n**Example**\n\n\nSelect the +X or -X face of the default cube and scale it by 0.5.\nAdd the mirror modifier and select bisect for the X axis so that the object is mirrored and bisected about the X axis.\nTurn on \"On cage\" for the mirror modifier then enter edit mode for the object.\nWhen selecting the vertices on plane X=0, you should notice that two of the vertices correspond to visible mirrored vertices and two correspond to vertices removed by the modifier. \n\nSimple scene showing the behavior. \n[MirrorSelectOnCagePapercut.blend](MirrorSelectOnCagePapercut.blend)\n", "Wrong UV after Vertex Slide or moving mesh with Correct Face Attributes\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 535.98\n\nBroken: version: 3.5.1\nWorked: unknown\n\nAfter Vertex Slide with \"Correct UV\" checked, or after moving mesh with \"Correct Face Attributes\" UV mapping is wrong. Vertices in UV get split and wrongly offset.\n\n\nExample 1\n1) Open attached Blend file\n[wrong_uv.blend](attachment)\n2) Locate objects plane01_small and plane01_larger. They are identical models with the same UVs. Just one is slightly smaller and one larger and they have different position.\n\n3) Now we will be vertex sliding this vertex to the diagonal one with snapping on vertex on (see picture) with \"Correct UV\" checked. See that the larger model has UV correct, but the smaller one has wrong UV after the vertex slide\n\n4) now go back (Undo) and lets try grab/move with snapping instead of vertex slide. Be sure to have checked ON \"Correct Face Attributes\" and \"Keep Connected\" in Tool Settings/Option - see picture. Now UVs are wrong in both cases\n\n\nExample 2:\n1) Lets look at plane02_01 and plane02_02. They are totally identical duplicated objects (not instances) just with different position.\n\n2) Vertex slide works OK in both cases here, so lets try Grab/move with vertex snapping and \"Correct Face Attributes\" + \"Keep Connected\" ON again. Here result UVs are OK in case of plane01_02 but wrong in case of plane01_01\n\n\n", "Mesh Optimization Project Progress\n### Committed\n\n- 2b640622ff\n- aa6f0f3d1f\n- deb71cef38\n- 5f749a03ca\n- 44d2479dc3\n- c2fa36999f\n- 496045fc30\n- e4c6da29b2\n- d8b8b4d7e2\n- bcefce33f2\n- 8a1860bd9a\n- 6bef255904\n- 174ed69c1b\n- b3f0dc2907\n- 513f566b40\n- 2d60c496a2\n- 27da305a40\n- 51568030e9\n- b5542c1ea4\n- 2d4ec90497\n- 4f9ef65dac\n- 04313f1bb5\n- 0f201049b4\n- f9c9e000ca\n- 1b4d5c7a35\n- 25c2875e0f (depending on 8839b4c32a)\n- 178086d581\n- 4ba06ad0a8\n- 39b2a7bb7e\n- 399b6ec76c\n\n### Differentials\n\n*Remove once committed.*\n\n- [D11294: DrawManager: Use threading for ibo.fdots_nor/hq](D11294)\n- [D11969: Depsgraph: Implement 'ID_RECALC_GEOMETRY_DEFORM' - Second solution](D11969)\n", "Wrong interaction by extrude region with 2 cube's faces\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.22\n\nBroken: version: 3.1.0\n\nWhen extrude the \"z\" and \"-x\" faces of cube they extrude up \n\n* Create a cube\n* Choose edit mode\n* Select \"z\" face(top of cube) and \"-x\" face\n* Use Extrude Region or press E\n\n{[F12930516](image.png), size=full}\n\nThanks!" ]

[ "UV Editor does not treat edge seams as island delimiters\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.0.1\n\nWhen overlapping mirrored islands, if they have a common edge as a seam they will get merged into a single island\nAlso when exporting those overlapped islands, they open the same way (merged) in other software too (tested in Maya 2022)\n\nWill add a photo guide on how to reproduce\n\n\n\n[MirrorBug_Example.blend](MirrorBug_Example.blend)\n\n" ]

[ "Mirror modifier with mirror object updates slowly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.83 (sub 15)\nWorked: Never (2.79+)\n\nAdding a Mirror Modifier and using an empty or another object to mirror across, causes slow viewport performance.\n\n[#76102.blend](T76102.blend)\n\n- Open file\n- Move Suzanne - Notice performance\n- Remove Mirror Object from mirror modifier\n- Move Suzanne - Performance much better\n\nYou can apply subdiv modifier, it shouldn't have an effect.", "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", "Viewport render still cannot render \"non-antialiased\" Outline overlay.\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nHi, I'm trying to get a non anti-aliased image out of the viewport render option, but the final image is still anti-aliased.\n\n\n\nUsing these settings in the preferences:\n\n\n\n\n", "Metal backend: View Port drawing issue with face orientation\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API Intel(R) Iris(TM) Plus Graphics 1.2\n\nBroken: version: 3.5.1, 3.6-beta, 4.0\nWorked: with OpenGL backend\n\nWhen enabling \"face orientation\" in the view port the display does not update until I rotate the model. When rotating the model the face orientation colour overlay display is broken.\n\nSee attached screen movie showing the issue.\n\nTo reproduce:\n1. start with a new default scene\n2. enable face orientation overlay from view port overlays menu\n3. rotate the cube\n\nThis was observed using the default startup cube.\n\n", "Video Sequence Editor cache not updating for scene strips\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.11\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79\n\n\nNot sure if I'm doing something wrong here, but the Video Sequence Editor is not updating scene strips when changes are made to the scene (like object/camera manipulation).\nWhatever is cached before the change stays in memory. The only way to force the update I've found so far is to change the \"Preview Shading\".\n\nThe expected behavior is that any visual change made to the scene in the scene strip would be updated real-time without changing the Preview Shading every time.\n\nThis isn't the case in 2.79. For the most part, I found scene strips updating when I made changes to the scene. If it won't update for some reason, I'd toggle something that won't affect my scene (like \"Show Grease Pencil\" when I have no GP elements).\nWhile even this wasn't ideal, at least I wasn't forced to change the strip visually to force the update, and it didn't need to be done every time.\n\nIf this isn't a bug but it's a settings issue, maybe the defaults need to be changed to make it work as expected.\n\n1. Add a scene strip to the VSE.\n2. Playback the timeline in VSE.\n3. Do something to change the scene. (e.g. Add a new Cube, move the camera, etc.)\n4. Scrub the timeline in VSE, and you should find that wherever there is cache, the scene doesn't update.\n\n[T66891_VSE_cache_scene.blend](T66891_VSE_cache_scene.blend)", "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)", "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.", "Viewport header menu, late/wrong responce to hover and click\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\n\n\nSometimes menu stucks when mouse pointer already over another menu.\n[2021-11-12_14-21-18.mp4](2021-11-12_14-21-18.mp4)", "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.", "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", "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", "Blender 3.5 Image editor does not fully refresh on some zoom levels while painting\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.1\nWorked: 3.3.2\n\nBlender 3.5 Image editor does not fully refresh on some zoom levels while painting\n\n\n- Open attached file\n- Scribble on the top left image editor\n- On 3.4.1, 3.5.0 and 3.5.1, the image editor being painted doesn't seem to update the view fully, both only below that uv seam line, and 3.5.0 had more portions that aren't updated compared to 3.5.1.\n- Zoom in/out, it refreshes back to normal.\n\nNote:\n\n- This only happens on some particular zoom levels, sometimes I can get a lower zoom level to produce this error too, by zooming in and out and draw, you could probably find some more zoom levels where the image update region isn't complete.\n- When you zoomed out to some level and it works, and then you could zoom to some other level it could fail again.\n\n| 3.3.2 (correct) | 3.4.1 | 3.5.0 | 3.5.1 |\n|--|--|--|--|\n|  |  |  |  |\n\n------\n\nOriginal description:\n\nWhen zoomed in at a particular level the real time properties of the image editor stop working, In the short video i sent I am painting a texture using the Image editor window, it updates the texture on the model and the UV editor below, but the image editor window doesnt update until I either zoom in or zoom out, At first I thought it was random but then I found it can be easily replicated by simply being zoomed in at the level that I was when the bug was happening.\n", "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", "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", "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)" ]

[ "Changing viewport studio lighting not working\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.92.0 Beta\n\nChanging viewport studio lighting not working, but works when you change 3d viewport.\n\n\n[C4YIiwtOTt.mp4](C4YIiwtOTt.mp4)\n1. Click viewport shading;\n2. switch studio lighting to others;\n3. no change in 3d viewport;\n4. rotate 3d viewport, and you will find it change.\n\n\n", "Shading changes in the viewport shading popup menu require movement in the 3D viewport to take affect.\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\nBisect points to 0f95f51361 being the responsible commit.\nWorked: 2cd091e9c7 and earlier.\n\nChanges in the viewport shading only updates after I zoomed, panned, rotated in the 3d viewport.\nFor example turning on Cavity, or switching to MatCap etc. EEVEE's AOV passes are affected as well.\n\nChange setting in viewport shading such as turn on MatCap\nRotate pan zoom in 3d view port\nNow you can see the change", "Viewport Shading Menu changes do not take immediate effect\nOperating system: Darwin-20.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 555X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.13\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92\n\nChanges to any options in the Shading Menu in the 3D Viewport do not take effect until a change is made in the viewport.\n\nHere is a simple set of steps to repeat the issue:\n- Open up a new default scene\n- In the 3D Viewport Shading Menu select 'Matcap' and choose any matcap of your choice\n- Observe that the default cube is still displayed with the old shading\n- Use the middle mouse button to rotate the view slightly\n# Observe that the new matcap takes effect as soon as you rotate the view\n\nBasically nothing from the Shading Menu takes effect until there is an interactive change in the viewport. Even interactive sliders like cavity ridge and valley don't take effect immediately.", "blender does not update rendering mode correctly\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14757 Core Profile Context 20.12.1 27.20.14501.28009\n\nBroken: version: 2.92.0 Beta\nWorked: 2.91\nwhen changing shading mode from lookdev to rendered the shading does not update, also changing viewport shading is not updating correctly too\n\n\nfrom any file, just play with the settings. the shading only updates once you move the camera in the viewport which is pretty annoying.\n\n[2021-01-21 16-48-15.mp4](2021-01-21_16-48-15.mp4)\n\nsorry if it is a duplicate.\n\n", "Viewport refresh\nOperating system: Linux-5.8.0-40-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: AMD RAVEN (DRM 3.38.0, 5.8.0-40-generic, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92\n\nWhen a visual viewport setting is changed it only updates changes after moving the view.\n\nin the viewport shading popover change colors to random, then move the view to see changes.\nI can confirm this happens also with background images in lookdev, matcaps, and flat shading.\n\n{[F9591113](ViewportShading-lookdev.mp4), layout=left, float, size=full, alt=\"a duckling\"}\n", "Toggling between Material Preview and Rendered mode does not refresh the 3D viewport\nOperating system: Linux-5.10.2-2-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: \n- 2.93.0 Alpha\n- 2.92.0 Beta\nWorked: version \n- 2.92.0 Alpha\n- 2.91.0\n\nWhile trying to toggle between Material Preview and Rendered mode, the view will not update and only display as if Material Preview was selected. Clicking any other option or doing any action in the viewport (like holding the middle mouse to rotate the view) will trigger a refresh, however, multiple clicks between both modes will not trigger it. This behavior only happens on EEVEE, Cycles works as expected.\n\nOn a new file, make sure EEVEE is selected as render engine; click on Material Preview, then click on Rendered, the viewport (if its replicable) should not refresh, and can be seen that toggling between those two options makes no difference, as the view will remain in Material Preview. Changing back to another mode, or interacting with the viewport will trigger a refresh.\nThis mainly happens when toggling from Material Preview to Rendered, Rendered to Material Preview updates as expected (The first time); however, if the viewport is already stuck on Material Preview, Rendered mode will not update when toggling back.\n\n", "viewport rendered shading sometimes not working\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.92.0 Beta\n\nRendered shading sometimes now activating.\n\nWhen switching from Material Preview to Rendered shading in the viewport, the viewport stays in Material Preview mode. Selecting Solid then selecting Rendered fixes this. \nThanks!\n\n", "Changes to the solid (workbench) viewport mode are failing to refresh automatically\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\n\n1. Open Viewport Shading menu\n2. Select any Matcap in Lighting\n3. Perform any action with the viewport (Move, Zoom)\n\nThis problem is present in Blender 2.92 beta!\n\n", "3d viewport is not updated immediately after changing the settings\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\n\nAfter changing the settings (for example, changing matcap), you need to move the viewport for the settings to apply\n\n1 - change matcap\nnothing changes\n2 - move viewport\nnew matcap applied\n\n", "Viewport settings update only after navigation\nOperating system: Linux-5.4.0-62-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.93.0 Alpha\nBroken: version 2.92.0 Beta\nWorked: 2.91.2\nWhen changing viewport settings in she shading option like the lighting method, matcap, cavity, etc, the viewport only updates once it gets navigated a bit.\n\n[2021-01-27 12-59-43.mp4](2021-01-27_12-59-43.mp4)\n\n\n\n", "viewport shading options not taking effect until clicking in viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.93.0 Alpha\nWorked: not sure, but I think it worked a month ago or so with 2.93 daily\n\n**Short description of error** and while in viewport looking at cube\nI select viewport shading> solid,\nthen I go to the viewport shading dropdown menu> viewport shading> lighting> studio (or matcap),\nwhen I select one of the options there, studio and matcap changes do not take effect until I click in the viewport,\nat which point the changes do take effect,\nwhereas in recent previous Blender versions I think I could just click on one of the lighting setup orbs\nand see the resulting changes in the viewport, without having to exit the lighting orb options and go into\nthe viewport\nI liked being able to just click on an orb and see the changes in the viewport, immediately, trying various orb options until I see a result I like, rather than having to click in the viewport to see a new result, because then I have to navigate back to through shading menu again in order to try various options there, not a problem unless I want to keep trying lots of various options, but if I do want to try lots of various options it's a lot of extra menu navigation, thanks for checking this, maybe its something on my end\n[Blender_2.93_1-20-21_bug_report_viewport_shading_studio_and_matcap_changes_not_working_until_clicking_in_viewport_1_1.blend](Blender_2.93_1-20-21_bug_report_viewport_shading_studio_and_matcap_changes_not_working_until_clicking_in_viewport_1_1.blend)\n\n" ]

[ "Batch Rendering Crashes if EEVEE set in scene\nOperating system: Windows 10\nGraphics card: Any or None\n\n2,83, 2,90, 2.92\n\nEEVEE is set as renderer in the scene file.\nThe scene is send to the render farm. \nOpenGL is not available as render farm is running as background service OR blades machines do not have any GPU at all.\nBlender in Commandline Crashes.\n\n(Side Note: Cycles works fine as CUDA is available within background service)\n\n\n**Expected Behavior**\nReport an error \"EEVEE requires OpenGL. Unable to find/initialize openGL32.dll\"\n\nTo reproduce the issue, you either need some helper service that starts Blender in commandline mode (I can provide one) OR you can use any machine that does not have a GPU installed.\nCreate a new scene with EEVEE as renderer.\nTry to commandline-render the scene.\n\nCommandline that we used:\n\"C:\\renderer_exe\\blender\\win_x64\\Blender_2.90\\blender.exe\" -b \"\\\\isilonai\\woodspeople\\Boar (With fur).blend\" -o \"\\\\isilonai\\woodspeople\\Boar (With fur)\\Brawler####\" -F PNG -x 1 -s 10 -e 10 -j 1 -t 24 -a -y\n\n\nCommandline output:\nR 6| >\"C:\\RR_localdata\\renderer_exe\\blender\\win_x64\\Blender_2.92\\blender.exe\" -b \"C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\" -o \"C:\\RR_localdata\\renderout\\A\\3D\\Blender\\render\\myOut####\" -F PNG -x 1 -s 2 -e 3 -j 1 -t 24 -a -y \nR 7| Blender 2.92.0 Alpha (hash 719bea0d6d06 built 2021-01-12 23:10:47)\nR 8| Read blend: C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\nR 9| Writing: C:\\RR_localdata\\temp\\A\\cube.crash.txt\nR 10| StdErr: Warning! Using result of ChoosePixelFormat.\nR 11| StdErr: Warning! Using result of ChoosePixelFormat.\nR 12| StdErr: Warning! Using result of ChoosePixelFormat.\nR 13| StdErr: Warning! Using result of ChoosePixelFormat.\nR 14| StdErr: Warning! Using result of ChoosePixelFormat.\nR 15| StdErr: Warning! Using result of ChoosePixelFormat.\nR 16| StdErr: Warning! Using result of ChoosePixelFormat.\nR 17| StdErr: Warning! Using result of ChoosePixelFormat.\nR 18| StdErr: Warning! Using result of ChoosePixelFormat.\nR 19| StdErr: Warning! Using result of ChoosePixelFormat.\nR 20| StdErr: Warning! Using result of ChoosePixelFormat.\nR 21| StdErr: Warning! Using result of ChoosePixelFormat.\nR 22| StdErr: Warning! Using result of ChoosePixelFormat.\nR 23| StdErr: Warning! Using result of ChoosePixelFormat.\nR 24| StdErr: Win32 Error# (127): The specified procedure could not be found.\nR 25| StdErr: Error : EXCEPTION_ACCESS_VIOLATION\nR 26| StdErr: Address : 0x00007FFF8DBA1C81\nR 27| StdErr: Module : VCRUNTIME140.dll\nR 28| StdErr: Thread : 00001c94\n[Boar.crash.txt](Boar.crash.txt)\n\n\n", "Crash on Mac when starting with `--debug-gpu` flag\nOperating system: Mac OS Ventura 13.1\nGraphics card: Apple M1 Max\n[system-info.txt](system-info.txt)\n\nBroken: 3.4.1\nWorked: 3.3.2\n\nBlender won't start on a Mac when starting with `--debug-gpu` flag.\nThe terminal output is this:\n\n```\n/Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\nRead prefs: /Users/vollstock/Library/Application Support/Blender/3.4/config/userpref.blend\nWARN (gpu.debug): source/blender/gpu/opengl/gl_debug.cc:165 init_gl_callbacks: Failed to hook OpenGL debug callback. Use fallback debug layer.\nzsh: segmentation fault /Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\n```\n\n\nStart with the flag\n\n```\n/Applications/Blender.app/Contents/MacOS/Blender --debug-gpu\n```", "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", "Mem leak when rendering on GPU\nOperating system: Windows 10 20H2 Build 19042.985\nGraphics card: Gigabyte RTX 30870\n\nBroken: 2.92 - 3.0\n\n\nRender 2.92 splash screen on GPU 60337d495677e942564cce76\n\nOn CPU, memory usage was 18GB, on GPU it went to 60GB and I had to terminate the process.", "Fill limited and unuspported GPUs list\nAfter [D5955: GPU: Platform Support Level](D5955) we have a mechanism to show one-time warnings for some GPUs on startup.\n\nHowever we still need to fill in this list. #61936 (EOL GPU problems tracking report) provides a starting point, along with other reported bugs. It may be most reliable to test for the driver version when possible, since often the bugs are in the driver, and old cards don't work with new drivers.\n\nWe will need to parse the driver version which can get tricky, need to look at a lot of OpenGL strings to figure out the patterns.\n\n- [x] Intel Windows\n- [x] Intel Linux (no known issues with OpenGL 3.3 drivers I believe)\n- [ ] AMD Windows\n**Latest GCN 1st gen drivers: 19.Q3.1 (pro), Adrenalin 2019 Edition 19.9.3** Latest Terascale 3 drivers: 15.201.2401.1010 (pro), 16.2.1, 15.7.1\n** Warn for driver version 16 and older. Or 18 and older?\n- [ ] AMD Linux\n** No obvious way to distinguish between Terascale and GCN. Maybe just don't warn as drivers are still being maintained for both.\n- [ ] NVIDIA: official driver\n**Latest driver for GTX 2xx: 342.01** Latest driver for NVIDIA Quadro Tesla: R340 U14 (342.00)\n** Warn for 341 and lower.\n- [ ] NVIDIA: nouveau driver unsupported\n** Always warn.\n- [ ] macOS\n** Test if operating system is 10.12 or newer.", "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", "Wintab rarely gets into a bad state and prevents Blender startup\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked:\n\nFor a few months now, I have been getting a fairly rare, but reoccurring issue (maybe once a week on average) where Wintab gets into some erroneous state and prevents Blender from starting if the Tablet API setting of the Input preferences is set to `Wintab` or `Automatic`.\nWhen Wintab gets into this erroneous state and Blender is already open, Blender will crash if I attempt to open the User Preferences. I'm not sure what else might cause a crash when Blender is already open.\n\nBy adding extra logging to a custom build of Blender, I've determined that the crash when starting Blender occurs when calling the `open` (`WTOpenA`) function: GHOST_Wintab.cc#L85\n\nMy drawing tablet's software also reports an exception in `WTOpen`, the value of which appears to equal 0xC0000005 which I think indicates a `STATUS_ACCESS_VIOLATION` according to 596a1078-e883-4972-9bbc-49e60bebca55.\n\n\nIn the drawing tablet's software, this exception only occurs if I actually connect the tablet to my PC, whereas Blender crashes even when the tablet is not connected.\n\nCurrently, if I don't actually need my tablet, I'm working around the issue by starting Blender headless, changing the Tablet API setting to Windows Ink, and then starting Blender normally.\n\nI have already tried updating the drivers for my tablet to the newest version and it made no difference.\n\nIf I start Blender with `--debug-wintab`, all that's printed is:\n```\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release> .\\blender.exe --debug-wintab\nRead prefs: \"C:\\Users\\Thomas\\AppData\\Roaming\\Blender Foundation\\Blender\\4.0\\config\\userpref.blend\"\nLoading Wintab for window 00000000000910C4\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release>\n```\n\nEvery version of Blender I've tried between 2.79 and 4.0.0a crashes unless I have the Tablet API set to `Windows Ink`.\n\nI don't know the specifics of how Wintab is handled, but could it be possible to either catch the exception in `WTOpen` and allow Blender to continue loading, or to check for a connected tablet before attempting to call `WTOpen`, similar to what my tablet's software appears to be doing?\n\nUnfortunately, Wintab getting into this erroneous state where it crashes in `WTOpen` occurs too rarely for me to figure out how to reproduce it and I'm not even sure if it's Blender that is causing it to get into this state in the first place.\n\n", "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.", "Blender segfault if Bake Line Art\nOperating system: Debian Linux Stable 11\nGraphics card: Intel internal UHD Graphics 630 (driver: i915)\n\nBroken: 3.2.2 - 3.6.1 official releases\n\nBlender segfault if Bake Line Art.\n\nConsole:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault\n```\n\nFile /tmp/blender.crash.txt:\n```\n# Blender 3.2.2, Commit date: 2022-08-02 18:15, Hash bcfdb14560e7\nbpy.ops.object.delete(use_global=False, confirm=False) # Operator\nDeleted 1 object(s) # Info\nbpy.ops.object.gpencil_add(align='WORLD', location=(0, 0, 0), scale=(1, 1, 1), type='MONKEY') # Operator\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.gpencil_modifier_add(type='GP_LINEART') # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xc1619d0]\n./blender() [0x11da18d]\n/lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f97f7664d60]\n./blender(MEM_lockfree_allocN_len+0x7) [0xc16e1e7]\n./blender(MEM_lockfree_dupallocN+0x14) [0xc16e624]\n./blender(BKE_gpencil_stroke_duplicate+0x1a) [0x11f926a]\n./blender(BKE_gpencil_frame_copy_strokes+0x42) [0x11f94c2]\n./blender() [0x1207d97]\n./blender(BKE_gpencil_prepare_eval_data+0x1b7) [0x1208b07]\n./blender(BKE_object_handle_data_update+0x2fe) [0x12af9ae]\n./blender(BKE_object_eval_uber_data+0x2f) [0x12afc7f]\n./blender() [0x1913f22]\n./blender() [0x19140f2]\n./blender() [0xc16574d]\n./blender() [0x1796a35]\n./blender() [0x1796ceb]\n./blender() [0x1783d27]\n./blender() [0x1790720]\n./blender() [0x179275c]\n./blender() [0x1792959]\n/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f97f807aea7]\n/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f97f7727a2f]\n\n# Python backtrace\n```\n\n1. Open Blender\n2. Click to default box and delete it (press del)\n3. Press Shift+A\n4. Select \"Grease Pencil\" - \"Monkey\"\n5. At right area select \"Modifier Properties\"\n6. Click \"Add Modifier\"\n7. Select \"Line Art\"\n8. At bottom of this area click \"Bake\" - \"Bake Line Art\"\n9. Segfault here\n\n", "Crash 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)", "Subdivision Surface: Out of memory exception in in post 2.79 versions\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\nWorked: (2.79)\n\nWhen rendering a displacement heavy blend file, We consistently get out of memory exception in blender 2.8x and 2.9.\n\n - Open the attached blend file.\n - Click F12 (Render Image).\n # Wait till it crashes (approximately 6min).\n\nMore info about this blend file:\n```\nResolution: 650px by 650px\nCycles: 10\nAll polygons are triangles.\nOne material with a displacement map on all objects.\nSubdivision modifier with Catmull Clark with 1.0 adaptive value, on all 3 objects.\nSimplify->Render->Maximum Subdivion is equal to 2.\nSimplify->Render->Texture Limit is equal to 8192.\nSimplify->Viewport->Maximum Subdivion is equal to 0.\n```\n\n[Bug-Upload(2.79).blend](Bug-Upload_2.79_.blend)", "MacOS: Eevee render crashes with GPU hang occurred\nLaptop: 2019 Macbook Pro 16\" \nOperating system: Mac OS Big Sur 11.1\nGraphics card: AMD Radeon Pro 5300M / Intel UHD Graphics 630 1536 MB\nProcessor: 2.6 GHz 6-Core Intel Core i7\nMemory: 16 GB 2667 MHz DDR4\n\nBroken: \n2.91.0 and 2.91.1 \n\nRender engine: eevee \nBlender crashes in rendered view or after hitting F12 (Render Image)\n> GPU hang occurred, msgtracer returned -1\n\n\nlast step taken in this file before crashing:\nMath node > function power > right side render tab > render: 64 *sample: 256* distribution: 1000\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n- \"Render image\" with render engine Eevee.\n[nebula.blend](nebula.blend)\n\nI'm completely new to blender, so I hope I wrote this down correctly! \n\n\n- adding crash report file \n[crashreport.docx](crashreport.docx)\n", "\"Repeat History\" unavailable after \"Undo\"\nCurrently undo clears the operator history,\nideally this should instead keep these actions in sync with the undo history.\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "(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" ]

[ " CPU render + OptiX denoiser leaves empty tiles unprocessed (Blender from Master)\nOperating system: Linux-5.4.0-14-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nCPU: i7 3770\n\nBroken: version: \n- 2.92.0 Beta\n- 2.92.0 Alpha\nWorked:\n- 2.92.0 Alpha (for @rjg) \n- 2.91.0\n\nWhen I render in Cycles with Sampling> Denoising> Render> Optix, strange things happen. The resulting render is left with empty tiles / holes and if you cancel (Esc) the render job you get the following error message:\n\n```\nCUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:816)\n```\n\n[CPU_OptiX denoiser problem.blend](CPU_OptiX_denoiser_problem.blend)\n\n\nDepending on the scene there may be more than one empty tile.\n\nProbably related to this fix?:\nT83925#1087610" ]

[ "Simulation Nodes Reset Behavior\nCurrently, the simulation range for geometry nodes is the scene range. So whenever the cache becomes invalid and we go back to frame 1 (or whatever the scene range start is), the cache is reset. \n\nNow, we want to add support for giving individual simulations separate frame ranges. Those might not match the scene range anymore. The simulation start might be before the scene start frame to support preroll (potentially even at a negative frame). Therefore, using the scene start frame as the reset point, does not make sense anymore.\n\nThe new behavior should/could work like this:\n* Invalidated simulations reset whenever the current frame is at or before the simulation start frame.\n* There is a new \"Play with Preroll\" button in the timeline that starts playback at the first simulation start frame in the scene. \n * Since this frame is at or before all simulation start frames, all invalidated simulations are reset.\n\nOpen Questions:\n * Are all or only invalidated simulations taken into account when determining the first frame for the \"Play with Preroll\" operator.\n * Where to put the new \"Play with Preroll\" button exactly, what should it be called and what should it look like?\n\n", "Circle select tool low performance\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\nWorked: (3.6)\n\n\nCircle select in edit mode on Blender 4.0 is not snappy as Blender 3.6.\nwhen I click and drag with circle select on vertices or edges or faces it's kinda laggy. on Blender 3.6 I get around 90 fps while selecting with circle select tool but in Blender 4.0 it's around 30fps.\n\n1- create a UV Sphere \n2- add subdivision surface level 2 and apply it (this step is just for better visualization not necessary)\n3- click on UV Sphere and enter edit mode\n4- select 'circle select' tool and click and drag on elements (like vertices)\n5- compare performance to Blender 3.6\n\n", "Edit-Mesh \"Select Next Active\" doesn't handle a wire edge loop (vertex mode)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nIt works with loop ,that surrounden by others, but can`t deal with single circle, when I am trying to select one per one.\nPlease watch video:\n[2020-01-17_19-06-34.mp4](2020-01-17_19-06-34.mp4)\n\n[untitled.blend](untitled.blend)", "if multiple splines on the same place... no selection is visable\nOperating system: Linuxmint 19.0\nGraphics card:Geforce GTX1050\n\nBlender Version\n81ea815dcb6, blender2.8, 2018-12-12\n\nI created a spline for modelling.\nThen I converted the spline into a mesh.\n\nI want to delete some vertices, but I could not select any.\nBy clicking an moving I saw there is 1 vertice selected.\n\nBut any other selection is blind.\n\nBy the way: I don't even know how these >10 splines were created...\nsuddenly they where there...\n\n\n[Bug-Multiple Objects.blend](Bug-Multiple_Objects.blend)\n", "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", "Make Thumbnail Dragging More Reliable\nOn some systems, the dragging is very glitchy and keeps invoking box selection instead.", "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?", "Cannot paginate shape key list\nSteps to reproduce:\n* add any mesh (e.g. a cube)\n* in Object Data Properties > Shape Keys click '+' twenty times\n* clicking above or below the scroll bar does not paginate the list\n\nBroken: 3.5 alpha, 50c7eb14f455, master, 2022-12-19\n", "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)", "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", "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.", "Double click is recognized even when the first click is consumed to close a menu\nOperating system: Windows 10\n\nBroken: 2.80 release, 2.81 5e5cf9ea9f7\nWorked: (optional)\n\nWhen clicking on a workspace name to close the splash screen, the second click gets treated as double click if it occurs fast enough. As a result instead of switching to the workspace, the workspace name switches into text edit mode.\n\nIt happens with other menus too, with wheel menus even when the first click is selecting an option at same time.\n\nObject names in the outliner do switch into text edit mode too.\n\n - Open Blender or make splash screen visible.\n - Double click on the name of a worskpace or object\n\nResult: Workspace (or object) name is in edit mode.\n\n**Or**\n\n - Move the default cube away from the 3D cursor\n - Shift + S to open Snap menu (wheel)\n # Double click on a workspace name while \"Selection to Cursor\" is highlighted\n\nResult: Selection moved to cursor and workspace name is in edit mode.", "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", "Pick Shortest path interferes with Ring select - Regression\nWindows 10\nNvidia GTX 1070\n\nBroken: Blender 3.0, 2.93LTS\nWorked: Blender 2.92.0\n\n In Blender 3.0 shortest path selection interferes with ring selection on my custom keymap where both operators share the same button layout, the difference being a single and double mouse click respectively. When selecting two edge rings, shortest path interferes and adds additional edges to connect the two edges from which a ring selection is produced. Instead, I expect it to only perform two ring selections.\n\n1. Map \"mesh.shortest_path_pick\" to Shift + LMB click\n2. Map \"mesh.edgering_select\" to Shift + LMB double click\n3. Create a cube or monkey\n4. Perform two edge ring selections that do not touch each other, preferably one or two edges apart from each other.\n5. Notice the additional edges selected in between the edges used to pick the ring selection with. \n\n[Bugreport - Shortest path & edgering selection.mp4](Bugreport_-_Shortest_path___edgering_selection.mp4)\nI also confirmed this on a factory reset 3.0.", "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" ]

[ "Select/Deselect All broken\nOperating system: Linux Mint 64-bit\nGraphics card: GeForce 840M\n\nBroken: Blender 2.8 Beta 8c620c8e2b3\nWorked: Blender 2.79b\n\nThe hotkey for selecting and deselecting all (A by default) does not respond at times. Often it does work, but sometimes it fails to respond to up to about ten keystrokes in a row.\n\nPress 'A' repeatedly at different intervals in a 3D Viewport. If the error does not occur, try rotating the camera a bit." ]

[ "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", "Add rotation offset in array modifier\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nIt would be really helpful to have the possibility to use a rotation offset in the array modifier. It is already possible to set this up, with a separate object as rotation offset, but it is time consuming to set up and requires the user to convert from degrees to radians in case the user want to set up a driver for rotation based on the \"count\" property in the array modifier. Duplicating geometry with the array modifier like this is useful if you intend to deform it with a lattice or welding vertices for example. \n\nThe goal is to have a very simple implementation. If complex rotation and translation is needed, using a separate object as offset is a better approach\n\nSee video below for what I'm trying to achieve\n\n[rotation offset.mp4](rotation_offset.mp4)\n\n---\nMockup for additional modifier panel.\nPossibly it could be a \"Factor slider\" per axis instead. \nIf \"X Factor\" == 0.5, the max spin in the X axis would only be 180 degrees\nf \"X Factor\" == 1, the max spin in the X axis would be 360 degrees\n\n\n\n\n\n", "different Skin Modifier outputs for same mesh\nWindows 10\nNvidia Quadro 600\n\nBroken: 1422f0d\n\nThe skin modifier produces different meshes on the default cube.\n\n\nTrigger the skin modifier to update by doing the same thing I do in the .gif\n\n[skin_modifier_bug.blend](skin_modifier_bug.blend)\n\nNote: this only seems to happen when the edges are orthogonal. When I move one point, the problem doesn't appear on this and connected points.\n\n(Originially reported here: 576)\n", "Mirror Modifier On Cage Selection Papercut \nBroken: 2.93.4\nWorked: Maybe never.\n\nWhen in edit mode, using the \"On Cage\" option for the mirror modifier results in some unintuitive behavior when selecting vertices created by the bisect feature. The vertices created by the by the bisection are mapped to the original mesh data in a way that appears to be based on blenders internal representation of the mesh and not based on something observable to the user.\nThe behavior when selecting should feel consistent to the user. To fix this, I suggest that the vertices created by the bisection should always map to the vertices on the original mesh that are on the removed side of the bisection plane. This way users would be able to tweak the centerline of the mirrored mesh in while using \"On Cage.\" As it is currently implemented, there are vertices that affect the mesh that cannot be accessed through normal click selection unless \"On Cage\" is off.\n\n**Example**\n\n\nSelect the +X or -X face of the default cube and scale it by 0.5.\nAdd the mirror modifier and select bisect for the X axis so that the object is mirrored and bisected about the X axis.\nTurn on \"On cage\" for the mirror modifier then enter edit mode for the object.\nWhen selecting the vertices on plane X=0, you should notice that two of the vertices correspond to visible mirrored vertices and two correspond to vertices removed by the modifier. \n\nSimple scene showing the behavior. \n[MirrorSelectOnCagePapercut.blend](MirrorSelectOnCagePapercut.blend)\n", "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}", "Multires: Editing base mesh creates random results on higher subdiv levels\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.1\n\nI applied a multiresolution modifier on this mesh, and it adds geometry that I didn't sculpt on the mesh (bumps, cracks...). It isn't always symmetric, as it happened even after I made more progress in my project. Deleting a face of the mesh and recreating it is enough to generate more of that random geometry. I don't know how to reproduce the problem. Removing and reapplying the multiresolution modifier works, but all the other sculpting is lost.\n[multiresolution.rar](multiresolution.rar)\n[multires_problem.blend](multires_problem.blend)\n", "Unable to undo subdivision with Multiresolution modifier\nOperating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 2.93.6\n\n**Bug**: If i subdivide with Multiresolution modifier after a sculpt action it doesn't undo subdivision but it needs to undo the sculpt action to undo that subdivision done with Multisolution modifier.\n**Note**: If no sculpt action is done before subdivision with Multiresolution modifier, the undo for subdivision just works (No need to undo the action done just before the subdivision to get the result back).\n**Mode** : Sculpt\n\n**Steps**:\n1. File> New> Sculpting. \n2. Add Multiresolution modifier.\n3. Sculpt with Grab brush.\n4. Subdivide once at Multiresolution modifier.\n5. Undo (Doesn't work).\n\n**File**:[Multiresolution_subdivision_bug.blend](Multiresolution_subdivision_bug.blend)\n\n", "Knife Tool produces bad geometry in certain cases (disconnected edges/vertices, overlapping faces)\nif i use tools knife i see this bug.\n\n\n\n", "Regression: Boolean Modifier Distorts UVs\nBroken: Blender 3.2.2 Official\nBroken: 2.93\nWorked: 2.92\n\nBroke with a3f091d7ce\n\n\nBoolean modifier distorts UVs of cutter object. In the attached screenshot and blend file. There are two cutters objects of roughly the same shape, one of them works correctly and the other doesn't.\n\n\n\n[tmp_2.blend](tmp_2.blend)", "Vertices will always merge when \"Clipping\" is checked on a mirror modifier\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: Not sure\n\nDespite \"merge\" being unchecked, if you have clipping checked on a mirror modifier it will behave as if merge is turned on.\n\n1. Scale down the default cube to 0.1. Apply scale.\n2. Add a loop cut down the middle and delete half the mesh\n3. Add a mirror modifier and turn off merge\n4. Select the edge loop you just created and move it very slightly off center (so there's a gap)\n5. Turn on clipping (but leave merge off)\n6. In edit move move the edge loop again and you'll see it auto-merge the vertices close to the edge. If you reduce the merge distance it will not merge them, showing that when clipping is enabled it will auto merge verts despite that being unchecked.\n\nAttached example:\n[clipping demo.blend](clipping_demo.blend)\n\n", "Carve vs. Bmesh booleans\n__ Copy for archival purposes from: 049334.html __\n\nAfter the removal of Carve for booleans, which is an important part of the \nFracture Modifier, I did some tests with Bmesh booleans to find out the \ndifferences and what we need to change in order to make FM work with that \nsystem. I'd like to share some of my observations and maybe discuss possible \nimprovements for consistency with you. \n \nOverview: \nBlend file: [booleans-bmesh-vs-carve.blend](booleans-bmesh-vs-carve.blend)\n(Note that you need an older Blender build with Carve) \n \nOur premise always was to make the Fracture Modifier a robust tool that should \nnot be nitpicky about the given input mesh. It should basically work for the \nartist at all times. This means the FM should also accept and work with \nnon-manifold, self-intersecting and complex meshes which are typical use cases \nin production and provide solutions for that. We have used Carve for this in \nthe past and analyzed and utilized its behavior to make that possible, thus my \ntests include all those possible variants. \n \nResults:\n\nMy first impression was that Bmesh is doing quite well now. It produces more \npredictable results for non-manifold targets and even for some manifold ones. \nHere are my observations: \n \n1 - Bmesh is leaving free edges in non-manifold results (well visible in orange \nin the lower right), those should be removed after operation. \n \n2 - Bmesh is not face normals aware. I'm not sure if this is good or bad thing \nin a higher sense, but I know that this is limiting factor for some users (see \ninverted normals variants which would flip results in Carve). \n\n3 - As a result of 2. Bmesh can produce meshes with inconsistent normals as it \nkeeps the original normals of the operator object but ignores them for the \nactual boolean operation (row 3 and 6). \n\nThis is what I could see, maybe there are more differences. I think that Bmesh \ncould be more consistent with Carve in general but it should at least output \nclean results. We have no \"make normals consistent\" modifier in Blender for \ninstance to fix normals within a modifier stack. \n \nI'm aware that these are not necessarily considered being bugs, so I'm just \nputting it here for discussion and making you aware of that.\n", "Allow changing the active modifier on linked objects\nUnzip the files from [active-modifier-linked.zip](active-modifier-linked.zip)\n\nOpen `linked.blend` and try to change the active modifer. You can't because it is linked.\n\nIn order to allow users to inspect their nodetrees (and eventually see the evaluated result of the modifier) I suggest we treat this as UI data and allow users to change that even for linked objects.\n\nWe do something similar already for the modifier \"Realtime - Display in viewport\" option.\n", "Strange shading behaviour when using boolean modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nWhen using a boolean modifier with an object that on a target object it uses the normals of the boolean object on the target object to determine the shading on the affected areas of the target object.\n\nWhen using a boolean modifier with an object that on a target object it uses the normals of the boolean object on the target object to determine the shading on the affected areas of the target object.\nThis means, that when using a boolean object that has shade flat on a target object that has shade smooth, the resulting object will have smooth shading everywhere except where the boolean operation happens.\nAdditionally, when using custom split normals (like e.g. weighted normals) it applies the custom split normals on the target object.\n\nThis behavior already seems pretty strange to me, since it almost always gives strange results since oftentimes the normals from the boolean object and the target object don't perfectly match, causing weird shading issues.\nI can understand that this may be an intentional feature, but it just brings so many problems, since normal editing modifiers after a boolean modifer like weighted normals don't affect the areas affected by the boolean modifier, meaning to tweak shading in these areas you have to tweak the normals of the boolean object and somehow make a seamless transition to the target object...\nApart from that it also causes some other problems, that are a worth a seperate bug report, which i will write shortly.\n\nAn additional problem with this is that shade smooth and shade flat aren't considered custom spilt normals, so after applying the boolean modifier the areas affected by the boolean modifier will change it's shading to that of the target object, since the shade smooth isn't applied as a custom normal.\nFor some reason that doesn't happen automatically, since directly after you aplly the boolean modifier the shading doesn't change immediately, instead it only changes when you \"recalculate\" the normals when using left click -> shade flat or shade smooth.\n\nA test file to demonstrate this behavior:\n[Test_file3.blend](Test_file3.blend)\n\nAfter applying the boolean modifier and \"recalculating\" the normals using left click -> shade flat or shade smooth the normals left from the boolean modifier will have vanished.\n\n\n", "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)", "Unexpected behavior when applying Geometry Nodes modifier on top of the Multires.\nThis is a more comprehensive report on a bug that was recently posted and closed [HERE ](T97603)\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1+\n\nApplying Geometry Nodes on top of the Multires modifier does not give expected results. Multires is an exception from the \"Applying a modifier will apply it as if it was first in the stack\" rule, when a modifier is applied on top of the Multires, the mesh changes will be applied to the currently visible subdivision level. Quick video below.\n[Multires GNodes Bug.mp4](Multires_GNodes_Bug.mp4)\nAnd the Example .blend file > [Multires GN Bug.blend](Multires_GN_Bug.blend)\n\nHow should applying the Geometry Nodes behave ? When the Geometry Nodes modifier doesn't change the vertex count and simply deforms the mesh, it should behave just like any other modifier, see example video with the Shrinkwrap modifier. \nSo what when Geometry Nodes does change the vertex count ? I say we keep the same behavior that solidify modifier has, it skips Multires and applies it as it would be first in the stack. While of course this will bring broken results, this is a already an existing behavior so i think it would be completely fine.\n\nSeries of images presenting how applying a Solidify modifier on top of Multires behaves. (Intended behavior)\n\n\n\n\n\n\n\n" ]

[ "Bmesh boolean fails with overlapping faces\nWin8.1 64bit | GTX680\n\nBroken: 2.76.4 ef49632\n\nBmesh boolean fails in this case.\n\nPlease see attached example, and try toggling Use Bmesh.\n\n[BMesh_boolean_t3.blend](BMesh_boolean_t3.blend)", "Some boolean modifiers not working\nOperating system: Darwin-18.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 6100 Intel Inc. 4.1 INTEL-12.8.38\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI'm using an object with a mirror modifier as a boolean object to cut out bits from another object but the mirrored side of the boolean object does not cut anything.\nPlease use the attached blend file to reproduce the problem.\n\nThere are 2 boolean modifiers. Each one is using an object that has a mirror modifier as well. With the one boolean modifier only one half of the mirrored objects is cutting and with the other boolean modifier nothing gets cut.\n\nAnother peculiar thing in this model: There is also a bevel modifier on the object. When I disable the bevel modifier in the viewport the boolean modifier is disabled as well.\n\nHere is the blend file that shows the problem: [boolean-problem.blend](boolean-problem.blend)\n\n", "Modifier Boolean sometimes not working properly\nOperating system: Windows 10\nGraphics card: GTX 960\n\nBroken: 2.80, 855b3e68ef27, \nWorked: (optional)\n\nOne cube is fresh created could do the Boolean with Plane object, but the one that do some works by some steps (watch?v=oknULG_zLJg) cannot be detected by Boolean modifier. However, I clean it as freash, It's still not work with Boolean modifier. I'm wondering If there something I missing, or It's actually a bug.\n\nThe brief steps in video:\n1. Change Cube's origin to left-bottom (also world origin).\n2. Hook on empty Cone with Copy Rotation and Rotate 60 degree for Cone.\n3. Create a plane and make It stick-like.\n4. Add a Boolean Modifier for plane with Cube. (Failed)\n\n5. I remove all modifier for that cube, but It seems to be a special cube that could not be Boolean with. The Attachment is in this scenario.\n\n[bug.blend](bug.blend)\n\nEdit:\nBoolean Difference does not work on some angle.\nsimple:\n[booleanIssue.blend](booleanIssue.blend)\n\n\nIt seems to be a Non-manifold problem, so It isn't a bug... :( ?" ]

[ "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)", "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)", "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", "In orthogonal view, XYZ axis overlay toggle doesn't work with axis aligned views\nBroken: 2.8x\n\nIn orthogonal view, XYZ axis overlay toggle doesn't work\n\n- press numpad 1/3/7\n- toggle xyz axis from overlays panel, they won't hide.\n\nVideo: [F8571714](2020-06-02_20-18-29.mp4)", "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.", "Node Group Sliders Slow Performance using Packed Textures\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.83.6, also tested in the 2.91 daily build, and 2.90.1. Same performance.\n\nUsing custom nodes groups sliders with packed textures make them very slow using Cycles, on EEVEE it seems working fine. \nIf i unpack the textures the sliders acts normally.\nI also notice every time i use any slider in the top left corner shows \"Updating images\" and the freeze occurs. \nI also discover if i change the values of all the sliders that are using the packed textures it comes back to normality and the lag disapears.\nIm not a tech but it seems it has something to do with loading the textures.\nSize and image formts seems that are not the problem i tried changing them.\n{[F9090399](Packed_textures_performance.gif), size=full}\n\n- Append node group with textures unpacked.\n- Sliders working good and fast with textures unpacked.\n- Pack the textures.\n- Sliders and load times freezing.\n- Unpack the textures again.\n- Sliders come back to normality.\nor\n- Open attached .blend file\n- Play with the custom node sliders\n- Unpack the textures again.\n- Sliders come back to normality.\n\n[Packed _Performance_new.blend](Packed__Performance_new.blend)\n\n", "Material reusability and fields\n# Problem\n\nCurrently materials are hard to share between multiple use cases. Any high level input that connects the material to outside information cannot be controlled from outside the material. For example, images and attribute names cannot be changed without changing the material.\n\nAny node input that can't vary per shader evaluation also currently isn't editable without changing the node directly. For example, the sky texture inputs can't be changed without changing the material directly.\n\nSo far, the answer to this lack of reusability has been simply duplicating the material. A combination of helper node groups, high level builtin nodes like various texture nodes and principled shaders have helped to make this work better. However, with material assets and increased use of attributes as shader inputs, this lack of re-usability is becoming a larger problem.\n\nPushing users away from reusing shaders causes performance problems too, particularly with shader compilation. Games spend a lot of effort reusing shaders with different inputs for this reason.\n\n# Solution\n\n## High Level Interface\n\n\n\nCurrently the property editor attempts to provide a high-level interface for editing a node tree. This exposes the value of **every single node value** to the user in a complex tree layout. That's flexible, yes, but most users don't want to edit every single value of the node tree, they want simple control of high-level input parameters.\n\n\n\nWe even present absurd menus like this to try to make editing nodes from the property editor viable.\n\n\n\nInstead, the material properties should follow the lead of geometry nodes and give a single high-level overview of explicitly configured node inputs. This has a few ramifications:\n\n- **Property editor node editing is removed**: Code is simplified, maintenance reduced, we don't have to try to make editing a graph in a vertical interface work well.\n- **Materials get group input nodes**: Since only explicitly \"exposed\" inputs are presented to the property editor high-level interface, materials become more like node groups-- they have explicit input nodes. For existing materials, these could be added by versioning for all sockets.\n- **High level material control is much more intuitive**: Since material authors can create large material node graphs but more easily choose what complexity they expose to users, using materials can be more powerful and simple.\n- **Material inputs are stored per-material, per geometry**: Similar to geometry nodes, these inputs are stored together for each material. Not storing them on the material is essential to allow reuse.\n\n## Fields\n\n\n\nExposing properties as node sockets provides the flexibility to create a high-level interface. But since node evaluations are expected to happen for every shader evaluation, it also doesn't quite work. Shaders aren't able to use a different attribute or image texture depending on some other input. Those things are expected to be constant.\n\nCurrently this isn't an issue because:\n1. Almost constant node inputs are just node properties, they aren't sockets.\n - This breaks reusability, since many of these like image textures are important inputs\n2. Other constant node inputs are strings, and there are no nodes to affect strings in shader nodes\n - This removes the ability to affect strings with nodes like switch nodes or string conversion nodes\n\nThe **fields** ([manual](fields.html)) concept from geometry nodes is a solution to this problem. Every node input can be a socket. If the input can't change per-shader evaluation, it will only accept single values. If it can vary, the link will be dashed, and that is clear visually.\n\nWithout the visual distinction, it would be too confusing to figure out which inputs can vary and which can't, and that status wouldn't propagate, which is an essential part of making the system usable.\n\n## Socket Types\n\nString, and image sockets should be exposed in shader nodes. This follows from previous points. \n\nIn the future, object and collection sockets could be exposed to shader nodes as well. There's no reason a geometry-nodes-object-info-like node couldn't work in shader nodes at that point. But that should probably be investigated as a next step. ", "Looks like an eevee limitations with UV maps and attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\n\nWhen working with multiple UVs and attributes, eevee disables some normal/bump maps.\nThere is an error in the console:\n```\nGPU_material_compile: Attribute \"nor\" overlap one or more index from another attribute. Note that mat4 takes up 4 indices. While merging eevee_legacy_material_surface_frag_opaque\n```\nIn 3.4, the shader cannot compile at all (pink texture).\n\nThis is not documented anywhere and it is not clear to me how it works, because until I connect nodes with attributes in Base Color, all normals are displayed.\n\n1. Open .blend file.\n2. Turn on the eevee render.\n3. Look, all normals are displayed.\n4. Connect nodes with attributes to Base Color.\n5. One normal map is missing. An error appeared in the console.\n\n", "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", " Greasepencil Hue/Saturation modifier\nOperating system:windows 10\nGraphics card:GTX 1060\n\nBroken:2.93beta\n\nHue/Saturation modifier can not take effect on fill-gradient", "Perfomance drop if Texture Limit Size enabled \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n[2021-04-02 12-29-11.mp4](2021-04-02_12-29-11.mp4)\n\n1. Add 4k cheker map to default cube\n2. Go to material preview\n3. Go to UV edit, manipulate UVs\n4. Toggle Texture Size Limit \n\n[#87133.blend](T87133.blend)\n", "Texture Painting not updating cycles shader in viewport\nOperating system: Linux-5.8.0-44-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa Intel(R) Xe Graphics (TGL GT2) Intel 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.92.0\n\n\nLevel 1. When texture painting in the 3D viewport, the image is updated, but the visible shader on the object doesn't update in cycles until switching to viewport shading and back to cycles.\nIt still works when switching to Eevee shading. When reloading the image in the shader image texture node, it updates in cycles, but the problem persists when the image is updated (painted on) again.\n\nLevel 2. The above bug becomes worse as follows:\n\nIn cycles the image stops updating even when switching to viewport shading and back to cycles.\n(A)-When reloading the image in the shader image texture node, it updates in cycles, but any new paint on the texture in the viewport or image editor -> paint mode won't update until step A is repeated. \n\nI do not know exactly what triggers this 2nd level bug, but it doesn't take long to show up. \nI was able to repeat it just by painting and switching between Eevee and cycles using my test .blend file (attached)\n\n\n\n\n1. Assign a material with an image node to an unwrapped object\n2. Switch to viewport texture painting and start painting on the image in cycles shading. \n3. The image updates in viewport shading, but not the visible shader on the object in cycles. \n4. Switch to Eevee shading - now eveything works as expected.\n\n5. I do not know what triggers the level 2 bug.\n\n[Cycles not painting on Cube.blend](Cycles_not_painting_on_Cube.blend)\n\n\n\n\n\n", "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", "Set Material Node does not reuse existing empty slot\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\n\n\nIf I set material with Set material node, it will not appear after remesh modifier.\nNo matter if i set material to initial instance or to final geometry after Realize node.\nHere the file for tests and demo\n[remesh after GN.blend](remesh_after_GN.blend)\n\n\n\n[2021-11-29_01-09-32.mp4](2021-11-29_01-09-32.mp4)\n\n[2021-11-29_01-13-43.mp4](2021-11-29_01-13-43.mp4)\n\n", "Remove normalization from original coordinate attribute (CD_ORCO)\nFrom #95776:\n\n> The internal CD_ORCO attribute is normalized to 0..1 which is not really helpful, not even as default texture coordinates. It would be good to do some refactoring so these are stored unnormalized and then applying any additional texture space scaling for rendering only." ]

[ "Image Texture Node - mapping settings ignored in the viewport textured mode\nBroken: 80ffa73b3f87 (blender2.8 HEAD)\nWorked: 2.79\n\nIn 2.79 you can set a mapping offset for textures, directly in the texture node. In 2.80 those settings are carried over, but:\n\n - They only work for render/lookdev - not for workbench\n - There is no UI to edit them - the texture panel does not show Cycles/EEVEE textures\n\nOpen this 2.79 file, change to textured mode and play with the Mapping settings on the texture panel:\n[uv-displace.blend](uv-displace.blend)\n\nNow in 2.80 turn on the texture option in the shading menu, you will see no texture offset in the viewport. Unless you switch from solid to lookdev or rendered (regardless of the render engine being EEVEE or Cycles). Besides you cannot edit the offset in 2.80." ]

[ "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", "Moving a keyframed object starts moving from wrong location when linked scene open in separate window\nOperating system: linux\nGraphics card: nvidia\n\nBroken: 3.2\nWorked: didn't check\n\n- Create a keyframed object that moves, i.e. frame 1 (object.x=0) and frame 30 (object.x=10)\n- Create a linked copy scene (Scene.001) and open a new main window set to that scene, and set timeline to frame 1.\n- In original window in original scene, scrub timeline to anywhere after frame 1.\n- Press \"g\" to move object in original window. Notice the object jumps to where it is in the other main window (Scene.001) instead of starting to move from where it is visually in the current window and scene.\n\nExpected:\n- Moving respects the current window/scene.\n\nRelated issues:\n- The keyframe color indicators stay orange (instead of turning yellow) when scrubbing to the frame with the keyframe and the location values don't update.\n\nTest file (first 3 steps included)\n[#99597.blend](T99597.blend)", "GN +motion blur =bi-direction\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\n\n\n\n[Мошкара.blend](Мошкара.blend)\n\n", "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!", "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", "python to_track_quat(track, up) could use option 'target z' (just like constrain TrackTo)\nIn constraint tab we can use 'track to' constraint, and it has very helpful option '**target z**' - use target Z axis, instead world Z.\nI really wish python counterpart : to_track_quat(track, up), had this option too (maybe optional to not break api). ", "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", "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", "Render automatically sets scene camera when there is none\nOperating system: Arch Linux\nGraphics card: GTX TITAN\n\nBroken: blender 2.80.68 (dfbbc5067e40)\n\n\nThe different ways in the active camera is shown isn't updating consistently, nor always correct\n\n\n- start with default scene (cube, light, cam)\n- add a 2nd camera, make it active and switch to cam view with Ctrl+Numpad0\n- use something like fly mode to get a good view of the cube\n- switch to Scene properties, note Camera is set correctly\n- delete the active camera with X\n- there's no active camera anymore, shown consistently:\n - Camera is empty in Scene properties\n - direction triangle of remaining cam is not filled\n - outliner doesn't show outline rectangle on camera objectdata\n- however, press F12, render works using the remaining camera\n- escape image view\n- select the remaining camera\n- move it a bit in 3D view\n- press F12, note that render is using new view\n- in Scene properties the Camera selection is now sometimes correct, sometimes still empty. Similar for camera objectdata icon in the outlienr. However, the direction triangle on the camera stays empty\n", "Motion Blur missing in the Render Preview of viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\n\nIn 2.83 we had the access to realtime motion blur with Eevee (which was limited to camera deformation).\nIn 2.90 and above this was replaced with a new motion blur system that is render only. \nEevee is amazing for having realtime screen space reflections, ambient occlusion, depth of field and motion blur, which made it perfect for screen capture or viewport rendering an animation without excessive time consumption.\nI was wondering wether this is a decision or a bug, since having the camera deformation motion blur back in the viewport would allow for the same realtime rendering results as in 2.83\n\n- Go to camera view\n- move the camera around\nIin 2.90 and above and youll see any motion blur previously existent in 2.83 is gone. \n", "Animation: Exiting NLA tweak mode on empty action corrupts entire NLA track\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3060 Ti\n\nBroken: 3.3.0, 3.5.0\nWorked: Unknown\n\n\nWhen tweaking a strip on the NLA, if the user deletes all the keyframes of the action being tweaked, when the user exits tweak mode, all other NLA strips on that track will be moved in an unexpected and undesirable way.\n\n[tweakbug.mp4](tweakbug.mp4)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open the attached .blend file\n2. Delete the keyframes on the track being tweaked.\n3. Exit tweak mode by pressing Tab.\n4. Observe that the NLA strips have been moved.\n\n[tweakbug.blend](tweakbug.blend)", "Eevee motion blur causes ghosting on image sequences when steps are greater than one\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nAlso tested on Windows-10-10.0.19041\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\nThe next frame of an image sequence/video texture is added onto the current one when the step count in Eevee's motion blur is any value greater than one.\n\n\n\nDemo file: [blur.blend](blur.blend)\nVideo used: [demo.mov.zip](demo.mov.zip)\n\n1. Create a material that references a video or image sequence in any form\n2. Turn on motion blur and set step count to any value greater than one\n3. Render", "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", "Tracking graph not showing as expected (Not a bug)\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.82\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional) Not sure this is a bug as I went back to Blender 2.79 and noticed similar behavior. It is however unexpected behavior.\n\n\nUnexpected/confusing Linked behavior between areas.\nMovie Clip Editor graph mode shows unexpected behavior.\n\n\nOpen a new general workspace. In my case I have a 3D Viewport as the main area, below it a Timeline. To the right of the 3D Viewport and the Timeline I have a Outliner and below the Outliner a Properties area.\n\nChange the main 3D Viewport to a Movie Clip Editor.\nLoad a image clip sequence. (for this sequence it does not seem to matter if you make any changes to the tracking points, focal length or sensor size)\nSelect any number of tracking points and track them. (Does not seem to matter if you track forward or backwards).\n\nChange the timeline to a movie clip editor.\nChange the type from a Clip to a Graph.\nEven though you have tracked several markers the graph is empty.\n\nRemove the Timeline/Movie Clip Editor area by letting the top Movie Clip Area expand over it.\nThen split/duplicate the Movie Clip Editor area downwards so there is a duplicate above and below.\nNow take the bottom Movie Clip Editor and change its type from clip to graph. You will now see the tracking graph with green and red graphs for the tracking markers.\n\nNow split the original Movie Clip Editor in two horizontal areas. So above the graph you will have two Movie Clip Editors, one left and the other right.\nTake any one of the two and either load a new clip, image sequence or simply unlink the data block and the graph will disappear.\n\nThis behavior is unexpected. It does not throw away or corrupt any data but did cause me to have to spend quite a bit of time trying to find out how to get the graph to actually appear and not disappear. I'm hoping you can find a more consistent and intuitive way of handling this.\n\nThank you for your awesome work on Blender!\n", "Alembic: Camera properties (focal length, focus distance, ...) animation not importing\nMacOS 10.13.3\n\nBroken: 2.79 5bd8ac9\n\n\n\nWhen importing camera in FBX or ABC file (exported from Nuke), the animation of focal length is not importing. It's being set to a constant value according to frame 1. Other values are imported correctly.\nIf I reimport to Nuke, the focal length is correctly animated.\n\nCamera files attached.[camera.fbx](camera.fbx)\n\n[camera.abc](camera.abc)\n" ]

[ "Regression: Setup tracking scene is disabled\nOperating system: Linux-5.19.0-21-generic-x86_64-with-glibc2.36 64 Bits\nGraphics card: RENOIR (renoir, LLVM 15.0.2, DRM 3.47, 5.19.0-21-generic) AMD 4.6 (Core Profile) Mesa 22.2.1\n\nBroken: version: 3.5.0 Alpha, caused by fe38715600\nWorked: 4d497721ecd11f08b832c6b083b1ecc45f692279\n\n\"Setup tracking scene\" is disabled after the \"solve camera motion\"\nI've tried with different videos and setups but with the same result.\n\nOpen the attached file with 4d497721ecd11f08b832c6b083b1ecc45f692279 or older\n\n\nOpen the attached file with the current master\n\n[untitled2.blend](untitled2.blend)\n\n" ]

[ "Rip edge-move for curves\nCurrently with meshes you can press Alt+D to add a vertex at one side of the verts edges and drag it *(based on the mouse cursor location)*.\n\nThis same behavior could be added to curves.\n\n- the basic behavior with single vertices selected is simple\n- with multiple segments are selected this becomes more involved (see how this works for meshes).", "GPencil: Airbrush draw tool with solid stroke has transparency artifacts\nOperating system: Win 11, GTX 3080, Wacom Tablet\n\n\n\nBroken: 2cd7e70c18a8\nWorked: ~~3.3.0~~\n\nThe airbrush tool has artifacts around the stroke during drawing. Also what is drawn during stroke has nothing to do with the final result visually. Please see the video for the issue.\n\n\n\n- New scene -> 2d Animation\n- Select Airbrush tool from the tool pane\n- Switch to `solid stroke` material from header\n- Draw\n\n[image](attachment)\n[blender_lOlSgoorkK.mp4](attachment)\n", "Trackpad stops working for a while\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M\n\nBroken: 3.6.2\nWorked: don't know\n\n\nSometimes, Blender stops responding to trackpad gestures such as two-finger scroll or pinch zoom. This is not just in the viewport but everywhere - I can't scroll menus or the node view, for example.\n\nThe UI is otherwise responsive when this happens - I can scroll menus by dragging the slider at the edge, just not with a two-finger scroll.\n\nIf I go and do something else in another app for a few minutes, it usually fixes itself.\n\nThis happens sporadically and I don't have a reliable way to reproduce it, but it seems to happen often after I render an image - after the image has rendered, I try to use pinch-zoom to look more closely and find I can't. I am not sure if it happens in other situations as well - if it does I will update this report.\n\n\nI'm afraid that I can't reproduce this reliably - it just happens every now and then, in any .blend file. I am happy to take any advice on how to look for a way to reproduce it.\n\n", "Follow Path & BezierCircle working unexpectedly with Lattice Modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\nI have an object attached to a Bezier Circle with a Follow Path Constraint. The Bezier Circle is being deformed by a Lattice Deformer. If the Lattice Modifier's 'Align on Spline' button is disabled, the Bezier Circle deforms properly, however the Follow Path Constraint doesn't work. If 'Align on Spline' is enabled, the Follow Path Constraint works, but the Bezier Circle is deforming incorrectly.\n\n\n1. Enable the Bezier Circle's Lattice Modifier's 'Align on Spline' button.\n[Lattice_Demo.blend](Lattice_Demo.blend)\n", "Tweak tool doesn't drag the point\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 516.59\n\nBroken: version: 3.6.0 Beta\n\nThe tweak tool is broken. It doesn't tweak a point.\n\n\nChhose the Tweak tool and try dragging a point.\n\n", "Converting hair don't work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: -\n\nUsing any of the conversion options in {nav Obejct > Convert}:\n1. Converting the new hair curves systems to any other type don't work, \n2. Converting the new hair curves systems to `Curves` removes the `Surface Deform` modifier\n\n- add a mesh and add the `Empty Hair` curves\n- go to sculpt mode for the hair system\n- add some hair and optionally start to sculpt the the hair with the Comb brush\n- go to object mode\n- press {key F3} or go to {nav Obejct > Convert} and try convert the hair to any other type.\nNoting will hapen unless you convert it to `Curves`, but the `Surface Deform` modifier will disapper.\n\n[Test Hair2.blend](Test_Hair2.blend)\n\nthis files has the old and new hair system for teating, and the old has a tool the new don't have, vutting the size of the hair. I don't know if that is a missing tool or by design, but I real hope that can be added later.\n\nkeep up the grate work :-)", "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", "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", "Spreadsheet editor in `Original` mode shows no geometry for curves\nOperating system: Linux-5.15.8-76051508-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: AMD Radeon RX 6700 XT (NAVY_FLOUNDER, DRM 3.42.0, 5.15.8-76051508-generic, LLVM 12.0.1) AMD 4.6 (Core Profile) Mesa 21.2.2\n\nBroken: version: 3.1.0 Alpha\nWorked: never (?)\n\n\nThe `Original` evaluation state should show the geometry before it is altered by modifiers.\nOn a curve object the `Original` state shows no geometry information.\n\n- Add curve object\n- Open spreadsheet editor\n- Switch to `Original` evaluation state", "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.", "Grease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\n\n\nBroken: version: 3.3.0 Alpha\n\n\nWorked: Blender 3.2 \n\n\n\n\nGrease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\n\n\n\n\n - New scene.\n - Keep the cube.\n - Don't delete it.\n - Add an empty Grease Pencil Object.\n - Don't delete the cube.\n - Add a Line Art Modifier to the Grease Pencil Object,\n - Switch Source to Object, and select the cube.\n - Assign the default layer and material.\n - You should be seeing something like this\n\n\n\n - Add geometry nodes nodes to the cube.\n - yes keep the damn cube.\n - here is the simplest setup that involves instances that I could think of\n\n\n\n - as you can see in the viewport the grease pencil line art has dissapeared completely.\n\n\nThanks for looking into it.\n\n", "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)", "Color Management / Use curves : Setting clipping option to Min = Max causes CRGB curves to go blank.\nWindows 10, GTX 1660\n\nBroken: Blender 2.82 release.\nBroken: Blender 2.83 daily update\n\nThis will recreate the black CRGB Curve display to go blank.\n\n1. In the Properties Panel, Select Color Management.\n2. Enable 'Use Curves'\n3. Select the 'Clipping Options'\n4. Set 'Max Y' to 0.00\n5. Now select anywhere in the CRGB curve display. It goes blank.\n", "GPencil: Average tool in Vertex Paint mode not working as expected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.0 Beta\n\nThe tool paints colors that exist in points far from the brush's area of influence and sometimes paints unexisting colors.\n\n1. Draw simple strokes with the Solid Stroke material.\n2. In VP mode paint half of it orange and half blue.\n3. try the the Average tool in the half blue area then in the other half.\n4. Now do Paint > Reset Vertex Color.\n5. Try the Average tool again.\n\n<video src=\"attachment\" title=\"Vertex Paint Bug-1.mp4\" controls></video>\n\n", "Proportional editing doesn't work with loop slide\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.2 Release Candidate\n\n\n[2021-07-06 19-47-45.mp4](2021-07-06_19-47-45.mp4)\n" ]

[ "Curves sculptmode: Slide tool with Pressure Sensitivity always resets at the end of the stroke\nOperating system: Linux-5.18.16-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.0 Beta\n\nCurves will snap back to it's original coordinates after the stroke. Turning off the pressure sensitivity will allow the hair curves to stay.\n\n*Use a pentablet or a screen display with pressure sensitivity*\n - Load Factory Settings\n - Go to 3D Viewport\n - Add mesh primitive\n - Add curve hair object while mesh primitive is active\n - Go to sculpt mode\n - Add some hair with the [**Add**] tool\n # Slide hair with the [**Slide**] tool\n\n----\n**Pentablet:** XP-Pen Deco 01 V2\n\n" ]

[ "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)", "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)", "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)", "Subdiv hangs blender\n**System Information** DESKTOP-HR30UII\nOperating system:Windows 11 Home Single Language\nGraphics card:2GB NVIDIA GRAPHICS DRIVER\n\n\nBroken: Blender Version 3.5\nWorked: ?\n\nBLENDER 3.5 KEEPS NOT RESPONDING WHILE I USE MODIFIERS \n\nON BLENDER ADD MESH AND ADD MODIFIERS TO SUBDIVISION SURFACE THEN CHANGING THE VALUE OF LEVELS VIEWPORT VALUE ABOVE 4 .THEN ONWARDS BLENDER COMPLETELY STOPS WORKING AND I NEED TO RESTART IT AGAIN\n\n", "Blender Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at [email protected]\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file", "Blender keeps crashing relocating linked library [3.5.1]\nOperating system: Windows-10-10.0.25357-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\nRelocating linked library file results in instant crash when different file is chosen. I need this because i work on both OSX and Windows. While testing file version, i had issue with indirectly linked files. These are nested files so to say. They are linked blend files inside another linked blend file. \n\n- Download and Unzip attached `RML-test file-bl350.zip` file\n- open file \"RML-test file-bl350.blend\"\n- go to `Outliner` > `Blender File` and select the linked lib file with exclamation mark \"linked object\"\n- Right click and select \"Relocate\"\n- Point to the file \"linked object-bl293\"\n\nBlender file browser closes and crashes short after.\n\nSide note\nThe linked lib blend file is name \"linked object\", if i rename the \"linked object-bl293\" to \"linked object\" it works. But because i work on both OSX and Windows and sometimes also with different version. I need to rename linked files so i dont break anything.\n\nHowever, i jsut tested these 2 files in an issue folder i created and then it links just fine. When these files are linked in the original folder, blender crashes right after i pick that file \"linked object-bl293.blend\". See attached screengrab.\n\n\n", "persisting issue: MacOS, Blender's system device usage rights (info.plist) add camera & mic usage descriptions\nOperating system: MacOS (13.2.1) \nGraphics card: any\n\nBroken: (All Blender addons that would need external peripheral like camera or microphone access, will cause Blender to CRASH, because of MacOS)\nWorked: (it's a MacOS dependent issue (since maybe macOS 12?)\n\n*\n\"Termination Reason: Namespace TCC, Code 0\nThis app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an com.apple.security.device.camera key with a string value explaining to the user how the app uses this data.\"*\n\n\nInstall an anddon that would need camera / microphone access. After checking the checkbox in blender addon menu, Blender crashes (or at the point that addon is running code that would need such peripheral. Nowadays you cannot add it manually and this needs to be addressed globally.\n\nFIX:\nglobally add info.plist usage rights for camera, mic and other widely used peripherals for blender's MacOS version, since the current state of MacOS, doesn't allow addon's to access any of those, and it really hinders the blender as a core, those of course aren't used if not needed, but at the moment addon developer cannot have any modules that use any of those without MACOS causing the blender to literally crash. I hope this could be corrected asap. Before it was still possible to manually grant access to applications via macos settings, but alas, its not anymore possible.\n\n", "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.", "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", "Blender Crash when deleting images too fast\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.44 30.0.13044.0\n\nBroken: version: 3.2.0\n\nBlender crashes when deleting images in the Layer blend file libery\n(3.3 alpha is crashing also and i didnt found any report about this issue)\n\n\n* go to outliner -> select blend file\n* make sure to be in the material preview mode\n* delete the first image by right click and then click on delete image\n* (now u only need to rightclick and leftclick to delete next images, because u dont need to aim for the delete anymore)\n* delete images while blender tries to preview the last change after deleting one of the images\n blender crashes\nwhen deleting images too fast, my blender just crashes (happens on my bad pc often, because i download models and rework them)\nIf you wait for the new material preview of the model after deleting nothing happens, but if you dont blender crashes when continuing to delete images\n\nVideo: CvO9nw4qilc\n\n[pharaoh x suite.blend](pharaoh_x_suite.blend)\n", "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)", "Combine crash\nOperating system: win 10\nGraphics card: 3090\n\nBlender Version 3.5.1 \n\nWhen using ctrl+j to combine components, blender will crash.\n\n", "Blender Crashes on Render (Save As), then refuses to start\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1\nWorked: N/A\n\nFirst observed with the attached file. I tried to save a png image render from it; when I clicked \"Save As,\" Blender crashed and then... wouldn't open. It seemed to initiate startup, because the little black window that usually notified me that it was reading my userprefs.py file would blink into existence just long enough for me to register what it said, then close itself and act like I hadn't clicked it.\n\nRestarting my computer fixes the problem temporarily, until the next crash. The crashes are inconsistent, but seem to happen only when I hit main menu items like Open or Save. This includes previous versions, apparently, as I still had 3.5 installed and it does the same quick blink.\n\nThe only thing I could think of was that that Read line in the black window referred to finding the userprefs file in C:\\ when I installed everything into M:\\, but I tried copying the required path over to C:\\ with no effect and also it gives me that same message when it's working and starts up fine.\n\nI also tried repairing the 3.6.1 install, and uninstalling/reinstalling, to no effect.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Blender Crashes when deselecting Name-fields\nOperating system: Windows-10\nGraphics card: NVIDIA GeForce RTX 3070\n\nalso tested on:\nOperating system: Windows-11 Home - Microsoft Surface\nGraphics card: - / 11th Gen Intel(R) Core(TM) i7-1185G7\n\nBroken: (tested with)\n- version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a, type: release\n- version: 3.5.1, branch: blender-v3.5-release, Date: 2023-04-24 18:11, hash: e1ccd9d4a1d3\n\nWorked: -\n\nFor a specific project, if I select any Text field that contains the name of an asset (texture, object, scene, ...) and click anywhere else within the Blender window, Blender will crash. \n\nThis error does not appear for other projects of mine or a new one.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Open file\n2. Navigate to Texture\n3. Create a new Texture\n4. Select Texture name (no need to alter the name to reproduce the error)\n5. Click into e.g. Viewport or hit Enter\n\nI created a copy of the problematic project, deleted all of its content and used the Blender cleanup feature to remove any remaining data blocks. Still the issue persists. Except for the missing shutdown logs due to the crash, the Debug Log doesn't show any differences to a normal file AFAIK.\n\nBlender does NOT crash when I use \"Escape\" to exit the field.\nTo be precise, the crash happens when deselecting \"Name Fields\" in the outliner, the Properties Panel or similar.\nThis doesn't happen in Search fields or Value fields that take e.g. floats for properties like \"Strength\" etc.\n\nThe project (used as asset library) worked fine yesterday and as far as I'm aware no updates were installed. I tried updating my NVIDIA driver but to no avail.\n\nNext, I'll try to copy my assets to a new file.", "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 3.0 alpha crashes \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel 4.5.0 - Build 26.20.100.7925\n\nBroken: version: 3.0.0 Alpha\n\nWarning I am totally new to Blender so please bear with me. Seems guaranteed to crash if I do the following:\n1. Click on Circle select while using Layout or Modelling.\n2. If I use Lock on any of the Axis X Y or Z can't consistently Move, Duplicate or Rotate the object. my Files are basic since I am just beginning with Blender.\n3. Same thing happens on all versions I have tried 2.9 and higher.\n\n\n" ]

[ "Fix big LIghtCache restriction\nAs reported in #78529 saving big lightcache is impossible due to blocksize restriction.\n\nFor now we restrict the lightcache size that can be written to disk but it would be better to slice the huge textures to avoid such limitation.\n\nHowever this needs some refactors in GPUTextures namely the need of a properly exposed `glTexSubImage2D` and `glTexSubImage3D`.", "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", "Object drop snapping should be disabled for cameras, lamps, etc\nE.g. when dragging a camera from the Outliner into the 3D View, it gets an all-0 rotation, which isn't useful. And it will always snap to an underlying surface, which is annoying because you wouldn't want a camera to snap to geometry or the grid. Think we should just bring back the old dropping behavior, even if it's a bit hard to predict which distance along the view it will use to place the object.\n\nIt wasn't intentional to have this. In review I asked to address this which I thought it was. Probably a misunderstanding.\n\nShould it be disabled for empties as well? It may be useful to have snapping for these.", "Can't setting camera.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.19\n\nBroken: version: 3.6.1\n\n\nWhen I render, will jumpback to the camera.002\n\n", "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 2.82: Fails to immediately report information to XServer on Linux\nOperating system: Manjaro Linux 5.6\nGraphics card: GTX 1070 ti\n\nBroken: 2.82, found as soon as app is open.\nWorked: 2.81\n\nIn Linux, if an app doesn't report anything to the Xserver, but still specifies window dimensions, it leads to a sort of awful stuttery broken effect while said app is loading. This is visible in 2.82, where, upon opening and loading, it fails to report to Xserver, and looks like this:\n\nIt looks like this while the app is loading (that is, only a title bar) and produces an odd effect if the window is dragged around during loading, and I can confirm that it lasts longer if Blender is put on a mechanical hard drive VS an SSD. This doesn't occur launching any other apps, nor even a binary of 2.81, which instead displays a gray screen while loading. This is obviously just an aesthetic problem, but it can (rarely) cause issues. \n\n\nOpen Blender. ", "Ambient Occlusion node with image texture\nOperating system: macOS 12.6.8 – 16GB\nGraphics card: Apple M1 8/4-4\n\nBroken: 3.6.3 RC\n\nWhen I mix an image texture (here a PNG) with Ambient Occlusion node, its not working, or results a weird render at least.\nIn the render-preview the image is disappearing, but in the final render is there but partially and broken (i think).\n\nAttached a screenshot and a very simple blend file.\n\nI hope I am the idiot and doing something wrong, but after a full week I didn't find the answer to this strange behavior.\n\n**Edit: it seems an earlier resolved problem is back:** [#94050](94050)\nIf I switch to CPU-rendering, its working fine... :(\n\n", "Transform gizmo disappears when up very close\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 3.0.0\n\nWhen your camera zooms in a lot because of very low near plane the transform gizmo disappears and when trying to zoom out just a bit you jump quite a lot back.\n[transformGizmoDisappearsNear.mp4](transformGizmoDisappearsNear.mp4)\n\n1. Create cube\n2. Set the near plane to 0.0001 m or lower\n3. Select any vertex and press the button to frame the object(for Industry Compatible it is **F**)\n4. The transform Gizmo disappears, when moving the camera it jitters strangely and when trying to zoom out a bit the camera jumps back a lot", "Viewer Node from Compositor is not updated in Camera's Background Image\nOperating system: Arch Linux\n\nBroken: 3.2.2\nWorked: never\n\nThe viewer node result from compositor is not propagated in the 3D viewport as a camera background image when selected. This might be really useful in many cases. I often use compositor to edit input videos and I want to adjust the 3D scene according to the video. Especially with the grease pencil, there might be a case when the animator wants to draw an animation over an existing one. It is really strange that the option to use the node is there but it's unusable, related to #73188.\n\n**Possible problems**\nRecursion mentioned in #73182. Might be resolved by overriding the order when the node is used in the camera or letting the user change the order somewhere.\n\n**Workaround**\nExport the composited result in a video and then use as a background image or hit F12 after every frame and use the render result in the background image.\n\n1. Create a setup in compositor that changes over time\n2. Connect the result to Viewer node\n3. Use Viewer node as camera background image in the 3D scene\n4. Move to another frame - no change in the background image\n\nIncluded the project file with simple texture animation and two workspaces. One with split screen where both compositor and 3D view are visible. When the compositor is hidden, the background image is not changed at all. When it's visible, it's updated but from the previous frame or state. It seems like the camera first takes the compositor result as the background and then the new compositing takes place. Yes, I understand that it's the design of these stages but this is still a trick to somehow make it work, the image does not update at all without the compositor window being active as shown in the second workspace.\n\n[viewerNodeInCamera.blend](viewerNodeInCamera.blend)", "the Unwrapping function doing wrong calculation\nOperating system: Windows 10\n\nBroken: 2.79, 2.80\n\nwrong size calculation uv shells\n[uv_unwrapping_wrong.blend](uv_unwrapping_wrong.blend)\n\n\nPS in other software\nmaya\n\n\n\nrizom uv\n", "Viewport fps tanks when application is full screened on macOS\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 3.5.1\n\nI've noticed that when using either my M1 Air or M1 16\" Pro, when running Blender, the viewport performance is heavily dependent on the physical size of the viewport on screen. At first I thought this was just a limitation of my base model M1 Air, but it also happens on my M1 Pro Mac when plugged into a 4K or 5K display. Having Blender fullscreen will drastically reduce the viewport performance, but scaling the window down will fix it. Setting the scaling in macOS lower can also reduce the issue.\n\nAs far as I can tell, this happens in both 3.5 and 3.6, Metal and OpenGL backend. \n\nPerhaps this is intended functionality, but I can run Blender on potato PCs and not have frame drops like this. Even just the default cube will drop tons of frames on both my Macs. \n\nOpen Blender on a high resolution display and just start using it. The viewport performance is usually pretty poor on 4K / 5K displays if not scaling the window down.\n\n", "Move some parameters to Blender's DNA\nThese parameters are supported (or going to be) by EEVEE-Next, and we should avoid duplicating the settings for each engine:\n- Motion blur curve\n- Panoramic camera settings\n- View Layer material override\n\nThis is a big change and 4.0 should be the right time to do this.\n\n", "Grease Pencil Outline Modifier not showing with duplicated camera in outliner\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.33\n\nBroken: version: 3.4.0 Alpha\n\nThe outline modifier of a grease pencil is not showing with a camera that gots duplicated in the outliner\n\n\n- Remove the default cube\n- In the outliner copy and paste the default camera\n- Remove the first camera\n- Add a grease pencil stroke\n- Add a Outline modifier to it\n\nThe outline will not show.\n\nThis bug is related to this report. I am just not sure if it is two different causes and cases, or the same. T102373\n\n\n\n[2022-11-09 10-30-57.mp4](2022-11-09_10-30-57.mp4)\n\n\n\n", "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)", "Brushes Assets Viewport User Interface\n{[F13331829](image.png), size=full}\n\nAdditional Notes:\n\n{[F13331831](image.png), size=full}" ]

[ "Lines too thin on macOS\nMacOS 10.14.1\n5K 27\" 2017\n\nAnnotate Pencil too thin for Mac\nAlso please thickness unlimit not only up to 10.\n", "Blender 2.80 too thinner wire.\nOperating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nBone is too thinner same on Dope sheet, \n\n\n\n\n\n", "Annotate and TimeLine too thin for Mac.\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\n\nBroken: version: 2.81 (sub 2)\nWorked: (optional)\n\nToo thin need to fix everything on TimeLine and Annotate\n\n\n\n\n" ]

[ "Wireframe visible when going relatively far from the 0,0,0 (20 meters)\nOperating system: Linux-5.16.15-76051615-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.54\n\nBroken: version: 3.1.2\nWorked: not sure\n\nYou can see the geometry of the object in cycles render in far away parts of it if the object its relatively far from the origin, 20 meters it's not so far, but you can see it.\n\n\n\n\n1.- Open the provided .blend\n2.- Don't touch anything, just enable viewport render\n3.- You should see the wireframe being visible\n4.- If you don't see the wireframe, you might need to change your render device/backend. E.G. Change between CPU, CUDA, OptiX, HIP, Metal, etc. At the moment, @Alaska can only reproduce this issue in CUDA with Blender 3.2 while @derekbarker can only reproduce the issue with OptiX.\n\n[train_bug_report.blend](train_bug_report.blend)\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", "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", "Blender crashes in edit mode in wireframe view\nOperating system: Linux Mint 21.1\nGraphics card: geforce gtx 1060\n\nBroken: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc, type: release\nWorked: 3.5.1\n\nOn the attached file, selecting the bear head and going into edit mode, then switching to wireframe, or switching to edit mode while in wireframe mode, blender crashes and exit.\n\nSelect the bear head, switch to edit mode in wireframe. It crashes. It doesn't happen with a default cube in an empty file. The bear has geometry node hairs attached to it on the fur layer, but the geometry nodes are disabled. It also has an armature.\n\nThe problem also happens on windows10 on the same computer.", "Mesh flickers in edit mode if shapekey added\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.0.0 and later\nWorked: 2.93\n\nThat mesh I put in .blend file is from my old project (started in 2.79). For some reason normals on that mesh go crazy if I try to edit it in Face selection mode. I found that this particular mesh can't have shapekeys and auto smooth enabled at the same time.\n\n1. Add Basis shapekey to the mesh\n2. Enter Edit Mode\n3. Select Face Selection Mode\n4. Move any face\n\n[bugFlicker.blend](bugFlicker.blend)\n[bandicam 2022-12-03 01-21-18-089.mp4](bandicam_2022-12-03_01-21-18-089.mp4)", "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)", "Artefacts when enabling shadows in solid shading viewport mode\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\nWorked: unknown\n\nEnabling shadows in solid shading mode results in flickering blocky artefacts\n\nDefaults scene, delete everything\nAdd a plane, scale up 20 times\nSwitch to solid shading and enable shadows\nMove around the viewport\n\n\n\n[Schermopname 2021-12-06 om 12.24.41.mov](Schermopname_2021-12-06_om_12.24.41.mov)", "MacOS Crease Problem Back end Metal\nOperating system: Macbook Pro 14\nGraphics card: Apple M2 Pro\n\n3.6.2\n\n\nWhen the backend setting of macos is set to metal, the color change of the edge when applying blender's vertex crease. When edge crease is used, magenta color does not come out and it is processed as black color.\n\nrecording video\n\nview?usp=sharing\n\nview?usp=sharing\n\n", "Cylinder mesh (outline) will not display in ortho when viewed end on with no end caps.\nOperating system: Windows 10 64-bit\nGraphics card: Not applicable\n\nBroken: 2.80 64-bit installer 9/2/2019\nWorked: Cylinder displays correctly in version 2.79b\n\nUpon further investigation problem seems to be confined to Object mode only. Cylinder seems to display normally in Edit mode, front orthographic.\n\n**Update (9/27)**: If I add a curved path and go to Object mode to scale it to length it disappears from view in both Orthographic and Perspective views. It appears in Edit mode but the scaling works differently in Edit mode for some reason. In Object mode one end of path remains anchored when scaling on Y axis, for example, but in Edit mode scaling occurs in the positive and negative directions simultaneously.? Not a show stopper but puzzling.\nAgain, the translation and scaling icons are still visible but not the object. Other objects remain visible selected or not. Perhaps it has something to do with the selection order; just a thought.\n\nThis may not be the correct place for a suggestion about Blender version information but it could be helpful, particularly for bug reports and such to put version information in the main menu under 'About' as in other Windows apps.\n\n**Original Complaint**\nCreate cylinder mesh, 64 facets, no end faces, rotate 90d around X axis, scaled on X,Y,Z by 3 to 4. If you switch to orthographic view and try to view the cylinder end on its outline is not visible. You can see the object pivot or center of mass and any manipulation icons but not the object itself. Zooming has no effect. I could discern a couple of pixels sometimes when zooming to try to find the object but it is unknown whether they were part of the cylinder although they did display in the typical orange selection color.\n\nSimply create as described above and the results should be the same. No apparent issues result when same cylinder is created in version 2.79b.\n", "Improve Palette management in Paint Modes (Meshes and Grease Pencil)\nThis is not a task only related to Grease Pencil, but also to any Paint mode.\n\nAs part of the Vertex Paint development in Grease Pencil, we have detected some missing features in Palettes and we have decided to fix it, because Palettes look a little outdate and without improvements for several versions.\n\nMissing features/ WishList:\n\n* There is no default palette.\n* Swatches cannot be re-arranged\n* Colors cannot be sorted\n* Colors can't be named\n* Palettes cannot be merged\n* templatePalette control UI is outdated\n* No ability to import palettes from other software\n* No ability to export palettes to other software\n* Missing easy way to create palettes from images\n\nAbout default palette, in grease pencil we have implemented a default palette similar to Krita/GImp palette. This palette is required by GPencil, but it would be good idea to set this default palette in Texture Paint and Vertex Paint for meshes too.\n\n\nCurrently, I have solved the Sorting, Moving, Join and some Import modules in Grease Pencil branch, but the list above is the initial ideas.", "Semitransparent grease pencil covers wireframe. Bug or limitation?\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nit looks like this \n\n[untitled3.blend](untitled3.blend)\nAnd it is difficuilt sometimes to work with wireframe and GP-sketch when I don`t see vertices\n", "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", "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.", "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.", "Trembling when selected cube in edit mode\nOperating system: MacOS Sierra - Versione 10.12.6\nGraphics card: NVIDIA GeForce GTX 680MX 2048 MB\n\nBroken: 2.83.0 (2020-06-03), 2.90 (2020-06-12)\nWorked: 2.82a\n\nA strange flicker happens when I select the faces of the cube.\n\nI select the cube.\nI change the visualization in Edit Mode.\nI set select mode to Face.\nI select the faces of the cube but they do not remain selected instead, a strange flicker of the object occurs. Here a video example:\n\n[blender_283_bug.mp4](blender_283_bug.mp4)" ]

[ "Mesh appears completely messed up when switching to wireframe with \"draw all edges\" enabled on a skinned mesh\n%%%--- Operating System, Graphics card ---\nMACOS10.8.4\nNVIDIA GeForce GT 650M 512 Mo\n\n - Blender version with error, and version that worked ---\n2.68a\n\n - Short description of error ---\nMesh looks completely messed up when switching to wireframe with \"draw all edges\" enabled. It seems to happen only with an armature-bound mesh. Sometimes (?), maximizing the view (shift+spacebar) fixes the mesh drawing.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\nSelect the geometry and check \"draw all edges\" in object tab\nSwitch to wireframe display\nMay or may not appear broken to you, sounds like a graphics card thing\n\nHadrien\n\n%%%" ]

[ "Wrong initial size in the operator panel if Cylinder object is added through left side tool panel gizmo.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.1.2\n\nI was told to post a bug report in the comments of my question so without further consideration I have done so.\n\nWhen creating a cylinder from the tool menu on the left-hand side of the screen, the dimensions present in the window do not match what was created and manually inputting new dimensions will not result in the correct size, instead seeming to multiply by the existing shape's dimensions.\n\nadd-mesh-cylinder-radius-confusion\n\n\n1. Click create cylinder on left-hand tool menu\n2. Click and drag to create cylinder of any size and depth\n3. The \"Add Cylinder\" panel will always show a radius of 1m and the depth of 2m, and adjusting the values will scale the geometry accordingly as if the gizmo-created cylinder size is the 1m/2m base size.\n\n", "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.", "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", "Creating Lattice object with script with {\"REGISTER\", \"UNDO\"} if parameters was changed in Undo window and mesh was in Edit mode - undo last changes to the mesh or last action\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.1\n\n{\"REGISTER\", \"UNDO\"} also undo last action if parameters was changed in \"Adjust last action\" pannel and mesh was in Edit mode.\n\n[Register_Undo_Issue.mp4](Register_Undo_Issue.mp4)\n\n[REGISTER_UNDO_in_EDIT_Mode.blend](REGISTER_UNDO_in_EDIT_Mode.blend)\n\n", "Geometry node group input for \"Single Value Only\"\nAdd a new \"Single Value Only\" option to node group inputs, only for geometry nodes.\n\nThis would hard-code the non-field status of that input, and remove the \"Use attribute\" toggle in modifier and tool inputs.\n\n", "Measure tool undo repitition\nOperating system: Arch Linux | Kernel: 5.11.8-arch1-1\nGraphics card: GTX 1070\n\nBroken: 2.93.0 alpha | Branch: master | Commit: 715c7462969e6075859f44a64bb4eb68d056345b | Date: Wed Mar 24 11:00:31 2021\nWorked: I also tested it in 2.91 and it is the same issue\n\nIf you draw multiple measurements with the measure tool and then try to undo one it instead undos the two most recent ones. Any further undo's after that will undo one as expected.\n\n1. Use the default startup file\n2. Take out the measure tool\n3. Draw a few lines (more than 1)\n4. Ctrl-z undo (two lines will disappear instead of one)\n5. Ctrl-z undo again (one line will disappear as expected)", "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.", "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.", "full scene copy does not duplicate obdata of objects in Edit mode\nOperating system:\nGraphics card:\n\nBroken: 3.3 LTS and 3.3.1 LTS\n\n\nif you make a full screen copy of a 2D blend file with some objects in edit mode, the objects in edit mode are linked to the original scene i.e.not independent.\n\nCreate a new 2D project and add a blank grease pencil object\nSelect draw mode and add a stroke say a square\nSelect edit mode and select the stroke for point editing\nCreate a full copy of the scene still in edit mode\nMove a point on the selected stroke in the new scene and observe that the same point moves on the original scene. This means the two scenes are linked.\nCarry out the same steps but before creating the new full copy change the mode to object mode.\nagain move one of the points of the stroke in the second scene and note that the object in the original scene does not change i.e. a full copy.\n\nSame is true at least for meshes and curves, so presumably all obdata.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "The bridge tool fails in a situation with multiple rows of faces facing each other\nWin10 Pro 64 bit; AMD Ryzen 2700X; Nvidia GTX 1060 6GB; 32 gigs RAM\n\nBroken: hash d1be30f (buildbot build May 4).\nWorked: never\n\nIn a situation where you have multiple rows of faces that face each other across empty space (with other areas where they face away from each other). The bridge tool (even with*loop pairs* checked) is unable to give priority to the direction the normals are facing. The result of this is that instead of getting nice bridges among the multiple rows of cubes, the tool produces faces that overlap and have zero area. As hinted, the*loop pairs* checkbox in this case does not do anything and the result is the same.\n\nOpen the .blend, invoke the bridge operator (the result is the same whether or not \"loop pairs\" is selected.\n\n**blend**\n[IffyBridge.blend](IffyBridge.blend)\n\n[IffyBridge.blend](IffyBridge.blend) (updated blend)\n\nAn additional note; I submitted this issue years ago, but it was never fixed and I couldn't find my old report. If the bug is not going to be fixed, then just close this as a todo item or with a \"won't fix\" tag.\n", "UI bug in preset window after repeated remove\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0\n\nWhen you remove a preset the textfield with the +/- moves one entry up\n[2022-07-15 09-17-07.mp4](2022-07-15_09-17-07.mp4)\n\n1. Go to the scene tab\n2. Create several new presets\n3. Remove all the new created presets in one go without moving the mouse away.\nI think the textfield with the +/- moves should just stay at the bottom and the window should shrink from the top.", "different Skin Modifier outputs for same mesh\nWindows 10\nNvidia Quadro 600\n\nBroken: 1422f0d\n\nThe skin modifier produces different meshes on the default cube.\n\n\nTrigger the skin modifier to update by doing the same thing I do in the .gif\n\n[skin_modifier_bug.blend](skin_modifier_bug.blend)\n\nNote: this only seems to happen when the edges are orthogonal. When I move one point, the problem doesn't appear on this and connected points.\n\n(Originially reported here: 576)\n", "Certain Float Curve clipping values (e.g. `Min Y -1` together with `Min X 0` & `Max X 0`) break the UI\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\n\nchanging float curve clipping values (e.g. `Min Y -1` together with `Min X 0` & `Max X 0`) break the UI\n\nchange y clipping to -1 then zoom in/out with the magnifier icons:\n\nUI disappears\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)", "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 :)" ]

[ "Drag to select dimensions don't work as expected\n**System Information:**\nCPU: Ryzen 5 2600\nGPU: RX 570 4GB\nOS: Windows 10 Home 64bit\n\n**Blender Version:**\nBroken:\nBlender 2.79b\nBlender 2.79 Master 874f12480f4 (November 24th)\nBlender 2.8 31e3b7790af (November 24th)\n\n**Short description of error:**\nIn the properties panel (N) of the 3D viewport there's three dimension values for a object, X, Y, Z. When two or three values are selected using the \"click and drag over fields\" method and edited, the effects won't take place or incorrect information is displayed.\n\n**Exact steps for others to reproduce the error:**\n1. Open Blender.\n2. Create a 3D object (*I'd recommend the Cude*) and follow one of the \"paths\" listed below.\n\n**Path 1:**\n3. In the properties panel, drag over two or all three of the dimensions variable and type in a value different from the current one and press enter to confirm.\n4. The effects won't take take place.\n\n**Path 2:**\n3. Drag over two or three values in the dimensions tab and drag horizontally to change the values. (E.G. X then Y then Z)\n4. Notice that only two values are changing (X and Z) while the 3D model is only showing the effects of Z being changed. Once the action is confirmed, X will jump back to what it was before modification.\nIn this case, the first selected variable (X) and last selected variable (Z) display a numerical change while the last selected variable (Z) is the only one having an effect on the object.\n\n**Path 3:**\n3. Change the dimensions of the cube to X=2 Y=1 Z=2\n4. Drag over two values (E.G. X then Y) in the dimensions tab and type in a value, E.G. 10, and press enter to confirm.\n5. Both X and Y will change to 2.\nIn this case, no matter what value is input, the second selected value (Y) will change to match that of the first (X) prior to inputs.", "Change of dimensions on multiple axis does not work via N panel\nWindows 10 64b\nGTX 750Ti\n\nBroken: 2.79, Tried also on 2.8 26ee700\nWorked: I think it never worked. I am not sure\n\nYou can change multiple number by click and drag down and than write number you want for all selected fields. It works also for all transforms in N panel in 3D view (i forgot ist name) expect for dimensions. It will just stay whatever it was before. \nFYI: i tried on text for X and Y and it set Y dimension same as X one was. Not what wrote. \n\n- Open defauld scene. \n- select cube\n- pres N\n- select multiple \"2\" in dimension and write something else. \n- after confirmation nothing will change. \n" ]

[ "Regression: broken normal shading, sharp edges appear on smooth surfaces.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: 2.93, version: 3.0.0 Alpha\nWorked: 2.83.9, 2,92\n\nCaused by 1c22b551d0\nTo fix this, 5c4d24e1fd got reverted\nProblem still persists though...\n\n\nIn newer versions normal mapping looks broken, sharp edges appear.\nEevee and Cycles have same bug.\n\nupdated: [untitled.blend](untitled.blend)\n\ndifference in shading\n**2.93 on top, 2.8 down below:**\n\n\nThis effect appears even with very small angle of clean surface (without normal maps)\n\n\n\n<video src=\"2021-05-18_16-17-05.mp4\" title=\"F10122604/2021-05-18_16-17-05.mp4\" controls></video>", "Eevee render display error in orthographic camera mode: Mesh material color changes during scaling \nOperating system: Win7 Home Premium 64-bit, SP1\nGraphics card: Nvidia GeForce GTX 750\n\nBroken: 2.80, c9df453ce70b, blender2.8, 2018-12-21\n2.80, d96596de294e blender2.80, 2018-12-31\n\nWorkspace: Layout\nObject mode\nDisplay rendered view: Eevee (other rendered views with Cycles, etc. do not have this problem)\nCamera orthographic view (!! in perspective or panoramic view, problem is not there)\nCamera type: orthographic\nLight: Sun shining perpendicular onto objects\n\nThree cube mesh objects with individual materials\n- Principled BSDF\n- Base Color (either Red, Green or Blue)\n\nThe *scaling** of one or more objects changes the color appearance in the camera view *and* in rendering.\n\n**scaling*can happen either:\n- pressing 's' key and move mouse\n- changing scale values in transform tab\n\n - > I thought there seemed to be an dependency on scale values. For example, scaling to 1.0 would always be a lighter tone than in a different scaling factor. But simply pressing 's' to scale and escaping can change the color tone of the mesh as well.\n\nThe direction of the sunlight makes of course a difference when viewing the objects, but after changing sunlight angles there is still the color changes during scaling.\n\nBlend file attached.\n\n\n - Select Display render preview \n - Simply choose one or more cubes \n # scale these slowly and the color will change from a fade color to a strong color infrequently\n\nIt seems the problem is the camera orthographic mode!?\n\n[Scale-Color-error.blend](Scale-Color-error.blend)\n", "UV: (investigate) Render UVs of selected object in UV Editor while in Object Mode\nCurrently, the UV Editor only works while in \"Edit\" mode.\n\nHow firm is that restriction?\n\nIt would be nice if we could view UVs in the UV editor, even in \"Object\" mode.\n\nIf would be even nicer if we could use the basic edit tools, such as move, scale and rotate on those UVS, again, even in Object mode.\n\nUVs can be generated and adjusted procedurally, but there's no good way to see them. It would be nice to allow displaying (not editing) evaluated UVs. Combined with features like visualizing overlapping faces, this could save a lot of time.\n\nThis is an *investigate* task, to see if such a thing is even possible. If we discover it's possible, we'll then need to decide if it's desirable.\n\nThanks @BlenderBob for the inspiration!\n\n", "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 ", "GPencil: Average tool in Vertex Paint mode not working as expected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.0 Beta\n\nThe tool paints colors that exist in points far from the brush's area of influence and sometimes paints unexisting colors.\n\n1. Draw simple strokes with the Solid Stroke material.\n2. In VP mode paint half of it orange and half blue.\n3. try the the Average tool in the half blue area then in the other half.\n4. Now do Paint > Reset Vertex Color.\n5. Try the Average tool again.\n\n<video src=\"attachment\" title=\"Vertex Paint Bug-1.mp4\" controls></video>\n\n", "Grease Pencil Color Management inconsistencies\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.81 (sub 14)\nWorked: (optional)\n\nBlender CM for GP is inconsistent between viewport and render. Viewport is not affected by Filmic, but render is.\n\nIn a new file, add a GP Suzanne. Change viewport to RENDERED. Render and compare colors/contrast: they are different.\nChange CM from Filmic to Standard. Render and compare again: they match.\n\n\n\n\n", "Regression: Vertex colors are now broken in hair strands\nOperating system: Gentoo Linux kernel 5.18.0-gentoo\nGraphics card: RX 480\n\nBroken: 3.2.0, 3.3.0\nWorked: 3.1.0\n\nCaused by b9799dfb8a\n\n\nVertex colors are strange and patchy when moving from 3.1.0 to 3.2.0 or later: \n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Make something with vertex colours and a hair system which utilises them in Blender 3.1.0. In my instance I used geometry nodes to generate them; this may differ when making them manually as one of my other projects which does it manually does not seem to exhibit this issue. \n2. Open file in Blender 3.2.0. \n\nI created the following .blend file to demonstrate the issue: [Color_test_3s.blend](Color_test_3s.blend)", "UVEditor: Add developer option to show vertex, edge and poly indexes.\nSimilar to the 3d viewport we should add option to show the vertex, edge and poly indexes to the uv editor.\n\nWithout I have looked to close to the current code-base this should be possible by adding the option to the UVEditor overlay and some tweaks in the overlay engine. \n\nCurrent work-around is to use a split screen.\n\n", "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)", "Improvements to Curve Modifiers (Animation Curves)\nThe intention of this design task is to improve the ways we interact with modifiers amongst multiple curves and other missing options like \"baking\" the result to the curve.\n\nBased on using modifiers for different things myself here is what I feel would be best:\n\n - First thing is to add a new menu under \"channel\" to add any modifier to all the selected/highlighted channels.\n - Also a second option to remove all modifiers from selected/highlighted channels. (as in most cases you'd only add one modifier to a channel).\n - This could be complimented by a remove all modifiers of x type from selected channels.\n - under Shift G (new menu for graph editor) select grouped everywhere else we could have an option to select curves with x type of modifier.\n - Add a naming box with automatic unique names to the curve modifiers in the same fashion as in the object modifiers, this will allow association and the use of \"alt\" for editing multiple modifiers. \n - At the top where the copy / paste modifiers buttons are paste should allow \"alt\" modifier to paste to all selected curves/channels or adding a second paste button that will do just that. \n # Among with the checkbox for activation and the x for modifier deletion a similar menu to this  could be added with the option to apply which should allow animation baking to the curve with simplified version of the \"bake action...\" operator allowing to define the range and steps and to delete or disable the baked modifiers for baking the resulting animation to that curve.\n\nAll of these are up for discussion but I feel it would improve heaps the way we can work with curve modifiers making them super more useful than they are right now because I feel in general people would use them much more if they were easy to handle for more than just one curve at a time.\n\nWhat do you guys think?\n \n\n\n\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", "Intersect Selection in edit mode\nOperating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.3.0 Alpha\n\nIntersect existing Selection apply just to what in the viewport frame \nI can t reproduce it with an exact steps\nopen the linked file and select some vertexes with Select Box and with Intersect Mode\nthe intersection apply just to the vertexes shown in the viewport frame \nsame problem in 2.83 - 3.1 - 3.2\n[bug.blend](bug.blend)", "Path Guiding: Cycles in viewport produce inconsistent results\nOperating system: Windows 11\nGraphics card: Geforce 1660S\n\nBroken: 3.5\n\nJust moving the camera around the viewport gives inconsistent cycles renders. I am not sure if it's directly related to path guiding as the issue is only visible in the mirror caustics.\n\n\n\n\n", "Mark vertices of the active vgroup \nThis is a Follow up Design task for #38573\n\nIdea: When weight-paint colors are enabled with vertex selection (both editmode and weight paint mode), then show vertices in the active vgroup with a different color, even in wireframe mode. this way we can quickly step over vgroups and immediately see which vertices use that group.\n\nExample (mockup):\n\n\n\nAll vertices of the active vgroup are marked in dark pink (just an example). this allows to see in this case there are some stray vertices with zero on the right side of the mesh. \n\nThe markup color for 'vertices in active vgroup' could also be customized in the team settings.", "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" ]

[ "viewport color anomalies/flickering with curves\nOperating system: macOS-12.6.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\nWorked: 3.5.1\nAlso Works Ok 4 alpha \n\nAdding a bezier curve to the scene, entering `edit` mode and grabbing and moving an end or handle of the curve causes the viewport to flicker colors, think aurora borealis , from the curve, and while still in `edit` mode panning, orbiting and zooming quarters of the viewport flick random colors. \n\n[**Based on the default startup** or an attached .blend file (as simple as possible)]\nOpen Blender 3.6.1 \nShift-A -> Curve-> Bezier\nSwitch to `edit` mode\nSelect either end of the curve or a handle \n[G]rab and move handle or end. Doesn't matter where.\nAdditionally Orbiting panning and zooming in `edit` mode causes the issue to become worse.\n\n", "Bezier Curve gizmo artifacts\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.1\nWorked: (Worked in 3.5)\n\nIf I try and edit bezier curves I get these really crazy visual artifacts. Here's a video showing what I'm seeing. This happens if I simply start a new file and add a bezier curve or in more complex scenes.\nview?usp=sharing\n\nAdd a bezier curve, then enter Edit mode, begin editing the curve.\n\n", "Splash screen with black blue color on blender apple silicon LTS 3.6.1. version while using curve pan\nOperating system: macOS Sonoma and Ventura \nGraphics card: M1max \n\n**Blender Version** LTS 3.6.1\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nsplash screen with difference color(black blue, etc) while using the curve pen tool\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. open blender \n2. add a new curve \n3. go to edit mode \n4. select all \n5. delete the original curve \n6. open the curve pen tool and try to draw \n7. error happen\n\n", "Screen is flickering\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.1\n\nWhen I add a curve, it is great now. But when I switch to Edit Mode, the screen is flickering when I do any operation, even include clicking my mouse. \n\nThat happened only when I switch the Edit Mode of the curve. In other mode, it is fine. I have uploaded some images of this error. Check it out!\n\n", "Graphic glitches while editing curves - Apple M2\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 1.2\n\nBroken: version: 3.6.1\nWorked: (3.6)\n\n[When editing a curve there are graphic glitches when one vertex is selected. The viewport flashes random colours, often a quarter of the screen at a time. The glitches happens in all viewport modes.]\n\n[Open a new scene, add any curve object, enter edit mode, select 1 vertex and pan or zoom around, doesn't happen when all vertices are selected]\n\n", "Display artifacts when in curve edit mode and nothing is selected\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\n\n\n\n-----------------------------\n\nWhen there are some unselected vertices there are very quickly and randomly changing artifacts visible\n\n\n\n\n", "Visual glitches when editing Curves on Mac.\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Ultra 1.2\n\nBroken: version: 3.6.1\nWorked: 3.5.1 for sure. Maybe 3.6.0 too but I am not sure.\n\nGlitches appear when editing curves as seen in the demo video.\n\nThe glitch appears only on Metal GPU backend, not with OpenGL\n\nOpen the file and edit the curve with Metal GPU backend active on an m1/m2 computer.\n\n", "When I enter edit mode after creating Bezier Curve, the graphics broke.\nOperating system: Mac OS (MacBook Pro)\nGraphics card: M2 Max (30 Cores)\n\nBroken: 3.6.1, the graphics broke, in Bezier Curve edit mode\nWorked: 3.6.1\n\nI made a Bezier Curve and tried to fix it in Edit Mode, but the graphics are broken. If you select globally, nothing happens, but if you click on each point and act on it to modify the details, you will see that error.\nI use blender in M2 Max MacBook.\n\nAdd Bezier Curve -> Press 'tab' go edit mode -> Click one of dot at Bezier -> Press 'R' or Click 'Mouse center button(wheel) to Navigate View Port -> Can see Broken graphic\n\n", "Glitches when zooming in edit mode\nOperating system: macOS 13.4.1 (22F82) \nGraphics card: Apple M2 Pro\n\nBroken: 13.4.1 (22F82)\n\nsee screen recording\n\n- delete default cube and light\n- add bezier curve\n- go into edit mode\n- use mouse wheel to zoom back and forth\n\n", "Screen flickering when editing a Bézier curve in Edit Mode\nOperating system: macOS-14.0-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.1\n\nScreen flickering when editing a Bézier curve in Edit Mode, as the attached video shows.\n\nI just created a Bézier curve, then entered Edit Mode, and various color blocks start flashing on the screen.\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", "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)", "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", "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", "Cloth simulation randomly breaks down when scrubbing timeline\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2.1\n\nWhen scrubbing the timeline , the cloth simulation may cause the mesh to become distorted even with the existence of cache. The video below will show a quick way to break the simulation, however, I first stumbled upon the problem when I set the keys for the bones.\n\n[2022-07-22 15-48-43.mp4](2022-07-22_15-48-43.mp4)\n\n1. Create cloth simulation.\n2. Scrub the timeline. After some time, a situation will arise where the mesh will be distorted.", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "Edge masking artefacts on higher subdiv levels when removing the mask from lower subdivs\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.90 (sub 2)\n\nThis is a follow-up report on this bug report I made: T76386\n\nTo quickly summarise, there are still masking artefacts that aren't removed when you delete a mask at a lower subdiv level. It only deletes the mask that all subdiv levels share, but in the process the edges of the mask remain at the higer levels because said geometry doesn't exist on the lower levels. This causes problems like these to occur:\n[Desktop 2020.05.17 - 00.35.46.01.mp4](Desktop_2020.05.17_-_00.35.46.01.mp4)\n\n\n1) Take a cube and subdivide it.\n\n2) Go down to level 0 and try to mask the mesh, which will be completely invisible. Then pick any subdiv level above it and mask.\n\n3) Remove the mask at a lower subdiv above level 0 and then move up one level. The mask edges should still be there.\n\n4) Repeat 3) until you reach the highest subdiv level.", "Prompt when entering sculpt mode on non-uniform scaling\n### Motivation\n\nIn the sculpting workflow it is a common step to always apply the scaling of an object so that the tools, brushes and operations work as expected.\nThis is adding extra steps for the user for something that could be automated or fixed. It also confuses most beginners who need to learn this the hard way.\n\n### Proposal\n\nAdd a prompt when entering sculpt mode on an object that has non-unform scaling. This popup will behave similarly to enabling dyntopo while having object data that could be destroyed by using that option:\n\n\nThis popup will ask the user \" Warning!\"\n\"You are entering sculpt mode on an object with non-uniform scaling values. We recommend to apply the scaling of the object before proceeding.\"\n\nIt will then offer 2 options: \"Apply Scale\" which is highlighted and will be used when pressing enter, and \"Don't Apply\" which enters sculpt mode regardless without applying the scale.\n\nIf the scaling is applied the normals should also be recalculated if the scale was negative. This will save the user some trouble of going into edit mode and doing this manually.\n\n### Issues\nCertain bugs would lead to progress being destroyed such as #74361.\nThese need to be resolved first.\n\nAlso ff the user wants to keep the scale intact it will also prompt them every time they enter sculpt mode. Potentially this is not ideal but still better than not having the prompt.", "Most sculpt tools do not work while model is animated\nLinux 64-bit\n2.93.2\nMost sculpt tools do not work as expected when the object is spinning like it's on a pottery wheel. Some tools like the clay tool work okay, but other tools like smooth and scrape do not. I think it has to do with the stroke method; the stroke accounts for screen space but not the local transform of the object if it's moving during a stroke. Video of my attempt here:\n[pottery.mp4](pottery.mp4)\nI made this as a joke and it looks like garbage, but unfortunately it went viral and everybody thinks it's a great idea so now more people are gonna try it and complain that it doesn't work. It's a valid workflow that you have to account for now apparently. I'm really sorry.\n - Open the attached file\n - Play the animation\n # Try to sculpt the thing while it spins\n[bowl.blend](bowl.blend)\n", "Triangle Mesh Transmission Rendering\nOperating system: Linux-5.10.0-12-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.1.0\nWorked: n/a\n\nDear Blender Devs,\n\nthank you very much for this awesome software. I encountered the following problem while working with some imported triangle meshes.\n\nI tried loading a triangle mesh, removing one side using Geometry Nodes and subsequently using the Solidify modifier to give it depth for the transmission rendering. When looking at the rendered view in the viewport, it looked \"fine\". Since I was dealing with a triangle mesh with some weird connectivity I expected there to be some artifacts. See below.\n\nHowever, when I rendered with F12 (optix), the result was completely different to what I saw in the viewport (also optix). See below.\n\nNote the weird artifact at the back of the object in the F12 rendered version. Normally I would attribute this problem to the \"bad\" triangle mesh and just move on with my life. However, because the F12 rendered version produces different results to the viewport rendered version, I assume that there might be a bug somewhere.\n\n\n- Difficult to explain, see the `.blend` file for an example as it seems to be an issue with this specific triangle mesh.\n\n[viewport_f12_problem.blend](viewport_f12_problem.blend)\n", "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)", "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", "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", "Dyntopo: detail flood fill ruins initial curvature\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 17)\n\n\n[2020-05-23_12-30-55.mp4](2020-05-23_12-30-55.mp4)\n[detail flood fill ruins curvature.blend](detail_flood_fill_ruins_curvature.blend)\n\nSubdivide quad shape few times.\nApply Dyntopo flood fill.\nCondition: initial detail density should be higher (2x) than flood details\n", "Redo causes pointy mesh artifacts in Multires\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.90 (sub 0)\n\nIn the new multires, if I sculpt on a level, then subdivide, sculpt on that layer again, then undo to the base level and redo back to the higher levels, it creates a pointy mess in the place of where I'd sculpted.\n[bad undo redo multires.blend](bad_undo_redo_multires.blend)\n[2020-05-02 01-39-06.mp4](2020-05-02_01-39-06.mp4)\n1. Remove default cube, add UV sphere. Go to sculpting workspace. \n2. Add a multires modifier and create a few subdivision levels.\n3. Sculpt on those levels and undo back to the lowest level.\n4. Redo back to the higher levels. Some of those steps would have pointy shapes.\n" ]

[ "clay strip brush (and probably any brush) create some strange shading and geometry artifacts...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\n\nclay strip brush (and probably any brush) create some strange shading and geometry artifacts...\n\n1. open blender, subdivide the default cube in edit mode a few times,\n2. add subdiv modifier with 3 levels (25,1 million in total) and apply modifier.\n3. go to sculpt mode and start playing with the clay strip brush and brush settings a little bit...\n4. change the sculpt plane to view plane, and add a stroke continuously in the edge of the cube, and some transparent shading bug appears when i go to check the back side of the stroke made, but this get fixed when i use the smooth brush a little bit in those boundary edges...\n\n\n5. change the sculpt plane to area plane again, and try on other edge the same again, and some grid topology starts to appear suddenly in the first stroke when drawing, but when i keep drawing it was less noticeable the artifact but was still there...\n\n\n\n" ]

[ "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "Cropping of Emitter (Face) By Hair In Render preview\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90 (sub 2)\nWorked: Never\n\nEverything goes back to working order when I press \"Delete Edit\" for the particles. \nI've tried opening the file on two other computers. On one it works as I'd hope but on the other the same issue occurs. \n\nI haven't ran into this issue before now and I can't replicate it.\n\n[Head Hair Bug.blend](Head_Hair_Bug.blend)\n\n\n\nHope the solution to this is simple and easy. Thank you for constantly making Blender better and better.", "Blender crashes: OpenVDB math::Transform::read throws exception. \nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.2\n\nBlender keeps crashing.\n\nI have a project were I created an animation of modified arrays. Everytime I play it it crashes\n\nCrash report: P1536\n\ncrashed thread: \n```\n\tThread 35 Crashed:\n0 libsystem_kernel.dylib \t0x00007fff726c733a __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff72783e60 pthread_kill + 430\n2 libsystem_c.dylib \t0x00007fff7264e8a2 __abort + 139\n3 libsystem_c.dylib \t0x00007fff7264e817 abort + 135\n4 libc++abi.dylib \t0x00007fff6f8ae458 abort_message + 231\n5 libc++abi.dylib \t0x00007fff6f89f8bf demangling_terminate_handler() + 262\n6 libobjc.A.dylib \t0x00007fff713da5b1 _objc_terminate() + 104\n7 libc++abi.dylib \t0x00007fff6f8ad887 std::__terminate(void (*)()) + 8\n8 libc++abi.dylib \t0x00007fff6f8b01a2 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27\n9 libc++abi.dylib \t0x00007fff6f8b0169 __cxa_throw + 113\n10 org.blenderfoundation.blender \t0x0000000110291c61 openvdb::v7_0::math::Transform::read(std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 4801\n11 org.blenderfoundation.blender \t0x000000011026082b openvdb::v7_0::io::Archive::readGrid(std::__1::shared_ptr<openvdb::v7_0::GridBase>, openvdb::v7_0::io::GridDescriptor const&, std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 1787\n12 org.blenderfoundation.blender \t0x0000000110286589 openvdb::v7_0::io::File::Impl::unarchive(openvdb::v7_0::io::File const&, std::__1::shared_ptr<openvdb::v7_0::GridBase>&, openvdb::v7_0::io::GridDescriptor const&, openvdb::v7_0::io::File::Impl::NoBBox) + 57\n13 org.blenderfoundation.blender \t0x0000000110282c91 openvdb::v7_0::io::File::readGridByName(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, openvdb::v7_0::math::BBox<openvdb::v7_0::math::Vec3<double> > const&) + 465\n14 org.blenderfoundation.blender \t0x0000000110282ab6 openvdb::v7_0::io::File::readGrid(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 54\n15 org.blenderfoundation.blender \t0x00000001128a2cc9 MANTA::updateGridFromVDB(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 361\n16 org.blenderfoundation.blender \t0x0000000112890985 MANTA::updateGridFromFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 869\n17 org.blenderfoundation.blender \t0x0000000112890cee MANTA::updateNoiseStructures(FluidModifierData*, int) + 558\n18 org.blenderfoundation.blender \t0x000000011287e2b5 manta_update_noise_structures + 21\n19 org.blenderfoundation.blender \t0x000000010df34cd0 BKE_fluid_modifier_processDomain + 3168\n20 org.blenderfoundation.blender \t0x000000010df316ce BKE_fluid_modifier_do + 142\n21 org.blenderfoundation.blender \t0x000000010e3ad4f6 applyModifier + 54\n22 org.blenderfoundation.blender \t0x000000010dea5b0a mesh_calc_modifiers + 2778\n23 org.blenderfoundation.blender \t0x000000010dea4d6b mesh_build_data + 123\n24 org.blenderfoundation.blender \t0x000000010dea4035 makeDerivedMesh + 133\n25 org.blenderfoundation.blender \t0x000000010dfe1281 BKE_object_handle_data_update + 1089\n26 org.blenderfoundation.blender \t0x000000010dfe1704 BKE_object_eval_uber_data + 52\n27 org.blenderfoundation.blender \t0x000000010e9f36ba DEG::(anonymous namespace)::deg_task_run_func(TaskPool*, void*, int) + 138\n28 org.blenderfoundation.blender \t0x00000001142cadbc task_scheduler_thread_run(void*) + 364\n29 libsystem_pthread.dylib \t0x00007fff72784109 _pthread_start + 148\n30 libsystem_pthread.dylib \t0x00007fff7277fb8b thread_start + 15\n```\n", "Crash 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 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.", "Crash while baking the Line Art modifier\nOperating system: Windows 11\nGraphics card: RTX 2070\n\nBroken: 7c2dc5183d03\n\n\n\nI get regular crashes when baking Line Art modifier in relatively complicated geometries. \n\nI can't provide my project file. I am hoping that the crash log will give insight into this bug.\n\n", "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)", "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", "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", "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", "Suspected asset library crash by `json_sax_dom_parser`\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nI dont completely know why but blender crashes very often for me.\nIts doing something no idea what it is doing.\nSorry for being vague, but it seems to mostly happen when i have the viewport set to cycles render and i am trying to modify materials, in the shader editor.\n\n", "Blender crash in bmesh.to_mesh() while using it to modify weights\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nCrash in bmesh.to_mesh() if using it to modify weights in weightpainting while playing animation\n\n*Remove any lights or cameras, keep just one cube in the scene (for the simple script to work).\n*Subdivide it 5 times and apply the modifier.\n*Add the script below to the script editor and run it\n*Go to weight paint mode for the cube\n*Run the animation and try to paint. If you just click the left mouse button it will paint a dot and the script will work, but if you hold and drag, Blender crashes.\n\n\n```\nimport bpy, bmesh\n\n\ndef add_handler():\n # remove existing handlers\n old_handlers = []\n for h in bpy.app.handlers.frame_change_post:\n if \"paint_test\" in str(h):\n old_handlers.append(h)\n for h in old_handlers: bpy.app.handlers.frame_change_post.remove(h)\n # add new handler\n bpy.app.handlers.frame_change_post.append(paint_test)\n\ndef paint_test(scene):\n for ob in scene.objects:\n me = ob.data\n \n print(str(scene.frame_current) + \": Creating Bmesh\")\n bm = bmesh.new()\n bm.from_mesh(me)\n \n group_index = ob.vertex_groups.active_index\n dvert_lay = bm.verts.layers.deform.active\n \n for vert in bm.verts:\n dvert = vert[dvert_lay]\n try: dvert[group_index] -= 0.1\n except: pass \n \n print(str(scene.frame_current) + \": Writing Bmesh\")\n bm.to_mesh(me)\n bm.free()\n \nadd_handler()\n```", "Particles from multiple systems disappear when all Physics Type are None.\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.81a\n\nWhen selecting a Particle System, all particles of the object disappear.\nImages showing before and after:\n\n\n\n- In the default cube add two particle systems.\n- Set the `Frame End` of both to 1 for better observation.\n- In the `Physics` tab of both choose `Physics Type` `None`.\n- Select any of the particle systems, note that the particles disappear.\n\nAttached file contains an example of multiple particle system on one object:\n[LP_grass.blend](LP_grass.blend)\n\nThis has to be the first file you open with the application.\nIf you open blender and enable the eevee material preview for example with the default cube and open the example file afterwards it works.", "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)", "Regression: Mesh render artifacts\nOperating system: Windows 10\nGraphics card: GTX 1070 TI\n\nBroken: 3.1, 3.6\nWorked: (3.0.1)\n\nNormals on hair mesh is corrupted in newer versions of blender while being perfect in older ones.\nMesh name is LOD0_1_front_hair_omote597.\n\n- Open the attached .blend file\n- View the model/mesh in normals/ambient occlusion render pass (cycles)\n\n" ]

[ "Creating 2 Particle systems breaks the app\nOperating system: Ryzen 7\nGraphics card: RX Vega 56\n\nBroken: 2.80 beta closes the app\n\nWorked: (optional)\n\nCreating second particle systems shut down the app. \n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. create a plane\n2. subdivide it 100 times\n3. add textures\n4. upload file with rocks (and add them to new collection)\n5. use them as Hair particles\n6. Set them the way i needed\n7. Upload anothe file with 1 rock\n8. create new collection for it\n9. choose terrain and add one more particle system\n10. breaks the app", "Blender 2.80 crashes on adding object instancing and hair particle system together\nHi everyone !\nSorry if this has already been reported, feel free to merge with duplicate or ask for more infos =D\nThanks !\n\nOperating system: Microsoft Windows 10 x64\nGraphics card: Nvidia GTX 1050 Ti Max-Q\n\nBroken: 2.80 Beta, e4dbfe0a98c1, 2018-12-26, branch 2.7\n\nBlender 2.80 crashes when a mesh object with instancing object is set (frames, verts or faces, else than none) and a hair particle system is added. It also crashes vice-versa, when a hair particle system is set and some object instancing is added.\nIf not a typical or intended action, blender should not crash but instead display an error message.\n\n\n- open blender with defaults and factory settings\n- in layout workspace, select the default cube in the 3d view editor\n- in the properties editor, go to object tab and change object instancing from \"none\" to either \"frames, verts or faces\"\n- then go to particles tab, click \"new\" for adding a particle system and change type from \"emitter\" to \"hair\"\nNote that the last two steps can be interverted (first add the hair particle system then instancing), the crash occurs anyway\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.", "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", "Metal: Display of bones in stick mode wrong\nOperating system: macOS M2 Ventura 13.2.1\nGraphics card: M2 GPU\n\nBroken: 3.5.1 and newer\nWorked: with OpenGL backend (see #109389, #108620)\n\n\nBones in Edit mode are displayed wrong when bone display type is set to Stick. In Blender 3.3.7 it looked as usual (see first image). In Blender 3.5.1 and in branch 'blender-v3.6-release' (after calling git pull and rebuilding) it seems broken (second image).\n\nBased on the default startup:\n1. Create a new Armature.\n2. Enter Edit mode.\n3. Set bone display mode to Stick.\nBones are displayed in black (second image).", "Orbit around selection not working with modifers in edit mode\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.40\n\nBroken: version: 2.92.0\n\n\nWhen \"orbit around selection\" is turned on in the preferences the viewport usually rotates around the selected object - for example a selected vertex.\nIf the objects geometry is influenced by a modifier, though, the viewport does not rotate around the modifieds position of the vertex but still around the original position of the vertex. This can be very limiting, esspecially when using heavily deformed meshes which is often the case when using lattices.\n\n1. Preferences -> Navigation -> check \"Orbit Around Selection\"\n2. create Cube\n3. put simple Deform Modifier on Object\n4. In the modifier next to the Camera and Viewport Display icons press the \"Edit Mode\" icon and the \"On Cage\" icons. (see image)\n5. Select a single vertex of the Cube and rotate the viewport\n6. The viewport does not rotate around the vertex.\n\n\n\n\n", "Animation: Circle & Lasso select does not work correctly on bones with custom shapes\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3060 Ti\n\nBroken: 3.3.1\nWorked: Unknown\n\n\nUsing circle or lasso select to select bones with custom shapes does not work correctly. It seems to pick against the actual bone shape instead of the custom bone shape. It's interesting to note that box select seems to work fine here.\n\n[circleselectcustombones.mp4](circleselectcustombones.mp4)", "Bone drivers do not copy when duplicated\nMac OSX 10.9.5 and NVIDIA GeForce GTX 470\n\nBroken: 2.77 (sub 3)\nWorked: ?\n\nIf a bone has any driver (on constraint or property) and it is duplicated (shift D in edit mode or \"symmetrize\") the drivers are not copied.\n\nBone constraints, however, copy perfectly and also try to find the correct .L or .R target if applicable.\nThis would save a lot of time if the drivers worked in the same way.\n", "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", "Knife Tool produces bad geometry in certain cases (disconnected edges/vertices, overlapping faces)\nif i use tools knife i see this bug.\n\n\n\n", "Select Grouped by Armature (option for pose / edit mode of armatures)\nProblem:\nWith the coming of editing and animating multiple armatures in blender which has been great, new needs come into play like selecting all the bones on a particular armature when you are in pose mode with more than just one of them\n\nSolution:\nAdd “by armature” operator in “select grouped by” (shift g) which will allow you to select a control from a particular armature and add all of that armature to the selection even if you are in posemode with several other armatures too.", "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", "Text Object - Edit Mode - Special Characters - Circle and Promille doesn't get created\nOperating system and graphics card\n\nNivida 760 GTX, Win 7, 64 Bit, german\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\nBlender 2.79\n\n\nText Object - Edit Mode - Special Characters, the Special characters Circle and Promille doesn't get created when i choose them. \n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n\nCreate a new scene. Create a text object. Insert special character promille, insert special character circle.\n\nThey should create. But here nothing happens then. There is no warning. The Info editor tells me the characters are created. But the characters are simply missing in the text.\n\nThe list in the Info editor seems also to have some flaws at displaying what character gets created. Two characters shows an empty string in the brackets. One shows the common square for a not found ascii character.\n\nMaybe this is because of my german Windows 7 64 Bit Home , with american keyboard layout removed.\n\nExample images and a file is attached.\n\n\n[missingcharacters.blend](missingcharacters.blend)\n\n\n\n\n", "Armature > Symmetrize doesn't symmetrize Inverse Kinematics constraints correctly\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.93.0\nWorked: non\n\nWhen one Armature > Symmetrize a bone, the IK constraints aren't correctly symmetrized. For example, IK constraint Limit Z (Min -180°, Max 10°) is symmetrized as (Min -180°, Max 10°), while the proper symmetrized result should be (Min -10°, Max 180°). Note that this behavior is inconsistent with how Limit Rotation constraint works. When using Armature > Symmetrize, Limit Rotation Z (Min -180°, Max 10°) is symmetrized as (Min -10°, Max 180°), which in my opinion, is the correct result.\n\n\n1. Create an armature\n2. Create a bone at (1, 0, 0)\n3. Set Bone Properties > Inverse Kinematics > Limit Z (Min -180°, Max 10°)\n4. Enter Edit Mode\n5. Armature > Symmetrize\n\n", "Broken Twist on meshes deformed with Particle Instance Modifier with Along Path\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.90.1\n\nThe twist of a mesh deformed with the Particle Instance Modifier with the Along Path option seems broken, more noticeable with steep curvature in hairs. I compare it to the Curve Deform modifier as an example of proper deformation. Now, you may say it's an unfair comparison given that curves have an explicit twist that you can modify, unlike hairs. But even without controlling the initial twist of the hair, it's broken in a couple of ways.\n\nFirst, it deforms the mesh unevenly, with some vertices twisting more than others, even in a case where vertices are completely equidistant around the origin and both origins are aligned, like the cube in this image. The selected face and the edgeloop here should be squares but aren't, unlike in the curve deform modifier \nSecond, when changing the length with the Position Slider, the whole thing seems to change twist at once. Instead of having a consistent twist on each point of the path [Particle Instance Mod bug2.mp4](Particle_Instance_Mod_bug2.mp4)\nAs a side note, when using Along Path, finding how to orient your mesh to the hair is unintuitive, always using the global Y axis as the length axis in which I added subdivisions but then twisting weirdly when changing the Axis option in the modifier, I settled for Z in this example.\n\n\nAttached is the same file used in the video, you can open it and move the Position slider in the Particle Instance Modifier, the scale of the Curve Deform modifier example is driven by it so you can see both changing in real time.\n\n[ParticleInstanceTwistBug.blend](ParticleInstanceTwistBug.blend)\n\nWhy do I think this is happening? Well, if you select the object with the particle system, go to the particle properties, and change the length of the hair under the Render>Timing>End subpanel, you can see the problem is the same, basically the twist changes with length. Maybe the modifier should do something different and get the twist from the whole length particle and then scale the mesh instance before deforming or something like that, idk\n\n", "Rotate bone snapping\nBroken: version: 3.2.0 Alpha\nWorked: -\n\nCannot rotate one bone (in edit or pose mode) to point at a target (any).\n\n- Open attached file or:\n - make an armature\n - edit mode\n - add bone (2 bones total)\n - move and rotate both bones off origin\n - turn on snap, snap to vertex, affect rotate\n - pivot on active element or individual origins\n - edit mode or pose mode\n- try to align one bone to point at the other bone head\n[snap_rotate_bug.blend](snap_rotate_bug.blend)", "Add cube\" wrong representation of Z-extrusion (Not a bug Just little correction)\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.93.0\n\n\"Add cube\" wrong representation of Z-axis direction\n\nNot an error but an incorrect representation of object depth creation while using \"Add cube\" function.\n\n\n\n" ]

[ "Armature display issues with Intel 5x0 GPU\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Intel(R) HD Graphics 530 Intel 4.4.0 - Build 20.19.15.4285\n\nBroken: version: 2.81 (sub 10)\n\nWhen creating an armature, the mesh that should be inside the bones is displayed in the opposite direction and always starting at the origin. When adding bones they continue the armature, but the mesh still starts at the origin. \nThat only applies to the forms Octahedral and B-Bones. Custom bone shapes are affected as well, they work with no form.\nCustom bones do work when Viewport Display is set to wireframe.\n\nNote: \nwe tested to export this to another pc and there the bug did not occure. \nWhen testing from the other pc back with a non-corupt file it did occure.\n\n\n*Open new Blender File and add Armature.\nOr\n*open attached File\n\n[Bones_Display_Bug.blend](Bones_Display_Bug.blend)\n\n\n\n\n\n\n\n\nThank You!" ]

[ "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.", "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)", "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.", "Metal: Assert is triggered when drawing a Batch with an attribute format different from the type used in the Shader\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: [couldn't check yet]\n\nI'm not sure how serious the problem is.\nEven with the assert, the drawing seems to work.\nBelow is a small code that demonstrates the problem:\n\n```python\nimport bpy\nimport gpu\nfrom gpu.types import (\n GPUBatch,\n GPUIndexBuf,\n GPUVertBuf,\n GPUVertFormat,\n)\n\ndef draw():\n x1=0\n y1=0\n x2=bpy.context.region.width\n y2=bpy.context.region.height\n\n # The size of each color in `vertex_colors` needs to be 4 and\n # the size of each vector in `vertices` needs to be 3\n # otherwise a assert will be triggered the Metal backend.\n vertex_colors = ((1.0, 0.0, 0.0, 1.0), (1.0, 1.0, 1.0, 1.0))\n vertices = ((x1, y1), (x2, y2))\n\n shader = gpu.shader.from_builtin('POLYLINE_SMOOTH_COLOR')\n shader.uniform_float(\"viewportSize\", gpu.state.viewport_get()[2:])\n shader.uniform_float(\"lineWidth\", 5)\n\n vbo_format = GPUVertFormat()\n vbo_format.attr_add(id='color', comp_type='F32', len=len(vertex_colors[0]), fetch_mode='FLOAT')\n vbo_format.attr_add(id='pos', comp_type='F32', len=len(vertices[0]), fetch_mode='FLOAT')\n\n vbo = GPUVertBuf(vbo_format, len(vertices))\n vbo.attr_fill('color', vertex_colors)\n vbo.attr_fill('pos', vertices)\n\n batch = GPUBatch(type='LINE_STRIP', buf=vbo)\n batch.draw(shader)\n del batch\n\n\nbpy.types.SpaceView3D.draw_handler_add(draw, (), 'WINDOW', 'POST_PIXEL')\n\n```\n\nNote that the dimension of the vertices is 2D.\nIf converted to 3D (by adding a z value), the assert is no longer triggered.\n\n- Open attached .blend file.\n- Run the script in the text editor\n- Update the 3D view (by zooming for example)\n\n[gpu_metal_assert__bug.blend](attachment)\n\n", "Missing icons for the release\nThere are typically a few new features for each release that need an icon. We can collect them here and make sure they are added before the release (before Bcon3 really).\n\nCurrently missing:\n\n- [x] Geometry Nodes Editor\n- [x] Line art modifier\n- [ ] Attribute domains {[F10162715](image.png) size=full}\n - Face corner icon is using a node snapping icon\n - Points probably shouldn't have a line\n - An icon for curve control points would be great\n- [ ] Asset icon (? Could re-use the Asset Browser icon, but rather have a dedicated one)\n- [ ] Asset Browser \"Unassigned\" catalog item\n- [ ] Asset Browser \"All\" catalog tree item (? Could also just be a regular parent item)\n- [ ] Asset Browser \"Open Blend File\" button\n\n- [x] Blender File (`FILE_BLEND` currently uses the Blender logo, which is wrong)\n\n**Sculpt tools:**\n*Postponed for the next release.*\n* - [ ] ~~Mask Filter Tool~~\n* - [ ] ~~Scene Project Brush Tool~~", "Array modifier is crazy, when using \"object offset\" pointed to empty, which is parented to curve\nOperating system: Mac OS Catalina 10.15.4 (latest)\nGraphics card: Intel HD 6000\n\nBroken: 2.83 beta as of 8-th of May\n\nArray modifier is crazy, when using \"object offset\" pointed to empty, which is parented to curve. And when the CURVE CONVERTED TO MESH -- it just destroys scale of object!\n\n1) Open .blend\n[plants.blend](plants.blend)\n2) Try to move empty -- everything works fine\n3) Select \"empty\" and \"petals\" (with shift) then parent them (Ctrl + P -- to object) to \"bezier curve\"\n4) Select bezier curve and \"convert to mesh\"\n5) Now try to move empty\n\nBefore:\n\nAfter:\n", "UVEditor: Add developer option to show vertex, edge and poly indexes.\nSimilar to the 3d viewport we should add option to show the vertex, edge and poly indexes to the uv editor.\n\nWithout I have looked to close to the current code-base this should be possible by adding the option to the UVEditor overlay and some tweaks in the overlay engine. \n\nCurrent work-around is to use a split screen.\n\n", "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", "UV Editor and Image Edito:- Assigning shortcuts to Annotate tools go in wrong section of keymap\nOperating system: Windows 10\n\n2.92.0, 02948a2cab44, master, 2021-04-24, as found on the splash screen\n\nFor the `Image Editor`, when assigning shortcuts to the 4 annotation tools (listed below), their shortcuts (Set Tool by Name) are getting registered in `\"Preferences > Keymap > Window\"` instead of their respective sections.\nWhen assigned the shortcuts from the `UV Editor` first, the shortcuts go correctly to `\"Preferences > Keymap > Image > UV Editor > UV Editor (Global)\"`\nMaybe both should go to `\"Preferences > Keymap > Image > Image (Global)\"`?\n\n- Go to Image Editor\n- Right click each of the tools below and assign a random shortcut (Z, R, T, L for example)\n - Annotate\n - Annotate Line\n - Annotate Polygon\n - Annotate Eraser\nThey are now listed under `\"Preferences > Keymap > Window\"`, which is not where they should be.", "Rendered Object Blurs if Auto Smooth Normals Turned On or Edge Split Modifier is Added\nOperating system: macOS Monterey Version 12.3.1\n\nGraphics card: Intel Iris Plus Graphics 1535 MB\n\n(Though I ran this animation though SheepIt Render Farm (animation below), and just about all the frames had the bug.)\n\nBroken: Blender 3.0.1 and Blender 3.2.1.\nWorked: Never\n\n\nObject looks blurry if Auto Smooth Normals is turned on or and Edge Split Modifier is added. \n\n\n\n\n\nIt looks fine Auto Smooth Normals turned off and no Edge Split Modifier (doesn't look as good in many cases). \n\n\n\nOf if you apply the Edge Split Modifier (looks fine in this case, but not ideal as it's a destructive process). \n\n\n\nHere's the bug in a video render:\n\n[V02 Vid0001-0065.mp4](V02_Vid0001-0065.mp4)\n\nObject is parented to a bone, which has a Child Of constraint of a different armature's bone. (As a test, I created another armature with a single bone, and switched the Child Of constraint to this new armature, and the bug still happened.) \n\n\n[Testing Area V1.blend](Testing_Area_V1.blend)\nUse the attached stripped down Blend file. \nTurn on Auto Smooth Normals or add an Edge Split Modifer and then render. \n", "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", "Copy/Paste Behavior in Viewport\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M390 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15\n\nBroken: version: 2.91.0 Alpha\nWorked: Never worked in 2.8+\n\nWhen pasting an object, the gizmo is not positioned at the newly created object, where you would expect it to be. Instead, there are two cases - both seem to be not intended.\nThe pasted object also is not active for direct manipulation despite the visual indication with the gizmo.\n\nIf there is a selection somewhere else before pasting, the gizmo ends up in the wrong position. Example:\n\n\nIf there is no selection before pasting, there is no gizmo appearing at all. Example:\n\n\nA directly interconnected problem is that pasted objects are not made active despite having an attached Gizmo. Example:\n\n\n**Potential fix**\n1. The gizmo could always appear and show where the object is pasted (belonging to the new object).\n2. The pasted object could become active. When multiple objects are pasted, the selection and active states of the copied objects could be transferred to the newly pasted ones. Also, all previous selections could be deselected after pasting.\n\nThank you :)\n", "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)", "Knife Tool / Knife Project: Vertex group weights not added/interpolated for KnifeVerts created in faces (works correctly on verts created on existing/split edges)\nWin7 32bit\n\nBroken: 3.4\nBroken: 2.78\n\nKnife Tool / Knife Project: Vertex group weights not added/interpolated for KnifeVerts created in faces (works correctly on verts created on existing/split edges)\n\n- create a plane\n- subdivide once\n- add a vertexgroup (all vertices with 1.0 weight)\n- use the knife tool (or Knife Project operator)\n- notice where existing edges are split, vertex weights are added/interpolated to new verts on that edge\n- newly created verts inside faces are not added to vertex groups though\n[#50604.webm](T50604.webm)\n\n\n**Original Report**\nLast cutting was done by simple Knife to show the difference\n[0001-0324.mp4](0001-0324.mp4)\n\nIn .Blend hit *Knife project*\n[Knife_project.blend](Knife_project.blend)\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." ]

[ "Unexpected results when exporting from Blender as an ,obj . When importing back into a blender file.\nOperating system and graphics card Win 64 Ultimo embarrassed to say GTX 280 \n\nBroken: (example: 2.69.7 4b206af, see splash screen) Offical 2.74 000dfc0\nWorked: (optional)\n\n**Short description of error** Imported .obj has excessive sharpening of edges over and above those wanted.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n\nPlease view video by pasting the following in to new browser widow to see what I'm encountering, there is sound. 6zlRWDItElJd and hit enter.\n\nI will also append the blend file if I can work out how. \n\n[Bottle_Opener_Bottom_6.0.6.blend](Bottle_Opener_Bottom_6.0.6.blend)" ]

[ "Normal Map gets inverted in Edit mode\nOperating system: Linux-5.3.0-7642-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 13)\n\nFor some reason having material shading enabled and entering edit mode inverts the normal map.\n[2020-04-14 14-01-54.mp4](2020-04-14_14-01-54.mp4)\n\n1. Open the file [bug.blend](bug.blend)\n2. Enable Material Preview\n3. Switch between Edit mode and object mode\n\n", "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", "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", "Regression: Boolean Modifier Distorts UVs\nBroken: Blender 3.2.2 Official\nBroken: 2.93\nWorked: 2.92\n\nBroke with a3f091d7ce\n\n\nBoolean modifier distorts UVs of cutter object. In the attached screenshot and blend file. There are two cutters objects of roughly the same shape, one of them works correctly and the other doesn't.\n\n\n\n[tmp_2.blend](tmp_2.blend)", "Scene strips don't include passes\nOperating system: Linux-5.8.11-1-MANJARO-x86_64-with-glibc2.32 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.8.11-1-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.1.8\n\nBroken: from 2.79 to version: 2.92.0 Alpha\nWorked: -\n\nThe render passes of another scene (as scene strip) are ignored in the master scene.\nThis will most probably be categorized as limitation. Since it is a severe one, it should at least be documented here:\nPagename: `video_editing/sequencer/strips/scene`\n\nName current scene \"A\", create new scene, in the sequencer add scene strip for \"A\", hit F12\nThe content of scene \"A\" will be rendered, but the Z channel (enabled by default / other channels if activated) of scene \"A\" will not be rendered, the Select Pass dropdown is not there and the layers are not saved to multilayerEXR.\n\n", "AVI Raw index corrupted\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0\nWorked: Never\n\nRendering AVI RAW file will create file with invalid or corrupted index. This seems to happen only with 3840x2160 resolution.\n\n\n[#80482.blend](T80482.blend)\n\n- Open file\n- Render animation\n- Open rendered file in VLC\n", "Using the alpha channel of an image texture corrupts RGB Channels in both EEVEE and cycles\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\nUsing the alpha channel of an image texture affects RGB Channels in both EEVEE and Cycles when connecting the alpha channel to another arbitrary node.\n\n\n- See attached .blend files for Eevee and for Cycles\n\n|Blender file that demonstrates that behavior in EEVEE:|The same behavior manifests itself a little differently in Cycles:\n| -- | -- |\n|[Plane_test_file_EEVEE.blend](Plane_test_file_EEVEE.blend)|[Plane_test_file_cycles.blend](https://archive.blender.org/developer/F12860576/Plane_test_file_cycles.blend)\n\n\nAs it seems connecting the alpha channel somehow unpremultiplies the image.\nAll images are stored as openexr, the image alpha is therefore set as premultiplied.", "Viewport Shading 'Attribute' Option Broken for Instanced Geometry\nOperating system: Windows 10\nGraphics card: Nvidia GTX 2080\n\nBroken: 3.5\nWorked: 3.4, 3.4.1\n\nWhen instancing a mesh to another meshes vertices, the Solid Viewport Color Option 'Attribute' is no longer displaying the vertex color data.\n\nCreate A Sphere, and using \"Vertex Paint Mode\" Paint a color onto the sphere.\nUsing geometry nodes set up the following, Group Input (Geometry) -> Mesh to points - > Instance on points -> Realize Instances -> Output (Geometry)\nSet a simple sphere as the object to be instanced.\nSet Shading mode to 'Solid'.\nToggle 'Attribute'\n\n", "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", "Texture Paint - bad behaving operator \"Save All Images\"\nGo to Texture Paint Mode with some Textures loaded. In T-Panel go to the Slots Tab. There you will find a Button labeled \"Save All Images\". However, do not push this Button !\nThis Button overwrites all involved/edited Textures in the Texture Paint Slots at once and instantly, without further inquiry, to the directory of the origins.\n\nIt's not a bug, it's working pretty well !\n\n \n", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "Viewport view resets after navigating within the Camera view\nOperating system: Pop!_Os 20.04\nGraphics card: Nvidia GTX 1080ti\n\nBroken: 3.0 Beta, 7a5b8cb20284, master, 2021-11- 05, 2.83, 2.79... etc\nWorked: Has never worked\n\nWhen navigating in camera view, if the user goes back to Viewport view it will reset the Viewport back to the world origin\n\n- New File\n- Add Camera\n- Navigate anywhere in Viewport view\n- Go into Camera view\n- Navigate again inside Camera view (use walk navigation)\n- Go back into Viewport view\n- Viewport will reset back to world origin\n\nNOTE: this only happens if you navigate inside the camera, if you go back to Viewport view using the middle mouse button it wont happen\n\n| Blender 3.0 | 2.83.16 | 2.79 |\n| -- | -- | -- |\n| [Peek 2021-11-07 04-54.mp4](Peek_2021-11-07_04-54.mp4) | [Peek 2021-11-07 05-05.mp4](Peek_2021-11-07_05-05.mp4) | [Peek 2021-11-07 05-09.mp4](Peek_2021-11-07_05-09.mp4) |\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)", "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", "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)" ]

[ "Environment Pass does not work with \"Persistent Data\" turned on\nOperating system: Windows 10\nGraphics card: Zotac gtx 1080\n\nBroken 3.0 a6f275cad3\nWorked 2.92\n\nEnvironment pass will create artifacts or black screen output if \"persistent data\" is turned on.\n\n[Bug_persistentdata_envoirement.blend](Bug_persistentdata_envoirement.blend)\n\n- Open file\n- Render image (see black background - env pass is black)\n- Uncheck Persistent Data\n- Render image\n\nBackground is now correct.\n" ]

[ "GUI: The curser is heavily lagging if GSync is set to windowed and full screen mode\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: Blender 2.79b up to Blender 3.0.0\n\nEverything is as expected if the mode is set to \"Fullscreen only\" (the default)\nBut as soon as you set to it to \"Window- and Fullscreen mode\" the mouse curser will lag heavily.\n\n\n1. Enable GSync\n2. Set it to \"Enable for windowed and full screen mode\"\n3. Save\n4. Open Blender and move the curser\n\n**Workaround** \nJust set it back to full screen mode only.\nOR\nIf you go to nVidia Control Panel > Manage 3d Settings > Program Settings.\n\nAdd Blender under Select Program To Customize. Changing to the following settings can fix it:\n\nMonitor Technology: Fixed Refresh\nPreferred Refresh Rate: Application-controlled\n\n**Desired behavior** \nA fluid curser on the screen even with \"windowed and full screen mode\" enabled", "Particles animation dont show\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nemitter particles animation don't show movement when i press G shortcut to move the model that contain the particles but they don't show any movement, so i can't do an autokeying animation whit the desire movement of the mouse.\n\nadd a cube, put particle emitter, press space bar and G key to move, the particles don't show movement only flickering.\n", "Render animation cycles-x bug March 11, 2022\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nRender count from 1 to 1200 frames\n\n\nBlender 3.2.0 Alpha within Cycles-x\nPush the 'Command + F12\" and render animation cause bug between start to end (855 - 1200 frames)\n\nBlender and video file: [Blender 3-2-0 by Kent Davis March 11 2022.zip](Blender_3-2-0_by_Kent_Davis_March_11_2022.zip)\n\n\n\n\n\n\n\nRadeon Pro 575:\n\n```\nChipset Model:\tRadeon Pro 575\nType:\tGPU\nBus:\tPCIe\nPCIe Lane Width:\tx16\nVRAM (Total):\t4 GB\nVendor:\tAMD (0x1002)\nDevice ID:\t0x67df\nRevision ID:\t0x00c4\nROM Revision:\t113-D000AA-931\nVBIOS Version:\t113-D0001A1P-025\nEFI Driver Version:\t01.00.931\nMetal Family:\tSupported, Metal GPUFamily macOS 2\nDisplays:\n```\niMac:\n```\nDisplay Type:\tBuilt-In Retina LCD\nResolution:\tRetina 5K (5120 x 2880)\nFramebuffer Depth:\t30-Bit Color (ARGB2101010)\nMain Display:\tYes\nMirror:\tOff\nOnline:\tYes\nAutomatically Adjust Brightness:\tNo\nConnection Type:\tInternal\n```\n\n", "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.", "OptiX denoiser creates dark artifacts in viewport when used with 2 GPUs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.3.1\n\nThe OptiX denoiser creates several black sectors in the viewport. The smaller the area to be cleaned the more visible the error is.\nThis is only present when I have my 2 GPUs activated at the same time (3070 and 2060s). And it works normally when I enable only one of them.\n\n\n\n1. Activate both GPUs in preferences (OptiX or CUDA)\n2. Select Cycles render > GPU\n3. Activate viewport denoise and select OptiX.\n4. In viewport (Ctrl + B) set a small render region.\n[Based on the default startup]\n\n", "CPU + GPU render precision differences for small, far away area light\nOperating system: Linux-4.19.0-5-amd64-x86_64-with-debian-10.0 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74\n\nBroken: version: 2.81 (sub 8)\nWorked: (optional)\n\nThis was recently reported in this thread : \n2\n\n I can at least say, that when using small area lights below a size of 1 (e.g. meter), and it’s getting darker (the light source is far away from the object) you can clearly see this problem: CPU renders the tiles darker than the CUDA GPU.\n\n\n\nCreate a new scene with the cube, remove the default light, create an area light, resize it to lets say 10% (or 1%… the smaller the bigger the effect) and rotate it that it lights the default cube.\nHere is a .blend that reproduce the issue :\n[TileProblem.blend.blend](TileProblem.blend.blend)\n\n", "CUDA problem Error: Invalid value in cuMemcpy2DUnaligned_v2(&param)\ndoes anybody know what this error mean (blender 3.5, 3.6, 4.0 win 11):\n\n*Error:Report:\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\n\n\nWe tried two rtx 4070ti video cards and this error came up when we were about to render. If I disable one of the two, the render runs fine, but if I enable both, the render freezes. I see that it starts using both, but it still gives an error.\n\nThanks\n\n", "Add-on preferences panel should open on activation\nBroken: 2.78 testbuild 1\n\n\n**Description of issue**\nAccording to the [new protocols for add-ons](Add-ons#New_Protocols), certain add-ons need more actions from the user than simple activation, before they do anything. This is an excerpt from the pie menu example:\n\n* With Pie menus, First you activate the addon & nothing happens!\n* You need to expand the Addons Preferences.\n* From here you can individually activate the menus you like to use. \n\nThis is bad UI design, as it requires the user to *know* that activating the add-on does nothing. Blender also requires them to click a button that doesn't appear any different than before (and thus doesn't visually indicate there is something else to see there now).\n\n**Possible solution**\nAutomatically opening the add-on's preferences panel when it is activated would help a lot. At least this allows the user to see that there are options to inspect, and possibly activate.\n", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n", "Preferences window lags with add-ons preferences UI raises an exception\nOperating system: Windows 10 1903\nGraphics card: GTX970\n\nBroken: blender-2.80-9c5d54bfaf48-win64\nWorked:blender-2.80-8ac0fef4dfd1-win64\n\n\nWhen you click on a triangle in the addons list which is corresponds to an addon which contains VISIBLE_IPO_ON in code, it starts to incredibly lag. Seriously, one frame per second or two. Everything is quick and snappy until you press that goddam triangle. After that whole Preferences window behave like this till the restart of Blender. Other windows are unaffected.\nObserve: \nwatch?v=9fObpt0L8B0\n\nIn a log I can see a long and sad error: Traceback (most recent call last):\n```\nFile \"C:\\Users\\ostap\\AppData\\Roaming\\Blender Foundation\\Blender\\2.80\\scripts\\addons\\DECALmachine\\ui\\UILists.py\", line 16, in draw_item\n row.prop(item, \"isvisible\", text=\"\", icon=isvisibleicon, emboss=False)\n```\nTypeError: UILayout.prop(): error with keyword argument \"icon\" - enum \"VISIBLE_IPO_ON\" not found in ('NONE', 'QUESTION', 'ERROR', 'CANCEL', 'TRIA_RIGHT', 'TRIA_DOWN', 'TRIA_LEFT', 'TRIA_UP', 'ARROW_LEFTRIGHT', 'PLUS', 'DISCLOSURE_TRI_RIGHT', 'DISCLOSURE_TRI_DOWN', 'RADIOBUT_OFF', 'RADIOBUT_ON', 'MENU_PANEL', 'BLENDER', 'GRIP', 'DOT', 'COLLAPSEMENU', 'X', 'DUPLICATE', 'TRASH', 'COLLECTION_NEW', 'NODE', 'NODE_SEL', 'WINDOW', 'WORKSPACE', 'RIGHTARROW_THIN', 'BORDERMOVE', 'VIEWZOOM', 'ADD', 'REMOVE', 'PANEL_CLOSE', 'COPY_ID', 'EYEDROPPER', 'AUTO', 'CHECKBOX_DEHLT', 'CHECKBOX_HLT', 'UNLOCKED', 'LOCKED', 'UNPINNED', 'PINNED', 'SCREEN_BACK', 'RIGHTARROW', 'DOWNARROW_HLT', 'FCURVE_SNAPSHOT', 'OBJECT_HIDDEN', 'PLUGIN', 'HELP', 'GHOST_ENABLED', 'COLOR', 'UNLINKED', 'LINKED', 'HAND', 'ZOOM_ALL', 'ZOOM_SELECTED', 'ZOOM_PREVIOUS', 'ZOOM_IN', 'ZOOM_OUT', 'DRIVER_DISTANCE', 'DRIVER_ROTATIONAL_DIFFERENCE', 'DRIVER_TRANSFORM', 'FREEZE', 'STYLUS_PRESSURE', 'GHOST_DISABLED', 'FILE_NEW', 'FILE_TICK', 'QUIT', 'URL', 'RECOVER_LAST', 'THREE_DOTS', 'FULLSCREEN_ENTER', 'FULLSCREEN_EXIT', 'LIGHT', 'MATERIAL', 'TEXTURE', 'ANIM', 'WORLD', 'SCENE', 'OUTPUT', 'SCRIPT', 'PARTICLES', 'PHYSICS', 'SPEAKER', 'TOOL_SETTINGS', 'SHADERFX', 'MODIFIER', 'BLANK1', 'FAKE_USER_OFF', 'FAKE_USER_ON', 'VIEW3D', 'GRAPH', 'OUTLINER', 'PROPERTIES', 'FILEBROWSER', 'IMAGE', 'INFO', 'SEQUENCE', 'TEXT', 'SOUND', 'ACTION', 'NLA', 'PREFERENCES', 'TIME', 'NODETREE', 'CONSOLE', 'TRACKER', 'ASSET_MANAGER', 'NODE_COMPOSITING', 'NODE_TEXTURE', 'NODE_MATERIAL', 'UV', 'OBJECT_DATAMODE', 'EDITMODE_HLT', 'UV_DATA', 'VPAINT_HLT', 'TPAINT_HLT', 'WPAINT_HLT', 'SCULPTMODE_HLT', 'POSE_HLT', 'PARTICLEMODE', 'TRACKING', 'TRACKING_BACKWARDS', 'TRACKING_FORWARDS', 'TRACKING_BACKWARDS_SINGLE', 'TRACKING_FORWARDS_SINGLE', 'TRACKING_CLEAR_BACKWARDS', 'TRACKING_CLEAR_FORWARDS', 'TRACKING_REFINE_BACKWARDS', 'TRACKING_REFINE_FORWARDS', 'SCENE_DATA', 'RENDERLAYERS', 'WORLD_DATA', 'OBJECT_DATA', 'MESH_DATA', 'CURVE_DATA', 'META_DATA', 'LATTICE_DATA', 'LIGHT_DATA', 'MATERIAL_DATA', 'TEXTURE_DATA', 'ANIM_DATA', 'CAMERA_DATA', 'PARTICLE_DATA', 'LIBRARY_DATA_DIRECT', 'GROUP', 'ARMATURE_DATA', 'COMMUNITY', 'BONE_DATA', 'CONSTRAINT', 'SHAPEKEY_DATA', 'CONSTRAINT_BONE', 'CAMERA_STEREO', 'PACKAGE', 'UGLYPACKAGE', 'EXPERIMENTAL', 'BRUSH_DATA', 'IMAGE_DATA', 'FILE', 'FCURVE', 'FONT_DATA', 'RENDER_RESULT', 'SURFACE_DATA', 'EMPTY_DATA', 'PRESET', 'RENDER_ANIMATION', 'RENDER_STILL', 'LIBRARY_DATA_BROKEN', 'BOIDS', 'STRANDS', 'LIBRARY_DATA_INDIRECT', 'GREASEPENCIL', 'LINE_DATA', 'LIBRARY_DATA_OVERRIDE', 'GROUP_BONE', 'GROUP_VERTEX', 'GROUP_VCOL', 'GROUP_UVS', 'FACE_MAPS', 'RNA', 'RNA_ADD', 'MOUSE_LMB', 'MOUSE_MMB', 'MOUSE_RMB', 'MOUSE_MOVE', 'MOUSE_LMB_DRAG', 'MOUSE_MMB_DRAG', 'MOUSE_RMB_DRAG', 'PRESET_NEW', 'DECORATE', 'DECORATE_KEYFRAME', 'DECORATE_ANIMATE', 'DECORATE_DRIVER', 'DECORATE_LINKED', 'DECORATE_LIBRARY_OVERRIDE', 'DECORATE_UNLOCKED', 'DECORATE_LOCKED', 'DECORATE_OVERRIDE', 'TRACKER_DATA', 'HEART', 'ORPHAN_DATA', 'USER', 'SYSTEM', 'SETTINGS', 'OUTLINER_OB_EMPTY', 'OUTLINER_OB_MESH', 'OUTLINER_OB_CURVE', 'OUTLINER_OB_LATTICE', 'OUTLINER_OB_META', 'OUTLINER_OB_LIGHT', 'OUTLINER_OB_CAMERA', 'OUTLINER_OB_ARMATURE', 'OUTLINER_OB_FONT', 'OUTLINER_OB_SURFACE', 'OUTLINER_OB_SPEAKER', 'OUTLINER_OB_FORCE_FIELD', 'OUTLINER_OB_GROUP_INSTANCE', 'OUTLINER_OB_GREASEPENCIL', 'OUTLINER_OB_LIGHTPROBE', 'OUTLINER_OB_IMAGE', 'RESTRICT_COLOR_OFF', 'RESTRICT_COLOR_ON', 'HIDE_ON', 'HIDE_OFF', 'RESTRICT_SELECT_ON', 'RESTRICT_SELECT_OFF', 'RESTRICT_RENDER_ON', 'RESTRICT_RENDER_OFF', 'RESTRICT_INSTANCED_OFF', 'OUTLINER_DATA_EMPTY', 'OUTLINER_DATA_MESH', 'OUTLINER_DATA_CURVE', 'OUTLINER_DATA_LATTICE', 'OUTLINER_DATA_META', 'OUTLINER_DATA_LIGHT', 'OUTLINER_DATA_CAMERA', 'OUTLINER_DATA_ARMATURE', 'OUTLINER_DATA_FONT', 'OUTLINER_DATA_SURFACE', 'OUTLINER_DATA_SPEAKER', 'OUTLINER_DATA_LIGHTPROBE', 'OUTLINER_DATA_GP_LAYER', 'OUTLINER_DATA_GREASEPENCIL', 'GP_SELECT_POINTS', 'GP_SELECT_STROKES', 'GP_MULTIFRAME_EDITING', 'GP_ONLY_SELECTED', 'GP_SELECT_BETWEEN_STROKES', 'MODIFIER_OFF', 'MODIFIER_ON', 'ONIONSKIN_OFF', 'ONIONSKIN_ON', 'RESTRICT_VIEW_ON', 'RESTRICT_VIEW_OFF', 'RESTRICT_INSTANCED_ON', 'MESH_PLANE', 'MESH_CUBE', 'MESH_CIRCLE', 'MESH_UVSPHERE', 'MESH_ICOSPHERE', 'MESH_GRID', 'MESH_MONKEY', 'MESH_CYLINDER', 'MESH_TORUS', 'MESH_CONE', 'MESH_CAPSULE', 'EMPTY_SINGLE_ARROW', 'LIGHT_POINT', 'LIGHT_SUN', 'LIGHT_SPOT', 'LIGHT_HEMI', 'LIGHT_AREA', 'CUBE', 'SPHERE', 'CONE', 'META_PLANE', 'META_CUBE', 'META_BALL', 'META_ELLIPSOID', 'META_CAPSULE', 'SURFACE_NCURVE', 'SURFACE_NCIRCLE', 'SURFACE_NSURFACE', 'SURFACE_NCYLINDER', 'SURFACE_NSPHERE', 'SURFACE_NTORUS', 'EMPTY_AXIS', 'STROKE', 'EMPTY_ARROWS', 'CURVE_BEZCURVE', 'CURVE_BEZCIRCLE', 'CURVE_NCURVE', 'CURVE_NCIRCLE', 'CURVE_PATH', 'LIGHTPROBE_CUBEMAP', 'LIGHTPROBE_PLANAR', 'LIGHTPROBE_GRID', 'COLOR_RED', 'COLOR_GREEN', 'COLOR_BLUE', 'TRIA_RIGHT_BAR', 'TRIA_DOWN_BAR', 'TRIA_LEFT_BAR', 'TRIA_UP_BAR', 'FORCE_FORCE', 'FORCE_WIND', 'FORCE_VORTEX', 'FORCE_MAGNETIC', 'FORCE_HARMONIC', 'FORCE_CHARGE', 'FORCE_LENNARDJONES', 'FORCE_TEXTURE', 'FORCE_CURVE', 'FORCE_BOID', 'FORCE_TURBULENCE', 'FORCE_DRAG', 'FORCE_SMOKEFLOW', 'RIGID_BODY', 'RIGID_BODY_CONSTRAINT', 'IMAGE_PLANE', 'IMAGE_BACKGROUND', 'IMAGE_REFERENCE', 'NODE_INSERT_ON', 'NODE_INSERT_OFF', 'NODE_TOP', 'NODE_SIDE', 'NODE_CORNER', 'SELECT_SET', 'SELECT_EXTEND', 'SELECT_SUBTRACT', 'SELECT_INTERSECT', 'SELECT_DIFFERENCE', 'ALIGN_LEFT', 'ALIGN_CENTER', 'ALIGN_RIGHT', 'ALIGN_JUSTIFY', 'ALIGN_FLUSH', 'ALIGN_TOP', 'ALIGN_MIDDLE', 'ALIGN_BOTTOM', 'BOLD', 'ITALIC', 'UNDERLINE', 'SMALL_CAPS', 'HOLDOUT_OFF', 'HOLDOUT_ON', 'INDIRECT_ONLY_OFF', 'INDIRECT_ONLY_ON', 'CON_CAMERASOLVER', 'CON_FOLLOWTRACK', 'CON_OBJECTSOLVER', 'CON_LOCLIKE', 'CON_ROTLIKE', 'CON_SIZELIKE', 'CON_TRANSLIKE', 'CON_DISTLIMIT', 'CON_LOCLIMIT', 'CON_ROTLIMIT', 'CON_SIZELIMIT', 'CON_SAMEVOL', 'CON_TRANSFORM', 'CON_TRANSFORM_CACHE', 'CON_CLAMPTO', 'CON_KINEMATIC', 'CON_LOCKTRACK', 'CON_SPLINEIK', 'CON_STRETCHTO', 'CON_TRACKTO', 'CON_ARMATURE', 'CON_CHILDOF', 'CON_FLOOR', 'CON_FOLLOWPATH', 'CON_PIVOT', 'CON_SHRINKWRAP', 'MODIFIER_DATA', 'MOD_WAVE', 'MOD_BUILD', 'MOD_DECIM', 'MOD_MIRROR', 'MOD_SOFT', 'MOD_SUBSURF', 'HOOK', 'MOD_PHYSICS', 'MOD_PARTICLES', 'MOD_BOOLEAN', 'MOD_EDGESPLIT', 'MOD_ARRAY', 'MOD_UVPROJECT', 'MOD_DISPLACE', 'MOD_CURVE', 'MOD_LATTICE', 'MOD_TINT', 'MOD_ARMATURE', 'MOD_SHRINKWRAP', 'MOD_CAST', 'MOD_MESHDEFORM', 'MOD_BEVEL', 'MOD_SMOOTH', 'MOD_SIMPLEDEFORM', 'MOD_MASK', 'MOD_CLOTH', 'MOD_EXPLODE', 'MOD_FLUIDSIM', 'MOD_MULTIRES', 'MOD_SMOKE', 'MOD_SOLIDIFY', 'MOD_SCREW', 'MOD_VERTEX_WEIGHT', 'MOD_DYNAMICPAINT', 'MOD_REMESH', 'MOD_OCEAN', 'MOD_WARP', 'MOD_SKIN', 'MOD_TRIANGULATE', 'MOD_WIREFRAME', 'MOD_DATA_TRANSFER', 'MOD_NORMALEDIT', 'MOD_PARTICLE_INSTANCE', 'MOD_HUE_SATURATION', 'MOD_NOISE', 'MOD_OFFSET', 'MOD_SIMPLIFY', 'MOD_THICKNESS', 'MOD_INSTANCE', 'MOD_TIME', 'MOD_OPACITY', 'REC', 'PLAY', 'FF', 'REW', 'PAUSE', 'PREV_KEYFRAME', 'NEXT_KEYFRAME', 'PLAY_SOUND', 'PLAY_REVERSE', 'PREVIEW_RANGE', 'ACTION_TWEAK', 'PMARKER_ACT', 'PMARKER_SEL', 'PMARKER', 'MARKER_HLT', 'MARKER', 'KEYFRAME_HLT', 'KEYFRAME', 'KEYINGSET', 'KEY_DEHLT', 'KEY_HLT', 'MUTE_IPO_OFF', 'MUTE_IPO_ON', 'DRIVER', 'SOLO_OFF', 'SOLO_ON', 'FRAME_PREV', 'FRAME_NEXT', 'NLA_PUSHDOWN', 'IPO_CONSTANT', 'IPO_LINEAR', 'IPO_BEZIER', 'IPO_SINE', 'IPO_QUAD', 'IPO_CUBIC', 'IPO_QUART', 'IPO_QUINT', 'IPO_EXPO', 'IPO_CIRC', 'IPO_BOUNCE', 'IPO_ELASTIC', 'IPO_BACK', 'IPO_EASE_IN', 'IPO_EASE_OUT', 'IPO_EASE_IN_OUT', 'NORMALIZE_FCURVES', 'VERTEXSEL', 'EDGESEL', 'FACESEL', 'CURSOR', 'PIVOT_BOUNDBOX', 'PIVOT_CURSOR', 'PIVOT_INDIVIDUAL', 'PIVOT_MEDIAN', 'PIVOT_ACTIVE', 'CENTER_ONLY', 'ROOTCURVE', 'SMOOTHCURVE', 'SPHERECURVE', 'INVERSESQUARECURVE', 'SHARPCURVE', 'LINCURVE', 'NOCURVE', 'RNDCURVE', 'PROP_OFF', 'PROP_ON', 'PROP_CON', 'PROP_PROJECTED', 'PARTICLE_POINT', 'PARTICLE_TIP', 'PARTICLE_PATH', 'SNAP_OFF', 'SNAP_ON', 'SNAP_NORMAL', 'SNAP_GRID', 'SNAP_VERTEX', 'SNAP_EDGE', 'SNAP_FACE', 'SNAP_VOLUME', 'SNAP_INCREMENT', 'STICKY_UVS_LOC', 'STICKY_UVS_DISABLE', 'STICKY_UVS_VERT', 'CLIPUV_DEHLT', 'CLIPUV_HLT', 'SNAP_PEEL_OBJECT', 'GRID', 'OBJECT_ORIGIN', 'ORIENTATION_GLOBAL', 'ORIENTATION_GIMBAL', 'ORIENTATION_LOCAL', 'ORIENTATION_NORMAL', 'ORIENTATION_VIEW', 'COPYDOWN', 'PASTEDOWN', 'PASTEFLIPUP', 'PASTEFLIPDOWN', 'VIS_SEL_11', 'VIS_SEL_10', 'VIS_SEL_01', 'VIS_SEL_00', 'AUTOMERGE_OFF', 'AUTOMERGE_ON', 'UV_VERTEXSEL', 'UV_EDGESEL', 'UV_FACESEL', 'UV_ISLANDSEL', 'UV_SYNC_SELECT', 'GIZMO', 'ORIENTATION_CURSOR', 'NORMALS_VERTEX', 'NORMALS_FACE', 'NORMALS_VERTEX_FACE', 'SHADING_BBOX', 'SHADING_WIRE', 'SHADING_SOLID', 'SHADING_RENDERED', 'SHADING_TEXTURE', 'OVERLAY', 'XRAY', 'LOCKVIEW_OFF', 'LOCKVIEW_ON', 'AXIS_SIDE', 'AXIS_FRONT', 'AXIS_TOP', 'NDOF_DOM', 'NDOF_TURN', 'NDOF_FLY', 'NDOF_TRANS', 'LAYER_USED', 'LAYER_ACTIVE', 'SORTALPHA', 'SORTBYEXT', 'SORTTIME', 'SORTSIZE', 'SHORTDISPLAY', 'LONGDISPLAY', 'IMGDISPLAY', 'BOOKMARKS', 'FONTPREVIEW', 'FILTER', 'NEWFOLDER', 'FILE_PARENT', 'FILE_REFRESH', 'FILE_FOLDER', 'FILE_BLANK', 'FILE_BLEND', 'FILE_IMAGE', 'FILE_MOVIE', 'FILE_SCRIPT', 'FILE_SOUND', 'FILE_FONT', 'FILE_TEXT', 'SORT_DESC', 'SORT_ASC', 'LINK_BLEND', 'APPEND_BLEND', 'IMPORT', 'EXPORT', 'LOOP_BACK', 'LOOP_FORWARDS', 'BACK', 'FORWARD', 'FILE_CACHE', 'FILE_VOLUME', 'FILE_3D', 'FILE_HIDDEN', 'FILE_BACKUP', 'DISK_DRIVE', 'MATPLANE', 'MATSPHERE', 'MATCUBE', 'MONKEY', 'HAIR', 'ALIASED', 'ANTIALIASED', 'MAT_SPHERE_SKY', 'MATSHADERBALL', 'MATCLOTH', 'MATFLUID', 'WORDWRAP_OFF', 'WORDWRAP_ON', 'SYNTAX_OFF', 'SYNTAX_ON', 'LINENUMBERS_OFF', 'LINENUMBERS_ON', 'SCRIPTPLUGINS', 'SEQ_SEQUENCER', 'SEQ_PREVIEW', 'SEQ_LUMA_WAVEFORM', 'SEQ_CHROMA_SCOPE', 'SEQ_HISTOGRAM', 'SEQ_SPLITVIEW', 'IMAGE_RGB', 'IMAGE_RGB_ALPHA', 'IMAGE_ALPHA', 'IMAGE_ZDEPTH', 'VIEW_PERSPECTIVE', 'VIEW_ORTHO', 'VIEW_CAMERA', 'VIEW_PAN', 'VIEW_ZOOM', 'BRUSH_BLOB', 'BRUSH_BLUR', 'BRUSH_CLAY', 'BRUSH_CLAY_STRIPS', 'BRUSH_CLONE', 'BRUSH_CREASE', 'BRUSH_FILL', 'BRUSH_FLATTEN', 'BRUSH_GRAB', 'BRUSH_INFLATE', 'BRUSH_LAYER', 'BRUSH_MASK', 'BRUSH_MIX', 'BRUSH_NUDGE', 'BRUSH_PINCH', 'BRUSH_SCRAPE', 'BRUSH_SCULPT_DRAW', 'BRUSH_SMEAR', 'BRUSH_SMOOTH', 'BRUSH_SNAKE_HOOK', 'BRUSH_SOFTEN', 'BRUSH_TEXDRAW', 'BRUSH_TEXFILL', 'BRUSH_TEXMASK', 'BRUSH_THUMB', 'BRUSH_ROTATE', 'GPBRUSH_SMOOTH', 'GPBRUSH_THICKNESS', 'GPBRUSH_STRENGTH', 'GPBRUSH_GRAB', 'GPBRUSH_PUSH', 'GPBRUSH_TWIST', 'GPBRUSH_PINCH', 'GPBRUSH_RANDOMIZE', 'GPBRUSH_CLONE', 'GPBRUSH_WEIGHT', 'GPBRUSH_PENCIL', 'GPBRUSH_PEN', 'GPBRUSH_INK', 'GPBRUSH_INKNOISE', 'GPBRUSH_BLOCK', 'GPBRUSH_MARKER', 'GPBRUSH_FILL', 'GPBRUSH_ERASE_SOFT', 'GPBRUSH_ERASE_HARD', 'GPBRUSH_ERASE_STROKE', 'SMALL_TRI_RIGHT_VEC', 'KEYTYPE_KEYFRAME_VEC', 'KEYTYPE_BREAKDOWN_VEC', 'KEYTYPE_EXTREME_VEC', 'KEYTYPE_JITTER_VEC', 'KEYTYPE_MOVING_HOLD_VEC', 'HANDLETYPE_FREE_VEC', 'HANDLETYPE_ALIGNED_VEC', 'HANDLETYPE_VECTOR_VEC', 'HANDLETYPE_AUTO_VEC', 'HANDLETYPE_AUTO_CLAMP_VEC', 'COLORSET_01_VEC', 'COLORSET_02_VEC', 'COLORSET_03_VEC', 'COLORSET_04_VEC', 'COLORSET_05_VEC', 'COLORSET_06_VEC', 'COLORSET_07_VEC', 'COLORSET_08_VEC', 'COLORSET_09_VEC', 'COLORSET_10_VEC', 'COLORSET_11_VEC', 'COLORSET_12_VEC', 'COLORSET_13_VEC', 'COLORSET_14_VEC', 'COLORSET_15_VEC', 'COLORSET_16_VEC', 'COLORSET_17_VEC', 'COLORSET_18_VEC', 'COLORSET_19_VEC', 'COLORSET_20_VEC', 'EVENT_A', 'EVENT_B', 'EVENT_C', 'EVENT_D', 'EVENT_E', 'EVENT_F', 'EVENT_G', 'EVENT_H', 'EVENT_I', 'EVENT_J', 'EVENT_K', 'EVENT_L', 'EVENT_M', 'EVENT_N', 'EVENT_O', 'EVENT_P', 'EVENT_Q', 'EVENT_R', 'EVENT_S', 'EVENT_T', 'EVENT_U', 'EVENT_V', 'EVENT_W', 'EVENT_X', 'EVENT_Y', 'EVENT_Z', 'EVENT_SHIFT', 'EVENT_CTRL', 'EVENT_ALT', 'EVENT_OS', 'EVENT_F1', 'EVENT_F2', 'EVENT_F3', 'EVENT_F4', 'EVENT_F5', 'EVENT_F6', 'EVENT_F7', 'EVENT_F8', 'EVENT_F9', 'EVENT_F10', 'EVENT_F11', 'EVENT_F12', 'EVENT_ESC', 'EVENT_TAB', 'EVENT_PAGEUP', 'EVENT_PAGEDOWN', 'EVENT_RETURN')\n\nAnd after changing VISIBLE_IPO_ON/OFF to HIDE_OFF/ON in the mentioned file issue disappears. Of course you may say that it's the issue with an un-updated addons. but that's weird. when Blender starts to misbehave instead of showing error message about the issue, isn't it?\n\n1. Open any scroll of the addon with VISIBLE_IPO_ON in it. \n2. Enjoy the performance. ", "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>", "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", "Cycle CPU + GPU hybrid path tracer\nThe main idea of CPU + GPU path tracer is to have two full size accumulation/render buffers. A unit of work is a single tile (the same size as the frame buffer) with a varying number of samples to render for each scheduled task. \n\nTwo accumulation threads, one for the CPU and one for the GPU, run almost independently until the sum of samples has reached the number of required samples (the threads have to synchronize on the number of rendered samples and the offset for random number generation). \n\nOn every execution, each processor renders the amount of sample that is most suited to its capabilities. The initial number of samples assigned for the GPU is higher than the one assigned to the CPU. As mor rendering information becomes available, the number of samples per device is determined based on the number of samples it can process within an update interval. Only GPU thread updates the display while the rendering is still in process. It allows for more flexibility to determine the launch frequency/number of samples on the CPU device. When all samples are rendered, the two buffers are merged, to produce the final output (the overhead of this method). \n\n```\n\n```\n\nThis is a preliminary and quick implementation, without software design consideration, as a proof of concept to show the benefit of distributing work on two processors with significant capability differences. The implementation has limited support. It is configured to work only on a single GPU + a single CPU, with no support for adaptive sampling, tiling, or offline rendering to name a few. \n```\n\n```\n\nThis version does not consist of new methods for sample distribution of scheduled tasks and is not optimized to its full potential. \n\n", "PBVH task scheduler performance issues\nThis is a task to investigate a possible issue in the PBVH task scheduler. \n\n**Issues**\n - Some users report bad performance in sculpt mode, while others can work without problems on really high poly meshes with similar hardware.\n\n - On my main computer, brush strokes with TBB disabled feel more responsive regardless the mesh vertex count. When TBB is enabled, strokes usually stop generating new samples in the middle of the stroke or take a fraction of a second to start. I know this is happening to some other users. \n\n - Simple operations that need to loop over all vertices on high poly meshes are extremely slow for no specific reason. (doing x = 1.0f - x on a 25M elements array often takes up to 5 seconds). When the operation is more complex (like updating the normals or updating the nodes on the GPU), this can take minutes to finish. \n\nWe are not getting the reports of people that may be affected by this issue because most of them assume that Blender sculpt mode performance is just bad by default, so I can't tell if this is a problem with a specific configuration of hardware/software or a general problem in how the scheduler works. It would be nice to have more data from this test (and sculpt mode performance in general) on different hardware/software configurations to have a better understanding of how we can improve it. \n\n**How to test:**\n\n - Apply this patch: [P1202](P1202.txt)\n - Add a cube, subdivide N number of times and apply\n - Enter Sculpt Mode\n - Run \"Invert Mask\" (press A + drag left)\n\n\n**My results**\n\nOperating system: Linux-5.4.2-1-MANJARO-x86_64-with-glibc2.29 64 Bits\nCPU: Intel i7 6700K @ 4.00GHz x 8\nRAM: 32GB\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nSubdivide default cube N number of times:\n\n| N Subdivisions | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|--------------|----------|------------|------------------|-------------------|---------|\n| 11 | 25165826 | 7596 | 2.474073 | 0.571511 | 432.90% |\n| 10 | 6291458 | 1920 | 0.307948 | 0.159395 | 193.20% |\n| 9 | 1572866 | 464 | 0.111459 | 0.096845 | 115.09% |\n| 8 | 393216 | 112 | 0.002289 | 0.007297 | 31.37% |\n\n\nSubdivide default cube 6 times, use multires to N level.\n\n| Level | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|-------|----------|------------|------------------|-------------------|---------|\n| 6 | 26763264 | 3696 | 1.076635 | 0.322183 | 334.17% |\n| 5 | 7102464 | 912 | 0.074586 | 0.113303 | 65.83% |\n| 4 | 1990656 | 232 | 0.012938 | 0.048273 | 26.80% |\n| 3 | 614400 | 56 | 0.004059 | 0.012778 | 31.77% |\n\n\nAs you can see, a simple loop over all vertices in the mesh is way faster on my setup with TBB disabled.\n\nIf I change the ##LEAF_LIMIT## in ##pbvh.c## to 100000 (x10) in order to increase the amount of work each node has and reduce the number of total nodes: \n\n| N Subdivisions | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|--------------|----------|------------|------------------|-------------------|--------|\n| 11 | 25165826 | 760 | 0.106868 | 0.210985 | 50.65% |\n| 10 | 6291458 | 184 | 0.029088 | 0.105376 | 27.60% |\n| 9 | 1572866 | 56 | 0.007168 | 0.029653 | 24.17% |\n| 8 | 393216 | 8 | 0.002261 | 0.006321 | 35.77% |\n\nIf we compare the two results with TBB on:\n\n| Vertices | 1000 LEAF_LIMIT (default) | 10000 LEAF_LIMIT (new) | Perf. gain |\n|----------|-----------------|------------------|------------|\n| 25165826 | 2.474073 | 0.106868 | 2315.07% |\n| 6291458 | 0.307948 | 0.029088 | 1058.68% |\n| 1572866 | 0.111459 | 0.007168 | 1554.95% |\n| 393216 | 0.002289 | 0.002261 | 101.24% |\n\nIt seems like if we avoid starting TBB with a large number of nodes the performance improvement is huge. Increasing the leaf limit makes these kinds of operations up to 23 times faster, but that would be like disabling multithreading for small brush strokes.\n\n- Is there a way to fix this in the scheduler?\n- Can we do something like sending small chunks of nodes to TBB instead of starting the loop with 7000 nodes at the same time?\n- Can we find a better optimal leaf limit to get a better workload per core suitable for modern processors by comparing the results on different hardware? Dyntopo leaf limit is in 100 elements, which I think it does not make much sense. ", "(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" ]

[ "GPU devices not reported correctly\nelementaryOS 0.4.1, GTX 1080\n\nBroken: 2.79 e32c1bd)\nWorked: (2.79)\n\nThe CUDA devices are not reported properly by C.user_preferences.addons['cycles'].preferences.devices. It labels the wrong card as display. I guess it happened when GPU+CPU was introduced recently.\n\nProbably you need a multiGPU setup. If you compare the settings in user-preferences with what the python console is reporting, there seems to be a mismatch. \nThe display in my computer is only connected to the GTX980 Ti, correctly reported by user-prefs, but not py Python.\nSee screenshot:\n\n" ]

[ "Bevel modifier - Clamp Overlap broken\nWindows 10\n\nBroken: 2.79.0-git.43a6cf1-windows64\nWorked: 2.79 RC2\n\n\n\nSee attached blend file.[clamp.blend](clamp.blend)", "Multi-Object-Mode: Operators that need refactor on their logic\nSome operators are working for multiple-object editing however are still not fully benefiting from it.\nThe most common case is that the operator works but only if all the objects have the same transformation matrix.\n\n* **~~MESH_OT_select_similar~~** (SIMEDGE_FACE_ANGLE, SIMFACE_AREA, SIMFACE_PERIMETER). 0c1934f3c2\n\n* **MESH_OT_knife_project** and **MESH_OT_knife_tool**.\nNeed to convert the code from screen space to world space. More details on [D3637](D3637).\n\n* **UV_OT_weld** (UV_STRAIGHTEN, UV_STRAIGHTEN_X, UV_STRAIGHTEN_Y).\nThe current logic to determine the first and last selected vertex is not very compatible with multi-object. We should be able to select vertices from different objects, and use their position to determine the line extremes.\n\n* **LATTICE_OT_flip**\nThe axis need to be in world space, not local space.\n\n* **~~CURVE_OT_select_similar~~** (SIMCURHAND_DIRECTION). ab77f5b5fe\nNeed to calculate direction taking scale into consideration.", "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", "Inconsistent Limitations of Instances in Geometry Nodes\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nIt's not clear what operations can or can't be done to an instance, eg. Extrude and Scale Element, Dual Mesh, Triangulate etc all work fine but Set Position doesn't. \n\nSorry for the complex file but I wanted to leave in all the nodes I'd been through before realising that I was working an Instance still.\nThe Set Position node was the first one in that line that gave me any indication that I was still on an instance.\n\n[12 Marching Squares.blend](12_Marching_Squares.blend)\n", "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", "Shortcut detection problem for tablet user\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\n\nThere are 2 types of shortcuts in Blender.\n1. General shortcuts that work regardless of the location of the mouse pointer. such as 'Ctrl+S'\n2. Window specific shortcuts that work only when the mouse pointer is hovering on the specific window.\n\nThe issue is about the second type of shortcuts that happens to tablet users.\nThe problem is that Blender shortcuts don't work even though the mouse pointer stays on the specific window if the tablet stylus is further from the tablet surface. \nThis behavior can't be reproduced with mouse on.\nBecause there's no indication on screen whether the window is activated to register shortcuts, users will be difficult to pinpoint why the shortcuts are not working.\nIt's also very difficult to utilize shortcuts when users need to press the shortcuts with a stylus in hand or shortcuts that require two hands to operate.\n\n\n\n\n\n1. Start up Blender on PC with a graphic tablet\n2. Make sure no mouse is connected on PC\n3. Select the cube mesh and go into edit mode\n4. Select one of vertice of the cube mesh\n5. Lift your stylus out of the tablet while making sure your mouse pointer stays on the desired window\n6. Try shortcut such as 'L' to select linked\n7. You will see the shortcuts don't work\n\n\n\n\n**Solution that I can think of is:**\n\nTo be able to recognize and register the shorcut inputs as long as the mouse pointer stays on the specific window even if the stylus is out of the distance of the tablet surface.\n\n", "Select loop only works if the hidden face is a ngon\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3070\n\nBroken: 3.3, 2.79b\nWorked: 2.49b, 2.59\n\nCan't select the boundary loop of a hidden face, unless the face is an ngon.\nThe expected selection behavior is the same as if the face was deleted instead of hidden.\nIn ancient Blender versions it works.\n\n- Open attached file\n- Alt click to select the open loop. It will only select an edge (selects loop for n > 4)\n[bug.blend](bug.blend)", "Glitches with Curve Fill Node\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked version: never\n\nIf you instance circles or other curves on a curve and you will realize those instances, and you will use the curve fill node on them. There are some glitches or inconsistencies.\nIf you change the scale, the fill node will also randomly decide what should be filled.\n\n\n\n\nTest File:\n[#95518.blend](T95518.blend)\n", "Loop Cuts and Inset Faces cutting Meshes\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 750 TI\n\nBroken: 3.2\n\nTrying to add regular edge loops with Control + R, or even trying inset a face, they are cutting my mesh, or merging the ends. (I shared this on reddit, and it was suggested I create bug for it. \n\nAll I did was delete the bottom face of the mesh since I would not need it, but somehow I created invalid geometry and when I add an edge loop near the end it merges. If I try to inset the faces, it gives me weird end geometry.\n\n(This is what was noted from someone on Reddit: Update: just checked the file and here are my findings:\n\n```\n Adding a loop, be it length ways, long ways, or any other way seems to works just fine with the CTRL-R shortcut\n```\n\n```\n The loop cut tool also works just fine.. except if you try and loop cut around the XY plane instead of the XZ plane (drawing a line around the thinnest faces) at which point the mesh seems to collapse to zero height\n```\n\n```\n Insetting faces also works fine, be it via the tool or pressing I... but if you then try and extrude the inset suddenly the model collapses\n```\n\nOther things of note: the face orientation is inside out for this mesh (turning on Face Orientation in the Overlays menu (two overlapping circles in the header) shows them as red) and the object-level scale hasn't been applied. Fixing both of these doesn't correct any of the above issues -- although it IS normally advised since it prevents a few shading and modelling issues -- but it does, for some reason, change how the errors manifest, like the model collapsing in a slightly different way or the CTRL-R shortcut suddenly causing the same issues the tool version of loop cut and slide has.\n\nConclusion: you've somehow managed to turn this mesh into some form of invalid geometry that Blender can't seem to handle properly. You may wish to report it as a bug, including this file as a demonstration.\n\n- Open .blend file\n- enter edit mode and select face mode\n- press numpad 3 for YZ plane view\n- Add loopcut on visible face side (it'll merge the edges)\n\n---\n- repeat first 2 steps from above\n- press numpad1 for XZ plane view\n# select visible face -> extrude + scale (will merge edges). Works with inset tool\n\nTest File:\n[Issues Build2.blend](Issues_Build2.blend)", "Data Transfer doesn't work in some situations (geometry nodes modifier preceeding the Data Transfer modifier)\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GT960\n\nBroken: 3.5.0 (2023/01/11)\n\nData Transfer does not work on geometry generated by Geometry Nodes\n\nError is set up in the attached file:\n\n[Color Transfer Test.blend](Color_Transfer_Test.blend)\n\nDoesnt work in `Material` or `Rendered` viewport mode either.\n\n[Color Transfer Test 2.blend](Color_Transfer_Test_2.blend)\n\nI don't know if it's related (it feels like it is) but even setting color inside a geometry node (on geo node created meshes) doesn't work in Material or Rendered viewport modes.\n\n[GeometryNodesColorBug.blend](GeometryNodesColorBug.blend)", "Curve Extrude Tool Todo\n## Curve Extrude\n * - [x] {icon circle color=red} Add Extrude tool to Curve Edit toolbar \n * - [x] {icon circle color=yellow} Add Extrude manipulator when using this tool\n * - [ ] {icon circle color=green} The direction of the extrude handle is only correct on one of the extremes:\n\nCorrect:\n\nGizmo points away from the curve\n\nIncorrect:\n\nGizmo points towards own curve\n\nThe gizmo should always point outwards at each end. ", "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", "Knife Tool produces bad geometry in certain cases (disconnected edges/vertices, overlapping faces)\nif i use tools knife i see this bug.\n\n\n\n", "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.", "Curves: Edit mode transform pivot on individual origins does not work\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.2.1.230210\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nAlso 3.5 beta.\n\nIn curves edit mode, transform pivot on individual origins does not work.\n\nPivot on active element also does not work, but it seems curves edit doesn't have the concept of active element at all, so not sure if this is a limitation right now.\n\n[CurvesEditTransformPivot.mp4](attachment)\n\n" ]

[ "Knife project stopped working altogether recently, always incorrectly reports no boundary edges to use for cutting.\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\nWorked: Unsure exactly.\n\n[knife project bug.blend](knife_project_bug.blend)\n[2021-11-04 14-32-49.mp4](2021-11-04_14-32-49.mp4)\n" ]

[ "Physics: The default value for Format Volumes is nothing...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 2.93.4\n\nThe default value for Format Volumes is nothing...\nBlender will stop working if you try to let the Animation play. EDIT: Can no longer reproduce with Blender 3.0\n\nDo a Backspace (to reset to default) on \"Format Volume\"\n![2021-09-09 09_15_29-Blender_ [C__Users_raimund.klink_Downloads_adaptive bug2.blend].png](2021-09-09_09_15_29-Blender___C__Users_raimund.klink_Downloads_adaptive_bug2.blend_.png)\n[happy_little_bug.blend](happy_little_bug.blend)\n\n", "Low unit scale values show wrong Stepsize in sliders\nOperating system: Linux-5.8.0-2-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: not in 2.80 or 2.83\n\nWhen the unit scale is too low (<= 0.002 for imperial, <= 0.00009 for metric) the stepsize is too big and sliding bound sliders (like thickness in solidify) will bounce them between their limits. At almost the same time seperate units stop showing the correct unit and instead switches to the default unit. But that seems to don't quite align as I was able to get the unit issue without the stepsize issue (might related to #81663).\n\nThe stepsize issue does not appear when Continuous Grab is disabled in the User Preferences.\n\nBased on default startup.\n1. In Scene Settings: enable seperate units\n2. set unit system to imperial with a unitscale of 0.001\n3. add a solidify modifier and slide the thickness value\n4. set unit system to metric with a unitscale of 0.00009\n5. slide the thickness value of the solidify modifier again (same behavior)\n6. disable Continuous Grab in the User Preferences\n7. slide the thickness value of the solidify modifier again (normal behavior)\n\n", "Add Object Tool, Resolve UI Issues & Polish\nThis task is to track the add-object tool.\n\n- - [x] Resolve behavior when axis aligned, see: #57210 (currently creates very large object). Done 1501c3adad\n- - [ ] Review design changes proposed by @DanielBystedt #57210#1010083", "Dimensions reported by Add Primitive Tools do not match actual dimensions.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro P4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.16\n\nBroken: version: 3.0.0 Alpha\nWorked: Never Known to Work\n\nNo matter what physical size the primitive is when created, the redo panel reports that it is 1m or 2m for any dimension. In the example attached  the radius and depth are reported as 39.4\" (1m) and 61.7\" (2m) respectively. While the actual dimensions reported in the N-Panel are 0.221\" x 0.255\" x 0.127\".\n\nCuboids (Cube) are especially erroneous because they can have a different actual value for width, length, and height, but the single dimension \"Size\" is reported as 2m in the redo panel.\n\nIn the base startup file, create a primitive using the tool in the tool panel. Open the redo panel and observe the dimensions reported and compare them to the dimensions reported in the Item Panel.", "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", "Editing asset shelf preview size can make asset shelf disappear\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\n\nEditing asset shelf preview size can make asset shelf disappear\n\n\n1. Use the example python file for asset shelf (edit `poll` and `asset_poll` functions to simply `return true`, not related, but helps to reproduce)\n\n2. Edit `preview size` with mouse drag, and randomly the region will disappear\n\n\n<video src=\"attachment\" title=\"2023-08-29 22-23-34.mp4\" controls></video>\n\n", "Possible 4.0 Top Menu Changes\nI'm hoping that with Blender 4.0 we can take the chance to move some menu items slightly.\n\nOne concern I'd love to address is the discoverability of the \"app\" (Blender logo) menu. I'm sure most users find it eventually, but that won't happen be immediately for new users.\n\nI would address this simply by moving out of that menu anything that a new user might need, and leave it for things that more advanced users use. This moves \"Splash\" and \"About\" items to the Help Menu. The \"System\" submenu expands out. \"Install Application Template\" moves to File Menu. This leaves it with only items that most new users can safely ignore at first: \n\n\n\nMoving \"Install Application Template\" to the \"New\" submenu makes it more clear that you can add to the list:\n\n\n\nWith the \"File\" menu it would be nice to group the \"Loading\" and \"Saving\" items together. This separates \"Import\" and \"Export\". These two items have contents that look almost identical so it is easy to select an import instead of an export and cause damage. This also makes the list shorter so that it can better accommodate #104678.\n\n\n\nFor the Edit menu we can group the items slightly better by making \"Undo History\" a part of the Undo/Redo group. And also make it clear that \"Adjust Last Operation\" is the same that is done when \"Repeat Last\" and is part of repeat history:\n\n\n\nI'd like for the Help menu to look a bit simpler by following our existing recommendations of not showing repeating item icons. And also move the Splash and About here:\n\n\n\nI have a sample PR that can be tested here: 106654\n\n", "Measure tool multi 3dview and quad view inconsistencies\nUbuntu 20.04 5.4.0-48-generic\nGeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBlender 2.91 master build from 8335c26119bf5ba78b2afa4e2f65bb3d04b42abe\n\nMeasure tool multi 3dview and quad view inconsistencies\n\nOpen default scene. Enable Measure tool in toolbar and add a measurement.\nEnable quad view with ctl+alt+q.\nGo to top view and adjust measurement. Do not do anything else.\nDo the same with front and side view, you now have 4 different measurements visible.\nYou can zoom, move and rotate views and you still have 4 measures, but if you select an other object it will change to the last adjusted measurement.\nSame if you split 3dview.", "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", "Low unit scale values show wrong Values and Units in sliders\nOperating system: Linux-5.8.0-2-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: not in 2.80 or 2.83\n\nWhen the unit scale is too low (< 0.0001 e.g. 0.00009), the values in all sliders will jump up to the value they would have with a unitscale of 1.0. This causes problems with the clipping planes of the viewport camera (didn't do this in 2.80). This seems to be independend of the unit system (metric/imperial).\n\nIf this is a known limitation then the shown precision of the unit scale slider should reflect that. Also a fix for the clipping plane issue is needed as that did work in 2.80.\n\nBased on default startup.\n1. In Scene Settings: enable seperate units\n2. set unitscale of 0.00009 or less (metric r imperial)\n3. observe what the dimensions sliders tell you about the dimension of the default cube.\n4. observe the buggy floor grid in the viewport probably due to the same bug in the clipping sliders (wasn't there in 2.80)\n", "Buggy floor grid when using a micrometer unit scale\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.83.5\n\nWhen working with micrometer unit, setting up unit scale up to 0.0001 works ok. But, from 0.00001 micrometer value and grid scale changes to weird condition.\n\n\n- In Scene Settings set unitscale to 0.00001 or less (metric r imperial)\n\n", "Transform orientation undo is inconsistent.\n\nBroken: 3.0\nWorked: ?\n\nTransform orientation undo is inconsistent. It works in object mode, but doesn't work properly in edit mode. In edit mode it sometimes won't undo, or undoes together with another different step(like changing mode, or moving vertex).\n\n- Open default startup;\n- Change the Transform Orientation from Global to something else\n- Undo/redo - it works;\n\n---\n- Reopen default file\n- Go to edit mode\n- move vertex\n- Change the Transform Orientation\n- undo multiple times - Will never undo the Transform Orientation. (now deselect cube and perform undo operation: will revert selected transform orientation)\n\n", "Volume overlap clipping\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.40\n\nBroken: version: 3.6.2\n\n<tr>\n <img src=\"attachment\" alt=\"Snag_a8e98af\" height=400px></td>\n <img src=\"attachment\" alt=\"Snag_a8e98af\" height=400px></td>\n</tr>\n\nOverlapping VDB/Volume objects create clipping issues where empty space of one volume meets another volume. Changing VDB space from Object to world does not address this issue, neither does changing the float precision from from half to full. Neither does increasing the volume steps, volume light bounces, or the transparency light bounces.\n\nThis has been a consistent issue now since maybe as far back as 2.79, then it could be mitigated by the \"optimise empty space\" being disabled, but now that's seemingly gone, the issue is back and really needs addressing. \n\n\n- Open the attached Blend file\n- head into rendered viewport.\n\nYou will see clipping like in the images attached\nAlternatively, just add a vdb or volume bake to a scene and instance it or duplicate it to overlap with one another and in Cycles you will see the clipping happen\n\nDownload from this link [NEW LINK](p6qN69KLpCFbMHc)\n\nThank you for looking into this\n\nEDIT: Updated link", "Some properties, like Dimensions, remain editable in 3DView for linked etc. IDs\nIn the 3DView properties panel, some non-RNA properties like Dimensions of objects remain editable, even for linked objects.\n\n[editable_linked_data.zip](editable_linked_data.zip)\n\nReproducible at least since 2.93, so not a (recent) regression.\n\nNOTE: ideally those non-RNA UI widgets should still use `RNA_property_editable_info` to check if they can edit the data, and display a proper explanation if not.", "Spin / Screw Adjust Last Operation: using the slider after having reset the axis will constantly pop up `Invalid/unset axis` [hard to escape]\nWindows 10\nNvidia mx 150\n\nBlender 2.9\n\nBlender starts to loose control in some functions when i press make some values to \"Zero\".\n\n1. Make a plane. goto edit mode and select face.\n2. Press \"Alt+E\" and select \"Spin\" option.\n3. Goto Last action menu, hover over the axis X value and press \"Backspace\" to make all values to zero. Error popup `Invalid/unset axis` comes up (which is correct)\n3. note here that Backspace seems broken [or intentionally disabled in recent builds], so it might be neccessary to set axis to zero \"by hand\"\n4. Now try to change the spin \"Steps\" using the slider (arrow keys are OK) and it will \"hang\" (as in: Error popup will follow the mouse) and you will have to hit ESC multiple times or force close blender.\n\n[#81042.webm](T81042.webm)" ]

[ "\"Multi-Number Button Editing\" not working in \"Dimensions\" when entering values with the keyboard\nWindows 7, nVidia GeForce GTX 570\n\nBroken: 2.70 RC1 19f7f9a\n\n\n\"Multi-Number Button Editing\" is not working in the \"Dimensions\" box inside the Properties of the 3D View when you try to edit them with the keyboard\n\nThe normal behavior is dragging-selecting the rows you want to edit simultaneously and moving the mouse, but if you want to do it numerically you just release the mouse button. At that moment, you are able to enter the values and when hitting Return they are not stored.\nI have tried with other ones such as \"Scale\", \"Rotation\", \"location\" and so on and all of them works perfectly.\nThe only one that doesn't is the \"Dimensions\" in the Properties right panel of the 3D View.\n" ]

[ "Splitting two modifier keys between two input devices doesn't work\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.0\n\n\nPressing modifier keys from two keyboard device doesn't correctly register in blender.\n\n\n- Have two physical \"Keyboard\" device that both have modifier keys\n- Press Ctrl on keyboard 1 and Alt on keyboard 2\n- Blender doesn't recognize that both Ctrl and Alt are pressed.\n\n-----\n\nOriginal description:\n\nHi - I have modifier keys (shift, alt ctrl) assigned on mouse and keyboard and razer keypad. \nI use alt to select edge/face loops without issue. \nIf I press shift+alt on keyboard then I can select as many loops as I like. Same if I press shift+alt both on mouse. \nHowever, if I use modifier keys combined between deviced (shift on keyboard and alt assigned on mouse, or vice versa) then it lets me add only one additional loop to selection only. \nI initially thought it was accessory issue, but Its true with my default keyboard, razer keypad, logitech G600 and Razer Naga mouse, I suspect the issue is within blender. \n\nIn summary combining modifier keys between keyboard/mouse doesn't seem to work, atleast with loop selections. Any advice? Thanks\n", "GPencil: Shortcuts in Draw Mode are hardcoded\nMultiple keys in the `gpencil_draw_modal` function are hardcoded and (some) don't show up in the info bar. This makes it impossible for the user to know what certain keys do as well as impossible to change them in the keymap. All of those keys should be in the keymap with the default keys set as they are now.\n\nHere is a list of these (hardcoded) shortcuts:\n\n - {key Enter}, {key Pad_Enter}, {key Esc}, {key Space}, {key Ctrl Z} (?): Confirm\n - {key Mousewheel_Up}, {key Pad_Plus}: Increase size of eraser\n - {key Mousewheel_Down}, {key Pad_Minus}: Decrease size of eraser\n - {key O}: Set center of guide\n - {key V}: Turn off speed guide\n - {key M}: Alternate or flip guide direction\n - {key L}: Turn on line guide; {key Ctrl L}: Turn on line guide with angle = 0; {key Alt L}: Turn on line guide with last angle\n - {key C}: Turn on circular guide\n - {key K}: Turn line guide clockwise\n - {key J}: Turn line guide anti-clockwise\n", "Wrong description in the property of the Cube Projection Mapping\nBroken: version: 2.83 (sub 6)\n\nWhen you perform the `Cube Projection` `UV Mapping` operation, you see on the `Redo Panel` a property called \"Cube Size\" - \"Size of the cube to project on\".\nSo you espect the input value represent a 3d cube with that size.\nBut when you use the tool the input is the divider of the cube size.\nSo, for example, if you wants a mesh of size 2 to be projected on a cube size of 3, you don't write the value 3.0 to the \"Cube Size\", but you write the result of 2/3 (0.66).\n\n- Open Blender\n- Select the default cube\n- Go to edit mode\n- press U - `Cube Projection`\n- enter the 0.66 value.\n\nYou will see a output UV like this, that is the UV expected when you use a cube of size 3x3x3\n\n\nIf you put an input of 2.0, this does not mean a cube with size 2x2x2, you obtain an UV like if the projection cube is twice the size (4 meters)\n", "The viewport may update at 0 FPS while navigating, until the mouse is released.\nOperating system: Windows 10\nGraphics card: RTX 3080 Ti\n\nBroken: 3.0.0\nWorked: 2.92.0\n\nWhen working in sculpt mode on a model with multires modifier, the viewport may update at 0 FPS while navigating, until the mouse is released.\n\nUsually when navigating in sculpt mode on a model with multires modifier, the model will switch to a low poly version while navigating. When this bug is happening, the viewport remains frozen and the high poly model remain on screen until mouse is released.\n\nThe bug will be temporarily fixed upon clicking on another application or resizing the blender window.\n\n1. Shift+A to create a plane\n2. Ctrl+E and subdivide it 4 times.\n3. Attach multires modifier onto the plane.\n4. Subdivide it 6 times with the multires modifier.\n5. Use sculpt mode and sculpt without moving the view for around 1~2 minutes (I used a wacom tablet. Using the sculptDraw brush, I added / subtracted (hold ctrl) from the mesh, also using smoothing brush (hold shift) to smooth certain parts, and undo (ctrl + z) multiple times to simulate a normal working environment.)\n6. Try to pan or rotate the view around.\n\n\n\n**I found another way to trigger this bug, and it's not strictly related to sculpt mode.**\n(Tested on blender 3.1.0 beta 03b57d3973)\n\n1. Click around with a Wacom tablet.\n2. Pan the camera around with a Wacom tablet.\n3. Pan the camera around with a mouse.\n\n\n[sculpt mode bug.blend](sculpt_mode_bug.blend)\n\n[2022-01-17 04-48-11_Trim.mp4](2022-01-17_04-48-11_Trim.mp4)", "Space Mouse not working properly\nOperating system: Mac OS Ventura 13.3.1 (a)\nGraphics card: Apple M1 Max\n\nBroken: 3.5.0\nWorked: 3.0.0\n\nNo buttons of the Spacemouse work anymore.\nEverything worked with Blender 3.0.0 and 3D Connexion Driver 10.7.0.\n\n1. Install latest 3D Connexion Driver 10.8.0.\n2. Set up some buttons in 3DxWare 10 like:\n a. \"Button 1\" = Keystroke \"Tab\".\n b. \"Button 2\" = Keystroke \"1\".\n c. \"Button 3\" = Keystroke \"2\".\n3. Start Blender.\n4. Try to switch between Edit and Object mode with \"Button 1\":\n a. No Function.\n5. Try to switch between select Modes with \"Buttons 2-3\":\n a. No Function.\n6. Try to select more Objects with holding \"shift\" on Space Mouse:\n a. No Function.\n\nI miss the combination so hard, it's impossible to work without my space mouse, I'm used to it for a decade. :(\nThe Space Mouse works fine in all other Programms, its an Blender Issue exclusively.\n\nAdditional Infos:\nSometimes restarting Blender multiple Times, re-installing it, fixes temporary the function of the basic Keys \"shift, cmd, etc\". The other buttons never work. They worked always in the past and still work in all other programs where I use the mouse. ", "Tool 'builtin.move' not found for space 'VIEW_3D'\nOperating system: Wondows 10 Home\nGraphics card: RTX2060\n\nBroken: 2.93.3, 3.0.0 Alpha\n\nIf you try to use W, E, R, T hotkey while you in Weight paint mode with some Armature selected, you will have this error/warning :\n`Tool 'builtin.move' not found for space 'VIEW_3D'`\nI tested it in Industry Compatible keymap which i used in both mentioned Blender versions. \n\n- Open attached file\n- Set the `Industry Compatible keymap`\n- Select Armature then Shift+select the skinned mesh\n- go to Weight paint mode.\n- Press W, E, R or T key and you will have this error:\n```\n'builtin.move' not found for space 'VIEW_3D'\nor 'builtin.rotate' not found for space 'VIEW_3D'\nand so on.\n```\n\n*The error also will appear if you try to use Q hotkey which are Box Selection tool. In this case it will be - Tool 'builtin.select_box' not found for space 'VIEW_3D'*\n\nThe problem its not just a warning/error themselve, but the fact what you will no longer have ability to set a hotkey for those keys trougth any addon, as example in my case - \"Pie Menu Editor\". \nSo a lot of hotkeys which can be set for certain modes will be lost and completely unavailable.\n[tool_shortcut_bug.blend](tool_shortcut_bug.blend)", "Mitigate the risk of wrong shape key selection in sculpt and edit mode.\n# The Issue\n\nA major weakness of any layered editing system is that it matters which layer is selected for editing operations, but this selection is not apparent in the actual editing space, because layer effects are by definition combined into a single result for display.\n\nFor instance, unless the single key mode is turned on, the effects of all relative shape keys are summed up into a final shape, which doesn't change no matter which one is selected.\n\nThis means that it is easy to apply editing operations to the wrong selected layer, including a possibility that the undo stack will be exhausted before the mistake is noticed.\n\nAn additional risk factor is that shape influence sliders are located in the same list, and a hurried misclick on a slider can change selection.\n\n# Proposed Solution\n\nThe industry standard way to mitigate this risk is layer locking: layers that are not currently being worked on can be locked by the user, in which case all editing operations that would affect that layer will instead abort with an error.\n\nBlender already supports this with Vertex Groups and weight painting - even though with groups it is more obvious which one is selected, and locking has additional effects related to normalization.\n\nI propose adding this feature for shape keys (implemented in #104463):\n\n\n\nSince it is a standard approach that is used by any advanced image editor, most users would likely be already familiar with the concept. However there are some details in its application that need discussing.\n\n## Scope Issue\n\nThe primary design question is which operations should react to layers being locked, balancing mainly implementation complexity and the effectiveness and convenience of the feature.\n\nIn implementing the prototype I decided that the main criteria should be:\n\n* Operations that affect vertex positions, and thus shape keys.\n\n* Operations where the shape key selection matters:\n\n For example, applying object mode transformation updates all shape keys. Thus the selection doesn't really matter, and respecting locks would inconvenience the user that is working on the scene layout, rather than individual object details.\n\n* Deform-only operations:\n\n Even though selection may affect the final vertex positions, operations that change topology necessarily change all shape keys. For that reason, topology manipulation also belongs in an earlier stage of the design pipeline than shape key creation, even though it may be necessary to do it later sometimes for various reasons. Finally, topology change is seldom not accompanied by using transformation operators that respect the locks.\n\n### Current Scope\n\nThis is the current scope of the checks in the prototype:\n\n* All Edit Mode <u>transformation</u> operations.\n\n Specifically, everything invoking the generic transform system initialization code.\n\n* All <u>Sculpt brushes</u> that affect vertices, and not colors or masks.\n\n Specifically, everything invoking the generic brush stroke initialization code.\n\n* <u>Smooth</u> and <u>Laplacian Smooth</u> operators in Edit Mode.\n* <u>Blend From Shape</u> operator in Edit Mode.\n* <u>Propagate To All Shapes</u> operator in Edit Mode.\n\n This one is a bit of a problem, because technically shape selection doesn't matter here: it snaps all shape keys to the current position. However currently I implemented a check to abort if any shape key is locked on the principle that it is a shape key operation. Maybe it should only check the main Basis, or work in some other way.\n\n* <u>Mirror Shape</u> and deleting shape keys.\n\n* A few other operators...\n\nThis [spreadsheet](edit?usp=sharing) containts an exact listing of which operators should and actually do check for locks.\n\n# Discussion\n\nIt is necessary to discuss whether the main criteria, or this specific list needs changing. For instance, I'm not confident that I remembered all operations that match the criteria for the checks.\n\nAnother minor design point is whether attempting to edit a locked layer should be an error (shows a message under the cursor) or a warning (appears in the status line).\n\nSince the checks are done by operators rather than low-level code, add-ons would have to implement them too where relevant. I wonder how many would be affected, and whether some API additions to help them do that easily would be necessary.\n\nThere have also been some questions raised in #104463, like:\n\n> - Are shape keys a special case? (is there other data we might want to lock).\n> - Is the current implementation disallowing editing in all anticipated situations? There seems to be quite a few ways to transform vertices that aren't included here, applying transform, moving object origins, ... to name a couple, probably other mesh tools too. It may feel like an incomplete feature if these are left out, yet, this means we need to add check in many more places.\n> - Are there ways this can be implemented in a way that doesn't frustrate users. For example, you load someone elses file, select objects and want to apply transform. If they have locked a shepe-key it could mean having to manually select and disable the the locks. Users may request a ways to disable locks on all selected objects, maybe going along in this direction is fine, but we can anticipate some of these issues and consider functionality that doesn't add unnecessary overhead. \n", "NDOF buttons no longer programmable with Blender commands\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 2060 SUPER\n\nBroken: 2.93.4\nWorked: 2.92\n\nNDOF (3D Connexion Space Navigator) has two programable buttons which are programmed in the 3D Connexion software. The button settings have a dropdown where one can select a 'Blender' drop down which lists a number of possible Blender functions for that button. Now, none of them work. It appears that only the 'Blender' dropdown is not functioning. Other dropdowns still work, so I know the Space Navigator is operating well. I particularly use the 'Fit' option in the 'Blender' dropdown, but I tested others and none of the Blender functions work now.\n\nThey did in previous versions (2.92) Beginning in 2.93, there were other problems with the Space Navigator that I did not report, but they were fixed in 2.93.4. Now this new problem of being unable to program either of the two side buttons with any of the 'Blender' functions has appeared.\n\nI contacted 3D Connexion Tech Support but they could find no solution. The problem appeared with the older device driver, but installing the newest driver did not solve the problem.\n\nError can be reproduced with Space Navigator and Blender 2.93.4\n\nThanks for Blender and all the time you spend perfecting it. ", "Polishing Correct Face Attributes\n- [ ] Initialize operators options based on the \"correct face attribute\" value (e.g., edge slide).\n- [ ] Unify naming of the option and the operator options.\n\nThe way we do Proportional Editing seems to be a good example to follow. These issues have been raised on 4387aff", "Not recognizing numpad page up /down keys .\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nBlender is failing to recognize the numpad keys !!!\n\nTrying to use the change workspace shortcut ctrl+PageUp /down and blender is not recognizing the keys in numpad and keep assuming the key 9 and 3 . Other software is fine and i can use Page up and Down, and the home end keys. \n\n", "Alt-Drag (multi-editing) fails for HSV color buttons\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.83 (sub 1)\nSeems to be a long-lasting issue, as even Blender 2.81a shows the same behaviour.\n\nPretty much the title. \nTrying to assign an object color through the Object Properties tab (Viewport Display > Color) to multiple Objects doesn't work, neither by picking the Color on the Color Wheel, nor by moving the HSV sliders, while Alt-Clicking. Only the last selected Object will update.\nHowever:\n\n\n - If sliders are set to RGB, editing them will correctly affect all selected Objects.\n - The Alpha slider, which is shared between all three Color Wheel modes, works as intended and affects all selected Objects.\n\n\nFrom the Info console I've noticed a tuple is set everytime a Color is picked from the Color Wheel, but doesn't show anything when using the HSV Sliders.\nMoving the the RGB and Alpha sliders correctly sets each Object's property to the selected value.\n\n\n\n\n - Open Blender, default startup file\n\n - Add>Mesh - Select any kind of Mesh Object (have at least 2 items in the scene, or more)\n\n - Go to the Shading Panel in the top right and Select \"Object\" down the Color section, to see Object Colors in the viewport\n\n - Press A to select All Objects, or alternatively, select them one by one by Shift+Right Click\n\n - Go to Object Properties > Viewport Display > Color\n\n - Hold ALT either while clicking on the Color Wheel or while moving the HSV Sliders. Only the last selected Object will update.\n\n\n\n\n - While holding ALT, try moving the Alpha slider. All selected Object will update.\n\n - In the Color Wheel, select the RGB tab. While holding ALT, try moving the R, G or B slider. All selected Object will update.\n\n\n\n\nHere's a quick demonstration:\n\n[2020-01-20_22-01-14.mp4](2020-01-20_22-01-14.mp4)\n\nAnd the Info panel readings:\n[2020-01-20_22-02-46.mp4](2020-01-20_22-02-46.mp4)\n", "Python variables becomes invalid when batch creating attribute layers\nOperating system: Gentoo Linux\nGraphics card: AMD WX 9100\n\nBroken: 3.2 and master\nWorked: I'm guessing this has been broken since attribute layers were introduced\n\nWhen creating new attributes layers via python, the returned attribute object will stop work after multiple layers are added.\nIt seems like the attribute layers might be reallocated and moved while the python pointers doesn't get updated when this happens.\n\nIn a python script, create multiple attributes for a mesh in a row and save the return value.\nNotice that if you add too many the previously returned variables will stop working.\n\nSteps to reproduce with the attached file:\n1. Click run script\n2. Notice that at2 through at5 is of length zero\n3. If you remove any one of the `new` calls the returned variables are valid.\n[attribute_error.blend](attribute_error.blend)", "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)", "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).", "Shape Key animations do not render if user is in edit mode when beginning the render.\nOperating system: Windows 10 Home 64 Bit\nGraphics card: Intel (R) HD Graphics 610\n\nBroken: 2.80, ee0d8426ab6d, 2019-05-03\n\nIf the user is in edit mode when they start the render, shape keys will not have any effect.\n\n1. Create an object.\n2. Add the 'Basis' shape key.\n3. Create another shape key, and edit it.\n4. Keyframe the value of the shape key at different frames.\n5. If the user is in edit mode when the render starts, the shape keys will not have any effect. Otherwise, it will work fine.[blend.blend](blend.blend)\n\n[no-edit.mkv](no-edit.mkv)\n\n[edit.mkv](edit.mkv)" ]

[ "Click and dag \"synchronized editing\" on \"Transform>Dimensions\" parameter on 3D view properties shelf has strange behavior\nWindows 7 64 bits\nNvidia Geforce Gtx 580\n\nBroken: 2.70 RC1 19f7f9a\nAlso present on: 2.70 RC1 571f184\n\nThere's this new feature where you can click and drag several vertical sliders so that you can synchronize edit their values.\nCurrently in the 3D view, properties shelf, if you drag the \"dimensions\" values the \"Y\" slider seems to be out of sync with the others, either not working or having a different value\n\nSelect default cube\nOpen Properties shelf (N)\nIn \"Transform>Dimensions\" parameter click on X and drag down till over Z\nDrag side ways to change value\nDimensions should stay in sync but Y value doesn't move\nAlso right clicking to cancel leaves the X value at 1.930 instead on original value\n\n(other axis combinations also produce strange behavior, sometimes setting size to 0)\n\n" ]

[ "Blender crashes with EXCEPTION_ACCESS_VIOLATION when executing the sequencer.duplicate_move operation while in background\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.0.0\nWorked: *unknown*\n\n\nWhen running the operator: `bpy.ops.sequencer.duplicate_move` while Blender is backgrounded with the `--background` command line argument the process crashes.\nSee more details in in `bug-report.zip/README.md` and `bug-report.zip/render-frames.crash.txt`\n\nA snippet of the python code triggering this crash is here (the entire source can be seen in the attached .zip):\n```\n override = bpy.context.copy()\n override[\"workspace\"] = bpy.data.workspaces[\"Scripting\"]\n override[\"screen\"] = bpy.data.screens[\"Scripting\"]\n override[\"area\"] = editor\n override[\"region\"] = editor.regions[-1]\n strip_len = len(strip.elements)\n retry = 5\n while(not bpy.ops.sequencer.duplicate_move.poll(override)):\n retry -= 1\n if retry < 0:\n print(\"Couldn't duplicate for pingpong ... quiting\")\n return False\n bpy.ops.sequencer.duplicate_move(\n override,\n SEQUENCER_OT_duplicate={},\n TRANSFORM_OT_seq_slide={\n \"value\": (strip_len, 0),\n \"snap\": False,\n \"snap_target\": 'CLOSEST',\n \"snap_point\": (0, 0, 0),\n \"snap_align\": False,\n \"snap_normal\": (0, 0, 0),\n \"release_confirm\": False,\n \"use_accurate\": False\n }\n )\n```\n\nDownload bug-report.zip and extract it. Follow detailed steps in README.md.\nIn summary:\n\n- Notice the happy case when running the following command a test movie of 6 frames is rendered to the output directory set in `render-frames.blend` by default this is in `/tmp/`. Blender is left in the forground because `--background` was not supplied\n\n```\n\"C:\\Program Files\\Blender Foundation\\Blender 3.0\\blender.exe\" render-frames.blend --python-text render-frames\n```\n\n- The crash occurs when supplying the `--background` flag in addition to the above\n\n```\n\"C:\\Program Files\\Blender Foundation\\Blender 3.0\\blender.exe\" render-frames.blend --background --python-text render-frames\n```\n[bug-report.zip](bug-report.zip)", "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)", "Collision on Properties is very badly LAG\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\nCollision on Properties is very badly LAG\n\nMacOS 13.5\nBlender 3.0.1, 3.4.1, 3.5.1, 3.6, 4.0 very badly lag during play on Cloth and Collision button.\nMy file is Lola Bunny 4.0.blend that version.\nI did save previous from 4.0 to 3.6 then to 3.5.1 then to 3.4.1 document .blend\n\nExplain:\nthere Timeline and push the right key from 1 to 2 timeline cause wait for a while then finish and try push the right key from 2 to 3 timeline cause wait too lag.\n\nfor Mac Push the Shift + Spacebar key (start play) cause wait too long super lag.\nO2p2Ms3\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", "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", "LineArt; Crash after press play in a scene with LineArt modifier\nOperating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\nNo idea what crashes blender. Just press play and wait some seconds.\n\nI would love to help solving this issue, so when someone could remind me where the crashreport usually lands in Linux, i could share that as well.\n[Narrator.blend](Narrator.blend)\n\n", "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", "Particle systems render wrong on frame 0\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.5 Release Candidate\n\nA particle system renders moving particles in the wrong place on frame 0, if particles are spawned (=Frame Start) before frame 0.\n\n1. Create a particle system\n2. Set Frame Start to something smaller than 0 (with bigger negative numbers the effect is more obvious, so f.e. Frame Start = -20) (the effect is even more obvious if \"End\" is set to 0 or close to 0)\n3. Set particle object to render (Render -> Render As -> Object; Select Instance Object)\n4. Setting timeline start to 0 and rendering the frames, the wrong particle placement in frame 0 is clearly observable in relation to the next few frames. \n\nMoving the whole project/particle system timing to later frames manually, fixes this location jump. This shows, the problem is only the frame being 0.\n\n[particle_system_bug.blend](particle_system_bug.blend)\n", "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.", "Cyclic Strip Time not work with non-zero Action Clip Start Frame\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.3\nWorked: ???\n\nCyclic Strip Time not work with Action Clip\n\nI attached .blend to show this bug.\nThe track called \"Ok\" works with the \"Cyclic Strip Time\" check mark correctly.\nThe track called \"Bug\" works with the \"Cyclic Strip Time\" check mark incorrectly.\n\nIn the track \"Ok\", there are two keys, at 0 and 10 frames.\nIn the track \"Bug\", the same two keys, but for 43 and 53 frames. In the Action Clip, I set the values Frame Start =43 and End = 53.\nI expect that the \"Bug\" track will perform the same actions as the \"Ok\" track, but this does not happen.\nI think this is a mistake.\n[BugCST.blend](BugCST.blend)\n", "Save dialogue display performance issue on macOS\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.83.0 Beta\nWorked: 2.80 less slow, *2.79 best*\n\nWhen calling the Save dialogue with Ctrl+S, the user has to wait for almost one second for the dialogue to appear and be functional. \nFurther, the file name field seems to appear with a delay, causing the interface to adjust - creating visual noise.\n\nOpen a new file. Save the file.\n\n", "'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", "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", "Denoising + negative lamps = black and white artifacts\nOS X Sierra 10.12.6,\nNVIDIA GeForce GT 750M 2048 MB\nIntel Iris Pro 1536 MB\n\nBroken: 2.79\n\nSimple scene with negative lights gives bad artefacts with denoising enabled.\n\nJust render the attached .blend file.\n\nAttachments are:\n* Denoised image with artefacts\n* Non-denoised image without artefacts\n* .blend file\n\n  [denoising.blend](denoising.blend)", "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" ]

[ "Audio in VSE starts in wrong location when rendered with negative frames\nOperating system: win 10 \nGraphics card: GTX960\n\n2.80\n\nWith negative frames, audio starts on the first negative frame not where it is placed in the VSE when it is rendered out. (same issue in 2.79B)[test-0048-0045.mp4](test-0048-0045.mp4)\nBased on the default startup or an attached .blend file (as simple as possible).\n[VSE starts audio in wrong frame.blend](VSE_starts_audio_in_wrong_frame.blend)" ]

[ "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.", "Scaling keys in dope sheet is different from graph editor (ignores handles, esp, noticable when scaling negative)\nOperating system:\nGraphics card:\n\nBroken: 3.4.0\n\nSeems like if handles are not auto-clamped then *Dope Sheet* messes things up.\n\n\nIn attached file duplicate and translate both keys further in timeline, also put timeline cursor between them:\n - With *Graph Editor* press **S-1** to reverse new keys -> result is OK\n - **CTRL Z** to undo and repeat reversing in *Dope Sheet* -> bezier handles are processed incorrectly\n[dopesheet_reverse.blend](dopesheet_reverse.blend)\n\n\n", "Rigid body: Animated body collision geometry have unapplied scale for the first frame.\nOperating system: macOS-12.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Plus Graphics 645 Intel Inc. 4.1 INTEL-18.8.6\n\nBroken: version: 3.5.1\n\n\nIf an rigid body object has a scale that's not 1 , when physics simulation begins, the collision on the first frame will be calculated as if the object (collision geometry) is scaled back to 1, but subsequent frames will have correct scale.\n\n-----\n\nI have been following this tutorial\n\nwatch?v=2Dnks7C2q9U\n\nand as soon as I set the 'handle' object 'Animated' and press 'Play' on timeline, the bullet physics immediately kicks-in,\n\n\n\nThis is the file I'm using:\n\n[20230618_rigid_body_tipping_over_stacks_of_cubes_animated_wrong_activation_0001.blend](attachment)\n\n", "Moving cloth with bone in pose mode does not resets cache\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.50\n\nBroken: version: 2.83 (sub 6)\nWorked: 2.79\n\nMoving cloth with bone in pose mode does not resets animation cache\nThe same applies when pin empties:\n[2020-04-14 01-39-39.mp4](2020-04-14_01-39-39.mp4)\n\n- open attached file\n- play animation\n- move bottom bone in pose mode while animation is playing to see cloth moving and cancel bone movement\n- let animation loop\nsee that cloth still keeps moving while bone is in place. moving bone (the same bottom one for example) in pose mode at this stage results in no reaction from cloth (cloth keeps old cache)\nmoving the entire armature resets cache\n[MoveClothWithBone.blend](MoveClothWithBone.blend)", "`action.frame_range` span always >=1 when there's only 1 key frame in it.\nOperating system: Mint\nGraphics card: Nvidia\n\nBroken: 3.5 & main branch\n\n\nframe_range wrong value when only 1 keyframe\n\n- with default cube, go to frame 6\n- Insert a keyframe (for example, on location)\n- bpy.context.object.animation_data.action.frame_range returns (6.0, 7.0)\n\nMy expectation was it returns (6.0, 6.0)\n\nIf you then insert a keyframe at frame 7, it still returns (6.0, 7.0)\n\n", "GPU Subdivision not optimized in Weight Paint mode\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\nI'm not sure if it's unimplemented/unplanned or just overlooked, so I'm here to report in case.\nWhen you have a mesh using an Armature modifier and Subdivision modifier, the Subdivision will affect performance while posing the armature but enabling GPU Subdivision will noticeably improve performance during posing and animation. \n\nHowever, if you select the armature and the mesh and go into weight paint mode, allowing you to pose the rig, the GPU Subdivision will not boost performance with the Subdivision modifier. Weight Paint Pose is slower regardless as to the Subdivision modifier, just GPU Subdivision seems to be disabled here. \n\n- Open attached .blend file\n- Make sure `GPU Subdivision` is enabled in Preferences\n- in Weight Paint Mode, pose the rig (move any bone)\n- Go to object mode, select the rig and go to Pose mode\n- Compare performance when posing the rig\n\n[#101485.blend](T101485.blend)\n", "After swapping the basis shape key to another one, the former basis key still affects the new one\n2.91.0\n\nWhat I try to do: I would like to make a later created shape key the basis one. \nI can do it with moving it to the top, and setting the former basis key's \"Relative To\" setting to this new basis one.\nIt works as expected until I'd like to make further changes in the old basis key (now just a regular shape key)\nIt affects the current basis, where - by definition - there's no \"relative to\" setting, so it shouldn't be affected by anything.\n\nI noticed that it does work as expected if I'm using the \"shape key in edit mode\" option - BUT it only behaves well until I come back to object mode. Then the new basis key instantaneously gets all the modifications I just made on the old basis.\n\nThe steps are below on an image with descriptions, but I attached the blend file too. Just change the shape key called \"starting basis\" and check what happens with the real basis one.\n\n\n[shapekey_error.blend](shapekey_error.blend)\n\nNote: there was one time when I created a shape key pair where this whole thing worked as intended. But out of (literally) 6 tries, only one worked and I couldn't pinpoint what I did differently in that case.", "Rigid body : the animation of the angle constraint parameters does not work with an animated object\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: 2.92\nWorked: don't know \n\n\nRigid body : A rigid body \"animated\" object + a another rigid body object connected with hinge rigid constraint. The animation of the angle constraint parameters does not work with an animated object. I have bugs sometimes also with other parameters like breakable . (see the blend)\n\n[rigidconstraint.blend](rigidconstraint.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", "Tweak tool doesn't drag the point\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 516.59\n\nBroken: version: 3.6.0 Beta\n\nThe tweak tool is broken. It doesn't tweak a point.\n\n\nChhose the Tweak tool and try dragging a point.\n\n", "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", "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", "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", "Dyntopo detail size drawing with Shift + D seems broken\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: At least a few alpha versions ago\n\nDyntopo size control with Shift + D seems broken.\nThe first time I tried, the gizmo simply froze and the Resolution value didn't change after mouse movement.\nAfter installing the latest GeForce Studio Driver — version 457.30 — I tried again. The gizmo casts infinite lines, but I noticed that the Resolution value does change after mouse movement.\n\n1. Enter Sculpt Mode.\n2. Activate Dyntopo.\n3. Switch to Constant Detail mode.\n4. Press Shift + D.", "The object is not zoomed in Sculpt Mode when you click on Frame Selected\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel 4.5.0 - Build 23.20.16.4944\n\nBroken: version: 2.91.0\n\nI don't know if it's a bug or if it should be. In Object Mode, when you click on Frame Selected, the object is centered and zoomed to the full screen, but in Sculpt Mode, the object is only centered on the screen, but not zoomed.\n\n[Frame_Selected.mp4](Frame_Selected.mp4)" ]

[ "Scaling armature from smaller size to scale 1 results in broken animations (IPO not updated?) and non-connected bones is pose is not rest one.\nUbuntu 14.04 Gnome Edition on Intel HD 4000 and\nDebian Sid (updated to latest packages) with Nvidia GTS 8600\n\nBroken: All (Tested on 2.71 and 2.69)\nWorked: Never\n\nSomewhere between missing functionality and a Bug, it seems that if your armature is scaled to negative values (not tested with positive but should give the same result) and apply the scale in object mode (back to 1,1,1), the animation keyframes do not get scaled accordingly.\nIt seems the IPO information is not translated, and the functionality to convert that seems to be missing.\n\nThis has been a issue for quite a long time, exporting models to other formats (ie, game engines requiring scale 1 for things like parent relations), and multiple reports could be found on the Blenderartists forum (example of matching description is t-195566.html)\n\nTake any model with Armature and animations, scale in object mode (to get big visual results scale to 0.019 or something like that), apply the scale in object mode, play a animation in pose mode.\n" ]

[ "UI: Sequencer/Preview jumps to cover entire preview area\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\n\n- In the Sequencer Preview, select Sequencer/Preview.\n- Adjust regions so both Preview and Sequencer are visible.\n- Adjust the height of the area.\n- Notice that when the area height meets the region height, the Sequencer region jumps to fill the entire area.\nExpected behaviour: that the sequencer region doesn't jump to cover the entire area, but is scaled with the change of the area height. Or in other words that the sequencer region height is scaled to the area height, instead of being fixed. \n{[F10144522](sequencer-preview-jump.gif),size=full}\n\nAn additional annoyance is when changing the area height:\n{[F10144525](sequencer-preview-jump2.gif),size=full}\n", "Can't pan more on the viewport when set to camera view with a wide resolution.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.81 (sub 16)\n\nI can't pan to the side more than this with the camera on the viewport. I wanted to have the cube in the center of the viewport but blender just doesn't pan anymore.\n\nHOWEVER! if I change the ratio of the 3D editor, it works (up to a limit), it is a workaround, but a weird one!\nLike this:\n\n\nOpen the file and try to pan to have the cube on the center of the viewport without exiting camera view:\n[Camera_pan.blend](Camera_pan.blend)\nThis happens with this kind of resolution settings and the camera > sensor fit > set to Vertical (that I need in my project).\n", "Screen flickers / goes black/ red when starting up Blender in fullscreen via startup file.\nOperating system: macOS Big Sur 11.0.1\nGraphics card: Radeon Pro Vega 48 8GB\nProcessor: 3.6 GHz 8-Core Intel Core i9\niMac (Retina 5K, 27 inch, 2019)\nMemory: 72GB 2667 MHz DDR4\n\nBroken: Blender 2.83.9, 2.92 alpha `ba740ad2abc6`, 8dc95f61f3\n\nThe screen flickers/ goes black/ goes red for about 2-3 seconds if the startup file was saved with Blender in full screen. Opening the startup file's again after Blender becomes usable doesn't cause this.\n\n\n- Delete the 2.83 config file or start from Factory Settings\n- Start Blender and the splash screen is displayed correctly\n- Now Click the Green button at the top left hand corner to Maximise the screen to full\n- Save the Default Startup File\n- Reopen Blender and the screen turns red apart from the header bar which is displayed correctly\n- The screen stays red for about 3 seconds\n# The splash screen is now displayed correctly and I can use Blender so far without any issues\n\nRestarted the iMac and restarted Blender with the same red screen error as above\n\n**Workaround**\nPress the Green Button so that Blender is not maximised anymore\nSave the Default Startup File\nRestart Blender and the splash screen is displayed (without the red screen)\n\nThis is my first bug report, so I hope I have filed this correctly.\n\n\nKind Regards,\n\nClayton", "Particle display problem in rendering when using the Time remapping option\nOperating system: Mac Os Mojave 10.14.6 (18G95) and Windows 10 (Last update)\nGraphics card: AMD Radeon R9 M295X 4 Go & Nvidia GTX 1070\n\nBlender 2.80\n\nThere is a problem of particle rendering if we use the Time remapping function which makes it possible to make a film slower by multiplying the number of images of an animation. The particle animation is not continuous, some disappear and then reappear creating a jerky effect.\nThe problem does not appear when launching the animation directly in the software but only by doing a rendering calculation whether it is in film or frame-by-frame mode or movie (with Cycle or Eevee rendering)\n\nIf I leave the time remapping by default (old 100, new 100) there is no problem.[torus particules.blend](torus_particules.blend)\nIf I change the time remapping to have a movie with 4 times more image (old 25, new 100), the problem appears: the particle animation is not continuous, some disappear and then reappear creating a jerky effect.", "Image Editor Blank After Switching Slots, Even If There Is A Render In That Slot\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: (2.80, 79f67acccb36, blender2.7, 2019-03-24)\n\nSwitching the slots in the image editor for the render result (hotkey \"j\") can show a blank image, even if there is an image available in that slot.\nSelecting the render layer in the dropdown menu brings it back.\nThis is irritating, especially since the image is shown right after rendering.\nThis only happens if the compositor is disabled.\n\n- Load [bug.blend](bug.blend).\n- Press F12 to render. The image editor comes up.\n- Press \"j\" to switch to switch the slot.\n- Press F12 to render again.\n- Press \"j\" to switch back to the previous slot. It now appears blank.", "Pack to box region in uv editor\n- Additional property option to the pack islands operator. \n- scales down uv's to fit the selected box\n- Uses new UV editor widget, similar to “render region” in the 3D Viewport, which is activated by the shortcut CTRL+B (deactivate with shortcut CTRL+ALT+B)\n- This feature could also be very useful for the **Unwrap** operator. Let me know if we need a separate task for that\n```\n\n```\n\n\n\n\n**Starting point**\n\nSelected UV islands should be packed into the “box region” that is “drawn” by the user.\n\n\n\n**Desired result**\n\nSelected UV islands are packed to the “box region” that was “drawn” by the user\n\n", "Grid unwrap uv\nMake rectangular uv layout of selected uv’s. If non rectangular/quad topology is selected, it is adjusted to the rectangular/quad topology. \n\n- Filter out continuous areas with gridlike topology\n- Filter out the grid area with the largest area\n- Align the grid area with largest area to a grid like uv layout\n- store current pinning\n- pin grid area with largest area and unselected vertices\n- unwrap the rest of the selected vertices\n- restore pinning\n\n**Starting point**\n\nSelected UV island shoud be automatically aligned to a to U and V as much as possible for the topology which is built in a grid like fashion\n\n\n\n\n**Desired result**\n\nThe topology that is built in a grid like fashion (selected/orange) is aligned to the U and V axis.\n\nThe topology that is not built in a grid like fashion (selected/green), or is not part of the contineous grid like topology with largest area, will be adjusted to fit nicely to the rectified UV’s.\n\nThe dominant grid is the continuous grid with the largest area. Supporting multiple grid areas are not important at the first implementation of the operator\n\n\n\n", "Asset browser group nodes within group nodes duplicates when the mode is \"Append(Reuse Data)\"\n{[F13045686](Screen_Recording_2022-05-02_at_6.51.42_pm.mov)}Operating system: macOs\nGraphics card: Intel HD Graphics 6000 1536 MB\n\nBroken: 3.2.0 Alpha \nWorked: None\n\nUsing asset browser, if you append a group node \nwhen that node is already inside a group node *that you already appended* it make a duplicate with the .001 in the end\ninstead of just reusing the asset when the mode is set to \"Append (Reuse Data)\"\n\n\n>Make a group node, mark that as asset\n>Make another group node, put the previous group node inside, mark it as asset\n>Make a new blend file, link the file of the group node assets \n>Change asset browser mode to \"Append (Reuse Data)\"\n>Drag the second group node inside your file\n>Save the file\n>Drag the first group node inside your file\n>You'll see that it's a duplicate with .001 in the end rather than a reused node.", "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", "Glitches with Curve Fill Node\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked version: never\n\nIf you instance circles or other curves on a curve and you will realize those instances, and you will use the curve fill node on them. There are some glitches or inconsistencies.\nIf you change the scale, the fill node will also randomly decide what should be filled.\n\n\n\n\nTest File:\n[#95518.blend](T95518.blend)\n", "UV Loop Select with Double Click and Shift+Double Click to Extend. Need to triple click to Extend + Border Extend problem\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nBroken: 2.93.1\nWorked: probably none of the versions\n\nInconsistent behavior for selecting multiple edge/face loop.\n\nChange keymap values:\nUV Loop Select: `dbl-Left Mouse`\nUV Loop Select (Extend): `Shift dbl-Left Mouse`\nWith custom key for UV Loop Select, selecting with extend become a problem\n\n\n- Load factory settings.\n- Change keymap as suggested\n- Click on UV Edge or Face selection\n- dbl-click selects loop\n- Shift + dbl-click - does not select the loop, need to click 3 or more times\n[UV_Loop_Selecting_Issue.mp4](UV_Loop_Selecting_Issue.mp4)\n\n", "`Materials` tab not opened at the first time running the script\nOperating system: macOS 10.14.2 (18C54)\nGraphics card: Intel Iris Plus Graphics 640 1536 MB\n\nBroken: (example: 2.80, 89207DF7222A, master, 2019-05-27, as found on the splash screen)\n\n`Materials` tab not open at the first time running the script in attached .blend file\n\n\n* Open the attached .blend file\n* Click `Run Script` the first time\n* It just opens the `Object` tab\n* Click `Run Script` the second time\n* It then opens the `Materials` tab\n\nIt should open Materials tab at the first time clicking `Run Script`\n\n[bug_001.blend](bug_001.blend)", "Mirror Uv\nThere already exists an operator called Copy Mirrored UV Coords. This could be extended to support the features described below\n\n\n- From +X to -X for example (source can be positive or negative X, Y or Z) \n- Options:\n - By object space\n - By world space\n - By topology \n\n\n\n**Starting point**\n\n\n**Desired result**\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", "Opening preferences while rendering causes rendering not to be finished (but computing continues)\nOperating system: W10\nGraphics card: 980Ti\n\nBroken: 2.80 19-03-31\nWorked: (optional)\n\nWhile rendering in a separate window, you can go back to main window, open preferences and boom, preferences are opened in the render window. You can see the progress bar on windows taskbar still going on, everything is being computed, but you are not going to get the full image. You can open the Rendering tab and see your render as 'finished' even though it's still computing. After it finishes - it does not update the image. It's in the state from the moment of opening settings.\n\n1. Click F11 to open rendering window\n2. Start rendering\n3. Minimize/switch windows to the main blender window\n4. Open preferences from the menu\n5. No profit, see desciption." ]

[ "UV editor bug\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nIn UV editor, when choose \"Repeat Image\" window start laggy and image repeats incorrectly\n[2019-12-02_07-17-06.mp4](2019-12-02_07-17-06.mp4)\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", "Cycles not really excluding lights from volume MIS calculation\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nI noticed that cycles, when using volume lights, if we exclude lights from the volume contribution it still affects the sampling of the visible volume lights.[Volumeissue.blend](Volumeissue.blend)\n\nIve included the blend file and also described the issue visually in this thread:\n10982\n\nTo check the issue just turn on and off the Volume Scatter ray visibility and compare the result by hiding the lights instead.\n\nI think this is a serious performance issue in scenes with multiple lights, with some lights contributing to volume while others not, which forces the user to unnecessarily throw a lot of volume samples to get rid of the noise.\n\n\n", "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", "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", "Eevee Motion Blur not applied to AOVs\nOperating system: Ubuntu 18.04\nGraphics card: GTX 2080 Super\n\n2.92 Official\n\nWhen rendering with eevee, motion blur is only applied to the beauty pass. Other passes such as cryptomatte or normal dont have mblur applied, but you can see the steps of the accumulation blur in some passes. This is a huge problem for compositing, it makes all the passes mostly useless.\n\n- animate an object\n- turn on passes\n- render with eevee with mblur on\n- check the aovs, there will be no mblur on them\n\n[aov_motion_blur.blend](aov_motion_blur.blend)", "Eevee: Image Texture Node: Switching the source from \"Generated\" to \"Single Image\" and back to \"Generated\" leaves the shader result as pink color\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\nWorked: Unknown\n\nSwitching the source of an Image Texture shader node from \"Generated\" to \"Single Image\" and back to \"Generated\" leaves the shader result as pink color in Eevee. If it is working correctly, it should display once more the original texture as seen initially with the \"Generated\" setting. The problem is present only when Eevee is used as renderer. With Cycles, the texture is switched correctly to undefined (pink color) when switching to \"Single Image\" and back to the original one if changed back to \"Generated\".\n\n\nLoad the attached .blend file, change the image source on the material texture node to \"Single Image\" and then back to \"Generated\" while Eevee is used as renderer. \n\nFor comparison: Change to Rendered Viewport and Cycles as renderer. Repeat the changing of the image source to observe the correct behavior.\n\n[generated-image.blend](generated-image.blend)\n\n\n\n", "Color management look contrasts apply the wrong gamma when the display device is set to None\nOperating system: window 11\nGraphics card: RTX 2060s\n\nBroken: 3.1 stable, 3.0 stable\n\nWhen the display device is set to None, applying a look contrast results in what looks like a double gamma correction. This doesn't happen when the Display device is set to XYZ.\n \n1. set the display device to None\n2. set the look contrast to any other setting than None or Medium", "Blender Interface Does Not Respect Windows Colour Profiles\nOperating system: Windows 10 Home 1909\nGraphics card: Nvidia GTX 1080\n\nBroken: 2.83.0 on Windows\nWorked: 2.83.0 on OSX\n\nBlender's interface shows incorrect colours on high colour gamut monitors in Windows 10. Any monitor over 100% sRGB is showing colours to be incorrectly vibrant in every panel, including image viewer, 3D view and compositing.\nThis is believed to be due to Blender failing to reference the OS's installed ICC/ICM profile, or the interface entirely lacking any colour management that respects monitor profiles.\nSince OSX has system-wide colour management, this issue is not apparent. Windows does not have system-wide colour management, and apps must perform their own referencing of the installed ICC/ICM profile.\n\nOpen Blender on a high-gamut monitor in Windows 10. Compare to sRGB 100% monitor or OSX.\nError initially produced on a Dell UP2516D high-gamut monitor.", "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", "Smoke darkening/miscoloration with multiple inflow objects\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nHaving 2 or more inflow objects in a smoke simulation, each with its own smoke color, causes darkening and other hue color glitches, even when the two smokes don't mix. At first I thought this was maybe an intended effect, like burning smoke, but with just one flow object the smoke comes out with a proper uniform color.\n\nOpen this file, select the domain and bake the smoke sim to see the darkening, you can see it better in Cycles. You can move the object \"model2\" out of the Flows collection and rebake again with just one Flow object, and see the color to compare\n\nThe attached images use a saturation node on the shader to exagerate the color so you guys can see it more clearly\n\n[BUGREPORT_smoke.blend](BUGREPORT_smoke.blend)\n\n\n\n", "Colection instances can't render if duplicated while instanced on a mesh with array\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.1\n\ncol instances disapear from render view if duplicated when instanced on an array\n\nmake a plane, add aray modifier. \nput anythng in a collection, instance it \nput the instance as child of the aray, toggle face instances on.\nduplicate the col instance: the previous one(s) will disapear from render.\n\nin this blend file, just turn render view and you'll see only the lastest col instance renders.\n\n", "EEVEE doesn't take collection visibility in account with collection instances\nOperating system: Arch Linux and Windows 10\nGraphics card: Intel UHD 620 and NVIDIA GTX 1060 Super\n\nBroken: `3.1 Alpha 43b0ff3054ba`; `3.0 Beta fb0ea94c6303`; `LTS 2.83.19`\nWorked: \n\nWhen baking (cubemaps or irradiance) with visibility collection set, it will ignore collection instances.\n\nTo explain, I've prepared the following screenshot, hopefully it will explain the situation well.\n\n\n\nAs you can see, the cubemap has visibility collection set to *Collection*, where a *Plane, Cube and an instance of Real* are present, however in the cubemap only the *Plane and Cube* are visible, while the instance is left out.\n\nAs a reference, this is how it should've looked like (this was after instances were made real):\n\n\n\n1. Open the appended file\n2. In render settings, under indirect lighting: *Delete Lighting Cache* and *Bake Cubemap Only*\n3. Switch to Renderered view\n4. Observe the missing floating instance of Real\n[eevee_visibility.blend](eevee_visibility.blend)", "Artefacts on render passes Shadow and Diffuse Direct when rendering image texture with zero value in a channel\nWindows 7 Ultimate, 64-bit SP1\nGeForce GTX 750 Ti\n\nversion: 2.79 (sub 1), branch: master, commit date: 2017-10-10 07:26, hash: 8d73ba5, type: Release\nbuild date: Tue 10/10/2017, 10:00 AM\n\nArtefacts on render passes Shadow and Diffuse Direct when rendering image texture with zero value in a channel. The scene is lighted with 3 spots each absolute red, green and blue.\n\n- Create a texture image file with absolute 0 spots in one channel. Or use this one: \n- Create a scene with 3 spots lights, each colored with an absolute red, green and blue color.\n- Add a random object with uvs\n- Assign the texture image file to the object (Tested with Principled BSDF, Diffuse BSDF, Toon BSDF).\n- Add Diffuse Direct and Shadow pass.\n- Render, get this: \n\n**Additionnal infos**\n- Other channels render correctly\n- Scene is lighted only with direct lights, bounces are set to 0.\n- Clamping lowest values to 1 in the texture map resolves the artefact partially.\n- Also shortly tested on unix system.\n- Blender file: \n[bug_cycles.blend](bug_cycles.blend)", "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).", "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: Random attribute in 'Object info' node malfunctions when object with particle system is link duplicated \nWindows 10 Pro 64 bit - i7 6880k MSI GTX1080 X Gaming\n\nBroken:\nversion: 2.80 (sub 44), branch: blender2.7, commit date: 2019-02-10 00:16, hash: 0b6dbbc306b0, type: Release\nbuild date: 09/02/2019, 17:04 - BUT as already logged particle system is broken in this build anyway.\nAlso Broken in \nversion: 2.80 (sub 44), branch: master, commit date: 2019-02-08 14:02, hash: 29922b6ff5f4, type: Release\nbuild date: 08/02/2019, 06:14 WHERE particle system works.\n\n**Short description of error** - Using eeVee\n\nIf you create an object with a material which uses the Random attribute in the 'Object info' node to control a colour ramp which is used to colour the shader in the object's material. Then add some particle hair. Then link duplicate (ALT-D) the object the Random attribute will not affect the colour properly. Infact if you render a number of frames the colour of the objects can flash in some frames to the other colour. Also seems to be the same for SHIFT-D though I have had varied results. If you hide the particle system for an object it's colour becomes the correct one.\n\nAs mentioned above... particles is broken in the Feb 9 build and particles will only display on the selected object and will not render so use Feb 8h build. This bug has been reported by someone else.\nBlend file attached{[F6569635](RandomTest.blend)}", "Object Info node does not return random value in EEVEE\nOperating system: Windows 10\n\nBroken:\n2.80, 60b930af3e73, blender2.8, 2018-12-26\n\nObject Info node does not return random value in EEVEE\n\nIn attached file switch between EEVEE and Cycles\n\n\n\n\n\n[bug.blend](bug.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", "Some meshes causing crash on file opening since Blender 3.4\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.4.0\nWorked: 3.3.2\n\nOpening some files in Blender 3.4 was causing a crash. The source was narrowed down to a mesh that might be corrupt in some way, and upon entering Edit Mode crashes 3.3 too, however 3.2 did not crash on opening the file, thus at least allowing to delete such meshes.\n\n[Amphitheater-cedar3.blend](Amphitheater-cedar3.blend)\nOpen the file -> Crash", "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", "Blender crash on combining textures (intel)\nOperating system: Windows 10\nGraphics card: Intel HD Graphics 4400\n\nBroken: 2.93.2\nWorked:\n\nWhen I tried to combine 2 textures like this blender is crashing.\n  \n\n[Test.blend](Test.blend)\n[Test.blend1](Test.blend1)\n[system-info.txt](system-info.txt)\n[Test.crash.txt](Test.crash.txt)\n[2021-11-12 09-11-32.mp4](2021-11-12_09-11-32.mp4)\n", "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", "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 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", "Render crashes – metal related\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.2\n\nI get some of these intermittently: `Context leak detected, msgtracer returned -1`\nrender ultimately fails (always at around frame 400) with this:\n\n```\nCommandBuffer Failed: cycles_metal_integrator_reset\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nCommandBuffer Failed: cycles_metal_integrator_init_from_camera\n``` \n\n- download and extract the files attached to this issue\n- run `render.sh` + wait until blender crashes\n\n~~using the opengl backend, it works just fine~~\n\n", "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", "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)", "GPencil: Blender crash when file open\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.0 Beta\n\nAs soon as I open attached file Blender crashes. Attached also crash log file.\n\n- Open attached file\n- Change radius (say 0.6)\n- Save file\n- reopen it (Crash)\n[#102930.blend](T102930.blend)", "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", "Blender 3.5.1 keeps crashing on occasion\nOperating system: Mac OS Ventura 13.3.1 (a) (22E772610a)\nGraphics card: Apple M1 Ultra (64-Core GPU)\n\nBroken: Version 3.5.1 (3.5.1 2023-04-25)\nWorked: N/A\n\nBlender occasionally crashes on my new Mac Studio (I used to work on a Windows PC beforehand and never had that problem). I'm guessing it is a saving error.\n\n- Download and open the demo-file `Blender 3.4 – “Charge” Open Movie` from demo-files/\n- Change the engine from Eevee to Cycles GPU\n- Set \"Viewport Shading\" to \"Rendered\" - nothing happens\n- Go back to Solid View - blender freezes\n\nAttached is is a video demonstrating what is happening, but in a few words:\n\nThe same happens with some of my heavy(ish) project in 3.6.0 beta\n\nIn 3.5.1 the same project responds in render view as it should be.\n\nWhen I try to reopen the same project blender doesn’t load the project but either freezes or crashes ( one of these crash logs is also attached)\nI manage to reopen the project after a few crashes.\n\nI hope it helps! \n\n\n", "Crash when 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", "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" ]

[ "Operator bpy.ops.uv.pack_islands call leads to Blender crash\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 3.6.0 Beta\nWorked: Blender 3.5.0 / 3.5.1\n\nCaused by edc12436c66a\n\nCalling of operator bpy.ops.uv.pack_islands leads to Blender crash.\n\nCreate new scene with default Cube then put this simple Python-code into the Console on the Scripting tab:\n```Py\nimport bpy\nobj = bpy.context.scene.objects['Cube']\nbpy.ops.object.mode_set(mode='EDIT', toggle=False)\nbpy.ops.uv.select_all(action='SELECT')\nbpy.ops.uv.pack_islands(margin=0.01) # This call will crash Blender 3.6 Beta\n```", "Crash with bpy.ops.uv.pack_islands()\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 535.98\n\nBroken: version: 3.6.0\nWorked: 3.5\n\nExecuting bpy.ops.uv.pack_islands from script, console or addon will crash Blender, BUT if you use 'INVOKE_DEFAULT' option, it will work as expected.\n\n\n### Reproduce with the Console:\n1. Open Blender and go to Scripting workspace.\n2. Turn the text editor into UV Editor.\n3. Go to edit mode.\n4. Select All in the UV Editor.\n5. In the console editor type `bpy.ops.uv.pack_islands()` and hit enter.\n6. Enjoy the crash.\n\n### Reproduce with a Script with the provided .blend:\n1. Download the provided .blend `TEST_UV_PACK.blend`\n2. Execute the script.\n\n\n\n", "Magic UV: Pack UV crashes Blender\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nThe Magic UV Add-on's `bpy.ops.uv.muv_pack_uv()` operator crashes Blender\n\n1. Select a Mesh object\n2. Switch to Edit Mode\n3. Select all faces\n4. In the UV Editor > Sidebar > Magic UV Panel, UV Manipulation Panel > click on **Pack UV**\n_Blender crashes_\n\n\n\n" ]

[ "Snapping to vertex for Rotation doesnt work for Empty and Pivot Point\nBroken: 2.92, 3.1.2\nWorked: -\n\nSnapping with Rotation enabled doesnt work for Empty and Pivot Point (In Affect Only Origin mode)\nIn attached file,\ncube was properly aligned during rotation with snapping to vertex on the plane (marked)\nbut rotation of Empty produce unexpected results\n\nPlace any type of Emply object or try to edit Pivot Point and rotate it with snapping to certain object vertex to match rotation. Rotation will always produce unexpected results.\n\nVideo demonstration: watch?v=zB9ElkiEG7U\n\n[snapping_issue_T99279.blend](snapping_issue_T99279.blend)", "Blender FBX won't export Mesh Geometry converted from Curve with geometry nodes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\n\nWhen creating meshes procedurally using geometry nodes modifier on a curve object, this object won't get exported by FBX exporter even if the result is a mesh, not a curve.\n\n1. Create a curve object\n2. Add geometry nodes modifier, create new GN node network \n3. Convert the curve to a mesh and add some topology (for example using curve fill)\n4. Export this object using FBX\nResult: The mesh is not exported\nExpected: The mesh is exported\n\n", "Geometry Nodes Inputs `is_animatable` Property Incorrectly Returns False\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0 Alpha\n\nGeometry Nodes inputs' context menus ([WM_MT_button_context ](bpy.types.Menu.html#extending-the-button-context-menu)) incorrectly show the inputs' `is_animatable` property as `False` when the property does accept keyframes (see screenshot, attached).\n\n\n - Open the attached .blend file (attached, below)\n - Run the script in the Text Editor\n - Right-click the Input property of the Cube's Geometry Nodes Modifier\n - Open the System Console to see the `is_animatable` property of `context.button_prop` is `False`\n[is_animatable.blend](is_animatable.blend)", "Curve to Mesh node causes other objects to edge split when not shaded smooth\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Beta\n\nWhen using a Curve to Mesh node, it causes other objects joined to it to be read with each face as a separate mesh island by Cycles (using the Random per Island socket of the Geometry node in shaders). This only happens while using Flat shading AND the Curve to Mesh is plugging into the first position of the Join Geometry node. In any other order it will not happen.\nAlso happens with more mesh objects as long as the Curve to Mesh object is the first on in the Join node.\n\nThe edges aren't actually split, it just seems to be Cycles that thinks they're individual mesh islands.\n\nAdd a grid node and join it to a curve going through a Curve to Mesh node.\nEnsure the Curve to Mesh is the first connection into the Join Geo node.\nAssign a material to the grid and in the shader, view the Random Per Island output of the Geometry node.\n\n[2021-11-06 18-08-29.mp4](2021-11-06_18-08-29.mp4)\n\n[Mesh Island Bug.blend](Mesh_Island_Bug.blend)", "Make Instances Real doesn't work for geometry instances\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0\n\nWhen I want to make instances real on object that has geometry nodes, blender create duplicate of whole mesh, togather with instances, on each place (point) where single instance mesh should be. I have attached screenshots and test scene that reproduces the bug. \n\nOpen .blend file I sent you, hover with mouse over 4 instaced spheres, and pres ctrl+A... select make instances real. You will see that geometry nodes instances are not created properly (whole geometry is duplicated on each geometry node point).\n\nSimilar thing happens when instancing collections, and trying to make them real - the parent relationship/hiararchy is not working. So there is a bug there also.[geom_nodes_bug.zip](geom_nodes_bug.zip)\n\n\n\n\n", "Eevee Group Node ignores socket type conversion (eg. Vector to Float)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha, branch: main\nWorked: N/A\n\nIf the input of a group node is `Float`, but you connect a `Vector`, the group will read the input as a vector instead of a float.\n\n1. Download the Blender file below\n[test.blend](test.blend)\n2. Switch to Eevee, it looks like this:\n\n3. Switch to Cycles, it looks like this:\n\n\nIt seems to be node group evaluation. When ungrouped it looks identical.", "\"Ctrl+Scroll\" to pan horizontally cause issue inside geometry node editor \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.93.0\n\n[ The two actions (Pan horizontally & change any float value of the parameters) are linked to same key combo (Ctrl+Scroll) inside geometry node editor which conflicts,]\n\n[1. Add cube and goto Geometry node editor\n2. add Transform or any node inside geometry node editor.\n3. Try to pan horizontally with Ctrl+scroll. As soon the node hit your mouse pointer while panning, the panning action will stop and it will change the slider value where the node hit the mouse pointer, this cause accidental change in value and other issue. either use Alt+scroll to pan. this same thing should be fundamental everywhere that Alt+scroll to change different tabs and Ctrl+scroll to change values, if possible.{[F10173799](Untitled.png)}]\n\n", "Bevel Vertex selection stops after for planar geometry\nOperating system: Windows 10\nGraphics card: NVIDIA Geforce GTX 1060 3 GB\n\n2.83.2\nBevel Vertex does not maintain the selection for planar objects. For other objects the selection is transferred onto the verts created from the Bevel.\n\nCreate a plane, circle, or any planar object/ \nIn edit mode, Bevel any amount of vertices (ctrl+shift+B) on a plane, circle, or any other type of planar geometry and try to bevel any number of the corners.", "Unify Image Texture node in geometry and shader nodes\nGeometry nodes added a new Image Texture node where the image datablock is a socket.\n\nWe should unify these two nodes. There are some design decision to make regarding how to deal with image users and the frame offset socket, see discussion in {[D12827](D12827).}. ", "Solidify Node\nWe will drop support for Simple mode since the difference is hard to tell and performance-wise better to optimize the Complex mode than maintaining both.\n\nFill and Only options are a bit confusing in the modifier since fill refers to the fill of the rim and has to be checked on to make Rim Only work.\nInstead, I suggest making Fill refer to the part that is not the rim and Rim refer to the rim and make them independent from each other and both true by default.\n\nThe modifier has options for a vertex group as a factor for the thickness and two vertex groups to store the fill and rim geometry.\nvertex groups will be replaced by two attribute string fields for the factor and to tag the rim geometry\n\n", "Node editor: Allow editing geometry node tree without context\nLike the \"Material/World\" toggle in the shader editor, add an option to allow choosing any node group regardless of the context.\n\n", "The 'Vector Rotate' node's 'Angle' input is displayed in degrees but uses radians when something is plugged into it.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\nWorked: -\n\n\nIf I don't have anything plugged into the 'Angle' input of the 'Vector Rotate' node I can set the 'Angle' value to be a number in degrees and the vector will be rotated by that many degrees, e.g. set it to 45 and it will rotate the vector 45 degrees. If I plug a 'Value' node set to the same value, e.g. 45, into the 'Angle' input, it will instead use Radians for the rotation and a 'Math' node set to 'To Radians' is needed between the two nodes to get the same result.\n\nThe expected result (to me) is that plugging in a 'Value' node set to 45 will result in a 45 degree rotation.\n\n\n\n\n[Vector rotate angle bug.blend](Vector_rotate_angle_bug.blend)\n\n1. Open the attached blend file.\n2. Change to rendered shading mode.\n3. Disable or remove the 'To Radians' node to see the incorrect rotation.\n\n", "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", "Animated Values in Node Trees and Geometry Nodes Modifier are not distinguishable \nOperating system: all\nGraphics card: all\n\nBroken: blender-3.0.0-alpha+master.12e8c783535c and below\n\nHello dear Blender devs,\nHello dear Geometry Nodes developers and maintainers,\n\nI did wait some time before reporting this as a \"bug\" as from some perspective this might sound like a feature request. But as there are some, to users unidentifiable names used, I guess this is may very well count as a bug.\n\nWhen working in Geometry nodes it is important to be able to keyframe some values and properties to achieve more controlled and art directable Animation of the Asset. While the setting of keyframes works really well, it gets really complicated to tell the different animation channels apart as they neither show the nodes name nor the nodes Label.\n\n\nOpen attached file, try to figure out which graph in the editor belongs to which Node.\n[geonodes_01.blend](geonodes_01.blend)\n\nFor simplification I added three screenshots each showing one of the three cases I could Isolate where this bug appears:\n\n1.) Animating Node Values in the Geometry Nodes Tree\n\n\n\n2.) Animating Exposed Custom Properties of the Geometry Nodes Modifier\n\n\n\n3.) Animating Node Values inside the Shader Graph.\n\n\nThank you in advance for your evaluation of this bug report\n\nAlex / zuggamasta", "Shader node float precision issue cause different results on CPU and GPU\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\nCPU: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz\n\nBroken: version: 2.80rc2 (2.80 (sub 74))\n\nWhen rendering a mandelbulb volumetric thing on cycles using CPU and GPU, the two have very different ideas on how the scene should look like, making the individual tiles clearly visible. \n\n**Render**\n \n(most tiles are GPU-rendered, note the stray red CPU-rendered tile to the left)\n\n**Blend**\n[mandelbrot.blend](mandelbrot.blend)\n\n**Potentially useful information**\n* #50193 may be the same bug; I opened a new one because that bug doesn't report differences within a single frame, and is from 2016.\n* Since most of this object is endless math nodes, it may be some sort of floating-point thing that works differently on CPUs and GPUs. \n* I was following this tutorial: watch?v=WSQFt1Nruns\n* I noticed that some operations for which I expected single inputs (namely the sines) had two inputs. In the tutorial, the dude said the second input doesn't do anything, but then, that's from the alpha. Maybe taking a 0.5th sine of a value does something strange?" ]

[ "Inconsistent vector rotate behavior\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.1.2\n\nThe vector rotate node uses degrees when using the input directly, but uses radians when another node is plugged to the input.\n\nTest file:\n\n[untitled.blend](untitled.blend)\n\nIt would be great if the vector rotate node always used radians.\n\nThanks and have a great day!" ]

[ "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", "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", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "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", "Native addons lose the \"Report a bug\" button when using a custom Config folder\nOperating system: Windows\n\nBroken: 4.0\nWorked: -\n\nReport by @Todor-CGDive (moved from 104635).\nPre-installed addons have a \"Report a bug\" button. However, if you create a custom Config folder, that button changes to \"Remove\". I am not sure if that's by design but it looks suspicious.\n\n\n- On Windows, go to directory `%USERPROFILE%\\AppData\\Roaming\\Blender Foundation\\Blender\\4.0\\` and copy de `config` folder\n- Past it in the your blender installation directory `/4.0` folder\n\n", "Audio in VSE starts in wrong location when rendered with negative frames\nOperating system: win 10 \nGraphics card: GTX960\n\n2.80\n\nWith negative frames, audio starts on the first negative frame not where it is placed in the VSE when it is rendered out. (same issue in 2.79B)[test-0048-0045.mp4](test-0048-0045.mp4)\nBased on the default startup or an attached .blend file (as simple as possible).\n[VSE starts audio in wrong frame.blend](VSE_starts_audio_in_wrong_frame.blend)", "Wrong reflection in Reflection Plane when Ambient Occlusion is also turned on\nIntel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB\nWindows 7 x64\n\nBroken: 2.8, 2.9\nWorked: n\\a\n\nReflection Plane object produces wrong reflections when Reflection Plane is nearly perpendicular to camera and Ambient Occlusion is turned on.\n\n1. Open provided Blender file, switch to Rendered view and observe how Reflection Plane reflects the opposite wall as almost black.\n2. Disable Ambient Occlusion and reflection will become normal.\n3. I have also noticed that if you change Ambient Occlusion value to something like 40 mm, reflection will be turned into a gradient.\n4. Moving Reflection Plane away from the wall does absolutely nothing, if you switch to the second camera that faces Reflection Plane straight on, back wall will look normal but side walls will become dark.\n[WrongReflection.blend](WrongReflection.blend)\n\n", "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", "bake operator reports uninitialised image that isn't even in use in the shader..\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\ncan't bake due to strange error\n\nopen blend file\nselect object\nselect the baked image texture node in the shader editor\nclick bake in the render setting (leave settings as is)\n\nstrange error pops up saying \n\"uninitialised image \"nightmare0134.png\" from object 'pavement.002'\n\nThis image isn't even in use by the shader.\n\nPS, it seems intermittently not possible to paste screengrabs into this new bug reporter. Also, how to do bullet points and embed video?\n\n", "GHOST:: m_windows not clearing list of fullscreen windows \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 8)\n\nI just wanted to warn you about a potential bug in GHOST when we close a fullscreen window. The problem is that I don't know how to reproduce it in blender official.\nThen this is just if someone is interested...\n\nWhen we close a fullscreen window, GHOST::m_windows list doesn't erase the fullscreen window. Then m_windows list size increases.\nWhen I erase the fullscreen window from m_windows list, it is fixing a crash with our fork of blender (upbge)\n\nI describe the steps to reproduce the bug here: 4fc32990010d5765ba1abd523d57b252be73a657\n\nThis needs to compile restart_hacks branch from upbge github: upbge\n\nThere's a link to the testfile in the commit in mentionned.\n\nJust in case:\n\n[ledi.blend](ledi.blend)\n\n", "Wrong editor type saved in workspace\nOperating system: Win11\nGraphics card: AMD Radeon (TM) Graphics (Included Graphics)\n\nBroken: 3.5.1\nWorked: N/A.\n\nMy properties editor is glitched and keeps resetting to nonlinear animation editor.\n(When saving file and reopening)\n\nIdk how to repreduce it, but here are steps for my blender file:\n1. Switch editor type to properties editor.\n2. Save file.\n3. Close blender .\n4. Open the saved file.\n5. Properties editor switched to nonlinear animation editor.\n6. (When repeating 1-4 with all objects deleted, then its working normally without the switch at restart).\n7. Viedeo: EDgFd6MIzjM.\n\n", "Cycles Regression: Changing \"Start Samples\" in denoiser resets viewport render\nOperating system: Linux-5.14.0-3-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.29.05\n\nBroken version: 3.0.0 Alpha\nWorked: Prior to Cycles-X merge\n\nChanging the `Start Samples` value for the viewport denoiser resets the viewport rendering. This did not happen prior to the Cycles-X merge.\n\n1. Create a scene that has noticeable amounts of noise in Cycles.\n2. Enable viewport denoising.\n3. Enter rendered viewport mode.\n4. Change the `Start Samples` value of the viewport denoiser. You will notice that viewport rendering will reset back to 1 sample. This did not happen prior to the Cycles-X merge.", "3D View - removing Hotkeys for Toolbar/Sidebar throws empty keymap 3D View Generic error\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\n\n3D View - removing Hotkeys for Toolbar/Sidebar in the View menu throws empty keymap 3D View Generic error in the console.\n\n\nOpen Blender. In the View menu of the 3D View remove the hotkeys for Toolbar and Sidebar. Open the Console ...\n\n\n\n", "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", "Support FFMPEG Autosplit filepaths for animation playback\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83.0\n\nIf you enable \"Autosplit Output\" under ffmpeg you cannot view the animation within blender cause \"//\" will be added to the file path.\n\n\n - load up new blender project\n - Set frame range to like 1-20\n - Set output format to ffmpeg, doesn't matter what settings\n - Enable \"Autosplit Output\" just below the container setting\n - In the viewport select \"View/ Viewport Render Animation\"\n - Wait for render to complete then select \"Render/view animation\" (ctrl+F11) \n # note incorrect file path, in my case it reads \"I:\\\\BlenderRenderCache\\\\0001-0020.mp4\"\n\n\n\n" ]

[ "UI bug on Win10 TP.\nWindows 10 TP\n\nBroken: 2.74\nWorked: \n\nAfter last Win 10 build update (10122) appears some offset on the top of UI and on left side (less). So cursor get same offset. On the screenshot lighted up \"File\" menu, but cursor is on black field right on the top. . Same offset in viewport and all others menues.\n\nstart Blender on Windows 10 PR build 10122", "Windows 10 - 2.75 test 1 visual bug\nwindows 10, build 10125 - just updated my windows build and now this happens\n\n\nBroken: 2.75 test 1 + 2.74\n\nVisual bug, the whole blender window is offset, and the cursor doesnt register where the buttons are\n\nopen blender\n\n\n", "UI: Mouse displacement/offset, top black border and thin black border on the left \nWindows 10 Preview build 10122\nNvidia 770Gtx Driver 352.84\n\nBroken: Blender 2.74\n\nUI: Mouse displacement, top black border and thin black border on the left \nWhen i try and click on anything in the window the mouse is offset and clicks 10px below the actual cursor.\n\nWhen i open blender i experience this problem\n" ]

[ "Transform Node Messes Up Alpha Channel Manipulation\nArch Linux\nNvidia 750ti\n\nBroken: 2.79 (Tried 2.8 as well and I have the same issue)\n\nAs referenced here:\n4\n\nWhen I take an image in the compositor and scale it up 2x or whatever and then separate the RGBA and dilate/erode the alpha and use that to set the alpha on the image, it only works within the size of the original image and not the scaled up image. Also even if I use the R, G, or B, it still only uses the size of the original image and not that of the scaled up one.\n\n\n\nCropped if I try to mess with the alpha after a transform.\n\n\nUncropped if I mute my changes to the alpha.\n\n\nAlso I believe that if you scale down\n\n[dilatecropissue.blend](dilatecropissue.blend)\n", "Crash when baking a normal map from procedural materials\nOperating system:\nManjaro w/ KDE\nGraphics card:\nNvidia GTX 1060 6GB\n\nBroken: 2.80 Beta, 5e626e766459, branch: blender2.7, 2019-06-13\n\n\nI've sculpted a high poly model from the lowpoly one - baking normals from that works fine.\nWhen I created procedural materials using Geometry Pointiness, Noise, a painted texture and other sources to create additional normal information - the baking crashes.\n\nHere's the project file. It's huge (781 MB), but compresses very well (turns out the painted texture was wasting a lot of space), without it the file is only 12 MB).\n\n[Barrel_02 08.zip](Barrel_02_08.zip)\n\nNormal map baked from Highpoly model to Lowpoly model:\n\nIf you disconnect the two materials on the highpoly model and just use a default Principled shader, it bakes fine.\n\n\nThe baking process crashes at various stages. First bake crashed after an hour or so, next attempts crashed much quicker.\n\nCrash logs:\n\n[Barrel_02 08.crash.txt](Barrel_02_08.crash.txt)\n\n[Barrel_02 07.crash.txt](Barrel_02_07.crash.txt)\n\n[Barrel_02 06.crash.txt](Barrel_02_06.crash.txt)", "Blender development todo list -- Tools (migrated from wiki)\nNOTE: this is a direct dump of Tools (without cherrypicking the valid items)\n\n\n# Scene\n\n**New scene - Full Copy**\nSeveral things are still not copied or reassigned when using this tool:\n- [ ] Particles - Not even the particle systems themselves, not to mention re-assigning 'objects' pointers to copied IDs too, see #40891.\n- [ ] Textures when they are only used by e.g. modifiers (i.e. not by a material, world or lamp).\n- [ ] Textures used by modifiers are not re-assigned to new copies when possible either (only objects are handled).\n\n# Library System\n- [x] Hard (or even impossible) to relocate libraries that have been moved (#44958). Addressed in id-remap branch, hopefully merged in 2.78.\n- [ ] 'Find Missing Files' does not work with .blend lib files (impossible with current master, easy to do once id-remap is merged, see #47774).\n\n# Transform\n- [ ] API and draw code for manipulator needs to be redone still. For this reason no manipulator drawing happens during transform.\n- [ ] Manipulator click behavior (left-click-release a manipulator axis to enable a transform on that axis -> perform transform and wait for another left-click to confirm. Expected behavior from 2.4x)\n- [ ] Operator parameters in toolbar don't have to be drawn all always, needs cleanup.\n- [x] Transform redo fails when you change mode during transform (use R S G keys).\n- [x] Mirror of rotated objects doesn't always work correct #37928\n- [ ] Numeric input for rotational transform resolves to modulo 360. Should it? #40167 - ''possible fix included''.\n- [ ] Transform along the axis does incorrect axis projection in certain circumstances #40893\n- [ ] Scaling from zero is not possible with 'S' shortcut (#44551).\n- [ ] Transform redo fails when mouse move is required (#50419).\n- [ ] Apply Scale: Option not to scale all object properties (curve radius, empty scale, text scale... etc). \"Scale Properties\" toggle.\n- [ ] Cursor input to calculate rotation can accumulate a small amount of error (impacts bend and rotate) #53590\n- [ ] Armature edit-mode transform proportional editing doesn't work (#53992).\n\n**Transform Snap**\n- [x] Snapping to vertex slide (Taking into account multiple selections)(#48927).\n- [x] Snapping to face local axis doesn't snap the vertex to the face surface (#38438).\n- [ ] Snapping to self doesn't work with proportional edit-mode (#44793).\n- [ ] Snapping doesn't work for Boolean modifier (#35023).\n- [x] Snapping in object mode rotates object around their origin, instead of rotating them around their snapped point (#42362).\n- [ ] Snapping doesn't behave as expected when having several parented objects (#41199).\n- [ ] Snapping between multiple objects can give some working-as-intended, but in practice quite undesirable behavior (using bounding box) (#47171).\n- [ ] Snapping falls back to using a grid, however this isn't clearly communicated<br>(advanced snapping on faces, vertices, etc. only works on move/rot/scale, see #42798).\n- [ ] Snap to cursor and snap to grid could be made to work more consistently: See (#34441)\n- [ ] snap_project individual element on surface of other objects - watch?v=XrEPpHGoKlk&feature=youtu.be&t=1m10s;\n- [ ] Snap does not work for NURB surfaces (#78434);\n\n# DupliObject\n- [ ] There is no good way to control the rotation of objects in DupliFaces option (rotation is computed from face normal (which is good) and first three vertices of the polygon (which is weak, epic fail with e.g. Mirror modifier). See #37365.\n- [ ] Duplifaces don't work well with the mirror modifier, see #37820.\n\n# Curves\n- [ ] Capping front / back -ends of beveled curve doesn't work, see #26136\n- [ ] Constructive modifier kills generated UV mapping on bevelled curves, see #27411\n- [ ] Surfaces Make Segment rotates U/V even when it's not actually needed, see #31480\n- [ ] Couldn't cycle through vertices with the same location using mouse selection, see #36760\n- [ ] Curve tessellation might work not as it's expected to, see #37386, #40171\n- [ ] Curve deform doesn't work if curve is zero-scaled #38907\n- [ ] Nurbs clamp order by total number of points, this should be clamped at runtime #40378\n- [ ] Handling of non-smooth control points with (Bézier/poly) curves in general, and their rotation in particular, could be improved when generating BevelList & Path, see #44393.\n- [ ] In some cases Bevel should prefer \"clip\" behavior over trying to keep constant shape across the path #50720.\n\n# Text objects\n\n- [ ] Font formatting interface should be improved (#49599)\n- [ ] Default Bfont doesn't support russian characters (or any other non-european charset) in text object, while UI does show Russian characters (#53744)\n\n# Metas\n\n- [ ] Some shapes (Cube) for eg. draw far outside the tessellation bounds making them hard to select. see #47455\n\n# Meshes\n\n**Mesh Editing**\n- [ ] Knife & loopcut\n - [ ] Knife/loop cut need to work properly with operator properties/redo\n - [ ] Restore Quad Corner Cut Methods (Innervert, Fan and Path) for Subdivisions and Knifecut\n - [ ] Knife cuts side-on, intersecting the entire face, could be detected and ignored #43816\n- [ ] Mirror edit mesh operator (Ctrl M) fails to flip normals leaving an incorrectly mirrored mesh (turns normals inside)\n- [ ] Add option to disable n-gons usage for tools (might be useful for some usages) (see #31268)\n- [ ] 'Checker deselect' could be modified to work in some cases where it currently fails, (see #34544)\n- [ ] Merge meshes: add option to join UVs (and other CD layers!) by names rather than index (see #36749).\n- [ ] toolbar mesh Extrude operator inconsistency (see #36977).\n- [ ] Shape keys: Enhance memory usage (not storing vcos for unchanged vertices? See blender/blender-addons#39287).\n\n- [ ] Bevel\n - [ ] Better handling of profile=1, profile=0.25, and implement profile=0 cases (see #39132 and #38458 and #40278).\n - [ ] Generalize to handle several manifold sheets touching at a point (see #34678).\n - [ ] Improve clamping code (see #38871).\n - [ ] More options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n - [ ] Treat more cases like \"pipe\" to avoid bulges (see #40258)\n - [ ] Option to have bevel not create n-gons (see bf-funboard thread)\n - [ ] Sometimes leaves degenerated geometry (#48174)\n\n- [ ] DataTransfer/Geometry Matching\n - [ ] Add 'matching' algorithms based on 'similar shape' rather than simple items proximity/raycasting (see #46762 for a usecase) - WARNING: most likely advanced, mathy project!\n - [ ] A review of islands handling could also be useful, current code is rather complex and not so efficient.\n\n- [ ] Discussion\n - [ ] Extrude behaviour on cancel, see (#23492).\n\n**Text Editing (3D)**\n- [ ] When converting beveled text into a mesh - there are many doubles.\n- [ ] Text object requires better integration with the system clipboard, #38556, #46330\n- [ ] Support font kerning (#47725).\n\n**UV Unwrapping**\n- [ ] Settings for pack margin in different operators behaves inconsistently, see detailed description: 039547.html\n- [ ] Remove doubles has an option to Merge with unselected verts, This would be very handy for welding also.\n- [ ] Detect convex mesh without seams on unwrap and print warning.\n- [ ] Unwrapping fails on a particular strange topology (#31145)\n- [ ] Unwrapping for concave polygons is badly supported #41810\n- [ ] Face/edge selection in UV Editor does not work same as in 3DView (#52276).\n\n; Not ported from 2.4x\n- [ ] Click Project from face\n- [ ] Consolidate into one image\n- [ ] Billboard render on active\n- [ ] Unwrapping could run out of stack size for tricky geometry #42524\n\n**Vertex Paint**\n\n- [ ] Undo in vertex (and weight paint) behave differently to sculpt/project-paint modes regarding undo steps #52993\n\n### Sculpt & Paint\n\n**Sculpting**\n- [ ] Check documentation and fix hotkeys which could be useful for artists (or remove redundant hotkeys and update documentation), see #26017\n- [ ] Grab + symmetry can make things shoot off more quickly than they should (strength of movement is being double counted), see #25370\n- [ ] Not all drawing modes supports PBVH drawing, see #32454, #38608, #38609\n- [ ] Not all shading modes are supported for dyntopo, see #34010\n- [ ] Hidden faces are treated as hidden by sculpt tools but when PBVH drawing isn't used, the hidden faces display (and cant be edited), see #33078\n- [ ] Multires modifiers: makes mesh invisible after leaving sculpting mode, see #36591\n- [ ] Multires sculpt: artifacts grabbing between different levels #40465\n- [ ] Dyntopo does not support restoration when aborting a stroke, see #46456.\n\n**Painting (3D)**\n- [ ] Solve projection paint issue when one vertex in a face in behind the view in perspective mode<br>index.php?func=detail&aid=26393&group_id=9&atid=498\n- [ ] Continue to unify paint modes\n - [ ] Consistent brush texture mapping across paint modes (sculpt/tex paint/proj paint).\n - [ ] Consistent brush options, eg. 'Rake' or 'Anchored' in texture paint.\n- [ ] Make paint of displacement texture apply real time on model (optional). (#24657)\n- [ ] Allow view center to work for selected/active face in WPaint mode.\n- [ ] Viewport navigation for painting modes can be improved #48113\n- [ ] Users can perform strokes which apply to a huge number of pixels (by accident) - this could be handled gracefully #52351\n\n**Painting (2D)**\n- [ ] Clone image painting should support the same translation/rotation/scale tools as stencil texture mapping.\n- [ ] Stepped lines in image editor painting, blending should use float coordinates and interpolate (#52610)\n\n\n**Grease Pencil**\n- [ ] Default attach point of GP data is confusing ((#21969))\n- [ ] GP ignores color management ((#50149))\n\n### Materials\n- [ ] Improve handling of linking of materials to Object/Data. Right assigning a material-less data to object the materials from object are gone too (blender/blender-addons#23805, #52484).\n- [ ] Fix EnvMap update, it can depends on many different things in the scene (#41900).\n\n### Modifiers\n- [ ] Make (at least some) generative modifiers to handle custom normals (like e.g. mirror one, see #44058).\n\n**Array Modifier**\n- [ ] Has been re-written to use bmesh, making 2.63 slower then 2.62, There are areas where speed could be improved, for full info see #30695\n- [ ] Textures from cap objects are completely ignored and no way to override them, see #33578\n\n**Boolean Modifier**\n- [ ] Boolean modifier does not preserve vertices/edges data, see #32203, #33548\n- [ ] Issues with degenerated faces, see #30447\n\n**Decimate Modifier**\n- [ ] Limit decimation along seams (UV vertex color, etc), see #32203\n\n**Explode Modifier**\n\n- [ ] Does not preserve UV maps when using Cut Edges option (#46514)\n\n**Multires Modifier**\n- [ ] Only solid draw mode uses optimized drawing\n- [ ] \"Applying Base\" gives spikes on lover levels sometimes, see #35560, #37997\n\n**Bevel Modifier**\n- [ ] Does not preserve edge custom data, see #35314.\n\n**Simple Deform Modifier**\n- [ ] The bend/taper/twist options use fixed axis, add XYZ options would be nice. #33712\n\n**Skin Modifier**\n- [ ] Skin modifier very slow in some cases, see #40770\n\n**Solidify Modifier**\n- [ ] Curves tesselation creates zero area faces which solidify doesn't handle well #52170\n\n**Remesh Modifier**\n- [ ] Mesh data at extreme distance from origin (2**24), crashes #47209<br>''Note, this is a real corner case - yet its a bug because it shouldn't crash.''\n\n### Physics\n- [ ] Allow using multiple baked caches on a single object (having different frame ranges), see #41896.\n- [ ] Bullet: High memory usage for objects that don't have scale applied (#35799)\n\n**Baking**\n\n- [ ] Generic issue: baking ignores making pointcaches when modifier preview has been disabled. Doesn't need fix - but let's keep track of this for future work.\n- [ ] Point caches do not work well with time remapping (example #35968)\n\n**Cloth**\n- [ ] Proper handling of rendered subframes without baked pointcache, for more info see (#21948)\n- [ ] Proper handling of different vertices placed at the same position with \"Soft Body Self Collision\" option turned on (see (#26956)).\n- [ ] Cloths doesn't allow preview during bake (see (#30490)).\n- [ ] Dupli-group cloth in NLA fails (#29838)\n- [ ] 'Emit from: verts' not working as expected when deforming #36237\n- [ ] Collision of hairs doesn't works properly #39219\n- [ ] Memory optimizations are possible for cloth #42577\n- [ ] Cloth pre-roll feature is totally weird and needs reconsideration #40103\n\n**Collisions**\n- [ ] Collision modifier updates it's data structure even if there are no physics that need it (can be slow), a check should be added to make sure the data is actually needed, see (#26965).\n- [ ] Force fields and collision objects are not included in DupliObjects. This is mostly a design decision (duplis being a purely visual feature), but would be nice to support at least in groups. #35264 #36300\n\n**Hair**\n- [ ] Better handling of collisions & force fields for dynamic hair\n- [ ] Wave kink direction is totally uncontrollable, probably there needs to be a way to define hair tangent direction in particle edit mode.\n- [ ] Adding hair in particle mode only uses the deformed mesh, see (#25689).\n\n**Particles**\n- [ ] Particle emission between frames is only accurate for object level emitter/parent animation, for parenting or constraints an interpolation method needs to be implemented, but before this can be done pointcache code has to get some changes too. See (#36516) for more details.\n*; Parent animation is now supported {{GitCommit|c24a23f. Similar issue still persists for non-animated parents (e.g. rigid bodies) though #39923\n- [ ] Reactor particles\n- [ ] Conversion from some old files could be better\n- [ ] Vector blur + particles being born/dying doesn't work properly, see (#23320).\n- [ ] Metaballs don't work with particles when the particle view setting isn't \"render\", see (#25794) for more info.\n- [ ] \"Constructive modifiers before particles\" is still an open issue, but some way to handle this gracefully would be really nice, see (#25838) for more info.\n- [ ] Density of particles can't be animated with animated textures, see (#28212).\n- [ ] Instanced objects do not show in particle edit mode, see (#28431).\n- [ ] Issue with ghosting particles if you don't bake first. (#28116)\n- [ ] Linked groups: Force fields and guides only work if you use \"Effector Group\" feature, set to its own group.\n- [ ] Particle Hair dynamics: stops working after using \"Add tool\". (#30557)\n- [ ] Instanced objects don't draw in Particle Edit Mode. (#31913)\n- [ ] Child particles Interpolated mode only works well for Hair, for other particles it doesn't take particle lifetime into account. (#33390)\n- [ ] Particle emission doesn't support NGons.\n- [ ] Particle Object duplication doesn't work with Mirror modifier (#34705)\n- [ ] Particle systems fail to duplicate for smoke simulation (#34705)\n- [ ] Random distribution of particles fails in specific setups (#35598)\n- [ ] Default point cache step of 10 frames fails in some cases, see #38563\n- [ ] Particles tangent rotation control by vertex group missing, see #35103\n- [ ] Texture doesn't affect grid particles #40404\n- [ ] The particle system needs to be set to 'Newtonian Physics' for texture to influence the size, and with global gravity turned off #28263\n- [ ] Multiple issues with particles rotation #32340, #44088\n- [ ] Particles hidden in viewport reappear during rendering #40463\n- [ ] Particle initial speed is not properly inherited from the parent #41305\n- [ ] Point density textures can not be used to control particles #44901\n- [ ] Particle duplication in general is rather poorly implemented (no relink of used datablocks, no duplication of psettings ID when duplicating objects, …) #45843.\n- [ ] Grid distribution only supports From Dupli Generated, but not UV. Potentially could use nearest face. #48928\n- [ ] Particles aren't spawned correctly, they are sometimes generated at the same location as other particles, or at the object's origin. See #50135 for one scenario.\n- [ ] Particle editmode could have its 'own' [X-mirror] option (and not reuse editmode option). See #53872\n\n**Rigid Body**\n- [ ] Velocities are not cached, which prevents a proper state update when cache has time gaps #50230.\n\n### Image & Video\n\n**Compositing**\n- [ ] DOF Defocus node: fStop close to 128 fails to give good results, stay away from that value! (#24534)\n- [ ] DOF node gives no realistic results as users expect, documentation needs upgrade for it.\n- [ ] Defocus node is very slow when large blur radius is needed, could be optimized somehow (mipmap, summed area table?) (#29481)\n- [ ] Defocus node does not work nicely without a camera controlling the blur radius. This makes external compositing workflows with defocus difficult. At the heart of this is a design conflict, because defocus is not a true postprocessing effect #36745\n- [ ] Fast Gauss (Gabor filter, Young/VanVliet) has bad results for edge cases. Needs image processing guru (#25543)\n- [ ] Check on DPX and ASC_CDL and (#27377)\n- [ ] Map UV makes mapped images blurry, see #31868\n- [ ] Some nodes does not preserve alpha channel replacing it with fully opaque, see #32580\n- [ ] With new compositor, on loading files a compositor doesn't start (for existing buffers), so viewers remain empty as well. #35417\n- [ ] Ghost Glare is of limited use, needs clarification and probably a more sophisticated generic lens flare alternative #30389 #36488\n- [ ] Some node inputs require a single constant value and don't work with image-based per-pixel values (#36585). This leads to confusion when nodes apparently don't work, because nothing prevents linking such variable values into constant inputs. Compositor nodes should keep track of constant values and limited inputs on the node level (also in node groups!).\n- [ ] Compositor gives unexpected results with specific curve mapping due to precision loss, see #36621\n- [ ] \"Full Sample\" merging does not work with the File Output node, sample merging happens only for render result outside compositor. Real-time editing might also be improved to deal with samples better (#36811, #39143)\n- [ ] Accumulation method in the Lens Distortion node causes artifacts on noisy input #37462\n- [ ] Compositor does not support render slots #43260\n- [ ] Scaling down produces artifacts due to lack of ellipse filtering of sampler #51070\n\n**Image formats**\n- [ ] Upgrade our DPX code to read newer or different versions, copy the ImageMagick code? (#24716)\n- [ ] No support yet to output images in user chosen color space. (#37650)", "EEVEE Holdout missing screen space reflections\nOperating system: windows 10\nGraphics card: rtx 2070 super\n\nBroken: 2.8.5\n\nscreen space reflections are not applied to an object from environment that has been held out using holdout button on collection. since the stuff is still there when holdout is applied to background, screen space should still be applied to objects that are not held out.\n\nhere is an example:\n\n\n\n[holdout ssr.blend](holdout_ssr.blend)", "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)", "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.", "Changing UI resolution scale messes up nodes snapping\nOperating system: Windows-10-10.0.25393-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: Never AFAIK\n\nWhen you have a node tree all snapped to grid and is perfectly organized, you move it and it all moves in an organized manner. But say you change your UI resoltuion scale, or line width; the perfectly organized node tree is not organized anymore 🥲. Now it may seem that this bug is really rare, but it's really infuriating when you open someone's file and you mess up the node tree in seconds by just moving.\n\nI created a small video that demonstrates the bug, but basically the steps are.\n1. Create a well-organized node tree that is snapped to grid.\n2. Change the UI resolution.\n3. Observe your node tree not snapped to grid anymore.", "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", "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", "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", "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.", "Grease pencil brush sizes incorrect\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.92.0 Beta\n\nGrease pencil brush sizes are not accurate, not even close. A 500px radius(!) size brush (which should be 1000 pixels wide since we're talking about a \"radius\") has actually about a 50px radius.\n\nOpen a new 2D animation file, increase brush size to the max of 500px, draw a line. Does that look like 1000pixels wide to you? Or ist it me? Maybe I need to work all the way zoomed into the canvas to see the accurate size? How big is the factory canvas?\n\n", "File Browser and Preference Windows open at unusable position/scale.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.8\n\nOn a multi-monitor set up the File Browser and Preferences windows open up on the \"wrong\" monitor and insanely small. They require being resized *every single time* they are opened - does not remember last position or scaling.\n\nScreenshot of both monitors. The main monitor is a 4k and the secondary, on which I regularly run Blender, is a Cintiq 22HD (1080).\n\n\n\n\n\nOn a multi-monitor display, especially one with a 4k as main, open the File Browser and/or Preferences windows.\n\n", "Transform pivot gizmo not scaled properly when drawn\nOperating system: Linux-5.8.0-55-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 2.93.0\n\nThe transform pivot gizmo doesn't use the settings for gizmo size, and can become minuscule.\n\n- Create a cube.\n- Enter \"edit\" mode.\n- Select all & scale 20x\n- Zoom out so the cube fits the screen.\n- Go to \"object\" mode.\n- Press Ctrl + \".\" (period) to switch context and show the transform pivot axes.\nSince the object matrix is still diag(1,1,1), the pivot gizmo will not be scaled up, and will be drawn too small.\n\n{[F10172633](Move_vs_transform_pivot_gizmos.png), size=full}\n\nDetails:\nBefore the \"transform pivot\" is drawn, it is only transformed using the object matrix.\n\noverlay_extra.c:\n```\nDRW_buffer_add_entry(cb->origin_xform, color_xform, ob->obmat);\n\n```\nThis means that for a mesh that is big in \"object local coordinates\", but the object matrix is\nstill ortho-normal, the gizmo will not be up-scaled to a proper size in \"screen space\".\n\nIn other places in the code, preferences -> Viewport -> Display -> Gizmo Size is used.\n\nFor example in transform_gizmo_3d.c:\n```\nvoid drawDial3d(const TransInfo *t)\n ...\n float scale = UI_DPI_FAC * U.gizmo_size;\n \n```\nSeems like a good idea to let the transform pivot axes be controlled by the U.gizmo_size as well\nto make their sizes constant in screen space.\n\n(PS This is not just me. I've been encouraged by other artists in my community to report this.)\n", "Wayland: crash when resizing secondary window and GNOME desktop has fractional scaling\nOperating system: Ubuntu 22.04\nGraphics card: Radeon 6800XT\n\nBroken: 3.4.0, branch: blender-v3.4-release, commit date: 2022-12-06 18:46, hash: a95bf1ac01be, type: release\nWorked: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a936, type: release\n\nWhen performing a window resize operation by dragging the bottom right corner of a secondary Blender window (e.g. Window -> New Window) with the corner resize mouse cursor so that window width and height are changed at the same time, Blender has a high chance of crashing, i.e. repeating the resize operation multiple times will lead to a crash, sometimes already on the first resize.\n\nAlso the resize operation is really slow, taking around one second for the resized window to render after releasing the mouse button. When setting display scaling to 100%, I could no longer crash Blender but the resize operation was still very slow.\n\nThis is running under a vanilla Ubuntu GNOME session with GNOME 42.5. Display server is Wayland with 125% fractional scaling. Screen resolution is 5120x2160 pixels.\n\nThis was never an issue with Blender 3.3.1.\n\n1. Log in to a vanilla GNOME desktop session using Wayland under Ubuntu 22.04\n2. Under GNOME settings -> Displays turn on \"Fractional scaling\" and set the scaling value to 125%\n3. Launch Blender 3.4.0\n4. Open a secondary window with Window -> New Window\n5. Resize the window by dragging the bottom right corner resize window handle\n6. Repeat 5. until Blender crashes" ]

[ "bad Dimension with Objet > Apply > Scale\nwindows 10 with blender-2.80-6cd3a67e36b-win64.zip\nblender 2.8 alpha 2 08/20/2018\n\nwith the default cube\n```\n scale X = 1.0\n scale Y = 1.0\n scale Z = 1.0\n```\nDimensions\n```\n X = 2.0\n Y = 2.0\n Z = 2.0\n```\n\nIn the properties window, change the scale of X, Y and Z to 4.0\n```\n scale X = 4.0\n scale Y = 4.0\n scale Z = 4.0\n```\nThe dimensions is now\n```\n X = 8.0\n Y = 8.0\n Z = 8.0\n```\n\nThen Objet > Apply > Scale\n\nThe scale is now (GOOD)\n```\n scale X = 1.0\n scale Y = 1.0\n scale Z = 1.0\n```\nBut the dimensions in the window propreties are (FALSE)\nDimensions\n```\n X = 2.0 ?????????\n Y = 2.0 ?????????\n Z = 2.0 ?????????\n```\n\nThat sould stay at 8.0\nIn the 3D view, the size of the cube remains at 8.0\n\n", "Apply Scale do not reflect correct dimensions immediately\nOperating system and graphics card: Windows 7 6.1 SP1 / nVidia GT525M \n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nblender-2.80.0-git.3f3eae675aa-windows64\nWorked: (optional)\n\n\nApply scale (Ctrl+A) on any mesh revert back dimensions to defalult dimensions (not really actual dimensions). changes will be seen correctly after moving the cube saving the file and reopening it.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n\n1- Select the default cube, type n and look at Scale and Dimensions ( scale 1 , dimensions 2m)\n2- Scale the cube by 0.6 for example (ie. s 0.6) ( scale 0.6 , dimensions 1.2m)\n3- Apply scale (Ctrl +A) you will see that scale is now 1 but Dimensions are 2m and should be 1.2m)\n2- Move the cube and Undo or save and reopen the file, dimensions will be correct again\n\n", "Sidebar Dimentions do not update after object dimentions are changed in edit mode.\nVerified on both WIndows and Linux across multiple types of hardware.\n\nBlender 2.8 Alpha 2\nWorked: Blender 2.79b\n\nWith the sidebar revealed, changing an objects dimensions in edit mode does not update dimensions in sidebar in object mode. 30 second video of bug here: [Scale in edit mode does not change dimension ](watch?v=nZuWZRXGM3U&feature=youtu.be)\n\n1. Push N to reveal sidebar\n2. Scale object in edit mode.\n3. Go back into object mode. Notice that object dimensions have not been updated to reflect true dimensions.\n4. True dimensions are only updates after scaling again and then undo change with ctrl-z", "Dimension Not properly work\nOS Name\tMicrosoft Windows 10 Home\n\nObject dimension not properly work when Scale applied the dimension not set to the actual dimension" ]

[ "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 when part of mesh is hidden results sometimes in wrong selection of vertices\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 3.2.0 Alpha\nalso broken in the latest official release of version 3.1.2, also broken in 2.93.\n\nBevel when part of the mesh is hidden and the selected points are not all connected results sometimes in the wrong selection of vertices and lines. I have noticed that the selection is wrong if the number of segments in the bevel attrributes is odd.\n\nOn the default startup file do the following:\n1. Edit the default cube, inset the top and bottom face \n2. Inset again, but only 0.001 \n3. Scale the selection in the Z by 0, \n4. Expand the selection (CTRL++)\n\n5. Shift+H to hide everything currently not selected\n6. Only select the top and bottom \n7. Try beveling, play a little with the segments and switch between vertex and line selection, you will see that not all the lines and not all the vertices that should be selected are selected. It seems to be wrong when you try odd number of segments\n\n\n\n\n\n\n\n", "The bridge tool fails in a situation with multiple rows of faces facing each other\nWin10 Pro 64 bit; AMD Ryzen 2700X; Nvidia GTX 1060 6GB; 32 gigs RAM\n\nBroken: hash d1be30f (buildbot build May 4).\nWorked: never\n\nIn a situation where you have multiple rows of faces that face each other across empty space (with other areas where they face away from each other). The bridge tool (even with*loop pairs* checked) is unable to give priority to the direction the normals are facing. The result of this is that instead of getting nice bridges among the multiple rows of cubes, the tool produces faces that overlap and have zero area. As hinted, the*loop pairs* checkbox in this case does not do anything and the result is the same.\n\nOpen the .blend, invoke the bridge operator (the result is the same whether or not \"loop pairs\" is selected.\n\n**blend**\n[IffyBridge.blend](IffyBridge.blend)\n\n[IffyBridge.blend](IffyBridge.blend) (updated blend)\n\nAn additional note; I submitted this issue years ago, but it was never fixed and I couldn't find my old report. If the bug is not going to be fixed, then just close this as a todo item or with a \"won't fix\" tag.\n", "Surface smoothing when sculpting does not respect mirror modifier\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.94\n\nBroken: version: 3.2.0\n\nSmoothing in sculpt mode using Surface deformation does not respect the clipping option of the mirror modifier. This is not the case in the other brushes.\n[0281-0782.mp4](0281-0782.mp4)\n\n1.Creatre an object with at least one plane of symmetry.\n2.Delete one side and add the mirror modifier to fill that same side.\n3.In sculpt mode, try smoothing over the mirror seam using Surface deformation.\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)", "Incorrect Rendering For Weighted/Custom Normals\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.1.2\nWorked: Unknown\n\nRendering in Evee and Cycles appears incorrect when using the Weighted Normals modifier or when manually creating custom normal data. This can be seen quite easily using the \"Normal\" Render Pass in the Material Preview or Rendered viewport shading modes, but it also affects rendering in the normal \"Combined\" mode.\n\n\n1. Delete all but the top and one side (facing the x-axis) of the default cube.\n2. Select the remaining edge and bevel it using a width of 0.1 with a single segment.\n3. In Object Mode, set the object to smooth shading and enable Auto Smooth on the Object Data Properties panel.\n4. Add a Weighted Normals modifier and set it to: Mode = \"Face Area\", Weight = 100.\n5. Applying the modifier does not seem to matter, but it makes it possible to view the vertex normals in edit mode by selecting the \"Display Split Normals\" in the Viewport Overlay panel. The normals on the beveled edges should point straight up and down the x-axis.\n6. Select the Material Preview shading mode and click the drop-down next to it to set the Render Pass to \"Normal\".\n7. Rotate the camera around the object so that the angle is similar to the screenshot (a low pitch). Note how harsh the beveled edge is at the top. This *should* be a smooth transition to \"blue\" as the normals are pointing straight up at this location.\n8. Now rotate the camera so that it is looking directly at the beveled face similar to the second screenshot. The camera should have a pitch of roughly 45 degrees. Notice how the hard edge disappears and there is now a smooth transition from red to purple to blue. This should be the appearance from any camera angle.\n\nAs a second test I exported this object to glTF and brought it into Unity where I could create a shader to preview the normals there. The results were as expected and no harsh edge exists at any camera angle in Unity.\n\n\n\n[IncorrectNormals.blend](IncorrectNormals.blend)", "Triangulate non-planar faces with \"beauty\" method produces faces that point in different directions\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.91.2\n\nTriangulating long faces on this cylindrical objects creates incorrect triangles when Beauty method is selected\n\n1. Open atached file\n2. Select faces as shown on the first image\n3. Apply Triangulate Faces\n4. Observe results similar to the second picture\n\n\n[triangulate_problem.blend](triangulate_problem.blend)", "Flipped one-sided emission in a mirrored object\nOperating system: Linux-5.3.0-23-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 610/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.129\n\n\nBroken: version: 2.80 (sub 75)\n\n\nUsing a one-sided emission material on a mirrored mesh object makes light come out wrong side\n\nWhen using a one sided emission material (Mix Shader with Emission and Transparent shaders as the inputs and using Backfacing Geometry as the Fac), mirroring a mesh object (negative scale on one axis) containing the material causes the light emission to come out of the wrong side, though the material's visible image displays on the correct side of the face.\n(Cycles rendering)\n\n\n\n[FlippedEmission.blend](FlippedEmission.blend)\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)", "Inset faces and Bevel Edge command has bugged interaction with Undo command and shape keys\nOperating system: Windows-7,10\n\nBroken: version: 2.83 (sub 2)\nBroken: version: 2.82 (sub 6)\n\n\nIn edit mode, while selecting a shape key, the Inset operation (I) followed by any other operation (Translating vertices or extruding or whatever), followed by an Undo (Ctrl-Z) command causes the shape key selector to hop to the \"basis\" shape key. This also occurs when using the `Bevel` command.\n\nFrom Default Startup:\n1. Create two shape keys: \"Basis\" and \"Key 1\"on Default Cube. Selection will be on \"Key 1\"\n2. Go into edit mode\n3. Inset a face on any of the existing faces with \"I\"\n5. Do ANY other operation or operations, such as moving a vertex or extruding. The bug occurs with any number of operations done after the Inset command.\n6. Undo (Ctrl-Z)\n7. Observe Shape key information as the undo command causes the selection to switch from \"Key 1\" to \"Basis\".\n8. Keep `Undoing` until you `Undo` the `Inset` operation.\n9. Notice that the shape key selection jumps back to \"Key 1\" as you `Undo` the `Inset`. \n", "Edge Sliding With Snap in Edge/Vertex Mode is Inconsistent.\nOperating system: Linux-5.19.0-42-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.1\n\nEdge sliding in vertex or edge mode behaves like it is in edge perpendicular mode. This is very inconsistent because it snaps as expected in face project mode. Also in edge mode, depending on the edge being snapped to, the snapping mode will either be as expected or in edge perpendicular mode.\n\n\nFrom the blend file try to snap the selected edge to the pink edge in edge or vertex mode. Then try snapping to the annotated geometry as per the mode described in the text editor:\n\n\n", "Bevel disappears when vertex group value is less than 0.5\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.1.0 Alpha\n\nBevel modifier disappears when vertex group value is less than 0.5.\n\n\n - Open file and start decreasing weight value of active vertex in N-panel -> see how bevel is shrinking relatively to the weight\n - Go under 0.5 value -> bevel stops working abruptly\n - Invert vgroup influence inside modifier options\n - Go from 0.5 to 0.0 value -> bevel functioning again\n\n[bevel_vgroup.blend](bevel_vgroup.blend)\n\n", "inset and bevel edits crashing blender 3.x\nThreadripper 1950x 128 gb ram 2tb SSD (home)\nNVIDA 3080 updated to latest drivers\n\nIntel i7 64 gb ram 2 tb SSD (work)\nAMD 6900xt updated to latest drivers\n\n\nHappens on all 3.x versions of blender.\n\nIssue happens on both my home PC (the thread ripper) and my work PC.\n\nStart editing default cube add bevels, insets place some cuts... crashes within a couple of minutes. Happens in all display modes.. mesh, solid, renders. Happens with a smooth display mesh and hard edges. Super frustrating need to save just before doing any of these procedures on any modeling task. Always update video drivers which probably cant be the issue because two different families of video cards in two different machines have the same issue. Been doing this ever since I updated to Blender 3. I assume it's a plugin I installed because I can't imagine why this would happen on two completely different computers. Is there a dump file or something I can send? Here is a video of a typical crash. No dialog box... just blender vanishes in the the middle of editing.\n\n", "Face selection inconsistency with respect to the view\nOperating system: Linux-6.1.0-5-amd64-x86_64-with-glibc2.36 64 Bits - confirmed on Multiple Windows and Mac\nGraphics card: Mesa Intel(R) UHD Graphics 630 (CFL GT2) Intel 4.6 (Core Profile) Mesa 22.3.3 and NVIDIA GeForce GTX 1060 with Max-Q Design and others.\n\nBroken: version: 3.4.0\nWorked: 2.83\n\nYou can't predict how many faces will be selected in solid mode, even for the more basic shapes.\nIs it related to blender/blender#82182 ?\n\n\nAttached a basic video showing the error. The video focuses on the orthographic view, this also happens in perspective mode.\n\nThank you,\nRiccardo\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" ]

[ "Vertex bevel incorrectly flips normals when used on just an isolated spline of vertices\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Quadro 600/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 369.09\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nStart with an isolated spline of vertices -- one in which all the edges have consistent normals (using a screw modifier to revolve the spline around a midpoint will allow you to visualize the surface normals in this case).\n\nIf you attempt to bevel 1 or more vertices on this object, the normals will incorrectly flip to one side of the bevel. This is very problematic; especially now since the subdivision surface modifier is sensitive to the normal direction.\n\nBefore bevel:\n\n\nAfter bevel:\n\n\n[vert-bevel-flip.blend](vert-bevel-flip.blend)\n- Load attached .blend\n - It contains a spline with 6 vertices, revolved around its origin (to create a surface)\n - It has also enabled the Face Orientation overlay\n- Attempt to vertex bevel one or more of the vertices in the middle\n- Notice that the normals become flipped -- with no ability to recalculate (recalculate only seems to work on faces, not this spline)\n" ]

[ "Cycle gpu rendering crashes randomly\nOperating system: Win11\nGraphics card: Nvidia RTX 3070 Ti\n\nbroken: all 3.0 versions\n\nRenders keep crashing randomly when I’m using my gpu with cycles, I updated my drivers, my memory use is okay, I tried to not use denoiser, lower my samples, resolution etc but nothing works, sometimes it render 10 frames sometimes 100 but it can't render my whole animation without crashing (also for animations with low poly count and small textures tiles) \nDon't know how to read the crash log file.\n\n", "Render animation cycles-x bug March 11, 2022\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nRender count from 1 to 1200 frames\n\n\nBlender 3.2.0 Alpha within Cycles-x\nPush the 'Command + F12\" and render animation cause bug between start to end (855 - 1200 frames)\n\nBlender and video file: [Blender 3-2-0 by Kent Davis March 11 2022.zip](Blender_3-2-0_by_Kent_Davis_March_11_2022.zip)\n\n\n\n\n\n\n\nRadeon Pro 575:\n\n```\nChipset Model:\tRadeon Pro 575\nType:\tGPU\nBus:\tPCIe\nPCIe Lane Width:\tx16\nVRAM (Total):\t4 GB\nVendor:\tAMD (0x1002)\nDevice ID:\t0x67df\nRevision ID:\t0x00c4\nROM Revision:\t113-D000AA-931\nVBIOS Version:\t113-D0001A1P-025\nEFI Driver Version:\t01.00.931\nMetal Family:\tSupported, Metal GPUFamily macOS 2\nDisplays:\n```\niMac:\n```\nDisplay Type:\tBuilt-In Retina LCD\nResolution:\tRetina 5K (5120 x 2880)\nFramebuffer Depth:\t30-Bit Color (ARGB2101010)\nMain Display:\tYes\nMirror:\tOff\nOnline:\tYes\nAutomatically Adjust Brightness:\tNo\nConnection Type:\tInternal\n```\n\n", "Render crashes – metal related\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.2\n\nI get some of these intermittently: `Context leak detected, msgtracer returned -1`\nrender ultimately fails (always at around frame 400) with this:\n\n```\nCommandBuffer Failed: cycles_metal_integrator_reset\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nCommandBuffer Failed: cycles_metal_integrator_init_from_camera\n``` \n\n- download and extract the files attached to this issue\n- run `render.sh` + wait until blender crashes\n\n~~using the opengl backend, it works just fine~~\n\n", "Regression: Image rendering fails while viewport rendering is in progress\nOperating system: OSX Ventura Version 13.3\nGraphics card:AMD Radeon Pro Vega II Duo 32 GB\n\nBroken: 3.5.0 Date 2023-03-29 02:56 Hash: 1be25cfff18b \nWorked: 3.4.1 Date 2022-12-19 17:00 Hash 55485cb379f7\nCommandBuffer Failed: cycles_metal_integrator_compact_shadow_states\n\n* Load file provided\n* Set ViewPortShading to MaterialPreview\n* Then select ViewPortShading to Rendered\n* While the viewport is rendering Select Render Image.\n\nThis will often cause the error. It may take an attempt or two but more likely to happen after at least one attempt.\n\nIn some case blender will throw the error in both the viewport and in the image window. In some cases...Blender will hang and require you to force quit. At other times it will crash the OS. \n\nThe larger the scene the more drastic the failure. In this simplified file it typically will recover.\n\n", "Blender crashes 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 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", "Shader not working on Mac blender 3.5 - works in Windows\nOperating system: macOS-13.3-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.0\n\nI have been trying to install the Weight Paint Tools paid addon weight_paint_tools?layout=profile&recommended_by=library\n\nThis worked fine for years, up till 3.5, now it crashes upon activation. The developer has attempted to update it for metal, but it still wont work. He's sent me a simplified script that he says should work without errors.. but still errors out. See attached blend file.\n\nRun the script\n\n\nRun the script\n\n", "Crash while baking the Line Art modifier\nOperating system: Windows 11\nGraphics card: RTX 2070\n\nBroken: 7c2dc5183d03\n\n\n\nI get regular crashes when baking Line Art modifier in relatively complicated geometries. \n\nI can't provide my project file. I am hoping that the crash log will give insight into this bug.\n\n", "Cycles GPU Out of memory in viewport Metal Backend\nOperating system: macOS-13.4.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 560X 1.2\nAdditional Hardware : eGPU Razer Core X with AMD Radeon 5700 XT\n\nBroken: version: 3.6.0\nWorked: version 3.3.8 \n\nGPU Out of Memory in cycles with a simple scene one object and one Sun Light\n\nLoad Scene \nSwitch to render mode \nNavigate in the scene in rendered mode changing the view, after some pan and zoom the error gpu memory error is showed and blender crash. \n\nSame scene in blender 3.3.8 is working fine.\n\nBlender 3.6.0 is using 11.55 GB of Memory\nBlender 3.3.8 is using 566 MB of Memory with the same scene in rendered mode.\n\n", "Crash using blender_debug_log.cmd and \"Reload Scripts\" in Cycles preview render\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nLoading Blender with blender_debug_log.cmd, it crash immediately when I try to reload the scripts if Cycles is running. This is not happening when launching blender.exe \n\nLaunch blender 2.8 using blender_debug_log.cmd.\nIn the view 3d, choose Cycles as render preview.\nIn the search bar, look for \"Reload Scripts\" and click on it.\nBlender Crash.\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n", "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)", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "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", "iMac CRASH through Blender 3.6.0 ASSET.\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 3.6.0 Alpha\n\niMac CRASH through Blender 3.6.0 ASSET.\n\nMacOS 13.4\nBlender cause bad memory leak through ASSET open.\ndemo-files/\n\nClick ( Cube Diorama )\nthen\nOpen Cube Diorama.alend\ncause bad memory leak cause iMac crash.\n\n\nSee my youtube. A2d0Wu8ig-w", "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?" ]

[ "Instant Crash activating Cycles GPU Rendering on OSX with AMD Radeon Pro 580\nOperating system: macOS-13.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5.0 Alpha\n\nI use the dailey build, self-compiled, but also in the dailey build from blender.org\n\nSine some days I get an instant crash when I activate GPU for Cycles and click render. Worked before without any problems. Tested it with Metal Viewport off (deleted Prefrences) or on. The Metal Viewport itself works.\n\nDefault scene\nGo to Render settings\nSet Cycles with GPU Rendering\nClick Render => Crash\n\n" ]

[ "Duplicating a passive body can make the child meshes not update\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 466.27\n\nBroken: version: 2.93.0 Beta\n\nWhen duplicating a passive rigid body and changing that child to an active rigid body, the child's mesh will not update.\n\nSet default cube to passive. Duplicate it and set the child to active. Play and watch \"nothing\" happen.\n\n[2021-05-19 19-00-19.mp4](2021-05-19_19-00-19.mp4)", "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)", "Vertices will always merge when \"Clipping\" is checked on a mirror modifier\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: Not sure\n\nDespite \"merge\" being unchecked, if you have clipping checked on a mirror modifier it will behave as if merge is turned on.\n\n1. Scale down the default cube to 0.1. Apply scale.\n2. Add a loop cut down the middle and delete half the mesh\n3. Add a mirror modifier and turn off merge\n4. Select the edge loop you just created and move it very slightly off center (so there's a gap)\n5. Turn on clipping (but leave merge off)\n6. In edit move move the edge loop again and you'll see it auto-merge the vertices close to the edge. If you reduce the merge distance it will not merge them, showing that when clipping is enabled it will auto merge verts despite that being unchecked.\n\nAttached example:\n[clipping demo.blend](clipping_demo.blend)\n\n", "The viewport may update at 0 FPS while navigating, until the mouse is released.\nOperating system: Windows 10\nGraphics card: RTX 3080 Ti\n\nBroken: 3.0.0\nWorked: 2.92.0\n\nWhen working in sculpt mode on a model with multires modifier, the viewport may update at 0 FPS while navigating, until the mouse is released.\n\nUsually when navigating in sculpt mode on a model with multires modifier, the model will switch to a low poly version while navigating. When this bug is happening, the viewport remains frozen and the high poly model remain on screen until mouse is released.\n\nThe bug will be temporarily fixed upon clicking on another application or resizing the blender window.\n\n1. Shift+A to create a plane\n2. Ctrl+E and subdivide it 4 times.\n3. Attach multires modifier onto the plane.\n4. Subdivide it 6 times with the multires modifier.\n5. Use sculpt mode and sculpt without moving the view for around 1~2 minutes (I used a wacom tablet. Using the sculptDraw brush, I added / subtracted (hold ctrl) from the mesh, also using smoothing brush (hold shift) to smooth certain parts, and undo (ctrl + z) multiple times to simulate a normal working environment.)\n6. Try to pan or rotate the view around.\n\n\n\n**I found another way to trigger this bug, and it's not strictly related to sculpt mode.**\n(Tested on blender 3.1.0 beta 03b57d3973)\n\n1. Click around with a Wacom tablet.\n2. Pan the camera around with a Wacom tablet.\n3. Pan the camera around with a mouse.\n\n\n[sculpt mode bug.blend](sculpt_mode_bug.blend)\n\n[2022-01-17 04-48-11_Trim.mp4](2022-01-17_04-48-11_Trim.mp4)", "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", "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", "Inconsistent behavior of the Subdivide Edge Ring and Subdivide actions on meshes with shape keys\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 511.23\n\nBroken:\n3.2.0 Alpha 2022-05-01 a5644f9a28ea\n3.1.2 2022-03-31 cc66d1020c3b\n3.0.1 2022-01-25 dc2d18018171\n2.93.9 2022-04-19 31712ce77a6a\n2.83.19 (can't find build details)\n\nWorked: -\n\nThere's an inconsistent behavior of the Subdivide Edge Ring and Subdivide actions on meshes with shape keys.\n\nWith Subdivide Edge Ring, no matter what kind of interpolation and profile factor you use, the one applied to all other shape keys will use \"Linear\" and \"0\" respectively.\n\nWith Subdivide, if you use it on the Basis shape key, all other shape keys will inherit half of the transform of the \"smoothness\" setting, and they will be transformed in some undefined manner by the \"fractal\" setting as well. If you use it on non-Basis shape key, in addition to the described behavior with remaining shape keys, the Basis shape key will always use the default settings (smoothness and fractal = 0).\n\n**Exact steps for others to reproduce the error / sort-of-transcript of the video**\nwatch?v=s9dPcdHOlpo\nIf you use the Subdivide Edge Ring, leave the default settings, and go through the shape keys, you can see that the positions of vertices are slightly off between the current/modified shapekey and others.\nHowever, that changes when you change interpolation to \"Linear\" - then they start being the same.\nWhen you go through various options it seems that the only thing applied properly across all shape keys is the number of cuts.\nAll shape keys other-than-the-active-one seem to always be using the \"Linear\" interpolation, and profile factor = \"0\"\nFrom my tests it doesn't matter which shape key you use this action on - it will always have the same effect between the current shape key and all other.\n\nNow, there's something even weirder goin on with the regular Subdivide.\nIf we Subdivide the mesh with default settings, it will look the same in all shape keys - that's great.\nHowever, if we change something, then the mesh across shapekeys will look different.\nAs a general rule, if we Subdivide a shapekey like Key 2, then the Basis will look like it was Subdivided with the default settings instead of the chosen ones (besides the number of cuts), but all other shape keys will also be modified, just in a different way than the active shapekey.\nFor example, if we change the smoothness of our Subdivide, then other shapekeys will look just \"less modified\". If we check the coordinates of the vertices, then we can see that in Key 1 they are transformed exactly half-way to their position in Key 2.\nHowever, if we use the Fractal setting, then the results are different: The Basis is still default-Subdivided, but the vertices of Key 1 are not just halfway there to the positions of Key 1 - they're completely different.\nOn a final note, with regular Subdivide, if, instead of Subdividing Key 2 you did that to the Basis, then both Key 1 and 2 would look like Key 1 in my example. There would be no shape key that stays with default Subdivide settings.", "Wrong UV after Vertex Slide or moving mesh with Correct Face Attributes\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 535.98\n\nBroken: version: 3.5.1\nWorked: unknown\n\nAfter Vertex Slide with \"Correct UV\" checked, or after moving mesh with \"Correct Face Attributes\" UV mapping is wrong. Vertices in UV get split and wrongly offset.\n\n\nExample 1\n1) Open attached Blend file\n[wrong_uv.blend](attachment)\n2) Locate objects plane01_small and plane01_larger. They are identical models with the same UVs. Just one is slightly smaller and one larger and they have different position.\n\n3) Now we will be vertex sliding this vertex to the diagonal one with snapping on vertex on (see picture) with \"Correct UV\" checked. See that the larger model has UV correct, but the smaller one has wrong UV after the vertex slide\n\n4) now go back (Undo) and lets try grab/move with snapping instead of vertex slide. Be sure to have checked ON \"Correct Face Attributes\" and \"Keep Connected\" in Tool Settings/Option - see picture. Now UVs are wrong in both cases\n\n\nExample 2:\n1) Lets look at plane02_01 and plane02_02. They are totally identical duplicated objects (not instances) just with different position.\n\n2) Vertex slide works OK in both cases here, so lets try Grab/move with vertex snapping and \"Correct Face Attributes\" + \"Keep Connected\" ON again. Here result UVs are OK in case of plane01_02 but wrong in case of plane01_01\n\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", "Many Grease Pencil operations cannot be performed without an \"Active Layer\", though it shouldn't be needed\nOperating system: Linux 64-bit\nGraphics card: GTX 1080 ti\n\n2.93.5 and also 3.1 alpha (Nov 19th build)\n\nWhen working in a scene with more than one GP object, it's easy to go into edit mode for one GP object while having selected the layer of another in the dope sheet. Selecting a GP stroke may automatically select a layer for a different GP object. When the active GP object in edit mode has no active layer, a lot of operations are disabled, and it makes no sense as to why they should need an active layer at all.\n[GP_bug.blend](GP_bug.blend)\n - Open the attached file, which is in Edit Mode for the Suzanne GP object on the left\n - With no active layer belonging to Suzanne selected in the Dope Sheet, not a single operator in the \"Stroke\" menu can be performed. Selected strokes can be transformed and extruded, but they cannot be assigned materials or subdivided. This is odd because none of these operators seem like they should need any particular layer to be selected\n # Deselect all layers in the Dope Sheet and select a stroke. A layer is automatically selected, but it belongs to Suzanne.001, which is also baffling.\n\n", "Mirror threshold too high, values less than 0.00002 are snapped to center\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.83.3\nWorked: 2.79b\n\nBlender 2.8x has a bug that forces it to snap to the YZ plane with a value less than 0.00002.\nThe above is occurring with the snap off.\nThe bug occurs even if the vertex's X coordinate is moved to more than 0.00002.\nDuplicating the object does not eliminate the bug.\n\n3D Viewport / Edit Mode.\nCreate an object with the following vertices:\n```\nObject-1 = {\n Vertex-A x = 0.00002, y = 0.00005, z = 0.0\n Vertex-a x = -0.00002, y = 0.00005, z = 0.0\n Vertex-B x = 0.000019, y = -0.00005, z = 0.0\n Vertex-b x = -0.000019, y = -0.00005, z = 0.0\n}\n```\n3D Viewport / Edit Mode / Tool / Options / Mirror X [enable].\n3D Viewport / Edit Mode / Snap [disable].\nSelect Vertex-A and Vertex-B.\nMove Vertex-A and Vertex-B.\nBlender 2.8x has a bug that forces it to snap to the YZ plane with a value less than 0.00002.\n\n3D Viewport / Object Mode.\nDuplicate the Object-1 to obtain the Object-2.\n3D Viewport / Edit Mode.\nMirror the vertices of object 2 as if they were object 1. This causes the same problem.\n\nEnlarge the Object-2 sideways.\nMirror the vertices of Object-2. The same problem still occurs. The problem occurs even if the Vertex-B x-coordinate is greater than 0.00002 after magnification.\n\n\n[X-Mirror_bug.blend](X-Mirror_bug.blend)\nThe objects in the X-Mirror_bug.blend file are very small, so zoom in on the view to the maximum size.\n\n\nThis is a 2.79b file with the X-Mirror working correctly:\n[X-Mirror_2.79b.blend](X-Mirror_2.79b.blend)\n\n\nThe difference in x-mirror behavior between 2.8x and 2.79b is shown in the following video:\n[Blender 2.8x BUG_X-Mirror.mp4](Blender_2.8x_BUG_X-Mirror.mp4)\n\n[Blender 2.79b X-Mirror.mp4](Blender_2.79b_X-Mirror.mp4)\n\n\nIf it is unintentionally aligned to the YZ plane like 2.8x, it will not be possible to edit it (if this behavior is a specification, it will be useful if you can implement it as a function separate from the mirror, align it to the YZ plane, and set a threshold to align).\n\n**When importing model data from the outside and editing a mirror, all vertices with an X coordinate of less than 0.00002 are already implicitly aligned to the YZ plane, so editing with an X mirror is no longer possible at all. Hence, until this bug is fixed, edits involving X mirrors should use 2.79b.**\n", "Wrong interaction by extrude region with 2 cube's faces\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.22\n\nBroken: version: 3.1.0\n\nWhen extrude the \"z\" and \"-x\" faces of cube they extrude up \n\n* Create a cube\n* Choose edit mode\n* Select \"z\" face(top of cube) and \"-x\" face\n* Use Extrude Region or press E\n\n{[F12930516](image.png), size=full}\n\nThanks!", "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.", "Linked Text Object Data Bug\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.42\n\nBroken: version: 2.93, 3.0.0\nWorked: -\n\nText objects with linked object data behave strangely. Some letters change their shape, which may vary from instance to instance. (see uploaded image)\nMaybe i´ve got the bug is because i use the Small Caps format.\n\n\n1. Create several same text Objects (you maybe should use Small Caps format in them)\n2. Link their Object Data\n3. Try to switch several times between Object and Edit mode and you will see the bug. It occurs everytime on different letter. And every instance of the text looks often different then the others.\nI am attaching the Blend file\n[bug.blend](bug.blend)\n", "Poly Build Tool: Editing poly build keymap causes poly build tool to not work properly\nWindows 10\nGeForce GTX 1080\n\nv2.81 Alpha\nDate: 2019-09-10 15:07\nHash: 8f55794c0e80\n\nWith a default blender open, edit the poly build keymap. The tool doesn't work properly with the new key assignment. \n\nFor example, switch 'face at cursor move' to shift + left mouse, and 'poly build delete at cursor' to ctrl + left mouse." ]

[ "latest build of 2.8 the proportional circle\nOperating system: Win 10 Pro\nGraphics card: GTX 750 TI\n\nBroken: ( 2.80, 546e20f5a2c0, master, 2019-4-30)\n\n\n\nproblem with the latest build of 2.8 the proportional circle appear in every mode and with any tool and any operation even while the proportional not active the circle appear on duplicate and with any thing. \n\n\n\n and from any thing", "Duplicate Function not working as usual\nOperating system: Windows 10 Home\nGraphics card: Nvidia GTX 1080\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender-2.80-e8daa615704b-win64\nWorked: (optional)\n\nDuplicate function not working as usual\n\nBased on the default startup or an attached .blend file (as simple as possible).\nJust Duplicate \"Default Cube\" with Shift D or Duplicate Linked with Alt D\nNow drag with mouse the new duplicated cube, and original cube is affected too!", "Duplicating objects enables proportional editing\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.01\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\nWhen using shift + D to duplicate an object, proportional editing is enabled no matter the state it was previously in, meaning you end up moving both the duplicate and its original, unless you right click to cancel the move and then grab (G) the new object.\n\n- Create/select an object\n- Shift + D to duplicate\n- Both objects will move together due to proportional editing\n\n\n", "SHIFT D to Duplicate is activating proportional editing and moving the primary object from its initial place\nOperating system: Windows-10-10.0.14393 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.5063\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\n\nShift D is duplicating objects with Proportional editing activated by default. \nFor 3d objects shift D is duplicating the object but moving the primary object along with the duplicate.\n\nIn case of grease pencil, unable to duplicate key frames using Shift D it is only working as move key frame\n\n\nOpen blender with general template\nselect the cube\npress shift d to duplicate and move the mouse\nobject is duplicated but the location of primary object is also shifted to last confirmed location of duplicate object.\n\nIn case of grease pencil key frames select any keyframe and press shift D it only moves the key frame. I think key frame is getting duplicated but as both the keyframes are in one time frame the end result shows only 1 keyframe.\n\n", "Shift D enabled proportional move\nOperating system: Windows 10\nGraphics card: 1080\n\nBroken: 546e20f5a2c0\nWorked: \"a few months ago...\"\n\nSimilar to #64013, pressing Shift D also enabled proportional move, even though that setting doesn't seem to be enabled.\n\n1. Add a cube\n2. Press Shift D\n\nResult:\nBoth cubes will now move and you can see the proportional editing circle indicator and resize it.\n\nExpected result:\nOnly the duplicated cube should move, and if the proportional editing icon is greyed out nothing else should move." ]

[ "driver on an NLA animated time strip isn't purple and cannot be removed\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.93.0 Alpha\n+ version: 2.92.0\nWorked: never\n\nWhen adding a driver on an NLA animated time strip value, the value does not turn purple, and cannot be remove.\nDon't know if it's related or not, but you also cannot delete/clear keyframes on that particular value aswell. Should i do another bug report ?\n\n(see video attached)\nanimate the default cube (example : revolution on Z axis, from frame 1 to 250)\ncreate an empty, add a custom property, animate that property\ncopy the custom property as a new driver\ngo to the NLA, push down the cube action, go to it's strip option and check \"animated time strips\"\npaste the driver on the \"animated time strips\" value\n[bugreport_drivercolor.mp4](bugreport_drivercolor.mp4)", "IDproperty subtype can cause Blender UI to throw exception\nOperating system: Win 10\nGraphics card:\n\nBroken: example: 3.3.1 LTS, b292cfe5a936, master, 2022-10-04\n\nAfter editing an IDproperty subtype through python interface, the blender GUI becomes broken when trying to edit the property\n\nobject.id_properties_ui(\"prop\").update(subtype = ***) will accept NONE', 'FILE_PATH', 'DIR_PATH', 'FILE_NAME', 'BYTE_STRING', 'PASSWORD', 'PIXEL', 'UNSIGNED', 'PERCENTAGE', 'FACTOR', 'ANGLE', 'TIME', 'TIME_ABSOLUTE', 'DISTANCE', 'DISTANCE_CAMERA', 'POWER', 'TEMPERATURE', 'COLOR', 'TRANSLATION', 'DIRECTION', 'VELOCITY', 'ACCELERATION', 'MATRIX', 'EULER', 'QUATERNION', 'AXISANGLE', 'XYZ', 'XYZ_LENGTH', 'COLOR_GAMMA', 'COORDINATES', 'LAYER', 'LAYER_MEMBER'\n\nBut anything other than 'NONE', 'COLOR', 'COLOR_GAMMA', 'EULER', 'QUATERNION' causes Blender UI to throw exception when editing the property.\n\n- open [bug.blend](bug.blend)\n- see the Cube's custom object ID property \"prop\" and that it's editable through the 'gear' button.\n- Change the type to `Float Array`\n- run the included script in text editor or run `bpy.data.objects[\"Cube\"].id_properties_ui(\"prop\").update(subtype='ANGLE')` in python console\n- see the property again in UI and try to edit it.", "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", "Simulation Nodes: show bakes in outliner\n_No response_\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", "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", "Custom property settings not preserved when changing its type\nBroken: version: 3.0.0 Alpha\n\n- Add integer property to default cube with a custom min/max/default value, and Is Library Overridable enabled.\n\n- `C.object['prop'] = 2.0`\n- The property's settings are all lost.\n\n\nIIRC, before the refactor, an integer property could have floats as its min/max so this would be allowed. Might be a bit of a pain point with the new system, but I think doing a best effort conversion between types would be nice when possible (even if some data is lost going from float to int, losing some data is better than losing all data).\n\n[#91256-2021-09-08_12.54.49.mp4](T91256-2021-09-08_12.54.49.mp4)\n\nTest File:\n[#91256.blend](T91256.blend)", "Renaming custom property doesn't update its animation data\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77\n\nBroken: version: 2.90.0 Beta\nWorked: Never (2.8+)\nCombining the name change of a CustomProperty with a key then these parameters create an incorrect name and a new obeckt in the Graph Editor/Dopesheet.\n\nadd cube\n\nadd Custom Properties\nset key inside the custom Properties \n\n\n\nedit Custom Properties add some letters /ok\n\n\n\nset key on another frame inside the Value.\n\n\ngo inside the dopesheet/grapheditor \nall new created/names inside the Properties are listed.\n\n\n\n\n[rename_key_Custom_Properties.blend](rename_key_Custom_Properties.blend)\n", "Transform generalized custom-data correction support\n\n**Motivation:**\n\nHaving to manually adjust custom-data is tedious\nwhile there is a UV correction option,\nit's limited to vertex & slide.\n\nThis proposal is to generalize the option so it can be used for any\ntransform mode.\n\n\n**Solution:**\n\nThis proposes to add two kinds of custom-data correction methods.\n\n- Correct based on surrounding geometry, this is suitable for\n```\nvertex & edge slide.\n```\n *The existing logic for vertex & edge slide can be used here.*\n\n- Project Custom-Data\n\n```\nThis would project geometry onto the surfaces of the original mesh\nto calculate the custom-data.\nThis would allow geometry.\n```\n\n```\nThis could be used for other transform modes besides vertex/edge slide.\n```\n\n\n**Limitations:**\n\nThis option works best when adjusting small regions of geometry and often won't work well moving large regions of faces.\n\nThere is a limit to how much UV's can be corrected in this case without re-unwrapping/projecting\n*(which is beyond the scope of this proposal).*\n\n\n**User Interface:**\n\nThese would be shown in the tool options panel, we could keep the transform option too (although this isn't essential).\n\n----\n\nThere is a risk that users accidentally leave this enabled and transform their UV's when moving the geometry.\n\nSince we have other fairly obscure options (transform origins for example), it may be best to show these are enabled while transforming (as we do for auto-keyframe).\n", "VSE unkeyed transforms in preview persist in cache\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken: version: 3.3.0 Alpha\nWorked: never\n\nVSE unkeyed transforms in preview persist in cache.\nIf transforms occur on a property that has an fcurve already (but no keyframe is actually created on that frame), this transform will remain in the cache for that frame.\nThis does not get invalidated on timeline scrubbing / frame change.\n\n(this report was split from #98015 (VSE strip transforms do not animate correctly and persist after clearing the animation) since multiple issues came up in that report)\n\n[VSE_keyframing.blend](VSE_keyframing.blend)\n\n- open .blend\n- create a keyframes for rotation on frame 1\n- go to frame 10\n- rotate in the `Preview` again and confirm the rotation (but dont create a keyframe)\n- scrub the timeline\n- since this change on frame 10 was not keyed, it should vanish, but it doesnt, it remains in the cache\n- note: when the strip in the `Sequencer` view gets moved, the issue goes away (assume the whole cache gets invalidated then)\n\n\n", "error in custom view3d.move Keymap Setting\nOperating system: Windows11\nGraphics card: It doesn't matter\n\nBroken: up to 3.5.1\n\n\n\nBecause I often use the 2D features in Blender, and the pan view function in Blender is not very convenient (requires using Shift + MMB), I made the settings as shown in the picture to add a new pan view keymap to Spacebar + LMB. In the normal object mode, I can indeed pan the view by using the new shortcut, but once I switch to any other mode, this shortcut key will be disabled. \n\nBased on the default startup or an attached .blend file (as simple as possible).\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", "Particle don't emit curves/text in 3.0 beta \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.39\n\nBroken: version: 3.0.0 Beta\n\nCaused by b9febb54a4.\n\nParticle don't emit TEXT\n\nNo particles text from 3.0 [Particle_Text_NOT_Working.blend](Particle_Text_NOT_Working.blend)\n", "Scale and rotate using individual origins as the transform pivot point is useless on poly and NURBS spline types\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.1.0 Alpha\n\nWith Bezier curves, using scale resizes the handles for each control point, but with paths and meshes converted into curves does nothing since they don't have handles. It would have been more useful if it used the median point for each isolated spline instead. That is what I expected it would do.", "NLA: Moving Strips Auto Changes Between Hold and Hold_Forward\nBug Report #42808 (NLA: Moving one strip resets extrapolation on other strip) #45854 (Hold forward is reseted in NLA)\n\n**Source of Problem**: #42808#843296 \n\n**Solution:** I think the code enforcing this can be removed. I don't think this restriction was ever necessary. When an animator uses a Full Replace Hold strip above other strips, it's expected behavior that it occludes the lower strips. That's what a Full Replace strip is supposed to do. Full means strip influence = 1. For consistency, we'll have to add support when a strip has extrapolation `None` leading to a strip with `Hold`. We'll also have to add support for `Hold_Backwards` extrapolation for completeness. In the case of conflicting adjacent strips (`Hold` into a `Hold`), we let the first strip have priority which leads to the next strip as behaving as `Hold_Forward`.\n\n**Potential Problems with Solution:** \n- When two adjacent strips have `Hold` extrapolation, which should evaluate? It seems natural to let only the preceding strip evaluate.\n- When a strip has `Hold_Forwards` extrapolation and the next has `Hold_Backwards`, which should evaluate? Here, I think we should still let only the preceding strip evaluate, for consistency with the previous point. \n\n____\n\n**Implementation/Patches**\n[D9942: NLA: Remove Hold resetting between Hold_Forward Behavior](D9942) \n[D9943: NLA: Strip Evaluate Held Strips Even When Not First Strip](D9943) (depends on previous patch)\n(todo) Patch3: Add `Hold_Backwards` support. Unsure about whether this is actually useful. Maybe we should wait till there is a concrete use-case for it? \n" ]

[ "NLA Visual Bake of Actions (with Rigify character) Gives broken results.\nOperating system: Windows 10 Home 64bit\nGraphics card: GeForce RTX 2080\n\nBroken: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: c77597cd0e15, type: release, build date: 2022-03-09, 00:44:13\nWorked: 3.0 and later - All that can open this file correctly.\n\n**Description**\n(Files provided for testing)\nyou'll find a stack of NLA Action strips resulting in desired animation.\nBaking those actions into a single Action using visual keying results in Broken looking animation (baked action is set to Replace).\nAdditionally even though the resulting strip is set to replace and placed as the top layer. Turning Layers on/off below it affects the resulting pose on the character.\nOne would expect once the top layer is set to Replace, anything happening in the lower layers should have no apparent effect and could safely be removed from the NLA.\n\nAttached Viewport Renders of Pre and Post Bakes for reference.\nAttached Character rig used as a Library override (save and relocate the library override from the outliner in the Animation file)\nAttached The Animation File in which I am attempting to Bake.\n\n[MomoDebug_A_rig.blend](MomoDebug_A_rig.blend)\n\n[BadBakeNLAActions.blend](BadBakeNLAActions.blend)\n\n- Open file BadBakeNLAActions.blend. MomoDebug_A_rig.blend is linked, so may need relocating\n- Delete The top NLA track - it is my failed bake.\n# Turn on all other tracks below\n\n- Run Object > Animation > Bake Action. Use Visual keying option.\n- Turn off all the layers below (EXCEPT for the WORLD PLACER, that one doesn't get baked because it affects the rig Object itself rather than the bones)\n\nResult:\nI couldn't remove the layers below without breaking the animation.\n\n", "NLA bake does not bake shape keys values\nTested on Blender 3.2, 3.3\n\n**Short description**\n\nI have a shape key animation that's driven by some other property (for example, object location). \nIf I try to bake it in NLA (F3 - nla.bake and run bake will options checked) it does bake object location, rotation etc but it ignores shape keys values.\n\nIt is important to be able to bake shape keys values to keyframes too because:\n1) after bake it will be possible to edit shape keys data as curves\n2) sometimes baking is required to be able to export shape keys values in some other software\n\nMy suggestion will be to either to bake shape keys values all the time or to add an option to do so.\nOther thing is there is no option to bake custom properties too.\n\nI've found some people that met this issue before - [here ]] and [[ https:*www.reddit.com/r/blenderhelp/comments/rhgwck/comment/hoqino2/ | there](https:*blenderartists.org/t/bake-action-and-shape-key-action/1310333), usually people add multiple bones to drive shape keys and then work with those bones animation. \nWhich seems redundant if you have really many shape keys (for example in productions for face animation we use around more than 50 of them). \n\n\n**Exact steps to reproduce the error**\nI've attached blend file with example - it's just a cube that has 1 shape key that's attached to cube's X location with driver. [cube_shapekey_bake.blend](cube_shapekey_bake.blend)\nYou can try to bake it with nla.bake and then check in Dope Sheet that no shape keys values keyframes was added.\n\nI've also wrote a script that does exactly that.\nI've attached the script to the blend file - you can go to scripting and run it to get the bake shape keys values for currently selected object. \nIt might be helpful for someone who struggles with that issue until it solved.\n\n```python\nimport bpy\n\ncontext = bpy.context\nscene = context.scene\nobject = context.object\nframe_start = scene.frame_start\nframe_end = scene.frame_end\n\n# bake current shapekeys values to keyframes (no need to actually store them)\nfor frame in range(frame_start, frame_end+1):\n```\n scene.frame_set(frame)\n for sk in object.data.shape_keys.key_blocks:\n if sk.name == 'Basis':\n continue\n sk.keyframe_insert(\"value\", frame=frame)\n```\n\n# remove baked drivers from shapekeys\ndrivers = object.data.shape_keys.animation_data.drivers\ndrivers_to_remove = list()\nfor fcurve in object.data.shape_keys.animation_data.drivers.values():\n```\n data_path = fcurve.data_path\n sk_name = data_path.split('key_blocks[\"')[1].rsplit('\"].value')[0]\n drivers_to_remove.append(fcurve)\n```\n\nfor driver in drivers_to_remove:\n```\n print(f'removing driver {driver}')\n drivers.remove(driver)\n```\n\n```\n\n" ]

[ "Crash after executing the script\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.1 Release Candidate\n\nApplication crashes when clicking on the script run button\n\n1/ launch Blender\n2/ click on \"Scripting\" tab; click \"New\"\n3/ paste the following chatgpt generated script and run it: \n```\nimport bpy\nfrom math import sqrt, sin, cos\n\n# Define the vertices of the tetrahedrons\nvertices1 = [\n (1, 1, 1),\n (-1, -1, 1),\n (-1, 1, -1),\n (1, -1, -1)\n]\n\nvertices2 = [\n (1, -1, -1),\n (-1, 1, -1),\n (-1, -1, 1),\n (1, 1, 1)\n]\n\n# Define the faces of the tetrahedrons\nfaces1 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\nfaces2 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\n# Create new meshes and objects\nmesh1 = bpy.data.meshes.new(\"Tetrahedron1\")\nobj1 = bpy.data.objects.new(\"Tetrahedron1\", mesh1)\n\nmesh2 = bpy.data.meshes.new(\"Tetrahedron2\")\nobj2 = bpy.data.objects.new(\"Tetrahedron2\", mesh2)\n\n# Set the object locations and scene context\nobj1.location = (-2, 0, 0)\nbpy.context.scene.collection.objects.link(obj1)\n\nobj2.location = (2, 0, 0)\nbpy.context.scene.collection.objects.link(obj2)\n\n# Create the vertices and faces of the meshes\nmesh1.from_pydata(vertices1, [], faces1)\nmesh1.update(calc_edges=True)\n\nmesh2.from_pydata(vertices2, [], faces2)\nmesh2.update(calc_edges=True)\n\n# Hinge the tetrahedrons together by one edge\nedge1 = mesh1.edges[0]\nedge2 = mesh2.edges[2]\n\nbpy.ops.object.select_all(action='DESELECT')\nobj1.select_set(True)\nobj2.select_set(True)\n\nbpy.context.view_layer.objects.active = obj2\nbpy.ops.object.mode_set(mode='EDIT')\nbpy.ops.mesh.select_all(action='DESELECT')\nedge2.select = True\nbpy.ops.mesh.edge_face_add()\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Add an armature to the tetrahedrons\nbpy.ops.object.armature_add()\narmature = bpy.context.object\narmature.name = \"HingeArmature\"\narmature.location = (0, 0, 0)\n\n# Add bones to the armature\nbpy.ops.object.mode_set(mode='EDIT')\nbone1 = armature.data.edit_bones.new('Bone1')\nbone1.head = (0, 0, 0)\nbone1.tail = (-2, 0, 0)\nbone1.use_deform = False\n\nbone2 = armature.data.edit_bones.new('Bone2')\nbone2.head = (0, 0, 0)\nbone2.tail = (2, 0, 0)\nbone2.use_deform = False\n\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Parent the tetrahedrons to the armature\nobj1.parent = armature\nobj1.parent_type = 'BONE'\nobj1.parent_bone = 'Bone1'\n\nobj2.parent = armature\nobj2.parent_type = 'BONE'\nobj2.parent_bone = 'Bone2'\n\n# Animate the hinge\nframes = 30\n\nfor frame in range(frames):\n bpy.context.scene.frame_set(frame)\n\n angle = frame / frames * 2 * 3.14159265\n\n bone1.tail = (-2 * cos(angle), 0, -2 * sin(angle))\n bone2.tail = (2 * cos(angle), 0, 2 * sin(angle))\n\n bone1.keyframe_insert(data_path='tail')\n bone2.keyframe_insert(data_path='tail')\n```", "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", "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", "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", "Crash when selecting object on Mac\nOperating system: macOS-12.5.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.3.0\n\nSystem crash trying to open einar_hair.blend file\n\nDownload einar_hair.blend fle from ?asset=6072\nSelect any object.\n\nBlender will crash. Also hair is not visible. It's possible, that OS will crash as well. ", "Running a script that registers an operator from the same operator crashes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIf you execute an `bpy.ops.text.run_script()` through the operator through the panel in a Text editor, then blender crashes.\n\nP.s. maybe it's my fault and I did something wrong, but is blender supposed to crash?\n\nCopy the script or download the file:\n```Py\nimport bpy\n\nclass Op(bpy.types.Operator):\n bl_idname = 'op.op'\n bl_label = \"Op\"\n def modal(self, context, event):\n bpy.ops.text.run_script() # <------- here -------\n return {'FINISHED'}\n def invoke(self, context, event):\n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n self.layout.operator(Op.bl_idname, text='Click me')\n\n\nclasses = (Op, Panel)\n\ndef register():\n for c in classes:\n bpy.utils.register_class(c)\ndef unregister():\n for c in reversed(classes):\n bpy.utils.unregister_class(c)\n\nif __name__==\"__main__\": register()\n```\n\n", "Blender 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", "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", "Crash when run the script code follow\nOperating system: Mac 11.4\nGraphics card: Intel Iris 1536 MB\n\nBroken: 3.0.1(2022-01-26)\n\nBlender crashed when running the script followed in \"Scripting Window\":\n\n```\nimport bpy\n\nfor obj in bpy.data.collections['Bg_objects'].all_objects:\n obj.is_holdout = True\n```\n\nAddressSanitizer error log:\n```lines=20\n==34714==ERROR: AddressSanitizer: heap-use-after-free on address 0x00015d792c38 at pc 0x00010523645c bp 0x00016fdfa1d0 sp 0x00016fdfa1c8\nREAD of size 8 at 0x00015d792c38 thread T0\n - 0 0x105236458 in rna_iterator_listbase_next rna_access.c:4677\n - 1 0x1053cc940 in Collection_all_objects_next rna_collection_gen.c:209\n - 2 0x105234920 in RNA_property_collection_next rna_access.c:3690\n - 3 0x105f6c330 in pyrna_prop_collection_iter_next bpy_rna.c:7107\n - 4 0x11366ad40 in _PyEval_EvalFrameDefault ceval.c:4001\n - 5 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 6 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 7 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 8 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 9 0x10a275444 in text_run_script text_ops.c:773\n - 10 0x10a275284 in text_run_script_exec text_ops.c:812\n - 11 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 12 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 13 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 14 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 15 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 16 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 17 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 18 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 19 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 20 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 21 0x1030043ec in WM_main wm.c:623\n - 22 0x10000ba94 in main creator.c:544\n - 23 0x1454710f0 in start+0x204 (dyld:arm64e+0x50f0)\n\n0x00015d792c38 is located 8 bytes inside of 80-byte region [0x00015d792c30,0x00015d792c80)\nfreed by thread T0 here:\n - 0 0x145a890f0 in wrap_free+0x98 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d0f0)\n - 1 0x1151b28e8 in MEM_lockfree_freeN mallocn_lockfree_impl.c:116\n - 2 0x114b67940 in BLI_freelistN listbase.c:463\n - 3 0x1003acbf8 in collection_object_cache_free collection.c:816\n - 4 0x1003aca74 in BKE_collection_object_cache_free collection.c:826\n - 5 0x100e4b080 in BKE_main_collection_sync_remap layer.c:1366\n - 6 0x1059bcf0c in rna_Object_hide_update rna_object.c:370\n - 7 0x105257fa8 in rna_property_update rna_access.c:2069\n - 8 0x105257bac in RNA_property_update rna_access.c:2138\n - 9 0x105f50268 in pyrna_py_to_prop bpy_rna.c:2083\n - 10 0x105f54308 in pyrna_struct_setattro bpy_rna.c:4453\n - 11 0x1135de558 in PyObject_SetAttr object.c\n - 12 0x113667dd0 in _PyEval_EvalFrameDefault ceval.c:2850\n - 13 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 14 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 15 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 16 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 17 0x10a275444 in text_run_script text_ops.c:773\n - 18 0x10a275284 in text_run_script_exec text_ops.c:812\n - 19 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 20 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 21 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 22 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 23 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 24 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 25 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 26 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 27 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 28 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 29 0x1030043ec in WM_main wm.c:623\n\npreviously allocated by thread T0 here:\n - 0 0x145a89380 in wrap_calloc+0x9c (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d380)\n - 1 0x1151b13b8 in MEM_lockfree_callocN mallocn_lockfree_impl.c:222\n - 2 0x1003b5754 in collection_object_cache_fill collection.c:754\n - 3 0x1003b5d20 in collection_object_cache_fill collection.c:775\n - 4 0x1003b53b0 in BKE_collection_object_cache_get collection.c:786\n - 5 0x1053cc5d8 in rna_Collection_all_objects_begin rna_collection.c:54\n - 6 0x1053cc2d0 in Collection_all_objects_begin rna_collection_gen.c:200\n - 7 0x105233a88 in RNA_property_collection_begin rna_access.c:3674\n - 8 0x105f6c158 in pyrna_prop_collection_iter_CreatePyObject bpy_rna.c:7076\n - 9 0x105f67ef0 in pyrna_prop_collection_iter bpy_rna.c:7083\n - 10 0x11357f400 in PyObject_GetIter abstract.c:2813\n - 11 0x11366ac34 in _PyEval_EvalFrameDefault ceval.c:3958\n - 12 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 13 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 14 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 15 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 16 0x10a275444 in text_run_script text_ops.c:773\n - 17 0x10a275284 in text_run_script_exec text_ops.c:812\n - 18 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 19 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 20 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 21 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 22 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 23 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 24 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 25 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 26 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 27 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 28 0x1030043ec in WM_main wm.c:623\n - 29 0x10000ba94 in main creator.c:544\n```\n\n- Open attached file\n- Go to Scripting workspace\n- Run the above script\n[bug.zip](bug.zip)", "Crash going to material preview or rendered shading mode Blender 2.83.0\nMacBook Pro 15 inch Early 2013\n2.7 GHz Intel Core i&\n16 GB 1600 Mhz DDR3\n|Operating system:|MacOS 10.12.5 - @Tramfabriek\n| -- | -- |\n||Mac OS X 10.12.6 (16G2136) - @johan-eds\n|| macOS 10.12.6 - @UmbertoOldani\n\n|Graphics card:|NVIDIA GeForce GT 650M 1024 MB + Intel HD Graphics 4000 1536 MB - @Tramfabriek\n| -- | -- |\n||NVIDIA GeForce GTX 775M, PCIe, 2048 MB - @johan-eds\n|| NVIDIA GeForce GTX 680MX 2048 MB - @UmbertoOldani\n\nBisected to find the bad commit: 804e90b42d\n\nCrash when clicking on Viewport Shading >Material Preview or >Rendered\nThis did happen already in the 2.83 betas, but none of the 2.82 and earlier version had this problem on this computer running this same OS at least since Blender 2.79.\n\n**System crash report 1** (crash in `UI_draw_roundbox_aa` -> `GPU_batch_draw `. Probably the material render icon):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff909add42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff90a9b457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff909134bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff9091342f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff88cdbfbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff76297390 0x7fff7607a000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff88cdd524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff76385867 0x7fff7607a000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff763554fd 0x7fff7607a000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff76282a2b 0x7fff7607a000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff7626ee9a 0x7fff7607a000 + 2051738\n11 com.apple.GeForceGLDriver \t0x00007fff76289654 0x7fff7607a000 + 2160212\n12 com.apple.GeForceGLDriver \t0x00007fff7626af97 0x7fff7607a000 + 2035607\n13 com.apple.GeForceGLDriver \t0x00007fff763851ad gldUpdateDispatch + 1041\n14 GLEngine \t0x00007fff7ff1d32a gleDoDrawDispatchCoreGL3 + 520\n15 GLEngine \t0x00007fff7fecebd9 gleDrawArraysOrElements_Entries_Body + 128\n16 GLEngine \t0x00007fff7fecaab4 glDrawArraysInstanced_GL3Exec + 220\n17 org.blenderfoundation.blender \t0x0000000109614f2c GPU_batch_draw_advanced + 428\n18 org.blenderfoundation.blender \t0x0000000109614d6c GPU_batch_draw + 124\n19 org.blenderfoundation.blender \t0x0000000105218c51 UI_draw_roundbox_aa + 353\n20 org.blenderfoundation.blender \t0x0000000104f3d96c ED_region_do_draw + 1372\n21 org.blenderfoundation.blender \t0x0000000104b6d49c wm_draw_update + 2092\n22 org.blenderfoundation.blender \t0x0000000104b6b010 WM_main + 48\n23 org.blenderfoundation.blender \t0x0000000104827762 main + 962\n24 libdyld.dylib \t0x00007fff9087f235 start + 1\n\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5b521f78 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff5b521fa0 rsp: 0x00007fff5b521f78\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x000000011ab85cf8 r13: 0x0000000000000000 r14: 0x00007fff998033c0 r15: 0x000000011ab85000\n rip: 0x00007fff909add42 rfl: 0x0000000000000206 cr2: 0x00007fff960d0b58\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n\n**System crash report 2** (crash in `blf_batch_draw ` -> `GPU_batch_draw `):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff8b1dfd42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2cd457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff8b1454bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff8b14542f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff83587fbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff71040390 0x7fff70e23000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff83589524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff7112e867 0x7fff70e23000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff710fe4fd 0x7fff70e23000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff7102ba2b 0x7fff70e23000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff71017f8e 0x7fff70e23000 + 2051982\n11 com.apple.GeForceGLDriver \t0x00007fff7100b6bc 0x7fff70e23000 + 2000572\n12 com.apple.GeForceGLDriver \t0x00007fff7100bec2 0x7fff70e23000 + 2002626\n13 com.apple.GeForceGLDriver \t0x00007fff7101113f 0x7fff70e23000 + 2023743\n14 com.apple.GeForceGLDriver \t0x00007fff7143f25e 0x7fff70e23000 + 6406750\n15 com.apple.GeForceGLDriver \t0x00007fff7143f4e6 0x7fff70e23000 + 6407398\n16 com.apple.GeForceGLDriver \t0x00007fff7143f5d7 0x7fff70e23000 + 6407639\n17 com.apple.GeForceGLDriver \t0x00007fff71013d3d 0x7fff70e23000 + 2035005\n18 com.apple.GeForceGLDriver \t0x00007fff7112e1ad gldUpdateDispatch + 1041\n19 GLEngine \t0x000000011925232a gleDoDrawDispatchCoreGL3 + 520\n20 GLEngine \t0x0000000119203bd9 gleDrawArraysOrElements_Entries_Body + 128\n21 GLEngine \t0x00000001191ffab4 glDrawArraysInstanced_GL3Exec + 220\n22 org.blenderfoundation.blender \t0x000000010b288f2c GPU_batch_draw_advanced + 428\n23 org.blenderfoundation.blender \t0x000000010b288d6c GPU_batch_draw + 124\n24 org.blenderfoundation.blender \t0x000000010b283d82 blf_batch_draw + 418\n25 org.blenderfoundation.blender \t0x000000010b282359 BLF_batch_draw_end + 9\n26 org.blenderfoundation.blender \t0x0000000106fc2163 view3d_draw_region_info + 8515\n27 org.blenderfoundation.blender \t0x0000000106936dbd DRW_draw_callbacks_post_scene + 445\n28 org.blenderfoundation.blender \t0x00000001069376cd DRW_draw_render_loop_ex + 1757\n29 org.blenderfoundation.blender \t0x0000000106fc2668 view3d_main_region_draw + 136\n30 org.blenderfoundation.blender \t0x0000000106bb157e ED_region_do_draw + 366\n31 org.blenderfoundation.blender \t0x00000001067e149c wm_draw_update + 2092\n32 org.blenderfoundation.blender \t0x00000001067df010 WM_main + 48\n33 org.blenderfoundation.blender \t0x000000010649b762 main + 962\n34 libdyld.dylib \t0x00007fff8b0b1235 start + 1\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff598ab4b8 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff598ab4e0 rsp: 0x00007fff598ab4b8\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x0000000120bebcf8 r13: 0x0000000000000000 r14: 0x00007fff93fe13c0 r15: 0x0000000120beb000\n rip: 0x00007fff8b1dfd42 rfl: 0x0000000000000206 cr2: 0x00007fff8b1c727d\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n1. Open Blender\n2. Click to remove start up information panel\n3. Click on Viewport Shading >Material Preview or >Rendered\n\nResult:\nCrash", "LineArt; Crash after press play in a scene with LineArt modifier\nOperating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\nNo idea what crashes blender. Just press play and wait some seconds.\n\nI would love to help solving this issue, so when someone could remind me where the crashreport usually lands in Linux, i could share that as well.\n[Narrator.blend](Narrator.blend)\n\n", "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", "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", "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", "Blender crashes when click on shading tab \nOperating system: Windows 10, 64-bit\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 4.5.0 NVIDIA 445.87\n\nBroken: \n - version: 2.81 (sub 16), branch: v2.81_octane2019 (modified), commit date: 2020-02-11 11:57, hash: 81ff79b8cdb7, type: build date: 2020-02-11, 12:22:28\n - version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503, type: Release\n\nBlender crashes when clicking on the shading tab. It closes and goes back to the desktop.\n\nSee short description.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)" ]

[ "Crash When Trying to UV Unwrap\nOperating system: Windows 10\nGraphics card: Intel(R) HD Graphics 5500\n\nBroken: newest version\nWorked: newest version\n\nWhen attempting to UV unwrap my object, blender just quits. The object is multiple parts joined together with a mirror modifier and only about 1k tris.\n\nEdit mode then select all faces, U and smart UV project (setting dont affect it crashing) and then Blender quits without any information. This has also happened to me with another project and I ended up having to export multiple pieces and texture them separately. [RatHead.blend](RatHead.blend)" ]

[ "Support for binding additional keys\nThere are keys which aren't included in Blender's keymap.\n\nHowever it doesn't make sense for us to include all possible keys, as there are many which don't make sense (system-wake, calculator, eject, brightness-up, ... [see a full list ](keycodes)).\n\nRecently we have added some keys which can be useful.\n\n- Application key (used for context menu)\n- F20-24 (for users to have keyboards with additional F-Keys).\n\nThis task is to keep track of other possible additions to the keymap.\n\nOpen Topics:\n\n- How to handle non US keymaps?\n - We could support binding raw keycodes *(so we don't need to expand our fixed table of keys to include keys from all keyboard layouts).*\n - We could support keyboard layouts, which all include the US keymap, extending on it for keys it doesn't include. This could be selected as a preference.", "Blend file thumbnail shows the file browser\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nWhen using the full screen file browser preference and saving a blend file, the thumbnail shows the file browser\n\n\n\nSet file browser to Maximized Area\n\nSave a file\nCheck the thumbnail\n\n", "Disappearing buttons in pie menu, depending on button text length and use of align=True\nOperating system: Linux-4.15.0-144-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\nWorked: - \n\nI have a pie menu, with a section like this:\n\n\n```\n box = pie.split()\n column = box.column(align=False)\n \n row = column.row(align=True)\n row.operator(\"transform.translate\", text=\"(B) Get Backup\")\n row.operator(\"transform.translate\", text=\"(V) Match\")\n\n row = column.row(align=True)\n row.operator(\"transform.translate\", text=\"(D) Project\")\n row.operator(\"transform.translate\", text=\"Unwrap\")\n```\n\nChanging the column's align argument to True, leads to the Unwrap button disappearing.\nIt can be brought back by changing the text length of any of the buttons. For instance, you can shorten or lengthen the Unwrap button's text. Same for the other buttons, changing the text length will usually bring the Unwrap button back. \n\nSee [video demo ](watch?v=v3VkH44p7xk): \n\n[disappearing_button.blend](disappearing_button.blend).\n\nI've checked back until 2.77 and it's present in all versions since, likely before that too.\n\n* open the blend, run the script in the text editor\n* the pie pops up and all 4 buttons are present\n* set the column's align arg to True\n* the Unwrap button disappears\n* change the text length of any of the 4 buttons to make the button re-appear\n\n", "Creating new folder in File View disables \"select all\"\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 5)\n\nThis seem to happen only when 'Select All Toggles' is enabled.\n\n - Enable **Select All Toggles** in **Preferences** > **Keymap**\n - Open **File View** (can be open or save menu)\n - Pressing \"**a**\" should toggle selection of all elements (you need some files in the folder for that).\n - Create new folder.\n - Type in a name\n - Now pressing \"**a**\" does nothing. Using box select should fix it.\n[file_view_select_all_bug.blend](file_view_select_all_bug.blend)", "The X or Delete button does not work in the outliner (Blender File)\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.6\n\n[The X or Delete button does not work in the outliner (Blender File)]\n\n- Open default startup file\n- {nav Outliner >Display Mode > Blender File}\n- In outliner {nav Brush > RMB > Delete > RMB > Assign Shortcut > X}\n- Attempt to delete any brush with hotkey (will not delete brush)\n- Change hotkey (eg {key Shift X}) and now attempt to delete brush with hotkey\n\nwhen you press X items in:\n| Broken | Brushes, Cameras, Images, Lights, Line Styles, Materials, Meshes, Palettes, Workspaces, Worlds |\n| -- | -- |\n| worked | Collections, Objects, Scenes |\n\n\n\n\n[Delete _X_ Button.blend.py](Delete__X__Button.blend.py)\n\n{[F12271213](Delete__X__Button.blend)}]\n\n", "Mirror UI in does not update immediately when a shortcut is assigning \nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.2.0\nWorked: for sculpt mode it used to work in blender 2.80-2.92, broke in blender 2.93 and up. \n\nAssigning a shortcut to the mirror widget in any mode does not immediately trigger a ui update when pressed.\n\n- Enter sculpt or any other mode\n- Assign shortcut to the mirror x widget, v for example since its unassigned by default \nUI does not update immediately when pressing the shortcut, mouse cursor need to hover over the ui to trigger the update, this used to work in 2.80-2.92, but since 2.93 and up the ui does not refresh after pressing the shortcut. \nVideo of the issue:\n[Blender 2022-07-02 14_30_21_Trim_Trim.mp4](Blender_2022-07-02_14_30_21_Trim_Trim.mp4)", "--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", "Not recognizing numpad page up /down keys .\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nBlender is failing to recognize the numpad keys !!!\n\nTrying to use the change workspace shortcut ctrl+PageUp /down and blender is not recognizing the keys in numpad and keep assuming the key 9 and 3 . Other software is fine and i can use Page up and Down, and the home end keys. \n\n", "Pose Library: Collection pop-up when creating new poses in Action Editor\nWhen creating poses from the Action Editor it should be explicit to which catalog the new asset should be added.\n\nBy default the Unassigned option should be highlighted, so users can post-pone this decision for later, similar to when marking data-blocks as assets.\n\nThis is part of #103265.\n\n---\n\nSome initial code snippets for anyone interested on tackling this: [P3408](P3408.txt)", "Particles animation dont show\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nemitter particles animation don't show movement when i press G shortcut to move the model that contain the particles but they don't show any movement, so i can't do an autokeying animation whit the desire movement of the mouse.\n\nadd a cube, put particle emitter, press space bar and G key to move, the particles don't show movement only flickering.\n", "Add Image/Sequence to video editing Squencer: number of images are truncated\nOperating system: Win10\nGraphics card: GeForce GTX 1050Ti\n\n**Blender Version** \nbroken: 2.8 RC3\nworked: 2.8 build from ca 1 month ago\n\nWhen you add images by drag 'n drop in de video sequencer, the number of images in the resulting strip is truncated aaround 27. \n\n(1) Open Blender\n(2) from the splash-screen choose: video editing\n(3) Open a windows explorer and select ca 100 jpg files;\n(4) use drag n drop to drop the files in the sequencer;\n\nYou then have a strip of just 27 frames where the selected number of files is expected. This used to work in the beta's", "Inset operator modal handling misses option to toggle \"Offset Even\" via shortcut\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nNoticed problems when using Inset Faces tool in Edit Mode. If I'm using the select tool and I press **I** to activate the tool Inset Faces tool its menu doesn't display anywhere so I can't choose Even for example. If I click on the tool icon then it works, even if I then use **I** to activate the tool. This makes it so I can't use shortcut keys anymore. I suspect this is happening with other tools as well. Another thing worth noting is that the status bar says the Call Menu is triggered by the right mouse button but it actually just closes the tool.\n\n\n\n\n\n\nGo into edit mode with the default cube. Select a face. Hit I to activate the inset faces tool. Notice that the options for the tool aren't available.\n\n", "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", "2D transform operations show options and use a modal keymap intended for 3D transform\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.92.0 Alpha\n\ntransform.seq_slide and transform.transform are linked to the transform keymap of the 3D transform. This results in the wrong shortcuts hints #83307 in the status bar and also wrong options in the Edit Last Operation: \n{[F9508650](transform_last_operation.gif),size=full} \n\n- Use `Move/Extend from Current Frame` to move the handle.\n- Check the `Edit Last Operation` options\n\n", "Bug with autosave in edit mode\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.3.0\n\nBlender creates autosave when in edit mode but doesn't save the file as in edit mode\n\n- Set `Auto save` timer to 1 minute\n- Open attached file\n- Switch to edit mode\n- Make changes until auto-save file will generate\n- Open another blender instance and open auto-saved file (you'll find default cube in there)\n[try-auto-save.blend](try-auto-save.blend)" ]

[ "Shift +F1 append not working\ni9 14 core\nNVidea Titan Pascal\n\ndd3f5186260e\n\nThe short cut shift+F1 for append only allows you to get to the top of the .blend file stack. You can not get below that to find the particular article/object etc that you are looking for.\n\nFile append works as normal.\n\nChecked and reported by 4 people of same facebook group.\n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Width text without \" . . . \" each text.\nOperating system: macOS-12.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.2.0\n\nWidth (unknow what is call name)\n\nPlease fix width everything I told them before. I was send them long time ago, They never did.\n\n\n\n", "Brushes Assets Viewport User Interface\n{[F13331829](image.png), size=full}\n\nAdditional Notes:\n\n{[F13331831](image.png), size=full}", "Keymap: use number keys for mode switching (2nd Iteration)\n## Motivation\n\n* Improve ease of mode switching with direct shortcuts (`Tab` and `Ctrl+Tab` functionality remains the same)\n* Consistent accross all object types.\n* Allows the use of pie menus for quickly going into sub-modes (and later adding more options like Island Select mode for meshes)\n* Having the `~` key (or equivalent left to 1) be the Switch Object (`Transfer Mode`) fits better with mode switching than D.\n* The current functionality of toggling Collections visibility often leads to confusion for new users:\n * Objects seemingly disappear\n * Risk of losing visibility settings or undo steps.\n\n## Proposed Solution\nThis task is to evaluate the possibility of using number keys for mode switching, in addition to the already existing `Tab` and `Ctrl+Tab` shortcuts to toggle Edit, Pose, and modes pie menu.\n\nThe current proposal:\n{[F10130043](image.png), size=full}\n\n\n* The numbers row will get a dedicated option in the Keymap Preferences:\n * Collection Visibility (default at least during the trial phase)\n * Mode Switching\n * Potentially `Emulate Numpad` could be part of this option as well.\n\n* Behavior for **Tab** and **Ctrl-Tab** for mode edit-mode switching will be kept as this is convenient and used in many other areas where numbers make less sense (graph-editor, NLA, sequencer... etc, where using numbers doesn't make so much sense).\n\n## Details\n\n- Modes would be mapped to a key consistently between object types, so the pose-mode number-key would do nothing for a curve (for example).\n- Equivalent modes would share a key between object types (grease-pencil Draw to use the same key as mesh Texture Paint, the same goes for Grease Pencil Sculpt, Vertex Paint... etc).\n- Modes to switch include (8): `OBJECT` `EDIT`, `SCULPT`, `TEXTURE_PAINT`, `VERTEX_PAINT`, `WEIGHT_PAINT`, `PARTICLE_EDIT`, `POSE`.\n\n\n## Open Topics\n\n**Should sub-modes have direct access?**\nWith the introduction of pie menus by default in 2.80, users are now used to these and pie menus could be used to access sub-modes. \n\nIt has been proposed in #84380 that vertex/edge/face be expanded into the number buttons too. This only works well for mesh and grease pencil edit-mode, however it has some down-sides.\n\n- We would be using all number keys by default, any additional modes or sub-modes wont fit.\n- Some sub-modes wont fit:\n - Particle edit (currently uses keys 1-3 to switch sub-modes).\n - Weight paint.\n - Texture/Vertex paint.\n\nThe ideal solution in this case isn't clear, either we accept loosing shortcuts for switching sub-modes or accept some inconsistency (having to add a different shortcut for sub-mode switching for modes besides edit-mode).\n\nThere are plans to merge painting modes into a single attribute painting mode, even if this is done, it might make sense to expose weight/texture/sculpt as sub-modes... either way, I don't think we should rely on this change unless it's committed to master before the keymap changes. The same applies to the future of Particle Edit once the new Hair object type is implemented.\n\n**What to do when pressing a modes key a second time?**\n\nCurrently nothing is planned. Options are to toggle the mode or cycle through sub-modes. Both have their pro's and con's so there are no plans to use second-time presses.\n\n**Is overwriting edit-mesh modes acceptable?**\n\nBy switching directly into vert/face/edge modes, this will overwrite the mixed modes which the user will need to manually set every time they enter edit-mode. Holding Shift while changing selection modes will extend the selection as it does currently.\nEven though this isn't such a common functionality, it would be good to avoid breaking peoples workflows.\n\n----\n\n*Updated by @pablovazquez based on notes from the UI meeting on 20 May.*", "Multiply and divide in item location only calculates second part of separate units.\nOperating system:any \nGraphics card:any\n\n3.4+\n\n\nWhen separate units (imperial) is enabled, the math (multiply/divide) in the item location field is broken.\n\n\nIn a new blender file, set the scene units to imperial.\nCheck the 'Separate Units' checkbox.\n\nIn the 3d viewport, select the default cube and press G X 6.5 to move the default cube 6'6\" in the X axis.\nNow in the Item Tab, Transform, Item Properties, enter the X location field and add /2 or *0.5 to the end of the line.\n\nThe expected behaviour is to halve the value in the field which would result in 3'3\". What happens though, is it only calculates for the inches portion of the location, resulting in a location value of 6'3\".\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", "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", "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", "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", "`action.frame_range` span always >=1 when there's only 1 key frame in it.\nOperating system: Mint\nGraphics card: Nvidia\n\nBroken: 3.5 & main branch\n\n\nframe_range wrong value when only 1 keyframe\n\n- with default cube, go to frame 6\n- Insert a keyframe (for example, on location)\n- bpy.context.object.animation_data.action.frame_range returns (6.0, 7.0)\n\nMy expectation was it returns (6.0, 6.0)\n\nIf you then insert a keyframe at frame 7, it still returns (6.0, 7.0)\n\n", "Angle input fields fail to accept units when scene rotation units are set to radians\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nAngle input fields usually accept rotation units as 'd' for degrees and 'r' for radians after the entered number, however when scene rotation units are changed to radians in the scene properties, this functionality stops working. Blender reports an error when units are entered: \n\n\n> Error evaluating number, see Info editor for details: File \"<string>\", line 1\n> 2d\n> ^\n> SyntaxError: unexpected EOF while parsing\n> \n\n\n\n\n\n\n1. Open new scene and change rotation units to radians in the Properties Editor, Scene tab, Units section. \n2. Type some number followed by 'd' for degrees in any rotation input filed.\n\n\n", "Double click list renaming not working on heavy scenes\nVista64, 2.7a, gtx470\nWhen the scene is heavy, so that interface becomes slightly laggy, double click list rename stops working, especially for fast clicking.\n\n - Add subdivision modifiers to any mesh until interface becomes laggy.\n - Add a vertex group or UV map.\n - Double click to rename - renaming is not activated.\n", "Affect origins indicator gizmo is not affected by unit scale\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.2\nWorked: never\n\nThe gizmo used to indicate affect origin feature of transform tool is enabled does not change with different unit scale. This makes the gizmo invisibly tiny when using unit scale of 0.01, which is mandatory for Unreal Engine export capability, as described here: scene_scale.mp4\n\n1. In a new .blend file, set unit scale to 0.01\n2. Create a new cube. Newly created cube should be sized appropriately for new unit scale.\n3. Select new cube, Activate move tool, and activate \"Origins\" Affect Only option.\nResult: The gizmo to indicate Affect Only Origins feature is enabled is invisibly tiny and requires extreme zoom in:\n\nExpected: The Affect Only Origins indicator gizmo scale changes appropriately with different unit scales.\n", "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", "Remove 'Use Nodes'\nWhen using Cycles and editing materials, the user is presented with a button called Use Nodes. This is confusing and adds an extra step before being able to set up materials.\n\nIt might be nicer to simply have the material use nodes always. Materials without nodes doesn't even really make sense when using Cycles as they are central to material editing and creation.\n\n", "Set parent (keep transform without inverse) has no effect on scale\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.0 Alpha\n\n\nSet parent (keep transform without inverse) has no effect on scale. End result is different if use Set parent (without inverse)\n\n[parent_scale.mp4](parent_scale.mp4)\n" ]

[ "Walk Teleport and other movements do not take into account the unit scale of the Scene\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\n\n\n\nIf you set Unit scale (scene) 0.1, Walk teleport (Space button in walk mode) jumps to empty nowhere\n[2019-07-11_18-22-54.mp4](2019-07-11_18-22-54.mp4)\n\n[walk to void.blend](walk_to_void.blend)\n\n" ]

[ "GizmoGroup with setup_keymap() doesn't work if addon is enabled by default\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: all versions so far\nWorked: never\n\nIf an addon is enabled by default, any of its GizmoGroup with setup_keymap() classmethod won't react to user input (if they are registered in the register() function). However, if they are registered during the normal operation (i.e. after Blender initializes and draws the first frame), the problem does not appear.\n\n1. Install the attached addon.\n2. Enable the addon (it's called \"!Gizmo test!\").\n3. Save Blender preferences.\n4. Close Blender.\n5. Open Blender.\n6. Select a camera and try dragging the circular gizmo. The gizmo won't react to the input.\n7. Disable the addon, then enable it again.\n8. Select a camera and try dragging the circular gizmo. Now it will rotate the camera.\n[gizmo_test.py](gizmo_test.py)", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "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", "Eyedropper for props does not work in dialog boxes\nBlender 2.81, 71f2229b0d82\nfor example, in Texture Paint Context Menu\nI wanted to implement something using Operator and context.window_manager.invoke_props_dialog()\nThis is not a bug, but why not do it at the dialog level.\n", "\"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.", "Holdout doesn't work with Mix Shader correctly in Eevee\nOperating system: Darwin-20.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.13\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.91.0\n- 2.90.1\nWorked: 2.83.x\n\nHoldout doesn't work with Mix Shader correctly in Eevee. \n\nWhat I expect when mixing with 100% Holdout:\n\n\n\nWhat I get instead:\n\n\n\n\n\n - Open the simple blend below\n - Move the timeline from 0-100, which moves the Mix Shader Fac from 0-1.\n - When at frame 1, it should be a 100% Holdout, but notice that this isn't the case\n - Switch to Cycles and verify that it indeed handles this case correctly\n\n[holdout_eevee_bug.blend](holdout_eevee_bug.blend)\n\n", "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.", " 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)", "Omitting a leading zero on transform commands complains on the terminal\nOperating system: Kubuntu 20.10\n\nBroken: 2.83 - master\n\nTyping transform commands with a number lacking a leading zero complains on the terminal but works otherwise. For example, when inserting commands like scale 90% as `s.9` there is output on the terminal saying:\n\n```\n File \"<string>\", line 1\n .\n ^\n SyntaxError: unexpected EOF while parsing\n```\n\nThat is a bit worrisome because I thought there was something wrong with the blend file I'm working on.\n\n1. blender --factory-startup\n2. select the default cube\n3. insert `s.9`\n", "temp_override working differently with passing as argument versus using override\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 1650\n\nBlender Version\nBroken: 3.4.0\nWorked: Not sure\n\nShort description of error\ntemp_override working differently with passing as argument versus using override\n\n1. Start Blender with --factory-startup\n2. Go to scripting tab and open a new text\n3. Paste the below and run\n\n```\nimport bpy\n\nws=bpy.data.workspaces['Animation']\n\nwith bpy.context.temp_override(workspace=ws):\n print('workspace', bpy.context.workspace, flush=True)\n\noverride=bpy.context.copy()\noverride['workspace']=ws\nwith bpy.context.temp_override(**override):\n print('workspace', bpy.context.workspace, flush=True)\n\n```\n\n4. Expected output\n\n```\nworkspace <bpy_struct, WorkSpace(\"Animation\") at 0x000001152A34CB88>\nworkspace <bpy_struct, WorkSpace(\"Animation\") at 0x000001152A34C408>\n\n```\n5. Obtained output\n\n```\nworkspace <bpy_struct, WorkSpace(\"Animation\") at 0x000001152A34CB88>\nworkspace <bpy_struct, WorkSpace(\"Scripting\") at 0x000001152A34C408>\n```\n", "Hotkeys malfunction after leaving text field with no input using IME(Chinese/Japanese/Korean)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.0.0 Release Candidate\nWorked: Unknow\n\n---\n\n\nUsing IME(Input method editor) like Chinese/Japanese/Korean IME, activate a text field then go back to 3D viewport while inputing nothing will make some hotkeys malfunction.\n\n\n - Default scene with any IME listed in the following image.\n - Click the default cube's name text field to activate the text field.\n - No input, go back to 3D viewport by clicking the 3D viewport area or right-clicking to cancel the operation.\n - Test {key A-Z}, for example press {key G} to transform the cube, the keys shouldn't be functioning.\n\n**Notes:**\n\n - After pressing {key A-Z}, similar IME-poping-ups might be shown as in these images: {[F12405595](图片.png)} The inputs are handled by IME but not being properly functioning like {key G} would not move the selected object.\n - Some other keys like {key 1-9}, {key Shift}, {key Ctrl}, {key CapsLock} and {key Space} are still functioning.\n - After the bug is reproduced, it is able to press {key Shift} to switch the mode of IME to fix the malfunction. And if right after canceling the text field input operation, press {key Ctrl RightMouseBottom} to finish a lasso select can also walk around the bug (but if there are already some inputs after the operation is canceled, doing {key Ctrl RightMouseBottom} won't fix the bug).\n - I found at the time been, Blender will automatically switch the IME modes (sorry I am not sure about which patch brought this feature), that means if in 3D viewport, the IME is automatically set to \"English\" mode and all inputs will not be handled by IME (this is the proper function); while in text field the IME mode is automatically switched to for example \"Chinese mode\" in Chinese IME. This \"auto-switching\" behavior is lost if the said work around is used to fix the bug, and in my case only after restarting Blender will bring back this feature.\n - I have tested a 3rd party Chinese IME \"搜狗输入法\" and in my opinion it has the similar bug as \"Microsoft Pinyin\": ", "Emulate 3 Button Mouse conflicting with Add Primitive tool\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.91.0 Alpha\n\nAs the title suggests, emulate 3 button mouse which works with Alt key conflicts with the alt key of the Add primitive tool where you get to extrude on both sides. I can't commit the extrude while holding alt.\n\n[2020-08-30 21-56-30.mp4](2020-08-30_21-56-30.mp4)\n1. Turn on Emulate 3 button mouse\n2. Select Add Primitive tool, drag out a shape.\n3. Hold Alt to turn on double side extrude and try to click to commit and it won't.\n\n", "Using a File Picker element in a popup window causes the popup to go away\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 2.93.4\nWorked: Not sure if it has, at least not for a while.\n\nIf I put a string property with a subtype of \"DIR_PATH\" or \"FILE_PATH\" to have the folder/file picker show up for a user to easily select a folder/file in an operator's props and then call it with a window manager invoke_props_dialog (or any of the other popup panel ops), after the user has selected a folder/file the file window goes away but so does the panel without executing the operator.\n\n1. Open included blend file\n2. Run 'Popup File Picker Test' script in text editor\n3. In the Object section of the Properties area, under \"Popup File Picker Test Panel\" click 'Test Popup'\n4. In the popup window use the folder picker button to select a folder and hit \"Accept\"\n5. If it worked, the popup should still be there for you to continue to change other props. If it ran execute instead there should be a statement in the info area and in the console window saying \"Ran execute\". Otherwise it most likely made the popup to disappear without running the operator\n\n[popup_file_pick_test.blend](popup_file_pick_test.blend)\n\n", "Preferences: no default key map export name and file type\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nPreferences: no default key map export name and file type\n\nWhen I wanted to export the default map keys ther was no default file name and file type.\nSo I tried to guess it was .txt and then exported. The exported file was \".py\", only the\nfile type whithout a file name. It would be nice to have someting like when saving a\nblend file aka \"untitled.blend\" -> \"untilted-key-map.py\", or something like that.\n\n- Open Blender (factory settings)\n- Go to Preferences > Keymap\n- Export \n- In the field where the file name needs to be specified there is no default name, that indicates the file type (and name)\n\n\n\n", "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" ]

[ "Default button in File Browser does not always listen to the Return / Enter key (regression)\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel HD Graphics 4000 OpenGL Engine Intel Inc. 4.1 INTEL-14.7.8\n\nBroken: version: 2.91.0 Beta\nWorked: 2.90\n\nDefault button in File Browser does not always listen to the Return / Enter key\n\nI have demonstrated this bug / problem to @JulianEisel in person, so he already knows about this bug, he just wanted me to write a few lines into the bug reporting system as a reminder. \n\nThere is no fixed case as to when this happens exactly, but about 50 percent of the time when a File Browser is there for opening / saving files and a filename is entered into the appropriate field, Blender will not listen to the Return / Enter key to continue and do what you had in mind.\n\nOnly when one clicks on the default button itself, will Blender carry out the request to \"Save\" / \"Open\" or similar command needed at that moment.\n\nThe problem occurs both on macOS 10.15.6 as well as Fedora 32 Linux distro.\n\n- Open Blender\n- On splash screen click on Open...\n- Enter filename, don't confirm\n- Move mouse into field with path\n- Press Enter to confirm filename input\n- Press Enter to load file\nNothing happens. If you keep pressing enter though, sometimes it eventually load the file.\nSometimes this happens when you press Ctrl+O, sometimes not.\n\nThis is also true for saving (where this is even more disturbing)\nfrom #88041 (ENTER does not Save file when mouse cursor is over Save dialog text field (regression)):\nWhen you type a new filename into the SAVE FILE dialog and the mouse cursor is still where you just placed it, i.e. IN the text field, hitting ENTER does not Save and dismiss the dialog. The user is pointlessly required to move their cursor into the file list.", "Save As doesn't work with keyboard confirmation\nOperating system: Darwin-20.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.13\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.91.0 \nWorked: 2.83, 2.90.1\n\nThe file browser's *Save As* dialog doesn't save the file when pressing {key enter} after editing the filename. \n\n- Save the file initially either through *File > Save* or {key Ctrl S}. Pressing {key enter} to confirm should work\n- Use *File > Save As* or {key Ctrl Shift S} and modify the name. Pressing {key enter} doesn't work unless you place the mouse cursor outside of the filename field.\n\n", "ENTER does not Save file when mouse cursor is over Save dialog text field (regression)\nOperating system: W10\nGraphics card: GeForce RTX 2060\n\nBroken: 2.92.0\nWorked: 2.83\n\nWhen you type a new filename into the SAVE FILE dialog and the mouse cursor is still where you just placed it, i.e. IN the text field, hitting ENTER does not Save and dismiss the dialog. The user is pointlessly required to move their cursor into the file list.\n\nThis is especially pernicious because it's pointless: the user **just** put the cursor there. It's **inside**the dialog! WTH?\n\n", "Save As dialog does not complete with Enter button\nBroken: 2.93.3, branch: master, commit date: 2021-08-17 18:30, hash: 8b80d19f3641, type: release\nWorked: n/a\n\nWhen doing \"Save As\" and type the name, pressing [Enter] gives no results. So I'm forced to take mouse, move it and click [Save As] by mouse.\n\nExpected behavior should be saving operation. E.g. when pressing [Esc] on the same dialog, that closes the dialog.\n\n- Open Blender\n- From menu select: File \\ Save As\n- By mouse activate the file name part (why I have to use mouse for that?)\n- Type some file name\n- Press [Enter] to save the file (not working)\n- Done\n\n\nbest regards\nPetri" ]

[ "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)", "Copy/Paste Behavior in Viewport\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M390 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15\n\nBroken: version: 2.91.0 Alpha\nWorked: Never worked in 2.8+\n\nWhen pasting an object, the gizmo is not positioned at the newly created object, where you would expect it to be. Instead, there are two cases - both seem to be not intended.\nThe pasted object also is not active for direct manipulation despite the visual indication with the gizmo.\n\nIf there is a selection somewhere else before pasting, the gizmo ends up in the wrong position. Example:\n\n\nIf there is no selection before pasting, there is no gizmo appearing at all. Example:\n\n\nA directly interconnected problem is that pasted objects are not made active despite having an attached Gizmo. Example:\n\n\n**Potential fix**\n1. The gizmo could always appear and show where the object is pasted (belonging to the new object).\n2. The pasted object could become active. When multiple objects are pasted, the selection and active states of the copied objects could be transferred to the newly pasted ones. Also, all previous selections could be deselected after pasting.\n\nThank you :)\n", "MacOS crash when opening a second rendered 3dview window --MacOS 13.0.1--\nOperating system: macOS-13.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.48\n\nBroken: version: 3.5.0 Alpha\n\n\nWhen in rendered 3dview and open a second window also in rendered 3d view, blender hangs for 20 sec. and then MacOS becomes unresponsive and finally crashes.\nNo way to 'force quit' or any other trick to stop blender. or the MacOS crash.\nThis happened now 5 times in a row, always when opening a second new window also in rendered 3dview.\n\nOpen blender 3.4 /3.5 in MacOS 13.01 & switch to rendered 3dview. Then after a minute open another rendered 3dview window.\n\n", "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!", "\"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", "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", "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", "Pin Scene to Workspace doesn't work (when multiple blender windows are open)\nOperating system: Linux-5.15.0-53-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.4.0 Alpha\nBroken: version: 3.3.0\n\n\nPin Scene to Workspace doesn't work\n\nOpen file, observe that scene.002 is active and pined.\n\n[switch scenes.blend](switch_scenes.blend)\n\nSwitch to Modeling tab then back to Layout.\n\nObserve that instead of scene.002, scene.001 is active. \n\nNOTE: this is only failing with multiple blender windows open (if the second window is closed, it works as expected)", "Greasepencil z fighting alpha issue\nHi,\nnot too sure if this is known issue or any fix but I am getting this alpha issue from certain angle when I have 2 different grease object. \n\n", "Fake Dependency Cycle: 'Disable in Viewport' depends on 'Disable in Renders'\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.2.2\n\nDriving hide_render from hide_viewport causes a dependency cycle\nwhile the error occurs on all objects, the driver does seem to work on some objects, but not others. In the default scene for example, the driver works with the camera, but not the cube or the light\n\n- in the outliner, edit the filter to display the `Disable in Viewport` option.\n- Right click the `Disable in Viewports` icon on any given object\n- Copy as New Driver\n- Right click the `Disable in Render` icon of the same object\n- Paste Driver\n[render visibility driver issue.blend](render_visibility_driver_issue.blend)\n\n", "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", "Double click is recognized even when the first click is consumed to close a menu\nOperating system: Windows 10\n\nBroken: 2.80 release, 2.81 5e5cf9ea9f7\nWorked: (optional)\n\nWhen clicking on a workspace name to close the splash screen, the second click gets treated as double click if it occurs fast enough. As a result instead of switching to the workspace, the workspace name switches into text edit mode.\n\nIt happens with other menus too, with wheel menus even when the first click is selecting an option at same time.\n\nObject names in the outliner do switch into text edit mode too.\n\n - Open Blender or make splash screen visible.\n - Double click on the name of a worskpace or object\n\nResult: Workspace (or object) name is in edit mode.\n\n**Or**\n\n - Move the default cube away from the 3D cursor\n - Shift + S to open Snap menu (wheel)\n # Double click on a workspace name while \"Selection to Cursor\" is highlighted\n\nResult: Selection moved to cursor and workspace name is in edit mode.", "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).", "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", "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" ]

[ "Isolate selection works randomly\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon (TM) Pro WX 7100 Graphics ATI Technologies Inc. 4.5.13559 Core Profile Context FireGL 26.20.11018.6\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nWhen trying to isolate selection in edit mode with one object selected - the first time i try to isolate selection, the view resets to frame selected, but the object is not isolated. When I exist isolate selection and try it a second time, then it properly isolated the elements.\n\n- Create a new file and add some geometry\n- select a single object and toggle isolate selection\n- the view should now be centered around the object yet it isn;t isolated\n- toggle isolate selection to exit out of local mode, and then toggle it again. Now the object should be properly isolated.\n" ]

[ "Adding Clearcoat freezes Blender with error \"Execution of the command buffer was aborted due to an error during execution\"\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 5700 XT 1.2\n\nBroken: version: 3.5.0\nWorked: Unknown\n\nAdding Clearcoat to a Surface freezes Blender, with Console logs showing only an \"Execution of the command buffer was aborted due to an error during execution. <private>\" error.\n\nOnly appears to happen when using Metal, using Blender in OpenGL mode doesn't have this issue. The issue is also present on brand-new projects with just the default cube.\n\n1. Create new file (Eevee renderer)\n2. Change the Clearcoat amount of the default cube from the Materials tab.\n3. Blender crashes usually within seconds, with the default cube I've found it freezes more easily if you use the sliding mechanism to change the Clearcoatness.\n\n", "Wrong reflection in Reflection Plane when Ambient Occlusion is also turned on\nIntel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB\nWindows 7 x64\n\nBroken: 2.8, 2.9\nWorked: n\\a\n\nReflection Plane object produces wrong reflections when Reflection Plane is nearly perpendicular to camera and Ambient Occlusion is turned on.\n\n1. Open provided Blender file, switch to Rendered view and observe how Reflection Plane reflects the opposite wall as almost black.\n2. Disable Ambient Occlusion and reflection will become normal.\n3. I have also noticed that if you change Ambient Occlusion value to something like 40 mm, reflection will be turned into a gradient.\n4. Moving Reflection Plane away from the wall does absolutely nothing, if you switch to the second camera that faces Reflection Plane straight on, back wall will look normal but side walls will become dark.\n[WrongReflection.blend](WrongReflection.blend)\n\n", "Burned Out Screen Space Reflections in Eevee Viewport - Nvidia GT 750M\nOperating system: macOS 10.14.3\nGraphics card: NVIDIA GeForce GT 750M 1024 MB\n\nBroken: 2.90.0\nWorked: 2.79\n\nIn some cases I detected that the Screen Space Reflections in Eevee Viewport gets out of control.\nA few seconds after switching to the viewport (even when viewport samples are set to 1) the issue kicks in and – as the sampling continues – an increasing percentage of the reflections get totally white.\n\n\n\nThe renders are correct.\nSurfaces affected by reflection planes are correct.\nHiding the chandeliers meshes solves the problem. Switch tab and back for this to work.\n\nI was able to strip down the scene and identify the source of the problem: Originally I set up the glass material with \"multiply\" blending. This was converted (when opened with belnder 2.82 alpha) to a \"Shader to RGB\" and a \"Transparent BSDF\" node. [1]\n\nThe \"Shader to RGB\" causes the problem in 2.82.\nThe \"multiply\" blending of the material causes it in 2.8.\n\nOpen the attached file.\nSwitch to LookDev or Rendered viewport.\nWait.\n\n[Chandelier.blend](Chandelier.blend)", "[cycles] - Distorted highlights when rendering detailed bump maps\nOperating system: Linux Mint 20.1 Ulyssa 64-bit\nGraphics card: GeForce RTX 2060\n\nBroken: 2.83, 2.92, 2.93 alpha\n\nWhen rendering dense scratch textures as bump maps, highlights appear as distorted rays instead of circles around the light. The error occurs with any high-frequency lines/micro-scratch image, including procedural and high-resolution textures. Changing bump strength/distance affects the size of the rays, but does not correct them. I have also tried different texture filtering and mapping options, and they all produce similar results.\n\n* Create/download a high density micro-scratch texture (long, thin lines in random directions)\n* Use the texture as height input for a bump node - more tiling will increase the effect\n* Set the bump strength or distance to a low value, around 0.005\n* Connect the bump node output to a glossy/reflective shader \nThe attached blend file has two bump map examples, and a normal map created from one of the bump textures. The normal map has the desired result, while the bump maps have distorted highlights/reflections.\n\n[scratch_highlight_example.blend](scratch_highlight_example.blend)\n\nResult from bump map (second one in blend file)\n\n\nExpected result, using normal map (created from previous bump map)\n\n\nMany thanks", "Hair particles: 'Use modifier Stack' option with simple children leads to texture disappearing in cycles [interpolated children are fine]\nOperating system: Mint Tara\nGraphics card: GTX 1080ti\n\nBroken: 2.79 latest, 2.80 latest\n\nThe render engine can't read a texture while using the \"use modifier stack\" checkbox with simple children. Works fine with Interpolated or None.\n \nOpen the attached blend file.\nSet the viewport to render.\nActivate the \"use modifier stack\" checkbox.\nTexture disappears.\n\n[hair_use_modifier_stack_texture_bug.blend](hair_use_modifier_stack_texture_bug.blend)", "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", "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", "Eevee flicker with ortho camera parented to specular object\nOperating system: Linux, Debian Stable\nGraphics card: Nvidia GTX 970. \n\nOperating system: Suse linux 15.1, \nGraphics card: ? Nvidia driver 450.57\n\n\nBroken: Blender versions 2.90, 2.91\nWorked: Never\n\nObjects with specular reflection parented to orthographic camera causes flickering in eevee.\nCycles doesn't have this issue\n\n[lock-reverse-sidebar_11152.blend](lock-reverse-sidebar_11152.blend)\n\n- Open file\n- Switch viewport shading to rendered\n- Play animation", "Invisible object in preview mode\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: AMD Radeon HD 8600/8700M ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0\n\nWhen I enable Material Preview mode in Blender, the object becomes invisible regardless of the Render Engine. Also the object is invisible with Rendered mode enabled when I use the Render Engine - Eevee. \n\nI don't know how it happened but I can't repair Blender. I reset all settings to factory, reinstalled the application, but it did not help. Can you help me, please?\n\n\n\n\n\n\n\n\n\n", "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.", "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", "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", "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", "Viewport 3d is not updated with VSE driver\nBroken: 2.82 (unknown which revision, custom build without buildinfo)\nWorked: (unknown)\n\n[system-info.txt](system-info.txt)\n\nViewport is not updated for a material that is driven by a VSE driver.\n\n[ejemplo.zip](ejemplo.zip)\n\nChanging the VSE strip opacity doesn't update the viewport.\n\n**More info from user**\n\nI am creating an addon to transform eevee into a VSE. I encountered several problems, and one is that by changing the values ​​\"chanel\", \"opacity\" or moving the strip (it should disappear). the changes are not visible until the 3d view is moved. Just there it is updated. This makes it uncomfortable to work with the addon. The only change that works well is when changing the resolution X of the render, when playing the video or scrolling through the timeline, everything looks correctly.\nEverything is being controlled by drivers.", "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" ]

[ "screen space reflections\nOperating system: windows 10\nGraphics card: gt 730\n\nBroken: (blender 3.3.2)\nWorked: (blender 3.0)\n\n**screen space reflections**\n\nBlender 3.0 with screen space reflections off\n\nBlender 3.0 with screen space reflections on you get the reflections and the Roughness keep the same.\n\nBlender 3.2.2 with screen space reflections off \n\nBlender 3.2.2 with screen space reflections on you get the reflections But everything becomes reflective like it have 0 Roughness (I test it on version 3.4.1 the same problem )\n\nthis is the blend file I used :\n[Test SSR .blend](Test_SSR_.blend)", "Regression: Screen Space Reflections on EEVEE render shaders with roughness a minimum regardless the value or map in the shader\nOperating system: Linux Manjaro \nGraphics card: Geforce 590\n\nBroken: 3.2 and succeeding versions\nWorked: 3.1\n@Tyson-Marchuk found the first bad commit: 80859a6cb2\nAlso mentioned the potential fix: #102423#1459379\n\nScreen Space Reflections on EEVEE render materials incorrectly\nThe shaders roughness valuue or map are ignored and all shaders are render \n| 3.3.1 (SSR off) | Broken: 3.3.1 (SSR on) | Worked: 3.1.0 (SSR on) |\n| -- | -- | -- |\n|  |  |  |\n\nThe problem became evident in a scene with medium or high roughness by enabling the Screen Space Reflactions\n\n[SSR.blend](SSR.blend)" ]

[ "Blender development todo list -- Tools (migrated from wiki)\nNOTE: this is a direct dump of Tools (without cherrypicking the valid items)\n\n\n# Scene\n\n**New scene - Full Copy**\nSeveral things are still not copied or reassigned when using this tool:\n- [ ] Particles - Not even the particle systems themselves, not to mention re-assigning 'objects' pointers to copied IDs too, see #40891.\n- [ ] Textures when they are only used by e.g. modifiers (i.e. not by a material, world or lamp).\n- [ ] Textures used by modifiers are not re-assigned to new copies when possible either (only objects are handled).\n\n# Library System\n- [x] Hard (or even impossible) to relocate libraries that have been moved (#44958). Addressed in id-remap branch, hopefully merged in 2.78.\n- [ ] 'Find Missing Files' does not work with .blend lib files (impossible with current master, easy to do once id-remap is merged, see #47774).\n\n# Transform\n- [ ] API and draw code for manipulator needs to be redone still. For this reason no manipulator drawing happens during transform.\n- [ ] Manipulator click behavior (left-click-release a manipulator axis to enable a transform on that axis -> perform transform and wait for another left-click to confirm. Expected behavior from 2.4x)\n- [ ] Operator parameters in toolbar don't have to be drawn all always, needs cleanup.\n- [x] Transform redo fails when you change mode during transform (use R S G keys).\n- [x] Mirror of rotated objects doesn't always work correct #37928\n- [ ] Numeric input for rotational transform resolves to modulo 360. Should it? #40167 - ''possible fix included''.\n- [ ] Transform along the axis does incorrect axis projection in certain circumstances #40893\n- [ ] Scaling from zero is not possible with 'S' shortcut (#44551).\n- [ ] Transform redo fails when mouse move is required (#50419).\n- [ ] Apply Scale: Option not to scale all object properties (curve radius, empty scale, text scale... etc). \"Scale Properties\" toggle.\n- [ ] Cursor input to calculate rotation can accumulate a small amount of error (impacts bend and rotate) #53590\n- [ ] Armature edit-mode transform proportional editing doesn't work (#53992).\n\n**Transform Snap**\n- [x] Snapping to vertex slide (Taking into account multiple selections)(#48927).\n- [x] Snapping to face local axis doesn't snap the vertex to the face surface (#38438).\n- [ ] Snapping to self doesn't work with proportional edit-mode (#44793).\n- [ ] Snapping doesn't work for Boolean modifier (#35023).\n- [x] Snapping in object mode rotates object around their origin, instead of rotating them around their snapped point (#42362).\n- [ ] Snapping doesn't behave as expected when having several parented objects (#41199).\n- [ ] Snapping between multiple objects can give some working-as-intended, but in practice quite undesirable behavior (using bounding box) (#47171).\n- [ ] Snapping falls back to using a grid, however this isn't clearly communicated<br>(advanced snapping on faces, vertices, etc. only works on move/rot/scale, see #42798).\n- [ ] Snap to cursor and snap to grid could be made to work more consistently: See (#34441)\n- [ ] snap_project individual element on surface of other objects - watch?v=XrEPpHGoKlk&feature=youtu.be&t=1m10s;\n- [ ] Snap does not work for NURB surfaces (#78434);\n\n# DupliObject\n- [ ] There is no good way to control the rotation of objects in DupliFaces option (rotation is computed from face normal (which is good) and first three vertices of the polygon (which is weak, epic fail with e.g. Mirror modifier). See #37365.\n- [ ] Duplifaces don't work well with the mirror modifier, see #37820.\n\n# Curves\n- [ ] Capping front / back -ends of beveled curve doesn't work, see #26136\n- [ ] Constructive modifier kills generated UV mapping on bevelled curves, see #27411\n- [ ] Surfaces Make Segment rotates U/V even when it's not actually needed, see #31480\n- [ ] Couldn't cycle through vertices with the same location using mouse selection, see #36760\n- [ ] Curve tessellation might work not as it's expected to, see #37386, #40171\n- [ ] Curve deform doesn't work if curve is zero-scaled #38907\n- [ ] Nurbs clamp order by total number of points, this should be clamped at runtime #40378\n- [ ] Handling of non-smooth control points with (Bézier/poly) curves in general, and their rotation in particular, could be improved when generating BevelList & Path, see #44393.\n- [ ] In some cases Bevel should prefer \"clip\" behavior over trying to keep constant shape across the path #50720.\n\n# Text objects\n\n- [ ] Font formatting interface should be improved (#49599)\n- [ ] Default Bfont doesn't support russian characters (or any other non-european charset) in text object, while UI does show Russian characters (#53744)\n\n# Metas\n\n- [ ] Some shapes (Cube) for eg. draw far outside the tessellation bounds making them hard to select. see #47455\n\n# Meshes\n\n**Mesh Editing**\n- [ ] Knife & loopcut\n - [ ] Knife/loop cut need to work properly with operator properties/redo\n - [ ] Restore Quad Corner Cut Methods (Innervert, Fan and Path) for Subdivisions and Knifecut\n - [ ] Knife cuts side-on, intersecting the entire face, could be detected and ignored #43816\n- [ ] Mirror edit mesh operator (Ctrl M) fails to flip normals leaving an incorrectly mirrored mesh (turns normals inside)\n- [ ] Add option to disable n-gons usage for tools (might be useful for some usages) (see #31268)\n- [ ] 'Checker deselect' could be modified to work in some cases where it currently fails, (see #34544)\n- [ ] Merge meshes: add option to join UVs (and other CD layers!) by names rather than index (see #36749).\n- [ ] toolbar mesh Extrude operator inconsistency (see #36977).\n- [ ] Shape keys: Enhance memory usage (not storing vcos for unchanged vertices? See blender/blender-addons#39287).\n\n- [ ] Bevel\n - [ ] Better handling of profile=1, profile=0.25, and implement profile=0 cases (see #39132 and #38458 and #40278).\n - [ ] Generalize to handle several manifold sheets touching at a point (see #34678).\n - [ ] Improve clamping code (see #38871).\n - [ ] More options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n - [ ] Treat more cases like \"pipe\" to avoid bulges (see #40258)\n - [ ] Option to have bevel not create n-gons (see bf-funboard thread)\n - [ ] Sometimes leaves degenerated geometry (#48174)\n\n- [ ] DataTransfer/Geometry Matching\n - [ ] Add 'matching' algorithms based on 'similar shape' rather than simple items proximity/raycasting (see #46762 for a usecase) - WARNING: most likely advanced, mathy project!\n - [ ] A review of islands handling could also be useful, current code is rather complex and not so efficient.\n\n- [ ] Discussion\n - [ ] Extrude behaviour on cancel, see (#23492).\n\n**Text Editing (3D)**\n- [ ] When converting beveled text into a mesh - there are many doubles.\n- [ ] Text object requires better integration with the system clipboard, #38556, #46330\n- [ ] Support font kerning (#47725).\n\n**UV Unwrapping**\n- [ ] Settings for pack margin in different operators behaves inconsistently, see detailed description: 039547.html\n- [ ] Remove doubles has an option to Merge with unselected verts, This would be very handy for welding also.\n- [ ] Detect convex mesh without seams on unwrap and print warning.\n- [ ] Unwrapping fails on a particular strange topology (#31145)\n- [ ] Unwrapping for concave polygons is badly supported #41810\n- [ ] Face/edge selection in UV Editor does not work same as in 3DView (#52276).\n\n; Not ported from 2.4x\n- [ ] Click Project from face\n- [ ] Consolidate into one image\n- [ ] Billboard render on active\n- [ ] Unwrapping could run out of stack size for tricky geometry #42524\n\n**Vertex Paint**\n\n- [ ] Undo in vertex (and weight paint) behave differently to sculpt/project-paint modes regarding undo steps #52993\n\n### Sculpt & Paint\n\n**Sculpting**\n- [ ] Check documentation and fix hotkeys which could be useful for artists (or remove redundant hotkeys and update documentation), see #26017\n- [ ] Grab + symmetry can make things shoot off more quickly than they should (strength of movement is being double counted), see #25370\n- [ ] Not all drawing modes supports PBVH drawing, see #32454, #38608, #38609\n- [ ] Not all shading modes are supported for dyntopo, see #34010\n- [ ] Hidden faces are treated as hidden by sculpt tools but when PBVH drawing isn't used, the hidden faces display (and cant be edited), see #33078\n- [ ] Multires modifiers: makes mesh invisible after leaving sculpting mode, see #36591\n- [ ] Multires sculpt: artifacts grabbing between different levels #40465\n- [ ] Dyntopo does not support restoration when aborting a stroke, see #46456.\n\n**Painting (3D)**\n- [ ] Solve projection paint issue when one vertex in a face in behind the view in perspective mode<br>index.php?func=detail&aid=26393&group_id=9&atid=498\n- [ ] Continue to unify paint modes\n - [ ] Consistent brush texture mapping across paint modes (sculpt/tex paint/proj paint).\n - [ ] Consistent brush options, eg. 'Rake' or 'Anchored' in texture paint.\n- [ ] Make paint of displacement texture apply real time on model (optional). (#24657)\n- [ ] Allow view center to work for selected/active face in WPaint mode.\n- [ ] Viewport navigation for painting modes can be improved #48113\n- [ ] Users can perform strokes which apply to a huge number of pixels (by accident) - this could be handled gracefully #52351\n\n**Painting (2D)**\n- [ ] Clone image painting should support the same translation/rotation/scale tools as stencil texture mapping.\n- [ ] Stepped lines in image editor painting, blending should use float coordinates and interpolate (#52610)\n\n\n**Grease Pencil**\n- [ ] Default attach point of GP data is confusing ((#21969))\n- [ ] GP ignores color management ((#50149))\n\n### Materials\n- [ ] Improve handling of linking of materials to Object/Data. Right assigning a material-less data to object the materials from object are gone too (blender/blender-addons#23805, #52484).\n- [ ] Fix EnvMap update, it can depends on many different things in the scene (#41900).\n\n### Modifiers\n- [ ] Make (at least some) generative modifiers to handle custom normals (like e.g. mirror one, see #44058).\n\n**Array Modifier**\n- [ ] Has been re-written to use bmesh, making 2.63 slower then 2.62, There are areas where speed could be improved, for full info see #30695\n- [ ] Textures from cap objects are completely ignored and no way to override them, see #33578\n\n**Boolean Modifier**\n- [ ] Boolean modifier does not preserve vertices/edges data, see #32203, #33548\n- [ ] Issues with degenerated faces, see #30447\n\n**Decimate Modifier**\n- [ ] Limit decimation along seams (UV vertex color, etc), see #32203\n\n**Explode Modifier**\n\n- [ ] Does not preserve UV maps when using Cut Edges option (#46514)\n\n**Multires Modifier**\n- [ ] Only solid draw mode uses optimized drawing\n- [ ] \"Applying Base\" gives spikes on lover levels sometimes, see #35560, #37997\n\n**Bevel Modifier**\n- [ ] Does not preserve edge custom data, see #35314.\n\n**Simple Deform Modifier**\n- [ ] The bend/taper/twist options use fixed axis, add XYZ options would be nice. #33712\n\n**Skin Modifier**\n- [ ] Skin modifier very slow in some cases, see #40770\n\n**Solidify Modifier**\n- [ ] Curves tesselation creates zero area faces which solidify doesn't handle well #52170\n\n**Remesh Modifier**\n- [ ] Mesh data at extreme distance from origin (2**24), crashes #47209<br>''Note, this is a real corner case - yet its a bug because it shouldn't crash.''\n\n### Physics\n- [ ] Allow using multiple baked caches on a single object (having different frame ranges), see #41896.\n- [ ] Bullet: High memory usage for objects that don't have scale applied (#35799)\n\n**Baking**\n\n- [ ] Generic issue: baking ignores making pointcaches when modifier preview has been disabled. Doesn't need fix - but let's keep track of this for future work.\n- [ ] Point caches do not work well with time remapping (example #35968)\n\n**Cloth**\n- [ ] Proper handling of rendered subframes without baked pointcache, for more info see (#21948)\n- [ ] Proper handling of different vertices placed at the same position with \"Soft Body Self Collision\" option turned on (see (#26956)).\n- [ ] Cloths doesn't allow preview during bake (see (#30490)).\n- [ ] Dupli-group cloth in NLA fails (#29838)\n- [ ] 'Emit from: verts' not working as expected when deforming #36237\n- [ ] Collision of hairs doesn't works properly #39219\n- [ ] Memory optimizations are possible for cloth #42577\n- [ ] Cloth pre-roll feature is totally weird and needs reconsideration #40103\n\n**Collisions**\n- [ ] Collision modifier updates it's data structure even if there are no physics that need it (can be slow), a check should be added to make sure the data is actually needed, see (#26965).\n- [ ] Force fields and collision objects are not included in DupliObjects. This is mostly a design decision (duplis being a purely visual feature), but would be nice to support at least in groups. #35264 #36300\n\n**Hair**\n- [ ] Better handling of collisions & force fields for dynamic hair\n- [ ] Wave kink direction is totally uncontrollable, probably there needs to be a way to define hair tangent direction in particle edit mode.\n- [ ] Adding hair in particle mode only uses the deformed mesh, see (#25689).\n\n**Particles**\n- [ ] Particle emission between frames is only accurate for object level emitter/parent animation, for parenting or constraints an interpolation method needs to be implemented, but before this can be done pointcache code has to get some changes too. See (#36516) for more details.\n*; Parent animation is now supported {{GitCommit|c24a23f. Similar issue still persists for non-animated parents (e.g. rigid bodies) though #39923\n- [ ] Reactor particles\n- [ ] Conversion from some old files could be better\n- [ ] Vector blur + particles being born/dying doesn't work properly, see (#23320).\n- [ ] Metaballs don't work with particles when the particle view setting isn't \"render\", see (#25794) for more info.\n- [ ] \"Constructive modifiers before particles\" is still an open issue, but some way to handle this gracefully would be really nice, see (#25838) for more info.\n- [ ] Density of particles can't be animated with animated textures, see (#28212).\n- [ ] Instanced objects do not show in particle edit mode, see (#28431).\n- [ ] Issue with ghosting particles if you don't bake first. (#28116)\n- [ ] Linked groups: Force fields and guides only work if you use \"Effector Group\" feature, set to its own group.\n- [ ] Particle Hair dynamics: stops working after using \"Add tool\". (#30557)\n- [ ] Instanced objects don't draw in Particle Edit Mode. (#31913)\n- [ ] Child particles Interpolated mode only works well for Hair, for other particles it doesn't take particle lifetime into account. (#33390)\n- [ ] Particle emission doesn't support NGons.\n- [ ] Particle Object duplication doesn't work with Mirror modifier (#34705)\n- [ ] Particle systems fail to duplicate for smoke simulation (#34705)\n- [ ] Random distribution of particles fails in specific setups (#35598)\n- [ ] Default point cache step of 10 frames fails in some cases, see #38563\n- [ ] Particles tangent rotation control by vertex group missing, see #35103\n- [ ] Texture doesn't affect grid particles #40404\n- [ ] The particle system needs to be set to 'Newtonian Physics' for texture to influence the size, and with global gravity turned off #28263\n- [ ] Multiple issues with particles rotation #32340, #44088\n- [ ] Particles hidden in viewport reappear during rendering #40463\n- [ ] Particle initial speed is not properly inherited from the parent #41305\n- [ ] Point density textures can not be used to control particles #44901\n- [ ] Particle duplication in general is rather poorly implemented (no relink of used datablocks, no duplication of psettings ID when duplicating objects, …) #45843.\n- [ ] Grid distribution only supports From Dupli Generated, but not UV. Potentially could use nearest face. #48928\n- [ ] Particles aren't spawned correctly, they are sometimes generated at the same location as other particles, or at the object's origin. See #50135 for one scenario.\n- [ ] Particle editmode could have its 'own' [X-mirror] option (and not reuse editmode option). See #53872\n\n**Rigid Body**\n- [ ] Velocities are not cached, which prevents a proper state update when cache has time gaps #50230.\n\n### Image & Video\n\n**Compositing**\n- [ ] DOF Defocus node: fStop close to 128 fails to give good results, stay away from that value! (#24534)\n- [ ] DOF node gives no realistic results as users expect, documentation needs upgrade for it.\n- [ ] Defocus node is very slow when large blur radius is needed, could be optimized somehow (mipmap, summed area table?) (#29481)\n- [ ] Defocus node does not work nicely without a camera controlling the blur radius. This makes external compositing workflows with defocus difficult. At the heart of this is a design conflict, because defocus is not a true postprocessing effect #36745\n- [ ] Fast Gauss (Gabor filter, Young/VanVliet) has bad results for edge cases. Needs image processing guru (#25543)\n- [ ] Check on DPX and ASC_CDL and (#27377)\n- [ ] Map UV makes mapped images blurry, see #31868\n- [ ] Some nodes does not preserve alpha channel replacing it with fully opaque, see #32580\n- [ ] With new compositor, on loading files a compositor doesn't start (for existing buffers), so viewers remain empty as well. #35417\n- [ ] Ghost Glare is of limited use, needs clarification and probably a more sophisticated generic lens flare alternative #30389 #36488\n- [ ] Some node inputs require a single constant value and don't work with image-based per-pixel values (#36585). This leads to confusion when nodes apparently don't work, because nothing prevents linking such variable values into constant inputs. Compositor nodes should keep track of constant values and limited inputs on the node level (also in node groups!).\n- [ ] Compositor gives unexpected results with specific curve mapping due to precision loss, see #36621\n- [ ] \"Full Sample\" merging does not work with the File Output node, sample merging happens only for render result outside compositor. Real-time editing might also be improved to deal with samples better (#36811, #39143)\n- [ ] Accumulation method in the Lens Distortion node causes artifacts on noisy input #37462\n- [ ] Compositor does not support render slots #43260\n- [ ] Scaling down produces artifacts due to lack of ellipse filtering of sampler #51070\n\n**Image formats**\n- [ ] Upgrade our DPX code to read newer or different versions, copy the ImageMagick code? (#24716)\n- [ ] No support yet to output images in user chosen color space. (#37650)", "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)", "Angle input fields fail to accept units when scene rotation units are set to radians\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nAngle input fields usually accept rotation units as 'd' for degrees and 'r' for radians after the entered number, however when scene rotation units are changed to radians in the scene properties, this functionality stops working. Blender reports an error when units are entered: \n\n\n> Error evaluating number, see Info editor for details: File \"<string>\", line 1\n> 2d\n> ^\n> SyntaxError: unexpected EOF while parsing\n> \n\n\n\n\n\n\n1. Open new scene and change rotation units to radians in the Properties Editor, Scene tab, Units section. \n2. Type some number followed by 'd' for degrees in any rotation input filed.\n\n\n", "Viewport: Auto-Depth rotation ignore transparent image reference empties\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\ncant rotate around partially occluded image objects.\n\n\nopen file, make sure rotate around mouse is enabled in preferences. hover mouse over either side images and hold in the mouse wheel, move the mouse, the view will rotate around the mouse. Now do the same for the middle image, the view no longer rotates around the mouse.\n\n[rotate around mouse bug with image objects that are occluded.blend](rotate_around_mouse_bug_with_image_objects_that_are_occluded.blend) \n\n", "Particle system: late update of object`s tracking axis after «object`s rotation» switching.\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 13)\nWorked: Apparently never (2.79 has the same problem)\n\nAfter switching on/off object`s rotation for particles, their rotation updates wrong and I need to switch something at initial object to update rotation of particles.\n[2020-04-22_16-08-56.mp4](2020-04-22_16-08-56.mp4)\n\n- Make particle system, that emits object.\n- Switch object`s tracking axis to +Z (relations)\n- Switch Object`s rotation in the particle system render tab.\n- Rotation is wrong and not changing until object`s transform not updated.\nor\n- Open attached file\n- Move the \"Cone\" object to update the particles\n- In the Cube particle settings, enable and disable `Object Rotation`\n[particle system rotation tracking no update.blend](particle_system_rotation_tracking_no_update.blend)", "Multi-Object-Mode: Operators that need refactor on their logic\nSome operators are working for multiple-object editing however are still not fully benefiting from it.\nThe most common case is that the operator works but only if all the objects have the same transformation matrix.\n\n* **~~MESH_OT_select_similar~~** (SIMEDGE_FACE_ANGLE, SIMFACE_AREA, SIMFACE_PERIMETER). 0c1934f3c2\n\n* **MESH_OT_knife_project** and **MESH_OT_knife_tool**.\nNeed to convert the code from screen space to world space. More details on [D3637](D3637).\n\n* **UV_OT_weld** (UV_STRAIGHTEN, UV_STRAIGHTEN_X, UV_STRAIGHTEN_Y).\nThe current logic to determine the first and last selected vertex is not very compatible with multi-object. We should be able to select vertices from different objects, and use their position to determine the line extremes.\n\n* **LATTICE_OT_flip**\nThe axis need to be in world space, not local space.\n\n* **~~CURVE_OT_select_similar~~** (SIMCURHAND_DIRECTION). ab77f5b5fe\nNeed to calculate direction taking scale into consideration.", "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", "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.", "Transformation Orientation list box on top panel is not updating\n{[F8902676](transformation_orientation.jpg)}**System Information:**\nOperating system: Windows 10\nGraphics card: NVidia (PC: GTX 1060 6 GB, LAPTOP: GT 650M 2GB)\n\n**Blender Version:**\n2.8*.*, 2.90.0\n\n**Description:**\nTransformation Orientation list box on top panel is not updating if you create custom orientation and then delete it by shortcuts.\n\n**Repro:**\n1.) Setup shortcuts for (+) Create Orientation and also for (x) Delete Orientation\n(in my case *[shift .]* & *[shift /]* with permanently checked *Use After Creation* & *Overwrite Previous* in Keymap Preferences)\n2.) Create any custom orientation by the shortcut\n(whatever: edit mode components or object mode objects)\nNow list box is updated correctly after creation with the name of currently created orientation\n3.) Deselect component or object used for orientation - this is important, otherwise 5th step is working\n4.) Delete custom orientation by the shortcut\n5.) You will see still the name of previously created orientation in top panel list box even though it should be Global\n\nThis is my first report, so I apologize for any shortcomings.", "Scaled Rigid Body causes issue (moving origin or mesh breaks collision, double transforms on negative scale)\nOperating system: Ubuntu 18.04 LTS\nGraphics card: Intel HD 4000\n\nBroken: 3.0\nBroken: 2.90.1\nWorked: I don't know if this works with any other version, I created the file using 2.90.1.\n\n\nSee the attached .blend file. This file contains two errors with Rigid body simulation. I'm filing both errors in one bug because these may be related (both happen in one example simulation).\n\nError 1: object origin distance from another object changes interaction between objects\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that \"Ball\" is attached to the chain.\n3. Stop the animation and jump to first frame.\n4. Select object \"Ball\" and from menu Object - set Origin - Origin to Center of Mass (Volume)\n5. Play the animation to verify that \"Ball\" is no longer attached to the chain.\n\nError 2: Rigid body type \"Active\" changes orientation of the object\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that chain is attached to the object \"Cube\".\n3. Stop the animation and jump to first frame.\n4. Change \"Cube\" Physics properties - Rigid body - Type: Active and Settings: Dynamic\n5. Play the animation and notice that Cube is now rotated 180 degress around the X axis. Obviously this results in chain no longer connected to the cube as expected and chain and Ball drop directly down during the animation.\n\nExample .blend file (cannot simplify more because Blender seems to be unstable with this file):\n[physics-test.blend](physics-test.blend)\n\n**Additional information**\nIt seems that I can work around Error 1 by selecting all items and applying \"Rotation & Scale\". I think this should not be required to get two objects to interact during simulation so I'm reporting the problematic file as-is. I cannot figure out the reason nor workaround for Error 2.\n\n$ apt policy blender\nblender:\n```\nInstalled: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nCandidate: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nVersion table:\n```\n *** 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0 500\n 500 ubuntu bionic/main amd64 Packages\n", "Generated Texture Coordinates Don't Update in Edit Mode.\nOperating system: Linux-5.15.0-52-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.1\nWorked: N/a\n\nGenerated texture coordinates don't update in edit mode, example when translating the vertices. I tried changing other coordinates, (uv, object), they all update fine in edit mode.\n\nBased on the default startup or an attached .blend file \n[Generated_editMode.blend](Generated_editMode.blend)\n1. Preview generated texture coordinates.\n2. Go into edit mode.\n3. Select everything and move it around in one direction (ex the left/-x).\nExpected result is the generated coordinates are identical to before moving the cube. Tab out of object mode and then it will update. \n\n", "Follow Active Quads affects on non-selected islands, when selected several objects\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.4\n\nWhen using Follow Active Quads, it is expected that it affects only the island(s) whose faces are highlighted. However, this works when one object is being edited, when editing several objects, the operator affects random islands of other objects\n\n[2023-01-18 05-07-25.mp4](2023-01-18_05-07-25.mp4)\n[untitled.blend](untitled.blend)\n1. execute Follow Active Quads first with one selected cylinder, and then several. The cylinders can be taken from the file above in order to shorten the time", "Apply scale normal flipping\nThe apply transforms operator in blender can apply negative scaling to an object.\nHowever there is two ways to do this. If you scale your model with a negative\nvalue in editmode, you get flipped normals. This is because the vertex order in the\nfaces is preserved and that is what determines the normal. In object mode however,\nthere is a flag in the render engines to flip the normals back, if they are flipped due\nto negative scale. This inconsistency creates the problem with the apply transforms\noperator. The following image shows on top the behavior in editmode and at the\nbottom the behavior in object mode.\n\n\n\nOf course both behaviors have their reasoning to exist.\n\nOne reason for the rendering flag to exist is, that instances of the same object can\nbe mirrored without causing normal problems. Obviously there is no other solution\nto that, since the underlying mesh is the same for all instances, so the render engine\nhas to handle negative scales.\n\nOn the other hand, in editmode you don't want to change the loop order for all your faces\nif you are just scaling. It makes much more sense for editmode scaling to just change\nvertex coordinates. That means you need to fix the normals manually.\n\n\nThe apply operator can only be called in object mode. From object mode the current\nbehaviour looks as if it was flipping the normals. Actually it is just applying the\ntransform \"in editmode\", which looses the negative scale information for rendering.\nThis looks like a bug to some users and is confusing for new users. Users have actually\nrequested this to be changed:\n\n4Zdbbc/\n\nI also heard this request on the BCON22.\n\nHowever the question arises, do we add another option or do we just always flip the\nnormals to make it consistent with rendering? Another question is what happens to\naddons which are using this operator if the operator gets changed in this way?\nHow many addons are actually using apply scale on negatively scaled objects?\nDo those addons fix the normals by flipping them manually?\n\nThere is already a patch available to add this normal flipping without an option:\n\nD16382", "Batch Rename: Preset support\nThe batch rename operator supports chaining operations, allowing for setup actions which users may want to re-use.\n\nThis is a convenience feature.\n\nExample use cases (which may be possible in the future):\n\n- *Bones*\n - Add a prefix.\n - Number the object/bone based on it's level in the hierarchy.\n - Add a L/R suffix based on it's side.\n- *Objects*\n - Rename them to match their object data.\n - Number them, ordering based on their Z locaiton.\n", "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." ]

[ "Gizmos in Object Data are not working properly\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nWhen I am trying to enter new rotation angle in Object Data for Y axis, it is moving by X axis and vice versa. And when I change the angle with Rotation Tool (Green Indicator), in the inspector panel the X Axis Rotation angle is changing and vice versa.[box_issue.blend](box_issue.blend)\n\nIn attached file open the Object Tab in the Inspector. Try to rotate the highlited object by X or Y axis. Compare axis You rotate with Object data.\n\n" ]

[ "Stitch by matching target edge length\nAdditional option to existing operator **stitch** that scales one uv island to match the other uv island by matching the edge lengths of the target uv island\n\n**Starting point**\n\nA couple of edges selected before running “stitch operator”\n\n\n\n\n**Undesired result**\n\n\n\nThe uv island that is being stitched to the bigger uv island is still very small\n\n\n\n**Desired result**\n\nThe loose UV island has the same texel density as the UV island that it stitches to \n\nSuggested approach:\n- Store\n - Original pinning\n - Original seams\n- Run “seams from islands”\n- Clear seams on selected edges\n- Pin all but the UV island that will stitched to bigger uv islande\n- Unwrap\n- Restore \n - Original pinning\n - Original seams\n\n", "Incorrect and Confusing Units for String to Curves Node\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\n\nIncorrect and Confusing Units for String to Curves Node, depending on Scene / Units\n\nIf Scene / Units is set to Metric this node looks like this:\n\n{[F13984816](image.png),width=100%}\nCharacter spacing is shown in meters, and that is so odd that it might as well be shown in \"number of chickens\". Our current Character Spacing is already done strangely enough. This value is divided by 2 then 0.5f is subtracted from it. That value is a portion of the font's em square that is added to each character. So a value of **1 means no change** to character spacing. 0 means that 0.5 of an em is subtracted from each one. That \"1\" means default is bad enough, but much worse to show it as one meter. \n\nAt minimum we should show this as unitless. Better would be to not do the division and shifting and therefore show \"0\" as default and add \"em\" as unit. This would match with CSS letter-spacing.\n\nWord spacing is similar, but is a factor multiplied against each character's advance. So again, \"1\" means normal, 0 means that a space has no width, a 2 means a space is twice as wide. No relation to grid size. So showing \"1 meter\" is pretty bad.\n\nThis also should be unitless. Ideal would be to change it from a factor to a absolute value added to the width of space characters. That way it can also be \"0\" by default and show \"em\" as units. This would match with CSS word-spacing.\n\nFor even more oddness, this what it looks like in Imperial\n\n{[F13984832](image.png),width=100%}\n\nAs in normal and default character width and normal word spacing are shown as \"3.28 inches\"?\n\n", "Extra face dots in UV Layout editor (GPU subdivision OFF, On Cage OFF in Subdivision modifier make a difference)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4835\n\nBroken: version: 3.4.1\nBroken: version: 3.1\nWorked: not since GPU subdivision was introduced (so in a way, it was working in 3.0)\n\nExtra random faces appear in the UV Layout editor\n\n- I can mosty repro this if GPU Subdivision in Preferences > Viewport > Subdivision is OFF\n- It does not happen at all if I turn off `On Cage - Adjust edit cage to modifier result` on the SubSurf modifier.\n\nIn the attached file, toggle from face select mode to vertex select mode and back to face select mode. (Might have to repeat 5-6 times) Extra faces appear in the UV Layout editor. Also see here: [1457172]\n\n", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "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", "Regression: Boolean Modifier Distorts UVs\nBroken: Blender 3.2.2 Official\nBroken: 2.93\nWorked: 2.92\n\nBroke with a3f091d7ce\n\n\nBoolean modifier distorts UVs of cutter object. In the attached screenshot and blend file. There are two cutters objects of roughly the same shape, one of them works correctly and the other doesn't.\n\n\n\n[tmp_2.blend](tmp_2.blend)", "Mesh Boolean and Bounding Box node joined together make lose the UVs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.5.0\n\nApparently, joining 2 branches of geometry node that contain a Mesh Boolean node and a Bounding Box node make the UV gone. On image attached, the cube on the left with the voronoid is the original cube and on the right it's the same cube with the Geometry node turned on. Maybe other node combination recreate this issue.\nWhen inspecting the branches independently the UV are still working but stop working when adding the Join Geometry.\n\n- Have an object with texture applied. \n- Have a geometry node modifier assigned.\n- The geometry node consists of a Mesh Boolean node joined with a Bounding box node. (I used a transformed node to move the bounding box away and see our object)\n\n", "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", "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", "UVEditor: Add developer option to show vertex, edge and poly indexes.\nSimilar to the 3d viewport we should add option to show the vertex, edge and poly indexes to the uv editor.\n\nWithout I have looked to close to the current code-base this should be possible by adding the option to the UVEditor overlay and some tweaks in the overlay engine. \n\nCurrent work-around is to use a split screen.\n\n", "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", "Bevel modifier disconnects vertices in the UV map\n{[F8713789](2KmuzHs.png)}Operating system: Windows 10 x64\nGraphics card: GTX 970\n\nBroken: 2.83.1, 47b6c332587ca45eddc98e75b3f563e2f17a0d47, probably all 2.8+ versions\n[SM_UVTest.blend](SM_UVTest.blend)\n\nWhen using an angle or weight limit on the Bevel modifier, vertices connecting beveled and unbeveled edges are split in the UV map, producing distorsions.\n\nAdded a blend file. To reproduce the issue, apply the Bevel modifier, and select all faces to see the problematic vertex in the UV editor. \n\nSome context is here : 1241831", "Nonfunctional \"Vertex Weight Proximity\" Modifier's Influence Mask Inversion\nOperating system: Linux-5.4.0-66-lowlatency-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nLast Broken: version: 2.93.0 Alpha\nFirst Broken: version: 2.90.0\nWorked: version: 2.83.13\n\nButton for inversion of Influence Mask (modifiers[\"VertexWeightProximity\"].invert_mask_vertex_group) in \"Vertex Weight Proximity\" Modifier doesn't work.\n\n\n* Open the attached .blend file.\n* Click Invert button of \"Mask Vertex Group\" in \"Vertex Weight Proximity\" modifier (Influence section).\n* Mask is not inverted on the model & Face button of Geometry proximity mode gets wrongly highlighted. (Its highlighting seems to be linked with the Invert button.)\n\n* Another thing I observed is that any change of Geometry Proximity mode (ie. Vertex / Edge / Face) clears both Falloff inversion and Mask Vertex Group inversion if they are switched on. Which was the case in Blender versions 2.83.x too.\n\n[Vertex Weight Proximity Bug.blend](Vertex_Weight_Proximity_Bug.blend)\n\nP.S.: This issue might be connected with the issue:\nT83863\n\nThanks and have a good day!\n", "Breaking nodes API changes for 4.0\n- [x] Remove `Node.width_hidden`\n- [ ] Complete \"Spline\" to \"Curve\"/\"Curves\" rename in geometry nodes\n- [ ] Stop storing node locations relative to their parents\n- [ ] Use a separate type for internal links (in RNA too) (see [D16960](D16960))\n- [ ] Use a separate type for node group interface inputs and outputs and node sockets\n- [ ] Use dynamically allocated `char *` array to store string socket default values", "Misuse of 'U.pixelsize' in code\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: -\n\n\nThe `U.pixelsize` is the user preference for line width in the UI. Go to \"Preference\" > \"Interfece\" > \"Line Width\".\nChanging the \"Line Width\" has an undesirable effect in some cases.\n\n- [ ] Zooming value with MMB-drag in Clip and Image editors\n- [ ] Dynamic-topology Detail Size\n- [ ] Width of tooltips block\n\nThere's an old list of places that need to be re-checked:\nD9604\n\n" ]

[ "Intel Mac Metal: UV Display Stretch Angle Fault Colors\nOperating system:Mac OS 13.3.1\nGraphics card:Radeon Pro Vega 48 8GB\n\nBroken: 3.5.0 - 3.5.1 - 3.6.0 alpha\nWorked: NA\n\nUsing Intel Apple, with GPU Backend Metal enabled\nUV Editing, when you turn on Display Stretch: Angle\nCorrect angles will show faulty colors.\nWhen I switched to OpenGL and restart.\nThe Stretching shows properly as it should.\nI tested using default blender with no addons. Clean install with Default Cube and the error persisted on the versions noted above.\n\n\n\n- Activate blender with GPU Backend: Metal\n- Use a default Cube, within the UV Editing tab\n- In Overlays menu, choose Display Stretch, and pick Angle.\n- Select all the Faces. The colors will appear faulty and extremely inaccurate.\n\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 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", "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 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)", "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", "The image node in GeoNodes can't use UDIM tiles\nOperating system: Windows 11\n\nBroken: 4aac5b92c1bb\n\n\nIt seems like the image texture node is not able to access the UDIM uv range properly. As you can see in the image the objects have proper UDIM tiles that the regular textures can utilize . The image texture node of the geonodesseems to bound the UVs within 0-1 range and cant access the tiles.\n\nPassing the UVs from the modifier does not seem to help with it.\n\n\n\n\nload the attached .blend file\n\nselect the NOUDIM object\n\nopen the geometry nodes graph of the object's modifier\n\nenable the viewer node\n\n[_01122022_2239_12_02_2022.zip](_01122022_2239_12_02_2022.zip)\n", "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", "crash when x-ray and wireframe are enabled\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.1 Release Candidate\n\nWhen I am working and periodically switch to x-ray and wireframe mode, the program crashes. It just shuts down and that's it. I thought it was related to GPU-subdiv, but today it was not confirmed, I turned off GPU-subdiv and literally after about 20 minutes of work when switching on X-ray and wireframe mode the program crashes. I turn on mode the shift+z hotkeys.\nThis happens randomly!!!\n\n\n\n", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "Crash when auto script execution is enabled\nOperating system: Windows 10 64-bit operating system, x64-based processor\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: Blender 4.0.0 7372b3bdda35 and later\nWorked: never? 2.93 fails too\n\nBlender daily build crashes immediately on launch. The blender start screen isn't shown at all, only a grey window which then immediately closes. The crash log indicates that it is a memory EXCEPTION_ACCESS_VIOLATION (see log file attached).\n\n- Open preferences, enable `auto script execution`\n- Save prefs and close blender\n- Rename attached file and replace it with existing startup file\n- Launch blender (crash)\n\n- - -\n<details>\n <summary> Original report </summary>\nStart Blender through Steam, Blender Launcher, blender_debug_log.cmd, blender_debug_gpu.cmd, or blender_debug_gpu_glitchworkaround.cmd.\nA grey window opens with the Blender logo in the top bar.\nThe window closes as Blender crashes.\n\n[ Crashing_4-0-0_daily.blend](https://projects.blender.orgattachment)\n</details>", "Crash with animated displacement modifier in Texture paint mode while playing\nAMD Ryzen 5 2600, 16GB ram\nWindows 7 64bit\nNvidia GTX 1060 6gb (driver version 416.34)\n\n2.79b\n\nI intend to paint a heightmap interactively. So i keyframed a displacement modifier (2 frames) on a subdivided plane and assigned a texture.\nPlaying the timeline should now refresh the modifier every frame. \nPainting in the UV-editor this way works fine, but switching to texture paint mode and painting on the mesh directly crashes blender after about 0.5seconds.\n[HeightmapPaint.blend](HeightmapPaint.blend)\nI attached an example file.\nHit play and in the uv editor paint on the noise texture. This works okay.\nNow switch to Texture painting in the 3d viewport. The moment a stroke is applied to the mesh it should crash (it does consistently for me). ", "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 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.", "Crash when selecting object on Mac\nOperating system: macOS-12.5.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.3.0\n\nSystem crash trying to open einar_hair.blend file\n\nDownload einar_hair.blend fle from ?asset=6072\nSelect any object.\n\nBlender will crash. Also hair is not visible. It's possible, that OS will crash as well. ", "My Blender won't open anymore\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: Every version\n\nWhen I try to open Blender the terminal appears then disappears and nothing else happens.\nBlender worked until today in all its versions, but now it no longer opens.\n\nI tried opening it as administrator, on different versions. I restarted my PC. I updated my drivers. There no bug/crash report or anything.\n\nI don't know what to do.\n\n" ]

[ "UV Local View: Cannot select anything in the UV editor, will crash with 'grab' 'relax' and 'pinch'\nOperating system: W10 v1903 (Build 18362.387)\nGraphics card: Nvidia GTX 1070 Max-Q\n\nBroken: 2.80\n\nIn a new Blender project this works seamlessly, but in the one I am working on right now I want to create some grass blades. Unfortunately I cannot select any vertices edges or faces that show up in the UV editor. Upon using either grab, relax or pinch, Blender will just close.\n\nOpen \"UV Editing\" tab, select one of the grass meshes, go to edit mode, try to select the vertices. Rest goes as described above.\n\n[wasserturm_4_1_gras.blend](wasserturm_4_1_gras.blend)" ]

[ "Tool 'builtin_brush.Grab/Relax/Pinch' not found for space 'IMAGE_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: 2.80.75, 4.0.0 Alpha\nWorked:\n\nWhen the active UV Editor tool is set to Grab, Relax or Pinch and the Tool (left) shelf of the UV Editor is opened/closed while not in Mesh Edit mode, a `Tool 'builtin_brush.Grab' not found for space 'IMAGE_EDITOR'` warning (or similar for the other tools) is displayed in the Status Bar and Blender Info Log (or any Info Editor). \n\nThe attached .blend (authored in 4.0.0a) is set up such that all you need to do is open/close the Tool shelf of the UV Editor.\n1. Open the UV Editor\n1. Enter Edit mode on a mesh\n1. Open the Tool (left) shelf of the UV Editor\n1. Set the active tool to Grab, Relax or Pinch\n1. Exit back to Object mode\n - It may be worth noting that the Grab, Relax and Pinch tools now disappear from the UI\n1. Open/close the Tool shelf of the UV Editor\n1. Observe a warning about the tool not being found\n\n\n\n", "Sculpt Mode Border Hide Tool Todo\n## Sculpt Mode Border Hide Tool Todo\n * - [x] {icon circle color=red} When this tool is selected, it currently shows the wrong tool settings which affect the brushes, not this tool. These should not be visible when this tool is active.\n * - [ ] {icon circle color=yellow} We should add a tool setting to add/remove the mask as you drag. Currently, the only way to remove from border hide, is very hidden: You drag with RMB. This could become more consistent and more discoverable if we added the same Add/Remove buttons as with other Sculpt tools", "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)", "Sculpt Mode - Face Set FK, mirror X is wrong when Scale/Translate using Pose brush with Lock Rotation When Scaling\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\nBroken: 2.92, 3.5.0 Alpha\nWorked: Never.\n\n\n- Change to pose brush.\n- Change brush deformation mode to Scale/Translate.\n- Enable brush Lock Rotation When Scaling.\n- Try to pose the hand.\n- The other hand is flipped.\n\n\n\n\n\nThis is the file I'm using:\n\n[20221205_model_human_sculting_pose_brush_using_facecets_0001.blend](20221205_model_human_sculting_pose_brush_using_facecets_0001.blend)\n", "Update 'dyntopo_detail_size_edit' to support Relative/Brush Detail settings\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\nAs of right now in sculpt mode the shortcut `R` is used while Dyntopo is enabled to change the detail size.\nIt calls the operator `SCULPT_OT_dyntopo_detail_size_edit` which displays a triangle overlay.\nIf `tool_settings.sculpt.detail_type_method` is not set to \"constant\" or \"manual\", it will fall back onto the older radial control `SCULPT_OT_set_detail_size` instead.\nThis operator is less ideal to control or display the target resolution.\n\n\n\nThe operator and overlays should be updated to work with either detail type method.\nThe methods \"Relative\" and \"Brush\" are screen based, instead of scene based, which doesn't strictly prevent the triangle overlay from displaying and estiamted resolution.\n\n", "Sculpt mode: annotation and unhide conflicts with Multiresolution modifier\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\n**Broken: version:**\n2.93.0 Alpha.\n3.0.0 Alpha\n\nUse of annotation tool unhides the hidden face\n\n**Steps to Reproduce the error**\n- Open .blend file\n- Hide the faces with Box Hide tool\n- Erase the word \"Erase\" with annotation tool (hidden part will appear)\n- Repeat step 2.\n- Draw a line with annotation tool. (Hidden part will reappear)\n\nTest File:\n[#87821.blend](T87821.blend)\n[Blender [C__Users_Pratik_Downloads_T87821.blend] 2021-07-12 09-55-06.mp4](Blender__C__Users_Pratik_Downloads_T87821.blend__2021-07-12_09-55-06.mp4)\n", "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", "After Remove Rigid Body World. The rigidbody setting will be lost.\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.3.1\nWorked: I don't know.\n\nAfter click the Remove Rigid Body World button. The object's rigidbody setting was lost.\nIts setting should be preserved, just like the rigidbody constraint setting.\n\n\n1. Create a cube.\n2. Enable rigidbody for the cube.\n3. Play 5 frame.\n4. Click the Remove Rigid Body World button.\n5. Recheck the cube's rigidbody setting. It can be found lost the rigidbody setting.\n", "Editing redo panel properties of torus in edit mode reverts some steps\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.24 355.11.10.50.10.103\n\nBroken: version: 3.4.1\nWorked: (never worked as expected)\n\nAdding and then adjusting a Torus or any Add Mesh add-on in edit mode reverts edits made to nodes, video sequencer, and more, since entering edit mode on the mesh object.\n\n1. Go to the Geometry Nodes workspace\n2. Select the default cube\n3. Click the New button to add the Geometry Nodes modifier and create and assign a new node group\n4. In the 3D Viewport switch to Edit mode\n5. In the Node Editor, pour your heart and soul into crafting an elaborate node tree (lol, jk 👀💔)\n6. In the 3D Viewport add a Torus\n7. Tweak any setting in the Adjust Last Operation panel\n8. Observe Geometry Nodes edits reverted (all edits since entering edit mode in the 3D Viewport)\n\nNo other built-in mesh primitives (nor even primatives!) have this effect, but the Add Mesh add-ons all do.\n\nI have checked some of the editors to see what data is reverted and what is preserved. This is not yet an exhaustive review.\nThe following data is reverted:\n- Video Sequencer\n- Properties\n- every Node editor\n- Timeline\n\nThe following data is preserved:\n- Preferences\n- Text Editor\n- Python Console\n- Movie Clip Editor\n- UV Editor\n\nThe Outliner has mixed results:\n- Hierarchy expansion reverts in Blender File, Data API, and Orphan Data but not in Scenes nor View Layer.\n\nSome editors have special behavior:\n- Image editor\n - Paint mode\n - {Add torus, paint image, tweak torus} reverts the paint\n - {Paint, add, tweak} kicks out of Edit mode into Object mode\n - Switching Image Editor modes does not close the ALO panel. The following sequence of steps produces a Python error:\n - Add torus\n - Switch Image Editor modes\n - Adjust torus\n (If this merits its own tracker issue, tell me and I will write one up. This all seems so tied to one root culprit that it is not my initial inclination to do so)\n\n", "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", "Brush Management: setting a brushes tool [vertex_tool, weight_tool, ...] may leave you with unaccesible tools (when no corresponding brush is left)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.83.2\n\nSee attached gif. Scene is the default scene without camera and light. Once I start switching tools in Weight Paint Mode through the different methods shown in the gif, I eventually reach a point where I lose access to some tools. Notice that even though the brush menus initially show the expected brush as the one currently selected, it isn't the one performing the painting (shown in the gif as the desync between \"Active Tool\" and the brush that appears as selected). As the gif also shows, the side menu doesn't select the expected brush either. \n\nAs a side question: why is the Smear brush named \"Smear.001\"? instead of just \"Smear\" like the other brushes?\n\nSee gif. \n\nThanks.\n\n\n\n\n", "Wireframes aren't displayed in Edit Mode when Overlays are off. \nBroken: 2.82a, 2.83, 2.90 alpha\nWorked: 2.81a\n\nWireframes aren't displayed in Edit Mode if Overlays are turned off, but they're only shown in object mode, or if there's a modifier with \"display in edit mode\" option. \n\nOpen default file.\nChange to wireframe mode.\nturn off overlays.\nchange to edit mode. Wireframe won't be shown.\n", "One of four edited hair systems won't simulate unless edit is deleted\nOperating system: Win10\nGraphics card: GTC 1060\n\nBroken: **2.92.0 master 2021-02-24 16:25 02948a2cab44** and **2.93.0, master 2021-06-02 11:21 84da05a8b806**\nWorked: Didn't find a working version\n\n4 particle systems, one (\"Back\") won't sim unless the edit is deleted. It stays in place and stretches towards the animated head cap.\n\n**Attempted things to fix it:**\nDelete all bakes and resim - failed\nChecked the weight painting - doesn't seem to be the source of the issue\nAppend into new files and resim - failed\nDisabled dynamics - now everything moves with the haircap, but obviously no sim\nRemoved hair edit - now it works but I loose the edit\n\nOpen the file and press space to run the sim and animation. I would not know how to make a sim from scratch which won't work though so I'm sending the file.[hair_bug.blend](hair_bug.blend)", "Hiding Armature in Outliner while in Pose Mode, leaves viewport without ability to select or exit the Pose Mode.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0\n\nWhen Armature is hidden via Outliner in Pose Mode, the selection, active object, and the Mode remains on that armature, not allowing to select anything anymore. Same happens with Meshes and Edit Mode, but one is still able to exit the Edit Mode. I assume it's likely that one either shouldn't be able to hide the object one is in Edit/Pose mode with, or the Mode probably should be exited upon hiding it's object. Or, at least, switching the Mode off shouldn't be disabled if the object is considered still active/selected.\n\n[armature.blend](armature.blend)\n - Select Bone,\n - Press Disable in Viewports for Armature object in Outliner,\n - > Can't select other objects in viewport now, or exit the pose mode.", "Sculpt: RCS keymap conflicts (Context menu blocked by Face Sets pie menu, angle control, smooth/lazy mouse, smooth brush)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nI found 3 keys which are simply blocked by others:\n[2021-01-25 14-35-28.mp4](2021-01-25_14-35-28.mp4)\n`Shift+S`: `Context Toggle` (toggle smooth/lazy mouse) >> `Brush Select` (Smooth Brush)\n`R`: `Angle Control` (VIEW3D_MT_angle_control) >> `Rotate` (from 3D View)\n`W`: `Context menu` >> `Face Sets pie menu`\n\nIn Sculpt mode, W uses a Pie Menu (`VIEW3D_MT_sculpt_face_sets_edit_pie`), which in addition to doing nothing in Dyntopo (#84973), does not provide alternative access to this menu.\n\n# {key R}: `Angle Control` (VIEW3D_MT_angle_control) vs `Rotate`\n - Go to sculpt mode\n - Press {key R} to call the \"Angle Control\" menu - Rotate will be performed\n - In the Sidebar, go to `Tool -> Brush Settings -> Texture` and change the `Mapping` to \"View Plane\"\n - Press {key R} - \"Angle Control\" menu is now called\n# {key Shift S}: `Context Toggle` (toggle smooth/lazy mouse) vs `Brush Select` (Smooth Brush)\n - Go to Sculpt mode\n - Press {key Shift S} to enable the \"Stabilize Stroke\" (`Tool -> Brush Settings -> Stroke`) - The Smooth brush will be selected instead.\n - Disable the \"Brush Select\" keyitem from the keymap\n - Press {key Shift S} in the 3D View again\n# {key W}: `Context menu` vs `Face Sets pie menu`\n - Go to Sculpt mode\n - Press {key W} - Pie menu will be called\n - Disable the \"Face Sets Edit\" keyitem from the keymap\n - Press {key W} in the 3D View again - Context menu will be called" ]

[ "Dyntopo keeps getting disabled\nWindows 10 x64\nGTX 950M\n\nBroken:\nDate: 02/03/2019\nHash: 2672552cf7a7\n\nWorked: (optional)\nDate: 2017-9-11\nHash: 5bc8ac9\nBranch: blender 2.79 (Official Release)\n\nEvery time you leave sculpt mode, dyntopo keeps getting disabled.\n\n\n\n1: Go to sculpt mode, enabled dyntopo and sculpt some\n2: Go to object mode\n3: Go back to sculpt mode\n4: Dyntopo is now disabled\n" ]

[ "Solid mode in EEVEE looks pixelated (NEW)/ CYCLES in GPU 3D AMD driver problem (OLD KNOWN Problem)\n**Xeon E3 1230 V2 - 16Gb RAM**\nOperating system: Windows 10\nGraphics card: AMD RX 570 8Gb VRAM\n\n**Blender Version 2.92.0**\n\n\nI opened an old work of mine that I was mading on same 2.92.0 before. Today when I opened the solid mode as default and appears very pixelated and like matrix effect, as AMD error was giving in Cycles before... \nMaybe is AMD driver problem or materials render data. \nSome months ago was Cycles incompatibility. Cycles is still working only on CPU and now Eevee have problems in solid mode. \nI've tested in 2.83.5 version and worked. \n\n\nattached photos. In 2.92.0 isn't \n\n**Work in a project\nfews days later (about 20 days) open the archive and solid mode was pixelated  \n\n[estilizada unir cabeca retopo.blend](estilizada_unir_cabeca_retopo.blend)\nBased on the default startup or an attached .blend file (as simple as possible).", "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", "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", "Inconsistent color space baking to float and byte images\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.14742 Core Profile Context 21.8.2 27.20.22025.1006\n\nBroken: version: 2.93.6\nWorked: ---\n\nIn blender we can create an image with 32 bit resolution (See image):\n\n\nThe new 32bit image can be used for baking in order to obtain a normal map.\nThis map works perfectly until saved in PNG (16bit or 8bit).\nInterestingly you can bake directly on a 16bit image and the resulting image works even if it is saved in 8bit.\n\nHere is a file where I put different pixel resolution combinations on textures saved in PNG:\n[TesteNormal.blend](TesteNormal.blend)\n\n\n\n1 - Bake a normal map image with 32 bit option enabled. (see the pic \"sample3.jpg\")\n```\n A simple cube can be used, no need to add any detail.\n```\n2 - Save the image as PNG in 8 bit or 16 bit.\n3 - Create a material and connect the saved baked normal map image to the normal map node. \n```\n Change color space option to \"non-color\" \n```\n4 - Observe the object becomes dark in rendered mode in Eevee or Cycles. \n\n[Teste_Normal_Textures.blend](Teste_Normal_Textures.blend)\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", "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)", "Render errors [glitchy frames] with baked cloth [from the UI, commandline as well as rendering with 'Lock Interface' is OK]\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77\n\nBroken: version: 2.91.0 Alpha, branch: master, commit date: 2020-10-07 21:43, hash: d8fcd8a316\n\n\nI have a simple scene I press render animation and some of the frames come out messed up. \nIt looks like some sort of motion blur bug. Looks similar to this bug #74457 (Mantaflow foam particles as objects break motion blur)\nI have rendered this on two different PC's, the problem is the same.\nWith baked cloth physics.\n\n\n\n[Jelly Jery (buggy render) - Cycles 256 samples Intel denoised.mov](Jelly_Jery__buggy_render__-_Cycles_256_samples_Intel_denoised.mov)\n\n\n[Jelly Jery.blend](Jelly_Jery.blend)\n\n\n\n\n | cycles | glitchy |\n | -- | -- |\n | cycles command line render | OK |\n | cycles with Lock Interface | OK |\n | eevee | glitchy |\n | eevee without motion blur | glitchy |", "Grid doesnt show\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", "UI: Show invalid cache as stripped lines\nAt the moment we use a faded color to indicate that a cache is invalid. The difference is a too subtle at times, even when users customize their theme colors.\n\nThe proposal here is to draw the invalid caches with a darker stripped diagonal line (see image). In this case I used the original color with a 50% value.\n\nIn this mockup you see the Simulation cache (pink) as invalid, and the Cloth cache (blue) as valid.\n\n\n\n_Design done with [Pablo Vazquez](pablovazquez)._", "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", "Simulation Nodes: bake UI in simulation node\n_No response_\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", "Alpha hashed material produces shifting artifacts when animated in EEVEE\nWhen an object with material that has alpha hashed transparency is animated in EEVEE, the noise pattern may look either unstable or shifting as shown below: \n[alpha-hashed-transparency-problem.mp4](alpha-hashed-transparency-problem.mp4)\n\n\n\nYou can observe that the artifacts on top staying in place rather than rotating with the cube while those on the sides keep flickering, thus producing shifting and unstable appearance.\n\nThe symptom is also noticeable when changing the camera position in rendered viewport mode in Blender. And it's particularly problematic in UPBGE (a fork of the old BGE based on the latest Blender source) because a game engine must animate objects in realtime with relatively small number of samples per frame.\n\nUpon an examination from the developers of UPBGE, it is found that the problem is due to the fact that the current implementation of alpha hashed transparency uses the world coordinate instead of the object space, as it is often recommended (e.g. [2017 ACM SIGGRAPH Symposium on Interactive 3D Graphics and Games](p4TYf5DDpbQ)).\n\nIt appears that a simple change from the world to object coordinate fixes the problem as shown in this [test commit (see line 80) ](e0a8638d0b255f2fc6ce778d10dd0d12a467b4d3#diff-2b8bf4f9e10009510d02c14e3659ee032c73f829de5453d6abcdf6a3f884fdfdR80), which produces the following result:\n[alpha-hashed-problem-solved.mp4](alpha-hashed-problem-solved.mp4)\n\nIt's my understanding that the [original author ]() decided to use the world matrix to avoid the difficulties with certain corner cases, like when the object is scaled by an extreme factor. However, while such a problem may be circumvented relatively easily (e.g. discard the scale information from the matrix) such a problem described above may pose more substantial issues with making an animation or rendering in realtime.\n\nSo, I hope this problem and the suggested fix may be evaluated again since we have more people interested in using Blender for such purposes now, thanks to the gaining popularity of EEVEE.", "Cycles and Eevee Significant Difference in Texture Output\nOperating system: Ubuntu 20.04\nGraphics card: GTX 1060 3Gb\n\nBroken: 2.80 and on (3.0.0 is still affected)\nWorked: 2.79\n\nFrom Blender 2.80, Cycles produces incorrect output for some procedural textures, while Eevee produces correct ones.\n{[F12696991](Cycles.png)}\n\nTest file (I assume there might be other files affected too). [Carbon_90.blend](Carbon_90.blend)", "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." ]

[ "Selected to Active Cycles Baking no longer working\nOSX 10.9.5\n\nBroken: master (d39e188)\nWorked: 2.75a\n\nBaking returns a black image when using \"Selected to Active\" (it works fine otherwise).\n\nCompare either file below between master and 2.75a. They all bake the diffuse color for simplicity sake.\n\nSelected to Active (not working):\n* Color: [cycles_bake_color.blend](cycles_bake_color.blend)\n* Texture:[cycles_bake_texture.blend](cycles_bake_texture.blend)\n\nSingle object (working):\n* [cycles_bake_single_object.blend](cycles_bake_single_object.blend)\n\n" ]

[ "Blender keeps crashing relocating linked library [3.5.1]\nOperating system: Windows-10-10.0.25357-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\nRelocating linked library file results in instant crash when different file is chosen. I need this because i work on both OSX and Windows. While testing file version, i had issue with indirectly linked files. These are nested files so to say. They are linked blend files inside another linked blend file. \n\n- Download and Unzip attached `RML-test file-bl350.zip` file\n- open file \"RML-test file-bl350.blend\"\n- go to `Outliner` > `Blender File` and select the linked lib file with exclamation mark \"linked object\"\n- Right click and select \"Relocate\"\n- Point to the file \"linked object-bl293\"\n\nBlender file browser closes and crashes short after.\n\nSide note\nThe linked lib blend file is name \"linked object\", if i rename the \"linked object-bl293\" to \"linked object\" it works. But because i work on both OSX and Windows and sometimes also with different version. I need to rename linked files so i dont break anything.\n\nHowever, i jsut tested these 2 files in an issue folder i created and then it links just fine. When these files are linked in the original folder, blender crashes right after i pick that file \"linked object-bl293.blend\". See attached screengrab.\n\n\n", "AMD: Rendering Instances On Points using a Collection crashes Blender on Linux\nBroken\nOperating system: Linux-6.2.0-060200-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 580 Series (polaris10, LLVM 15.0.7, DRM 3.49, 6.2.0-060200-generic) AMD 4.6 (Core Profile) Mesa 23.1.0\nversion: 3.5.1\n\nBroken\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\nversion: 3.5.1\n\nFine (same system as above, but using nvidia)\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\nversion: 3.5.1\n\n\nOn Linux, using Geometry Nodes to have a Collection Info node feed instances of like items to an Instance on Points node going to Group Output will work properly, but will crash Blender when Rendering.\n\nDoing the obligatory Donut Tutorial. When creating the sprinkles using the Collection Info node to feed Instance on Points will create a nice set of sprinkles. The sprinkles share a Linked Material to randomize colors. Using Render Preview in the Layout (or Shading) tab correctly displays randomly colored sprinkles. However, actually rendering crashes Blender. Using the Realize Instances geometry node before the Output node will allow it to render, but then every sprinkle has a single, random color.\n\nReproduce (using Linux): \n1. Using the attached file, render using the Realize Instances node on the Icing's Geometry Nodes (file's current setup). Blender will not crash, but all sprinkles have same color. \n2. Remove the Realize Instances geometry node, and the sprinkle colors will be properly randomized. Render, and blender will crash.\n\nWarning: This is a hard system freeze, not a simple Blender crash. Typically requires a system reset to recover.\nUpdate: AMD graphic cards only. Eevee rendering only.", "Crash undoing in certain scenario (disabling Global Undo)\nOperating system: Linux-5.10.12-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.82a\n\nCrash undoing in certain scenario (disabling Global Undo)\n\nFrom the default startup file (order of operations is important here):\n- move the cube (could be any objectmode operator) {key G Z 3}\n- disable `Global Undo` in Preferences {key F4} > `Preferences` > `System` > uncheck `Global Undo`\n- add an armature {key Shift A} > `Armature`\n- go to pose mode\n- select bone\n- move bone\n- Undo {key Ctrl Z}\n - > crash\n\n```\n1 BKE_scene_object_base_flag_sync_from_base scene.c 2914 0x35b41a9 \n2 BKE_scene_set_background scene.c 2125 0x35b2957 \n3 setup_app_data blendfile.c 386 0x4b63950 \n4 setup_app_blend_file_data blendfile.c 416 0x4b639e4 \n5 BKE_blendfile_read_from_memfile blendfile.c 524 0x4b63e38 \n6 BKE_memfile_undo_decode blender_undo.c 88 0x4b62cc0 \n7 memfile_undosys_step_decode memfile_undo.c 193 0x486eb47 \n8 undosys_step_decode undo_system.c 214 0x4bb97ec \n9 BKE_undosys_step_load_data_ex undo_system.c 809 0x4bbb2df \n10 BKE_undosys_step_undo_with_data_ex undo_system.c 870 0x4bbb4a4 \n11 BKE_undosys_step_undo_with_data undo_system.c 880 0x4bbb4d3 \n12 BKE_undosys_step_undo undo_system.c 889 0x4bbb511 \n13 ed_undo_step_direction ed_undo.c 278 0x486c907 \n14 ed_undo_exec ed_undo.c 489 0x486d214 \n15 wm_operator_invoke wm_event_system.c 1332 0x3a17b06 \n16 wm_handler_operator_call wm_event_system.c 2161 0x3a198e3 \n17 wm_handlers_do_keymap_with_keymap_handler wm_event_system.c 2486 0x3a1a617 \n18 wm_handlers_do_intern wm_event_system.c 2782 0x3a1b591 \n19 wm_handlers_do wm_event_system.c 2914 0x3a1bafc \n20 wm_event_do_handlers wm_event_system.c 3445 0x3a1d2a3 \n```\n```\n \n```\n\n\n", "Blender 3.6 problem by rendering scene on EEEVEE (Freeze and crash GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9)\nOperating system: Windows 11 Home\nGraphics card: Radeon Graphics\n\nBroken: (example: 3.6, as found on the splash screen)\n\n\nBlender 3.6 doesn't render the scene as blender demo file in EEVEE\nOpen Blender splash fox of blender 2.90\nRender the scene\nFreeze and crash of blender when rendering on EEVEE\n\n", "EEVEE 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", "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.", "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", "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", "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", "MacOS ARM64 builds have issues saving WEBP images from 32bpp buffers\nOperating system: MacOS ARM64 buildbot\n\nBroken: 3.6 main 7699c7407d08e79580c36554206f14310f0f56c9\nWorked: n/a\n\nThe newly added `imbuf_save` is failing for certain scenarios but only on MacOS ARM64 builds.\n\nThis is a tracking bug so we can investigate the issue and re-enable the tests.\n\n- Uncomment the 2 WebP tests in `tests/python/bl_imbuf_save.py`\n- Run and observe large deviations in expected pixel values:\n\nThe first failure seems entirely incorrect while the second exceeds our 1% failure threshold @ 0.016.\n\n```\nwebp-rgb-70__from__rgba32.webp\n Mean error = 0.0058668\n RMS error = 0.01072\n Peak SNR = 39.3961\n Max error = 0.0862745 @ (77, 45, G) values are 0.04705883, 0.043137256, 0.0627451 vs 0.13333334, 0.12941177, 0.14901961\n 9791 pixels (59.8%) over 1e-06\n 2354 pixels (14.4%) over 0.016\n\n\nwebp-rgba-70__from__rgba32.webp\n Mean error = 0.00128407\n RMS error = 0.00366359\n Peak SNR = 48.7219\n Max error = 0.054902 @ (112, 62, R) values are 0.5058824, 0.25882354, 0.50980395, 1 vs 0.56078434, 0.3137255, 0.5647059, 1\n 5139 pixels (31.4%) over 1e-06\n 312 pixels (1.9%) over 0.016\nFAILURE\n```\n\n", "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "Point Cloud - Missing Particles when Rendering with Cuda on Linux\nOperating system: Linux-5.13.0-35-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.1.0\n\nWhen rendering large amounts of particles with CUDA on Linux, there appear to be some random patches of particles missing. This does not occur when using the OptiX rendering backend or CPU rendering backend. This problem **does not** occur on Windows for any rendering backend, i.e. the same render has been confirmed to work on Windows with the CUDA backend.\n\n1. Open the attached .blend file.\n2. Render with Cycles and CUDA backend on linux. *Note: It might be necessary to render the same scene multiple times if the error does not occur on the first render, or to switch the render device back and forth.*\n3. See the attached image for an example screenshot of the problem\n\n(alternative)\n1. \n - create a plane object and create 1000 edge loops in x and y direction so that the object has roughly 1 million vertices.\n - add \"Mesh to Points\" geometry node with radius 0.001\n2. Render with Cycles and CUDA backend on linux. *Note: It might be necessary to render the same scene multiple times if the error does not occur on the first render, or to switch the render device back and forth.*\n3. See the attached image for an example screenshot of the problem\n\n.blend File:\n[particles_problem.blend](particles_problem.blend)\n\nImage of the Problem:\n", "Crash while using several rigid bodies and some force fields.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe scene is pretty simple, a house with some elements used as rigid bodies and some force field, vortex and wind force are applied.\n\nWhen I play the animation, it starts and around frame 140-200 it crashes.\n\nAttached blend file. The only thing to do is to play the animation and wait for the crash.\nAttached crash report.[Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash](Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash)\n\n[casaFalla.blend](casaFalla.blend)\n\n", "Crash after linked object is edited then switched to another scene (object origin scene)\nOperating system: Window10\nGraphics card:\n\n\nBroken: 2.90.1 ( hash: 3e85bb34d0d7 )\nWorked: unknown\n\n\nBlender simply crash and close the window directly after editing the \"linked\" object from 2nd screen and switched back to 1st screen.\n\n\n\nThis error can be reproduced with 2 scenes setup.\n\n- First scene contains a simple mesh object. Let's say a \"Cube\" object\n- Create a second scene.\n- In the first scene, select the \"Cube\" object then \"Make Links\" {key Ctrl L} to 2nd scene.\n- Now, we switch to 2nd scene. The 2nd scene now should contains the same \"linked\" Cube object from 1st scene.\n- Okay, this is important step. In this 2nd scene, we select this \"linked\" Cube object and set the Relations to: *Object > Relations > Make Single User > Object*\n- After that, we go to \"Edit Mode\" for this \"linked\" Cube object.\n- In \"Edit mode\", make a simple change to this \"linked\" Cube object.\n- Once simple change is done, don't do anything else. You just directly switch back to \"First scene\". CRASH here.\n\n", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n" ]

[ "LibFree() crashes Blender\nWindows 7 64 bit, Nvidia GeForce GT540M Cuda\n\nBroken: 2.50 up to current: 2.70a\n\nBlender crashes when freeing libraries: [bge.logic.LibFree(l) for l in bge.logic.LibList()]. It occurs sporadically. Possibly related to materials.\n\nPress 'P' to start the game. A number of objects will be spawned and their meshes will be replaced by new ones (LibNew()). Press 'Spacebar' to free all libraries. For testing purposes on every logic tic only one library will be freed. After some are freed Blender crashes.\n\nNow reopen the blend and remove the material slot on the Icosphere and follow the same steps. This time Blender doesn't crash. Note that removing the material slot won't prevent a crash with some builds after 2.70a, for example Hash c08c931.\n\n[LibFree_crash_bug.blend](LibFree_crash_bug.blend)" ]

[ "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", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "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!", "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 just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "Not recognizing numpad page up /down keys .\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nBlender is failing to recognize the numpad keys !!!\n\nTrying to use the change workspace shortcut ctrl+PageUp /down and blender is not recognizing the keys in numpad and keep assuming the key 9 and 3 . Other software is fine and i can use Page up and Down, and the home end keys. \n\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", "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", "Reliable GPU hang on common Intel cards (Linux)\nOperating system: Linux Fedora 32\nGraphics card: UHD Graphics 620 (rev 07) Intel\n\nBroken: 2.80.x, 2.90.0-x\n\n\n\nBlender crashes the computer, freezing, dmesg command shows a GPU Hang error.\n\n\nOnly with Intel GPU (Intel Corporation UHD Graphics 620 (rev 07) here)\n\nOpen the given blend file [F8892221](gpuhangtest.blend) (Thanks @HDMaster84 ) and activate lookdev or render view - the graphic server hangs.\n\nI followed the dmesg output that says to create an issue on freedesktop gitlab: 2422 (you can see my dmesg and gpu error) - anyway, thos problem only happens with Blender.\n\nThe problem started from 2.80 if I'm not wrong, not with others earlier versions.\n\n", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n", "Blender Crashes on Render (Save As), then refuses to start\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1\nWorked: N/A\n\nFirst observed with the attached file. I tried to save a png image render from it; when I clicked \"Save As,\" Blender crashed and then... wouldn't open. It seemed to initiate startup, because the little black window that usually notified me that it was reading my userprefs.py file would blink into existence just long enough for me to register what it said, then close itself and act like I hadn't clicked it.\n\nRestarting my computer fixes the problem temporarily, until the next crash. The crashes are inconsistent, but seem to happen only when I hit main menu items like Open or Save. This includes previous versions, apparently, as I still had 3.5 installed and it does the same quick blink.\n\nThe only thing I could think of was that that Read line in the black window referred to finding the userprefs file in C:\\ when I installed everything into M:\\, but I tried copying the required path over to C:\\ with no effect and also it gives me that same message when it's working and starts up fine.\n\nI also tried repairing the 3.6.1 install, and uninstalling/reinstalling, to no effect.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Blender 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", "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", "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)", "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)" ]

[ "The blender does not start on windows; console quickly opens and closes.\n\nIntel(R) Core(TM) i5-7200U CPU @\n2.50GHGz 2.70GHz\n8g\nIntel(R) HD Graphics 620\n\nBroken: Blender 2.81\nWorking: no version works\n\nThe blender does not start. The command line opens quickly and closes immediately.\n\n```\n AL lib: <EE> UpdateDevieParams: Failed to set 48000hz, got 44100hz instead.\n```\nIt produces similar errors\n\nSet different versions of the blender. 2.69 and earlier versions, new versions and now I have the latest version installed. I have no version of the blender that works.\n\nI tried to fix them, but to no avail. Launched on behalf of the administrator, solved the compatibility problem. Nothing works.\nI wanted to run blender.exe --debug-all, I don’t have it at all. Drivers are fine. I recently fixed a laptop about drivers.\n\nI opened the blender_debug_gpu.cmd file [blender_debug_output.txt](blender_debug_output.txt)" ]

[ "Animation: Extra operators for the graph editor's sliders\nThis is a list of operators being added to the sliders tool in the Graph Editor. \n\nIt is based on the structure already created by @ChrisLend. The main work is in `keyframes_general.c`, the rest is just following what he did.\n\nThere is one slider missing: Wave-Noise. I will add it to the list once I add the PR\n\n- [x] Blend to Infiniti: [#106517](106517)\n- [x] Blend Offset: [#106518](106518)\n- [x] Blend to Ease: [106519](106519)\n- [x] Time Offset: [#106520](106520)\n- [x] Shear Left: [#106521](106521)\n- [x] Shear Right: [#106522](106522)\n- [ ] Scale Right: [#106523](106523)\n- [ ] Scale Left: [#106524](106524)\n- [ ] Ease-Ease: [#106525](106525)\n- [x] Scale Average: [#106526](106526)\n- [x] Push Pull: [#106527](106527)\n- [ ] Blend to Frame: [#106754](106754)\n", "Copy Datablock button has different behaviour in Graph as Modifier\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.3.0\n\nThe button to duplicate the current node tree works as such in the node graph but on the modifier, it creates a new node tree.\nIn other areas of Blender (eg materials) the same button duplicates current datablock.\n\n\n\nAdd a new geometry node tree\nAdd a node\nClick the Copy Node group button in graph and see graph is duplicated\nClick the Copy Node group button in modifier and see graph is replaced\n[2022-09-15 11-14-53.mp4](2022-09-15_11-14-53.mp4)\n", "Redesign Graph editor Header and Menus to 2.80 Blender UI standards\nThe current graph editor menus have slowly evolved and not been evaluated carefully. As a result, the header menus are a bit of a mess:\n\nHere some options are really hard to parse and arranged oddly (for intance, Show Handles and Show \"Only Selected Keyframe Handles\" are related, but seperated from each other, and it is really hard to parse what they do, some options like \"AutoMerge Keyframes\" don't belong at all in View.\nThis design task is to work towards making the header area in the graph editor match blender design, so that options are found in an expected place, similar to e.g. the 3D View header which has received more attention:\n\n\n - Reorganize the header so that similar items are in similar places, e.g. pivot and snapping options should be centered\n - Add an overlay menu and organize some of the clutter in the view menu so it makes more sense, and fits a (Blender) users expectations of where things should be\n - Reorganize all the menus if needed, and move items that don't belong (e.g. the aforementioned AutoMerge Keyframes) to a logical place\n - Potentially upgrade the editor to use the tool system and have two lines in the header for options, etc.\n\n", "Broken curve drawing in normalized view in graph editor\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.1\nWorked: ?\n\nin the normalized mapping in the graph editor, the curve behaves strangely. In the normal display, everything is fine\n[2022-04-20 22-13-05.mp4](2022-04-20_22-13-05.mp4)\n\n- Open attached .blend file\n- In graphics editor pan view up and down\nDisable Normalized to hide the problem\n[bandit_anim.blend](bandit_anim.blend)", "Inconsistent Grease Pencil auto-keying behavior\nOperating system: Linux 64-bit\nGraphics card: GTX 1080\n\n3.1 and prior\n\nWhen auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe. \n\nAlso, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.\n[GP_autokey_bug.blend](GP_autokey_bug.blend)\n - Open the attached file.\n - Grab (G) a stroke, then right-click to cancel moving it. The keyframe was inserted, even though no change was made.\n # Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!\n\n", "Action editor key frames not displaying sometimes\nSometimes when working with multiply animations and switching through them in the action editor. The Keyframes stop displaying for certain action. \nWhen the Panel with the action editor View is removed and added again, the displaying is working again.\nThis bug was seen in Version 2.76 and daily Build from 10/30/2015.\n\nError:\n\nFixed after closing and opening action editor view\n\n\nMy Project without Mesh. Bug is seen in walk_back_cycle action.\n[animation_editor_error_project.blend](animation_editor_error_project.blend)\n\nThis bug is very annoying in my workflow.\n\nGreetings and thank you for your work!", "Regression: Mouse cursor jumps to the left when keep clicking on the colour circle under Windows\nOperating system: Windows 10, 21H2\nGraphics card: Intel A770\n\nBroken: 3.4, 3.6.0\nWorked: 3.3\n\nIf I keep clicking random place in the colour circle, the mouse pointer randomly jumps to the left edge of the circle. This seems to be happening only under Windows, not under Linux. \nI have only one Windows installation, so I am not sure if this would happen on other computers. Please check for it.\n\n- Just keep clicking random places on the color circle for about 10 seconds. (See the attached screen recording.)\n\nNot necessary: ~~I was using a 4K monitor with 200% scaling and Blender interface scaling was 1.0.~~", "Keyframed parameters are not preserved when frame_change_post handler is used\nOperating system: Win 10 Pro\nGraphics card: GTX 1080\n\nBroken: v2.81, master, 2018-11-26\nWorked: (optional)\n\n---\n\n\n**EDIT** by @EAW \n\n\n> In the .blend file setup, the 'mesh_cache' object would instance a cube over the vertices for display in rendering. An ocean modifier is added to the object with 'Geometry' set to Displace and the 'time' parameter is keyframed over a frame range. \n> \n> Playback in the viewport shows the ocean modifier evolving shape during the animation. If the animation is rendered, the ocean modifier does not evolve over time and the render result is static.\n> \n\n\n\n> Here is a script that generates a 2d grid of vertices in the frame_change_post handler:\n> \n> ```\n> import bpy\n> \n> def frame_change_post(scene, depsgraph):\n> # Generate a 2d grid of vertices. A cube object is set to be instanced over the vertices for rendering\n> vertices = []\n> for j in range(100):\n> for i in range(100):\n> vertices.append((i * 0.05, j * 0.05, 0.0))\n> \n> mesh_cache_object = bpy.data.objects.get(\"mesh_cache\")\n> mesh_cache_object.data.clear_geometry()\n> mesh_cache_object.data.from_pydata(vertices, [], [])\n> \n> depsgraph.update()\n> \n> \n> bpy.app.handlers.frame_change_post.append(frame_change_post)\n> ```\n> \n\n\n\n\n> Here is the .blend file including the script: [keyframed_modifier_bug.blend](keyframed_modifier_bug.blend)\n> \n> How to reproduce:\n> 1. Open .blend file\n> 2. Press 'Run Script'\n> 3. Blender > Render > Render Animation\n> \n> The result is a static animation.\n\n\n**End Edit**\n\n---\n\n\n\nI have created a FlipFluids simulation in Blender 2.81 ( 2019-11-25 21:45) and added an Ocean modifier in displacement mode to the fluid_surface. Then I have baked the complete sim from within FlipFluids.\nWhen I move from keyframe to keyframe in the default timeline everything is moving as desired in the default 3D window:\nOcean modifier waves, FlipFluids waves & wake, flags, radars...\n\nWhen I render the complete animation everything EXCEPT the ocean modifier waves are moving. The ocean modifier waves remain static but the FLIPFLUIDS waves move on that surface.\nALL modifiers and elements ARE enabled for renderings. D-NOISE: AI Denoiser is on (switching denoiser off did not help).\nComputer is a HP Z800 with dual Xeons, 72 GB of vRAM and a GTX 1060.\n\nIf I render & save the keyframes manually individually by hand the ocean surface moves! Which means I get the proper result.\n\nAs its working when rendering&saving each frame manually as image (Png) and its not giving the same result when saving out the same images (Png) when I hit render animation, I do suppose this might be a bug in 2.81.\nRunning indiviual frames via Renderpilot did not yield the proper result either. So I do suspect it might be that there is not enough time gap between saving the last frame and rendering the next. Or, something does not get purged properly.\n\nFor propriatary reasons I can not share the blend file.", "Proportional editing lag\nWin7 x64, GTX 460\n\nBroken: 2.73, 2.74\nWorked: 2.63 \n\nWith proportional editing on, I get a few seconds freeze when activate translating (G); than after freeze, \neverything goes ok. I thought that the problem was a large mesh, but 2.63 works great and without lags in the same file. \n\nMy \"bugged\" file is the one, I am working with. If it is possible, can i sent it in private and not give it to the world here?\n\nThank you!", "GPencil: Shortcuts in Draw Mode are hardcoded\nMultiple keys in the `gpencil_draw_modal` function are hardcoded and (some) don't show up in the info bar. This makes it impossible for the user to know what certain keys do as well as impossible to change them in the keymap. All of those keys should be in the keymap with the default keys set as they are now.\n\nHere is a list of these (hardcoded) shortcuts:\n\n - {key Enter}, {key Pad_Enter}, {key Esc}, {key Space}, {key Ctrl Z} (?): Confirm\n - {key Mousewheel_Up}, {key Pad_Plus}: Increase size of eraser\n - {key Mousewheel_Down}, {key Pad_Minus}: Decrease size of eraser\n - {key O}: Set center of guide\n - {key V}: Turn off speed guide\n - {key M}: Alternate or flip guide direction\n - {key L}: Turn on line guide; {key Ctrl L}: Turn on line guide with angle = 0; {key Alt L}: Turn on line guide with last angle\n - {key C}: Turn on circular guide\n - {key K}: Turn line guide clockwise\n - {key J}: Turn line guide anti-clockwise\n", "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.", "Wrong editor type saved in workspace\nOperating system: Win11\nGraphics card: AMD Radeon (TM) Graphics (Included Graphics)\n\nBroken: 3.5.1\nWorked: N/A.\n\nMy properties editor is glitched and keeps resetting to nonlinear animation editor.\n(When saving file and reopening)\n\nIdk how to repreduce it, but here are steps for my blender file:\n1. Switch editor type to properties editor.\n2. Save file.\n3. Close blender .\n4. Open the saved file.\n5. Properties editor switched to nonlinear animation editor.\n6. (When repeating 1-4 with all objects deleted, then its working normally without the switch at restart).\n7. Viedeo: EDgFd6MIzjM.\n\n", "NLA strip's Influence initial keyframe sets to 0\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.36\n\nBroken: version: 2.93.0 Beta\nWorked: Never (2.80+)\n\nInfluence value is resetting to 0 when adding the initial keyframe to the NLA strip's influence channels. This problem gets worse when adding also keyframes to an active action at the same time. The values of the edited action are changed as well according to the new 0 value of the strip's influence. You can see how the action values change in the sample file's graph editor when adding a keyframe to all channels in the timeline editor.\nThis problem happens only when keyframing the influence channels in the dopesheet and timeline editor, but the Influence property in general has some more issues, also with updating.\n\n[#89339.blend](T89339.blend)\nAdd a keyframe in \"**All channels**\" in the Timeline editor or a Dopesheet editor on frame 15. \nThe influence of the NLA strip sets automatically to 0, even if it had a value of 1.\n\n\n", "Keyframes and drivers on custom nodes properties seem not working\nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 540 Intel Inc. 4.1 INTEL-12.4.7\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI'm not able to animate the properties of custom nodes. Keyframes do not work properly: when I set one all the others seem to disappear and only the last value set as a keyframe is shown on every time step.\n\n1. Go to the text editor, import the 'Custom Nodes' template and run the script.\n2. Open the 'Custom Node Tree' area.\n3. Add a 'Custom Node', in the 'Some Nodes' category.\n4. Add a keyframe for 'my_float_prop' on frame 1.\n5. Change the frame, change 'my_float_prop' value and set a keyframe.\n6. Now I should see (at least it was like this in the last version) the property changing while scrolling through the timeline between the two keyframes I just set, but I don't. The property keeps the last value.\n", "Dope Sheet: Keyframe Type Colors and Shape Improvements\nAfter the spring production the animation team at the blender institute had a meeting, to come up with the issues we had during the production and sharing them with the developers.\n\nOne of the issues we had, was that the \"Set Keyframe Type\", which changes the color of the keyframes, was really hard to see due to non saturated colors + size changes. When keyframes are dense, the keyframe type becomes almost impossible to see. We agreed that this feature was really useful for organizing the keyframes of a shot, but it needed improvements.\n\n### Current behaviour:\n\n{[F7785806](Set_Keyframe_Type_Visibility_UnSelected_Original_Comparison__copy_1_.png), height=55}\n\n - The size of the keyframe changes, 3 of the 5 options make the icons smaller, making them harder to find\n - The colors are not bright enough.\n - Colors of Selected/Unselected are too similar.\n\n{[F7785842](Set_Keyframe_type.mov), loop, autoplay, layout=left, float}\n\n\n- Keyframe colors become almost impossible to see when there are more keyframes nearby.\n\n---------------------------\n\nSo we came up with a proposal with three main points in mind:\n\n- The user is the one deciding the color/shape\n- Clear colors\n- Clear Shapes (so they are easy to see even for color blind people, as some of them might not be able to differentiate the colors)\n\n### Animation team proposal:\n\n{[F7785822](Set_Keyframe_Type_Visibility_UnSelected_Mock_Up_Comparison2__copy_1_.png), height=50}\n\nThis visualizing way could also propagate to the graph editor, which connects with [D5621](D5621) :\n\n{[F7785827](Graph_Editor_Key_Visibility_Blue_Selected__copy_1_.png), height=250}\n\n\n ---------------------------\n\nBut this proposal fundamentally conflicts with the new way of visualizing the handle type in the dopesheet, as that one changes the keyframe shape as well.\n\n## Current handle type icons\n\n{[F7785830](handletype-current.png), height=50}\n\nFor the animators at the studio showing the handle type in the dope sheet is not really useful, so we keep the option off, but we understand that there are other users that will find these really useful.\n\nI think it's important to understand how we use the dopesheet: \n\n- Since generally every bone has 9 different channels, and we are dealing with a lot of bones in a rig, we keep the channels collapsed in the dope sheet, using the summary or the top channel to make changes, if we want more precise control we'll jump into the Graph Editor.\n\nThe main issues we have with the handle type visualization and the interpolation type visualization are:\n\n### Spring shot file example\n\n{[F7785832](springshotexample.png), height=80}\n\n- When you have a lot of keyframes together the shape difference is so small it becomes really hard to see, becoming more confusing than helpful.\n \n### Open - Collapsed example:\n\n{[F7785835](coolapse-open.png), height=250}\n\n\nWhen the channels are collapsed, the information shown is not reliable. In the example used above, each one of the channels have different handle types and different interpolations. When collapsed there is no single type to be shown, creating misinformation. \n\n---------------------------\n\n## Conclusion:\n\nKeyframe colors are important. We propose an improvement by:\n\n - Clarifying keyframe-type colors and shapes in the dopesheet\n - Suggesting this would be useful in the graph editor too ([D5621](D5621))\n - Offer a switch between handle-type shape and keyframe-type shape (instead of the on/off switch for handle-type shape).\n```\n\n```\n*I’m not not a designer, so this is not final or beautiful design just a proposal to visualize my points. \n" ]

[ "Incorrect behaviour when editing aligned handles in curve editor\nWindows 7 Professional 64-bit w Service Pack 1\nDisplay card: Nvidia GeForce GTX 760\n\nBlender 2.69 - r60995\n\n\n\nThere is a bug editing aligned handles of an animation curve.\n\nSee attached file: “handle editing bug.blend”\n\nTo reproduce:\n\nIn the curve editor, select the right hand handle of the middle keyframe as in first image, “handle edit A.jpg”.\n\nNow move press 'G' and move the handle to the position as indicated in the second image file, “handle edit B.jpg”\n\nIt will be seen that the behaviour of the handle on the opposite side of the keyframe anchor point is not moving correctly. It is as if the control point of the second handle wants to remain vertically locked to the frame it is on. This behviour is not correct and often leads to a wild overshoot of the bezier curve.\n\nThe correct behaviour of the handle on the opposite side when being edited is indicated in the last image, “handle edit C.jpg”. Here we see that the handle on the opposite side remains the same length (thus retaining the same 'tension') and simply rotates around the keyframe anchor point.\n\n\n[handle_editing_bug.blend](handle_editing_bug.blend)\n\n\n\n\n\n" ]

[ "Quad View Exiting Behavior\nUsers coming from other software expect Quad View to behave a certain way. Since d71db08f6d, when exiting Quad View we always toggle to the *User Perspective* (top right) view, rather than the one the mouse currently hovers. That differs from what users probably expect (see #43523, #42462, #42368, #43452, #69717).\nIt should not be hard to get the (presumably) expected behavior to work again while addressing the reasons it was removed.\n\nQuick proposal:\n* Maximize the hovered view when exiting Quad View\n* Keep rotation of that view locked if it wasn't the *User Perspective* one\n* Keep the view transform of the *User Perspective* stored so when going back to Quad View, it shows that in the top right.\n\nFor more details, see d71db08f6d.", "Ability to cancel viewport operations (rotate/pan/zoom)\nSince most transforming view-port operations can be cancelled, it would be useful if viewport operations such as rotate/pan/zoom could be cancelled by pressing Escape. [See request ](showthread.php?392619-Call-for-Quick-Hack-ideas-(for-beginner-students-to-complate-in-a-day)&p=3010312&viewfull=1#post3010312).\n\nWhile not high priority, this is nice to support for consistency with other parts of Blender.", "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", "3D cursor doesn't precisely follow mouse pointer when Transform Pivot Point is Active Element\nOperating system: Fedora Linux (Wayland)\nGraphics card: AMD\n\nBroken: at least from 2.93 to 4.0 all broken\nWorked: never?\n\nWhen moving the 3D cursor, it's moved distance is multiplied by some value depending on the view orientation. \n\n\n- Move the default cube and rotate the viewport orientation\n- Select Active Element as the Transform Pivot Point\n- Move the 3D-Cursor with shift+RMB\n\n", "Viewport 3d is not updated with VSE driver\nBroken: 2.82 (unknown which revision, custom build without buildinfo)\nWorked: (unknown)\n\n[system-info.txt](system-info.txt)\n\nViewport is not updated for a material that is driven by a VSE driver.\n\n[ejemplo.zip](ejemplo.zip)\n\nChanging the VSE strip opacity doesn't update the viewport.\n\n**More info from user**\n\nI am creating an addon to transform eevee into a VSE. I encountered several problems, and one is that by changing the values ​​\"chanel\", \"opacity\" or moving the strip (it should disappear). the changes are not visible until the 3d view is moved. Just there it is updated. This makes it uncomfortable to work with the addon. The only change that works well is when changing the resolution X of the render, when playing the video or scrolling through the timeline, everything looks correctly.\nEverything is being controlled by drivers.", "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", "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", "Transform orientation undo is inconsistent.\n\nBroken: 3.0\nWorked: ?\n\nTransform orientation undo is inconsistent. It works in object mode, but doesn't work properly in edit mode. In edit mode it sometimes won't undo, or undoes together with another different step(like changing mode, or moving vertex).\n\n- Open default startup;\n- Change the Transform Orientation from Global to something else\n- Undo/redo - it works;\n\n---\n- Reopen default file\n- Go to edit mode\n- move vertex\n- Change the Transform Orientation\n- undo multiple times - Will never undo the Transform Orientation. (now deselect cube and perform undo operation: will revert selected transform orientation)\n\n", "Drawing of pose markers does not take NLA time mapping into account\nOperating system: Linux-5.11.0-49-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.2.0 Alpha, branch: `master`, hash: `d6e7241237`\nWorked: don't think it ever workerd\n\nShifting an Action on the NLA, then going into tweak mode to edit it, shows the keyframes shifted in the animation editors. The action's pose markers are still in their absolute position.\n\n\n\nThe pose markers should align with the 2nd, 3rd, and 4th keyframe.\n\n- Open the attached file, look at the pose markers.\n- Drag the action in the NLA editor, and see the keys moving while the pose markers stay put.\n\n[[D14176](D14176)-select-markers.blend](https://archive.blender.org/developer/F13001132/D14176-select-markers.blend)\n\n**Context & Relevance**\n\nThese \"pose\" markers originated from the old, now obsolete, pose library. However, regardless of the status of that library, I've heard the desire to have Action-scoped markers (so independent of scene time), and the pose markers would fit that need quite well. The only thing that has to be done to make this a reality is a rename (from \"pose marker\" to \"action marker\") and some UI cleanup. Fixing this bug is a good start.\n\nMarked as low-prio because the new purpose for pose markers isn't that official yet.\n\n**Note:** Be sure to test the `marker.select_leftright` operator as well (f1ae6952a8) after addressing this issue.\n", "Particle Angular velocity doesn't work\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: Never (2.80+)\n\nRotation > Angular velocity section of particle system settings doesn't rotate particles over time.\n\n\n[#81671.blend](T81671.blend)\n* open attached .blend\n* play animation\n", "Bisect Tool rotation Gizmo doesn't behave correctly\nOperating system: Linux-5.15.0-27-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.3.0 Alpha\n\nI wasn't sure how to call the title. \nThe issue is that if you use the Bisect tool in the toolbar, you get an adjust last operation gizmo after using it.\nBut the rotation gizmo doesn't seem to take the mouse movement relative to the viewport rotation into account that well.\nIt behaves quite strange and unintuitively.\n\n- Go into Edit Mode on a cube\n- Select everything\n- Use the Bisect Tool from the toolbar on the cube\n- Use the blue ring on the gizmo\n- Try using it from different angles (rotate around the cube)", "Link-drag-search unsupported in texture node editor\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.1\nWorked: 3.0.0, since there is no such feature.\n\n\"Auto-completion/search\" is not working as intended with Texture Node Editor. For some reason, only reroutes are being displayed. [2022-11-23 22-42-21_1.mp4](2022-11-23_22-42-21_1.mp4)\n\nOpen Texture Node Editor -> Drag from any socket.\n\nNote: sorry for the incorrect spelling of word \"reroute\"\n", "Switching object with alt+click do not fade inactive objects\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.92.0\n\nExpected: same fading as with direct entering to sculpt/edit or as with newer switch operator.\n\n[2021-03-09_16-33-47.mp4](2021-03-09_16-33-47.mp4)", "NLA: Active Strip State lost when dragging Strip between tracks\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: Never Worked\n\nClicking on a strip and dragging or G dragging the Strip on the timeline on the same Track and then hitting TAB to enter tweak mode is working, but if I do the same thing but drag it to another TRACK then hit TAB I get an error\n\nOpen my example Blend file and select the \"Click and Drag Me to the Drag Strip Here track\" STRIP and drag it to \"Click and Drag Me to the Drag Strip Here track\" then hit the TAB key to enter tweak mode, you should see an error as shown in the image. \n\"No active strip(s) to enter tweak mode on\n\"\n\n\n\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." ]

[ "Walk/fly navigation doesn't work properly with graphic tablets\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.41\nGraphic tablet: Huion Inspiroy Q11K V2\n\nBroken: version: 3.0.0 Beta\nWorked: ???\n\nPreviously reported this bug here: T65559\n\nThe fly/navigation mode is still not working for me with a graphic tablet- the view spins on it own.\n\nWhen I change tablet API mode in Blender's preferences to WinTab, when I activate fly mode, the view starts to spin very fast around on the Z axis (looking at the gizmo in viewport's corner). Apart from the spinning, the view tilts quite correctly, you can see the Z axis seems to rotate in relation to moving the cursor up and down.\nWhen I change tablet API mode to Windows Ink, the view stays still when I move the pen - nothing happens.\nEnabling and disabling Windows Ink in the tablet driver (latest version) changes nothing.\n\nWhat's interesting, I tried this addon (mouselook)- it seems to have its own implementation of fly navigation that works well with a tablet.\n\n1) In preferences, change tablet API mode to WinTab.\n2) With cursor in the center of viewport, activate fly navigation (shift+tilde).\n3) Don't move the pen -the viewport's view starts spin very fast around the Z axis on its own (should stay still). \n4) Exit fly mode (escape key)\n5) In preferences, change tablet API mode to Windows Ink.\n6) With cursor in the center of viewport, activate fly navigation (shift+tilde).\n7) When moving the pen, nothing happens, the view stays still (the view should rotate, like when using a mouse)\n\nI'm attaching a screen recording of how it behaves on my PC using WinTab mode:\n[21-11-23 12-10-32-1_h264.mp4](21-11-23_12-10-32-1_h264.mp4)\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).", " Freestyle renders extra lines\n%%%--- Operating System, Graphics card ---\n1st PC: Win7 64bit & Quattro 2000\n2nd PC: Win7 64bit & Nvidia 560ti\n\n\n\n - Blender version with error, and version that worked ---\n2.68a\n\n - Short description of error ---\nFreestyle produces lines through objects as they are transparent\nI build a moving staircase and some lines of the glass roof appear \"randomly\" through the walls.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\n\n\nI just created objects + render. %%%", "Grease Pencil Proportional Edit \"Connected Only\" fails to delimit unconnected strokes if they are selected\nVersion 2.80 rc3 (Linux 54)\n\n[GP_proportional_edit_bug.blend](GP_proportional_edit_bug.blend)\n\nHow to reproduce:\n\n - Open attached file, remain in edit mode.\n - Note the proportional edit settings and selected stroke vertices.\n # Move around the whole blue stroke, along with one vertex at the tip of the black stroke.\n\nObserve how the black stroke is affected by the selected vertices of the blue stroke, even though the two strokes are not connected and are on different layers. This is not the expected behavior of the \"Connected Only\" setting. The strokes should only be affected by their own vertices, but as long as any vertex of either stroke is selected, they will affect each other as though the \"Connected Only\" setting is ignored!", "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 ", "Grease pencil rendering inconsistency when lines are intersecting geometry\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken:\n2.83.3\n2.90.0 Beta\n2.91.0 Alpha\n\nGrease pencil lines are sometimes rendered, sometimes not, depending on distance from camera. This seems\nto be caused by the grease pencil line intersecting the plane:\n\nIn viewport same line is always rendered however (both in solid and rendered modes), which is confusing.\n\n - Open file:\n[grease_pencil_sorting.blend](grease_pencil_sorting.blend)\n - Hit render. Grease pencil line will not be rendered.\n - Move camera -1 or +1 on y axis. Render. Line is still not visible.\n - Move camera -1.1 or +1.1 on y axis instead and the line will get rendered.\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.", "Reflection Plane + SSR produce fuzzy outlines\nIntel i9-10850K, 32 Gb RAM, NVidia GeForce GTX 1070 8GB\nWindows 10 x64\n\nBroken: 2.93, 3.0\nWorked: 2.92\n\nReflection Plane produces thick fuzzy outlines against the background when Screen Space Reflections is also enabled, it reacts to Half Res Trace option which makes it a little bit thinner but it's still very visible which didn't happen in 2.91 where the same outline also exists but is barely visible.\n\n\nOpen provided file, enable Rendered mode and observe the result in the mirror, disable Screen Space Reflections and fuzzy outlines will disappear.\n[Fuzzy_Reflection_Outlines.blend](Fuzzy_Reflection_Outlines.blend)\n\n\nSorry, I haven't seen the reply in my other report before posting this but anyway, is there any way to reduce this? This problem is VERY noticeable and causes a lot of problems.", "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", "Grease Pencil shimmers in the viewport and renders\nOperating system: Windows 7 Ultimate\nGraphics card: Nvidia Quadro 2000\n\n2.92.0\n\nI have a video below, If you see carefully the lines are shimmering, Is there any way to avoid that? watch?v=aBIJbTTiLlU \nAttached a blender file as well.\nI tried \n- increasing samples of viewport \n- increasing anti-aliasing of grease pencil. \n- different render systems 'eevee' and 'cycles'. \n- Tried all possible file exports but the problem is in the viewport itself.\nShould I try denoising it? although that didn't work so well either.\nThe problem just isn't going way. Is it my system? Could you help?\n\n[room fix.blend](room_fix.blend)", "Grease pencil motion blur color bleeding and noise\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 512.95\n\nBroken: version: 3.2.0\n\nRendering objects in front of grease pencil with motion blur causes bleeding of the color behind the grease pencil and a noisy result independent of sample count.\nThis happens for both the stroke and fill option of the grease pencil.\nThis happens for both Eevee and Cycles.\n\nScene setup and Cycles result (note the orange pixels):\n\nEevee:\n\n\nHave grease pencil between two objects with motion blur enabled.\n[GreasyMotion.blend](GreasyMotion.blend)\n", "Mode hotkeys - different hotkeyset for grease pencil object required, entries in keymanager problem\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 51)\nWorked: (optional)\n\n\n\nThe grease pencil object doesn't show the general object mode hotkeys when you assign some. It requires its own hotkey set for the modes. But in the keymanager they will appear as the exact same entries. Except draw mode, which doesn't exist for other object types. \n\nThere is a problem then with the display in the key manager. When you add the extra set for the grease pencil type, then you can't see the mode anymore for the mesh object type modes. I guess it's because it is in fact a double entry with the ones created for the grease pencil object.\n\nI also managed to mess up the object mode hotkeys then with saving the preferences. All modes except object mode had the same key assigned then. But this wasn't reproduceable so far. And might be another issue.\n\n\nCreate a set of hotkeys for the modes with a mesh object. Create a grease pencil object, have a look at the modes. No hotkeys except object mode.\n\nCreate a set of hotkeys for the modes with the grease pencil object.\n\nHead over to the preferences into the keymap tab. Search for mode. Have a look at the Object Non-Modal section. Here you can find the mode hotkeys. Open the first ones up, have a look for the modes. No mode content in the boxes ...\n\nI wonder why the grease pencil object doesn't find the other mode hotkeys from the mesh object at all. That's the second thing. There is no visible difference in the keymanager, it's in the same category ...\n\n\n\n\n\n\n\n\n", "Volume voxels visible in compositing (Cycles)\nOperating system: Windows 10\nGraphics card: GeForce GTX 950 OC\n\nBlender 2.80 cc73d59ad580\n\nFirst of all :\nNot sure if this is a bug or if Im just not getting it.\n\nEverything is done in Cycles\n\nIm subtacting the DiffInd passes in compositing and I get the volxel shape of my smoke sim.\n\nHere a screenshot of my Nodesetup (note the backdrop)\n\n\nI do this to extract the Indirect lighting of for example fire or something else while excluding the sun and stuff.\n\n\nThis is the image (the white cuby thing to the right of the smoke)\n\n\n\n\nAdd a basic smoke simm with high resolution and a ground and wall.\nAdd a sun light\nAdd a new view layer\nExclude the smoke domain from the 2nd layer\nEnable the DiffInd pass for both layeres\n\nIn compositing :\nSubtract the DiffInd passes from each other.\n\n\nThis is an example scene:\n[debug.blend](debug.blend)\n\nIt seems like there is a problem how \"null\" surfaces get handeled.\nIf I set a layer to indirect only the indirect light only appear outside the voxels (where they are intersecting the geometry).\n", "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.", "Grease Pencil vertices selection is offset when Layers/Transform Location as set to a driver\nOperating system: Win10\nGraphics card: RTX3070\n\nBroken: 3.1.0 A\nWorked: N/A\n\n**Short Description of issue**\nMoving a Grease Pencil object's layer via Layers->Transform, by using a Driver, offsets where you have to click to select vertices from that layer.\n\nNOTE: Switching to Draw Mode and drawing a stroke fixes it temporarily, but once you move the controller of the driver again, the problem returns.\n\n**Steps to Reproduce**\n- Open .blend file\n- Select Suzanne and switch to edit mode\n- Try selecting vertices (Does not work)\n- Now attempt to select in circled area\n\n\n\n[#95902.blend](T95902.blend)\nVideo example: iZ_A2wOnAJQ", "Grease pencil: unstable offset height (surface drawing)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\n\nWhen I use perspective camera, and try to drad on surface with GP, offset is unstable and depends on distance from camera.\n\nTest File:\n[#94735.blend](T94735.blend)\n[2022-01-08_10-23-37.mp4](2022-01-08_10-23-37.mp4)\n" ]

[ "Grease pencil stroke partially invisible until mouse-up\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nWhile drawing in the attached scene the stroke is only partially visible. The full line becomes visible only on mouse-up\n\n* open the attached .blend\n* draw over the area with the 3d geometry behind it, only part of the line will show until you end the stroke (see video below)\n\nScreen recording of the problem: Jehz9YAXmE0\n\nBlend file: [gpdrawbug.blend](gpdrawbug.blend)\n\n" ]

[ "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", "Caustics not work as expected\nHi,\nI'm going crazy with shadow caustics.\nOddly they work when they turn off.\nIn the attached scene [caustics_not_work.blend](caustics_not_work.blend), if you disabled caustics on lights or objects, they will be displayed, otherwise no caustics will be displayed.", "Crash going to material preview or rendered shading mode Blender 2.83.0\nMacBook Pro 15 inch Early 2013\n2.7 GHz Intel Core i&\n16 GB 1600 Mhz DDR3\n|Operating system:|MacOS 10.12.5 - @Tramfabriek\n| -- | -- |\n||Mac OS X 10.12.6 (16G2136) - @johan-eds\n|| macOS 10.12.6 - @UmbertoOldani\n\n|Graphics card:|NVIDIA GeForce GT 650M 1024 MB + Intel HD Graphics 4000 1536 MB - @Tramfabriek\n| -- | -- |\n||NVIDIA GeForce GTX 775M, PCIe, 2048 MB - @johan-eds\n|| NVIDIA GeForce GTX 680MX 2048 MB - @UmbertoOldani\n\nBisected to find the bad commit: 804e90b42d\n\nCrash when clicking on Viewport Shading >Material Preview or >Rendered\nThis did happen already in the 2.83 betas, but none of the 2.82 and earlier version had this problem on this computer running this same OS at least since Blender 2.79.\n\n**System crash report 1** (crash in `UI_draw_roundbox_aa` -> `GPU_batch_draw `. Probably the material render icon):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff909add42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff90a9b457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff909134bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff9091342f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff88cdbfbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff76297390 0x7fff7607a000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff88cdd524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff76385867 0x7fff7607a000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff763554fd 0x7fff7607a000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff76282a2b 0x7fff7607a000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff7626ee9a 0x7fff7607a000 + 2051738\n11 com.apple.GeForceGLDriver \t0x00007fff76289654 0x7fff7607a000 + 2160212\n12 com.apple.GeForceGLDriver \t0x00007fff7626af97 0x7fff7607a000 + 2035607\n13 com.apple.GeForceGLDriver \t0x00007fff763851ad gldUpdateDispatch + 1041\n14 GLEngine \t0x00007fff7ff1d32a gleDoDrawDispatchCoreGL3 + 520\n15 GLEngine \t0x00007fff7fecebd9 gleDrawArraysOrElements_Entries_Body + 128\n16 GLEngine \t0x00007fff7fecaab4 glDrawArraysInstanced_GL3Exec + 220\n17 org.blenderfoundation.blender \t0x0000000109614f2c GPU_batch_draw_advanced + 428\n18 org.blenderfoundation.blender \t0x0000000109614d6c GPU_batch_draw + 124\n19 org.blenderfoundation.blender \t0x0000000105218c51 UI_draw_roundbox_aa + 353\n20 org.blenderfoundation.blender \t0x0000000104f3d96c ED_region_do_draw + 1372\n21 org.blenderfoundation.blender \t0x0000000104b6d49c wm_draw_update + 2092\n22 org.blenderfoundation.blender \t0x0000000104b6b010 WM_main + 48\n23 org.blenderfoundation.blender \t0x0000000104827762 main + 962\n24 libdyld.dylib \t0x00007fff9087f235 start + 1\n\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5b521f78 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff5b521fa0 rsp: 0x00007fff5b521f78\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x000000011ab85cf8 r13: 0x0000000000000000 r14: 0x00007fff998033c0 r15: 0x000000011ab85000\n rip: 0x00007fff909add42 rfl: 0x0000000000000206 cr2: 0x00007fff960d0b58\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n\n**System crash report 2** (crash in `blf_batch_draw ` -> `GPU_batch_draw `):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff8b1dfd42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2cd457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff8b1454bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff8b14542f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff83587fbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff71040390 0x7fff70e23000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff83589524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff7112e867 0x7fff70e23000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff710fe4fd 0x7fff70e23000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff7102ba2b 0x7fff70e23000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff71017f8e 0x7fff70e23000 + 2051982\n11 com.apple.GeForceGLDriver \t0x00007fff7100b6bc 0x7fff70e23000 + 2000572\n12 com.apple.GeForceGLDriver \t0x00007fff7100bec2 0x7fff70e23000 + 2002626\n13 com.apple.GeForceGLDriver \t0x00007fff7101113f 0x7fff70e23000 + 2023743\n14 com.apple.GeForceGLDriver \t0x00007fff7143f25e 0x7fff70e23000 + 6406750\n15 com.apple.GeForceGLDriver \t0x00007fff7143f4e6 0x7fff70e23000 + 6407398\n16 com.apple.GeForceGLDriver \t0x00007fff7143f5d7 0x7fff70e23000 + 6407639\n17 com.apple.GeForceGLDriver \t0x00007fff71013d3d 0x7fff70e23000 + 2035005\n18 com.apple.GeForceGLDriver \t0x00007fff7112e1ad gldUpdateDispatch + 1041\n19 GLEngine \t0x000000011925232a gleDoDrawDispatchCoreGL3 + 520\n20 GLEngine \t0x0000000119203bd9 gleDrawArraysOrElements_Entries_Body + 128\n21 GLEngine \t0x00000001191ffab4 glDrawArraysInstanced_GL3Exec + 220\n22 org.blenderfoundation.blender \t0x000000010b288f2c GPU_batch_draw_advanced + 428\n23 org.blenderfoundation.blender \t0x000000010b288d6c GPU_batch_draw + 124\n24 org.blenderfoundation.blender \t0x000000010b283d82 blf_batch_draw + 418\n25 org.blenderfoundation.blender \t0x000000010b282359 BLF_batch_draw_end + 9\n26 org.blenderfoundation.blender \t0x0000000106fc2163 view3d_draw_region_info + 8515\n27 org.blenderfoundation.blender \t0x0000000106936dbd DRW_draw_callbacks_post_scene + 445\n28 org.blenderfoundation.blender \t0x00000001069376cd DRW_draw_render_loop_ex + 1757\n29 org.blenderfoundation.blender \t0x0000000106fc2668 view3d_main_region_draw + 136\n30 org.blenderfoundation.blender \t0x0000000106bb157e ED_region_do_draw + 366\n31 org.blenderfoundation.blender \t0x00000001067e149c wm_draw_update + 2092\n32 org.blenderfoundation.blender \t0x00000001067df010 WM_main + 48\n33 org.blenderfoundation.blender \t0x000000010649b762 main + 962\n34 libdyld.dylib \t0x00007fff8b0b1235 start + 1\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff598ab4b8 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff598ab4e0 rsp: 0x00007fff598ab4b8\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x0000000120bebcf8 r13: 0x0000000000000000 r14: 0x00007fff93fe13c0 r15: 0x0000000120beb000\n rip: 0x00007fff8b1dfd42 rfl: 0x0000000000000206 cr2: 0x00007fff8b1c727d\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n1. Open Blender\n2. Click to remove start up information panel\n3. Click on Viewport Shading >Material Preview or >Rendered\n\nResult:\nCrash", "Shader compilation freeze Blender on Intel Arc770\nOperating system: Windows 10\nGraphics card: Intel Arc770 16Gb (Resizable Bar enabled)\n\n3.6.0\nDate: 2023-06-27 08:08\nHash: c7fc78b81ecb\nBranch: blender-v3.6-release\n\n**Intel driver version**\n31.0.101.4665\nReleased 11.08.2023 (latest on moment of this post)\n\nAll modes of viewport on new scene (default, for example) works fine: solid, material preview, display render. But, if I open my scene, works only 1 and 3 option. Building a shaders freezes Blender. It's around 800+ materials on scene, and GeForce cards works fine with that. The video card works at full power, with enabled Resizable Bar function. Cycles render (oneAPI) also works fine, but i can't switch the viewport on material preview. Blender freezes when shaders start compile.\n\n", "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", "Particles disappear, motion blur not showing properly\nOperating system: Windows 10 Pro, version 21H2, OS version 19044.2486, 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB, version 31.0.15.1694\n\nBroken: version: 3.2.1\n\nParticles disappear in animation, most notable at the beginning.\n\nDuring the dissolve effect, motion blur isn't showing. At the moment the effect ends, motion blur shows up.\n\n1. Render e.g. frame 16; particles are not showing, no motion blur.\n2. Render e.g. frame 31; all particles seem to be showing, motion blur.\n\n", "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", "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", "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", "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", "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**", "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", "Steam Blender doesnt open Saved Files\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\n\nSaved Files from Steams Blender do not open and require me to have a normal Blender file downloaded separately.\n\nSave a file from the Blender downloaded from Steam, then try to open it normally. The PC will say it cannot find a suitable software to open it in. The problem will be fixed if I have a separate Blender downloaded. (I need the steam to count the time I spend on it)\nBased on the normal Startup of Blender, I have not added or changed anything.\n\nThank you very much, and all the best.\nTake care.\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", "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" ]

[ "ChromeOS: Black screen/window on startup: \nOperating system: Chromeos 83/84/85 buildin linux VM\nGraphics card: Intel Gen8, HD Graphics 5500/UHD Graphics 620\n\nBroken: (2.83 LTS, 2.90 Alpha)\nWorked: (2.82a)\nFirst bad commit: 001f7c92d1\n\nBlack window/screen never shows the splashscreen\nSee attached picture\n\n```\nWarning: Could not find a matching GPU name. Things may not behave as expected.\nDetected OpenGL configuration:\nVendor: Red Hat\nRenderer: virgl\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. start ./blender from its home folder\n2. Black window/screen shows up\n\n[P1458](P1458.txt)", "Program Crash on Launch blender 2.83.0 linux \n**Google Pixelbook i7 16 GB**\nOperating System: Debian GNU/Linux 10 (buster)\n```\n Kernel: Linux 4.19.113-08528-g5803a1c7e9f9\n Architecture: x86-64\n```\nGraphics card: Intel HD Graphics 615\n\nblender-2.83.0-linux64\nBroken: Crash on launch\nWorked: blender-2.82a-linux64\n\napplication window appears with completely black screen. Splash screen never appears.\n\nlaunch ./blender from terminal .\n\n**Notes**\nlaunching ./blender-softwaregl from terminal allows blender 2.82a-linux to launch, however performance drops exponentially. " ]

[ "Empty object property \"Size\" should be \"Radius\"\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.0\n\n- Mesh Cube is 1 meters wide when set its \"Size\" to 1 meters when creating\n- Empty Cube is 2 meters wide when set its \"Radius\" to 1 meter when creating.\n- However the property tab for the empty cube shows \"Size\" as 1 when it really supposed to mean \"Radius\".\n\n- Add a Mesh Cube with size 1 meter\n- Add an Empty Cube with size 1 meter\n- Compare the size. The size of Empty Cube is 2 Meters when set to 1 meter\n\n", "Geometry node - setting lacunarity to 0 crashes Blender (musgrave texture)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.2.2\n\nIn a fairly simple geonode tree, trying to set lacunarity to 0 will crash Blender instantly.\n\n- Use attached Blend.file\n- In the 'set position' branch, try to set 'musgrave texture' lacunarity to 0\n- Crashes everytime for me\n\n[Geonode attribute.blend](Geonode_attribute.blend)", "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)", "Checker texture artifacts when feeded with object texture coordinates\nOperating system: Linux-5.4.0-90-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.1.0 Alpha\nWorked: afaik never, still had this issues with all previous versions down to 2.7\n\nChecker texture has calcuation issues when feeded with object texture coordinates.\nOther textures like brick or voronoy are ok.\n\ncreate a plane\nassign the checker texture with object coordinates\n\n\n[checker_texture_problem.blend](checker_texture_problem.blend)\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", "Object Info node not update if delete object from viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nIf you delete an object selected in the Object Info node, the object remains selected in the node\n\n\n\nDelete object from viewport selected in the Object Info node. Object Info node not update socket\n\n[Proximity_displaces2.blend](Proximity_displaces2.blend)\n\nNote that if you delete it from the outliner things work. The issue is when the object is deleted from the viewport.\n\n**Original file**\nThis file doesn't help because the object was already deleted from it:\n[Proximity_displaces.blend](Proximity_displaces.blend)\n\n\n\n\n", "Geometry Nodes: volume output shows as cube in eevee rendered view\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nVolumes outputted via geometry nodes appear as a cube when rendering in eevee\n\n - Solid viewport: Looks ok\n - eevee material preview/rendered: Volume appears as a cube\n\t\nThis affects volumes from the Points To Volume node as well as when using a volume via a Object Info node. Cycles seems ok once the material has been assigned to the object instead of the data.\nI did try some debugging for this issue and it appears that the volume is setup correctly but the rendering code seems to be called twice once for the real volume and again for an empty mesh which obscures the real volume. \n\n\nOutput a volume with geometry nodes and switch to the eevee rendered view (Right side of picture below)\n\n\n", "Texture properties not working with OSL enabled and unpacked textures\nOperating system: Linux-5.11.7-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 520 (SKL GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.92.0\nBroken: version: 2.93.0 Alpha\n\nI have a texture with RGB channels set to 1 and alpha set to 0. When trying to use this texture with OSL, the alpha property (at least) of the image texture node does not work when the texture is unpacked. I set it to channel packed, expecting the color data to be always white. The problem is that when the texture is unpacked, the color data is black.\n\n1. Open the attached file.\n2. Set viewport shading to rendered.\n3. The plane shows as white (as it should).\n4. Unpack the texture.tga file.\n5. Toggle between preview and rendered viewport shading to refresh.\n6. The plane now shows as black.\n7. Pack the texture again.\n8. The plane shows as white again.\n\n[bug.blend](bug.blend)", "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", "Some Overlays are not rendered in Viewport Render (Text Info incl object name, Statistics, 3D Cursor)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.1\nAlso 3.1.0 Alpha\n\nUsing viewport render (or workbench) I'm unable to view object or empty names \n```\n(bpy.data.objects[\"NAME\"].show_name)\n```\n\nEnable show name on a visible object, and make a viewport render (bpy-ops-render-opengl)\nThe text isn't rendered in the image like it is in the viewport.\n\n", "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)", "Material Preview (and final render in EEVEE) purple\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7263\n\nBroken: version: 2.83.0\nWorked: I don't remember this bug occuring in previous versions.\n\nI know, that materials should become purple when the texture is missing.\nBut the problem is that they not behave as they should even without applying textures and also with the default material.\nThis bug occurs in EEVEE:\n1) In material preview in properties\n2) In render\n3) Sometimes - in viewport\n\nIn a render, it is also a problem with the scene surface material.\nI attach some screenshots from material preview: they are all the same default material.\n\n\n1) Open Blender\n2) Press F12 or go to material preview in object settings.\n3) ... see the bug\n\n\n\n\n\n\n\n\n", "Ghost / False Node inputs\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40\n\nBroken: version: 3.1, 3.2, 3.3\n\nWhen the output type of a node changes:\n\nVector Math multiply (vector output) ----> Vector Math distance (float output)\n\nIt causes the node that has the changing type as it's input to be in a bugged state.\n\n* Open .blend file\n[ghost_inputs.blend](ghost_inputs.blend)\n* Change the multiply to distance (easiest one I could think of)\n* The other math node will be in a messed up state\n\n* You can even drag from the ghost input and you will be able to see that Blender thinks it is still connected.\nThanks!", "EEVEE-Next: Refactor renderpass storage\nCurrently render-passes are allocated in multiple texture buffers.\nThey take a lot of binding points and currently prevent the deferred pipeline to output diffuse color correctly.\n\nThe plan is to combine all render-passes into the same array texture and use an associated UBO containing offset to the layer of each pass type.\n\nThis would very similar to the AOV support.\n\nAnother direct benefit of this would be that the GBuffer encoding could be simplified.\n\n", "A combination of shader nodes causes lack of material emission at any brightness (Cycles)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.0(tested as well on 3.3.0 and 3.5.0 alpha)\nWorked: (none)\n\nA difference of bevel node and normal coordinates produces no light at any emission level. Clipping the result due to suspicion about negative brightness has no result.\nNote: adding any value to the result adds corresponding emission, but despite visuals, brightness from combination above does not.\n\n\n- Open attached file\n[cycles_where_is_emission__bug.blend](attachment)\n\n\n" ]

[ "Texture coordinate object output error\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 53)\nWorked: (optional)\n\n\nTexture coordinate object output error when move cube object.\n\n[bug.blend](bug.blend)\n\n\n\n\n", "Procedural texture doesnt follow an empty in Eevee\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 71)\nWorked: (optional)\n\n\nMoving an empty moves texture in Cycles but not in Eevee.\n\n(Switch to Rendered) Move/scale/rotate the empty in attached blend file. Using Cycles everything works as expected. Using Eevee the procedural texture doesn't react.\n[TextureNotFollowEmptyInEevee.blend](TextureNotFollowEmptyInEevee.blend)", "Custom object coordinate does not work on Eevee\nOperating system: Windows 10 Pro\nGraphics card: GTX1080\n\n1af810b4ff17\n\nThe custom object mapping mode is not working on Eevee\n\n[Object Mapping.blend](Object_Mapping.blend)\n3D Viewport is set to Look Dev mode (Eevee)\nMove around the timeline a bit. Nothing happens.\nSet 3D Viewport to render mode (Cycles)\nMove around the timeline a bit. Mapping works as expected.", "Texture coordinate object reference not interactively updating in Eevee\nWindows 10 (Tested in Linux too)\n\nblender-2.80.0-git.c750ebe113e-windows64\n\nThe Texture Coordinate Node's ability to reference an external object to manipulate coordinates does not function in Eevee. You can select an empty, for example, and move it about and it has no impact on the resulting texture coordinates.\n\n", "Object texture coordinate updates in viewport only if material has animation data\nOperating system: Linux-4.15.0-47-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 (sub 54)\nWorked: in cycles.\n\n\nObject texture coordinate updates only if material has animation data\n\n1. Open file:\n\n[object-coordinate-test.blend](object-coordinate-test.blend)\n\n2. Change viewport shading mode to **Rendered** and playback the animation. You will see:\n\n\n\nThe difference between to planes is the right one has a keyframe in one of the material nodes.\n\n", "Vector math node works different in Cycles / EEVEE\n{[F6875849](LBC-035.blend)}Operating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Intel(R) HD Graphics 520 Intel 4.5.0 - Build 23.20.16.4973\n\n\nBroken: version: 2.80 (sub 51)\nWorked: (optional)\n\n\nIn Cycles the vector math node ( dot-product ) works fine. If I switch to EEVEE the shader is not mixing correctly.\nRemoving the dot-product solves the problem.\n\n\n\n- Open the blend-file \"LBC-035.blend\"\n- Render in Cycles --> OK\n- Switch to EEVEE --> render is not OK\n- Remove dot-product en connect mapping to colorramp --> OK\n\n\n\n\n\n\n\n", "Object Texture Coordinates missing refresh for Eevee\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 73)\n\nWhen using Object Texture Coordinates, it doesn't refresh when moving the object\n\n - Open this blend:\n\n[object_coordinates_refresh_bug.blend](object_coordinates_refresh_bug.blend)\n - Move the Empty object\n - Notice the gradient texture isn't updating\n - Select one of the cubes, and un-plug and re-plug the Texture Coordinate node\n - Now it will update\n\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", "The Object Mode drop down menu in the 3D viewports is not reactive to larger font point settings.\nOperating system: Windows 10 1803\nGraphics card: nVidia RTX 2070\n\nBroken: v 2.80 as found on the splash screen\n\nThe Object Mode drop down menu in the 3D viewports does not properly resize itself if the user picks a larger font point size in the Themes section of the preferences. Instead of resizing the control truncates the overrunning text with a square character.\n\nStart Blender\nIn Preferences \\Themes \\ Text Style change the Widget Points setting from the default of 11 to a larger value. I used 15.\n\n", "Usability issues with old group operators\nBroken: 2.79, 2.8x\n\n\nWhen using linked objects, all the Group commands [Remove From Group / Remove From All Groups / Add Selected To Active Group / Remove Selected From Active Group] except [Create New Group (Ctrl G)], do nothing\n\n\nIn my particular usage, I link a scene from one file into my main scene, afterwards I create a [New scene with Link Objects] from the Linked scene. \n\n [GroupsFail.blend](GroupsFail.blend)\n [GroupsFail-MainScene.blend](GroupsFail-MainScene.blend)\n\nI can Create Groups by selected objects, and I can remove the group from the object in the Object Properties tab but the only way to remove multiple groups is through python script or deleting the group itself.\n\nSince this report is used to more generally handle issues with the old group operators and other reports have already been merged here, will also list these:\n- Ctrl G is placing new collections inside \"Orphan Data\"", "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)", "Nodes: Group input subtype \"Angle\" max values are in radians, but the default implies degrees.\nOperating system: Linux-5.4.0-148-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: 3.6.0 Alpha\n\nThe subtype \"angle\" in the socket editor provides a default value in °, and a min and a max value, which seem related to the default setting in degrees, so the user assumes the slider in the modifier frontend UI to stop at the set values. Which it doesn't. Set max to say 1, and the slider will stop at 57,3° (180/pi), not at 1°.\n\n\n", "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", "Applying Data Transfer Modifier - only the active Shape Key is taken into account\nOperating system: Win 10 x64\nGraphics card: 3080 TI\n\nBroken: 3.3.2, 86abbf717691, master, 2022-11-28\nWorked: ??\n\nWhen applying data transfer modifier to an object (to transfer vertex groups), it only takes into account the selected shape key, not all others too.\n\nExample:\n\nDownload test Blend:\n[datatransfer_shapekeys.blend](datatransfer_shapekeys.blend)\n\nThis is the cube's vertex group:\n\n\nPlane is moved down by shape key \"Key 1\". All looks good in the viewport, this is how the vertex group should look when you apply it:\n\n\nBut if the 'Basis' shape key is selected instead of 'Key 1' when you apply the modifier, it ignores Key 1.\n\n\nSee how the position of the vertex weight is off as compared to the first picture, as if Key 1 were disabled.\n\n\nBut if you were to have Key 1 selected when you apply the modifier, it works as expected:\n\n\nThis is troublesome with objects that have many shape keys, all with different influences on the affected area. When you apply the modifier, it should take into account every active shape key.\n\nThis gets even less predictable if you have multiple shapekeys besides the `Basis` shapekey.\nHere I have two (both with 0.5 weight).\nYou get different results selecting `Key 1` or `Key 2` and none look like what you had in the viewport:\n[datatransfer_shapekeys_multiple.blend](datatransfer_shapekeys_multiple.blend)", "Improve usability of Group Colors in animation editors\nProblem:\n\nWithout going into much detail, as it stands in the animation editors for the right contrast to be achieved between the white text and the colours they have to be dim but to be useful in the view port they need to be bright (again for contrast).\n\nBlender's default colors unselected in the viewport:\n\n\nOriginal Group Colors selected in the viewport:\n\n\nBrightly colored bones are especially important in the 3D Viewport when they have thin shapes. Dimmer bone colors are hard to see over Blender's dark wireframe and dark background.\n\nIt's really hard to tell apart the selected ones from the non selected ones.\nIf i didn't show you the first picture and you only looked at the second picture you wouldn't have a clue whether any bone is selected or unselected.\n\nThe Rigify add-on uses bright bone colors to aid visibility in the 3D Viewport. However, this makes the channel list unreadable, as can be seen in the image below.\n\nFor optimal readability in the Channel List the colors would have to be darker, which conflicts with the requirements for the 3D Viewport.\n\n\n\nThis method has 1 great side and very important for animation which is making very obvious and clear which bones are selected, unselected and active.\n\nAnd the downside is that the dope sheet/graph editor gets even more unreadable when you expand the channel's attributes:\n\n\nLeaving us in at a point of: bright groups will give us the readability we need in the viewport but mess completely the animation editors and on the default colors improving the readability in the animation editor but making it really hard on the eyes in the viewport.\n\nSo currently the existing solution\nHere comes: \n\n\nAn option that has been there for ages and has proven not only useful but for anyone that works with character rigs is the first button they press every time they go to the graph editor posing a new problem: the option is local to the file, so every new shot, every new animation you need to un-tick this box in every animation editor.\n\nSo there are a few things here we propose which \n\nFirst: **Move the option to the Animation preferences panel**\nPros: you as user chose how do you like it to stay, even if it its on by default you turn it on once and that's it.\nCons: it's still on by default.\n\nSecond: **Redesign the way the bone group colors are presented in the animation editors**\nPros: done well means we could eventually get rid of the option to turn on/off if we come to a solution that is non intrusive a-la outliner, taking full advantage of all the ideas that at this moment seem to be playing against each other.\nCons: longer process to design and implement correctly.\n\nIn adition to the presentation of the bone group colors in the animation editors we also can see that creating and editing group colors can be time consuming and way more complex than we want it to be, we'll propose a simplified yet powerful version that will be more clear and faster to setup.\n", "Value of Quad Corner Type changes automatically in the Subdivide operator.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.93.0 Alpha\n\nValue of `Quad Corner Type` changes automatically in the Subdivide operator.\n\n\n1) Open Default Scene.\n2) Go to Edit Mode, right click and select Subdivide.\n3) Uncheck the Create N-gons box.\nQuad Corner type is automatically set to `Inner Vert` from `Straight Cut`.\n\n(But we can still select `Straight Cut`, not like its disabled) so this doesn't look like consistent behavior?\n\n", "Grease Pencil vertex paint select is using sculpt mode selection mode\nOperating system: Linux-6.4.6-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.6-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-50c29e1ffa)\n\nBroken: version: 4.0.0 Alpha\nWorked: \n\nWhen selecting with mouse clicks the selection mode in the header determines which component is selected.\nIn Grease Pencil sculpt mode this behaves as expected. If it's set to \"points\", selecting will select points. If it's set to \"stroke\" it will select entire strokes.\n\nWhen switching to vertex paint mode this is not the case. Instead it will select components based on the selection mode that is set in sculpt mode.\n\nThe ideal behavior imo would be to have all grease pencil modes share the active selection mode.\nThis makes it easier to manage and simpler to use.\n\n- Change the keymap preferences to right click select (Selection shortcuts in left click select are partially broken atm)\n- Add a Gpencil Monkey\n- Switch to Sculpt Mode\n- Enable point selection mode\n- Select some points with `RMB` and `Shift RMB`\n- Switch to Vertex Paint mode\n- Make sure to use stroke selection mode\n- Select some strokes with `RMB` and `Shift RMB` (Notice how it will instead select points)\n\n", "X-ray toggle button in weight-paint mode is ignored (honors edit-mode setting instead)\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.91.0-a509e79a4c77-linux64\nWorked: 2.80 - Xray was not changed when switching modes there\n\nWhen in weight-paint mode, with select vertices enabled, the \"Toggle X-ray\" button in the upper right corner is ignored, does not allow to select vertices through the object (on both sides). But instead, if you switch to the edit mode, enable the x-ray mode, and then switch back to the weight-paint mode, then the vertex selection through object is turned on correctly. So oddly enough, the weight-paint mode x-ray is controlled from edit mode, ignoring its own x-ray toggle button.\n\n**Steps to reproduce**\n[xray-weight-paint-bug.blend](xray-weight-paint-bug.blend)\n\n- Open file\n- Toggle X-ray mode", "Eevee Group Node ignores socket type conversion (eg. Vector to Float)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha, branch: main\nWorked: N/A\n\nIf the input of a group node is `Float`, but you connect a `Vector`, the group will read the input as a vector instead of a float.\n\n1. Download the Blender file below\n[test.blend](test.blend)\n2. Switch to Eevee, it looks like this:\n\n3. Switch to Cycles, it looks like this:\n\n\nIt seems to be node group evaluation. When ungrouped it looks identical.", "Using Ctrl to select bones in weight paint mode with Xray on is broken with left click select\nOperating system: Gentoo Linux\nGraphics card: AMD 5700xt\n\nBroken: 2.90 master, 2020-05-25\n\nWhen using X-ray in weight paint mode, you can no longer select bones with left click select (the right click select keymap works)\n[weightpaint.mp4](weightpaint.mp4)\n[test_gradation_T01_01.blend](test_gradation_T01_01.blend)\n\n1. Open the attached file.\n2. Go to the \"viewport shading\" drop down menu and activate X-ray with something less than 100%\n3. Try to select any bones with ctrl + left mouse\n4. Notice that you can't select any bones with X-ray on.\n\nI noticed that this is caused by a \"Select\" key binding in weight paint mode. This binding only exists in the left click select key map.\nIf I remove this binding, I can select in xray mode again. This doesn't seem to remove any functionality, so I am a bit confused why this binding exists here at all.\n", "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", "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." ]

[ "Adjusting properties in weighting operation popups reverts vertex group locks\nOperating system: Linux (and others)\nGraphics card: nVidia 1060\nBroken: 2.9x\n\nIn Weight Paint mode:\nIf I lock some vertex groups and then Weights -> Smooth (or any operation that has adjustable values), things behave as expected.\nBUT, if I then try to alter the values the Properties popup window, the list of locked vertex groups changes (revert/undo?), which causes weights to bleed undesirably & defeating the purpose of locking groups.\nThis can even return a \"*All groups are locked*\" error, if the previous configuration had 1 or less groups unlocked and Weights -> Normalize All is performed. Normalize All needs at least 2 groups unlocked to shift weights around, and if you try to alter the properties popup it will revert the locked weights list to an incompatible configuration.\n\nI've verified this bug with the Smooth, Levels and Normalize All procedures. Therefore, I'm assuming this will affect any Weights operation that has an adjustable properties popup.\n\n1. Create cylinder (subdivisions not needed, but helps if you wan to understand the technique being used).\n2. Skin cylinder to chain of at least 3 bones that resides within the cylinder.\n3. Enter Weight Painting mode.\n4. Lock all but 2 of the vertex groups, and select one of the unlocked groups.\n5. Activate Weights -> Smooth\n6. Adjust some values on the Factor or Iterations on the Properties popup.\n7. Notice how the list of locked groups changes.\n\n[weightsUnlock_2020-12-27.mp4](weightsUnlock_2020-12-27.mp4)\n\n**Assumed Issue**\nPerhaps Blender is altering these Properties values via Undos? \nIf, in between steps 4 and 5, you perform another action (i.e. enter and exit Edit mode) it will not change the list of locked Vertex Groups.\n\n**Importance**\nThis weight locking technique is very effective in preventing skin weights from bleeding across the model when skinning, which creates a mess that require cleanup (*see timestamp 9:30 Demeter's tutorial on \"[Weight Painting Part 2 ](5efe0d7405aef1cf3b89644d#comment-4576)\". Demeter demonstrates the problem and his workaround, which can introduces other problems, as the \"Clean\" operation is destructive and does not always fully fix the bleeding weights.\nIn the comments of the tutorial, I demonstrate the precision gained when using locked group weights and how it prevents bleeding, removing the need for any post cleanup.\n\nThis bug prevents the awesome property sliders from being used, meaning that values have to be set very low and the weighting operation needs to be performed in multiple steps till the desired effect is reached. This is not a very effective workaround.\n\n**BONUS**\nWhile looking at the code involved in this bug, I request looking at adding in a \"Normalize\" checkbox to allow the affects of the operations to be seen immediately on the vertex positions, without the requirement of additional Normalize steps.\nWhen performing operations such as Smooth, it's very common (assumed) that this step will be followed up with a Normalize All operation. Many popular skin weighting addons (see below) try to fill this gap by introducing checkboxes to automatically perform Normalize operations after adjusting weights.\nHere are two Example Addons that introduce an \"auto normalize\" for common Weight operations.\nweight_paint_tools\nsmooth_unlocked", "Vertex weight options error modifing parameters\nOperating system: Linux-5.4.0-58-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.91.0\n\n\nIn weight paint if you apply an option and modify the parameters they make effect only on the first vertex group that you enter in\n\n\n*Download the attached .blend and open the file\n*Select one of two vertex group and next switch to weight paint\n*Select an option (for exemple smooth) and change any parameters (for example factor)\n*It is stil ok, but if you switch to the other vertex goup and repeat these passages when you change any parameters it returns to the first one\n\nIf i want apply the right parameters I have to leave weight paint, select another vertex group and re-enter, or I could apply the option to the first, then I cancel whit crt+z (if I don't want it) and re-apply whitout changing anything to the another\n\n\n[weighterror.blend](weighterror.blend)\n\n\n\n\n", "Weight paint mode \"Levels\" option changes active vertexgroup after execution\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nTrying to set vertex group levels, the active group keeps changing automatically and unpredictably.\n\nSee attached video.\nSetting the weight level of a vertex group is very un-intuitive, and even when following the correct steps, often doesn't work as expected.\n1. Go into weight paint mode.\n2. Select a vertex group.\n3. Choose menu option Weights/Levels.\n4. Choose \"Active Group\" for \"Subset\", and make some changes.\n5. Sometimes, a different group is automatically selected and the changes applied to instead of the group that was selected when choosing the menu option.\n[Weight Levels 720.mov](Weight_Levels_720.mov)\n\n" ]

[ "Grease Pencil keyframes not updating after GPencilFrames.copy()\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha\n\nCopied keyframes do not update with Grease Pencil Layer\n\n- Create a new document with the 2D Animation template\n- Draw a shape \n- (Note by @iss) It may be necessary to make new keyframe at later frame, see video\n- Run the below script in the Text Editor\n# Run the \"Grease Pencil Test Script\" command from the Draw Menu\n\nThe Grease Pencil data isn't updating in the Viewport unless the playhead is going backwards, a keyframe is deleted, or if the keyframes are added to a new `GPencil` object. I believe the issue is because the keyframes generated with `GPencilFrames.copy` are missing the layer update for some reason. If I use `GPencilFrames.new()` and copy every attribute manually, this issue does not happen. In the below code, I am updating all of the data I know to be possible.\n\n```\nimport bpy\n\ndef main(context):\n active_layer = context.active_gpencil_layer\n frames = active_layer.frames\n start_frame = frames[0]\n frame_numbers = [frame.frame_number for frame in frames]\n\n for frame in range(start_frame.frame_number, context.scene.frame_end+1):\n if frame in frame_numbers:\n continue\n new_frame = frames.copy(start_frame)\n for i,start_stroke in enumerate(start_frame.strokes):\n new_stroke = new_frame.strokes[i]\n for p,start_pt in enumerate(start_stroke.points):\n new_pt = new_stroke.points[p]\n new_pt.co[0] = start_pt.co[0]+(frame*0.5)\n new_frame.frame_number = frame\n\n gpencil = context.object\n gpencil.data.layers.update()\n for l in gpencil.data.layers:\n l.frames.update()\n for f in l.frames:\n f.strokes.update()\n for s in f.strokes:\n s.points.update()\n\n gpencil.data.update_tag()\n context.view_layer.depsgraph.update()\n context.view_layer.update()\n bpy.ops.gpencil.recalc_geometry()\n\nclass GPENCIL_OT_simple_operator(bpy.types.Operator):\n bl_idname = \"gpencil.simple_operator\"\n bl_label = \"Grease Pencil Test Script\"\n\n def execute(self, context):\n main(context)\n return {'FINISHED'}\n\ndef draw(self, context):\n self.layout.operator(GPENCIL_OT_simple_operator.bl_idname)\n\ndef register():\n bpy.utils.register_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.append(draw)\n\ndef unregister():\n bpy.utils.unregister_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.remove(draw)\n\nif __name__ == \"__main__\":\n register()\n```\n\nPlease disregard the step where I put the GP Object into Edit mode & create a new keyframe. This step is not necessary to seeing the `GPencilFrames.copy` bug.\n[duplicated_frame.mp4](duplicated_frame.mp4)\n\nNot sure if the bug will show consistently, but here is the scene file:\n[Grease_Pencil_Data_Bug.blend](Grease_Pencil_Data_Bug.blend)", "GPencil: Object keyframes are not visible in grease pencil dopesheet mode\nOperating system: windows 10\nGraphics card: GTX 1650\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nIn grease pencil Object when I assign a key frame to its properties (like opacity or transformation ), I cant see the key frames in the action editor.\nAnd same thing when I do frame by frame animation.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n{[F10286546](GP_and_Action_Editor.blend)}", "Inconsistent Grease Pencil auto-keying behavior\nOperating system: Linux 64-bit\nGraphics card: GTX 1080\n\n3.1 and prior\n\nWhen auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe. \n\nAlso, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.\n[GP_autokey_bug.blend](GP_autokey_bug.blend)\n - Open the attached file.\n - Grab (G) a stroke, then right-click to cancel moving it. The keyframe was inserted, even though no change was made.\n # Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!\n\n", "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)", "Regression: Blender text editor lost support for dead keys\nOperating system: Linux-4.19.0-11-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 2.93.0\nWorked: 2.92\n\nCaused by cafd6b519c\n\n\nOn any text input field, on the Python Console, on the text editors, I cannot type any of the characters that need dead keys (I use English International with dead-keys to type English, Spanish, and German).\nI cannot, for example even type quotes, which makes Python expressions hard - let alone accents, etc. \n\nThis used to work on previous versions of Blender. The latest I found it working on is on a 2.92 release candidate I had somewhere on my hard drive.\n\n\n1. On a computer configured with dead-keys input, open the default scene\n2. Switch the main display to be a Text Editor.\n3. Press \"New\" to create a new file.\n4. Try to type \"é\" (by pressing 'e) or \"'' by typing (' space).\n\nExpected behaviour: Blender accepts the typed-in characters.\nActual behaviour: Blender ignores the typed-in characters.\n\nSomething like this gets printed to the console:\n\n```\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7f80237f2980 0x7f804905d0c0\n```", "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. ", "Sculpting - Switching stroke method with a shortcut causes a freeze\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1\n\nWhen using E shortcut in sculpt mode to change stroke method of the brush, there is a ~5-10 second freeze every time.\nHowever, when you do the same thing from the brush UI, the switch is silky smooth. See the video for example\n\n1. Open attached file\n2. Switch to sculpt mode\n3. Do a few strokes, press E - blender will freeze for about 10 seconds\n4. Do a few strokes again, this time change stroke method from UI - no freezes here\n\nVideo:\n[blender_am0pkp0Cwy.mp4](blender_am0pkp0Cwy.mp4)\nExample File:\n[sculptbug.blend](sculptbug.blend)\n\n", "Wintab rarely gets into a bad state and prevents Blender startup\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked:\n\nFor a few months now, I have been getting a fairly rare, but reoccurring issue (maybe once a week on average) where Wintab gets into some erroneous state and prevents Blender from starting if the Tablet API setting of the Input preferences is set to `Wintab` or `Automatic`.\nWhen Wintab gets into this erroneous state and Blender is already open, Blender will crash if I attempt to open the User Preferences. I'm not sure what else might cause a crash when Blender is already open.\n\nBy adding extra logging to a custom build of Blender, I've determined that the crash when starting Blender occurs when calling the `open` (`WTOpenA`) function: GHOST_Wintab.cc#L85\n\nMy drawing tablet's software also reports an exception in `WTOpen`, the value of which appears to equal 0xC0000005 which I think indicates a `STATUS_ACCESS_VIOLATION` according to 596a1078-e883-4972-9bbc-49e60bebca55.\n\n\nIn the drawing tablet's software, this exception only occurs if I actually connect the tablet to my PC, whereas Blender crashes even when the tablet is not connected.\n\nCurrently, if I don't actually need my tablet, I'm working around the issue by starting Blender headless, changing the Tablet API setting to Windows Ink, and then starting Blender normally.\n\nI have already tried updating the drivers for my tablet to the newest version and it made no difference.\n\nIf I start Blender with `--debug-wintab`, all that's printed is:\n```\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release> .\\blender.exe --debug-wintab\nRead prefs: \"C:\\Users\\Thomas\\AppData\\Roaming\\Blender Foundation\\Blender\\4.0\\config\\userpref.blend\"\nLoading Wintab for window 00000000000910C4\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release>\n```\n\nEvery version of Blender I've tried between 2.79 and 4.0.0a crashes unless I have the Tablet API set to `Windows Ink`.\n\nI don't know the specifics of how Wintab is handled, but could it be possible to either catch the exception in `WTOpen` and allow Blender to continue loading, or to check for a connected tablet before attempting to call `WTOpen`, similar to what my tablet's software appears to be doing?\n\nUnfortunately, Wintab getting into this erroneous state where it crashes in `WTOpen` occurs too rarely for me to figure out how to reproduce it and I'm not even sure if it's Blender that is causing it to get into this state in the first place.\n\n", "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", "Grease Pencil ripped line when rendering in EVEE\nOperating system: Windows 10\nGraphics card: GeForce 1050 ti\n\n3.62\n\nGrease pencil object is displayed normally in the viewport, but when rendering the line becomes jagged, not like in the viewport. In Cycles all is good.\n\n\n\n", "Image-editor UI/mode inconsistency related to Annotation\nOperating system: Linux-5.16.11-76051611-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (NAVI10, DRM 3.44.0, 5.16.11-76051611-generic, LLVM 12.0.1) AMD 4.6 (Core Profile) Mesa 21.3.5\n\nBroken: version: 3.1.2\n\nI have tested this on development/latest version (on Jeroen's desktop ;)\nAlso tested this with 3.0.1 release (last version on steam)\n\n\n\nTwo (related ?) issues:\n\n1) When switching FROM 'VIEW' TO \"PAINT\" modes in image-editor the grease-pencil mode is retained, even though UI indicates that you are trying to paint with selected brush\n2) When using Grease-Pencil in PAINT mode, switching to VIEW mode will not indicate Grease-pencil is active, while it in fact is. (Annotate-button not highlighted) \n\n1) \nExpected result is : painting with the brush that is active (showing brush-circle)\nReal result is: having a large 'brush-circle' that produces GreasePencil marks instead of brushed paint on Image-editor in 'paint' mode\n\n2) \nExpected result: When having used Annotate/GP in PAINT mode, switching to VIEW mode should *either* de-activate Annotate-mode OR Highlight Annotate-tool-button to indicate state\nReal reasult is: Switching from PAINT to VIEW mode after having annotated results in Annotate-tool still being active, but UI does not reflect this state.\n\n\n\n1) \nCreate image editor panel\nCreate image\nSwitch to 'VIEW' mode\nSelect 'Annotate' tool\nDraw something with Grease-Pencil\nSwitch to 'PAINT' mode\n\nIn my tests, I get shown a UI that clearly intends me to stroke a brush. It has the brush-type shown (right-side), and it has the top-most tool (Draw) highlighted, as well as showing a large circle-shape to indicate brush-size on mouse-cursor position.\n\nHowever, stroking results into Grease-pencil stroke.\n\n\n2)\nCreate image editor panel\nSwitch to 'PAINT' mode\nSelect 'Annotate' tool\nAnnotate\nSwitch to 'View' mode.\n\nIn my tests, this results in me being able to annotate, though the Annotate-tool is not highlighted.\n\n\n\n\n\n", "Grease Pencil wrong Cursor Size Smooth Brush when accesed with the [SHIFT] key\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 460M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.3.1\nWorked: \n\nThe On Screen **Smooth Brush Cursor Size** is inaccurate when using the Smooth Brush with the **[SHIFT] **key while using any other brush of a different radius setting.Grease Pencil > Draw any curve \nGrease Pencil > Sculpt > **Smooth Brush**> Make the Smooth **Brush Radius VERY SMALL** (10).\nGrease Pencil > Sculpt > **Grab Brush** (or **ANY OTHER BRUSH**) > Make the **Brush Radius HUGE**(150). \nUse the **Grab Brush** as you wish.\nPress **[SHIFT]**to activate**Smooth Brush**while in Grab Brush (or**ANY OTHER BRUSH**)\nThe on screen cursor Radius while the [SHIFT] key is pressed does not reflect the VERY SMALL Brush Radius (10) that we set earlier. This is constantly confusing. Can you please make the radius display correctly based on the actual Smooth Brush Setting?\nattached scene: GreasePencil_SmoothBrush_CursorSize_bug.blend\n[GreasePencil_SmoothBrush_CursorSize_bug.blend](GreasePencil_SmoothBrush_CursorSize_bug.blend)\nThank you!", "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.", "Walk navigation using tablet - repositioning the stylus rotates the view\nOperating system: Windows-10-10.0.14393-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Alpha\nWorked: unknown\n\nThis is a follow-up to #83718. Specifically addressing this comment - #83718#1075294 by @PMA33.\n\nThe problem is when using a tablet in a walk navigation, lifting and repositioning the stylus is handled as if the stylus has been moved to the new position in range. This makes the view rotate a lot, making the walk navigation only usable when the stylus doesn't leave the range height.\n\n1. In 3D Viewport execute the walk operator ({nav View > Navigation > Walk Navigation}).\n2. Use tablet to rotate view.\n3. Lift the stylus out of range.\n4. Reposition it to considerable distance and get it in range.\n\nResult: The view rotates a lot, as if the stylus has been moved to the new location.\n\nExpected: View doesn't move, new stylus location is assumed a new reference point.\n\n**Possible Fix**\n\nFirst of all, we need to reset `walk->is_cursor_absolute` when going from absolute to relative. Because currently, as long as a tablet has been used once, during the walk modal running, `walk->is_cursor_absolute` will stay absolute (even if a relative pointing device is used afterwards).\n```\ndiff --git a/source/blender/editors/space_view3d/view3d_walk.c b/source/blender/editors/space_view3d/view3d_walk.c\nindex 665d704e6b2..79f66cb9e48 100644\n--- a/source/blender/editors/space_view3d/view3d_walk.c\n+++ b/source/blender/editors/space_view3d/view3d_walk.c\n@@ -705,12 +705,12 @@ static void walkEvent(bContext *C, WalkInfo *walk, const wmEvent *event)\n }\n\n if ((walk->is_cursor_absolute == false) && event->tablet.is_motion_absolute) {\n- walk->is_cursor_absolute = true;\n copy_v2_v2_int(walk->prev_mval, event->mval);\n copy_v2_v2_int(walk->center_mval, event->mval);\n /* without this we can't turn 180d */\n CLAMP_MIN(walk->mouse_speed, 4.0f);\n }\n+ walk->is_cursor_absolute = event->tablet.is_motion_absolute;\n #endif /* USE_TABLET_SUPPORT */\n\n walk->moffset[0] += event->mval[0] - walk->prev_mval[0];\n\n```\n\nSecond we'll need a (reliable) relative position event when a tablet goes out of range so the absolute coordinates get re-centered each time the tablet goes in range. For that we can send a dummy mouse move event on WT_PROXIMITY, when not `inRange`.\n```\ndiff --git a/intern/ghost/intern/GHOST_SystemWin32.cpp b/intern/ghost/intern/GHOST_SystemWin32.cpp\nindex 7e800619dda..e375b99cb41 100644\n--- a/intern/ghost/intern/GHOST_SystemWin32.cpp\n+++ b/intern/ghost/intern/GHOST_SystemWin32.cpp\n@@ -1614,6 +1614,10 @@ LRESULT WINAPI GHOST_SystemWin32::s_wndProc(HWND hwnd, UINT msg, WPARAM wParam,\n case WT_PROXIMITY: {\n bool inRange = LOWORD(lParam);\n window->processWintabProximityEvent(inRange);\n+ if (!inRange) {\n+ /* Send a dummy mouse event to be able to detect that the tablet went out of range. */\n+ event = processCursorEvent(window);\n+ }\n break;\n }\n case WT_PACKET:\n\n```\n\nNot sure if this (second part) is an acceptable solution, maybe there's a more elegant one. Maybe @PrototypeNM1 can take a look. Also, I have no idea how this behaves on the other platforms. I tested this with WinTab only. Triaging help on other platforms is appreciated.\n\nNote that the proposed fix doesn't work well if the stylus went in range not over the Blender window. Those events may also be handled if this is a way to go.", "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" ]

[ "Surface Pen First Events in Grease Pencil\nOperating system: Windows 10 Pro\nGraphics card: Nvidia GeForce GPU (SURFACE BOOK)\n\nBroken: Blender 2.80 Beta (blender-2.80-925380050d0-win64) (, 2018-12-02 04:09, Hash:925380050d0\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\nGrease Pencil drawing, Problem with Surface Pen first events as \nDescribed previously by a developer in this video. Od5T5csS1B?amp=1\n\n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "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", "LineArt: New module to generate lines over meshes using grease pencil as target\nThis is the main Line Art task, includes the implementation of following functions:\n\n- Line Art cpu calculation code and UI.\n- Line Art modifier for Grease Pencil.\n- Other additional data structures in Object/Collection/Materials.\n", "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)", "Grease Pencil: Better render Anti-Aliasing\n## Motivations:\nThin lines are correctly rendered using grease pencil with the currently implemented post process Anti-Aliasing. This is done by making sure the line width is not less than 1.3 and by modulating its opacity.\nHowever, there is cases where this is not enough. For instance really dense drawings with small lines with little to no curvature still tends to flicker a lot.\nAnother case is when the gpencil strokes intersects the scene geometry. This makes the line less thick to the post process which makes it too small.\n\n## Proposed solution:\nWe propose to implement a Temporal AntiAliasing solution. It is robust and will match Cycles & EEVEE's film filtering if using the same filtering function. This only adds one temporary buffer (low VRAM usage compared to rendering at higher resolution) and is completely self contained (works with transparency and don't interfere with other features).\n\nI propose to only implement this for final rendering since it might introduce flickering that might be annoying while drawing.\n\nHowever this wouldn't solve the issue of gpencil strokes intersecting geometry.\nFor this I propose to erode or reproject the render's depth to match the render sample of the new AA scheme. This should fix the second problem completely.\n\n## Technical details:\n- Implementation just need to be ported from Workbench which has a lighter form of TAA than EEVEE. Also [D10414](D10414) can be of great help to reduce render/convergence time.\n- Depth buffer modification can be implemented after new AA is in.", "GPencil: Airbrush draw tool with solid stroke has transparency artifacts\nOperating system: Win 11, GTX 3080, Wacom Tablet\n\n\n\nBroken: 2cd7e70c18a8\nWorked: ~~3.3.0~~\n\nThe airbrush tool has artifacts around the stroke during drawing. Also what is drawn during stroke has nothing to do with the final result visually. Please see the video for the issue.\n\n\n\n- New scene -> 2d Animation\n- Select Airbrush tool from the tool pane\n- Switch to `solid stroke` material from header\n- Draw\n\n[image](attachment)\n[blender_lOlSgoorkK.mp4](attachment)\n", "Touch on Gizmos can return invalid cursor coordinates\nversion: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-23 21:42, hash: e5e885d0ecb9, type: Release\nbuild date: 23/12/2018, 17:14\nplatform: Windows\n\n\nWhen using a pen, as in a Microsoft Surface or similar device, using the camera Gizmos and moving the pen outside the 3D viewport seems to return null/invalid coordinates, and it breaks. They can ONLY be used inside the 3D viewport. It's an absolute deal breaker for touch screen users (Surface, Wacom, etc)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nAny default .blender. On a touch device using a stylus pen, click on a Gizmo (axis, zoom, or drag) and move the pen outside the 3D viewport.\n\n\nWhen using a regular mouse the cursor gets hidden and it works as intended.", "Grease Pencil sculpt tool affecting strokes behind camera\nOperating system: Windows 11 Home\nGraphics card: Nvidia GeForce MX350\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\nWorked: ?\n\nIf the 3D view camera has strokes in front of it (visible on screen) as well as behind it (not visible on screen), in Grease Pencil's Sculpt Mode, using the grab tool will affect not only the strokes that you can see, but also the ones behind the camera that you do not see.\n\n1. Move the Camera object to the origin\n2. Create an empty Grease Pencil object\n3. Place the 3D cursor a little bit in front of the Camera object, set the Stroke Placement to 3D Cursor and the Drawing Plane to View. Align the 3D view to the active camera object.\n4. Draw some strokes, make sure to cover a good portion of the screen. The strokes will be visible.\n5. Rotate the active camera object around the Z-axis 180 degrees. Move the 3D cursor to again be a bit in front of the camera and make sure the 3D view is aligned to the active camera object again.\n6. Draw some more strokes. They will be visible, while the strokes from before are now no longer visible since they are behind the camera.\n7. Go to Sculpt Mode and select the grab tool.\n8. Grab and manipulate some strokes that you can see.\n\nExpected outcome: only the strokes from step 6 are manipulated, and the ones from step 4 are not.\nActual outcome: both the strokes from step 6 and step 4 are manipulated.", "Decentralize .blend I/O for grease pencil modifiers.\nThis is a follow up task for #76372.\n\nFor normal modifiers this has been done already. Have a look at `ModifierTypeInfo.blendWrite` and `ModifierTypeInfo.blendRead` for more details.", "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)", "GPencil: Materials' preview thumbnails cause heavy lag when updating\nOperating system: Windows 10\nGraphics card: RTX 3070 FE\n\nBroken: 3.2.1 RC\nWorked: n/a\n\n\n\nAny action that requires the refreshing of your Grease Pencil materials' thumbnails (isolate/hide materials, etc.) causes major lag until the thumbnails are finished refreshing. The more materials your GP object has, the longer the lag. Sometimes the lag is so bad, that it makes the sound buffer skip while the thumbnails refresh.\n\n\n**Video Explanation**\nwatch?v=5KAWsJkIeRY\n\n\n**Steps to Reproduce**\nCreate a GP object and add 10-20 unique materials\nClick one of the \"Isolate Material\" buttons, and start drawing/moving strokes. You will notice extreme lag until all of the little circle thumbnails are finished updating. \n\nTest File:\n[#99361.blend](T99361.blend)", "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", "Grease Pencil export SVG / PDF - can create Incorrect Strokes, Layer order and Error\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\nWorked: n/a\n\nFirstly compliments on the work on this branch of work thus far. \n\nAll below issues noted with various attempts at PDF/SVG Exporting default Cube r/click converted to GP. PDF and SVG results appear to be similarly affected.\n\n - View from Blender\n\n - Result of SVG/PDF export\n\nnote: Frontmost and Rearmost 'panes' are both colored green\n\n***issues*:**1. Export always results in**WireFrame Stokes over Fills** (i.e. All strokes are shown on top of fills, effectively producing incorrect object occlusion)\n2. Export sometimes resulted in **incorrect Fill layer ordering** (i.e. Bottom of cube is above sides in SVG layer order)\n3. On different attempts (start from scratch) - sometimes the PDF export fails with: **ERROR: error_no=1017, detail_no=13** \n4. If I start in 3D mode. Convert cube to GP. Export in default User perspective the **resultant file is un-useable**\n\n***queries*:**\n1. Attempting to paint (tint) a single surface of the GP converted cube seems impossible - without deconstructing the cube. Otherwise the paint bleeds to any surface 'under' the tint brush. I have also tried to paint (tint) with Origin on Surface etc. Should this be possible?\n2. An unsaved document always starts export path in 'My Documents' (which seems to be true for all other export operations too). It also does not remember last save location. Seems there is no option to set default Export path (*I think*)?\n\n\nissue: 1 & 2 (*see: cubed-gp.blend, cubed-gp.svg, cubed-gp1.pdf*), 3\n - Start in 2D mode\n - Add Cube mesh object\n - R/Click convert to Grease Pencil \n - File > Export > Grease Pencil as SVG / PDF\n\nissue: 4 (*see: cubed-gp2.svg*)\n - Start in General (3D) mode\n - R/Click default cube, convert to Grease Pencil \n - File > Export > Grease Pencil as SVG / PDF\n - Result un-useable SVG/PDF (no dimensions and all point values are the same)\n\n[cubed-gp.blend](cubed-gp.blend)\n\n\n\n[cubed-gp1.pdf](cubed-gp1.pdf)\n\n\n\n\n\n", "Grease Pencil: various issues\n*Note: this tasks can be split up once we get feedback on issues, for now this is to discuss changes to make.*\n\n----\n\n\n- Brush pixels are not pixels,\n```\nshouldn't we use a meaningful value?\n(pixels or blender units).\n```\n\n- Grease pencil brushes have material pointers which are globally overwritten.\n\n```\nWhen you set a material, all brushes are looped over and have their material values clobbered.\n```\n\n```\nWhy have a material attached to the brush at all? This could be a scene level setting (or at least not stored per-brush).\n```\n\n```\nSee: `BKE_brush_update_material` called by rna `rna_Brush_material_update` when setting any material.\n```\n\n- Grease pencil sculpt uses it's own brush system,\n```\nis there a good reason for this?\n```\n\n```\nSince these brushes are fairly advanced (pressure & curve mapping options)\nwouldn't it be better to use the existing brush system?\n```\n\n *Note: while particle system for eg: has 'simple' brush types like this, grease-pencil sculpt brushes are more advanced and duplicate more of what we have for regular brushes used elsewhere.* \n\n- Grease pencil weight brush seems to have no way to paint a weight value (only add weight).\n\n```\nAs with mesh weight paint we should be able to paint a weight.\n```\n\n- In edit-mode, vertex selection exists but is hidden by default (0.0 opacity).\n\n```\nShouldn't they be visible?\n```\n\n----\n\n### Lower Priority\n\n- Internally grease pencil sculp is called:\n\n - grease pencil edit (`GP_BrushEdit_Settings`, `GP_EditBrush_Data`, `GP_BRUSHEDIT_FLAG_APPLY_UV`)\n\n```\nThis is highly confusing since we have grease pencil edit-mode, can't we rename these `GP_Sculpt*`. ?\n```\n\n - grease pencil paint (`GPENCIL_OT_brush_paint`)\n\n```\nPaint is easily confused with draw, seems this is for sculpt/weight painting.", "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)", "Tablet Pressure not working in New Window\nOperating system: Windows 10 20H1\nGraphics card: Nvidia 2070 8G\nDrawing Tablet: Huion Kamvas 16 Pro 2019\n[system-info.txt](system-info.txt)\n\nBroken: 2.92.0 and 2.93.6\n\nPen pressure not working on newly created window. Very repeatable. \n\n\n - Open Blender\n - Open Project\n - Create new Window from Main View\n - Move New window to Kamvas 16 Tablet\n - Use tablet pen to paint the mask. \n - **Pressure does not work.**\n - Verify by toggling Pen pressure button in radius and strength fields.\n - Use tablet pen again to verify\n - **Pressure still not working.**\n - Close The window on the Kamvas Tablet. \n - Move Main Window to Kamvas Tablet. \n - Use tablet pen to paint the mask. \n # Pressure is working.\n\n\nExpected behavior would be that the pressure works in the newly created window. The steps outlined above as well as the attached video evidence prove that the Tablet Pen is working In blender just not on the newly created window. \n[2021-11-23 03-52-41.mkv](2021-11-23_03-52-41.mkv)\n\n" ]

[ "Windows 10 Pen input\nWindows 10 Home build 17134\nToshiba convertible with touch/pen screen (Wacom 0x056A, 0x50A2, driver/utility 6.3.31-4 aka 7.3.4.48, wintab.dll 1.0.5.9)\n\nBroken: 2.79b f4dc9f9d68b (2.80 alpha also)\n\nGrease pencil stroke does not start on touch, but only after some time or distance (not clear)\n\nStart blender\nOpen default\nDraw with any grease pencil (radial strokes from one starting point, or zig zag lines\n\n\n**Details**\nI have been digging around a little and found a few other reports of similar issues (also see further down, some blender issue reports):\n\nstylus-delay-in-grease-pencil\npainting-problem-when-using-pen-in-blender\n\nThe latter points to controlling_pen_behavior_in_windows_10/ from March 2018 where Microsoft inform about a Windows update where a registry \"hack\" can affect (revert?) the changed behaviour (LegacyPenInteractionModel).\n\n> Controlling Pen Behavior in Windows 10\n> \n> Greetings to the Windows Ink Community!\n> \n> In response to overwhelming feedback from our Windows Insiders, the Windows 10 Fall Creator’s Update changed how the pen behaves when it isn’t doing its primary function of laying down ink. The pen now scrolls/pans content, but the previous behavior of lasso/text selection is still accessible by depressing the barrel button before making contact with the screen.\n> \n> To deliver a consistent experience we also changed the behavior for legacy Win32 applications that weren’t specifically designed for pen. These applications instead rely on Windows to convert pen input into another form of compatible input, such as mouse. While we try to test as many of the most popular applications used with pen before releasing, there is a chance that one of your favorite applications wasn’t covered as part of our validation, relies on input conversion, and may not function as intended after this change.\n> \n> While we closely monitor application compatibility issues and work with our developer community to resolve them, we understand that in the interim you need to use that app. Starting with Windows 10 build 17110, we’re putting you in control of your pen experience with legacy applications.\n> \n> By executing the following from an elevated command line, the next time any legacy application starts it will get the prior pen behavior from the Windows 10 Anniversary Update: “reg add HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Pen /v LegacyPenInteractionModel /t REG_DWORD /d 1 /f”\n> \n> Anytime you want to switch legacy applications back to the behavior introduced in the Windows 10 Fall Creator’s Update, execute this: “reg add HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Pen /v LegacyPenInteractionModel /t REG_DWORD /d 0 /f”\n> \n> The Windows Ink team is working on improving the UX for controlling this via our settings UI in a future flight and we’ll keep you posted as this progresses. We really appreciate your feedback and would love to receive more of it! For our Windows Ink fans, please check out the most natural way to enter text with your pen with inline handwriting in the latest insider builds. You can now handwrite directly in to the text boxes of UWP applications with your pen; simply tap in the text field and start writing!\n> \n>  Thanks,  David\n> \n> [email protected]\n\n\n\nHowever, this did not work for me (in addition to disable some Flick and other Pen options as well as Blender's Continuous Grab and trying newer/older Wacom divers).\nSo I can't use the pen input I'd like to use very much for Grease Pencil (unless I boot Ubuntu and do it there...).\n\nI found other reports that might be related, notably\nT55589 Microsoft Surface pens does not send first events when moves\nand others\nT53601 Microlag on tablet pc.\nT53621 Surface Book 2 pen pressure sensitivity issue\nT57151 Graphics Tablet Problem\n\n\nSo it might be that Windows broke something, but blame is not helping, so I would like to ask if someone could revisit the pen input handling to figure out the current \"state of the art\" - whether this is really a bug by Microsoft and a workaround is available or maybe some API has changed that should be supported by Blender (WinTab apparently is at V1.0.5.9). Other programs seem to have no problem with the changes - are they using a workaround or new API?\n\nOf course I'd be glad contribute mouse/touch/pen event logs etc. for my hardware if you let me know how (don't have a build environment).\n\nI was not able to find a program to test mouse/touch/pen events, but came across some API links and further bug reports.\n\nsystem-events-and-mouse-messages\n\nlistening-to-system-events\n \n> Applications can listen to system events by using the InkCollector object and listening for the SystemGesture event on it. You can set which events an application listens to. When a tablet pen action occurs, the corresponding SystemGesture event is sent to the application on its InkCollector object. An application can cancel the mouse message that corresponds to a given SystemGesture event when it receives the event. For details about canceling mouse messages, see SystemGesture event.\n\n\nflicks-gestures\n36492 Digital Pen input is interpreted as touch instead of mouse after Windows 1709 Fall Creator Update #36492\n\nupdate_fix_now_available_unexpected_application/\nadditional_control_for_pen_behavior_in_legacy/\nD8801?id=23714 WinInk: Simulate native mouse events for handled pen events (Krita)\n\n\nI will add a video/gif of the behaviour later when I get a chance." ]

[ "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", "My Blender won't open anymore\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: Every version\n\nWhen I try to open Blender the terminal appears then disappears and nothing else happens.\nBlender worked until today in all its versions, but now it no longer opens.\n\nI tried opening it as administrator, on different versions. I restarted my PC. I updated my drivers. There no bug/crash report or anything.\n\nI don't know what to do.\n\n", "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", "Crash when using OCIO v2\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.0.0 Release Candidate\n\nWhen I used OCIO v2 config file and used Cycles for rendering with Optix, it worked for viewport rendering. But if I pressed F12 for final render, Blender 3.0 crashed when the render was finsihing.\nI tried with a few scenes even if the Blender default scene still crashed. Then I tried rendering with CPU, it still crashed.\nI also tried in Blender 2.93.5. It crashed again even if the render didn't start.\nI downloaded the OCIO v2 config file from ocio_v2_demo.html.\n\nWhen I used OCIO v1.2 config file, Blender worked perfectly.\n\n[test-ocio2.txt](test-ocio2.txt)\n- Set the OCIO environment variable to the location of the test-ocio2.txt config file.\n- Start blender and set Cycles as the render engine\n- F12\n\n-----\nOCIO v2 Config\n{[F12676993](image.png) size=full}\n\nBlender 3.0 crash video\n[Crash.mp4](Crash.mp4)\n", "Blender 3.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", "Vega GPU crash during render\nOperating system: Debian 11 bullseye x86_64 Linux 5.10.0-17-amd64\nGraphics card: gfx900 AMD/ATI Vega 10 XTX [Radeon Vega Frontier Edition]\n\nHip info: \n```\n➜ blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release hipconfig\nHIP version : 5.2.21152-4b155a06\n\n== hipconfig\nHIP_PATH : /opt/rocm-5.2.1\nROCM_PATH : /opt/rocm-5.2.1\nHIP_COMPILER : clang\nHIP_PLATFORM : amd\nHIP_RUNTIME : rocclr\nCPP_CONFIG : -D__HIP_PLATFORM_HCC__= -D__HIP_PLATFORM_AMD__= -I/opt/rocm-5.2.1/include -I/opt/rocm-5.2.1/llvm/bin/../lib/clang/14.0.0 -I/opt/rocm-5.2.1/hsa/include\n\n== hip-clang\nHSA_PATH : /opt/rocm-5.2.1/hsa\nHIP_CLANG_PATH : /opt/rocm-5.2.1/llvm/bin\nAMD clang version 14.0.0 (llvm-project roc-5.2.1 22204 50d6d5d5b608d2abd6af44314abc6ad20036af3b)\nTarget: x86_64-unknown-linux-gnu\nThread model: posix\nInstalledDir: /opt/rocm-5.2.1/llvm/bin\nAMD LLVM version 14.0.0git\n Optimized build.\n Default target: x86_64-unknown-linux-gnu\n Host CPU: znver2\n\n Registered Targets:\n amdgcn - AMD GCN GPUs\n r600 - AMD GPUs HD2XXX-HD6XXX\n x86 - 32-bit X86: Pentium-Pro and above\n x86-64 - 64-bit X86: EM64T and AMD64\nhip-clang-cxxflags : -std=c++11 -isystem \"/opt/rocm-5.2.1/llvm/lib/clang/14.0.0/include/..\" -isystem /opt/rocm-5.2.1/hsa/include -isystem \"/opt/rocm-5.2.1/include\" -O3\nhip-clang-ldflags : -L\"/opt/rocm-5.2.1/lib\" -O3 -lgcc_s -lgcc -lpthread -lm -lrt\n\n=== Environment Variables\nPATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/home/ian/.local/bin\n\n== Linux Kernel\nHostname : *****Linux***** 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64 GNU/Linux\nNo LSB modules are available.\nDistributor ID:\tDebian\nDescription:\tDebian GNU/Linux 11 (bullseye)\nRelease:\t11\nCodename:\tbullseye\n```\n\nBroken: blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release\nWorked: N/A\n\nBlender crashes when attempting to render more complex scenes on Vega GPU.\n\n[lone monk demo](lone-monk_cycles_and_exposure-node_demo.blend)\n./blender ../lone-monk_cycles_and_exposure-node_demo.blend\nrender on gpu\n\n```\n➜ blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release ./blender ../lone-monk_cycles_and_exposure-node_demo.blend | tee log.txt\nRead prefs: /home/ian/.config/blender/3.3/config/userpref.blend\nRead blend: /home/ian/Downloads/lone-monk_cycles_and_exposure-node_demo.blend\nWARNING: Shader warning [node_vertex_color]: Invalid attribute.\nMemory access fault by GPU node-1 (Agent handle: 0x7f2683fa6400) on address 0x7f2400000000. Reason: Unknown.\n[1] 25965 abort ./blender ../lone-monk_cycles_and_exposure-node_demo.blend | \n 25966 done tee log.txt\n```\n\n```\n:0:rocdevice.cpp :2652: 2702732952 us: 249488: [tid:0x7f1dd0b76640] Device::callbackQueue aborting with error : HSA_STATUS_ERROR_MEMORY_APERTURE_VIOLATION: The agent attempted to access memory beyond the largest legal address. code: 0x29\n[1] 249488 abort ./blender --factory-startup --debug-all\n```", "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)", "Segmentation Fault Crashing Blender when Rendering\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.1\n\nDuring rendering, Blender will often crash with segmentation fault \"Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header\" message.\n\nNeed guidance to help provide a blend file to reproduce the issue.\n\nThe issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports. \n\nMy workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame.\n\nI believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model.\n\nGPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash.\n\nI have tested on 2 other Windows computers with the same results, so it is not Ubuntu related.\n\nOther frames render perfectly.\n\nThere is no issue with viewport render mode. Often I get \"out of memory\", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around.\n\nI have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file.\n\nN.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well.\n\nIs there any advice I can get as to how to narrow down this problem?\n\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "Blender stops updating display after GPU spike\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 2.92.0 Beta\nWorked: I have not found a version that works as expected on this computer. I have tried 2.79, 2.8, 2.91\n\nI was premature in saying the problem is gone for [#85061 ](T85061).\n>After a few minutes of using Blender, the window freezes. Windows does not detect that it is not responding, but Blender does not respond to any input, including clicking on the close button. All elements that are drawn by Blender remain as they were at the moment of the crash except if I resize the window smaller.\n\nIf I watch the performance tab on Windows Task Manager, the freeze coincides with a 100% spike on the GPU.\nAs long as that spike doesn't happen, there is no problem, but once it does, Blender stops responding to any input, but it does not crash.\nI have updated my graphics drivers.\n[blender_debug_output.txt](blender_debug_output.txt)\n\nI have not determined exact steps. It has occurred on multiple files doing multiple different tasks. As far as I can tell, there is no correlation between what I am working on or what task I am performing, and the error occurring.\n", "Crash when deleting ViewLayer while rendering\nOperating system: Linux-5.4.0-66-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.92.0\n\nA crash will happen when deleting a ViewLayer while rendering stills or animations, for any render_display_type\n\n- In the default scene, add a new ViewLayer\n- Set the renderer to Cycles so that you can see the render progress. In Eevee you could set up a little animation to get the same problem.\n- Start a normal render\n- While Blender is still rendering, delete the new ViewLayer that you just added and that was being in use when the render process was called\n- A crash happens with a Segfault, even after some time.\n\nThis problem looks to me as just an unhandled context change, because I noticed that if you delete the current scene or the current camera used while rendering animations, those context changes are appropriately handled and the render process is effectively stopped without a crash.\n", "Crash - 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 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)", " 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)", "Blender crashes with Segmentation fault when selecting Render Preview in Cycles with GPU Compute\nOperating system: Linux-6.1.46-gentoo-gentoo-dist-x86_64-12th_Gen_Intel-R-_Core-TM-_i3-12100F-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 6400 (navi24, LLVM 16.0.6, DRM 3.49, 6.1.46-gentoo-gentoo-dist) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 3.6.0\nWorked: - (read description)\n\nWhen I try to render using Cycles on my GPU, blender immediately crashes with Segmentation fault, as the error message. Here are the logs that were shown right before the Segmentation fault:\n```\nI0903 17:06:40.864868 14239 device.cpp:511] Mapped host memory limit set to 12,302,073,856 bytes. (11.46G)\nI0903 17:06:40.865039 14239 device_impl.cpp:62] Using AVX2 CPU kernels.\nWriting: /tmp/blender.crash.txt\nzsh: segmentation fault blender-3.6 --debug-all\n```\nIt worked with =dev-libs/rocm-comgr-5.3.3-r2, but started happening after the new update of the package. I used to apply a patch that solved the problem of being unable to select the render device in Blender's options (27552#issuecomment-1379233453), but with the new rocm-comgr package, the original problem solved itself. The old version of Blender (version 3.5.1) that worked before rocm-comgr got the new update, doesn't work now.\n\n1. Open the Render properties tab and set the Render Engine to Cycles.\n2. Set the device to GPU Compute.\n3. Set the viewport shading to Rendered.\n\n" ]

[ "OpenCL RX Vega 56 Cycles Render Problem \"Split kernel error: invalid ray state\"\nOperating system: Windows 10 \nGraphics card: RX Vega 56 - Radeon Software Ver. 21.2.2\nBlender 2.92\n\n\nBlender crash when trying to render one of my project.\nThe crash happen on Cycles Render and GPU Compute. The error says:\nSplit kernel error: invalid ray state\n\n\nRendering project below using Cycles Render and GPU Computer.\nThe render start couples tiles, and then stop working\nThe error show up", "Cycles! Not Loading Kernel! 2.91!\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.Q4 27.20.11027.5002\n\nBroken: version: 2.91.0\nWorked: (Don't know)\n\nCycles not loading, i was just trying to see how was it with the pro drivers and doesn't load, before i could even start it and when rendering was crashing the whole software and hardware. \n\nChange To OpenCl render in the preferences\nChange to gpu compute in Cycles menu\nGo to Viewport Shading. \n\n\n", "RX 570 problem with Cycles\nOperating system: Windows 10\nGraphics card: AMD RX 570 4GB\n\nBroken: 2.92.0\nWorked: haven't tried older version\n\nI enabled my Graphics Card in preference - system settings, but then when I switch the renderer to Cycles and change CPU to GPU Compute and render or change the viewport shading to rendered, the Blender stopped responding until it crash.\n\nBased on the default startup with just enabled GPU in System Preference", "GPU Compute with OpenCL in Cycles: Crash or Freeze\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 3 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.28 27.20.1028.1\n\nBroken: version: 2.93.0 Alpha\n\nFor my graphics card, \"GPU Compute\" is Greyed out for Cycles except I have 2 options in Edit > Preferences > System > Cycles Rendering Devices > OpenCL.\n* AMD Radeon Vega 3 Graphics\n* AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx\nOnly checking the box for the first option (\"AMD Radeon Vega 3 Graphics\") un-greys out the GPU Compute option.\nI have successfully rendered in Cycles (F12) with OpenCL and this graphics card, but never had a successful use of Render Mode in Viewport.\n(However I have also had crashes/freezes with a regular Render)\n\nMost often I get:\n**Split kernel error: failed to load kernel_indirect_background**\nAnd then the cube becomes monocolor grey but I can still move around the viewport.\nAnd then Blender hangs/freezes when I try to switch Viewport Shading.\n(But also sometimes just crashes)\n\nBut also:\n**Split kernel error: failed to load kernel_path_init**\n\nSometimes:\n**OpenCL error (-6): CL_OUT_OF_HOST_MEMORY**\nOpenCL: Error creating command queue\nOpenCL error: CL_INVALID_COMMAND_QUEUE in clEnqueueWriteBuffer(cqCommandQueue, CL_MEM_PTR(mem.device_pointer), CL_TRUE, 0, mem.memory_size(), zero, 0, NULL, NULL) (C:\\b\\buildbot-worker-windows\\windows_291\\blender.git\\intern\\cycles\\device\\opencl\\device_opencl_impl.cpp:1083)\nOpenCL: failed to initialize device.\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7D8CCC6A2\nModule : blender.exe\nThread : 00001128\nWriting: XXXXXXXXXXXXXXXXXX\\blender.crash.txt\n\n/# Blender 2.93.0, Commit date: 2021-01-17 11:35, Hash 4ef0654449e9\nbpy.context.space_data.context = 'RENDER' # Property\nbpy.context.scene.render.engine = 'CYCLES' # Property\nbpy.context.scene.cycles.device = 'GPU' # Property\nbpy.context.space_data.shading.type = 'MATERIAL' # Property\nbpy.context.space_data.shading.type = 'RENDERED' # Property\nbpy.context.space_data.shading.type = 'SOLID' # Property\nbpy.context.space_data.shading.type = 'RENDERED' # Property\nbpy.context.scene.cycles.preview_pause = True # Property\n\n/# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF6C008F910\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters- [x] : 0x0000000000000000\n\tParameters- [x] : 0xFFFFFFFFFFFFFFFF\n\n\nStack trace:\nblender.exe :0x00007FF6C008F7D0 ccl::OpenCLDevice::~OpenCLDevice C:\\blender-git\\blender\\intern\\cycles\\device\\opencl\\device_opencl_impl.cpp:710\nblender.exe :0x00007FF6C00A2F10 ccl::OpenCLDevice::`scalar deleting destructor'\nblender.exe :0x00007FF6C0089980 ccl::MultiDevice::`scalar deleting destructor'\nblender.exe :0x00007FF6C049F8E0 ccl::Session::~Session C:\\blender-git\\blender\\intern\\cycles\\render\\session.cpp:125\nblender.exe :0x00007FF6C0013EA0 ccl::BlenderSession::~BlenderSession C:\\blender-git\\blender\\intern\\cycles\\blender\\blender_session.cpp:117\nblender.exe :0x00007FF6C000F070 ccl::free_func C:\\blender-git\\blender\\intern\\cycles\\blender\\blender_python.cpp:273\npython37.dll :0x00007FFDDB166EE0 PyMethodDef_RawFastCallKeywords\npython37.dll :0x00007FFDDB233FA0 PyEval_GetFuncDesc\npython37.dll :0x00007FFDDB22E490 PyEval_EvalFrameDefault\npython37.dll :0x00007FFDDB1664E0 PyObject_Call\npython37.dll :0x00007FFDDB1669C0 PyFunction_FastCallKeywords\npython37.dll :0x00007FFDDB233FA0 PyEval_GetFuncDesc\npython37.dll :0x00007FFDDB22E490 PyEval_EvalFrameDefault\npython37.dll :0x00007FFDDB1664E0 PyObject_Call\npython37.dll :0x00007FFDDB1C6D00 PyType_Ready\npython37.dll :0x00007FFDDB1A5950 PyObject_CallFinalizer\npython37.dll :0x00007FFDDB1BE3F0 PyType_GenericNew\nblender.exe :0x00007FF6BF7304C0 BPY_DECREF_RNA_INVALIDATE C:\\blender-git\\blender\\source\\blender\\python\\intern\\bpy_interface.c:544\nblender.exe :0x00007FF6C2A59090 RE_engine_free C:\\blender-git\\blender\\source\\blender\\render\\intern\\engine.c:151\nblender.exe :0x00007FF6BFB96BB0 ED_view3d_stop_render_preview C:\\blender-git\\blender\\source\\blender\\editors\\space_view3d\\space_view3d.c:240\nblender.exe :0x00007FF6BF68EED0 rna_3DViewShading_type_update C:\\blender-git\\blender\\source\\blender\\makesrna\\intern\\rna_space.c:1052\nblender.exe :0x00007FF6BF62F1F0 rna_property_update C:\\blender-git\\blender\\source\\blender\\makesrna\\intern\\rna_access.c:2255\nblender.exe :0x00007FF6BF62C070 RNA_property_update C:\\blender-git\\blender\\source\\blender\\makesrna\\intern\\rna_access.c:2320\nblender.exe :0x00007FF6BFA60A90 ui_apply_but_funcs_after C:\\blender-git\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:947\nblender.exe :0x00007FF6BFA6F1C0 ui_region_handler C:\\blender-git\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:10723\nblender.exe :0x00007FF6BF2EF470 wm_handlers_do_intern C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2778\nblender.exe :0x00007FF6BF2EEAC0 wm_handlers_do C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2889\nblender.exe :0x00007FF6BF2EBFE0 wm_event_do_handlers C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3385\nblender.exe :0x00007FF6BF2D7940 WM_main C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm.c:638\nblender.exe :0x00007FF6BEFC9C70 main C:\\blender-git\\blender\\source\\creator\\creator.c:527\nblender.exe :0x00007FF6C34CE5D8 __scrt_common_main_seh d:\\A01\\_work\\6\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\n\n\n", "Split kernel error: failed to load kernel_lamp_emission on 2.93+\nOperating system: Linux Mint 20.1 Cinnamon, Linux-5.4.0-72-generic-x86_64-with-debian-bullseye-sid 64 Bits \nGraphics card: AMD Radeon RX 570 Series ATI Technologies Inc. 4.5.14735 Core Profile Context 21.10 (Driver: amdgpu 21.10)\n\nBroken: version: 2.93.0 Beta, 3.0.0-932b23782a5e\nWorked: 2.83.13 LTS, 2.83.14-d35974cd870b, (all previous LTS at this date)\n\nWhen trying to switch to Viewport Rendering/Viewport Shading on versions 2.93+ it throws the said error (Split kernel error: failed to load kernel_lamp_emission)\n\n1) Open Blender\n2) Go to \"Render Properties\" and switch the engine to Cycles\n3) Switch the \"Device\" option to GPU Compute\n4) Make sure your graphics card is selected and enabled on Preferences > System\n5) Switch to Viewport Shading or start a normal rendering of the actual default cube\n6) After a couple minutes while compiling the render kernels, Blender should throw \"Split kernel error: failed to load kernel_lamp_emission\" like in the following image:\n\n\n\n- Full Rendering by pressing F12 works fine without issues\n- On Blender 2.92 this issue doesn't takes effect, instead it throws a Segmentation Fault using the same steps, issue regarding this version reported [here ](T87724)\n- All LTS versions of Blender at this date runs fine without these problems at all.\n- I don't have a Windows PC with me right now for test, might update in a while if this happens on Windows versions\n- If you attempt to close Blender when this error appears, it hangs forever, forcing a close using the terminal.\n\nHere's my system-info.txt:\n[system-info2.93.txt](system-info2.93.txt)\n\nAnd the console dump if it's useful (made using the args --debug and --debug-cycles)\n[blenderconsoledump2.93.txt](blenderconsoledump2.93.txt)\n", "Blender Cycles Died: Split Kernel Error still happens after the last Blender update\nOperating system: Windows 10 1909\nGraphics card: AMD RX 570 (driver version: 20.11.2 - recommended version by AMD)\n\nBroken: All versions after 2.83.5\nWorked: 2.83.5\n\nAfter the Eevee update, the Blender Cycles cannot use any GPU core of the AMD Graphics Cards.\n\n\nJust try to render using cycles using an AMD Graphics Card. The Blender will show this error, freeze, consume 16GB of Memory ram, and crash\n\n\n\n\n\n", "Cycles: Split kernel error with OpenCL\nOperating system: Windows 10\nGraphics card:\n - Radeon RX 570 Series\n - RX480 8G, 20.2.2 driver version\n - Radeon RX550/550 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.Q4 27.20.11027.5002\n\nBroken: 2.91.0, 2.92.0\nWorked: ?\n\nGPU rendering fails with a split kernel error and often in combination with an OpenGL shader compilation issue due to seemingly incorrect reported extensions by the device.\n\n- Configure the user preferences to use *OpenCL*\n- Set the *Device* to *GPU* in the *Render Properties*\n- Either set the *Viewport Shading* to *Rendered* or render the scene {key F12}", "Blender Kernel issues with GPU Compute\nOperating system: Windows 10\nGraphics card: Radeon Pro WX 5100\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nKernel errors when switching to GPU Compute\n\nBased on the default startup or an attached .blend file (as simple as possible).\nSwitch to GPU Compute\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)" ]

[ "Modal keymap for snapping in the `Corner Pin` widget has no effect\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nThe bottom bar states that pressing ^ will enable snapping, but it seems it does nothing.\n\n\n\n1. Create a new default file;\n2. Go to the compositor;\n3. Enable nodes;\n4. Add a viewer node (this allows you to resize and test different sizes for the `Corner Pin` Gizmo);\n5. Add a `Corner Pin` node;\n6. Edit the `Corner Pin` widget and try to snap.\n", "Wireframes aren't displayed in Edit Mode when Overlays are off. \nBroken: 2.82a, 2.83, 2.90 alpha\nWorked: 2.81a\n\nWireframes aren't displayed in Edit Mode if Overlays are turned off, but they're only shown in object mode, or if there's a modifier with \"display in edit mode\" option. \n\nOpen default file.\nChange to wireframe mode.\nturn off overlays.\nchange to edit mode. Wireframe won't be shown.\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).", "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)", "Measure Tool Todo's\n\n- #69660 (Measure tool thickness option exposed in the UI)", "Impossible to use any other mouse button than MMB to navigate in Knife tool mode\nOperating system: Windows 10\nGraphics card: GTX1080Ti\n\nBroken: 2.8 latest master\nWorked: Probably never\n\nThe way Knife tool mode is executed makes it impossible to navigate 3D viewport in the Knife tool mode as long as navigation buttons are mapped to any other key than middle mouse button (MMB). This does not interfere with default Blender kemap, where Orbit (Rotate), Pan and Zoom viewport navigation actions are mapped to MMB, but doesn't allow viewport navigation in the other custom keymaps, including the proposed industry compatible one: T54963 \n\nThere is no combination of settings in Knife Tool Modal Map section which would allow to solve this issue and make non-MMB based viewport navigation function in Knife tool mode.\n\n\n1, In factory default setup Blender, got to edit mode of the default cube, activate Knife tool using K key, and notice MMB to orbit, Shift+MMB to pan and Ctrl+MMB works.\n2, Go to User Preferences, Keymap section, and in 3D View>3D View (Global) \n3, Change Rotate View from Middle mouse to Alt+Left Mouse and change the action type from \"Press\" to \"Click-Drag\" (To distinguish from Alt+LMB click, which selects edge loops)\n4, Change Zoom view from Ctrl+Middle Mouse to Alt+Right Mouse\n5, In 3D viewport, notice that Alt+LMB and Alt+RMB work correctly to activate Viewport Rotate and Viewport Zoom respectively\n6, Enter Knife tool mode, and notice that Alt+LMB and Alt+RMB do not work to Rotate or Zoom the viewport.\n7, In Keymap editor, under 3D View>Knife Tool Modal Map, notice there is no possible setup to make these new navigation hotkeys work.\n\nResult: There is no way to configure Knife Tool Modal Map so that viewport navigation in Knife Tool Mode works with any other mouse buttons than MMB.\n\nExpected: It is possible to configure Knife Tool Modal Map so that it works with non-MMB based viewport havigation configuration.", "Wireframe opacity doesn't work if object is \"in front\" and viewport shading is set to material preview or rendered.\nBroken: 3.0\nWorked: \n\nWireframe opacity slider doesn't work if the object is \"in front\" and \"texture space\" is checked and viewport shading is set to material preview or rendered.\n\nSelect Cube\nObject properties-> viewport display -> in front ON\nObject properties-> viewport display -> texture space ON\nIn the viewport overlay panel, drag the wireframe opacity to lower the value.\nchange the viewport shading to preview or rendered, wire will have full opacity.", "Node search: Arrow cuts off when highlighting\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 532.03\n\nBroken: 3.0, 4.0\nWorked: never\n\nIn nodes search panel, arrow is partially visible on the hovered element\nThis is due to overlapping as Harley mentioned in: 112183#issuecomment-1017576: [image](blenderattachment)\n\n- Open GN workspace\n- add node tree\n- F3 to open search panel,, notice the arrow of highlighted element\n\n\n", "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.", "keyboard shortcut to switch between vertex / edge / face not present in tooltip\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nI rely on the tooltips to learn keyboard shortcuts.\nWhen hovering above the vertex / edge / face select button, the shortcut to enable this button is not mentioned.\nexpected: \nVertex Select: 1\nEdge Select: 2\nFace select: 3\n", "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", "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)", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "Inset operator modal handling misses option to toggle \"Offset Even\" via shortcut\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nNoticed problems when using Inset Faces tool in Edit Mode. If I'm using the select tool and I press **I** to activate the tool Inset Faces tool its menu doesn't display anywhere so I can't choose Even for example. If I click on the tool icon then it works, even if I then use **I** to activate the tool. This makes it so I can't use shortcut keys anymore. I suspect this is happening with other tools as well. Another thing worth noting is that the status bar says the Call Menu is triggered by the right mouse button but it actually just closes the tool.\n\n\n\n\n\n\nGo into edit mode with the default cube. Select a face. Hit I to activate the inset faces tool. Notice that the options for the tool aren't available.\n\n", "Offset Edge Tool Menu Rescaling Makes It Impossible To Use\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.3 26.20.13025.1004\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nName: Edit Mesh Tools (0, 3, 6)\nAuthor: Meta-Androcto\n\nThe tool menu ad the bottom left of the viewport pops between sizes making it impossible to use\n\nselect edges, use the offset edge with extrude option.\nopen the tool menu in bottom left of 3D viewport, then switch between Angle or Depth option a few times.\nNow hovering over either the Depth or Angle button will trigger it and rescale the menu. This moves the other button up making it impossible to select.[edit menu pops up and down.mp4](edit_menu_pops_up_and_down.mp4)\n\n\n" ]

[ "Tools don't have a way to snap to geometry before they're activated (knife)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen the Knife tool is active, before starting cutting, the tool does not snap to points or edges. Although the snapping works, if you activate the tool using the K key.\n\nIn Edit Mode activate Knife Tool on T-panel. Start cutting from some point. Snapping doesn't work.\n\n", "Knife Tool. No preview dot of where the cut will start.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nWhen activating a knife tool, the preview dot of where the cut will begin does not show up. So i do not know if the cut will begin on a face, or on an edge, and i can't see if it snaps to a vertex, etc. I can see all of this only when i actually begin a cut. \nA desirable behavior is when i activate a knife operation with \"k\" key. \n\nCreate a cube. Enter edit mode. Select a knife tool. Point it on a mesh. There is no green dot projected on mesh, indicating where the cut will start.\nOn the other hand, when in edit mode, press \"k\" and you immediately see where the cut will start, and if ctrl is pressed - to which place it snaps.[Knife_Tool_cube.blend](Knife_Tool_cube.blend)\n\n" ]

[ "Make Thumbnail Dragging More Reliable\nOn some systems, the dragging is very glitchy and keeps invoking box selection instead.", "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", "UI bug in preset window after repeated remove\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0\n\nWhen you remove a preset the textfield with the +/- moves one entry up\n[2022-07-15 09-17-07.mp4](2022-07-15_09-17-07.mp4)\n\n1. Go to the scene tab\n2. Create several new presets\n3. Remove all the new created presets in one go without moving the mouse away.\nI think the textfield with the +/- moves should just stay at the bottom and the window should shrink from the top.", "Bone Selection with \"select box \" Inconsistent\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 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: never before has this ever worked correctly.\n\nWhen box selecting multiple bones in edit mode and they occlude each other making impossible to select all of the ones you need only allowing you to switch to other selection modes like circle select or lasso select.\n\nOpen a character with multiple bones mounted onto each other.\ngo into edit mode\ntry to select a large group of bones via box select\nresult: some get selected some not, no matter how many times or different angles you try.\n\nnote: Lasso picks up all of them afaict\nnote: this also seems to work better in posemode\n[#80296.blend](T80296.blend)\n\nHere is a gif depicting the issue.\n\n\n\n\n", "Blender 2.8 Small but really anoing bug when you save rendered images. Cursor shift his position\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 74)\nWorked: (optional)\n\n\nWhen I rendering more then 1 image in same folder, I found that if you will have touch any file (filename) inside explorer - the main string will turn to red (it's normal), but at same time will occure a bug that change mouse position down to 1 string (and it save to all save-explorer menu folder). And it really anoing.\nMaybe will be usefull: 1 - save menu always opens fullscreen, bacause I usual render big size images. 2 I use tablet (Wacom Intous Touch S)\nHere is how it's looks like briefly: a9f6df16ce40e492e4440f6db621dfa9.mp4\nMore closely with my explanation and thoughts what was the reason of this bug: [2019-07-17 02-32-39.mov](2019-07-17_02-32-39.mov)\n\nOpen file. [BUG.blend](BUG.blend) Then press \"F12\". Then \"Shift+S\". In explorer menu create new Folder, and type name \"1\" and press at any empty space. And then press Enter (it will same as you will press \"Save As Image\" effect) Then press Esc, to quit from Render Result Vindow. And repeat all this again, but change each time name to 2,3..ect. \nAnd at some moment (usually it close to \"5\") you will see how render output image will slightly changed, like this: L21z04wuRV9klA.jpg \nAnd that will be mean that bug appeared. And when you will open Save As (SHIFT+S) menu, you will find that cursor position shifted down to 1 string. And you can't normally type anything or select anything. Only when you will maimize windows - it will bring to normal.\n\n", "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.", "Visual bug when using strenght tool in 3D space left for Tool Panel\nOperating system: Windows 10 64Bit\nGraphics card: Nvidia GTX 960M\n\nBroken: 2.80 RC\n\nVisual bug in Sculpt mode, Vertex Paint, Weight paint and Texture paint\n\n1. Go to Texture Paint mode\n2. Set strength tool to 1.0 (shift F)\n3. Use strenght tool hotkey (Shift F) in the narrow 3D space left for the Tool Panel\n\n", "Cursor's icon doesn't update correctly when going from panel to scene\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.2.0 Alpha\nWorked: Never (introduced/discovered with new design for 2.8 series)\n\nThe cursor icon doesn't update properly when returning it to the scene fast enough after tweaking in panels, and on it's way passing over text panels.\n\n- Go edit mode and select a vertice/edge/face to activate the transform panel\n- Place the cursor in the panel where its icon displays the OS default one\n- Move the cursor fast enough onto the scene. On its way pass over text panels.\n- The cursor icon is the default's one, not the cross as it should.\nSee the .gif for visual explanation:\n", "\"Loop Cut and Slide\" requires to click anywhere first (different from loop cut)\nOperating system: Windows 10 64bits\nGraphics card: RTX 3070\n\nBroken: Blender 3.1\nWorked: Blender 2.93.6\n\nBehavior changed in f8b51f702c\n\n\nCalling for \"Loop Cut and Slide\" won't start previewing the possible cuts until a first left click is made anywhere on the viewport. This behavior is different from the \"Loop Cut\". It is a very small thing, but it is getting anoying.\n\n - Enter edit mode on the default cube.\n - Search and activate the operator \"Loop Cut\". It will show possible cuts immediately.\n - Search and activate the operator \"Loop Cut and Slide\". It won't show any possible cut until a left click.\n\n[2022-03-21 16-25-50.mkv](2022-03-21_16-25-50.mkv)", "Continuous Grab doesn't work with tablet on Linux\nOperating system: Manjaro Linux\nGraphics card: Nvidia GeForce GTX 750 Ti\n\nBroken: 2.92 and 2.93\nWorked: 2.93 on Windows\n\nContinuous grab function doesn't work with a tablet\n\nHave a tablet set to Relative Mode (Mouse mode). Select the cube. Press G and move the cursor to the edge of the screen. On linux with a tablet the cursor and the cube will stop at the edge of the screen but with a mouse (and with a tablet on Windows) you can keep moving them. Same thing happens when scrolling the menus with the middle mouse click (for example in outliner)\nPlease watch the video. I demonstrate the issue in the 3D viewport, as well as in the blender preferences menu\n[2021-06-20 12-55-33.mp4](2021-06-20_12-55-33.mp4)", "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)", "Animation (e.g. driver) jumps to another socket, when i move input socket in the node group.\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.3.0\n\nOpen file, try to move Scale input socket upper. Driver will jump to Scale socket\n[driver jumps.blend](driver_jumps.blend)\n\n[2022-09-24_22-56-08.mp4](2022-09-24_22-56-08.mp4)\n", "NLA: Moving Strips Auto Changes Between Hold and Hold_Forward\nBug Report #42808 (NLA: Moving one strip resets extrapolation on other strip) #45854 (Hold forward is reseted in NLA)\n\n**Source of Problem**: #42808#843296 \n\n**Solution:** I think the code enforcing this can be removed. I don't think this restriction was ever necessary. When an animator uses a Full Replace Hold strip above other strips, it's expected behavior that it occludes the lower strips. That's what a Full Replace strip is supposed to do. Full means strip influence = 1. For consistency, we'll have to add support when a strip has extrapolation `None` leading to a strip with `Hold`. We'll also have to add support for `Hold_Backwards` extrapolation for completeness. In the case of conflicting adjacent strips (`Hold` into a `Hold`), we let the first strip have priority which leads to the next strip as behaving as `Hold_Forward`.\n\n**Potential Problems with Solution:** \n- When two adjacent strips have `Hold` extrapolation, which should evaluate? It seems natural to let only the preceding strip evaluate.\n- When a strip has `Hold_Forwards` extrapolation and the next has `Hold_Backwards`, which should evaluate? Here, I think we should still let only the preceding strip evaluate, for consistency with the previous point. \n\n____\n\n**Implementation/Patches**\n[D9942: NLA: Remove Hold resetting between Hold_Forward Behavior](D9942) \n[D9943: NLA: Strip Evaluate Held Strips Even When Not First Strip](D9943) (depends on previous patch)\n(todo) Patch3: Add `Hold_Backwards` support. Unsure about whether this is actually useful. Maybe we should wait till there is a concrete use-case for it? \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)", "Modifying keymap produces unreliable results when duplicate entries exists\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken: 2.83-3.0\n\nModifying keymap produces unreliable results when duplicate entries exists.\n\n**Steps to reproduce**\n1. To create duplicate keymaps apply patch \n[P2817: (An Untitled Masterwork)](P2817.txt)\n```\ndiff --git a/release/scripts/presets/keyconfig/keymap_data/blender_default.py b/release/scripts/presets/keyconfig/keymap_data/blender_default.py\nindex 5fb0f052154..ad335883afa 100644\n--- a/release/scripts/presets/keyconfig/keymap_data/blender_default.py\n+++ b/release/scripts/presets/keyconfig/keymap_data/blender_default.py\n@@ -2758,20 +2758,28 @@ def km_sequencercommon(params):\n def km_sequencer(params):\n items = []\n keymap = (\n \"Sequencer\",\n {\"space_type\": 'SEQUENCE_EDITOR', \"region_type\": 'WINDOW'},\n {\"items\": items},\n )\n\n items.extend([\n *_template_items_select_actions(params, \"sequencer.select_all\"),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n+ {\"properties\": [(\"type\", 'SOFT')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n+ {\"properties\": [(\"type\", 'HARD')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n+ {\"properties\": [(\"type\", 'SOFT')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n+ {\"properties\": [(\"type\", 'HARD')]}),\n (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n {\"properties\": [(\"type\", 'SOFT')]}),\n (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n {\"properties\": [(\"type\", 'HARD')]}),\n (\"sequencer.mute\", {\"type\": 'H', \"value\": 'PRESS'},\n {\"properties\": [(\"unselected\", False)]}),\n (\"sequencer.mute\", {\"type\": 'H', \"value\": 'PRESS', \"shift\": True},\n {\"properties\": [(\"unselected\", True)]}),\n (\"sequencer.unmute\", {\"type\": 'H', \"value\": 'PRESS', \"alt\": True},\n {\"properties\": [(\"unselected\", False)]}),\n\n```\n \n\n2. Remove shift modifier key from all `sequencer.split` keymap entries\n - First time this works, after that entries will be removed\n3. Try to set Shift modifier key for last `sequencer.split` keymap entry.\n - This sets Shift modifier key on first `sequencer.split` keymap entry.\n4. Try to set Shift modifier key for second `sequencer.split` keymap entry. (Type is Hard)\n - This entry will jump to bottom and it is last entry now.\n" ]

[ "Continuous Grab occasionally jumping when going across region border at high mouse polling rate\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.74\n\nBroken: version: 2.83 (sub 13)\n(broken since at least 2.6x, as long as I've used Blender)\n\nWith continuous grab enabled and mouse set to a high polling rate, the view occasionally jumps looping over the region border. At 1000hz it renders continuous grab nearly ununsable, and I can't reproduce at all at 125hz. Supposedly doesn't happen on Linux. Tested both on my main 144hz monitor and secondary 60hz, problem seems to be only related to mouse polling rate.\n\n1. Set mouse polling rate to 1000hz. If you cannot adjust the polling rate, don't expect to be able to reproduce.\n2. Open the shading tab\n3. Pan the node area with MMB\n4. Quickly wiggle the mouse so that it crosses the border and loops back around\n\nSee video: \n\n[HHhX8reola.mp4](HHhX8reola.mp4)", "Modifying property with continuous drag jumps to the wrong value\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.92.0 Alpha, ranch: master, commit date: 2020-12-22 04:50, hash: `9f34f2b20d`\n\n- Place the mouse cursor over any property, press the left mouse button and drag to the right\n- Let the mouse button go\nThe resulting value is not where the mouse was let go.\n\n[CD value issue.blend](CD_value_issue.blend)\n\n[2020-12-27_08-18-24.mp4](2020-12-27_08-18-24.mp4)\n\n" ]

[ "Inconsistency in the behavior of 'Jump to next/previous keyframe' operator\nOperating system: Linux-5.4.0-124-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.3.0 Beta, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: as far as I know, none.\n\nWhen calling the 'Jump to next/previous keyframe' operator, there are inconsistency of behavior depending whether the active object is a Grease Pencil one or not.\nFor standard keyframes, it jumps to next keyframe if the object is active, regardless of if the object or any of its channels are selected.\nFor grease pencil layers keyframes, it jumps to next keyframe only if the layer channel is selected.\n\nReproduce the bug :\n - Open a new blender file,\n - Add one grease pencil object with two keyframes,\n - Add one 3D mesh (for example) with two keyframes (at different frames than the grease pencil ones),\n - Try to jump to next or previous keyframes, standard shortcut : up/down arrow in the viewport.\n\n[issue_jump_to_next_keyframe.mp4](issue_jump_to_next_keyframe.mp4)\n\n", "GRAB_CURSOR bl_option stops working as soon as modal operator returns PASS_THROUGH the first time\nOperating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67\n\n\nBroken: version: 2.80 (sub 57)\n\n\nUsing the `GRAB_CURSOR` bl_option in a modal operator, works fine until the operator returns `PASS_THROUGH` the first time - for instance, to adjust the viewport using `MIDDLEMOUSE`, while the modal is active.\nAfter the first `PASS_THROUGH` the cursor is no longer warped to the opposite side.\n\n\n* open attached blend file\n* run the script\n* in the 3d view, look for 'GrabCursorBug' operator in the search menu and run it\n* move the mouse horizontally across the region borders, notice how it warps to the opposite side accordingly\n* hold down `MIDDLEMOUSE` and move the mouse to adjust the viewport, release again\n* try moving the mouse across the region borders again, it won't warp to the other side anymore\n\n[video demo ](watch?v=liPmg5Z_hCk)\n[grab_cursor.blend](grab_cursor.blend)\n\n\n", "Quad View Exiting Behavior\nUsers coming from other software expect Quad View to behave a certain way. Since d71db08f6d, when exiting Quad View we always toggle to the *User Perspective* (top right) view, rather than the one the mouse currently hovers. That differs from what users probably expect (see #43523, #42462, #42368, #43452, #69717).\nIt should not be hard to get the (presumably) expected behavior to work again while addressing the reasons it was removed.\n\nQuick proposal:\n* Maximize the hovered view when exiting Quad View\n* Keep rotation of that view locked if it wasn't the *User Perspective* one\n* Keep the view transform of the *User Perspective* stored so when going back to Quad View, it shows that in the top right.\n\nFor more details, see d71db08f6d.", "Regression: Child hair particles set to \"Interpolated\" causes jittering when the based vertex changes position\nOperating system:win10\nGraphics card:RTX3060ti\n\nBroken: c8c6f62cf3a3,fca8df9415\nBroken: 3.5\nWorked: 3.4\n\nCaused by d20f9923224d2637374dd4390ae84c5041e3f9d3\n\nChild hair particles set to \"Interpolated\" causes jittering when the based vertex changes position\nThis problem seems to have been solved before,in #63534 and #56408\n\nOpen the file and render animation\n\n", "Mesh selection in viewport broken with scenes using a high number of models\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.5.0 Alpha\nWorked: Never (2.8+)\nWe are working on a commercial project with imported SketchUp scenes using 55K+ models and running more and more into broken scenes with selection issues in the viewport.\n\n`What we figured out so far:`\n- Selection in the outliner works\n- Some models can be selected by a point and click\n- Other models can't be selected by a point and click\n- Models at a different location will be selected by a point and click and not at the mouse pointer location\n- Box select is messed up and doesn't work overall (selects just parts of the model or fails completely)\n- Lasso select seems to work as intended\n- Circle select seems to work as intended (but can freeze Blender)\n- Some random models can cause a hard crash of Blender when selecting them by a point and click\n**When we delete all my other scenes in the Blender file and purge the data the selection modes work again.**\n\n\n\n\n[T104008_Selection_Bug_350_v006_CUBES_REPORT.blend](T104008_Selection_Bug_350_v006_CUBES_REPORT.blend)\n\nTry to select cubes.\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. ", "The viewport may update at 0 FPS while navigating, until the mouse is released.\nOperating system: Windows 10\nGraphics card: RTX 3080 Ti\n\nBroken: 3.0.0\nWorked: 2.92.0\n\nWhen working in sculpt mode on a model with multires modifier, the viewport may update at 0 FPS while navigating, until the mouse is released.\n\nUsually when navigating in sculpt mode on a model with multires modifier, the model will switch to a low poly version while navigating. When this bug is happening, the viewport remains frozen and the high poly model remain on screen until mouse is released.\n\nThe bug will be temporarily fixed upon clicking on another application or resizing the blender window.\n\n1. Shift+A to create a plane\n2. Ctrl+E and subdivide it 4 times.\n3. Attach multires modifier onto the plane.\n4. Subdivide it 6 times with the multires modifier.\n5. Use sculpt mode and sculpt without moving the view for around 1~2 minutes (I used a wacom tablet. Using the sculptDraw brush, I added / subtracted (hold ctrl) from the mesh, also using smoothing brush (hold shift) to smooth certain parts, and undo (ctrl + z) multiple times to simulate a normal working environment.)\n6. Try to pan or rotate the view around.\n\n\n\n**I found another way to trigger this bug, and it's not strictly related to sculpt mode.**\n(Tested on blender 3.1.0 beta 03b57d3973)\n\n1. Click around with a Wacom tablet.\n2. Pan the camera around with a Wacom tablet.\n3. Pan the camera around with a mouse.\n\n\n[sculpt mode bug.blend](sculpt_mode_bug.blend)\n\n[2022-01-17 04-48-11_Trim.mp4](2022-01-17_04-48-11_Trim.mp4)", "Viewport header menu, late/wrong responce to hover and click\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\n\n\nSometimes menu stucks when mouse pointer already over another menu.\n[2021-11-12_14-21-18.mp4](2021-11-12_14-21-18.mp4)", "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", "Regression: lag from camera view when using mouse scroll\nOperating system: Windows 10\nGraphics card: Nvidia Titan XP\n\nBroken: 3.3.1-3.5\nWorked: 3.2\nCaused by befe38fe1d\n\nMassive lag in camera view mode with objects about 20 mil triangles when using mouse scroll with view locked to camera even in Solid preview mode. When using Ctrl Alt mouse move seems no lag, scroll works as usual. Only scrolling is not working properly, rotation works nomally.\nIn this video: Blender 3.3.1, two separate cubes subdivided to level 10, first trying to scroll with mouse wheel - it lags, then using Ctrl Alt Mouse - no lag, then again with mousewheel - lag. No matter if GPU subdivision is on or off.\n\n- Open attached .blend file\n- first trying to scroll with mouse wheel - it lags\n- using Ctrl Alt Mouse - no lag\n[Blender Mouse scroll issue.blend](Blender_Mouse_scroll_issue.blend) \n[Lag when in camera view Blender 332.mp4](Lag_when_in_camera_view_Blender_332.mp4)", "Inconsistent input drag editing\nOperating system:\nGraphics card:\n\nBroken: \nWorked: \n\nSome inputs that allows editing whit mouse drag can change values with any drag movement, and the will be clamped to \nmin-max values, but other inputs relies on mouse position rather that the drag movement, this makes that if the user makes a drag beyond bounds, to be able to edit the values the user need to move the mouse again within the bounds of the input, that is not necessary because mouse is not visible.\n\n\n1. Use the color picker and move the mouse to the left beyond limits\n2. Move the mouse to the right, see that there not instantly a value change, the invisible mouse need to enters within bounds\n\n\n\nHere in the video, i edited the surface radius and is is visible that any movement changes the value\nBut for Surface the mouse need to be reallocated in the input box\nAlso for color picker\nImportant Note: **I force to show the mouse** to see the actual mouse movement, using the slider or color picker without knowing where the mouse is makes it feel weird \n<video src=\"attachment\" title=\"2023-08-16 17-58-31.mp4\" controls></video>\n\n", "Click selection and box selection in 3D view do not work properly in scenes with many objects\nOperating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\n[In my environment, if there are close to 100,000 objects, the objects can not be selected normally]\n[select_bug.mp4](select_bug.mp4)\n\nUploaded blend file has nearly 100,000 simple cubes\nClick on an object in the 3D view to select a distant object\nEven a box selection can make a crazy choice\nBut lasso selection and circle selection work fine\n[test_file.blend](test_file.blend)\n\n", "Trackpad stops working for a while\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M\n\nBroken: 3.6.2\nWorked: don't know\n\n\nSometimes, Blender stops responding to trackpad gestures such as two-finger scroll or pinch zoom. This is not just in the viewport but everywhere - I can't scroll menus or the node view, for example.\n\nThe UI is otherwise responsive when this happens - I can scroll menus by dragging the slider at the edge, just not with a two-finger scroll.\n\nIf I go and do something else in another app for a few minutes, it usually fixes itself.\n\nThis happens sporadically and I don't have a reliable way to reproduce it, but it seems to happen often after I render an image - after the image has rendered, I try to use pinch-zoom to look more closely and find I can't. I am not sure if it happens in other situations as well - if it does I will update this report.\n\n\nI'm afraid that I can't reproduce this reliably - it just happens every now and then, in any .blend file. I am happy to take any advice on how to look for a way to reproduce it.\n\n", "Skipping node auto-attachment doesn't work with custom keymap\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 526.86\n\nBroken: version: 3.5.0 Alpha\nWorked: none\n\nBy default holding `ALT` while dragging a node disables auto-attachment. However, this doesn't work when using a custom keymap that has been imported from previous version. The prompt doesn't show which key to hold, and holding `ALT` just makes the prompt flicker like crazy, but doesn't disable auto-attachment.\n\n\n\n\n**Steps to reproduce the bug**\n\n - Switch to a keymap that has been created with an earlier Blender version\n - Move a node in any node editor\n - Hold `ALT`\n\n\n\n", "Sometime when using color picker, Cursor will snap to middle of the screen.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Radeon RX Vega 64 ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.1\nWorked: 3.4.1 work normal\n\nWhen click drag to select color on color picker sometime cursor snap into middle of the screen\nIt happened everywhere that you can use color picker\n\nOccurred on 3.5 and 3.5.1 \n\nJust click drag on color picker it randomly happened \n\n[Snap Demo - Factory Setting.mp4](attachment)\n\n" ]

[ "Continuous grab 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 496.13\n\nBroken: version: 3.1.1 Release Candidate\nWorked: Blender 2.79\n\nWhen I use Continuous grab, any action associated with the grab starts to behave strangely. The cursor seems to jump from one value to another. The problem has been going on since version 2.8.\n\n[vivaldi_LI7Ow16Xrw.mp4](vivaldi_LI7Ow16Xrw.mp4)\n[blender_xV8aYKNaKD.mp4](blender_xV8aYKNaKD.mp4)\n[blender_VEuv5eOjFe.mp4](blender_VEuv5eOjFe.mp4)" ]

[ "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", "My blender doesnt open\nOperating system: Windows 10\nGraphics card: ?\n\n\nBroken: 3.6.2 LTS\nWorked: ?\n\n\nWhenever I try to open blender a Pop up appears saying \" No se pudo inicia la aplicacion;la configuracion en paralelo no es correcta.Consulte el registro de eventos de la aplicacion o use la herramienta sxstrace.exe para obtener mas detalles\"\n\nI have no idea, the one thats dowloaded by ZIP, i have already tryed this by the installer and the same problem\n\n\nWay literally, download blender and try to open it\nBased on the default startup or an attached .blend file (as simple as possible).\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. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "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)", "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)", "Weird VSE crash\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) no clue\n\nBlender crashes on opening file. Was trying to make an alternative caption that gets around the Multiply color issue #112267 but came across a new bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nOpen the file I've attached\n\n", "Blender Crash when deleting images too fast\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.44 30.0.13044.0\n\nBroken: version: 3.2.0\n\nBlender crashes when deleting images in the Layer blend file libery\n(3.3 alpha is crashing also and i didnt found any report about this issue)\n\n\n* go to outliner -> select blend file\n* make sure to be in the material preview mode\n* delete the first image by right click and then click on delete image\n* (now u only need to rightclick and leftclick to delete next images, because u dont need to aim for the delete anymore)\n* delete images while blender tries to preview the last change after deleting one of the images\n blender crashes\nwhen deleting images too fast, my blender just crashes (happens on my bad pc often, because i download models and rework them)\nIf you wait for the new material preview of the model after deleting nothing happens, but if you dont blender crashes when continuing to delete images\n\nVideo: CvO9nw4qilc\n\n[pharaoh x suite.blend](pharaoh_x_suite.blend)\n", "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 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", "GPencil: Blender crash when file open\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.0 Beta\n\nAs soon as I open attached file Blender crashes. Attached also crash log file.\n\n- Open attached file\n- Change radius (say 0.6)\n- Save file\n- reopen it (Crash)\n[#102930.blend](T102930.blend)", "use after free Fluid sim seg fault\nIn Debian testing, and Debian stable.\n\nbroken: blender 3.0.0 f7b22fc3d27113715e8726c69ab3264e1d487439\nbroken: Blender 2.93.0, Commit date: 2021-05-10 22:16, Hash ce62d650945f \nbroken: blender 2.92\n\nSegfaults on bake of modular fluid sim.\nReproducible each time I run blender on it.\n(Building a debug build now. the crash text isn't so useful yet).\n\n1. Load .blend (attached)\n2. Bake fluid\n3. Segfault\n\n[flu.blend](flu.blend)\nAsan report on f7b22fc3d27113715e8726c69ab3264e1d487439 [T88475_asan_use_after_free.txt](T88475_asan_use_after_free.txt)\nTwo crash reports on blender 2.92: \n[Blender_2021-05-22-145034_MACBOOKAIR.crash](Blender_2021-05-22-145034_MACBOOKAIR.crash)\nSimilar to #88113#1157996: [Blender_2021-05-22-193554_MACBOOKAIR.crash](Blender_2021-05-22-193554_MACBOOKAIR.crash)", "When Blender calls a python function thtrough a DLL, Blender crashes.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.0\n\nWhen Blender calls a python function thtrough a DLL, Blender crashes. \n\n[1] test.dll includes \"Python.h\". Python version is 3.10.9. test.dll has \"pyChecker()'.\nthe code of pyChecker():\n Py_Initialize();\n PyRun_SimpleString(\"print('Hello Python')\");\n Py_Finalize();\n\n[2] I built test.dll by Visual Studio 2019. C++ version is 14. \n\n[3] Import the dll by:\npyDll = ctypes.PyDLL (dllFilePath)\n\n[4] Call pyChecker() by:\npyDll.pyChecker()\n\n[5]Blender Console will print \"Hello Python\" and then crash directly.\n\n[Why do I use DLL?]\nIf Blender can call python functions through dll, developers can install add-ons by DLL. DLL also protects the code. For developers, it's helpful.\n\n", "Regression: Crash on Start Up\nOperating system: Mac OS 12.6.9\nGraphics card: AMD FirePro D500 3 GB\n\nBroken: blender-3.6.3-stable+v36.d3e6b08276ba-darwin.x86_64-release.dmg\nWorked: blender-3.6.3-candidate+v36.71b55b491e9c-darwin.x86_64-release.dmg\n\nApp crashes at start up.\n\nClick on App icon, app attempt to start, crash. I restarted my computer with same results. Not opening app from a .blend file. Tried opening default app with same result.\n\n", "Blender 2.93 crashes randomly\nHardware: MacBook Pro 13\", 8 GB 2016, as well MacMini 8GB 2020\nOperating system: MacOS\nGraphics card:\n\nBroken: version: 2.93.1\nWorked: ?\n\nI work with files exported from CAD-software packages imported into Blender showing technical installations: vacuum chambers and related technical infrastructure. I process the objects in the files by sorting them into collections representing subsystems (vacuum chambers, electrodes, magnets, ...) joining parts of larger systems, assigning materials from a material library file. I use hierarchies of files containing standard parts occurring at various places, materials and larger structures. In total, the files have a size of about 1 GB of data.\n\nWhen working with the files, Blender repeatedly and randomly crashes without obvious relation to specific actions.\n\nCannot provide this kind of information: random crashes.\n\nI am willing to give access to a git repo containing the 1 GB files\n\nSystem_info.txt:\n\n```lines\n> =====================================\n> = Blender 2.93.1 System Information =\n> =====================================\n> \n> \n> Blender:\n> =====================================\n> \n> version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: 1b8d33b18c2f, type: release\n> build date: 2021-06-22, 23:47:10\n> platform: Darwin\n> binary path: '/Applications/Blender.app/Contents/MacOS/Blender'\n> build cflags: -Wall -Werror=implicit-function-declaration -Werror=return-type -Wno-tautological-compare -Wno-unknown-pragmas -Wno-char-subscripts -Wstrict-prototypes -Wmissing-prototypes -Wunused-parameter -mmacosx-version-min=10.13 -Xclang -fopenmp -I'/Users/blender/git/blender-v293/blender.git/../lib/darwin/openmp/include' -std=gnu11 -msse -pipe -funsigned-char -fno-strict-aliasing -msse2 \n> build cxxflags: -Wall -Wno-tautological-compare -Wno-unknown-pragmas -Wno-char-subscripts -Wno-overloaded-virtual -Wno-sign-compare -Wno-invalid-offsetof -mmacosx-version-min=10.13 -ftemplate-depth=1024 -stdlib=libc++ -Xclang -fopenmp -I'/Users/blender/git/blender-v293/blender.git/../lib/darwin/openmp/include' -std=c++17 -msse -pipe -funsigned-char -fno-strict-aliasing -msse2 \n> build linkflags: -fexceptions -framework CoreServices -framework Foundation -framework IOKit -framework AppKit -framework Cocoa -framework Carbon -framework AudioUnit -framework AudioToolbox -framework CoreAudio -framework Metal -framework QuartzCore -framework ForceFeedback -liconv -Wl,-stack_size,0x100000 -Wl,-unexported_symbols_list,'/Users/blender/git/blender-v293/blender.git/source/creator/osx_locals.map' -stdlib=libc++\n> build system: CMake\n> \n> Python:\n> =====================================\n> \n> version: 3.9.2 (default, Mar 16 2021, 14:53:03) [Clang 10.0.0 (clang-1000.11.45.5)]\n> file system encoding: utf-8:surrogateescape\n> paths:\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/startup'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/modules'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/python/lib/python39.zip'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/freestyle/modules'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/addons/modules'\n> \t'/Users/wgeithner/Library/Application Support/Blender/2.93/scripts/addons/modules'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/addons'\n> \t'/Users/wgeithner/Library/Application Support/Blender/2.93/scripts/addons'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/addons_contrib'\n> \t'/Users/wgeithner/.local/lib/python3.9/site-packages'\n> \n> Python (External Binary):\n> =====================================\n> \n> binary path: '/Applications/Blender.app/Contents/Resources/2.93/python/bin/python3.9'\n> version: Python 3.9.2\n> \n> Directories:\n> =====================================\n> \n> scripts:\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts/modules'\n> \t'/Applications/Blender.app/Contents/Resources/2.93/scripts'\n> \t'/Users/wgeithner/Library/Application Support/Blender/2.93/scripts'\n> user scripts: '/Users/wgeithner/Library/Application Support/Blender/2.93/scripts'\n> pref scripts: None\n> datafiles: '/Users/wgeithner/Library/Application Support/Blender/2.93/datafiles'\n> config: '/Users/wgeithner/Library/Application Support/Blender/2.93/config'\n> scripts : '/Users/wgeithner/Library/Application Support/Blender/2.93/scripts'\n> autosave: '/Users/wgeithner/Library/Application Support/Blender/2.93/autosave'\n> tempdir: '/var/folders/qc/ph84tvmx4h19sn6wl8nnn8hw0000gn/T/blender_iWUimt/'\n> \n> FFmpeg:\n> =====================================\n> \n> avcodec: '58, 54, 100'\n> avdevice: '58, 8, 100'\n> avformat: '58, 29, 100'\n> avutil: '56, 31, 100'\n> swscale: ' 5, 5, 100'\n> \n> SDL:\n> =====================================\n> \n> Version: 2.0.12\n> Loading method: linked (WITH_SDL_DYNLOAD=OFF)\n> \n> Other Libraries:\n> =====================================\n> \n> OpenColorIO: 2, 0, 0\n> OpenImageIO: 2, 1, 15\n> OpenShadingLanguage: 1, 11, 10\n> OpenSubdiv: 0, 0, 0\n> OpenVDB: 8, 0, 0\n> Alembic: 1, 7, 16\n> USD: 0, 21, 2\n> \n> OpenGL:\n> =====================================\n> \n> renderer:\t'Intel(R) Iris(TM) Plus Graphics 640'\n> vendor:\t\t'Intel Inc.'\n> version:\t'4.1 INTEL-16.5.2'\n> extensions:\n> \tGL_APPLE_client_storage\n> \tGL_APPLE_container_object_shareable\n> \tGL_APPLE_flush_render\n> \tGL_APPLE_object_purgeable\n> \tGL_APPLE_rgb_422\n> \tGL_APPLE_row_bytes\n> \tGL_APPLE_texture_range\n> \tGL_ARB_ES2_compatibility\n> \tGL_ARB_blend_func_extended\n> \tGL_ARB_draw_buffers_blend\n> \tGL_ARB_draw_indirect\n> \tGL_ARB_explicit_attrib_location\n> \tGL_ARB_gpu_shader5\n> \tGL_ARB_gpu_shader_fp64\n> \tGL_ARB_instanced_arrays\n> \tGL_ARB_internalformat_query\n> \tGL_ARB_occlusion_query2\n> \tGL_ARB_sample_shading\n> \tGL_ARB_sampler_objects\n> \tGL_ARB_separate_shader_objects\n> \tGL_ARB_shader_bit_encoding\n> \tGL_ARB_shader_subroutine\n> \tGL_ARB_shading_language_include\n> \tGL_ARB_tessellation_shader\n> \tGL_ARB_texture_buffer_object_rgb32\n> \tGL_ARB_texture_cube_map_array\n> \tGL_ARB_texture_gather\n> \tGL_ARB_texture_query_lod\n> \tGL_ARB_texture_rgb10_a2ui\n> \tGL_ARB_texture_storage\n> \tGL_ARB_texture_swizzle\n> \tGL_ARB_timer_query\n> \tGL_ARB_transform_feedback2\n> \tGL_ARB_transform_feedback3\n> \tGL_ARB_vertex_attrib_64bit\n> \tGL_ARB_vertex_type_2_10_10_10_rev\n> \tGL_ARB_viewport_array\n> \tGL_ATI_texture_mirror_once\n> \tGL_EXT_debug_label\n> \tGL_EXT_debug_marker\n> \tGL_EXT_framebuffer_multisample_blit_scaled\n> \tGL_EXT_texture_compression_s3tc\n> \tGL_EXT_texture_filter_anisotropic\n> \tGL_EXT_texture_sRGB_decode\n> \tGL_NV_texture_barrier\n> \n> Implementation Dependent OpenGL Limits:\n> =====================================\n> \n> Maximum DrawElements Vertices:\t1048575\n> Maximum DrawElements Indices:\t150000\n> \n> GLSL:\n> Maximum Varying Floats:\t150000\n> Maximum Vertex Attributes:\t16\n> Maximum Vertex Uniform Components:\t4096\n> Maximum Fragment Uniform Components:\t4096\n> Maximum Vertex Image Units:\t16\n> Maximum Fragment Image Units:\t16\n> Maximum Pipeline Image Units:\t80\n> \n> Cycles:\n> =====================================\n> \n> \n> CPU device capabilities: SSE2 SSE3 SSE41 AVX AVX2\n> \n> Enabled add-ons:\n> =====================================\n> \n> io_anim_bvh (version: (1, 0, 0), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_anim_bvh/__init__.py)\n> io_curve_svg (version: UNKNOWN, path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_curve_svg/__init__.py)\n> io_mesh_ply (version: UNKNOWN, path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_mesh_ply/__init__.py)\n> io_mesh_stl (version: (1, 1, 3), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_mesh_stl/__init__.py)\n> io_mesh_uv_layout (version: (1, 1, 1), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_mesh_uv_layout/__init__.py)\n> io_scene_fbx (version: (4, 22, 0), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_scene_fbx/__init__.py)\n> io_scene_gltf2 (version: (1, 6, 16), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_scene_gltf2/__init__.py)\n> io_scene_obj (version: (3, 8, 1), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_scene_obj/__init__.py)\n> io_scene_x3d (version: (2, 2, 5), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/io_scene_x3d/__init__.py)\n> cycles (version: UNKNOWN, path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/cycles/__init__.py)\n> GTry (version: (1, 3, 7), path: /Users/wgeithner/Library/Application Support/Blender/2.93/scripts/addons/GTry/__init__.py)\n> add_curve_sapling (version: (0, 3, 4), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/add_curve_sapling/__init__.py)\n> materials_utils (version: (2, 2, 0), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/materials_utils/__init__.py)\n> materials_library_vx (version: (0, 6, 0), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/materials_library_vx/__init__.py)\n> render_auto_tile_size (version: (3, 1, 3), path: /Applications/Blender.app/Contents/Resources/2.93/scripts/addons/render_auto_tile_size.py)\n> ```\n\n\n[BlenderCrash_20210730-01](BlenderCrash_20210730-01)\n[BlenderCrash_20210801-01](BlenderCrash_20210801-01)" ]

[ "Blender Crash on Startup: Blender has stopped working\nOS: Windows 7 64-bit\nCPU: Intel Core i7-4770k @ 3.50 GHz\nGPU: Nvidia GeForce GTX 770\nRAM: 16.0 GB\nHard Drive: 250 GB w/ 53.1 GB remaining\n\n\nBroken: (all versions including 32-bit and 64-bit)\nWorked: (one year ago)\n\n**Immediately upon launching, the command prompt pops up quickly and is then covered by the Blender window. The Blender window will go gray and an error box will pop up with the message \"Blender has stopped working\" Blender will then crash.**\n\n**Launch Blender from desktop or .exe file. No matter which way I launch it, the same error occurs.**\n\nI used Blender version 2.68a 64-bit one year ago. It always worked without crashing. However now it will always crash.\n\n", "Blender Crashes on Startup\nCPU: f5fa1f4fc33cb4bb9d049bd2b1a6f9ce\nGPU: 3GB vRAM, AMD Radeon R9 280\n\nNewest, no more info\n\nBlender just crashes at the startup\n1.) Start blender.exe\n2.) Crash\n\nI debugged it, it crases on this ASM Instruction: \"vmovsd\"\n\nDebug Output: \nC:\\Users\\Bennet\\Documents\\blender-2.71-windows64>blender.exe -d\nSwitching to fully guarded memory allocator.\n*Crash*\nC:\\Users\\Bennet\\Documents\\blender-2.71-windows64>" ]

[ "Objects with clampto constraint change their position after the target object from copy rotation constraint is rotated and then pressed ctrl+z\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.3\nWorked: 2.82a\n\n\nOn the video clampto constrain is used on the ammo. When I rotate it and press ctrl+z ammo change their position and move chaotically\n\n[20210901_054810.mp4](20210901_054810.mp4)\n\n[#91102.blend](T91102.blend)\n\nRotate the empty and press ctrl+z, object array in \"ammo\" collection will change shape.\n", "Improve Render Region Border UI (show/hide the control gizmo)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\n\nRender Region UI control elements are active only after drawing in empty scene or after deleting any object in scene.\n\n1. Create new file and delete all objects in scene.\n2. Draw Render Region border (View --> View Regions --> Render Region or press CTRL+B).\n3. By dragging UI controls adjust Render Region border size.\n4. Add couple of objects to scene and draw Render Region border - UI controls aren't active now.\n5. Delete one of the objects and adjust Render Region border size.\n\n[DGSu5HJRQg.mp4](DGSu5HJRQg.mp4)\n\n", "The Tool Settings UI should update when holding modifier keys\nIn Sculpt Mode, users can hold Ctrl to invert the effect of the current tool. However, both the tool settings + and - buttons, as well as the color of the brush cursor, don't update to reflect that you've inverted the effect. \n\nBoth of these should update their state when the user holds Ctrl.\n\n\n\nThe same is true for the selection tools and their modes.\n\n{[F5686801](Screenshot_2018-11-23_at_00.36.36.png), full=true}\n\nWhen holding Shift or Ctrl to add or remove, the state of these buttons should update to reflect that. ", "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", "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.", "Can't re-select the previous tool in any paint mode after changing on Property Area\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nOn Texture Paint mode, can't select a tool after change the Image Paint Tool on Properties.\n\n[2019-11-29 21-01-51.mkv](2019-11-29_21-01-51.mkv)\n\n1. Select a tool on T Panel\n2. Change the Image Paint Tool on Properties to other tool\n3. Try to select again the first tool (Step 1)", "General purpose cleanup tool\nWe have a few areas where a cleanup tool can be helpful to keep a project organised:\n\n - remove empty vertex groups\n - delete shape keys with no effect\n - remove unused materials\n - remove items with 0 users\n - what else...?\n\nOne possible way to handle this is to add cleanup options to related operators. Like for example adding a \"remove empty vgroups\" option to the vertex clean tool.\n\nAnother possible way is to create a cleanup operator that can take a bunch of options (settings).\n\nSuch a tool could be directly built into Blender, or it could be created as an Addon.\n\nIf you know more areas where a cleanup tool would be helpful, then please add your finds to the list. Or if you have ideas how such a tool should operate, please add your ideas to this task.", "Changing rotation axis in operator panel has no effect\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.1.0 Alpha\n\nAfter confirming a rotation operator with a click, attempting to change the axis in the popup panel has no result.\n\n\nAdd any object. Press R to rotate it, and choose any specific axis. After you click to confirm, attempt to change the axis of rotation in the operator panel. \n", "Slow and laggy transforms using the tool pop-up box after clicking the transform gizmo\nOperating system: Windows 10 \nGraphics card: Geforce GTX 1650 Super\n\n3.5.0 (also same issue in 3.4.1)\n\nWhen I move/rotate the gizmo in the viewport with the mouse it is nice and responsive. However, when I use the rotate and move transform value sliders in the transform pop-up box the values are very slow to update and the viewport object being transformed lags quite drastically. Not only when using the mouse to slide value but using the increment arrows too. This seems to only be when using the TRANSFORM_OT_translate.value / TRANSFORM_OT_rotate.value / TRANSFORM_OT_resize.value \nAs a note the viewport side panel Item-Transform (Object.location, Object.rotation_euler, Object.scale) doesn't seem to have this problem and updates as it should, allowing nice responsive viewport updates as the value slider is dragged.\n\n- Unzip attached file\n- Open .blend file\n- Select any object\n- Rotate it with the help of viewport gizmo\n- Now change values from redo panel (notice slowdown).", "Annotation tool in Image Editor does not switched off when mode is changed\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version:\n- 2.93.0 Alpha\n- 2.91.2\n- 2.90.1\n- 2.83.10\n- 2.81a\n- 2.80\nWorked: Never\n\n\nWhen annotation tool is selected in View Mode, and then changed to the Paint Mode,\nthe annotation tool remains \"ON\" even if Draw tool is active in Paint Mode. \n\n\n\nI uploaded a snapshot.\nThe active tool is Draw tool, as shown in tool panel.\nBut the annotation line is drawn when the mouse is dragged.\n\n- Open the Image Editor and create a new image.\n- Switch to *Paint* mode in the *Image Editor* and select the *Draw* tool.\n- Switch to *View* mode in the *Image Editor* and select the *Annotation* tool.\n- Switch to *Paint* mode and notice that the *Draw* tool is indicated as active tool in the toolbar\n# Try to use the *Draw* tool.\nAn annotation line is drawn instead of a brush stroke with the *Draw* tool. It only starts to work once the tool is reselected in the toolbar.", "Animation Editors: Modifier keys cancel out dragging handles \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.4.0 Alpha\n\nIn recent releases db4313610cab was implemented and the animation editors are still not adapted to this behaviour. This fix allows the use to press any keyboard key, like `Shift` or `X`, etc, before the drag threshold of the current action is reached, and it will cause the operator to execute.\n\nFor example: Click and hold on a move gizmo in object mode. Either drag 3 pixels to start the operation and then press `X` and hold `Shift` to slowly move along the x axis.\nOR immediately press `X` and hold `Shift` without reaching the drag threshold of 3 pixels to already start the operator.\n\nBefore this fix, any pressed keys would cancel the click & drag and prevent the operator from running.\nThis is still the case with the graph and dopesheet editors.\n\n- Create a simple animation to the default cube\n- click and drag on the keyframes or handles in the animation editors\n- Now click and hold them, hold `Shift`, and then continue to drag. Nothing happens.", "Move origin from Transform Options not working for collection correctly - not moving, but moving if Object Set Origin is changed\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.0.1\nBroken: version: 3.2.0\nWorked: (newest version of Blender that worked as expected) - don't know any working version from 2.8\n\nMove origin from Transform Options not working for collection correctly - not moving, but moving if Object Set Origin is changed\nLooks like limitation maybe around Transform Options and lack of implementations or bug that blocking move origin.\nWhen using addon Cad Tranform (slcad_transform_0.91.0.zip) and Turn on Transform Options Origins then can move origin (but problems with magnet snap).. soo looks like bug in blender grab area.\nAnyway it's problem when looking correct position for my object and work with collections, only addon can solve problems.\n\n1. Turn on Transform Options Origins - try move origin for Collection2, eg. for corner\n2. Turn off Transform Options Origins, select Object Set Origin and Origin to Center or other option\n\n\n\n\n[Origin_bug.blend](Origin_bug.blend)\n", "GPencil: Hotkeys of Tools is not consistent when Draw Tool is active\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.76\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nI'm not sure whether this is intended or not.\nHotkeys (1 to 9) shift downward one by one depending on whether you are in a draw tool or not.\n\n1. Go to Draw Mode\n2. Select a draw tool by pressing Shift Spacebar, O (Not 1)\n3. Select a fill tool by pressing Shift Spacebar, 1\n4. Select a draw tool by pressing Shift Spacebar, 1 (Not O)\n\n", "Inset operator modal handling misses option to toggle \"Offset Even\" via shortcut\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nNoticed problems when using Inset Faces tool in Edit Mode. If I'm using the select tool and I press **I** to activate the tool Inset Faces tool its menu doesn't display anywhere so I can't choose Even for example. If I click on the tool icon then it works, even if I then use **I** to activate the tool. This makes it so I can't use shortcut keys anymore. I suspect this is happening with other tools as well. Another thing worth noting is that the status bar says the Call Menu is triggered by the right mouse button but it actually just closes the tool.\n\n\n\n\n\n\nGo into edit mode with the default cube. Select a face. Hit I to activate the inset faces tool. Notice that the options for the tool aren't available.\n\n", "NLA: Fix Dragging Strips\nNOTE: test the patches for Solution1 temp-[D10103](https://archive.blender.org/developer/D10103)-nla_support_strip_overlap_during_transform/temp-[D10103](D10103)-nla_support_strip_overlap_during_transform-blender-2.92.0-5065c0e6d5bc-windows64.zip\n\nThis is no longer true, we would rather remove them and improve the interaction with HOLD type ****Update design since transition strips should be kept.****\nTodo: Add concrete examples where transitions are useful in the ideal case (where strips animate through the transition).\n___\nReport: #82195 (NLA tracks won't pass through actions or locked tracks)\n\n**Summary:** The ideal solution is to get rid of transition strip types. They're useless. Let strips overlap. When they do, they get blended in order like an upper strip. Then we don't have to restrict movement.\n\n___\n\nBehavior can be found in: (transform_convert_nla.c) *recalcData_nla()*\n**Problem**: The core intent of the function is to prevent moved strips from overlapping other strips. The restriction is reasonable since NLA evaluation is undefined in this case. However, the implementation prevents the ability to move a strip to its destination even if it wouldn't result in overlap. \n\nWhen moving strips:\n* You cannot move a strip through a locked track, even if not the intended final destination.\n\n* You cannot move a strip past another in the same track, even if the intended final destination would not result in overlap.\n\n* You cannot move a strip into through or into a track if doing so results in overlap. \n\n* Vertically moving strips, when there are no more nla tracks, leads to strips being vertically compressed. This breaks the animation when strip extrapolation is important.\n\n___\n**Solution1:** (Simpler solution) We only apply the restriction on the final strip location. If the strip cannot be placed without overlap, then we either cancel the move operation (not ideal) or notify the user (show the strip as red?) without cancelling.\n\n[D10101: Cleanup: Nla: Refactor nla.c functions](D10101) (independent patch) Does a little bit of refactoring which [D10103](D10103) relies on.\n[D10102: NLA: Strip Post-transform Horizontal Shuffle](D10102) (independent patch) Adds support for horizontal shuffling so users can horizontally drag strips past eachother.\n[D10103: NLA: Strip Post-transform Vertical Shuffle and Auto-Grow Track List](D10103) (depends on prior patches) Adds support for vertical shuffling so users can vertically drag strips into a new track even if it results in overlap or the user moves the strip into a locked track.\n\nPatches have been made for this solution since it's simpler and faster to implement. Overlap support can still be worked on but is a lower priority and still has design problems to figure out.\n___\n**Solution2:** (Ideal solution, but would take longer to implement) We change NLA evaluation to work properly when strips overlap. Then we can completely remove the restriction and let the animator freely move strips. \n \n**Patch1: Completely remove transition types**\nWe can simplify NLA evaluation here a bit. NLA transitions are problematic and ineffective. *Transition strip types should be completely removed.* They do a lerp between the previous strip's last pose and next strip's first pose. Generally in animation, lerping 2 poses is a problem you fix, not something you ever want. Support-wise, transitions are a bit broken anyways (see [D9711](D9711) and [D9713](D9713))\n\n**Patch2: Implement new behavior when strips overlap**\nInstead of an explicit transition strip type, we'll let action and meta strips support a new transition behavior. When two strips overlap, we simply blend the next strip as if it was an upper strip. That's the core idea. \"Transitioning\" strips of the same track would used for convenience and organization. This would simplify the keyframe remapping math. In [D8296](D8296), I couldn't figure out the math to properly invert through transitions between a Quaternion Combine strip and a Quaternion Replace (or any non-Combine) strip. With the new behavior, keyframing through transitions is simplified to inverting through any other strip. \n\n**Patch3: Re-add support for holding poses through the transition**\nThough, as is, both strips are always animated through the transition. We don't have the ability to hold one strip's boundary pose while the other animates through the transition. I propose a few new strip properties: `hold_left_duration` (unit: scene frame), `hold_right_duration`. The influence over these regions can be automatically calculated when strips overlap. Or they can be keyed into shape using the existing influence fcurve. As an example of these new properties, we'll have two strips that only overlap over this held duration. \n*Note. I'm having second thoughts on the properties. Yes, there should be support for holding poses through the transition. But the problem is how these properties are anchored relative to the strip bounds and what's most convenient. I want to avoid problems like the ones we already have with nla strip frame_start/end being tightly related to the action clips frame_start/end, scale and repeat values. This leads to unintuitive strip frame_start/end changes.*\n\n**Patch4: Finally loosen strip dragging logic (only relies on patch2)**\nWe can completely remove the dragging restriction and let the animator freely move and overlap strips.\n \n___\n\n(Pretend the two strips are in the same row/track. I did not draw them that way because I'm not sure how the UI should look. This also isn't a suggestion for how the UI should render)\n\nThis results in *nearly*the same result as old Transition clips. Only *nearly*, because the old implementation would first blend the prev strip with the lower NLA stack, then blend the next strip with the lower NLA stack, then lerp the two. The new behavior holds the previous strip's last pose over the light green area. The next strip's first pose is held over the pink area. The influence of the next strip increases linearly. \n___\n\nThis holds the previous strip's last pose. The next strip animates as it's blended.\n___\n\n\nAnother possibility.\n___\n\n**Problematic UI case**: I'm not sure what the proper UI should look like when one strip completely overlaps. The animator can always just move the strip out above as a work around. Logically, it would evaluate fine. It would just be a UI issue. What if N strips overlap? It still all works out. We blend the strips in the order of their start frame. What if all strips are on the same start frame? That case won't be properly supported and considered undefined (as in we won't fix it). The animator can and should fix it themselves. \n__\n\n**Alternative WorkAround:** Add operators that can be used as workarounds.\n* ([RCS]())Send strip to the end of the active strip or track, with options to handle overlap properly. \n\n___\nPatches:\n\n**(Abandoned)Patch set 1: Removal of transitions** \n*Note: I'm not sure how file versioning should be handled? I haven't removed the strip type NLASTRIP_TYPE_TRANSITION yet. I'm not sure if the enum should remain so it can be used for file versioning to either delete transitions or convert them to the new behavior (after Patch set 3).*\n[D9702: Nla Transitions Obselete: remove ui icon](D9702)\n[D9703: Nla Transitions Obselete: Nla Stack no longer evaluates Transitions](D9703)\n[D9704: Nla Transitions Obselete: Remove Operator Add Transition](D9704) \n[D9705: Nla Transitions Obselete: Remove themed drawing](D9705) \n[D9706: Nla Transitions Obselete: Remove default naming case](D9706) \n[D9707: Nla Transitions Obselete: Special case for adjacent strip deletion](D9707) \n[D9708: Nla Transitions Obselete: Adjacent strip overlap resolution](D9708) \n[D9709: Nla Transitions Obselete: nlastrip_get_frame()](D9709) \n[D9710: Nla Transitions Obselete: RNA strip frame_start/end set functions](D9710) \n[D9711: Nla Transitions Obselete: Transform, redundant check](D9711) \n[D9712: Nla Transitions Obselete: Transform, Cancelling](D9712) \n[D9713: Nla Transitions Obselete: Transform, broken strip exceed resolution](D9713) \n[D9714: Nla Transitions Obselete: Loose comments](D9714)\n**Abandon Reason:** I misunderstood why transitions were limited. Yes, their current implementation only supports single pose transitions. But they would be more useful if the strips animated through the transition. Alexander Gavrilov suggested we keep transitions for their branched evaluation behavior.\n" ]

[ "Regression: Transform Gizmos doesnt work anymore\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\n\nGizmos from the Toolbar wont react (Edit and Object mode).\n\n[2020-08-21 02-28-38.mp4](2020-08-21_02-28-38.mp4)\n" ]